Feedback
Table Of Contents
System Messages
This section lists messages alphabetically by facility and mnemonic.
AAA Messages
This section contains authentication, authorization, and accounting messages.
AAA-2
Error Message %AAA-2-FORKFAIL: Cannot fork process %sExplanation Attempted to fork a process and 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 nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %AAA-2-FORKFAIL: Cannot fork process %sExplanation 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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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-2-UNAVAILABLE: %s(%08X): Acct db for Id %08X absentExplanation AAA internal 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 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.
AAA-3
Error Message %AAA-3-ACCT_IOMEM_LOW: AAA ACCT process suspended : low I/O memoryExplanation 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. 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-ATTRFORMATERR: Attribute with unknown format %dExplanation An attribute was found with an invalid format
Recommended Action Attribute with unknown format in definition, call your technical support representative
Error Message %AAA-3-ATTRFORMATERR: Attribute with unknown format %dExplanation An attribute was found with an invalid format.
Recommended Action Attribute with unknown format in definition. Enable AAA debug and try to replicate the steps to get the message. If the meassage appears again, Check bug toolkit on Cisco website for the issue. If you didn't find one, Enter Show tech-support command, Collect all the information and error message and report it to your technical support representative.
Error Message %AAA-3-BADCURSOR: invalid cursor index %d max %d service %s protocol %sExplanation An 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 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-BADLIST: invalid list AAA ID %uExplanation An 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 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-BADMAGIC: Data structure failed magic number sanity checkExplanation 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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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-BADMAGIC: Data structure failed magic number sanity checkExplanation 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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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-BADMETHOD: Cannot process %s method %uExplanation 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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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-BADMETHODERROR: Cannot process %s method %sExplanation 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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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-BUFFER_OVERFLOW: Radius I/O buffer has overflowedExplanation An unusually large number of RADIUS attributes has caused AAA to overflow its RADIUS I/O buffer.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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-DROPACCTFAIL: Accounting record dropped, send to server failed: %sExplanation 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 %AAA-3-DROPACCTFAIL: Accounting record dropped, send to server failed: %sExplanation An attempt to send an accounting record to a server failed. This happens when device exhaust all its retries and retransmission. The cause for this be the servers may not be operational or the NAS is not configured properly.
Recommended Action Check the server , whether they are operational or not. Next check whether the device is configured properly. Refer tothe server configuration section of the cisco IOS documentation. Finally, check that the NAS can communicate with the server. If the problem persist, Enter show running-config command, contact your cisco technical support representative and provide all the information gathered to the representative.
Error Message %AAA-3-INVALIDPARM: invalid parameter was used when accessing AAA functionExplanation 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 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-IPILLEGALMSG: Invalid use of ip_pid(%u)Explanation This error means a process sent an illegal 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 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-IPILLEGALMSG: Invalid use of ip_pid(%u)Explanation This message means a process sent an illegal message to IP which IP has not subscribed for
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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-ISDNINTF: %s %s: Can not apply configuration to ISDN channel: %sExplanation Configuration can not be applied to individual ISDN channels.
Recommended Action You need virtual-profiles and virtual-access interfaces to apply configuration to ISDN. Refer to the section on Configuring virtual profile by AAA Configuration in the Cisco IOS Dial Technologies Configuration Guide.
Error Message %AAA-3-MLIST_TOO_MANY_METHODS: method list '%s'Explanation This is an internal software error. An AAA client attempted to add too many methods to a method list.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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-NULLCURSOR: Null cursorExplanation An AAA client has provided a non-existant 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 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-NULLVRF: Null vrf entryExplanation 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 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-PARSEERR: Error(%d) parser is unable to parse %s per-user commandExplanation All attempts to parse this per_user unconfigure command failed.
Recommended Action The given unconfigure command was not unconfigured. Report it to your technical support representative.
Error Message %AAA-3-PARSEERR: Error(%d) parser is unable to parse %s per-user commandExplanation All attempts to parse this per_user unconfigure command failed. The unconfigure command is called when an error occurs while configuring per-user commands, to revert back. The unconfiguration may fail due to parser or AAA error.
Recommended Action The given unconfigure command was not executed. Switch on the debug peruser command and repeat the steps that caused the error. If you get the error, Report it to your technical support representative.
Error Message %AAA-3-SG_DEADTIME_FORKFAIL: Failed to fork process for %s.Explanation Quite likely, we ran out of memory. Other explanations are possible.
Recommended Action If this message recurs. Check bug toolkit on Cisco website for the issue. If you didn't find one, Enter Show tech-support command, collect all the information and error message and report it to your technical support representative.
Error Message %AAA-3-SG_INTERNAL_ERROR: server group '%s': %sExplanation This is an internal software error in the AAA server group subsystem.
Recommended Action This is an internal software error. Check bug toolkit on Cisco website for the issue. If you didn't find one, Enter Show tech-support command, collect all the information and error message, report it to your technical support representative.
Error Message %AAA-3-SG_TESTPROC_FORKFAIL: Failed to fork process for %s.Explanation Quite likely, we ran out of memory. Other explanations are possible.
Recommended Action If this message recurs. Check bug toolkit on Cisco website for the issue. If you didn't find one, Enter Show tech-support command, Collect all the information and error message and report it to your technical support representative.
Error Message %AAA-3-UNAVAILABLE: %s %s: Can not apply configuration to ISDN channel: %sExplanation Configuration can not be applied to individual ISDN channels.
Recommended Action You need virtual-profiles and virtual-access interfaces to apply configuration to ISDN. Refer to the section on Configuring virtual profiles by AAA Configuration in the Cisco IOS Dial Technologies Configuration Guide.
Error Message %AAA-3-UNAVAILABLE: %s :Peruser Could not sort the %s attributesExplanation 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 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-UNAVAILABLE: AAA ACCT process suspended : low I/O memoryExplanation 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. 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-UNAVAILABLE: AAA ID %uExplanation 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 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-UNAVAILABLE: AAA unable to create UID for incoming calls due to insufficient processor memoryExplanation 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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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-UNAVAILABLE: AAA unable to handle accounting requests due to insufficient memory. So, we trash all queued accounting reguests, which may worry customerPlease upgrade your memory or plan to get more free memory by optimizing your configuration.Explanation Dropping the accounting request as there is no enough 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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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-UNAVAILABLE: Accounting record dropped, send to server failed: %sExplanation 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 %AAA-3-UNAVAILABLE: Attribute with unknown format %dExplanation An attribute was found with an invalid format
Recommended Action Attribute with unknown format in definition, call your technical support representative
Error Message %AAA-3-UNAVAILABLE: 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-UNAVAILABLE: Cannot process %s method %sExplanation 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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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-UNAVAILABLE: Cannot process %s method %uExplanation 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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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-UNAVAILABLE: Cannot process %s server type %sExplanation A method list function encountered a server type that was unknown, or could not be handled. This may be due to a server misconfiguration.
Recommended Action Research the cause of the misconfiguration and attempt to correct it, otherwise take the following action. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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-UNAVAILABLE: Data structure failed magic number sanity checkExplanation 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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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-UNAVAILABLE: Error(%d) parser is unable to parse %s per-user commandExplanation All attempts to parse this per_user unconfigure command failed.
Recommended Action The given unconfigure command was not unconfigured. Report it to your technical support representative.
Error Message %AAA-3-UNAVAILABLE: Failed to fork process for %s.Explanation Quite likely, we ran out of memory. Other explanations are possible.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message %AAA-3-UNAVAILABLE: Invalid use of ip_pid(%u)Explanation This message means a process sent an illegal message to IP which IP has not subscribed for
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message %AAA-3-UNAVAILABLE: Null cursorExplanation A AAA client has provided a non-existant 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 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-UNAVAILABLE: Null vrf entryExplanation A NULL vrf entry 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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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-UNAVAILABLE: RADIUS process is unable to handle the requests due to insufficient low I/O memoryExplanation RADIUS process unable to handle request due to insufficient IO memory. Hence 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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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-UNAVAILABLE: Radius I/O buffer has overflowedExplanation An unusually large number of Radius attributes has caused AAA to overflow it's Radius I/O buffer
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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-UNAVAILABLE: Server '%i': %sExplanation This is an internal software error in the AAA server group 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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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-UNAVAILABLE: Unknown protocol %uExplanation 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 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-UNAVAILABLE: Unknown service %uExplanation 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 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-UNAVAILABLE: invalid cursor index %d max %d service %s protocol %sExplanation 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 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-UNAVAILABLE: invalid hdl AAA ID %u, hdl %x, %sExplanation 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 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-UNAVAILABLE: invalid list AAA ID %uExplanation 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 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-UNAVAILABLE: invalid parameter was used when accessing AAA functionExplanation 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 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-UNAVAILABLE: method list '%s'Explanation This is an internal software error. An AAA client attempted to add too many methods to a method list.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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-UNAVAILABLE: method list '%s': %sExplanation 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 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-UNAVAILABLE: server group '%s': %sExplanation This is an internal software error in the AAA server group 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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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.
AAA-6
Error Message %AAA-6-ACCTSESSIDWRAP: Accounting-Session-ID %d exceeded max value allowedExplanation Accounting-Session-ID value exceeded max value allowed
Recommended Action This is informational only, not a error.
Error Message %AAA-6-ACCTSESSIDWRAP: Accounting-Session-ID %d exceeded max value allowedExplanation Accounting-Session-ID value exceeded max value allowed. Now it is wrapping.
Recommended Action This is informational only, not an error.
Error Message %AAA-6-UNAVAILABLE: Accounting-Session-ID %d exceeded max value allowedExplanation Accounting-Session-ID value exceeded max value allowed
Recommended Action This is informational only, not a error.
Error Message %AAA-6-UNAVAILABLE: Enable view requires to be authenticated by non-none methods,Please use the appropriate method with the login authenticationExplanation 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 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.
AAAA Messages
This section contains TACACS+ authentication, authorization, and accounting security messages.
AAAA-3
Error Message %AAAA-3-ACCTATTR: last accounting attribute:Explanation The data buffer overflowed while building the accounting packet.The accounting attribute that was being written to the buffer while the buffer overflow occured was logged.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AAAA-3-ACCTDUMP: dump of accounting data:Explanation The data buffer overflowed while building the accounting packet as the total length of the attributes exceed the buffer size. Last 128 bytes of buffer data is dumped.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AAAA-3-BADAUTHENSTR: Bad authentication data: %sExplanation The data buffer overflowed while building the authentication packet as the total length of the attributes exceeded the buffer size.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AAAA-3-BADREG: Illegal registry call.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. 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 %AAAA-3-BADSTR: Bad accounting data: %sExplanation 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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AAAA-3-DROPACCTFULLQ: Accounting record dropped due to a full aaa accounting queue: %s-%s %s %sExplanation 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-INTERNAL_ERROR: %sExplanation 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 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 %AAAA-3-NULUSR: accounting for null userExplanation 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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AAAA-3-RELOGIN: sanity check in re-login %s to %sExplanation 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 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 %AAAA-3-UNAVAILABLE: %% 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 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 %AAAA-3-UNAVAILABLE: %sExplanation Administrative process has been enabled but somehow could not run
Error Message %AAAA-3-UNAVAILABLE: %% AAA: No free %s lists for %sExplanation You have reached the maximum number of possible authentication lists for this method.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AAAA-3-UNAVAILABLE: %% AAA: bad %s list %sExplanation 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 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 %AAAA-3-UNAVAILABLE: %% 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 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 %AAAA-3-UNAVAILABLE: %% 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 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 %AAAA-3-UNAVAILABLE: %s AUTHOR/%s: Internal state is invalid: astruct 0x%x ustruct 0x%xExplanation 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 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 %AAAA-3-UNAVAILABLE: %sExplanation 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 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 %AAAA-3-UNAVAILABLE: %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 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 %AAAA-3-UNAVAILABLE: %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 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 %AAAA-3-UNAVAILABLE: 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 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 %AAAA-3-UNAVAILABLE: 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 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 %AAAA-3-UNAVAILABLE: Accounting record dropped due to a full aaa accounting queue: %s-%s %s %sExplanation 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-UNAVAILABLE: Accounting record dropped due to low memory: %s-%s %s %sExplanation 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-UNAVAILABLE: Accounting record dropped, send to server failed: %s-%s %s %sExplanation 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-UNAVAILABLE: Bad Subtype %d for %s (%d)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 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 %AAAA-3-UNAVAILABLE: Bad accounting data: %sExplanation 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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AAAA-3-UNAVAILABLE: Bad authentication data: %sError Message %AAAA-3-UNAVAILABLE: Could not establish port informationExplanation 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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AAAA-3-UNAVAILABLE: Duplicate free of server group 0x%xExplanation 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 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 %AAAA-3-UNAVAILABLE: 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-UNAVAILABLE: 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 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 %AAAA-3-UNAVAILABLE: 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-UNAVAILABLE: 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-UNAVAILABLE: 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-UNAVAILABLE: Illegal %s %s name %s rejectedExplanation 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-UNAVAILABLE: Illegal registry call.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. 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 %AAAA-3-UNAVAILABLE: 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.
Error Message %AAAA-3-UNAVAILABLE: 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-UNAVAILABLE: No name for servergroup in method %sExplanation 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. 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 %AAAA-3-UNAVAILABLE: 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 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 %AAAA-3-UNAVAILABLE: Overwrote internal buffer space %sExplanation 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 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 %AAAA-3-UNAVAILABLE: 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 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 %AAAA-3-UNAVAILABLE: 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 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 %AAAA-3-UNAVAILABLE: accounting for null userExplanation 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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AAAA-3-UNAVAILABLE: accounting record dropped, output record queue full: %s-%s %s %sExplanation An accounting record was dropped. The record could not be enqueued because the number of records in the output queue has exceeded the system limit.
Recommended Action Disable periodic accounting if it is on. [no] aaa accounting update newinfo periodic
Error Message %AAAA-3-UNAVAILABLE: sanity check in re-login %s to %sExplanation 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-UNAVAILABLE: 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 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.
AAAA-4
Error Message %AAAA-4-UNAVAILABLE: %% 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-4-UNAVAILABLE: Bad %s method-list name %s (this is only a warning)Explanation A method-list name should not be the same as a method name. Please choose a different name for the method list.
Recommended Action Pick a different method-list name, that is not also a method-name.
Error Message %AAAA-4-UNAVAILABLE: Bad server-group name %s (type %s).Explanation The given server-group name either doesn't exist or the given type does not match the defined server-group.
Recommended Action Verify that the group exists and has the same type.
Error Message %AAAA-4-UNAVAILABLE: Server-group %s is not of type %s.Explanation The given server-group name does not match the specified type
Recommended Action Verify that the group exists and has the same type.
Error Message %AAAA-4-UNAVAILABLE: The aaa cache process is not created. Please configure aaa cache profile firstExplanation 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-UNAVAILABLE: 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-UNAVAILABLE: 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-UNAVAILABLE: Warning: DNIS group %s is not defined.Explanation The DNIS group was used without defining it first. It should be defined before use.
Recommended Action Define the DNIS group before using it.
Error Message %AAAA-4-UNAVAILABLE: Warning: Server %i is not defined.Explanation The given server is not on the master-list, and should be defined, or unexpected things might happen.
Recommended Action Please define the server on the appropriate master-list as soon as possible.
Error Message %AAAA-4-UNAVAILABLE: Warning: Server %i:%d,%d is not part of server group %s.Explanation 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-6-UNAVAILABLE: %s %s: %sExplanation 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-UNAVAILABLE: %s %s: %sExplanation 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
Error Message %AAAA-6-UNAVAILABLE: %sExplanation A AAA accounting start message.
Recommended Action This information is for information only.
Error Message %AAAA-6-UNAVAILABLE: %sExplanation A AAA accounting stop message.
Recommended Action This information is for information only.
Error Message %AAAA-6-UNAVAILABLE: %sExplanation A AAA accounting watchdog/update message.
Recommended Action This information is for information only.
AAL-5
Error Message %AAL5-1-UNAVAILABLE: %s: No buffer available for size %d bytesExplanation There is no memory 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 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 %AAL5-1-UNAVAILABLE: %sExplanation There is no memory available for allocation from heap. 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 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 %AAL5-1-UNAVAILABLE: msgtxt_nomemoryExplanation An operation could not be accomplished because of a low-memory condition. The current system configuration, network environment, or possibly a software error might have exhausted or fragmented the system's memory.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a configuration that has more memory.
Error Message %AAL5-2-UNAVAILABLE: %sExplanation 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 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 %AAL5-3-UNAVAILABLE: %sExplanation 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 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 %AAL5-3-UNAVAILABLE: %sExplanation The AAL5 subsystem 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 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 %AAL5-3-UNAVAILABLE: %x, orig %x, port=%sExplanation This message is only seen during AAL5 debug. It is used for debugging AAL5 errors
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AAL5-3-UNAVAILABLE: Flow Hdr: (%d) %sExplanation AAL5 datapath has received a large packet it cannot handle or there are no more buffers available. So the packet is dropped. 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 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 %AAL5-3-UNAVAILABLE: Flow Hdr: (%d) %sExplanation AAL5 datapath has received a packet with AAL5 checksum error. So the packet is dropped. 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 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 %AAL5-3-UNAVAILABLE: Input Interface %s: %sExplanation AAL5 datapath has received a packet with invalid encap for packet type(DATA, CNTL,..). Th packet is dropped. 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 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.
AAA_CACHE Messages
This section contains authentication, authorization, and accounting cache messages.
Error Message %AAA_CACHE-3-NULL_TREE_PERIODIC_PROC: Cache Tree pointer is of null valueExplanation The cache tree pointer is of null 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 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_CACHE-3-UNAVAILABLE: Cache Tree pointer is of null valueExplanation The cache tree pointer is of null 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 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.
AC Messages
Error Message %AC-3-AC_PROVISION: %sExplanation An error was encountered during Attachment Circuit [un]provisioning.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AC-3-AC_SUBBLOCK: %sExplanation 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 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 %AC-3-AC_VECTOR: %sExplanation An error was encountered during Attachment Circuit configuration which 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 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 %AC-3-UNAVAILABLE: %sExplanation An error was encountered during Attachment Circuit [un]provisioning.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AC-3-UNAVAILABLE: %sExplanation An error was encountered during Attachment Circuit configuration which 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 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 %AC-3-UNAVAILABLE: %sExplanation 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 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 %AC-3-UNAVAILABLE: Circuit info missing in %s message.Explanation AC Manager received message with missing circuit info
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AC-3-UNAVAILABLE: Corrupted L2SS handle [%x].Explanation An internal L2SS Manager 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. 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-UNAVAILABLE: Encountered a NULL context in %sExplanation 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 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 %AC-3-UNAVAILABLE: Received %sExplanation Attachment Circuit Manager recieves 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 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 %AC-3-UNAVAILABLE: Received invalid %s handleExplanation Attachment Circuit Manager recieves 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 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 %AC-3-UNAVAILABLE: Received unexpected %s messageExplanation 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 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 %AC-3-UNAVAILABLE: Wrong set of keys in %s messageExplanation 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 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.
ACCESS_IE Messages
Error Message %ACCESS_IE-3-UNAVAILABLE: 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 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.
ACE Messages
This section contains access control encryption messages.
ACE-2
Error Message %ACE-2-UNAVAILABLE: Crypto engine error: %s (%d)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-UNAVAILABLE: Internal %s table error: %sExplanation Internal table operation fails. This means the state of the module is mostly like 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 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.
ACE-3
Error Message %ACE-3-INITFAIL: %s: initialization failed (%s)Explanation ACE initialization sequence 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 nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %ACE-3-INVTID: %s: %s of invalid %s trans id %dExplanation An invalid transaction ID of for the indicated transaction type was encountered
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ACE-3-NOMORETID: %s: out of %s transactionsExplanation Transaction pool for the indicated transaction type was exhausted.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ACE-3-UNAVAILABLE: %s: %s NAK trans 0x%x; opcode 0x%x; param 0x%xExplanation An negative acknowledge occured in the indicated control transaction.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ACE-3-UNAVAILABLE: %s: %s of invalid %s trans id %dExplanation An invalid transaction ID of for the indicated transaction type was encountered
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ACE-3-UNAVAILABLE: %s: %s trans 0x%x; opcode 0x%x (%s); param 0x%x; error 0x%x (%s); retry cnt %dExplanation An error occured in the indicated control transaction.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ACE-3-UNAVAILABLE: %s: %s trans 0x%x; opcode 0x%x (%s); param 0x%x; too many retriesExplanation An error occured in the indicated control transaction.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ACE-3-UNAVAILABLE: %s: %s trans 0x%x; opcode 0x%x; param 0x%x; error 0x%x; retry cnt %dExplanation An error occured in the indicated control transaction.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ACE-3-UNAVAILABLE: %s: Received truncated HAPI message (tlen=%d, actual=%d)Explanation The received ACE control packet was smaller than the size field indicated
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ACE-3-UNAVAILABLE: %s: boot error: %sExplanation 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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ACE-3-UNAVAILABLE: %s: crashdump retrieval error: %s %sExplanation An error occurred during crashdump file retrieval from ACE.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ACE-3-UNAVAILABLE: %s: crashdump retrieval initiated to file %sExplanation 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-UNAVAILABLE: %s: initialization failed (%s)Explanation ACE initialization sequence 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 nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %ACE-3-UNAVAILABLE: %s: out of %s transactionsExplanation Transaction pool for the indicated transaction type was exhausted.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ACE-3-UNAVAILABLE: ACE %s failed to register.Explanation The ACE failed to register with CEAL
Recommended Action Reset the hw module
Error Message %ACE-3-UNAVAILABLE: Interface %s has no crypto engine slotExplanation 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-UNAVAILABLE: Too many %s in the system. Cannot allocate a new oneExplanation All VPN-accelerator resources of a particular are in used and thus this allocation request fails.
Recommended Action Remove the crypto map 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-UNAVAILABLE: Too may %s IDs in the system. Cannot allocate a new oneExplanation 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.
ACE-6
Error Message %ACE-6-UNAVAILABLE: %s has been moved from %s to %s to relieve congestionExplanation The congestion manager has moved a tunnel from a congested crypto engine to an uncongested crypto engine
Recommended Action System performance is not affected. No customer action is necessary.
Error Message %ACE-6-UNAVAILABLE: %s: %sExplanation This is informational message from ACE
Recommended Action This is informational message from ACE. This occurs in normal operation.
Error Message %ACE-6-UNAVAILABLE: %s: boot info: %sExplanation 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-UNAVAILABLE: %s: crashdump retrieval completeExplanation 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-UNAVAILABLE: %s: received unexpected IPsec packet: src IP: %i; dst IP: %i; firsthop/lasthop = %s/%s (count=%d)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.
Error Message %ACE-6-UNAVAILABLE: %s: received unexpected IPsec packet: src: %s; dst: %s; (count=%d)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-UNAVAILABLE: All crypto engines are congested, assigning %s to %sExplanation The congestion manager has assigned a new tunnel to an already congested crypto engine. All crypto engines have indicated congestion, the least congested engine was selected for the tunnel
Recommended Action Packets may be lost on some tunnels, either reduce bandwidth used by existing tunnels or install additional crypto engines
Error Message %ACE-6-UNAVAILABLE: VPN-SPA switchover: %d/%d has been %s %d/%dExplanation A blade to blade switcover has occurred. System performance is not affected.
Recommended Action System performance is not affected. No customer action is necessary.
ACLMEGR-3
Error Message %ACLMERGE-3-CUDDERROR: A CUDD Library error was detected in %sExplanation 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
ACLMGR-2
Error Message %ACLMGR-2-UNAVAILABLE: Cannot create ACL Manager data structures for VLAN Map %sExplanation 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 Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ACLMGR-2-UNAVAILABLE: Cannot create VMR data structures for access list %sExplanation 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-2-UNAVAILABLE: Cannot create memory block for VLAN %dExplanation 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.
ACLMGR-3
Error Message %ACLMGR-3-UNAVAILABLE: %s ACL merge error %d (%s) on %s label %dExplanation 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-UNAVAILABLE: Acl Tcam Full! Sofware Forwarding packets on %s label %d on %s %sExplanation 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-UNAVAILABLE: Augmenting of access-map %s on %s label %d failedExplanation The system ran out of CPU DRAM when attempting to merge internally required elements with the configuredaccess map(s).
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ACLMGR-3-UNAVAILABLE: Cannot allocate %s label for vlan-id %dExplanation 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-UNAVAILABLE: Insert of access-map %s #%d into %s label %d failedExplanation The system ran out of CPU DRAM when trying to merge sections of an access 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 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 %ACLMGR-3-UNAVAILABLE: Reloading %s label %d featureExplanation 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 Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ACLMGR-3-UNAVAILABLE: Too many (%d) levels of recursion while merging ACLs (code %d).Explanation 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-UNAVAILABLE: Unknown VMR access group action 0x%xExplanation 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. 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 %ACLMGR-3-UNAVAILABLE: Unloading %s label %d featureExplanation 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.
ACL_HDL_HA_API-3
Error Message %ACL_HDL_HA_API-3-UNAVAILABLE: %sExplanation A run-time module could not obtain the resources that are required to complete a task. The failure most likely occurred because of a software error or a lack of system memory. Additional details on the nature of the error are specified in the message text on the console or in the system log. The system state between the active and standby units might not be properly synchronized.
Recommended Action If you determine that this condition was caused by a lack of system memory, reduce system activity to ease memory demands, or if conditions warrant, upgrade to a larger memory configuration. 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 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 %ACL_HDL_HA_API-3-UNAVAILABLE: Failed to register with %s, rc =%dExplanation A redundancy client could not be registered. An internal failure associated with client registration occurred in the run-time module specified in the message output. The return code that is specified in the message output identifies the type of failure that was detected. The failure most likely occurred because of a software error. The system state between the active and standby units might not be properly synchronized.
Recommended Action .Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ACL_HDL_HA_API-3-UNAVAILABLE: Failed to send %s message to active for %s, rc=%dExplanation The specified synchronization message, which is an internal IPC message, could not be sent to the active unit in the specified run-time module. The failure most likely occurred because of a software error. Additional details on the nature of the error are specified in the message text on the console or in the system log. The system state between the active and standby units might not be properly synchronized.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ACL_HDL_HA_API-3-UNAVAILABLE: Failed to send %s message to standby for %s, rc=%dExplanation The specified synchronization message, which is an internal IPC message, could not be sent to the standby unit in the specified run-time module. The failure most likely occurred because of a software error. The numeric error code in the message output identifies the type of failure. The system state between the active and standby units might not be properly synchronized.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ACL_HDL_HA_API-3-UNAVAILABLE: Invalid %s message receivedExplanation A message that is used for state synchronization was not received correctly. An internal data structure for a message could not be retrieved. The failure most likely occurred because of a software error. The system state between the active and standby units might not be properly synchronized.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ACL_HDL_HA_API-3-UNAVAILABLE: Invalid checkpointing status code received, rc=%dExplanation An invalid checkpoint status code has been detected. An internal status code that is associated with checkpointing was found to be invalid. The return code that is specified in the message output identifies the invalid code that was detected. The failure most likely occurred because of a software error. The system state between the active and standby units might not be properly synchronized.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ACL_HDL_HA_API-3-UNAVAILABLE: No checkpointing buffer for %s, rc=%dExplanation A message data buffer that is used for state synchronization could not be obtained. An internal data structure could not be allocated for synchronization in the run-time module specified in the message output. The return code that is specified in the message output identifies the type of failure. The failure most likely occurred because of a software error or a lack of system memory. The system state between the active and standby units might not be properly synchronized.
Recommended Action If you determine that this condition was caused by a lack of system memory, reduce system activity to ease memory demands, or if conditions warrant, upgrade to a larger memory configuration. 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 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 %ACL_HDL_ISSU-2-UNAVAILABLE: ACL handle ISSU client encountered unexpected client nego_done. Error: %d (%s)Explanation An ISSU-compliant client transitions through a series of internal states. The ACL handle 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 Show issu session and show issu negotiated capability )
Error Message %ACL_HDL_ISSU-2-UNAVAILABLE: ACL handle ISSU client failed to get buffer for message. Error: %d (%s)Explanation The ACL handle 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 Show logging and show checkpoint client. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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.
Recommended Action
Error Message %ACL_HDL_ISSU-2-UNAVAILABLE: ACL handle ISSU client failed to register session information. Error: %d (%s)Explanation The ACL handle 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 Show issu capability entries, issu session and show issu negotiated capability. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ACL_HDL_ISSU-2-UNAVAILABLE: ACL handle ISSU client failed to send negotiation message. Error: %d (%s)Explanation The ACL handle 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 Show logging and show checkpoint client. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ACL_HDL_ISSU-2-UNAVAILABLE: ACL handle ISSU client initialization failed to %s. Error: %d (%s)Explanation The ACL handle 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 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 %ACL_HDL_ISSU-3-UNAVAILABLE: 'Message Type %d' is not supported by ACL handle ISSU client at peerExplanation The ACL handle ISSU client at the peer supervisor is not compatible for this message type. The ACL handle client will be marked as incompatible with the peer.
Recommended Action Show issu capability entries, issu session and show issu negotiated capability. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ACL_HDL_ISSU-3-UNAVAILABLE: ACL handle ISSU client %s transform failed for 'Message Type %d'. Error: %d (%s)Explanation The ACL handle 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 ACL handle state between the active device and the standby device is not identical.
Recommended Action Show issu session and show issu negotiated version. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ACL_HDL_ISSU-3-UNAVAILABLE: ACL handle ISSU client 'Message Type %d' is not compatibleExplanation The ACL handle ISSU client received an incompatible message from the peer device. The message cannot be processed.
Recommended Action Show issu session and show issu negotiated version. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ACL_HDL_ISSU-3-UNAVAILABLE: ACL handle ISSU client capability exchange result incompatible.Explanation The Switch Vlam ISSU client capability exchange have negotiated as incompatible with the peer.
Recommended Action Show issu capability entries, issu session and show issu negotiated capability. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ACL_HDL_ISSU-3-UNAVAILABLE: ACL handle ISSU client capability list is empty.Explanation The ACL handle ISSU client capability exchange list size is invalid.
Recommended Action LShow issu capability entries, issu session and show issu negotiated capability. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ACL_HDL_ISSU-3-UNAVAILABLE: ACL handle ISSU client does not have a valid registered session.Explanation The ACL handle ISSU client does not have a valid registered session.
Recommended Action Show issu session and show issu negotiated version. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ACL_HDL_ISSU-3-UNAVAILABLE: ACL handle ISSU client failed to get the MTU for Message Type %d.Error: %d (%s)Explanation The ACL handle ISSU client failed to calculate the MTU for the specified message. The ACL handle ISSU client is not able to send the message to the standby device.
Recommended Action Show issu session and show issu negotiated version. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ACL_HDL_ISSU-3-UNAVAILABLE: ACL handle ISSU client failed to unregister session information. Error: %d (%s)Explanation The ACL handle ISSU client failed to unregister session information.
Recommended Action Show issu session and show issu negotiated version. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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.
ADJ Messages
This section contains adjacency (ADJ) subsystem messages.
ADJ-3
Error Message %ADJ-3-UNAVAILABLE: Adj bundles: %sExplanation 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 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 %ADJ-3-UNAVAILABLE: Adj resolve request: %s %s %sExplanation 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 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 %ADJ-3-UNAVAILABLE: Adj stack2 error %s: %sExplanation 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 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 %ADJ-3-UNAVAILABLE: Adjacency distribution client: %sExplanation 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 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 %ADJ-3-UNAVAILABLE: Adjacency mac address for %s overflowed by %d bytesExplanation 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 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 %ADJ-3-UNAVAILABLE: Adjacency mac string for %s not byte aligned, offset %x, length %xExplanation 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 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 %ADJ-3-UNAVAILABLE: Allocating adj when adj subsystem downExplanation 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 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 %ADJ-3-UNAVAILABLE: Bundle type %s must be ISSU aware to send to slot(s) %sExplanation 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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ADJ-3-UNAVAILABLE: CEF Interface not found - %sExplanation 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 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 %ADJ-3-UNAVAILABLE: Failed to allocate an adjacencyExplanation An internal software error 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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ADJ-3-UNAVAILABLE: Failed to allocate an adjacency debug filter blockExplanation An internal software error 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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ADJ-3-UNAVAILABLE: Failed to allocate an adjacency interest list subblockExplanation An internal software error 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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ADJ-3-UNAVAILABLE: Failed to allocate an adjacency summary event blockExplanation An internal software error 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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ADJ-3-UNAVAILABLE: Failed to allocate memory %sExplanation An internal software error 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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ADJ-3-UNAVAILABLE: Failed to deallocate an adjacency interest list subblockExplanation An internal software error 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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ADJ-3-UNAVAILABLE: Failed to deallocate memory %sExplanation 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 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 %ADJ-3-UNAVAILABLE: Failed to dispatch a refresh adjacency summary eventExplanation 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 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 %ADJ-3-UNAVAILABLE: Failed to enqueue an adjacency summary event blockExplanation 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 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 %ADJ-3-UNAVAILABLE: Failed to initialise adjacency RP broker facilityExplanation 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 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 %ADJ-3-UNAVAILABLE: Failed to initialise adjacency interest list facilityExplanation 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 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 %ADJ-3-UNAVAILABLE: Failed to initialise adjacency subblock facilityExplanation 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 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 %ADJ-3-UNAVAILABLE: Generation of encapsulation string for %s failedExplanation 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 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 %ADJ-3-UNAVAILABLE: Illegal arguments - %sExplanation 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 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 %ADJ-3-UNAVAILABLE: Unexpected state transition from %s to %sExplanation 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 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 %ADJ-3-UNAVAILABLE: Using an unsupported address type %d when trying to add/delete/modify/find an adjacencyExplanation An internal software error 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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ADJ-3-UNAVAILABLE: Using an unsupported linktype %s when trying to add/delete/modify/find an adjacencyExplanation An internal software error 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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ADJ-3-UNAVAILABLE: Zero address length detected distributing adj %sExplanation An internal software error 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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ADJ-3-UNAVAILABLE: adjacency %s is followed by bad magicExplanation 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 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 %ADJ-3-UNAVAILABLE: adjacency mac string end %x not %s alignedExplanation 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 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.
ADJ-5
Error Message %ADJ-5-UNAVAILABLE: Midchain parent maintenance for %s - %sExplanation 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 Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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.
AFLSEC
Error Message %AFLSEC-6-OALRL: Oal logging rate-limited or missed %d packet%sExplanation 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 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 %AFLSEC-6-OALRL: Oal logging rate-limited or missed %d packet%sExplanation Some packet matching logs were missed because the logmessages 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 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.
AGGMGR
Error Message %AGGMGR-0-UNAVAILABLE: No space left for creator %s to add data item to agg list (items %d max %d remaining %d)Explanation An attempt was made to add an item to an aggregation list that had just been successfully created but for some reason the add failed. This situation should never occur. If it does occur, then it is the result of a program error which would be found during development and considered an internal error. There is no work around.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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.
AIP
Error Message %AIP-3-UNAVAILABLE: %s Failed to setup vc %d (Cause: %s)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 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 %AIP-3-UNAVAILABLE: Interface %s, Failed to setup vc %d (Cause: %s) Expected range [%d .. %d]Kbps for AIP Average Rate Metering. Average Rate=Peak Rate= %d Kbps turns Average Rate Metering OFFExplanation 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 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.
ALARM
Error Message %ALARM-1-UNAVAILABLE: CRITICAL alarm condition detectedExplanation An critical alarm event has happened, it will cause the serious result, and needs immediate attention and to be fixed. Syetem will shut down within two minutes.
Recommended Action Check the source of the critical alarms to take corresponding actions. Don't turn on power unless the situation is corrected. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ALARM-2-UNAVAILABLE: Major alarm condition detectedExplanation An major alarm event has happened, it will affect the system service, and needs attention or fix.
Recommended Action Check the source of the major alarms to take corresponding actions. This situation should be corrected or be aware of. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ALARM-3-UNAVAILABLE: Attempt to change alarm status for undefined typeExplanation The alarm subsystem has no record of this type of alarm. The type has either not be registered or has been deleted.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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 %ALARM-3-UNAVAILABLE: Attempt to set alarm status for undefined sourceExplanation The alarm subsystem has no record of this alarm source. The source has either not be registered or has been deleted.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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 %ALARM-3-UNAVAILABLE: Max number of alarm sources exceededExplanation 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 information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %ALARM-3-UNAVAILABLE: Minor alarm condition detectedExplanation 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 information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %ALARM-3-UNAVAILABLE: No alarm messages leftExplanation There we no more alarm messages available in the message cache
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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 %ALARM-3-UNAVAILABLE: OUT of Memory: %sError Message %ALARM-3-UNAVAILABLE: Unknown Alarm Severity ClassExplanation The alarm status tables contain an alarm entry with an unknown alarm severity class.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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 %ALIGN-3-UNAVAILABLE: %sExplanation A trace that shows where the previous ALIGN 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 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.
ALIGN Messages
This section contains ALIGN messages.
ALIGN-3
Error Message %ALIGN-3-TRACE: -Traceback= %08x %08x %08x %08x %08x %08x %08x %08xExplanation A trace that shows where the previous ALIGN 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 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 %ALIGN-3-UNAVAILABLE: -Traceback= %08x %08x %08x %08x %08x %08x %08x %08xExplanation A trace that shows where the previous ALIGN 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 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 %ALIGN-3-UNAVAILABLE: -Traceback= %sExplanation A trace that shows where the previous ALIGN 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 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 %ALIGN-3-UNAVAILABLE: Alignment correction made at %s %sing %sExplanation A software component within the router needs memory optimization.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ALIGN-3-UNAVAILABLE: Alignment correction made at 0x%x %sing 0x%xExplanation A software component within the router needs memory optimization.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ALIGN-3-UNAVAILABLE: Alignment log is full - no new entries will be recordedExplanation The router identified more software components in need of memory optimization than it can record.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ALIGN-3-UNAVAILABLE: Spurious memory access made at %s reading %sExplanation 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-UNAVAILABLE: Spurious memory access made at 0x%x reading 0x%xExplanation 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-UNAVAILABLE: Spurious memory access made at 0x%x reading 0x%xExplanation An error was identified (and temporarily corrected) within a software component in the router.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ALIGN-3-UNAVAILABLE: Warning : read accees failed at %s, still continuingExplanation 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 %ALPS-3-UNAVAILABLE: ALPS: Assertion failed: %sExplanation 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. 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
This section contains Airline Product Set (ALPS) messages.
ALPS-3
Error Message %ALPS-3-UNAVAILABLE: ALPS: Assertion failed: %sExplanation 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. 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-UNAVAILABLE: 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-UNAVAILABLE: Polling for ASCU %02x on interface %s is stalled.Explanation The polling mechanism for an ALPS interface has become stuck.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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.
ALPS-5
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 agent set control unit (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 agent set control unit (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 agent set control unit (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_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 %ALIGN-3-UNAVAILABLE: Warning : read accees failed at %s, still continuingExplanation 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.
ALPS-5
Error Message %ALPS-5-UNAVAILABLE: ASCU %02x on interface %s has been disabled since 4 consecutive messages were received from same SID.Explanation An ALPS ASCU has been automatically disabled.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ALPS-5-UNAVAILABLE: ASCU %02x on interface %s is down.Explanation An ALPS ASCU has transitioned from up to down.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ALPS-5-UNAVAILABLE: ASCU %02x on interface %s is up.Explanation An ALPS ASCU has transitioned from down to up.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ALPS-5-UNAVAILABLE: Circuit %s changed state to closed, rsn = %s.Explanation An ALPS circuit has tranistioned from open to closed
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ALPS-5-UNAVAILABLE: Circuit %s changed state to open.Explanation An ALPS circuit has transitioned from closed to open.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ALPS-5-UNAVAILABLE: Peer (%i, %s) ID modified to (%i, %s).Explanation An ALPS peer connection identifier has changed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ALPS-5-UNAVAILABLE: Peer (%i, %s) changed state to closed.Explanation An ALPS peer connection is now closed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ALPS-5-UNAVAILABLE: Peer (%i, %s) changed state to open.Explanation An ALPS peer connection is now open.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ALPS-5-UNAVAILABLE: Peer (%i, %s) closed due to inactivity.Explanation An ALPS peer connection is now closed due to inactivity.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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.
ALPS-6
Error Message %ALPS-6-UNAVAILABLE: Circuit %s has entered a congested state.Explanation An ALPS circuit is experiencing congestion.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ALPS-6-UNAVAILABLE: Circuit %s received a Circuit Open Confirm with a list of rejected ascusExplanation An ALPS circuit sent a Circuit Open Request message and received a Circuit Open Confirm with a list of rejected ascus.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ALPS-6-UNAVAILABLE: Circuit %s received a Circuit Open Failed message, rsn = %s.Explanation An ALPS circuit sent a Circuit Open Request message and received a Circuit Open Failed message as a reply.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ALPS-6-UNAVAILABLE: Circuit %s received a Circuit Open Failed message, rsn = %s.Explanation An ALPS circuit sent a Circuit Update message and received a Circuit Open Failed message as a reply.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ALPS-6-UNAVAILABLE: Host unresponsive on X.25 VC for circuit %sExplanation 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-UNAVAILABLE: Peer (%i, %s) has entered a congested state.Explanation An ALPS peer connection is experiencing congestion.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ALPS-6-UNAVAILABLE: Peer (%i, %s) has exited a congested state.Explanation An ALPS peer connection is no longer experiencing congestion.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ALPS-6-UNAVAILABLE: Peer (%i, %s) open failed, rsn = %sExplanation An ALPS peer connection attempted to open, but failed to open.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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.
ALPS-7
Error Message %ALPS-7-UNAVAILABLE: Circuit %s has exited a congested state.Explanation An ALPS circuit is no longer experiencing congestion.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ALPS-7-UNAVAILABLE: Threshold exceeded for TCP Queue overflow peer drops for peer (%i, %s).Explanation The number of ALPS peer drops due to queue overflow exceeds the ALPS peer threshold 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 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 %ALPS-7-UNAVAILABLE: Threshold exceeded for X.25 VC Reset drops for circuit %sExplanation The number of ALPS circuit drops due to X.25 VC Reset exceeds the ALPS circuit threshold 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 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 %ALPS-7-UNAVAILABLE: Threshold exceeded for circuit disabled drops for circuit %sExplanation The number of ALPS circuit drops due to circuit disabled exceeds the ALPS circuit threshold 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 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 %ALPS-7-UNAVAILABLE: Threshold exceeded for invalid ASCU drops for circuit %sExplanation The number of ALPS circuit drops due to invalid ASCU identifier exceeds the ALPS circuit threshold 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 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 %ALPS-7-UNAVAILABLE: Threshold exceeded for lifetime timer expiration drops for circuit %sExplanation The number of ALPS circuit drops due to lifetime timer expiration exceeds the ALPS circuit threshold 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 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 %ALPS-7-UNAVAILABLE: Threshold exceeded for maximum size exceeded drops for peer (%i, %s).Explanation The number of ALPS peer drops due to maximum size exceeded exceeds the ALPS peer threshold 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 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 %ALPS-7-UNAVAILABLE: Threshold exceeded for peer unreachable peer drops for peer (%i, %s).Explanation The number of ALPS peer drops due to a peer unreachable condition exceeds the ALPS peer threshold 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 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 %ALPS-7-UNAVAILABLE: Threshold exceeded for queue overflow drops for circuit %sExplanation The number of ALPS circuit drops due to queue overflow exceeds the ALPS circuit threshold 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 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 %ALPS-7-UNAVAILABLE: Threshold exceeded for version mismatch peer drops for peer (%i, %s).Explanation The number of ALPS peer drops due to version mismatch exceeds the ALPS peer threshold 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 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.
AMDP2-FE-1
Error Message %AMDP2_FE-1-UNAVAILABLE: %s CSR%d=0x%04xExplanation 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 the message recurs, call your technical support representative for assistance.
Error Message %AMDP2_FE-1-UNAVAILABLE: %s CSR%d=0x%04xExplanation The software failed to initialize/restart an Ethernet/Fast Ethernet interface.
Recommended Action Try resetting the interface by doing a shutdown followed by a no shutdown. If the message recurs, try reseating the Port Adaptor. If reseating also does not work call your technical support representative for assistance.
Error Message %AMDP2_FE-1-UNAVAILABLE: %s MII transceiver not connectedExplanation 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-UNAVAILABLE: %s, Init failed, CSR%d=0x%04xExplanation The software failed to initialize/restart an Ethernet/Fast Ethernet interface.
Recommended Action Clear the interface. If the message recurs, call your technical support representative for assistance.
Error Message %AMDP2_FE-1-UNAVAILABLE: %s, Memory error, CSR%d=0x%04xExplanation 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 the message recurs, call your technical support representative for assistance.
Error Message %AMDP2_FE-1-UNAVAILABLE: 2FE PA not supported on NPE100, shutting down bayExplanation 2FE PA is not supported on a 7200 with NPE100.
Recommended Action NPE150 or better is needed for 2FE PA.
Error Message %AMDP2_FE-1-UNAVAILABLE: Only found %d interfaces on bay %d, shutting down bayExplanation The software could not identify the interface card.
Recommended Action Power down, reseat the interface card, and reboot. If the message recurs, call your technical support representative for assistance.
AMDP2-FE-2
Error Message %AMDP2_FE-2-UNAVAILABLE: %s hardware does not support ISLExplanation The interface cannot be configured as an ISL trunk.
Recommended Action Check the configuration.
Error Message %AMDP2_FE-2-UNAVAILABLE: Interface %s does not support ISLExplanation The interface cannot be configured as an ISL trunk.
Recommended Action Check the configuration.
AMDP2-FE-3
Error Message %AMDP2_FE-3-UNAVAILABLE: %s packet buffer, pak=0x%xExplanation The software detected an error in descriptor ownership.
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-UNAVAILABLE: %s spurious chip init, CSR%d=0x%04xExplanation An illegal condition indicating initialization done has occurred.
Recommended Action Clear the interface. If this message recurs, call your technical support representative for assistance.
Error Message %AMDP2_FE-3-UNAVAILABLE: %s transmit errorExplanation 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-3-UNAVAILABLE: %s, Spurious chip interrupt, CSR%d=0x%04xExplanation An illegal condition indicating initialization done has occurred.
Recommended Action Clear the interface. If this message recurs, call your technical support representative for assistance.
Error Message %AMDP2_FE-3-UNAVAILABLE: %s, packet buffer, pak=0x%xExplanation The software detected an error in descriptor ownership.
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-UNAVAILABLE: %s, transmit errorExplanation 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-3-UNAVAILABLE: Bad packet with %d particles, pak=0x%xExplanation 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-UNAVAILABLE: Slot %d device ID seen as %#x, expected %#xExplanation The software could not recognize the interface chips.
Recommended Action Power down, reseat the interface card, and reboot. If the message recurs, call your technical support representative for assistance.
AMDP2-FE-4
Error Message %AMDP2_FE-4-UNAVAILABLE: %s transmit problem, CSR0=%#xExplanation The transmitter has been on the channel longer than the timetaken to transmit the largest frame
Recommended Action The system should recover. No action is required.
Error Message %AMDP2_FE-4-UNAVAILABLE: %s, Spurious interrupt error, CSR0=%#xExplanation An illegal condition encountered during initialization.
Recommended Action The system should recover. No action is required.
Error Message %AMDP2_FE-4-UNAVAILABLE: %s, transmit problem, CSR0=%#xExplanation 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.
AMDP2-FE-5
Error Message %AMD79C971_FE-5-UNAVAILABLE: Failed to suspend the amd79c971 chipExplanation Failed to suspend the amd79c971 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 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 %AMDP2_FE-5-UNAVAILABLE: %s cable/transceiver problem?Explanation The cable and/or transceiver is not connected.
Recommended Action Connect the cable and/or transceiver.
Error Message %AMDP2_FE-5-UNAVAILABLE: %s transmit errorExplanation Late collisions occurred on the Ethernet/Fast Ethernet interface.When a collision occurs after the preamble has been transmitted then such a collision is called a LATE collision. The packet will be retransmitted, but this condition could also indicate that another device is failing to detect when the network is in use.
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-UNAVAILABLE: %s, Excessive collisions, 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 %AMDP2_FE-5-UNAVAILABLE: %s, lost carrier. cable/transceiver problem?Explanation The cable and/or transceiver is not connected.
Recommended Action Connect the cable and/or transceiver.
Error Message %AMDP2_FE-5-UNAVAILABLE: %s, transmit errorExplanation 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-UNAVAILABLE: The Internal Ethernet Interface is not configurableExplanation The internal ethernet is for system use only.
Recommended Action No action is required.
AMDP2-FE-6
Error Message %AMDP2_FE-6-UNAVAILABLE: %s TDR=%d, TRC=%dExplanation 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 %AP-1-UNAVAILABLE: Distributed DOS attackExplanation 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.
AP Messages
This section contains Authentication Proxy (AP) messages.
AP-1
Error Message %AP-1-AUTH_PROXY_DDOS_ATTACK: Distributed DOS attackExplanation 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 potential DDOS attack.
Error Message %AP-1-UNAVAILABLE: IP-address %i has exceeded the maximum retry limit AUDITSESSID=%sExplanation 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-UNAVAILABLE: POLICY=%s| POLICYNAME=%s| IP=%i| ERROR=| AUDITSESSID=%sExplanation 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-1-UNAVAILABLE: Possible DOS attack from source IP-address %i| AUDITSESSID=%sExplanation 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.
AP-4
Error Message %AP-4-AUTH_PROXY_NOMEM: Sufficient memory was not available to %sExplanation 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 stateExplanation 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-4-UNAVAILABLE: Exceeded maximum limit (%d) on entires in authentication proxy posture cache in initializing stateExplanation 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-4-UNAVAILABLE: Sufficient memory was not available to %sExplanation 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.
AP-5
Error Message %AP-5-UNAVAILABLE: Event=AAA %s. HOST=%i| POLICY %s=%s.| AUDITSESSID=%sExplanation 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.
AP-6
Error Message %AP-6-POSTURE_DOWNLOAD_ACL: Send AAA request to download (%s) named access control listExplanation 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| AUDITSESSID=%sExplanation 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-UNAVAILABLE: %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-UNAVAILABLE: IP=%i| Interface=%s| AUDITSESSID=%sExplanation 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-UNAVAILABLE: IP=%i| MAC=%u| PROFILE_NAME=%s| EVENT=%s| AUDITSESSID=%sExplanation This message indicates a fallback to authproxy has been initiated/terminated for the given host.
Recommended Action No action required
Error Message %AP-6-UNAVAILABLE: IP=%i| STATE=%s| AUDITSESSID=%sExplanation 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
Error Message %AP-6-UNAVAILABLE: Send AAA request to download (%s) named access control listExplanation 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-UNAVAILABLE: initiator (%i) send %u packets %u bytes; duration time %s| AUDITSESSID=%sExplanation 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-UNAVAILABLE: initiator (%i) start| AUDITSESSID=%sExplanation 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.
APS Messages
This section contains Automatic Protection Switching (APS) messages.
APS-1
Error Message %APS-1-UNAVAILABLE: No Active Port In Group %sExplanation 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.
APA-2
Error Message %APS-2-UNAVAILABLE: %s %dExplanation APS software detected an internal 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 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 %APS-2-UNAVAILABLE: %sExplanation A software error occurred during initialization of the APS subsystem
Recommended Action Check for sufficient processor memory. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %APS-2-UNAVAILABLE: Group %s: Channel Config MismatchExplanation 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-UNAVAILABLE: Group %s: Channel Mismatch - %sExplanation 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-UNAVAILABLE: Group %s: Far End Prot Failure - %sExplanation 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-UNAVAILABLE: Group %s: Mode Mismatch - %sExplanation 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-UNAVAILABLE: Group %s: Prot Switch Byte Failure - %sExplanation 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.
APS-3
Error Message %APS-3-UNAVAILABLE: %s Port Fail On %sExplanation 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.
APS-6
Error Message %APS-6-UNAVAILABLE: Auto-Failover - Group %sExplanation 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-UNAVAILABLE: Disable Auto-Failover On %sExplanation APS has disabled auto-failover for the indicated group
Recommended Action Show aps group.
Error Message %APS-6-UNAVAILABLE: Enable Auto-Failover On %sExplanation This message is posted when APS software enables hardware to perform APS actions for failures detected by the hardware. This is informational only.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %APS-6-UNAVAILABLE: Group %s - %s channel is now ACTIVEExplanation This message is posted when a previously standby channel becomes the active channel. This is informational only.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %APS-6-UNAVAILABLE: Group %s: Mode Mismatch - %sExplanation 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-UNAVAILABLE: Group %s: Remote Request - %sExplanation 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. This is informational only.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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.
ARAP Messages
ARAO-0
Error Message %ARAP-0-UNAVAILABLE: TTY %dExplanation An internal software error occured.
Recommended Action Report this error to your technical support representative.
Error Message %ARAP-0-UNAVAILABLE: TTY %dExplanation 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 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 %ARAP-0-UNAVAILABLE: TTY %d: VS queued errorExplanation 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 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 %ARAP-0-UNAVAILABLE: TTY %d: arg msg bad %xExplanation The router received an invalid packet during ARAP MNP4 connection setup phase.
Recommended Action Check for excessive line noise. Check the ARAP client software configuration for possible problems.
ARAP-2
Error Message %ARAP-2-UNAVAILABLE: TTY %d: Could not malloc logExplanation 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 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.
ARAP-3
Error Message %ARAP-3-UNAVAILABLE: TTY %d: Bad packet type in arap_send_msgExplanation Internal data structures are corrupted.
Recommended Action Check for abnormally high CPU usage.
Error Message %ARAP-3-UNAVAILABLE: TTY %d: arap callback abortedExplanation 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 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 %ARAP-3-UNAVAILABLE: TTY %d: arap expected message timeoutExplanation 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 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 %ARAP-3-UNAVAILABLE: TTY %d: arap input errorExplanation 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 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 %ARAP-3-UNAVAILABLE: TTY %d: unhandled configuration commandExplanation A configuration command was not recognized.
Recommended Action Check the configuration file on the server for any invalid configuration commands.
ARAP-4
Error Message %ARAP-4-UNAVAILABLE: TTY %d: ARAP connection failed: %sExplanation 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-UNAVAILABLE: 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.
ARAP-5
Error Message %ARAP-5-UNAVAILABLE: TTY %d: ARAP invalid packet receivedExplanation A corrupted packet reached the ARA protocol code.
Recommended Action Check for excessive CPU usage or excessive line noise.
Error Message %ARAP-5-UNAVAILABLE: TTY %d: ARAP unexpected initialization packet %sExplanation The startup negotiation between a client and the ARA protocol server fell out of order. If this message is received sporadically, it indicates line noise.
Recommended Action If this message recurs, reinstall the ARA client software.
ARAP-6
Error Message %ARAP-6-UNAVAILABLE: TTY %dExplanation 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-UNAVAILABLE: TTY %dExplanation 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-UNAVAILABLE: TTY %d: ARAP ended for user %s; address %A; %d seconds connectedExplanation This message appears only when ARA protocol logging is configured. The message notes that an ARA protocol user has logged out.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ARAP-6-UNAVAILABLE: TTY %d: ARAP started for user %s; address %d.%dExplanation This message appears only when ARA protocol logging is configured. The message notes that an ARA protocol user has logged in.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ARAP-6-UNAVAILABLE: TTY %d: MNP4 input disconnectExplanation This indicates that the router received disconnect request from the remote Macintosh 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 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 %ARAP-6-UNAVAILABLE: TTY %d: MNP4 timeout errorExplanation 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-UNAVAILABLE: TTY %d: Rcv giant. dropping frameExplanation 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-UNAVAILABLE: TTY %d: Receive getbuffer failure. dropping frameExplanation No buffer exists for an incoming packet.
Recommended Action Examine buffer usage statistics. Possibly more memory is required.
Error Message %ARAP-6-UNAVAILABLE: TTY %d: Received LT in CONNECTION PHASEExplanation 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-UNAVAILABLE: TTY %d: T401 %d baud rate %dExplanation This message indicates that the router received MNP4 connection request. MNP4 acknowledgement timer value is also indicated.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ARAP-6-UNAVAILABLE: TTY %d: exited user %s: %sExplanation 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-UNAVAILABLE: 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
This section contains ARCHIVE_CONFIG messages.
ARCHIVE_CONFIG-4
Error Message %ARCHIVE_CONFIG-4-UNAVAILABLE: 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-4-UNAVAILABLE: 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 Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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.
ARCHIVE_CONFIG-6
Error Message %ARCHIVE_CONFIG-6-UNAVAILABLE: 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 Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ARCHIVE_CONFIG-6-UNAVAILABLE: 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 Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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.
ARCHIVE_DIFF Messages
This section contains ARCHIVE_DIFF messages.
ARCHIVE_DIFF-3
Error Message %ARCHIVE_DIFF-3-UNAVAILABLE: Could not initialize the Config Diff and Rollback subsystemExplanation 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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ARCHIVE_DIFF-3-UNAVAILABLE: Failed to register the special case %s command:%s 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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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.
ARCHIVE_DIFF-5
Error Message %ARCHIVE_DIFF-5-UNAVAILABLE: Backing up current running config to %sExplanation The current running config is saved so that when the timer expires, if no confirmation has been received from user to confirm what they've configured, the system will rollback to the 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-UNAVAILABLE: Failed to acquire configuration lock. Rollback did not start. Schedule to retry in 5 minutesExplanation 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-UNAVAILABLE: Start rolling to: %sExplanation 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-UNAVAILABLE: System will rollback to config %s in one minute. Enter configure confirm if you wish to keep what you've configuredExplanation Rollback will start in one minute. User could enter configure confirm if they wish to keep what they've 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-UNAVAILABLE: User %s on tty %d has been idle for %lu minutes. System will rollback to config %s in oneminute if it continues to be idle. Enter configure confirm if you wish to keep what you've configuredExplanation Rollback will start in one minute. User could enter configure confirm if they wish to keep what they've 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-UNAVAILABLE: User: %s Reset Rollback Confirmed Change timer(idle) to %lu minuteExplanation 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-UNAVAILABLE: User: %s: Confirm the configuration changeExplanation The configuration change is confirmed. The timer for rolling to the previously saved config 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-UNAVAILABLE: User: %s: Reset Rollback Confirmed Change timer(absolute) to %lu minuteExplanation 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-UNAVAILABLE: User: %s: Rollback Confirmed Change is cancelled due to %s failureExplanation Rollback Confirmed Change is normally configured along with other configuration operations, such as config term or config replace. If those operation failed, Rollback Confirmed Change should not be activated.
Recommended Action Remove the error condition and try again later.
Error Message %ARCHIVE_DIFF-5-UNAVAILABLE: User: %s: 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-UNAVAILABLE: User: %s: Scheduled to rollback to config %s if session has been idle for %lu minutesExplanation The system will wait for the user to confirm that they wish to keep what they've 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-UNAVAILABLE: User: %s: Scheduled to rollback to config %s in %lu minutesExplanation The system will wait for the user to confirm that they wish to keep what they've 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.
ARCHIVE_ISSU Messages
This section contains messge related to the In Service Software Upgrade facility.
ARCHIVE_ISSU-2
Error Message %ARCHIVE_ISSU-2-UNAVAILABLE: 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 Show logging and show checkpoint client. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ARCHIVE_ISSU-2-UNAVAILABLE: 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 Show issu capability entries, issu session and show issu negotiated capability. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ARCHIVE_ISSU-2-UNAVAILABLE: 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 Show logging and show checkpoint client. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ARCHIVE_ISSU-2-UNAVAILABLE: 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 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 %ARCHIVE_ISSU-2-UNAVAILABLE: 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 Show issu session and show issu negotiated version. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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.
ARCHIVE_ISSU-3
Error Message %ARCHIVE_ISSU-3-UNAVAILABLE: 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 Show issu session and show issu negotiated version. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ARCHIVE_ISSU-3-UNAVAILABLE: Archive ISSU client 'Message Type %d' is not compatibleExplanation The Archive ISSU client received an incompatible message from the peer device. The message cannot be processed.
Recommended Action Show issu session and show issu negotiated version. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ARCHIVE_ISSU-3-UNAVAILABLE: Archive ISSU client does not have a valid registered session.Explanation The Archive ISSU client does not have a valid registered session.
Recommended Action Show issu capability entries, issu session and show issu negotiated capability. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ARCHIVE_ISSU-3-UNAVAILABLE: 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 Show issu session and show issu negotiated version. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ARCHIVE_ISSU-3-UNAVAILABLE: Archive ISSU client failed to unregister session information. Error: %d (%s)Explanation The Archive ISSU client failed to unregister session information.
Recommended Action Show issu session and show issu negotiated version. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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.
AS5400-0
Error Message %AS5400-0-UNAVAILABLE: 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.
AS5400-1
Error Message %AS5400-1-UNAVAILABLE: DFC %d: Detected PCI %s Error, CSR=0x%xExplanation PCI error is detected on the DFC. This is due to hardware failure. IOS will powerdown this DFC and cleanup the system datastructures 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 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 %AS5400-1-UNAVAILABLE: %sExplanation The specified component should have the latest HW revision. If the hw 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 issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AS5400-1-UNAVAILABLE: Unknown DFC interrupt: DFC slot no %d, interrupt %dExplanation 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 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 %AS5400-1-UNAVAILABLE: Unknown interrupt: interrupt %dExplanation 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 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.
AS5400-3
Error Message %AS5400-3-UNAVAILABLE: NULLExplanation DFC hardware error is detected. IOS will powerdown this DFC and cleanup the system datastructures 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 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.
AS5400-ENVM
Error Message %AS5400_ENVM-1-UNAVAILABLE: A DFC is powered down due to board over-temperature. Slot: %d, Type: %sExplanation 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-UNAVAILABLE: A DFC is powered on due to board temperature cooling down. Slot: %d, Type: %sExplanation 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-UNAVAILABLE: 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-UNAVAILABLE: 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-UNAVAILABLE: 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-UNAVAILABLE: 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-UNAVAILABLE: 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-UNAVAILABLE: 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-UNAVAILABLE: 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-UNAVAILABLE: Environmental monitor is trying to power down a DFC by simulating OIR removal. Slot: %d, Type: %sExplanation 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-UNAVAILABLE: Environmental monitor is trying to power on a DFC by simulating OIR insertion. Slot: %d, Type: %sExplanation 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 Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AS5400_ENVM-1-UNAVAILABLE: 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-1-UNAVAILABLE: 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-UNAVAILABLE: 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.
AS5400-ENVM3
Error Message %AS5400_ENVM-3-UNAVAILABLE: %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-UNAVAILABLE: %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.
Error Message %AS5400_ENVM-3-UNAVAILABLE: 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-UNAVAILABLE: 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 %ASPP-3-UNAVAILABLE: %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.
ASPP-3
Error Message %ASPP-3-UNAVAILABLE: %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.
AT-1
Error Message %AT-1-UNAVAILABLE: Could not allocate memory for %s at line %d in %sExplanation 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 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.
AT-2
Error Message %AT-2-UNAVAILABLE: AppleTalk assertion failed: %sExplanation The software detected an inconsistency. Although this error is serious, the router attempts to continue. AppleTalk processing might be impaired.
Recommended Action Copy the message exactly as it appears, note any AppleTalk problems you experience, and call your technical support representative.
AT-3
Error Message %AT-3-UNAVAILABLE: %s: AURP connection out of sync...terminatingExplanation AURP detected packets that were out of sequence. This might be caused by a lost connection.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AT-3-UNAVAILABLE: %s: AppleTalk interface disabled; conflicts with interface %sExplanation An attempt was made to configure an interface to have the same or a conflicting AppleTalk address or cable range as another interface on the same router.
Recommended Action Verify that you are not specifying an AppleTalk address or cable range used previously on this router, and reconfigure the interface.
Error Message %AT-3-UNAVAILABLE: %s: AppleTalk interface disabled; network incompatible with %#aExplanation The interface was disabled because the configured AppleTalk address or cable range for the interface conflicts with that of another router on the attached network.
Recommended Action Reconfigure the affected routers so that there are no conflicting addresses or cable ranges on the attached network.
Error Message %AT-3-UNAVAILABLE: %s: AppleTalk interface disabled; zone list incompatible with %#aExplanation The zone list of the configured interface is inconsistent with the zone list of other routers.
Recommended Action Reconfigure the zone list on the router so that it does not conflict with that the zoen lists on other routers.
Error Message %AT-3-UNAVAILABLE: %s: AppleTalk interface warning; default zone differs from %#aExplanation During the verification startup process, there was a disagreement between the default zone (the first zone defined after the appletalk cable-range command) and the router that confirmed the configuration. When an AppleTalk end node is first connected to a network, it joins the default zone until it is overridden.
Recommended Action Use the appletalk zone command to correct the configuration so that all routers are advertising the same default zone. Note that several router implementations are known to mismanage the default zone.
Error Message %AT-3-UNAVAILABLE: %s: AppleTalk interface warning; zone multicast %e differs from our multicast %eExplanation A computed multicast address disagrees with that provided by another AppleTalk router. The other AppleTalk router might be misconfigured or faulty.
Recommended Action Correct the problem at the other router.
Error Message %AT-3-UNAVAILABLE: %s: AppleTalk node down; no addresses availableExplanation No free node could be found on the interface.
Recommended Action If your AppleTalk network has less than 250 nodes, issue the debug appletalk errors command and then call your technical support representative. If your AppleTalk network has more than 250 nodes, split it into smaller networks by creating new segments and moving some nodes into the new segments.
Error Message %AT-3-UNAVAILABLE: %s: AppleTalk node warning; discovery mode disabledExplanation 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/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AT-3-UNAVAILABLE: %s: AppleTalk packet error; no source address availableExplanation The router could not generate an AppleTalk packet because no valid AppleTalk source address was available to identify this router in the packet.
Recommended Action Configure an interface to have an address or cable range. Use the show appletalk command to verify that the interface is operational.
Error Message %AT-3-UNAVAILABLE: %s: client tried to connect, but no virtual network is declaredExplanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %AT-3-UNAVAILABLE: %s: client tried to open socket, but failedExplanation open socket failed;Possible out of memory situation
Error Message %AT-3-UNAVAILABLE: AppleTalk error: %sExplanation An internal error occurred. Specifically, a programming assertion in the AppleTalk networking code was violated.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AT-3-UNAVAILABLE: AppleTalk not runningExplanation You tried to show or change the AppleTalk configuration when AppleTalk routing was not turned on.
Recommended Action Issue the appletalk routing command before issuing any other AppleTalk configuration or display command.
Error Message %AT-3-UNAVAILABLE: Cannot delete %s route %d by clearing; remove it by reconfiguringExplanation You attempted to remove a route from the routing table by issuing the clear appletalk route command. The command failed because the route was on a directly connected interface, that is, it was created when you configured the router.
Recommended Action Remove the route by reconfiguring the directly connected interface with which it is associated.
Error Message %AT-3-UNAVAILABLE: Could not compute best path for network %#AExplanation A path to the specified network could not be found.
Recommended Action Use the show appletalk route command to verify that a path to the specified network exists. If it does, copy the error message exactly as it appears, and report it along with the output of the show appletalk route command to your technical support representative.
Error Message %AT-3-UNAVAILABLE: Invalid NBPtest command %sExplanation An unrecognized command was specified in the Name Binding Protocol (NBP) test facility.
Recommended Action Enter a valid command.
Error Message %AT-3-UNAVAILABLE: Loop detected on domain %d [%s]Explanation The domain router detected a routing loop. Routing loops are not allowed. The domain router runs a background loop detection process. The domain router starts this process when it receives a new zone list from a domain that is identical to the list in the main routing table and whose network range length matches that in this list. The loop detection process sends several AppleTalk NBP loopback packets. When one of these packets is received on an interface that does not belong to the original domain, the domain router first shuts off all the domains involved in the loop, and then shuts off all the interfaces in these domains. The loop detection does not catch all types of loops. It is your responsibility to make sure that no loop exists.
Recommended Action Disable the cause of the routing loop. Then use the clear appletalk command to restart the interfaces involved.
Error Message %AT-3-UNAVAILABLE: No route to destination %aExplanation The router could not deliver a packet to a destination because it did not know where to send it.
Recommended Action Use the show appletalk route command to verify that a path to the destination exists. If it does, copy the error message exactly as it appears, and report it with the output of the show appletalk route command to your technical support representative.
Error Message %AT-3-UNAVAILABLE: No such neighbor, %#aExplanation You specified a nonexistent neighbor address in a show appletalk neighbor or clear appletalk neighbor.
Recommended Action Specify a valid neighbor address, that is, one that appears in the output of the show appletalk neighbor command.
Error Message %AT-3-UNAVAILABLE: Remap range overflow for %s domain %dExplanation The remap range overflowed. If a network (range) cannot fit inside the remapping range, the network or cable range being advertised by a neighboring router is not accepted. When an overflow occurs, all interfaces in the domain are disabled.
Recommended Action Use the appletalk domain remap-range command to increase the remapping range. Then restart the interfaces.
AT-4
Error Message %AT-4-UNAVAILABLE: %s: AppleTalk node down; conflicts with active internetExplanation The configuration specified for the interface conflicts with the active AppleTalk internetwork. For example, a cable range might be configured that overlaps an existing route but does not match the entry exactly.
Recommended Action Use the appletalk cable-range command to reconfigure the interface so that there are no conflicts with the existing AppleTalk rnetwork, or take any other actions necessary to resolve the conflict. AppleTalk will periodically attempt to restart the interface.
Error Message %AT-4-UNAVAILABLE: %s: MacIP inoperable IP interface, %iExplanation If the appletalk event-logging command is configured, this message appears on the console when a MacIP server can no longer operate due to a change in the condition of the IP interface it serves. This condition can occur if IP routing is shut down on the interface, or the IP address of the interface is changed so that the MacIP server's IP address is no longer valid on the same cable. The AppleTalk zone served by the MacIP server replaces the zone specified in the appletalk zone command. The IP address configured on the MacIP server replaces the IP address configured by the ip address command.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AT-4-UNAVAILABLE: %s: MacIP inoperable configuration, %iExplanation If the appletalk event-logging command is configured, this message appears on the console when a MacIP server cannot begin or recover operations because of an invalid IP address configuration. This condition only occurs when the configured MacIP server's IP address is not valid on the same cable of any operable IP interface. The AppleTalk zone served by the MacIP server replaces the zone specified in the appletalk zone command. The IP address configured on the MacIP server replaces the IP address configured by the ip address command. When this error occurs, the MacIP configuration is considered invalid and is deleted.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AT-4-UNAVAILABLE: AURP path %#A rejected; conflict detectedExplanation The router detected a conflicting cable range. A router is configured with a cable range that overlaps with an existing range but does not match the entry exactly.
Recommended Action Use the show appletalk command to identify the overlapped cable range, and then reconfigure the misconfigured router.
AT-5
Error Message %AT-5-UNAVAILABLE: %s: AppleTalk interface restarting; interface clearedExplanation A clear interface command was issued on an interface that is currently routing AppleTalk.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AT-5-UNAVAILABLE: %s: AppleTalk interface restarting; node address taken by %eExplanation Another AppleTalk node on a common network interface claimed the same AppleTalk address that this router was using. This error indicates a serious, unexpected problem. If it recurs, a physical network problem in which the nodes cannot communicate with each other might exist.
Recommended Action The interface on this router restarts AppleTalk processing on the common network interface to resolve the address conflict.Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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.
Recommended Action
Error Message %AT-5-UNAVAILABLE: %s: AppleTalk interface restarting; protocol restartedExplanation The hardware interface was reset because of a configuration change. After the reset, AppleTalk automatically reinitialized the 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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AT-5-UNAVAILABLE: %s: AppleTalk internet compatibility mode required by %#aExplanation A neighboring router supports only extended AppleTalk networks with a cable range of 1 and with one assigned zone, for example, 25-25.
Recommended Action Upgrade the routers that support only the original AppleTalk specification. In the meantime, observe the compatibility rules for AppleTalk Phase 1 and Phase 2 routers.
Error Message %AT-5-UNAVAILABLE: %s: AppleTalk neighbor down; lost contact with %#aExplanation A peer router is unreachable.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AT-5-UNAVAILABLE: %s: AppleTalk neighbor ignored; %#a is misconfiguredExplanation A neighboring router's AppleTalk configuration does not agree with this router's AppleTalk configuration. This condition can result from a mismatch between the neighbor's network range and this router's network range.
Recommended Action Modify either this router's or the neighboring router's configuration so that the network ranges agree.
Error Message %AT-5-UNAVAILABLE: %s: AppleTalk node down; line protocol downExplanation An AppleTalk hardware interface was disabled because of a bad serial line, a configuration command, or a bad interface.
Recommended Action If the interface was not intentionally disabled, this message indicates a hardware problem. In this case, repair or replace the applicable hardware.
Error Message %AT-5-UNAVAILABLE: %s: AppleTalk node down; line protocol not supportedExplanation An encapsulation method on the specified interface does not support AppleTalk.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AT-5-UNAVAILABLE: %s: AppleTalk node warning; address %A already in useExplanation The initial hint address was in use. A search will be made for a valid address.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AT-5-UNAVAILABLE: %s: AppleTalk node warning; address %A is invalidExplanation The hint address specified for the interface was not valid for the current configuration.
Recommended Action The hint address is ignored and a random valid hint address is automatically computed. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AT-5-UNAVAILABLE: %s: AppleTalk route cache disabled; firmware is obsoleteExplanation The firmware on the MCI controller card does not support AppleTalk fast switching.
Recommended Action No corrective action is required. Normal AppleTalk operation continues, but the fast switching cache is disabled for the interface associated with the MCI card. If this message is unexpected, verify that the MCI firmware for the interface specified in the error message is at level 1.7 or higher.
Error Message %AT-5-UNAVAILABLE: %s: RTMP path to %#A via %#a now in %s state (metric %d, %d hops)Explanation The state of a path changed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AT-5-UNAVAILABLE: AppleTalk FDDI neighbor %#a using obsolete FDDI addressingExplanation Another AppleTalk router on the FDDI ring is running a release of the router software earlier than 9.0(2). Routers running these early software releases use an encapsulation for AppleTalk on FDDI rings that is not compatible with the Apple FDDITalk implementation.
Recommended Action Upgrade the routers running the software releases that use the pre-FDDITalk encapsulation for AppleTalk on FDDI rings.
Error Message %AT-5-UNAVAILABLE: AppleTalk neighbor incompatibility; %#A has multiple zonesExplanation Although this router has neighbors that require your internetwork to observe compatibility rules, AppleTalk has learned of a route with multiple zone names defined. This condition can cause node inconsistencies on your AppleTalk network.
Recommended Action Upgrade the routers that support only the original AppleTalk specification. In the meantime, observe the compatibility rules for AppleTalk Phase 1 and Phase 2 routers.
Error Message %AT-5-UNAVAILABLE: AppleTalk neighbor incompatibility; %#A has wide cable rangeExplanation Although this router has neighbors that require your internetwork to observe compatibility rules, AppleTalk has learned of a route that has a cable range greater than 1. This condition can cause node inconsistencies on your AppleTalk network.
Recommended Action Upgrade the routers that support only the original AppleTalk specification. In the meantime, observe the compatibility rules for AppleTalk Phase 1 and Phase 2 routers.
Error Message %AT-5-UNAVAILABLE: No such route %dExplanation You specified a nonexistent route in a show appletalk route or clear appletalk route command.
Recommended Action Specify a valid route, that is, one that appears in the output of the show appletalk route command.
Error Message %AT-5-UNAVAILABLE: Route to %#A is now using path of type %s on %s via %#aExplanation The path to a network changed because either the old path went down or the new path was better.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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.
AT-6
Error Message %AT-6-UNAVAILABLE: %s: AppleTalk %s path to %#A down; reported bad by %#aExplanation A router went down somewhere on the AppleTalk network. The indicated peer notified this router of the change.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AT-6-UNAVAILABLE: %s: AppleTalk %s path to %#A via %#a has been deletedExplanation A path on the AppleTalk network aged out.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AT-6-UNAVAILABLE: %s: AppleTalk %s path to network %#A added; via %#a (metric %d)Explanation A new AppleTalk path has been learned. The message indicates the source of the path, its distance in hops, its metric, and the type of path.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AT-6-UNAVAILABLE: %s: AppleTalk interface enabled; no neighbors foundExplanation No other AppleTalk routers were found on the network attached to the 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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AT-6-UNAVAILABLE: %s: AppleTalk interface enabled; verified by %#aExplanation The AppleTalk configuration was verified by consulting the indicated router.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AT-6-UNAVAILABLE: %s: AppleTalk interface initializing; acquiring %sExplanation The interface is determining the correct configuration. This message is displayed when discovery mode is enabled and no other router 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 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 %AT-6-UNAVAILABLE: %s: AppleTalk interface restarting; line protocol came upExplanation An AppleTalk interface that was previously shut down was restarted.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AT-6-UNAVAILABLE: %s: AppleTalk neighbor added; %#a is operationalExplanation The router discovered a new AppleTalk router on the network.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AT-6-UNAVAILABLE: %s: AppleTalk neighbor up; %#a has restartedExplanation A neighboring router to which this router previously lost connectivity reappeared on the network.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AT-6-UNAVAILABLE: %s: AppleTalk network added; %#A via %#a (%d hop %s)Explanation A new AppleTalk route was learned. The message indicates the source of the route and its distance in hops.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AT-6-UNAVAILABLE: %s: AppleTalk network down; %#A reported bad by %#aExplanation A router went down somewhere on the AppleTalk network. The indicated peer notified this router of the change.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AT-6-UNAVAILABLE: %s: AppleTalk network down; interface to %#A disabledExplanation A connected route is being advertised as down (also known as otify neighbor) because the configured interface is no longer operational.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AT-6-UNAVAILABLE: %s: AppleTalk network up; %#A via %#a (%d hop %s)Explanation A routing update was received for a previously suspect route.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AT-6-UNAVAILABLE: %s: AppleTalk node %a misconfigured; reply has been broadcastExplanation An AppleTalk node sent a GetNet Info request to this router specifying an invalid network number for the source of the GetNet Info request. This situation occurs when an AppleTalk end node is moved to another network and is therefore misconfigured for the current network.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AT-6-UNAVAILABLE: %s: AppleTalk node up; using address %AExplanation No hint address or a bad hint address was specified. This message indicates which AppleTalk address will be used for the 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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AT-6-UNAVAILABLE: %s: MacIP server operational, %iExplanation If the appletalk event-logging command is configured, this message appears on the console when a MacIP server is fully initialized and is ready to accept client requests. The AppleTalk zone served by the MacIP server replaces the zone specified in the appletalk zone command. The IP address configured on the MacIP server replaces the IP address configured by the ip address command.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AT-6-UNAVAILABLE: %s: MacIP server shutting down, %iExplanation If the appletalk event-logging command is configured, this message appears on the console when a MacIP server is no longer operational for any reason. MacIP servers shut down in response to MacIP configuration changes or errors, or a change in the condition or configuration of an AppleTalk or IP interface for which the MacIP server is providing service. The AppleTalk zone served by the MacIP server replaces the zone specified in the appletalk zone command. The IP address configured on the MacIP server replaces the IP address configured by the ip address command.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AT-6-UNAVAILABLE: AppleTalk network deleted; %#A removed from routing tableExplanation A route on the AppleTalk network aged out.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AT-6-UNAVAILABLE: AppleTalk proxy defined; zone %s using network %#AExplanation This message reports the zone name and network number that are being advertised to support the appletalk nbp-proxy command.
Recommended Action When proxy service is initiated, this message is generated each time the appletalk nbp-proxy command is issued. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AT-6-UNAVAILABLE: AppleTalk proxy deleted; zone %s freed network %#AExplanation A previously configured Name Binding Protocol (NBP) proxy was deleted. The router can no longer convert NBP requests to a format understood by routers that support only the original AppleTalk specification.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AT-6-UNAVAILABLE: AppleTalk zone added; zone %*s definedExplanation A new AppleTalk zone was created.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AT-6-UNAVAILABLE: AppleTalk zone deleted; zone %s releasedExplanation The router removed an unused zone from the zone 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 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 %AT-6-UNAVAILABLE: NBP registration of %s at [%s] pendingExplanation A name registration call is being performed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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 %AT-6-UNAVAILABLE: Neighbor entry for %#a deletedExplanation The clear appletalk neighbor command displays this command when it completes successfully.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AT-6-UNAVAILABLE: Route to %#A has gone badExplanation The system did not detect a route within the required timeout period. Therefore, the route is marked as bad. A network might have become unreachable for some reason, perhaps because of a broken connection. This message does not necessarily indicate an error condition.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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.
AT-7
Error Message %AT-7-UNAVAILABLE: AppleTalk bug: %sExplanation The software detected an unexpected condition. The router takes corrective action and continues.
Recommended Action Copy the message exactly as it appears, note any AppleTalk problems you experience, and call your technical support representative.
Error Message %AT-7-UNAVAILABLE: AppleTalk debug: %sExplanation This message is generated by a debug command and provides additional information about an AppleTalk condition.
Recommended Action Copy the message exactly as it appears, note any AppleTalk problems you experience, and call your technical support representative.
ATM Messages
This section contains ATM messages.
ATM-1
Error Message %ATM-1-ISSU_NOMEMORY: msgtxt_nomemoryExplanation 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 %ATM-1-UNAVAILABLE: Unit %d, not enough interface memoryExplanation The specified ATM interface hardware has run out of interface 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. 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 %ATM-1-UNAVAILABLE: msgtxt_nomemoryExplanation 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.
ATM-3
Error Message %ATMPA-3-CMDFAIL: %s Command Failed at %s - line %d, arg %dExplanation The port adapter failed to process a command. A possible reason for this condition is an OIR operation was performed of a line card or port adapter and RP was in the process of executing commands. If this message is seen during any other time, it indicates a software problem.
Recommended Action If this message appeared while an OIR operation was being performed of a port adapter or line card, and if the slot or bay number in the message text corresponds to the removed hardware, this message indicates normal system operation 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 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 %ATM-3-UNAVAILABLE: ATM ISSU: send message failed, rc = %dExplanation 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 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 %ATM-3-UNAVAILABLE: %s %s:%dExplanation Internal Error (see message) occurs during ILMI Primary to Secondary Sync
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ATM-3-UNAVAILABLE: %s [%08X=%s] %s:%dExplanation Internal Error (see message) occurs during ILMI Primary to Secondary Sync
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ATM-3-UNAVAILABLE: ATM failed to create VC on Interface %sExplanation Either the configuration contains invalid traffic shaping parameters or the software ran out of rate queues.
Recommended Action Check the configuration for errors.
Error Message %ATM-3-UNAVAILABLE: ATM failed to create VC on Interface %sExplanation The ATM subsystem ran out of internal resources necessary to create a new virtual circuit. This may indicate 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 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 %ATM-3-UNAVAILABLE: ATM failed to create VC(VCD=%d, VPI=%d, VCI=%d) on Interface %s, (Cause of the failure: %s)Explanation This message can occur for the following unrelated reasons. Each reason is accompanied by a recommended action. The virtual circuit descriptor (VCD) exceeded the maximum available memory. - Use a smaller VCD number. Address Resolution Protocol (ARP) is allowed only on AAL5-SNAP virtual circuits. - Change the encapsulation to AAL5SNAP. The virtual path identifier-virtual channel identifier (VPI-VCI) pair or the VCD is already in use. - Try using a different VPI-VCI or VCD number. Only one virtual channel connection (VCC) is allowed on a point-to-point interface. - Try using a different subinterface. AAL3/4-SMDS virtual circuit must be the only virtual circuit on an interface. - Turn off AAL3/4. AAL3/4-SMDS MID exceeds the maximum. - Try a smaller Multiplex ID (MID) value. Switched Multimegabit Data Service (SMDS) is not enabled. - Enable SMDS. The driver failed to accept the virtual circuit. - Try initiating the virtual circuit again.
Recommended Action If none of the previous actions fix the problem, copy the error message exactly as it appears and report it to your Cisco technical support representative.
Error Message %ATM-3-UNAVAILABLE: ATM failed to modify VC(VCD=%d, VPI=%d, VCI=%d) on Interface %s, (Cause of the failure: %s)Explanation ATM failed to modify QoS params on a VC
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ATM-3-UNAVAILABLE: ATM failed to remove VC(VCD=%d, VPI=%d, VCI=%d) on Interface %s, (Cause of the failure: %s)Explanation This message can occur for the following reason. When the PVC configuration parameters are changed it is recreated, during recreation if the removal of PVC from the PA fails, this message is generated. If after generation of this error message if the PVC still remains in INACTIVE state give shut/no shut on the interface.
Recommended Action If none of the previous actions fix the problem, copy the error message exactly as it appears and report it to your Cisco technical support representative.
Error Message %ATM-3-UNAVAILABLE: Interface %s: Total %s allocation %u%s exceeded maximum %s of %u%s.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 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 %ATM-3-UNAVAILABLE: MLPoATM not configured properly on Link %s Bundle %s :%sExplanation The configuration of MLPPP-over-ATM (MLPoATM) on the ATM PVC is either incorrect or incomplete.
Recommended Action Ensure that the queueing strategy on the ATM interface is per VC queueing and queueing algorithm is FIFO.To verify the configuration, use the show inteface atm and show running-config virtual-template commands.
ATM-4
Error Message %ATM-4-UNAVAILABLE: %s: failed, rc=%sExplanation 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 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 %ATM-4-UNAVAILABLE: atm-issu-compat: returned FALSEExplanation 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 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 %ATM-4-UNAVAILABLE: %s [%08X=%s] %s:%dExplanation Recoverable Internal Error (see message) occurs during ILMI Primary to Secondary Sync
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ATM-4-UNAVAILABLE: (%d/%d/%d:%d): %s. Please verify peer UNI versionExplanation The ATM peer equipment appears to be running an old version of ATM UNI. Communication with it is not possible.
Recommended Action The peer equipment needs to be upgraded in order to communicate with this system.
Error Message %ATM-4-UNAVAILABLE: Call from: ATM NSAP - %s has mismatched PDU size - forward size is %d - backward size is %d, int %s PDU size %s %sExplanation The calling or called party has a maximum transmission unit (MTU) size configured that is different from the MTU size on the current interface.
Recommended Action Either change the configured MTU size on the current interface to that of the caller's or called party's interface, or change the caller's or called party's interface to match the current interface.
Error Message %ATM-4-UNAVAILABLE: ILMI(%s): Restarting ATM signalling and ILMI. Keepalive failure detected.Explanation Adjacent peer device is not responding to ILMI Keepalive polling.
Recommended Action Check the connection of the ATM interface and the status of the adjacent peer device. Correct them if neccessary. Wait and check if ILMI Keepalive comes up again. If the problem persists, copy this warning message exactly as it appears, and report it to your technical support representative.
Error Message %ATM-4-UNAVAILABLE: ILMI(%s): Restarting ATM signalling and ILMI. Peer Configuration change detected.Explanation Configuration of adjacent peer device has been changed.
Recommended Action Wait for the interface to restart itself.
Error Message %ATM-4-UNAVAILABLE: VPI/VCI range parameters are dis-joint on %sExplanation MinSvccVci MaxVci, after negotiation with the peer through ILMI.
Recommended Action Disable auto-cinfiguration on both sides and change the port configuration appropriately so that SVCCs can be setup.
Error Message %ATM-4-UNAVAILABLE: clearing stuck VCD %d from map on %sExplanation A SVC map entry has a stuck VCD attached to it, which has been previously cleared in the driver.
Recommended Action No action required as the stuck VCD condition is detected and cleared.
ATM-5
Error Message %ATM-5-UNAVAILABLE: %sExplanation Informational Message for ILMI Redundency Support
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ATM-5-UNAVAILABLE: Address registration on %s is enabled.Explanation The command just entered enables atm address registration.
Recommended Action No action required.
Error Message %ATM-5-UNAVAILABLE: Changing VC %d/%d VC-state to %sExplanation The ATM VC is either created, removed, activated, or deactivated.
Recommended Action No action required if status change is intended, otherwise the cause for status change may deserve to be noticed. shut/no shut CLI command deactivates/activates VC.
Error Message %ATM-5-UNAVAILABLE: ILMI(%s): %sExplanation Informational Message for ILMI Redundency Support
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ATM-5-UNAVAILABLE: New access filter setting will be applied to registration of new addresses on %s.Explanation The command just entered sets up new ilmi access filter for address registration. It only affects new addresses to be registered. The addresses already registered will not be affected.
Recommended Action Shut/no shut on this interface to restart address registration if need to remove addresses already registered but not permitted by the new access filter.
Error Message %ATM-5-UNAVAILABLE: New global default access filter setting will be applied to registration of new addresses on interfaces using global default access filter.Explanation The command just entered sets up new global default access filter for addres registration. It only affects new addresses to be registered on interfaces using the global default. The addresses already registered will not be affected.
Recommended Action Shut/no shut on desired interfaces to restart address registration if need to remove addresses already registered but not permitted by the new global default access filter.
Error Message %ATM-5-UNAVAILABLE: Restarting ATM signalling and ILMI on %s.Explanation The command just entered causes ATM Soft Restart.
Recommended Action Stand by and let ATM Signalling and ILMI to restart.
ATM-6
Error Message %ATM-6-UNAVAILABLE: ILMI(%s): Auto configuration already disabled.Explanation Atm auto-configuration has been enabled already. 'no atm auto-configuration' command just entered is ignored.
Recommended Action No action required.
Error Message %ATM-6-UNAVAILABLE: ILMI(%s): Auto-configuration already enabled.Explanation Atm auto-configuration has been enabled already. 'atm auto-configuration' command just entered is ignored.
Recommended Action No action required.
Error Message %ATM-6-UNAVAILABLE: ILMI(%s): Auto-configuration cannot be enabled.The interface has VC configuration which cannot be supported with Auto-configuration enabledExplanation Auto-configuration cannot be enabled if there are some conflicting configuration on an interface. Like if there are VCs with vpi 255, auto-configuration cannot be done till these VCs are removed, as with auto-configuration enabled vpi 255 cannot be supported.
Recommended Action Undo the conflicting configuration on the interface for this command to succeed.
Error Message %ATM-6-UNAVAILABLE: ILMI(%s): Auto-configuration is disabled, current interface parameters will be used at next interface restart.Explanation The command just entered causes auto-configuration to be disabled, the most recently entered interface parameters will be used at next interface restart.
Recommended Action Be aware of what parameteres have been configured.
Error Message %ATM-6-UNAVAILABLE: ILMI(%s): This command does not apply to internal terminating port.Explanation Internal terminating does not need to be configured with this command. The command just entered is ignored.
Recommended Action No action required.
ATMCES-1
Error Message %ATMCES-1-UNAVAILABLE: Invalid Port Adapter Hardware Type Type=%dExplanation Port Adapter ID was not correct.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ATMCES-1-UNAVAILABLE: The 1575 device could not be initialized on bay %d, shutting down bayExplanation The Port Adapter has failed its initialization.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ATMCES-1-UNAVAILABLE: The 1575 device failed to create VC %d, file:%s line:%dExplanation The Port Adapter encounters errors in setting up VC
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ATMCES-1-UNAVAILABLE: The 1575 device not totally clean in removing VC %d, file:%s line:%dExplanation The Port Adapter encounters errors in shut vc. May affect future VC creation
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ATMCES-1-UNAVAILABLE: The Slave device could not be initialized on bay %d, shutting down bayExplanation The Port Adapter has failed its initialization.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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.
ATMCES-3
Error Message %ATMCES-3-UNAVAILABLE: Couldn't configure the Altera, DIO not resetExplanation The Port Adapter has failed its initialization.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ATMCES-3-UNAVAILABLE: Couldn't get bridge configuration: %sExplanation Bridge 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/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ATMCES-3-UNAVAILABLE: Couldn't initialize the Altera, DIO not setExplanation The Port Adapter has failed its initialization.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ATMCES-3-UNAVAILABLE: Device reported %08xExplanation PCI devide ID was not correct.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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.
ATMCORE-2
Error Message %ATMCORE-2-UNAVAILABLE: %sExplanation The ATM core subsystem 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 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.
ATMCORE-3
Error Message %ATMCORE-3-UNAVAILABLE: %sExplanation The ATM core subsystem 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 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.
ATMCORE-4
Error Message %ATMCORE-4-UNAVAILABLE: %sExplanation The ATM core subsystem 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 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 %ATMCORE-4-UNAVAILABLE: %sExplanation This warning is generated by the ATM core subsystem to the user. This could arise because the user request may not be granted due to some existing configuration on the device. This message serves as an alert to the user. This 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 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 %ATMCORE-4-UNAVAILABLE: Configuration Error: %sExplanation This message indicates a configuration error. The message will display more specific information about the problem location.
Recommended Action Change the configuration to correct the error.
ATMCORE-RED-2
Error Message %ATMCORE_RED-2-UNAVAILABLE: %sExplanation The ATM core redundancy subsystem 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 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 %ATMCORE_RED-3-UNAVAILABLE: %sExplanation The ATM core redundancy subsystem 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 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.
ATMCORE-RED-3
Error Message %ATMCORE_RED-3-UNAVAILABLE: %sExplanation The ATM core redundancy subsystem 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 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.
ATMCORE-RED-4
Error Message %ATMCORE_RED-4-UNAVAILABLE: %sExplanation The ATM core redundancy subsystem 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 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.
ATMLC-1
Error Message %ATMLC-1-UNAVAILABLE: The ATM line card in slot %d failed to initialize (cause %s)Explanation The ATM linecard has failed its initialization as indicated in the message. The problems can be one of the following: 1) memory allocation failure for control data, 2) framer, ATM SAR devices, or line card FPGA access failure, 3) uncorrectable multi-bit ECC errors in line card memory, 4) PCI bus timeout, 5) failure of downloading ATM SAR firmware to the SAR devices, or 6) ATM SAR device (reassembler or segmenter) does not boot up or does not respond to configuration commands.
Recommended Action Consult your line card installation and configuration guide and make sure the line card is properly installed and configured. If the line card is properly installed, perform an online insertion and removal (OIR) on the line card, either via a physical removal and insertion, or via the hw-module slot [slot#][stop|start] command. If the OIR does not work, try to reload the system if possible to bring the system offline. If the problem persists, the message indicates an unrecoverable hardware failure. Copy the error message exactly as it appears on the console or in the system log and call your Cisco 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 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.
ATMLC-3
Error Message %ATMLC-3-UNAVAILABLE: The ATM line card in slot %d encountered a hardware failure: %sExplanation The ATM line card has encountered a hardware failure and should be deactivated. The problem can be any one of the following: 1) memory allocation failure for control data, 2) framer, ATM SAR devices, or line card FPGA access failure, 3) uncorrectable multi-bit ECC errors in line card memory, 4) PCI bus timeout, 5) ATM SAR device (reassembler or segmenter) does not respond to configuration commands, or 6) unrecoverable data corruption/parity error.
Recommended Action The message indicates a hardware failure. The line card may have been deactivated by the system. Perform a line card online insertion and removal(OIR) to confirm that the problem persists. If the problem persists, copy the error message exactly as it appears on the console or in the system log. Enter show c7300, show diag slot-number, show c7300 errorlog slot, show interface atm, and show controller atm and provide the gathered information 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 nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
ATMLC-4
Error Message %ATMLC-4-UNAVAILABLE: Interface ATM%d/%d, received SONET/SDH alarm: %sExplanation The ATM framer interface received SONET/SDH alarm(s) as indicated in the message.
Recommended Action SONET/SDH alarms may occur when the line card is initializing and negotiating clocking with the peer. In this situation, the alarms will be cleared and the error message is used only to provide information. If the message continues to appear after the line card is initialized and the connection is set up, use the show controller atm command to check the framer alarms. If the alarms from show controller atm do not disappear, ensure that the optical fiber cable is not broken and is properly inserted and that the far end of the peer is not malfunctioning. If the error message persists, the message should reflect the alarm conditions of the SONET/SDH-based network. In this scenario, the alarm was sent by a far-end entity and the source and purpose of the alarm should be investigated by a network administrator if not already known. If you think the message itself is being received in error, copy the message exactly as it appears on the console or in the system log and capture the output of the show c7300 and the show controller atm commands. Call your Cisco technical support representative and provide the representative with the gathered information. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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.
ATMLC-6
Error Message %ATMLC-6-UNAVAILABLE: Interface ATM%d/%d, changed clock source to %sExplanation The clock source of the ATM interface changed to either line clock or internal clock as indicated in the message. If the ATM interface is configured for line clocking and receives SONET/SDH alarms including one of loss of signal (LOS), loss of frame (LOF), and line alarm indication (Line AIS), the interface will first change to internal clock before changing back to line clock when the alarms are cleared. If the ATM interface is configured for internal clocking, the SONET/SDH alarms will not cause any clocking change. This message shows the run-time clock source changes on an ATM interface while the show controller atm command always shows the user-configured clock source.
Recommended Action No action is required.
ATMCO31
Error Message %ATMOC3-1-UNAVAILABLE: %s error.Explanation A non-recoverable 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.
Error Message %ATMOC3-1-UNAVAILABLE: %s traffic type not allowed in a PVP.Explanation This traffic type cannot be configured in a PVP.
Recommended Action Either change the traffic type of this VC or remove it from the PVP.
Error Message %ATMOC3-1-UNAVAILABLE: %s, packet(size %d) too big.Explanation A packet greater than the 256 bytes received on this interface.
Recommended Action The system should recover. No action is required. If the problem reccurs, it indicates an error that might be related to data traffic patterns. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %ATMOC3-1-UNAVAILABLE: Failed to activate F4 %s VC. PVP %d.Explanation The required control VC was not established.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %ATMOC3-1-UNAVAILABLE: The ATM Network Module in slot %d is incompatible with the PCMCIA controller in the router.Explanation The PCMCIA controller is down level.
Recommended Action Copy the error message exactly as it appears, and contact your technical support representative for upgrade information.
Error Message %ATMOC3-1-UNAVAILABLE: The Network Module in slot %d did not initialize.Explanation The Network Module has failed its initialization.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ATMOC3-1-UNAVAILABLE: The Network Module in slot %d failed to initialize (cause %s).Explanation The Network Module has failed its initialization.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ATMOC3-1-UNAVAILABLE: The network module hardware reports an invalid %s device id of %#x.Explanation The ATMOC3 network module hardware may be 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 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.
ATMPS-0
Error Message %ATMPA-0-UNAVAILABLE: misc_cntl_reg %#x. Resetting the OC12 PA...Explanation The ASIC that interfaces the SAR engines to the VIP4 packet switching and routing processor has encountered an error that has caused it to fail. As its main function, this ASIC supports the SARs by implementing the cell and packet buffering scheme that is expected on the Port 1 interface, and by managing the commands and indications sequences on the Port 2 interface.
Recommended Action The OC-12 reboots itself. May need to do clear int
ATMPS-1
Error Message %ATMPA-1-UNAVAILABLE: %s control memory badExplanation A memory test failed within the PCI control memory. This probably indicates a memory chip has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the 'sh tech-support' command to gather data that may help to determine the nature of error. Call your Cisco technical support representative and provide representative with the gathered information.
Error Message %ATMPA-1-UNAVAILABLE: %s failed to send report %d at %s - line %dExplanation The port adaptor failed to send a report from vip.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %ATMPA-1-UNAVAILABLE: %s vc %d received a giant packet size %d - %08x %08x %08x %08x %08x %08xExplanation The port adaptor received a giant packet.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %ATMPA-1-UNAVAILABLE: VIP2-40 and below only supports one OC-3 ATM PA. The other PA bay needs to be emptied in order for the ATM PA to function.Explanation The bandwidth requirements of the installed port adapters exceed the processor's rated capability.
Recommended Action Either remove one of the port adapters or upgrade the VIP.
Error Message %ATMPA-1-UNAVAILABLE: register %08x write value 0x%02x but read 0x%02xExplanation The port adaptor failed to write a register.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
ATMPS-2
Error Message %ATMPA-2-UNAVAILABLE: Slot %d device is invalid (ID %#x)Explanation The ATM Deluxe PCI driver found an incorrect PCI device ID during initialization. This could mean that a hardware failure caused an actual failure to read the ID, or that the software needs to be upgraded to support hardware that did not exist yet at the time the software was written.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ATMPA-2-UNAVAILABLE: ti1570_vc_setup failed. (vp_count %d max_vp %d).Explanation Attempt has been made to create more Virtual Paths than the maximum configured Virtual Paths.
Recommended Action ATM-Light supports 6 Virtual Paths by default. The default value can be changed using interface config command atm vc-per-vp xxx. Decrease the vc-per-vp value to increase the number of Virtual Paths that can be created.
ATMPS-3
Error Message %ATMPA-3-UNAVAILABLE: %s Command Failed at %s - line %d, arg %dExplanation The port adapter failed to process a command. A possible reason for this condition is an OIR operation was performed of a line card or port adapter and RP was in the process of executing commands. If this message is seen during any other time, it indicates a software 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 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 %ATMPA-3-UNAVAILABLE: %s Have to close all VCs beforemodifying the VP tunnel %dExplanation The VP Tunnel has open VCs assosiated with it.
Recommended Action Remove all the VCs associated with the VP tunnel before modifying the VP.
Error Message %ATMPA-3-UNAVAILABLE: %s Runs out of VP space for vpi %dExplanation Unable to get a driver VP control block, neither from inuse_q nor from virgin_q. So, we cannot Setup a new Vp nor a new VC.
Recommended Action To increase the number of VPs configurable on PA-A3-OC12 we can use 'atm vc-per-vp' interface configuration command. So the recommended action here is to set the appropriate value in 'atm vc-per-vp'.
Error Message %ATMPA-3-UNAVAILABLE: %s SAR doing %s error: %sExplanation ATM driver SAR operation error.
Recommended Action Enable 'debug atm events' & gather the log. Issue the 'sh tech-support' command to gather data that may help to determine the nature of error. Call your Cisco technical support representative and provide representative with the gathered information.
Error Message %ATMPA-3-UNAVAILABLE: %s SAR firmware checksum error (expected 0x%04x, obtained 0x%04x)Explanation CM622 ATM SAR firmware checksum errors.
Recommended Action Enable 'debug atm events' & gather the log. Issue the 'sh tech-support' command to gather data that may help to determine the nature of error. Call your Cisco technical support representative and provide representative with the gathered information.
Error Message %ATMPA-3-UNAVAILABLE: %s Tx Indication FIFO full.Explanation TX Indication FIFO full. From TX FPGA.
Recommended Action None. The OC-12 reboots itself.
Error Message %ATMPA-3-UNAVAILABLE: %s bad vcd %d packet - %08x %08x %08x %08x %08x %08xExplanation The port adaptor received packet on a non-existent vc.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %ATMPA-3-UNAVAILABLE: %s tx cmd ack error (%#x), vcd %d.Explanation Error while processing the Tx Ack cmd.
Recommended Action Enable 'debug atm events' & gather the log. Issue the 'sh tech-support' command to gather data that may help to determine the nature of error. Call your Cisco technical support representative and provide representative with the gathered information.
Error Message %ATMPA-3-UNAVAILABLE: %s: Platform Setup_vc failed for %d/%d, vcd %dExplanation RSP Platform Setup VC failed.
Recommended Action Turn on debug atm error on platform console and see why.
Error Message %ATMPA-3-UNAVAILABLE: %s: Platform Setup_vp failed for vpi %dExplanation RSP Platform Setup VP failed.
Recommended Action Turn on debug atm error on platform console and see why.
Error Message %ATMPA-3-UNAVAILABLE: %s: SAR%d Chip Crashdump:Explanation The SAR chip crashed and interface is being reset.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the 'sh cont atm xxx' command to gather data that may help to determine the nature of error. Call your Cisco technical support representative and provide representative with the gathered information.
Error Message %ATMPA-3-UNAVAILABLE: %s: bad rx particle 0x%08x flags 0x%08x index %dExplanation The PA host driver dectected a duplicate rx host buffer returned
Recommended Action Copy the error message exactly as it appears, and report it to your echnical support representative.
Error Message %ATMPA-3-UNAVAILABLE: %s: bad tx packet on vcd %d size %dExplanation The PA host driver dectected a bad tx host buffer with size 0
Recommended Action Enable 'debug atm events' & gather the log. Issue the 'sh tech-support' command to gather data that may help to determine the nature of error. Call your Cisco technical support representative and provide representative with the gathered information.
Error Message %ATMPA-3-UNAVAILABLE: %s: receive freeze %dExplanation This message indicates excessive traffic congestion on the ATM interface may have resulted in cell loss. The PCI-ATM interface's cell buffers were full when a cell arrived on the interface, resulting in a receive freeze 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 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 %ATMPA-3-UNAVAILABLE: %s: transmit freeze %dExplanation This message indicates the PCI-ATM interface had to stop the transmitter while waiting for data.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ATMPA-3-UNAVAILABLE: ATMPA (bay %d), Init Failed at %s - line %dExplanation The port adaptor failed to complete hardware initialization.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %ATMPA-3-UNAVAILABLE: In file %s - line %dExplanation Cannot create the CM622 Process Agent process, which is a temp process to download firmware.
Recommended Action Enable 'debug atm events' & gather the log. Issue the 'sh tech-support' command to gather data that may help to determine the nature of error. Call your Cisco technical support representative and provide representative with the gathered information.
Error Message %ATMPA-3-UNAVAILABLE: Interface %s: %s command not supportedExplanation An attempt was made to configure a rate queue on an ATM Lite port adapter that does not support rate queues.
Recommended Action Check the configuration and try again, avoiding unsupported features.
Error Message %ATMPA-3-UNAVAILABLE: Only %#x bytes of memory available for %sExplanation The port adaptor needs more PCI memory. The installed amount is less than required by the drivers for packet buffers.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ATMPA-3-UNAVAILABLE: RX DMA entry %#x not going inactiveExplanation A receive DMA channel failed to deactivate during shutdown of a virtual circuit. This failure could originate in 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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ATMPA-3-UNAVAILABLE: Slot %d device is not TI1570 (ID %#x)Explanation The driver found a device type other than what it expected in the specified PCI slot. If the device is a TI1570 then a hardware failure may have occurred.
Recommended Action Power down the system, re-seat the interface card, and reboot. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ATMPA-3-UNAVAILABLE: Slot %d device is not a valid PCI device vendor ID used onOC-12 PA (ID %#x)Explanation The driver found a device type other than what it expected in the specified PCI slot.
Recommended Action Power down the system, re-seat the interface card, and reboot. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ATMPA-3-UNAVAILABLE: TI1570 unit %s: PCI parity error (0x%08x)Explanation A parity error occurred on the PCI bus. This probably indicates an existing or developing 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 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 %ATMPA-3-UNAVAILABLE: TX CMD %d failed for vcd %d.Explanation Failure while processing a Batman tx SAR cmd or unable to performa cmd ack.
Recommended Action Enable 'debug atm events' & gather the log. Issue the 'sh tech-support' command to gather data that may help to determine the nature of error. Call your Cisco technical support representative and provide representative with the gathered information.
Error Message %ATMPA-3-UNAVAILABLE: TX DMA not flushedExplanation A transmit DMA channel failed to flush its buffers during shutdown of an ATM interface. This failure could originate in 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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ATMPA-3-UNAVAILABLE: found %d interfaces on bay %d (device ID %08X)Explanation The software could not identify the interface card.
Recommended Action Power down the system, reseat the interface card, and reboot. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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.
ATMPS-4
Error Message %ATMPA-4-UNAVAILABLE: %s: Shaped peak rate adjusted to %dExplanation CM622 only allows shaped rate up to half of line rate.
Recommended Action You can either specify a value within range oruse the adjusted value
Error Message %ATMPA-4-UNAVAILABLE: RX SAR cmd %s error: %s (indication=0x%08x 0x%08x 0x%08x)Explanation ATM driver RX SAR indication errors.
Recommended Action Enable 'debug atm events' & gather the log. Issue the 'sh tech-support' command to gather data that may help to determine the nature of error. Call your Cisco technical support representative and provide representative with the gathered information.
ATMPS-5
Error Message %ATMPA-5-UNAVAILABLE: ti1570_vc_setup failed. (vci %d of the lastvpi %d exceeds (vc-per-vp - 3)).Explanation The TI1570 chip reserves 3 RX DMA channels for OAM cells.As a result, the last 3 VCIs of the last VPI block cannotbe used for regular traffic.
Recommended Action Avoid try different vci/vpi combinations.
ATMPS-7
Error Message %ATMPA-7-UNAVAILABLE: %s 0x%08x, %s 0x%08x, %s 0x%08xExplanation SAR APU Registers dump
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %ATMPA-7-UNAVAILABLE: %s 0x%08x, %s 0x%08x, %s 0x%08x, %s 0x%08xExplanation SAR CW4010 Registers dump
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %ATMPA-7-UNAVAILABLE: 00 0x%08x, 01 0x%08x, 02 0x%08x, 03 0x%08xExplanation SAR Misc. dump
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %ATMPA-7-UNAVAILABLE: 04 0x%08x, 05 0x%08x, 06 0x%08x, 07 0x%08xExplanation SAR Misc. dump
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %ATMPA-7-UNAVAILABLE: 08 0x%08x, 09 0x%08x, 10 0x%08x, 11 0x%08xExplanation SAR Misc. dump
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %ATMPA-7-UNAVAILABLE: 12 0x%08x, 13 0x%08x, 14 0x%08x, 15 0x%08xExplanation SAR Misc. dump
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
ATMSIG-3
Error Message %ATMSIG-3-UNAVAILABLE: %sExplanation An internal software error or unexpected condition occured during PNNI (Connection/Path) Trace related processing
Recommended Action Show atm pnni trace information.Also gather information about where/how trace was initiated, and for what type of VC.Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ATMSIG-3-UNAVAILABLE: 1st halfLeg failed, %sExplanation 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 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 %ATMSIG-3-UNAVAILABLE: 2nd halfLeg failed, %sExplanation 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 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 %ATMSIG-3-UNAVAILABLE: ATMSIG(%s %d,%d - %04d/%02d) SVC wavl del failed:svc 0x%xExplanation A software error occurred during closure of an SVC. Other error messages appearing immediately prior to this one may be related.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ATMSIG-3-UNAVAILABLE: ATMSIG(%s %d,%d - %04d/%02d) SVC wavl ins failed:svc 0x%xExplanation A software error occurred during creation of an SVC. Other error messages appearing immediately prior to this one may be related.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ATMSIG-3-UNAVAILABLE: ATMSIG(%s %d,%d - %04d/%02d) avl prty del failed:svc 0x%x party 0x%xExplanation A software error occurred during removal of a party from a point-to-multipoint call. Other error messages appearing immediately prior to this one may be related.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ATMSIG-3-UNAVAILABLE: ATMSIG(%s %d,%d - %04d/%02d) avl prty ins failed:svc 0x%x party 0x%xExplanation A software error occurred during addition of a party to a point-to-multipoint call. Other error messages appearing immediately prior to this one may be related.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ATMSIG-3-UNAVAILABLE: ATMSIG(%s)Explanation A software error occurred during addition of a member to a closed user group. Other error messages appearing immediately prior to this one may be related.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ATMSIG-3-UNAVAILABLE: ATMSIG(%s)Explanation A software error occurred during removal of a member from a closed user group. Other error messages appearing immediately prior to this one may be related.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ATMSIG-3-UNAVAILABLE: Assertion failed: %sExplanation 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 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 %ATMSIG-3-UNAVAILABLE: Cannot find a Callref value to allocate: %sExplanation This indicates an internal software error, probably including memory exhaustion.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ATMSIG-3-UNAVAILABLE: Duplicate LISTEN by %s for existing NSAP %s owned by %sExplanation An application attempted to either LISTEN on an NSAP owned by another application or to LISTEN for the same NSAP twice
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ATMSIG-3-UNAVAILABLE: Invalid msg from routing/pnni : %sExplanation This message indicates an error in the PNNI routing subsystem. It could be caused by an internal software error or by bad control information received from peer equipment. The message will contain additional information that can help locate the cause. Any message with 'NULL' probably indicates a problem with this system, others probably point at the peer equipment.
Recommended Action Check this system and the peer equipment for any obvious errors. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ATMSIG-3-UNAVAILABLE: Signalling control block initialization failure, %sExplanation An internal software or resource 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.
Error Message %ATMSIG-3-UNAVAILABLE: Xconnect failed, %sExplanation An internal software error occurred during installation of an SVC cross-connect.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ATMSIG-3-UNAVAILABLE: halfLeg removal failed, %sExplanation An internal software error occurred. This message should only be displayed when verbose debugging is enabled for an SVC.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ATMSIG-3-UNAVAILABLE: no SVC, %sExplanation 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 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 %ATMSIG-3-UNAVAILABLE: process_enqueue failed, %sExplanation An internal software error occurred while handling a user 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.
ATMSIG-4
Error Message %ATMSIG-4-UNAVAILABLE: Configuration Error: %s %sExplanation This message indicates a configuration error in the ATM Signaling subsystem. The message will display more specific information about the problem location.
Recommended Action Change the configuration to correct the error.
ATMSPA-2
Error Message %ATMSPA-2-UNAVAILABLE: %s - Init Failed return code: %uExplanation The SPA failed to complete hardware initialization. One of the devices in the SPA failed to initialize successfully. Information about the failed device is specified in the message text on the console or in the system log.
Recommended Action Please power down and reseat the indicated SPA card. If the condition persists, copy the error message exactly as it appears. Next research and attempt to resolve the issue using the SPA hardware troubleshooting documentation as well as the tools and utilities provided at http://www.cisco.com/public/support/tac/tools.shtml. If you still require assistance, open a case with the Technical Assistance Center via the Internet at 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).
ATMSPA-3
Error Message %ATMSPA-3-UNAVAILABLE: %s %s %s: %dExplanation Traffic shaping parameters could not be configured because the number of unique shaping parameters that are configured on the PVCs or PVPs in this specified ATM SPA is over the maximum limit. The maximum number of unique shaping parameters that can be configured on the PVCs or PVPs is 4096.
Recommended Action Ensure that the total number of unique shaping parameters that are configured on both PVCs and PVPs does not exceed the maximum limit of 4096.
Error Message %ATMSPA-3-UNAVAILABLE: %s Error 0x%x %sExplanation A datapath protocol violation or sequence error 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 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 %ATMSPA-3-UNAVAILABLE: %s Error 0x%x %sExplanation The specified error 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 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 %ATMSPA-3-UNAVAILABLE: %s Error 0x%x %sExplanation The specified hardware error 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 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 %ATMSPA-3-UNAVAILABLE: %s Error 0x%x %sExplanation The specified software error 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 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 %ATMSPA-3-UNAVAILABLE: %s: VC queue configuration failed due to un-initialized queue table(global identifier %d)Explanation Software configuration of a VC queue failed due to un-initialized queue table.
Recommended Action Attempt to perform a soft OIR operation by entering the command that is described in the shared port adapter software configuration guide. If the condition persists, copy the error message exactly as it appears, and report it to your technical support representative. Also supply a 'show tech-support' at that time.
Error Message %ATMSPA-3-UNAVAILABLE: Cannot perform the requested FPD update operation because %s in subslot %u/%u has incompatible HW version %u.%u with FPD image version %d.%d for FPD ID %d. Only image version greater than %u.%u can be used in the update operation of %s with HW version greater than %u.%u.Explanation The version of the FPD image from the FPD image bundle or package is not compatible with the HW version of the target card
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ATMSPA-3-UNAVAILABLE: occurred on %s. Resetting SPAExplanation The SPA has been reset due to a critical error in one of its devices. The error could either be a single occurrence of an event or multiple occurrences within a period of time. The message text on the console or in the system log provides more information on the specific nature of the error.
Recommended Action If the SPA is reset more than once, copy the error message exactly as it appears. Next research and attempt to resolve the issue using the SPA hardware troubleshooting documentation as well as the tools and utilities provided at http://www.cisco.com/public/support/tac/tools.shtml. If you still require assistance, open a case with the Technical Assistance Center via the Internet at 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).
ATMSPA-4
Error Message %ATMSPA-4-UNAVAILABLE: %s: VC setup command received on the LC for an existing VC (VCD %d)Explanation A command to set up a VC has been received for a VC that has already been set up. The VC has already been configured by a previous setup VC command from the RP. A duplicate setup command may indicate that the RP did not receive a response from the LC for the previous setup command.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ATMSPA-4-UNAVAILABLE: %s: VC tear down command received on the LC for a non-existing VC (VCD %d)Explanation The VC does not exist on the LC. Most likely, it has been torn down by a previous teardown command from RP. A duplicate teardown command may indicate that the RP did not receive a response from the LC for the previous teardown command.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ATMSPA-4-UNAVAILABLE: %s: VP setup command received on the LC for an existing VP (VPI %d)Explanation A command to set up a VP has been received for a VP that has already been set up. The VP has already been configured by a previous setup VP command from the RP. A duplicate setup command may indicate that the RP did not receive a response from the LC for the previous setup command.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ATMSPA-4-UNAVAILABLE: %s: VP tear down command received on the LC for a non-existing VP (VPI %d)Explanation The VP does not exist on the LC. Most likely, it has been torn down by a previous teardown command from RP. A duplicate teardown command may indicate that the RP did not receive a response from the LC for the previous teardown command.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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.
ATMSCOP-3
Error Message %ATMSSCOP-3-UNAVAILABLE: INIT SSCOP - Intf : %s, Event : %s, State : %s.Explanation A software error occurred in the ATM SSCOP 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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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.
ATMSCOP-4
Error Message %ATMSSCOP-4-UNAVAILABLE: (%s): %s. Please verify peer UNI versionExplanation The ATM peer equipment appears to be running an old version of ATM UNI. Communication with it is not possible.
Recommended Action The ATM peer equipment may need attention. Please verify its UNI version is at least 3.1, and upgrade if necessary.
ATMSSCOP-5
Error Message %ATMSSCOP-5-UNAVAILABLE: - Intf : %s, Event : %s, State : %s.Explanation This message indicates a routine step of the ATM SSCOP initialization sequence.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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.
ATMPA Messages
Error Message %ATMPA-1-INVALIDCONFIG: VIP2-40 and below only supports one OC-3 ATM PA. The other PA bay needs to be emptied in order for the ATM PA to function.Explanation The bandwidth requirements of the installed port adapters exceed the processor's rated capability.
Recommended Action Either remove one of the port adapters or upgrade the VIP.
Error Message %ATOM_TRANS-3-INIT_FAIL: Failed to start AToM ManagerExplanation Failed to start and initialize AToM Manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit 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/launch.do, or contact your Cisco technical support.
ATMSPA Messages
This section contains ATM Shared Port Adapter (ATMSPA) messages.
ATMSPA-2
Error Message %ATMSPA-2-INITFAIL: [chars] - Init Failed return code: [int]Explanation The shared port adapter (SPA) failed to complete hardware initialization. One of the devices in the SPA failed to initialize successfully. Information about the failed device is specified in the message text on the console or in the system log.
Recommended Action Power down and reseat the indicated SPA card. If the condition persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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.
ATMSPA-3
Error Message %ATMSPA-3-DATA_ERROR: [chars] Error [hex] [chars]Explanation A data path protocol violation or sequence error has been detected. The message text on the console or in the system log provides more information on the specific cause of the 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 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 %ATMSPA-3-FATAL_ERROR: occurred on [chars]. Resetting SPAExplanation The shared port adapter (SPA) has been reset because of a critical error in one of its devices. The error could either be a single occurrence of an event or multiple occurrences within a period of time. The message text on the console or in the system log provides more information on the specific cause of the error.
Recommended Action If the SPA is reset more than once, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ATMSPA-3-FPD_VER_DEPENDENCY_NOTE: Cannot perform the requested FPD update operation because [chars] in subslot [int]/[int] has incompatible HW version [int].[int] with FPD image version [dec].[dec] for FPD ID [dec]. Only image version greater than [int].[int] can be used in the update operation of [chars] with HW version greater than [int].[int].Explanation The version of the field-programmable device (FPD) image from the FPD image bundle or package is not compatible with the hardware (HW) version of the target card.
Recommended Action If the SPA is reset more than once, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ATMSPA-3-GEN_ERROR: [chars] Error [hex] [chars]Explanation The error that is specified in the message 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 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 %ATMSPA-3-HW_ERROR: [chars] Error [hex] [chars]Explanation A hardware error has been detected. The message text on the console or in the system log provides more specific informationabout the 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 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 %ATMSPA-3-QOS_ALLOC_FAILED: [chars] [chars] [chars]: [dec]Explanation Traffic-shaping parameters could not be configured because the number of unique shaping parameters that are configured on the PVCs or PVPs in this specified ATM SPA is over the maximum limit. The maximum number of unique shaping parameters that can be configured on the PVCs or PVPs is 4096.
Recommended Action Ensure that the total number of unique shaping parameters that are configured on both PVCs and PVPs does not exceed the maximum limit of 4096.
Error Message %ATMSPA-3-SW_ERROR: [chars] Error [hex] [chars]Explanation A software error has been detected. The message text on the console or in the system log provides more specific information about the 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 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 %ATMSPA-3-VCQ_ERROR: [chars]: VC queue configuration failed due to un-initialized queue table(global identifier [dec])Explanation The software configuration of a virtual circuit (VC) queue failed because of an uninitialized queue table.
Recommended Action Attempt to perform a soft OIR operation by entering the command that is described in the shared port adapter software configuration guide. If the condition persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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.
ATMSPA-4
Error Message %ATMSPA-4-VCSETUP: [chars]: VC setup command received on the LC for an existing VC (VCD [dec])Explanation A command to set up a virtual circuit (VC) has been received for a VC that has already been set up and configured by a previous setup VC command from the RP. A duplicate setup command may indicate that the RP did not receive a response from the line card for the previous setup command.
Recommended Action No action is required.
Error Message %ATMSPA-4-VCTEARDOWN: [chars]: VC tear down command received on the LC for a non-existing VC (VCD [dec])Explanation The virtual circuit (VC) does not exist on the line card. The VC probably has been torn down by a previous teardown command from the route processor (RP). A duplicate teardown command may indicate that the RP did not receive a response from the line card for the previous teardown command.
Recommended Action No action is required.
Error Message %ATMSPA-4-VPSETUP: [chars]: VP setup command received on the LC for an existing VP (VPI [dec])Explanation A command to set up a virtual path (VP) has been received for a VP that has already been set up. The VP has already been configured by a previous setup VP command from the route processor (RP). A duplicate setup command may indicate that the RP did not receive a response from the line card for the previous setup command.
Recommended Action No action is required.
Error Message %ATMSPA-4-VPTEARDOWN: [chars]: VP tear down command received on the LC for a non-existing VP (VPI [dec])Explanation The virtual path (VP) does not exist on the line card. The VP probably has been torn down by a previous teardown command from the route processor (RP). A duplicate teardown command may indicate that the RP did not receive a response from the line card for the previous teardown command.
Recommended Action No action is required.
ATOM_NP_CLIENT Messages
This section contains Any Transport Over MPLS (AToM) NP client messages.
ATOM_NP_CLIENT-3
Error Message %ATOM_NP_CLIENT-3-INFO: %sExplanation ATOM NP Client failed to initialize properly which will result in improper operation of Any Transport Over MPLS feature
Recommended Action Try to reload the IOS image on the affected card or platform. If the error persists, record the output from the show log and show tech commands. Provide this information to your technical support representative.
Error Message %ATOM_NP_CLIENT-3-NOMEM: %sExplanation ATOM NP Client failed to initialize properly which will result in improper operation of Any Transport Over MPLS feature
Recommended Action This error may indicate that more memory must be installed on the affected card or platform in order to service all the features and related entities enabled via the configuration. Try to reload the IOS image on the affected card or platform. If the error persists, record the output from the show log and show tech commands. Provide this information to your technical support representative.
Error Message %ATOM_NP_CLIENT-3-UNAVAILABLE: %sExplanation ATOM NP Client failed to initialize properly which will result in improper operation of Any Transport Over MPLS feature
Recommended Action This error may indicate that more memory must be installed on the affected card or platform in order to service all the features and related entities enabled via the configuration. Try to reload the IOS image on the affected card or platform. If the error persists, record the output from the show log and show tech commands. Provide this information to your technical support representative.
ATOM_NP_CLIENT-4
Error Message %ATOM_NP_CLIENT-4-WARN: %s %d %sExplanation AToM Entry could not be added because: 1. Entry passed is invalid.
Recommended Action Try to reload the IOS image on the affected card or platform. If the error persists, record the output from the show log and show tech commands. Provide this information to your technical support representative.
ATOM_SEG Messages
This section contains Any Transport Over MPLS (AToM) Segment Handler messages.
ATOM_SEG-3
Error Message %ATOM_SEG-3-UNAVAILABLE: Error freeing %sExplanation ATOM Segment Handler 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 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 %ATOM_SEG-3-UNAVAILABLE: Illegal label %d update %sExplanation AToM Segment Handler 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 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 %ATOM_SEG-3-UNAVAILABLE: Unsupported update %sExplanation AToM Segment Handler 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 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.
ATOM_TRANS Messages
This section contains Any Transport Over MPLS (AToM) Layer 2 messages.
ATOM_TRANS-3
Error Message %ATOM_TRANS-3-UNAVAILABLE: %sExplanation An action attempted by the layer 2 transport over MPLS implementation encountered an unexpected 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 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 %ATOM_TRANS-3-UNAVAILABLE: Failed to allocate local label for peer:%i, vcid:%uExplanation Failed to allocate local label for specified AToM VC.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ATOM_TRANS-3-UNAVAILABLE: Failed to start AToM ManagerExplanation Failed to start and initialize AToM 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 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.
ATOM_TRANS-4
Error Message %ATOM_TRANS-4-UNAVAILABLE: %sExplanation AToM pseudowire uses undesirable 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 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.
ATOM_TRANS-5
Error Message %ATOM_TRANS-5-UNAVAILABLE: %sExplanation Disposition disabled for specified AToM VC.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ATOM_TRANS-5-UNAVAILABLE: %sExplanation Disposition enabled for specified AToM VC.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ATOM_TRANS-5-UNAVAILABLE: %sExplanation Imposition disabled specified AToM VC.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %ATOM_TRANS-5-UNAVAILABLE: %sExplanation Imposition enabled for specified AToM VC.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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.
AUDIT Messages
This section contains audit messages.
AUDIT-1
Error Message %AUDIT-1-UNAVAILABLE: Audit File Roll-over: %dExplanation Audit Circular File Rolled Over.
Recommended Action Increase Audit filesize.
AUDIT-3
Error Message %AUDIT-3-UNAVAILABLE: Cannot create Audit file.Explanation File system error while creating the audit file.
Recommended Action Check DISK filesystems on the router.
Error Message %AUDIT-3-UNAVAILABLE: Cannot create Audit process.Explanation Insufficient internal resource available to create process.
Recommended Action Check available memory on router.
Error Message %AUDIT-3-UNAVAILABLE: Cannot resize Audit file.Explanation File system error while resizing the audit file.
Recommended Action Check DISK filesystems on the router.
Error Message %AUDIT-3-UNAVAILABLE: Cannot write to Audit file.Explanation File system error while writing to the audit file.
Recommended Action Check DISK filesystems on the router.
AUDIT-5
Error Message %AUDIT-5-UNAVAILABLE: Auditing disabledExplanation Audit was disabled on the router.
Recommended Action Check if Audit was disabled by someone authorized to do so
Error Message %AUDIT-5-UNAVAILABLE: Auditing enabledExplanation Audit was enabled on the router.
Recommended Action Audit logs can be verified, if changes are valid
Error Message %AUDIT-5-UNAVAILABLE: Filesystem changed. Hash: %sExplanation FLASH/DISK Filesystems on the router changed.
Recommended Action Check if it is a valid change.
Error Message %AUDIT-5-UNAVAILABLE: Hardware changed. Hash: %sExplanation Hardware on the router changed.
Recommended Action Check if it is a valid change.
Error Message %AUDIT-5-UNAVAILABLE: Running Configuration changed. Hash: %sExplanation Running Config on the router changed.
Recommended Action Check if it is a valid change in config.
Error Message %AUDIT-5-UNAVAILABLE: Running Version changed. Hash: %sExplanation Running Version on the router changed.
Recommended Action Check if it is a valid change.
Error Message %AUDIT-5-UNAVAILABLE: Startup Configuration changed. Hash: %sExplanation Startup config on the router changed.
Recommended Action Check if it is a valid change.
AUTHMGR Messages
This section contains Auth Manager messages.
AUTHMGR-5
Error Message %AUTHMGR-5-UNAVAILABLE: Authorization failed for client (%s) on Interface %sExplanation Authorization was unsuccessful
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AUTHMGR-5-UNAVAILABLE: Authorization succeeded for client (%s) on Interface %sExplanation Authorization was successful
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AUTHMGR-5-UNAVAILABLE: Interface %s unauthorizedExplanation Port has become unuthorized
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AUTHMGR-5-UNAVAILABLE: Security violation on the interface %s, new MAC address (%e) is seen.Explanation A host on the specified interface is attempting to gain access into the network or is trying to authenticate in a host mode that does not support the number of hosts attached. This is treated as a security violation and the port has been error-disabled.
Recommended Action Ensure that the port is configured to support the number of hosts attached. Enter the shutdown command followed by no shutdown command to restart the port.
Error Message %AUTHMGR-5-UNAVAILABLE: Starting '%s' for client (%s) on Interface %sExplanation Starting an authentication method
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AUTHMGR-5-UNAVAILABLE: VLAN %d assigned to Interface %sExplanation VLAN assignment
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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.
AUTHMGR-7
Error Message %AUTHMGR-7-UNAVAILABLE: Authentication result '%s' from '%s' for client (%s) on Interface %sExplanation Authentication result received from a method
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AUTHMGR-7-UNAVAILABLE: Exhausted all authentication methods for client (%s) on Interface %sExplanation All available authentication methods have been tried
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AUTHMGR-7-UNAVAILABLE: Failing over from '%s' for client (%s) on Interface %sExplanation Failing over from the current authentication method
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AUTHMGR-7-RESULT: Authentication result '[chars]' from '[chars]' for client ([chars]) on Interface [chars]Explanation The authentication result and method are displayed for the client.
Recommended Action No action is required.
AUTH_MGR_ISSU Messages
This section contains Auth Manager in-service software upgrade (ISSU) messages.
AUTH_MGR_ISSU-2
Error Message %AUTH_MGR_ISSU-2-UNAVAILABLE: Auth Mgr ISSU client encountered unexpected client nego_done. Error: %d (%s)Explanation An ISSU-compliant client transitions through a series of internal states. The Auth Mgr 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 Show issu session and show issu negotiated capability. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AUTH_MGR_ISSU-2-UNAVAILABLE: Auth Mgr ISSU client failed to get buffer for message. Error: %d (%s)Explanation The Auth Mgr 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 Show logging and show checkpoint client. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AUTH_MGR_ISSU-2-UNAVAILABLE: Auth Mgr ISSU client failed to register session information. Error: %d (%s)Explanation The Auth Mgr 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 Show issu capability entries, issu session and show issu negotiated capability. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AUTH_MGR_ISSU-2-UNAVAILABLE: Auth Mgr ISSU client failed to send negotiation message. Error: %d (%s)Explanation The Auth Mgr 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 Show logging and show checkpoint client. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AUTH_MGR_ISSU-2-UNAVAILABLE: Auth Mgr ISSU client initialization failed to %s. Error: %d (%s)Explanation The Auth Mgr 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 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.
AUTH_MGR_ISSU-3
Error Message %AUTH_MGR_ISSU-3-UNAVAILABLE: 'Feature Id %d, Tag %d' is not supported by Auth Mgr ISSU client at peerExplanation The Auth Mgr ISSU client at the peer supervisor is not compatible for this message type. The Auth Mgr client will be marked as incompatible with the peer.
Recommended Action Show issu session and show issu negotiated version. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AUTH_MGR_ISSU-3-UNAVAILABLE: Auth Mgr ISSU client %s transform failed for 'Feature Id %d, Tag %d'. Error: %d (%s)Explanation The Auth Mgr 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 Auth Mgr state between the active device and the standby device is not identical.
Recommended Action Show issu session and show issu negotiated version. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AUTH_MGR_ISSU-3-UNAVAILABLE: Auth Mgr ISSU client 'Feature Id %d, Tag %d' is not compatibleExplanation The Auth Mgr ISSU client received an incompatible message from the peer device. The message cannot be processed.
Recommended Action Show issu session and show issu negotiated version. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AUTH_MGR_ISSU-3-UNAVAILABLE: Auth Mgr ISSU client capability exchange result incompatible.Explanation The Auth Mgr ISSU client capability exchange have negotiated as incompatible with the peer.
Recommended Action Show issu negotiated capability.Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AUTH_MGR_ISSU-3-UNAVAILABLE: Auth Mgr ISSU client capability list is empty.Explanation The Auth Mgr ISSU client capability exchange list size is invalid.
Recommended Action Show issu message group and issu session, and show issu negotiated version. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AUTH_MGR_ISSU-3-UNAVAILABLE: Auth Mgr ISSU client does not have a valid registered session.Explanation The Auth Mgr ISSU client does not have a valid registered session.
Recommended Action Show issu capability entries, issu session and show issu negotiated capability. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AUTH_MGR_ISSU-3-UNAVAILABLE: Auth Mgr ISSU client failed to get the MTU for Feature Id %d, Tag %d. Error: %d (%s)Explanation The Auth Mgr ISSU client failed to calculate the MTU for the specified message. The Auth Mgr ISSU client is not able to send the message to the standby device.
Recommended Action Show issu session and show issu negotiated version. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AUTH_MGR_ISSU-3-UNAVAILABLE: Auth Mgr ISSU client failed to unregister session information. Error: %d (%s)Explanation The Auth Mgr ISSU client failed to unregister session information.
Recommended Action Show issu session and show issu negotiated capability. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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.
AUTORP Messages
This section contains Protocol Independent Multicast (PIM) version 2 Auto-Rendezvous Point (AUTORP) messages.
AUTORP-2
Error Message %AUTORP-2-UNAVAILABLE: Error initializing the Auto-RP radix treeExplanation 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 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.
AUTORP-4
Error Message %AUTORP-4-UNAVAILABLE: AutoRP %s packet is received on interface %s with Source address=%i, Destination address=%i, TTL=%u, IP length=%u Datagram size/UDP length=%uExplanation The AutoRP packet was received with wrong packet length. The packet has been dropped as it may be a malformed packet.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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 %AUTORP-4-UNAVAILABLE: AutoRP %s packet, group %i with mask %i removed because of multicast boundary for %i with mask %iExplanation The multicast boundary has a longer network mask than the AutoRP encoded group.
Recommended Action Use postive permit clauses in the AutoRP Access Control List
Error Message %AUTORP-4-UNAVAILABLE: Error expiring semi-static RP-mapping entry (%i/%d, RP:%i)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 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 %AUTORP-4-UNAVAILABLE: Error inserting a new entry into the RP-mapping radix treeExplanation 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