System Error Messages Guide For Access and Edge Routers
Available Languages
System Error Messages Guide for Access and Edge Routers
Revised: November 28, 2018
Overview of System Messages
Use this document together with the tools and utilities that are available on Cisco.com on this page:
http://www.cisco.com/c/en/us/support/index.html
■ Cisco Technical Assistance Center (TAC): https://mycase.cloudapps.cisco.com/case
■ Bug Search Tool link: https://bst.cloudapps.cisco.com/bugsearch/
Note: When contacting TAC, please have available the nonzipped, plain-text (.txt) output of the show logging and show tech-support commands, as well as any pertinent troubleshooting logs.
System messages can be grouped into these categories:
■ System Event Messages—Describe the system and error messages that are generated for events related to the Cisco platform, and its hardware and software components.
■ DOCSIS Event Messages—Describe the error messages for events as required by the DOCSIS specifications.
■ Video/QAM Event Messages—Describe the error messages for events as required by the Video specifications.
System error messages begin with a percent sign (%) and are structured as follows:
%FACILITY-SUBFACILITY-SEVERITY-MNEMONIC: Message-text
System error messages contain the following components:
■ FACILITY is a code indicating the platform or other component that is generating the message.
■ SEVERITY is a number that reflects the significance of the error message. All error messages have a Cisco severity number that ranges from 0 to 7. DOCSIS-related events also contain a DOCSIS severity level that ranges from 129 to 136. The lower the number, the more serious the situation. This table describes the possible severity levels and their meanings.
■ MNEMONIC is a string that uniquely identifies the error message. Error messages are usually organized and referred to by their mnemonic value.
■ The Message-text is a string that provides details about the particular error. This string can include specifics about cable interface, IP or MAC addresses, and other information. In this document, the specific information is presented by variable fields that are indicated by square brackets ([ ]). A decimal number, for example, is represented as [dec].
System Messages Description
A
AAA
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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 <CmdBold>Show tech-support<NoCmdBold> command, Collect all the information and error message and report it to your technical support 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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-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 <CmdBold>Show tech-support<NoCmdBold> 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 <CmdBold>show running- config<NoCmdBold> command, contact your cisco technical support representative and provide all the information gathered to the representative.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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 <CmdBold>Show tech-support<NoCmdBold> command, Collect all the information and error message and report it to your technical support representative.
%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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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 <CmdBold>Show tech-support<NoCmdBold> command, Collect all the information and error message and 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 <CmdBold>Show tech-support<NoCmdBold> command, collect all the information and 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 <CmdBold>Show tech-support <NoCmdBold> command, collect all the information and error message, 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 <CmdBold>Show tech-support<NoCmdBold> command, Collect all the information and error message and report it to your technical support representative.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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.
AAAA
%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-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-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-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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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-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-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. <CmdBold>[no] aaa accounting update newinfo periodic <interval><NoCmdBold>
%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-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-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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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-NOADMINPROC : [chars]
Explanation Administrative process has been enabled but somehow could not run
Recommended Action None
%AAAA-3-NOFREELISTS : %%AAA: No free [chars] lists for [chars]
Explanation You have reached the maximum number of possible authentication lists for this method.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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-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-OVERWRITE : Overwrote internal buffer space [chars]
Explanation An internal software error.
Recommended Action Report to tac@cisco.com.
%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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%AAAA-3-SUBTYPE : Bad Subtype [dec] for [chars] ([dec])
Explanation An internal software error.
Recommended Action Report to tac@cisco.com.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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-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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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-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-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-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-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-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-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-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-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-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-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-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
AC
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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-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 <CmdBold>no crypto map command. Then reattach the cryptomap set to the interface using <CmdBold>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-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-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-CEAL_REGISTRATION : ACE [chars] failed to register.
Explanation The ACE failed to register with CEAL
Recommended Action Reset the hw module
%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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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.
ACL
%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-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
ADJ
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%ADJ-5-ADJISSUINCOMPATIBLE : All or part of sdjacency 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-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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
ALARM
%ALARM-3-CLEAR : [chars] [chars] [chars] [chars] [chars]
Explanation None
Recommended Action None
%ALARM-3-NOMEM : OUT of Memory: [chars]
Explanation None
Recommended Action None
%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 None
Recommended Action None
%ALG_COM-3-ALG_REGISTER_FAILED : [dec]
Explanation ALG registration failed.
Recommended Action LOG_STD_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_PROXY
%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
%ALG_PROXY-3-PROXY_MEM_EXTEND_FAILED : ALG IPC subtype: [dec]
Explanation Extending memory failed.
Recommended Action LOG_STD_ACTION
%ALG_PROXY-3-PROXY_MEM_REQ_FAILED : ALG IPC subtype: [dec]
Explanation Requesting more memory failed.
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-4-PROXY_IPC_INVALID_MSG_LEN : [dec]:[dec] len [dec] flags [hex] source [dec]
Explanation Invalid IPC message length.
Recommended Action LOG_STD_ACTION
ALIGN
%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-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-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-RO_WRITE : Spurious memory access made at [chars] writing to [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 <CmdBold>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 <CmdBold>show alignment output, call your Cisco technical support representative and provide the representative with the gathered information.
%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 <CmdBold>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 <CmdBold>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-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.
ALPS
%ALPS-3-ALPSFAIL : ALPS: Assertion failed: [chars]
Explanation An internal software error has occurred.
Recommended Action LOG_STD_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
%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-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-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-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-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-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-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_BUSY_START : Circuit [chars] has entered a congested state.
Explanation An ALPS circuit is experiencing congestion.
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_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_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-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-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_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-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_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_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_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_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_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-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_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-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_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
AMT
%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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
AN
%AN-3-ACP_CHANNEL_TO_NBR_FAILED : Failed to create ACP channel to neighbor [chars] on phy interface [chars]
Explanation Autonomic Network Control Plane Channel has not been created to the neighbor
Recommended Action No action is required.
%AN-3-ACP_IPSEC_TO_NBR_FAILED : Failed to create IPSEC tunnel [chars] to neighbor [chars]
Explanation Autonomic Network Control plane - Failed to create IPSEC tunnel to neighbor
Recommended Action No action is required.
%AN-3-ACP_VRF_GLOBAL_CREATE_FAIL : Failed to create AN VRF globally, vrf name [chars], vrf id [dec]
Explanation Autonomic network VRF has not been created globally
Recommended Action No action is required.
%AN-3-ACP_VRF_INTERFACE_CREATE_FAIL : Failed to create AN 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-3-ANRA_WHITELIST_FILE_ERROR : ANRA dev id [chars] domain id [chars] -error in reading from whitelist file [chars], will continue without any whitelist devices
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-DOMAIN_KEY_GEN_FAIL : The bootstrapping device [chars] failed to generate key pair for enrollment at ANRA
Explanation The key pair generation failed at the device for triggering BS request message to ANRA. Can be due to failure in RSA key pair generation in the crypto library
Recommended Action No action is required.
%AN-3-IDP_INTENT_FILE_ERROR : Error in reading from intent file -[chars]
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-3-MSG_INVALID_HEADER : Invalid message header type [dec] received
Explanation The message packet header got corrupted and invalid header obtained
Recommended Action No action is required.
%AN-3-NBR_DOMAIN_CERT_INVALID : Invalid domain certificate of neighbor device udi [chars] on interface [chars]
Explanation The domain certificate of the neighbor device is in invalid
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-4-ANRA_SIGN_VERIFY_FAIL : Signature verification of ANRA by new device has [chars]
Explanation The new device joining the network verified the signature of ANRA as a part of mutual authentication and the verification failed
Recommended Action No action is required.
%AN-4-DEVICE_NOT_ALLOWED_BY_ANRA : Device udi [chars] is not allowed by ANRA in its domain [chars]
Explanation The autonomic network registration authority will not allow this device to join
Recommended Action No action is required.
%AN-4-MASA_AUDIT_LOG_FAIL : Device 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-4-MASA_AUTH_FAIL : Device 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_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-5-ANRA_DOWN : Disabled ANRA @ device udi [chars]
Explanation The autonomic network registration authority functionality is disabled
Recommended Action No action is required.
%AN-5-ANRA_UP : Configured ANRA, device id [chars], AN domain id [chars]
Explanation The autonomic network registration authority has been confgiured and is locally up
Recommended Action No action is required.
%AN-5-DEVICE_BOOTSTRAPPED_BY_ANRA : Device udi [chars] has been boot strapped by ANRA, in AN domain [chars]
Explanation The autonomic network registration authority has bootstrapped this device
Recommended Action No action is required.
%AN-5-IDP_INTENT_VER_OLD_DISCARD : Dicarding older intent version-[dec]
Explanation The device obtained an old intent file by Intent Distribution Protocol and is dicarding it
Recommended Action No action is required.
%AN-5-IDP_INTENT_VER_UPDATED : Updated to a new intent version [dec]
Explanation The device obtained a new intent file by Intent Distribution Protocol
Recommended Action No action is required.
%AN-5-NBR_ADDED : nbr udi [chars] is added as a neighbor on interface [chars]
Explanation A hello message as obtained and the device is added in the neighbor table
Recommended Action No action is required.
%AN-5-NBR_IN_DOMAIN : nbr udi [chars] on interface [chars] is inside the AN domain [chars] -got device id [chars]
Explanation The device has been admitted into the autonomic domain
Recommended Action No action is required.
%AN-5-NBR_LOST : connectivity to nbr udi [chars] on interface [chars] is lost
Explanation Lost connectivity to the neighboring device & it is no longer part of AN domain
Recommended Action No action is required.
%AN-5-NBR_OUT_DOMAIN : nbr udi [chars] on interface [chars] is outside the AN domain
Explanation The device is removed from the AN 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-SERVICE_LEARNT : AN service learnt, Service Type [dec] Service IP Addr [chars]
Explanation The device obtained a new AN service by Service Discovery Protocol
Recommended Action No action is required.
%AN-6-ACP_CHANNEL_TO_NBR_CREATED : Established ACP channel [chars] to neighbor [chars] on phy interface [chars]
Explanation Autonomic Network Control plane Channel has been created to the neighbor
Recommended Action No action is required.
%AN-6-ACP_CHANNEL_TO_NBR_REMOVED : Removed ACP channel (phy int [chars]) to neighbor [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 tunnel [chars] to neighbor [chars]
Explanation Autonomic Network Control plane - IPSEC tunnel established to neighbor
Recommended Action No action is required.
%AN-6-ACP_IPSEC_TO_NBR_REMOVED : Removed IPSEC tunnel [chars] to neighbor [chars], Tunnel state [dec]
Explanation Autonomic Network Control plane - IPSEC tunnel to neighbor is removed
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_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_VRF_GLOBAL_CREATE_SUCCESS : AN VRF created globally vrf name [chars], vrf id [dec]
Explanation Autonomic network VRF has been created globally
Recommended Action No action is required.
%AN-6-ACP_VRF_GLOBAL_REMOVE : AN 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 : AN VRF created 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-6-ANRA_WHITELIST_CONFIG : ANRA dev id [chars] domain id [chars] has whitelist-will allow only these devices in AN 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-ANRA_WHITELIST_NOT_CONFIG : ANRA dev id [chars] domain id [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-6-DEVICE_ALLOWED_BY_ANRA : Device udi [chars] is allowed by ANRA in its domain [chars]
Explanation The autonomic network registration authority has authorised this device to enter its network
Recommended Action No action is required.
%AN-6-MASA_NOT_CONFIG : ANRA 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-NBR_DOMAIN_CERT_VALID : Validated domain certificate of neighbor device udi [chars] on interface [chars]
Explanation The domain certificate of the neighbor device is validated successfully
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-6-UDI_AVAILABLE : UDI -[chars]
Explanation Unique device identification number is available on the device
Recommended Action No action is required.
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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
APPFW
%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-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-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_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_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_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-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_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_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_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_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_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_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-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-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.
%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_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_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_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_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.
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-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-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-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-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-4-SERVICE_CTX_DISABLE : SERVICE-CONTROLLER: Alarm 10001, Severity: Major Disabling service context [chars]
Explanation Disabling service context
Recommended Action None
%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-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-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-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-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
ARAP
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%ARAP-0-NULLRESEND : TTY [dec]
Explanation An internal software error occured.
Recommended Action Report this error to you technical support representative.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-6-XTICKLE : TTY [dec]: exited user [chars]: Other side stopped answering ARAP tickles (mnp4 pak resent [dec] mnp4 pak sent [dec] last [dec] now [dec])
Explanation The router disconnected as the remote Macintosh client stopped sending ARAP tickle or data packets.
Recommended Action To determine the cause of the disconnection, correlate the receipt of this message with the user problem reports.
ARCHIVE_CONFIG
%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-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-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-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)
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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-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-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-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-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-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-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>)
ARP
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%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-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-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-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-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-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.
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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%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-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-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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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-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-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-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-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-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-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-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-NOSOCKET : [chars]: client tried to open socket, but failed
Explanation open socket failed;Possible out of memory situation
Recommended Action None
%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-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-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-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-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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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-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-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-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-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-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-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-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-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-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-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-5-LOSTNEIGHBOR : [chars]: AppleTalk neighbor down; lost contact with %#a
Explanation A peer router is unreachable.
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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-NEWZONE : AppleTalk zone added; zone %*s defined
Explanation A new AppleTalk zone was created.
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-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-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-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-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-REGPENDING : NBP registration of [chars] at [[chars]] pending
Explanation A name registration call is being performed.
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-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-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-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-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-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-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.
ATA
%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.
%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.
ATMSIG
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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.
%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.
ATMSPA
%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: https://mycase.cloudapps.cisco.com/start 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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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-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: https://mycase.cloudapps.cisco.com/start 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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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 show tech-support to your support representative, or attach it to your case
%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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%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-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: https://mycase.cloudapps.cisco.com/start 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: https://mycase.cloudapps.cisco.com/start 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.
ATMSSCOP
%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-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-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_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-PROXY_UNHANDLED_MSG : subtype [dec]
Explanation Attention proxy received a message with an unknown subtype.
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-0-CONFIG_CORRUPT : Checksummed interface configuration corruption detected.
Explanation Interface configuration field was modified unexpectedly.
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-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-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-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-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 <cmdbold>shutdown<nocmdbold> command followed by <cmdbold>no shutdown<nocmdbold> command to restart the port.
%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-VLANASSIGN : VLAN [dec] assigned to Interface [chars] AuditSessionID [chars]
Explanation VLAN assignment
Recommended Action No action is required.
%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-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-7-STOPPING : Stopping '[chars]' for client [enet] on Interface [chars] AuditSessionID [chars]
Explanation Stopping the current authentication method
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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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_UPGRADE
%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_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_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_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-3-AUTO_UPGRADE_FAILED_COPY : Failed to copy upgrade packages from switch [dec] to switch [dec].
Explanation TODO: add an explanation.
Recommended Action TODO: add an action
%AUTO_UPGRADE-3-AUTO_UPGRADE_FAILED_DISK : Switch [dec] doesn't have enough free disk space to perform auto upgrade. A minimum of [dec] KB of free disk space 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-AUTO_UPGRADE_FAILED_MEM : Switch [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_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_FAILED_STATE : A previous provisioning action is pending reboot. Please reboot the switch [dec].
Explanation The user has run an operation that requires a reboot to take action.
Recommended Action Reload the switch
%AUTO_UPGRADE-3-AUTO_UPGRADE_INTERNAL_ERROR : Stack manager did not publish local information
Explanation Somehow the chassis number is missing.
Recommended Action Try to do it again.
%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_UPGRADE_NOTHING_TO_UPGRADE : No incompatible switch 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_NOT_SUPPORTED : The system is not running installed software. Auto upgrade for switch number [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 is not running installed software. The user must manually upgrade the incompatible switch.
Recommended Action Expand the super package to /flash. Boot the package from the flash using 'boot flash:packages.conf'
%AUTO_UPGRADE-3-AUTO_UPGRADE_PLATMISMATCH : No software was found to upgrade switch [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_UPGRADE_ROMMON : Failed to set boot var on switch [dec]. Please use the 'reload' command to reload the switch and then manually set the BOOT rommon var to [chars].
Explanation TODO: add an explanation.
Recommended Action NO action is 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-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-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-5-AUTO_ADVISE_SW_CONV : Switch [dec] running bundled software has been added to the stack that is running installed software.\The 'request platform software package install autoupgrade' command can be used to convert switch [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_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_ADVISE_SW_INITIATED : Auto advise initiated for switch [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_ADVISE_SW_MSG : Switch [dec] with incompatible software has been added to the stack. \all stack members were scanned and it has been determined that the\ 'request platform software package install autoupgrade' command can be used \to install compatible software on switch [dec].
Explanation TODO: add an explanation.
Recommended Action TODO: add an action
%AUTO_UPGRADE-5-AUTO_ADVISE_SW_SEARCH : Searching stack for software to upgrade switch [dec].
Explanation Just an init message.
Recommended Action No action is required.
%AUTO_UPGRADE-5-AUTO_ADVISE_SW_START : Upgrading switch [dec] with software from switch [dec].
Explanation Just an init message.
Recommended Action No action is required.
%AUTO_UPGRADE-5-AUTO_UPGRADE_CONV : Converting switch [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-5-AUTO_UPGRADE_FINISH : Finished installing software on switch [dec].
Explanation TODO: add an explanation.
Recommended Action TODO: add an action
%AUTO_UPGRADE-5-AUTO_UPGRADE_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_INITIATED : Auto upgrade initiated for switch [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-5-AUTO_UPGRADE_INSTALLED : Finished installing the running software on switch [dec].
Explanation TODO: add an explanation.
Recommended Action TODO: add an action
%AUTO_UPGRADE-5-AUTO_UPGRADE_RELOAD : Reloading switch [dec] to complete the auto upgrade.
Explanation Part of autoupgrade
Recommended Action Just wait until the reload completes.
%AUTO_UPGRADE-5-AUTO_UPGRADE_RELOAD_INSTALLED : Reloading switch [dec] to boot in installed mode.
Explanation TODO: add an explanation.
Recommended Action TODO: add an action
%AUTO_UPGRADE-5-AUTO_UPGRADE_SEARCH : Searching stack for software to upgrade switch [dec].
Explanation Just an init message.
Recommended Action No action is required.
%AUTO_UPGRADE-5-AUTO_UPGRADE_START : Upgrading switch [dec] with software from switch [dec].
Explanation Just an init message.
Recommended Action No action is required.
AUTO_UPGRADE_MODULAR
%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
%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-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_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-5-AUTO_NOTICE_STBY_RELOAD : Installing SMUs on standby. Standby will reload
Explanation No explanation required.
Recommended Action No action required.
B
BFD_HA
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
BFD_ISSU
%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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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-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_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-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-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_OFFLOAD
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
BFD_PROXY
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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-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.
%BINOS_LOGIN-3-PAMERR : PAM error [chars] encountered.
Explanation The system encountered a PAM error.
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-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.
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/c/en/us/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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
BOOT
%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-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-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-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_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-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_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-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-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-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-5-BOOTTIME_SMU_MISMATCH_DETECTED : SMU mismatch from active dectected. 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-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-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-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-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.
BSC
%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.
%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.
BSHELL
%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-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_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-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-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.
%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-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-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-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-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-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-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.
BSTUN
%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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%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.
%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-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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%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-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-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-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-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-6-RECONNECT : PHDR: reconnect from peer [chars]
Explanation A remote peer reestablished a connection to this router.
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-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.
BTRACE_ROTATE
%BTRACE_ROTATE-3-ARCHIVE_FAIL : Error archiving trace file -[chars]
Explanation While trying to archive a trace file on the active RP, an error occurred that prevented the file transfer. The trace file is not saved.
Recommended Action This message is usually seen a result of an underlying problem with the harddisk: file system, so check the console log for messages related to harddisk: file system messages.
BUFCAP
%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 Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, copy the error message exactly as it appears on the console or in the system log, enter the <CmdBold>show monitor capture point all<NoCmdBold> and <CmdBold>show tech<NoCmdBold> commands and contact your Cisco technical support representative, providing 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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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-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-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-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-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-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-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-ENABLE : Capture Point [chars] enabled.
Explanation Specified capture point has been enabled.
Recommended Action No action is required.
%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 None
%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.
C
CALL_CONTROL
%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-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-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-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
%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-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-CALL_LOOP : The incoming call has a global identfier already present in the list of currently handled calls. It is being refused.
Explanation The incoming call has a global identfier 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-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-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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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_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 <CmdBold>show proc cpu<NoCmdBold> 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 <CmdBold>call threshold global cpu-5sec<NoCmdBold> 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 <CmdBold>call threshold poll-interval<NoCmdBold> 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 <CmdBold>show proc cpu<NoCmdBold> 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 <CmdBold>call threshold global cpu-avg<NoCmdBold> command.
%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 <CmdBold>show proc cpu<NoCmdBold> 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_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 <CmdBold>show mem<NoCmdBold> and <CmdBold>show proc mem<NoCmdBold> 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 <CmdBold>call threshold global io-mem<NoCmdBold> 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 <CmdBold>show mem<NoCmdBold> and <CmdBold>show proc mem<NoCmdBold> 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 <CmdBold>call threshold global total-mem<NoCmdBold> 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 <CmdBold>show mem<NoCmdBold> and <CmdBold>show proc mem<NoCmdBold> 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 <CmdBold>call threshold global proc-mem<NoCmdBold> 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 <CmdBold>call threshold global proc-mem<NoCmdBold> command.
CALLTREAT_NOSIGNAL
%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 <CmdBold>show proc cpu<NoCmdBold> 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 <CmdBold>call threshold global cpu-5sec<NoCmdBold> 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 <CmdBold>call threshold poll-interval<NoCmdBold> 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 <CmdBold>show proc cpu<NoCmdBold> 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 <CmdBold>call threshold global cpu-avg<NoCmdBold> command.
%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 <CmdBold>show proc cpu<NoCmdBold> 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_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 <CmdBold>show mem<NoCmdBold> and <CmdBold>show proc mem<NoCmdBold> 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 <CmdBold>call threshold global io-mem<NoCmdBold> 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 <CmdBold>show mem<NoCmdBold> and <CmdBold>show proc mem<NoCmdBold> 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 <CmdBold>call threshold global total-mem<NoCmdBold> 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 <CmdBold>show mem<NoCmdBold> and <CmdBold>show proc mem<NoCmdBold> 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 <CmdBold>call threshold global proc-mem<NoCmdBold> 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 <CmdBold>call threshold global proc-mem<NoCmdBold> command.
CAPWAP_FRAG
%CAPWAP_FRAG-2-UNENABLED : [chars] feature not enabled at interface [chars], packet cannot be processed, MSGDEF_LIMIT_SLOW
Explanation Capwap Fragmentation feature as indicated not enabled by the control plane. This is a critical problem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CAPWAP_FRAG-3-CAPWAP_FRAG_DBG : Capwap Fragmentation encountered an error: [chars], [chars] [int], [chars] [int]
Explanation Capwap Fragmentation encountered a runtime error as indicated in the message with parameter data for debug
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CAPWAP_FRAG-3-CAPWAP_FRAG_ERR : Capwap Fragmentation encountered an error: [chars]
Explanation Capwap Fragmentation encountered a runtime error as indicated
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CAPWAP_FRAG-3-INIT_FAILED : Initialization of the CAPWAP_FRAG feature in QFP failed
Explanation Initialization of the CAPWAP_FRAG 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CAPWAP_FRAG-3-INVALID_QFP_NO : Invalid qfp device no.: [chars]
Explanation Invalid qfp device no.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
CAPWAP_REASS
%CAPWAP_REASS-2-UNENABLED : [chars] feature not enabled at interface [chars], packet cannot be processed, MSGDEF_LIMIT_SLOW
Explanation Capwap Reassembly feature as indicated not enabled by the control plane. This is a critical problem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CAPWAP_REASS-3-ALLOC_FAILED : Allocation of [chars] memory failed for CAPWAP_REASS feature in QFP
Explanation Allocation of memory by the QFP CAPWAP_REASS 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CAPWAP_REASS-3-CAPWAP_REASS_DBG : Capwap Reassembly encountered an error: [chars], [chars] [int], [chars] [int]
Explanation Capwap Reassembly encountered a runtime error as indicated in the message with parameter data for debug
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CAPWAP_REASS-3-CAPWAP_REASS_ERR : Capwap Reassembly encountered an error: [chars]
Explanation Capwap Reassembly encountered a runtime error as indicated
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CAPWAP_REASS-3-INIT_FAILED : Initialization of the CAPWAP_REASS feature in QFP failed
Explanation Initialization of the CAPWAP_REASS 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CAPWAP_REASS-3-INVALID_QFP_NO : Invalid qfp device no.: [chars]
Explanation Invalid qfp device no.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CAPWAP_REASS-3-MEM_INIT_FAILED :
Explanation Failure occurred initializing capwap reass memory pool.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CAPWAP_REASS-3-MEM_REQ_FAILED :
Explanation IPC Failure occurred when attempting to request more capwap reass pool memory.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
CAPWAP_REASS_PROXY
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
CASA
%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-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-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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
CBAC_C3PL
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show registry brief command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show memory command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show memory command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show memory command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
CBUS
%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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%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-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-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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%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-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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%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 <CmdBold>show tech-support<NoCmdBold> and <CmdBold>show logging<NoCmdBold> commands, contact your Cisco technical support representative, and provide the representative with the gathered information.
%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-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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or 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-CT3DSX3ERR : ([chars])Illegal dsx3 value -unit is [dec]
Explanation None
Recommended Action None
%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-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 <Bold>clear interface<NoBold> 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%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 <Bold>clear interface<NoBold> command. LOG_STD_RECUR_ACTION
%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-CTRRAMTEST : Interface [chars], RAM Addressing Test Failed -[chars]
Explanation The Token Ring interface failed its memory diagnostic tests.
Recommended Action Issue a <Bold>clear interface<NoBold> command. LOG_STD_RECUR_ACTION
%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 <Bold>clear interface<NoBold> 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 <Bold>clear interface<NoBold> command. LOG_STD_RECUR_ACTION
%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-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-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-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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%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 <CmdBold>show tech-support<NoCmdBold> and <CmdBold>show logging<NoCmdBold> commands, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or 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 <CmdBold>show tech-support<NoCmdBold> and <CmdBold>show logging<NoCmdBold> commands, 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-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-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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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-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-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
CCE_PI_PD
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show cce cpdp associations command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%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-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-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_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-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-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-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-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>)
%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-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>)
CCH323
%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-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-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-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-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-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_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_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_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-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-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-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-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-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_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-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-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-CCH323_UNKNOWN_EVENT : unknown event [hex]
Explanation Unknown CCH323 Event
Recommended Action No action is required
%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-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-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-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-OSS_INIT_FAILED : [chars]: OSS init failure: errno = [dec]
Explanation OSS ASN1 initialization failed
Recommended Action This can be catastrophic
%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-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-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.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CCH323-6-REGSTR : Gateway [chars] registered with Gatekeeper [chars]
Explanation Gateway registered with the Gatekeeper
Recommended Action no action is required
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_ADJ_IDX_FAILED : [hex]
Explanation Failed to get adjacency index from IPC packet.
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-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-4-PROXY_IPC_INVALID_MSG : [hex]
Explanation Received an invalid IPC messages subtype.
Recommended Action LOG_STD_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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
CEMA
%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-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-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
%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-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-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-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-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-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
CENT
%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
%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-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
CFT
%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-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-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_API
%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-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_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
%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_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-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-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
CFC_LISP
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CFC_LISP-3-DEPRECATED_API : Use of a deprecated API [chars][chars]
Explanation None
Recommended Action Increase the MTU of the path to the remote RLOC
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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-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 <CmdBold> ip lisp pmtu min NUMBER max NUMBER <NoCmdBold> 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 <CmdBold> ipv6 lisp pmtu min NUMBER max NUMBER <NoCmdBold> command to decrease the minimum MTU allowed and/or increase the maximum MTU that is allowed.
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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show process cpu command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
CLSDR
%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.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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-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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
CMANRP
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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-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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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.
%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-CMHASTATUS : RP switchover, [chars]
Explanation RP switchover events received by chassis manager.
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-6-CMSTATUS : Chassis Manager Process is [chars]
Explanation The current status of Chassis Manager Process.
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-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.
CMCC
%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/c/en/us/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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/c/en/us/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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/c/en/us/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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/c/en/us/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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/c/en/us/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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/c/en/us/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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/c/en/us/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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/c/en/us/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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/c/en/us/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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/c/en/us/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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-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/c/en/us/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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/c/en/us/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information
%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-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-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/c/en/us/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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/c/en/us/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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/c/en/us/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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-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_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-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/c/en/us/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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-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-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/c/en/us/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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/c/en/us/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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/c/en/us/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information
%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-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-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-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-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-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-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-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-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-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-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-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-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-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-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_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_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-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-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-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-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-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-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_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-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-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-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-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-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-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-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-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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%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-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_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
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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
CMFP
%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/c/en/us/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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-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-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-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-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-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-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-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/c/en/us/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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/c/en/us/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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-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-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-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-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-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
CMLIB
%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-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-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-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.
%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.
CMRP
%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-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-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_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_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-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_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_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-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-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-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-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-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-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-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-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-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-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-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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%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-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-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-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_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-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_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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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_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_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_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_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_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_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-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-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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%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_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_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_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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%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_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-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-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-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_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-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_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-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_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-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-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-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-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-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-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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%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-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-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-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-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-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-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_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-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-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-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-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-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-RP_RESET : RP is resetting : [chars]
Explanation This RP is resetting due to the reason specified.
Recommended Action No action is necessary.
%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-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-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-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-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_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-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-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-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-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-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-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-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-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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%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-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-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-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_SB_RELOAD_REQ : Reloading Standby FP: [chars]
Explanation A reload of Standby FP has been requested.
Recommended Action No action is necessary.
%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-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_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_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_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-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-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-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-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-RFROLE : RP switchover, [chars]
Explanation On RP switchover chasfs rfrole property has been changed.
Recommended Action No user action is necessary.
%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-6-RP_SWITCH_SB_SYNC : RP switchover: [chars]
Explanation The RP switch synchronization timer expired.
Recommended Action No user action is necessary.
%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-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-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-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-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_ENVMON
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
CMRP_PFU
%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-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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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 and not replaced.
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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%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-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-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-6-PFU_BEACON_LED_ON_OFF : [chars] beacon LED in slot PS[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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
COMP
%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-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-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-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.
%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-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_MATRIX
%COMP_MATRIX-3-PRST_VBL_DELETE : ISSU Compatibility Matrix was unable to delete a persistent variable from the [chars] system (rc = [dec]).
Explanation The ISSU compatibility matrix was unable to access a persistent variable. There is no way to determine if issu image-version compatibility checking should be enabled or disabled.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show persistent variable command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%COMP_MATRIX-3-PRST_VBL_GET : ISSU Compatibility Matrix was unable to read a persistent variable from the local system (rc = [dec]).
Explanation The ISSU compatibility matrix was unable to access a persistent variable. There is no way to determine if issu image-version compatibility checking should be enabled or disabled.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show persistent variable command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%COMP_MATRIX-3-PRST_VBL_WRITE : ISSU Compatibility Matrix was unable to write to persistent variables on the [chars] system (rc = [dec]).
Explanation The ISSU compatibility matrix was unable to access a persistent variable. There is no way to determine if issu image-version compatibility checking should be enabled or disabled.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show persistent variable command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%COMP_MATRIX-4-DISABLED : Compatibility Matrix has been disabled. No image compatibility checking will be done.
Explanation The ISSU compatibility matrix check has been disabled via configuration command <cmdBold>no service image-version compatibility<noCmdBold>. When the standby comes up, no image compatibility checking will be done, which results in SSO redundancy mode even if the active and standby are running different images.
Recommended Action The ISSU compatibility matrix check has been disabled using the global configuration command no service image-version compatibility. Redundancy mode would be SSO. Please be sure this is your intention or change configuration using service image-version compatibility.
COMMON_FIB
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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-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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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-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-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_MFIB
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
COMPILED_ACL
%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-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_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-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_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-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-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-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-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
%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-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-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
COND_DEBUG_HA
%COND_DEBUG_HA-2-INIT : COND_DEBUG ISSU client initialization failed to [chars]. Error: [dec] ([chars])
Explanation The COND_DEBUG 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%COND_DEBUG_HA-3-TRANSFORM : COND_DEBUG ISSU client [chars] transform failed for 'Message Type [dec]'. Error: [dec] ([chars])
Explanation The COND_DEBUG 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 COND_DEBUG 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>)
%COND_DEBUG_HA-2-GET_BUFFER : COND_DEBUG ISSU client failed to get buffer for message. Error: [dec] ([chars])
Explanation The COND_DEBUG HA client failed to get buffer space for building chkpt message. Message cannot be sent to standby device. If a problem occurs, the standby device cannot be brought up properly.
Recommended Action LOG_STD_SH_CMD_ACTION( show logging and show checkpoint client)
%COND_DEBUG_HA-2-SEND_NEGO_FAILED : COND_DEBUG ISSU client failed to send negotiation message. Error: [dec] ([chars])
Explanation The COND_DEBUG 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)
%COND_DEBUG_HA-2-SESSION_NEGO : COND_DEBUG ISSU client encountered unexpected client nego_done. Error: [dec] ([chars])
Explanation An ISSU-compliant client transitions through a series of internal states. The COND_DEBUG 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>)
%COND_DEBUG_HA-2-SESSION_REGISTRY : COND_DEBUG ISSU client failed to register session information. Error: [dec] ([chars])
Explanation The COND_DEBUG 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>)
%COND_DEBUG_HA-3-INVALID_SESSION : COND_DEBUG ISSU client does not have a valid registered session.
Explanation The COND_DEBUG 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>)
%COND_DEBUG_HA-3-MSG_SIZE : COND_DEBUG ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] ([chars])
Explanation The COND_DEBUG ISSU client failed to calculate the MTU for the specified message. The COND_DEBUG ISSU client will 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>)
%COND_DEBUG_HA-3-SESSION_UNREGISTRY : COND_DEBUG ISSU client failed to unregister session information. Error: [dec] ([chars])
Explanation The COND_DEBUG 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>)
CONF_SW
%CONF_SW-2-IPC_INIT : IPC message handler registration failure, rc [int]
Explanation Registering an IPC message handler for the CONF SW feature failed. This will cause the feature not to function. The function
Recommended Action This is normally a software issue. The consequences are that the CONF SW feature will not function. LOG_STD_ACTION
%CONF_SW-3-FEAT_DOWN : Invalid request [chars] while feature down, conf id [int]
Explanation While the feature was not active, an invalid request was received from another layer of the CONF_SW software stack for the specified conf ID. Some requests do not have an associated conf ID. For them the displayed conf ID is zero.
Recommended Action This is a software issue. The consequences could be limited to only one or a few confs. LOG_STD_RECUR_ACTION
%CONF_SW-3-FEAT_UP : Invalid request [chars] while feature up
Explanation While the feature was active, an invalid request was received from another layer of the CONF SW software stack.
Recommended Action This is a software issue. There are no consequences as this can only have been an Init request while the feature was already active. LOG_STD_RECUR_ACTION
%CONF_SW-3-IPC_NORES : No space for the IPC reply, size [int]
Explanation For a request from upper CONF SW 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 conf that cannot be established etc. In rare cases this could also affect other operations such as feature activation, deactivation, modification, High-Availability switchover operations.
Recommended Action This is normally a software issue. LOG_STD_RECUR_ACTION
%CONF_SW-3-IPC_OPEN_REPLY : IPC Open Reply failed, request [int]
Explanation For a request from upper CONF SW software stack layers it was not possible to open the reply buffer. The consequence of this could be a stuck conf that cannot be established etc. In rare cases this could also affect other operations such as feature activation, deactivation, modification, High-Availability switchover operations.
Recommended Action This is normally a software issue. LOG_STD_RECUR_ACTION
%CONF_SW-3-NO_RES : [chars] resource not available for the [chars] request, conf id [int]
Explanation The specified software resource was not available or could not be located for the specified request from upper CONF SW software stack layers for the specified conf ID.
Recommended Action This is a software issue. The consequences are that the specified request could not be performed. LOG_STD_RECUR_ACTION
CONST_ISSU
%CONST_ISSU-2-NEGO_NOT_DONE : [chars]([dec]): ISSU Negotiation not complete
Explanation Unable to complete ISSU negotiation.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CONST_ISSU-3-CAPENTRY_REG : [chars]([dec]): failed to register a capability entry ([chars])
Explanation The ISSU client failed to register a capability entry
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CONST_ISSU-3-CAP_EXCHANGE : [chars]([dec]): Capability exchange failed with error ([chars])
Explanation The capability exchange failed, the ISSU client is unable to process the received capability
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CONST_ISSU-3-CAPGROUP_REG : [chars]([dec]): failed to register a capability group ([chars])
Explanation The ISSU client failed to register a capability group
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CONST_ISSU-3-CAP_REG : [chars]([dec]): failed to register its capabilities ([chars])
Explanation The capabilities of the ISSU client could not be registered
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CONST_ISSU-3-CAPTYPE_REG : [chars]([dec]): failed to register capability type ([chars])
Explanation The ISSU client failed to register a capability type
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CONST_ISSU-3-CF_SEND : [chars]([dec]): Client failed to send message ([dec])
Explanation ISSU client cannot send a negotiation message to a peer
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CONST_ISSU-3-CLIENT_REG : [chars]([dec]): Client failed to register ([chars])
Explanation The ISSU Client could not be registered
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CONST_ISSU-3-CLIENT_REG_FAILED : [chars]([dec]): Client is not initialized
Explanation The ISSU Client is not yet initialized. The negotiation for this client is not yet done.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CONST_ISSU-3-CONST_MTU_NOT_ENOUGH : [chars]([dec]): Requested buffer size ([dec]) is greater than the max MTU size ([dec])
Explanation Checkpoint buffer size requested is greater than the max MTU size checkpoint supports
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CONST_ISSU-3-ENTITY_REG : [chars]([dec]): failed to register the entity ([chars])
Explanation The ISSU entity could not be registered
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CONST_ISSU-3-ENTITY_UNREG : [chars]([dec]): failed to unregister the entity ([chars])
Explanation The ISSU entity could not be unregistered
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CONST_ISSU-3-ICC_SEND : [chars]([dec]): Client failed to send message
Explanation ISSU client cannot send a negotiation message to a peer
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CONST_ISSU-3-MSGGROUP_REG : [chars]([dec]): failed to register a message group ([chars])
Explanation The ISSU client failed to register a message group
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CONST_ISSU-3-MSG_MTU : [chars]([dec]): Client failed to get mtu for message [dec] ([chars])
Explanation %s(%d): client cannot get the MTU for a message type
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CONST_ISSU-3-MSG_NOT_OK : [chars]([dec]): ISSU message type ([dec]) is not compatible
Explanation ISSU received a message not compatible with the running version.
Recommended Action LOG_STD_SH_CMD_ACTION( show message type <Client_ID>)
%CONST_ISSU-3-MSG_POLICY : [chars]([dec]): Client failed to negotiate version for message type ([dec]), error ([chars])
Explanation ISSU client cannot negotiate message to a peer
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CONST_ISSU-3-MSG_REG : [chars]([dec]): failed to register its messages ([chars])
Explanation Messages for the ISSU client could not be registered
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CONST_ISSU-3-MSGTYPE_REG : [chars]([dec]): failed to register a message type ([chars])
Explanation The ISSU client failed to register a message type
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CONST_ISSU-3-NEGO_PROCESS : [chars]([dec]): Cannot create process: [chars]
Explanation The process to negotiate the session for the specified ISSU client cannot be created.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CONST_ISSU-3-SESSION_REG : [chars]([dec]): session failed to register ([chars])
Explanation The client's ISSU session could not be registered
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CONST_ISSU-3-SESSION_UNREG : [chars]([dec]): session ([dec]) failed to unregister ([chars])
Explanation The client's ISSU session could not be unregistered
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CONST_ISSU-3-START_NEGO_FAILED : [chars]([dec]): failed to start negotiation ([chars])
Explanation The ISSU client cannot start its negotiation
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CONST_ISSU-3-TRANSFORM_FAILED : [chars]([dec]): [chars] transformation failed ([chars])
Explanation The transformation operation for the ISSU message has failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
CONTROLLER
%CONTROLLER-4-ACR_DCR_CLOCK_DS1 : [chars]: [chars] Clock status is [chars] for clock_id [dec] on circuit: [int] ([chars])
Explanation DS1 Recovered clock status change message
Recommended Action No action is required.
%CONTROLLER-4-ACR_DCR_CLOCK_DS3 : [chars]: [chars] Clock status is [chars] for clock_id [dec] on circuit: [int] ([chars])
Explanation DS3 Recovered clock status change message
Recommended Action No action is required.
%CONTROLLER-4-ACR_DCR_CLOCK_DS3_CHANNEL : [chars]: [chars] Clock status is [chars] for clock_id [dec] on circuit: [int]/[int] ([chars])
Explanation DS3:channelized Recovered clock status change message
Recommended Action No action is required.
%CONTROLLER-4-ACR_DCR_CLOCK_OCN_CT3 : [chars]: [chars] Clock status is [chars] for clock_id [dec] on circuit: [int]/[int]/[int] ([chars])
Explanation OCN_CT3: Recovered clock status change message
Recommended Action No action is required.
%CONTROLLER-4-ACR_DCR_CLOCK_OCN_T3 : [chars]: [chars] Clock status is [chars] for clock_id [dec] on circuit: [int]/[int] ([chars])
Explanation OCN_T3: Recovered clock status change message
Recommended Action No action is required.
%CONTROLLER-4-ACR_DCR_CLOCK_OCN_VT_T1 : [chars]: [chars] Clock status is [chars] for clock_id [dec] on circuit: [int]/[int]/[int]/[int] ([chars])
Explanation OCN_VT_T1: Recovered clock status change message
Recommended Action No action is required.
%CONTROLLER-4-ACR_DCR_CLOCK_STMN_CT3 : [chars]: [chars] Clock status is [chars] for clock_id [dec] on circuit: [int]/[int]/[int]/[int] ([chars])
Explanation STMN_CT3: Recovered clock status change message
Recommended Action No action is required.
%CONTROLLER-4-ACR_DCR_CLOCK_STMN_E3 : [chars]: [chars] Clock status is [chars] for clock_id [dec] on circuit: [int]/[int]/[int] ([chars])
Explanation STMN_E3: Recovered clock status change message
Recommended Action No action is required.
%CONTROLLER-4-ACR_DCR_CLOCK_STMN_T3 : [chars]: [chars] Clock status is [chars] for clock_id [dec] on circuit: [int]/[int]/[int] ([chars])
Explanation STMN_T3: Recovered clock status change message
Recommended Action No action is required.
%CONTROLLER-4-ACR_DCR_CLOCK_STMN_VC1x : [chars]: [chars] Clock status is [chars] for clock_id [dec] on circuit: [int]/[int]/[int]/[int] ([chars])
Explanation STMN_VC1x: Recovered clock status change message
Recommended Action No action is required.
%CONTROLLER-2-CDB_NULL : cdb is NULL
Explanation A NULL pointer is detected
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%CONTROLLER-2-CRASHED : Interface Processor in slot [dec] not responding ([hex]): shutting it down
Explanation A controller stopped responding to commands over the cBus, so it was put into shutdown mode.
Recommended Action Re-enable the controllers by issuing the no shut configuration command on all controllers on the card, or hotswap out the bad card and install the new one. You must still manually <CmdBold>no shut the controllers.
%CONTROLLER-2-DSX_NULL : dsx pointer is NULL
Explanation A NULL pointer is detected
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%CONTROLLER-2-FIRMWARE : Controller [chars], [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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%CONTROLLER-2-NOTFOUND : For controller [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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%CONTROLLER-5-CALLDROP : Controller [chars], [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.
%CONTROLLER-5-CLOCKSTATE : Controller [chars], [chars]
Explanation A configurable controller clock changed its state.
Recommended Action No action is required.
%CONTROLLER-5-DOWNDETAIL : Controller [chars], changed state to [chars] due to [chars]
Explanation A configurable controller changed its state.
Recommended Action No action is required.
%CONTROLLER-5-HDLC_INSUFF_RESOURCE : Insufficient HDLC resources to enable channel [dec]
Explanation Limited number of HDLC channels can be allocated for this trunk
Recommended Action Please check the number of HDLC resources supported for this trunk card. Please contact your technical support representative.
%CONTROLLER-5-LOOPSTATUS : Controller [chars], [chars]
Explanation A configurable controller loopback status.
Recommended Action No action is required.
%CONTROLLER-5-REMLOCALLOOP : Controller [chars], local loop [chars] [chars]
Explanation A configurable controller entered local loopback.
Recommended Action No action is required.
%CONTROLLER-5-REMLOOP : Controller [chars], remote loop [chars] [chars]
Explanation A configurable controller entered remote loopback.
Recommended Action No action is required.
%CONTROLLER-5-UPDOWN : Controller [chars], changed state to [chars]
Explanation A configurable controller changed its state.
Recommended Action No action is required.
CPP_LDN
%CPP_LDN-2-PROXY_IPC_INIT_FAILED : CPP LDN Proxy IPC interface initialization failure (result: [dec]).
Explanation Cisco internal software error. CPP LDN initialization detected that the Proxy IPC interface initialization failed. The LDN 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CPP_LDN-3-PROXY_GPM_RSRC_FAIL : failure: [chars]
Explanation LDN Proxy failed in performing a GPM operation.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CPP_LDN-3-PROXY_IPC_INVALID : failure: [dec]
Explanation LDN Proxy received an invalid IPC msg from the client.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CPP_LDN-3-PROXY_IPC_SEND : failure: [chars]
Explanation LDN Proxy send response failed, response was dropped.
Recommended Action LOG_STD_ACTION
CPP_BQS
%CPP_BQS-2-MPASS_FS_REG : CPP BQS PROXY feature special vector [dec] registration failed (result: [dec])
Explanation Cisco internal software error. CPP multipass registration of a feature special processing vector for BQS Proxy failed. The BQS proxy will not be fully functional while this condition exists.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CPP_BQS-2-PROXY_IPC_INIT_FAILED : CPP BQS Proxy IPC interface initialization failure (result: [dec]).
Explanation Cisco internal software error. CPP BQS initialization detected that the Proxy IPC interface initialization failed. The BQS 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CPP_BQS-3-CARVE : [chars]: size [int] SW carved out memory region initialization failed.
Explanation A BQS proxy failed to initialize the software memory region.
Recommended Action LOG_STD_ACTION
%CPP_BQS-3-CMD_ACTIVE : CPP BQS Proxy Command, correlator [int]
Explanation A BQS Proxy command was received, but the correlator was still in use. Commad was not processed.
Recommended Action LOG_STD_ACTION
%CPP_BQS-3-INIT_FAILED : CPP BQS RM Proxy, region [chars]
Explanation BQS proxy failed due initialize or resize software managed memory.
Recommended Action LOG_STD_ACTION
%CPP_BQS-3-INVALID_SUBTYPE : CPP BQS RM Proxy subtype [int]
Explanation BQS proxy failed because of receiving invalid sub-type or failed to allocate ipc response buffer.
Recommended Action LOG_STD_ACTION
%CPP_BQS-3-MAX_GPM_TX_LEN_EXCEED : CPP BQS Proxy Command, exceed GPM tx len [int]
Explanation A BQS Proxy command recycle a packet exceed GPM tx len
Recommended Action LOG_STD_ACTION
%CPP_BQS-3-PROXY_IPC_SEND : failure: [chars]
Explanation BQS Proxy send response failed, response was dropped.
Recommended Action LOG_STD_ACTION
%CPP_BQS-3-RESIZE : CPP BQS Proxy Memory Manager, region [chars]
Explanation BQS proxy failed to resize software managed memory.
Recommended Action LOG_STD_ACTION
CPP_BQS_QMOVE
%CPP_BQS_QMOVE-3-PROXY_COMPLETE : Proxy Operation: [chars]
Explanation Operation that was flagged as timed out, has now completed
Recommended Action LOG_STD_ACTION
%CPP_BQS_QMOVE-3-PROXY_ERROR : Proxy Operation Failed: [chars]
Explanation BQS Proxy operation failed.
Recommended Action LOG_STD_ACTION
%CPP_BQS_QMOVE-3-PROXY_TIMEOUT : Proxy Operation: [chars] node_id [hex] data [hex] data [hex]
Explanation BQS Proxy operation timeout. Proxy will continue to retry operatin.
Recommended Action LOG_STD_ACTION
CPPDRV
%CPPDRV-2-HALT : [chars]([dec]) Interrupt : [chars] Seq:%03d Halt bit set.
Explanation A Serious CPP hardware error has occurred.
Recommended Action No action is required.
%CPPDRV-3-ALLOC_NOTF : CPP[dec]: Failed to Allocate: ([chars])
Explanation A function failed to allocate data.
Recommended Action No action is required.
%CPPDRV-3-CLEANUP_NOTF : Failed to Cleanup: ([chars])
Explanation A function failed to cleanup data.
Recommended Action No action is required.
%CPPDRV-3-DESTROY_NOTF : Failed to destroy connection :([chars])
Explanation A function failed to destroy a connection.
Recommended Action No action is required.
%CPPDRV-3-FATAL_ACQUIRE_LOCK : CPP[dec]: ([hex]) Failed to acquire memory lock [chars]
Explanation SW failed to acquire shared memory lock
Recommended Action No action is required.
%CPPDRV-3-FATAL_ALLOCATE : CPP[dec]: ([hex]) Failed to allocate [chars] -[chars]
Explanation Failed to allocate data
Recommended Action No action is required.
%CPPDRV-3-FATAL_ATTACH : CPP[dec]: ([hex]) FAILED: to attach [chars]
Explanation Device Failed to attach
Recommended Action No action is required.
%CPPDRV-3-FATAL_CPP_SUBDEV_ACCESS : CPP[dec].[dec]: An access error has been reported. Error count [int].
Explanation The system has reported an error while accessing a CPP subdevice
Recommended Action No action is required.
%CPPDRV-3-FATAL_CPU_FEATURE : CPP[dec]: CPU lacks feature ([chars]). Packet forwarding disabled.
Explanation The currently installed CPU lacks a certain feature that is required by the forwarding engine. The QFP is operating with reduced functionality with packet forwarding disabled.
Recommended Action No action is required.
%CPPDRV-3-FATAL_CREATE : ([hex]) Failed to create [chars] -[chars]
Explanation Failed to create device
Recommended Action No action is required.
%CPPDRV-3-FATAL_CREATE_ID : CPP[dec]: ([hex]) Failed to create [chars] -[chars]
Explanation Failed to create device
Recommended Action No action is required.
%CPPDRV-3-FATAL_GET_DETAILS : CPP[dec]: ([hex]) Failed to get [chars] details -[chars]
Explanation Failed to get device details
Recommended Action No action is required.
%CPPDRV-3-FATAL_INIT : ([hex]) Failed to initialize [chars] -[chars]
Explanation Failed to init device
Recommended Action No action is required.
%CPPDRV-3-FATAL_INIT_ID : CPP[dec]: ([hex]) Failed to initialize [chars] -[chars]
Explanation Failed to init device
Recommended Action No action is required.
%CPPDRV-3-FATAL_INTERNAL : CPP[dec]: ([hex]) Internal Error [chars]
Explanation Internal coding error.
Recommended Action No action is required.
%CPPDRV-3-FATAL_INTERRUPT_CLEAR : CPP[dec]: ([hex]) Failed to clear [chars] interrupt
Explanation Failed to clear an interrupt node
Recommended Action No action is required.
%CPPDRV-3-FATAL_INTERRUPT_HANDLER : CPP[dec]: ([hex]) Failed to register [chars] interrupt handler -[chars]
Explanation Failed to register interrupt handler
Recommended Action No action is required.
%CPPDRV-3-FATAL_INTERRUPT_INIT : CPP[dec]: ([hex]) Failed to initialize [chars] interrupt -[chars]
Explanation Failed to initialize an interrupt
Recommended Action No action is required.
%CPPDRV-3-FATAL_INTERRUPT_OPEN : CPP[dec]: ([hex]) Failed to access [chars] interrupt node -[chars]
Explanation Failed to open an interrupt
Recommended Action No action is required.
%CPPDRV-3-FATAL_MEM_CLEAR : CPP[dec]: ([hex]) Failed to clear memory [chars]
Explanation SW failed to clear memory location
Recommended Action No action is required.
%CPPDRV-3-FATAL_MEM_SIZE : CPP[dec]: ([hex]) Failed to acquire memory size [chars]
Explanation SW failed to acquire the size of a block of memory
Recommended Action No action is required.
%CPPDRV-3-FATAL_MEM_WRITE : CPP[dec]: ([hex]) Failed to write to memory [chars]
Explanation SW failed to write to a memory location
Recommended Action No action is required.
%CPPDRV-3-FATAL_MIN_CPU : CPP[dec]: Insufficent number of CPUs (detected = [dec], required = [dec])
Explanation The current system lacks a sufficent number of CPUs (or cores) to operate.
Recommended Action No action is required.
%CPPDRV-3-FATAL_PLAT_DB : CPP[dec]: ([hex]) Platform failure accessing [chars]
Explanation Platform DB query failed
Recommended Action No action is required.
%CPPDRV-3-FATAL_RELEASE_LOCK : CPP[dec]: ([hex]) Failed to release memory lock [chars]
Explanation SW failed to release shared memory lock
Recommended Action No action is required.
%CPPDRV-3-FATAL_UNSUPPORT : CPP[dec]: ([hex]) -unsupported CPP TYPE. CPP TYPE:[dec]
Explanation Unsupported CPP TYPE
Recommended Action No action is required.
%CPPDRV-3-GUEST_CPU_FEATURE : CPP[dec]: Guest CPU lacks feature ([chars]).
Explanation The currently installed Guest CPU lacks a certain feature that is required by the forwarding engine, but that feature is supported by the Host CPU. The QFP is operating with normal functionality using the host CPU feature, but live migration to a host which lacks this feature will result in a crash.
Recommended Action No action is required.
%CPPDRV-3-HOT : [chars]([dec]) Interrupt : [chars] Seq:%03d repeating interrupt has been disabled.
Explanation A repeating hardware interrupt has been disabled.
Recommended Action No action is required.
%CPPDRV-3-INIT_NOTF : Failed to initialize: ([chars])
Explanation A function failed to initialize.
Recommended Action No action is required.
%CPPDRV-3-INIT_NOTF_ID : CPP[dec]: Failed to initialize: ([chars])
Explanation A function failed to initialize.
Recommended Action No action is required.
%CPPDRV-3-LOCKDOWN : QFP[int].[int] CPP Driver LOCKDOWN encountered due to previous fatal error ([chars]: [chars]).
Explanation A fatal error has caused the driver to LOCKDOWN.
Recommended Action No action is required.
%CPPDRV-3-LOCKDOWN_INITIATED : QFP[int].[int] CPP Driver LOCKDOWN being triggered due to fatal error.
Explanation A fatal error has caused the process to initiate LOCKDOWN.
Recommended Action No action is required.
%CPPDRV-3-SRT_PERR_FAILURE : [chars]([dec]) Failed to correct BQS SRT Parity error.
Explanation Failed to correct a BQS SRT Parity error.
Recommended Action No action is required.
%CPPDRV-3-TCAM_PERR : [chars]([dec]) TCAM Parity error TCAM device #[dec] at offset [hex].
Explanation A Parity error has occurred in a TCAM device.
Recommended Action No action is required.
%CPPDRV-3-TCAM_PERR_FAILURE : [chars]([dec]) Failed to correct TCAM Parity error. Parity error detection disabled.
Explanation Failed to correct a TCAM Parity error and further detection has been disabled.
Recommended Action No action is required.
%CPPDRV-4-ADRSPC_LIMIT : Address space limit [int] KB reached, mapping block [chars] size [int] dynamically, over limit space: [int] KB
Explanation The process indicated tried to map more of the Forwarding Engine's address space than was allocated for it. A slower access method will be used instead. This will lower the performance of some operations which require accesses to the Forwarding Engine
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%CPPDRV-4-CORE_TABLE : CPP[dec] specific core dump table '[chars]' not found, using minimal fallback table '[chars]' instead
Explanation The QFP configuration found on this board did not match any of the tables which define which data has to be collected if a fatal error is detected. Instead a minimal table is used which covers most of the QFP registers. The QFP is fully operational.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%CPPDRV-4-CPU_FEATURE : CPP[dec]: CPU lacks feature ([chars]). Performance may be sub-optimal.
Explanation The currently installed CPU lacks a certain feature that improve performance of the forwarding engine. The QFP is fully operational, but may operate at a reduced capacity.
Recommended Action No action is required.
%CPPDRV-4-HW_REV_OLD : Found HW revision [chars], using [chars] based on [chars]. No customer deployment.
Explanation The specified board or chip showed an incorrect, invalid or too old hardware revision. That hardware revision was (possibly) overridden to a different value based on some other data available at the time. For instance, the QFP hardware revision might be unprogrammed, so the correct revision was derived from the board type and revision or the QFP's die ID. Boards showing this warning should not be deployed at customer sites.
Recommended Action No action is required.
%CPPDRV-6-ACCTRC16B : Access CPP [dec] address 0x%08llX (Blk/Off:[chars]/0x%08llX) [chars] %3d bytes 0x%016llX_%016llX flags [hex]
Explanation A CPP access was traced
Recommended Action No action is required.
%CPPDRV-6-ACCTRC8B : Access CPP [dec] address 0x%08llX (Blk/Off:[chars]/0x%08llX) [chars] %3d bytes 0x%016llX flags [hex]
Explanation A CPP access was traced
Recommended Action No action is required.
%CPPDRV-6-INTR : [chars]([dec]) Interrupt : [chars]
Explanation A CPP hardware interrupt has occurred.
Recommended Action No action is required.
CPP_FM
%CPP_FM-3-CPP_FM_CLIENT_WARNING : Client Is Invalid: [chars]
Explanation None
Recommended Action None
%CPP_FM-3-CPP_FM_TCAM_WARNING : TCAM limit exceeded: [chars]
Explanation None
Recommended Action None
%CPP_FM-4-CPP_FM_FIELD_IGNORED : Matching on field type [int] ([chars] value [int] ([hex])) not supported for client [chars] ([int]), rule oid: [chars], seqnos: [int], [int], [int]: RULE *IGNORED*
Explanation User is trying to use a classification criterion not supported by the feature. For example, user is trying to apply a with a class matching matched on an IPv6 ACL that contains a match on flow-label. The entire rule (e.g. ACE) containing the unsupported criterion is ignored. In our example, only the ACEs containing match on flow label are ignored. All other ACEs are still downloaded to CPP.
Recommended Action No action is required.
CPP_FR
%CPP_FR-2-BQS_SCRATCH_TOOSMALL : QFP BQS Scratch area too small for Frame Relay MFR feature usage (size: [dec], need: [dec]).
Explanation Cisco internal software error. QFP Frame Relay MFR initialization detected that the BQS scratch memory area is insufficient for Frame Relay MFR usage. The Frame Relay MFR Bundle interfaces 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CPP_FR-2-PROXY_IPC_INIT_FAILED : Frame Relay Proxy IPC interface initialization failure (result: [dec]).
Explanation Cisco internal software error. FR initialization detected that the Proxy IPC interface initialization failed. The FR interfaces may not function properly while this condition exists.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CPP_FR-3-INV_PROXY_MSG : CPP FR Proxy received invalid IPC message ID [dec]
Explanation Cisco internal software error. CPP FR Proxy received an invalid message ID. This message will be ignored.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CPP_FR-3-MFR_INVALID_RX_DLCI : Frame Relay MFR DLCI ([dec]) received from the peer must be configured for interface [chars] (Peer error), MSGDEF_LIMIT_SLOW
Explanation Possible error on the peer device with Multilink FR. Received Multilink FR packet contained wrond DLCI number.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CPP_FR-3-PROXY_DUP_DLCI_ID : QFP Frame Relay MFR Proxy ([chars] [chars]) duplicate DLCI [dec] for interface [chars] and [chars]
Explanation Cisco internal software error. QFP Frame Relay MFR Proxy message DLCI Add could not be processed for the indicated interface due use of a given DLCI on multiple member links within the same Frame Relay MFR Bundle. The associated Frame Relay MFR Bundle interface may not be fully functional as a result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CPP_FR-3-PROXY_DUP_LINK_ID : QFP Frame Relay MFR Proxy ([chars] [chars]) duplicate Link ID [dec] for interface [chars] and [chars]
Explanation Cisco internal software error. QFP Frame Relay MFR Proxy message Link Add could not be processed for the indicated interface due use of a given Link ID on multiple member links within the same Frame Relay MFR Bundle. The associated Frame Relay MFR Bundle interface may not be fully functional as a result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CPP_FR-3-PROXY_INV_BUFFER_LIMIT : QFP Frame Relay MFR Proxy ([chars] [chars]) indicated an invalid Rx buffer limit ([dec]) for interface [chars]
Explanation Cisco internal software error. QFP Frame Relay MFR was provided a invalid Rx buffer limit value. The associated Frame Relay MFR Bundle interface may not be fully functional as a result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CPP_FR-3-PROXY_INV_BUNDLE_STATE : QFP Frame Relay MFR Proxy ([chars] [chars]) invalid Bundle state [chars] ([dec]) for interface [chars]
Explanation Cisco internal software error. QFP Frame Relay MFR Proxy message could not be processed due to the Frame Relay MFR Bundle being in an incorrect state to accept the message. The associated Frame Relay MFR Bundle interface may not be fully functional as a result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CPP_FR-3-PROXY_INV_DLCI_INFO : QFP Frame Relay MFR Proxy ([chars] [chars]) invalid PVC Info (Base: [hex], Num: [dec]) for interface [chars]
Explanation Cisco internal software error. QFP Frame Relay MFR Proxy message contained invalid Frame Relay MFR PVC information. The associated Frame Relay MFR Bundle interface may not be fully functional as a result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CPP_FR-3-PROXY_INV_LINK_ID : QFP Frame Relay MFR Proxy ([chars] [chars]) invalid Link ID [dec] for interface [chars]
Explanation Cisco internal software error. QFP Frame Relay MFR Proxy message Link Add could not be processed for the indicated interface due to an invalid Link ID. The associated Frame Relay MFR Bundle interface may not be fully functional as a result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CPP_FR-3-PROXY_INV_LINK_STATE : QFP Frame Relay MFR Proxy ([chars] [chars]) invalid Link state [chars] ([dec]) for interface [chars]
Explanation Cisco internal software error. QFP Frame Relay MFR Proxy message could not be processed due to the Frame Relay MFR Link being in an incorrect state to accept the message. The associated Frame Relay MFR Bundle interface may not be fully functional as a result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CPP_FR-3-PROXY_INV_LOST_SEQ_TO : QFP Frame Relay MFR Proxy ([chars] [chars]) indicated an invalid lost sequence timeout ([dec]) for interface [chars]
Explanation Cisco internal software error. QFP Frame Relay MFR was provided a invalid lost sequence timeout value. The associated Frame Relay MFR Bundle interface may not be fully functional as a result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CPP_FR-3-PROXY_INV_RX_TX_INTF_VALUE : QFP Frame Relay MFR Proxy ([chars] [chars]) invalid Rx/Tx interface value [dec] for interface [dec] (handle)
Explanation Cisco internal software error. QFP Frame Relay MFR Proxy was unable to complete the requested Frame Relay MFR Bundle state change or configuration update due to an invalid interface Rx/Tx designation in the proxy request. The associated Frame Relay MFR Bundle interface may not be fully functional as a result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CPP_FR-3-PROXY_INV_SUB_DEV_ID : QFP Frame Relay MFR Proxy ([chars] [chars]) invalid Sub-Device ID [dec] for interface [chars]
Explanation Cisco internal software error. QFP Frame Relay MFR Proxy message Bundle Add could not be processed for the indicated interface due to an invalid Sub-Device ID. The associated Frame Relay MFR Bundle interface may not be fully functional as a result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CPP_FR-3-PROXY_INV_TX_LINK_WEIGHT : QFP Frame Relay MFR Proxy ([chars] [chars]) indicated an invalid Tx Link weight ([dec]) for interface [chars]
Explanation Cisco internal software error. QFP Frame Relay MFR Proxy message contained invalid Tx Link weight information. The associated Frame Relay MFR Member Link and/or Bundle interface may not be fully functional as a result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CPP_FR-3-PROXY_IPC_ALLOC_FAIL : CPP Frame Relay Proxy response to msg id [int] lost due to buffer allocation failure
Explanation Cisco internal software error. CPP Frame Relay Proxy message processing detected a IPC buffer allocation failure during response processing.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CPP_FR-3-PROXY_NULL_BUNDLE : QFP Frame Relay MFR Proxy ([chars] [chars]) NULL Bundle sub-block for interface [dec] (handle)
Explanation Cisco internal software error. QFP Frame Relay MFR Proxy was unable to complete the requested Frame Relay MFR Bundle state change or configuration update due to an invalid or uninitialized Bundle sub-block. The associated Frame Relay MFR Bundle interface may not be fully functional as a result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CPP_FR-3-PROXY_NULL_DLCI : QFP Frame Relay MFR Proxy ([chars] [chars]) NULL PVC sub-block for interface [dec] (handle)
Explanation Cisco internal software error. QFP Frame Relay MFR Proxy was unable to complete the requested Frame Relay MFR Member PVC state change or configuration update due to an invalid or uninitialized PVC sub-block. The associated Frame Relay MFR PVC interface may not be fully functional as a result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CPP_FR-3-PROXY_NULL_LINK : QFP Frame Relay MFR Proxy ([chars] [chars]) NULL Member Link sub-block for interface [dec] (handle)
Explanation Cisco internal software error. QFP Frame Relay MFR Proxy was unable to complete the requested Frame Relay MFR Member Link state change or configuration update due to an invalid or uninitialized Member Link sub-block. The associated Frame Relay MFR Member Link interface may not be fully functional as a result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CPP_FR-3-PROXY_SID_UPDATE_COMPLETE_ERROR : QFP Frame Relay MFR Proxy ([chars]) SID Update Complete w/o Preceeding Lock (Interface [chars], SID: [hex])
Explanation Cisco internal software error. QFP Frame Relay MFR Proxy message processing detected a Bundle Schedule SID update sequence error. One or more interface schedules could have been affected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CPP_FR-3-PROXY_SID_UPDATE_LOCK_ERROR : QFP Frame Relay Proxy ([chars]) Multiple SID Update Locks to same interface (Interface [chars], SID: [hex])
Explanation Cisco internal software error. QFP Frame Relay MFR Proxy message processing detected a Bundle Schedule SID update sequence error. One or more interface schedules could have been affected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CPP_FR-4-PROXY_IPC_ALLOC_FAIL2 : QFP Frame Relay MFR Proxy ([chars]) response lost due to buffer allocation failure (Interface [chars])
Explanation Cisco internal software error. QFP Frame Relay MFR Proxy message processing detected a IPC buffer allocation failure during proxy response processing. The associated Frame Relay MFR functionality may not be fully functional as a result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CPP_FR-4-PROXY_SYNC : QFP Frame Relay MFR Proxy ([chars] [chars]) Bundle/Link sync issue with interface [chars]
Explanation Cisco internal software error. QFP Frame Relay MFR Proxy message processing detected a Bundle-Link state synchronization abnormality. This condition should be cosmetic. Full context of the message will aid in problem isolation.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CPP_FR-4-TX_BUNDLE_FLOWED_OFF : QFP Frame Relay MFR Tx Bundle [chars] flowed off for an abnormal duration due to one or more congested member link(s)
Explanation Possible Cisco internal software or hardware error. QFP Frame Relay MFR Tx processing detected that a Frame Relay MFR Bundle interface was flowed off for an extended period of time due to a congested member link queue. The associated Frame Relay MFR Bundle interface may not be fully functional as a result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
CPPFPM
%CPPFPM-6-FMANACLLOGMISSMSG : access-list logging datapath rate-limited or missed [int] packet[chars]
Explanation Some packet matching logs were missed because the access list log messages were rate-limited or no access list log buffers were available.
Recommended Action No action is required.
%CPPFPM-6-IPACCESSLOGDP : list [chars] [chars] [chars] [chars] [chars]-> [chars] ([int]/[int]), [int] packet[chars]
Explanation A packet matching the log criteria for the given access list was detected.
Recommended Action No action is required.
%CPPFPM-6-IPACCESSLOGNP : list [chars] [chars] [int] [chars] [chars]-> [chars], [int] packet[chars]
Explanation A packet matching the log criteria for the given access list was detected.
Recommended Action No action is required.
%CPPFPM-6-IPACCESSLOGP : list [chars] [chars] [chars] [chars]([int]) [chars]-> [chars]([int]), [int] packet[chars]
Explanation A packet matching the log criteria for the given access list was detected.
Recommended Action No action is required.
CPP_IPHC_PROXY
%CPP_IPHC_PROXY-3-INVALID_IPC_INPUT : [chars] CPP IPHC Client Proxy failure
Explanation IPHC proxy failed because of receiving invalid sub-type or failed to allocate ipc response buffer.
Recommended Action LOG_STD_ACTION
CPPOSLIB
%CPPOSLIB-3-CLEAN_NOTIFY : Failed to cleanup: ([chars])
Explanation A function failed to cleanup data.
Recommended Action No action is required.
%CPPOSLIB-3-ERROR_NOTIFY : [chars] encountered an error
Explanation Print error message to console
Recommended Action No action is required.
%CPPOSLIB-3-GET_NOTIFY : Failed to get data: ([chars])
Explanation A function failed to get data.
Recommended Action No action is required.
%CPPOSLIB-3-INIT_NOTIFY : Failed to initialize: ([chars])
Explanation A function failed to initialize.
Recommended Action No action is required.
%CPPOSLIB-3-REGISTER_NOTIFY : Failed to register: ([chars])
Explanation A function failed to register.
Recommended Action No action is required.
CPPTCAMRM
%CPPTCAMRM-6-HIGH_WATER_MARK : TCAM resources in the system is limited.
Explanation The TCAM device has limited number of free cells left to allocate.
Recommended Action No action is required.
%CPPTCAMRM-6-LOW_WATER_MARK : There is sufficient TCAM resources in the system.
Explanation The TCAM device has sufficient number of free cells left.
Recommended Action No action is required.
%CPPTCAMRM-6-TCAM_RSRC_ERR : Allocation failed because of insufficient TCAM resources in the system.
Explanation The TCAM device has no free cells to accomodate the current allocation request.
Recommended Action No action is required.
CPPUI
%CPPUI-3-ERROR_NOTIFY : [chars]
Explanation An UI fault has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
CRASH_DUMP
%CRASH_DUMP-3-FILE_OP : FILE operation [chars] failed CRASH DUMP May not be successfull
Explanation The File operation for dumping DSP crash details failed The error message could be a software issue or due to not enough disk space.
Recommended Action No action is required.
%CRASH_DUMP-6-ABORT : CRASH DUMP aborted for device [dec]
Explanation Crash dump aborted. Crash Dump may not be successfull
Recommended Action No action is required.
%CRASH_DUMP-6-TIMEOUT : CRASH DUMP may not be successfull for the device [dec]
Explanation Crash dump process timed out waiting for diaganostic messages
Recommended Action No action is required.
CSVERIFY
%CSVERIFY-3-CSVERIFY_FAIL : Signature verification: [[chars]]
Explanation During digital signature verification, an error has occured
Recommended Action Check the diagnostic csverify trace file for more information on the underlying failure.
%CSVERIFY-6-CSVERIFY_SUCCESS : Signature verification success for [chars]
Explanation Signature verification was successful for the file mentioned.
Recommended Action This is an informational message. No action is required.
CRYPTO_DEV_PROXY
%CRYPTO_DEV_PROXY-2-PROXY_IPC_INIT_FAILED : QFP Crypto device Proxy IPC interface initialization failure (result: [dec]).
Explanation Cisco internal software error. QFP Crypto device Proxy initialization detected that the IPC interface initialization failed. QFP Crypto device 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CRYPTO_DEV_PROXY-2-PROXY_REG_NULL_MSG_HNDLR : QFP Crypto device Proxy registered invalid message handlers (source: [chars]).
Explanation Cisco internal software error. QFP Crypto device Proxy registered with invalid message handler. QFP Crypto device 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CRYPTO_DEV_PROXY-3-PROXY_BAD_MSG : QFP Crypto device Proxy received bad length message type [dec]
Explanation Cisco internal software error. QFP Crypto device 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CRYPTO_DEV_PROXY-3-PROXY_INV_MSG : QFP Crypto device Proxy received invalid message type [dec]
Explanation Cisco internal software error. QFP Crypto device 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CRYPTO_DEV_PROXY-3-PROXY_IPC_ALLOC_FAILED : QFP Crypto device Proxy [chars] message lost due to message buffer allocation failure.
Explanation Cisco internal software error. QFP Crypto device 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CRYPTO_DEV_PROXY-3-PROXY_IPC_SEND_FAILED : QFP Crypto device Proxy [chars] message lost due to message sent failure (result: [dec]).
Explanation Cisco internal software error. QFP Crypto device 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
CRYPTO_RSA_ISSU
%CRYPTO_RSA_ISSU-3-GET_BUFFER : Crypto RSA ISSU client failed to get buffer for message. Error: [dec] ([chars])
Explanation Crypto RSA ISSU client failed to get buffer for building a negotiation message. Hence, it cannot send the negotiation message to the standby unit. When there is a problem in the negotiaiton the standby unit can not be brought up.
Recommended Action LOG_STD_SH_CMD_ACTION( show logging and show checkpoint client)
%CRYPTO_RSA_ISSU-3-INIT : Crypto RSA ISSU client initialization failed to [chars]. Error: [dec] ([chars])
Explanation Crypto RSA ISSU client could not be initiailzed, this will cause catstrophic failure when ISSU upgrade or downgrade is performed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%CRYPTO_RSA_ISSU-3-INVALID_SESSION : Crypto RSA ISSU client does not have a valid registered session.
Explanation Crypto RSA ISSU client does not have a valid registered session. When there is a problem with the session the standby unit cannot be brought up.
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>)
%CRYPTO_RSA_ISSU-3-MSG_NOT_OK : Crypto RSA ISSU client message type [dec] is not compatible
Explanation Crypto RSA ISSU client received an incompatible message from the peer unit. Since the message is not compatible it cannot be processed by this unit
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>)
%CRYPTO_RSA_ISSU-3-MSG_SIZE : Crypto RSA ISSU client failed to get the MTU for message type [dec]. Error: [dec] ([chars])
Explanation Crypto RSA ISSU client failed to calculate MTU for the message specified. The dot1x ISSU client will not be able to send message to the standby unit.
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>)
%CRYPTO_RSA_ISSU-3-SEND_NEGO_FAILED : Crypto RSA ISSU client failed to send negotiation message. Error: [dec] ([chars])
Explanation Crypto RSA ISSU client failed to send a session negotiation message to the peer. When there is a problem in the ISSU negotiation the standby unit can not be brought up.
Recommended Action LOG_STD_SH_CMD_ACTION( show logging and show checkpoint client)
%CRYPTO_RSA_ISSU-3-SESSION_NEGO : Crypto RSA ISSU client encountered unexpected client nego_done. Error: [dec] ([chars])
Explanation Crypto RSA ISSU client encountered an unexpected 'client negotiation done'.
Recommended Action LOG_STD_SH_CMD_ACTION( show issu session <client_id> and show issu negotiated capability <session_id>)
%CRYPTO_RSA_ISSU-3-SESSION_REGISTRY : Crypto RSA ISSU client failed to register session information. Error: [dec] ([chars])
Explanation Crypto RSA ISSU client failed to register session information. When there is a problem with the session the standby unit cannot be brought up.
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>)
%CRYPTO_RSA_ISSU-3-SESSION_UNREGISTRY : Crypto RSA ISSU client failed to unregister session information. Error: [dec] ([chars])
Explanation Crypto RSA 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>)
%CRYPTO_RSA_ISSU-3-TRANSFORM_FAIL : Crypto RSA ISSU client [chars] transform failed for message type [dec]. Error: [dec] ([chars])
Explanation Crypto RSA ISSU client could not transform the message. If the transmit transformation failed, it means that the checkpoint message can not be sent to the standby unit. If the receive transformation failed, it means that the checkpoint message can not be applied on the standby unit. In both cases the Crypto RSA state will not be indentical with the active unit.
Recommended Action LOG_STD_SH_CMD_ACTION( show issu session <client_id> and show issu negotiated version <session_id>)
CTS_PD
%CTS_PD-2-IPC_FAILURE : CTS-IPC message [chars] handler failed, rc [int]
Explanation An IPC message handler for the CTS feature failed. This will cause the feature to not function.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CTS_PD-3-FEAT_CTX_DOWN : CTS-Invalid request [chars] ([int]) while context is down
Explanation While the feature context was not active, an invalid request was received from another layer of the CTS software stack.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%CTS_PD-3-FEAT_DOWN : CTS-Invalid request [chars] ([int]) while feature is down
Explanation While the feature was not active, an invalid request was received from another layer of the CTS software stack.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%CTS_PD-3-IPC_INIT_FAILED : CTS-IPC message handler registration failure, rc [int]
Explanation Registering an IPC message handler for the CTS feature failed. This will cause the feature to not function.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CTS_PD-3-IPC_INVALID_MSG : CTS-Invalid request [int]
Explanation We received an invalid message from another layer of the CTS software stack.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%CTS_PD-3-IPC_INVALID_MSG_LEN : CTS-Invalid IPC length, [dec]:[dec] len [dec] flags [hex] source [dec]
Explanation Invalid IPC message length
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CTS_PD-3-IPC_NORES : CTS-No space for the IPC reply, size [int], request [int]
Explanation For a request from upper CTS software stack layers it was not possible to allocate space for a reply for the specified size.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%CTS_PD-3-IPC_OPEN_REPLY : CTS-IPC Open Reply failed, request [int]
Explanation For a request from upper CTS software stack layers it was not possible to open the reply buffer.
Recommended Action This is normally a software issue. LOG_STD_RECUR_ACTION
%CTS_PD-3-IPC_SEND_FAILED : CTS-IPC [chars] [int] send failed [int]
Explanation IPC message send failure
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
CVLA
%CVLA-2-IPC_INIT : IPC message handler registration failure, rc [int]
Explanation Registering an IPC message handler for the CVLA infra failed. This will cause the infra to not function.
Recommended Action This is normally a software issue. The consequences are that the CVLA infra will not function. LOG_STD_ACTION
%CVLA-3-IPC_NORES : No space for the IPC reply, size [int]
Explanation For a request from upper CVLA 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 infra activation.
Recommended Action This is normally a software issue. LOG_STD_RECUR_ACTION
%CVLA-3-IPC_OPEN_REPLY : IPC Open Reply failed, request [int]
Explanation For a request from upper CVLA 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 infra activation.
Recommended Action This is normally a software issue. LOG_STD_RECUR_ACTION
CWAN_ALARM
%CWAN_ALARM-6-INFO : [chars] [chars] [chars] [chars] [chars]
Explanation This message provides alarm assertion or deassertion information.
Recommended Action No action is required.
%CWAN_ALARM-6-SONET : [chars] [chars] [chars] [chars] [chars]
Explanation This message is generated whenever (a) an alarm is present in the system (and the alarm status has been reported to the RP) or (b) an alarm has been removed from the system (and the alarm status has been reported to the RP
Recommended Action No action is required.
CWAN_CHOC
%CWAN_CHOC-4-ALLOCFAIL : Interface [dec]/[dec] allocation failed: [chars]
Explanation required resources unavailable.
Recommended Action Either upgrade system memory or reconfigure memory usage.
%CWAN_CHOC-4-CORRUPT : [chars] information seems to be corrupted, bad value =[int]
Explanation wrong parameters detected internally
Recommended Action This is only a debug warning message. The unexpected value is discarded.
%CWAN_CHOC-4-IFCONFIG : [chars] config error ([dec], lc delay:[dec] ms): [chars]
Explanation RP received configuration error from linecard.
Recommended Action Reconfigure or shut/no shut the error channel.
%CWAN_CHOC-4-LCCFG_MISMATCH : LC needs reboot due to config mismatch on [chars], (rc=[int])
Explanation RP detects LC's channel provisioning mismatching start-config
Recommended Action reset linecard: hw-module module <slot> reset
%CWAN_CHOC-4-LCLOCK_FAIL : Interface [chars] failed to acquire semaphore for LC access: [chars]
Explanation Other process locked the semaphore for too long.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_CHOC-4-PROV_FAIL : Interface [chars] provisioning ch([dec]) failed: [chars]
Explanation provisioning conflict or resource shortage
Recommended Action workaround: under 'controller sonet', do 'no channelized' followed by 'channelized', twice. If problem persists, do a 'show controller sonet <slot>/<port>' and 'show controller {pos/serial} <slot>/<port>:<chan>' then contact cisco technical support representative.
%CWAN_CHOC-4-UNPROV_FAIL : Interface [chars] unprovisioning failed: [chars]
Explanation Linecard failed to response unprovisioning command.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_CHOC-4-UNSUP : Slot [dec]: Unknown [chars] ([dec])
Explanation This value is not recognized by this version of software.
Recommended Action Check linecard version. Normally this is harmless but worth contacting cisco technical support representative.
%CWAN_CHOC-4-WRONG_LL : %.16s received wrong loveletter : type=[int], length=[int]
Explanation wrong parameters detected internally
Recommended Action This is only a debug warning message. The unexpected messages from linecard is harmlessly discarded.
%CWAN_CHOC-6-LCDRIVER : OIR failed: slot [int] linecard not responding to initial query
Explanation OIR insertion aborted due to failing to contact lc
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_CHOC-6-WRONG_GULF : [chars] hardware version (gulf v[int]) does not support OC-12 or OC-48
Explanation Early version of hw asic (GULF2.0 and below) has bugs in rx fifo depth which can not handle oc-12 or oc-48 rate. Either limiting channel provisioning or upgrading hw
Recommended Action Limit channel provisioning to DS3 and/or OC3
CWAN_CHOC_DS0
%CWAN_CHOC_DS0-3-CDBFAIL : Port [dec]/[dec] -fail to create a SONET controller data structure
Explanation The software resource can't be allocated for this hardware
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_CHOC_DS0-3-CFG_BAD_PARA : [chars]: invalid config parameter [chars]
Explanation Configuration parameter is invalid
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_CHOC_DS0-3-IFCONFIG_ERR : config error on port [dec]/[dec]([chars]), cmd [dec] [chars]
Explanation A configuration command sent from the system to a linecard failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_CHOC_DS0-3-PORTFAIL : Port [dec]/[dec] -fail to create a port instance data structure
Explanation The software resource can't be allocated for this hardware
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_CHOC_DS0-3-RMCTRLR_UNKNOWN : Slot [dec] -Unknown linecard type [dec] removed
Explanation This hardware can't be recognized by this version of software.
Recommended Action Check software version. Make sure the software supports the hardware.
%CWAN_CHOC_DS0-3-T1CFG_CCBERROR : CCB command error (cmd, [dec], arg [dec]) on T1 [dec]/[dec]/[dec]
Explanation A command sent from the system to a linecard failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_CHOC_DS0-3-UNKNOWNCTRLR : Slot [dec] -Unknown linecard type [dec]
Explanation This hardware can't be recognized by this version of software.
Recommended Action Check software version. Make sure the software supports the hardware.
%CWAN_CHOC_DS0-3-UNKNOWN_MIB_TYPE : Unknown MIB type [int] from slot [int]
Explanation Draco received unknown communication message from linecard
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%CWAN_CHOC_DS0-3-VCCFG_CCBERROR : CCB command error (cmd, [dec], arg [dec]) on port [dec]/[dec] channel [dec]
Explanation A command sent from the system to a linecard failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_CHOC_DS0-4-ALLOCFAIL : Interface [dec]/[dec] allocation failed: [chars]
Explanation required resources unavailable.
Recommended Action Either upgrade system memory or reconfigure memory usage.
%CWAN_CHOC_DS0-4-CORRUPT : [chars] information seems to be corrupted, bad value =[int]
Explanation wrong parameters detected internally
Recommended Action This is only a debug warning message. The unexpected value is discarded.
%CWAN_CHOC_DS0-4-IFCONFIG : [chars] config error ([dec], lc delay:[dec] ms): [chars]
Explanation RP received configuration error from linecard.
Recommended Action Reconfigure or shut/no shut the error channel.
%CWAN_CHOC_DS0-4-LCLOCK_FAIL : Interface [chars] failed to acquire semaphore for LC access: [chars]
Explanation Other process locked the semaphore for too long.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_CHOC_DS0-4-PROV_FAIL : Interface [chars] provisioning ch([dec]) failed: [chars]
Explanation provisioning conflict or resource shortage
Recommended Action workaround: under 'controller sonet', do 'no channelized' followed by 'channelized', twice. If problem persists, do a 'show controller sonet <slot>/<port>' and 'show controller {pos/serial} <slot>/<port>:<chan>' then contact cisco technical support representative.
%CWAN_CHOC_DS0-4-UNPROV_FAIL : Interface [chars] unprovisioning failed: [chars]
Explanation Linecard failed to response unprovisioning command.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_CHOC_DS0-4-UNSUP : Slot [dec]: Unknown [chars] ([dec])
Explanation This value is not recognized by this version of software.
Recommended Action Check linecard version. Normally this is harmless but worth contacting cisco technical support representative.
%CWAN_CHOC_DS0-4-WRONG_LL : %.16s received wrong loveletter : type=[int], length=[int]
Explanation wrong parameters detected internally
Recommended Action This is only a debug warning message. The unexpected messages from linecard is harmlessly discarded.
%CWAN_CHOC_DS0-5-LOOPSTATUS : [chars], [chars]
Explanation A configurable loopback status.
Recommended Action No action is required.
CWAN_CHOC_DSX
%CWAN_CHOC_DSX-3-ENQUEUE_FAIL : [chars]
Explanation cmd enqueue failure
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%CWAN_CHOC_DSX-3-INVALID_SUBR_HWIDB : Invalid Subrate hwidb on T3 [dec]/[dec]
Explanation invalid subrate hwidb
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%CWAN_CHOC_DSX-3-NODESTROYSUBBLOCK : The [chars] subblock named [chars] was not removed
Explanation A software error has occured, this message is displayed when IDB subblocks cannot be removed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_CHOC_DSX-3-NULLDS3MIBTABLE : Null DS3 MIB table (snmp_if_index [int])
Explanation System cannot find the DS3 MIB table pointer
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%CWAN_CHOC_DSX-3-PROCESS_ERROR : process error -[chars]
Explanation process encountered fatal error
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%CWAN_CHOC_DSX-3-PROCESS_FAIL : process creation failed for [chars]
Explanation process creation failed for handling cmd
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%CWAN_CHOC_DSX-3-SEND_DRIVER_READY : send driver ready msg failed for [dec]
Explanation IPC message failure
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%CWAN_CHOC_DSX-3-T1CFG_ERROR : T1 [int]/[int]/[int] config command error (cmd [int], arg [int], retval [int])
Explanation A command sent from the system to a linecard failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_CHOC_DSX-3-T3CFG_ERROR : T3 [int]/[int] config command error (cmd [int], arg [int], retval [int])
Explanation A command sent from the system to a linecard failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_CHOC_DSX-3-UNKNOWN_CTRLR : Slot [dec] -Unknown linecard type [dec]
Explanation This hardware can't be recognized by this version of software.
Recommended Action Check software version. Make sure the software supports the hardware.
%CWAN_CHOC_DSX-3-VCCFG_ERROR : VC [int]/[int]:[int] config command error (cmd [int], arg [int], retval [int])
Explanation A command sent from the system to a linecard failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_CHOC_DSX-3-VC_CONFIG_ERR : [chars] T1 [dec] channel group [dec] of T3 [dec]/[dec] unsuccessful (error code [dec])
Explanation channel configuration error
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%CWAN_CHOC_DSX-5-DEF_SUBRATE : [chars] [chars]
Explanation Remote subrate configuration changed
Recommended Action Inform the network operator that subrate configuration changed by remote end
%CWAN_CHOC_DSX-5-UNKNOWN_EVENT : [chars]
Explanation Unexpected event received by the process
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
CWAN_CONTAINER_ACCESS
%CWAN_CONTAINER_ACCESS-5-CWAN_NO_CONTAINER : Associated container interface does not exist for [chars]
Explanation The container interface no longer exists for access interface.
Recommended Action No action is required.
%CWAN_CONTAINER_ACCESS-5-CWAN_VRF_MISMATCH : VRF of [chars] access does not match with [chars]
Explanation VRF of access interface does not match with that of associated container interface. Either container interface is deleted or VRF of container interface is changed
Recommended Action No action is required.
CWAN_HA
%CWAN_HA-3-CCB_INIT_ERROR : Failed to initialize CCB list for slot [dec].
Explanation The High Availability component for WAN modules failed to properly initialize state information for the specified slot.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_HA-3-IFCFG_CMD_NOT_UNIQUE : More than one command registered for unique-key generator for interface configuration command [int].
Explanation The High Availability component for WAN modules is unable to properly synchronize state information for the current configuration due to a conflict in command identifiers.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_HA-3-IFCFG_INIT_ERROR : Failed to initialize Interface Configuration list for slot [int]/[int].
Explanation The High Availability component for WAN modules failed to properly initialize state information for the specified slot.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_HA-3-IFCFG_NO_UNIQUE_KEY : No unique-key generator registered for interface configuration command [int].
Explanation The High Availability component for WAN modules is unable to properly synchronize state information for the current configuration.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_HA-4-CCB_PLAYBACK_ERROR : CCB playback failed for slot [dec].
Explanation The High Availability component for WAN modules failed to synchronize some new state information for the specified slot.
Recommended Action Reload the standby supervisor module to force a fresh bulk synchronization. If this error recurs, LOG_STD_ACTION
%CWAN_HA-4-CCB_RECORD_ERROR : CCB record failed for slot [dec].
Explanation The High Availability component for WAN modules failed to record some new state information for the specified slot.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_HA-4-IFCFG_DFLT_LIST_ERROR : For Interface Configuration command [int], default retval list search resulted [hex] for slot [int]/[int]
Explanation The High Availability component for WAN modules failed to synchronize some new state information for the specified slot.
Recommended Action LOG_STD_SH_CMD_ACTION(show platform redundancy if-config default-retvals)
%CWAN_HA-4-IFCFG_PLAYBACK_ERROR : Interface Configuration command [int] playback failed for slot [int]/[int].
Explanation The High Availability component for WAN modules failed to synchronize some new state information for the specified slot.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_HA-4-IFCFG_RECORD_ERROR : Interface Configuration command [int] record failed for slot [int]/[int].
Explanation The High Availability component for WAN modules failed to record some new state information for the specified slot.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_HA-4-IFEVENT_BULKSYNCFAIL : [chars] ifevent: [dec] error: [dec]
Explanation Failed CWAN if-event bulk sync.
Recommended Action No action is required.
%CWAN_HA-4-IFEVENT_INCRSYNCFAIL : [chars] for ifevent: [dec] with error: [dec]
Explanation Failed CWAN if-event incremental sync.
Recommended Action No action is required.
%CWAN_HA-4-IFEVENT_UNEXPECTED_BULKTYPE : Unexpected value for bulk sync type ([dec]) received.
Explanation Received a unexpected type in bulk sync message.
Recommended Action No action is required.
%CWAN_HA-4-LTLSYNCFAIL : Failed to sync LTL data during [chars] for [chars] [int]: (slot=[dec],slotunit=[dec], if_num=[dec]) to standby (vlan=[int],hash=[int],ltl=[int])
Explanation Some LTL data did not sync correctly from active to standby RP
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_HA-4-NOSRPBULKSYNC : Failed to [chars] SRP bulk data (slot=[dec], intf=[dec], type=[dec]), ret code [dec]
Explanation Some SRP-related state information failed to sync correctly from the active RP to the standby RP during the HA bulk-synchronization phase.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_HA-4-NOSRPSYNC : Failed to sync SRP packet (slot=[dec],intf=[dec]) to standby, HA_SYNC_STATUS=[dec]
Explanation Some SRP-related state information failed to sync correctly from the active RP to the standby RP when the configuration changed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_HA-4-SRPSYNC : Slot [dec]: [chars]
Explanation An error occured while syncing SRP states from active RP to standby RP.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
CWANLC
%CWANLC-2-PCIERROR : Fatal PCI Error [chars] seen on PCI Bus [dec]
Explanation A Fatal PCI Error was detected on the PCI bus. Most likely it is a hardware problem.
Recommended Action Call your technical support representative for assistance if this message persists.
%CWANLC-3-CWANLC_EARL_VERSION_NOTICE : CWAN receives mismatch Earl version notification. New Earl[int] vs Earl[int]
Explanation The RP has determined, via an SCP find operation, that the version of the EARL switching engine on the line card has changed. This message occurs during switchover operation. The version of the EARL switching engine is specified in the message text.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWANLC-3-FATAL : [chars]
Explanation The Optical Services Module line card has encountered a fatal error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWANLC-3-FPD_INCOMPATIBLE : FPD ID=[int] image in this FPD package is for revision [int].x boards. It is incompatible with current board revision of [int].[int]
Explanation This FPD package does not contain images that are compatible with the current board revision.
Recommended Action Perform the FPD upgrade operation with a newer version of FPD image package that is compatible with the running Cisco IOS software. Consult with the FPD image package section of the Cisco IOS software release note to confirm if your board revision is supported for a particular release.
%CWANLC-3-HWREVREADFAIL : Failed to retrieve h/w version from EEPROM
Explanation The Linecard failed to read the hardware version from the CPU eeprom.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWANLC-3-IPCALLOCFAIL : Failed to allocate IPC buffer [chars]
Explanation The Linecard failed to allocate a buffer for communication with the Route Processor (Draco).
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%CWANLC-3-IPCPORT : Failed to [chars] IPC port '[chars]', error [chars]
Explanation The Linecard failed to create a port for communication with the Route Processor (Draco).
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%CWANLC-3-IPCPORTFAIL : Failed to open IPC port '[chars]' [chars]
Explanation The Linecard failed to open a port for communication with the Route Processor (Draco).
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%CWANLC-3-IPCSENDFAIL : Failed to send IPC message [chars]
Explanation The Linecard failed to send a message to the Route Processor (Draco).
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%CWANLC-3-LTL_NOPPEPORTMAP : Failed to retrieve default port mapping for packet processor [int]
Explanation The linecard software initialization was not completed correctly
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWANLC-3-TVPN_NOMEM : Failed to start vpn, not enough memory
Explanation The OSM card could not start VPN due to a memory exhaustion
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If this message recurs, LOG_STD_ACTION
%CWANLC-4-LOGMSGTOOBIG : Logger message length exceeds max, [int] bytes
Explanation The Linecard attempted to send a large message to the Route Processor (Draco).
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWANLC-5-IPCPENDING : Too many messages ([dec]) in IPC pending queue
Explanation The IPC pending queue is growing. Will soon deplete the IPC header cache and the IO buffers
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWANLC-5-NOSCPPING : Linecard has not sent SCP PING responses for too long
Explanation SCP ping mechanism is used by RP/SP processors to monitor if the linecard executing IOS is in a healthy state. This SCP ping response has not been sent by the line card for long time now - the line card has exported its context information to the RP and may be powercycled. The exported context is available in the output of 'show diag'
Recommended Action Save the 'show diag' output generated and contact your technical support representative if the line card is reset
%CWANLC-6-BUSSTALL : Constellation BUS Stall detected
Explanation This message indicates that a stall was detected on the Constellation Bus probably due to some OIR activity on the Bus.
Recommended Action No action needed, Informational.
%CWANLC-6-BUSSTALLCLEAR : Constellation BUS Stall cleared
Explanation This message indicates that a stall was cleared on the Constellation Bus.
Recommended Action No action needed, Informational.
%CWANLC-6-LONGSTALL : Long bus stall ([int] ms), check for improperly seated cards
Explanation This message indicates that a stall was detected, but the backplane stall was longer than expected.
Recommended Action Make sure all cards are firmly seated. If the problem reoccurs, it may indicate a hardware failure.
CWANLC_ATM
%CWANLC_ATM-3-CMDERR : [chars]: [chars] IPC command fails (cause: [hex])
Explanation The ATM RP driver experienced IPC command error.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%CWANLC_ATM-3-IPC_ERROR : [chars]: IPC command [chars] failure due to [chars]
Explanation The SPA ATM RP driver experienced IPC command error.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%CWANLC_ATM-3-NOVPSPACE : [chars]: out of VP space for VPI [dec]
Explanation Out of VPs on the SAR.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%CWANLC_ATM-3-VCCLOSEFAIL : [chars]: Failed to remove VC [dec]/[dec] cause [int]
Explanation Attempt to remove VC on the linecard failed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%CWANLC_ATM-3-VPCLOSEFAIL : [chars]: Failed to remove VP [dec] cause [int]
Explanation Attempt to remove VP on the linecard failed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%CWANLC_ATM-4-CLOSEPEND : [chars]: The TX SAR is currently freeing internal buffers previously allocated for the identical channel id. The execution of the current command is delayed.
Explanation The TX SAR has taken longer than expected to free its internal buffers.
Recommended Action No action is required.
%CWANLC_ATM-4-MISMATCH_VCENCAP : [chars]: Cannot mix VC encapsulation types in multipoint interfaces
Explanation This ATM card only allows VC encapsulations of the same type on the main interface or multipoint subinterfaces
Recommended Action Reconfigure the ATM interface with matching VC encapsulations
%CWANLC_ATM-4-SEMHOG : [chars]: Process [dec] ([chars]) hogging semaphore --called by process [dec] ([chars])
Explanation The named process has held the resource semaphore longer than expected.
Recommended Action No action is required.
%CWANLC_ATM-4-UNSUP : [chars]: unsupported feature: [chars]
Explanation This feature is not supported by Draco ATM RP.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
CWAN_RP
%CWAN_RP-1-OVERRIDE_MAC_INVALID : [chars] has invalid override-mac-address.
Explanation The user has issued an override-mac-address that does not match the mac address of the MSFC. This can occur if the config has been moved to new hardware or the mac-address command has been used on another interface. while the system automatically corrects this, the config needs to be adjusted.
Recommended Action Modify the override-mac-address command in the config.
%CWAN_RP-1-TOO_MANY_VRF : Slot [int] can not support all the VRFs configured!
Explanation A non-Enhanced OSM card has been inserted into a router with more than 511 IP VRFs already configured. This router cannot support more than 511 IP VRFs if there is at least one non-Enhanced OSM in the system.
Recommended Action Replace the inserted non-Enhanced OSM with an Enhanced OSM, or decrease the number of IP VRFs to 511 or fewer.
%CWAN_RP-3-BAD_IFCOMTYPE : Bad ifcom message type=[int]
Explanation A WAN module passed down a message that the RP software was not prepared to handle.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_RP-3-BOOTFAIL : The WAN module in slot [int]/[int] failed to boot
Explanation The WAN module in the slot indicated in the error messages failed to boot and will be reset.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_RP-3-CHANGE_POSEIDON_NEGOTIATION : Unable to change negotiation. Failed to send message to slot [dec] port [dec]!
Explanation MSFC2 failed to send message to change negotiation to OSM-4GE-WAN-GBIC
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_RP-3-CWAN_IFCOM_RMI : Cwan ifcom RMI failure -[chars]([dec])
Explanation The CWAN IFCOM RMI Registration.
Recommended Action No action is required.
%CWAN_RP-3-ERROR : NULL
Explanation This message can take many forms. It provides information about a software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_RP-3-FAILED_CONFIG : Failed to send line card config message [chars] for slot [int] port [int]
Explanation The RP could not send the specified configuration message to the line card
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_RP-3-FOREVER : cmd [int] to [chars] (slot [int]/[int]) took [int]secs, done [hex]
Explanation A CCB command from the RP to a WAN module took longer than expected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_RP-3-GBIC_INSERTED : GBIC media type [dec] inserted in [chars]
Explanation A GBIC was inserted in the interface.
Recommended Action No action is required.
%CWAN_RP-3-GBIC_REMOVED : GBIC removed from [chars]
Explanation The GBIC was removed from the interface.
Recommended Action No action is required.
%CWAN_RP-3-HV_ALLOCFAIL : [chars]: Failed to allocate a VLAN: [chars]
Explanation VLAN allocation failed for the stated reason.
Recommended Action First, power down any unused linecards. Next, delete any unused interfaces/subinterfaces, and any unused L2 VLANs from the VLAN database. Then wait for >3 minutes and retry.
%CWAN_RP-3-IFCFG_CMD_NOT_OWNER : Process '[chars]' waiting for interface configuration command ([hex]) to slot [int]/[int] without acquiring lock owned by process '[chars]'
Explanation A process on the RP sent an configuration command to the slot specified in the error message and a different process waited for the result. This could cause incorrect line card configuration states.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_RP-3-IFCFG_FOREVER : to [chars] (slot [int]/[int]) took [int]secs, ret_val [int]
Explanation A interface config command from the RP to a WAN module took longer than expected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_RP-3-IFCONFIG_ERR : Interface config failed on port [dec]/[dec], cmd [dec], retval [dec]
Explanation A configuration command sent from the system to a linecard failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_RP-3-IPCALLOCFAIL : Failed to allocate IPC buffer [chars]
Explanation The RP failed to allocate a buffer for communication with a WAN module.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_RP-3-IPCPORTFAIL : Failed to open IPC port '[chars]' [chars] with error [chars]
Explanation The RP failed to open a port for communication with a WAN module.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_RP-3-IPCSENDFAIL : Failed to send IPC message [chars]
Explanation The RP failed to send a message to a WAN module.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_RP-3-KEEPFAIL : The WAN module in slot [int]/[int] is not responding to keepalives
Explanation The WAN module was either reset or has crashed and will be reset.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_RP-3-LC_CRASHINFO : [chars] copied onto RP bootflash
Explanation The WAN module has crashed, and the crashinfo file has been copied onto the RP bootflash. The crashinfo filename indicates the module's slot. The file can be viewed using the <CmdBold>more<noCmdBold> command.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_RP-3-LC_CRASHINFO_BLOCKED : Duplicate crashinfo upload from slot [int]/[int] blocked
Explanation The WAN module has crashed, and the crashinfo was not saved because the WAN module has already crashed recently.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_RP-3-LC_CRASHINFO_CORRUPT : Verification of crashinfo from slot [int]/[int] failed
Explanation The WAN module has crashed, and verification of the crashinfo it sent failed. The crashinfo has not been saved to RP bootflash.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_RP-3-LC_CRASHINFO_ERR : Unexpected error while receiving crashinfo from slot [int]/[int]
Explanation The WAN module has crashed, and an unexpected error occured while the crashinfo was being copied onto RP bootflash.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_RP-3-LC_CRASHINFO_IFSERR : Error [chars] [chars]: [chars] ([int])
Explanation The WAN module has crashed, and an error occured while trying to access the RP's bootflash to save the crashinfo.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_RP-3-LC_CRASHINFO_NOSPACE : Not enough space on RP bootflash for crashinfo from slot [int]/[int] ([int] bytes needed, [int] available)
Explanation The WAN module has crashed, and there is not enough space on the RP bootflash to store the crashinfo.
Recommended Action Free up space on the RP's bootflash by using the <CmdBold>delete and <CmdBold>squeeze commands.
%CWAN_RP-3-LCLOG_BADSEV : Invalid message severity from slot [int]/[int]: [int]
Explanation The WAN module passed down a logger message with an invalid severity level that the RP could not handle.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_RP-3-MODULE_TYPE : cannot find FCI for module type [int] in slot [int]
Explanation An internal software error occurred while the system was detecting the module type for the module in the specified slot. The operation of the module will be affected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_RP-3-OIRTWICE : Slot [int] OIR insertion/removal not paired up: [chars]
Explanation An internal OIR-related error occured for the specified WAN module.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_RP-3-POWER_CYCLE : Power cycling WAN module in slot [int]/[int]. [chars]
Explanation The WAN module is being power cycled.
Recommended Action No action is required.
%CWAN_RP-3-POWER_CYCLE_IMMINENT : The WAN module in slot [int]/[int] will be power cycled in [dec] seconds.
Explanation The WAN module in the slot specified in the error message will be power cycled in the amount of time specified in the error message
Recommended Action No action is required.
%CWAN_RP-3-PROCMSG : Process msg send failed for process[dec]
Explanation Process message send failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_RP-3-RESET_FAIL : The WAN module in slot [int] failed even after several resets
Explanation The WAN module in the slot specified in the error message did not boot successfully, even after multiple attempts.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_RP-3-SCPALLOCFAIL : Failed to allocate SCP packet [chars]
Explanation The RP failed to allocate a packet for communication with other slots in the chassis.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_RP-3-SLOTCACHE_SYNTAX : Error ([chars])!
Explanation The RP failed to parse the slot configuration string.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_RP-3-UPGRADE_ERROR : Slot [int]: The ROMMON upgrade failed to complete.
Explanation An error occurred during the upgrade process.
Recommended Action If the module reloads successfully, please check the file and try again, otherwise please contact your Cisco technical support representative.
%CWAN_RP-3-WAN_BRIDGING_CFG_EXCD : The number of VPLS/EoMPLS/Bridging/QinQ VCs exceeded the maximum([int]) supported by slot: [int] [chars]
Explanation The user has attempted to configure more VPLS, EoMPLS, Bridging VCs than the number that is supported by the platform.Review the configuration guidelines for the features that are being configured and reduce the number of VPLS, EoMPLS, Bridging to the number that is supported by the platform.
Recommended Action None
%CWAN_RP-4-CONFIG_MISMATCH : Irreconcilable Configuration difference between Active & Standby Supervisors due to OIR/Config Event for [dec]/[dec] -> Reloading Standby Supervisor to synchronize the configuration.
Explanation Unexpected configuration difference between Supervisors.
Recommended Action None. This is expected behavior.
%CWAN_RP-4-EMPTY_CWANBAYS : FLEXWAN in slot [dec] is empty. Please remove the Flexwan or insert it with atleast one PA
Explanation The FLEXWAN in the specified slot does not contain any Port Adapters.
Recommended Action The FLEXWAN should be removed as this is an unsupported configuration
%CWAN_RP-4-IFCFG_CMD_TIMEOUT : Interface configuration command ([hex]) to slot [int]/[int] timed out
Explanation The RP sent an configuration command to the slot specified in the error message and received no confirmation for the command.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_RP-4-INCR_CFG_SYNC_FAIL : 7600 incremental running-config sync for [[dec]/[dec]] failed -[chars]([dec]) , Reload Standby
Explanation The specified 7600 incremental running-config sync failed
Recommended Action Power cycle the redundant supervisor
%CWAN_RP-4-INVALID_UNIT : Invalid 7600 Unit: [[dec]/[dec]].
Explanation The specified 7600 slot/cpu beyonds the Chassis's limit.
Recommended Action Power cycle the redundant supervisor
%CWAN_RP-4-IPCFAILED : IPC failed to send RPC message to WAN module
Explanation The RP failed to send an RPC message via IPC to a WAN module.
Recommended Action No action is required.
%CWAN_RP-4-LCLOG_TOOLONG : Message too long from slot [int]/[int]: [int] bytes
Explanation The WAN module passed down a logger message that is too long for the RP to handle.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_RP-4-LL_UNKNOWN : Unknown linecard message: type [int], [chars]
Explanation Mismatch version between RP and LC, or internal message format mismatch
Recommended Action No action is required.
%CWAN_RP-4-MODULE_CONFIG_MISSING : configuration not available/not matching in startup-config for slot [int]
Explanation Some information regarding the configuration of the module in the specified slot is missing. Any configuration in the startup-config for the interfaces will not be applied. If the module in the specified slot is a FlexWAN, the missing configuration information is details of the Port Adapters in the FlexWAN module. This information is missing from the <CmdBold>SLOTCACHE<NoCmdBold> ROMMON variable.
Recommended Action If the module in the slot specified in the error message has not previously been inserted, it has no previous configuration; therefore, no action is required. If the configuration for the specified slot in the startup-config is suitable for the module in that slot, manually apply the configuration after the module has loaded by one of the following two methods. The second method requires a system reload: - Enter the <CmdBold>copy nvram:startup-config system:running-config<NoCmdBold> command to re-apply your saved configuration, then enter the <CmdBold>no shutdown<NoCmdBold> command on all interfaces whose configuration was rejected, then enter the <CmdBold>copy system:running-config nvram:startup-config<NoCmdBold> command to save your configuration and the WAN module slot configuration. - Enter the <CmdBold>copy<NoCmdBold> command to copy your startup-config to a temporary location (for example, <CmdBold>copy nvram:startup-config bootflash:tmp-config<NoCmdBold>), then enter the <CmdBold>copy system:running-config nvram:startup-config<NoCmdBold> command to update the WAN module slot configuration, then enter the <CmdBold>copy<NoCmdBold> command to restore the temporary copy of the startup-config (for example, <CmdBold>copy bootflash:tmp-config nvram:startup-config<NoCmdBold>), then enter the <CmdBold>reload<NoCmdBold> command to reload the system. After using the second method, you may wish to use the <CmdBold>delete<NoCmdBold> command to remove the temporary copy of the startup-config. To prevent this condition from recurring, ensure that the <CmdBold>SLOTCACHE<NoCmdBold> variable is updated whenever modules that require it (FlexWANs, but not OSMs) are moved between slots in the chassis. The <CmdBold>SLOTCACHE<NoCmdBold> variable is updated when the running-config is written to the startup-config using the <CmdBold>copy system:running-config nvram:startup-config<NoCmdBold> command (or the deprecated <CmdBold>write memory<NoCmdBold> equivalent). The two methods of restoring the configuration for the module shown above ensure the <CmdBold>SLOTCACHE<NoCmdBold> variable is updated.
%CWAN_RP-4-SEMAHOG : Process [dec] ([chars]) hogging [chars]! calling proc [dec] ([chars])
Explanation The RP waited too long for a reply to a command sent to a WAN module.
Recommended Action No action is required.
%CWAN_RP-6-ADF_FILE : Slot [int]: Using VPN-SM Upgrade File: [chars]
Explanation Booting specified upgrade image for VPN Services Module.
Recommended Action No action is required.
%CWAN_RP-6-AUX_FILE : Slot [int]: Found VPN-SM Firmware in File: [chars]
Explanation The file specified in the message was found and will be loaded by the VPN Services Module instead of the bundled image.
Recommended Action No action is required.
%CWAN_RP-6-CARDRECONCILE : Module type changed on slot [int]/[int] from [int] to [int]
Explanation The WAN module has booted, and it has been detected that it is of a different type to the WAN module that was previously in this slot.
Recommended Action No action is required.
%CWAN_RP-6-CARDRELOAD : Module reloaded on slot [int]/[int]
Explanation The WAN module has booted.
Recommended Action No action is required.
%CWAN_RP-6-COREDUMP_ENABLED : No heartbeat or keepalive resets will occur for slot [int] since coredump has been enabled
Explanation The module in the slot has crashed and is configured to generate a coredump file. The module will not be reset due to heartbeat and keepalive failures to ensure the coredump file generation is not prematurely terminated.
Recommended Action No action is required.
%CWAN_RP-6-IMAGE_UPGRADE : Bootflash image upgrade [chars] for slot [int]/[int][chars]
Explanation The bootflash image on the WAN module has been or is being automatically upgraded.
Recommended Action No action is required.
%CWAN_RP-6-LC_PRESENT : [chars] in slot [int]
Explanation A WAN module was detected by the hardware.
Recommended Action No action is required.
%CWAN_RP-6-LC_RESET : The RP is reloaded, resetting slot [dec] is necessary. Please ignore errors if any, till the linecard comes up.
Explanation If the system is running Catalyst operating system software on the supervisor engine and Cisco IOS software on the MSFC, the WAN line cards that power up before the RP powers up will be reset automatically.
Recommended Action No action is required.
%CWAN_RP-6-NOPWRISSU : Spa inserted in [chars] powered down because ISSU is in progress
Explanation The Spa insertion detected during ISSU upgrade process. It will be acted upon completion of the ISSU process.
Recommended Action No action is required.
%CWAN_RP-6-OUT_OF_RESOURCE : [chars] configuration has exceeded available internal resources.
Explanation The resources required for configuration are no longer available. They may have been acquired by another application.
Recommended Action If the requested resources have not been allocated to another application, call your technical support representative for further assistance.
%CWAN_RP-6-OVERRIDE : Slot [int]: ...Overriding Intrinsic VPN-SM Firmware.
Explanation Specified image will be used instead of bundled image.
Recommended Action No action is required.
%CWAN_RP-6-PLAT_AVL_DEL_FAILED : Platform AVL delete failed for PPPoE session due to wrong slot id [dec]
Explanation Deletion of session related information from the AVL tree failed, because the slot number used to index it is wrong
Recommended Action No action is required.
%CWAN_RP-6-QUIESCE_FAIL : Quiesce failed for slot [int]/[int]
Explanation The RP failed to contact the WAN module during failover. The WAN module will be reset.
Recommended Action No action is required.
%CWAN_RP-6-SESS_LIMITS_CHASSIS : Exceeded max number of sessions supported. Supported limit 32000/chassis
Explanation Total number of subscriber sessions on this chassis exceeded the allowed limits. The supported limit is 32000 sessions per chassis
Recommended Action Avoid bringing up more number of sessions than the supported limit
%CWAN_RP-6-SESS_LIMITS_ES_PLUS : Exceeded max number of sessions supported on ES+ LC in slot [dec]. Supported limit 16000/ES+
Explanation Total number of subscriber sessions on ES+ line card exceeded the allowed limits. The supported limit is 16000 sessions per ES+
Recommended Action Avoid bringing up more number of sessions than the supported limit
%CWAN_RP-6-SESS_LIMITS_PORT_GROUP : Exceeded max number of sessions supported on port-group Gig[dec]/[dec] to Gig[dec]/[dec].Supported limit 4000/port-group on ES+ LC
Explanation Total number of subscriber sessions on a single port-group in ES+ exceeded the allowed limits. The supported limit is 4000 sessions per port-group
Recommended Action Rearrange the subscribers on ES+ in such a way maximum number of sessions supported in a port-group is 4000.
%CWAN_RP-6-SESS_LIMITS_SIP400 : Exceeded max number of sessions supported on SIP400 LC in slot [dec]. Supported limit 8000/SIP400
Explanation Total number of subscriber sessions on SIP400 line card exceeded the allowed limits. The supported limits is, 8000 sessions per SIP400
Recommended Action Avoid bringing up more number of sessions than the supported limit
%CWAN_RP-6-SESS_LIMITS_TEN_GIG_PORT : Exceeded max number of sessions supported on port Te[dec]/[dec]. Supported limit 8000/port on a Ten Gig port on ES+ LC.
Explanation Total number of subscriber sessions on a single Ten Gig port in ES+ exceeded the allowed limits. The supported limit is 8000 sessions per Ten Gig port.
Recommended Action Rearrange the subscribers on ES+ in such a way that maximum number of sessions per Ten Gig port is 8000
%CWAN_RP-6-UNQUIESCE_FAIL : Unquiesce failed for slot [int]/[int]. Error = [dec]
Explanation The RP failed to unquiesce the WAN module. The WAN module will be reset.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show diagbus and show ipc status command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_RP-6-UPGRADE_COMPLETE : Slot [int]: ROMMON upgrade complete. Reset the card for the changes to take effect.
Explanation The ROMMON upgrade has completed successfully. The card must be reloaded for the changes to take effect
Recommended Action No action is required.
%CWAN_RP-7-SLOTCACHE_CARDTYPE : parsed slot [dec], fci_type [dec]
Explanation Information parsed from the slot configuration string by the RP.
Recommended Action No action is required.
%CWAN_RP-7-SLOTCACHE_PATYPE : Bay [chars] has type [dec] ports([hex])
Explanation Information parsed from the slot configuration string by the RP.
Recommended Action No action is required.
CWAN_SLOT
%CWAN_SLOT-1-CF_ADDFAILED : Failed to register chkpt client, client = [dec]
Explanation The CF client could not be registered.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_SLOT-1-CF_NOBUF : Failed to get chkpt buffer, client = [dec]
Explanation Failed to get enough memory for checkpointing.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
CWAN_SPA
%CWAN_SPA-3-CREATION_FAILURE : slot=[dec] subslot=[dec], spa_type=[hex], lc_type=[hex].
Explanation Failed to create a SPA object.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_SPA-3-DIAG_CONFIG : [chars] did not complete [dec]/[dec]
Explanation An error has occured during diagnostic test.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_SPA-3-FAILURE : [chars]: SPA failure -cause: [chars] ([hex]), recovery action: [chars] ([dec])
Explanation The SPA failed for the specified reason
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_SPA-3-INTR_THROTTLE : Interface [chars] MAC interrupt was throttled. Reenabling MAC interrupts via one sec spa process
Explanation MAC interrupt burst has occurred on one of the interfaces on the link daughtercard. The error message indicates that a throttling mechanism has been applied to this port to avoid any operational damage that could be provoked by this event. The cause for this problem could be bad transceiver, highly frenquent flapping optical signals, or mismatched path signals (e.g. receiving 10GBASE-W signal on 10GE LAN interface), etc.
Recommended Action Check the interface configuration and received signal characteristics. Also verify the XFP transceiver and receive signal path to determine the If this message recurs, LOG_STD_ACTION
%CWAN_SPA-3-INVALID_DATA_INSTANCE : interface type [chars], slot [dec] port [dec] vc [dec] : [chars]
Explanation Data required to support the interface is not available.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_SPA-3-INVALID_IF_INDEX : index= [dec], cardType=[hex], spaType=[hex], slot [dec] subSlot [dec] slotunit [dec] vc [dec]
Explanation Index for the interface is not valid.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_SPA-3-INVALID_INDX_RANGE : index1= [dec], index2= [dec], maxIndex= [dec]
Explanation Invalid index range.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_SPA-3-MEM_ALLOC_ERROR : [chars]
Explanation Memory allocation error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_SPA-3-NULL_ATM_DB : Unable to create ATM DB for [chars]
Explanation Data required to support the interface is not available.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_SPA-3-NULL_SPA_PTR :
Explanation Pointer to a SPA object is NULL.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_SPA-3-NULL_VFT : [chars] virtual function table is not initialized. spaType=[hex]
Explanation A required function table is not initialized
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_SPA-3-NULL_VFUNC : [chars] vector is not initialized. spaType=[hex]
Explanation A required function vector is not initialized
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_SPA-3-POWER_CYCLE : [chars] occurred on Shared Port Adapter [int]/[int]
Explanation An error has occurred which will cause the Shared Port Adapter to be power cycled
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWAN_SPA-3-SPA_CREATION_FAILURE : slot=[dec] subslot=[dec], PID=[chars] lc_type=[hex].
Explanation Failed to create a SPA object.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
CWAN_T3E3
%CWAN_T3E3-3-IFCONFIG_ERR : Interface config error on T3 port [dec]/[dec], cmd [dec], retval [dec]
Explanation A configuration command sent from the system to a linecard failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
CWPA
%CWPA-2-BAD_HWVERS : Unable to determine board hardware version
Explanation The line card software cannot read the line card hardware version. This condition indicates a hardware error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWPA-2-PAOIR : Port adapter OIR not supported, reloading
Explanation An OIR operation occurred on the port adapters of the specified line card. OIR operations are not supported on the port adapter. This error has caused the line card to crash and reload.
Recommended Action Do not attempt an OIR operation on the port adapters of the specified line card.
%CWPA-2-PA_VOLFAIL : Port adapter [dec]V failed, Reloading flexwan
Explanation The line card has encountered an error involving power delivery to the line card. Likely causes for this error are an environmental condition, an overtemperature condition, or inconsistent voltage to the line card.
Recommended Action Check the input voltage and temperature of the line card. LOG_STD_RECUR_ACTION
%CWPA-2-WHICH_INT : Unexpected [chars] interrupt, INT status = [hex]
Explanation The line card specified in the error message has encountered an unexpected interrupt.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWPA-3-BAD_IFCOMTYPE : Bad ifcom message type=[int]
Explanation The Route Processor (Draco) passed down a message that the software was not prepared to handle.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%CWPA-3-BADMALUCMD2 : CWPA([int]): Unsupported MALU cmd/arg0=[hex][hex], arg1arg2=[hex][hex] , pascb=[hex]
Explanation The Route Processor (Draco) passed down a command that the software was not prepared to handle.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%CWPA-3-BADMALUCMD : Unsupported MALU command [dec], arg=[hex], pascb=[hex]
Explanation The Route Processor (Draco) passed down a command that the software was not prepared to handle.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%CWPA-3-CMDNOPASCB : PASCB Null for command [dec], arg=[hex]
Explanation The Route Processor (Draco) passed down a command that the software was unprepared to handle.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%CWPA-3-DIAGFAIL : Failed to handle diag [chars] [dec]
Explanation The FlexWAN line card failed to execute diag command. Further details are specified in the text that is displayed on the console or in the system log.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%CWPA-3-IPCALLOCFAIL : Failed to allocate IPC buffer [chars]
Explanation The FlexWAN line card failed to allocate a buffer for communication with the Route Processor (Draco).
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%CWPA-3-IPCSENDFAIL : Failed to send IPC message [chars]
Explanation The FlexWAN line card failed to send a message to the Route Processor (Draco).
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%CWPA-3-LVLTRTOOBIG : Loveletter length exceeds max, [int] bytes
Explanation The FlexWAN line card attempted to send a large message to the Route Processor (Draco).
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%CWPA-3-NODISPATCH : Dispatch vector Null, cmd=[dec], dintf=[dec]
Explanation No command dispatch vector was found for the specified interface.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%CWPA-3-PROCCREATEFAIL : Failed to create [chars] process
Explanation The Linecard failed to create a process which which is necessary for proper functioning of the linecard.
Recommended Action Copy the error message as it appears, and report it to your technical support representative. If it is the 'stats export process' then you might not see input/output rate and bytes getting incremented in 'show interface' output for flexwan/flexwan2 non- channelised interfaces. However you can get the stats from 'show interface acc' or 'show interface stats'.
%CWPA-4-HEADER_TOO_BIG : Needs [dec] bytes, with only [dec] bytes available. Packet size [int], received from [chars], buffer [hex] packet start [hex]: %-08x:[hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex] %-08x:[hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex]
Explanation A packet was sent from the PA to either the route processor or the line card. That packet did not have enough available space to append the header. A new particle has been linked to the packet to store the header.
Recommended Action No action is required.
CWPAATOM
%CWPAATOM-3-BADLTL : Bad LTL index [hex] for vlan [int] local_vc_label [int]
Explanation Local Target Logic index value is invalid
Recommended Action If your EoMPLS traffic is fine then ignore this If not then contact your Cisco technical support representative.
CWRPSPA
%CWRPSPA-3-HWIDB_FAILURE : Creation: slot [dec] subSlot [dec] port [dec] vc [dec]
Explanation Failed to create an interface hwidb.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWRPSPA-3-INVALID_PORT_NUM : slot=[dec] port=[dec], hwidbType=[hex], max_port_num=[dec], LCtype=[hex]
Explanation The port number is out of range.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWRPSPA-3-MAX_SPA : Power to IPSEC-SPA-2G in [chars] is denied because it has exceeded the number allowed([dec])
Explanation The number of IPSEC-SPA-2G in a chassis is limited. This message is displayed when the number of IPSEC-SPA-2G in the chassis has exceeded this limit.
Recommended Action Use only the number of supported IPSEC-SPA-2G
%CWRPSPA-3-NO_HOST_INFO : slot [dec] subSlot [dec], spaType [hex]
Explanation Failed to get information about the host linecard.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWRPSPA-3-SPA_NO_HOST_INFO : slot [dec] subSlot [dec], PID [chars]
Explanation Failed to get information about the host linecard.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWRPSPA-4-SPA_CMD_NO_RESP : [chars]: No response for interface configuration command [chars]
Explanation A timeout occurred while RP was waiting for a response from line card. This may happen due to line card CPU being too busy to respond to the command.
Recommended Action No action is required.
%CWRPSPA-4-SPA_RESP_CMD_MISMATCH : [chars]: Expecting response to interface configuration command [chars] but received response to command [chars].
Explanation An internal synchronization error occurred while configuring the interface. The configuration may not have succeeded.
Recommended Action Check that the running configuration for the interface is correct. If this message occurred on the standby, try reloading the standby to ensure that its configuration is in sync. If this message is repeatable, please LOG_STD_SH_TECH_ACTION
%CWRPSPA-5-OUT_OF_RESOURCES : [chars]: Unable to create [chars] due to SPA resource limitations.
Explanation The SPA was unable to create the requested resource due to limited hardware or software resources
Recommended Action No action is required.
%CWRPSPA-6-CARDRELOAD : Module [int] reload due to SPA insert in [int]/[int].
Explanation When inserting a SPA on this carrier card, the card is reset.
Recommended Action No action is required.
CWS
%CWS-2-IPC_INIT_FAILED : CWS-IPC message handler registration failure, rc [int]
Explanation Registering an IPC message handler for the CWS feature failed. This will cause the feature to not function.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWS-3-IPC_INVALID_MSG : CWS-Invalid request [int]
Explanation Received Invalid message from CWS client proxy
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWS-3-IPC_NORES : CWS-No space for the IPC reply, size [int], request [chars]
Explanation For a request from CWS client proxy it was not possible to allocate space for a reply for the specified size.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWS-3-IPC_OPEN_REPLY : CWS-IPC Open Reply failed, request [chars]
Explanation For a request from CWS client proxy opening the reply buffer failed
Recommended Action This is normally a software issue. LOG_STD_RECUR_ACTION
%CWS-3-IPC_SEND_FAILED : CWS-IPC [chars] [chars] send failed [int]
Explanation IPC message send failure
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWS-5-CWS_INVALID_REF_COUNT : Invalid ref count [dec] in chunk [hex]
Explanation CTR has seen an invalid ref count in the NSH pool
Recommended Action This message is for informational purposed only, and used for CWS troubleshooting. LOG_STD_NO_ACTION
%CWS-5-CWS_ON_PATH_DEBUG : NSH D-bit set for SIP: %CA DIP: %CA Src_node: [dec] Src_If_Id: [dec] Tenant_Id: [dec]
Explanation CTR has seen an NSH header with D-bit set
Recommended Action This message is for informational purposed only, and used for CWS Per Flowing debugging in the Cloud. LOG_STD_NO_ACTION
CWTLC
%CWTLC-0-DMA_ENGINE_ASIC_FATAL_ERR : DMA Engine Asic[[dec]] fatal error: [chars]
Explanation The CWTLC DMA Engine ASIC received a fatal error.
Recommended Action This error will result in a crash. Collect the crashinfo file in line card,traffic parameters and config that triggered the issue then LOG_STD_SH_TECH_ACTION
%CWTLC-0-FATAL_EXCEPTION : [chars]
Explanation The Optical Services Module line card has encountered a fatal exception.
Recommended Action This error will result in a crash. Collect the crashinfo file in line card, traffic parameters and config or event that triggered the issue then LOG_STD_SH_TECH_ACTION
%CWTLC-2-FATAL_ATM : [chars]
Explanation The OSM card has encountered a fatal line management interrupt. This error is not recoverable and will cause the system to crash.
Recommended Action This error will result in a crash. Collect the crashinfo file in line card, traffic parameters and config that triggered the issue then LOG_STD_SH_TECH_ACTION
%CWTLC-2-PCITIMEOUT : Fatal Local I-O Bus [dec] Timeout Addr = [hex]
Explanation The Optical Services Module has encountered a PCI timeout.
Recommended Action Collect the details that triggered the issue, say like oir of linecard, switchover etc and then LOG_STD_SH_CMD_ACTION('show pci hardware' and 'show pci controller' from the line card)
%CWTLC-2-PLIM_RX : [chars]
Explanation The OSM line card encountered an FPGA error that caused a sequence error.
Recommended Action Collect the configuration, traffic parameter and event that triggered the issue and LOG_STD_SH_CMD_ACTION( 'show platform atm vc', 'show controllers' from the line card)
%CWTLC-2-SLAVEPCI : [chars]
Explanation The Optical Services Module has encountered a PCI error.
Recommended Action Collect the details that triggered the issue, say like any oir of linecard, switchover etc and then LOG_STD_SH_CMD_ACTION('show pci hardware' and 'show pci controller' from the line card)
%CWTLC-3-ATMTXFIFO : [chars]
Explanation The OSM line card has encountered an error with the FPGA that has caused the FIFO queue to exceed the maximum limit. This condition will cause the system to crash.
Recommended Action This error will result in a crash. Collect the crashinfo file in line card, traffic parameters and config that triggered the issue then LOG_STD_SH_TECH_ACTION
%CWTLC-3-BAD_IFCOMTYPE : Bad ifcom message type=[int]
Explanation The Route Processor (Draco) passed down a message that the software was not prepared to handle.
Recommended Action Collect the details that triggered the issue, say like any config change, switchover etc and then LOG_STD_SH_TECH_ACTION
%CWTLC-3-BADINT : Attempted to access HWIDB for port [int]
Explanation The Linecard attempted to access structure for interface associated with a non-existent port.
Recommended Action Check if reload of the Line card helps, else LOG_STD_SH_CMD_ACTION(show diagbus <slno>, from RP and 'show idb', 'show cwan vlans' from Line card )
%CWTLC-3-BADINTCREATE : Attempted to install HWIDB for port [int]
Explanation The Linecard failed to install a structure for interface because the associated port number was out of range.
Recommended Action Check if reload of the Line card helps, else LOG_STD_SH_CMD_ACTION(show diagbus <slno>, from RP and 'show idb', 'show cwan vlans' from Line card )
%CWTLC-3-BADMALUCMD2 : Unsupported MALU cmd/arg0=[hex][hex], arg1arg2=[hex][hex] , hwidb=[chars]
Explanation The Route Processor (Draco) passed down a command that the software was not prepared to handle.
Recommended Action Collect the details that triggered the issue, say like any config change, switchover etc and then LOG_STD_SH_TECH_ACTION
%CWTLC-3-BADMALUCMD : Unsupported MALU command [dec], arg=[hex], pascb=[hex]
Explanation The Route Processor (Draco) passed down a command that the software was not prepared to handle.
Recommended Action Collect the details that triggered the issue, say like any config change, switchover etc and then LOG_STD_SH_TECH_ACTION
%CWTLC-3-CMDNOINT : HWIDB Null for command [dec], arg=[hex]
Explanation The Route Processor (Draco) passed down a command that the software was unprepared to handle.
Recommended Action Collect the details that triggered the issue, say like any config change, switchover etc and then LOG_STD_SH_TECH_ACTION
%CWTLC-3-CONST_SWITCHING_BUS_INTERFACE_ASIC_ERR : Constellation Switching Bus Interface Asic [[dec]] error: [chars]
Explanation The CWTLC Switching Bus Interface ASIC received an error.
Recommended Action No action is required if traffic recovers. Otherwise, LOG_STD_SH_CMD_ACTION('show platform hardware sculptor fatal', 'show platform hardware sculptor drop', 'show platform hardware sculptor errors', 'show platform hardware sculptor registers' in line card)
%CWTLC-3-CONST_SWITCHING_BUS_INTERFACE_ASIC_HWERR : Constellation Switching Bus Interface Asic [[dec]] HW error: [chars]
Explanation The CWTLC Switching Bus Interface ASIC received a HW error and will be reset.
Recommended Action No action is required if traffic recovers. Otherwise, LOG_STD_SH_CMD_ACTION('show platform hardware sculptor fatal', 'show platform hardware sculptor drop', 'show platform hardware sculptor errors', 'show platform hardware sculptor registers')
%CWTLC-3-DMA_ENGINE_ASIC_ERR : DMA Engine Asic [[dec]] error: [chars]
Explanation The CWTLC DMA Engine ASIC received an error.
Recommended Action No action is required if traffic recovers. Otherwise LOG_STD_SH_CMD_ACTION('show platform hardware vanallen errors', 'show platform hardware vanallen registers', in line card)
%CWTLC-3-ERR_DETAIL : [chars]
Explanation This message provides additional error details for a previous error message, which may be of use to your support representative.
Recommended Action Follow the instructions for any error messages preceding this one, and be sure to include the text for this error.
%CWTLC-3-EXCEPTION_ERR : [chars]
Explanation The Optical Services Module line card has encountered an error exception.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWTLC-3-FABRIC_INTERFACE_ASIC_FATAL : OSM Fabric Interface ASIC Fatal Error. ERROR CODE: [chars]
Explanation The OSM Fabric Interface ASIC received a FATAL ERROR.
Recommended Action No action is required if traffic recovers. Otherwise, LOG_STD_SH_CMD_ACTION('show platform hardware medusa registers', 'show platform hardware medusa interrupt', from line card)
%CWTLC-3-FABRIC_INTERFACE_ASIC_PXF : CWAN PXF Client [[dec]] Not Running
Explanation An ASIC device on the OSM has detected that the designated PXF client is not running.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWTLC-3-FR_BAD_BRIDGING : Frame Relay: old bridge-vlan([int]) or new bridge-vlan([int]) on the bridged interface [chars] is malformed
Explanation This is an unexpected update from the route processor and should be ignored
Recommended Action No action is required.
%CWTLC-3-FR_CHANGEDLCI : frame relay p2p if_number([int]) and dlci([int]) mismatch: [chars] old dlci [int]
Explanation new dlci update comes on a different interface than previous update
Recommended Action LOG_STD_SH_CMD_ACTION('show frame-relay pvc',in RP 'show platform frame-relay' in Line card)
%CWTLC-3-FR_INTLEVEL : unexpected interrupt level invocation of frame-relay handler: [chars] if_number([dec]) dlci([dec])
Explanation Some feature code inadvertently invoked the linecard frame-relay handler which is designed to run at process-level. This may lead to data corruption and linecard crash.
Recommended Action LOG_STD_SH_CMD_ACTION('show frame-relay pvc', in RP 'show platform frame-relay' in Line card)
%CWTLC-3-FR_RX_TVC : RX_TVC greater than max for [chars] if_number([dec]) dlci([dec])
Explanation The system encountered an error while it was configuring the frame-relay connection. Trying to access the internal resources out of bound.
Recommended Action Collect the details that triggered the issue, say like any config change, switchover etc and then LOG_STD_SH_CMD_ACTION( 'show frame-relay pvc' ,in RP 'show platform frame-relay', 'show platform toaster intfid all' in Line card)
%CWTLC-3-INVALID_IF_IDX : invalid if_index ([dec])
Explanation CWTLC received a command with invalid interface index
Recommended Action Collect the details that triggered the issue, say like any config change, switchover etc and then LOG_STD_SH_CMD_ACTION('show idb', 'show cwan vlans', from Line card)
%CWTLC-3-IPCALLOCFAIL : Failed to allocate IPC buffer [chars]
Explanation The Linecard failed to allocate a buffer for communication with the Route Processor (Draco).
Recommended Action LOG_STD_SH_CMD_ACTION('show diagbus <slno>' from RP, 'show memory failures alloc', 'show memory' from Line card)
%CWTLC-3-IPCSENDFAIL : Failed to send IPC message [chars]
Explanation The Linecard failed to send a message to the Route Processor (Draco).
Recommended Action Collect the details that triggered the issue, say like any config change, switchover etc and then LOG_STD_SH_TECH_ACTION
%CWTLC-3-LL_FAIL : [chars]: loveletter failed. [chars]
Explanation failed to send loveletter to RP. Either no memory or IPC send failed
Recommended Action LOG_STD_SH_CMD_ACTION('show frame-relay pvc', 'show diagbus slno',in RP 'show platform frame-relay', 'show memory failures alloc','show memory' from Line card)
%CWTLC-3-LVLTRTOOBIG : Loveletter length exceeds max, [int] bytes
Explanation The Linecard attempted to send a large message to the Route Processor (Draco).
Recommended Action Collect the details that triggered the issue, say like any config change, switchover etc and then LOG_STD_SH_TECH_ACTION
%CWTLC-3-MCAST_REPL_ENGINE_FATAL : Multicast Replication Engine Asic Fatal Error. Resetting ASIC.
Explanation The OSM Multicast Replication Engine ASIC received a FATAL ERROR.
Recommended Action No action is required if traffic recovers. Otherwise, LOG_STD_SH_CMD_ACTION('show platform hardware titan registers', 'show platform hardware titan errors', from line card)
%CWTLC-3-NODISPATCH : Dispatch vector Null, cmd=[dec], dintf=[dec]
Explanation An internal Command sent from RP to LC has not been dispatched properly.
Recommended Action Collect the details that triggered the issue, say like any config change, switchover etc and then LOG_STD_SH_TECH_ACTION
%CWTLC-3-NOFABRICPROCESS : No fabric process created
Explanation The CWTLC Cross Bar Switch Fabric interface does not have a link process running: the system failed to create this process. This module will not support the fabric interface
Recommended Action Check if reload of the Line card helps, else LOG_STD_SH_CMD_ACTION('show fabric' from RP 'show processes memory, show processes cpu' in Line card)
%CWTLC-3-NOMEM : [chars]
Explanation The OSM card could not obtain statistics due to a memory exhaustion
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If this message recurs, LOG_STD_SH_CMD_ACTION( 'show diagbus slno' in RP, 'show memory failures alloc', 'show memory' from Line card)
%CWTLC-3-NO_STATID : PXF([dec]): no stat_id is available for statistics collection
Explanation The OSM line card has used up all statistics collection resources. No more resources available for further statistics collection
Recommended Action Reduce number of features configured on this PXF. If conditions warrant, LOG_STD_SH_CMD_ACTION('show platform vtms queue', 'show platform system-drop', 'show platform toaster stats all' from line card)
%CWTLC-3-NULLIFHWIDB : no hwidb (if index [dec])
Explanation CWTLC hwidb pointer is null
Recommended Action Collect the details that triggered the issue, say like any config change, switchover etc and then LOG_STD_SH_CMD_ACTION( 'show idb','show cwan stats' 'show cwan vlans', from Line card)
%CWTLC-3-OLDIOFPGA : Upgrade your I/O FPGA
Explanation Optical Services Module line card has a downlevel version of the I/O FPGA software
Recommended Action Contact your Cisco technical support representative to upgrade your I/O FPGA to the latest version in your hardware
%CWTLC-3-PLIM_TX : [chars]
Explanation The OSM line card encountered an FPGA error that caused a sequence error. The line card will attempt to recover from the error.
Recommended Action If the recovery was successful, no action is required. if system doesnt recover, Collect the configuration, traffic parameter and event that triggered the issue and LOG_STD_SH_CMD_ACTION('show platform atm vc', 'show controllers' from the line card)
%CWTLC-3-PORTERROR : Port control error, cmd=[chars], port=[dec]
Explanation Port control command function failed. This may be problem with auto negotiation or may be a hardware issue
Recommended Action LOG_STD_SH_CMD_ACTION( 'sh platform hardware gt48520 registers', in line card console)
%CWTLC-3-SECPAIRINT : Unexpected VA/Toaster interrupt from second pair
Explanation The Optical Services Module line card has experienced an unexpected interrupt.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%CWTLC-3-TMC_STATID_INCONSISTENCY : PXF([dec]):Inconsistent stats id([hex]) [int] packets dropped.
Explanation WAN line card had received inconsistent statistics from PXF. PXF reported that a packets has been dropped, but did not report the packet count corresponding to that packet count.
Recommended Action LOG_STD_SH_CMD_ACTION('show platform vtms queue', 'show platform system-drop', 'show platform toaster stats all' from line card)
%CWTLC-3-TMTRIE_ALLOC_FAILED : Failed to allocate toaster mtrie nodes.
Explanation The system encountered an error while it was attempting to allocate memory from a WAN Optical Services Module component.
Recommended Action Try reducing the number of routes associated with a a VRF identifier or upgrade the WAN Optical Services Module to a higher version.
%CWTLC-3-UNSUPPORTED_LABEL_RANGE : The maximum label range configured for this system exceeds the [int] limit supported by the OSM module.
Explanation The MPLS label range configured for this system is not supported. The maximum label range limit is specified in the message.
Recommended Action Change the maximum MPLS label range by entering the <CmdBold>mpls label range<NoCmdBold> command.
%CWTLC-3-VTMS : [chars]
Explanation The OSM line card could not schedule the wheel entry. The reasons for the error are specified in the error message text.
Recommended Action LOG_STD_SH_CMD_ACTION('show platform vtms queue', 'show platform vtms queue detail', 'show platform vtms schedule-wheel', 'show platform vtms calculate-rate row', 'show platform toaster buffers' from line card at least twice at a interval of 30 sec.)
%CWTLC-3-VTMSQ_NOTIDLE : Queue not idle when modifying Q([hex])
Explanation The VTMS queue was in the process of being modified for a change in QoS configuration, but packets are still going through the queue. Traffic in the queue when the queue is being modified is unexpected.
Recommended Action LOG_STD_SH_CMD_ACTION('show platform vtms queue', 'show platform vtms queue detail', 'show platform toaster buffers from line card and 'show policy-map interface' from RP)
%CWTLC-4-ASIC_RESET : Reset asics -[chars]
Explanation The ASICs on the OSM line card are resetting. System traffic should recover and continue normally after reset.
Recommended Action No action is required.
%CWTLC-4-FABRICCRCERRORS : [dec] Fabric crc error events in 100ms period
Explanation The ASIC that is the interface between the line card local switch bus and the switch fabric encountered more CRC errors than the Supervisor CRC error threshold allows. The number of CRC errors is specified in the message. The supervisor engine records these CRC errors.
Recommended Action No action is required. If you want to display the CRC errors, enter the <CmdBold>show fabric errors<NoCmdBold> command
%CWTLC-4-FABRICSYNCERRS : [dec] Fabric sync error events in 100ms period
Explanation The CWTLC Cross Bar Switch Fabric interface encountered more sync error events than the Supervisor sync error threshold allows.
Recommended Action The linecard has notified the Supervisor and the fabric interface will be re-sync'ed. No action is required from the user.
%CWTLC-4-FABRICSYNC_REQ : Fabric resync requested due to [dec] fabric errors in last 100ms
Explanation The CWTLC Cross Bar Switch Fabric interface encountered more sync error events than the Supervisor sync error threshold allows.
Recommended Action The linecard has notified the Supervisor and the fabric interface will be re-sync'ed. No action is required from the user.
%CWTLC-4-PORT_ASIC_OLDIOFPGA : Link negotiation maybe be affected, upgrade I/O FPGA
Explanation A downlevel version of the I/O FPGA has been detected. This needs to be upgraded to the latest version.
Recommended Action Upgrade the I/O FPGA to the newest version. If you require assistance, LOG_STD_SH_TECH_ACTION
%CWTLC-4-TMC_INVALID_STATID : PXF:Invalid-Statid ([dec]) for vc [int]nder interface [int]
Explanation The OSM line card has encountered an internal error while setting up the stats system
Recommended Action LOG_STD_SH_CMD_ACTION('show platform vtms queue', 'show platform system-drop', 'show platform toaster stats all' from line card)
%CWTLC-5-BUS_SEQ_ERR : Constellation bus Sequence Error. Resetting port ASICS.
Explanation The SP has detected a sequence error on the backplane bus of the OSM. A reset sequence from the EARL has been called to recover from this error. System traffic should recover and continue normally.
Recommended Action If traffic recovers, no action is required. Otherwise, LOG_STD_SH_TECH_ACTION
%CWTLC-5-DATAPATH_RECOVERY_PATCH : EARL reset patch invoked.
Explanation The ASICs on the OSM line card has been reset so that it can recover from constellation bus sequence error. This condition is usually occurred under stress traffic with HA-related switchover or a line card OIR operation. System traffic should recover and continue normally.
Recommended Action If traffic recovers, no action is required. Otherwise, LOG_STD_SH_TECH_ACTION
%CWTLC-5-FABRIC_INTERFACE_ASIC_RE_INIT : Fabric Interface Asic Re-initialize.
Explanation The OSM Fabric Interface ASIC is being re-initialized because of system backplane bus sequence error or fatal asic error or on Line card itself.
Recommended Action No action is required if traffic recovers. Otherwise, LOG_STD_SH_CMD_ACTION('show platform hardware medusa registers', 'show platform hardware medusa interrupt', from line card)
%CWTLC-5-PENDING_PATCH : Invoke pending data recovery patch.
Explanation The ASICs on the OSM line card has been reset so that it can recover from backplane switching bus sequence errors or local hardware ASIC errors. This condition is usually occurred under stress traffic with HA-related switchover or a line card OIR operation. System traffic should recover and continue normally.
Recommended Action If traffic recovers, no action is required. Otherwise, LOG_STD_SH_TECH_ACTION
%CWTLC-6-FABRIC_INTERFACE_ASIC_MODECHANGE : Fabric Interface Asic switching bus Mode changed to [chars]
Explanation The Supervisor has changed the CWTLC Fabric Interface Asic switching bus mode.
Recommended Action No action is required from the user.
%CWTLC-6-TMC_NULLQID : PXF([dec]):Null-QID ([chars]) [int] packets dropped.
Explanation Constellation line card had encountered invalid queue. The packet has been dropped. The packet will be counted in the null queue statistics. Packet traffic should continue normally.
Recommended Action LOG_STD_SH_CMD_ACTION('show platform vtms queue', 'show platform system-drop', 'show platform toaster stats all' from line card)
D
DATACORRUPTION
%DATACORRUPTION-1-DATAINCONSISTENCY : [chars], -PC= 0x[chars]
Explanation Software has detected that some internal data structures may be corrupt. This may lead to unpredictable device operation; including, but not limited to, unexpected reloads or spurious memory accesses. This detection is a proactive check for operating system consistency.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
DATA_DESCR
%DATA_DESCR-3-CTRLR_DECODE : Lookup Failure: %0-8x.%0-8x.%0-8x.%0-8x.%0-8x ([int]-[int]/[int])
Explanation Data descriptors are used to encode an interface index in a compact fashion for transfer between redundant route processor units. An interface corresponding to a data descriptor index was not found on the Standby unit when it was looked up. The failure most likely occurred because of a software error. The numeric error code in the message output identifies the failing data descriptor index. The system state between the Active and Standby units might not be properly synchronized.
Recommended Action Gather system logs and error messages at both the active and the standby units. Issue the recommended show commands at the active unit. LOG_STD_SH_CMD_ACTION(show data-descriptor controller)
%DATA_DESCR-3-DEFER_FAILURE : Defer failure on [chars] for descriptor [int]-[int]/[int]/[int]/[int]
Explanation Data descriptors are used to encode an interface index in a compact fashion for transfer between redundant route processor units. An error occurred during the processing of a data descriptor. The failure most likely occurred because of a software error. The numeric error code in the message output identifies the failing data descriptor index. The system state between the Active and Standby units might not be properly synchronized.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DATA_DESCR-3-ENTRY_EXPIRED : Found expired message entry for descriptor [int]-[int]/[int]/[int]/[int]
Explanation Data descriptors are used to encode an interface index in a compact fashion for transfer between redundant route processor units. An error occurred during the processing of a data descriptor. The failure most likely occurred because of a software error. The numeric error code in the message output identifies the failing data descriptor index. The system state between the Active and Standby units might not be properly synchronized.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DATA_DESCR-3-GENERIC_DECODE : Lookup Failure: %0-8x.%0-8x.%0-8x.%0-8x.%0-8x ([int]-[int]/[int]/[int]/[int]/[int])
Explanation Data descriptors are used to encode an interface index in a compact fashion for transfer between redundant route processor units. An interface corresponding to a data descriptor index was not found on the Standby unit when it was looked up. The failure most likely occurred because of a software error. The numeric error code in the message output identifies the failing data descriptor index. The system state between the Active and Standby units might not be properly synchronized.
Recommended Action Gather system logs and error messages at both the active and the standby units. Issue the recommended show commands at the active unit. LOG_STD_SH_CMD_ACTION(show data-descriptor [hwidb|swidb|controller])
%DATA_DESCR-3-GENERIC_ENCODE : Encode failure: [chars], descriptor type=[dec]
Explanation An internal data descriptor could not be encoded for synchronization for the interface or controller in the run-time module specified in the message output. The failure most likely occurred because of a software error. The descriptor type specified in the message output identifies the type of failure. The system state between the active and standby units might not be properly synchronized.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DATA_DESCR-3-GENERIC_VIRTUAL_DECODE : Lookup Failure: %0-8x.%0-8x.%0-8x.%0-8x.%0-8x ([int]-[int]/[int]/[int])
Explanation Data descriptors are used to encode an interface index in a compact fashion for transfer between redundant route processor units. An interface corresponding to a data descriptor index was not found on the Standby unit when it was looked up. The failure most likely occurred because of a software error. The numeric error code in the message output identifies the failing data descriptor index. The system state between the Active and Standby units might not be properly synchronized.
Recommended Action Gather system logs and error messages at both the active and the standby units. Issue the recommended show commands at the active unit. LOG_STD_SH_CMD_ACTION(show data-descriptor [hwidb|swidb])
%DATA_DESCR-3-HWIDB_DECODE : Lookup Failure: %0-8x.%0-8x.%0-8x.%0-8x.%0-8x ([int]-[int]/[int]/[int]/[int])
Explanation Data descriptors are used to encode an interface index in a compact fashion for transfer between redundant route processor units. An interface corresponding to a data descriptor index was not found on the Standby unit when it was looked up. The failure most likely occurred because of a software error. The numeric error code in the message output identifies the failing data descriptor index. The system state between the Active and Standby units might not be properly synchronized.
Recommended Action Gather system logs and error messages at both the active and the standby units. Issue the recommended show commands at the active unit. LOG_STD_SH_CMD_ACTION(show data-descriptor hwidb)
%DATA_DESCR-3-QUEUE_INTERNAL_ERROR : Internal error on data descriptor queue: [chars]
Explanation Data descriptors are used to encode an interface index in a compact fashion for transfer between redundant route processor units. An error occurred during the processing of a data descriptor. The failure most likely occurred because of a software error. The numeric error code in the message output identifies the failing data descriptor index. The system state between the Active and Standby units might not be properly synchronized.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DATA_DESCR-3-SWIDB_DECODE : Lookup Failure: %0-8x.%0-8x.%0-8x.%0-8x.%0-8x ([int]-[int]/[int]/[int]/[int]/[int])
Explanation Data descriptors are used to encode an interface index in a compact fashion for transfer between redundant route processor units. An interface corresponding to a data descriptor index was not found on the Standby unit when it was looked up. The failure most likely occurred because of a software error. The numeric error code in the message output identifies the failing data descriptor index. The system state between the Active and Standby units might not be properly synchronized.
Recommended Action Gather system logs and error messages at both the active and the standby units. Issue the recommended show commands at the active unit. LOG_STD_SH_CMD_ACTION(show data-descriptor swidb)
DBAL
%DBAL-3-MQIPC_EVENTLOSS :
Explanation MQIPC event notifying of non-empty queue not delivered to DBAL
Recommended Action Report this occurance to Cisco TAC
DC
%DC-3-BUILTIN_INIT_FAIL : [chars]
Explanation Initilization of Device classifier Built-in database failed. So the device classifier will be operationally down.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DC-3-CHECK_INIT_FAIL : [chars]
Explanation Loading of the Checks databae in Device classifier failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DC-3-DB_INIT_FAIL : Device Classifier disabled. [chars] initialization failed
Explanation Initilization of Device classifier Internal database failed So the device classifier will be operationally down.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DC-3-DC_DISABLED : [chars].
Explanation The device classifier is disabled due to an error condition encountered during initialization or parsing the profiles
Recommended Action The specified error message is logged. After the error condition is resolved re-enable the device classifier
%DC-3-DISABLE_FAIL : Failed to disable DC.
Explanation Internal error occured trying to disable Device Classifier.
Recommended Action Please run the command: show macro auto monitor clients and try disabling the clients
%DC-3-ENABLE_FAIL : Failed to enable DC.
Explanation Internal error occured trying to enable Device Classifier.
Recommended Action Please check the previous DC error messages and take the relevant action
%DC-3-FILE_CHECKSUM : Checksum [chars] failed for the profile file: [chars]
Explanation Checksum computation or verification failed for the profiles file. The profiles in the errored file cannot be loaded into the device classifier.
Recommended Action None
%DC-3-FILE_READ_ERROR : Error [chars] the profile file: [chars]
Explanation There was an error reading the profile file contents. The profiles in the errored file cannot be loaded into the device classifier.
Recommended Action None
%DC-3-HRPC_SYNC : Error on member switch [dec], error_code = [dec]
Explanation Internal error occured while trying to sync Device Classifier.state
Recommended Action Please check the state of the stack members
%DC-3-INCOMPATIBLE_PROFILE_VERSION : Incompatible version of Profile detected in [chars]. Expected version:[dec], Version found:[dec]
Explanation An incompatible profile version is detected. The device classifier feature will be operationally down.
Recommended Action Reload the expected version of device profiles file to the system and re-enable the device classifier
%DC-3-MAX_OUI_EXCEEDED : [chars].
Explanation The maximum number of OUI codes that can be defined in device profiles exceeded the maximum limit. The device classifier will be operationally down if failure occured for the Embedded profiles.
Recommended Action Reduce the number of rules in the device profiles file and reload it into the system and re-enable the device classifier
%DC-3-MAX_PROFILES_EXCEEDED : [chars].
Explanation The maximum number of profiles that can be defined in device profiles exceeded the maximum limit. The device classifier will be operationally down if failure occured for the Embedded profiles.
Recommended Action Reduce the number of rules in the device profiles file and reload it into the system and re-enable the device classifier
%DC-3-MAX_RULES_EXCEEDED : [chars].
Explanation The maximum number of rules that can be defined in device profiles exceeded the maximum limit. The device classifier will be operationally down if failure occured for the Embedded profiles.
Recommended Action Reduce the number of rules in the device profiles file and reload it into the system and re-enable the device classifier
%DC-3-NO_MEM : [chars].
Explanation There is no memory left to allocate in the system The device classifier will be operationally down if failure occured for the Embedded profiles.
Recommended Action Increase the memory size in the system and re-enable the device classifier
%DC-3-OUI_INIT_FAIL : OUI Table initialization failed for [chars]
Explanation Loading of the OUI databae in Device classifier failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DC-3-PATTERN_NOT_FOUND : [chars]
Explanation The device profiles file parsing failed. This indicates that the file may be corrupt. The device classifier will be operationally down if failure occured for the Embedded profiles.
Recommended Action Reload the Device Profiles file to the flash and re-enable the device classifier
%DC-3-SM_API : [chars] return [chars].
Explanation Internal error returned by Session Manager api.
Recommended Action None
%DC-3-SM_GET : Failed to get [chars].
Explanation Internal error occured during communication with Session Manager. This may cause the show command not to display the device classification results.
Recommended Action None
%DC-3-SM_INIT_FAIL : Device Classifier disabled. [chars] initialization failed
Explanation Registraton of Device classifier with SM failed. So the device classifier will be operationally down.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DC-3-SM_UPDATE : Failed to update [chars].
Explanation Internal error occured during device classification . This may cause the device to be unknown.
Recommended Action None
%DC-4-FILE_OPEN_WARNING : Not able to open [chars]
Explanation The device classifier did not find the default profile file or it may be corrupted. DC is working using built-in profiles.
Recommended Action Perform archive download using the tar bundle image to install the profile file in the flash. Reload the switch with the image to see the warning message is gone.
%DC-6-DEFAULT_INIT_INFO : [chars]
Explanation The default profiles are not loaded and those devices will not be classified. Device classifier will continue to work with built-in profiles.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
DFP
%DFP-4-AGENT_NOT_FOUND : [chars] Service has not been registered with DFP.
Explanation No such service registered with DFP subystem.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%DFP-4-BAD_LISTEN : Service [chars] -Listen failed
Explanation Listen for DFP Manager failed.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%DFP-4-BAD_POINTER : [chars] Application did not set pointer
Explanation Application passed invalid pointer to DFP subsystem
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%DFP-4-BAD_SEND : Manager [IP_address]:[int] -Send failed
Explanation Sending a message to DFP Manager failed
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%DFP-4-BIND_FAIL : Failure binding port [int] to socket for service [chars].
Explanation Problem with call to socket bind.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%DFP-4-ENQUEUE : Process enqueue failed: [chars]
Explanation An unexpected error occurred while enqueueing a DFP element
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%DFP-4-NO_PARSE : Manager [IP_address]: Service [chars] -Could not parse message
Explanation Could not parse message from DFP Manager
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%DFP-4-NO_PROCESS_START : Could not start process for service [chars]
Explanation Could not start DFP Process for service %s
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%DFP-4-NO_QUEUE_REQUEST : Could not queue request for [chars] for service [chars]
Explanation Could not queue request to the DFP process for specific action
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%DFP-4-NUM_TOO_LARGE : [chars] Application sent too many values
Explanation Application sent too many values to DFP subsystem
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%DFP-4-PACKET_TOO_SMALL : The DFP packet is too small from manager [IP_address] service [chars].
Explanation A DFP packet has been received that is too small.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%DFP-4-READ_ERR : Manager [IP_address]: Service [chars] -Too many read errors
Explanation Too many errors reading message header from DFP Manager
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%DFP-4-REPEAT_SERVICE_INIT : Service [chars] is already intialized, cannot re-initialize
Explanation The application has atempted to re-initialize a service
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%DFP-4-SECURITY_FAIL : [chars] security information in CASA packet from manager [IP_address] service [chars].
Explanation Security check failed.
Recommended Action Make sure all CASA/DFP systems are configured with the same password.
%DFP-4-SOCK_ERR : Manager [IP_address]: Service [chars] -Socket_recv error [dec]
Explanation Socket_recv error receiving message from DFP Manager
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%DFP-4-STRING_TOO_LONG : The string [chars] exceeds 15 characters -too long for service name.
Explanation The user input a service string that exceeds 15 characters
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%DFP-4-SUBSYS_NOT_UP : Service [chars] -attempted to register before DFP Subsytem is up.
Explanation Problem with order of subsystem initialization.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%DFP-4-UKN_CON : Manager [IP_address] Service [chars] -Unknown connection state [int]
Explanation Unknown connection state processing DFP timer
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%DFP-4-UNK_TYPE : Manager [IP_address]: Service [chars] -Unknown message type [int]
Explanation Message from DFP Manager has unknown type
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
DHCP
%DHCP-3-HA_INIT_FAIL : Function [chars] in DHCP client failed to initialize: [chars]
Explanation A high availability related function in the DHCP client failed to initialize properly. If you are using a platform with a redundant processor or box-to-box redundancy, DHCP client settings may fail to be preserved if the main processor fails forcing use of the standby.
Recommended Action Please contact the TAC for assistance.
%DHCP-5-RESTART : Interface [chars] is being restarted by DHCP
Explanation DHCP is restarting the interface.
Recommended Action No action is required.
%DHCP-6-ADDRESS_ASSIGN : Interface [chars] assigned DHCP address [IP_address], mask [IP_address], hostname [chars]
Explanation The interface has been allocated an address via DHCP
Recommended Action This is an informational message. No action is required
DHCPD
%DHCPD-2-HA_INSUFFICIENT_BUFFER : DHCP insufficient buffer; information is not synced to Standby.
Explanation Reason for failure is unknown.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%DHCPD-2-MALLOC_ERROR : There is inadequate memory for DHCP services.
Explanation DHCP could not allocate mandatory data structures.
Recommended Action Add more memory.
%DHCPD-2-NO_PROCESS : DHCP could not start its [chars] process.
Explanation DHCP could not start one of its processes.
Recommended Action Add more memory.
%DHCPD-2-READ_DEADLOCK : DHCP has detected a deadlock condition (excessive read failures).
Explanation The DHCP server could not read bindings from any database agent. All read attempts have failed. To prevent a possible deadlock, the server has made all pool addresses available for assignment.
Recommended Action Verify that all URLs are correct and connectivity exists between the server and all database agents. Check for corrupt database files. All files must contain the *time* and *end* keywords. Execute the command, show ip dhcp database. If there are aborted file transfers, increase the appropriate timeouts. Restart the DHCP server.
%DHCPD-2-RECVMSG_ERROR : Recvmsg failed unexpectedly. DHCP services have been terminated.
Explanation Reason for failure is unknown.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%DHCPD-2-SOCKET_ERROR : DHCP could not open UDP port [int].
Explanation DHCP could not open UDP port 67 (bootps).
Recommended Action Check if another application is using UDP port 67. If the port is available, add more memory.
%DHCPD-3-HA_INIT_FAIL : Function [chars] in DHCP server failed to initialize: [chars]
Explanation A high availability related function in the DHCP server failed to initialize properly. If you are using a platform with a redundant processor or box-to-box redundancy, DHCP server data may fail to be preserved if the main processor fails forcing use of the standby.
Recommended Action Please contact the TAC for assistance.
%DHCPD-3-NO_AAA_CONTEXT : AAA configured, but no AAA context in [chars]
Explanation DHCP is attempting to use AAA to grant a DHCP lease, but no AAA context is associated with the binding
Recommended Action Please contact the TAC for assistance.
%DHCPD-3-READ_ERROR : DHCP could not read bindings from [chars].
Explanation The DHCP server could not read bindings from the specified database agent.
Recommended Action Verify that the URL is correct and connectivity exists between the server and database agent. Check for a corrupt database file. The file must contain the *time* and *end* keywords. Execute the command, show ip dhcp database. If there are aborted file transfers, increase the database transfer timeout.
%DHCPD-3-WRITE_ERROR : DHCP could not write bindings to [chars].
Explanation The DHCP server could not write bindings to the specified database agent.
Recommended Action Verify that the URL is correct and connectivity exists between the server and database agent. Execute the command, show ip dhcp database. If there are aborted file transfers, increase the database transfer timeout.
%DHCPD-4-DECLINE_CONFLICT : DHCP address conflict: client [chars] declined [IP_address].
Explanation The DHCP client has detected an address conflict. Another host is using the specified IP address. After resolving the conflict, execute the command, clear ip dhcp conflict.
Recommended Action Resolve the misconfiguration. Clear the conflict from the DHCP database.
%DHCPD-4-HA_CONFIG_MISMATCH : DHCP pool [chars] configuration on Active is not matched on the Standby.
Explanation The software has detected a possible DHCP configuration mismatch on the Active and Standby units. Please verify that the configuration on the Standby matches that of the Active.
Recommended Action Resolve the misconfiguration.
%DHCPD-4-PING_CONFLICT : DHCP address conflict: server pinged [IP_address].
Explanation The DHCP server has detected an address conflict. Another host is using the specified IP address. After resolving the conflict, execute the command, clear ip dhcp conflict.
Recommended Action Resolve the misconfiguration. Clear the conflict from the DHCP database.
%DHCPD-4-RELAY_ONLY : DHCP will run as a relay agent only.
Explanation DHCP could not start its database process. The server component has been disabled. Only the relay agent is active.
Recommended Action Add more memory.
%DHCPD-6-HIGH_UTIL : Pool [chars] is in high utilization state ([int] addresses used out of [int]). Threshold set at [int]%%.
Explanation The pool's utilization has exceeded the user configured high watermark.
Recommended Action Examine the DHCP pool and determine if the pool needs more IP addresses than currently allocated.
%DHCPD-6-LOW_UTIL : Pool [chars] is in low utilization state ([int] addresses used out of [int]). Threshold set at [int]%%.
Explanation The pool's utilization has fallen below the user configured high watermark.
Recommended Action Examine the DHCP pool and determine if the pool needs more IP addresses than currently allocated.
DHCPV6C
%DHCPV6C-3-NOPACKET : Cannot setup or duplicate a socket packet
Explanation Most likely a resource problem within the system.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
%DHCPV6C-3-NOSOCKET : Cannot create DHCPv6 client socket
Explanation Most likely no IP enabled on any interface or a resource problem within the system.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
%DHCPV6C-4-ZEROXID : Calculated DHCPv6 Lease Query xid is zero. Nothing is wrong, just drop the LQv6 msg
Explanation After multiple tries, the generated LQv6 msg xid is zero by accident. Just drop the LQv6 msg.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
DHCPV6R
%DHCPV6R-3-INVALID_USR_LINKADDR : Invalid user specified link-address [IPV6 address] idb [chars] in ipv6 dhcp relay CLI. Removing user specified invalid address from the CLI.
Explanation Invalid link-address has been provisioned in the ipv6 relay destination CLI.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
%DHCPV6R-3-INVALID_USR_SRCADDR : Invalid user specified source-address [IPV6 address] idb [chars] in ipv6 dhcp relay CLI. Removing user specified invalid address from the CLI and auto-computing source with SAS.
Explanation Invalid source-address has been provisioned in the ipv6 relay destination CLI.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
DHCPV6S
%DHCPV6S-3-DBNOTLOADED : Binding database not loaded
Explanation Fail to load the DHCPv6 binding database.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DHCPV6S-3-DBOPEN : Openning [chars]: [chars]
Explanation Fail to open a DHCPv6 binding database file.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DHCPV6S-3-DBREAD : Reading file: [chars]
Explanation Fail to read a DHCPv6 binding database file.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DHCPV6S-3-DBWRITE : Writing file: [chars]
Explanation Fail to write a DHCPv6 binding database file.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DHCPV6S-3-NOPACKET : Cannot setup or duplicate a DHCPv6 server socket packet
Explanation Most likely a resource problem within the system.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
DIALER
%DIALER-2-CIRCUITCOUNT : Dialer count 0 on [chars]
Explanation An internal software error occurred.
Recommended Action LOG_STD_SH_TECH_ACTION
%DIALER-2-NOSWIDB : No software interface associated with hw interface [chars]
Explanation An internal software error occurred.
Recommended Action Call your technical support representative and report the error message, the system version, and the router configuration. (Use the show version command to obtain the software version.)
%DIALER-2-NULLPTR : Unexpected null pointer in [chars]
Explanation An internal software error occurred.
Recommended Action LOG_STD_SH_TECH_ACTION
%DIALER-3-SBINIT : Error initializing [chars] subblock data structure. [chars]
Explanation Initialization of the specified subblock data structure could not be accomplished.
Recommended Action LOG_STD_ACTION
%DIALER-4-MTU_WARNING : Current MTU setting of [dec] on [chars] is being overwritten by setting of [dec] defined by [chars].
Explanation This is a warning message indicating that an interface setting is changed based on a dialer rotary group memebership.
Recommended Action LOG_STD_NO_ACTION
%DIALER-6-BIND : Interface [chars] bound to profile [chars]
Explanation This is a status message indicating that a dialer interface has been bound to a dialer profile.
Recommended Action LOG_STD_NO_ACTION
%DIALER-6-UNBIND : Interface [chars] unbound from profile [chars]
Explanation This is a status message indicating that a dialer interface has been unbound to a dialer profile.
Recommended Action LOG_STD_NO_ACTION
DIALER_LIST_PROXY
%DIALER_LIST_PROXY-3-PROXY_ALLOC_PAK_FAILED : alloc pak failed, MSGDEF_LIMIT_MEDIUM
Explanation alloc pak failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DIALER_LIST_PROXY-3-PROXY_IPC_FAILED : [chars] failed to send ipc rc: [int]
Explanation send ipc failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DIALER_LIST_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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DIALER_LIST_PROXY-3-PROXY_MEM_EXTEND_FAILED : IPC subtype: [dec]
Explanation add more memory failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DIALER_LIST_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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DIALER_LIST_PROXY-4-PROXY_IPC_INVALID_MSG_LEN : [dec]:[dec] len [dec] flags [hex] source [dec]
Explanation Invalid IPC message length.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
DIALPEER_DB
%DIALPEER_DB-3-ADDPEER_MEM_THRESHOLD : Addition of dial-peers limited by available memory
Explanation The available memory does not permit the addition of more dial-peers.
Recommended Action Increase the processor memory in order to be able to add more dialpeers.
%DIALPEER_DB-3-ADDPEER_PLATFORM_LIMIT : Addition of dial-peers limited by platform
Explanation This platform does not permit the addition of more dial-peers.
Recommended Action Reduce the number of dial-peers in your numbering plan.
%DIALPEER_DB-3-DIALPEER_ACCOUNTING : Connections for dial-peer [dec] is negative. Resetting connections to 0.
Explanation Active Connections for dial-peer is negative.
Recommended Action Verify if dial-peers were removed with active calls associated to them and added back while the calls were still connected.
%DIALPEER_DB-3-DP_MALLOC_FAIL : Could not allocate memory in [chars] for tag [dec]
Explanation Ran out of memory
Recommended Action Observe why memory is exhausted
%DIALPEER_DB-3-NOMAP : Could not load dnis-map [chars] url=[chars] errno=[dec]=[chars]
Explanation Could not read in the dnis-map
Recommended Action Check that map exists on the server, and is readable.
%DIALPEER_DB-6-ADDPEER_WARNING : Addition of too many dial-peers may affect performance
Explanation The number of dial-peers is high. This will have an effect on the dial-peer lookup time, resulting in longer call setup time.
Recommended Action Use the minimum number of dial-peers necessary for your numbering plan.
%DIALPEER_DB-6-FB_ENTRY_NOT_CREATED : Could not create probe for tag [dec]
Explanation Fallback cache full
Recommended Action Increase Fallaback cache size
DLC
%DLC-2-NOMEMORY : no memory for [chars]
Explanation There was not enough free memory to complete the operation.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DLC-3-BADPARAM : Function [chars]: value [hex] passed in parameter [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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DLC-3-INVPCEP : Close Station, invalid P_CEP
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DLC-3-WPUTERR : unknown port type [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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
DLINK
%DLINK-3-BAD_QELEM : Bad queue elem -[hex]: flink [hex], blink [hex] , flink->blink [hex], blink->flink [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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%DLINK-3-NULL_QELEM : Null queue elem
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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
DLSWC
%DLSWC-3-BADCLSI : [chars] primitive not valid for dlsw [chars] [chars]
Explanation A data-link switching system error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DLSWC-3-BADCLSICNF : [chars] Invalid confirm [chars] [chars]
Explanation A data-link switching system error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DLSWC-3-BADCLSIIND : [chars] Invalid indication [chars], [chars]
Explanation A data-link switching system error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DLSWC-3-BADCLSIRET : [chars] Invalid ret code ([hex]) [chars], [chars]
Explanation A data-link switching system error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DLSWC-3-BADCLSISAP : [chars] Bad clsi SAP id = [hex] [chars]
Explanation A data-link switching system error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DLSWC-3-BADPEEROP : bad peer op in peer_to_core [dec]
Explanation A data-link switching system error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DLSWC-3-BADSSPHDR : bad ssp hdr in proc ssp -[chars] = [hex]
Explanation A Silicon Switch Processor (SSP) header received from the remote peer contains errors in one of the fields.
Recommended Action If the remote peer is a nonCisco router, confirm that it supports the DLSw RFC 1795 standard.
%DLSWC-3-IDMGR : [chars]
Explanation A data-link switching system error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DLSWC-3-NODLSW : [chars] [dec]
Explanation A data-link switching system error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DLSWC-3-NOPEER : [chars]
Explanation A data-link switching system error occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%DLSWC-3-RECVSSP : SSP OP = [dec]([chars]) [chars] from [chars]
Explanation A Silicon Switch Program (SSP) frame was received from the remote peer.
Recommended Action No action is required.
%DLSWC-3-SENDSSP : SSP OP = [dec]([chars]) [chars] to [chars] [chars]
Explanation A Silicon Switch Program (SSP) frame was sent to the remote peer.
Recommended Action No action is required.
DLSWMasterSlave
%DLSWMasterSlave-3-DLSWMS : [chars]
Explanation DLSw Master-Slave Error
Recommended Action No action is required.
%DLSWMasterSlave-3-DLSWMSCSM : [chars], [chars]
Explanation DLSw Master-Slave Error
Recommended Action No action is required.
%DLSWMasterSlave-3-DLSWMSDLX : [chars] [hex] from [enet]
Explanation DLSw Master-Slave Error
Recommended Action No action is required.
%DLSWMasterSlave-3-DLSWMSFSM : [chars]: [chars] from [enet]
Explanation DLSw Master-Slave Error
Recommended Action No action is required.
%DLSWMasterSlave-3-DLSWMSRCV : [chars] from [enet]
Explanation DLSw Master-Slave Error
Recommended Action No action is required.
%DLSWMasterSlave-3-DLSWMSSAP : [chars]: [chars]
Explanation DLSw Master-Slave Error
Recommended Action No action is required.
%DLSWMasterSlave-3-DLSWMSTX : [chars]: [chars] to [enet]
Explanation DLSw Master-Slave Error
Recommended Action No action is required.
DLSWP
%DLSWP-3-PBADVALUE : [chars]: invalid [chars] [dec]
Explanation A bad parameter value was passed to function chars1 - invalid parameter chars2 with value. This error should not cause any network problems unless it happens repeatedly.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DLSWP-3-PCAPMISMATCH : [chars]: [chars]
Explanation Priority keyword was used on one router but not on the other. The priority keyword is an option on the DLSW remote peer definition. If priority keyword is used on one router, it must be used on the other.
Recommended Action If you wish to use prioritization, use it on both routers.
%DLSWP-3-PEERFAILURE : [chars] [chars]
Explanation A DLSW peer failed: - keepalive failure, dlsw between cisco peers is sending a peer keepalive by default every 30 sec. After missing 3 consecutive keepalives the peer is taken down. - We are not promiscuous, Rej conn from peer a.b.c.d The local dlsw peer is not configured for promiscuous and we receive a request to open a dlsw peer for which we have no corresponding dlsw remote peer statement. - received tcp fini, dlsw peer code has received a tcp fini from the underlaying tcp subsystem. To obey the tcp fini dlsw wring bring down the peer connection for which the tcp fini was received.
Recommended Action - keepalive failure Check end to end connectivity between the DLSW peers - We are not promiscuous, Rej conn from peer a.b.c.d correct your configuration. - received tcp fini, Check the underlaying tcp connection between the two dlsw peers.
%DLSWP-3-PGENERAL : [chars]
Explanation A general error condition was detected as described in the message text. This error should not cause any network problems unless it happens repeatedly.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DLSWP-3-PLFCHANGE : [chars] [dec]; [chars]
Explanation The largest frame size configured in the DLSW remote peer definition is being changed because the MTU size configured on the interface, used by DLSW, is less than the configured value of the largest frame on DLSW remote peer definition. The largest frame size is being changed to that configured on the interface.
Recommended Action If you wish to use this largest frame size for DLSW, increase the MTU on the interface to a value larger than the configured largest frame size.
%DLSWP-3-PNOCOOKIE : uninitalized peer [chars] from [IP_address]([dec]) to [IP_address]([dec])
Explanation DLSw received a packet on an uninitialized peer connection.
Recommended Action Verify configuration and DLSw peer status on both routers.
%DLSWP-3-PNOMEM : No memory to [chars]
Explanation The router ran out of system memory for operation, as described in the message text. Most likely, the router image requires more system memory (RAM) than the router contains.
Recommended Action Consult with your Cisco technical support representative about memory requirements for a specific image.
%DLSWP-3-PPASSIVE : passive open failed from [IP_address]([dec]) -> [dec]
Explanation The system does not have enough main memory (RAM) for TCP to allocate the data structures required to accept an incoming TCP connection. Most likely, the router image requires more system memory (RAM) than the router contains.
Recommended Action Consult with your Cisco technical support representative about memory requirements for a specific image.
%DLSWP-5-PEERUPDOWN : [chars] [chars]
Explanation A DLSW peer is either connected or disconnected
Recommended Action None, informational message only.
DMI
%DMI-2-CDB_MAN_SUB_FAIL :
Explanation A Confd error has occurred attempting to mark DMI as a mandatory subscriber
Recommended Action Stop and restart netconf-yang.
%DMI-2-CHG_VRF_FAIL :
Explanation The DMI application failed to set the correct virtual routing and forwarding network thus, it cannot communicate with Confd.
Recommended Action Stop and restart netconf-yang.
%DMI-2-CLI_CHANNEL_CLOSED :
Explanation The CLI engine event channel to the network element closed unexpectedly.
Recommended Action DMI will reset. No action necessary.
%DMI-2-CONFD_CB_REG_DONE_FAIL :
Explanation A DMI application cannot complete callback registration with Confd.
Recommended Action Stop and restart netconf-yang.
%DMI-2-CONFD_CB_REG_FAIL :
Explanation A DMI application cannot register a particular callback with Confd.
Recommended Action Stop and restart netconf-yang.
%DMI-2-CONFD_CONNECT_FAIL :
Explanation A DMI application cannot connect to Confd via a particular socket type.
Recommended Action Stop and restart netconf-yang.
%DMI-2-CONFD_INIT_FAIL :
Explanation Confd did not initialize properly.
Recommended Action Back out any recent yang model updates. Stop and restart netconf-yang.
%DMI-2-CONFD_SUB_DONE_FAIL :
Explanation A DMI application cannot complete subscriptions for changes to yang models.
Recommended Action Back out any recent model updates. Stop and restart netconf-yang.
%DMI-2-CONFD_SUB_FAIL :
Explanation A DMI application cannot subscribe for changes to a particular yang model.
Recommended Action Back out any recent model updates. Stop and restart netconf-yang.
%DMI-2-CONTROL_SOCKET_ERROR :
Explanation The control socket connection to Confd has returned an error.
Recommended Action DMI will reset. No action necessary.
%DMI-2-MAAPI_CONNECT_FAIL :
Explanation A Confd error has occurred attempting to connect via MAAPI socket.
Recommended Action Stop and restart netconf-yang.
%DMI-2-MAAPI_WAIT_FAIL :
Explanation Confd did not initialize properly.
Recommended Action Back out any recent yang model updates. Stop and restart netconf-yang.
%DMI-2-NESD_CREATE_FAIL :
Explanation Either an out-of-memory condition has been encountered, or the DMI CLI engine cannot connect to the network element.
Recommended Action Stop and restart netconf-yang.
%DMI-2-NESD_INIT_FAIL :
Explanation The nesd daemon failed to initialize.
Recommended Action Stop and restart netconf-yang.
%DMI-2-NESD_PREHOOK_INIT_FAIL :
Explanation The nesd daemon failed to initialize its component-specific add-ons.
Recommended Action Stop and restart netconf-yang.
%DMI-2-NES_RESET_FAIL :
Explanation The network element synchronizer daemon cannot reset in order to recover from a critical error.
Recommended Action Stop and restart netconf-yang.
%DMI-2-NETCONF_SSH_CRITICAL :
Explanation A critical message from the NETCONF SSH daemon.
Recommended Action Not applicable
%DMI-2-NOTIFICATION_READ_FAIL :
Explanation An attempt to read an event from the Confd notification socket failed.
Recommended Action DMI will reset. No action necessary.
%DMI-2-SD_INIT_FAIL :
Explanation The syncfd daemon failed to initialize.
Recommended Action Stop and restart netconf-yang.
%DMI-2-SD_RESET_FAIL :
Explanation The syncfd daemon cannot reset in order to recover from a critical error.
Recommended Action Stop and restart netconf-yang.
%DMI-2-VTY_SERVER_RESET_FAIL :
Explanation Failed to reset VTY server utility in order to recover from critical error.
Recommended Action Stop and restart netconf-yang.
%DMI-2-WORKER_SOCKET_CLOSED :
Explanation The worker socket connection to Confd has closed unexpectedly.
Recommended Action DMI will reset. No action necessary.
%DMI-2-WORKER_SOCKET_ERROR :
Explanation The worker socket connection to Confd has returned an error.
Recommended Action DMI will reset. No action necessary.
%DMI-3-CDB_ABORT_FAIL :
Explanation A Confd error has occurred attempting to abort a transaction.
Recommended Action Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration.
%DMI-3-CDB_READ_FAIL :
Explanation A Confd error has occurred attempting to read a specific model path from the DMI data store.
Recommended Action Download the model in question from the network element and verify the path exists. Update the model if needed.
%DMI-3-CDB_SET_NAMESPACE_FAIL :
Explanation A Confd error has occurred attempting to set a specific model namespace for accessing the DMI data store.
Recommended Action Stop and restart netconf-yang.
%DMI-3-CDB_START_FAIL :
Explanation A Confd error has occurred attempting to open the DMI data store.
Recommended Action Stop and restart netconf-yang.
%DMI-3-CDB_SYNC_FAIL :
Explanation A Confd error has occurred attempting to sync the subscription socket.
Recommended Action Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration.
%DMI-3-CLI_ENGINE_CONNECT_FAIL :
Explanation DMI cannot connect to the network element in order to interact with its CLI parser.
Recommended Action Check the CLI engine protocol settings.
%DMI-3-CLI_ENGINE_CONNECT_LOSS :
Explanation DMI has lost connection to the network element.
Recommended Action No action necessary.
%DMI-3-CLI_ENGINE_EVENT_FAIL :
Explanation DMI cannot retrieve its CLI engine event in order to interact with the network element CLI parser.
Recommended Action Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration.
%DMI-3-CLI_ENGINE_LOG_LVL_FAIL :
Explanation DMI cannot set its CLI engine logging level.
Recommended Action Stop and restart DMI.
%DMI-3-CLI_ENGINE_POLL_FAIL :
Explanation DMI cannot read its CLI engine results in order to interact with the network element CLI parser.
Recommended Action Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration. If problem continues, stop and restart netconf-yang
%DMI-3-CLI_ENGINE_READ_EVENT_FAIL :
Explanation DMI cannot read its CLI engine event in order to interact with the network element CLI parser.
Recommended Action Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration. If problem continues, stop and restart netconf-yang
%DMI-3-CLI_ENGINE_READ_FAIL :
Explanation DMI cannot read its CLI engine results in order to interact with the network element CLI parser.
Recommended Action Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration.
%DMI-3-CLI_ENGINE_RECONNECT_FAIL :
Explanation The CLI engine has lost its connection to the network element and attempted to reconnect with an error occurred.
Recommended Action Stop and restart netconf-yang.
%DMI-3-CLI_ENGINE_VTY_CREATE_FAIL :
Explanation The DMI CLI engine cannot create a VTY instance.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
%DMI-3-CLI_ENGINE_VTY_OPEN_FAIL :
Explanation The DMI CLI engine cannot open a VTY.
Recommended Action Free up available VTY resources by closing unused VTYs. Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration. If problem continues, stop and restart netconf-yang
%DMI-3-CLI_ENGINE_VTY_TIMEOUT_FAIL :
Explanation DMI disables the VTY timeout for the network element synchronizer's VTY connection to ensure its number cannot be silently claimed by other VTY sessions.
Recommended Action None required
%DMI-3-CLI_ENGINE_WRITE_FAIL :
Explanation A CLI engine error occurred while send a command line to the network element's CLI parser
Recommended Action Enter the command line in question manually via the network element's console or vty. If successful, stop and restart netconf-yang and retry.
%DMI-3-CLI_GEN_FAIL :
Explanation A Confd error has occurred when requesting the CLI change set for a transaction.
Recommended Action Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration.
%DMI-3-DIFF_FAIL :
Explanation An operating system error occurred while performing a diff of two files and redirecting to a third file.
Recommended Action Check free space on device. Clean up if necessary. Also, reducing the value of max-diag-messages-saved in the cisco-ia model may help.
%DMI-3-DIR_EXISTS :
Explanation A existing file is conflicting with a directory name.
Recommended Action Remove or rename the offending file.
%DMI-3-INIT_SYNC_FAIL :
Explanation DMI failed to synchronize the network element's running configuration with the DMI data store upon DMI startup.
Recommended Action Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration.
%DMI-3-INTERNAL_ERROR :
Explanation An unexpected internal error has occurred.
Recommended Action Consult man page for impacted area to interpret the error code and string.
%DMI-3-INVALID_PRESERVE_PATH :
Explanation A non-existent XPath has been specified to be preserved during complete syncs.
Recommended Action Remove the offending path from the /native/cisco-ia/preserve-ned-path list.
%DMI-3-INVALID_REG_EXP :
Explanation An invalid regular expression has been specified which will not compile.
Recommended Action Remove the offending regular expression from the specified model or via o CLI\.
%DMI-3-LOAD_SCHEMAS_FAIL :
Explanation DMI failed to load Confd schemas for yang model namespaces.
Recommended Action Back out any recent yang model updates. Stop and restart netconf-yang.
%DMI-3-MAAPI_APPLY_TRANS_FAIL :
Explanation A Confd error has occurred attempting to apply a transaction via MAAPI.
Recommended Action via MAAPI. Stop and restart netconf-yang.
%DMI-3-MAAPI_DELETE_FAIL :
Explanation A Confd error has occurred attempting to delete a model path via MAAPI.
Recommended Action Stop and restart netconf-yang.
%DMI-3-MAAPI_FINISH_TRANS_FAIL :
Explanation A Confd error has occurred attempting to finish a transaction via MAAPI.
Recommended Action via MAAPI. Stop and restart netconf-yang.
%DMI-3-MAAPI_LOAD_FAIL :
Explanation A Confd error has occurred attempting to load commands to a model path via MAAPI.
Recommended Action Stop and restart netconf-yang.
%DMI-3-MAAPI_LOAD_FILE_FAIL :
Explanation A Confd error has occurred attempting to load commands from a file via MAAPI.
Recommended Action Stop and restart netconf-yang.
%DMI-3-MAAPI_LOCK_FAIL :
Explanation A Confd error has occurred attempting to lock the DMI data store via MAAPI.
Recommended Action Stop and restart netconf-yang.
%DMI-3-MAAPI_SAVE_FAIL :
Explanation A Confd error has occurred attempting to save a model path via MAAPI.
Recommended Action Stop and restart netconf-yang.
%DMI-3-MAAPI_START_TRANS_FAIL :
Explanation A Confd error has occurred attempting to start a transaction via MAAPI.
Recommended Action via MAAPI. Stop and restart netconf-yang.
%DMI-3-MAAPI_START_USER_FAIL :
Explanation A Confd error has occurred attempting to start a user session via MAAPI.
Recommended Action Stop and restart netconf-yang.
%DMI-3-MAAPI_UNLOCK_FAIL :
Explanation A Confd error has occurred attempting to unlock the DMI data store via MAAPI.
Recommended Action Stop and restart netconf-yang.
%DMI-3-MEM_UNAVAIL :
Explanation Insufficient system memory is available to perform the DMI action.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
%DMI-3-MODEL_RESTORE_FAIL :
Explanation DMI failed to restore the model '%s' from the network element's running configuration to the DMI data store.
Recommended Action Check the netconf-yang section of the network element's running configuration. If populated with non-default values, stop and restart netconf-yang. If problem continues, restore the model's configuration in question via Netconf
%DMI-3-NETCONF_SSH_ERROR :
Explanation An error message from the NETCONF SSH daemon.
Recommended Action Not applicable
%DMI-3-SAVE_FAIL :
Explanation An operating system error occurred while opening or writing to a diagnostic file.
Recommended Action Check free space on device. Clean up if necessary. Also, reducing the value of max-diag-messages-saved in the cisco-ia model may help.
%DMI-3-SYNC_CLI_FILTER_ADD_FAIL :
Explanation DMI cannot add a CLI filter to monitor for external CLI changes.
Recommended Action Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration.
%DMI-3-SYNC_CLI_FILTER_CREAT_FAIL :
Explanation DMI cannot create a CLI filter to monitor for external CLI changes.
Recommended Action Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration.
%DMI-3-SYNC_CLI_FILTER_MODE_FAIL :
Explanation DMI cannot set the mode for its CLI filter to monitor for external CLI changes.
Recommended Action Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration.
%DMI-3-SYNC_LOCK_FAIL :
Explanation A Confd error has occurred attempting to lock the DMI data store via MAAPI.
Recommended Action Stop and restart netconf-yang.
%DMI-3-SYNC_SYSLOG_FILTER_ADD_FAIL :
Explanation DMI cannot add a syslog filter to monitor for external CLI changes.
Recommended Action Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration.
%DMI-3-SYNC_SYSLOG_FILTER_CREAT_FAIL :
Explanation DMI cannot create a syslog filter to monitor for external CLI changes.
Recommended Action Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration.
%DMI-3-SYNC_UNLOCK_FAIL :
Explanation A Confd error has occurred attempting to unlock the DMI data store via MAAPI.
Recommended Action Stop and restart netconf-yang.
%DMI-3-VTY_NUM_FAIL :
Explanation DMI must keep track of its tty number it uses to send command lines to the network element's parser in order to avoid triggering its own sync events
Recommended Action Check that the 'show users line' command line is working
%DMI-3-VTY_SERVER_CREAT_FAIL :
Explanation Failed to create VTY server utility instance for DMI operational data use.
Recommended Action Stop and restart netconf-yang.
%DMI-3-VTY_SERVER_START_FAIL :
Explanation Failed to start VTY server utility instance for DMI operational data use.
Recommended Action Stop and restart netconf-yang.
%DMI-4-CLI_ENGINE_ENABLE_FAIL :
Explanation DMI cannot enter privileged mode when communicating with the network element's CLI parser.
Recommended Action Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration. Check AAA settings for the Netconf/Restconf user account.
%DMI-4-CLI_ENGINE_RC_FAIL :
Explanation DMI cannot read CLI engine return code for the particular command.
Recommended Action Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration. If problem continues, stop and restart netconf-yang
%DMI-4-CLI_ENGINE_STATE_FAIL :
Explanation DMI cannot read its CLI engine state.
Recommended Action Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration. If problem continues, stop and restart netconf-yang
%DMI-4-CLI_ROLLBACK_WARN :
Explanation A Confd induced CLI transaction was aborted and during the rollback CLIs, an error was returned
Recommended Action Confirm that the network element's running configuration is in the original state before the failed transaction
%DMI-4-CONFD_ROLLBACK_WARN :
Explanation An error occurred saving the Confd rollback information.
Recommended Action Please enable rollback in Confd. Check for free file system space.
%DMI-4-CONTROL_SOCKET_CLOSED :
Explanation The control socket connection to Confd has closed unexpectedly.
Recommended Action DMI will reset. No action necessary.
%DMI-4-DIAG_WARN :
Explanation An error occurred saving DMI message diagnostics.
Recommended Action Check for free file system space.
%DMI-4-NETCONF_TRACE_WARN :
Explanation An error occurred saving the Netconf trace information.
Recommended Action Please enable netconfTraceLog in Confd. Check for free file system space.
%DMI-4-SUB_READ_FAIL :
Explanation A Confd error has occurred attempting to read the subscription socket.
Recommended Action DMI will reset. No action necessary.
%DMI-5-CONFIG_I :
Explanation A change to the running configuration was performed using NETCONF or RESTCONF.
Recommended Action Informational only. No action required.
%DMI-5-SYNC_COMPLETE :
Explanation An external change (outside of NETCONF or RESTCONF) has been detected thus, the running-config has been sent to Confd to
Recommended Action Informational only. No action required.
%DMI-5-SYNC_NEEDED :
Explanation A configuration change that may trigger additional changes has been detected thus, the running-config will be sent to Confd to
Recommended Action Informational only. No action required.
%DMI-5-SYNC_START :
Explanation An external change (outside of NETCONF or RESTCONF) has been detected thus, the running-config will be sent to Confd to
Recommended Action Informational only. No action required.
%DMI-6-NETCONF_SSH_INFO :
Explanation An informational message from the NETCONF SSH daemon.
Recommended Action Not applicable
%DMI-7-GEN_DEBUG :
Explanation A debug message for syslog consumption. For troubleshooting wihtout btrace
Recommended Action Not applicable
DOT1X
%DOT1X-3-PROC_START_ERR :
Explanation The system failed to create the Dot1x process.
Recommended Action Restart Dot1x process by entering <cmd>dot1x system-auth-control<cmd> command. If this message recurs, Reload the device.
%DOT1X-3-UNKN_ERR :
Explanation The Dot1x process cannot operate due to an internal system error.
Recommended Action Reload the device/process
%DOT1X-4-INFO_EAPOL_PING_RESPONSE :
Explanation An EAPOL ping was sent out on this port to determine 802.1x readiness of the client attached. An EAPOL response has been received by the device such as a PC.
Recommended Action No action required.
%DOT1X-4-MEM_UNAVAIL :
Explanation Insufficient system memory is available to perform the Dot1x Authentication.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
%DOT1X-5-FAIL :
Explanation Dot1x authentication was unsuccessful.
Recommended Action No action is required.
%DOT1X-5-IGNORE_LARGER_EAPOL :
Explanation Targetted EAPOL packet size is larger than mtu size of the port on which client is connected and hence ignoring the packet to be sent out
Recommended Action Configure AAA server to fragement eap-method data so that EAPOL size is smaller than interface MTU size
%DOT1X-5-RESULT_OVERRIDE :
Explanation Authentication result was overridden
Recommended Action No action is required.
%DOT1X-5-SUCCESS :
Explanation Dot1x authentication was successful.
Recommended Action No action is required.
DPSS
%DPSS-2-IPC_INIT : IPC message handler registration failure, rc [int]
Explanation Registering an IPC message handler for the DPSS feature failed. This will cause the feature to not function.
Recommended Action This is normally a software issue. The consequences are that the DPSS feature will not function. LOG_STD_ACTION
%DPSS-3-DPSS_INIT_FAILED : DPSS [chars] Register failed
Explanation DPSS Initialization of registration failed.
Recommended Action LOG_STD_ACTION
%DPSS-3-IPC_NORES : No space for the IPC reply, size [int]
Explanation For a request from upper DPSS 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
%DPSS-3-IPC_OPEN_REPLY : IPC Open Reply failed, request [int]
Explanation For a request from upper DPSS 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
%DPSS-3-MEM_INIT_FAILED : Allocation of [chars] memory failed for DPSS
Explanation DPSS Initialization of channel pool failed.
Recommended Action LOG_STD_ACTION
%DPSS-3-PKT_REPLICA_INIT_FAILED : Register to Generic Packet Replication failed for DPSS
Explanation DPSS Initialization of packet replication registration failed.
Recommended Action LOG_STD_ACTION
DNET
%DNET-3-HEARSELF : Hello type [hex] for my address from [dec].[dec] via [chars]
Explanation The system is receiving its own DECnet packets. Either a serial line is looped back or another host with the same DECnet address is already present on the LAN.
Recommended Action Check the serial lines (if present) and the DECnet configuration.
%DNET-3-NOMEMORY : Insufficient memory for DECnet accounting entry
Explanation The traffic information for a particular pair of DECnet nodes cannot be recorded due to a low memory condition.
Recommended Action LOG_STD_REDUCE_ACTION
%DNET-4-DUPENTRY : Duplicate DECnet Accounting List Entry for nodes [dec].[dec] -[dec].[dec]
Explanation A synchronization problem has occurred whilst a new transit DECnet Accounting List Entry was being added and a duplicate entry has been found.
Recommended Action LOG_STD_SH_CMD_ACTION(show decnet accounting)
%DNET-4-MAPCON : Map entry [dec].[dec] conflicts with adjacency to [dec].[dec]
Explanation Your DECnet configuration is incorrect. A host that is specified as nonlocal is present on your local network.
Recommended Action Correct the configuration. Call your technical support representative if you need assistance.
DOSFS
%DOSFS-3-RESETERR : [chars] [chars]
Explanation disk could not be reset while the system is initiated reload. This will cause a transient disk error, disk timeout error, when the ROMMON initialization code tries to reads the DIB. This is a transient error and the system will be able to access the disk and continue normal operation.
Recommended Action No action is required.
%DOSFS-4-DFS_FSCK_ERR : Error while running fsck on the file [chars].
Explanation Fsck is running in a loop while walking through the cluster chain of a file and has aborted.
Recommended Action Report this occurrence to Engineering. Use Topic to search for a similar DDTS. If you find none, write a DDTS for this problem.
%DOSFS-5-DFS_CLOSE_ERR : Error during close of the file [chars]. [chars]
Explanation An error occured during a file close operation.
Recommended Action Enter the <CmdBold>fsck<NoCmdBold> <CmdArg>filesystem prefix:<NoCmdArg> command to check and attempt to repair the disk. If this does not fix the problem, format the disk.
%DOSFS-5-DIBERR : [chars] [chars]
Explanation The system cannot boot a image from the Flash disk because the Device Information Block is different. The Flash disk can be read by the router, but will require formatting by the router before an image can be booted from it.
Recommended Action Follow any instructions provided in the error message. Before storing a image in the Flash disk and trying to boot from this device, enter the format command to format the flash disk from the router. Then copy the desired image to the Flash disk and then boot from this device.
DRIP
%DRIP-3-DRIPFAIL : DRIP: Assertion failed: [chars]
Explanation An internal software error has occurred.
Recommended Action LOG_STD_ACTION
%DRIP-6-DRIP_CONFLICT : DRIP conflict with CRF [dec].
Explanation A DRIP conflict has occured. The virtual ring or pseudo ring's CRF is being re-used in the network.
Recommended Action Make sure that the CRF vlanid of the virtual ring and the pseudo ring is unique in the network.
DRP
%DRP-3-MULTICOMMAND : multiple DRP commands encountered
Explanation Multiple DRP commands were found in a single DRP packet.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%DRP-3-NOSOCKET : Unable to open socket
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.
%DRP-3-NOWRITE : unable to send response to [IP_address]:[dec]
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.
%DRP-3-SUBNETTED : unable to determine metric for [IP_address], [IP_address] subnetted
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.
%DRP-7-NOROUTE : no route for destination [IP_address]
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.
DS0_DUMP
%DS0_DUMP-3-INIT_FAIL : DS0 PCM Tracer is not initialized.
Explanation DS0 dump process can't be initialized.
Recommended Action Make sure there is enough memory in the system and IOS is properly installed.
%DS0_DUMP-3-MALLOC_PROC_MEM : Process memory allocation failed for PCM capture: size [hex].
Explanation The free process memory in the system is not enough for the PCM capture session.
Recommended Action Refer to the user guide for the estimation of process memory needed for PCM capture. Do 'show memory' to make sure there is enough memory before PCM capture starts.
%DS0_DUMP-3-PCM_TRACE_NOT_SUPPORTED : PCM Trace/ds0 dump is not supported on slot [int].
Explanation Can't execute this command on the slot number specified.
Recommended Action Refer to the user guide for which slot ds0 dump is supported on.
%DS0_DUMP-3-PCM_TRACER_RUNNING : A previous session of PCM capture is in progress.
Explanation Can't start new PCM capture session since there is one going on now.
Recommended Action Make sure there is no other PCM capture session going on before start the new capture.
%DS0_DUMP-3-PCM_TRACE_START_FAILED : PCM capture start failed.
Explanation Failed to start the ds0 dump in the TDM driver.
Recommended Action Make sure there is no hardware defect and there is no other ds0 dump/test tdm dump session going on.
%DS0_DUMP-6-PCM_TRACER_NOT_RUNNING : no PCM capture is in progress.
Explanation None
Recommended Action None
%DS0_DUMP-6-PCM_TRACE_RSP_ERROR : module fail and terminate the pcm capture for [dec]/[dec]/[dec]/[dec]
Explanation None
Recommended Action None
%DS0_DUMP-6-PCM_TRACE_RSP_STARTED : module start PCM capture for [dec]/[dec]/[dec]/[dec]
Explanation None
Recommended Action None
%DS0_DUMP-6-PCM_TRACE_RSP_STOPPED : module stop or complete PCM capture for [dec]/[dec]/[dec]/[dec]
Explanation None
Recommended Action None
%DS0_DUMP-6-PCM_TRACE_RSP_UNKNOWN : module send unkonwn pcm capture response [dec] for [dec]/[dec]/[dec]/[dec]
Explanation None
Recommended Action None
%DS0_DUMP-6-PCM_TRACE_STARTED : PCM capture started.
Explanation None
Recommended Action None
%DS0_DUMP-6-PCM_TRACE_STOP_FAILED : failed to stop PCM capture
Explanation None
Recommended Action None
%DS0_DUMP-6-PCM_TRACE_STOPPING : stopping PCM capture
Explanation None
Recommended Action None
DSA_PROXY
%DSA_PROXY-3-PROXY_CHUNK_CLEAR_FAILED :
Explanation Chunk clear failed.
Recommended Action LOG_STD_ACTION
%DSA_PROXY-3-PROXY_CHUNK_CREATION_FAILED :
Explanation Chunk creation failed.
Recommended Action LOG_STD_ACTION
%DSA_PROXY-3-PROXY_DEBUG_REG_FAILED :
Explanation DSA Conditional Debugging registration failed.
Recommended Action LOG_STD_ACTION
%DSA_PROXY-3-PROXY_IPC_ALLOC_FAILED :
Explanation Generating IPC failed.
Recommended Action LOG_STD_ACTION
%DSA_PROXY-3-PROXY_IPC_INIT_FAILED : [dec]
Explanation IPC handler initialization failed.
Recommended Action LOG_STD_ACTION
%DSA_PROXY-3-PROXY_IPC_INVALID_PARAM :
Explanation IPC Invalid parameters.
Recommended Action LOG_STD_ACTION
%DSA_PROXY-3-PROXY_IP_CLEAR_FAILED : [dec]
Explanation IP Cache clear failed.
Recommended Action LOG_STD_ACTION
%DSA_PROXY-3-PROXY_IP_CLEAR_TO_FAILED : [dec] [dec]
Explanation IP Cache clear failed.
Recommended Action LOG_STD_ACTION
%DSA_PROXY-3-PROXY_IPC_SEND_CLEAR_FAILED : [dec]
Explanation DSA clear ip cache failed.
Recommended Action LOG_STD_ACTION
%DSA_PROXY-3-PROXY_IPC_SEND_INIT_FAILED : [dec]
Explanation Send initialization IPC failed.
Recommended Action LOG_STD_ACTION
%DSA_PROXY-3-PROXY_IPC_SEND_UNINIT_FAILED : [dec]
Explanation DSA Send UNINIT IPC failed.
Recommended Action LOG_STD_ACTION
%DSA_PROXY-3-PROXY_LOW_MEM_REQ_FAILED :
Explanation Send low mem IPC failed.
Recommended Action LOG_STD_ACTION
%DSA_PROXY-3-PROXY_MEM_EXTEND_FAILED :
Explanation Extending memory failed.
Recommended Action LOG_STD_ACTION
%DSA_PROXY-3-PROXY_NO_IP_POOL_MEM :
Explanation IP Cache pool is not allocated.
Recommended Action LOG_STD_ACTION
%DSA_PROXY-3-PROXY_RETURN_MEM_FAILED :
Explanation return mem IPC failed.
Recommended Action LOG_STD_ACTION
%DSA_PROXY-3-PROXY_TBL_INIT_FAILED :
Explanation IP Cache table init failed.
Recommended Action LOG_STD_ACTION
%DSA_PROXY-3-PROXY_UNINIT_FAILED :
Explanation UNINIT cleanup failed.
Recommended Action LOG_STD_ACTION
%DSA_PROXY-4-PROXY_IPC_INVALID_MSG :
Explanation Invalid IPC message
Recommended Action LOG_STD_ACTION
%DSA_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
DSM
%DSM-3-DSPALARM : channel [chars], DSP ID [hex]: status=[hex] message=[hex] text=[chars]
Explanation The DSP reported a fatal error. All sessions on the DSP were dropped and a DSP reload was attempted.
Recommended Action Contact your technical support representative, include the full text of the error message.
%DSM-3-DSP_TIMEOUT : DSP timeout on channel [chars], event [hex]: DSP ID=[hex]: [chars]
Explanation Timeout on DSP response.
Recommended Action The DSP has been automatically reset. If problem persists, contact your technical support representative
%DSM-3-INTERNAL : Internal Error : [chars]
Explanation DSM Internal error
Recommended Action Contact your technical support representative
%DSM-3-MSGSNDFAIL : channel:[chars] DSP ID:[hex] Message ID:[hex]
Explanation A message could not be sent to the DSP. The session continued but may have experienced problems.
Recommended Action Contact your technical support representative, include the full text of the error message.
%DSM-3-NOEVENT : no free event structure available from [chars] for DSM message
Explanation There were no event structures remaining in the system pools to alert the router of a voice or signaling event.
Recommended Action Contact your technical support representative, include the full text of the error message.
%DSM-6-SESSION_DATABASE_FAILED : Cannot create DSM session database
Explanation Failed to create DSM session.
Recommended Action Check the size of free memory to make sure there is enough memory.
DSP
%DSP-3-DSP_ALARM : DSP device [dec] is not responding. Trying to recover DSP device by reloading
Explanation A DSP device on DSP-SPA is not responding. The error message indicates the slot, subslot, the SPA type and the name of the hardware device.
Recommended Action Software will try to recover by reloading the failed DSP. If the problem persists then perform OIR of the SPA located in the specified subslot. Before removing the SPA, enter the hw-module subslot stop command. Remove the SPA, wait 5 seconds, and reinsert the SPA. If the problem persists, copy the error message text exactly as it appears on the console or in the system log, enter the show diag command, contact your Cisco technical support representative and provide the representative with the gathered information.
%DSP-3-DSP_DNLD : DSP device [dec] DNLD process exited. Trying to recover DSP device by rebooting the DSP
Explanation A DSP device on DSP-SPA is not responding. The error message indicates the slot, subslot, the SPA type and the name of the hardware device.
Recommended Action Software will try to recover by reloading the failed DSP. If the problem persists then perform OIR of the SPA located in the specified subslot. Before removing the SPA, enter the hw-module subslot stop command. Remove the SPA, wait 5 seconds, and reinsert the SPA. If the problem persists, copy the error message text exactly as it appears on the console or in the system log, enter the show diag command, contact your Cisco technical support representative and provide the representative with the gathered information.
%DSP-3-DSP_KEEPALIVE : DSP device [dec] is not responding. Trying to recover DSP device by reloading
Explanation A DSP device on DSP-SPA is not responding. The error message indicates the slot, subslot, the SPA type and the name of the hardware device.
Recommended Action Software will try to recover by reloading the failed DSP. If the problem persists then perform OIR of the SPA located in the specified subslot. Before removing the SPA, enter the hw-module subslot stop command. Remove the SPA, wait 5 seconds, and reinsert the SPA. If the problem persists, copy the error message text exactly as it appears on the console or in the system log, enter the show diag command, contact your Cisco technical support representative and provide the representative with the gathered information.
%DSP-3-DSP_WATCHDOG : DSP device [dec] is not responding. Trying to recover DSP device by reloading
Explanation A DSP device on DSP-SPA is not responding. The error message indicates the slot, subslot, the SPA type and the name of the hardware device.
Recommended Action Software will try to recover by reloading the failed DSP. If the problem persists then perform OIR of the SPA located in the specified subslot. Before removing the SPA, enter the hw-module subslot stop command. Remove the SPA, wait 5 seconds, and reinsert the SPA. If the problem persists, copy the error message text exactly as it appears on the console or in the system log, enter the show diag command, contact your Cisco technical support representative and provide the representative with the gathered information.
%DSP-3-FIRMWARE_VER_INFO : Downloading streamware... for device [dec]. DSP firmware(ver:[int].[int]) contained in image has different version from the firmware(ver:[int].[int]) in harddisk or bootflash
Explanation DSP firmware version check
Recommended Action No action is required.
%DSP-3-TIMER : [chars] timer expired for DSP [dec]
Explanation DSP timer has expired
Recommended Action No action is required.
%DSP-5-DNLD : DNLD started for device [dec]
Explanation DSP bootloader DNLD starte
Recommended Action No action is required.
%DSP-5-UPDOWN : DSP [dec] is [chars]
Explanation DSP device changed state up/down
Recommended Action No action is required.
DSP_SPA
%DSP_SPA-2-INITFAIL : Not Enough Resources:[chars]
Explanation The shared port adaptor failed to complete software initialization.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%DSP_SPA-3-BUFF_FAIL : Not Enough MEM Buffers [chars]
Explanation Not enought memory buffers for shared port adaptor operation.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%DSP_SPA-3-FILE_OP_FAIL : Failed to open file [chars] : [chars]
Explanation Failed to open file
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%DSP_SPA-3-FILE_RD_FAIL : Failed to read [int] bytes from file: [chars]
Explanation Failed to read data from file
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%DSP_SPA-3-HW_ERROR : [chars]: A Hardware device error was detected. Trying to recover the SPA by reload. Error information : [chars]
Explanation An internal hardware device error has occurred on the services SPA. The error message indicates the slot, subslot, the SPA type and the name of the hardware device. The SPA has been deactivated and reactivated to resolve the problem. If the error occurs more than five times within an hour, no further attempts to reactivate the SPA will be made. This message is likely due to an unrecoverable hardware failure.
Recommended Action Perform OIR of the SPA located in the specified subslot. Before removing the SPA, enter the hw-module subslot stop command. Remove the SPA, wait 5 seconds, and reinsert the SPA. If the problem persists, copy the error message text exactly as it appears on the console or in the system log, enter the show diag command, contact your Cisco technical support representative and provide the representative with the gathered information.
%DSP_SPA-3-HW_ERROR_INFO : [chars]: Non fatal hardware device error was detected. Error information : [chars]
Explanation An internal hardware device error has occurred on the services SPA. The error message indicates the slot, subslot, the SPA type and the name of the hardware device. This message is likely due to a recoverable hardware failure.
Recommended Action Perform OIR of the SPA located in the specified subslot. Before removing the SPA, enter the hw-module subslot stop command. Remove the SPA, wait 5 seconds, and reinsert the SPA. If the problem persists, copy the error message text exactly as it appears on the console or in the system log, enter the show diag command, contact your Cisco technical support representative and provide the representative with the gathered information.
%DSP_SPA-3-NULL_FAIL : Non-Initialized ptr: [chars]
Explanation About to Access non-initialized pointer
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
DSPRM
%DSPRM-5-NULLIDB_CREATE_FAIL : VoIP Null IDB creation failed.
Explanation VoIP nullidb creation failed.
Recommended Action None
DSS
%DSS-3-ACK_FAIL : Ack failed for dsp_id [dec], seq_no [dec]
Explanation DSP core not responding to host messages
Recommended Action No action is required.
%DSS-3-DSPID_INVALID : Invalid DSPID [dec]
Explanation Invalid DSP ID detetced in the message
Recommended Action No action is required.
%DSS-3-TIMER : [chars] timer expired for DSPID [dec]
Explanation DSS timer has expired
Recommended Action No action is required.
%DSS-5-UPDOWN : DSP core [dec] is [chars]
Explanation DSP core changed state up/down
Recommended Action No action is required.
DSMP
%DSMP-3-DSPALARM : Alarm on DSP [chars]: status=[hex] message=[hex] text=[chars]
Explanation The DSP reported a fatal error. All sessions on the DSP were dropped and a DSP reload was attempted.
Recommended Action Contact your technical support representative, include the full text of the error message.
%DSMP-3-DSP_TIMEOUT : DSP timeout on DSP [chars]: event [hex], [chars]
Explanation Timeout on DSP response.
Recommended Action The DSP has been automatically reset. If problem persists, contact your technical support representative
%DSMP-3-INTERNAL : Internal Error : [chars]
Explanation DSMP Internal error
Recommended Action Contact your technical support representative
%DSMP-3-INVALID_EVENT : Unhandled event: current state:[chars] event:[chars]
Explanation The event is not handled in the DSMP gateway state machine specification
Recommended Action Contact your technical support representative
%DSMP-3-MSGSNDFAIL : channel:[chars] DSP ID:[hex] Message ID:[hex]
Explanation A message could not be sent to the DSP. The session continued but may have experienced problems.
Recommended Action Contact your technical support representative, include the full text of the error message.
%DSMP-3-NOEVENT : no free event structure available from [chars] for DSMP message
Explanation There were no event structures remaining in the system pools to alert the router of a voice or signaling event.
Recommended Action Contact your technical support representative, include the full text of the error message.
%DSMP-3-PRG_ERROR : Programming Error : [chars]
Explanation Progaramming error in DSMP subsys
Recommended Action Contact your technical support representative
%DSMP-3-SUBSYS_UNINITIALIZED : Internal Error : [chars]
Explanation DSMP Subsystem not initialized
Recommended Action Contact your technical support representative
%DSMP-4-WARNING : Warning : [chars]
Explanation Resource temporarily not available
Recommended Action Contact your technical support representative if condition lasts
%DSMP-6-SESSION_DATABASE_FAILED : Cannot create DSMP session database
Explanation Failed to create DSMP session.
Recommended Action Check the size of free memory to make sure there is enough memory.
DSPDUMP
%DSPDUMP-5-DUMPSTART : DSP [dec] ([hex]) in slot [dec] starting dump
Explanation The DSP resource is beginning crash dump collection
Recommended Action No action is required.
%DSPDUMP-5-RX_CONTROL_DROP : DSP [dec] in slot [dec] Rx Control Message Dropped by DSP
Explanation The DSP has reported that a Rx Control Message was dropped
Recommended Action No action is required.
%DSPDUMP-5-TX_CONTROL_DROP : DSP [dec] in slot [dec] Tx Control Message Dropped by DSP
Explanation The DSP has reported that a Tx Control Message was dropped
Recommended Action No action is required.
DSPFARM
%DSPFARM-3-ERROR : Errors on DSPFARM module [chars]
Explanation Errors on DSPFARM module
Recommended Action Check sh dspfarm all
%DSPFARM-4-INFO : Info on DSPFARM module [chars]
Explanation Info on DSPFARM module
Recommended Action Check sh dspfarm
%DSPFARM-4-NOTICE : Failure on DSPFARM module [chars]
Explanation Failure on DSPFARM module
Recommended Action Check sh dspfarm
%DSPFARM-4-WARNING : Warning on DSPFARM module [chars]
Explanation Warning on DSPFARM module
Recommended Action Check sh dspfarm all
DSPU
%DSPU-3-ActpuNegResponse : ACTPU Neg rsp received from PU [chars]
Explanation Remote PU rejected the router's request for an SSCP-PU session.
Recommended Action Verify PU configuration parameters at the router and at the remote PU. Determine whether the problem exists at the remote PU, and correct it. If the problem persists, call your Cisco technical support representative for assistance.
%DSPU-3-CLSIBadAdptCorr : CLSI bad Adaptor correlator, header= [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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%DSPU-3-CLSIBadIdentifier : CLSI bad identifier, header= [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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%DSPU-3-CLSIBadIdentifierType : CLSI bad identifier type, header= [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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%DSPU-3-CLSIBadLength : CLSI bad length, header= [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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%DSPU-3-CLSIBadPrimitiveCmd : CLSI bad primitive command, header= [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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%DSPU-3-CLSIBadPrimitiveType : CLSI bad primitive type, header= [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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%DSPU-3-CLSIBadReturnCode : CLSI bad return code: [dec], header= [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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%DSPU-3-CLSIUnexpctActSapCnf : CLSI unexpected ActivateSapCnf, header= [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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%DSPU-3-CLSIUnexpctDeactSapCnf : CLSI unexpected DeactivateSapCnf, header= [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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%DSPU-3-CLSIUnexpctEnableCnf : CLSI unexpected EnableCnf, header= [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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%DSPU-3-CLSIUnexpctIdStnInd : CLSI unexpected IdStnInd, header= [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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%DSPU-3-DSPU_BufferCorrupted : DSPU could not free buffer -buffer corrupted
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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%DSPU-3-LSConnInFailed : Connect in from remote address [chars] failed.
Explanation Connection with remote station could not be established.
Recommended Action Verify configuration parameters at the router and at the remote station. Determine whether the router is configured to accept connectIn from this remote station.
%DSPU-3-LSConnInFailedNoMem : Connect in from remote address [chars] failed; insufficient memory.
Explanation Connection with the remote station could not be established because of insufficient memory in the router.
Recommended Action Correct low memory problem in the router. If the problem persists, call your technical support representative for assistance.
%DSPU-3-LSConnInFromHostFailed : Connect in from host [chars] with remote address [chars] failed.
Explanation Connection with the remote host could not be established.
Recommended Action Verify host configuration parameters at the router and at the host. Determine whether the router is configured to accept connection from this host.
%DSPU-3-LSConnInFromPuFailed : Connect in from pu [chars] with remote address [chars] failed.
Explanation Connection with the remote PU could not be established.
Recommended Action Verify PU configuration parameters at the router and at the remote PU. Determine whether the router is configured to accept connectIn from this remote PU.
%DSPU-3-LSConnOutToHostFailed : Connect out to host [chars] failed.
Explanation Connection with the remote host could not be established.
Recommended Action Verify host configuration parameters at the router and at the host. Determine whether the host is active and responding to connection requests.
%DSPU-3-LSConnOutToPuFailed : Connect out to pu [chars] failed.
Explanation Connection with the remote PU could not be established.
Recommended Action Verify PU configuration parameters at the router and at the remote PU. Determine whether the remote PU is active and responding to connection requests.
%DSPU-3-LSInvalidMaxIFrame : Connection attempt failed from XID= [chars], Invalid MaxIFrame= [dec]
Explanation An invalid MaxIFrame value in an exchange identification (XID) was received from the remote station; connection with remote station could not be established.
Recommended Action Correct link station configuration at the remote station.
%DSPU-3-LSInvalidWindowSize : Connection attempt failed from XID= [chars], Invalid WindowSize= [dec]
Explanation An invalid WindowSize value in an exchange identification (XID) was received from the remote station; connection with remote station could not be established.
Recommended Action Correct link station configuration at the remote station.
%DSPU-3-LSNoACTPUCapability : Connection attempt failed from XID= [chars], ACTPU not supported
Explanation The remote station did not request PU 2.0 activation; connection with remote station is terminated.
Recommended Action Correct link station configuration parameters at the remote station to request a system services control point (SSCP)-PU session with the router.
%DSPU-3-LSXIDNegotiationError : XID Negotiation Error, bad byte= [dec], bad bit= [dec], sense data= [chars]
Explanation XID3 with an error indication was received from the remote station; connection with the remote station could not be established.
Recommended Action Determine, from the CV 22 byte or bit information, which field in the XID3 is rejected by the remote station, and correct the link station configuration parameters at either the router or the remote station.
%DSPU-3-NotifyNegRsp : LU [dec] received a Notify Neg Resp from host [chars]
Explanation Remote host rejected the router's request to activate/deactivate an SSCP-LU session.
Recommended Action Verify host configuration parameters at the router and at the remote host. Determine whether the problem exists at the remote host and correct it. If the problem persists, call your technical support representative for assistance.
%DSPU-3-SnaBadData : Bad SNA data received from PU [chars], data= [chars]
Explanation Unrecognized SNA data was received from the remote PU.
Recommended Action Correct the problem at the remote PU. If the problem persists, call your Cisco technical support representative for assistance.
%DSPU-3-UnknownXid : XID Format not supported, XID= [chars]
Explanation Unsupported XID received from the remote station; connection with remote station could not be established.
Recommended Action Configure the remote station to send supported XID (if possible). Supported XID formats are: XID Format 0 XID Format 3.
DSX
%DSX-4-ALARM : [chars] [chars]: [chars]
Explanation The specified T1/E1 or T3/E3 Alarm has been asserted or cleared
Recommended Action The recommended action is to isolate and repair the source of the asserted alarm
DUAL
%DUAL-3-ANCHORCOUNT : Anchor count negative
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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DUAL-3-BADCOUNT : Route [chars], [dec] successors, [dec] rdbs
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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DUAL-3-BADIGRPSAP : Cannot send incremental SAP update to peer on [chars]. tIncreasing output-sap-delay may help
Explanation An incremental SAP update could not be sent, because this might cause the SAP tables between peers to become out of synch.
Recommended Action Increase the output SAP delay on the listed interface to reduce buffer usage. If, after changing the delay the message remains, copy the error message exactly as it appears and report it to your technical support representative.
%DUAL-3-BADIGRPSAPTYPE : Unsupported SAP type for EIGRP being [chars] -type [hex]
Explanation There are two types of service access points (SAPs)-general queries and general responses. This message is sent when you receive or attempt to send an SAP with a type code which is not a general query or a general response. It is also sent when you receive a general query not addressed to the broadcast address.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative. If possible, also provide the output of the <bold>debug ipx sap activity<nobold> and <bold>debug ipx sap event<nobold> commands for the period during which this message appeared.
%DUAL-3-INTERNAL : [chars] [dec]: Internal Error
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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DUAL-3-LINKSEXIST : Interface [chars] going down and [dec] links exist
Explanation An interface is going down or is being removed from routing through IGRP, but not all links (neighbors) have been removed from the topology table.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DUAL-3-LINKSTILLUP : Link [dec] [chars] still exists on [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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DUAL-3-MULTIFLOW : Flow control error, [chars], on [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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DUAL-3-NOBUFFER : No buffers available for [int] byte packet
Explanation The DUAL software was unable to allocate a packet buffer. The system may be out of memory.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%DUAL-3-NOHANDLE : Handle [dec] is not allocated in pool.
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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DUAL-3-NOMATCH : Nexthop and infosource don't match. N = [chars], I = [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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DUAL-3-NOSOCKET : Unable to open socket for AS [dec]
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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DUAL-3-PEERSEXIST : [dec] peers exist on IIDB [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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DUAL-3-PFXLIMIT : [chars] [dec]: [chars] prefix limit reached([int]).
Explanation Number of prefixes for eigrp has reached the configured or default limit.
Recommended Action Use show ip eigrp accounting for details on the source of the prefixes and take corrective measures.
%DUAL-3-RDBLEFT : Lingering DRDB deleting IIDB, dest [chars], nexthop [chars] ([chars]), origin [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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DUAL-3-REFCOUNT : Negative refcount in pakdesc [hex]
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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DUAL-3-SIA : Route [chars] stuck-in-active state in [chars] [dec]. Cleaning up
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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DUAL-3-UNKTIMER : Unknown timer type [dec] expiration
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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DUAL-4-PFXLIMITTHR : [chars] [dec]: [chars] threshold prefix level([int]) reached.
Explanation Number of prefixes in the topology database has reached the configured or default threshold level.
Recommended Action Take preventive action by identifying the source of the prefixes. Use show ip eigrp accounting for details.
%DUAL-5-NBRCHANGE : [chars] [dec]: Neighbor [chars] ([chars]) is [chars]: [chars]
Explanation A neighbor went up or down.
Recommended Action No action is required.
%DUAL-6-EVENT : [chars], [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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DUAL-6-NBRINFO : [chars] [dec]: Neighbor [chars] ([chars]) is [chars]: [chars]
Explanation Information regarding a neighbor.
Recommended Action No action is required.
DWDM
%DWDM-3-CLEAR_G709_CTR : Unable to clear g709 counter in slot [dec] rc = [dec]
Explanation The SPA driver was unable to clear the G.709 OTN protocol counters for bit errors
Recommended Action Please check the configuration of the interfaces and controllers and correct the configuration if necessary. If the problem persists contact your Cisco technical support representative
%DWDM-3-CONFIG_ALARM_REPORT : Failed to config report alarm [chars] slot [dec] rc = [dec]
Explanation The SPA driver could not configure one of the reporting status of the alarms
Recommended Action Please check the configuration of the interfaces and controllers and correct the configuration if necessary. If the problem persists contact your Cisco technical support representative
%DWDM-3-CONFIG_ALARM_THRESHOLD : Failed to config threshold alarm [chars] slot [dec] rc = [dec]
Explanation The SPA driver could not configure one of the threshold alarms for the optical data or transport unit
Recommended Action Please check the configuration of the interfaces and controllers and correct the configuration if necessary. If the problem persists contact your Cisco technical support representative
%DWDM-3-CONFIG_OVERHEAD_TTI : Failed to config [chars] [chars] slot [dec] rc = [dec]
Explanation The LC driver could not configure the tail trace identifier for the optical data or transport unit
Recommended Action Please check the configuration of the interfaces and controllers and correct the configuration if necessary. If the problem persists contact your Cisco technical support representative
%DWDM-3-CONFIG_PM : Failed to config [chars] [chars] slot [dec] rc = [dec]
Explanation The LC driver could not configure the PM parameters for the optical data or transport unit
Recommended Action Please check the configuration of the interfaces and controllers and correct the configuration if necessary. If the problem persists contact your Cisco technical support representative
%DWDM-3-CONFIG_TX_POWER : Failed to config transmit power [dec] on slot [dec] rc = [dec]
Explanation The SPA driver detected a error in configuring the Tx power level for the UT2 transponder module
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: https://mycase.cloudapps.cisco.com/start 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).
%DWDM-3-DWDM_CONFIG_FAIL : Failed to [chars] [chars] in slot [dec] rc = [dec]
Explanation The SPA driver detected failure during configuring one of the DWDM parameters
Recommended Action Reload the SPA card and if the problem persists call the tachnical assistance centre
%DWDM-3-DWDM_GET_INFO_FAIL : Failed receiving [chars] from slot [dec] rc = [dec]
Explanation The SPA driver did not receive the necessary optics information from the slot
Recommended Action Please check the configuration of the interfaces and controllers and correct the configuration if necessary. If the problem persists contact your Cisco technical support representative
%DWDM-3-DWDM_NULL_INFO : DWDM info is NULL in [dec]
Explanation The SPA driver detected NULL information for DWDM
Recommended Action Reload the SPA and if the problem persists contact the technical support representative
%DWDM-3-IPC_SHIM_INIT : DWDM IPC SHIM init failed
Explanation The SPA driver detected failure during DWDM IPC SHIM initialization
Recommended Action Please power down and reseat the indicated SPA card If the problem persists please contact your technical support representative
%DWDM-3-LC_ERR_STATS : error sending LC stats to RP
Explanation The SPA driver encountered an error while sending the LC stats to the RP
Recommended Action Reload the SPA card and if the problem persists call the technical support representative
%DWDM-3-MALLOC_FAIL : malloc failure creating G.709 port on slot [dec]
Explanation The SPA driver detected a memory error on the SPA card
Recommended Action Reload the card and if the problem persists call TAC
%DWDM-3-OTN_STATS_CREATE_IF_FAIL : stats for interface index [dec] could not be created with status [dec]
Explanation None
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%DWDM-3-OTN_STATS_CREATE_IF_FAILED_TO_ALLOCATE : stats for interface index [dec] could not be created with status [dec]
Explanation None
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%DWDM-3-OTN_STATS_DELETE_IF_FAIL : stats for interface index [dec] could not be deleted with status [dec]
Explanation None
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%DWDM-3-RPC_FAILED : Application error rc = [dec]:
Explanation The system failed to retrieve the information required to execute the command
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show version command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%DWDM-3-RPC_INIT_FAIL : DWDM RPC init failure
Explanation The system failed to create the resources required to process user interface commands for transceivers. The error is not fatal but some show commands could fail.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show version command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%DWDM-3-RPC_PROCESSING_ERROR : DWDM RPC error: [chars]
Explanation Non Fatal error occured in processing an RPC messsage.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show version command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%DWDM-3-RX_G709_INFO : Failed receiving G709 info from slot [dec] rc = [dec]
Explanation The SPA driver did not receive the necessary G.709 OTN protocol information from the slot
Recommended Action Please check the configuration of the interfaces and controllers and correct the configuration if necessary. If the problem persists contact your Cisco technical support representative
%DWDM-3-RX_LOS_THRESHOLD : Failed to config rx los threshold = [dec] on slot [dec] rc = [dec]
Explanation The SPA driver detected an error in configuring the transponder receive power threshold
Recommended Action Reload the SPA card and if the problem persists call TAC
%DWDM-3-TIMER_ERR : Timer error
Explanation The Driver did not obtain an expired timer from the timer tree for the DWDM process
Recommended Action The SPA driver has encountered an error event on the SPA card. If the condition persists, copy the error message exactly as it appears or contact your technical support representative
%DWDM-4-G709ALARM : [chars]: [chars] [chars]
Explanation The specified G709 Alarm has been declared or released
Recommended Action Recommended action is to repair the source of the alarm.
DYNCMD
%DYNCMD-3-CHAINADDFAIL : Parse chain link add failed for '[chars]'
Explanation An error has occurred when a dynamic command is being added to the IOS command set. The commands specified will not be available.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DYNCMD-3-CHAINDELFAIL : Parse chain link delete failed for '[chars]'
Explanation An error has occurred when a dynamic command is being removed from the IOS command set. The commands specified will stil not be available.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DYNCMD-3-FLAGSINUSE : New feature flags list [int] invalid while feature flags in use [int]
Explanation IOS received a message to set the feature flags for the CLI. The message received to set the feature flags changed the number of feature flags which is unexpected. The message is ignored.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DYNCMD-3-FLAGSINVALID : New feature flag list values ([int]) different than expected ([int])
Explanation IOS received a message to set the feature flags for the CLI. The message received does not contains the number of feature flag values that the message list size indicated.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DYNCMD-3-INIT : Dynamic command subsystem failed to initialize '[chars]'
Explanation Some features depend on portions of the dynamic command infrastructure. Such features will be unavailable.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DYNCMD-3-LINKINVALIDALT : Link alternate node message received for node '[chars]', which cannot have an alternate.
Explanation IOS received a message to add a command into the CLI. One of the messages to link nodes instructed IOS to link nodes which would result in an invalid construction.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DYNCMD-3-LINKINVALIDTRANS : Link transition '[chars]' message received for node '[chars]', which cannot have such a transition.
Explanation IOS received a message to add a command into the CLI. One of the messages to link nodes instructed IOS to link nodes which would result in an invalid construction.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DYNCMD-3-LINKOUTOFSEQ : Create node message received when in mode '[chars]'
Explanation IOS received a message to add a command node into the CLI. The message was received out of sequence
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DYNCMD-3-LINKUNKNOWNACCEPTNODE : Link node message received for unknown accept ([chars]) node '[int]'
Explanation IOS received a message to add a command into the CLI. One of the messages to link nodes referenced a node unknown to IOS
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DYNCMD-3-LINKUNKNOWNALTNODE : Link node message received for unknown alternate node '[int]'
Explanation IOS received a message to add a command into the CLI. One of the messages to link nodes referenced a node unknown to IOS
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DYNCMD-3-LINKUNKNOWNNODE : Link node message received for unknown node '[int]'
Explanation IOS received a message to add a command into the CLI. One of the messages to link nodes referenced a node unknown to IOS
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DYNCMD-3-MSGBIPCBUFFER : Unable to acquire a BIPC buffer for sending messages.
Explanation A message was to be sent by IOS, but no BIPC buffer was available. The message to be sent has been discarded and the associated operation failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DYNCMD-3-MSGBIPCERR : Unable to process received BIPC messages for Dynamic Commands, error: [chars]
Explanation An unexpected condition has occurred while IOS was trying to process a received BIPC message for Dynamic Commands.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DYNCMD-3-MSGBUILDERROR : Error '[dec]' building TDL message '[chars]' to send to the Shell Manager
Explanation An unexpected condition has occurred while IOS is building a TDL message to send to the Shell Manager
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DYNCMD-3-MSGDISPATCH : Unable to dispatch received TDL messages for Dynamic Commands
Explanation An unexpected condition has occurred while IOS is trying to dispatch to the TDL message handler functions for received TDL messages for Dynamic Commands.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DYNCMD-3-MSGDISPATCHNULL : Received NULL TDL message
Explanation An unexpected condition in which IOS has received a NULL TDL message for Dynamic Commands.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DYNCMD-3-MSGENQUEUEERROR : Error queueing TDL message '[chars]' to send to the Shell Manager
Explanation An unexpected condition has occurred when IOS attempted to queue a TDL message to send to the Shell Manager
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DYNCMD-3-MSGERROR : Error '[chars]' handling a received TDL message '[chars]' for Dynamic Commands
Explanation An unexpected condition has occurred while IOS is processing a received Dynamic Command TDL message
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DYNCMD-3-MSGINVALIDFIELDINT : Invalid field '[chars]' in TDL message '[chars]' received: value '[int]' for Dynamic Commands
Explanation A message with an invalid field value was received for Dynamic Command creation
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DYNCMD-3-MSGINVALIDFIELDSTR : Invalid field '[chars]' value '[chars]' in TDL message '[chars]' received for Dynamic Commands
Explanation A message with an invalid field value was received for Dynamic Command creation
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DYNCMD-3-MSGMARSHALERROR : Error '[dec]' marshaling TDL message '[chars]' to send to the Shell Manager
Explanation An unexpected condition has occurred while IOS is marshaling TDL message to send to the Shell Manager
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DYNCMD-3-MSGMISSINGFIELD : Missing field '[chars]' in TDL message '[chars]' received from the Shell Manager
Explanation A message missing a required field was received from the Shell Manager
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DYNCMD-3-NODEDUPLICATE : Create node message received for duplicate node '[int]'
Explanation IOS received a message to add a command into the CLI. One of the command nodes to be created has an identifier of an existing node. The new node is ignored.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DYNCMD-3-NODEOUTOFSEQ : Create node message received when in mode '[chars]'
Explanation IOS received a message to add a command node into the CLI. The message was received out of sequence
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DYNCMD-3-NODETYPEUNKNOWN : Create node message received for unknown node type '[dec]', '[chars]'
Explanation IOS received a message to add a command into the CLI. One of the command nodes to be created is of a type unknown to IOS
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DYNCMD-3-PKGERR_LOG_FAIL : Failed to log errors for package '[chars]'
Explanation An error has occurred updating the commandset for a newly installed package. The commands which failed to transfer could not be saved for further analysis.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DYNCMD-3-PKGHANDLER_FILE_REMOVE : Package '[chars]' failed to remove: [chars] ([chars])
Explanation An error has occurred when a package was attempting to remove a file. This should never fail.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DYNCMD-3-PKGHANDLER_FILE_WRITE : Package '[chars]' failed to write: [chars] ([chars])
Explanation An error has occurred when a package was attempting to write a file. The configuration for the package could not be propagated to associated components.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DYNCMD-3-PKGINT_API : Package interface failure for package '[chars]': [chars]
Explanation Some features' configuration depends on a packaging infrastructure. Packaged configuration for the specified package will be unavailable.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DYNCMD-3-PKGINT_ARG : Incorrect argument type for package '[chars]', operation '[chars]': [chars] ([int])
Explanation An error has occurred loading the commandset for a newly installed package. The package is not compatible with the running IOS instance.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DYNCMD-3-PKGINT_ARG_NUMBERVAL : Invalid argument value for package '[chars]', operation '[chars]': [int] ([int])
Explanation An error has occurred loading the commandset for a newly installed package. The package is not compatible with the running IOS instance.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DYNCMD-3-PKGINT_ARG_OPAQUEVAL : Invalid argument value for package '[chars]', operation '[chars]': [IPV6 address] ([int])
Explanation An error has occurred loading the commandset for a newly installed package. The package is not compatible with the running IOS instance.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DYNCMD-3-PKGINT_ARGS : Incorrect argument count for package '[chars]', operation '[chars]': [dec] not [dec]
Explanation An error has occurred loading the commandset for a newly installed package. The package is not compatible with the running IOS instance.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DYNCMD-3-PKGINT_DIR_CREATE : Package integration failed to create directory: [chars] ([chars])
Explanation An error has occurred when attempting to create a package export directory. This should never fail.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DYNCMD-3-PKGINT_DIR_MOVE : Package integration failed to move directory: [chars] to [chars] ([chars])
Explanation An error has occurred when attempting to move a package export directory. This should never fail.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DYNCMD-3-PKGINT_DIR_OPEN : Package integration failed to open directory: [chars] ([chars])
Explanation An error has occurred when attempting to open a package export directory. This should never fail.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DYNCMD-3-PKGINT_DIR_REMOVE : Package integration failed to remove directory: [chars] ([chars])
Explanation An error has occurred when attempting to remove a package export directory. This should never fail.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DYNCMD-3-PKGINT_FILE_OPEN : Package integration failed to open file: [chars] ([chars])
Explanation An error has occurred when attempting to open a file in a package export directory. This should never fail.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DYNCMD-3-PKGINT_FILE_REMOVE : Package integration failed to remove: [chars] ([chars])
Explanation An error has occurred when attempting to remove a package export file. This should never fail.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DYNCMD-3-PKGINT_INSTALL : Failed to install '[chars]': [chars]
Explanation Some features' configuration depends on a packaging infrastructure. Packaged configuration for the specified package will be unavailable.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DYNCMD-3-PKGINT_LOAD : Failed to load '[chars]': [chars]
Explanation Some features' configuration depends on a packaging infrastructure. Packaged configuration for the specified package will be unavailable.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DYNCMD-3-PKGINT_LOCK : Failed to acquire package list lock for [chars]: [chars]
Explanation An error occurred when a configuration package was being installed or removed. This may indicate a timeout which may be a temporary condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DYNCMD-3-PKGINT_OFFSET : Invalid offset argument for package '[chars]', operation '[chars]': [chars] ([int])
Explanation An error has occurred loading the commandset for a newly installed package. The package is not compatible with the running IOS instance.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DYNCMD-3-PKGINT_PKGLOCK : [chars] failed to acquire package lock for [chars]
Explanation An error occurred when locking a configuration package. The package needs to be locked for processing configuration commands or timer-based processing of configuration data.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DYNCMD-3-PKGINT_SYMBOL : Package [chars] incompatible: symbol '[chars]' is of type [chars], expected [chars]
Explanation Some features' configuration depends on a packaging infrastructure. Packaged configuration for the specified package will be unavailable.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DYNCMD-3-PKGINT_UNLOCK : Failed to release the package list lock: [chars]
Explanation An error occurred when a configuration package was being installed or removed. This should not occur.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DYNCMD-3-PKGINT_VALIDATE : Failed to validate '[chars]': [chars]
Explanation Some features' configuration depends on a packaging infrastructure. Packaged configuration for the specified package will be unavailable.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DYNCMD-3-PKGNODE_ADD_FAIL : Parse node add failed for package '[chars]', [chars] ([int])
Explanation An error has occurred loading the commandset for a newly installed package. The node could not be added and the commandset for the package will not be available.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DYNCMD-3-TREETOP : Unable to link top-level keyword '[chars]' into parse tree
Explanation IOS received a message to add a command into the CLI. The appropriate location to link in the command could not be found.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DYNCMD-3-TREETOPNOTKW : The top-level parser transition '[chars]' is not a keyword
Explanation IOS received a message to add a command into the CLI. The top-level node must be a keyword node.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%DYNCMD-4-CMD_DEPRECATION : The command 'platform trace runtime' is being deprecated. Please use the exec mode command 'set platform software trace' instead. Note that using this command and 'set platform software trace' together will lead to indeterministic results
Explanation The command 'platform trace runtime' is being deprecated.
Recommended Action No action is required.
%DYNCMD-7-CMDSET_LOADED : The Dynamic Command set has been loaded from the Shell Manager
Explanation IOS has completed loading the set of commands published and processed by components running in packages other than the IOS package.
Recommended Action No action is required.
%DYNCMD-7-CMDSET_UNLOADED : The Dynamic Command set from the Shell Manager has been unloaded
Explanation IOS has completed unloading the Dynamic Command set. This should only occur when a new package has been installed and should shortly be followed by a message indicating that the new Dynamic Command set has been loaded.
Recommended Action No action is required.
%DYNCMD-7-PKGINT_INSTALLED : The command package '[chars]' has been succesfully installed
Explanation IOS has completed installation of the specified command package. Configuration commands for the package are now available.
Recommended Action No action is required.
%DYNCMD-7-PKGINT_UNINSTALLED : The command package '[chars]' has been succesfully uninstalled
Explanation IOS has completed uninstallation of the specified command package. Configuration commands for the package are no longer available.
Recommended Action No action is required.
E
E911
%E911-3-MISSING_DEFAULT_NUMBER : It is mandatory to configure an ELIN under 'voice emergency response settings.'
Explanation The administrator has enabled the Enhanced 911 feature without configuring a default ELIN under 'voice emergency response settings.'
Recommended Action The administrator should enter the 'voice emergency response settings' mode and configure a value for the 'elin' CLI.
%E911-4-CALLBACK_UNREACHABLE : Unable to contact the last emergency caller at [chars].
Explanation The Public Safety Answering Point is calling an Emergency Line Identification Number (ELIN). The last caller from that ELIN has its calling number saved for three hours from the time the emergency call was originated. If the ELIN cannot be translated to the caller's calling number, then one of the following has happened: 1) The emergency call information has expired. Forwarding has not been set-up when calls have expired. 2) A system reload has occurred, thereby erasing the emergency call information.
Recommended Action The dial-peer created to accept ELIN calls could set-up Call Forwarding to a corporate operator or main help desk to avoid having the call backs rejected.
%E911-5-EMERGENCY_CALL_HISTORY : calling number[[chars]]; called number[[chars]]; ELIN[[chars]]
Explanation A call has been made to an emergency response number. This message simply informs system administrators of the call.
Recommended Action The administrator determines the policy for outbound emergency calls. The administrator may set up an application to page or email a technician everytime this message is emitted.
EAP
%EAP-2-PROCESS_ERR :
Explanation This is critical condition where the router could not perform EAP process related operation.
Recommended Action Review SM 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. Reload the device/process.
%EAP-3-BADPKT :
Explanation This messages informs that the router received an invalid or malformed EAP packet from the specified host.
Recommended Action Check specified host for EAP operation.
%EAP-6-MPPE_KEY :
Explanation This messages informs that the router received MPPE KEY for the specified host.
Recommended Action No action is required.
EC
%EC-3-BWMISMATCH : [chars] should be removed from the Port-channel[dec]
Explanation The member-link shouldn't have been part of the port-channel bundle because the bandwidth of the member-link doesn't match the bandwidth of the bundle. This configuration shouldn't have been allowed. This error indicates it was allowed due to some software issue.
Recommended Action Remove the member-link from the port-channel for proper operation.
%EC-5-MINLINKS_MET : Port-channel [chars] is up as its bundled ports ([dec]) meets min-links
Explanation The administrative configuration of minimum links is equal or less than the number of bundled ports. Therefore this port channel has been brought up
Recommended Action None.
%EC-5-MINLINKS_NOTMET : Port-channel [chars] is down bundled ports ([dec]) doesn't meet min-links
Explanation The administrative configuration of minimum links is greater than the number of bundled ports. Therefore this port channel has been brought down
Recommended Action Reduce the min-links configuration for this group or add more ports to this port-channel to have them bundle.
ECFM_PROXY
%ECFM_PROXY-2-PROXY_IPC_INIT_FAILED : QFP ECFM Proxy IPC interface initialization failure (result: [dec]).
Explanation Cisco internal software error. QFP ECFM Proxy initialization detected that the IPC interface initialization failed. QFP ECFM 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%ECFM_PROXY-3-ECFM_MEM_EXTEND_FAILED : ECFM 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%ECFM_PROXY-3-ECFM_MEM_REQ_FAILED : ECFM 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%ECFM_PROXY-3-PROXY_BAD_MSG : QFP ECFM Proxy received bad length message type [dec]
Explanation Cisco internal software error. QFP ECFM 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%ECFM_PROXY-3-PROXY_IPC_ALLOC_FAILED : QFP ECFM Proxy [chars] message lost due to message buffer allocation failure.
Explanation Cisco internal software error. QFP ECFM 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%ECFM_PROXY-3-PROXY_IPC_SEND_FAILED : QFP ECFM Proxy [chars] message lost due to message sent failure (result: [dec]).
Explanation Cisco internal software error. QFP ECFM 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%ECFM_PROXY-4-PROXY_INVALID_MSG : QFP ECFM Proxy received invalid message type [dec]
Explanation Cisco internal software error. QFP ECFM 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%ECFM_PROXY-4-PROXY_INVALID_MSG_LEN : QFP ECFM Proxy IPC invalid length, [dec]:[dec] len [dec] flags [hex] source [dec]
Explanation Cisco internal software error. QFP ECFM 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
EEM
%EEM-6-SUCCESS : [chars]
Explanation EEM Policy provisioning by the Auto-deploy is successful.
Recommended Action No action is required.
EFP_STORMCTRL
%EFP_STORMCTRL-6-ACTION_DEFAULT : Service Instance [dec] on interface [chars] has dropped packets due to storm-control
Explanation Configured Storm Control Threshold on Ethernet Service Instance Reached
Recommended Action No Action
EI_CLI_MT_SPI
%EI_CLI_MT_SPI-3-FILE_ERROR : Error occured: [chars], for file: [chars]
Explanation An error occured while trying to manipulate a file.
Recommended Action Make sure file permissions are appropriate and locations are correct. Then try a restart.
%EI_CLI_MT_SPI-3-GENERAL_ERROR : Error occured: [chars]
Explanation An error occured during startup of the CLI Agent causing unwanted behavior and early exit.
Recommended Action Please contact TAC.
EM
%EM-3-EXCEED : EM exceed maximum open events ([dec]).
Explanation The total number of open events exceeded the maximum number of possible open events. The maximum number that the EM server permits is specified in the error message. EM clients are either opening too many events or not closing events within the permitted time period.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show em state | inc <em_type> command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.|Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the output Interpreter (https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl). Issue the <CmdBold> show em state | inc <em_type> command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl). If you still require assistance, open a case with the Technical Assistance Center via the Internet (http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl) , or contact your Cisco technical support representative and provide the representative with the gathered information.
%EM-3-FAIL : The specified EM Function failed ([chars]).
Explanation The specified EM function failed. This condition might be caused by incorrect logic or a memory corruption.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the <CmdBold>show em state<NoCmdBold> command or the <CmdBold>show em status<NoCmdBold> command to gather data that may help Cisco technical support to identify the nature of the error. Contact your Cisco technical support representative and provide the representative with the gathered information.
%EM-3-NOMEM : The EM failed to allocate memory resources for the specifiedEM function ([chars]).
Explanation The EM failed to allocate memory resources for the specified function because memory is running low.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the <CmdBold>show memory summary <NoCmdBold> command to gather data that may help Cisco technical support to identify the nature of the error. Contact your Cisco technical support representative and provide the representative with the gathered information.
%EM-3-NULLPTR : The pointer in a specified EM function ([chars]) is incorrectly NULL.
Explanation The pointer in the specified EM function is incorrectly NULL. This condition might be caused by incorrect logic or a memory corruption.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the <CmdBold>show em state<NoCmdBold> command or the <CmdBold>show em status<NoCmdBold> command to gather data that may help Cisco technical support to identify the nature of the error. Contact your Cisco technical support representative and provide the representative with the gathered information.
%EM-4-AGED : The specified EM client ([chars] type=[dec], id=[dec]) did not close the EM event within the permitted amount of time ([dec] msec).
Explanation A timeout occurred. This condition is minor and should not affect the functionality of the switch.
Recommended Action This message should not affect switch functionality but can be sign of a software bug condition. Please check Bug Toolkit on the Cisco web-site for relevant bugs against this message. If you do not find any, please contact the TAC with the output of <CmdBold>show em client<NoCmdBold>
%EM-4-INVALID : The specified EM function ([chars]) received Invalid operands <[dec]>.
Explanation The EM client used invalid API parameters.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the <CmdBold>show em state<NoCmdBold> command or the <CmdBold>show em status<NoCmdBold> command to gather data that may help Cisco technical support to identify the nature of the error. Contact your Cisco technical support representative and provide the representative with the gathered information.
%EM-4-LIMIT : EM exceed open events limit ([dec]).
Explanation The EM has exceeded the permitted number of open events. The open event limit is 5000.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%EM-4-NOTUP : The EM is not available ([chars]).
Explanation Because some basic initialization failed, the EM is not available. This condition might be caused by failure of a basic infrastructure functionality or a memory corruption.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the <CmdBold>show em state<NoCmdBold> command or the <CmdBold>show em status<NoCmdBold> command to gather data that may help Cisco technical support to identify the nature of the error. Contact your Cisco technical support representative and provide the representative with the gathered information.
%EM-4-SEARCH : The EM function ([chars]) searched for the specified open event ([dec]),but the search failed.
Explanation The specified EM function could not find the specified open event. This condition might be caused by a memory corruption.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the <CmdBold>show em state<NoCmdBold> command or the <CmdBold>show em status<NoCmdBold> command to gather data that may help Cisco technical support to identify the nature of the error. Contact your Cisco technical support representative and provide the representative with the gathered information.
%EM-4-SENDFAILED : The specified EM client (type=[dec]) failed to send messages to standby.
Explanation Because the specified EM client failed to send messages to the standby supervisor engine, the standby supervisor engine is not updated. Do not attempt to failover to standby supervisor engine.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show checkpoint clients command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
EMD
%EMD-0-EVENT_LIBRARY : An event facility initialization or maintenance function failed because [chars]
Explanation An event facility initialization or maintenance function failed. This error could be due to a software defect or system resource limitation.
Recommended Action Restart the card.
%EMD-0-RESOLVE_FRU : Failed to determine [chars] card because [chars]
Explanation The system was unable to to determine a card state. This error could be due to a software defect or system resource limitation.
Recommended Action Restart the card.
%EMD-0-SERVICES_INITIALIZATION : Failed to initialize general application services because [chars]
Explanation The system failed to initialize the application services. This error could be due to a software defect or system resource limitation.
Recommended Action Restart the card.
%EMD-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 can occur from a hardware defect, software defect, or incorrect IDPROM content.
Recommended Action Examine the logs for IDPROM and hardware errors.
%EMD-3-IDPROM_SENSOR : One or more sensor fields from the idprom failed to parse properly because [chars].
Explanation One or more IDPROM sensor fields failed to parse properly. The most likely reason is a checksum failure in the IDPROM from incorrect IDPROM content.
Recommended Action Examine the logs for IDPROM and hardware errors.
%EMD-3-PFU_INITIALIZATION : The RP has failed to initialize a Power Supply/Fan module controller because [chars]
Explanation The route processor (RP) failed to initialize a power supply or a fan module controller. This error could be caused by a hardware defect or a C2W access failure.
Recommended Action Examine the logs for C2W and hardware errors.
%EMD-3-SENSOR_INITIALIZATION : Failed to initialize sensor monitoring because [chars].
Explanation The system failed to initialize an IDPROM sensor monitoring process. This error can occur from a hardware defect, software defect, or incorrect IDPROM content.
Recommended Action Examine the logs for IDPROM and hardware errors.
ERM
%ERM-6-NOTIFY : Owner: [chars](%0llx), User: [chars](%0llx), Threshold Type: [chars], Level: [chars], Direction: [chars], Limit: [int], Usage: [int], Policy ID: [dec]
Explanation A notification has been sent out by the resource owner because of a threshold violation.
Recommended Action This is just informational message only. This message appears because a threshold has been violated. Do 'show runnning' and look for the configuration under the mode 'resource manager' and check the thresholds that has been set. This is just a notification that the threshold has been violated - nothing to stop the resource exhaustion is being done here.
EM_ISSU
%EM_ISSU-2-GET_BUFFER : Event Manager ISSU client failed to get buffer for message. Error: [dec] ([chars])
Explanation The Event Manager 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)
%EM_ISSU-2-INIT : Event Manager ISSU client initialization failed to [chars]. Error: [dec] ([chars])
Explanation The Event Manager 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%EM_ISSU-2-SEND_NEGO_FAILED : Event Manager ISSU client failed to send negotiation message. Error: [dec] ([chars])
Explanation The Event Manager 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)
%EM_ISSU-2-SESSION_NEGO : Event Manager ISSU client encountered unexpected client nego_done. Error: [dec] ([chars])
Explanation An ISSU-compliant client transitions through a series of internal states. The Event Manager 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>)
%EM_ISSU-2-SESSION_REGISTRY : Event Manager ISSU client failed to register session information. Error: [dec] ([chars])
Explanation The Event Manager 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>)
%EM_ISSU-3-INVALID_SESSION : Event Manager ISSU client does not have a valid registered session.
Explanation The Event Manager 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>)
%EM_ISSU-3-MSG_NOT_OK : Event Manager ISSU client 'Message Type [dec]' is not compatible
Explanation The Event Manager 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>)
%EM_ISSU-3-MSG_SIZE : Event Manager ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] ([chars])
Explanation The Event Manager ISSU client failed to calculate the MTU for the specified message. The Event Manager 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>)
%EM_ISSU-3-OPAQUE_MSG_NOT_OK : Event Manager ISSU client 'Opaque Message Type [dec]' is not compatible
Explanation The Event Manager ISSU client received an incompatible message from the peer device. The opaque 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>)
%EM_ISSU-3-SESSION_UNREGISTRY : Event Manager ISSU client failed to unregister session information. Error: [dec] ([chars])
Explanation The Event Manager 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>)
%EM_ISSU-3-TRANSFORM_FAIL : Event Manager ISSU client [chars] transform failed for 'Message Type [dec]'. Error: [dec] ([chars])
Explanation The Event Manager 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 Event Manager 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>)
ENT_API
%ENT_API-3-NOCREAT : EntityApiProcess not created -Entity MIB will not be initialised
Explanation Attempt to start EntityApiProcess failed when the entity subsystem was initialised. The Entity MIB will not be populated.
Recommended Action The Entity MIB API process was not created, possibly due to lack of memory. If you want to use the Entity MIB API, reconfigure the box so that less memory is used by other features, or add more memory to the system. Reload the box after reconfiguring.
%ENT_API-4-MULTIPLEREG : Multiple registration request with same entity name = [chars] using entity index [int] and phyDescr = [chars].
Explanation An attempt to register a physical entity happened and failed, because the same entity name is being used, for which a registration has already been done.
Recommended Action Need to raise a DDTS with the component responsible for the for the registration to use different entity names for registering different entities.
%ENT_API-4-NOALIAS : [chars] entity not found when adding an alias with physical index = [int] and logical index = [int] to the Entity MIB
Explanation An attempt to add an alias entry to the Entity MIB was made. The logical or physical entity with the specified index does not exist, and so the alias entry creation failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Using your NMS tool, also provide the content of the Entity MIB table.
%ENT_API-4-NOENT : Trying to add or delete an unknown entity to the Entity MIB
Explanation An attempt to add/delete an unknown entity to the Entity MIB was made. The request could not be processed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Using your NMS tool, also provide the content of the Entity MIB table.
%ENT_API-4-NOLPMAP : [chars] entity not found when adding an LPMapping entry with logical index = [int] and physical index = [int] to the Entity MIB
Explanation An attempt to add an LPMapping entry to the Entity MIB was made. The logical or physical entity with the specified index does not exist, and so the LPMapping entry creation failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Using your NMS tool, also provide the content of the Entity MIB table.
%ENT_API-4-NOPARENT : Parent physical entity [int] did not exist when trying to add child physical entity [int], phyDescr = [chars], phyName = [chars].
Explanation An attempt to add a physical entity failed, because its parent physical entity did not exist in the entPhysicalTable of the Entity MIB.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Using your NMS tool, also provide the content of the Entity MIB table.
%ENT_API-4-NOPORT : Physical entity does not have a Port PhysicalClass when adding an alias with physical index = [int], logical index = [int], phyDescr = [chars], phyName = [chars], phyClass = [int], phyContainedIn = [int], to the Entity MIB
Explanation An attempt to add an alias entry to the Entity MIB was made. The physical entity with the specified index does not have an entPhysicalClass of 10(Port class) and so the alias entry creation failed. See RFC2737 for the definition of the PhysicalClass textual-convention and the aliasMappingEntry object.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Using your NMS tool, also provide the content of the Entity MIB table.
ENVIRONMENTAL
%ENVIRONMENTAL-1-ALERT : [chars], Location: [chars], State: [chars], Reading: [dec] [chars]
Explanation One of the sensors in the system is reading an out of normal value.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%ENVIRONMENTAL-1-SENSORFAIL : [chars], Location [chars], State: fail
Explanation One of the sensors in the system has detected a failure condition from which it can not recover. This sensor is no longer reporting readings to the environmental monitoring subsystem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%ENVIRONMENTAL-3-CHASFSERR : Sensor [chars] on FRU [chars] has an invalid chasfs device state [chars]
Explanation The system does not understand the state that the sensor is reporting. This is most likely a filesystem corruption or ISSU problem. You may try rebooting the router to see if the problem corrects itself.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%ENVIRONMENTAL-3-TDLERROR : Error processing TDL message. [dec]
Explanation An unexpected condition in which IOS has received a TDL message which it can not process.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%ENVIRONMENTAL-5-SENSOROK : [chars], Location: [chars], State: normal
Explanation One of the sensors in the system had been in a failure condition but is now operating normally.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%ENVIRONMENTAL-6-NOTICE : [chars], Location: [chars], State: [chars], Reading: [dec] [chars]
Explanation Informational message on the sensor reading
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
ENVM
%ENVM-3-NOFORK : Could not create environmental polling process
Explanation None
Recommended Action None
%ENVM-4-LONGBUSYREAD : C2W Interface busy for long time reading temperature sensor [dec]
Explanation None
Recommended Action None
%ENVM-4-LONGBUSYWRITE : C2W Interface busy for long time writing temperature sensor [dec]
Explanation None
Recommended Action None
%ENVM-4-READERROR : Error reading temperature sensor [dec]
Explanation None
Recommended Action None
%ENVM-4-WRITEERROR : Error writing temperature sensor [dec]
Explanation None
Recommended Action None
EPC
%EPC-3-MEM_INIT_FAILED : Allocation of [chars] memory failed for EPC
Explanation EPC Initialization of channel pool failed.
Recommended Action LOG_STD_ACTION
%EPC-3-PKT_REPLICA_INIT_FAILED : Register to Generic Packet Replication failed for EPC
Explanation EPC Initialization of packet replication registration failed.
Recommended Action LOG_STD_ACTION
EPM
%EPM-4-ACL_CONFIG_ERROR :
Explanation This message indicates that adding an ACE to the specified ACL was ignored because of wrong configuration
Recommended Action Change ACE configuration for the specifed ACL
%EPM-4-POLICY_APP_FAILURE :
Explanation This message indicates that the displayed policy for the client could not be applied by the EPM
Recommended Action Policy application failure could happen due to multiple reasons.The reason for the failure is notified to the client and the client has to take appropriate action based on it
%EPM-6-AAA :
Explanation This message indicates a download request has been sent/downloaded successfully for the specified dACL
Recommended Action No action required
%EPM-6-AUTH_ACL :
Explanation his message indicates a AUTH_DEF_ACL or AUTH_DEF_ACL_OPEN has been applied or removed
Recommended Action No action required
%EPM-6-IPEVENT :
Explanation This message indicates the IP event Wait/Release/Assignment that has occured with respect to the specified host
Recommended Action No action required
%EPM-6-POLICY_APP_SUCCESS :
Explanation This message indicates that the displayed policy for the client has been applied successfully by the EPM
Recommended Action No action required
%EPM-6-POLICY_REQ :
Explanation This message indicates that a policy application/remove request has been received by the EPM
Recommended Action No action required
EPM_PLUGIN
%EPM_PLUGIN-5-ERR_VLAN_NOT_FOUND :
Explanation An attempt was made to assign a VLAN to an 802.1x port, but the VLAN was not found in the VTP database.
Recommended Action Make sure the VLAN exists and is not shutdown or use another VLAN.
EPOCH
%EPOCH-6-EPOCH_REJECTED : Peer [chars] has rejected epoch: [chars]
Explanation This error occurs if epoch from shell-manager has been rejected by the peer.
Recommended Action Check the epoch and peer state.
ERSPAN
%ERSPAN-3-MEM_INIT_FAILED : Allocation of [chars] memory failed for ERSPAN
Explanation ERSPAN Initialization of channel pool failed.
Recommended Action LOG_STD_ACTION
%ERSPAN-3-PKT_REPLICA_INIT_FAILED : Register to Generic Packet Replication failed for ERSPAN
Explanation ERSPAN Initialization of packet replication registration failed.
Recommended Action LOG_STD_ACTION
ESS_FEATURE
%ESS_FEATURE-3-ESF_STUB : CPP ESS per-session feature ([chars]) executes stub entry in [chars] direction
Explanation Cisco internal software error. CPP ESS per-session feature stub entry got executed. The packet will be dropped.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%ESS_FEATURE-4-ESF_DROP_POLICY : CPP ESS feature encounted unexpected linktype=[dec]
Explanation Cisco internal software error. CPP ESS per-session feature encounted unexpected linktype when executing output drop policy
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
ESS_IPSUB
%ESS_IPSUB-3-ESS_IPSUB_STUB : CPP ESS IPSUB executes stub entry in [chars] direction
Explanation Cisco internal software error. CPP ESS IPSUB stub entry got executed. The packet will be dropped.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%ESS_IPSUB-3-FSOL_THROTTLE_ERR : Allocation of [chars] memory failed for ESS IP Subscriber
Explanation Allocation of memory resource demanded by ESS IPSUB FSOL throttle failed. This is a serious problem at the ESS IPSUB FSOL initialization for throttling.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
ESS_PROXY
%ESS_PROXY-2-IPC_THROTTLE_ERR : Allocation of [chars] memory failed for ESS Proxy unsolicited event throttling
Explanation Allocation of memory resource demanded by ESS Proxy throttle failed. This is a serious problem at the ESS Proxy IPC initialization for unsolicited event throttling.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%ESS_PROXY-2-KA_CHANNEL_ALLOC_FAILED : CPP ESS Proxy Session Keepalive channel creation failure.
Explanation Cisco internal software error. CPP ESS Proxy Session Keepalive detected that the channel creation failed. CPP ESS proxy session keepalive 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%ESS_PROXY-2-KA_PKT_REPLICA_REG_FAILED : CPP ESS Proxy Session Keepalive packet replication registration failure (result: [dec]).
Explanation Cisco internal software error. CPP ESS Proxy Session Keepalive detected that the packet replication registration failed. CPP ESS proxy session keepalive 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%ESS_PROXY-2-KA_PKT_TMPL_BFR_ALLOC_FAILED : CPP ESS Proxy Session Keepalive packet template allocation failure ([chars] buffer length: [dec]).
Explanation Cisco internal software error. CPP ESS Proxy Session Keepalive detected that the packet template buffer allocation failed. CPP ESS proxy session keepalive 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%ESS_PROXY-2-KA_TIMER_INIT_FAILED : CPP ESS Proxy Session Keepalive timer initialization failure.
Explanation Cisco internal software error. CPP ESS Proxy Session Keepalive detected that the timer initialization failed. CPP ESS proxy session keepalive 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%ESS_PROXY-2-PROXY_IPC_INIT_FAILED : CPP ESS Proxy IPC interface initialization failure (result: [dec]).
Explanation Cisco internal software error. CPP ESS Proxy initialization detected that the IPC interface initialization failed. CPP ESS 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%ESS_PROXY-3-PROXY_BAD_MSG : CPP ESS Proxy received bad length message type [dec]
Explanation Cisco internal software error. CPP ESS 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%ESS_PROXY-3-PROXY_INV_MSG : CPP ESS Proxy received invalid message type [dec]
Explanation Cisco internal software error. CPP ESS Proxy received an invalid message type 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%ESS_PROXY-3-PROXY_IPC_ALLOC_FAILED : CPP ESS Proxy [chars] message lost due to message buffer allocation failure., MSGDEF_LIMIT_MEDIUM
Explanation Cisco internal software error. CPP ESS 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%ESS_PROXY-3-PROXY_IPC_NO_HDLR : CPP ESS Proxy received unregistered message type [dec]
Explanation Cisco internal software error. CPP ESS Proxy received a message from control plane but there is no registered handler. 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%ESS_PROXY-3-PROXY_IPC_SEND_FAILED : CPP ESS Proxy [chars] message lost due to message sent failure (result: [dec]).
Explanation Cisco internal software error. CPP ESS 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
ESS_SWITCH
%ESS_SWITCH-3-ESS_STUB : CPP ESS switching ([chars]) feature executes stub entry in [chars] direction
Explanation Cisco internal software error. CPP ESS Switching feature stub entry got executed. The packet will be dropped.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%ESS_SWITCH-3-STATS_INVALID_PTR : CPP ESS Switching invalid statistics block for session [chars]., MSGDEF_LIMIT_GLACIAL
Explanation Cisco internal software error. CPP ESS Switching session contains an invalid statistics block. The session statistics is lost.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
ETH_SPA_GEN
%ETH_SPA_GEN-3-CU_SFP_NOT_SUPP : CU-SFP is not supported on SPA-2x1GE-V2 / SPA-2x1GE-SYNCE
Explanation CU-SFP is not supported on SPA-2x1GE-V2 / SPA-2x1GE-SYNCE
Recommended Action Use PHY based ports for CU Connections
%ETH_SPA_GEN-3-UNSUPPORTED_XCVR : Transceiver type GLC-GE-100FX is not supported on SPA-8xGE-V2
Explanation Transceiver type GLC-GE-100FX is not supported on SPA-8xGE-V2
Recommended Action Consult the documentation and ensure supported transceivers are plugged into the SPA
ETH_SPA_GILA_FUGU
%ETH_SPA_GILA_FUGU-3-DATA_VER_MISMATCH : TCAM checkpointed data version [dec] differs from current version [dec].
Explanation During Minimal Disruptive Restart, version of checkpointed tcam data is found to be different from the data in the current version. The SPA will be reset as normal and hence will impact traffic.
Recommended Action Open a case with Cisco Technical Assistance Center for further assistance.
%ETH_SPA_GILA_FUGU-3-ELT_NOT_IN_CUR_VER : The element at address [dec] in [chars] tcam is found missing during Minimal Disruptive Restart reconcilation.
Explanation During the reconcilation phase of Minimumal Disruptive Restart, an element was found to be present in the old IOS but not present in the new IOS image. This indicates that the config for this element was not played down from the RP during config-replay. This is an error condition, and the SPA will be reset as normal and hence will impact traffic.
Recommended Action Open a case with Cisco Technical Assistance Center for further assistance
%ETH_SPA_GILA_FUGU-3-HDR_PARAMS_MISMATCH : TCAM checkpointed header values differs from values in current version.
Explanation During Minimal Disruptive Restart, values of fields in the checkpointed tcam header is found to be differnt from the values in the current version of IOS. The SPA will be reset as normal and hence will impact traffic.
Recommended Action Open a case with Cisco Technical Assistance Center for further assistance.
%ETH_SPA_GILA_FUGU-3-HDR_VER_MISMATCH : TCAM checkpointed header version [dec] differs from current version [dec].
Explanation During Minimal Disruptive Restart, version of checkpointed tcam header is found to be different from the header in the current version. The SPA will be reset as normal and hence will impact traffic.
Recommended Action Open a case with Cisco Technical Assistance Center for further assistance.
%ETH_SPA_GILA_FUGU-3-HW_SW_MISMATCH : The hardware and software copies of the element at address [dec] in tcam [chars] do not match. This indicates reconcilation failure.
Explanation During reconcilation phase of Minimal Disruptive Restart, it is found that the software and hardware copies of an element in tcam do not match. This indicates an error and the SPA will be reset as normal and impact traffic.
Recommended Action Open a case with Cisco Technical Assistance Center for further assistance
%ETH_SPA_GILA_FUGU-3-RECONFIG_FAILURE : Fugu reconfiguration failed for SPA in slot [int], bay [int] during Minimal Disruptive Restart.
Explanation During Minimal Disruptive Restart, fugu reconfiguration error has occured. This indicates an error and the SPA will be reset as normal and impact traffic.
Recommended Action Open a case with Cisco Technical Assistance Center for further assistance.
%ETH_SPA_GILA_FUGU-3-RESTART_FAILURE : Fugu restart failed for SPA in slot [int], bay [int] with error [dec] during Minimal Disruptive Restart.
Explanation During Minimal Disruptive Restart, fugu restart error has occured. This indicates an error and the SPA will be reset as normal and impact traffic.
Recommended Action Open a case with Cisco Technical Assistance Center for further assistance.
%ETH_SPA_GILA_FUGU-3-SPI4_MCALPRTY_ERR : [chars] : [chars] Calender memory Parity error
Explanation An internal SPI4 error (SPI4 calender memory parity error) occurred in the SPA.
Recommended Action If the issue persists, it may be a case of bad hardware. Please open a case with Cisco technical support personnel for further assistance.
%ETH_SPA_GILA_FUGU-3-SPI4_MCALRBPRTY_ERR : [chars] : [chars] Calender memory read back Parity error
Explanation An internal SPI4 error (SPI4 Calender memory read back parity error) occurred in the SPA.
Recommended Action Try reseating the SPA and if the issue persists, open a case with the Cisco Technical Assistance Center.
%ETH_SPA_GILA_FUGU-3-SPI4_MCNTPRTY_ERR : [chars] : [chars] Memory Parity error
Explanation An internal SPI4 error (SPI4 Control FIFO Memory Parity error) occurred in the SPA.
Recommended Action If the issue persists, open a case with Cisco Technical Assistance Center for further assistance.
%ETH_SPA_GILA_FUGU-3-SPI4_MDATAPRTY_ERR : [chars] : [chars] Memory Parity error
Explanation An internal SPI4 error (SPI4 DATA FIFO Memory Parity error) occured in the SPA.
Recommended Action If the issue persists, open a case with Cisco Technical Assistance Center for further assistance.
%ETH_SPA_GILA_FUGU-3-SPI4_OVF_ERR : [chars] : [chars] Overflow Error
Explanation An internal SPI4 error (SPI4 Overflow Error) occured in the SPA.
Recommended Action Open a case with Cisco Technical Assistance Center for further assistance.
%ETH_SPA_GILA_FUGU-3-SPI4_RDOOF_ERR : [chars] : [chars] Rdata Out of Frame error
Explanation An internal SPI4 error (SPI4 Rdata Out of Frame error) occured in the SPA.
Recommended Action If the issue persists, open a case with the Cisco Technical Assistance Center.
%ETH_SPA_GILA_FUGU-3-SPI4_SYNC_FAIL : [chars] : Sync check failed in [chars] SPI4 interafce
Explanation Synchronization check failed in the Gila/Fugu SPI4 interafce
Recommended Action Try reseating the SPA. If the issue persists, contact Cisco Technical Assistance Center.
%ETH_SPA_GILA_FUGU-3-TCAM_RECONFIG_FAILURE : Fugu TCAM reconfiguration failed for SPA in slot [int], bay [int] with error [dec], reconfig_needed [dec] during Minimal Disruptive Restart.
Explanation During Minimal Disruptive Restart, fugu tcam reconfiguration error has occure. This indicates an error and SPA will be reset as normal and impact traffic.
Recommended Action Open a case with Cisco Technical Assistance Center for further assistance.
%ETH_SPA_GILA_FUGU-3-TCAM_RESTART_FAILURE : TCAM restart failed for SPA in slot [int], bay [int] with error [dec] during Minimal Disruptive Restart.
Explanation During Minimal Disruptive Restart, fugu tcam restart has failed. This indicates an error and SPA will be reset as normal and impact traffic.
Recommended Action Open a case with Cisco Technical Assistance Center for further assistance.
%ETH_SPA_GILA_FUGU-3-VLAN_TCAM_ERR : TCAM programming error at offset [dec]
Explanation An error was encountered when programming the VLAN TCAM. Two tcam entries are seen to have the same logical address, so traffic drop will be seen on these subinterfaces
Recommended Action Reload the Linecard. If the issue persists, please open a case with Cisco TAC for further assistance.
%ETH_SPA_GILA_FUGU-6-ELT_IS_NEW : The element at address [dec] in [chars] tcam is found to be new during Minimal Disruptive Restart reconcilation.
Explanation During the reconcilation phase of Minimumal Disruptive Restart, an element was found to be present in the new IOS but not present in the old IOS image. This is not an error condition, the SPA driver will program this new entry into the hardware.
Recommended Action Open a case with Cisco Technical Assistance Center for further assistance
ETH_SPA_MAC
%ETH_SPA_MAC-3-INTR_MAX_BURST : Bursts of interrupts from [chars] have crossed maximum limit [dec] for port [dec]/[dec]/[dec]
Explanation Burst of interrupts that have crossed the maximum limit are detected by the SPA.
Recommended Action Check the interface configuration and receive signal characteristics. Also verify the XFP transceiver and receive signal path. Re-enable the interface after corrective action.
%ETH_SPA_MAC-3-PHY_RECONFIG_FAILURE : PHY reconfiguration failed for SPA in slot [int], bay [int] with error [dec] during Minimal Disruptive Restart. This indicates an error and the SPA will be reset as normal and impact traffic.
Explanation None
Recommended Action Open a case with Cisco Technical Assistance Center for further assistance.
%ETH_SPA_MAC-3-PHY_RESTART_FAILURE : PHY restart failed for SPA in slot [int], bay [int] with error [dec] during Minimal Disruptive Restart.
Explanation During Minimal Disruptive Restart, phy restart error has occured. This indicates an error and the SPA will be reset as normal and impact traffic.
Recommended Action Open a case with Cisco Technical Assistance Center for further assistance.
%ETH_SPA_MAC-3-RECONFIG_FAILURE : MAC reconfiguration failed for SPA in slot [int], bay [int] during Minimal Disruptive Restart.
Explanation During Minimal Disruptive Restart, a mac reconfiguration error has occured.This indicates an error and the SPA will be reset as normal and impact traffic.
Recommended Action Open a case with Cisco Technical Assistance Center for further assistance.
%ETH_SPA_MAC-3-RESTART_FAILURE : MAC restart failed for SPA in slot [int], bay [int] with error [dec] during Minimal Disruptive Restart.
Explanation During Minimal Disruptive Restart, mac restart error has occured. This indicates an error and the SPA will be reset as normal and impact traffic.
Recommended Action Open a case with Cisco Technical Assistance Center for further assistance.
%ETH_SPA_MAC-3-SPI4_ERROR : [chars] : SPI4 Error occured in the MAC
Explanation SPI4 error occured in the MAC.
Recommended Action SPI error reported in the SPA. Try reseating the SPA if the error occurs multiple times. If you further need assistance please open a case with Cisco TAC at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl
%ETH_SPA_MAC-3-SPI4_SINK_INIT_ERR : [chars] : Marvel spi4.1 sink init failed PL410 global status <lock> not set
Explanation An internal SPI4 error occurred in the SPA.
Recommended Action If the issue persists, return the SPA using the RMA process.
%ETH_SPA_MAC-3-UNREC_ECC_ERR : [chars] : An unrecoverable ECC error occured in the MAC
Explanation An unrecoverable ECC error occured in the MAC.
Recommended Action Try to reload the SPA to recover from the failure. If the problem persist, contact Cisco Technical Assistance Center for assistance.
%ETH_SPA_MAC-6-INTR_BURST : Interrupts from [chars] have crossed burst limit of [dec] in [dec] msec for port [dec]/[dec]/[dec]
Explanation Interrupts that have crossed the burst limit are detected by the SPA.
Recommended Action Check the interface configuration and receive signal characteristics. Also verify the XFP transceiver and receive signal path. Re-enable the interface after corrective action.
ETH_SPA_SERDES
%ETH_SPA_SERDES-3-RECONFIG_FAILURE : Serdes reconfiguration failed for SPA in slot [int], bay [int] during Minimal Disruptive Restart.
Explanation During Minimal Disruptive Restart, serdes reconfiguration error has occured. This indicates an error and the SPA will be reset as normal and impact traffic.
Recommended Action Open a case with Cisco Technical Assistance Center for further assistance.
%ETH_SPA_SERDES-3-RESTART_FAILURE : Serdes restart failed for SPA in slot [int], bay [int] during Minimal Disruptive Restart.
Explanation During Minimal Disruptive Restart, serdes restart error has occured. This indicates an error and the SPA will be reset as normal and impact traffic.
Recommended Action Open a case with Cisco Technical Assistance Center for further assistance.
ETHERCHANNEL
%ETHERCHANNEL-2-PROXY_IPC_INIT_FAILED : QFP Etherchannel Proxy IPC interface initialization failure (result: [dec]).
Explanation Cisco internal software error. QFP Etherchannel initialization detected that the Proxy IPC interface initialization failed. The EC Bundle interfaces 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%ETHERCHANNEL-3-INV_PROXY_MSG : QFP ETHERCHANNEL Proxy received invalid Message ID [dec]
Explanation Cisco internal software error. QFP Etherchannel Proxy received an invalid Message ID. This message will be ignored.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%ETHERCHANNEL-3-LOCK_ERROR : QFP EC Lock Failure: retval:[dec] tries[dec]
Explanation Cisco internal software error. QFP EC Lock Failure locking attempt failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%ETHERCHANNEL-3-LOCK_STATE_ERROR : QFP EC Lock State Failure: retval:[dec]
Explanation Cisco internal software error. QFP EC Lock State Failure Illegal lock state
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%ETHERCHANNEL-3-PROXY_IPC_ALLOC_FAIL : QFP ETHERCHANNEL Proxy ([chars]) response lost due to buffer allocation failure (Interface [chars])
Explanation Cisco internal software error. QFP ETHERCHANNEL Proxy message processing detected a IPC buffer allocation failure during response processing. The associated ETHERCHANNEL interface may not be fully functional as a result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%ETHERCHANNEL-3-PROXY_SID_UPDATE_COMPLETE_ERROR : QFP EC Proxy ([chars]) SID Update Complete w/o Preceeding Lock (Interface [chars], SID: [hex])
Explanation Cisco internal software error. QFP EC Proxy message processing detected a Bundle Schedule SID update sequence error. One or more interface schedules could have been affected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%ETHERCHANNEL-3-PROXY_SID_UPDATE_LOCK_ERROR : QFP EC Proxy ([chars]) Multiple SID Update Locks to same interface (Interface [chars], SID: [hex])
Explanation Cisco internal software error. QFP EC Proxy message processing detected a Bundle Schedule SID update sequence error. One or more interface schedules could have been affected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
ETHERNET_LACP
%ETHERNET_LACP-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.
%ETHERNET_LACP-3-ISSU_SENDFAILED : LACP ISSU: send message failed, rc = [dec]
Explanation The sending of a message has failed. This is an informational message only.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%ETHERNET_LACP-4-ISSU_INCOMPATIBLE : lacp-issu-compat: returned FALSE
Explanation The ISSU compatibility matrix check has failed. This is an informational message only.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%ETHERNET_LACP-4-ISSU_XFORM : [chars]: failed, rc=[chars]
Explanation The ISSU transform has failed. This is an informational message only.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%ETHERNET_LACP-4-RF_CLIENT_BUNDLE : LACP HA: Unable initiate checkpoint bundle mode.
Explanation LACP is unable to initialize checkpoint bundle mode. This is an informational message only.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%ETHERNET_LACP-4-RF_CLIENT_INIT : LACP HA: Unable to initiate RF client.
Explanation LACP is unable to initialize as a RF client. This is an informational message only.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
ETHERNET_MLACP
%ETHERNET_MLACP-3-PEER_ICCP_VERSION_INCOMPATIBLE : Peer ICCP version [dec] is incompatible with local ICCP version [dec].
Explanation mLACP peer is running with a different version of ICCP. Incompatible ICCP would prevent mLACP from working properly.
Recommended Action Reboot peer with identical IOS version would correct the issue. Compatible ICCP version between different IOS images can still be achieved by doing show lacp multichassis group on the both devices to check if ICCP versions are compatible. If ICCP versions are incompatible, repeat IOS image loading and CLI above until a compatible image is loaded.
%ETHERNET_MLACP-3-SYS_CFG_DUPL_ID : Remote mLACP peer has duplicate mLACP node-id [dec]
Explanation A remote mLACP peer is configured with the same mLACP node-id as this device.
Recommended Action Reconfigure the mLACP node-id to be unique between the two devices with the mlacp node-id configuration command. Refer to the mLACP configuration section of the Cisco IOS documentation for more information on configuring mLACP.
%ETHERNET_MLACP-3-SYS_CFG_INVALID_ID : Received invalid mLACP node-id [dec] from peer
Explanation A remote mLACP peer is configured with an invalid mLACP node-id.
Recommended Action Reconfigure the peer to send a valid mLACP node-id with the mlacp node-id configuration command. Refer to the mLACP configuration section of the Cisco IOS documentation for more information on configuring mLACP.
%ETHERNET_MLACP-4-CORE_CONNECTED : mLACP has recovered from a core isolation failure. Attempting to recover [dec] LAGs in redundancy group [int]
Explanation mLACP has recovered from core isolation and has attempted to recover the LAGs in the redundancy group.
Recommended Action This message may not require any action. However the show lacp multi-chassis group and show lacp multi-chassis port-channel commands may be used to verify the state of the mLACP port-channels. Reference the mLACP section of the IOS documentation for details on core isolation failures and related configuration commands.
%ETHERNET_MLACP-4-CORE_ISOLATION : mLACP Core isolation failure: Attempting to failover [dec] LAGs in redundancy group [int]
Explanation mLACP has detected isolation from the core and has attempted to failover.
Recommended Action Use the show interchassis redundancy command to determine which core facing interface has triggered the isolation failure. Correct the failure for the given interface, this will clear the mLACP core isolation failure. Reference the mLACP section of the IOS documentation for more information on core isolation failures and related configuration commands.
%ETHERNET_MLACP-4-ICRM_CLIENT_RECV_BAD_LEN : Received an mLACP TLV with bad length [dec], total message length [dec]
Explanation The mLACP TLV length is longer than the total message length.
Recommended Action Issue the show version command on the local and remote devices to get the versions of IOS that are running. Reference the mLACP section of the IOS documentation to verify that mLACP is compatible between the IOS versions on the two devices. If the versions are compatible and the message still appears then please contact your Cisco technical support representative. Provide the representative with the exact message being seen as well as the output of the following commands, show version, show run, show lacp multi-chassis group, and show lacp multi-chassis port-channel.
%ETHERNET_MLACP-4-ICRM_CLIENT_RECV_NO_TYPELEN : Received an mLACP TLV without a type and/or length field ([dec])
Explanation mLACP received an improperly formatted TLV from the peer. As a result the local and peer devices may have mismatched state data.
Recommended Action Issue the show version command on the local and remote devices to get the versions of IOS that are running. Reference the mLACP section of the IOS documentation to verify that mLACP is compatible between the IOS versions on the two devices. If the versions are compatible and the message still appears then please contact your Cisco technical support representative and provide the representative with the exact error message being seen as well as the versions of IOS from both devices.
%ETHERNET_MLACP-4-ICRM_CLIENT_RECV_REJ : Received rejected mLACP TLV from peer with message ID [dec]
Explanation A remote mLACP peer has rejected an mLACP TLV.
Recommended Action Issue the show version command on the local and remote devices to get the versions of IOS that are running. Reference the mLACP section of the IOS documentation to verify that mLACP is compatible between the IOS versions on the two devices. If the versions are compatible and the message still appears then please contact your Cisco technical support representative and provide the representative with the exact error message being seen as well as the versions of IOS from both devices.
%ETHERNET_MLACP-4-PC_CHANGE : mLACP [chars] status changed to [chars]
Explanation A mLACP port-channel state change event has occurred. This might have been caused by a mLACP failure or recovery event on the local or peer POA in the same redundancy group. It is normal to get these messages during provisioning and administrative actions on the mLACP port-channel.
Recommended Action User should debug further to analyze root cause of the event. Use show redundancy interchassis , show lacp multi-chassis port-channel, show lacp multi-chassis group and show lacp internal on both POAs to check mLACP port-channel health. If any failure exists, appropriate actions should be taken to recover port-channel from failure. If failure persists then please contact your Cisco technical support representative and provide the collected information.
%ETHERNET_MLACP-4-PEER_DISCONNECT : An mLACP peer has disconnected from redundancy group [int], attempting to reconnect
Explanation mLACP has detected that a peer device from the specified redundancy group has disconnected. mLACP will attempt to reconnect to the device until successful.
Recommended Action This message is typically caused by a configuration event on the peer router, and so no action may be necessary. However if this message is unexpected then issue the show redundancy interchassis command on both the local and peer mLACP devices to determine which peer member IP has lost communication. Use this information to further debug the network communication issue, and re-enable communication with the peer. Reference the mLACP section of the IOS documentation for more information on peer down failures.
%ETHERNET_MLACP-4-PEER_DOWN : mLACP Peer down failure: Attempting to make [dec] local LAGs active in redundancy group [int]
Explanation mLACP has detected a peer down failure and has attempted to make the local port-channels become active.
Recommended Action The peer down failure should be corrected by re-enabling communication with the peer mLACP device. Use the show redundancy interchassis command on both the local and peer mLACP devices to determine which peer member IP has lost communication. Use this information to further debug the network communication issue, and re-enable communication with the peer. Reference the mLACP section of the IOS documentation for more information on peer down failures.
%ETHERNET_MLACP-4-PEER_RECONNECT_FAILED : The attempt to reconnect to the peer in redundancy group [int] has failed
Explanation After an mLACP peer device disconnected, an attempt was made to reconnect, however that attempt has failed.
Recommended Action To reinitialize the connection, unconfigure mlacp interchassis group from the port-channel, and then reconfigure it. After doing that, issue show redundancy interchassis to get the peer member IP connection status and the mLACP connection state. If the peer member IP connection status is not CONNECTED then there is a more basic communication issue that needs to be fixed. Otherwise if the peer member IP is CONNECTED but the mLACP state is not CONNECTED, then there could be a software issue. In that case collect the output of show redundancy interchassis, show lacp multi-chassis group, and show lacp multi-chassis port-channel. Then please contact your Cisco technical support representative and provide the collected information.
%ETHERNET_MLACP-4-PEER_UP : mLACP has recovered from a peer down failure in redundancy group [int]
Explanation mLACP is now in communication with the peer device, and has recovered from a previous peer down failure.
Recommended Action This message may not require any action. However the show lacp multi-chassis group and show lacp multi-chassis port-channel commands may be used to verify the state of the mLACP port-channels. Reference the mLACP section of the IOS documentation for details on peer down failures and related configuration commands.
%ETHERNET_MLACP-6-PEER_CONNECT : mLACP peer is now connected in redundancy group [int]
Explanation This message indicates that the local mLACP device is now connected to a peer device in the specified redundancy group.
Recommended Action No action is required. To view the peer information the command show lacp multi-chassis port-channel or show lacp multi-chassis group may be issued.
ETHERCHANNEL_LB
%ETHERCHANNEL_LB-3-MSG_SEND_FAIL : The load-balance message [dec] has failed to send
Explanation The load-balancing feature has detected an error while trying to send an internal message.
Recommended Action If this message was the result of performing a configuration command, then try unconfiguring and reconfiguring the same command. If the error message continues to be displayed then it may indicate that the system is low on memory. The show memory free command should be used to check if the system has sufficient available memory. If the system appears to have available memory and the error continues to be displayed, then please contact your Cisco technical support representative and provide the representative with the exact error message being seen as well as the version of IOS being used.
%ETHERCHANNEL_LB-3-XDR_MSG_XMIT_FAIL : Failed to transmit XDR message of size [dec] to slot [dec]
Explanation An error occurred while attempting to send a load-balancing XDR message to the specified slot.
Recommended Action Because the message failed to send, the specified slot may now be out of sync with the rest of the system. To correct the issue the card in the specified slot may be rebooted, at which point the full configuration will be re-synced with the card in that slot. If the specified slot is zero, then that message was intended for cards in all slots, and the router should be reloaded to re-sync the entire system.
ETHER_LMI
%ETHER_LMI-6-MISMATCHED_VLAN_CONFIGURED : VLAN [chars] configured but not in VLAN mapping for UNI [chars]
Explanation VLANs configured on UNI but do not exist according to VLAN mapping received from Network via Ethernet LMI.
Recommended Action Verify configurations of VLANs on UNI to match those assigned.
%ETHER_LMI-6-MISMATCHED_VLAN_NOT_CONFIGURED : VLAN [chars] not configured but in VLAN mapping for UNI [chars]
Explanation VLAN mapping received from Network via Ethernet LMI do not match those which are configured on the UNI.
Recommended Action Verify configurations of VLANs on UNI to match those assigned.
ETHER_LMI_HA
%ETHER_LMI_HA-2-GET_BUFFER : Ether LMI ISSU client failed to get buffer for message. Error: [dec] ([chars])
Explanation The Ether LMI HA client failed to get buffer space for building chkpt message. Message cannot be sent to standby device. If a problem occurs, the standby device cannot be brought up properly.
Recommended Action LOG_STD_SH_CMD_ACTION( show logging and show checkpoint client)
%ETHER_LMI_HA-2-INIT : Ether LMI ISSU client initialization failed to [chars]. Error: [dec] ([chars])
Explanation The Ether LMI 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%ETHER_LMI_HA-2-SEND_NEGO_FAILED : Ether LMI ISSU client failed to send negotiation message. Error: [dec] ([chars])
Explanation The Ether LMI 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)
%ETHER_LMI_HA-2-SESSION_NEGO : Ether LMI ISSU client encountered unexpected client nego_done. Error: [dec] ([chars])
Explanation An ISSU-compliant client transitions through a series of internal states. The Ether LMI 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>)
%ETHER_LMI_HA-2-SESSION_REGISTRY : Ether LMI ISSU client failed to register session information. Error: [dec] ([chars])
Explanation The Ether LMI 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>)
%ETHER_LMI_HA-3-INVALID_SESSION : Ether LMI ISSU client does not have a valid registered session.
Explanation The Ether LMI 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>)
%ETHER_LMI_HA-3-MSG_NOT_OK : Ether LMI ISSU client 'Message Type [dec]' is not compatible
Explanation The Ether LMI 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>)
%ETHER_LMI_HA-3-MSG_SIZE : Ether LMI ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] ([chars])
Explanation The Ether LMI ISSU client failed to calculate the MTU for the specified message. The Ether LMI ISSU client will 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>)
%ETHER_LMI_HA-3-SESSION_UNREGISTRY : Ether LMI ISSU client failed to unregister session information. Error: [dec] ([chars])
Explanation The Ether LMI 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>)
%ETHER_LMI_HA-3-TRANSFORM : Ether LMI ISSU client [chars] transform failed for 'Message Type [dec]'. Error: [dec] ([chars])
Explanation The Ether LMI 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 Ether LMI 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>)
ETHERNET_OAM
%ETHERNET_OAM-2-CRIT_ERR : The Ethernet OAM protocol has encountered the critical error: [chars].
Explanation The protocol has run into a critical error. The reason should be given in the brackets.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%ETHERNET_OAM-2-GET_BUFFER : ETHERNET OAM ISSU client failed to get buffer for message. Error: [dec] ([chars])
Explanation The ETHERNET OAM 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)
%ETHERNET_OAM-2-INIT : ETHERNET OAM ISSU client initialization failed to [chars]. Error: [dec] ([chars])
Explanation The ETHERNET OAM 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%ETHERNET_OAM-2-SEND_NEGO_FAILED : ETHERNET OAM ISSU client failed to send negotiation message. Error: [dec] ([chars])
Explanation The ETHERNET OAM 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)
%ETHERNET_OAM-2-SESSION_NEGO : ETHERNET OAM ISSU client encountered unexpected client nego_done. Error: [dec] ([chars])
Explanation An ISSU-compliant client transitions through a series of internal states. The ETHERNET OAM 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>)
%ETHERNET_OAM-2-SESSION_REGISTRY : ETHERNET OAM ISSU client failed to register session information. Error: [dec] ([chars])
Explanation The ETHERNET OAM 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>)
%ETHERNET_OAM-3-INVALID_SESSION : ETHERNET OAM ISSU client does not have a valid registered session.
Explanation The ETHERNET OAM 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>)
%ETHERNET_OAM-3-LOOPBACK_ERROR : Loopback operation on interface [chars] has encountered an error([chars]).
Explanation Because of the specified error, the loopback operation has ended abnormally.
Recommended Action No action is required.
%ETHERNET_OAM-3-MSG_SIZE : ETHERNET OAM ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] ([chars])
Explanation The ETHERNET OAM ISSU client failed to calculate the MTU for the specified message. The ETHERNET OAM 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>)
%ETHERNET_OAM-3-SESSION_UNREGISTRY : ETHERNET OAM ISSU client failed to unregister session information. Error: [dec] ([chars])
Explanation The ETHERNET OAM 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>)
%ETHERNET_OAM-3-TRANSFORM_FAIL : ETHERNET OAM ISSU client [chars] transform failed for 'Message Type [dec]'. Error: [dec] ([chars])
Explanation The ETHERNET OAM 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 ETHERNET OAM 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>)
%ETHERNET_OAM-4-ISSU_INCOMPATIBLE : ether_oam-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%ETHERNET_OAM-5-EVENTTLV : [chars] is received from the remote client on interface [chars].
Explanation An Event TLV is received from the remote OAM client. It must have detected errors in receiving frames from this local interface.
Recommended Action No action is required.
%ETHERNET_OAM-5-LINK_MONITOR : [chars] detected over the last [chars] on interface [chars].
Explanation A monitored error has been detected to have crossed the user-specified threshold.
Recommended Action No action is required.
%ETHERNET_OAM-6-CRITICAL_EVENT : The client on interface [chars] has received a Critical Event indication from its remote peer (action = [chars])
Explanation An OAMPDU has been received from the remote client that indicates a Critical Event has occurred. The indicated action will be performed. If the action is error-block the link will go into error-block state, where data traffic is blocked but link-oam can still be exchanged. If the action is error-disable, the link is brought down.
Recommended Action Investigate the issue on the remote peer
%ETHERNET_OAM-6-CRITICAL_EVENT_CLEAR : The client on interface [chars] has received a clear of the Critical Event indication from its remote peer (action = [chars])
Explanation An OAMPDU has been received from the remote client that indicates that the Critical Event condition previously seen has cleared. If the action was error-block, traffic on the link will now be re-enabled. Error-disable state can only be cleared by performing a shut/no shut of the interface.
Recommended Action No action is required.
%ETHERNET_OAM-6-DYING_GASP : The client on interface [chars] has received a Dying Gasp indication from its remote peer (failure reason = [chars], action = [chars])
Explanation An OAMPDU has been received from the remote client that indicates a Dying Gasp, which may signal that the remote client is about to go down. The indicated action will be performed. If the action is error-block the link will go into error-block state, where data traffic is blocked but link-oam can still be exchanged. If the action is error-disable, the link is brought down.
Recommended Action Investigate the issue on the remote peer
%ETHERNET_OAM-6-DYING_GASP_CLEAR : The client on interface [chars] has received a clear of the Dying Gasp indication from its remote peer (action = [chars])
Explanation An OAMPDU has been received from the remote client that indicates that the Dying Gasp condition previously seen has cleared. If the action was error-block, traffic on the link will now be re-enabled. Error-disable state can only be cleared by performing a shut/no shut of the interface.
Recommended Action No action is required.
%ETHERNET_OAM-6-ENTER_SESSION : The client on interface [chars] has entered the OAM session.
Explanation Ethernet OAM client on the specified interface has detected a remote client and has entered the OAM session.
Recommended Action No action is required.
%ETHERNET_OAM-6-EXIT_SESSION : The client on interface [chars] has left the OAM session.
Explanation Ethernet OAM client on the specified interface has experienced some state change.
Recommended Action No action is required.
%ETHERNET_OAM-6-LINK_FAULT : The client on interface [chars] has received a Link Fault indication from its remote peer (action = [chars])
Explanation An OAMPDU has been received from the remote client that indicates a Link Fault has been detected. This indicates a fault has occurred in the receive direction of the sending client. The indicated action will be performed. If the action is error-block the link will go into error-block state, where data traffic is blocked but link-oam can still be exchanged. If the action is error-disable, the link is brought down.
Recommended Action Check the wiring between the two interfaces.
%ETHERNET_OAM-6-LINK_FAULT_CLEAR : The client on interface [chars] has received a clear of the Link Fault indication from its remote peer (action = [chars])
Explanation An OAMPDU has been received from the remote client that indicates that the Link Fault condition previously seen has cleared. If the action was error-block, traffic on the link will now be re-enabled. Error-disable state can only be cleared by performing a shut/no shut of the interface.
Recommended Action No action is required.
%ETHERNET_OAM-6-LINK_TIMEOUT : The client on interface [chars] has timed out and exited the OAM session.
Explanation The Ethernet OAM client on the specified interface has not received any OAMPDUs in the number of seconds for timeout that were configured by the user. The client has exited the OAM session.
Recommended Action No action is required.
%ETHERNET_OAM-6-LOOPBACK : Interface [chars] has [chars] the [chars] loopback mode.
Explanation The specified interface has entered or exited loopback mode because of protocol control or an external event, such as the interface link going down.
Recommended Action No action is required.
ETHERNET_PROXY
%ETHERNET_PROXY-2-PROXY_IPC_INIT_FAILED : CPP ETHERNET Proxy IPC interface initialization failure (result: [dec]).
Explanation Cisco internal software error. CPP ETHERNET Proxy initialization detected that the IPC interface initialization failed. CPP ETHERNET 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%ETHERNET_PROXY-3-PROXY_BAD_MSG : CPP ETHERNET Proxy received bad length message type [dec]
Explanation Cisco internal software error. CPP ETHERNET 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%ETHERNET_PROXY-3-PROXY_INV_MSG : CPP ETHERNET Proxy received invalid message type [dec]
Explanation Cisco internal software error. CPP ETHERNET Proxy received an invalid message type 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%ETHERNET_PROXY-3-PROXY_IPC_ALLOC_FAILED : CPP ETHERNET Proxy [chars] message lost due to message buffer allocation failure., MSGDEF_LIMIT_MEDIUM
Explanation Cisco internal software error. CPP ETHERNET 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%ETHERNET_PROXY-3-PROXY_IPC_NO_HDLR : CPP ETHERNET Proxy received unregistered message type [dec]
Explanation Cisco internal software error. CPP ETHERNET Proxy received a message from control plane but there is no registered handler. 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%ETHERNET_PROXY-3-PROXY_IPC_SEND_FAILED : CPP ETHERNET Proxy [chars] message lost due to message sent failure (result: [dec]).
Explanation Cisco internal software error. CPP ETHERNET 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
ETHER_PLATFORM_SW
%ETHER_PLATFORM_SW-3-BD_NULL : Unable to get bridge-domain [dec] information for EFP [dec]
Explanation The software dataplane was unable to get the bridge-domain information for the EFP.
Recommended Action This error may be transient. If the error persists you may need to reload the router.
%ETHER_PLATFORM_SW-3-DOT1AH_CHNK_LCK_FAILED : Unable to lock memory while learning C-MAC to B-MAC mapping
Explanation The Ethernet Software Platform was unable to lock a particular piece of memory while attempting to learn a C-MAC to B-MAC mapping
Recommended Action This error may be transient. If the error persists you may need to reload the router.
%ETHER_PLATFORM_SW-3-DOT1AH_DEL_MAP_FAILED : Unable to remove 802.1ah mapping entry for B-MAC [enet], C-MAC [enet].
Explanation The Ethernet Software Platform was unable to remove an 802.1ah mapping entry from the tree of entries.
Recommended Action This error may be transient. If the error persists you may need to reload the router.
%ETHER_PLATFORM_SW-3-DOT1AH_PROC_ENQ_FAILED : Unable to enqueue a request to learn a C-MAC to B-MAC mapping
Explanation An error occurred while trying to enqueue a request to learn a C-MAC to B-MAC mapping.
Recommended Action This error may be transient. If the error persists you may need to reload the router.
%ETHER_PLATFORM_SW-3-EFP_CANNOT_CLEAR_DIM : Unable to clear EFP's encapsulation data
Explanation An error occurred while trying to clear the encapsulation data for an EFP.
Recommended Action Enable debugging with 'debug ethernet service instace'. Retry the operation that caused the error to see if additional debugging messages are provided. If the error persists you may need to reload the router.
%ETHER_PLATFORM_SW-3-NO_PD_EFP : Unable to find software platform EFP information for EFP ID [dec]
Explanation The software dataplane was unable to get the platform dependent EFP information for the EFP with the given ID.
Recommended Action This error may indicate a bug in the software dataplane implementation. If the error occurs after a specific configuration was performed then precisely record those configuration steps. Contact your Cisco technical support representative and provide the gathered information.
%ETHER_PLATFORM_SW-3-REWRITE_FAILED : Unable to apply rewrite to packet
Explanation An error occurred while trying to perform an ingress rewrite operation on a frame.
Recommended Action This error may be transient. If the error persists you may need to reload the router.
ETHER_SERVICE
%ETHER_SERVICE-3-EFP_DEBUG_INIT_FAILURE : The Ether Infra Trace and Debug Library Failed to initialize successfully due to error: [int]
Explanation All trace and debug may not work
Recommended Action No Action
%ETHER_SERVICE-3-ETHER_CHAN_SERV_INSTANCE_POLICY_REMOVED : [chars] service policy [chars] has been removed from service instance [dec] of ethernet channel [chars] due to failure to install the policy on member link [chars].
Explanation The member link does not support the service policy or installation failed due to resources limitation at the time.
Recommended Action Check for any error message that indicates incompatiblity between the policy and the member link. Remove the member link from the ethernet channel and reconfigure the policy on the service instance. If the problem persists, copy the error exactly as it appears and report it to your technical support representative.
%ETHER_SERVICE-3-EFP_INVALID_TYPE : [chars] : [chars] is INVALID
Explanation invalid type
Recommended Action Copy the error and send it to TAC
%ETHER_SERVICE-3-EFP_NO_MEMORY : [chars] : memory allocation failed for [chars]
Explanation memory allocation failed
Recommended Action 'show proc mem' or 'show buffs' to check if memory or buffer is full. shutdown unused tasks or reset cards usually can recover those memory leak problem. Copy the error and send it to TAC if those actions does not help.
%ETHER_SERVICE-3-EFP_NULL_POINTER : [chars] : [chars] pointer is NULL
Explanation NULL pointer
Recommended Action Copy the error and send it to TAC
%ETHER_SERVICE-4-UNSUP_MIRPENABLE : %%Not supported since no ethernet mac-flush notification mirp command is configured.
Explanation no ethernet mac-flush notification mirp is configured.
Recommended Action Configure ethernet mac-flush notification mirp command.
%ETHER_SERVICE-6-ERR_DISABLED : [chars] -shutdown service instance [dec] at [chars]
Explanation Service instance shutdown due to errdisable
Recommended Action No Action
%ETHER_SERVICE-6-EVC_STATUS_CHANGED : status of [chars] changed to [chars]
Explanation EVC status has changed
Recommended Action No Action
%ETHER_SERVICE-6-EVC_VLAN_NOT_CONFIGURED : VLANs [chars] not configured at [chars] but is in a CEVLAN/EVC map
Explanation VLANs part of the CEVLAN/EVC map for an EVC associated to an interface but the interface doesn't have those VLANs configured
Recommended Action Verify configurations of VLANs on the interface
%ETHER_SERVICE-6-UPDOWN : Service instance [dec] on interface [chars] changed to [chars]
Explanation Service instance shutdown due to errdisable
Recommended Action No Action
ETHER_SERVICE_IPC
%ETHER_SERVICE_IPC-3-IPCPORT_CREATE : Unable to create IPC port ([chars]).
Explanation Ethernet Service was unable to create an IPC port
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%ETHER_SERVICE_IPC-3-IPCPORT_REGISTER : Unable to register IPC port ([chars]).
Explanation Ethernet Service was unable to register an IPC port
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%ETHER_SERVICE_IPC-3-IPCPORT_REMOVE : Unable to remove IPC port ([chars]).
Explanation Ethernet Service was unable to remove an IPC port
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%ETHER_SERVICE_IPC-3-IPCPROCESSES : Unable to create IPC processes on ([chars]).
Explanation Ethernet Service was unable to create IPC processes
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%ETHER_SERVICE_IPC-3-IPC_RESP_ERROR : IPC send response error ([chars])
Explanation An error was detected in the response for an IPC message that was transmitted to the peer.
Recommended Action This error could be transient. If this error persists, copy the error message exactly as it appears, and report it to your technical support representative.
%ETHER_SERVICE_IPC-3-IPCSESSION : Unable to open an IPC session for communicating with ([chars]). Error: [chars]
Explanation This is an internal error
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%ETHER_SERVICE_IPC-3-IPC_TRANSMIT_FAILED : IPC message transmission failure ([chars])
Explanation An error was detected when transmitting an IPC message between Standby RP and SP. The failure most likely occurred because of a software error. The message output identifies the type of error that occurred.
Recommended Action This could be a transient error. If this error persists, copy the error message exactly as it appears, and report it to your technical support representative.
%ETHER_SERVICE_IPC-3-NOIPCDESC : Unable to allocate IPC descriptor for Ethernet Service on ([chars]).
Explanation This is an internal error
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%ETHER_SERVICE_IPC-3-NOMEM : Unable to allocate memory for Ethernet Service on ([chars]).
Explanation This is an internal error
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%ETHER_SERVICE_IPC-3-RMI_CALLBACK : Ethernet Infra encountered an error while processing a callback from the Resource Manager (RMI), [chars]
Explanation Ethernet Infra registers with the Resource Manager (RMI) to get status notifications about resources (such as IPC) and uses them to throttle the sending to messages to the peer. The Ethernet Infra encountered an error while processing a callback from RMI. This error most likely occured because of a software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show tech command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%ETHER_SERVICE_IPC-3-RMI_FAILED : Ethernet Infra failed to register with the Resource Manager (RMI), [chars]
Explanation Ethernet Infra registers with the Resource Manager (RMI) to get status notifications about resources (such as IPC) and uses them to throttle the sending to messages to the peer. The Ethernet Infra was unable to register itself with RMI and hence cannot throttle the sending of any messages. The system may still operate normally. This error most likely occured because of a software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show tech command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%ETHER_SERVICE_IPC-4-NOIPCDATA : IPC Message has no data area, ([chars])
Explanation Cannot find data area in an IPC message. This is a warning message, no action is required
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%ETHER_SERVICE_IPC-4-NOIPCPORT : IPC port is NULL, ([chars])
Explanation Ethernet Service cannot send the message as the IPC port information is NULL. This is a warning message, no action is required.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%ETHER_SERVICE_IPC-4-NOMESSAGE : Message is NULL, ([chars])
Explanation Cannot send the message as the message is NULL. This is a warning message, no action is required
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
EVENT
%EVENT-3-INSERT_FAILURE : Failed to insert [chars]
Explanation The event process failed to insert the newly created row in its linked list data structure
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%EVENT-3-NULL_ELEMENT : Null pointer in the watched queue for [chars] test
Explanation The process was woken up with an NULL element
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%EVENT-3-NULL_STRUCT : Null pointer to the [chars] structure
Explanation The process was woken up with an element, which had a null pointer to the test structure
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
EVENTLIB
%EVENTLIB-3-CPUHOG : [chars]: [int]ms, Traceback=[chars]
Explanation This error occurs when a particular event consumes an unfair share of the CPU that may degrade overall system response time.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show platform software process event command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%EVENTLIB-3-EVFDREAD : Event notification read failed with err [chars]
Explanation This occurs when we fail to read a thread notify event
Recommended Action Report this occurrence to Engineering. Use Topic to search for a similar DDTS. If you find none, write a DDTS for this problem.
%EVENTLIB-3-HISTELEM : elem[[int]] event: [chars] [chars] set: [int]ms unset: [int]ms hog check: [dec] caller: [IPV6 address] app-info: [chars]
Explanation This event element is part of a CPUHOG or TIMEHOG error, providing diagnostic details useful to engineering. Save all element messages along with the HOG error.
Recommended Action Report this occurrence to Engineering. Use Topic to search for a similar DDTS. If you find none, write a DDTS for this problem.
%EVENTLIB-3-HISTSUMM : dispatch start: [int]ms elapsed time: [int]ms detected hog: [int] set count: [int]
Explanation This event summary is part of a CPUHOG or TIMEHOG error, providing diagnostic details useful to engineering. Save this summary message along with the HOG error.
Recommended Action Report this occurrence to Engineering. Use Topic to search for a similar DDTS. If you find none, write a DDTS for this problem.
%EVENTLIB-3-RUNHOG : [chars]: [int]ms, Traceback=[chars]
Explanation This error occurs when a particular event consumes an overall unfair share of the CPU that may degrade overall system response time.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show platform software process event command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%EVENTLIB-3-TIMEHOG : [chars]: [int]ms, Traceback=[chars]
Explanation This error occurs when a particular event takes an unusually long time to complete. This may affect overall system response time.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show platform software process event command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
EVENT_TRACE
%EVENT_TRACE-3-CLOSE_FILE : Error closing file [chars]
Explanation The Event Trace subsystem can not close the specified file
Recommended Action No action required. This will not affect system functionality
%EVENT_TRACE-3-CONTINUOUS : Enable trace before setting continuous display
Explanation The specified event trace must be enabled before continuous display could occurs.
Recommended Action Enable the specified event trace.
%EVENT_TRACE-3-GROUP_ID : Duplicate registration of group-id [dec]
Explanation Software subsystem is trying to register a group id for event trace which has already been used by another subsystem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%EVENT_TRACE-3-NO_FILENAME : Dump file not specified.
Explanation No filename has been specified as output for the event trace.
Recommended Action You must specify the trace dump filename. To specify the trace dump filename, enter the monitor event-trace comp dump-file filename command in global configuration mode
%EVENT_TRACE-3-NO_MEM : Not enough memory for [dec] trace elements.
Explanation The system memory is insufficient for the number of trace elements specified.
Recommended Action Reduce the size of the event trace
%EVENT_TRACE-3-NO_TRACE_NAME : Invalid trace name [chars]
Explanation There is no trace buffer configured by the name entered.
Recommended Action Check whether there is an event trace buffer configured by the name entered and then enter the correct trace buffer name.
%EVENT_TRACE-3-NUM_ELEM : Number of trace element = [dec] is greater than number = [dec] allowed
Explanation The number of trace entries exceed the allowed amount
Recommended Action Reduce the number of trace entries
%EVENT_TRACE-3-OPEN : [chars]: Trace failed to open
Explanation Initialization of the specified event trace has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%EVENT_TRACE-3-OPEN_FILE : Couldn't open [chars]...
Explanation The Event Trace subsystem could not open a file for the specified event trace dump.
Recommended Action If a file by the same name already exists, rename the dump file or remove the existing file from the file system.
%EVENT_TRACE-3-RESIZE : Enable trace before resizing
Explanation The specified event trace must be enabled before resizing occurs.
Recommended Action Enable the specified event trace.
%EVENT_TRACE-3-SIZE_ELEM : Size of trace element = [dec] is greater than size = [dec] allowed
Explanation The size of the specified individual trace entry is greater than the allowed size.
Recommended Action Reduce the individual trace entry size so as not to exceed the max while initializing the event trace
%EVENT_TRACE-3-SIZE_FILENAME : Trace filename size = [dec] greater than size = [dec] allowed
Explanation The length of the specified Event Trace filename exceeds the allowed.
Recommended Action Shorten the filename.
%EVENT_TRACE-3-WRITE_FILE : Error writing to file [chars]
Explanation Event trace is not able to write to the specified filesystem
Recommended Action The filesystem might not be available. Try changing the destination filesystem and dumping there. If none work, copy the error message exactly as it and call your Cisco technical support representative
%EVENT_TRACE-6-ENABLE : Trace already enabled.
Explanation Specified event trace has already been enabled
Recommended Action This is a debug message only. No action is required.
%EVENT_TRACE-6-NO_FORMATTER : [chars]: no formatter provided, binary dumping.
Explanation No formatter function was provided during the initialization of the specified event trace.
Recommended Action No action is required.
EVTMON_PROXY
%EVTMON_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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%EVTMON_PROXY-4-PROXY_IPC_EVTMON_FEAT_UPDATE_FAILED : feature user failed to [chars] because of [chars]
Explanation Event monitor feature user failed to attach or detach.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%EVTMON_PROXY-4-PROXY_IPC_EVTMON_REC_UPDATE_FAILED : event record update failed
Explanation Event monitor failed to attach or detach event record.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%EVTMON_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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
EZMAN_CLIENT
%EZMAN_CLIENT-2-ECC_DOUBLE_BIT_ERROR : Double bit ECC errors observed. MIP100 is going to be reloaded to recover
Explanation ECC error observed on the NP device.Reset the NP Device.
Recommended Action This error is usually self-correcting. If the problem persists, the MIP100 hardware may need to be replaced.
%EZMAN_CLIENT-3-ECC_SINGLE_BIT_ERROR : Single bit ECC error
Explanation ECC error observed on the NP device.Reset the NP Device.
Recommended Action This error is usually self-correcting. If the problem persists, the MIP100 hardware may need to be replaced.
%EZMAN_CLIENT-3-OBJECT_FAIL : Failed to bringup [chars]. Failure reason is [chars]
Explanation Bringup of object(NP/Bay/Interface) has failed in EZMAN. This can be due to any hardware/software failures and can be a serious error
Recommended Action Restart the Linecard.
%EZMAN_CLIENT-5-EZ_CLIENT_VLAN_FULL : TCAM Full VLAN is not Able to add
Explanation Rx Sync Failed for Interlaken, Status Timer Expired. So, Resetting the Rx Interlaken Core
Recommended Action No user action is required.
EZMAN_INFRA
%EZMAN_INFRA-3-PLATFORM_ID_ERR : Invalid HW Part number([dec]) and HW Revision([dec])
Explanation HW Part number and revision read from the IDPROM are not showing up expected values which means the IDPROM is either corrupted or incorrectly programmed.
Recommended Action Possible Hardware issue. Change the hardware.
EZMAN_RM
%EZMAN_RM-3-SERDES_AUTOTUNE_FAIL : Serdes Autotune [chars] on lane [dec]
Explanation NP5 Serdes RX is unable to autotune to the peer device's TX. This is a physical layer issue between NP5 and peer device.
Recommended Action OIR the Host-card if possible.
F
FARM_DSPRM
%FARM_DSPRM-4-NOC5510WARN : dsp service dspfarm can not be configured for this card type.
Explanation There is C549 NM-HDV card configured for dspfarm service. Only one dspfarm card type is allowed.
Recommended Action If C5510 card type dspfarm is desired then remove C549 NM-HDV dspfarm service and reconfigure dspfarm service for this card.
%FARM_DSPRM-6-CALLDROPINFO : dspfarm active calls on this card dsp [dec] channel [dec] will be dropped.
Explanation The card has been removed. Dspfarm active calls on this card will be dropped.
Recommended Action No action is required.
%FARM_DSPRM-6-CARDINSERTINFO : dspfarm card slot [dec] is inserted.
Explanation dspfarm card type is inserted into the slot.
Recommended Action No action is required.
%FARM_DSPRM-6-CARDREMOVEINFO : dspfarm card slot [dec] is removed.
Explanation dspfarm card type is remvoed from the slot.
Recommended Action No action is required.
FEC_ISSU
%FEC_ISSU-3-BUFFER : FEC ISSU client failed to get buffer for message, error [dec]
Explanation FEC ISSU client failed to get buffer for building a negotiation message. Hence, it can send the negotiation message to the standby unit. When there is a problem in the negotiaiton the standby unit can not be brought up.
Recommended Action LOG_STD_SH_CMD_ACTION(show logging and show checkpoint client)
%FEC_ISSU-3-CAPABILITY : FEC ISSU client [chars]
Explanation FEC SWITCH ISSU client observed an error during capability negotiaiton. When this error happens there is a mismatch between the client capability between the active and standby unit.
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>)
%FEC_ISSU-3-INIT : FEC ISSU client initialization failed at [chars], error [chars]
Explanation FEC ISSU client could not be initiailzed, this will cause catstrophic failure when ISSU upgrade or downgrade is performed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%FEC_ISSU-3-MSG_NOT_OK : FEC ISSU client message [dec] is not compatible
Explanation FEC ISSU client received an incompatible message from the peer unit. Since the message is not compatible it can be processed by this unit
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>)
%FEC_ISSU-3-MSG_SIZE : FEC ISSU client failed to get the message size for message [dec]
Explanation FEC ISSU client failed to calculate message size for the message specified. The OIR ISSU client will not be able to send message to the standby unit.
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>)
%FEC_ISSU-3-POLICY : FEC ISSU client message type [dec] is [chars]
Explanation FEC ISSU client received an message type which it does not support. The policy is applied to make the session compatible.
Recommended Action LOG_STD_SH_CMD_ACTION(show issu session <client_id>)
%FEC_ISSU-3-SEND_FAILED : FEC ISSU client failed to send a negotiation message, error [dec]
Explanation FEC ISSU client could not send a session negotiation message to the peer. When there is a problem in the negotiation the standby unit can not be brought up.
Recommended Action LOG_STD_SH_CMD_ACTION(show logging and show checkpoint client)
%FEC_ISSU-3-SESSION : FEC ISSU client [chars]
Explanation FEC ISSU client observed an error during a session negotiation with the peer unit. When there is a problem with the session the standby unit can not be brought up.
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>)
%FEC_ISSU-3-SESSION_UNREGISTRY : FEC ISSU client failed to unregister session information. Error: [dec] ([chars])
Explanation The FEC 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>)
%FEC_ISSU-3-TRANSFORM : FEC ISSU client [chars] transform failed, error [chars]
Explanation FEC ISSU client could not transform the message. If the transmit transformation failed, it means that the checkpoint message can not be sent to the standby unit. If the receive transformation failed, it means that the checkpoint message can not be applied on the standby unit. In both cases the FEC state will not be indentical with the active unit.
Recommended Action LOG_STD_SH_CMD_ACTION(show issu session <client_id> and show issu negotiated version <session_id>)
FIB
%FIB-2-DFIBSWITCH : Error trying to turn on Distributed CEF without CEF on
Explanation IPV4FIB_INTERNAL_ERROR
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FIB-2-FIBDISABLE : Fatal error, slot [chars]: [chars]
Explanation An internal software error has occurred because of an IPC problem between the LC and the RP. CEF switching has been disabled on the specified slot.
Recommended Action Enter the <bold>clear cef linecard [slot no]<nobold> command, then check the status of the line card by entering the <bold>show cef linecard<nobold> command. If the status shows that the line card is still disabled, disable and re-enable DCEF and check the status of the line card again. LOG_STD_RECUR_ACTION
%FIB-2-FIBDOWN : CEF has been disabled due to a low memory condition. It can be re-enabled by configuring ip cef [distributed]
Explanation CEF was disabled because of a low memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade the RP so that it has more DRAM.
%FIB-2-FIBFEATSESINIT : Error initializing CEF repop feature session queue
Explanation Initialization of a CEF feature session queue could not be accomplished because of a low memory condition.
Recommended Action Reduce other system activitiy to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
%FIB-2-FIB_OVERLENGTH_XDR : Overlength CEF XDR message -len [dec] > [dec] from [chars]
Explanation An internal software error occurred preventing the sending of an CEF XDR message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FIB-2-IDBQINIT : Error initializing CEF IDB queue
Explanation Initialization of the CEF IDB queue could not be accomplished because of a low memory condition.
Recommended Action Reduce other system activitiy to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
%FIB-2-LINECARDINIT : Error initializing CEF Linecard queue
Explanation Initialization of the CEF linecard queue could not be accomplished because of a low memory condition.
Recommended Action Reduce other system activitiy to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
%FIB-2-XDRINIT : Error initializing CEF xdr chunks
Explanation Initialization of the CEF xdr chunks could not be accomplished because of a low memory condition.
Recommended Action Reduce other system activitiy to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
%FIB-3-FIBBADXDRSLOT : Invalid XDR slot. Type/len/slot [dec]/[dec]/[chars]. XDR at [hex]
Explanation IPV4FIB_INTERNAL_ERROR
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FIB-3-FIBPENDINGLIST : Error queueing interface [chars] to CEF pending event list.
Explanation Queueing an interface to the CEF pending up event list failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FIB-3-FIBSBINIT : Error initializing [chars] subblock data structure. [chars]
Explanation Initialization of the specified CEF 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FIB-3-FIBSBNOFN : Missing [chars] subblock [chars] function for [chars]
Explanation Functions for distributing this subblock are missing from the image.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FIB-3-FIBXDRLEN : Invalid XDR length. Type [dec][chars]. XDR/buffer len [dec]/[dec]
Explanation IPV4FIB_INTERNAL_ERROR
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FIB-3-INVALIDSTATE : Slot [chars] in invalid transition from [chars] to [chars]
Explanation An internal software error ocurred. Linecard is in incorrect state
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FIB-3-MAC_ACCT : [chars]: [chars]
Explanation IPV4FIB_INTERNAL_ERROR
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FIB-3-PREC_ACCT : [chars]: [chars]
Explanation IPV4FIB_INTERNAL_ERROR
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FIB-4-FIBCBLK : Missing cef table for tableid [dec] during [chars] event
Explanation IPV4FIB_INTERNAL_ERROR
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FIB-4-FIBEVENT : Invalid event. Type [chars], event [dec]
Explanation IPV4FIB_INTERNAL_ERROR
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FIB-4-FIBLCTUNSEQ : [chars] Error Initializing/Updating Linecard Tunnel Configuration
Explanation Configuration of a Tunnel on this linecard may not have been successful because of an internal software error.
Recommended Action Reconfigure the Tunnel concerned. If problem persists copy the message exactly as it appears, and report it to your technical support representative.
%FIB-4-FIBSPECIALPREFIX : Invalid Special Prefix Type. Type [dec]
Explanation IPV4FIB_INTERNAL_ERROR
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FIB-4-FIBXDRINV : Invalid format. [chars] [chars] ([dec])
Explanation IPV4FIB_INTERNAL_ERROR
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FIB-6-FIBLCTUNDELSEQ : Update received on a linecard for a deleted tunnel([chars]) -ignored.
Explanation An update was received on a linecard for a tunnel that has already been deleted and the update was ignored.
Recommended Action No action is required.
FILESYS
%FILESYS-3-FLASH : [chars] [chars] error [dec]
Explanation A file system error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%FILESYS-3-IPC : [chars] [chars]: IPC error [[chars]]
Explanation RFS operation failed due to an IPC error.
Recommended Action None
%FILESYS-4-CLPDINT : Management interrupts are [chars] for pcmcia device in socket [dec]. [chars]
Explanation A faulty PCMCIA flash device might be generating spurious insert or remove interrupts continiously. The pcmcia controller will be set temporarily to disable interrupt generation and will be reenabled after a few seconds. This is to avoid storming CPU with spurious interrupts. If the (alternate) pcmcia device is inserted while the interrupts are disabled, sometimes the device may not be readable. You have to remove and reinsert the pcmcia device once again.
Recommended Action Replace the pcmcia flash device with an alternate one
%FILESYS-4-RCSF : [chars] ([dec]) <[chars]>
Explanation A Running config sync file error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%FILESYS-5-CFLASH : Compact flash card [chars] [chars]
Explanation A file system's status has changed. Follow any instructions provided with the message.
Recommended Action None
%FILESYS-5-DEV : PCMCIA flash card [chars] [chars]
Explanation A file system's status has changed. Follow any instructions provided with the message.
Recommended Action No action is required.
%FILESYS-5-IFLASH : Internal Flash [chars] [chars]
Explanation A file system's status has changed. Follow any instructions provided with the message.
Recommended Action No action is required.
%FILESYS-5-MISMATCH : [chars] device programming algorithm mismatch detected, reformat is recommended
Explanation The flash device programming algorithm written to the device when the flash was formatted is different from what the current running software detected. A reformat of the flash device will solve the problem.
Recommended Action No action is required.
%FILESYS-5-UNKNDEV : Unknown device [chars] [chars]
Explanation A file system's status has changed. Follow any instructions provided with the message.
Recommended Action No action is required.
FILESYS_RFS
%FILESYS_RFS-3-IPC : [chars] [chars]: msg_type [[dec]] sub_type [[dec]]: IPC error [[chars]]
Explanation RFS operation failed due to an IPC error.
Recommended Action None
%FILESYS_RFS-4-RFS_REQUEST_TIMEOUT : Timeout has occurred while executing the RFS request on file [chars] [[dec]].
Explanation A RFS request is sent to server from the client. While executing the request on the server side, timeout has occurred at the client side.
Recommended Action No action is required.
FILTER_BINARY_NOTIFICATION
%FILTER_BINARY_NOTIFICATION-5-MERGE_COMPLETED : Merged logs generation completed.
Explanation Notification to user that merged logs are generated
Recommended Action Go to bootflash and view the merged logs
FLASH_CHECK
%FLASH_CHECK-3-DISK_QUOTA : Flash disk quota exceeded [free space is [dec] kB] -Please clean up files on bootflash.
Explanation The remaining free space on the flash disk is below the recommended threshold of at least half the installed RP memory. This limits the system from core files necessary to root cause critical system faults.
Recommended Action Please remove unneeded files from bootflash: device. Any core files under the bootflash:/core directory should be reported and then deleted.
FLEXDSPRM
%FLEXDSPRM-3-TDM_CONNECT : failed to connect voice-port ([dec]/[dec]/[dec]) to dsp_channel([dec]/[dec]/[dec])
Explanation TDM connection between Analog/VWIC and the DSP has failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FLEXDSPRM-3-UNSUPPORTED_CODEC : codec [chars] is not supported on dsp [dec]/[dec]
Explanation Call failed due to the dsp does not support the codec.
Recommended Action Check dsp capability and make the call on supported dsp
%FLEXDSPRM-5-CB_UPDOWN : Channel Bank [chars] state is [chars]
Explanation Channel Bank status has been changed
Recommended Action See if the voice ports in the channel bank are UP
%FLEXDSPRM-5-OUT_OF_RESOURCES : [chars]
Explanation Flex DSPRM temporarily fail to allocate a DSP for this call. A oversubscription has happened and the current free DSP MIPS/Credits are not sufficient to admit a new call.
Recommended Action Check availability of router DSP resource and DSP sharing configurations
%FLEXDSPRM-5-TDM_SLOT : voice channel is being shared from slot [dec]. Configure network-clock-participate slot [dec]
Explanation Configure network-clock-participate slot for sharing DSPs
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FLEXDSPRM-6-DSP_USAGE : DSP [chars] usage has reached [dec]
Explanation Usage of DSP resources has reached a certain percentage.
Recommended Action Examine whether or not enough DSP resources are reserved.
FMANRP_ACL
%FMANRP_ACL-3-EXPOGACLLIMITERR : Expanded OGACL ([chars]) size ([dec]) exceeded MAX ACL limit ([dec])
Explanation Expanded OGACL size exceeded the maximum ACL limit. Command rejected
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> Reduce # of ACEs in the ACL command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_ACL-4-INVALIDV4ACETYPE : v4 ACE type is invalid
Explanation An unexpected condition has occurred which is due to the type of v4 ACE created
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show ip access-list command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_ACL-4-INVALIDV6OP : Operation is invalid
Explanation An unexpected condition has occurred which is due to the operation performed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show ipv6 access-list command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_ACL-4-NOACL : ACL is null
Explanation An unexpected condition has occurred which is due to the absence of an ACL structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show ip access-list command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_ACL-4-NOMACACE : mac ACE is null
Explanation An unexpected condition has occurred which is due to the absence of an mac ACE structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show access-list command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_ACL-4-NOSB : Subblock on interface [chars] ([hex]) is null
Explanation An unexpected condition has occurred which is due to the absence of a subblock structure on interface.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show ip interface command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_ACL-4-NOSWIDB : Sub-interface is null
Explanation An unexpected condition has occurred which is due to the absence of a swidb structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show ip interface command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_ACL-4-NOV4ACE : v4 ACE is null
Explanation An unexpected condition has occurred which is due to the absence of an v4 ACE structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show ip access-list command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_ACL-4-NOV6ACE : v6 ACE is null
Explanation An unexpected condition has occurred which is due to the absence of an v6 ACE structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show ipv6 access-list command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_ACL-4-TMPLACLDISABLEERR : Not enough resources to disable template ACL
Explanation Not enough resurces to store individual ACLs
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show ip access-list template summary command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_ACL-4-TMPLACLINITERR : Template ACL initialization error
Explanation An unexpected condition has occurred on template ACL initialization
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show memory command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_ACL-4-TMPLACLNOMEMERR : Template ACL no memory error
Explanation An unexpected condition has occurred on template ACL processing
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show memory command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_ACL-4-UPDMACSTATSERR : Update mac ACL statistics error
Explanation An unexpected condition has occurred when updating mac ACL statistics
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show access-list command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_ACL-4-UPDV4STATSERR : Update v4 ACL statistics error
Explanation An unexpected condition has occurred when updating v4 ACL statistics
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show ip access-list command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_ACL-4-UPDV6STATSERR : Update v6 ACL statistics error
Explanation An unexpected condition has occurred when updating v6 ACL statistics
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show ipv6 access-list command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
FMANFP
%FMANFP-3-CRYPTO_DEVICE_REQUEST_FAILED : Crypto-device is busy processing last request. This request will be discarded
Explanation Crypto-device is still processing previous reload reqeust or still processing crypto feature packets. New request will not be applied
Recommended Action No action is required.
%FMANFP-3-CRYPTO_LICENSE_THPUT_MAX_APPROACHED : Average crypto throughput rate approached the licensed crypto bandwidth of [int] bps during [dec] sampling periods in the last 24 hours, sampling period is [dec] seconds
Explanation To monitor crypto throughput and, to generate notification/warning if the average throuput utilization over a longer time are approaching or exceeding the cypro licensed bandwidth
Recommended Action No action is required.
%FMANFP-3-CRYPTO_LICENSE_THPUT_THRESHOLD_EXCEED : Average crypto throughput rate exceeded [dec] percent of licensed crypto bandwidth of [int] bps during [dec] sampling periods in the last 24 hours, sampling period is [dec] seconds
Explanation To monitor crypto throughput and, to generate notification/warning if the average throuput utilization over a longer time are approaching or exceeding the cypro licensed bandwidth
Recommended Action No action is required.
%FMANFP-3-LICENSE_THPUT_INVALID : Invalid throughput [int]kbps
Explanation The throughput value is invalid. The forwarding engine will not operate at the throughput value.
Recommended Action Report this occurrence to Engineering. Use Topic to search for a similar DDTS. If you find none, write a DDTS for this problem.
%FMANFP-6-CRYPTO_DEVICE_NOT_PRESENT : Hardware crypto-device is not present. Request aborted
Explanation Hardware crypto-device is not present on the system. User request doesn't apply or be executed. This may not be an error.
Recommended Action No action is required.
%FMANFP-6-CRYPTO_DEVICE_REQUEST_COMPLETE : Crypto-device is ready to process packets
Explanation Crypto-device is load with new core based on user request. Now it is ready to process packets
Recommended Action No action is required.
%FMANFP-6-FMANACLLOGMISSMSG : access-list logging datapath rate-limited or missed [int] packet[chars]
Explanation Some packet matching logs were missed because the access list log messages were rate-limited or no access list log buffers were available.
Recommended Action No action is required.
%FMANFP-6-IPACCESSLOGDP : list [chars] [chars] [chars] [chars] [chars]-> [chars] ([int]/[int]), [int] packet[chars]
Explanation A packet matching the log criteria for the given access list was detected.
Recommended Action No action is required.
%FMANFP-6-IPACCESSLOGNP : list [chars] [chars] [int] [chars] [chars]-> [chars], [int] packet[chars]
Explanation A packet matching the log criteria for the given access list was detected.
Recommended Action No action is required.
%FMANFP-6-IPACCESSLOGP : list [chars] [chars] [chars] [chars]([int]) [chars]-> [chars]([int]), [int] packet[chars]
Explanation A packet matching the log criteria for the given access list was detected.
Recommended Action No action is required.
%FMANFP-6-IPACCESSLOGSGDP : ingress_interface='[chars]' sgacl_name='[chars]' action='[chars]' protocol='[chars]' src-ip='[chars]' dest-ip='[chars]' type='[int]' code='[int]' sgt='[int]' dgt='[int]' logging_interval_hits='[int]'
Explanation A packet matching the log criteria for the given access list was detected.
Recommended Action No action is required.
%FMANFP-6-IPACCESSLOGSGNP : ingress_interface='[chars]' sgacl_name='[chars]' action='[chars]' protocol='[int]' src-ip='[chars]' dest-ip='[chars]' sgt='[int]' dgt='[int]' logging_interval_hits='[int]'
Explanation A packet matching the log criteria for the given access list was detected.
Recommended Action No action is required.
%FMANFP-6-IPACCESSLOGSGP : ingress_interface='[chars]' sgacl_name='[chars]' action='[chars]' protocol='[chars]' src-ip='[chars]' src-port='[int]' dest-ip='[chars]' dest-port='[int]' sgt='[int]' dgt='[int]' logging_interval_hits='[int]'
Explanation A packet matching the log criteria for the given access list was detected.
Recommended Action No action is required.
%FMANFP-6-IPV6ACCESSLOGDP : list [chars] [chars] [chars] [chars] [chars]-> [chars] ([int]/[int]), [int] packet[chars]
Explanation A packet matching the log criteria for the given access list was detected.
Recommended Action No action is required.
%FMANFP-6-IPV6ACCESSLOGNP : list [chars] [chars] [int] [chars] [chars]-> [chars], [int] packet[chars]
Explanation A packet matching the log criteria for the given access list was detected.
Recommended Action No action is required.
%FMANFP-6-IPV6ACCESSLOGP : list [chars] [chars] [chars] [chars]([int]) [chars]-> [chars]([int]), [int] packet[chars]
Explanation A packet matching the log criteria for the given access list was detected.
Recommended Action No action is required.
FMANRP
%FMANRP-4-INVALID_CCE_POSITION : Invalid position '[dec]' prevented [chars]
Explanation A messaging error has occurred during service-policy modification and the configuration could not be downloaded properly
Recommended Action Report this occurrence to Engineering. Use Topic to search for a similar DDTS. If you find none, write a DDTS for this problem.
FMANRP_DPSS
%FMANRP_DPSS-3-DPSSFOIOSDENQUEUE : Failed to enqueue dpss feature object [hex] config message for transmission
Explanation This operation to enqueue an IPC message for sending has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_DPSS-3-DPSSFOIPCALLOC : Failed to alloc IPC buffer for dpss feature object [hex] config message
Explanation This operation to allocate IPC buffer for dpss feature object configuration has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_DPSS-3-DPSSFOTDLCREATE : Failed to create tdl msg for dpss feature object [hex] config message
Explanation This operation to create an TDL message has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_DPSS-3-DPSSFOTDLMSGMARSHAL : Failed to copy dpss feature object config message to IPC buffer for fo_hdl [hex]
Explanation This operation to build a TDL message for dpss feature object configuration has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_DPSS-3-DPSSFOTDLSET : Failed to set tdl msg detail for dpss feature object [hex] config message
Explanation This operation to set an TDL message has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_DPSS-3-DPSSGLOBALIOSDENQUEUE : Failed to enqueue dpss global config message for transmission
Explanation This operation to enqueue an IPC message for sending has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_DPSS-3-DPSSGLOBALIPCALLOC : Failed to alloc IPC buffer for dpss global config message
Explanation This operation to allocate IPC buffer for dpss global configuration has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_DPSS-3-DPSSGLOBALTDLCREATE : Failed to create tdl msg for dpss global config message
Explanation This operation to create an TDL message has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_DPSS-3-DPSSGLOBALTDLMSGMARSHAL : Failed to copy dpss global config message to IPC buffer
Explanation This operation to build a TDL message for dpss global configuration has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_DPSS-3-DPSSGLOBALTDLSET : Failed to set tdl msg detail for dpss global config message
Explanation This operation to set an TDL message has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
FMANRP_IPSEC
%FMANRP_IPSEC-3-HAPI_PCP_UNEXP_REPLY : [chars]: PCP (trans [hex], opcode [hex]): unexpected reply from crypto hardware.
Explanation An unexpected internal software error. Engineering must be reported and investigate this occurrence.
Recommended Action Report this occurrence to Engineering. Use Topic to search for a similar DDTS. If you find none, write a DDTS for this problem.
%FMANRP_IPSEC-6-HAPI_PCP_NACK : [chars]: PCP NACK (trans [hex], opcode [hex], errcode [hex]): crypto hardware configuration may be out of sync.
Explanation A failure has occured during security policy downloading in crypto hardware. The command is rejected.
Recommended Action The configuration may be ignorable or recovered automatically in crypto hardware. The session may still be functional but less than optimal performance. If you determine that the system is adversely affected then Embedded Services Processor (ESP) tracelog should be collected. LOG_STD_ACTION
FMANRP_MFR
%FMANRP_MFR-3-BLCFGFAIL : Unable to [chars] link [chars] [chars]
Explanation An unexpected condition has occurred at Bundle link configuration %s
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_MFR-3-BLFAIL : Unable to [chars] link [chars] [chars]
Explanation An unexpected condition has occurred at Bundle link configuration %s
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_MFR-3-BNDLFAIL : Unable to [chars] bundle [chars]
Explanation An unexpected condition has occurred at Bundle configuration
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_MFR-3-TDLFAIL : Unable to send [chars] [chars] message to Forwarding Manager Process ([chars])
Explanation An unexpected condition has occurred which resulted in a configuration not being sent to the Forwarding Manager Processs.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
FMANRP_MPLS
%FMANRP_MPLS-3-ENQUEFAIL : Unable to send [chars] [chars] message to Forwarding Manager Process
Explanation An unexpected condition has occurred which resulted in a configuration not being sent to the Forwarding Manager Processs.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_MPLS-3-NOOBJ : Object entry is null
Explanation An unexpected condition has occurred which is due to the absence of an object entry structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show mpls command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_MPLS-3-UNSPTYPE : Not supported bundle type [dec]
Explanation An unexpected condition has occurred which is due to an operation request to an unsupported bundle oce type is received.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
FMANRP_NAT
%FMANRP_NAT-3-AVLDELETE : Failed to delete node from NAT [chars] database for [IP_address]
Explanation This operation to perform delete processing has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_NAT-3-AVLTREEWALK : Failed to walk NAT [chars] database for [chars]
Explanation This operation to perform stale processing has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_NAT-3-DEBUGTDLMSGMARSHAL : Failed to copy debug NAT request message to IPC buffer
Explanation This operation to build a TDL message for debug NAT command has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_NAT-3-INVALID_ADDRESS : Received an invalid address [IP_address]
Explanation An unsupported address for the given config was received.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_NAT-3-IOSDENQUEUE : Failed to enqueue NAT [chars] message for transmission
Explanation This operation to enqueue an IPC message for sending has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_NAT-3-IPALIASTDL : Error with ipalias message received from data path
Explanation An unexpected condition has occurred with received ipalias message from data path
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_NAT-3-IPALIASTYPE : Received ipalias message from data path with unsupported address type [dec]
Explanation An unexpected condition has occurred with received ipalias message from data path with unsupported address type
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_NAT-3-IPSTATICROUTETDL : Error with static ip route message received from data path
Explanation An unexpected condition has occurred with received static ip route message from data path
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_NAT-3-IPSTATICROUTETYPE : Received ip static route message from data path with unsupported address type
Explanation An unexpected condition has occurred with received static ip route message from data path with unsupported address type
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_NAT-3-MIBEVENT : Failed to get NAT MIB response message: [chars]
Explanation An unsupported error occured with waiting for NAT MIB respsonse message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_NAT-3-MSGALLOCERR : Failed to allocate message
Explanation When attempting to send message to dataplane, there was not enough memory to allocate the message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_NAT-3-NATSETTDLMSGFAIL : When download [chars], failed to set a field in message
Explanation sotware error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_NAT-3-PORTLISTPROTO : Protocol type [dec] for global addr [IP_address] in the portlist allocation request is not supported
Explanation An unexpected protocol type has occurred with received portlist allocation request message from data path
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_NAT-3-PORTLISTTDL : Error with portlist allocation request message received from data path
Explanation An unexpected condition has occurred with received portlist allocation request message from data path
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_NAT-3-PORTLISTTYPE : Address type [dec] for global address in the portlist allocation request is not supported
Explanation An unexpected address type has occurred with received portlist allocation request message from data path
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_NAT-3-WLANSESSIDB : Received WLAN session message from data path with nil input interface for inside local host [IP_address]
Explanation An unexpected condition has occurred with received WLAN session message from data path with nil input interface
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_NAT-3-WLANSESSTDL : Error with WLAN session message received from data path
Explanation An unexpected condition has occurred with received WLAN session message from data path
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_NAT-3-WLANSESSTYPE : Received WLAN session message from data path with unsupported address type [dec]
Explanation An unexpected condition has occurred with received WLAN session message from data path with unsupported address type
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_NAT-4-LOGGING_PARAM : Highspeed logging export [chars] [int]nsupported
Explanation An unsupported exporting paremeter for highspeed logging on data path is received.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show running command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_NAT-4-NOLOGGINGPARAM : Highspeed logging structure is nil
Explanation An unexpected condition has occurred which is due to the absence of a logging parameter structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show running command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_NAT-4-NOREPLICATEPARAM : Session replication structure is nil
Explanation An unexpected condition has occurred which is due to the absence of a session replication parameter structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show running command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_NAT-3-IFADDRTDLMSGMARSHAL : Failed to copy interface address change message to IPC buffer for interface [chars], new address [IP_address]
Explanation This operation to build a TDL message for NAT interface address configuration has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_NAT-3-IFTDLMSGMARSHAL : Failed to copy interface config essage to IPC buffer for Interface [chars] ([hex]), domain [chars], operation [chars]
Explanation This operation to build a TDL message for interface configuration has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_NAT-3-MAPPINGTDLMSGMARSHAL : Failed to copy mapping config message to IPC buffer for mapping id [dec] (vrf table id [dec])
Explanation This operation to build a TDL message for mapping configuration has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_NAT-3-MAXENTRYTDLMSGMARSHAL : Failed to copy max entry config message to IPC buffer for type [chars], entry data [hex], max_limit [dec]
Explanation This operation to build a TDL message for max entry add/delete has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_NAT-3-POOLTDLMSGMARSHAL : Failed to copy pool config message to IPC buffer for pool [chars] (id [dec])
Explanation This operation to build a TDL message for pool configuration has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_NAT-3-PORTLISTTDLMSGMARSHAL : Failed to copy portlist config message to IPC buffer for addr [IP_address], proto [dec], start_port [dec], end_port [dec]
Explanation This operation to build a TDL message for portlist add/delete has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_NAT-3-RANGETDLMSGMARSHAL : Failed to copy pool address range config message to IPC buffer for pool [chars], range start [IP_address], range end [IP_address]
Explanation This operation to build a TDL message for address range configuration has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_NAT-3-SERTDLMSGMARSHAL : Failed to copy service config message to IPC buffer for application type [dec], protocol type [dec], port [dec]
Explanation This operation to build a TDL message for service configuration has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_NAT-3-SERVICERM : Failed to delete NAT services for appl type [chars], protocol [chars], port [dec]
Explanation An unexpected condition has occurred which is due to the failure to remove data structures for NAT special services.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_NAT-3-STATSUPDTDL : Failed to update NAT [chars] statistics
Explanation An unexpected condition has occurred when updating statistics
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_NAT-3-TIMEOUTTDLMSGMARSHAL : Failed to copy timeout config message to IPC buffer for timeout type [dec]
Explanation This operation to build a TDL message for timeout configuration has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_NAT-3-VRFDELTDLMSGMARSHAL : Failed to copy VRF delete message to IPC buffer for vrf table id [dec]
Explanation This operation to build a TDL message for vrf deletion configuration has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_NAT-4-BADACTION : Invalid action [dec] for NAT configuration
Explanation An unexpected condition has occurred which is invalid action for a NAT configuration.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_NAT-4-NOACL : Access list is null
Explanation An unexpected condition has occurred which is due to the absence of an access list structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show ip access-lists command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_NAT-4-NOMAPPING : A mapping structure is null
Explanation An unexpected condition has occurred which is due to the absence of a NAT mapping structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_NAT-4-NONATSERVICE : Service structure is null
Explanation An unexpected condition has occurred which is due to the absence of a NAT service structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_NAT-4-NOPOOL : Pool structure is null
Explanation An unexpected condition has occurred which is due to the absence of a NAT pool structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_NAT-4-NORANGE : Pool address range structure is null
Explanation An unexpected condition has occurred which is due to the absence of a NAT pool address range structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_NAT-4-NOSWIDB : Sub-interface is null
Explanation An unexpected condition has occurred which is due to the absence of a swidb structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show ip interface command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
FMANRP_NETFLOW
%FMANRP_NETFLOW-3-AGGRCACHENULL : The pointer for aggregation cache type [dec] is NULL
Explanation An unexpected condition has occurred which is due to the absence of an aggregation cache data structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show ip cache flow command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_NETFLOW-3-CACHETDLMSGMARSHAL : Failed to copy cache config message to IPC buffer for cache type [dec]
Explanation The operation of building a TDL message for cache configuration has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_NETFLOW-3-CLRSTATSTDLMSGMARSHAL : Failed to copy clear statistics message to IPC buffer
Explanation The operation of building a TDL message for clearing statistics in the data path has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_NETFLOW-3-EXPORTERSRCIFINVALID : Management interface ([chars]) cannot be used as source for an exporter
Explanation Exporter configuration failed because the management interface cannot be configured as source interface
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_NETFLOW-3-EXPORTERTDLMSGMARSHAL : Failed to copy exporter config message to IPC buffer for cache type [dec]
Explanation The operation of building a TDL message for exporter configuration has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_NETFLOW-3-IFFLOWTDLMSGMARSHAL : Failed to copy interface flow config message to IPC buffer for [chars]
Explanation The operation of building a TDL message for interface flow configuration has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_NETFLOW-3-INVALIDFLOWDEFCPP : CPP Flow definition can not be created [int]
Explanation The operation of building a flow definition using flow fields received from CPP has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_NETFLOW-3-NOSAMPLER : Sampler for sampler-map name [chars] is null
Explanation An unexpected condition has occurred which is due to the absence of a sampler-map structure
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show sampler command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_NETFLOW-3-NOSAMPLERNAME : Sampler-map name is null
Explanation An unexpected condition has occurred which is due to the absence of a sampler-map name.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show sampler command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_NETFLOW-3-SAMPLERTDLMSGMARSHAL : Failed to copy sampler-map config message to IPC buffer for [chars]
Explanation The operation of building a TDL message for sampler-map configuration has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_NETFLOW-3-STATSUPDTDL : Failed to update netflow [chars] statistics
Explanation An unexpected condition has occurred when updating statistics
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_NETFLOW-3-UNKNOWNCACHECMD : Unknown aggregation cache command [dec] received
Explanation The aggregation cache configuration command has failed due to unknown command.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_NETFLOW-3-UNKNOWNCACHETYPE : Unknown cache type [dec] received
Explanation The cache configuration command has failed due to unknown cache scheme type.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_NETFLOW-4-EXPORTERVERSION : Failed to change default exporter version to [dec]
Explanation The operation of changing the default exporter version has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show ip flow export command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_NETFLOW-4-NOFIBIDB : fibdb for interface [chars] is null
Explanation An unexpected condition has occurred which is due to the absence of a fibidb structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show ip interface command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_NETFLOW-4-NOSWIDB : Sub-interface is null
Explanation An unexpected condition has occurred which is due to the absence of a swidb structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show ip interface command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
FMANRP_PBR
%FMANRP_PBR-3-INVALIDIF : The interface specified for '[chars]' is not valid
Explanation An non-existent interface is specified for the policy based routing route-map operation specified in the message.
Recommended Action show interface
%FMANRP_PBR-3-RTMAP_NAME_NULL : The route-map name for [chars] is NULL
Explanation An unexpected condition has occurred due to the absence of an internal route-map data structure.
Recommended Action show route-map
%FMANRP_PBR-3-RTMAPNULL : The route-map structure for [chars] is NULL
Explanation An unexpected condition has occurred due to the absence of an internal route-map data structure.
Recommended Action show route-map
%FMANRP_PBR-3-UNSUPPORTED_RMAP : Route-map [chars] has unsupported options for Policy-Based Routing. It has been removed from the interface, if applied.
Explanation The route-map attached to an interface for policy routing contains an action that is not supported on this platform. This is a hardware limitation.
Recommended Action Reconfigure the route-map. Use only 'permit' entries and 'set ip next-hop' action in the route-map.
FMANRP_PFR
%FMANRP_PFR-4-NOINTF : PfR Interface [chars] not exist, can't be [chars]
Explanation An unexpected condition has occurred which is due to the absence of MCP PfR interface info.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show oer border command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_PFR-4-NULLINPUT : NULL input, [chars]
Explanation An unexpected condition has occurred which is due to the NULL value of the input parameter.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show oer border command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_PFR-4-UNSUPPORTED : Unsupported action, [chars]
Explanation An unexpected condition has occurred which is due to and unsupported action being executed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show oer border command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
FMANRP_QOS
%FMANRP_QOS-3-ACTNOCLASSMAP : Class-map information not found
Explanation An unexpected condition has occured when trying to determine class-map information for one of the classes in a policy-map.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show policy-map command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_QOS-3-ACTNOPOLICYMAP : Policy-map information not found
Explanation An unexpected condition has occured when trying to determine policy-map information for one of the service policies attached to an interface.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show policy-map command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_QOS-3-CLPOLFAIL : No support for client policy with policing in class-default and marking in custom class
Explanation An internal error occured during installing qos policy.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_QOS-3-NOACCOUNTSTATS : account stats entry not found for class [int].[int], target [int]
Explanation An internal error occured when looking up account statistics.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show policy-map interface command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_QOS-3-NOPOLICERSTATS : policer stats entry not found for class [int].[int], target [int]
Explanation An internal error occured when looking up policer statistics.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show policy-map interface command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_QOS-3-NOSETSTATS : set stats entry not found for class [int].[int], target [int]
Explanation An internal error occured when looking up set statistics.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show policy-map interface command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_QOS-3-QOSAPIPARAM : Internal QOS API error.
Explanation An internal API error occured. QOS configuration may be limited.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_QOS-3-QOSCLASSDEL : Error trying to remove class [chars] from policymap [chars]
Explanation An operation to remove a class from a policy has failed due to an internal error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show policy-map command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_QOS-3-QOSGIDBSP : Service policy [[chars]] installation error: invalid interface type [dec]
Explanation An invalid interface type was encountered when trying to configure a service policy. This service policy could not be installed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show policy-map command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_QOS-3-QOSIDBSP : Service policy [[chars]] installation error: invalid interface type [dec]
Explanation An invalid interface type was encountered when trying to configure a service policy. This service policy could not be installed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show policy-map command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_QOS-3-QOSTDLMARSHAL : Failed to copy more than [dec] bytes of message [chars], length [dec] into IPC buffer
Explanation An internal error occured when trying to build an IPC message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_QOS-3-QOSTMPLCREATEFAIL : QoS template interface creation failed for policy [chars]: [chars]
Explanation An error occured during template interface creation
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_QOS-3-QOSTMPLDBERROR : Failed to [chars] record for policymap [chars], err [chars]
Explanation Database operation failed for record of the policymap
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_QOS-3-QOSTMPLDELETEFAIL : QoS template interface deletion failed for policy [chars]: [chars]
Explanation An error occured during template interface deletion
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_QOS-3-QOSTMPLNONEXIST : QoS template does not exist in [chars] for policymap [chars]
Explanation QoS template information does not exist
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_QOS-4-CLMODIFYFAIL : classmap [chars] is currently used by policymap, please remove policymap from all targets before the modification
Explanation An internal error occured when classmap being modified
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_QOS-4-MPOLDMVPNGRE : Only Shape and/or BRR is allowed on the QoS policy on GRE tunnel on MPoL hierarchy
Explanation An error occurred during MPoL check between DMVPN and GRE tunnel QoS policy
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_QOS-4-NOFAIRQONVC : fair-queue can not be configured on the parent queue of an ATM VC, use child queue instead
Explanation Configuring fair-queue on the parent queue of an ATM VC is not supported
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_QOS-4-QIDGENFAIL : qid generation failed, reverting to default
Explanation An internal error occured during platform qos initialization.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_QOS-4-QOSSTACK : Failed to install all classes for policymap [chars], excessive stack usage
Explanation An operation to configure the classes within a policymap has failed due to a resource issue. QoS configuration for this policymap is unlikely to work.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show policy-map command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_QOS-4-QOSUBR : qos can not be attached to the target with UBR configured
Explanation An error occured to attach qos to ATM VC/VP target with UBR configured
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_QOS-6-QOSCLASSEXIST : class [chars] (id [int]) in policymap [chars] (id [int]) already exists
Explanation This is an informational message and no action is required.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show policy-map command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
FMANRP_SC
%FMANRP_SC-3-DBGTDLMSGMARSHAL : Failed to copy debug SC request message to IPC buffer
Explanation This operation to build a TDL message for debug SC command has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_SC-3-INTFTDLMSGMARSHAL : Failed to copy interface config message to IPC buffer for Interface [chars] ([hex]), operation [chars]
Explanation This operation to build a TDL message for interface configuration has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_SC-3-SCIOSDENQUEUE : Failed to enqueue SC [chars] message for transmission
Explanation This operation to enqueue an IPC message for sending has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_SC-3-SCTXTDLMSGMARSHAL : Failed to copy service context config message to IPC buffer for sctx_name id [dec]
Explanation This operation to build a TDL message for service context configuration has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_SC-4-NOSERVICECTX : A mapping structure is null
Explanation An unexpected condition has occurred which is due to the absence of a SC mapping structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_SC-4-SCBADACTION : Invalid action [dec] for SC configuration
Explanation An unexpected condition has occurred which is invalid action for a SC configuration.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_SC-4-SCNOSWIDB : Sub-interface is null
Explanation An unexpected condition has occurred which is due to the absence of a swidb structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show ip interface command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
FMANRP_SSLVPN
%FMANRP_SSLVPN-3-AAATDLERR : [chars][chars]. [chars]
Explanation An unexpected condition has occurred in processing AAA request/reply message causing AAA handling failure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_SSLVPN-3-CFGSTATUSERR : [chars]: [chars]
Explanation An unexpected condition has occurred when got status of configuration
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_SSLVPN-3-CONDDEBERR : [chars]. [chars]
Explanation An unexpected condition has occurred in processing conditional debug message
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_SSLVPN-3-GWERR : Failed [chars]: [chars]
Explanation An unexpected condition has occurred in configuration processing causing configuration failure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_SSLVPN-3-PKIERR : Failed [chars]: [chars]
Explanation An unexpected condition has occurred in configuration processing causing configuration failure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_SSLVPN-3-RRICHUNKERR : [chars]
Explanation Error has occurred when requested memory for SSLVPN route handling
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_SSLVPN-3-RRITDLERR : [chars][chars]. [chars]
Explanation An unexpected condition has occurred in processing of SSLVPN route inject/remove message
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_SSLVPN-3-STATSCLEARERR : Unable to send clear WEB VPN context stats message. [chars] ([dec])
Explanation This operation to build a TDL messages for WEB VPN context stats clearing has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_SSLVPN-3-STATSGUPDERR : Update WEB VPN context stats error. [chars] ([dec])
Explanation An unexpected condition has occurred when updating global sslvpn statistics
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_SSLVPN-3-STATSWVUPDERR : [chars]: [chars]
Explanation An unexpected condition has occurred when updating ssl web vpn context statistics
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_SSLVPN-3-VWCONFERR : Failed [chars]: [chars]
Explanation An unexpected condition has occurred during WebVPN Context configuration causing failure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FMANRP_SSLVPN-4-AAAFRIPWARN : [chars]Invalid framed ip address [IP_address] received from AAA. Not sending user config
Explanation Wrong AAA server config.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
FMD
%FMD-2-IPC_INIT : IPC message handler registration failure, rc [int]
Explanation Registering an IPC message handler for the FMD feature failed. This will cause the feature to not function.
Recommended Action This is normally a software issue. The consequences are that the FMD feature will not function. LOG_STD_ACTION
%FMD-3-IPC_NORES : No space for the IPC reply, size [int]
Explanation For a request from upper FMD 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 binding 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
%FMD-3-IPC_OPEN_REPLY : IPC Open Reply failed, request [int]
Explanation For a request from upper FMD software stack layers it was not possible to open the reply buffer. The consequence of this could be a stuck binding 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
FME
%FME-2-IPC_INIT : IPC message handler registration failure, rc [int]
Explanation Registering an IPC message handler for the FME feature failed. This will cause the feature to not function.
Recommended Action This is normally a software issue. The consequences are that the FME feature will not function. LOG_STD_ACTION
%FME-3-IPC_NORES : No space for the IPC reply, size [int]
Explanation For a request from upper FME 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
%FME-3-IPC_OPEN_REPLY : IPC Open Reply failed, request [int]
Explanation For a request from upper FME 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
FME_DP
%FME_DP-3-DEBUG_REG_FAILED : Flow Metric Engine fails to registrate with Conditional Debugging.
Explanation Flow Metric Engine fails to registrate with Conditional Debugging infra.
Recommended Action LOG_STD_ACTION
FMFP
%FMFP-3-DP_NOMEM : DP not enough memory. [chars]
Explanation An object download to DP failed because the memory of DP is not enough.
Recommended Action Run show platform resource to see the memory usage
%FMFP-3-INTERFACE_OBJECT_NOT_FOUND : Interface object lookup by [chars] not found for interface [int]
Explanation The desired interface object was not found.
Recommended Action Examine the interface state in the operating system, route processor (RP) and forwarding processor (FP) forwarding manager logs.
%FMFP-3-OBJ_DWNLD_TO_CPP_STUCK : AOM download to CPP stuck
Explanation An object download from FMAN-FP to lower layer has taken more than 30 seconds. It can be caused by incomplete configuration or software defects
Recommended Action Run show platform software object-manager fp [active|standby] [pending-issue-update|pending-ack-update|pending-issue-batch| pending-ack-batch|pending-ack-commands] sorted <min_pending_time> to see the sorted list of update/batch/command in pending state for more than the min_pending_time. Use 3600 for min_pending_time to see context that have been pending for more than an hour. For incomplete configuration, use show platform platform software object fp [active|standby] resolve to see if there is any resolve object
%FMFP-3-OBJ_DWNLD_TO_DP_FAILED : [chars] download to DP failed
Explanation An object has failed to download to the data plane
Recommended Action Examine the list of error objects in the forwarding processor (FP) forwarding manager asynchronous object logs.
%FMFP-6-OBJ_DWNLD_TO_CPP_RESUME : AOM download to CPP resumed
Explanation An object download from FMAN-FP to lower layer has finished after a temporary stuck. It can be caused by incomplete configuration or software defects
Recommended Action check if there is any functional impact after recovery
FMFP_ACL
%FMFP_ACL-3-ACL_LIMIT_EXCEEDED : ACL [chars] exceeded limitation of [int] ACEs per ACL
Explanation A software limitation has been exceeded.
Recommended Action Reduce the access control list (ACL) configuration. A reboot of the forwarding processor (FP) is recommended.
%FMFP_ACL-3-ACL_MODIFY_FAILED : ACL:[chars] modification through object group edit failed
Explanation Object-group used in the ACL was modified. Those changes could not be accommodated in the ACL
Recommended Action Fix the object-group changes. Delete ACL and reconfigure it
%FMFP_ACL-3-ACL_OBJECT_DOWNLOAD : [chars][chars] fail to download because [chars].
Explanation The access control list (ACL) object has failed to download. This could be due to a hardware or software resource limitation or a software defect.
Recommended Action Check the logs for information on the relevant object download states. Remove the ACL attachment to the interface or delete the ACL. Reboot the forwarding processor (FP).
%FMFP_ACL-3-ACL_PROTOCOL_CHECK : ACL [chars] protocol does not match what was previously configured
Explanation The error occurs for one of two reasons. An access control list (ACL) reference was made to an ACL of a different protocol or an ACL was added or edited when there were similarly named ACL references of a different protocol
Recommended Action Remove the conflicting ACL or the conflicting ACL references.
%FMFP_ACL-3-SGACL_OBJECT_DOWNLOAD : SGACL Cell ([dec] [dec]) policy [chars] fail to download because [chars].
Explanation The SGACL policy has failed to download. This could be due to a hardware or software resource limitation or a software defect.
Recommended Action Check the logs for information on the relevant object download states. Remove the SGACL policy for that cell, correct the error and reconfigure it
FMFP_CXSC
%FMFP_CXSC-3-CXSC_DEINITIALIZATION : [chars] Returned: [chars]
Explanation The CXSC DEINITIALIZATION has FAILED. This could be due to a hardware or software resource limitation or a software defect.
Recommended Action Check memory usage and router configuration and try to re-activate virtual service again. If it shows the same results then please contact TAC.
%FMFP_CXSC-3-CXSC_DOMAIN_CONFIG : [chars] Returned: [chars]
Explanation The CXSC DOMAIN CONFIG DOWNLOAD has FAILED. This could be due to a hardware or software resource limitation or a software defect.
Recommended Action Check memory usage and router configuration and try to re-activate virtual service again. If it shows the same results then please contact TAC.
%FMFP_CXSC-3-CXSC_INITIALIZATION : [chars] Returned: [chars]
Explanation The CXSC INITIALIZATION has FAILED. This could be due to a hardware or software resource limitation or a software defect.
Recommended Action Check memory usage and router configuration and try to re-activate virtual service again. If it shows the same results then please contact TAC.
%FMFP_CXSC-3-CXSC_POLICY_DOWNLOAD : [chars] Returned: [chars]
Explanation The CXSC POLICY DOWNLOAD has FAILED. This could be due to a hardware or software resource limitation or a software defect.
Recommended Action Check memory usage and router configuration and try to re-activate virtual service again. If it shows same results then please contact TAC.
%FMFP_CXSC-6-CXSC_POLICY_DOWNLOAD_SUCCESS : New policy version: [int] has now been installed and is active
Explanation The CXSC POLICY DOWNLOAD of the numbered version has succeeded.
Recommended Action This an informational message only, no action is required. Note that policy version is not monotonically increasing so there is nothing to be concerned about if the current installed policy version is less than the previous installed policy version.
FMFP_QOS
%FMFP_QOS-6-QOS_STATS_PROGRESS : statistics are progressing
Explanation QoS statistics are now progressing normally. This is an informational message.
Recommended Action No action is required.
%FMFP_QOS-6-QOS_STATS_STALLED : statistics stalled
Explanation QoS statistics are temporarily stalled. This is an informational message.
Recommended Action No action is required.
FMFP_URPF
%FMFP_URPF-3-LIST_DOWNLOAD : Unicast RPF list [chars] for list [int] fail to download because [chars].
Explanation The unicast reverse path forwarding (URPF) list failed to download. This can be caused by a hardware or software resource limitation or software defect.
Recommended Action Check the logs for information on the relevant download states.Reboot the forwarding processor (FP).
%FMFP_URPF-3-OBJECT_DOWNLOAD : Unicast RPF [chars] on inteface [chars] fail to download because [chars].
Explanation The unicast reverse path forwarding (URPF) operation failed to download. This can be caused by a hardware or software resource limitation or a software defect.
Recommended Action Check the logs for information on the relevant download states.Remove the uRPF feature enabled on any interface. Reboot the forwarding processor (FP).
FNF
%FNF-3-CFT_REG_FAILED : FNF fails to connect to CFT infra.
Explanation FNF fails to connect to CFT infra.
Recommended Action LOG_STD_ACTION
%FNF-3-CLEANUP_ENTRY : Failed, MSGDEF_LIMIT_MEDIUM
Explanation Netflow failed to clean up a record for reuse.
Recommended Action LOG_STD_ACTION
%FNF-3-DEBUG_REG_FAILED : FNF fails to registrate with Conditional Debugging.
Explanation FNF fails to registrate with Conditional Debugging infra.
Recommended Action LOG_STD_ACTION
%FNF-3-FNF_CWALK_FLEXIBLE_UNEXPECTED_LAYOUT : Failed copy to CLI buffer , PI will receive zero buffer, MSGDEF_LIMIT_MEDIUM
Explanation Failed copy to CLI buffer during the walk process ,fill the buffer with 0
Recommended Action LOG_STD_ACTION
%FNF-3-FNF_EXPORT_BUILD_TYPE_FAILED : Format: [dec], MSGDEF_LIMIT_MEDIUM
Explanation FNF Exporter build failed. unknown type.
Recommended Action None
%FNF-3-FNF_FIELD_LIST_MEM_INSUFFICIENT : Insufficient memory [dec] for field_list, MSGDEF_LIMIT_MEDIUM
Explanation Internal error, netflow client provided insufficient memory to process a field list
Recommended Action LOG_STD_ACTION
%FNF-3-FNF_FIELD_LIST_TOO_LARGE : Field_list too large, max [dec], MSGDEF_LIMIT_MEDIUM
Explanation Netflow field list contains too many fields. At most 32 fields are supported, including any hidden fields automatically added as necessary for record keeping
Recommended Action LOG_STD_ACTION
%FNF-3-FNF_FIELD_LIST_TS_CNT_KEY : Field_id [dec] must be non-key, MSGDEF_LIMIT_MEDIUM
Explanation Netflow Field list specified timestamp/counter field as a key field, which is not supported
Recommended Action LOG_STD_ACTION
%FNF-3-FNF_FIELD_LIST_VAR_INVALID : Unknown field variety [dec] for field_id [dec], MSGDEF_LIMIT_MEDIUM
Explanation Internal error, Netflow field list entry mapped to unknown field variety
Recommended Action LOG_STD_ACTION
%FNF-3-FNF_FIELD_UNEXPECTED_SIZE : Unexpected size for field_id [dec], expected [dec]/got [dec], MSGDEF_LIMIT_MEDIUM
Explanation Netflow specified unexpected size for field_id
Recommended Action LOG_STD_ACTION
%FNF-3-FNF_FREC_LAYOUT_TOO_LARGE : Flow record layout too large, max [dec], MSGDEF_LIMIT_MEDIUM
Explanation Netflow field list results in a flow record layout which is too large. At most 128 bytes of flow record data is supported, including any padding, and any hidden fields automatically added as necessary for record keeping
Recommended Action LOG_STD_ACTION
%FNF-3-FNF_UNSUPPORTED_AGG_FMT : Format: [dec], MSGDEF_LIMIT_MEDIUM
Explanation Netflow doesn't support this aggregation type.
Recommended Action LOG_STD_ACTION
%FNF-3-FNF_UNSUPPORTED_EXP_FMT : Format: [dec], MSGDEF_LIMIT_MEDIUM
Explanation Netflow doesn't support this export format.
Recommended Action LOG_STD_ACTION
%FNF-3-FNF_UNSUPPORTED_MMA_FIELD : MMA global ID [dec] (Netflow field [dec]) is not supported by MMA, MSGDEF_LIMIT_SLOW
Explanation Netflow field that is marked as MMA (Metric Mediation Agent) controlled field is not supported by MMA
Recommended Action LOG_STD_ACTION
%FNF-3-FNF_UNSUPPORTED_OPTION : Option: [dec], MSGDEF_LIMIT_MEDIUM
Explanation Netflow doesn't support this export option.
Recommended Action LOG_STD_ACTION
%FNF-3-FREE_LIST_ADD : Failed for record: [hex], MSGDEF_LIMIT_MEDIUM
Explanation Netflow failed to return a record to the free list.
Recommended Action LOG_STD_ACTION
%FNF-3-INVALID_CMD : Flow builder encountered an invalid command: [dec]., MSGDEF_LIMIT_MEDIUM
Explanation Flow builder doesn't support the command encountered in the instruction stream.
Recommended Action LOG_STD_ACTION
%FNF-3-INVALID_FO : FNF FO is not valid, MSGDEF_LIMIT_MEDIUM
Explanation FNF feature object is not valid.
Recommended Action LOG_STD_ACTION
%FNF-3-IPFIX_UNSUPPORTED_MON_TYPE : Monitor type: [dec], MSGDEF_LIMIT_MEDIUM
Explanation IPFIX doesn't support this monitor type.
Recommended Action LOG_STD_ACTION
%FNF-3-KEY_SIZE_INVALID : Unexpected key fields size: [dec], MSGDEF_LIMIT_SLOW
Explanation Netflow attempted to install a flow with an invalid key fields size.
Recommended Action LOG_STD_ACTION
%FNF-3-LC_STATUS : Flow monitor [chars] can not be added to [chars], rejected on module [chars] : [chars]
Explanation The flow monitor has been rejected on the specified module. It will have been removed from the RP configuration too. This can happen for example when a monitor is removed and added again immediately before the tidy has been completed, or in the case where a flow monitor is waiting at automore when the monitor is removed from the interface then reapplied
Recommended Action Check the configuration of the Flow Monitor that was applied for errors. If the rejection was due to the LC not having finished cleaning up after a previous removal of a Flow Monitor, wait until the cleaning up has finished then reapply the config.
%FNF-3-PROVISIONING : [chars] failed to provision '[chars] flow monitor [chars] [chars]' on [chars]: [chars]
Explanation The attachment of the Flow Monitor to has had a problem on the device identified. It may be working on other devices, and the configuration is retained.
Recommended Action Check the device identified is working as expected and that it can support the configuration of the Flow Monitor to the chosen attachment point.
%FNF-3-REFCNT_TIMEOUT : never reached 0 for entry [hex], MSGDEF_LIMIT_SLOW
Explanation Netflow timed out waiting for an flow cache entries refcnt. to hit 0. The entry was forced out
Recommended Action LOG_STD_ACTION
%FNF-3-REFCNT_UNDERFLOW : refcnt underflow for entry [hex], MSGDEF_LIMIT_SLOW
Explanation Netflow error caused flow cache entry reference count to go negative. The decrement was rescinded
Recommended Action LOG_STD_ACTION
%FNF-3-UNSUPPORTED_PROT : [chars], MSGDEF_LIMIT_MEDIUM
Explanation This protocol is unsupported.
Recommended Action LOG_STD_ACTION
%FNF-4-FREE_LIST_EMPTY : Monitor: [hex], MSGDEF_LIMIT_MEDIUM
Explanation Netflow attempted to install a flow but no free flow records were available.
Recommended Action LOG_STD_ACTION
%FNF-6-AGER_OVERRIDE : Flow [chars] time modified by [chars] to [dec]
Explanation The aging timer has been modified and may be different from configured value.
Recommended Action No action is required.
%FNF-6-CONFIGURATION : Invalid FNF configuration: [chars]
Explanation An invalid FNF configuration was detected.
Recommended Action Review the FNF configuration before repeating the action.
%FNF-6-ERROR : FNF error: [chars]
Explanation An FNF error occurred.
Recommended Action For more information, repeat the action with FNF debugging enabled.
%FNF-6-DYNAMIC_MONITORS_OVER_SUBSCRIPTION : Interface [chars] (dir=[chars]): the number of monitors that should run on the packet([dec]) exceeds QFP limit([dec]), [dec] monitor[chars] won't run, MSGDEF_LIMIT_GLACIAL
Explanation QFP maximum supported number of monitors per packet was exceeded. As a result the excess number of monitors will not run on the packet. Static monitors always take priority over policy-map monitors.
Recommended Action LOG_STD_DBG_ACTION
%FNF-6-SYNC_CACHE_TOO_MANY_RECS_FOR_INTERVAL : For synchronized cache the number of records is larger than can be exported in configured interval., MSGDEF_LIMIT_MEDIUM
Explanation The number of records is too large for the configured interval. As a result some records may not be exported in a timely manner. Consider reducing cache size or increasing interval length.
Recommended Action LOG_STD_DBG_ACTION
FNF_PROXY
%FNF_PROXY-3-EVAL_FREC_FIELD_LIST : Failed with return code: [dec], MSGDEF_LIMIT_MEDIUM
Explanation Netflow failed to process an evaluate flow record field list request.
Recommended Action LOG_STD_ACTION
%FNF_PROXY-3-EXPORTER_FORCE_TEMPLATE_REFRESH : Failed with return code: [dec], MSGDEF_LIMIT_MEDIUM
Explanation Netflow failed to force a template refresh for an exporter.
Recommended Action LOG_STD_ACTION
%FNF_PROXY-3-EXPORTER_INIT : Failed with return code: [dec], MSGDEF_LIMIT_MEDIUM
Explanation Netflow failed to initialize the exporter.
Recommended Action LOG_STD_ACTION
%FNF_PROXY-3-EXPORTER_OPTION_TEMPLATE_BIND : Failed for exporter: [hex] with return code: [dec], MSGDEF_LIMIT_MEDIUM
Explanation Netflow failed to bind an option template.
Recommended Action LOG_STD_ACTION
%FNF_PROXY-3-EXPORTER_OPTION_TEMPLATE_UNBIND : Failed for exporter: [hex] with return code: [dec], MSGDEF_LIMIT_MEDIUM
Explanation Netflow failed to unbind an option template.
Recommended Action LOG_STD_ACTION
%FNF_PROXY-3-EXPORTER_OPTION_TIMER_START : Failed for exporter: [hex] with return code: [dec], MSGDEF_LIMIT_MEDIUM
Explanation Netflow failed to start an option timer.
Recommended Action LOG_STD_ACTION
%FNF_PROXY-3-EXPORTER_OPTION_TIMER_STOP : Failed for exporter: [hex] with return code: [dec], MSGDEF_LIMIT_MEDIUM
Explanation Netflow failed to stop an option timer.
Recommended Action LOG_STD_ACTION
%FNF_PROXY-3-EXPORTER_SHUT : Failed with return code: [dec], MSGDEF_LIMIT_MEDIUM
Explanation Netflow failed to shutdown the exporter.
Recommended Action LOG_STD_ACTION
%FNF_PROXY-3-FLOW_CACHE_WALK : Failed for session: [hex] with return code: [dec], MSGDEF_LIMIT_MEDIUM
Explanation Netflow failed to process a flow cache walk request.
Recommended Action LOG_STD_ACTION
%FNF_PROXY-3-FLOW_CACHE_WALK_FLEXIBLE : Failed for session: [hex] with return code: [dec], MSGDEF_LIMIT_MEDIUM
Explanation Netflow failed to process a flow cache walk/flexible request.
Recommended Action LOG_STD_ACTION
%FNF_PROXY-3-FNF_CWALK_TOP_TALKERS_INVALID_SORT : This field can't be used for sort, MSGDEF_LIMIT_MEDIUM
Explanation Show Top Talkers command contains sort field specification that is not supported.
Recommended Action LOG_STD_ACTION
%FNF_PROXY-3-IPC_UNHANDLED : type [dec]
Explanation An unknown message was received by the Netflow Client Proxy.
Recommended Action LOG_STD_ACTION
%FNF_PROXY-3-MON_CACHE_AGER_INIT : Failed with return code: [dec], MSGDEF_LIMIT_MEDIUM
Explanation Netflow failed to initialize the ager.
Recommended Action LOG_STD_ACTION
%FNF_PROXY-3-MON_CACHE_AGER_SHUT : Failed with return code: [dec], MSGDEF_LIMIT_MEDIUM
Explanation Netflow failed to shutdown the ager.
Recommended Action LOG_STD_ACTION
%FNF_PROXY-3-MON_CACHE_CLEAN : Failed with return code: [dec], MSGDEF_LIMIT_MEDIUM
Explanation Netflow failed to perform cache cleanup.
Recommended Action LOG_STD_ACTION
%FNF_PROXY-3-MON_CACHE_FORCE_FLUSH : Failed with return code: [dec], MSGDEF_LIMIT_MEDIUM
Explanation Netflow failed to force a cache flush.
Recommended Action LOG_STD_ACTION
%FNF_PROXY-3-MON_CACHE_FREE_LIST_INIT : Failed with return code: [dec], MSGDEF_LIMIT_MEDIUM
Explanation Netflow failed to initialize the free list.
Recommended Action LOG_STD_ACTION
%FNF_PROXY-3-MON_CACHE_FREE_LIST_POOL_ADD : Failed with return code: [dec], MSGDEF_LIMIT_MEDIUM
Explanation Netflow failed to populate the free list.
Recommended Action LOG_STD_ACTION
%FNF_PROXY-3-OBJ_MODIFY : Failed with return code: [dec], MSGDEF_LIMIT_MEDIUM
Explanation Netflow failed to process an object modify request.
Recommended Action LOG_STD_ACTION
%FNF_PROXY-3-PROCESS_FREC_FIELD_LIST : Failed with return code: [dec], MSGDEF_LIMIT_MEDIUM
Explanation Netflow failed to process a process flow record field list request.
Recommended Action LOG_STD_ACTION
%FNF_PROXY-3-PROXY_IPC_PAK_ALLOC_FAILED :
Explanation Allocation of IPC packet failed.
Recommended Action LOG_STD_ACTION
%FNF_PROXY-3-PROXY_IPC_SEND_FAILED : [dec]
Explanation Could not send IPC reply for proxy request.
Recommended Action LOG_STD_ACTION
%FNF_PROXY-3-STATS : Failed with return code: [dec], MSGDEF_LIMIT_MEDIUM
Explanation Netflow failed to process a stats request.
Recommended Action LOG_STD_ACTION
FPD_MGMT
%FPD_MGMT-2-CREATE_FAIL : Couldn't create [chars].
Explanation The system does not have enough free main memory to create the specified resource.
Recommended Action Make sure that the system main memory size meets the minimum requirement that is specified in the Cisco IOS software release note.If the system meets the minimum requirement for this Cisco IOS software release, make sure that the amount of free main memory in the system also meets the minimum memory required to use this software feature. Use the <CmdBold>show memory<NoCmdBold> command to find out this information and add more main memory if it is necessary. If the system meets all the memory requirements, copy the error message exactly as it appears on the console and gather the output of the <CmdBold>show tech-support<NoCmdBold> command and contact your technical support representative with this information.
%FPD_MGMT-3-BNDL_CARD_TYPE_MISMATCH : The [chars] file does not contain the card type ([hex]) in the image bundle to indicate the support of the target card. Please make sure that this is a valid FPD image [chars] file for card in [chars].
Explanation The image bundle in the indicated file does not contain a correct card type value for the target card.
Recommended Action Make sure that the version of the FPD image package, which is stated in the package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the right one from the Cisco Software Center website. If the problem persists, copy the error message exactly as it appears and gather the output of the <CmdBold>show hw-module subslot fpd<NoCmdBold>, <CmdBold>show upgrade fpd table<NoCmdBold> and <CmdBold>show upgrade fpd file<NoCmdBold> <CmdArg>fpd-pkg-url<NoCmdArg> commands, then contact your technical support representative with the gathered information.
%FPD_MGMT-3-BNDL_CRC_CHECK_FAIL : The [chars] file contains a corrupted image bundle -CRC mismatch: current value [hex], expected value [hex]. Please make sure that this is a valid FPD image [chars] file for card in [chars].
Explanation The file failed the CRC checking process. This failure indicates a corrupt FPD image bundle or package file.
Recommended Action Try to download again the required package from the Cisco Software Center website as the indicated one might be corrupted. If the problem persists, copy the error message exactly as it appears and gather the output of the <CmdBold>show hw-module subslot fpd <NoCmdBold>, <CmdBold>show upgrade fpd table<NoCmdBold> and <CmdBold> show upgrade fpd file<NoCmdBold> <CmdArg>fpd-pkg-url<NoCmdArg> commands, then contact your technical support representative with the gathered information.
%FPD_MGMT-3-BNDL_NAME_PREFIX_MISMATCH : The [chars] file contains a bundle name prefix ([chars]) that does not match with the expected value of [chars] for the image bundle. Please make sure that this is a valid FPD image [chars] file for card in [chars].
Explanation The content of the selected FPD image bundle does not match its filename.
Recommended Action Make sure that the version of the FPD image package, which is stated in the package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the right one from the Cisco Software Center website. If the problem persists, copy the error message exactly as it appears and gather the output of the <CmdBold>show hw-module subslot fpd<NoCmdBold>, <CmdBold>show upgrade fpd table<NoCmdBold> and <CmdBold>show upgrade fpd file<NoCmdBold> <CmdArg>fpd-pkg-url<NoCmdArg> commands, then contact your technical support representative with the gathered information.
%FPD_MGMT-3-BNDL_WRONG_HDR_LEN : The [chars] file contains wrong header length for the image bundle: [int] bytes (expected [int] bytes). Please make sure that this is a valid FPD image [chars] file for card in [chars].
Explanation The indicated file might not be a valid FPD image bundle or package file for the target card.
Recommended Action Make sure that the version of the FPD image package, which is stated in the package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the right one from the Cisco Software Center website. If the problem persists, copy the error message exactly as it appears and gather the output of the <CmdBold>show hw-module subslot fpd<NoCmdBold>, <CmdBold>show upgrade fpd table<NoCmdBold> and <CmdBold>show upgrade fpd file<NoCmdBold> <CmdArg>fpd-pkg-url<NoCmdArg> commands, then contact your technical support representative with the gathered information.
%FPD_MGMT-3-BNDL_WRONG_MAGIC_NUM : The [chars] file contains a wrong magic number for the image bundle: [hex] (expected [hex]). Please make sure that this is a valid FPD image [chars] file for card in [chars].
Explanation The indicated file might not be a valid FPD image bundle or package file for the target card or the file could be corrupted.
Recommended Action Make sure that the version of the FPD image package, which is stated in the package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the right one from the Cisco Software Center website. If the problem persists, copy the error message exactly as it appears and gather the output of the <CmdBold>show hw-module subslot fpd<NoCmdBold>, <CmdBold>show upgrade fpd table<NoCmdBold> and <CmdBold>show upgrade fpd file<NoCmdBold> <CmdArg>fpd-pkg-url<NoCmdArg> commands, then contact your technical support representative with the gathered information.
%FPD_MGMT-3-BNDL_WRONG_SIZE : The [chars] file contains incorrect image bundle size: [int] bytes (expected [int] bytes). Please make sure that this is a valid FPD image [chars] file for card in [chars].
Explanation The indicated file might not be a valid FPD image bundle or package file for the target card.
Recommended Action Make sure that the version of the FPD image package, which is stated in the package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the right one from the Cisco Software Center website. If the problem persists, copy the error message exactly as it appears and gather the output of the <CmdBold>show hw-module subslot fpd<NoCmdBold>, <CmdBold>show upgrade fpd table<NoCmdBold> and <CmdBold>show upgrade fpd file<NoCmdBold> <CmdArg>fpd-pkg-url<NoCmdArg> commands, then contact your technical support representative with the gathered information.
%FPD_MGMT-3-BUNDLE_EXTRACT_ERROR : Cannot extract the [chars] bundle from [chars] -[chars]
Explanation Bundle file extraction error. The cause of the failure is indicated in the error message. The indicated file might not be a valid FPD image package file.
Recommended Action Make sure that the version of the FPD image package, which is stated in the package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the right one from the Cisco Software Center website. If the problem persists, copy the error message exactly as it appears and gather the output of the <CmdBold>show hw-module subslot fpd<NoCmdBold>, <CmdBold>show upgrade fpd table<NoCmdBold> and <CmdBold>show upgrade fpd file<NoCmdBold> <CmdArg>fpd-pkg-url<NoCmdArg> commands, then contact your technical support representative with the gathered information.
%FPD_MGMT-3-CARD_DISABLED : [chars] card in [chars] is being disabled because of an incompatible FPD image version. Note that the [chars] package will be required if you want to perform the upgrade operation.
Explanation The indicated card contains an incompatible FPD image version, and is being disabled to avoid operational problems with the existing Cisco IOS software. This can happen if the automatic upgrade feature has not been enabled with the <CmdBold>upgrade fpd auto<NoCmdBold> global configuration command or if the automatic upgrade operation failed to perform the required upgrade or because it could not find the necessary FPD image package file. The incompatible image will need to be upgraded in order for the system to enable the card.
Recommended Action The FPD image upgrade can be performed automatically by making sure that the automatic upgrade feature is enabled with the <CmdBold>upgrade fpd auto<NoCmdBold> global configuration command and the necessary FPD image package file is located in the system's default filesystem (e.g. disk0:) or in a location indicated by the <CmdBold>upgrade fpd path<NoCmdBold> <CmdArg>directory-url<NoCmdArg> global configuration command. When the automatic upgrade feature is enabled, then the upgrade is triggered by the reinsertion of the card to the system or the use of a system command to reload or power-cycle the target card. Another way to perform the upgrade is through the use of the <CmdBold> upgrade hw-module<NoCmdBold> privileged EXEC command. For more information about these commands, refer to the FPD_DOCUMENT_NAME.
%FPD_MGMT-3-CLOSE_FAILED : Failed to close [chars] file.
Explanation FPD_INTERNAL_SW_ERR_STD_EXPLANATION
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FPD_MGMT-3-DUPLICATE_UPGRADE_RESULT : Upgrade result already received for the FPD image upgrade of FPD ID [int] for [chars] card in [chars].
Explanation FPD_INTERNAL_SW_ERR_STD_EXPLANATION
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FPD_MGMT-3-FPD_UPGRADE_CANCELED : Rest of the FPD upgrade sequence for [chars] card in [chars] has been canceled due to upgrade failure with [chars] (FPD ID=[int]) image.
Explanation The FPD image upgrade process for additional FPD images has been canceled due to upgrade error in the indicated device.
Recommended Action Retry the upgrade operation again. If the affected card remains disabled by the system after attempts to retry the upgrade, then copy the error message exactly as it appears and gather the output of <CmdBold>show hw-module subslot fpd<NoCmdBold> and contact your technical support representative with the gathered information.
%FPD_MGMT-3-FPD_UPGRADE_FAILED : [chars] (FPD ID=[int]) image upgrade for [chars] card in [chars] has FAILED.
Explanation The FPD image upgrade process has failed for the indicated device.
Recommended Action Retry the upgrade operation again. If the affected card remains disabled by the system after attempts to retry the upgrade, then copy the error message exactly as it appears and gather the output of <CmdBold>show hw-module subslot fpd<NoCmdBold> and contact your technical support representative with the gathered information.
%FPD_MGMT-3-IMG_CRC_CHECK_FAILED : The FPD image for [chars] (FPD ID [int]) in [chars] file is corrupted -CRC mismatch: current value [hex], expected value [hex]. Please make sure that this is a valid FPD image bundle or package file for card in [chars].
Explanation The image failed the CRC checking process, this indicates a corrupt FPD image bundle or package file.
Recommended Action Make sure that the version of the FPD image package, which is stated in the package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the right one from the Cisco Software Center website. If the problem persists, copy the error message exactly as it appears and gather the output of the <CmdBold>show hw-module subslot fpd<NoCmdBold>, <CmdBold>show upgrade fpd table<NoCmdBold> and <CmdBold>show upgrade fpd file<NoCmdBold> <CmdArg>fpd-pkg-url<NoCmdArg> commands, then contact your technical support representative with the gathered information.
%FPD_MGMT-3-IMG_DATA_UNCOMPRESS_ERROR : Could not uncompress [chars] FPD image for [chars] in [chars].
Explanation An error has been detected during the uncompress operation of the compressed FPD image data.
Recommended Action Make sure that the version of the FPD image package, which is stated in the package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the right one from the Cisco Software Center website. If the problem persists, copy the error message exactly as it appears and gather the output of the <CmdBold>show hw-module subslot fpd<NoCmdBold>, <CmdBold>show upgrade fpd table<NoCmdBold> and <CmdBold>show upgrade fpd file<NoCmdBold> <CmdArg>fpd-pkg-url<NoCmdArg> commands, then contact your technical support representative with the gathered information.
%FPD_MGMT-3-INVALID_IMG_FORMAT : Invalid image format '[chars]' detected for FPD ID=[int].
Explanation The selected FPD image to upgrade the indicated field programmable device does not have the right image format that can be used by the system to perform the upgrade operation.
Recommended Action Please check if the FPD image package used in the upgrade is for the correct platform. This can be checked by using the <CmdBold>show upgrade fpd package default<NoCmdBold> privileged EXEC command.
%FPD_MGMT-3-IMG_VER_NOT_FOUND : FPD image version information is not available for [chars] card in [chars]. All the FPD images will be upgraded to recover from this error.
Explanation The FPD image version information for the indicated card is not available because the system was not able to extract this information for all the FPDs in the card. This could be the result of a corrupted FPD image from a power failure.
Recommended Action If the automatic upgrade feature is not enabled, then the affected card will be disabled. If this happens, then follow the recommended action described for the FPD_MGMT-3-CARD_DISABLED message.
%FPD_MGMT-3-INCOMP_BNDL_VER : The selected [chars] file contain an image bundle that has a version number that is incompatible for this IOS release -[chars]. Selected version = [int].[int], minimum compatible version = [int].[int]. Please make sure that this is a valid FPD image [chars] file for card in [chars]. The SPA type is [chars].
Explanation The version of the selected FPD image bundle does not contain a valid version number that is compatible for the IOS release. The major version number should be the same and the minor version number should be at least equal to the minimal required version.
Recommended Action Make sure that the version of the FPD image package, which is stated in the package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the right one from the Cisco Software Center website. If the problem persists, copy the error message exactly as it appears and gather the output of the <CmdBold>show hw-module subslot fpd<NoCmdBold>, <CmdBold>show upgrade fpd table<NoCmdBold> and <CmdBold>show upgrade fpd file<NoCmdBold> <CmdArg>fpd-pkg-url<NoCmdArg> commands, then contact your technical support representative with the gathered information.
%FPD_MGMT-3-INCOMP_IMG_VER : Incompatible [chars] (FPD ID=[int]) image version detected for [chars] card in [chars]. Detected version = [int].[int], minimum required version = [int].[int]. Current HW version = [int].[int].
Explanation An incompatible FPD image version has been detected. The FPD image needs to be upgraded either automatically, or manually, to make the card operational. If the automatic upgrade feature is not enabled, or if the system cannot find the necessary FPD image package file, then the card will be disabled.
Recommended Action If the automatic upgrade feature is not enabled, then the affected card will be disabled. If this happens, then follow the recommended action described for the FPD_MGMT-3-CARD_DISABLED message.
%FPD_MGMT-3-INVALID_IMAGE_SIZE : The [chars] FPD image from [chars] file does not have a valid image size: expected size = [dec] bytes, actual size = [dec] bytes.
Explanation The size of the indicated FPD image does not have the expected size. The FPD image bundle or package might not be a valid file.
Recommended Action Make sure that the version of the FPD image package, which is stated in the package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the right one from the Cisco Software Center website. If the problem persists, copy the error message exactly as it appears and gather the output of the <CmdBold>show hw-module subslot fpd<NoCmdBold>, <CmdBold>show upgrade fpd table<NoCmdBold> and <CmdBold>show upgrade fpd file<NoCmdBold> <CmdArg>fpd-pkg-url<NoCmdArg> commands, then contact your technical support representative with the gathered information.
%FPD_MGMT-3-INVALID_IMG_VER : Invalid [chars] (FPD ID=[int]) image version detected for [chars] card in [chars].
Explanation The indicated field programmable device contains an invalid version for the FPD image, because the system was not able to extract this information from the indicated card. A failed upgrade attempt might have corrupted the FPD image identification on the device.
Recommended Action If the automatic upgrade feature is not enabled, then the affected card will be disabled. If this happens, then follow the recommended action described for the FPD_MGMT-3-CARD_DISABLED message.
%FPD_MGMT-3-INVALID_PKG_FILE : The indicated file ([chars]) is not a valid FPD image package file -[chars]
Explanation The file format does not appear to be a valid FPD image package.
Recommended Action Make sure that the version of the FPD image package, which is stated in the package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the right one from the Cisco Software Center website. If the problem persists, copy the error message exactly as it appears and gather the output of the <CmdBold>show hw-module subslot fpd<NoCmdBold>, <CmdBold>show upgrade fpd table<NoCmdBold> and <CmdBold>show upgrade fpd file<NoCmdBold> <CmdArg>fpd-pkg-url<NoCmdArg> commands, then contact your technical support representative with the gathered information.
%FPD_MGMT-3-INVALID_PKG_FILE_SIZE : The indicated file ([chars]) does not have a valid FPD image package file size, minimum size = [dec] bytes.
Explanation The file size of the indicated FPD image package does not meet the required minimum size. The file is too small to be a valid FPD image package file.
Recommended Action Make sure that the version of the FPD image package, which is stated in the package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the right one from the Cisco Software Center website. If the problem persists, copy the error message exactly as it appears and gather the output of the <CmdBold>show hw-module subslot fpd<NoCmdBold>, <CmdBold>show upgrade fpd table<NoCmdBold> and <CmdBold>show upgrade fpd file<NoCmdBold> <CmdArg>fpd-pkg-url<NoCmdArg> commands, then contact your technical support representative with the gathered information.
%FPD_MGMT-3-INVALID_UPGRADE_RESULT : Invalid upgrade result '[int]' received for the FPD image upgrade of [chars] (FPD ID=[int]) for [chars] card in [chars].
Explanation FPD_INTERNAL_SW_ERR_STD_EXPLANATION
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FPD_MGMT-3-IPC_FAILED : Failed to send IPC message to [chars] in [chars] -[chars]
Explanation The system failed to send a message via IPC to the indicated card. The cause of the specific IPC failure is inicated in the message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FPD_MGMT-3-MAJOR_VER_MISMATCH : Major image version mismatch detected with [chars] (FPD ID=[int]) for [chars] card in [chars]. Image will need to be [chars] from version [int].[int] to at least a minimum version of [int].[int]. Current HW version = [int].[int].
Explanation A major image version mismatch has been detected. This incompatibility will need to be resolved by doing an upgrade or downgrade operation either automatically, or manually, to make the card operational. If the automatic upgrade feature is not enabled, or if the system cannot find the necessary FPD image package file, then the card will be disabled.
Recommended Action If the automatic upgrade feature is not enabled, then the affected card will be disabled. If this happens, then follow the recommended action described for the FPD_MGMT-3-CARD_DISABLED message.
%FPD_MGMT-3-MISSING_BUNDLE_ENTRY : Failed to find a matching entry in the programmable device bundle information table for [chars] in [chars]. Card type or HW version ([int].[int]) might not have FPD support.
Explanation FPD_INTERNAL_SW_ERR_STD_EXPLANATION
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FPD_MGMT-3-MISSING_DEV_INFO : Could not find [chars] (FPD ID=[int]) in the list of FPD IDs populated for [chars] card in [chars].
Explanation FPD_INTERNAL_SW_ERR_STD_EXPLANATION
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FPD_MGMT-3-MISSING_IMAGE : Could not find the required [chars] image (FPD ID=[int] and FPD version=[int].[int] compatible with HW version=[int].[int]) from the [chars]-fpd.bndl bundle in [chars] file. Please make sure that this is a valid FPD image [chars] file for [chars] card in [chars].
Explanation The indicated FPD image bundle or package file might not be the correct one. IF this is a FPD image package file, then an incompatible package file might have been renamed with a filename that matched with the one that the system is expecting for this Cisco IOS software release. You should never rename an FPD image package file name.
Recommended Action Make sure that the version of the FPD image package, which is stated in the package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the right one from the Cisco Software Center website. If the problem persists, copy the error message exactly as it appears and gather the output of the <CmdBold>show hw-module subslot fpd<NoCmdBold>, <CmdBold>show upgrade fpd table<NoCmdBold> and <CmdBold>show upgrade fpd file<NoCmdBold> <CmdArg>fpd-pkg-url<NoCmdArg> commands, then contact your technical support representative with the gathered information.
%FPD_MGMT-3-OPEN_FAILED : Failed to open [chars] ([chars]). Please make sure that the required file is in a valid path.
Explanation The system cannot access the required file from the indicated URL.
Recommended Action Make sure that the indicated URL is a valid path, and the system has access to the filesystem where the file has been placed.
%FPD_MGMT-3-OUT_OF_MEMORY : Could not allocate the required [dec] bytes of memory.
Explanation The system does not have enough free main memory to download the bundle file.
Recommended Action Make sure that the system main memory size meets the minimum requirement that is specified in the Cisco IOS software release note.If the system meets the minimum requirement for this Cisco IOS software release, make sure that the amount of free main memory in the system also meets the minimum memory required to use this software feature. Use the <CmdBold>show memory<NoCmdBold> command to find out this information and add more main memory if it is necessary. If the system meets all the memory requirements, copy the error message exactly as it appears on the console and gather the output of the <CmdBold>show tech-support<NoCmdBold> command and contact your technical support representative with this information.
%FPD_MGMT-3-PKG_VER_FILE_EXTRACT_ERROR : Cannot extract the [chars] version file from [chars] -[chars]
Explanation Package version file extraction error. The cause of the failure is indicated in the error message. The indicated file might not be a valid FPD image package file.
Recommended Action Make sure that the version of the FPD image package, which is stated in the package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the right one from the Cisco Software Center website. If the problem persists, copy the error message exactly as it appears and gather the output of the <CmdBold>show hw-module subslot fpd<NoCmdBold>, <CmdBold>show upgrade fpd table<NoCmdBold> and <CmdBold>show upgrade fpd file<NoCmdBold> <CmdArg>fpd-pkg-url<NoCmdArg> commands, then contact your technical support representative with the gathered information.
%FPD_MGMT-3-PKG_FILE_SEARCH_FAILED : FPD image package ([chars]) cannot be found in system's flash card or disk to do FPD upgrade.
Explanation By default, if the <CmdBold>upgrade fpd path<NoCmdBold> <CmdArg>fpd-pkg-url<NoCmdArg> global configuration command is not configured, then the system will try to locate the required FPD image package file from removable flash cards or disks that are accessible by the system for FPD upgrade. This message indicates that the system could not find the package file.
Recommended Action Make sure that the indicated FPD image package file is copied into a flash card or disk that is accessible by the system, then restart the FPD upgrade by reinsertion of the target card to the system or use of a system command to reload or power-cycle the target card.
%FPD_MGMT-3-PKG_VER_MISMATCH_NOTE : The FPD image package being used ([chars]) is not the right version for this IOS version (it appears that a '[chars]' package was renamed to '[chars]'). An attempt to find the required FPD image will still be performed with this package.
Explanation The indicated FPD image package that is being used in FPD automatic upgrade does not contain the correct version information for the IOS version that is running in the system. This condition can occur if a different version of the FPD image package was renamed to match the filename that the IOS image is expecting to use. The upgrade operation will still be performed by trying to find the required FPD image from the renamed package file.
Recommended Action If the upgrade operation fails because the required FPD image cannot be found with the renamed FPD image package, replace the wrong package file with a valid one and perform the upgrade operation again.
%FPD_MGMT-3-READ_BNDL_HDR_ERROR : Failed to read the FPD bundle header from [chars] file.
Explanation The indicated file might not be a valid FPD image bundle or package file.
Recommended Action Make sure that the version of the FPD image package, which is stated in the package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the right one from the Cisco Software Center website. If the problem persists, copy the error message exactly as it appears and gather the output of the <CmdBold>show hw-module subslot fpd<NoCmdBold>, <CmdBold>show upgrade fpd table<NoCmdBold> and <CmdBold>show upgrade fpd file<NoCmdBold> <CmdArg>fpd-pkg-url<NoCmdArg> commands, then contact your technical support representative with the gathered information.
%FPD_MGMT-3-READ_ERROR : Could not read the [chars] file.
Explanation The system cannot read the required file from the indicated URL.
Recommended Action Make sure that the indicated URL is a valid path, and the system has access to the filesystem where the file has been placed.
%FPD_MGMT-3-SEND_IMG_FAILED : [chars] (FPD ID=[int]) image for [chars] card in [chars] has failed to be sent for upgrade operation -[chars]
Explanation The FPD image was not able to be sent for the upgrade operation. The system might be too busy to handle this operation. The affected card will be disabled by this failure.
Recommended Action Wait until the system load is lower to try again with the manual upgrade procedure by using the <CmdBold>upgrade hw-module<NoCmdBold> privileged EXEC command. If the symptom persists, copy the error message exactly as it appears and gather the output of the <CmdBold>show tech-support<NoCmdBold> command and contact your technical support representative with the gathered information.
%FPD_MGMT-3-TOO_MANY_FPD_ENTRIES : Too many FPD entries for the FPD Bundle Info Table. Required number of entries = [int], maximum number of entries allowed = [int].
Explanation FPD_INTERNAL_SW_ERR_STD_EXPLANATION
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FPD_MGMT-3-UNKNOWN_BNDL_HDR_FORMAT : Unknown header format version: [hex]
Explanation FPD_INTERNAL_SW_ERR_STD_EXPLANATION
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FPD_MGMT-3-WRONG_IMG_DATA_LEN : The FPD image for [chars] (FPD ID [int]) in [chars] file contains wrong data length: total data length (with padding) = [int] bytes, data length = [int] bytes. Please make sure that this is a valid FPD image bundle or package file for card in [chars].
Explanation The indicated file might not be a valid FPD image bundle or package file for the card.
Recommended Action Make sure that the version of the FPD image package, which is stated in the package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the right one from the Cisco Software Center website. If the problem persists, copy the error message exactly as it appears and gather the output of the <CmdBold>show hw-module subslot fpd<NoCmdBold>, <CmdBold>show upgrade fpd table<NoCmdBold> and <CmdBold>show upgrade fpd file<NoCmdBold> <CmdArg>fpd-pkg-url<NoCmdArg> commands, then contact your technical support representative with the gathered information.
%FPD_MGMT-3-WRONG_IMG_HDR_LEN : The FPD image for [chars] (FPD ID [int]) in [chars] file contains wrong header length: [int] bytes (expected [int] bytes). Please make sure that this is a valid FPD image bundle or package file for card in [chars].
Explanation The indicated file might not be a valid FPD image bundle or package file for the card.
Recommended Action Make sure that the version of the FPD image package, which is stated in the package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the right one from the Cisco Software Center website. If the problem persists, copy the error message exactly as it appears and gather the output of the <CmdBold>show hw-module subslot fpd<NoCmdBold>, <CmdBold>show upgrade fpd table<NoCmdBold> and <CmdBold>show upgrade fpd file<NoCmdBold> <CmdArg>fpd-pkg-url<NoCmdArg> commands, then contact your technical support representative with the gathered information.
%FPD_MGMT-3-WRONG_IMG_MAGIC_NUM : The FPD image for [chars] (FPD ID [int]) in [chars] file contains wrong magic number: [hex] (expected [hex]). Please make sure that this is a valid FPD image bundle or package file for card in [chars].
Explanation The indicated file might not be a valid FPD image bundle or package file for the card.
Recommended Action Make sure that the version of the FPD image package, which is stated in the package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the right one from the Cisco Software Center website. If the problem persists, copy the error message exactly as it appears and gather the output of the <CmdBold>show hw-module subslot fpd<NoCmdBold>, <CmdBold>show upgrade fpd table<NoCmdBold> and <CmdBold>show upgrade fpd file<NoCmdBold> <CmdArg>fpd-pkg-url<NoCmdArg> commands, then contact your technical support representative with the gathered information.
%FPD_MGMT-3-WRONG_IMG_MAJOR_VER : The selected FPD image for upgrade contains wrong FPD image major version number = '[int]' (expected number = '[int]') for [chars] (FPD ID [int]). Please make sure that the file being used for upgrade is a valid FPD image [chars] for card in [chars].
Explanation The file used for upgrade might not be a valid FPD image bundle or package file for the card.
Recommended Action Make sure that the version of the FPD image package, which is stated in the package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the right one from the Cisco Software Center website. If the problem persists, copy the error message exactly as it appears and gather the output of the <CmdBold>show hw-module subslot fpd<NoCmdBold>, <CmdBold>show upgrade fpd table<NoCmdBold> and <CmdBold>show upgrade fpd file<NoCmdBold> <CmdArg>fpd-pkg-url<NoCmdArg> commands, then contact your technical support representative with the gathered information.
%FPD_MGMT-4-BYPASS_AUTO_UPGRADE : The automatic FPD image upgrade feature is not enabled, bypassing the image upgrade for [chars] card in [chars].
Explanation The automatic FPD image upgrade feature is not enabled. The incompatible image will not be automatically upgraded. The card will be disabled until the image is upgraded to a compatible version.
Recommended Action Enable the automatic FPD image upgrade with the <CmdBold>upgrade fpd auto<NoCmdBold> global configuration command or use the <CmdBold>upgrade hw-module<NoCmdBold> privileged EXEC command for a manual upgrade operation. For more information about these commands, refer to the FPD_DOCUMENT_NAME .
%FPD_MGMT-4-CFG_NOT_SYNCED : Failed to sync [chars] command to standby: [chars]
Explanation A FPD configuration command failed to get synced to standby RP due to the indicated error condition. Usually this can happen if the standby RP hardware doesn't support the type of filesystem supported on the active one.
Recommended Action Configure again the command with a filesystem that is supported on both standby and active RP. To find out if a specific filesystem is also supported on standby RP, the <CmdBold>dir ?<NoCmdBold> command can be used to display a list of filesytem supported on both standby and active RP.
%FPD_MGMT-3-SW_ERROR : NULL
Explanation FPD_INTERNAL_SW_ERR_STD_EXPLANATION
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FPD_MGMT-4-UPGRADE_EXIT : Unexpected exit of FPD image upgrade operation for [chars] card in [chars].
Explanation The FPD image upgrade operation was interrupted by the physical removal of the card from the system or by the use of other commands that have interrupted the normal operation of the target card. The partial upgrade operation might have left the card unusable because of corrupted FPD images.
Recommended Action If the card does not come up after reinserting into the system, then perform the recovery upgrade operation by using the <CmdBold>upgrade hw-module<NoCmdBold> privileged EXEC command. With this command the system will attempt the reprogramming of the image to recover from the previous partial upgrade operation. For more information about performing a recovery upgrade operation, refer to the FPD_DOCUMENT_NAME.
%FPD_MGMT-3-UPGRADE_LIST_FULL : Could not add a new entry in the FPD Management Upgrade List. No upgrade will be performed for the [chars] card in [chars].
Explanation FPD_INTERNAL_SW_ERR_STD_EXPLANATION
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FPD_MGMT-4-VERSION_CHECK_ABORTED : FPD image version check operation has been aborted for [chars] card in [chars] because manual upgrade has already being started.
Explanation The FPD image version check operation required for the automatic upgrade feature is not being performed for the indicated card because the <CmdBold>upgrade hw-module<NoCmdBold> privileged EXEC command has already being executed. These two operations cannot be performed at the same time.
Recommended Action If an automatic upgrade operation is required, do not enter the <CmdBold>upgrade hw-module<NoCmdBold> privileged EXEC command for the manual upgrade while the target card is initializing. Enter the <CmdBold>show hw-module subslot fpd<NoCmdBold> command and ensure that the target card is displayed in the command output before proceeding with the manual upgrade.
%FPD_MGMT-5-CARD_POWER_CYCLE : [chars] card in [chars] is being power cycled for the FPD image upgrade to take effect.
Explanation The indicated card is being power cycled after the FPD image upgrade. This action allows the target card to be operational with the new upgraded FPD image or images.
Recommended Action No action is required.
%FPD_MGMT-5-POST_UPGRADE_REMINDER : [chars] card in [chars] will require a [chars] for the FPD image upgrade to take effect.
Explanation The indicated card will require manual intervention after the FPD image upgrade. The specified operation is required for the upgraded FPD image to take effect.
Recommended Action No action is required.
%FPD_MGMT-5-UPGRADE_ATTEMPT : Attempting to automatically upgrade the FPD image(s) for [chars] card in [chars]. Use 'show upgrade fpd progress' command to view the upgrade progress ...
Explanation The automatic FPD image upgrade feature is enabled with the <CmdBold> upgrade fpd auto<NoCmdBold> global configuration command. The system is currently upgrading an incompatible image version automatically.
Recommended Action No action is required. The upgrade process can take a long time.The FPD_MGMT-6-UPGRADE_TIME message gives an estimate of the total upgrade time
%FPD_MGMT-6-BUNDLE_DOWNLOAD : Downloading FPD image bundle for [chars] card in [chars] ...
Explanation The system is downloading the field programmable device image bundle to the system main memory.
Recommended Action No action is required.
%FPD_MGMT-6-OVERALL_UPGRADE : All the attempts to upgrade the required FPD images have been completed for [chars] card in [chars]. Number of successful/failure upgrade(s): [int]/[int].
Explanation All the FPD image upgrades have completed for the indicated card.
Recommended Action No action is required.
%FPD_MGMT-6-PENDING_UPGRADE : [int] more FPD image upgrade operation will be required on [chars] in [chars] after additional power-cycle operation on the target card.
Explanation All upgrade operations have not completed, and additional power-cycle operations are required before the upgraded or new FPD image will be applied to the system configuration. The message text indicates the number of pending upgrade operations that will be performed. More than one power-cycle operation might be required to complete the overall upgrade process.
Recommended Action No action is required.
%FPD_MGMT-6-UPGRADE_PASSED : [chars] (FPD ID=[int]) image in the [chars] card in [chars] has been successfully updated from version [chars] to version [int].[int]. Upgrading time = %lTE
Explanation The FPD image upgrade process has completed successfully for the indicated device.
Recommended Action No action is required.
%FPD_MGMT-6-UPGRADE_RETRY : Attempting to recover from the failed upgrades ...
Explanation Because of an image upgrade failure, the system will attempt again the upgrade operation for the same FPD image.
Recommended Action No action is required.
%FPD_MGMT-6-UPGRADE_START : [chars] (FPD ID=[int]) image upgrade in progress for [chars] card in [chars]. Updating to version [int].[int]. PLEASE DO NOT INTERRUPT DURING THE UPGRADE PROCESS (estimated upgrade completion time = %TS) ... FPD upgrade in progress on hardware, reload/configuration change on those hardware is not recommended as it might cause HW programming failure and result in RMA of the hardware.
Explanation The FPD image upgrade process has started. Do not interrupt the upgrade operation as any interruption could render the target card unusable. Avoid actions like removing the target card from the system, powering off the system, or using commands that can power-cycle the target card during the upgrade process.
Recommended Action No action is required.
%FPD_MGMT-6-UPGRADE_TIME : Estimated total FPD image upgrade time for [chars] card in [chars] = %TS.
Explanation The estimated total time for all FPD images to be upgraded is displayed for the indicated card.
Recommended Action No action is required.
FR
%FR-3-BQ_DEQ_ERR : fr_bq_proc: unknown packet on broadcast queue, packet dropped!
Explanation Invalid packet on FR broadcast queue, packet dropped!
Recommended Action If the router or some features are not operational due to this condition, attempt to disable the Frame Relay broadcast queue by entering the <CmdBold>no frame-relay broadcast-queue<NoCmdBold> command in interface configuration mode for a immediate workaround. And LOG_STD_ACTION
%FR-3-BQ_DEQ_PTR : fr_br_proc: hdr-[hex] size-[dec] dlci-[hex] [hex] [hex]
Explanation The Frame Relay broadcast queue contains a datagram that is invalid. The packet has been dropped.
Recommended Action Inform Cisco technical support representative
%FR-3-BQ_ENQ_ERR : fr_oqueue: Invalid datagramstart [hex] [hex], pak dropped
Explanation A broadcast packet was detected in the Frame Relay output queue that contained an invalid datagram header. The packet has been dropped.
Recommended Action If the router or some features are not operational due to this condition, attempt to disable the Frame Relay broadcast queue by entering the <CmdBold>no frame-relay broadcast-queue<NoCmdBold> command in interface configuration mode for a immediate workaround. And LOG_STD_ACTION
%FR-3-FR_INV_OUTPUT_VECTOR : An invalid output vector detected on interface [chars]
Explanation An invalid internal function vector is installed on a Frame Relay interface, which affects the ability of processing outbound traffic on the device.
Recommended Action Remove and re-apply Frame Relay encapsulation on the interface to recover from the error.
%FR-3-FR_PVC_STATUS_Q_CREATE_ERROR : FR PVC status event queue error: failed to create queue
Explanation Unable to create FR PVC status event queue
Recommended Action LOG_STD_ACTION
%FR-3-FRTSZEROCIR : FRTS: attempt to configure zero CIR
Explanation It should not be possible to configure a zero CIR. To do so would prevent data transmission on the VC.
Recommended Action Inform Cisco technical support representative
%FR-3-MAP_DELETE_ERROR : [chars]
Explanation An error occurred while deleting a frame-relay map
Recommended Action LOG_STD_ACTION
%FR-3-MFR_UNEXPECTEDEVENT : MFR Timer process error: event table is NULL for event [dec], state [dec]
Explanation The event was ignored because the state transition table is NULL. Normal processing continue.
Recommended Action Please refer to Bug Toolkit on CCO to check for existing bugs. If you need further assistance, please provide 'show version' and 'show running' and any configurations that were being done at the time the message was seen. Copy the message text exactly as it appears on the console or in the system log. Inform Cisco technical support representative, and provide the representative with the gathered information.
%FR-3-MLPOFR_ERROR : MLPoFR not configured properly on Link [chars] Bundle [chars] :[chars]
Explanation The configuration of MLPPP-over-Frame-Relay (MLPoFR) on the FR PVC is either incorrect or incomplete.
Recommended Action Ensure that FRTS has been configured on physical interface and that the service policy has been attached to the Virtual Template. To verify the configuration, use the <CmdBold>show running-config serial inteface and <CmdBold>show running-config virtual-template commands.
%FR-3-NOMEMORY : No memory for [chars]
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.
%FR-3-NULL_PTR_DEREF : Dereferencing NULL pointer [chars]
Explanation Dereferencing a NULL pointer
Recommended Action Inform Cisco technical support representative
%FR-3-SVC_SETUP : [chars]: interface [chars]: DLCI [dec]
Explanation An error occurred while attempting to setup a Frame-Relay SVC. There may have been an attempt to setup a SVC using a DLCI thats already in use
Recommended Action Check if the DLCI is already in use. For example: A PVC may be configured to use the same DLCI (use <CmdBold>show frame-relay pvc<CmdBold> to verify). If so, please remove the configuration
%FR-4-DLCIDELETE : Interface [chars] -DLCI [dec] -PVC use count [dec]
Explanation Trying to remove PVC DLCI while it is still being used.
Recommended Action If this error can be easily recreated, enter the <CmdBold>debug frame-relay event<NoCmdBold> command and recreate the condition that caused this error. Copy all the debug messages text and the system message text exactly as it appears on the console or in the system log, enter the show tech-support command, contact your Cisco technical support representative, and provide the representative with the gathered information.
%FR-4-NNISUBINTF : Subinterface not supported on Frame Relay NNI
Explanation Trying to change the state of a subinterface on FR NNI.
Recommended Action Reconfigure the Frame Relay link type or remove the subinterface.
%FR-5-CONVERT_ROUTE : Converting route pair to connect
Explanation A pair of Frame Relay routes are being converted to connections.
Recommended Action No action is required.
%FR-5-DLCICHANGE : Interface [chars] -DLCI [dec] state changed to [chars]
Explanation The state of the Frame Relay PVC specified by the DLCI changed.
Recommended Action Notification message only. No action required.
FRAG
%FRAG-2-UNENABLED : [chars] feature not enabled at interface [chars], packet cannot be processed, MSGDEF_LIMIT_SLOW
Explanation Reassembly or fragmentation feature as indicated not enabled by the control plane. This is a critical problem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FRAG-3-FRAG_DESC_MEM_INIT_FAILED :
Explanation Failure occurred initializing fragment descriptor pool.
Recommended Action LOG_STD_ACTION
%FRAG-3-FRAG_DESC_MEM_REQ_FAILED :
Explanation IPC Failure occurred when attempting to request more fragment descriptor pool memory.
Recommended Action LOG_STD_ACTION
%FRAG-3-FRAG_STATE_MEM_INIT_FAILED :
Explanation Failure occurred initializing fragment state pool.
Recommended Action LOG_STD_ACTION
%FRAG-3-FRAG_STATE_MEM_REQ_FAILED :
Explanation IPC failure occurred when attempting to request more fragment state pool memory.
Recommended Action LOG_STD_ACTION
%FRAG-3-INVALID_MTU : [chars] feature failed at interface [chars] due to invalid L3 MTU [int], MSGDEF_LIMIT_SLOW
Explanation Fragmentation was not able to be performed due to invalid adj L3 MTU given by the control plane.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FRAG-3-INVALID_QFP_NO : Invalid qfp device no.: [chars]
Explanation Invalid qfp device no.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FRAG-3-REASSEMBLY_DBG : Reassembly/VFR encountered an error: [chars], [chars] [int], [chars] [int]
Explanation Reassembly/VFR encountered a runtime error as indicated in the message with parameter data for debug
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%FRAG-3-REASSEMBLY_ERR : Reassembly/VFR encountered an error: [chars]
Explanation Reassembly/VFR encountered a runtime error as indicated
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
FRAG_DESC_PROXY
%FRAG_DESC_PROXY-3-PROXY_IPC_FRAG_MEM_EXTEND_FAILED :
Explanation Increasing of fragment descriptor pool failed.
Recommended Action LOG_STD_ACTION
%FRAG_DESC_PROXY-3-PROXY_IPC_FRAG_MEM_INIT_FAILED :
Explanation Initialization of fragment descriptor pool failed.
Recommended Action LOG_STD_ACTION
%FRAG_DESC_PROXY-3-PROXY_IPC_INIT_FAILED : [dec]
Explanation IPC handler initialization failed.
Recommended Action LOG_STD_ACTION
%FRAG_DESC_PROXY-3-PROXY_IPC_VFR_MEM_EXTEND_FAILED :
Explanation Increasing of vFR state pool failed.
Recommended Action LOG_STD_ACTION
%FRAG_DESC_PROXY-3-PROXY_IPC_VFR_MEM_INIT_FAILED :
Explanation Initialization of vFR state pool failed.
Recommended Action LOG_STD_ACTION
%FRAG_DESC_PROXY-4-PROXY_IPC_INVALID_MSG : [hex]
Explanation Invalid IPC message subtype.
Recommended Action LOG_STD_ACTION
FR_ELMI
%FR_ELMI-3-INCORRECT_ID : Incorrect ID
Explanation Incorrect ID in QOS parameter message.
Recommended Action None
%FR_ELMI-3-INCORRECT_IE : Incorrect IE
Explanation Enhanced LMI is not configured on the interface. The frame was dropped.
Recommended Action None
FR_FRAG
%FR_FRAG-3-BADPAK : Inconsistent packet: size [dec], linktype [chars], input [chars], output [chars]
Explanation A packet being fragmented has inconsistent size and data
Recommended Action Inform Cisco technical support representative
FR_HA
%FR_HA-3-ISSU : [chars]: [chars]
Explanation A Frame Relay ISSU error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%FR_HA-3-SYNC : [chars]: code [dec]
Explanation An error occurred when syncing Frame Relay state to the Standby Route Processor. This may affect Non-Stop Forwarding capability on Frame Relay interfaces during and after switchover until the state is recovered through normal protocol operation.
Recommended Action Reset the standby processor to attempt the sync again. LOG_STD_RECUR_ACTION
FR_LMI
%FR_LMI-3-INCORRECT_IE : Enhanced LMI not configured, incorrect IE
Explanation An unexpected LMI information element has been received.
Recommended Action Verify the configuration for enhanced LMI on the switch matches the c onfiguration on the router.
%FR_LMI-3-MSG_TOO_BIG : [chars] ([chars]) Status message too big, status of PVCs with dlci values from [dec] will not be reported.
Explanation LMI STATUS message size is too big to fit into interface MTU.
Recommended Action LMI type - cisco - does not support segmentation of STATUS message, so either increase the interface MTU or use LMI types - ansi or q933a.
FR_VCB
%FR_VCB-3-ADJ_SRC_ERROR : Error sourcing adjacency -vc-bundle [chars] dlci [dec]
Explanation An error occurred while setting up the adj for a member pvc
Recommended Action Try reconfiguring the vc-bundle
%FR_VCB-3-BUMPING : Bumping error -vcb [chars] -[chars]
Explanation An error occurred while bumping traffic in a vc-bundle
Recommended Action As a workaround, reconfigure the vc-bundle to avoid bumping
%FR_VCB-3-CONFIG : Configuration error -vcb [chars] -[chars]
Explanation An error occurred while interpreting vc-bundle configuration
Recommended Action Try reconfiguring the vc-bundle
%FR_VCB-3-FIBSW_MISSING_TABLE_ENTRY : FIB switching error -vc-bundle [chars]
Explanation An error occurred while FIB switching packet(s) across vc-bundle
Recommended Action As a workaround, delete the vc-bundle and employ a PVC to substitute for the vc-bundle
%FR_VCB-3-PROCESS_SWITCHING : Switching error -vcb [chars] -[chars]
Explanation An error occurred while switching packet(s) across vc-bundle
Recommended Action As a workaround, delete the vc-bundle and employ a PVC to substitute for the vc-bundle
%FR_VCB-5-UPDOWN : FR VC-Bundle [chars] changed state to [chars]
Explanation The state of a frame-relay vc-bundle changed to up/down
Recommended Action Notification message only. No action required
FW
%FW-2-BLOCK_HOST : [chars]Blocking new TCP connections to host [IP_address] for [dec] minute[chars] (half-open count [dec] exceeded).
Explanation This message indicates that any subsequent new TCP connection attempts to the specified host will be denied because the max-incomplete host threshold of half-open TCP connections is exceeded, and the blocking option is configured to block the subsequent new connections. The blocking will be removed when the configured block-time expires.
Recommended Action This message is for informational purposes only, but may indicate that a SYN flood attack was attempted.
%FW-3-FTP_NON_MATCHING_IP_ADDR : [chars]Non-matching address [IP_address] used in [chars] --FTP client [IP_address] FTP server [IP_address]
Explanation An FTP client attempted to use a PORT command or the FTP server attempted to use the response to a PASV command to trick the firewall into opening access to a third-party host that is different from the two hosts engaged in the FTP connection. This message indicates that a suspicious violation was detected while attempting to modify the security policy in the firewall. The command is rejected and the connection is reset by the firewall.
Recommended Action This message is for informational purposes only, but may indicate that an attempt was made to grant or open access to unauthorized hosts.
%FW-3-FTP_PRIV_PORT : [chars]Privileged port [dec] used in [chars] --FTP client [IP_address] FTP server [IP_address]
Explanation An FTP client attempted to use a PORT command or the FTP server attempted to use the response to a PASV command to trick the firewall into opening access to a privileged port. This message indicates that a suspicious violation was detected from the FTP client/server attempting to modify the security policy in the firewall. The command is rejected and the connection is reset by the firewall.
Recommended Action This message is for informational purposes only, but may indicate that an attempt was made to gain access to privileged ports.
%FW-3-FTP_SESSION_NOT_AUTHENTICATED : [chars]Command issued before the session is authenticated --FTP client [IP_address] FTP server [IP_address]
Explanation An FTP client attempted to use the PORT command or an FTP server attempted to use the response to a PASV command to open a data channel in the firewall prior to the client's successful authentication with the server. This is a suspicious attempt by the client/server to trick the firewall into opening a hole so that outside attackers can take advantage of the firewall opening. This message indicates that a suspicious violation was detected, and the PORT or PASV command/response is rejected by the firewall. The data channel in the firewall will not be opened until the authentication is done successfully.
Recommended Action This message is for informational purposes only, but may indicate that an illegal attempt was made to modify the firewall security policy.
%FW-3-HTTP_JAVA_BLOCK : [chars]JAVA applet is blocked from ([IP_address]:[dec]) to ([IP_address]:[dec]).
Explanation A Java applet was seen in the HTTP channel, and the firewall configuration indicates that the applet from this Web site should be prohibited. The message indicates that the applet is being downloaded from one of the prohibited sites and its entrance to the protected network is not allowed. The connection is reset and the transmission of the detected applet is aborted immediately.
Recommended Action This message is for informational purposes only, but may indicate a security problem.
%FW-3-INTERNAL_ERROR : IP Firewall internal failure --[chars]
Explanation This message indicates the misc errors in the IP FW subsystem
Recommended Action This message indicates the misc errors in the IP FW subsystem
%FW-3-NOTFOUND : [chars]Session context for ([IP_address]:[dec]) => ([IP_address]:[dec]) not found.
Explanation The CBAC code was searching its database for information for a particular inspection session, but this information was not found.
Recommended Action If this message recurs, copy it down exactly as it appears and contact your technical support representative for assistance.
%FW-3-RESPONDER_WND_SCALE_INI_NO_SCALE : Dropping packet -Invalid Window Scale option for session [IP_address]:[dec] to [IP_address]:[dec] (Initiator scale [int] Responder scale [int])
Explanation Firewall detected the packet from Responder to Initiator has windows scaling option but did not have the scaling option in the SYN packet from Initiator to responder. This is an error according to RFC 1323
Recommended Action Turn on window scaling option on both Initiator and Responder,or Turn off window scaling on the Responder
%FW-3-SMTP_INVALID_COMMAND : [chars]Invalid SMTP command ([chars])(total [dec] chars) from initiator ([IP_address]:[dec])
Explanation The CBAC code detected an invalid SMTP command in the inspected SMTP connection. This message indicates that a suspicious violation was detetected that may be an attack to the mail server system. The command is rejected and the connection is reset by the firewall immediately.
Recommended Action This message is for informational purposes only, but may indicate a security problem.
%FW-3-SMTP_UNSUPPORTED_PARAMETER : [chars]Unsupported SMTP parameter ([chars]) from initiator ([IP_address]:[dec])
Explanation The CBAC code detected an invalid/unsupported parameter in an SMTP command. The parameter ''data size'' means that the initiator is trying to send a huge data which is more than the default or configured firewall threshold (max-data). The parameter ''@ or # to ETRN'' means that the initiator is trying to send an invalid ETRN command.
Recommended Action This message is for informational purposes only, but may indicate a security problem.
%FW-3-TIMER_WHEEL_INIT_FAILED : Timer Wheel initialization failed
Explanation This message indicates that Timer Wheel initialization is failed in the FW subsystem
Recommended Action This message indicates a series problem with IOS Firewall. On seeing this error message, copy the message exactly as it appears, and report it to your technical support representative.
%FW-4-ALERT_OFF : [chars][chars], count ([dec]/[dec]) current 1-min rate: [dec]
Explanation Either the number of half-open connections or the new connection initiation rate has gone below the max-incomplete low threshold. This message indicates that the rate of incoming new connections has slowed down and is issued only when the max-incomplete low threshold is crossed.
Recommended Action This message is for informational purposed only, but may indicate that an attack has stopped.
%FW-4-ALERT_ON : [chars][chars], count ([dec]/[dec]) current 1-min rate: [dec]
Explanation Either the max-incomplete high threshold of half-open connections or the new connection initiation rate has been exceeded. This error message indicates that an unusually high rate of new connections is coming through the firewall, and a DOS attack may be in progress. This message is issued only when the max-incomplete high threshold is crossed.
Recommended Action This message is for informational purposed only, but may indicate a security problem.
%FW-4-HOST_TCP_ALERT_ON : [chars]Max tcp half-open connections ([dec]) exceeded for host [IP_address].
Explanation The max-incomplete host limit of half-open TCP connections has been exceeded. This message indicates that a high number of half-open connections is coming to the protected server, and may indicate that a SYN flood attack is in progress and is targeted to the specified server host.
Recommended Action This message is for informational purposes only, but may indicate that a SYN flood attack was attempted. If this alert is issued frequently and identified to be mostly false alarms, then the max-incomplete host threshold value is probably set too low, and there is a lot of legitimate traffic coming in to that server. In this case, the max-incomplete host parameter should be set to a higher number to avoid false alarms.
%FW-4-SESSION_THRESHOLD_EXCEEDED : [chars]Number of sessions for the firewall rule '[chars]' applied on interface '[chars]' exceeds the configured threshold [dec]
Explanation This message indicates that the number of established CBAC sessions have crossed the configured threshold.
Recommended Action This message is for informational purpose only, but may indicate a security problem. This might also mean that the session threshold is set to a low value, in which case the threshold value could be increased through CLI command
%FW-4-SKINNY_INSPECTION_DISABLED : Skinny Inspection Disabled; Error = [chars]
Explanation Skinny inspection is disabled due to internal errors and hence firewall will not inspect any Skinny protocol traffic. This will be caused when firewall does not have enough memory to allocate initial skinny data-structures.
Recommended Action Verify the memory usage to see if any process has used large amounts of memory and see if any corrective action can be taken for it. Otherwise, upgrade the memory. In any case, the firewall/router needs to be restarted to enable Skinny inspection.
%FW-4-TCP_MAJORDOMO_EXEC_BUG : [chars]Majordomo Execute Attack -from [IP_address] to [IP_address]
Explanation A bug in the Majordomo program will allow remote users to execute arbitrary commands at the privilege level of the server.
Recommended Action For security reasons users should not be allowed to execute programs via e-mail servers. This is a very serious indication that your network may be under attack and the source should be shunned immediately.
%FW-4-TCP_SENDMAIL_BAD_FROM_SIG : [chars]Sendmail Invalid Sender -from [IP_address] to [IP_address]
Explanation Triggers on any mail message with a ''pipe'' (|) symbol in the ''From:'' field.
Recommended Action For security reasons users should not be allowed to execute programs via e-mail servers. This is a very serious indication that your network may be under attack and the source should be shunned immediately.
%FW-4-TCP_SENDMAIL_BAD_TO_SIG : [chars]Sendmail Invalid Recipient -from [IP_address] to [IP_address]
Explanation Triggers on any mail message with a ' 'pipe'' (|) symbol in the recipient field.
Recommended Action For security reasons users should not be allowed to execute programs via e-mail servers. This is a very serious indication that your network may be under attack and the source should be shunned immediately.
%FW-4-TCP_SENDMAIL_DECODE : [chars]Sendmail Decode Alias -from [IP_address] to [IP_address]
Explanation Triggers on any mail message with '': decode@'' in the header. The decode alias is used to uudecode files and is primarily implemented as a convenience for system administration.
Recommended Action For security reasons users should not be allowed to execute programs via e-mail servers. This is a very serious indication that your network may be under attack and the source should be shunned immediately.
%FW-4-TCP_SENDMAIL_INVALID_COMMAND : [chars]Invalid SMTP command -[IP_address] to [IP_address]
Explanation Triggers on an invalid SMTP command in the SMTP connection. This message indicates that a suspicious violation was detetected that may be an attack to the mail server system.
Recommended Action This is unusual traffic and may warrantinvestigation.
%FW-4-TCP_SENDMAIL_OLD_SIG : [chars]Archaic Sendmail Attacks -from [IP_address] to [IP_address]
Explanation Triggers when ''wiz'' or ''debug'' commands are sent to the SMTP port.
Recommended Action For security reasons users should not be allowed to execute programs via e-mail servers. This is a very serious indication that your network may be under attack and the source should be shunned immediately.
%FW-4-UNBLOCK_HOST : [chars]New TCP connections to host [IP_address] no longer blocked
Explanation New TCP connection attempts to the specified host are no longer blocked. This message indicates that the blocking of new TCP attempts to the specified host has been lifted.
Recommended Action This message is for informational purposed only, but may indicate a SYN flood attack was attempted to the host.
%FW-5-EMAIL_DROP_FRAGMENT : [chars]Dropping [chars] command fragment from initiator ([IP_address]:[dec])
Explanation The CBAC code detected a pipelined POP3/IMAP command fragment, in the inspected POP3 connection. This message indicates that a suspicious violation was detetected that may be an attack to the mail server system. The fragment is dropped by the firewall immediately.
Recommended Action This message is for informational purposes only, but may indicate a security problem.
%FW-5-IMAP_INVALID_COMMAND : [chars]Invalid IMAP command from initiator ([IP_address]:[dec]): [chars]
Explanation The CBAC code detected an invalid IMAP command in the inspected IMAP connection. This message indicates that a suspicious violation was detetected that may be an attack to the mail server system. The command is rejected and the connection is reset by the firewall immediately.
Recommended Action This message is for informational purposes only, but may indicate a security problem.
%FW-5-IMAP_NON_SECURE_LOGIN : [chars]LOGON IMAP command from initiator ([IP_address]:[dec]): [chars]
Explanation The CBAC code detected a cleartext logon attempt in the inspected IMAP connection while secure-login is configured. The command is rejected and the connection is reset by the firewall immediately.
Recommended Action This message is for informational purposes only, but may indicate a security problem.
%FW-5-POP3_INVALID_COMMAND : [chars]Invalid POP3 command from initiator ([IP_address]:[dec]): [chars]
Explanation The CBAC code detected an invalid POP3 command in the inspected POP3 connection. This message indicates that a suspicious violation was detetected that may be an attack to the mail server system. The command is rejected and the connection is reset by the firewall immediately.
Recommended Action This message is for informational purposes only, but may indicate a security problem.
%FW-5-POP3_NON_SECURE_LOGIN : [chars]LOGON POP3 command from initiator ([IP_address]:[dec]): [chars]
Explanation The CBAC code detected a cleartext logon attempt in the inspected POP3 connection while secure-login is configured. The command is rejected and the connection is reset by the firewall immediately.
Recommended Action This message is for informational purposes only, but may indicate a security problem.
%FW-6-DROP_PKT : Dropping [chars] pkt [IP_address]:[int] => [IP_address]:[int]
Explanation Packet dropped by firewall inspection.
Recommended Action This message is for informational purposes only. It may be used to verify that packets were dropped by the firewall.
%FW-6-INIT : Firewall inspection startup completed; beginning operation.
Explanation Firewall inspection is configured on at least one interface in the startup config.
Recommended Action This message is for informational purposes only. It may be used to verify whether firewall inspection is on at startup.
%FW-6-PRE_ALLOCATED_MEDIA_CHANNEL : [chars]Pre-Allocated [chars] channel from [IP_address][[dec]:[dec]] to [IP_address][[dec]:[dec]]
Explanation CBAC inspection has pre-allocated data-structures and created ACEs to allow the data/media traffic to flow through the Firewall.
Recommended Action This message is for informational purposes only. It may be used to verify whether data/media sessions are being created.
%FW-6-SESS_AUDIT_TRAIL : [chars]Stop [chars] session: initiator ([IP_address]:[dec]) sent [int] bytes --responder ([IP_address]:[dec]) sent [int] bytes
Explanation This message documents the per-session transaction log of network activities. The message is issued at the end of each inspected session and it records the source/destination addresses and ports, as well as the number of bytes transmitted by the client and server.
Recommended Action This message is for informational purposed only, and can be used to collect the basic accounting for the inspected sessions.
%FW-6-SESS_AUDIT_TRAIL_START : [chars]Start [chars] session: initiator ([IP_address]:[dec]) --responder ([IP_address]:[dec])
Explanation This message documents the opening of an inspection session. The message is issued at the start of each inspected session and it records the source/destination addresses and ports.
Recommended Action This message is for informational purposed only, and can be used to collect the basic accounting for inspected sessions.
FWALL_PROXY
%FWALL_PROXY-3-PROXY_DEBUG_REG_FAILED : [dec]
Explanation FW Conditional Debugging registration failed.
Recommended Action LOG_STD_ACTION
%FWALL_PROXY-3-PROXY_FWALL_INIT_FAILED : [dec]
Explanation Firewall initialization failed.
Recommended Action LOG_STD_ACTION
%FWALL_PROXY-3-PROXY_HA_MEM_EXTEND_FAILED :
Explanation Increasing of ha retry pool failed.
Recommended Action LOG_STD_ACTION
%FWALL_PROXY-3-PROXY_HA_MEM_INIT_FAILED :
Explanation Initialization of ha retry pool failed.
Recommended Action LOG_STD_ACTION
%FWALL_PROXY-3-PROXY_HOSTDB_MEM_EXTEND_FAILED :
Explanation Increasing of host database pool failed.
Recommended Action LOG_STD_ACTION
%FWALL_PROXY-3-PROXY_HOSTDB_MEM_INIT_FAILED :
Explanation Initialization of host database pool failed.
Recommended Action LOG_STD_ACTION
%FWALL_PROXY-3-PROXY_HSL_ADD_DEST_FAILED :
Explanation HSL add destination failed.
Recommended Action LOG_STD_ACTION
%FWALL_PROXY-3-PROXY_HSL_BIND_FAILED :
Explanation HSL bind failed.
Recommended Action LOG_STD_ACTION
%FWALL_PROXY-3-PROXY_HSL_BIND_TEMPLATE_FAILED : [dec]
Explanation HSL bind tempalte failed at given index.
Recommended Action LOG_STD_ACTION
%FWALL_PROXY-3-PROXY_HSL_CREATE_FAILED :
Explanation HSL creation failed.
Recommended Action LOG_STD_ACTION
%FWALL_PROXY-3-PROXY_HSL_ENABLE_FAILED :
Explanation HSL enable failed.
Recommended Action LOG_STD_ACTION
%FWALL_PROXY-3-PROXY_HSL_MODIFY_DEST_FAILED :
Explanation HSL modify destination failed.
Recommended Action LOG_STD_ACTION
%FWALL_PROXY-3-PROXY_HSL_MODIFY_FAILED :
Explanation HSL modification failed.
Recommended Action LOG_STD_ACTION
%FWALL_PROXY-3-PROXY_ICMP_ERROR_MEM_EXTEND_FAILED :
Explanation Increasing of ICMP Error pool failed.
Recommended Action LOG_STD_ACTION
%FWALL_PROXY-3-PROXY_ICMP_ERROR_MEM_INIT_FAILED :
Explanation Initialization of ICMP Error control block pool failed.
Recommended Action LOG_STD_ACTION
%FWALL_PROXY-3-PROXY_IPC_ALLOC_FAILED : [int]
Explanation IPC allocation failed.
Recommended Action LOG_STD_ACTION
%FWALL_PROXY-3-PROXY_IPC_ERM_CONF_CHANGE_FAILED : [dec]
Explanation FW IPC send failed to reply for event rate monitoring configuration change.
Recommended Action LOG_STD_ACTION
%FWALL_PROXY-3-PROXY_IPC_FAILED : [chars] [dec]
Explanation IPC message allocation for firewall failed.
Recommended Action LOG_STD_ACTION
%FWALL_PROXY-3-PROXY_IPC_INIT_FAILED : [dec]
Explanation IPC handler initialization failed.
Recommended Action LOG_STD_ACTION
%FWALL_PROXY-3-PROXY_IPC_SEND_CLEAR_FAILED : [dec]
Explanation IPC send failed to reply for firewall session clear.
Recommended Action LOG_STD_ACTION
%FWALL_PROXY-3-PROXY_IPC_SEND_DEBUG_FAILED : [dec]
Explanation IPC send failed to reply for firewall session debug.
Recommended Action LOG_STD_ACTION
%FWALL_PROXY-3-PROXY_IPC_SEND_FAILED : [int]:[chars]
Explanation IPC send failed.
Recommended Action LOG_STD_ACTION
%FWALL_PROXY-3-PROXY_IPC_SEND_INIT_FAILED : [chars] [dec]
Explanation IPC failed to reply for firewall initialization status.
Recommended Action LOG_STD_ACTION
%FWALL_PROXY-3-PROXY_IPC_SEND_SCB_QUERY_FAILED : [dec]
Explanation IPC send failed to reply for firewall scb query.
Recommended Action LOG_STD_ACTION
%FWALL_PROXY-3-PROXY_IPC_SEND_SESSION_FAILED : [dec]
Explanation IPC send failed to reply for firewall session query.
Recommended Action LOG_STD_ACTION
%FWALL_PROXY-3-PROXY_IPC_SEND_STATS_FAILED : [dec]
Explanation IPC send failed to reply for firewall status.
Recommended Action LOG_STD_ACTION
%FWALL_PROXY-3-PROXY_SCB_MEM_EXTEND_FAILED :
Explanation Increasing of session control block pool failed.
Recommended Action LOG_STD_ACTION
%FWALL_PROXY-3-PROXY_SCB_MEM_INIT_FAILED :
Explanation Initialization of session control block pool failed.
Recommended Action LOG_STD_ACTION
%FWALL_PROXY-3-PROXY_TBL_INIT_FAILED : [chars]
Explanation Failed to initialize table.
Recommended Action LOG_STD_ACTION
%FWALL_PROXY-3-PROXY_TEARDOWN_MEM_EXTEND_FAILED :
Explanation Increasing of teardown pool failed.
Recommended Action LOG_STD_ACTION
%FWALL_PROXY-3-PROXY_TEARDOWN_MEM_INIT_FAILED :
Explanation Initialization of teardown pool failed.
Recommended Action LOG_STD_ACTION
%FWALL_PROXY-4-PROXY_HSL_ALREADY_INIT :
Explanation HSL logger already initialized
Recommended Action LOG_STD_ACTION
%FWALL_PROXY-4-PROXY_HSL_NOT_INIT : [int]
Explanation HSL logger not initialized
Recommended Action LOG_STD_ACTION
%FWALL_PROXY-4-PROXY_IPC_INVALID_MSG : [hex]
Explanation Invalid IPC message subtype.
Recommended Action LOG_STD_ACTION
%FWALL_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
%FWALL_PROXY-4-PROXY_IPC_UNINIT_POOL_FAILED : [chars]: [dec]
Explanation Could not destroy chunk pool
Recommended Action LOG_STD_ACTION
%FWALL_PROXY-4-PROXY_UNINIT_SESSIONS : in use [int] [int]
Explanation Not all sessions freed
Recommended Action LOG_STD_ACTION
G
GBIC_SECURITY
%GBIC_SECURITY-4-EEPROM_CRC_ERR : EEPROM checksum error for GBIC in [chars]
Explanation The GBIC in the port specified in the error message has invalid EEPROM data.
Recommended Action Remove the GBIC from the specified port.
%GBIC_SECURITY-4-EEPROM_READ_ERR : Error in reading GBIC serial ID in [chars]
Explanation Error when reading GBIC type from EEPROM
Recommended Action Please remove GBIC from this Port
%GBIC_SECURITY-4-EEPROM_SECURITY_ERR : GBIC in [chars] failed security check
Explanation The GBIC in the port specified in the error message has invalid EEPROM data.
Recommended Action Remove the GBIC from the specified port.
%GBIC_SECURITY-4-GBIC_INTERR : Internal error occurred in setup for GBIC interface [chars]
Explanation The system could not allocate resources, or had some other problem, in the setup for the specified GBIC interface.
Recommended Action Reload the system. If the problem persists, contact TAC.
GBIC_SECURITY_CRYPT
%GBIC_SECURITY_CRYPT-4-ID_MISMATCH : Identification check failed for GBIC in port [dec]
Explanation The GBIC was identified as a Cisco GBIC, but the system was unable to verify its identity
Recommended Action Check to see if the Cisco IOS software running on the system supports the GBIC. If the GBIC is newer, a system software upgrade might be required. Otherwise, verify that the GBIC was obatined from Cisco or from a supported vendor.
%GBIC_SECURITY_CRYPT-4-UNRECOGNIZED_VENDOR : GBIC in port [dec] manufactured by an unrecognized vendor
Explanation The GBIC was identified as a Cisco GBIC, but the system was unable to match its manufacturer with one on the known list of Cisco GBIC vendors
Recommended Action Check to see if the Cisco IOS software running on the system supports the GBIC. If the GBIC is newer, a system software upgrade might be required.
%GBIC_SECURITY_CRYPT-4-VN_DATA_CRC_ERROR : GBIC in port [dec] has bad crc
Explanation The GBIC was identified as a Cisco GBIC, but it does not have valid CRC in the EEPROM data.
Recommended Action Check to see if the Cisco IOS software running on the system supports the GBIC. If the GBIC is newer, a system software upgrade might be required. Even if the GBIC is unrecognized by the system, the GBIC may still operate properly, but might have limited functionality.
GBIC_SECURITY_UNIQUE
%GBIC_SECURITY_UNIQUE-3-DUPLICATE_GBIC : GBIC interface [dec]/[dec] is a duplicate of GBIC interface [dec]/[dec]
Explanation The GBIC was identified as a Cisco GBIC, but its vendor ID and serial number match that of another interface on the system.
Recommended Action Cisco GBICs are assigned unique serial numbers. Verify that the GBIC was obtained from Cisco or a supported vendor
%GBIC_SECURITY_UNIQUE-4-DUPLICATE_SN : GBIC interface [dec]/[dec] has the same serial number as another GBIC interface
Explanation The GBIC was identified as a Cisco GBIC, but its serial number matches that of another interface on the system.
Recommended Action Cisco GBICs are assigned unique serial numbers. Verify that the GBIC was obtained from Cisco or a supported vendor.
GDOI
%GDOI-1-GDOI_ACE_DENY : A Group Member ACL policy containing deny was attempted. This is not supported.
Explanation A Group Member ACL policy containing deny was attempted. This is not supported.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%GDOI-1-GDOI_ACL_NUM : The ACL has too many entries. GDOI will honor only the first 100 ACL entries specified.
Explanation The ACL has too many entries. GDOI will honor only the first 100 ACL entries specified.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%GDOI-1-KS_NO_RSA_KEYS : RSA Key -[chars] : Not found, Required for group [chars]
Explanation Rsa Keys were not found in Key Server and they are required for signing and verifying rekey messages
Recommended Action Contact the Key Server's administrator and ask him to do create the RSA Key pair
%GDOI-1-UNAUTHORIZED_IDENTITY : Group [chars] received registration from unauthorized identity: [chars]
Explanation The registration request was dropped because the requesting device was not authorized to join the group.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%GDOI-1-UNAUTHORIZED_IPADDR : Group [chars] received registration from unauthorized ip address: [chars]
Explanation The registration request was dropped because the requesting device was not authorized to join the group.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%GDOI-1-UNREGISTERED_INTERFACE : Group [chars] received registration from unregistered interface.
Explanation Receiving registration from unregistered interface. Stop processing it.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%GDOI-2-COOP_MINOR_VERSION_MISMATCH : COOP-KS Minor version mistmatch in group [chars]. My COOP version is [dec].[dec].[dec], peer [chars] has version [dec].[dec].[dec]. Upgrade [chars] [chars] to COOP version [dec].[dec].[dec] to prevent COOP outage.
Explanation Coop KS has different minor version.
Recommended Action show crypto gdoi ks coop
%GDOI-3-COOP_ANN_SEQ_FAILURE : COOP Ann msg seq check failed for group [chars], ann seq# [int], sess seq# [int]
Explanation COOP Ann msg seq check failed
Recommended Action Contact Administrator
%GDOI-3-COOP_CONFIG_MISMATCH : WARNING: Group [chars], [chars] configuration between Primary KS and Secondary KS are mismatched
Explanation The configuration between Primary KS and Secondary KS are mismatched
Recommended Action Contact the Key Sever's administrator
%GDOI-3-COOP_KS_CANNOT_FIND_PROFILE : Coop KS in group [chars] has a configured IKEv2 profile '[chars]' that doesn't exist. The COOP will not come up until this error is fixed.
Explanation The KS COOP coniguration redunadancy ikve2-profile specifies a profile that doesn't exist. The COOP will not come up.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%GDOI-3-COOP_KS_SEND_WINDOW_LIMIT_REACHED : The COOP KS has reached its window limit for the peer addresses local [chars] remote [chars]. This is due to connectivity issues between the key servers in question.
Explanation The COOP KS running over IKEv2 has a limit to the number of pending messages that can be sent. This limit has been reached which is an indication that there is a connectivity issue between the key servers
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%GDOI-3-COOP_KSSID_OVERLAP : Overlapping KS Sender Identifier(s) (KSSID) {[chars]} with COOP-KS peer [chars] in group [chars] blocking GM registration (MISCONFIG)
Explanation Another COOP-KS peer in the group has been configured with a KSSID value that is the same as one configured on this KS. GM registration is blocked as a result until the overlap is fixed.
Recommended Action Check the configured KSSID(s) for all COOP-KS peers by issuing 'show crypto gdoi ks coop ident detail' on the primary KS
%GDOI-3-COOP_KS_TOO_MANY_GROUPS_SHARE_IKE_SA : The COOP KS has too many groups sharing the same IKE SA for the peer addresses local [chars] remote [chars]. Connectivity could be compromised. Please reduce to [dec].
Explanation There is a limit to the number of COOP KS groups that can share the. same IKE SA. This can lead to intermittent connectivity for the COOP KS in congested networks
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%GDOI-3-COOP_KS_UNREACH : Cooperative KS [chars] Unreachable in group [chars]. IKE SA Status = [chars]
Explanation The reachability between the configugred cooperative key servers is lost. Some might consider this a hostile event.
Recommended Action Contach the Administrator(s) of the configured key servers.
%GDOI-3-COOP_LIMIT_REACHED : Peer [chars] has reached COOP limit of maximum number of gms. COOP GM database sync fails. Upgrade to COOP version [dec].[dec].[dec] and above
Explanation COOP-KS has a non-compatible peer.
Recommended Action Check COOP version compatibility on peer KS
%GDOI-3-COOP_MAJOR_VERSION_MISMATCH : COOP-KS Major Version mismatch in group [chars]. My version is [dec].[dec].[dec], peer [chars] has version [dec].[dec].[dec]
Explanation COOP-KS has a non-compatible major version.
Recommended Action Check COOP version compatibility on KS
%GDOI-3-COOP_PACKET_DROPPED : Announcement message dropped due to packet size [dec] bytes.
Explanation Hard limit set on the driver buffer size prevents sending packets of this size or bigger
Recommended Action Informational message
%GDOI-3-GDOI_ACL_RANGE : The ACL [chars] contains port range which is NOT supported. WARNING: No TEK policy will be created.
Explanation GDOI does not support port range in the ACL policy.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%GDOI-3-GDOI_REKEY_FAILURE : Processing of REKEY payloads failed on GM [chars] in the group [chars], with peer at [chars]
Explanation During GDOI rekey the payload parsing failed on this GM from the Key Server.
Recommended Action Contact the Group member's administrator.
%GDOI-3-GDOI_REKEY_SEQ_FAILURE : Failed to process rekey seq # [int] in seq payload for group [chars], last seq # [int]
Explanation During GDOI rekey the seq payload parsing failed on this GM from the Key Server.
Recommended Action Contact the Group member's administrator.
%GDOI-3-GM_ACL_PERMIT : GM doesn't support permit configured under local access-list. Traffic from [chars] to [chars] will be dropped.
Explanation GM can only support ACL for deny. Any traffic matching the permit entry will be dropped.
Recommended Action Remove the permit entry from the ACL used by GDOI crypto map
%GDOI-3-GM_FAILED_TO_INITIALISE : GDOI GM Process has failed to initialise
Explanation GDOI Group Member process has failed to initialise on this Network Element
Recommended Action None
%GDOI-3-GM_INCOMPLETE_CFG : Registration: incomplete config for group [chars]
Explanation Registration can not be completed since the GDOI group configuration may be missing the group id, server id, or both
Recommended Action Contact the Group member's administrator.
%GDOI-3-GM_IPD3P_AND_CMD_CANT_COEXIST : GETVPN group-member does not support coexistance of IPD3P and Cisco-metadata features
Explanation GETVPN group-member does not support the enabling of IPD3P and Cisco-metadata features (e.g TBAR-PST, SGT) at the time
Recommended Action Contact the Administrator(s) to correct the key server policy.
%GDOI-3-GM_IPD3P_NO_IPV6_SUPPORT : GETVPN group-member does not support IP-D3P for IPv6.
Explanation GETVPN group-member does not support IP-D3P for IPv6.
Recommended Action Contact the Administrator(s) to correct the key server policy.
%GDOI-3-GM_IPD3P_NO_TRANSPORT_SUPPORT : GETVPN group-member does not support IPD3P transport mode
Explanation GETVPN group-member does not support IPD3P transport mode
Recommended Action Contact the Administrator(s) to correct the key server policy.
%GDOI-3-GM_MAJOR_VERSION_MISMATCH : GM [IP_address] registration rejected due to major version mismatch. GM must be using major version [dec] in order to be compatible with this KS
Explanation GM has a non-compatible major version.
Recommended Action Check GDOI version compatibility on KS and GMs
%GDOI-3-GM_NO_CRYPTO_ENGINE : No crypto engine is found due to lack of resource or unsupported feature requested
Explanation Failed to select a suitable crypto engine because requested packet path not available, or requested feature not supported
Recommended Action Check policy configured on KS
%GDOI-3-GM_NO_IPSEC_FLOWS : IPSec FLOW limit possibly reached
Explanation Hardware Limitation for IPSec Flow limit Reached. Cannot create any more IPSec SAs
Recommended Action Contact the Group member's administrator.
%GDOI-3-IPSEC_INITIATE_GM_REGISTER_IGNORE : IPSEC triggering registration for group [chars] too frequently. Ignore the request as registartion has already been scheduled to occur in [dec] msec.
Explanation GM detects IPSEC triggering registration for the group too frequently. GDOI will ignore the request as registration has already been scheduled.
Recommended Action Contact the Group member's administrator.
%GDOI-3-IPSEC_INITIATE_GM_REGISTER_POSTPONE : IPSEC triggering registration for group [chars] too frequently. Postpone the registration to occur in [dec] msec.
Explanation GM detects IPSEC triggering registration for the group too frequently. GDOI will rate-limit and postpone the registration.
Recommended Action Contact the Group member's administrator.
%GDOI-3-KS_BAD_ID : Registration: [chars] config mismatch between KS and the GM [IP_address], in the group [chars].
Explanation During GDOI registration protocol, a configuration mismatch between local key server and group member.
Recommended Action Contact the Group member's administrator.
%GDOI-3-KS_BLACKHOLE_ACK : KS blackholing GM [IP_address] in group [chars].
Explanation Key server has reached a condition of blackholing messages from GM Some might consider this a hostile event.
Recommended Action None
%GDOI-3-KS_GM_REVOKED : Re-Key: GM [IP_address] revoked by KS in the group [chars].
Explanation During Re-key protocol, an unauthorized member tried to join a group. Some might consider this a hostile event.
Recommended Action Contact the Key Server's administrator.
%GDOI-3-KS_MAJOR_VERSION_MISMATCH : COOP-KS Major Version mismatch in group [chars]. My version is [dec].[dec].[dec], peer [chars] has version [dec].[dec].[dec]
Explanation COOP-KS has a non-compatible major version.
Recommended Action Check GDOI version compatibility on KS
%GDOI-3-KS_NO_SID_AVAILABLE : GMs for group [chars] need SIDs but this KS has no KS SIDs configured or no more SIDs available.
Explanation This KS has a counter-mode transform configured requiring SIDs and either has no KSSIDs configured or has run out of SIDs. Registering GMs will not be able to register successfully until more KSSIDs are configured on this KS.
Recommended Action Check the configured KSSID(s) for this KS by issuing 'show crypto gdoi ks ident detail' and consider configuring more KSSIDs using the 'identifier' sub-mode under 'server local'.
%GDOI-3-KS_REKEY_AUTH_KEY_LENGTH_INSUFFICIENT : Rejected [chars] change: using sig-hash algorithm [chars] requires an authentication key length of at least [int] bits ([int] blocks in bytes) -[chars] [chars] key [chars] is only [int] blocks in bytes
Explanation Using a sig-hash algorithm for rekeys requires that the RSA key modulus length for the rekey authentication be at least the length of the hash generated by the sig-hash algorithm plus some padding bytes. If the RSA key modulus length is not large enough, the Key Server administrator needs to generate a new RSA key pair wit a sufficient length.
Recommended Action Contact the Key Server's administrator to re-generate the RSA key pair with at least the modulus length given in the syslog.
%GDOI-3-KS_UNAUTHORIZED : Registration: Unauthorized [IP_address] tried to join the group [chars].
Explanation During GDOI registration protocol, an unauthorized member tried to join a group Some might consider this a hostile event.
Recommended Action Contact the Key Server's administrator.
%GDOI-3-P2P_KGS_INFRA_ERROR : PIP session with [chars] failed because of KGS Infra failure. Reason = [chars]
Explanation A Group Member has encountered a KGS Infra failure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%GDOI-3-P2P_PEER_MIGRATE_FAILED : Failed to install P2P rekey SA with peer [chars] in group [chars]
Explanation Installation of P2P Rekey SA with an existing peer has failed
Recommended Action Check the status of all peers using the command 'show crypto gdoi gm p2p peers' and wait for PIP initiation between the failed peers. Traffic distruption may occur.
%GDOI-3-PIP_PSEUDO_TIME_ERROR : An Anti-Replay check has failed for PIP in group [chars]: my_pseudotime = [chars], peer_pseudotime = [chars], replay_window = %lld (sec), src_addr = [chars], dst_addr = [chars]
Explanation A Group member has failed PIP anti replay check.
Recommended Action None
%GDOI-3-PSEUDO_TIME_LARGE : Pseudotime difference between KS ([dec] sec) and GM ([dec] sec) is larger than expected in group [chars]. Adjust to new PST
Explanation A Group member has received pseudotime which has large difference as compared to own pseudotime
Recommended Action None
%GDOI-3-PSEUDO_TIME_TOO_OLD : Rekey received in group [chars] is too old and fail PST check: my_pst is [dec] sec, peer_pst is [dec] sec, allowable_skew is [dec] sec
Explanation A Group member has received pseudotime which has large difference as compared to own pseudotime
Recommended Action None
%GDOI-3-SA_KEK_INSATALL_FAILED : Failed to install KEK SA
Explanation KEK SA instalation has failed
Recommended Action Informational message.
%GDOI-3-UNEXPECTED_SIGKEY : Unexpected Signature Key detected: freeing it
Explanation Unexpected Signature Key found: freeing the signature key
Recommended Action Informational message
%GDOI-3-UNSUPPORTED_TEK_PROTO : Unexpected TEK Protocol : [dec]
Explanation Unexpected TEK PROTOCOL
Recommended Action Informational message
%GDOI-4-COOP_KS_CHECKPT_MISMATCH : Coop KS [chars] in group [chars] received Checkpoint Mismatch message.
Explanation The KS COOP had received a checkpoint mismatch from a KS COOP peer
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%GDOI-4-COOP_KS_CKM_INCOMPATIBLE : Found incompatible COOP-KS that cannot support CKM in group [chars]. Please check 'show crypto gdoi feature ckm'and upgrade the incompatible KS immediately.
Explanation Found incompatible COOP-KS that cannot support CKM in the group. Network administrator should check 'show crypto gdoi feature ckm'and upgrade the incompatible KS immediately
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%GDOI-4-COOP_KS_RBLY_FAILED : Coop KS [chars] in group [chars] session Reassembly failed in TransID [int]
Explanation The KS COOP had an error reassmbling a packet from a peer KS
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%GDOI-4-COOP_KS_UNAUTH : Contact from unauthorized KS [chars] in group [chars] at local address [chars] (Possible MISCONFIG of peer/local address)
Explanation An authorized remote server tried to contact the local KS may be at different key server address in a group. Some might consider this a hostile event.
Recommended Action Informational message
%GDOI-4-GDOI_ANN_INCONSISTENT_TBAR : COOP_KS ANN received from [chars] in group [chars] has inconsistent TBAR setting inconsistent than mine
Explanation The KS has received an ANN msg from a secondary KS in which the timestamp is too old
Recommended Action None
%GDOI-4-GDOI_ANN_TIMESTAMP_LARGE : COOP_KS ANN received from KS [chars] in group [chars] has PST bigger than myself. Adjust to new PST: my_old_pst is [int] sec, peer_pst is [int] sec
Explanation The KS receive an ANN from a KS in which the timestamp is bigger than expected; also update my PST to peer's
Recommended Action None
%GDOI-4-GDOI_ANN_TIMESTAMP_LARGE_NO_UPDATE : COOP_KS ANN received from KS [chars] in group [chars] has PST bigger than myself: my_pst is [int] sec, peer_pst is [int] sec
Explanation The KS receive an ANN from a KS in which the timestamp is bigger than expected; No update of my PST
Recommended Action None
%GDOI-4-GDOI_ANN_TIMESTAMP_TOO_OLD : COOP_KS ANN from KS [chars] in group [chars] is too old and fail PST check: my_pst is [int] sec, peer_pst is [int] sec, allowable_skew is [dec] sec
Explanation The KS has received an ANN msg from a primary KS in which the timestamp is too old
Recommended Action None
%GDOI-4-GM_DELETE : GM [chars] deleted from group [chars].
Explanation A group member has been deleted in a group from Key Server
Recommended Action Informational message
%GDOI-4-GM_HASH_FAIL : Registration: Bad(No) hash in message sent by the KS [IP_address] to GM in the group [chars].
Explanation During GDOI registration protocol, a message sent by the Key server has bad or no hash .
Recommended Action Contact the Key Server's administrator.
%GDOI-4-GM_MINOR_VERSION_MISMATCH : GM [IP_address] Minor Version mismatch. Use 'show crypto gdoi ks members' to see GM versions
Explanation GM has different minor version.
Recommended Action show crypto gdoi ks members
%GDOI-4-GM_RECOVERY_REGISTRATION : GM recovery re-registration for group [chars] will start in a randomly chosen period of [dec] sec
Explanation GM recovery feature detects dataplane error and will re-register to KS to refresh keys and policy
Recommended Action Informational message.
%GDOI-4-GM_RECOVERY_REGISTRATION_POSTPONED : Detects data error in group [chars] but the previous recovery/rekey has occured within the last recovery-check interval. Postpone recovery registration to start in [dec] sec
Explanation GM recovery feature detects dataplane error and will re-register to KS to refresh keys and policy
Recommended Action Informational message.
%GDOI-4-GM_RECV_DELETE : GM received delete-msg from KS in group [chars]. TEKs lifetime are reduced and re-registration will start before SA expiry
Explanation A messages sent by the KS to delete the GM has been received.
Recommended Action Informational message.
%GDOI-4-GM_RECV_DELETE_IMMEDIATE : GM receive REMOVAL-NOW in group [chars] to cleanup downloaded policy now. Re-registration will start in a randomly chosen period of [dec] sec
Explanation A messages sent by the KS to delete the GM has been received.
Recommended Action Informational message.
%GDOI-4-GM_RECV_POLICY_REPLACE_NOW : GM received policy replace now rekey from KS in group [chars].
Explanation A messages sent by the KS to immediately replace SAs policies on the GM has been received.
Recommended Action Informational message.
%GDOI-4-GM_RECV_RE_AUTH : GM received Re-auth-msg from KS in group [chars]. re-registration will start before SA expiry
Explanation A message sent by the KS to have a GM re-auth has been received.
Recommended Action Informational message.
%GDOI-4-GM_REJECTING_SA_PAYLOAD : Registration: Policy in SA payload sent by KS [IP_address] rejected by GM in the group [chars] reason [chars].
Explanation During GDOI registration protocol, a proposal sent by the key server was refused by the local group member.
Recommended Action Contact the Key server's administrator.
%GDOI-4-GM_REKEY_NOT_RECD : GM did not receive rekey from KS [IP_address] in group [chars].
Explanation GM has not received a rekey message from a key server in a group Currently Unimplemented.
Recommended Action Informational message
%GDOI-4-GM_RE_REGISTER : The IPSec SA created for group [chars] may have expired/been cleared, or didn't go through. Re-register to KS.
Explanation The IPSec SA created for one group may have expired/been cleared, or didn't go through, need to re-register to KS.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%GDOI-4-GM_SA_TRACK_SET_EOT_ERROR : Group [chars] encountered error in setting EOT object ID [dec] to state [chars].
Explanation GM SA TRACK state change occur but fail to update EOT object ID accordingly
Recommended Action Informational message. Check to make sure the EOT object ID is configured properly
%GDOI-4-KS_GM_REJECTS_SA_PAYLOAD : Registration: GM [IP_address] rejected a policy in the SA proposal sent by KS, in the group [chars].
Explanation During GDOI registration protocol, a proposal sent by the key server was refused by the group member.
Recommended Action Contact the Group member's administrator.
%GDOI-4-KS_HASH_FAIL : Registration: Bad(No) Hash in Message sent by the GM [IP_address] to KS in the group [chars].
Explanation During GDOI registration protocol, a message sent by the Group member has bad or no hash .
Recommended Action Contact the Group member's administrator.
%GDOI-4-KS_MINOR_VERSION_MISMATCH : COOP-KS Minor Version mistmatch in group [chars]. My version is [dec].[dec].[dec], peer [chars] has version [dec].[dec].[dec]
Explanation Coop KS has different minor version.
Recommended Action show crypto gdoi ks coop
%GDOI-4-KS_UNSOL_ACK : KS received unsolicited ACK from GM [IP_address] in group [chars].
Explanation Key server has received an unsolicited ACK from a past GM or is under a DOS attack. Some might consider this a hostile event.
Recommended Action None
%GDOI-4-LKH_GM_DELETE : GM [IP_address] deleted from LKH in group [chars].
Explanation A Group member has been deleted in a group from LKH
Recommended Action None
%GDOI-4-NEWER_GM_VERSION_REGISTER : WARNING: GM [IP_address] registers to group [chars] with newer GDOI version than KS. Please check'show crypto gdoi ks members' and 'show crypto gdoi feature' to ensure all GMs can support the GETVPN features enabled.
Explanation A GM is registered with newer GDOI SW version; cannot determine its feature capability.
Recommended Action Check GMs can support all GETVPN features enabled in KS. Also check output of 'show crypto gdoi feature' and 'debug crypto gdoi ks infra detail' (note: high volume of debugs). msgdef_ddts_component(ipsec-getvpn)
%GDOI-4-REJECT_GM_CKM_REGISTER : Reject registration of GM [IP_address] in group [chars] as it has CKM enabled but this secondaryKS has not sync up all KGS params yet
Explanation Reject GM registration because this is a secondaryKS and it has not received KGS seed and rekey-epoch from primaryKS yet
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%GDOI-4-REJECT_GM_VERSION_REGISTER : Reject registration of GM [IP_address] (ver [hex]) in group [chars] as it cannot support these GETVPN features enabled: [chars]
Explanation Reject GM registration because it cannot support the GETVPN features enabled in the group.
Recommended Action Check GMs can support all GETVPN features enabled in KS. Also check output of 'show crypto gdoi feature' and 'debug crypto gdoi ks infra detail' (note: high volume of debugs). msgdef_ddts_component(ipsec-getvpn)
%GDOI-4-RSA_KEYS_MODIFIED : WARNING: GMs for group [chars] will re-register due to signature verification failure
Explanation Rekeys will be dropped by GM as signature verification would fail due to modification of RSA Keys
Recommended Action Informational message
%GDOI-4-TIMEBASED_REPLAY_FAILED : An anti replay check has failed in group [chars]: my_pseudotime = [chars], peer_pseudotime = [chars], replay_window = [dec] (sec), src_ip = [IP_address], dst_ip = [IP_address]
Explanation A Group member or Key server has failed an anti replay check.
Recommended Action None
%GDOI-4-TIMEBASED_REPLAY_FAILED_IPV6 : An anti replay check has failed in group [chars]: my_pseudotime = [chars], peer_pseudotime = [chars], replay_window = [dec] (sec), src_ip = [IPV6 address], dst_ip = [IPV6 address]
Explanation A Group member or Key server has failed an anti replay check.
Recommended Action None
%GDOI-4-UNKNOWN_GM_VERSION_REGISTER : WARNING: GM [IP_address] with unknown GDOI ver registered to group [chars] (e.g old-IOS or non-Cisco GM please check 'show crypto gdoi ks members' and 'show crypto gdoi feature' to ensure all your GMs can support the GETVPN features enabled.
Explanation A GM is registered with unknown GDOI SW version; cannot determine its feature capability.
Recommended Action Check GMs can support all GETVPN features enabled in KS. Also check output of 'show crypto gdoi feature' and 'debug crypto gdoi ks infra detail' (note: high volume of debugs). msgdef_ddts_component(ipsec-getvpn)
%GDOI-5-COOP_KS_ADD : [chars] added as COOP Key Server in group [chars].
Explanation A key server has been added to the list of cooperative key servers in a group
Recommended Action Informational message
%GDOI-5-COOP_KS_ADMN_USRP_PRI : Primary role Usurped by KS [chars] in group [chars].
Explanation A network adminstrator has made the local KS as primary, by means of a CLI command. Currently Unimplemented.
Recommended Action Informational message
%GDOI-5-COOP_KS_BLOCK_NEW_GM_REGISTER_ANN : This KS temporarily blocks GM with ip-addr [chars] from registering in group [chars] as it has not received an ANN with valid PST for prolonged period
Explanation No valid ANN message has been received in this secondary KS for a prolong period. Temporarily blocking new GM registrations until a valid ANN is received
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%GDOI-5-COOP_KS_BLOCK_NEW_GM_REGISTER_ELECTION : This KS temporarily blocks GM with ip-addr [chars] from registering in group [chars] as the KS election is underway
Explanation The KS is in the process of electing a primary. Temporarily blocking new GM registrations until the election is complete
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%GDOI-5-COOP_KS_BLOCK_NEW_GM_REGISTER_KSSID : This KS is blocking GM with ip-addr [chars] from registering in group [chars] as it has overlapping KS Sender Identifier(s) (KSSID) with another COOP-KS peer (MISCONFIG)
Explanation Another COOP-KS peer in the group has been configured with a KSSID value that is the same as one configured on this KS. GM registration is blocked as a result until the overlap is fixed.
Recommended Action Check the configured KSSID(s) for all COOP-KS peers by issuing 'show crypto gdoi ks coop ident detail' on the primary KS
%GDOI-5-COOP_KS_ELECTION : KS entering election mode in group [chars] (Previous Primary = [chars])
Explanation The local Key server has entered the election process in a group
Recommended Action Informational message
%GDOI-5-COOP_KS_REACH : Reachability restored with Cooperative KS [chars] in group [chars].
Explanation The reachability between the configugred cooperative key servers is restored.
Recommended Action Informational message
%GDOI-5-COOP_KS_REMOVE : [chars] removed as COOP Key Server in group [chars].
Explanation A key server has been removed from the list of cooperative key servers in a group
Recommended Action Informational message
%GDOI-5-COOP_KS_RESUME_NEW_GM_REGISTER : This KS will now resume new GM registration functionality in group [chars]
Explanation This KS will now resume new GM registration functionality
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%GDOI-5-COOP_KSSID_OVERLAP_RESOLVED : Resolved overlapping KS Sender Identifier(s) (KSSID) with COOP-KS peer allowing GM registrations once again
Explanation Another COOP-KS peer in the group had been configured with a KSSID value that was the same as one configured on this KS, but has been resolved so that GM registration is allowed again.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%GDOI-5-COOP_KS_TRANS_TO_PRI : KS [chars] in group [chars] transitioned to Primary (Previous Primary = [chars])
Explanation The local Key server transitioned to a primary role from being a secondary server in a group
Recommended Action Informational message
%GDOI-5-COOP_KS_VALID_ANN_TIMER_EXPIRED : This sec-KS has NOT received an ANN with valid PST for an extended period in group [chars]. It will block new GMs registration temporarily until a valid ANN is received
Explanation No valid ANN message has been received in this secondary KS for a prolong period. Temporarily blocking new GM registrations until a valid ANN is received
Recommended Action Informational message
%GDOI-5-ESON_POLICY_CHANGE_RESTART1 : ESON group [chars] policy has changed. Must use 'clear crypto gdoi ks members now' to restart the group
Explanation Reminder message that ESON configuration has changed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%GDOI-5-ESON_POLICY_CHANGE_RESTART2 : ESON group [chars] policy has changed. Must use 'crypto gdoi ks replace now' to restart the group
Explanation Reminder message that ESON configuration has changed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%GDOI-5-GM_ACL_MERGE : ACL betweem KS and GM in group [chars] merged.
Explanation The ACL differences between GM and KS are resolved and a merge took place
Recommended Action None
%GDOI-5-GM_CLEAR_REGISTER : Config: GM cleared gdoi configuration for the group [chars].
Explanation clear crypto gdoi command has been executed by the local GM
Recommended Action Informational message.
%GDOI-5-GM_CM_ATTACH : Crypto map attached for GM in group [chars].
Explanation A crypto map has been attached for the local group member.
Recommended Action Informational message.
%GDOI-5-GM_CM_DETACH : Crypto map detached for GM in group [chars].
Explanation A crypto map has been detached for the local group member.
Recommended Action Informational message.
%GDOI-5-GM_CONV_SA_DUPLEX : IPSec SAs converted to Duplex in group [chars] on the GM.
Explanation IPSec SAs have been converted to bidirectional mode in a group on a GM
Recommended Action None
%GDOI-5-GM_CONV_SA_DUPLEX_LOCAL : IPSec SAs converted to Duplex in group [chars] on a GM by a local event.
Explanation IPSec SAs have been converted to bidirectional mode in a group on a GM by a CLI command
Recommended Action None
%GDOI-5-GM_DELETE_EXPIRED_KEK : KEK expired for group [chars] and was deleted
Explanation Deleting Expired KEK
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%GDOI-5-GM_DELETE_EXPIRED_P2P : P2P SA with epoch hash 0x[chars] expired for group [chars] and was deleted
Explanation Deleting Expired P2P
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%GDOI-5-GM_DELETE_EXPIRED_PIP : PIP with SPI 0x[chars] expired for group [chars] and was deleted
Explanation Deleting Expired PIP
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%GDOI-5-GM_ENABLE_GDOI_CM : GM has enabled ACL on GDOI crypto map in group [chars].
Explanation Group member has enabled ACL on a GDOI Crypto map in a group with a key server
Recommended Action None
%GDOI-5-GM_FAILED_TO_INSTALL_POLICIES : FAILED: Installation of Reg/Rekey policies from KS [chars] for group [chars] & gm identity [chars]
Explanation Failed Policy installation
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%GDOI-5-GM_INSTALL_POLICIES_SUCCESS : SUCCESS: Installation of Reg/Rekey policies from KS [chars] for group [chars] & gm identity [chars] fvrf [chars] ivrf [chars]
Explanation Policy Installation Success
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%GDOI-5-GM_IV_EXHAUSTED : GM for group [chars] exhausted its IV space for interface [chars] and will re-register.
Explanation One of the interfaces where a CTR transform (e.g. GCM-AES / GMAC-AES) has been installed as TEK policy with SIDs has exhausted its IV space & must re-register to receive new SIDs.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%GDOI-5-GM_RECV_REKEY : Received Rekey for group [chars] from [chars] to [chars] with seq # [dec], spi [hex][hex]
Explanation Received Rekey
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%GDOI-5-GM_REGISTER_UPDATE_TBAR : Platform HA forwarding-plane comes online, group [chars] gm-identity [chars] fvrf [chars] ivrf [chars] re-register to refresh TBAR info.
Explanation HA forwarding-plane comes online, group %s gm-identity %s fvrf %s ivrf %s is re-registering to refresh TBAR info.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%GDOI-5-GM_REGS_COMPL : Registration to KS [chars] complete for group [chars] using address [chars] fvrf [chars] ivrf [chars]
Explanation Complete registration
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%GDOI-5-GM_REKEY_CIPHER_HASH_CHECK_FAIL : Rekey cipher/hash ([chars]) used in Group [chars] is unacceptable by this client.
Explanation The key-server has chosen KEK rekey cipher/hash algorithms which are not acceptable by this group-member
Recommended Action Contact the Key server's administrator.
%GDOI-5-GM_REKEY_IPV4_POLICY_CHECK_FAIL : Non-IPv4 policies is received in IPv4 Group [chars]; rekey is rejected
Explanation This GM is registering to an IPv4 group but erroneously receiving IPv6 policies in rekey
Recommended Action Contact the Key server's administrator.
%GDOI-5-GM_REKEY_IPV6_POLICY_CHECK_FAIL : Non-IPv6 policies is received in IPv6 Group [chars]; rekey is rejected
Explanation This GM is registering to an IPv6 group but erroneously receiving IPv4 policies in rekey
Recommended Action Contact the Key server's administrator.
%GDOI-5-GM_REKEY_TRANS_2_MULTI : Group [chars] transitioned to multicast rekey.
Explanation GM has transitioned from using unicast rekey mechanism to multicast mechanism
Recommended Action Informational message
%GDOI-5-GM_REKEY_TRANS_2_UNI : Group [chars] transitioned to Unicast Rekey.
Explanation GM has transitioned from using multicast rekey mechanism to unicast mechanism
Recommended Action Informational message
%GDOI-5-GM_REKEY_TRANSFORMSET_CHECK_FAIL : The transformset ([chars]) for data-protection in Group [chars] is unacceptable by this client.
Explanation The key-server has chosen a TEK transformset which is not acceptable by this group-member
Recommended Action Contact the Key server's administrator.
%GDOI-5-GM_SA_INGRESS : Receive only ACL received from KS [IP_address] in group [chars].
Explanation Received only acl has been received by GM from a KS in a group
Recommended Action None
%GDOI-5-GM_UNREGISTER : GM left the group [chars].
Explanation A Group member has left the group.
Recommended Action Informational message.
%GDOI-5-IPSEC_INITIATE_GM_REGISTER : IPSEC initiate GDOI group [chars] to register
Explanation IPSEC initiate a GM registration for the group
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%GDOI-5-KS_CLEAR_REGISTER : Config: KS cleared gdoi configuration for the group [chars].
Explanation clear crypto gdoi command has been executed by the local KS
Recommended Action Informational message.
%GDOI-5-KS_CONV_SAS_DUPLEX : IPSec SAs converted to Duplex in group [chars].
Explanation IPSec SAs have been converted to bidirectional mode in a group
Recommended Action None
%GDOI-5-KS_CONV_SAS_INGRESS : IPSec SAs converted to Ingress in group [chars].
Explanation IPSec SAs have been converted to receive only mode in a group
Recommended Action None
%GDOI-5-KS_GROUP_ADD : Config: KS [IP_address] added to the Group [chars].
Explanation A Config command has been executed to add a Key Server in a group
Recommended Action Informational message.
%GDOI-5-KS_GROUP_DELETE : Config: KS [IP_address] removed from the Group [chars].
Explanation A Config command has been executed to remove a Key Server from a group
Recommended Action Informational message.
%GDOI-5-KS_NACK_GM_EJECT : KS ejected GM [IP_address] in group [chars].
Explanation Key server has reached a condition of not receiving an ACK from GM and has been ejected
Recommended Action Informational message
%GDOI-5-KS_REGS_COMPL : KS completed successful registration in group [chars] with GM [IP_address].
Explanation Key server has successfully completed a registration in a group
Recommended Action None
%GDOI-5-KS_REINIT_FINISH : Re-initialization of group [chars] completed.
Explanation A previously triggered re-initialization, as signified by a %GDOI-5-KS_REINIT_GROUP syslog, has completed after the expiry of the old TEK.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%GDOI-5-KS_REINIT_GROUP : [chars] for group [chars] and will re-initialize the group.
Explanation KS has reached one of the following conditions (indicated by the first part of the message) requiring re-initialization of the group: - Group Size configuration changed - Previously used KSSID removed from configured KSSID set - KS runs out of KSSIDs & GMSIDs - COOP SID client gets a re-initialization indication from COOP-KS - KSSID overlap detected by COOP is resolved - TEK policy is changed from non-CTR to CTR (SIDs required).
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%GDOI-5-KS_REKEY_TRANS_2_MULTI : Group [chars] transitioned to multicast rekey.
Explanation Group has transitioned from using unicast rekey mechanism to multicast mechanism
Recommended Action Informational message
%GDOI-5-KS_REKEY_TRANS_2_UNI : Group [chars] transitioned to Unicast Rekey.
Explanation Group has transitioned from using multicast rekey mechanism to unicast mechanism
Recommended Action Informational message
%GDOI-5-KS_SEND_MCAST_REKEY : Sending Multicast Rekey [chars]for group [chars] from address [chars] to [chars] with seq # [dec] spi: [hex][hex]
Explanation Sending Multicast Rekey
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%GDOI-5-KS_SEND_UNICAST_REKEY : Sending Unicast Rekey [chars]for group [chars] from address [chars] with seq # [dec] spi: [hex][hex]
Explanation Sending Unicast Rekey
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%GDOI-5-KS_USING_DEFAULT_TRANSFORM : GETVPN is using default transforms for profile [chars]
Explanation Using default transformset
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%GDOI-5-LKH_DISABLE : LKH disabled in group [chars].
Explanation LKH has been disabled in a group
Recommended Action None
%GDOI-5-LKH_ENABLE : LKH enabled in group [chars].
Explanation LKH has been enabled in a group
Recommended Action None
%GDOI-5-POLICY_CHANGE : GDOI group [chars] policy has changed. Use 'crypto gdoi ks rekey' to send a rekey, or the changes will be send in the next scheduled rekey
Explanation Reminder message that GDOI configuration has changed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%GDOI-5-POLICY_CHANGE_ERROR_MULTIPLE_PORTS : Multiple ports detected for ACL [chars] which is not supported. WARNING: No TEK policy will be created.
Explanation Informs user that there is an error in the ACL with regards to the number of ports.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%GDOI-5-POLICY_CHANGE_TO_SUITEB : Group [chars] changed to Suite-B policy. Use 'crypto gdoi ks rekey' to generate the new Suite-B policy and cause all GMs to re-register to download SIDs, or this will happen in the next scheduled rekey
Explanation Migrating from non-Suite-B to Suite-B policy requires that the user issues 'crypto gdoi ks rekey' like any other POLICY_CHANGE, but this will cause a re-initialization rather than just a rekey.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%GDOI-5-SA_KEK_UPDATED : SA KEK was updated [hex][hex][hex][hex]
Explanation KEK was updated in the Registration/Rekey and a new KEK SA was created
Recommended Action Informational message.
%GDOI-5-SA_PIP_UPDATED : SA PIP was updated 0x[chars]
Explanation PIP was updated in Registration/Rekey and a new PIP SA was created
Recommended Action Informational message.
%GDOI-5-SA_TEK_UPDATED : SA TEK was updated
Explanation TEK was updated in the Registration/Rekey and a new TEK IPSEC SA was created
Recommended Action Informational message.
%GDOI-6-COOP_KS_VER_TRANSIT : Coop KS [chars] protocol version transits from version 1.0.1 to 2.0.0
Explanation The KS is transitioning to a new version.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%GDOI-6-KS_FIRST_GM : Re-key: First GM [IP_address] seen by KS in the group [chars].
Explanation Local key server has received the first group member joining the group
Recommended Action Informational message.
%GDOI-6-KS_LAST_GM : Re-key: Last GM [IP_address] left the group [chars].
Explanation Last group member has left the group on the local key server
Recommended Action Informational message.
GENERIC_SUBBLOCK
%GENERIC_SUBBLOCK-2-BUILDXDR : Failed to build message for GSB: [chars]
Explanation An attempt to build a message for distribution of generic subblock failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%GENERIC_SUBBLOCK-2-GSBNOTISSUAWARE : GSB [chars] is not ISSU aware. Cannot distribute it to ISSU-aware slots
Explanation This GSB is expected to be ISSU aware but it is not. It cannot be distributed safely to ISSU-aware slots as it may not be correctly interpreted
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%GENERIC_SUBBLOCK-2-LATE_REGISTER : Late registration of GSB type [chars], with id [dec]
Explanation An attempt to register a new generic subblock type was received after subblocks have already been allocated from the control structure with previously registered types
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%GENERIC_SUBBLOCK-2-UNPACKXDR : Unpacked [dec] bytes and attempted to consume [dec] bytes for GSB: [chars]
Explanation A discrepancy was detected between length of message expected versus length of message received
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
GEN_DB
%GEN_DB-3-INVALID_CLIENT_TYPE : [chars]: Invalid client type, got [dec] (must be between 0 and [dec])
Explanation This message indicates that client type is outside the expected range
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%GEN_DB-3-INVALID_RECORD_KEY : [chars]: invalid record key *
Explanation This message indicates that the record key is invalid
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%GEN_DB-3-KEY_FUNC_DOESNT_EXIST : [chars]: Key function does not exist
Explanation This message indicates that key function being considered does not exist in the database definition
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%GEN_DB-3-LIST_FAIL : [chars]:[chars]
Explanation This message indicates that a list operations such as enqueue, dequeu failed
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%GEN_DB-3-LIST_FAIL_FOR_RECORD : [chars]:[dec]:[chars]
Explanation This message indicates that a list operations such as enqueue, dequeu failed
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%GEN_DB-3-NO_KEY_FUNC : [chars]: [chars][chars]
Explanation This message indicates that key functions are missing from the database handle, or key function is a NULL Pointer
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%GEN_DB-3-NULL_DB_HNDL : NULL Database Handle [chars]
Explanation This message indicates the database handle was NULL
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%GEN_DB-3-NULL_DB_HNDL_ELEMENT : [chars]: NULL Database Element [chars]
Explanation This message indicates the database handle element was NULL
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%GEN_DB-3-NULL_TREE_NODE : Node is NULL [chars]
Explanation This message indicates that the tree node being examined is NULL
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%GEN_DB-3-PARSER_INIT_FAIL : [chars]:[dec]: Parser Could not be initialized
Explanation This message indicates that the IOS Parser command could not be initialized
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%GEN_DB-3-RECORD_DELETE_FAIL : [chars]:[chars]
Explanation This message indicates that a record could not be deleted
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%GEN_DB-3-UNKNOWN_PARSER_CMD : [chars]:[dec]: Unknown Parser Command
Explanation This message indicates that the IOS Parser command was not recognized
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%GEN_DB-3-WAVL_FAIL : [chars]: [chars]
Explanation This message indicates that a wavl tree operation failed
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
GEN_PROXY
%GEN_PROXY-3-GPM_ALLOC_FAILED : GPM allocation for reply failed pak_size [hex] reply_size [hex]
Explanation GPM could not be allocated for reply.
Recommended Action LOG_STD_ACTION
%GEN_PROXY-3-IPC_SEND_FAILED : IPC send reply failed [chars]
Explanation GEN proxy failed to send of reply to IPC msg.
Recommended Action LOG_STD_ACTION
%GEN_PROXY-3-IPC_UNHANDLED : failure
Explanation An unknown message type: %d was received by the Generic Client Proxy.
Recommended Action LOG_STD_ACTION
%GEN_PROXY-3-REPLY_MSG : wrong version [dec]
Explanation An incorrect SBS message was received by the Generic Client Proxy.
Recommended Action LOG_STD_ACTION
%GEN_PROXY-3-STACK_ALLOC_FAILED : Stack allocation for reply failed reply_size [hex]
Explanation Stack space could not be allocated for reply.
Recommended Action LOG_STD_ACTION
GLBP
%GLBP-3-MISCONFIG : Cannot add MAC address [enet] to interface [chars] -not supported
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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%GLBP-4-BADAUTH : Bad authentication received from [chars], group [dec]
Explanation Two routers participating in a Gateway Load Balancing Protocol group disagree on the valid authentication string.
Recommended Action Use the glbp authentication interface command to repair the GLBP authentication discrepancy between the local system and the one whose IP address is reported.
%GLBP-4-BADVIP : [chars] Grp [dec] address [chars] is in the wrong subnet for this interface
Explanation The GLBP virtual IP address contained in the Hello message cannot be learnt as it is not within a subnet configured on the interface.
Recommended Action Check the configuration on all GLBP routers and ensure that the virtual IP address is within a configured subnet.
%GLBP-4-DIFFVIP1 : [chars] Grp [dec] active routers virtual IP address [chars] is different to the locally configured address [chars]
Explanation The GLBP virtual IP address contained in the Hello message from the Active router is different to that configured locally.
Recommended Action Check the configuration on all GLBP routers.
%GLBP-4-DUPADDR : Duplicate address [chars] on [chars], sourced by [enet]
Explanation The IP address in a GLBP message received on the interface is the same as the router's own IP address. This may be because of misconfiugration, or because of a malfunctioning switch
Recommended Action Check the configurations on all the GLBP routers, and make sure that any switches you have are functioning properly.
%GLBP-4-DUPVIP1 : [chars] Grp [dec] address [chars] is already assigned to [chars] group [dec]
Explanation The GLBP virtual IP address contained in the Hello message cannot be learnt as it is already assigned to a different GLBP group.
Recommended Action Check the configuration on all GLBP routers.
%GLBP-4-DUPVIP2 : [chars] Grp [dec] address [chars] is already assigned on this interface
Explanation The GLBP virtual IP address contained in the Hello message cannot be learnt as it is already assigned to this interface.
Recommended Action Check the configuration on all GLBP routers.
%GLBP-4-DUPVIP3 : [chars] Grp [dec] address [chars] is already assigned to, or overlaps with, an address on another interface or application
Explanation The GLBP virtual IP address contained in the Hello message cannot be learnt as it is already assigned to, or overlaps with, an address on another interface or application.
Recommended Action Check the configuration on all GLBP routers.
%GLBP-6-FWDSTATECHANGE : [chars] Grp [int] Fwd [int] state [chars] -> [chars]
Explanation The GLBP forwarder has changed state
Recommended Action No action is required.
%GLBP-6-STATECHANGE : [chars] Grp [int] state [chars] -> [chars]
Explanation The GLBP gateway has changed state
Recommended Action No action is required.
GRIP
%GRIP-2-BADROUTE : Error [chars] route -null table
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.
%GRIP-3-BADPATHS : Invalid number of paths ([dec]) for %q
Explanation An internal inconsistency was detected in the XNS routing table structure.
Recommended Action Note the parameters associated with this message and call your technical support representative for assistance.
H
HAL_GENMEM
%HAL_GENMEM-3-HAL_MISMATCHED_GENMEM : VADDR:[int] LINE: [dec]
Explanation Mismatched genmem.
Recommended Action LOG_STD_ACTION
HAL_PACKET
%HAL_PACKET-3-HAL_GATHER_ASYNC_WAIT_TIMEOUT : seqnum=[int] pak-type=[int]
Explanation Packet Hardware Transmit Error
Recommended Action LOG_STD_ACTION
HA_PROXY
%HA_PROXY-2-HA_FIND_SERVICE_FAILED : [chars]: unable to find [chars] service
Explanation HA could not find the specified service
Recommended Action LOG_STD_ACTION
%HA_PROXY-2-HA_SESSION_ALLOC_FAILED : [chars]: unable to allocate entry for [chars] binding
Explanation HA could not allocate a control block to manage the service
Recommended Action LOG_STD_ACTION
%HA_PROXY-3-HA_DUP_SERVICE_INDEX : [chars]: Duplicate service index: [dec] on bind
Explanation Duplicate service index on ha service bind
Recommended Action LOG_STD_ACTION
%HA_PROXY-3-HA_DUP_SERVICE_NAME : [chars]: Duplicate service name: [chars] on bind
Explanation Duplicate service name on ha service bind
Recommended Action LOG_STD_ACTION
%HA_PROXY-3-HA_INVALID_REQUEST : [chars]: Unknown request: [dec]
Explanation HA control services received unknown request
Recommended Action LOG_STD_ACTION
%HA_PROXY-3-HA_MALFORMED_PKT : Malformed packet bad [chars] [hex], MSGDEF_LIMIT_MEDIUM
Explanation HA Sync packet was malformed, may not have been fully processed
Recommended Action LOG_STD_ACTION
%HA_PROXY-3-PROXY_IPC_PAK_ALLOC_FAILED :
Explanation Allocation of IPC packet failed.
Recommended Action LOG_STD_ACTION
%HA_PROXY-4-HA_PKT_ERROR : Error processing HA sync pkt, rg [hex], MSGDEF_LIMIT_MEDIUM
Explanation HA Sync packet was dropped while processing
Recommended Action LOG_STD_ACTION
%HA_PROXY-4-HA_UNKNOWN_SERVICE : Sync msg for unknown service [hex] rg [hex], MSGDEF_LIMIT_MEDIUM
Explanation HA Sync received a message for an unknown service
Recommended Action LOG_STD_ACTION
HDLC
%HDLC-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.
%HDLC-4-ISSU_INCOMPATIBLE : hdlc-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%HDLC-4-ISSU_SENDFAILED : HDLC 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%HDLC-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
HFSLIB
%HFSLIB-3-HFSINOFAILED : Inotify failed to initialize : [chars]
Explanation This error occurs when the inotify sub-system is misbehaving
Recommended Action No action is required.
%HFSLIB-3-HFSINOWATCH : Inotify failed to add a watch: [chars]
Explanation This error occurs when the inotify sub-system is misbehaving
Recommended Action No action is required.
%HFSLIB-3-HFSOPEN : Problem accessing the udev generated file: [chars]
Explanation No explanation.
Recommended Action No action is required.
HMAN
%HMAN-2-INITIALIZATION_FAILED : Host Manager initialization failed.
Explanation Initialization of the host manager failed.
Recommended Action Review Host Manager 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. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/c/en/us/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%HMAN-3-CONSOLE_SETUP_FAILED : Failed to setup console service. It should be enabled on [chars]
Explanation Setup of a console service failed.
Recommended Action Check the host manager launch parameters and correct as required.
%HMAN-3-HOSTNAME_SET_FAILED : Failed to set hostname: [chars]
Explanation The host manager received notification that the system hostname has been set. The host manager failed to pass this value to the ASR kernel.
Recommended Action Repeat the process to configure the hostname. 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/c/en/us/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
HW_API
%HW_API-3-BACKWALK_REQUEST : Backwalk request failed, [chars]
Explanation A request to walk internal data structures has failed. Depending on criticality of the data, accuracy of forwarding may impacted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%HW_API-3-BACKWALK_REQUEST_VALUE : Backwalk request failed, [chars] ([hex])
Explanation A request to walk internal data structures has failed. Depending on criticality of the data, accuracy of forwarding may impacted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%HW_API-3-INIT_FAIL : HW-API init [chars] failed[chars]
Explanation HW_API_INTERNAL_ERROR
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%HW_API-3-INVALID_CONTEXT : Invalid context [hex]
Explanation HW_API_INTERNAL_ERROR
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%HW_API-3-INVALID_OBJ : Invalid object [hex]
Explanation HW_API_INTERNAL_ERROR
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%HW_API-3-INVALID_TYPE : Invalid type [dec]
Explanation HW_API_INTERNAL_ERROR
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%HW_API-3-INVALID_WALK_SPEC : Invalid walk spec [hex]
Explanation HW_API_INTERNAL_ERROR
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%HW_API-3-NO_OBJ_TYPE_LIST_ENTRY2 : Invalid sw_obj_link_type ([dec]) used with obj_type_list
Explanation HW_API_INTERNAL_ERROR
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%HW_API-3-NO_OBJ_TYPE_LIST_ENTRY : Invalid sw_obj_type ([dec]) used with obj_type_list
Explanation HW_API_INTERNAL_ERROR
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%HW_API-3-RESILIENCE_NO_HANDLER : No handlers in place for [chars] sw object creation failure.
Explanation COMMON_HW_API_INTERNAL_ERROR
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%HW_API-3-VECTOR : Failed to set [chars] vector for [chars], [chars]
Explanation HW_API_INTERNAL_ERROR
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%HW_API-3-WALK_MODE_UNSUPPORTED : Walk mode '[chars]' unsupported
Explanation HW_API_INTERNAL_ERROR
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
HPI
%HPI-3-CODEC_NOT_LOADED : channel:[chars] DSP ID:[hex], command failed as codec not loaded [dec]
Explanation Sending messages to DSP without a loaded codec can result with the DSP failing
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%HPI-3-FAILED_START : channel:[chars] DSP ID:[hex], failed mode [dec] for service [dec]
Explanation Failed to start DSP services
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%HPI-3-GSMAMRNB_LICENSE_NOT_ACTIVATED : ********************************************************* GSM AMR-NB License is not yet activated. Please configure 'license feature gsmamrnb-codec-pack' and accept the EULA to activate the license. *********************************************************
Explanation Failed to start DSP services for GSM AMR-NB codec
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%HPI-3-INVALID_PAYLOAD : wrong payload size, channel:[chars] DSP ID:[hex], failed mode [dec] for service [dec]
Explanation Failed to start DSP services
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%HPI-3-NACK_HIGH : DSP to IOS Nack message with severity [chars] [chars] [chars]
Explanation DSP to IOS Nack message with high severity
Recommended Action Check the NACKed message's parameters for configuration errors. These messages tend to affect call flow, thus they are labeled with high severity.
%HPI-3-SRTP_EVAL_FREE_ERROR : Error encountered on release SRTP bandwidth and tunnels reservation
Explanation Error encountered on release SRTP bandwidth and tunnels
Recommended Action No action is required.
%HPI-4-INVALID_CODEC_LOAD : channel:[chars] DSP ID:[hex], invalid hpi mode [dec] for loading codec [dec]
Explanation Attempt to load codec when the DSP is in an invalid mode which can result with DSP failure
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%HPI-4-INVALID_ECAN_TYPE : [chars] ECAN is not available in voice-card [dec], [chars] ECAN will be used
Explanation All voice cards participated in DSPFarm must have the same echo canceller type
Recommended Action Make sure all voice cards participated in DSPFarm have the same echo canceller type configured
%HPI-4-NACK_MED : DSP to IOS Nack message with severity [chars] [chars] [chars]
Explanation DSP to IOS Nack message with medium severity
Recommended Action Check the NACKed message's parameters for minor configuration errors.
%HPI-4-NO_CLOSE : channel:[chars] DSP ID:[hex]
Explanation Attempt to release DSP without sending close message
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%HPI-6-NACK : DSP to IOS Nack message [chars] [chars]
Explanation DSP to IOS Nack message with no severity in order to work with dspware without Nack severity implementation
Recommended Action Information only, displaying NACKed messages.
%HPI-6-NACK_LOW : DSP to IOS Nack message with severity [chars] [chars] [chars]
Explanation DSP to IOS Nack message with low severity
Recommended Action Information only, displaying NACKed messages that are for debugging purposes.
%HPI-6-SRTP_EVAL_LIMIT : The SRTP bandwidth and tunnels usage exceed the license limits
Explanation The SRTP bandwidth and tunnels exceed the license limits
Recommended Action No action is required.
HSRP
%HSRP-3-MISCONFIG : Attempt to change [chars] MAC address to [enet] when DECNET already running
Explanation An HSRP group attempted to become active on an interface that can only support a single MAC address and which is running DECnet. If standby use-bia is not configured then HSRP would normally set the interface MAC address to the HSRP virtual MAC address, but this is not allowed if DECnet is running.
Recommended Action Enable standby use-bia on the interface.
%HSRP-3-NOSOCKET : Unable to open socket
Explanation The system was unable to initialize an IP connection for the Hot Standby protocol.
Recommended Action Make sure that there is at least one interface configured to run IP.
%HSRP-4-BADAUTH2 : Bad authentication from [chars]
Explanation Two routers participating in HSRP disagree on the valid authentication string.
Recommended Action Use the standby authentication command to repair the HSRP authentication discrepancy between the local system and the one whose IP address is reported.
%HSRP-4-BADAUTH : Bad authentication from [chars], group [dec], remote state [chars]
Explanation Two routers participating in HSRP disagree on the valid authentication string.
Recommended Action Use the standby authentication command to repair the HSRP authentication discrepancy between the local system and the one whose IP address is reported.
%HSRP-4-BADVIP : [chars] Grp [dec] address [chars] is in the wrong subnet for this interface
Explanation The HSRP virtual IP address contained in the Hello message cannot be learnt as it is not within a subnet configured on the interface.
Recommended Action Check the configuration on all HSRP routers and ensure that the virtual IP address is within a configured subnet.
%HSRP-4-DIFFVIP1 : [chars] Grp [dec] active routers virtual IP address [chars] is different to the locally configured address [chars]
Explanation The HSRP virtual IP address contained in the Hello message from the Active router is different from the virtual IP address configured locally.
Recommended Action Check the configuration on all HSRP routers in the group and ensure they are all configured with the same virtual IP address.
%HSRP-4-DUPADDR : Duplicate address [chars] on [chars], sourced by [enet]
Explanation The IP address in an HSRP message received on the specified interface is the same as the IP address of the router. Another router might be configured with the same IP address. The most likely cause is a network loop or a misconfigured switch that is causing the router to see its own HSRP Hello messages.
Recommended Action Check the configurations on all the HSRP routers to ensure that the interface IP addresses are unique. Check that no network loops exist. If port channels are configured check that the switch is correctly configured for port-channels. Enable standby use-bia so that the error message displays the interface MAC address of the sending router. This can be used to determine if the error message is caused by a misconfigured router or a network loop.
%HSRP-4-DUPVIP1 : [chars] Grp [dec] address [chars] is already assigned to [chars] group [dec]
Explanation The HSRP virtual IP address contained in the Hello message cannot be learnt as it is already assigned to a different HSRP group.
Recommended Action Check the configuration on all HSRP routers and ensure that the virtual IP address of each HSRP group is unique.
%HSRP-4-DUPVIP2 : [chars] Grp [dec] address [chars] is already assigned on this interface
Explanation The HSRP virtual IP address contained in the Hello message cannot be learnt as it is already assigned to this interface.
Recommended Action Check the configuration on all HSRP routers and ensure that the virtual IP address of each HSRP group is unique.
%HSRP-4-DUPVIP3 : [chars] Grp [dec] address [chars] is already assigned to, or overlaps with, an address on another interface or application
Explanation The HSRP virtual IP address contained in the Hello message cannot be learnt as it is already assigned to, or overlaps with, an address on another interface or application.
Recommended Action Check the configuration on all HSRP routers and ensure that the virtual IP address of each HSRP group is unique.
%HSRP-5-STATECHANGE : [chars] Grp [dec] state [chars] -> [chars]
Explanation The router has changed state
Recommended Action No action is required.
HTTP
%HTTP-3-INIT_FAIL : HTTP Process Init failed.
Explanation Initialization of the HTTP Subsystem has failed
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
%HTTP-3-OUTOF_MEM : HTTP out of memory.
Explanation An error occurred during initialization of the HTTP process. The HTTP process could not create crucial internal data structures that are required for operation of the HTTP subsystem. The most likely reason for this condition is an exhaustion of system memory.
Recommended Action Reduce other system activity to ease memory demands. if conditions warrant, upgrade to a larger memory configuration.
%HTTP-3-PROC_NOCREAT : Unable to create HTTP process.
Explanation An error occurred during initialization of the HTTP process. The HTTP process that processes all HTTP requests and responses could not be created.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
%HTTP-4-SERVER_CONN_RATE_EXCEED : Number of connections per minute has exceeded the maximum limit([dec]) as specified by the platform.
Explanation The message indicates that the current number of connections requested per minute has exceeded the limit specified by the platform. HTTP server will resume accepting the connections 15 seconds from the time the message is issued. This restriction is done as per the HTTP throttling functionality.
Recommended Action Reduce connection rate to the server.
%HTTP-6-SERVER_SETUP_FAILED : Server setup failed
Explanation Setup of the HTTP(S) server to listen on the specified port number has failed.
Recommended Action Disable the server, verify that port number is correct and enable the server. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
HTTPC
%HTTPC-3-CACHE_MEM : HTTP Client Cache Init out of memory.
Explanation None
Recommended Action None
%HTTPC-3-CONNECT_NULL : NULL connection structure for fd([dec]) -closing socket.
Explanation The HTTP Client is receiving the socket READ event but it fails to locate the connection structure for this file descriptor(fd). If this is seen continuously in a loop, it is an indication that something has gone wrong in the socket code. Since the socket is immediately closed after this event, the HTTP client should stop seeing READ event.
Recommended Action Record the error and traceback and report it to the system administrator.
%HTTPC-3-COOKIE_MEM : HTTP Client runs out of allowable memory to store cookies.
Explanation The total memory allocated for storing cookies has run out. All cookies received from the HTTP server will be dropped. Users may no longer be able to interact with a session-based origin server until memory is freed up.
Recommended Action Users may want to try their requests at a later time or contact the system administrator to increase the maximum RAM allowed for saving HTTP cookies.
%HTTPC-3-INIT_FAIL : HTTP Client Process Init failed.
Explanation None
Recommended Action None
%HTTPC-3-OUTOF_MEM : HTTP Client out of memory.
Explanation None
Recommended Action None
%HTTPC-3-OUTOF_SYNC : HTTP Client header tables out of sync.
Explanation None
Recommended Action None
%HTTPC-3-PROC_NOCREAT : Unable to create HTTP Client process.
Explanation None
Recommended Action None
%HTTPC-3-RECEIVE_SOCK_READ_EVENT_WHILE_DISABLED : Received socket read event while read interest is disabled callID([dec]) fd([dec]) -closing socket.
Explanation The HTTP Client is receiving the socket READ event while the READ interest is being disabled. Something has gone wrong between the http client and the socket interfaced.
Recommended Action Record the error and report it to the system administrator.
%HTTPC-6-CLOSE_SRV_CONNECT : The connection to server [IP_address] appears to be hung and will be closed.
Explanation Messages are being backed up in the HTTP Client's write queue in the connection with the specified server. The connection is assumed to have gone bad and the HTTP Client is closing the connection.
Recommended Action Check with the specified server for possible connection error.
%HTTPC-6-CONNECT_FAILED : The connection to server [IP_address] failed
Explanation None
Recommended Action None
%HTTPC-6-REQUEST_FAILED : request URI [chars] failed
Explanation None
Recommended Action None
HW_IDPROM_ENVMON
%HW_IDPROM_ENVMON-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 If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%HW_IDPROM_ENVMON-3-HW_IDPROM_CHECKSUM_INVALID : The idprom contains an invalid checksum in a sensor entry. Expected: [hex], calculated: [hex]
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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%HW_IDPROM_ENVMON-3-HW_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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
HW_PFU
%HW_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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%HW_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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
I
ICC
%ICC-2-JOIN : ICC mcast joining failed member <[hex]> to group <[hex]> with ipc error <[chars]>
Explanation ICC was not able to join a member for the mcast group
Recommended Action collect output 'show icc mcast status' from RP
%ICC-2-NOMEM : No memory available for [chars]
Explanation The ICC subsystem could not obtain the memory it needed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%ICC-2-OPEN : ICC Create Session Failed for card <[hex]> Queue <[chars]>
Explanation ICC was not able to create a session for the destination seat
Recommended Action collect output from 'show oir debug swover_global_mask' from SP
%ICC-3-MAST_BAD_FREE : ICC multicast memory already freed
Explanation One of the ICC multicast request's memory was found to be free when response arrived
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%ICC-4-BAD_ACCOUNTING : ICC received a bad class [dec]
Explanation A communication failure has occurred between this card and another card in the system.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%ICC-4-COMM : Communication failure occurred while [chars]
Explanation None
Recommended Action None
%ICC-4-CONSISTENCY : Internal consistency check: [chars]
Explanation An internal inconsistency was found in some ICC data structures.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%ICC-4-HEARTBEAT : Card [dec] failed to respond to heartbeat
Explanation A communication failure has occurred between the primary and the specified line card.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%ICC-5-HUGE_BUFFER : Class [[chars]] with Request id [dec] requested a huge buffer of Size [dec].
Explanation Huge packet requests would deplete the memory at the linecards
Recommended Action ICC client is trying to request huge packet buffer Please use the command Show icc internal to get get the traceback and file a DDTS against the component
%ICC-5-WATERMARK : [dec] [chars] [chars] pkts for class [chars] are waiting to be processed
Explanation Processor got packets for the class and are waiting to be procssed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
IDB_IDENTITY
%IDB_IDENTITY-3-MALLOC : Memory allocation failure for HWIDB type [dec]
Explanation A memory allocation failure occured when trying to allocate the identity for this HWIDB. This HWIDB will not be allocated an IF Index which will prevent it from being used for forwarding data.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
IDB_SGI
%IDB_SGI-2-MEMREQ : [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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IDB_SGI-2-XDRREG : [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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IDB_SGI-3-BADPTR : [chars] of interface with ifindex [int] is invalid
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IDB_SGI-3-MEMFAIL : [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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IDB_SGI-3-XDRREQ : [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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IDB_SGI-4-INTERR : [chars] for interface with ifindex [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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IDB_SGI-4-MEMBERREQ : member request failure for interface with ifindex [int] returned err -[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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IDB_SGI-4-UNEXPINP : [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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
IDMGR
%IDMGR-3-ID_MANAGER_INTERNAL_ERROR : [chars]
Explanation Internal Error occured with ID Manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IDMGR-3-INTERRUPT : [chars]
Explanation An id_get attempted at interrupt level.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IDMGR-3-INVALID_ID : bad id in [chars] (id: [hex])
Explanation An ID Manager error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IDMGR-3-INVALID_ID_TABLE_SIZE : bad new ID table size
Explanation A bad new table request to ID Manager occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IDMGR-3-MALLOC_FAILURE : [chars]
Explanation A malloc failure occured in ID Manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
IEDGE
%IEDGE-3-CH_INTERNAL_ERROR : Internal error in command processing -session handle=[hex]
Explanation There has been an internal error relating to CoA command processing.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%IEDGE-3-CH_REGISTER_ERROR : CoA registration error in command processing -type '[chars]'
Explanation There has been an internal error relating to CoA command processing.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%IEDGE-4-CLOCK_CHANGE_TIMER_INV : A Local clock change has caused a running timer to be invalid
Explanation A change in local clock has made a currently running timer to be invalid
Recommended Action Check the clock configuration
%IEDGE-4-PBHK_DEPLETED_INDICES : No more portbundles can be allocated
Explanation The source interfaces configured for Portbundle Hostkey feature are not sufficient and the number of portbundles available are all used up. Add more source interfaces in the configuration.
Recommended Action Check configuration on the ISG
%IEDGE-4-TC_UNDEFINED_ACL : Traffic class ACL [chars] is not defined, creating permit all ACL
Explanation The ACL specified for classification of traffic is not configured on the ISG. Creating a permit all ACL. ACL should be configured on the ISG.
Recommended Action Configure the ACL on the ISG
IF
%IF-2-IDB_TABLE_INIT : Malloc failed while initializing idb table
Explanation None
Recommended Action None
%IF-3-BADHWUNLOCK : ([chars]) attempted to unlock [chars] ([dec]). Locked by [chars] ([dec]).
Explanation Attempt to release semaphore held by another process.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IF-3-BADLOCK : Invalid lock use for [chars]: [chars][chars]
Explanation Application layer code attempted to access an unlocked interface.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IF-3-BADMACADDRTYPE : illegal mac address type, [dec]
Explanation This is an interal error that was recovered gracefully.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IF-3-BAD_MTU : Internal error. MTU on [chars] too large or negative. Truncating from %ld to [int].
Explanation An internal software error occurred. The system attempted to set the MTU on an interface to an invalid value.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%IF-3-IDB_LIST_BAD_REF_COUNT : A bad reference count was encountered in an idb list element.
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%IF-3-SEMAHOG : ([chars]) could not get [chars] semaphore. Held by ([chars]).
Explanation Unable to obtain interface semaphore.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IF-4-BACKWARD_COUNTERS : Corrected for backward [chars] counters ([int] -> [int]) on [chars]
Explanation The interface specified in the message has a packet counter that has decreased in number. This condition can occur if a packet is counted and then dropped. This event was detected and corrected.
Recommended Action If this condition persists, copy the error message exactly as it appears on the console or in the system log. Issue the <CmdBold>show tech-support<NoCmdBold> 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 <CmdBold>show tech-support<NoCmdBold> command output, contact your Cisco technical support representative and provide the representative with the gathered information.
%IF-4-NOBGPROCESS : Network background process not running. [chars]
Explanation A process which manages network interface background processing is not yet running, but another system process has tried to send the process a message.
Recommended Action An interface on the router may have missed a request to bring itself up. If that happens, it may be necessary to reset the interface using a <CmdBold>shutdown<NoCmdBold> operation and then a <CmdBold>no shutdown<NoCmdBold>.
IFDAMP
%IFDAMP-5-UPDOWN : interface [chars] update [chars] state to [chars], interface is [chars]suppressed
Explanation dampening interface changed state.
Recommended Action No action is required.
%IFDAMP-5-ZERODELAY : dampening reuse timer is updated with 0 delay time
Explanation Inconsistency of dampening reuse timer wheel
Recommended Action No action is required.
IFMAP
%IFMAP-3-CAUSE_CFG : hash table not initialized
Explanation PAL interface handle to uidb hash table not initialized
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
IFMGR
%IFMGR-3-BADIFINDEXTABLE : The file nvram:ifIndex-table is corrupt.
Explanation The file is not in the expected format.
Recommended Action If possible, please delete the file.
%IFMGR-3-DUP_IFINDEX : Duplicate ifIndex ([dec]) found for ifDescr [chars]; exists in ifTable for ifDescr [chars].
Explanation Interfaces have same ifIndex in IF-MGR assigned list. The 2nd interface registered with IF-MGR will be assigned with new index
Recommended Action 1. No Action, if ifIndex persist is not required. 2. Reload the standby RP, if ERR msg only seen in standby RP 3. Reload the router with the proper ifindex-table and image
%IFMGR-3-IFDB : IF manager interface database [chars] failure-[dec]
Explanation None
Recommended Action TBD
%IFMGR-3-IFINDEX_PERSIST_ENTRY_CORRUPT : [chars] seems to be corrupted. Trying to read [dec] size
Explanation The ifIndex-table seems to be corrupted.
Recommended Action Delete the ifindex-table.
%IFMGR-3-IFTDB : IF manager interface table database [chars] failure-[dec]
Explanation None
Recommended Action TBD
%IFMGR-3-INVALID_PERSISTENT_DATA : Invalid persistent data
Explanation Trying to write invalid persistent data
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%IFMGR-3-NOIMACP : IF manager control process failed to start
Explanation None
Recommended Action TBD
%IFMGR-3-NOTYPEVECTOR : Interface manager failed to allocate IF type vector. size [dec]
Explanation The interface type vector was not able to be allocated with the number of elements required--initially or resize.
Recommended Action TBD
%IFMGR-3-NOVECTOR : Interface manager failed to allocate IF vector. size [dec]
Explanation The interface vector was not able to be allocated with the number of elements required--initially or resize (see size in the error message).
Recommended Action TBD
%IFMGR-3-VECTOREXD : IF manager attempted to use interface [dec] outside vector range.
Explanation This message indicates that an interface with too large of an ifIndex value was attempted to be added to the IF-MGR DB.
Recommended Action Additional IF-MGR warning and/or error messages should accompany indication of this error. These additional messages should provide more details on the effected interface.
%IFMGR-3-VECTORPOSUSED : IF manager attempted to add interface [dec] which was already added.
Explanation This message comes from the IF-MGR DB when it is trying to add an ifIndex value for this interface which already exists in the ifIndex DB.
Recommended Action TBD
%IFMGR-4-NOIFINDEX : All SNMP if indices are exhausted
Explanation All SNMP MIB indices have been exhausted. Interfaces will not be able to obtain an interface index that they can use to register with the interface MIB.
Recommended Action Attempt a system reload. If the problem persists after the system reload, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
%IFMGR-4-NOSYNC : ifIndex not being synced between active and standby
Explanation When the standby comes up, then the tuple of ifIndex and ifDescr is synced so that when interfaces comes up they get the same ifIndex. This error happens when the interface doesn't get the ifIndex for the given ifDescr
Recommended Action Inform the technical support to raise the ddts
%IFMGR-4-STACK_RELATIONSHIP_ADD_ERROR : [chars]: Request for creating invalid stack relationship [dec], [dec]
Explanation The IF MGR received the call to add invalid stack relationship. The higher and lower ifIndex are shown in the message. The module of the IF MGR from where this message is generated is also shown in the message
Recommended Action Inform the technical support to raise the ddts
%IFMGR-4-VECTORIFSUSPECT : IF manager added interface [dec] which is unexpectedly large.
Explanation The ifIndex allocation scheme gives out sequential ifIndex values. This message comes from the IF-MGR DB when it is trying to add an ifIndex value much larger than the former greatest ifIndex value in the DB.
Recommended Action TBD
%IFMGR-5-RESTART : [chars]
Explanation The IF MGR process has restarted
Recommended Action This is an informational message. The system should recover on its own.
%IFMGR-7-NO_IFINDEX_FILE : Unable to open [chars] [chars]
Explanation This is a informational message. This means system found no saved ifIndex information, and ifIndex is not persisted across reboots. The ifIndices will be reassigned.
Recommended Action 1. No Action, if 'snmp-server ifIndex persist' is not configured. 2. If 'snmp-server ifindex persist' is configured then copy the error message exactly as it appears, and report it to your technical support representative.
IFS
%IFS-3-FS_CREATE_FAIL2 : Failed to create [chars] simple file system, [chars]
Explanation An internal software error occurred.
Recommended Action Call your technical support representative for assistance.
%IFS-3-FS_CREATE_FAIL : Failed to create [chars] file system, [chars]
Explanation An internal software error occurred.
Recommended Action Call your technical support representative for assistance.
%IFS-3-FSDUP : Failed to add [chars], filesystem prefix exists
Explanation A file system cound not be added because another file system exists with the same name.
Recommended Action Contact your technical support representative.
%IFS-3-FSMAX : Failed to add [chars], maximum filesystems [dec]
Explanation The router has reached the maximum number of file systems that can be supported at one time.
Recommended Action Contact your technical support representative.
%IFS-3-FS_MISSING_FUNCTIONS : '[chars]' file system missing required functions, not created
Explanation Some file systems require a certain set of function to be present in order to be usable. This file sustem does not support all the mandatory functionality.
Recommended Action Call your technical support representative for assistance.
%IFS-3-FS_STRUCT_ERROR : Data does not match expected internal representation
Explanation A mismatch exists between the representation of data extracted from the filesystem and the expectation of its formatting. This may occur when running in a dual-RP environment, with different IOS versions running on the two RPs.
Recommended Action Ensure both RPs are running the IOS same version, if running in a dual-RP environment. If not, call your technical support representative for assistance.
%IFS-4-FILEMAX : Failed to open [chars], maximum open files [dec])
Explanation The router has reached the maximum number of files that may be open at one time.
Recommended Action Close some files and try again. If this messages recurs, contact your technical support representative.
INTERFACE_API
%INTERFACE_API-1-NAMESTRTOOLONG : Interface name [chars].[int] exceeded maximum allowed length [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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%INTERFACE_API-1-NOMORE_HASWIDBS : No more IDBS can be created. The maximum allowed numbers, [int], has been reached on Standby Please force redundancy mode to RPR if full Active Capacity, [int], is needed
Explanation No more Software IDB numbers can be Created. The maximum allowed numbers has been reached for this High Available System.
Recommended Action None
%INTERFACE_API-1-NOMOREHWIDBNUMBERS : No more hardware IDB numbers can be issued. The maximum allowed numbers, [dec], has been reached for this platform.
Explanation No more hardware IDB numbers can be issued. The maximum allowed numbers has been reached for this platform.
Recommended Action In addition to the following, copy the information from <CmdBold>show idb<NoCmdBold>. LOG_STD_ACTION
%INTERFACE_API-1-NOMORESWIDB : No more SWIDB can be allocated, maximum allowed [dec]
Explanation No more Interfaces can be created because the maximum number of SWIDB allowed for this platform has been reached
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%INTERFACE_API-1-NOMORESWIDBNUMBERS : No more software IDB numbers can be issued. The maximum allowed numbers, [dec], has been reached for this platform.
Explanation No more software IDB numbers can be issued. The maximum allowed numbers has been reached for this platform.
Recommended Action In addition to the following, copy the information from <CmdBold>show idb<NoCmdBold>. LOG_STD_ACTION
%INTERFACE_API-3-BADIDBSTATUSCHANGECALL : Invalid function call at interrupt level.
Explanation An internal function was illegally called at interrupt level. This error might be caused by incorrectly coded creation or deletion of an interface, or during an OIR operation.
Recommended Action Perform a search of the Bug Toolkit, BUG_TOOLKIT . If you still require assistance, copy the error message exactly as it appears on the console or in the system log. Issue the <CmdBold>show tech<NoCmdBold> command and copy the output. If you performed any actions before the error message appeared, make a note of this. Open a case with the Technical Assistance Center via the Internet TAC_CASE_OPEN , or contact your Cisco technical support representative and provide the representative with the gathered information.
%INTERFACE_API-3-CANNOTGETMTU : Error [dec] received while getting MTU: [chars]. Using default [int]
Explanation A software error has occurred while attempting to retrieve the MTU value from the interface.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%INTERFACE_API-3-HWIDBQREENTRANT : [chars] in progress of being inserted/removed, ignoring new request to [chars]
Explanation A software error has occurred while attempting to insert or remove the interface into the system as there's already another attempt in progress to insert or remove this interface. The first attempt must complete before a new attempt can be started. The user should retry this operation at a later time.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%INTERFACE_API-3-IFNUMTOIDBERROR : Error occurred while using the ifnum to idb table for interface [chars], if number [dec], during [chars]
Explanation A software error has occurred. This message is displayed when an operation on the if_number to idb mapping table could not be performed successfully.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%INTERFACE_API-3-INVALIDSUBBLOCKPARAMETERS : Invalid subblock parameters for [chars] were supplied.
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 idb and show tech-support commands to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit BUG_TOOLKIT . If you still require assistance, open a case with the Technical Assistance Center via the Internet TAC_CASE_OPEN , or contact your Cisco technical support representative and provide the representative with the gathered information.
%INTERFACE_API-3-NOADDSUBBLOCK : The [chars] subblock named [chars] was not added to [chars]
Explanation A software error has occured, this message is displayed when IDB subblocks cannot be added.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%INTERFACE_API-3-NODESTROYSUBBLOCK : The [chars] subblock named [chars] was not removed
Explanation A software error has occured, this message is displayed when IDB subblocks cannot be removed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%INTERFACE_API-3-NOSUBBLOCK : [chars] subblock does not exist on 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%INTERFACE_API-3-SUBNUMDBERR : subnum [hex] error in [chars]
Explanation A software error has occured, this message is displayed when a problem has occured with a sub_number db.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%INTERFACE_API-4-BADPAKINPUT : pak->if_input is not initialized
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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%INTERFACE_API-4-BADPAKOUTPUT : pak->if_output is not initialized on interface [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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%INTERFACE_API-4-BADPOINTER : Function [chars] detected an invalid [chars] pointer of %08lX, ignoring
Explanation A software error has occurred, this message is displayed when an invalid pointer is detected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%INTERFACE_API-4-BADSWIDB : [chars] may not be referencing the correct swidb
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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%INTERFACE_API-4-TBLERROR : A error occurred while using the Index Table utility for [chars].
Explanation A software error has occurred; this message is displayed when an Index table feature could not be used successfully.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
IKEV2
%IKEV2-1-SEND_COOKIE_CHALLENGE : NULL
Explanation None
Recommended Action None
%IKEV2-3-NEG_ABORT : NULL
Explanation None
Recommended Action None
%IKEV2-5-INCREASE_PEER_WINDOW_SIZE : NULL
Explanation None
Recommended Action None
%IKEV2-5-IPSEC_COLLISION : NULL
Explanation None
Recommended Action None
%IKEV2-5-OSAL_INITIATE_TUNNEL : NULL
Explanation None
Recommended Action None
%IKEV2-5-RECV_CONNECTION_REQUEST : NULL
Explanation None
Recommended Action None
%IKEV2-5-SA_DOWN : NULL
Explanation None
Recommended Action None
%IKEV2-5-SA_REJECTED_LIMIT_REACHED : NULL
Explanation None
Recommended Action None
%IKEV2-5-SA_REJECTED_RESOURCE_LOW : NULL
Explanation None
Recommended Action None
%IKEV2-5-SA_UP : NULL
Explanation None
Recommended Action None
IM
%IM-0-EVENT_LIBRARY :
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.
%IM-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.
%IM-2-ACTIVATION_STATE : [chars] '[chars]' [chars] [chars]
Explanation The activation state of the named virtualization service has changed as notified by IOx-manager.
Recommended Action In the failed case, check IOx-manager's logs for the cause of the failure. In the successful case, this notification can be ignored.
%IM-2-ALLOC_VIRT_INST_RCS : Virtualization Service[chars]
Explanation A memory allocation request failed to allocate a data structure required to activate the virtualization service.
Recommended Action Enable the IOx-manager trace logs and repeat the activation of the virtualization service. Collect the IOx-manager logs and scan them for the cause.
%IM-2-CPUSHARES_LIMIT : Virtualization Service[chars]
Explanation The virtualization service machine definition file is requesting more CPU shares than the system has available for virtualization services.
Recommended Action Deactivate any other virtualization services to free up CPU share resources and activate this virtualization service. If that does not address the problem, then enable the IOx-manager trace logs and repeat the activation of the virtualization service. Collect the IOx-manager logs and scan them for the cause.
%IM-2-DEACT_FOR_ISSU : [chars] Max ([int]s)
Explanation An ISSU event is pending. Any active VMs will be automatically deactivated to allow ISSU preprocessing to validate the environment. Any ISSU-deactivated VMs will be automatically restarted if the ISSU is cancelled.
Recommended Action None. Allow the ISSU to continue and the VMs will restart when the ISSU completes or cancel the ISSU and IOx-manager will automatically
%IM-2-DISK_IMAGE_PATH : Virtualization Service[chars]
Explanation The virtualization service machine definition file contains an invalid disk image path for one of the disk devices. This may be a Harddisk, CDROM or USB storage device.
Recommended Action Enable the IOx-manager trace logs and repeat the activation of the virtualization service. Collect the IOx-manager logs and scan them for the cause.
%IM-2-FIND_VIRT_INST_ENTRY : Failed to find virtualization service with id [int] in the IOx-manager list
Explanation The virtualization service with the ID named could not be located in the IOx-manager list.
Recommended Action Enable the IOx-manager trace logs and repeat the activation of the virtualization service. Collect the IOx-manager logs and scan them for the cause.
%IM-2-GENERAL_FAILURE : Virtualization Service[chars]
Explanation The named virtualization service has triggered the log. Please interpret the log in the context of the virtualization services.
Recommended Action No action is required
%IM-2-GUESTSHELL_ENABLED : The guest shell has been enabled. The command '[chars]' may be used to access it, '[chars] destroy' to remove it.
Explanation Informs the user that the guest shell virtualization service has been enabled (which is done by default).
Recommended Action The user may use or remove the guest shell with the commands specified.
%IM-2-HA_STATE : [chars] [chars] [chars] [chars]
Explanation IOx-manager tries to detect the role/slot of various nodes on HA events from the platform. If any of those event callbacks fail, this notification would be raised.
Recommended Action In the failed case, check IOx-manager's logs for the cause of the failure. Check for the HA event error msg and root cause the same.
%IM-2-HA_SWITCHOVER_STATE : [chars] [chars] [chars] [chars]
Explanation IOx-manager HA switchover state related messages for a virtual-service whilst it is being recovered on newly active RP after a HA switchover.
Recommended Action In the failed case, check IOx-manager's logs for the cause of the failure. Check for the HA event error msg and root cause the same.
%IM-2-HA_SYNC_ERR : [chars] '[chars]' [chars]
Explanation The ha-sync persistent storage disk for the virtualization service cannot be watched for sync to standby RP.
Recommended Action Collect the IOx-manager logs and scan them for the cause.
%IM-2-HA_SYNC_THREAD_STATE : HA remote sychronize thread has failed and exited.
Explanation IOx-manager tries to remote sync the OVA repository to all online nodes using a separate thread. If that thread fails, this notification would be raised.
Recommended Action In the failed case, check IOx-manager's logs for the cause of the failure. Check for the pthread error msg and root cause the same.
%IM-2-INITIALIZATION_FAILED :
Explanation Initialization of IOx Manager process failed.
Recommended Action Review ioxman 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.
%IM-2-INSTALL_FAILURE : Virtualization Service[chars]
Explanation The installation of the virtualization service failed.
Recommended Action Enable the IOx-manager trace logs and repeat the installation of the virtualization service. Collect the IOx-manager logs and scan them for the cause.
%IM-2-INSTALL_LOG : [chars] [chars] [chars] [chars]
Explanation The installation log of the named virtualization service, is to provide more information about long running operation, that could affect the control of CLI
Recommended Action No action is required
%IM-2-INSTALL_MEDIA_RETRY : VM install media still unavailable.[chars]
Explanation The install media was not detected. Waiting for udev to complete install media(harddisk) detection.
Recommended Action After IOx-manager exceeds the maximum retry limit, verify if install media (harddisk) is accessible and retry the installation again.
%IM-2-INSTALL_STATE : [chars] '[chars]'[chars] [chars]
Explanation The installation state of the named virtualization service has changed as notified by IOx-manager.
Recommended Action In the failed case, check IOx-manager's logs for the cause of the failure. In the successful case, this notification can be ignored.
%IM-2-INVALID_ACT_MSG : Virtualization Service[chars]
Explanation The virtualization service activate message was received, however, the data it contained could not be interpreted
Recommended Action Enable the IOx-manager trace logs and repeat the activation of the virtualization service. Collect the IOx-manager logs and scan them for the cause.
%IM-2-INVALID_DEACT_MSG : Failed to process virtualization service deactivate message
Explanation The virtualization service deactivate message was received, however, the data it contained could not be interpreted
Recommended Action Enable the IOx-manager trace logs and repeat the activation of the virtualization service. Collect the IOx-manager logs and scan them for the cause.
%IM-2-INVALID_UNPROV_MSG : Failed to process virtualization service unprovision message
Explanation The virtualization service unprovision message was received, however, the data it contained could not be interpreted
Recommended Action Enable the IOx-manager trace logs and repeat the activation followed by deactivation and then unprovision of the virtualization service. Collect the IOx-manager logs and scan them for the cause.
%IM-2-IOX_INST_CRIT : IOX SERVICE [chars] LOG: [chars]
Explanation The named virtual service has triggered the log. Please interpret the log in the context of the virtual services.
Recommended Action No action is required
%IM-2-IOX_INST_LOG_UNTHROTTLE : Failed to unthrottle the log for IOX service [chars]
Explanation The named IOX service had sent overwhelming sys log messages and its log had been throttled as a result, but system has failed to unthrottle it for some reason.
Recommended Action For debugging collect the ioxman logs and scan them for the cause.
%IM-2-MEMORY_LIMIT : Virtualization Service[chars]
Explanation The virtualization service machine definition file is requesting more memory than the system has available for virtualization services.
Recommended Action Enable the IOx-manager trace logs and repeat the activation of the virtualization service. Collect the IOx-manager logs and scan them for the cause.
%IM-2-MOVE_STATE : [chars] '[chars]' [chars] [chars]
Explanation The move of the core or log file of the named virtualization service has as been successful or failed as notified by IOx-manager.
Recommended Action In the failed case, check IOx-manager's logs for the cause of the failure. In the successful case, this notification can be ignored.
%IM-2-NETWORK_CONFIG_ERROR : Virtualization Service[chars]
Explanation A network configuration error has been detected for the named virtualization service.
Recommended Action No action is required
%IM-2-RESET_FORCE : Virtualization Services non-recoverable reset command processed
Explanation A 'virtualization service reset force' command has been entered and processed. This action initiates a cleanup of last resort. Occasionally a VM will get into an unrecoverable state that prevents it from activating but also from uninstalling. This is a rare event but when it happens the only resort may be to remove the .conf control file and reboot, which forces a cleanup of all previously installed VM files and artifacts. Note that once this command is used, current VMs are considered to be in an unstable or unpredictable state, and all future install, uninstall, upgrade, and activation commands will be blocked.
Recommended Action Once the command is entered and accepted, there is no recourse but to restart the system.
%IM-2-RESIZE_OPER_STATE : Virtualization service '[chars]' [chars][chars] to '[int]' [chars]
Explanation IOx-manager attempts to resize various VM parameters like rootfs size, CPU share, memory if requested by user. Success/failure status messages for these resize operations are communicated by this syslog.
Recommended Action In the failed case, check IOx-manager's logs for the cause of the failure. Check for the HA event error msg and root cause the same.
%IM-2-RSYNC_STATE : [chars] [chars] [chars] [chars]
Explanation IOx-manager tries to remote sync the virtual-instance configuration file and the OVA repository to all online nodes. If rsync fails even after consecutive retries, this notification would be raised.
Recommended Action In the failed case, check IOx-manager's logs for the cause of the failure. Check for the rsync error code and root cause the same.
%IM-2-START_FAILED : Virtualization Service[chars]
Explanation The named virtualization service failed to start.
Recommended Action Enable the IOx-manager trace logs and repeat the activation of the virtualization service. Collect the IOx-manager logs and scan them for the cause.
%IM-2-UNINSTALL_ALL_VMS : All Virtualization Services are being uninstalled [chars][chars] [chars]
Explanation All virtualization services are being uninstalled by IOx-manager.
Recommended Action Examine the reason given as to why all virtualization services are being uninstalled for more information. If the reason indicated is due to some error condition, check IOx-manager's logs for the cause of the failure.
%IM-2-UPGRADE_LOG : [chars] [chars] [chars] [chars]
Explanation The upgrade log of the named virtualization service, is to provide more information about long running operation, that could affect the control of CLI
Recommended Action No action is required
%IM-2-VCPU_INVALID : Virtualization Service[chars]
Explanation The virtualization service machine definition file is requesting invalid VCPU value.
Recommended Action Enable the IOx-manager trace logs and repeat the activation of the virtualization service. Collect the IOx-manager logs and scan them for the cause.
%IM-2-VCPU_LIMIT : Virtualization Service[chars]
Explanation The virtualization service machine definition file is requesting more VCPUs than the system has reserved for virtualization services.
Recommended Action Enable the IOx-manager trace logs and repeat the activation of the virtualization service. Collect the IOx-manager logs and scan them for the cause.
%IM-2-VIRT_INST_DISK : Virtualization Service[chars]
Explanation The virtualization service requires Disk Storage in excess of the Free Disk Storage available to virtualization services.
Recommended Action Enable the IOx-manager trace logs and repeat the activation of the virtualization service. Collect the IOx-manager logs and scan them for the cause.
%IM-2-VIRT_INST_LOG_UNTHROTTLE : Failed to unthrottle the log for virtualization service [chars]
Explanation The named virtualization service had sent overwhelming sys log messages and its log had been throttled as a result, but system has failed to unthrottle it for some reason.
Recommended Action For debugging collect the iox-manager logs and scan them for the cause.
%IM-2-VIRT_INST_MEMORY : Virtualization Service[chars]
Explanation The virtualization service requires physical memory in excess of the free memory available to virtualization services.
Recommended Action Enable the IOx-manager trace logs and repeat the activation of the virtualization service. Collect the IOx-manager logs and scan them for the cause.
%IM-2-VIRT_INST_MGMT_INTERFACE : Virtualization service [chars] has no management interface defined but it is configured in CLI.
Explanation A management interface is configured but none is defined.
Recommended Action Deactivate the virtualization service, remove the management interface configuration CLI, and reactivate the virtual-service.
%IM-2-VIRT_INST_STATE : Virtualization Service[chars]
Explanation The named virtualization service has failed. It is no longer running either because the guest OS has failed, the guest OS has shut down the machine or the emulator has failed.
Recommended Action An attempt at restarting the virtualization service can be made from the IOS configuration by doing a no activate/activate. For debugging collect the IOx-manager logs and scan them for the cause.
%IM-3-IOX_INST_ERR : IOX SERVICE [chars] LOG: [chars]
Explanation The named IOX service has triggered the log. Please interpret the log in the context of the IOX services.
Recommended Action No action is required
%IM-3-PSS_ERR : Purpose: [chars], URI: [chars], errcode: [dec]
Explanation Persistent Storage Service handling error
Recommended Action Collect the IOx-manager logs and scan them for the cause.
%IM-3-PSS_SNAPSHOT_ERR : Source URI: [chars], Destination URI: [chars], errcode: [dec]
Explanation Persistent Storage Service snapshot error
Recommended Action Collect the IOx-manager logs and scan them for the cause.
%IM-3-SDWRAP_ERR : Description: [chars], errcode: [dec]
Explanation Debug infrastructure error
Recommended Action Collect the IOx-manager logs and scan them for the cause.
%IM-4-HA_SYNC_NEEDED : If using the guest shell, please use 'guestshell sync' if you want to preserve state on standby in case of supervisor switchover
Explanation Message notifying user that he needs to manually synchronize the Virtualization service contents to standby supervisor in order to preserve these contents in case of a supervisor switchover. Currently only applicable to the guest shell
Recommended Action User can type the 'guestshell sync' command on active supervisor to synchronize it's contents to the standby supervisor if desired.
%IM-4-IOX_INST_WARN : IOX SERVICE [chars] LOG: [chars]
Explanation The named IOX service has triggered the log. Please interpret the log in the context of the IOX services.
Recommended Action No action is required
%IM-4-WATCHDOG_TIMER : [chars] '[chars]' [chars] [chars]
Explanation The watchdog timer configured for the named virtual service has expired.
Recommended Action Check any logs produced by the virtualization service to determine the cause.
%IM-5-AUX : Virtualization Service[chars]
Explanation The AUX login to a virtualization service may allow the user access to system functions that may not have been tested or may interact with the system in unintended ways. Use with caution.
Recommended Action No action is required
%IM-5-IOX_INST_NOTICE : IOX SERVICE [chars] LOG: [chars]
Explanation The named IOX service has triggered the log. Please interpret the log in the context of the IOX services.
Recommended Action No action is required
%IM-5-PERMISSION_DENIED : Virtualization Service '[chars]' is not owned by client IOSd
Explanation An attempt was made to modify a virtual-service that is not owned by by the client. The request was rejected.
Recommended Action No action is required.
%IM-6-IOX_INST_INFO : IOX SERVICE [chars] LOG: [chars]
Explanation The named IOX service has triggered the log. Please interpret the log in the context of the IOX services.
Recommended Action No action is required
%IM-7-IOX_INST_DEBUG : IOX SERVICE [chars] LOG: [chars]
Explanation The named IOX service has triggered the log. Please interpret the log in the context of the IOX services.
Recommended Action No action is required
IMGR
%IMGR-0-FIPS_CPP_CLIENT_BYPASS_TEST : CPP Client FIPS bypass test failed for [chars].
Explanation Forwarding Manager CPP client IPSEC bypass test failed. This could be due to a hardware malfunction or a software defect.
Recommended Action If the problem persists reboot the forwarding processor (ESP).
%IMGR-0-FIPS_FMFP_BYPASS_TEST : NIST bypass test failed for [chars].
Explanation Forwarding Manager IPsec component detected a discrepancy when adding or deleting a security sensitive object. This could be due to a hardware or software resouce limitation or a software defect.
Recommended Action Check the logs for information on the relevant object download states. Remove the object or a parent object in question. If the problem persists reboot the forwarding processor (ESP).
%IMGR-0-FIPS_FMFP_N2_SEVERE_ERR_FAIL : Cryptographic coprocessor severe failure: [chars].
Explanation Cryptographic coprocessor critical operation failed. Further data processing on ESP is halted
Recommended Action forwarding processor (ESP) is rebooted automatically. no action needed
%IMGR-6-FIPS_FMFP_CRNG_TEST : continuous [chars]approved RNG test failed.
Explanation Forwarding Manager IPsec component detected two identical random number sequences. This could be due to a hardware mulfunction or a software defect.
Recommended Action If the problem persists reboot the forwarding processor (ESP).
%IMGR-6-FIPS_FMFP_KAT_TEST : power up cryptographic self-test didnot run to completion: [chars].
Explanation Forwarding Manager power up known answer self-test (KAT) failed. This could be due to a hardware malfunction or a software defect.
Recommended Action If using ipsec, reboot the forwarding processor (ESP).
%IMGR-6-FIPS_FMFP_N2_ERR_FAIL : Cryptographic coprocessor non-critical failure: [chars].
Explanation Cryptographic coprocessor non-critical operation failed. If the problem persists reboot the forwarding processor(ESP)
Recommended Action If the problem persists reboot the forwarding processor (ESP).
%IMGR-6-FIPS_FMFP_OLAP_TEST : FIPS-approved RNG key seed and state overlap.
Explanation Forwarding Manager IPsec component detected an overlap in FIPS-approved RNG key seed and state. This could be due to a hardware mulfunction or a software defect.
Recommended Action If the problem persists reboot the forwarding processor (ESP).
%IMGR-6-FMFP_IPSEC_CRYPTO_CTRL_THROTTLED : IPsec Control Plane Overload Crypto Device: [chars].
Explanation This ESP crypto device is overloaded.
Recommended Action May need to config platform ipsec control-plane medium|heavy
%IMGR-6-FMFP_IPSEC_MIN_MTU_INFO : MTU smaller than minimum IPSec MTU, [chars].
Explanation Minimum MTU supported by crypto processor is 256B, MTU lower than 256B is set to 256B
Recommended Action No action needed
%IMGR-6-FMFP_IPSEC_UNSUPPORTED_CIPHER : Cipher [chars] is not supported on this ESP.
Explanation This ESP does not support this IPSec cipher
Recommended Action No action needed
%IMGR-6-FMFP_KAT_TEST_RESULT : crypto self-test for algorithm: ([chars] ... passed).
Explanation Forwarding Manager power up known answer self-test (KAT) success. This is not an error message
Recommended Action No action needed.
INDXOBJ
%INDXOBJ-3-ADD_ERROR : index add for [chars] failed: [chars]
Explanation index object routine error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%INDXOBJ-3-INTERRUPT : index object routine [chars] called from interrupt context
Explanation inappropriate index object routine called from interrupt routine.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
INFRA
%INFRA-3-INVALID_GPM_ACCESS : Invalid GPM [chars] at [hex] HAL start [hex] HAL end [hex] INFRA start [hex] INFRA [hex] NET [hex], MSGDEF_LIMIT_MEDIUM
Explanation Processing packet went beyond valid packet data, packet was possibly invalid, ppe info and encrypted pkt dump follow
Recommended Action LOG_STD_ACTION
%INFRA-3-INVALID_GPM_ACCESS_DATA :
Explanation Packet associated with previous exception error The packet data has been encrypted
Recommended Action LOG_STD_ACTION
%INFRA-3-INVALID_GPM_ACCESS_INFO : [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex]
Explanation Registers associated with previous exception error
Recommended Action LOG_STD_ACTION
INSTALL
%INSTALL-3-INSTANT_ERROR_MESSAGE : Error Message: [chars]
Explanation This message is used to send a instant erorr message.
Recommended Action No action required.
%INSTALL-3-OPERATION_ERROR_MESSAGE : Failed to [chars] package [chars], Error: [chars]
Explanation This message is used to inform the failure reason.
Recommended Action Please refer to the error message to analyze the cause of failure.
%INSTALL-5-INSTALL_AUTO_ABORT : Install auto abort timer expired: initiating abort
Explanation An install operation has been aborted because the auto abort timer has expired.
Recommended Action No user action is needed. If you want to commit the ISSU upgrade, redo the upgrade. Otherwise, this is an informational message only.
%INSTALL-5-INSTALL_AUTO_ABORT_TIMER_PROGRESS : Install auto abort timer will expire in [dec] seconds
Explanation An install operation will be aborted after specified seconds of time.
Recommended Action No user action is needed. If you want to commit the ISSU upgrade, redo the upgrade. Otherwise, this is an informational message only.
%INSTALL-5-INSTALL_COMPLETED_INFO : Completed [chars] [chars] [chars]
Explanation This message is used to indicate the completion of install operations.
Recommended Action No action required. This is not an error, it is an indication that the system completed this operation.
%INSTALL-5-INSTALL_START_INFO : Started [chars] [chars] [chars]
Explanation This message is used to indicate the beginning of install operations.
Recommended Action No action required. This is not an error, it is an indication that the system is starting this operation.
%INSTALL-5-OPERATION_COMPLETED_INFO : Completed [chars] package [chars]
Explanation This message is used to indicate the completion of operations.
Recommended Action No action required. This is not an error, it is an indication that the system completed the operation.
%INSTALL-5-OPERATION_START_INFO : Started [chars] package [chars]
Explanation This message is used to indicate the beginning of operations.
Recommended Action No action required. This is not an error, it is an indication that the system is starting the operation.
INTERCHASSIS_REDUNDANCY
%INTERCHASSIS_REDUNDANCY-4-STDBY_PRESENT : Removal of standby RP in location [chars] is recommended for inter-chassis redundancy configuration
Explanation Removal of standby RP from the chassis is recommended for inter-chassis redundancy
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
IOMD_INFRA
%IOMD_INFRA-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.
%IOMD_INFRA-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.
%IOMD_INFRA-3-INTR_EVENT : IOMd fast thread event ([dec]).
Explanation IOMd fast thread event
Recommended Action Examine the logs for IOMD. 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/c/en/us/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOMD_INFRA-3-INVALID_BAY_NUM : An invalid bay number is specified in one of the internal APIs. bay=[dec] max_bay=[dec]
Explanation Invalid bay number to find the TDL domain
Recommended Action Examine the logs for IOMD. 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/c/en/us/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOMD_INFRA-3-INVALID_SLOT_NUM : An invalid slot number is specified in one of the internal APIs. slot=[dec] max_slot=[dec]
Explanation Invalid slot number to find the TDL domain
Recommended Action Examine the logs for IOMD. 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/c/en/us/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOMD_INFRA-3-IPCALLOCFAIL : Failed to allocate IPC buffer [chars]
Explanation The IM failed to allocate a buffer for communication with RSP
Recommended Action Examine the logs for IOMD. 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/c/en/us/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOMD_INFRA-3-IPCSENDFAIL : IOMD failed to send a message [chars] reason: [chars]
Explanation IOMD failed to send message to the RP
Recommended Action Examine the logs for IOMD. 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/c/en/us/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOMD_INFRA-3-LINECARDDIAGSFAILED : Module [chars] in Slot [dec] failed online diagnostics. Please use 'show post' for more details
Explanation Online Diag 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 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.
%IOMD_INFRA-4-BADPOINTER : Function [chars] detected an invalid [chars] pointer of %08lX, ignoring
Explanation A software error has occurred, this message is displayed when an invalid pointer is detected.
Recommended Action Examine the logs for IOMD. 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/c/en/us/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOMD_INFRA-4-INTR_OVER_LIMIT : IOMd main thread disabled interrupt for [int] msec.
Explanation IOMd main thread process disabled interrupt too long
Recommended Action Examine the logs for IOMD. 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/c/en/us/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOMD_INFRA-6-TDLMSG_INCOMPATIBLE : Failed to copy message [chars] to buffer, not allowed for current domain.
Explanation Failure to marshal a message indicates an incompatibility \ with the intended recipient.
Recommended Action Examine the logs for IOMD. 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/c/en/us/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
IOSD
%IOSD-3-BIPC_REJECT : Could not accept ipc connection: [chars]
Explanation This error occurs if shell-manager has denied an ipc connection request from IOS.
Recommended Action Check the connection request parameters.
%IOSD-3-TDL_PROPERTIES : Could not set message properties for connection: [chars]
Explanation This error occurs if shell-manager is unable to set message properties for the IOS-sman connection
Recommended Action Check the connection request parameters.
IOSD_INFRA
%IOSD_INFRA-6-IFS_DEVICE_OIR : Device [chars] [chars]
Explanation USB inserted/removed
Recommended Action No action is required.
IOS_LICENSE_IMAGE_APPLICATION
%IOS_LICENSE_IMAGE_APPLICATION-3-FAILED : [chars]
Explanation The ios licensing subsystem failed to create a process/watched boolean etc to watch request from the remote show subsys license commands
Recommended Action please capture the error msg and forward it to the appropriate licensing component
%IOS_LICENSE_IMAGE_APPLICATION-3-UNKNOWN_EVENT : [chars]
Explanation The ios image licensing subsystem received an event which it does not understand or recognizes
Recommended Action please capture the error msg and forward it to the appropriate licensing component
%IOS_LICENSE_IMAGE_APPLICATION-3-UNKNOWN_VERSION : [chars]
Explanation The ios image licensing subsystem received an event for an unknown version of a feature
Recommended Action please capture the error msg and forward it to the appropriate licensing component
%IOS_LICENSE_IMAGE_APPLICATION-6-LICENSE_CONFIG : EULA must be accepted for license level = [chars]
Explanation This is an informational message to inform user that the user needs to reissue the command from an interactive terminal
Recommended Action This is an informational message, no action is required
%IOS_LICENSE_IMAGE_APPLICATION-6-LICENSE_LEVEL : Module name = [chars] Next reboot level = [chars] and License = [chars]
Explanation This is an informational message to display the change in the next reboot license level
Recommended Action This is an informational message, no action is required
%IOS_LICENSE_IMAGE_APPLICATION-6-LICENSE_LEVEL_CONFIG : Please issue 'license boot' config command to make extension license ([chars]) available for use.
Explanation This is an informational message to info user that to make extension license available to support image level, licensing image level needs to be configured
Recommended Action This is an informational message, no action is required
%IOS_LICENSE_IMAGE_APPLICATION-6-NO_LICENSE : [chars] [chars].
Explanation There is no valid license available on the box and we are running on a default feature
Recommended Action please purchase a license to activate required features.
IOSXE_APS
%IOSXE_APS-3-CCCONFIGFAILED : Pair config for interface [chars] Group [dec] failed
Explanation Pair config for interface has failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_APS-3-CONFIG_FAIL : config change for interface [chars] Group [dec] failed
Explanation config for an interface to forwarding plane has failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_APS-3-DOWNLOADFAIL : Unable to download [chars] message to [chars]
Explanation An unexpected condition has occurred which resulted in a configuration not being sent to the reported process.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_APS-3-FLOWCONFIGTOCCFAILED : Flow id to cc for interface [chars] Group [dec] failed
Explanation Flow id to cc for an interface has failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_APS-3-FLOWIDALLOCFAILED : Allocation of APS flow ID with manager failed for interface [chars] group [dec]
Explanation An unexpected condition has occurred that allocation of APS flow ID. failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show interface command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_APS-3-FLOWIDDELETIONFAILED : Deletion of APS flow ID with manager failed for interface [chars] group [dec]
Explanation An unexpected condition has occurred that deletion of APS flow ID.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show interface command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_APS-3-GROUP_CONFIG_FAIL : Group change for interface [chars] Group [dec] failed
Explanation Group change for interface has failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_APS-3-PAIR_CONFIG_FAIL : Pair config for interface [chars] Group [dec] failed
Explanation Pair config for interface has failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
IOSXE_CSLIFS
%IOSXE_CSLIFS-3-ERROR_SETTING : Error setting default file system ([dec])
Explanation There is an error happened after calling function ifs_set_default_directory
Recommended Action Check the csl filesystem
IOSXE_CXSC
%IOSXE_CXSC-3-ACTION : Unknown proposition action ([dec])
Explanation When the proposition was being sent to the data plane, the action was unknown error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_CXSC-3-ALLOC : Failed to allocate message for proposition
Explanation When attempting to program the dataplane with a CXSC proposition object, there was no enough memory to allocate the message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_CXSC-3-BAD_PROPOSITION : Proposition obj corrupt
Explanation When the proposition was being sent to the data plane, the object itself is corrupt.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_CXSC-3-BAD_PROTOCOLPACK : Invalid Protocol Pack object
Explanation When the Protocol Pack was being sent to the data plane, the object's contents were invalid.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_CXSC-3-BAD_SUMMARY : Summary obj corrupt
Explanation When the proposition summary was being sent to the data plane, the object itself is corrupt.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_CXSC-3-FILESYSTEM_ERR : FileSystem Error ([chars]): Unable to Copy File from [chars] to [chars]
Explanation Unable to copy the NBAR Protocol Pack File to the file system for subsequent loading. The system will revert to the previously loaded Protocol Pack.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_CXSC-3-INSUFFICIENT_ALLOC_IOSXE_VER : Insufficent memory allocated for IOSXE version String
Explanation The input IOSXE Version String has insufficient memory to hold the IOSXE Version.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_CXSC-3-INSUFFICIENT_ALLOC_NBAR_VER : Insufficent memory allocated for NBAR Engine Version String
Explanation The input NBAR Engine Version string has insufficient memory to hold the NBAR Engine Version.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_CXSC-3-MESSAGE : Failed to send message for proposition
Explanation When the proposition was being prepared for sending to the data plane, there was an error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_CXSC-3-PLATFORM_TYPE : Unrecognised platform type. CPU ID [dec]
Explanation The platform that the cxsc service is being installed on is not recognised. The most likely cause is that this platform is not supported.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_CXSC-3-RF_INIT : Failed to initialize CXSC Redundancy Facility client
Explanation An unexpected condition occurred where the CXSC Redundancy Facility failed to initialize.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_CXSC-3-STATISTICS_ALLOCATION : Unable to allocate space for statistics
Explanation During initialization, there was failure in the allocation of the memory to gather the statistics. It is non fatal, but after seeing this message, the CXSC subsystem will not be able to gather statistics.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_CXSC-3-STILE_ACTIVATE : Failed to activate NBAR classification: ([dec])
Explanation An unexpected condition occurred where the CXSC NBAR protocol classification failed to activate.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_CXSC-4-DUAL_RP_UNSUPPORTED : Dual RPs are not supported in conjunction with CXSC
Explanation CXSC is not supported in a dual RP environment. To resolve this warning, either unconfigure CXSC or remove the redundant Route Processor.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
IOSXE_EPA
%IOSXE_EPA-3-ACT2_AUTHENTICATION_FAILURE : slot=[dec] subslot=[dec], spa_type=[hex], lc_type=[hex].
Explanation ACT2 dev authentication Failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_EPA-3-AUTONEG_CFG_ERR : interface [chars] autoneg state '[chars]' is incompatible with transciever. Remove '[chars]' to allow the transceiver.
Explanation Autoneg Config is not compatible. Remove autoneg config on the interface to allow the transceiver
Recommended Action Remove the negotiation auto config or reinsert the previously enabled transceiver.
%IOSXE_EPA-3-CREATION_FAILURE : slot=[dec] subslot=[dec], spa_type=[hex], lc_type=[hex].
Explanation Failed to create a SPA object.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_EPA-3-NULL_DEVOBJ_PTR :
Explanation Pointer to a DEVOBJ object is NULL.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_EPA-3-NULL_DEVPSEQ_PTR :
Explanation Pointer to a DEVPSEQ object is NULL.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_EPA-3-NULL_EPA_PTR :
Explanation Pointer to an EPA object is NULL.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_EPA-3-NULL_EPASENSOR_PTR :
Explanation Pointer to a DEVSENSOR object is NULL.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_EPA-3-NULL_FPGA_PTR :
Explanation Pointer to a FPGA object is NULL.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_EPA-3-NULL_PORT_PTR :
Explanation Pointer to a PORT object is NULL.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_EPA-3-NULL_VFT :
Explanation Pointer to a DEVSENSOR object is NULL.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_EPA-3-NULL_VSC_PHY_INFO_PTR :
Explanation Pointer to a VSC PHY INFO object is NULL.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_EPA-3-UNSUPPORTED_XCVR : Transceiver type [chars] is not allowed on spa [chars], port [dec],
Explanation This transceiver is not allowed on the SPA
Recommended Action Consult the documentation and ensure supported transceivers are plugged into the SPA
%IOSXE_EPA-3-XCVR_EC_BWMISMATCH : Trasnsceiver bandwidth is incompatible with Port-channel[dec] allowed bandwidth. Remove 'channel-group [dec]' config for interface [chars] to allow the transceiver
Explanation The interface port into which the transceiver is inserted is part of a Port-channel. The Port-channel has member links whose bandwidth doesn't match with the inserted transceier's bandwidth. Since, port-channel cannot allow heterogenous bandwidth links, this transceiver is not allowed in to the port.
Recommended Action Remove the channel-group config for the port where transceiver is inserted or insert a transceiver whose bandwidth is compatible with the port-channel bandwidth
%IOSXE_EPA-3-XCVR_PROHIBIT : Transceiver is prohibited to come online for interface [chars]
Explanation XCVR is prohibited on the interface
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
IOSXE_ETHERCHAN
%IOSXE_ETHERCHAN-3-LINK_MTU_FAIL : Failure in changing MTU of interface [chars] to port-channel [chars] MTU
Explanation The MTU for the interface mentioned in the message cannot be changed to match the MTU configured on the port channel interface
Recommended Action Remove the link mentioned in the message from the port-channel group
%IOSXE_ETHERCHAN-6-LINK_MTU : Interface [chars] MTU set to port-channel [chars] MTU [dec]
Explanation The MTU for the interface mentioned in the message is changed to match the MTU configured on the port channel interface
Recommended Action No action is required.
IOSXE_EZMENU
%IOSXE_EZMENU-3-VIRT_SRVC_REGISTER : Failed to register '[chars]' with virtual service manager
Explanation An unexpected error has occured while trying to register this virtual service with the virtual service manager. This has prevented the virtual service from being enabled/disabled.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
IOSXE_FMANRP_FPM
%IOSXE_FMANRP_FPM-3-NOSTATUPDATE : Failed to update class-map statistics during periodic update
Explanation A statistics update for a class-map has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_FMANRP_FPM-4-INVALIDACTION : FPM feature action is invalid [dec]
Explanation An unexpected condition has occurred which is due to the invalid action type when trying to bind FPM action with target class group.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_FMANRP_FPM-4-INVALIDLENTYPE : Field length type in PHDF file is invalid
Explanation An unexpected condition has occurred which is due to the invalid field length type in PHDF file.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_FMANRP_FPM-4-INVALIDMATCHTYPE : FPM match type is invalid [dec]
Explanation An unexpected condition has occurred which is due to the invalid FPM match type in one of FPM class-map filter match entry
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
IOSXE_FMANRP_OBJID2
%IOSXE_FMANRP_OBJID2-3-DUPCREATE : Duplicate forwarding object creation obj_handle [hex], type [int], existing obj_id [hex], type [int]
Explanation An unexpected condition has occurred which results in duplicate forwarding object creation with different object types.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
IOSXE_FMANRP
%IOSXE_FMANRP-3-EPOCHTDLMSGMARSHAL : Failed to copy epoch TDL message to IPC buffer, epoch number [dec]
Explanation This operation to build a TDL messages for epoch message has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_FMANRP-3-MSGENQERR : Unable to enqueue IPC messages to IOS IPC queue. Message: [chars].
Explanation An unexpected condition has occurred while IOS trying to enqueue IPC message to IOS IPC queue in order to send the message to Forwarding Manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_FMANRP-3-MSGMARSHALERR : Unable to copy IPC messages into transport buffer. Message: [chars]
Explanation An unexpected condition has occurred while IOS trying to copy IPC message to transport buffer in order to send the message from IOSd to Forwarding Manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_FMANRP-4-MSGDISPATCH : Unable to dispatch received TDL message '[chars]' from Forwarding Manager. LUID: [chars]
Explanation An unexpected condition has occurred while IOS trying to dispatch the TDL message handler functions for received TDL messages from Forwarding Manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_FMANRP-4-MSGDISPATCHNULL : TDL messages NULL from IOS.
Explanation An unexpected condition has occurred while IOS trying to dispatch the TDL message handler functions for received TDL messages from Forwarding Manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_FMANRP-4-MSGIPCERR : Unable to process received IPC messages from Forwarding Manager, error: [chars].
Explanation An unexpected condition has occurred while IOS trying to process received IPC message from Forwarding Manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_FMANRP-4-MSGNONTDLSTATSERR : Unable to process received non-TDL stats message from Forwarding Manager, error: [chars] ([dec]).
Explanation An unexpected condition has occurred while IOS trying to process received non-TDL stats message from Forwarding Manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
IOSXE_FMANRP_ADJ
%IOSXE_FMANRP_ADJ-3-ENCSIZE : Invalid encap length [dec] which is larger than max allowed [dec] bytes
Explanation An unexpected condition has occurred which is due to invalid adjacency encapsulation size being larger than the maximum value allowed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_FMANRP_ADJ-3-ENQUEFAIL : Unable to send [chars] [chars] message to Forwarding Manager Process
Explanation An unexpected condition has occurred which resulted in a configuration not being sent to the Forwarding Manager Processs.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_FMANRP_ADJ-3-NOADJ : Adjacency entry is null
Explanation An unexpected condition has occurred which is due to the absence of an adjacency entry structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show adjacency command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_FMANRP_ADJ-3-NOFIBHWIDB : FIB Interface [chars] is null
Explanation An unexpected condition has occurred which is due to the absence of a FIB interface structure.
Recommended Action LOG_STD_SH_CMD_ACTION(show adj)
IOSXE_FMANRP_CCE
%IOSXE_FMANRP_CCE-3-CCE_CLASS_CREATE : Unable to create class [int].[int]
Explanation An error occured when trying to create a class-map.
Recommended Action LOG_STD_SH_CMD_ACTION(show policy-map [type <policy type> <name>])
%IOSXE_FMANRP_CCE-3-CCE_FILTER_OVERFLOW : Filter list overflow at type [chars]
Explanation An internal error occured when trying to build class-map information for one of the classes in a policy-map.
Recommended Action LOG_STD_SH_CMD_ACTION(show class-map [type <class type> <name>])
%IOSXE_FMANRP_CCE-3-CCE_INVALID_FILTER_RELN : Invalid filter relation [int]
Explanation An internal error occured when trying to build class-map information for one of the classes in a policy-map.
Recommended Action LOG_STD_SH_CMD_ACTION(show policy-map [type <policy type> <name>])
%IOSXE_FMANRP_CCE-4-CCE_NESTED_CLASS_LIMIT : Nested class [dec] layers cannot exceed 4
Explanation When configure nested classes as match statements, the total levels of nested classes cannot exceed 4 layers
Recommended Action LOG_STD_SH_CMD_ACTION(show class-map [type <class type> <name>])
%IOSXE_FMANRP_CCE-4-CCE_STACK_LIMIT : Failed to create class [dec] filter list
Explanation An operation to send a filter list to the forwarding processor for a particular class has failed due to a resource issue. This may imply that the notification was dropped.
Recommended Action LOG_STD_SH_CMD_ACTION(show class-map [type <class type> <name>])
IOSXE_FMANRP_CEF
%IOSXE_FMANRP_CEF-3-ENQUEFAIL : Unable to send [chars] [chars] message to Forwarding Manager Process
Explanation An unexpected condition has occurred which resulted in a configuration not being sent to the Forwarding Manager Processs.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_FMANRP_CEF-3-NOFIB : FIB entry is null
Explanation An unexpected condition has occurred which is due to the absence of a FIB entry structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show ip cef command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_FMANRP_CEF-3-NOFIBIDB : FIB interface is null
Explanation An unexpected condition has occurred which is due to the absence of a FIB interface structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show ip cef command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_FMANRP_CEF-3-NOFIBPUSHCNT : FIB push counter is null
Explanation An unexpected condition has occurred which is due to the absence of a FIB push counter structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show ip cef command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_FMANRP_CEF-3-NOFIBSB : FIB SB entry is null
Explanation An unexpected condition has occurred which is due to the absence of a FIB SB entry structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show ip cef command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_FMANRP_CEF-3-NOFIBTABLE : FIB table is null
Explanation An unexpected condition has occurred which is due to the absence of a FIB table structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show ip cef command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_FMANRP_CEF-3-NONATADDR : NAT address is null
Explanation An unexpected condition has occurred which is due to the absence of an NAT address.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show ip alias command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_FMANRP_CEF-3-ROUTEMSGMARSHAL : Failed to copy route essage to IPC buffer for prefix [chars]/[dec] -[chars]
Explanation This operation to build a TDL messages for route download has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_FMANRP_CEF-4-UPDFRAGSTATSERR : Update IP Fragmentation statistics error
Explanation An unexpected condition has occurred when updating fragmentation statistics
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_FMANRP_CEF-4-UPDREASSSTATSERR : Update IP Reassembly statistics error
Explanation An unexpected condition has occurred when updating reassembly statistics
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_FMANRP_CEF-4-UPDSTATSERR : Update CEF statistics error
Explanation An unexpected condition has occurred when updating cef statistics
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
IOSXE_FMANRP_OBJID
%IOSXE_FMANRP_OBJID-5-DUPCREATE : Duplicate forwarding object creation obj_handle [hex], type [int], existing obj_id [hex], type [int]
Explanation An unexpected condition has occurred which results in duplicate forwarding object creation.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
IOSXE_FMANRP_RTMAP
%IOSXE_FMANRP_RTMAP-3-INVALID_LIST : NULL
Explanation An internal list structure has been detected as invalid.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_FMANRP_RTMAP-3-RTMAPNULL : The route-map structure for [chars] is null
Explanation An unexpected condition has occurred which is due to the absence of a route-map data structure.
Recommended Action show route-map
%IOSXE_FMANRP_RTMAP-3-RTMAP_UNSUPPORTED : Routemap ([chars]) contain unsupported match/set clause, ignored
Explanation A map contains unsupported match or set clause
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_FMANRP_RTMAP-4-UNKOWNCLIANT : Unknown client type [dec] received
Explanation An unexpected known client type is received for route-map download.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
IOSXE_FMANRP_URPF
%IOSXE_FMANRP_URPF-3-INVALIDIFHDL : Invalid interface handle [int] for interface (number= [int], swidb= [hex], name= [chars])
Explanation An unexpected condition has occurred which is due to an invalid interface handle
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_FMANRP_URPF-4-NOV4SWIDB : v4 sub-interface is null
Explanation An unexpected condition has occurred which is due to the absence of a v4 swidb structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show ip interface command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_FMANRP_URPF-4-NOV6SWIDB : v6 sub-interface is null
Explanation An unexpected condition has occurred which is due to the absence of a v6 swidb structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show ipv6 interface command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_FMANRP_URPF-4-UPDV4STATSERR : Update v4 URPF statistics error
Explanation An unexpected condition has occurred when updating v4 URPF statistics
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show ip interface <name> command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_FMANRP_URPF-4-UPDV6STATSERR : Update v6 URPF statistics error
Explanation An unexpected condition has occurred when updating v6 URPF statistics
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show ipv6 interface <name> command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
IOSXE_FMANRP_ZONES
%IOSXE_FMANRP_ZONES-3-NOSTATUPDATE : Failed to update zone-pair statistics during periodic update (zone [chars], class [int])
Explanation A statistics update for a zone-pair has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
IOSXE_INFRA
%IOSXE_INFRA-2-FATAL_NO_PUNT_KEEPALIVE : Keepalive not received for [int] seconds resetting
Explanation Punt Inject keepalive message was not received
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_INFRA-3-APP_SESS_OPEN_FAILED : An attempt to open [chars] with handle number [dec] has failed ([dec])
Explanation Application session between processes failed to estabish.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_INFRA-3-BSO_MSG_CACHE_ERR : BSO mmessage query cache update error
Explanation BSO mmessage query cache update error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_INFRA-3-BSO_MSG_HDR_LENGTH_ERR : BSO message header length [int] is incorrect
Explanation BSO message header length is incorrect
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_INFRA-3-BSO_MSG_HDR_MSGTYPE_ERR : BSO message header msgtype [int] is incorrect
Explanation BSO message header msgtype is incorrect
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_INFRA-3-BSO_MSG_UNMARSHAL_ERR : BSO message unmarshalling has failed
Explanation BSO message unmarshalling has failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_INFRA-3-CONSOLE_DBUG_DROP : System dropped [dec] bytes of console debug messages.
Explanation Debugging messages are being generated faster than they can be displayed on the console. The messages can not be guaranteed to be seen so this message replaces the lost messages.
Recommended Action Consider using conditional debugging or turning off console logging.
%IOSXE_INFRA-3-CYAN_API_ERROR : Failed to retrieve platform dependent value of [chars] (err=[dec])
Explanation CYAN API function failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_INFRA-3-IFS_DFLT_FS_REG_FAIL : Unable to set [chars] as a default file system.
Explanation IOSXE's platform dependent code failed to register the default file system.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_INFRA-3-IFS_EXTLINK_ADD_FAIL : Could not add filesystem [chars] to IFS links
Explanation Attempt to add filesystem root to allow for links failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_INFRA-3-IFS_INIT_HIDDEN_FAIL : IOSXE shim layer initialization failed: Can not create receiving queues
Explanation IOSXE IOS shim layer initialization of hidden path watch failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_INFRA-3-IFS_UDEV_REMOVE_FAIL : Could not remove udev device [chars]
Explanation Attempt to remove udev device failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_INFRA-3-INJECT_EMBEDDED_HDR_LENGTH_ERR : Can't allot space needed for embedded inject hdr size [int] exceeds limit
Explanation Can't allot space needed for embedded inject header, exceeds pak header space
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_INFRA-3-INJECT_FEATURE_ESS_ERR : ESS segment not found, type [dec] hdl [hex]
Explanation Packets to be injected to an unsupported ESS segment
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_INFRA-3-INJECT_GSB_CTL_INIT_FAIL : Inject adjacency subblock init failed
Explanation Adj subblock control or register failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_INFRA-3-INJECT_HDR_LENGTH_ERR : Inject hdr size [int] exceeds limit
Explanation Inject header length exceeds pak header space
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_INFRA-3-INJECT_NO_IF_OUTPUT_ERR : Output intf is NULL, [chars]
Explanation Output intf is requred to proceed, else skip the feautre
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_INFRA-3-INVALID_ERRMSG : Error message type [dec] not defined
Explanation Error message type used is not defined in IOSXE infrastruction
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_INFRA-3-INVALID_RUNTIME_IDX : Thread runtime index [dec] is not valid
Explanation Export the thread's running time failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_INFRA-3-PUNT_ADDR_RES_ENCAP_ERR : Punted address resolution packet with unknown encap [chars]
Explanation Punted packet for ARP/ND with encap not supported
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_INFRA-3-PUNT_INCOMP_WRONG_ADJID : Punted address resolution packet linktype [chars], adj-id [dec] is with linktype [chars]
Explanation CPP needs to punt incomplete adjacency for resolution by specifying the adjacency-id, but the included adjacency-id does not match the incomplete adjacency this packet triggered.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_INFRA-3-PUNT_KEEPALIVE_LOG_ERR_ALLOC_CSB : Failed to allocate a csb
Explanation Can't allocate a csb when generating punt err log
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_INFRA-3-PUNT_KEEPALIVE_LOG_ERR_ALLOC_TTY : Failed to allocate a tty
Explanation Can't allocate a TTY when generating punt err log
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_INFRA-3-PUNT_KEEPALIVE_LOG_ERR_OPEN_FILE : Failed to open file: [chars]
Explanation Failed to open file when generating punt err log
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_INFRA-3-PUNT_KEEPALIVE_LOG_ERR_PARSE_CMD : Failed to parse command: [chars]
Explanation Failed to parse a command when generating punt err log
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_INFRA-3-PUNT_KEEPALIVE_LOG_ERR_WRITE_TO_FILE : Write to file Id [dec] failed [dec] bytes, expected [dec] bytes
Explanation Write to file failed when generating punt err log
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_INFRA-3-PUNT_SVC_PROC_ERR : Punt service [chars] create failed
Explanation Punt service process can not be created
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_INFRA-3-PUNT_SVC_TYPE_UNKNOWN : Punted packet with unknown service type [int]
Explanation Punted pak with an unsupported service type
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_INFRA-3-RELOAD_INFO_SAVE_FAIL : Unable to save reload information: [dec]: [chars].
Explanation IOSXE's platform dependent code failed to save the reload information.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_INFRA-3-SHIM_INIT_DISPATCH_INIT_FAIL : IOSXE shim layer initialization, dispatch path init failed.
Explanation IOSXE IOS shim layer initialization of TDL disatch path
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_INFRA-3-SHIM_INIT_MEM_FAIL : IOSXE shim layer initialization failed: Memory initialization failed.
Explanation IOSXE IOS shim layer initialization of memory failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_INFRA-3-SHIM_INIT_PROC_FAIL : IOSXE shim layer initialization failed: Dispatch process creation failed
Explanation IOSXE IOS shim layer initialization creating dispatch process failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_INFRA-3-SHIM_INIT_TDL_FAIL : IOSXE shim layer initialization TDL Lib [chars] failed.
Explanation IOSXE IOS shim layer initialization of TDL library
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_INFRA-3-SHIM_INIT_WQ_CHASFS_FAIL : IOSXE shim layer initialization failed: Can not create receiving chasfs watched queue
Explanation IOSXE IOS shim layer initialization of watched queue failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_INFRA-3-SHIM_INIT_WQ_FAIL : IOSXE shim layer initialization failed: Can not create receiving queues
Explanation IOSXE IOS shim layer initialization of watched queue failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_INFRA-3-SHIM_IPC_NOT_PROCESSED : msg handler returned FALSE for IPC msg for fd [dec], seq_num [dec], service [chars]
Explanation None
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_INFRA-3-SHIM_NO_IPC_DISPATCH_HDL : IOSXE shim layer [chars] process message without IPC dispatch handler.
Explanation IOSXE IOS shim layer has no ipc dispatch handler set
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_INFRA-3-SHIM_RXMSG_NO_IPC_HDL : IOSXE shim layer without IPC handler for fd [dec], seqnum [dec].
Explanation IOSXE IOS shim layer cannot find ipc handler
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_INFRA-3-SN_IPFRR_PROC_ERR : Static Nexthop IPFRR [chars] create failed
Explanation SN IPFRR process can not be created
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_INFRA-3-SWIFT_ORCH_PROC_FAIL : IOSXE SWIFT Orchestrator process creation failed
Explanation The SWIFT Orchestrator process could not be created
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_INFRA-3-VM_PAGE_TABLE_ERR : VM guarded page operation failed, address [hex], [chars]
Explanation VM guarded page avl tree operation error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_INFRA-4-BSO_MSG_RIB_WATCH_WARN : BSO message RIB watch start error
Explanation BSO message RIB watch start error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_INFRA-4-INJECT_TUN_NONIP_WARN : pak with linktype [chars] gets into non-ip tunnel
Explanation IP/IPv6/MPLS packet should to go through GRE tunnel for non-IP payload
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_INFRA-4-NO_PUNT_KEEPALIVE : Keepalive not received for [int] seconds
Explanation Punt Inject keepalive message was not received
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_INFRA-4-PUNT_KEEPALIVE_LOG_ERR_CLOSE_FILE : Failed to close file with descriptor: [dec]
Explanation Closing of file failed when generating punt err log
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_INFRA-4-PUNT_KEEPALIVE_LOG_ERR_GET_FILE_NAME : Failed to get file name
Explanation Could not form a file name when generating punt err logPunt keepalive log error seen
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_INFRA-4-PUNT_KEEPALIVE_LOG_ERR_GET_PROCID : Failed to get process id
Explanation Can't get identifier of the process generating punt err log
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_INFRA-4-PUNT_KEEPALIVE_LOG_ERR_INV_FILE_ID : Invalid file descriptor: [dec]
Explanation Invalid file descriptor was found when generating punt err log
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_INFRA-4-PUNT_KEEPALIVE_LOG_ERR_INV_PARAM : Invalid parameter: [chars]
Explanation Invalid parameter was passed when generating punt err log
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_INFRA-4-PUNT_KEEPALIVE_LOG_ERR_INV_PROCID : Invalid proc id [dec], expected [dec]
Explanation Invalid process trying to generate punt err log
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_INFRA-5-PUNT_SVC_CANT_ENQUEUE : Punted pak can't be enqueued for service
Explanation Punted pak enqueue failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_INFRA-5-PUNT_SVC_INVALID_OPT_PKT : Invalid IPv4 options packet punted to RP
Explanation Invalid IPv4 options packet dropped in RP
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_INFRA-6-AUXTHD_REQUEST : Too many outstanding requests for file system access
Explanation Resource temporarily unavailable
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_INFRA-6-CHASFS_CLOCK_SET_FAIL : Failed to set Chasfs property on system time change
Explanation Unable to set chasfs property on system time change
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_INFRA-6-CONSOLE_ACTIVE : [chars]
Explanation Indicates that the current instance of IOS is assuming active control of the console. This is informational.
Recommended Action No action is required.
%IOSXE_INFRA-6-PLATFORM_RELOAD : [chars]
Explanation Indicates that the current instance of IOS is being reset by the platform code. This is part of a normal reset sequence and the message is informational.
Recommended Action No action is required.
%IOSXE_INFRA-6-PROCPATH_CLIENT_HOG : IOS shim client '[chars]' has taken %ld msec (runtime: %ld msec) to process a '[chars]' message
Explanation The specified IOSXE IOS shim client has taken too long to process a received IPC or chasfs message
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_INFRA-6-SHIM_RXMSG_IPC_INFO : IOS shim layer process IPC msg for fd [dec], seq_num [dec], ipc_status [dec]
Explanation None
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_INFRA-6-THEAD_SELECT_ERR : Inbound message or packet select error, [chars].
Explanation Socket select operation error in threads
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
IOSXE_LICENSE_POLICY_MANAGER
%IOSXE_LICENSE_POLICY_MANAGER-2-BAY_MALLOC_FAILED : [chars]: Policy Mgr Bay DB malloc failed for [dec]/[dec]
Explanation Memory allocation for SPA/EPA failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_LICENSE_POLICY_MANAGER-2-CONFIG_NULL : [chars]: Configuration is unavailable
Explanation License Configuration is undefined for this platform.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_LICENSE_POLICY_MANAGER-2-FEATURE_CONFIG_NULL : [chars]: Feature Configuration is unavailable
Explanation Feature Configuration is undefined for this platform.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_LICENSE_POLICY_MANAGER-2-FEATURE_MALLOC_FAILED : [chars]: Policy Mgr Feature Registration struct malloc failed
Explanation Memory allocation for Feature Registration Struct failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_LICENSE_POLICY_MANAGER-2-FEATURE_NAME_NULL : [chars]: Feature name is NULL
Explanation License feature name string is NULL
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_LICENSE_POLICY_MANAGER-2-IF_MALLOC_FAILED : [chars]: Policy Mgr IF DB malloc failed for [dec]/[dec]
Explanation Memory allocation for SPA/EPA interfaces failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_LICENSE_POLICY_MANAGER-2-LIC_REG_FAILED : [chars]: Failed to register [chars] license feature, result = [hex]
Explanation License Registration failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_LICENSE_POLICY_MANAGER-2-LIC_REL_FAILED : [chars]: [dec]/[dec]: Lic release failed (idx:[dec]), lic_cnt=[dec], err=[dec]
Explanation License Release failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_LICENSE_POLICY_MANAGER-2-LIC_REL_GEN_FAIL : [chars]: [dec]/[dec]: Lic request failed
Explanation License Release failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_LICENSE_POLICY_MANAGER-2-LIC_REQ_FAILED : [chars]: [dec]/[dec]: Lic request failed (idx:[dec]), lic_cnt=[dec], err=[dec]
Explanation License Request failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_LICENSE_POLICY_MANAGER-2-LIC_REQ_GEN_FAIL : [chars]: [dec]/[dec]: Lic request failed
Explanation License Request failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_LICENSE_POLICY_MANAGER-6-LIC_REL_SUC : [int]/[int]/[int]: License release is successful for [chars] feature
Explanation License release is successful, port allowed to go down
Recommended Action Nothing the system is working properly
%IOSXE_LICENSE_POLICY_MANAGER-6-LIC_REQ_SUC : [int]/[int]/[int]: License request is successful for [chars] feature
Explanation License release is successful, port allowed to go down
Recommended Action Nothing the system is working properly
IOSXE_MEMPOOL_MIB
%IOSXE_MEMPOOL_MIB-3-BUFFPOOL_REG_ERROR : Bufferpool register data exceeds allocated memory; Retrieved only [dec] entries.
Explanation Memory allocated is not enough
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
IOSXE_MGMTVRF
%IOSXE_MGMTVRF-3-AFI_ATTACH_FAIL : Management VRF AFI [chars] attach failed
Explanation Can not create afi subblock for mgmt vrf
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_MGMTVRF-3-INTF_ATTACH_FAIL : Management VRF attach to mgmt [chars] failed
Explanation Can not associate mgmt port to mgmt vrf
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_MGMTVRF-3-PROCESS_CREATE_FAIL : Management VRF process creation failed, [chars]
Explanation Can not create IOS process for mgmt port init
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_MGMTVRF-3-SET_TABLEID_FAIL : Installing [chars] Management interface tableid [hex] failed
Explanation Fail to set mgmt port tableid into Linux kernel
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_MGMTVRF-3-VRF_CREATE_FAIL : Management VRF creation failed [chars]
Explanation Can not create mgmt vrf during system init
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_MGMTVRF-6-CREATE_SUCCESS_INFO : Management vrf [chars] created with ID [dec], ipv4 table-id [hex], ipv6 table-id [hex]
Explanation mgmt vrf and ipv4, ipv6 tables created for mgmt port
Recommended Action None
IOSXE_MLP
%IOSXE_MLP-2-DB_ALLOC_FAIL : MLP link db allocation failed
Explanation MLP link database error. Memory chunk creation for MLP link database has failed.
Recommended Action Check for accurate memory management. Perform memory leak checks and look for memory corruption causes. Execute 'show proc memory' command.
%IOSXE_MLP-2-DB_DELETE_FAIL : MLP link db entry delete for link [chars] failed
Explanation MLP link database error. Removal of entry from MLP link database has failed.
Recommended Action Check for accurate memory management. Perform memory leak checks, look for mamory corruption causes and check for correct database management. Execute 'show proc memory' command.
%IOSXE_MLP-2-DB_DESTROY_FAIL : MLP link database destroy failed
Explanation MLP link database error. Memory chunk destroy has failed for MLP link database.
Recommended Action Check for accurate memory management. Perform memory leak checks and look for memory corruption causes. Execute show proc memory command.
%IOSXE_MLP-2-DB_ENTRY_ALLOC_FAIL : MLP link db entry allocation for link [chars] failed
Explanation MLP link database error. Memory chunk allocation for MLP link database entry has failed.
Recommended Action Check for accurate memory management. Perform memory leak checks and look for memory corruption causes. Execute 'show proc memory' command.
%IOSXE_MLP-2-DB_ENTRY_FREE_FAIL : MLP link entry free failed
Explanation MLP link database error. Memory chunk free of MLP link database entry has failed.
Recommended Action Check for accurate memory management. Perform memory leak checks and look for memory corruption causes. Execute 'show proc memory' command.
%IOSXE_MLP-2-DB_INSERT_FAIL : MLP link db entry add for interface [chars] failed
Explanation MLP link database error. Insertion of a new entry into MLP link database has failed.
Recommended Action Check for accurate memory management. Perform memory leak checks, look for memory corruption causes, verify correct database management. Execute 'show proc memory' command.
%IOSXE_MLP-3-ENQUEFAIL : Unable to send [chars] [chars] message to Forwarding Manager Process
Explanation An unexpected condition has occurred which resulted in a configuration not being sent to the Forwarding Manager Processs.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_MLP-4-UPDSTATSERR : Update MLP statistics error
Explanation An unexpected condition has occurred when updating mlp statistics
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
IOSXE_OIR
%IOSXE_OIR-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_OIR-3-OIRTWICE : Subslot [int]/[int] OIR insertion/removal not paired up: [chars]
Explanation An internal OIR-related error occured for the specified SPA.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_OIR-3-POWER_CYCLE_IMMINENT : The SPA in subslot [int]/[int] will be power cycled in [dec] seconds.
Explanation The SPA in the specified subslot will be power cycled in the amount of time specified in the error message.
Recommended Action No action is required.
%IOSXE_OIR-3-PROCMSG : Process msg send failed for process[dec]
Explanation Process message send failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_OIR-3-QUIESCE_FAIL : Quiesce failed for subslot [int]/[int] (error = [dec])
Explanation The RP failed to contact the SPA during failover. The SPA will be reset.
Recommended Action No action is required.
%IOSXE_OIR-3-SPA_INTF_ID_ALLOC_FAILED : Failed to allocate interface identifiers for SPA([chars]) in slot/bay: [int]/[int]
Explanation Failed to get CC buffer and flow control identifiers for the SPA in the specified subslot Traffic cannot flow through the SPA under this failure condition. This can happen if the system runs out of available identifiers.
Recommended Action Try to reduce the number of interfaces configured in the system either by physically removing the SPAs or by changing the system configuration
%IOSXE_OIR-3-SPA_MDR_FAIL : Minimal Disruptive Restart process failed for SPA in subslot [int]/[int], reason [chars].
Explanation The SPA in the subslot 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 No action is required.
%IOSXE_OIR-3-UNQUIESCE_FAIL : Unquiesce failed for subslot [int]/[int] (error = [dec])
Explanation The RP failed to unquiesce the SPA in the specified subslot. The SPA will be reset.
Recommended Action No action is required.
%IOSXE_OIR-6-CARDRECONCILE : SPA type changed on subslot [int]/[int] from [int] to [int]
Explanation The SPA in the specified subslot has been initialized, and it has been detected that it is of a different type to the SPA that was previously in this subslot.
Recommended Action No action is required.
%IOSXE_OIR-6-INSCARD : Card ([chars]) inserted in slot [chars]
Explanation The OIR facility detected the insertion of a card in the slot number specified in the message.
Recommended Action No action is required.
%IOSXE_OIR-6-INSSPA : SPA inserted in subslot [int]/[int]
Explanation The OIR facility detected the insertion of a SPA in the subslot number specified in the message.
Recommended Action No action is required.
%IOSXE_OIR-6-INSSSFP : VCoP inserted in port [chars]
Explanation The OIR facility detected the insertion of VCoP SSFP in the port number specified in the message.
Recommended Action No action is required.
%IOSXE_OIR-6-OFFLINECARD : Card ([chars]) offline in slot [chars]
Explanation The OIR facility detected the state change to offline for the card in the slot number specified in the message.
Recommended Action No action is required.
%IOSXE_OIR-6-ONLINECARD : Card ([chars]) online in slot [chars]
Explanation The OIR facility detected the state change to online for the card in the slot number specified in the message.
Recommended Action No action is required.
%IOSXE_OIR-6-REMCARD : Card ([chars]) removed from slot [chars]
Explanation The OIR facility detected the removal of a card from the slot number specified in the message.
Recommended Action No action is required.
%IOSXE_OIR-6-REMSPA : SPA removed from subslot [int]/[int], interfaces disabled
Explanation The OIR facility detected the removal of a SPA from the subslot number specified in the message. The interfaces on that processor will be administratively shut down and marked as removed. The routing table will be flushed of any routes through the removed interfaces.
Recommended Action No action is required.
%IOSXE_OIR-6-REMSSFP : VCoP removed from port [chars]
Explanation The OIR facility detected the removal of VCoP SSFP in the port number specified in the message.
Recommended Action No action is required.
%IOSXE_OIR-6-SOFT_RELOADSPA : SPA([chars]) reloaded on [chars]
Explanation The SPA in the specified subslot is reloaded by the command hw-module subslot slot#/subslot# reload
Recommended Action No action is required.
%IOSXE_OIR-6-SOFT_STARTSPA : SPA([chars]) restarted in [chars]
Explanation The SPA in the specified subslot is restarted by the command hw-module subslot slot#/subslot# start
Recommended Action No action is required.
%IOSXE_OIR-6-SOFT_STOPSPA : SPA([chars]) stopped in [chars], interfaces disabled
Explanation The SPA in the specified subslot is stopped by the command hw-module subslot slot#/subslot# stop The interfaces on that processor will be administratively shut down and marked as removed. The routing table will be flushed of any routes through the removed interfaces.
Recommended Action No action is required.
%IOSXE_OIR-6-SPARELOAD : SPA reloaded on subslot [int]/[int]
Explanation The SPA in the specified subslot is reloaded.
Recommended Action No action is required.
%IOSXE_OIR-6-SYNCSPA : SPA ([chars]) reloading to come up in [chars] mode
Explanation The SPA in the specified subslot is reloaded by the command hw-module subslot slot#/subslot# reload
Recommended Action No action is required.
IOSXE_PEM
%IOSXE_PEM-3-FANFAIL : The fan in slot [chars]/[dec] is encountering a failure condition
Explanation The fan's hardware is reporting that the fan is failing. This is most likely because the hardware detects the fan as spinning below the minimum speed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_PEM-3-FAN_FAIL_SHUTDOWN : More thatn one [chars] has failed, Leads to shutdown the system
Explanation The Temperature sensor reaching maximum threshold value working properly.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_PEM-3-PEMCHASFSERR : The PEM in slot [chars] has encountered a system software error.
Explanation The PEM's underlying software for storing PEM state is not working properly.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_PEM-3-PEMFAIL : The PEM in slot [chars] is switched off or encountering a failure condition.
Explanation The PEM hardware has been either switched off, or is reporting a failure condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_PEM-3-PEMREDNOPWR : Cannot enable power redundancy mode [chars] because config would create mode with insufficient [chars] power
Explanation Configuration set by user is not valid as power supplies in the active slots do not contain enough power to meet the power requirements
Recommended Action Insert additional power supplies and configure them to be active or configure current standby power supplies to active such that power requirements are met
%IOSXE_PEM-3-PEMREDNOSTDBY : Total power budget of standby power supplies is zero
Explanation Operating in unprotected mode Should insert at least one ps in standby slots
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_PEM-3-SSFP_TEMPERATURE_RAISE : [chars] transceiver temeprature reached threshold value, Leads to shutdown the system
Explanation The Temperature sensor reaching maximum threshold value working properly.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_PEM-3-TEMPERATURE_RAISE : Sensor [chars] has reached maximum temeprature value, Leads to shutdown the system
Explanation The Temperature sensor reaching maximum threshold value working properly.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_PEM-6-FANOK : The fan in slot [chars]/[dec] is functioning properly
Explanation The fan was reporting a failure condition. This message indicates that the fan is no longer reporting a failure
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_PEM-6-INSPEM_FM : PEM/FM slot [chars] inserted
Explanation The platform detected the insertion of a power/fan module in the slot number specified in the message.
Recommended Action No action is required.
%IOSXE_PEM-6-PEMOK : The PEM in slot [chars] is functioning properly
Explanation The PEM hardware may have been either switched off, or reporting a failure condition. This message indicates that the PEM is no longer either switched off, or reporting a failure
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_PEM-6-PEMREDAUTOLCCONFLICT : Cannot enable power redundancy and autoLC shutdown simultaneously
Explanation Power supply redundancy mode n+1 or n+n is not compatible with autoLC shutdown feature.
Recommended Action Disable autoLC shutdown or set power redundancy mode to combined
%IOSXE_PEM-6-REMPEM_FM : PEM/FM slot [chars] removed
Explanation The platform detected the removal of a power/fan module in the slot number specified in the message.
Recommended Action No action is required.
IOSXE_PLATFORM
%IOSXE_PLATFORM-3-WDC_INVALID_LENGTH : WDC length can not be determined: [dec]
Explanation WDC length was not retrieved properly
Recommended Action Check if WDC is programmed on this device
%IOSXE_PLATFORM-3-WDC_NOT_FOUND : WDC returned length: [dec]
Explanation WDC length was set to 0, which specifies probably WDC does not exist
Recommended Action Check if WDC is programmed on this device
%IOSXE_PLATFORM-3-WDC_TLV_NOT_FOUND : WDC TLV could not be read from the Quack device
Explanation WDC TLV couldn't be read from the Quack device
Recommended Action Check if WDC is programmed on this device.
IOSXE_RP_ALARM
%IOSXE_RP_ALARM-2-ESP : [chars] [chars] [chars] [chars] [chars]
Explanation No ESP running alarm information
Recommended Action No action is required.
%IOSXE_RP_ALARM-2-PEM : [chars] [chars] [chars] [chars] [chars]
Explanation Power Entity Module missing information
Recommended Action No action is required.
%IOSXE_RP_ALARM-6-INFO : [chars] [chars] [chars] [chars] [chars]
Explanation Alarm assertion or deassertion information.
Recommended Action No action is required.
IOSXE_RP_CFG_NOT
%IOSXE_RP_CFG_NOT-2-MSGIPCINITERROR : Error initializing IPC queue
Explanation An unexpected condition in which IOS could not initialize a message queue to the PSD.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_CFG_NOT-2-MSGNOEXP : Can not construct a '[chars]' message for configuration export: [chars]
Explanation This error usually indicates either an out of memory condition or a TDL error. If ample memory is available, then the the TDL error may indicate a version conflict with respect to configuration.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_CFG_NOT-2-MSGTDLERROR : Error processing TDL message. [dec]
Explanation An unexpected condition in which IOS has received a TDL message which it can not process.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_CFG_NOT-2-MSGTDLINITERROR : Configuration Notification messaging module initialization failed: Unable to initialize messaging: [chars]
Explanation The Configuration Notification subsystem has failed to initialize the infrastructure for messaging with the Pluggable Services Daemon. Notification of configuration to critical modules cannot proceed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_CFG_NOT-3-MCP_DBPERSIST_ERROR : System configuration update could not complete
Explanation When a 'reload' operation occurs, this chasfs property is read to determine the status of the DB persist/restore/delete operation. This message indicates that the operation failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_CFG_NOT-3-MCP_DBPERSIST_STAT : Failed to read [chars] property: [dec]
Explanation When a 'reload' operation occurs, this chasfs property is read to determine the status of the DB persist/restore/delete operation. This message indicates that the read failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_CFG_NOT-3-MCP_FRU_INVALID : Unknow FRU location: [chars]
Explanation Unknown FRU location
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_CFG_NOT-3-MCP_FRU_LOCATION : Failed to get local FRU location: [dec]
Explanation Unable to get local FRU location
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_CFG_NOT-3-MSGENCRYPTINVALID : The mcprp_cfg_notify subsystem has seen an encryption type it does not recognize. [dec]
Explanation An unexpected condition has occurred while IOS is trying to process a username command.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_CFG_NOT-3-MSGIPCTXERROR : IPC transmit error. [dec]
Explanation An unexpected condition in which IOS encountered an error trying to send a message to another process. %d
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_CFG_NOT-3-MSGNOCAND : Can not construct a candidate entry for configuration export
Explanation This error usually indicates either an out of memory condition or a TDL error. If ample memory is available, then the the TDL error may indicate a version conflict with respect to configuration.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_CFG_NOT-3-MSGNOPWARR : Can not construct an array for configuration export
Explanation This error usually indicates either an out of memory condition or a TDL error. If ample memory is available, then the the TDL error may indicate a version conflict with respect to configuration.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_CFG_NOT-3-MSGNOREPLMSG : Can not construct a replace message for configuration export
Explanation This error usually indicates either an out of memory condition or a TDL error. If ample memory is available, then the the TDL error may indicate a version conflict with respect to configuration.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_CFG_NOT-3-MSGNOUPDATEMSG : Can not construct an update message for configuration export
Explanation This error usually indicates either an out of memory condition or a TDL error. If ample memory is available, then the the TDL error may indicate a version conflict with respect to configuration.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_CFG_NOT-3-MSGOBJNULL : An unexpected condition in which IOS has received a null pointer that it expects to be non-null.
Explanation An unexpected condition has occurred while IOS is trying to process a username command.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_CFG_NOT-3-NVWRITE_EXPORT : Failed to export [chars] notification: [dec]
Explanation When a 'write memory' or 'write erase' operation occurs, the Configuration Notification subsystem exports this event into the chassis file system. This message indicates that the export failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_CFG_NOT-6-IOX_SERVICE_NOTSUPPORTED : IOx service not supported.
Explanation IOx service is not supported in this platform currently. This may be either due to the feature unavailability or due the current inadequate license level of the system.
Recommended Action None
IOSXE_RP_DPIDB
%IOSXE_RP_DPIDB-3-BULK_SYNC : Failed to send [chars] information to peer
Explanation The bulk synchronization of the DPIDX configuration to the standby RP has failed to complete successfully; DPIDX has therefore taken the action which will result in a reload of the peer in order to once more attempt to successfully synchronize the configuration state which may have failed initially to a transient condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_DPIDB-3-CF : Datapath IDB CF operation failed -[chars]
Explanation Failure in some datapath ID CF activity.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show interface command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_DPIDB-3-DECODE : Decode via [chars] of [chars] failed
Explanation A message of the transport and type described failed in its attempt to be decoded on the standby. The resultant action taken by the standby route processor is an attempt to resynchronize.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_DPIDB-3-DOWNLOADFAIL : Unable to download [chars] message to [chars]
Explanation An unexpected condition has occurred which resulted in a configuration not being sent to the reported process.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_DPIDB-3-DYN_SYNC : Failed to process [chars] dynamic state
Explanation The incremental synchronization of the DPIDX configuration to the standby RP has failed to complete successfully. This implies that the configuration state between the active and standby RP is inconsistent.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show interfaces command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_DPIDB-3-EFPSTATSFAILED : EFP stats message data get error: ([dec]) for EFP [int] on [chars]
Explanation An unexpected error occurred extracting fields from an EFP stats message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_DPIDB-3-EXDMAXVRFERR : Exceed Pathmgr max rloc vrf error
Explanation An unexpected condition has occurred when exceeding max rloc vrf
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_DPIDB-3-FASTNOTIFY : Fast notify failed for [chars]
Explanation A fast notify message failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show interface command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_DPIDB-3-FRRLDFLOWIDDELETIONFAILED : Deletion of fast-reroute flow ID with manager failed
Explanation An unexpected condition has occurred that deletion of fast-reroute flow ID.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show interface command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_DPIDB-3-IDBBADTYPE : Datapath IDB type [dec] is not valid
Explanation An unexpected condition has occurred as the type of a datapath IDB is not valid.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show interface command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_DPIDB-3-IDBEXIST : Datapath IDB already exists in this mapping entry: [chars]-[dec]
Explanation An unexpected condition has occurred that an attempt is made to save datapath IDB in a mapping entry filled by another.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show interface command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_DPIDB-3-IDBNONEXIST : Datapath IDB does not exist in this mapping entry: [chars]-[dec]
Explanation Datapath IDB lookup points to empty mapping entry.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show interface command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_DPIDB-3-IDBNOTVAI : Invalid API call for [chars]
Explanation Failure in an internal API
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show interface command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_DPIDB-3-IDXALLOCFAILED : Datapath IDB index allocation failed: [chars]
Explanation An unexpected condition has occurred as all the available of datapath IDB indices are used.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show interface command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_DPIDB-3-IDXBADRANGE : Datapath IDB index [dec] is not in a valid range
Explanation An unexpected condition has occurred as the index of a datapath IDB is not valid.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show interface command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_DPIDB-3-IDXDELETIONFAILED : Deletion of datapath IDB index from the database failed ([chars] -[hex]) rc [dec]
Explanation An unexpected condition has occurred that deletion of datapath IDB indices failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show interface command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_DPIDB-3-IDXINSERTFAILED : Insertion of datapath IDB index [dec] into database failed
Explanation An unexpected condition has occurred that insertion of datapath IDB indices failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show interface command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_DPIDB-3-IDXLOOKUPFAILED : Lookup of datapath IDB index from the database failed ([chars])
Explanation An unexpected condition has occurred that lookup of datapath IDB indices failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show interface command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_DPIDB-3-IP_MTU_ALLOC_FAIL : No hardware resources for [int] byte IP MTU on [chars]
Explanation We reached to the threshold of maximum supported unique IP MTU on this platform.
Recommended Action No action is required.
%IOSXE_RP_DPIDB-3-ISSU : [chars] [chars] failed; [chars]
Explanation An operation pertaining to the ISSU support for DPIDX failed to complete using either the CF or IPC transport context with the reason specified
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_DPIDB-3-LIST : List [chars] failed for [chars]
Explanation List enqueue or removal failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show interface command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_DPIDB-3-MTU_ALLOC_FAIL : No hardware resources for [int] byte MTU on [chars]
Explanation We reached to the threshold of maximum supported unique MTU on this platform.
Recommended Action No action is required.
%IOSXE_RP_DPIDB-3-NEGOTIATION : Failed to start ISSU [chars] session negotiation; [chars]
Explanation The ISSU negotiation with the peer failed to start for either the CF or IPC transport with the reason specified.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_DPIDB-3-NOHWSUBBLOCK : HWIDB [chars] does not have a hardware subblock
Explanation An unexpected condition has occurred that no hardware subblock was previously allocated for a HWIDB.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show interface command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_DPIDB-3-NOSWSUBBLOCK : SWIDB [chars] does not have a software subblock
Explanation An unexpected condition has occurred that no software subblock was previously allocated for a SWIDB.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show interface command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_DPIDB-3-NULLTIMER : NULL timer
Explanation A timer is NULL
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show interface command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_DPIDB-3-PROGRESSION : Unable to inform RF of bulk sync completion; [chars]
Explanation The active route processor has sent a notification to the standby to inform of the completion of the bulk synchronization of the DPIDX configuration. The standby has failed to respond to the active informing that it received the notification noting the reason for the failure. The resultant action taken by the standby route processor is an attempt to resynchronize.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_DPIDB-3-RECEIVE : Message via [chars] is [chars]
Explanation An attempt to receive and process a versioned negotiation or synchronization message has failed due to an internal error being detected by the information received from the IPC or CF components.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_DPIDB-3-REGISTRATION : ISSU [chars] failed for [chars]; [chars]
Explanation An ISSU registration for the set of initial capabilities and sessions failed due to the reason specified. This will have the effect of the DPIDX ISSU support being unavailable between peers.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_DPIDB-3-RF : Datapath IDB RF operation failed -[chars]
Explanation Failure in some datapath ID RF activity.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show interface command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_DPIDB-3-RPC : Datapath IDB RPC operation failed -[chars]
Explanation Failure in some datapath ID RPC activity.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show interface command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_DPIDB-3-TRANSFORM : [chars] of [chars] via [chars] failed for dpidx [int]
Explanation An attempt to either encode or decode a versioned synchronization message has failed due to an internal error encountered by the ISSU component.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_DPIDB-3-TRANSMIT : Unable to send via [chars] [chars] [chars] [chars]; [chars]
Explanation An attempt to send a versioned negotiation or synchronization message has failed due to an internal error encountered by the IPC or CF components.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_DPIDB-6-READY : [chars] peer not ready, discarding [chars]
Explanation The synchronization attempt for the message has determined that the transport has lost communication with its peer. This is a normal situation which indicates that the standby route-processor is currently out of service implying a simplex redundancy mode.
Recommended Action None
%IOSXE_RP_DPIDB-6-RELOAD : [chars], reloading [chars]
Explanation A synchronization attempt between the active and standby RP peers has failed with the reason indicated. The standby peer is reloaded in an attempt to resynchronize when operating in a stateful redundant mode.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_DPIDB-6-TIMEOUT : Bulk sync is flow controlled by [chars]
Explanation The bulk synchronization of the DPIDX configuration to the standby RP has encountered a flow control condition which has effected a timeout awaiting the condition to clear. This will result in a reload of the standby RP to allow the bulk synchronization to restart.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
IOSXE_RP_IF_FLOW_IDS
%IOSXE_RP_IF_FLOW_IDS-3-BUFF_OFFSET_NULL : Unable to utilize the memory buffer provided by the Checkpoint Facility. This [chars] CF client has failed to Bulk Sync.
Explanation This error indicates the Checkpoint Facility is having problems recognizing its own buffer layout. If this occurs during Bulk Sync then Bulk Sync will terminate without completing. Otherwise the incremental Sync will fail.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_IF_FLOW_IDS-3-CF_CANNOT_REGISTER : The call to add this [chars] CF client to the Checkpoint Facility failed with the error [chars]. This client is unable to proceed and will not be registered.
Explanation For some reason the Checkpoint Facility will not register this client. As a result the Standby will never receive synchronized state from this CF client on the Active RP, The system is not capable of SSO and HA switchover.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_IF_FLOW_IDS-3-CF_SEND_BULK_NONBLOCKED : The Checkpoint Facility reported the error [chars] while attempting to send a message. Bulk Sync of this [chars] CF client is terminating.
Explanation This error indicates the Checkpoint Facility has internal problems related to IPC, and cannot perform a non-blocked send operation.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_IF_FLOW_IDS-3-CF_SEND_INCR_NONBLOCKED : The Checkpoint Facility reported the error [chars] while attempting to send a non-blocked message. The Incremental Sync transaction for this [chars] CF client cannot be sent to the Standby RP.
Explanation This error indicates the Checkpoint Facility has internal problems related to IPC.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_IF_FLOW_IDS-3-DECODE : Decode via CF of [chars] failed
Explanation A message sent via the CF transport failed in its attempt to be decoded on the standby. The resultant action taken by the standby route processor is an attempt to resynchronize.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_IF_FLOW_IDS-3-DEFERRED_DURING_BULK_SYNC : Encountered error [chars] while trying to place an [chars] transaction on the Deferred list during Bulk Sync for the [chars] CF client.
Explanation Unable to cache a deferred transaction while Bulk Sync is underway. This can adversely impact SSO state on the Standby RP.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_IF_FLOW_IDS-3-ISSU_OP : [chars] [chars] failed; [chars]
Explanation An operation pertaining to the ISSU support for SPA MARMOT IDs failed to complete using the CF transport context with the reason specified
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_IF_FLOW_IDS-3-NEGOTIATION : Failed to start ISSU [chars] session negotiation; [chars]
Explanation The ISSU negotiation with the peer failed to start for either the CF or IPC transport with the reason specified.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_IF_FLOW_IDS-3-NO_BUFF_FOR_SYNC : The Checkpoint Faclity reported the error [chars] during a request for a buffer length of [dec]. This [chars] CF client has failed to synchronize a transaction to the Standby RP.
Explanation This error indicates that the buffer management within the Checkpoint Facility has either run out of buffers, or has some other problem. If this occurs during Bulk Sync then Bulk Sync will terminate without completing. Otherwise the incremental Sync will fail.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_IF_FLOW_IDS-3-RECEIVE : Client reports message CF is [chars]
Explanation An attempt to receive and process a versioned negotiation or synchronization message has failed due to an internal error being detected by the information received from the CF component.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_IF_FLOW_IDS-3-REGISTRATION : ISSU [chars] failed for [chars]; [chars]
Explanation An ISSU registration for the set of initial capabilities and sessions failed due to the reason specified. This will have the effect of the SPA MARMOT ID ISSU support being unavailable between peers.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_IF_FLOW_IDS-3-RF_ADD_CLIENT_FAILED : The RF facility failed to add this [chars] client, reason given is [chars].
Explanation This indicates the RF facility could not add the client.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_IF_FLOW_IDS-3-RF_IF_ID_REGEN_ERROR : Error code [dec] encountered trying to regenerate interface flow-control identifer. If id [int] resides in slot/subslot/port ([int]/[int]/[int]).
Explanation The background process which performs Flow Control Id Pool regeneration encountered an error. As a consequence the Standby does not have valid Id pools and cannot progress to Active state.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_IF_FLOW_IDS-3-RF_PEER_EVENT_BUFFER : This [chars] RF client is unable to acquire an event buffer to send an RF peer message, the error [chars] was returned.
Explanation This indicates the RF facility is unable to provide a message buffer needed to communicate with the RF peer. As a consequence the RF progression may be compromised.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_IF_FLOW_IDS-3-RF_POOL_REGEN_ERROR : Id Pool Regeneration encountered error code [dec], cannot switchover.
Explanation The background process which performs Flow Control Id Pool regeneration encountered an error. As a consequence the Standby does not have valid Flow Id pools and cannot progress to Active state.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_IF_FLOW_IDS-3-RF_POOL_REGEN_PROCESS_FAILED : The [chars] RF client Failed to create the Id Pool Regeneration process.
Explanation The background process which performs Flow Control Id Pool regeneration failed to start. As a consequence the Standby will never obtain the relevent SSO state to enable HA switchover.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_IF_FLOW_IDS-3-RF_PROCESS_FAILED : This [chars] RF client Failed to create the Bulk Sync Process.
Explanation The background process which performs the RF Bulk Sync failed to be created. As a consequence the Standby will never obtain the relevent SSO state to enable HA switchover.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_IF_FLOW_IDS-3-RF_SEND_PEER : This [chars] RF client encountered error [chars], when attempting to send a peer message.
Explanation This indicates the RF facility could not send a message to the RF peer. As a consequence the RF progression may be compromised.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_IF_FLOW_IDS-3-RF_SPA_ID_REGEN_ERROR : Error code [dec] encountered trying to regenerate spa [chars] identifier in slot/subslot ([int]/[int])
Explanation The background process which performs Flow Control Id Pool regeneration encountered an error. As a consequence the Standby does not have valid Id pools and cannot progress to Active state.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_IF_FLOW_IDS-3-SEND_FAIL_RELOAD : Checkpoint Facility Failed to send a [chars] transaction for this [chars] CF client. Reloading the Standby RP.
Explanation This indicates the underlying Checkpoint Facility could not deliver a message sent from the active RP to the standby RP. The process will automatically reload the standby RP.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_IF_FLOW_IDS-3-TRANSFORM : [chars] of [chars] via CF failed
Explanation An attempt to either encode or decode a versioned synchronization message has failed due to an internal error encountered by the ISSU component.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_IF_FLOW_IDS-3-TRANSMIT : Unable to send via [chars] [chars] [chars] [chars]; [chars]
Explanation An attempt to send a versioned negotiation or synchronization message has failed due to an internal error encountered by the CF component.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_IF_FLOW_IDS-4-DEF_LIST_REMOVE : Failed to remove one entry from the Deferred Sync list, for the [chars] CF client.
Explanation An unexpected condition occured during list maintenance.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_IF_FLOW_IDS-6-CFPEER_CANNOT_RECV : The Checkpoint Peer is not ready to receive messages. The Incremental Sync transaction for this [chars] CF client will not occur.
Explanation This error indicates the Checkpoint Facility has signalled the peer has gone away.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_IF_FLOW_IDS-6-READY : [chars] peer not ready, discarding [chars]
Explanation The synchronization attempt for the message has determined that the transport has lost communication with its peer. This is a normal situation which indicates that the standby route-processor is currently out of service implying a simplex redundancy mode.
Recommended Action None
IOSXE_RP_MGMTE
%IOSXE_RP_MGMTE-3-MSGCREATENULL : Cannot allocate [chars] TDL message
Explanation An unexpected condition in which IOS cannot allocate TDL message for Management ethernet.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_MGMTE-3-MSGTDLINITERROR : Management ethernet interface messaging module initialization failed: Unable to initialize messaging: [chars]
Explanation The Management ethernet interface subsystem has failed to initialize the infrastructure for messaging with the Pluggable Services Daemon. Configuration of management ethernet modules cannot proceed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_MGMTE-3-PROCESS_CREATE_FAIL : Management ethernet statistics process creation failed
Explanation Can not create IOS process for RP management ethernet port statistics collection
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
IOSXE_RP_NV
%IOSXE_RP_NV-3-BACKUP_NV_ACCESS_FAIL : Initial read of backup NVRAM contents failed
Explanation This error happens when the contents of the backup NVRAM cannot be read during system initialization. The failure may be due to data corruption of the backup NVRAM contents. The primary nvram contents will be backed up here again.
Recommended Action LOG_STD_ACTION
%IOSXE_RP_NV-3-NV_ACCESS_FAIL : Initial read of NVRAM contents failed
Explanation This error happens when the contents of the NVRAM cannot be read during system initialization. The failure may be due to data corruption of the NVRAM contents. The initial configuration dialog will be entered and the configuration must be restored.
Recommended Action LOG_STD_ACTION
IOSXE_RP_SPA
%IOSXE_RP_SPA-3-BAD_IFCOMTYPE : Bad ifcom message type=[int]
Explanation A SPA module passed down a message that the RP software was not prepared to handle.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_SPA-3-CI_UPDATE_FAIL : Failed to update connection identifier for interface [chars]
Explanation The SPA driver is not able to update the datapath connection identifier for the interface specified in the message. This indicates a software error.
Recommended Action No action is required.
%IOSXE_RP_SPA-3-DPIDX_LKUP_FAIL : Failed to retrieve datapath identifier for interface [chars]
Explanation The SPA driver is not able to retrieve the datapath identifier for the interface specified in the message. This indicates a software error.
Recommended Action No action is required.
%IOSXE_RP_SPA-3-ERROR : common_str_empty_str
Explanation This message can take many forms. It provides information about a software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_SPA-3-FLOWID_ALLOC_FAIL : Failed to allocate a flow control identifier for interface [chars]
Explanation The SPA driver is not able to allocate the datapath flow control identifier for the interface specified in the message. This indicates a software error.
Recommended Action No action is required.
%IOSXE_RP_SPA-3-FLOWID_RELEASE_FAIL : Failed to release a flow control identifier for interface [chars] (status = [dec])
Explanation The SPA driver is not able to release the datapath flow control identifier for the interface specified in the message. This indicates a software error.
Recommended Action No action is required.
%IOSXE_RP_SPA-3-FOREVER : cmd [int] to [chars] (slot [int]/[int]) took [int]secs, done [hex]
Explanation A CCB command from the RP to a SPA module took longer than expected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_SPA-3-HWIDB_FAILURE : Creation: slot [dec] subSlot [dec] port [dec] vc [dec]
Explanation Failed to create an interface hwidb.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_SPA-3-HWIDB_INIT_FAIL : Failed to initialize data structure for SPA port [dec]/[dec]/[dec]
Explanation A SPA driver was not able to properly initialize a data structure mentioned in the message. This indicates a software error.
Recommended Action No action is required.
%IOSXE_RP_SPA-3-IFCFG_CMD_NOT_OWNER : Process '[chars]' waiting for interface configuration command ([hex]) to slot [int]/[int] without acquiring lock owned by process '[chars]'
Explanation A process on the RP sent an configuration command to the slot specified in the error message and a different process waited for the result. This could cause incorrect line card configuration states.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_SPA-3-IFCFG_FOREVER : to [chars] (slot [int]/[int]) took [int]secs, ret_val [int]
Explanation A interface config command from the RP to a SPA module took longer than expected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_SPA-3-IFCFG_NO_UNIQUE_KEY : No unique-key generator registered for interface configuration command [int].
Explanation The High Availability component for SPA modules is unable to properly synchronize state information for the current configuration.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_SPA-3-INVALID_PORT_NUM : slot=[dec] port=[dec], hwidbType=[hex], max_port_num=[dec], LCtype=[hex]
Explanation The port number is out of range.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_SPA-3-IPCALLOCFAIL : Failed to allocate IPC buffer [chars]
Explanation The RP failed to allocate a buffer for communication with a SPA
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_SPA-3-IPCPORT : Failed to [chars] IPC port '[chars]', error [chars]
Explanation The Linecard failed to create a port for communication with the Route Processor (IOSXE-RP).
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%IOSXE_RP_SPA-3-IPCPORTFAIL : Failed to open IPC port '[chars]' with error [chars]
Explanation The RP failed to open a port for communication with a SPA module.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_SPA-3-IPCSENDFAIL : Failed to send IPC message [chars]
Explanation The RP failed to send a message to a SPA module.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_SPA-3-MAC_FILTER_ADD_FAIL : All the available [dec] mac filters for [chars] have been consumed. Failed to add [enet] for interface [chars]
Explanation The hardware cannot support any more filters.
Recommended Action The interface configuration should be reworked to not cross the limit set by the hardware. If the error is still seen please LOG_STD_SH_TECH_ACTION
%IOSXE_RP_SPA-3-MAX_SPA : Power to IPSEC-SPA-2G in [chars] is denied because it has exceeded the number allowed([dec])
Explanation The number of IPSEC-SPA-2G in a chassis is limited. This message is displayed when the number of IPSEC-SPA-2G in the chassis has exceeded this limit.
Recommended Action Use only the number of supported IPSEC-SPA-2G
%IOSXE_RP_SPA-3-NO_HOST_INFO : slot [dec] subSlot [dec], spaType [hex]
Explanation Failed to get information about the host linecard.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_SPA-3-NULL_DATA_STRUCTURE : common_str_empty_str
Explanation A SPA driver is not able to retrieve the data structure mentioned in the message. This indicates a software error.
Recommended Action No action is required.
%IOSXE_RP_SPA-3-PROGRESSION : Unable to inform RF of bulk sync completion; [chars]
Explanation The standby has failed to notify the active that its bulks synchronization of the SPA TSM has completed. The resultant action taken by the standby route processor is an attempt to resynchronize.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_SPA-3-SEND_L2_HDR_MSG_FAIL : slot [dec] subslot [dec]
Explanation Failed to send ngio L2 header to iomd.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_SPA-3-SEND_NGIO_MSG_FAIL : NGIO Module message send failed for slot [dec] subslot [dec]
Explanation Failed to send ngio msg to iomd.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_SPA-3-SPA_NO_HOST_INFO : slot [dec] subSlot [dec], PID [chars]
Explanation Failed to get information about the host linecard.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_SPA-3-VC_FLOWID_ALLOC_FAIL : Failed to allocate a flow control identifier for VC [dec] under interface [chars]
Explanation The SPA driver is not able to allocate the datapath flow control identifier for the VC/interface specified in the message. This indicates a software error.
Recommended Action No action is required.
%IOSXE_RP_SPA-3-VC_INGID_ALLOC_FAIL : Failed to allocate a ingress identifier for VC [dec] interface [chars]
Explanation The SPA driver is not able to allocate the datapath ingress identifier for the VC/interface specified in the message. This indicates a software error.
Recommended Action No action is required.
%IOSXE_RP_SPA-3-VC_PROV_FAIL : Failed to provision interface [chars]
Explanation The SPA driver is not able to provision the interface specified in the message. Verify that the SPA hardware is not provisioned above the supported limit. Otherwise, this indicates a hardware error.
Recommended Action No action is required.
%IOSXE_RP_SPA-4-CCB_PLAYBACK_ERROR : CCB playback failed for slot [dec].
Explanation The High Availability component for SPA modules failed to synchronize some new state information for the specified slot.
Recommended Action Reload the standby supervisor module to force a fresh bulk synchronization. If this error recurs, LOG_STD_ACTION
%IOSXE_RP_SPA-4-CCB_RECORD_ERROR : CCB record failed for slot [dec].
Explanation The High Availability component for SPA modules failed to record some new state information for the specified slot.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_SPA-4-IFCFG_CMD_TIMEOUT : Interface configuration command ([hex]) to slot [int]/[int] timed out
Explanation The RP sent an configuration command to the slot specified in the error message and received no confirmation for the command.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_SPA-4-IFCFG_DFLT_LIST_ERROR : For Interface Configuration command [int], default retval list search resulted [hex] for slot [int]/[int]
Explanation The High Availability component for SPA modules failed to synchronize some new state information for the specified slot.
Recommended Action LOG_STD_SH_CMD_ACTION(show platform redundancy if-config default-retvals)
%IOSXE_RP_SPA-4-IFCFG_PLAYBACK_ERROR : Interface Configuration command [int] playback failed for slot [int]/[int].
Explanation The High Availability component for SPA modules failed to synchronize some new state information for the specified slot.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_SPA-4-IFCFG_RECORD_ERROR : Interface Configuration command [int] record failed for slot [int]/[int].
Explanation The High Availability component for SPA modules failed to record some new state information for the specified slot.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_SPA-4-INCR_CFG_SYNC_FAIL : [chars] incremental running-config sync for [[dec]/[dec]] failed -[chars]([dec]) , Reload Standby
Explanation The specified IOSXE incremental running-config sync failed
Recommended Action Power cycle the redundant supervisor
%IOSXE_RP_SPA-4-IPCFAILED : IPC failed to send RPC message to SPA module
Explanation The RP failed to send an RPC message via IPC to a SPA module.
Recommended Action No action is required.
%IOSXE_RP_SPA-4-LCLOG_PARSE_ERR : Error parsing logger message: [chars] from subslot [int]/[int]
Explanation The SPA module passed down a logger message that could not be parsed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_SPA-4-LCLOG_TOOLONG : Message too long from slot [int]/[int]: [int] bytes
Explanation The SPA module passed down a logger message that is too long for the RP to handle.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_SPA-4-SEMAHOG : Process [dec] ([chars]) hogging [chars]! calling proc [dec] ([chars])
Explanation The RP waited too long for a reply to a command sent to a SPA module.
Recommended Action No action is required.
%IOSXE_RP_SPA-4-SPA_CMD_NO_RESP : [chars]: No response for interface configuration command [int]
Explanation A timeout occurred while RP was waiting for a response from line card. This may happen due to line card CPU being too busy to respond to the command.
Recommended Action No action is required.
%IOSXE_RP_SPA-4-SPA_RESP_CMD_ERR : [chars]: Received response to interface configuration command [chars] with wrong return value [int].
Explanation An internal error occurred while configuring the interface. The configuration may not have succeeded.
Recommended Action Check that the running configuration for the interface is correct. If this message is repeatable, please LOG_STD_SH_TECH_ACTION
%IOSXE_RP_SPA-4-SPA_RESP_CMD_MISMATCH : [chars]: Expecting response to interface configuration command [int] but received response to command [int].
Explanation An internal synchronization error occurred while configuring the interface. The configuration may not have succeeded.
Recommended Action Check that the running configuration for the interface is correct. If this message occurred on the standby, try reloading the standby to ensure that its configuration is in sync. If this message is repeatable, please LOG_STD_SH_TECH_ACTION
%IOSXE_RP_SPA-6-CARDRELOAD : Module [int] reload due to SPA insert in [int]/[int].
Explanation When inserting a SPA on this carrier card, the card is reset.
Recommended Action No action is required.
%IOSXE_RP_SPA-6-CTRLRSWITCH : switching controller type from [chars]([dec]) to [chars]([dec]) for subslot [int]/[int].
Explanation When IOSXE-SIP40 is inserted in the slot previously occupied by IOSXE-SIP10 or vice-versa the controller type of the card is overwritten to reflect the current SIP.
Recommended Action No action is required.
%IOSXE_RP_SPA-3-FRR_CFG_REC_FAIL : Failed to record fast reroute conifguration on [chars]: [chars]
Explanation This message is displayed when a fast reroute configuration is not properly recorded.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_SPA-3-LIC_REG_FAILED : [int]/[int]/[int]: Failed to register license feature [chars], err=[hex]
Explanation License registration has been denied by license manager
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_SPA-3-LIC_REL_FAILED : [int]/[int]/[int]: Failed to release license feature [chars], handle=[hex], err=[hex]
Explanation License release has been denied by license manager
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_SPA-3-LIC_REQ_FAILED : [int]/[int]/[int]: Interface enable not allowed -license request failed , err=[hex]
Explanation A 10 Gig License is required to enable this port. License request has been denied by license manager
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_SPA-3-MISSING_SPA_PKG_ERR : sipspa[chars] package is not installed for slot = [dec] and subslot = [dec], SPA bootup failed.
Explanation This message is displayed when attempting to bootup a SPA without installing a subpackage required for the same.
Recommended Action Download the sub-package required for the affected SPA from the Cisco CCO software download site and install the same. This SPA can be booted in sub-package mode only. Please refer to the Cisco ASR platform documentation for obtaining and installing sub-packages.
%IOSXE_RP_SPA-3-MISSING_SPA_PKG_WARN : sipspa[chars] package is not installed in standby for slot = [dec] and subslot = [dec].
Explanation This message is displayed in standby console when attempting to bootup or restart or reload a WMA SPA without installing a subpackage in the standby RP, although the SPA is or will be operational due to prior wma spa package installation in active RP. If switchover takes place the WMA SPA will still be operational. But any subsequent soft or hard oir of the SPA will fail due to missing sub package required to boot up the SPA. Hence it is recommended to complete the wma spa package installation in standby also before switchover or immidiately after switchover.
Recommended Action Download the sub-package required for the affected SPA from the Cisco CCO software download site and install the same for the standby RP as is done on active RP. Please refer to the Cisco ASR platform documentation for obtaining and installing sub-packages.
%IOSXE_RP_SPA-3-SONET_ALARM_PROC_ERR : [chars] Error has occurred while processing in the sonet alarm-proc
Explanation Either free/create of the memory failed in SONET alarm proc
Recommended Action None
%IOSXE_RP_SPA-3-SPA_WRONGTYPE : Mismatched SPA type ([dec]) in slot [dec]/[dec]. Expected type [dec]. Use 'no card [dec]/[dec]' command to override preprovisioning and update card type.
Explanation The SPA inserted does not match the currently provisioned SPA type.
Recommended Action Replace wrong SPA with currently provisioned SPA type, or type 'no card' to allow new card type to be discovered.
%IOSXE_RP_SPA-3-UNSUPPORTED_SRVCS_SPA : Service SPA ([hex]) in [dec]/[dec] is not supported. SPA bootup failed.
Explanation This message is displayed when attempting to bootup any service SPA in router running non K9 image, i.e., non-crypto image.
Recommended Action Download the K9 IOS XE sub-packages and the required sub-package for the given service SPA from the Cisco CCO software download site and install the same. This SPA can be booted in sub-package mode only. Please refer to the Cisco ASR platform documentation for obtaining and installing sub-packages.
%IOSXE_RP_SPA-6-MEDIA_AUTOFAILOVER : Media Fail over from ([chars]) to ([chars])
Explanation Gige Media Failover.
Recommended Action This is inforamtional message, Not an error message. Use 'show interface gig' to see the current active media type.
%IOSXE_RP_SPA-3-FRR_CFG_REC_FAIL : Failed to record fast reroute conifguration on [chars]: [chars]
Explanation This message is displayed when a fast reroute configuration is not properly recorded.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_SPA-3-LIC_REG_FAILED : [int]/[int]/[int]: Failed to register license feature [chars], err=[hex]
Explanation License registration has been denied by license manager
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_SPA-3-LIC_REL_FAILED : [int]/[int]/[int]: Failed to release license feature [chars], handle=[hex], err=[hex]
Explanation License release has been denied by license manager
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_SPA-3-LIC_REQ_FAILED : [int]/[int]/[int]: Interface enable not allowed -license request failed , err=[hex]
Explanation A 10 Gig License is required to enable this port. License request has been denied by license manager
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_SPA-3-MISSING_SPA_PKG_ERR : sipspa[chars] package is not installed for slot = [dec] and subslot = [dec], SPA bootup failed.
Explanation This message is displayed when attempting to bootup a SPA without installing a subpackage required for the same.
Recommended Action Download the sub-package required for the affected SPA from the Cisco CCO software download site and install the same. This SPA can be booted in sub-package mode only. Please refer to the Cisco ASR platform documentation for obtaining and installing sub-packages.
%IOSXE_RP_SPA-3-MISSING_SPA_PKG_WARN : sipspa[chars] package is not installed in standby for slot = [dec] and subslot = [dec].
Explanation This message is displayed in standby console when attempting to bootup or restart or reload a WMA SPA without installing a subpackage in the standby RP, although the SPA is or will be operational due to prior wma spa package installation in active RP. If switchover takes place the WMA SPA will still be operational. But any subsequent soft or hard oir of the SPA will fail due to missing sub package required to boot up the SPA. Hence it is recommended to complete the wma spa package installation in standby also before switchover or immidiately after switchover.
Recommended Action Download the sub-package required for the affected SPA from the Cisco CCO software download site and install the same for the standby RP as is done on active RP. Please refer to the Cisco ASR platform documentation for obtaining and installing sub-packages.
%IOSXE_RP_SPA-3-SONET_ALARM_PROC_ERR : [chars] Error has occurred while processing in the sonet alarm-proc
Explanation Either free/create of the memory failed in SONET alarm proc
Recommended Action None
%IOSXE_RP_SPA-3-SPA_WRONGTYPE : Mismatched SPA type ([dec]) in slot [dec]/[dec]. Expected type [dec]. Use 'no card [dec]/[dec]' command to override preprovisioning and update card type.
Explanation The SPA inserted does not match the currently provisioned SPA type.
Recommended Action Replace wrong SPA with currently provisioned SPA type, or type 'no card' to allow new card type to be discovered.
%IOSXE_RP_SPA-3-UNSUPPORTED_SRVCS_SPA : Service SPA ([hex]) in [dec]/[dec] is not supported. SPA bootup failed.
Explanation This message is displayed when attempting to bootup any service SPA in router running non K9 image, i.e., non-crypto image.
Recommended Action Download the K9 IOS XE sub-packages and the required sub-package for the given service SPA from the Cisco CCO software download site and install the same. This SPA can be booted in sub-package mode only. Please refer to the Cisco ASR platform documentation for obtaining and installing sub-packages.
%IOSXE_RP_SPA-6-MEDIA_AUTOFAILOVER : Media Fail over from ([chars]) to ([chars])
Explanation Gige Media Failover.
Recommended Action This is inforamtional message, Not an error message. Use 'show interface gig' to see the current active media type.
IOSXE_SERVICE_ENGINE
%IOSXE_SERVICE_ENGINE-3-MSGINITFAIL : Initialization of interface [chars] failed
Explanation The initialization of the interface mentioned in the error message has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_SERVICE_ENGINE-3-MSGOPENFAIL : Cannot open interface [chars] ([dec])
Explanation During the creation of a Service-Engine interface, it is necessary to program the system parameters in the driver. The driver cannot be opened.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_SERVICE_ENGINE-3-MSGSETFAIL : Set id on interface [chars] ([dec])
Explanation During the creation of a Service-Engine interface, it is necessary to program the system parameters in the driver. The failed to accept the programming.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
IOSXE_RP_VTYMGT
%IOSXE_RP_VTYMGT-3-MSGBIPCBUFFER : Unable to acquire a BIPC buffer of length [dec] for sending messages.
Explanation A message was to be sent by IOS, but no BIPC buffer was available. The message to be sent has been discarded and the associated operation failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_VTYMGT-3-MSGBIPCERR : Unable to process received BIPC messages for Vty Management, error: [chars]
Explanation An unexpected condition has occurred while IOS was trying to process a received BIPC message for Vty Management.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_VTYMGT-3-MSGBUILDERROR : Error '[dec]' building TDL Vty Management message '[chars]': [chars]
Explanation An unexpected condition has occurred while IOS is building a TDL response message for Vty Management
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_VTYMGT-3-MSGDISPATCH : Unable to dispatch received TDL messages for Vty Management
Explanation An unexpected condition has occurred while IOS is trying to dispatch to the TDL message handler functions for received TDL messages for Vty Management.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_VTYMGT-3-MSGDISPATCHNULL : Received NULL TDL message
Explanation An unexpected condition in which IOS has received a NULL TDL message for Vty Management.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_VTYMGT-3-MSGENQUEUEERROR : Error queueing TDL Vty Management message '[chars]'
Explanation An unexpected condition has occurred when IOS attempted to queue a TDL response message for Vty Management
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_VTYMGT-3-MSGERROR : Error '[dec]' handling a received TDL message '[chars]' for Vty Management: [chars]
Explanation An unexpected condition has occurred while IOS is processing a received Vty Management TDL message
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_VTYMGT-3-MSGEXTAPPUPDATE : Unable to update external application data for line '[dec]'
Explanation An attempt to update the external application for a line failed unexpectedly. The line update failed and if the line number specified is valid, the line was released.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_VTYMGT-3-MSGINVALIDFIELDINT : Invalid field '[chars]' in TDL message '[chars]' received: value '[int]' for Vty Management
Explanation A message with an invalid field value was received for Vty Management
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_VTYMGT-3-MSGINVALIDFIELDSTR : Invalid field '[chars]' value '[chars]' in TDL message '[chars]' received for Vty Management
Explanation A message with an invalid field value was received for Vty Management
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_VTYMGT-3-MSGMARSHALERROR : Error '[dec]' marshaling TDL Vty Management message '[chars]': [chars]
Explanation An unexpected condition has occurred while IOS is marshaling TDL response message for Vty Management
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_VTYMGT-3-MSGMISSINGFIELD : Missing field '[chars]' in TDL Vty Management message '[chars]' received
Explanation A message missing a required field was received for Vty Management
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_VTYMGT-3-MSGVTYCOUNT : Invalid vty count [dec] detected on initialization
Explanation Upon initialization, the Vty Management subsystem checks that the number of available vtys for the platform is valid.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_VTYMGT-3-MSGVTYSVCINIT : Unable to initialize the Vty Management service listen port
Explanation The platform IPC services failed to register the Vty Management service's need for a listen port. The Vty Management service will be unable to process requests. IOS services will be unavailable to external access methods.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_RP_VTYMGT-3-SET_ACCESS_FAIL : Installing LIIN interface access control failed
Explanation This error happens when the Vty Management subsystem failed to set the access control function for the LIIN, possibly due to IOS out of memory or corruption. Persistent access features into IOS will not work.
Recommended Action LOG_STD_ACTION
IOSXE_SIP_SPA
%IOSXE_SIP_SPA-3-APS_CFG_FAIL : Failed to configure APS on [chars]: [chars].
Explanation The SPA driver failed to configure APS on an interface.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_SIP_SPA-3-APS_PGP_FAIL : APS PGP Message send failed toslot/tobay [dec]: [dec].
Explanation APS PGP between working and protect has failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_SIP_SPA-3-ASR1000IPCALLOCFAIL : Failed to allocate Common IPC buffer [chars]
Explanation The Carrier Card failed to allocate a buffer for communication with the Route Processor.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%IOSXE_SIP_SPA-3-BAD_IFCOMTYPE : Bad ifcom message type=[int]
Explanation The Route Processor (ASR1000-RP) passed down a message that the software was not prepared to handle.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%IOSXE_SIP_SPA-3-BADMALUCMD2 : Unsupported MALU cmd/arg0=[hex][hex], arg1arg2=[hex][hex] , hwidb=[chars]
Explanation The Route Processor (ASR1000-RP) passed down a command that the software was not prepared to handle.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%IOSXE_SIP_SPA-3-BADMALUCMD : Unsupported MALU command [dec], arg=[hex], pascb=[hex]
Explanation The Route Processor (ASR1000-RP) passed down a command that the software was not prepared to handle.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%IOSXE_SIP_SPA-3-C2W_MAIN_INIT_FAIL : Failed to initialize SPA main c2w bus for subslot [dec] (status = [dec])
Explanation The SPA driver is not able to initialize SPA main c2w. This indicates a hardware error.
Recommended Action No action is required.
%IOSXE_SIP_SPA-3-CMDNOINT : HWIDB Null for command [dec], port [hex]
Explanation The Route Processor passed down a port number that is unknown on the carrier card.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%IOSXE_SIP_SPA-3-DEVICE_ERROR : subSlot [dec], spatype [hex]. Device error: [chars]
Explanation An error related to a device on the SPA is detected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_SIP_SPA-3-EFC_CHAN_ERR : EFC error -interface [chars], vc [dec], anyphy [dec], err_code [dec] : [chars]
Explanation Failed to configure efc channel/parameters
Recommended Action Seach for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, LOG_STD_ACTION
%IOSXE_SIP_SPA-3-EFC_FC_MAP_FAIL : Failed to update EFC flow control identifier for interface [chars] (status = [dec])
Explanation The SPA driver is not able to update the datapath EFC flow control identifier for the interface specified in the message. This indicates a hardware error.
Recommended Action No action is required.
%IOSXE_SIP_SPA-3-EFC_PROV_FAIL : Failed to provision EFC for interface [chars] (status = [dec])
Explanation The SPA driver is not able to provision EFC for the interface specified in the message. This indicates a hardware error.
Recommended Action No action is required.
%IOSXE_SIP_SPA-3-EFC_UNPROV_FAIL : Failed to unprovision EFC for VC [chars] (status = [dec])
Explanation The SPA driver is not able to unprovision EFC for the interface specified in the message. This indicates a hardware error.
Recommended Action No action is required.
%IOSXE_SIP_SPA-3-FAST_NOTIFY_ERROR : Failed to send fast notification to [chars] for [chars] [chars].
Explanation The SPA driver failed to deliver a fast notification.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_SIP_SPA-3-FCI_NOT_SET : Bay [dec] -FCI type not set
Explanation An FCI type of zero was detected
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_SIP_SPA-3-FRR_CFG_FAIL : Failed to configure fast reroute on [chars]: [chars].
Explanation The SPA driver failed to configure fast rerouting on an interface.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_SIP_SPA-3-HWIDB_FAILURE : Creation: port [dec] vc [dec]
Explanation Failed to create a hwidb.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_SIP_SPA-3-INVALID_ANYPHY : Bay [dec] -Invalid anyphy number [int] for vc [dec]
Explanation Interface has invalid anyphy mumber
Recommended Action Seach for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start 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).
%IOSXE_SIP_SPA-3-INVALID_IF : Attempted to access HWIDB for port [int] on slot [dec] subSlot [dec]
Explanation The ASR1000 attempted to access the HWIDB associated with a non-existent port.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%IOSXE_SIP_SPA-3-IPCALLOCFAIL : Failed to allocate IPC buffer [chars]
Explanation The SPA failed to allocate a buffer for communication with the Route Processor (ASR1000-RP).
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%IOSXE_SIP_SPA-3-IPCPORT : Failed to [chars] IPC port '[chars]', error [chars]
Explanation The Linecard failed to create a port for communication with the Route Processor (ASR1000-RP).
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%IOSXE_SIP_SPA-3-IPCPORTFAIL : Failed to open IPC port '[chars]' [chars] with error [chars]
Explanation The RP failed to open a port for communication with a SPA module.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_SIP_SPA-3-IPCSENDFAIL : Failed to send IPC message [chars]
Explanation The Linecard failed to send a message to the Route Processor (ASR1000-RP).
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%IOSXE_SIP_SPA-3-ISR_RC_ERROR : ISR return code out of range. rc=[dec]
Explanation The ISR error return code is out of range.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_SIP_SPA-3-LINKREC_ERROR : Link record error -Bay [dec] vc [dec], error code [dec]
Explanation Error processing link record structure
Recommended Action Seach for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start 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).
%IOSXE_SIP_SPA-3-LVLTRTOOBIG : Loveletter length exceeds max, [int] bytes
Explanation The ASR1000-SIP line card attempted to send a large message to the Route Processor (ASR1000-RP).
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%IOSXE_SIP_SPA-3-MDR_BACKUP_FAIL : Minimal Disruptive Restart backup failed for slot [int], bay [int]; reason ([chars])
Explanation The SPA driver could not backup data required for Minimal Disruptive Restart process. The Minimal Disruptive Restart process for the SPA may be terminated as a consequence.
Recommended Action The Minimal Disruptive Restart backup is stored in RP harddisk or Bootflash. If sufficient space is available on these devices, copy the error message exactly as it appears, and report it to your technical support representative.
%IOSXE_SIP_SPA-3-MDR_BACKUP_OPEN_FAIL : Failed to open Minimal Disruptive Restart backup for slot [int], bay [int], type [dec]; reason ([chars])
Explanation The SPA driver could not open Minimal Disruptive Restart backup file. The Minimal Disruptive Restart process may be terminated as a consequence.
Recommended Action The Minimal Disruptive Restart backup is stored in RP harddisk or Bootflash. If sufficient space is available on these devices, copy the error message exactly as it appears, and report it to your technical support representative.
%IOSXE_SIP_SPA-3-MDR_BACKUP_READ_FAIL : Failed to read [dec] from Minimal Disruptive Restart backup for slot [int], bay [int], type [dec]; reason ([chars])
Explanation The SPA driver could not read from Minimal Disruptive Restart backup file. The Minimal Disruptive Restart process may be terminated as a consequence.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_SIP_SPA-3-MDR_BACKUP_WRITE_FAIL : Failed to write [dec] bytes to Minimal Disruptive Restart backup[chars] for slot [int], bay [int], type [dec]; reason ([chars])
Explanation The SPA driver could not write to Minimal Disruptive Restart backup file. The Minimal Disruptive Restart process may be terminated as a consequence.
Recommended Action The Minimal Disruptive Restart backup is stored in RP harddisk or Bootflash. If sufficient space is available on these devices, copy the error message exactly as it appears, and report it to your technical support representative.
%IOSXE_SIP_SPA-3-MDR_CONFIG_REPLAY : Configuration replay failed during Minimal Disruptive Restart for slot [int], bay [int]; reason ([chars])
Explanation The SPA driver failed to process config replay during Minimal Disruptive Restart. The Minimal Disruptive Restart process may be terminated as a consequence.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_SIP_SPA-3-MESSAGE_ERROR : Bay [dec]: [chars]
Explanation An unexpected error has occurred.
Recommended Action Seach for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, LOG_STD_ACTION
%IOSXE_SIP_SPA-3-NETCLK_FAIL : Failed to [chars] SPA reference clock on [chars]
Explanation The SPA driver is not able to correctly configure the SPA reference clock on the specified interface. This indicates a hardware error.
Recommended Action No action is required.
%IOSXE_SIP_SPA-3-NODISPATCH : Dispatch vector Null, cmd=[dec], dintf=[dec]
Explanation No command dispatch vector was found for the specified interface.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%IOSXE_SIP_SPA-3-POWER : Bay [dec] 12V power is [chars]
Explanation SPA 12V power fault indicator
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_SIP_SPA-3-SONET_CLOCK_FAILED : SPA Sonet clock has failed (status = [hex])
Explanation The SPA SONET clock has failed. SPAs that rely on the SPA SONET clock for proper operation, such as POS and ATM will be affected.
Recommended Action If the SPA Sonet clock does not recover, perform an OIR. LOG_STD_RECUR_ACTION
%IOSXE_SIP_SPA-3-SONET_CLOCK_RECOVERED : SPA Sonet clock has recovered (status = [hex])
Explanation SPA Sonet clock has recovered
Recommended Action No action is required.
%IOSXE_SIP_SPA-3-SPA_CTRL_EFC_CONFIG_FAILURE : Subslot, spa controller EFC configuration failure, error [dec]
Explanation Failed to configure SPA controller EFC
Recommended Action Seach for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, LOG_STD_ACTION
%IOSXE_SIP_SPA-3-SPA_CTRL_INIT_FAILURE : Subslot [dec], spa controller initialisation failure, error [dec]
Explanation Failed to initialise SPA controller
Recommended Action Seach for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, LOG_STD_ACTION
%IOSXE_SIP_SPA-3-SPA_ETHER_SUSPEND_ERROR : SPA ETHER process suspended too long; totally for [dec] milliseconds
Explanation The SPA ETHER process is not able to write to ezman as ezman is blocked for writes. Copy the error message exactly as it appears and report it to your technical support representative.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_SIP_SPA-3-SPA_INTF_ID_CC_ALLOC_FAILED : Failed to allocate interface identifiers for SPA ([chars]) in slot/bay: [int]/[int]
Explanation Failed to get CC buffer and flow control identifiers for the SPA in the specified subslot Traffic cannot flow through the SPA under this failure condition. This can happen if the system runs out of available identifiers.
Recommended Action Try to reduce the number of interfaces configured in the system either by physically removing the SPAs or by changing the system configuration
%IOSXE_SIP_SPA-3-SPI4_CONFIG_FAILURE : Bay [dec], spi4 configuration failure, error [dec]
Explanation Failed to configure SPI4 interface
Recommended Action Seach for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, LOG_STD_ACTION
%IOSXE_SIP_SPA-3-SPI4_INIT_FAILURE : Bay [dec] initialization failure
Explanation Failed to create SPI4 subblock
Recommended Action Seach for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, LOG_STD_ACTION
%IOSXE_SIP_SPA-3-SPI4_NOTSYNC : [chars]: Can not synchronize SPI4 bus (host: src [chars]in sync, sink [chars]in sync, spa: src [chars]in sync, sink [chars]in sync).
Explanation SPI4 bus between modular services card and SPA is not synchronized. It indicates either a not properly seated SPA, a hardware failure or an outdated ROMMON/FPGA image.
Recommended Action Ensure that the SPA is properly seated in its subslot and reseat it if required.
%IOSXE_SIP_SPA-4-MAX_BANDWIDTH : Total SPA bandwidth exceeds line card capacity of [int] Mbps
Explanation The total bandwidth of SPAs exceeds the rated capacity of this line card.
Recommended Action Refer to the line card guidelines for the maximum allowed aggregated SPA bandwidth for the line card
%IOSXE_SIP_SPA-4-MAX_BANDWIDTH_NS : Total SPA bandwidth exceeds line card capacity, full utilization of installed SPA interfaces is not supported
Explanation The total bandwidth of SPAs exceeds the rated capacity of this line card.
Recommended Action Refer to the line card guidelines for the maximum allowed aggregated SPA bandwidth for the line card
%IOSXE_SIP_SPA-4-SPABUS2 : Subslot [dec] SPA BUS access failed. No SPA present error
Explanation SPABUS has reported an error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_SIP_SPA-4-SPABUS : Subslot [dec], [chars] SPA BUS access failed. timeout=[int] err=[int] par=[int] err_c=[hex] addr=[hex] data =[hex]
Explanation SPABUS has reported an error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_SIP_SPA-6-LOGGERMSGTOOBIG : Logger message length ([int] bytes) exceeds the maximum allowed size
Explanation The carrier card attempted to send a large message to the Route Processor
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_SIP_SPA-6-OIR : Bay [dec] [chars] changed to [chars]
Explanation SPA OIR Sequence
Recommended Action No action is required.
IOSXE_SPA
%IOSXE_SPA-3-CREATE_TDLH_FAILURE : Failed to create SPA [dec]/[dec] handle
Explanation Failed to create message handle for SPA communication.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_SPA-3-CREATE_TDLMSG_FAILURE : Failed to create [chars] message for [chars].
Explanation Failed to create/allocate necessary TDL message for SPA communication.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_SPA-3-CREATION_FAILURE : slot=[dec] subslot=[dec], spa_type=[hex], lc_type=[hex].
Explanation Failed to create a SPA object.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_SPA-3-DIAG_CONFIG : [chars] did not complete [dec]/[dec]
Explanation An error has occured during diagnostic test.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_SPA-3-DISPATCH_INIT_TDLH_FAILURE : Failed to initialize dispatch path for SPA [dec]/[dec] handle
Explanation Failed to initialize dispatch path handle for SPA communication.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_SPA-3-DOMAIN_TDLH_FAILURE : [chars], rc = [dec]
Explanation Failed to bind message handle for SPA communication.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_SPA-3-INVALID_CPU_NUM : cpu= [dec], max cpu = [dec]
Explanation An invalid CPU number is specified in one of the internal APIs.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_SPA-3-INVALID_DATA_INSTANCE : interface type [chars], slot [dec] port [dec] vc [dec] : [chars]
Explanation Data required to support the interface is not available.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_SPA-3-INVALID_DB_NUM : db = [dec], max db = [dec], db intf = [dec], max db intf = [dec]
Explanation An invalid daughter board number is specified in one of the internal APIs.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_SPA-3-INVALID_HANDLE : Failed to get a valid IPC handle for type [int], slot [dec], subslot [dec].
Explanation The client handle was found to be NULL for the given type/slot/subslot.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_SPA-3-INVALID_IF_INDEX : index= [dec], spaType=[hex], slot [dec] subSlot [dec] slotunit [dec] vc [dec]
Explanation Index for the interface is not valid.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_SPA-3-INVALID_INDX_RANGE : index1= [dec], index2= [dec], maxIndex= [dec]
Explanation An invalid index range is specified in one of the internal APIs.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_SPA-3-INVALID_RP_SLOT_NUM : slot= [dec], max slot = [dec]
Explanation An invalid RP slot number is specified in one of the internal APIs.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_SPA-3-INVALID_SLOT_NUM : slot= [dec], max slot = [dec]
Explanation An invalid slot number is specified in one of the internal APIs.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_SPA-3-INVALID_SLOTUNIT_NUM : cardwide-port = [dec], max cardwide-port = [dec]
Explanation An invalid cardwide-port number is specified in one of the internal APIs.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_SPA-3-INVALID_SPA_TDL_CCAPI_USAGE :
Explanation Incorrect usage of an internal API that should only be used on CC.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_SPA-3-INVALID_SUBSLOT_NUM : subslot= [dec], max subslot = [dec]
Explanation An invalid subslot number is specified in one of the internal APIs.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_SPA-3-IPC_FAILURE : IPC failure while [chars]
Explanation An error has occurred while prepareing or sending an IPC message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_SPA-3-MEM_ALLOC_ERROR : [chars]
Explanation Memory allocation error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_SPA-3-NULL_BAY_PTR :
Explanation Pointer to SPA bay is NULL.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_SPA-3-NULL_SPA_PTR :
Explanation Pointer to a SPA object is NULL.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_SPA-3-NULL_VFT : [chars] virtual function table is not initialized. spaType=[hex]
Explanation A required function table is not initialized
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_SPA-3-NULL_VFUNC : [chars] vector is not initialized. spaType=[hex]
Explanation A required function vector is not initialized
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_SPA-3-POWER_CYCLE : [chars] occurred on Shared Port Adapter [int]/[int]
Explanation An error has occurred which will cause the Shared Port Adapter to be power cycled
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_SPA-3-SENDCFGFAIL : Failed to send configuration for [chars] to carrier-card for subslot=[dec]/[dec]
Explanation Sending configuration failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_SPA-3-SETUP_TDLH_FAILURE : Failed to set the alloc/free handler for SPA [dec]/[dec] handle
Explanation Failed to set the alloc/free handler for SPA communication.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_SPA-3-SPA_CREATION_FAILURE : slot=[dec] subslot=[dec], PID=[chars] lc_type=[hex].
Explanation Failed to create a SPA object.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_SPA-3-SPA_SETUP_FAILURE : Failed to properly setup for SPA communication on slot [dec], subslot [dec].
Explanation Discovery of the linux interface used to communicate with a SPA failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_SPA-3-UNSUPPORTED_DATA : Data conversion error ([chars], [hex])
Explanation An internal software error has occured when converting the data specified in the message from one representation to another.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_SPA-6-DUAL_RATE_CHANGE : [chars]: [chars]
Explanation Change in rate of the link.
Recommended Action No action is required.
%IOSXE_SPA-6-TDLMSG_INCOMPATIBLE : Failed to copy message [chars] to buffer, not allowed for current domain.
Explanation Failure to marshal a message indicates an incompatibility with the intended recipient.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_SPA-6-UPDOWN : Interface [chars], link down due to [chars]
Explanation Ethernet link is down due to remote/local fault.
Recommended Action Replace the faulty cable.
IOSXE_TIMESTAMP_ENGINE
%IOSXE_TIMESTAMP_ENGINE-3-TSU_ERR : An unexpected condition has occurred at module ([chars])
Explanation An unexpected condition has occurred at the Interface Module TSU.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_TIMESTAMP_ENGINE-4-ERROR : NULL
Explanation An unexpected condition has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
IOSXE_THROUGHPUT
%IOSXE_THROUGHPUT-3-CONF_FAILED : Configuration failed. Installed license does not support the throughput level. Please install the valid license
Explanation An error occurred when the throughput configuration was attempted.
Recommended Action None
%IOSXE_THROUGHPUT-3-EULA_NOT_ACCEPTED : The EULA has to be accepted prior to throughput configuration.
Explanation Users need to accept EULA to activate the license
Recommended Action Accept EULA for throughput license
%IOSXE_THROUGHPUT-3-INVALID_CONFIG : No valid license found for the configured throughput level: [chars] kbps
Explanation Users has the boot up throughput set to non-default level without having the valid license.
Recommended Action Install valid throughput license
%IOSXE_THROUGHPUT-3-INVALID_LEVEL : An invalid throughput level: [chars] kbps was selected.
Explanation The configured throughput level is unknown
Recommended Action None
%IOSXE_THROUGHPUT-3-SETUP_FAILED : Throughput level setup failed. Boot up will be at the default throughput
Explanation An error occurred when licensing tried to setup the througput
Recommended Action None
%IOSXE_THROUGHPUT-6-LEVEL : Throughput level has been set to [dec]00000 kbps
Explanation Throughput level has been set to a number
Recommended Action None
IOSXE_USB
%IOSXE_USB-3-ESHOW_USB : Internal Error locating database for USB Devices.
Explanation The mcp_usb_devices is incorrect and needs to be changed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
IOSXE_UTD
%IOSXE_UTD-3-ALLOC : Failed to allocate message
Explanation When attempting to program the dataplane there was not enough memory to allocate the message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_UTD-3-MESSAGE : Failed to send message
Explanation When the message was being prepared for sending to the data plane, there was an error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_UTD-4-MT_CONFIG_DOWNLOAD : UTD MT configuration download has [chars]
Explanation In UTD multitenancy mode, the configuration download to the container can take a while. Please be patient.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_UTD-4-MT_CONTAINER_MESSAGE_NAK : Container responded to UTD message with an error: [dec]
Explanation The container rejected the UTD message
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_UTD-4-MT_CONTAINER_MESSAGE_TIMEOUT : UTD message sent to the container has timed out
Explanation The UTD message sent to the container has timed out.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_UTD-4-MT_CONTAINER_SESSION_TIMEOUT : UTD container download has timed out
Explanation The container did not respond with an up/down status before the session timed out.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_UTD-4-MT_CONTAINER_STATUS_DOWN : UTD poll: container status is DOWN
Explanation The container sent a down status to the poll message
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_UTD-4-SIG_UPDATE_CFG : UTD signature updates have been configured -A brief service interruption at the time of update is expected
Explanation The UTD service will be restarted if a new signature package is found. During this time, if fail-close has been configured (recommended), traffic that would be inspected by UTD will be dropped. Otherwise (default), traffic that would be inspected by UTD will be allowed to pass uninspected. To minimize this service interruption, it is recommended to schedule this operation outside of normal business hours.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_UTD-4-SIG_UPDATE_EXEC : UTD signature update has been executed -A brief service interruption is expected
Explanation The UTD service will be restarted if a new signature package is found. During this time, if fail-close has been configured (recommended), traffic that would be inspected by UTD will be dropped. Otherwise (default), traffic that would be inspected by UTD will be allowed to pass uninspected. To minimize this service interruption, it is recommended to execute this operation outside of normal business hours.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_UTD-4-VERSION_INCOMPATIBILITY : UTD OVA version ([chars]) does not match supported UTD version ([chars])
Explanation The UTD OVA version does not match the required UTD version embedded in this IOS-XE version. This is an unsupported configuration and may behave unexpectedly.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
IOSXE_VMAN
%IOSXE_VMAN-3-MSGDISPATCH : Unable to dispatch received TDL message from Virt-manager
Explanation An unexpected condition has occurred while IOS was trying to dispatch a TDL message received from Virt-manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_VMAN-3-MSGINITFAIL : Failed to initialize required Virt-manager resource: [chars]
Explanation During the initialization of the resources required by Virt-manager, a failure occurred. This has prevented virtual services from being activated.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_VMAN-3-RSPMSGHDLR : Failed to deliver response message: [chars]
Explanation An unexpected condition has occurred while IOS was trying to deliver a response message to a virtual service received from Virt-manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
IOSXE_WD
%IOSXE_WD-2-HEARTBEAT_FAIL : Heartbeat is not emitted. Heartbeat count:[dec]
Explanation Failure in IOS to generate a heartbeat is an abnormal condition
Recommended Action This message may be related to an abnormal configuration and system load, or transient high processing demand. When reporting this message, copy the message text exactly as it appears, include the stack trace and report to your technical support representative
%IOSXE_WD-2-HOG_DETECT_FAIL : CPUHOG detection failed to start.
Explanation Failure in setting up CPUHOG detection mechanism is an abnormal condition
Recommended Action This message may be related to an abnormal configuration and system load, or transient high processing demand. When reporting this message, copy the message text exactly as it appears, include the stack trace and report to your technical support representative
IOSXE_UPGRADE_ROMMON
%IOSXE_UPGRADE_ROMMON-0-ROMMON_LOADTEST_FAIL : ROMMON FIPS_140-3 Load test *FAILED*: file [chars]
Explanation FIPS 140-3 Related Load test failed for the ROMmon.
Recommended Action Check the system messages to see if any messages appeared that might indicate the source of the ROMmon Load test problem. If you do not find any additional information indicating a correctable problem, collect all output on the screen, in particular the console port output after the upgrade rom-monitor command was entered and the output of show rom-monitor, and provide the collected information to a Cisco technical support representative.
%IOSXE_UPGRADE_ROMMON-0-ROMMON_UPGRADE_FAIL : ROMMON upgrade failed: partition [chars]
Explanation An attempt to upgrade the ROMmon failed.
Recommended Action Check the system messages to see if any messages appeared that might indicate the source of the ROMmon problem. If you do not find any additional information indicating a correctable problem, collect all output on the screen, in particular the console port output after the upgrade rom-monitor command was entered and the output of show rom-monitor, and provide the collected information to a Cisco technical support representative.
IOSXE_WCCP
%IOSXE_WCCP-4-ACELIMIT : Too many ACEs in MASK ACL, please switch to Hash mode
Explanation Mask merged ACL generate too many ACEs.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show ip access-lists command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_WCCP-4-BADACE : Access list contains invalid ace
Explanation An unexpected condition has occurred which is due to an invalid statement in the access list structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show ip access-lists command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_WCCP-4-NOACL : Access list is null
Explanation An unexpected condition has occurred which is due to the absence of an access list structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show ip access-lists command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_WCCP-4-NOINPUT : NULL input, [chars]
Explanation An unexpected condition has occurred which is due to the NULL value of the input parameter.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show ip wccp command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_WCCP-4-NOINTF : No [chars] interface info for Service Group ([dec], [dec], [int])
Explanation An unexpected condition has occurred which is due to the absence of MCP WCCP interface info for the specific service group.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show platform software wccp command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_WCCP-4-NOSTATS : WCCP [chars] message error
Explanation An unexpected condition has occurred which is due to the error in receiving WCCP stats update message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show platform software wccp <id> counters command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_WCCP-4-NOSTATSINTF : Interface handle [int] not exsit for the stats message
Explanation An unexpected condition has occurred which can't find the interface handle for the interface stats message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show platform software wccp <id> int counters command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_WCCP-4-NOSTATSSVC : Service Group ([dec], [dec], [int]) not exist for the stats message
Explanation An unexpected condition has occurred which can't find the service group for the service group stats message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show platform software wccp command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_WCCP-4-NOSVCGRP : [chars] Service Group ([dec], [dec], [int]) NOT exist
Explanation An unexpected condition has occurred which is due to the absence of the service group structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show ip wccp command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOSXE_WCCP-4-UNKNOWNDIR : Unknown [chars] interface direction [hex] for Service Group ([dec], [dec], [int])
Explanation An unexpected condition has occurred which is due to the unknown direction has been applied to the interface for the service group.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show platform software wccp command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
IOXN_APP
%IOXN_APP-3-CFGFAIL : [chars] [chars]
Explanation An unexpected condition resulted into failure to apply auto config
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOXN_APP-3-CLEANUPFAIL : Failed to create chasfs property to indicate cleanup of previous app installation (rc = [chars])
Explanation An unexpected condition resulted in failure to setup the start of an application.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOXN_APP-3-GSFAIL : [chars] [int]
Explanation An unexpected condition resulted into failure to start an application.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOXN_APP-3-INITFAIL : Failed to create chasfs property ioxman (rc =[chars]) or caf (rc = [chars]) is not up
Explanation An unexpected condition resulted into failure to start an application.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOXN_APP-3-MSGFAIL : Message dispatch failure ([chars]).
Explanation Message could not be dispatched to an application.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IOXN_APP-3-PREVOPFAIL : Overriding previous operation ([chars] iox) that is taking longer than [int] secs to complete
Explanation An unexpected condition resulted in failure to apply iox config
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
IP
%IP-3-BADIPALIGN : Invalid alignment in packet for IP. [chars]=[hex]
Explanation The packet data structure is misaligned. This condition may result in a small amount of overhead in processing IP traffic.
Recommended Action Enter a show hardware command and report the output, along with this error message, to your technical support representative.
%IP-3-BADSROUTE : Improper source route. Length [dec] Ptr [dec]
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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IP-3-CNTRFULL : IP counter block is full (setting protocol [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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IP-3-DESTHOST : src=[IP_address], dst=[IP_address], NULL desthost
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IP-3-ICMPRATELIMIT : [int]nreachables rate-limited within [int] milliseconds on [chars]. [int] log messages suppressed since last log message displayed on [chars]
Explanation An excessive number of packets are triggering log messages on this interface
Recommended Action change the log threshold with the icmp rate-limit command or find the source of the packets and block the packets from this router
%IP-3-ICMPRATELIMITDF : [int] DF unreachables rate-limited within [int] milliseconds on [chars]. [int] DF log messages suppressed since last log message displayed on [chars]
Explanation An excessive number of packets are triggering log messages on this interface
Recommended Action change the log threshold with the icmp rate-limit command or find the source of the packets and block the packets from this router
%IP-3-IPTOPOID : Topology ID [hex] is invalid, can't get the base topology ID.
Explanation An internal software error occurred
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IP-3-LOOPOUTIF : Output interface for packet has been changed for [dec] times and dropped -src=[IP_address], dst=[IP_address], hl=[int], tl=[int], prot=[int], in=[chars], nexthop=[IP_address], out=[chars]
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IP-3-LOOPPAK : Looping packet detected and dropped -src=[IP_address], dst=[IP_address], hl=[int], tl=[int], prot=[int], sport=[int], dport=[int] in=[chars], nexthop=[IP_address], out=[chars]options=[chars]
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IP-3-MAXIRDP : Attempt to send IRDP to proxies exceeding configurable limit: [dec], interface: [chars], secondary = [dec], proxy = [dec]
Explanation The sum of configured secondary addresses and configured proxy addresses exceeds the number of total addresses that the IRDP can support in its implementation.
Recommended Action Reduce the number of either the secondary IP addresses or proxy addresses configured for the interface.
%IP-3-NONALIAS : non-alias address [IP_address] in table [chars] found in IP alias list
Explanation The IP alias list holds IP aliases only but non-alias entries are found.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IP-3-NOOUTINTF : Output interface not available. source address: [IP_address], destination address: [IP_address], routing type: [int]
Explanation The output interface for this packet is not set
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IP-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IP-4-CLASS : Bad IP address and mask [IP_address]%m in class_resolve()
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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IP-4-DUPADDR : Duplicate address [IP_address] on [chars], sourced by [enet]
Explanation Another system is using your IP address.
Recommended Action Change the IP address of one of the two systems.
%IP-4-IPPOOLS : Detected a local pool and a DHCP pool with the same name: [chars]
Explanation A local pool and a DHCP pool have been configured with the same name. This may cause conflict during address allocations.
Recommended Action Change the name of one of the two pools
%IP-4-UNICASTRPF : IP unicast reverse-path check disabled on [chars]
Explanation The IP verify unicast reverse-path feature was disabled because CEF was disabled (either through configuration or due to an internal error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IP-4-ZERO_ADDR : Zero MAC address for [IP_address] in ARP cache
Explanation An entry in the ARP cache have a NULL MAC address
Recommended Action If this message recurs, call your technical support representative for assistance.
%IP-5-ACL : [chars]
Explanation Error occured in IP access checks.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IP-5-TURBOACL : [chars]
Explanation Error occured in intialisation of TURBOACL.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the <CmdBold> show process command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IP-5-WEBINST_COMP : Selected IP address [IP_address]
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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IP-5-WEBINST_KILL : Terminating DNS process
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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IP-5-WEBINST_RESP : Sending DNS response to [IP_address] (request was for [IP_address])
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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IP-5-WEBINST_START : Attempting web install from host [IP_address]
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.
%IP-6-L2MCASTDROP : Layer 2 Multicast packet detected and dropped, src=[IP_address], dst=[IP_address]
Explanation Layer 2 Multicast packet with Layer3 Unicast Destination was dropped.
Recommended Action No action is required.
%IP-6-PHYBCASTDROP : Physical broadcast packet detected and dropped, src=[IP_address], dst=[IP_address]
Explanation Physical broadcast packet was dropped.
Recommended Action No action is required.
IPA
%IPA-3-INVMBXCMD : [chars]: invalid mailbox command: [hex]
Explanation A subsytem attempted to register a mailbox command that is out of range.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPA-3-NEVER : bay [[chars]] mailbox response timed out after ([int] + [int]) usecs, mbx=[hex]
Explanation A mailbox command sent from driver to the channel port adapter never completed within the expected time limit. As a result of this error, the channel port adapter driver will reset the port adapter and reload microcode to it.
Recommended Action The reset and reload rectified the problem. If that did not occur, then try the <Bold> microcode reload <NoBold> operation again. <Body><par>If the error still occurs, record the output from the following commands: <Bullet><par><Bold>show tech <NoBold> <Bullet><par><Bold>dir slot0: <NoBold> <Bullet><par><Bold>dir slot1: <NoBold> <Bullet><par><Bold>show log <NoBold> <Body><par>Provide this information to your technical support representative.
%IPA-3-PORTCONN : bay [[int]] failed to establish [chars] connection ([hex])
Explanation An attempt to establish the console or debugger connection with the channel port adapter failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPA-3-PORTIOKILL : Port IO [chars] process terminating.
Explanation Unexpected termination of a port io process.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPA-3-UKNMBXCMD : [chars]: unknown mailbox command: [hex] [hex] [hex] [hex]
Explanation The channel port adapter sent a mailbox command that the driver did not expect. This may occur if there is a version mismatch between the system image and the microcode.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
IPACCESS
%IPACCESS-2-NOMEMORY : Alloc fail for acl-config buffer. Disabling distributed mode on lc
Explanation Unable to malloc a buffer to send access-list configuration down to linecards.
Recommended Action Enter a show chunks command and report the output, along with this error message, to your technical support representative.
%IPACCESS-2-WRONGREQUEST : Invalid request to allocate chunk of size [dec]
Explanation We only allow acl chunks of max size IPACCESS_LARGE_CHUNK_SZ
Recommended Action None
%IPACCESS-2-WRONGSIZE : Incorrect length acl ipc xdr of type=[chars] len=[dec] received
Explanation Received an acl message of the wrong size for that type
Recommended Action Report this error message, to your tech support representative.
%IPACCESS-3-SANITY_ERROR : [chars]
Explanation A sanity error occurred while the ACL was being configured on the RP, or while the ACL configuration was being downloaded to the line card.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPACCESS-3-XDRREGISTRATION : Failed to register [chars] XDR client due to [chars]
Explanation Failure to register the said XDR client.
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative.
%IPACCESS-4-INVALIDACL : Invalid ACL field: [chars] is [dec]
Explanation An internal software error occurred.
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative.
IPC
%IPC-3-LOG_ERR : [chars] CPP QoS Client Proxy failure
Explanation QoS proxy failed because of receiving invalid sub-type or failed to allocate ipc response buffer.
Recommended Action LOG_STD_ACTION
IPC_LOG
%IPC_LOG-3-IPC_LOGWRITE_FAILED : ipc log write [int] bytes failed because [chars]
Explanation An internal logging mechanism failed to write a message.
Recommended Action No action is required. However, if router performance is noticeably degraded, contact Cisco Technical Assistance. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/c/en/us/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
IPC_TEST
%IPC_TEST-3-INVALID_SUBTYPE : CPP IPC TEST Proxy subtype [int]
Explanation IPC test proxy failed because of receiving invalid sub-type.
Recommended Action LOG_STD_ACTION
%IPC_TEST-3-MEM_ALLOC_FAILED : CPP IPC TEST Proxy mem alloc
Explanation IPC test proxy failed because the GPM allocation failed.
Recommended Action None
%IPC_TEST-3-REPLY_FAILED : CPP IPC TEST Proxy send reply
Explanation IPC test proxy failed because the reply failed to send.
Recommended Action None
IPFAST
%IPFAST-2-FAILOPENIPCPORT : Could not open the IPC ports. [chars]
Explanation ipfast could not open the ipc port to communicate to the LC/RRP/SP.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPFAST-2-INVALSIZE : The IP fast path received an IPC message with an invalid size(size/type -[dec]/[dec])
Explanation The IP fast path switching module has received an IPC message with an invalid size.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPFAST-2-IPCACHEINIT : Error initializing IP fast cache structures
Explanation A programming error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%IPFAST-2-MSGDROP : IPC queue limit is reached and message is dropped. queue limit = [dec] cumulative drops = [dec]
Explanation IPC raw queue limit for IP fast path is reached.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPFAST-2-RADIXINIT : Error initializing IP fast cache structures
Explanation A programming error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPFAST-6-PAKSHORT : Packet too short from [IP_address], datagram size [dec], tl [dec]
Explanation An IP packet which is too short was received
Recommended Action No action is required.
IPFLOW
%IPFLOW-2-CACHEINIT : Error initializing IP flow cache
Explanation Initialization of the Flow cache could not be accomplished because of a low memory condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPFLOW-2-EXPORTINIT : Error initializing Flow Export queue
Explanation Initialization of the Flow export queue could not be accomplished because of a low memory condition.
Recommended Action Reduce other system activitiy to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
%IPFLOW-2-PROCESSINIT : Error initializing Flow background process
Explanation Initialization of the Flow background process could not be accomplished because of a low memory condition.
Recommended Action Reduce other system activitiy to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
%IPFLOW-2-QUEUEINIT : Error initializing Flow feature queue
Explanation Initialization of the Flow feature queue could not be accomplished because of a low memory condition.
Recommended Action Reduce other system activitiy to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
%IPFLOW-2-TEMPLATETBL_INIT : Error initializing Flow Export Template Table
Explanation Initialization of the Flow export template table could not be accomplished because of a low memory condition.
Recommended Action Reduce other system activitiy to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
%IPFLOW-3-DISABLEFLOWEXPORT : NULL
Explanation Flow export is disabled because export destination address matches with one of the interface's IP addresses
Recommended Action IP addresses of all the interfaces must be checked to make sure none of them matches with flow export destination IP address.
%IPFLOW-3-SBINIT : Error initializing [chars] subblock data structure. [chars]
Explanation Initialization of the specified subblock data structure could not be accomplished.
Recommended Action None
%IPFLOW-4-V9_TEMPLATE_EXPORT : Error creating [chars]
Explanation Version 9 export template length is zero
Recommended Action This is a debug message only. No action is required.
IPMOBILE
%IPMOBILE-0-IPMOBILE_DHCP : [chars]
Explanation Two reasons for this error message, 1. DHCP Client failed to get started, this could be because of malloc failures. 2. IPMOBILE DHCP Process failed to start
Recommended Action If this error message is seen it is recommended not to use this HA for binding creation with DHCP Address Allocation. Check the available memory in the box and for the first reason try to get 'debug dhcp detail' before the failure. Contact your technical support representative with the error message you got.
%IPMOBILE-0-NOPROCESS : [chars]
Explanation A Process could not be started
Recommended Action Please contact your technical support representative with the error message you got and with the output of 'show process '.
%IPMOBILE-2-ASSERTFAILED : IPMOBILE assertion failed: [chars]
Explanation The software detected an inconsistency. This is considered a serious error. The router attempts to continue, but IP Mobility processing may be impaired.
Recommended Action Copy the error message exactly as it appears, noting any IP Mobility problems that you are experiencing, and report it to your technical support representative.
%IPMOBILE-3-CONFIGERROR : Standby FA configuration is not in sync with the active
Explanation The software detected an inconsistency in configuration between the standby and the active. Standby FA may not proceed with the sync for this visitor.
Recommended Action Re-configure standby FA and make sure the configuration between the standby and the active is in sync.
%IPMOBILE-3-NOSOCKET : Unable to open socket
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.
%IPMOBILE-3-NOTUNNEL : Maximum number of tunnels [dec] reached
Explanation The number of Mobile IP tunnels allowed on the box is reached.
Recommended Action This occures if the HA/FA is overloaded. If you suspect this condition contact technical support representative with the output of show tech
%IPMOBILE-3-SA_PARSE_FAILED : Error in parsing the security association for [chars]
Explanation The Mobile IP Home Agent encountered an error while processing the Security Association in the RADIUS Access-Accept message.
Recommended Action Check the Radius profile config for the Mobile Node for which the processing of the Security Association failed.
%IPMOBILE-5-MIP_TUNNELDELETE : Mobile IP tunnel [chars] deleting
Explanation The Mobile IP tunnel is going to be deleted.
Recommended Action This occurs if the active mobile ip binding is deleted. If you suspect this condition contact technical support representative with the output of show tech
%IPMOBILE-6-DUPMOBNET : Unable to [chars] dynamic mobile network [IP_address] [IP_address] for MR [chars]; already [chars] MR [chars]
Explanation A mobile router's attempt to dynamically add or delete a mobile network failed because that mobile network was already statically configured for or dynamically registered by another mobile router. A mobile network may be configured or registered for only one mobile router.
Recommended Action To avoid duplication errors, check the static mobile network configuration on the HA or the dynamic mobile network configuration on the mobile router(s).
%IPMOBILE-6-DUPVIRTNET : Unable to [chars] dynamic mobile network [IP_address] [IP_address] for MR [chars]; already configured as a virtual network
Explanation A mobile router's attempt to dynamically add or delete a mobile network failed because that mobile network was already configured as a virtual network in the home agent.
Recommended Action To avoid duplication errors, make sure that the virtual networks configuration on the home agent and the dynamic mobile network configuration on the mobile router do not have any overlapping network prefixes.
%IPMOBILE-6-REDUPDATEFAIL : Too many redundancy update failures ([dec]) in the last minute.
Explanation The standby HA attempts to update its binding table by contacting the active HA several times each minute. Some or all of these attempts failed and the number of failures exceeded a threshhold number.
Recommended Action Ensure connectivity between the active HA and the standby HA. Also make sure the clocks are in sync between the two and that the security associations are properly set between the two. If the preemption delay is set, try setting it to a shorter time period.
%IPMOBILE-6-SECURE : Security violation on [chars] from [chars] [chars] -errcode [chars] ([dec]), reason [chars] ([dec])
Explanation A security violation occurred during registration attempt.
Recommended Action This is for informational purpose only.
IPNAT
%IPNAT-3-BADMAPPINGTYPE : NAT mapping type [dec] for mapping statistics from platform is invalid
Explanation The mapping type for passing mapping statistics from platform is not for static nor dynamic mapping type which is invalid. This condition can cause the statistic counters for NAT mapping to be inaccurate on the RP
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPNAT-3-CONFIG : Unable to [chars] the configuration of dynamic mappings
Explanation An internal operation relating to the configuration of the dynamic mappings has failed. This may imply that the mapping has not been installed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPNAT-3-CSBNULL : Parser structure for route-map [chars] configuration is nul
Explanation The parser structure for route-map configuraion is nul which is invalid. This condition can cause the new translations to fail in the data path
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPNAT-3-IF_UP : Error in sending interface UP event for [chars] to the ager process
Explanation An internal operation relating to the interface UP event has failed which is unexpected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPNAT-3-LIMITSTATSNULL : NAT mexentry statistics structure from platform is null
Explanation The structure for passing maxentry limit statistics from platform is nul which is invalid. This condition can cause the statistic counters for NAT maxentry limit to be inaccurate on the RP
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPNAT-3-MAPPING_NULL : Unexpected NULL pointer received as input.
Explanation An internal operation relating to notifying the platform about a mapping has provided an unexpected input.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPNAT-3-MAPPINGSTATSNULL : NAT mapping statistics structure from platform is null
Explanation The structure for passing mapping statistics from platform is nul which is invalid. This condition can cause the statistic counters for NAT mapping to be inaccurate on the RP
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPNAT-3-POOLSTATSNULL : NAT pool statistics structure from platform is nul
Explanation The structure for passing global/systems stats from platform is nul which is invalid. This condition can cause the statistic counters for NAT pool to be inaccurate on the RP
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPNAT-3-PORTLISTNULL : Portlist for address [IP_address] proto [dec] is null
Explanation The portlist for the address which requests more port blocks is nul which is invalid. This condition can cause the new translations to fail in the data path
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPNAT-3-PORTNULL : Start port or end port for port block allocation request is null
Explanation Start port or end port for port block allocation request is nul, This condition can cause the new translations to fail in the data path
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPNAT-3-RTMAPNAMENULL : Route-map name for [chars] configuration is nul
Explanation The route-map name is nul which is invalid. This condition can cause the new translations to fail in the data path
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPNAT-3-RTMAPNULL : route-map for configuration download is nul
Explanation The route-map structure is nul which is invalid. This condition can cause the new translations to fail in the data path
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPNAT-3-SBINIT : Error initializing [chars] subblock data structure. [chars]
Explanation Initialization of the specified subblock data structure could not be accomplished.
Recommended Action None
%IPNAT-3-SYSSTATSNULL : NAT global/system statistics structure from platform is nul
Explanation The structure for passing global/systems statistics from platform is nul which is invalid. This condition can cause the NAT global statistic counters in inaccurate on the RP
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPNAT-4-ADDR_ALLOC_FAILURE : Address allocation failed for [IP_address], pool [chars] might be exhausted
Explanation An address could not be allocated from the IP NAT pool. This condition can cause a translation failure and might result in packets being dropped. The counter for misses will be incremented for these packets.
Recommended Action Check to see if the NAT pool has been exhausted. To reuse any existing addresses in the NAT pool for new packet flows, clear the current NAT entries using clear ip nat translation *
%IPNAT-3-UNEXPECTED_ADDRESS : NULL
Explanation An address contained an unexpected value.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPNAT-3-UNEXPECTED_MAPPING_FLAG : Unexpected mapping flag %#04x received
Explanation An internal operation relating to notifying the platform about a mapping has provided an unexpected input.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPNAT-3-WLANSESSNULL : NAT WLAN session structure for session [chars] from platform is null
Explanation The structure for passing WLAN session from platform is nul which is invalid. This condition can cause the NAT WLAN session to fail in the data path
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPNAT-6-ENTRIES : Static translation count reset, inside/outside source/destination [int]/[int] [int]/[int]
Explanation Upon the removal of the last remaining static translation from the configuration it has been determined that there is a discrepancy with the internal accounting as regards the previous provisioning of inside source/destination versus outside source entries. The internal accounting has been reset to indicate that there are no translations of any type currently.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPNAT-6-ID : [chars] identifier has wrapped
Explanation The identifier which is assigned to that which is resultant from the configuration in question has cycled through the available number space and is now allocating from its initial value again.
Recommended Action No action is required.
%IPNAT-6-PORT_ALLOC : Port allocation via [chars] for [int] [chars] [chars] ports, min [int] max [int]
Explanation A port allocation request for the specified range of ports has been attempted from the named party on the standby RP. This is an informational message which tracks the request source.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
IPNAT_HA
%IPNAT_HA-3-ATTRIBUTE : Bulk sync of [chars] via [chars], [chars] is invalid for [chars]
Explanation An attempt to bulk sync an address pool or a dynamic/static translation has detected that the entity which is to be sent to the standby RP when acting in a stateful redundant mode contains an invalid owner property and hence cannot be synchronized. The detection of this case will result in a failure of the bulk sync.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPNAT_HA-3-BULK_SYNC : Failed to send [chars] information to peer
Explanation The bulk synchronization of the NAT configuration to the standby RP has failed to complete successfully; NAT has therefore taken the action which will result in a reload of the peer in order to once more attempt to successfully synchronize the configuration state which may have failed initially to a transient condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPNAT_HA-3-CLIENT : Failed to register with [chars], [chars]
Explanation The NAT High Availability has failed to register with the specified component during initialization. This is an internal error which indicates that the NAT HA services will be unavailable.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPNAT_HA-3-DECODE : Decode via [chars] of [chars] failed
Explanation A message of the transport and type described failed in its attempt to be decoded on the standby. The resultant action taken by the standby route processor is an attempt to resynchronize.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPNAT_HA-3-DYN_DEFERQ : [chars] failed to defer[chars]
Explanation The incremental synchronization of the NAT dynamic state to the standby RP has failed to add the information to the deferral queue for later processing during the time where the standby RP is progressing to it's hot standby redundant state. This implies that the runtime state between the active and standby RP would be inconsistent once the standby has been fully initialized.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show ip nat ha command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPNAT_HA-3-DYN_SYNC : Failed to process [chars] dynamic state
Explanation The incremental synchronization of the NAT configuration to the standby RP has failed to complete successfully. This implies that the configuration state between the active and standby RP is inconsistent.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show ip nat ha command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPNAT_HA-3-INTERFACE_TYPE : [chars] type/slot [hex] unit [int] num [int] channel [int] value [int]
Explanation An attempt to sync a dynamic translation or address change has detected that the interface which was encoded on the active RP has a different type the standby RP. The detection of this case will result in a failure of the bulk or LBL sync.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPNAT_HA-3-ISSU : [chars] [chars] failed; [chars]
Explanation An operation pertaining to the ISSU support for NAT failed to complete using either the CF or IPC transport context with the reason specified
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPNAT_HA-3-MISMATCH : [chars] [chars] mismatch with id [int]
Explanation The specified synchronization operation has failed to complete on the standby route processor due to an inconsistency in the internal id which would have resulted in an inconsistent configuration between active and standby. The resultant action taken by the standby route processor is an attempt to resynchronize.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPNAT_HA-3-NEGOTIATION : Failed to start ISSU [chars] session negotiation; [chars]
Explanation The ISSU negotiation with the peer failed to start for either the CF or IPC transport with the reason specified.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPNAT_HA-3-PROGRESSION : Unable to inform RF of bulk sync completion; [chars]
Explanation The active route processor has sent a notification to the standby to inform of the completion of the bulk synchronization of the NAT configuration. The standby has failed to respond to the active informing that it received the notification noting the reason for the failure. The resultant action taken by the standby route processor is an attempt to resynchronize.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPNAT_HA-3-PURGE : Failed to purge [chars] information
Explanation The synchronization of the NAT configuration state to the standby RP has failed to purge an entry which has been deemed to be stale; NAT has therefore taken the action which will result in a reload of the peer in order to once more attempt to successfully synchronize the configuration state which may have failed initially to a transient condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPNAT_HA-3-RECEIVE : Message via [chars] is [chars]
Explanation An attempt to receive and process a versioned negotiation or synchronization message has failed due to an internal error being detected by the information received from the IPC or CF components.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPNAT_HA-3-REGISTRATION : ISSU [chars] failed for [chars]; [chars]
Explanation An ISSU registration for the set of initial capabilities and sessions failed due to the reason specified. This will have the effect of the NAT ISSU support being unavailable between peers.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPNAT_HA-3-TRANSFORM : [chars] of [chars] via [chars] failed [chars]
Explanation An attempt to either encode or decode a versioned synchronization message has failed due to an internal error encountered by the ISSU component.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPNAT_HA-3-TRANSMIT : Unable to send via [chars] [chars] [chars] [chars]; [chars]
Explanation An attempt to send a versioned negotiation or synchronization message has failed due to an internal error encountered by the IPC or CF components.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPNAT_HA-6-ADDR_CHANGE : [chars] unable to encode data descriptor for interface [chars]
Explanation An attempt to sync an address change to the standby RP has detected that the interface which was to be encoded on the active RP is no longer present or does not support encoding. The interface may have been removed from the configuration or may not support encoding.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPNAT_HA-6-INTERFACE : [chars] type/slot [hex] uint [int] num [int] channel [int]
Explanation An attempt to sync a dynamic translation or address change has detected that the interface which was encoded on the active RP is not present on the standby RP. The detection of this case may result in a failure of the bulk or LBL sync.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPNAT_HA-6-MAPPING_COMPARE : [chars] [chars] [chars] mapping id [int] comparing [chars] [chars] [chars] mapping id [int]
Explanation The specified synchronization operation on the standby route processor has detected an internal condition with respect to the properities of dynamic mappings. This is informational.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPNAT_HA-6-MAPPING_EXISTS : [chars] [chars] [chars] mapping id [int]
Explanation The specified synchronization operation on the standby route processor has detected the presence of an existing matching mapping. This may be associated with any observed PRC failures on the standby.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPNAT_HA-6-READY : [chars] peer not ready, discarding [chars]
Explanation The synchronization attempt for the message has determined that the transport has lost communication with its peer. This is a normal situation which indicates that the standby route-processor is currently out of service implying a simplex redundancy mode.
Recommended Action None
%IPNAT_HA-6-RELOAD : [chars], reloading [chars]
Explanation A synchronization attempt between the active and standby RP peers has failed with the reason indicated. The standby peer is reloaded in an attempt to resynchronize when operating in a stateful redundant mode.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPNAT_HA-6-RELOAD_DISABLED : Standby reload has been disabled, NAT RP state is out of sync and the standby should be reloaded manually
Explanation The active and standby RPs are out of sync and the standby RP would have been reloaded, but this reload was suppressed based on the configured environment.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPNAT_HA-6-TIMEOUT : Bulk sync is flow controlled by [chars]
Explanation The bulk synchronization of the NAT configuration to the standby RP has encountered a flow control condition which has effected a timeout awaiting the condition to clear. This will result in a reload of the standby RP to allow the bulk synchronization to restart.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
IPSEC
%IPSEC-3-ANTI_REPLAY : SA ([hex],[hex])
Explanation Anti Replay check failed for the SA.
Recommended Action LOG_STD_ACTION
%IPSEC-3-CHUNK_CREATE_FAIL :
Explanation Chunk creation failed
Recommended Action LOG_STD_ACTION
%IPSEC-3-CHUNK_DESTROY_ERROR :
Explanation Chunk destroy error, force cleanup
Recommended Action LOG_STD_ACTION
%IPSEC-3-CHUNK_DESTROY_FAIL :
Explanation Chunk destroy failed
Recommended Action LOG_STD_ACTION
%IPSEC-3-DROP : result type [hex]
Explanation Classification results in Drop.
Recommended Action LOG_STD_ACTION
%IPSEC-3-FOR_US_CLEARTEXT_POLICY_FAIL :
Explanation Policy fail for For-Us cleartext packet.
Recommended Action LOG_STD_ACTION
%IPSEC-3-FRAG_ERROR : IPSec SA received fragmented ESP packet, DP Handle [dec], src_addr %Ci, dest_addr %Ci, SPI ([hex]), MSGDEF_LIMIT_GLACIAL
Explanation Fragmented ESP packet is received for this IPSec session.
Recommended Action LOG_STD_ACTION
%IPSEC-3-FRAG_ERROR_IPV6 : IPSec SA received fragmented ESP packet, DP Handle [dec], ipv6 src_addr %CI, ipv6 dest_addr %CI, SPI ([hex]), MSGDEF_LIMIT_GLACIAL
Explanation Fragmented ESP packet is received for this IPSec session.
Recommended Action LOG_STD_ACTION
%IPSEC-3-FRAG_MPASS :
Explanation Multipass Error
Recommended Action LOG_STD_ACTION
%IPSEC-3-HMAC_ERROR : IPSec SA receives HMAC error, DP Handle [dec], src_addr %Ci, dest_addr %Ci, SPI [hex], MSGDEF_LIMIT_GLACIAL
Explanation HMAC calculation error is encountered for this IPSec session.
Recommended Action LOG_STD_ACTION
%IPSEC-3-HMAC_ERROR_V6 : IPSec SA receives HMAC error, DP Handle [dec], ipv6 src_addr %CI, ipv6 dest_addr %CI, SPI [hex], MSGDEF_LIMIT_GLACIAL
Explanation HMAC calculation error is encountered for this IPSec session.
Recommended Action LOG_STD_ACTION
%IPSEC-3-IKE_TED_MSG_LIMIT : cnt [dec], sp [hex], cp sp [hex]
Explanation IKE TED Message Limit exceeded.
Recommended Action LOG_STD_ACTION
%IPSEC-3-IKE_TED_MSG_RATE : cnt [dec], sp [hex], cp sp [hex]
Explanation IKE TED Message Rate exceeded.
Recommended Action LOG_STD_ACTION
%IPSEC-3-IN_POLICY_FAIL : out sa ([hex],[hex]), out sp ([hex],[hex]), in sa ([hex],[hex]), in sp ([hex],[hex])
Explanation In-Out SP mis-match.
Recommended Action LOG_STD_ACTION
%IPSEC-3-IN_POLICY_MISS : sa [hex], cp sa [hex]
Explanation TCAM miss.
Recommended Action LOG_STD_ACTION
%IPSEC-3-INTF_NOT_CFG :
Explanation Got an encrypted packet on an interface on which ipsec is not configured.
Recommended Action LOG_STD_ACTION
%IPSEC-3-INVALID_PROT : invalid ipsec prot [hex]
Explanation Got an invalid IPSEC protocol value.
Recommended Action LOG_STD_ACTION
%IPSEC-3-INVALID_SA : sa [hex], cp sa [hex]
Explanation SA is invalid.
Recommended Action LOG_STD_ACTION
%IPSEC-3-INVALID_SPI : spi [hex]
Explanation Got an invalid SPI value.
Recommended Action LOG_STD_ACTION
%IPSEC-3-INVALID_VAL : val [hex]
Explanation Invalid value seen.
Recommended Action LOG_STD_ACTION
%IPSEC-3-IPC_ERR_SA : rc [hex]
Explanation An error has occurred sending SA Byte Lifetime expiry event.
Recommended Action LOG_STD_ACTION
%IPSEC-3-IPC_HANDLER_ERR : rc [hex]
Explanation Error setting IPC Handler.
Recommended Action LOG_STD_ACTION
%IPSEC-3-IPC_INVALID_MSG_LEN : [dec]:[dec] len [dec] flags [hex] source [dec]
Explanation Invalid IPC message length
Recommended Action LOG_STD_ACTION
%IPSEC-3-IPC_PAK_ALLOC : sp [hex], cp sp [hex]
Explanation IPC pak allocation failed.
Recommended Action LOG_STD_ACTION
%IPSEC-3-IPC_PAK_ALLOC_SA_EVENT : event [hex], sa [hex]
Explanation IPC pak allocation failed.
Recommended Action LOG_STD_ACTION
%IPSEC-3-IPC_PAK_SEND : rc [hex], sp [hex], cp sp [hex]
Explanation IPC send failed.
Recommended Action LOG_STD_ACTION
%IPSEC-3-IPC_PAK_SEND_SA_EVENT : rc [hex], event [hex], sa [hex]
Explanation IPC send failed.
Recommended Action LOG_STD_ACTION
%IPSEC-3-MEM_ALLOC_REACHED_LIMIT : IPC type [hex]
Explanation Cannot allocate more memory to store state for IPSec Traffic, reached upper limit.
Recommended Action LOG_STD_ACTION
%IPSEC-3-MEM_EXTEND_FAILED : IPC type [hex]
Explanation Extending memory failed
Recommended Action LOG_STD_ACTION
%IPSEC-3-MEM_REQ_FAILED : IPC type [hex]
Explanation Requesting more memory failed.
Recommended Action LOG_STD_ACTION
%IPSEC-3-NO_MEMORY : No memory [hex]
Explanation No memory to send response back.
Recommended Action LOG_STD_ACTION
%IPSEC-3-PKT_TOO_BIG : IPSec Packet size [dec] larger than maximum supported size [dec] hence dropping it, MSGDEF_LIMIT_GLACIAL
Explanation Maximum size for packet with IPSEC encapsulation is 9K, This packet exceeded the size limit hence dropping it.
Recommended Action LOG_STD_ACTION
%IPSEC-3-RECVD_PKT_NOT_IPSEC : Rec'd packet not an IPSEC packet, dest_addr= %Ci, src_addr= %Ci, prot= [dec], MSGDEF_LIMIT_GLACIAL
Explanation Rec'd packet matched crypto map ACL, but is not IPSEC-encapsulated.
Recommended Action LOG_STD_ACTION
%IPSEC-3-RECVD_PKT_NOT_IPSECV6 : Rec'd packet not an IPSEC packet, dest_addr= %CI, src_addr= %CI, prot= [dec], MSGDEF_LIMIT_GLACIAL
Explanation Rec'd packet matched crypto map ACL, but is not IPSEC-encapsulated.
Recommended Action LOG_STD_ACTION
%IPSEC-3-REPLAY_ERROR : IPSec SA receives anti-replay error, DP Handle [dec], src_addr %Ci, dest_addr %Ci, SPI [hex], MSGDEF_LIMIT_GLACIAL
Explanation Anti-replay error is encountered for this IPSec session.
Recommended Action LOG_STD_ACTION
%IPSEC-3-REPLAY_ERROR_IPV6 : IPSec SA receives anti-replay error, DP Handle [dec], ipv6 src_addr %CI, ipv6 dest_addr %CI, SPI [hex], MSGDEF_LIMIT_GLACIAL
Explanation Anti-replay error is encountered for this IPSec session.
Recommended Action LOG_STD_ACTION
%IPSEC-3-SA_HARD_BYTE : SA ([hex],[hex])
Explanation SA Hardbyte Lifetime expiry event.
Recommended Action LOG_STD_ACTION
%IPSEC-3-SA_NOT_FOUND :
Explanation SA not found.
Recommended Action LOG_STD_ACTION
%IPSEC-3-SA_SOFT_BYTE : SA ([hex],[hex])
Explanation SA Softbyte Lifetime expiry event.
Recommended Action LOG_STD_ACTION
%IPSEC-3-SEQNO_OVERFLOW : SA ([hex],[hex])
Explanation Sequence Number overflow for the SA.
Recommended Action LOG_STD_ACTION
%IPSEC-3-TRANSIT_POLICY_FAIL :
Explanation Policy fail for transit ipsec packet.
Recommended Action LOG_STD_ACTION
%IPSEC-3-UNEXPECTED_ERROR : orh.w0 [hex], error_op [hex], SA ([hex],[hex])
Explanation Unexpected error for the SA.
Recommended Action LOG_STD_ACTION
IP_SNMP
%IP_SNMP-3-SOCKET : can't open UDP socket
Explanation The SNMP server was unable to open a port for receiving or transmitting SNMP requests. This usually happens when the SNMP server is started using the snmp-server community configuration command on a router or communication server with an interface that has no IP address configured. Another possible cause is low memory.
Recommended Action Configure at least one interface with an IP address or specify the no snmp-server command to remove the SNMP server process. Call your technical support representative if problems persist or if it becomes necessary to add memory.
%IP_SNMP-4-NOTRAPIP : SNMP trap source [chars] has no ip address
Explanation The user entered an snmp-server trap-source command. The interface requested for use as the source address has no ipv4 address associated with it. The SNMP trap is being sent anyway, but without the source address that the user intended.
Recommended Action There are two possible solutions. Either enter a no snmp-server trap-source command to disable the request for a specific source IP address, or add an IP address to the interface referenced in the snmp-server trap-source configuration command.
%IP_SNMP-4-NOTRAPIPV6 : SNMP trap source [chars] has no ipv6 address
Explanation The user entered an snmp-server trap-source command. The interface requested for use as the source address has no ipv6 address associated with it. The SNMP trap is being sent anyway, but without the source address that the user intended.
Recommended Action There are two possible solutions. Either enter a no snmp-server trap-source command to disable the request for a specific source IP address, or add an IPV6 address to the interface referenced in the snmp-server trap-source configuration command.
%IP_SNMP-4-TOOBIG : Oversize message from [IP_address], datagram size [int], udp length [int]
Explanation An incoming SNMP packet had a length field so large that the system had to assume it was in error. This system made a correct reaction to bad external data. Since SNMP packets should originate from systems under the same administration, this may indicate that the network host used to originate the SNMP request had a problem in its networking layer. Alternatively, if the SNMP packet originated from outside the local administrative domain, it could indicate an failed attempt at security penetration and that site should be watched more closely.
Recommended Action If the origin is local, no action is required. If the origin is determined to be malicious, either contact the administrator of the originating site or install filters to prevent access by that site, as circumstances warrant.
IP_TUNNEL
%IP_TUNNEL-2-IPC_INIT : IPC message handler registration failure, rc [int]
Explanation Registering an IPC message handler for the Tunnel feature failed. This may cause the feature to not function.
Recommended Action This is normally a software issue. The consequences are that the tunnel feature may not function. LOG_STD_ACTION
%IP_TUNNEL-3-IPC_NORES : No space for the IPC reply, size [int]
Explanation For a request from upper TUNNEL 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
%IP_TUNNEL-3-IPC_OPEN_REPLY : IPC Open Reply failed, request [int]
Explanation For a request from upper TUNNEL 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
IPV4_FORWARDING
%IPV4_FORWARDING-2-CAUSE_THROTTLE_ERR : Allocation of ipv4 throttle [chars] memory failed
Explanation Allocation of memory resource use by ipv4 throttle fail
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPV4_FORWARDING-3-CAUSE_LINKTYPE_ERR : Unsupported link type -linktype = [dec], dropping packet
Explanation Link type is unsupported at the current time.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPV4_FORWARDING-3-TABLE_ID_SZ_ERR : Table ID size configured incorrectly: [dec]
Explanation Table ID size must be less than or equal to 16 or 32 bits.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPV4_FORWARDING-3-TRAFFIC_IDX_ERR : Traffic index invalid value: [dec] Buckets allocated: [dec]
Explanation Traffic index is greater than or equal to the buckets allocated
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPV4_FORWARDING-4-CHECKSUM_ERR : Checksum buffer walk failed
Explanation Internal problem occured during calculating segmented packet checksum.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
IPV4_REASS_PROXY
%IPV4_REASS_PROXY-3-PROXY_IPC_FRAG_INFO_MEM_EXTEND_FAILED :
Explanation Increasing of fragment information pool failed.
Recommended Action LOG_STD_ACTION
%IPV4_REASS_PROXY-3-PROXY_IPC_FRAG_INFO_MEM_INIT_FAILED :
Explanation Initialization of fragment information pool failed.
Recommended Action LOG_STD_ACTION
%IPV4_REASS_PROXY-3-PROXY_IPC_INIT_FAILED : [dec]
Explanation IPC handler initialization failed.
Recommended Action LOG_STD_ACTION
%IPV4_REASS_PROXY-4-PROXY_IPC_INVALID_MSG : [hex]
Explanation Received an invalid IPC messages subtype.
Recommended Action LOG_STD_ACTION
IPV6_ACL
%IPV6_ACL-6-ACCESSLOGDP : list [chars]/[dec] [chars] [chars] [IPV6 address] [chars]-> [IPV6 address] ([dec]/[dec]), [dec] packet[chars]
Explanation A packet matching the log criteria for the given access list was detected.
Recommended Action No action is required.
%IPV6_ACL-6-ACCESSLOGNP : list [chars]/[dec] [chars] [dec] [IPV6 address] [chars]-> [IPV6 address], [dec] packet[chars]
Explanation A packet matching the log criteria for the given access list was detected.
Recommended Action No action is required.
%IPV6_ACL-6-ACCESSLOGP : list [chars]/[dec] [chars] [chars] [IPV6 address]([dec]) [chars]-> [IPV6 address]([dec]), [dec] packet[chars]
Explanation A packet matching the log criteria for the given access list was detected.
Recommended Action No action is required.
%IPV6_ACL-6-ACCESSLOGSP : list [chars]/[dec] [chars] [chars] [IPV6 address] [chars]-> [IPV6 address], [dec] packet[chars]
Explanation A packet matching the log criteria for the given access list was detected.
Recommended Action No action is required.
IPV6_ADDRESS
%IPV6_ADDRESS-3-ADDRESS_CFG : [IPV6 address]/[dec] can not be configured on [chars], [chars]
Explanation An error was encountered while configuring an IPv6 address
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPV6_ADDRESS-3-INTERNAL : Internal 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPV6_ADDRESS-3-NO_PROCESS : Cannot start an IPv6 process; router will not process IPv6 packets.
Explanation An IPv6 process could not be started. This machine will not be able to process any IPv6 packets.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
%IPV6_ADDRESS-3-NO_UNIQUE_IDENTIFIER : Cannot determine an unique IPv6 identifier for the system. IPv6 will not be started.
Explanation An unique IPv6 Identifier could not be determined for the system. Therefore the IPv6 process will not be started. This machine will not be able to process any IPv6 packets.
Recommended Action Verify that there is at least one interface in this machine that supports IEEE-style addresses.
%IPV6_ADDRESS-3-NULLIDB : Uninitialized interface pointer -[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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPV6_ADDRESS-3-OPINPROGRESS : Operation in progress -[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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
IPV6_ADDRMGR
%IPV6_ADDRMGR-3-INTERNAL : Internal 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
IPV6_FORWARDING
%IPV6_FORWARDING-2-CAUSE_THROTTLE_ERR : Allocation of ipv6 throttle [chars] memory failed
Explanation Allocation of memory resource use by ipv6 throttle fail
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPV6_FORWARDING-3-CAUSE_LINKTYPE_ERR : Unsupported link type [chars], dropping packet
Explanation Link type is unsupported at the current time.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPV6_FORWARDING-3-TABLE_ID_SZ_ERR : Table ID size configured incorrectly: [dec]
Explanation Table ID size must be less than or equal to 16 or 32 bits.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPV6_FORWARDING-4-CHECKSUM_ERR : Checksum buffer walk failed
Explanation Internal problem occured during calculating segmented packet checksum.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
IPV6_POLICY_API
%IPV6_POLICY_API-4-IPV6_LOCALPOLICYOVERIDE : Local dynamic policy overriding static local policy
Explanation Static policy and dynamic local policy are configured. The dynamic local policy will override the static local policy.
Recommended Action Remove the static local policy config if desired.
%IPV6_POLICY_API-4-IPV6_POLICYOVERIDE : Dynamic policy overriding static on intf:[chars]
Explanation Static policy and dynamic policy are configured on the interface. The dynamic policy will override the static policy.
Recommended Action Remove the static policy config if desired.
IPV6_REASS_PROXY
%IPV6_REASS_PROXY-3-PROXY_IPC_FRAG_INFO_MEM_EXTEND_FAILED :
Explanation Increasing of fragment information pool failed.
Recommended Action LOG_STD_ACTION
%IPV6_REASS_PROXY-3-PROXY_IPC_FRAG_INFO_MEM_INIT_FAILED :
Explanation Initialization of fragment information pool failed.
Recommended Action LOG_STD_ACTION
%IPV6_REASS_PROXY-3-PROXY_IPC_INIT_FAILED : [dec]
Explanation IPC handler initialization failed.
Recommended Action LOG_STD_ACTION
%IPV6_REASS_PROXY-4-PROXY_IPC_INVALID_MSG : [hex]
Explanation Received an invalid IPC messages subtype.
Recommended Action LOG_STD_ACTION
IPV6_RIP
%IPV6_RIP-3-ALLOC_ERR : Memory allocation problem -RIPv6
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPV6_RIP-3-ALLOC_IPDB : Can't alloc iPDB structure -RIPv6
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPV6_RIP-3-ALLOC_PDB : Can't alloc PDB structure -RIPv6
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPV6_RIP-3-NULLIDB : Uninitialized interface pointer -RIPv6
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPV6_RIP-3-NULLIPDB : Uninitialized iPDB pointer -RIPv6
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPV6_RIP-3-NULLPAK : Uninitialized packet pointer -RIPv6
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPV6_RIP-3-NULLPDB : Uninitialized PDB pointer -RIPv6
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPV6_RIP-3-NULLPROTO : Uninitialized protocol pointer -RIPv6
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPV6_RIP-3-NULLSOC : Uninitialized socket pointer -RIPv6
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPV6_RIP-3-PROCESS_CREATE : Can't create process -RIPv6
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%IPV6_RIP-3-PROCESS_MSG_SEND : Can't send message to process -RIPv6
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
IP_VFR
%IP_VFR-3-INVALID_FRAG_LENGTH : [chars]: fragment length invalid -received from [IP_address], destined to [IP_address]
Explanation This message indicates that the router has encountered a ping-of-death sort of an attack
Recommended Action To prevent further attacks, its highly recommendated that an ACL be configured to drop any traffic from the sender
%IP_VFR-3-OVERLAP_FRAGMENTS : [chars]: from the host [IP_address] destined to [IP_address]
Explanation This message is logged whenever the router encounters overlap fragments. Overlap fragment means, offset of one fragment overlaps the offset of another fragment. For example, if first fragment's offset is 0 and length is 800, then the second fragments offset must be 800. If second fragment's offset is less than 800, that means the second fragment overlaps the first fragment.
Recommended Action This could possibly be an attack, configure a static ACL to prevent further overlap fragments from the sender
%IP_VFR-3-SYSTEM_ERROR : [chars]: IP VFR System failure -[chars]
Explanation This message indicates the misc errors in the VFR subsystem
Recommended Action None
%IP_VFR-4-FRAG_TABLE_OVERFLOW : [chars]: the fragment table has reached its maximum threshold [dec]
Explanation This means the number of datagrams reassembled at a time reached its maximum limit, increase the value of max-reassemblies using ip virtual-reassembly max-reassemblies <number>
Recommended Action None
%IP_VFR-4-TINY_FRAGMENTS : [chars]: from the host [IP_address] destined to [IP_address]
Explanation This message indicates that the router is receiving tiny fragments - meaning the initial fragment does not have complete layer 4 header
Recommended Action This is an informational message
%IP_VFR-4-TOO_MANY_FRAGMENTS : [chars]: Too many fragments per datagram (more than [dec]) -sent by [IP_address], destined to [IP_address]
Explanation This message indicates the datagram being reassembled has received more fragments than its threshold value
Recommended Action Check if the fragments received are from a genuine source, if so increase the value of max-fragments using the CLI ip virtual-reassembly max-fragments <number>
ISDN
%ISDN-1-NOMEMORY : no memory for [chars]
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.
%ISDN-2-ISDN_EXIT : [chars]
Explanation The ISDN task has terminated execution for the specified reason, and may cause CISCO IOS to terminate.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%ISDN-2-ISDN_FATAL : ISDN FATAL ERROR: file [chars], function [chars], message: [chars]
Explanation ISDN has detected a fatal system error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%ISDN-2-ISDN_GENERAL_TRACEBACK : [chars]:[dec]
Explanation A debug - traceback condition has occurred
Recommended Action No action is required.
%ISDN-3-ISDN_CCB_FREE : [chars]: CCB with call id [hex] on b channel [dec] was leaked, but has been freed by ISDN Housekeeping. Reason: [chars]
Explanation A data structure internal to ISDN has leaked.
Recommended Action No action is required.
%ISDN-3-ISDN_CCB_FREE_FAILS : [chars]: CCB with call id [hex] on b channel [dec] was leaked (reason: [chars]), and can't be free'd by ISDN Housekeeping.
Explanation A data structure internal to ISDN has leaked and we can't fix it for some reason.
Recommended Action No action is required.
%ISDN-3-ISDN_NLCB_FREE : [chars]: NLCB with call id [hex] was leaked, but has been freed by ISDN Housekeeping. Reason: [chars]
Explanation A data structure internal to ISDN has leaked.
Recommended Action No action is required.
%ISDN-3-ISDN_RESOURCE_UNAVAILABLE : [chars]: Resource not available, at [chars]:[dec]
Explanation Hardware resource could not be allocated
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%ISDN-3-LAYER2_DOWN : Layer 2 for Interface [chars], TEI [int] changed to down
Explanation This is an informational message but being logged as ERR at request from some customers. It is sent when an ISDN Layer2 logical link is down. It also shows the TEI associated with this logical link.
Recommended Action No action is required.
%ISDN-3-LAYER2_UP : Layer 2 for Interface [chars], TEI [int] changed to up
Explanation This is an informational message but being logged as an ERR at request from some customers. It is sent when an ISDN Layer2 logical link is up. It also shows the TEI associated with this logical link.
Recommended Action No action is required.
%ISDN-4-BAD_DSL_FOR_CREATE_DELETE_L2 : [chars]: isdn_create_delete_signalling_channel: Unknown DSL [int] for [chars]
Explanation The Creation/Deletion service for the L2 Signalling handlerfor the given DSL is missing
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%ISDN-4-GET_STATUS_STATE_FAIL : [chars]: isdn_get_status_state: Unknown DSL [int]
Explanation An attempt to retrieve the status of a DSL that is not currently configured.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%ISDN-4-INVALID_CALLEDNUMBER : Interface [chars], Ignoring call, LDN and Called Party Number mismatch
Explanation The incoming ISDN call is ignored because the Called Party Number does not match the LDN numbers configured in the router.
Recommended Action Correct the LDN in the router to match the Called Party Number delivered in the incoming setup message.
%ISDN-4-INVALID_EID : Interface [chars], Ignoring call, EndPoint Identifier (EID) mismatch
Explanation The incoming ISDN call is ignored because the EID delivered in the incoming setup message cannot be matched.
Recommended Action If EID is delivered in the setup message, use the <bold> isdn debugs <nobold> and <bold> show isdn status <nobold> commands to determine the current EID values. You may need to contact the service provider.
%ISDN-4-INVALID_EVENT : [chars]: Bad Event Received For Current State
Explanation The State Transition for the ISDN L2 Socket Process failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%ISDN-4-INVALID_SPID : Interface [chars], Spid[dec] was rejected
Explanation The SPID configured in the router has been rejected by the switch.
Recommended Action Determine the correct SPID, reenter the SPID and clear the BRI interface.
%ISDN-4-ISDN_CCB_LEAK : [chars]: CCB with callid [hex] on b channel [dec] has been leaked. Reason: [chars]
Explanation A data structure internal to ISDN has been leaked
Recommended Action No action is required.
%ISDN-4-ISDN_L2_INTERFACE_NOT_REGISTERED : [chars]: isdn_to_L2: Unknown DSL [int] for command [chars]
Explanation The ISDN Stack has not registered its L2 Message Handler
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%ISDN-4-ISDN_NLCB_LEAK : [chars]: NLCB leak detected. nlcb [hex] call id [hex] reason: [chars]
Explanation A data structure internal to ISDN has not been freed
Recommended Action No action is required.
%ISDN-4-ISDN_UNEXPECTED_EVENT : [chars]: Occurred at [chars]:[dec]
Explanation An unexpected event of significance has occurred
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%ISDN-4-OPEN_TEMP_SOCKET_FAIL : [chars]: Failed to Open Required Temporary Socket[chars]
Explanation The (Re)Open attempt for a required temporary socket failed,without this socket the L2 socket process will fail
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%ISDN-4-RESTART : Interface [chars] [chars] [chars] message with restart class of [chars] chan [dec]
Explanation This is an informational message but will logged as a warning message if so configured.
Recommended Action No action is required.
%ISDN-4-RLM_STATUS_CHANGE : ISDN SC [chars]: Status Changed to: [chars].
Explanation ISDN has been notified by the RLM component of a status change in the RLM link
Recommended Action No action is required.
%ISDN-4-SERV_AUDIT_C1 : Interface [chars] service audit trigger condition [dec] on channel [dec]
Explanation This is an informational message but will be logged as a warning message if so configured.
Recommended Action No action is required.
%ISDN-4-SERVICE : Interface [chars] [chars] [chars] message for chan [dec] state [chars]
Explanation This is an informational message but will be logged as a warning message if so configured.
Recommended Action No action is required.
%ISDN-4-SPURIOUS_CONNECT : [chars]: Spurious Connection Accepted and Closed on port [int]
Explanation An unknown TCP connection was accepted and refused.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%ISDN-4-STATUS : Interface [chars] [chars] [chars] st [hex] ev [hex] cid [hex] cref [hex]
Explanation This is an informational message but being logged as a warning message if so configured.
Recommended Action No action is required.
%ISDN-5-SERV_AUDIT_C2 : Interface [chars] service audit trigger condition [dec] on channel [dec]
Explanation This is an informational message but will be logged as a warning message if so configured.
Recommended Action No action is required.
%ISDN-6-CALL_COLLISION : Interface [chars] Call Cid [hex] Cref [hex] collision on Channel [dec] in_use_cid [hex] cref [hex], Channel awarded to the received call
Explanation This is an informational message. It is sent when a Call is received that collides with an existing call on the same channel.
Recommended Action No action is required.
%ISDN-6-CHAN_UNAVAILABLE : Interface [chars] Requested Channel [dec] is not available
Explanation This is an informational message. It is sent when the requested channel is not available.
Recommended Action No action is required.
%ISDN-6-CONNECT : Interface [chars] is now connected to [chars] [chars]
Explanation This is an informational message sent when a call is connected. The message displays the remote name and number, which it receives from the Point-to-Point Protocol (PPP) authentication or from where the dialer placed the call to.
Recommended Action No action is required.
%ISDN-6-DISCONNECT : Interface [chars] disconnected from [chars] [chars], call lasted [int] seconds
Explanation This is an informational message sent when a call is disconnected. The message displays the remote name and number, which it receives from the Point-to-Point Protocol (PPP) authentication or from where the dialer placed the call to. It also shows how long the call lasted.
Recommended Action No action is required.
%ISDN-6-INVALID_TIMER : [chars]: Invalid Timer Handle, caller [hex] handle %3d
Explanation This could be an indication of low memory. It is sent when an invalid ISDN timer handle is passed on for timer operations
Recommended Action capture the show isdn mem, show isdn status output for possible debugging information. Reduce other system activity to ease the memory demands in the system.
%ISDN-6-LAYER2DOWN : Layer 2 for Interface [chars], TEI [int] changed to down
Explanation This is an informational message. It is sent when an ISDN Layer2 logical link is down. It also shows the TEI associated with this logical link.
Recommended Action No action is required.
%ISDN-6-LAYER2UP : Layer 2 for Interface [chars], TEI [int] changed to up
Explanation This is an informational message. It is sent when an ISDN Layer2 logical link is up. It also shows the TEI associated with this logical link.
Recommended Action No action is required.
%ISDN-6-NFAS_STATUS_CHANGE : [chars] [chars] [chars] [chars]
Explanation The NFAS D-channel status has changed.
Recommended Action No action is required.
%ISDN-6-NO_TIMER : No Free Timer Entry, caller [hex], timers used [dec]
Explanation This could be an indication of low memory. It is sent when the ISDN protocol cannot start new timers for it's operation.
Recommended Action capture the show isdn mem, show isdn status output for possible debugging information. Reduce other system activity to ease the memory demands in the system.
%ISDN-6-REPEATED_SETUP : Interface [chars] Call Cid [hex] Cref [hex] received a retransmitted setup on channel [dec] in_use_cid [hex] cref [hex].
Explanation This is an informational message sent when a duplicate SETUP message is received on a B-channel. This indicates that the rate of calls being received is momentarily greater than the rate calls can be processed. No action is required.
Recommended Action No action is required.
%ISDN-6-SERV_AUDIT_C3 : Interface [chars] service audit trigger condition [dec] on channel [dec]
Explanation This is an informational message but will be logged as a warning message if so configured.
Recommended Action No action is required.
ISSU
%ISSU-0-BOOT_SYNC_FAIL : Problem with sync of ISSU boot state -[chars]
Explanation The ISSU state between two FRUs is not properly synchronized as a result of a boot error.
Recommended Action This message will automatically appear during certain events, such as during a FRU removal or if the FRU loses connectivity. In most cases, the router will resynchronize the ISSU state between the FRUs without any user intervention. If the ISSU state is not resynchronized after multiple attempts, the problem is likely a result of another problem. Monitor the other system messages to see if a more serious issue has occurred on your router. If you are unable to resolve this other issue and this message persists, gather the output of show tech-support and provide it to a Cisco technical support representative.
%ISSU-0-PKG_INCONSIST : Reason: [chars]
Explanation A software consolidated package or sub-package has an error that indicates the sub-package should not be installed or used.
Recommended Action If this message is received, the desired consolidated package or sub-package should not be used. Upgrade using a different consolidated package or sub-package, and report the problem consolidated package or sub-package to Cisco technical support.
%ISSU-0-PKG_MNT_SCRIPT_FAIL : Package: [chars]
Explanation A consolidated package or sub-package has encountered an error indicating it is not usable.
Recommended Action Upgrade your software using a different consolidated package or sub-package.
%ISSU-0-RESET_FRU_FAIL : Problem with ISSU reset of remote FRU -[chars]
Explanation After a sub-package installation, one or more FRUs that were upgraded failed to initialize within the timeout period.
Recommended Action This problem is more likely to occur in routers with larger configurations, so if your router has a large configuration, you may want to wait a few more minutes to see if your hardware initializes. If the hardware continues to not initialize, reset the FRUs which failed to initialize. If resetting the FRUs fails to resolve the issue, gather the output of show tech-support and contact a Cisco technical support representative.
%ISSU-0-SOFTWARE_INVALID : Package for location [chars]: [chars]
Explanation The sub-packages have encountered an error related to the structure of the loaded software.
Recommended Action This error is likely caused by a failure of the boot or installation process or a corrupted provisioning file. If the system displays error messages related to the boot that can be addressed, address those messages. Downloading new software, if possible, may also help with the problem. If the problem persists, gather the output of show tech-support and provide it to a Cisco technical support representative.
%ISSU-3-BOOT_SYNC : Problem with sync of ISSU boot state -[chars]
Explanation The ISSU state between two FRUs is not properly synchronized as a result of a boot error.
Recommended Action This message will automatically appear during certain events, such as during a FRU removal or if the FRU loses connectivity. In most cases, the router will resynchronize the ISSU state between the FRUs without any user intervention. If the ISSU state is not resynchronized after multiple attempts, the problem is likely a result of another problem. Monitor the other system messages to see if a more serious issue has occurred on your router. If you are unable to resolve this other issue and this message persists, gather the output of show tech-support and provide it to a Cisco technical support representative.
%ISSU-3-BOOT_UNCLEAN : Found reload log file, moved to [chars]
Explanation A log file was found at bootup indicating that all shutdown tasks were not performed on a previous reload.
Recommended Action No user action is necessary. The system will automatically resolve most issues related to the shutdown task as part of the bootup procedure. If a problem related to the tasks that did not shutdown occurs, another error message will occur providing information about that problem.
%ISSU-3-INCOMPAT : The packages in [chars] are not consistent
Explanation The sub-packages specified for running on the chassis are not compatible with one other.
Recommended Action Install a compatible set of packages to allow normal operation. This will require booting a known-good package set.
%ISSU-3-SYNC_ERR : Problem with sync of state -[chars]
Explanation The software state between two FRUs or switches is not properly synchronized as a result of a boot error.
Recommended Action This message may appear during certain events, such as during a FRU or switch removal or if the FRU or switch loses connectivity. In most cases, the router will resynchronize the software state between the FRUs or switches without any user intervention. If the software state is not resynchronized after multiple attempts, the problem is likely a result of another problem. Monitor the other system messages to see if a more serious issue has occurred on your router. If you are unable to resolve this other issue and this message persists, gather the output of show tech-support and provide it to a Cisco technical support representative.
%ISSU-3-UCODE_INCOMPAT : Found mismatch for ucode feature -[chars]
Explanation During boottime microcode feature version check, a version mismatch was found for this feature.
Recommended Action Please ensure that versions of features in microcode are compatible by provisioning a different set of microcode files.
%ISSU-5-ISSU_AUTO_ROLLBACK : ISSU rollback timer expired: initiating rollback
Explanation An ISSU upgrade has been rolled back because the rollback timer has expired.
Recommended Action No user action is needed. If you want to commit the ISSU upgrade, redo the upgrade. Otherwise, this is an informational message only.
%ISSU-5-ISSU_STATE_INVALID : ISSU stored state found invalid and cleaned up: [chars]
Explanation The RP has corrected a failed ISSU install state that was detected at bootup.
Recommended Action No user action is necessary. This is an informative message indicating that the failed ISSU state has been corrected.
IVR
%IVR-1-APP_PARALLEL_INVALID_LIST : Call terminated. Huntgroup '[dec]' does not contain enough valid SIP end-points to proceed with a parallel call.
Explanation The call to a parallel hunt-group was denied because less than two valid SIP end-points were found in the huntgroup list.
Recommended Action Check the hunt-group list's numbers. Remove any incorrect numbers or numbers that have a non-SIP dial-peer. If the numbers are from SIP phones, then verify whether the phones have registered to the system yet.
%IVR-2-APP_CRIT : [chars]
Explanation A critical message was reported by an IVR Tcl application.
Recommended Action The remedy of the problem is application specific.
%IVR-2-APP_CRIT_R : [chars]
Explanation A critical message was reported by an IVR Tcl application.
Recommended Action The remedy of the problem is application specific.
%IVR-2-INVALID_DSAPP_DIALPEER : Service dsapp contains an invalid dial peer tag: [chars]
Explanation An invalid dial peer tag has been configured for the dsapp service. The tag either is not in the range from 1 to 2147483647, or it belongs to a non-existent dial-peer.
Recommended Action Enter the show running-config or the show dial-peer voice command to find a valid dial peer tag. Reconfigure the dial peer with a valid tag or remove the dial peer tag completely to allow the system to match from the system dial peers.
%IVR-3-ABNORMAL_EXIT : TCL IVR Process for this call with CallID [dec] exits , bad event: [chars] received
Explanation The TCL IVR call process exited for the specified call. The call process did not clear a prior call properly, so other events could not be handled. Only the specified call is affected
Recommended Action If problem persists for subsequent calls,copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
%IVR-3-APP_ERR : [chars]
Explanation An error message was reported by an IVR Tcl application.
Recommended Action The remedy of the problem is application specific.
%IVR-3-APP_ERR_R : [chars]
Explanation An error message was reported by an IVR Tcl application.
Recommended Action The remedy of the problem is application specific.
%IVR-3-BAD_IVR_VERSION : Script requires version [dec].[dec], image supports [dec].[dec]
Explanation IVR Script requires a higher IVR infrastructure version
Recommended Action Upgrade IOS, or use a different script
%IVR-3-BADSCRIPT : Could not parse malformed IVR script: [chars]
Explanation Could not parse malformed IVR script
Recommended Action Check the script and fix the syntax error.
%IVR-3-LOW_CPU_RESOURCE : IVR: System experiencing high cpu utilization ([dec]/100). Call (callID=[dec]) is rejected.
Explanation 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.
%IVR-3-LOW_MEMORY : IVR: Sytem running on low memory. Free memory: %l bytes. Call is rejected.
Explanation System does not have enough memory to accept calls
Recommended Action Check to see what is causing low system memory.
%IVR-3-LOW_MEMORY_RESOURCE : IVR: System running low on memory ([dec]/100 in use). Call (callID=[dec]) is rejected.
Explanation System does not have enough free memory to accept a new call
Recommended Action Ensure that the gateway has the recommended amount of memory for this IOS feature set and version.
%IVR-3-NOSCRIPT : Could not load IVR script [chars] errno=[dec]=[chars]
Explanation Could not read in the IVR script
Recommended Action Check that script exists on the server, and is readable.
%IVR-4-APP_WARN : [chars]
Explanation A warning message was reported by an IVR Tcl application.
Recommended Action The remedy of the problem is application specific.
%IVR-4-APP_WARN_R : [chars]
Explanation A warning message was reported by an IVR Tcl application.
Recommended Action The remedy of the problem is application specific.
%IVR-4-INVALID_DSAPP_BLINDTIME : Blind-xfer-wait-time [dec] is invalid. Resetting to [dec] seconds.
Explanation The configured value for blind-xfer-wait-time was outside of the acceptable range (0-10) and has been reset to the indicated value.
Recommended Action If the new value for blind-xfer-wait-time is unacceptable, you can change it from the command line interface.
%IVR-4-INVALID_DSAPP_TOGGLE_TIME : Disc-toggle-time [dec] is invalid. Resetting to [dec] seconds.
Explanation The configured value for disc-toggle-time was outside of the acceptable range (10-30) and has been reset to the indicated value.
Recommended Action If the new value for disc-toggle-time is unacceptable, you can change it from the command line interface.
%IVR-5-APP_LOG_DUR_CALL_DETECTED : [chars]
Explanation A notification message was reported by an IVR application on detecting long duration call.
Recommended Action This is not a problem but notifying syslog about long duration call.
%IVR-5-APP_MED_INACT_DETECTED : [chars]
Explanation A notification message was reported by an IVR application on detecting media inactivity.
Recommended Action This is not a problem but notifying syslog about media inactivity.
%IVR-5-APP_MED_REACT_DETECTED : [chars]
Explanation A notification message was reported by an IVR application on detecting media activity.
Recommended Action This is not a problem but notifying syslog about media activity.
%IVR-6-APP_INFO : [chars]
Explanation An informational message was reported by an IVR Tcl application.
Recommended Action The remedy of the problem is application specific.
%IVR-6-APP_INFO_R : [chars]
Explanation An informational message was reported by an IVR Tcl application.
Recommended Action The remedy of the problem is application specific.
%IVR-6-APP_PARALLEL : Cannot use dial-peer [dec] (parallel hunt-group) for a rotary or in a hunt-group call.
Explanation The dial-peer for parallel hunt-groups must have a unique pilot number.
Recommended Action Create a unique dial-peer destination-number for the parallel hunt-group.
%IVR-6-APP_SEQ_HUNT : Pilot hunt-group '[chars]' found in hunt-group list. Nested hunt-groups are allowed only as the hunt-group's final number.
Explanation Nested sequential hunt-group detected in dial-peer rotary. Nested hunt-groups is unsupported.
Recommended Action Do not create hunt-group lists that contain hunt-group pilot numbers.
IVR_MSB
%IVR_MSB-3-NOPROMPT : Could not create IVR prompt [chars] errno=[dec]=[chars]
Explanation Could not read in the IVR prompt
Recommended Action Check that prompt exists on the server, and is readable.
IVR_NOSIGNALING
%IVR_NOSIGNALING-3-LOW_CPU_RESOURCE : IVR: System experiencing high cpu utilization ([dec]/100). Application cannot be instantiated.
Explanation System does not have enough CPU capacity to spawn a new instance of IVR application
Recommended Action Ensure that the call setup rate is within the supported capacity of this gateway.
%IVR_NOSIGNALING-3-LOW_MEMORY_RESOURCE : IVR: System running low on memory ([dec]/100 in use). Application cannot be instantiated.
Explanation System does not have enough free memory to spawn a new instance of IVR application
Recommended Action Ensure that the gateway has the recommended amount of memory for this IOS feature set and version.
K
KERBEROS
%KERBEROS-3-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, call your technical support representative for assistance.
KEYMAN
%KEYMAN-4-KEYSTR_BAD_CRYPTO : Bad encrypted keystring for key id [dec].
Explanation The system could not successfully decrypt an encrypted keystring. The keystring may have been corrupted during system configuration.
Recommended Action Re-enter the key-string command, and reconfigure the key string.
%KEYMAN-4-KEYSTR_CRYPTO_TYPE : Type [dec] encryption unknown. Interpreting keystring as literal
Explanation The format type was not recognized by the system. A keystring format type value of 0 (unencrypted keystring) or 7 (hidden keystring), followed by a space, can precede the actual keystring to indicate its format. An unknown type value will be accepted, but the system will consider the keystring as being unencrypted.
Recommended Action Use the correct format for the value type or remove the space following the value type
KEYSTORE
%KEYSTORE-3-BAD_MAGIC : Bad magic number [hex] in software keystore file [chars].
Explanation Keystore data file appears to have been corrupted. Keys can not be retrieved from persistent memory.
Recommended Action None
%KEYSTORE-3-IFS_OPEN_R : Failed to open file [chars] for reading software keystore. ([chars])
Explanation An error occurred while opening the keystore file for reading. CTS keys could not be retrieved.
Recommended Action None
%KEYSTORE-3-IFS_OPEN_W : Failed to open file [chars] for writing software keystore. ([chars])
Explanation An error occurred while opening a file for persistent storage. CTS keys could not be saved to persistent storage.
Recommended Action None
%KEYSTORE-3-IFS_READ : An error ([chars]) occurred while reading from the software keystore file.
Explanation CTS keys could not be retrieved from persistent storage.
Recommended Action None
%KEYSTORE-3-IFS_WRITE : An error occurred while writing to the software keystore file.
Explanation CTS keys could not be saved to persistent storage.
Recommended Action None
%KEYSTORE-3-IPCNOCONN : No IPC communication path to peer available for keystore [chars].
Explanation No IPC connection to the peer was available for keystore redundancy messages. This means that any updates made to the ACTIVE keystore cannot be pushed to the STANDBY keystore.
Recommended Action None
%KEYSTORE-3-IPC_NO_PROC : Could not create a process to receive keystore redundancy messages.
Explanation An error was encountered when trying to create a process to handle incoming keystore redundancy messages. This means that any updates made to the ACTIVE keystore cannot be pushed to the STANDBY keystore.
Recommended Action None
%KEYSTORE-3-IPCOPEN : Failed to open IPC port to peer for keystore redundancy: [chars]
Explanation An error was encountered when trying to open an IPC port for keystore redundancy messages. This means that any updates made to the ACTIVE keystore cannot be pushed to the STANDBY keystore.
Recommended Action None
%KEYSTORE-3-IPCPORT : Failed to create IPC port ([chars]) for keystore redundancy. [chars].
Explanation An error was encountered when trying to create an IPC port. This means that any updates made to the ACTIVE keystore cannot be pushed to the STANDBY keystore.
Recommended Action None
%KEYSTORE-3-IPCSEND : IPC send error ([chars]) while sending [chars].
Explanation An error occurred while sending an IPC message to the peer during a keystore redundancy operation. This means that any updates made to the ACTIVE keystore cannot be pushed to the STANDBY keystore.
Recommended Action None
%KEYSTORE-3-ISSU_INCOMPAT : Standby incompatible for SSO.
Explanation The image on the standby failed ISSU message version negotiation. As a result, we will not be able to sync keystore updates to it and so it is disallowed from reaching hot standby status in SSO mode.
Recommended Action None
%KEYSTORE-3-NO_KEYSTORE : CTS hardware keystore is not responsive and software emulation is not enabled.
Explanation The CTS hardware keystore on the switch has failed and needs to be inspected. Since CTS credentials are stored in the keystore, this means that CTS authentication and authorization operations will fail. The following action is recommended: If the defect is shown on the Active Supervisor, try to switchover to Standby Supervisor. If the defect is shown on Standby Supervisor, try to reset the Standby. If the defect persists, there may be damage to the hardware keystore chip, please take appropriate action. In the meantime, you can configure the switch to use software keystore emulation. After you have enabled software keystore emulation, please re-configure CTS credentials to populate the software keystore.
Recommended Action None
%KEYSTORE-3-UNEXPECTED_EOF : Unexpected end of file while reading software keystore [chars].
Explanation Keystore data file appears to have been truncated. One or more keys can not be retrieved from persistent memory.
Recommended Action None
L
L2
%L2-3-DUP_REG : L2 Forwarding Engine: [chars] Attempt to program duplicate MAC address
Explanation Attempt to program duplicate MAC address in the match registers
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%L2-4-NOBUF : Buffer alloc failed: [chars] [dec]
Explanation System is running out of buffers
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%L2-4-NOMEM : Malloc failed: [chars] [dec]
Explanation System is running out of memory
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%L2-4-QUEERR : Que Full Error: [chars] [chars]
Explanation Can not enqueue due to lack of system resources
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
L2_AGING
%L2_AGING-0-CREATEQFAIL : Failed to create L2-AGING queue
Explanation Linecards may have inconsistent info because of this
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%L2_AGING-2-SIG_INST_FAIL : [chars]: Failed to install signal handler
Explanation L2-AGING: A signal handler could not be installed for the process that involved Layer 2 aging
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%L2_AGING-2-SPAWNFAIL : [chars] task spawn failed
Explanation L2-AGING task spawn failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%L2_AGING-4-ENTRY_DNLDFAIL : Slot [dec]: Download entries failed, reason [chars]
Explanation Download of aging entries to linecard failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%L2_AGING-4-INPROGRESS : Download already in progress to slot [dec]
Explanation L2-AGING Download process error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%L2_AGING-4-INVSLOT : Download to invalid slot [dec] requested
Explanation L2-AGING internal error(lcc)
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%L2_AGING-4-MISSING_SLOTNO : Cannot get the slot to download l2 entries
Explanation L2-AGING Download process error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%L2_AGING-4-UNKMESG : [chars]: received unknown message [dec]
Explanation Internal error -- maybe mismatch in image versions.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
L2_API
%L2_API-5-INVADDR : Invalid static entry address computed. Offset [hex], rc [chars]
Explanation Internal software error detected
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%L2_API-5-INVOPER : Invalid operation [dec]
Explanation Invalid operation requested
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%L2_API-5-MAC_REPLACE : Mac [enet], Vlan [dec] replaced with Mac [enet], Vlan [dec]
Explanation A lower priority mac entry had to be removed from the MAC table in order to add an important mac entry
Recommended Action No action is required.
%L2_API-5-RETADDR : Unsupported action.
Explanation Internal error -- unsupported api invoked
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%L2_API-5-SENDFAIL : ICC Send failed. Reason [chars]
Explanation L2-API message send to linecards failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
L2_APPL
%L2_APPL-0-TASK_SPAWN_FAIL : Failed to spawn task [chars]
Explanation Spawn task failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%L2_APPL-4-UNKMESG : Unknown received message [dec]
Explanation Internal error -- maybe mismatch in image versions.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%L2_APPL-5-MAC_USAGE : MAC usage for EARL [dec] is currently [dec]
Explanation The utilization of the L2 Forwarding table of the Enhanced Address Recognition Logic is greater than threshold set by the user. The EARL Forwarding Table exceeding the utilization threshold and the current utilization are specified in the error message text.
Recommended Action No action is required.
L2BD_PROXY
%L2BD_PROXY-2-PROXY_IPC_INIT_FAILED : QFP L2BD Proxy IPC interface initialization failure (result: [dec]).
Explanation Cisco internal software error. QFP L2BD Proxy initialization detected that the IPC interface initialization failed. QFP L2BD 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%L2BD_PROXY-3-L2BD_MEM_EXTEND_FAILED : L2BD 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%L2BD_PROXY-3-L2BD_MEM_REQ_FAILED : L2BD 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%L2BD_PROXY-3-PROXY_BAD_MSG : QFP L2BD Proxy received bad length message type [dec]
Explanation Cisco internal software error. QFP L2BD 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%L2BD_PROXY-3-PROXY_IPC_ALLOC_FAILED : QFP L2BD Proxy [chars] message lost due to message buffer allocation failure.
Explanation Cisco internal software error. QFP L2BD 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%L2BD_PROXY-3-PROXY_IPC_SEND_FAILED : QFP L2BD Proxy [chars] message lost due to message sent failure (result: [dec]).
Explanation Cisco internal software error. QFP L2BD 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%L2BD_PROXY-4-PROXY_INVALID_MSG : QFP L2BD Proxy received invalid message type [dec]
Explanation Cisco internal software error. QFP L2BD 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%L2BD_PROXY-4-PROXY_INVALID_MSG_LEN : QFP L2BD Proxy IPC invalid length, [dec]:[dec] len [dec] flags [hex] source [dec]
Explanation Cisco internal software error. QFP L2BD 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
L2CTRL
%L2CTRL-3-ADD_REGISTRY_FAILED : Subsystem [chars] fails to add callback function [chars]
Explanation Other subsystem must have mistakenly add its own callback functions. This syslog is for debugging purpose.
Recommended Action No action is required.
L2_CTRL
%L2_CTRL-4-UNKMESG : [chars]: unknown received message [dec]
Explanation Internal error -- maybe mismatch in image versions.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
L2_DIST_LRN
%L2_DIST_LRN-4-NO_INIT : Initialization failed: [chars]
Explanation Initialization of L2 Distributed Learning Failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%L2_DIST_LRN-4-NO_MAC_RDRT : MAC redirect initialization failed: [chars]
Explanation Initialization of MAC redirection failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%L2_DIST_LRN-4-NO_MEM : Malloc failed: [chars]
Explanation System is running out of memory
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%L2_DIST_LRN-4-PAK_BLD_FAIL : [chars] Unable to build L2 Dist Lrn packet
Explanation Unable to build L2 Dist Lrn packet
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%L2_DIST_LRN-6-BUFFER_OVERRUN : Buffer Overrun: [chars]
Explanation Too many new learns are being processed by L2 Dist Lrn
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%L2_DIST_LRN-6-NO_LRN : Unable to propogate L2 new learn at addr [hex]
Explanation Temporary condition where a new Layer 2 Table entry cannot be propogated to other linecards
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%L2_DIST_LRN-6-NO_PKT_SEND : Unable to send L2 Dist Lrn packet: [chars]
Explanation Unable to send L2 Dist Lrn correction packet
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
L2FIB
%L2FIB-3-BAD_PARAM : [chars]
Explanation Invalid parameter
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
L2_MAC
%L2_MAC-4-ADDMACFAIL : User static MAC [enet] (vlan [dec]) cannot be installed. Reason: [chars]
Explanation A user requested static MAC address cannot be installed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
L2_MGR
%L2_MGR-2-MGR_SPAWNFAIL : Failed to spawn L2-MGR task --DFC linecards will affected
Explanation Linecards may have inconsistent info because of this
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%L2_MGR-2-SPAWNFAIL : [chars] task spawn failed
Explanation L2-MGR task spawn failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%L2_MGR-4-BADVLAN_DNLDFAIL : Slot [dec]: Download Bad vlan failed, reason [chars]
Explanation Download of data to linecard failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%L2_MGR-4-ENTRY_DNLDFAIL : Slot [dec]: Download entries failed, reason [chars], entries [dec]/[dec]
Explanation Download of static L2 entries to linecard failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%L2_MGR-4-INPROGRESS : Download already in progress to slot [dec]
Explanation L2-MGR Download process error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%L2_MGR-4-INVSLOT : Download to invalid slot [dec] requested
Explanation L2-MGR internal error(lcc)
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%L2_MGR-4-MISSING_SLOTNO : Cannot get the slot to download l2 entries
Explanation L2-MGR Download process error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%L2_MGR-4-UNKMESG : Unknown received message [dec]
Explanation Internal error -- maybe mismatch in image versions.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
L2_THROTTLE
%L2_THROTTLE-4-BLOCKFAIL : l2 throttle blocking task failed
Explanation L2-THROTTLE blocking task failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%L2_THROTTLE-4-UNKMESG : Unknown received message [dec]
Explanation Internal error -- maybe mismatch in image versions.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
L2TP
%L2TP-3-CRITICAL : [chars]
Explanation An critical event has been processed by the L2TP subsystem.
Recommended Action No action is required.
%L2TP-3-ILLEGAL : [chars]: [chars]
Explanation An illegal event has been processed by the L2TP subsystem.
Recommended Action No action is required.
%L2TP-5-IGNOREICMPMTU : Ignoring received ICMP Type 3 Code 4, 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 to decrease or increase the MTU then use the vpdn pmtu min command to decrease the minimum MTU allowed and enter the vpdn pmtu max command to increase the maximum MTU that is allowed. The minimum value specified is the minimum MTU that is allowed, and the maximum value specified is the maximum MTU that is allowed.
L2TP_HA
%L2TP_HA-3-ISSU : [chars]: [chars]
Explanation A L2TP ISSU error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%L2TP_HA-3-SYNC : [chars]: code [dec]
Explanation An error occurred when syncing L2TP state to the Standby Route Processor. This may affect Non-Stop Forwarding capability on L2TP-based interfaces during and after switchover until the state is recovered through normal protocol operation.
Recommended Action Reset the standby processor to attempt the sync again. LOG_STD_RECUR_ACTION
L4_INSPECT
%L4_INSPECT-3-INVALID_CHUNK_ID : Invalid chunk ID for protocol ([int])
Explanation Failed to determine chunk ID for specified protocol. Unable to free CFT feature object.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
LANMGR
%LANMGR-2-NOMEMORY : No memory available: [chars]
Explanation The requested operation failed 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.
%LANMGR-4-BADRNGNUM : Ring number mismatch on [chars], shutting down the interface
Explanation The router detected a conflict in assigned ring numbers for the specified Token Ring. The Ring Parameter Server (RPS) function was shut down to prevent potentially incorrect information from being sourced onto the ring.
Recommended Action Check all bridges connected to this Token Ring and ensure that they are using the same assigned ring number.
%LANMGR-4-BADUPCALL : Unexpected call ([chars]) from LLC2 for Bridge [hex]-[hex]-[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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%LANMGR-4-NORING : No ring info for [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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%LANMGR-4-OLDTRAMON : Cannot run RPS on [chars], Old TRAMON code.
Explanation The software on this interface cannot support the functions required for LAN Network Manager.
Recommended Action Call your Cisco technical support representative about a firmware upgrade for this interface card.
LAPB
%LAPB-2-NOBUF : Interface [chars], no buffer available to [chars]
Explanation There was insufficient memory for the LAPB protocol engine to send a message.
Recommended Action This message is acceptable if it occurs infrequently, because the LAPB protocol is designed to handle loss of frames. Frequent occurrences can cause disruption of service. The system can be configured to ease memory demands or, if conditions warrant, the system can be upgraded to a larger memory configuration.
%LAPB-3-BADPAYLOAD : Interface [chars], Invalid payload value: [chars]
Explanation An internal software error occurred.
Recommended Action If either of these messages recur, call your technical support representative for assistance.
%LAPB-3-CONTEXTERR : [chars]: [chars]
Explanation An internal software error occurred.
Recommended Action If either of these messages recur, call your technical support representative for assistance.
%LAPB-3-NOINPIDB : Input idb not set
Explanation An internal software error occurred.
Recommended Action If either of these messages recur, call your technical support representative for assistance.
%LAPB-3-NULLPAK : Interface [chars], NULL packet ptr, rvr [dec], vs [dec], vr [dec]
Explanation An internal software error occurred.
Recommended Action If either of these messages recur, call your technical support representative for assistance.
%LAPB-3-TIMERERR : LAPB timer task cannot be created
Explanation An internal software error occurred.
Recommended Action If either of these messages recur, call your technical support representative for assistance.
%LAPB-4-CTRLBAD : Interface [chars], Invalid control field
Explanation A received FRMR reported a frame with an invalid control code.
Recommended Action Check the serial line and the devices attached to the line.
%LAPB-4-FRAMEERR : Interface [chars], Frame error: CF [hex], VS [dec] %c VR [dec], Reason [hex]
Explanation A FRMR frame was received, indicating that a protocol violation was detected. The Reason field will be interpreted by generating INFOBAD, CTRLBAD, N1TOOBIG, or INVNR messages immediately after this message; refer to the explanations for these messages for more information.
Recommended Action The protocol will recover by resetting the service. This will disrupt any network service on top of LAPB (for example, X.25 virtual circuits will be cleared). Follow the recommended action for any error message following the FRMR reports; if service becomes unacceptable, check the serial line and its attached devices.
%LAPB-4-INFOBAD : Interface [chars], Info field not permitted
Explanation A received FRMR frame reported that an information field was present in a frame where no information field is allowed.
Recommended Action Check the serial line and the device attached to the line.
%LAPB-4-INVNR : Interface [chars], Invalid NR value
Explanation A received FRMR reported a frame with an invalid N(R) value.
Recommended Action Verify that the equipment attached to the serial line is configured with the same K value (maximum number of outstanding I frames).
%LAPB-4-N1TOOBIG : Interface [chars], N1 too large
Explanation A received FRMR reported an information frame that was too long.
Recommended Action Verify that the equipment attached to the serial line is configured with the same N1 value. N1 is in bits and includes the entire frame plus 16 bits of CRC. However, some equipment may require configuration in octets, the omission of the two CRC octets, or the omission of the three octets of LAPB control information.
LAT
%LAT-3-BADDATA : Tty%t, Data pointer does not correspond to current packet
Explanation An internal software error occurred.
Recommended Action If this message recurs, contact your technical support representative.
%LAT-3-BUFFULL : Tty%t, data buffer full with count [dec]
Explanation An internal software error occurred.
Recommended Action If this message recurs, contact your technical support representative.
%LAT-3-NOSYNC : Tty%t, Output data ptrs out of sync with byte count
Explanation An internal software error occurred.
Recommended Action If this message recurs, contact your technical support representative.
%LAT-3-NULLIDB : Null IDB pointer with destination [enet]
Explanation An internal software error occurred.
Recommended Action If this message recurs, contact your technical support representative.
%LAT-3-QBSPACED : Queue block at [hex] not found for HI connection
Explanation An internal software error occurred.
Recommended Action If this message recurs, contact your technical support representative.
%LAT-3-REUSE : Tty%t, Attempt to re-use slot array, empty = [dec], fill = [dec]
Explanation An internal software error occurred.
Recommended Action If this message recurs, contact your technical support representative.
LAYER2_BRIDGE
%LAYER2_BRIDGE-3-ALLOC_FAILED : Allocation of [chars] memory failed for layer 2 bridging feature in QFP
Explanation Allocation of memory by the QFP layer 2 bridging 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LAYER2_BRIDGE-3-HA_BULK_SYNC_FAIL : rg [dec], MSGDEF_LIMIT_MEDIUM
Explanation There was a failure such that Layer 2 bridge domain bulk sync did not occur
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LAYER2_BRIDGE-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LAYER2_BRIDGE-3-INIT_FAILED : Initialization of the layer 2 bridging feature in QFP failed
Explanation Initialization of the layer 2 bridging 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LAYER2_BRIDGE-3-PKT_REPLICA_INIT_FAILED : Failed to register with generic packet replication for layer 2 bridging feature in QFP
Explanation Layer 2 bridging initialization of packet replication registration failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
LAYER2_SVI
%LAYER2_SVI-3-ALLOC_FAILED : Allocation of [chars] memory failed for SVI feature in QFP
Explanation Allocation of memory by the QFP SVI 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LAYER2_SVI-3-INIT_FAILED : Initialization of the SVI feature in QFP failed
Explanation Initialization of the SVI 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LAYER2_SVI-3-PKT_REPLICA_INIT_FAILED : Failed to register with generic packet replication for SVI feature in QFP
Explanation SVI initialization of packet replication registration failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
LFD
%LFD-2-AVL : [chars] [hex]
Explanation AVL tree operation error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LFD-2-FPIHANDLER3 : [chars] [hex] [hex] [hex]
Explanation FPI Handler error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LFD-3-BADEXEC : Unexpected Code Execution: [chars] [dec]
Explanation Unexpected Code Execution
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LFD-3-BADFRRTYPE : illegal frr type: [dec]
Explanation FRR request type error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LFD-3-BADLABELADD : Cannot add label -[chars].
Explanation Unable to create label due to reason given.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LFD-3-BADSHORTLABELADD : Cannot add short label: path_idx [dec], moi_type [dec]
Explanation Unable to create MFI feature space in FIB entry, so unable to store short path extension information there.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LFD-3-BROKERINITFAIL : Failed to initialise lte 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LFD-3-CHUNKMGR : chunk mgr: [chars] [hex]
Explanation Chunk manager error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LFD-3-CHUNKMGRALLOC : failed chunk alloc: [chars]
Explanation Chunk alloc() failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LFD-3-CHUNKMGRDEALLOC : failed chunk dealloc: [chars]
Explanation Chunk free() failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LFD-3-CORRUPTED_PKT : [chars]
Explanation lfd received corrupted packet
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LFD-3-EVTLOGBADSOURCE : Illegal log event source: [dec]
Explanation Illegal event found in log buffer
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LFD-3-FIBIPINVALID : [chars], table: [dec] label: [dec]
Explanation IP path information is invalid for the indicated label table entry
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%LFD-3-FIBIPINVALIDAF : AF: [dec] [chars], table: [dec] label: [dec]
Explanation IP path information AF is invalid for the indicated label table entry
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%LFD-3-FIBNONIPINVALID : [chars], table: [dec] label: [dec]
Explanation Non IP path information is invalid for the indicated label table entry
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%LFD-3-FIB_SRC : Label [[dec]/[dec]] [chars] [chars] [chars]
Explanation The fib entry could not be sourced for label in question.
Recommended Action If there is no matching bug for this problem, please collect the output of show mpls forwarding-table internal and show ip route [vrf <name>] <prefix> and the error message traceback and file a bug
%LFD-3-FPIHANDLER : LFD SSS Handler: [chars]
Explanation Error in fpi handler
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LFD-3-FPITYPEWRONG : Require fpi type [chars], get fpi type [chars]
Explanation Unmatched FPI type
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LFD-3-INTFDB2 : intf db: [chars] [hex] [hex]
Explanation Interface db error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LFD-3-INTFDB : intf db: [chars] [hex]
Explanation Interface db error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LFD-3-INVIPLABELTYPE : Wrong label type [dec] for IP Label [dec], table [dec] prefix [chars], vrf [chars]
Explanation Label type is invalid for the indicated label table entry
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version and show running-config and contact your Cisco technical support representative.
%LFD-3-INVLABELTYPE : Wrong label type [dec] for non-ip LTE [dec]/[dec]
Explanation Label type invalid for non-ip label table entry
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LFD-3-INVLABELUPDTYPE : Wrong label type [dec] for label [dec] table [dec] [chars] [chars]
Explanation An invalid Label type was encountered during the specified operation
Recommended Action If there is no matching bug for this problem, please collect the output of show mpls forwarding-table label <label> internal and the error message traceback and file a bug report.
%LFD-3-INVPATHLBL : [chars] [chars]
Explanation An invalid outgoing label is attached to the prefix
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version and show running-config and contact your Cisco technical support representative.
%LFD-3-INVPEXTLEN : [chars] path ext : attempt to decode beyond XDR buffer, cp [hex], cp_end [hex], msg_type [dec], msg_size [dec], padding [dec]
Explanation Accessing memory beyond XDR buffer length while decoding path extensions
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LFD-3-INVPLIST : Wrong path list type [dec] for label [dec]/[dec] [chars]
Explanation The path list type is set incorrectly for the label in question
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LFD-3-INVPLISTTYPE : Wrong plist_type expected [dec] for [dec]/[dec] update (was [dec])
Explanation Rewrite PLISTTYPE invalid for non-ip label table entry
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LFD-3-INVRWID : Wrong rwid [dec] for non-ip LTE [dec]/[dec]
Explanation Rewrite ID invalid for non-ip label table entry
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LFD-3-KEY_DB_INSERTFAIL : [chars], entry [hex], existing [hex]
Explanation The element could not be inserted into the LFD's key database.
Recommended Action If there is no matching bug for this problem, please collect the output of show mpls forwarding-table internal and the error message traceback and file a bug
%LFD-3-LABEL_BLOCK_CHUNK : [chars]
Explanation lfd label block chunk entry corrupted
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LFD-3-LCXDRCLIENT : LTE 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LFD-3-LTABLEMEM : Cannot allocate new mpls table [dec] of size [dec] needed for entry [dec]
Explanation Not enough contiguous memory for mpls forwarding table
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
%LFD-3-NONIPINFO : Non-ip info: [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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LFD-3-NOOCE : Attempt to get labels from OCE failed -[chars].
Explanation Calling function has provided insufficient information to get labels.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LFD-3-NORESOURCE : [chars] [dec]
Explanation Resource Failure: %s %d
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LFD-3-NULLADJACENCY : NULL Adjacency
Explanation NULL adjacency encountered
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LFD-3-NULLFIBIDB : NULL FIB IDB: [chars] [dec]
Explanation NULL FIB IDB encountered
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LFD-3-OCE_CHAIN : [chars]
Explanation NULL OCE in chain
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LFD-3-ORPHANLTE : Label [dec]/[dec], plist [dec], LDM: [hex]
Explanation The LTE for the label was supposed to be deleted, but is still present
Recommended Action Collect the running configuration and output of show mpls forwarding-table labels label-num command and contact cisco technical service representative.
%LFD-3-PATHEXTENCODE : [chars] [chars], path list: [IPV6 address], path ext: [IPV6 address]
Explanation MPLS path extensions could not be encoded for distribution
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%LFD-3-REWMGR2 : [chars] [hex] [hex]
Explanation Rewrite lookup failed due to FPI inconsisency
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LFD-3-REWMGR : Rewrite Manager: [chars] [hex]
Explanation Rewrite Manager error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LFD-3-RPXDRCLIENT : Invalid XDR 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LFD-3-RUNNING_TIMER : [chars] [dec] [chars] [dec]
Explanation The MPLS forwarding entry for the specified label was deleted prior to the expiry of its associated timer
Recommended Action If there is no matching bug for this problem, please collect the output of show mpls forwarding-table label <label> internal and the error message traceback and file a bug report.
%LFD-3-SM : [chars] [dec]
Explanation State Machine error: %s %d
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LFD-3-SMBADEVENT : Unexpected event [chars] for state [chars]
Explanation The LFD received an unexpected event for its state. The state of the LFD, and the unexpected event, are specified in the message text.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LFD-3-UNSUPPORTED_XDR : [chars]
Explanation Decoding of an XDR message revealed data or format that is unsupported in the current release.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LFD-3-UNSUPPORT_OCE : Not support -[chars] [dec]
Explanation Unsupported OCE
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LFD-3-UPDATEHANDLER2 : [chars] [hex] [hex]
Explanation Error in update handler
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LFD-3-UPDATEHANDLER3 : [chars] [hex] [hex] [hex]
Explanation Error in update handler
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LFD-3-UPDATEHANDLERFPI : No handler installed: fpi=[dec] handler type=[chars]
Explanation No handler installed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LFD-3-XDRBADMAGIC : xdr message for [chars] spilled out of allocated static storage
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LFD-4-FIB_SRC1 : Label [[dec]/[dec]] [chars] [chars] [chars]
Explanation The fib entry could not be sourced for label in question.
Recommended Action If there is no matching bug for this problem, please collect the output of show mpls forwarding-table internal and show ip route [vrf <name>] <prefix> and the error message traceback and file a bug
%LFD-4-NOFIBIDB : [chars] -ifnum [dec]
Explanation fibidb missing on linecard
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%LFD-4-OWNCHANGED : Owner changed for [chars] [dec]/[dec] from [dec] to [dec]
Explanation Label was previously installed by different installer
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LFD-4-RE_ENTRANT : Re-entrancy detected: [chars]
Explanation lfd non ip recalculation has re-entrancy
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LFD-4-UNSUPPORTEDRW : Unexpected rewrites seen where MPLS is not supported by platform for this slot
Explanation MPLS is either not needed or not handled by the platform for this card and should not handle rewrites
Recommended Action No action is required.
%LFD-6-RESOURCE : [chars]
Explanation MPLS software is disabled on LC
Recommended Action No action is required.
LI
%LI-3-MEM_INIT_FAILED : Allocation of [chars] memory failed for LI
Explanation LI Initialization of channel pool failed.
Recommended Action LOG_STD_ACTION
%LI-3-PKT_REPLICA_INIT_FAILED : Register to Generic Packet Replication failed for LI
Explanation LI Initialization of packet replication registration failed.
Recommended Action LOG_STD_ACTION
LICENSING
%LICENSING-6-LIC_MISMATCH : Configured license image level [chars] does not match the current level [chars]. Reload is required to bring the system up in [chars]
Explanation During boot-up of system, the configured license image level might mismatch with the current level. This could happen when customer copy a different startup-config to the system.
Recommended Action Reload is required to bring the system up in the configured license image level.
LIIN
%LIIN-3-SET_ACCESS_FAIL : Installing LIIN interface access control failed
Explanation This error happens when IOS failed to set the access control function for the LIIN, possibly due to IOSd out of memory or corruption. In this case, LIIN interface setup will not proceed, will not operate properly and cannot be recovered. Persistent access features and interactive commands will not work.
Recommended Action LOG_STD_ACTION
%LIIN-3-SET_TABLEID_FAIL : Installing [chars] LIIN interface tableid failed
Explanation This error happens when IOS failed to set tableid into linux kernel, possibly due to either IOSd or kernel out of memory or corruption. In this case, LIIN interface will not have VRF installed for the associated address family. The LIIN interface will not operate properly and cannot be recovered. Persistent access features and interactive commands will not work.
Recommended Action LOG_STD_ACTION
%LIIN-3-VRFADD_FAIL : Problem creating vrf
Explanation The LIIN config process failed to allocate a mandatory iVRF. The LIIN interface will not operate properly and cannot be recovered. Persistent access features and interactive commands will not work.
Recommended Action LOG_STD_ACTION
%LIIN-3-VRFMODIFY_FAIL : Problem adding LIIN interface to vrf table
Explanation The LIIN config process failed to assign the LIIN interface to its mandatory iVRF. The LIIN interface will not operate properly and cannot be recovered. Persistent access features and interactive commands will not work.
Recommended Action LOG_STD_ACTION
%LIIN-6-TELNET_ALLOWED : Telnet access allowed due to romvar: SR_INIT_SHELL
Explanation Telnet from shell to IOS allowed because rommon variable SR_INIT_SHELL is set with value aux_do_system_shell. Remove this value from SR_INIT_SHELL or unset SR_INIT_SHELL to disable the telnet access
Recommended Action No action is required.
LINEPROTO
%LINEPROTO-5-UPDOWN : Line protocol on Interface [chars], changed state to [chars]
Explanation The data link level line protocol changed state.
Recommended Action No action is required.
LINK
%LINK-0-REENTER : Fatal reentrancy, level=[dec], intfc=[chars]
Explanation An internal software error occurred. The system code tried to access a critical data structure which was already in use.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LINK-2-BADVCALL : Interface [chars], undefined entry point
Explanation An internal software error occurred. The high-level system code tried to use an unimplemented entry point with the virtual interface descriptor block (IDB) driver.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LINK-2-INTVULN : In critical region with interrupt level=[dec], intfc=[chars]
Explanation An internal software error occurred. The high-level system code tried to call this routine with interrupts enabled.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LINK-2-LINEST : No linestate vector for [chars]
Explanation An internal software inconsistency occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LINK-2-NOSOURCE : Source idb not set
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%LINK-3-BADENCAP : Interface [chars], Bad encapsulation code ([dec])
Explanation The lower level software was unable to write a MAC header for a datagram. A probable cause is configuration error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LINK-3-BADMACREG : Interface [chars], non-existent MACADDR registry for link [dec]
Explanation An attempt to map a network level address to a MAC level address failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LINK-3-BOGUSENCAP : msgtxt_badencap
Explanation A serial interface has been configured with an unknown encapsulation.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LINK-3-COMPREG : Interface [chars], non-existent (de)compression registry. Packet dropped
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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LINK-3-EMPTYPAK : Interface [chars], empty packet dequeued; linktype [dec], queue [dec].
Explanation This message indicates an internal software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LINK-3-FCS_ERROR : [chars] [chars] [chars] [chars]
Explanation The FCS Error rate exceeds the configured threshold
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LINK-3-IDBLISCRE : Unable to create [chars] interface list
Explanation This message indicates an internal software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LINK-3-IDBLISINS : Not able to insert interface [chars] into [chars] list
Explanation This message indicates an internal software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LINK-3-LINK_FAULT : [chars] [chars] [chars] [chars]
Explanation The link state for the port is down
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LINK-3-TOOSMALL : Interface [chars], Output runt packet of [dec] bytes
Explanation An output packet was detected that was smaller than the minimum allowable datagram size. An error in another driver or an error in the system software probably triggered this error message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LINK-3-UPDOWN : Interface [chars], changed state to [chars]
Explanation The interface hardware went either up or down.
Recommended Action If the state change was unexpected, confirm the configuration settings for the interface.
%LINK-4-BADQID : Interface [chars], bad output queue ID specified ([dec]). Packet dropped
Explanation This message indicates an internal software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LINK-4-BRIDGECONFLICT : Interface [chars], encapsulated BPDU recvd from [enet]
Explanation An FCIT running in nonencapsulating transparent mode detected an FDDI bridge running in encapsulation mode on the same fiber. This is an unstable situation and should be corrected. The incoming interface is displayed, along with the FDDI MAC address in standard form.
Recommended Action Upgrade the errant interface to full transparent mode. Copy the error message exactly as it appears, and report it to your Cisco technical support representative.
%LINK-4-FDDISTAT : Interface [chars], FDDI state [chars] detected
Explanation There was a state change on the FDDI ring.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LINK-4-NOMAC : A random default MAC address of [enet] has been chosen. Ensure that this address is unique, or specify MAC addresses for commands (such as 'novell routing') that allow the use of this address as a default.
Explanation An addressing inconsistency occurred.
Recommended Action Make sure that this address is unique, or specify MAC addresses for commands such as novell routing that allow the use of this address as a default.
%LINK-4-NOSSB : SSB deleted with timer running
Explanation An internal software error occurred. Problem has been corrected, and router operation has not been impaired.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LINK-4-TOOBIG : Interface [chars], Output packet size of [dec] bytes too big
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LINK-5-BOOTP : [chars] address [IP_address], resolved by [IP_address]
Explanation An interface's IP address was successfully learned dynamically through BootP. The first address is the learned IP address. The second IP address is the IP address of the BootP server that provided the information.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LINK-5-CHANGED : Interface [chars], changed state to [chars]
Explanation The interface hardware changed state.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LINK-5-LOOPSTATUS : Interface [chars], [chars]
Explanation The interface entered or exited loopback.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LINK-5-RARP : [chars] address [IP_address], resolved by [IP_address]
Explanation The Reverse Address Resolution Protocol (RARP) resolved an IP address.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LINK-5-REMLOOP : Interface [chars], remote loop [chars] [chars]
Explanation The interface entered or exited a remote loopback.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LINK-5-SLARP : [chars] address [IP_address], resolved by [IP_address]
Explanation The Serial Line Address Resolution Protocol (SLARP) resolved an IP address.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LINK-6-BERTMSGS : [chars]
Explanation BERT related information messages.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LINK-6-BERTSTATUS : Interface [chars], [chars]
Explanation BERT is completed for this interface.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
LISP_PROXY
%LISP_PROXY-3-PROXY_IPC_GET_STATS_FAILED : lisp proxy get stats failed for type[[chars]] idx = [dec], ppe_addr[[hex]].
Explanation Getting lisp default entry stats failed.
Recommended Action LOG_STD_ACTION
%LISP_PROXY-3-PROXY_IPC_INIT_FAILED : lisp proxy init failed, rc = [dec]
Explanation IPC handler initialization failed.
Recommended Action LOG_STD_ACTION
%LISP_PROXY-3-PROXY_IPC_PACKET_ALLOCATION_FAILED : lisp proxy alloc reply pak failed
Explanation Failed to allocate packet buffer for IPC
Recommended Action LOG_STD_ACTION
%LISP_PROXY-3-PROXY_IPC_PACKET_SEND_FAILED : lisp proxy send failed, rc = [dec]
Explanation Failed to send IPC packet.
Recommended Action LOG_STD_ACTION
%LISP_PROXY-3-PROXY_IPC_REQUEST_MSG_INVALID : lisp proxy request msg invalid.
Explanation Failed to get lisp default entry stats req from IPC packet.
Recommended Action LOG_STD_ACTION
%LISP_PROXY-4-PROXY_IPC_INVALID_MSG : invalid lisp proxy msg [dec]
Explanation Received an invalid IPC messages subtype.
Recommended Action LOG_STD_ACTION
LLC
%LLC-2-UNEXPECT : LLC2: [chars] UNEXPECTED EVENT
Explanation An internal software error was found. A software component is trying to use LLC2 structures that do not exist.
Recommended Action Record the configuration and any information that would be useful in recreating the error and call your technical support representative.
LLDP
%LLDP-4-LLDP_NEW_ENTRY : Neighbor record not committed -malloc failure
Explanation LLDP entry creation failed
Recommended Action Run memory diagnostics
LLIST
%LLIST-3-OFFLIST : [chars] from [hex], [hex] not on list
Explanation An internal inconsistency was detected when an attempt was made to remove an item from a list not on the list.
Recommended Action Copy the message exactly as it appears and report it to your technical service representative.
%LLIST-3-ONLIST : [chars] to [hex], [hex] on list
Explanation An internal inconsistency was detected when an attempt was made to add an item to a list already on the list.
Recommended Action Copy the message exactly as it appears and report it to your technical service representative.
LNMC
%LNMC-3-BADCLSI : [chars] primitive not valid for lnm [chars] [chars]
Explanation A LAN network manager system error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LNMC-3-BADCLSICNF : [chars] Invalid confirm [chars] [chars]
Explanation A LAN network manager system error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LNMC-3-BADCLSIDATALEN : [chars] Bad data len = [dec] [chars]
Explanation A LAN network manager system error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LNMC-3-BADCLSIHDRLEN : [chars] Bad header len = [hex] [chars]
Explanation A LAN network manager system error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LNMC-3-BADCLSIIDTYPE : [chars] Invalid ID type = [hex] [chars]
Explanation A LAN network manager system error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LNMC-3-BADCLSIIND : [chars] Invalid indication [chars], [chars]
Explanation A LAN network manager system error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LNMC-3-BADCLSIPRIMTYPE : [chars] Invalid primitive type = [hex] [chars]
Explanation A LAN network manager system error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LNMC-3-BADCLSIRET : [chars] Invalid ret code ([hex]) [chars], [chars]
Explanation A LAN network manager system error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LNMC-3-BADCLSISAP : [chars] Bad clsi SAP id = [hex] [chars]
Explanation A LAN network manager system error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
LOGGER
%LOGGER-3-ASSERT : failure at [hex]:[chars]:[int] ([chars]), MSGDEF_LIMIT_FAST
Explanation Software detected a fatal data inconsistency.
Recommended Action LOG_STD_ACTION
%LOGGER-3-IPC_INIT : failure
Explanation Logger client proxy IPC registration failed.
Recommended Action LOG_STD_ACTION
%LOGGER-3-IPC_UNHANDLED : failure, MSGDEF_LIMIT_GLACIAL
Explanation An unknown message was received by the logger client proxy.
Recommended Action LOG_STD_ACTION
%LOGGER-6-DROPPED : [int] messages, MSGDEF_LIMIT_GLACIAL
Explanation Due to a lack of available buffers, one or more log messages were dropped.
Recommended Action LOG_STD_ACTION
%LOGGER-6-IPC_ALLOC : failure, MSGDEF_LIMIT_GLACIAL
Explanation Logger client IPC alloc failed, messages were droppped.
Recommended Action LOG_STD_ACTION
%LOGGER-6-IPC_SEND : failure: [chars], MSGDEF_LIMIT_GLACIAL
Explanation Logger client IPC send failed, messages were dropped.
Recommended Action LOG_STD_ACTION
LSD
%LSD-2-APP_NOTSUPP : [chars] interface does not support app [chars]
Explanation Interface does not support app
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD-2-AVL : [chars] [hex]
Explanation AVL tree operation error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD-2-FPIHANDLER : [chars] [hex]
Explanation FPI Handler error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD-2-INVALID_VAR2 : [chars] [hex] [hex]
Explanation Function received invalid parameters
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD-2-INVALID_VAR : [chars]
Explanation Function received invalid parameters
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD-2-RESOURCE : [chars]
Explanation System resource error occured
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
%LSD-2-TESTAPP2 : Test app error: [chars]: [hex] [hex]
Explanation Test application error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD-3-APPMGR : [chars] [hex]
Explanation App Mansger error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD-3-BADEXEC : Unexpected Code Execution: [chars] [dec]
Explanation Unexpected Code Execution
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD-3-CHUNKMGR : chunk mgr: [chars] [hex]
Explanation Chunk manager error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD-3-CLIENT_CONN2 : [chars] [hex] [hex]
Explanation Client connection error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD-3-CLIENT_CONN : [chars]
Explanation Client connection error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD-3-EVTLOGBADSOURCE : Illegal log event source: [dec]
Explanation Illegal event found in log buffer
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD-3-INTF_DB2 : [chars] [hex] [hex]
Explanation interface db error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD-3-INTF_DB : [chars]
Explanation interface db error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD-3-INVALID_PROC_EVT : Unexpected process event [dec] for pid [dec]
Explanation The LSD component received an unexpected process event notification for the process with the specified ID
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD-3-LABEL2 : [chars] [hex] [hex]
Explanation label error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD-3-LABEL : [chars][dec]
Explanation label operation error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD-3-LABEL_TBL_ERR : Failed to create new label table due to [chars]
Explanation Label space is not carved properly. This is likely due to platform capabilities.
Recommended Action Check platform capabilities to make sure max label values are set correctly.
%LSD-3-MULTISERVICEREQ : Multiple outstanding service requests: [dec] [dec]
Explanation Server request attempted with one already outstanding
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD-3-OS_NOTIFY : Process id [dec] [chars], error code [dec]
Explanation LSD was unable to notify the operating system about (un)registration of the specified process.
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version, show running-config, show mpls infrastructure lsd apps and contact your Cisco technical support representative.
%LSD-3-OUTLABEL_RESV_ERROR : [chars]
Explanation outlabel reservation error - allocated cli-app outlabels are more than the platform supported outlabels
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD-3-REWMGR2 : [chars] [hex] [hex]
Explanation Rewrite lookup failed due to FPI inconsisency
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD-3-REWMGR : Rewrite Manager: [chars] [hex]
Explanation Rewrite Manager error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD-3-UPDATELISTMGR2 : [chars] [dec] [dec]
Explanation General error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD-3-UPDATELISTMGREXEC : Illegal exec: [chars] [hex]
Explanation Illegal code execution
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD-4-BADAPI : [chars] from [chars]
Explanation LSD recieved message with invalid parameters
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD-4-HW_RESOURCE_EXHAUSTED : Hardware resource exhausted on [chars] of type [dec]
Explanation The platform has run out of hardware resources.
Recommended Action Reduce the mpls configuration.
%LSD-4-INVALID_VAR_WARN : [chars]
Explanation Function received invalid parameters
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD-4-LABELFREETO : requested free timeout ([int] ms) by [chars] limited to: [int] ms
Explanation MPLS application label free timeout exceed max allowed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD-4-LABEL_RESOURCE : label range [dec]-[dec] exhausted
Explanation MPLS application is trying to allocate more labels than configuration will allow
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
LSD_CLIENT
%LSD_CLIENT-2-MSGHANDLERERR : Client=[dec] Msg type=[dec] Error=[chars]
Explanation LSD Client API message handler error encountered
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version and show running-config and contact your Cisco technical support representative.
%LSD_CLIENT-2-XDREXEC2 : [chars] [hex] [hex]
Explanation Illegal code execution in XDR path
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version and show running-config and contact your Cisco technical support representative.
%LSD_CLIENT-2-XDREXEC : [chars] [dec]
Explanation Illegal code execution in XDR path
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version and show running-config and contact your Cisco technical support representative.
%LSD_CLIENT-3-CLIENTAPI : Client API error: [chars] [dec]
Explanation Unexpected Client API error
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version and show running-config and contact your Cisco technical support representative.
%LSD_CLIENT-3-INVALID_VAR : [chars]
Explanation Function received invalid parameters
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version and show running-config and contact your Cisco technical support representative.
%LSD_CLIENT-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.
%LSD_CLIENT-3-ISSU_MSG_CONV : [chars] [dec] [dec]
Explanation Could not convert received message type to known message
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version and show running-config and contact your Cisco technical support representative.
%LSD_CLIENT-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.
%LSD_CLIENT-3-PCHUNK2 : [chars]: [chars] [hex] [hex]
Explanation Parameterized Chunk Manager error occurred
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version, show running-config and show process memory and contact your Cisco technical support representative.
%LSD_CLIENT-3-UTIL2 : [chars]: [hex] [hex]
Explanation MFI Utilities error occurred
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version and show running-config and contact your Cisco technical support representative.
LSD_HA
%LSD_HA-2-RESOURCE : [chars]
Explanation System resource error occured
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
%LSD_HA-2-RF : [chars][dec]
Explanation RF related error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD_HA-3-GENERAL : [chars]
Explanation Function received invalid parameters
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD_HA-3-INVALID_VAR : [chars]
Explanation Function received invalid parameters
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD_HA-3-LABEL_RANGE_DB : [chars]
Explanation Error happen in label range db
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD_HA-3-UNSENT_MSG_DB : [chars]
Explanation Error happen in unsent msg db
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD_HA-4-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
LSMPI
%LSMPI-4-INJECT_FEATURE_ESCAPE : Egress [chars] packet delivered via legacy inject path
Explanation A packet with a CPP supported L3 encapsulation (such as IP) was produced by IOS but delivered to CPP via the L2/legacy inject path instead of the proper L3 inject path. For this packet, outbound features will not be applied and packet accounting will likely be incorrect.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
LMLIB_RTU_LICENSE
%LMLIB_RTU_LICENSE-1-AP_INSUFFICIENT_PERM_APCOUNT : APs connected exceed the permanent licenses available by [dec].
Explanation The number of APs connected is greater than the number of permanent licenses.
Recommended Action Purchase adder licenses to add to your existing permanent licenses.
%LMLIB_RTU_LICENSE-1-AP_USAGE_EXCEEDED : AP-count license usage has exceeded the available AP-count by [dec].
Explanation AP-count license usage has exceeded the available AP-count.
Recommended Action Remove the excess APs from the controller.
%LMLIB_RTU_LICENSE-1-EVAL_EXP : Evaluation period of [chars] license expired [dec] days ago. Purchase a permanent license.
Explanation The evaluation license has expired.
Recommended Action Purchase a permanent license.
%LMLIB_RTU_LICENSE-1-EXCESS_AP_LIC : Total AP-count licenses available have exceeded the maximum supported AP-count by [dec].
Explanation The number of AP-count licenses available is greater than the maximum number of supported AP-count.
Recommended Action The extra AP-count licenses can be moved to another controller.
%LMLIB_RTU_LICENSE-1-PRIMARY_REMOVED : The current stack does not support the applied AP License Count. Reconnect a Catalyst 5760 SKU running valid AP License Count within 90 days.
Explanation AIR-CT5760-HA-K9 does not support the same licensing as AIR-CT5760-HA-K9. So an AIR-CT5760-HA-K9 SKU is needed in the stack to support this licensing.
Recommended Action Reconnect a Catalyst 5760 SKU running valid AP License Count within 90 days.
%LMLIB_RTU_LICENSE-1-RTU_DISABLED : Cannot proceed. Right-to-use Licensing is diabled. Switch is in Smart Licensing mode.
Explanation RTU functionality is disabled when switch in SL mode.
Recommended Action Enable RTU licensing with CLI: no license smart enable.
%LMLIB_RTU_LICENSE-1-SKU_INCOMPAT : Both the switches in the stack are AIR-CT5760-HA-K9 SKUs. Replace one of the switches with another Catalyst 5760 SKU running valid AP License Count
Explanation Two AIR-CT5760-HA-K9 SKUs are not supposed to stack.
Recommended Action Replace the license mismatch switch with a Catalyst 5760 SKU running valid AP License Count.
%LMLIB_RTU_LICENSE-1-TERM_EXP : Subscription term period of [chars] license expired [dec] days ago. Please renew your license.
Explanation The subscription license has expired.
Recommended Action Renew your subscription license.
%LMLIB_RTU_LICENSE-3-FILE_ERR : [chars]: License file update failed. Reapply the configuration.
Explanation Failed to update the license file.
Recommended Action Reapply the configuration.
%LMLIB_RTU_LICENSE-3-FILE_READ_ERR : [chars]: License file read failed.
Explanation Failed to read the license file.
Recommended Action Reapply the configuration.
%LMLIB_RTU_LICENSE-4-EVAL_WARN : Evaluation period of [chars] license is about to expire in [dec] days. Purchase a permanent license.
Explanation The evaluation license is about to expire.
Recommended Action Purchase a permanent license.
%LMLIB_RTU_LICENSE-4-TERM_WARN : Subscription term period of [chars] license is about to expire in [dec] days. Please renew your license.
Explanation The subscription license is about to expire.
Recommended Action Renew your subscription license.
%LMLIB_RTU_LICENSE-6-AP_ADD : [dec] adder AP-count licenses are added
Explanation AP-count licenses have been added.
Recommended Action More APs can be supported.
%LMLIB_RTU_LICENSE-6-AP_DEL : [dec] adder AP-count licenses are removed.
Explanation AP-count licenses have been removed.
Recommended Action Fewer APs are supported.
%LMLIB_RTU_LICENSE-6-DISABLE_RTU : [chars]: Right-to-use Licensing is disabled. Switch is in Smart Licensing mode.
Explanation User enables Smart Licensing.
Recommended Action Request image license license if needed.
%LMLIB_RTU_LICENSE-6-ENABLE_RTU : [chars]: Right-to-use Licensing is enabled. Switch is in RTU mode.
Explanation User configures RTU licensing by disabling Smart Licensing.
Recommended Action Configure image license and ap count license if needed.
%LMLIB_RTU_LICENSE-6-FACTORY_DEFAULT_ERROR : Factory Default License File [chars] on [chars].
Explanation An error occured when trying to create the factory default file.
Recommended Action Fix the issue and try again.
%LMLIB_RTU_LICENSE-6-IOSD_LIC_MISMATCH : Switch #[dec]: Current IOSd runs on [chars] license while RTU active license is [chars]. Please configure RTU license to current IOSd license.
Explanation When customer switches license mode from Smart Licensing to RTU Licensing, current IOSd license might mismatch with RTU active license.
Recommended Action Configure RTU license level to current IOSd license.
%LMLIB_RTU_LICENSE-6-LIC_ACT : [chars] license is activated successfully on [chars].
Explanation The license level is activated.
Recommended Action Reboot the switch to invoke the activated license.
%LMLIB_RTU_LICENSE-6-LIC_ACTVED : [chars] license was already activated.
Explanation The license level was already activated.
Recommended Action Reboot the switch to invoke the activated license.
%LMLIB_RTU_LICENSE-6-LIC_CHANGE : [chars] reboot license level changed from [chars] to [chars]. Reboot the switch to invoke the new license level.
Explanation Reboot license level has been changed.
Recommended Action Reboot the switch to invoke the activated license level.
%LMLIB_RTU_LICENSE-6-LIC_EULA_CLEAR : EULA for [chars] license has been cleared on [chars].
Explanation License level has been deactivated.
Recommended Action The end user license agreement (EULA) needs to be accepted while activating this license level.
%LMLIB_RTU_LICENSE-6-LIC_EVAL_TO_PERM : License level upgraded from [chars] [chars] to [chars] [chars]
Explanation A license has been upgraded to a permanent or subscription license. A reboot is NOT required for the new license level to be effective.
Recommended Action No action is required
%LMLIB_RTU_LICENSE-6-LIC_EXPED : [chars] evaluation license has expired you cannot activate it again.
Explanation You cannot use an expired evaluatoin license.
Recommended Action Purchase a permanent license level or activate another license level.
%LMLIB_RTU_LICENSE-6-LIC_IMAGE_INVALID : Switch #[dec]: The license boot level string is invalid. Boot up with the highest activated license.
Explanation The license boot level string is invalid. The RTU highest activated license is used.
Recommended Action Use 'license boot level' to configure a valid license level
%LMLIB_RTU_LICENSE-6-LIC_INCOMPAT : Switch [dec] has an incompatible license level. Activate a compatible license on the switch so that the switch can join the stack.
Explanation The added switch has an incompatible license level.
Recommended Action Activate a new license and reboot the switch.
%LMLIB_RTU_LICENSE-6-LIC_INVALID_DEACT : [chars] license is not active on [chars] therefore, it cannot be
Explanation The license level is not activated.
Recommended Action No need to deactivate this license.
%LMLIB_RTU_LICENSE-6-PLAT_INCOMPAT : Switch [dec] has an incompatible platform level. Activate a compatible platform on the switch so that the switch can join the stack.
Explanation The added switch has an incompatible platform level.
Recommended Action Run in compatible scaled mode and reboot the switch.
LMRP
%LMRP-0-CHASFS_LOCATION_TRANSLATE : Failed to translate a location to a chasfs object name because [chars]
Explanation The license 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.
%LMRP-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.
%LMRP-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.
%LMRP-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.
%LMRP-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.
%LMRP-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.
%LMRP-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.
%LMRP-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.
%LMRP-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.
%LMRP-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.
%LMRP-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.
%LMRP-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.
%LMRP-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.
%LMRP-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.
%LMRP-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.
%LMRP-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.
%LMRP-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.
%LMRP-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.
%LMRP-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.
%LMRP-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.
%LMRP-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.
%LMRP-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.
%LMRP-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.
%LMRP-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.
%LMRP-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.
%LMRP-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.
%LMRP-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.
%LMRP-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.
%LMRP-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.
%LMRP-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.
%LMRP-3-LICENSE_SERVICE_SETUP : Failed to setup the licensing proxy service
Explanation License Manager failed to set itself up as a proxy for licensable features.
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.
%LMRP-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.
%LMRP-3-RTU_UNINITIALIZED : RTU not yet initialized: stack enabled [dec]
Explanation License manager has not initialized RTU, but manager got RTU enable/disable request
Recommended Action No user action is necessary. Reloading might work
%LMRP-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.
%LMRP-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.
%LMRP-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.
LOGGER
%LOGGER-3-TEST1 : Non rate limited message test
Explanation None
Recommended Action None
%LOGGER-3-TEST2 : Rate limited message test
Explanation None
Recommended Action None
LSD
%LSD-2-APP_NOTSUPP : [chars] interface does not support app [chars]
Explanation Interface does not support app
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD-2-AVL : [chars] [hex]
Explanation AVL tree operation error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD-2-FPIHANDLER : [chars] [hex]
Explanation FPI Handler error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD-2-INVALID_VAR2 : [chars] [hex] [hex]
Explanation Function received invalid parameters
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD-2-INVALID_VAR : [chars]
Explanation Function received invalid parameters
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD-2-RESOURCE : [chars]
Explanation System resource error occured
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
%LSD-2-TESTAPP2 : Test app error: [chars]: [hex] [hex]
Explanation Test application error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD-3-APPMGR : [chars] [hex]
Explanation App Mansger error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD-3-BADEXEC : Unexpected Code Execution: [chars] [dec]
Explanation Unexpected Code Execution
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD-3-CHUNKMGR : chunk mgr: [chars] [hex]
Explanation Chunk manager error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD-3-CLIENT_CONN2 : [chars] [hex] [hex]
Explanation Client connection error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD-3-CLIENT_CONN : [chars]
Explanation Client connection error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD-3-EVTLOGBADSOURCE : Illegal log event source: [dec]
Explanation Illegal event found in log buffer
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD-3-INTF_DB2 : [chars] [hex] [hex]
Explanation interface db error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD-3-INTF_DB : [chars]
Explanation interface db error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD-3-INVALID_PROC_EVT : Unexpected process event [dec] for pid [dec]
Explanation The LSD component received an unexpected process event notification for the process with the specified ID
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD-3-LABEL2 : [chars] [hex] [hex]
Explanation label error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD-3-LABEL : [chars][dec]
Explanation label operation error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD-3-LABEL_TBL_ERR : Failed to create new label table due to [chars]
Explanation Label space is not carved properly. This is likely due to platform capabilities.
Recommended Action Check platform capabilities to make sure max label values are set correctly.
%LSD-3-MULTISERVICEREQ : Multiple outstanding service requests: [dec] [dec]
Explanation Server request attempted with one already outstanding
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD-3-OS_NOTIFY : Process id [dec] [chars], error code [dec]
Explanation LSD was unable to notify the operating system about (un)registration of the specified process.
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version, show running-config, show mpls infrastructure lsd apps and contact your Cisco technical support representative.
%LSD-3-OUTLABEL_RESV_ERROR : [chars]
Explanation outlabel reservation error - allocated cli-app outlabels are more than the platform supported outlabels
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD-3-REWMGR2 : [chars] [hex] [hex]
Explanation Rewrite lookup failed due to FPI inconsisency
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD-3-REWMGR : Rewrite Manager: [chars] [hex]
Explanation Rewrite Manager error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD-3-UPDATELISTMGR2 : [chars] [dec] [dec]
Explanation General error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD-3-UPDATELISTMGREXEC : Illegal exec: [chars] [hex]
Explanation Illegal code execution
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD-4-BADAPI : [chars] from [chars]
Explanation LSD recieved message with invalid parameters
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD-4-HW_RESOURCE_EXHAUSTED : Hardware resource exhausted on [chars] of type [dec]
Explanation The platform has run out of hardware resources.
Recommended Action Reduce the mpls configuration.
%LSD-4-INVALID_VAR_WARN : [chars]
Explanation Function received invalid parameters
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD-4-LABELFREETO : requested free timeout ([int] ms) by [chars] limited to: [int] ms
Explanation MPLS application label free timeout exceed max allowed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD-4-LABEL_RESOURCE : label range [dec]-[dec] exhausted
Explanation MPLS application is trying to allocate more labels than configuration will allow
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
LSD_HA
%LSD_HA-2-RESOURCE : [chars]
Explanation System resource error occured
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
%LSD_HA-2-RF : [chars][dec]
Explanation RF related error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD_HA-3-GENERAL : [chars]
Explanation Function received invalid parameters
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD_HA-3-INVALID_VAR : [chars]
Explanation Function received invalid parameters
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD_HA-3-LABEL_RANGE_DB : [chars]
Explanation Error happen in label range db
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD_HA-3-UNSENT_MSG_DB : [chars]
Explanation Error happen in unsent msg db
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%LSD_HA-4-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
LUA_VM
%LUA_VM-2-INITIALIZATION : Cannot initialize the Lua Virtual Machine
Explanation The Lua Virtual Machine is a critical component of the shell-manager process. It is used to render responses to user commands. If this component cannot be initialized then the shell-manager will be unable to process any commands directed at the IOS-XE daemons.
Recommended Action The shell-manager process could not be started. Check the trace log files for more details as to why the virtual machine failed to initialize correctly. This may be an out of memory condition so rebooting the chassis may resolve the problem.
M
MAB
%MAB-5-FAIL :
Explanation MAB Authentication was unsuccessful.
Recommended Action No action is required.
%MAB-5-SUCCESS :
Explanation MAB Authentication was successful.
Recommended Action No action is required.
MACSEC
%MACSEC-4-IPMTU_OVERSIZE : MACsec enabled interface [chars] IP MTU can't be more than [dec]
Explanation User config IP MTU size over MACsec enabled interface allows.
Recommended Action Reconfigure IP MTU base on the suggested range.
%MACSEC-4-RX_SC_EXCEED : (RX SCI [hex] : TX SCI [hex] : vport [dec] : secy vport [dec])
Explanation RX SC exceeds hardware limit.
Recommended Action No action required (normal operation).
%MACSEC-4-TX_SC_EXCEED : (TX SCI [hex] : vport [dec])
Explanation TX SC exceeds hardware limit.
Recommended Action No action required (normal operation).
%MACSEC-5-TX_SA_PN_EXPIRE : (TX SCI [hex] : AN [dec]) TX SA PN about to expire.
Explanation TX SA PN about to expire. Send a request to MKA to perform a SAK Rekey for the given TX SCI and AN.
Recommended Action No action required (normal operation).
%MACSEC-6-CREATE_RX_SC : ([chars] RX SCI [hex] : TX SCI [hex] : vport [dec] : secy vport [dec])
Explanation MKA request MACsec PD to create a RX SC on the given RX SCI and vport.
Recommended Action No action required (normal operation).
%MACSEC-6-CREATE_TX_SC : ([chars] TX SCI [hex] : vport [dec])
Explanation MKA request MACsec PD to create a TX SC on the given TX SCI and vport.
Recommended Action No action required (normal operation).
%MACSEC-6-DEL_RX_SA : ([chars] RX SCI [hex] : vport [dec] : an [dec])
Explanation MKA request MACsec PD to delete a RX SA on the given RX SCI, vport and an.
Recommended Action No action required (normal operation).
%MACSEC-6-DEL_RX_SC : ([chars] RX SCI [hex] : vport [dec])
Explanation MKA request MACsec PD to delete a RX SC on the given RX SCI and vport.
Recommended Action No action required (normal operation).No action required (normal operation).
%MACSEC-6-DEL_TX_SC : ([chars] TX SCI [hex] : vport [dec])
Explanation MKA request MACsec PD to delete a TX SC on the given TX SCI and vport.
Recommended Action No action required (normal operation).
%MACSEC-6-INSTALL_RX_SA : ([chars] RX SCI [hex] : vport [dec] : an [dec] : secy_vport [dec])
Explanation MKA request MACsec PD to install a RX SA on the given RX SCI, vport and an.
Recommended Action No action required (normal operation).
%MACSEC-6-INSTALL_TX_SA : ([chars] TX SCI [hex] : vport [dec] : an [dec] : next_pn [hex])
Explanation MKA request MACsec PD to install a TX SA on the given TX SCI, vport and an.
Recommended Action No action required (normal operation).
%MACSEC-6-POST_FAIL : ([chars] Power-On-System-Test failure in Trial No.[dec])
Explanation MACSEC power-on-system-test failed
Recommended Action No action required (normal operation).
%MACSEC-6-POST_SUCC : ([chars] Power-On-System-Test success in Trial No.[dec])
Explanation MACSEC power-on-system-test successful
Recommended Action No action required (normal operation).
MBOX
%MBOX-3-DEREG_FAIL_BAD_PARM : event [hex]
Explanation Deregistration of handler function for a mailbox event failed due to a bad parameter.
Recommended Action LOG_STD_ACTION
%MBOX-3-DEREG_FAIL_NO_HANDLER : event [hex], handler [hex]
Explanation Deregistration of handler function for a mailbox event failed because no handler was registered for the event.
Recommended Action LOG_STD_ACTION
%MBOX-3-NO_HANDLER_FOR_EVENT : events [hex] bad bit number [int]
Explanation Mailbox event is pending but no handler is registered for event.
Recommended Action LOG_STD_ACTION
%MBOX-3-REG_FAIL_BAD_PARM : event [hex], handler [hex]
Explanation Registration of handler function for a mailbox event failed due to a bad parameter.
Recommended Action LOG_STD_ACTION
%MBOX-3-REG_FAIL_HANDLER_EXISTS : event [hex], handler [hex]
Explanation Registration of handler function for a mailbox event failed because a handler is already registered for the event.
Recommended Action LOG_STD_ACTION
MCPRP_CLI
%MCPRP_CLI-6-LICENSE_EXPIRED : Shell access disabled due to license expiration
Explanation Shell license is expired. Thus the shell access is disabled
Recommended Action Get and install another shell license
MCPRP_DAI
%MCPRP_DAI-4-ERR_DISABLE : DAI detected error on [chars], putting [chars] to err-disable
Explanation Dynamic ARP inspection has detected an error condition because ARP packets have exceeded the configured rate or burst
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
MDNSPROXY
%MDNSPROXY-3-API_FAIL_MDNS : [chars] API failed
Explanation An error occurred while calling the APIs.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MDNSPROXY-3-CHUNK_MEMORY_FAIL : Chunk memory allocation failed
Explanation Chunk memory allocation failed for Cache element
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MDNSPROXY-3-INIT_MDNS_FAIL : [chars] Initialisation failure.
Explanation An internal error occurred during mDNS initialisation.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MDNSPROXY-3-NULL_CONTEXT_ID_MDNS : Encountered a NULL context for the ID [int]
Explanation NULL context for the ID passed in id_to_ptr.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MDNSPROXY-3-OS_API_FAIL_MDNS : IOS API [chars] failed
Explanation Encountered an error while calling the API.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MDNSPROXY-3-PORT_RESERVED_MDNS : [chars] Initialisation failure.
Explanation UDP Port 5353 Already reserved. Please disable the feature which uses 5353 and And Try Again.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
MCP_SYS
%MCP_SYS-0-ASSERTION_FAILED : Assertion failed: [chars]
Explanation An internal state consistency check failed.Correct operation cannot be guaranteed, and the system has been halted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
MCT1E1
%MCT1E1-2-CMD_DROP : [chars], cmd: [dec], arg0: [dec], arg1: [dec] arg2: [dec], arg3: [dec], vc: [dec] reason: [chars]
Explanation The SPA driver dropped a configuration command. One or more interfaces or controllers associated with the SPA may not be configured correctly.
Recommended Action Please check the configuration of the interfaces and controllers and correct the configuration if necessary. If the condition persists, copy the error message exactly as it appears, and report it to your technical support representative. Please also supply a show tech-support at that time.
%MCT1E1-2-EV_DROP : [chars], cmd: [dec], arg0: [dec], arg1: [dec] arg2: [dec] arg3: [dec] reason [chars]
Explanation The SPA driver dropped an event notification command. Counters or line protocols for one or more interfaces or controllers may be incorrect.
Recommended Action Please restart any interfaces or controllers that are down. If the condition persists, copy the error message exactly as it appears, and report it to your technical support representative. Please also supply a show tech-support at that time.
%MCT1E1-3-AUTODNR : [chars] failed for slot [dec] bay [dec] err [dec]
Explanation AUTODNR/USNDNR process has failed. The SPA and SIP are out of synchronization. This condition indicates a software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MCT1E1-3-BAD_SIZE_ERR : [chars]: [dec] [chars] events on HDLC Controller were encountered. The SPA is being Restarted.
Explanation The SPA driver detected an error event on the HDLC controller.
Recommended Action CTE1_STD_ACTION
%MCT1E1-3-BATCH_CMD_INVALID_TAG : [chars]: Invalid tag value [dec] at index [dec].
Explanation The SPA driver detected invalid tag value in a batch command.
Recommended Action The SPA driver has detected invalid command format from RP. If the ports on the SPA are not operating as expected, power down and reseat the indicated SPA card. CTE1_STD_ACTION
%MCT1E1-3-BERT_OPERATION_ERR : [chars]: BERT operation error on interface [chars] -[chars].
Explanation The SPA reported failure during BERT operation. The current BERT operation will be terminated, but the affected interface might not be operational, if that is the case, try to 'shutdown' and then 'no shutdown' the interface to recover from this failure.
Recommended Action If manual 'shutdown' and then 'no shutdown' of the interface does not restore the operation, then SPA will need to be reloaded to recover from this failure state.
%MCT1E1-3-BERT_STOP_ERR : [chars]: Failed to stop BERT operation on interface [chars] -[chars].
Explanation The SPA failed to stop the BERT operation on the indicated interface. The interface might not be functional after this event, if that is the case, try to 'shutdown' and then 'no shutdown' the interface to recover from this failure.
Recommended Action If manual 'shutdown' and then 'no shutdown' of the interface does not restore the operation, then SPA will need to be reloaded to recover from this failure state.
%MCT1E1-3-CMD_FAILED : [chars]: Failed to send command '[chars]' to SPA -[chars].
Explanation The SPA driver could not successfully send a cmd to firmware.
Recommended Action The SPA driver has detected a command failure. If the ports on the SPA are not operating as expected, power down and reseat the indicated SPA card. CTE1_STD_ACTION
%MCT1E1-3-COR_MEM_ERR : [chars]: [dec] correctable [chars] memory error(s) encountered. The error has been corrected and normal processing should continue. The memory address of most the recent error is: [hex]
Explanation The SPA driver detected a correctable memory error on the SPA card.
Recommended Action The SPA has encountered a correctable memory error on the SPA card. The error has been corrected and normal processing should continue. The hexadecimal memory address of the most recent error is specified in the message text on the console or in the system log. CTE1_STD_ACTION
%MCT1E1-3-FPGA_CNTR_ERR : [chars]: [dec] [chars] error(s) encountered.
Explanation The SPA driver detected an FPGA error condition on the SPA card. Interface packet error counter corruption may result.
Recommended Action The SPA driver has encountered a parity error on the SPA card. The SPA should continue to function normally. If the error condition recurs, please reset the SPA by doing a physical OIR. CTE1_STD_ACTION
%MCT1E1-3-FRMR_CLKFAIL : [chars]: Framer input clock failure detected, CTCLK = [chars]CTIVE, LREFCLK = [chars]CTIVE, SREFCLK = [chars]CTIVE, ctclk count [int] lrefclk count [int] srefclk count [int]
Explanation The SPA driver detected failure of one ore more input clocks to the framer chip. The T1/E1 Ports may not operate as expected.
Recommended Action The SPA driver has detected input clock failures on the framer chip. If the ports on the SPA are not operating as expected, power down and reseat the indicated SPA card. CTE1_STD_ACTION
%MCT1E1-3-HDLC_CTRL_ERR : [chars]: [dec] [chars] events on HDLC Controller were encountered.
Explanation The SPA driver detected an error event on the HDLC Controller.
Recommended Action The SPA driver has encountered an error event on the SPA card. CTE1_STD_ACTION
%MCT1E1-3-INITFAIL : MCT1E1 (bay [dec]), Init Failed at [chars] -line [dec] arg [hex]
Explanation The SPA failed to complete hardware initialization.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%MCT1E1-3-LOOPBACK_CFG_ERR : [chars]: Loop [chars] configuration error on controller [chars] -[chars][chars].
Explanation The SPA reported failure during setting of loop up/down operation. The current loopback will be terminated, but the affected controller might not be operational, if that is the case, try to 'shutdown' and then 'no shutdown' the controller to recover from this failure.
Recommended Action If manual 'shutdown' and then 'no shutdown' of the controller does not restore the operation, then SPA will need to be reloaded to recover from this failure state.
%MCT1E1-3-LOOP_UNSUPPORTED : [chars]: [chars] on port [dec]/[dec]/[dec] and it is not supported on SPA.
Explanation The SPA driver received 'loopback payload' request from the remote device on the SPA card. SPA does not support loopback payload.
Recommended Action The SPA driver has received 'loopback payload' request from the remote device on the SPA card. SPA does not support loopback payload. The remote request is ignored. Please unconfigure the command on the remote device.
%MCT1E1-3-PERIODIC_PROCESS : [chars]: periodic process error [chars].
Explanation The SPA driver detected an error with periodic processing routine.
Recommended Action The SPA driver has detected problem with periodic routine. If the ports on the SPA are not operating as expected, power down and reseat the indicated SPA card. CTE1_STD_ACTION
%MCT1E1-3-QUEUE_HALT_FAIL : [chars]: Could not suspend message ([dec]) or command ([dec]) queue
Explanation The Message/Command queue could not be stopped prior to the OIR removal of the SPA.
Recommended Action If the ports on the SPA are not operating as expected, power down and reseat the indicated SPA card. CTE1_STD_ACTION
%MCT1E1-3-SPI4_HW_ERR : [chars]: [chars] Hardware error was encountered.
Explanation The SPA driver detected a Hardware error condition on the SPA card. This might result in improper operation.
Recommended Action The SPA driver has encountered a Hardware error on the SPA's SPI4 bus. Please power down and reseat the indicated SPA card. CTE1_STD_ACTION
%MCT1E1-3-TIMEOUT : [chars]: [chars] failed: [dec], state: [dec], ml_id: [dec] progress: [dec]
Explanation Linkrec is stuck at non ready. This condition indicates a software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MCT1E1-3-UNCOR_MEM_ERR : [chars]: [dec] uncorrectable [chars] memory error(s) encountered. The memory address of the most recent error is: [hex]. The SPA is being restarted.
Explanation The SPA driver detected an uncorrectable memory error condition on the SPA card. Packet corruption may result.
Recommended Action The SPA driver has encountered an uncorrectable memory error on the SPA card. The hexadecimal memory address of the most recent error is specified in the message text on the console or in the system log. Please power down and reseat the indicated SPA card. CTE1_STD_ACTION
%MCT1E1-3-UNCOR_PARITY_ERR : [chars]: [dec] [chars] parity error(s) encountered. The address of the most recent error is: [hex]
Explanation The SPA driver detected an uncorrectable parity error condition on the SPA card. Packet corruption may result.
Recommended Action Please power down and reseat the indicated SPA card. CTE1_STD_ACTION
MDR
%MDR-3-NO_ACTIVE_ESP : No active ESP was found when initiating Minimal Disruptive Restart
Explanation An unexpected error has occured where no active ESP was found to continue forwarinding traffic during the Minimal Disruptive Restart. All requested linecards and or modules were reset as normal.
Recommended Action Review the IOSd, RP and CC chassis manager logs for errors or linecard OIR.
%MDR-3-NODE_ISSU_SIP_WAIT : Could not wait for [chars] to complete Minimal Disruptive Restart
Explanation An unexpected error has occured where the specified linecard was performing a Minimal Disruptive Restart using node ISSU, however Minimal Disruptive Restart did not complete before the next operation needed to commence. This linecard was reset as normal.
Recommended Action Review the IOSd, RP and CC chassis manager logs for errors or module OIR.
%MDR-3-NODE_ISSU_SPA_WAIT : Could not wait for [chars] in [chars] to complete Minimal Disruptive Restart
Explanation An unexpected error has occured where the specified module was performing a Minimal Disruptive Restart using node ISSU, however Minimal Disruptive Restart did not complete before the next operation needed to commence. This module was reset as normal.
Recommended Action Review the IOSd, RP and CC chassis manager logs for errors or module OIR.
%MDR-3-NO_SPAS_IN_SIP : No Minimal Disruptive Restart compatible SPAs found in [chars]
Explanation An unexpected error has occured where the specified linecard that was to undergo Minimal Disruptive Restart did not contain any compatible SPAs. This linecard was reset as normal.
Recommended Action Review the IOSd, RP and CC chassis manager logs for errors or module OIR.
%MDR-3-READ_COMPAT_INFO : Failed to read valid Minimal Disruptive Restart compatibility information for [chars]
Explanation An unexpected error has occured where either modules in or the specified linecard itself, was to undergo Minimal Disruptive Restart however valid compatibility information could not be read prior to commencing Minimal Disruptive Restart. If the linecard itself was to go through Minimal Disruptive Restart, it and the modules within it were reset as normal. If only modules were going through Minimal Disruptuve Restart, all modules were reset as normal.
Recommended Action Review the IOSd, RP and CC chassis manager logs for errors.
%MDR-3-READ_SIP_RESET : Failed to read a valid Minimal Disruptive Restart reset value for [chars]
Explanation An unexpected error has occured where either modules in or the specified linecard itself, was to undergo Minimal Disruptive Restart however a valid SIP reset value could not be read. This linecard was reset as normal.
Recommended Action Review the IOSd, RP and CC chassis manager logs for errors.
%MDR-3-RESTART_FAILED : Failed to perform Minimal Disruptive Restart on [chars]
Explanation An unexpected error has occured where the specified linecard or module failed to undergo a Minimal Disruptive Restart. This linecard or module was reset as normal.
Recommended Action Review the IOSd, RP and CC chassis manager logs for errors.
%MDR-3-SIP_OFFLINE : [chars] is not online to perform Minimal Disruptive Restart
Explanation An unexpected error has occured where the specified linecard was to undergo Minimal Disruptive Restart however the linecard was not found to be online. The linecard was reset as normal.
Recommended Action Review the IOSd, RP and CC chassis manager logs for errors or linecard OIR.
%MDR-3-SOFTWARE_TRANSFER : Failed to receive upgrade software for [chars]
Explanation An unexpected error has occured where the specified linecard was to undergo Minimal Disruptive Restart however the linecard was not able to receive the upgrade software prior to commencing Minimal Disruptive Restart. The linecard was reset as normal.
Recommended Action Review the IOSd, RP and CC chassis manager logs for errors.
%MDR-3-SPA_BAY_INVALID : Could not perform Minimal Disruptive Restart on invalid [chars] in [chars]
Explanation An unexpected error has occured where the specified module was to undergo Minimal Disruptive Restart however the module was invalid.
Recommended Action Review the IOSd, RP and CC chassis manager logs for errors or module OIR.
%MDR-3-SPA_IS_NOT_READY : [chars] in [chars] is not ready to perform Minimal Disruptive Restart
Explanation An unexpected error has occured where the specified module was to undergo Minimal Disruptive Restart however the module was not found to be ready. The module was reset as normal.
Recommended Action Review the IOSd, RP and CC chassis manager logs for errors or module OIR.
%MDR-3-SPA_NOT_FOUND : [chars] in [chars] could not be found to perform Minimal Disruptive Restart
Explanation An unexpected error has occured where the specified module was to undergo Minimal Disruptive Restart however the module was not found. The module was reset as normal.
Recommended Action Review the IOSd, RP and CC chassis manager logs for errors or module OIR.
%MDR-3-SPA_OFFLINE : [chars] in [chars] is not online to perform Minimal Disruptive Restart
Explanation An unexpected error has occured where the specified module was to undergo Minimal Disruptive Restart however the module was not found to be online. The module was reset as normal.
Recommended Action Review the IOSd, RP and CC chassis manager logs for errors or module OIR.
%MDR-3-SPA_TYPE_MISMATCH : Could not perform Minimal Disruptive Restart on [chars] in [chars] due to a SPA type mismatch
Explanation An unexpected error has occured where the specified module was to undergo Minimal Disruptive Restart however the module's SPA type was found to be different to what was expected. The module was reset as normal.
Recommended Action Review the IOSd, RP and CC chassis manager logs for errors or module OIR.
%MDR-3-SPA_WAS_NOT_READY : [chars] in [chars] was not ready to perform Minimal Disruptive Restart
Explanation An unexpected error has occured where the specified module was to undergo Minimal Disruptive Restart however the module was not found to be ready at the time it was checked. The module was reset was normal.
Recommended Action Review the IOSd, RP and CC chassis manager logs for errors or module OIR.
%MDR-5-CARD_RESTART : Minimal Disruptive Restart [chars] to acquire provisioned software
Explanation The FRU specified was not running the currently provisioned software, which it will acquire on Minimal Disruptive Restart.
Recommended Action No user action is necessary. This message indicates the system is functioning normally and is provided for informational purposes only.
%MDR-5-SIP_UNSUPPORTED : [chars] does not support Minimal Disruptive Restart
Explanation The linecard specified was restarted during an Minimal Disruptive Restart, however it does not support this feature either because of its type or there are no SPA's that support Minimal Disruptive Restart inserted. This linecard was reset as normal.
Recommended Action No user action is necessary.
%MDR-5-SPA_UNSUPPORTED : [chars] does not support Minimal Disruptive Restart
Explanation The module specified was restarted during an Minimal Disruptive Restart, however it does not support this feature either because of its type or software version. This module was reset as normal.
Recommended Action No user action is necessary.
MDT_SUBSCRIPTION
%MDT_SUBSCRIPTION-4-INVALID_ARGUMENTS :
Explanation Detailed explanation of why the subscription failed The value of the given parameter is invalid or not specified.
Recommended Action Correct the invalid parameter and try the subscription again.
%MDT_SUBSCRIPTION-4-NOT_SUPPORTED :
Explanation Detailed explanation of why the subscription failed The value of the given parameter is not supported.
Recommended Action Try the subscription again with a supported value.
%MDT_SUBSCRIPTION-4-OUTSIDE_LIMIT :
Explanation Detailed explanation of why the subscription failed The value of the parameter is outside of the allowable range.
Recommended Action Try the subscription again with a value within the allowable range.
%MDT_SUBSCRIPTION-4-XPATH_INVALID :
Explanation Detailed explanation of why the subscription failed The specified XPath filter is invalid.
Recommended Action Correct the XPath filter and try the subscription again.
MEM_MGR
%MEM_MGR-3-MEM_MGR_EXCEED_MAX : memory pool exceeds maximum ([dec] bytes) allowed.
Explanation An attempt was made to allocate a buffer from the specified memory pool which has reached its maximum limit
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MEM_MGR-3-MEM_MGR_INVALID : The Memory Management code encounters an invalid parameter.
Explanation It appears that the Memory Management code has received an invalid parameter from its caller.
Recommended Action Copy the error message exactly has it appears, and report it to your technical support representative.
%MEM_MGR-3-MEM_MGR_NOMEM : Out of memory
Explanation System out of memory.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MEM_MGR-2-DRAM_POOL_CREATE_ERR : return code [dec]
Explanation Creation of public DRAM memory pool failed.
Recommended Action LOG_STD_ACTION
%MEM_MGR-2-DUP_DRAM_POOL_CREATE : pool exists
Explanation Request to create public DRAM memory pool failed because pool already exists.
Recommended Action LOG_STD_ACTION
%MEM_MGR-2-DUP_SRAM_POOL_CREATE : pool exists
Explanation Request to create public SRAM memory pool failed because pool already exists.
Recommended Action LOG_STD_ACTION
%MEM_MGR-2-ELEMENT_CORRUPT : pool handle [hex], addr 0x5x, magic value [hex], ref cnt [int], MSGDEF_LIMIT_MEDIUM
Explanation Memory element has been corrupted.
Recommended Action LOG_STD_ACTION
%MEM_MGR-2-POOL_CORRUPT : pool handle [hex], magic value [hex], MSGDEF_LIMIT_MEDIUM
Explanation Memory pool data structure has been corrupted.
Recommended Action LOG_STD_ACTION
%MEM_MGR-2-SRAM_POOL_CREATE_ERR : return code [dec]
Explanation Creation of public SRAM memory pool failed.
Recommended Action LOG_STD_ACTION
%MEM_MGR-3-DESTROY_PARM_ERR : pool handle [hex]
Explanation Request to delete memory pool failed due to bad parameter value.
Recommended Action LOG_STD_ACTION
%MEM_MGR-3-FREE_PARM_ERR : pool handle [hex], addr [hex]
Explanation Memory deallocation request failed due to bad parameter value.
Recommended Action LOG_STD_ACTION
%MEM_MGR-3-LOCK_MAX_REF_CNT : pool handle [hex], addr [hex], MSGDEF_LIMIT_MEDIUM
Explanation Request to lock memory pool element failed due to reference count for element already being at the maximum value.
Recommended Action LOG_STD_ACTION
%MEM_MGR-3-LOCK_PARM_ERR : pool handle [hex], addr [hex]
Explanation Request to lock memory pool element failed due to bad parameter value.
Recommended Action LOG_STD_ACTION
%MEM_MGR-3-MALLOC_NO_MEM : pool handle [hex], size [int], MSGDEF_LIMIT_MEDIUM
Explanation Memory pool allocation request failed due to insufficient memory being available.
Recommended Action LOG_STD_ACTION
%MEM_MGR-3-MALLOC_PARM_ERR : pool handle [hex], size [int]
Explanation Memory allocation request failed due to bad parameter value.
Recommended Action LOG_STD_ACTION
%MEM_MGR-3-POOL_APPEND_PARM_ERR : pool handle [hex], addr [hex], size [int]
Explanation Append of additional memory to pool failed due to bad parameter value.
Recommended Action LOG_STD_ACTION
%MEM_MGR-3-POOL_CREATE_PARM_ERR : addr [hex], size [int]
Explanation Creation of memory pool failed due to bad parameter value.
Recommended Action LOG_STD_ACTION
%MEM_MGR-3-POOL_STATS_PARM_ERR : pool handle [hex], stats addr [hex]
Explanation Read of memory pool statistics failed due to bad parameter value.
Recommended Action LOG_STD_ACTION
MEM_PROXY
%MEM_PROXY-3-PROXY_IPC_PAK_ALLOC_FAILED :
Explanation Allocation of IPC packet failed.
Recommended Action LOG_STD_ACTION
%MEM_PROXY-3-PROXY_IPC_SEND_FAILED : [chars]
Explanation Could not send IPC request for more memory.
Recommended Action LOG_STD_ACTION
METS
%METS-2-INITFAIL : Can't start analysis
Explanation The requested operation failed due to lack of resource, maybe temporarily
Recommended Action Reduce system resource/memory usage, and retry for the commands.
%METS-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%METS-3-NOREGION : No region found: [chars]
Explanation Resource failure: No region found.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%METS-3-NULLPOOL : Can't process null pool: [chars]
Explanation Resource failure: Null pool in the region
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
MFI
%MFI-3-BADREADUPDATESIZE : Read update reply message from RP has bad size: [dec]
Explanation read update message does not match the read message parse result
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MFI-3-CLIENT_INTF : [chars]: [hex] [hex]
Explanation Client Interface
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MFI-3-EVTLOGCAPTURE : Event Logger Capture Error [dec] [dec]
Explanation Failure during Event Logger capture
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MFI-3-EVTLOGCLIENT : Invalid client [dec]
Explanation Invalid client accessed the Event Logger
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MFI-3-EVTLOGCONTROL : [chars]: [dec]
Explanation General Event Logger Controller error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MFI-3-EVTLOGREGISTER : Event Logger Registration Error [dec] [dec] [dec]
Explanation Failure during Event Logger client registration
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MFI-3-LCPULSE : LC pulse failed: [chars] [dec]
Explanation LC pulse request operation failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MFI-3-MFICOMM2 : [chars]: [hex] [hex]
Explanation MFI General Communication Module
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MFI-3-MFICOMM3 : [chars]: [hex] [hex] [hex]
Explanation MFI General Communication Module
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MFI-3-MFICOMM : [chars]
Explanation MFI General Communication Module
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MFI-3-MPLS_MTU_SET : [chars] [dec] [chars] [chars] [chars] [dec][chars]
Explanation Most drivers will be able to support baby giants and will gracefully drop packets that are too large. Certain drivers will have packet forwarding problems including data corruption.
Recommended Action Please increase the interface mtu on all routers connected to this interface to the needed mtu size using mtu bytes command.
%MFI-3-PNDMSGMGR : [chars] [chars] [dec] [dec] [dec]
Explanation Only one outstanding request is allowed from same process
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MFI-3-REDISTMGR2 : Redistribution Manager: [chars] [hex] [hex]
Explanation Redistribution Manager error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MFI-3-REDISTMGR : Redistribution Manager: [chars] [hex]
Explanation Redistribution Manager error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MFI-3-REPLYMSGSIZE : Reply message is too large: [chars]: [dec]
Explanation read update message won't fit into xdr buffer
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MFI-4-MFICOMM_WARN_1 : [chars]: [hex]
Explanation MFI General Communication Module
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MFI-4-NOCLIENTREQ : [chars] [chars]: [dec] [dec] [dec]
Explanation Client reply could not find an outstanding request
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MFI-4-REDISTMGR3 : Redistribution Manager: [chars] [hex]
Explanation Redistribution Manager error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
MFIB
%MFIB-3-ADJ_GSB_INIT :
Explanation Could not initialise the adjacency GSB memory pool
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%MFIB-3-ADJ_GSB_REGISTER :
Explanation Could not register an adjacency GSB identifier
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%MFIB-3-DECAP_OCE_CREATION_FAILED : Decap OCE creation 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MFIB-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MFIB-3-MFIB_CTXT_DEPTH_EXCEEDED :
Explanation MFIB has exceeded maximum number of switching contexts
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%MFIB-3-MRIB_PROCESS : [chars][chars]
Explanation The MFIB process which intefaces with the MRIB failed to start. The MFIB will be unusable.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%MFIB-3-NETWORK_GET_FAIL : MFIB can not get network offset: datagram [hex]; network [hex]
Explanation The MFIB failed to find a suitable packet network offset
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%MFIB-3-NETWORK_SET_FAIL : MFIB can not set network offset: datagram [hex]; length [dec]; offset [dec]
Explanation The MFIB failed to set offset within packet
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%MFIB-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MFIB-3-SR_ADJ_GSB_INIT :
Explanation Could not initialise the SR adjacency GSB memory pool
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%MFIB-3-SR_ADJ_GSB_REGISTER :
Explanation Could not register an SR adjacency GSB identifier
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%MFIB-3-SR_ADJ_INCORRECT_ADD : A different MFIB Service Reflect adj is being added
Explanation A different SR adjacency subblock is being added to the adjacency without first removing the existing one. This indicates that SR forwarding may no longer work correctly
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%MFIB-3-WIRE_LOOKUP_OR_ALLOC_FAILED : Lookup or allocation of MFIB wire failed
Explanation Lookup or allocation of MFIB wire failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MFIB-6-MFIB_HEADER_LIMIT_EXCEEDED : [dec] at [chars]
Explanation MFIB attempted to exceed maximum number of replicated packet header buffers
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%MFIB-6-MFIB_POOL_GETBUFFER_FAILURE :
Explanation MFIB has failed in an attempt to retrieve a particular type of memory. The MFIB will continue using another memory area
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%MFIB-6-PAK_TOO_SHORT : Packet too short from [chars], datagram size [dec], tl [dec]
Explanation An IP/IPv6 packet which is too short was received
Recommended Action No action is required.
MFIB_PLTF
%MFIB_PLTF-3-ANNOT_TOO_LONG : [chars] [IPV6 address] [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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MFIB_PLTF-3-CALLBACK_RETURN_INVALID : [chars]. [IPV6 address] [IPV6 address] [IPV6 address]
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MFIB_PLTF-3-ENTRY_DUPLICATE_ADD : [chars] entry [chars] [[IPV6 address] ([IPV6 address]/[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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MFIB_PLTF-3-ENTRY_HANDLE_BAD : [chars]. [IPV6 address]
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MFIB_PLTF-3-ENTRY_LOCK_FAIL : [chars]. [chars] entry [IPV6 address] [chars] [[IPV6 address] ([IPV6 address]/[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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MFIB_PLTF-3-ENTRY_UNLOCK_FAIL : [chars]. [chars] entry [IPV6 address] [chars] [[IPV6 address] ([IPV6 address]/[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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MFIB_PLTF-3-HANDLE_CONSTRAINT : [chars] [IPV6 address]
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MFIB_PLTF-3-IOITEM_DUPLICATE_ADD : [chars] ioitem [chars] [chars] [[IPV6 address] ([hex]/[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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MFIB_PLTF-3-IOITEM_HANDLE_BAD : [chars]. [IPV6 address]
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MFIB_PLTF-3-IOITEM_LOCK_FAIL : [chars]. [chars] ioitem [IPV6 address] [chars] [chars] [[IPV6 address] ([IPV6 address]/[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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MFIB_PLTF-3-IOITEM_UNLOCK_FAIL : [chars]. [chars] ioitem [IPV6 address] [chars] [chars] [[IPV6 address] ([IPV6 address]/[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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MFIB_PLTF-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MFIB_PLTF-3-TABLE_HANDLE_BAD : [chars]. [IPV6 address]
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MFIB_PLTF-3-TABLE_LOCK_FAIL : [chars]. [chars] table [IPV6 address] [IPV6 address] ([IPV6 address]/[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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MFIB_PLTF-3-TABLE_UNLOCK_FAIL : [chars]. [chars] table [IPV6 address] [IPV6 address] ([IPV6 address]/[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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MFIB_PLTF-3-TRANSACTION_MEMORY : [dec] [dec]
Explanation Failed to allocate memory for platform transaction.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
%MFIB_PLTF-3-UPDATE_SET_MEMORY : [chars] [IPV6 address] -> [chars] [[IPV6 address] ([IPV6 address]/[chars])]
Explanation Failed to allocate memory for platform transaction.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
%MFIB_PLTF-3-XDRISSUREGERROR : ISSU client [chars] ([dec]), entity [dec], failed ISSU registration: [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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
MFI_LABEL_BROKER
%MFI_LABEL_BROKER-3-DELETE_MOI_FAIL : Label [dec] in table [dec], [chars], [chars]
Explanation The MFI Label Broker could not honor a request to immediately handle the process restart of the application indicated. It will try to handle it in the background
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release and contact your Cisco technical support representative.
%MFI_LABEL_BROKER-3-DUPREG_LDM : [chars]
Explanation An MPLS application is registering multiple times with the label broker.
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version and show running-config and contact your Cisco technical support representative.
%MFI_LABEL_BROKER-3-IMMEDIATE_LDM_RESTART : application [chars]
Explanation None
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version and show running-config and contact your Cisco technical support representative.
%MFI_LABEL_BROKER-3-INVALID_LABEL : [dec]
Explanation The MFI Label Broker received a request to allocate an invalid label.
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version and show running-config and contact your Cisco technical support representative.
%MFI_LABEL_BROKER-3-INVALID_LDM : [dec]
Explanation The MFI Label Broker received a (un)registration request from an invalid MPLS application.
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version and show running-config and contact your Cisco technical support representative.
%MFI_LABEL_BROKER-3-INVALID_PARAM : [chars]
Explanation The MFI Label Broker received an invalid parameter in a request to allocate or free a local label.
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version and show running-config and contact your Cisco technical support representative.
%MFI_LABEL_BROKER-3-INVALID_PID : LDM([dec]), PID([dec])
Explanation The MFI Label Broker received a registration request with invalid PID.
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version and show running-config and contact your Cisco technical support representative.
%MFI_LABEL_BROKER-3-INVALID_PROC_EVT : [chars][dec][chars][dec]
Explanation The MFI Label Broker received an invalid process event from the IOS-on-Neutrino infrastructure.
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version and show running-config and contact your Cisco technical support representative.
%MFI_LABEL_BROKER-3-LABEL_PROGRAM_FAIL : Label [dec] in table [dec], for [chars]
Explanation The MFI Label Broker was unable to program the label in question for the mentioned FEC.
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version, show running-config, show mpls forwarding-table internal and contact your Cisco technical support representative.
%MFI_LABEL_BROKER-3-MULTIPLE_BIND : Label [dec] in table [dec], [chars], [chars] [p/bm [dec]/[hex]],ldm request info: [chars]
Explanation The MFI Label Broker received a request to bind the label to a prefix, but the label is already bound to another prefix.
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version, show running-config and show mpls forwarding-table and contact your Cisco technical support representative.
%MFI_LABEL_BROKER-3-NO_ACTIVE_LABEL : [chars] Label [dec] in table [dec], [chars] [hex]
Explanation The MFI Label Broker encountered a situation where there is no currently active label for applications to use for the FEC indicated.
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version, show running-config, show mpls forwarding-table internal and contact your Cisco technical support representative.
%MFI_LABEL_BROKER-3-NULL_KEY :
Explanation The MFI Label Broker received a null key pointer
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version and show running-config and contact your Cisco technical support representative.
%MFI_LABEL_BROKER-3-OS_NOTIFY : Process id [dec] [chars], error code [dec]
Explanation The MFI Label Broker was unable to notify the operating system about (un)registration of the specified process.
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version, show running-config, show mpls infrastructure label-broker ldm and contact your Cisco technical support representative.
%MFI_LABEL_BROKER-3-UNREG_LDM : [chars]
Explanation An MPLS application requested label broker services without registering first.
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version and show running-config and contact your Cisco technical support representative.
MGCP_APP
%MGCP_APP-6-RTP_SERVICES_INIT_FAILED : Failed to start VOIP call leg
Explanation Failed to start VOIP call leg.
Recommended Action Check the size of free memory to make sure there is enough memory.
MLDP
%MLDP-2-CHUNK_ERR : Error initializing MLDP db chunks
Explanation Error initializing MLDP db chunks
Recommended Action No action is required.
%MLDP-2-FEC_CHUNK_ERR : Error initializing MLDP FEC chunks
Explanation Error initializing MLDP FEC chunks
Recommended Action No action is required.
%MLDP-2-FEC_ERR : Error, the FEC size is too large
Explanation The FEC size is too large
Recommended Action No action is required.
%MLDP-2-FEC_NTF_ERR : Error initializing MLDP FEC notifier
Explanation Error initializing MLDP FEC notifier
Recommended Action No action is required.
%MLDP-2-FEC_TBL_ERR : Error initializing MLDP FEC tbl
Explanation Error initializing MLDP FEC tbl
Recommended Action No action is required.
%MLDP-2-FILTER_CHUNK_ERR : Error initializing MLDP filter chunks
Explanation Error initializing MLDP filter chunks
Recommended Action No action is required.
%MLDP-2-FILTER_NTF_ERR : Error registering MLDP filter FEC notifier
Explanation Error registering MLDP filter FEC notifier
Recommended Action No action is required.
%MLDP-2-FILTER_TBL_ERR : Error initializing MLDP filter tbl
Explanation Error initializing MLDP filter tbl
Recommended Action No action is required.
%MLDP-2-HA_INSERT_ERR : Error inserting node into MLDP HA radix tree
Explanation Error inserting node into MLDP HA radix tree
Recommended Action No action is required.
%MLDP-2-ID_RESERVE_ERR : Error reserving id for mldp database
Explanation Error reserving id for mldp database
Recommended Action No action is required.
%MLDP-2-INTERNAL_ERR : Internal mLDP error
Explanation Internal error
Recommended Action No action is required.
%MLDP-2-MRIB_PROCESS_ERR : Error initializing MLDP MRIB process
Explanation Can't start the MLDP MRIB process
Recommended Action No action is required.
%MLDP-2-PEER_ERR : Received attached address [IP_address], but there is no LDP peer
Explanation Internal error
Recommended Action No action is required.
%MLDP-2-PEER_NOT_FOUND : Peer doesn't exist while syncing to standby
Explanation Peer doesn't exist while syncing to standby
Recommended Action No action is required.
%MLDP-2-PROCESS_ERR : Error initializing MLDP process
Explanation Can't start the MLDP process
Recommended Action No action is required.
%MLDP-2-RADIX_BRANCH_ERR : Error initializing MLDP BRANCH radix tree
Explanation Internal error
Recommended Action No action is required.
%MLDP-2-RADIX_DB_ERR : Error initializing MLDP DB radix tree
Explanation Error initializing MLDP_DB radix ree
Recommended Action No action is required.
%MLDP-2-ROOT_NOT_FOUND : Root doesn't exist while syncing to standby.
Explanation Root doesn't exist while syncing to standby
Recommended Action No action is required.
%MLDP-4-DB_BRANCH_DEL_PENDING : [chars] tree, with LSM ID: [hex] has both IPv4 and IPv6 del_pending set
Explanation An mLDP database entry has both the IPv4 and IPv6 del_pending flags set to TRUE -- This is an inconsistent state
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MLDP-5-ADD_BRANCH : [chars] Root: [IP_address], Add [chars] branch [chars] [chars]
Explanation Logging of changes to mLDP branch
Recommended Action No action is required.
%MLDP-5-DELETE_BRANCH : [chars] Root: [IP_address], Delete [chars] branch [chars] [chars]
Explanation Logging of changes to mLDP branch
Recommended Action No action is required.
%MLDP-5-MODIFY_BRANCH : [chars] Root: [IP_address], Modify [chars] branch [chars] [chars]
Explanation Logging of changes to mLDP branch
Recommended Action No action is required.
%MLDP-5-MODIFY_NBR : [chars] Root: [IP_address], Modify [chars] entry peer [chars] [chars]
Explanation Logging of changes to mLDP entry peer
Recommended Action No action is required.
%MLDP-5-ROUTING_LOOP : There is a routing loop for this root.
Explanation There is a routing loop for this root
Recommended Action No action is required.
MMA
%MMA-2-IPC_INIT : IPC message handler registration failure, rc [int]
Explanation Registering an IPC message handler for the MMA feature failed. This will cause the feature to not function.
Recommended Action This is normally a software issue. The consequences are that the MMA feature will not function. LOG_STD_ACTION
%MMA-3-CACHE_OVERFLOW : The number of flows has exceeded 95 percent of the configured size, monitor [chars], please increase cache size
Explanation This is warning message if the flow size exceeds the maximum value
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MMA-3-CHUNKCREATE : Failed to chunk create memory for [chars]
Explanation Unable to chunk create memory chunk
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MMA-3-CHUNKDESTROY : Failed to chunk destroy memory for [chars]
Explanation Unable to chunk destroy memory chunk
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MMA-3-CHUNKMALLOC : Failed to malloc chunk memory for [chars]
Explanation Unable to malloc memory chunk, malloc failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MMA-3-DB : [chars]
Explanation Error during managing MMA database
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MMA-3-FIELD : [chars]
Explanation Error during initializing a field
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MMA-3-FLOW_EXCEED : The number of flows has exceeded 95 percent of the configured maximum flow. [chars]
Explanation This is warning message if the flow size exceeds the maximum value
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MMA-3-FLOW_NONEXCEED : The number of flows is below 85 percent of the configured maximum flow. [chars]
Explanation This is info message if the flow size falls below the maximum value
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MMA-3-INV_ACTION_OBJ : action object is not valid -[chars]
Explanation This is an internal error, the saved action object info is corrupted
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MMA-3-INV_ARG : The argument is not valid -[chars]
Explanation An internal error occurred. The argument for an internal API is not valid
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MMA-3-INV_COMMON_MONITOR : The common monitor pointer is invalid
Explanation An internal error occurred. The common monitor pointer saved in the performance-monitor monitor is NULL
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MMA-3-INV_DB_OBJ : Internal error, mma db pointer invalid
Explanation No valid pointer to mma db
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MMA-3-INV_MONITOR : The flow monitor pointer is invalid
Explanation An internal error occurred. The performance-monitor monitor pointer saved in the common monitor is NULL
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MMA-3-INV_MONITOR_TYPE : The monitor type [dec] is invalid
Explanation An internal error occurred. The monitor type is out of the range
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MMA-3-INV_REACT : react is not valid -[chars]
Explanation This is an internal error, the saved react info is corrupted
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MMA-3-IPC_NORES : No space for the IPC reply, size [int]
Explanation For a request from upper MMA 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 binding 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
%MMA-3-IPC_OPEN_REPLY : IPC Open Reply failed, request [int]
Explanation For a request from upper MMA software stack layers it was not possible to open the reply buffer. The consequence of this could be a stuck binding 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
%MMA-3-LIST : Failed to [chars] list [chars]
Explanation A list operation failed. This could be caused by memory corruption
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MMA-3-MCOL : [chars]
Explanation Error during collecting metrics in MMA PI
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MMA-3-MEM : Memory [chars] failed -[chars]
Explanation Memory creation failed during the initialization
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MMA-3-NULLFLOW : A flow does not exist
Explanation An internal error occurred. Try to access a null flow
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MMA-3-NULLHIST : A history bucket does not exist
Explanation An internal error occurred. Try to access a null history
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MMA-3-PARSER : [chars]
Explanation Error during register parser or parsing CLI
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MMA-3-PROV : [chars]
Explanation A fatal error happened during provision
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MMA-3-RM_SET : [chars]
Explanation An error happened during setting of Resource Manager event
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MMA-2-IPC_INIT : IPC message handler registration failure, rc [int]
Explanation Registering an IPC message handler for the MMA feature failed. This will cause the feature to not function.
Recommended Action This is normally a software issue. The consequences are that the MMA feature will not function. LOG_STD_ACTION
%MMA-3-CACHE_OVERFLOW : The number of flows has exceeded 95 percent of the configured size, monitor [chars], please increase cache size
Explanation This is warning message if the flow size exceeds the maximum value
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MMA-3-CHUNKCREATE : Failed to chunk create memory for [chars]
Explanation Unable to chunk create memory chunk
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MMA-3-CHUNKDESTROY : Failed to chunk destroy memory for [chars]
Explanation Unable to chunk destroy memory chunk
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MMA-3-CHUNKMALLOC : Failed to malloc chunk memory for [chars]
Explanation Unable to malloc memory chunk, malloc failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MMA-3-DB : [chars]
Explanation Error during managing MMA database
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MMA-3-FIELD : [chars]
Explanation Error during initializing a field
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MMA-3-FLOW_EXCEED : The number of flows has exceeded 95 percent of the configured maximum flow. [chars]
Explanation This is warning message if the flow size exceeds the maximum value
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MMA-3-FLOW_NONEXCEED : The number of flows is below 85 percent of the configured maximum flow. [chars]
Explanation This is info message if the flow size falls below the maximum value
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MMA-3-INV_ACTION_OBJ : action object is not valid -[chars]
Explanation This is an internal error, the saved action object info is corrupted
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MMA-3-INV_ARG : The argument is not valid -[chars]
Explanation An internal error occurred. The argument for an internal API is not valid
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MMA-3-INV_COMMON_MONITOR : The common monitor pointer is invalid
Explanation An internal error occurred. The common monitor pointer saved in the performance-monitor monitor is NULL
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MMA-3-INV_DB_OBJ : Internal error, mma db pointer invalid
Explanation No valid pointer to mma db
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MMA-3-INV_MONITOR : The flow monitor pointer is invalid
Explanation An internal error occurred. The performance-monitor monitor pointer saved in the common monitor is NULL
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MMA-3-INV_MONITOR_TYPE : The monitor type [dec] is invalid
Explanation An internal error occurred. The monitor type is out of the range
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MMA-3-INV_REACT : react is not valid -[chars]
Explanation This is an internal error, the saved react info is corrupted
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MMA-3-IPC_NORES : No space for the IPC reply, size [int]
Explanation For a request from upper MMA 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 binding 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
%MMA-3-IPC_OPEN_REPLY : IPC Open Reply failed, request [int]
Explanation For a request from upper MMA software stack layers it was not possible to open the reply buffer. The consequence of this could be a stuck binding 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
%MMA-3-LIST : Failed to [chars] list [chars]
Explanation A list operation failed. This could be caused by memory corruption
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MMA-3-MCOL : [chars]
Explanation Error during collecting metrics in MMA PI
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MMA-3-MEM : Memory [chars] failed -[chars]
Explanation Memory creation failed during the initialization
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MMA-3-NULLFLOW : A flow does not exist
Explanation An internal error occurred. Try to access a null flow
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MMA-3-NULLHIST : A history bucket does not exist
Explanation An internal error occurred. Try to access a null history
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MMA-3-PARSER : [chars]
Explanation Error during register parser or parsing CLI
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MMA-3-PROV : [chars]
Explanation A fatal error happened during provision
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MMA-3-RM_SET : [chars]
Explanation An error happened during setting of Resource Manager event
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
MN_SPA_PTP
%MN_SPA_PTP-3-BITS_CLOCK : [chars] : SPA bits transmit clock has encountered error : [hex] .
Explanation Error message regarding BITS transmit clock failure
Recommended Action OIR the SPA if the error is consistent
%MN_SPA_PTP-3-GMII_LINKUP_DOWN : GMII Links are [chars] and [chars] for ports 1 and 2 respectively on the SPA.
Explanation Error Message: GMII link status has changed on the SPA.
Recommended Action OIR the SPA to recover from the error.
%MN_SPA_PTP-3-SEMAHOG : SEMAHOG by SPA [chars] Process holding Sema is [chars]
Explanation SEMAPHORE LOCK ERROR
Recommended Action Remove the config which caused this
%MN_SPA_PTP-4-PTP_CLOCK_MODE : SPA [dec]/[dec] is working in PTP SLAVE or Boundary mode external clock on BITS port would be PTP recovered clock
Explanation Info regarding external clock in PTP slave mode
Recommended Action No further action required. (This is an INFORMATION message, not an error Message.)
%MN_SPA_PTP-6-CONFIG_CHANGE : Change in ToP configuration on [dec]/[dec]. This will result into Termination of all existing PTP sessions on [dec]/[dec].
Explanation To take effect of new/changed configuration requrie restart of PTP session
Recommended Action No further action required. (This is an INFORMATION message, not an error Message.)
%MN_SPA_PTP-6-SPLL_STATE_CHANGE : Recovered clock in [dec]/[dec] status changed to [chars]
Explanation Recovered clock status change info
Recommended Action No further action required. (This is an INFORMATION message, not an error Message.)
MONITOR
%MONITOR-3-VPN_EVENT : ipsec : [chars] : [dec] events, MSGDEF_LIMIT_FAST
Explanation Crypto failure count hits limit. This message is just a warning, not an error.
Recommended Action LOG_STD_ACTION
%MONITOR-3-VARRESTFAIL : ROM monitor variable restoration of [chars], failed.
Explanation The new ROM monitor variable could not be written to memory, and the ROM monitor variable could not be restored to its original value.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support and show bootvar commands 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 tech-support and show bootvar command output, contact your Cisco technical support representative and provide the representative with the gathered information.
%MONITOR-3-VARSETFAIL : ROM monitor variable set of [chars] failed.
Explanation The system could not set a ROM Monitor variable. This condition typically occurs when no ROM monitor memory is available to save the variable. The ROM monitor memory is most likely already filled with configuration boot commands.
Recommended Action Enter the show bootvar command and check the output to see if there is anything unusual with the system. Try to reduce the number of configuration boot commands.
MPLS_IPRM
%MPLS_IPRM-3-DB : [chars]
Explanation There is an inconsistency in the information required to request labels from or to process labels received from an IP label distribution module
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MPLS_IPRM-3-DB_PATH : [chars]
Explanation There is an inconsistency in the information about a prefix path required to request labels from or to process labels received from an IP label distribution module
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MPLS_IPRM-3-DB_PNDG_DISC : [chars]
Explanation There is an inconsistency in the information about a temporarily deferred action required to populate MPLS forwarding data structures for a prefix
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MPLS_IPRM-3-DB_TABLE : [chars]
Explanation There is an inconsistency in the information about a (vrf) tableid required to request labels from or to process labels received from an IP label distribution module
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MPLS_IPRM-3-DB_TRANS : [chars]
Explanation There is an inconsistency in the information about an ongoing transaction required to populate MPLS forwarding data structures for a prefix
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MPLS_IPRM-3-INTERNAL : [chars]
Explanation An operation required for proper operation of the IP rewrite manager has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MPLS_IPRM-3-PATH_LABEL_DEL : [chars]
Explanation An attempt to delete MPLS forwarding information for the specified prefix has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MPLS_IPRM-3-PATH_LABEL_GET : [chars]
Explanation An attempt to access MPLS forwarding information for the specified prefix has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MPLS_IPRM-3-PATH_LABEL_UPD : [chars]
Explanation An attempt to update MPLS forwarding information for the specified prefix has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MPLS_IPRM-3-WALK : [chars]
Explanation A request by an IP label distribution module (e.g., LDP, BGP) to walk a CEF table cannot be handled.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
MPLS_TE_HA
%MPLS_TE_HA-3-CF_REGISTER_FAILED : Failed to register with CF
Explanation system may be low on memory
Recommended Action Verify system memory availability. Then deconfigure graceful restart full-mode and configure it again. This will attempt to re-start the RSVP HA process and re-register with CF
%MPLS_TE_HA-3-CLI_ADD_FAILED : Failed to add RSVP HA to CLI
Explanation system may be low on memory
Recommended Action Verify system memory availability. Then deconfigure graceful restart full-mode and configure it again. This will attempt to re-start the RSVP HA process and re-register with CF
%MPLS_TE_HA-3-DB_INIT_FAILED : Database init failed
Explanation system may be low on memory
Recommended Action Verify system memory availability. Then deconfigure graceful restart full-mode and configure it again. This will attempt to re-start the RSVP HA process and re-register with CF
%MPLS_TE_HA-3-ENTRY_MOVE_FAILED : Failed to move a database entry to [chars] tree
Explanation An attempt to move a data entry from one wavl tree to another wavl tree failed
Recommended Action This error should never happen under normal operation and indicates an internal error. Open a ddts
%MPLS_TE_HA-3-ISSU_INIT_FAILED : In Service Software Upgrade (ISSU) Init failed
Explanation system may be low on memory
Recommended Action Verify system memory availability. Then deconfigure graceful restart full-mode and configure it again. This will attempt to re-start the RSVP HA process and re-register with CF
%MPLS_TE_HA-3-ITEM_SIZE_TOO_BIG : Item size ([int]) bigger than default CF buffer ([int]) supported by the platform
Explanation A database entry cannot be sent to the standby because the database entry doesn't fit in a CF maximum size buffer allowed by the platform.
Recommended Action This error indicates a problem with design in handling platform dependent restrictions. Open a ddts
%MPLS_TE_HA-3-MAIN_INIT_FAILED : Main init failed
Explanation system may be low on memory
Recommended Action Verify system memory availability. Then deconfigure graceful restart full-mode and configure it again. This will attempt to re-start the RSVP HA process and re-register with CF
%MPLS_TE_HA-3-MSG_MGR_INIT_FAILED : Message Manager init failed
Explanation system may be low on memory
Recommended Action Verify system memory availability. Then deconfigure graceful restart full-mode and configure it again. This will attempt to re-start the RSVP HA process and re-register with CF
%MPLS_TE_HA-3-PROCESS_CREATE_FAILED : Failed to create RSVP HA process
Explanation system may be low on memory
Recommended Action Verify system memory availability. Then deconfigure graceful restart full-mode and configure it again. This will attempt to re-start the RSVP HA process
%MPLS_TE_HA-3-PROCESS_KILL : Killing RSVP HA process
Explanation system may be low on memory. Failed to create RSVP HA services
Recommended Action No action is required.
%MPLS_TE_HA-3-RF_REGISTER_FAILED : Failed to register with RF
Explanation system may be low on memory
Recommended Action Verify system memory availability. Then deconfigure graceful restart full-mode and configure it again. This will attempt to re-start the RSVP HA process and re-register with CF
%MPLS_TE_HA-3-RF_UNREGISTER_FAILED : Failed to unregister with RF
Explanation RSVP HA client may not have registered with RF
Recommended Action No action is required.
%MPLS_TE_HA-3-SSO_UNSUPPORTED : Attempt to init RSVP HA subsystem when TE SSO not supported
Explanation RSVP TE SSO is included in image that doesn't support SSO
Recommended Action This error indicates a problem with design in. Open a ddts
MPLS_TE_NSR
%MPLS_TE_NSR-3-RESEQUENCE_ERROR : Error occurred during TE NSR resequence
Explanation An unrecoverable error occurred during TE NSR resequence of state
Recommended Action Disable and then reenable TE NSR functionality and open a DDTS
MPLS_TE_PCE
%MPLS_TE_PCE-5-PCE_ERR_RX : PCEP peer [chars] sent PCError message -type: [int], value: [int]
Explanation PCErr message was received from peer
Recommended Action Verify PCEP protocol operation
%MPLS_TE_PCE-5-PCE_STATE : Connection to PCE server:[chars] [chars]
Explanation The connection to PCE server changed state.
Recommended Action If the state change was unexpected check connectivity and state of the PCE server
MTRIE
%MTRIE-4-MTRIECORRUPTLEAF : [IP_address]/[dec] -[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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MTRIE-4-MTRIELEAFOPFAIL : [IP_address]/[dec] -[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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MTRIE-4-MTRIEMISALIGNEDNODEPTR : [hex] -[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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%MTRIE-4-PLACEALLOC : Failed to allocate place holder
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
MSG_FIFO
%MSG_FIFO-2-MSG_FIFO_CREATE : [chars]: Bad parameter to message fifo creaate [chars] = [hex]
Explanation Failed to create message fifo, invalid memory size or other parameter.
Recommended Action LOG_STD_ACTION
MSG_POS_OC3_OC12_SPA
%MSG_POS_OC3_OC12_SPA-3-AUXC2W_INIT : [chars] (slot [dec]; bay [dec]) Device Auxiliary C2W initialization failed.
Explanation Auxiliary C2W bus initialization failed. It indicates a hardware failure.
Recommended Action Change the hardware or copy the error message exactly as it appears, and report it to your technical support representative.
%MSG_POS_OC3_OC12_SPA-3-DS1844_INIT : [chars] (slot [dec]; bay [dec]) Device DS1844 initialization failed.
Explanation DS1844 potentiometer initialization failed. It indicates a hardware failure
Recommended Action Change the hardware or copy the error message exactly as it appears, and report it to your technical support representative.
%MSG_POS_OC3_OC12_SPA-3-FRAMER_CREATE : [chars] (slot [dec]; bay [dec]) Device Framer creation failed.
Explanation Framer device creation failed.
Recommended Action Change the hardware or copy the error message exactly as it appears, and report it to your technical support representative.
%MSG_POS_OC3_OC12_SPA-3-FRAMER_INIT : [chars] (slot [dec]; bay [dec]) Device Framer initialization failed.
Explanation Framer device initialization failed. It indicates a hardware failure.
Recommended Action Change the hardware or copy the error message exactly as it appears, and report it to your technical support representative.
%MSG_POS_OC3_OC12_SPA-3-IOFPGA_CREATE : [chars] (slot [dec]; bay [dec]) Device IOFPGA creation failed.
Explanation IOFPGA Device creation failed.
Recommended Action Change the hardware or copy the error message exactly as it appears, and report it to your technical support representative.
%MSG_POS_OC3_OC12_SPA-3-IOFPGA_INIT : [chars] (slot [dec]; bay [dec]) Device IOFPGA initialization failed.
Explanation IOFPGA Device initialization failed. It indicates FPGA associated PLL lock or interrupt issues. It may also indicate a hardware failure.
Recommended Action Change the hardware or copy the error message exactly as it appears, and report it to your technical support representative.
%MSG_POS_OC3_OC12_SPA-3-MAX1668_INIT : [chars] (slot [dec]; bay [dec]) Device MAX1668 initialization failed.
Explanation MAX1668 temperature sensor initialization failed. It indicates a hardware failure.
Recommended Action Change the hardware or copy the error message exactly as it appears, and report it to your technical support representative.
%MSG_POS_OC3_OC12_SPA-3-RESOURCE_ERROR : [chars] ([hex], [hex], [hex]) [chars]
Explanation Failed to get required interface.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%MSG_POS_OC3_OC12_SPA-3-SMM665_INIT : [chars] (slot [dec]; bay [dec]) Device SMM665 initialization failed.
Explanation SMM665 Summit Controller initialization failed. It indicates a hardware failure.
Recommended Action Change the hardware or copy the error message exactly as it appears, and report it to your technical support representative.
%MSG_POS_OC3_OC12_SPA-3-SPI42_CREATE : [chars] (slot [dec]; bay [dec]) Device SPi42 creation failed.
Explanation SPi4.2 Device creation failed
Recommended Action Change the hardware or copy the error message exactly as it appears, and report it to your technical support representative.
%MSG_POS_OC3_OC12_SPA-3-SPI42_INIT : [chars] (slot [dec]; bay [dec]) Device SPi42 initialization failed.
Explanation SPi42 Device initialization failed. It indicates a hardware failure.
Recommended Action Change the hardware or copy the error message exactly as it appears, and report it to your technical support representative.
%MSG_POS_OC3_OC12_SPA-3-XCVR_ANALYZE : [chars] (slot [dec]; bay [dec]; port [dec]) Tranceiver analyze failed.
Explanation Tranceiver analyze failed
Recommended Action None
%MSG_POS_OC3_OC12_SPA-3-XCVR_RATE_NOTSUPPORTED : [chars] (slot [dec]; bay [dec]) Tranceiver rate not supported on the SPA.
Explanation Tranceiver rate not supported on the SPA.
Recommended Action Remove the tranceiver module and insert a valid module with rate that is supported on the SPA.
MX
%MX-3-BADFEAT : [chars]: [dec]
Explanation Software detected the use of an invalid feature enumeration, which may be the result of incompatible software versions on different system components.
Recommended Action LOG_STD_ACTION
%MX-3-BADMAGIC : [chars]: [hex] in [hex], MSGDEF_LIMIT_MEDIUM
Explanation A data structure inconsistency was detected in a buffer header, perhaps as the result of memory corruption. A buffer has been dropped because of this, resulting in a memory leak and potential system unreliability.
Recommended Action Please report the problem Cisco technical support, along with the text of the error message. If the system becomes unstable, restarting or reloading the affected component should correct the instability.
%MX-3-BADPOOL : [chars]: [int]
Explanation Software detected the use of an invalid pool index, which may be the result of incompatible software versions on different system components.
Recommended Action LOG_STD_ACTION
%MX-3-BADSTART : [chars]: [hex] (current [hex], size [int])
Explanation A software error was detected during an attempt to increase the size of an external memory region.
Recommended Action LOG_STD_ACTION
%MX-3-CARVE : [chars]: size [int] too small
Explanation A software error resulted in an attempt to create buffers in an area of memory that was too small.
Recommended Action LOG_STD_ACTION
%MX-3-INITBUFHDR : [chars]: mgmt memory allocation failure (size [int])
Explanation insufficient mgmt memory provided for initialization of the external memory manager, which will cause features that manage packets in multiple pieces, or that directly export data, not to work properly.
Recommended Action LOG_STD_ACTION
%MX-3-MAXPOOLS : too low
Explanation A source code inconsistency was detected.
Recommended Action Increase the number of pools allowed.
%MX-3-RESIZE : [chars]: non-contiguous resize: orig [hex]/[hex], new [hex]/[hex], MSGDEF_LIMIT_MEDIUM
Explanation A software error was detected during a resize operation on the specified memory region.
Recommended Action LOG_STD_ACTION
%MX-3-SUBRGNINDX : [chars]: Subregion Index allocation failure
Explanation Unable to obtain a sub region index so unable add sw managed memory
Recommended Action LOG_STD_ACTION
%MX-6-NOBUFHDR : [chars]
Explanation An attempt to add buffers within a memory region failed.
Recommended Action LOG_STD_ACTION
%MX-6-NOMEM : [chars] bufhdr allocation failure, MSGDEF_LIMIT_MEDIUM
Explanation An attempt to allocate memory failed. This could cause features that manage packets in multiple pieces, or that directly export data, not to work properly in some cases.
Recommended Action LOG_STD_ACTION
N
NBAR
%NBAR-1-LINKNEXTCORRUPTED : link->next not NULL when allocated. link->next = [chars]
Explanation An attempt was made to get a link from the free bucket which is pointing to another resource. Links within the free bucket should be NULL, therefore this link is corrupted and should not be used
Recommended Action Configure the router with the ip nbar resources to allocate a larger initial pool of resources.
%NBAR-1-LINKPREVCORRUPTED : link->prev not NULL when allocated. link->prev = [chars]
Explanation An attempt was made to get a link from the free bucket which is pointing to another resource. Links within the free bucket should be NULL, therefore this link is corrupted and should not be used
Recommended Action Configure the router with the ip nbar resources to allocate a larger initial pool of resources.
%NBAR-1-MAXMEMORYUSED : Reached maximum amount of memory allocated for stile
Explanation This platform allows NBAR to use a limited amount of memory for classification and that amount has been used up because of high traffic conditions.
Recommended Action Increase amount of memory in router.
%NBAR-1-NODESIZEMISMATCH : Nodes size mismatch between parsing and sending:[chars]
Explanation Failure during the distribution of NBAR graph nodes from the route processor to the linecards. Failure is related to node size changes between parsing and sending phase
Recommended Action Disable nbar protocols
%NBAR-2-HEURISTIC_XDR_FAILED : Failure in the heuristic subsystem of NBAR: [chars]
Explanation Failure during the distribution of NBAR heuristic data structures from the route processor to the linecards.
Recommended Action Disable heuristic protocols
%NBAR-2-NOMEMORY : No memory available for [chars]
Explanation An attempt at memory allocation failed.
Recommended Action Try these actions to remedy the problem: Add memory. Disable some features. Apply filtering to decrease the size of system data structures - the routing table, for example. In general, reduce other system activities to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
%NBAR-2-NOSTATEMEM : Memory for maintaining state used up
Explanation NBAR uses memory to maintain state information about stateful flows. There is a maximum limit on how much memory NBAR can use for this purpose and this limit has been reached.
Recommended Action Increase memory on platform
%NBAR-2-RMINVALIDCONFIG : NBAR resource manager : too many buckets ([dec])
Explanation NBAR was configured such that the internal data structures needed to maintain stateful protocol information were too large.
Recommended Action Configure the router with the ip nbar resources with a smaller max-idle time.
%NBAR-2-RMNORESOURCE : NBAR resources exhausted
Explanation In order to save stateful information on protocols, NBAR must use dynamic resources. These resources have been exhausted.
Recommended Action Configure the router with the ip nbar resources to allocate a larger initial pool of resources. The default number of initial resources is 10000. Also try configuring a shorter max-idle time.
%NBAR-4-STILE_MAX_PD_INTF : NBAR protocol-discovery is enabled on maximum number of interfaces ([dec]) supported by this platform
Explanation This platform allows NBAR to enable protocol-discovery on a limited number of interfaces, and that limit has reached.
Recommended Action Need to disable protocol-discovery from an interface, to enable protocol-discovery on any new interface.
%NBAR-6-INACTIVE_PROTOCOL_PACK : [chars] is successfully loaded as an Inactive Protocol Pack
Explanation The NBAR Engine Version of the protocol pack is either less than the Minimum Backward Compatible Engine Version, or is greater than the NBAR Engine Version of the image, and therefore, it will be loaded as an Inactive Protocol Pack
Recommended Action Since the protocol pack is loaded as an Inactive Protocol Pack, signatures in this pack will not be available for any classification. To use the protocol pack, upgrade/downgrade to an image which is compatible with the NBAR Engine Version of the protocol pack.
%NBAR-6-PDL_ERRORS : PDL parsing error: [chars]
Explanation Unable to parse PDL, issue in syntax
Recommended Action PL need to fine tune or modify PDL.
%NBAR-6-PORT_MAP_DEPRECATION : [chars] command will be deprecated soon. In future it will not be necessary to configure port-map on a Protocol to create a new Custom protocol onto the same well known port.
Explanation In future releases it will not be necessary to configure port-map on a Protocol to create a new Custom protocol onto the same well known port. Port-map command will be deprecated in future releases.
Recommended Action No action required.
NCS4200IM
%NCS4200IM-3-DIFF_IM_INSERTED : [chars] -[chars] in bay [dec]
Explanation A different IM type has been inserted in the bay which previously had another IM type. If the interfaces were set to default before swap, the IM will boot up fine. If not, IM will goto Out-of-service state. Kindly insert the previous IM type, use hw-module subslot 0/x default and then proceed with the IM swap. If not, might need to reload the box for recovery
Recommended Action None
%NCS4200IM-3-INCOMPATIBLE : [chars]-[dec]
Explanation P1D and onwards, Cu IM.... is not backward compatible with P1A/P1B/P1C Cu IM, use the same build of Cu IM or reload the router to use the new build.
Recommended Action None
%NCS4200IM-3-INVALID_COMBINATION : [chars] is not allowed in bay [dec], can be supported only in bay(s) [chars]
Explanation The inserted IM is not supported in the specified subslot given the combination of existing IMs in the chassis.
Recommended Action None
%NCS4200IM-3-UNSUPPORTED : This Interface Module is not supported in subslot [dec]
Explanation The inserted IM is not supported in the specified subslot. Kindly check the supported slots for the IM type.
Recommended Action None
%NCS4200IM-3-UNSUPPORTED_PLATFORM : This Interface Module is not supported in [chars] platform
Explanation The inserted IM is not supported in the specified platform
Recommended Action None
NCS4200INTF
%NCS4200INTF-3-UNSUPPORTED : Interface [chars] is not supported in subslot [dec] by the [chars] module
Explanation The Interface specified in the error message is not supported in the specified Subslot by the version of the operating system currently running on the system.
Recommended Action None
NCS4200_RP_ATM_SPA
%NCS4200_RP_ATM_SPA-3-ATM_PER_SPA_MAX_VC_LIMIT_REACHED : total active atm vc per ATM SPA reached limitation of [dec]
Explanation total number of active atm vc per ATM SPA has reached max limit
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
NETCLK
%NETCLK-4-NETCLK_CMD_FAIL : NULL
Explanation This message indicates that a network clock command from RP to IOS-SR or SPAs has failed
Recommended Action The message can be ignored if the carrier card was reloaded or powered down. Otherwise, LOG_STD_SH_CMD_ACTION(show logging and show network-clocks)
%NETCLK-5-NETCLK_CHANGE : Network clock source transitioned from priority [dec] [chars] to priority [dec] [chars]
Explanation This notice indicates a change in the clock source.
Recommended Action No action required.
%NETCLK-5-NETCLK_MODE_CHANGE : Network clock source not available. The network clock has changed to [chars]
Explanation None
Recommended Action No action required
%NETCLK-5-NETCLK_PHASE_LOST : Network clock source not available. Phase-lost on clock priority [dec] [chars]
Explanation None
Recommended Action No action required
NIM_XXD
%NIM_XXD-3-DISK_ERROR : Error detected on disk [dec] in module [chars] in subslot [dec]/[dec]. [chars].
Explanation Disk error detected in the SPA (NIM-SSD/NIM-HDD). Refer to comment for details.
Recommended Action Back-up any data and replace the disk.
%NIM_XXD-3-DISK_REMOVAL : One or more disks in SPA ([chars]) in subslot [dec]/[dec] can not be detected. Please power down this SPA and insert disk(s).
Explanation Disks have been removed from SPA
Recommended Action Power down the SPA, insert disks and power up the SPA.
%NIM_XXD-5-DISK_MONITOR : Disk [dec] in module [chars] in subslot [dec]/[dec] is detected but monitoring is not available.
Explanation Monitoring of disk in SPA (NIM-SSD/NIM-HDD) is unavailable.
Recommended Action Add a database file with monitoring information for this disk model and manufacturer.
O
OOM
%OOM-0-NO_MEMORY_RESET : The system is completely out of available memory. The board will be reset.
Explanation The system has exhausted all available memory and the hardware component will be reset.
Recommended Action Review other messages related to low memory states and see if those messages contain any information about an issue that can be addressed. If this problem persists, copy all the output from the console as well as the output of show tech-support, and provide the gathered information to your Cisco technical support representative.
%OOM-3-NO_MEMORY_AVAIL : The system is very low on available memory. Operations will begin to fail.
Explanation The system has exhausted all available memory. It is not possible to continue stable operation.
Recommended Action The system has exhausted all available memory and stable operation is no longer possible.
P
PAD
%PAD-2-INTR : [chars] called at interrupt level [hex]
Explanation An internal software error occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears and report it to your technical support representative.
%PAD-2-PUTSETUP : Tty%t, buffer already setup
Explanation An internal software error occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears and report it to your technical support representative.
%PAD-3-GETLINE : Tty%t, bad return code [dec] from x3_getline()
Explanation An internal software error occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears and report it to your technical support representative.
PAM_UPDB
%PAM_UPDB-3-NOENVIRONMENT_SET : Error setting user in application environment: [chars]
Explanation The user has succesfully authenticated, but the user information could not be saved to the application environment. The user session will not proceed.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%PAM_UPDB-3-NOPROMPT_READ : Error reading [chars] prompt: [chars]
Explanation The authentication module was unable to read the specified prompt file. The default prompt will be used.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
PA_PKT_PROXY
%PA_PKT_PROXY-2-PROXY_IPC_INIT_FAILED : [dec]
Explanation Could not initialize IPC handler.
Recommended Action LOG_STD_ACTION
%PA_PKT_PROXY-3-PROXY_IPC_INVALID_MSG : [dec]:[dec] len [dec] flags [hex] source [dec]
Explanation Invalid length for IPC message.
Recommended Action LOG_STD_ACTION
%PA_PKT_PROXY-3-PROXY_IPC_PBUF_EXTEND_FAILED : [dec]
Explanation Extending of packet buffer header memory failed.
Recommended Action LOG_STD_ACTION
%PA_PKT_PROXY-3-PROXY_IPC_PKT_DRAM_EXTEND_FAILED : [dec]
Explanation Extending of extended packet memory failed.
Recommended Action LOG_STD_ACTION
%PA_PKT_PROXY-4-PROXY_IPC_UNKNOWN_SUBTYPE : [dec]
Explanation Unknown IPC message detected.
Recommended Action LOG_STD_ACTION
PATHMGR
%PATHMGR-2-IPC_INIT : IPC message handler registration failure, rc [int]
Explanation Registering an IPC message handler for the PATHMGR feature failed. This will cause the feature to not function.
Recommended Action This is normally a software issue. The consequences are that the PATHMGR feature will not function. LOG_STD_ACTION
%PATHMGR-3-IPC_NORES : No space for the IPC reply, size [int]
Explanation For a request from upper PATHMGR 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
%PATHMGR-3-IPC_OPEN_REPLY : IPC Open Reply failed, request [int]
Explanation For a request from upper PATHMGR 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
PBUF
%PBUF-3-PBUF_MEM_INIT_FAILED : [chars]
Explanation Failure occurred when attempting to create memory resource
Recommended Action LOG_STD_ACTION
%PBUF-3-PBUF_MEM_REQ_FAILED :
Explanation Failure occurred when attempting to request extended packet memory.
Recommended Action LOG_STD_ACTION
%PBUF-3-PBUF_PKT_MEM_CORRUPT : [hex] [hex]
Explanation Memory corruption detected while freeing extended packet memory
Recommended Action LOG_STD_ACTION
%PBUF-3-PBUF_SH_DRAM_CVT_FAIL : [chars]
Explanation An attempt to convert a shared DRAM buffer to non-shared failed.
Recommended Action LOG_STD_ACTION
PCMCIAFS
%PCMCIAFS-3-RESETERR : PCMCIA disk [dec] [chars]
Explanation PCMCIA disk could not be reset while the system is initiated reload. This will cause a transient disk error, disk timeout error, when the ROMMON initialization code tries to reads the DIB. This is a transient error and the system will be able to access the disk and continue normal operation.
Recommended Action No action is required.
%PCMCIAFS-4-DFS_FSCK_ERR : Error while running fsck on the file [chars].
Explanation Fsck is running in a loop while walking through the cluster chain of a file and has aborted.
Recommended Action Report this occurrence to Engineering. Use Topic to search for a similar DDTS. If you find none, write a DDTS for this problem.
%PCMCIAFS-5-DFS_CLOSE_ERR : Error during close of the file [chars]. [chars]
Explanation An error occured during a file close operation.
Recommended Action Enter the fsck filesystem prefix: command to check and attempt to repair the disk. If this does not fix the problem, format the disk.
%PCMCIAFS-5-DIBERR : [dec] [chars]
Explanation The system cannot boot a image from the PCMCIA Flash disk because the Device Information Block is different. The Flash disk can be read by the router, but will require formatting by the router before an image can be booted from it.
Recommended Action Follow any instructions provided in the error message. Before storing a image in the Flash disk and trying to boot from this device, enter the format command to format the flash disk from the router. Then copy the desired image to the Flash disk and then boot from this device.
PCM_TRACER
%PCM_TRACER-3-PCMT_CHANNEL_TYPE_NOT_SUPPORTED : The channel/group type of ds0 [int] is not supported by PCM Tracer.
Explanation Can't execute this command on the ds0 number specified.
Recommended Action Refer to the user guide for the channel/group type PCM Tracer supports.
%PCM_TRACER-3-PCMT_NO_ACTIVE_CALL : No active calls to trace.
Explanation PCM Tracer can be applied only on active calls.
Recommended Action Make sure there is an active call before starting the PCM Tracer.
%PCM_TRACER-3-PCMT_NO_CAPTURE_DURATION : No capture duration configured.
Explanation Capture duration is required for starting the PCM Tracer.
Recommended Action Configure capture duration before starting the PCM Tracer.
%PCM_TRACER-3-PCMT_NO_CAPTURE_TDM : No capture-tdm configured under profile [int].
Explanation Capture-tdm is required for starting the PCM Tracer.
Recommended Action Configure capture-tdm before starting the PCM Tracer.
%PCM_TRACER-3-PCMT_NO_DEST : No PCM Tracer capture destination configured.
Explanation Capture destination is required for starting the PCM Tracer.
Recommended Action Configure capture destination before starting the PCM Tracer.
%PCM_TRACER-3-PCMT_NO_PROFILE : No PCM Tracer profile configured.
Explanation Capture profile is required for starting the PCM Tracer.
Recommended Action Configure capture profile before starting the PCM Tracer.
%PCM_TRACER-3-PCMT_NOT_SUPPORTED : PCM Tracer is not supported on slot [int].
Explanation Can't execute this command on the slot number specified.
Recommended Action Refer to the user guide for which slot PCM Tracer is supported on.
%PCM_TRACER-3-PCMT_RUNNING : A PCM Tracer session is currently running.
Explanation Can't execute this command since there is a PCM Tracer running now.
Recommended Action Make sure there is no PCM Tracer sesssion running before execute this command.
%PCM_TRACER-6-PCMT_START : Starting PCM Trace on channel under profile [dec]
Explanation None
Recommended Action None
%PCM_TRACER-6-PCMT_STOP : Stopping PCM Trace on channel under profile [dec]
Explanation None
Recommended Action None
%PCM_TRACER-6-PCMT_STOP_FAIL : Fail to Stop PCM Trace on channel under profile [dec]
Explanation None
Recommended Action None
%PCM_TRACER-6-PCMT_STOP_RUNNING : Stop PCM capture
Explanation None
Recommended Action None
PERF_MON
%PERF_MON-3-CHUNKCREATE : Failed to chunk create memory for [chars]
Explanation Unable to chunk create memory chunk
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_MON-3-CHUNKDESTROY : Failed to chunk destroy memory for [chars]
Explanation Unable to chunk destroy memory chunk
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_MON-3-CHUNKMALLOC : Failed to malloc chunk memory for [chars]
Explanation Unable to malloc memory chunk, malloc failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_MON-3-DEFRECCREATE : Creation of default-record [chars] failed -reason [chars]
Explanation Failed to create system defined default flow-records
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_MON-3-LIST : Failed to [chars] list [chars]
Explanation A list operation failed. This could be caused by memory corruption
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_MON-3-MEM : Memory [chars] failed -[chars]
Explanation Memory creation failed during the initialization
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_MON-3-PARSER : [chars]
Explanation Parser failure. This could due to invalid command or corrupted csb
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_MON-3-RECSETKEY : Adding key fields for default-record [chars] failed -reason [chars]
Explanation Failed to add key fields for defined default flow-records
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_MON-3-RECSETNONKEY : Adding non-key fieds for [chars] default-record failed -reason [chars]
Explanation Failed to add non-key fields for defined default flow-records
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_MON-3-RECSETPROP : Setting property for [chars] default-record failed -reason [chars]
Explanation Failed to set properties for system defined default flow-records
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
PERF_MON_REACT
%PERF_MON_REACT-0-EMERGCLEAR : TCA CLEAR. Detailed info: [chars][chars][chars][chars][chars]
Explanation A threshold crossing alarm is cleared. The alarm severity is EMERGENT.
Recommended Action No action is required.
%PERF_MON_REACT-0-EMERGSET : TCA RAISE. Detailed info: [chars][chars][chars][chars][chars]
Explanation A threshold crossing alarm is raised. The alarm severity is EMERGENT. system is unusable.
Recommended Action No action is required.
%PERF_MON_REACT-1-ALERTCLEAR : TCA CLEAR. Detailed info: [chars][chars][chars][chars][chars]
Explanation A threshold crossing alarm is cleared. The alarm severity is ALERT.
Recommended Action No action is required.
%PERF_MON_REACT-1-ALERTSET : TCA RAISE. Detailed info: [chars][chars][chars][chars][chars]
Explanation A threshold crossing alarm is raised. The alarm severity is ALERT.
Recommended Action No action is required.
%PERF_MON_REACT-2-CRITCLEAR : TCA CLEAR. Detailed info: [chars][chars][chars][chars][chars]
Explanation A threshold crossing alarm is cleared. The alarm severity is CRITICAL.
Recommended Action No action is required.
%PERF_MON_REACT-2-CRITSET : TCA RAISE. Detailed info: [chars][chars][chars][chars][chars]
Explanation A threshold crossing alarm is raised. The alarm severity is CRITICAL.
Recommended Action No action is required.
%PERF_MON_REACT-2-INFOCLEAR : TCA CLEAR. Detailed info: [chars][chars][chars][chars][chars]
Explanation A threshold crossing alarm is cleared. The alarm severity is INFO.
Recommended Action No action is required.
%PERF_MON_REACT-2-INFOSET : TCA RAISE. Detailed info: [chars][chars][chars][chars][chars]
Explanation A threshold crossing alarm is raised. The alarm severity is INFO.
Recommended Action No action is required.
%PERF_MON_REACT-3-ERRCLEAR : TCA CLEAR. Detailed info: [chars][chars][chars][chars][chars]
Explanation A threshold crossing alarm is cleared. The alarm severity is ERROR
Recommended Action No action is required.
%PERF_MON_REACT-3-ERRSET : TCA RAISE. Detailed info: [chars][chars][chars][chars][chars]
Explanation A threshold crossing alarm is raised. The alarm severity is ERROR
Recommended Action No action is required.
%PERF_MON_REACT-0-EMERGCLEAR : TCA CLEAR. Detailed info: [chars][chars][chars][chars][chars]
Explanation A threshold crossing alarm is cleared. The alarm severity is EMERGENT.
Recommended Action No action is required.
%PERF_MON_REACT-0-EMERGSET : TCA RAISE. Detailed info: [chars][chars][chars][chars][chars]
Explanation A threshold crossing alarm is raised. The alarm severity is EMERGENT. system is unusable.
Recommended Action No action is required.
%PERF_MON_REACT-1-ALERTCLEAR : TCA CLEAR. Detailed info: [chars][chars][chars][chars][chars]
Explanation A threshold crossing alarm is cleared. The alarm severity is ALERT.
Recommended Action No action is required.
%PERF_MON_REACT-1-ALERTSET : TCA RAISE. Detailed info: [chars][chars][chars][chars][chars]
Explanation A threshold crossing alarm is raised. The alarm severity is ALERT.
Recommended Action No action is required.
%PERF_MON_REACT-2-CRITCLEAR : TCA CLEAR. Detailed info: [chars][chars][chars][chars][chars]
Explanation A threshold crossing alarm is cleared. The alarm severity is CRITICAL.
Recommended Action No action is required.
%PERF_MON_REACT-2-CRITSET : TCA RAISE. Detailed info: [chars][chars][chars][chars][chars]
Explanation A threshold crossing alarm is raised. The alarm severity is CRITICAL.
Recommended Action No action is required.
%PERF_MON_REACT-2-INFOCLEAR : TCA CLEAR. Detailed info: [chars][chars][chars][chars][chars]
Explanation A threshold crossing alarm is cleared. The alarm severity is INFO.
Recommended Action No action is required.
%PERF_MON_REACT-2-INFOSET : TCA RAISE. Detailed info: [chars][chars][chars][chars][chars]
Explanation A threshold crossing alarm is raised. The alarm severity is INFO.
Recommended Action No action is required.
%PERF_MON_REACT-3-ERRCLEAR : TCA CLEAR. Detailed info: [chars][chars][chars][chars][chars]
Explanation A threshold crossing alarm is cleared. The alarm severity is ERROR
Recommended Action No action is required.
%PERF_MON_REACT-3-ERRSET : TCA RAISE. Detailed info: [chars][chars][chars][chars][chars]
Explanation A threshold crossing alarm is raised. The alarm severity is ERROR
Recommended Action No action is required.
PERF_TRAFFIC_INFRA
%PERF_TRAFFIC_INFRA-3-CHUNKCREATE : Failed to chunk create memory for [chars]
Explanation Unable to chunk create memory chunk
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-CHUNKDESTROY : Failed to chunk destroy memory for [chars]
Explanation Unable to chunk destroy memory chunk
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-CHUNK_INIT : Chunk is not initialized -[chars]
Explanation Chunk memory is not created or failed to be created
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-CHUNKMALLOC : Failed to malloc chunk memory for [chars]
Explanation Unable to malloc memory chunk, malloc failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-CONV_FAILURE : Conversion failed -[chars]
Explanation Conversion from one format to another has failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-DEFRECCREATE : Creation of default-record [chars] failed -reason [chars]
Explanation Failed to create system defined default flow-records
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-EXP_ATTR : Failed to set flow attribute for exporter -[chars]
Explanation An error occured when setting flow attribute use to transform match and collect metrics to export message
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-FDEF_NOTIFY : Failed to register PD flow definition [chars]
Explanation The flow def received from ME or PD is NULL
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-FDEF_TEMP : Invalid flow definition template -[chars]
Explanation The template was not initialized during system initialization
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-FIELDENA : Enable fnf field [chars] failed -[chars]
Explanation Failed to enable a field for use with a config
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-FLOW_EXCEED : The number of flows has exceeded 95 percent of the configured maximum flow. [chars]
Explanation This is warning message if the flow size exceeds the maximum value
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-FLOW_NONEXCEED : The number of flows is below 85 percent of the configured maximum flow. [chars]
Explanation This is info message if the flow size falls below the maximum value
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-FNFPARSERENA : Enable flow monitor parser failed -[chars]
Explanation Failed to enable performance monitor typed monitor
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-INV_ARG : The argument is not valid -[chars]
Explanation An internal error occurred. The argument for an internal API is not valid
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-INVCMD : Invalid cmd type [dec] to [chars]
Explanation This is an internal error, the command type is invalid
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-INV_COMMON_MONITOR : The common monitor ptr is invalid
Explanation An internal error occurred. The common monitor ptr saved in the performance-monitor monitor is NULL
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-INVCRIT : Invalid react criteria [dec] to [chars]
Explanation This is an internal error, the saved react criteria is corrupted
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-INVFIELDTYPE : Enable fnf field [dec] failed -invalid field type
Explanation Failed to enable a field for use with a config
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-INVMODE : Invalid performance-monitor configuration mode
Explanation This is an internal error, the configuration sub mode is invalid
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-INVMONITOR : The flow monitor pointer is invalid
Explanation An internal error occurred. The performance-monitor monitor pointer saved in the common monitor is NULL
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-INV_MONITOR_TYPE : The monitor type [dec] is invalid
Explanation An internal error occurred. The monitor type is out of the range
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-INV_POLICY_MAP : The retrieved policy map is invalide -[chars]
Explanation An internal error occurred. The policy map saved in csb is invalid
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-INV_REACT : react is not valid -[chars]
Explanation This is an internal error, the saved react info is corrupted
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-INV_TARGET : A target object does not exist -[chars]
Explanation An internal error occurred. Try to access a null target obj
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-MEMLEAK : Memory leak detected -[chars]
Explanation A memory leak is detected during media-mon memory handling
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-MMONOBJDUP : A mmon_obj already exists for policy [chars] class [chars]
Explanation A mmon obj already exists in the MMON DB under the same policy and class for CLASS_ADD
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-MMONOBJINV : A mmon_obj does not exist for policy [chars] class [chars]
Explanation Unable to find an existing mmon obj for event CLASS_REMOVE and CLASS_MODIFY
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-MONITOR_CREATE : Failed to create Monitor at Metering layer. Error -[chars]
Explanation Failed to create monitor at Metering layer for this policy. The error code provides the reason for failure. No statistics will be collected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-MONITOR_DELETE : Failed to delete Monitor at Metering layer. Error -[chars]
Explanation Failed to delete monitor at Metering layer for this policy. The error code provides the reason for failure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-MONITOR_SYNC : Out of sync -[chars]
Explanation This is an internal error, the reference count in flow monitor reached negative
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-NOPARENTMMONOBJ : Internal error, target has no parent mmon object
Explanation None valid pointer to mmon obj found in tgt obj for CLASS_REMOVE
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-NULLFLOW : A flow does not exist
Explanation An internal error occurred. Try to access a null flow
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-NULLHIST : A history bucket does not exist
Explanation An internal error occurred. Try to access a null history
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-PROC_MSG : Failed to process received record -[chars]
Explanation Failure during the process of handling the received fnf record
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-RECSETKEY : Adding key fields for default-record [chars] failed -reason [chars]
Explanation Failed to add key fields for defined default flow-records
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-RECSETNONKEY : Adding non-key fieds for [chars] default-record failed -reason [chars]
Explanation Failed to add non-key fields for defined default flow-records
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-RECSETPROP : Setting property for [chars] default-record failed -reason [chars]
Explanation Failed to set properties for system defined default flow-records
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-RESETMODE : Failed to reset csb vars
Explanation Reset of the csb vars failed due to lack of memory
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-SIB_LINK : sib member [int] with [int], error [chars]
Explanation Failed to link two sibling members in the MMON PD
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-SIB_UNLINK : sib member [int] from [int], error [chars]
Explanation Failed to unlink two sibling members in the MMON PD
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-CHUNKCREATE : Failed to chunk create memory for [chars]
Explanation Unable to chunk create memory chunk
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-CHUNKDESTROY : Failed to chunk destroy memory for [chars]
Explanation Unable to chunk destroy memory chunk
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-CHUNK_INIT : Chunk is not initialized -[chars]
Explanation Chunk memory is not created or failed to be created
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-CHUNKMALLOC : Failed to malloc chunk memory for [chars]
Explanation Unable to malloc memory chunk, malloc failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-CONV_FAILURE : Conversion failed -[chars]
Explanation Conversion from one format to another has failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-DEFRECCREATE : Creation of default-record [chars] failed -reason [chars]
Explanation Failed to create system defined default flow-records
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-EXP_ATTR : Failed to set flow attribute for exporter -[chars]
Explanation An error occured when setting flow attribute use to transform match and collect metrics to export message
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-FDEF_NOTIFY : Failed to register PD flow definition [chars]
Explanation The flow def received from ME or PD is NULL
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-FDEF_TEMP : Invalid flow definition template -[chars]
Explanation The template was not initialized during system initialization
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-FIELDENA : Enable fnf field [chars] failed -[chars]
Explanation Failed to enable a field for use with a config
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-FLOW_EXCEED : The number of flows has exceeded 95 percent of the configured maximum flow. [chars]
Explanation This is warning message if the flow size exceeds the maximum value
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-FLOW_NONEXCEED : The number of flows is below 85 percent of the configured maximum flow. [chars]
Explanation This is info message if the flow size falls below the maximum value
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-FNFPARSERENA : Enable flow monitor parser failed -[chars]
Explanation Failed to enable performance monitor typed monitor
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-INV_ARG : The argument is not valid -[chars]
Explanation An internal error occurred. The argument for an internal API is not valid
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-INVCMD : Invalid cmd type [dec] to [chars]
Explanation This is an internal error, the command type is invalid
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-INV_COMMON_MONITOR : The common monitor ptr is invalid
Explanation An internal error occurred. The common monitor ptr saved in the performance-monitor monitor is NULL
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-INVCRIT : Invalid react criteria [dec] to [chars]
Explanation This is an internal error, the saved react criteria is corrupted
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-INVFIELDTYPE : Enable fnf field [dec] failed -invalid field type
Explanation Failed to enable a field for use with a config
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-INVMODE : Invalid performance-monitor configuration mode
Explanation This is an internal error, the configuration sub mode is invalid
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-INVMONITOR : The flow monitor pointer is invalid
Explanation An internal error occurred. The performance-monitor monitor pointer saved in the common monitor is NULL
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-INV_MONITOR_TYPE : The monitor type [dec] is invalid
Explanation An internal error occurred. The monitor type is out of the range
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-INV_POLICY_MAP : The retrieved policy map is invalide -[chars]
Explanation An internal error occurred. The policy map saved in csb is invalid
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-INV_REACT : react is not valid -[chars]
Explanation This is an internal error, the saved react info is corrupted
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-INV_TARGET : A target object does not exist -[chars]
Explanation An internal error occurred. Try to access a null target obj
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-MEMLEAK : Memory leak detected -[chars]
Explanation A memory leak is detected during media-mon memory handling
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-MMONOBJDUP : A mmon_obj already exists for policy [chars] class [chars]
Explanation A mmon obj already exists in the MMON DB under the same policy and class for CLASS_ADD
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-MMONOBJINV : A mmon_obj does not exist for policy [chars] class [chars]
Explanation Unable to find an existing mmon obj for event CLASS_REMOVE and CLASS_MODIFY
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-MONITOR_CREATE : Failed to create Monitor at Metering layer. Error -[chars]
Explanation Failed to create monitor at Metering layer for this policy. The error code provides the reason for failure. No statistics will be collected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-MONITOR_DELETE : Failed to delete Monitor at Metering layer. Error -[chars]
Explanation Failed to delete monitor at Metering layer for this policy. The error code provides the reason for failure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-MONITOR_SYNC : Out of sync -[chars]
Explanation This is an internal error, the reference count in flow monitor reached negative
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-NOPARENTMMONOBJ : Internal error, target has no parent mmon object
Explanation None valid pointer to mmon obj found in tgt obj for CLASS_REMOVE
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-NULLFLOW : A flow does not exist
Explanation An internal error occurred. Try to access a null flow
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-NULLHIST : A history bucket does not exist
Explanation An internal error occurred. Try to access a null history
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-PROC_MSG : Failed to process received record -[chars]
Explanation Failure during the process of handling the received fnf record
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-RECSETKEY : Adding key fields for default-record [chars] failed -reason [chars]
Explanation Failed to add key fields for defined default flow-records
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-RECSETNONKEY : Adding non-key fieds for [chars] default-record failed -reason [chars]
Explanation Failed to add non-key fields for defined default flow-records
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-RECSETPROP : Setting property for [chars] default-record failed -reason [chars]
Explanation Failed to set properties for system defined default flow-records
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-RESETMODE : Failed to reset csb vars
Explanation Reset of the csb vars failed due to lack of memory
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-SIB_LINK : sib member [int] with [int], error [chars]
Explanation Failed to link two sibling members in the MMON PD
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PERF_TRAFFIC_INFRA-3-SIB_UNLINK : sib member [int] from [int], error [chars]
Explanation Failed to unlink two sibling members in the MMON PD
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
PERF_TRAFFIC_REACT
%PERF_TRAFFIC_REACT-0-EMERGCLEAR : TCA CLEAR. Detailed info: [chars][chars][chars][chars][chars]
Explanation A threshold crossing alarm is cleared. The alarm severity is EMERGENT.
Recommended Action No action is required.
%PERF_TRAFFIC_REACT-0-EMERGSET : TCA RAISE. Detailed info: [chars][chars][chars][chars][chars]
Explanation A threshold crossing alarm is raised. The alarm severity is EMERGENT. system is unusable.
Recommended Action No action is required.
%PERF_TRAFFIC_REACT-1-ALERTCLEAR : TCA CLEAR. Detailed info: [chars][chars][chars][chars][chars]
Explanation A threshold crossing alarm is cleared. The alarm severity is ALERT.
Recommended Action No action is required.
%PERF_TRAFFIC_REACT-1-ALERTSET : TCA RAISE. Detailed info: [chars][chars][chars][chars][chars]
Explanation A threshold crossing alarm is raised. The alarm severity is ALERT.
Recommended Action No action is required.
%PERF_TRAFFIC_REACT-2-CRITCLEAR : TCA CLEAR. Detailed info: [chars][chars][chars][chars][chars]
Explanation A threshold crossing alarm is cleared. The alarm severity is CRITICAL.
Recommended Action No action is required.
%PERF_TRAFFIC_REACT-2-CRITSET : TCA RAISE. Detailed info: [chars][chars][chars][chars][chars]
Explanation A threshold crossing alarm is raised. The alarm severity is CRITICAL.
Recommended Action No action is required.
%PERF_TRAFFIC_REACT-2-INFOCLEAR : TCA CLEAR. Detailed info: [chars][chars][chars][chars][chars]
Explanation A threshold crossing alarm is cleared. The alarm severity is INFO.
Recommended Action No action is required.
%PERF_TRAFFIC_REACT-2-INFOSET : TCA RAISE. Detailed info: [chars][chars][chars][chars][chars]
Explanation A threshold crossing alarm is raised. The alarm severity is INFO.
Recommended Action No action is required.
%PERF_TRAFFIC_REACT-3-ERRCLEAR : TCA CLEAR. Detailed info: [chars][chars][chars][chars][chars]
Explanation A threshold crossing alarm is cleared. The alarm severity is ERROR
Recommended Action No action is required.
%PERF_TRAFFIC_REACT-3-ERRSET : TCA RAISE. Detailed info: [chars][chars][chars][chars][chars]
Explanation A threshold crossing alarm is raised. The alarm severity is ERROR
Recommended Action No action is required.
%PERF_TRAFFIC_REACT-0-EMERGCLEAR : TCA CLEAR. Detailed info: [chars][chars][chars][chars][chars]
Explanation A threshold crossing alarm is cleared. The alarm severity is EMERGENT.
Recommended Action No action is required.
%PERF_TRAFFIC_REACT-0-EMERGSET : TCA RAISE. Detailed info: [chars][chars][chars][chars][chars]
Explanation A threshold crossing alarm is raised. The alarm severity is EMERGENT. system is unusable.
Recommended Action No action is required.
%PERF_TRAFFIC_REACT-1-ALERTCLEAR : TCA CLEAR. Detailed info: [chars][chars][chars][chars][chars]
Explanation A threshold crossing alarm is cleared. The alarm severity is ALERT.
Recommended Action No action is required.
%PERF_TRAFFIC_REACT-1-ALERTSET : TCA RAISE. Detailed info: [chars][chars][chars][chars][chars]
Explanation A threshold crossing alarm is raised. The alarm severity is ALERT.
Recommended Action No action is required.
%PERF_TRAFFIC_REACT-2-CRITCLEAR : TCA CLEAR. Detailed info: [chars][chars][chars][chars][chars]
Explanation A threshold crossing alarm is cleared. The alarm severity is CRITICAL.
Recommended Action No action is required.
%PERF_TRAFFIC_REACT-2-CRITSET : TCA RAISE. Detailed info: [chars][chars][chars][chars][chars]
Explanation A threshold crossing alarm is raised. The alarm severity is CRITICAL.
Recommended Action No action is required.
%PERF_TRAFFIC_REACT-2-INFOCLEAR : TCA CLEAR. Detailed info: [chars][chars][chars][chars][chars]
Explanation A threshold crossing alarm is cleared. The alarm severity is INFO.
Recommended Action No action is required.
%PERF_TRAFFIC_REACT-2-INFOSET : TCA RAISE. Detailed info: [chars][chars][chars][chars][chars]
Explanation A threshold crossing alarm is raised. The alarm severity is INFO.
Recommended Action No action is required.
%PERF_TRAFFIC_REACT-3-ERRCLEAR : TCA CLEAR. Detailed info: [chars][chars][chars][chars][chars]
Explanation A threshold crossing alarm is cleared. The alarm severity is ERROR
Recommended Action No action is required.
%PERF_TRAFFIC_REACT-3-ERRSET : TCA RAISE. Detailed info: [chars][chars][chars][chars][chars]
Explanation A threshold crossing alarm is raised. The alarm severity is ERROR
Recommended Action No action is required.
PKI
%PKI-1-CERT_EXPIRY_ALERT : [chars] Certificate belonging to trustpoint [chars] will expire in [int] Days [int] hours [int] mins [int] secs. Issuer-name [chars] Subject-name [chars] Serial-number [chars] Auto-Renewal: [chars]
Explanation Alert to indicate that certificate will expire in less than one week.
Recommended Action If auto-enrol feature is not configured, re-enrol the certificate manually. Else, check if any issues with auto-enrol.
%PKI-3-AUTOCERTERR : Auto Certificate (re)enrollment failed. Cannot retry
Explanation Automatic certificate re-enrollment failed. The router clock my not be set correctly. If the router has a certificate it may be expired.
Recommended Action Check router clock is set correctly Make sure the router's cert has not expired
%PKI-3-CERTIFICATE_INVALID : Certificate chain validation has failed.
Explanation The certificate is not valid
Recommended Action Check the system clock to see if its set correctly
%PKI-3-CERTIFICATE_INVALID_EXPIRED : Certificate chain validation has failed. The certificate (SN: [chars]) has expired. Validity period ended on [chars]
Explanation The certificate validity period indicates that this certificate has expired
Recommended Action Check the system clock to see if its set correctly
%PKI-3-CERTIFICATE_INVALID_NOT_YET_VALID : Certificate chain validation has failed. The certificate (SN: [chars]) is not yet valid Validity period starts on [chars]
Explanation The certificate validity period indicates that this certificate is not yet valid
Recommended Action Check the system clock to see if its set correctly
%PKI-3-CERTIFICATE_INVALID_UNAUTHORIZED : Certificate chain validation has failed. Unauthorized
Explanation The certificate is valid but not authorized
Recommended Action Check the system clock to see if its set correctly
%PKI-3-CERTIFICATE_REVOKED : Certificate chain validation has failed. The certificate (SN: [chars]) is revoked
Explanation The certificate has been revoked by the CA administrator.
Recommended Action Check the status, contact the CA administrator
%PKI-3-CERTPENDERR : Failed to receive pending certificate during enrollment
Explanation The router's cert remains in a pending state after the maximum number of retries to enroll.
Recommended Action Contact the CA administrator. Then retry the enrollment.
%PKI-3-CERTRETFAIL : Certificate enrollment failed.
Explanation Certificate enrollment transaction failed due to internal error.
Recommended Action Contact CE.
%PKI-3-CS_CRIT_STORAGE : Critical certificate server storage, [chars], is inaccessible, server disabled.
Explanation Critical certificate server storage is inaccessible, server disabled.
Recommended Action Make storage accessible, or re-configure the storage location
%PKI-3-GETCARACERT : Failed to receive RA/CA certificates.
Explanation Encountered failure when parsing and processing CA/RA certificates
Recommended Action Check the status, contact the CA administrator
%PKI-3-INVALIDCACERT : Failed to process CA certificate.
Explanation Failed to process the ca certificate received from ca server.
Recommended Action Use parser command cr ca auth and try again.
%PKI-3-INVALID_INPUT : The input to the parser command is not correct
Explanation The input to the parser command is not correct
Recommended Action Repeat the command.
%PKI-3-POLLCACERT : Polling CA certificate .....
Explanation Polling ca certificate.
Recommended Action Check if CA or ldap server is online.
%PKI-3-POLLRACERT : Polling RA certificate .....
Explanation Polling ra certificate.
Recommended Action Check if CA or ldap server is online.
%PKI-3-POLLROUTERCERT : Polling Router certificate for [chars] .....
Explanation Polling router certificate.
Recommended Action Check if CA or ldap server is online.
%PKI-3-QUERYCACERT : Failed to query CA certificate.
Explanation Failed to query ca certificate from ca server.
Recommended Action Use parser command cr ca auth and try again.
%PKI-3-QUERY_KEY : Querying key pair failed.
Explanation Querying public key/private key using subject name failed
Recommended Action Resubmit enrollment request. Check the subject name.
%PKI-3-SOCKETSELECT : Failed to select the socket.
Explanation The failure is caused by socket selection
Recommended Action Check tcp/socket debugging message
%PKI-3-SOCKETSEND : Failed to send out message to CA server.
Explanation The failure is caused by http transaction.
Recommended Action Check http connection to the CA server
%PKI-3-UNUSABLE_KEY_USAGE : Key-usage type '[chars]' for cert with serial number [chars] is not usable.
Explanation The given key-usage type is not usable by IOS. If seen during an import operation, this will likely cause the import to fail. Acceptable key-usage types should include Key-encipherment and/or digital-signature. Other key-usage types may be present, but will be ignored.
Recommended Action Recreate the certificate with Key-encipherment, digital-signature, or both.
%PKI-4-AUTOCERTFAILWARN : Certificate (re)enrollment failed. Delaying before retry
Explanation Automatic certificate re-enrollment failed. The router will retry in 6 hours or less depending on the expiration time of the router's certificate. Caution - Router's Certificate may expire soon.
Recommended Action Contact the CA administrator. The router will retry.
%PKI-4-CERT_ENROLL_RETRY_FAIL : Certificate (re)enrollment has failed after [dec] attempts
Explanation Automatic certificate re-enrollment failed. Caution - Router's Certificate may expire soon.
Recommended Action Contact the CA administrator. Enrollment failed.
%PKI-4-CERT_EXPIRY_WARNING : [chars] Certificate belonging to trustpoint [chars] will expire in [int] Days [int] hours [int] mins [int] secs. Issuer-name [chars] Subject-name [chars] Serial-number [chars] Auto-Renewal: [chars]
Explanation Warning to indicate that certificate is expiring soon.
Recommended Action If auto-enrol feature is not configured, re-enrol the certificate manually. Else, check if any issues with auto-enrol.
%PKI-4-CERTIFICATE_INVALID_SUBJECT : Certificate has a missing or invalid subject name.
Explanation The certificate subject name attribute must be present and not empty OR The certificate subject alt name extension must be present and include at least one entry.
Recommended Action Examine the offending certificate and re-issue it with a proper subject name.
%PKI-4-CRLHTTPFETCHFAIL : CRL Request for trustpoint [chars] returned [dec] [chars]
Explanation The CRL fetch returned something other than success. If the trustpoint revocation-check includes the keyword 'none', the transaction will succeed. If revocation- checking is not optional, the transaction will fail.
Recommended Action Verify that the CRL is at the location specified in the Certificate, and that the server is operational. To see interaction between IOS and the CRL-server, please turn on debug crypto pki transactions
%PKI-4-CRLINSERTFAIL : Trustpoint [chars] [chars] (error [dec]:[chars])
Explanation Inserting and/or verifying the CRL failed. If the trustpoint revocation-check includes the keyword 'none', the transaction will succeed. If revocation- checking is not optional, the transaction will fail.
Recommended Action Check the CRL manually to see it is correct. To see interaction between IOS and the CRL-server, please turn on debug crypto pki transactions
%PKI-4-CRL_LDAP_QUERY : An attempt to retrieve the CRL from [chars] using LDAP has failed
Explanation An LDAP query was made to acquire the certificate revocation list, but the LDAP server did not respond with the requested information. This is a warning that only applies to the Distribution Point listed. It does not necessarily reflect the overall success or failure of CRL aquistion since a prior or subsequent retrival of the CRL may have succedeed.
Recommended Action Check that the LDAP server is reachable and online. Verify that the CRL is at the requested location
%PKI-4-CS_GRANT_AUTO_CACERT_FAILURE : A rollover request for a subordinate CA certificate cannot be auto granted.
Explanation A rollover request for a subordinate CA certificate cannot be authorized and the configured auto grant policy will be ignored. This request will be added to the CS server request queue but will need to be manually granted
Recommended Action Insure that the peer's current sub CA cert is valid.
%PKI-4-CS_PUBLISH_STORAGE : Publish certificate server storage, [chars], is inaccessible.
Explanation Publish certificate server storage is inaccessible.
Recommended Action Make storage accessible, or re-configure the storage location
%PKI-4-HTTPREDIRECT : Maximum Redirection limit of [dec] exceeded, trying to retrieve URL [chars]
Explanation While fetching a document via http, there were too many redirections, and the operation has aborted. If the trustpoint revocation-check includes the keyword 'none', the transaction will succeed. If revocation- checking is not optional, the transaction will fail.
Recommended Action Verify that the CRL is at the location specified in the Certificate, and that the server is operational. To see interaction between IOS and the CRL-server, please turn on debug crypto pki transactions
%PKI-4-NOAUTOSAVE : Configuration was modified. Issue write memory to save new certificate
Explanation Auto-Enroll has obtained a new router key pair and certificate. However, the running configuration was previously modified.
Recommended Action Issue the write memory command to save the new certificate(s) and key(s).
%PKI-4-NOCONFIGAUTOSAVE : Configuration was modified. Issue write memory to save new IOS PKI configuration
Explanation IOS PKI APIs have generated new PKI configuration. However, the running configuration was previously modified.
Recommended Action Issue the write memory command to save the new PKI configuration.
%PKI-4-NOSHADOWAUTOSAVE : Configuration was modified. Issue write memory to save new IOS CA certificate
Explanation IOS CA Rollover has generated a shadow CA key pair and certificate. However, the running configuration was previously modified.
Recommended Action Issue the write memory command to save the new certificate(s) and key(s).
%PKI-4-OCSP_SERVER_CERT_VALIDATE : The OCSP Server [chars]: responder certificate validation failed
Explanation The OCSP server responder certificate validation failed
Recommended Action Check if the configured OCSP server responder certificate
%PKI-4-OCSP_SERVER_NO_RESP : The OCSP Server URL [chars] is not reachable or not responding
Explanation The OCSP server is not reachable or is not responding to the OCSP request
Recommended Action Check if the OCSP server is reachable and is receiving the OCSP request
%PKI-4-OCSP_SERVER_RESP_COMP : The OCSP Server [chars]: error:responder certificate is peer certificate
Explanation The OCSP responder certificate is peer certificate
Recommended Action Check if the configured OCSP server and responder OCSP server is same or not
%PKI-4-OCSP_SERVER_RESP_DECODE : The OCSP Server [chars]: failed to decode OCSP response data
Explanation The OCSP response data decoding is failing
Recommended Action Check if the configured OCSP server response data
%PKI-4-OCSP_SERVER_RESP_VARIFY : The OCSP Server [chars]: failed to verify OCSP response
Explanation The OCSP response verification failed
Recommended Action Check if the configured OCSP server response
%PKI-4-TRUSTPOOL_AUTO_UPDATE_DISABLED : Auto-trustpool update is disabled.
Explanation One of the certificates in the trustpool will expire soon. An attmpt to download a new trustpool bundle cannot be attempted since a bundle location is not configured
Recommended Action Either configure the bundle location in the trustpool policy or manually update the trustpool bundle.
%PKI-4-TRUSTPOOL_CERTIFICATE_SAVE_CHANGE : Downloaded Trustpool certificates present prior to image upgrade should be re-downloaded. Issue 'crypto pki trustpool import url <url>' to re-download the certificates.
Explanation Downloaded Trustpool certificates present prior to image upgrade should be re-downlaoded
Recommended Action Before image upgrade, clean all the downloaded trustpool certificates. Import them again after image upgrade.
%PKI-4-TRUSTPOOL_DOWNLOAD_FAIL : Trustpool download requires [int] bytes, available free storage [int] bytes is insufficient
Explanation Trustpool download failed Free space in nvram is not sufficient to store Trustpool Certificates. Change the Trustpool policy for its storage
Recommended Action Change the storage policy for Trustpool
%PKI-4-TRUSTPOOL_DOWNLOAD_FAILURE : Trustpool Download failed
Explanation Failed to download the trustpool bundle
Recommended Action Enable debugs and obtain the reason for failure
%PKI-4-TRUSTPOOL_EXPIRATION_WARNING : The Trustpool will expire in [chars].
Explanation One of the certificates in the trustpool will expire soon. If a bundle location is configured an auto aupdate will be attempted at predetermined intervals.
Recommended Action If a bundle location is configured in the trustpool policy no further action is required. Otherwise manual update of trustpool bundle may be needed.
%PKI-5-CERT_ENROLL_RETRY : Certificate (re)enrollment has failed and retry will happen for [dec] attempts
Explanation Automatic certificate re-enrollment failed. We are printing a consolidated message for the maximum number of retry attempts. The router will continue to retry depending on the expiration time of the router's certificate. The retry attempts will be either 999 (default) or as specified Caution - Router's Certificate may expire soon.
Recommended Action Contact the CA administrator. The router will retry.
%PKI-5-ROUTER_CERT_EXPIRED : Router certificate expired, cannot re-enroll/retry for enrollment/re-enroll
Explanation Cannot re-enroll/retry for enroll/re-enroll. Caution - Router's Certificate has expired.
Recommended Action Enroll the router manually.
%PKI-6-AUTOCERTFAIL : Certificate (re)enrollment failed. Delaying before retry
Explanation Automatic certificate enrollment or re-enrollment failed The router will retry in 6 hours or less depending on the expiration time of the router's certificate.
Recommended Action Contact the CA administrator.
%PKI-6-AUTOENROLL_KEY_LOCKED : Auto-enroll failed -RSA keypair is locked
Explanation Auto-enroll attempted to generate a new RSA keypair. However the existing RSA keypair is locked so auto-enroll cannot proceed
Recommended Action Auto-enroll will retry the enrollment request Make sure the existing RSA keypair is unlocked before the next retry
%PKI-6-AUTOSAVE : Running configuration saved to NVRAM
Explanation Auto-Enroll has obtained a new router key pair and certificate, and has done an automatic write memory to save them.
Recommended Action No action required. Informational message
%PKI-6-CERTFAIL : Certificate enrollment failed.
Explanation Certificate enroll encounter fatal error
Recommended Action Contact the CA administrator.
%PKI-6-CERT_FATAL_ERR : [chars]
Explanation Certificate enroll encounter fatal error. Abort.
Recommended Action Contact the CA administrator.
%PKI-6-CERTIFSRECV : Could not receive router's Certificate from file system.
Explanation The router's certificate could not be received from file system.
Recommended Action Verify the enrollment URL and that the router is able to read from the file system.
%PKI-6-CERTIFSSEND : Could not send Certificate enrollment request to file system.
Explanation The certificate enrollment request could not be sent to file system.
Recommended Action Verify the enrollment URL and that the router is able to write to the file system.
%PKI-6-CERTPENDING : Enter manual authentication ...
Explanation CA server want to manually authenticate the router.
Recommended Action Follow a manual authentication procedure.
%PKI-6-CERTREJECT : Certificate enrollment request was rejected by Certificate Authority
Explanation A previous certificate enrollment request was received by the Certificate Authority. It has rejected the enrollment request.
Recommended Action Contact the Certificate Authority administrator.
%PKI-6-CERTRENEWAUTO : Renewing the router certificate for trustpoint [chars]
Explanation Trustpoint certificate will expire soon, and is being automatically renewed
Recommended Action No action required. Informational message
%PKI-6-CERTRENEWMANUAL : Please renew the router certificate for trustpoint [chars]
Explanation Trustpoint certificate will expire soon, and should be renewed
Recommended Action Obtain a new certificate from the Certificate Authority
%PKI-6-CERTRET : Certificate received from Certificate Authority
Explanation A previous certificate enrollment request was received by the Certificate Authority. It has issued the certificate, and sent back a copy
Recommended Action Informational message only. No action required.
%PKI-6-CONFIGAUTOSAVE : Running configuration saved to NVRAM
Explanation IOS PKI APIs have generated new PKI configuration, and has done an automatic write memory to save them.
Recommended Action No action required. Informational message
%PKI-6-CRLHTTPFETCHREDIR : CRL Request for trustpoint [chars] returned [dec] [chars] -> [chars]
Explanation The CRL fetch returned a redirect directive. This need not be an error, if the file exists at the redirected location.
Recommended Action If no other errors are seen, then the CRL was fetched from the new location, and no action is necessary. To see interaction between IOS and the CRL-server, please turn on debug crypto pki transactions
%PKI-6-CS_DELETE : Certificate Server is deleted.
Explanation Certificate Server is deleted.
Recommended Action No action required. Informational message.
%PKI-6-CS_DELETE_TP_KEY : Trustpoint and key deleted.
Explanation Trustpoint and key used by the Certificate Server are deleted.
Recommended Action No action required. Informational message.
%PKI-6-CS_DISABLED : Certificate server now disabled.
Explanation Certificate server now disabled.
Recommended Action No action required. Informational message.
%PKI-6-CS_ENABLED : Certificate server now enabled.
Explanation Certificate server now enabled.
Recommended Action No action required. Informational message.
%PKI-6-CS_GRANT_AUTO : All enrollment requests will be automatically granted.
Explanation All enrollment requests will be automatically granted.
Recommended Action No action required. Informational message.
%PKI-6-CS_GRANT_AUTO_CACERT : All rollover subordinate CA cert requests will be automatically granted.
Explanation All rollover subordinate CA cert requests will be automatically granted.
Recommended Action No action required. Informational message.
%PKI-6-CS_GRANT_AUTO_RA : Enrollment requests coming from known RAs will be automatically granted.
Explanation Enrollment requests coming from known RAs will be automatically granted.
Recommended Action No action required. Informational message.
%PKI-6-CS_GRANT_AUTO_RACERT : All rollover RA cert requests will be automatically granted.
Explanation All rollover RA cert requests will be automatically granted.
Recommended Action No action required. Informational message.
%PKI-6-CS_REJECT_AUTO : All enrollment requests will be automatically rejected.
Explanation All enrollment requests will be automatically rejected.
Recommended Action No action required. Informational message.
%PKI-6-CS_ROLLOVER_SUCCESS : The rollover CA certificate is now active.
Explanation A switch to the CA rollover certificate has occurred.
Recommended Action No action required. Informational message.
%PKI-6-ECDSA_CERT_WITH_SHA1 : User has accepted the security implication of using lesser hash strength(SHA1) for the Elliptic Curve Key present in the certificate
Explanation The SHA1 hash algorithm is not recommended for use with the elliptic curve key in this certificate. It is recommended that SHA2 or stronger hash algorithm be used.
Recommended Action Informational message only. No action required.
%PKI-6-PKCS12EXPORT_FAIL : PKCS #12 Export Failed.
Explanation An attempt to generate and export a PKCS #12 has failed.
Recommended Action No action required. Informational message
%PKI-6-PKCS12EXPORT_SUCCESS : PKCS #12 Successfully Exported.
Explanation A PKCS #12 has been generated and successfully exported.
Recommended Action No action required. Informational message
%PKI-6-PKCS12IMPORT_FAIL : PKCS #12 Import Failed.
Explanation An attempt to import a PKCS #12 has failed.
Recommended Action No action required. Informational message
%PKI-6-PKCS12IMPORT_SUCCESS : PKCS #12 Successfully Imported.
Explanation A PKCS #12 has been successfully imported.
Recommended Action No action required. Informational message
%PKI-6-PKI_CRL_DOWNLOADED : CRL download notification sent for Issuer = [chars].
Explanation CRL is downloaded and successfully inserted in the database. Notification for the same is sent to applications registered.
Recommended Action Informational message only. No action required.
%PKI-6-SHADOWAUTOSAVE : Running configuration saved to NVRAM
Explanation IOS CA Rollover has generated a shadow CA key pair and certificate, and has done an automatic write memory to save them.
Recommended Action No action required. Informational message
%PKI-6-TRUSTPOOL_AUTO_UPDATE : Auto-trustpool update in progress from [chars].
Explanation One of the certificates in the trustpool will expire soon. An attmpt to download a new trustpool bundle is in progress
Recommended Action Since an url has been configured that identifies the location to aquire the trustpool bundle, then no action is required.
%PKI-6-TRUSTPOOL_DOWNLOAD_SUCCESS : Trustpool Download is successful
Explanation Trustpool Download is successful
Recommended Action No action required. Informational message
PKTLOG
%PKTLOG-1-PROXY_MEM_APPEND_ERR : [int] [int] [int]
Explanation Could not add memory to memory pool
Recommended Action LOG_STD_ACTION
%PKTLOG-1-PROXY_MEM_RET_ERR : [chars] [int] [int] [int]
Explanation IPC failed and could not return memory
Recommended Action LOG_STD_ACTION
%PKTLOG-2-PROXY_IPC_SET_FAILED : [chars]
Explanation Packet logger proxy IPC handler could not be initialized.
Recommended Action LOG_STD_ACTION
%PKTLOG-3-PKTLOG_IPC_SEND_FAILED : [chars] [chars]
Explanation Transmission of an IPC message by the packet logger failed. ACL and stats lost.
Recommended Action LOG_STD_ACTION
%PKTLOG-3-PROXY_BAD_SUBTYPE : [dec]
Explanation Invalid subtype was passed to packet logger proxy IPC handler.
Recommended Action LOG_STD_ACTION
%PKTLOG-3-PROXY_IPC_ALLOC_FAILED : [chars]
Explanation Allocation of an IPC packet buffer by the packet logger proxy failed.
Recommended Action LOG_STD_ACTION
%PKTLOG-3-PROXY_IPC_SEND_FAILED : [chars] [chars]
Explanation Transmission of an IPC message by the packet logger proxy failed.
Recommended Action LOG_STD_ACTION
%PKTLOG-4-PKTLOG_IPC_ALLOC_FAILED : [chars]
Explanation Allocation of an IPC packet buffer by the packet logger failed.
Recommended Action LOG_STD_ACTION
%PKTLOG-4-PROXY_DUP_INIT : [chars]
Explanation Duplicate initialization IPC message received for user %d client id %d.
Recommended Action LOG_STD_ACTION
%PKTLOG-4-PROXY_INVALID_USER_IDX : [int] [int]
Explanation IPC message contained invalid user index for client id.
Recommended Action LOG_STD_ACTION
%PKTLOG-4-PROXY_IPC_INVALID_MSG_LEN : [dec]:[dec] len [dec] flags [hex] source [dec]
Explanation Invalid IPC message length.
Recommended Action LOG_STD_ACTION
PLATFORM
%PLATFORM-3-BACKUP_NVRAM_OPEN_FAIL : Failed to open backup nvram -[chars].
Explanation The backup nvram device could not be opened.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PLATFORM-3-BACKUP_NVRAM_READ_FAIL : Failed to read backup nvram -[chars].
Explanation The backup nvram contents could not be read.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PLATFORM-3-BACKUP_NVRAM_WRITE_FAIL : Failed to write backup nvram -[chars].
Explanation Couldn't write into the backup nvram device.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PLATFORM-3-GEC_NOMAC : Can't allocate MAC address for port-channel interface [int]
Explanation MAC address allocation failed for the port-channel interface specified in the message. This may happen if the port-channel interface exceeds the maximum number of supported port-channel interfaces.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PLATFORM-3-HASTATUS_FAIL : RP switchover, [chars] (count [int])
Explanation RP switchover failed to reach active state. The RP will be reset. This is indicative of a IPC problem between IOSd and CMRP
Recommended Action Make sure system achieves full redundant state after the RP reset. If not, reload entire system
%PLATFORM-3-NO_BASEMAC : Can't retrieve base MAC address
Explanation Base MAC address determination failed at system start.
Recommended Action LOG_STD_ACTION
%PLATFORM-3-NOMAC : Can't allocate MAC address for interface [int]/[int]
Explanation MAC address allocation failed because of an incorrect slot and port combination, which exceeds the maximum available hardware.
Recommended Action LOG_STD_ACTION
%PLATFORM-3-NOMAC_INTF : Failed to allocate MAC address for interface [chars]
Explanation MAC address allocation failed for logical interface specified in the message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PLATFORM-3-NVRAM_OPEN_FAIL : Failed to open nvram -[chars].
Explanation The nvram device could not be opened.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PLATFORM-3-NVRAM_READ_FAIL : Failed to read nvram -[chars].
Explanation The nvram contents could not be read.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PLATFORM-3-NVRAM_WRITE_FAIL : Failed to write nvram -[chars].
Explanation Couldn't write into the nvram device.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PLATFORM-3-REDMODE_FAIL : Redundancy mode: [chars] (rc [dec])
Explanation Redundancy mode change could not be processed. This is indicative of a IPC problem between IOSd and the peer platform process.
Recommended Action Make sure system achieves full redundant state. If not, reload entire system
%PLATFORM-3-RF_PROG_FAIL : Progression completion notification to chassis management failed, [chars]
Explanation Could not notify the completion of the RF progression to the chassis management process. The system will potentially not be in a fully redundant state.
Recommended Action LOG_STD_ACTION
%PLATFORM-3-RF_RELOAD_PEER : Reload peer notification to chassis management failed, [chars]
Explanation Could not notify Reload Peer to the chassis management process. The Standby peer could not be reloaded by the Active. The system will potentially not be in a fully redundant state.
Recommended Action Reload peer instance using the available CLI commands. If system does not achieve full Standby status after that, the system must be reloaded
%PLATFORM-4-HASTATUS_WARN : RP HA status warning, [chars])
Explanation Standby RP reports peer not present event. This is indicative of a IPC problem between IOSd and CMRP
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PLATFORM-4-RELOAD_STANDBY : [chars] reload requested by [chars]. Reason [chars]
Explanation Unexpected configuration or states mismatch between Active and Standby RPs. Reloading Standby to synchronize the configuration or states.
Recommended Action None. This is expected behavior.
%PLATFORM-4-STATS_COLLECTION : Reducing statistics collection interval for SPA ([chars]) will impact the RP control plane activity
Explanation MIB statistics for HW counters are sent from CC to RP every 10 seconds by default, changing the timer through CLI to send more often will increase RP CPU utilization and result in sending more IPC messages between CC and RP
Recommended Action No action is required.
%PLATFORM-6-EVENT_LOG : [chars]
Explanation An entry from the internal event log at reload on the standby RP. This is informational.
Recommended Action No action is required.
%PLATFORM-6-HASTATUS : RP switchover, [chars]
Explanation RP switchover events received by platform code.
Recommended Action No action is required.
%PLATFORM-6-HASTATUS_DETAIL : RP switchover, [chars] (count [int])
Explanation RP switchover events received by platform code.
Recommended Action No action is required.
%PLATFORM-6-LOWSPACE : SD [chars] : low space alarm assert
Explanation bootflash memory is very low Delete the old file from boot flash to create space
Recommended Action No action is required.
%PLATFORM-6-LOWSPACERECOVER : SD [chars] : low space alarm deassert
Explanation bootflash memory
Recommended Action No action is required.
%PLATFORM-6-RF_PROG_SUCCESS : RF state [chars]
Explanation A marker to illuminate when the standby reaches a terminal state.
Recommended Action No action is required.
%PLATFORM-6-SB_INIT_DELAY : RF progression will be suspended due to standby initialization delay configuration setting. Standby initialization will resume after [int] seconds
Explanation An informational message about the standby initialization delay configuration. RF progression will be delayed for the configured value. Bulk-sync and other progression events will not happen until after the configured delay value
Recommended Action No action is required.
%PLATFORM-6-SB_INIT_DELAY_END : RF progression delay timer expired. Standby initialization will now continue
Explanation An informational message about the standby initialization delay configuration. RF progression will now continue since configured delay has expired
Recommended Action No action is required.
%PLATFORM-3-ELEMENT_CRITICAL : [chars]: [chars] value [chars] [chars] critical level [chars]
Explanation The Shell Manager monitors the health of each board and emits an error message when a value has passed a critical level.
Recommended Action Reduce static and dynamic loads on the system by reducing the number of elements in the configuration or by limiting the capacity for dynamic services.
%PLATFORM-4-ELEMENT_WARNING : [chars]: [chars] value [chars] [chars] warning level [chars]
Explanation The Shell Manager monitors the health of each board and emits a warning message when a value has passed a critical level.
Recommended Action Reduce static and dynamic loads on the system by reducing the number of elements in the configuration or by limiting the capacity for dynamic services.
PLATFORM_ACT2
%PLATFORM_ACT2-2-SUDI_VALIDATION_FAILED : Secure UDI validation failed. [chars]
Explanation Secure UDI validation for the chassis failed. The router failed to authenticate itself
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
PLATFORM_BRKOUT
%PLATFORM_BRKOUT-3-BRKOUTCMD_SYNCFAILED : Failed to send Breakout command to hardware.
Explanation A messages that was sent the hardware module, was not deliverd correctly. The failure most likely occurred because of a software communication error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
PLATFORM_CAPABILITY
%PLATFORM_CAPABILITY-4-CALL : Fatal Initialization Error -[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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%PLATFORM_CAPABILITY-4-INIT : Fatal Initialization 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
PLATFORM_INFRA
%PLATFORM_INFRA-5-IOS_INTR_EVENT : IOS thread interrupt event ([dec]).
Explanation IOS thread process interrupt event
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PLATFORM_INFRA-5-IOS_INTR_HISTORY : [[dec]|[dec]] [[dec]:[dec]] [[dec]->[dec]] ra[ l* [hex] l* [hex] ]
Explanation IOS thread process interrupt history
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PLATFORM_INFRA-5-IOS_INTR_INVALID_LEVEL : IOS thread interrupt level [dec] replaced by [dec]
Explanation An invalid IOS thread interrupt level was used
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PLATFORM_INFRA-5-IOS_INTR_LIMIT_NOT_SET : IOS thread interrupt limit not set
Explanation IOS failed to retrieve interrupt limit
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PLATFORM_INFRA-5-IOS_INTR_OVER_LIMIT : IOS thread disabled interrupt for [int] msec
Explanation IOS thread process disabled interrupt too long
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
PLATFORM_SCC
%PLATFORM_SCC-1-AUTHENTICATION_FAIL : Chassis authentication failed
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 Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
PLATFORM_TAM
%PLATFORM_TAM-2-SUDI_VALIDATION_FAILED : Secure UDI validation failed. [chars]
Explanation Secure UDI validation for the module failed. The module failed to authenticate itself
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
PLIM_QOS
%PLIM_QOS-3-IOSXE_RP_PLIM_QOS_FAIL : A software error while configuring the [chars] on slot [dec]
Explanation This error happens when IOS fails to send messages to configure the per slot qos parameters in forwarding plane
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
PMAN
%PMAN-0-PROCESS_NOTIFICATION : The process lifecycle notification component failed because [chars]
Explanation The process lifecycle notification component failed, preventing proper detection of a process start and stop. This problem is likely the result of a software defect in the software sub-package.
Recommended Action Note the time of the message and investigate the kernel error message logs to learn more about the problem and see if it is correctable. If the problem cannot be corrected or the logs are not helpful, copy the error message exactly as it appears on the console along with the output of show tech-support and provide the gathered information to a Cisco technical support representative.
%PMAN-0-PROCFAILCRIT : A critical process [chars] has failed (rc [dec])
Explanation A process important to the functioning of the router 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, copy the error message and the output of show platform software tech-support into a plaintext file and contact Cisco technical support with the gathered information.
%PMAN-3-PROC_BAD_COMMAND : Non-existent executable or bad library used for process [chars]
Explanation The executable file used for the process is missing or a dependent library is bad
Recommended Action Make sure that the named executable is present and dependent libraries are good
%PMAN-3-PROC_BAD_EXECUTABLE : Bad executable or permission problem with process [chars]
Explanation The executable file used for the process is bad or has permission problem
Recommended Action Make sure that the named executable is replaced with correct executable
%PMAN-3-PROC_EMPTY_EXEC_FILE : Empty executable used for process [chars]
Explanation The executable file used for the process is empty
Recommended Action Make sure that the named executable is of non-zero size
%PMAN-3-PROCFAIL : The process [chars] has failed (rc [dec])
Explanation The process has failed as the result of an error.
Recommended Action This message will appear with other messages related to the process. Check the other messages to determine the reason for the failures and see if corrective action can be taken. If the problem persists, copy the error messages and the output of show platform software tech-support into a plaintext file and contact Cisco technical support.
%PMAN-3-PROCFAIL_IGNORE : [chars] process exits and failures are being ignored due to debug settings. Normal router functionality will be affected. Critical router functions like RP switchover, router reload, FRU resets, etc. may not function properly.
Explanation A process exit or failure is being ignored due to the user-configured debug settings.
Recommended Action If this behavior is desired and the debug settings are set according to the user's preference, no action is needed. If the appearance of this message is viewed as a problem, change the debug settings. The router is not expected to behave normally with this debug setting. Functionality like SSO switchover, router reloads, FRU resets, etc. will be affected. This setting should only be used in a debug scenario. It is not normal to run the router with this setting
%PMAN-3-PROCFAILOPT : An optional process [chars] has failed (rc [dec])
Explanation A process that does not affect the forwarding of traffic has failed.
Recommended Action Note the time of the message and investigate the kernel error message logs to learn more about the problem. Although traffic will still be forwarded after receiving this message, certain functions on the router may be disabled as a result of this message and the error should be investigated. If the logs are not helpful or indicate a problem you cannot correct, copy the error message as it appears on the console and the output of show tech-support and provide the information to a Cisco technical support representative.
%PMAN-3-PROCHOLDDOWN : The process [chars] has been helddown (rc [dec])
Explanation The process was restarted too many times with repeated failures and has been placed in the holddown state.
Recommended Action This message will appear with other messages related to the process. Check the other messages to determine the reason for the failures and see if corrective action can be taken. If the problem persists, copy the error messages and the output of show platform software tech-support into a plaintext file and contact Cisco technical support.
%PMAN-3-PROC_RESTART_CNT_EXCEEDED : The process [chars] restart count ([dec]) has exceeded the configured limit ([dec])
Explanation The process was restarted many times and has exceeded the configured limit.
Recommended Action This message will appear with other messages related to the process. Check the other messages to determine the reason for the failures and see if corrective action can be taken. If the problem persists, copy the error messages and the output of show platform software tech-support into a plaintext file and contact Cisco technical support.
%PMAN-3-RELOAD_FRU_IGNORED : All [chars]/[dec] reloads are being ignored. This is being done for debugging purposes and will be changed at a later time to allow the reload. Critical router functions like RP switchover, router reload, FRU resets, etc. may not function properly.
Explanation A supervisor failure is being ignored due to debugging purposes.
Recommended Action This will be removet at a later point in time
%PMAN-3-RELOAD_RP : Reloading: [chars]
Explanation The RP is being reloaded
Recommended Action Make sure this is not due to an error condition. If it is due to an error condition, collect information requested by the other log messages
%PMAN-3-RELOAD_RP_SB_NOT_READY : Reloading: [chars]
Explanation The RP is being reloaded since there is no ready standby instance
Recommended Action Make sure this is not due to an error condition
%PMAN-3-RELOAD_SYSTEM : Reloading: [chars]
Explanation The system is being reloaded
Recommended Action Make sure this is not due to an error condition. If it is due to an error condition, collect information requested by the other log messages
%PMAN-3-RPSWITCH : RP switch initiated. Critical process [chars] has failed (rc [dec])
Explanation A RP switchover has been initiated due to a critical fault
Recommended Action Make sure this is not due to an error condition. If it is due to an error condition, collect debug information like all console output and log files
%PMAN-5-EXITACTION : Process manager is exiting: [chars]
Explanation The process manager is exiting
Recommended Action Make sure this is not due to an error condition. If it is due to an error condition, collect information requested by the other log messages
%PMAN-6-PROCSHUT : The process [chars] has shutdown
Explanation The process has gracefully shutdown.
Recommended Action No user action is necessary. This message is provided for informational purposes only.
%PMAN-6-PROCSTART : The process [chars] has started
Explanation The process has launched and is operating properly.
Recommended Action No user action is necessary. This message is provided for informational purposes only.
%PMAN-6-PROCSTATELESS : The process [chars] is restarting stateless
Explanation The process has requested a stateless restart.
Recommended Action No user action is necessary. This message is provided for informational purposes only.
PMDWDM
%PMDWDM-4-TCA : [chars]: [chars] [chars] [chars] value (%lld) threshold (%lld) [chars]
Explanation The specified PM FEC TCA has been declared or released
Recommended Action Recommended action is to repair the source of the alarm.
PMIPV6
%PMIPV6-5-TUNNELDELETE : Deleting the Proxy Mobile IPv6 tunnel [chars]
Explanation The PMIPv6 tunnel is being deleted.
Recommended Action If you suspect this condition contact technical support representative with the output of show tech
%PMIPV6-5-TUNNELUP : Bringing up the Proxy Mobile IPv6 tunnel [chars]
Explanation The PMIPv6 tunnel is being deleted.
Recommended Action If you suspect this condition contact technical support representative with the output of show tech.
POLICY_API
%POLICY_API-3-SBINIT : Error initializing [chars] subblock data structure. [chars]
Explanation Initialization of the specified subblock data structure could not be accomplished.
Recommended Action None
%POLICY_API-4-POLICYDYNCLR : Dynamic policy on intf:[chars] cleared. Static policy in use.
Explanation A dynamic policy was overriding the static policy. The dynamic policy has been cleared, the static policy is now in effect.
Recommended Action No action required.
%POLICY_API-4-POLICYOVERIDE : Dynamic policy overriding static on intf:[chars]
Explanation Static policy and dynamic policy are configured on the interface. The dynamic policy will override the static policy.
Recommended Action Remove the static policy config if desired.
%POLICY_API-4-POLICYSTATICCLR : Static policy on intf:[chars] cleared. Dynamic policy in use.
Explanation A dynamic policy was overriding the static policy. Static policy has been cleared.
Recommended Action No action required.
POLICY_MANAGER
%POLICY_MANAGER-2-INIT_FAILURE : Init failure: [chars]
Explanation A problem occurred in the Policy Manager during initialization
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%POLICY_MANAGER-2-NO_FREE_EVENT_BUFFERS : Event pool depleted: [chars]
Explanation The event pool has been depleted. There are no free buffers to process event
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%POLICY_MANAGER-3-INVALID_ACTION : Invalid action
Explanation An invalid Policy Manager action was detected.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%POLICY_MANAGER-3-INVALID_PARAMETERS : A call to Policy Manager is made with invalid parameters
Explanation A call to Policy Manager was made with one or more invalid parameters
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%POLICY_MANAGER-3-INVALID_SEVERITY : Invalid event severity [hex]
Explanation The event that was received by the Policy Manager contained an invalid severity and was therefore not processed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%POLICY_MANAGER-3-NO_FREE_POLICY_IDS : No more Policy IDs available
Explanation There are no more Policy IDs that can be allocated. The effect of this is that Policy Manager policies can no longer be created.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%POLICY_MANAGER-3-NULL_ACTION_ROUTINE : NULL action routine invoked
Explanation The Policy Manager attempted to invoke an action which was NULL
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%POLICY_MANAGER-3-PRE_INIT_CALL : Policy Manager routine called prior to initialization
Explanation The Policy Manager component was called prior to initialization. This could result in vital information being lost.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
POS_SPA_FRMR
%POS_SPA_FRMR-3-C2_MISMATCH : The software ([int]) and hardware ([int]) copy of sonet c2 is detected to be different during Minimal Disruptive Restart.
Explanation During Minimal Disruptive Restart, the software and hardware copy of the sonet C2 parameter is found to be different. This indicates an error and the SPA will be reset as normal and will impact traffic.
Recommended Action Open a case with Cisco Technical Assistance Center for further assistance.
%POS_SPA_FRMR-3-CRC_MISMATCH : The software ([dec]) and hardware ([dec]) copy of crc is detected to be different during Minimal Disruptive Restart.
Explanation During Minimal Disruptive Restart, the software and hardware copy of the crc parameter is found to be different. This indicates an error and the SPA will be reset as normal and will impact traffic.
Recommended Action Open a case with Cisco Technical Assistance Center for further assistance.
%POS_SPA_FRMR-3-FRAMING_MISMATCH : The software ([dec]) and hardware ([dec]) copy of framing is detected to be different during Minimal Disruptive Restart.
Explanation During Minimal Disruptive Restart, the software and hardware copy of the framing parameter is found to be different. This indicates an error and the SPA will be reset as normal and will impact traffic.
Recommended Action Open a case with Cisco Technical Assistance Center for further assistance.
%POS_SPA_FRMR-3-LOOPBACK_MISMATCH : The software ([dec]) and hardware ([dec]) copy of loopback is detected to be different during Minimal Disruptive Restart.
Explanation During Minimal Disruptive Restart, the software and hardware copy of the loopback parameter is found to be different. This indicates an error and the SPA will be reset as normal and will impact traffic.
Recommended Action Open a case with Cisco Technical Assistance Center for further assistance.
%POS_SPA_FRMR-3-MTU_MISMATCH : The software ([dec]) and hardware ([dec]) copy of mtu is detected to be different during Minimal Disruptive Restart.
Explanation During Minimal Disruptive Restart, the software and hardware copy of the mtu is found to be different. This indicates an error and the SPA will be reset as normal and will impact traffic.
Recommended Action Open a case with Cisco Technical Assistance Center for further assistance.
%POS_SPA_FRMR-3-NULL_DEV_OBJ :
Explanation Pointer to framer device object is NULL.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%POS_SPA_FRMR-3-RECONCILE_FAILURE : Framer reconcilation failure for SPA in [int]/[int] during Minimal Disruptive Restart.
Explanation During Minimal Disruptive Restart, the framer reconcilation error has occured. This indicates an error and the SPA will be reset as normal and will impact traffic.
Recommended Action Open a case with Cisco Technical Assistance Center for further assistance.
%POS_SPA_FRMR-3-RECONFIG_FAILURE : Framer reconfiguration failed for SPA in [int]/[int], with error [dec] during Minimal Disruptive Restart.
Explanation During Minimal Disruptive Restart, the framer reconfig error has occured. This indicates an error and the SPA will be reset as normal and will impact traffic.
Recommended Action Open a case with Cisco Technical Assistance Center for further assistance.
%POS_SPA_FRMR-3-RESTART_FAILURE : Framer restart failed for SPA in [int]/[int] with error [dec] during Minimal Disruptive Restart.
Explanation During Minimal Disruptive Restart, framer restart error has occured. This indicates an error and the SPA will be reset as normal and will impact traffic.
Recommended Action Open a case with Cisco Technical Assistance Center for further assistance.
%POS_SPA_FRMR-3-S1S0_MISMATCH : The software ([int]) and hardware ([int]) copy of sonet S1S0 is detected to be different during Minimal Disruptive Restart.
Explanation During Minimal Disruptive Restart, the software and hardware copy of the sonet S1S0 parameter is found to be different. This indicates an error and the SPA will be reset as normal and will impact traffic.
Recommended Action Open a case with Cisco Technical Assistance Center for further assistance.
%POS_SPA_FRMR-3-SCRAMBLE_MISMATCH : The software ([dec]) and hardware ([dec]) copy of scrambling is detected to be different during Minimal Disruptive Restart.
Explanation During Minimal Disruptive Restart, the software and hardware copy of the scrambling parameter is found to be different. This indicates an error and the SPA will be reset as normal and will impact traffic.
Recommended Action Open a case with Cisco Technical Assistance Center for further assistance.
%POS_SPA_FRMR-3-TRANSMIT_DELAY_MISMATCH : The software ([int]) and hardware ([int]) copy of transmit-delay is detected to be different during Minimal Disruptive Restart.
Explanation During Minimal Disruptive Restart, the software and hardware copy of the transmit delay parameter is found to be different. This indicates an error and the SPA will be reset as normal and will impact traffic.
Recommended Action Open a case with Cisco Technical Assistance Center for further assistance.
POS_SPA_SPI4
%POS_SPA_SPI4-3-RECONFIG_FAILURE : SPI4 reconfiguration failed for SPA in [int]/[int], with error [dec] during Minimal Disruptive Restart.
Explanation During Minimal Disruptive Restart, the spi4 reconfig error has occured. This indicates an error and the SPA will be reset as normal and will impact traffic.
Recommended Action Open a case with Cisco Technical Assistance Center for further assistance.
%POS_SPA_SPI4-3-RESTART_FAILURE : SPI4 restart failed for SPA in [int]/[int] with error [dec] during Minimal Disruptive Restart.
Explanation During Minimal Disruptive Restart, spi4 restart error has occured. This indicates an error and the SPA will be reset as normal and will impact traffic.
Recommended Action Open a case with Cisco Technical Assistance Center for further assistance.
PRST_IFS
%PRST_IFS-3-FILE : persistent media IFS file error: [chars]
Explanation Persistent media module (file system) file error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PRST_IFS-3-FILEMEM : No memory to update [chars]. Please free some space
Explanation There is no filesystem memory for the system to write an updated version of the persistent variable file.
Recommended Action Please free space on the filesystem shown in the error message as soon as possible. This will involve deleting existing files, and/or squeezing the filesystem if the filesystem requires it (bootflash for example may require it).
%PRST_IFS-3-GENERAL : persistent media IFS general error: [chars]
Explanation Persistent media module (file system) general error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
PSM
%PSM-3-BADLABELADD : Cannot add label -[chars].
Explanation Unable to create label due to reason given.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PSM-3-CHUNK : [chars]: [chars] [hex] [hex]
Explanation Parameterized Chunk Manager error occurred
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version, show running-config and show process memory and contact your Cisco technical support representative.
%PSM-3-INVALIDPARAM : Invalid parameter -[chars]
Explanation Calling function has passed an invalid parameter.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PSM-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.
%PSM-3-L2_PATH : [chars] -path set [hex]([IPV6 address]), path [chars]
Explanation Internal error while processing layer 2 path.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PSM-3-NONIPINFO : Non-ip info: [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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PSM-3-NOOCE : Attempt to get labels from OCE failed -[chars].
Explanation Calling function has provided insufficient information to get labels.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PSM-3-NORESOURCE : [chars] [dec]
Explanation Resource Failure: %s %d
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
PTPD
%PTPD-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.
%PTPD-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.
%PTPD-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.
%PTPD-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.
%PTPD-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.
%PTPD-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.
%PTPD-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.
%PTPD-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.
%PTPD-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.
%PTPD-0-IPC_CONNECT_MASTER : IPC connection to the active RSP failed because [chars]
Explanation IPC connection to the active RSP 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.
%PTPD-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.
%PTPD-0-MESSAGE_REGISTER : Failed to register with active RSP because [chars]
Explanation The active RSP 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.
%PTPD-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.
%PTPD-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.
%PTPD-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.
%PTPD-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.
%PTPD-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.
%PTPD-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.
%PTPD-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.
%PTPD-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.
PUNT_INJECT
%PUNT_INJECT-2-CAUSE_CFG_ERR : [chars] [chars] initialization failed
Explanation Initialization of Punt/Inject cause failed due to invalid configuration parameters
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PUNT_INJECT-3-DROP_POLICY_SKIPPED : [chars] cause=[dec] output drop policy skipped
Explanation Output drop policy unexpected skipped on punt packet
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PUNT_INJECT-5-DROP_PUNT_CAUSE : punt cause policer drop packet casue [dec], MSGDEF_LIMIT_SLOW
Explanation drop punt packet by punt cause policer
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%PUNT_INJECT-5-DROP_PUNT_INTF : punt interface policer drop packet from [chars], MSGDEF_LIMIT_SLOW
Explanation drop punt packet from source interface
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
PW
%PW-3-IPC_ALLOC_FAILED : [chars]
Explanation Allocation of an IPC packet buffer by the pseudo wired feature failed.
Recommended Action LOG_STD_ACTION
%PW-3-IPC_SEND_FAILED : [chars]
Explanation Transmission of an IPC message by the pseudo wire feature failed.
Recommended Action LOG_STD_ACTION
Q
QFP_MLP
%QFP_MLP-2-BQS_SCRATCH_TOOSMALL : QFP BQS Scratch area too small for MLP feature usage (size: [dec], need: [dec]).
Explanation Cisco internal software error. QFP MLP initialization detected that the BQS scratch memory area is insufficient for MLP usage. The MLP Bundle interfaces 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-2-PROXY_IPC_INIT_FAILED : QFP MLP Proxy IPC interface initialization failure (result: [dec]).
Explanation Cisco internal software error. QFP MLP initialization detected that the Proxy IPC interface initialization failed. The MLP Bundle interfaces 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-3-EARLY_RX_CLEANUP : QFP MLP Early Receive cleanup error ([chars])
Explanation Cisco internal software error. Multilink Early Receive cleanup could not be performed due to indicated error. This could cause possible QFP memory leak.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-3-EARLY_RX_INIT : QFP MLP Early Receive initialization error ([chars])
Explanation Cisco internal software error. Multilink Early Receive initialization could not be performed due to indicated error. This could cause possible lost MLP encapsulated packets during member link/bundle bringup and possibly cause the failure to complete member link/bundle initialization.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-3-INV_PROXY_MSG : QFP MLP Proxy received invalid Message ID [dec]
Explanation Cisco internal software error. QFP MLP Proxy received an invalid Message ID. This message will be ignored.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-3-MCMP_INVALID_RX_CLASS : MLP MCMP suspension class ID ([dec]) received from the peer must be less than the number of negotiated classes ([dec]) for interface [chars] (Peer error), MSGDEF_LIMIT_SLOW
Explanation Possible error on the peer device with PPP Multilink Multiclass (MCMP). Received MLP packet contained a MCMP suspension class ID greater than the number of negotiated suspension classes.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-3-MCMP_TX_ENCAP_SEQ_CFG_ERROR : MLP QoS encap-sequence ([dec]) must be less than the number of MCMP suspension classes ([dec]) for output interface [chars], MSGDEF_LIMIT_SLOW
Explanation User software configuration mismatch with PPP Multilink Multiclass (MCMP). User needs to either reduce the highest encap-sequence in the policy-map to be less than the number of negotiated MCMP suspension classes or increase the number of suspension classes negotiated with the peer.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-3-MLP_INVALID_EVSI_INTF_STATE : MLP Link Add/Update receved with invalid EVSI indication for Member Link: [chars], Bundle: [chars]
Explanation Either the user attempted to mix broadband and non-broadband member links on the same bundle or an internal error has occurred processing a configuration update.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-3-PROXY_B_TX_IDLE_LINK_TRANSITION : QFP MLP Proxy ([chars] [chars]) invalid Bundle state [chars] ([dec]) for interface [chars]/[chars]
Explanation Cisco internal software error. Multilink Idle-Link transition could not be made due invalid Bundle state at the time of the request. The associated MLP Bundle interface may not be fully functional as a result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-3-PROXY_DUP_LINK_ID : QFP MLP Proxy ([chars] [chars]) duplicate Link ID [dec] for interface [chars] and [chars]
Explanation Cisco internal software error. QFP MLP Proxy message Link Add could not be processed for the indicated interface due use of a given Link ID on multiple member links within the same MLP Bundle. The associated MLP Bundle interface may not be fully functional as a result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-3-PROXY_INV_BUFFER_LIMIT : QFP MLP Proxy ([chars] [chars]) indicated an invalid Rx buffer limit ([dec]) for interface [chars]
Explanation Cisco internal software error. QFP MLP was provided a invalid Rx buffer limit value. The associated MLP Bundle interface may not be fully functional as a result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-3-PROXY_INV_BUNDLE_STATE : QFP MLP Proxy ([chars] [chars]) invalid Bundle state [chars] ([dec]) for interface [chars]
Explanation Cisco internal software error. QFP MLP Proxy message could not be processed due to the MLP Bundle being in an incorrect state to accept the message. The associated MLP Bundle interface may not be fully functional as a result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-3-PROXY_INV_CLASS_INFO : QFP MLP Proxy ([chars] [chars]) invalid Class Info (Base: [hex], Num: [dec]) for interface [chars]
Explanation Cisco internal software error. QFP MLP Proxy message contained invalid MLP Class information. The associated MLP Bundle interface may not be fully functional as a result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-3-PROXY_INV_LINK_ID : QFP MLP Proxy ([chars] [chars]) invalid Link ID [dec] for interface [chars]
Explanation Cisco internal software error. QFP MLP Proxy message Link Add could not be processed for the indicated interface due to an invalid Link ID. The associated MLP Bundle interface may not be fully functional as a result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-3-PROXY_INV_LINK_STATE : QFP MLP Proxy ([chars] [chars]) invalid Link state [chars] ([dec]) for interface [chars]
Explanation Cisco internal software error. QFP MLP Proxy message could not be processed due to the MLP Link being in an incorrect state to accept the message. The associated MLP Bundle interface may not be fully functional as a result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-3-PROXY_INV_LOST_FRAG_TO : QFP MLP Proxy ([chars] [chars]) indicated an invalid lost fragment timeout ([dec]) for interface [chars]
Explanation Cisco internal software error. QFP MLP was provided a invalid lost fragment timeout value. The associated MLP Bundle interface may not be fully functional as a result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-3-PROXY_INV_MRRU : QFP MLP Proxy ([chars] [chars]) invalid MRRU [dec] for interface [chars]
Explanation Cisco internal software error. QFP MLP Proxy message contained an invalid MLP Bundle MRRU. The associated MLP Bundle interface may not be fully functional as a result of this condition. Possible workaround is to reduce the interface mtu on the Multilink bundle interface on both ends of the connection to 9216 or less and then shut/no shut the Multilink bundle interface to force renegotiation of the MLP MRRU.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-3-PROXY_INV_RX_TX_INTF_VALUE : QFP MLP Proxy ([chars] [chars]) invalid Rx/Tx interface value [dec] for interface [dec] (handle)
Explanation Cisco internal software error. QFP MLP Proxy was unable to complete the requested MLP Bundle state change or configuration update due to an invalid interface Rx/Tx designation in the proxy request. The associated MLP Bundle interface may not be fully functional as a result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-3-PROXY_INV_SUB_DEV_ID : QFP MLP Proxy ([chars] [chars]) invalid Sub-Device ID [dec] for interface [chars]
Explanation Cisco internal software error. QFP MLP Proxy message Bundle Add could not be processed for the indicated interface due to an invalid Sub-Device ID. The associated MLP Bundle interface may not be fully functional as a result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-3-PROXY_INV_TX_LINK_FRAG_SIZE : QFP MLP Proxy ([chars] [chars]) indicated an invalid Tx Link optimal fragment size ([dec]) for interface [chars]
Explanation Cisco internal software error. QFP MLP Proxy message contained invalid Tx Link optimal fragment size information. The associated MLP Member Link and/or Bundle interface may not be fully functional as a result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-3-PROXY_INV_TX_LINK_WEIGHT : QFP MLP Proxy ([chars] [chars]) indicated an invalid Tx Link weight ([dec]) for interface [chars]
Explanation Cisco internal software error. QFP MLP Proxy message contained invalid Tx Link weight information. The associated MLP Member Link and/or Bundle interface may not be fully functional as a result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-3-PROXY_IPC_ALLOC_FAIL : QFP MLP Proxy ([chars]) response lost due to buffer allocation failure (Interface [chars])
Explanation Cisco internal software error. QFP MLP Proxy message processing detected a IPC buffer allocation failure during response processing. The associated MLP interface may not be fully functional as a result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-3-PROXY_LAI_TX_IDLE_LINK_TRANSITION : QFP MLP Proxy ([chars] [chars]) invalid Link state [chars] ([dec]) for interface [chars]/[chars]
Explanation Cisco internal software error. Multilink Idle-Link transition could not be made due invalid Link state at the time of the request to convert the link to an Idle-Link. The associated MLP Bundle interface may not be fully functional as a result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-3-PROXY_LIA_TX_IDLE_LINK_TRANSITION : QFP MLP Proxy ([chars] [chars]) invalid Link state [chars] ([dec]) for interface [chars]/[chars]
Explanation Cisco internal software error. Multilink Idle-Link transition could not be made due invalid Link state at the time of the request to convert the Idle-Link to an active link. The associated MLP Bundle interface may not be fully functional as a result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-3-PROXY_NULL_BUNDLE : QFP MLP Proxy ([chars] [chars]) NULL Bundle sub-block for interface [dec] (handle)
Explanation Cisco internal software error. QFP MLP Proxy was unable to complete the requested MLP Bundle state change or configuration update due to an invalid or uninitialized Bundle sub-block. The associated MLP Bundle interface may not be fully functional as a result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-3-PROXY_NULL_LINK : QFP MLP Proxy ([chars] [chars]) NULL Member Link sub-block for interface [dec] (handle)
Explanation Cisco internal software error. QFP MLP Proxy was unable to complete the requested MLP Member Link state change or configuration update due to an invalid or uninitialized Member Link sub-block. The associated MLP Member Link interface may not be fully functional as a result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-3-PROXY_SID_UPDATE_COMPLETE_ERROR : QFP MLP Proxy ([chars]) SID Update Complete w/o Preceeding Lock (Interface [chars], SID: [hex])
Explanation Cisco internal software error. QFP MLP Proxy message processing detected a Bundle Schedule SID update sequence error. One or more interface schedules could have been affected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-3-PROXY_SID_UPDATE_LOCK_ERROR : QFP MLP Proxy ([chars]) Multiple SID Update Locks to same interface (Interface [chars], SID: [hex])
Explanation Cisco internal software error. QFP MLP Proxy message processing detected a Bundle Schedule SID update sequence error. One or more interface schedules could have been affected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-4-PROXY_IPC_ALLOC_FAIL2 : QFP MLP Proxy ([chars]) response lost due to buffer allocation failure (Interface [chars])
Explanation Cisco internal software error. QFP MLP Proxy message processing detected a IPC buffer allocation failure during proxy response processing. The associated MLP functionality may not be fully functional as a result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-4-PROXY_SYNC : QFP MLP Proxy ([chars] [chars]) Bundle/Link sync issue with interface [chars]
Explanation Cisco internal software error. QFP MLP Proxy message processing detected a Bundle-Link state synchronization abnormality. This condition should be cosmetic. Full context of the message will aid in problem isolation.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-4-TX_BUNDLE_FLOWED_OFF : QFP MLP Tx Bundle [chars] flowed OFF for an abnormal duration due to one or more congested member link(s) (Ticks: [dec])
Explanation Possible Cisco internal software or hardware error. QFP MLP Tx processing detected that a MLP Bundle interface was flowed off for an extended period of time due to a congested member link queue. The associated MLP Bundle interface may not be fully functional as a result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-4-TX_BUNDLE_FLOWED_ON : QFP MLP Tx Bundle [chars] flowed ON after being flowed OFF for an abnormal duration (Ticks: [dec])
Explanation Possible Cisco internal software or hardware error. QFP MLP Tx processing detected that a MLP Bundle interface was flowed off for an extended period of time due to a congested member link queue. The associated MLP Bundle interface may not be fully functional as a result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-4-TX_BUNDLE_LOOP : QFP detected re-entry into MLP Tx Bundle [chars])., MSGDEF_LIMIT_SLOW
Explanation Possible software configuration error in the network that causes re-entry of packets into the MLP Tx bundle. Packets are being discarded and the bundle will not be fully operational until the loop is terminated
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-2-BQS_SCRATCH_TOOSMALL : QFP BQS Scratch area too small for MLP feature usage (size: [dec], need: [dec]).
Explanation Cisco internal software error. QFP MLP initialization detected that the BQS scratch memory area is insufficient for MLP usage. The MLP Bundle interfaces 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-2-PROXY_IPC_INIT_FAILED : QFP MLP Proxy IPC interface initialization failure (result: [dec]).
Explanation Cisco internal software error. QFP MLP initialization detected that the Proxy IPC interface initialization failed. The MLP Bundle interfaces 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-3-EARLY_RX_CLEANUP : QFP MLP Early Receive cleanup error ([chars])
Explanation Cisco internal software error. Multilink Early Receive cleanup could not be performed due to indicated error. This could cause possible QFP memory leak.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-3-EARLY_RX_INIT : QFP MLP Early Receive initialization error ([chars])
Explanation Cisco internal software error. Multilink Early Receive initialization could not be performed due to indicated error. This could cause possible lost MLP encapsulated packets during member link/bundle bringup and possibly cause the failure to complete member link/bundle initialization.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-3-INV_PROXY_MSG : QFP MLP Proxy received invalid Message ID [dec]
Explanation Cisco internal software error. QFP MLP Proxy received an invalid Message ID. This message will be ignored.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-3-MCMP_INVALID_RX_CLASS : MLP MCMP suspension class ID ([dec]) received from the peer must be less than the number of negotiated classes ([dec]) for interface [chars] (Peer error), MSGDEF_LIMIT_SLOW
Explanation Possible error on the peer device with PPP Multilink Multiclass (MCMP). Received MLP packet contained a MCMP suspension class ID greater than the number of negotiated suspension classes.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-3-MCMP_TX_ENCAP_SEQ_CFG_ERROR : MLP QoS encap-sequence ([dec]) must be less than the number of MCMP suspension classes ([dec]) for output interface [chars], MSGDEF_LIMIT_SLOW
Explanation User software configuration mismatch with PPP Multilink Multiclass (MCMP). User needs to either reduce the highest encap-sequence in the policy-map to be less than the number of negotiated MCMP suspension classes or increase the number of suspension classes negotiated with the peer.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-3-MLP_INVALID_EVSI_INTF_STATE : MLP Link Add/Update receved with invalid EVSI indication for Member Link: [chars], Bundle: [chars]
Explanation Either the user attempted to mix broadband and non-broadband member links on the same bundle or an internal error has occurred processing a configuration update.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-3-PROXY_B_TX_IDLE_LINK_TRANSITION : QFP MLP Proxy ([chars] [chars]) invalid Bundle state [chars] ([dec]) for interface [chars]/[chars]
Explanation Cisco internal software error. Multilink Idle-Link transition could not be made due invalid Bundle state at the time of the request. The associated MLP Bundle interface may not be fully functional as a result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-3-PROXY_DUP_LINK_ID : QFP MLP Proxy ([chars] [chars]) duplicate Link ID [dec] for interface [chars] and [chars]
Explanation Cisco internal software error. QFP MLP Proxy message Link Add could not be processed for the indicated interface due use of a given Link ID on multiple member links within the same MLP Bundle. The associated MLP Bundle interface may not be fully functional as a result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-3-PROXY_INV_BUFFER_LIMIT : QFP MLP Proxy ([chars] [chars]) indicated an invalid Rx buffer limit ([dec]) for interface [chars]
Explanation Cisco internal software error. QFP MLP was provided a invalid Rx buffer limit value. The associated MLP Bundle interface may not be fully functional as a result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-3-PROXY_INV_BUNDLE_STATE : QFP MLP Proxy ([chars] [chars]) invalid Bundle state [chars] ([dec]) for interface [chars]
Explanation Cisco internal software error. QFP MLP Proxy message could not be processed due to the MLP Bundle being in an incorrect state to accept the message. The associated MLP Bundle interface may not be fully functional as a result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-3-PROXY_INV_CLASS_INFO : QFP MLP Proxy ([chars] [chars]) invalid Class Info (Base: [hex], Num: [dec]) for interface [chars]
Explanation Cisco internal software error. QFP MLP Proxy message contained invalid MLP Class information. The associated MLP Bundle interface may not be fully functional as a result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-3-PROXY_INV_LINK_ID : QFP MLP Proxy ([chars] [chars]) invalid Link ID [dec] for interface [chars]
Explanation Cisco internal software error. QFP MLP Proxy message Link Add could not be processed for the indicated interface due to an invalid Link ID. The associated MLP Bundle interface may not be fully functional as a result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-3-PROXY_INV_LINK_STATE : QFP MLP Proxy ([chars] [chars]) invalid Link state [chars] ([dec]) for interface [chars]
Explanation Cisco internal software error. QFP MLP Proxy message could not be processed due to the MLP Link being in an incorrect state to accept the message. The associated MLP Bundle interface may not be fully functional as a result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-3-PROXY_INV_LOST_FRAG_TO : QFP MLP Proxy ([chars] [chars]) indicated an invalid lost fragment timeout ([dec]) for interface [chars]
Explanation Cisco internal software error. QFP MLP was provided a invalid lost fragment timeout value. The associated MLP Bundle interface may not be fully functional as a result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-3-PROXY_INV_MRRU : QFP MLP Proxy ([chars] [chars]) invalid MRRU [dec] for interface [chars]
Explanation Cisco internal software error. QFP MLP Proxy message contained an invalid MLP Bundle MRRU. The associated MLP Bundle interface may not be fully functional as a result of this condition. Possible workaround is to reduce the interface mtu on the Multilink bundle interface on both ends of the connection to 9216 or less and then shut/no shut the Multilink bundle interface to force renegotiation of the MLP MRRU.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-3-PROXY_INV_RX_TX_INTF_VALUE : QFP MLP Proxy ([chars] [chars]) invalid Rx/Tx interface value [dec] for interface [dec] (handle)
Explanation Cisco internal software error. QFP MLP Proxy was unable to complete the requested MLP Bundle state change or configuration update due to an invalid interface Rx/Tx designation in the proxy request. The associated MLP Bundle interface may not be fully functional as a result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-3-PROXY_INV_SUB_DEV_ID : QFP MLP Proxy ([chars] [chars]) invalid Sub-Device ID [dec] for interface [chars]
Explanation Cisco internal software error. QFP MLP Proxy message Bundle Add could not be processed for the indicated interface due to an invalid Sub-Device ID. The associated MLP Bundle interface may not be fully functional as a result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-3-PROXY_INV_TX_LINK_FRAG_SIZE : QFP MLP Proxy ([chars] [chars]) indicated an invalid Tx Link optimal fragment size ([dec]) for interface [chars]
Explanation Cisco internal software error. QFP MLP Proxy message contained invalid Tx Link optimal fragment size information. The associated MLP Member Link and/or Bundle interface may not be fully functional as a result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-3-PROXY_INV_TX_LINK_WEIGHT : QFP MLP Proxy ([chars] [chars]) indicated an invalid Tx Link weight ([dec]) for interface [chars]
Explanation Cisco internal software error. QFP MLP Proxy message contained invalid Tx Link weight information. The associated MLP Member Link and/or Bundle interface may not be fully functional as a result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-3-PROXY_IPC_ALLOC_FAIL : QFP MLP Proxy ([chars]) response lost due to buffer allocation failure (Interface [chars])
Explanation Cisco internal software error. QFP MLP Proxy message processing detected a IPC buffer allocation failure during response processing. The associated MLP interface may not be fully functional as a result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-3-PROXY_LAI_TX_IDLE_LINK_TRANSITION : QFP MLP Proxy ([chars] [chars]) invalid Link state [chars] ([dec]) for interface [chars]/[chars]
Explanation Cisco internal software error. Multilink Idle-Link transition could not be made due invalid Link state at the time of the request to convert the link to an Idle-Link. The associated MLP Bundle interface may not be fully functional as a result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-3-PROXY_LIA_TX_IDLE_LINK_TRANSITION : QFP MLP Proxy ([chars] [chars]) invalid Link state [chars] ([dec]) for interface [chars]/[chars]
Explanation Cisco internal software error. Multilink Idle-Link transition could not be made due invalid Link state at the time of the request to convert the Idle-Link to an active link. The associated MLP Bundle interface may not be fully functional as a result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-3-PROXY_NULL_BUNDLE : QFP MLP Proxy ([chars] [chars]) NULL Bundle sub-block for interface [dec] (handle)
Explanation Cisco internal software error. QFP MLP Proxy was unable to complete the requested MLP Bundle state change or configuration update due to an invalid or uninitialized Bundle sub-block. The associated MLP Bundle interface may not be fully functional as a result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-3-PROXY_NULL_LINK : QFP MLP Proxy ([chars] [chars]) NULL Member Link sub-block for interface [dec] (handle)
Explanation Cisco internal software error. QFP MLP Proxy was unable to complete the requested MLP Member Link state change or configuration update due to an invalid or uninitialized Member Link sub-block. The associated MLP Member Link interface may not be fully functional as a result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-3-PROXY_SID_UPDATE_COMPLETE_ERROR : QFP MLP Proxy ([chars]) SID Update Complete w/o Preceeding Lock (Interface [chars], SID: [hex])
Explanation Cisco internal software error. QFP MLP Proxy message processing detected a Bundle Schedule SID update sequence error. One or more interface schedules could have been affected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-3-PROXY_SID_UPDATE_LOCK_ERROR : QFP MLP Proxy ([chars]) Multiple SID Update Locks to same interface (Interface [chars], SID: [hex])
Explanation Cisco internal software error. QFP MLP Proxy message processing detected a Bundle Schedule SID update sequence error. One or more interface schedules could have been affected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-4-PROXY_IPC_ALLOC_FAIL2 : QFP MLP Proxy ([chars]) response lost due to buffer allocation failure (Interface [chars])
Explanation Cisco internal software error. QFP MLP Proxy message processing detected a IPC buffer allocation failure during proxy response processing. The associated MLP functionality may not be fully functional as a result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-4-PROXY_SYNC : QFP MLP Proxy ([chars] [chars]) Bundle/Link sync issue with interface [chars]
Explanation Cisco internal software error. QFP MLP Proxy message processing detected a Bundle-Link state synchronization abnormality. This condition should be cosmetic. Full context of the message will aid in problem isolation.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-4-TX_BUNDLE_FLOWED_OFF : QFP MLP Tx Bundle [chars] flowed OFF for an abnormal duration due to one or more congested member link(s) (Ticks: [dec])
Explanation Possible Cisco internal software or hardware error. QFP MLP Tx processing detected that a MLP Bundle interface was flowed off for an extended period of time due to a congested member link queue. The associated MLP Bundle interface may not be fully functional as a result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-4-TX_BUNDLE_FLOWED_ON : QFP MLP Tx Bundle [chars] flowed ON after being flowed OFF for an abnormal duration (Ticks: [dec])
Explanation Possible Cisco internal software or hardware error. QFP MLP Tx processing detected that a MLP Bundle interface was flowed off for an extended period of time due to a congested member link queue. The associated MLP Bundle interface may not be fully functional as a result of this condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QFP_MLP-4-TX_BUNDLE_LOOP : QFP detected re-entry into MLP Tx Bundle [chars])., MSGDEF_LIMIT_SLOW
Explanation Possible software configuration error in the network that causes re-entry of packets into the MLP Tx bundle. Packets are being discarded and the bundle will not be fully operational until the loop is terminated
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
QLLC
%QLLC-3-BADOPCODE : Opcode [chars] is invalid
Explanation Either remote source-route bridging or local acknowledgment is configured incorrectly.
Recommended Action Verify that remote source-route bridging and local acknowledgment are configured correctly.
%QLLC-3-BADQLLCSTATE : Bad qllc state -[chars]
Explanation An invalid QLLC primitive was detected.
Recommended Action Verify that the partner QLLC device is configured correctly.
%QLLC-3-BADRSRBOPCODE : Bad opcode [hex] from [enet] to [enet]
Explanation Either remote source-route bridging is incorrectly configured, or the other RSRB device is down.
Recommended Action Verify that remote source-route bridging is configured correctly with the right version of the IOS software.
%QLLC-3-BADSTATE : Bad qllc state -[chars] -[enet]
Explanation An invalid LLC primitive was detected.
Recommended Action Verify that the Token Ring ports and any participating LAN devices are configured correctly.
%QLLC-3-BADSTATEEVENT : Bad qllc state -[chars] event -[chars] macaddr -[enet]
Explanation The LLC primitive specified placed the router in an invalid state.
Recommended Action Verify that the Token Ring ports and any participating LAN devices are configured correctly.
%QLLC-3-BAD_XID : Sna configuration error for [enet]: Lan device is PU2.1, X.25 device is PU2.0 (XID Format 1)
Explanation The IBM Gateway (3172) or front-end processor on the LAN is sending XID Format 3 which is used to communicate with PU2.1 devices. The X.25 device is a PU2.0 (3174) that is configured to send XID Format 1 messages. This is a very rare situation - for example, Revision A5.6 on, and C5.1 on the 3172. A likely cause is that the revision levels on the IBM equipment are incompatible.
Recommended Action Check the revision levels on the external equipment, and upgrade them if necessary.
%QLLC-3-DIFFPRTR : [enet] -Different partner -originally [enet] -now [enet]
Explanation The partner for this QLLC virtual MAC address does not match the MAC address that was defined with the qllc partner command.
Recommended Action Verify that the qllc partner statement in the configuration file is correct.
%QLLC-3-GENERRMSG : [chars]
Explanation The text string provided with this error message describes the specific QLLC problem.
Recommended Action Follow the instructions that appear with the error message. Copy the error message exactly as it appears, and report it to your technical support representative.
%QLLC-3-IFRAME : [chars]
Explanation An I-Frame was discarded due to network congestion.
Recommended Action Verify that the LAN is not beaconing and that it is not in a congested state. Copy the error message exactly as it appears, and report it to your technical support representative.
%QLLC-3-INCALL_CFG : Incoming call: No QLLC Service Access Point Configured for x.25 subaddress [chars]
Explanation A remote X.25 device is calling the router for QLLC service using a subaddress that was not configured by the X.25 routing facility. The subaddress was not configured for QLLC service.
Recommended Action Correct the QLLC configuration. Configure only the subaddress on the QLLC service, not the complete X.121 address that the remote X.25 device uses.
%QLLC-3-INCALL_NO_PARTNER : Incoming call: No partner Mac Address configured -X.25 subaddress [chars]
Explanation There is an incoming call, but a connection cannot be initiated to a partner since no partner is configured in a qllc dlsw command (for QLLC/DLSw+ only).
Recommended Action Configure a partner for the incoming calling (such as using the qllc dlsw partner command).
%QLLC-3-LNXNOTFOUND : lnx_remove_macaddr_hash did not find target lnx
Explanation The qllc srb command was not defined for this interface.
Recommended Action Add a valid qllc srb statement for this serial interface.
%QLLC-3-NOLLC2 : Unable to open an llc2 session
Explanation An LLC2 session could not be established with the destination MAC address.
Recommended Action Verify that the qllc partner statement in the configuration file is correct, and that the partner is on the desired LAN.
%QLLC-3-NOMACADDR : No lnx entry for macaddr [enet]
Explanation No virtual MAC address was defined for this interface.
Recommended Action Define the virtual MAC address, using either the x25 map qllc or the x25 pvc qllc command.
%QLLC-3-NOMEM : Not enough memory available
Explanation There is not enough memory in the system to complete this request.
Recommended Action Add more memory to the router. Otherwise, reduce the configuration or the load on the router.
%QLLC-3-NONULLXID : Couldn't make null xid -[enet] -[enet]
Explanation An attempt to create an IEEE XID failed.
Recommended Action Verify that the qllc partner statement in the configuration file is correct, and that the partner is on the desired LAN.
%QLLC-3-NOPAKENQ : Pak enqueue failed
Explanation A packet was not sent to the LAN.
Recommended Action Verify that the LAN partner is configured correctly, and that the partner is on the desired LAN.
%QLLC-3-NO_QLLCBUFFER : M bit Reassembly failed -couldn't allocate a packet
Explanation The router ran out of memory to allocate buffers.
Recommended Action Make sure that the router configuration is adequate for the service expected of it. You might want to tune the buffer pools, or upgrade to a larger router. At the very least, you will need more memory.
%QLLC-3-NO_QSR : No QLLC Service Access Points defined
Explanation No QLLC services have been configured, even though the router will accept incoming calls for QLLC.
Recommended Action Configure the QLLC service required.
%QLLC-3-NO_RESOURCE : Incoming Call: Insufficient resources available
Explanation This message is reporting insufficient system memory.
Recommended Action Upgrade the memory.
%QLLC-3-NOXID2 : Couldn't make xid -[enet] -[enet]
Explanation The QLLC XID could not be forwarded to the LAN.
Recommended Action Verify that the qllc partner and the qllc xid commands are correct.
%QLLC-3-NULLPTR : [chars] ptr is null
Explanation The specified structure was not configured.
Recommended Action Confirm the configuration commands for the structure.
%QLLC-3-PARTNER_MISMATCH : Outgoing call: Partner Mac Address [enet] doesn't match configured partner [enet]
Explanation A device tried to connect to a QLLC VMAC (from Token Ring, for instance), but the MAC address of that device does not match the partner in the qllc dlsw command.
Recommended Action Correct the QLLC configuration to match the right partner.
%QLLC-3-QLLCMAP_ERR : Incoming call: QLLC map entry not found
Explanation A software error in the router code occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%QLLC-4-NOQLLC : Unable to open qllc session, current state is [chars]
Explanation A QLLC session could not be established.
Recommended Action Verify that the qllc partner and the qllc xid commands are correct.
QOS
%QOS-3-ATLEAST_ONE_FAILOVER_ERR : Fail-over of dynamic interface [chars] failed
Explanation Dynamic interface has changed its route out of different physical interface and queueing can not set-up data-sructures for that new physical interface
Recommended Action One possibility is that new physical interface already has service-policy or some other dynamic interface already has queueing data-structures associated with that physical interface and conjuction of such service-policies are not allowed. Remove one or the other service-policy in that case. If that is not the case then contact technical support
%QOS-3-BADXDRSLOT : Invalid XDR slot. Type/len/slot [dec]/[dec]/[chars]. XDR at [hex]
Explanation An internal software error occured
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QOS-3-BLT_INDEX : Failed to assign index for target/policy/class/action [int]/[int]/[int]/[chars]
Explanation The configuration of queuing has resulted in the failure to generate an internal unique identifier which represents the queue. This is an internal software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QOS-3-BURST_BC_ERR : Burst Bc increased to [dec] bytes
Explanation If Burst BC is less than the default burst size then Burst Bc is increased to AF_DEAFULT_BURST
Recommended Action This is informational message. No action is required
%QOS-3-CFGERR : interface [chars]: configuration failed
Explanation Enough memory is not available to configure feature
Recommended Action It is not possible to configure issued command (feature) unless required memory is released by some other means
%QOS-3-COEX_NOT_ALLWD : queueing policy at session cannot co-exist with service policy at sub-interface/pvc
Explanation There already may be user-defined flat policy or hierarchical policy at the sub-interface/pvc. With existing of such policy no queueing policy is allowed on session
Recommended Action Remove the policy attached to the sub-interface/pvc before attaching a new policy to a session
%QOS-3-COLLISION_COUNT : [chars] mismatch, count [int]
Explanation The specified type of collision has detected that although there are no collisions present the count of such indicates otherwise. This is an internal software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QOS-3-COLLISION_DELETE : [chars] unable to remove index [hex]
Explanation The specified type of collision is unable to removed the specified index. This is an internal software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QOS-3-COLLISION_TYPE : Type [int] is invalid for collision [chars]
Explanation The specified type of collision is an invalid value which indicates that there is no support for the generation of an internal identifier. This is an internal software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QOS-3-HA_BULK_SYNC : [chars] Failure in completing bulk sync
Explanation QoS configuration can't be synced to the standby
Recommended Action Contact your Cisco technical support representative.
%QOS-3-HA_BULK_SYNC_BEFORE_TIMEOUT : [chars] Failure in completing bulk sync before timeout
Explanation QoS configuration can't be synced to the standby The interface bandwidth is more than the total bandwidth that is required for QoS policy on this interface.
Recommended Action Contact your Cisco technical support representative. There is no user action required.
%QOS-3-HA_COLLISION_INVALID : Received collision table of type [int]
Explanation The specified type of collision is an invalid value which indicates that the message received on the standby RP contains erroneous data. This is an internal software error which should result in a reload of the standby RP so that the bulk sync of configuration can be sent once more by the active RP.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QOS-3-HA_COLLISION_SIZE : Received [chars] message, total/unit [int]/[int] [chars]
Explanation The specified type of collision table has been determined to contain a discrepancy between the total message size and the individual table unit that is being decoded on the standby RP. This is an internal software error which should result in a reload of the standby RP so that the bulk sync of configuration can be sent once more by the active RP.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QOS-3-HA_COLLISION_STRING : Received [chars] message, length [int] for string [chars]
Explanation The specified type of collision table contains an individual unit within the message which has an incorrectly encoded string which is used to represent the collision which is being synced from the active RP. This is an internal software error which should result in a reload of the standby RP so that the bulk sync of configuration can be sent once more by the active RP.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QOS-3-HA_GET_ARG_NUM : [chars] Failure in getting event identification
Explanation QoS configuration can't be synced to the standby
Recommended Action Contact your Cisco technical support representative.
%QOS-3-HA_MISMATCH : Bulk sync failed for [chars] collisions, space available [int], buffer [int]
Explanation A synchronization attempt between the active and standby RP peers has failed due to the detection of a mismatch in the source and destination sizes of a buffer used in the transport of the collision information to the standby RP. This is an internal software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QOS-3-HQF_FEA_API_FAIL : Feature processing API returned NULL pak with INCOMPLETE flag
Explanation HQF calls feature processing API to get the next packet from the feature, for example Frame-relay fragmentation. The API returns conflicting flags with NULL packet.
Recommended Action Check if the system resources, e.g. packet buffers, are exhausted. Contact technical support
%QOS-3-HQFNOPAK : interface [chars]: pak_reparent failed
Explanation pak_reparent has been invoked and failed.
Recommended Action Collect show buffer and show policy interface output and send to technical support
%QOS-3-HQFPAKREQUEUE : interface [chars]: pak_requeue_head has been invoked
Explanation pak_requeue_head() function has been invoked on a packet. One or more packets have been dropped. This is not the normal mode of operation
Recommended Action Collect show buffer and show policy interface output and send to technical support
%QOS-3-HQFPOOLERR : interface [chars]: failed to allocate hqf particle
Explanation The HQF particle pool is empty. It cannot process a router generated packet
Recommended Action Collect show buffer and show policy interface output and send to technical support
%QOS-3-HQF_QID_ERR : Maximum number of QoS queues ([dec]) reached.
Explanation The system has run out of QoS queue identifiers and cannot allocate any more until existing queues are freed up.
Recommended Action Existing QoS configurations will need to be removed to free up more queue identifiers. For example, remove existing QoS service-policy configurations or modify policy-map templates to have fewer queueing actions.
%QOS-3-INDEX_DELETE : [chars] unable to remove index [hex]
Explanation The specified entity is unable to removed the specified index. This is an internal software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QOS-3-INDEX_EXISTS : [chars] attempt to add index [hex] [chars]
Explanation The specified entity is unable to add an entry due to the detection of an existing entry with the same index or name. This is an internal software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show cce cp id [collisions] command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%QOS-3-INVALID_POLICY : queueing policy at session/tunnel can co-exist only with class-default shaping policy at sub-interface/pvc
Explanation There already may be user-defined flat policy or hierarchical policy at the sub-interface/pvc. With existing of such policy no queueing policy is allowed on session
Recommended Action Make sub-interface/pvc based policy just one level policy with only class-default
%QOS-3-ISSU_COMP : Failed to exchange capability with peer
Explanation The attempt to negotiate version capabilities and the exhange of the peer support has failed. This indicates that QoS is unable to support a redundant operation with the standby RP peer.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QOS-3-MAIN_SUB_POLICY : FR fragmentation is not supported with interface or sub-interface based policies
Explanation On Cisco 7500 series routers, Frame Relay fragmentation is not supported when service policies are configured on the interface or subinterfaces.
Recommended Action Remove the service policy configuration under the interface or subinterfaces and reissue either the class command from Frame-Relay DLCI interface configuration mode or the frame-relay fragment command from map-class configuration mode.
%QOS-3-MULTIPLE_INTERFACES : Load-sharing mode has changed. Queuing functionality may not be supported after this.
Explanation Dynamic interface has changed its route out of different physical interface. It might resolve into multiple interfaces for queuing. HQF functionality will get affected.
Recommended Action Likely scanario is that CEF is returning multiple paths across different interfaces. For those tunnels which has queuing features need unique out-going interface to resolve queuing hierarchy. Common instance is per-prefix load-balancing to per-destination. Need to remove offending configurations. May also need reload to get the queuing in working state
%QOS-3-SA_SESSION_FAILOVER_ERR : Fail-over of dynamic SA session to interface [chars] failed
Explanation Dynamic SA session has changed its route out of different physical interface and queueing can not set-up data-sructures for that new physical interface
Recommended Action One possibility is that new physical interface already has service-policy with queueing configured Remove the other service-policy in that case. If that is not the case then contact technical support
%QOS-3-VTEMP_MAIN_ERR : Attaching a service policy to a PPP/PPPoE virtual-access interface is not allowed when another policy is already attached to the main interface to which the PPP/PPPoE virtual-access interface is bound.
Explanation Attaching a service policy to a PPP/PPPoE virtual-access interface is not allowed when another policy is already attached to the main interface to which the PPP/PPPoE virtual-access interface is bound.
Recommended Action Remove the policy attached to the main interface before attaching a new policy to a PPP/PPPoE virtual-access interface
%QOS-3-VTEMP_MLP_ERR : A service policy cannot be attached to a PPP virtual-access interface when ppp multilink is enabled. A service policy can be attached to a ppp multilink bundle interface only.
Explanation A service policy attached to a virtual-template is usually copied to associated virtual-access interfaces. However, if such a virtual-access interface joins a multilink ppp bundle, the policy is not attached to the virtual-access interface.
Recommended Action This is informational message. No action is required
%QOS-3-VTEMP_SUB_ERR : Attaching a service policy to a PPP/PPPoE virtual-access interface is not allowed when another policy is already attached to the subinterface to which the PPP/PPPoE virtual-access interface is bound.
Explanation Attaching a service policy to a PPP/PPPoE virtual-access interface is not allowed when another policy is already attached to the subinterface to which the PPP/PPPoE virtual-access interface is bound.
Recommended Action Remove the policy attached to the subinterface before attaching a new policy to a PPP/PPPoE virtual-access interface
%QOS-3-VTEMP_VC_ERR : Attaching a service policy to a PPP/PPPoE virtual-access interface is not allowed when another policy is already attached to the vc/pvc to which the PPP/PPPoE virtual-access interface is bound.
Explanation Attaching a service policy to a PPP/PPPoE virtual-access interface is not allowed when another policy is already attached to the vc/pvc to which the PPP/PPPoE virtual-access interface is bound.
Recommended Action Remove the policy attached to the vc/pvc before attaching a new policy to a PPP/PPPoE virtual-access interface
%QOS-3-XDRLEN : Invalid XDR length. Type [dec][chars]. XDR/buffer len [dec]/[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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QOS-4-DYN_SUSPEND : Queueing hierarchy move failed on [chars], suspending policy.
Explanation A forwarding path change has moved the given queue to a new port where its QoS queuing policy cannot be satisfied. This is likely due to a conflicting policy or insufficient bandwidth on the new port, or simply that a new port has not yet been calculated. The policy has thus been temporarily suspended.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QOS-4-FO_IN_USE : Releasing feature object with reference count [dec]
Explanation This is an internal software error. A QoS policy feature object has a stale reference.
Recommended Action If the message recurs, try to isolate the traffic conditions which trigger the message and contact technical support. Provide the output from the show tech-support and show policy-map interface commands.
%QOS-4-HQUEUE_QLIMIT_VALUE_SYNC_ISSUE : The hold-queue value is less than the sum of queue-limit values.
Explanation The hold-queue value is less than the queue-limit configured. This will lead to no-buffer drops instead of tail drops
Recommended Action The hold-queue value should be properly adjusted to prevent no-buffer drops.
%QOS-4-INVALIDBW : interface [chars]: Not enough bandwidth to configure service-policy
Explanation The issued interface bandwidth is less than the total bandwidth that is required for QoS policy on this interface.
Recommended Action Reconfigure the service policy for the new issued bandwidth on the interface, or increase the issued interface bandwidth to the required value. There is no user action required.
%QOS-4-LC_STATS_MSG_DROPPED : QoS statistics update message dropped due to [chars]
Explanation Changes to QoS counters are sent periodically from linecards to the route processor. One of these statistics update messages was discarded because it was inconsistent or because the route processor ran out of message buffers. The packet and bytes counters for a single service-policy may be underreported by show commands and SNMP queries.
Recommended Action This is an informational message only. No action is required.
%QOS-4-QLIMIT_HQUEUE_VALUE_SYNC_ISSUE : The sum of all queue-limit value is greater than the hold-queue value.
Explanation The hold-queue value is less than the queue-limit configured. This will lead to no-buffer drops instead of tail drops
Recommended Action The hold-queue value should be properly adjusted to prevent no-buffer drops.
%QOS-4-WRED_QLIMIT_OUT_OF_SYNC : On interface [chars] user-defined wred max threshold higher than default queue-limit
Explanation The user defined random-detect is greater that the default queue-limit for this interface. Some of the random-detect configurations will not function properly due to this anomaly.
Recommended Action If the random-detect value is configured greater than default queue-limit intentionally then keep it as it is else please investigate and use a random-detect value(s) that will be lower than the default queue-limit.
%QOS-6-ACTIVATE : Activating service policy [chars] on [chars] in [chars] direction
Explanation The interface bandwidth is more than the total bandwidth that is required for QoS policy on this interface.
Recommended Action There is no user action required.
%QOS-6-ACTIVATE_NOHW : Activating service policy [chars] in [chars] direction
Explanation None
Recommended Action None
%QOS-6-ADAPTIVE_QOS_DISABLED : Adaptive QoS functionality is disabled. Shaper is reset to upper-bound
Explanation Multiple and consecutive reports from peer are not received. This leads to an assumption that the peer has gone away.
Recommended Action Removal and re-application of policy may be required to re-enable the adaptive QoS functionality
%QOS-6-COLLISION_MAX : Maximum number of collision entries, [int], reached
Explanation The system limit on the number of collision entries used in assigning unique identifiers for policy and class maps et al. has been reached. This indicates that no further configuration of entities which require additional generation of a unique identifier will be possible.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QOS-6-DYN_INSTALL : Installing suspended policy on [chars].
Explanation IOS is restoring a previously suspended policy.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QOS-6-EXTENDED_BURST_CHANGED_WARN : Illegal extended burst size; it is increased to [int]
Explanation Configured extended burst size is less than the Rate. It is considered to be illegal and has been reset based on the Rate.
Recommended Action This is an informational message only. No action is required.
%QOS-6-NON_AGG_WRED : ATM SPA doesn't support true non-aggregate WRED. All non-specified dscp/prec values will be aggregated in default WRED profile
Explanation ATM SPA has limited hardware capability which is not enough to support traditional WRED. ATM SPA would support 'limited' non-aggregate WRED for the specified dscp/prec values (maximum of 6) and the rest non-specified dscp/prec colors will go to default WRED profile.
Recommended Action There is no user action required.
%QOS-6-NORMAL_BURST_CHANGED_WARN : Illegal normal burst size; it is increased to [int]
Explanation Configured normal burst size is less than the Rate. It is considered to be illegal and has been reset based on the Rate.
Recommended Action This is an informational message only. No action is required.
%QOS-6-RADIO_MULTI_REM : Remove [chars] policy before removing policy from ([chars])
Explanation Prevent the removal of policies from radio layer if child targets have any queuing policies.
Recommended Action This is an informational message only. No action is required.
%QOS-6-RELOAD : [chars], reloading [chars]
Explanation A synchronization attempt between the active and standby RP peers has failed with the reason indicated. The standby peer is reloaded in an attempt to resynchronize when operating in a stateful redundant mode.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QOS-3-DETACH : Failed to detach [chars] [chars] service policy
Explanation The specified type of service policy has failed to detach itself from the attachment point indicated. The service policy will remain attached although repeated attempts to remove such should fail in a similar manner.
Recommended Action LOG_STD_SH_CMD_ACTION(show policy-map [type] <attachment point>)
%QOS-3-ISSU_GTP_CFG_ENHANCE : GTP-AIC configuration has been detected, which is totally different with peer. Delete all GTP-AIC related config to proceed with ISSU/ISSD. After ISSU/ISSD done, config GTP-AIC again.
Explanation PEER GTP-AIC configuration would be messed up.
Recommended Action Manually remove all GTP-AIC configuration and reinitiate ISSU/ISSD.
%QOS-3-TARGET_INDEX : [chars] [chars] service policy attachment failed to assign index
Explanation The configuration of a service policy has resulted in the failure to generate an internal unique identifier which represents the attachment point (target) of the associated policy map. This is an internal software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QOS-3-UNASSIGNED : A [chars] event resulted in an (un)assigned index for [chars] [chars]
Explanation The configuration of either the addition or removal of the specified entity has resulted in the failure to either assign or remove a previously assigned index from such. This is an internal software error and indicates an out of sync condition if operating in a redundant manner
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%QOS-4-SERV_FRAG_POLICY : service-policy [chars] can't be attached without corresponding service-fragment policy on appropriate target first
Explanation For a fragment policy that is being installed check if parent targets have relevant service-fragment class installed. If not then we can not allow fragment policy installation.
Recommended Action Check the parent target to add relevant service-fragment class.
%QOS-6-POLICY_INST_FAILED : Service policy installation failed on [chars] policy:[chars], dir:[chars], ptype:[chars], ctype:[chars]
Explanation Service policy could not be installed
Recommended Action This is an informational message only. No action is required.
%QOS-6-POLICY_REM_FAILED : Service policy remove failed on [chars] policy:[chars], dir:[chars], ptype:[chars], ctype:[chars]
Explanation Service policy could not be removed
Recommended Action This is an informational message only. No action is required.
%QOS-6-SUSPEND : Suspending service policy [chars] on [chars] in [chars] direction
Explanation The interface bandwidth is less than the total bandwidth that is required for QoS policy on this interface.
Recommended Action There is no user action required.
R
RAC
%RAC-3-RACIPL : DHCP is already running on interface [chars]
Explanation The interface already has a DHCP originated address via some other system mechanism
Recommended Action Verify the system configuration
%RAC-3-RACNOIPL : Can not find lease information for interface [chars]
Explanation Internal error - DHCP lease information is missing for the interface
Recommended Action Report the problem and how it can be reproduced to Cisco TAC
%RAC-3-RACNOQ : Can't create RAC work queue
Explanation Internal error - probable cause is insufficient memory resources
Recommended Action Check available memory.
RADIUS
%RADIUS-3-ALLDEADSERVER : Group [chars]: No active radius servers found. Id [dec].
Explanation This error message occurs when all the servers configured in a server group are found to be unresponsive.
Recommended Action Check the network connectivity to the RADIUS servers, and check that the servers are running.
%RADIUS-3-SERVERTYPEMISMATCH : Servers [chars] and [chars] in server group '[chars]' are of different types.
Explanation All the servers in a server group should either be of type standard or non-standard.
Recommended Action Enter show running-config command and make sure all the RADIUS servers in the server group printed above are of the same type - either standard or non-standard.
%RADIUS-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.The given server is not on the global public servers list. This is an internal consistency error
Recommended Action This is an internal software error. Collect the trace-back appeared as a part of message and report it to your technical support representative.Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%RADIUS-3-CANNOT_OPEN_SOCKET : Cannot open UDP socket for service [chars]
Explanation The router is unable to open a socket for UDP communications by the indicated service. Most of the time another service might be using the same port.
Recommended Action Check your configuration to make sure that no other services are using the same port. If not able to debug the issue, enter show running-config and contact your technical support representative for assistance.
%RADIUS-3-CORRUPTCONTEXT : Bad Magic pattern in [chars]:[hex], magic:[hex]!
Explanation The magic pattern imprinted on the internal hash table data structures in RADIUS subsystem is missing and indicates memory corruption. The memory is getting overwritten by a misbehaving process. The traceback and the process information is generated to the result of the error.
Recommended Action Check bug toolkit on Cisco web-site to look for a bug that has symptoms similar to the one occured. If there is no entry for the problem you faced, collect the system message text exactly as it appears on the console or in the system log. Enter show tech-support command, contact your technical support representative and provide the representative with the gathered information.
%RADIUS-3-DATAERROR : Warning: [chars]
Explanation The given data passed into the Radius subsystem is considered invalid and may result in loss of attributes.
Recommended Action Please collect traceback and contact your technical support representative.
%RADIUS-3-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, enter show tech-support command and call your technical support representative for assistance.
%RADIUS-3-FORMATLONG : Format string too long.Maximum allowed length is [dec].
Explanation The user is attempting to configure a format string with a prefix that is too long.
Recommended Action Enter a shorter string to configure.
%RADIUS-3-IDENTFAIL : Saving of unique accounting ident aborted. Configuration has been modified.
Explanation The configuration has been modified. We can not save the unique accounting IDENT to nvram. The message is to inform the user that the saving of unique accounting ident is aborted due to the change in configuration.
Recommended Action Save the configuration and try again. If the error persists, Enter show tech-support contact your Cisco technical support representative, and provide the representative with the gathered information for assistance.
%RADIUS-3-INVALIDFORMAT : Invalid Nas Port Format: [chars] %c
Explanation The user is attempting to configure an incorrect format string.
Recommended Action Enter a 32 character string using supported characters only.
%RADIUS-3-INVALID_PACKET : Invalid packet posted to RADIUS.
Explanation Radius not able to process a packet as it in invalid
Recommended Action No action is required.
%RADIUS-3-IPV4_FIB_SEND_FAILED : Radius ipv4 send failed due to FIB error. Error code: [dec].
Explanation Radius not able to send udp packets as fib failed
Recommended Action No action is required.
%RADIUS-3-MALLOC_FAILED : Insufficient memory : [chars].
Explanation Memory allocation failed due to insufficient memory
Recommended Action No action is required.
%RADIUS-3-NOACCOUNTINGRESPONSE : Accounting message [chars] for session %*s failed to receive Accounting Response.
Explanation Maximum number of retransmissions is exceeded. The network is not accessible or the RADIUS server is down.
Recommended Action Check the network connectivity to the RADIUS servers, and check that the servers are running. If not able to debug the issue, enter show running-config and contact your technical support representative for assistance.
%RADIUS-3-NOATTRLIST : No attribute-list passed through parser.
Explanation An internal error has occurred. The reason could be hardware or software. The error appears when no attribute list is passed through the parser.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%RADIUS-3-NOHOSTNAME : Failed to retrieve my hostname.
Explanation Could not find the router's hostname. A hostname needs to be defined, since it determines the RADIUS profile we will retrieve.
Recommended Action Define a hostname on the router's config. Refer to the hostname configuration section of IOS documentation.
%RADIUS-3-NOSERVERS : No Radius hosts configured or no valid server present in the server group [chars]
Explanation RADIUS is attempting to send a request, but there are no hosts configured to which the request is send.
Recommended Action Configure a host with the 'radius-server' command providing the IP address of the server. Refer to the radius-server host configuration section of IOS documentation.
%RADIUS-3-OVERRUN : Insufficient buffer space [dec] for string value.
Explanation This error occurs due to the insufficient memory allocated to the buffer. The condition could be caused by a software, less likely by a hardware. The traceback and process information is generated due to this condition.
Recommended Action If the error re-occurs, check bug toolkit on Cisco web-site to look for a bug that has symptoms similar to the one occured. If there is no entry for the problem you faced, collect the system message text exactly as it appears on the console or in the system log. Enter show tech-support, and contact your technical support representative, and provide the representative with all the information gathered.
%RADIUS-3-SECRETDEFINEFAILED : Key definition ignored.
Explanation The user is attempting to store either a corrupted shared secret or memory allocation failed during secret definition. Any existing shared secret will be preserved.
Recommended Action Configure a proper secret. Refer to the shared secret configuration section for RADIUS servers in IOS documentation.
%RADIUS-3-SOURCEPORTALLOCERROR : Warning: Unable to allocate port [dec]
Explanation Unable to allocate a certain port, will not have the full range of source ports. This is not supposed to happen, contact support.
Recommended Action Contact support
%RADIUS-3-UNKNOWNAPI : Unknown API type [dec]
Explanation RADIUS code has been invoked using an unknown API type. This is the result of a bug in the RADIUS subsystem.
Recommended Action Check bug toolkit on Cisco web-site to look for a bug which has symptoms similar to the one occured. If there is no entry for the problem you faced, Please collect traceback and contact your technical support representative.
%RADIUS-3-ZEROATTRLEN : Radius attr [dec] len 0
Explanation An internal error has occurred
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%RADIUS-4-BADATTRLIST : Unable to process attribute list.
Explanation The attribute list is syntactically incorrect.
Recommended Action Please specify the attribute list as a comma- delimited string of integers between 1 and 255.
%RADIUS-4-NOATTRLISTDEF : Warning: Attribute list [chars] is not defined.
Explanation The given attribute list is not defined.
Recommended Action Please define the attribute list as soon as possible.
%RADIUS-4-NOPUBLICSERV : Warning: No servers were found in the public server list.
Explanation The given server is not on the global public servers list. This is an internal consistency error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%RADIUS-4-NOSERV : Warning: Server [chars]:[dec],[dec] is not defined.
Explanation The given server is not globally defined, please define it.
Recommended Action Please define the server. Refer to the server configuration section of IOS documentation.
%RADIUS-4-NOSERVNAME : Warning: Server [chars] is not defined.
Explanation The given server name is not globally defined, please define it.
Recommended Action Please define the server. Refer to the new server name configuration section of IOS documentation.
%RADIUS-4-RADIUS_ALIVE : RADIUS server [chars]:[int],[int] is being marked alive.
Explanation A RADIUS server that previously was not responding has responded to a new request or the deadtimer has expired.
Recommended Action No action is required.
%RADIUS-4-RADIUS_DEAD : RADIUS server [chars]:[int],[int] is not responding.
Explanation The server might not be available to serve request. server has not responded to repeated requests.
Recommended Action Check for the connectivity to server. Check if the RADIUS server is still active. If not able to debug the issue, enter show running-config and contact your technical support representative for assistance.
%RADIUS-4-SERVREF : Warning: Server [chars]:[dec],[dec] is still referenced by server group.
Explanation The server being removed is still referenced by a server group. This message appears when server configuration is removed but in a server group it still exists.
Recommended Action Please dereference the server from the server group as soon as possible. Refer to server group configuration section in IOS documentation.
%RADIUS-4-SERVREFNAME : Warning: Server %S is still referenced by server group.
Explanation The server being removed is still referenced by a server group. This message appears when server configuration is removed but in a server group it still exists.
Recommended Action Please dereference the server from the server group as soon as possible. Refer to server group configuration section in IOS documentation.
%RADIUS-6-GETPOOLS : Retrieving IP-Pools via user [chars]
Explanation Getting initial IP-Pool definitions from RADIUS, using the given user's profile.
Recommended Action No action required.
%RADIUS-6-GETROUTES : Retrieving static routes in user [chars]
Explanation Getting initial static routes from RADIUS, using the given user's profile.
Recommended Action No action required. The message is informatory in nature and tells that it is getting the static routes based on user's profile.
%RADIUS-6-IDENTSAVE : Saving config with new acct ident in nvram.
Explanation Saving an accounting ident in nvram. The message is informatory.
Recommended Action No action required.
%RADIUS-6-RESETDEADSERVER : Group [chars]: Marked alive as Radius server [chars]:[dec],[dec] configured.
Explanation RADIUS server is now configured in the server group which was previously marked dead.
Recommended Action No action required. The message is informatory in nature and tells that the dead server is now configured and up.
%RADIUS-6-SERVERALIVE : Group [chars]: Radius server [chars]:[dec],[dec] is responding again (previously dead).
Explanation A RADIUS server, which previously was dead, has started responding again.
Recommended Action No action required. This message is informatory in nature and tells that the server has come up and running.
RADIX
%RADIX-2-INIT : No memory for radix initialization: [chars]
Explanation The system ran out of memory during initialization. This should only occur if an image is too large for the existing dynamic memory.
Recommended Action Use a smaller subset image or upgrade hardware.
%RADIX-3-ADDMASK : Error adding mask entry, [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.
%RADIX-3-BADTREE : Invalid pointer to head of tree, [hex]
Explanation A software programming error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%RADIX-3-DELETE : Error deleting trie entry, [chars]
Explanation A software programming error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%RADIX-3-NOMEMORY : No memory available [chars]
Explanation The system is out of memory.
Recommended Action Try one of these actions to correct the problem: Reduce the number of routes accepted by this router. Upgrade hardware. Use a smaller subset image on run-from-RAM platforms.
%RADIX-4-ORPHAN : Orphaned mask [hex], refcount=[dec] at [hex], next=[hex]
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
RADPROXY
%RADPROXY-3-INIT : Initialisation failure, [chars]
Explanation An internal error occurred during RP initialisation.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%RADPROXY-3-INVALID_FSM_EVENT : Received invalid RP event [chars] in state [chars]
Explanation An internal RP error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%RADPROXY-3-INVALID_FSM_STATE : Encountered an invalid RP state [dec] in [chars]
Explanation An internal RP error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%RADPROXY-3-INVALID_MAC : Received invalid MAC [chars] in [chars] from [IP_address] with NAS-IP [IP_address]
Explanation Error occurred on receiving a invalid MAC
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%RADPROXY-3-MEMORY_CORRUPT : RP Memory magic corrupted
Explanation RP memory magic corrupted
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%RADPROXY-3-MEMORY_LOW : Memory low in RP, terminating session
Explanation System memory is running low.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%RADPROXY-3-NULL_FSM_CONTEXT : Encountered a NULL RP context in [chars]
Explanation Encountered a NULL context in RP.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%RADPROXY-3-PROTOCOL_VIOLATION : RP encountered fatal protocol violation
Explanation Unrecoverable protocol error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
RCMD
%RCMD-4-RCMDDNSFAIL : DNS hostname/ip address mismatch. [chars] unknown to DNS
Explanation The IP address for an incoming rcmd request is not registered with DNS.
Recommended Action Add the IP address to DNS.
%RCMD-4-RCPATTEMPTED : Remote copy from [chars] at [chars] denied
Explanation An attempt was made to connect to a router through RCP, but the router was not configured as an RCP server.
Recommended Action Configure an RCP server.
%RCMD-4-RSHATTEMPTED : Remote shell from [chars] at [chars] denied
Explanation An attempt was made to connect to a router through rsh, but the router was not configured as an rsh server.
Recommended Action Configure an rsh server.
REDUNDANCY
%REDUNDANCY-3-CONFIG_SYNC : [chars]
Explanation A REDUNDANCY config sync error occurred. The details about what was attempted and what went wrong will be printed.
Recommended Action Copy the error message exactly as it appears. Copy down the system's configuration along with any other relevant information. Contact your technical support representative for assistance.
%REDUNDANCY-3-EHSAISSU : [chars] failed with error code [ [chars] ]
Explanation An ISSU related REDUNDANCY error occurred. The details about what was attempted and what went wrong will be printed.
Recommended Action Copy the error message exactly as it appears. Copy down the system's configuration along with any other relevant information. Contact your technical support representative for assistance.
%REDUNDANCY-3-FSM : [chars]
Explanation A REDUNDANCY Finite State Machine (FSM) error occurred. The details about what was attempted and what went wrong will be printed.
Recommended Action Copy the error message exactly as it appears. Copy down the system's configuration along with any other relevant information. Contact your technical support representative for assistance.
%REDUNDANCY-3-FSM_ERROR : [chars], Error Code: [dec]
Explanation A REDUNDANCY Finite State Machine (FSM) error occurred. The details about what was attempted and what went wrong will be printed.
Recommended Action Copy the error message exactly as it appears. Copy down the system's configuration along with any other relevant information. Contact your technical support representative for assistance.
%REDUNDANCY-3-GENERAL : [chars]
Explanation A REDUNDANCY error occurred. The details about what was attempted and what went wrong will be printed.
Recommended Action Copy the error message exactly as it appears. Copy down the system's configuration along with any other relevant information. Contact your technical support representative for assistance.
%REDUNDANCY-3-IPC : [chars] [chars]
Explanation An Interprocess Communication (IPC) error occurred. The details about what was attempted and what went wrong will be printed.
Recommended Action Copy the error message exactly as it appears. Copy down the system's configuration along with any other relevant information. Contact your technical support representative for assistance.
%REDUNDANCY-3-MEMORY_DIFF : WARNING, nonsymetrical configuration: Active has [dec]K Standby has [dec]K
Explanation The redundant RPs have different memory configurations.
Recommended Action The configuation is allowed but discouraged.
%REDUNDANCY-3-PEER_MONITOR : [chars]
Explanation A REDUNDANCY Peer Monitor error occurred. The details about what was attempted and what went wrong will be printed.
Recommended Action Copy the error message exactly as it appears. Copy down the system's configuration along with any other relevant information. Contact your technical support representative for assistance.
%REDUNDANCY-3-REDUNDANCY_ALARMS : [chars]
Explanation A REDUNDANCY Alarm assertions error occurred. The details about what was attempted and what went wrong will be printed.
Recommended Action Copy the error message exactly as it appears. Copy down the system's configuration along with any other relevant information. Contact your technical support representative for assistance.
%REDUNDANCY-3-STANDBY_LOST : Standby processor fault ([chars])
Explanation The standby processor is no longer available.
Recommended Action Copy the error message exactly as it appears. Copy down the system's configuration along with any other relevant information. Contact your technical support representative for assistance.
%REDUNDANCY-3-SWITCHOVER : RP switchover ([chars])
Explanation A REDUNDANCY switchover has occurred.
Recommended Action Copy the error message exactly as it appears. Copy down the system's configuration along with any other relevant information. Contact your technical support representative for assistance.
%REDUNDANCY-4-PEER_DID_NOT_RESPOND : Resetting peer [chars] because it did not respond to verification of HA role.
Explanation The platform uses the HA hardware lines to perform HA role negotiation at boot time. Whichever controller card becomes the Standby verifies this role via the MBUS with the Active. If the Active does not respond it is reset as it is either hung, or is running an old version of software.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%REDUNDANCY-4-RELOADING_STANDBY : Reloading the Standby [chars]
Explanation The Active has sent a reload IPC request to the Standby peer. If the reload is not successful then the Standby will be power cycled instead.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%REDUNDANCY-5-PEER_MONITOR_EVENT : [chars] ([chars][chars]([dec]))
Explanation A REDUNDANCY Peer Monitor event occurred and reported. The report should help to find out the reason for a switch-over.
Recommended Action Copy the error message exactly as it appears. Copy down the system's configuration along with any other relevant information. Contact your technical support representative for assistance.
%REDUNDANCY-6-STANDBY_HAS_RELOADED : The Standby [chars] has reloaded; reason: [chars]
Explanation The Standby peer has reloaded itself to correct a configuration mismatch between the Active and the Standby. The Standby has detected that it is missing configuration for a line card. This has most likely happened because the Standby was reloaded prior to the new card being inserted.
Recommended Action No action is required.
%REDUNDANCY-6-SWITCHOVERTIME : Time taken to switchover = [dec] milliseconds
Explanation This is how long the Standby peer took to become Active after a failure of the existing Active.
Recommended Action No action is required.
REDUNDANCY_UTILS
%REDUNDANCY_UTILS-3-INVALID_UNIT_DESIGNATION : An invalid redundancy designation ([chars]) has been detected.
Explanation The redundancy utility assigns each system a unit designation of either an Active Unit, Standby Unit, or Other Unit, and this designation was found to be invalid in the run-time module associated with the system traceback message. This condition most likely occurred because of a software error. The message text provides more information on the specific nature of the error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
REGISTRY
%REGISTRY-2-REG_FLAG_DEADLOCK : Registry call to [chars] timed out due to deadlock
Explanation When a remote registry is not serviced within 25 seconds, the remote process (and presumably the entire system) is deadlocked. This message is printed when the deadlock is broken by a timeout
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%REGISTRY-2-REG_PARSE_ERROR : [chars]: Could not parse notification [chars] : error/no. of items = [dec]
Explanation Registry library is unable to parse notification received from name server. This could be for several reasons: a) There is a bug in sscanf b) The notification block is corrupted c) The pathname published to the name server is invalid This is a serious issue that affects inter-process communication.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%REGISTRY-3-FASTCASE_OUT_OF_BOUNDS : Attempt made in [chars] to register with out of bounds key.
Explanation In FASTCASE registry the key has to be smaller than the size specified when the registry was created. This message indicates that an attempt was made to register with a key out of bounds.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%REGISTRY-3-REG_FLAG_ERR : Invalid combination of registry flag and scheduler control : [chars]
Explanation When process blocking has been disabled either using raise_interrupt_level or assign_blocking_disabled, a remote registry with flags REG_FLAG_DATA_SAFE/REG_FLAG_PEER has been invoked.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%REGISTRY-3-REG_SUSPEND : Registry of type SUSPEND called when suspends are not allowed.
Explanation When process blocking has been disabled either using raise_interrupt_level or assign_blocking_disabled, a remote registry of type SUSPEND has been invoked.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%REGISTRY-3-REG_XDR : [chars]
Explanation There was an error while marshalling a parameter to a remote (inter-process) registry call
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%REGISTRY-3-SEQ_LIST_OVERWRITE : Attempt made to overwrite a set sequence function ([chars])
Explanation A single function can be set as a callback for a specified sequence number for a sequenced list registry. This message indicates that an attempt to set a new callback has failed because a callback function has already been set for this sequence number.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%REGISTRY-3-STUB_CHK_OVERWRITE : Attempt made to overwrite a set stub function in [chars].
Explanation A single function can be set as a callback for when a stub w/ check registry is invoked. This message indicates that an attempt to set a new callback has failed because a callback function has already been set.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
RFS
%RFS-3-CAPENTRY_REG : RFS Cap Entry ([dec]) for Entity ([dec]) Registration failed
Explanation RFS ISSU Cap Entry registration failed
Recommended Action Enter the following commands: show issu capability entries and copy the error and send it to TAC. TAC team can contact the file-systems team to check why this capability entry failed to register
%RFS-3-CAPGROUP_REG : RFS Cap Group ([dec]) for Entity ([dec]) Registration failed
Explanation RFS ISSU Cap Group registration failed
Recommended Action Enter the following commands: show issu capability groups and copy the error and send it to TAC. TAC team can contact the file-systems team to check why this capability group failed to register
%RFS-3-CAPTYPE_REG : RFS Cap Type for Entity ([dec]) Registration failed
Explanation RFS ISSU Cap Type registration failed
Recommended Action Enter the following commands: 'show issu capability types' and copy the error and send it to TAC. TAC team can contact the file-systems team to check why this capability type failed to register
%RFS-3-CLIENT_REG : RFS Client ([dec]) Registration failed
Explanation RFS ISSU client registration failed
Recommended Action Enter the following command:'show issu client' and copy the error and send it to TAC. TAC team can contact the file-systems team to check why no uid with this value found registered in ISSU Database
%RFS-3-CLIENT_SESSION_REG : RFS ISSU client shared msg session for entity ([dec]) registration failed
Explanation RFS ISSU client shared msg session registration failed
Recommended Action Enter the following commands: show issu sessions and copy the error and send it to TAC. TAC team can contact the file-systems team to check why this shared message session failed to register
%RFS-3-CLIENT_SESSION_UNREG : RFS session ([dec]) Un-Registration failed
Explanation RFS ISSU client session un-registration failed
Recommended Action Enter the following commands: show issu sessions and copy the error and send it to TAC. TAC team can contact the file-systems team to check why this client session failed to un-register
%RFS-3-CREATE_CLIENT_PORT : RFS create client port ([chars]) failed
Explanation RFS ISSU create client port failed
Recommended Action Enter the following commands: show ipc port and copy the error and send it to TAC. TAC team can contact the file-systems team to check why this ipc port could not be created
%RFS-3-CREATE_SERVER_PORT : RFS create server port ([chars]) failed
Explanation RFS ISSU create server port failed
Recommended Action Enter the following commands: show ipc port and copy the error and send it to TAC. TAC team can contact the file-systems team to check why this ipc port could not be created
%RFS-3-ENTITY_REG : RFS Entity ([dec]) Registration failed
Explanation RFS ISSU entity failed to register with ISSU
Recommended Action Enter the following command:'show issu entities' and copy the error and send it to TAC. TAC team can contact the file-systems team to check why this entity failed to register
%RFS-3-IPC_GET_BUFFER : RFS issu ipc get buffer failed
Explanation RFS ISSU ipc get buffer failed
Recommended Action Enter the following commands:'show proc mem' or 'show buffs' to check if memory or buffer is full. shutdown unused tasks or reset cards usually can recover those memory leak problem. Copy the error and send it to TAC if those actions do not help.
%RFS-3-LOCATE_PORT : RFS locates port ([chars]) failed
Explanation RFS ISSU locates port failed
Recommended Action Enter the following commands: show ipc port and copy the error and send it to TAC. TAC team can contact the file-systems team to check why this ipc port could not be located
%RFS-3-MSG_GET_NEGO_VER : RFS Client ([dec]) get msg negotiated version failed. Error = [dec]
Explanation RFS ISSU client get msg negotiated version failed
Recommended Action Enter the following commands: show issu fsm, show issu ses and copy the error and send it to TAC. TAC team can contact the file-systems team to check why get message negotiated version failed
%RFS-3-MSGGROUP_REG : RFS Msg Group ([dec]) for Entity ([dec]) Registration failed
Explanation RFS ISSU Msg Group registration failed
Recommended Action Enter the following commands: 'show issu message groups', and copy the error and send it to TAC. TAC team can contact the file-systems team to check why this message group failed to register
%RFS-3-MSG_INCOMP : [chars](): msg_type [[dec]] under session [[dec]] is incompatible
Explanation The message types are incompatible under ISSU
Recommended Action Enter the following command: show issu message types 110 and copy the output and send it to TAC. TAC team can contact the file-systems team to check why messages are incompatible
%RFS-3-MSG_MTU : RFS Client ([dec]) get msg mtu failed. Error = [dec]
Explanation RFS ISSU client get msg mtu failed
Recommended Action Enter the following commands: show issu fsm, show issu ses and copy the error and send it to TAC. TAC team can contact the file-systems team to check why get message mtu failed
%RFS-3-MSG_RCV : RFS Client ([dec]) on session ([dec]) to seat [[hex]] failed receive transformation with error[[chars]]
Explanation RFS ISSU client receive msg failed
Recommended Action Enter the following commands:show issu sessions and copy the error and send it to TAC. TAC team can contact the file-systems team to check why receive message for this client failed
%RFS-3-MSGTYPE_REG : RFS Msg Type for Entity ([dec]) Registration failed
Explanation RFS ISSU Msg Type registration failed
Recommended Action Enter the following commands: 'show issu entities', 'show issu message types' and copy the error and send it to TAC. TAC team can contact the file-systems team to check why this message types failed to register
%RFS-3-MSG_XMIT : RFS Client ([dec]) on session ([dec]) to seat [[hex]] failed send transformation with error[[chars]]
Explanation RFS ISSU client send msg failed
Recommended Action Enter the following commands:show issu sessions and copy the error and send it to TAC. TAC team can contact the file-systems team to check why send message for this client failed
%RFS-3-NEGO_COMP : RFS nego is not compatible ([dec])
Explanation RFS ISSU start shared nego session failed
Recommended Action Enter the following commands: 'show issu sessions' and copy the error and send it to TAC. TAC team can contact the file-systems team to check why this client negotiation session is not compatible
%RFS-3-NEGO_SESSION_REG : RFS nego session for Entity ([dec]) Registration failed
Explanation RFS ISSU shared nego session registration failed
Recommended Action Enter the following commands: 'show issu sessions', 'show issu entities' and copy the error and send it to TAC. TAC team can contact the file-systems team to check why this client negotiation session failed to register
%RFS-3-NEGO_SESSION_UNREG : RFS session ([dec]) Un-Registration failed
Explanation RFS ISSU shared nego session un-registration failed
Recommended Action Enter the following commands: 'show issu sessions' and copy the error and send it to TAC. TAC team can contact the file-systems team to check why this client negotiation session failed to un-register
%RFS-3-OPEN_CLIENT_PORT : RFS open client port ([chars]) failed. Reason:[chars]
Explanation RFS ISSU open client port failed
Recommended Action Enter the following commands: show ipc port and copy the error and send it to TAC. TAC team can contact the file-systems team to check why this ipc port could not be opened
%RFS-3-OPEN_SERVER_PORT : RFS open server port ([chars]) failed
Explanation RFS ISSU open server port failed
Recommended Action Enter the following commands: show ipc port and copy the error and send it to TAC. TAC team can contact the file-systems team to check why this ipc port could not be opened
%RFS-3-RECEIVE_NEGO_FAILED : RFS receive nego message ([IPV6 address]) failed
Explanation RFS ISSU receive nego message failed
Recommended Action Enter the following commands: 'show issu session' and copy the error and send it to TAC. TAC team can contact the file-systems team to check why this client negotiation message failed
%RFS-3-RECEIVE_NEGO_NOT_DONE : RFS receive nego message is not done ([dec])
Explanation RFS ISSU receive nego message is not done
Recommended Action Enter the following commands: show issu session and copy the error and send it to TAC. TAC team can contact the file-systems team to check why this client negotiation failed to complete
%RFS-3-REG_PORT : RFS reg port ([dec]) failed
Explanation RFS ISSU reg port failed
Recommended Action Enter the following commands: show ipc port and copy the error and send it to TAC. TAC team can contact the file-systems team to check why this port failed to register
%RFS-3-RFS_BOOL_CREATE_ERR : [chars].
Explanation The RFS RF client has error in creating watched boolean.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%RFS-3-RFS_ISSU_CLIENT_OR_ENTITY_ID : RFS ISSU couldnt find client/entity id in peer.
Explanation RFS ISSU couldnt find client/entity id in peer.
Recommended Action Enter the following command:'show issu entities' and copy the error and send it to TAC. TAC team can contact the file-systems team to check why this client/entity id coudlnt find in peer
%RFS-3-RFS_ISSU_NEGO_PROCESS : RFS create rfs_issu_start_port watch boolean failed
Explanation RFS ISSU create nego process failed
Recommended Action Enter the following commands:show proc mem and copy the error and send it to TAC. TAC team can contact the file-systems team to check why this watched boolean could not be created
%RFS-3-RFS_ISSU_START_PORT : RFS create rfs_issu_start_port watch boolean failed
Explanation RFS ISSU create rfs_issu_start_port watch boolean failed
Recommended Action Enter the following commands:show proc mem and copy the error and send it to TAC. TAC team can contact the file-systems team to check why this watched boolean could not be created
%RFS-3-RFS_ISSU_START_SESSION : RFS create rfs_issu_start_session watch boolean failed
Explanation RFS ISSU create rfs_issu_start_session watch boolean failed
Recommended Action Copy the error and send it to TAC. TAC team can contact the file-systems team to check why this ipc port could not be created
%RFS-3-RFS_RF_PROG_ERR : Failed to send the bulk sync notification done. Error ([dec]).
Explanation The RFS RF client failed to send the final bulk sync otification.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%RFS-3-RFS_RF_PROG_NOT_SENT_ERR : [chars].
Explanation The RFS RF client has error in sending client progression.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%RFS-3-SEND_NEGO_MESSAGE : RFS send nego message ([IPV6 address]) failed
Explanation RFS ISSU send nego message failed
Recommended Action Enter the following commands: 'show issu session' and copy the error and send it to TAC. TAC team can contact the file-systems team to check why this client negotiation message failed
%RFS-3-START_NEGO_SESSION : RFS nego ([dec]:[dec]) to [[chars]:[hex]] failed: [[chars]]
Explanation RFS ISSU start shared nego session failed
Recommended Action Enter the following commands: 'show issu sessions' and copy the error and send it to TAC. TAC team can contact the file-systems team to check why this client negotiation session failed to start
%RFS-3-UNREG_ENTITY : RFS ISSU Client unreg entity failed.
Explanation RFS ISSU client unreg entity failed
Recommended Action Enter the following command:'show issu entities' and copy the error and send it to TAC. TAC team can contact the file-systems team to check why this entity failed to un-register
RG_AR
%RG_AR-3-NOPEER : Peer does not exist for RG ID = ([dec]) with error code = ([dec])
Explanation Failures in communication with peer
Recommended Action Make sure that there are no configuration errors.
%RG_AR-3-NOPROCESS : Unable to create process for [chars].
Explanation Quite likely, we ran out of memory. Other explanations are possible.;msgdef_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.
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.
RG_FAULTS
%RG_FAULTS-3-NOPROCESS : Unable to create a new process for [chars].
Explanation Quite likely, we ran out of memory. Other explanations are possible.;msgdef_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.
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.
%RG_FAULTS-6-PRICHANGE : RG Infra RG[[dec]] Priority update. new priority [[dec]] old priority [[dec]] [chars]
Explanation The runtime priority of the group was updated
Recommended Action Look at rg_infra trace for the cause for priority change
%RG_FAULTS-6-PRICONFCHANGE : RG Infra RG[[dec]] Priority configuration changed. New runtime priority:[[dec]]
Explanation The configured priority changed, runtime priority was affected
Recommended Action No action need to be taken
RG_MEDIA
%RG_MEDIA-3-INVALIDPLATFORM : Unsupported Platform
Explanation The peer platform is unsupported as a RG-pair
Recommended Action Only like platforms can be configured as a RG pair.
%RG_MEDIA-3-NOPROCESS : Unable to create process for [chars].
Explanation Quite likely, we ran out of memory. Other explanations are possible.;msgdef_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.
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.
%RG_MEDIA-3-NOSOCKET : Unable to open socket
Explanation The system was unable to initialize an IP connection for RG Protocol
Recommended Action Make sure that there is at least one interface configured to run IP.
%RG_MEDIA-3-TIMEREXPIRED : RG id [dec] Hello Timer Expired.
Explanation This router did not receive hello message from the peer within the configured hold time. This may result in a role change.
Recommended Action Enter show tech-support, show history commands, collect all the information and error message and report it to your technical support representative.
%RG_MEDIA-4-BADSEQ : Group [dec]: Sequence number larger than expected -indicates packet loss
Explanation Sequence number expected from peer is too big, this usually indicates packet loss
Recommended Action Check for connectivity problems between the 2 peers.
RG_PROTOCOL
%RG_PROTOCOL-3-NOPROCESS : Unable to create process for [chars].
Explanation Quite likely, we ran out of memory. Other explanations are possible.;msgdef_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.
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.
%RG_PROTOCOL-3-UNEXPECTEDACTIVE : RG id [dec] unexpected Active peer [IP_address]
Explanation An unexpected Active peer has been detected via control interface; there are 2 Active RGs in the redundancy group
Recommended Action If this is not a transient state, check for connectivity problems or inconsistency of rg protocol timer configuration between the peers
%RG_PROTOCOL-4-UNEXPECTEDSTANDBY : RG id [dec] unexpected Standby peer [IP_address]
Explanation An unexpected Standby peer has been detected via control interface; there are 2 Standby RGs in the redundancy group
Recommended Action If this is not a transient state, check for connectivity problems or inconsistency of rg protocol timer configuration between the peers
%RG_PROTOCOL-5-ROLECHANGE : RG id [dec] role change from [chars] to [chars]
Explanation RG role (Init/Standby/Active) has been changed
Recommended Action No action is required.
RG_TRANSPORT
%RG_TRANSPORT-3-NOPROCESS : Unable to create process for [chars].
Explanation Quite likely, we ran out of memory. Other explanations are possible.;msgdef_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.
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.
%RG_TRANSPORT-3-TRANSFAIL : Negotiation failure with error code: [dec]
Explanation The query_status in msg is not RG_TRANS_SUCCESS
Recommended Action Make sure that there are no configuration errors.
RG_VP
%RG_VP-3-NOPROCESS : Unable to create process for [chars].
Explanation Quite likely, we ran out of memory. Other explanations are possible.;msgdef_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.
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.
%RG_VP-6-BULK_SYNC_DONE : RG group [dec] BULK SYNC to standby complete.
Explanation Indicagtes Standby bulk sync complete
Recommended Action No action is required.
%RG_VP-6-STANDBY_READY : RG group [dec] Standby router is in SSO state
Explanation Indicates standby readiness
Recommended Action No action is required.
RMON
%RMON-5-FALLINGTRAP : Falling threshold has been crossed because the value of [chars] has fallen below the falling-threshold value [dec]
Explanation A Falling Event will be generated.The value of the specified MIB object has fallen below the falling threshold value as configured by the rmon alarm command for the specified object
Recommended Action Take appropriate action on the specified MIB object.
%RMON-5-HCFALLINGTRAP : Falling trap is generated because the value of [chars] has fallen belowthe falling-threshold hc value [int]
Explanation A Falling Trap has been generated.The value of the specified MIB object has fallen below the falling threshold value as configured by the rmon hc-alarms command for the specified object
Recommended Action Take appropriate action on the specified MIB object.
%RMON-5-HCRISINGTRAP : Rising trap is generated because the value of [chars] exceeded therising-threshold hc value [int]
Explanation A Rising Trap has been generated.The value of the specified MIB object has exceeded the rising threshold value as configured by the rmon hc-alarms command for the specified object
Recommended Action Take appropriate action on the specified object.
%RMON-5-RISINGTRAP : Rising threshold has been crossed because the value of [chars] exceeded the rising-threshold value [dec]
Explanation A Rising Event will be generated.The value of the specified MIB object has exceeded the rising threshold value as configured by the rmon alarm command for the specified object
Recommended Action Take appropriate action on the specified object.
ROLLBACK_ISSU
%ROLLBACK_ISSU-2-GET_BUFFER : Rollback ISSU client failed to get buffer for message. Error: [dec] ([chars])
Explanation The Rollback 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)
%ROLLBACK_ISSU-2-INIT : Rollback ISSU client initialization failed to [chars]. Error: [dec] ([chars])
Explanation The Rollback 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%ROLLBACK_ISSU-2-SEND_NEGO_FAILED : Rollback ISSU client failed to send negotiation message. Error: [dec] ([chars])
Explanation The Rollback 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)
%ROLLBACK_ISSU-2-SESSION_NEGO_FAIL_START : Failed to start Rollback ISSU session negotiation. Error: [dec] ([chars])
Explanation The Rollback 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>)
%ROLLBACK_ISSU-2-SESSION_REGISTRY : Rollback ISSU client failed to register session information. Error: [dec] ([chars])
Explanation The Rollback 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>)
%ROLLBACK_ISSU-3-INVALID_SESSION : Rollback ISSU client does not have a valid registered session.
Explanation The Rollback 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>)
%ROLLBACK_ISSU-3-MSG_NOT_OK : Rollback ISSU client 'Message Type [dec]' is not compatible
Explanation The Rollback 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>)
%ROLLBACK_ISSU-3-MSG_SIZE : Rollback ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] ([chars])
Explanation The Rollback ISSU client failed to calculate the MTU for the specified message. The Rollback 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>)
%ROLLBACK_ISSU-3-SESSION_UNREGISTRY : Rollback ISSU client failed to unregister session information. Error: [dec] ([chars])
Explanation The Rollback 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>)
%ROLLBACK_ISSU-3-TRANSFORM_FAIL : Rollback ISSU client [chars] transform failed for 'Message Type [dec]'. Error: [dec] ([chars])
Explanation The Rollback 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 Rollback 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>)
ROUTEMAP
%ROUTEMAP-4-BADTRACKOBJECTTYPE : can't track this type of object
Explanation Route maps only support STATE type track objects. This object is not a STATE object
Recommended Action Reconfigure the track object to make it a STATE object.
RPL
%RPL-3-CHUNK_ERROR : [chars]
Explanation This Error message would be encountered when trying to 1. access chunk or chunk element when they are not valid. 2. lock failure on chunk element.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%RPL-3-CONFIG_ERROR : RPL [chars] configuration failed: [chars] [chars] code [dec]
Explanation This Error message would be encountered when trying to configure rpl through api.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%RPL-3-MALFORMEDMSG : Malformed [chars] received from: [IPV6 address]
Explanation This Error message would be encountered if a malformed RPL Control message is received
Recommended Action Informational
RSCMSM
%RSCMSM-3-NO_LIST_CREATED : [chars]: Cannot create interface-based rsc list.
Explanation This failure is due to the list create operation.
Recommended Action Please check the memory at the moment.
%RSCMSM-3-NO_SUCH_INTERFACE : [chars]: The interface doesn't exist
Explanation The interface for resource measurement doesn't exist at the time of the operation.
Recommended Action Check the configuration to see if that interface is there
%RSCMSM-5-TEST_ALREADY_RUNNING : One test is already running.
Explanation there is already one test running at the same time.
Recommended Action Please wait for the completeness of the running test before starting another test.
RSRB
%RSRB-3-BADVERSIONFST : FSTin: [chars]: version mismatch, mine [dec], theirs [dec]
Explanation The remote end of a direct serial peer is running the wrong version of the system software. Either the local end, the remote end, or both are not up to date.
Recommended Action Call your technical support representative for an update.
%RSRB-3-BADVERSIONIF : IFin: [chars]: version mismatch, mine [dec], theirs [dec]
Explanation The remote end of a direct serial peer is running the wrong version of the system software. Either the local end, the remote end, or both are not up to date.
Recommended Action Call your technical support representative for an update.
%RSRB-3-BADVERSIONTCP : [chars]: [dec]/[IP_address]: version mismatch, mine [dec], theirs [dec]
Explanation The remote end of a TCP remote peer is running the wrong version of the system software. Either the local end, the remote end, or both are not up to date.
Recommended Action Call your technical support representative for an update.
%RSRB-3-FSTERR : [chars]: [chars]: [IP_address], op [hex], len [dec], trn [dec]
Explanation The remote end of a direct serial RSRB connection detected a configuration problem or traffic that is not recognized by the configuration.
Recommended Action Examine the configuration on both sides of the serial connection for possible problems. Examine the traffic being offered for propagation with respect to the configuration. The destination target ring is denoted by the value of trn.
%RSRB-3-HDRNOVRP : Peer [IP_address], HDR, no vrp
Explanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
%RSRB-3-HDRVRP : Peer [dec]/[IP_address], HDR, vrp state wrong, [dec]
Explanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
%RSRB-3-IFERR : [chars]: [chars]: [chars], op [hex], len [dec], trn [dec]
Explanation The remote end of a direct serial RSRB connection detected a configuration problem or traffic that is not recognized by the configuration.
Recommended Action Examine the configuration on both sides of the serial connection for possible problems. Examine the traffic being offered for propagation with respect to the configuration. The destination target ring is denoted by the value of trn.
%RSRB-3-NOMEMORY : Unit [dec], no memory for [chars]
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.
%RSRB-3-NOTREM : Null idb and not remote
Explanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
%RSRB-3-SENDPUNTFST : [chars]: sent [chars] to [chars]
Explanation The local end of a direct serial RSRB connection detected a configuration problem or traffic that is not recognized by the configuration.
Recommended Action Examine the configuration on both sides of the serial connection for possible problems. Examine the traffic being offered for propagation with respect to the configuration.
%RSRB-3-SENDPUNTIF : [chars]: sent [chars] to [chars]
Explanation The local end of a direct serial RSRB connection detected a configuration problem or traffic that is not recognized by the configuration.
Recommended Action Examine the configuration on both sides of the serial connection for possible problems. Examine the traffic being offered for propagation with respect to the configuration.
%RSRB-4-BADLEN : Peer [chars], [chars], bad length [dec], trn [dec]
Explanation An internal software error occurred.
Recommended Action If either message recurs, call your technical support representative for assistance.
%RSRB-4-BADLENIP : Peer [dec]/[IP_address], [chars], bad length [dec], trn [dec]
Explanation An internal software error occurred.
Recommended Action If either message recurs, call your technical support representative for assistance.
%RSRB-4-BADVRE : Bad vre type
Explanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
%RSRB-4-CONIPST : Peer [dec]/[IP_address], CONN, illegal state [dec]
Explanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
%RSRB-4-CONNILLSTATE : Peer [chars], CONN, illegal state [dec]
Explanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
%RSRB-4-CONNSTAT : Peer [chars], IFin, bad connection state [dec]
Explanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
%RSRB-4-HDRRECV : Peer [dec]/[IP_address], HDR, recv state invalid, not empty [dec]
Explanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
%RSRB-4-ILLPEER : Peer [chars] [%-08x], illegal state [dec]
Explanation An internal software error occurred.
Recommended Action If either of these messages recur, call your technical support representative for assistance.
%RSRB-4-LOCAL : Unit [dec], local/vring set simultaneously, vrn [dec]
Explanation An internal software error occurred.
Recommended Action If either of these messages recur, call your technical support representative for assistance.
%RSRB-4-OPTNULL : Remopened and t NULL
Explanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
%RSRB-4-PEERSTAT : Peer [chars], wrong state [dec]
Explanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
%RSRB-4-RNGXFAIL : Ring exchange failure, resetting peer: [chars]
Explanation The RSRB peer initiation logic failed due to a memory shortage or congestion condition.
Recommended Action The problem should clear and the peers should re-open without operator intervention.
RSVP
%RSVP-1-RSVP_AUTH_NO_KEYS_LEFT : No valid keys left for [IP_address]
Explanation The router attempted to use a key in an RSVP key chain but discovered that all the keys in the chain have expired and no other per-neighbor or per-interface keys are available for the specified neighbor. The router will continue to use the last key in the chain rather than revert to an unauthentication condition. However, the specified neighbor router may start discarding RSVP messages at that point and reservations with that neighbor may eventually time out.
Recommended Action Update the key chain by updating the text and expiration time(s) for the expired key(s).
%RSVP-2-RSVP_AUTH_KEY_CHAIN_EXPIRED : All the keys in chain [chars] have expired -please update the key chain now
Explanation The router attempted to use a key in an RSVP key chain but discovered that all the keys in the chain have expired. The router will attempt to to find another suitable key. If no other suitable per-neighbor key can be found, the router will attempt to use key (chain) configured for the interface over which the authenticated RSVP message is being sent or received.
Recommended Action Update the key chain by updating the text and expiration time(s) for the expired key(s).
%RSVP-3-BAD_RMSG_TIMER : Inconsistent RSVP reliable message timer
Explanation The summary refresh timer may be blocked.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support rsvp command to gather data which may help identify the nature of the error. Then send this information to your Cisco technical support representative.
%RSVP-3-BAD_RSVP_MSG_RCVD_AUTH_COOKIE : [chars] message from [IP_address] discarded -challenge failed for key ID %*s
Explanation The router sent an RSVP message to challenge the untrusted source to compute a secure hash on a random piece of data and return the hash with the same data, but the source did not return the expected data. RSVP discarded the response because the untrusted source may be (unsuccessfully) attempting an RSVP challenge response replay attack.
Recommended Action If you can verify that the source is trusted, it is possible that the source has malfunctioned; in this case, copy the error message exactly as it appears on the console or in the system log, issue the show tech-support rsvp command to gather data which may help identify the nature of the error, and send this information to your Cisco technical support representative. Otherwise, try to find and disable the untrusted source.
%RSVP-3-BAD_RSVP_MSG_RCVD_AUTH_DIGEST : [chars] message from [IP_address] discarded -incorrect message digest
Explanation The router received an RSVP message that contained a different secure hash from the one computed by the router. RSVP discarded the message because the message may have come from an untrusted source.
Recommended Action Check the configuration on the router and the sending system to make sure they are using the correct security key and secure hash algorithm.
%RSVP-3-BAD_RSVP_MSG_RCVD_AUTH_DUP : [chars] message from [IP_address] discarded -authentication seq #[int] is a duplicate
Explanation The router received an RSVP message with an authentication sequence number that has already been seen. RSVP discarded the message because an untrusted source may be (unsuccessfully) attempting an RSVP message replay attack.
Recommended Action If you can verify that the source is trusted, it is possible that the source has rebooted and its clock has gone backward in time; in this case, the source should be configured to synchronize its clock with an NTP server. Otherwise, the sender could be an untrusted source (unsuccessfully) attempting an RSVP message replay attack; try to find and disable the untrusted source.
%RSVP-3-BAD_RSVP_MSG_RCVD_AUTH_NO_SA : [chars] message from [IP_address] discarded: no security association for [IP_address] -no RSVP security key configured or no memory left.
Explanation The router received an RSVP message that contained a secure hash but dropped the message because the router was not able to create a security association for the sending system.
Recommended Action Check the configuration on the router to make sure that RSVP has access to a security key for the sending system. If such a key is configured, then check to see if the router has run out of memory.
%RSVP-3-BAD_RSVP_MSG_RCVD_AUTH_WIN : [chars] message from [IP_address] discarded -seq #[int] outside authentication window
Explanation The router received an RSVP message whose authentication sequence number is less than the lower limit of the out-of-order window. RSVP discarded the message because an untrusted source may be (unsuccessfully) attempting an RSVP message replay attack.
Recommended Action It is possible that a trusted source is sending a burst of reordered RSVP messages that is too large for the authentication window size. If you can verify that the source is trusted and its messages are being sent in large reordered bursts, use the ip rsvp authentication window-size command to increase the window size on the receiving router. It is also possible that a trusted source has rebooted and its clock has gone backward in time; in this case, the source should be configured to synchronize its clock with an NTP server. Otherwise, the sender could be an untrusted source (unsuccessfully) attempting an RSVP message replay attack; try to find and disable the untrusted source.
%RSVP-3-BAD_RSVP_MSG_RCVD_CHECKSUM : RSVP Message had a bad checksum: [dec] foo: [dec]
Explanation The router received an RSVP message with the checksum field incorrectly set. Bad checksums would most likely be caused by packet corruption outside RSVP. Be aware that corruption reported by RSVP might also be affecting other protocols on the router and might explain other unexpected non-RSVP protocol behavior. Please attempt to track down the source of the corruption.
Recommended Action LOG_BAD_RSVP_MSG_ACTION Copy the error message(s) exactly as it appears on the console or in the system log. Issue the show tech-support rsvp command to gather data that may help identify the nature of the error and send this information to your Cisco technical support representative.
%RSVP-3-BAD_RSVP_MSG_RCVD_LEN : RSVP Message had a bad length; ip data len: [dec] rsvp len: [dec]
Explanation The router received an RSVP message with the length field set to an unexpected value. Be aware that a bad length error may also be a side-effect of packet corruption.
Recommended Action LOG_BAD_RSVP_MSG_ACTION Copy the error message(s) exactly as it appears on the console or in the system log. Issue the show tech-support rsvp command to gather data that may help identify the nature of the error and send this information to your Cisco technical support representative.
%RSVP-3-BAD_RSVP_MSG_RCVD_MALFORMED : RSVP Message was malformed; traversed objects len: [dec] rsvp msg len: [dec]
Explanation An error was encountered during validation of the objects in an RSVP message received by the router.
Recommended Action LOG_BAD_RSVP_MSG_ACTION Copy the error message(s) exactly as it appears on the console or in the system log. Issue the show tech-support rsvp command to gather data that may help identify the nature of the error and send this information to your Cisco technical support representative.
%RSVP-3-BAD_RSVP_MSG_RCVD_OBJ_LEN : Received a bad RSVP message, num objs: [dec] obj len: [dec] msg_len: [dec]
Explanation An error was encountered during validation of the objects in an RSVP message received by the router. The number of objects in the RSVP message was found to be greater than the maximum expected number or the size of an object was found to be smaller than the minimum expected size.
Recommended Action LOG_BAD_RSVP_MSG_ACTION Copy the error message(s) exactly as it appears on the console or in the system log. Issue the show tech-support rsvp command to gather data that may help identify the nature of the error and send this information to your Cisco technical support representative.
%RSVP-3-BAD_RSVP_MSG_RCVD_TYPE : RSVP Message had a bad type: [dec]
Explanation The router received an incorrect RSVP message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support rsvp command to gather data which may help identify the nature of the error. Then send this information to your Cisco technical support representative.
%RSVP-3-BAD_RSVP_MSG_RCVD_VER : RSVP Message had a bad version: [dec]
Explanation The router received an RSVP message with the version field set to an unexpected value.
Recommended Action LOG_BAD_RSVP_MSG_ACTION Copy the error message(s) exactly as it appears on the console or in the system log. Issue the show tech-support rsvp command to gather data that may help identify the nature of the error and send this information to your Cisco technical support representative.
%RSVP-3-CONSISTENCY : [chars]: [chars] [chars] [chars]
Explanation An action attempted by the rsvp implementation encountered an unexpected condition
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support rsvp command to gather data which may help identify the nature of the error. Then send this information to your Cisco technical support representative.
%RSVP-3-IP_HDR : [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex]
Explanation This is an auxiliary message to several packet-related messages. It displays the contents of 8 32-bit words immediately following the start of the IPv4/v6 header, in hex format. To decode the information in the IPv4 and IPv6 headers, please refer to RFCs 791 and 2460.
Recommended Action Decode the information in the IPv4 and IPv6 headers to determine the source of the RSVP message.
%RSVP-3-MSG_1 : [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex]
Explanation This is an auxiliary message to several packet-related messages. It displays the contents of the first 8 32-bit words immediately following the start of the RSVP header, in hex format. To decode the information in the RSVP header, please refer to RFC 2205.
Recommended Action If you need additional information about the packet, then turn on debug ip rsvp dump-messages <msg type> [hex] and try to capture the bad message. If you use the hex version of this command, you can convert it to pcap format with the offline tool text2pcap and then view the contents with another offline tool such as ethereal.
%RSVP-3-MSG_2 : [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex]
Explanation This is an auxiliary message to several packet-related messages. It displays the contents of the next 8 32-bit words following those that are printed by the MSG_1 message above, in hex format. To decode the information in these 32-bit words, please refer to RFC 2205.
Recommended Action If you need additional information about the packet, then turn on debug ip rsvp dump-messages <msg type> [hex] and try to capture the bad message. If you use the hex version of this command, you can convert it to pcap format with the offline tool text2pcap and then view the contents with another offline tool such as ethereal.
%RSVP-3-RSVP_MFI_RECOVERY : RSVP calculated Recovery Time is longer than TE Rewrite Hold-Time registered with LSD. Some LSPs may not be be recovered.
Explanation TE registered a maximum cutover time with the LSD that is less than the time it may actually take to recover all LSPs. As a result, more than usual traffic loss may occur on some LSPs during recovery
Recommended Action Make note of the number of Checkpointed LSPs in the RSVP HA database by issuing the command show ip rsvp high-availability database internal . This number likely exceeds the hard defined limit of the number of recoverable LSPs. Provide this information to Cisco technical support representative.
%RSVP-3-RSVP_MSG_AUTH_CHALLENGE_TIMEOUT : No response to challenge issued to [IP_address] for key ID %*s
Explanation The router sent an RSVP message to challenge the untrusted source to compute a secure hash on a random piece of data and return the hash with the same data, but the source did not reply. The source may have crashed or lost its network connection. However, it is also possible that the source was (unsuccessfully) attempting to replay an RSVP message before the challenge and gave up when it saw the challenge from the router
Recommended Action If you can verify that the source is trusted, try to determine if it has crashed or lost its network connection and then restore network connectivity to it. If the source repeatedly crashes when challenged, a temporary workaround might be to disable challenges on the router by issuing a no ip rsvp authentication challenge command until the problem on the source is resolved. Otherwise, assume the source is untrusted; try to find and disable it.
%RSVP-3-RSVP_MSG_AUTH_TYPE_MISMATCH : [chars] message from [IP_address] discarded -authentication algorithm mismatch
Explanation The router received an RSVP message from a source that required authentication but the received message was using the wrong authentication algorithm.
Recommended Action Issue a show ip rsvp authentication detail <source> command on the router to display the expected algorithm type. Then find the source and change its configuration to match.
%RSVP-4-RSVP_AUTH_DUPLICATE_KEY_ID : Key chains [chars] and [chars] contain duplicate key ID [int]
Explanation An attempt is being made to add a new key identifier to a key chain in the router configuration but RSVP detected that this identifier is found in another key chain already assigned to RSVP. Since key identifiers must be unique across all the key chains used by RSVP, RSVP will not use the keys with this identifier in all such key chains. This could cause RSVP authentication to fail in some cases.
Recommended Action Update the listed key chain(s) so they use different key identifiers.
%RSVP-5-CLEAR_COUNTERS : Clear RSVP message counters by [chars]
Explanation The RSVP message counters have been cleared
Recommended Action No action is required.
%RSVP-5-NO_MATCH_IF_ID_HOP : Received PATH ([IP_address]_[int]->[IP_address]_[int]) -Failed to find interface from IF_ID HOP from neighbor [IP_address]
Explanation The interface id in the HOP object does not match any of this node's interfaces.
Recommended Action Verify the configuration.
%RSVP-5-RSVP_AUTH_KEY_ACL_CHANGE : Key chain [chars] [chars] for [IP_address] because ACL [chars] [chars]
Explanation The ACL specified in the message text associates the key chain specified in the message text with a set of RSVP neighbors. RSVP uses the specified key chain to authenticate each RSVP message exchanged with that set of RSVP neighbors after the association is configured. Subsequently, the specified ACL has been reconfigured such that the key chain association is no longer valid for one or more RSVP neighbors in the set. This causes RSVP to search the configuration for another suitable key chain to use with those neighbors. If no such key chain is found, RSVP will no longer be able to provide authentication for messages exchanged with those RSVP neighbors. This causes RSVP to discard RSVP messages from that set of neighbors. Because this may ultimately lead to loss of RSVP functionality with those neighbors, RSVP generates this system message. This system message may also be generated if the ACL is subsequently changed so that it re-associates RSVP neighbors with the specified key chain. If RSVP is not using another key chain for the set of RSVP neighbors specified by the ACL, RSVP will begin using the specified key chain to exchange authenticated RSVP messages with that set of RSVP neighbors, potentially restoring RSVP functionality with those neighbors.
Recommended Action If the ACL change unexpectedly caused authentication to be disabled or enabled for one or more RSVP neighbors, undo the ACL change so that RSVP authentication is not impacted.
%RSVP-5-RSVP_AUTH_ONE_KEY_EXPIRED : Key (ID) [int] in chain [chars] has expired
Explanation The router has detected that one key in a RSVP key chain has expired and that RSVP has switched to the next unexpired key in that chain.
Recommended Action Update the key chain by changing the text and expiration time(s) for the expired key.
RSVP_SYNC_ISSU
%RSVP_SYNC_ISSU-2-GET_BUFFER : RSVP_SYNC ISSU client failed to get buffer for message. Error: [dec] ([chars])
Explanation The RSVP_SYNC 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)
%RSVP_SYNC_ISSU-2-INIT : RSVP_SYNC ISSU client initialization failed to [chars]. Error: [dec] ([chars])
Explanation The RSVP_SYNC 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%RSVP_SYNC_ISSU-2-SEND_NEGO_FAILED : RSVP_SYNC ISSU client failed to send negotiation message. Error: [dec] ([chars])
Explanation The RSVP_SYNC 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)
%RSVP_SYNC_ISSU-2-SESSION_NEGO : RSVP_SYNC ISSU client encountered unexpected client nego_done. Error: [dec] ([chars])
Explanation An ISSU-compliant client transitions through a series of internal states. The RSVP_SYNC 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>)
%RSVP_SYNC_ISSU-2-SESSION_REGISTRY : RSVP_SYNC ISSU client failed to register session information. Error: [dec] ([chars])
Explanation The RSVP_SYNC 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>)
%RSVP_SYNC_ISSU-3-CAP_INVALID_SIZE : RSVP_SYNC ISSU client capability list is empty.
Explanation The RSVP_SYNC ISSU client capability exchange list size is invalid.
Recommended Action LOG_STD_SH_CMD_ACTION( show issu capability entires <Client_ID>)
%RSVP_SYNC_ISSU-3-CAP_NOT_COMPATIBLE : RSVP_SYNC ISSU client capability exchange result incompatible.
Explanation The RSVP_SYNC ISSU client capability exchange have negotiated as incompatible with the peer.
Recommended Action LOG_STD_SH_CMD_ACTION( show issu negotiated capability <Session_ID>)
%RSVP_SYNC_ISSU-3-INVALID_SESSION : RSVP_SYNC ISSU client does not have a valid registered session.
Explanation The RSVP_SYNC 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>)
%RSVP_SYNC_ISSU-3-MSG_NOT_COMPATIBLE_WITH_PEER : 'Message Type [dec]' is not supported by RSVP_SYNC ISSU client at peer
Explanation The RSVP_SYNC ISSU client at the peer supervisor is not compatible for this message type. The RSVP_SYNC client will be marked as incompatible with the peer.
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>)
%RSVP_SYNC_ISSU-3-MSG_NOT_OK : RSVP_SYNC ISSU client 'Message Type [dec]' is not compatible
Explanation The RSVP_SYNC 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>)
%RSVP_SYNC_ISSU-3-MSG_SIZE : RSVP_SYNC ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] ([chars])
Explanation The RSVP_SYNC ISSU client failed to calculate the MTU for the specified message. The RSVP_SYNC 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>)
%RSVP_SYNC_ISSU-3-SESSION_UNREGISTRY : RSVP_SYNC ISSU client failed to unregister session information. Error: [dec] ([chars])
Explanation The RSVP_SYNC 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>)
%RSVP_SYNC_ISSU-3-TRANSFORM_FAIL : RSVP_SYNC ISSU client [chars] transform failed for 'Message Type [dec]'. Error: [dec] ([chars])
Explanation The RSVP_SYNC 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 RSVP_SYNC 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>)
RTMGR
%RTMGR-3-GENERAL : [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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%RTMGR-3-TOPO_AF_ENABLE_ERR : Failed to enable AF base topology [chars] (error [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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%RTMGR-3-TOPO_AFI_CTX : Topology address-family [chars] context block is NULL.
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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%RTMGR-3-TOPO_CACHE_ADD_ERROR : ([chars])
Explanation cached topo entry creation failure
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%RTMGR-3-TOPO_CACHE_ERROR : ([chars])
Explanation cached topo failure
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%RTMGR-3-TOPO_CACHE_INIT_ERROR : ([chars])
Explanation cached topo initialization failure
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%RTMGR-3-TOPO_HA_LOCK_IVRF_TOPO : Acquired a HA lock on an iVRF topology([chars])
Explanation Topology HA lock shouldn't be applied in an iVRF topology
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%RTMGR-3-TOPO_INTF_CTX : Interface [chars] address-family [chars] topology context is NULL or the function [chars] is not set
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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%RTMGR-3-TOPO_INTF_INV_VRFID : Interface [chars] with invalid vrfid [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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%RTMGR-3-TOPO_IPMCAST_BASE_ERR : Failed to create the base mcast topology in vrf [chars] with error [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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%RTMGR-3-TOPO_LCKMGR_GET_LOCK_COUNT_ERROR : Failed to get lock count for topology([chars])
Explanation Topology lock manager get lock count failure
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%RTMGR-3-TOPO_LCKMGR_INIT_ERROR : ([chars]) manager init failure
Explanation Topology lock manager initialization failure
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%RTMGR-3-TOPO_PROCESS_INIT_ERROR : Topology process init failed due to [chars]
Explanation Topology process initialization failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%RTMGR-3-TOPO_SUBMODE_ERROR : Unexpected transition from parser submode '[chars]'
Explanation An error occured while parsing the topology command
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%RTMGR-3-TOPO_SYNC_ERR : Failed to duplicate active topology on standby (rc=[dec]), id [hex] [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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%RTMGR-3-TOPO_UNSUPPORTED_AFI : Attempt to enable unsupported AFI ([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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%RTMGR-3-TOPO_UNSUPPORTED_API : Topology API [chars] is unsupported due to [chars]
Explanation Topology API is unavailable
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%RTMGR-3-TOPO_VRF_ERR : Topology [chars] address-family [chars] has no VRF entry
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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%RTMGR-3-UNLOCK_ERR : Attempt to unlock active topology '[chars]' (in VRF [chars] [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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%RTMGR-3-VRF_ERR : Topology VRF [chars] creation error
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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
RTT
%RTT-3-AUTO : Error: [chars]
Explanation An error occured while generating IPSLAs Auto operation.
Recommended Action Please check the configuration and try again
%RTT-3-EPNOTIFYFAILED : event type = [chars], client = [chars], reason = [chars]
Explanation Notification for specified type to specified IPSLAs Event Publisher client failed
Recommended Action This maybe transient system error and the notification may work next time. Take the action as suggested by the identified client for loss of notification.
%RTT-3-EPSTARTERROR : Failed to start IPSLAs Event Publisher
Explanation IPSLAs is unable to start a new process for Event Publisher. Reaction Alert notifications will not work.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
%RTT-3-EPURFTYPE : IPSLAs EventPublisher: Unknown reaction filter type for client [chars]
Explanation IPSLAs Event Publisher encountered unknown filter type while sending the reaction alert to specified client Reaction Alert notifications may continue to work for same and other clients.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
%RTT-3-IPSLA_AQM : [chars]: [chars]
Explanation This message indicates software error in IPSLA auto qos monitor feature.
Recommended Action Contact your Cisco technical support representative.
%RTT-3-IPSLAINITIALIZEFAIL : IP SLAs: Failed to initialize, IP SLAs functionality will not work
Explanation IP SLAs failed to initialize. This condition is caused by either a timer wheel timer functionality init that failed or a process that could not be created. A likely cause of this condition is that sufficient memory is not available to complete the task.
Recommended Action Search for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. LOG_STD_REDUCE_ACTION
%RTT-3-IPSLANEGATIVEVALUE : IP SLAs([dec]): Negative Value for [chars]
Explanation IP SLAs statistics has generated an error message.
Recommended Action Contact your Cisco technical support representative
%RTT-3-IPSLANOPROCESS : IP SLAs: Cannot create a new process
Explanation IP SLAs is unable to start a new process, and may not be running.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
%RTT-3-IPSLAPROBENOTFOUND : IP SLAs: Error deleting the probe
Explanation Trying to delete a probe which does not exist
Recommended Action Contact your Cisco technical support representative
%RTT-3-IPSLARESPEVQINITFAIL : IP SLAs responder initialzation failed
Explanation The IP SLAs responder initialization failed to initialize event queue. Because of this failure the IP SLAs probes on other routers for which this router acts as responder will not work.
Recommended Action Contact your Cisco technical support representative.
%RTT-3-IPSLARESPTWINITFAIL : IP SLAs responder initialzation failed
Explanation None
Recommended Action None
%RTT-3-IPSLARTPAPPINITFAILED : IP SLAs rtp operation application process initialzation failed
Explanation The IP SLAs rtp operation application process failed to initialize. Because of this failure the IP SLAs rtp operations will not work.
Recommended Action Contact your Cisco technical support representative.
%RTT-3-IPSLATHRESHOLD : IP SLAs([dec]): Threshold [chars] for [chars]
Explanation This informational message logs threshold violations in the Service Assurance Agent probes. This messages appears when the ip sla logging trap command is entered
Recommended Action If this message is not necessary, enter the no ip sla logging trap command to disable logging. Otherwise, no action is required
%RTT-3-IPSLATWINITFAIL : IP SLAs: Generic Timer wheel timer functionality failed to initialize
Explanation IP SLAs could not initialize the timer wheel.
Recommended Action Search for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. LOG_STD_REDUCE_ACTION
%RTT-3-REACTNOTIFYFAILED : entry number = [dec], reason = [chars]
Explanation IPSLAs Reaction condition was met for specified operation and one or more IPSLAs Event Publisher clients have registered interest for this condition but the notification for this occurence failed.
Recommended Action These maybe transient system errors and the notification may work next time. Use show ip sla event-publisher command to see which clients are registered and take action recommended by them.
%RTT-3-SAAMPLS : IP SLA Monitor([dec]): MPLS [chars] Probe [chars] [chars] for destination-address [IP_address] lsp-selector [IP_address]
Explanation This informational message logs violations in the Service Assurance Agent probes. This messages appears when the ip sla logging trap command is entered
Recommended Action If this message is not necessary, enter the no ip sla logging trap command to disable logging. Otherwise, no action is required
%RTT-4-AUTOAPI : IPSLAs Auto CFG ERR: [chars]([chars]) [chars]
Explanation An error occured while configuring IPSLAs Auto parameters. Some, or all of your configurations may not have been (un)set
Recommended Action Please check the configuration and try again
%RTT-4-AUTOAPIOPER : IPSLAs Auto CFG ERR: [chars]([chars])[[dec]] [chars]
Explanation An error occured while configuring IPSLAs Auto parameters. Some, or all of your configurations may not have been (un)set
Recommended Action Please check the configuration and try again
%RTT-4-AUTOMEM : IPSLAs Auto MEM ERR: [chars]([chars]) [chars]
Explanation IPSLAs Auto feature failed during memory allocation
Recommended Action These maybe transient errors, please try again
%RTT-4-DuplicateEvent : IP SLAs [dec]: Duplicate event received. Event number [dec]
Explanation IP SLAs process has received a duplicate event
Recommended Action This is only a warning message. If this recurs, enter the command show ip sla configuration<NoCmdBld> and copy the output of the command. Copy the message as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information along with information about the application that is configuring and polling the Service Assurance Agent probes.
%RTT-4-EPAPI : IPSLAs EP API: [chars] api failed, client = [chars], reason = [chars]
Explanation IPSLAs Event Publisher API failed for reason identified
Recommended Action The error code is reported to API client. Take the action recommended by the client identified.
%RTT-4-EPINIT : IPSLAs Event Publisher Init Failed. Reason = [chars]
Explanation IPSLAs Event Publisher Initialization failed. The system will try to recover by doing the initialization tasks when first client subscribes to IPSLAs events.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
%RTT-4-INVALIDSRCIPADDR : Possible invalid src IP address ([IP_address]) configured.
Explanation This message appears when no source IP address is found on the host matching the one specified by the user
Recommended Action Unconfigure the probe and reconfigure with valid source IP address
%RTT-4-IPSLAAUTODISCOAUTHFAIL : IP SLAs end point discovery authentication failure for spoke [IP_address].
Explanation The IP SLAs responder initialization failed to initialize timerwheel. Because of this failure the IP SLAs probes on other routers for which this router acts as responder will not work.
Recommended Action Contact your Cisco technical support representative.
%RTT-4-IPSLACLOCKNOTSET : IP SLAs Probe(s) could not be scheduled because clock is not set.
Explanation One or more IP SLAs probes could not be scheduled because system clock is not set.
Recommended Action Ensure that the system clock is functional by using Network Time Protocol or another mechanism.
%RTT-4-IPSLAENDPOINTDEREGISTER : IP SLAs end point de-registered by hub [IP_address].
Explanation None
Recommended Action None
%RTT-4-IPSLASCHEDCONFIGFAIL : IP SLAs Probe [dec]: [chars]
Explanation The IP SLAs probe could not be scheduled. Either the configured starting time has already ocurred, or the starting time is invalid.
Recommended Action Reschedule the failed probe with a valid start time.
%RTT-4-OPER_CLOSS : condition [chars], entry number = [dec]
Explanation This message logs connection loss condition in the IPSLAs operations. This message is enabled when the ip sla monitor logging trap command is entered
Recommended Action Ensure the the destination for the IPSLAs operation is reachable. Also ensure that the IPSLAs responder operation is configured on the destination. If you do not want to log these messages for IPSLA operations, enter the no ip sla monitor logging trap command to disable logging.
%RTT-4-OPER_PROTOERR : Entry number = [dec], Protocol Specific Error [chars], specific code = [dec]
Explanation This message logs protocol specific error condition in the IPSLAs operations. This message is enabled when the ip sla logging traps command is entered
Recommended Action Ensure that the destination for the IPSLAs operation is reachable. Also ensure that the IPSLA responder operation is configured on the destination. If you do not want to log these messages for IPSLAs operations, enter the no ip sla logging traps command to disable the logging
%RTT-4-OPER_TIMEOUT : condition [chars], entry number = [dec]
Explanation This message logs timeout condition in the IPSLAs operations. This message is enabled when the ip sla monitor logging trap command is entered
Recommended Action Ensure that the destination for the IPSLAs operation is reachable. If you do not want to log these messages for IPSLAs operations, enter the no ip sla monitor logging trap command to disable the logging
%RTT-4-REACTPARTIALEVENT : entry number = [dec], missing data = [chars]
Explanation IPSLAs Reaction Event is missing some interesting data
Recommended Action This could be because of IPSLAs software error. Please collect show ip sla config output and report issue to TAC
%RTT-4-SAAGRPSCHEDCONFIGFAIL : Group Schedule Entry [dec]: [chars]
Explanation The probes could not be group scheduled. Either the configured starting time has already ocurred, or the starting time is invalid.
Recommended Action Reschedule the group scheduling entry with a valid start time.
%RTT-4-SAASCHEDCONFIGFAIL : IP SLA Monitor Probe [dec]: [chars]
Explanation The IP SLA Monitor probe could not be scheduled. Either the configured starting time has already ocurred, or the starting time is invalid.
Recommended Action Reschedule the failed probe with a valid start time.
S
SADB
%SADB-4-TREE_CORRUPTED : SADB : AVL Tree got corrupted
Explanation SADB's one of the AVL Trees got corrupted
Recommended Action No action is required.
SBC
%SBC-2-IPC_INIT : IPC message handler registration failure, rc [int]
Explanation Registering an IPC message handler for the SBC feature failed. This will cause the feature not to function. The function
Recommended Action This is normally a software issue. The consequences are that the SBC feature will not function. LOG_STD_ACTION
%SBC-3-FEAT_DOWN : Invalid request [chars] while feature down, call id [int]
Explanation While the feature was not active, an invalid request was received from another layer of the SBC software stack for the specified call ID. Some requests do not have an associated call ID. For them the displayed call ID is zero.
Recommended Action This is a software issue. The consequences could be limited to only one or a few calls. LOG_STD_RECUR_ACTION
%SBC-3-FEAT_UP : Invalid request [chars] while feature up
Explanation While the feature was active, an invalid request was received from another layer of the SBC software stack.
Recommended Action This is a software issue. There are no consequences as this can only have been an Init request while the feature was already active. LOG_STD_RECUR_ACTION
%SBC-3-IPC_NORES : No space for the IPC reply, size [int]
Explanation For a request from upper SBC 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 call that cannot be established etc. In rare cases this could also affect other operations such as feature activation, deactivation, modification, High-Availability switchover operations.
Recommended Action This is normally a software issue. LOG_STD_RECUR_ACTION
%SBC-3-IPC_OPEN_REPLY : IPC Open Reply failed, request [int]
Explanation For a request from upper SBC software stack layers it was not possible to open the reply buffer. The consequence of this could be a stuck call that cannot be established etc. In rare cases this could also affect other operations such as feature activation, deactivation, modification, High-Availability switchover operations.
Recommended Action This is normally a software issue. LOG_STD_RECUR_ACTION
%SBC-3-MEM_INIT_FAILED : Allocation of [chars] memory failed for SBC
Explanation SBC Initialization of channel pool failed.
Recommended Action LOG_STD_ACTION
%SBC-3-NO_RES : [chars] resource not available for the [chars] request, call id [int]
Explanation The specified software resource was not available or could not be located for the specified request from upper SBC software stack layers for the specified call ID.
Recommended Action This is a software issue. The consequences are that the specified request could not be performed. LOG_STD_RECUR_ACTION
%SBC-3-PKT_REPLICA_INIT_FAILED : Register to Generic Packet Replication failed for SBC
Explanation SBC Initialization of packet replication registration failed.
Recommended Action LOG_STD_ACTION
SBC_CFG
%SBC_CFG-3-DBE_CONFIG_FAILURE : An SBC DBE configuration failure has occurred.
Explanation SBC has been unable to apply its DBE configuration.
Recommended Action Attempt to manually reconfigure the SBC DBE. LOG_STD_ACTION
%SBC_CFG-3-MED_NOT_DEL_V4 : IPv4 address(es) deleted ([IP_address] [IP_address], VRF '[chars]'), media addresses/pools not removed.
Explanation One or more IPv4 addresses of an SBC interface were removed while the SBC was still active. Please remove the media addresses/pools later manually. If the media addresses/pools were associated with a VRF then it will be necessary to remove the media addresses/pools by unconfiguring the SBC.
Recommended Action None
%SBC_CFG-3-MED_NOT_DEL_V6 : IPv6 address(es) deleted ([IPV6 address]/[int] VRF '[chars]'), media addresses/pools not removed.
Explanation One or more IPv6 addresses of an SBC interface were removed while the SBC was still active. Please remove the media addresses/pools later manually. If the media addresses/pools were associated with a VRF then it will be necessary to remove the media addresses/pools by unconfiguring the SBC.
Recommended Action None
%SBC_CFG-3-SBC_NOT_CONFIG : SBC is not configured. VOIP LI configuration request failed
Explanation Since SBC is not configured, the VOIP LI request is rejected. First configure SBC and then VOIP LI requests will be processed.
Recommended Action None
%SBC_CFG-3-SERVICE_CHANGE_COLD_BOOT_FAILED : Delayed ServiceChange failed.
Explanation SBC has failed to send the delayed ServiceChange message at boot.
Recommended Action Ensure that the SBC configuration is valid, and perform a manual SBC Activation.
%SBC_CFG-4-BLACKLIST_BLOCKED : Source [chars]: blacklisted, blocked, reason: [chars]
Explanation The source is blacklisted.
Recommended Action None
%SBC_CFG-4-BLACKLIST_CLEARED : Source [chars]: cleared blacklist event or alert, reason: [chars]
Explanation A blacklist event or alert is cleared.
Recommended Action None
%SBC_CFG-4-BLACKLIST_CRITICAL : Source [chars]: critical blacklist alert, reason: [chars]
Explanation A critical blacklist alert has been generated.
Recommended Action None
%SBC_CFG-4-BLACKLIST_MAJOR : Source [chars]: major blacklist alert, reason: [chars]
Explanation A major blacklist alert has been generated.
Recommended Action None
%SBC_CFG-4-BLACKLIST_MINOR : Source [chars]: minor blacklist alert, reason: [chars]
Explanation A minor blacklist alert has been generated.
Recommended Action None
%SBC_CFG-4-SERVICE_CHANGE_COLD_BOOT_DELAY_FAILED : Failed to delay ServiceChange.
Explanation SBC has failed to start a timer for delaying a ServiceChange message at boot. The ServiceChange message will be sent out without a delay.
Recommended Action Ensure that SBC has been fully Activated and that all requested pinholes have been established. LOG_STD_ACTION
%SBC_CFG-6-SERVICE_CHANGE_COLD_BOOT : Delay [chars].
Explanation SBC has been configured to delay sending a ServiceChange message at boot. Upon the delay timer expiring, the ServiceChange message will be sent.
Recommended Action This message is for informational purposes only. A ServiceChange message will be sent out once the delay timer expires.
SBC_HA
%SBC_HA-3-CONFIG_SYNC : SBC failed to cache SBC config of size [dec].
Explanation The SBC module was unable to successfully cache the SBC config on the Standby. The Standby will be unable to write SBC config to NVRAM.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SBC_HA-3-HOLD_PROGRESSION : SBC RF failed to start the progression holding process.
Explanation The SBC module was unable to successfully start the RF progression holding process. RF progression will resume immediately, but if a switchover occurs immediately after the system reaches the Standby Hot redundancy state then some SBC calls may be lost.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SBC_HA-3-ILT_PROC_CREATE : SBC ILT process creation failed.
Explanation The SBC module was unable to successfully create an SBC process. SBC will not be able to operate in a stateful mode.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SBC_HA-3-ILT_REGISTRATION : SBC ILT registration failed.
Explanation The SBC module was unable to successfully register for communication with the peer unit. SBC will not be able to operate in a stateful mode.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SBC_HA-3-ILT_STUB : SBC ILT Stub process creation failed.
Explanation The SBC module was unable to successfully create the ILT Stub process. SBC will not be able to operate in a stateful mode.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SBC_HA-3-INTERNAL : An internal SBC HA error has been encountered[chars].
Explanation An internal error has been encountered.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SBC_HA-3-IPC_INIT : SBC IPC failed to initialise ([chars]).
Explanation The SBC IPC module was unable to successfully initialise. SBC may not be able to operate in a stateful mode.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SBC_HA-3-IPC_RMI_INIT : SBC IPC failed to register with RMI ([chars]).
Explanation The SBC IPC module was unable to successfully register with the Resource Manager. SBC may not be able to operate in a stateful mode.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SBC_HA-3-IPC_SEND : SBC IPC message send failed (error [chars]).
Explanation The SBC module was unable to successfully send a message to its peer. SBC will not be able to operate in a stateful mode.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SBC_HA-3-ISSU_CAPENTRY_REGISTRATION : SBC Cap Entry ([dec]) for Entity ([dec]) Registration failed ([chars]).
Explanation A capability entry could not be registered for SBC ISSU. SBC will not be able to operate in a stateful mode.
Recommended Action LOG_STD_SH_CMD_ACTION(show issu capability entries)
%SBC_HA-3-ISSU_CAPGROUP_REGISTRATION : SBC Cap Group ([dec]) for Entity ([dec]) Registration failed ([chars]).
Explanation A capability group could not be registered for SBC ISSU. SBC will not be able to operate in a stateful mode.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show capability groups command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%SBC_HA-3-ISSU_CAPTYPE_REGISTRATION : SBC Cap Type for Entity ([dec]) Registration failed ([chars]).
Explanation A capability type could not be registered for SBC ISSU. SBC will not be able to operate in a stateful mode.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show issu capability types command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%SBC_HA-3-ISSU_CLIENT_REGISTRATION : SBC Client ([dec]) Registration failed ([chars]).
Explanation The SBC module was unable to successfully register with the ISSU infrastructure. SBC will not be able to operate in a stateful mode.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show issu clients command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%SBC_HA-3-ISSU_ENTITY_REGISTRATION : SBC Entity ([dec]) Registration failed ([chars]).
Explanation The SBC ISSU entity could not be registered. SBC will not be able to operate in a stateful mode.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show issu entities command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%SBC_HA-3-ISSU_MSGGROUP_REGISTRATION : SBC Msg Group ([dec]) for Entity ([dec]) Registration failed ([chars]).
Explanation The message group for SBC ISSU could not be registered. SBC will not be able to operate in a stateful mode.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show issu message groups command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%SBC_HA-3-ISSU_MSG_MTU : SBC Client ([dec]) get msg mtu failed. Error = [dec].
Explanation The SBC ISSU client could not obtain a message of the required size.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show issu fsm command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%SBC_HA-3-ISSU_MSGTYPE_REGISTRATION : SBC Msg Type for Entity ([dec]) Registration failed ([chars]).
Explanation The message type for SBC ISSU could not be registered. SBC will not be able to operate in a stateful mode.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show issu message types command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%SBC_HA-3-ISSU_NEGOTIATION : SBC ISSU negotiation failed.
Explanation The SBC module was unable to successfully negotiate with its peer. SBC will not be able to operate in a stateful mode.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SBC_HA-3-ISSU_REGISTRATION : SBC ISSU failed to register.
Explanation The SBC module was unable to successfully register with the ISSU infrastructure. SBC will not be able to operate in a stateful mode.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SBC_HA-3-ISSU_SESSION_REGISTRATION : SBC session for Entity ([dec]) Registration failed ([chars]).
Explanation The SBC ISSU session could not be registered. SBC will not be able to operate in a stateful mode.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show issu sessions command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%SBC_HA-3-ISSU_START_NEGOTIATION : SBC ISSU negotiation failed to start ([chars]).
Explanation The SBC module was unable to successfully start negotiatiation with its peer. SBC will not be able to operate in a stateful mode.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show issu fsm command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%SBC_HA-3-ISSU_TRANSFORM : SBC ISSU [chars] transformation failed ([chars]).
Explanation The transformation operation for an SBC ISSU message has failed.
Recommended Action LOG_STD_SH_CMD_ACTION(show issu fsm and show issu sessions)
%SBC_HA-3-LARGE_IPS_MSG : SBC failed to receive large sync message of size [dec].
Explanation The SBC module was unable to successfully receive a large sync message on the Standby. The Standby will be will not have an identical dynamic state as the Active.
Recommended Action No action is required.
%SBC_HA-3-LARGE_IPS_MSG_FAIL : SBC failed to send large sync message of size [dec].
Explanation The SBC module was unable to successfully send a large sync message to the Standby because this version of the Standby does not support large messages. The Standby will be will not have an identical dynamic state as the Active.
Recommended Action No action is required.
%SBC_HA-3-LARGE_IPS_UNSUPP : The current version of the SBC Standby does not support the syncing of large SBC contexts
Explanation The current version of the SBC Standby does not support the syncing of large SBC contexts. A context that contains 24 or more media and signaling flows is a large context. It is rare to have such a large context and thus, ISSU compatibility has been permitted even though this difference in support exists. Normal SBC High Availability synchronization will continue to operate successfully as long as no contexts contain more than 24 signaling or media flows. Context information beyond 24 flows will not be replicated and thus on RP switchover the Active RP will not have information about all the contexts
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SBC_HA-3-NO_SYNC_PROCESS : SBC RF failed to start the config sync process.
Explanation The SBC module was unable to successfully start the configuration sync process. The Standby will be unable to fully initialise.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SBC_HA-3-RF_CONFIG_SYNC : SBC RF will not be able to synchronise SBC configuration to the Standby. Failure cause: [chars].
Explanation The SBC module will not be able to synchronise the SBC config to the Standby. The Standby will be unable to write SBC config to NVRAM.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SBC_HA-3-RF_PROGRESSION : SBC RF failed to resume RF progression at state [chars].
Explanation The SBC module was unable to successfully resume RF progression at the noted state. The Standby will be unable to fully initialise.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SBC_HA-3-RF_REGISTRATION : SBC RF failed to register
Explanation The SBC module was unable to successfully register with the RF infrastructure. SBC will not be able to operate in a stateful mode.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SBC_HA-3-RF_TIMER_EXTENSION_EXPIRY : SBC RF progression extension timer expired.
Explanation The SBC module's RF progression extension timer expired. RF progression will resume, but if a switchover occurs immediately after the system reaches the Standby Hot redundancy state then some SBC calls may be lost.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SBC_HA-3-SBC_B2B_RESTART : SBC restart has taken longer than expected. The SBC will be restarted, but may require a shut/no shut of the redundancy group in order to return to stateful HA with the active router.
Explanation SBC process restart timedout, may require manual intervention.
Recommended Action Shut/No shut the standby redundancy group associated with the SBC. LOG_STD_ACTION
%SBC_HA-3-SBC_CAC_ENHANCEMENT_CFG : SBC has detected cac enhancement feature configured which may have branch cli OR cac-scope (adjacency ,account)cli SBC cannot proceed as HA client. Remove all cac enhancement feature config to proceed with ISSU/ISSD.
Explanation Peer SBC does not support cac enhancement feature configuration.
Recommended Action Manually remove cac enhancement feature configuration and reinitiate ISSU. LOG_STD_ACTION
%SBC_HA-3-SBC_CODEC_INTERWORK_CFG : SBC has detected codec configuration which is not supported on the peer. SBC cannot proceed as HA client. Remove all newly entered codec configuration to proceed with ISSU/ISSD.
Explanation Peer SBC does not support codec preference, variant or interwork configuration.
Recommended Action Manually remove newly added codec configuration and reinitiate ISSU. LOG_STD_ACTION
%SBC_HA-3-SBC_DBL_NA_ALERT_CFG : SBC has detected blacklist entries configured which have reason na-policy-failure OR minor, major, critical alerts which is not supported on the peer. SBC cannot proceed as HA client. Remove all blacklist entries with this reason or any alerts configuration to proceed with ISSU/ISSD.
Explanation Peer SBC does not support blacklist reason na-policy-failure or blacklist alerts configuration.
Recommended Action Manually remove blacklist reason na-policy-failure and minor, major or critical alerts configuration and reinitiate ISSU. LOG_STD_ACTION
%SBC_HA-3-SBC_DYNAMIC_CODEC_CFG : SBC has detected Dynamic Codec configuration which is not supported on the peer. SBC cannot proceed as HA client. Remove all codec configuration to proceed with ISSU/ISSD.
Explanation Peer SBC does not support Dynamic Codec configuration.
Recommended Action Manually remove Dynamic Codec configuration and reinitiate ISSU. LOG_STD_ACTION
%SBC_HA-3-SBC_FLEX_MED_RTG_CFG : SBC has detected flexible media routing configuration. This feature is not supported on the peer. SBC cannot proceed as HA client. Remove all flexible media routing config from the configuration to proceed with ISSU/ISSD.
Explanation Peer SBC does not support flexible media routing configuration.
Recommended Action Manually remove flexible media routing from configuration and reinitiate ISSU. LOG_STD_ACTION
%SBC_HA-3-SBC_HA_ADMIN_DOMAIN_CFG : SBC has detected an admin-domain configuration. This feature is not supported on the peer. SBC cannot proceed as HA client. Remove all admin-domain submodes from the configuration to proceed with ISSU/ISSD.
Explanation Peer SBC does not support admin-domain configuration.
Recommended Action Manually remove the admin-domain submodes from configuration and reinitiate ISSU. LOG_STD_ACTION
%SBC_HA-3-SBC_HA_CAC_AVG_PER2_CFG : SBC has detected averaging-period 2 cac configuration. Averaging-period 2 is not supported on the peer. SBC cannot proceed as HA client. Remove the cac-policy-set averaging-period 2 configuration to proceed with ISSU/ISSD.
Explanation Peer SBC does not support averaging-period 2 cac configuration.
Recommended Action Manually remove the cac-policy-set averaging-period 2 configuration and reinitiate ISSU. LOG_STD_ACTION
%SBC_HA-3-SBC_HA_CAC_AVG_PER2_RATE_CFG : SBC has detected cac-policy-set rate limit configuration for averaging-period 2. Averaging-period 2 is not supported on the peer. SBC cannot proceed as HA client. Remove the cac-policy-set rate limit configuration for averaging-period 2 to proceed with ISSU/ISSD.
Explanation Peer SBC does not support cac rate limit configuration for averaging-period 2.
Recommended Action Manually remove the rate limit commands for averaging-period 2 found within the cac-policy-set entry and reinitiate ISSU. LOG_STD_ACTION
%SBC_HA-3-SBC_HA_CAC_PRIVACY_SERV_CFG : SBC has detected cac-policy-set privacy-service configuration for a cac entry. This enhancement is not supported on the peer. SBC cannot proceed as HA client. Remove the cac-policy-set privacy-service related configuration to proceed with ISSU/ISSD.
Explanation Peer SBC does not support cac-policy-set privacy-service configuration for a cac entry.
Recommended Action Manually remove the privacy-service related commands configured within the cac-policy-set entry and reinitiate ISSU. LOG_STD_ACTION
%SBC_HA-3-SBC_HA_CALL_ONA_CFG : SBC has detected first-outbound-na-table configured within a call-policy-set. This command is not supported on the peer. SBC cannot proceed as HA client. Remove all first-outbound-na-table configuration to proceed with ISSU/ISSD.
Explanation Peer SBC does not support first-outbound-na-table configuration within a call-policy-set.
Recommended Action Manually remove the first-outbound-na-table configuration and reinitiate ISSU. LOG_STD_ACTION
%SBC_HA-3-SBC_HA_PORT_TAG_CFG : SBC has detected an port tag configuration. This feature is not supported on the peer. SBC cannot proceed as HA client. Remove all port tag from the configuration to proceed with ISSU/ISSD.
Explanation Peer SBC does not support port tag configuration.
Recommended Action Manually remove the port tag from configuration and reinitiate ISSU. LOG_STD_ACTION
%SBC_HA-3-SBC_IMP_NA_EDITSRC_CFG : SBC has detected number analysis entries that have edit-src actions, which are not supported on the peer. Remove all edit-src actions from all number analysis entries to proceed with ISSU/D
Explanation Peer SBC does not support edit-src actions in number analysis entries.
Recommended Action Manually remove edit-src actions from all number analysis entries and reinitiate ISSU. LOG_STD_ACTION
%SBC_HA-3-SBC_IMP_NA_REGEX_CFG : SBC has detected number analysis entries that match on text addresses, which are not supported on the peer. Remove all regex number analysis entries to proceed with ISSU/D
Explanation Peer SBC does not support regex number analysis entries.
Recommended Action Manually remove regex number analysis entries and reinitiate ISSU. LOG_STD_ACTION
%SBC_HA-3-SBC_IMP_NA_SRCANON_CFG : SBC has detected na-src-name-anonymous number analysis tables, which are not supported on the peer. Remove all na-src-name-anonymous number analysis tables to proceed with ISSU/D
Explanation Peer SBC does not support na-src-name-anonymous number analysis tables.
Recommended Action Manually remove all na-src-name-anonymous number analysis tables and reinitiate ISSU. LOG_STD_ACTION
%SBC_HA-3-SBC_IMS_RF_CFG : SBC has detected ims rf configured. SBC cannot proceed now. Remove all ims rf config to proceed with ISSU/ISSD.
Explanation Peer SBC does not support ims rf configuration.
Recommended Action Manually remove ims rf configuration and reinitiate ISSU. LOG_STD_ACTION
%SBC_HA-3-SBC_IPV6_CFG : SBC has detected configuration/dynamic state ([chars]) which is not supported on the peer.
Explanation Peer SBC does not support IPv6.
Recommended Action Manually remove IPv6 configuration and reinitiate ISSU. LOG_STD_ACTION
%SBC_HA-3-SBC_LRU_CFG : SBC has detected LRU configured SBC cannot proceed now. Remove all LRU CONFIG to proceed with ISSU/ISSD.
Explanation Peer SBC does not support LRU configuration.
Recommended Action Manually remove LRU configuration and reinitiate ISSU. LOG_STD_ACTION
%SBC_HA-3-SBC_MEDIA_ADDRESS_PRESERVE_INIT_NEGO_CFG : SBC has detected media address preserve init-negotiation configured SBC cannot proceed now. Remove all media address preserve init-negotiation config to proceed with ISSU/ISSD.
Explanation Peer SBC does not support media address preserve init-negotiation configuration.
Recommended Action Manually remove media address preserve init-negotiation configuration and reinitiate ISSU. LOG_STD_ACTION
%SBC_HA-3-SBC_MEDIA_BYPASS_NATTAGGEN_CFG : SBC has detected media bypass auto-nat-tag-gen configured SBC cannot proceed now. Remove all media bypass auto-nat-tag-gen config to proceed with ISSU/ISSD.
Explanation Peer SBC does not support media bypass auto-nat-tag-gen configuration.
Recommended Action Manually remove media bypass auto-nat-tag-gen configuration and reinitiate ISSU. LOG_STD_ACTION
%SBC_HA-3-SBC_MESSAGE_EDITING_CFG : SBC has detected message editing configured which may have sip editor_type editor OR parameter-editor OR header-editor OR method-editor OR body-editor OR option-editor which is not supported on the peer. SBC cannot proceed as HA client. Remove all message editing config to proceed with ISSU/ISSD.
Explanation Peer SBC does not support message editing configuration.
Recommended Action Manually remove message editing configuration and reinitiate ISSU. LOG_STD_ACTION
%SBC_HA-3-SBC_MSMB_CFG : SBC has detected Multi SBC Media Bypass configuration which is not supported on the peer. SBC cannot proceed as HA client. Remove all Multi SBC Media Bypass configuration to proceed with ISSU/ISSD.
Explanation Peer SBC does not support Multi SBC Media Bypass configuration.
Recommended Action Manually remove Multi SBC Media Bypass configuration and reinitiate ISSU. LOG_STD_ACTION
%SBC_HA-3-SBC_QOS_DEMARCATION_CFG : SBC has detected qos demarcation configured which may have statistics threshold OR g107a factor OR cal_moscqe OR g107 bpl OR g107 ie OR qos trap configured ,which is not supported on the peer. SBC cannot proceed as HA client. Remove all qos demarcation config to proceed with ISSU/ISSD.
Explanation Peer SBC does not support qos demarcation configuration.
Recommended Action Manually remove qos demarcation configuration and reinitiate ISSU. LOG_STD_ACTION
%SBC_HA-3-SBC_RG_NO_CLIENT : SBC was unable to register the RG Client with the RG infrastructure for inter-chassis HA.
Explanation SBC will not be able to support inter-chassis HA.
Recommended Action No action is required.
%SBC_HA-3-SBC_RG_NO_PROCESS : SBC was unable to start a process used by the RG client
Explanation SBC will not be able to support inter-chassis HA.
Recommended Action No action is required.
%SBC_HA-3-SBC_RG_NO_SOCKET : SBC was unable to open a socket for the RG client
Explanation SBC will not be able to support inter-chassis HA.
Recommended Action No action is required.
%SBC_HA-3-SBC_RG_NO_TRANSPORT : SBC was unable to register a transport with the RG infrastructure for inter-chassis HA.
Explanation SBC will not be able to support inter-chassis HA.
Recommended Action No action is required.
%SBC_HA-3-SBC_RG_NO_VRF : SBC VRF mismatch between active and standby, please add [chars]
Explanation SBC may fail to fully support SSO
Recommended Action No action is required.
%SBC_HA-3-SBC_RG_SOCK_FAIL : SBC lost connection with RG peer, socket failure [chars], len=[dec]
Explanation SBC HA may be disabled until peer connection is established.
Recommended Action No action is required.
%SBC_HA-3-SBC_RG_VRF_INUSE : VRF is used by SBC, add back or remove from active, please add [chars]
Explanation SBC may fail to fully support SSO
Recommended Action No action is required.
%SBC_HA-3-SBC_SDP_EDITING_CFG : SBC has detected sdp editing configured which may have script-set OR active-script-set OR test script-set on any adjacency configured which is not supported on the peer. SBC cannot proceed as HA client. Remove all sdp editing config to proceed with ISSU/ISSD.
Explanation Peer SBC does not support sdp editing configuration.
Recommended Action Manually remove sdp editing configuration and reinitiate ISSU. LOG_STD_ACTION
%SBC_HA-3-SBC_SIPS_H323_INTWK_CFG : SBC has detected SIPS-H323 Interworking configured which may have trusted H323 Adjacencies or secure calls configured which is not supported on the peer. SBC cannot proceed as HA client. Remove all SIPS-H323 Interworking config to proceed with ISSU/ISSD.
Explanation Peer SBC does not support SIPS-H323 Interworking configuration.
Recommended Action Manually remove SIPS-H323 Interworking configuration and reinitiate ISSU. LOG_STD_ACTION
%SBC_HA-3-SBC_SUBSCRIBER_TCP_CFG : SBC has detected subscriber tcp configured which may have subscriber tcp incoming-only configured which is not supported on the peer. SBC cannot proceed as HA client. Remove all subscriber tcp config to proceed with ISSU/ISSD.
Explanation Peer SBC does not support susbscriber tcp configuration.
Recommended Action Manually remove subscriber tcp configuration and reinitiate ISSU. LOG_STD_ACTION
%SBC_HA-3-SBC_VIA_PASSTHROUGH_CFG : SBC has detected Via Passthrough configured SBC cannot proceed now. Remove all Via Passthrough CONFIG to proceed with ISSU/ISSD.
Explanation Peer SBC does not support Via Passthrough configuration.
Recommended Action Manually remove Via Passthrough configuration and reinitiate ISSU. LOG_STD_ACTION
%SBC_HA-3-SBC_XML_BILLING_CFG : SBC has detected Xml Billing configuration which is not supported on the peer. SBC cannot proceed as HA client. Remove all xml billing configuration to proceed with ISSU/ISSD.
Explanation Peer SBC does not support Xml Billing configuration.
Recommended Action Manually remove Xml Billing configuration and reinitiate ISSU. LOG_STD_ACTION
%SBC_HA-3-WATCH_PROGRESSION : SBC RF failed to create progression watch points.
Explanation The SBC module was unable to successfully create the RF progression watch points. RF progression will not be suspended at bulk synchronisation time, so some SBC calls may be lost if a switchover occurs immediately after the system reaches the Standby Hot redundancy state.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SBC_HA-4-ISSU_GET_BUFFER : SBC ISSU session failed to get buffer.
Explanation The SBC ISSU client failed to get a buffer. Some High-Availability SBC information may be missing from the peer.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show processes memory command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
SBC_MPS
%SBC_MPS-3-ENQUEFAIL : Enqueue of TDL message failed ([chars]).
Explanation An unexpected condition has occurred which resulted in configuration or event details not being forwarded.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SBC_MPS-3-INITFAIL : SBC module initialisation failure: [chars].
Explanation An unexpected condition has occurred which resulted in the module being unable to initialise.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SBC_MPS-3-INTERNAL : An internal IOSd SBC error has been encountered[chars].
Explanation An internal error has been encountered.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SBC_MPS-3-MAX_RESOURCES : The maximum resource limit has been reached.
Explanation The system was asked to allocate more resources, but the maximum resource limit had already been reached
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SBC_MPS-3-UNEXPECTED_TIMOUT : An unexpected timeout has been encountered by SBC ([chars]).
Explanation A timeout was experienced by the IOSd SBC subsystem, but no such timeout should have occurred. The system will ignore the timeout and continue operating.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SBC_MPS-4-MPF_CAPABILITIES : SBC MPF Capabilities handling failure.
Explanation SBC has been unable to properly prepare a Media Packet Forwarding capabilities message. SBC may not be able to support select functionality such as transcoding or SRTP.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SBC_MPS-4-MPF_SRTP_CAPABILITIES : Unable to set SRTP capabilities
Explanation SBC made an attempt to set the platform capabilities with respect to its handling of SRTP streams and was not successful. SRTP streams will not be handled through the SBC.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SBC_MPS-4-NEW_MPF_CAPABILITIES : New SBC MPF Capabilities handling failure.
Explanation SBC has received a new set of Media Packet Forwarding capabilities from the associated Forwarding Processor that are inconsistent with those already in use. SBC was unable to process these new capabilities online, and will automatically restart.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SBC_MPS-4-TRANSCODE_MPF_CAPABILITIES : Transcoding SBC MPF Capabilities handling failure.
Explanation SBC has been unable to prepare a transcoding supported Media Packet Forwarding capabilities message. SBC will not be able to support transcoding functionality.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SBC_MPS-4-UNEXPECTED_PKT : An unexpected packet for call [dec] has been received by SBC.
Explanation A packet been received by SBC for the noted call, but the call was not in a correct state to handle it. The system will ignore the packet and continue operating.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SBC_MPS-6-DEACTIVATE_NO_RSP : SBC deactivate response is considered lost.
Explanation The response for SBC deactivate can get lost due to FP startup or switchover while deactivation is in progress.
Recommended Action SBC can be activated now if needed.
%SBC_MPS-6-DEACTIVATE_RESPONSE : SBC deactivate is complete.
Explanation SBC deactivation can take a while. This happens when SBC deactivation is done in the presence of a lot calls with deactivation-mode set to abort. SBC deactivate is now complete.
Recommended Action SBC can be safely activated now if needed.
%SBC_MPS-6-UNEXPECTED_TDL : An unexpected message ([chars]) has been received by SBC while in the [chars] state.
Explanation An internal message has been received by SBC, but it was not expecting that message at that particular time. The system will ignore the message and continue operation.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
SBC_SPF
%SBC_SPF-3-ENQUEFAIL : Enqueue of TDL message failed ([chars]).
Explanation An unexpected condition has occurred which resulted in configuration or event details not being forwarded.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SBC_SPF-3-INTERNAL : An internal IOSd SBC error has been encountered[chars].
Explanation An internal error has been encountered.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SBC_SPF-3-NOT_FOUND : An unsolicited message has been received by SBC ([chars] [int])
Explanation An internal message has been received by SBC, but it was not expecting that message at that particular time. The system will ignore the message and continue operation.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
SCC
%SCC-3-XCVR_BAD_ID_HW : Failed identification test in [dec]/[dec]/[dec].
Explanation The Transceiver in the specified port has failed authentication.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
SCHED_TEST
%SCHED_TEST-2-EXITHOOK : Exit routine invoked for process [chars].
Explanation None
Recommended Action None
%SCHED_TEST-6-ERRMSG : This errmsg should print correctly.
Explanation None
Recommended Action None
SCOOBY
%SCOOBY-0-SERIAL_BRIDGE_CRITICAL_ERROR : Reloading [chars] due critical event [hex] in block [chars]/[dec] of serial bridge [dec]
Explanation A critical serial bridge I/O event has occurred.
Recommended Action The system automatically reloads the hardware component experiencing the error. If the problem persists, copy the message exactly as it appears on the console or in the system log, collect the output of show tech-support and any other relevant logs, and contact your Cisco technical support representative.
%SCOOBY-0-SERIAL_BRIDGE_CRITICAL_ERROR_RATE : Reloading [chars] due to critically high serial bridge error rate.
Explanation A Serial Bridge has experienced a persistently high error rate. The condition is serious and the card must be reloaded. This could be due to a hardware or software driver defect.
Recommended Action Copy the message exactly as it appears on the console or in the system log, collect the output of show tech-support and any other relevant logs, and contact your Cisco technical support representative.
%SCOOBY-5-SERIAL_BRIDGE_BLOCK_EVENT : Block [chars]/[dec] of serial bridge [dec] had I/O event [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.
%SCOOBY-5-SERIAL_BRIDGE_EVENT_RATE : The [chars] event rate of [int] has exceeded the threshold of [int] on serial bridge [dec] interconnect [dec]
Explanation A Serial Bridge has experienced a high event rate. This condition is not considered serious, but is logged for diagnostic purposes. This could be due to a hardware or software driver defect.
Recommended Action No user action is required. If this message persists, a serial bridge critical message that needs to be addressed will appear.
SDLC
%SDLC-2-ILLEGSTATE : [chars], illegal state for addr [hex], [chars]([dec])
Explanation An internal SDLC state violation was detected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%SDLC-2-NOMEMORY : No memory available: [chars]
Explanation The requested operation failed 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.
%SDLC-2-NOPOINTER : AW_SDLC_SEC with no sdllc_llc pointer.
Explanation An error condition occurred during SDLLC initiation.
Recommended Action No action is required. The SDLLC session will restart without operator intervention.
%SDLC-3-CONFIGERR : [chars], addr [hex], Sent SNRM, received SNRM. Check link station roles.
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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SDLC-3-DLU_ERROR : [chars], DLU failed to close station [hex] before re-opening, [chars]/[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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SDLC-3-NOINPIDB : Input idb not set
Explanation This is a software error. A frame was given to the SDLC handler to process, but the interface on which the frame arrived is not known.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%SDLC-3-NULLPAK : Interface [chars], NULL packet ptr, rvr [dec], vs [dec], vr [dec]
Explanation An internal software error occurred in the router's SDLC processing system.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%SDLC-4-BADFRAME : [chars], Received bad SDLC [chars]frame, address [hex], control [hex]
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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SDLC-4-CTRLBAD : Interface [chars], Invalid control field
Explanation A bad SDLC frame was received.
Recommended Action If this message recurs, check the SDLC serial line and the devices attached to it.
%SDLC-4-DROPPED : Dropped SDLC packet from SDLC hold queue
Explanation An SDLC frame had to be dropped from the output hold queue, usually because of excessive congestion on the output link.
Recommended Action If this message occurs frequently, determine why your SDLC link is being overloaded with data and resolve the cause (typically by either increasing bandwidth to your SDLC line or reducing the load on your link).
%SDLC-4-FRAMEERR : Interface [chars], Frame error: CF [hex], VS [dec] %c VR [dec], Reason [hex]
Explanation A FRMR frame was received. This can be due to a noisy serial line, an overloaded SDLC device, or corrupted data.
Recommended Action If this message recurs, service the serial line and the devices attached to it.
%SDLC-4-INFOBAD : Interface [chars], Info field not permitted
Explanation A bad SDLC frame was received.
Recommended Action If this message recurs, check the SDLC serial line and the devices attached to it.
%SDLC-4-INVLDGRPCFG : Interface [chars], ignoring group-poll mismatch, UPOLL [hex]
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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SDLC-4-INVNR : Interface [chars], Invalid NR value
Explanation A bad SDLC frame was received.
Recommended Action If this message recurs, check the SDLC serial line and the devices attached to it.
%SDLC-4-N1TOOBIG : Interface [chars], N1 too large
Explanation An information frame was received from the other end of the SDLC link that was larger than allowed with the N1 parameter on this link.
Recommended Action Either increase the value of the N1 parameter for this interface on the router or reduce the size of the maximum information frame sent by the other end of the link.
%SDLC-4-NOUA : [chars], addr [hex] received command [hex] in response to SNRM, expected UA
Explanation The router received a frame other than a UA in response to a SNRM.
Recommended Action Check the end station to see if the SNA stack is up and running.
%SDLC-4-SDLC_ERR : SDLC_ERROR with no poll
Explanation A protocol error was detected on a secondary station, but FRMR could not be sent because the station did not own the poll bit. This message indicates either poor line conditions or a faulty SDLC implementation.
Recommended Action If this message recurs, run traces on the SDLC line. Copy the error message exactly as it appears, and report it to your technical support representative.
%SDLC-4-XID_NOMATCH : [chars], XID mismatch for [hex]. CONNECTION REJECTED
Explanation An inbound exchange identification (XID) from a PU 2.0/PU 2.1 node was rejected. The targeted SDLC address is displayed. The XID information is displayed in a subsequent message = SDLLC-6-XID_DISPLAY or SDLLC-6-FORMAT.
Recommended Action This is a security feature. Additional information is displayed to help trace the source of the rejected XID. If the message is undesirable, simply remove the XID statement from the router configuration.
%SDLC-5-INVLDGRPPOLL : Interface [chars], not configured for group-poll frame, received [hex]
Explanation An unnumbered poll (UP) was received with the wrong group poll address.
Recommended Action Make sure the group poll address configured on the router matches the one configured in the physical unit macro (GP3174=XX) in the Network Control Program (NCP) generate file.
%SDLC-6-XID_DISPLAY : sa [enet] da [enet] ss [hex] ds [hex] [[hex][hex][hex][hex]]
Explanation This message supplies the information for the received and rejected XID.
Recommended Action See the SDLC-6-XID_NOMATCH error message.
%SDLC-6-XID_FORMAT : Unsupported XID format received, format [dec]
Explanation An inappropriate exchange identification (XID) format was received for this mode of SDLLC operation. Review the type of devices you are connecting with SDLLC to make sure they are supported.
Recommended Action See the SDLLC-6-XID_NOMATCH error message.
SDLLC
%SDLLC-5-ACT_LINK : SDLLC: [chars] LINK address [hex] ACTIVATED: [chars]
Explanation An SDLLC media conversion session was activated.
Recommended Action No action is required.
%SDLLC-5-DACT_LINK : SDLLC: [chars] LINK address [hex] DEACTIVATED: [chars]
Explanation An SDLLC media conversion session was deactivated. If deactivation is a result of an error condition, this message will include a reason.
Recommended Action If the message does not include a description of an error, the deactivation was normal and the message is for information only. If the message does include a description of an error, begin problem analysis. Determine whether session loss is related to LLC2 timers by issuing the debug llc2-err command. If the problem is related to LLC2 timers, consider using SDLLC with the local acknowledgment feature. Copy the error message exactly as it appears, and report it to your technical support representative.
SEC
%SEC-2-NOOPT : Box secured, no option on internal packet
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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%SEC-2-NOTSEC : First opt in tcb not BASIC security
Explanation An internal software error occurred.
Recommended Action If this message recurs, contact your technical support representative.
%SEC-2-SECINS : Security opt in tcb not SECINSERT
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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%SEC-3-NOMAX : No default for NLESO defined
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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%SEC-4-SHELFCTLRTELOPT : malformed option on vty%t %c%c%c[dec] len [dec] [chars]
Explanation A packet containing shelf controller telnet options was malformed. Options were ignored or truncated.
Recommended Action No action is required.
%SEC-4-TOOMANY : Box secured, too many options on internal packet
Explanation No room for all desired IP header options. Packet discarded.
Recommended Action Configure for fewer IP header options.
%SEC-6-IPACCESSLOGDP : list [chars] [chars] [chars] [IP_address] [chars]-> [IP_address] ([dec]/[dec]), [dec] packet[chars] [chars]
Explanation A packet matching the log criteria for the given access list was detected.
Recommended Action No action is required.
%SEC-6-IPACCESSLOGNP : list [chars] [chars] [dec] [IP_address] [chars]-> [IP_address], [dec] packet[chars] [chars]
Explanation A packet matching the log criteria for the given access list was detected.
Recommended Action No action is required.
%SEC-6-IPACCESSLOGP : list [chars] [chars] [chars] [IP_address]([dec]) [chars]-> [IP_address]([dec]), [dec] packet[chars] [chars]
Explanation A packet matching the log criteria for the given access list was detected.
Recommended Action No action is required.
%SEC-6-IPACCESSLOGRL : access-list logging rate-limited or missed [dec] packet[chars]
Explanation Some packet matching logs were missed because the access list log messages were rate-limited or no access list log buffers were available.
Recommended Action No action is required.
%SEC-6-IPACCESSLOGRP : list [chars] [chars] [chars] [IP_address] [chars]-> [IP_address], [dec] packet[chars] [chars]
Explanation A packet matching the log criteria for the given access list wasdetected.
Recommended Action No action is required.
%SEC-6-IPACCESSLOGS : list [chars] [chars] [IP_address] [dec] packet[chars] [chars]
Explanation A packet matching the log criteria for the given access list was detected.
Recommended Action No action is required.
SEC_LOGIN
%SEC_LOGIN-1-QUIET_MODE_ON : Still timeleft for watching failures is [int] secs, [user: [chars]] [Source: [chars]] [localport: [int]] [Reason: [chars]] [ACL: [chars]] at [chars]
Explanation Quiet Mode is ON. No request for connection is accepted other than allowed by the Access List, if configured for the blocking period. Else an implicity *deny all* login's will be in force
Recommended Action As all the requests from other sources are blocked check ACL and add any source addr. if needed.
%SEC_LOGIN-3-INIT_FAILED : Secure Login Initialization failed. [chars]
Explanation Initialization of Secure Login Subsystem failed
Recommended Action Copy the error message exactly as it appears; include the stack trace; and report it to your technical support representative.
%SEC_LOGIN-4-LOGIN_FAILED : Login failed [user: [chars]] [Source: [chars]] [localport: [int]] [Reason: [chars]] at [chars]
Explanation Invalid User Name or Password is given from terminal.
Recommended Action A notification to indicate that login failed
%SEC_LOGIN-5-LOGIN_SUCCESS : Login Success [user: [chars]] [Source: [chars]] [localport: [int]] at [chars]
Explanation A successful login happened with the device.
Recommended Action A notification that login succeeded.
%SEC_LOGIN-5-QUIET_MODE_OFF : Quiet Mode is OFF, because [chars] at [chars]
Explanation Quiet Mode is OFF. Router now operates in normal connection processing mode
Recommended Action A notification that the device now operates in normal connection processing mode and the reason why it switched mode is also indicated with the notification.
SENSORMGR
%SENSORMGR-3-NOMEM : Sensor manger failed to allocate memory : [chars]
Explanation The sensor manager was not able to add a new threshold node to its database.
Recommended Action TBD
SERDES
%SERDES-3-SERDES_CRITICAL_ERROR : Critial error [chars] in FRU [chars] when [chars]
Explanation A critical error was occurred. The condition is serious and the card must be reloaded. This could be due to bad or unknown hardware (chassis or modules). Chassis Manager could also initialize the Serdes library with incorrect input parameters.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Collect the output of show platform, show verson, show log, sh diag chassis eeprom detail, show diagnostic slot <slot#> eeprom detail, and any other relevant logs. Contact your Cisco technical support representative.
%SERDES-5-SERDES_NOTICE : from FRU [chars], [chars].
Explanation CMAN sends a significant Serdes event to IOSD to log it
Recommended Action No action is required for this notice.
SERIAL_12IN1
%SERIAL_12IN1-1-CLOCKRATE : [chars]:Link has been brought [chars] due to clock rate change, threshold configured = [int], received clock rate = [int]
Explanation The received clock rate is changed from below the threshold configured to above or vice versa..
Recommended Action Check the received clock rate from the provider end and the clockrate threshold configuration, if the clock rate goes below the threshold configured, interface is brought down
%SERIAL_12IN1-3-SPI4_ERR : SPA [dec]/[dec]: [chars] was encountered. Intr status: [hex]
Explanation The SPA driver detected a Hardware error condition on the SPA card. This might result in improper operation.
Recommended Action The SPA driver has encountered a Hardware error on the SPA's SPI4 bus. 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 TAC_CASE_OPEN or contact your Cisco technical support representative and provide the representative with the information you have gathered. Be sure to attach to your case the output of the show logging, show monitor event-log spa all and show tech-support commands, your troubleshooting logs, and the specific error message.
%SERIAL_12IN1-3-SW_ERR_1 : [chars]: A software error was encountered at [chars]: [chars] [hex]
Explanation The SPA driver detected a software error condition on the SPA card. This might result in improper operation.
Recommended Action The SPA driver has encountered a software error. Please power down and reseat the indicated SPA card. Copy the error message exactly as it appears and open a case with the Technical Assistance Center via the Internet at TAC_CASE_OPEN or contact your Cisco technical support representative and provide the representative with the information you have gathered. Be sure to attach to your case the output of the show logging, show monitor event-log spa all and show tech-support commands, your troubleshooting logs, and the specific error message.
%SERIAL_12IN1-3-SW_ERR_2 : [chars]: A software error was encountered at [chars]: [chars] [hex]/[hex]
Explanation The SPA driver detected a software error condition on the SPA card. This might result in improper operation.
Recommended Action The SPA driver has encountered a software error. Please power down and reseat the indicated SPA card. Copy the error message exactly as it appears and open a case with the Technical Assistance Center via the Internet at TAC_CASE_OPEN or contact your Cisco technical support representative and provide the representative with the information you have gathered. Be sure to attach to your case the output of the show logging, show monitor event-log spa all and show tech-support commands, your troubleshooting logs, and the specific error message.
%SERIAL_12IN1-3-SW_ERR : [chars]: A software error was encountered at [chars]: [chars]
Explanation The SPA driver detected a software error condition on the SPA card. This might result in improper operation.
Recommended Action The SPA driver has encountered a software error. Please power down and reseat the indicated SPA card. Copy the error message exactly as it appears and open a case with the Technical Assistance Center via the Internet at TAC_CASE_OPEN or contact your Cisco technical support representative and provide the representative with the information you have gathered. Be sure to attach to your case the output of the show logging, show monitor event-log spa all and show tech-support commands, your troubleshooting logs, and the specific error message.
SERVICE_CHAIN
%SERVICE_CHAIN-3-ALLOC_FAILED : Allocation of [chars] memory failed for Service Chaining feature
Explanation Allocation of memory by the Service Chaining 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SERVICE_CHAIN-3-PKT_REPLICA_INIT_FAILED : Failed to register with generic packet replication for Service Chaining feature
Explanation Service Chaining initialization of packet replication registration failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
SERVICES
%SERVICES-0-INVALID_OWNERSHIP : Error using service handle [IPV6 address] -invalid ownership ([IPV6 address], [IPV6 address])
Explanation A multi-thread application is trying to incorrectly use the services library. Applications must follow thread confinement strategy with the services library. Each thread of the application must initialize private managed context of the service library.
Recommended Action Copy the error message, tracebacks and version information and contact a Cisco representative.
%SERVICES-2-NOINIT : Error initializing services: [chars]
Explanation An application failed to initialize the core services library. The application will not be able to communicate with other modules on the system.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%SERVICES-2-NORESOLVE_ACTIVE : Error resolving active FRU: [chars]
Explanation An application was not able to determine the active FRU. The application was likely started incorrectly.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%SERVICES-2-NORESOLVE_LOCAL : Error resolving local FRU: [chars]
Explanation An application was not able to determine its local FRU. The application was likely started incorrectly.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%SERVICES-2-NORESOLVE_STANDBY : Error resolving standby FRU: [chars]
Explanation An application was not able to determine the standby FRU. The application was likely started incorrectly.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%SERVICES-3-INVALID_CHASFS : Thread [IPV6 address] has no global chasfs context
Explanation A multi-thread application is trying to incorrectly use the services library. Applications must follow thread confinement strategy with the services library. Each thread of the application must initialize private managed context of the service library.
Recommended Action Copy the error message, tracebacks and version information and contact a Cisco representative.
SESSION_MGR
%SESSION_MGR-0-CONFIG_CORRUPT :
Explanation Interface configuration field was modified unexpectedly.
Recommended Action No action is required.
%SESSION_MGR-4-ILLEGAL_TRACE_REQ :
Explanation Component ID %d not registered.
Recommended Action No action is required.
%SESSION_MGR-4-UNAUTH_MOVE :
Explanation Move while not authenticated on old IDB
Recommended Action No action is required.
%SESSION_MGR-5-FAIL :
Explanation Authorization was unsuccessful.
Recommended Action Authorization was unsuccessful for the client. Collect the smd logs and system console logs
%SESSION_MGR-5-MACMOVE :
Explanation Client has moved to a new interface without logging off on the previous one.
Recommended Action No action is required.
%SESSION_MGR-5-MACREPLACE :
Explanation A new client has triggered a violation causing an existing client to be replaced
Recommended Action No action is required.
%SESSION_MGR-5-SECURITY_VIOLATION :
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 host count attached. Enter the shutdown command followed by no shutdown command to restart the port.
%SESSION_MGR-5-START :
Explanation Starting an authentication method
Recommended Action Message notification informing about the session manager client is being started to authenticate the endpoint attached to the interface
%SESSION_MGR-5-SUCCESS :
Explanation Authorization was successful.
Recommended Action Client connected to the switch has been successfully authorized by the session manager framework
%SESSION_MGR-5-VLANASSIGN :
Explanation VLAN assignment to an interface for the session
Recommended Action No action is required.
%SESSION_MGR-7-NOMOREMETHODS :
Explanation All available authentication methods have been tried
Recommended Action No action is required.
%SESSION_MGR-7-STOPPING :
Explanation Stopping the current authentication method
Recommended Action No action is required.
SFP
%SFP-3-EEPROM_DUP_ERR : SFP on ports [chars] and [chars] have duplicate serial numbers
Explanation The GBIC/SFP was identified as a Cisco GBIC, but its vendor id and serial number match that of another GBIC on the system.
Recommended Action Report to Cisco tech support.
%SFP-3-NOT_COMPATIBLE : Detected for SFP module in [chars], module disabled
Explanation The SFP module for the interface specified in the error message is not compatible with the interface. As a result of the error, the module is disabled.
Recommended Action Replace the module with a compatible SFP.
%SFP-3-NOT_SUPPORTED : Detected for SFP module in [chars], module disabled
Explanation The SFP module for the interface specified in the error message is not a cisco supported module. As a result of the error, the module is disabled.
Recommended Action Replace the module with a cisco supported SFP.
%SFP-4-EEPROM_CRC_ERR : EEPROM checksum error for SFP in [chars]
Explanation The SFP in the port specified in the error message has invalid EEPROM data.
Recommended Action Remove the SFP from the specified port.
%SFP-4-EEPROM_READ_ERR : Error in reading SFP serial ID in [chars]
Explanation Error when reading SFP type from EEPROM
Recommended Action Please remove SFP from this Port
%SFP-4-EEPROM_SECURITY_ERR : SFP in [chars] failed security check
Explanation The SFP in the port specified in the error message has invalid EEPROM data.
Recommended Action Remove the SFP from the specified port.
%SFP-4-REMOVED : SFP module removed from [chars]
Explanation The online insertion and removal (OIR) facility detected the removal of a SFP module from the interface specified in the error message.
Recommended Action No action is required.
%SFP-6-INSERTED : SFP module inserted in [chars]
Explanation The online insertion and removal (OIR) facility detected a newly inserted SFP module for the interface specified in the error message.
Recommended Action No action is required.
SGBP
%SGBP-1-AUTHFAILED : Member [chars] failed authentication
Explanation This message is generated only when SGBP hellos or errors debugging is enabled. This indicates that an attempted peer connection ended in authentication failure. A peer may be misconfigured. Or this could indicate an attempted security breach.
Recommended Action Check if the peer is correctly configured. If there is a chance your network is under attack, obtain knowledgeable assistance. LOG_STD_ACTION
%SGBP-1-DIFFERENT : Rcv [chars]'s addr [IP_address] is different from the hello's addr [IP_address]
Explanation The internally-configured address for an SGBP member does not match the address of the host that tried to authenticate as that member. The configuration is incorrect on either this system or the other member - they must agree.
Recommended Action Determine which configuration is in error and fix it.
%SGBP-1-DUPLICATE : Rcv Duplicate bundle [chars] is found on member [chars]
Explanation This message is generated only when SGBP hellos or errors debugging is enabled. This indicates that a duplicate bundle was received from the same peer more than once. The duplicate was discarded.
Recommended Action LOG_STD_RECUR_ACTION
%SGBP-1-MISSCONF : Possible misconfigured member [chars] using [IP_address]
Explanation This message is generated only when SGBP hellos or error debugging is enabled. This indicates a configuration error. Either this router has an incorrect IP address listed for the peer or the peer is using an incorrect IP address.
Recommended Action Find and correct the configuraton error.
%SGBP-1-NOTAUTH : Rcv Connection request by non-authenticated member [chars]
Explanation None
Recommended Action None
%SGBP-1-UNKNOWNHELLO : Rcv Hello message from non-group member using [IP_address]
Explanation This message is generated only when SGBP hellos or error debugging is enabled. An SGBP Hello message was received from a host that is not a member of the SGBP group, and discarded.
Recommended Action This is a configuration error. Either that host should be listed in this router's configuration as a member (if that is actually true) or the other host is misconfigured to attempt to join this group.
%SGBP-3-INVALID : MQ message with [chars]
Explanation This message is generated only when SGBP error debugging is enabled. An invalid message was received and discarded.
Recommended Action This probably indicates an error in network media or a peer which is generating erroneous packets.
%SGBP-3-INVALIDADDR : Stack group [chars] IP address [IP_address]
Explanation The current configuration does not allow a local IP address to be configured using sgbp member <address>. Any local address is automatically removed fro the SGBP group.
Recommended Action Do not configure sgbp member <address> using a local IP address.
%SGBP-3-INVALIDB : [chars] for bundle '[chars]' --[chars]
Explanation An internal software error has occurred.
Recommended Action LOG_STD_ACTION
%SGBP-3-INVFIELD : [chars] field type [hex] has [chars] [dec] (expected [dec])
Explanation This message indicates that an SGBP request from a peer contained invalid or corrupt data.
Recommended Action Check the peer equipment or network media for any problems.
%SGBP-3-PEERERROR : Peer [IP_address] [chars] during 'PB [chars]' state for bundle [chars]
Explanation An internal software error has occurred.
Recommended Action LOG_STD_ACTION
%SGBP-3-TIMEOUT : Peer [IP_address] bidding; state 'PB [chars]' deleted
Explanation This message is generated only when SGBP event debugging is enabled. It indicates that a peer timed out while closing a query. The connection has been dropped.
Recommended Action Check the peer equipment and network media for problems.
%SGBP-3-UNEXP : MQ [chars] from [IP_address] for query [dec]:[dec], bundle [chars], bid [dec], state [chars]
Explanation This message is generated only when SGBP error debugging is enabled. The SGBP connection has entered an unexpected state, possibly due to a software error.
Recommended Action LOG_STD_ACTION
%SGBP-3-UNKNOWN : [IP_address] not known
Explanation This message is generated only when SGBP error debugging is enabled. An SGBP connection was attempted by a host which was not recognized as a peer. The connection was not accepted.
Recommended Action Depending on the network topology and firewalling, SGBP connection attempts from a non-peer host could indicate probing and attempts to breach security. If there is a chance your network is under attack, obtain knowledgeable assistance. LOG_STD_ACTION
%SGBP-3-UNKNOWNEVENT : Event [hex] from peer at [IP_address]
Explanation This message is generated only when SGBP error debugging is enabled. An invalid event occurred, which probably indicates an internal software error.
Recommended Action LOG_STD_ACTION
%SGBP-3-UNKNOWNPEER : Event [hex] from peer at [IP_address]
Explanation This message is generated only when SGBP error debugging is enabled. An SGBP event came from a network host which was not recognizable as an SGBP peer. The event was discarded.
Recommended Action Check if a network media error could have corrupted the address, or if peer equipment is malfunctioning to generate corrupted packets. Depending on the network topology and firewalling, SGBP packets from a non-peer host could indicate probing and attempts to breach security. If there is a chance your network is under attack, obtain knowledgeable assistance. LOG_STD_ACTION
%SGBP-5-ARRIVING : New peer event for member [chars]
Explanation This message is generated only when SGBP event debugging is enabled. An SGBP peer joined the group.
Recommended Action LOG_STD_NO_ACTION
%SGBP-5-LEAVING : Member [chars] leaving group [chars]
Explanation This message is generated only when SGBP event debugging is enabled. An SGBP peer has left the group.
Recommended Action LOG_STD_NO_ACTION
%SGBP-5-SHUTDOWN : [chars]
Explanation This message is generated only when SGBP event debugging is enabled. A process involved in SGBP was terminated upon completion of its work.
Recommended Action LOG_STD_NO_ACTION
%SGBP-5-STARTUP : [chars]
Explanation This message is generated only when SGBP event debugging is enabled. An process involved in SGBP was started.
Recommended Action LOG_STD_NO_ACTION
%SGBP-7-ACTIVE : Member [chars] State -> Active
Explanation This message is generated only when SGBP errors or events debugging is enabled. This indicates that a link to another SGBP member has completed the interactions to set it up and is now entering the active state.
Recommended Action LOG_STD_NO_ACTION
%SGBP-7-AUTHOK : Member [chars] State -> AuthOK
Explanation This message is generated only when SGBP errors or events debugging is enabled. A message was received from another SGBP member indicating that an authentication attempt to that member succeeded.
Recommended Action LOG_STD_NO_ACTION
%SGBP-7-CANCEL : Local query #[dec]:[dec] for bundle [chars]
Explanation This message is generated only when SGBP query debugging is enabled. It provides information about queries in progress.
Recommended Action LOG_STD_NO_ACTION
%SGBP-7-CHALLENGE : Send Hello Challenge to [chars] group [chars]
Explanation This message is generated only when SGBP hellos debugging is enabled. This indicates that an authentication challenge was sent to a peer.
Recommended Action LOG_STD_NO_ACTION
%SGBP-7-CHALLENGED : Rcv Hello Challenge message from member [chars] using [IP_address]
Explanation This message is generated only when SGBP hellos debugging is enabled. This indicates that an authentication challenge was received from a peer.
Recommended Action LOG_STD_NO_ACTION
%SGBP-7-CLOSE : Closing pipe for member [chars]
Explanation This message is generated only when SGBP event debugging is enabled. An interprocess communication link was closed.
Recommended Action LOG_STD_NO_ACTION
%SGBP-7-DONE : Query #[dec] for bundle [chars], count [dec], master is [chars]
Explanation This message is generated only when SGBP query debugging is enabled. It provides information about queries in progress.
Recommended Action LOG_STD_NO_ACTION
%SGBP-7-DUPL : Duplicate local query #[dec] for [chars], count [dec], ourbid [dec]
Explanation This message is generated only when SGBP query debugging is enabled. It provides information about queries in progress.
Recommended Action LOG_STD_NO_ACTION
%SGBP-7-EQUAL : [dec] equal highest bids, randomly select bid# [dec]
Explanation This message is generated only when SGBP query debugging is enabled. It provides information about queries in progress.
Recommended Action LOG_STD_NO_ACTION
%SGBP-7-HANGUP : I am a forward-only member, can't forward bundle [chars], hangup
Explanation This message is generated only when SGBP query, event and/or error debugging is enabled. This indicates a routine change of role for the router in its SGBP interactions with its peers.
Recommended Action LOG_STD_NO_ACTION
%SGBP-7-KEEPALIVE : Sending Keepalive to [chars], retry=[dec]
Explanation This message is generated only when SGBP hellos debugging is enabled. It indicates that a keepalive message was send to an SGBP member.
Recommended Action LOG_STD_NO_ACTION
%SGBP-7-KEEPALIVE_TIMEOUT : Keepalive timeout on [chars]
Explanation This message is generated only when SGBP hellos debugging is enabled. It indicates that keepalive messages were not answered so the pipe to an SGBP member has been closed.
Recommended Action LOG_STD_NO_ACTION
%SGBP-7-MQ : [chars] ([hex]) for query [dec]:[dec], bundle [chars], bid [dec], len [dec]
Explanation This message is generated only when SGBP error debugging is enabled. This message indicates that an SGBP query has been received.
Recommended Action LOG_STD_NO_ACTION
%SGBP-7-MQB : tBundle: [chars]tState: [chars]tOurBid: %03d
Explanation This message is part of a list of debug states displayed at the request of the operator.
Recommended Action LOG_STD_NO_ACTION
%SGBP-7-NEWL : Local query #[dec] for [chars], count [dec], ourbid [dec]
Explanation This message is generated only when SGBP query debugging is enabled. It provides information about queries in progress.
Recommended Action LOG_STD_NO_ACTION
%SGBP-7-NEWP : Peer query #[dec] for [chars], count [dec], peerbid [dec], ourbid [dec]
Explanation This message is generated only when SGBP query debugging is enabled. It provides information about queries in progress.
Recommended Action LOG_STD_NO_ACTION
%SGBP-7-NORESP : Failed to respond to [chars] group [chars], may not have password
Explanation An authentication challenge was received but there was no information available to respond to it. This probably indicates a configuration error, a missing password.
Recommended Action Refer to the documentation to configure a username with the same name as the SGBP group.
%SGBP-7-PB : t[IP_address]tState: [chars]tBid: %03d Retry: [dec]
Explanation This message is part of a list of debug states displayed at the request of the operator.
Recommended Action LOG_STD_NO_ACTION
%SGBP-7-RCVD : MQ [chars] from [IP_address] for query [dec]:[dec], bundle [chars], bid [dec], prot[chars]
Explanation This message is generated only when SGBP message debugging is enabled. It indicates that an SGBP packet was received.
Recommended Action LOG_STD_NO_ACTION
%SGBP-7-RCVINFO : Received Info Addr = [IP_address] Reference = [hex]
Explanation This message is generated only when SGBP hellos debugging is enabled. It indicates that data was received by a listener process.
Recommended Action LOG_STD_NO_ACTION
%SGBP-7-RESPONSE : Send Hello Response to [chars] group [chars]
Explanation This message is generated only when SGBP hellos debugging is enabled. This indicates that a response to an authentication challenge was sent to a peer.
Recommended Action LOG_STD_NO_ACTION
%SGBP-7-RESPONSED : Rcv Hello Response message from member [chars] using [IP_address]
Explanation This message is generated only when SGBP hellos debugging is enabled. This indicates that a response to an authentication challenge was received from a peer.
Recommended Action LOG_STD_NO_ACTION
%SGBP-7-SENDAUTHOK : Send Hello Authentication OK to member [chars] using [IP_address]
Explanation This message is generated only when SGBP hellos debugging is enabled. A message was send or re-sent to another SGBP member indicating that an authentication attempt from that member succeeded.
Recommended Action LOG_STD_NO_ACTION
%SGBP-7-SENDINFO : Send Info Addr to [chars]
Explanation This message is generated only when SGBP hellos debugging is enabled. It indicates that data was sent by the listener process in response to received data.
Recommended Action LOG_STD_NO_ACTION
%SGBP-7-SENT : MQ [chars] to [IP_address] for query [dec]:[dec], bundle [chars], bid [dec], prot[chars], len [dec]
Explanation This message is generated only when SGBP message debugging is enabled. It indicates that an SGBP packet was sent.
Recommended Action LOG_STD_NO_ACTION
%SGBP-7-WAITINFO : Member [chars] State -> WaitInfo
Explanation None
Recommended Action None
%SGBP-1-AUTHFAILED : Member [chars] failed authentication
Explanation This message is generated only when SGBP hellos or errors debugging is enabled. This indicates that an attempted peer connection ended in authentication failure. A peer may be misconfigured. Or this could indicate an attempted security breach.
Recommended Action Check if the peer is correctly configured. If there is a chance your network is under attack, obtain knowledgeable assistance. LOG_STD_ACTION
%SGBP-1-DIFFERENT : Rcv [chars]'s addr [IP_address] is different from the hello's addr [IP_address]
Explanation The internally-configured address for an SGBP member does not match the address of the host that tried to authenticate as that member. The configuration is incorrect on either this system or the other member - they must agree.
Recommended Action Determine which configuration is in error and fix it.
%SGBP-1-DUPLICATE : Rcv Duplicate bundle [chars] is found on member [chars]
Explanation This message is generated only when SGBP hellos or errors debugging is enabled. This indicates that a duplicate bundle was received from the same peer more than once. The duplicate was discarded.
Recommended Action LOG_STD_RECUR_ACTION
%SGBP-1-MISSCONF : Possible misconfigured member [chars] using [IP_address]
Explanation This message is generated only when SGBP hellos or error debugging is enabled. This indicates a configuration error. Either this router has an incorrect IP address listed for the peer or the peer is using an incorrect IP address.
Recommended Action Find and correct the configuraton error.
%SGBP-1-NOTAUTH : Rcv Connection request by non-authenticated member [chars]
Explanation None
Recommended Action None
%SGBP-1-UNKNOWNHELLO : Rcv Hello message from non-group member using [IP_address]
Explanation This message is generated only when SGBP hellos or error debugging is enabled. An SGBP Hello message was received from a host that is not a member of the SGBP group, and discarded.
Recommended Action This is a configuration error. Either that host should be listed in this router's configuration as a member (if that is actually true) or the other host is misconfigured to attempt to join this group.
%SGBP-3-INVALID : MQ message with [chars]
Explanation This message is generated only when SGBP error debugging is enabled. An invalid message was received and discarded.
Recommended Action This probably indicates an error in network media or a peer which is generating erroneous packets.
%SGBP-3-INVALIDADDR : Stack group [chars] IP address [IP_address]
Explanation The current configuration does not allow a local IP address to be configured using sgbp member <address>. Any local address is automatically removed fro the SGBP group.
Recommended Action Do not configure sgbp member <address> using a local IP address.
%SGBP-3-INVALIDB : [chars] for bundle '[chars]' --[chars]
Explanation An internal software error has occurred.
Recommended Action LOG_STD_ACTION
%SGBP-3-INVFIELD : [chars] field type [hex] has [chars] [dec] (expected [dec])
Explanation This message indicates that an SGBP request from a peer contained invalid or corrupt data.
Recommended Action Check the peer equipment or network media for any problems.
%SGBP-3-PEERERROR : Peer [IP_address] [chars] during 'PB [chars]' state for bundle [chars]
Explanation An internal software error has occurred.
Recommended Action LOG_STD_ACTION
%SGBP-3-TIMEOUT : Peer [IP_address] bidding; state 'PB [chars]' deleted
Explanation This message is generated only when SGBP event debugging is enabled. It indicates that a peer timed out while closing a query. The connection has been dropped.
Recommended Action Check the peer equipment and network media for problems.
%SGBP-3-UNEXP : MQ [chars] from [IP_address] for query [dec]:[dec], bundle [chars], bid [dec], state [chars]
Explanation This message is generated only when SGBP error debugging is enabled. The SGBP connection has entered an unexpected state, possibly due to a software error.
Recommended Action LOG_STD_ACTION
%SGBP-3-UNKNOWN : [IP_address] not known
Explanation This message is generated only when SGBP error debugging is enabled. An SGBP connection was attempted by a host which was not recognized as a peer. The connection was not accepted.
Recommended Action Depending on the network topology and firewalling, SGBP connection attempts from a non-peer host could indicate probing and attempts to breach security. If there is a chance your network is under attack, obtain knowledgeable assistance. LOG_STD_ACTION
%SGBP-3-UNKNOWNEVENT : Event [hex] from peer at [IP_address]
Explanation This message is generated only when SGBP error debugging is enabled. An invalid event occurred, which probably indicates an internal software error.
Recommended Action LOG_STD_ACTION
%SGBP-3-UNKNOWNPEER : Event [hex] from peer at [IP_address]
Explanation This message is generated only when SGBP error debugging is enabled. An SGBP event came from a network host which was not recognizable as an SGBP peer. The event was discarded.
Recommended Action Check if a network media error could have corrupted the address, or if peer equipment is malfunctioning to generate corrupted packets. Depending on the network topology and firewalling, SGBP packets from a non-peer host could indicate probing and attempts to breach security. If there is a chance your network is under attack, obtain knowledgeable assistance. LOG_STD_ACTION
%SGBP-5-ARRIVING : New peer event for member [chars]
Explanation This message is generated only when SGBP event debugging is enabled. An SGBP peer joined the group.
Recommended Action LOG_STD_NO_ACTION
%SGBP-5-LEAVING : Member [chars] leaving group [chars]
Explanation This message is generated only when SGBP event debugging is enabled. An SGBP peer has left the group.
Recommended Action LOG_STD_NO_ACTION
%SGBP-5-SHUTDOWN : [chars]
Explanation This message is generated only when SGBP event debugging is enabled. A process involved in SGBP was terminated upon completion of its work.
Recommended Action LOG_STD_NO_ACTION
%SGBP-5-STARTUP : [chars]
Explanation This message is generated only when SGBP event debugging is enabled. An process involved in SGBP was started.
Recommended Action LOG_STD_NO_ACTION
%SGBP-7-ACTIVE : Member [chars] State -> Active
Explanation This message is generated only when SGBP errors or events debugging is enabled. This indicates that a link to another SGBP member has completed the interactions to set it up and is now entering the active state.
Recommended Action LOG_STD_NO_ACTION
%SGBP-7-AUTHOK : Member [chars] State -> AuthOK
Explanation This message is generated only when SGBP errors or events debugging is enabled. A message was received from another SGBP member indicating that an authentication attempt to that member succeeded.
Recommended Action LOG_STD_NO_ACTION
%SGBP-7-CANCEL : Local query #[dec]:[dec] for bundle [chars]
Explanation This message is generated only when SGBP query debugging is enabled. It provides information about queries in progress.
Recommended Action LOG_STD_NO_ACTION
%SGBP-7-CHALLENGE : Send Hello Challenge to [chars] group [chars]
Explanation This message is generated only when SGBP hellos debugging is enabled. This indicates that an authentication challenge was sent to a peer.
Recommended Action LOG_STD_NO_ACTION
%SGBP-7-CHALLENGED : Rcv Hello Challenge message from member [chars] using [IP_address]
Explanation This message is generated only when SGBP hellos debugging is enabled. This indicates that an authentication challenge was received from a peer.
Recommended Action LOG_STD_NO_ACTION
%SGBP-7-CLOSE : Closing pipe for member [chars]
Explanation This message is generated only when SGBP event debugging is enabled. An interprocess communication link was closed.
Recommended Action LOG_STD_NO_ACTION
%SGBP-7-DONE : Query #[dec] for bundle [chars], count [dec], master is [chars]
Explanation This message is generated only when SGBP query debugging is enabled. It provides information about queries in progress.
Recommended Action LOG_STD_NO_ACTION
%SGBP-7-DUPL : Duplicate local query #[dec] for [chars], count [dec], ourbid [dec]
Explanation This message is generated only when SGBP query debugging is enabled. It provides information about queries in progress.
Recommended Action LOG_STD_NO_ACTION
%SGBP-7-EQUAL : [dec] equal highest bids, randomly select bid# [dec]
Explanation This message is generated only when SGBP query debugging is enabled. It provides information about queries in progress.
Recommended Action LOG_STD_NO_ACTION
%SGBP-7-HANGUP : I am a forward-only member, can't forward bundle [chars], hangup
Explanation This message is generated only when SGBP query, event and/or error debugging is enabled. This indicates a routine change of role for the router in its SGBP interactions with its peers.
Recommended Action LOG_STD_NO_ACTION
%SGBP-7-KEEPALIVE : Sending Keepalive to [chars], retry=[dec]
Explanation This message is generated only when SGBP hellos debugging is enabled. It indicates that a keepalive message was send to an SGBP member.
Recommended Action LOG_STD_NO_ACTION
%SGBP-7-KEEPALIVE_TIMEOUT : Keepalive timeout on [chars]
Explanation This message is generated only when SGBP hellos debugging is enabled. It indicates that keepalive messages were not answered so the pipe to an SGBP member has been closed.
Recommended Action LOG_STD_NO_ACTION
%SGBP-7-MQ : [chars] ([hex]) for query [dec]:[dec], bundle [chars], bid [dec], len [dec]
Explanation This message is generated only when SGBP error debugging is enabled. This message indicates that an SGBP query has been received.
Recommended Action LOG_STD_NO_ACTION
%SGBP-7-MQB : tBundle: [chars]tState: [chars]tOurBid: %03d
Explanation This message is part of a list of debug states displayed at the request of the operator.
Recommended Action LOG_STD_NO_ACTION
%SGBP-7-NEWL : Local query #[dec] for [chars], count [dec], ourbid [dec]
Explanation This message is generated only when SGBP query debugging is enabled. It provides information about queries in progress.
Recommended Action LOG_STD_NO_ACTION
%SGBP-7-NEWP : Peer query #[dec] for [chars], count [dec], peerbid [dec], ourbid [dec]
Explanation This message is generated only when SGBP query debugging is enabled. It provides information about queries in progress.
Recommended Action LOG_STD_NO_ACTION
%SGBP-7-NORESP : Failed to respond to [chars] group [chars], may not have password
Explanation An authentication challenge was received but there was no information available to respond to it. This probably indicates a configuration error, a missing password.
Recommended Action Refer to the documentation to configure a username with the same name as the SGBP group.
%SGBP-7-PB : t[IP_address]tState: [chars]tBid: %03d Retry: [dec]
Explanation This message is part of a list of debug states displayed at the request of the operator.
Recommended Action LOG_STD_NO_ACTION
%SGBP-7-RCVD : MQ [chars] from [IP_address] for query [dec]:[dec], bundle [chars], bid [dec], prot[chars]
Explanation This message is generated only when SGBP message debugging is enabled. It indicates that an SGBP packet was received.
Recommended Action LOG_STD_NO_ACTION
%SGBP-7-RCVINFO : Received Info Addr = [IP_address] Reference = [hex]
Explanation This message is generated only when SGBP hellos debugging is enabled. It indicates that data was received by a listener process.
Recommended Action LOG_STD_NO_ACTION
%SGBP-7-RESPONSE : Send Hello Response to [chars] group [chars]
Explanation This message is generated only when SGBP hellos debugging is enabled. This indicates that a response to an authentication challenge was sent to a peer.
Recommended Action LOG_STD_NO_ACTION
%SGBP-7-RESPONSED : Rcv Hello Response message from member [chars] using [IP_address]
Explanation This message is generated only when SGBP hellos debugging is enabled. This indicates that a response to an authentication challenge was received from a peer.
Recommended Action LOG_STD_NO_ACTION
%SGBP-7-SENDAUTHOK : Send Hello Authentication OK to member [chars] using [IP_address]
Explanation This message is generated only when SGBP hellos debugging is enabled. A message was send or re-sent to another SGBP member indicating that an authentication attempt from that member succeeded.
Recommended Action LOG_STD_NO_ACTION
%SGBP-7-SENDINFO : Send Info Addr to [chars]
Explanation This message is generated only when SGBP hellos debugging is enabled. It indicates that data was sent by the listener process in response to received data.
Recommended Action LOG_STD_NO_ACTION
%SGBP-7-SENT : MQ [chars] to [IP_address] for query [dec]:[dec], bundle [chars], bid [dec], prot[chars], len [dec]
Explanation This message is generated only when SGBP message debugging is enabled. It indicates that an SGBP packet was sent.
Recommended Action LOG_STD_NO_ACTION
%SGBP-7-WAITINFO : Member [chars] State -> WaitInfo
Explanation None
Recommended Action None
SGPM
%SGPM-3-PACL_NAME_TOO_LONG : The pacl name ([chars]-[chars]) is too long, it exceeds the maximum length of [dec].
Explanation Too many acl entries have made the pacl name exceed the maximum supported length
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SGPM-3-POLICY_CTX_ACTIVE : Active policy context [hex] has bad magic, [hex].
Explanation The magic number in the active policy context is wrong.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SGPM-3-POLICY_CTX_POISONED : Policy context [hex] has bad magic, [hex].
Explanation The magic number in the policy context is wrong.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SGPM-3-POLICY_INCOMPLETE_RULE : Subscriber policy rule ([chars]), event ([chars]) is missing a mandatory action for service ([chars] automatically adding.
Explanation The subscriber policy rule was missing a mandatory action; automatically added.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SGPM-3-POLICY_RULE_SERVICE_CONFIG_ERROR : Service ([chars]) is configured incorrectly, service_failed event will be thrown
Explanation In policy rule, the service is configured incorrectly, then a service-failed event will be thrown.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
SHELL_ISSU
%SHELL_ISSU-2-COPY_SHELL_INIT_TO_STANDBY : Failed to copy the shell init file [chars] to standby
Explanation If the shell init file is not copied to standby, the shell init file CLI will not be applied to maintain the consistancy between active and standby.
Recommended Action LOG_STD_SH_CMD_ACTION( Try manually copy a file to standby to see if it's a filesystem issue. It could be a space issue in the standby disk)
%SHELL_ISSU-2-GET_BUFFER : Shell ISSU client failed to get buffer for message. Error: [dec] ([chars])
Explanation The Shell 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)
%SHELL_ISSU-2-INIT : Shell ISSU client initialization failed to [chars]. Error: [dec] ([chars])
Explanation The Shell 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SHELL_ISSU-2-SAVE_TRIGGER_FOR_REAPPLY : Failed to add trigger to the re-apply queue. Trigger: [chars], Env: [chars]
Explanation Triggers that failed to get applied during ISSU must be saved and then re-applied after ISSU completes.
Recommended Action LOG_STD_SH_CMD_ACTION( Manually re-apply the trigger after ISSU completes)
%SHELL_ISSU-2-SEND_NEGO_FAILED : Shell ISSU client failed to send negotiation message. Error: [dec] ([chars])
Explanation The Shell 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)
%SHELL_ISSU-2-SESSION_NEGO_FAIL_START : Failed to start Shell ISSU session negotiation. Error: [dec] ([chars])
Explanation The Shell 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>)
%SHELL_ISSU-2-SESSION_REGISTRY : Shell ISSU client failed to register session information. Error: [dec] ([chars])
Explanation The Shell 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>)
%SHELL_ISSU-3-INVALID_SESSION : Shell ISSU client does not have a valid registered session.
Explanation The Shell 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>)
%SHELL_ISSU-3-MSG_NOT_OK : Shell ISSU client 'Message Type [dec]' is not compatible
Explanation The Shell 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>)
%SHELL_ISSU-3-MSG_SIZE : Shell ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] ([chars])
Explanation The Shell ISSU client failed to calculate the MTU for the specified message. The Shell 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>)
%SHELL_ISSU-3-SESSION_UNREGISTRY : Shell ISSU client failed to unregister session information. Error: [dec] ([chars])
Explanation The Shell 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>)
SIP
%SIP-3-BADPAIR : Unexpected [chars] [dec] ([chars]) in state [dec] ([chars]) substate [dec] ([chars])
Explanation The SIP state machine has encountered an error while processing an event or timer.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%SIP-3-CONSTRUCT : Error encountered while trying to construct a [dec] [chars] [chars] message
Explanation An error was encountered while attempting to construct a SIP request or response message. If malloc errors where also seen, then that is most likely the root of the problem. If no memory allocation errors have occurred, then this may be an internal problem.
Recommended Action If there were memory allocation errors at the same time as this error, then this error can be ignored. Otherwise: LOG_STD_SH_TECH_ACTION
%SIP-3-DIGITEND : Missing digit end event for '%c' for call ID [chars]
Explanation A digit begin event was detected without a matching digit end. This is most likely an internal error which is self correcting (the NOTIFY for the digit has been transmitted).
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SIP-3-DIGITQFULL : Unable to queue DTMF digit. Queue full. size: [dec]
Explanation A request to queue a DTMF digit was rejected because the DTMF queue is full. A 5xx server error has been returned. This error may indicate that a flood of DTMF digit requests from an external SIP application for a specific call has been recieved in a very short period of time.
Recommended Action No action is required.
%SIP-3-FORKING_CODEC : No forking codecs configured for dial-peer [dec], the forked m-lines will be rejected. Forking codecs are [chars]
Explanation Media forking requests which arrive in an INVITE message are identified by multiple media lines (m-lines) in the SDP. Each media line defines a media stream with destination port and payload types. In order to fork multiple media streams from a single call, all streams must share the same payload type and codec. Only a subset of the full list of SIP codecs are available for media forking, and the dial-peer selected for the call which is to be forked must include one of these supported codecs. This error indicates that the dial-peer does not include one of the supported codecs, so only the original media stream will be maintained; the remaining media streams will be rejected in the response by setting the port number to zero (0) in the SDP.
Recommended Action Modify the dial-peer configuration to include one of the forking codecs listed using either the codec command or the voice-class codec command.
%SIP-3-INSV_ERROR : Error encountered while trying to bring the SIP component into service
Explanation During bootup of the gateway, each of the Service Provider Interfaces (SPIs) are brought into service. The SIP SPI creates several processes and notifies the Call Control API (CCAPI) when it is finished. One or more of these tasks failed, so the SIP component will not be properly initialized.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%SIP-3-INVALID : Invalid [chars] [dec]
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%SIP-3-LIST_ERROR : Unable to create list for [chars]
Explanation Failure to create a list generally indicates that the router is out of memory, either due to a memory leak or insufficient memory. If the error was generated soon after a reload, its more likely that the router doesn't have enough memory. If the router has been running for a while, a memory leak is more likely. The SIP component is not properly initialized, and SIP calls may not complete properly.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show process memory command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%SIP-3-NOGETSTRUCT : No data structure passed to MIB API subsystem.
Explanation The SNMP Agent MIB subsystem for this MIB did not pass any data structure to the MIB API subsystem for the proper retrieval of the requested object data. Processing of the GET operation cannot continue.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SIP-3-NOMATCH : Unable to find matching CCB for ccCallID [dec]
Explanation An internal error was encountered while trying to match a call ID with a call control block
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%SIP-3-NORESOURCE : No resources for [chars]
Explanation An error was encountered while trying to obtain memory resources for an internal queue or table. If malloc errors where also seen, then that is most likely the root of the problem. If no memory allocation errors have occurred, then this may be an internal problem.
Recommended Action If there were memory allocation errors at the same time as this error, then this error can be ignored. Otherwise: LOG_STD_SH_TECH_ACTION
%SIP-3-NOSETDATA : No SET data passed to MIB API subsystem.
Explanation The SNMP Agent MIB subsystem for this MIB did not pass any data to the MIB API subsystem for the proper assignment of values to the internal data structures of the object. Processing of the SET operation cannot continue.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SIP-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 SIP 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show process cpu command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%SIP-3-UNKNOWNOBJ : MIB object [chars].[dec] is not known by MIB API subsystem.
Explanation The MIB object specified in the SNMP GET PDU has been correctly identified by the SNMP Agent infrastructure, but was not correctly identified by the subsystem responsible for the MIB. Processing of the GET operation cannot continue. The SNMP Agent infrastructure and subsystem responsible for the MIB, under normal conditions, will always be synchronized to the same set of MIB objects (that is, the same version of the MIB). This condition indicates that synchronization has not occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SIP-3-UNSUPPORTED : [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%SIP-4-MAXSDP : SIP message sent with maximum SDP.
Explanation An SIP protocol message containing the maximum allowable SDP size has been sent. If the desired SDP was greater than the maximum size limit, the SDP has been truncated at the limit. If the desired SDP was equal to the maximum size limit, no truncation has occurred. This warning may indicate that an SIP request containing an unusually large SDP has been received from an external SIP application for a specific call, resulting in an SIP response with the maximum SDP.
Recommended Action No action is required.
%SIP-5-DIALPEER_STATUS : VoIP dial-Peer <[dec]> is [chars]
Explanation VoIP dial-peer's operational status is changed
Recommended Action If the dial-peer status is busyout, the session target configured under the dial-peer is not reachable
%SIP-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
SIPSPA
%SIPSPA-3-BADCMD : [chars]: Unsupported command [dec], arg0=[hex], arg1=[hex], arg2=[hex]
Explanation The Route Processor passed down a command that the software was not prepared to handle.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%SIPSPA-3-BAD_IFCOMTYPE : Bad ifcom message type=[int]
Explanation The Route Processor passed down a message that the software was not prepared to handle.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%SIPSPA-3-BADINT : Attempted to access HWIDB for port [int]
Explanation The Linecard attempted to access the HWIDB associated with a non-existent port.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%SIPSPA-3-CMDNOINT : HWIDB Null for command [dec], arg=[hex]
Explanation The Route Processor passed down a command that the software was unprepared to handle.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%SIPSPA-3-DEVICE_ERROR : subSlot [dec], spatype [hex]. Device error: [chars]
Explanation An error related to a device on the SPA is detected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%SIPSPA-3-EFC_CHAN_ERR : EFC error -interface [chars], vc [dec], anyphy [dec], err_code [dec] : [chars]
Explanation Failed to configure efc channel/parameters
Recommended Action Seach for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, LOG_STD_ACTION
%SIPSPA-3-FCI_NOT_SET : Bay [dec]: [chars]: FCI type not set
Explanation An FCI type of zero was detected
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SIPSPA-3-HWIDB_FAILURE : Creation: port [dec] vc [dec]
Explanation Failed to create a hwidb.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%SIPSPA-3-INVALID_ANYPHY : Bay [dec] -Invalid anyphy number [int] for vc [dec]
Explanation Interface has invalid anyphy mumber
Recommended Action Seach for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start 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).
%SIPSPA-3-IPCALLOCFAIL : Failed to allocate IPC buffer [chars]
Explanation The Linecard failed to allocate a buffer for communication with the Route Processor.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%SIPSPA-3-IPCSENDFAIL : Failed to send IPC message [chars]
Explanation The Linecard failed to send a message to the Route Processor.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%SIPSPA-3-ISR_RC_ERROR : ISR return code out of range. rc=[dec]
Explanation The ISR error return code is out of range.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%SIPSPA-3-LINKREC_ERROR : Link record error -Bay [dec] vc [dec], error code [dec]
Explanation Error processing link record structure
Recommended Action Seach for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start 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).
%SIPSPA-3-MESSAGE_ERROR : Bay [dec]: [chars]
Explanation An unexpected error has occurred.
Recommended Action Seach for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, LOG_STD_ACTION
%SIPSPA-3-MSGTOOBIG : Message length exceeds max, [int] bytes
Explanation The Linecard attempted to send too large a message to the Route Processor.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%SIPSPA-3-NODISPATCH : Dispatch vector Null, cmd=[dec], dintf=[dec]
Explanation No command dispatch vector was found for the specified interface.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%SIPSPA-3-POWER : Bay [dec] 12V power is [chars]
Explanation SPA 12V power fault indicator
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SIPSPA-3-SONET_CLOCK_FAILED : SPA Sonet clock has failed (status = [hex])
Explanation The SPA SONET clock has failed. SPAs that rely on the SPA SONET clock for proper operation, such as POS and ATM will be affected.
Recommended Action If the SPA Sonet clock does not recover, perform an OIR. LOG_STD_RECUR_ACTION
%SIPSPA-3-SONET_CLOCK_RECOVERED : SPA Sonet clock has recovered (status = [hex])
Explanation SPA Sonet clock has recovered
Recommended Action No action is required.
%SIPSPA-3-SPI4_CONFIG_FAILURE : Bay [dec], spi4 configuration failure, error [dec]
Explanation Failed to configure SPI4 interface
Recommended Action Seach for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, LOG_STD_ACTION
%SIPSPA-3-SPI4_INIT_FAILURE : Bay [dec] initialization failure
Explanation Failed to create SPI4 subblock
Recommended Action Seach for resolved software issues using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, LOG_STD_ACTION
%SIPSPA-4-MAX_BANDWIDTH : Total SPA bandwidth exceeds line card capacity of [int] Mbps
Explanation The total bandwidth of SPAs exceeds the rated capacity of this line card.
Recommended Action Refer to the line card guidelines for the maximum allowed aggregated SPA bandwidth for the line card
%SIPSPA-4-MAX_BANDWIDTH_NS : Total SPA bandwidth exceeds line card capacity, installed combination of SPA interfaces is not supported
Explanation The total bandwidth of SPAs exceeds the rated capacity of this line card.
Recommended Action Refer to the line card guidelines for the maximum allowed aggregated SPA bandwidth for the line card
%SIPSPA-4-SPABUS2 : Bay [dec] [chars] failed. sz=[int] rd_par=[int] noresp=[int] absent=[int] err_l=[int] addr=[hex] data=[hex] parity=[hex] deadman=[int]
Explanation SPABUS has reported an error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SIPSPA-4-SPABUS : Bay [dec] [chars] failed. sz=[int] rd_par=[int] noresp=[int] err_l=[int] addr=[hex] data=[hex] parity=[hex] deadman=[int]
Explanation SPABUS has reported an error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SIPSPA-4-SPI_PORT_LIMIT_EXCEEDED : SPI port limit exceeded, [chars] in [chars] has been powered down.
Explanation The total number of SPI ports required exceeds the capacity of this line card.
Recommended Action Refer to the line card guidelines for SPA combinations supported by this line card
%SIPSPA-6-ERRORRECOVER : A Hardware or Software error occurred on [chars]. Reason : [chars] Automatic Error recovery initiated. No further intervention required.
Explanation An error occurred in one of the devices, recovery would be attempted. If recovery succeeds no further messages would be logged and no intervention would be required.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%SIPSPA-6-OIR : Bay [dec] [chars] changed to [chars]
Explanation SPA OIR Sequence
Recommended Action No action is required.
SISF
%SISF-3-INTERNAL : Internal 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SISF-4-DATA_GLEAN_NOTIF_RECEIVED : No binding for [chars]
Explanation A data packet notification has been received because a snooping policy with the data glean option is configured and the Source address of the packet is not currently in the Binding Table.
Recommended Action There are valid scenarios where the binding could not be learned (e.g. control packet was lost) or the binding is lost (e.g. switch reboot). Conversely, it could also be the case that an unauthorized Source Address is trying to generate traffic, in which case this should be investigated further to determine if the host on this particular interface needs to be disconnected.
%SISF-4-ENTRY_BLOCKED : Entry blocked [chars]
Explanation An attempt to install an entry in the IPv6 binding table was blocked. This can be due to a conflicting entry or maximum number of entries reached
Recommended Action If the maximum table size is reached, consider increasing it. If a conflicting entry already exist, this maybe an attempt to steal address ownership. You should investigate which host is connected on the interface and wether it should be disconnected
%SISF-4-IP_THEFT : IP Theft [chars]
Explanation A duplicate IP address has been detected (IP theft) and blocked This can be due to a configuration error on end-device, an intentional IP theft or an IP movind too quickly
Recommended Action If the existing entry is REACHABLE in the binding table, and it moved to a new port consider reducing the REACHABLE timer otherwise it is either an attack or a configuration issue that must be resolved
%SISF-4-MAC_AND_IP_THEFT : MAC_AND_IP Theft [chars]
Explanation A duplicate MAC and IP address has been detected (MAC_AND_IP theft) and blocked This can be due to a configuration error on end-device, an intentional MAC_AND_IP theft or MAC moving too quickly
Recommended Action If the existing entry is REACHABLE in the binding table, and it moved to a new port consider reducing the REACHABLE timer otherwise it is either an attack or a configuration issue that must be resolved
%SISF-4-MAC_THEFT : MAC Theft [chars]
Explanation A duplicate MAC address has been detected (MAC theft) and blocked This can be due to a configuration error on end-device, an intentional MAC theft or MAC moving too quickly
Recommended Action If the existing entry is REACHABLE in the binding table, and it moved to a new port consider reducing the REACHABLE timer otherwise it is either an attack or a configuration issue that must be resolved
%SISF-4-PAK_DROP : Message dropped [chars]
Explanation A message was dropped because one of the IPv6 first-hop security features said so
Recommended Action Look at the reason. It can either be a valid drop and the could go up to disconnect the host attached to the interface, or the policy configured on this interface is too severed and should be amended
%SISF-4-RESOLUTION_VETO : Resolution vetoed [chars]
Explanation IPv6 Neighbor Discovery (ND) was about to resolve a target destination. SISF Destguard has vetoed this because the target is known not to be on-link.
Recommended Action A low rate of vetoed resolutions is not serious. If there is a high rate of vetos this might suggest that the link is under attack. Investigate the source of the packets driving these resolution requests
%SISF-6-ENTRY_CHANGED : Entry changed [chars]
Explanation An entry was changed in the binding table
Recommended Action This is an informationnal message
%SISF-6-ENTRY_CREATED : Entry created [chars]
Explanation An entry was created in the binding table
Recommended Action This is an informationnal message
%SISF-6-ENTRY_DELETED : Entry deleted [chars]
Explanation An entry was created in the binding table
Recommended Action This is an informationnal message
%SISF-6-ENTRY_MAX_ORANGE : Reaching 80 percent of max adr allowed per [chars]
Explanation Reached 80% of maximum # addresses for the target
Recommended Action A client is approaching red zone and might soon be blocked. The maximum value configured may be too low and you should consider increasing it. Or some of this client addresses are stale and you could clear them
SISF_ISSU
%SISF_ISSU-2-GET_BUFFER : Sisf ISSU client failed to get buffer for message. Error: [dec] ([chars])
Explanation The Sisf 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)
%SISF_ISSU-2-INIT : Sisf ISSU client initialization failed to [chars]. Error: [dec] ([chars])
Explanation The Sisf 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SISF_ISSU-2-SEND_NEGO_FAILED : Sisf ISSU client failed to send negotiation message. Error: [dec] ([chars])
Explanation The Sisf 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)
%SISF_ISSU-2-SESSION_NEGO : Sisf ISSU client encountered unexpected client nego_done. Error: [dec] ([chars])
Explanation An ISSU-compliant client transitions through a series of internal states. The Sisf 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>)
%SISF_ISSU-2-SESSION_REGISTRY : Sisf ISSU client failed to register session information. Error: [dec] ([chars])
Explanation The Sisf 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>)
%SISF_ISSU-3-CAP_INVALID_SIZE : SISF ISSU client capability list is empty.
Explanation The SISF ISSU client capability exchange list size is invalid.
Recommended Action LOG_STD_SH_CMD_ACTION( show issu capability entires <Client_ID>)
%SISF_ISSU-3-CAP_NOT_COMPATIBLE : Sisf ISSU client capability exchange result incompatible.
Explanation The Sisf ISSU client capability exchange have negotiated as incompatible with the peer.
Recommended Action LOG_STD_SH_CMD_ACTION( show issu negotiated capability <Session_ID>)
%SISF_ISSU-3-INVALID_SESSION : Sisf ISSU client does not have a valid registered session.
Explanation The Sisf 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>)
%SISF_ISSU-3-MSG_NOT_OK : Sisf ISSU client 'Message Type [dec]' is not compatible
Explanation The Sisf 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>)
%SISF_ISSU-3-MSG_SIZE : Sisf ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] ([chars])
Explanation The Sisf ISSU client failed to calculate the MTU for the specified message. The Sisf 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>)
%SISF_ISSU-3-SESSION_UNREGISTRY : Sisf ISSU client failed to unregister session information. Error: [dec] ([chars])
Explanation The Sisf 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>)
%SISF_ISSU-3-TRANSFORM_FAIL : Sisf ISSU client [chars] transform failed for 'Message Type [dec]'. Error: [dec] ([chars])
Explanation The Sisf 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 Sisf 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>)
SISF_TRACKING_HA
%SISF_TRACKING_HA-4-ENTRY_OUT_OF_SYNC : Host mac-address [enet] ip-address [IP_address] interface [chars]
Explanation An inconsistency has been detected in the IP device tracking table for this host between active and standby
Recommended Action No action is required.
SLA
%SLA-3-SLAAVAILABILITY : IP SLAs([int]): State change for [chars];[chars];FLR -[dec]
Explanation This informational message logs availability transitions in the Service Assurance Agent probes. This messages appears when the ip sla logging trap command is entered
Recommended Action If this message is not necessary, enter the no ip sla logging trap command to disable logging. Otherwise, no action is required
%SLA-3-SLATHRESHOLD : IP SLAs([int]): Threshold for [chars]; [chars]; [dec]
Explanation This informational message logs threshold violations in the Service Assurance Agent probes. This messages appears when the ip sla logging trap command is entered
Recommended Action If this message is not necessary, enter the no ip sla logging trap command to disable logging. Otherwise, no action is required
SLIP
%SLIP-2-BADQUOTE : Impossible quoted character [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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%SLIP-2-BADSTATE : Impossible input state [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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
SM
%SM-2-INITIALIZATION_FAILED :
Explanation Initialization of session manager process failed.
Recommended Action Review SM 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.
SMAN
%SMAN-2-NO_MEMORY : Cannot allocate memory for an internal data structure
Explanation An out-of-memory condition occurred when attempting to create an internal data structure. The daemon encountering the problem will exit, after which the process manager will restart.
Recommended Action Check the log files for the associated daemon. Monitor processes for excessive memory consumption.
%SMAN-2-TDL_MESSAGE : Cannot construct an IPC message for library. The message name is [chars] and the reason is: [chars]
Explanation A problem occurred while constructing a type definition language (TDL) message or setting a field in a TDL message. If the problem occurred during construction of a TDL message, the system is out of memory. If the problem occurred while setting a field in the TDL message, there is a library mismatch issue.
Recommended Action Check [uipeer] ERR entries in the log files for message reporting problems.
%SMAN-3-HOSTINFO_MONITOR_FAILURE : Error initializing host info monitoring: [chars]
Explanation During initialization, the Shell Manager monitors changes to host-related information, such as the hostname. This error occurs if initialization fails.
Recommended Action Check the Shell Manager trace file for related details.
%SMAN-3-HOSTINFO_READ_FAILURE : Error reading host info ([chars]): [chars]
Explanation During process startup and when changes occur, the Shell Manager reads host-related information, such as the hostname. This error occurs if there is a failure reading information.
Recommended Action Check the Shell Manager trace file for related details.
%SMAN-3-INVALID_EPOCH_FILE : An upgrade or installation has produced an invalid messaging configuration file [chars], [chars]
Explanation During an upgrade or installation of a new package, an invalid messaging configuration file was produced. The file is either empty or has invalid permissions and cannot be read.
Recommended Action Repeat the installation or upgrade. If the problem persists, revert to a previous known good package.
%SMAN-3-NO_CDL_FILE : Could not access command definition file [chars]: [chars]
Explanation During initialization, the Shell Manager loads a XML CDL file to load all the CLI structure. This file is for some reason not found.
Recommended Action Check the Shell Manager trace file for related details.
%SMAN-3-PTL_RENDERER_FAILURE : Rendering error with [chars].[chars]. Transform is missing or invalid for data.
Explanation The Shell Manager process attempted to render a command response but the transformation failed due to an internal error. The failure may have been caused by a missing transform file or an included file cannot be found. The transformation may also fail if the data returned in the response is binary and has not been processed correctly. In this case, the rendering engine is unable to interpret the data resulting in a failure. The transformation may also fail if there is a mismatch of packages installed on the system. In this case, incompatible messages are exchanged between the Shell Manager and the daemon servicing the command request and incorrect data is passed to the rendering engine.
Recommended Action This error indicates a configuration issue resulting from bad or mismatched packages. Review the Shell Manager trace files and log files. Uninstall, then reinstall, any new packages.
SMANRP
%SMANRP-3-BADREPLYJOBID : Incorrect command reply job id [int] (origin [chars]), expecting [int]
Explanation A command reply message from the Shell Manager referenced the wrong originating job id
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SMANRP-3-CMDBUILD : Interactive command directive [dec] of [dec] failed
Explanation In processing a CLI command, one of the instructions returned through the Shell Manager could not be turned into an interactive command for remote execution.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SMANRP-3-CMDCONNECT : Connection to local interactive relay failed: [chars]
Explanation Connecting to the local relay for an interactive command failed due to the reason indicated in the error message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SMANRP-3-CMDSEND : Send interactive command to relay failed: [chars]
Explanation Sending the interactive command string to the local relay after the connection was established failed by the reason indicated in the error message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SMANRP-3-CMDTOOLONG : Interactive command too long
Explanation Instructions for command execution would result in creation of a command string that is beyond the maximum size.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SMANRP-3-INVALIDCONNHANDLE : Invalid connection handle [int] referenced during command execution.
Explanation The execution of a CLI command, which must communicate with Shell Manager for command execution, has referenced a connection handle that is invalid. The CLI command execution will have failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SMANRP-3-MSGBIPCBUFFER : Unable to acquire a BIPC buffer for sending messages.
Explanation A message was to be sent by IOS, but no BIPC buffer was available. The message to be sent has been discarded and the associated operation failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SMANRP-3-MSGBIPCCONNERR : Unable to register with the BIPC subsystem for connections to Shell Manager
Explanation IOS Shell Manager client code could not register with the BIPC communications infrastructure in order to establish a connection with the Shell Manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SMANRP-3-MSGBIPCERR : Unable to process received BIPC messages from Shell Manager, error: [chars]
Explanation An unexpected condition has occurred while IOS trying to process a received BIPC message from Shell Manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SMANRP-3-MSGBUILDERROR : Error [dec] building TDL message '[chars]' to send to the Shell Manager: [chars]
Explanation An unexpected condition has occurred while IOS is building a TDL message to send to the Shell Manager
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SMANRP-3-MSGDISPATCH : Unable to dispatch received TDL message '[chars]' from Shell 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 Shell Manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SMANRP-3-MSGDISPATCHNULL : Received NULL TDL message
Explanation An unexpected condition in which IOS has received a NULL TDL message from Shell Manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SMANRP-3-MSGENQUEUEERROR : Error queueing TDL message '[chars]' to send to the Shell Manager
Explanation An unexpected condition has occurred when IOS attempted to queue a TDL message to send to the Shell Manager
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SMANRP-3-MSGERROR : Error [dec] handling a received TDL message '[chars]' from the Shell Manager: [chars]
Explanation An unexpected condition has occurred while IOS is processing a TDL message received from the Shell Manager
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SMANRP-3-MSGINVALIDFIELDINT : Invalid field '[chars]' in TDL message '[chars]' received: value '[int]' from the Shell Manager
Explanation A message with an invalid field value was received from the Shell Manager
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SMANRP-3-MSGINVALIDFIELDSTR : Invalid field '[chars]' value '[chars]' in TDL message '[chars]' received from the Shell Manager
Explanation A message with an invalid field value was received from the Shell Manager
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SMANRP-3-MSGMARSHALERROR : Error '[dec]' marshaling TDL message '[chars]' to send to the Shell Manager
Explanation An unexpected condition has occurred while IOS is marshaling TDL message to send to the Shell Manager
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SMANRP-3-MSGMISSINGFIELD : Missing field '[chars]' in TDL message '[chars]' received from the Shell Manager
Explanation A message missing a required field was received from the Shell Manager
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SMANRP-3-SET_ACCESS_FAIL : Installing LIIN interface access control failed
Explanation This error happens when the Shell Manager shim failed to set the access control function for the LIIN, possibly due to IOS out of memory or corruption. Interactive commands will not work.
Recommended Action LOG_STD_ACTION
%SMANRP-3-SMAN_HANDLER_QUEUE_NOTEMPTY : Dynamic command handler exited foreground process with non-empty queue
Explanation The dynamic command handler which dispatches commands to the shell manager, has exited without proper cleanup.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SMANRP-3-SMAN_INIT_CONN_FAIL : Shell Manager client connection pool initialization failed: Unable to request creation of [int] of [int] connections.
Explanation The Shell Manager client has failed to create all of its connections to Shell Manager. Ability to execute some CLI commands will be severely restricted or non-existent.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SMANRP-3-SMAN_INIT_DC_TDL_FAIL : Shell Manager client initialization failed: Unable to initialize messaging: [chars]
Explanation The Shell Manager client has failed to initialize the infrastructure for messaging with the Shell Manager. Ability to execute some CLI commands will be severely restricted or non-existent.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SMANRP-3-SMAN_INIT_WQ_FAIL : Shell Manager client connection handler initialization failed: Unable to create [int] of [int] receiving queues.
Explanation The Shell Manager client has failed to create all of its receiving queues. Ability to execute some CLI commands will be severely restricted or non-existent.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SMANRP-6-SMSTATUS : Shell Manager is [chars]
Explanation The current status of Shell Manager.
Recommended Action No action is required.
SMF
%SMF-4-INVALID_ACTION : failed to create SMF entry for [enet] on [chars] with result [hex]
Explanation An internal software error occurred.
Recommended Action LOG_STD_ACTION
SMRP
%SMRP-2-ASSERTFAILED : SMRP assertion failed: [chars]
Explanation The software detected an inconsistency. This is considered a serious error. The router attempts to continue, but SMRP processing may be impaired.
Recommended Action Copy the error message exactly as it appears, noting any SMRP problems that you are experiencing, and report it to your technical support representative.
%SMRP-3-NOFDDICOMPAT : SMRP port [chars] disabled; pre-fdditalk not supported
Explanation SMRP cannot be started on an interface that is running pre-FDDITalk.
Recommended Action Use FDDITalk on the FDDI ring if possible.
%SMRP-5-NEIGHBORDOWN : [chars]: SMRP neighbor down -[chars]
Explanation A neighboring SMRP router is now down.
Recommended Action Notification message only. No action required.
%SMRP-5-PORTDOWN : [chars]: SMRP port down -[chars]
Explanation An SMRP port is down and is no longer operational.
Recommended Action Notification message only. No action required.
%SMRP-6-NEIGHBORUP : [chars]: SMRP neighbor up -[chars]
Explanation A neighboring SMRP router has appeared.
Recommended Action Notification message only. No action required.
%SMRP-6-PORTUP : [chars]: SMRP port up -[chars]
Explanation An SMRP port has come up.
Recommended Action Notification message only. No action required.
%SMRP-7-DEBUGMSG : SMRP Debug: [chars]
Explanation This message is generated by some debug commands to provide additional information about conditions in SMRP.
Recommended Action If you are experiencing problems in SMRP, these messages should be provided, along with any other information, in a report to your technical support representative.
SNAPSHOT
%SNAPSHOT-2-BADSTATE : Bad state for Snapshot block [chars][[dec]], location [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.
%SNAPSHOT-2-TOOMANYDIALERS : Exceeded maximum dialer interfaces to watch. Ignoring [chars]
Explanation Snapshot is being used over more than 100 DDR interfaces.
Recommended Action Do not use snapshot over more than 100 DDR interfaces.
SNMP
%SNMP-3-AUTHFAIL : Authentication failure for SNMP req from host [IP_address]
Explanation An SNMP request was sent to this host which was not properly authenticated.
Recommended Action Make sure that the community/user name used in the SNMP req has been configured on the router.
%SNMP-3-AUTHFAILIPV6 : Authentication failure for SNMP request from host [IPV6 address]
Explanation An SNMP request was sent by this host which was not properly authenticated.
Recommended Action Make sure that the community/user name used in the SNMP req has been configured on the router.
%SNMP-3-BADIFINDEXTABLE : The file nvram:ifIndex-table is corrupt.
Explanation The file is not in the expected format.
Recommended Action If possible, please delete the file.
%SNMP-3-BADOID : Attempt to generate an invalid object identifier
Explanation A valid object identifier must contain at least two subidentifiers. An attempt was made to generate an object identifier whose size was less than two.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%SNMP-3-BADVALUE : Maximum number of index supported is 20
Explanation An SNMP trap contains some number of MIB objects, and the size of the instance identifier for these objects is restricted. This message indicates that an attempt was made to generate an SNMP trap containing a MIB object whose size exceeded this limit.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%SNMP-3-CPUHOG : Processing [chars] of [chars]
Explanation SNMP took too much time processing a request.
Recommended Action If feasible, use the <bold>debug snmp packet<nobold> command to determine the contents of the SNMP request that is causing the message. Copy the error message exactly as it appears, and report it along with any debug output to your technical support representative.
%SNMP-3-DUPLICATE_IFINDEX : [chars] has [dec] duplicate ifIndices.
Explanation ifIndex-table file is corrupt. Ignoring duplicate entries.
Recommended Action If ifIndex-table is not needed, please delete the file from nvram.
%SNMP-3-DVR_DUP_REGN_ERR : Attempt for dupe regn with SNMP IM by driver having ifIndex [dec] and ifDescr [chars]
Explanation Driver is attempting to register an idb with the interface manager while there is already an interface with the same ifIndex and ifDescr BUT different idb registered. This would lead into the problem that interface counters shown by snmp would not work properly for this particular interface.
Recommended Action Fix the duplicate registration in driver level.
%SNMP-3-DVR_DUP_REGN_WARNING : Attempt for dupe regn with SNMP IM by driver having ifIndex [dec] and ifDescr [chars]
Explanation Driver is attempting to register the same idb with the interface manager while it's already registered. This is just a warning message and handled by snmp.
Recommended Action Fix the duplicate registration in driver level.
%SNMP-3-DYNSYNCFAIL : Snmp Dynamic Sync Failed for [chars] = [chars]
Explanation One of the SNMP MIB Dynamic Sync(sync of Snmp SET) to standby failed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%SNMP-3-FILEOPENFAILED : Could not open [chars].
Explanation The ifIndex-table is not accesible, and hence the facility for ifindex persistence may not be available.
Recommended Action Please debug using the debug ifs file command.
%SNMP-3-FILESTATFAILED : Could not get information for file [chars].
Explanation The ifIndex-table is not accesible, and hence the facility for ifindex persistence may not be available.
Recommended Action Please debug using the debug ifs file command.
%SNMP-3-IFINDEXTABLE_DECOMPRESSFAILED : The file nvram:ifIndex-table.gz could not be decompressed.
Explanation There is either insufficient memory to compress it or the nvram space is insufficient or some other reason.
Recommended Action If possible, please delete the file.
%SNMP-3-IFINDEXTABLEFILEINTWOFORMATS : ifIndex-table is present in two formats.
Explanation Both nvram:ifIndex-table and nvram:ifIndex-table.gz are present.
Recommended Action No action is necessary.
%SNMP-3-INCORRECT_SIZE_FOR_NVRAM : Size should be > 0, but it is [dec].
Explanation There is some initialization problem in software.
Recommended Action Ideally, you should never see this message. If you do, please report it at the earliest convenience.
%SNMP-3-INPUT_QFULL_ERR : Packet dropped due to input queue full
Explanation Snmp packet dropped due to input queue full error
Recommended Action The condition is usually caused by a large delay collecting data for a specific OID, which will backup the SNMP queue with subsequent requests. You may see an accompanying SNMP-CPUHOG message that displays which OID is taking too long. If the SNMP-CPUHOG error consistently points to the same OID, then the user should search for a matching Cisco CDETS ID which improves performance of that OID. Blocking the OID with an snmp view is an optional workaround, but that will impact the ability for management software to get data from the device. In a small percentage of cases, the root cause is overall CPU utilization, which affects all processes, including SNMP. So, reducing CPU load (especially on the control plane CPU) is recommended. This is more likely the root cause if the SNMP-CPUHOG errors point to a variety of OIDs.
%SNMP-3-INTERRUPT_CALL_ERR : [chars] function, cannot be called from interrupt handler
Explanation This message indicates that a call has been made to the function from an interrupt handler. This is not permitted because it will fail and device will reboot down the stack in malloc call.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
%SNMP-3-ISSU_ERR : [chars]
Explanation Error happens when doing ISSU Versioning Operation
Recommended Action Report this message to technical support
%SNMP-3-MAX_TRAPS_EXCEED_ERR : Maximum number of traps exceeded the maximum allowed in the current sync-message to STANDBY
Explanation This message indicates the number of SNMP traps defined exceeded the maximum we can accomodate in a checkpoint sync-message. You, the developer need to increase SNMP_SYNC_BITMASK_MAX to a higher value. Please check smci_rf_status_event() for further details.
Recommended Action Developers will never see this error message.
%SNMP-3-NON_POSITIVE_IFINDEX : [chars] has [dec] non-positive ifIndices.
Explanation ifIndex-table file has some invalid entries that have non-positive ifIndex values. Ignoring invalid entries.
Recommended Action If ifIndex-table is not needed, please delete the file from nvram.
%SNMP-3-RESPONSE_DELAYED : processing [chars] of [chars] ([dec] msecs)
Explanation SNMP OID that is not responding within the threshold time specified
Recommended Action Get the OID causing the error and block using snmp views Contact mib owners to solve the issue further
%SNMP-3-SYNCFAIL : SNMP MIB Sync Failure: [chars]
Explanation One of the SNMP MIB Sync to standby failed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%SNMP-3-TOOMANYIFINDICES : Some ifindices might not be persisted.
Explanation There are too many ifindices and the system is unable to persist all of them.
Recommended Action Most likely, this is a system limitation and there is no workaround.
%SNMP-3-TRAPBLOCK : Attempt to generate SNMP trap from a process with blocking disabled
Explanation During processing, a process with blocking disabled attempted to generate an SNMP trap which would block. This is not allowed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%SNMP-3-TRAPINTR : Attempt to generate SNMP trap from interrupt level
Explanation During the processing of an interrupt, the code attempted to generate an SNMP trap. This is not allowed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%SNMP-4-HIGHCPU : Process exceeds [dec]ms threshold ([dec]ms IOS quantum) for [chars] of [chars]--result [chars]
Explanation SNMP took more than the warning threshold processing a var-binding.
Recommended Action If feasible, use the <bold>debug snmp packet<nobold> command to determine the contents of the SNMP request that is causing the message. Copy the error message exactly as it appears, and report it along with any debug output to your technical support representative. Some MIB objects require a relatively large amount of time to process. MIB objects in the multi-variable-binding are processed one by one. If possible, MIB objects appearing in this message should NOT be retrieved using multi-variable-binding SNMP PDUs.
%SNMP-4-IFINDEXPERS_INTERNAL_ERROR : An internal error occurred in ifindex persistence code.
Explanation There is an unexpected internal error in ifindex persistence software.
Recommended Action None
%SNMP-4-NOENGINEID : Remote snmpEngineID for [IP_address] not found when creating user: [chars]
Explanation An attempt to create a user failed.This is likely because the engine ID of the remote agent (or SNMP manager) was not configured.
Recommended Action Configure the remote snmpEngineID and reconfigure the user. If the problem persists, copy the error message exactly as it appears, and report it to your technical support representative.
%SNMP-4-NOENGINEIDV6 : Remote snmpEngineID for [IPV6 address] not found when creating user: [chars]
Explanation An attempt to create a user failed.This is likely because the engine ID of the remote agent (or SNMP manager) was not configured.
Recommended Action Configure the remote snmpEngineID and reconfigure the user. If the problem persists, copy the error message exactly as it appears, and report it to your technical support representative.
%SNMP-4-NOFLASH : Reading snmpEngineBoots from flash failed
Explanation An attempt to read the snmpEngineBoots file from flash failed. Most likely, this means that the flash card does not exist on the router. This message should appear only when the router is reloaded.
Recommended Action Check if installing a flash card makes the message go away. If a flash card exists already, it may be full. Try erasing flash and reloading the router. If after these steps, the problem persists, copy the error message exactly as it appears, and report it to your technical support representative.
%SNMP-4-TRAPDROP : [chars]
Explanation An attempt was made to generate an SNMP trap, but the trap could not be sent because of the reason given in this message. Most likely, this message means that the SNMP traps process is not running.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative. Use the <bold>show process<nobold> command to determine whether the SNMP traps process is running. If it is not running, reload the system. If, after reloading, the SNMP traps process is still not running, there may not be enough memory for it to run.
%SNMP-5-CHASSISALARM : Chassis Alarm Trap: tmpAlarm([chars]), minorAlarm([chars]), and/or majorAlarm([chars])
Explanation This message shows the SNMP agent sends out the Chassis Alarm On/Off Traps to the engine ID of the remote agent (or SNMP manager) because the corresponding chassis alarm is on/off.
Recommended Action None
%SNMP-5-COLDSTART : SNMP agent on host [chars] is undergoing a cold start
Explanation The snmp server underwent a coldstart.
Recommended Action Notification message only. No action required.
%SNMP-5-LINK_DOWN : LinkDown:Interface [chars] changed state to down
Explanation The state of the Interface is changed to down.
Recommended Action None
%SNMP-5-LINK_UP : LinkUp:Interface [chars] changed state to up
Explanation The state of the Interface is changed to up.
Recommended Action None
%SNMP-5-MODULERESET : [chars] object has been set to 'reset' for [chars]=[dec] from IP address [chars].
Explanation The SNMP server has reset a module.
Recommended Action Notification message only. No action required.
%SNMP-5-MODULETRAP : Module [dec] [[chars]] Trap
Explanation This message shows the SNMP agent sends out the Module Up/Down Traps to the engine ID of the remote agent (or SNMP manager) because the corresponding module is up/down.
Recommended Action None
%SNMP-5-WARMSTART : SNMP agent on host [chars] is undergoing a warm start
Explanation The snmp server underwent a warmstart.
Recommended Action Notification message only. No action required.
%SNMP-6-VIEWNAMELENGTH : Invalid view name length; truncated.
Explanation SNMP agent generated view length greater than that allowed by definition so the view name was truncated to fit the defined maximum view name length.
Recommended Action Make sure your trap group and view names are setup appropriately. You can override with 'snmp-server group' command. Notify Cisco that this needs to be fixed.
SNMP_MGR
%SNMP_MGR-3-BADAGETIMER : Unexpected age timer found on session [hex]
Explanation An internal timer was found running when it should not have been.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative. Disable the SNMP manager via the no snmp-server manager command. Then re-enable it via the snmp-server manager command. This should effectively reset all of the internal structures.
%SNMP_MGR-3-BADINFORMTRANSPORT : Unknown inform transport type: [chars]
Explanation This SNMP inform destination uses an unknown transport type. Inform notifications cannot be sent to this destination.
Recommended Action Copy the error message and the output from 'show techsupport' exactly as it appears, and report it to your technical support representative.
%SNMP_MGR-3-BADOP : Unknown operation code [int]
Explanation An SNMP PDU delivered to the SNMP manager contains an unknown operation code.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%SNMP_MGR-3-BADPDUTYPE : Received unknown PDU type: [int]
Explanation The SNMP manager was delivered a PDU of an unknown type.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%SNMP_MGR-3-BADTRANSPORT : Unknown transport type: [int]
Explanation The SNMP manager was delivered a PDU from an unknown transport type.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%SNMP_MGR-3-BADUSECOUNT : Corrupted use counter found on session [hex]
Explanation A cached SNMP session structure appears to have been corrupted.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative. Disable the SNMP manager via the no snmp-server manager command. Then re-enable it via the snmp-server manager command. This should effectively reset all of the internal structures.
%SNMP_MGR-3-MISSINGHOST : Cannot locate information on SNMP informs host: [IP_address]
Explanation A table entry for the mentioned SNMP informs destination cannot be found. As a result, inform notifications will not be sent to this destination.
Recommended Action Run the 'show snmp host' and 'show snmp' commands. Copy the error message and output from the show commands exactly as they appear, and report it to your technical support representative. Deleting and re-adding the informs destination via the 'snmp-server host' configuration command may clear the condition. Otherwise, reloading the system may be necessary.
%SNMP_MGR-3-MISSINGHOSTIPV6 : Cannot locate information on SNMP informs host: [IPV6 address]
Explanation A table entry for the mentioned SNMP informs destination cannot be found. As a result, inform notifications will not be sent to this destination.
Recommended Action Run the 'show snmp host' and 'show snmp' commands. Copy the error message and output from the show commands exactly as they appear, and report it to your technical support representative. Deleting and re-adding the informs destination via the 'snmp-server host' configuration command may clear the condition. Otherwise, reloading the system may be necessary.
%SNMP_MGR-3-NOPROC : Failed to create SNMP Manager process
Explanation The SNMP manager process was unable to initialize. This is most likely due to a lack of memory.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative. Use the show memory command to examine the amount of available memory. If free memory is low, you may need to reconfigure and/or reload the system.
%SNMP_MGR-3-RESPDROP : Insufficient memory to handle response to request id [int]
Explanation An SNMP response PDU was received but there was not enough memory available in order to cache the response and return it to the original requesting IOS application.
Recommended Action If this was only a transient problem, the original SNMP request will likely be resent, another SNMP response will be returned and delivered to the original requesting IOS application. If this message repeats, then you will need to free up some memory in order for the SNMP manager to function. Use show memory to verify whether available memory is low. You may need to reconfigure and/or reload the system in order to free up some memory. Otherwise you can disable the SNMP manager functionality via the no snmp-server manager command.
%SNMP_MGR-3-SESSIONINUSE : Attempt to destroy session [hex] that is still in use
Explanation An attempt was made to remove a cached SNMP session structure, however it appears that the session is still in use, and therefore should not be removed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%SNMP_MGR-4-BADAUTHTYPE : Unsupported SNMP authorization type: [int]
Explanation An unknown SNMP authorization type was found. This may result in the inability of the SNMP manager functionality to correctly send and/or receive SNMP messages to/from a particular SNMP agent.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%SNMP_MGR-4-BADRESPONSESTATUS : Unknown response status code: [int]
Explanation The SNMP Manager process received an internal response with an unknown status code.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%SNMP_MGR-4-EMPTYQUEUE : Input queue is empty
Explanation The SNMP Manager process was notified that it needs to process it's input queue. But, when the queue was examined, it was found to be empty.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%SNMP_MGR-4-NOCANCEL : Unable to cancel a previously sent inform request.
Explanation The number of unacknowledged inform requests in-flight has reached the configured maximum limit. In order to make available resources for sending out a new inform request, one of these older inform requests must be cancelled. The algorithm used to choose the most appropriate inform to cancel has failed to choose any. The new inform that was to be sent will be dropped instead.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%SNMP_MGR-4-NOTENABLED : SNMP Manager not enabled (requested by [chars])
Explanation An IOS application is attempting to make use of the SNMP manager's services. However the SNMP manager functionality has not been enabled.
Recommended Action If you wish to enable the SNMP manager services you may do so via the 'snmp-server manager' config command. Otherwise the IOS application that is requesting these services is given in the message. Disable or reconfigure this application such that it no longer tries to make SNMP manager requests.
SNMP_MIB_ISSU
%SNMP_MIB_ISSU-2-GET_BUFFER : SNMP MIB ISSU client failed to get buffer for message. Error: [dec] ([chars])
Explanation The SNMP MIB 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)
%SNMP_MIB_ISSU-2-INIT : SNMP MIB ISSU client initialization failed to [chars]. Error: [dec] ([chars])
Explanation The SNMP MIB 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SNMP_MIB_ISSU-2-SEND_NEGO_FAILED : SNMP MIB ISSU client failed to send negotiation message. Error: [dec] ([chars])
Explanation The SNMP MIB 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)
%SNMP_MIB_ISSU-2-SESSION_NEGO : SNMP MIB ISSU client encountered unexpected client nego_done. Error: [dec] ([chars])
Explanation An ISSU-compliant client transitions through a series of internal states. The SNMP MIB 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>)
%SNMP_MIB_ISSU-2-SESSION_REGISTRY : SNMP MIB ISSU client failed to register session information. Error: [dec] ([chars])
Explanation The SNMP MIB 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>)
%SNMP_MIB_ISSU-3-CAP_INVALID_SIZE : SNMP MIB ISSU client capability list is empty.
Explanation The SNMP MIB ISSU client capability exchange list size is invalid.
Recommended Action LOG_STD_SH_CMD_ACTION( show issu capability entires <Client_ID>)
%SNMP_MIB_ISSU-3-CAP_NOT_COMPATIBLE : SNMP MIB ISSU client capability exchange result incompatible.
Explanation The SNMP MIB ISSU client capability exchange have negotiated as incompatible with the peer.
Recommended Action LOG_STD_SH_CMD_ACTION( show issu negotiated capability <Session_ID>)
%SNMP_MIB_ISSU-3-INVALID_SESSION : SNMP MIB ISSU client does not have a valid registered session.
Explanation The SNMP MIB 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>)
%SNMP_MIB_ISSU-3-MSG_NOT_OK : SNMP MIB ISSU client 'Message Type [dec]' is not compatible
Explanation The SNMP MIB 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>)
%SNMP_MIB_ISSU-3-MSG_SIZE : SNMP MIB ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] ([chars])
Explanation The SNMP MIB ISSU client failed to calculate the MTU for the specified message. The SNMP MIB 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>)
%SNMP_MIB_ISSU-3-SESSION_UNREGISTRY : SNMP MIB ISSU client failed to unregister session information. Error: [dec] ([chars])
Explanation The SNMP MIB 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>)
%SNMP_MIB_ISSU-3-TRANSFORM_FAIL : SNMP MIB ISSU client [chars] transform failed for 'Message Type [dec]'. Error: [dec] ([chars])
Explanation The SNMP MIB 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 SNMP MIB 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>)
SONET
%SONET-3-ALARMTIMERFAIL : [chars]
Explanation Alarm timer monitor process creation failed
Recommended Action Report this occurrence to Engineering. Use Topic to search for a similar DDTS. If you find none, write a DDTS for this problem.
%SONET-3-APSCOMM : [chars]: [chars]
Explanation APS errors related to failure of working-protect communication
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SONET-3-APSCOMMCHANGE : [chars]: Link to [chars] channel reverts to PGP protocol version [dec]
Explanation APS has reverted to a different version of the PGP protocol between working and protect routers.
Recommended Action None - information only.
%SONET-3-APSCOMMEST : [chars]: Link to [chars] channel established -PGP protocol version [dec]
Explanation APS has established connectivity between working and protect routers.
Recommended Action None - information only.
%SONET-3-APSCOMMLOST : [chars]: Link to [chars] channel lost
Explanation Connectivity between Working and Protect has been lost. APS operation can continue in degraded mode.
Recommended Action Restore connectivity between working and protect routers.
%SONET-3-APSEVENT : [chars]: APS event type error: event [dec] undefined
Explanation APS software has malfunctioned
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SONET-3-APSHAHOLDTIME : [chars]: [chars]
Explanation Messages issued by HA APS when PGP holdtime is adjusted
Recommended Action None - information only.
%SONET-3-APSNCHN : APS Local request [dec] has no corresponding channel number
Explanation APS software has malfunctioned.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SONET-3-APSNOINTFC : APS No interfaces available for IP connection
Explanation APS requires an out-of-band path for inter-router communication.
Recommended Action Configure an out-of-band path for inter-router APS communication
%SONET-3-APSSYNCSECONDARY : [dec]/[dec]: No hwidb
Explanation New secondary RP unable to find device descriptor block corresponding to slot/unit specified by primary RP.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SONET-3-BADAUTH : [chars]: APS Bad authentication from [IP_address],
Explanation APS software has detected unauthorized message.
Recommended Action This message could result from improper configuration, unauthorized access, or packet corruption. LOG_STD_ACTION
%SONET-3-BADTCA : TCA signal [dec] is invalid
Explanation TCA software has malfunctioned.
Recommended Action Report this occurrence to Engineering. Use Topic to search for a similar DDTS. If you find none, write a DDTS for this problem.
%SONET-3-BADTCATH : TCA threshold [int] is not supported
Explanation The specific TCA threshold is not supported
Recommended Action Report this occurrence to Engineering. Use Topic to search for a similar DDTS. If you find none, write a DDTS for this problem.
%SONET-3-DELAYTIMER : [chars]
Explanation Delay timer creation failure
Recommended Action Report this occurrence to Engineering. Use Topic to search for a similar DDTS. If you find none, write a DDTS for this problem.
%SONET-3-MISVER : [chars]: APS version mismatch.t WARNING: Loss of Working-Protect link can deselect botht protect and working interfaces. [chars] router requirest software upgrade for full protection.
Explanation APS software has detected that either the working or protect router requires software upgrade. APS operation can continue prior to the upgrade.
Recommended Action Upgrade specified router.
%SONET-3-NOBUFFER : No buffer available for sending APS message
Explanation No data buffer was available for sending APS message.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%SONET-3-NOSOCKET : Unable to open socket
Explanation APS system unable to open a socket for communication purposes
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SONET-4-ALARM : [chars]: [chars] [chars]
Explanation The specified SONET Alarm has been declared or released.
Recommended Action Recommended action is to repair the source of the alarm.
%SONET-4-APSMM : [chars]: APS mode mismatch -[chars]
Explanation There has been a unidirectional/bidirectional mismatch detected by the APS system
Recommended Action It is recommended that the router configuration match the provisioned circuit.
%SONET-6-APSMANPRO : Manual APS switchover initiated for [chars]
Explanation APS manual switchover is initialted
Recommended Action None - normal situation.
%SONET-6-APSREFL : [chars]: Remote reflection of APS status now [chars]
Explanation APS software has detected a change in the reflected local APS status
Recommended Action None - normal situation.
%SONET-6-APSREMSWI : [chars]: Remote APS status now [chars]
Explanation APS software has detected a change in the APS status of the remote interface
Recommended Action None - normal situation.
SONETIFMIB
%SONETIFMIB-3-NULLPTR : NULL pointer at step = [dec]
Explanation Attempted to initialize ifAlias for VT using a NULL pointer.
Recommended Action No action is required.
%SONETIFMIB-3-OUTOFBOUND : Out of bound values path=[dec]/tug2=[dec]/e1=[dec]
Explanation Invalid values used while determining the ifAlias
Recommended Action No action is required.
SONETMIB
%SONETMIB-1-DELETE : could not delete interface, if_index=[dec]
Explanation The specified interface was not successfully dequeued.
Recommended Action No action is required.
%SONETMIB-1-LOSTUPDATE : Lost raw stats update for if_index=[dec]
Explanation None
Recommended Action None
%SONETMIB-1-MALLOCNEW : Malloc failed for new interface=[dec]
Explanation Unable to allocate enough memory to create SONET MIB structure for new interface.
Recommended Action No action is required.
%SONETMIB-3-NULLCFGPTR : NULL SONET MIB config pointer, if_index=[dec]
Explanation Attempted to initialize the SONET MIB using a NULL pointer.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
SPA_CHOC_DSX
%SPA_CHOC_DSX-3-AUTODNR : [chars] failed for slot [dec] bay [dec]
Explanation AUTODNR/USNDNR process has failed. The SPA and SIP are out of synchronization. This condition indicates a software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SPA_CHOC_DSX-3-BAD_SIZE_ERR : SPA [dec]/[dec]: [dec] [chars] events on HDLC Controller were encountered. The SPA is being restarted.
Explanation The SPA driver detected an error event on the HDLC controller.
Recommended Action The SPA driver has encountered an error event on the 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: https://mycase.cloudapps.cisco.com/start or contact your Cisco technical support representative. Be sure to provide the the information you have gathered and a tech-support to your support representative, or attach it to your case in non-zipped, plain text format (.txt).
%SPA_CHOC_DSX-3-COR_MEM_ERR : SPA [dec]/[dec]: [dec] correctable [chars] memory error(s) encountered. The error has been corrected and normal processing should continue. The memory address of most the recent error is: [hex]
Explanation The SPA driver detected a correctable memory error on the SPA card.
Recommended Action The SPA has encountered a correctable memory error on the SPA card. The error has been corrected and normal processing should continue. The hexadecimal memory address of the most recent error is specified in the message text on the console or in the system log. If the condition persists, or other errors are indicated for the SPA, copy the error message exactly as it appears. Then power down and reseat the indicated SPA card. 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: https://mycase.cloudapps.cisco.com/start or contact your Cisco technical support representative. Be sure to provide the the information you have gathered and a tech-support to your support representative, or attach it to your case in non-zipped, plain text format (.txt).
%SPA_CHOC_DSX-3-DPIDX_LKUP_ERR : Failed to retrieve datapath identifier for interface [chars]
Explanation The SPA driver is not able to retrieve the datapath identifier for the interface specified in the message. This indicates a software error.
Recommended Action No action is required.
%SPA_CHOC_DSX-3-EFC_ERROR : EFC ERROR: [chars] -[chars] [int]
Explanation The SPA Extended Flow Control encountered an error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%SPA_CHOC_DSX-3-HDLC_CTRL_ERR : SPA [dec]/[dec]: [dec] [chars] events on HDLC Controller were encountered.
Explanation The SPA driver detected an error event on the HDLC Controller.
Recommended Action The SPA driver has encountered an error event on the 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: https://mycase.cloudapps.cisco.com/start or contact your Cisco technical support representative. Be sure to provide the the information you have gathered and a tech-support to your support representative, or attach it to your case in non-zipped, plain text format (.txt).
%SPA_CHOC_DSX-3-INVALID_IF_TYPE : Invalid SPA type [dec] on [chars]. Port Number = [dec].
Explanation The software can not recognize the interface type
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SPA_CHOC_DSX-3-INVLIAD_IF_INDEX : Invalid interface index [dec] on slot/bay:[dec]/[dec]. Min. Index = [dec]. MAx. Index = [dec].
Explanation The index is not valid for the interface specified in the error message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SPA_CHOC_DSX-3-LINK_TABLE_ERR : [chars]: Could not create link table, error [dec]
Explanation Error creating link record table. Interfaces may not come up / pass traffic.
Recommended Action If the ports on the SPA are not operating as expected, power down and reseat the indicated SPA card. 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: https://mycase.cloudapps.cisco.com/start or contact your Cisco technical support representative. Be sure to provide the the information you have gathered and a tech-support to your support representative, or attach it to your case in non-zipped, plain text format (.txt).
%SPA_CHOC_DSX-3-NODESTROYSUBBLOCK : The [chars] subblock named [chars] was not removed
Explanation IDB sub-blocks could not be removed during the unprovisioning of a channel. This condition indicates a software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SPA_CHOC_DSX-3-NULL_DATA_STRUCTURE : Failed to create [chars] on slot/bay:[dec]/[dec]. Port Number = [dec].
Explanation The software resource can not be allocated for this hardware
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SPA_CHOC_DSX-3-NULL_SPA_PTR :
Explanation The pointer to an SPA value is of a null value.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%SPA_CHOC_DSX-3-NULL_VIRT_SPA_PTR : [chars]
Explanation Pointer to virtual SPA object is NULL in card prot grp.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%SPA_CHOC_DSX-3-PERIODIC_PROCESS : [chars]: periodic process error [chars].
Explanation The SPA driver detected an error with the periodic processing routine.
Recommended Action If the ports on the SPA are not operating as expected, take it out of service by issuing command hw-module subslot slot#/bay# stop followed by hw-module subslot slot#/bay# start for the indicated SPA card. 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: https://mycase.cloudapps.cisco.com/start or contact your Cisco technical support representative.
%SPA_CHOC_DSX-3-PROCESS_FAIL : process creation failed in [chars] spa type [chars] for [chars]
Explanation The Periodic one second process creation failed. This indicates a software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SPA_CHOC_DSX-3-SEMAHOG : SPA on [chars]: Semaphore Hog was encountered.Hogged by process [chars]
Explanation The semaphore used by the IPC communication between host and the SPA was hogged by one process. This behavior would cause other processes fail to send commands down to the SPA. This might result improper operation.
Recommended Action Please first stop all the traffic on the SPA and then reload the configuration by doing shut/no shut on the controllers. If the problem persists, please power cycle the SPA. 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 Bug Tookit on the Cisco web-site. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start or contact your Cisco technical support representative. Be sure to provide the the information you have gathered and a tech-support to your support representative, or attach it to your case in non-zipped, plain text format (.txt).
%SPA_CHOC_DSX-3-SPA_CMD_RETURN_ERR : SPA command [chars] return error [int]
Explanation The SPA returned an error status for a host command
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%SPA_CHOC_DSX-3-SPA_CMD_SEND_ERR : Failed to send [chars] command to SPA
Explanation The host failed to send a command to SPA
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%SPA_CHOC_DSX-3-SPA_SW_ERR : SPA on [chars]: [chars] Software error was encountered.
Explanation The SPA driver detected a Software error condition on the SPA card. This might result improper operation.
Recommended Action The SPA driver has encountered a Software error. Please first reload the configuration by doing shut/no shut on the controllers. If the problem persists, please power cycle the SPA. If the condition persists, copy the error message exactly as it appears. Next research and attempt to resolve the issue using the Bug Toolkit on the Cisco web-site. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start or contact your Cisco technical support representative. Be sure to provide the the information you have gathered and a tech-support to your support representative, or attach it to your case in non-zipped, plain text format (.txt).
%SPA_CHOC_DSX-3-SPI4_HW_ERR : SPA on [chars]: [chars] Hardware error was encountered.
Explanation The SPA driver detected a Hardware error condition on the SPA card. This might result in improper operation.
Recommended Action The SPA driver has encountered a Hardware error on the SPA's SPI4 bus. 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: https://mycase.cloudapps.cisco.com/start or contact your Cisco technical support representative. Be sure to provide the the information you have gathered and a tech-support to your support representative, or attach it to your case in non-zipped, plain text format (.txt).
%SPA_CHOC_DSX-3-T1CFG_ERROR : Interface [chars] T3 [int] T1 [int] config command error (cmd [int], arg [int], retval [int])
Explanation A command sent from the system to a linecard has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%SPA_CHOC_DSX-3-T3CFG_ERROR : Interface [chars] T3 [int] config command error (cmd [int], arg [int], retval [int])
Explanation A command sent from the system to a linecard has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%SPA_CHOC_DSX-3-UNCOR_MEM_ERR : SPA [dec]/[dec]: [dec] uncorrectable [chars] memory error(s) encountered. The memory address of most the recent error is: [hex] The SPA is being restarted.
Explanation The SPA driver detected an uncorrectable memory error condition on the SPA card. Packet corruption may result.
Recommended Action The SPA driver has encountered an uncorrectable memory error on the SPA card. The hexadecimal memory address of the most recent error is specified in the message text on the console or in the system log. 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: https://mycase.cloudapps.cisco.com/start or contact your Cisco technical support representative. Be sure to provide the the information you have gathered and a tech-support to your support representative, or attach it to your case in non-zipped, plain text format (.txt).
%SPA_CHOC_DSX-3-UNCOR_PARITY_ERR : SPA [dec]/[dec]: [dec] [chars] parity error(s) encountered. The address of the most recent error is: [hex]
Explanation The SPA driver detected an uncorrectable parity error condition on the SPA card. Packet corruption may result.
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: https://mycase.cloudapps.cisco.com/start or contact your Cisco technical support representative. Be sure to provide the the information you have gathered and a tech-support to your support representative, or attach it to your case in non-zipped, plain text format (.txt).
%SPA_CHOC_DSX-3-UNKNOWN_CMD : Unknown [chars] command recieved on slot/bay:[dec]/[dec]. Command Type = [dec]
Explanation An unknown command was recieved by the SPA card carrier
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SPA_CHOC_DSX-3-VCCFG_ERROR : Interface [chars] config command error (cmd [int], arg [int], retval [int])
Explanation A command sent from the system to a linecard has failed.
Recommended Action This is an internal software error. Decode the traceback and get the output of the show logging command on RP and SIP and check if there are any errors being reported. Try to recreate the problem to see if there is a consistant method to recreate. Check the Bug Toolkit before contacting TAC. When contacting TAC, provide the above information along with the output of the show tech-support command.
%SPA_CHOC_DSX-4-UNPROV_FAIL : Interface [chars] unprovisioning failed: [chars]
Explanation The system failed to respond to an unprovisioning command. A hidden VLAN could not be deleted within a 2 second timeout window. This condition may be caused by a system that is too busy, or by a FIB IPC failure. The line card driver code will attempt to delete the hidden VLAN.
Recommended Action If processing continues normally, no action is required. If system operation is adversely affected, LOG_STD_ACTION
SPA_CHOCX
%SPA_CHOCX-3-CHOCX_NAMESTRING_ERROR : failed to get [chars] namestring
Explanation Error in retrieving namestring of a specified Controller/IDB
Recommended Action This is a internal software error. If the error persists or occurred during normal operation, decode the traceback and LOG_STD_ACTION
%SPA_CHOCX-3-CORRUPT : Corrupt configuration, unsupported [chars] ([int]) encountered
Explanation The OC3/STM1 RP driver running configuration is corrupted.
Recommended Action SPA_CHOCX_INTERNAL_SW_ERROR_ACTION
%SPA_CHOCX-3-CREATE_FAIL : Failed to create [chars] : slot/bay:[dec]/[dec]
Explanation The channelized SPA controller descriptor block creation failed. Check the amount of available system memory.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%SPA_CHOCX-3-ERROR : Failed to create for [chars] : slot/bay:[dec]/[dec]
Explanation The channelized SPA controller encountered an error.
Recommended Action Check the memory availabe in system and LOG_STD_SH_TECH_ACTION
%SPA_CHOCX-3-FATAL_ERROR : Fatal error for [chars] : slot/bay:[dec]/[dec]
Explanation The channelized SPA controller encountered a fatal error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%SPA_CHOCX-3-FRR_ERROR : Error in handling FRR: [chars], [chars], [hex], [hex]
Explanation Error in FRR processing.
Recommended Action This is a internal software error. If this error happened while configuring FRR, try reconfiguring the interface. If the error persists or occurred during normal operation, decode the traceback and LOG_STD_ACTION
%SPA_CHOCX-3-INTFC_FAILED : Channel provisioning failed for [chars]
Explanation Channel could not be provisioned on SPA for this interface, interface corresoponding to that channel has been moved to down state. If this interface was provisoned using the user interface then it may not appear in the interface list.
Recommended Action SPA_CHOCX_INTERNAL_SW_ERROR_ACTION
%SPA_CHOCX-3-INVALID_SPA_TYPE : Invalid SPA type : slot/bay:[dec]/[dec], spa_type=[dec].
Explanation The channelized SPA type cannot be recognized by the version of Cisco IOS software currently running on the system.
Recommended Action Upgrade your system to a version of Cisco IOS software that supports this SPA type.
%SPA_CHOCX-3-NULL : [chars]
Explanation The NULL pointer was detected when getting the data structure.
Recommended Action SPA_CHOCX_ENABLE_DEBUG_ACTION
%SPA_CHOCX-3-NULL_INSTANCE : Null [chars] instance for [chars] : slot/bay:[dec]/[dec]
Explanation The instance pointer is NULL when getting data structure.
Recommended Action SPA_CHOCX_INTERNAL_SW_ERROR_ACTION
%SPA_CHOCX-3-NULL_SUBBLOCK : Null ssb for [chars]
Explanation The hwidb subblock is NULL.
Recommended Action SPA_CHOCX_INTERNAL_SW_ERROR_ACTION
%SPA_CHOCX-3-RETURN_ERROR : Return error for [chars]: return_value=[dec]
Explanation Return error code received.
Recommended Action SPA_CHOCX_INTERNAL_SW_ERROR_ACTION
%SPA_CHOCX-3-SONET_ALARM_PROC_ERR : [chars] Error has occurred while processing in the sonet alarm-proc
Explanation Either free/create of the memory failed in SONET alarm proc
Recommended Action None
%SPA_CHOCX-3-UNKNOWN_OPTION : Received unknown [chars]: option=[dec]
Explanation Unknown option received.
Recommended Action SPA_CHOCX_INTERNAL_SW_ERROR_ACTION
%SPA_CHOCX-3-XFP_UNSUPPORTED : [dec]/[dec]/[dec]: [chars] detected/inserted is not supported
Explanation Unsupported XFP has been detected or inserted in a port in Channelized SPA.
Recommended Action Remove the unsupported XFP/SFP and replace it with supported one.
%SPA_CHOCX-5-DEF_SUBRATE : [chars] [chars]
Explanation Remote subrate configuration changed.
Recommended Action Inform the network operator that subrate configuration was changed by remote end.
%SPA_CHOCX-6-SONET_ALARM : [chars] [chars] [chars] [chars] [chars]
Explanation This message is generated whenever (a) sonet alarm is present in the system (and the alarm status has been reported to the RP) or (b) sonet alarm has been removed from the system (and the alarm status has been reported to the RP
Recommended Action No action is required.
%SPA_CHOCX-6-XFP_OK : [dec]/[dec]/[dec]: [chars] detected/inserted
Explanation XFP has been detected or inserted in a port in Channelized SPA.
Recommended Action This is a information message, no action required
%SPA_CHOCX-6-XFP_REMOVED : [dec]/[dec]/[dec]
Explanation XFP removed from a port in Channelized SPA
Recommended Action This is a information message, no action required
SPA_CHOCX_MCPRP
%SPA_CHOCX_MCPRP-1-ALLOCFAIL : OC3/STM1 [dec]/[dec] [chars] allocation failure
Explanation CHOCX controller or channel memory allocation failure
Recommended Action This is a internal software error. Decode the traceback. Enable debug hw-module subslot <slot>/<bay> oir plugin when the problem is happening. Check Bug Toolkit before calling the TAC. When calling the TAC, please provide the above information along with output of show logging and the output of show tech details.
%SPA_CHOCX_MCPRP-3-APS_CMD_FAIL : Failed to send APS command [hex] to [chars] (retcode [hex])
Explanation APS command sending failed
Recommended Action This is a internal software error. If this error happened while configuring APS, try reconfiguring the interface. If the error persists or occurred during normal operation, decode the traceback and LOG_STD_ACTION
%SPA_CHOCX_MCPRP-3-CORRUPT : Corrupt configuration, unsupported [chars] ([int]) encountered
Explanation The OC3/STM1 RP driver running configuration is corrupt
Recommended Action This is a internal software error. Decode the traceback and get the output of show running-config. Check Bug Toolkit before calling the TAC. When calling the TAC, please provide the above information along with the output of show tech details
%SPA_CHOCX_MCPRP-3-FRR_ERROR : Error in handling FRR: [chars], [chars], [hex], [hex]
Explanation Error in FRR processing
Recommended Action This is a internal software error. If this error happened while configuring FRR, try reconfiguring the interface. If the error persists or occurred during normal operation, decode the traceback and LOG_STD_ACTION
%SPA_CHOCX_MCPRP-3-NULL_SUBBLOCK : Null ssb for [chars]
Explanation The hwidb subblock is NULL
Recommended Action This is a internal software error. Decode the traceback and get the output of show running-config. Check Bug Toolkit before calling the TAC. When calling the TAC, please provide the above information along with the output of show running and show tech details.
%SPA_CHOCX_MCPRP-3-PLUGIN_ERR : [chars]
Explanation The RP plugin encountered an error during one of the Plugin calls
Recommended Action This is a internal software error. Decode the traceback. Enable debug hw-module subslot <slot>/<bay> oir plugin when the problem is happening. Check Bug Toolkit before calling the TAC. When calling the TAC, please provide the above information along with the output of show logging and the output of show tech details.
%SPA_CHOCX_MCPRP-3-TIMEOUT : Interface ([chars]): [chars]
Explanation The CHOCX RP driver queries the LC for SONET information, the LC didn't reply.
Recommended Action This is a internal software error. Decode the traceback. Enable debug hw-module subslot <slot>/<bay> command. Check Bug Toolkit before calling the TAC. When calling the TAC, please provide the above information along with the output of show logging and the output of show tech<NoCmdBold details.
%SPA_CHOCX_MCPRP-5-DEF_SUBRATE : [chars] [chars]
Explanation Remote subrate configuration changed
Recommended Action Inform the network operator that subrate configuration changed by remote end
%SPA_CHOCX_MCPRP-5-PATH_UPDOWN : Path [chars], changed state to [chars]
Explanation A Sonet high order path changed its state.
Recommended Action This is a internal software error. Decode the traceback and get the output of show controller sonet. Look into this output to see if there are any alarms being reported at the path level. Check Bug Toolkit before calling the TAC. When calling the TAC, please provide the above information along with the output of show tech details
%SPA_CHOCX_MCPRP-5-T3_UPDOWN : T3 [chars], changed state to [chars]
Explanation A T3 within STS1 changed its state.
Recommended Action This is a internal software error. Decode the traceback and get the output of show controller sonet. Look into this output to see if there are any alarms being reported at the T3 level. Check Bug Toolkit before calling the TAC. When calling the TAC, please provide the above information along with the output of show tech details
SPA_CT3
%SPA_CT3-3-INVALID_SPA_TYPE : Invalid SPA type : slot/bay:[dec]/[dec], spa_type=[dec].
Explanation The Channelized T3 SPA type cannot be recognized by the version of Cisco IOS software currently running on the system.
Recommended Action Upgrade your system to the latest version of Cisco IOS software in your release train. If you require further assistance, LOG_STD_SH_TECH_ACTION
%SPA_CT3-3-PROCESS_FAIL : process creation failed for [chars]
Explanation A command could not be processed because of a process creation failure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SPA_CT3-3-SUBRATE_FPGA_DL_FAILED : [chars]: Failed to download the subrate FPGA image.
Explanation The indicated SPA was not able to download the subrate FPGA image during card initialization sequence. The image might be corrupted and the system will try to recover from this error by upgrading the image.
Recommended Action If the system cannot recover from this error automatically after a few attempts, it will power-off the affected SPA. In this case, copy the error message exactly as it appears and gather the output of the show hw-module subslot slot/subslot fpd and show hw-module subslot slot/subslot oir commands, then contact your technical support representative with the gathered information.
%SPA_CT3-5-DEF_SUBRATE : [chars] [chars]
Explanation Remote subrate configuration changed
Recommended Action Inform the network operator that subrate configuration changed by remote end
SPA_DSPRM
%SPA_DSPRM-3-DSPALARM : Received alarm indication from dsp ([dec]/[dec]/[dec]).
Explanation Operational error detected in DSP.
Recommended Action Reload the SPA card and if the problem persists LOG_STD_ACTION
%SPA_DSPRM-3-DSPALARMINFO : [chars]
Explanation DSP Alarm Data
Recommended Action Reload the SPA card and if the problem persists LOG_STD_ACTION
%SPA_DSPRM-3-INSUFFICIENT : Insufficient memory for [chars]
Explanation Insufficient memory for SPA-DSP DSPRM operation
Recommended Action Enter the show memory summary command to attempt to determine the cause of the error. LOG_STD_REDUCE_ACTION
%SPA_DSPRM-5-RESTART : DSP ([dec]/[dec]/[dec]) is restarted
Explanation DSP device restarted
Recommended Action No action is required.
%SPA_DSPRM-5-UPDOWN : DSP ([dec]/[dec]/[dec]) is [chars]
Explanation DSP device changed state up/down
Recommended Action No action is required.
SPA_FPD
%SPA_FPD-2-PWR_NO_OK : SPA POWER OK signal is not asserted for [chars] in [chars] for FPD upgrade.
Explanation The check for SPA POWER OK signal assertion failed. This might indicate a HW problem with the SPA.
Recommended Action Contact your Cisco technical support representative to have the SPA replaced.
%SPA_FPD-3-ADM106X_EEPROM_READ_ERROR : [chars]: Failed to read the content of ADM106x [chars] EEPROM section -[chars]
Explanation The read operation to ADM106x is performed through C2W serial interface from SPA carrier card, the indicated failure might be caused by busy C2W serial interface.
Recommended Action Retry the same operation again later. If the problem persists, remove the configuration of the SPA before trying again the operation.
%SPA_FPD-3-ADM106X_EEPROM_VERIFY_ERROR : [chars]: Verification of write operation failed in ADM106x [chars] EEPROM section for address [hex] -read value '[hex]', expected value '[hex]'.
Explanation The verification of the write operation has found a mismatch on the EEPROM data. The problem might be an indication of aging effect on the device that cannot longer hold written data.
Recommended Action Retry the upgrade operation again later. If the problem persists, replace the SPA.
%SPA_FPD-3-ADM106X_EEPROM_WRITE_ERROR : [chars]: Failed to write new configuration into ADM106x [chars] EEPROM section -[chars]
Explanation The write operation to ADM106x is performed through C2W serial interface from SPA carrier card, the indicated failure might be caused by busy C2W serial interface.
Recommended Action Retry the upgrade operation again later. If the problem persists, remove the configuration of the SPA before trying again the upgrade operation.
%SPA_FPD-3-ADM106X_READ_VER_ERROR : [chars]: Failed to read version info from ADM106x device -[chars]
Explanation The read operation to ADM106x is performed through C2W serial interface from SPA carrier card, the indicated failure might be caused by busy C2W serial interface.
Recommended Action Try to reload the SPA with hw-module subslot slot#/subslot# reload command to correct the failure. If problem persists, move the SPA to another bay of the carrier card.
%SPA_FPD-3-GETVER_FAILED : [chars]: Failed to get FPD version for [chars] (ID=[dec]): [chars].
Explanation Failed to get FPD version due to either IPC problem or operation error. The card will be disabled.
Recommended Action Check SPA seating and SPA status. Ensure compatibility among FPD, IOS and possible SPA firmware by comparing output of command show hw-module subslot fpd with IOS Release Notes. Obtain IOS version by command show version.
%SPA_FPD-3-IHEX_PARSE_ERROR : NULL
Explanation This error is seen when there is a problem in the format of the Intel HEX data; it should not be seen under normal operation.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SPA_FPD-3-JTAG_ERR : [chars]: Failed to program a [chars] FPD image file. Error code [hex].
Explanation While attempting to program a SPA FPGA via JTAG bus, an error occurs. It could be caused by an outdated carrier card FPGA or SPA connection. It may also flag an internal software error.
Recommended Action Retry the upgrade after reseating SPA. Verify carrier card FPGA is current. Copy exact the error message and report to TAC.
%SPA_FPD-3-PWR_OFF_FAILED : Failed to power-off [chars] in [chars] for FPD offline upgrade within [dec] seconds.
Explanation The power-off operation of the indicated SPA failed within the number of specified seconds. This might indicate that the time used to wait for SPA to power-off is not long enough, which can happen if the SPA has a lot of interfaces configured.
Recommended Action Retry the upgrade operation again later. If the problem persists, remove the configuration of the SPA before trying again the upgrade operation.
%SPA_FPD-3-SMM665_CONF_WRITE_ERROR : [chars]: Failed to write new configuration into SMM665 device.
Explanation The write operation to SMM665 is performed through C2W serial interface from SPA carrier card, the indicated failure might be caused by busy C2W serial interface.
Recommended Action Retry the upgrade operation again later. If the problem persists, remove the configuration of the SPA before trying again the upgrade operation.
%SPA_FPD-3-SW_ERROR : NULL
Explanation This error is seen when there is a problem in internal software coding; it should not be seen under normal operation.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SPA_FPD-3-UPGRADE_FAILED : [chars]: Failed to upgrade FPD, [chars].
Explanation The FPD image upgrade operation failed. This error is specific to the SPA. The cause could be a wrong image file, error in accessing fpga storage, physical interrupt such as power failure or card removal. Depending on SPA type and error cause, the card could be in an unusable status. Normally the system automatically reattempts the upgrade and shuts the card after repeated failures.
Recommended Action Do not interrupt the system while an FPD upgrade is in progress. Obtain the matching FPD package. Refer to IOS Release Notes for more information on obtaining the correct FPD package for the SPA. Review the output of the RP FPD logs.
%SPA_FPD-4-UPGRADE_ABORTED : [chars]: Upgrade aborted for [chars] (ID=[dec]) -[chars]
Explanation The upgrade operation for the FPD image was aborted because the provided image cannot be used by the driver to perform the image programming operation.
Recommended Action Make sure that the provide FPD image package for the FPD upgrade operation is a valid one for the Cisco IOS release in use. This can be verified with the show upgrade fpd package default command to display the required FPD image package version for the IOS image.
%SPA_FPD-6-IMG_CORRUPTION : [chars]: FPD image corruption detected for [chars] (ID=[dec]), forcing upgrade of the corrupted image to correct this problem.
Explanation The software detected corruption on a FPD image and it is triggering the FPD automatic upgrade mechanism to correct the problem.
Recommended Action No Action is required.
SPA_GE_DWDM
%SPA_GE_DWDM-3-DWDM_ERROR : [chars]
Explanation SPA driver detected an error in the DWDM init routine
Recommended Action The SPA driver has detected problem with DWDM init routine. If the ports on the SPA are not operating as expected, power down and reseat the indicated SPA card. 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: https://mycase.cloudapps.cisco.com/start 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).
%SPA_GE_DWDM-3-MALLOC_FAILED : [chars]
Explanation The SPA driver detected a memory error on the SPA card
Recommended Action Reload the card and if the problem persists, call the TAC
%SPA_GE_DWDM-3-NULL_DATA_STRUCTURE : [chars] [dec] [dec]
Explanation The SPA driver detected NULL data during DWDM initialization
Recommended Action Reload the SPA card and if the problem persists contact your technical support representative
%SPA_GE_DWDM-3-PLL_NOT_LOCKED : [chars] not locked after [dec] retries [hex]
Explanation The SPA driver failed to initialize the PLL
Recommended Action The SPA driver has detected problem with DWDM init routine. If the ports on the SPA are not operating as expected, power down and reseat the indicated SPA card. 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: https://mycase.cloudapps.cisco.com/start 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).
%SPA_GE_DWDM-3-SFP_DETECT : [chars]
Explanation The SPA driver did not detect a Cu-SFP for the port
Recommended Action Please plugin a CISCO compliant SFP in the corresponding port and retry the command
%SPA_GE_DWDM-3-UT2_SPA : [chars]
Explanation The SPA driver did not detect a UT2 transponder module
Recommended Action Check if the SPA is a DWDM SPA before executing the command
SPA_LNM
%SPA_LNM-2-REMEXCEED : Interface [chars], noise exceeded above removal threshold
Explanation Noise on the link has exceeded above the threshold value configured for link removal
Recommended Action This link requires administrative attention
%SPA_LNM-2-REMEXCEEDLASTLINK : Interface [chars], Last link in bundle, noise exceeded above removal threshold
Explanation Noise on the link has exceeded above the threshold value configured for link removal. However, this link is the last link in the multilink bundle and it is not removed from the service.
Recommended Action This link requires administrative attention
%SPA_LNM-2-REMFAILED : Interface [chars], failed to remove link from bundle
Explanation Noise on the link has exceeded above the threshold value configured for link removal. However, this link is not removed from the MLP bundle
Recommended Action No Action required
%SPA_LNM-2-REMIMPROVE : Interface [chars], noise improved below removal threshold
Explanation Noise on the link has improved and is below the threshold value configured for link removal
Recommended Action No Action required
%SPA_LNM-2-REMOVE : Interface [chars] removed from bundle. Noise exceeded above remove threshold
Explanation Noise on the link has crossed the threshold value configured for link removal. This link is taken out of the MLP bundle. This is critical status for the link. This link is under monitoring state and will be added to the bundle again when the noise level is below the configured value.
Recommended Action This link requires administrative attention
%SPA_LNM-2-RESTORE : Interface [chars] restored to bundle. Noise improved below removal threshold
Explanation Noise on the link has improved below the threshold value configured for link removal. This link is restored back to MLP bundle.
Recommended Action No action required
%SPA_LNM-2-RESTOREFAILED : Interface [chars], failed to restore link to the bundle
Explanation Noise on the link has improved and is below the threshold value configured for link removal. However, the link restore back to the MLP bundle failed
Recommended Action No Action required
%SPA_LNM-3-GENEVENT : [chars]
Explanation An Error has occured in the link noise monitoring
Recommended Action Copy the error message exactly as it appears and report it to your technical support representative
%SPA_LNM-3-MAJWARNEXCEED : Interface [chars], noise exceeded above major warning threshold
Explanation Noise on the link has exceeded above the threshold value configured for major warning level
Recommended Action This link requires administrative attention
%SPA_LNM-3-MAJWARNIMPROVE : Interface [chars], noise improved below major warning threshold
Explanation Noise on the link has improved and is below the threshold value configured for major warning level
Recommended Action No action required
%SPA_LNM-3-MINWARNEXCEED : Interface [chars], noise exceeded above minor warning threshold
Explanation Noise on the link has exceeded above the threshold value configured for minor warning level
Recommended Action This link requires administrative attention
%SPA_LNM-3-MINWARNIMPROVE : Interface [chars], noise improved below minor warning threshold
Explanation Noise on the link has improved and is below the threshold value configured for minor warning level
Recommended Action No action required
%SPA_LNM-5-DISABLED : Interface [chars], noise monitoring disabled for [chars]
Explanation Link Noise Monitoring has been disabled on the specified T1/E1 interface
Recommended Action This is an information message to notify that Link Noise Monitoring has been disabled on the T1/E1 link. No user action is required.
%SPA_LNM-5-ENABLED : Interface [chars], noise monitoring enabled for [chars]
Explanation Link Noise Monitoring has been enabled on the specified T1/E1 interface
Recommended Action This is an information message to notify that Link Noise Monitoring has been enabled on the T1/E1 link. No user action is required.
SPAN
%SPAN-3-MEM_UNAVAIL : Memory was not available to perform the SPAN operation
Explanation Unable to perform a SPAN operation because of a lack of memory
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
%SPAN-3-REDIR_HW_UNAVAIL : Redirect hardware resource not available [chars]
Explanation The system could not allocate resource for redirecting BPDUs. A possible cause of this condition is that all available redirect registers in PFC are used by other features.
Recommended Action Free up a redirect register in PFC by unconfiguring features that use redirect registers and retry allowing BPDUs for SPAN servicemodules. If Protocol Tunneling is configured on any ports, then remove Protocol Tunneling configuration from all ports to free up one redirect register.
%SPAN-3-SESS_HW_UNAVAIL : SPAN hardware resource not available [chars]
Explanation The system could not allocate a SPAN hardware resource for the feature specified in the error message. A possible cause of this condition is that all available SPAN source sessions are already in use. The system can be configured with a maximum of two SPAN source sessions or one RSPAN source session
Recommended Action Remove one of the existing SPAN or RSPAN source sessions and retry the operation.
%SPAN-3-UNKN_ERR : An internal error occurred during a SPAN operation.
Explanation SPAN detected an error in its internal operation.
Recommended Action The error might be transient, in which case trying the SPAN operation again might be successful. If this fails, the switch might need to be reloaded for the desired operation to complete.
%SPAN-3-UNKN_ERR_PORT : An internal error occurred when configuring SPAN on port [chars]
Explanation SPAN detected an error in its internal operation.
Recommended Action The error might be transient, in which case trying the SPAN operation again might be successful. If this fails, the switch might need to be reloaded for the desired operation to complete.
%SPAN-5-ERSPAN_ADJ_TUNNEL : ERSPAN Destination behind a tunnel. Shutting down session [dec]
Explanation The next hop to the IP Address specified as the ERSPAN destination lies behind a tunnel. This configuration is not supported. ERSPAN session is shut down when such configuration is detected
Recommended Action Specify another IP address as the ERSPAN destination which does not have tunnel as the next-hop adjacency.
%SPAN-5-PKTCAP_START : Packet capture session [dec] started
Explanation Packet capture is activated by user or after the scheduled time
Recommended Action Stop the capture when it is not required. You can change the rate of packets reaching CPU for capturing by configuring the rate-limit value in the monitor session type capture config mode. Protocol packets may get dropped if the capture traffic rate is high.
%SPAN-5-PKTCAP_STOP : Packet capture session [dec] ended [chars], [dec] packets captured
Explanation Packet capture is stopped. This will happen if the capture buffer is full or if user stops the capture or if capture timeout happens.
Recommended Action Packet capture is stopped. You can export the capture buffer using the 'monitor capture <id> export buffer <url>' command. Buffer can be dislayed on the console also. Delete the capture session, if it is no longer required.
%SPAN-6-SPAN_EGRESS_REPLICATION_MODE_CHANGE : Span Egress HW Replication Mode Change Detected. Current replication mode for session [chars] is [chars]
Explanation When auto detection of egress span replication mode is enabled, the system will transition any available sessions to centralized mode when an distributed egress span incapable linecard is inserted. The system will transition back the available sessions to distributed egress span mode when the last distributed egress span incapable linecard is removed
Recommended Action To prevent a session switching back to distributed egress span mode,use the command monitor session egress replication-mode centralized
SPANTREE
%SPANTREE-2-BLOCK_BPDUGUARD : Received BPDU on port [chars] with BPDU Guard enabled. Disabling port.
Explanation A BPDU was received in the interface specified in the error message that has the spanning tree BPDU Guard feature enabled. As a result, the interface was administratively shut down.
Recommended Action Either remove the device sending BPDUs or disable the BPDU Guard feature. The BPDU Guard feature can be locally configured on the interface or globally configured on all ports that have portfast enabled. After the conflict has been resolved, reenable the interface by entering the no shutdown command in interface configuration mode.
%SPANTREE-2-BLOCK_BPDUGUARD_VP : Received BPDU on port [chars], vlan [dec] with BPDU Guard enabled. Disabling vlan.
Explanation A BPDU was received on the interface and vlan specified in the error message. The spanning tree BPDU Guard feature was enabled and configured to shutdown the vlan. As a result, the vlan was placed in the error-disabled state.
Recommended Action Either remove the device sending BPDUs or disable the BPDU Guard feature. The BPDU Guard feature can be locally configured on the interface or globally configured on all ports that have portfast enabled. After the conflict has been resolved, reenable the interface/vlan by entering the clear errdisable command.
%SPANTREE-2-BLOCK_PVID_LOCAL : Blocking [chars] on [chars]. Inconsistent local vlan.
Explanation The spanning tree port associate with the listed spanning tree instance and interface will be held in spanning tree blocking state until the Port VLAN ID (PVID) inconsistency is resolved. The listed spanning tree instance is that of the native VLAN id of the listed interface.
Recommended Action Verify that the configuration of the native VLAN id is consistent on the interfaces on each end of the 802.1Q trunk connection. Once corrected, spanning tree will automatically unblock the interfaces as appropriate.
%SPANTREE-2-BLOCK_PVID_PEER : Blocking [chars] on [chars]. Inconsistent peer vlan.
Explanation The spanning tree port associate with the listed spanning tree instance and interface will be held in spanning tree blocking state until the port VLAN Id (PVID) inconsistency is resolved. The listed spanning tree instance is that of the native VLAN id of interface on the peer switch to which the listed interface is connected.
Recommended Action Verify that the configuration of the native VLAN id is consistent on the interfaces on each end of the 802.1Q trunk connection. Once corrected, spanning tree will automatically unblock the interfaces as appropriate.
%SPANTREE-2-BRIDGE_ASSURANCE_BLOCK : Bridge Assurance blocking port [chars][chars].
Explanation BPDUs were not received from a neighboring switch on the interface that has spanning tree Bridge Assurance configured. As a result, the interface was moved to the spanning tree Blocking state
Recommended Action Either disable Bridge Assurance configuration on the interface or make sure that the interface is connected to a L2 switch/bridge device
%SPANTREE-2-BRIDGE_ASSURANCE_UNBLOCK : Bridge Assurance unblocking port [chars][chars].
Explanation The interface listed in the message has been restored to normal spanning tree state after receiving BPDUs from the neighboring L2 switch/bridge
Recommended Action No action is required.
%SPANTREE-2-CHNL_MISCFG : Detected loop due to etherchannel misconfiguration of [chars] [chars]
Explanation A loop caused the misconfiguration of a channel group has been detected. An example of such a misconfiguration would be where the ports on one side of the etherchannel either aren't configured to be in the channel or failed to bundle for some reason while the other side has successfully bundled the ports into the etherchannel
Recommended Action Determine which local ports are involved using the command show interfaces status err-disabled and then check etherchannel configuration on the remote device using the command show etherchannel summary on the remote device. Once the configuration is corrected, do shutdown / no shutdown on the associated port-channel interface.
%SPANTREE-2-LOOPGUARD_BLOCK : Loop guard blocking port [chars] on [chars].
Explanation The spanning tree message age timer has expired because and no BPDUs were received from the designated bridge. Since this condition could be caused by an unidirectional link failure, the interface is put into blocking state and marked as loop guard inconsistent in order to prevent possible loops from being created
Recommended Action Issue the show spanning-tree inconsistentports command to review the list of interfaces with loop guard inconsistencies. Determine why devices connected to the listed ports are not sending BPDUs. One reason could be that they do not run the spanning tree protocol; in this case you should disable loopguard in the inconsistent interface/s or start the spanning tree protocol on the other side of the link/s.depending on the context. Another reason could be a failure in the cable: if the link has a failure that makes it unidirectional (you can transmit but you can not receive) it should be replaced with a proper cable.
%SPANTREE-2-LOOPGUARD_CONFIG_CHANGE : Loop guard [chars] on port [chars].
Explanation The spanning tree loopguard configuration for the listed interface has been changed. If enabled, the interface will be put into blocking state and marked as loopguard inconsistent when the message age timer expires because no BPDU were received from the designated bridge. This feature is mainly used to detect unidirectional links
Recommended Action Verify that this is the desired configuration for the listed interface. Correct it if this is not the desired configuration otherwise no further action is required.
%SPANTREE-2-LOOPGUARD_UNBLOCK : Loop guard unblocking port [chars] on [chars].
Explanation The listed interface has received a BPDU and therefore if the inconsistency was due to an unidirectional link failure, now the problem is not there anymore. The loop guard inconsistency is cleared for the interface which is taken out of the blocking state if appropriate.
Recommended Action No action is required.
%SPANTREE-2-NOMEM : Memory Allocation Failure -[chars]: [chars]
Explanation The system could not allocate the memory that is required for the STP feature. This condition might indicate that more memory must be installed on the system.
Recommended Action Check available memory and install more if necessary. If sufficient memory is available, reload the Cisco IOS image on the affected platform. If the error persists, LOG_STD_SH_CMD_ACTION(show tech-support and show logging)
%SPANTREE-2-PVST_PEER_BLOCK : PVST+ peer detected on port [chars]
Explanation PVST+ BPDU(s) are detected on the listed interface when MSTP PVST+ Simulation feature is disabled
Recommended Action Please make sure the PVST+ switch is removed from the network or enable the MSTP PVST Simulation feature.
%SPANTREE-2-PVST_PEER_UNBLOCK : Unblocking port [chars]
Explanation The listed interface is no longer receiving the PVST+ BPDUs. The inconsistency is cleared and the interface returns to normal operation.
Recommended Action No action is required.
%SPANTREE-2-PVSTSIM_FAIL : Blocking [chars] port [chars]: Inconsitent [chars] PVST BPDU received on VLAN [dec], claiming root [dec]:[enet]
Explanation When a MST switch is connected to a PVST+ switch, the CIST (MST00) information on the port of the MST switch must be consistently better than all the PVST+ messages if the port is designated or consistently worse than all the PVST+ messages if the port is root. If this constraint is not respected, the port on the MST switch is blocked in order to prevent a potential bridging loop
Recommended Action When STP is converging after a new switch, or switch port is added to the topology, this condition may happen transiently. The port unblocks automatically in such cases. If the port remains blocked, identify the root bridge as reported in the message, and configure a worse or better priority for the VLAN spanning tree consistent with the CIST role on the port of the MST switch. There could be more inconsistencies than the message indicates, and the port will not recover until all such inconsistencies are cleared. If you cannot determine which other VLANs have inconsistencies, disable and reenable the port. This message will appear again and specify another VLAN with inconsistencies to be fixed. Repeat this process until all inconsistencies on all VLANs are cleared.
%SPANTREE-2-PVSTSIM_OK : PVST Simulation inconsistency cleared on port [chars].
Explanation The listed interface is no longer receiving PVST BPDUs advertising an information inconsistent with the CIST port information. The PVST Simulation Inconsistency is cleared and the interface returns to normal operation
Recommended Action No action is required.
%SPANTREE-2-RECV_1Q_NON_1QTRUNK : Received 802.1Q BPDU on non 802.1Q trunk [chars] [chars].
Explanation The listed interface on which a SSTP BPDU was received, was in trunk mode but not using 802.1Q encapsulation.
Recommended Action Verify that the configuration and operational state of the listed interface and that of the interface to which it is connected have the same mode (access vs trunk). If mode is trunk, verify the same encapsulation (ISL, 802.1Q). Once these parameters are consistent, spanning tree will automatically unblock the interfaces as appropriate.
%SPANTREE-2-RECV_BAD_TLV : Received SSTP BPDU with bad TLV on [chars] [chars].
Explanation The list interface received a SSTP BPDU that was missing the VLAN id tag. The BPDU is discarded.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%SPANTREE-2-RECV_PVID_ERR : Received BPDU with inconsistent peer vlan id [dec] on [chars] [chars].
Explanation The listed interface received a SSTP BPDU that is tagged with a VLAN id that does not match the VLAN id on which the BPDU was received. This occurs when the native VLAN is not consistently configured on both ends of a 802.1Q trunk.
Recommended Action Verify that the configuration of the native VLAN id is consistent on the interfaces on each end of the 802.1Q trunk connection. Once corrected, spanning tree will automatically unblock the interfaces as appropriate.
%SPANTREE-2-ROOTGUARD_BLOCK : Root guard blocking port [chars] on [chars].
Explanation A BPDU was received on the listed interface which advertizes a superior spanning tree root bridge to that currently in use. The interface is put into blocking state and marked as root guard inconsistent in order to prevent a suboptimal spanning tree topology to form.
Recommended Action Issue the show spanning-tree inconsistentports command to review the list of interfaces with root guard inconsistencies. Determine why devices connected to the listed ports are sending BPDUs with a superior root bridge and take action to prevent further occurances. Once the bogus BPDUs have been stopped, the interfaces will automatically recover and resume normal operation. Make sure that it is appropriate to have root guard enabled on the interface.
%SPANTREE-2-ROOTGUARD_CONFIG_CHANGE : Root guard [chars] on port [chars].
Explanation The spanning tree root guard configuration for the listed interface has been changed. If enabled, any BPDU received on ths interface which advertizes a superior spanning tree root bridge to that already in use will cause the interface to be put into blocking state and marked as root guard inconsistent.
Recommended Action Verify that this is the desired configuration for the listed interface. Correct it if this is not the desired configuration otherwise no further action is required.
%SPANTREE-2-ROOTGUARD_UNBLOCK : Root guard unblocking port [chars] on [chars].
Explanation The listed interface is no longer receiving BPDUs advertizing a superior root bridge. The root guard inconsistency is cleared for the interface and then it is taken out of the blocking state if appropriate.
Recommended Action No action is required.
%SPANTREE-2-UNBLOCK_CONSIST_PORT : Unblocking [chars] on [chars]. Port consistency restored.
Explanation The Port VLAN ID and/or Port Type inconsistencies have been resolved and spanning tree will now unblock the listed interface of the listed spanning tree instance as appropriate.
Recommended Action No action is required.
%SPANTREE-3-BAD_PORTNUM_SIZE : Rejected an attempt to set the port number field size to [dec] bits (valid range is [dec] to [dec] bits).
Explanation The spanning tree port identifier is a 16 bit wide field that is, by default, divided evenly between port priority and port number, each sub field being 8 bits wide. This allows the port number field to represent port numbers between 1 and 255. However, on systems with greater than 255 ports, the size of port number portion of the port id must be increased to support the greater number of ports. This is done by the STP subsystem at system init time since the maximum number of ports on a particular platform will not change. This error would only occur due to an error in the platform specific code which caused it to request more (or less) bits than were possible. This error should not be seen in any production images.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show version command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%SPANTREE-3-ERR_NO_UNIDIR_EDGE : [chars]: Portfast disabled, reverting to bidirectional mode
Explanation Because UCP is for edge ports only, portfast must be configured. This messageis typically seen when spanning-tree portfast is enabled on a port, thenauthentication control-direction is set to inbound (unidirectional), and thenportfast is disabled.
Recommended Action Re-enable portfast on the edge port. This will re-enable unidirectionalauthentication control.
%SPANTREE-3-PORT_SELF_LOOPED : [chars] disabled.-received BPDU src mac ([enet]) same as that of interface
Explanation The source MAC address contained in a BPDU received on the listed interface matches the MAC address assigned to that interface This indicates the possibility that a port is looped back to itself, possibly due to a diagnostic cable being plugged in. The interface will be administratively shutdown.
Recommended Action Check the interface configuration and any cable plugged into the interface. Once problem resolved, re-enable interface by doing a no shutdown in the interface configuration.
%SPANTREE-3-PRESTD_NEIGH : pre-standard MST interaction not configured ([chars]). Please, configure: 'spanning-tree mst pre-standard' on ports connected to MST pre-standard switches.
Explanation The switch has received a pre-standard MST BPDU on a port that is not configured for pre-standard MST BPDU transmission. The switch will automatically adjust its mode of operation on this port and will start sending pre-standard BPDUs. However, this auto-detection of pre-standard neighbors is not 100% accurate and it is recommended to configure explicitly the port for pre-standard MST BPDU transmission. This warning message will only be display once.
Recommended Action Configure 'spanning-tree mst pre-standard' on all the ports that are connected to switches running Cisco's pre-standard version of MST. It is recommended to migrate all the switches in the network to the IEEE standard MST version when it is possible.
%SPANTREE-4-PORT_NOT_FORWARDING : [chars] [chars] [chars] [chars]
Explanation The port is not forwarding packets, i.e it is not in a forwarding state
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SPANTREE-5-EXTENDED_SYSID : Extended SysId [chars] for type [chars]
Explanation The extended system id feature has either enabled or disabled for the given type of spanning tree. If enabled, the spanning tree instance identifier is stored in the lower portion of the bridge id priority field and this will cause the allowed values for the bridge priority to be limited to the range of 0 to 61440 in increments of 4096. If disabled, the bridge id priority field consists entirely of the configured priority but some spanning tree features may not be available on a given platform (i.e. 4096 vlan support). On some platforms, this feature may be mandatory.
Recommended Action No action is required.
%SPANTREE-5-ROOTCHANGE : Root Changed for [chars] [dec]: New Root Port is [chars]. New Root Mac Address is [enet]
Explanation The Root has changed for an instance of spanning tree
Recommended Action No action is required.
%SPANTREE-5-TOPOTRAP : Topology Change Trap for [chars] [dec]
Explanation A trap has been generated to indicate the change in topology
Recommended Action No action is required.
%SPANTREE-6-PORTADD_ALL_VLANS : [chars] added to all Vlans
Explanation The interface has been added to all Vlans
Recommended Action No action is required.
%SPANTREE-6-PORTDEL_ALL_VLANS : [chars] deleted from all Vlans
Explanation The interface has been deleted from all Vlans
Recommended Action No action is required.
%SPANTREE-6-PORT_STATE : Port [chars] instance [dec] moving from [chars] to [chars]
Explanation The Spanning-Tree port has changed state.
Recommended Action No action is required.
%SPANTREE-7-BLOCK_PORT_TYPE : Blocking [chars] on [chars]. Inconsistent port type.
Explanation The listed interface is being held in spanning tree blocking state until the port type inconsistency is resolved.
Recommended Action Verify that the configuration and operational state of the listed interface and that of the interface to which it is connected have the same mode (access vs trunk). If mode is trunk, verify the same encapsulation (ISL, 802.1Q). Once these parameters are consistent, spanning tree will automatically unblock the interfaces as appropriate.
%SPANTREE-7-PORTDEL_SUCCESS : [chars] deleted from Vlan [dec]
Explanation The interface has been deleted from Vlan
Recommended Action No action is required.
%SPANTREE-7-RECV_1Q_NON_TRUNK : Received 802.1Q BPDU on non trunk [chars] [chars].
Explanation A SSTP BPDU was received on the listed interface that was not operationally a trunk.
Recommended Action Verify that the configuration and operational state of the listed interface and that of the interface to which it is connected have the same mode (access vs trunk). If mode is trunk, verify the same encapsulation (none, ISL, 802.1Q). Once these parameters are consistent, spanning tree will automatically unblock the interfaces as appropriate.
SPANTREE_VLAN_SHIM
%SPANTREE_VLAN_SHIM-2-MAX_INSTANCE : Platform limit of [dec] STP instances exceeded. No instance created for [chars] (port [chars]).
Explanation The number of currently active VLAN spanning tree instances has reached a platform specific limit. No additional VLAN instances will be created until the number of existing instances drops below the platform limit. The message shows the smallest VLAN number of those VLANs that are unable have STP instances created.
Recommended Action Reduce the number of currently active spanning tree instances by either disabling some of the currently active spanning tree instances or deleting the VLANs associated with currently active spanning tree instances. Note : need to manually enable the spanning- trees that were unable to be created due to limited instances.
%SPANTREE_VLAN_SHIM-3-ADD_REGISTRY_FAILED : Subsystem [chars] fails to add callback function [chars]
Explanation Other subsystem must have mistakenly add its own callback functions. This syslog is for debugging purpose.
Recommended Action No action is required.
SPANTREE_VLAN_SW
%SPANTREE_VLAN_SW-2-MAX_INSTANCE : Platform limit of [dec] STP instances exceeded. No instance created for [chars] (port [chars]).
Explanation The number of currently active VLAN spanning tree instances has reached a platform specific limit. No additional VLAN instances will be created until the number of existing instances drops below the platform limit. The message shows the smallest VLAN number of those VLANs that are unable have STP instances created.
Recommended Action Reduce the number of currently active spanning tree instances by either disabling some of the currently active spanning tree instances or deleting the VLANs associated with currently active spanning tree instances. Note : need to manually enable the spanning- trees that were unable to be created due to limited instances.
SPA_SE1
%SPA_SE1-3-APPL_BOOT_ERR : [chars]: Application boot error detected [chars], with error ([chars], error code = [hex]).
Explanation Service SPA application error was detected during booting of the SPA.
Recommended Action BUTLER_APPBOOT_ERROR_STD_ACTION
%SPA_SE1-3-APPL_BOOT_TIMEOUT : [chars]: Timeout booting application image.
Explanation Initialization of service SPA timed out during booting of the sipspawmak9 sub-package. The system will attempt to reload the SPA to recover from the failure.
Recommended Action BUTLER_APPBOOT_ERROR_STD_ACTION
%SPA_SE1-3-BOOTFLASH_DEBUG_MODE : Service engine [chars] has been booted in bootflash debug mode. This is an engineering use only mode and some or all of the SPA functions could be disabled.
Explanation The SPA was booted with test hw-module subslot bay_num bootflash debug enable configured. Disable this mode and reload the SPA for normal SPA operation.
Recommended Action No action is required.
%SPA_SE1-3-CHECKING_DISK : [chars]: Disk is being checked because of previous unclean shutdown of the SPA or mount count limit reached. Boot time will take longer because of this operation (e.g. 5 to 7 minute for a 250GB disk). Please do not remove the SPA when this operation is being performed.
Explanation Checking of the disk file system is being performed to correct any error due to unclean shutdown of the SPA. Make sure that the SPA is properly shutdown before removing it from the system to prevent file system corruption.
Recommended Action No action is required.
%SPA_SE1-3-CHECK_SPA_CONNECTOR : [chars]: SPI4 error was detected during bootup, automatic reload operation will be attempted for recovering the SPA. Please make sure that the SPA is secured properly in the SIP slot.
Explanation SPI4 error has occurred during SPA bootup. The SPA has been deactivated and reactivated to resolve the problem. If the error occurs more than five times within an hour, no further attempts to reactivate the SPA will be made. This message is likely due to bad connection of the SPA connector with the SIP slot.
Recommended Action Pull out and reinsert the SPA to make secure connection with the SIP slot. Before removing the SPA, make sure to stop the SPA by entering the hw-module subslot slot#/ subslot# stop command. Remove the SPA, wait 5 seconds, and reinsert the SPA into the SIP. If the problem persists, check for physical damage in the connector of both SPA and SIP. If no damage is visible, then copy the error message exactly as it appears and gather the output from the show hw-module subslot bay_num tech-support command from the SIP console, then contact your Cisco technical support representative with the gathered information.
%SPA_SE1-3-DEFAULT_APPL_BOOT_TIMEOUT : [chars]: Timeout booting the default application image, will attempt to boot the helper image.
Explanation Initialization of service SPA timed out during booting of the default application image, the system will attempt to recover from the failure by trying to boot the helper image.
Recommended Action No action is required.
%SPA_SE1-3-DISK_CHECK_ERROR : [chars]: Disk file system check error detected, manual execution of disk checking operation will be required to correct this problem. The SPA will continue operating with reduced disk space.
Explanation An error was detected during automatic checking operation of disk file system integrity. The affected disk partition won't be mounted, and this will prevent the SPA from operating under normal conditions. The ability to store error logging on the disk might not be available and any debugging information could be lost after a SPA reload. Performance of the SPA might also get affected because of the reduced memory storage.
Recommended Action BUTLER_DISK_FS_ERROR_STD_ACTION
%SPA_SE1-3-DISK_CHECKING_TIMEOUT : [chars]: Timeout checking the disk after more than [dec] seconds. Another attempt to check the disk will be done after the SPA reload.
Explanation The disk checking operation has not completed in the expected time frame. To recover from possible disk checking failure, the SPA will be reloaded to allow a retry of the disk checking operation.
Recommended Action BUTLER_DISK_FS_ERROR_STD_ACTION
%SPA_SE1-3-DISK_MOUNT_ERROR : [chars]: Disk mount error detected, manual execution of disk checking operation might be required to correct this problem. The SPA will continue operating with reduced disk space.
Explanation Error were detected during mounting operation of disk partition. The affected disk partition won't be mounted, this will prevent the SPA from operating at normal condition. Capability to store error logging on the disk might not be available and any debugging information could be lost after SPA reload. Performance of the SPA might also get affected because of the reduced memory storage.
Recommended Action BUTLER_DISK_FS_ERROR_STD_ACTION
%SPA_SE1-3-DISK_NOT_PRESENT : [chars]: Cannot detect the presence of disk drive on the SPA. Please check for loose cable connection to the drive. The SPA will continue operating without the disk.
Explanation The disk was not detected by the SPA during bootup, and this will prevent the SPA from operating under normal conditions. The ability to store error logging on the disk will not be available and any debugging information will be lost after a SPA reload. Performance of the SPA might also get affected because of reduced memory storage.
Recommended Action BUTLER_DISK_STATE_ERROR_STD_ACTION
%SPA_SE1-3-DISK_UNFORMATTED : [chars]: The disk drive on the SPA it is not formatted. The SPA cannot use an unformatted disk. Please follow instructions in the Cisco IOS installation and configuration guide to perform the manual format operation. The SPA will continue operating without the disk.
Explanation The disk was not formatted, and this will prevent the SPA from operating under normal conditions. The ability to store error logging on the disk will not be available and any debugging information will be lost after a SPA reload. Performance of the SPA might also get affected because of the reduced memory storage.
Recommended Action Follow the instructions on the Cisco IOS installation and configuration guide to format the disk drive to correct this problem.
%SPA_SE1-3-DISK_UNKNOWN_STATE : [chars]: The disk drive on the SPA is in a unknown operational state. Check for a loose cable connection to the drive. The SPA will continue operating without the disk.
Explanation The disk was in an unknown operational state during SPA bootup, and this will prevent the SPA from operating under normal conditions. The ability to store error logging on the disk will not be available and any debugging information will be lost after a SPA reload. Performance of the SPA might also get affected because of the reduced memory storage.
Recommended Action BUTLER_DISK_STATE_ERROR_STD_ACTION
%SPA_SE1-3-HELPER_BOOT_ERR : [chars]: Helper image boot error detected ([chars], error code = [hex]).
Explanation Service SPA helper image error was detected during booting of the SPA.
Recommended Action No action is required.
%SPA_SE1-3-MAINTENANCE_MODE : Service engine [chars] has been booted in maintenance mode. This is an engineering use only mode and some or all of the SPA functions could be disabled.
Explanation The SPA was booted with test hw-module subslot subslot# maintenance-mode enable configured. Disable this mode and reload the SPA for normal SPA operation
Recommended Action No action is required.
%SPA_SE1-3-MEM_CPU_BIST_ERR : [chars]: CPU BIST failure detected, with error ([chars], error code = [hex]).
Explanation The service SPA CPU Build-In Self Test (BIST) to check memory used by SPA ROMMON has failed. If this test fails, there is probably and issue with the DDR2 memory used by the SPA.
Recommended Action BUTLER_MEM_ERROR_STD_ACTION
%SPA_SE1-3-MEM_INIT_ERR : [chars]: memory init failure occurred [chars], with error ([chars], error code = [hex]).
Explanation The service SPA memory initialization procedure failed.
Recommended Action BUTLER_MEM_ERROR_STD_ACTION
%SPA_SE1-3-ROMMON_BOOT_ERR : [chars]: ROMMON boot error detected [chars] -[chars]
Explanation Service SPA ROMMON error was detected during booting of the SPA. The system will attempt to reload the SPA to recover from the failure.
Recommended Action BUTLER_ROMMON_ERROR_STD_ACTION
%SPA_SE1-3-ROMMON_BOOT_TIMEOUT : [chars]: Timeout booting ROMMON image in [chars] state [chars] -[chars]
Explanation Initialization of service SPA timed out during booting of the ROMMON image, the system will now attempt to reload the SPA to recover from the failure.
Recommended Action BUTLER_ROMMON_ERROR_STD_ACTION
%SPA_SE1-3-ROMMON_IMG_RECOVER : [chars]: ROMMON boot failed, recovering ROMMON image with backup copy.
Explanation A service SPA ROMMON error was detected during booting of the SPA. An attempt to re-program the ROMMON image will be performed to recover from this failure. This problem could have been caused by a previous interruption of the ROMMON FPD upgrade operation.
Recommended Action No action is required.
%SPA_SE1-3-ROMMON_SPI4SYNC_TIMEOUT : [chars]: Timeout getting SPI4 sync from ROMMON
Explanation Initialization of the service SPA timed out after failing to get SPI4 sync. The system will attempt to reload the SPA to recover from the failure.
Recommended Action BUTLER_ROMMON_ERROR_STD_ACTION
%SPA_SE1-3-SKIPPED_DISK_MOUNT : [chars]: Disk mounting operation has been skipped for manual disk repair operation. Please follow the procedures on hardware configuration guide on how to enter into service engine console to continue with the disk repair operation.
Explanation The SPA was configured to not mount the disk after a reload operation. This is the initial step to prepare the SPA for manual disk repair operation.
Recommended Action No action is required.
%SPA_SE1-3-SW_ERR : NULL
Explanation The SPA driver detected a software error condition on the SPA card. This might result in improper operation.
Recommended Action The SPA driver has encountered a software error. Power down and reseat the indicated SPA card. If the problem persists, copy the error message exactly as it appears on the console, and open a case with the Technical Assistance Center via the Internet at TAC_CASE_OPEN , or contact your Cisco technical support representative and provide the representative with the information you have gathered. Be sure to attach to your case the output of the show logging, show monitor event-log spa all and show tech-support commands, your troubleshooting logs, and the specific error message.
%SPA_SE1-3-SYSINIT_FAILURE : [chars]: System init failure was detected during bootup -[chars]. SPA will be disabled because of this failure.
Explanation A failure was detected during system bootup of the SPA. The SPA has been deactivated because of the problem.
Recommended Action Copy the error message exactly as it appears on the console, and gather the output from the show hw-module subslot bay_num tech-support command from the SIP console. Contact your Cisco technical support representative with the gathered information.
%SPA_SE1-5-BOOTING_DEFAULT_APPL : [chars]: booting the default application image.
Explanation The service SPA is booting the default application image from disk.
Recommended Action No action is required.
%SPA_SE1-5-BOOTING_HELPER : [chars]: booting the helper image.
Explanation The service SPA is booting the helper image from bootflash.
Recommended Action No action is required.
%SPA_SE1-5-BOOTING_HOST_IMAGE : [chars]: booting application image downloaded from host.
Explanation The service SPA is booting the default application image from disk.
Recommended Action No action is required.
%SPA_SE1-5-NO_APPL_IN_DISK : [chars]: no application image was found in disk drive.
Explanation The disk driver in service SPA doesn't have a valid application image.
Recommended Action No action is required.
%SPA_SE1-5-NO_VALID_PARTITION : [chars]: no valid partition was found in disk drive ([chars], error code = [hex]).
Explanation The disk driver in service SPA doesn't have valid partition.
Recommended Action Follow the instructions on the Cisco IOS installation and configuration guide to format the disk drive to correct this problem.
SPA_SRVCS_ENGINE
%SPA_SRVCS_ENGINE-0-APP_MSG_EMER : NULL
Explanation The application running on the service SPA has encountered an emergency error.
Recommended Action Refer to the software application documentation for more information. If the problem persists, copy the error message exactly as it appears on the console, and gather the output from the show hw-module subslot bay_num tech-support command from the SIP console, and the output of show tech-support command from service engine Vegas shell console. Contact your Cisco technical support representative with the gathered information.
%SPA_SRVCS_ENGINE-1-APP_MSG_ALERT : NULL
Explanation The application running on the service SPA has issued an alert.
Recommended Action Refer to the software application documentation for more information. If the problem persists, copy the error message exactly as it appears on the console, and gather the output from the show hw-module subslot bay_num tech-support command from the SIP console, and the output of show tech-support command from service engine Vegas shell console. Contact your Cisco technical support representative with the gathered information.
%SPA_SRVCS_ENGINE-2-APP_MSG_CRIT : NULL
Explanation The application running on the service SPA has encountered a critical error.
Recommended Action Refer to the software application documentation for more information. If the problem persists, copy the error message exactly as it appears on the console, and gather the output from the show hw-module subslot bay_num tech-support command from the SIP console, and the output of show tech-support command from service engine Vegas shell console. Contact your Cisco technical support representative with the gathered information.
%SPA_SRVCS_ENGINE-2-CONFIGFAILED : Service Engine [chars] [chars] configuration failed
Explanation The indicated configuration for the service-engine interface has failed.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%SPA_SRVCS_ENGINE-3-APP_MSG_ERR : NULL
Explanation The application running on the service SPA has encountered an error.
Recommended Action Refer to the software application documentation for more information. If the problem persists, copy the error message exactly as it appears on the console, and gather the output from the show hw-module subslot bay_num tech-support command from the SIP console, and the output of show tech-support command from service engine Vegas shell console. Contact your Cisco technical support representative with the gathered information.
%SPA_SRVCS_ENGINE-3-APP_RESET : Application on service engine [chars] has failed and requested a service engine reset.
Explanation The application running on the service SPA failed and as a result the service engine will be restarted in order to recover from the communication failure with host.
Recommended Action No action is required.
%SPA_SRVCS_ENGINE-3-APP_STATUS : Application on service engine [chars] is [chars]
Explanation The Application running on the service SPA has changed state.
Recommended Action No action is required.
%SPA_SRVCS_ENGINE-3-HW_ERR : [chars]: A Hardware device error was detected by [chars], trying to recover the SPA by reload.
Explanation An internal hardware device error has occurred on the services SPA. The error message indicates the SIP slot, the SPA subslot, the SPA type and the name of the hardware device. The SPA has been deactivated and reactivated to resolve the problem. If the error occurs more than five times within an hour, no further attempts to reactivate the SPA will be made. This message is likely due to an unrecoverable hardware failure.
Recommended Action Perform OIR of the SPA located in the specified subslot. Before removing the SPA, enter the hw-module subslot stop command. Remove the SPA, wait 5 seconds, and reinsert the SPA into the SIP. If the problem persists, copy the error message text exactly as it appears on the console or in the system log, enter the show diag command, contact your Cisco technical support representative and provide the representative with the gathered information.
%SPA_SRVCS_ENGINE-3-PASSWORDRESET : Service Engine [chars] password reset [chars][chars]
Explanation The password reset of the service SPA failed or is not supported.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%SPA_SRVCS_ENGINE-3-RBCP_MSG_VER_MISMATCH : Service Engine [chars] is using incorrect RBCP message version (expected version = [dec], current version = [dec]). Please update the software package for the SPA with the correct version. Unexpected behavior might occur if the issue is not addressed.
Explanation The service engine is running with a software version that doesn't use the same RBCP message header version. This could happen if the wrong version of the software package for the SPA was installed in the system.
Recommended Action Find the appropriate software package for the SPA based on the Cisco IOS software version that the system is running. Follow the installation documentation that corresponds to your software version and platform to properly install the software package and correct the problem.
%SPA_SRVCS_ENGINE-3-SE_RESET : Service engine [chars] will be reset to recover from failure ([chars]).
Explanation The service SPA is restarting to recover from the communication failure with host.
Recommended Action No action is required.
%SPA_SRVCS_ENGINE-3-SHUTDOWN_FAILED : Service Engine [chars] shutdown failed to be executed.
Explanation The service engine did not yet respond to the shutdown request. This is probably due to a bug.
Recommended Action No action is required.
%SPA_SRVCS_ENGINE-3-SPA_CPU_ERR : [chars]: SPA CPU HW errors: [chars]
Explanation An internal hardware device error has occurred on the Services SPA CPU. The error message indicates the modular services card slot, the SPA subslot, the SPA type and the name of the hardware device. The SPA has been deactivated and reactivated to resolve the problem. If the error occurs more than five times within an hour, no further attempts to reactivate the SPA will be made. This message is likely due to an unrecoverable hardware failure
Recommended Action If the SPA does not recover automatically, perform OIR of the SPA located in the specified subslot. Before removing the SPA, enter the hw-module subslot stop command. Remove the SPA, wait 5 seconds, and reinsert the SPA into the SIP. If the problem persists, copy the error message text exactly as it appears on the console or in the system log, enter the show tech-support command, contact your Cisco technical support representative and provide the representative with the gathered information.
%SPA_SRVCS_ENGINE-3-SW_ERR : NULL
Explanation The SPA driver detected a software error condition on the SPA card. This might result in improper operation.
Recommended Action The SPA driver has encountered a software error. Please power down and reseat the indicated SPA card. Copy the error message exactly as it appears and open a case with the Technical Assistance Center via the Internet at TAC_CASE_OPEN or contact your Cisco technical support representative and provide the representative with the information you have gathered. Be sure to attach to your case the output of the show logging, show monitor event-log spa all and show tech-support commands, your troubleshooting logs, and the specific error message.
%SPA_SRVCS_ENGINE-4-APP_MSG_WARN : NULL
Explanation The application running on the service SPA has issued a warning message.
Recommended Action Refer to the software application documentation for more information. If the problem persists, copy the error message exactly as it appears on the console, and gather the output from the show hw-module subslot bay_num tech-support command from the SIP console, and the output of show tech-support command from service engine Vegas shell console. Contact your Cisco technical support representative with the gathered information.
%SPA_SRVCS_ENGINE-4-BADPLATFORMINFO : Service Engine [chars] platform information not received correctly.
Explanation The platform and service SPA hardware information was not received correctly.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%SPA_SRVCS_ENGINE-5-APP_MSG_NOTICE : NULL
Explanation The application running on the service SPA has issued a notice.
Recommended Action Refer to the software application documentation for more information.
%SPA_SRVCS_ENGINE-5-NEWPASSWORD : Service Engine [chars] password changed to '[chars]'.
Explanation The password of the service SPA was changed.
Recommended Action No action is required.
%SPA_SRVCS_ENGINE-5-RESTORED_DEF_GW : Service Engine [chars] service-engine ip default-gateway restored.
Explanation The service-engine default gateway IP address was restored after the system verified that the interface IP address was changed. There are certain configuration requirements for the service-engine IP address and the default gateway IP address with the SPA interface IP address. The system has verified that the IP address for the service-engine IP default gateway is still on the same subnet as the service-engine IP address and therefore, the default-gateway configuration is restored.
Recommended Action No action is required.
%SPA_SRVCS_ENGINE-5-RESTORE_EXT_IP : Service Engine [chars] service-engine ext ip address restored.
Explanation The service-engine external IP address was restored after the system verified that the interface IP address changed. There are certain configuration requirements for the service-engine IP address and the default gateway IP address with the SPA interface IP address. The system has verified these requirements and restored the external IP address.
Recommended Action No action is required.
%SPA_SRVCS_ENGINE-5-RESTORE_IP : Service Engine [chars] service-engine ip address restored.
Explanation The service-engine IP address was restored after the system verified that the interface IP address changed. There are certain configuration requirements for the service-engine IP address and the default gateway IP address with the SPA interface IP address. The system has verified these requirements and restored the IP address.
Recommended Action No action is required.
%SPA_SRVCS_ENGINE-5-SHUTDOWN_BUTTON : Service engine [chars] shutdown button was pressed, shutdown initiated.
Explanation The Shutdown button on the SPA was pressed and shutdown initiated.
Recommended Action No action is required.
%SPA_SRVCS_ENGINE-5-SHUTDOWN_DONE : Service engine [chars] shutdown complete
Explanation The shutdown of the service engine was completed.
Recommended Action No action is required.
%SPA_SRVCS_ENGINE-5-SHUTDOWN_NOT_DONE : Service Engine [chars] shutdown was not done in a proper fashion: Reseating the SPA may corrupt the hard disk.
Explanation The SPA was not properly shutdown before removal of the SPA. This could result in the corruption of the hard disk on the SPA.
Recommended Action No action is required.
%SPA_SRVCS_ENGINE-5-UNCONFIGURE_DEF_GW : Service Engine [chars] service-engine ip default-gateway unconfigured.
Explanation The service-engine default gateway IP is unconfigured as interface IP address changed.
Recommended Action No action is required.
%SPA_SRVCS_ENGINE-5-UNCONFIGURE_EXT_IP : Service Engine [chars] service-engine ext ip address unconfigured.
Explanation The service-engine external IP address is unconfigured as interface IP address changed.
Recommended Action No action is required.
%SPA_SRVCS_ENGINE-5-UNCONFIGURE_IP : Service Engine [chars] service-engine ip address unconfigured.
Explanation The service-engine IP address is unconfigured as interface IP address changed.
Recommended Action No action is required.
%SPA_SRVCS_ENGINE-6-APP_MSG_INFO : NULL
Explanation The application running on the service SPA has issued a informational message.
Recommended Action Refer to the software application documentation for more information.
%SPA_SRVCS_ENGINE-7-APP_MSG_DEBUG : NULL
Explanation The application running on the service SPA has displayed a debug message.
Recommended Action Refer to the software application documentation for more information.
SPA_SRVCS_IF
%SPA_SRVCS_IF-3-SRVCS_IF_SW_ERR : NULL
Explanation The SPA driver detected a software error condition on the SPA card. This might result in improper operation.
Recommended Action The SPA driver has encountered a software error. Power down and reseat the indicated SPA card. If the problem persists, copy the error message exactly as it appears in the console and open a case with the Technical Assistance Center via the Internet at TAC_CASE_OPEN , or contact your Cisco technical support representative and provide the representative with the information you have gathered. Be sure to attach to your case the output of the show logging, show monitor event-log spa all and show tech-support commands, your troubleshooting logs, and the specific error message.
SPA_T3E3
%SPA_T3E3-3-LOVEFAIL : [chars]: failed to send [chars] love letter
Explanation A love letter (status or configuration message) could not be sent.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%SPA_T3E3-3-MSGERR : Illegal message type [dec] received for Interface [chars]
Explanation An unknown message was received by RP.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%SPA_T3E3-3-NO_SSB : [chars]: Failed to get serial subblock.
Explanation Serial subblock pointer is NULL. Internal software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%SPA_T3E3-3-SSBINIT : [chars]: Fail to initialize serial IDB
Explanation Most common reason is lack of system memory. Earlier messages might indicate memory allocation failures.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%SPA_T3E3-3-SUBRATE_FPGA_LOAD_FAILED2 : [chars] Programming [chars] subrate FPGA failed. The FPGA image is corrupted. FPD upgrade has been attempted. SPA is shut.
Explanation The indicated subrate FPGA image is corrupted even after FPD upgrade. The SPA is disabled until this problem is corrected.
Recommended Action Verify the correctness of the FPD Image Package. Note that the FPD Image Package used in the upgrade should match the running Cisco IOS release. This can be verified by the use of show upgrade fpd package default command.
%SPA_T3E3-4-SUBRATE_FPGA_LOAD_FAILED : [chars] Programming [chars] subrate FPGA failed. The FPGA image is corrupted. One upgrade attempt is made.
Explanation The indicated subrate FPGA image is corrupted and programming of FPGA failed. One upgrade attempt will be made to recover from the failure.
Recommended Action Automatically upgrade the subrate FPGA image uses default FPD Image Package. The package should match the running Cisco IOS release. This can be verified by the use of show upgrade fpd package default command. If subrate FPGA failure persists after upgrade, SPA is disabled. Ensure the package file is intact.
%SPA_T3E3-5-BERT : Interface [chars], BERT [chars]
Explanation The spa t3e3 driver processed a BERT task.
Recommended Action None, this is just a notification upon completion of a BERT task.
%SPA_T3E3-5-DEF_SUBRATE : [chars] [chars]
Explanation Remote subrate configuration changed
Recommended Action Inform the network operator that subrate configuration changed by remote end
%SPA_T3E3-5-MSG_ENQUEUE_ERR : [chars]: Unable to enqueue message to T3E3 SPA process
Explanation The T3E3 SPA process message queue is full.
Recommended Action Copy the error message exactly as it appears, collect the output of 'show tech-support' command immediately, and report it to your technical support representative.
%SPA_T3E3-5-MSG_QUEUE_ERR : [chars]: T3E3 process message queue not initialized.
Explanation The T3E3 process message queue is not ready.
Recommended Action Copy the error message exactly as it appears, collect the output of 'show tech-support' command immediately, and report it to your technical support representative.
%SPA_T3E3-5-MSG_UNEXPECTED_ERR : [chars]: Unexpected SPA message [dec].
Explanation SPA has been removed, but still there are outstanding events.
Recommended Action If the CPU utilization is high, try to reduce the CPU utilization
SRP
%SRP-1-WRAPPING_PROCESS_LOCKED : [chars] The wrap/unwrap state-change process is locked
Explanation A wrap/unwrap state change process has not come to an end on time.
Recommended Action If message is periodic, issue a shut and no shut on the interface.
%SRP-3-DUP_MAC_ADDR : [chars] : Duplicate mac addresses in topology
Explanation The topology contains 1 or more duplicate mac addresses
Recommended Action Identify duplicate address and correct configuration.
%SRP-3-FALSE_VAL_ALARM : [chars] -error in [chars]
Explanation FALSE value returned. Some features/commands may not work properly
Recommended Action Please Contact Cisco Systems TAC support
%SRP-3-NULL_P_ALARM : Dereferencing NULL pointer [chars] in [chars]
Explanation NULL pointer error condition exists. Some features/commands may not work properly
Recommended Action Please Contact Cisco Systems TAC support
%SRP-3-RING_ID_ERROR : [chars] : Rx side [chars], Tx side of fiber originates on side [chars]
Explanation The fiber on the specified side is remotely connected to the wrong side
Recommended Action Verify that each side A is connected to side B and each side B is connected to side A.
%SRP-3-SINGLE_NODE_TOPO : [chars] : Single node in topology
Explanation The topology discovery resulted in a single node being found
Recommended Action This can be due to duplicated mac addresses. Identify mac address of interface and ensure it is not duplicated on other nodes. If the node is in loopback, disregard this message.
%SRP-4-ALARM : [chars] Side %c [chars]
Explanation A physical line error condition exists on the indicated network
Recommended Action Diagnose and repair the physical error
%SRP-4-RAC_ALARM : [chars] Side %c [chars]
Explanation A physical error condition detected at the indicated RAC
Recommended Action Diagnose and repair the physical error
%SRP-4-SRR_STATE_CHANGE : [chars] SRR usage changed ([chars])
Explanation SRR ring usage is changed using Inner, Outer or Both rings.
Recommended Action Diagnose the cause of the ring usage change.
%SRP-4-SRR_VER_MISSMATCH : [chars] SRR version missmatch detected.
Explanation Different SRR version received from other nodes.
Recommended Action Update the IOS image on all nodes of the ring to the same SRR version
%SRP-4-WRAP_STATE_CHANGE : [chars] [chars] on side %c ([chars])
Explanation The specified side of the interface is wrapped or unwrapped.
Recommended Action Diagnose the cause of the wrap.
SRPMIB
%SRPMIB-3-FALSE_VAL_ALARM : [chars] -error in [chars]
Explanation FALSE value returned. Some features/commands may not work properly
Recommended Action Please Contact Cisco Systems TAC support
%SRPMIB-3-NULL_P_ALARM : Dereferencing NULL pointer [chars] in [chars]
Explanation NULL pointer error condition exists. Some feature/command may not work properly
Recommended Action Please Contact Cisco Systems TAC support
SRW
%SRW-7-BAD_SRW_DATA : Bad SRW data ([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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%SRW-7-BAD_SRW_MAGIC : Bad SRW magic [hex] @ [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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%SRW-7-SRW_ERROR2 : [chars]: [hex] [hex] [dec] [dec] [dec] [dec] [hex] [hex] [hex] [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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%SRW-7-SRW_ERROR3 : [chars]: [hex] [hex] [dec] [dec] [dec] [dec] [hex] [hex] [hex] [dec] [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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%SRW-7-SRW_ERROR : [chars]: [hex] [hex] [dec] [dec] [dec] [dec] [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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
SSL
%SSL-3-SSL_REC_HDR_BUF_OVERFLOW : QFP SSL record header buffer overflow
Explanation Cisco internal software error. QFP SSL record processing detected header buffer overflow condition. The SSL connection 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SSL-3-SSL_STUB : QFP SSL ([chars]) feature executes stub entry in [chars] direction
Explanation Cisco internal software error. QFP SSL feature stub entry got executed. The packet will be dropped.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
SSLMGR
%SSLMGR-0-ASYMMETRIC_KEY_FAIL : Asymmetric key failure: [chars].
Explanation Asymmetric key failure.
Recommended Action No action required - forwarding processor (ESP) rebooted automatically.
%SSLMGR-0-N2_VSERVER_FAIL : Virtual server context failure: [chars].
Explanation Cryptographic coprocessor critical operation failed. Further data processing on ESP is halted
Recommended Action forwarding processor (ESP) is rebooted automatically. no action needed
%SSLMGR-0-SYMMETRIC_KEY_FAIL : Symmetric key failure: [chars].
Explanation Symmetric key failure.
Recommended Action No action required - forwarding processor (ESP) rebooted automatically.
%SSLMGR-3-N2_CONTEXT_FAIL : Context failure: [chars].
Explanation Coprocessor context operation failed due to resource limit
Recommended Action Monitoring required
SSLVPN
%SSLVPN-1-LICENSE_EXPIRED : IOS SSLVPN evaluation license has expired
Explanation IOS SSLVPN evaluation license has expired and a new license needs to be obtained. Existing user sessions will continue till they are closed and no new sessions will be allowed.
Recommended Action Please visit http://www.cisco.com/go/sslvpn for instructions on how to obtain a IOS SSLVPN license
%SSLVPN-3-CERT_GEN_FAILED : Generation of self-signed certificate failed for Gateway [chars]
Explanation This message indicates that generation of self-signed certificate failed
Recommended Action Check the server configuration and reconfigure it
%SSLVPN-3-LICENSE_NO_LICENSE : No valid license is available to use IOS SSLVPN service
Explanation IOS SSLVPN service is a licensed feature on this platform. It will not be functional until a valid license is installed.
Recommended Action Please visit http://www.cisco.com/go/sslvpn for instructions on how to obtain a IOS SSLVPN license
%SSLVPN-4-LICENSE_COUNT_EXCEEDS_MAX_LIMIT : License count of currently installed license exceeds the maximum supported sessions on this platform
Explanation License count of currently installed license exceeds the maximum supported sessions on this platform. Excess count will not be utilized.
Recommended Action Please collect the output of show license detail command and contact your technical support representative.
%SSLVPN-5-HTTP_REQUEST_NOT_AUTHORIZED : vw_ctx: [chars] vw_gw: [chars] remote_ip: [IP_address] status: HTTP request without login cookie resource: [chars]
Explanation This message indicates that HTTP request doesn't have valid login cookie and is not authorized to access the resource
Recommended Action No action is required.
%SSLVPN-5-LOGIN_AUTH_FAILED : vw_ctx: [chars] vw_gw: [chars] remote_ip: [IP_address] user_name: [chars], Failed to contact authentication server
Explanation This message is seen when the authentication server is unavailable because it is down or unreachable
Recommended Action Verify if routes are configured correctly to reach authentication and the server is configured correctly
%SSLVPN-5-LOGIN_AUTH_PASSED : vw_ctx: [chars] vw_gw: [chars] remote_ip: [IP_address] user_name: [chars], Authentication successful, user logged in
Explanation This message indicates that login authentication succeeded for user
Recommended Action No action is required.
%SSLVPN-5-LOGIN_AUTH_REJECTED : vw_ctx: [chars] vw_gw: [chars] remote_ip: [IP_address] user_name: [chars], Failed to authenticate user credentials
Explanation This message indicates that authentication server failed to validate credentials provided by the user to login under webvpn context
Recommended Action Check username and password configured on authentication server
%SSLVPN-5-SESSION_TERMINATE : vw_ctx: [chars] vw_gw: [chars] remote_ip: [IP_address] user_name: [chars] reason: [chars]
Explanation This message indicates that user session is terminated due to reason indicated
Recommended Action No action is required.
%SSLVPN-5-SSL_TLS_CONNECT_OK : vw_ctx: [chars] vw_gw: [chars] i_vrf: [dec] f_vrf: [dec] status: SSL/TLS connection successful with remote at [IP_address]:[dec]
Explanation This message indicates that SSL/TLS handshake with peer was successful
Recommended Action No action is required.
%SSLVPN-5-SSL_TLS_ERROR : vw_ctx: [chars] vw_gw: [chars] i_vrf: [dec] f_vrf: [dec] status: SSL/TLS connection error with remote at [IP_address]:[dec]
Explanation This message indicates that SSL/TLS connection has encountered error this normally means that either handshake failed or protocol error occured during life-time of the connection
Recommended Action Check certificate and trustpoint configuration in global config mode as well as under webvpn gateway
%SSLVPN-5-SSLVPNMGR_ERROR : [chars] [chars]
Explanation SSLVPN Manager error.
Recommended Action No action is required.
%SSLVPN-5-UPDOWN : sslvpn [chars] : [chars] changed state to [chars]
Explanation sslvpn service state changed.
Recommended Action No action is required.
%SSLVPN-6-CONTEXT_MAX_USERS_LOGIN_DENIED : Login denied for user [chars] ; Max users exceeded for profile [chars]
Explanation This message indicates that the user was denied to login because the the max users for the profile has been exceeded
Recommended Action Check the gateway configuration and reconfigure the maximum allowed users in the profile
%SSLVPN-6-CONTEXT_OUT_OF_SERVICE : Failed to apply configuration on vaccess ; Context [chars] is made out of service ; [chars]
Explanation This message indicates that applying configuration on vaccess failed. This is caused if the configuration is not valid while doing inservice.
Recommended Action Check the configuration before doing inservice of the context.
%SSLVPN-6-GLOBAL_MAX_USERS_LOGIN_DENIED : Login denied for user [chars] ; Global max users limit reached
Explanation This message indicates that the user was denied to login because the the max users limit reached
Recommended Action To support more users, more sslvpn gateways need to be installed
%SSLVPN-6-HTTPAUTH_NTLM_NEGO_ERROR : NTLM Negotiation error while doing HTTP authentication for url [chars]://[chars][chars] being accessed by user [chars] in context [chars]
Explanation This message indicates that a NTLM negotiation error occurred while doing the HTTP authentciaton with the the server for the url
Recommended Action Check the server configuration and reconfigure it
%SSLVPN-6-HTTP_KEEPALIVE_DISABLED : HTTP Keepalive is disabled on the server for url [chars]://[chars][chars] being accessed by user [chars] in context [chars]
Explanation This message indicates that the HTTP Keepalive is disabled on the server for the url.
Recommended Action Check the server configuration and reconfigure it
%SSLVPN-6-INVALID_RADIUS_CONFIGURATION : Radius configured [chars] [chars] does not exist
Explanation This message indicates that the name configured on the Radius server, does not match any of the configured names on the gateway *//* "This message indicates that the HTTP Authentication method configured " *//* "on the server for the url, is not supported by the gateway"); *//* msgdef_recommended_action( *//* "Check the server configuration and reconfigure it"); */
Recommended Action Check the gateway configuration and reconfigure the radius server *//* "Check the server configuration and reconfigure it"); */
%SSLVPN-6-LICENSE_NO_FREE_COUNT : All avaiable SSLVPN session licenses are in use
Explanation All SSLVPN sessions avaialable per current license are in use. Hence, no additional user sessions can be allowed.
Recommended Action To support more users, additional license needs to be purchased. Please visit http://www.cisco.com/go/sslvpn for instructions on how to obtain a IOS SSLVPN license
%SSLVPN-6-OVERSIZE_NTLM_TYPE3_CREDENTIALS : NTLM Type3 credentials size is larger than supported for url [chars]://[chars][chars] being accessed by user [chars] in context [chars]
Explanation This message indicates that the NTLM Type3 credentials size for the url, is larger than what is supported on the gateway
Recommended Action Check the server configuration and reconfigure it
%SSLVPN-6-RADIUS_ATTRIBUTE_TOO_LONG : Attribute length [dec] is longer than buffer size [dec]
Explanation This message indicates that the attribute configured on the Radius server is longer than the allocated buffer size and will be ignored.
Recommended Action Reconfigure the radius attribute with the appropriate length
%SSLVPN-6-UNSUPPORTED_BASIC_HTTP_METHOD : Unsupported Basic HTTP method configured for url [chars]://[chars][chars] being accessed by user [chars] in context [chars]
Explanation This message indicates that the Basic HTTP method configured on the server for the url, is not supported by the gateway
Recommended Action Check the server configuration and reconfigure it
%SSLVPN-6-UNSUPPORTED_HTTPAUTH_METHOD : Unsupported HTTP Authentication method configured for url [chars]://[chars][chars] being accessed by user [chars] in context [chars]
Explanation msgdef (UNSUPPORTED_HTTPAUTH_METHOD, SSLVPN, LOG_INFO, 0 , Unsupported HTTP Authentication method configured for url %s://%s%s being accessed by user %s in context %s This message indicates that the HTTP Authentication method configured on the server for the url, is not supported by the gateway
Recommended Action msgdef (UNSUPPORTED_HTTPAUTH_METHOD, SSLVPN, LOG_INFO, 0 , Unsupported HTTP Authentication method configured for url %s://%s%s being accessed by user %s in context %s Check the server configuration and reconfigure it
%SSLVPN-6-WEBVPN_APP_ACL_NET : The request( source ip: [IP_address], destion ip : [IP_address] ) from user [chars] is [chars] by ACL
Explanation A request is matched with network ACL.
Recommended Action No action is required.
%SSLVPN-6-WEBVPN_APP_ACL_URL : The request( scheme: [chars], host : [chars], port : [dec], path : [chars] ) from user [chars] is [chars] by ACL
Explanation A request is matched with application ACL.
Recommended Action No action is required.
%SSLVPN-6-WEBVPN_SSO_AUTH_REJECT : Single Sign On session establishment failed for user: [chars] in context [chars]
Explanation This message indicates that a Single Sign On session failed for the user
Recommended Action The information is used to track Single Sign On events. No action is required.
%SSLVPN-6-WEBVPN_SSO_AUTH_SUCCESS : Single Sign On session successfully established for user: [chars] in context [chars]
Explanation This message indicates that a Single Sign On session was established for the user
Recommended Action The information is used to track Single Sign On events. No action is required.
%SSLVPN-6-WEBVPN_SSO_SESSION_FAIL : Single Sign On session creation failed for user: [chars] in context [chars]
Explanation This message indicates that a Single Sign On session creation failed for the user. Session creation can fail for various reasons such as DNS lookup failure, timeouts and retry attempts exceeded
Recommended Action The information is used to track Single Sign On events. No action is required.
%SSLVPN-6-WEBVPN_TUNNEL_USER_LOGOUT : User: [chars] has logged out from gateway [chars] context [chars]
Explanation A Tunneling user has logged out from the given gateway/context
Recommended Action The information is used to track user logout events. No action is required.
SSLVPNMGR
%SSLVPNMGR-5-LOGIN_AUTH_FAILED : Failed to contact authentication server. [chars]
Explanation Authentication server is unavailable because it is down or unreachable
Recommended Action Verify if routes are configured correctly to reach authentication and the server is configured correctly
%SSLVPNMGR-5-LOGIN_AUTH_REJECTED : Failed to authenticate user credentials. [chars]
Explanation Authentication server failed to validate credentials provided by the user to login under webvpn context
Recommended Action Check username and password configured on authentication server
%SSLVPNMGR-6-CONTEXT_MAX_USERS_LOGIN_DENIED : Authentication successful, user logged in. [chars]Session terminated. [chars]HTTP request without login cookie. [chars]Login denied for user [chars]. Max users exceeded for context [chars]
Explanation This message indicates that login authentication succeeded for user SSLVPN session was terminated This message indicates that HTTP request doesn't have valid login cookie and is not authorized to access the resource This message indicates that user was denied to login because the the max users for the context has been exceeded
Recommended Action Check the gateway configuration and reconfigure the maximum allowed users in the context
SSLVPN_PROXY
%SSLVPN_PROXY-2-PROXY_IPC_INIT_FAILED : QFP SSLVPN Proxy IPC interface initialization failure (result: [dec]).
Explanation Cisco internal software error. QFP SSLVPN Proxy initialization detected that the IPC interface initialization failed. QFP SSLVPN 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SSLVPN_PROXY-3-PROXY_BAD_MSG : QFP SSLVPN Proxy received bad length message type [dec]
Explanation Cisco internal software error. QFP SSLVPN 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SSLVPN_PROXY-3-PROXY_CRYPTO_CTX_MEM_REQ_FAIL : QFP SSLVPN Proxy failed to repleneish crypto context memory., MSGDEF_LIMIT_SLOW
Explanation Cisco internal software error. QFP SSLVPN Proxy message processing detected leaking of crypto context memory condition. QFP SSLVPN will not be functional properly while this condition exist.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SSLVPN_PROXY-3-PROXY_INV_MSG : QFP SSLVPN Proxy received invalid message type [dec]
Explanation Cisco internal software error. QFP SSLVPN 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SSLVPN_PROXY-3-PROXY_IPC_ALLOC_FAILED : QFP SSLVPN Proxy [chars] message lost due to message buffer allocation failure.
Explanation Cisco internal software error. QFP SSLVPN 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SSLVPN_PROXY-3-PROXY_IPC_SEND_FAILED : QFP SSLVPN Proxy [chars] message lost due to message sent failure (result: [dec]).
Explanation Cisco internal software error. QFP SSLVPN 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SSLVPN_PROXY-3-PROXY_SSL_CTX_MEM_REQ_FAIL : QFP SSLVPN Proxy failed to repleneish SSL context memory., MSGDEF_LIMIT_SLOW
Explanation Cisco internal software error. QFP SSLVPN Proxy message processing detected leaking of SSL context memory condition. QFP SSLVPN will not be functional properly while this condition exist.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SSLVPN_PROXY-4-PROXY_CRYPTO_CTX_REQ_FAIL : QFP SSLVPN Proxy failed to replenish hardware context handles., MSGDEF_LIMIT_SLOW
Explanation Cisco internal software error. QFP SSLVPN Proxy message processing detected out-of-resource condition and cannot replenish hardware context handles. QFP SSLVPN will not be functional properly while this conidtion exist.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
SSSMGR
%SSSMGR-3-DYNAMIC_UPDATE_NOT_SUPPORTED : [[dec]] Dynamic session updates not allowed on this [chars] session. It is an unsupported configuration.
Explanation Updates on these sessions not supported. This is an unsupported configuration.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SSSMGR-3-ERROR_RESOURCE_OVERFLOW : Resource overflow
Explanation A fixed size system resource has been exceeded.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SSSMGR-3-INFO_TYPE_NO_COPY_VECTOR : info type has no copy vector ([dec]).
Explanation An internal SSS Manager error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SSSMGR-3-INIT : Initialisation failure, [chars]
Explanation An internal SSS Manager error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SSSMGR-3-INVALID_FSM_STATE : Encountered an invalid SSS Mgr state [dec] in [chars]
Explanation An internal SSS Manager error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SSSMGR-3-INVALID_INFO_TYPE : Received an INVALID info type value ([dec]).
Explanation An internal SSS Manager error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SSSMGR-3-INVALID_SERVICE_TYPE : Received an INVALID service type ([dec])[chars].
Explanation An internal SSS Manager error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SSSMGR-3-MEMORY_LOW : Memory low ([dec] times), disconnecting session
Explanation Required memory is running low.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SSSMGR-3-NULL_FSM_CONTEXT : Encountered a NULL SSS Mgr context in [chars]
Explanation Encountered a NULL context in SSS Manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SSSMGR-3-NULL_INFO_STRING : Received a NULL info string value.
Explanation An internal SSS Manager error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SSSMGR-3-RESOURCE_OVERFLOW : Resource overflow
Explanation A fixed size system resource has been exceeded.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SSSMGR-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SSSMGR-3-UNEXPECTED_MSG : Encountered an unexpected message: [chars]
Explanation Encountered an unexpected message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SSSMGR-3-UNEXPECTED_SIP_INFO : Encountered an unexpected SIP info: [chars]
Explanation Encountered an unexpected SIP info.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SSSMGR-3-UNSUPPORTED_CFG : Unsupported configuration detected: [uid: [int]] [chars]
Explanation Unsupported configuration detected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SSSMGR-4-WARN_RESOURCE_ABOVE_WM : Resource above watermark
Explanation A fixed size system resource is above watermark.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SSSMGR-5-BB_LICENSE_PROCUREMENT_FAILURE : Failed to procure [int] BroadBand licenses
Explanation None
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SSSMGR-5-BB_LICENSE_PROCUREMENT_SUCCESS : Successfully procured [int] BroadBand licenses
Explanation None
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SSSMGR-5-BB_LICENSE_RELEASE_FAILURE : Failed to release all BroadBand licenses
Explanation None
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SSSMGR-5-BB_LICENSE_RELEASE_SUCCESS : Successfully released all BroadBand licenses
Explanation None
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SSSMGR-5-BB_LICENSE_REQUEST_SENT : Broadband license request sent for [int] license with configured license count [int]
Explanation None
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SSSMGR-5-IFCFG_NOTALLWED_IN_SVC : Interface-config not allowed at service config level, ignoring
Explanation Interface-config attribute is not allowed while in a service profile. It is only supported in user profiles.
Recommended Action Remove interface-config attribute from the service profile and reconfigure using a user profile.
%SSSMGR-5-UNSUPPORTED_CFG_NOTICE : Unsupported configuration detected, [chars]
Explanation The value of the specified configuration parameter was out of range. This is not considered an error as the value was adjusted to be within the supported range. Update the configuration source to a value within the supported range to avoid this message.
Recommended Action No action is required.
STILE_CLIENT
%STILE_CLIENT-4-MAX_LINK_TOUCH_CLEAR : NBAR number of [chars] has declined below its threshold, links are available for [chars].
Explanation After NBAR was in links shortage, the number of links has declined below its threshold. New traffic flows will be classified properly
Recommended Action No action is required.
%STILE_CLIENT-4-MAX_LINK_TOUCH_WARN : NBAR number of [chars] threshold is reached, can't allocate more memory for [chars].
Explanation Because of non-availability of flow links new traffic flows may not be classified properly
Recommended Action No action is required.
%STILE_CLIENT-4-NBAR_ACTIVATION_FAILED : NBAR activation process has failed with errcode [dec].
Explanation Activation of NBAR has failed. the cause is provided through the error code from cerrno.h
Recommended Action No action is required.
%STILE_CLIENT-4-NBAR_GENERAL_FAILED : An error occured, with errcode [dec].
Explanation An error occured, will not handle the messages, wait for deactivate the cause is provided through the error code from cerrno.h
Recommended Action No action is required.
%STILE_CLIENT-4-NBAR_MEMORY_BOUNDARY_TOUCH_CLEAR : NBAR memory utilization has declined below its threshold, memory is available for [chars].
Explanation After NBAR was in memory shortage, memory utilization has declined below its threshold New traffic flows will be classified properly
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%STILE_CLIENT-4-NBAR_MEMORY_BOUNDARY_TOUCH_WARN : NBAR reached maximum configured memory utilization. Can't allocate more memory for [chars].
Explanation Because of NBAR memory shortage new flows may not be classified properly
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%STILE_CLIENT-4-NBAR_NOT_ENOUGH_STATIC_MEMORY : NBAR does not have enough memory to be activated.
Explanation System does not have enough free memory to allow activation of NBAR
Recommended Action No action is required.
%STILE_CLIENT-4-SYS_FREE_MEMORY_LOW_WATERMARK_TOUCH_CLEAR : System free memory has increased above its lower watermark, memory is available for [chars].
Explanation After system memory was in shortage, free memory has increased above its lower watermark New traffic flows will be classified properly
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%STILE_CLIENT-4-SYS_FREE_MEMORY_LOW_WATERMARK_TOUCH_WARN : System free memory has reached its lower watermark. Can't allocate more memory for [chars].
Explanation Because of system memory shortage new flows may not be classified properly
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
STILE_PROXY
%STILE_PROXY-3-IPC_NORES : No space for the IPC reply, size [int]
Explanation For a request from upper STILE 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 binding 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_ACTION
%STILE_PROXY-3-IPC_OPEN_REPLY : IPC Open Reply failed, request [int]
Explanation For a request from upper STILE software stack layers it was not possible to open the reply buffer. The consequence of this could be a stuck binding 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_ACTION
%STILE_PROXY-3-IPC_UNHANDLED : type [dec]
Explanation An unknown message was received by the STILE Client Proxy.
Recommended Action LOG_STD_ACTION
%STILE_PROXY-3-PROXY_IPC_SEND_FAILED : IPC send msg for [chars] [dec] failed
Explanation IPC failed to reply
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%STILE_PROXY-3-PROXY_SLINK_MEM_EXTEND_FAILED :
Explanation Increasing of stile slink pool failed.
Recommended Action LOG_STD_ACTION
%STILE_PROXY-3-SLINK_MEM_REQ_FAILED :
Explanation IPC Failure occurred when attempting to request more stile link memory.
Recommended Action LOG_STD_ACTION
STP_ISSU
%STP_ISSU-2-GET_BUFFER : STP ISSU client failed to get buffer for message. Error: [dec] ([chars])
Explanation STP 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)
%STP_ISSU-2-INIT : STP ISSU client initialization failed to [chars]. Error: [dec] ([chars])
Explanation The STP 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%STP_ISSU-2-SEND_NEGO_FAILED : STP ISSU client failed to send negotiation message. Error: [dec] ([chars])
Explanation The STP 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)
%STP_ISSU-2-SESSION_ARBITRATE : STP ISSU client failed to register arbitrate callback. Error: [dec] ([chars])
Explanation The STP ISSU client failed to register arbitrate callback. If a problem occurs with the callback 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>)
%STP_ISSU-2-SESSION_NEGO : STP ISSU client encountered unexpected client nego_done. Error: [dec] ([chars])
Explanation An ISSU-compliant client transitions through a series of internal states. The STP 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>)
%STP_ISSU-2-SESSION_REGISTRY : STP ISSU client failed to register session information. Error: [dec] ([chars])
Explanation The STP 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>)
%STP_ISSU-3-INVALID_CAPABILITY : STP ISSU client: invalid capability list
Explanation STP ISSU client observed an error during capability negotiaiton. When this error happens there is a mismatch in the client capability between the active and standby unit.
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>)
%STP_ISSU-3-INVALID_SESSION : STP ISSU client does not have a valid registered session.
Explanation STP 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>)
%STP_ISSU-3-MSG_NOT_OK : STP ISSU client 'Message Type [dec]' is not compatible
Explanation The STP 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>)
%STP_ISSU-3-MSG_SIZE : STP ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] ([chars])
Explanation The STP ISSU client failed to calculate the MTU for the specified message. The STP 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>)
%STP_ISSU-3-POLICY_NOT_SUPPORTED : STP ISSU client does not support Message Type [dec]
Explanation STP ISSU client received an message type which it does not support. The policy is applied to make the session incompatible.
Recommended Action LOG_STD_SH_CMD_ACTION(show issu session <client_id>)
%STP_ISSU-3-REJECTED_CAPABILITY : STP ISSU client rejected capability '[chars]'
Explanation STP ISSU client rejected a capability during negotiaiton. When this error happens there is a mismatch in the client capability between the active and standby unit.
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>)
%STP_ISSU-3-REJECTING_CAPABILITY : STP ISSU client rejecting capability '[chars]'
Explanation STP ISSU client is rejecting a capability during negotiaiton. When this error happens there is a mismatch in the client capability between the active and standby unit.
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>)
%STP_ISSU-3-SESSION_UNREGISTRY : STP ISSU client failed to unregister session information. Error: [dec] ([chars])
Explanation The STP 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>)
%STP_ISSU-3-TRANSFORM_FAIL : STP ISSU client [chars] transform failed for 'Message Type [dec]'. Error: [dec] ([chars])
Explanation The STP 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 STP 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>)
STUN
%STUN-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 STUN group. If memory shortages persist, call your Cisco technical support representative for assistance.
%STUN-2-NOMEMORY : No memory available: [chars]
Explanation The requested operation failed 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.
%STUN-2-NOTGI : Please remove and redefine protocol group [dec]
Explanation An internal error occurred. The configuration is irregular.
Recommended Action Remove and reconfigure the STUN protocol group. Record the configuration and call your Cisco technical support representative for assistance.
%STUN-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%STUN-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%STUN-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%STUN-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%STUN-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%STUN-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%STUN-3-NOINPIDB : Input idb not set
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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%STUN-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%STUN-3-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%STUN-4-DUPROUTE : Cannot define duplicate route on the same group
Explanation This route command is defined on another interface belonging to the same group. Cannot define duplicate route on the same group
Recommended Action Consider defining a new group and moving this interface onto that group
%STUN-4-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%STUN-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%STUN-6-CONNOPENFAIL : CONN: peer [chars] open failed, [chars] [[int]]
Explanation An attempt to connect to a remote TCP STUN peer failed.
Recommended Action Verify that the remote peer is accessible from this router, that it is running software capable of supporting STUN, and that it is configured correctly.
%STUN-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.
%STUN-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.
%STUN-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.
%STUN-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 STUN reconfiguration or disabling. This is good, expected behavior.
Recommended Action No action is required.
%STUN-6-RECONNECT : PHDR: reconnect from peer [chars]
Explanation A remote peer reestablished a connection to this router.
Recommended Action No action is required.
%STUN-6-TCPFINI : peer [chars] closed [previous state [chars]]
Explanation A remote peer closed a STUN 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.)
%STUN-6-TCPPEERSHUT : [chars] [chars], [IP_address]([dec])
Explanation This route closed a STUN 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.)
SUBSYS
%SUBSYS-2-BADCLASS : Bad subsystem class ([dec]) -ignoring subsystem
Explanation A software consistency check failed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%SUBSYS-2-BADSEQUENCE : Subsystem ([chars]) has cross-class sequence for ([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.
%SUBSYS-2-BADVERSION : Bad subsystem version number ([dec]) -ignoring subsystem
Explanation A software consistency check failed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%SUBSYS-2-MISMATCH : Kernel and subsystem version differ ([dec].[dec]) -ignoring subsystem
Explanation A software consistency check failed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%SUBSYS-2-NOTFOUND : Subsystem ([chars]) needs subsystem ([chars]) to start
Explanation A software consistency check failed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%SUBSYS-2-RECURSION : Maximum sequence depth exceeded ([dec]) by ([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.
%SUBSYS-3-NOAPIHOOK : The API [chars] has no lookup hook for subsystems.
Explanation This process uses the named API, but the process initialization code could not find the subsystem-initialization hook for this API. Process initialization cannot proceed without all hooks being present.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative, along with output from 'show tech'.
%SUBSYS-3-PAGEZERO : The [chars] class subsystem [chars] was being initialized.
Explanation In all Cisco products the first 256 bytes of memory is unused and off limits. Newer platforms have hardware to immediately trap reads or writes to this area. Older platforms periodically perform checks on this memory. This message appears only on older platforms and indicates that this off limits memory area was modified.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%SUBSYS-3-UNORDERED : The subsys class [dec]([chars]) has no initialization order.
Explanation The specified class subsystem has an unknown initialization order.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative, along with output from 'show tech'.
SWITCH_L2M
%SWITCH_L2M-3-ALLOC_FAILED : Allocation of [chars] memory failed for SWITCH_L2M feature in QFP
Explanation Allocation of memory by the QFP SWITCH_L2M 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SWITCH_L2M-3-INIT_FAILED : Initialization of the SVI feature in QFP failed
Explanation Initialization of the SWITCH_L2M 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SWITCH_L2M-3-PKT_REPLICA_INIT_FAILED : Failed to register with generic packet replication for SWITCH_L2M feature in QFP
Explanation SWITCH_L2M initialization of packet replication registration failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
SW_MGR
%SW_MGR-3-CM_ERROR : Connection Manager Error -[chars].
Explanation A Segment Switch Connection Manager error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SW_MGR-3-CM_ERROR_CLASS : Connection Manager Error: Class [chars]: -[chars].
Explanation A Segment Switch Connection Manager error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SW_MGR-3-CM_ERROR_FEATURE : Connection Manager Feature Error: ([chars]) -[chars].
Explanation A Segment Switch Connection Manager feature class error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SW_MGR-3-CM_ERROR_FEATURE_CLASS : Connection Manager Feature Error: Class [chars]: ([chars]) -[chars].
Explanation A Segment Switch Connection Manager feature error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SW_MGR-3-FHM_ERROR : SSM Feature Handler Manager Error -[chars].
Explanation A Feature Handler Manager error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SW_MGR-3-INVALID_HANDLE : Segment Manager Error -Invalid [chars] handle -[dec].
Explanation A Connection Manager error occurred due to a invalid handle.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SW_MGR-3-INVALID_SEGMENT : Segment Switch Manager Error -Invalid segment -[chars].
Explanation A Segment Switch Manager error occurred due to a invalid segment.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SW_MGR-3-SM_ERROR : Segment Manager Error -[chars].
Explanation A Segment Manager error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SW_MGR-3-SSM_SEG_ISSU : SSM Segment ISSU: [chars] not supported.
Explanation ISSU of this SSM Segment is not supported.
Recommended Action No action is required.
%SW_MGR-3-XDRREGISTRATION : XDR failed to register [chars] client due to [chars]
Explanation Failure to register the said XDR client.
Recommended Action No action is required.
SWPORT
%SWPORT-3-ALLOC_FAILED : Allocation of [chars] memory failed for SWPORT feature in QFP
Explanation Allocation of memory by the QFP SWPORT 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SWPORT-3-INIT_FAILED : Initialization of the SWPORT feature in QFP failed
Explanation Initialization of the SWPORT 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
SWPORT_PROXY
%SWPORT_PROXY-2-PROXY_IPC_INIT_FAILED : QFP SWPORT Proxy IPC interface initialization failure (result: [dec]).
Explanation Cisco internal software error. QFP SWPORT Proxy initialization detected that the IPC interface initialization failed. QFP SWPORT 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SWPORT_PROXY-3-PROXY_BAD_MSG : QFP SWPORT Proxy received bad length message type [dec]
Explanation Cisco internal software error. QFP SWPORT 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SWPORT_PROXY-3-PROXY_IPC_ALLOC_FAILED : QFP SWPORT Proxy [chars] message lost due to message buffer allocation failure.
Explanation Cisco internal software error. QFP SWPORT 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SWPORT_PROXY-3-PROXY_IPC_SEND_FAILED : QFP SWPORT Proxy [chars] message lost due to message sent failure (result: [dec]).
Explanation Cisco internal software error. QFP SWPORT 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SWPORT_PROXY-3-SWPORT_MEM_EXTEND_FAILED : SWPORT 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SWPORT_PROXY-3-SWPORT_MEM_REQ_FAILED : SWPORT 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SWPORT_PROXY-4-PROXY_INVALID_MSG : QFP SWPORT Proxy received invalid message type [dec]
Explanation Cisco internal software error. QFP SWPORT 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%SWPORT_PROXY-4-PROXY_INVALID_MSG_LEN : QFP SWPORT Proxy IPC invalid length, [dec]:[dec] len [dec] flags [hex] source [dec]
Explanation Cisco internal software error. QFP SWPORT 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
SYNCE_SPA_INFO
%SYNCE_SPA_INFO-6-NETSYNC_UNCONF_SOURCE : CLOCK LOCK is [chars] for [chars] interface, which is not selected as source to synchronize chassis.
Explanation INFORMATION Message: CLOCK LOCK is Cleared/Asserted for interface which is not configure as a source
Recommended Action No further action required. This is source monitor INFORMATION message, not an error Message.
SYS
%SYS-1-CISCOPRO : CiscoPro hardware requires CiscoPro software.
Explanation The CiscoPro hardware platforms require the use of CiscoPro specific software. Other software images from Cisco Systems will not function on this hardware
Recommended Action Obtain the appropriate CiscoPro software for your hardware.
SYSPLAT
%SYSPLAT-3-PLIM_BRIDGE_CRITICAL_ERROR : Reloading [chars] due critical event [hex] in block [chars]/[dec] of PLIM device
Explanation A critical PLIM device I/O event has occurred.
Recommended Action The system automatically reloads the hardware component experiencing the error. If the problem persists, copy the message exactly as it appears on the console or in the system log, collect the output of show tech-support and any other relevant logs, and contact your Cisco technical support representative.
%SYSPLAT-3-PLIM_CRITICAL_ERROR_RATE : Reloading [chars] due to critically high PLIM device error rate.
Explanation A Serial Bridge has experienced a persistently high error rate. The condition is serious and the card must be reloaded. This could be due to a hardware or software driver defect.
Recommended Action Copy the message exactly as it appears on the console or in the system log, collect the output of show tech-support and any other relevant logs, and contact your Cisco technical support representative.
%SYSPLAT-5-PLIM_BLOCK_EVENT : Block [chars]/[dec] of PLIM device had I/O event [hex]
Explanation A PLIM device I/O event has occurred. This event is not serious but is logged for diagnostic purposes.
Recommended Action No user action is required.
%SYSPLAT-5-PLIM_EVENT_RATE : The [chars] event rate of [int] has exceeded the threshold of [int] on interconnect [dec]
Explanation A Serial Bridge has experienced a high event rate. This condition is not considered serious, but is logged for diagnostic purposes. This could be due to a hardware or software driver defect.
Recommended Action No user action is required. If this message persists, a PLIM device critical message that needs to be addressed will appear.
T
TAC
%TAC-3-PICKCTX : No pick-context
Explanation The context to pick the next server has disappeared.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TAC-3-SECRETDEFINEFAILED : Key definition ignored.
Explanation The user is attempting to store either a corrupted shared secret or memory allocation failed during secret definition. Any existing shared secret will be preserved.
Recommended Action Configure a proper secret.
%TAC-3-SERVCONF : Server config failure: [chars]
Explanation The server configuration failed
Recommended Action Please configure the server properly
%TAC-3-SERVINT : [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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TAC-3-SERVNO : Server [chars] is not configured
Explanation The server is not configured
Recommended Action Please configure a server before un-configuring it
%TAC-3-XTACACL : [chars]: accesslist [hex] out of range for [chars]
Explanation The TACACS facility created a message that contains an accesslist which is not a valid accesslist (out of bounds).
Recommended Action If this message recurs, call your technical support representative for assistance.
%TAC-4-NOTIMEOUT : Warning: This command has been deprecated in favor of the line-command timeout login response
Explanation This command is deprecated, and should no longer be used. Instead, the line-command timeout login response now provides this functionality
Recommended Action Use the line-command timeout user-response
%TAC-4-SERVREF : Warning: Server [chars]:[dec] is still referenced by server group.
Explanation The server being removed is still referenced by a server group
Recommended Action Please dereference the server from the server group as soon as possible.
%TAC-4-SERVREFNAME : Warning: Server [chars] is still referenced by server group.
Explanation The server being removed is still referenced by a server group
Recommended Action Please dereference the server from the server group as soon as possible.
%TAC-4-UNEXREP : Reply for non-existent request, [dec] on queue
Explanation The TACACS facility received a message it was not expecting. This may occur when a TACACS server sends duplicate responses or when it responds to a request that has already timed out. It also may be due to an internal software problem.
Recommended Action If this message recurs, call your technical support representative for assistance.
%TAC-6-SENDTMO : Send type [dec] to [IP_address] timed out
Explanation A background TACACS notification (enabled with the command tacacs notify) was not acknowledged by the TACACS server processor within the timeout period (5 minutes). The information contained in that notification was lost. This loss of information may interfere with accounting or auditing on the server. This condition arises when the TACACS server is misconfigured, crashed, or became unreachable via the network.
Recommended Action Check the TACACS server and the network attached to it.
%TAC-6-SERVDEP : tacacs-server host CLI will be deprecated soon. Please move to tacacs server <name> CLI
Explanation Migration from tacacs-server host CLI to tacacs server <name> CLI
Recommended Action Please try to use new CLI
TAR_FS
%TAR_FS-3-IMAGE_FILE_INVALID : [chars] file not found in archive
Explanation The Tar File System could not locate the relevant tar element inside the archive
Recommended Action Check whether the Archive is complete and not corrupted or of the wrong format. If the problem could be recreated with debug ifs file turned on, it could help in quick identification of the problem. Collect the output of archive tar /table archive-name if it is a pure tar archive or show image contents file archive-name if the archive is a system image
TCP
%TCP-3-TCP_REG_FAILED : QFP TCP registers failed
Explanation Cisco internal software error. QFP TCP feature initialization detected that registration failed. QFP TCP 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
TCP_PROXY
%TCP_PROXY-2-PROXY_IPC_INIT_FAILED : QFP TCP Proxy IPC initialization failure (result: [dec]).
Explanation Cisco internal software error. QFP TCP Proxy initialization detected that the IPC interface initialization failed. QFP TCP 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TCP_PROXY-3-PROXY_BAD_MSG : CPP TCP Proxy received bad length message type [dec]
Explanation Cisco internal software error. CPP TCP 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TCP_PROXY-3-PROXY_DEBUG_REG_FAILED :
Explanation TCP Conditional Debugging registration failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TCP_PROXY-3-PROXY_INV_MSG : CPP TCP Proxy received invalid message type [dec]
Explanation Cisco internal software error. CPP TCP Proxy received an invalid message type 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TCP_PROXY-3-PROXY_IPC_ALLOC_FAILED : CPP TCP Proxy [chars] message lost due to message buffer allocation failure.
Explanation Cisco internal software error. CPP TCP 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TCP_PROXY-3-PROXY_IPC_CHUNK_FAILED : CPP TCP Proxy chunk memory failure [dec]
Explanation Cisco internal software error. QFP TCP Proxy chunk memory allocation detected failure. QFP TCP 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TCP_PROXY-3-PROXY_IPC_SEND_FAILED : CPP TCP Proxy [chars] message lost due to message sent failure (result: [dec]).
Explanation Cisco internal software error. CPP TCP 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
TDLDB
%TDLDB-3-SESSION_LOCK_TIMEOUT : Owner: user-proc: [chars], DB: [chars]. Lock expired [chars] ago.
Explanation An application running in a process wishes to have an exclusive write access to DB. It acquires a session lock with for a specific period and is expected to release or renew the session lock. The appication has failed to do so and hence the unexpected timeout has occured
Recommended Action This is unexpected. Report this to Cisco TAC.
TELNETD
%TELNETD-3-ISSUE_FILE_OPEN : Error opening login banner: [chars]
Explanation An error has occurred opening the login banner. It could not be displayed to a user connecting via telnet.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
TENSRFSM
%TENSRFSM-3-INVEVENT : Invalid event_id [hex]
Explanation state machine invalid event
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TENSRFSM-3-INVSTATE : Invalid current state [hex]
Explanation state machine invalid state
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TENSRFSM-3-INVTRANS : obj: [[hex]] event_id: [[hex]] er_p: [[hex]] arg: [[hex]] session state [chars] -> [chars]
Explanation state machine invalid transition
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TENSRFSM-3-NOEVENT : Unable to apply event [hex]
Explanation state machine transition failure
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TENSRFSM-3-NOPROCID : Unable to launch TE NSR FSM Process.
Explanation state machine transition process launch failure
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TENSRFSM-3-NULLMACH : Invalid machine pointer [hex]
Explanation state machine invalid pointer
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
THREAT_DEFENSE
%THREAT_DEFENSE-3-DESTROY_CHUNK_FAILED :
Explanation Destroy chunk failed.
Recommended Action LOG_STD_ACTION
%THREAT_DEFENSE-3-VTCP_INIT_FAILED :
Explanation Initialization of VTCP failed.
Recommended Action LOG_STD_ACTION
%THREAT_DEFENSE-4-TD_ERM_AVERAGE_THREAT : Event Rate Monitoring: Average threat identified. Zone [[chars]], event type [[chars]], average [[dec]] configured threshold [[dec]]
Explanation Event Rate Monitoring: Average threat identified
Recommended Action LOG_STD_ACTION
%THREAT_DEFENSE-4-TD_ERM_BURST_THREAT : Event Rate Monitoring: Burst threat identified. Zone [[chars]], event type [[chars]], configured threshold [[dec]]
Explanation Event Rate Monitoring: Burst threat identified
Recommended Action LOG_STD_ACTION
THREAT_DEFENSE_PROXY
%THREAT_DEFENSE_PROXY-3-PROXY_IPC_INIT_FAILED : [dec]
Explanation IPC handler initialization failed.
Recommended Action LOG_STD_ACTION
%THREAT_DEFENSE_PROXY-3-PROXY_MEM_EXTEND_FAILED :
Explanation Extending memory failed.
Recommended Action LOG_STD_ACTION
%THREAT_DEFENSE_PROXY-4-PROXY_IPC_INVALID_MSG : [dec]
Explanation Invalid IPC message
Recommended Action LOG_STD_ACTION
%THREAT_DEFENSE_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
TIME
%TIME-2-HB_START_FAILED : timer services failed to start
Explanation The timer services could not be started, because GPM allocation failed
Recommended Action LOG_STD_ACTION
%TIME-2-TIMESTAMP_BAD_CLOCK : [int]
Explanation Unsupported PPE core clock frequency.
Recommended Action LOG_STD_ACTION
%TIME-3-HB_SEQ_FAIL : expected seq_num [hex], rcvd seq_num [hex], MSGDEF_LIMIT_MEDIUM
Explanation The timer services had exceeded the maximum number of timer heartbeat sequence number errors.
Recommended Action LOG_STD_ACTION
TLSCLIENT
%TLSCLIENT-5-REKEY_CONN_FAILURE : Rekey failed for Session [[IPV6 address]] to TLSGW [[chars]]
Explanation This message indicates that the Rekey for the tunnel to the tlsgw failed.
Recommended Action Either the server is down or the connectivity to the server is broken
%TLSCLIENT-5-UPDOWN : Session [[IPV6 address]] to TLSGW: [[chars]] is [chars]
Explanation TLS Tunnel service state changed.
Recommended Action No action is required.
TMQ
%TMQ-3-NOTFOUND : TMQ, Attempt to delete entry not in queue
Explanation An attempt was made to delete an entry not in the queue.
Recommended Action Advisory message only. No action required.
TN
%TN-2-BADCONN : Bad conn pointer [hex] closing all connections on terminal line [dec]
Explanation An internal software error occurred.
Recommended Action If any message recurs, call your technical support representative for assistance.
%TN-2-BADLOGIN : Bad login string pointer [hex]
Explanation An internal software error occurred.
Recommended Action If any message recurs, call your technical support representative for assistance.
TN3270
%TN3270-2-INP_OVF1 : Input Buffer overflow
Explanation A problem in TN3270 protocol was detected. Eight KB (8192) bytes of data were received without a TN3270 end-of-packet indicator. The TN3270 buffer overflowed.
Recommended Action Copy this error message exactly as it appears, and contact your technical support representative for assistance.
TN
%TN-3-BADSTATE : Illegal state [dec]
Explanation An internal software error occurred.
Recommended Action If any message recurs, call your technical support representative for assistance.
%TN-3-READLINE : Unknown return code [dec] from telnet_readline()
Explanation An internal software error occurred.
Recommended Action If any message recurs, call your technical support representative for assistance.
TPLUS
%TPLUS-3-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, call your technical support representative for assistance.
%TPLUS-3-UNKNOWNTYPE : TPLUS: [hex] Unknown Request type [int].
Explanation Unknown request type in client request
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
TR
%TR-2-NOMEMORY : Unit [dec], no memory for [chars]
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.
%TR-2-PANIC : Unit [dec], panic %-08x %-08x %-08x
Explanation The Token Ring monitor firmware detected a fatal error that indicates an impending interface failure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TR-2-PANICINF : Unit [dec], PI %-08x %-08x %-08x %-08x %-08x %-08x
Explanation This message is similar to the %TR-3-PANIC error message, but indicates a nonfatal error. This message appears in very unusual situations that should not arise in normal operation.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%TR-2-PANICTYPE : Unit [dec], [chars] error
Explanation This message is similar to the %TR-3-PANIC error message, but indicates a nonfatal error. This message appears in very unusual situations that should not arise in normal operation.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%TR-3-ADPCHK : Interface [chars], adapter check error (non-fatal)([hex] [hex] [hex] [hex])
Explanation The Token Ring monitor firmware detected a non-fatal error on the interface card.
Recommended Action Issue a clear interface command. If this message recurs, call your technical support representative for assistance.
%TR-3-ADPCHKFATAL : Interface [chars], adapter check error (fatal) ([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. If this message recurs, call your technical support representative for assistance. You may need to replace the interface card
%TR-3-BADBRDGPARMS : Unit [dec], bad bridge parameters: bridge_num=[dec], max_rd=[dec]thisring=[dec], targetring=[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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%TR-3-BADBUFFSIZE : Unit [dec], bad buffersize = [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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%TR-3-BADFIRM : Unit [dec], Tokenring firmware download failed got [hex], expected [hex], at address [hex].[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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%TR-3-BADFIRMTYPE : Unit [dec], bad firmware type code during [chars]. type=[hex], fw=[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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%TR-3-BADFUNC : Unit [dec], bad functional address=[hex], ring mode=[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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%TR-3-BADMUL : [chars]: Can't set address to a multicast ([enet])
Explanation An attempt was made to set the Token Ring interface MAC address to a reserved multicast address.
Recommended Action Check your configuration. Make sure that your XNS and/or Novell Token Ring addresses have not inadvertently been set to reserved multicast addresses.
%TR-3-BADRNGNUM : Unit [dec], ring number ([dec]) doesn't match established number ([dec]).
Explanation The number you have configured for the local ring does not match the value currently in use on the ring.
Recommended Action Check the configuration to make sure you used the correct ring number. If it is correct, confirm the configuration of all other bridges on the ring to make sure they are using the same ring number.
%TR-3-BADSTART : Unit [dec], Start completion and wrong idb state -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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%TR-3-BADUNIT : Bad unit number [dec]
Explanation This error message pertains only to the IGS. When displayed, it indicates that the system cannot find the chipset registers where it expects them to be. This is most likely a hardware error.
Recommended Action If this message recurs, call your technical support representative for assistance. It will be necessary to determine the hardware unit configuration.
%TR-3-DIAGFAIL : Interface [chars] failed init diags ([hex]), [chars]
Explanation The microcode attempted to run its diagnostics on the chip and failed.
Recommended Action Issue a clear interface command. LOG_STD_RECUR_ACTION
%TR-3-INITFAIL : Unit [dec], init failed. result code=[hex], error code=[hex]
Explanation The Token Ring hardware failed to initialize properly.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%TR-3-INTFAIL : Unit [dec] interface failure: [hex] [hex] [hex], idb state [dec]
Explanation The Token Ring Monitor firmware detected a fatal error due either to an internal software problem or to a hardware failure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%TR-3-MODEFAIL : Unit [dec], change mode failed. result code=[hex], error code=[hex]
Explanation An internal hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%TR-3-NOFIRM : Unit [dec], no TMS380 firmware present. eagle=[hex], magic=[hex]
Explanation An internal hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%TR-3-OPENFAIL2 : Unit [dec], open failed: check the lobe cable DB-9 connection.
Explanation The Token Ring interface was unable to insert itself into the ring, and the error code returned indicates a wiring problem.
Recommended Action Check the cable connecting the router to the Token Ring MAU, and try to open the interface again. This generally can be accomplished by issuing the clear interface tokenring command. LOG_STD_RECUR_ACTION
%TR-3-OPENFAIL : Unit [dec], open failed: [chars], [chars]
Explanation The Token Ring interface was unable to insert itself into the ring. This is an indication of a busy or broken ring. The first character string in this error message indicates the stage of initialization at which the error occurred, and the second describes the error.
Recommended Action Try to open the interface again. This generally can be accomplished by issuing the clear interface tokenring command. If the error message recurs, call your Cisco technical support representative for assistance.
%TR-3-RESETFAIL : Unit [dec], reset failed, error code %-08x.
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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%TR-3-SETBRIDGEFAIL : Unit [dec], set bridge failed (code [hex]).
Explanation A hardware error occurred. The source routing accelerator (SRA) chip on the Token Ring card could not be initialized.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%TR-3-SETFUNFAIL : Unit [dec], set functional address failed (code [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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%TR-3-SETGRPFAIL : Unit [dec], set group address failed (code [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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%TR-3-WIREFAULT : Unit [dec], wire fault: check the lobe cable MAU connection.
Explanation The Token Ring hardware is reporting a wire fault condition.
Recommended Action Check the cable connecting the router to the Token Ring media attachment unit (MAU).
%TR-6-STATE : [chars]: Ring Status: [chars]
Explanation This message is displayed when the Token Ring's status changed as determined by the chipset. This information also is used to automatically determine whether the interface is still usable to propagate network traffic.
Recommended Action No action is required.
%TR-6-STATRING : TR[dec]: Ring Status: [chars] [chars]
Explanation This message is displayed when the Token Ring's status changed as determined by the chipset. This information also is used to automatically determine whether the interface is still usable to propagate network traffic. The meaning of each status code is shown in the Token Ring Status Codes Table. Code Explanation Fatal 0x8000 Signal loss Yes 0x4000 Hard error Yes 0x2000 Soft error No 0x1000 Transmit beacon Yes 0x0800 Lobe wire fault Yes 0x0400 Auto removal error Yes 0x0100 Receive request removed Yes 0x0080 Counter overflow No 0x0040 Single station No 0x0020 Ring recovery No
Recommended Action Check the Token Ring for the indicated condition.
TRACK
%TRACK-3-ERROR : Internal 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TRACK-4-WARN : Internal warning, [chars]
Explanation An internal software warning occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TRACK-6-INFO : Internal info, [chars]
Explanation An internal software information message occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TRACK-6-STATE : [chars]
Explanation The Tracked object has changed state.
Recommended Action No action is required.
TRCCFG
%TRCCFG-3-INVALID_BOOT_TRACE_CFG : Boottime trace configuration string [chars] invalid
Explanation The value is not accepted by flash library due to an error. The result is that the boottime trace configuration settings are not successfully saved for use across re-boots.
Recommended Action Check that the boot trace configuration is valid. If valid, try saving configuration again.
%TRCCFG-3-ROMMON_OUT_OF_SPACE_TRACE_CFG : No space in rommon for boot trace configuration
Explanation Rommon is full and does not have room to save boot trace configuration.
Recommended Action Remove any unnecessary rommon variables to free up space and retry.
TTY
%TTY-3-AUTOCONFIG : TTY%t: Modem auto-configuration failed
Explanation Modem auto-configuration failed either because the modem rejected the configuration string or because of a timeout. An attempt should be made to apply the configuration string mannually.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TTY-3-NOPROCESS : Cannot create [chars] process
Explanation Failed creating the process.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
TTYMON
%TTYMON-3-AGETTY : Cannot initiate a switch in console ownership. A required program could not be launched successfully.
Explanation The Host Manager process on the Route Processor, and only the Route Processor, is responsible for determining which process has control of the console port, either IOSd or an IOSXE process. A user can initiate a switch in ownership by by entering the 'send break' command at a telnet prompt to switch from IOSd to a shell instance. Control is returned to IOSd by exiting the shell instance. Switching ownership of the console port is initiated by the user entering a 'send break' command at a telnet prompt. The Host Manager launches one or more programs to authenticate users and to provide a shell instance. One or more of these programs has not been configured correctly.
Recommended Action Some required programs are either not available or not configured correctly or are failing for some reason. If this occurs after a recent upgrade it is possible that the upgrade has corrupted the current installation.
%TTYMON-3-CHASFS : The software which monitors ownership of the console port cannot [chars] a filesystem configuration value.
Explanation The Host Manager process on the Route Processor, and only the Route Processor, is responsible for determining which process has control of the console port, either IOSd or an IOSXE process. A user can initiate a switch in ownership by by entering the 'send break' command at a telnet prompt to switch from IOSd to a shell instance. Control is returned to IOSd by exiting the shell instance. The component within the Host Manager responsible for monitoring a change of console ownership uses the filesystem to store various settings. This error indicates that the daemon encountered a problem either reading or writing a value from/to the filesystem.
Recommended Action Check the log files for the Host Manager and search for entries related to 'ttymon' and 'chasfs' and this should give an indication as to why the operation failed. Check available resources and see if other daemons are also experiencing problems with the chassis filesystem since this may indicate a more pervasive problem. If so the reboot the box.
%TTYMON-3-INIT : The software which monitors ownership of the console port cannot be initialized correctly
Explanation The Host Manager process on the Route Processor, and only the Route Processor, is responsible for determining which process has control of the console port, either IOSd or an IOSXE process. A user can initiate a switch in ownership by by entering the 'send break' command at a telnet prompt to switch from IOSd to a shell instance. Control is returned to IOSd by exiting the shell instance. The component within the Host Manager responsible for this has encountered an initialization error and console monitoring is no longer available.
Recommended Action Check the status of the Host Manager process. Check the Host Manager log files for further indications as to why the initialization failed and if necessary restart the machine.
TUN
%TUN-3-6RD : [chars]: [chars]
Explanation The tunnel 6RD feature encountered an internal software error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TUN-3-API_ARGS : unexpected arguments: [chars], [chars]
Explanation A public tunnel component api was driven with arguments outside the expected boundaries.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TUN-3-CM1 : [chars]
Explanation The tunnel classification module encountered an internal software error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TUN-3-CM2 : [chars] [dec]
Explanation The tunnel classification module encountered an internal software error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TUN-3-DECAP_OCE : [chars] [chars]
Explanation An internal software error occurred in the tunnel subsystem which is responsible for building forwarding for the purposes of decapsulation
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TUN-3-DECAP_TINFO : [chars] [chars]
Explanation An internal software error occurred in the tunnel subsystem which is responsible for driving forwarding based on the tinfo configuration
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TUN-3-ENDPOINT_ERROR : [chars] [chars]
Explanation An internal software error occurred when manipulating the tunnel endpoint database
Recommended Action No action is required.
%TUN-3-ENDPOINT_STORE : Operation [chars] failed for [chars]
Explanation Manipulation of the tunnel endpoint store failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TUN-3-GROUPS : Tunnel Groups: [chars]: [chars]
Explanation The tunnel group component encountered an internal software error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TUN-3-ILLEGAL_ARGS : 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TUN-3-L3VPN_ENCAP_IP_PROFILE : L3VPN Encap IP : [chars]: [chars]
Explanation The L3VPN Encap IP component encountered an internal software error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TUN-3-L3VPN_GROUP : Tunnel L3VPN Groups: [chars]: [chars]
Explanation The tunnel group component encountered an internal software error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TUN-3-MTUCONFIGEXCEEDSL2MTU_IPV4 : [chars] IPv4 MTU configured [int] exceeds tunnel maximum MTU [int]
Explanation An IPv4 MTU value is configured on the tunnel interface and this value exceeds the tunnel's maximum MTU. This message is typically observed when the tunnel header size changes or when the MTU of the underlying exit interface changes. As a result of either, the tunnel maximum MTU can change. This message can also be observed when using an IPv6 tunnel to carry IPv4 since IPv4 MTU config in this case allows for a value to be configured that is greater than the tunnel's maximum MTU. As a result of any of these conditions, packets may be dropped.
Recommended Action If a specific IPv4 MTU value is not required, it is recommended that you leave the value at the default by typing no ip mtu on the tunnel interface. If a specific value is required, it is recommended that you check the interface MTU value from the show interface tunnel command and adjust ip mtu on the tunnel interface to be lower than or equal to this.
%TUN-3-MTUCONFIGEXCEEDSL2MTU_IPV6 : [chars] IPv6 MTU configured [int] exceeds tunnel maximum MTU [int]
Explanation An IPv6 MTU value is configured on the tunnel interface and this value exceeds the tunnel's maximum MTU. This message is typically observed when the tunnel header size changes or when the MTU of the underlying exit interface changes. As a result of either, the tunnel maximum MTU can change. This message can also be observed when using an IPv6 tunnel to carry IPv6 since IPv6 MTU config in this case allows for a value to be configured that is greater than the tunnel's maximum MTU. As a result of any of these conditions, packets may be dropped.
Recommended Action If a specific IPv6 MTU value is not required, it is recommended that you leave the value at the default by typing no ipv6 mtu on the tunnel interface. If a specific value is required, it is recommended that you check the interface MTU value from the show interface tunnel command and adjust ipv6 mtu on the tunnel interface to be lower than or equal to this.
%TUN-3-MULTI_KEYS_INFO : [chars] [chars]
Explanation Manipulation of the tunnel keys database failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TUN-3-MULTI_KEYS_INFO_ERROR : [chars] [dec]
Explanation Manipulation of the tunnel keys database failed because of incorrect idb_index.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TUN-3-OTV_GROUP : Tunnel OTV Groups: [chars]: [chars]
Explanation The tunnel group component encountered an internal software error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TUN-3-SIA_GROUP : Tunnel SIA Groups: [chars]: [chars]
Explanation The tunnel group component encountered an internal software error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TUN-3-TUN_DBG : TUN_DBG: [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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TUN-3-TUN_HA : Tunnel HA: [chars]
Explanation Tunnel HA encountered an internal software error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TUN-3-TUN_SB : TUN_SB: [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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TUN-3-TUN_SIDB2TUNS : [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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TUN-3-TUNTO : Operation: [chars], Action: [chars], Reason: [chars]
Explanation The tunnel-to module encountered an internal software error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TUN-3-WCCP_GROUP : Tunnel WCCP Groups: [chars]: [chars]
Explanation The tunnel group component encountered an internal software error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TUN-4-L3VPN_ENCAP_IP_SRC_DEL : L3VPN Encap IP : [chars]: [chars]
Explanation The user configuration change results in a warning. This message is typically printed when the user tries to delete a loopback interface, and the loopback interface is configured as the source interface of the L3VPN encap IP profile
Recommended Action It is recommended that the user removes the loopback interface as the source interface of the L3vpn encap ip profile, before deleting the loopback interface.
%TUN-4-MTUCONFIGEXCEEDSTRMTU_IPV4 : [chars] IPv4 MTU configured [int] exceeds tunnel transport MTU [int]
Explanation An IPv4 MTU value has been configured on the tunnel interface and this value exceeds the tunnel's transport (default) MTU. As a result, fragmentation of the transport packet may occur before this goes out of the underlying exit interface.
Recommended Action If a specific IPv4 MTU value is not required, it is recommended that you leave the value at the default by typing no ip mtu on the tunnel interface. If a specific value is required, it is recommended that you check the tunnel transport MTU value from the show interface tunnel command and adjust ip mtu on the tunnel interface to be lower than or equal to this.
%TUN-4-MTUCONFIGEXCEEDSTRMTU_IPV6 : [chars] IPv6 MTU configured [int] exceeds tunnel transport MTU [int]
Explanation An IPv6 MTU value has been configured on the tunnel interface and this value exceeds the tunnel's transport (default) MTU. As a result, fragmentation of the transport packet may occur before this goes out of the underlying exit interface.
Recommended Action If a specific IPv6 MTU value is not required, it is recommended that you leave the value at the default by typing no ipv6 mtu on the tunnel interface. If a specific value is required, it is recommended that you check the tunnel transport MTU value from the show interface tunnel command and adjust ipv6 mtu on the tunnel interface to be lower than or equal to this.
%TUN-4-MTUCONFIGLESSTHAN_MINIPV4MTU : [chars] IPv4 MTU [int] is lesser than the minimum IP MTU [int], fragmentation may occur
Explanation The IPv4 MTU value calculated on the tunnel interface is less than the minimum IP MTU. The MTU of the underlying exit interface of the tunnel is too small. As a result, fragmentation of the transport packet may occur before this goes out of the underlying exit interface.
Recommended Action If a specific MTU value is not required for the exit interface, it is recommended that you leave the value at the default by typing no mtu on the exit interface. If a specific value is required, it is recommended that you check the MTU value from the show interface command for the exit interface and adjust mtu on the tunnel exit to be higher than this.
%TUN-4-MTUDEFAULTEXCEEDSL2MTU_IPV4 : [chars] transport MTU [int] exceeds [chars] configured IPv4 MTU [int], fragmentation may occur
Explanation A default MTU value has been configured on the tunnel and this value exceeds the underlying physical interface MTU. As a result, fragmentation of the transport packet may occur before this goes out of the underlying exit interface.
Recommended Action If possible, increase the size of the IPv4 MTU on the underlying physical interface using ip mtu.
%TUN-4-UDLR_IDB_ERROR : UDLR [chars] -[chars]
Explanation An error was encountered on a udlr interface
Recommended Action No action is required.
%TUN-5-6RD_INFO : [chars]: [chars]
Explanation 6RD configuration has been removed as it is not compatible with the new sub-mode
Recommended Action No action is required.
%TUN-5-HW_IF_INDEX_ILLEGAL : Attempt to create tunnel interface for [chars] with illegal index: [dec]
Explanation Creation of tunnel interface failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TUN-5-IGNOREICMP6MTU : [chars] ignoring received ICMP6 Type 2 Code 0 , due to pmtud min-mtu setting
Explanation An ICMP6 Type 2 Code 0 (ICMP6 Packet Too Big message) packet has been received. This packet has specified a Next-Hop MTU smaller than the tunnel current minimum path mtu discovery mtu value. The ICMP6 packet has been ignored and the MTU of the tunnel has not been changed.
Recommended Action If you want the ICMP6 packet to be accepted and to be used to decrease the tunnel MTU then use the tunnel path-mtu-discovery min-mtu command to decrease the minimum mtu allowed. The min-mtu specified is the minimum tunnel payload mtu allowed. Use the show interface tunnel command to view the current path mtu discovery settings.
%TUN-5-IGNOREICMPMTU : [chars] ignoring received ICMP Type 3 Code 4, due to pmtud min-mtu 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 smaller than the tunnel current minimum path mtu discovery mtu value. The ICMP packet has been ignored and the MTU of the tunnel has not been changed.
Recommended Action If you want the ICMP packet to be accepted and to be used to decrease the tunnel MTU then use the tunnel path-mtu-discovery min-mtu command to decrease the minimum mtu allowed. The min-mtu specified is the minimum tunnel payload mtu allowed. Use the show interface tunnel command to view the current path mtu discovery settings.
%TUN-5-INIT_ERROR : A critical error [chars]occurred during initialization
Explanation Creation of tunnel subsystem failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TUN-5-L3VPN_IP_PROFILE_DELETE : l3vpn encap ip profile [chars] deleted
Explanation l3vpn encap ip profile is deleted
Recommended Action No action is required.
%TUN-5-RECURDOWN : [chars] temporarily disabled due to recursive routing
Explanation When routing the same payload protocol over a carrier protocol (tunneling IP over IP, for example), it is possible to misconfigure your network so that you will try to route to the tunnel destination address via the tunnel. This is usually caused by a misconfiguration of the tunnel or a temporary instability due to route flapping elsewhere in your network. It is important to take steps to ensure that routing information between the carrier networks and the payload networks is not allowed to mix. If the router discovers a recursive routing problem, it will temporarily shut down the tunnel interface for a few minutes so that the situation that is causing this problem can resolve itself as routing protocols converge. If the problem is caused by misconfiguration, the link may oscillate indefinitely.
Recommended Action No action is required.
%TUN-5-RECURDOWN_SRC : [chars] linestate down, recursive source interface, next output [chars]
Explanation Whilst evaluating tunnel linestate we revisted a source interface.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TUN-5-TUN_DB_IF : Operation on tunnel interface table failed for [chars] -[chars]
Explanation Manipulation of the tunnel interface table failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TUN-5-TUN_HWIDB_DELETE : Failed to delete hwidb for Tunnel [dec] index [dec]
Explanation Deletion of tunnnel interface failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TUN-5-TUN_HWIDB_LIST_DELETE : Failed to delete [chars] from tunnel hwidb list
Explanation Deletion of tunnnel from hwidb list failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TUN-5-TUN_HWIDB_LIST_INSERT : Failed to add [chars] to tunnel hwidb list
Explanation Insertion of tunnnel to hwidb list failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TUN-5-TUN_HWIDB_RECYCLE : Failed to recycle hwidb for Tunnel [dec] index [dec]
Explanation Recycling of tunnnel interface failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TUN-5-TUN_INTF_STATE_RESET : Failed to reset tunnel interface state for [chars]
Explanation Reset of tunnnel interface failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TUN-5-TUN_LIST_CREATE : Failed to create tunnel list [chars]
Explanation Creation of tunnel list failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TUN-5-TUN_SWIDB_DELETE : Failed to delete swidb for Tunnel [dec] index [dec]
Explanation Deletion of tunnnel interface failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TUN-5-TUN_SWIDB_RECYCLE : Failed to recycle swidb for Tunnel [dec] index [dec]
Explanation Recycling of tunnnel interface failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TUN-5-TUN_TABLE : Operation [chars] on tunnel table failed for [chars] -[chars]
Explanation Manipulation of the tunnel table failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TUN-5-TUN_UNIT_LIST_DELETE : Failed to delete entry unit [dec] to tunnel unit list
Explanation Deletion from tunnnel unit failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TUN-5-TUN_UNIT_LIST_INSERT : Failed to add entry unit [dec] to tunnel unit list
Explanation Insertion of tunnnel unit failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
TVI_PROXY
%TVI_PROXY-2-TVI_MSG_PROXYINIT_FAILURE : ET-Analytics -Failed to register IPC message handler, result code [int]
Explanation QFP ET-Analytics feature failed to register an IPC message handler for communication with control plane. This will cause the featue not to function.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TVI_PROXY-3-PROXY_HSL_ADD_DEST_FAILED :
Explanation HSL add destination failed.
Recommended Action LOG_STD_ACTION
%TVI_PROXY-3-PROXY_HSL_BIND_FAILED :
Explanation HSL bind failed.
Recommended Action LOG_STD_ACTION
%TVI_PROXY-3-PROXY_HSL_BIND_TEMPLATE_FAILED : [dec]
Explanation HSL bind tempalte failed at given index.
Recommended Action LOG_STD_ACTION
%TVI_PROXY-3-PROXY_HSL_CREATE_FAILED :
Explanation HSL creation failed.
Recommended Action LOG_STD_ACTION
%TVI_PROXY-3-PROXY_HSL_ENABLE_FAILED :
Explanation HSL enable failed.
Recommended Action LOG_STD_ACTION
%TVI_PROXY-3-PROXY_HSL_MODIFY_DEST_FAILED :
Explanation HSL modify destination failed.
Recommended Action LOG_STD_ACTION
%TVI_PROXY-3-PROXY_HSL_MODIFY_FAILED :
Explanation HSL modification failed.
Recommended Action LOG_STD_ACTION
%TVI_PROXY-3-TVI_MSG_PROXY_ALLOC_FAILURE : ET-Analytics -Failed to get [int] bytes space for IPC reply message
Explanation QFP ET-Anallytics feature detected buffer allocation failure while sending reply to a message from another layer of ET-Analytics feature's software stack.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TVI_PROXY-3-TVI_MSG_PROXY_DEBUG_REG_FAILED :
Explanation ET-Analytics Conditional Debugging Registration failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TVI_PROXY-3-TVI_MSG_PROXY_INVALID_MSGLEN : ET-Analytics -Received an invalid length IPC message
Explanation QFP ET-Analytics feature received an incorrect length of IPC message from anoter layer of ET-Analytics feature's software stack, m_enum %d, m_subtype %d, m_len %d, m_flags 0x%x, m_source %d.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TVI_PROXY-3-TVI_MSG_PROXY_IPCSEND_FAIL : ET-Analytics -Failed to send IPC message, result code [dec]
Explanation QFP ET-Analytics feature failed to send IPC message to another layer of ET-Analytics feature's software stack.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TVI_PROXY-3-TVI_MSG_PROXY_OPENREPLY_FAIL : ET-Analytics -Failed to open reply message part of IPC packet
Explanation QFP ET-Analytics feature failed to open message part of IPC packet while sending a reply to another layer of ET-Analytics feature's software stack.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%TVI_PROXY-3-TVI_MSG_PROXY_UNKNOWN_IPCMSG : ET-Analytics -Received an unknown type (code [int]), IPC message
Explanation QFP ET-Analytics feature received an unknown message from another layer of ET-Analytics feature's software stack.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%TVI_PROXY-4-PROXY_HSL_ALREADY_INIT :
Explanation HSL logger already initialized
Recommended Action LOG_STD_ACTION
%TVI_PROXY-4-PROXY_HSL_NOT_INIT : [int]
Explanation HSL logger not initialized
Recommended Action LOG_STD_ACTION
%TVI_PROXY-4-PROXY_IPC_INVALID_MSG_LEN : [dec]:[dec] len [dec] flags [hex] source [dec]
Explanation Invalid ET-Analytics IPC message length.
Recommended Action LOG_STD_ACTION
U
UBD
%UBD-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 inforation to a Cisco technical support representative.
%UBD-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.
%UBD-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.
%UBD-2-INITIALIZATION_FAILED :
Explanation Initialization of ursa bootstrap process failed.
Recommended Action Review UBOOTD 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.
UC_SAF
%UC_SAF-3-COMM_DECODE_ERR : [chars] while decoding [chars]
Explanation Error occurred while trying to decode the SAF advertisement
Recommended Action Turn on error debugs and re-publish the specified instance. Based on the information in the error logs, check and correct the configuration on the remote publisher
%UC_SAF-3-COMM_ENCODE_ERR : [chars] while encoding element [chars]
Explanation Error occurred while trying to encode the client supplied data
Recommended Action Modify the element that failed to encode using client's configuration clis
%UC_SAF-3-COMM_FWDR_ERR : [chars] for operation [chars] on instance [[int].[int].[int].[int]] sub-service [[dec]] for client [[chars]] on channel [[dec]]
Explanation Error occurred while trying to request an action from SAF Forwarder
Recommended Action If the failure is due to lack of memory, then check the size of free memory to make sure there is enough memory to run SAF service. If the error is due to mismatch between client and forwarder, then undo the current operation and retry. If the error is due to publish data is too large, then reduce the amount of data to be advertised and retry
%UC_SAF-3-COMM_FWDR_REG_ERR : [chars] for operation [chars] for client [[chars]] on channel [[dec]]
Explanation Error occurred while trying to request an action from SAF Forwarder
Recommended Action If the failure is due to lack of memory, then check the size of free memory to ensure there is enough memory to run SAF service. If the failure is due to invalid AS or vrouter name, check the values configured in the client with those of the Forwarder. If the error is due to mismatch between client and forwarder, then undo the current operation and retry
%UC_SAF-3-COMM_INT_ERR : Internal error occurred: [chars]
Explanation None
Recommended Action If the error is due to lack of memory check the size of free memory to make sure there is enough to run SAF service
%UC_SAF-3-COMM_NOTIFY_ERR : [chars] for operation [chars] on instance [[int].[int].[int].[int]] sub-service [[dec]] for client [[chars]] on channel [[dec]]
Explanation Error occurred while acting upon a notification from SAF Forwarder
Recommended Action If the failure is due to lack of memory, then check the size of free memory to make sure there is enough memory to run SAF service. If the error is due to invalid data received in the SAF advertisement, turn on error debugs and re-publish the service from the specified instance. Based on the information in the error debugs, check and correct the configuration on the remote publisher
%UC_SAF-3-COMM_OUTOFSYNC_ERR : [chars] error occurred with client [[chars]] on channel[[dec]]
Explanation COMM process is out of sync with client
Recommended Action Disable/delete the channel and retry the operation. If that does not help then shutdown and restart the client's SAF service
%UC_SAF-3-VSAF_CLIENT_COMM_QUEUE_ERROR : Unable to enqueue uc-comm event [chars] ([dec]) to process watched queue
Explanation An event to lower layer was dropped because it could not be added to the queue, most likely due to system's memory constraints. This may sometimes result in data and state inconsistencies across one or more modules or even nodes. Say in the case of publish the other nodes in the network who has subscribed to the service on this router may not get the latest advertised service data.
Recommended Action Check the size of free memory to make sure there is enough memory. Manually execute publish command when the memory conditions on the router improves to ensure the latest profile is advertised to other subscribed nodes.
%UC_SAF-3-VSAF_CLIENT_INSV_ERR : Could not bring voice saf client in service
Explanation Failed to instantiate client abstraction or initialization/ registration with other support modules has failed while voice service saf command was executed
Recommended Action Check the size of free memory to make sure there is enough memory to run SAF service
%UC_SAF-3-VSAF_CLIENT_INTERNAL : [chars]
Explanation An internal software error has occurred
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%UC_SAF-3-VSAF_CLIENT_PROCESS_CONTROL_ERR : Client process event loop detected -[chars]
Explanation Invalid state or unexpected events detected at the client manager process execution
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%UC_SAF-3-VSAF_CLIENT_SUBS_NOTIFICATION_ERROR : Error while adding or updating subscription notification from instance [dec]:[int].[int].[int].[int]
Explanation Subscription notification received from the specified instance could not be added in the database. This could be because none of the advertised patterns were found to be valid or trunk-route parameters were invalid or the SAF DN database was already full.
Recommended Action If the error is due to invalid advertisement, turn on error debugs and re-publish the specified instance. Based on the error logs check and correct the configuration on the remote publisher
%UC_SAF-3-VSAF_CLIENT_TASK_BAG_ERROR : Error while performing task bag [chars] corresponding to task event [dec] job.
Explanation A transient object that carries task parameters could not be instantiated or is corrupted. This may result in improper execution of the associated task which inturn can affect the ongoing operation.
Recommended Action Check the size of free memory to make sure there is enough memory.
%UC_SAF-3-VSAF_CLIENT_TASK_QUEUE_ERROR : Unable to enqueue task event [chars] ([dec]) to process watched queue
Explanation An internal event was dropped because it could not be added to the queue, most likely due to system's memory constraints. This may sometimes result in internal data structures to get into undeterministic state.
Recommended Action Check the size of free memory to make sure there is enough memory.
%UC_SAF-6-COMM_CHANNEL_UNREG : [chars] for client [[chars]] on channel [[dec]] could not be completed because channel was unregistered
Explanation The most likely reason could be that the forwarder sent REGISTRATION notification message to UC SAF COMM process which causes the channel to be unregistered. Any messages from VSAF client in the interim for that channel will fail
Recommended Action Take the necessary steps to re-instate the vrouter configurations. Then do shut followed by no shut on VSAF channel cli
%UC_SAF-6-VSAF_CHANNEL_REGISTER : Client channel id [dec] is [chars]
Explanation Configured voice saf operational state
Recommended Action If the channel went down unintentionally it is probably due to misconfiguration resulting in error. Check if the configured channel arguments matches those under router eigrp command level. Do shut/no shut under the channel to reset the voice saf channel operations
%UC_SAF-6-VSAF_SERVICE_PUBLISH_INVALID_PROFILE : Attempted publish of service [chars] ([dec]) with tag [dec] failed due to invalid profile.
Explanation The user or system triggered service advertisement failed due to the detection of invalid or incomplete profile.
Recommended Action Please check for the completeness of the service profile constructs. If they look ok, pls check the status of the interfaces used under the trunk-route profile session parameters.
%UC_SAF-6-VSAF_SERVICE_WITHDRAWN_INVALID_PROFILE : Service [chars] ([dec]) with inst-id <[int].[int].[int].[int]> has been withdrawn due to invalid profile [dec] detection.
Explanation Withdrawal of service triggered due to change in state of configured profile.
Recommended Action If the service was unintentionaly withdrawn it was probably due to certain critical parameters missing in the profile or if the state of the hardware used in the profile is down. Say ip interface state used in the trunk-route is down. Please verify and re-do the publish command from the config or exec level.
UDEV
%UDEV-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.
UDLD
%UDLD-3-UDLD_IDB_ERROR : UDLD error handling [chars] interface: [chars]
Explanation A softare error occurred in UDLD processing associated with a specific interface.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%UDLD-3-UDLD_INTERNAL_ERROR : UDLD internal error: [chars]
Explanation A softare sanity check failed in the course of UDLD processing.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%UDLD-3-UDLD_INTERNAL_IF_ERROR : UDLD internal error, interface [chars]: [chars]
Explanation A softare sanity check failed in the course of UDLD processing.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%UDLD-4-UDLD_PORT_DISABLED : UDLD disabled interface [chars], [chars] detected
Explanation An interface was disabled because UDLD protocol detected the cause indicated on the interface indicated. Cause is likely due to bad interface hardware or cable misconfiguration. User should investigate.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%UDLD-4-UDLD_PORT_FAILURE : UDLD failure reported per user request, interface [chars], [chars] detected.
Explanation An interface failure was reported because UDLD protocol detected the cause indicated on the interface. Cause is likely due to bad interface hardware or cable misconfiguration. Interface not err-disabled as user choose to see error-report. User should investigate and take action.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%UDLD-6-UDLD_PORT_RESET : UDLD reset interface [chars]
Explanation A port which had been disabled for UDLD has been reset.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
UFAST_MCAST_SW
%UFAST_MCAST_SW-3-PROC_START_ERROR : No process available for transmitting UplinkFast packets.
Explanation UplinkFast packets will not be transmitted as the process could not be created.
Recommended Action UplinkFast will not work unless you reload. If this problem persists even after reload, please contact your Cisco Technical Support representative with the configuration and technical support information.
%UFAST_MCAST_SW-4-MEM_NOT_AVAILABLE : No memory is available for transmitting UplinkFast packets on Vlan [dec].
Explanation UplinkFast packets will not be transmitted on Vlan %d due to a lack of memory.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
UI
%UI-3-IPC_ALLOC : module type [int] subtype [int]
Explanation IPC packet allocation failed for UI reply. Sender will not get reply
Recommended Action LOG_STD_ACTION
%UI-3-REPLY : module type [int] subtype [int]
Explanation A UI reply message failed in the IPC send. Sender will not get reply
Recommended Action LOG_STD_ACTION
%UI-6-NOHANDLER : module type [int] subtype [int]
Explanation A UI message was received containing an unrecognized module type or module subtype
Recommended Action LOG_STD_ACTION
UICFGEXP
%UICFGEXP-3-LIBRARY_ERROR : Error loading library '[chars]': [chars]
Explanation A configuration message was received which required a library to be loaded. The library failed to load.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%UICFGEXP-3-MESSAGE_ERROR : Unable to process message for '[chars]': [chars]
Explanation A message was received by the configuration export module which could not be processed. The message has been discarded.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%UICFGEXP-3-SYMBOL_ERROR : Error loading library symbol '[chars]' from '[chars]': [chars]
Explanation A configuration message was received which required a library to be loaded. The library failed to load all required symbols.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%UICFGEXP-3-WRITE_FAILED : Unable to write configuration for '[chars]': [chars]
Explanation The configuration export module failed to write the server configuration files. The server configuration change has not occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%UICFGEXP-6-SERVER_NOTIFIED_START : Server [chars] has been notified to start
Explanation The server has been notified to start.
Recommended Action No action is required.
%UICFGEXP-6-SERVER_NOTIFIED_STOP : Server [chars] has been notified to stop
Explanation The server has been notified to stop.
Recommended Action No action is required.
UIPEER
%UIPEER-2-TDL_MESSAGE : Cannot construct an IPC message for library. The message name is [chars] and the reason is: [chars]
Explanation A problem occurred while constructing a type definition language (TDL) message or setting a field in a TDL message. If the problem occurred during construction of a TDL message, then the system is out of memory. If the problem occurred while setting a field in the TDL message, there is a library mismatch issue.
Recommended Action Check [uipeer] ERR entries in the log files for message reporting problems.
%UIPEER-3-INVALID_DEBUG_MESSAGE : The peer process was unable to process an incoming message for 'debug all' from the shell-manager
Explanation When the 'debug all' command is issued, the Shell Manager broadcasts a notification of the command request to its peers. If the notification message has been corrupted or incorrectly created, the peers cannot complete the requested operation.
Recommended Action Check the trace files for the Shell Manager failed process. Restart the system.
%UIPEER-3-INVALID_EPOCH_MESSAGE : The peer process was unable to process an incoming epoch update message from the shell-manager
Explanation For each new type definition language (TDL) epoch, the Shell Manager broadcasts a change notification message to its peers. If the Shell Manager's message is incorrect or corrupt, the peers are unable to identify the new epoch. In this case, the peers reject the proposed epoch.
Recommended Action Check the trace files for the Shell Manager failed process. Check or undo any recently installed packages, then restart the system.
%UIPEER-3-INVALID_HOSTINFO_MESSAGE : The peer process was unable to process an incoming message for host info from the shell-manager
Explanation When host information, such as the hostname, changes, the Shell Manager broadcasts a notification of the change to its peers. If the notification message has been corrupted or incorrectly created, the peers cannot complete the requested operation.
Recommended Action Check the trace files for the Shell Manager failed process. Restart the system.
%UIPEER-3-NO_PEER : A process was unable to retrieve a shell-manager peer handle.
Explanation A process was attempting to communicate with the Shell Manager daemon using the integrated [uipeer] component. The error occurred because the peer instance could not be found.
Recommended Action Check [uipeer] ERR entries in the log files for message reporting problems.
%UIPEER-5-TIMER_ACCURACY_TEST : Timer Accuracy Test [chars].
Explanation Test result of Timer Accuracy Test
Recommended Action No action is required. This is informational message
UNICAST_FLOOD
%UNICAST_FLOOD-4-DETECTED : Host [enet] on vlan [dec] is flooding to an unknown unicast destination at a rate greater than/equal to [dec] Kfps
Explanation A Host has been found to be flapping between ports
Recommended Action Check the reason why the host is sending traffic to an unknown unicast destination
%UNICAST_FLOOD-4-FILTER_TABLE_FULL : The filter table is full
Explanation Too many floods to unknown destinations have been detected
Recommended Action Check the reason why in the network so many hosts are sending traffic to unknown unicast destinations
%UNICAST_FLOOD-5-FILTER_INSTALLED : Filter for host [enet] has been installed. It will be removed in %ld minute(s)
Explanation A host was flooding to an unknown destination. Filter has been installed as requested by the user
Recommended Action Check which host is sending traffic to unknown destinations and why
URLF
%URLF-3-ALLOW_MODE : [chars]Connection to all the URL filter servers are down and the allow mode is '[chars]'
Explanation This messages indicates that connection to all the URL filter servers are down. If allow mode is 'on' the router will pass all the http traffic, otherwise it will drop the http traffic and close the TCP connection
Recommended Action The network administrator can possibly check whether the URL filter server (WebSense/N2H2) is down and restart it if required. If it still does not work then the admin may have to install a URL filter server on another system and configure the same on the router.
%URLF-3-MAX_REQ : [chars]The number of pending request exceeds the maximum limit [dec]
Explanation This message indicates that the number of requests pending in the router for URL authentication from URL filter server exceeds the maximum limit. In this case the http request will be dropped
Recommended Action This message is just for informational purpose
%URLF-3-RESOURCE_ALLOC_FAILED : The resource allocation failed for URL filter subsystem
Explanation This message indicates that the URLF feature is not able to allocate memory for various data structures
Recommended Action The router is running out of memory, disable the features that are not used, or check if something goes wrong
%URLF-3-SERVER_DOWN : [chars]Connection to the URL filter server [IP_address] is down
Explanation This messages indicates that a connection between the router and a url filter server is down. If more than one servers are configured the router will make use of other servers for URL authentication, otherwise it will check whether allow mode is 'on' or 'off'. If allow mode is 'on' the router will pass all the packets, otherwise it will drop all the packet and close the TCP connection.
Recommended Action The network administrator can possibly check whether the URL filter server (WebSense/N2H2) is down and restart it if required. If it still does not work then the admin may have to install a URL filter server on another system and configure the same on the router.
%URLF-3-URL_TOO_LONG : [chars]URL sent from [IP_address] is too long (more than [dec] bytes), possibly a fake packet?
Explanation The URL parsed from http GET request is too long, it could possibly be a fake packet, so the packet will be dropped
Recommended Action This could be a fake packet sent by the attackers
%URLF-4-SITE_BLOCKED : [chars]Access denied for the site '[chars]', client [IP_address]:[dec] server [IP_address]:[dec]
Explanation This message indicates that all underlying URLs of the specified domain are blocked
Recommended Action This indicates that an user has made an attempt to browse a forbidden site
%URLF-4-URL_BLOCKED : [chars]Access denied URL '[chars]', client [IP_address]:[dec] server [IP_address]:[dec]
Explanation This message indicates that access to the requested URL is denied and the corresponding TCP connection is closed
Recommended Action This indicates that an user has made an attempt to browse a forbidden site
%URLF-5-SERVER_UP : [chars]Connection to an URL filter server([IP_address]) is made, the router is returning from ALLOW MODE
Explanation This message indicates that at least one connection is up between router and a URL filter server. System is leaving out of allow mode
Recommended Action This is just an informational message
%URLF-6-SITE_ALLOWED : [chars]Client [IP_address]:[dec] accessed server [IP_address]:[dec]
Explanation This message indicates that all URLs belongs to the server are allowed to be passed with out URL filter servers authentication
Recommended Action This message is just for informational purpose, it can be used to keep track of number of GET request that are sent from client to server
%URLF-6-URL_ALLOWED : [chars]Access allowed for URL '[chars]', client [IP_address]:[dec] server [IP_address]:[dec]
Explanation This message indicates that the http GET request sent from client is allowed to be transmitted to http server
Recommended Action This is just an informational message
USB_TOKEN
%USB_TOKEN-3-USB_TOKEN_MAX_TOKENS_INSERTED : Unavailable USB Security Token slot
Explanation Maximum number of tokens that can be supported are already inserted
Recommended Action Remove the other tokens that are not in use. And, remove and insert this token again.
%USB_TOKEN-3-USB_TOKEN_MSG_FAILURE : Failure in handling USB Security Token insertion/removal event
Explanation Retrieving Token insertion/removal message failed in Token Daemon
Recommended Action Remove the token and insert it back. If the problem still persists, report the problem to your technical support representative along with the output of show usb device, show usb controller and show file systems commands.
%USB_TOKEN-3-USB_TOKEN_NOMEM : No available memory for [chars]
Explanation Memory allocation failure.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
%USB_TOKEN-3-USB_TOKEN_SEMCREATE_FAILURE : Failure in creating USB Security Token semaphore
Explanation Watched semaphore creation failed
Recommended Action Report the problem to your technical support representative along with the output of show usb device and show usb controller commands.
USB_TOKEN_FILESYS
%USB_TOKEN_FILESYS-3-ASYNC_IO_ERROR_CREATING_DIRECTORY : Error creating directory: dir [chars], ret code [hex], [chars].
Explanation Token Asynchronous I/O process failed to create a directory in USB token device.
Recommended Action Report the error message to your technical representative along with the output of 'show usb', 'show usb controller' and 'show file system' commands.
%USB_TOKEN_FILESYS-3-ASYNC_IO_ERROR_CREATING_FILE : Error creating file: file [chars], ret code [hex], [chars].
Explanation Token Asynchronous I/O process failed to create a file in USB token device.
Recommended Action Report the error message to your technical representative along with the output of 'show usb', 'show usb controller' and 'show file system' commands.
%USB_TOKEN_FILESYS-3-ASYNC_IO_ERROR_DECODE_OP_CODE : Unrecognized I/O Op-code: [dec].
Explanation Token Asynchronous I/O process could not decode the Op-code in an I/O request.
Recommended Action Report the error message to your technical representative along with the output of 'show usb', 'show usb controller' and 'show file system' commands.
%USB_TOKEN_FILESYS-3-ASYNC_IO_ERROR_WRITING_FILE : Error writing file: file [chars], ret code [hex], [chars].
Explanation Token Asynchronous I/O process encountered I/O write failure.
Recommended Action Report the error message to your technical representative along with the output of 'show usb', 'show usb controller' and 'show file system' commands.
%USB_TOKEN_FILESYS-3-ASYNC_IO_FAIL_TO_GET_ARGUMENT : Token Asynchronous I/O: Could not get argument.
Explanation Token Asynchronous I/O process failed to retrieve argument.
Recommended Action Report the error message to your technical representative along with the output of 'show usb', 'show usb controller' and 'show file system' commands.
%USB_TOKEN_FILESYS-3-ASYNC_IO_FAIL_TO_REQUEUE_REQUEST : Token Asynchronous I/O: failing to requeue an I/O request.
Explanation Token Asynchronous I/O process failed to requeue an I/O request.
Recommended Action Report the error message to your technical representative along with the output of 'show usb', 'show usb controller' and 'show file system' commands.
%USB_TOKEN_FILESYS-3-ASYNC_IO_UNEXPECTED_EVENT : Token Asynchronous I/O: Unexpected Event [dec].
Explanation Token Asynchronous I/O process received an unexpected event.
Recommended Action Report the error message to your technical representative along with the output of 'show usb', 'show usb controller' and 'show file system' commands.
%USB_TOKEN_FILESYS-3-FAIL_TO_BUILD_MFD : USB Token File System failed to build MFD...
Explanation USB Token File System failed to build the Master File Directory (MFD) database.
Recommended Action Remove this token and insert it again. If the problem still persists, report the error message to your technical representative along with the output of 'show usb', 'show usb controller' and 'show file system' commands.
%USB_TOKEN_FILESYS-3-FAIL_TO_CREATE_TALKER : Token File System callback: failed to create token talker, token name [chars], status [dec].
Explanation USB Token File System failed to establish connection with USB Token Device Driver.
Recommended Action Remove and insert this token again. If the problem still persists, report the error message to your technical representative along with the output of 'show usb', 'show usb controller' and 'show file system' commands.
%USB_TOKEN_FILESYS-3-FAIL_TO_CREATE_WATCHED_BOOLEAN : Could not create a watched boolean!
Explanation USB Token File System could not create a watched boolean. This condition indicates that memory resources are being exhausted.
Recommended Action Reduce other system activities to ease memory demands or remove any token device that is not in use to free up some memory.
%USB_TOKEN_FILESYS-3-FAIL_TO_DESTROY_TALKER : Token File System callback: failed to destroy token talker, token name [chars], status [dec].
Explanation USB Token File System failed to destroy the connection with USB Token Device Driver.
Recommended Action Insert and remove this token again. If the problem still persists, report the error message to your technical representative along with the output of 'show usb', 'show usb controller' and 'show file system' commands.
%USB_TOKEN_FILESYS-3-FAIL_TO_REGISTER_WITH_IFS : Failed to register USB Token File System with IFS.
Explanation The process of registering USB Token File System with IOS File System (IFS) did not succeed. IFS provides a common user interface to all users of file system functionality regardless of the differences among file systems.
Recommended Action Remove this token and insert it again. If the problem still persists, report the error message to your technical representative along with the output of 'show usb', 'show usb controller' and 'show file system' commands.
%USB_TOKEN_FILESYS-3-MAX_TOKENS_INSERTED : The number of tokens exceeded the maximum that can be supported by USB Token File System.
Explanation Maximum number of tokens that can be supported by USB Token File System are already inserted.
Recommended Action Remove the other tokens that are not in use. And, remove and insert this token again. If the problem still persists, report the problem to your technical representative along with the output of 'show usb', 'show usb controller' and 'show file system' commands.
%USB_TOKEN_FILESYS-3-MFD_FORWARD_INCOMPATIBLE : Unable to understand MFD database of version [dec].[dec].
Explanation The version of the Master File Directory (MFD) database stored in token device is higher than what the running USB Token File System can support or understand.
Recommended Action Upgrade the USB Token File System by reloading the router with a higher version of IOS software.
%USB_TOKEN_FILESYS-3-UNKNOWN_TOKEN_EVENT : Token File System callback: unknown event [dec].
Explanation USB Token File System callback function received an unknown event from USB Token Device Driver.
Recommended Action Check USB ports to see if the token device is inserted or removed correctly. If the problem still persists, report the error message to your technical representative along with the output of 'show usb', 'show usb controller' and 'show file system' commands.
%USB_TOKEN_FILESYS-6-REGISTERED_WITH_IFS : USB Token File System [chars] is registered...
Explanation USB Token File System registered successfully.
Recommended Action Informational message only. No action required.
%USB_TOKEN_FILESYS-6-REGISTERING_WITH_IFS : Registering USB Token File System [chars]: might take a while...
Explanation Registering USB Token File System is being registered.
Recommended Action Informational message only. No action required.
%USB_TOKEN_FILESYS-6-USB_TOKEN_INSERTED : USB Token device inserted: [chars].
Explanation A USB Token device has been detected.
Recommended Action Informational message only. No action required.
%USB_TOKEN_FILESYS-6-USB_TOKEN_REMOVED : USB Token device removed: [chars].
Explanation A USB Token device has been removed.
Recommended Action Informational message only. No action required.
UTD
%UTD-2-IPC_FAILURE : UTD-IPC message [chars] handler failed, rc [int]
Explanation An IPC message handler for the UTD feature failed. This will cause the feature to not function.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%UTD-2-IPC_INIT_FAILED : UTD-IPC message handler registration failure, rc [int]
Explanation Registering an IPC message handler for the UTD feature failed. This will cause the feature to not function.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%UTD-3-FEAT_CTX_DOWN : UTD-Invalid request [chars] ([int]) while context is down
Explanation While the feature context was not active, an invalid request was received from another layer of the UTD software stack.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%UTD-3-FEAT_DOWN : UTD-Invalid request [chars] ([int]) while feature is down
Explanation While the feature was not active, an invalid request was received from another layer of the UTD software stack.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%UTD-3-IPC_INVALID_MSG : UTD-Invalid request [int]
Explanation We received an invalid message from another layer of the UTD software stack.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%UTD-3-IPC_INVALID_MSG_LEN : UTD-Invalid IPC length, [dec]:[dec] len [dec] flags [hex] source [dec]
Explanation Invalid IPC message length
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%UTD-3-IPC_NORES : UTD-No space for the IPC reply, size [int], request [int]
Explanation For a request from upper UTD software stack layers it was not possible to allocate space for a reply for the specified size.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%UTD-3-IPC_OPEN_REPLY : UTD-IPC Open Reply failed, request [int]
Explanation For a request from upper UTD software stack layers it was not possible to open the reply buffer.
Recommended Action This is normally a software issue. LOG_STD_RECUR_ACTION
%UTD-3-IPC_SEND_FAILED : UTD-IPC [chars] [int] send failed [int]
Explanation IPC message send failure
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%UTD-3-UTD_COND_DEBUG_REG_FAILED : Failed to initialize Conditional Debugging for UTD
Explanation A non-fatal error occurred when attempting to Register/Initialize conditional debugging.
Recommended Action LOG_STD_ACTION
%UTD-4-UTD_DIVERT_DROP_PKT : Diversion: VPATH decapsulation dropped packet from [chars] %CA:[int] => %CA:[int] proto [chars] due to ([int]) [chars] ident [int] [chars], MSGDEF_LIMIT_FAST
Explanation Packet dropped during packet reinjection
Recommended Action This message is for informational purposed only, but may indicate a security problem. LOG_STD_NO_ACTION
%UTD-4-UTD_ENCAPS_DROP_PKT : Diversion: VPATH encapsulation dropped packet from [chars] %CA:[int] => %CA:[int] proto [chars] due to ([int]) [chars] ident [int] [chars], MSGDEF_LIMIT_FAST
Explanation Packet dropped while attempting to add VPATH data
Recommended Action This message is for informational purposed only, but may indicate a security problem. LOG_STD_NO_ACTION
%UTD-4-UTD_INSPECT_DROP_PKT : Inspection: Dropped packet from [chars] %CA:[int] => %CA:[int] proto [chars] due to ([int]) [chars] ident [int] [chars], MSGDEF_LIMIT_FAST
Explanation Packet dropped during packet inspection for the given reason
Recommended Action This message is for informational purposed only, but may indicate a security problem. LOG_STD_NO_ACTION
%UTD-5-UTD_HEALTH_CHANGE : Service node changed state [chars] => [chars] ([int])
Explanation Service node and changed health status
Recommended Action Service node has changed status Green - Service node is health. No action required. Yellow - Service node not accepting new connections. Too many connections for enhanced inspection. Red - Service node is down Check IPS/IDS service node Not detected - Unknown state. Service node not detected Check IPS/IDS service node LOG_STD_ACTION
%UTD-5-UTD_POLICY_DROP_PKT : Policy: Dropped packet from [chars] %CA:[int] => %CA:[int] proto [chars] due to ([int]) [chars] ident [int] [chars], MSGDEF_LIMIT_FAST
Explanation Packet dropped during packet policy phase for the given reason
Recommended Action This message is for informational purposed only, but may indicate a security problem. LOG_STD_NO_ACTION
%UTD-5-UTD_POLICY_NAT_DROP_PKT : NAT packet drop, MSGDEF_LIMIT_SLOW
Explanation Packet dropped by NAT during UTD policy phase
Recommended Action Inspect NAT diagnostics to determine reason for packet drop LOG_STD_ACTION
%UTD-6-UTD_DF_BLACKLIST_MATCH : UTD WebFilter Domain Blacklist [**] [Domain: [chars]] [Matched Pattern: [chars]] {[chars]} %CA:[int] -> %CA:[int], MSGDEF_LIMIT_FAST/100
Explanation DNS domain matched to one of the configured blacklist patterns
Recommended Action This message is for informational purposed only, but may indicate a security problem. LOG_STD_NO_ACTION
%UTD-6-UTD_DF_WHITELIST_MATCH : UTD WebFilter Domain Whitelist [**] [Domain: [chars]] [Matched Pattern: [chars]] {[chars]} %CA:[int] -> %CA:[int], MSGDEF_LIMIT_FAST/100
Explanation DNS domain matched to one of the configured whitelist patterns
Recommended Action This message is for informational purposed only, but may indicate a security problem. LOG_STD_NO_ACTION
UTIL
%UTIL-0-ITEMLIST_RESIZE : An attempt was made to resize an itemlist but not enough memory is available
Explanation An attempt was made to resize itemlist memory to be larger than the memory available. Itemlists are often used when showing interface statistics. This event is unexpected and may be an indication of memory corruption.
Recommended Action Note any recent commands that may have triggered this error. Copy the error message and traceback exactly as it appears, and report it to your technical support representative.
%UTIL-3-DLL : Data structure error --[chars]
Explanation A software error occurred, resulting in data structure inconsistency.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%UTIL-3-IDTREE_NOTRACE : [chars]
Explanation A software error occurred, resulting in a data structure inconsistency.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%UTIL-3-IDTREE_TRACE : [chars]
Explanation A software error occurred, resulting in a data structure inconsistency.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%UTIL-3-RADIXTREE : Data structure error--[chars]
Explanation A software error occurred, resulting in a data structure inconsistency.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative. Ask for their assistance in obtaining a version of code with the error fixed.
%UTIL-3-RANGEINCON : internal inconsistency [dec] [hex]
Explanation A fatal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
%UTIL-3-RANGENULLINPUT : null pointer input to range function
Explanation An attempt was made to access a range function with a NULL pointer. The range list creation failed.
Recommended Action Review the error log for a corresponding malloc failed message. Copy the error message exactly as it appears, and report it to your technical support representative.
%UTIL-3-TREE : Data structure error--[chars]
Explanation A software error occurred, resulting in a data structure inconsistency.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative. Ask for their assistance in obtaining a version of code with the error fixed.
%UTIL-6-RANDOM : A pseudo-random number was generated twice in succession
Explanation A pseudo-random number generator produced the same number twice in succession.
Recommended Action Under normal circumstances a pseudo-random number generator will occasionally produce the same number twice in succession and this is not a problem. However if this message occurs frequently, the system should be manually reloaded. If the message is persistent across reloads, copy the error message exactly as it appears, and report it to your technical support representative.
V
VASI
%VASI-2-DB_ALLOC_FAIL : VASI pair db allocation failed
Explanation VASI pair database error. Memory chunk creation for VASI pair database has failed.
Recommended Action Check for accurate memory management. Perform memory leak checks and look for memory corruption causes. Execute 'show proc memory' command.
%VASI-2-DB_DELETE_FAIL : VASI pair db entry delete for interface [chars] failed
Explanation VASI pair database error. Removal of entry from VASI database has failed.
Recommended Action Check for accurate memory management. Perform memory leak checks, look for mamory corruption causes and check for correct database management. Execute 'show proc memory' command.
%VASI-2-DB_DESTROY_FAIL : VASI pair database destroy failed
Explanation VASI pair database error. Memory chunk destroy has failed for VASI pair database.
Recommended Action Check for accurate memory management. Perform memory leak checks and look for memory corruption causes. Execute show proc memory command.
%VASI-2-DB_ENTRY_ALLOC_FAIL : VASI pair db entry allocation for interface [chars] failed
Explanation VASI pair database error. Memory chunk allocation for VASI pair database entry has failed.
Recommended Action Check for accurate memory management. Perform memory leak checks and look for memory corruption causes. Execute 'show proc memory' command.
%VASI-2-DB_ENTRY_FREE_FAIL : VASI pair entry free failed
Explanation VASI pair database error. Memory chunk free of VASI pair database entry has failed.
Recommended Action Check for accurate memory management. Perform memory leak checks and look for memory corruption causes. Execute 'show proc memory' command.
%VASI-2-DB_INSERT_FAIL : VASI pair db entry add for interface [chars] failed
Explanation VASI pair database error. Insertion of a new entry into VASI pair database has failed.
Recommended Action Check for accurate memory management. Perform memory leak checks, look for memory corruption causes, verify correct database management. Execute 'show proc memory' command.
VDSL_DAEMON
%VDSL_DAEMON-3-FIRMWARE_WARN : Need to reload IOS for VDSL PHY firmware file change to take effect
Explanation The old phy firmware is used until IOS is reload
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%VDSL_DAEMON-3-FPGA_FAIL : VDSL FPGA Download failed.
Explanation The VDSL module hardware may be bad
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%VDSL_DAEMON-3-INITFAIL : VDSL Daemon [chars] init failed.
Explanation The VDSL module hardware may be bad
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%VDSL_DAEMON-3-INVALID_DS : Daemon [chars] invalid vdsl instance.
Explanation Encounter an invalid vdsl instance
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%VDSL_DAEMON-3-MALLOCFAIL : There is not enough main memory for the new VDSL [chars] firmware images on flash
Explanation The router failed to malloc a buffer for the firmware imageson the flash. More DRAM is required for the feature which allows specificVDSL firmware images on the flash to replace the VDSL firmware imagesembedded in IOS.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%VDSL_DAEMON-3-MODEMRESET : VDSL Modem reset. [chars]
Explanation The VDSL module is under reset.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/ . Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%VDSL_DAEMON-3-NOMEM : VDSL Daemon [chars] malloc failed : out of memory
Explanation The router does not have enough memory installed to run this VDSL/ADSL feature
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%VDSL_DAEMON-3-NOPROC : VDSL Daemon [chars] SM create event process failed
Explanation The router does not have enough memory run this VDSL/ADSL feature
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%VDSL_DAEMON-3-VDSL_CMD_ADD_FAIL : VDSL [chars] add failed.
Explanation adding a command exceeds the maximum number of commands allowed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%VDSL_DAEMON-3-VDSL_LINE_UPDOWN : Controller [chars], line [dec], changed state to [chars]
Explanation VDSL Line changed state
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%VDSL_DAEMON-4-INVALID_CDB : Invalid daemon [chars] controller [chars].
Explanation Encounter an invalid daemon cdb instance.
Recommended Action nothing
%VDSL_DAEMON-4-MODE_SWITCH : Please save the configuration and reload the Router due to the ATM-PTM mode change on vdsl 0 controller
Explanation Operating mode switch between ATM and PTM mode require reload
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%VDSL_DAEMON-4-QUEUE_EMPTY : Daemon [chars] configuration queue is empty.
Explanation program is unable to send a message to the queue process.
Recommended Action nothing
%VDSL_DAEMON-4-TRAINMODE_NOT_SUPPORTED : [chars] transport mode is not supported on [chars].
Explanation Only ATM is supported on ADSL and PTM/Ethernet is supported on VDSL2).
Recommended Action Change DSLAM profile to select the correct mode for CPE
VFI
%VFI-3-ILLEGAL : [chars]
Explanation An illegal event has been processed by the xconnect subsystem.
Recommended Action No action is required.
%VFI-4-CONFIG : [chars]
Explanation Invalid VFI configuration data passed.
Recommended Action No action is required.
%VFI-6-VFI_STATUS_CHANGED : Status of VFI [chars] changed from [chars] to [chars]
Explanation VFI status has changed
Recommended Action No action is required.
VIDB
%VIDB-3-FORKFAIL : 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%VIDB-3-FREETIMENOTSET : Value not specified for vidb forcible free time by platform.
Explanation Platform has requested for delayed vidb recycling support, but hasn't specified any value for forcible free time.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
VINES
%VINES-2-BADPARAM : [chars] called with [chars] parameter set to [chars]
Explanation One of the VINES lookup functions was called with an illegal argument.
Recommended Action Copy the message exactly as it appears, do a memory dump up to 128 bytes and the location specified in the error message, and report this information to your technical support representative.
%VINES-2-BADTIMER : RTP timer for [chars] was found disabled, and was reset
Explanation An internal interface timer is not running. This condition usually occurs after an interface is reset.
Recommended Action No action is required. The system automatically restarts the timer.
%VINES-2-CACHEFAILED : Cannot build cache entry ([dec] bytes) for %#z on [chars]
Explanation VINES fast switching detected that the packet destined to a given address did not have proper encapsulation information or its encapsulation size was too large to fit into the cache.
Recommended Action Verify that the VINES encapsulation and interface-specific mappings for the interface concerned are properly configured. Copy the message exactly as it appears, and report it your technical support representative.
%VINES-2-CACHEUNSUPP : Caching of [chars] not supported on [chars]
Explanation The cache population routing for VINES fast switching was called for an interface that does not support VINES fast switching.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative. If other encapsulation types are available on the interface, try using them. If this problem is not limited to one or two destinations but rather occurs with all traffic using the interface, diable VINES fast switching for the interface until you have identified the real cause of the problem.
%VINES-2-CONSISTENCY : Error [chars]
Explanation The VINES code ran into a situation that should not happen. For example, an IPC port number needs to be allocated, but all 65535 port numbers are currently in use. Another possible cause is that VINES attempted to add a cache entry but had no path associated with the destination address. This may cause temporary slow performance to only those stations that have experienced this inconsistency until complete cache entries are added. However, connectivity should not be lost, because all data traffic can still be routed vvia process-level switching.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative. If the warning message is about IPC port number depletion, use the show vines ipc command to check how many IPC ports are currently in use by which services and determine whether the IPC connections are all legitimate. To release IPC ports, issue the clear vines ipc command. If the warning message is about vines cache entries, provide the contents of the vines route cache, neighbor, and route tables immediately after the error messages appeared. If the problem persists, issue the clear vines cache command, and monitor the router if the situation improves.
%VINES-2-CORRUPTENTRY : Detected a corrupted entry in the [chars] table
Explanation The VINES code detected that an internal table entry was corrupted.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative. If possible, clear the VINES routing table or neighbor table, depending on the table in which the corrupted entry was observed. This will result in a temporary loss of connectivity until the routing or neighbor table is rebuilt.
%VINES-2-DUPADDR : Duplicate address detected on interface [chars]
Explanation The router detected that its VINES address is being used by another router.
Recommended Action To identify the other router that is using this address, manually inspect each router's configuration. When you have identified the router with the duplicate address, issue the vines routing recompute command on both routers or issue the enable vines routing command, specifying specify a unique address. If one of the routers does not support the recompute keyword, disable VINES on that router, issue the write terminal command to save the configuration to memory, reboot the router, and then enter the vines routing command with a unique vines address on the offending routers until each router has a unique address.
%VINES-2-ENCAPFAILED : Encapsulation failed for %#z via %#z on [chars]
Explanation VINES fast switching encountered an encapsulation failure when building a cache entry for a neighbor.
Recommended Action Examine your configuration for causes of the encapsulation failure. Look for missing map statements, interfaces that have gone down, and so on. If this error results in lost connectivity, disable vines fast switching by issuing the no vines route-cache command. Because disabling fast switching will slow network perform, you should issue the vines route-cache command to re-enable fast switching as soon as you have identified the cause of the problem. If you cannot identify the cause, contact your technical support representative. Provide the output of the show vines cache, show vines neighbor, and show vines route commands for the destination address and neighboring routers you are using. Also provide the output of the show interface and show vinces interface commands for the incoming and outgoing interfaces.
%VINES-2-INVALIDPATH : Bad [chars] in path for neighbor entry %z
Explanation While searching the neighbor table, the code determined that a pointer that should point to a VINES path structure actually points to some other structure.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative. If possible, clear the VINES neighbor table. This will result in a temporary loss of connectivity until all neighbors and routes are relearned.
%VINES-2-INVALIDROUTE : Bad [chars] in route for server entry %Z
Explanation While searching the routing table, the code determined that a pointer that should point to a VINES route structure actually points to some other structure.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative. If possible, clear the VINES routing table. This will result in a temporary loss of connectivity until all routes are relearned.
%VINES-2-NOBUFFERS : No buffers available for [chars]
Explanation There were no buffers available to send a VINES service query or reply.
Recommended Action Examine your system's memory and buffer capacity and compare it with current usage. If you notice a substantial discrepancy, monitor your system for possible memory leaks or buffer drainage and report the problem to your technical support representative, along with the output of the show memory, show memory processor, show buffers, show buffers assigned, and show buffers old commands.
%VINES-2-NOVENCAP : Encapsulation failed on [chars] for address %#z
Explanation The VINES code tried to send a packet on an interface that does not have a new encapsulation routine for outbound packets.
Recommended Action Toggle the problematic interface by issuing the interface shut and no shut commands, and then issue the no vines metric and vines metric command see if the problem goes away. If the problem persists, copy the message exactly as it appears, and report it your technical support representative. If possible, turn on and provide interface- specific debug traces, particularly for VINES activities.
%VINES-6-FNNOTFOUND : [chars] service [chars] routine missing [chars] vector
Explanation There is an inconsistency in the static VINES data structures for handling application-layer packets.
Recommended Action Turn on VINES service level debugging for the service reported in the error message, and copy the debug traces and the error message exactly as they appear, and report them to your technical support representative.
%VINES-6-IPCNOROUTINE : IPC port [dec] registered without an upcall ([chars])
Explanation There is an inconsistency in the active VINES data structure for handling IPC data messages. A message was received for a port that should have a listener, but the listener routine cannot be found.
Recommended Action Examine the IPC ports currently supported on the router by issuing the show vines ipc command, and see whether the reported IPC port is indeed not active. Copy the message exactly as it appears, and report it to your technical support representative along with the output of the debug vines ipc command.
%VINES-6-RPCNOSERVICE : IPC port [dec] registered without a service
Explanation There is an inconsistency in the active VINES data structure for handling Net RPC messages. A message was received for a port that should have a service description, but that service description cannot be found.
Recommended Action Enter the show vines ipc command and see whether the reported IPC port has a registered service. Copy the message exactly as it appears, and report it to your technical support representative, if possible, along with output of the debug vines netrpc command.
%VINES-6-RTNNOTFOUND : [chars] service [chars] routine not found while [chars]
Explanation There is an inconsistency in the active VINES service description data structures. A service handler routine cannot find the description of its own service.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative. In addition, provide the output of the show vines service command and debug vines service traces for the service reported in the error message.
VIRT_SERVICE
%VIRT_SERVICE-3-ACTIVATE_FAIL : Failed to send virtual service [chars] activate message
Explanation During the creation and transmission of the virtual service activate TDL message a failure occurred. The message was not successfully sent and therefore the virtual service was not activated.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%VIRT_SERVICE-3-DEACTIVATE_FAIL : Failed to send virtual service [chars] deactivate message
Explanation During the creation and transmission of the virtual service deactivate TDL message a failure occurred. The message was not successfully sent and therefore the virtual service was not deactivated.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%VIRT_SERVICE-3-INIT_FAIL : Failed to initialize required virtual service object: [chars]
Explanation During the initialization of the resources required for the virtual service feature, a memory allocation failure occurred. This has prevented the virtual service feature from being enabled.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%VIRT_SERVICE-3-INVALID_APPLIANCE_TIMEOUT : A response timeout occurred for an invalid virtual service
Explanation An unexpected condition occurred where the virtual service context pointer in the expired timer was set to NULL.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%VIRT_SERVICE-3-INVALID_RF_MSG : Received an invalid RF message type from peer
Explanation An unexpected condition occurred where an invalid message type was detected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%VIRT_SERVICE-3-PKG_PATH : Failed to [chars] required by virtual service [chars]
Explanation Specified package definition file was not found following a switchover.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%VIRT_SERVICE-3-PKG_PATH_ACTIVATE : Failed to [chars]. Virtual service [chars] will not be activated
Explanation Specified package definition file was not found following a switchover. Unable to activate virtual service without specified package definition file present.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%VIRT_SERVICE-3-RESET : Virtual service [chars] reset
Explanation An unexpected condition has occurred where Virt-manager has reported that it detected the named virtual service reset. This virtual service is not configured to be activated and as such, no attempt to reactivate it will be made.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%VIRT_SERVICE-3-RESPONSE_TIMEOUT : Virtual service [chars] timed out waiting for a response from Virt-manager
Explanation Failed to receive a response message from Virt-manager for last activation operation performed on the named virtual service. The virtual service activation state was marked as deactivated.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%VIRT_SERVICE-3-ROMMON_UNSUPPORTED : ROM monitor configuration does not support virtualization
Explanation Virtualization is not supported by the current ROM monitor configuration. Verify both the ROM monitor version and ROM monitor variable ENABLE_VTX are correct to enable virtualization.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%VIRT_SERVICE-3-SEND_RF_MSG : Failed to send RF message to peer -[chars]
Explanation An unexpected condition occurred where an attempt to send an RF message to peer failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%VIRT_SERVICE-3-STBY_PKG_PATH : Failed to [chars] required by virtual service [chars] on standby
Explanation Specified package definition file was not found on standby. Configuration was accepted. Copy package definition file to standby at earliest convenience.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%VIRT_SERVICE-3-STBY_ROMMON_UNSUPPORTED : Standby ROM monitor configuration does not support virtualization
Explanation Virtualization is not supported by the current ROM monitor configuration on the standby. Verify both the ROM monitor version and ROM monitor variable ENABLE_VTX are correct to enable virtualization.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%VIRT_SERVICE-3-UNKNOWN_APPLIANCE_TIMEOUT : A response timeout occurred for unknown virtual service [chars]
Explanation A response timeout occurred for a virtual service that is no longer in the virtual service database.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%VIRT_SERVICE-3-UNKNOWN_RF_MSG : Received an unknown RF message type ([dec]) from peer
Explanation An unexpected condition occurred where an unknown timer event was detected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%VIRT_SERVICE-3-UNKNOWN_TIMEOUT_TYPE : A response timeout occurred for an unknown timeout type ([dec])
Explanation An unexpected condition occurred where an unknown timeout type was detected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%VIRT_SERVICE-3-UNKNOWN_TIMER_EVENT : A timer event occurred for an unknown timer event ([dec])
Explanation An unexpected condition occurred where an unknown timer event was detected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%VIRT_SERVICE-3-UNPROVISION_FAIL : [chars]: [chars]
Explanation During the unprovision of the named virtual service, an unexpected failure occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%VIRT_SERVICE-4-SWITCHOVER_ACTIVATE : Virtual service [chars] will not be activated following a switchover
Explanation Following a switchover, this virtual service will not be activated as there is an issue with its package definition file. Copy package definition file to standby at earliest convenience.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%VIRT_SERVICE-5-ACTIVATION_STATE : [chars] [chars]
Explanation The activation state of the named virtual service has changed as notified by Virt-manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%VIRT_SERVICE-5-INSTALL_STATE : [chars] [chars]
Explanation The installation state of the named virtual service has changed as notified by Virt-manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%VIRT_SERVICE-5-RESET_REACTIVATE : Virtual service [chars] reset and will be reactivated
Explanation Virt-manager has reported that it detected the named virtual service reset. An attempt will be name to reactivate this virtual service.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
VLAN
%VLAN-3-INTERFACE_NOT_PRESENT : The [chars] link [chars] does not exist. Sub-interface: [chars] VLAN-Id: [int]
Explanation This message appears when the below command is issued (under port-channel sub-interface) with the unknown primary and/or secondary links. encap dot1q <vlan-id> primary <interface> secondary <interface> The interface specified in the command is not available at present. The card might have been physically removed or may not have been inserted properly.
Recommended Action Verify if the interface shows up, using the command - show ip int brief. Please insert the card in case it is removed and run the command again once the card comes up.
%VLAN-5-PRIMARY_LINK_NOT_IN_EC : Warning: VLAN [int]'s main interface is not the channel group of primary=[chars]Per-VLAN manual load-balancing will not take effect until channel-group is configured under the primary interface.
Explanation The interface configured as primary is not a memberlink in the port channel.
Recommended Action Verify the configuration.
%VLAN-5-SECONDARY_LINK_NOT_IN_EC : Warning: VLAN [int]'s main interface is not the channel group of secondary=[chars]Per-VLAN manual load-balancing will not take effect until channel-group is configured under the secondary interface.
Explanation The interface configured as secondary is not a memberlink in the port channel.
Recommended Action Verify the configuration.
VMAN
%VMAN-2-ACTIVATION_STATE : [chars] '[chars]' [chars] [chars]
Explanation The activation state of the named virtual service has changed as notified by Virt-manager.
Recommended Action In the failed case, check Virt-manager's logs for the cause of the failure. In the successful case, this notification can be ignored.
%VMAN-2-ALLOC_VIRT_INST_RCS : Virtual Service[chars]
Explanation A memory allocation request failed to allocate a data structure required to activate the virtual service.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
%VMAN-2-COMMIT_VIRT_INST_RCS : Virtual Service[chars]
Explanation The request to commit the resources required by the named virtual service failed.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
%VMAN-2-CPUSHARES_LIMIT : Virtual Service[chars]
Explanation The virtual service machine definition file is requesting more CPU shares than the system has available for virtual services.
Recommended Action Deactivate any other virtual services to free up CPU share resources and activate this virtual service. If that does not address the problem, then enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
%VMAN-2-CPUTUNES_INTERNAL_ERROR : Virtual Service[chars]
Explanation Virt-manager and its associated infrastructure experienced an internal error.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
%VMAN-2-CPUTUNES_SHARES_LIMIT : Virtual Service[chars]
Explanation The virtual service machine definition file is requesting more CPU shares than the system has available for virtual services.
Recommended Action Deactivate any other virtual services to free up CPU share resources and activate this virtual service. If that does not address the problem, then enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
%VMAN-2-CREATE_VIRT_INST_ENTRY : Virtual Service[chars]
Explanation The request to create a DB entry for the named virtual service failed.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
%VMAN-2-DEACT_FOR_ISSU : [chars] Max ([int]s)
Explanation An ISSU event is pending. Any active VMs will be automatically deactivated to allow ISSU preprocessing to validate the environment. Any ISSU-deactivated VMs will be automatically restarted if the ISSU is cancelled.
Recommended Action None. Allow the ISSU to continue and the VMs will restart when the ISSU completes or cancel the ISSU and vman will automatically
%VMAN-2-DEFER_VIRT_INST_PROC : Virtual Service[chars]
Explanation The final activation processing failed to successfully defer.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
%VMAN-2-DISK_IMAGE_PATH : Virtual Service[chars]
Explanation The virtual service machine definition file contains an invalid disk image path for one of the disk devices. This may be a Harddisk, CDROM or USB storage device.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
%VMAN-2-FIND_VIRT_INST_ENTRY : Failed to find virtual service with id [int] in the Virt-manager DB
Explanation The virtual service with the ID named could not be located in the Virt-manager DB.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
%VMAN-2-GENERAL_FAILURE : Virtual Service[chars]
Explanation The named virtual service has triggered the log. Please interpret the log in the context of the virtual services.
Recommended Action No action is required
%VMAN-2-GUESTSHELL_ENABLED : The guest shell has been enabled. The command '[chars]' may be used to access it, '[chars] destroy' to remove it.
Explanation Informs the user that the guest shell virtual service has been enabled (which is done by default).
Recommended Action The user may use or remove the guest shell with the commands specified.
%VMAN-2-HA_STATE : [chars] [chars] [chars] [chars]
Explanation VMAN tries to detect the role/slot of various nodes on HA events from the platform. If any of those event callbacks fail, this notification would be raised.
Recommended Action In the failed case, check Virt-manager's logs for the cause of the failure. Check for the HA event error msg and root cause the same.
%VMAN-2-HA_SWITCHOVER_STATE : [chars] [chars] [chars] [chars]
Explanation VMAN HA switchover state related messages for a virtual-service whilst it is being recovered on newly active RP after a HA switchover.
Recommended Action In the failed case, check Virt-manager's logs for the cause of the failure. Check for the HA event error msg and root cause the same.
%VMAN-2-HA_SYNC_ERR : [chars] '[chars]' [chars]
Explanation The ha-sync persistent storage disk for the virtual service cannot be watched for sync to standby RP.
Recommended Action Collect the Virt-manager logs and scan them for the cause.
%VMAN-2-HA_SYNC_THREAD_STATE : HA remote sychronize thread has failed and exited.
Explanation VMAN tries to remote sync the OVA repository to all online nodes using a separate thread. If that thread fails, this notification would be raised.
Recommended Action In the failed case, check Virt-manager's logs for the cause of the failure. Check for the pthread error msg and root cause the same.
%VMAN-2-INCONSISTENT_CPUTUNES_CONFIG : Virtual Service[chars]
Explanation The virtual service machine definition file is requesting invalid CPU tunes parameter.
Recommended Action Use a different valid machine definition file for the virtual service. If the problem persists, then enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
%VMAN-2-INCONSISTENT_MEM_CONFIG : Virtual Service[chars]
Explanation The virtual service machine definition file is inconsistent in the specification of required memory via the <memory> and <currentMemory> nodes.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
%VMAN-2-INSERT_VIRT_INST_ENTRY : Virtual Service[chars]
Explanation Inserting the named virtual service into the virtual service DB tracked by Virt-manager failed.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
%VMAN-2-INSTALL_FAILURE : Virtual Service[chars]
Explanation The installation of the virtual service failed.
Recommended Action Enable the Virt-manager trace logs and repeat the installation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
%VMAN-2-INSTALL_LOG : [chars] [chars] [chars] [chars]
Explanation The installation log of the named virtual service, is to provide more information about long running operation, that could affect the control of CLI
Recommended Action No action is required
%VMAN-2-INSTALL_MEDIA_RETRY : VMAN, VM install media still unavailable.[chars]
Explanation The install media was not detected. Waiting for udev to complete install media(harddisk) detection.
Recommended Action After VMAN exceeds the maximum retry limit, verify if install media (harddisk) is accessible and retry the installation again.
%VMAN-2-INSTALL_STATE : [chars] '[chars]'[chars] [chars]
Explanation The installation state of the named virtual service has changed as notified by Virt-manager.
Recommended Action In the failed case, check Virt-manager's logs for the cause of the failure. In the successful case, this notification can be ignored.
%VMAN-2-INVALID_ACT_MSG : Virtual Service[chars]
Explanation The virtual service activate message was received, however, the data it contained could not be interpreted
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
%VMAN-2-INVALID_DEACT_MSG : Failed to process virtual service deactivate message
Explanation The virtual service deactivate message was received, however, the data it contained could not be interpreted
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
%VMAN-2-INVALID_PACKAGE : Virtual Service[chars]
Explanation The package definition file for the named virtual service has failed to be validated and the virtual service will not run
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. The most likely cause would be that the package file has been corrupted during file transfer. The suggested action would be to redo the file transfer.
%VMAN-2-INVALID_UNPROV_MSG : Failed to process virtual service unprovision message
Explanation The virtual service unprovision message was received, however, the data it contained could not be interpreted
Recommended Action Enable the Virt-manager trace logs and repeat the activation followed by deactivation and then unprovision of the virtual service. Collect the Virt-manager logs and scan them for the cause.
%VMAN-2-MACHINE_TYPE_NOT_SUPPORTED : Virtual Service[chars]
Explanation The virtual service cannot be activated as the machine type specified is not supported
Recommended Action Enable the support for the machine type and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
%VMAN-2-MACH_PARSE_FAILURE : Virtual Service[chars]
Explanation The named virtual service has an invalid parameter specified in the .xml file inside the .ova package
Recommended Action Fix the .xml file inside the .ova package to have valid values. Then retry installing and activating it
%VMAN-2-MEMORY_LIMIT : Virtual Service[chars]
Explanation The virtual service machine definition file is requesting more memory than the system has available for virtual services.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
%VMAN-2-MEMORY_LIMIT_WARN : Virtual service ([chars])[chars] defines [int] MB of Memory exceeding the maximum [int] MB.
Explanation The virtual service machine definition file is requesting more memory for the specified profile, than the system has available for virtual services.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
%VMAN-2-MORETHANONE_CPUTUNES_CONFIG : Virtual Service[chars]
Explanation The virtual service machine definition file is requesting more than one CPU tunes parameter.
Recommended Action Use a different valid machine definition file for the virtual service. If the problem persists, then enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
%VMAN-2-MOVE_STATE : [chars] '[chars]' [chars] [chars]
Explanation The move of the core or log file of the named virtual service has as been successful or failed as notified by Virt-manager.
Recommended Action In the failed case, check Virt-manager's logs for the cause of the failure. In the successful case, this notification can be ignored.
%VMAN-2-NETWORK_CONFIG_ERROR : Virtual Service[chars]
Explanation A network configuration error has been detected for the named virtual service.
Recommended Action No action is required
%VMAN-2-PROCESS_PKG_DEF : Virtual Service[chars]
Explanation The virtual service package for the named virtual service has failed to be validated and the virtual service will not run.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
%VMAN-2-PROC_INT_LIST : Virtual Service[chars]
Explanation The interface list embedded in the activate request for the named virtual service could not be processed.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
%VMAN-2-REMOVE_VIRT_INST_ENTRY : Virtual Service[chars]
Explanation Removing the named virtual service from the virtual service DB tracked by Virt-manager failed.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
%VMAN-2-RESET_FORCE : Virtual Services non-recoverable reset command processed
Explanation A 'virtual service reset force' command has been entered and processed. This action initiates a cleanup of last resort. Occasionally a VM will get into an unrecoverable state that prevents it from activating but also from uninstalling. This is a rare event but when it happens the only resort may be to remove the .conf control file and reboot, which forces a cleanup of all previously installed VM files and artifacts. Note that once this command is used, current VMs are considered to be in an unstable or unpredictable state, and all future install, uninstall, upgrade, and activation commands will be blocked.
Recommended Action Once the command is entered and accepted, there is no recourse but to restart the system.
%VMAN-2-RESIZE_OPER_STATE : Virtual service '[chars]' [chars][chars] to '[int]' [chars]
Explanation VMAN attempts to resize various VM parameters like rootfs size, CPU share, memory if requested by user. Success/failure status messages for these resize operations are communicated by this syslog.
Recommended Action In the failed case, check Virt-manager's logs for the cause of the failure. Check for the HA event error msg and root cause the same.
%VMAN-2-RSYNC_STATE : [chars] [chars] [chars] [chars]
Explanation VMAN tries to remote sync the virtual-instance configuration file and the OVA repository to all online nodes. If rsync fails even after consecutive retries, this notification would be raised.
Recommended Action In the failed case, check Virt-manager's logs for the cause of the failure. Check for the rsync error code and root cause the same.
%VMAN-2-SET_VTX_ROMVAR_SPACE : Failed to set ROM monitor variable ENABLE_VTX: No space in table
Explanation Failed to set ENABLE_VTX ROM monitor variable due to no space in Monitor Variable Table.
Recommended Action Verify number of entries in Monitor Variable Table.
%VMAN-2-SET_VTX_ROMVAR_STRING : Failed to set ROM monitor variable ENABLE_VTX: Invalid string format: [chars]
Explanation Failed to set ENABLE_VTX rom monitor variable due to invalid string format.
Recommended Action Verify format of string from error message.
%VMAN-2-START_FAILED : Virtual Service[chars]
Explanation The named virtual service failed to start.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
%VMAN-2-UNINSTALL_ALL_VMS : All Virtual Services are being uninstalled [chars][chars] [chars]
Explanation All virtual services are being uninstalled by Virt-manager.
Recommended Action Examine the reason given as to why all virtual services are being uninstalled for more information. If the reason indicated is due to some error condition, check Virt-manager's logs for the cause of the failure.
%VMAN-2-UPGRADE_LOG : [chars] [chars] [chars] [chars]
Explanation The upgrade log of the named virtual service, is to provide more information about long running operation, that could affect the control of CLI
Recommended Action No action is required
%VMAN-2-VCPU_INVALID : Virtual Service[chars]
Explanation The virtual service machine definition file is requesting invalid VCPU value.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
%VMAN-2-VCPU_LIMIT : Virtual Service[chars]
Explanation The virtual service machine definition file is requesting more VCPUs than the system has reserved for virtual services.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
%VMAN-2-VIRT_INST_CRIT : VIRTUAL SERVICE [chars] LOG: [chars]
Explanation The named virtual service has triggered the log. Please interpret the log in the context of the virtual services.
Recommended Action No action is required
%VMAN-2-VIRT_INST_DISK : Virtual Service[chars]
Explanation The virtual service requires Disk Storage in excess of the Free Disk Storage available to virtual services.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
%VMAN-2-VIRT_INST_INTERFACE : Virtual Service[chars]
Explanation The number of configured virtual port group interfaces must match the number of Ethernet Network Interfaces defined in the machine definition file
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
%VMAN-2-VIRT_INST_LOG_UNTHROTTLE : Failed to unthrottle the log for virtual service [chars]
Explanation The named virtual service had sent overwhelming sys log messages and its log had been throttled as a result, but system has failed to unthrottle it for some reason.
Recommended Action For debugging collect the virt-manager logs and scan them for the cause.
%VMAN-2-VIRT_INST_MEMORY : Virtual Service[chars]
Explanation The virtual service requires physical memory in excess of the free memory available to virtual services.
Recommended Action Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.
%VMAN-2-VIRT_INST_MGMT_INTERFACE : Virtual service [chars] has no management interface defined but it is configured in CLI.
Explanation A management interface is configured but none is defined.
Recommended Action Deactivate the virtual service, remove the management interface configuration CLI, and reactivate the virtual-service.
%VMAN-2-VIRT_INST_STATE : Virtual Service[chars]
Explanation The named virtual service has failed. It is no longer running either because the guest OS has failed, the guest OS has shut down the machine or the emulator has failed.
Recommended Action An attempt at restarting the virtual service can be made from the IOS configuration by doing a no activate/activate. For debugging collect the Virt-manager logs and scan them for the cause.
%VMAN-3-PSS_ERR : Purpose: [chars], URI: [chars], errcode: [dec]
Explanation Persistent Storage Service handling error
Recommended Action Collect the Virt-manager logs and scan them for the cause.
%VMAN-3-PSS_SNAPSHOT_ERR : Source URI: [chars], Destination URI: [chars], errcode: [dec]
Explanation Persistent Storage Service snapshot error
Recommended Action Collect the Virt-manager logs and scan them for the cause.
%VMAN-3-SDWRAP_ERR : Description: [chars], errcode: [dec]
Explanation Debug infrastructure error
Recommended Action Collect the Virt-manager logs and scan them for the cause.
%VMAN-3-VIRT_INST_ERR : VIRTUAL SERVICE [chars] LOG: [chars]
Explanation The named virtual service has triggered the log. Please interpret the log in the context of the virtual services.
Recommended Action No action is required
%VMAN-4-HA_SYNC_NEEDED : If using the guest shell, please use 'guestshell sync' if you want to preserve state on standby in case of supervisor switchover
Explanation Message notifying user that he needs to manually synchronize the Virtual service contents to standby supervisor in order to preserve these contents in case of a supervisor switchover. Currently only applicable to the guest shell
Recommended Action User can type the 'guestshell sync' command on active supervisor to synchronize it's contents to the standby supervisor if desired.
%VMAN-4-PACKAGE_SIGNING_LEVEL_CHANGED : Package signing level changed from allow '[chars]' to allow '[chars]'
Explanation The package certificate signing level global setting has been changed via configuration under the virtual-service global sub-mode.
Recommended Action Ensure that this setting has been changed as expected by an authorized user.
%VMAN-4-UPDATE_WARNING : Virtual Service[chars]
Explanation The named virtual service has triggered the log. Please interpret the log in the context of the virtual services.
Recommended Action No action is required
%VMAN-4-VIRT_INST_WARN : VIRTUAL SERVICE [chars] LOG: [chars]
Explanation The named virtual service has triggered the log. Please interpret the log in the context of the virtual services.
Recommended Action No action is required
%VMAN-4-VIRT_SERV_LIBVIRTD_WARN : VMAN not able to connect to the libvirt daemon after '[dec]' attempts
Explanation VMAN has been unable to connect to the libvirt daemon. Virtualization services will not be available until this connection is made.
Recommended Action Collect the logs produced by 'show virt tech'
%VMAN-4-WATCHDOG_TIMER : [chars] '[chars]' [chars] [chars]
Explanation The watchdog timer configured for the named virtual service has expired.
Recommended Action Check any logs produced by the virtual service to determine the cause.
%VMAN-5-AUX : Virtual Service[chars]
Explanation The AUX login to a virtual service may allow the user access to system functions that may not have been tested or may interact with the system in unintended ways. Use with caution.
Recommended Action No action is required
%VMAN-5-PACKAGE_SIGNING_LEVEL_ON_INSTALL : Package '[chars]' for service container '[chars]' is '[chars]', [chars] '[chars]'
Explanation A service container software package with the certificate signing level described is being installed.
Recommended Action Take note of the service container and software package. Verify the software package is expected to be (un)signed as described and has the appropriate contents. Uninstall the package if unsure of the package origins.
%VMAN-5-PERMISSION_DENIED : Virtual Service '[chars]' is not owned by client IOSd
Explanation An attempt was made to modify a virtual-service that is not owned by by the client. The request was rejected.
Recommended Action No action is required.
%VMAN-5-VIRT_INST : LOG FROM VIRTUAL SERVICE [chars]: [chars]
Explanation The named virtual service has triggered the log. Please interpret the log in the context of the virtual services.
Recommended Action No action is required
%VMAN-5-VIRT_INST_NOTICE : VIRTUAL SERVICE [chars] LOG: [chars]
Explanation The named virtual service has triggered the log. Please interpret the log in the context of the virtual services.
Recommended Action No action is required
%VMAN-6-VIRT_INST_INFO : VIRTUAL SERVICE [chars] LOG: [chars]
Explanation The named virtual service has triggered the log. Please interpret the log in the context of the virtual services.
Recommended Action No action is required
%VMAN-7-VIRT_INST_DEBUG : VIRTUAL SERVICE [chars] LOG: [chars]
Explanation The named virtual service has triggered the log. Please interpret the log in the context of the virtual services.
Recommended Action No action is required
VOICE_HA
%VOICE_HA-1-DATA_RECREATE_ERR_THRESHOLD : ([chars]): RECREATE_ERR have exceeded threshold counts; performance degradation may occur. Most recent error: Module [chars] reported [chars] RECREATE failure (mainst ID:[dec], CID:[dec]) on STANDBY.
Explanation Specified HA module reported error during call leg re-create.
Recommended Action Collect requested data and forward to the appropriate DDTS-component/module owner of the specified HA module for investigation.
%VOICE_HA-1-INTERFACE_DOWN : [chars] RG[[dec]] [chars].
Explanation Interface went down
Recommended Action None
%VOICE_HA-1-SELF_STATE_PROTECTED : [chars] RG[[dec]] [chars].
Explanation VOICE HA functionality has been disabled in this router due to call checkpointing failure.
Recommended Action Router need immediate reload.
%VOICE_HA-2-BULK_SYNC_ERR : [chars].
Explanation VOICE HA INFRA encountered a bulk-sync error.
Recommended Action Collect requested data/traceback and forward to the voice-ha component.
%VOICE_HA-2-SWITCHOVER_IND : [chars].
Explanation VOICE HA detected a failover transition on the STANDBY to become the new ACTIVE.
Recommended Action Verify calls on the new ACTIVE. Peer needs to be in STANDBY mode before the next failover.
%VOICE_HA-2-SYM_DATA_COLLECT_ERR : UC-INFRA HA module [chars] reported DATA COLLECT failure (CID:[dec]) with error code [dec].
Explanation Specified HA module reported error during call leg data collection.
Recommended Action Collect requested data/traceback and forward to the appropriate DDTS-component/module owner of the specified HA module for investigation.
%VOICE_HA-2-SYM_DATA_RECREATE_ERR : UC-INFRA HA module [chars] reported RECREATE failure (CID:[dec]) with error code [dec].
Explanation Specified HA module reported error during call leg re-create.
Recommended Action Collect requested data/traceback and forward to the appropriate DDTS-component/module owner of the specified HA module for investigation.
%VOICE_HA-3-DATA_COLLECT_ERR : ([chars]): HA Module [chars] reported DATA COLLECT failure (mainst ID:[dec], CID:[dec]).
Explanation Specified HA module reported error during call leg data collection.
Recommended Action Collect requested data and forward to the appropriate DDTS-component/module owner of the specified HA module for investigation.
%VOICE_HA-3-DATA_RECREATE_ERR : ([chars]): HA Module [chars] reported [chars] RECREATE failure (mainst ID:[dec], CID:[dec]).
Explanation Specified HA module reported error during call leg re-create.
Recommended Action Collect requested data and forward to the appropriate DDTS-component/module owner of the specified HA module for investigation.
%VOICE_HA-5-PEER_STATE_PROTECTED : [chars] RG[[dec]]. HA functionality disabled for Voice.
Explanation VOICE HA functionality is disabled on the peer. due to call checkpointing failure.
Recommended Action Peer Router need immediate reload.
%VOICE_HA-5-PEER_STATE_READY : [chars] RG[[dec]] VOICE HA Peer exiting from PROTECTED state.
Explanation VOICE HA functionality is enabled on peer.
Recommended Action None
%VOICE_HA-7-STATUS : [chars].
Explanation VOICE HA INFRA info/status messages.
Recommended Action None
VOICE_IEC
%VOICE_IEC-3-EXT : Externally-generated Internal Error Code received: [dec].[dec].[dec].[dec].[dec].[dec]
Explanation Some external entity has initiated the termination of a voice call. It has signalled its Internal Error Code to this gateway, to be reported in the accounting record for this call. In addition, it is being reported through syslog because of the voice iec syslog configuration.
Recommended Action Refer to the IEC Error Message Decoder at http://www.cisco.com/univercd/cc/td/doc/product/voice/vtgemd.htm and enter the IEC, or enter the show voice iec description IECvalue command, with IECvalue being the value of the IEC that was received, for more information on the details of this error. It is possible some debugging actions might also indicate the cause of the error.
%VOICE_IEC-3-GK : [chars]: Internal Error ([chars]): IEC=[dec].[dec].[dec].[dec].[dec].[dec] on GUID [chars] confid [chars]
Explanation An internally-detected error has caused a voice call to be released or terminated. An Internal Error Code (IEC) has been generated to report the error. This IEC will be logged in the accounting record for this call. In addition it is being reported through syslog because of the voice iec syslog configuration.
Recommended Action Refer to the IEC Error Message Decoder at http://www.cisco.com/univercd/cc/td/doc/product/voice/vtgemd.htm and enter the IEC, or enter the show voice iec description IECvalue command, with IECvalue being the value of the IEC that was received, for more information on the details of this error. It is possible some debugging actions might also indicate the cause of the error.
%VOICE_IEC-3-GW : [chars]: Internal Error ([chars]): IEC=[dec].[dec].[dec].[dec].[dec].[dec] on callID [dec] [chars]
Explanation An internally-detected error has caused a voice call to be released or terminated. An Internal Error Code (IEC) has been generated to report the error. This IEC will be logged in the accounting record for this call. In addition it is being reported through syslog because of the voice iec syslog configuration.
Recommended Action Refer to the IEC Error Message Decoder at http://www.cisco.com/univercd/cc/td/doc/product/voice/vtgemd.htm and enter the IEC, or enter the show voice iec description IECvalue command, with IECvalue being the value of the IEC that was received, for more information on the details of this error. It is possible some debugging actions might also indicate the cause of the error.
VPDN
%VPDN-3-DROP_ADDR_MISMATCH : [chars]
Explanation The remote server changed its address.
Recommended Action Change initiate-to configuration at the LAC to point to the exact IP address LNS will use
%VPDN-3-IP_SWITCH_ERR : l2x ip switching vector not installed
Explanation Platform dependent l2x ip cef switching module is missing.
Recommended Action None
%VPDN-3-NORESOURCE : [chars] [chars][chars] no resources for user [chars][chars][chars]
Explanation The NAS/LAC or HGW/LNS is out of resources for the forwarding of a VPDN user.
Recommended Action None
%VPDN-4-REFUSED : Session for [chars] Refused status = [hex]
Explanation The remote server refused this session.
Recommended Action Check configuration on the HG or LNS
%VPDN-4-SESSIONERROR : [chars] [chars][chars] unable to terminate user [chars][chars][chars]
Explanation The HGW/LNS was unable to complete the forwarding of the VPDN user due to an internal error. This error may be resource related or configuration related. A reason string may be present to indicate the point of failure.
Recommended Action Check the configuration on the HGW/LNS
%VPDN-5-NOIDB : [chars] [chars][chars] unable to terminate user [chars]
Explanation The HGW/LNS is out of resources to create sessions for VPDN forwarded users, in particular it has reached the maximum number of interfaces allowed on the router.
Recommended Action None
%VPDN-5-UNREACH : [chars] [chars][chars] is unreachable
Explanation The NAS/LAC or HGW/LNS has timed out attempting to establish a tunnel connection to a HGW/LNS or NAS/LAC. This may be due to network or authentication/authorization issues.
Recommended Action Check configuration on the NAS/LAC or HGW/LNS, check network connectivity between the NAS/LAC and HGW/LNS. Check if the tunnel setup needs to have a different source IP address from that of the NAS/LAC.
%VPDN-6-AUTHENERR : [chars] [chars][chars] cannot authenticate for [chars] [chars] [chars][chars][chars]
Explanation The NAS/LAC or HGW/LNS is unable to locate a AAA server for the purposes of authenticating the user or tunnel. An error of this type indicates that the router was unable to establish a network connection with the designated/configured server. A reason string may also be present to provide further information.
Recommended Action Check AAA configuration on the NAS/LAC or HGW/LNS and network connectivity to the AAA server(s).
%VPDN-6-AUTHENFAIL : [chars] [chars][chars], [chars]authentication failure [chars]for [chars] [chars] [chars][chars][chars]
Explanation The NAS/LAC or HGW/LNS has failed to authenticate a user or a tunnel, or the HGW/LNS has failed authentication with the client which initiated the session. For authentication failures of the user or tunnel a reason string should be present which will indicate the point of failure. When a client fails to authenticate the HGW a reason string may be present depending upon the point of failure.
Recommended Action Check username configuration on the NAS/LAC or HGW/LNS and possibly even the client if the HGW/LNS is failing authentication, removing the negotiation of outbound authentication is one possible solution i.e. only authenticate the user in the inbound direction. If AAA is applicable, check AAA configuration on the NAS/LAC or HGW/LNS and network connectivity to the AAA server(s).
%VPDN-6-AUTHORERR : [chars] [chars][chars] cannot authorize for [chars] [chars] [chars][chars][chars]
Explanation The NAS/LAC or HGW/LNS is unable to locate a AAA server for the purposes of authorizing the user or tunnel. An error of this type indicates that the router was unable to establish a network connection with the designated/configured server. A reason string may also be present to provide further information.
Recommended Action Check AAA configuration on the NAS/LAC or HGW/LNS and network connectivity to the AAA server(s).
%VPDN-6-AUTHORFAIL : [chars] [chars][chars], [chars]authorization failure for [chars] [chars] [chars][chars][chars]
Explanation The NAS/LAC or HGW/LNS has failed to authorize a user or a tunnel. A reason string may be present to indicate the point of failure.
Recommended Action Check authorization configuration on the NAS/LAC or HGW/LNS. If AAA is applicable, check network connectivity to the AAA server(s).
%VPDN-6-CLOSED : [chars] [chars][chars] closed [chars] [chars] [chars][chars][chars]
Explanation The remote server, typically the HGW/LNS closed this session. The reason for the closure is encoded in a hexadecimal format and corresponds to the particular protocol descriptions i.e. for L2F the values are documented in section 4.4.5 of the Internet Draft. A description string may also be present which describes the closure reason.
Recommended Action Check configuration on the NAS/LAC or HGW/LNS
%VPDN-6-DOWN : [chars] [chars][chars] changed state to down [chars] [chars] [chars][chars][chars]
Explanation The remote server, typically the HGW/LNS closed this tunnel. The reason for the closure is encoded in a decimal format, which corresponds to the particular protocol descriptions i.e. for L2F the values are documented in section 4.4.5 of the Internet Draft. A description string may also be present which describes the closure reason.
Recommended Action Check configuration on the NAS/LAC or HGW/LNS
%VPDN-6-MAX_SESS_EXCD : [chars] [chars][chars] has exceeded configured local session-limit and rejected [chars] [chars] [chars][chars][chars]
Explanation The NAS/LAC or HGW/LNS has refused this session since the configured maximum VPDN session limit has been reached.
Recommended Action None
%VPDN-6-RESIZE : Updated [chars] MID table size to [int]
Explanation The NAS/LAC or HGW/LNS has altered the size of the session table through command line configuration.
Recommended Action None
%VPDN-6-SOFTSHUT : [chars] [chars][chars] has turned on softshut and rejected [chars] [chars] [chars][chars][chars]
Explanation The NAS/LAC or HGW/LNS can no longer accept new connection when softshut has been turned on. Existing session will continue until termination.
Recommended Action None
%VPDN-6-TIMEOUT : [chars] [chars][chars] disconnected [chars] [chars] [chars][chars][chars]
Explanation The NAS/LAC or HGW/LNS has disconnected the user due to the expiration of a timer, this may be e.g. PPP negotiation related or an absolute timeout for the session.
Recommended Action None
%VPDN-6-TUNNEL_IN_RESYNC : [chars] [chars] [chars] tunnel is in HA resync, reject [chars] [chars] [chars]
Explanation The tunnel towards the peer is still in High Availability (HA) resync, hence it cannot bring up any new sessions until the resync is complete.
Recommended Action It is normal for this to occur during tunnel High Availability (HA) resync phase. New sessions cannot be brought up on a tunnel that is in HA resync. Once resync is complete, new sessions can be brought up on this tunnel.
%VPDN-6-VPDN_DEADCACHE_EVENT : LSG dead cache entry [IP_address] [chars]
Explanation A dead cache entry status is changed in the VPDN Load Sharing Group (LSG) table. The event could be 'Added', where a LSG entry goes Down, 'Deleted', where an entry moves out of the Down status, or 'Cleared', where an entry is cleared by a user.
Recommended Action None
VRFS
%VRFS-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%VRFS-3-SBNOFN : Missing [chars] subblock [chars] function for [chars]
Explanation Functions for distributing this subblock are missing from the image.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
VRRP
%VRRP-3-ERROR : Internal 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%VRRP-4-BADAUTH : Bad authentication from [IP_address], group [dec], type [dec]
Explanation Two routers participating in VRRP disagree on authentication
Recommended Action Use the vrrp authentication command to repair the VRRP authentication discrepancy between the local system and the one whose IP address is reported.
%VRRP-4-BADAUTHTYPE : Bad authentication from [IP_address], group [dec], type [dec], expected [dec]
Explanation Two routers participating in VRRP disagree on the valid authentication type.
Recommended Action Use the vrrp authentication command to repair the VRRP authentication discrepancy between the local system and the one whose IP address is reported.
%VRRP-4-CFG_WARN : [chars]
Explanation There is a mismatch in the number of additional addresses advertised by the peer; or the addresses are mis-ordered in the peer advertisement.
Recommended Action No action is required.
%VRRP-4-WARN : Internal warning, [chars]
Explanation An internal software warning occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%VRRP-6-INFO : Internal info, [chars]
Explanation An internal software information message occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%VRRP-6-STATE : [chars]
Explanation The VRRP router has changed state.
Recommended Action No action is required.
%VRRP-6-STATECHANGE : [chars] Grp [dec] state [chars] -> [chars]
Explanation The VRRP router has changed state
Recommended Action No action is required.
VRRS
%VRRS-3-ACCTFORKFAIL : Failed to start accounting process. Accounting-off records may not be sent.
Explanation Failed to create the accounting process.
Recommended Action Free up some memory.
%VRRS-3-ERROR : Internal 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%VRRS-4-WARN : Internal warning, [chars]
Explanation An internal software warning occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%VRRS-6-INFO : Internal info, [chars]
Explanation An internal software information message occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%VRRS-6-STATE : [chars]
Explanation The VRRS router has changed state.
Recommended Action No action is required.
VTCP
%VTCP-3-VTCP_CREATE_CB_MALLOC_FAILED :
Explanation Malloc failed during VTCP create callback.
Recommended Action LOG_STD_ACTION
VTSP
%VTSP-2-H320_MATCH_CALL_QUEUE_ERROR : Memory corruption is found on H.320 Primary Call Match Data Queue. Queue Size=[dec]
Explanation Failed to match an H.320 primary call for an incoming call due to memory curruption.
Recommended Action Contact your technical support representative. Report the configuration and full text of the error message.
%VTSP-3-CAPABILITYMISMATCH : voice port [chars]: call connection id [[hex] [hex] [hex] [hex]]
Explanation There was a capabilities mismatch between the two call legs. capabilities are negotiated between call legs for CODEC, VAD and FAX rate.
Recommended Action Check that the dial peer configuration is appropriate for the interface in question. Also check that and configuration on the interface is correct.
%VTSP-3-DOCALLHISFAIL : vtsp_do_call_history: [chars]
Explanation Allocate or insert an active VTSP call record into call history list failed.
Recommended Action No action is required.
%VTSP-3-DSPALARM : channel [chars], DSP ID [hex]: status=[hex] message=[hex] text=[chars]
Explanation The DSP reported a fatal error. All calls on the DSP were dropped and a DSP reload was attempted.
Recommended Action Verify that the DSP reloaded properly by attempting to place a call on the affected voice port. Contact your technical support representative, include the full text of the error message.
%VTSP-3-DSP_TIMEOUT : DSP timeout on channel [chars], event [hex]: DSP ID=[hex]: [chars] (call mode=[dec])
Explanation Timeout on DSP response.
Recommended Action The DSP has been automatically reset. If problem persists, contact your technical support representative
%VTSP-3-FSM_ERROR : [chars]
Explanation Internal Finite State Machine Error.
Recommended Action Contact your technical support representative, include the full text of the error message.
%VTSP-3-MSGSNDFAIL : channel:[chars] DSP ID:[hex] Message ID:[hex]
Explanation A message could not be sent to the DSP. The call continued but may have experienced problems.
Recommended Action Verify that the DSP is still functioning properly by attempting to place a call on the affected voice port. Contact your technical support representative, include the full text of the error message.
%VTSP-3-NOEVENT : no free event structure available from [chars] for DSP message
Explanation There were no event 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.
%VTSP-3-VTSP_BLOCK : vtsp_call_block allocate failed
Explanation VTSP call block allocation failed.
Recommended Action Add more memory
%VTSP-3-VTSP_CALL_DISC_FAILED : VTSP call disconnect failed. channel id [chars], ret [dec]
Explanation VTSP call disconnect could not be successfully passed and it may result hung calls.
Recommended Action Contact your technical support representative. Report the configuration and full text of the error message.
%VTSP-3-VTSP_CALL_INFO_CHUNK : VTSP callInfo chunk creation failed.
Explanation Creation of VTSP callInfo chunk failed due to lack of memory.
Recommended Action Add more memory.
%VTSP-3-VTSP_DB_ERR : vtsp_call_block database error
Explanation Internal VTSP call block 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.
%VTSP-3-VTSP_HAIRPIN_FAILED : Call hairpinning failed. cdb [hex], dst_cdb [hex], dst_call_id [dec]
Explanation A DSP-less call could not be hairpinned.
Recommended Action Under heavy traffic, this failure may happen because no TDM resources wereavailable. Contact your technical support representative, include the full text of the error message.
%VTSP-3-VTSP_HAIRPINN : hairpin peer cdb does not exist, cdb [hex], dst_call_id [dec]
Explanation A hairpin call setup failed because the other call leg does not exist.
Recommended Action Contact your technical support representative. Report the configuration, and the full text of the error message.
%VTSP-3-VTSP_HAIRPIN_NOTPOSSIBLE : Call can't be hairpinned. cdb [hex], dst_cdb [hex], dst_call_id [dec]
Explanation A DSP-less call could not be hairpinned.
Recommended Action Check the dial-peer configuration.
%VTSP-4-FSM_BAD_EVENT : Invalid FSM Input on channel [chars]: state=[chars] event=[dec]
Explanation Internal state machine illegal input. This message represents an internal software fault and may manifest itself as dropped or hung calls.
Recommended Action Contact your field service representative if indication is coincident with dropped or hung calls.
%VTSP-4-VTSP_PLAR_TIE_FAILED : VTSP connection plar tie set up failed. channel id [chars], cause [dec]
Explanation Connection plar tie set up failed for non-normal reason
Recommended Action Contact your technical support representative. Report the configuration and full text of the error message.
%VTSP-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%VTSP-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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
W
WANPHY
%WANPHY-4-WANALARM : [chars]: [chars] [chars]
Explanation The specified WANPHY Alarm has been declared or cleared.
Recommended Action Recommended action is to repair the source of the alarm.
WCCP
%WCCP-1-SERVICELIST : Failed to derive service [chars][chars][chars] from service-list [chars]
Explanation The WCCP Access Control List used to define the specified closed service has been modified and can no longer be used to create the service. The service has been marked as inactive. Either change the configuration to an Open service or update the ACL to correctly identify the desired service
Recommended Action Update the service-list ACL to correctly define the desired service
%WCCP-1-SERVICELOST : Service [chars][chars][chars] lost on WCCP client [chars]
Explanation WCCP has lost the service associated the specified WCCP client
Recommended Action Verify the operation of the specified WCCP client
%WCCP-3-BADACE : Service [chars][chars][chars], invalid access-list entry (seq:[dec] reason:[chars])
Explanation The Access Control List associated with the specified WCCP service contains an incompatible entry. The hardware cannot process the resultant merged access list and will fall back to software based netflow switching
Recommended Action Update the Access Control List to remove or change the incompatible entry
%WCCP-3-CAP_API_DEF : Failed to set WCCP platform parameter defaults [hex] ([chars])
Explanation The platform failed to set the WCCP platform parameter defaults.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%WCCP-3-CAP_API_GET : Failed to get WCCP platform parameter [int] ([chars])
Explanation The platform failed to read a WCCP platform parameter.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%WCCP-3-CAP_API_INI : Failed to initialize WCCP platform parameter [int]
Explanation Initialization of a WCCP platform parameter failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%WCCP-3-CAP_API_SET : Failed to set WCCP platform parameter [int] to [int] ([chars])
Explanation The platform failed to modify a WCCP platform parameter.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%WCCP-3-SBADDFAIL : Unable to add [chars] WCCP subblock on interface [chars]
Explanation An internal error indicating that the WCCP process was unable to attach interface specific service information
Recommended Action Ensure that there is enough memory available for all processes
%WCCP-3-SBCREATEFAIL : Unable to allocate [chars] WCCP subblock on interface [chars]
Explanation An internal error indicating that the WCCP process was unable to allocate memory to hold interface specific service information
Recommended Action Ensure that there is enough memory available for all processes
%WCCP-3-SBINIT : Error initializing [chars] WCCP 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. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%WCCP-3-SIFIGNORED : source-interface [chars] ignored ([chars])
Explanation The configured source interface has been ignored whilst determining the WCCP router ID.
Recommended Action Use the indicated reason message to determine why WCCP refused to use the configured interface as its router ID.
%WCCP-5-SERVICEFOUND : Service [chars][chars][chars] acquired on WCCP client [chars]
Explanation WCCP has acquired a service on the specified WCCP client
Recommended Action No action is required.
%WCCP-5-SERVICEMISMATCH : Service [chars][chars][chars] mismatched on WCCP client [chars]
Explanation WCCP has rejected a mismatched service on the specified WCCP client
Recommended Action Amend the WCCP service definition
WEBSERVER
%WEBSERVER-5-LOGIN_FAILED :
Explanation Login unsuccessful
Recommended Action No action is required
%WEBSERVER-5-LOGIN_PASSED :
Explanation Login successful
Recommended Action No action is required
%WEBSERVER-5-SESS_LOGOUT :
Explanation Logout successful
Recommended Action No action is required
%WEBSERVER-5-SESS_TIMEOUT :
Explanation Session Timeout
Recommended Action No action is required
WUILOGIN
%WUILOGIN-2-AUTHENTICATION_SYSTEM_FAILED : WebUI standalone authentication process failed. Reason: [chars]
Explanation During the id and password validation phase of the wuilogin access module authentication attempt, an exception occurred. This message usually occurs as a result of a failure of the underlying PAM authentication module.
Recommended Action Note the time of the error and check the web user interface log (wuilogin-*.log) for additional information on why the attempt to access the web user interface failed.
%WUILOGIN-2-INITIALIZATION_FAILED : WebUI standalone login initialization failed.
Explanation The attempt to access the web user interface using the wuilogin access module failed. The wuilogin access module is used to authenticate web user interface access only when the IOS integrated webserver, which is enabled using the ip http server command, or the IOS process is down or disabled.
Recommended Action Note the time of the error and check the web user interface log (wuilogin-*.log) for additional information on why the attempt to access the web user interface failed.
X
X25
%X25-2-ILLP4 : Interface [chars], Illegal state [chars] when P4
Explanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
%X25-3-ADDRESSBAD : Interface [chars], x25 address [chars] subaddress %c is too long
Explanation This message occurs when a subaddress is configured. When this subaddress is combined with the interface's X.121 address, the total address exceeds the limit of 15 characters.
Recommended Action Reconfigure the subaddress so that this does not happen.
%X25-3-BADCONFIG : Interface [chars], X.25 [chars], current config. retained
Explanation The interface's X.25 configuration is not valid; the existing configuration was not changed.
Recommended Action Verify the following: The interface's switched virtual circuit ranges do not overlap; for nonzero values, lic <= hic < ltc <= htc < loc <= hoc. (For more information, refer to Configuring Virtual Circuit Ranges in the Router Products Configuration Guide.) If an incoming-only range is defined, check that it is numerically less than the two-way range. If an outgoing-only range is defined, check that it is numerically greater than the two-way range. No virtual circuit high/low parameter is zero unless its partner low/high parameter is also zero. The default window sizes are less than the interface modulo.
%X25-3-BADCONFIGATTEMPT : Attempt to [chars].
Explanation The user attempted an illegal configuration.
Recommended Action The error will indicate what illegal action was attempted. The user should check their configuration and if necesarry contact technical support representative for assistance.
%X25-3-COMPERR : Interface [chars] LCI [dec] low-level stac compression error
Explanation A Stacker compression algorithm internal error or shortage of buffer space was encountered during a compression operation. This should never happen.
Recommended Action Report the error to your technical support representative.
%X25-3-ERR_SUBST_XOT_DNS_DEST : Error substituting regular expression for XOT DNS destination pattern
Explanation This message occurs when the regular expression substitute utility fails to arrive at X.25 hostname pattern to be sent to DNS for address resolution
Recommended Action Correct the X.25 route command's DNS substitution pattern
%X25-3-INTIMEQ : Interface [chars], LCN [dec] already in timer queue, new time %#Ta
Explanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
%X25-3-INVCFGID : [dec] is not a valid X.25 configuration ID
Explanation This message occurs when an invalid configuration id is used
Recommended Action LOG_STD_ACTION
%X25-3-LCIBOGUS : in x25_timer NULL lci_idb [hex]
Explanation An internal software error occurred.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
%X25-3-NOLCI : Interface [chars], Delete: lci [dec] not found in [chars] table
Explanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
%X25-3-NOTFINDBH : Can't find bfe host address [IP_address] to delete
Explanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
%X25-3-PROFILENO : profile [chars] does not exist
Explanation This message occurs when an X.25 interface is configured to use an X.25 profile that does not exist
Recommended Action Create and configure the x25 profile using x25 profile <name> global subcommand before referencing the profile.
%X25-3-PVCBAD : Interface [chars], PVC [dec], [chars]
Explanation A switched PVC cannot be connected. The final [chars] text string in the message represents the state of the PVC. These text strings can also appear in show x25-vc output. For more information, refer to the show x25-vc documentation in the Router Products Command Reference publication.
Recommended Action Validate the configuration of the PVCs at both ends of the connection, and reconfigure them if necessary.
%X25-3-SIZEBAD : Interface [chars] LCI [dec] Decompression size error
Explanation An internal software error occurred. The PBP header has an uncompressed packet size field. Each uncompressed packet size is checked against this field.
Recommended Action Contact your technical support representative for assistance.
%X25-3-SPURD1 : Interface [chars], Spurious D1 timer wakeup on LCI [dec]
Explanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
%X25-3-SYNCBAD : Interface [chars] LCI [dec] Decompression sync error. expected [dec] got [dec]
Explanation An internal software error occurred. The PBP header has a sync field. The sync field (8 bits) is checked on each received packet.
Recommended Action Contact your technical support representative for assistance.
%X25-3-TRUNCATE_ALT_XOT_DNS_DEST : Truncating excess XOT addresses ([dec]) returned by DNS
Explanation This message occurs when an X.25 route DNS lookup returns more than the 6 permissible XOT destination addresses
Recommended Action Review the DNS database entries used for XOT destination lookup for possible modification
%X25-3-UNKNOWNPROT : [chars] : Unable to identify lower layer protocol
Explanation IDB is not using X25 and IDB is not capable of supporting CMNS.
Recommended Action Check your hardware configuration or contact your technical support representative for assistance.
%X25-3-VERSIONBAD : Interface [chars] LCI [dec] Compression Version mismatch expected [hex] received [hex]
Explanation An internal software error occurred. The PBP header has a mismatched version field. The version is checked on each received packet.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
%X25-3-X25DEENCINV : [chars]
Explanation This message occurs when deconfiguring X.25 service.
Recommended Action LOG_STD__ACTION
%X25-3-X25ENCINV : [chars]
Explanation This message occurs when configuring an X.25 service.
Recommended Action LOG_STD_ACTION
%X25-3-X25INT : Interface [chars], X.25 internal error [chars]
Explanation This is a general message covering numerous internal X25 error conditions. The message text contains additional details that can be used to identify the problem.
Recommended Action LOG_STD_RECUR_ACTION
%X25-3-X25NOCFG : Profile is not configured
Explanation This message occurs when an X.25 interface is configued to use an X.25 profile that isn't configured
Recommended Action Configure the x25 profile using x25 profile <name> global subcommand before referencing the profile.
%X25-3-X25NOTAVAIL : [chars] : Lower layer protocol is not available
Explanation The required lower layer service is unavailable.
Recommended Action Check your configuration or contact your technical support representative for assistance.
%X25-3-XOTINT : XOT internal error [chars]
Explanation An internal software error occurred.
Recommended Action LOG_STD_ACTION
%X25-3-XOTPROTOCOL : XOT protocol error from [IP_address]: [chars]
Explanation A protocol error was detected over an X.25-over-TCP (XOT) connection, causing the connected VC to close. A flaw may exist in the remote host's XOT implementation.
Recommended Action If this message recurs, call your technical support representative for assistance.
%X25-4-BADMBIT : Interface [chars], VC [dec], partial data packet has M-bit set
Explanation This message occurs when a virtual circuit is set up using the default maximum packet sizes, but the DTE and DCE are not configured with the same default values. A packet was received that had the M-bit set, signifying that more data follows, but the packet did not carry the maximum number of bytes allowed. Such partial data packets must have the M-bit cleared. The resulting loss of a message boundary might cause problems for the data recipient.
Recommended Action Verify the default flow control parameters of the DTE and the DCE. If this message recurs, call your technical support representative for assistance.
%X25-4-BADUPCALL : Interface [chars], Unexpected call ([chars]) from LLC2 DTE=[hex][hex].[hex][hex].[hex][hex].
Explanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
%X25-4-BFEIP : Warning: IP address is missing or incompatible with BFE mode
Explanation An interface configured for X.25 BFE mode does not have an IP address configured, or the IP address does not conform to BFE requirements, so cannot be mapped to an X.121 address.
Recommended Action Please configure a valid Class A IP address for the interface or remove the 'bfe' option from the 'encapsulation x25' command for the interface.
%X25-4-DEBUG_LCI : LCI deleted at interrupt time
Explanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
%X25-4-LARGEPKSIZE : Interface [chars], [chars] packet sizes [dec]/[dec] too large; lower values will be negotiated
Explanation The interface's default packet sizes or outgoing packet size facility values are too large to be carried by Link Access Procedure, Balanced (LAPB).
Recommended Action The router will negotiate lower packet size values automatically. The LAPB N1 value should be increased. For example, for an X.25 maximum packet size of 1024, modulo 8 X.25 operation will add 3 bytes of overhead and modulo 8 LAPB operation will add 4 bytes of overhead (the two bytes of CRC are defined to be included). This means that N1 must be at least 1031 bytes * 8 = 8248.
%X25-4-PARTIALMAP : Interface [chars], [chars] encapsulation call from [chars] partially mapped to [chars]
Explanation An incoming X.25 call specified a protocol that was assigned to a multiprotocol map; the VC will not be able to carry the full set of protocols specified by the map.
Recommended Action Modify the configuration of the router or the far host to match the encapsulation method used.
%X25-4-RANGEUNUSED : Interface [chars], [chars] VC range unused; set limits to zero
Explanation An outgoing-only or incoming-only virtual circuit range exactly overlaps the two-way virtual circuit range. This was the former method for specifying that a virtual circuit range was not used. The current method is to set the range limits to zero.
Recommended Action Use the privileged copy running-config startup-config command to write the configuration to memory. This will store the modified (zero) range limits.
%X25-4-VCLOSTSYNC : Interface [chars], VC [dec] TCP connection [chars]
Explanation An X.25 circuit that is being tunneled over a TCP connection between routers was cleared ungracefully. The last [chars] text string in the message can take one of two forms. If the text string is closed unexpectedly, the router at the remote end of the connection was rebooted, or the connection failed. If the text string is connection corrupted, it is likely that the connection was made to a router running an older software release.
Recommended Action If the text string is closed unexpectedly, reestablish the connection after the remote router or intervening network is operational. If the text string is connection corrupted, upgrade the router at the other end of the connection to a more recent software release.
%X25-4-XOTHOSTWRONG : Wrong host ([IP_address]) for XOT connection to [chars] PVC [dec]; expecting [IP_address]
Explanation This message occurs when an incoming XOT connection identifies a PVC that is configured for a different host IP address, and whose configuration does not permit connection to a different host.
Recommended Action If the host attempting the connection should be allowed, either the remote host should be configured to use a single host address (by adding the xot-source-ifc option), or the local PVC should be configured to accept connections from any host (by using the xot-promiscuous option). If the host attempting the connection should not be allowed, the network administrator should take action appropriate for an attempt to create an unauthorized connection.
%X25-4-XOTPVCDUPLICATE : Duplicated remote PVC data for {[chars], pvc [dec]} and {[chars], pvc [dec]}
Explanation This message identifies two local XOT PVCs that are defined using duplicate specifications for the connecting remote XOT PVC.
Recommended Action This message probably reflects a configuration error; the network administrator should examine the identified PVCs to determine what XOT PVC configuration is required.
%X25-5-NOBUF : Interface [chars] LCI [dec] [chars]
Explanation This is a warning only (the compressed packet was not lost). However, an X.25 packet layer RNR (wait) was generated and packet-level transmission on the LCN will not resume (RR issued) until a decompression buffer becomes available.
Recommended Action If this message occurs frequently, you may need to modify the buffer pool. Copy the message exactly as it appears, and report it your technical support representative.
%X25-5-PBPDBIT : Interface [chars] LCI [dec] PBP Compression does not support X25 D bit
Explanation Compression is not enabled because D-bit support is configured for the LCI.
Recommended Action Reconfigure without D-bit support, or do not attempt to run with compression.
%X25-5-PBPHOLDQ : Interface [chars] LCI [dec] X25 Hold queue needs to be at least default size
Explanation An attempt was made to configure the X.25 hold queue to less than the minimum value.
Recommended Action Configure the X.25 hold queue to be ten or more.
%X25-5-PBPNOEND : Interface [chars] LCI [dec] End system not configured for X25 PBP
Explanation A compression or decompression operation was attempted by a router other than an end router. Only end routers can perform compression and decompression.
Recommended Action Reconfigure the routers so that only the end routers in the network perform compression and decompression.
%X25-7-DIAGEVENT : Interface [chars], X.25 diagnostic event, [chars], lci [dec][chars]
Explanation A standard X.25 diagnostic event has been detected. Per Recommendation X.25 a DCE detecting this will send a Diagnostic packet whereas a DTE cannot. The Recommendation defines diagnostic events for packets occurring on an unassigned channel, receipt of some classes of malformed packets, non-standard usage of channel 0 for Call setup or Data traffic, and some protocol timeout events. An unexpected, but benign, diagnostic event may occur when an attached station doesn't respond to a protocol event soon enough; e.g. a timeout waiting for a response to a Call, Clear or Reset sent. The most common malign cause of a diagnostic event is a mismatched configuration of the logical channel ranges between the DTE and DCE stations.
Recommended Action If an attached station is delaying responses to protocol events, check if the appropriate timeout value is sufficient for expected network behavior, and if the connected station is unduly delaying its response. For unassigned logical channel events, enter the show x25 interface <CmdItalics>id<NoCmdItalics> for the reporting station to verify the logical channel assignments configured are correct and operational. These ranges must match those defined on the connected station; refer to the Setting the Virtual Circuit Ranges section of the Cisco IOS Wide-Area Networking Configuration Guide for more information. For the rare case where logical channel 0 is designated for non-standard Call setup or Data traffic, both stations must be configured to reflect that usage. LOG_STD_RECUR_ACTION
%X25-7-DIAGRX : Interface [chars], X.25 Diagnostic received, [chars][chars]
Explanation An X.25 diagnostic packet has been received at the DTE from the DCE. Per Recommendation X.25, a DCE station must send a Diagnostic packet when it detects a standard diagnostic event, which the DTE must discard with no protocol action taken; a DTE cannot send a Diagnostic packet. Recommendation X.25 defines diagnostic events for packets occurring on an unassigned channel, receipt of some classes of malformed packets, non-standard usage of channel 0 for Call setup or Data traffic, and some protocol timeout events. An unexpected, but benign, Diagnostic packet may be received when the DTE station doesn't respond to a protocol event soon enough; e.g. the DCE timed out waiting for a response to a Call, Clear or Reset. The most common malign cause of a diagnostic event is a mismatched configuration of the logical channel ranges between the two stations.
Recommended Action If an attached station is delaying responses to protocol events, check if the appropriate timeout value is sufficient for expected network behavior, and if the connected station is unduly delaying its response. For unassigned logical channel events, enter the show x25 interface <CmdItalics>id<NoCmdItalics> for the reporting station to verify the logical channel assignments configured are correct and operational. These ranges must match those defined on the connected station; refer to the Setting the Virtual Circuit Ranges section of the Cisco IOS Wide-Area Networking Configuration Guide for more information. For the rare case where logical channel 0 is designated for non-standard Call setup or Data traffic, both stations must be configured to reflect that usage. LOG_STD_RECUR_ACTION
X40G
%X40G-2-TCAM_MGR_CRIT_ERR : GTM ERROR: [chars] ([dec])
Explanation X40G TCAM critical error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%X40G-3-TCAM_MGR_ERR : GTM ERROR: [chars] ([dec])
Explanation X40G TCAM MGR interaction error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%X40G-3-TCAM_MGR_HW_ERR : GTM HW ERROR: [chars] ([dec]) [[dec]:[hex]]
Explanation X40G TCAM hardware error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%X40G-3-TCAM_MGR_HW_PERR : GTM HW ERROR: [chars] ([dec])
Explanation X40G TCAM interface parity error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%X40G-4-TCAM_MGR_ALLOC_ERR : [chars] NP ([dec]), Region Id ([dec])
Explanation NP TCAM entry allocation failure
Recommended Action LOG_STD_SH_CMD_ACTION(remote command module <module#> sh platform software xtcammgr instance <NP#> info)
%X40G-5-TCAM_MGR_INFO : [chars]
Explanation X40G TCAM driver error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
XCONNECT
%XCONNECT-3-CONFIG : [chars]
Explanation An invalid xconnect configuration or an error in processing xconnect configuration has occurred.
Recommended Action No action is required.
%XCONNECT-3-ILLEGAL : [chars]
Explanation An illegal event has been processed by the xconnect subsystem.
Recommended Action No action is required.
%XCONNECT-5-PW_STATUS : [chars]
Explanation An event has occurred that has caused the pseudowire to change status
Recommended Action No action is required.
%XCONNECT-5-PW_STATUS_LOST : [chars]
Explanation The system is dropping PW_STATUS messages because the status queue is full
Recommended Action No action is required.
%XCONNECT-5-REDUNDANCY : [chars]
Explanation An event has occurred that has caused the xconnect redundancy facility to generate a switchover event to the specified backup member
Recommended Action No action is required.
XDR
%XDR-3-BADSEQVAL : Incorrect maximum sequence calculated ([dec], was [dec]) for slot [chars] with [dec] out of [dec] buffers available
Explanation Internal software error. May result in unpredictable behaviour.
Recommended Action LOG_STD_SH_CMD_ACTION(show xdr linecard)
%XDR-3-BYPASSFOFNEGO : Bypassing FOF ISSU client [chars] ([int]) nego for XDR client [chars], slot [chars] as FOF ISSU client is not present in [chars] image.
Explanation This XDR client has a dependency on another ISSU client due to having foreign-owned-fields. As the ISSU client that owns the foreign-owned fields is not in the image the XDR client will not wait for that client to finish ISSU negotiation. Appearance of this error message indicates that work is required to add the missing client to the image.
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative.
%XDR-3-CLIENTISSUBADGROUP : New m/cast group (slots [chars]) has multiple members before nego complete.
Explanation A new multicast group has been created with multiple slots before ISSU negotiation for each client has completed. This will lead to unpredictable results.
Recommended Action Get the output of show xdr multicast, show xdr client all and show issu message types [XDR client ISSU ID]. Copy the message exactly as it appears, and report it to your technical support representative.
%XDR-3-CLIENTISSUBADNEGOMSG : Unexpected nego msg -slot [chars], XDR client [chars], ctxt [dec]
Explanation XDR has received a negotiation message unexpectedly as this client is either not ISSU aware or has already completed negotiation for this slot. This is likely a precursor to unpredictable behaviour for this client.
Recommended Action Get the output of show xdr multicast, show xdr client all and show issu message types [XDR client ISSU ID]. Copy the message exactly as it appears, and report it to your technical support representative.
%XDR-3-CLIENTISSU_FOF_NEGOFAIL : ISSU negotiation failed for FOF client [int], for peer [chars] (ISSU peer [dec]), blocking ISSU client [chars] ([dec]) reason -[chars]
Explanation ISSU negotiation failed for a client which has registered ISSU FOF client dependencies. The dependent clients on this and the remote slot cannot interoperate in SSO mode. Syncing of information to/from this slot will not happen for this and the dependent clients. See output of show xdr multicast for full details.
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative.
%XDR-3-CLIENTISSU_FOF_REGERROR : ISSU client [chars] ([dec]), entity [dec], message [dec] ([chars]), failed ISSU FOF registration: [chars], reason: [chars],
Explanation This ISSU client has a message containing a foreign field owned by another client and failed to register this dependency.
Recommended Action This error indicates a potential coding problem. It is an error that may occur every time this image is run, and may require a code change to fix it.
%XDR-3-CLIENTISSUNEGATIVEPADDING : Negative padding for [chars], slots [chars], msg [dec] (padded: [dec], unpadded: [dec])
Explanation Internal error. Mismatch of internal data structures.
Recommended Action Get the output of show xdr multicast, show xdr client all and show issu message types [XDR client ISSU ID]. Copy the message exactly as it appears, and report it to your technical support representative.
%XDR-3-CLIENTISSU_NEGOFAIL : ISSU negotiation failed for XDR client [chars], slot [chars], reason: [chars]
Explanation ISSU negotiation failed. This XDR client on this and the remote slot cannot interoperate in SSO mode. Syncing of information to/from this slot will not happen for this and dependent clients. See output of show xdr multicast for full details.
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative.
%XDR-3-CLIENTISSUNEGONOTDONE : Attempting to push send XDR message ([dec]) to slots [chars] for [chars] before nego complete.
Explanation Internal error. May result in unpredictable behaviour.
Recommended Action Get the output of show xdr multicast, show xdr client all and show issu message types [XDR client ISSU ID]. Copy the message exactly as it appears, and report it to your technical support representative.
%XDR-3-CLIENTISSU_NEGOREGERROR : XDR client [chars], failed ISSU negotiation result notification registration for ISSU client [chars] ([dec]), reason: [chars],
Explanation This client has dependency on the succesful ISSU negotiation of another client and failed to register this dependency
Recommended Action This error indicates a potential coding problem. It is an error that may occur every time this image is run, and may require a code change to fix it.
%XDR-3-CLIENTISSU_NEGOUNREGERROR : Failed to unregister ISSU negotiation result notification registration for ISSU client [chars] ([dec]), reason: [chars],
Explanation This client has dependency on the succesful ISSU negotiation of another client and failed to unregister this dependency when not required.
Recommended Action This error indicates a potential coding problem. It is an error that may occur every time this image is run, and may require a code change to fix it.
%XDR-3-CLIENTISSUNOMSGGRP : Cannot determine ISSU message group for slot [dec]. Unknown [chars]
Explanation Not able to determine the set of ISSU messages to be used between local and remote slot, due to not being able to determine linecard type for one or other slot. This might be due to a new linecard type.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%XDR-3-CLIENTISSU_PUSHFAIL : Attempting to push send XDR message ([chars]) to slots [chars] via XDR client [chars] failed due to [chars][chars]
Explanation Internal error. May result in unpredictable behaviour.
Recommended Action Get the output of show xdr multicast, show xdr client all and show issu message types [XDR client ISSU ID]. Copy the message exactly as it appears, and report it to your technical support representative.
%XDR-3-CLIENTISSU_REGERROR : 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.
%XDR-3-CLIENTISSUSENDFAILED : Can't send XDR client ISSU nego msg: reason [chars], slot [chars], XDR client [chars]
Explanation XDR has failed to send an ISSU negotiation message for the given client. The slot will be marked as ISSU-unaware, and communication with this slot will proceed on that basis. However, this is likley to lead to unpredictable behaviour.
Recommended Action Get the output of show xdr multicast, show xdr client all and show issu message types [XDR client ISSU ID]. Also copy the message exactly as it appears, and report it to your technical support representative.
%XDR-3-CLIENTISSUSTARTNEGOFAIL : Can't start nego: reason [chars], slot [chars], XDR client [chars], sid [dec]
Explanation XDR has failed to start ISSU negotiation with the remote slot for the reason given. The slot will be marked as ISSU-unaware, and communication with this slot will proceed on that basis. However, this is likley to lead to unpredictable behaviour.
Recommended Action Get the output of show xdr multicast, show xdr client all and show issu message types [XDR client ISSU ID]. Also copy the message exactly as it appears, and report it to your technical support representative.
%XDR-3-DATA_TOO_LARGE : Data length [dec] exceeds limit of [dec] bytes
Explanation An attempt was made by a client to send XDR data that was over the given length limit, which caused the send to fail.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%XDR-3-FRAG_CLIENT_NOT_ALLOWED : Received an XDR fragment from client [chars], slot [chars], which is not allowed to send fragments
Explanation Certain clients are restricted by XDR from fragmenting their data, yet such a fragment was received received.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start, or contact your Cisco technical support representative and provide the representative with the gathered information.
%XDR-3-ILLEGAL_CAP_TYPE : Illegal ISSU capability type ([dec]) for XDR client [chars]
Explanation Capability type requested is invalid. The named XDR client may not function as expected.
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative.
%XDR-3-ILLEGAL_CAP_VALUE_CHANGE : ISSU capabilities for peers running same IOS version must be supported.
Explanation Basic assumption is that all peers running the same IOS version as the active RP will support the same ISSU capabilities as the active RP. This is an attempt to mark one such peer as not supporting all capabilities. This will break assumptions in XDR ISSU code and cannot be allowed. The traceback will indicate the offending XDR client.
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative.
%XDR-3-ISSUBADREGPARAMS : XDR client [chars] trying to register with incomplete ISSU support.
Explanation This client does not properly support ISSU and will be registered as not supporting ISSU.
Recommended Action We cannot allow a client to register with partial ISSU support so it will be registered without it. Please report this message to your technical support representative.
%XDR-3-ISSUCAPNEGOFAIL : XDR client [chars] failed to [chars] capability/ies due to [chars]
Explanation Internal software error - capability negotiation failed unexpectedly.
Recommended Action Copy the message exactly as it appears and report it to your technical support representative
%XDR-3-ISSU_ENUM_ERROR : Enum for [chars] ([chars] component) 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.
%XDR-3-ISSUINITFAIL : Unable to register XDR ISSU [chars], reason: [chars]
Explanation Unable to register the given XDR ISSU parameter due to the reason given. This will stop ISSU working for this client and may lead to unpredictable behaviour.
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative.
%XDR-3-ISSU_NEGOFAIL : ISSU negotiation failed for XDR, slot [chars], reason: [chars]
Explanation ISSU negotiation failed. XDR on this and the remote slot cannot interoperate. Syncing of information to/from this slot for all XDR clients will not be allowed.
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative.
%XDR-3-MISMATCHED_ISSU_CAPABILITY_INFO : [chars]: [chars]
Explanation ISSU-aware XDR clients may have capabilities to negotiate. They can ask XDR to manage the state of these, but must provide all relevant supporting functions to do so. In this case, the given client has not done so.
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative.
%XDR-3-MSGSIZEFAIL : The IPC message size is out of bounds The ipc_msg_size is : [dec] while the maximum size we can handle is the XDR_IPC_BUFFER_SIZE : [dec] .
Explanation The size of the IPC message that was received is out of bounds
Recommended Action We were not meant to get the IPC message we did. The size of the IPC message is larger than the maximum size that can be handled. This is probably due to communication incompatibility issues between the active and the standby RPs. Please report it to your technical support representative.
%XDR-3-NONINCRSEQ : Non-increasing maximum sequence ([dec], was [dec]) received from slot [chars]
Explanation Internal software error. May result in unpredictable behaviour.
Recommended Action LOG_STD_SH_CMD_ACTION(show xdr linecard)
%XDR-3-ONINT : Invalid operation [chars] at interrupt level by XDR client [chars]
Explanation Invalid operation at interrupt level
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative.
%XDR-3-PRIOCLIENTISSU_NEGOFAIL : ISSU negotiation failed for XDR client [chars], slot [chars], reason: [chars]
Explanation ISSU negotiation failed for a core XDR client. XDR on this and the remote slot cannot interoperate in SSO mode. Syncing of information to/from this slot will not happen for any XDR client.
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative.
%XDR-3-PULLSENDFAIL : Sending data for pull client [chars] to [chars] failed due to slot(s) [chars] not being in group [hex] of slot(s) [chars]
Explanation Data sending for an XDR pull client failed for the reason specified. The data was not sent.
Recommended Action LOG_STD_SH_CMD_ACTION(show xdr multicast-group)
%XDR-3-XDRIPC : XDR IPC error on multicast-group [hex] due to [chars].
Explanation A general IPC related error occurred which may prevent transfer of data to other peers using the IPC mechanism
Recommended Action Get the output of show xdr multicast immediately after this error. Copy the message exactly as it appears, and report it to your technical support representative.
%XDR-3-XDRMCASTGRPINVALID : Invalid XDR multicast group for slot(s) [chars]: [chars]
Explanation Internal error. May result in unpredictable behaviour.
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative.
%XDR-3-XDRMCASTJOIN : Attempt to join [chars] to [chars] failed because client [chars] returned an error
Explanation Internal error. May result in unpredictable behaviour.
Recommended Action Get the output of show xdr multicast, show xdr client all and show monitor event-trace xdr all. Copy the message exactly as it appears, and report it to your technical support representative.
%XDR-3-XDRMCASTJOINREQ : Client [chars] returned an invalid response to a join request for groups [chars] and [chars]
Explanation Internal error. May result in unpredictable behaviour.
Recommended Action Get the output of show xdr multicast, show xdr client all and show monitor event-trace xdr all. Copy the message exactly as it appears, and report it to your technical support representative.
%XDR-3-XDRMCAST_PEER_BINDING : XDR peer [chars] bind to group [chars] (was bound to [chars]): [chars]
Explanation Internal error. May result in unpredictable behaviour.
Recommended Action Get the output of show xdr multicast, and show monitor event-trace xdr all. Copy the message exactly as it appears, and report it to your technical support representative.
%XDR-3-XDRNOMEM : XDR failed to allocate memory during [chars] creation.
Explanation Allocation of memory by the XDR subsystem failed. This may result in an unpredictable behavior of XDR
Recommended Action Make sure that there is enough memory for the operations being performed by your machine. Copy the message exactly as it appears, and report it to your technical support representative.
%XDR-3-XDROOS : Received an out of sequence IPC message. Expected [dec] but got [dec] from slot [chars].
Explanation An out of sequence IPC message was received
Recommended Action We weren't meant to get the IPC message we did. From this point onwards IPC can't be relied on. Copy the message exactly as it appears, and report it to your technical support representative.
%XDR-4-FAILATTEMPTOPENIPCPORT : Attempt to open the IPC ports failed. [chars]
Explanation XDR failed an attempt to open the IPC port to communicate to the specified peer
Recommended Action No action is required.
%XDR-6-CLIENTISSUBADRCVTFM : Failed to rcv_transform message -from slot [chars], XDR client [chars], context [dec]
Explanation Cannot perform ISSU receive transform. This is likely due to a failure in negotiation earlier, or when one side of an ISSU-enabled XDR connection is out of sync with the other.
Recommended Action Get the output of show xdr multicast, show xdr client all and show issu message types [XDR client ISSU ID]. Copy the message exactly as it appears, and report it to your technical support representative.
%XDR-6-CLIENTISSUBADTXTFM : Failed to xmit_transform message -to slot [chars], XDR client [chars], context [dec]
Explanation Cannot perform ISSU transmit transform. This is likely due to a failure in negotiation earlier, or when one side of an ISSU-enabled XDR connection is out of sync with the other.
Recommended Action Get the output of show xdr multicast, show xdr client all and show issu message types [XDR client ISSU ID]. Copy the message exactly as it appears, and report it to your technical support representative.
%XDR-6-CLIENTISSUUNREG : Failed to unregister session -XDR client [chars], slot [chars], reason [chars]
Explanation Unable to unregister this session. This will likely cause problems when reregistering and should be reported.
Recommended Action Get the output of show xdr multicast, show xdr client all and show issu message types [XDR client ISSU ID]. Copy the message exactly as it appears, and report it to your technical support representative.
%XDR-6-CLIENTNOTREGONRP : Client [chars] has registered on slot [chars] before RP.
Explanation XDR client has registered on non-RP card before RP card. If this has occurred while toggling the client's registration status rapidly then it may be a transient problem and will resolve itself. If not, then the client's status may be unpredictable, and ISSU negotiation (if platform is ISSU-aware) may not take place correctly.
Recommended Action Verify whether the client's registration status is the same on both the RP and the card on which the problem is reported by comparing the output of 'show xdr client all' to see if the client is present or absent in BOTH. If so, and no other error messages have been seen, then this is a transient issue and no further action is required. Otherwise, copy the message exactly as it appears, and report it to your technical support representative.
%XDR-6-ISSUBADRCVTFM : Failed to rcv_transform message -slot [chars], reason: [chars]
Explanation Unable to perform ISSU transform on incoming XDR header. Message will be ignored
Recommended Action Get the output of show xdr multicast, show xdr client all and show issu message types [XDR client ISSU ID]. Copy the message exactly as it appears, and report it to your technical support representative.
%XDR-6-ISSUBADTXTFM : Failed to xmit_transform message -slot [chars], reason [chars]
Explanation Unable to perform ISSU transform on outgoing XDR header. Message will be ignored
Recommended Action Get the output of show xdr multicast, show xdr client all and show issu message types [XDR client ISSU ID]. Copy the message exactly as it appears, and report it to your technical support representative.
%XDR-6-ISSUCLIENTABSENT : XDR client [chars] absent on slot [chars]. Client functionality may be affected.
Explanation The remote slot doesn't support this ISSU client. The software will handle this by reducing client functionality locally to continue in SSO mode, or by forcing the remote peer into RPR mode as apprporiate. This is expected behaviour in ISSU-capable systems.
Recommended Action No action required. This message just indicates that certain functionality may be reduced due to running different images together.
%XDR-6-XDRDISABLEREQUEST : Peer in slot [chars] requested to be disabled due to: [chars]. Disabling linecard
Explanation Due to some error condition the linecard has requested to be disabled
Recommended Action Execute clear xdr linecard from the RP followed by clear xdr channel on the linecard in question to clear the error condition. If the problem persists get the output of show monitor event-trace xdr all from the RP and the linecard in question and report it to your technical support representative.
%XDR-6-XDRINVALIDHDR : XDR for client ([chars]) dropped (slots:[chars] from slot:[chars] context:[int] length:[int]) due to: [chars]
Explanation The XDR message was dropped for the reason given.
Recommended Action If the failure was due to an invalid context for the CEF push client and occurred during an ISSU upgrade then it may be safely ignored. Otherwise: LOG_STD_ACTION
%XDR-6-XDRINVALIDHDRISSU : XDR ISSU negotiation message for client ([chars]) dropped (slots:[chars] from slot:[chars] context:[int] length:[int]) due to: [chars]
Explanation The XDR ISSU negotiation message was dropped for the reason given.
Recommended Action If the message occurred during an ISSU upgrade then it may be safely ignored. Otherwise: LOG_STD_ACTION
%XDR-6-XDRIPCPEER : XDR IPC error occurred for peer in slot [chars] due to [chars][chars].
Explanation A general IPC related error occurred which may prevent transfer of data to other peers using the IPC mechanism
Recommended Action Get the output of show xdr multicast and show xdr linecard immediately after this error. Copy the message exactly as it appears, and report it to your technical support representative.
%XDR-6-XDRLCDISABLEREQUEST : Client [chars] requested to be disabled. [chars]
Explanation Due to some error condition the linecard has requested to be disabled
Recommended Action Execute clear xdr linecard from the RP followed by clear xdr channel on the linecard in question to clear the error condition. If the problem persists get the output of show monitor event-trace xdr all from the RP and the linecard in question and report it to your technical support representative.
%XDR-6-XDRMCASTINIT : XDR mcast subsystem initilisation error: [chars]
Explanation XDR non functional.
Recommended Action A failure occured which prohibits the XDR client from registering with the core. Copy the message exactly as it appears, and report it to your technical support representative.
%XDR-6-XDRREGISTRATION : XDR failed to register [chars] client due to [chars]
Explanation Failure to register the said XDR client.
Recommended Action A failure occured which prohibits the XDR client from registering with the core. Copy the message exactly as it appears, and report it to your technical support representative.
Z
ZONE
%ZONE-4-API : Zone [chars] [chars][chars] [chars] failed to notify the data plane
Explanation The notification of a zone operation has failed to update the data plane and as such the application of the zone information 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 zone rendering the configuration inconsistent in terms of application.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show memory command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%ZONE-4-LICENSE : License smart enable and zone-license enable should be enabled first
Explanation The notification indicates that zone smart license should be enabled
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show running command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
%ZONE-6-CONFIG : Zone security [chars] is removed due to VRF config change on interface [chars]
Explanation The notification of a zone is removed from an interface due to a vrf is removed from the interface
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the tools at https://cway.cisco.com/go/sa/. Issue the show running command to gather data that may help identify the nature of the error. Also perform a search using the Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center: https://mycase.cloudapps.cisco.com/start , or contact your Cisco technical support representative and provide the representative with the gathered information.
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information, see What’s New in Cisco Product Documentation.
To receive new and revised Cisco technical content directly to your desktop, you can subscribe to the What’s New in Cisco Product Documentation RSS feed. The RSS feeds are a free service.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Copyright ©2018, Cisco Systems, Inc.
All rights reserved. Printed in USA.
FeedbackContact Cisco
- Open a Support Case
- (Requires a Cisco Service Contract)