|
|
The following are TACACS+ authentication, authorization, and accounting security (AAA) accounting error messages.
Error Message
%AAAA-6-ACCTSTART: [chars]Explanation This message is an AAA accounting start message.
Recommended Action No action is required.
Error Message
%AAAA-6-ACCTSTOP: [chars]Explanation This message is an AAA accounting stop message.
Recommended Action No action is required.
Error Message
%AAAA-6-ACCTWATCH: [chars]Explanation This message is an AAA accounting watchdog/update message.
Recommended Action No action is required.
Error Message
%AAAA-6-ADMINMSG: [chars] [chars]: [chars]Explanation This administrative message was passed to the NAS from the AAA server.
Recommended Action No action is required, but the message may contain useful information regarding an event on the server.
Error Message
%AAAA-3-BADARG: [atalk_address]talk_address]AA: bad argument ([hex])Explanation NVGEN was attempted on a nonexistent AAA command.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%AAAA-3-BADCOMM: Trying config command but should not be.Explanation An internal error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%AAAA-3-BADLIST: [atalk_address]talk_address]AA: bad [chars] list [chars]Explanation One of the AAA methods does not seem to have a list associated with it.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%AAAA-4-BADMETHNAME: Bad [chars] method-list name [chars] (this is only a warning)Explanation A method list name should not be the same as a method name.
Recommended Action Choose a different method list name that is not also a method name.
Error Message
%AAAA-3-BADREG: Illegal registry callExplanation An internal error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%AAAA-4-BADSGNAME: Bad server-group name [chars] (type [chars])Explanation Either the given server-group name does not exist or the given type does not match the defined server group.
Recommended Action Verify that the group exists and that the type is accurate.
Error Message
%AAAA-3-BADSTATE: [atalk_address]talk_address]AA: Bad state for [chars] list name ([dec])Explanation A AAA method list is neither named nor supplied by default.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%AAAA-3-BADSTR: Bad accounting data: [chars]Explanation During AAA accounting operations, the internal database of accounting information for a user was found to be corrupt. This message indicates an internal software error, and the accounting information for this user session has been lost.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%AAAA-3-DLRFORKFAIL: Failed to fork process for [chars]Explanation A possible memory loss has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%AAAA-3-DROPACCT: accounting record dropped: [chars]-[chars] [chars] [chars]Explanation An attempt to send an accounting record to a server has failed.
Recommended Action Check that the server (TACACS+ or RADIUS) is operational. Next, check that the network access server (NAS) is configured properly. Finally, check that the NAS can communicate with the server.
Error Message
%AAAA-3-ILLEGALNAME: Illegal [chars] [chars] name [chars] rejectedExplanation A method list name should not be the same as a method name.
Recommended Action Choose a different method list name that is not also a method name,
Error Message
%AAAA-3-ILLSGNAME: Illegal server-group name [chars] (type [chars])Explanation The given server-group name is a name that could conflict with internally chosen lists.
Recommended Action Choose a different server-group name.
Error Message
%AAAA-3-INTERNAL_ERROR: [chars]Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%AAAA-3-INVALIDLIST: [atalk_address]talk_address]AA: invalid [chars] list [dec]Explanation One of the AAA methods lists has inconsistent settings.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%AAAA-3-INVSTATE: [chars] AUTHOR/[chars]: Internal state is invalid: astruct 0x[hex] ustruct 0x[hex]Explanation One of the two mentioned data-structures is not set, but is needed. An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%AAAA-3-LISTCREATE: The list [dec] for [chars] is NULL. This should never be.Explanation One of the method lists, to be created at startup, was not created. This may cause a reload.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%AAAA-3-LOSTTIMER: Lost periodic accounting timer for user [chars]. Restarting timer...Explanation The periodic timer associated with the specified user has been lost.
Recommended Action Reallocate and restart a timer.
Error Message
%AAAA-3-MKTIMERFAIL: Failed to create periodic accounting timer for user [chars]. This user may not generate periodic accounting records.Explanation The system failed to allocate memory for a periodic accounting timer.
Recommended Action Free up some memory and have the user reauthenticate.
Error Message
%AAAA-3-NOADMINPROC: [chars]Explanation Administrative process has been enabled but could not run.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%AAAA-3-NOFREELISTS: [atalk_address]talk_address]AA: No free [chars] lists for [chars]Explanation You have reached the maximum number of possible authentication lists for this method.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%AAAA-3-NOLIST: [chars]: no method list-nameExplanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%AAAA-3-NOREG: [chars] method [dec] has no registryExplanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%AAAA-3-NOSERV: No name for servergroup in method [chars]Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%AAAA-4-NOSERVER: Warning: Server [int] is not definedExplanation The given server is not on the master list and should be defined, or unexpected results may occur.
Recommended Action Define the server on the appropriate master list as soon as possible.
Error Message
%AAAA-3-NOSG: No server-group passed through parserExplanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%AAAA-3-NULUSR: accounting for null userExplanation This message indicates an internal software error. During shutdown of a line or interface, the system tried to send accounting information via AAA, but could not find the user to which the accounting information belonged. This error was probably caused by the system trying to do accounting twice for the same event. This error message can occur without any loss of accounting information.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%AAAA-3-OVERWRITE: Overwrote internal buffer space [chars]Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%AAAA-3-PERIODICFORKFAIL: Failed to start periodic accounting process. Periodic accounting records may not be sentExplanation An attempt to create the periodic accounting process has failed.
Recommended Action Free up some memory.
Error Message
%AAAA-3-PERNOTIMER: AAA/ACCT/TIMER: Periodic update but no timerExplanation An attempt was made to free a timer, and the method is PERIODIC, but no timer seems to exist.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%AAAA-3-RELOGIN: sanity check in re-login [chars] to [chars]Explanation A software or hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%AAAA-3-STRCREATE: str_create overwrote its internal bufferExplanation An internal buffer used to assemble a string was exceeded, possibly corrupting other memory.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%AAAA-3-SUBTYPE: Bad Subtype [dec] for [chars] ([dec])Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%AAAA-3-TIMERNOPER: AAA/ACCT/TIMER: No periodic update but timer setExplanation An attempt to free a timer was unsuccessful. The update method was not PERIODIC, and therefore no timer will exist.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%AAAA-6-SERVERMSG: [chars] [chars]: [chars]Explanation This message was passed to the network access server (NAS) from the AAA server.
Recommended Action No action is required, but the message may contain useful information regarding an event on the server.
Error Message
%AAAA-4-SERVUNDEF: The server-group [chars] is not defined. Please define itExplanation A given server group was listed in a method list without first being defined. Server groups should be defined before use.
Recommended Action Define the server group before using it.
The following are adjacency subsystem error messages.
Error Message
%ADJ-3-ADJDELMSG: Invalid delete message length [dec]Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%ADJ-3-ADJFIBIDB: Adjacency update with invalid fibidb([dec])Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%ADJ-3-NULLFIBHWIDB: Add [chars] with null cef hwidb([chars])Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%ADJ-3-NULLFIBIDB: Add [chars] with null cef idbExplanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are ATM Interface Processor (AIP) error messages.
Error Message
%AIP-3-AIPFAILSETUPVC: [chars] Failed to setup vc [dec] (Cause: [chars])Explanation The ATM Interface Processor (AIP) driver has failed to set up a virtual circuit.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.
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 OFFExplanation A software or hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are ATM Line Card (ALC) error messages.
Error Message
%ALC-3-CMDERR: ([dec]/[dec]) Interface ([chars]): [chars] IPC command fails (cause: 0x[hex])Explanation The ATM Route Processor (RP) driver has experienced an interprocess communication (IPC) command error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%ALC-3-EVENT: ([dec]/[dec]) Interface ([chars]): unknown IPC event ([int]) from linecardExplanation The ATM Route Processor (RP) driver received an unknown event from the line card.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%ALC-4-HIRATE: ([dec]/[dec]) Interface ([chars]): SAR limits VBR VC PCR to [dec] kbps, opening UBR VC insteadExplanation The segmentation and reassembly (SAR) sublayer limits variable bit rate (VBR) virtual circuit (VC) peak cell rate PCR to one-half of the link bandwidth.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%ALC-3-INIT: ATM driver ([int]/[int]) initialization [chars].Explanation The ATM Route Processor (RP) driver has experienced a software initialization error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%ALC-4-NULLCEFIDB: ([dec]/[dec]) Interface ([chars])Explanation Cisco express forwarding (CEF) IDB is missing from this interface.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%ALC-4-UNSUP: ([dec]/[dec]) Interface ([chars]): unsupported feature: [chars]Explanation This feature is not supported by GSR ATM Route Processor (RP).
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%ALC-3-VCADJ: ([dec]/[dec]) Per-VC adjacency error: VC:[int] [chars]Explanation The ATM RP driver experienced a per-VC adjacency software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%ALC-3-VCENCTYPE: ([dec]/[dec]) VC:[int] unknown VC encapsulation type ([int])Explanation The ATM Route Processor (RP) driver has experienced an unknown virtual circuit (VC) encapsulation software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
The ALIGN facility controls a feature in Reduced Instruction Set Computer (RISC)-processor-based Cisco products that identifies software in need of memory use optimization.
Error Message
%ALIGN-3-SPURIOUS: Spurious memory access made at 0x[hex] reading 0x[hex]Explanation An error was identified (and temporarily corrected) within a software component in the router.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are Airline Protocol Support (ALPS) error messages.
Error Message
%ALPS-3-ALPSFAIL: ALPS: Assertion failed: [chars]Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%ALPS-5-ASCU_DISABLED_ASCU_STUCK: ASCU [hex] on interface [chars] has been disabled since 4 consecutive messages were received from same SIDExplanation An ALPS agent-set control unit (ASCU) has been automatically disabled.
Recommended Action No action is required.
Error Message
%ALPS-5-ASCU_DOWN: ASCU [hex] on interface [chars] is downExplanation An ALPS agent-set control unit (ASCU) has transitioned from up to down.
Recommended Action No action is required.
Error Message
%ALPS-3-ASCU_FSM_ERR: ASCU [hex] on interface [chars] has an internal FSM errorExplanation An internal software error has occurred.
Recommended Action Turn debug flags on, capture traces, and contact Cisco technical support.
Error Message
%ALPS-3-ASCU_IF_STUCK: Polling for ASCU [hex] on interface [chars] is stalledExplanation The polling mechanism for an ALPS interface has become stuck.
Recommended Action No action is required.
Error Message
%ALPS-5-ASCU_UP: ASCU [hex] on interface [chars] is upExplanation An ALPS agent-set control unit (ASCU) has transitioned from down to up.
Recommended Action No action is required.
Error Message
%ALPS-7-CIRCUIT_BUSY_END: Circuit [chars] has exited a congested stateExplanation 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 stateExplanation 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 transitioned 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 agent-set control unit (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 caused by a 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 virtual circuit (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 openExplanation 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-CIRCUIT_X25_VC_STUCK: Host unresponsive on X.25 VC for circuit [chars]Explanation The X.25 or EMTOX host is not advancing the transmit window for extended periods of time. This delay may be indicative of a temporary problem with the host application. An X.25 reset is sent to reset the transmit and receive windows to allow communication to proceed.
Recommended Action No action is required.
Error Message
%ALPS-6-PEER_BUSY_END: Peer ([int], [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 ([int], [chars]) has entered a congested stateExplanation An ALPS peer connection is experiencing congestion.
Recommended Action No action is required.
Error Message
%ALPS-5-PEER_CLOSED: Peer ([int], [chars]) changed state to closedExplanation An ALPS peer connection is now closed.
Recommended Action No action is required.
Error Message
%ALPS-5-PEER_CLOSED_DYNAMIC_INACTIVITY: Peer ([int], [chars]) closed due to inactivityExplanation An ALPS peer connection is now closed because of inactivity.
Recommended Action No action is required.
Error Message
%ALPS-5-PEER_CONN_ID_CHANGE: Peer ([int], [chars]) ID modified to ([int], [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 ([int], [chars])Explanation The number of ALPS peer drops caused by surpassing the 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 ([int], [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 ([int], [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-7-PEER_DROPS_VERSION_MISMATCH: Threshold exceeded for version mismatch peer drops for peer ([int], [chars])Explanation The number of ALPS peer drops caused by a version mismatch exceeds the ALPS peer threshold value.
Recommended Action No action is required.
Error Message
%ALPS-5-PEER_OPEN: Peer ([int], [chars]) changed state to openExplanation An ALPS peer connection is now open.
Recommended Action No action is required.
Error Message
%ALPS-6-PEER_OPEN_FAIL: Peer ([int], [chars]) open failed, rsn = [chars]Explanation An attempt to open an ALPS peer connection has failed.
Recommended Action No action is required.
The following messages are AMDP2 Ethernet and Fast Ethernet error messages.
Error Message
%AMDP2_FE-4-BABBLE: AMDP2/FE 0/0/[dec], Babble errorExplanation 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 0/0/[dec], Excessive collisions, TDR=[dec], TRC=[dec]Explanation Ethernet or Fast Ethernet is seeing multiple collisions. This may occur under heavy loads. The system should recover
Recommended Action No action is required.
Error Message
%AMDP2_FE-5-CONFIGNOT: The Internal Ethernet Interface is not configurableExplanation The internal Ethernet 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 bayExplanation The software could not identify the interface card.
Recommended Action Power down, reseat the interface card, and reboot. If the message recurs, call your Cisco technical support representative for assistance.
Error Message
%AMDP2_FE-1-INITFAIL: AMDP2/FE 0/0/[dec], Init failed, CSR[dec]=0x[hex]Explanation The software failed to initialize/restart an Ethernet or Fast Ethernet interface.
Recommended Action Clear the interface. If the message recurs, call your Cisco technical support representative for assistance.
Error Message
%AMDP2_FE-5-LATECOLL: AMDP2/FE 0/0/[dec], Late collisionExplanation Late collisions occurred on the Ethernet or 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 0/0/[dec], Lost carrier. Transceiver problem?Explanation The cable or transceiver is not connected.
Recommended Action Connect the cable or transceiver.
Error Message
%AMDP2_FE-1-MEMERR: AMDP2/FE 0/0/[dec], Memory error, CSR[dec]=0x[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 the message recurs, call your Cisco technical support representative for assistance.
Error Message
%AMDP2_FE-2-NOISL: Interface [chars] does not support ISLExplanation The interface cannot be configured as an ISL trunk.
Recommended Action Check the configuration.
Error Message
%AMDP2_FE-1-NOMII: AMDFE 0/0/[dec],MII Interface transceiver not connectedExplanation The MII transceiver was disconnected while the MII port was selected.
Recommended Action Connect the transceiver and enter the shut and no shut commands for the interface in the configuration menu.
Error Message
%AMDP2_FE-3-NOTAMDP2: Device reported [hex]Explanation The software could not recognize the interface chips.
Recommended Action Power down the system, reseat the interface card, and reboot the system. 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
%AMDP2_FE-3-OVERFLO: AMDP2/FE 0/0/[dec], Receive overflowExplanation While receiving a frame, the local buffer of the controller chip sent 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 0/0/[dec], Buffer ownership error, pak=0x[hex]Explanation The software detected an error in descriptor ownership.
Recommended Action Try a later version of the software. If the message recurs, call your Cisco technical support representative for assistance.
Error Message
%AMDP2_FE-3-SPURIDON: AMDP2/FE 0/0/[dec], Spurious IDON interrupt, CSR[dec]=0x[hex]Explanation An illegal condition has occurred, indicating that initialization has been done .
Recommended Action Clear the interface. If this message recurs, call your Cisco technical support representative for assistance.
Error Message
%AMDP2_FE-4-SPURIOUS: AMDP2/FE 0/0/[dec], Spurious interrupt errorExplanation An illegal condition has been encountered during initialization.
Recommended Action The system should recover. No action is required.
Error Message
%AMDP2_FE-3-UNDERFLO: AMDP2/FE 0/0/[dec], Transmit underflowExplanation While transmitting a frame, the local buffer of the controller chip 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. The system should recover.
Recommended Action No action is required.
The following are Authentication Proxy (AP) error messages.
Error Message
%AP-6-AUTH_PROXY_AUDIT_START: initiator ([int]) startExplanation This message documents the transaction log of network activities of Authentication Proxy (AP). The message is issued at the start of each (AP) cache, recording the source addresses.
Recommended Action This message is for informational purposes only and can be used to collect the basic accounting data for the proxied sessions.
Error Message
%AP-6-AUTH_PROXY_AUDIT_STOP: initiator ([int]) send [int] bytes; duration time [chars]Explanation This message documents the transaction log of network activities of Authentication Proxy (AP). The message is issued at the stop of each AP cache, recording the source addresses, the number of bytes transmitted by the client, and the cache duration time.
Recommended Action This message is for informational purposes only and can be used to collect the basic accounting data for the proxied sessions.
The following are Apple Remote Access Protocol error messages.
Error Message
%ARAP-3-ABORTED: TTY [dec]: arap callback abortedExplanation An unexpected message was received during the Microcom Networking Protocol version 4 (MNP4) link setup.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call 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_address]; [dec] seconds connectedExplanation This message appears only when ARA protocol logging is configured. The message notes that an ARA protocol user has logged out.
Recommended Action 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-3-BADPAK: TTY [dec]: Bad packet type in arap_send_msgExplanation Internal data structures are corrupted.
Recommended Action Check for abnormally high CPU usage.
Error Message
%ARAP-3-BADCONFIG: TTY [dec]: unhandled configuration commandExplanation A configuration command was not recognized.
Recommended Action Check the configuration file on the server for any invalid configuration commands.
Error Message
%ARAP-6-BADEXIT: TTY [dec]: exited user [chars]: [chars]Explanation A user was disconnected from ARA protocol at an unexpected time. The disconnection may have been caused by dropped modems, server errors, client problems, or related difficulties.
Recommended Action To determine the cause of the disconnection, correlate the receipt of this message with the user problem reports.
Error Message
%ARAP-4-CONFAILED: TTY [dec]: ARAP connection failed: [chars]Explanation The ARA protocol client was denied access, probably because of a configuration problem on the server. The error message should indicate the problem. This message does not indicate access denials caused by the use of bad passwords.
Recommended Action Investigate the problem reported in the error message.
Error Message
%ARAP-0-DEFAULT: TTY [dec]Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%ARAP-5-INITCONFUSED: TTY [dec]: ARAP unexpected initialization packet [chars]Explanation The startup negotiation between a client and the ARA protocol server fell out of order. If this message is received sporadically, it indicates line noise.
Recommended Action If this message recurs, reinstall the ARA client software.
Error Message
%ARAP-6-LRPHASERROR: TTY [dec]: Received LT in CONNECTION PHASEExplanation The router received an invalid packet during the ARA protocol connection setup phase.
Recommended Action Check for excessive line noise. Check the ARAP client software configuration for possible problems.
Error Message
%ARAP-6-MAXRESENDS: TTY [dec]Explanation The router resent MNP4 packets the maximum number of times without receiving an acknowledgment.
Recommended Action To determine the cause of the disconnection, correlate the receipt of this message with the user problem reports.
Error Message
%ARAP-6-MNP4RCVDISC: TTY [dec]: MNP4 input disconnectExplanation The router has 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 The router has received a MNP4 connection request. The MNP4 acknowledgment timer value is also indicated.
Recommended Action No action is required.
Error Message
%ARAP-4-NOEXTTACACS: TTY [dec]: arap TACACS is configured but extended TACACS is notExplanation Terminal Access Controller Access Control System (TACACS) authentication failed because extended TACACS is not configured.
Recommended Action Configure extended TACACS.
Error Message
%ARAP-2-NOLOG: TTY [dec]: Could not malloc logExplanation Sufficient memory is not available for internal MNP4 logging.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%ARAP-0-NOTNULLRESEND: TTY [dec]Explanation An internal software error has occurred occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%ARAP-0-NULLRESEND: TTY [dec]Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%ARAP-5-PAKINVALID: TTY [dec]: ARAP invalid packet receivedExplanation A corrupted packet has reached the ARA protocol code.
Recommended Action Check for excessive CPU usage or excessive line noise.
Error Message
%ARAP-6-RCVGIANT: TTY [dec]: Rcv giant. dropping frameExplanation The router has received an oversized MNP4 frame.
Recommended Action Check for excessive line noise. Check the ARAP client software configuration for possible problems.
Error Message
%ARAP-6-RCVNOPAK: TTY [dec]: Receive getbuffer failure. dropping frameExplanation No buffer exists for an incoming packet.
Recommended Action Examine buffer usage statistics. Possibly more memory is required.
Error Message
%ARAP-3-REMOTEERROR: TTY [dec]: arap input errorExplanation ARAP connection was terminated without a known cause.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%ARAP-6-RESENDSLOW: TTY [dec]Explanation The router repeated resending of MNP4 packets because the Macintosh client failed to acknowledge previously resent packets.
Recommended Action If this error message persists for several ARAP connections, report it to your Cisco technical support representative.
Error Message
%ARAP-3-TIMEOUT: TTY [dec]: arap expected message timeoutExplanation The software timed out during the MNP4 link setup.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%ARAP-6-TIMERERROR: TTY [dec]: MNP4 timeout errorExplanation The router is dropping the connection after doing the maximum number of resends.
Recommended Action To determine the cause of the disconnection, correlate the receipt of this message with the user problem reports.
Error Message
%ARAP-0-VSERROR: TTY [dec]: VS queued errorExplanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%ARAP-0-WAITBADMSG: TTY [dec]: arg msg bad [hex]Explanation The router received an invalid packet during ARAP MNP4 connection setup phase.
Recommended Action Check for excessive line noise. Check the ARAP client software configuration for possible problems.
Error Message
%ARAP-6-XTICKLE: TTY [dec]: exited user [chars]: Other side stopped answering ARAP tickles (mnp4 pak resent [dec] mnp4 pak sent [dec] last [dec] now [dec])Explanation The router disconnected as the remote Macintosh client stopped sending ARAP tickle or data packets.
Recommended Action To determine the cause of the disconnection, correlate the receipt of this message with the user problem reports.
The following are Asynchronous Security Protocol (ASPP) error messages.
Error Message
%ASPP-3-NOTTY: [chars]: Unable to set Rx/Tx tty async service hooks.Explanation This message occurs only when ASP is configured. It indicates the serial interface using ASP is configured incorrectly or does not support asynchronous mode.
Recommended Action Verify that the correct hardware interface type is being used.
The following are AppleTalk (AT) error 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_address] already in useExplanation 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_address] is invalidExplanation The hint address specified for the interface was not valid for the current configuration.
Recommended Action The hint address is ignored and a random valid hint address is automatically computed. No action is required.
Error Message
%AT-6-ADDRUSED: [chars]: AppleTalk node up; using address [atalk_address]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-2-ASSERTFAILED: AppleTalk assertion failed: [chars]Explanation The software has detected an inconsistency. Although this error is serious, the router attempts to continue. AppleTalk processing might be impaired.
Recommended Action Copy the message exactly as it appears, note any AppleTalk problems you experience, and call your Cisco technical support representative.
Error Message
%AT-5-BADNEIGHBOR: [chars]: AppleTalk neighbor ignored; [atalk_address] is misconfiguredExplanation The AppleTalk configuration of a neighboring router does not agree with the AppleTalk configuration of this router. This condition can result from a mismatch between the network range of the neighbor and network range of this router.
Recommended Action Modify the AppleTalk configuration of either this router or the neighboring router so that the network ranges agree.
Error Message
%AT-6-BADROUTE: Route to [atalk_address] has gone badExplanation The system did not detect a route within the required timeout period. Therefore, the route is marked as bad. A network might have become unreachable for some reason, perhaps because of a broken connection. This message does not necessarily indicate an error condition.
Recommended Action No action is required.
Error Message
%AT-7-BUGREPORT: AppleTalk bug: [chars]Explanation The software has detected an unexpected condition. The router takes corrective action and continues.
Recommended Action Copy the message exactly as it appears, note any AppleTalk problems you experience, and call your Cisco technical support representative.
Error Message
%AT-3-CANTDEL: Cannot delete [chars] route [dec] by clearing; remove it by reconfiguringExplanation The user has attempted to remove a route from the routing table by issuing the clear appletalk route command. The command failed because the route was on a directly connected interface (created when the user configured the router).
Recommended Action Remove the route by reconfiguring the directly connected interface with which it is associated.
Error Message
%AT-5-COMPATERR1: [chars]: AppleTalk internet compatibility mode required by [atalk_address]Explanation A neighboring router supports only extended AppleTalk networks with a cable range of 1 and with one assigned zone, for example, 25-25.
Recommended Action Upgrade the routers that support only the original AppleTalk specification. In the meantime, observe the compatibility rules for AppleTalk Phase 1 and Phase 2 routers.
Error Message
%AT-5-COMPATERR2: AppleTalk neighbor incompatibility; [atalk_address] has multiple zonesExplanation Although this router has neighbors that require your internetwork to observe compatibility rules, AppleTalk has learned of a route with multiple zone names defined. This condition can cause node inconsistencies on your AppleTalk network.
Recommended Action Upgrade the routers that support only the original AppleTalk specification. In the meantime, observe the compatibility rules for AppleTalk Phase 1 and Phase 2 routers.
Error Message
%AT-5-COMPATERR3: AppleTalk neighbor incompatibility; [atalk_address] has wide cable rangeExplanation Although this router has neighbors that require your internetwork to observe compatibility rules, AppleTalk has learned of a route that has a cable range greater than 1. This condition can cause node inconsistencies on your AppleTalk network.
Recommended Action Upgrade the routers that support only the original AppleTalk specification. In the meantime, observe the compatibility rules for AppleTalk Phase 1 and Phase 2 routers.
Error Message
%AT-5-COMPATERR4: AppleTalk EIGRP neighbor incompatibility; [atalk_address] has same router ID ([dec])Explanation Two routers on the network have the same router ID.
Recommended Action Reconfigure the router to have a unique router ID. If the problem recurs, copy the error message exactly as it appears and report it to your Cisco technical support representative.
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-7-DEBUGMSG: AppleTalk debug: [chars]Explanation This message is generated by a debug command and provides additional information about an AppleTalk condition.
Recommended Action Copy the message exactly as it appears, note any AppleTalk problems you experience, and call your Cisco technical support representative.
Error Message
%AT-3-DEFZONEERR: [chars]: AppleTalk interface warning; default zone differs from [atalk_address]Explanation During the verification startup process, there was a disagreement between the default zone (the first zone defined after the appletalk cable-range command) and the router that confirmed the configuration. When an AppleTalk end node is first connected to a network, it joins the default zone until it is overridden.
Recommended Action Use the appletalk zone command to correct the configuration so that all routers are advertising the same default zone. Note that several router implementations are known to mismanage the default zone.
Error Message
%AT-6-DELROUTE: AppleTalk network deleted; [atalk_address] removed from routing tableExplanation A route on the AppleTalk network has aged out.
Recommended Action No action is required.
Error Message
%AT-3-DISCOFF: [chars]: AppleTalk node warning; discovery mode disabledExplanation A hardware or software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%AT-3-DOMLOOP: Loop detected on domain [dec] [[chars]]Explanation The domain router has detected a routing loop. Routing loops are not allowed. The domain router runs a background loop detection process. The domain router starts this process when it receives a new zone list from a domain that is identical to the list in the main routing table and whose network range length matches that in this list. The loop detection process sends several AppleTalk NBP loopback packets. When one of these packets is received on an interface that does not belong to the original domain, the domain router first shuts off all the domains involved in the loop and then shuts off all the interfaces in these domains. The loop detection does not catch all types of loops. The user must ensure that no loop exists.
Recommended Action Disable the cause of the routing loop. Then use the clear appletalk command to restart the interfaces involved.
Error Message
%AT-3-DOMOVERFLOW: Remap range overflow for [chars] domain [dec]Explanation The remap range overflowed. If a network (range) cannot fit inside the remapping range, the network or cable range being advertised by a neighboring router is not accepted. When an overflow occurs, all interfaces in the domain are disabled.
Recommended Action Use the appletalk domain remap-range command to increase the remapping range. Then restart the interfaces.
Error Message
%AT-5-DUPADDR: [chars]: AppleTalk interface restarting; node address taken by [sci_notation]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-6-EIGRPLINKDN: AppleTalk EIGRP link down: [chars]Explanation An AppleTalk hardware interface was disabled.
Recommended Action No action is required.
Error Message
%AT-6-EIGRPLINKUP: Appletalk EIGRP link up: [chars]Explanation An AppleTalk Enhanced Interior Gateway Routing Protocol (IEGRP) interface that was previously shut down has been restarted.
Recommended Action No action is required.
Error Message
%AT-6-EIGRPLOG: EIGRP logging: [chars] from [atalk_address] ([int]) on [chars] for network [atalk_address], metric [int] / [int]Explanation A new AppleTalk Enhanced Interior Gateway Routing Protocol (EIGRP) path has been learned. The message indicates the source of the path, its distance in hops, its metric, and the type of path.
Recommended Action No action is required.
Error Message
%AT-4-EIGRPLOTSOWORK: AppleTalk EIGRP WorkQ processed [int] entries, required [int] ms, did [chars] suspendExplanation AppleTalk Enhanced Interior Gateway Routing Protocol (EIGRP) did not have enough time to process packets.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%AT-6-EIGRPPEERDN: AppleTalk EIGRP peer down: [atalk_address], router ID: [int], just lost on [chars]Explanation A peer router is unreachable.
Recommended Action No action is required.
Error Message
%AT-6-EIGRPPEERUP: AppleTalk EIGRP peer up: [atalk_address], router ID: [int], newly heard on [chars]Explanation A new neighbor has appeared on the network.
Recommended Action No action is required.
Error Message
%AT-5-FDDICOMPAT: AppleTalk FDDI neighbor [atalk_address] using obsolete FDDI addressingExplanation Another AppleTalk router on the FDDI ring is running a release of the router software earlier than 9.0(2). Routers running these early software releases use an encapsulation for AppleTalk on FDDI rings that is not compatible with the Apple FDDITalk implementation.
Recommended Action Upgrade the routers running the software releases that use the pre-FDDITalk encapsulation for AppleTalk on FDDI rings.
Error Message
%AT-3-IFCONFLICT: [chars]: AppleTalk interface disabled; conflicts with interface [chars]Explanation An attempt was made to configure an interface to have an AppleTalk address or cable range that is the same as or conflicts with another interface on the same router.
Recommended Action Verify that you are not specifying an AppleTalk address or cable range used previously on this router, and reconfigure the interface.
Error Message
%AT-5-INTCLEARED: [chars]: AppleTalk interface restarting; interface clearedExplanation A clear interface command was issued on an interface that is currently routing AppleTalk.
Recommended Action No action is required.
Error Message
%AT-5-INTDOWN: [chars]: AppleTalk node down; line protocol downExplanation An AppleTalk hardware interface was disabled because of a bad serial line, a configuration command, or a bad interface.
Recommended Action If the interface was not intentionally disabled, this message indicates a hardware problem. In this case, repair or replace the affected hardware.
Error Message
%AT-5-INTRESTART: [chars]: AppleTalk interface restarting; protocol restartedExplanation The hardware interface was reset because of a configuration change. After the reset, AppleTalk automatically reinitialized the interface.
Recommended Action No action is required.
Error Message
%AT-6-INTUP: [chars]: AppleTalk interface restarting; line protocol came upExplanation An AppleTalk interface that was previously shut down has been restarted.
Recommended Action No action is required.
Error Message
%AT-3-INVNBPCMD: Invalid NBPtest command [chars]Explanation An unrecognized command was specified in the Name Binding Protocol (NBP) test facility.
Recommended Action Enter a valid command.
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, [int]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 occurs only when the IP address of the configured MacIP server 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, [int]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, [int]Explanation If the appletalk event-logging command is configured, this message appears on the console when a MacIP server can no longer operate because of 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 IP address of the MacIP server 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, [int]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-3-MCMISMATCH: [chars]: AppleTalk interface warning; zone multicast [sci_notation] differs from our multicast [sci_notation]Explanation A computed multicast address disagrees with that provided by another AppleTalk router. The other AppleTalk router might be misconfigured or faulty.
Recommended Action Correct the problem at the other router.
Error Message
%AT-6-NBRDELETED: Neighbor entry for [atalk_address] deletedExplanation 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 restartedExplanation A neighboring router to which this router had previously lost connectivity has reappeared on the network.
Recommended Action No action is required.
Error Message
%AT-3-NETDISAGREES: [chars]: AppleTalk interface disabled; network incompatible with [atalk_address]Explanation The interface was disabled because the configured AppleTalk address or cable range for the interface conflicts with that of another router on the attached network.
Recommended Action Reconfigure the affected routers so that there are no conflicting addresses or cable ranges on the attached network.
Error Message
%AT-4-NETINVALID: [chars]: AppleTalk node down; conflicts with active internetExplanation The configuration specified for the interface conflicts with the active AppleTalk internetwork. For example, a cable range might be configured that overlaps an existing route but does not match the entry exactly.
Recommended Action Use the appletalk cable-range command to reconfigure the interface so that there are no conflicts with the existing AppleTalk network, or take any other actions necessary to resolve the conflict. AppleTalk will periodically attempt to restart the interface.
Error Message
%AT-6-NEWNEIGHBOR: [chars]: AppleTalk neighbor added; [atalk_address] is operationalExplanation The router has discovered a new AppleTalk router on the network.
Recommended Action No action is required.
Error Message
%AT-6-NEWROUTE: [chars]: AppleTalk network added; [atalk_address] via [atalk_address] ([dec] hop [chars])Explanation A new AppleTalk route has been learned. 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 %*s definedExplanation A new AppleTalk zone has been created.
Recommended Action No action is required.
Error Message
%AT-3-NOADDRSAVAIL: [chars]: AppleTalk node down; no addresses availableExplanation No free node could be found on the interface.
Recommended Action If the AppleTalk network has fewer than 250 nodes, issue the debug appletalk errors command and then call your Cisco technical support representative. If the AppleTalk network has more than 250 nodes, split it into smaller networks by creating new segments and moving some nodes into the new segments.
Error Message
%AT-3-NOBESTPATH: Could not compute best path for network [atalk_address]Explanation A path to the specified network could not be found.
Recommended Action Use the show appletalk route command to verify that a path to the specified network exists. If the path exists, copy the error message exactly as it appears, and report it along with the output of the show appletalk route command to your Cisco technical support representative.
Error Message
%AT-6-NODEWRONG: [chars]: AppleTalk node [atalk_address] misconfigured; reply has been broadcastExplanation An AppleTalk node has 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 error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative. 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-6-NOPROXY: AppleTalk proxy deleted; zone [chars] freed network [atalk_address]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-3-NOROUTE: No route to destination [atalk_address]Explanation The router could not deliver a packet to a destination because the router did not know where to send it.
Recommended Action Use the show appletalk route command to verify that a path to the destination exists. If it does, copy the error message exactly as it appears, and report it with the output of the show appletalk route command to your Cisco technical support representative.
Error Message
%AT-3-NOSRCADDR: [chars]: AppleTalk packet error; no source address availableExplanation The router could not generate an AppleTalk packet because no valid AppleTalk source address was available to identify this router in the packet.
Recommended Action Configure an interface to have an address or cable range. Use the show appletalk command to verify that the interface is operational.
Error Message
%AT-3-NOSUCHNBR: No such neighbor, [atalk_address]Explanation The user specified a nonexistent neighbor address when using a show appletalk neighbor or clear appletalk neighbor command.
Recommended Action Specify a valid neighbor address that appears in the output of the show appletalk neighbor command.
Error Message
%AT-5-NOSUCHROUTE: No such route [dec]Explanation The user specified a nonexistent route when using a show appletalk route or clear appletalk route command.
Recommended Action Specify a valid route that appears in the output of the show appletalk route command.
Error Message
%AT-3-NOTRUNNING: AppleTalk not runningExplanation The user tried to show or change the AppleTalk configuration when AppleTalk routing was not turned on.
Recommended Action Issue the appletalk routing command before issuing any other AppleTalk configuration or display command.
Error Message
%AT-5-NOTSUPPORTED: [chars]: AppleTalk node down; line protocol not supportedExplanation An encapsulation method on the specified interface does not support AppleTalk.
Recommended Action No action is required.
Error Message
%AT-3-NOVIRTUAL: [chars]: client tried to connect, but no virtual network is declaredExplanation A hardware or software error has occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your Cisco technical support representative.
Error Message
%AT-5-OLDMCI: [chars]: AppleTalk route cache disabled; firmware is obsoleteExplanation The firmware on the MCI controller card does not support AppleTalk fast switching.
Recommended Action No corrective action is required. Normal AppleTalk operation continues, but the fast switching cache is disabled for the interface associated with the MCI card. If this message is unexpected, verify that the MCI firmware for the interface specified in the error message is at level 1.7 or higher.
Error Message
%AT-6-ONLYROUTER: [chars]: AppleTalk interface enabled; no neighbors foundExplanation No other AppleTalk routers were found on the network attached to the interface.
Recommended Action No action is required.
Error Message
%AT-3-OUTOFSYNC: [chars]: AURP connection out of sync...terminatingExplanation The AppleTalk Update-Based Routing Protocol (AURP) detected packets that were out of sequence. This error might be caused by a lost connection.
Recommended Action Copy the error message exactly as it appears, and report it to your Cisco technical support representative.
Error Message
%AT-6-PATHADD: [chars]: AppleTalk [chars] path to network [atalk_address] added; via [atalk_address] (metric [dec])Explanation A new AppleTalk path has been learned. The message indicates the source of the path, its distance in hops, its metric, and the type of path.
Recommended Action No action is required.
Error Message
%AT-5-PATHCHANGE: Route to [atalk_address] is now using path of type [chars] on [chars] via [atalk_address]Explanation The path to a network has 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_address] via [atalk_address] has been deletedExplanation 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_address] down; reported bad by [atalk_address]Explanation A router has gone down somewhere on the AppleTalk network. The indicated peer has notified this router of the change.
Recommended Action No action is required.
Error Message
%AT-4-PATHREJECTED: AURP path [atalk_address] rejected; conflict detectedExplanation The router has detected a conflicting cable range. A router is configured with a cable range that overlaps an existing range but does not match the entry exactly.
Recommended Action Use the show appletalk command to identify the overlapped cable range, and then reconfigure the misconfigured router.
Error Message
%AT-6-REGPENDING: NBP registration of [chars] at [[chars]] pendingExplanation 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_address] disabledExplanation A connected route is being advertised as down. This condition is 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_address] reported bad by [atalk_address]Explanation A router has gone down somewhere on the AppleTalk network. The indicated peer has notified this router of the change.
Recommended Action No action is required.
Error Message
%AT-6-ROUTEOK: [chars]: AppleTalk network up; [atalk_address] 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_address] 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 was violated.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%AT-3-ZONEDISAGREES: [chars]: AppleTalk interface disabled; zone list incompatible with [atalk_address]Explanation The zone list of the configured interface is inconsistent with the zone list of other routers.
Recommended Action Reconfigure the zone list on the router so that it does not conflict with the zone lists on other routers.
Error Message
%AT-6-ZONEGC: AppleTalk zone deleted; zone [chars] releasedExplanation The router has 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_address]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.
The following are Asynchronous Transfer Mode (ATM) error messages.
Error Message
%ATM-5-ATMSOFTSTART: Restarting ATM signalling and ILMI on [chars]Explanation The command just entered causes ATM Soft Restart.
Recommended Action Stand by and allow ATM Signalling and Interim Local Management Interface (ILMI) to restart.
Error Message
%ATM-2-FAILATMSWDB: Fail malloc atm_swdb at [chars]Explanation System memory exhaustion caused an internal software error in the ATM subsystem.
Recommended Action If the system exhibits any unexpected behavior as a result of this memory exhaustion, it may require resetting to clear the error. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message
%ATM-3-FAILCREATEVC: ATM failed to create VC(VCD=[dec], VPI=[dec], VCI=[dec]) on Interface [chars], (Cause of the failure: [chars])Explanation This message can occur for one of the following unrelated reasons. Each reason is accompanied by a recommended action.
Recommended Action If none of the listed actions fixes the problem, copy the error message exactly as it appears, and report it to your Cisco technical support representative.
Error Message
%ATM-5-ILMIACCFILTER: New access filter setting will be applied to registration of new addresses on [chars]Explanation The command just entered sets up a new Interim Local Management Interface (ILMI) access filter for address registration. It affects only new addresses to be registered. The addresses already registered will not be affected.
Recommended Action Issue the shutdown and no shutdown commands on this interface to restart address registration if you must remove addresses already registered but not permitted by the new access filter.
Error Message
%ATM-5-ILMIADDREG: Address registration on [chars] is enabled. It will be initiated at next interface restartExplanation The command just entered enables ATM address registration.
Recommended Action Issue the shutdown and no shutdown commands on this interface if you must start address registration right away; otherwise, wait for next interface restart.
Error Message
%ATM-6-ILMIAUTOCFGALREADY: ILMI([chars]): Auto-configuration already enabledExplanation ATM auto-configuration has already been enabled. The atm auto-configuration command just entered is ignored.
Recommended Action No action is required.
Error Message
%ATM-4-ILMICONFIGCHANGE: ILMI([chars]): Restarting ATM signalling and ILMI. Peer Configuration change detectedExplanation The configuration of an adjacent peer device has been changed.
Recommended Action Wait for the interface to restart itself.
Error Message
%ATM-5-ILMIDEFACCFILTER: New global default access filter setting will be applied to registration of new addresses on interfaces using global default access filterExplanation The command just entered sets up a new global default access filter for address registration. It affects only new addresses to be registered on interfaces using the global default. The addresses already registered will not be affected.
Recommended Action Issue the shutdown and no shutdown commands on desired interfaces to restart address registration if you must remove addresses already registered but not permitted by the new global default access filter.
Error Message
%ATM-4-ILMIKEEPALIVEFAIL: ILMI([chars]): Restarting ATM signalling and ILMI. Keepalive failure detectedExplanation An adjacent peer device is not responding to Interim Local Management Interface (ILMI) Keepalive polling.
Recommended Action Check the connection of the ATM interface and the status of the adjacent peer device. Correct them if necessary. Wait and check to see if ILMI Keepalive comes up again. If the problem persists, copy this warning message exactly as it appears and report it to your Cisco technical support representative.
Error Message
%ATM-6-ILMINOAUTOCFG: ILMI([chars]): Auto-configuration is disabled, current interface parameters will be used at next interface restartExplanation The command just entered causes autoconfiguration to be disabled. The most recently entered interface parameters will be used at the next interface restart.
Recommended Action Note which parameters have been configured.
Error Message
%ATM-6-ILMINOAUTOCFGALREADY: ILMI([chars]): Auto configuration already disabledExplanation ATM autoconfiguration has already been enabled. The no atm auto-configuration command just entered is ignored.
Recommended Action No action is required.
Error Message
%ATM-4-MTUCALLMISMATCH: Call from: ATM NSAP - [chars] has mismatched PDU size - forward size is [dec] - backward size is [dec], int [chars] PDU size [chars] [chars]Explanation The calling or called party has a maximum transmission unit (MTU) size configured that is different from the MTU size on the current interface.
Recommended Action Either change the configured MTU size on the current interface to that of the interface of the caller or called party, or change the interface of the caller or called party to match the current interface.
Error Message
%ATM-1-NOPUSRAM: Unit [dec], not enough interface memoryExplanation The specified ATM interface hardware has run out of interface memory.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%ATM-3-OUT_OF_VCDS: ATM failed to create VC on Interface [chars]Explanation The ATM subsystem has run out of internal resources necessary to create a new virtual circuit. This condition may indicate a software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%ATM-3-OVERSUBSCRIBED: Interface [chars]: Total [chars] allocation [int][chars] exceeded maximum [chars] of [int][chars]Explanation A software or hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%ATM-4-UNMATCHUNIVERSION: ([dec]/[dec]/[dec]:[dec]): [chars]. Please verify peer UNI versionExplanation The ATM peer equipment appears to be running an old version of ATM UNI. Communication with it is not possible.
Recommended Action The peer equipment must be upgraded in order to communicate with this system.
Error Message
%ATM-3-UNSUPPORTED_QOS_PARAMS: ATM failed to create VC on Interface [chars]Explanation Either the configuration contains invalid traffic shaping parameters or the software has run out of rate queues.
Recommended Action Check the configuration for errors.
Error Message
%ATM-4-VPIVCIRANGE: VPI/VCI range parameters are dis-joint on [chars]Explanation The MinSvccVci is greater than the MaxVci, after negotiation with the peer through Interim Local Management Interface (ILMI). No SVCCs can be set up.
Recommended Action Disable autoconfiguration on both sides and change the VPI/VCI range parameters in the port configuration so that SVCCs can be set up.
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 bayExplanation The port adapter has failed its initialization.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%ATMCES-3-BADALTERACONFIG: Couldn't configure the Altera, DIO not resetExplanation The port adapter has failed its initialization.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%ATMCES-3-BADALTERAINIT: Couldn't initialize the Altera, DIO not setExplanation The port adapter has failed its initialization.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%ATMCES-3-BADBRDGCFG: Couldn't get bridge configuration: [chars]Explanation The bridge configuration has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%ATMCES-1-BADPATYPE: Invalid Port Adapter Hardware Type Type=[dec]Explanation The port adapter ID was not correct.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%ATMCES-1-BADSLAVE: The Slave device could not be initialized on bay [dec], shutting down bayExplanation The port adapter has failed its initialization.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%ATMCES-1-ERRCREATEVC: The 1575 device failed to create VC [dec], file:[chars] line:[dec]Explanation The port adapter has encountered errors in setting up a virtual circuit (VC).
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%ATMCES-1-ERRRMVC: The 1575 device not totally clean in removing VC [dec], file:[chars] line:[dec]Explanation The port adapter is encountering errors when the user enters the shut vc command. This error may affect future virtual circuit (VC) creation.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%ATMCES-3-NOTATMCESDEV: Device reported [hex]Explanation The protocol control information (PCI) device ID was not correct.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are ATM core error messages.
Error Message
%ATMCORE-4-ATM_SYS_ERROR: [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 error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call 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 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 error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%ATMCORE-3-INTERNAL_ERROR: [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 error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative, and provide the representative with the gathered information.
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 error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Posted: Fri Jun 16 11:44:15 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.