Table Of Contents
C6K_SAMI_CENTRALIZED_CONFIG Messages
C10KMULTILINK_FRAGSIZE_BELOW_MIN_WARNING Messages
C10K_MULTILINK_USER_WARNING Messages
C10K_QUEUE_CFG_GENERAL Messages
C10K_QUEUE_CFG_WARNING Messages
System Messages
This section lists messages alphabetically by facility and mnemonic.
AAA Messages
The following are authentication, authorization and accounting messages.
Error Message%AAA-3-ACCT_IOMEM_LOW : AAA ACCT process suspended : low I/O memory
Explanation AAA ACCT process has been suspended due to insufficient IO memory.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%AAA-3-ACCT_LOW_MEM_TRASH : AAA unable to handle accounting requests due to insufficient processor memory and could be trashing the queued accounting records
Explanation Dropping the accounting request as there is not enough processor memory. All queued accounting requests will be trashed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%AAA-3-ACCT_LOW_MEM_UID_FAIL : AAA unable to create UID for incoming calls due to insufficient processor memory
Explanation Stop creating the AAA UID, due to LOW processor memory.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%AAA-6-ACCTSESSIDWRAP : Accounting-Session-ID [dec] exceeded max value allowed
Explanation Accounting-Session-ID value exceeded max value allowed. Now it is wrapping.
Recommended Action This is informational only, not an error. No action is required.
Error Message%AAA-3-ATTRFORMATERR : Attribute with unknown format [dec]
Explanation An attribute was found with an invalid format.
Recommended Action Attribute with unknown format in definition. Enable AAA debug and try to replicate the steps to get the message. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.Error Message%AAA-3-AUTH_LOW_IOMEM : RADIUS process is unable to handle the requests due to insufficient I/O memory
Explanation RADIUS process unable to handle request due to insufficient IO memory, thus returning failure.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%AAA-6-BADHDL : invalid hdl AAA ID [int], hdl [hex], [chars]
Explanation An AAA client has provided an invalid attribute list handle to AAA.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%AAA-3-BADMAGIC : Data structure failed magic number sanity check
Explanation A corrupted data structure has been found which was stored internally.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%AAA-3-BADMETHOD : Cannot process [chars] method [int]
Explanation A method list function encountered a method list that was unknown, or could not be handled.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%AAA-3-BADMETHODERROR : Cannot process [chars] method [chars]
Explanation A method list function encountered a method type that was unknown, or could not be handled.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%AAA-3-BUFFER_OVERFLOW : Radius I/O buffer has overflowed
Explanation An unusually large number of RADIUS attributes has caused AAA to overflow its RADIUS I/O buffer.
Recommended Action This is an internal software error. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.Error Message%AAA-3-DROPACCTFAIL : Accounting record dropped, send to server failed: [chars]
Explanation An attempt to send an accounting record to a server failed. This happens when device exhausts all its retries and retransmission. The cause for this might be the servers are not operational or the NAS is not configured properly.
Recommended Action Check the server , whether they are operational or not. Next check whether the device is configured properly. Refer to the server configuration section of the cisco IOS documentation. Finally, check that the NAS can communicate with the server. If this message recurs, copy the message exactly as it appears on the console or in the system log. Enter the show running-config command to gather information that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%AAA-2-FORKFAIL : Cannot fork process [chars]
Explanation Attempted to fork a process and failed. The reason could be either hardware or software.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%AAA-3-HA_INIT_FAILURE : High availability initialization failure: [chars]
Explanation The AAA subsystem was unable to perform necessary high-availability related initialization. In the event of switchover to a standby device, sessions depending on high availability capabilities in the AAA subsystem will be forced to renegotiate.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%AAA-3-HA_INTERNAL_ERROR : High availability internal error for unique id [hex]: [chars]
Explanation The AAA subsystem has suffered an internal error. In the event of switchover to a standby device, sessions depending on high availability capabilities in the AAA subsystem may be forced to renegotiate.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%AAA-6-INVALIDROUTE : Syntax error in route statement: [chars]
Explanation Current downloading route contains syntax error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%AAA-3-IPILLEGALMSG : Invalid use of ip_pid([int])
Explanation This error means a process sent an illegal message.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Enter the Show tech-support command to gather information that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%AAA-3-ISDNINTF : [chars] [chars]: cannot apply configuration to ISDN channel:
"[chars]"Explanation Configuration cannot be applied to individual ISDN channels.
Recommended Action You need virtual-profiles and virtual-access interfaces to apply configuration to ISDN. Refer to the section on "Configuring virtual profile by AAA Configuration" in the Cisco IOS Dial Technologies Configuration Guide.
Error Message%AAA-3-LOW_MEM : [chars] process is unable to handle the incoming packet due to low memory
Explanation Check the processor memory or IO memory. Most likely one of them has less available memory or, worst case, both may have insufficient memory.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%AAA-3-MLIST_TOO_MANY_METHODS : method list '[chars]'
Explanation This is an internal software error. An AAA client attempted to add too many methods to a method list.
Recommended Action This is an internal software error. Check bug tool-kit on Cisco web-site for the issue. If you did not find one, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%AAA-3-NULLCURSOR : Null cursor
Explanation A AAA client has provided a nonexistent attribute cursor to AAA.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%AAA-3-NULLVRF : Null vrf entry
Explanation A NULL VRF entry was found while comparing the AAA VRF attributes.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%AAA-3-PARSEERR : Error([dec]) parser is unable to parse [chars] per-user command
Explanation All attempts to parse this per_user unconfigure command failed. The unconfigure command is called when an error occurs while configuring per-user commands, to revert back. The unconfiguration may fail due to parser or AAA error.
Recommended Action The given unconfigure command was not executed. Enter the debug peruser command and repeat the steps that caused the error. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%AAA-3-SERVER_INTERNAL_ERROR : Server '[IP_address]': [chars]
Explanation This is an internal software error in the AAA server group subsystem.
Recommended Action This is an internal software error. Check bug toolkit on Cisco website for the issue. If you did not find one, copy the message exactly as it appears on the console or in the system log. Enter the Show tech-support command to gather information that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%AAA-3-SG_DEADTIME_FORKFAIL : Failed to fork process for [chars].
Explanation Quite likely, it ran out of memory. Other explanations are possible.
Recommended Action This is an internal software error. Check bug toolkit on Cisco website for the issue. If you did not find one, copy the message exactly as it appears on the console or in the system log. Enter the Show tech-support command to gather information that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%AAA-3-SG_INTERNAL_ERROR : server group '[chars]': [chars]
Explanation This is an internal software error in the AAA server group subsystem.
Recommended Action This is an internal software error. Check bug toolkit on Cisco website for the issue. If you did not find one, copy the message exactly as it appears on the console or in the system log. Enter the Show tech-support command to gather information that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%AAA-3-SG_TESTPROC_FORKFAIL : Failed to fork process for [chars].
Explanation Quite likely, it ran out of memory. Other explanations are possible.
Recommended Action This is an internal software error. Check bug toolkit on Cisco website for the issue. If you did not find one, copy the message exactly as it appears on the console or in the system log. Enter the Show tech-support command to gather information that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.AAL Messages
The following are messages.ATM Adaptation Layer 5 messages.
Error Message%AAL5-2-INTERNAL_CRITICAL : [chars]
Explanation The AAL5 datapath has encountered a critical software error.
The error message contains text which can be used to help
identify the nature of the problem.Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AAL5-3-INTERNAL_ERROR : [chars]
Explanation The AAL5 datapath has encountered an internal software error.
The error message contains text which can be used to help identify the nature of the problem.Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AAL5-1-NOBUFFER : [chars]: No buffer available for size [dec] bytes
Explanation No memory is available for buffer allocation.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AAL5-1-NOMEMORY : [chars]
Explanation No memory is available for allocation from heap.
The error message contains text that can be used to help
identify the nature of the problem.Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AAL5-3-PAK : Flow Hdr: ([dec]) [chars]
Explanation Either the AAL5 data path has received a large packet that is cannot process, or no more buffers are available. The packet has been dropped. The error message contains text that can help identify the nature of the problem
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AAL5-3-RXERR : Flow Hdr: ([dec]) [chars]
Explanation The AAL5 datapath has received a packet with AAL5 checksum
error. packet has been dropped. The error message contains text that can help identify the nature of the problem.Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AAL5-3-RXERR_PAKTYPE : Input Interface [chars]: [chars]
Explanation The AAL5 data path has received a packet with an invalid encapsulation for the type of packet (for example, DATA or CNTL). The packet has been dropped. The error message contains text that can help identify the nature of the problem.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
AAAA Messages
The following are TACACS+ authentication, authorization, and accounting security messages.
Error Message%AAAA-3-BADREG : Illegal registry call.
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%AAAA-3-DROPACCTQUEUEEXCEEDED : accounting record dropped, output record queue full: [chars]-[chars] [chars] [chars]
Explanation An accounting record was dropped. The record could not be enqueued because the number of records in the output queue has exceeded the system limit.
Recommended Action If periodic accounting is on, disable it by entering the [no] aaa accounting update newinfo periodic interval command.
Error Message%AAAA-3-INVALIDATTRLIST : aaa attribute list CLI is not valid when configuring in sub-mode.
Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%AAAA-4-NOCACHEPROC : The aaa cache process is not created. Please configure aaa cache profile first
Explanation Cache was listed in a method-list without defining it first. Cache profile should be defined before use.
Recommended Action Define the cache profile before using it.
AC Messages
The following are Attachtment Circuit messages.
Error Message%AC-3-ACMGR_INVALID_HDL : Received invalid [chars] handle
Explanation The Attachment Circuit Manager has recieves an invalid handle.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AC-3-ACMGR_INVALID_MSG : Received [chars]
Explanation The Attachment Circuit manager has received an invalid message.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AC-3-ACMGR_MISSED_CIRCUIT : Circuit info missing in [chars] message.
Explanation The Attachment Circuit manager has received message with missing circuit information.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AC-3-AC_PROVISION : [chars]
Explanation An error was encountered during Attachment Circuit provisioning or unprovisioning.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AC-3-AC_SUBBLOCK : [chars]
Explanation An error was encountered during Attachment Circuit
sub-block creation or removal.Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AC-3-AC_VECTOR : [chars]
Explanation An error was encountered during the configuration of the Attachment Circuit that caused problems in the setting or restoration of the interface vectors.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AC-3-L2SS_BAD_HANDLE : Corrupted L2SS handle [[hex]].
Explanation An internal L2SS Manager has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AC-3-L2SS_NULL_CONTEXT : Encountered a NULL context in [chars]
Explanation Encountered a NULL context in L2SS Manager.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AC-3-L2SS_UNEXPECTED : Received unexpected [chars] message
Explanation L2SS recieve unexpected message.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AC-3-L2SS_WRONG_KEYS : Wrong set of keys in [chars] message
Explanation The SIP sends a wrong set of keys to L2SS Manager.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
ACCESS Messages
The following are Access IE messages.
Error Message%ACCESS_IE-3-INVALID_HANDLE : Caller passed in invalid handle - traceback to follow.
Explanation An invalid handle was encountered in the Access IE library.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
ACE Messages
The following are Access Control Encryption messages.
Error Message%ACE-3-CEAL_REGISTRATION : ACE [chars] failed to register.
Explanation The ACE failed to register with CEAL.
Recommended Action Reset the hardware module.
Error Message%ACE-6-SWITCHOVER : VPN-SPA switchover: [dec]/[dec] has been [chars] [dec]/[dec]
Explanation A blade to blade switcover has occurred. System performance is not affected.
Recommended Action The system performance is not affected. This is an informational message. No action is required.
ACLMGR Messages
The following are Access Control List Manager messages.
Error Message%ACLMGR-3-ACLTCAMFULL : Acl Tcam Full! Sofware Forwarding packets on [chars] label [dec] on [chars] [chars]
Explanation There are too many ACL configuration for the platform specific ACL Tcam Table to support.
Recommended Action Reduce the number IP or MAC access lists to be configured to interfaces.
Error Message%ACLMGR-3-AUGMENTFAIL : Augmenting of access-map [chars] on [chars] label [dec] failed
Explanation The system ran out of CPU DRAM when attempting to merge internally required elements with the configuredaccess map(s).
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%ACLMGR-3-INSERTFAIL : Insert of access-map [chars] #[dec] into [chars] label [dec] failed
Explanation The system ran out of CPU DRAM when trying to merge sections of an access map.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%ACLMGR-3-MAXRECURSION : Too many ([dec]) levels of recursion while merging ACLs (code [dec]).
Explanation The configuration is too complicated for the platform specific ACL merge code to support. The most likely cause is including too many separate access lists in a single VLAN map or policy map.
Recommended Action Reduce the number IP or MAC access lists (considered separately) in any one VLAN or policy map to fewer than the number of levels reported by this log message.
Error Message%ACLMGR-3-MERGEFAIL : [chars] ACL merge error [dec] ([chars]) on [chars] label [dec]
Explanation The ACL Manager was unable to complete the merge of the configured features into a form suitable for loading into the hardware. Packets potentially affected by this feature will be sent to the CPU for processing instead. The most likely cause is specifying an ACL that is too large or too complex for the system to handle.
Recommended Action Try specifying a smaller and less complicated configuration.
Error Message%ACLMGR-3-NOLABEL : Cannot allocate [chars] label for vlan-id [dec]
Explanation The ACL Manager was unable to allocate a label for the features on this interface. This means that the hardware cannot be programmed to implement the features, and packets for this interface will be filtered in software. There is a limit of 256 labels per direction.
Recommended Action Allocate more space to the relevant section of the TCAM and reboot, or else use a simpler configuration. Use the same ACLs on multiple interfaces, if possible.
Error Message%ACLMGR-2-NOMAP : Cannot create ACL Manager data structures for VLAN Map [chars]
Explanation The ACL Manager could not allocate the data structures needed to describe a VLAN Map in a form that can be loaded into hardware. Probably caused by lack of free memory.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%ACLMGR-2-NOVLB : Cannot create memory block for VLAN [dec]
Explanation The ACL Manager was unable to save per-VLAN information needed for its correct operation. Some per-interface features, such as access groups or VLAN maps, will not be configured correctly.
Recommended Action Use a less complicated configuration that requires less memory.
Error Message%ACLMGR-2-NOVMR : Cannot create VMR data structures for access list [chars]
Explanation The ACL Manager could not allocate the data structures needed to describe an ACL in a form that can be loaded into hardware. Probably caused by lack of available memory.
Recommended Action Use a less complicated configuration that requires less memory.
Error Message%ACLMGR-3-RELOADED : Reloading [chars] label [dec] feature
Explanation The ACL Manager was able to fit more of the configured features on this label into the hardware. One or more features had previously been unloaded because of lack of space.
Recommended Action No action is required.
Error Message%ACLMGR-3-UNKNOWNACTION : Unknown VMR access group action [hex]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%ACLMGR-3-UNLOADING : Unloading [chars] label [dec] feature
Explanation The ACL Manager was unable to fit the complete configuration into the hardware, so some features will have to be applied in software. This prevents some or all of the packets in a VLAN from being forwarded in hardware, and requires them to be forwarded by the CPU. Multicast packets may be dropped entirely instead of being forwarded.
Recommended Action Allocate more space to the relevant section of the TCAM and reboot, or else use a simpler configuration. Use the same ACLs on multiple interfaces, if possible.
ACL_ASIC Messages
The following are the ACL_ASIC messages.
Error Message%ACL_ASIC-4-INTR_THROTTLE : Throttling "[chars]" interrupt exceeded permitted [int]/[dec] interrupts/msec
Explanation This message indicates an excessive number of interrupts. The system performs throttling to keep the switch processor safe.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
ACR Messages
The following are the ACR messages.
Error Message%ACR-3-ACRIFADD : [chars] interface add failed for ACR group [dec].
Explanation An attempt to add an interface to the ACR group has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show acr all command and your pertinent troubleshooting logs.Error Message%ACR-3-ACRIFDEL : [chars] interface del failed for ACR group [dec].
Explanation An attempt to delete an interface from the ACR group has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show acr all command and your pertinent troubleshooting logs.Error Message%ACR-6-ACRPVCADD : PVC creation failed for VCD= [dec] on [chars] interface of ACR interface [chars].
Explanation An attempt to create a PVC on ACR physical interface has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of show acr group and show acr group detail command and your pertinent troubleshooting logs.Error Message%ACR-3-ACRPVCDISABLE : PVC Disable failed for VCD= [dec] on [chars] interface of ACR interface [chars].
Explanation An attempt to disable a PVC on the ACR physical interface has failed.
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of show acr group and show acr group detail command and your pertinent troubleshooting logs.Error Message%ACR-6-ACRPVCENABLE : PVC Enable failed for VCD= [dec] on [chars] interface of ACR interface [chars].
Explanation An attempt to enable a PVC on the ACR physical interface has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of show acr group and show acr group detail command and your pertinent troubleshooting logs.Error Message%ACR-6-ACRVPADD : VP creation failed for VPI= [dec] on [chars] interface of ACR group [chars].
Explanation An attempt to create a VP on the ACR physical interface has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of show acr group and show acr group detail command and your pertinent troubleshooting logs.Error Message%ACR-6-ACRVPDEL : PVC deletion failed for VPI= [dec] on [chars] interface of ACR group [chars].
Explanation An attempt to delete a VP on the ACR physical interface has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of show acr group and show acr group detail command and your pertinent troubleshooting logs.Error Message%ACR-3-ACRVPDISABLE : VP Disable failed for VPI= [dec] on [chars] interface of ACR interface [chars].
Explanation An attempt to disable a VP on the ACR physical interface has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of show acr group and show acr group detail command and your pertinent troubleshooting logs.Error Message%ACR-3-ACRVPENABLE : VP Enable failed for VPI= [dec] on [chars] interface of ACR interface [chars].
Explanation An attempt to enable a VP on the ACR physical interface has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of show acr group and show acr group detail command and your pertinent troubleshooting logs.Error Message%ACR-4-ISSU_INCOMPATIBLE :
acr-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 gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ACR-1-ISSU_NOMEMORY : Unit [dec], no memory for [chars]
Explanation The requested operation could not be accomplished because of a low memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%ACR-3-ISSU_SENDFAILED :
ACR ISSU: send message failed, rc = [dec]
Explanation The sending of a message has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ACR-4-ISSU_XFORM :
[chars]: failed, rc=[chars]Explanation The transform has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
ADJ Messages
The following are Adjacency Subsystem messages.
Error Message%ADJ-3-ABNORMALSHUTDOWN : Memory expected to be freed is still in use on adj system shutdown
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%ADJ-3-ADJGENALLOCATEFAIL : Failed to allocate memory [chars]
Explanation An internal software error has occurred. This is probably because not enough memory was available.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%ADJ-3-ADJGENDEALLOCATEFAIL : Failed to deallocate memory [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%ADJ-3-ADJMGRALLOCATEFAIL : Failed to allocate an adjacency summary event block
Explanation An internal software error has occurred. This is probably because not enough memory was available.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%ADJ-3-ADJMGRDISPATCHFAIL : Failed to enqueue an adjacency summary event block
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%ADJ-3-ADJMGRREFRESHFAIL : Failed to dispatch a refresh adjacency summary event
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%ADJ-3-ALLOCATEFAIL : Failed to allocate an adjacency
Explanation An internal software error has occurred. This is probably because not enough memory was available.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%ADJ-3-ALLOCATEONDOWN : Allocating adj when adj subsystem down
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter
https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%ADJ-3-BADADDRLEN : Zero address length detected distributing adj [chars]
Explanation An internal software error has occurred. An attempt to reference an adjacency with an unsupported address type has been made.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%ADJ-3-BADADDRTYPE : Using an unsupported address type [dec] when trying to add/delete/modify/find an adjacency
Explanation An internal software error has occurred. An attempt to reference an adjacency with an unsupported address type has been made.
Recommended Action CCopy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%ADJ-3-BADLINKTYPE : Using an unsupported linktype [chars] when trying to add/delete/modify/find an adjacency
Explanation An internal software error has occurred. An attempt to reference an adjacency with an unsupported address type has been made.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%ADJ-3-BADMACALIGN : adjacency mac string end [hex] not [chars] aligned
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%ADJ-3-BADMACALIGN2 : Adjacency mac string for [chars] not byte aligned, offset [hex], length [hex]
Explanation An internal software error occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%ADJ-3-BADMAGIC : adjacency [chars] is followed by bad magic
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%ADJ-3-BOARDENCAP : Generation of encapsulation string for [chars] failed
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%ADJ-3-BROKERINITFAIL : Failed to initialise adjacency RP broker facility
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.Error Message%ADJ-3-BUNDLES : Adj bundles: [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.Error Message%ADJ-3-DBGFILTERALLOCATEFAIL : Failed to allocate an adjacency debug filter block
Explanation An internal software error has occurred. This is probably because not enough memory was available.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%ADJ-3-FEATURE : Adj features: [chars][chars][chars]
Explanation An internal software error has occurred.
Error Message%ADJ-3-ILALLOCATEFAIL : Failed to allocate an adjacency interest list subblock
Explanation An internal software error has occurred. This is probably because not enough memory was available.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%ADJ-3-ILDEALLOCATEFAIL : Failed to deallocate an adjacency interest list subblock
Explanation An internal software error has occurred. This is probably because not enough memory was available.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%ADJ-3-ILINITFAIL : Failed to initialise adjacency interest list facility
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.Error Message%ADJ-3-ILLEGALARGS : Illegal arguments - [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%ADJ-3-LCXDRCLIENT : Adjacency distribution client: [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%ADJ-3-MACOVERFLOW : Adjacency mac address for [chars] overflowed by [dec] bytes
Explanation An internal software error occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%ADJ-3-NOFIBIDB : CEF Interface not found - [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%ADJ-3-RESOLVE_REQ : Adj resolve request: [chars] [chars] [chars]
Explanation An internal software error occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%ADJ-3-RPXDRCLIENT : Adjacency distribution client: [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%ADJ-3-SBINITFAIL : Failed to initialise adjacency subblock facility
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.Error Message%ADJ-3-STATETRANSITION : Unexpected state transition from [chars] to [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%ADJ-3-TYPENOTISSUAWARE : Bundle type [chars] must be ISSU aware to send to slot(s) [chars]
Explanation The given bundle type is not ISSU aware so cannot be distributed to a slot with which ISSU negotiation has occurred. This indicates a design problem which requires code changes to fix.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%ADJ-3-XDRBADMAGIC : xdr message for [chars] spilled out of allocated static storage
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.AFLSEC Messages
The following are the AFLSEC messages.
Error Message%AFLSEC-6-OALDP : [chars] icmp [IP_address] -> [IP_address] ([dec]/[dec]), [dec] packet[chars]
Explanation Packet(s) matching the optimized ACL log criteria was detected.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AFLSEC-6-OALNP : [chars] ip protocol=[dec] [IP_address] -> [IP_address], [dec] packet[chars]
Explanation Packet(s) matching the optimized ACL log criteria was detected.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AFLSEC-6-OALP : [chars] [chars] [IP_address]([dec]) -> [IP_address]([dec]), [dec] packet[chars]
Explanation Packet(s) matching the optimized ACL log criteria was detected.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AFLSEC-6-OALRL : Oal logging rate-limited or missed [dec] packet[chars]
Explanation Some packet matching logs were missed because the log
messages were rate-limited or cache table was full or no log buffers
were available.Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AFLSEC-6-OALRP : [chars] igmp [IP_address] -> [IP_address] ([dec]), [dec] packet[chars]
Explanation Packet(s) matching the optimized ACL log criteria was detected.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
AGGMGR Messages
The following are the aggregation manager messages.
Error Message%AGGMGR-0-NO_SPACE : No space left for creator "[chars]" to add data item to agg list (items [dec] max [dec] remaining [dec])
Explanation An attempt to add an item to an aggregation list has failed. The creation of the aggregation list was successful, but for an unknown reason the addition failed. This is considered an internal error. There is no current workaround.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
AIP Messages
The following are ATM Interface Processor messages.
Error Message%AIP-3-AIPFAILSETUPVC : [chars] Failed to setup vc [dec] (Cause: [chars])
Explanation The AIP driver failed to set up a virtual circuit.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AIP-3-AIPFAILSETUPVCAVG : Interface [chars], Failed to setup vc [dec] (Cause: [chars]) Expected range [[dec] .. [dec]]Kbps for AIP Average Rate Metering. Average Rate=Peak Rate= [dec] Kbps turns Average Rate Metering OFF
Explanation A software or hardware error occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Alarm Messages
The following are Telco chassis alarm related messages.
Error Message%ALARM-1-CRITICAL_ALARM : CRITICAL alarm condition detected
Explanation A critical alarm event that needs immediate attention has occurred. The system will shut down within two minutes.
Recommended Action Check the source of the critical alarm to take any corresponding action. Do not power on unless the situation is corrected. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ALARM-6-ENTITY_INFO : [chars] [chars] [chars] [chars] [chars]
Explanation This messages indicates entity alarm assertion or deassertion information.
Recommended Action No action is required.
Error Message%ALARM-2-MAJOR_ALARM : Major alarm condition detected
Explanation A major alarm event that will affect system service has occurred.
Recommended Action Either correct or note this condition. Check the source of the major alarm and take corresponding actions.
Error Message%ALARM-3-MINOR_ALARM : Minor alarm condition detected
Explanation An minor alarm event that does not affect the system service has occurred.
Recommended Action Check the source of the minor alarm to avoid a worsening of the situation. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ALARM-3-NOCLASS : Unknown Alarm Severity Class
Explanation The alarm status tables contain an alarm entry with an unknown
alarm severity class.Recommended Action Check the source of the minor alarm to avoid a worsening of the situation. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ALARM-3-NOMESSAGES : No alarm messages left
Explanation No more alarm messages are available in the message cache
Recommended Action Check the source of the minor alarm to avoid a worsening of the situation. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ALARM-3-NOSOURCE : Attempt to set alarm status for undefined source
Explanation The alarm subsystem has no record of this alarm source. Either the source has not been registered or it has been deleted.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ALARM-3-NOTYPE : Attempt to change alarm status for undefined type
Explanation The alarm subsystem has no record of this type of alarm. Either the alarm type has not been registered or it has been deleted.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ALARM-3-TOOMANYSOURCES : Max number of alarm sources exceeded
Explanation Too many alarm sources were added by the system
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
ALPS Messages
The following are ALPS messages.
Error Message%ALPS-3-ALPSFAIL : ALPS: Assertion failed: [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ALPS-5-ASCU_DISABLED_ASCU_STUCK : ASCU [hex] on interface [chars] has been disabled since 4 consecutive messages were received from same SID.
Explanation An ALPS ASCU has been automatically disabled.
Recommended Action No action is required.
Error Message%ALPS-5-ASCU_DOWN : ASCU [hex] on interface [chars] is down.
Explanation An ALPS ASCU has transitioned from up to down.
Recommended Action No action is required.
Error Message%ALPS-3-ASCU_IF_STUCK : Polling for ASCU [hex] on interface [chars] is stalled.
Explanation The polling mechanism for an ALPS interface has stalled.
Recommended Action No action is required.
Error Message%ALPS-5-ASCU_UP : ASCU [hex] on interface [chars] is up.
Explanation An ALPS ASCU has transitioned from down to up.
Recommended Action No action is required.
Error Message%ALPS-6-CIRCUIT_ASCU_REJECT : Circuit [chars] received a Circuit Open Confirm with a list of rejected ascus
Explanation An ALPS circuit sent a Circuit Open Request message and
received a Circuit Open Confirm with a list of rejected ASCUs.Recommended Action No action is required.
Error Message%ALPS-7-CIRCUIT_BUSY_END : Circuit [chars] has exited a congested state.
Explanation An ALPS circuit is no longer experiencing congestion.
Recommended Action No action is required.
Error Message%ALPS-6-CIRCUIT_BUSY_START : Circuit [chars] has entered a congested state.
Explanation An ALPS circuit is experiencing congestion.
Recommended Action No action is required.
Error Message%ALPS-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-7-CIRCUIT_DROPS_CKT_DISABLED : Threshold exceeded for circuit disabled drops for circuit [chars]
Explanation The number of ALPS circuit drops caused by a disabled circuit exceeds the ALPS circuit threshold value.
Recommended Action No action is required.
Error Message%ALPS-7-CIRCUIT_DROPS_INVALID_ASCU : Threshold exceeded for invalid ASCU drops for circuit [chars]
Explanation The number of ALPS circuit drops caused by an invalid ASCU identifier exceeds the ALPS circuit threshold value.
Recommended Action No action is required.
Error Message%ALPS-7-CIRCUIT_DROPS_LIFETIME_EXPIRED : Threshold exceeded for lifetime timer expiration drops for circuit [chars]
Explanation The number of ALPS circuit drops due to lifetime timer
expiration exceeds the ALPS circuit threshold value.Recommended Action No action is required.
Error Message%ALPS-7-CIRCUIT_DROPS_QUEUE_OVERFLOW : Threshold exceeded for queue overflow drops for circuit [chars]
Explanation The number of ALPS circuit drops caused by queue overflow exceeds the ALPS circuit threshold value.
Recommended Action No action is required.
Error Message%ALPS-7-CIRCUIT_DROPS_VC_RESET : Threshold exceeded for X.25 VC Reset drops for circuit [chars]
Explanation The number of ALPS circuit drops caused by an X.25 VC reset exceeds the ALPS circuit threshold value.
Recommended Action No action is required.
Error Message%ALPS-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-6-CIRCUIT_OPEN_FAILED : Circuit [chars] received a Circuit Open Failed message, rsn = [chars].
Explanation An ALPS circuit sent a Circuit Open Request message and
received a Circuit Open Failed message as a reply.Recommended Action No action is required.
Error Message%ALPS-6-CIRCUIT_UPDATE_FAILED : Circuit [chars] received a Circuit Open Failed message, rsn = [chars].
Explanation An ALPS circuit sent a Circuit Update message and
received a Circuit Open Failed message as a reply.Recommended Action No action is required.
Error Message%ALPS-6-PEER_BUSY_END : Peer ([IP_address], [chars]) has exited a congested state.
Explanation An ALPS peer connection is no longer experiencing congestion.
Recommended Action No action is required.
Error Message%ALPS-6-PEER_BUSY_START : Peer ([IP_address], [chars]) has entered a congested state.
Explanation An ALPS peer connection is experiencing congestion.
Recommended Action No action is required.
Error Message%ALPS-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-7-PEER_DROPS_MAX_SIZE_EXCEEDED : Threshold exceeded for maximum size exceeded drops for peer ([IP_address], [chars]).
Explanation The number of ALPS peer drops caused by surpassing maximum size exceeds the ALPS peer threshold value.
Recommended Action No action is required.
Error Message%ALPS-7-PEER_DROPS_PEER_UNREACHABLE : Threshold exceeded for peer unreachable peer drops for peer ([IP_address], [chars]).
Explanation The number of ALPS peer drops caused by a peer unreachable condition exceeds the ALPS peer threshold value.
Recommended Action No action is required.
Error Message%ALPS-7-PEER_DROPS_QUEUE_OVERFLOW : Threshold exceeded for TCP Queue overflow peer drops for peer ([IP_address], [chars]).
Explanation The number of ALPS peer drops due to queue overflow
exceeds the ALPS peer threshold value.Recommended Action No action is required.
Error Message%ALPS-7-PEER_DROPS_VERSION_MISMATCH : Threshold exceeded for version mismatch peer drops for peer ([IP_address], [chars]).
Explanation The number of ALPS peer drops caused by a queue overflow exceeds the ALPS peer threshold value.
Recommended Action No action is required.
Error Message%ALPS-5-PEER_OPEN : Peer ([IP_address], [chars]) changed state to open.
Explanation An ALPS peer connection is now open.
Recommended Action No action is required.
Error Message%ALPS-6-PEER_OPEN_FAIL : Peer ([IP_address], [chars]) open failed, rsn = [chars]
Explanation An attempt to open an ALPS peer connection has failed.
Recommended Action No action is required.
AMDP2_FE Messages
The following are AMDP2 Ethernet and Fast Ethernet messages.
Error Message%AMDP2_FE-4-BABBLE : AMDP2/FE [chars], Babble error
Explanation The transmitter has been on the channel longer than the time taken to transmit the largest
frame.Recommended Action The system should recover. No action is required.
Error Message%AMDP2_FE-5-COLL : AMDP2/FE [chars], Excessive collisions, TDR=[dec], TRC=[dec].
Explanation Ethernet/Fast Ethernet is seeing multiple collisions. This may occur under heavy loads.
Recommended Action The system should recover. No action is required.
Error Message%AMDP2_FE-5-CONFIGNOT : The Internal Ethernet Interface is not configurable
Explanation The internal Ehternet is for system use only.
Recommended Action No action is required.
Error Message%AMDP2_FE-1-DISCOVER : Only found [dec] interfaces on bay [dec], shutting down bay
Explanation The software could not identify the interface card.
Recommended Action Power down, reseat the interface card, and reboot. If the message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%AMDP2_FE-3-GENERAL : [chars]
Explanation General C10K failure message.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%AMDP2_FE-1-INITFAIL : AMDP2/FE [dec], Init failed, CSR[dec]=[hex]
Explanation The software failed to initialize/restart an Ethernet/Fast Ethernet interface.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%AMDP2_FE-5-LATECOLL : AMDP2/FE [chars], Late collision
Explanation Late collisions occurred on the Ethernet/Fast Ethernet interface.
Recommended Action If the interface is Fast Ethernet, verify that both peers are in the same duplex mode. For regular Ethernet, the system should recover. No action is required.
Error Message%AMDP2_FE-5-LOSTCARR : AMDP2/FE [chars], Lost carrier. Transceiver problem?
Explanation The cable and/or transceiver is not connected.
Recommended Action Connect the cable and/or transceiver.
Error Message%AMDP2_FE-1-MEMERR : AMDP2/FE [chars], Memory error, CSR[dec]=[hex]
Explanation The interface could not access system resources for a long time. This problem may occur under very heavy loads.
Recommended Action The system should recover. No action is required. If thise message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%AMDP2_FE-2-NOISL : Interface [chars] does not support ISL
Explanation The interface cannot be configured as an ISL trunk.
Recommended Action Check the configuration.
Error Message%AMDP2_FE-1-NOMII : AMDFE [chars],MII Interface transceiver not connected
Explanation The MII transceiver was disconnected while the MII port was selected.
Recommended Action Connect the transceiver and enter the shut and no shut commands to shut down and restart the interface in the configuration menu.
Error Message%AMDP2_FE-3-NOTAMDP2 : Device reported [hex]
Explanation The software could not recognize the interface chips.
Recommended Action Power down, reseat the interface card, and reboot. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%AMDP2_FE-3-OVERFLO : AMDP2/FE [chars], Receive overflow
Explanation While receiving a frame, the controller chip's local buffer transmitted insufficient data because data could not be transferred to DRAM fast enough to keep pace with its input rate. Normally, such a problem is temporary, depending on transient peak loads within the system.
Recommended Action The system should recover. No action is required.
Error Message%AMDP2_FE-3-OWNERR : AMDP2/FE [chars], Buffer ownership error, pak=[hex]
Explanation The software detected an error in descriptor ownership.
Recommended Action Try a later version of the software. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%AMDP2_FE-3-SPURIDON : AMDP2/FE [chars], Spurious IDON interrupt, CSR[dec]=[hex]
Explanation An illegal condition indicating initialization done has occurred.
Recommended Action Clear the interface. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%AMDP2_FE-4-SPURIOUS : AMDP2/FE [chars], Spurious interrupt error
Explanation An illegal condition encountered during initialization.
Recommended Action The system should recover. No action is required.
Error Message%AMDP2_FE-5-SUBIF : Subinterfaces are not supported on FastEthernet
Explanation There is currently no subinterface support on fast Ethernet.
Recommended Action No action is required.
Error Message%AMDP2_FE-3-UNDERFLO : AMDP2/FE [chars], Transmit underflow
Explanation While transmitting a frame, the controller chip's local buffer received insufficient data because data could not be transferred to the chip fast enough to keep pace with its output rate. Normally, such a problem is temporary, depending on transient peak loads within the system.
Recommended Action The system should recover. No action is required.
AMD79C971_FE Messages
The following are AMD79C971 FastEthernet messages.
Error Message%AMD79C971_FE-5-FAILED_SUSPEND : Failed to suspend the amd79c971 chip
Explanation An attempt to suspend the AMD Am79C971 chip has failed.
Recommended Action No action is required.
APS Messages
The following are APS messages.
Error Message%APS-6-BIDIRSWCH : Group [chars]: Remote Request - [chars]
Explanation This message is posted by the local network element after an APS switchover that is triggered by an APS request from the remote network element.
Recommended Action This is an informational message only. No action is required.
Error Message%APS-6-CHNLACTIVE : Group [chars] - [chars] channel is now ACTIVE
Explanation The channel that was a standby channel is now the active channel. This message is informational only.
Recommended Action No action is required.
Error Message%APS-6-DISAUTFOV : Disable Auto-Failover On [chars]
Explanation APS has disabled autofailover for the indicated group.
Recommended Action Enter the show aps group name command to gather data that might help identify the nature of the error. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show aps group name, show logging, and show tech-support commands and your pertinent troubleshooting logs.
Error Message%APS-6-ENAUTFOVR : Enable Auto-Failover On [chars]
Explanation This message is posted when APS software enables hardware to perform APS actions for failures detected by the hardware. This is an informational only.
No action is required.
Error Message%APS-2-INITSYS : [chars]
Explanation A software error occurred during initialization of the APS subsystem.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%APS-2-INTRNLERR : [chars] [dec]
Explanation A software error occurred during initialization of the APS subsystem.
Recommended Action No action is required.
Error Message%APS-2-NOSOCKET : Failed To Open Socket
Explanation This message is posted when the APS subsystem fails to create a UDP socket for exchanging APS channel protocol messages over an APS message channel configured for IP. This error usually is caused by low memory in the system.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
ARAP Messages
The following are the AppleTalk Remote Access Protocol (ARAP) messages.
Error Message%ARAP-3-ABORTED : TTY [dec]: arap callback aborted
Explanation An unexpected message was received during the Microcom Networking Protocol version 4 (MNP4) link setup.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%ARAP-6-ADDRFREE : TTY [dec]: ARAP ended for user [chars]; address [atalk_net]; [dec] seconds connected
Explanation This message appears only when ARA protocol logging is configured. The message indicates that an ARA protocol user has logged out.
Recommended Action No action is required.
Error Message%ARAP-6-ADDRUSED : TTY [dec]: ARAP started for user [chars]; address [dec].[dec]
Explanation This message appears only when ARA protocol logging is configured. The message notes that an ARA protocol user has logged in.
Recommended Action No action is required.
Error Message%ARAP-0-DEFAULT : TTY [dec]
Explanation An internal software error has occured.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ARAP-6-MNP4RCVDISC : TTY [dec]: MNP4 input disconnect
Explanation This indicates that the router received a disconnect request from the remote Macintosh client.
Recommended Action No action is required.
Error Message%ARAP-6-MNP4T401 : TTY [dec]: T401 [dec] baud rate [dec]
Explanation This message indicates that the router received MNP4 connection request. MNP4 acknowledgment timer value is also indicated.
Recommended Action No action is required.
Error Message%ARAP-2-NOLOG : TTY [dec]: Could not malloc log
Explanation Memory not available for internal MNP4 logging.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ARAP-0-NOTNULLRESEND : TTY [dec]
Explanation An internal software error has occured.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ARAP-3-REMOTEERROR : TTY [dec]: arap input error
Explanation An ARAP connection was terminated without a known cause.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%ARAP-3-TIMEOUT : TTY [dec]: arap expected message timeout
Explanation The software timed out during the MNP4 link setup.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%ARAP-0-VSERROR : TTY [dec]: VS queued error
Explanation An internal software error occured.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
ARCHIVE_CONFIG Messages
The following are Archive Configuration-related messages.
Error Message%ARCHIVE_CONFIG-6-ARCHIVE_CREATE_FAILED_STANDBY : Could not create an archive of the router configuration on the standby RP.
Explanation The router could not create an archive file on the standby RP. The file that was being created contains an archive of the router configuration. This could occur, for example, if the active RP cannot communicate with the standby RP.
Recommended Action No action is required.
Error Message%ARCHIVE_CONFIG-4-ARCHIVE_DELETE_FAILED : Delete of a previously saved archive of the router configuration could not be completed.
Explanation The router could not delete a file that was previously written. The file that was being deleted file contains an archive of the router configuration. This could occur, for example, if the file was manually deleted.
Recommended Action No action is required.
Error Message%ARCHIVE_CONFIG-6-ARCHIVE_DELETE_FAILED_STANDBY : Delete of a previously saved archive of the router configuration could not be completed on the standby RP.
Explanation The router could not delete a file that was previously written on the standby RP. The file that was being deleted file contains an archive of the router configuration. This could occur, for example, if the file was manually deleted. Alternatively, the file could not be deleted when the active RP cannot communicate with the standby RP.
Recommended Action No action is required.
Error Message%ARCHIVE_CONFIG-4-ARCHIVE_SKIPPED : Archive of router configuration was skipped due to a previous initiation.
Explanation Only one archive can be created at a time. Two or more simultaneous archives in progress is not allowed. This could occur, for example, if two users attempt to create an archive simultaneouly.
Recommended Action Retry the archive creation later, when the previous archive has finished being written.
ARCHIVE_DIFF Messages
The following are Archive Diff and Rollback-related messages.
Error Message%ARCHIVE_DIFF-3-DIFF_CMD_INIT_FAILED : Failed to register the special case [chars] command:"[chars]" during initialization. Config Diff and Rollback cannot be used as a result of this error.
Explanation An internal software error occurred during initialization - Config Diff and Rollback cannot be used as a result of this error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%ARCHIVE_DIFF-3-DIFF_INIT_FAILED : Could not initialize the Config Diff and Rollback subsystem
Explanation An internal software error occurred during initialization. Config Diff and Rollback cannot be used as a result of this error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_BACKUP : Backing up current running config to [chars]
Explanation The current running configuration is saved so that when the timer expires, if no confirmation has been received from user to confirm what was configured, the system will rollback to the saved configuration.
Recommended Action This message DOES NOT denote any error condition. It is a part of the normal operation of the rollback confirmed change.
Error Message%ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_CANCEL : User: [chars]: Rollback Confirmed Change is cancelled due to [chars] failure
Explanation Rollback Confirmed Change is normally configured along with other configuration operations, such as "config term" or "config replace". If those operations failed, Rollback Confirmed Change should not be activated.
Recommended Action Remove the error condition and try again later.
Error Message%ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_CONFIRM : User: [chars]: Confirm the configuration change
Explanation The configuration change is confirmed. The timer for rolling to the previously saved configuration is cancelled
Recommended Action This message DOES NOT denote any error condition. It is a part of the normal operation of the rollback confirmed change.
Error Message%ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_RESET_ABSTIMER : User: [chars]: Reset Rollback Confirmed Change timer(absolute) to [int] minute
Explanation Reset Rollback Confirmed Change timer(absolute) to a new value.
Recommended Action This message DOES NOT denote any error condition. It is a part of the normal operation of the rollback confirmed change.
Error Message%ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_RESET_IDLETIMER : User: [chars] Reset Rollback Confirmed Change timer(idle) to [int] minute
Explanation Reset Rollback Confirmed Change timer(idle) to a new value.
Recommended Action This message DOES NOT denote any error condition. It is a part of the normal operation of the rollback confirmed change.
Error Message%ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_REVERTNOW : User: [chars]: Rollback immediately.
Explanation Rollback immediately and cancel the timer.
Recommended Action This message DOES NOT denote any error condition. It is a part of the normal operation of the rollback confirmed change.
Error Message%ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_ROLLBACK_RETRY : Failed to acquire configuration lock. Rollback did not start. Schedule to
retry in 5 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-ROLLBK_CNFMD_CHG_ROLLBACK_START : Start rolling to: [chars]
Explanation The timer for Rollback Confirmed Change has expired. System will rollback to the previously saved config.
Recommended Action This message DOES NOT denote any error condition. It is a part of the normal operation of the rollback confirmed change.
Error Message%ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_START_ABSTIMER : User: [chars]: Scheduled to rollback to config [chars] in [int] minutes
Explanation The system will wait for you to confirm that you wish to keep what was configured until the timer expires. If the confirmation is not received in time, the router will rollback.
Recommended Action This message DOES NOT denote any error condition. It is a part of the normal operation of the rollback confirmed change.
Error Message%ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_START_IDLETIMER : User: [chars]: Scheduled to rollback to config [chars] if session has been idle for [int] minutes
Explanation The system will wait for you to confirm that you wish to keep what was configured until the timer expires. If the confirmation is not received in time, the router will rollback.
Recommended Action This message DOES NOT denote any error condition. It is a part of the normal operation of the rollback confirmed change.
Error Message%ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_WARNING_ABSTIMER : System will rollback to config [chars] in one minute. Enter "configure confirm" if you wish to keep what you've configured
Explanation Rollback will start in one minute. You could enter the configure confirm command if you wish to keep what has been configured.
Recommended Action This message DOES NOT denote any error condition. It is a part of the normal operation of the rollback confirmed change.
Error Message%ARCHIVE_DIFF-5-ROLLBK_CNFMD_CHG_WARNING_IDLETIMER : User [chars] on tty [dec] has been idle for [int] minutes. System will rollback to config [chars] in oneminute if it continues to be idle. Enter "configure confirm" if you wish to keep what you've configured
Explanation Rollback will start in one minute. You can enter the configure confirm command if you wish to keep what has been configured.
Recommended Action This message DOES NOT denote any error condition. It is a part of the normal operation of the rollback confirmed change.
Recommended Action
ARP Messages
The following are ARP-related messages.
Error Message%ARP-3-ARPADJ : Internal software error during updating CEF Adjacency for ARP entry for [IP_address] on [chars]
Explanation An internal software error has occurred during updating CEF Adjacency.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ARP-3-ARPHAMSGFMT : Malformed ARP HA checkpointing message (size = [int], entry count = [int])
Explanation A malformed ARP HA checkpointing message has been received.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs
Error Message%ARP-3-ARPINIT : Internal software error during ARP subsystem initialization
Explanation An internal software error has occurred during ARP subsystem initialization.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ARP-3-ARPINT : ARP table accessed at interrupt level [dec]
Explanation ARP table is accessed at interrupt level which is forbidden.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ARP-4-ARPLEARNCROSS : [int] Learned ARP entries are installed in the ARP table and reached the max limit
Explanation The number of dynamically learned ARP entries has reached a preconfigured maximum limit in the ARP table.
Recommended Action Inspect the ARP entries on the interface. If they are valid entries, either increase the configured maximum limit or reconfigure the network to reduce ARP peers.
Error Message%ARP-6-ARPLEARNRESUME : Resuming Learn ARP entries to install in ARP table.
Explanation The number of dynamically learned ARP entries is in range of permit threshold value. The system is allowing new learned ARP entries to install in the ARP table.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%ARP-4-ARPLEARNTHRES : Learned ARP entries have reached to threshold level [int]
Explanation The number of unconfigured learned ARP entries has reached a preconfigured threshold, indicating a possible misconfiguration or a DOS attack.
Recommended Action Inspect the ARP entries on the interface. If they are valid entries, either increase the configured maximum limit or reconfigure the network to reduce ARP peers.
Error Message%ARP-3-TABLEERR : Internal software error during ARP table operation for ARP entry
Explanation An internal software error has occurred during an ARP table operation.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
AS5400 Messages
The following are AS5400 messages.
Error Message%AS5400-1-DFC_ERR : DFC [dec]: Detected PCI [chars] Error, CSR=[hex]
Explanation A PCI error that was caused by a hardware failure has been detected on the DFC. The Cisco IOS software will power down this DFC and clean up the associated system data structures.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%AS5400-3-HW_ERROR : NULL
Explanation A DFC hardware error has been detected. The Cisco IOS software will power down this DFC and clean up the associated data structures.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%AS5400-1-OLD_FIRMWARE : [chars]
Explanation The specified component should have the latest HW revision.
If the hardware revision is not the latest, then it needs to be updated to the version specified in this message.Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%AS5400-1-UNKNOWN_DFC_INT : Unknown DFC interrupt: DFC slot no [dec], interrupt [dec]
Explanation An unknown DFC interrupt is detected.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%AS5400-1-UNKNOWN_INT : Unknown interrupt: interrupt [dec]
Explanation The system detected an unknown interrupt.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
AT Messages
The following are the Apple Talk (AT) messages.
Error Message%AT-6-ACQUIREMODE : [chars]: AppleTalk interface initializing; acquiring [chars]
Explanation The interface is determining the correct configuration. This message is displayed when discovery mode is enabled and no other router is detected.
Recommended Action No action is required.
Error Message%AT-5-ADDRINUSE : [chars]: AppleTalk node warning; address [atalk_net] already in use
Explanation The initial hint address was in use. A search will be made for a valid address.
Recommended Action No action is required.
Error Message%AT-5-ADDRINVALID : [chars]: AppleTalk node warning; address [atalk_net] is invalid
Explanation The hint address specified for the interface was not valid for the current configuration.
Recommended Action The hint address is ignored and a random valid hint address is automatically computed. No action is required.
Error Message%AT-6-ADDRUSED : [chars]: AppleTalk node up; using address [atalk_net]
Explanation No hint address or a bad hint address was specified. This message indicates which AppleTalk address will be used for the interface.
Recommended Action No action is required.
Error Message%AT-6-BADROUTE : Route to [atalk_net] has gone bad
Explanation The system did not detect a route within the required timeout period. Therefore, the route is marked as bad. A network might have become unreachable for some reason, perhaps because of a broken connection. This message does not necessarily indicate an error condition.
Recommended Action No action is required.
Error Message%AT-6-CONFIGOK : [chars]: AppleTalk interface enabled; verified by [atalk_address]
Explanation The AppleTalk configuration was verified by consulting the indicated router.
Recommended Action No action is required.
Error Message%AT-6-DELROUTE : AppleTalk network deleted; [atalk_net] removed from routing table
Explanation A route on the AppleTalk network aged out.
Recommended Action No action is required.
Error Message%AT-3-DISCOFF : [chars]: AppleTalk node warning; discovery mode disabled
Explanation A hardware or software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%AT-5-DUPADDR : [chars]: AppleTalk interface restarting; node address taken by [enet]
Explanation Another AppleTalk node on a common network interface has claimed the same AppleTalk address that this router was using. The interface on this router restarts AppleTalk processing on the common network interface to resolve the address conflict. If the error recurs, a physical network problem in which the nodes cannot communicate with each other might exist.
Recommended Action No action is required unless the error persists. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AT-5-INTCLEARED : [chars]: AppleTalk interface restarting; interface cleared
Explanation A clear interface command was issued on an interface that is currently routing AppleTalk.
Recommended Action No action is required.
Error Message%AT-5-INTRESTART : [chars]: AppleTalk interface restarting; protocol restarted
Explanation The hardware interface was reset because of a configuration change. After the reset, AppleTalk automatically reinitialized the interface.
Recommended Action No action is required.
Error Message%AT-6-INTUP : [chars]: AppleTalk interface restarting; line protocol came up
Explanation An AppleTalk interface that was previously shut down has been restarted.
Recommended Action No action is required.
Error Message%AT-5-LOSTNEIGHBOR : [chars]: AppleTalk neighbor down; lost contact with [atalk_address]
Explanation A peer router is unreachable.
Recommended Action No action is required.
Error Message%AT-4-MACIPBADCONF : [chars]: MacIP inoperable configuration, [IP_address]
Explanation If the appletalk event-logging command is configured, this message appears on the console when a MacIP server cannot begin or recover operations because of an invalid IP address configuration. This condition only occurs when the configured MacIP server's IP address is not valid on the same cable of any operable IP interface. The AppleTalk zone served by the MacIP server replaces the zone specified in the appletalk zone command. The IP address configured on the MacIP server replaces the IP address configured by the ip address command. When this error occurs, the MacIP configuration is considered invalid and is deleted.
Recommended Action No action is required.
Error Message%AT-6-MACIPDOWN : [chars]: MacIP server shutting down, [IP_address]
Explanation If the appletalk event-logging command is configured, this message appears on the console when a MacIP server is no longer operational for any reason. MacIP servers shut down in response to MacIP configuration changes or errors, or a change in the condition or configuration of an AppleTalk or IP interface for which the MacIP server is providing service. The AppleTalk zone served by the MacIP server replaces the zone specified in the appletalk zone command. The IP address configured on the MacIP server replaces the IP address configured by the ip address command.
Recommended Action No action is required.
Error Message%AT-4-MACIPNOCABLE : [chars]: MacIP inoperable IP interface, [IP_address]
Explanation If the appletalk event-logging command is configured, this message appears on the console when a MacIP server can no longer operate due to a change in the condition of the IP interface it serves. This condition can occur if IP routing is shut down on the interface, or the IP address of the interface is changed so that the MacIP server's IP address is no longer valid on the same cable. The AppleTalk zone served by the MacIP server replaces the zone specified in the appletalk zone command. The IP address configured on the MacIP server replaces the IP address configured by the ip address command.
Recommended Action No action is required.
Error Message%AT-6-MACIPUP : [chars]: MacIP server operational, [IP_address]
Explanation If the appletalk event-logging command is configured, this message appears on the console when a MacIP server is fully initialized and is ready to accept client requests. The AppleTalk zone served by the MacIP server replaces the zone specified in the appletalk zone command. The IP address configured on the MacIP server replaces the IP address configured by the ip address command.
Recommended Action No action is required.
Error Message%AT-6-NBRDELETED : Neighbor entry for [atalk_address] deleted
Explanation The clear appletalk neighbor command displays this command when it completes successfully.
Recommended Action No action is required.
Error Message%AT-6-NEIGHBORUP : [chars]: AppleTalk neighbor up; [atalk_address] has restarted
Explanation A neighboring router to which this router previously lost connectivity reappeared on the network.
Recommended Action No action is required.
Error Message%AT-6-NEWNEIGHBOR : [chars]: AppleTalk neighbor added; [atalk_address] is operational
Explanation The router discovered a new AppleTalk router on the network.
Recommended Action No action is required.
Error Message%AT-6-NEWROUTE : [chars]: AppleTalk network added; [atalk_net] via [atalk_address] ([dec] hop [chars])
Explanation A new AppleTalk route has been added. The message indicates the source of the route and its distance in hops.
Recommended Action No action is required.
Error Message%AT-6-NEWZONE : AppleTalk zone added; zone [chars] defined
Explanation A new AppleTalk zone has beenn created.
Recommended Action No action is required.
Error Message%AT-6-NODEWRONG : [chars]: AppleTalk node [atalk_address] misconfigured; reply has been broadcast
Explanation An AppleTalk node sent a GetNet Info request to this router specifying an invalid network number for the source of the GetNet Info request. This situation occurs when an AppleTalk end node is moved to another network and is therefore misconfigured for the current network.
Recommended Action No action is required.
Error Message%AT-1-NOMEM : Could not allocate memory for [chars] at line [dec] in [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%AT-6-NOPROXY : AppleTalk proxy deleted; zone [chars] freed network [atalk_net]
Explanation A previously configured Name Binding Protocol (NBP) proxy was deleted. The router can no longer convert NBP requests to a format understood by routers that support only the original AppleTalk specification.
Recommended Action No action is required.
Error Message%AT-5-NOTSUPPORTED : [chars]: AppleTalk node down; line protocol not supported
Explanation An encapsulation method on the specified interface does not support AppleTalk.
Recommended Action No action is required.
Error Message%AT-6-ONLYROUTER : [chars]: AppleTalk interface enabled; no neighbors found
Explanation No other AppleTalk routers were found on the network attached to the interface.
Recommended Action No action is required.
Error Message%AT-6-PATHADD : [chars]: AppleTalk [chars] path to network [atalk_net] added; via [atalk_address] (metric [dec])
Explanation A new AppleTalk path has been added. The message indicates the source of the path, its distance in hops, its metric, and the type of path.
Recommended Action No action is required.
Error Message%AT-5-PATHCHANGE : Route to [atalk_net] is now using path of type [chars] on [chars] via [atalk_address]
Explanation The path to a network changed because either the old path went down or the new path was better.
Recommended Action No action is required.
Error Message%AT-6-PATHDEL : [chars]: AppleTalk [chars] path to [atalk_net] via [atalk_address] has been deleted
Explanation A path on the AppleTalk network has aged out.
Recommended Action No action is required.
Error Message%AT-6-PATHNOTIFY : [chars]: AppleTalk [chars] path to [atalk_net] down; reported bad by [atalk_address]
Explanation A router went down somewhere on the AppleTalk network. The indicated peer notified this router of the change.
Recommended Action No action is required.
Error Message%AT-6-REGPENDING : NBP registration of [chars] at [[chars]] pending
Explanation A name registration call is being performed.
Recommended Action No action is required.
Error Message%AT-6-ROUTEDOWN : [chars]: AppleTalk network down; interface to [atalk_net] disabled
Explanation A connected route is being advertised as down (also known as "notify neighbor") because the configured interface is no longer operational.
Recommended Action No action is required.
Error Message%AT-6-ROUTENOTIFY : [chars]: AppleTalk network down; [atalk_net] reported bad by [atalk_address]
Explanation A router went down somewhere on the AppleTalk network. The indicated peer notified this router of the change.
Recommended Action No action is required.
Error Message%AT-6-ROUTEOK : [chars]: AppleTalk network up; [atalk_net] via [atalk_address] ([dec] hop [chars])
Explanation A routing update has been received for a previously suspect route.
Recommended Action No action is required.
Error Message%AT-5-RTMPSTATE : [chars]: RTMP path to [atalk_net] via [atalk_address] now in [chars] state (metric [dec], [dec] hops)
Explanation The state of a path has changed.
Recommended Action No action is required.
Error Message%AT-3-SUBROUTINE_ERROR : AppleTalk error: [chars]
Explanation An internal error has occurred. Specifically, a programming assertion in the AppleTalk networking code has been violated.
Recommended Action No action is required.
Error Message%AT-6-ZONEGC : AppleTalk zone deleted; zone [chars] released
Explanation The router removed an unused zone from the zone table.
Recommended Action No action is required.
Error Message%AT-6-ZONEPROXY : AppleTalk proxy defined; zone [chars] using network [atalk_net]
Explanation This message reports the zone name and network number that are being advertised to support the appletalk nbp-proxy command. When proxy service is initiated, this message is generated each time the appletalk nbp-proxy command is issued.
Recommended Action No action is required.
ATA Messages
The following are ATA messages.
Error Message%ATA-6-ATA_STATUS_TIMEOUT : Timeout occurred while querying the status of ATA device.
Explanation A timeout occurred while querying the status of ATA device.
Recommended Action Replace the new ATA device and retry the operation. If this message recurs,
(1) Run 'show tech' command.
(2) Enable file system operation logs by entering the following commands:
(a) `debug ifs file'
(b) 'debug ifs fs'
(c) 'debug ifs verbose'
(3) Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.ATM Messages
The following are Asynchronous Transfer Mode messages.
Error Message%ATM-3-ATM_WAVL_TREE_ERROR : ATM(Node1 [chars] VCD [dec] ([dec]/[dec]), Node2 [chars] VCD [dec] ([dec]/[dec]) Comparison failed
Explanation A 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%ATM-6-AUTOPPP : ATM([chars]): VC(VCD=[dec], VPI=[dec], VCI=[dec]) Auto Detected Encap Type is [chars].
Explanation ATM VC AutoPPP Encapsulation Type has been changed automatically.
Recommended Action No action is required.
Error Message%ATM-3-FAILMODIFYVC : ATM failed to modify
VC(VCD=[dec], VPI=[dec], VCI=[dec]) on Interface [chars], (Cause of the
failure: [chars])Explanation ATM failed to modify QoS params on a VC for this session.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%ATM-3-FAILREGAUTOVC : ATM failed to register AutoVC
VC(VCD=[dec], VPI=[dec], VCI=[dec]) on Interface [chars], (Cause of the
failure: [chars])Explanation ATM failed to register Auto VC to the driver.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%ATM-4-ISSU_INCOMPATIBLE : atm-issu-compat: returned FALSE
Explanation The compatibility checking has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%ATM-1-ISSU_NOMEMORY : Unit [dec], no memory for [chars]
Explanation The requested operation could not be accomplished because of a low memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%ATM-3-ISSU_SENDFAILED : ATM ISSU: send message failed, rc = [dec]
Explanation The sending of a message has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%ATM-4-ISSU_XFORM : [chars]: failed, rc=[chars]
Explanation The transform has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%ATM-3-MLPDEQUEUE : MLPPP failed CosQ=[hex], MLP=[hex], OQDQ=[hex] [hex],(Cause of the failure: [chars])
Explanation This message can occur for several related reasons. Each reason is accompanied by a recommended action. The MLP has a NULL pointer error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%ATM-3-PPPOEOA_VCFLAG : ATM: [chars] PVC [dec]/[dec] : Error in PPPoE flag
Explanation The ATM PVC PPPoE flag is still set while it should not be set. ATM uses a flag to indicate whether or not it should process PPPoE frames. In some rare conditions, the flag can still be set for ATM to process PPPoE frames while it should not be. This condition can cause PPPoE frames to be processed when they should be dropped.
Recommended Action In most cases, no action is required as the system will set the flag so that ATM will not process PPPoE frames, and the system will continue to operate normally. However, If the ATM PVC specified in the error message is repeatedly experiencing problems involving PPPoE, unconfigure all commands under the PVC and remove and then reconfigure the PVC. Enter the interface atm interface.subinterface-number command in global configuration mode to enter atm interface configuration mode. Then specify the PVC you would like to unconfigure and enter the no encapsulation command. Specify the PVC you just unconfigured, then reconfigure the PVC by entering the encapsulation command.
Error Message%ATM-6-PVC_STATE_CHANGE : ATM([chars]): PVC(VCD=[dec], VPI=[dec], VCI=[dec]) state changed to [chars].
Explanation ATM PVC status has changed.
Recommended Action LOG_NO_ACTION.
Error Message%ATM-3-REJECTVC : ATM failed to create VC(VCD=[dec], VPI=[dec], VCI=[dec]) on Interface [chars], (Cause of the failure: [chars])
Explanation This message occurs when platform fails to create vc with parameterspassed to 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%ATM-5-UPDOWN : Interface [chars], Changing autovc [dec]/[dec] to [chars]
Explanation The ATM Auto 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. Enter the shutdown and no shutdown CLI commands to shut down and restart the VC.
ATMCES Messages
The following are ATM access concentrator protocol control information (PCI) port adapter driver error messages.
Error Message%ATMCES-1-BAD1575 : The 1575 device could not be initialized on bay [dec], shutting down bay
Explanation 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 gathered information.
Error Message%ATMCES-3-BADALTERACONFIG : Couldn't configure the Altera, DIO not reset
Explanation 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 gathered information.
Error Message%ATMCES-3-BADALTERAINIT : Couldn't initialize the Altera, DIO not set
Explanation 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 gathered information.
Error Message%ATMCES-3-BADBRDGCFG : Couldn't get bridge configuration: [chars]
Explanation The bridge configuration has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%ATMCES-1-BADPATYPE : Invalid Port Adapter Hardware Type Type=[dec]
Explanation The 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 gathered information.
Error Message%ATMCES-1-BADSLAVE : The Slave device could not be initialized on bay [dec], shutting down bay
Explanation 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 gathered information.
Error Message%ATMCES-1-ERRCREATEVC : The 1575 device failed to create VC [dec], file:[chars] line:[dec]
Explanation The Port Adapter encountered errors in setting up a virtual circuit (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 gathered information.
Error Message%ATMCES-1-ERRRMVC : The 1575 device not totally clean in removing VC [dec], file:[chars] line:[dec]
Explanation The Port Adapter encountered errors in shut vc command. This error 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 gathered information.
Error Message%ATMCES-3-NOTATMCESDEV : Device reported [hex]
Explanation The protocol control information (PCI) device ID is 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 gathered information.
ATMCORE Messages
The following are the ATMCORE messages.
Error Message%ATMCORE-4-ATM_SYS_ERROR : [chars]
Explanation 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 gathered information.
Error Message%ATMCORE-2-INTERNAL_CRITICAL : [chars]
Explanation 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 gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ATMCORE-3-INTERNAL_ERROR : [chars]
Explanation 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 gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ATMCORE-4-INTERNAL_WARNING : [chars]
Explanation The ATM core subsystem has encountered an internal software error. The error message contains text that can be used to help identify the nature of the problem.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ATMCORE_RED-2-INTERNAL_CRITICAL : [chars]
Explanation 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 gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ATMCORE_RED-3-INTERNAL_ERROR : [chars]
Explanation 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 gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ATMCORE_RED-4-INTERNAL_WARNING : [chars]
Explanation 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 gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
ATMLC Messages
The following are Cisco 7300 ATM line card software messages.
Error Message%ATMLC-4-ALARM : Interface ATM[dec]/[dec], received SONET/SDH alarm: [chars]
Explanation 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 messages should reflect the natural alarm conditions of the SONET/SDH-based network and do not indicate a network problem. 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.
Error Message%ATMLC-6-CLOCKING : Interface ATM[dec]/[dec], changed clock source to [chars]
Explanation 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.
Error Message%ATMLC-3-HWFAIL : The ATM line card in slot [dec] encountered a hardware failure: [chars]
Explanation 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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show c7300, show diag slot-number, show c7300 errorlog slot, show interface atm, and show controller atm commands and your pertinent troubleshooting logs.
Error Message%ATMLC-6-S1BYTE : Interface ATM[dec]/[dec] S1 byte indicates [chars] line synchronization with remote end
Explanation The remote side is indicating that the line synchronizationhas been lost or restored through the S1 byte. The S1byte is extracted from the frames.
Recommended Action No action is required.
Error Message%ATMLC-4-SONET : Interface ATM[dec]/[dec] [chars]
Explanation The ATM framer SONET failure as indicated in the message.The ATM framer SONET failure can be framer J1 trace bufferaccess fail.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.ATMOC3 Messages
The following are ATM OC-3 network module messages.
Error Message%ATMOC3-1-DISCOVER : The Network Module in slot [dec] 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 gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ATMOC3-1-GENERAL : [chars] error.
Explanation A non-recoverable error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ATMOC3-1-INITFAIL : The Network Module in slot [dec] failed to initialize (cause [chars]).
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 gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ATMOC3-1-INVALID_PCI_ID : The network module hardware reports an invalid [chars] device id of [hex].
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 gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
ATMPA Messages
The following are ATM Port Adapter messages.
Error Message%ATMPA-3-CMDFAIL : [chars] Command Failed at [chars] - line [dec], arg [dec]
Explanation The port adapter failed to process a command. The reason
could be that an OIR operation was performed of a line card or port adapter and RP was in the process of executing commands. If this message recurs, 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.Error Message%ATMPA-3-DISCOVER : found [dec] interfaces on bay [dec] (device ID [hex])
Explanation The software could not identify the interface card.
Recommended Action Power down the system. Reseat the interface card and reboot the system.
Error Message%ATMPA-2-INVDEVICE : Slot [dec] device is invalid (ID [hex])
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 gathered information.
Error Message%ATMPA-3-NOTCM622 : Slot [dec] device is not a valid PCI device vendor ID used onOC-12 PA (ID [hex])
Explanation The PCI vendor ID of the PA is not Valid. This condition could be due to a failed PA.
Recommended Action Power down the system. Reseat the interface card and reboot the system.
Error Message%ATMPA-3-NOTTI1570 : Slot [dec] device is not TI1570 (ID [hex])
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. Reseat the interface card and reboot the system.
Error Message%ATMPA-3-NOTXDESCSPACE : [chars] No tx descriptor space in buffer, data block [hex], data start [hex]
Explanation The driver could not allocate memory for a packet. This message is probably caused by memory exhaustion.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%ATMPA-3-PCIMEMNOTENOUGH : Only [hex] bytes of memory available for [chars]
Explanation 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 gathered information.
Error Message%ATMPA-3-PCI_PERROR : TI1570 unit [chars]: PCI parity error ([hex])
Explanation A parity error has 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 gathered information.
Error Message%ATMPA-3-RXDMANOTINACT : RX DMA entry [hex] not going inactive
Explanation A receive DMA channel failed to deactivate during shutdown of
a virtual circuit. This failure could originate in 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 gathered information.
Error Message%ATMPA-3-SARCRASH : [chars]: SAR[dec] SARCRASH
Explanation The SAR chip crashed and interface is being reset.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the sh cont atm xxx command to gather data that might identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%ATMPA-3-TXDMANOTFLUSHED : TX DMA not flushed
Explanation A transmit DMA channel failed to flush its buffers during
shutdown of an ATM interface. This failure could originate in 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 gathered information.
Error Message%ATMPA-3-TXFREEZE : [chars]: transmit freeze [dec]
Explanation This message indicates that the PCI-ATM interface had to stop the
transmitter while waiting for data.Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
ATMSIG Messages
The following are the ATM signalling subsystem messages.
Error Message%ATMSIG-3-ATMSIG_CUG_DELETE_FAILED : ATMSIG([chars])
Explanation A software error has 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 gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ATMSIG-3-ATMSIG_CUG_INSERT_FAILED : ATMSIG([chars])
Explanation A software error has occurred during the addition of a member to a
closed user group. Other error messages appearing immediately prior to this one might 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 gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ATMSIG-3-ATMSIG_LISTEN_FAILED_DUP : Duplicate LISTEN by [chars] for existing NSAP [chars] owned by [chars]
Explanation An application attempted to either LISTEN on an NSAP owned by
another application or to LISTEN for the same NSAP twice.Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ATMSIG-3-ATMSIG_PRTY_DELETE_FAILED : ATMSIG([chars] [dec],[dec] - [dec]/[dec]) avl prty del failed:svc [hex] party [hex]
Explanation A software error has 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 gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ATMSIG-3-ATMSIG_PRTY_INSERT_FAILED : ATMSIG([chars] [dec],[dec] - [dec]/[dec]) avl prty ins failed:svc [hex] party [hex]
Explanation A software error has occurred during addition of a party to a
point-to-multipoint call. Other error messages appearing immediately prior to this one might 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 gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ATMSIG-3-ATMSIG_SVC_DELETE_FAILED : ATMSIG([chars] [dec],[dec] - [dec]/[dec]) SVC wavl del failed:svc [hex]
Explanation A software error occurred during closure of an SVC. Other error
messages appearing immediately prior to this one may be related.Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ATMSIG-3-ATMSIG_SVC_INSERT_FAILED : ATMSIG([chars] [dec],[dec] - [dec]/[dec]) SVC wavl ins failed:svc [hex]
Explanation A software error has occurred during creation of an SVC. Other error messages appearing immediately prior to this one might 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 gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ATMSIG-3-DBINITFAIL : Signalling control block initialization failure, [chars]
Explanation An internal software or resource error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ATMSIG-3-ENQFAIL : process_enqueue failed, [chars]
Explanation An internal software error has 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 gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ATMSIG-3-FAIL1STHALFLEG : 1st halfLeg failed, [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ATMSIG-3-FAIL2NDHALFLEG : 2nd halfLeg failed, [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ATMSIG-3-FAILASSERT : Assertion failed: [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ATMSIG-3-FAILHALFLEGREM : halfLeg removal failed, [chars]
Explanation An internal software error has 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 gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ATMSIG-3-FAILXCONN : Xconnect failed, [chars]
Explanation An internal software has error occurred during the 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 gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ATMSIG-3-INVPNNIMSG : Invalid msg from routing/pnni : [chars]
Explanation This message indicates that an error has occurred in the PNNI routing subsystem. It could be caused by an internal software error or by bad control information received from the peer equipment. The message contains additional information that can help locate the cause. Any message with NULL probably indicates a problem with this system; other messages probably indicate a problem with the peer equipment.
Recommended Action Check this system and the peer equipment for any obvious errors. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%ATMSIG-3-NOCALLREF : Cannot find a Callref value to allocate: [chars]
Explanation An internal software error, probably including
memory exhaustion, has occured.Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ATMSIG-3-NOSVC : no SVC, [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ATMSIG-3-PNNI_TRACE_INTERNAL : [chars]
Explanation An internal software error or an unexpected condition occurred during PNNI (connection/path) trace-related processing.
Recommended Action Enter the show atm pnni trace information command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the message text or from the output of show atm pnni trace information command, gather information about where or how the 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 gathered information.
ATMSPA Messages
The following are ATM Shared Port Adapater messages.
Error Message%ATMSPA-3-DATA_ERROR : [chars] Error [hex] [chars]
Explanation A datapath protocol violation or sequence error has been detected.
Recommended Action The message text on the console or in the system log provides more information on the specific nature of the error.
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 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 gathered information.
Recommended Action gathered information.
Error Message%ATMSPA-3-GEN_ERROR : [chars] Error [hex] [chars]
Explanation 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 gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ATMSPA-3-HW_ERROR : [chars] Error [hex] [chars]
Explanation The specified hardware error has been detected.
Recommended Action The message text on the console or in the system log provides more information on the specific nature of the error.
Error Message%ATMSPA-3-SW_ERROR : [chars] Error [hex] [chars]
Explanation 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 gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ATMSPA-4-VPSETUP : [chars]: VP setup command received on the LC for an existing VP (VPI [dec])
Explanation A command to set up a VP has been received for a VP that has already been set up. The VP has already been configured by a previous setup VP command from the RP. A duplicate setup command may indicate that the RP did not receive a response from the LC for the previous setup command.
Recommended Action No action is required.
Error Message%ATMSPA-4-VPTEARDOWN : [chars]: VP tear down command received on the LC for a non-existing VP (VPI [dec])
Explanation The VP does not exist on the LC. Most likely, it has been torn down by a previous teardown command from RP. A duplicate teardown command may indicate that the RP did not receive a response from the LC for the previous teardown command.
Recommended Action No action is required.
ATMSSCOP Messages
The following are the Service Specific Connection Oriented Protocol (SSCOP) error messages.
Error Message%ATMSSCOP-5-SSCOPINIT : - Intf : [chars], Event : [chars], State : [chars].
Explanation This message indicates a routine step of the ATM SSCOP
initialization sequence.Recommended Action No action is required.
ATOM _NP_CLIENT Messages
The following are Area Transport over MPLS NP client messages.
Error Message%ATOM_NP_CLIENT-3-INFO : [chars]
Explanation 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 message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show tech and show log commands and your pertinent troubleshooting logs.
Error Message%ATOM_NP_CLIENT-3-NOMEM : [chars]
Explanation ATOM NP Client failed to initialize properly which will result in
improper operation of Any Transport Over MPLS featureRecommended 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
message recurs copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show tech and show log commands and your pertinent troubleshooting logs.Error Message%ATOM_NP_CLIENT-4-WARN : [chars] [dec] [chars]
Explanation AToM Entry could not be added because the entry passed is invalid.
Recommended Action Try to reload the IOS image on the affected card or platform. If the message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show tech and show log commands and your pertinent troubleshooting logs
ATOM_SEG Messages
The following are MFI AToM Segment handler messages.
Error Message%ATOM_SEG-3-CHUNKFREE : Error freeing [chars] [hex]
Explanation 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%ATOM_SEG-3-ILLEGALUPD : Illegal label [dec] update [chars]
Explanation 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%ATOM_SEG-3-NOTSUPP : Unsupported update [chars]
Explanation 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.ATOM_TRANS Messages
The following are Layer 2 Transport over MPLS messages.
Error Message%ATOM_TRANS-4-CONFIG : [chars]
Explanation 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%ATOM_TRANS-3-CONSISTENCY : [chars]
Explanation 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 gathered information.
Error Message%ATOM_TRANS-5-DISPOSITION_DISABLED : [chars]
Explanation Disposition disabled for specified AToM VC.
Recommended Action No action is required.
Error Message%ATOM_TRANS-5-DISPOSITION_ENABLED : [chars]
Explanation Disposition enabled for specified AToM VC.
Recommended Action No action is required.
Error Message%ATOM_TRANS-5-IMPOSITION_DISABLED : [chars]
Explanation Imposition disabled specified AToM VC.
Recommended Action No action is required.
Error Message%ATOM_TRANS-5-IMPOSITION_ENABLED : [chars]
Explanation Imposition enabled for specified AToM VC.
Recommended Action No action is required.
Error Message%ATOM_TRANS-3-INIT_FAIL : Failed to start AToM Manager
Explanation Failed to start and initialize the 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%ATOM_TRANS-3-LABEL_ALLOC_FAIL : Failed to allocate local label for peer:[IP_address], vcid:[int]
Explanation 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 gathered information.
AUTOSEC Messages
The following are the Auto Secure messages.
Error Message%AUTOSEC-3-CONFSAVE_FAIL : Applying AutoSecure config to running-conf failed with error [dec]
Explanation Configuration of the AutoSecure session could not be applied to the running configuration.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
AUDIT Messages
The following are Audit feature messages.
Error Message%AUDIT-1-FILE_ROLLOVER : Audit File Roll-over: [dec]
Explanation The audit circular file has rolled over.
Recommended Action Increase the audit file size.
AUTORP Messages
The following are PIMv2 AUTORP messages.
Error Message%AUTORP-6-RP_MAPPING_IDB_DEL : AutoRP RP-MAPPING IDB [chars] is deleted
Explanation The configured rp-mapping idb has been deleted.
Recommended Action No action is required.
BACKPLANE_BUS_ASIC Messages
The following are backplane bus ASIC messages.
Error Message%BACKPLANE_BUS_ASIC-5-BUS_MODE_CHANGE : The System Switching Bus Mode changed to [chars] mode
Explanation The System Switching Bus Interface device has changed switching bus modes.
Recommended Action The Supervisor has instructed this line card to change the mode on the switching bus. No action is required.
Error Message%BACKPLANE_BUS_ASIC-5-BUS_SEQ_ERR : Constellation bus Sequence Error. Resetting Backplane Bus Asic.
Explanation The switch processor has detected a sequence error on the backplane bus. A reset sequence from the EARL has been called to recover from this error. System traffic should recover and continue normally.
Recommended Action If traffic recovers, no action is required. Otherwise, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%BACKPLANE_BUS_ASIC-5-DEV_INIT_FAILURE : The Backplane Bus Asic initialization failed
Explanation The Backplane Bus Asic initialization was not successful.
Recommended Action The Backplane Bus Asic could not be initialized. As a result, this device is not operational and has been disabled. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%BACKPLANE_BUS_ASIC-5-DEV_INTR_INFO : [chars]
Explanation This message provides more information about the interrupts from the backplane bus ASIC to the line card CPU.
Recommended Action No action is required if traffic recovers. 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%BACKPLANE_BUS_ASIC-4-DEV_RESET : Backplane Bus Asic reset, interrupt [chars]
Explanation