Downloads |
 Feedback
|
Table Of Contents
AAA Messages
Error Message%AAA-2-AAAMULTILINKERROR : [chars]([hex]): Acct db for Id [hex] absent
Explanation An AAA internal error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AAA-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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%AAA-3-ACCT_IOMEM_LOW : AAA ACCT process suspended : low I/O memory
Explanation AAA ACCT process has been suspended due to insufficient IO memory.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.
Error Message%AAA-3-ACCT_LOW_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 not enough processor memory. All queued accounting requests will be trashed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.
Error Message%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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.
Error Message%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. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AAA-3-AUTHORMLISTUNDEF : Authorization method list '%s' 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.
Error Message%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, thus returning failure.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.
Error Message%AAA-3-BADCURSOR : invalid cursor index %d max %d service %s protocol %s
Explanation A AAA client has provided an invalid attribute cursor to AAA.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%AAA-3-BADHDL : invalid hdl AAA ID %u, hdl %x, %s
Explanation A AAA client has provided an invalid attribute list handle to AAA.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%AAA-3-BADLIST : invalid list AAA ID %u
Explanation A AAA client has provided an invalid attribute list to AAA.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.
Error Message%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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.
Error Message%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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.
Error Message%AAA-3-BADPROTOCOL : Unknown protocol %u
Explanation The AAA subsystem encountered an unknown protocol type.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%AAA-3-BADSERVERTYPEERROR : Cannot process [chars] server type [chars]
Explanation A method list function encountered a server type that was unknown, or could not be handled. This may be due to a server misconfiguration.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AAA-3-BADSERVICE : Unknown service %u
Explanation The AAA subsystem encountered an unknown service type.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%AAA-3-BUFFER_OVERFLOW : Radius I/O buffer has overflowed
Explanation An unusually large number of RADIUS attributes has caused AAA to overflow its RADIUS I/O buffer.
Recommended Action This is an internal software error. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%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 exhausts all its retries and retransmission. The cause for this might be the servers are not 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 this message recurs, copy the message exactly as it appears on the console or in the system log. Enter the show running-config command to gather information that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.
Error Message%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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%AAA-3-HA_INTERNAL_ERROR : High availability internal error for unique id [hex]: [chars]
Explanation The AAA subsystem has 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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%AAA-3-IPILLEGALMSG : Invalid use of ip_pid([int])
Explanation This error means a process sent an illegal message.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Enter the Show tech-support command to gather information that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%AAA-3-ISDNINTF : [chars] [chars]: cannot apply configuration to ISDN channel: '[chars]'
Explanation Configuration cannot 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.
Error Message%AAA-3-LOW_MEM : [chars] process is unable to handle the incoming packet due to low memory
Explanation Check the processor memory or IO memory. Most likely one of them has less available memory or, worst case, both may have insufficient memory.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%AAA-3-MLIST_INTERNAL_ERROR : method list '%s': %s
Explanation This is an internal software error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%AAA-3-MLIST_TOO_MANY_METHODS : method list '[chars]'
Explanation 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 did not find one, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%AAA-3-NOTABLE : AAA ID %u
Explanation Resource failure.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%AAA-3-NULLCURSOR : Null cursor
Explanation A AAA client has provided a nonexistent attribute cursor to AAA.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%AAA-3-NULLVRF : Null vrf entry
Explanation A NULL VRF entry was found while comparing the AAA VRF attributes.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%AAA-3-PARSEERR : Error([dec]) parser is unable to parse [chars] per-user command
Explanation All attempts to parse 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. Enter the debug peruser command and repeat the steps that caused the error. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%AAA-3-SERVER_INTERNAL_ERROR : Server '[IP_address]': [chars]
Explanation 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 did not find one, copy the message exactly as it appears on the console or in the system log. Enter the Show tech-support command to gather information that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%AAA-3-SG_DEADTIME_FORKFAIL : Failed to fork process for [chars].
Explanation Quite likely, it ran out of memory. Other explanations are possible.
Recommended Action This is an internal software error. Check bug toolkit on Cisco website for the issue. If you did not find one, copy the message exactly as it appears on the console or in the system log. Enter the Show tech-support command to gather information that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%AAA-3-SG_INTERNAL_ERROR : server group '[chars]': [chars]
Explanation 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 did not find one, copy the message exactly as it appears on the console or in the system log. Enter the Show tech-support command to gather information that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%AAA-3-SG_TESTPROC_FORKFAIL : Failed to fork process for [chars].
Explanation Quite likely, it ran out of memory. Other explanations are possible.
Recommended Action This is an internal software error. Check bug toolkit on Cisco website for the issue. If you did not find one, copy the message exactly as it appears on the console or in the system log. Enter the Show tech-support command to gather information that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%AAA-3-SORTFAIL : %s :Peruser Could not sort the %s attributes
Explanation Sorting of the attributes received from AAA server failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%AAA-5-USER_LOCKED : User [chars] locked out on authentication failure
Explanation The user was locked out because the number of authentication failures exceeded the configured threshold.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%AAA-5-USER_RESET : User [chars] failed attempts reset by [chars]
Explanation The number of failed user authentication attempts has been reset to zero.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%AAA-5-USER_UNLOCKED : User [chars] unlocked by [chars]
Explanation The user has been unlocked by the system administrator. The user is enabled to log in to the system.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter at https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%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. No action is required.
Error Message%AAA-6-BADHDL : invalid hdl AAA ID [int], hdl [hex], [chars]
Explanation An AAA client has provided an invalid attribute list handle to AAA.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.
Error Message%AAA-6-INVALIDROUTE : Syntax error in route statement: [chars]
Explanation Current downloading route contains syntax error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%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, you need connectivity with modems supporting V.92 modem standards. If there is no modem, there would not be any TTY, without which MOH attributes cannot be used.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.AAAA Messages
Error Message%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.
Error Message%AAAA-3-ACCTATTR : last accounting attribute:
Error Message%AAAA-3-ACCTDUMP : dump of accounting data:
Recommended Action .
Error Message%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.
Error Message%AAAA-3-BADARG : %% AAA: bad argument (%0#4x)
Explanation We tried to NVGEN a non-existent AAA command.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%AAAA-3-BADAUTHENSTR : Bad authentication data: %s
Error Message%AAAA-3-BADCOMM : Trying config command but should not be.
Explanation An internal error has occurred
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%AAAA-3-BADLIST : %% AAA: bad %s list %s
Explanation One of the AAA methods does not seem to have a list associated with it.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%AAAA-3-BADMETHNAME : Bad [chars] method-list name '[chars]' rejected
Explanation A method-list name should not be the same as a method name. Please choose a different name for the method list.
Recommended Action Pick a different method-list name, that is not also a method-name.
Error Message%AAAA-3-BADREG : Illegal registry call.
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.
Error Message%AAAA-3-BADSTATE : %% AAA: Bad state for %s list name (%d)
Explanation A AAA method list is neither default nor named. This is bad.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%AAAA-3-BADSTR : Bad accounting data: %s
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.
Error Message%AAAA-3-DLRFORKFAIL : Failed to fork process for %s.
Explanation Quite likely, we ran out of memory. Other explanations are possible.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%AAAA-3-DROPACCTFULLQ : Accounting record dropped due to a full aaa accounting queue: %s-%s %s %s
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.
Error Message%AAAA-3-DROPACCTLOWMEM : Accounting record dropped due to low memory: %s-%s %s %s
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.
Error Message%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 If periodic accounting is on, disable it by entering the [no] aaa accounting update newinfo periodic interval command.
Error Message%AAAA-3-DROPACCTSNDFAIL : Accounting record dropped, send to server failed: %s-%s %s %s
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.
Error Message%AAAA-3-ILLEGALNAME : Illegal %s %s name %s rejected
Explanation A method-list name should not be the same as a method name. Please choose a different name for the method list.
Recommended Action Pick a different method-list name, that is not also a method-name.
Error Message%AAAA-3-ILLSGNAME : Illegal server-group name %s (type %s).
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: %s
Explanation This is an internal software error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%AAAA-3-INTERNAL_ERROR : [chars]
Explanation This is an internal software error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.
Error Message%AAAA-3-INVALIDLIST : %% AAA: invalid %s list %d.
Explanation One of the AAA methods lists has inconsistent settings
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%AAAA-3-INVSTATE : %s AUTHOR/%s: Internal state is invalid: astruct 0x%x ustruct 0x%x
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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%AAAA-3-LISTCREATE : The list %d for %s 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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%AAAA-3-MKTIMERFAIL : Failed to create periodic accounting timer for user %s. 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.
Error Message%AAAA-3-MKTIMERINVALID : Invalid request to create periodic accounting timer for user %s. 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.
Error Message%AAAA-3-NOADMINPROC : %s
Explanation Administrative process has been enabled but somehow could not run
Recommended Action .
Error Message%AAAA-3-NOADMINSOC : %s
Explanation socket setup for the administrative process failed, process exitting
Recommended Action .
Error Message%AAAA-3-NOFREELISTS : %% AAA: No free %s lists for %s
Explanation You have reached the maximum number of possible authentication lists for this method.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%AAAA-3-NOLIST : %s: no method list-name.
Explanation An internal software error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%AAAA-3-NOREG : %s method %d has no registry!
Explanation An internal error has occurred
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show acr all command and your pertinent troubleshooting logs.Error Message%AAAA-3-NOSERV : No name for servergroup in method %s
Explanation An internal error has occurred
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%AAAA-3-NOSG : No server-group passed through parser.
Explanation An internal error has occurred
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%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.
Error Message%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.
Error Message%AAAA-3-OVERWRITE : Overwrote internal buffer space %s
Explanation An internal software error.
Recommended Action Report to tac@cisco.com.
Error Message%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.
Error Message%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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%AAAA-3-RELOGIN : sanity check in re-login %s to %s
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.
Error Message%AAAA-3-SGDUPFREE : Duplicate free of server group 0x%x
Explanation This is an internal software error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%AAAA-3-STRCREATE : str_create overwrote its internal buffer.
Explanation An internal buffer, used to assemble a string, was exceeded, thus possibly corrupting other memory.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%AAAA-3-SUBTYPE : Bad Subtype %d for %s (%d)
Explanation An internal software error.
Recommended Action Report to tac@cisco.com.
Error Message%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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%AAAA-4-BADMETHNAME : Bad [chars] method-list name '[chars]' (this is only a warning)
Explanation A method list name should not be the same as a method name.
Recommended Action Choose a different method list name that is not also a method name.
Error Message%AAAA-4-BADSGNAME : Bad server-group name [chars] (type [chars]).
Explanation Either the given server-group name does not exist or the given type does not match the defined server group.
Recommended Action Verify that the group exists and that the type is accurate.
Error Message%AAAA-4-BADSGTYPE : Server-group [chars] is not of type [chars].
Explanation The specified server group name does not match the specified type.
Recommended Action Verify that the group exists and that it is of the same type.
Error Message%AAAA-4-DNISGPUNDEF : Warning: DNIS group [chars] is not defined.
Explanation The DNIS group was used without being defined.
Recommended Action Define the DNIS group before using it.
Error MessageExplanation The DNIS group was used without defining it first. It should be defined before use.
Recommended Action Define the DNIS group before using it.
Error Message%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.
Error Message%AAAA-4-NOSERVER : Warning: Server [IP_address] is not defined.
Explanation The specified server is not on the master list and should be defined, or unexpected results may occur.
Recommended Action Define the server on the appropriate master list as soon as possible.
Error Message%AAAA-4-SERVNOGRP : Warning: Server [IP_address]:[dec],[dec] is not part of server group [chars].
Explanation The specified server does not belong to the specified server group.
Recommended Action Check that the specified server belongs to the server group.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error MessageExplanation The server does not belong to the specified server group
Recommended Action Please check that the specified server belongs to the server group
Error Message%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 does not support the configured AAA action.
Recommended Action Use a radius server-group.
Error Message%AAAA-4-SERVNOTACPLUS : The server-group %s is not a tacacs+ server group. Please define %s 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.
Error Message%AAAA-4-SERVUNDEF : The server-group %s 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.
Error Message%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
Error Message%AAAA-6-ACCTSTART : %s
Explanation A AAA accounting start message.
Recommended Action This information is for information only.
Error Message%AAAA-6-ACCTSTOP : %s
Explanation A AAA accounting stop message.
Recommended Action This information is for information only.
Error Message%AAAA-6-ACCTWATCH : %s
Explanation A AAA accounting watchdog/update message.
Recommended Action This information is for information only.
Error Message%AAAA-6-ADMINMSG : %s %s: %s
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
Error Message%AAAA-6-SERVERMSG : %s %s: %s
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.
AAA_CACHE Messages
Error Message%AAA_CACHE-3-NULL_TREE_PERIODIC_PROC : Cache Tree pointer is of null value
Explanation The cache tree pointer is of null value.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
AAL5 Messages
Error Message%AAL5-1-NOBUFFER : [chars]: No buffer available for size [dec] bytes
Explanation No memory is available for buffer allocation.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AAL5-1-NOMEMORY : [chars]
Explanation No memory is available for allocation from heap. The error message contains text that can be used to help identify the nature of the problem.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AAL5-2-INTERNAL_CRITICAL : [chars]
Explanation The AAL5 datapath has encountered a critical software error. The error message contains text which can be used to help identify the nature of the problem.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AAL5-3-INTERNAL_ERROR : [chars]
Explanation The AAL5 datapath has encountered an internal software error. The error message contains text which can be used to help identify the nature of the problem.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AAL5-3-NOBUFFER : %s, vpi %d, vci %d
Recommended Action .
Error Message%AAL5-3-PAK : Flow Hdr: ([dec]) [chars]
Explanation Either the AAL5 data path has received a large packet that is cannot process, or no more buffers are available. The packet has been dropped. The error message contains text that can help identify the nature of the problem
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AAL5-3-RXERR : Flow Hdr: ([dec]) [chars]
Explanation The AAL5 datapath has received a packet with AAL5 checksum error. packet has been dropped. The error message contains text that can help identify the nature of the problem.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AAL5-3-RXERR_PAKTYPE : Input Interface [chars]: [chars]
Explanation The AAL5 data path has received a packet with an invalid encapsulation for the type of packet (for example, DATA or CNTL). The packet has been dropped. The error message contains text that can help identify the nature of the problem.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
AC Messages
Error Message%AC-3-ACMGR_INVALID_HDL : Received invalid [chars] handle
Explanation The Attachment Circuit Manager has recieves an invalid handle.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AC-3-ACMGR_INVALID_MSG : Received [chars]
Explanation The Attachment Circuit manager has received an invalid message.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AC-3-ACMGR_MISSED_CIRCUIT : Circuit info missing in [chars] message.
Explanation The Attachment Circuit manager has received message with missing circuit information.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AC-3-AC_PROVISION : [chars]
Explanation An error was encountered during Attachment Circuit provisioning or unprovisioning.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AC-3-AC_SUBBLOCK : [chars]
Explanation An error was encountered during Attachment Circuit sub-block creation or removal.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AC-3-AC_SANITY : [chars]
Explanation An unexpected sanity check failed during the Attachment Circuit processing.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AC-3-AC_VECTOR : [chars]
Explanation An error was encountered during the configuration of the Attachment Circuit that caused problems in the setting or restoration of the interface vectors.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AC-3-L2SS_BAD_HANDLE : Corrupted L2SS handle [[hex]].
Explanation An internal L2SS Manager has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AC-3-L2SS_NULL_CONTEXT : Encountered a NULL context in [chars]
Explanation Encountered a NULL context in L2SS Manager.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AC-3-L2SS_UNEXPECTED : Received unexpected [chars] message
Explanation L2SS recieve unexpected message.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AC-3-L2SS_WRONG_KEYS : Wrong set of keys in [chars] message
Explanation The SIP sends a wrong set of keys to L2SS Manager.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
ACCESS Messages
The following are Access IE messages.
Error Message%ACCESS_IE-3-INVALID_HANDLE : Caller passed in invalid handle - traceback to follow.
Explanation An invalid handle was encountered in the Access IE library.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
ACE Messages
The following are Access Control Encryption messages.
Error Message%ACE-2-CRYPTOENGERR : Crypto engine error: [chars] ([dec])
Explanation A crypto engine operation did not complete.This error condition can indicate that the crypto enginecannot bind or unbind an interface to a crypto engine.It can also indicate that the crypto engine cannot queryan interface ID.
Recommended Action Remove the cryptomap set from the interface by issuing no crypto map command. Then reattach the cryptomap set to the interface using crypto map command. Although removing and reattaching the crypto map might fix the cryptographic engine operation failure, report the failure to your technical support representative along with the sequence of commands that lead to the failure
Error Message%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
Error Message%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.
Error Message%ACE-3-CEAL_REGISTRATION : ACE [chars] failed to register.
Explanation The ACE failed to register with CEAL.
Recommended Action Reset the hardware module.
Error Message%ACE-3-CRASHDUMPERR : [chars]: crashdump retrieval error: [chars] [chars]
Explanation An error occurred during crashdump file retrieval from ACE.
Error Message%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 technicalsupport representative.
Error Message%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.
Error Message%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.
Error Message%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.
Error Message%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
Error Message%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.
Error Message%ACE-3-OUTOFID_RL : Too may [chars] IDs in the system. Cannot allocate a new one
Explanation All the IDs of the specified type are in use.
Recommended Action Reduce the traffic load, number of IPSec tunnels and/or frequency of re-key.If this message was seen under light loading conditions, thencopy the error message exactly as it appears, and report it to your technical support representative.
Error Message%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 thenumber of cryptomaps in the system. For SPD and SPD map, reduce the number of interface with cryptomap set attached.
Error Message%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.
Error Message%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.
Error Message%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.
Error Message%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.
Error Message%ACE-3-UNKACE : Received packet from unknown ACE [enet]
Explanation An ACE architecture IPSec hardware accelerator control packet was received from an unknown source.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%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.
Error Message%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 technicalsupport representative.
Error Message%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.
Error Message%ACE-6-SWITCHOVER : VPN-SPA switchover: [dec]/[dec] has been [chars] [dec]/[dec]
Explanation A blade to blade switcover has occurred. System performance is not affected.
Recommended Action The system performance is not affected. This is an informational message. No action is required.
Error Message%ACE-6-UNEXPIPSEC : RP received unexpected IPsec packet for [IP_address] (count=[dec])
Explanation An IPSec packet was unexpectedly forwarded to the route processor.
Recommended Action If this message was seen while the router was booting, while the hardware crypto accelerator was being enabled, or while an invalid peer IP address was encountered, this message is normal and no action is required. Otherwise, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%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.
Error Message%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.
ACLMERGE Messages
Error Message%ACLMERGE-3-CUDDERROR : A CUDD Library error was detected in %s
Explanation An error was detected by the CUDD Library, the ACL-Merge for this invokation has failed. This could result in more traffic being switched by software. The effect of this could be lower performance, for the interface for which the merge failed.
Recommended Action Copy and save this message. Report this to Engineering along with the ACL configuration of this device. Use Topic to search for a similar DDTS. If none found, write a DDTS for this problem
Error Message%ACLMERGE-3-CUDDWARN : A CUDD Library warning message for interest in this event in %s
Explanation Debug message only. No action required
Recommended Action Copy and save this message. Report this to Engineering along with the ACL configuration of the device. This is just a debug message of interest to engineering to investigate the case why this happened.
ACLMGR Messages
The following are ACL Manager messages.
Error Message%ACLMGR-2-NOMAP : Cannot create ACL Manager data structures for VLAN Map [chars]
Explanation The ACL Manager could not allocate the data structures needed to describe a VLAN Map in a form that can be loaded into hardware. Probably caused by lack of free memory.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%ACLMGR-2-NOVLB : Cannot create memory block for VLAN [dec]
Explanation The ACL Manager was unable to save per-VLAN information needed for its correct operation. Some per-interface features, such as access groups or VLAN maps, will not be configured correctly.
Recommended Action Use a less complicated configuration that requires less memory.
Error Message%ACLMGR-2-NOVMR : Cannot create VMR data structures for access list [chars]
Explanation The ACL Manager could not allocate the data structures needed to describe an ACL in a form that can be loaded into hardware. Probably caused by lack of available memory.
Recommended Action Use a less complicated configuration that requires less memory.
Error Message%ACLMGR-3-ACLTCAMFULL : Acl Tcam Full! Sofware Forwarding packets on [chars] label [dec] on [chars] [chars]
Explanation There are too many ACL configuration for the platform specific ACL Tcam Table to support.
Recommended Action Reduce the number IP or MAC access lists to be configured to interfaces.
Error Message%ACLMGR-3-AUGMENTFAIL : Augmenting of access-map [chars] on [chars] label [dec] failed
Explanation The system ran out of CPU DRAM when attempting to merge internally required elements with the configuredaccess map(s).
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%ACLMGR-3-FEATUREMISMATCH : %s can not be supported with the image running on switch-%d
Explanation A feature has been configured on the stack but can not be supported on one or more switches in the stack. This feature will continue to work on the rest of the switches that support it, but will not be applied to the switches that can not support it. All other features continue to work as expected on the stack.
Recommended Action Upgrade the software running on switches that can not support this feature. Upgrade to a software version that supports this feature.
Error Message%ACLMGR-3-IECPORTLABELERROR : ACL labels are out-of-sync on interface %s, label %d is not available on asic %d
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%ACLMGR-3-INSERTFAIL : Insert of access-map [chars] #[dec] into [chars] label [dec] failed
Explanation The system ran out of CPU DRAM when trying to merge sections of an access map.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%ACLMGR-3-INTTABLE : Not in truth table: VLMAP %d RACL %d Rtprot %d Mcb %d Feat %d
Explanation An unrecoverable software error occurred while trying to merge the configured input features.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show running-config command and your pertinent troubleshooting logs.Error Message%ACLMGR-3-INVALIDL4PORTINDEX : Invalid L4 port array index while processing (%s), number of L4 source ports (0x%x), L4 source port index (0x%x), number of L4 destination ports (0x%x), L4 destination port index (0x%x)
Explanation ACL Manager module received invalid value for L4 port array index. The problem can be due to memory corruption or bad system memory.
Recommended Action HACL_L4OP_ERROR
Error Message%ACLMGR-3-INVALIDPARAM : Invalid %s %d encountered
Explanation ACL Manager has encountered an invalid parameter value.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show running-config command and your pertinent troubleshooting logs.Error MessageExplanation The configuration is too complicated for the platform specific ACL merge code to support. Most likely cause is including too many separate access lists in a single VLAN map or policy map.
Recommended Action Reduce the number IP or MAC access lists (considered separately) in any one VLAN or policy map to fewer than the number of levels reported by this log message.
Error Message%ACLMGR-3-MAXRECURSION : Too many ([dec]) levels of recursion while merging ACLs (code [dec]).
Explanation The configuration is too complicated for the platform specific ACL merge code to support. The most likely cause is including too many separate access lists in a single VLAN map or policy map.
Recommended Action Reduce the number IP or MAC access lists (considered separately) in any one VLAN or policy map to fewer than the number of levels reported by this log message.
Error Message%ACLMGR-3-MERGEFAIL : [chars] ACL merge error [dec] ([chars]) on [chars] label [dec]
Explanation The ACL Manager was unable to complete the merge of the configured features into a form suitable for loading into the hardware. Packets potentially affected by this feature will be sent to the CPU for processing instead. The most likely cause is specifying an ACL that is too large or too complex for the system to handle.
Recommended Action Try specifying a smaller and less complicated configuration.
Error Message%ACLMGR-3-NOLABEL : Cannot allocate [chars] label for vlan-id [dec]
Explanation The ACL Manager was unable to allocate a label for the features on this interface. This means that the hardware cannot be programmed to implement the features, and packets for this interface will be filtered in software. There is a limit of 256 labels per direction.
Recommended Action Allocate more space to the relevant section of the TCAM and reboot, or else use a simpler configuration. Use the same ACLs on multiple interfaces, if possible.
Error Message%ACLMGR-3-OUTTTABLE : Not in truth table: RACL %d VLMAP %d
Explanation An unrecoverable software error occurred while trying to merge the configured output features.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show running-config command and your pertinent troubleshooting logs.Error Message%ACLMGR-3-PACLTTABLE : Not in truth table: IPSrcGrd %d PACL %d Rtprot %d
Explanation An unrecoverable software error occurred while trying to merge the configured port acl features.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show running-config command and your pertinent troubleshooting logs.Error Message%ACLMGR-3-QOSTTABLE : Not in truth table: ACL %d in map, action %d
Explanation A software error occurred while trying to merge a QoS Policy Map
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show running-config command and your pertinent troubleshooting logs.Error Message%ACLMGR-3-RELOADED : Reloading [chars] label [dec] feature
Explanation The ACL Manager was able to fit more of the configured features on this label into the hardware. One or more features had previously been unloaded because of lack of space.
Recommended Action No action is required.
Error Message%ACLMGR-3-UNKNOWNACTION : Unknown VMR access group action [hex]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%ACLMGR-3-UNKNOWNL4OPERATION : Unknown L4 operation 0x%x
Explanation ACL Manager module received invalid value for L4 operation. The problem can be due to memory corruption or bad system memory.
Recommended Action HACL_L4OP_ERROR
Error Message%ACLMGR-3-UNLOADING : Unloading [chars] label [dec] feature
Explanation The ACL Manager was unable to fit the complete configuration into the hardware, so some features will have to be applied in software. This prevents some or all of the packets in a VLAN from being forwarded in hardware, and requires them to be forwarded by the CPU. Multicast packets may be dropped entirely instead of being forwarded.
Recommended Action Allocate more space to the relevant section of the TCAM and reboot, or else use a simpler configuration. Use the same ACLs on multiple interfaces, if possible.
Error Message%ACLMGR-4-ACLTCAMFULL : %sACL TCAM Full. Software Forwarding packets on %s label %d on %s %s
Explanation The ACL configuration is too large to fit in the platform-specific ACL TCAM table.
Recommended Action Simplify the ACLs applied to interfaces, or reduce their number.
Error Message%ACLMGR-4-RELOADED : Reloading %s %s label %d %s %sfeature
Explanation The ACL Manager was able to fit more of the configured features on this label into the hardware. One or more features had previously been unloaded because of lack of space.
Recommended Action No action is required.
Error Message%ACLMGR-4-RELOADEDFSPAN : Reloading %s session %d %s feature
Explanation The ACL Manager was able to fit more of the configured Flow based SPAN features on this session into the hardware. One or more features had previously been unloaded because of lack of space.
Recommended Action No action is required.
Error Message%ACLMGR-4-UNLOADING : Unloading %s %s label %d %s %sfeature
Explanation The ACL Manager was unable to fit the complete configuration into the hardware, so some features will have to be applied in software. This prevents some or all of the packets in a VLAN/port from being forwarded in hardware, and requires them to be forwarded by the CPU. Multicast packets may be dropped entirely instead of being forwarded.
Recommended Action Allocate more space to the relevant section of the TCAM and reboot, or else use a simpler configuration. Use the same ACLs on multiple interfaces, if possible.
Error Message%ACLMGR-4-UNLOADINGFSPAN : Unloading %s session %d %s feature
Explanation The ACL Manager was unable to fit the complete Flow based SPAN configuration into the hardware, so this feature has been temporarily disabled for the given session.
Recommended Action Allocate more space to the ACL section of the TCAM by choosing an SDM template with more ACL TCAM space, and reboot the switch. You may also use a simpler ACL configuration and/or use the same ACLs on multiple interfaces, if possible.
Error Message%ACL_ASIC-4-INTR_THROTTLE : Throttling '[chars]' interrupt exceeded permitted [int]/[dec] interrupts/msec
Explanation This message indicates an excessive number of interrupts. The system performs throttling to keep the switch processor safe.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
ACR Messages
The following are the ACR messages.
Error Message%ACR-1-ISSU_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.
Error Message%ACR-3-ACRIFADD : [chars] interface add failed for ACR group [dec].
Explanation An attempt to add an interface to the ACR group has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show acr all command and your pertinent troubleshooting logs.
Error Message%ACR-3-ACRIFDEL : [chars] interface del failed for ACR group [dec].
Explanation An attempt to delete an interface from the ACR group has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show acr all command and your pertinent troubleshooting logs.
Error Message%ACR-3-ACRPVCDISABLE : PVC Disable failed for VCD= [dec] on [chars] interface of ACR interface [chars].
Explanation An attempt to disable a PVC on the ACR physical interface has failed.
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of show acr group and show acr group detail command and your pertinent troubleshooting logs.
Error Message%ACR-3-ACRVPDISABLE : VP Disable failed for VPI= [dec] on [chars] interface of ACR interface [chars].
Explanation An attempt to disable a VP on the ACR physical interface has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of show acr group and show acr group detail command and your pertinent troubleshooting logs.
Error Message%ACR-3-ACRVPENABLE : VP Enable failed for VPI= [dec] on [chars] interface of ACR interface [chars].
Explanation An attempt to enable a VP on the ACR physical interface has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of show acr group and show acr group detail command and your pertinent troubleshooting logs.
Error Message%ACR-3-ISSU_SENDFAILED : ACR ISSU: send message failed, rc = [dec]
Explanation The sending of a message has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ACR-4-ISSU_INCOMPATIBLE : acr-issu-compat: returned FALSE
Explanation The compatibility checking has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ACR-4-ISSU_XFORM : [chars]: failed, rc=[chars]
Explanation The transform has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ACR-6-ACRPVCADD : PVC creation failed for VCD= [dec] on [chars] interface of ACR interface [chars].
Explanation An attempt to create a PVC on ACR physical interface has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of show acr group and show acr group detail command and your pertinent troubleshooting logs.
Error Message%ACR-6-ACRPVCENABLE : PVC Enable failed for VCD= [dec] on [chars] interface of ACR interface [chars].
Explanation An attempt to enable a PVC on the ACR physical interface has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of show acr group and show acr group detail command and your pertinent troubleshooting logs.
Error Message%ACR-6-ACRVPADD : VP creation failed for VPI= [dec] on [chars] interface of ACR group [chars].
Explanation An attempt to create a VP on the ACR physical interface has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of show acr group and show acr group detail command and your pertinent troubleshooting logs.
Error Message%ACR-6-ACRVPDEL : PVC deletion failed for VPI= [dec] on [chars] interface of ACR group [chars].
Explanation An attempt to delete a VP on the ACR physical interface has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of show acr group and show acr group detail command and your pertinent troubleshooting logs.
ADAPTER Messages
Error Message%ADAPTER-0-DIAGDATA : Module Call: [hex][hex] Error ID: [hex][hex]
Explanation A diagnostic routine has detected a failure in the ECA hardware. The indicated codes are used to locate the specific component that failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ADAPTER-0-DIAGFAIL : Port [dec] failed the [chars] diagnostic
Explanation A diagnostic routine has failed. The specified port will not be used.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ADAPTER-0-DIAGTERM : Port [dec]: The [chars] diagnostic failed to terminate
Explanation A diagnostic routine did not end when expected. The specified port will not be used.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ADAPTER-0-LOADFAIL : Port [dec] microcode load failed.
Explanation Each adapter has an onboard microprocessor. This message indicates that the operation to load the code for that microprocessor has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ADAPTER-0-START_FAIL : Diagnostics failed for port [dec], start request ignored.
Explanation Prior to receipt by the adapter of a start command from the Route Processor, a set of diagnostics is run. If one of them fails, then the adapter will not be started when the start command is issued.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ADAPTER-6-BADREQUEST : Bad request code [dec] generated on port [dec]
Explanation A request was sent to the function that handles general requests for the specified port. The request code was not in a range recognized by that function.
Recommended Action The CIP has recovered by ignoring the request. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ADAPTER-6-BADSTATE : Bad state: port [dec], request code [dec], state [dec], flags [hex]
Explanation The specified port was in an invalid state while it was attempting to process the specified general request.
Recommended Action The CIP recovered by forcing the port into a valid state. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ADAPTER-6-DIAGBEGIN : [chars] diagnostic starting
Explanation The user has used the test cbus command to request a particular adapter diagnostic to be run. This message informs the user that the diagnostic routine has started.
Recommended Action Wait for the next message.
Error Message%ADAPTER-6-DIAGDATA2 : Module Call: [hex][hex] Error ID : [hex][hex]
Explanation A diagnostic routine has detected a failure in the ECA hardware. The indicated codes are used to locate the specific component that failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ADAPTER-6-DIAGFAIL2 : [chars] diagnostic failed
Explanation A diagnostic requested by the test cbus command has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ADAPTER-6-DIAGGOOD2 : [chars] diagnostic ran successfully
Explanation A diagnostic requested by the test cbus command has completed successfully.
Recommended Action No action is required.
Error Message%ADAPTER-6-DIAGRANGE : Diagnostic number ([dec]) out of range 0-[dec]
Explanation The diagnostic number requested by the test cbus command is invalid.
Recommended Action Reenter the command with a valid diagnostic number.
Error Message%ADAPTER-6-DIAGSTOP : Interface must be shutdown to run diagnostic
Explanation The test cbus command was used to run a diagnostic on an active interface. The interface must be shut down before the diagnostic is run.
Recommended Action Use the shutdown command to stop the interface and then reissue the diagnostic request.
Error Message%ADAPTER-6-DIAGTERM2 : [chars] diagnostic failed to terminate
Explanation A diagnostic requested by the test cbus command did not end when expected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ADAPTER-6-LOGDATA : [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex]
Explanation An error has occurred in the adapter. The information displayed will help software developers determine the nature of the error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ADAPTER-6-LOGOUT : Port [dec] logout data. Adapter microcode [hex]
Explanation This message indicates the start of the logout data. Logout data occurs whenever a problem is detected on the port adapter or, with an ECA, on the fiber.
Recommended Action If this message is being continually generated on a new installation, it may indicate that the fiber is not connected properly. Verify that the connector is firmly seated. If a loose fiber was not the cause of these messages, report this message to your Cisco technical support representative.
Error Message%ADAPTER-6-LOGSAME : [hex] to [hex] same as above
Explanation This message is used when logout information is displayed to avoid printing duplicate data.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ADAPTER-6-NO_CHAN_EV_BUF : No channel event buffer: Daughter board [dec]
Explanation Channel link incident events are being dropped by the channel adapter because of an overflow of incidents.
Recommended Action Use SNMP to poll the CIP for the current LIR counts.
Error Message%ADAPTER-6-NO_CHAN_EV_POOL : Could not allocate channel event pool
Explanation There is insufficient memory on the channel adapter to allocate buffers used for generating channel adapter events. Unless the memory is increased, no channel link incident events (SNMP traps) will be generated.
Recommended Action Add more memory to the channel adapter.
Error Message%ADAPTER-6-SCAN : Port [dec] scan data. Adapter microcode [hex]
Explanation This message precedes the SCANDATA error message for the adapter in the specified port. This scan is usually produced as a result of a hardware error.
Recommended Action Report the entire error message, including the SCANDATA error message that follows it, to your Cisco technical support representative.
Error Message%ADAPTER-6-SCANDATA : [hex] [hex] [hex] [hex] [hex]
Explanation The data in this message is related to the hardware failure of an adapter.
Recommended Action Report the entire error message, including the preceding SCAN error message, to your Cisco technical support representative.
Error Message%ADAPTER-6-WRAP : Wrap plug detected in port [dec]. Wrap loop started.
Explanation A wrap plug is installed in the specified port. Wrap diagnostics will run until the wrap plug is removed, if this is the only adapter, or until both adapters have wrap plugs installed.
Recommended Action Remove the wrap plug and connect the interface to a channel.
Error Message%ADAPTER-6-WRAPSTOP1 : Wrap plug removed from port [dec]. Wrap loop ended.
Explanation The wrap plug has been removed, causing the wrap diagnostics to end.
Recommended Action No action is required.
Error Message%ADAPTER-6-WRAPSTOP2 : Port [dec] active. Port [dec] wrap loop ended.
Explanation The wrap diagnostics have ended because the other adapter is active.
Recommended Action Remove the wrap plug and connect the interface to a channel if you wish to use this adapter. Otherwise, no action is required.
ADJ Messages
The following are adjacency subsystem messages.
Error Message%ADJ-3-ABNORMALSHUTDOWN : Memory expected to be freed is still in use on adj system shutdown
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%ADJ-3-ADJDELMSG : Invalid delete message length [dec]
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ADJ-3-ADJFIBIDB : Adjacency update with invalid fibidb([dec])
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ADJ-3-ADJGENALLOCATEFAIL : Failed to allocate memory [chars]
Explanation An internal software error has occurred. This is probably because not enough memory was available.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%ADJ-3-ADJGENDEALLOCATEFAIL : Failed to deallocate memory [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%ADJ-3-ADJMGRALLOCATEFAIL : Failed to allocate an adjacency summary event block
Explanation An internal software error has occurred. This is probably because not enough memory was available.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%ADJ-3-ADJMGRDISPATCHFAIL : Failed to enqueue an adjacency summary event block
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%ADJ-3-ADJMGRREFRESHFAIL : Failed to dispatch a refresh adjacency summary event
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%ADJ-3-ADJSTACK2 : Adj stack2 error %s: %s
Explanation An internal software error occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%ADJ-3-ALLOCATEFAIL : Failed to allocate an adjacency
Explanation An internal software error has occurred. This is probably because not enough memory was available.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%ADJ-3-ALLOCATEONDOWN : Allocating adj when adj subsystem down
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%ADJ-3-BADADDRLEN : Zero address length detected distributing adj [chars]
Explanation An internal software error has occurred. An attempt to reference an adjacency with an unsupported address type has been made.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%ADJ-3-BADADDRTYPE : Using an unsupported address type [dec] when trying to add/delete/modify/find an adjacency
Explanation An internal software error has occurred. An attempt to reference an adjacency with an unsupported address type has been made.
Recommended Action CCopy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%ADJ-3-BADLINKTYPE : Using an unsupported linktype [chars] when trying to add/delete/modify/find an adjacency
Explanation An internal software error has occurred. An attempt to reference an adjacency with an unsupported address type has been made.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%ADJ-3-BADMACALIGN : adjacency mac string end [hex] not [chars] aligned
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%ADJ-3-BADMAGIC : adjacency [chars] is followed by bad magic
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%ADJ-3-BOARDENCAP : Generation of encapsulation string for [chars] failed
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%ADJ-3-BROKERINITFAIL : Failed to initialise adjacency RP broker facility
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ADJ-3-BUNDLES : Adj bundles: [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ADJ-3-DBGFILTERALLOCATEFAIL : Failed to allocate an adjacency debug filter block
Explanation An internal software error has occurred. This is probably because not enough memory was available.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%ADJ-3-FEATURE : Adj features: [chars][chars][chars]
Explanation An internal software error has occurred.
Error Message%ADJ-3-ILALLOCATEFAIL : Failed to allocate an adjacency interest list subblock
Explanation An internal software error has occurred. This is probably because not enough memory was available.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%ADJ-3-ILDEALLOCATEFAIL : Failed to deallocate an adjacency interest list subblock
Explanation An internal software error has occurred. This is probably because not enough memory was available.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%ADJ-3-ILINITFAIL : Failed to initialise adjacency interest list facility
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ADJ-3-ILLEGALARGS : Illegal arguments - [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%ADJ-3-INVALIDADJTYPE : Invalid adjacency type ([dec])
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ADJ-3-LCXDRCLIENT : Adjacency distribution client: [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%ADJ-3-MACOVERFLOW : Adjacency mac address for [chars] overflowed by [dec] bytes
Explanation An internal software error occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%ADJ-3-NOFIBIDB : CEF Interface not found - [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%ADJ-3-NOMATCH : Adj=[hex] index=[dec] tbl_entry=[hex]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ADJ-3-NULLFIBHWIDB : Add [chars] with null cef hwidb([chars])
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ADJ-3-NULLFIBIDB : Add [chars] with null cef idb
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ADJ-3-RESOLVE_REQ : Adj resolve request: [chars] [chars] [chars]
Explanation An internal software error occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%ADJ-3-RPXDRCLIENT : Adjacency distribution client: [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%ADJ-3-SBINITFAIL : Failed to initialise adjacency subblock facility
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ADJ-3-STATETRANSITION : Unexpected state transition from [chars] to [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%ADJ-3-TYPENOTISSUAWARE : Bundle type [chars] must be ISSU aware to send to slot(s) [chars]
Explanation The given bundle type is not ISSU aware so cannot be distributed to a slot with which ISSU negotiation has occurred. This indicates a design problem which requires code changes to fix.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%ADJ-3-XDRBADMAGIC : xdr message for [chars] spilled out of allocated static storage
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%ADJ-5-ADJISSUINCOMPATIBLE : All or part of adjacency message for %s not sent to incompatible CEF instance for %s
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.
Error Message%ADJ-5-PARENT : Midchain parent maintenance for %s - %s
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 inteface other than the tunnel itself or by bringing the tunnel down
Recommended Action No action is required.
AESOP_AIM Messages
The following are Service Engine AIM messages.
Error Message%AESOP_AIM-1-INITFAIL : AIM slot [dec]: PCI device [dec] initialization failed
Explanation The Service Engine AIM has failed to initialize.
Recommended Action Power off the system, reseat the interface card, and reboot the system.
AFLSEC Messages
The following are the AFLSEC messages.
Error Message%AFLSEC-6-OALDP : [chars] icmp [IP_address] - [IP_address] ([dec]/[dec]), [dec] packet[chars]
Explanation Packet(s) matching the optimized ACL log criteria was detected.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AFLSEC-6-OALNP : [chars] ip protocol=[dec] [IP_address] - [IP_address], [dec] packet[chars]
Explanation Packet(s) matching the optimized ACL log criteria was detected.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AFLSEC-6-OALP : [chars] [chars] [IP_address]([dec]) - [IP_address]([dec]), [dec] packet[chars]
Explanation Packet(s) matching the optimized ACL log criteria was detected.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AFLSEC-6-OALRL : Oal logging rate-limited or missed [dec] packet[chars]
Explanation Some packet matching logs were missed because the log messages were rate-limited or cache table was full or no log buffers were available.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AFLSEC-6-OALRP : [chars] igmp [IP_address] - [IP_address] ([dec]), [dec] packet[chars]
Explanation Packet(s) matching the optimized ACL log criteria was detected.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
AGGMGR Messages
The following are the aggregation manager messages.
Error Message%AGGMGR-0-NO_SPACE : No space left for creator '[chars]' to add data item to agg list (items [dec] max [dec] remaining [dec])
Explanation An attempt to add an item to an aggregation list has failed. The creation of the aggregation list was successful, but for an unknown reason the addition failed. This is considered an internal error. There is no current workaround.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
AHDLC_TRINIAN Messages
Error Message%AHDLC_TRINIAN-1-DISCOVER : Found [dec] interfaces on bay [dec], shutting down bay
Explanation The number of interfaces found was not the number that was expected. This condition possibly indicates a hardware failure.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AHDLC_TRINIAN-3-BADCHANNEL : chid [dec]
Explanation The AHDLC driver has detected that the channel number is greater than what is supported.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AHDLC_TRINIAN-3-BADDEV : packet received for unknown device
Explanation The channel encapsulation has become corrupted.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AHDLC_TRINIAN-3-BADDEVCH : packet received for unknown device channel [dec]
Explanation The channel encapsulation has become corrupted.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AHDLC_TRINIAN-3-BADHW : Bad Hardware
Explanation The AHDLC hardware did not initialize.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AHDLC_TRINIAN-3-DOWNLOAD : download fail at [hex], expect=[hex], readback=[hex]
Explanation A software or hardware error has occurred. The AHDLC driver detected that the transmit ring is in an inconsistent and unrecoverable state.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AHDLC_TRINIAN-3-NOCH : packet received for unknown resource manager channel [dec]
Explanation The channel encapsulation has become corrupted.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AHDLC_TRINIAN-3-NOMEMORY : No Memory for channel allocation
Explanation The AHDLC driver could not allocate memory for the channel.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AHDLC_TRINIAN-3-NOTAHDLC : Device reported [hex]
Explanation The AHDLC hardware has failed. A non-AHDLC device pointed at the software for the AHDLC.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AHDLC_TRINIAN-3-NOTAHDLCHW : Bad HWIDB returned.
Explanation The AHDLC driver detected that the CDMA software invoked the AHDLC driver with an incorrect engine ID.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AHDLC_TRINIAN-3-PAKOVERFLOW : packet buffer, pak=[hex], size=[dec]
Explanation A software or hardware error has occurred. The AHDLC driver detected that the transmit ring is in an inconsistent and unrecoverable state.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AHDLC_TRINIAN-3-PAKTOOBIG : packet buffer, pak=[hex], size=[dec]
Explanation A software or hardware error has occurred. The AHDLC driver received a packet from an application that was larger than the expected size.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AHDLC_TRINIAN-3-SEQERR : rsc_mgr_chid [dec], receive=[dec], expect=[dec]
Explanation A software or hardware error has occurred. The AHDLC driver detected that the transmit ring is in an inconsistent and unrecoverable state.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AHDLC_TRINIAN-3-TXOVERRUN : dev [dec] chid [dec], particle_count=[dec]
Explanation The AHDLC driver detected that the outstanding Tx buffer has exceeded its maximum allowance.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AHDLC_TRINIAN-3-TXQFULL : pak=[hex], particle_count=[dec], wp=[dec], rp=[dec]
Explanation A software or hardware error has occurred. The AHDLC driver detected that the transmit ring is in an inconsistent and unrecoverable state.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AHDLC_TRINIAN-6-SHUTDOWN : [chars] shutting down
Explanation The specified AHDLC driver is shutting down. The driver may have been physically removed.
Recommended Action No action is required.
AICMGMT Messages
Error Message%AICMGMT-1-AIC_ALERT : AIC Slot [int]: [chars]
Explanation The Alarm Interface Controller network module in the specified slot has forwarded this error message to the Cisco IOS software. This error is localized to the Alarm Interface Controller network module and does not involve the Cisco IOS software.
Recommended Action Consult the documentation for the Alarm Interface Controller network module for information about the described condition.
Error Message%AICMGMT-2-AIC_CRITICAL : AIC Slot [int]: [chars]
Explanation The Alarm Interface Controller network module in the specified slot has forwarded this error message to the Cisco IOS software. This error is localized to the Alarm Interface Controller network module and does not involve the Cisco IOS software.
Recommended Action Consult the documentation for the Alarm Interface Controller network module for information about the described condition.
Error Message%AICMGMT-3-AIC_ERR : AIC Slot [int]: [chars]
Explanation The Alarm Interface Controller network module in the specified slot has forwarded this error message to the Cisco IOS software. This error is localized to the Alarm Interface Controller network module and does not involve the Cisco IOS software.
Recommended Action Consult the documentation for the Alarm Interface Controller network module for information about the described condition.
Error Message%AICMGMT-4-AIC_UNEXPVER : AIC Slot [int]: management message version mismatch - [hex] [hex] [hex] [hex]
Explanation The Cisco IOS software image and the firmware version of the Alarm Interface Controller network module may be incompatible. The four bytes that are specified in the error string represent the version of the current Alarm Interface Controller network module firmware. To see the expected version for the Alarm Interface Controller network module firmware (specified when the current Cisco IOS image was produced), enter the show alarm-interface slot# command.
Recommended Action To correct the mismatched versions, replace the installed version of the Cisco IOS software image or the version of the firmware of the Alarm Interface Controller network module, or replace both versions. The Cisco documentation for release notes and field notices will provide information on the versions that are compatible. This message is only a warning. It does not imply that errors will occur if the system continues to run with the mismatched versions. If you decide to contact a Cisco technical support representative for assistance, first enter the show alarm-interface slot# command for the slot that was specified in the error message. Report the gathered information, along with the version of Cisco IOS software used, to your Cisco technical support representative.
Error Message%AICMGMT-4-AIC_WARNING : AIC Slot [int]: [chars]
Explanation The Alarm Interface Controller network module in the specified slot has forwarded this error message to the Cisco IOS software. This error is localized to the Alarm Interface Controller network module and does not involve the Cisco IOS software.
Recommended Action Consult the documentation for the Alarm Interface Controller network module for information about the described condition.
AIM Messages
The following are advanced interface module (AIM) messages.
Error Message%AIM-2-AIMSUPP : AIM type [dec] is not supported by this platform.
Explanation The AIM that is installed is not supported by this platform.
Recommended Action Power off the router and replace the AIM card.
Error Message%AIM-2-AIMUNSUPP : AIM type [hex] is not supported by this platform.
Explanation The AIM that is installed is not supported by this platform.
Recommended Action Power off and replace the AIM card.
Error Message%AIM2CUE-1-INITFAIL : Slot [dec]: [chars]
Explanation The initialization of the Internal Service Module has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%AIM2CUE-1-SUPPORTCUE2 : Slot [dec]: [chars]
Explanation The AIM2-APPRE-104-K9 and AIM2-CUE-K9 are not supported for use in AIM1 (Slot 1).
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
AIP Messages
Error Message%AIP-3-AIPFAILSETUPVC : [chars] Failed to setup vc [dec] (Cause: [chars])
Explanation The AIP driver failed to set up a virtual circuit.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AIP-3-AIPFAILSETUPVCAVG : Interface [chars], Failed to setup vc [dec] (Cause: [chars]) Expected range [[dec] .. [dec]]Kbps for AIP Average Rate Metering. Average Rate=Peak Rate= [dec] Kbps turns Average Rate Metering OFF
Explanation A software or hardware error occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Alarm Messages
The following are Telco chassis alarm related messages.
Error Message%ALARM-1-CRITICAL_ALARM : CRITICAL alarm condition detected
Explanation A critical alarm event that needs immediate attention has occurred. The system will shut down within two minutes.
Recommended Action Check the source of the critical alarm to take any corresponding action. Do not power on unless the situation is corrected. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ALARM-2-MAJOR_ALARM : Major alarm condition detected
Explanation A major alarm event that will affect system service has occurred.
Recommended Action Either correct or note this condition. Check the source of the major alarm and take corresponding actions.
Error Message%ALARM-3-CLEAR : %s %s %s %s %s %ALARM-3-MINOR_ALARM: Minor alarm condition detected
Explanation An minor alarm event has happened, it does not affect the system service, but needs attention.
Recommended Action Check the source of the minor alarms to avoid the situation getting worse. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%ALARM-3-MINOR_ALARM : Minor alarm condition detected
Explanation An minor alarm event that does not affect the system service has occurred.
Recommended Action Check the source of the minor alarm to avoid a worsening of the situation. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ALARM-3-NOCLASS : Unknown Alarm Severity Class
Explanation The alarm status tables contain an alarm entry with an unknown alarm severity class.
Recommended Action Check the source of the minor alarm to avoid a worsening of the situation. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ALARM-3-NOMEM : OUT of Memory: %s
Recommended Action .
Error Message%ALARM-3-NOMESSAGES : No alarm messages left
Explanation No more alarm messages are available in the message cache
Recommended Action Check the source of the minor alarm to avoid a worsening of the situation. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ALARM-3-NORESOURCES : Failed to [chars] [chars] alarms for [chars].
Explanation System resources were insufficient to process the alarm request.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ALARM-3-NOSOURCE : Attempt to set alarm status for undefined source
Explanation The alarm subsystem has no record of this alarm source. Either the source has not been registered or it has been deleted.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ALARM-3-NOTYPE : Attempt to change alarm status for undefined type
Explanation The alarm subsystem has no record of this type of alarm. Either the alarm type has not been registered or it has been deleted.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ALARM-3-TOOMANYSOURCES : Max number of alarm sources exceeded
Explanation Too many alarm sources were added by the system
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs. ALPS Messages The following are ALPS messages.
Error Message%ALARM-6-ENTITY_INFO : [chars] [chars] [chars] [chars] [chars]
Explanation This messages indicates entity alarm assertion or deassertion information.
Recommended Action No action is required.
Error Message%ALC-3-CMDERR : ([dec]/[dec]) Interface ([chars]): [chars] IPC command fails (cause: [hex])
Explanation The ATM RP driver has experienced an IPC command error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ALC-3-EVENT : ([dec]/[dec]) Interface ([chars]): unknown IPC event ([int]) from linecard
Explanation The ATM RP driver has received a unknown event from the line card.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ALC-3-INIT : ATM driver ([int]/[int]) initialization [chars].
Explanation The ATM RP driver has experienced a software initialization error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ALC-3-VCADJ : ([dec]/[dec]) Per-VC adjacency error: VC :[int] [chars]
Explanation The ATM RP driver has experienced a per-VC adjacency software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ALC-3-VCENCTYPE : ([dec]/[dec]) VC :[int] unknown VC encapsulation type ([int])
Explanation The ATM RP driver has experienced an unknown VC encapsulation software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ALC-4-HIRATE : ([dec]/[dec]) Interface ([chars]): SAR limits VBR VC PCR to [dec] kbps, opening UBR VC instead
Explanation The SAR sublayer limits VBR VC PCR to one-half of the link bandwidth.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ALC-4-NULLCEFIDB : ([dec]/[dec]) Interface ([chars])
Explanation CEF IDB is missing from this interface.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ALC-4-UNSUP : ([dec]/[dec]) Interface ([chars]): unsupported feature: [chars]
Explanation This feature is not supported by Internet router ATM RP.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
ALIGN Messages
Error Message%ALIGN-1-FATAL : [chars]
Explanation An alignment error has occurred. Alignment errors are caused by misaligned reads and writes. For example, a two-byte read of a memory address that is not a multiple of two bytes is an alignment error. Alignment errors are caused by internal software failures. The system will be reloaded, often with a bus error.
Recommended Action This message is caused by a software failure. To take advantage of recent fixes, upgrade your system to the latest Cisco IOS software release in your release train. If this message recurs, copy the error message text exactly as it appears on the console or in the system log, enter the show log, show alignment and show tech-support commands, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ALIGN-3-CORRECT : Alignment correction made at 0x%x %sing 0x%x
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.
Error Message%ALIGN-3-CORRECT_SO : Alignment correction made at %s %sing %s
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.
Error Message%ALIGN-3-FULL : Alignment log is full - no new entries will be recorded
Explanation The router identified more software components in need of memory optimization than it can record.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%ALIGN-3-READEXCEPTION : Warning : read accees failed at %s, 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.
Error Message%ALIGN-3-RO_WRITE : Spurious memory access made at 0x%x writing to 0x%x
Explanation An attempted but illegal access to a low memory address within a software component in the router has been temporarily blocked.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show alignment command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show alignment output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%ALIGN-3-SPURIOUS : Spurious memory access made at 0x%x reading 0x%x
Explanation An attempted but illegal access to a low memory address within a software component in the router has been temporarily blocked.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show alignment command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show alignment output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%ALIGN-3-SPURIOUS_SO : Spurious memory access made at %s reading %s
Explanation An attempted but illegal access to a low memory address within a software component in the router has been temporarily blocked.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show alignment command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show alignment output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%ALIGN-3-TRACE : -Traceback= %08x %08x %08x %08x %08x %08x %08x %08x
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.
Error Message%ALIGN-3-TRACEX : %s
Explanation A trace that shows where the previous ALIGN error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative. %ALIGN-3-TRACE_SO: -Traceback= %s
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.
Error Message%ALIGN-3-TRACE_SO : -Traceback= [chars]
Explanation This trace message indicates where the previously reported alignment error occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
ALPS Messages
Error Message%ALPS-3-ALPSFAIL : ALPS: Assertion failed: [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ALPS-3-ASCU_FSM_ERR : ASCU %02x on interface %s has an internal FSM error.
Explanation Internal error.
Recommended Action Turn debug flags on, capture traces & contact Cisco technical support
Error Message%ALPS-3-ASCU_IF_STUCK : Polling for ASCU [hex] on interface [chars] is stalled.
Explanation The polling mechanism for an ALPS interface has stalled.
Recommended Action No action is required.
Error Message%ALPS-5-ASCU_DISABLED_ASCU_STUCK : ASCU [hex] on interface [chars] has been disabled since 4 consecutive messages were received from same SID.
Explanation An ALPS ASCU has been automatically disabled.
Recommended Action No action is required.
Error Message%ALPS-5-ASCU_DOWN : ASCU [hex] on interface [chars] is down.
Explanation An ALPS ASCU has transitioned from up to down.
Recommended Action No action is required.
Error Message%ALPS-5-ASCU_UP : ASCU [hex] on interface [chars] is up.
Explanation An ALPS ASCU has transitioned from down to up.
Recommended Action No action is required.
Error Message%ALPS-5-CIRCUIT_CLOSED : Circuit [chars] changed state to closed, rsn = [chars].
Explanation An ALPS circuit has tranistioned from open to closed
Recommended Action No action is required.
Error Message%ALPS-5-CIRCUIT_OPEN : Circuit [chars] changed state to open.
Explanation An ALPS circuit has transitioned from closed to open.
Recommended Action No action is required.
Error Message%ALPS-5-PEER_CLOSED : Peer (%i, %s) changed state to closed.
Explanation An ALPS peer connection is now closed.
Recommended Action No action is required.
Error Message%ALPS-5-PEER_CLOSED_DYNAMIC_INACTIVITY : Peer ([IP_address], [chars]) closed due to inactivity.
Explanation An ALPS peer connection is now closed due to inactivity.
Recommended Action No action is required.
Error Message%ALPS-5-PEER_CONN_ID_CHANGE : Peer ([IP_address], [chars]) ID modified to ([IP_address], [chars]).
Explanation An ALPS peer connection identifier has changed.
Recommended Action No action is required.
Error Message%ALPS-5-PEER_OPEN : Peer ([IP_address], [chars]) changed state to open.
Explanation An ALPS peer connection is now open.
Recommended Action No action is required.
Error Message%ALPS-6-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 No action is required.
Error Message%ALPS-6-CIRCUIT_BUSY_START : Circuit [chars] has entered a congested state.
Explanation An ALPS circuit is experiencing congestion.
Recommended Action No action is required.
Error Message%ALPS-6-CIRCUIT_OPEN_FAILED : Circuit [chars] received a Circuit Open Failed message, rsn = [chars].
Explanation An ALPS circuit sent a Circuit Open Request message and received a Circuit Open Failed message as a reply.
Recommended Action No action is required.
Error Message%ALPS-6-CIRCUIT_UPDATE_FAILED : Circuit [chars] received a Circuit Open Failed message, rsn = [chars].
Explanation An ALPS circuit sent a Circuit Update message and received a Circuit Open Failed message as a reply.
Recommended Action No action is required.
Error Message%ALPS-6-CIRCUIT_X25_VC_STUCK : Host unresponsive on X.25 VC for circuit %s
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
Error Message%ALPS-6-PEER_BUSY_END : Peer ([IP_address], [chars]) has exited a congested state.
Explanation An ALPS peer connection is no longer experiencing congestion.
Recommended Action No action is required.
Error Message%ALPS-6-PEER_BUSY_START : Peer ([IP_address], [chars]) has entered a congested state.
Explanation An ALPS peer connection is experiencing congestion.
Recommended Action No action is required.
Error Message%ALPS-6-PEER_OPEN_FAIL : Peer ([IP_address], [chars]) open failed, rsn = [chars]
Explanation An attempt to open an ALPS peer connection has failed.
Recommended Action No action is required.
Error Message%ALPS-7-CIRCUIT_BUSY_END : Circuit [chars] has exited a congested state.
Explanation An ALPS circuit is no longer experiencing congestion.
Recommended Action No action is required.
Error Message%ALPS-7-CIRCUIT_DROPS_CKT_DISABLED : Threshold exceeded for circuit disabled drops for circuit [chars]
Explanation The number of ALPS circuit drops caused by a disabled circuit exceeds the ALPS circuit threshold value.
Recommended Action No action is required.
Error Message%ALPS-7-CIRCUIT_DROPS_INVALID_ASCU : Threshold exceeded for invalid ASCU drops for circuit [chars]
Explanation The number of ALPS circuit drops caused by an invalid ASCU identifier exceeds the ALPS circuit threshold value.
Recommended Action No action is required.
Error Message%ALPS-7-CIRCUIT_DROPS_LIFETIME_EXPIRED : Threshold exceeded for lifetime timer expiration drops for circuit [chars]
Explanation The number of ALPS circuit drops due to lifetime timer expiration exceeds the ALPS circuit threshold value.
Recommended Action No action is required.
Error Message%ALPS-7-CIRCUIT_DROPS_QUEUE_OVERFLOW : Threshold exceeded for queue overflow drops for circuit [chars]
Explanation The number of ALPS circuit drops caused by queue overflow exceeds the ALPS circuit threshold value.
Recommended Action No action is required.
Error Message%ALPS-7-CIRCUIT_DROPS_VC_RESET : Threshold exceeded for X.25 VC Reset drops for circuit [chars]
Explanation The number of ALPS circuit drops caused by an X.25 VC reset exceeds the ALPS circuit threshold value.
Recommended Action No action is required.
Error Message%ALPS-7-PEER_DROPS_MAX_SIZE_EXCEEDED : Threshold exceeded for maximum size exceeded drops for peer ([IP_address], [chars]).
Explanation The number of ALPS peer drops caused by surpassing maximum size exceeds the ALPS peer threshold value.
Recommended Action No action is required.
Error Message%ALPS-7-PEER_DROPS_PEER_UNREACHABLE : Threshold exceeded for peer unreachable peer drops for peer ([IP_address], [chars]).
Explanation The number of ALPS peer drops caused by a peer unreachable condition exceeds the ALPS peer threshold value.
Recommended Action No action is required.
Error Message%ALPS-7-PEER_DROPS_QUEUE_OVERFLOW : Threshold exceeded for TCP Queue overflow peer drops for peer ([IP_address], [chars]).
Explanation The number of ALPS peer drops due to queue overflow exceeds the ALPS peer threshold value.
Recommended Action No action is required.
Error Message%ALPS-7-PEER_DROPS_VERSION_MISMATCH : Threshold exceeded for version mismatch peer drops for peer ([IP_address], [chars]).
Explanation The number of ALPS peer drops caused by a queue overflow exceeds the ALPS peer threshold value.
Recommended Action No action is required.
AMD79C971_FE Messages
Error Message%AMD79C971_FE-5-FAILED_SUSPEND : Failed to suspend the amd79c971 chip
Explanation An attempt to suspend the AMD Am79C971 chip has failed.
Recommended Action No action is required.
AMDP2_FE Messages
Error Message%AMDP2_FE-1-DISCOVER : Only found [dec] interfaces on bay [dec], shutting down bay
Explanation The software could not identify the interface card.
Recommended Action Power down, reseat the interface card, and reboot. If the message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%AMDP2_FE-1-INITFAIL : AMDP2/FE [dec], Init failed, CSR[dec]=[hex]
Explanation The software failed to initialize/restart an Ethernet/Fast Ethernet interface.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%AMDP2_FE-1-MEMERR : AMDP2/FE [chars], Memory error, CSR[dec]=[hex]
Explanation The interface could not access system resources for a long time. This problem may occur under very heavy loads.
Recommended Action The system should recover. No action is required. If thise message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%AMDP2_FE-1-NOMII : AMDFE [chars],MII Interface transceiver not connected
Explanation The MII transceiver was disconnected while the MII port was selected.
Recommended Action Connect the transceiver and enter the shut and no shut commands for the interface in the configuration menu.
Error Message%AMDP2_FE-1-NOTSUPPORTED : 2FE PA not supported on NPE100, shutting down bay
Explanation 2FE PA is not supported on a 7200 with NPE100.
Recommended Action NPE150 or better is needed for 2FE PA.
Error Message%AMDP2_FE-2-MISS : [chars], [chars] receive problem, CSR0=[hex]
Explanation The interface lost an incoming receive frame because a receive descriptor was not available.
Recommended Action The system should recover. No action is required.
Error Message%AMDP2_FE-2-NOISL : Interface [chars] does not support ISL
Explanation The interface cannot be configured as an ISL trunk.
Recommended Action Check the configuration.
Error Message%AMDP2_FE-3-BIC_FE_RESET : Reseting [chars]
Explanation The BIC FE interface is being reset.
Recommended Action No action is required.
Error Message%AMDP2_FE-3-GENERAL : [chars]
Explanation General C10K failure message.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%AMDP2_FE-3-NOINITBUFFPOOL : [chars] Failed to allocate Buffer Pools
Explanation System failed to alloacte Buffer Pools on initialization of AMD 79c972 MAC chip.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%AMDP2_FE-3-NOTAMDP2 : Device reported [hex]
Explanation The software could not recognize the interface chips.
Recommended Action Power down, reseat the interface card, and reboot. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%AMDP2_FE-3-OVERFLO : AMDP2/FE [chars], Receive overflow
Explanation While receiving a frame, the controller chip's local buffer transmitted insufficient data because data could not be transferred to DRAM fast enough to keep pace with its input rate. Normally, such a problem is temporary, depending on transient peak loads within the system.
Recommended Action The system should recover. No action is required.
Error Message%AMDP2_FE-3-OWNERR : AMDP2/FE [chars], Buffer ownership error, pak=[hex]
Explanation The software detected an error in descriptor ownership.
Recommended Action Try a later version of the software. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%AMDP2_FE-3-SPURIDON : AMDP2/FE [chars], Spurious IDON interrupt, CSR[dec]=[hex]
Explanation An illegal condition indicating initialization done has occurred.
Recommended Action Clear the interface. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%AMDP2_FE-3-TOOMANYPART : Bad packet with %d particles, pak=0x%x
Explanation The software detected an invalid packet.
Recommended Action Try a later version of the software. If the message recurs, call your technical support representative for assistance.
Error Message%AMDP2_FE-3-UNDERFLO : AMDP2/FE [chars], Transmit underflow
Explanation While transmitting a frame, the controller chip's local buffer received insufficient data because data could not be transferred to the chip fast enough to keep pace with its output rate. Normally, such a problem is temporary, depending on transient peak loads within the system.
Recommended Action The system should recover. No action is required.
Error Message%AMDP2_FE-4-BABBLE : AMDP2/FE [chars], Babble error
Explanation The transmitter has been on the channel longer than the time taken to transmit the largest frame.
Recommended Action The system should recover. No action is required.
Error Message%AMDP2_FE-4-SPURIOUS : AMDP2/FE [chars], Spurious interrupt error
Explanation An illegal condition encountered during initialization.
Recommended Action The system should recover. No action is required.
Error Message%AMDP2_FE-5-BIC_FE_RESET : Resetting [chars]
Explanation BIC FE interface resetting.
Recommended Action Information message only. No action is required.
Error Message%AMDP2_FE-5-COLL : AMDP2/FE [chars], Excessive collisions, TDR=[dec], TRC=[dec].
Explanation Ethernet/Fast Ethernet is seeing multiple collisions. This may occur under heavy loads.
Recommended Action The system should recover. No action is required.
Error Message%AMDP2_FE-5-CONFIGNOT : The Internal Ethernet Interface is not configurable
Explanation The internal Ehternet is for system use only.
Recommended Action No action is required.
Error Message%AMDP2_FE-5-EXCESSCOLL : [chars] TDR=[dec], TRC=[dec]
Explanation Ethernet or Fast Ethernet is seeing multiple collisions. This condition may occur under heavy loads. If an interface fails to allocate a slot in which it can transmit its frame without another collision for 16 times, it will not retry the operation. The frame is not transmitted and is marked as an excessive collision.
Recommended Action The system should recover. No action is required.
Error Message%AMDP2_FE-5-LATECOLL : AMDP2/FE [chars], Late collision
Explanation Late collisions occurred on the Ethernet/Fast Ethernet interface.
Recommended Action If the interface is Fast Ethernet, verify that both peers are in the same duplex mode. For regular Ethernet, the system should recover. No action is required.
Error Message%AMDP2_FE-5-LOSTCARR : AMDP2/FE [chars], Lost carrier. Transceiver problem?
Explanation The cable and/or transceiver is not connected.
Recommended Action Connect the cable and/or transceiver.
Error Message%AMDP2_FE-5-SUBIF : Subinterfaces are not supported on FastEthernet
Explanation There is currently no subinterface support on fast Ethernet.
Recommended Action No action is required.
Error Message%AMDP2_FE-6-EXCESSCOLL : %s TDR=%d, TRC=%d
Explanation Ethernet/Fast Ethernet is seeing multiple collisions. This may occur under heavy loads.
Recommended Action The system should recover. No action is required.
Error Message%ANCP_ISSU-2-GET_BUFFER : ANCP ISSU client failed to get buffer for message. Error: %d (%s)
Explanation The ANCP 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 Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show checkpoint client command and your pertinent troubleshooting logs.Error Message%ANCP_ISSU-2-INIT : ANCP ISSU client initialization failed to %s. Error: %d (%s)
Explanation The ANCP 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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%ANCP_ISSU-2-SEND_NEGO_FAILED : ANCP ISSU client failed to send negotiation message. Error: %d (%s)
Explanation The ANCP 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 Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show checkpoint client command and your pertinent troubleshooting logs.Error MessageExplanation An ISSU-compliant client transitions through a series of internal states. The ANCP 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 Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show issu session and show issu negotiated capability command and your pertinent troubleshooting logs.Error Message%ANCP_ISSU-2-SESSION_REGISTRY : ANCP ISSU client failed to register session information. Error: %d (%s)
Explanation The ANCP 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 Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show issu capability entries and show issu negotiated capability command and your pertinent troubleshooting logs.Error Message%ANCP_ISSU-3-CAP_INVALID_SIZE : ANCP ISSU client capability list is empty.
Explanation The ANCP ISSU client capability exchange list size is invalid.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the
show issu negotiated capability command and your pertinent troubleshooting logs.Error Message%ANCP_ISSU-3-CAP_NOT_COMPATIBLE : ANCP ISSU client capability exchange result incompatible.
Explanation The ANCP ISSU client capability exchange have negotiated as incompatible with the peer.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the
show issu negotiated capability command and your pertinent troubleshooting logs.( show issu negotiated capability )Error Message%ANCP_ISSU-3-INVALID_SESSION : ANCP ISSU client does not have a valid registered session.
Explanation The ANCP ISSU client does not have a valid registered session.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show issu session and show issu negotiated capability command and your pertinent troubleshooting logs.Error Message%ANCP_ISSU-3-MSG_NOT_COMPATIBLE_WITH_PEER : 'Message Type %d' is not supported by ANCP ISSU client at peer
Explanation The ANCP ISSU client at the peer supervisor is not compatible for this message type. The ANCP client will be marked as incompatible with the peer.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show issu message group and show issu session command and your pertinent troubleshooting logs.Error Message%ANCP_ISSU-3-MSG_NOT_OK : ANCP ISSU client 'Message Type %d' is not compatible
Explanation The ANCP ISSU client received an incompatible message from the peer device. The message cannot be processed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show message group and show issu negotiated version command and your pertinent troubleshooting logs.Error Message%ANCP_ISSU-3-MSG_SIZE : ANCP ISSU client failed to get the MTU for Message Type %d.Error: %d (%s)
Explanation The ANCP ISSU client failed to calculate the MTU for the specified message. The ANCP ISSU client is not able to send the message to the standby device.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show message group and show issu negotiated version command and your pertinent troubleshooting logs.Error Message%ANCP_ISSU-3-SESSION_UNREGISTRY : ANCP ISSU client failed to unregister session information. Error: %d (%s)
Explanation The ANCP ISSU client failed to unregister session information.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show issu session and show issu negotiated capability command and your pertinent troubleshooting logs.Error Message%ANCP_ISSU-3-TRANSFORM_FAIL : ANCP ISSU client %s transform failed for 'Message Type %d'. Error: %d (%s)
Explanation The ANCP 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 ANCP state between the active device and the standby device is not identical.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show issu session and show issu negotiated version command and your pertinent troubleshooting logs.AP Messages
The following are Authentication Proxy messages.
Error Message%AP-1-AUTH_PROXY_DDOS_ATTACK : Distributed DOS attack
Explanation This message indicates that the auth-proxy router is possibly under a Distributed DOS attack. It has received more than 512 HTTP connections with no data.
Recommended Action This is a potention DDOS attack.
Error Message%AP-1-AUTH_PROXY_DOS_ATTACK : Possible DOS attack from source IP-address %i| AuditSessionID %s
Explanation This message indicates that a host is continuously opening HTTP connections through the auth-proxy without sending data on them. This can potentially be a DOS attack.
Recommended Action This is a potention DOS attack the source should be shunned. It may also be a false alarm wherein a user is connecting to an HTTP server via a telnet like program to port 80.
Error Message%AP-1-AUTH_PROXY_RETRIES_EXCEEDED : IP-address %i has exceeded the maximum retry limit | AuditSessionID %s
Explanation This message indicates that a host has exceeded the maximum allowed limit for login-attempts. The host may be infected by a virus which is continuously sending HTTP requests.
Recommended Action This maybe a potential DOS attack and the source should be shunned. It may also be a false alarm wherein the user is making legitimate attempts to log in.
Error Message%AP-1-POSTURE_POLICY_ERROR : POLICY %s| POLICYNAME %s| IP %i| ERROR | AuditSessionID %s
Explanation This message indicates that the specified policy was not applied for the given host IP due to the reason specified as Error.
Recommended Action In case of HOST ACL policy verify if an input access list is defined and configured on interface. While for URL REDIRECT ACL policy needs url-redirect VSA to have an assoicated access control list url-redirect-acl VSA, that is used to determine HTTP redirect critera. HTTP packets matching the access control list will be subjected to redirection. In case the 'url-redirect-acl' access control list is not specified or is not configured, the host will not be setup for HTTP redirection.
Error Message%AP-4-AMESSAGE : This is a non-sense message
Explanation To be filled out later
Recommended Action To be filled out later
Error Message%AP-4-AUTH_PROXY_NOMEM : Sufficient memory was not available to %s
Explanation There was no encuogh memory to perform the specified operation.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%AP-4-POSTURE_EXCEED_MAX_INIT : Exceeded maximum limit (%d) on entires in authentication proxy posture cache in initializing state
Explanation This message indicates that the number of entires in authentication proxy posture cache which are in INIT state has exceeded the maximum limit.
Recommended Action This may be a potential Denial of Service attack.
Error Message%AP-5-AP_AAA_DOWN : Event=AAA %s. HOST %i| POLICY %s %s | AuditSessionID %s
Explanation This messages notifies that AAA servers defined by the methodlist are unreachable for the given host and the policy being applied.
Recommended Action The failure is due to unreachable AAA servers.
Error Message%AP-6-AUTH_PROXY_AUDIT_START : initiator (%i) start| AuditSessionID %s
Explanation This message documents the transaction log of network activities of auth-proxy. The message is issued at the start of each auth-proxy cache and it records the source addresses.
Recommended Action This message is for informational purposed only, and can be used to collect the basic accounting for the proxyied sessions.
Error Message%AP-6-AUTH_PROXY_AUDIT_STOP : initiator (%i) send %u packets %u bytes; duration time %s| AuditSessionID %s
Explanation This message documents the transaction log of network activities of auth-proxy. The message is issued at the stop of each auth-proxy cache and it records the source addresses, the number of bytes transmitted by the client, and the cache duration time.
Recommended Action This message is for informational purposed only, and can be used to collect the basic accounting for the proxyied caches.
Error Message%AP-6-FALLBACK_REQ : IP %i| MAC %u| PROFILE_NAME %s| EVENT %s| AuditSessionID %s
Explanation This message indicates a fallback to authproxy has been initiated/terminated for the given host.
Recommended Action No action required
Error Message%AP-6-POSTURE_DOWNLOAD_ACL : Send AAA request to download (%s) named access control list
Explanation This message indicates the router has send a request to AAA to get the contents of the specified downloadable access contol list.
Recommended Action This is an informational message and no action is required
Error Message%AP-6-POSTURE_POLICY : %s %s (%s) policy for host (%i)
Explanation This message specifies the policy enforced or removed for the specified host. The policy could be either an access control list or a URL to which any intercepted HTTP traffic would be redirected.
Recommended Action This is an informational message and no action is required
Error Message%AP-6-POSTURE_START_VALIDATION : IP %i| Interface %s| AuditSessionID %s
Explanation This message indicates the router has created an entry for the host in authentication porxy posture cache and has initiated posture validation process.
Recommended Action This is an informational message and no action is required
Error Message%AP-6-POSTURE_STATE_CHANGE : IP %i| STATE %s| AuditSessionID %s
Explanation This message indicates the change of posture validation state of the specified host in the authentication proxy posture validation cache.
Recommended Action This is an informational message and no action is required.
APPFW Messages
The following are APPFW for HTTP subsystem messages.
Error Message%APPFW-3-HTTP_APPFW_CONF_ERROR : Application Firewall configuration error -- [chars]
Explanation An error has occurred during Application Firewall configuration.
Recommended Action This message indicates an error during firewall configuration and may be a potential security problem.
Error Message%APPFW-3-HTTP_MAX_REQ_EXCEED : Maximum of [dec] unanswered HTTP requests exceeded from [IP_address]:[dec] to [IP_address]:[dec]
Explanation 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.
Error Message%APPFW-3-HTTP_MAX_REQ_EXCEEDED : Number of unanswered HTTP requests exceeded the limit [dec] -[chars]
Explanation The number of unanswered HTTP requests has exceeded the specified limit.
Recommended Action This message is informational only, but may indicate a security problem.
Error Message%APPFW-4-HTTP_ARG_LENGTH : HTTP arguments length ([dec]) out of range -[chars]
Explanation The length of the HTTP argument has exceeded the configured threshold.
Recommended Action This message is informational only, but may indicate a security problem.
Error Message%APPFW-4-HTTP_ARG_REGEX_MATCHED : ARG regex ([chars]) matched -[chars]
Explanation The argument of an HTTP request has matched the specified configured regular expression.
Recommended Action This message is informational only, but may indicate a security problem.
Error Message%APPFW-4-HTTP_BODY_REGEX_MATCHED : Body regex ([chars]) matched -[chars]
Explanation The body of an HTTP packet has matched the specified configured regular expression.
Recommended Action This message is informational only, but may indicate a security problem.
Error Message%APPFW-4-HTTP_CONTENT_LENGTH : Content length ([int]) out of range -[chars]
Explanation The specified content or body length is not in the configured range.
Recommended Action This message is informational only, but may indicate a security problem.
Error Message%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.
Error Message%APPFW-4-HTTP_CONT_TYPE_MATCH : Sig:[dec] Content type not found - [chars] [chars] from [IP_address]:[dec] to [IP_address]:[dec]
Explanation 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.
Error Message%APPFW-4-HTTP_CONT_TYPE_MISMATCH : Content type ([chars]) in the response does not match the Accept type in the request -[chars]
Explanation The specified content type in the response does not match the accept type that was filed in the request.
Recommended Action This message is informational only, but may indicate a security problem.
Error Message%APPFW-4-HTTP_CONT_TYPE_SIZE : Sig:[dec] Content size [int] out of range - [chars] [chars] from [IP_address]:[dec] to [IP_address]:[dec]
Explanation 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.
Error Message%APPFW-4-HTTP_CONT_TYPE_UNKNOWN : Content type not known -[chars]
Explanation The received content type does not match against the system support list of content types.
Recommended Action This message is informational only, but may indicate a security problem.
Error Message%APPFW-4-HTTP_CONT_TYPE_VERIFY : Sig:[dec] Content type does not match the specified type - [chars] [chars] from [IP_address]:[dec] to [IP_address]:[dec]
Explanation 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.
Error Message%APPFW-4-HTTP_CONT_TYPE_VIOLATION : Content magic does not match the specified content type ([chars]) -[chars]
Explanation The content-type magic in the body does not match the content-type value in the header.
Recommended Action This message is informational only, but may indicate a security problem.
Error Message%APPFW-4-HTTP_DEOBFUSCATE : Sig:[dec] Deobfuscation signature detected - [chars] [chars] from [IP_address]:[dec] to [IP_address]:[dec]
Explanation 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.
Error Message%APPFW-4-HTTP_DEOBFUSCATION : Deobfuscation signature ([dec]) detected -[chars]
Explanation The HTTP message has violated the de-obfuscate application firewall inspection rule.
Recommended Action This message is informational only, but may indicate a security problem.
Error Message%APPFW-4-HTTP_HDR_FIELD_LENGTH : Header field ([chars]) length ([dec]) out of range -[chars]
Explanation The length of the configured HTTP header field has exceeded the configured threshold.
Recommended Action This message is informational only, but may indicate a security problem.
Error Message%APPFW-4-HTTP_HDR_FIELD_REGEX_MATCHED : Header field ([chars]) matched -[chars]
Explanation An HTTP packet has matched a configured header field and associated regular expression.
Recommended Action This message is informational only, but may indicate a security problem.
Error Message%APPFW-4-HTTP_HDR_REGEX_MATCHED : Header regex ([chars]) matched -[chars]
Explanation An HTTP message has matched one of the configured regular expressions.
Recommended Action This message is informational only, but may indicate a security problem.
Error Message%APPFW-4-HTTP_HEADER_COUNT : Number of header fields ([dec]) exceeded the limit -[chars]
Explanation The number of header fields in an HTTP packet has exceeded the configured limit.
Recommended Action This message is informational only, but may indicate a security problem.
Error Message%APPFW-4-HTTP_HEADER_LENGTH : HTTP Header length ([int]) out of range -[chars]
Explanation The specified header length exceeds the configured threshold.
Recommended Action This message is informational only, but may indicate a security problem.
Error Message%APPFW-4-HTTP_JAVA_APPLET : HTTP Java Applet detected -[chars]
Explanation An HTTP Java applet was detected in in a response.
Recommended Action This message is informational only, but may indicate a security problem.
Error Message%APPFW-4-HTTP_MATCH_REQ_RESP : Sig:[dec] Content type: [chars] does not match the Accept-Type from [IP_address]:[dec] to [IP_address]:[dec]
Explanation 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.
Error Message%APPFW-4-HTTP_MAX_HDR_LEN : Sig:[dec] HTTP Header length exceeded. Received [int] byte of header - [chars] [chars] from [IP_address]:[dec] to [IP_address]:[dec]
Explanation 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.
Error Message%APPFW-4-HTTP_MAX_URI_LEN : Sig:[dec] HTTP URI length exceeded. Received [int] byte of URL - [chars] [chars] from [IP_address]:[dec] to [IP_address]:[dec]
Explanation 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.
Error Message%APPFW-4-HTTP_METHOD : HTTP method ([chars]) matched -[chars]
Explanation The specified HTTP method matches a configured regular expression.
Recommended Action This message is informational only, but may indicate a security problem.
Error Message%APPFW-4-HTTP_PORT_MISUSE_IM : Sig:[dec] HTTP Instant Messenger detected - [chars] [chars] from [IP_address]:[dec] to [IP_address]:[dec]
Explanation 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.
Error Message%APPFW-4-HTTP_PORT_MISUSE_P2P : Sig:[dec] HTTP Peer-to-Peer detected - [chars] [chars] from [IP_address]:[dec] to [IP_address]:[dec]
Explanation 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.
Error Message%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.
Error Message%APPFW-4-HTTP_PORT_MISUSE_TYPE_IM : HTTP Instant Messenger ([chars]) detected -[chars]
Explanation The HTTP port is being used for IM applications.
Recommended Action This message is informational only, but may indicate a security problem.
Error Message%APPFW-4-HTTP_PORT_MISUSE_TYPE_P2P : HTTP Peer-to-Peer ([chars]) detected -[chars]
Explanation The HTTP port is being used for P2P applications.
Recommended Action This message is informational only, but may indicate a security problem.
Error Message%APPFW-4-HTTP_PORT_MISUSE_TYPE_TUNNEL : HTTP Tunnel ([chars]) detected -[chars]
Explanation The HTTP port is being used for tunneling.
Recommended Action This message is informational only, but may indicate a security problem.
Error Message%APPFW-4-HTTP_PROTOCOL_VIOLATION : HTTP protocol violation ([dec]) detected -[chars]
Explanation The HTTP message violates the strict HTTP application firewall inspection rule.
Recommended Action This message is informational only, but may indicate a security problem.
Error Message%APPFW-4-HTTP_REPEATED_HDR_FIELDS : Multiple occurrences of the header field ([chars]) -[chars]
Explanation An HTTP header has multiple occurrences of the same specified header field.
Recommended Action This message is informational only, but may indicate a security problem.
Error Message%APPFW-4-HTTP_REQ_METHOD_EXT : Sig:[dec] HTTP Extension method illegal - [chars] '[chars]' from [IP_address]:[dec] to [IP_address]:[dec]
Explanation 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.
Error Message%APPFW-4-HTTP_REQ_METHOD_RFC : Sig:[dec] HTTP RFC method illegal - [chars] '[chars]' from [IP_address]:[dec] to [IP_address]:[dec]
Explanation 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.
Error Message%APPFW-4-HTTP_STLINE_REGEX_MATCHED : Status line regex ([chars]) matched -[chars]
Explanation The HTTP status line of a response packet has matched one of the configured regular expressions.
Recommended Action This message is informational only, but may indicate a security problem.
Error Message%APPFW-4-HTTP_STRICT_PROTOCOL : Sig:[dec] HTTP protocol violation detected - [chars] [chars] from [IP_address]:[dec] to [IP_address]:[dec]
Explanation 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.
Error Message%APPFW-4-HTTP_TRANSFER_ENCODE : Sig:[dec] HTTP Transfer encoding violation detected - [chars] [chars] from [IP_address]:[dec] to [IP_address]:[dec]
Explanation 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.
Error Message%APPFW-4-HTTP_TRANSFER_ENCODING : HTTP Transfer encoding ([chars]) detected -[chars]
Explanation The HTTP message violates the transfer encoding application firewall inspection rule.
Recommended Action This message is informational only, but may indicate a security problem.
Error Message%APPFW-4-HTTP_URI_LENGTH : HTTP URI length ([int]) out of range -[chars]
Explanation The Universal Resource Indicator length exceeds the configured threshold.
Recommended Action This message is informational only, but may indicate a security problem.
Error Message%APPFW-4-HTTP_URI_REGEX_MATCHED : URI regex ([chars]) matched -[chars]
Explanation The Universal Resource Indicator of an HTTP request has matched one of the configured regular expressions.
Recommended Action This message is informational only, but may indicate a security problem.
Error Message%APPFW-6-HTTP_SESSION_AUDIT_TRAIL : HTTP session initiator [IP_address]:[dec] sends [dec] bytes - responder [IP_address]:[dec] sends [dec] bytes
Explanation 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.
Error Message%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.
Error Message%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.
Error Message%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.
Error Message%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.
Error Message%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.
Error Message%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.
Error Message%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.
Error Message%APPFW-6-P2P_PORT_HOP : [chars] using [chars] port - [chars]
Explanation By examining the payload, a peer-to-peer protocol has been detected using a non-standard port or re-using the standard port for another protocol.
Recommended Action This message is informational only, but may indicate a security problem with peer-to-peer protocol attempting to bypass the firewall.
Error Message%APPFW-6-P2P_SERVICE : Identified [chars] [chars] [chars] - [chars]
Explanation A peer-to-peer protocol has been detected on the session with the specified protocol and sub-protocol. Also indicates if the session action configured for that session performed a reset.
Recommended Action This message is informational only and can be used to collect the information about sessions inspected for peer-to-peer protocols.
Error Message%APP_PRINTF--DONT_USE_PRINTF : Application: %s ( %s )
Explanation These messages are from apps that uses printfs in their code.
Recommended Action UNAVAILABLE
APS Messages
Error Message%APS-1-NO_ACTIVE : No Active Port In Group %s
Explanation After an active interface failure, the system switches over to the standby interface if APS has been enabled. This message is posted if after a switchover the system finds no active interface, i.e. both working and protection interfaces are found to be nonoperational.
Recommended Action Isolate the cause of failure on both working and protection interfaces.
Error Message%APS-2-CHNLCFGMM : Group %s: Channel Config Mismatch
Explanation Working and Protection interfaces do not point to the same path on local and remote network elements
Recommended Action Configure working and protection interfaces to point to the same path on local and remote network elements
Error Message%APS-2-CHNLMISMATCH : Group %s: Channel Mismatch - %s
Explanation This message is posted by the local network element, if the received bridged channel number (in the REVERSE-REQUEST from the remote network element) does not match the request channel number in the APS request sent by the local network element. This message is relevant only for bidirectional operation. For 1+1 APS, this message should normally be not posted unless a) the transmit bridged channel number in the REVERSE-REQUEST from remote is somehow corrupted or b) there is a bug in the APS software itself.
Recommended Action Check for any failures on the APS commnication channel. If APS communication channel is operational, contact Cisco TAC.
Error Message%APS-2-FEPF : Group %s: Far End Prot Failure - %s
Explanation This message is posted by the local network element if it detects a Far End Protection Failure condition. The Far End Protection Failure condition is detected if the Far End Protection Defect count exceeds a threshold. A Far End Protection Defect is detected when the local network element receives a remote APS message with request set to SF (Signal Fail) and request channel set to 0 (NULL or Protection channel).
Recommended Action Isolate the cause of failure on the protection channel on the remote network element.
Error Message%APS-2-INITSYS : [chars]
Explanation A software error occurred during initialization of the APS subsystem.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%APS-2-INTRNLERR : [chars] [dec]
Explanation A software error occurred during initialization of the APS subsystem.
Recommended Action No action is required.
Error Message%APS-2-MODEMISMATCH : Group %s: Mode Mismatch - %s
Explanation This message is posted by the local network element if the local APS group has been configured for bidirectional operation but the associated remote APS group has been configured for unidirectional operation. This message indicates that a mismatch in mode (unidirectional or bidirectional) has been detected.
Recommended Action Configure the remote APS group for bidirectional operation.
Error Message%APS-2-NOSOCKET : Failed To Open Socket
Explanation This message is posted when the APS subsystem fails to create a UDP socket for exchanging APS channel protocol messages over an APS message channel configured for IP. This error usually is caused by low memory in the system.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%APS-2-PSBF : Group %s: Prot Switch Byte Failure - %s
Explanation This message is posted by the local network element if a Protection Switch Byte Failure is detected. A Protection Switch Byte Failure is detected when the Protection Switch Byte defect count exceeds a threshold. A Protection Switch Byte Defect is detected when one of the following happens: 1) The remote APS request is not one of the supported requests. 2) The remote APS request channel number is invalid. For 1+1 APS, the channel number must be 0 or 1. 3) Operation is bidirectional and neither local nor remote network element is sending a REVERSE-REQUEST, and the remote APS request is of lower priority than the local APS request. 4) Operation is bidirectional and the sequence number in the remote APS REVERSE-REQUEST does not match the sequence number of the most recent APS request sent by the local network element. This error is posted if a) the APS request is somehow corrupted, or b) there is a bug in the APS software itself or c) if the APS communication between two network elements is broken, e.g. local network element can send and receive, whereas the remote network element can send but not receive.
Recommended Action Check for failures on the APS communication channel. Isolate the cause for such failures and restore the communication channel to working condition
Error Message%APS-3-PORT_FAIL : %s Port Fail On %s
Explanation This message is posted when APS subsystem receives a port fail indication from the driver subsystem. This message indicates that the specified interface has detected a failure condition (e.g. Loss Of Light).
Recommended Action Isolate the cause of the failure and restore the interface to normal operational condition.
Error Message%APS-5-CMDFAIL : Controller [chars], execution of '[chars]' command failed.
Explanation The APS switch command that was entered by the user has been rejected.
Recommended Action Review the controller information and, if required, reenter the command.
Error Message%APS-5-STATUS : Controller [chars], fiber port [dec] is [chars].
Explanation The specified port has changed its state to either functional or nonfunctional.
Recommended Action No action is required.
Error Message%APS-5-SWITCH : Controller [chars], fiber port [dec] is now active port.
Explanation The specified port has become the active fiber port and has started to transmit traffic.
Recommended Action No action is required.
Error Message%APS-6-ADJUSTMODE : Group %s: Mode Mismatch - %s
Explanation This message is posted by the local network element if the local APS group has been configured for bidirectional operation but the associated remote APS group has been configured for unidirectional operation. This message is posted after the local network element detects the mismatch and changes the operation to unidirectional.
Recommended Action Configure the remote APS group for bidirectional operation.
Error Message%APS-6-AUTOFOVER : Auto-Failover - Group %s
Explanation This message is posted if APS hardware successfully switched over to the standby interface after the failure of the active interface. This is informational only.
Recommended Action Isolate the cause of failure of the previous active interface and restore it to a working condition.
Error Message%APS-6-BIDIRSWCH : Group [chars]: Remote Request - [chars]
Explanation This message is posted by the local network element after an APS switchover that is triggered by an APS request from the remote network element.
Recommended Action This is an informational message only. No action is required.
Error Message%APS-6-CHNLACTIVE : Group [chars] - [chars] channel is now ACTIVE
Explanation The channel that was a standby channel is now the active channel. This message is informational only.
Recommended Action No action is required.
Error Message%APS-6-DISAUTFOV : Disable Auto-Failover On [chars]
Explanation APS has disabled autofailover for the indicated group.
Recommended Action Enter the show aps group name command to gather data that might help identify the nature of the error. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show aps group name, show logging, and show tech-support commands and your pertinent troubleshooting logs.
Error Message%APS-6-ENAUTFOVR : Enable Auto-Failover On [chars]
Explanation This message is posted when APS software enables hardware to perform APS actions for failures detected by the hardware. This is an informational only. No action is required.
ARAP Messages
The following are the AppleTalk Remote Access Protocol (ARAP) messages.
Error Message%ARAP-0-DEFAULT : TTY [dec]
Explanation An internal software error has occured.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ARAP-0-NOTNULLRESEND : TTY [dec]
Explanation An internal software error has occured.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ARAP-0-NULLRESEND : TTY %d
Explanation An internal software error occured.
Recommended Action Report this error to you technical support representative.
Error Message%ARAP-0-VSERROR : TTY [dec]: VS queued error
Explanation An internal software error occured.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ARAP-0-WAITBADMSG : TTY %d: arg msg bad %x
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.
Error Message%ARAP-2-NOLOG : TTY [dec]: Could not malloc log
Explanation Memory not available for internal MNP4 logging.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ARAP-3-0 : TTY [dec]: arap callback aborted
Explanation ARAP callback has ended because the system received an unexpected message during the MNP4 link setup.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ARAP-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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%ARAP-3-BADCONFIG : TTY %d: unhandled configuration command
Explanation A configuration command was not recognized.
Recommended Action Check the configuration file on the server for any invalid configuration commands.
Error Message%ARAP-3-BADPAK : TTY %d: Bad packet type in arap_send_msg
Explanation Internal data structures are corrupted.
Recommended Action Check for abnormally high CPU usage.
Error Message%ARAP-3-REMOTEERROR : TTY [dec]: arap input error
Explanation An ARAP connection was terminated without a known cause.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%ARAP-3-TIMEOUT : TTY [dec]: arap expected message timeout
Explanation The software timed out during the MNP4 link setup.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%ARAP-4-CONFAILED : TTY %d: ARAP connection failed: %s
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.
Error Message%ARAP-4-NOEXTTACACS : TTY %d: 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.
Error Message%ARAP-5-INITCONFUSED : TTY %d: ARAP unexpected initialization packet %s
Explanation The startup negotiation between a client and the ARA protocol server fell out of order. If this message is received sporadically, it indicates line noise.
Recommended Action If this message recurs, reinstall the ARA client software.
Error Message%ARAP-5-PAKINVALID : TTY %d: ARAP invalid packet received
Explanation A corrupted packet reached the ARA protocol code.
Recommended Action Check for excessive CPU usage or excessive line noise.
Error Message%ARAP-6-ADDRFREE : TTY [dec]: ARAP ended for user [chars]; address [atalk_net]; [dec] seconds connected
Explanation This message appears only when ARA protocol logging is configured. The message indicates that an ARA protocol user has logged out.
Recommended Action No action is required.
Error Message%ARAP-6-ADDRUSED : TTY [dec]: ARAP started for user [chars]; address [dec].[dec]
Explanation This message appears only when ARA protocol logging is configured. The message notes that an ARA protocol user has logged in.
Recommended Action No action is required.
Error Message%ARAP-6-BADEXIT : TTY %d: exited user %s: %s
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.
Error Message%ARAP-6-LRPHASERROR : TTY %d: 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.
Error Message%ARAP-6-MAXRESENDS : TTY %d
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.
Error Message%ARAP-6-MNP4RCVDISC : TTY [dec]: MNP4 input disconnect
Explanation This indicates that the router received a disconnect request from the remote Macintosh client.
Recommended Action No action is required.
Error Message%ARAP-6-MNP4T401 : TTY [dec]: T401 [dec] baud rate [dec]
Explanation This message indicates that the router received MNP4 connection request. MNP4 acknowledgment timer value is also indicated.
Recommended Action No action is required.
Error Message%ARAP-6-RCVGIANT : TTY %d: 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.
Error Message%ARAP-6-RCVNOPAK : TTY %d: Receive getbuffer failure. dropping frame
Explanation No buffer exists for an incoming packet.
Recommended Action Examine buffer usage statistics. Possibly more memory is required.
Error Message%ARAP-6-RESENDSLOW : TTY %d
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.
Error Message%ARAP-6-TIMERERROR : TTY %d: 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.
Error Message%ARAP-6-XTICKLE : TTY %d: exited user %s: Other side stopped answering ARAP tickles (mnp4 pak resent %d mnp4 pak sent %d last %d now %d)
Explanation The router disconnected as the remote Macintosh client stopped sending ARAP tickle or data packets.
Recommended Action To determine the cause of the disconnection, correlate the receipt of this message with the user problem reports.
ARCHIVE_CONFIG Messages
Error Message%ARCHIVE_CONFIG-4-ARCHIVE_DELETE_FAILED : Delete of a previously saved archive of the router configuration could not be completed.
Explanation The router could not delete a 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 No action is required.
Error Message%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.
Error Message%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 No action is required.
Error Message%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 No action is required.
ARCHIVE_DIFF Messages
Error Message%ARCHIVE_DIFF-3-DIFF_CMD_INIT_FAILED : Failed to register the special case [chars] command:'[chars]' during initialization. Config Diff and Rollback cannot be used as a result of this error.
Explanation An internal software error occurred during initialization - Config Diff and Rollback cannot be used as a result of this error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%ARCHIVE_DIFF-3-DIFF_INIT_FAILED : Could not initialize the Config Diff and Rollback subsystem
Explanation An internal software error occurred during initialization. Config Diff and Rollback cannot be used as a result of this error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_BACKUP : Backing up current running config to [chars]
Explanation The current running configuration is saved so that when the timer expires, if no confirmation has been received from user to confirm what was configured, the system will rollback to the saved configuration.
Recommended Action This message DOES NOT denote any error condition. It is a part of the normal operation of the rollback confirmed change.
Error Message%ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_CANCEL : User: [chars]: Rollback Confirmed Change is cancelled due to [chars] failure
Explanation Rollback Confirmed Change is normally configured along with other configuration operations, such as 'config term' or 'config replace'. If those operations failed, Rollback Confirmed Change should not be activated.
Recommended Action Remove the error condition and try again later.
Error Message%ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_CONFIRM : User: [chars]: Confirm the configuration change
Explanation The configuration change is confirmed. The timer for rolling to the previously saved configuration is cancelled
Recommended Action This message DOES NOT denote any error condition. It is a part of the normal operation of the rollback confirmed change.
Error Message%ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_RESET_ABSTIMER : User: [chars]: Reset Rollback Confirmed Change timer(absolute) to [int] minute
Explanation Reset Rollback Confirmed Change timer(absolute) to a new value.
Recommended Action This message DOES NOT denote any error condition. It is a part of the normal operation of the rollback confirmed change.
Error Message%ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_RESET_IDLETIMER : User: [chars] Reset Rollback Confirmed Change timer(idle) to [int] minute
Explanation Reset Rollback Confirmed Change timer(idle) to a new value.
Recommended Action This message DOES NOT denote any error condition. It is a part of the normal operation of the rollback confirmed change.
Error Message%ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_REVERTNOW : User: [chars]: Rollback immediately.
Explanation Rollback immediately and cancel the timer.
Recommended Action This message DOES NOT denote any error condition. It is a part of the normal operation of the rollback confirmed change.
Error Message%ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_ROLLBACK_RETRY : Failed to acquire configuration lock. Rollback did not start. Schedule to retry in 5 minutes
Explanation Failed to acquire configuration lock. Rollback did not start. In this case, retry will be scheduled.
Recommended Action This message DOES NOT denote any error condition. It is a part of the normal operation of the rollback confirmed change.
Error Message%ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_ROLLBACK_START : Start rolling to: [chars]
Explanation The timer for Rollback Confirmed Change has expired. System will rollback to the previously saved config.
Recommended Action This message DOES NOT denote any error condition. It is a part of the normal operation of the rollback confirmed change.
Error Message%ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_START_ABSTIMER : User: [chars]: Scheduled to rollback to config [chars] in [int] minutes
Explanation The system will wait for you to confirm that you wish to keep what was configured until the timer expires. If the confirmation is not received in time, the router will rollback.
Recommended Action This message DOES NOT denote any error condition. It is a part of the normal operation of the rollback confirmed change.
Error Message%ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_START_IDLETIMER : User: [chars]: Scheduled to rollback to config [chars] if session has been idle for [int] minutes
Explanation The system will wait for you to confirm that you wish to keep what was configured until the timer expires. If the confirmation is not received in time, the router will rollback.
Recommended Action This message DOES NOT denote any error condition. It is a part of the normal operation of the rollback confirmed change.
Error Message%ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_WARNING_ABSTIMER : System will rollback to config [chars] in one minute. Enter 'configure confirm' if you wish to keep what you've configured
Explanation Rollback will start in one minute. You could enter the configure confirm command if you wish to keep what has been configured.
Recommended Action This message DOES NOT denote any error condition. It is a part of the normal operation of the rollback confirmed change.
Error Message%ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_WARNING_IDLETIMER : User [chars] on tty [dec] has been idle for [int] minutes. System will rollback to config [chars] in oneminute if it continues to be idle. Enter 'configure confirm' if you wish to keep what you've configured
Explanation Rollback will start in one minute. You can enter the configure confirm command if you wish to keep what has been configured.
Recommended Action This message DOES NOT denote any error condition. It is a part of the normal operation of the rollback confirmed change.
Error Message%ARCHIVE_ISSU-2-GET_BUFFER : Archive ISSU client failed to get buffer for message. Error: %d (%s)
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 Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show checkpoint client command and your pertinent troubleshooting logs.Error Message%ARCHIVE_ISSU-2-INIT : Archive ISSU client initialization failed to %s. Error: %d (%s)
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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%ARCHIVE_ISSU-2-SEND_NEGO_FAILED : Archive ISSU client failed to send negotiation message. Error: %d (%s)
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 Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show checkpoint client command and your pertinent troubleshooting logs.Error Message%ARCHIVE_ISSU-2-SESSION_NEGO_FAIL_START : Failed to start Archive ISSU session negotiation. Error: %d (%s)
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 Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show issu session command and your pertinent troubleshooting logs.( show issu session )Error Message%ARCHIVE_ISSU-2-SESSION_REGISTRY : Archive ISSU client failed to register session information. Error: %d (%s)
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 Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show issu capability entries and show issu session and show issu negotiated capability commands and your pertinent troubleshooting logs.Error Message%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 Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show issu capability entries and show issu session and show issu negotiated capability commands and your pertinent troubleshooting logs.Error Message%ARCHIVE_ISSU-3-MSG_NOT_OK : Archive ISSU client 'Message Type %d' is not compatible
Explanation The Archive ISSU client received an incompatible message from the peer device. The message cannot be processed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show issu message group, show issu session and show issu negotiated version commands and your pertinent troubleshooting logs.Error Message%ARCHIVE_ISSU-3-MSG_SIZE : Archive ISSU client failed to get the MTU for Message Type %d.Error: %d (%s)
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 Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show issu message group, show issu session and show issu negotiated version commands and your pertinent troubleshooting logs.Error Message%ARCHIVE_ISSU-3-SESSION_UNREGISTRY : Archive ISSU client failed to unregister session information. Error: %d (%s)
Explanation The Archive ISSU client failed to unregister session information.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show issu message group, show issu session and show issu negotiated capability commands and your pertinent troubleshooting logs.Error Message%ARCHIVE_ISSU-3-TRANSFORM_FAIL : Archive ISSU client %s transform failed for 'Message Type %d'. Error: %d (%s)
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 Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show issu session and show issu negotiated version commands and your pertinent troubleshooting logs.ARP Messages
Error Message%ARP-3-ARPADJ : Internal software error during updating CEF Adjacency for ARP entry for [IP_address] on [chars]
Explanation An internal software error has occurred during updating CEF Adjacency.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs
Error Message%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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ARP-3-ARPINVALIDEENTRY: ARP system internal error. Returns NULL arp entry on node
Explanation An internal software error occurred in the Address Resolution Protocol (ARP) subsystem causing a NULL ARP entry.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ARP-4-ARPLEARNCROSS : [int] Learned ARP entries are installed in the ARP table and reached the max limit
Explanation The number of dynamically learned ARP entries has reached a preconfigured maximum limit in the ARP table.
Recommended Action Inspect the ARP entries on the interface. If they are valid entries, either increase the configured maximum limit or reconfigure the network to reduce ARP peers.
Error Message%ARP-4-ARPLEARNTHRES : Learned ARP entries have reached to threshold level [int]
Explanation The number of unconfigured learned ARP entries has reached a preconfigured threshold, indicating a possible misconfiguration or a DOS attack.
Recommended Action Inspect the ARP entries on the interface. If they are valid entries, either increase the configured maximum limit or reconfigure the network to reduce ARP peers.
Error Message%ARP-4-NULL_SRC_MAC : NULL MAC address from [IP_address] on [chars]
Explanation The application or peer tried to insert entry with NULL SRC MAC.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%ARP-6-ARPLEARNRESUME : Resuming Learn ARP entries to install in ARP table.
Explanation The number of dynamically learned ARP entries is in range of permit threshold value. The system is allowing new learned ARP entries to install in the ARP table.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
AS5350 Messages
Error Message%AS5350-1-IMAGE_UNSUPPORTED : Image not supported on this platform!
Explanation The last Cisco IOS Software for AS5350, AS5400 (non XM) and AS5400HPX would be 12.4(15)T. IOS 12.4(20)T and higher will operate on the AS5400XM and AS5350XM only.
Recommended Action Install the software image prior to 12.4(20)T.
AS5400 Messages
The following are AS5400 messages.
Error Message%AS5400-0-INCOMPATIBLE_IMAGE : 12.2 mainline images are not compatible with the AS5400HPX system.
Explanation 12.2 mainline images are not compatible with the AS5400HPX system.
Recommended Action Load an image compatible with the system.
Error Message%AS5400-1-DFC_ERR : DFC [dec]: Detected PCI [chars] Error, CSR=[hex]
Explanation A PCI error that was caused by a hardware failure has been detected on the DFC. The Cisco IOS software will power down this DFC and clean up the associated system data structures.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%AS5400-1-IMAGE_UNSUPPORTED : Image not supported on this platform!
Explanation The last Cisco IOS Software for AS5350, AS5400 (non XM) and AS5400HPX would be 12.4(15)T. IOS 12.4(20)T and higher will operate on the AS5400XM and AS5350XM only.
Recommended Action Install the software image prior to 12.4(20)T.
Error Message%AS5400-1-NVRAM : [chars]
Explanation An error has occurred during NVRAM functions.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%AS5400-1-NVRAM_INT_LEVEL : [chars] [dec]
Explanation Performing NVRAM erase/write functions with a non-zero interrupt level.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%AS5400-1-OLD_FIRMWARE : [chars]
Explanation The specified component should have the latest HW revision. If the hardware revision is not the latest, then it needs to be updated to the version specified in this message.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%AS5400-1-UNINSTALLED_MASKED_INT : Uninstalled or masked interrupt: interrupt status [hex] mask [hex] vector [hex]
Explanation The system detected an uninstalled or masked interrupt.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%AS5400-1-UNKNOWN_DFC_INT : Unknown DFC interrupt: DFC slot no [dec], interrupt [dec]
Explanation An unknown DFC interrupt is detected.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%AS5400-1-UNKNOWN_INT : Unknown interrupt: interrupt [dec]
Explanation The system detected an unknown interrupt.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%AS5400-1-UNKNOWN_ISR : Unknown ISR : interrupt mask [hex]
Explanation An Interrupt Service Routine has never been installed for the interrupt mask.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter at https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%AS5400-3-HW_ERROR : NULL
Explanation A DFC hardware error has been detected. The Cisco IOS software will power down this DFC and clean up the associated data structures.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%AS5400-3-RTC_TIMEOUT : [chars] to onboard Real Time Clock timed out
Explanation A timeout occurred while reading or writing to the onboard Real Time Clock through the SMBUS.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%AS5400_ENVM-1-CAN_NOT_POWER_ON_DFC : Can't power on DFC on slot %d for unknown reason.
Explanation Powering on a DFC failed.
Recommended Action Check the power plug to the DFC on the slot. If still fail, unplug the DFC and do diagnostic on it.
Error Message%AS5400_ENVM-1-DFC_BUSYOUT : All DFCs are busy out due to board over temperature.
Explanation The System experienced an Over Temperature condition.
Recommended Action For AS5400, all DFCs are busy out to prevent the DFCs from damaging and to cool down the temperature. Check air conditioning and the surrounding of the AS5400 box. A customer should type 'show environment' to display temperature data and compare with temperature meter. If really fails, call Cisco to replace the temperature sensor
Error Message%AS5400_ENVM-1-DFC_POWER_DOWN : A DFC is powered down due to board over-temperature. Slot: %d, Type: %s
Explanation The System experienced an over-temperature condition.
Recommended Action For AS5400, a DFC is powered down to prevent the DFC from damaging and to cool down the temperature. Check air conditioning and the surrounding of the AS5400 box. A customer should type 'show environment' to display temperature data and compare with temperature meter. If really fails, call Cisco to replace the temperature sensor
Error Message%AS5400_ENVM-1-DFC_POWER_ON : A DFC is powered on due to board temperature cooling down. Slot: %d, Type: %s
Explanation The temperature in the system cools down.
Recommended Action For AS5400, when the board temperature cools down, a DFC is powered on, back to work. A customer should type 'show environment' to display temperature data and compare with temperature meter to verify the recovery.
Error Message%AS5400_ENVM-1-DFC_UNBUSYOUT : All DFCs are unbusy out due to board temperature cooling down.
Explanation The System experienced an over-temperature condition.
Recommended Action For AS5400, when the board temperature cools down, all DFCs are unbusy out, back to work. A customer should type 'show environment' to display temperature data and compare with temperature meter to verify the recovery.
Error Message%AS5400_ENVM-1-DROP_FAN_MONITOR : Environmental Monitor of Fans is dropped.
Explanation If a temperature sensor at inlet or outlet fails to work, the environmental monitoring of fans is dropped.
Recommended Action For AS5400, once the fan monitoring is dropped, only console message is sent out and alarm is activated. A customer should type 'show environment' to display temperature data and compare with temperature meter. If really fails, call Cisco to replace the temperature sensor
Error Message%AS5400_ENVM-1-DROP_TEMP_MONITOR : Environmental Monitor of Temperature is dropped.
Explanation If all temperature sensors fail to work, the environmental monitoring of temperature is dropped.
Recommended Action For AS5400, once the temperature monitoring is dropped, only console message is sent out and alarm is activated. A customer should type 'show environment' to display temperature data and compare with temperature meter. If really fails, call Cisco to replace the temperature sensor
Error Message%AS5400_ENVM-1-OIR_POWER_DOWN : Environmental monitor is trying to power down a DFC by simulating OIR removal. Slot: %d, Type: %s
Explanation The System experienced an over-temperature condition. For AS5400, a DFC is powered down to prevent the DFC from damaging and to cool down the temperature. The environmental monitor apply the scheme of OIR removal to power down the DFC.
Recommended Action Make sure that the room temperature is not too high and that air flow to the card is not blocked. Check air conditioning and the surrounding of the AS5400 box.
Error Message%AS5400_ENVM-1-OIR_POWER_ON : Environmental monitor is trying to power on a DFC by simulating OIR insertion. Slot: %d, Type: %s
Explanation The temperature cools down inside the chassis. For AS5400, when the board temperature cools down, a DFC is powered on, back to work. The environmental monitor apply the scheme of OIR insertion to power on the DFC.
Recommended Action No action is required.
Error Message%AS5400_ENVM-1-OK_FAN_MONITOR : Environmental Monitor of Fans is recovered.
Explanation If temperature sensors at both inlet or outlet recovers to work, the environmental monitoring of fans is recovered.
Recommended Action For AS5400, once the fan monitoring is recovered, console message is sent out and alarm is disabled. Fan state is set as normal. A customer should type 'show environment' to display temperature data and compare with temperature meter to verify the recovery.
Error Message%AS5400_ENVM-1-OK_TEMP_MONITOR : Environmental Monitor of Temperature is recovered.
Explanation If a temperature sensor recovers to work, the environmental monitoring of temperature is recovered.
Recommended Action For AS5400, once the temperature monitoring is recovered, console message is sent out and alarm is disabled. temperature state is set as normal. A customer should type 'show environment' to display temperature data and compare with temperature meter to verify the recovery.
Error Message%AS5400_ENVM-1-TEMP_SENSOR_FAIL : Temperature sensor #%d fails to work.
Explanation The health of each temperature sensor itself is also monitored. There are three cases that we consider a sensor fails to operate normally: 1. a sensor generates extraordinary data, such as higher than 200 degree C; 2. temperature change exceeds limits in one minute, such as 25 degree C; 3. temperature differential between sensors in the same box is greater than limit, such as 25 degrees C.
Recommended Action For AS5400, once the failure of a temperature sensor is detected, ENVMON will set the temperature state of that sensor as disabled, send out console message. The temperature data from that sensor is ignored in temperature monitoring. A customer should type 'show environment' to display temperature data and compare with temperature meter. If really fails, call Cisco to replace the temperature sensor
Error Message%AS5400_ENVM-1-TEMP_SENSOR_OK : Temperature sensor #%d recovers to work.
Explanation The health of each temperature sensor itself is also monitored. There are three cases that we consider these sensors fail to operate normally: 1. a sensor generates extraordinary data, such as higher than 200 degree C; 2. temperature change exceeds limits in one minute, such as 25 degree C; 3. temperature differential between sensors is greater than limit, such as 25 degrees C.
Recommended Action For AS5400, once the recovery of a temperature sensor is detected, ENVMON will set the senor_state of that sensor as normal, send out console message. The temperature data from that sensor is read again in temperature monitoring. A customer should type 'show environment' to display temperature data and compare with temperature meter to verify the recovery.
Error Message%AS5400_ENVM-1-TEMP_STATE : System detected that temperature is in %s condition.
Explanation The environmental monitor detected a temperature change, either failure or recovery.
Recommended Action Make sure that the room temperature is not too high and that air flow to the card is not blocked. If this condition persists, the environmental monitor might shut down the system. Check air conditioning and the surrounding of the AS5400 box. Call your technical support representative for assistance, if necessary.
Error Message%AS5400_ENVM-3-DISABLE_ENVM : AS5400 Environmental Monitor is disabled.
Explanation A configuration command can disable AS5400 environmental monitor when a user doesn't need it in certain special situations.
Recommended Action For AS5400, once the ENVMON is disabled, both console message and a SNMP trap are sent out. No further action.
Error Message%AS5400_ENVM-3-ENABLE_ENVM : AS5400 Environmental Monitor is enabled.
Explanation A configuration command can enable AS5400 environmental monitor after it was disabled in certain special situations.
Recommended Action For AS5400, once the ENVMON is enabled, both console message and a SNMP trap are sent out, and all ENVMON actions will be taken if necessary.
Error Message%AS5400_ENVM-3-FAN_FAIL : %s fail to work.
Explanation Some cooling fans fail to work. This is detected by the temperature delta between the inlet and outlet. A big delta indicates fan failure.
Recommended Action Replace the fan as soon as possible or the system may shut itself down or fail to operate properly.
Error Message%AS5400_ENVM-3-FAN_OK : %s recovered to work.
Explanation Some cooling fans recover to work. This is detected by the temperature delta between the inlet and outlet. A small delta indicates fan recovery.
Recommended Action Verify the fan work properly by checking the 4 fans and a customer should type 'show environment' to display temperature delta data and verify the recovery.
AS5X_FC Messages
Error Message%AS5X_FC-3-BUSYOUT : [chars] [dec] [chars]
Explanation Errors occurred during the busyout of the AS5X-FC high-density packet voice and fax feature card.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AS5X_FC-3-CARDCOOKIE : [chars]:[dec]
Explanation An invalid cookie was detected for the AS5X-FC high-density packet voice and fax feature card.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AS5X_FC-3-FPGA : [chars] for slot:[dec] written pktpump_bar:[hex] read pktpump_bar:[hex]
Explanation The FPGA Packet Pump Base Address Register was not programmed correctly.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AS5X_FC-3-FPGA_IMAGE_LOAD_FAILED : [chars] in slot [dec]
Explanation An AS5X-FC high-density packet voice and fax feature card FPGA image has failed to load.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AS5X_FC-3-IMC : [chars]:[dec]
Explanation An IMC controller was not detected.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AS5X_FC-3-MALLOC : Memory allocation failure for: [chars]
Explanation A memory allocation failure has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AS5X_FC-3-PVDMCOOKIE : Invalid PVDM cookie in Slot:[dec] PVDM :[dec]
Explanation An invalid packet voice/data module cookie has been detected.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AS5X_FC-3-RESET_CLEARED_FAILED : AS5X-FC [dec] Reset-Cleared Failed
Explanation An AS5X-FC high-density packet voice and fax feature card reset-cleared operation has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AS5X_FC-3-TIMER_RUNNING : AS5X-FC OIR remove for the Slot [dec] is still in progress, AS5X-FC insertion is aborted
Explanation The AS5X-FC high-density packet voice and fax feature card OIR timer is still running and the AS5X-FC OIR removal is in progress.
Recommended Action No action is required.
Error Message%AS5X_FC-3-UNSUPPORTEDPVDM : pvdm_type:[hex] pvdm_slot:[dec]
Explanation An unsupported PVDM type has been detected in the specified slot.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AS5X_FC-6-FPGA_IMAGE_DAMAGED : [chars] in slot [dec], loading image version [dec]
Explanation There is a damaged AS5X-FC high-density packet voice and fax feature card FPGA image.
Recommended Action This is an informational message only. No action is required.
Error Message%AS5X_FC-6-FPGA_IMAGE_LOADED : [chars] in slot [dec]
Explanation An AS5X-FC high-density packet voice and fax feature card FPGA image has been loaded.
Recommended Action This is an informational message only. No action is required.
Error Message%AS5X_FC-6-FPGA_IMAGE_UPGRADE : [chars] in slot [dec], from revision [dec] to revision [dec]
Explanation Upgrading the AS5X-FC high-density packet voice and fax feature card FPGA image.
Recommended Action No action is required.
Error Message%AS5X_FC-6-NODSP : [chars]:[dec]
Explanation No DSPs were found on the specified card.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ASPP-3-NOTTY : %s: 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.
Error Message%ASR900_PTP-3-MSGDISPATCH : Unable to dispatch received TDL message from PTP daemon
Explanation An unexpected condition has occurred while IOS was trying to dispatch a TDL message received from PTP daemon.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%ASR900_PTP-3-MSGINITFAIL : Failed to initalize required PTP resource: [chars]
Explanation During the initialization of the resources required by PTP, a failure occured. This has prevented PTP from being activated.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
IOSXE Messages
Error Message%ASR1000_APPLIANCE-3-ACTIVATE_FAIL: Failed to send appliance '[chars]' activate message
Explanation A failure occurred during the creation and transmission of the appliance activate message. The message was not successfully sent and therefore the appliance was not activated.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ASR1000_APPLIANCE-3-DEACTIVATE_FAIL : Failed to send appliance '[chars]' de-activate message
Explanation A failure occurred during the creation and transmission of the appliance deactivate message. The message was not successfully sent and therefore the appliance was not deactivated.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ASR1000_APPLIANCE-3-INIT_FAIL : Failed to initialize required appliance objects
Explanation A memory allocation failure occurred during the initialization of the resources required for the appliance feature, thus preventing the appliance feature from being enabled.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ASR1000_APPLIANCE-3-PKG_PATH_ACTIVATE_FAIL: Failed to find appliance definition file '[chars]'. Appliance '[chars]' will not be activated
Explanation The specified appliance definition file was not found after a switchover. This caused the failure to activate the appliance.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ASR1000_APPLIANCE-3-ROMMON_UNSUPPORTED: ROMMON configuration does not support virtualization
Explanation Virtualization is not supported by the current ROMMON configuration.
Recommended Action To enable virtualization, verify whether both the ROMMON version and ROMMON variable ENABLE_VTX are correct. If the error 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error MessageExplanation The specified appliance definition file is not found on the standby router. This appliance will not be activated after a switchover. Copy the appliance definition file to the standby router as soon as possible.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ASR1000_APPLIANCE-3-STBY_PKG_PATH_FAIL: Failed to find appliance definition file '[chars]' required by appliance '[chars]' on Standby
Explanation The specified appliance definition file is not found on the standby router. The configuration is accepted upon a switchover; however, if the definition file is not found, the configuration will be removed. Copy the appliance definition file to the standby as soon as possible.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%IOSXE_DSP-3-ENQUEFAIL : Enqueue of TDL message failed ([chars]).
Explanation The configuration, resource, or call details were not forwarded because an unexpected condition has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IOSXE_ETHERCHAN-3-LINK_MTU_FAIL : Failure in changing MTU of interface %s to port-channel %s 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
Error Message%IOSXE_ETHERCHAN-6-LINK_MTU : Interface %s MTU set to port-channel %s MTU %d
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.
Error Message%IOSXE_LICENSE_BOOT_CLI-3-CHASFS_OBJECT_FAILURE : Unable to create the chassis file system object [chars], for storage of the license boot level.
Explanation An attempt to create the specified chassis file system object used for the storage of the license boot level has failed. Executing the show license image-levels command may not display the latest values.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IOSXE_LICENSE_BOOT_CLI-3-CHASFS_PROPERTY_CREATE_FAILURE : Unable to create the chassis file system Property [chars], for storage of a property for the license boot level.
Explanation An attempt to create the specified chassis file system property used for the storage of a property for the license boot level has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error MessageExplanation An attempt to create the specified chassis file system property used for the storage of a property for the license boot level has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IOSXE_MEMPOOL_MIB-3-BUFFPOOL_REG_ERROR : Bufferpool register data exceeds allocated memory; Retrieved only %d entries.
Explanation Memory allocated is not enough
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_MGMTVRF-3-AFI_ATTACH_FAIL : Management VRF AFI %s attach failed
Explanation Can not create afi subblock for mgmt vrf
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_MGMTVRF-3-INTF_ATTACH_FAIL : Management VRF attach to mgmt port failed
Explanation Can not associate mgmt port to mgmt vrf
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_MGMTVRF-3-PROCESS_CREATE_FAIL : Management VRF process creation failed, %s
Explanation Can not create IOS process for mgmt port init
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_MGMTVRF-3-SET_TABLEID_FAIL : Installing %s Management interface tableid 0x%x failed
Explanation Fail to set mgmt port tableid into Linux kernel
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_MGMTVRF-3-VRF_CREATE_FAIL : Management VRF creation failed
Explanation Can not create mgmt vrf during system init
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_MGMTVRF-6-CREATE_SUCCESS_INFO : Management vrf %s created with ID %d, ipv4 table-id 0x%x, ipv6 table-id 0x%x
Explanation mgmt vrf and ipv4, ipv6 tables created for mgmt port
Recommended Action .
Error Message%IOSXE_OIR-3-MODULE : Missing %s for %s
Explanation A hardware or software error occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%IOSXE_OIR-3-OIRTWICE : Subslot %u/%u OIR insertion/removal not paired up: %s
Explanation An internal OIR-related error occured for the specified SPA.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_OIR-3-POWER_CYCLE_IMMINENT : The SPA in subslot %u/%u will be power cycled in %d 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.
Error Message%IOSXE_OIR-3-PROCMSG : Process msg send failed for process%d
Explanation Process message send failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_OIR-3-QUIESCE_FAIL : Quiesce failed for subslot %u/%u (error = %d)
Explanation The RP failed to contact the SPA during failover. The SPA will be reset.
Recommended Action No action is required.
Error Message%IOSXE_OIR-3-UNQUIESCE_FAIL : Unquiesce failed for subslot %u/%u (error = %d)
Explanation The RP failed to unquiesce the SPA in the specified subslot. The SPA will be reset.
Recommended Action No action is required.
Error Message%IOSXE_OIR-6-CARDRECONCILE : SPA type changed on subslot %u/%u from %u to %u
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.
Error Message%IOSXE_OIR-6-INSCARD : Card (%s) inserted in slot %s
Explanation The OIR facility detected the insertion of a card in the slot number specified in the message.
Recommended Action No action is required.
Error Message%IOSXE_OIR-6-INSSPA : SPA inserted in subslot %u/%u
Explanation The OIR facility detected the insertion of a SPA in the subslot number specified in the message.
Recommended Action No action is required.
Error Message%IOSXE_OIR-6-OFFLINECARD : Card (%s) offline in slot %s
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.
Error Message%IOSXE_OIR-6-ONLINECARD : Card (%s) online in slot %s
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.
Error Message%IOSXE_OIR-6-REMCARD : Card (%s) removed from slot %s
Explanation The OIR facility detected the removal of a card from the slot number specified in the message.
Recommended Action No action is required.
Error Message%IOSXE_OIR-6-REMSPA : SPA removed from subslot %u/%u, 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.
Error Message%IOSXE_OIR-6-SOFT_RELOADSPA : SPA(%s) reloaded on %s
Explanation The SPA in the specified subslot is reloaded by the command hw-module subslot slot#/subslot# reload
Recommended Action No action is required.
Error Message%IOSXE_OIR-6-SOFT_STARTSPA : SPA(%s) restarted in %s
Explanation The SPA in the specified subslot is restarted by the command hw-module subslot slot#/subslot# start
Recommended Action No action is required.
Error Message%IOSXE_OIR-6-SOFT_STOPSPA : SPA(%s) stopped in %s, interfaces disabled
Explanation The SPA in the specified subslot is stopped by the command hw-module subslot slot#/subslot# stopThe 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.
Error Message%IOSXE_OIR-6-SPARELOAD : SPA reloaded on subslot %u/%u
Explanation The SPA in the specified subslot is reloaded.
Recommended Action No action is required.
Error Message%ASR1000_PEM-3-FANFAIL : The fan in slot %d/%d 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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%ASR1000_PEM-3-PEMCHASFSERR : The PEM in slot %d has encountered a system software error.
Explanation The PEM's underlying software for storing PEM state is not working properly.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%ASR1000_PEM-3-PEMFAIL : The PEM in slot %d 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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error MessageExplanation The fan was reporting a failure condition. This message indicates that the fan is no longer reporting a failure
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%ASR1000_PEM-6-INSPEM_FM : PEM/FM slot P%u 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.
Error Message%ASR1000_PEM-6-PEMOK : The PEM in slot %d 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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%ASR1000_PEM-6-REMPEM_FM : PEM/FM slot P%u 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.
Error Message%IOSXE_PROCMIB -4-MSGERR : %s Error with process mib message from sub-slot %d/%d
Explanation When processing a process MIB message from the specified subslot, the specified error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_PROCMIB -4-SENDMSGERR : Failure in sending process mib information from subslot %d/%dto RP
Explanation A failure is encountered when sending process MIB statistics from the IOS driver for the subslot specified in the message to RP IOS. This indicates a software failure.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%ASR1000_RP_ALARM-6-INFO : %s %s %s %s %s
Explanation Alarm assertion or deassertion information.
Recommended Action No action is required.
Error Message%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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_RP_CFG_NOT-2-MSGNOEXP : Can not construct a '%s' message for configuration export: %s
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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_RP_CFG_NOT-2-MSGTDLERROR : Error processing TDL message. %d
Explanation An unexpected condition in which IOS has received a TDL message which it can not process.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_RP_CFG_NOT-2-MSGTDLINITERROR : Configuration Notification messaging module initialization failed: Unable to initialize messaging: %s
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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_RP_CFG_NOT-3-MSGIPCTXERROR : IPC transmit error. %d
Explanation An unexpected condition in which IOS encountered an error trying to send a message to another process. %d
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_RP_DIAG_TEST-3-MSGDIAGCANTENQUEUE : Online diagnostics could not enqueue a diagnostic test response.
Explanation The asr1000 online diagnostics failed to respond properly to a request by the system to perform a diagnostic test.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_RP_DIAG_TEST-3-MSGDIAGTIMEOUT : A timeout occured while waiting for an online diagnostic test to finish.
Explanation The asr1000 online diagnostics failed to respond properly to a request by the system to perform a diagnostic test.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_RP_DIAG_TEST-3-MSGIPCTXERROR : IPC transmit error. %d
Explanation An unexpected condition in which IOS encountered an error trying to send a message to another process. %d
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error MessageError Message %IOSXE_RP_DIAG_TEST-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 perform online diagnostics work.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_RP_DIAG_TEST-3-MSGRESPTDLERR : A diagnostic test result could not be read properly.
Explanation The asr1000 online diagnostics failed to respond properly to a request by the system to perform a diagnostic test.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_RP_DIAG_TEST-3-MSGTDLERROR : Error processing TDL message. %d
Explanation An unexpected condition in which IOS has received a TDL message which it can not process.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_RP_DIAG_TEST-6-MSGOUTOFORDER : Received a test result after IOS had timed out. [%d,%d]
Explanation When a diagnostic test is performed, IOS waits for the result be returned. If it does not return in a specified period of IOS times out on that test request and moves on.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_RP_DIAG_TEST-6-MSGUNEXPECTEDEVENT : Unexpected event recieved.
Explanation When a diagnostic test is performed, IOS waits for the result be returned. While waiting for the result, IOS unexpectedly received an event it does not recognize and so IOS stopped waiting for the result. The test continued, IOS does not know what the results are and hence can not report them.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_RP_DPIDB-3-BULK_SYNC : Failed to send %s 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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_RP_DPIDB-3-CF : Datapath IDB CF operation failed - %s
Explanation Failure in some datapath ID CF activity.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show interface command and your pertinent troubleshooting logs.Error Message%IOSXE_RP_DPIDB-3-DECODE : Decode via %s of %s 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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_RP_DPIDB-3-DYN_SYNC : Failed to process %s 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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show interface command and your pertinent troubleshooting logs.Error Message%IOSXE_RP_DPIDB-3-IDBBADTYPE : Datapath IDB type %d is not valid
Explanation An unexpected condition has occurred as the type of a datapath IDB is not valid.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show interfaces command and your pertinent troubleshooting logs.Error Message%IOSXE_RP_DPIDB-3-IDBEXIST : Datapath IDB already exists in this mapping entry: %s-%d
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 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the commands and your pertinent troubleshooting logs. (show interface)
Error Message%IOSXE_RP_DPIDB-3-IDBNONEXIST : Datapath IDB does not exist in this mapping entry: %s-%d
Explanation Datapath IDB lookup points to empty mapping entry.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the commands and your pertinent troubleshooting logs. (show interface)
Error Message%IOSXE_RP_DPIDB-3-IDBNOTVAI : Invalid API call for %s
Explanation Failure in an internal API
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the commands and your pertinent troubleshooting logs. (show interface)
Error Message%IOSXE_RP_DPIDB-3-IDXALLOCFAILED : Datapath IDB index allocation failed: %s
Explanation An unexpected condition has occurred as all the available of datapath IDB indices are used.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the commands and your pertinent troubleshooting logs. (show interface)
Error Message%IOSXE_RP_DPIDB-3-IDXBADRANGE : Datapath IDB index %d 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 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the commands and your pertinent troubleshooting logs. (show interface)
Error Message%IOSXE_RP_DPIDB-3-IDXDELETIONFAILED : Deletion of datapath IDB index from the database failed
Explanation An unexpected condition has occurred that deletion of datapath IDB indices failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the commands and your pertinent troubleshooting logs. (show interface)
Error Message%IOSXE_RP_DPIDB-3-IDXINSERTFAILED : Insertion of datapath IDB index %d into database failed
Explanation An unexpected condition has occurred that insertion of datapath IDB indices failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the commands and your pertinent troubleshooting logs. (show interface)
Error Message%IOSXE_RP_DPIDB-3-IDXLOOKUPFAILED : Lookup of datapath IDB index from the database failed (%s)
Explanation An unexpected condition has occurred that lookup of datapath IDB indices failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the commands and your pertinent troubleshooting logs. (show interface)
Error Message%IOSXE_RP_DPIDB-3-ISSU : %s %s failed; %s
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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_RP_DPIDB-3-LIST : List %s failed for %s
Explanation List enqueue or removal failed
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the commands and your pertinent troubleshooting logs. (show interface)
Error Message%IOSXE_RP_DPIDB-3-NEGOTIATION : Failed to start ISSU %s session negotiation; %s
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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_RP_DPIDB-3-NOHWSUBBLOCK : HWIDB %s does not have a ASR1000 subblock
Explanation An unexpected condition has occurred that no ASR1000 subblock was previously allocated for a HWIDB.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the commands and your pertinent troubleshooting logs. (show interface)
Error Message%IOSXE_RP_DPIDB-3-NOSWSUBBLOCK : SWIDB %s does not have a ASR1000 subblock
Explanation An unexpected condition has occurred that no ASR1000 subblock was previously allocated for a SWIDB.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the commands and your pertinent troubleshooting logs. (show interface)
Error Message%IOSXE_RP_DPIDB-3-NULLTIMER : NULL timer
Explanation A timer is NULL
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the commands and your pertinent troubleshooting logs. (show interface)
Error Message%IOSXE_RP_DPIDB-3-PROGRESSION : Unable to inform RF of bulk sync completion; %s
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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_RP_DPIDB-3-RECEIVE : Message via %s is %s
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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_RP_DPIDB-3-REGISTRATION : ISSU %s failed for %s; %s
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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_RP_DPIDB-3-RF : Datapath IDB RF operation failed - %s
Explanation Failure in some datapath ID RF activity.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the commands and your pertinent troubleshooting logs. (show interface)
Error Message%IOSXE_RP_DPIDB-3-RPC : Datapath IDB RPC operation failed - %s
Explanation Failure in some datapath ID RPC activity.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the commands and your pertinent troubleshooting logs. (show interface)
Error Message%IOSXE_RP_DPIDB-3-TRANSFORM : %s of %s via %s failed for dpidx %u
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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_RP_DPIDB-3-TRANSMIT : Unable to send via %s %s %s %s; %s
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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_RP_DPIDB-6-READY : %s peer not ready, discarding %s
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 .
Error Message%IOSXE_RP_DPIDB-6-RELOAD : %s, reloading %s
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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_RP_DPIDB-6-TIMEOUT : Bulk sync is flow controlled by %s
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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_RP_IF_FLOW_IDS-3-BUFF_OFFSET_NULL : Unable to utilize the memory buffer provided by the Checkpoint Facility. This %s 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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_RP_IF_FLOW_IDS-3-CF_CANNOT_REGISTER : The call to add this %s CF client to the Checkpoint Facility failed with the error %s. 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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_RP_IF_FLOW_IDS-3-CF_SEND_BULK_NONBLOCKED : The Checkpoint Facility reported the error %s while attempting tosend a message. Bulk Sync of this %s 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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_RP_IF_FLOW_IDS-3-CF_SEND_INCR_NONBLOCKED : The Checkpoint Facility reported the error %s while attempting tosend a non-blocked message. The Incremental Sync transaction for this %s 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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_RP_IF_FLOW_IDS-3-DEFERRED_DURING_BULK_SYNC : Encountered error %s while trying to place an %s transaction on the Deferred list during Bulk Sync for the %s 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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_RP_IF_FLOW_IDS-3-NO_BUFF_FOR_SYNC : The Checkpoint Faclity reported the error %s during a request for a buffer length of %d. This %s 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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_RP_IF_FLOW_IDS-3-RF_ADD_CLIENT_FAILED : The RF facility failed to add this %s client, reason given is %s.
Explanation This indicates the RF facility could not add the client.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, 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 %d encountered trying to regenerate interface flow-control identifer. If id %u resides in slot/subslot/port (%u/%u/%u).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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_RP_IF_FLOW_IDS-3-RF_PEER_EVENT_BUFFER : This %s RF client is unable to acquire an event buffer to send an RF peer message, the error %s 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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_RP_IF_FLOW_IDS-3-RF_POOL_REGEN_ERROR : Id Pool Regeneration encountered error code %d, 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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_RP_IF_FLOW_IDS-3-RF_POOL_REGEN_PROCESS_FAILED : The %s 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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_RP_IF_FLOW_IDS-3-RF_PROCESS_FAILED : This %s 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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_RP_IF_FLOW_IDS-3-RF_SEND_PEER : This %s RF client encountered error %s, 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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_RP_IF_FLOW_IDS-3-RF_SPA_ID_REGEN_ERROR : Error code %d encountered trying to regenerate spa %s identifier in slot/subslot (%u/%u)
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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_RP_IF_FLOW_IDS-3-SEND_FAIL_RELOAD : Checkpoint Facility Failed to send a %s transaction for this %s 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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_RP_IF_FLOW_IDS-4-DEF_LIST_REMOVE : Failed to remove one entry from the Deferred Sync list, for the %s CF client.
Explanation An unexpected condition occured during list maintenance.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_RP_IF_FLOW_IDS-6-CFPEER_CANNOT_RECV : The Checkpoint Peer is not ready to receive messages. The Incremental Sync transaction for this %s CF client will not occur.
Explanation This error indicates the Checkpoint Facility has signalled the peer has gone away.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_RP_MGMTE-3-MSGCREATENULL : Cannot allocate %s TDL message
Explanation An unexpected condition in which IOS cannot allocate TDL message for Management ethernet.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_RP_MGMTE-3-MSGTDLINITERROR : Management ethernet interface messaging module initialization failed: Unable to initialize messaging: %s
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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_RP_ONLINE_DIAG-3-MSGMAXCARDS : Online diagnostics maximum number of cards exceeded
Explanation An unexpected condition in which IOS has attempted to register more hardware cards for diagnostics than it expects the maximum to be.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error MessageExplanation An unexpected condition has occurred while IOS is trying to perform online diagnostics work.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_RP_ONLINE_DIAG-3-MSGTDLERROR : Error processing TDL message. %d
Explanation An unexpected condition in which IOS has received a TDL message which it can not process.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error MessageIOSXE_RP_SPA-3-IOSXE_RP_SPA : Bad ifcom message type=%u
Explanation A SPA module passed down a message that the RP software was not prepared to handle.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error MessageIOSXE_RP_SPA-3-CI_UPDATE_FAIL : Failed to update connection identifier for interface %s
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.
Error MessageIOSXE_RP_SPA-3-DPIDX_LKUP_FAIL : Failed to retrieve datapath identifier for interface %s
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.
Error MessageIOSXE_RP_SPA-3-ERROR: NULL
Explanation This message can take many forms. It provides information about a software error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error MessageIOSXE_RP_SPA-3-FLOWID_ALLOC_FAIL : Failed to allocate a flow control identifier for interface %s
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.
Error MessageIOSXE_RP_SPA-3-FLOWID_RELEASE_FAIL : Failed to release a flow control identifier for interface %s (status = %d)
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.
Error MessageIOSXE_RP_SPA-3-FOREVER : cmd %u to %s (slot %u/%u) took %u usecs, done %x
Explanation A CCB command from the RP to a SPA module took longer than expected.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error MessageIOSXE_RP_SPA-3-HWIDB_FAILURE: Creation: slot %d subSlot %d port %d vc %d
Explanation Failed to create an interface hwidb.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error MessageIOSXE_RP_SPA-3-HWIDB_INIT_FAIL : Failed to initialize data structure for SPA port %d/%d/%d
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.
Error MessageIOSXE_RP_SPA-3-IFCFG_CMD_NOT_OWNER : Process '%s' waiting for interface configuration command (0x%x) to slot %u/%u without acquiring lock owned by process '%s'
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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error MessageIOSXE_RP_SPA-3-IFCFG_FOREVER : to %s (slot %u/%u) took %u usecs, ret_val %lu
Explanation A interface config command from the RP to a SPA module took longer than expected.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error MessageIOSXE_RP_SPA-3-IFCFG_NO_UNIQUE_KEY : No unique-key generator registered for interface configuration command %u.
Explanation The High Availability component for SPA modules is unable to properly synchronize state information for the current configuration.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error MessageIOSXE_RP_SPA-3-INVALID_PORT_NUM : slot=%d port=%d, hwidbType=0x%x, max_port_num=%d, LCtype=0x%x
Explanation The port number is out of range.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error MessageIOSXE_RP_SPA-3-IPCALLOCFAIL : Failed to allocate IPC buffer %s
Explanation The RP failed to allocate a buffer for communication with a SPA
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error MessageIOSXE_RP_SPA-3-IPCPORT : Failed to %s IPC port '%s', error %s
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.
Error MessageIOSXE_RP_SPA-3-IPCPORTFAIL : Failed to open IPC port '%s' with error %s
Explanation The RP failed to open a port for communication with a SPA module.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error MessageIOSXE_RP_SPA-3-IPCSENDFAIL : Failed to send IPC message %s
Explanation The RP failed to send a message to a SPA module.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error MessageIOSXE_RP_SPA-3-MAX_SPA : Power to IPSEC-SPA-2G in %s is denied because it has exceeded the number allowed(%d)
Explanation The number of IPSEC-SPA-2G in a chassis is limited.This message is displayed when the number of IPSEC-SPA-2G inthe chassis has exceeded this limit.
Recommended Action Use only the number of supported IPSEC-SPA-2G
Error MessageIOSXE_RP_SPA-3-NO_HOST_INFO : slot %d subSlot %d, spaType 0x%x
Explanation Failed to get information about the host linecard.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error MessageIOSXE_RP_SPA-3-NULL_DATA_STRUCTURE : NULL
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.
Error MessageIOSXE_RP_SPA-3-SPA_NO_HOST_INFO : slot %d subSlot %d, PID %s
Explanation Failed to get information about the host linecard.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error MessageIOSXE_RP_SPA-3-VC_PROV_FAIL : Failed to provision interface %s
Explanation The SPA driver is not able to provision the interfacespecified 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.
Error MessageIOSXE_RP_SPA-4-CCB_PLAYBACK_ERROR : CCB playback failed for slot %d.
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, Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error MessageIOSXE_RP_SPA-4-CCB_RECORD_ERROR : CCB record failed for slot %d.
Explanation The High Availability component for SPA modules failed to record some new state information for the specified slot.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error MessageIOSXE_RP_SPA-4-IFCFG_CMD_TIMEOUT : Interface configuration command (0x%x) to slot %u/%u 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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error MessageIOSXE_RP_SPA-4-IFCFG_DFLT_LIST_ERROR : For Interface Configuration command %u, default retval list search resulted 0x%x for slot %u/%u
Explanation The High Availability component for SPA modules failed to synchronize some new state information for the specified slot.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the commands and your pertinent troubleshooting logs. (show platform redundancy if-config default-retvals)
Error MessageIOSXE_RP_SPA-4-IFCFG_PLAYBACK_ERROR : Interface Configuration command %u playback failed for slot %u/%u.
Explanation The High Availability component for SPA modules failed to synchronize some new state information for the specified slot.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error MessageIOSXE_RP_SPA-4-IFCFG_RECORD_ERROR : Interface Configuration command %u record failed for slot %u/%u.
Explanation The High Availability component for SPA modules failed to record some new state information for the specified slot.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error MessageIOSXE_RP_SPA-4-INCR_CFG_SYNC_FAIL : ASR1000 incremental running-config sync for [%d/%d] failed - %s(%d), Reload Standby
Explanation The specified ASR1000 incremental running-config sync failed
Recommended Action Power cycle the redundant supervisor
Error MessageIOSXE_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.
Error MessageIOSXE_RP_SPA-4-LCLOG_TOOLONG : Message too long from slot %u/%u: %u bytes
Explanation The SPA module passed down a logger message that is too long for the RP to handle.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error MessageIOSXE_RP_SPA-4-LCLOG_TOOLONG :
Explanation The SPA module passed down a logger message that could not be parsed.
Explanation Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error MessageIOSXE_RP_SPA-4-SEMAHOG : Process %d (%s) hogging %s! calling proc %d (%s)
Explanation The RP waited too long for a reply to a command sent to a SPA module.
Recommended Action No action is required.
Error MessageIOSXE_RP_SPA-4-SPA_CMD_NO_RESP : %s: No response for interface configuration command %u
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.
Error MessageIOSXE_RP_SPA-4-SPA_RESP_CMD_MISMATCH : %s: Expecting response to interface configuration command %u but received response to command %u.
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 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error MessageIOSXE_RP_SPA-6-CARDRELOAD : Module %u reload due to SPA insert in %u/%u.
Explanation When inserting a SPA on this carrier card, the cardis reset.
Recommended Action No action is required.
Error Message%IOSXE_RP_VTYMGT-3-MSGBIPCBUFFER : Unable to acquire a BIPC buffer of length %d 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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_RP_VTYMGT-3-MSGBIPCERR : Unable to process received BIPC messages for Vty Management, error: %s
Explanation An unexpected condition has occurred while IOS was trying to process a received BIPC message for Vty Management.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_RP_VTYMGT-3-MSGBUILDERROR : Error '%d' building TDL Vty Management message '%s': %s
Explanation An unexpected condition has occurred while IOS is building a TDL response message for Vty Management
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_RP_VTYMGT-3-MSGENQUEUEERROR : Error queueing TDL Vty Management message '%s'
Explanation An unexpected condition has occurred when IOS attempted to queue a TDL response message for Vty Management
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_RP_VTYMGT-3-MSGERROR : Error '%d' handling a received TDL message '%s' for Vty Management: %s
Explanation An unexpected condition has occurred while IOS is processing a received Vty Management TDL message
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_RP_VTYMGT-3-MSGEXTAPPUPDATE : Unable to update external application data for line '%d'
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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_RP_VTYMGT-3-MSGINVALIDFIELDINT : Invalid field '%s' in TDL message '%s' received: value '%u' for Vty Management
Explanation A message with an invalid field value was received for Vty Management
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_RP_VTYMGT-3-MSGINVALIDFIELDSTR : Invalid field '%s' value '%s' in TDL message '%s' received for Vty Management
Explanation A message with an invalid field value was received for Vty Management
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_RP_VTYMGT-3-MSGMARSHALERROR : Error '%d' marshaling TDL Vty Management message '%s': %s
Explanation An unexpected condition has occurred while IOS is marshaling TDL response message for Vty Management
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_RP_VTYMGT-3-MSGMISSINGFIELD : Missing field '%s' in TDL Vty Management message '%s' received
Explanation A message missing a required field was received for Vty Management
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_RP_VTYMGT-3-MSGVTYCOUNT : Invalid vty count %d 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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%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 Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_SCHED-3-AVL_INSERT_FAIL : Could not insert pid %d into process tree
Explanation An avl_insert() failed to add a process structure to the ASR1000 scheduler tree. This should never occur, as the tree is always searched first for the presence of the process.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_SCHED-3-CALLED_FROM_INT : API call incorrectly made from interrupt level
Explanation An external routine provided by the ASR1000 scheduler was incorrectly called from the context of an interrupt handler. This is not a supported use of the external routine; the calling code must be fixed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_SCHED-3-NEGATIVE_DEPTH : Queue '%s' consumed more than it produced (%d)
Explanation Based upon internal state derived from calls to mcp_queue_produced() and mcp_queue_consumed(), more data was consumed from a balanced queue than was produced into it. This is logically impossible, so the presence of this error generally indicates incorrect use of the two above mentioned routines.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_SCHED-3-NULLQ : Invalid API parameter
Explanation An external routine provided by the ASR1000 scheduler was incorrectly called with an invalid (NULL) pointer.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_SERVICE_ENGINE-3-MSGINITFAIL: Initialization of interface [chars] failed
Explanation The initialization of the interface specified in the error message failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%IOSXE_SERVICE_ENGINE-3-MSGOPENFAIL: Cannot open interface [chars] ([dec])
Explanation The driver cannot be opened because the system parameters in the driver were not programmed during the creation of a Service-Engine interface.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%IOSXE_SERVICE_ENGINE-3-MSGSETFAIL: Set id on interface [chars] ([dec])
Explanation Program the system parameters in the driver, during the creation of a Service-Engine interface.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%IOSXE_SIP_SPA-3-IOSXEIPCALLOCFAIL : Failed to allocate Common IPC buffer %s
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.
Error Message%IOSXE_SIP_SPA-3-BADMALUCMD : Unsupported MALU command %d, arg=%#x, pascb=%#x
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.
Error Message%IOSXE_SIP_SPA-3-BADMALUCMD2 : Unsupported MALU cmd/arg0=0x%04x%04x, arg1arg2=0x%04x%04x, hwidb=%s
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.
Error Message%IOSXE_SIP_SPA-3-BAD_IFCOMTYPE : Bad ifcom message type=%u
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.
Error Message%IOSXE_SIP_SPA-3-C2W_MAIN_INIT_FAIL : Failed to initialize SPA main c2w bus for subslot %d (status = %d)
Explanation The SPA driver is not able to initialize SPA main c2w. This indicates a hardware error.
Recommended Action No action is required.
Error Message%IOSXE_SIP_SPA-3-CMDNOINT : HWIDB Null for command %d, port %#x
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.
Error Message%IOSXE_SIP_SPA-3-DEVICE_ERROR : subSlot %d, spatype 0x%x. Device error: %s
Explanation An error related to a device on the SPA is detected.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%IOSXE_SIP_SPA-3-EFC_CHAN_ERR : EFC error - interface %s, vc %d, anyphy %d, err_code %d : %s
Explanation Failed to configure efc channel/parameters
Recommended Action Seach for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_SIP_SPA-3-EFC_FC_MAP_FAIL : Failed to update EFC flow control identifier for interface %s (status = %d)
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.
Error Message%IOSXE_SIP_SPA-3-EFC_PROV_FAIL : Failed to provision EFC for interface %s (status = %d)
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.
Error Message%IOSXE_SIP_SPA-3-EFC_UNPROV_FAIL : Failed to unprovision EFC for VC %s (status = %d)
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.
Error Message%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 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IOSXE_SIP_SPA-3-FCI_NOT_SET : Bay %d - FCI type not set
Explanation An FCI type of zero was detected
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%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 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IOSXE_SIP_SPA-3-HWIDB_FAILURE : Creation: port %d vc %d
Explanation Failed to create a hwidb.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%IOSXE_SIP_SPA-3-INVALID_ANYPHY : Bay %d - Invalid anyphy number %u for vc %d
Explanation Interface has invalid anyphy mumber
Recommended Action Seach for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl or contact your Cisco technical support representative. 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).
Error Message%IOSXE_SIP_SPA-3-INVALID_IF : Attempted to access HWIDB for port %u on slot %d subSlot %d
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.
Error Message%IOSXE_SIP_SPA-3-IPCALLOCFAIL : Failed to allocate IPC buffer %s
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.
Error Message%IOSXE_SIP_SPA-3-IPCPORT : Failed to %s IPC port '%s', error %s
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.
Error Message%IOSXE_SIP_SPA-3-IPCPORTFAIL : Failed to open IPC port '%s' %s with error %s
Explanation The RP failed to open a port for communication with a SPA module.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_SIP_SPA-3-IPCSENDFAIL : Failed to send IPC message %s
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.
Error Message%IOSXE_SIP_SPA-3-ISR_RC_ERROR : ISR return code out of range. rc=%d
Explanation The ISR error return code is out of range.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%IOSXE_SIP_SPA-3-LINKREC_ERROR : Link record error - Bay %d vc %d, error code %d
Explanation Error processing link record structure
Recommended Action Seach for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl or contact your Cisco technical support representative. 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).
Error Message%IOSXE_SIP_SPA-3-LVLTRTOOBIG : Loveletter length exceeds max, %u 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.
Error Message%IOSXE_SIP_SPA-3-MESSAGE_ERROR : Bay %d: %s
Explanation An unexpected error has occurred.
Recommended Action Seach for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%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 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IOSXE_SIP_SPA-3-NETCLK_FAIL : Failed to %s SPA reference clock on %s
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.
Error Message%IOSXE_SIP_SPA-3-NODISPATCH : Dispatch vector Null, cmd=%d, dintf=%d
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.
Error Message%IOSXE_SIP_SPA-3-POWER : Bay %d 12V power is %s
Explanation SPA 12V power fault indicator.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_SIP_SPA-3-SONET_CLOCK_FAILED : SPA Sonet clock has failed (status = 0x%08x)
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. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_SIP_SPA-3-SONET_CLOCK_RECOVERED : SPA Sonet clock has recovered (status = 0x%08x)
Explanation SPA Sonet clock has recovered.
Recommended Action No action is required.
Error Message%IOSXE_SIP_SPA-3-SPA_CTRL_EFC_CONFIG_FAILURE : Subslot, spa controller EFC configuration failure, error %d
Explanation Failed to configure SPA controller EFC.
Recommended Action Seach for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_SIP_SPA-3-SPA_CTRL_INIT_FAILURE : Subslot %d, spa controller initialisation failure, error %d
Explanation Failed to initialise SPA controller.
Recommended Action Seach for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_SIP_SPA-3-SPI4_CONFIG_FAILURE : Bay %d, spi4 configuration failure, error %d
Explanation Failed to configure SPI4 interface.
Recommended Action Seach for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%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 subslotTraffic 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 interfacesconfigured in the system either by physically removing the SPAsor by changing the system configuration
Error MessageError Message%IOSXE_SIP_SPA-3-SPI4_INIT_FAILURE : Bay %d initialization failure
Explanation Failed to create SPI4 subblock
Recommended Action Seach for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_SIP_SPA-3-SPI4_NOTSYNC : %s: Can not synchronize SPI4 bus (host: src %sin sync, sink %sin sync, spa: src %sin sync, sink %sin 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.
Error Message%IOSXE_SIP_SPA-4-MAX_BANDWIDTH : Total SPA bandwidth exceeds line card capacity of %lu Mbps
Explanation The total bandwidth of SPAs exceeds the rated capacityof this line card.
Recommended Action Refer to the line card guidelines for the maximum allowedaggregated SPA bandwidth for the line card
Error Message%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 capacityof this line card.
Recommended Action Refer to the line card guidelines for the maximum allowed aggregated SPA bandwidth for the line card
Error Message%IOSXE_SIP_SPA-4-SPABUS : Subslot %d, %s SPA BUS access failed. timeout=%u err=%u par=%u err_c=0x%x addr=0x%08x data =0x%x
Explanation SPABUS has reported an error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error MessageExplanation SPA OIR Sequence
Recommended Action No action is required.
Error Message%IOSXE_SIP_SPA-4-SPABUS2 : Subslot %d SPA BUS access failed. No SPA present error
Explanation SPABUS has reported an error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IOSXE_SPA-3-CREATE_TDLH_FAILURE : Failed to create SPA %d/%d handle
Explanation Failed to create message handle for SPA communication.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%IOSXE_SPA-3-CREATE_TDLMSG_FAILURE : Failed to create %s message for %s.
Explanation Failed to create/allocate necessary TDL message for SPA communication.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%IOSXE_SPA-3-CREATION_FAILURE : slot=%d subslot=%d, spa_type=0x%x, lc_type=0x%x.
Explanation Failed to create a SPA object.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%IOSXE_SPA-3-DIAG_CONFIG : %s did not complete %d/%d
Explanation An error has occured during diagnostic test.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%IOSXE_SPA-3-DISPATCH_INIT_TDLH_FAILURE : Failed to initialize dispatch path for SPA %d/%d handle
Explanation Failed to initialize dispatch path handle for SPA communication.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs. %IOSXE_SPA-3-DOMAIN_TDLH_FAILURE: %s, rc = %d
Explanation Failed to bind message handle for SPA communication.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%IOSXE_SPA-3-INVALID_CPU_NUM : cpu= %d, max cpu = %d
Explanation An invalid CPU number is specified in one of the internal APIs.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%IOSXE_SPA-3-INVALID_DATA_INSTANCE : interface type %s, slot %d port %d vc %d : %s
Explanation Data required to support the interface is not available.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%IOSXE_SPA-3-INVALID_IF_INDEX : index= %d, spaType=0x%x, slot %d subSlot %d slotunit %d vc %d
Explanation Index for the interface is not valid.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%IOSXE_SPA-3-INVALID_INDX_RANGE : index1= %d, index2= %d, maxIndex= %d
Explanation An invalid index range is specified in one of the internal APIs.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%IOSXE_SPA-3-INVALID_RP_SLOT_NUM : slot= %d, max slot = %d
Explanation An invalid RP slot number is specified in one of the internal APIs.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%IOSXE_SPA-3-INVALID_SLOTUNIT_NUM : cardwide-port = %d, max cardwide-port = %d
Explanation An invalid cardwide-port number is specified in one of the internal APIs.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%IOSXE_SPA-3-INVALID_SLOT_NUM : slot= %d, max slot = %d
Explanation An invalid slot number is specified in one of the internal APIs.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%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 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%IOSXE_SPA-3-INVALID_SUBSLOT_NUM : subslot= %d, max subslot = %d
Explanation An invalid subslot number is specified in one of the internal APIs.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%IOSXE_SPA-3-IPC_FAILURE : IPC failure while %s
Explanation An error has occurred while prepareing or sending an IPC message.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%IOSXE_SPA-3-MEM_ALLOC_ERROR : %s
Explanation Memory allocation error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%IOSXE_SPA-3-NULL_SPA_PTR :
Explanation Pointer to a SPA object is NULL.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%IOSXE_SPA-3-NULL_VFT : %s virtual function table is not initialized. spaType=0x%x
Explanation A required function table is not initialized
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%IOSXE_SPA-3-NULL_VFUNC : %s vector is not initialized. spaType=0x%x
Explanation A required function vector is not initialized
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%IOSXE_SPA-3-POWER_CYCLE : %s occurred on Shared Port Adapter %u/%u
Explanation An error has occurred which will cause the Shared Port Adapter to be power cycled
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%IOSXE_SPA-3-SENDCFGFAIL : Failed to send configuration for %s to carrier-card for subslot=%d/%d
Explanation Sending configuration failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%IOSXE_SPA-3-SETUP_TDLH_FAILURE : Failed to set the alloc/free handler for SPA %d/%d handle
Explanation Failed to set the alloc/free handler for SPA communication.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%IOSXE_SPA-3-SPA_CREATION_FAILURE : slot=%d subslot=%d, PID=%s lc_type=0x%x.
Explanation Failed to create a SPA object.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%IOSXE_SPA-3-UNSUPPORTED_DATA : Data conversion error (%s, 0x%X)
Explanation An internal software error has occured when converting the data specified in the message from one representation to another.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%IOSXE_VMAN-3-MSGINITFAIL: Failed to initialize required vman resources
Explanation A failure occurred during the initialization of the resources required for virtualization management (VMAN). This failure is preventing appliances from being activated.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%IOSXE_WD-2-HEARTBEAT_FAIL : Heartbeat is not emitted. Heartbeat count:%d
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
Error Message%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.
AS_PLATFORM Messages
The following are AS Platform messages.
Error Message%AS_PLATFORM-1-DFC_ERR : DFC [dec]: Detected PCI [chars] Error, CSR=[hex]
Explanation PCI error is detected on the DFC. This is due to hardware failure. IOS will power down this DFC and clean up the system data structures associated with it.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%AS_PLATFORM-1-OLD_FIRMWARE : [chars]
Explanation The specified component should have the latest hardware revision. If the hardware revision is not the latest, then it needs to be updated to the printed out version.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%AS_PLATFORM-1-UNINSTALLED_MASKED_INT : Uninstalled or masked interrupt: interrupt status [hex] mask [hex] vector [hex]
Explanation System detected an uninstalled or masked interrupt.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%AS_PLATFORM-1-UNKNOWN_DFC_INT : Unknown DFC interrupt: DFC slot no [dec], interrupt [dec]
Explanation Unknown DFC interrupt is detected.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the