Table Of Contents
System Error Messages
AAA Accounting Messages
TACACS+ Authentication, Authorization, and Accounting security accounting error messages
Error Message%AAAA-3-BADSTR, MSG_TRACEBACK, Bad accounting data: [chars]Explanation During AAA accounting operations, the internal database of accounting information for a user was found to be corrupt. In all cases, this indicates an internal software error, and that accounting information for a particular user session has been lost.
Recommended Action Copy the error message exactly as it appears and report it to your technical support representative.
Error Message%AAAA-3-NULUSR, MSG_TRACEBACK, accounting for null userExplanation This message indicates an internal software error. During shutdown of a line or interface, the system tried to send accounting information via AAA, but could not find the user to which the accounting information belonged. The most likely reason for this error is trying to do accounting twice for the same event. This error message can occur without any loss of accounting information.
Recommended Action Copy the error message exactly as it appears and report it to your technical support representative.
ALIGN Error Messages
This facility controls a feature in the RISC-processor-based Cisco products that identifies software in need of memory use optimization.
Error Message%ALIGN-3-CORRECT: Alignment correction made at [hex] reading/writing [hex]Explanation A software component within the router needs memory optimization.
Recommended Action Report this message to your technical support representative.
Error Message%ALIGN-1-FATAL: Illegal access to low address [hex]Explanation The router identified a fatal error in a software component and could not correct it.
Recommended Action Record the entire message and immediately contact your technical support representative for assistance.
Error Message%ALIGN-3-FULL: Alignment log is full - no new entries will be recorded.Explanation The router identified more software components in need of memory optimization than it can record.
Recommended Action Call your technical support representative for assistance.
Error Message%ALIGN-3-NOMEM: Not enough memory to start alignment subsystem.Explanation The router cannot start the memory performance monitoring system because there is not enough system memory to do so.
Recommended Action Call your technical support representative for assistance.
Error Message%ALIGN-3-SPURIOUS: Spurious memory access made at [hex] reading [hex]Explanation An error was identified (and temporarily corrected) within a software component in the router.
Recommended Action Report the entire message and any problem you are experiencing to your technical support representative.
Error Message%ALIGN-3-UNUSUAL: Unusual alignment correction at [hex] [chars]ing [hex]Explanation An error was identified (and temporarily corrected) within a software component in the router.
Recommended Action Report the entire message and any problem you are experiencing to your technical support representative.
APPN Error Messages
Advanced Peer-to-Peer Networking error messages
Error Message%APPN-1-APPNALERT, MSG_TRACEBACK | MSG_PROCESS, [chars]Explanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%APPN-2-APPNCRIT, MSG_TRACEBACK | MSG_PROCESS, [chars]Explanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%APPN-7-APPNDEBUG: [chars]Explanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%APPN-0-APPNEMERG, MSG_TRACEBACK | MSG_PROCESS, [chars]Explanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%APPN-3-APPNERR: [chars]Explanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%APPN-7-APPNETERROR: [chars]Explanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%APPN-3-APPNETLOG: [chars]Explanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%APPN-6-APPNINFO: [chars]Explanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%APPN-6-APPNLOGMSG: [chars]Explanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%APPN-5-APPNNOTICE: [chars]Explanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%APPN-7-APPNSENDEVENT: [chars]Explanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%APPN-6-APPNSENDMSG: [chars]Explanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%APPN-5-APPNSENDREQ: [chars]Explanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%APPN-4-APPNWARNING: [chars]Explanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
ARAP Error Messages
Apple Remote Access Protocol error messages
Error Message%ARAP-3-ABORTED: TTY [dec]: arap callback abortedExplanation An unexpected message was received during the MNP4 link set up.
Recommended Action Report this error to your technical support representative.
Error Message%ARAP-6-ADDRFREE: TTY [dec]: ARAP ended for user [chars]; address [atalk_address]Explanation This message only appears when ARAP logging is configured. The message notes that an ARAP 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 will only appear when ARAP logging is configured. The message notes that an ARAP user has logged in.
Recommended Action No action is required.
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 ARAP at an unexpected time. This may be due to modems dropping, server error, client problems, or any number of other difficulties.
Recommended Action Possibly correlate with user problem reports.
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-4-CONFAILED: TTY [dec] ARAP connection failed: [chars]Explanation The ARAP client was denied access, probably due to a configuration problem on the server. Error message should indicate the problem. Denials due to bad passwords don't show up here.
Recommended Action Investigate problem reported in error message.
Error Message%ARAP-4-GETBUFFER: MSG_TRACEBACK getbuffer failed: size [dec]: [chars]Explanation ARAP could not obtain a buffer for an incoming packet.
Recommended Action Examine buffer usage statistics. Possibly more memory is required.
Error Message%ARAP-5-INITCONFUSED: TTY [dec]: ARAP unexpected initialization packet [chars]Explanation The startup negotiation between a client and the ARAP server fell out of order. If this is sporadic, it indicates line noise.
Recommended Action If this message recurs, reinstall the ARA client software.
Error Message%ARAP-4-NOEXTTACACS: TTY [dec]: arap TACACS is configured but extended TACACS is not.Explanation TACACS authentication failed because extended TACACS is not configured.
Recommended Action Configure extended TACACS.
Error Message%ARAP-3-NOMEM: TTY [dec]: ARAP session failed; no memoryExplanation ARAP failed to run because it couldn't allocate enough memory for its internal data structures.
Recommended Action Run show mem for details of memory usage. You probably need to install more memory.
Error Message%ARAP-5-PAKINVALID: TTY [dec] : ARAP invalid packet receivedExplanation A corrupted packet reached the ARAP code.
Recommended Action Check for excessive CPU usage or excessive line noise.
Error Message%ARAP-4-TIMEOUT: TTY [dec]: arap expected message timeoutExplanation The software timed out during the MNP4 link set up.
Recommended Action Report this error to your technical support representative.
AT Error Messages
AppleTalk error messages
Error Message%AT-6-ACQUIREMODE: [chars]: AppleTalk port initializing; acquiring [chars]Explanation The port is determining the correct configuration. This message is generated when discovery mode is enabled and no other router is detected.
Recommended Action Informational message only. No action 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 Notification message only. No action required.
Error Message%AT-5-ADDRINVALID: [chars]: AppleTalk node warning; address [atalk_address] is invalidExplanation The hint address specified for the port was not valid for its current configuration.
Recommended Action No action required; the hint is ignored and a random valid hint is automatically computed.
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.
Recommended Action Informational message only. No action required.
Error Message%AT-2-ASSERTFAILED: AppleTalk assertion failed: [chars]Explanation The software detected an inconsistency. Although this error is serious, the router attempts to continue. AppleTalk processing can be impaired.
Recommended Action Record the entire message and note any AppleTalk problems you experience. Give this information to your technical support representative in a problem report.
Error Message%AT-5-BADNEIGHBOR: [chars]:AppleTalk neighbor ignored; [node] is misconfiguredExplanation A neighboring router's AppleTalk configuration does not agree with this router's AppleTalk configuration. This condition can result from a mismatch between the neighbor's network range and this router's network range.
Recommended Action Modify either this router's or the neighboring router's configuration so that the network ranges agree.
Error Message%AT-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. This can mean that a network has become unreachable for some reason—perhaps a broken connection. This message does not necessarily reflect an error condition.
Recommended Action Informational message only. No action required.
Error Message%AT-7-BUGREPORT: AppleTalk Bug: [chars]Explanation The software detected an unexpected condition. The router takes corrective action and continues.
Recommended Action Record the entire message and note any AppleTalk problems you experience. Give this information to your technical support representative in a problem report.
Error Message%AT-3-CANTDEL: Cannot delete [chars] route [dec] by clearing; please remove by reconfigurationExplanation The user attempted to remove a route from the routing table with the command clear appletalk route. The command failed because the route was directly connected (that is, it was created by a configuration command).
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 [node]Explanation A neighboring router only supports extended AppleTalk networks with a cable range of 1 and with one assigned zone, for example, 25-25.
Recommended Action Upgrade routers that can support only the original AppleTalk specification, and observe the compatibility rules in the interim.
Error Message%AT-5-COMPATERR2: AppleTalk neighbor incompatibility; [atalk_net] 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 inconsistencies for nodes in your internet.
Recommended Action Upgrade routers that can support only the original AppleTalk specification, and observe the compatibility rules in the interim.
Error Message%AT-5-COMPATERR3: AppleTalk neighbor incompatibility; [atalk_net] 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 wide (greater than 1) cable range. This condition can cause inconsistencies for nodes in your internetwork.
Recommended Action Upgrade routers that can support only the original AppleTalk specification, and observe the compatibility rules in the interim.
Error Message%AT-5-COMPATERR4: AppleTalk EIGRP neighbor incompatibility; [node] has same router ID [dec]Explanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%AT-6-CONFIGOK: [chars]: AppleTalk port enabled; verified [node]Explanation The AppleTalk configuration was verified by consulting the indicated router.
Recommended Action Informational message only. No action required.
Error Message%AT-6-CPUPIG, MSG_PROCESS|MSG_TRACEBACK, AppleTalk CPU piggie info: just spent [dec] ms. without scheduleExplanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%AT-7-DEBUGMSG: AppleTalk Debug: [chars]Explanation This message is generated by a debug command to provide additional information about a condition in AppleTalk.
Recommended Action If you experience problems in AppleTalk, show these messages to your technical support representative.
Error Message%AT-3-DEFZONEERR: [chars]: AppleTalk port warning; default zone differs with [node]Explanation This message is generated during the verification startup process when there is 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 this default zone until it is overridden.
Recommended Action 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_net] removed from routing tableExplanation A route aged out of the AppleTalk internetwork.
Recommended Action Informational message only. No action required.
Error Message%AT-5-DISCOFF: [CHARS]: AppleTalk node warning; discovery mode disabledExplanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%AT-3-DOMLOOP: LOOP Detected on Domain [dec] [ [chars] ]Explanation A routing loop was detected by the domain router.
Loops are not allowed; however, a loop detection process running in the background of the domain router tries to spot a loop situation. Whenever a domain router gets a new zone list from one of the domains that is identical to one in the main routing table and the length of the network range matches, it starts a loop detection process.
A loop detection process sends several AppleTalk loop packets, which are NBP packets of type "LoopBack". When a loop packet is received on the interface that does not belong to the original domain, the domain router shuts off all the domains, and subsequently all the interfaces in these domains, which are involved in the loop.
Loop detection may not catch all types of loops. It is the responsibility of the user to make sure that no loop exists.
Recommended Action Disable the cause of the routing loop. 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, then it is not accepted until more remapping room is available. When overflow occurs, all interfaces in the domain are disabled.
Recommended Action Increase the remapping range. Restart the interfaces.
Error Message%AT-5-DUPADDR: [chars]: AppleTalk port restarting; node address taken by [enet]Explanation Another AppleTalk node on a common network interface claimed the same AppleTalk address that this router was using. This error indicates a serious, unexpected problem. If it recurs, a physical network problem in which the nodes cannot hear each other may exist.
Recommended Action This router will restart AppleTalk processing on the common network interface to resolve the address conflict. No action required.
Error Message%AT-6-EIGRPLINKDN: AT/EIGRP Link Down: [chars]Explanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%AT-6-EIGRPLINKUP: AT/EIGRP Link Up: [chars]Explanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%AT-6-EIGRPLOG: EIGRP Logging: [chars] from [atalk_address] ([dec]) on [chars] for network [atalk_net], metric [dec] / [dec]Explanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%AT-4-EIGRPLOTSOWORK: AT/EIGRP WorkQ processed [dec] entries, required [dec] ms. we did[chars] suspendExplanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%AT-6-EIGRPPEERDN: AT/EIGRP Peer Down: [atalk_address], router ID: [dec], just lost on [chars]Explanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%AT-6-EIGRPPEERUP: AT/EIGRP Peer Up: [atalk_address], router ID: [dec], newly heard on [chars]Explanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%AT-5-FDDICOMPAT: AppleTalk FDDI neighbor [atalk_net] using obsolete FDDI addressingExplanation Another router on an FDDI ring running AppleTalk is running a release of the router software previous to 9.0(2). Routers running software releases earlier than 9.0(2) use an encapsulation for AppleTalk on FDDI rings that is not compatible with the Apple FDDITalk preliminary proposal.
Recommended Action Notification message only. No action required.
Error Message%AT-3-IFCONFLICT: [chars]: AppleTalk port disabled; conflicts with port [chars]Explanation An attempt was made to configure an interface to have the same or a conflicting AppleTalk address or cable range as another interface on the same router.
Recommended Action Verify that you are not specifying an AppleTalk address or cable range used previously on this router, and reconfigure the interface.
Error Message%AT-5-INTCLEARED: [chars]: AppleTalk port restarting; interface clearedExplanation This message is generated by performing the EXEC command clear interface on an interface currently routing AppleTalk.
Recommended Action Notification message only. No action 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 port was not intentionally disabled, this message can reflect a hardware problem. If so, repair or replace the controller.
Error Message%AT-5-INTRESTART: [chars]: AppleTalk port restarting; protocol restartedExplanation This message is generated when a configuration change necessitates resetting the hardware interface. AppleTalk reinitialized the port.
Recommended Action Notification message only. No action required.
Error Message%AT-6-INTUP: [chars]: AppleTalk port restarting; Line protocol came upExplanation An AppleTalk port that was previously shut down was restarted.
Recommended Action Informational message only. No action required.
Error Message%AT-3-INVNBPCMD: Invalid NBPtest command `[chars]'Explanation An unrecognized command was given 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 [node]Explanation A peer router is unreachable.
Recommended Action Notification message only. No action required.
Error Message%AT-3-MACIPBADCONF: ZONE-NAME: MacIP inoperable configuration, X.X.X.XExplanation 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. An AppleTalk zone of the MacIP server replaces ZONE-NAME. The MacIP server's configured IP address replaces X.X.X.X.
When this error occurs, the MacIP configuration is considered invalid and is deleted.
Recommended Action Advisory message. No action required.
Error Message%AT-6-MACIPDOWN: ZONE-NAME: MacIP server shutting down, X.X.X.XExplanation 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. An AppleTalk zone of the MacIP server replaces ZONE-NAME. The MacIP server's configured IP address replaces X.X.X.X.
Recommended Action Informational message only. No action required.
Error Message%AT-3-MACIPNOCABLE: ZONE-NAME: MacIP inoperable IP interface, X.X.X.XExplanation 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. An AppleTalk zone of the MacIP server replaces ZONE-NAME. The MacIP server's configured IP address replaces X.X.X.X.
Recommended Action Advisory message only. No action required.
Error Message%AT-6-MACIPUP: ZONE-NAME: MacIP server operational, X.X.X.XExplanation 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. An AppleTalk zone served by the MacIP server replaces ZONE-NAME. The MacIP server's configured IP address replaces X.X.X.X.
Recommended Action Informational message only. No action required.
Error Message%AT-3-MCMISMATCH: [chars]: AppleTalk port warning; zone multicast differs with [node]Explanation A computed multicast address disagrees with that provided by another AppleTalk router. The other AppleTalk router may be misconfigured or faulty.
Recommended Action Correct the problem at the other router.
Error Message%AT-6-NBRDELETED: Neighbor entry for [atalk_net] has been deletedExplanation This message is displayed upon successful completion of the EXEC command clear appletalk neighbor.
Recommended Action Informational message only. No action required.
Error Message%AT-6-NEIGHBORUP: [chars]: AppleTalk neighbor up; [node] has restartedExplanation A neighboring router to which this router previously lost connectivity reappeared on the network.
Recommended Action Informational message only. No action required.
Error Message%AT-3-NETDISAGREES: [chars]: AppleTalk port disabled; network incompatible with [node]Explanation The port was disabled because the configured AppleTalk address or cable range on the interface conflicts with another router on the attached network.
Recommended Action Reconfigure the applicable routers.
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 is configured so that it overlaps an existing route but does not match the entry exactly.
Recommended Action Reconfigure the port so that it is consistent with the existing internetwork or take any other actions necessary to resolve the conflict. AppleTalk will periodically attempt to restart the port.
Error Message%AT-6-NEWNEIGHBOR: [chars]: AppleTalk neighbor added; [node] is operationalExplanation The router discovered a new AppleTalk router.
Recommended Action Informational message only. No action required.
Error Message%AT-6-NEWROUTE: [chars]: AppleTalk network added; [atalk_net] via [node] ([dec] hop[char])Explanation A new AppleTalk route has been learned. The message includes the source of the route and its distance in hops.
Recommended Action Informational message only. No action required.
Error Message%AT-6-NEWZONE: AppleTalk zone added; zone [chars] definedExplanation A new AppleTalk zone has been created.
Recommended Action Informational message only. No action 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 fewer than 250 nodes reside on your AppleTalk network, call your technical support representative. Otherwise, you must split your AppleTalk network into smaller networks.
Error Message%AT-3-NOBESTPATH: Could not compute best path for network [atalk_net]Explanation A path to the specified network could not be found.
Recommended Action Call your technical support representative for assistance.
Error Message%AT-6-NODEWRONG: [chars]: AppleTalk node [atalk_address] misconfigured; reply has been broadcastExplanation An AppleTalk node sent a GetNet Info request to this router specifying an invalid network number for the source of the GetNet Info request. This situation occurs when an AppleTalk end node is moved between networks and is therefore misconfigured for the current network.
Recommended Action Informational message only. No action required.
Error Message%AT-1-NOMEM: Could not allocate memory for [chars] at line [dec] in [chars]Explanation An internal software error occurred.
Recommended Action Call your technical support representative for assistance.
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 specification of AppleTalk.
Recommended Action Informational message only. No action required.
Error Message%AT-3-NOROUTE: No route to destination [atalk_address]Explanation The router could not deliver a packet to a destination because it did not know where to send it.
Recommended Action If the destination is valid, you must determine why the router does not know the route (that is, the neighboring router may be withholding information).
Error Message%AT-3-NOSRCADDR: [chars]: AppleTalk packet error; no source address availableExplanation An attempt to generate an AppleTalk packet from the router failed because no valid AppleTalk source address is available to identify this router in the packet.
Recommended Action Configure a port to have an address or cable range and verify that the port is operational.
Error Message%AT-3-NOSUCHNBR: No such neighbor, [atalk_net]Explanation The user tried to execute the EXEC commands show appletalk neighbor or clear appletalk neighbor with a nonexistent neighbor address.
Recommended Action Specify a valid neighbor address, that is, one that appears in the output of the show appletalk neighbor command with no arguments.
Error Message%AT-5-NOSUCHROUTE: No such route [dec]Explanation The user tried to execute the EXEC commands show appletalk route or clear appletalk route with a nonexistent route.
Recommended Action Specify a valid route, that is, one that appears in the output of the show appletalk route command with no arguments.
Error Message%AT-3-NOTRUNNING: AppleTalk not runningExplanation You tried to show or change the AppleTalk configuration when AppleTalk routing was not turned on.
Recommended Action Issue the appletalk routing configuration command prior to issuing any other AppleTalk configuration or display command.
Error Message%AT-5-NOTSUPPORTED: [chars]: AppleTalk node down; line protocol not supportedExplanation The specified interface has an encapsulation method that does not support AppleTalk.
Recommended Action Notification message only. No action required.
Error Message%AT-3-NOVIRTUAL: [chars]: Client tried to connect, but no virtual network is declaredExplanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
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 is permitted, but the fast switching cache is disabled for the associated port. If unexpected, verify that the MCI controller firmware for the interface specified in the error message is at level 1.7 or higher.
Error Message%AT-6-ONLYROUTER: [chars]: AppleTalk port enabled; no neighbors foundExplanation No other AppleTalk routers were found on the network attached to the port.
Recommended Action Informational message only. No action required.
Error Message%AT-6-OUTOFSYNC; [chars]: AURP connection out of sync...terminatingExplanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%AT-6-PATHADD: [chars]: AppleTalk [chars] path to network [atalk_net] added; via [node] (metric [dec])Explanation A new AppleTalk path has been learned. The message includes the source of the path, its distance in hops, its metric, and the type of path.
Recommended Action Informational message only. No action required.
Error Message%AT-5-PATHCHANGE: Route to [atalk_net] is now using path of type [chars] on [chars] via [node]Explanation The path to a network changed either because the old path went down or the new path was better.
Recommended Action Notification message only. No action required.
Error Message%AT-6-PATHDEL: AppleTalk [chars] path to [atalk_net] via [node] has been deletedExplanation A path aged out of the AppleTalk network.
Recommended Action Informational message only. No action required.
Error Message%AT-6-PATHNOTIFY: [chars]: AppleTalk [chars] path to [atalk_net] down; reported bad by [node]Explanation A router went down somewhere on the AppleTalk network. The specified peer notified this router of the change.
Recommended Action Informational message only. No action required.
Error Message%AT-4-PATHREJECTED: AURP path [atalk_net] rejected; conflict detectedExplanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%AT-6-REGPENDING: NBP registration of [chars]@[chars] pendingExplanation A name registration call is being performed.
Recommended Action Informational message only. No action required.
Error Message%AT-6-ROUTEDOWN: [chars]: AppleTalk network down; port to [atalk_net] disabledExplanation A connected route is being advertised as down (also known as notify neighbor) because the configured port is no longer operational.
Recommended Action Informational message only. No action required. If unexpected, correct the situation that caused the port to be disabled.
Error Message%AT-6-ROUTENOTIFY: [chars]: AppleTalk network down; [atalk_net] reported bad by [node]Explanation A router went down somewhere on the AppleTalk network. The specified peer notified this router of the change.
Recommended Action Informational message only. No action required.
Error Message%AT-6-ROUTEOK: [chars]: AppleTalk network up; [atalk_net] via [node] ([dec] hop[char])Explanation A routing update was received for a previously suspect route.
Recommended Action Informational message only. No action required.
Error Message%AT-5-RTMPSTATE: [chars]: [chars] RTMP Path to [atalk_net] via [node] now in [chars] state (metric [dec])Explanation The state of a path changed.
Recommended Action Informational message only. No action required.
Error Message%AT-3-SUBROUTINE_ERROR: AppleTalk error: [chars]Explanation An internal error occurred that violates a programming assertion in the AppleTalk networking module.
Recommended Action Save the text of the message, the output of the show version command, and a copy of the router configuration file. Call your technical support representative for assistance.
Error Message%AT-3-ZONEDISAGREES: [chars]: AppleTalk port disabled; zone list incompatible with [node]Explanation The configurations of one or more other routers are inconsistent with the configuration of this router.
Recommended Action Reconfigure the routers so they are all consistent.
Error Message%AT-6-ZONEGC: AppleTalk zone deleted; zone [chars] releasedExplanation The router purged an unused zone from the zone table.
Recommended Action Informational message only. No action 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.
Recommended Action Informational message only. No action required. One message is generated for each configuration command when proxy service is initiated.
ATM Error Message
Asynchronous Transfer Mode error message
Error Message%ATM-4-NOMEM: Failed to allocate memory--[chars], ONEMINExplanation The system attempted to allocate some memory but failed.
Recommended Action Reduce the RAM usage or add more RAM to your router.
BGP Error Messages
Border Gateway Protocol error messages
Error Message%BGP-3-BADMASK: Attempt to install route for [inet] without valid mask in [chars]Explanation An internal software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%BGP-6-NEXTHOP: Invalid next hop ([inet]) received from [inet]: [chars], 5*ONESECExplanation The remote BGP peer sent in a route with an illegal next hop.The given route was ignored.
Recommended Action This is an informational message only. The remote peer may be misconfigured.
Error Message%BGP-3-NOMEMORY: No memory for [chars] entry, resettingExplanation 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%BGP-3-RADIXINIT: Radix tree initialization failedExplanation Initialization of the radix tree 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.
BRI Error Messages
ISDN Basic Rate Interface error messages
Error Message%BRI-3-BADENCAP: Unit [dec], bad encapsulation in idb->enctype = [hex]%BRI-3-BADUNIT: Bad unit number [dec]Explanation An internal software error occurred.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%BRI-1-INITFAIL: Unit [dec], initialization timeout failureExplanation The hardware failed to initialize correctly.
Recommended Action Repair or replace the controller.
Error Message%BRI-0-NOMEMORY: Unit [dec], no memory for [chars]%BRI-1-NOMEMORY, 0, msgtxt_nomemory, MSGDEF_LIMIT_SLOWRecommended Action 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%BRI-3-ODDSTART: Interface [chars]Explanation An internal software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%BRI-3-OUTENCAP: Unit [dec], bad output packet encapsulation: [hex]Explanation An internal software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%BRI-3-OWNERR: Unit [dec], buffer ownership errorExplanation An Ethernet interface is malfunctioning, or an internal software error occurred.
Recommended Action Repair or replace the malfunctioning controller.
BSC Error Messages
Binary Synchronous Communications protocol error messages
Error Message%BSC-3-BADPEERTYPE: Peer [chars] is incorrect typeExplanation This message occurs only when BSC local-ack is configured. It indicates the serial interfaces that are using the BSTUN tunnel are configured incorrectly, that is, both have been configured as a secondary.
Recommended Action Reconfigure the serial interfaces correctly to be a primary and secondary pair.
Error Message%BSC-2-NOMEM: No buffers available on interface [chars].Explanation This message indicates that memory in the router was exhausted.
Recommended Action Perform diagnostics on the router to locate the sub-system or interface responsible for consuming memory. The only method that will clear this situation is to reload the router.
BSTUN Error Messages
Block serial tunneling error messages
Error Message%BSTUN-3-BADCONN: CONN: bad connection ([dec]), peer: [chars]%BSTUN-3-BADLENOP: [chars]: bad len or unknown op, op [dec], len [dec]%BSTUN-3-BADMAGIC: [chars]: wrong magic, mine [hex], theirs [hex] ([dec])%BSTUN-3-BADMAGICTCP: [chars]: peer [chars], wrong magic, min [hex], theirs [hex]%BSTUN-3-BADPASSIVEOPEN: passive open from [inet] ([dec]) -> [dec] failed%BSTUN-3-CONNILLSTATE: CONN: Peer [chars], illegal state [dec]Explanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%BSTUN-6-CONNOPENFAIL: CONN: peer [chars] open failed, [chars] [[dec]]Explanation An attempt to connect to a remote TCP BSTUN peer failed.
Recommended Action Verify that the remote peer is accessible from this router, that it is running software capable of supporting BSTUN, and that it is configured correctly.
Error Message%BSTUN-6-ERR: [chars]: [chars]: [chars], op [hex], len [dec]Explanation An internal software error occurred.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%BSTUN-2-NOBUF: Interface [chars], no buffer available to [chars]Explanation A memory shortage existed at the time that the configuration command was issued. This condition is rare and, under normal conditions, temporary.
Recommended Action Reconfigure the BSTUN group. If memory shortages persist, call your technical support representative for assistance.
Error Message%BSTUN-3-NOPROTMEM: No memory for BSTUN protocol definition of [chars]Explanation The system does not have sufficient memory to define a new BSTUN schema.
Recommended Action This error message should only print when the router is critically short of memory. Call your technical support representative for assistance.
Error Message%BSTUN-6-OPENED: [chars]: peer [chars] opened, [previous state [chars]]%BSTUN-6-OPENING: CONN: opening peer [chars], [dec]%BSTUN-6-PASSIVEOPEN: passive open [inet]([dec]) -> [dec]Explanation A connection attempt to a remote peer completed successfully (OPENED, PASSIVE-OPEN) or is in the process of being opened (OPENING). This is good, expected behavior.
Recommended Action Informational message only. No action required.
Error Message%BSTUN-6-PEERSHUTDOWN: shutting down peer [chars] on [chars]Explanation A connection to a remote peer is being shut down. This is typically the result of user intervention in BSTUN reconfiguration or disabling. This is good, expected behavior.
Recommended Action Informational message only. No action required.
Error Message%BSTUN-4-PEERSTATE: Peer [chars], wrong state [dec] ([dec])Explanation An internal software error occurred.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%BSTUN-6-RECONNECT: PHDR: reconnect from peer [chars]Explanation A remote peer reestablished a connection to this router.
Recommended Action Informational message only. No action required.
Error Message%BSTUN-3-SENDPUNT: [chars]: sent [chars] to [chars]%STUN-3-SENDPUNTTCP: [chars]: sent [chars] to ([[dec]]) [inet]Explanation An internal software error occurred.
Recommended Action If either message recurs, call your technical support representative for assistance.
Error Message%BSTUN-6-TCPFINI: peer [chars] closed [previous state [chars]]Explanation A remote peer closed a BSTUN connection with this router.
Recommended Action Examine the other router to see why it closed this connection with this peer. This can be caused by normal events, such as reconfiguration.
Error Message%BSTUN-6-TCPPEERSHUT: [chars] [chars], [inet]([dec])Explanation This route closed a BSTUN connection with a remote peer.
Recommended Action Examine this router to see why it closed this connection with this peer. This can be caused by normal events, such as reconfiguration.
CBus Error Messages
ciscoBus controller error messages
Error Message%CBUS-3-AIPCFG: Interface [chars], Cannot config interface, AIP MEM [hex],status [dec]%CBUS-3-AIPINVPLIM: Interface [chars], Invalid PLIM detected. Interface downed%CBUS-3-AIPRSET: Interface [chars], Error ([hex]) [chars] - aip_reset()%CBUS-3-AIPRSETU: Unit [dec], Error ([hex]) [chars] - aip_reset()Explanation A software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%CBUS-3-BIGBUF:Controller [dec], Error [hex], Big Buffers [dec]Explanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%CBUS-3-BUFFER: Controller [dec], Error ([hex]), Buffersize = [dec], Bufferpool = [dec], number [dec]Explanation An internal software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%CBUS-3-CBUSBCE: Failed to select a BCE, response [hex] - cbus_bce_update_ifa()Explanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%CBUS-3-CBUSBCEPERM: Failed to select a BCE, response [hex] - cbus_bce_permissions_update()Explanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
Explanation
%CBUS-3-CCBCMDFAIL0: Controller [dec], cmd ([dec]) failed (0x%-04x)Explanation A command sent from the system to an interface processor failed to complete successfully.
Recommended Action The system recovered by generating an error code to the requester.
Error Message%CBUS-3-CCBCMDFAIL1: Controller [dec], cmd ([dec] 0x%-08x) failed (0x%-04x)Explanation A command sent from the system to an interface processor failed to complete successfully.
Recommended Action The system recovered by generating an error code to the requester.
Error Message%CBUS-3-CCBPTIMEOUT, MSG_TRACEBACK, CCB handover timed out, CCB 0x[hex], slot [dec]Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears and report it to your technical support representative.
Error Message%CBUS-3-CCBREPLY: [chars]: bad CCB reply [hex]Explanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%CBUS-4-CIPADPTCHNG: Interface [chars], adapter changed from [chars] to [chars]Explanation The port adapter on the CIP interface reported a different interface type than it previously did, which should not happen without your removing the CIP and reinstalling it.
Recommended Action Call your technical support representative for assistance.
Error Message%CBUS-3-CIPCFGFAIL: [chars]: configuration command [chars] [chars] failedExplanation A configuration command sent to the CIP after a reset failed to complete successfully.
Recommended Action Reissue the configuration command.
Error Message%CBUS-3-CIPDTRFAIL: [chars]: Channel-protocol [chars] command failed; resetting to default.Explanation The channel-protocol configuration command sent to the CIP after a reset failed to complete successfully.
Recommended Action The channel data transfer rate was reset to the default value. Reissue the configuration command.
Error Message%CBUS-3-CIPRESET: Interface [chars], Error [hex] [chars] - cip_reset()Explanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%CBUS-3-CMD, MSG_TRACEBACK, Cmd failed: [chars], response %#04x, [chars]Explanation A software or hardware error occurred.
Recommended Action Copy the error message exactly as it appears and report it to your technical support representative.
Error Message%CBUS-3-CMDTIMEOUT, MSG_TRACEBACK, Cmd timed out, CCB 0x[hex], slot [dec], cmd code [dec]Explanation A software or hardware error occurred.
Recommended Action Copy the error message exactly as it appears and report it to your technical support representative.
Error Message%CBUS-3-CORRUPT: Controller [dec], wrote [hex], read [hex], loc [hex] - dci_memtest()Explanation A hardware component failed an internal diagnostic test.
Recommended Action Replace the malfunctioning device.
Error Message%CBUS-3-CTRACHECK: Unit [dec], Adapter Check Error ([hex] [hex] [hex] [hex])Explanation The Token Ring monitor firmware detected a fatal error on the interface card.
Recommended Action Issue a clear interface command. If this message recurs, call your technical support representative for assistance.
Error Message%CBUS-3-CTRCMDFAILED: Unit [dec], CTR Command [hex] Failed, [char] ([hex])Explanation A command from the system to the Token Ring interface failed to complete.
Recommended Action Call your technical support representative for assistance.
Error Message%CBUS-3-CTRCMDFAILED2: Unit [dec], CTR Command %#04x Failed, Code %#04xExplanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%CBUS-3-CTRINIT: Unit [dec], CTR Initialization Failed - [char]Explanation The Token Ring interface failed its internal self-tests.
Recommended Action Issue a clear interface command. If this message recurs, call your technical support representative for assistance.
Error Message%CBUS-3-CTRLRCMDFAIL0: Controller [dec], cmd ([dec]) failed (0x%-04x) count ([dec])Explanation A command sent from the system to an interface processor failed to complete successfully.
Recommended Action The system recovered by generating an error code to the requester.
Error Message%CBUS-3-CTRLRCMDFAIL1: Controller [dec], cmd ([dec] 0x%-08x) failed (0x%-04x) count ([dec])Explanation A command sent from the system to an interface processor failed to complete successfully.
Recommended Action The system recovered by generating an error code to the requester.
Error Message%CBUS-3-CTRLRINITERR: Controller [dec], Error [hex], cdb [hex] [chars] - cbus_init()Explanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%CBUS-3-CTRRAMTEST: Unit [dec], RAM Addressing Test Failed - [char]Explanation The Token Ring interface failed its memory diagnostic tests.
Recommended Action Issue a clear interface command. If this message recurs, call your technical support representative for assistance.
Error Message%CBUS-3-CTRRESET: Unit [dec], Error (%-04x) [char] - cbus_token_reset()Explanation The Token Ring interface failed to complete a command that is part of the reset sequence.
Recommended Action Issue a clear interface command. If this message recurs, call your technical support representative for assistance.
Error Message%CBUS-3-CTRUCHECK: Unit [dec], Microcode Check ErrorExplanation The CTR microcode detected an unrecoverable error.
Recommended Action Issue a clear interface command. If this message recurs, call your technical support representative for assistance.
Error Message%CBUS-3-DAUGHTER: Unit [dec], daughter controller [dec] failed [chars] test - interface disabledExplanation A hardware component failed an internal diagnostic test. Test output and descriptions of ranges follow.
Unit [dec] (ranges 0-14):Indicates the Multibus jumper setting for the ciscoBus controller, or in the Cisco 7000, a slot number.
daughter controller [dec] (ranges 0-3):Indicates the ciscoBus relative slot number (0 to 3, or in the Cisco 7000, 0 to 4) of the daughter card that failed the test.
failed [chars] test ([chars]= memd read, memd write):If the failed test was memd read, the processor was able to write to shared ciscoBus buffer memory from the ciscoBus registers, but was unable to read back that memory through special commands to the daughter card.
If the failed test was memd write, writes to MEMD through the daughter card were not verified successfully with reads through the ciscoBus controller.
The daughter card under test responds successfully to some commands (otherwise the software would have received a DAUGHTER_NO_RSP message), but its MEMD tests failed. The daughter card must be able to write to some MEMD addresses; otherwise, it cannot respond to any commands.
Recommended Action First check that the daughter controller card is properly seated in its Multibus and ciscoBus connectors. Next, swap daughter cards and check whether the error follows the daughter card or the slot. If the message recurs, call your technical support representative for assistance.
Error Message%CBUS-3-DAUGHTER_NO_RSP: Unit [dec], daughter [dec], not responding [hex] - disabledExplanation A hardware component failed an internal diagnostic test. Test output and descriptions of ranges follow.
Unit [dec] (ranges 0-14):
Indicates the Multibus jumper setting for the ciscoBus controller.daughter controller [dec] (ranges 0-3):
Indicates the ciscoBus relative slot number (0 to 3, or in the Cisco 7000, 0 to 4) of the daughter card that failed the test.The daughter card's hardware was recognized across the ciscoBus backplane, but the daughter card did not respond to the first command issued to it.
This condition is a result of one of the following: the daughter card did not reset, or the microcode on the card is in a hung state, or the card cannot fully communicate across the ciscoBus backplane (cannot read or write shared MEMD or does not get the MALU_ATTENTION signal across the ciscoBus).
Recommended Action First, make sure that the daughter card is properly seated in its Multibus and ciscoBus connectors. If this action does not solve the problem, call your technical support representative.
Error Message%CBUS-3-FCICMDFAIL0: Controller [dec], cmd ([dec]) failed (0x%-04x) count ([dec])Explanation A command sent from the system to an interface processor failed to complete successfully.
Recommended Action The system recovered by generating an error code to the requester
Error Message%CBUS-3-FCICMDFAIL1: Controller [dec], cmd ([dec] 0x%-08x) failed (0x%-04x) count ([dec])Explanation A command sent from the system to an interface processor failed to complete successfully.
Recommended Action The system recovered by generating an error code to the requester.
Error Message%CBUS-3-FDDIRSET: Interface [chars], Error ([hex]) [chars] -fddi_reset()%CBUS-3-FDDIRSETU: Unit [dec], Error ([hex]) [chars] - fddi_reset()Explanation A hardware device did not respond appropriately to a request.
Recommended Action Make sure the device is functioning and is configured correctly.
Error Message%CBUS-3-FSIPRSET: Interface [chars], Error ([hex]) [chars] - fsip_reset()Explanation A Fast Serial Interface Processor (FSIP) did not respond to a reset request from the route processor.
Recommended Action Check FSIP electrical connections, cable, and ciscoBus connections. An FSIP microcode reload will be required. If the check of electrical connections reveals no problems and the message recurs, call your technical support representative for assistance.
Error Message%CBUS-3-GHOST; Attempted operation on missing hardware [chars] - [chars]Explanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%CBUS-3-HSSIRSET: Interface [chars], Error ([hex]) [chars] - hssi_reset()%CBUS-3-HSSIRSETU: Unit [dec], Error ([hex]) [chars] - hssi_reset()Explanation A hardware component did not respond to a reset command.
Recommended Action Call your technical support representative for assistance.
Error Message%CBUS-3-INITERR: Interface [dec], Error ([hex]) [chars] - cbus_init()Explanation The switch processor or ciscoBus controller signaled an error while processing a packet or selecting an interface. This indicates a software problem.
Recommended Action Call your technical support representative.
Error Message%CBUS-3-INTR: Interface [dec], idb %08x [dec] [chars] - cbus_interrupt()Explanation The switch processor or ciscoBus controller returned a nonsensical value.
Recommended Action Call your technical support representative.
Error Message%CBUS-4-INTR Interface [dec], [chars] - cbus_interrupt()Explanation A hardware device did not respond appropriately to a request.
Recommended Action Make sure the device is functioning and is configured correctly.
Error Message%CBUS-3-MEC_OUTHUNG: Interface [chars] output hung, [hex], [chars], [chars]Explanation Output hung on a ciscoBus Ethernet interface.
Recommended Action Correct any problems with the Ethernet cable, then manually re-enable the port.
Error Message%CBUS-3-MIPSTAT: Out of buffers--losing status information for the MIP cardExplanation This ERROR results from CPU starvation, typically caused by heavy fast switching activity. The counts displayed for the MultiChannel Interface Processor (MIP) card are incorrect.
Recommended Action Call your technical support representative for assistance.
Error Message%CBUS-3-MODULE: Missing [chars] for [chars]Explanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%CBUS-3-NOBUF, MSG_TRACEBACK, Buffer allocation failure: [chars]Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears and report it to your technical support representative.
Error Message%CBUS-4-NOCOOKIE: [chars]-[dec] controller missing configuration data - disabledExplanation The controller type was derived from a hardware probe. The controller number indicates the ciscoBus relative slot number. The most likely problem is a missing or invalid MAC address cookie ROM. A less likely explanation is corrupted MEMD after the memd self-tests.
Recommended Action Call your technical support representative for assistance. It will be necessary to replace the cookie ROM.
Error Message%CBUS-3-NOMEMORY: No memory for [chars]Explanation The requested operation could not be accomplished because of a low memory condition or an unseated card in the Cisco 7000.
Recommended Action Reduce other system activity to ease memory demands. Confirm that all cards are properly seated. If conditions warrant, upgrade to a larger memory configuration.
Error Message%CBUS-3-OUTHUNG: [chars]: tx%c output hung (%-04x - [chars]), [chars]Explanation A transmission attempt on an interface failed. This can indicate an interface with no cable attached. It can also be an indication of a software problem.
Recommended Action Check for unterminated interfaces. If that is not the problem, call your technical support representative.
Error Message%CBUS-4-OUTHUNG: Interface [chars] output hung, restarting cBus[dec] controller - mci_output()Explanation A ciscoBus controller took too long to respond to a command and was restarted by software.
Recommended Action If this message recurs, call your technical support representative for assistance. You might need to repair or replace the controller.
Error Message%CBUS-3-POLLFAIL: Interface [chars] failed to respond, debug info followsExplanation A Token Ring interface card failed to respond to periodic polling. This can indicate a software or hardware problem.
Recommended Action Copy the debugging information exactly as it appears and report it to your technical support representative. See CBUS-3-POLLFAILDAT for the syntax of this message.
Error Message%CBUS-3-POLLFAILDAT: Int [dec]: %04X %04X %04X %04X %04X %04XExplanation This is the debugging information for the CBUS-3-POLLFAIL error.
Recommended Action Copy the debugging information exactly as it appears and report it to your technical support representative.
Error Message%CBUS-3-PORTTYPE, MSG_TRACEBACK, Unexpected interface type for [chars][dec], port [dec], type [dec]Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears and report it to your technical support representative.
Error Message%CBUS-4-RSETFAIL: Interface [chars] failed to reset properly in [chars], code [hex]Explanation An interface reset command failed. This may be a software or hardware problem.
Explanation Call your technical support representative for assistance.
Error Message%CBUS-3-RESETNXI: Reset of removed interface [hex] ([chars])Explanation An interface reset was attempted on an interface that was removed from the router. This message appears if you use the shutdown command to bring down a removed interface.
Recommended Action Informational message only. No action required.
Error Message%CBUS-3-SELECT: Select error, slot [dec], port [dec], error [dec]Explanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%CBUS-3-TESTFAIL: Unit [dec], failed [chars] test - interface disabledExplanation A hardware component failed an internal diagnostic test.
Recommended Action Check switch settings on the interface cards. Check for proper unit numbers. Reset the cards. Replace the malfunctioning device.
Error Message%CBUS-3-TXALLOC: Error ([hex]) tx_allocate - cbus_init()Explanation A hardware device did not respond appropriately to a request.
Recommended Action Make sure the device is functioning and is configured correctly.
Error Message%CBUS-3-UNKENC: Interface [chars], unknown encaps type [hex], 15*ONESECExplanation A packet was received from the CIP with an unknown encapsulation type. The packet will be dropped.
Recommended Action Call your technical support representative for assistance.
CCP Error Message
Point-to-point Compression Control Protocol error message
Error Message%CCP-4-NOBUF: Interface [chars] [chars]Explanation Compression requested a new data buffer for decompressing into and was refused, due to none being available for this interface.
Recommended Action Use the buffers configuration command to increase the number of buffers available on the interface that this occurred. This should prevent a repeat. An example of the commands you execute follows:
YourBox# YourBox#conf t YourBox(config)# YourBox(config)#buffers bri 0 max-free 12CI Error Messages
Chassis Interface (75xx platform environmental monitor card) error messages
Error Message%CI-3-BLOWER: Blower [dec] failureExplanation One of the router's cooling fans failed.
Recommended Action Replace the fan as soon as possible or the router may shut itself down or fail to operate properly.
Error Message%CI-6-BPLANE: CI type [dec] differs from NVRAM type [dec]Explanation The chassis type as reported by the CI is different from that programmed into NVRAM.
Recommended Action Call your technical support representative for assistance.
Error Message%CI-4-COND: Restarting with [dec] recent soft power failuresExplanation A soft power failure occurs when the router shuts itself down due to a detected over temperature condition.
Recommended Action Call your technical support representative for assistance.
Error Message%CI-3-CTRLRTYPE: Wrong controller type %02xExplanation The CI was manufactured incorrectly.
Recommended Action Call your technical support representative for assistance.
Error Message%CI-2-ENVCRIT: [chars] measured at [chars]Explanation One of the measured environmental test points exceeds an extreme threshold.
Recommended Action Correct the specified condition or the router may shut itself down or fail to operate properly.
Error Message%CI-4-ENVWARN: [chars] measured at [chars]Explanation One of the measured environmental test points exceeds the warning threshold.
Recommended Action Closely monitor the condition and correct if possible. If the situation worsens, call your technical support representative for assistance.
Error Message%CI-2-INT: Unexpected interrupt - status %02xExplanation An unexpected interrupt occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%CI-4-MAXOUTPUT: Power supply [dec] [dec]V is at or near rated outputExplanation The specified power supply is at or near its maximum rated output for the specified voltage.
Recommended Action Closely monitor the situation. Install another power supply, if necessary. If the situation worsens, call your technical support representative for assistance.
Error Message%CI-3-NOACK, MSG_TRACEBACK, [chars] acknowledge failure, cmd %02x, addr %02x, data %02xExplanation The CI software failed to communicate with the CI hardware.
Recommended Action Copy the error message exactly as it appears and report it to your technical support representative.
Error Message%CI-3-NOFORK: Couldn't start environment polling daemonExplanation The CI software failed to initialize properly.
Recommended Action Call your technical support representative for assistance.
Error Message%CI-4-NOTFOUND: Chassis Interface not foundExplanation The system software could not detect the presence of a CI card.
Recommended Action Verify that the CI card is correctly and fully installed in the backplane. If the error recurs, call your technical support representative for assistance.
Error Message%CI-6-PSCHANGE: Power supply [dec] changed from [chars] to [chars]Explanation The CI reported that a power supply was either installed, removed, or changed.
Recommended Action If the situation does not correspond with a physical change in the system's power supplies, call your technical support representative for assistance.
Error Message%CI-3-PSFAIL: Power supply [dec] failureExplanation One of the router's power supplies failed.
Recommended Action Replace the failed power supply as soon as possible.
Error Message%CI-3-SLOTCOMP: Inconsistent slot %02xExplanation The CI software detected a possible inconsistency in the CI hardware.
Recommended Action Confirm that the CI card is correctly and fully installed in the backplane. If error recurs, call your technical support representative for assistance.
Error Message%CI-4-SYSLOAD: System [dec]V load exceeds single power supply [dec] capacityExplanation The measured current load of the system voltage is higher than can be supported by the single power supply.
Recommended Action Call your technical support representative for assistance, especially if non-redundant operation is unacceptable.
Error Message%CI-4-UNBALANCE: Unbalanced [dec]V output from dual power suppliesExplanation The current output at the specified voltage from the two power supplies is significantly different.
Recommended Action Call your technical support representative for assistance.
CIP Error Messages
The system can report error conditions in several facility codes related to the Channel Interface Processor. As shown in the following example, the format of the error messages for the CIP differs slightly from the format of other system error messages:
%CIP3-6-MSG:%ADAPTER-6-DIAGBEGIN: [chars] diagnostic startingAll CIP-related error messages begin with a percent sign (%), the facility code CIP, and a number that indicates the slot where the CIP is installed. The next meaningful information is the facility subcode, severity level, and mnemonic. This part of the error message is preceded by another percent sign, such as %ADAPTER-6-DIAGBEGIN in the above example.
For simplicity, CIP error messages are organized into sections alphabetically by facility subcode beginning with CIP-ADAPTER. Within each CIP section, messages appear alphabetically by mnemonic.
Note
CIP and slot number are not shown in the error message listing that follows.
CIP-ADAPTER Error Messages
CIP error messages for the adapter task
Error Message%ADAPTER-6-DIAGBEGIN: [chars] diagnostic startingExplanation A user used the test cbus command to request a particular adapter diagnostic to be run. This message informs the user that the diagnostic routine started.
Recommended Action Wait for the next message.
Error Message%ADAPTER-0-DIAGDATA: Module Call: [hex] [hex] Error ID: [hex] [hex]Explanation A diagnostic routine detected a failure in the ECA hardware. These codes are used to locate the specific component that failed.
Recommended Action Report this message to your technical support representative.
Error Message%ADAPTER-6-DIAGDATA2: Module Call:[hex] [hex] Error ID: [hex] [hex]Explanation A diagnostic routine detected a failure in the ECA hardware. These codes are used to locate the specific component that failed.
Recommended Action Report this message to your technical support representative.
Error Message%ADAPTER-0-DIAGFAIL: Port [dec] failed the [chars] diagnosticExplanation A diagnostic routine failed. The specified port will not be used.
Recommended Action Report this message to your technical support representative.
Error Message%ADAPTER-6-DIAGFAIL2: [chars] diagnostic failedExplanation A diagnostic requested by the test cbus command failed.
Recommended Action Report this message to your technical support representative.
Error Message%ADAPTER-6-DIAGGOOD2: [chars] diagnostic ran successfullyExplanation A diagnostic requested by the test cbus command completed successfully.
Recommended Action None.
Error Message%ADAPTER-6-DIAGRANGE: Diagnostic number [dec] out of range 0-[dec]Explanation The diagnostic number requested by the test cbus command is not a valid diagnostic number.
Recommended Action Re-enter the command with a valid diagnostic number.
Error Message%ADAPTER-6-DIAGSTOP: Interface must be shutdown to run diagnosticExplanation The test cbus command was used to run a diagnostic on an active interface.
Recommended Action Use the shutdown command to stop the interface and then reissue the diagnostic request.
Error Message%ADAPTER-0-DIAGTERM: Port [dec]: The [chars] diagnostic failed to terminateExplanation A diagnostic routine did not complete execution. The specified port will not be used.
Recommended Action Report this message to your technical support representative.
Error Message%ADAPTER-6-DIAGTERM2:[chars] diagnostic failed to terminateExplanation A diagnostic requested via the test cbus command did not terminate.
Recommended Action Report this message to your technical support representative.
Error Message%ADAPTER-0-LOADFAIL:Port [dec] microcode load failed.Explanation Each adapter has an onboard microprocessor. This message indicates that the operation to load the code for that microprocessor failed.
Recommended Action Report this message to your technical support representative.
Error Message%ADAPTER-6-LOGDATA: [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex]Explanation An error occurred in the adapter. The information displayed will help personnel in software development to determine the nature of the error.
Recommended Action Report this message to your technical support representative.
Error Message%ADAPTER-6-LOGOUT: Port [dec] logout dataExplanation This message is displayed at the start of the logout data. It is then followed by the previous message.
Recommended Action Report this message to your technical support representative.
Error Message%ADAPTER-6-LOGSAME: [hex] to [hex] same as aboveExplanation This message is used when logout information is displayed in order to avoid printing duplicate data.
Recommended Action Report this message to your technical support representative.
Error Message%ADAPTER-6-SCAN: Port [dec] scan dataExplanation The data in this message is scan data for the adapter in the specified port. This data is usually produced as a result of a hardware error.
Recommended Action Report the entire error message and scan data to your technical support representative.
Error Message%ADAPTER-6-SCANDATA: [hex] [hex] [hex] [hex] [hex]Explanation The data in this message is related to a hardware failure of an adapter.
Recommended Action Report the entire error message and scan data to your technical support representative.
Error Message%ADAPTER-0-START_FAIL: Diagnostics failed for port [dec], start request ignored.Explanation Prior to the adapter receiving a start command from the route processor, a set of diagnostics runs. If one of them fails, then the adapter will not be started when the start command is issued.
Recommended Action Report this message to your technical support representative.
Error Message%ADAPTER-6-WRAP: Wrap plug detected in port [dec]. Wrap loop started.Explanation A wrap plug is installed in the specified port. Wrap diagnostics will run until the plug is removed if this is the only adapter or if both adapters have wrap plugs installed.
Recommended Action Remove the wrap plug and connect the interface to a channel.
Error Message%ADAPTER-6-WRAPSTOP1: Wrap plug removed from port [dec]. Wrap loop ended.Explanation The wrap plug was removed, causing the wrap diagnostics to terminate.
Recommended Action No action is required.
Error Message%ADAPTER-6-WRAPSTOP2: Port [dec] active. Port [dec] wrap loop ended.Explanation The wrap diagnostics have been terminated because the other adapter is active.
Recommended Action Remove the wrap plug and connect the interface to a channel if you wish to use this adapter. Otherwise, no action is required.
CIP-BSQ Error Messages
CIP error messages for buffer status queue processing
Error Message%BSQ-0-SCB_CHAIN: Read SCB chain is out of sequenceExplanation The sequence of buffer status queue entries received for read commands does not match the sequence of the storage control blocks used for the reads. This is a fatal internal logic error.
Recommended Action Report this message to your technical support representative.
Error Message%BSQ-0-TOOMANY: More than 16 buffers queued for one channel commandExplanation Either an attempt was made to transfer more data in a single channel command word than the CIP can handle, or an internal error occurred. This is a fatal internal logic error.
Recommended Action Report this message to your technical support representative.
CIP-CBUS_ATTN Error Message
CIP error messages relating to the CBUS_ATTN routine, the facility that receives configuration requests and gathers statistics
Error Message%CBUS_ATTN-3-BADADDR:Bad memory address [hex] requestedExplanation The RP requested the CIP to store a configuration command at an invalid memory address. The CIP recovered by ignoring the request.
Recommended Action Report this error to your technical support representative.
CIP-CBUS_WRITE Error Messages
CIP error messages for the CBUS_WRITE facility, which is used by the Enhanced Online Insertions Removal (EOIR) support on the CIP to track writes to MEMD and reissue them if a cBus problem occurs.
Error Message%CBUS_WRITE-3-BADTYPE: Invalid write type [dec]Explanation The type parameter in the write tracking table is invalid. This is an internal CIP logic error. The CIP recovered by ignoring the entry.
Recommended Action Report this error to your technical support representative.
Error Message% CBUS_WRITE-3-INVALID: Valid bit not set in IO exception register [hex]Explanation A write error interrupt occurred, but the hardware that keeps track of the address of the error does not have a valid address.
Recommended Action Report this error to your technical support representative.
Error Message%CBUS_WRITE-3-MISSING: Entry for address [hex] not foundExplanation A write error was detected, but there was no corresponding entry in the table that keeps track of these entries. This is an internal CIP logic error. The CIP recovered by ignoring the write error.
Recommended Action Report this error to your technical support representative.
Error Message%CBUS_WRITE-3-STACK: [dec] [dec] [hex] [hex] [hex]Explanation This is a debugging print of the CBUS write stack. It is associated with the CBUS_WRITE-3-MISSING error message.
Recommended Action Report this error to your technical support representative.
Error Message%CBUS_WRITE-3-UNEXPECTED: Unexpected IO write error.Address=[hex]Explanation A write operation to an address other than MEMD timed out. This is probably a hardware problem. The CIP failed and attempted to restart.
Recommended Action Record the address indicated in the error message. The address will enable a support representative to determine which component to replace. Report this error to your technical support representative.
CIP-CCA Error Messages
CIP error messages for channel card adapter processing
Error Message%CCA-3-ACR: Accept command response status receivedExplanation The adapter notified the CIP that an accept command response was issued. The CIP does not request notification of accept command response messages. Therefore, this message means the adapter generated an unexpected message.
Recommended Action Normal processing will resume, but it is useful for software development personnel to know that this message occurred. Report this message to your technical support representative.
Error Message%CCA-0-BADCCA: Undefined CCA code received CCA=[hex] [hex]Explanation The adapter presented the CIP with a message using an undefined code point. This is a fatal internal logic error.
Recommended Action Report this message to your technical support representative.
Error Message%CCA-0-BSQ_FULL: Buffer status queue is fullExplanation The adapter notified the CIP that the buffer status queue was full. The CIP never provides enough buffers to the adapter to cause the buffer status queue to become full. This is a fatal internal logic error.
Recommended Action Report this message to your technical support representative.
Error Message%CCA-3-BYPASS: Select bypass switch is in bypass position for port [dec]Explanation A user attempted to start the PCA with the select bypass switch in the BYPASS position. The PCA cannot go on-line with the switch in the bypass position.
Recommended Action Move the select bypass switch on the PCA-Y cable from the bypass position to the SELECT position.
Error Message%CCA-3-CANCEL1: Invalid cancel code [hex]Explanation The adapter notified the CIP that a halt subchannel command was issued by the host, but provided the CIP with an undefined type of cancel.
Recommended Action The CIP will recover but software development personnel should be informed. Report this message to your technical support representative.
Error Message%CCA-3-CANCEL2: Cancel received for undefined path [hex]Explanation The adapter notified the CIP that a halt subchannel command was issued by the host for an undefined path. This is an internal logic error.
Recommended Action The CIP software recovered but software development personnel need to know the problem. Report this message to your technical support representative.
Error Message%CCA-3-COMMAND_PATH: Command connection received for undefined path [hex]Explanation The adapter notified the CIP that a start subchannel command was issued by the host for an undefined path. This is an internal logic error.
Recommended Action The CIP software recovered, but software development personnel need to know the problem. Report this message to your technical support representative.
Error Message%CCA-3-CONN_RESULT: Connection result for device [hex] [hex] expected [hex] [hex]Explanation The adapter notified the CIP that a connection was established for a device other than the one that the CIP had just requested. This is an internal logic error.
Recommended Action The CIP software recovered, but software development personnel need to know the problem. Report this message to your technical support representative.
Error Message%CCA-0-DEV_ERR1: Undefined device error type [hex]Explanation When a device error occurs, the adapter specifies the type of error so that the correct recovery action can be performed. The type specified is not defined. This is a fatal internal logic error.
Recommended Action Report this message to your technical support representative.
Error Message%CCA-0-DEV_ERR2: Device error but no active defined deviceExplanation A device error was generated, and either it occurred while status was being presented but no device was active, or it occurred for an undefined device. This is a fatal internal logic error.
Recommended Action Report this message to your technical support representative.
Error Message%CCA-0-DEV_ERR3: Device error received for undefined path [hex]Explanation A device error occurred, but the path specified in the device error message is not defined. This is a fatal internal logic error.
Recommended Action Report this message to your technical support representative.
Error Message%CCA-3-END_STATUS: Ending status interrupt received for [hex] CCWExplanation The adapter reported an ending status interrupt for a channel command word that should not have caused the CIP to be notified. This is an internal logic error.
Recommended Action The CIP recovered, but software development personnel should be notified of the problem. Report this message to your technical support representative.
Error Message%CCA-3-LOGOUT: Invalid logout command modifier [hex]Explanation The adapter sent a request to the CIP to perform a logout, but the command modifier in the message was not a valid value. This is an internal logic error.
Recommended Action The CIP recovered, but software development personnel should be notified of the problem. Report this message to your technical support representative.
Error Message%CCA-3-REQUEST_STATUS: Request status received for undefined path [hex]Explanation The adapter requested the CIP to present status for an undefined path. This is an internal logic error.
Recommended Action The CIP recovered, but software development personnel should be notified of the problem. Report this message to your technical support representative.
Error Message%CCA-3-RESET_PATH: Reset received for undefined path [hexExplanation The adapter requested the CIP to perform reset processing for an undefined path. This is an internal logic error.
Recommended Action The CIP recovered, but software development personnel should be notified of the problem. Report this message to your technical support representative.
Error Message%CCA-3-RLP1: Invalid rlp flags [hex]Explanation The adapter requested the CIP to reset a logical path, but the flags on the reset request were not valid. This is an internal logic error.
Recommended Action The CIP recovered, but software development personnel should be notified of the problem. Report this message to your technical support representative.
Error Message%CCA-3-RLP2: RLP received for undefined path [hex]Explanation The adapter requested the CIP to reset an undefined logical path. This is an internal logic error.
Recommended Action The CIP recovered, but software development personnel should be notified of the problem. Report this message to your technical support representative.
Error Message%CCA-0-SCBNRDY: Unexpected SCB not ready CCA = [hex] [hex]Explanation The CIP was notified that an I/O operation was attempted with a storage control block that was marked as not ready. The specified I/O operation should never have a not-ready storage control block. This is a fatal internal logic error.
Recommended Action Report this message to your technical support representative.
Error Message%CCA-3-SEL_RESET1: Invalid selective reset code [hex]Explanation The adapter requested that the CIP perform a selective reset, but the request code in the message was not a valid value. This is an internal logic error.
Recommended Action The CIP recovered, but software development personnel should be notified of the problem. Report this message to your technical support representative.
Error Message%CCA-3-SEL_RESET2: Selective reset received for undefined path [hex]Explanation The adapter requested the CIP to perform a selective reset on an undefined logical path. This is an internal logic error.
Recommended Action The CIP recovered, but software development personnel should be notified of the problem. Report this message to your technical support representative.
Error Message%CCA-3-STATUS_NOTICE: Undefined status notice request code [hex]Explanation The adapter notified the CIP that status was accepted by the channel, but the request code in the status message was not a valid code. This is an internal logic error.
Recommended Action The CIP recovered, but software development personnel should be notified of the problem. Report this message to your technical support representative.
Error Message%CCA-3-SYS_RESET: Invalid system reset code [hex]Explanation The adapter requested that the CIP perform a system reset, but the request code in the message was not a valid value. This is an internal logic error.
Recommended Action The CIP recovered, but software development personnel should be notified of the problem. Report this message to your technical support representative.
Error Message%CCA-3-WRAPPLUG: Wrap plug is installed on port [dec]Explanation The wrap plug is installed on the PCA in the specified port. The PCA can not be used unless connected to a channel.
Recommended Action Remove the wrap plug and connect the channel cables.
Error Message%CCA-0-WRITE_FAIL: Write of response CCA failedExplanation The adapter requested the CIP to perform a request. When the CIP tried to present the response to the request, it could not write to the common communication area. This is a fatal internal logic error.
Recommended Action Report this message to your technical support representative.
CIP-CLAW Error Messages
CIP error messages related to the Common Link Access for Workstations (CLAW) facility
Error Message%CLAW-0-BADHAPPL: Host appl. names do not match. Host is [chars]. Control Unit is [chars]Explanation An attempt was made to establish a connection, but the host application name specified on the host does not match the host application name specified in the router configuration.
Recommended Action Correct the host and/or router configuration.
Error Message%CLAW-0-BADHNAME: Host system names do not match.Host is [chars]. Control Unit is [chars].Explanation During the system validate processing, the host name configured in the router did not match the host name configured on the host.
Recommended Action Correct the host and/or router configuration.
Error Message%CLAW-0-BADRSIZE: Host read frame size of [dec] is less than Control Unit size of [dec].Explanation The host is configured to receive frames that are smaller than the CIP is designed to send. The CIP notified the host of the problem.
Recommended Action Reconfigure the frame size on the host to be 4096 or larger.
Error Message%CLAW-6-BADSVR: System Validate Response had a return code of [dec]Explanation The host generated a bad return code in the response to the system validate request sent by the CIP.
Recommended Action Check the return code and correct the configuration as appropriate.
Error Message%CLAW-0-BADVERSION: Host CLAW version [dec] does not equal control unit version [dec]Explanation The version specified in a message from the host is not the same as the version specified in the CIP.
Recommended Action Report this error to your technical support representative.
Error Message%CLAW-0-BADWAPPL: Workstation appl. names do not match.Host is [chars]. Control Unit is [chars].Explanation An attempt was made to establish a connection, but the work station application name specified on the host does not match the work station application name specified in the router configuration.
Recommended Action Correct the host and/or router configuration.
Error Message%CLAW-0-BADWNAME: Workstation system names do not match.Host is [chars]. Control Unit is [chars].Explanation During the system validate processing, the work station name configured in the router did not match the work station name configured on the host.
Recommended Action Correct the host and/or router configuration.
Error Message%CLAW-0-BADWSIZE: Host write frame size of [dec] is greater than Control Unit size of [dec]Explanation The host is configured to write more data in a single frame to the CIP than the CIP is designed to receive. The CIP notified the host of the problem.
Recommended Action Reconfigure the frame size on the host to be 4096 or smaller.
Error Message%CLAW-6-COMMAND: Unrecognized CLAW command code [dec].xfer_element = [hex]Explanation The host sent a CLAW command with an invalid CLAW command code. The CIP ignored the request.
Recommended Action Report this error to your technical support representative.
Error Message%CLAW-6-NOCONN: Channel wrote data on link [dec] without a valid connection. Path=[hex] device=[hex]Explanation A packet was received from the host but the logical link specified with the data does not represent a valid connection. The packet was dropped.
Recommended Action Report this error to your technical support representative.
Error Message%CLAW-0-NOLINKID: Unable to allocate link id.Explanation An attempt was made to allocate a link ID to assign to a connection request, but all link IDs were in use. The CIP recovered by generating a bad return code to the requester.
Recommended Action Report this error to your technical support representative.
Error Message%CLAW-6-NOTPRESENT: Link [dec] being freed was not presentExplanation The host software attempted to disconnect a link that was not established. The CIP ignored the request.
Recommended Action Report this error to your technical support representative.
Error Message%CLAW-6-NOTXBUF: Unable to allocate txbufExplanation No available transmit buffers exist, but the CLAW connection did not reach its transmit buffer limit. The packet was dropped.
Recommended Action Report this error to your technical support representative.
Error Message%CLAW-6-RANGE: Link [dec] being freed is out of rangeExplanation The link ID in a disconnect is not in the valid range for all CLAW links. The CIP recovered by ignoring this request.
Recommended Action Report this error to your technical support representative.
Error Message%CLAW-6-TYPE: Unrecognized type code [dec]in CLAW. xfer_element = [hex]Explanation The request type in a transfer element is not a valid value. This is an internal logic error. The CIP recovered by ignoring the transfer element.
Recommended Action Report this error to your technical support representative.
Error Message%CLAW-6-UNEXPECTED: Unexpected type code [dec] in CLAW. xfer_element = [hex]Explanation The request type in a transfer element is valid but is not expected to occur at this time. This is an internal logic error. The CIP recovered by ignoring the transfer element.
Recommended Action Report this error to your technical support representative.
CIP-CONFIG Error Messages
CIP error messages related to the configuration facility
Error Message%CONFIG-6-BAD_DBTYPE: Bad port type [dec]Explanation The port type function returned an invalid port type. This is an internal logic error.
Recommended Action Report this message to your technical support representative.
Error Message%CONFIG-6-BADCONFIG: Bad configuration type [dec] in update_tx_maxExplanation The router encountered an unrecognized configuration type when it attempted to update the maximum number of transmit buffers to be used by a device. This is an internal logic error.
Recommended Action Report this message to your technical support representative.
Error Message%CONFIG-6-BADDEVT: Bad device type [dec]Explanation The device type specified by the route processor in a configuration request is not a valid device type. This is an internal logic error. The configuration request was ignored.
Recommended Action Report this message to your technical support representative.
Error Message%CONFIG-0-BADSPEED: Incorrect PCA speed passed to cbus attention exit routine.Explanation The router attempted to configure a PCA adapter with an invalid channel speed.
Recommended Action The CIP recovered by ignoring the request. Report this error to your technical support representative.
Error Message%CONFIG-3-BADVCN: Virtual circuit number [dec] too largeExplanation The virtual circuit number specified by the route processor on a configuration request is too large. This is an internal logic error. The configuration request was ignored.
Recommended Action Report this message to your technical support representative.
Error Message%CONFIG-3-BADVCN2: Bad vcn [dec] ([hex]), port adapter [dec].Explanation A packet was queued for the CIP with an invalid virtual circuit number.
Recommended Action The CIP recovered by dropping the packet. Report this error to your technical support representative.
Error Message%CONFIG-3-CLAWDEV: CLAW device address ([hex]) must be evenExplanation The route processor attempted to configure an odd address for a CLAW device. CLAW configuration requests must specify an even address. This is an internal logic error. The configuration request was ignored.
Recommended Action Report this message to your technical support representative.
Error Message%CONFIG-3-DIFFDEVT: Device type [dec] does not match device [hex] device type [dec]Explanation The route processor attempted to reconfigure an existing device without first removing the device. This is an internal logic error. The original configuration remains.
Recommended Action Report this message to your technical support representative.
Error Message%CONFIG-3-DUPDEV: Duplicate device address ([hex])Explanation The route processor attempted to configure an existing device. This is an internal logic error. The configuration request was ignored.
Recommended Action Report this message to your technical support representative.
Error Message%CONFIG-3-DUPVCN: Virtual circuit number already in use. Path = [hex] [hex] [hex] Device = [hex]Explanation The route processor attempted to configure a device using a virtual circuit number that was already in use by another device. This is an internal logic error. The configuration request was ignored.
Recommended Action Report this message to your technical support representative.
Error Message%CONFIG-3-NOAPPLESPC: Error allocating storage for application blockExplanation The CIP does not have sufficient storage to allocate an application block. The configuration request was ignored.
Recommended Action Purchase the next larger storage size for the CIP or configure fewer devices.
Error Message%CONFIG-3-NOCUI: Control unit image does not exist for [hex] [hex] [hex]Explanation The route processor attempted to unconfigure a device, but the control unit image for the device could not be located. This is an internal logic error. The unconfigure request was ignored.
Recommended Action Report this message to your technical support representative.
Error Message%CONFIG-3-NODEV: Device [hex] is not defined.Explanation The route processor attempted to unconfigure a device, but the device was not defined. This is an internal logic error. The unconfigure request was ignored.
Recommended Action Report this message to your technical support representative.
Error Message%CONFIG-3-NODEVSPC: Error allocating storage for device blockExplanation No storage was available for the device block. The configuration request is ignored.
Recommended Action Purchase the next larger storage size for the CIP or configure fewer devices.
Error Message%CONFIG-3-NOFREEPATH: No free paths - only 64 may be specifiedExplanation An attempt was made to configure more than 64 different paths. Only 64 paths are supported. The configuration request was ignored.
Recommended Action Configure fewer paths.
Error Message%CONFIG-3-NOPATHSPC: Error allocating storage for logical path tableExplanation No storage was available for the logical path table. The configuration request was ignored.
Recommended Action Purchase the next larger storage size for the CIP or configure fewer devices.
Error Message%CONFIG-3-NOVCN: Virtual circuit number [dec] is not definedExplanation The route processor attempted to unconfigure a device, but the virtual circuit number for the device is not defined. This is an internal logic error. The unconfigure request was ignored.
Recommended Action Report this message to your technical support representative.
Error Message%CONFIG-3-TOOMANYDEV: Too many devices defined. Only 256 may be used.Explanation An attempt was made to define more than 256 devices. Only 256 devices are supported on an adapter. The configuration request was ignored.
Recommended Action Configure fewer devices.
Error Message%CONFIG-3-WORKLEFT: Work pending on work queue when device terminated.Explanation Work was pending when the router finished processing an unconfigure request. This is an internal logic error.
Recommended Action Report this message to your technical support representative.
Error Message%CONFIG-3-WRONGINT: VCN [dec] ([hex]) not for port adapter [dec].Explanation A packet was queued for the CIP with a valid virtual circuit number, but the virtual circuit number is associated with the other port adapter.
Recommended Action The CIP recovered by dropping the packet. Report this error to your technical support representative.
CIP-DIAG Error Message
CIP error message for diagnostic processing
Error Message%DIAG-6-BADCODE: Invalid request code [dec] to run_diagExplanation A request was made to run an ESCON Channel Adapter (ECA) diagnostic, but the number of the diagnostic to run was not valid. This is an internal logic error. The request to run the diagnostic is ignored.
Recommended Action Report this message to your technical support representative.
CIP-DMA Error Messages
Error messages for the function on the CIP that is responsible for transferring data between the DRAM on the CIP and MEMD
Error Message%DMA-3-CBUSERR: CBUS error (no ACK neither NACK) [hex]Explanation The cBus controller started a read or write operation and did not receive a response from the CBUS indicating the completion status. The packet was dropped.
Recommended Action Report this error to your technical support representative.
Error Message%DMA-3-CBUSPARITY: CBUS parity error [hex]Explanation A parity error was detected on the cBus during a data transfer. The packet was dropped.
Recommended Action Report this error to your technical support representative.
Error Message%DMA-4-DATAPARITY: DMA Data FPGA parity error [hex]Explanation A parity error was detected during data transfer. The packet was dropped.
Recommended Action Report this error to your technical support representative.
Error Message%DMA-0-INCOMPL: DMA transfer incomplete on interruptExplanation The CIP was notified that the current DMA transfer had completed, but the DMA status register indicated the transfer was still in progress. The CIP restarted.
Recommended Action Report this error to your technical support representative.
Error Message%DMA-3-LOGICERR:CBUS timeout (10 us) [hex]Explanation The CBUS did not respond to the DMA controller within 10 microseconds (10µs). The packet was dropped.
Recommended Action Report this error to your technical support representative.
Error Message%DMA-0-NOXFER: No transfer pending on DMA interruptExplanation A DMA interrupt occurred, but no transfer was pending. This is either an internal logic error or a hardware failure. The CIP restarted.
Recommended Action Report this error to your technical support representative.
CIP-GET_DATA Error Message
CIP error messages related to the internal routine for allocating transfer elements
Error Message%GET_DATA-0-NOMEMORY: Can not allocate storage for xfer elementsExplanation An attempt was made to allocate a transfer element and no storage was available. This is a fatal error. The CIP restarted.
Recommended Action Report this error to your technical support representative.
CIP-INT Error Messages
CIP error messages for the interrupt handler interface
Error Message%INT-0-ADDFAST: Add: Invalid fast io code [dec]Explanation A request was made to add an interrupt handler to the fast I/O path with an invalid interrupt type. This is a fatal internal logic error.
Recommended Action Report this error to customer engineering.
Error Message%INT-0-ADDFLIH: Add: Invalid interrupt code [dec]Explanation A request was made to add an interrupt handler with an invalid interrupt number. This is a fatal internal logic error.
Recommended Action Report this error to customer engineering.
Error Message%INT-0-ADDFULL:Add: Invalid full io code [dec]Explanation A request was made to add an I/O interrupt handler with an invalid interrupt code. This is a fatal internal logic error.
Recommended Action Report this error to customer engineering.
Error Message%INT-0-ADDTRAP: Add: Invalid trap code [dec]Explanation A request was made to add a system call handler with an invalid system call number. This is a fatal internal logic error.
Recommended Action Report this error to customer engineering.
Error Message%INT-0-REMOVEFAST: Remove: Invalid fast io code [dec]Explanation A request was made to remove an interrupt handler from the fast I/O path with an invalid interrupt type. This is a fatal internal logic error.
Recommended Action Report this error to customer engineering.
Error Message%INT-0-REMOVEFLIH: Remove: Invalid interrupt code [dec]Explanation A request was made to remove an interrupt handler with an invalid interrupt number. This is a fatal internal logic error.
Recommended Action Report this error to customer engineering.
Error Message%INT-0-REMOVEFULL: Remove: Invalid full io code [dec]Explanation A request was made to remove an I/O interrupt handler with an invalid interrupt code. This is a fatal internal logic error.
Recommended Action Report this error to customer engineering.
Error Message%INT-0-REMOVETRAP: Remove: Invalid trap code [dec]Explanation A request was made to add a system call handler with an invalid system call number. This is a fatal internal logic error.
Recommended Action Report this error to customer engineering.
CIP-LOVE Error Message
CIP error messages related to the mechanism that sends statistics from the CIP to the router.
Error Message%LOVE-3-LOVELETTER: Error in love letter processingExplanation An attempt was made to transfer statistics to the Route Processor (RP). The DMA routines returned the wrong transfer request. The CIP recovered.
Recommended Action Report this error to your technical support representative.
CIP-MEMD Error Message
CIP error message related to the MEMD facility
Error Message%MEMD-3-BADVCN: Bad vcn [dec] ([hex]), daughter board [dec]Explanation A packet was queued to the CIP and the virtual circuit associated with the packet is not valid. The CIP dropped the packet.
Recommended Action Report this error to your technical support representative.
CIP-NEVADA Error Messages
Error messages related to the CIP interrupt controller
Error Message%NEVADA-0-BADADD: Add: Invalid nevada interrupt code[dec]Explanation An attempt was made to specify an interrupt handler for an invalid interrupt type on the nevada interrupt control chip. This is a fatal internal logic error.
Recommended Action Report this error to your technical support representative.
Error Message%NEVADA-0-BADDISABLE: Disable: Invalid nevada interrupt code [dec]Explanation An attempt was made to disable an invalid interrupt type on the nevada interrupt control chip. This is a fatal internal logic error.
Recommended Action Report this error to your technical support representative.
Error Message%NEVADA-0-BADENABLE: Enable: Invalid nevada interrupt code [dec]Explanation An attempt was made to enable an invalid interrupt type on the nevada interrupt control chip. This is a fatal internal logic error.
Recommended Action Report this error to your technical support representative.
Error Message%NEVADA-0-BADENABLE2: Enable: No interrupt routine for code [dec]Explanation An attempt was made to enable an interrupt routine on the nevada interrupt control chip, but there was not interrupt routine specified. This is a fatal internal logic error.
Recommended Action Report this error to your technical support representative.
Error Message%NEVADA-0-BADINT: Interrupt received with no interrupt routine definedExplanation An interrupt was received for a code with no interrupt handler defined. This is a fatal internal logic error.
Recommended Action Report this error to your technical support representative.
Error Message%NEVADA-0-BADREMOVE: Remove: Invalid nevada interrupt code [dec]Explanation An attempt was made to remove an interrupt handler for an invalid interrupt type on the nevada interrupt control chip. This is a fatal internal logic error.
Recommended Action Report this error to your technical support representative.
CIP-SCB Error Message
CIP error messages related to the storage control block
Error Message%SCB-6-BADSCB: Request to free SCB 0 ignoredExplanation An attempt was made to free SCB 0. This is an internal logic error. The request was ignored.
Recommended Action Report this message to your technical support representative.
CIP-SCHED Error Messages
Error messages related to the scheduler, the facility responsible for determining which process to run at a given time on the CIP
Error Message%SCHED-0-BADPRIORITY: Task priority of [dec] is not allowedExplanation A request was made to create a process, but the priority for the process was not valid. The process was not created.
Recommended Action Report this error to your technical support representative.
Error Message%SCHED-0-INVLOCK1: Invalid lock word of [dec] used in lock requestExplanation An attempt was made to request a lock, but the lock word contained invalid data. This is a fatal internal logic error.
Recommended Action Report this error to your technical support representative.
Error Message%SCHED-0-INVLOCK2: Invalid lock word of [dec] used in unlock requestExplanation An attempt was made to unlock a lock, but the data in the lock word was not valid. This is a fatal internal logic error.
Recommended Action Report this error to your technical support representative.
Error Message%SCHED-0-NMLDATA: tcb_addr = [hex] current_tcb = 0x%8x lock_value = [dec]);Explanation This message contains data that relates to the SCHED-0-NOTMYLOCK message.
Recommended Action Report this error to your technical support representative.
Error Message%SCHED-0-NOLOCK: Attempt was made to unlock resource that wasn't lockedExplanation An attempt was made to unlock a lock that was not held. This is a fatal internal logic error.
Recommended Action Report this error to your technical support representative.
Error Message%SCHED-0-NOPROCID: No process id available for task creationExplanation An attempt was made to create more tasks than the CIP is designed to allow. The process was not created.
Recommended Action Report this error to your technical support representative.
Error Message%SCHED-0-NOSTACK: Could not allocate [dec] bytes for stack from SRAMExplanation An attempt was made to create a process and there was not sufficient storage available to contain the stack for the process. The process was not created.
Recommended Action Report this error to your technical support representative.
Error Message%SCHED-0-NOTCB: Could not allocate [dec] bytes for tcb from SRAMExplanation An attempt was made to create a process and there was not sufficient storage available to contain the control block for the process. The process was not created.
Recommended Action Report this error to your technical support representative.
Error Message%SCHED-0-NOTMYLOCK: Attempt was made to unlock another tasks resourceExplanation An attempt was made to unlock a lock that was set by another task. This is a fatal internal logic error.
Recommended Action Report this error to your technical support representative.
Error Message%SCHED-2-SEMUNLOCK: [chars] attempted to unlock semaphore owned by [chars], 30*ONESECExplanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
CIP-SLC Error Messages
CIP error messages related to the serial link controller
Error Message%SLC-3-SCANEP1: Scan of EP ring 1 failedExplanation An attempt to scan the first set of internal latches on the ESCON processor failed.
Recommended Action Report this message to your technical support representative.
Error Message%SLC-3-SCANEP2: Scan of EP ring 2 failedExplanation An attempt to scan the second set of internal latches on the ESCON processor failed.
Recommended Action Report this message to your technical support representative.
Error Message%SLC-3-SCANSLC: Scan of SLC ring failedExplanation An attempt to scan the internal latches of the serial link controller failed.
Recommended Action Report this message to your technical support representative.
Error Message%SLC-3-STOPBIDITO: Stop BIDI clock timed outExplanation An attempt was made to stop the clock on the interface between the Enterprise Systems Connection (ESCON) processor and the serial link controller. The serial link controller did not indicate that the clock was stopped.
Recommended Action Report this message to your technical support representative.
Error Message%SLC-3-STOPEPTO: Stop EP clock timed outExplanation An attempt was made to stop the clock on the ESCON processor. The serial link controller did not indicate that the clock was stopped. The CIP attempted to stop the BIDI clock.
Recommended Action Report this message to your technical support representative.
CLEAR Error Message
Clear error message
Error Message%CLEAR-5-COUNTERS: Clear counter on [chars] [chars] by [chars]Explanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
CLNS Error Messages
OSI Connectionless Network Service error messages
Error Message%CLNS-4-AREALOST: Too many IS-IS areas--can't route to area [chars]Explanation Intermediate System-to-Intermediate system (IS-IS) allows only three area addresses per area. Multiple routers with at least one area address in common merge all of their configured area addresses into a single set. If the resulting set more than three area addresses, this message appears and indicates that there will be a loss of connectivity to the specified area.
Recommended Action Reconfigure the network so that the area has fewer area addresses, or split the area into multiple areas.
Error Message%CLNS-4-BADPACKET: [chars]: [chars], [chars] from [chars] ([chars]), MSGDEF_LIMIT_SLOWExplanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%CLNS-4-CKSUMERR: [chars]: L[dec] LSP [chars] database checksum error, restarting, MSGDEF_LIMIT_SLOWExplanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%CLNS-4-EDATFAIL: Encapsulation failed, dst= [chars]%CLNS-4-EESHFAIL: Interface [chars], encapsulation of ESH failed, HLEN [dec]Explanation Either message can occur when an interface is down and a static neighbor entry exists in the system's CLNS routing table. If this is not the case, the message indicates an internal software error.
Recommended Action Check the interface. If the interface is not down and no static neighbor entry exists for that interface, call your technical support representative for assistance.
Error Message%CLNS-4-LSPFULL: [chars]: L[dec] LSP filled to capacity, dropping routes, 10*ONEMINExplanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%CLNS-4-LSPTOOBIG: [chars]: L[dec] LSP [chars] size [dec] bigger than interface [chars] MTU [dec], LSP dropped, 10*ONEMINExplanation A software or hardware error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%CLNS-3-NSAPES: Invalid NSAP type in ES table: [hex] for [chars]%CLNS-4-NSAPIS: Invalid NSAP type in IS table: [hex] [dec]%CLNS-4-REDIRECT: Redirect found for non-route entry, dst= [chars], next-hop= [chars]Explanation An internal software error occurred.
Recommended Action If the message recurs, call your technical support representative for assistance.
CLS Error Message
Cisco Link Services error message
Error Message%CLS-3-CLSFAIL, MSG_TRACEBACK, CLS: Assertion failed: [chars], MSGDEF_LIMIT_FASTExplanation A software or hardware error occurred.
Recommended Action Call your technical support representative for assistance.
CLSDR Error Messages
Cisco Link Services Driver error messages
Error Message%CLSDR-3-ERRRTN: [chars] failed error 0x[hex]Explanation An error was returned from Cisco Link Services I (CLSI) to the destination logical unit (DLU) because CLSI did not perform the action desired by the DLU.
Recommended Action Refer to CLSI software documentation for more information about this error. Report this error to your technical support representative.
Error Message%CLSDR-3-INCORRECTPORT: Incorrect port pointer in USapIdExplanation Cisco Link Services I (CLSI) returned an incorrect port pointer in the USapID.
Recommended Action Report this error to your technical support representative.
Error Message%CLSDR-3-MSGERR: [chars] couldn't get a messageExplanation The destination logical unit (DLU) could not send a correct message to Cisco Link Services I (CLSI) because the message was formed incorrectly. CLSI will not perform the desired action.
Recommended Action Report this error to your technical support representative.
Error Message%CLSDR-3-NOCLSSERVER: unable to start the Server processExplanation Could not start the CLSDRIVER process, possibly due to a resource problem. The subsystem using CLSDRIVER does not work.
Recommended Action Remove and then restore the destination logical unit (DLU) in the configuration file and try and reboot the system. Report this error to your technical support representative.
Error Message%CLSDR-3-NODLUCREATE: Cannot create DLU for this type [dec]Explanation The CLSDRIVER does not understand the destination logical unit (DLU) type. Currently, only STUN uses the CLSDRIVER. Any other value results in an error.
Recommended Action Make note of all details associated with this error message and report them to your technical support representative.
Error Message%CLSDR-3-NOINIT: CLSDRIVER not initializedExplanation A CLSDRIVER initialization failed earlier. Trying to use the driver now results in an error condition.
Recommended Action Remove and then restore the destination logical unit (DLU) in the configuration file and try and reboot the system. Report this error to your technical support representative.
Error Message%CLSDR-3-NOPORTCREATE: Cannot create PORT structureExplanation The CLSDRIVER cannot enable this port for processing.
Recommended Action Try rebooting the router. Report this error to your technical support representative.
Error Message%CLSDR-3-NOREMOVECEP: RemoveCep : Cep 0x[hex] not on listExplanation The destination logical unit (DLU) is trying to remove a non-existent connection end point from the internal data structure. This creates a problem in the connection end point (CEP) maintenance logic.
Recommended Action Report this error to your technical support representative.
Error Message%CLSDR-3-NOREMOVEPORT: RemovePort: port 0x[hex] not on listExplanation The destination logical unit (DLU) is trying to remove an non-existent port from the list of active ports because it does not have the correct list of active ports.
Recommended Action Report this error to your technical support representative.
Error Message%CLSDR-3-WRONGMSG: Should never be here, cls message type unknownExplanation The CLS message type is unknown to the destination logical unit (DLU).
Recommended Action Report this error to your technical support representative.
COMP Error Messages
Compression error messages
Error Message%COMP-3-CONFIGBAD: Interface [chars] Compression internal configuration errorExplanation An internal software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%COMP-5-NOBUF: Interface [chars] [chars]Explanation Interface serial0 compression getbuffer failed, causing Link Access Procedures, Balanced (LAPB) retransmissions.
Recommended Action Configure additional large and big buffers.
Error Message%COMP-3-NOMEMORY: No memory to decompress packet on interface [chars]Explanation The router is attempting to decompress an incoming packet, but no memory is available for the decompression. The packet will be dropped. The rare occurrence of this message should not be of great concern.
Recommended Action These actions can help to rectify this condition:
•
•
•
•
Error Message%COMP-3-SIZEBAD: Interface [chars] Decompression size error%COMP-3-SYNCBAD: Interface [chars] Decompression sync error%COMP-3-VERSIONBAD: Interface [chars] Compression Version mismatch expected [hex] received [hex]Explanation One interface is configured for predictor compression, the other is not.
Recommended Action Configure both interfaces for predictor compression.
CONTROLLER Error Messages
Controller error messages
Error Message%CONTROLLER-2-CRASHED: Interface Processor in slot [dec] not responding [hex]: shutting it downExplanation A controller stopped responding to commands over the cBus, so it was put into shutdown mode.
Recommended Action Re-enable the controllers by issuing the no shut configuration command on all controllers on the card, or hotswap out the bad card and install the new one. You must still manually "no shut" the controllers.
Error Message%CONTROLLER-2-NOTFOUND: Controller not found for slot [dec].Explanation An internal software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%CONTROLLER-3-REMLOOP: Controller [chars], remote loop [chars] [chars]Explanation A configurable controller entered remote loopback.
Recommended Action No action required.
Error Message%CONTROLLER-3-UPDOWN: Controller [chars] changed state to [chars]Explanation A configurable controller changed its state.
Recommended Action No action required.
CSC2 Error Message
CPU card error message
Error Message%CSC2-4-BREAK: AUX port hung because 'Transmit Break' would not clearExplanation The Universal Asynchronous Receiver/Transmitter (UART) in the console serial interface is malfunctioning.
Recommended Action Service the console serial port hardware.
DBUS Error Messages
dBus error messages
Error Message%DBUS-3-BADCTRLRTYPE, MSG_TRACEBACK, Invalid controller type [dec] in slot [dec]Explanation An interface processor responded with an unknown or illegal controller type when queried. This should not happen unless the running software does not support the interface processor in question, or the interface processor fails.
Recommended Action Copy the error message exactly as it appears and report it to your technical support representative.
Error Message%DBUS-3-BADEEPROM: Invalid EEPROM data found for card in slot [dec], card disabledExplanation The ID EEPROM on the indicated card is not programmed correctly.
Recommended Action Call your technical support representative for a replacement.
Error Message%DBUS-3-DBUSTIMOUT, MSG_TRACEBACK, dbus not responding in slot [dec]Explanation An interface processor failed to respond when queried for its controller type.This message indicates a probable software or hardware problem.
Recommended Action Copy the error message exactly as it appears and report it to your technical support representative.
Error Message%DBUS-3-CXBUSERR: Slot [dec], CxBus ErrorExplanation A processor reported a bus error. The processor will be reset and not used until the next online insertion and removal (OIR) event or microcode download, when it will be retested.
Recommended Action Reinstall the processor or download the microcode. If this message recurs, call your technical support representative for assistance.
Error Message%DBUS-3-DAUGHTER_STATS: Slot [n] control [hex1], status [hex2]Explanation A processor reported an error. This message is sent out in conjunction with other error messages to provide additional information.
Recommended Action Call your technical support representative and report information about all error messages displayed.
Error Message%DBUS-3-DBUSINTERR: Slot [dec], Internal ErrorExplanation A processor reported an internal error. The processor will be reset and not used until the next OIR event or microcode download, when it will be retested.
Recommended Action Reinstall the processor or download the microcode. If this message recurs, call your technical support representative for assistance. Currently no boards report this error.
Error Message%DBUS-3-NOMAC: No system mac address found in RP1 EEPROM, using interface mac addressExplanation You have either a prototype or an RP1 EEPROM that does not have the necessary block of MAC addresses.
Recommended Action Replace the RP1 EEPROM. Call your technical support representative for assistance.
Error Message%DBUS-3-NOMAGIC: No magic number found in RP1 EEPROMExplanation The structure containing the system MAC address needed by the OIR facility cannot be found in the RP EEPROM. The RP must be returned for reprogramming.
Recommended Action Return the RP for reprogramming and call your technical support representative for assistance.
Error Message%DBUS-3-SLOTCOMP: Slot [dec], dbus error, slot [hex] and complement [hex] do not matchExplanation A processor reported a mismatch between the contents of the slot register and its complement. This condition indicates a hardware failure in the diagnostic bus controller on that processor or on the diagnostic bus. The processor will be reset and not used until the next OIR event or microcode download, when it will be retested.
Recommended Action Call your technical support representative for assistance.
Error Message%DBUS-3-SW_NOTRDY, MSG_TRACEBACK, DBUS software not ready after > [chars], elapsed [dec], status 0x[hex], control 0x[hex]Explanation An interface processor failed to come on line after being reset. This message indicates a probable software or hardware problem.
Recommended Action Copy the error message exactly as it appears and report it to your technical support representative.
Error Message%DBUS-3-UNKNOWN: Slot [dec], unknown controller type [hex], ignoringExplanation A processor reported a controller type that is unknown to the system. The processor will not be used and needs to be repaired.
Recommended Action Call your technical support representative for assistance.
Error Message%DBUS-3-WCSCTRLRERR: Slot [dec], WCS Controller Instruction ErrorExplanation Writable Control Store (WCS) is the set of devices on each interface processor that contains the running microcode. It can be loaded either from the ROM on the interface processor or from the system by using the downloadable microcode facility. In this message, a processor reported a WCS controller instruction error. The processor will be reset and not used until the next OIR event or microcode download, when it will be retested.
Recommended Action Call your technical support representative for assistance.
Error Message%DBUS-3-WCSERR: Slot [dec], WCS controller in error state [hex], resettingExplanation The processor in slot [n] reported a WCS controller error. The processor will be reset and new microcode loaded. This error message is encountered only while downloading microcode.
Recommended Action If this message recurs after the processor is reset and new microcode is loaded, call your technical support representative for assistance.
Error Message%DBUS-3-WCSLDERR: Slot [dec], error loading WCS, status [hex] cmd/data [hex] pos [dec]Explanation A processor indicated an error condition while downloading microcode. The status, cmd/data, and pos numbers reflect the error condition, the last byte of microcode loaded, and the position in the file, respectively. If this error is encountered, the microcode download is aborted and the ROM microcode is loaded.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%DBUS-3-WCSPARERR: Slot [dec], WCS Controller Parity ErrorExplanation A processor reported a WCS parity error. The processor will be reset and not used until the next OIR event or microcode download, when it will be retested.
Recommended Action Replace the processor or download microcode. If this message recurs, call your technical support representative for assistance.
Error Message%DBUS-3-XILINX: ready wait timeout, slot [dec]Explanation The field-programmable gate arrays on an interface processor failed to load after being reset. This indicates a probable software or hardware problem.
Recommended Action Call your technical support representative for assistance.
DIALER Error Messages
Dial-on-demand routing error messages
Error Message%DIALER-2-NOMEMORY: No memory to send dialer kicker packet out interface [chars], MSGDEF_LIMIT_SLOWExplanation The router is out of memory and cannot initiate a dialer call to start the snapshot active period.
Recommended Action Check the memory usage of the router and report the problem to your technical support representative.
Error Message%DIALER-2-NOSWIDB: No software interface associated with hw interface [chars]Explanation An internal software error occurred.
Recommended Action Call your technical support representative and report the error message, the system version, and the router configuration. (Use the show version command to obtain the software version.)
DLC Error Messages
Data-link control error messages
Error Message%DLC-3-BADPARAM, MSG_TRACEBACK | MSG_PROCESS, Function [chars]: value [hex] passed in parameter [chars]Explanation An internal software error occurred.
Recommended Action Call your technical support representative and report the error message and the system version. (Use the show version command to obtain the software version.)
Error Message%DLC-3-INVPCEP: Close Station, invalid P_CEPExplanation An internal software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%DLC-4-OPTNULL, MSG_TRACEBACK | MSG_PROCESS, Error, NULL parameter unexpected.Explanation An internal software error occurred.
Recommended Action Call your technical support representative and report the error message and the system version. (Use the show version command to obtain the software version.)
Error Message%DLC-3-WPUTERR: default port type, MSGDEF_LIMIT_FASTExplanation An internal software error occurred.
Recommended Action Call your technical support representative for assistance.
DLSw Error Messages
Data-link switching error messages
Error Message%DLSWC-3-BADCLSI: [chars] primitive not valid for dlsw [chars] [chars]%DLSWC-3-BADCLSICNF: [chars] Invalid confirm [chars] [chars]%DLSWC-3-BADCLSIDATALEN: Bad data len = [dec] [chars]%DLSWC-3-BADCLSIHDRLEN: [chars] Bad header len = [hex] [chars]%DLSWC-3-BADCLSIIDTYPE: [chars] Invalid ID type = [hex] [chars]%DLSWC-3-BADCLSIIND: [chars] Invalid indication [chars] [chars]%DLSWC-3-BADCLSIPRIMTYPE: [chars] Invalid primitive type = [hex] [chars]%DLSWC-3-BADCLSIRET: [chars] Invalid ret code [hex] [chars] [chars]%DLSWC-3-BADCLSISAP: [chars] Bad clsi SAP id = [hex] [chars]%DLSWC-3-BADDLCOP: dlsw_action, bad dlc event [dec] [chars]%DLSWC-3-BADPEEROP: bad peer op in peer_to_core -dec]%DLSWC-3-BADSSPEVENT: dlsw_action, bad ssp event [dec] [chars]Explanation A data-link switching system error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%DLSWC-3-BADSSPHDR: bad ssp hdr in proc ssp - [chars] = [hex]Explanation A Silicon Switch Processor (SSP) header received from the remote peer contains errors in one of the fields.
Recommended Action If the remote peer is a non-Cisco router, confirm that it supports the DLSw RFC 1795 standard.
Error Message%DLSWC-3-BADSSPOP: bad ssp op in proc ssp [dec]Explanation A Silicon Switch Processor (SSP) frame with an invalid command was received from the remote peer.
Recommended Action If the remote peer is a non-Cisco router, confirm that it supports DLSw RFC 1795 standard.
Error Message%DLSWC-3-BADTIMEROP: dlsw_action, bad timer event [dec] [chars]Explanation A data-link switching system error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%DLSWC-3-FAILASSERT: Assertion failed: [chars]Explanation An internal software inconsistency occurred. The router continues to operate.
Recommended Action If this continues to recur, record the entire message and note any DLSw+ problems that you experience. Provide this information to your technical support representative.
Error Message%DLSWC-3-FORKFAIL: Can't fork : [chars] process);Explanation DLSw process cannot run.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory. If this message recurs, copy the error message exactly as it appears and report it to your technical support representative.
Error Message%DLSWC-3-FSMACTION: [chars]Explanation Indicates frames sent by DLSw on LAN or WAN side. This is good, expected behavior.
Recommended Action Informational message only. No action required.
Error Message%DLSWC-3-FSMCALL: [chars] state [chars] , event: [chars] [chars]%DLSWC-3-FSMERR: fsm error [chars] [chars] [chars] event: [chars] [chars]%DLSWC-3-FSMINTERR: fsm internal error - [chars]%DLSWC-3-FSMUNKERR: [chars] [dec] : [chars] [chars] event:[chars] [chars] input: [dec] [dec] states: [dec] [dec]%DLSWC-3-INVALIDSTATE: finite state machine in invalid state%DLSWC-3-INVALIDTIMER: bad timer pop for [chars], new state [chars]%DLSWC-3-NOBUFF: No buffer%DLSWC-3-NODLSW: no dlsw, [chars]Explanation A data-link switching system error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%DLSWC-3-NOMEMBACK: No memory to create circuit entries - backgroundExplanation DLSw+ could not start a new circuit 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%DLSWC-3-NOMEMDLC: No memory to create circuit entry - from dlc%DLSWC-3-NOMEMSSP: No memory to create circuit entry - from sspExplanation A data-link switching system error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%DLSWC-3-NOPARAM, MSG_TRACEBACK, dlsw_action, null param blk%DLSWC-3-NOPEER, MSG_TRACEBACK, no peer, [chars]Explanation A data-link switching system error occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears and report it to your technical support representative.
Error Message%DLSWC-3-RECVSSP: SSP OP = [dec] [chars]) [chars] from [chars]Explanation A Silicon Switch Program (SSP) frame was received from the remote peer.
Recommended Action Informational message only. No action required.
Error Message%DLSWC-3-SENDSSP: SSP OP = [dec] ([chars]) [chars]to [chars] [chars]Explanation A Silicon Switch Program (SSP) frame was sent to the remote peer.
Recommended Action Informational message only. No action required.
Error Message%DLSWP-3-PBADVALUE, MSG_TRACEBACK, DLSw: [chars]: invalid [chars] [dec]Explanation A bad parameter value was passed to function chars1—invalid parameter chars2 with value. This error should not cause any network problems unless it happens repeatedly.
Recommended Action Copy the error message exactly as it appears and report it to your technical support representative as a case problem.
Error Message%DLSWP-3-PGENERAL, MSG_TRACEBACK, DLSw: [chars] [chars]Explanation A general error condition was detected as described in the message text. This error should not cause any network problems unless it happens repeatedly.
Recommended Action Copy the error message exactly as it appears and report it to your technical support representative as a case problem.
Error Message%DLSWP-3-PNOMEM, MSG_TRACEBACK, DLSw: No memory to [chars]Explanation The router ran out of system memory for operation, as described in the message text. Most likely, the router image requires more system memory (RAM) than the router contains.
Recommended Action Consult with your technical support representative about memory requirements for a specific image.
Error Message%DLSWP-3-PPASSIVE, MSG_TRACEBACK, DLSw: passive open failed from [inet]([dec]) -> [dec]Explanation The system does not have enough main memory (RAM) for TCP to allocate the data structures required to accept an incoming TCP connection. Most likely, the router image requires more system memory (RAM) than the router contains.
Recommended Action Consult with your technical support representative about memory requirements for a specific image.
Error Message%DLSWP-3-PPRIMISMATCH: DLSw: [chars]: [chars]Explanation The priority option on the specified partner's remote peer definition does not match the priority option defined on the local remote peer definition. This is a configuration error.
Recommended Action Check each remote peer statement and make sure use of the priority option is consistent on both peers.
DNET Error Messages
DECnet error messages
Error Message%DNET-3-HEARSELF: Hello type [hex] for my address from [dec].[dec] via [chars]Explanation The system is receiving its own DECnet packets. Either a serial line is looped back or another host with the same DECnet address is already present on the LAN.
Recommended Action Check the serial lines (if present) and the DECnet configuration.
Error Message%DNET-4-MAPCON: Map entry [dec].[dec] conflicts with adjacency to [dec].[dec]Explanation Your DECnet configuration is incorrect. A host that is specified as nonlocal is present on your local network.
Recommended Action Correct the configuration. Call your technical support representative if you need assistance.
Error Message%DNET-3-NOMEMORY: No memory available 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.
DNSIX Error Message
Department of Defense Intelligence Information System Network Security error message
Error Message%DNSIX-3-NOBUFFER: No buffer available for sending packet, MSGDEF_LIMIT_MEDIUMExplanation The system tried to allocate a buffer but that request was denied.
Recommended Action Examine buffer usage statistics; possibly more memory is required.
DSPU Error Messages
Downstream physical unit error messages
Error Message%DSPU-3-ActpuNegResponse: ACTPU Neg rsp received from PU [chars]Explanation Remote PU rejected the router's request for an SSCP-PU session.
Recommended Action Verify PU configuration parameters at the router and at the remote PU. Determine whether the problem exists at the remote PU, and correct it. If the problem persists, call your technical support representative for assistance.
Error Message%DSPU-3-CLSIBadAdptCorr:CLSI bad Adaptor correlator, header= [chars]Explanation An internal software error occurred.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%DSPU-3-CLSIBadIdentifier: CLSI bad identifier, header= [chars]Explanation An internal software error occurred.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%DSPU-3-CLSIBadIdentifierType: CLSI bad identifier type, header= [chars]Explanation An internal software error occurred.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%DSPU-3-CLSIBadLength: CLSI bad length, header= [chars]Explanation An internal software error occurred.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%DSPU-3-CLSIBadPrimitiveCmd: CLSI bad primitive command, header= [chars]Explanation An internal software error occurred.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%DSPU-3-CLSIBadPrimitiveType: CLSI bad primitive type, header= [chars]Explanation An internal software error occurred.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%DSPU-3-CLSIBadReturnCode:CLSI bad return code: %d, header= [chars]Explanation An internal software error occurred.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%DSPU-3-CLSIUnexpctActSapCnf:CLSI unexpected ActivateSapCnf, header= [chars]Explanation An internal software error occurred.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%DSPU-3-CLSIUnexpctDeactSapCnf:CLSI unexpected DeactivateSapCnf, header= [chars]Explanation An internal software error occurred.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%DSPU-3-CLSIUnexpctEnableCnf:CLSI unexpectedEnableCnf, header= [chars]Explanation An internal software error occurred.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%DSPU-3-CLSIUnexpctIdStnInd: CLSI unexpected IdStnInd, header= [chars]Explanation An internal software error occurred.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%DSPU-3-DSPU_BufferCorrupted: DSPU could not free buffer - buffer corruptedExplanation An internal software error occurred.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%DSPU-3-LSConnInFailed: Connect in from remote MAC [chars] failedExplanation Connection with remote station could not be established.
Recommended Action Verify configuration parameters at the router and at the remote station. Determine whether the router is configured to accept connectIn from this remote station.
Error Message%DSPU-3-LSConnInFailedNoMem: Connect in from remote MAC [chars] failed; insufficient memoryExplanation Connection with the remote station could not be established because of insufficient memory in the router.
Recommended Action Correct low memory problem in the router. If the problem persists, call your technical support representative for assistance.
Error Message%DSPU-3-LSConnInFromHostFailed: Connect in from host [chars] with remote MAC [chars] failedExplanation Connection with the remote host could not be established.
Recommended Action Verify host configuration parameters at the router and at the host. Determine whether the router is configured to accept connectIn from this host.
Error Message%DSPU-3-LSConnInFromPuFailed: Connect in from pu [chars] with remote MAC [chars] failedExplanation Connection with the remote PU could not be established.
Recommended Action Verify PU configuration parameters at the router and at the remote PU. Determine whether the router is configured to accept connectIn from this remote PU.
Error Message%DSPU-3-LSConnOutToHostFailed: Connect out to host [chars] failedExplanation Connection with the remote host could not be established.
Recommended Action Verify host configuration parameters at the router and at the host. Determine whether the host is active and responding to connection requests.
Error Message%DSPU-3-LSConnOutToPuFailed:Connect out to pu [chars] failedExplanation Connection with the remote PU could not be established.
Recommended Action Verify PU configuration parameters at the router and at the remote PU. Determine whether the remote PU is active and responding to connection requests.
Error Message%DSPU-3-LSInvalidMaxIFrame: Connection attempt failed from XID= [chars], Invalid MaxIFrame= [dec]Explanation An invalid MaxIFrame value in XID was received from the remote station; connection with remote station could not be established.
Recommended Action Correct link station configuration at the remote station.
Error Message%DSPU-3-LSInvalidWindowSize:Connection attempt failed from XID= [chars], Invalid WindowSize= [dec]Explanation An invalid WindowSize value in XID was received from the remote station; connection with remote station could not be established.
Recommended Action Correct link station configuration at the remote station.
Error Message%DSPU-3-LSNoACTPUCapability:Connection attempt failed from XID= [chars], ACTPU not supported);Explanation The remote station did not request PU 2.0 activation; connection with remote station is terminated.
Recommended Action Correct link station configuration parameters at the remote station to request a system services control point (SSCP)-PU session with the router.
Error Message%DSPU-3-LSXIDNegotiationError: XID Negotiation Error, bad byte= [dec], ** bad bit= [dec], sense data= [hex]Explanation XID3 with error indication was received from the remote station; connection with remote station could not be established.
Recommended Action Determine which field in XID3 (from bad byte/bit info) is rejected by the remote station and why (from sense data), and correct link station configuration parameters at either the router or the remote station.
Error Message%DSPU-3-NotifyNegRsp: LU [dec] received a Notify Neg Resp from host [chars]Explanation Remote host rejected the router's request to activate/deactivate an SSCP-LU session.
Recommended Action Verify host configuration parameters at the router and at the remote host. Determine whether the problem exists at the remote host and correct it. If the problem persists, call your technical support representative for assistance.
Error Message%DSPU-3-SnaBadData: Bad SNA data received from PU [chars], data= [chars]Explanation Unrecognized SNA data was received from the remote PU.
Recommended Action Correct the problem at the remote PU. If the problem persists, call your technical support representative for assistance.
Error Message%DSPU-3-UnknownXid:XID Format not supported, XID= [chars]Explanation Unsupported XID received from the remote station; connection with remote station could not be established.
Recommended Action Configure the remote station to send supported XID (if possible). Supported XID formats are
XID Format 0
XID Format 3DSX1 Error Messages
Channelized E1 (Europe) and T1 (US) DSX1 telephony standard error messages
Error Message%DSX1-1-NOMEMORY, 0, msgtxt_nomemory%DSX1-1-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%DSX1-3-BADENCAP, 0, msgtxt_badencap%DSX1-3-BADENCAP: Unit [dec], bad encapsulation in idbenctype = [hex]Explanation An internal software error occurred.
Recommended Action If this message recurs, call your technical support representative for assistance.
DUAL Error Messages
Enhanced Interior Gateway Protocol error messages
Error Message%DUAL-3-BADCOUNT, MSG_TRACEBACK, Route [chars], [dec] successors, [dec] rdbsExplanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%DUAL-3-BADSUMNOTIFY: Dual notified us about summary [chars]Explanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%DUAL-6-EVENT: [chars], [chars]Explanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%DUAL-3-LINKSEXIST: Interface [chars] is going down and [dec] links existExplanation An interface is going down or is being removed from routing through IGRP, but not all links (neighbors) have been removed from the topology table.
Recommended Action Call your technical support representative for assistance.
Error Message%DUAL-3-LINKSTILLUP: Link [dec] [chars] still exists on [chars]Explanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%DUAL-3-NOBUFFER: No buffers available for [dec] byte packet, MSGDEF_LIMIT_SLOWExplanation The DUAL software was unable to allocate a packet buffer. The system may be out of memory.
Recommended Action Record the output from the following commands: show proc mem (repeated twice), show mem, show buffers, show version, write terminal. Provide this information to your technical support representative.
Error Message%DUAL-3-NOHANDLE: Handle [dec] is not allocated in pool.Explanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%DUAL-3-NOMATCH: Nexthop and infosource don't match. N = [chars]Explanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%DUAL-3-NOMEMORY: No memory available for [chars]Explanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%DUAL-3-NOSOCKET: Unable to open socket for AS [dec]Explanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%DUAL-3-SIA: Route [chars] stuck-in-active state in [chars] [dec]. Cleaning upExplanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%DUAL-3-SIANOHANDLE: Stuck-in-active and unallocated handle in reply-status table. Cleaning upExplanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
EGP Error Messages
Exterior Gateway Protocol error messages
Error Message%EGP-3-NOPDB: No pdb for [inet]Explanation An internal software error occurred.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%EGP-3-TOOBIG: Insufficient ([dec]) buffering for update messageExplanation An EGP update message was too large to fit into a single buffer.
Recommended Action Call your technical support representative for assistance.
ENV Error Messages
Environmental monitor card error messages for AGS+
Error Message%ENV-2-FLOW: Air flow appears marginal.Explanation A temperature reading indicates poor air flow.
Recommended Action Attempt to resolve the air flow problem. If the problem is not resolved, call your technical support representative for assistance.
Error Message%ENV-1-SHUTDOWN: Environmental Monitor initiated shutdown.Explanation One of the environmental measurements reached SHUTDOWN status. The system is about to shut down the processor to prevent damage to the hardware.
Recommended Action Attempt to resolve the temperature problem. If the problem is not resolved, call your technical support representative for assistance.
Error Message%ENV-2-TEMP: Ambient temperature measured [chars]. Shutdown at [chars]Explanation The ENV card indicates the temperature it measured and the temperature at which it shuts down.
Recommended Action Attempt to resolve the temperature problem. If the problem is not resolved, call your technical support representative for assistance.
Error Message%ENV-2-VOLTAGE: [chars] testpoint measured [chars]. Shutdown margin is [chars].Explanation The ENV card indicates which voltage it is measuring (for example, +5, +12, -5, -12), the amount of voltage that it measured, and the voltage at which the processor will shut down the system.
Recommended Action Attempt to resolve the voltage problem. If the problem is not resolved, call your technical support representative for assistance.
ENVM Error Messages
Environmental monitor error messages for the Cisco 7000 series
Error Message%ENVM-2-FAN: Fan array has failed, shutdown in [dec] minutesExplanation There might be a hardware problem with the fan array. If the error condition continues for two minutes, the router automatically shuts down to prevent damage to router components.
Recommended Action If the system shuts down, replace the fan tray. Call your technical support representative for assistance.
Error Message%ENVM-2-FANOK: Fan array has recovered.Explanation One or more of the variable speed fans on the 7010 recovered from a prior failure.
Recommended Action Informational message only. No action required.
Error Message%ENVM-1-SHUTDOWN: Environmental Monitor initiated shutdownExplanation The system reached a SHUTDOWN temperature level, and the router is being shut down to avoid any damage.
Recommended Action Attempt to resolve the temperature problem. If the problem is not resolved, call your technical support representative for assistance.
Error Message%ENVM-2-SUPPLY: Power Supply is Non-OperationalExplanation A power supply is not working or is not turned on.
Recommended Action Check that the power supply is turned on; if it is turned on and still does not operate, call your technical support representative for assistance.
Error Message%ENVM-2-TEMP: [chars] temperature has reached [chars] level at [dec](C)Explanation The temperature parameter shown reached a warning or critical level and is approaching or approached a condition that is outside the acceptable range.
Recommended Action Attempt to resolve the temperature problem. If the problem is not resolved, call your technical support representative for assistance.
Error Message%ENVM-2-VOLTAGE: [chars] volts has reached [chars] level at [chars](V)Explanation The voltage parameter shown reached a critical level and is now out of specification.
Recommended Action Verify the failure and call your technical support representative for repair or replacement.
ETHERNET Error Messages
C1000 series Ethernet error messages
Error Message%ETHERNET-1-NOMEMORY, 0, msgtxt_nomemoryExplanation Insufficient memory exists to allocate the necessary memory pools.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%ETHERNET-1-TXERR: [chars]: Fatal transmit error. Restarting...Explanation A fatal transmit error occurred on the Ethernet line, causing the line to be restarted.
Recommended Action If this message recurs, call your technical support representative for assistance.
FDDI Error Messages
Fiber Distributed Data Interface error messages
Error Message%FDDI-3-BADMUL: Unit [dec], Can't set FDDI mac address to hardware multicast address [enet]Explanation Part of your FDDI hardware failed.
Recommended Action Call your technical support representative for assistance.
Error Message%FDDI-3-BADSLOT: Unit [dec], Slot [dec] does not existExplanation The main processor detects an invalid slot location for one of the network interface cards. This should never happen.
Recommended Action Call your technical support representative about obtaining a replacement card.
Error Message%FDDI-3-FDDIFAIL: Interface [chars], [chars], [chars] = [hex]Explanation The FDDI interface failed.
Recommended Action Save the output of the error message and call your technical support representative for assistance.
Error Message%FDDI-3-FDDIFAIL2: Interface [chars], [chars], [chars] = [hex], [chars] = [hex]Explanation The FDDI interface failed. This is the second line of the preceding FDDIFAIL message. This line contains debug information.
Recommended Action Save the output of the error message and call your technical support representative for assistance.
Error Message%FDDI-3-FDDIRSET: Interface [char], Error ([char]-04x) [chars] - fddi_reset()Explanation FDDI-related command execution failure.
Recommended Action Call your technical support representative for assistance.
Error Message%FDDI-3-FDDIRSETU: Unit [dec], Error ([char]-04x) [chars] - fddi_reset()Explanation FDDI-related command execution failure.
Recommended Action Call your technical support representative for assistance.
Error Message%FDDI-3-NOCAM: Unit [dec], No CAM exists for this interface.Explanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%FDDI-1-NOMEMORY, 0, msgtxt_nomemory, MSGDEF_LIMIT_SLOWExplanation The FDDI Management Information Base/Station Management (MIB/SMT) processing functions could not initialize due to insufficient memory.
Recommended Action Call your technical support representative for assistance.
FDDISTAT Error Message
FDDI state error message
Error Message%FDDISTAT-4-STATUS: FDDI state [chars] detected on interface [chars]Explanation An internal software error occurred.
Recommended Action Call your technical support representative for assistance.
FILESYS Error Messages
Personal Computer Memory Card International Association (PCMCIA) Flash card error messages
Error Message%FILESYS-5-PCMCIA_INSERT: PCMCIA flash card is inserted into [chars]Explanation A Flash card was just inserted into slot0 or slot1.
Recommended Action Informational message only that indicates the card is there now. No action required.
Error Message%FILESYS-5-PCMCIA_REMOVE: PCMCIA flash card is removed from [chars]Explanation A Flash card was just pulled out of slot0 or slot1.
Recommended Action Make sure the removed card does not contain important files such as the boot system image, boot loader image, system configuration file, and so on. Make these checks before doing a system reload.
FLASH Error Messages
Flash non-volatile memory error messages
Error Message%FLASH-3-ERASEFAIL: flash_erasefail_msgExplanation The system was unable to erase a Flash device.
Recommended Action Try to erase again. If that fails, call your technical support representative for assistance.
Error Message%FLASH-3-WRITEFAIL: flash_writefail_msgExplanation The write operation to Flash failed.
Recommended Action Try erasing the device and trying the write again. If that fails, call your technical support representative for assistance.
FR Error Message
Frame Relay error message
Error Message%FR-5-DLCICHANGE: Interface [chars] - DLCI [dec] state changed to [chars]Explanation The state of the Frame Relay PVC specified by the DLCI changed.
Recommended Action Notification message only. No action required.
Error Message%FR-4-MAPERROR: Interface [chars] - remove maps or interface-dlci command before changeExplanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
GRIP Error Messages
XNS Routing Protocol error messages
Error Message%GRIP-3-BADPATHS: Invalid number of paths [dec] for [dec]Explanation An internal inconsistency was detected in the XNS routing table structure.
Recommended Action Note the parameters associated with this message and call your technical support representative for assistance.
Error Message%GRIP-2-BADROUTE: Error [chars] route - null tableExplanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
HD Error Messages
HD64570 serial controller error messages
Error Message%HD-3-BADENCAP, 0, msgtxt_badencap%HD-1-BADENCAP:Unit [dec], bad encapsulation in idb->enctype = [hex]%HD-1-BADRING: Bad [chars] ring size%HD-3-BADUNIT: Bad unit number [dec]Explanation An internal software error occurred.
Recommended Action If message recurs, call your technical support representative for assistance.
Error Message%HD-1-BADLOOPCABLE, 0, msgtxt_badloopcableExplanation Loopback mode is not allowed when using an X.21 DTE cable on a Quad serial NIM port.
Recommended Action Do not enable loopback, or use a different cable type.
Error Message%HD-1-BADPORT: [chars]Explanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%HD-1-BADPORTADAPTER: [chars]Explanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%HD-0-INITFAIL: Unit [dec], initialization timeout failure,csr[dec]=[hex]Explanation The hardware failed to initialize correctly.
Recommended Action Repair or replace the controller.
Error Message%HD-5-LINEFLAP: Unit [dec] excessive modem control changesExplanation Too many modem control interrupts have been received. The port was disabled to prevent excessive use of the CPU.
Recommended Action Check the cable on the serial port.
Error Message%HD-1-MEMERR: Unit [dec], memory error, csr0 = [hex]Explanation A network serial interface detected a hardware problem.
Recommended Action Repair or replace the controller.
Error Message%HD-1-NOMEMOR, 0, msgtxt_nomemory, MSGDEF_LIMIT_SLOWExplanation 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%HD-0-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%HD-3-ODDSTART: Interface [chars], Odd datagram start = [hex], pak =[hex]%HD-3-OUTENCAP: Unit [dec], bad output packet encapsulation: [hex]Explanation An internal software error occurred.
Recommended Action If either of these messages recur, call your technical support representative for assistance.
Error Message%HD-3-OWNERR: Unit [dec], buffer ownership errorExplanation An Ethernet interface is malfunctioning, or an internal software error occurred.
Recommended Action Repair or replace the controller.
HUB Error Messages
Cisco Ethernet hub error messages
Error Message%HUB-1-BADHUB: Invalid hub type [dec] and number [dec]Explanation An internal software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%HUB-1-BADUNIT: Bad port number [dec]Explanation An internal software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%HUB-1-NOMEMORY, 0, msgtxt_nomemory, MSGDEF_LIMIT_SLOWExplanation The system detected that there is not enough memory for the hub initialization.
Recommended Action If conditions warrant, upgrade to larger memory configuration.
Error Message%HUB-1-READERR: Read op [dec] not allowedExplanation An internal software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%HUB-1-WRITEERR: Write op [dec] not allowedExplanation An internal software error occurred.
Recommended Action Call your technical support representative for assistance.
IBM2692 Error Messages
Error Message%IBM2692 -1-ADP_CHK: msg_adaptor_checkExplanation Indicates a hardware failure. The port is disabled.
Recommended Action Copy the error message exactly as it appears and report it to your technical support representative.
Error Message%IBM2692-1-ICDB_PERROR: msg_icdb_perrorExplanation Indicates a hardware failure.
Recommended Action Copy the error message exactly as it appears and report it to your technical support representative.
Error Message%IBM2692-1-INITFAIL: msg_initfailExplanation Indicates a hardware failure. The port failed to initialize.
Recommended Action Copy the error message exactly as it appears and report it to your technical support representative.
Error Message%IBM2692-1-NOPCIMEMORY: msg_nopcimemoryExplanation Could not allocate memory for the descriptors.
Recommended Action Copy the error message exactly as it appears and report it to your technical support representative.
Error Message%IBM2692-1-NOSYSMEMORY: msg_nosysmemoryExplanation Ran out of system memory.
Recommended Action Copy the error message exactly as it appears and report it to your technical support representative.
Error Message%IBM2692-1-PCI_PERROR: msg_pci_perrorExplanation The PCI bus failed.
Recommended Action Copy the error message exactly as it appears and report it to your technical support representative.
Error Message%IBM2692-1-RX_HALT: msg_rx_haltExplanation The RX channel has shut down.
Recommended Action The software should recover, record the message for later reference.
IGRP Error Message
Interior Gateway Routing Protocol error message
Error Message%IGRP-3-NOSOCKET: Unable to open socket for AS [dec]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.
IP Error Messages
Internet Protocol error messages
Error Message%IP-3-BADIPALIGN: Invalid alignment in packet for IP. [chars]=[hex]Explanation The packet data structure is misaligned. This condition may result in a small amount of overhead in processing IP traffic.
Recommended Action Enter a show hardware command and report the output, along with this error message, to your technical support representative.
Error Message%IP-3-BADSROUTE: Improper source route. Length [dec] Ptr [dec]Explanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%IP-4-CLASS: Bad IP address [inet] and mask [inet] in class_resolve()%IP-3-DESTHOST: src=[inet], dst=[inet], NULL desthostExplanation An internal software error occurred.
Recommended Action If either of these messages recur, call your technical support representative for assistance.
Error Message%IP-4-DUPADDR: Duplicate address [inet] on [chars], sourced by [enet]Explanation Another system is using your IP address.
Recommended Action Change the IP address of one of the two systems.
IPC Error Messages
Interface processor chassis error messages
Error Message%IPC-2-CONSISTENCY, MSG_TRACEBACK, Message failed consistency check: [chars]Explanation An internal inconsistency was found in some IPC data structures.
Recommended Action Informational message only. No action required.
Error Message%IPC-2-DELETED, MSG_TRACEBACK, Attempt to delete an IPC message (0x[hex]) a second time., MSGDEF_LIMIT_FASTExplanation An internal inconsistency was found in some IPC data structures.
Recommended Action Informational message only. No action required.
Error Message%IPC-2-LOCK, MSG_TRACEBACK, Lock done a deleted elementExplanation An internal inconsistency was found in some IPC data structures.
Recommended Action Informational message only. No action required.
Error Message%IPC-5-NODELFUNC: Delayed init function not availableExplanation The IPC application can not be initialized due to the absence of its initialization function in the initialization function list of IPC.
Recommended Action Copy the error message exactly as it appears and report it to your technical support representative.
Error Message%IPC-2-NODISPATCH: Message from [dec].[dec] has no receive queue or dispatch routine., MSGDEF_LIMIT_FASTExplanation IPC user failed to provide any means of handling received message.
Recommended Action Informational message only. No action required.
Error Message%IPC-2-ONINT, MSG_TRACEBACK, Called from interrupt level: [chars], MSGDEF_LIMIT_FASTExplanation IPC user attempted a prohibited call into IPC while running on the interrupt stack.
Recommended Action Informational message only. No action required.
Error Message%IPC-5-SLAVELOG: VIP-SLOT[dec] [chars]Explanation The Cisco IOS software, running on a VIP card, generated this message. The error message has been passed up to the RP/RSP for display. This message is seen only if the user has configured service slavelog.
Recommended Action Copy the error message exactly as it appears and report it to your technical support representative.
Error Message%IPC-2-UNLOCK, MSG_TRACEBACK, Unlock done on already unlocked element.Explanation An internal inconsistency was found in some IPC data structures.
Recommended Action Informational message only. No action required.
IPFAST Error Messages
IP fast-switching error messages
Error Message%IPFAST-2-BADIF: No support available for interface [chars] (programming error), 30*ONESECExplanation A programming error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%IPFAST-7-INTLEV, MSG_TRACEBACK, Cache update request at interrupt level: [inet]([chars])->[inet]([chars]), 5*ONESECExplanation A programming error occurred.
Recommended Action Copy the error message exactly as it appears and report it to your technical support representative.
Error Message%IPFAST-6-INVALIDATE, MSG_TRACEBACK | MSG_PROCESS, Cache invalidation occurring for [chars], ONESECExplanation The system is invalidating all cache entries for a given interface.
Recommended Action Informational message only. No action required.
Error Message%IPFAST-6-INVALREQ, MSG_TRACEBACK | MSG_PROCESS, Cache invalidation request for [chars]Explanation The system is invalidating all cache requests for a given interface.
Recommended Action Informational message only. No action required.
Error Message%IPFAST-4-RADIXDELETE, MSG_TRACEBACK | MSG_PROCESS, Error trying to delete prefix entry for [dec] [dec] (expected [hex], got [hex])Explanation A debugging message related to problems with the IP route cache. The router should correct for this error.
Recommended Action Informational message. No action required. If you're still having problems though (ie the router can't forward packets properly), copy the error message exactly as it appears and report it to your technical support representative.
Error Message%IPFAST-2-RADIXINIT: Error initializing IP fast cache structuresExplanation A programming error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%IPFAST-4-RADIXINSERT, MSG_TRACEBACK | MSG_PROCESS, Error trying to insert prefix entry for [dec] [dec] (expected [hex], got [hex])Explanation A debugging message related to problems with the IP route cache. The router should correct for this error.
Recommended Action Informational message. No action required. If you're still having problems though (ie the router can't forward packets properly), copy the error message exactly as it appears and report it to your technical support representative.
Error Message %IPFAST-3-SANITY, MSG_PROCESS, Found existing [chars] specific entry [dec] [ip mask]..[ipmask]->[dec] ([chars]) when " "attempting to create [dec] [ipmask]..[ipmask]->[dec] ([chars])Explanation A debugging message related to problems with the IP route cache. The router should correct for this error.
Recommended Action Informational message. No action required. If you're still having problems though (ie the router can't forward packets properly), copy the error message exactly as it appears and report it to your technical support representative.
IPRT Error Messages
Internet Protocol routing error messages
Error Message%IPRT-3-BADCOMLIST, MSG_PROCESS | MSG_TRACEBACK, Community list check with bad list [dec], 10*ONESECExplanation A user specified an invalid BGP community list number.
Recommended Action Check the system configuration to make sure that the community list specified falls within the valid range.
Error Message%IPRT-2-COMPRESS: Bad route_compress() call, sdb= [hex]Explanation An internal software error occurred.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%IPRT-3-NOMEMORY: No memory available for [chars]Explanation The requested operation failed because of a low memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%IPRT-3-PATHIDX, MSG_PROCESS | MSG_TRACEBACK, Bad path index of [dec] for [inet], [dec] max, ONEMINExplanation A software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%IPRT-3-TOOMANYNETS: Too many networks in [char] [dec] (limit [dec])Explanation Too many network subcommands have been entered for this routing protocol.
Recommended Action Advisory message only. No action required.
IPX Error Messages
Internetwork Packet Exchange error messages
Error Message%IPX-3-BADCOUNT: Bad IPX server count. [chars] [dec], [chars] [dec]Explanation The internal SAP service count does not match the number of services currently present and displayed by the show ipx servers command.
Recommended Action You can report the problem to your technical support representative, but no corrective action is necessary.
Error Message%IPX-3-BADIGRPSAP: Cannot send incremental SAP update to peer on interface [chars]. Increase buffers or increase output-sap-delay.Explanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%IPX-3-BADIGRPSATYPE: Unsupported SAP type for EIGRP being [chars] - type [hex]Explanation An unsupported SAP type was detected.
Recommended Action Call your technical support representative for assistance.
Error Message%IPX-3-BADPATHS: Invalid number of paths [dec] for [hex]Explanation An internal inconsistency was detected in the IPX routing table structure.
Recommended Action Note the parameters associated with this message. If possible, clear the IPX routing table by issuing the clear ipx route command. (This will result in lost connectivity until the routing table is rebuilt.) If the message recurs, note the parameters and call your technical support representative for assistance.
Error Message%IPX-3-NOMEMORY: Unable to allocate memory for [event]Explanation The system failed to allocate memory for an event. The event variable will be one of the following procedures which attempts to allocate memory:
SAP queue routing table SAP update SAP update queue entry RIP update queue entry SAP heap sort pointer array RIP update EIGRP process route entryRecommended Action Call your technical support representative for assistance.
LANCE Error Messages
LANCE Ethernet interface error messages
Error Message%LANCE-4-BABBLE: Unit [dec], babble error, csr0 = [hex]Explanation An Ethernet interface is malfunctioning.
Recommended Action Repair or replace the controller.
Error Message%LANCE-3-BADENCAP: Unit [dec], bad encapsulation in idbenctype = [hex]%LANCE-3-BADUNIT: Bad unit number [dec]Explanation An internal software error occurred.
Recommended Action If either message recurs, call your technical support representative for assistance.
Error Message%LANCE-5-COLL: Unit [dec], excessive collisions. TDR=[dec]Explanation An Ethernet cable is broken or unterminated, or the transceiver is unplugged. The time delay reflectometer (TDR) counter is an internal LANCE counter that counts the time (in "ticks" of 100 ns each) from the start of a transmission to the occurrence of a collision. Because a transmission travels about 35 feet per tick, this value is useful to determine the approximate distance to a cable fault.
Recommended Action If the transceiver appears to be properly terminated, repair or replace the Ethernet interface card.
Error Message%LANCE-1-INITFAIL: Unit [dec], initialization timeout failure, csr[dec] = [hex]Explanation The hardware failed to initialize correctly.
Recommended Action Repair or replace the controller.
Error Message%LANCE-5-LATECOLL: Unit [dec], late collision errorExplanation An Ethernet transceiver is malfunctioning, the Ethernet is overloaded, or the Ethernet cable is too long.
Recommended Action Repair or replace the controller.
Error Message%LANCE-5-LOSTCARR: Unit [dec], lost carrier. Transceiver problem?Explanation An Ethernet transceiver is unplugged or faulty.
Recommended Action Repair or replace the controller.
Error Message%LANCE-1-MEMERR: Unit [dec], memory error, csr0 = [hex]Explanation An Ethernet interface detected a hardware problem.
Recommended Action Repair or replace the controller.
Error Message%LANCE-1-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%LANCE-3-OWNERR: Unit [dec], buffer ownership errorExplanation An Ethernet interface is malfunctioning, or an internal software error occurred.
Recommended Action Repair or replace the controller.
Error Message%LANCE-3-SPURIDON: Unit [dec], spurious IDON interruptExplanation An Ethernet interface generated a spurious Initialization Done interrupt.
Recommended Action Repair or replace the controller.
Error Message%LANCE-3-UNDERFLO: Unit [dec], underflow errorExplanation The data transfer rate is exceeding the limitations of the router.
Recommended Action Reduce or eliminate access lists, reduce the number of users on the Ethernet segment, or fast switch (use a route cache to expedite packet switching). If this situation appears to be more than bursty, it may indicate that your system is handling peak traffic. You may consider upgrading to a higher platform, such as the Cisco C4500. If the error persists, call your technical support representative.
LANE Error Messages
LAN emulation error messages
Error Message%LANE-3-BADILMI, MSG_TRACEBACK, Unexpected ILMI event [dec]Explanation An internal error occurred.
Recommended Action This error should not occur. Download the system error log, then call your technical support representative and provide the log, the error message, and the router configuration.
Error Message%LANE-3-BADNAME: ELAN name must be 1-32 characters longExplanation An emulation LAN (ELAN) name was entered in a command that is longer than 32 characters. The LAN Emulation standard v1.0 requires a name that is 32 characters or less in length.
Recommended Action Re-enter a shorter name.
Error Message%LANE-3-BADTYPE: LAN Emulation supports only Ethernet typeExplanation The user specified a Token-Ring-emulated LAN, which is not currently supported.
Recommended Action Specify an Ethernet-emulated LAN. Future software releases will support Token Ring ELANs.
Error Message%LANE-3-LANE_LESBUS_UP: LES/BUS coming up from previous commandExplanation The lane server-bus command was reissued to start the LAN Emulation service components while the router was trying to execute a previously issued lane server-bus command.
Recommended Action Wait for the initial lane server-bus command to either succeed or fail. The status of the server bus can be checked via the show lane server-bus interface sub-interface name command. The previous command can also be cancelled with the no lane server-bus command. If these steps fail to clear the problem, issue the shutdown command followed by a no shutdown command cycle on the subinterface, or on the whole interface. As a last resort, issue the no interface sub-interface name command followed by the shutdown, no shutdown command cycle.
Error Message%LANE-3-LANE_SIG_CHAIN, MSG_TRACEBACK, not in [chars] chain ([hex] [hex])Explanation An internal error occurred while system routines were handling ATM signaling messages for LAN Emulation.
Recommended Action Copy the error message exactly as it appears and report it to your technical support representative.
Error Message%LANE-3-LANE_SIG_ERR, MSG_TRACEBACK, [chars]Explanation An internal error occurred while system routines were handling ATM signaling messages for LAN Emulation.
Recommended Action Copy the error message exactly as it appears and report it to your technical support representative.
Error Message%LANE-3-LANE_SIG_INV_MSG: invalid msg received ([hex] [hex] [hex])Explanation An internal error occurred while system routines were handling ATM signaling messages for LAN Emulation.
Recommended Action Call your technical support representative for assistance.
Error Message%LANE-3-LANE_SIG_INV_STATE, MSG_TRACEBACK, invalid [chars] req in state [dec] ([hex])Explanation An internal error occurred while system routines were handling ATM signaling messages for LAN Emulation.
Recommended Action Copy the error message exactly as it appears and report it to your technical support representative.
Error Message%LANE-6-LEC: [chars]Explanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%LANE-3-LEC_BADAD: [chars] LEC unable to compute ATM addressExplanation The client cannot obtain an ATM address from the given configuration, or auto-assignment failed to get an ATM prefix from the switch.
Recommended Action If you expect the switch to assign the prefix to the router, check that the Interim Local Management Interface (ILMI) is functional and the switch has a prefix configured. Otherwise, confirm that the client has an address in the NVRAM configuration.
Error Message%LANE-3-LEC_CONTROL_MSG: Received bad control message on interface > [chars], 10*ONESECExplanation The client received a control message over one of its control virtual channel connections (VCCs) that failed the header check.
Recommended Action This message indicates a non-interoperable LANE configuration server, LANE server, or LANE client implementation on the emulated LAN.
Error Message%LANE-3-LEC_LISTEN: [chars] listen failed on [chars]Explanation The client failed an attempt to listen on a particular ATM address.
Recommended Action Reconfigure the client ATM address. It is conflicting with another component on the ATM Interface Processor (AIP) for the same ATM address.
Error Message%LANE-3-LEC_SIGNAL: Unexpected SigAPI event [dec], 10*ONESECExplanation ATM signaling sent the client an unexpected message type.
Recommended Action This message should not display. Call your technical support representative for assistance.
Error Message%LANE-4-LEC_STATE_ERROR: State: [dec], Event [dec]Explanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%LANE-6-LEC_TIMER: Timer [chars] expiredExplanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%LANE-3-LSV_ADDR: [chars] elan [chars] unable to register LES/BUS ATM addrExplanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%LANE-3-LSV_BADAD: <interface> elan <ELAN name> unable to compute [chars] ATM addressExplanation Software was unable to compute an ATM address based on the ATM address template given. The characters in chars (see above display) will be either "BUS" (broadcast-and-unknown), "server", or "config server" in the actual error message.
Recommended Action Enter a correct ATM address template for the LAN emulation component ("BUS," "server", or "config server") named in the error message.
Error Message%LANE-3-LSV_CRASH, MSG_TRACEBACK, <interface> elan <ELAN name> unrecoverable error [chars]Explanation An internal error occurred.
Recommended Action This error should not occur. Download the system error log, then call your technical support representative and provide the log, the error message, and the router configuration.
Error Message%LANE-3-LSV_DUPATM: <interface> elan <ELAN name> client [dec] duplicate ATM address registration <ATM address>Explanation An attempt was made by the specified LANE client to register a MAC address and ATM address pair that duplicated an ATM address already registered to another LANE client.
Recommended Action Use the show lane server command to list the registered addresses in the LANE server reporting the error. Correct one of the two LANE clients that is trying in error to use the same ATM address.
Error Message%LANE-3-LSV_DUPID: <interface> elan <ELAN name> duplicate LECID [dec]Explanation An attempt was made to define two different server-direct PVCs both on the same subinterface (same LANE server) and both for the same client (LECID).
Recommended Action Delete one of the lane pvc commands that has this duplicated LECID.
Error Message%LANE-3-LSV_DUPMAC: <interface> elan <ELAN name> client [dec] duplicate MAC address registration [enet]Explanation An attempt was made by the specified LANE client to register a MAC address and ATM address pair that duplicated a MAC address already registered to another LANE client.
Recommended Action Use the show lane server command to list the registered addresses in the LANE server reporting the error. Correct one of the two LANE clients that is trying in error to use the same MAC address.
Error Message%LANE-4-LSV_LECID: <interface> elan <ELAN name> LECIDs exhausted, 10*ONESECExplanation The LANE server specified has 65279 clients. No more can be added.
Recommended Action Change the configurations to avoid trying to have more than 65279 LANE clients on this server.
Error Message%LANE-3-LSV_MCAST: <interface> elan <ELAN name> unable to create [chars] MC groupExplanation An internal error occurred.
Recommended Action This error should not occur. Download the system error log, then call your technical support representative and provide the log, the error message, and the router configuration.
Error Message%LANE-3-LSV_NOREG: <interface> elan <ELAN name> client [dec] unable to register MAC address [enet]Explanation An internal error occurred.
Recommended Action This error should not occur. Download the system error log, then call your technical support representative and provide the log, the error message, and the router configuration.
Error Message%LANE-6-MAKE17: Created vcd [dec] (PVC [dec]/[dec]) for config server accessExplanation The LANE software created a PVC (normally 0/17) for accessing the LANE configuration server.
Recommended Action Informational message only. No action required.
Error Message%LANE-3-NAMECHG: Attempt to change ELAN nameExplanation Both the LANE client and the LANE server/BUS may have an emulation LAN (ELAN) name specified in the configuration via the lane server-bus and lane client commands. If both specify the ELAN name, then the name cannot be changed by re-entering just one of the commands.
Recommended Action Use the no lane server-bus command to delete the server-bus or the no lane client command to delete the client. Then, the other of the two commands can be re-entered with another ELAN name. Finally, re-enter the deleted command with the new ELAN name.
Error Message%LANE-3-NEWPREF: <interface> elan <ELAN name> ATM address prefix [chars]Explanation Entering a new ATM address template for some LANE component caused the specified LANE server or bus to drop all clients and restart.
Recommended Action Informational message only. No action required.
Error Message%LANE-3-NOILMI, MSG_TRACEBACK, ILMI service registration failedExplanation The Interim Local Management Interface (ILMI) feature is not included in the software build running on the router.
Recommended Action Reload router with software that includes the ILMI feature.
Error Message%LANE-3-NOINT: <interface> still destroying old sub-interfaceExplanation An attempt was made to create a new subinterface while a previous version of the subinterface was still being destroyed.
Recommended Action Wait a minute and try again. If failure still occurs, try shutting down the main interface. Rebooting may be required to recover in extreme cases.
Error Message%LANE-3-NOREGATM: <interface> cannot register <ATM address> with ILMIExplanation An attempt to register the given ATM address with the ATM switch failed. This failure can occur because the ATM switch is down or misconfigured. The registration will be retried.
Recommended Action If the situation persists after a number of attempts, and the switch is up, the configuration of the switch and router must be examined. The most likely cause is that ATM address being registered is not compatible with the parameters — for example, the ATM address prefix — configured in the switch. Correct the configuration.
Error Message%LANE-3-NOVCD: VCDs exhaustedExplanation When trying to create PVC 0/17, the router ran out of PVC resources.
Recommended Action The number of PVCs can be increased with the atm maxvc command.
Error Message%LANE-3-PVCBAD: <interface> elan <ELAN name> PVC vcd [dec] has no [chars] assignedExplanation The characters in chars (see above display) will be either "ATM address" or "LECID". This message is reported when a permanent virtual circuit (PVC) is created without all the necessary information included in the lane pvc command.
Recommended Action Include a lane pvc command with the information appropriate for the PVC.
Error Message%LANE-3-PVCLECS: Unable to create PVC [dec]/[dec]Explanation An attempt to create the named PVC failed. The most likely reason is that a PVC was defined on the same or another sub-interface with the same virtual path identifier/virtual channel identifier (VPI/VCI), but with a different encapsulation or usage type.
Recommended Action Correct the configuration.
Error Message%LANE-3-REGSTATE, MSG_TRACEBACK, ILMI event in state [dec]Explanation An internal error occurred.
Recommended Action This error should not occur. Download the system error log, then call your technical support representative and provide the log, the error message, and the router configuration.
Error Message%LANE-3-TYPECHG: Attempt to change ELAN typeExplanation Both the LANE client and the LANE Server/BUS may have an ELAN type specified in the configuration via the lane server-bus and lane client commands as either Ethernet or Token-Ring. If both, specify the type; the type cannot be changed by re-entering just one of the commands.
Recommended Action Use the no lane server-bus command to delete the server-bus or the no lane client command to delete the client. Then, the other of the two commands can be re-entered with a new type. Finally, re-enter the deleted command with the new type.
LANMGR Error Messages
IBM LAN Network Manager error messages
Error Message%LANMGR-4-BADRNGNUM: Ring number mismatch on [chars], shutting down RPS.Explanation The router detected a conflict in assigned ring numbers for the specified Token Ring. The Ring Parameter Server (RPS) function was shut down to prevent potentially incorrect information from being sourced onto the ring.
Recommended Action Check all bridges connected to this Token Ring and ensure that they are using the same assigned ring number.
Error Message%LANMGR-4-BADUPCALL: Unexpected call ([chars]) from LLC2 for Bridge [hex]-[hex]-[hex].Explanation An internal software error occurred.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%LANMGR-4-OLDTRAMON: Cannot run RPS on [chars], Old TRAMON code.Explanation The software on this interface cannot support the functions required for LAN Network Manager.
Recommended Action Call your technical support representative about a firmware upgrade for this interface card.
LAPB Error Messages
X.25 Link Access Protocol, Balanced error messages
Error Message%LAPB-4-CTRLBAD: Interface [chars], Invalid control fieldExplanation A received FRMR reported a frame with an invalid control code.
Recommended Action Check the serial line and the devices attached to the line.
Error Message%LAPB-4-FRAMEERR: Interface [chars], Frame error: CF [hex], VS[dec] [char] VR [dec], Reason [hex]Explanation A FRMR frame was received, indicating that a protocol violation was detected. The Reason field will be interpreted by generating INFOBAD, CTRLBAD, N1TOOBIG, or INVNR messages immediately after this message; refer to the explanations for these messages for more information.
Recommended Action The protocol will recover by resetting the service. This will disrupt any network service on top of LAPB (for example, X.25 virtual circuits will be cleared). Follow the recommended action for any error message following the FRMR reports; if service becomes unacceptable, check the serial line and its attached devices.
Error Message%LAPB-4-INFOBAD: Interface [chars], Info field not permittedExplanation A received FRMR frame reported that an information field was present in a frame where no information field is allowed.
Recommended Action Check the serial line and the device attached to the line.
Error Message%LAPB-4-INVNR: Interface [chars], Invalid NR valueExplanation A received FRMR reported a frame with an invalid N(R) value.
Recommended Action Verify that the equipment attached to the serial line is configured with the same K value (maximum number of outstanding I frames).
Error Message%LAPB-4-N1TOOBIG: Interface [chars], N1 too largeExplanation A received FRMR reported an information frame that was too long.
Recommended Action Verify that the equipment attached to the serial line is configured with the same N1 value. N1 is in bits and includes the entire frame plus 16 bits of CRC. However, some equipment may require configuration in octets, the omission of the two CRC octets, or the omission of the three octets of LAPB control information.
Error Message%LAPB-2-NOBUF: Interface [chars], no buffer available to [chars]Explanation There was insufficient memory for the LAPB protocol engine to send a message.
Recommended Action This message is acceptable if it occurs infrequently, because the LAPB protocol is designed to handle loss of frames. Frequent occurrences can cause disruption of service. The system can be configured to ease memory demands or, if conditions warrant, the system can be upgraded to a larger memory configuration.
Error Message%LAPB-3-NOINPIDB: Input idb not set%LAPB-3-NULLPAK: Interface [chars], NULL packet ptr, rvr [dec],vs [dec], vr [dec]Explanation An internal software error occurred.
Recommended Action If either of these messages recur, call your technical support representative for assistance.
LAT Error Messages
DEC Local Area Transport error messages
Error Message%LAT-3-BADDATA: Tty[t-line], Data pointer does not correspond to current packet%LAT-3-BUFFULL: Tty[t-line], data buffer full with count [dec]Explanation An internal software error occurred.
Recommended Action If either of these messages recur, call your technical support representative for assistance.
Error Message%LAT-3-NOSYNC: Tty[t-line], Output data ptrs out of sync with byte countExplanation An internal software error occurred.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%LAT-3-NULLIDB: Null IDB pointer with destination [enet]%LAT-3-QBSPACED: Queue block at [hex] not found for HI connection%LAT-3-REUSE: Tty[t-line], Attempt to re-use slot array, empty =[dec], fill = [dec]Explanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
LEX Error Messages
LAN extension error messages
Error Message%LEX-3-NOTSENT: Serial line down, [chars] : [chars] not sentExplanation The serial line went down, and the specified command was not sent to the LAN Extender.
Recommended Action Determine why the serial line went down. For example, was the cable was pulled, or the LAN Extender powered off? The command will automatically be re-sent once the serial interface is operational.
Error Message%LEX-3-RCMDNAK: [chars] : [chars] could not be processed by LAN ExtenderExplanation The LAN Extender could not process the command from the host router. Possible causes are:
•
•
•
•
Recommended Action If the command was copy tftp lex unit-number or copy flash lex unit-number, make sure that the correct file, that is, a FLEX image file, is specified. Only a single copy request can be handled at one time. If the problem was caused by a temporary out-of-memory condition on the LAN Extender, re-enter the command.
Error Message%LEX-3-RCMDREJ: [chars] : [chars] could not be processed by LAN ExtenderExplanation The LAN Extender did not recognize the code for the specified remote command. This might occur if the user is running old LAN Extender software with newer host router software that has support for new LEX remote commands.
Recommended Action Update the LAN Extender software.
Error Message%LEX-3-TIMEOUT: Retry count exceeded for [chars] : [chars]Explanation The host router re-sent the given message as many times as specified in the lex retry-count command configuration variable, without receiving an acknowledgment from the LAN Extender. At this point, the host router gives up trying to send this particular remote command message.
Recommended Action Use the LEDs on the LAN Extender to determine if it is operational. Confirm that the lex timeout configuration command is set appropriately for the speed of the link.
LINEPROTO Error Message
Line Protocol error message
Error Message%LINEPROTO-5-UPDOWN: Line protocol on Interface [chars], changed state to [chars]Explanation The data link level line protocol changed state.
Recommended Action Notification message only. No action required.
LINK Error Messages
Data link error messages
Error Message%LINK-3-BADENCAP: Interface [chars] Bad encapsulation code [dec]Explanation The lower level software was unable to write a MAC header for a datagram. A probable cause is configuration error.
Recommended Action Call your technical support representative for assistance.
Error Message%LINK-3-BADETHER: Interface [chars], Bad ethernet encap codeExplanation An internal software error occurred.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%LINK-3-BADMACREG: Interface [chars], non-existent MACADDR registry for link [dec]Explanation An attempt to map a network level address to a MAC level address failed.
Recommended Action Call your technical support representative for assistance.
Error Message%LINK-2-BADVCALL: Interface [chars], undefined entry pointExplanation An internal software error occurred. The high-level system code tried to use an unimplemented entry point with the virtual IDB driver.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%LINK-5-BOOTP: [chars] address [inet], resolved by [inet]Explanation An interface's IP address was successfully learned dynamically through BootP. The first address is the learned IP address. The second IP address is the IP address of the BootP server that provided the information.
Recommended Action No action required.
Error Message%LINK-4-BRIDGECONFLICT: [char], encapsulated BPDU recvd from [enet]Explanation An FCIT running in nonencapsulating transparent mode detected an FDDI bridge running in encapsulation mode on the same fiber. This is an unstable situation and should be corrected. The incoming interface is displayed, along with the FDDI MAC address in canonical form.
Recommended Action Upgrade the errant interface to full transparent mode. Call your technical support representative for assistance.
Error Message%LINK-5-CHANGED: Interface [chars], changed state to [chars]Explanation The interface hardware changed state.
Recommended Action Notification message only. No action required.
Error Message%LINK-3-COMPREG: Interface [chars], non-existent (de)compression registry. Packet droppedExplanation A software or hardware error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%LINK-4-FDDISTAT: Interface [chars], FDDI state [chars] detectedExplanation There was a state change on the FDDI ring.
Recommended Action Dependent on the specific error condition. Call your technical support representative for assistance.
Error Message%LINK-4-FDDIUNK: [chars]: unknown [hex] len [dec]Explanation An unknown FDDI datagram was received.
Recommended Action Record the complete error message and call your technical support representative for assistance.
Error Message%LINK-2-LINEST: No linestate vector for [chars]Explanation An internal software inconsistency occurred.
Recommended Action Call your technical support representative for assistance.
%LINK-4-NOMAC: A random default MAC address of [enet] has\n been chosen.Explanation An addressing inconsistency occurred.
Recommended Action Make sure that this address is unique, or specify MAC addresses for commands such as novell routing that allow the use of this address as a default.
Error Message%LINK-2-NOSOURCE: Source idb not set%LINK-3-TOOBIG: Interface [chars], Output packet size of [dec] bytes too big%LINK-3-TOOSMALL, MSG_TRACEBACK, Interface [chars], Output packet size of [dec] bytes too small. Changed to [dec] bytes%LINK-2-UENCAP: Unknown line encapsulation code [dec]Explanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%LINK-5-RARP: [chars] address [inet], resolved by [inet]Explanation The Reverse Address Resolution Protocol (RARP) resolved an IP address.
Recommended Action Notification message only. No action required.
Error Message%LINK-3-REMLOOP: Interface [chars], remote loop [chars] [chars]Explanation The interface entered or exited a remote loopback.
Recommended Action Notification message only. No action is required.
Error Message%LINK-5-SLARP: [chars] address [inet], resolved by [inet]Explanation The Serial Line Address Resolution Protocol (SLARP) resolved an IP address.
Recommended Action Notification message only. No action required.
Error Message%LINK-3-UPDOWN: Interface [chars], changed state to [chars]Explanation The interface hardware went either up or down.
Recommended Action If the state change was unexpected, confirm the configuration settings for the interface.
LLC2 Error Messages
Logical Link Control, type 2 error messages
Error Message%LLC-2-UNEXPECT, MSG_TRACEBACK, LLC2: [chars] UNEXPECTED EVENTExplanation An internal software error was found. A software component is trying to use LLC2 structures that do not exist.
Recommended Action Record the configuration and any information that would be useful in recreating the error and call your technical support representative.
Error Message%LLC-4-T1_ERR: LLC2: [chars] INCREASE LLC TIMERSExplanation The T1 timer popped for an LLC2 session. However, the frame which is to be retransmitted is still on a queue inside the router awaiting transmission over RSRB, Frame Relay, or other protocol. If the retransmission occurs, the LLC2 session will probably fail due to N2 retry failures.
Recommended Action Increasing the LLC2 acknowledgment timers decreases the likelihood of failure. In addition, investigate sporadic congestion in a routed network.
LNMC Error Messages
Error Message%LNMC-3-BADCLSI, MSG_TRACEBACK, [chars] primitive not valid for lnm [hex] [hex]%LNMC-3-BADCLSICNF, MSG_TRACEBACK, [chars] Invalid confirm [chars] [cha [chars]%LNMC-3-BADCLSIDATALEN, MSG_TRACEBACK, [chars] Bad data len =[dec] [hex]%LNMC-3-BADCLSIHDRLEN, MSG_TRACEBACK, [chars] Bad header len = [hex] [hex] [chars]%LNMC-3-BADCLSIIDTYPE, MSG_TRACEBACK, [chars] Invalid ID type = [hex] [hex] [chars]%LNMC-3-BADCLSIIND, MSG_TRACEBACK, [chars] Invalid indication [chars], [chars]%LNMC-3-BADCLSIPRIMTYPE, MSG_TRACEBACK, [chars] Invalid primitive type = [hex] [hex] [chars]%LNMC-3-BADCLSIRET, MSG_TRACEBACK, [chars] Invalid ret code [hex] [hex] [chars] [chars]%LNMC-3-BADCLSISAP, MSG_TRACEBACK, [chars] Bad clsi SAP id = [hex] [chars]Explanation A LAN network mangaer system error occured.
Recommended Action Copy the error message exactly as it appears and report it to your technical support representative.
LPD Error Message
Line printer daemon error message
Error Message%LPD-3-MANYLF: Line [t-line], packet has too many newlines to convertExplanation An internal buffer did not have enough room to add all the necessary carriage returns to a packet of LPD data destined for a printer configured with a newline-convert command. This message is unlikely to occur with a file containing valid data.
Recommended Action Check the file being printed to see whether it contains valid, printable data.
M32 Error Messages
HDLC controller error messages
Error Message%M32-1-NOMEMORY, 0, msgtxt_nomemory, MSGDEF_LIMIT_SLOWExplanation An error has occurred caused by a lack of main memory, a lack of I/O memory, or a hardware failure.
Recommended Action Use the show memory command to confirm that there is enough memory available. If there is not enough memory, you need to upgrade your router. If the router has enough memory, then there is probably a hardware problem. Call your technical support representative for assistance.
MAILBOX Error Messages
ChipCom mailbox error messages
Note
Error Message%MAILBOX-3-BADCHKSUM: Checksum failed. Expected = 0x%02x, calculated = 0x%02x. Ignoring PDU.Explanation A hardware or software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%MAILBOX-3-BADDATA: Bad data in mailbox test, got [hex], expected [hex]%MAILBOX-3-FLAGSTAT: Timeout while waiting for FLAGSTAT, status=[hex]%MAILBOX-3-INITPC2: Timeout waiting for PC2 during initialization, status=[hex]%MAILBOX-3-INTERR: Bad mailbox interrupt = [hex]%MAILBOX-3-MAIL020: Timeout while waiting for MAIL020, status=[hex]%MAILBOX-3-MAILFAIL: Mailbox failed to initialize%MAILBOX-3-PC2: Timeout while waiting for PC2, status=[hex]%MAILBOX-3-SPURINT: Spurious mailbox interrupt = [hex], MAIL020 not assertedExplanation A hardware problem was detected in a ChipCom interface board.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%MAILBOX-3-BADECHO: Echo-response did not match echo-request!Explanation The data received from an ECHO_RESPONSE protocol data unit (PDU) did not match the original data provided in the ECHO_REQUEST. Usually, this message is seen during initialization, and indicates a catastrophic failure of the mailbox interface. See MAILBOX-3-INITFAIL for more information.
Recommended Action Confirm the router module installation. Make sure the software revision on the management module and the router module carrier card is up-to-date. If the error persists, call your technical support representative for assistance.
Error Message%MAILBOX-3-BADPDU: PDU of type [chars] received. Invalid or unsupported. Ignoring.Explanation The protocol data unit (PDU) received was valid, but the type is not supported in the current software implementation. It will be ignored.
Recommended Action Informational message only. No action required.
Error Message%MAILBOX-3-INITFAIL: Mailbox initialization failure. [Incoming|Outgoing] mailbox offline.Explanation A catastrophic failure involving the initialization of the administrative mailbox occurred. The mailbox will be taken offline and remain in that state until a router module reset, or a system reload, occurs At that time, initialization will again be attempted. Note that the functionality of the router, that is, it's ability to receive and forward packets, is not affected by this error.
Recommended Action Confirm the router module installation. Make sure the software revision on the management module and the router module carrier card is up-to-date. If the error persists, call your technical support representative for assistance.
Error Message%MAILBOX-6-INITOK: Mailbox initialization successful.Explanation This message is generated after a router reload to indicate the mailbox was successfully initialized.
Recommended Action Informational message only. No action required.
Error Message%MAILBOX-7-MBOXDEBUG: [chars]Explanation This message header is paired with general debugging messages used to provide information about the functionality of the mailbox. To enable mailbox debugging, issue the command debug mailbox.
Recommended Action Advisory message only. No action required.
Error Message%MAILBOX-3-NOECHO: Echo-request timed out. No response received. Mailbox offline.Explanation An ECHO_RESPONSE was not received in the appropriate time after the generation of an ECHO_REQUEST. This failure only occurs during mailbox initialization, and indicates a problem between the communication path of the router module and its carrier card.
Recommended Action Confirm the router module installation. Make sure the software revision on the management module and the router module carrier card is up-to-date. If the error persists, call your technical support representative for assistance.
Error Message%MAILBOX-3-OFFLINE: [Incoming|Outgoing] mailbox is offline. Interrupt ignored.Explanation This message is generated when an attempt is made by the management module to communicate with an offline mailbox. When it appears, it indicates a problem exists between the perceived state of the mailbox from the router's side versus the management module's side.
Recommended Action Issue a system-wide reset on the management module. If the error persists, call your technical support representative for assistance.
Error Message%MAILBOX-7-ONLINE: [Incoming|Outgoing] mailbox coming online.Explanation This message is generated only when mailbox debugging is enabled. It provides information about the state of each incoming or outgoing mailbox.
Recommended Action Advisory message only. No action required.
Error Message%MAILBOX-7-READ: Reading 0x%02x from carrier.Explanation This message is generated only when mailbox debugging is enabled. It provides very low-level information about the incoming mailbox data stream.
Recommended Action Advisory message only. No action required.
Error Message%MAILBOX-3-TIMEOUT: Intra-PDU timeout occurred on [incoming|outgoing] mailbox data.Explanation A timeout occurred while sending or receiving the characters of a protocol data unit (PDU). The entire PDU will be ignored.
Recommended Action Informational message only. No action required
Error Message%MAILBOX-7-WRITE: Writing 0x%02x to carrier.Explanation This message is generated only when mailbox debugging is enabled. It provides very low-level information about the outgoing mailbox data stream.
Recommended Action Advisory message only. No action required.
MCI Error Messages
Multiport Communications Interface error messages
Error Message%MCI-5-INPUTERR: Interface [chars] excessive input error rateExplanation The input error rate was so high that the interface was temporarily disabled. The interface will be automatically reenabled in 30 seconds.
Recommended Action If this message recurs, check the communication lines.
Error Message%MCI-4-NOCOOKIE: MCI controller[dec] missing configuration data - disabledExplanation The configuration PAL is missing.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%MCI-4-NOKEEPALIVE: Interface [chars] keepalive not sentExplanation 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%MCI-5-OBSOLETE: Obsolete MCI firmware: can't route [chars] and bridge simultaneouslyExplanation The firmware on your MCI controller card is out of date.
Recommended Action Upgrade your MCI firmware.
Error Message%MCI-4-RSETFAIL: Interface [chars] failed to reset properly in[chars], code [hex]Explanation A hardware device did not respond appropriately to a request. This generally indicates a hardware problem.
Recommended Action Call your technical support representative for assistance.
Error Message%MCI-3-RXINDEX: Unit [dec], invalid RX index [dec]Explanation The MCI did not answer a Multibus request. This generally indicates a hardware problem.
Recommended Action Call your technical support representative for assistance.
Error Message%MCI-3-SETUPERR: Unit [dec], Error ([hex]) on setup, index [hex],restarting controller - mci_interrupt()Explanation A hardware device did not respond appropriately to a request. This generally indicates a hardware problem.
Recommended Action Call your technical support representative for assistance.
Error Message%MCI-4-TESTFAIL: Unit [dec] failed [chars] test, skippingExplanation A hardware component failed an internal diagnostic test.
Recommended Action Call your technical support representative for assistance. You need to replace the malfunctioning component.
MK5 Error Messages
MK5025 serial controller error messages
Error Message%MK5-3-BADENCAP: Unit [dec], bad encapsulation in idb->enctype = [hex]%MK5-3-BADRING: Bad [chars] ring size%MK5-3-BADUNIT: Bad unit number [dec]Explanation An internal software error occurred.
Recommended Action If either of these messages recur, call your technical support representative for assistance.
Error Message%MK5-0-INITFAIL: Unit [dec], initialization timeout failure,csr[dec]=[hex]%MK5-1-INITNOPPRIM: Unit [dec], initialization failure - No CSR1_PPRIM_INIT_CONF, csr1 = [hex]%MK5-1-INITUERR: Unit [dec], initialization CSR1_UERR failure,csr1=[hex]Explanation The hardware failed to initialize correctly.
Recommended Action Repair or replace the controller.
Error Message%MK5-5-LINEFLAP: Unit [dec] excessive modem control changesExplanation Too many modem control interrupts have been received. The port was disabled to prevent excessive use of the CPU.
Recommended Action Check the cable on the serial port.
Error Message%MK5-1-MEMERR: Unit [dec], memory error, csr0 = [hex]Explanation A network serial interface detected a hardware problem.
Recommended Action Repair or replace the controller.
Error Message%MK5-0-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%MK5-3-ODDSTART: Interface [chars], Odd datagram start = [hex], pak =[hex]%MK5-3-OUTENCAP: Unit [dec], bad output packet encapsulation: [hex]Explanation An internal software error occurred.
Recommended Action If either of these messages recur, call your technical support representative for assistance.
Error Message%MK5-3-OWNERR: Unit [dec], buffer ownership errorExplanation An Ethernet interface is malfunctioning, or an internal software error occurred.
Recommended Action Repair or replace the controller.
Error Message%MK5-3-PLOSTERR: Unit [dec], provider primitive lost,csr0=[hex], csr1=[hex]%MK5-3-PPRIMERR: Unit [dec], unexpected provider primitive, csr0=[hex], csr1=[hex]%MK5-3-SPURPPRIMERR: Unit [dec], spurious provider primitive, csr0=[hex], csr1=[hex]%MK5-3-UPRIMERR: Unit [dec], user primitive error, csr0=[hex], csr1=[hex]Explanation A network serial interface detected a hardware problem.
Recommended Action Repair or replace the controller.
NETMGT Error Message
Network Management error message
Error Message%NETMGT-6-ALERT: [chars] SNA LLC : [chars]\n [chars]\n [chars]\n [chars]Explanation A software or hardware error occurred.
Recommended Action Call your technical support representative for assistance.
NHRP Error Message
Next Hop Resolution Protocol error message
Error Message%NHRP-3-NOBUFFER: No buffer available for sending packet, MSGDEF_LIMIT_MEDIUMExplanation The NHRP software could not allocate a packet buffer. The system may be out of memory.
Recommended Action Record the output from the following commands: show proc mem (repeated twice), show mem, show buffers, show version, write terminal. Provide this information to your technical support representative.
NIM Error Messages
Network interface module error messages
Error Message%NIM-2-BADSLOT: Illegal reference to non-existent slot [dec]%NIM-2-BADSUBUNIT: Illegal reference to non-existent subunit [dec] in slot [dec]%NIM-2-DEADICHAINQ: Attempted to manipulate uninitialized ichainQ in [chars]%NIM-2-LOSTICHAINQ: Couldn't find idb [hex] in ichainQ in [chars]%NIM-2-NOHWADDRESS: All hardware addresses have been allocated — maximum of [dec]Explanation An internal software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message%NIM-2-BADNIMREV: Unsupported version of [chars] NIM in slot [dec]|> Version 0x[hex]Explanation The indicated network interface module (NIM) is not supported because it is not of the correct revision. Certain platforms (Cisco 4500 or Cisco 4700, for example) require some NIMs to be of a minimum rev level.
Recommended Action Upgrade the NIM to the proper level.
Error Message%NIM-2-UNSUPNIM: Unsupported [chars] NIM in slot [dec]Explanation The indicated NIM is not supported on this platform.
Recommended Action Remove the NIM.
OIR Error Messages
Online insertion and removal error messages
Error Message%OIR-6-INSCARD: Card inserted in slot [dec], interfaces administratively shut downExplanation The OIR facility detected a newly inserted processor in slot dec. The inserted interface will be shut down until it is configured by the user or, if an interface of that type was previously configured, it will be restored to its previous state.
Recommended Action Informational message only. No action required.
Error Message%OIR-3-LONGSTALL: Long bus stall ([dec] ms), check for improperly seated cardsExplanation Something is preventing the CxBus or CyBus from operating. The usual reason is an improperly seated interface processor.
Recommended Action Make sure all interface processor cards are firmly seated. If the problem persists, it may be a hardware problem. Call your technical support representative for assistance.
Error MessageOIR-6-NOEOIR: [chars] hardware version 1.0 not capable of EOIRExplanation An attempt was made to remove or insert a card in a system containing at least one card that does not support enhanced online insertion and removal (EOIR).
Recommended Action Upgrade to a card that supports EOIR features. If this odes not solve the problem, contact your technical support representative for assistance.
Error Message%OIR-6-REMCARD: Card removed from slot [dec], interfaces disabledExplanation The OIR facility detected the removal of a processor from slot [n]. The interfaces on that processor will be administratively shut down and marked as removed. The routing table will be flushed of any routes through the removed interfaces.
Recommended Action Informational message only. No action required.
OSPF Error Messages
Open Shortest Path First error messages
Error Message%OSPF-4-BADLENGTH: Invalid length [dec] in OSPF packet from [inet] (ID [inet]], [chars]Explanation The system received an OSPF packet with a length field of less than normal header size or inconsistent with the size of the IP packet in which it arrived. This indicates an error in the sender of the packet.
