Table Of Contents
System Error Messages
AAA Accounting Messages
TACACS+ Authentication, Authorization, and Accounting security accounting error messages
Error Message%AAAA-3-BADSTR: Bad accounting data: [chars]Explanation During AAA accounting operations, the internal database of accounting information for a user was found to be corrupt. 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: 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.
Error Message%AAAA-3-RELOGIN sanity check in re-login [chars] to [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.
AIP Error Messages
ATM Interface Processor error messages
Error Message%AIP-3-AIPFAILSETUPVC: Interface [chars], Failed to setup vc [dec] (Cause: [chars])Explanation This error message indicates that the AIP driver failed to set up a virtual circuit (VC).
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%AIP-3-AIPREJCMD: Interface [chars], AIP driver rejected [chars] command (error code [hex])Explanation This indicates that the AIP microcode rejected a command sent by the route processor (RP). The error code is the status value returned by the command.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
ALIGN Error Messages
The ALIGN facility controls a feature in reduced instruction-set computer (RISC)-processor-based Cisco products that identifies software in need of memory use optimization.
Error Message%ALIGN-3-CORRECT: Alignment correction made at [hex] reading/writing [hex]Explanation A software component within the router needs memory optimization.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%ALIGN-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 Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%ALIGN-3-FULL: Alignment log is full - no new entries will be recorded.Explanation The router identified more software components in need of memory optimization than it can record.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%ALIGN-3-NOMEM: Not enough memory to start alignment subsystem.Explanation The router cannot start the memory performance monitoring system because not enough system memory is available for doing so.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
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 Copy the error message exactly as it appears, and report it 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 Copy the error message exactly as it appears, and report it to your technical support representative.
APPN Error Messages
Advanced Peer-to-Peer Networking error messages
Error Message%APPN-1-APPNALERT: [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%APPN-2-APPNCRIT: [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%APPN-7-APPNDEBUG: [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%APPN-0-APPNEMERG: [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%APPN-3-APPNERR: [chars]Explanation A race condition occurred between two components in the APPN software.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%APPN-7-APPNETERROR: [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%APPN-3-APPNETLOG: [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%APPN-6-APPNINFO: [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%APPN-6-APPNLOGMSG: [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%APPN-5-APPNNOTICE: [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%APPN-7-APPNSENDEVENT: [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%APPN-6-APPNSENDMSG: [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%APPN-5-APPNSENDREQ: [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%APPN-4-APPNWARNING: [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%APPN-7-MSALERT: Alert [chars] issued with sense code [hex] by [chars] APPN_COMPLAIN_IVLExplanation An alertable condition occurred in the local node.
Recommended Action Reference the "Detailed Alert" section of the IBM Systems Network Architecture Management Services Reference (order number: SC30-3346) for a description of ALERTID. Also reference the "Sense Data" section of IBM Systems Network Architecture Formats (order number: GA27-3136) for a description of SENSE_CODE. Report this message to your technical support representative.
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 Microcom Networking Protocol version 4 (MNP4) link setup.
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 appears only when ARA protocol logging is configured. The message notes that an ARA protocol user has logged out.
Recommended Action No action is required.
Error Message%ARAP-6-ADDRUSED:TTY [dec]: ARAP started for user [chars]; address [dec].[dec]Explanation This message appears only when ARA protocol logging is configured. The message notes that an ARA protocol user has logged in.
Recommended Action No action is required.
Error Message%ARAP-3-BADCONFIG: TTY [dec]: unhandled configuration commandExplanation A configuration command was not recognized.
Recommended Action Check the configuration file on the server for any invalid configuration commands.
Error Message%ARAP-6-BADEXIT: TTY [dec]: exited user [chars] [chars]Explanation A user was disconnected from ARA protocol at an unexpected time. The disconnection may be due to modems dropping, server error, client problems, or any number of other difficulties.
Recommended Action To determine the cause of the disconnection, correlate the receipt of this message with the user problem reports.
Error Message%ARAP-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 ARA protocol client was denied access, probably due to a configuration problem on the server. The error message should indicate the problem. This message does not indicate access denials due to bad passwords.
Recommended Action Investigate the problem reported in the error message.
Error Message%ARAP-4-GETBUFFER: getbuffer failed: size [dec]: [chars]Explanation The ARA protocol could not obtain a buffer for an incoming packet.
Recommended Action Examine buffer usage statistics. More memory might be required.
Error Message%ARAP-5-INITCONFUSED: TTY [dec]: ARAP unexpected initialization packet [chars]Explanation The startup negotiation between a client and the ARA protocol server fell out of order. If this message is received sporadically, it indicates line noise.
Recommended Action If this message recurs, reinstall the ARA client software.
Error Message%ARAP-4-NOEXTTACACS: TTY [dec]: arap TACACS is configured but extended TACACS is not.Explanation Terminal Access Controller Access Control System (TACACS) authentication failed because extended TACACS is not configured.
Recommended Action Configure extended TACACS.
Error Message%ARAP-3-NOMEM: TTY [dec]: ARAP session failed; no memoryExplanation ARA protocol failed to run because it could not 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 ARA protocol 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 setup.
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 Copy the error message exactly as it appears, and report it to your technical support representative.
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: AppleTalk CPU piggie info: just spent [dec] ms. without scheduleExplanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%AT-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 Copy the error message exactly as it appears, and report it to your technical support representative.
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 Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%AT-6-EIGRPLINKUP: AT/EIGRP Link Up: [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%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 Copy the error message exactly as it appears, and report it to your technical support representative.
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 Copy the error message exactly as it appears, and report it to your technical support representative.
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 Copy the error message exactly as it appears, and report it to your technical support representative.
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 Copy the error message exactly as it appears, and report it to your technical support representative.
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 Copy the error message exactly as it appears, and report it to your technical support representative.
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 Copy the error message exactly as it appears, and report it to your technical support representative.
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 Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%AT-5-OLDMCI: [chars]: AppleTalk route cache disabled; firmware is obsoleteExplanation The firmware on the MCI controller card does not support AppleTalk fast switching.
Recommended Action No corrective action is required. Normal AppleTalk operation 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 Copy the error message exactly as it appears, and report it to your technical support representative.
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 Copy the error message exactly as it appears, and report it to your technical support representative.
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 Messages
Asynchronous Transfer Mode error messages
Error Message%ATM-3-FAILCREATEVC: ATM failed to create VC(VCD=[dec], VPI=[dec], VCI=[dec]) on Interface [chars], (Cause of the failure: [chars])Explanation This message can occur for various unrelated reasons. Each reason is listed below, along with a recommended action.
•
The virtual circuit descriptor (VCD) exceeded the maximum available memory.
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Recommended Action If none of the above fixes the problem, copy the error message exactly as it appears and report it to your technical support representative.
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 Copy the message exactly as it appears, and report it your technical support representative.
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: msgtxt_nomemoryRecommended 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 Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%BRI-3-OUTENCAP: Unit [dec], bad output packet encapsulation: [hex]Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
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-BADLINESTATE: Line state Tx when receiving non-Tx event: [dec].Explanation An unexpected receive occurred while transmitting.
Recommended Action Check that the line has been consistently defined in regards to the carrier. If a message report was sent, hard-on stop and start the bisynchronous interface in question.
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 subsystem 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-NOGRPDEF: No bstun group defined on interface [chars]Explanation An action was taken which requires the previous definition of a BSTUN group number.
Recommended Action Make sure encapsulation bstun and the bstun group have been defined for the interface.
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. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message x%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-PROCEXIT: Process terminating. Due to signal [dec]. Subcode [dec]. Address [hex].Explanation The BSTUN background process is terminating.
Recommended Action If this happened while unconfiguring BSTUN, no action is required. Otherwise record all the displayed values and any other bstun error messages. Contact your technical support representative.
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.
Error Message%BSTUN-3-UNKPROTOEV: Unknown protocol event [dec] on interface [chars]Explanation A non-decodeable event was passed to the BSUTN layer for processing.
Recommended Action If the problem happens hard-on, stop and start the indicated interface.
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 Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CBUS-4-BADENCAPSZ: [chars]: CIP encapsulated msg size ([dec]) exceeds max ([dec]Explanation An encapsulated control message from the CIP had a size greater than the maximum expected size. The message was truncated.
Recommended Action Copy the error message exactly as it appears and copy down the router's configuration along with any other relevant information. Contact 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 Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CBUS-3-BUFFER: Controller [dec], Error ([hex]), Buffersize = [dec], Bufferpool = [dec], number [dec]Explanation An internal 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-CBUSBCE: Failed to select a BCE, response [hex] - cbus_bce_update_ifa()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-CBUSBCEPERM: Failed to select a BCE, response [hex] - cbus_bce_permissions_update()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.
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: CCB handover timed out, CCB [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 Copy the error message exactly as it appears, and report it to your technical support representative.
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 Copy the error message exactly as it appears, and report it to your technical support representative.
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-CIPENCAP: [chars]: No elements available for message ([hex] [hex])Explanation An encapsulated control message arrived from the CIP, but no elements were available to receive it. The Route Processor (RP) or the RSP will reset the interface.
Recommended Action Copy the error message exactly as it appears and copy down the router's configuration along with any other relevant information. Contact your technical support representative for assistance.
Error Message%CBUS-3-CIPNOPREQ: [chars]: Unable to pre allocate response element; cfg not sent.Explanation An attempt to allocate a buffer for the CIP configuration response, or for the configuration state change request, was unsuccessful. The configuration request was not sent to the CIP.
Recommended Action The configuration command must be reissued.
Error Message%CBUS-3-CIPRSET: Interface [chars], Error ([hex]) [chars] cip_reset()Explanation The Channel Interface Processor (CIP) did not respond to a reset request from the route processor.
Recommended Action
Try each of the following fixes in sequence. If a fix corrects the problem, there's no need to perform the tasks which follow it.
1
2
3
If the error still occurs, copy the error message exactly as it appears. Record the output from the following commands:
•
•
•
•
•
Record any of the other log messages that surround the CIPRSET message. Provide this information to your technical support representative.
Error Message%CBUS-3-CMD: 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: Cmd timed out, CCB [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 Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CBUS-3-CTRCMDFAILED2: Unit [dec], CTR Command [hex] Failed, Code [hex]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-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 Copy the error message exactly as it appears, and report it to your technical support representative.
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 the memory device (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 Copy the error message exactly as it appears, and report it to your technical support representative.
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 Copy the error message exactly as it appears, and report it to your technical support representative.
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 [hex] [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 Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CBUS-3-MODULE: Missing [chars] for [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-3-NOBUF: 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. Cookie ROM is a ROM device that controls the micro-code characteristics of an interface. Another possibility is a corrupted memory device (MEMD) after the memd self-tests.
Recommended Action It will be necessary to replace the cookie ROM. Copy the error message exactly as it appears, and report it to your technical support representative.
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. The interface might not be attached to a cable or there might be a software problem.
Recommended Action Check that the interfaces are all connected to the proper cables. 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]: [hex] [hex] [hex] [hex] [hex] [hex]Explanation 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: 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 Copy the error message exactly as it appears, and report it to your technical support representative.
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 Copy the error message exactly as it appears, and report it to your technical support representative.
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 Copy the error message exactly as it appears, and report it to your technical support representative.
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-1-BLOWSHUT: Blower failure, shutdown in [dec] secondsExplanation One of the six blowers in a five-slot chassis has failed. Since each blower cools a separate region of the cards in the chassis, all blowers are needed for router operation. If a blower failure persists for two minutes, the router will shut itself down and will need to be power cycled.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
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 Copy the error message exactly as it appears, and report it to your technical support representative.
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 Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CI-3-CTRLRTYPE: Wrong controller type [hex]Explanation The CI was manufactured incorrectly.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
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 [hex]Explanation An unexpected interrupt occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
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: [chars] acknowledge failure, cmd [hex], addr [hex], data [hex]Explanation 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 Copy the error message exactly as it appears, and report it to your technical support representative.
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 [hex]Explanation 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 nonredundant 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 Copy the error message exactly as it appears, and report it to your technical support representative.
CIP Error Messages
The system can report error conditions in several facility codes related to the Channel Interface Processor (CIP). 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-ADAPTER Error Messages
CIP error messages for the adapter task
Error Message%ADAPTER-4-BADREQUEST: Bad request code [dec] generated on port [dec]Explanation A request was sent to the function that handles general requests for the specified port. The request code was not in a range recognized by that function.
Recommended Action The CIP recovered by ignoring the request. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%ADAPTER-6-BADSTATE: Bad state: port [dec], request code [dec], state [dec], flags [hex]Explanation The specified port was in an invalid state while it attempted to process the specified general request
Recommended Action The CIP recovered by forcing the port into a well-known state. Copy the error message exactly as it appears, and report it to your technical support representative.
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 ESCON Channel Adapter (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 ESCON Channel Adapter (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 Reenter 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. Logout data will occur whenever a problem is detected on the port adapter or with an ESCON Channel Adapter (ECA), on the fiber.
Recommended Action If this message is being continually generated on a new installation, it may be an indication that the fiber is not connected properly. Verify that the connector is firmly seated. If a loose fiber was not the cause of these messagees, 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 run. 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 message 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 route processor (RP) requested that the CIP 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 write operations to the memory device (MEMD) and reissue them if a ciscoBus 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 the memory device (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 parallel channel adapter (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 about this 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 about this 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 about this 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 that the CIP 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 that the CIP 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 that the CIP 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 that the CIP 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 that the CIP 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-0-TOOMANY: Too many buffers ([dec]) required for a write operation.Explanation The mainframe wrote data to the CIP. The number of buffers needed to hold that data exceeded the total number of buffers allocated on the CIP for that purpose. This is a fatal error.
Recommended Action Copy the error message exactly as it appears, and report it 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 parallel channel adapter (PCA) in the specified port. The PCA cannot 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 that the CIP 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-BADAPPL2: Configured names: \[chars]\ - \[chars]\Explanation An attempt was made to establish a connection, but the application names specified on the host do not match the application names specified in the router configuration.
Recommended Action Correct the host and/or router configuration.
Error Message%CLAW-6-BADCHAIN: Too many buffers in an IP Datagram write chain.Explanation All data sent in an IP datagram must fit in one transfer list element. This IP datagram required more than one transfer list element.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
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 names specified on the host do not match the host application names 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-LONGREC: Attempt to transmit too large a record.Explanation The amount of data being read by the channel exceeded the size of the read channel command word (CCW).
Recommended Action Copy the error message exactly as it appears, and report it 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.
Error Message%CLAW-6-VIRTCLAW: CLAW device may not be created on a virtual port adapterExplanation An attempt was made to configure a CLAW device on the virtual port adapter. CLAW devices cannot be configured on virtual port adapters. They can only be configured on physical port adapters.
Recommended Action The configuration request was ignored. No action required.
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 parallel channel adapter (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-CONFIGINIT: Invalid config registry identifier [dec]Explanation During initialization, each application that receives configuration commands from the system registers the routines needed to process its configuration commands. An incorrect registration identifier was used.
Recommended Action This is a fatal error. The CIP has been restarted.
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-NOCONFIG: No configuration routine registered for entry [dec]: [chars]Explanation Configuration command processing is dynamically set up when features are added to an image. The feature needed to process a configuration command is not part of the current image.
Recommended Action Either run a CIP microcode load that supports the configuration command being issued, or do not issue that configuration command.
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-NOSPACE: No space to build configuration confirmationExplanation Whenever the system sends a configuration command to the CIP, it responds with a confirmation message. There was not enough memory on the CIP to allocate a block to hold a confirmation message.
Recommended Action If you are not at the maximum CIP memory configuration, additional memory may be installed on the CIP. Otherwise, configure fewer channel connections.
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-OFFLDEV: Offload device address ([hex]) must be evenExplanation The route processor attempted to configure an odd-numbered address for an offload device. Offload configuration requests must specify an even-numbered address. This is an internal logic error. The configuration request was ignored.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CONFIG-3-STATEINIT: Too many state change notification routinesExplanation During initialization, each application that uses the virtual port adapter registers to receive notification when that adapter is shut or not shut. The table to hold these registration requests is too small.
Recommended Action This is a fatal error. The CIP has been restarted.
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-UNEXPCFG: Configuration command code [dec] is not supportedExplanation Configuration command processing is dynamically set up when features are added to an image. The feature needed to process the configuration command is not a part of the current image.
Recommended Action Either run a CIP microcode load that supports the configuration command being issued, or do not issue that configuration command.
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-CTA Error Messages
CIP error messages for the channel transport architecture (CTA) device task/mapper
Error Message%CTA-6-BADCHAIN: PA[dec] CTA [hex]-[hex] Too many buffers in a CSNA write chain.Explanation All data sent in a CIP Systems Network Architecture (CSNA) write request should fit in one transfer list element. This message required more than one.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CTA-0-ERRSTASH: PA[dec] CTA [hex]-[hex] buffer [hex] not in stash, pc: [hex]Explanation An error was detected while processing host-bound messages.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CTA-0-ERRSTATE1: PA[dec] CTA [hex]-[hex] sequence error during subchannel setup, pc: [hex]Explanation A host write request was received while the setup state equalled "pending open."
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CTA-0-ERRSTATE2: PA[dec] CTA [hex]-[hex] sequence error during subchannel setup, pc: [hex]Explanation Ahost read request was received while the setup state equalled "setup open."
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CTA-0-ERRSTATE3: PA[dec] CTA [hex]-[hex] sequence error during subchannel setup, pc: [hex]Explanation A host read request was received while the setup state equalled "pending complete."
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CTA-0-ERRSTATE4: PA[dec] CTA [hex]-[hex] sequence error during subchannel setup, pc: [hex]Explanation A host write request was received while the setup state equalled "setup complete."
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CTA-6-FLUSH: PA[dec] CTA [hex]-[hex] Read data flushed.Explanation Due to an error on the channel, some of the data that was intended for the channel was not sent to it. Virtual Telecommunications Access Method (VTAM) will receive an error indication and should retry the operation.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CTA-6-INIT: PA[dec] CTA [hex]-[hex] Device initializedExplanation A CIP Systems Network Architecture (CSNA) device has been initialized. The elements of the device string, CSNAx/yyyy/zz, have the following meaning: x is the daughter card number, yyyy is the path, and zz is the device number.
Recommended Action No action required.
Error Message%CTA-6-LONGREC: PA[dec] CTA [hex]-[hex] Attempt to transmit too large a record.Explanation The amount of data being read by the channel exceeded the size of the read channel command word (CCW).
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CTA-0-MSGERR1: PA[dec] CTA [hex]-[hex] mismatch between channel block size and msg countsExplanation An error was present in the host message as indicated by the description.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CTA-0-MSGERR2: PA[dec] CTA [hex]-[hex] msg size less than DLC hdr sizeExplanation An error was present in the host message as indicated by the description.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CTA-0-NOMEM: CTA attempt to acquire memory failed, pc: [hex]Explanation A call to create a pool or get a buffer failed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CTA-0-QUEUE_ERROR: PA[dec] CTA [hex]-[hex] attempt to init or alloc a queue failed at [hex]Explanation A call to initialize or allocate a queue failed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CTA-6-SHUTDOWN: PA[dec] CTA [hex]-[hex] Device shutdownExplanation A CIP Systems Network Architecture (CSNA) device was shut down. The elements of the device string, CTAn/mmmm/yy, have the following meaning: n is the daughter card number, mmmm is the path, and yy is the device number.
Recommended Action No action required.
Error Message%CTA-0-SYSMGT_ERROR1: CTA detected error in sysmgt call: invalid CSNA DEVICE length%CTA-0-SYSMGT_ERROR2: CTA detected error in sysmgt call: invalid LLC2 CONN length%CTA-0-SYSMGT_ERROR3: CTA detected error in sysmgt call: invalid CSNA typeExplanation An invalid parameter was received in a system management call.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CTA_TEST_TOOL-3-INVALID_CFGBLK_LEN: CTA Test-Tool configuration block length invalidExplanation A CTA test-tool configuration command with an invalid configuration block length was received. The command was ignored.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CTA_TEST_TOOL-3-INVALIDLEN: CTA Test-Tool configured incorrectly for a CTA command, cmd: [hex]Explanation The offset and length of a CTA test-tool command was out of range for a CTA command buffer. The CTA test-tool cannot process the CTA command.
Recommended Action Verify that the CTA test-tool command configured offset and length with values from the CTA formats and protocol document. If you do not have a configuration error, copy the error message exactly as it appears and report it to your technical support representative.
Error Message%CTA_TEST_TOOL-3-INVALIDMBUF: CTA Test-Tool detected an invalid CTA command mbuf, cmd: [hex]Explanation The CTA test-tool cannot identify the format of the CTA command mbuf. The CTA Test-Tool cannot process the CTA command.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CTA_TEST_TOOL-3-NOMEMORY: CTA Test-Tool code could not allocate memory, pc: [hex]Explanation An attempt was made to allocate memory for the CTA test-tool utility. Not enough memory was available when the cta-test-tool configuration command was processed by the CIP. The cta-test-tool command will not be executed.
Recommended Action Retry the cta-test-tool configuration command at a later time, or install more memory on the CIP card. If neither action resolves the problem, copy the error message exactly as it appears and report it to your technical support representative.
Error Message%CTA-0-UNEXP_CTA_CMD: PA[dec] CTA [hex]-[hex] received CTA command [hex] at [hex]Explanation The received CTA command code was not in the valid range.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CTA-0-UNEXP_EVENT: PA[dec] CTA [hex]-[hex] received unrecognized type code [hex] at [hex]Explanation The received transfer element type code was not in the valid range.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CTA-0-UNEXP_LSI_CMD: PA[dec] CTA [hex]-[hex] received LSI command [hex] at [hex]Explanation The CTA Device Task received a Link Services Interface (LSI) command code that was not in the valid range.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CTA-0-UNEXP_LSI_STATUS: CTA received status [hex] in LSI cmd [hex]Explanation The received Link Services Interface (LSI) status code was not valid for the command.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
CIP-DEBUGGER Error Messages
CIP error messages issued when nonrecoverable errors occur on the CIP
Error Message%DEBUGGER-0-CIP_HWVINFO: SNr. [dec] HWRev. [int].[int] EPROM [int].[int] VPLD [int].[int]Explanation A fatal internal CIP error occurred. The message includes software version information.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%DEBUGGER-0-CIP_SWVINFO: [dec].[dec] [chars]Explanation A fatal internal CIP error occurred. The message includes software version information.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%DEBUGGER-0-FATAL_ERROR: Fatal error (code=%02d)Explanation A fatal internal CIP error occurred. The CIP failed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%DEBUGGER-0-LCORE_DATA: [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex]Explanation The message displays data from the low core area of the CIP.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%DEBUGGER-0-LCORE_START: Dump of lowcoreExplanation The CIP has failed. The low core area of the CIP will begin to dump.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%DEBUGGER-0-RESTART: Restart due to breakpointExplanation The CIP finished dumping all debugging information and is attempting a restart.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%DEBUGGER-0-STACK_DATA1: [hex] [hex]%DEBUGGER-0-STACK_DATA2: [hex] [hex] [hex]%DEBUGGER-0-STACK_DATA3: [hex] [hex] [hex] [hex]%DEBUGGER-0-STACK_DATA4: [hex] [hex] [hex] [hex] [hex]%DEBUGGER-0-STACK_DATA5: [hex] [hex] [hex] [hex] [hex] [hex]%DEBUGGER-0-STACK_DATA6: [hex] [hex] [hex] [hex] [hex] [hex] [hex]%DEBUGGER-0-STACK_DATA7: [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex]%DEBUGGER-0-STACK_DATA8: [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex]Explanation This message displays internal interrupt stack information.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%DEBUGGER-0-STACK_START: Stack addr: [hex]Explanation The CIP failed. The internal interrupt stack will begin to dump.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%DEBUGGER-0-TRACE_ADDR: Table:[hex] Next:[hex] First:[hex] Last:[hex] Full:[hex]Explanation This message displays the internal trace table header.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%DEBUGGER-0-TRACE_DATA: [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex]Explanation The message displays a single entry from the internal trace table.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%DEBUGGER-0-TRACE_START: Dump of trace tableExplanation The CIP failed. The internal trace table will begin to dump.
Recommended Action Copy the error message exactly as it appears, and report it 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 dynamic RAM (DRAM) on the CIP and memory device (MEMD) facility
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 direct memory access (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 direct memory access (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 direct memory access (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.
Error Message%DMA-0-REGISTERS: [hex] [hex] [hex] [hex]Explanation An error occurred during a direct memory access (DMA) transfer. The hexadecimal numbers represent the DMA hardware controller registers at the end of the transfer.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
CIP-GET_DATA Error Message
CIP error message 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-IPC Error Messages
CIP error messages related to the Interprocess Communication subfacility
Error Message%IPC-2-CONSISTENCY: Message failed consistency check: [chars]Explanation An internal IPC protocol error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%IPC-2-DELETED: Attempt to delete an IPC message ([hex]) a second time.Explanation An internal IPC protocol error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%IPC-2-LOCK: Lock done on a deleted element.Explanation An internal IPC protocol error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%IPC-2-NOBUFFER, MSG_PROCESS, Could not fetch a new message buffer.Explanation The IPC protocol subsystem could not obtain the message buffers it needed.
Recommended Action The CIP card may require more memory. 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.Explanation An internal IPC protocol error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%IPC-2-NOMEM: No memory availble for [chars].Explanation The IPC protocol subsystem could not obtain the memory it needed.
Recommended Action The CIP card may require more memory. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%IPC-2-NOMEMD: Unable to obtain CBUS IPC buffersExplanation The IPC protocol subsystem cannot obtain the buffers it needs.
Recommended Action Ensure that at least one CIP interface is not shutdown. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%IPC-2-UNLOCK: Unlock done on already unlocked element.Explanation An internal IPC protocol error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
CIP-LOADER Error Messages
CIP error messages related to the relocating loader facility.
Error Message%LOADER-3-ABSERR: Error: not handled - Symbol [chars] is absoluteExplanation The loader cannot handle variables of this type.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LOADER-3-ALOCER1: Error: Allocating storage - load fails%LOADER-3-ALOCER2: Error: Did not allocate storage - loading of data failed.Explanation There is not enough storage to load this file.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative. More storage will probably be needed. You might use the current storage more efficiently by running a different combination of features.
Error Message%LOADER-3-ATFERR: Error: atf array overflowExplanation The area to free (ATF) array is too small. The ATF array is an array of areas to be freed when an attempted load fails.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LOADER-3-BADSHT: Error: Section header type [hex]([dec]) not understoodExplanation The input file is not in the proper format.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LOADER-3-BAKEXP: Error: Deleting external symbol [chars] from the exported table.Explanation The symbols should have been deleted from the table, but were not. This will probably cause problems during future file loads.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LOADER-3-BIGEND: Error: Input is not big endianExplanation The input file is not the correct type for loading.
Recommended Action Check the input file type. If the file type is correct, then copy the error message exactly as it appears and report it to your technical support representative.
Error Message%LOADER-3-BINDERR: Error: Bind value in symbol table entry not understoodExplanation The loader cannot handle variables of this type.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LOADER-3-COMERR: Error: type not handled, must be .scommonExplanation The loader cannot handle this type.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LOADER-3-COMMIX: Error: common variable [chars] matches name of non-common loaded variable.Explanation An error occurred in the input files.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LOADER-3-COMPER: Error: Compiled for incorrect target machineExplanation The input file is not the correct type for loading.
Recommended Action Check the input file type. If the file type is correct, then copy the error message exactly as it appears and report it to your technical support representative.
Error Message%LOADER-3-DREADE: Error: Reading in program dataExplanation An error prevented the loader from reading a section of the file.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LOADER-3-DUPEXP: Error: Duplicate exported external symbol [chars] not allowedExplanation The file being loaded attempted to export a symbol that had already been exported by a previously loaded file.
Recommended Action There is a conflict between loadable files and/or the kernel. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LOADER-3-EIDENT: Error: File header has unknown data in e_ident areaExplanation The input file is not in the correct format needed for loading.
Recommended Action Check the input file format. If the format is correct, then copy the error message exactly as it appears and report it to your technical support representative.
Error Message%LOADER-3-ELF32: Error: Input is not an ELF32 fileExplanation The input file is not in the correct format needed for loading.
Recommended Action Check the input file format. If the format is correct, then copy the error message exactly as it appears and report it to your technical support representative.
Error Message%LOADER-3-ELFH: Error: Cannot read ELF header from input fileExplanation The loader could not read the module header information.
Recommended Action Check the file. If it is correct, then report this error message to your technical support representative.
Error Message%LOADER-3-ERR16H: Error: processing HI16 LO16 pair. Low without HighExplanation The loader cannot handle relocation entries of this type.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LOADER-3-FCLOSE: Warning: File close failed, code = [dec]Explanation Loading is complete, but the close failed
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LOADER-3-FILESIZE: Unable to access image fileExplanation The CIP has failed to access the necessary image files.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LOADER-3-FOPEN: Error: Cannot open the input file \[chars]\.Explanation An error occurred when attempting to open a file to be loaded.
Recommended Action Confirm that the file exists. Create it if possible. If the problem persists, copy the error message exactly as it appears and report it to your technical support representative.
Error Message%LOADER-3-FOPENER: Error: file open failure code [dec]Explanation The required file cannot be opened.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LOADER-3-FREADE: Error: reading, offset: [hex] size: [hex]([dec])Explanation The loader could not read the input file. The load failed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LOADER-3-GPPROB: Error: Allocation of GP relative space problem: [hex]([dec]) left, [hex]([dec]) needed.Explanation The space needed for the allocation of a larger area has been exhausted.
Recommended Action Sufficient space should be allocated in advance. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LOADER-3-GREADE: Error: reading in GP relative section dataExplanation An error prevented the loader from reading a section of the file.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LOADER-3-HDRSIZ: Error: this size header entry cannot be handled.Explanation The file is not in the proper format. The loader cannot handle it.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LOADER-3-HDRVER: Error: Input is not current versionExplanation The input file is not the correct version of object file format.
Recommended Action Check the file format version. If the file version is correct, then copy the error message exactly as it appears and report it to your technical support representative.
Error Message%LOADER-3-HREADE: Error: Cannot read headers from the fileExplanation An error occurred while reading the file headers.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LOADER-3-INSUFF: Error: insufficient space for suballocation: [hex]([dec]) left, [hex]([dec]) needed.Explanation There is not enough space for the new allocation.
Recommended Action Sufficient space should be allocated in advance. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LOADER-0-INVALIDIOS: IOS version incompatible with CIP - must be at least [dec].[dec]Explanation The version of Cisco IOS software is incompatible with this CIP microcode image.
Recommended Action The Cisco IOS software must be updated to match the CIP version. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LOADER-6-LOADING: [chars] -- [dec] bytesExplanation The CIP successfully loaded a segment image.
Recommended Action This is an informational message. No action required.
Error Message%LOADER-3-LOADRC: Error: Return code is [hex]([dec])Explanation This message displays the error level on the load failure.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LOADER-3-MAXRSE: Error: too many Resident Symbol TablesExplanation MAX_RSE_TABS is not sufficient to handle this file.
Recommended Action MAX_RSE_TABS must be increased, and the loadrel.c file must be recompiled. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LOADER-3-MAXSEC: Error: Total number of sections has exceeded pre-allocated space for [dec] entries.Explanation MAX_SECTION_COUNT is not sufficient to handle this file.
Recommended Action MAX_SECTION_COUNT must be increased, and the loadrel.c file must be recompiled.. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LOADER-3-MAXSTRT: Error: Too many string tablesExplanation MAX_STR_TABS is not sufficient to handle this file.
Recommended Action MAX_STR_TABS must be increased, and the loadrel.c file must be recompiled. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LOADER-3-MAXSYMT: Error: Too many symbol tablesExplanation MAX_SYM_TABS is not sufficient to handle this file.
Recommended Action MAX_SYM_TABS must be increased, and the loadrel.c file must be recompiled. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LOADER-3-NOBITS0: Error: NOBITS but size [dec] is not 0, not understoodExplanation Either the loader cannot process the input file, or the file is not in the proper format.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LOADER-3-NODSO: Error: section contains dynamic shared objectsExplanation The input file cannot have dynamic shared objects.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LOADER-3-NOELF: Error: Input is not an ELF fileExplanation The input file is not in the correct format.
Recommended Action Check the input file format. If the format is correct, then copy the error message exactly as it appears and report it to your technical support representative.
Error Message%LOADER-3-NOERES: Error: Could not resolve external symbol [chars]Explanation A reference from the file being loaded to an external symbol cannot be resolved.
Recommended Action Define all prerequisite external symbols before loading the file. If problems persist, copy the error message exactly as it appears and report it to your technical support representative.
Error Message%LOADER-3-NOPREFIX: Unable to determine microcode image nameExplanation The CIP is unable to compose the microcode image name.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LOADER-3-NOPRG: Error: No code to handle program headersExplanation The input file is not in the correct format.
Recommended Action Check the input file format. If the format is correct, then copy the error message exactly as it appears and report it to your technical support representative.
Error Message%LOADER-3-NOSECH: Error: No section headers to processExplanation The input file is not in the proper format.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LOADER-3-NOSO: Error: section contains symbols conflicting with shared objectsExplanation The input file cannot have shared objects.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LOADER-3-NOTRE: Error: File is neither relocatable nor executableExplanation The input file is not the correct type for loading.
Recommended Action Check the input file type. If the file type is correct, then copy the error message exactly as it appears and report it to your technical support representative.
Error Message%LOADER-3-NOVERS: Error: No entry for \loader_segment_version\Explanation The loader requires that files to be loaded should have an entry, loader_segment_version, containing a specific structure.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LOADER-3-READERR: Error: file read failure code [dec]Explanation An error occurred while the file was being read.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LOADER-3-RELFLG: Error: Cannot handle the flags in the relocation entryExplanation The loader cannot handle relocation entries of this type.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LOADER-3-RELREAD: Error: Cannot read relocation entriesExplanation The loader could not read part of the file.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LOADER-3-RELTYP: Error: relocation type [hex]([dec]) not recognizedExplanation The loader cannot handle this type of relocation.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LOADER-3-RELTYP2: Error: relocation type R_MIPS_[chars] not handled.Explanation The loader cannot handle this type of relocation.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LOADER-3-RESERR: [chars] [dec] external symbols cannot be resolvedExplanation Either the prerequisite files are not loaded, or there are incorrect references.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LOADER-3-SECERR: Error: Cannot handle section [chars]Explanation The loader cannot process this type of section of the code.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LOADER-3-SEEKER: Error: file seek failure code [dec]Explanation An error occurred positioning within the file.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LOADER-3-SHFLAGE: Error: no storage allocated - sh_flags did not indicate howExplanation The loader cannot handle this file.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LOADER-3-SHNHIPE: Error: not handled -End appl specific range of indices%LOADER-3-SHNHIR: Error: not handled - End reserved range of indicesExplanation The loader cannot handle variables of this type.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LOADER-3-SIZERR1: Error: common variable [chars] has a size incompatible with loaded variable.Explanation The loader cannot allocate a larger variable to an already loaded smaller variable.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LOADER-3-SORBER: Error: type not handled, must be .sdata or .sbss.Explanation The loader cannot handle this type.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LOADER-3-SREADE: Error: Cannot read in symbol string%LOADER-3-SREADS: Error: Cannot read in symbol tableExplanation The loader could not read a needed section of the file.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LOADER-3-STOTHER: Error: Problem: a symbol table entry is using field ST_OTHERExplanation The loader cannot handle this file.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LOADER-3-STREXE: Error: Strings exceed string table area allocated [dec] > [dec]Explanation The preallocated area is not large enough.
Recommended Action The loader must be recompiled with more area. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LOADER-3-SUNDERR: Error: not handled - Small undefined symbolExplanation The loader cannot handle variables of this type.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LOADER-3-SYMEXE: Error: Symbols exceed symbol table area allocated [dec] > [dec]Explanation The preallocated area is not large enough for loading.
Recommended Action The loader must be recompiled with more area. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LOADER-3-SYRERRExplanation An error occurred in the input file.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LOADER-3-TSHSIZ: Error: total sections headers [hex]([dec]) too large for pre-allocated area [hex]([dec]).Explanation The preallocated area is not large enough for loading.
Recommended Action The loader must be recompiled with more area. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LOADER-3-TYPERR: Error: Type value in symbol table entry not understood%LOADER-3-USRERR: Error: not handled - Undefined section reference%LOADER-3-VARHIP: Error: Symbol is HIPROC variable - not handled%LOADER-3-VARLOP: Error: Symbol is LOPROC variable - not handledExplanation The loader cannot handle variables of this type.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
CIP-LOVE Error Message
CIP error message 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 direct memory access (DMA) routines returned the wrong transfer request. The CIP recovered.
Recommended Action Report this error to your technical support representative.
CIP-MBUF Error Messages
Memory buffer (mbuf) error messages
Error Message%MBUF-0-MFREEx2: mfree: mbuf [hex] already free'ed from pc=[hex] ra=[hex] @(pc=[hex]ra=[hex])Explanation A request was made to free a memory buffer (mbuf) that was already free.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%MBUF-0-PANIC: panic[[chars]@[dec]] in [chars]: [chars]Explanation An unexpected internal error occurred in the TCP/IP stack.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
CIP-MEMD Error Messages
CIP error message related to the memory device facility.
Error Message%MEMD-3-BADIPC: IPC message received with no IPC handlerExplanation An Interprocess Communication (IPC) message was queued to the CIP, but there was no handler defined to process it. The CIP dropped the IPC message.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%MEMD-3-BADVCN: Bad vcn [dec] ([hex]), daughter board [dec]Explanation A packet was queued to the CIP, but 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.
Error Message%MEMD-3-VCNDEREGISTER: Invalid VCN ([dec]) specifiedExplanation An attempt to deregister a routine to handle data for a given virtual circuit was ignored because the virtual circuit number was out of range.
Recommended Action Try restarting the CIP. If problems persist, report the error message to your technical support representative.
Error Message%MEMD-3-VCNREGISTER: Invalid VCN ([dec]) specifiedExplanation A given virtual circuit number was out of range, preventing a routine to handle that virtual circuit number from being registered. No messages for the given virtual circuit will be accepted. Any messages that were sent to the CIP for transmission on that invalid virtual circuit will generate additional error messages.
Recommended Action Try restarting the CIP. If problems persist, report the error message to your technical support representative.
CIP-MSG802 Error Messages
CIP 802 error messages related to the IEEE 802.2cx Logical Link Control (LLC) protocol stack
Error Message%MSG802-6-ADAPTER_OPEN: Adapter [chars]/[int] now openExplanation This informational message is sent after the specified adapter opens.
Recommended Action No action required.
Error Message%MSG802-6-ADAPTER_REM: Adapter [chars]/[int] now removedExplanation This informational message is sent after the specified adapter is removed.
Recommended Action No action required.
Error Message%MSG802-6-ADAPTER_UPD: Adapter [chars]/[int] LLC parm now alteredExplanation This informational message is sent after changes have been completed to the Logical Link Control (LLC) parameters for each specified adapter.
Recommended Action No action required.
Error Message%MSG802-6-CTASET_FAIL: set cta max_conn [dec] failed ([dec] bytes free) - max conn remain at [dec]Explanation In its current configuration, the channel transport architecture (CTA) mapper cannot accept the maximum number of connections because it is low on resources such as memory. An attempt to reduce the maximum number of connections will fail.
Recommended Action CIP Systems Network Architecture (CSNA) should be run on a CIP board with at least 32 MB of memory. For all others, refer to the CIP CSNA configuration guide to determine the memory requirements for the maximum number of connections configured. Check the router configuration in the virtual interface of the CIP (x/2) for the MAX-LLC-CONNECTIONS parameter. Determine whether the device is over configured. If it is not, report this error message to your technical support representative.
Error Message%MSG802-3-HARD_ERROR: [chars]Explanation The protocol stack encountered error conditions that prevent it from continuing normal operations.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%MSG802-3-INVALID_CFGCMD: invalid config cmd detected cmd=[dec]Explanation The Logical Link Control (LLC) task detected an invalid configuration command. The command was not executed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%MSG802-6-INVALID_ID: [chars]: invalid id type = [hex]Explanation The Logical Link Control (LLC) received an invalid ID type. The LLC discarded the request.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%MSG802-3-INVALID_MSICMD: invalid msi cmd detected cmd=[dec]Explanation The Logical Link Control task detected an invalid MAC Service Interface command. The request was canceled.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%MSG802-6-INVALID_PRIMITIVE: [chars]: invalid primitive code = [hex]Explanation The Logical Link Control (LLC) received invalid service primitives. The module and routine that received the primitives along with the service primitive codes are displayed.
Recommended Action The CIP Systems Network Architecture (CSNA) should continue to operate. If problems persist, copy the error message exactly as it appears and report it to your technical support representative.
Error Message%MSG802-3-INVALID_VCN1: LAN not configured for vcn=[dec], adapter=[dec], lan=[dec], ran=[dec] - cfg cmd rejectedExplanation The configuration command could not be processed because of an invalid virtual circuit number (VCN). The command was not executed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%MSG802-3-INVALID_VCN2: LAN has configured for vcn=[dec], adapter=[dec], lan=[dec], ran=[dec] - cfg cmd rejectedExplanation The configuration command could not be processed because of an invalid virtual circuit number (VCN). The command was not executed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%MSG802-6-LLC_DUP_CCB: LLC Station Address: RMAC=[hex].[hex].[hex] LSAP=[int] RSAP=[int]Explanation An open station request was received, but the station address was already open.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%MSG802-6-LLC_DUP_SAP: LLC Duplicat SAP on interface [int] : SAP=[int].Explanation The service access point (SAP) has been opened by more than one External Communication Adaptor (XCA) major node.
Recommended Action Check the XCA node definitions.
Error Message%MSG802-6-LLC_SHUT: LLC shutdown completedExplanation The shutdown of the Logical Link Control (LLC) is complete. Both the LLC memory device (MEMD) READ/WRITE task and the TIMER task have been shutdown.
Recommended Action No action required.
Error Message%MSG802-6-LLC_START: Starting LLC-2 with a session capacity of [int]Explanation A Logical Link Control (LLC) subsystem session has begun.
Recommended Action No action required.
Error Message%MSG802-6-LLC_UNEXP_ACK: Unexpected acknowledgement - transmit not complete : pcep=[int]Explanation A frame has been acknowledged before its transmission was completed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%MSG802-6-MAX_FAILED: change max conn [dec] failed ([dec] bytes free) - max conn remain at [dec]Explanation The CIP is not able to support the maximum number of connections set in its current configuration. The CIP may be low on resources such as connections and memory. An attempt to reduce the maximum number of connections will fail.
Recommended Action Check the router configuration in the virtual interface of the CIP (x/2) for the MAX-LLC-CONNECTIONS parameter. Determine whether the device is over configured. If it is not, copy the error message exactly as it appears and report it to your technical support representative.
Error Message%MSG802-6-MAX_FAILED2: cipmsg pool empty - max conn remain at [dec]Explanation In its current configuration, the CIP cannot accept the maximum number of connections because it cannot allocate a message buffer from the CIP message pool.
Recommended Action Retry the max_llc command. If the error persists, copy the error message exactly as it appears and report it to your technical support representative.
Error Message%MSG802-6-MAX_LLC_EXCEEDED: MAX_LLC_SESSIONS([int]) exceeded - [int] sessions rejected.Explanation The maximum number of concurrent Logical Link Control (LLC) connections has been exceeded.
Recommended Action Increase the MAX_LLC_SESSIONS parameter on the CIP virtual interface.
Error Message%MSG802-3-ODD_MEMD: Odd boundary memd buffer; memd_addr=[hex]Explanation The memory device (MEMD) should never be in the odd boundary. A run-time error might have occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%MSG802-3-QUEUE_OPEN: [chars]Explanation The Logical Link Control (LLC) task detected a queue open failure. The resource is unavailable for the request.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%MSG802-3-RESOURCE_DEPLETED: [chars]Explanation The protocol stack encountered error conditions that prevent it from continuing normal operations.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%MSG802-6-SHRINK_CONN: reducing max_conn doesn't take effect until the virtual interface is restarted - max conn remain at [dec]Explanation An attempt was made to reduce the max_conn parameter. Reducing the max_conn parameter is not allowed in this release.
Recommended Action No action required.
Error Message%MSG802-6-SHUT_IN_PROG: shutdown in progress ... [chars] command rejectedExplanation The Logical Link Control (LLC) is in "shutdown cleanup" state. In this state, the LLC will reject all configuration commands.
Recommended Action Retry the command when the LLC is in "operational" state.
Error Message%MSG802-6-START802_FAILED: unable to start 802 for [dec] connections - Memory Avail = [dec] bytesExplanation The CIP is not able to bring up the channel transport architecture (CTA) 802 task. The CIP is low on resources such as connections and memory.
Recommended Action Check the router configuration in the virtual interface of the CIP (x/2) for the MAX-LLC-CONNECTIONS parameter. Determine whether the device is over configured. If it is not, copy the error message exactly as it appears and report it to your technical support representative.
Error Message%MSG802-3-UNKNOWN_EVENT: detect unknown event; event=[dec]Explanation The Logical Link Control (LLC) task detected an unknown event.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%MSG802-3-UNSUPPORTED: [chars]Explanation The Logical Link Control (LLC) task detected a request for an unsupported function. The request was canceled.
Recommended Action Copy the error message exactly as it appears, and report it 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 no interrupt routine was 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 an undefined interrupt handler. 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-OFFL Error Messages
CIP error messages related to the offload protocol.
Error Message%OFFL-6-COMMAND: Unrecognized Offload command code [dec]. xfer_element = [hex]Explanation The host sent an offload command with an invalid offload command code.
Recommended Action The CIP ignored the request. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%OFFL-3-ILLALD: Illegal data alignment: [hex] + [dec] bytes >= [hex]. xfer_element = [hex]Explanation An internal logic error occurred. A block of offload protocol parameters crossed a buffer boundary.
Recommended Action The CIP ignored the request. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%OFFL-3-ILLALH: Illegal hdr alignment detected. Address [hex] + [dec] bytes > [hex]. xfer_element = [hex]Explanation An internal logic error occurred. An offload message header crossed a buffer boundary.
Recommended Action The CIP ignored the request. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%OFFL-3-ILLEN: Illegal byte count in offload data. [dec] specified, [dec] available. xfer_element = [hex]Explanation An internal logic error occurred. The buffer length field in the offload message header does not equal the size of the data buffer.
Recommended Action The CIP assumes the offload message header contains no data. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%OFFL-0-ILLINTF: Illegal number of offload interfaces. [dec] specified, [dec] expected.Explanation The offload initialization code found an internal error.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%OFFL-3-ILLRST: Received restart with [dec] intf, [dec] is max. xfer_element = [hex]Explanation The host sent an offload restart request with too many defined interfaces.
Recommended Action The CIP ignored the request. Check your host configuration for this offload device. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%OFFL-6-LONGREC: Attempt to transmit too large a record.Explanation The amount of data read by the channel exceeded the size of the read channel command word (CCW).
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%OFFL-6-MSGLEFT: Type [dec] xfer_element in work queue after shutdown.Explanation An internal logic error occurred. The offload application received a message after a shutdown. The message was ignored.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%OFFL-3-MISRST: Received restart [chars] with unknown IP [dec].[dec].[dec].[dec]Explanation The host sent an offload restart request with an unknown IP address for the application programming interface (API) link.
Recommended Action The CIP ignored the mismatch. Correct your host configuration for this offload device.
Error Message%OFFL-0-NOMBUF: Out of mbuf's for handling socket operations.Explanation An internal logic error occurred. Not enough memory buffers were allocated to handle the current offload socket operation.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%OFFL-3-NOMEM: Not enough memory to start offload tasks.Explanation Not enough free memory is available to start the TCP/IP offload tasks. The configuration request was ignored.
Recommended Action Install more memory for the CIP, or configure fewer devices.
Error Message%OFFL-0-NOPEND: Trying to free buffer when no send is pending.Explanation An internal logic error occurred. A request to free a send buffer was made even though no send is pending.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%OFFL-6-NOTXBUF: Unable to allocate txbuf.Explanation No transmit buffers are available for sending a RESTART response.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%OFFL-3-PENDREQ: Pending request [hex] deleted due to new request [hex].Explanation An internal logic error occurred. The offload application had to save a socket request for later execution while another request of the same type was pending. The first request was dropped.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%OFFL-3-REJSOCK: Not enough memory to handle new socket. [dec] sockets open.Explanation Not enough free memory is available to open another socket. The socket request failed.
Recommended Action Install more memory for the CIP, configure fewer devices, or limit the number of sessions through this offload device.
Error Message%OFFL-3-REQFORM: Socket request [dec] uses invalid parameters. Offset [dec]: [hex].Explanation The host sent a socket request with an invalid parameter. The CIP sent an error message in respose to this request.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%OFFL-3-REQLEN: Socket request [dec] has wrong length [dec].Explanation The host sent a socket request with an incorrect length. The CIP sent an error message in respose to this request.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%OFFL-3-REQTYPE: Unknown [chars] socket request code [dec].Explanation The host sent a socket request with an unknown type.
Recommended Action The CIP ignored the request. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%OFFL-6-SOCREQ: Unrecognized socket request code [dec].Explanation The host sent a socket request with an invalid code.
Recommended Action The CIP ignored the request. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%OFFL-6-UNEXP: Unexpected Offload command code [dec]Explanation An internal logic error occurred. The request type in the offload message was valid but unexpected.
Recommended Action The CIP ignored the request. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%OFFL-6-VIRTOFFL: Offload device may not be created on a virtual port adapter.Explanation An attempt was made to configure an offload device on the virtual port adapter. Offload devices are permitted on physical port adapters only.
Recommended Action The configuration request was ignored. No action required.
Error Message%OFFL-0-WRONGFREE: Trying to free mbuf out of sequence.Explanation An internal logic error occurred. An unexpected address was specified in a request to free a buffer
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%OFFL-3-WRONGLINK: Trying to send mbuf on CLAW control link.Explanation An internal logic error occurred. An attempt was detected to send a packet in a memory buffer (mbuf) on CLAW link 0. The packet was ignored.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
CIP-SCB Error Message
CIP error message 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 = [hex] 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-PCANMIRESET: Reset of Port [dec] NMI failedExplanation After a nonmaskable interrupt from a parallel channel adapter (PCA) interface was serviced, an attempt to reset the interrupt failed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SLC-3-SCANEP1: Scan of EP ring 1 failedExplanation An attempt to scan the first set of internal latches on the Enterprise System Connection (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 Enterprise System Connection (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 Enterprise System Connection (ESCON) processor. The serial link controller did not indicate that the clock was stopped. The CIP attempted to stop the bidirectional bus (BIDI) clock.
Recommended Action Report this message to your technical support representative.
CIP-SSI802 Error Message
CIP SSI802 error messages related to the common service System Service Interface (SSI) facility
Error Message%SSI802-3-FATAL_ERROR: SSI_ASSERT failure in [chars] @ [int] - [chars]Explanation The CIP Systems Network Architecture (CSNA) encountered unrecoverable error conditions that prevented it from continuing its normal operations.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
CIP-SUBSYS Error Messages
Software subsystem error messages
Error Message%SUBSYS-2-BADCLASS: Bad subsystem clas ([dec]) - ignoring subsystemExplanation A software consistency check failed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SUBSYS-2-BADSEQUENCE: Subsystem ([chars]) has cross-class sequence for ([chars])Explanation A software consistency check failed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SUBSYS-2-BADVERSION: Bad subsystem version number ([dec]) - ignoring subsystemExplanation A software consistency check failed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SUBSYS-2-MAXRECUR: Too many levels of recursionExplanation A software consistency check failed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SUBSYS-2-MISMATCH: Kernel and subsystem version differ ([dec].[dec]) - ignoring subsystemExplanation A software consistency check failed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SUBSYS-2-NOTFOUND: Subsystem ([chars]) needs subsystem ([chars]) to startExplanation A software consistency check failed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
CIP-SYS Error Messages
CIP operating system error messages
Error Message%SYS-3-BADBLOCK: Bad block pointer [hex]Explanation At the indicated location, a block of memory is corrupt.
Recommended Action If this message recurs, copy the error message exactly as it appears and report it to your technical support representative.
Error Message%SYS-3-BADFREEMAGIC: Corrupt free block at [hex] (magic [hex])Explanation A block of memory is corrupt at the indicated location.
Recommended Action If this message recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message%SYS-3-BADFREEPTRS: Bad [chars] pointer [hex] at [hex] ([chars] = [hex])Explanation A pointer in the block header at the indicated location is corrupt.
Recommended Action If this message recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message%SYS-3-BADMAGIC: Corrupt block at [hex] (magic [hex])Explanation The free memory pool is corrupted.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SYS-2-BADSHARE: Bad refcount in [chars], ptr=[hex], count=[hex]Explanation An internal software 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%SYS-6-BLKINFO: [chars]blk [hex], words [int], alloc [hex], [chars], dealloc [hex], rfcnt [hex]Explanation An internal software 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%SYS-2-FREEBAD: Attempted to free memory at [hex], not part of buffer poolExplanation An internal software 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%SYS-2-FREEFREE: Attempted to free unassigned memory at [hex], alloc [hex], dealloc [hex]Explanation An internal software 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%SYS-3-INUSEFREE: Block [hex] on free list [dec] in useExplanation An internal software error has 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%SYS-3-INVMEMINT: Invalid memory action ([chars]) at interrupt levelExplanation A memory allocation or deallocation was attempted from an interrupt handler.
Recommended Action If this message recurs, copy the error message exactly as it appears and report it to your technical support representative.
Error Message%SYS-2-LOWMEM: Low memory debug exception (limit=[int] free=[int])Explanation The CIP is running short on memory.
Recommended Action It might be necessary to free some memory by quitting a program. If this message recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message%SYS-6-MTRACE: [chars]: addr,pc\n ADDRPC ADDRPC ADDRPC ADDRPC \n ADDRPC ADDRPC ADDRPC ADDRPC);Explanation The free memory pool is corrupt.
Recommended Action If this message recurs, copy the error message exactly as it appears and report it to your technical support representative.
Error Message%SYS-2-NOMEMFRG: Memory fragmentation check debug exception (fragment size [int])Explanation The system detected an error-checking memory fragmentation.
Recommended Action If this message recurs, copy the error message exactly as it appears and report it to your technical support representative.
Error Message%SYS-2-NOMEMORY: No memory available for [chars] [dec]Explanation An 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%SYS-3-NZREFCNT: Block [hex] on free list [dec] with ref count [dec]Explanation A block of memory in the free pool is in use. The number of processes using the memory block is indicated.
Recommended Action If this message recurs, copy the error message exactly as it appears and report it to your technical support representative.
Error Message%SYS-3-OVERRUN: Block overrun at [hex] (redzone [hex])Explanation An internal software 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%SYS-5-RELOAD: Reload requestedExplanation A reload or restart was requested.
Recommended Action Informational message. No action required.
Error Message%SYS-5-RESTART: System restarted --\n[chars]Explanation A reload or restart was requested.
Recommended Action Informational message. No action required.
Error Message%SYS-3-WRONGFREELIST: Block [hex], size [dec], on wrong free list ([dec], [dec])Explanation A freed buffer has been placed on the wrong list of free buffers.
Recommended Action If this message recurs, copy it exactly as it appears and report it to your technical support representative.
CIP-SYSMGT Error Messages
CIP error messages related to network management processing for system management remote procedure calls
Error Message%SYSMGT_RPC-3-ERROR: Error detected ([chars])Explanation An error was detected in the systems management remote procedure call processing.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SYSMGT_RPC-3-IPC_ERROR: [chars] [chars] failed ([chars])Explanation The system management remote procedure call operation failed. Requests for information from the CIP card will not be processed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SYSMGT_RPC-6-STATE_CHANGE: System Management [chars]Explanation The CIP system management subsystem has changed state.
Recommended Action This is an informational message. No action required.
CIP-TCPIP Error Message
TCP/IP CIP error message
Error Message%TCPIP-0-PANIC: panic[[chars]@[dec]] in [chars]: [chars]Explanation An unexpected internal error occurred in the TCP/IP stack.
Recommended Action Copy the error message exactly as it appears, and report it 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 Copy the error message exactly as it appears, and report it to your technical support representative.
CLNS Error Messages
OSI Connectionless Network Service error messages
Error Message%CLNS-5-ADJCHANGE: [chars] Adjacency to <neighbor id> (<interface>) <Up/Down>, <reason>Explanation An Intermediate System-to-Intermediate System (ISIS) or NetWare Link Services Protocol (NLSP) adjacency with a neighboring router has either come up or gone down. The message describes the change and the reason for it. This message will only appear if "log-adjacency-changes" is configured for the ISIS or NLSP process.
Recommended Action This message is primarily informational and will appear normally as routers and links go up or down. Unexpected adjacency loss may indicate high error rates or high packet loss in the network and should be investigated.
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])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%CLNS-1-BKUPERR: ISIS: [chars] in [hex], ndb_next [hex], ndb_prev [hex], lsp_next [hex], lsp_prev [hex], metric [hex], index [dec], [chars] [hex]Explanation An internal error occurred in the maintenance of the Intermediate System-to-Intermediate System (ISIS) backup route table.
Recommended Action Copy the error message exactly as it appears and copy down the router's configuration along with any other relevant information. Contact your technical support representative for assistance.
Error Message%CLNS-4-CKSUMERR: [chars]: L[dec] LSP [chars] database checksum error, restartingExplanation 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%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-1-LINKERR: ISIS: [chars] in [hex], lsp_next [hex], lsp_prev [hex], index [dec], ver [dec], [chars] [hex]Explanation An internal error occurred in the maintenance of Intermediate System-to-Intermediate System (ISIS) or NetWare Link Services Protocol (NLSP) link-state packet (LSP) linkages.
Recommended Action Copy the error message exactly as it appears and copy down the router's configuration along with any other relevant information. Contact your technical support representative for assistance.
Error Message%CLNS-3-LSPCHAIN: [chars]: non-null [chars] pointer [hex] on freed LSP, index [dec]Explanation An internal error occurred in the Intermediate System-to-Intermediate System (ISIS) or NetWare Link Services Protocol (NLSP).
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CLNS-4-LSPCKSUM: ISIS: Bad <level> LSP <LSP ID> checksum received on <interface>, bad count <error count>%CLNS-4-LSPCKSUM: NLSP: Bad <level> LSP <LSP ID> checksum received on <interface>, bad count <error count>Explanation A link-state packet (LSP) was received for either Intermediate System-to-Intermediate System (ISIS) or NetWare Link Services Protocol (NLSP) which failed an internal data checksum, but which had passed the datalink checksum. The interface on which the LSP was received is indicated, along with the total count of checksum errors received, the LSP ID, and the level of the failing LSP. This usually indicates data corruption occurring on a link but may also indicate data corruption in memory in a neighboring router.
Recommended Action If the error is in a neighboring router's memory, the problem will correct itself within 15 minutes (since that router will detect its internal error and regenerate the corrupted data). This case is usually indicated by a single LSP ID appearing repeatedly in these messages (and the same LSP ID may appear in this message on other routers).
If datalink corruption has caused the error, the link should be checked for errors and dealt with appropriately. This case is usually indicated by a number of different LSP IDs appearing in these messages.
Error Message%CLNS-3-LSPDB: [chars]: Inconsistent LSPIX entry, lsp [hex], index [dec], ixentry [hex], ixentry->lsp [hex]Explanation An internal error occurred in the Intermediate System-to-Intermediate System (ISIS) or NetWare Link Services Protocol (NLSP).
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CLNS-4-LSPFULL: [chars]: L[dec] LSP filled to capacity, dropping routes, 10*ONEMINExplanation 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%CLNS-3-LSPIXARRMATCH: [chars]: LSPix entry [dec] mismatch with LSP [hex], LSP [chars] is [dec], entry [dec]Explanation An internal error occurred in the Intermediate System-to-Intermediate System (ISIS) or NetWare Link Services Protocol (NLSP).
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CLNS-3-LSPIXARRNULL: [chars]: LSPix entry [dec] should be null, is [hex]%CLNS-3-LSPIXHEAD: [chars]: LSPix [chars] [dec] head [hex] doesn't match first prev [hex]Explanation An internal error occurred in the Intermediate System-to-Intermediate System (ISIS) or NetWare Link Services Protocol (NLSP).
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
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 Copy the error message exactly as it appears, and report it to your technical support representative.
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.
Error Message%CLNS-3-ONLIST: [chars]: entry already threaded, prev [hex], next [hex], index [dec], ver [dec]Explanation An internal error occurred in the Intermediate System-to-Intermediate System (ISIS) or NetWare Link Services Protocol (NLSP).
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CLNS-4-TENT: [chars]: [chars]Explanation An internal error occurred in the Intermediate System-to-Intermediate System (ISIS) or NetWare Link Services Protocol (NLSP).
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
CLS Error Message
Cisco Link Services error message
Error Message%CLS-3-CLSFAIL: CLS: Assertion failed: [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.
CLSDR Error Messages
Cisco Link Services Driver error messages
Error Message%CLSDR-3-ERRRTN: [chars] failed error [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-NOCEP: Cannot found cep in free poolExplanation 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%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 [hex] not on listExplanation The destination logical unit (DLU) is trying to remove a nonexistent 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 [hex] not on listExplanation The destination logical unit (DLU) is trying to remove an nonexistent 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 Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%COMP-5-NOBUF: Interface [chars] [chars]Explanation Interface serial0 compression getbuffer failed, causing Link Access Procedure, 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-FIRMWARE Controller [chars], [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%CONTROLLER-2-NOTFOUND: Controller not found for slot [dec].Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
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
Data bus error messages
Error Message%DBUS-3-BADCTRLRTYPE: 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: 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. Copy the error message exactly as it appears, and report it to your technical support representative.
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 Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%DBUS-3-SW_NOTRDY: DBUS software not ready after > [chars], elapsed [dec], status [hex], control [hex]Explanation An interface processor failed to come on line after being reset. 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%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 Copy the error message exactly as it appears, and report it to your technical support representative.
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 Copy the error message exactly as it appears, and report it to your technical support representative.
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-WCSFLOW: Slot [dec], flow cntrl error loading WCS, last data [hex] pos [dec]Explanation A processor has indicated an error condition while downloading microcode. The status, cmd/data, and position numbers shown in the message reflect the error condition, the last byte of microcode loaded, and the position in the file, respectively. If this error appears, the microcode download is aborted, and the ROM microcode is loaded.
Recommended Action If this error message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%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 Copy the error message exactly as it appears, and report it to your technical support representative.
DIALER Error Messages
Dial-on-demand routing (DDR) error messages
Error Message%DIALER-2-NOMEMORY: No memory to send dialer kicker packet out interface [chars]Explanation 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: 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 Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%DLC-3-NOMEMORY: no memory for [chars]Explanation There was not enough free memory to complete the operation.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%DLC-4-OPTNULL: 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 typeExplanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
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 Copy the error message exactly as it appears, and report it to your technical support representative.
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 nonCisco 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 nonCisco 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 Copy the error message exactly as it appears, and report it to your technical support representative.
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 Copy the error message exactly as it appears, and report it to your technical support representative.
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 Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%DLSWC-3-NOPARAM: dlsw_action, null param blk%DLSWC-3-NOPEER: 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: 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-PCAPMISMATCH: DLSw: [chars]: [chars]Explanation Priority keyword was used on one router but not on the other. The priority keyword is an option on the DLSW remote peer definition. If priority keyword is used one router, it must be used on the other.
Recommended Action If you wish to use prioritization, use it on both routers.
Error Message%DLSWP-3-PGENERAL: 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: 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: 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.
DMA Error Messages
Direct memory access error messages
Error Message%DMA-1-BADICBPTR: msg_badicbptrExplanation An internal software error occurred.
Recommended Action If this error message recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message%DMA-1-BADJUMPSTART: DMA jumpstart failed [dec]Explanation An anomalous situation where the Direct Memory Access (DMA) jumpstart mechanism failed to find the DMA to start.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%DMA-1-BADLENGTH: msg_badlengthExplanation VIP found that the memory device (MEMD) buffer header indicated a zero length transmit.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%DMA-1-BADOWN: msg_badownExplanation This message indicates that an unexpected own bit was found in a DMA entry.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
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 packetExplanation 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) DSX-1 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: Route [chars], [dec] successors, [dec] rdbsExplanation 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%DUAL-3-BADSUMNOTIFY: Dual notified us about summary [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%DUAL-6-EVENT: [chars], [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%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 Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%DUAL-3-LINKSTILLUP: Link [dec] [chars] still exists on [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%DUAL-3-NOBUFFER: No buffers available for [dec] byte packetExplanation 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 Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%DUAL-3-NOMATCH: Nexthop and infosource don't match. N = [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%DUAL-3-NOMEMORY: No memory available for [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%DUAL-3-NOSOCKET: Unable to open socket for AS [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%DUAL-3-SIA: Route [chars] stuck-in-active state in [chars] [dec]. Cleaning upExplanation 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%DUAL-3-SIANOHANDLE: Stuck-in-active and unallocated handle in reply-status table. Cleaning upExplanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
DVMRP Error Messages
Distance Vector Multicast Routing Protocol (DVMRP) error messages
Error Message%DVMRP-1-BADMASK: Bad mask [int] received from [int], Report ignoredExplanation 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%DVMRP-1-ROUTEHOG: Receiving [dec] routes from [int] ([chars]) in the last [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.
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 Copy the error message exactly as it appears, and report it to your technical support representative.
ENV Error Messages
Environmental monitor card error messages
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. Copy the error message exactly as it appears, and report it to your technical support representative.
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 Copy the error message exactly as it appears, and report it to your technical support representative.
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 Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%FDDI-3-FDDIRSETU: Unit [dec], Error ([char]-04x) [chars] - fddi_reset()Explanation FDDI-related command execution failure.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%FDDI-3-NOCAM: Unit [dec], No CAM exists for this interface.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%FDDI-1-NOMEMORY: msgtxt_nomemoryExplanation The FDDI Management Information Base/Station Management (MIB/SMT) processing functions could not initialize due to insufficient memory.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
FDDISTAT Error Message
Fiber Distributed Data Interface (FDDI) state error message
Error Message%FDDISTAT-4-STATUS: FDDI state [chars] detected on interface [chars]Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
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 nonvolatile memory error messages
Error Message%FLASH-3-ACCESSATTRIBONRP: [chars]Explanation The route processor cannot access the flash card's attribute memory. The flash card should continue to operate normally.
Recommended Action If there is still a problem with the flash card, copy the error message exactly as it appears and report it to your technical support representative.
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 Messages
Frame Relay error messages
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 Copy the error message exactly as it appears, and report it to your technical support representative.
GRIP Error Messages
Xerox Network Systems (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 Copy the error message exactly as it appears, and report it to your technical support representative.
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 Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%HD-1-BADPORTADAPTER: [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%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: msgtxt_nomemoryExplanation The requested operation could not be accomplished because of a low memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%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 Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%HUB-1-BADUNIT: Bad port number [dec]Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%HUB-1-NOMEMORY: msgtxt_nomemoryExplanation 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 Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%HUB-1-WRITEERR: Write op [dec] not allowedExplanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
IBM2692 Error Messages
Error messages which refer to an IBM Token Ring chip set
Error Message%IBM2692 -1-ADP_CHK: msg_adaptor_checkExplanation A hardware failure occurred. 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 A hardware failure occurred.
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 A hardware failure occurred. 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 The router or access server 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 The router or access server 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 protocol control information (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 receiving (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 Copy the error message exactly as it appears, and report it to your technical support representative.
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.
Error Message%IP-3-LOOPPAK: Looping packet detected and dropped - \nsrc=[int], dst=[int], hl=[int], tl=[int], prot=[int], sport=[int], dport=[int] \nin=[chars], nexthop=[int], out=[chars]\noptions=[chars], 1 * ONEMINExplanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%IPC-5-NODELFUNC: Delayed init function not availableExplanation A software or hardware error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
IPC Error Messages
Interprocess Communication error messages
Error Message%IPC-2-CANT_SEND: Cannot send IPC message: [chars]Explanation An error occurred in the IPC slave discovery mechanism. It might result in a malfunction in the operation of the IPC.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%IPC-2-CONSISTENCY: 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: Attempt to delete an IPC message ([hex]) a second time.Explanation An internal inconsistency was found in some IPC data structures.
Recommended Action Informational message only. No action required.
Error Message%IPC-2-LOCK: 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 cannot be initialized because its initialization function does not appear in the IPC initialization function list.
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.Explanation The IPC user failed to provide any means of handling the received message.
Recommended Action Informational message only. No action required.
Error Message%IPC-2-NOMEM: No memory available for [chars].Explanation The IPC protocol subsystem could not obtain the memory it needed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%IPC-2-ONINT: Called from interrupt level: [chars]Explanation The IPC user attempted a prohibited call into IPC while IPC was 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 Versatile Interface Processor (VIP) card, generated this message. The error message has been passed up to the Route Processor or Route Switch Processor (RP/RSP) for display. This message appears 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: 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.
Error Message%IPC_RSP_CBUS-3-CARDERR: [chars]Explanation An IPC card has registered itself to the IPC master twice. The card malfunctioned and its IPC is not active.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%IPC_RSP_CBUS-3-INVNUM: [chars] ([dec])Explanation The IPC application tried to send a message which was larger than IPC could handle. The message was not transmitted.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%IPC_RSP_CBUS-3-MSGERR: [chars] ([dec])Explanation The slave IPC can not register with master. It cannot exchange messages with the master.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%IPC_RSP_CBUS-3-NOBUF: [chars]Explanation The IPC ran out of memory device (MEMD) buffers.
Recommended Action Reduce the number of applications currently running on the IPC. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%IPC_RSP_CBUS-3-NOHWQ: Hardware queue for card at slot [dec] not foundExplanation IPC messages can not be transmitted due to a missing hardware queue. The messages were discarded and subsequent messages will not be transmitted to that card.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%IPC_RSP_CBUS-3-PROC: [chars] ([dec])Explanation IPC processes can not be created due to operating system errors. The IPC will be inactive.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%IPC_RSP_CBUS-3-SEATERR: [chars] ([dec])Explanation The ID associated with an IPC card is either missing, duplicated, or can not be created.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
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 Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%IPFAST-7-INTLEV: 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: 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: 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: Error trying to delete prefix entry for [dec] [dec] (expected [hex], got [hex])Explanation Problems related to the IP route cache triggered this debugging message.
Recommended Action The router should correct for this error. If the router cannot forward packets properly or is experiencing other problems, 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 Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%IPFAST-4-RADIXINSERT: Error trying to insert prefix entry for [dec] [dec] (expected [hex], got [hex])Explanation Problems related to the IP route cache triggered this debugging message.
Recommended Action The router should correct for this error. If the router cannot forward packets properly or is experiencing other problems, copy the error message exactly as it appears and report it to your technical support representative.
Error Message%IPFAST-3-SANITY: Found existing [chars] specific entry [dec] [ip mask]..[ipmask]->[dec] ([chars]) when " "attempting to create [dec] [ipmask]..[ipmask]->[dec] ([chars])Explanation Problems related to the IP route cache triggered this debugging message.
Recommended Action The router should correct for this error. If the router cannot forward packets properly or is experiencing other problems, 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: 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: Bad path index of [dec] for [inet], [dec] max, ONEMINExplanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
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 Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%IPX-3-BADIGRPSAPTYPE: Unsupported SAP type for EIGRP being [chars] - type [hex]Explanation There are two types of service access points (SAPs), general queries and general responses. This message is sent when you receive or attempt to send an SAP with a type code which is not a general query or a general response. It is also sent when you receive a general query not addressed to the broadcast address.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
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 Copy the error message exactly as it appears, and report it to your technical support representative.
ISDN Error Messages
Integrated Services Digital Network (ISDN) error messages
Error Message%ISDN-6-CONNECT: Interface [chars] is now connected to [chars] [chars]Explanation This is an informational message. It is sent when a call is connected. The message displays the remote name and number, which it receives from the Point-to-Point Protocol (PPP) authentication or from where the dialer placed the call to.
Recommended Action No action is required.
Error Message%ISDN-6-DISCONNECT: Interface [chars] disconnected from [chars] [chars], call lasted [int] secondsExplanation This is an informational message. It is sent when a call is disconnected. The message displays the remote name and number, which it receives from the Point-to-Point Protocol (PPP) authentication or from where the dialer placed the call to. It also shows how long the call lasted.
Recommended Action No action is required.
LANCE Error Messages
Local Area Network Controller Ethernet interface error messages
Error Message%LANCE-4-BABBLE: Unit [dec], babble error, csr0 = [hex]Explanation An Ethernet interface is malfunctioning.
Recommended Action
1
2
•
3
•
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: 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: 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: [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 Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LANE-3-LANE_SIG_INV_STATE: 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 Copy the error message exactly as it appears, and report it to your technical support representative.
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_CFG: [chars] CFG_REQ failed, [chars] (LECS returned [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%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 noninteroperable LANE configuration server, LANE server, or LANE client implementation on the emulated LAN.
Error Message%LANE-3-LEC_ERR: [chars], 10*ONESECExplanation 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%LANE-6-LEC_INFO: [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%LANE-3-LEC_JOIN: [chars] JOIN failed, [chars] (LES returned [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%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 Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LANE-4-LEC_STATE_ERROR: State: [dec], Event [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%LANE-6-LEC_TIMER: Timer [chars] expiredExplanation 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%LANE-3-LECS_ERR: [chars]Explanation An internal consistency error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LANE-4-LECS_WARN: [chars]Explanation The LAN Emulation Configuration Server (LECS) address could not be registered with or de-registered from the switch, using Interim Local Management Interface (ILMI).
Possible causes
•
•
•
•
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LANE-3-LSV_ADDR: [chars] elan [chars] unable to register LES/BUS ATM addrExplanation 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%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: <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: 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 subinterface 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: 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.
Error Message%LANE-5-UPDOWN: [chars] [chars] [chars]: [chars] changed state to [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.
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 Procedure, 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 Copy the error message exactly as it appears, and report it to your technical support representative.
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 Copy the error message exactly as it appears, and report it to your technical support representative.
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 interface descriptor block (IDB) driver.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%LINK-3-BOGUSENCAP: msgtxt_badencapExplanation A serial interface has been configured with an unknown encapsulation.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
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. Copy the error message exactly as it appears, and report it to your technical support representative.
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 Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LINK-4-FDDISTAT: Interface [chars], FDDI state [chars] detectedExplanation There was a state change on the FDDI ring.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
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 Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%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: 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-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.
Error Message%LLC-2-UNEXPECT: 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.
LNMC Error Messages
LAN network manager system error messages
Error Message%LNMC-3-BADCLSI: [chars] primitive not valid for lnm [hex] [hex]
%LNMC-3-BADCLSICNF: [chars] Invalid confirm [chars] [cha [chars]%LNMC-3-BADCLSIDATALEN: [chars] Bad data len =[dec] [hex]%LNMC-3-BADCLSIHDRLEN: [chars] Bad header len = [hex] [hex] [chars]%LNMC-3-BADCLSIIDTYPE: [chars] Invalid ID type = [hex] [hex] [chars]%LNMC-3-BADCLSIIND: [chars] Invalid indication [chars], [chars]%LNMC-3-BADCLSIPRIMTYPE: [chars] Invalid primitive type = [hex] [hex] [chars]%LNMC-3-BADCLSIRET: [chars] Invalid ret code [hex] [hex] [chars] [chars]%LNMC-3-BADCLSISAP: [chars] Bad clsi SAP id = [hex] [chars]Explanation A LAN network manager system error occurred.
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 Message
High-Level Data Link Control (HDLC) controller error message
Error Message%M32-1-NOMEMORY: msgtxt_nomemoryExplanation 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. Copy the error message exactly as it appears, and report it to your technical support representative.
MAILBOX Error Messages
ChipCom mailbox error messages
Note
Error Message%MAILBOX-3-BADCHKSUM: Checksum failed. Expected = [hex], calculated = [hex]. Ignoring PDU.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%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 [hex] 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 [hex] 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 Copy the error message exactly as it appears, and report it to your technical support representative.
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 Copy the error message exactly as it appears, and report it to your technical support representative.
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 Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%MCI-4-TESTFAIL: Unit [dec] failed [chars] test, skippingExplanation A hardware component failed an internal diagnostic test.
Recommended Action You need to replace the malfunctioning component. Copy the error message exactly as it appears, and report it to your technical support representative.
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.
MROUTE Error Messages
Multicast route error messages
Error Message%MROUTE-2-RADIXINIT: Error initializing IP multicast radix for [int]Explanation There isn't enough memory to initialize the IP multicast routing table.
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%MROUTE-4-RADIXDELETE: Error trying to delete multicast route entry [int]/[dec] for [int] (expected [hex], got [hex])Explanation An error in the multicast routing table occurred. A route could not be deleted from the routing table.
Recommended Action Execute a clear ip mroute command. Determine whether the router is low on memory. If the problem persists, copy the error message exactly as it appears and report it to your technical support representative.
Error Message%MROUTE-4-RADIXINSERT: Error trying to add multicast route entry [int]/[dec] for [int] (expected [hex], got [hex])Explanation An error in the multicast routing table occurred. A route could not be inserted in the routing table.
Recommended Action Execute a clear ip mroute command. Determine whether the router is low on memory. If the problem persists, copy the error message exactly as it appears and report it to your technical support representative.
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 Copy the error message exactly as it appears, and report it to your technical support representative.
NHRP Error Message
Next Hop Resolution Protocol error message
Error Message%NHRP-3-NOBUFFER: No buffer available for sending packetExplanation 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 Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%NIM-2-BADNIMREV: Unsupported version of [chars] NIM in slot [dec]|> Version [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-DEADICHAINQ: Attempted to manipulate uninitialized ichainQ in [chars]\nExplanation 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%NIM-2-LOSTICHAINQ: Couldn't find idb [hex] in ichainQ in [chars]\nExplanation 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%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 reoccurs, it may indicate a hardware failure. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%OIR-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 does 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.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%OSPF-4-BADLSATYPE: LOG_WARNING: Invalid lsa type [dec] in LSA [dec], [dec] from [dec], OSPF_COMPLAIN-IVLExplanation The router received an LSA with invalid LSA Type. The cause is either memory corruption or unexpected behavior on a router.
Recommended Action From neighbor address, locate the problem router and reboot it. To determine what is causing this problem, call your technical support representative for assistance.
Error Message%OSPF-4-CONFLICTING_LSAID: Found lsa type [dec] in LSA [inet], [inet] from [inet], [chars]Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%OSPF-4-ERRRCV: Received invalid packet: [chars] from [inet], [chars]Explanation An invalid OSPF packet was received. Details are included in the error message. The cause might be a misconfigured OSPF or an internal error in the sender.
Recommended Action Check the OSPF configuration of the receiver and the sender for inconsistency.
Error Message%OSPF-3-INTERNALERR: Internal error: [chars], OSPF_COMPLAIN_IVLExplanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%OSPF-3-NOBACKBONE: Flagged as being an ABR without a backboneExplanation The router was flagged as an Area Border Router (ABR) without backbone area in the router.
Recommended Action Restart the OSPF process.
Error Message%OSPF-3-NOCONNDB: No database entry for connected address [int]Explanation While calculating OSPF routes, the router could not find the link-state advertisement that represents the connected route in the router.
Recommended Action Clear the IP routes in the routing table by entering the command clear ip ro.
Error Message%OSPF-3-NOLSA: Failed to find this router LSA in [chars]Explanation The router is not able to find its own router link-state advertisement. This can occur occasionally and self-correct. However, if this message recurs, restart the OSPF process.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%OSPF-3-NOMEMORY: 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%OSPF-4-NONEIGHBOR: Received [chars] from unknown neighbor [inet]Explanation OSPF hello, database description, or database request packet was received, but the router could not identify the sender.
Recommended Action This situation should correct itself. If the message recurs, call your technical support representative for assistance.
Error Message%OSPF-4-NORTRID: Could not allocate router IDExplanation OSPF failed while attempting to allocate a router ID from the IP address of one of its interfaces.
Recommended Action Make sure that there is at lease one interface that is up and has a valid IP address. If there are multiple OSPF processes running on the router, each process needs its own unique router ID. You must have enough "up" interfaces so that each of them can obtain a router ID.
Error Message%OSPF-6-NOSRCPDB: ex_route_callback(): Can't find the src protocol to redistribute net [inet] [inet]Explanation OSPF attempted to redistribute a route but could not fine a valid source protocol.
Recommended Action No action is required.
Error Message%OSPF-6-NOTREDIST1: ex_route_callback(): do not redistribute net [inet] [inet], [chars]Explanation For information only.
Recommended Action No action is required.
Error Message%OSPF-6-NOTREDIST3: build_ex_route(): don't redistribute net [inet] [inet], [inet] advertises it alreadyExplanation For information only.
Recommended Action No action is required.
Error Message%OSPF-4-NOTREDIST4: Database scanner: external LSA [inet] [inet] is lost, reinstallsExplanation The software detected an unexpected condition. The router will take corrective action and continue.
Recommended Action Record the entire error message and note any OSPF problem you experience. Report the error message to your technical support representative.
Error Message%OSPF-4-NOTREDIST5: db_free: external LSA [inet] [inet],Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%OSPF-4-OSPFINTDOWN: Interface [chars] is up but OSPF state is down. Clean up, OSPF_COMPLAIN_IVLExplanation An inconsistency in an internal state was found and corrected.
Recommended Action Informational message only. No action required.
Error Message%OSPF-3-UNKNOWNSTATE: Reached unknown state in neighbor state machineExplanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%OSPF-4-VIRTUAL_IN_NON_BACKBONE: Virtual link information found in non-backbone area: [chars], OSPF_COMPLAIN_IVLExplanation An internal error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
PA Error Messages
Port adapter error messages
Error Message%PA-2-BADIDB: PA interface idb incorrect, [hex]Explanation The port adapter system control block (PASCB) data structure indicates a zero interface descriptor block (IDB).
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%PA-2-BADINTERFACE: msg_badsubunitExplanation The software specified an out-of-range port adapter interface.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%PA-1-BADPABAY: msg_badbayExplanation The software specified an out-of-range port adapter bay.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%PA-2-BADPASCB: PA interface pascb incorrect, [hex]Explanation The port adapter system control block (PASCB) data structure was incorrectly set in the command data structure.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%PA-2-UNDEFPA: msg_undefpaExplanation The software already has a driver for that port adapter type in the specified bay.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%PA-2-UNDEFPABRIDGE: msg_undefpabridgeExplanation The software does not have a driver for that port adapter protocol control information bridge in the specified bay.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
PAD Error Messages
X.25 packet assembler/disassembler error messages
Error Message%PAD-3-GETLINE: Tty[t-line], bad return code [dec] fromx3_getline()%PAD-2-INTR: [chars] called at interrupt level [hex]%PAD-2-PUTSETUP: Tty[t-line], buffer already setupExplanation An internal software error occurred.
Recommended Action If any of these messages recur, copy the error message exactly as it appears and report it to your technical support representative.
PARSER Error Messages
Parser error messages
Error Message%PARSER-4-ADRANGE: Bad range <[dec]-[dec]> for command '[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%PARSER-4-BADCFG: Unexpected end of configuration file.Explanation This message occurs when a configuration is read from the Trivial File Transfer Protocol (TFTP) server or nonvolatile RAM (NVRAM) and the end of the file is encountered before the end statement. The configuration may be corrupted or incomplete. What was read is in effect.
Recommended Action Make sure the configuration is good then execute either a copy running-config startup-config command to write the good configuration to NVRAM, or a copy running-config tftp command to write to a network TFTP server.
Error Message%PARSER-3-BADSUBCMD: Unrecognized subcommand in Function: [chars] Command: `[chars] Switch value: [dec]%PARSER-3-CREATEINT: Can't create any more subinterfaces%PARSER-4-INVLDLINE: Invalid line in NV generation: [chars]%PARSER-4-LINKPOINT: Parser reached link_point%PARSER-4-MULFUNCS: Unknown test in test_multiple_funcs [char]%PARSER-4-MULTIPLEIFS: interface_action: multiple ifs present when unit_only set%PARSER-3-NOLINK: no link_point [dec] in the [chars] [chars] command chain%PARSER-4-NUMHELP: general_number_short_help: Invalid [chars] number flag%PARSER-4-NVGEN: nvgen_token called but csb->nvgen not set%PARSER-4-PROTOADDR: protoaddr_action: Unknown link_type [dec]Explanation The parser failed an internal software check.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%PARSER-2-INTDISABLE: Interrupts disabled in mode [chars] by command '[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%PARSER-3-NOMEMORY: [chars]: no memory for [chars]Explanation A memory allocation failed, possibly because the router is out of memory, or because the parser is using more memory than it should.
Recommended Action If the router is running out of memory, reduce other system activity to ease memory demands. If the router has sufficient memory but the parser is low on memory, call your technical support representative for assistance.
PCBUS Error Messages
PCbus (PC ISA-to-AccessPro router interface) error messages
Error Message%PCBUS-3-BADENCAP: msgtxt_badencapExplanation A nonHDLC encapsulation packet was received. The packet will be treated as an HDLC packet and subsequently be dumped.
Recommended Action An informational message only. No action required
Error Message%PCBUS-1-NOMEMORY: msgtxt_nomemoryExplanation This message is logged (via the global logging command) when an attempt to get packet memory or data memory fails. The router will crash right after the error is logged.
Recommended Action An informational message only. No action required.
PPP Error Messages
Point-to-Point Protocol error messages
Error Message%PPP-4-CONFNAK: fsm_rconfnak([hex]) - possible CONFNAK loopExplanation The remote and local PPP cannot agree on a set of options that both can perform.
Recommended Action If this message recurs, copy the error message exactly as it appears and report it to your technical support representative.
Error Message%PPP-4-IPXNET: mismatched IPX network numbers. Ours = [hex], theirs = [hex]Explanation The two ends of a serial link have different IPX network numbers.
Recommended Action Confirm the configuration of both devices.
Error Message%PPP-6-LOOPED: The line appears to be looped backExplanation The communications line appears to be echoing the characters that are sent to it.
Recommended Action Check your data communications equipment to make sure it is configured correctly.
Error Message%PPP-4-NOEXTTACACS: PPP TACACS is configured but extended TACACS is not.Explanation PPP was configured to use TACACS, but extended TACACS was not configured or was disabled.
Recommended Action Either issue the no ppp use-tacacs command to stop PPP from using TACACS, or issue the tacacs-server extended command to enable extended TACACS.
QA Error Message
Queue and accumulator error message
Error Message%QA-3-ALLOC: [chars]Explanation This is a software error.
Recommended Action Copy the error message exactly as it appears. Also copy the output of show version and show cont cbus. Contact your technical support representative.
QLLC Error Messages
Qualified Logical Link Control error messages
Error Message%QLLC-3-BADOPCODE: Opcode [chars] is invalidExplanation Either remote source-route bridging or local acknowledgment is configured incorrectly.
Recommended Action Verify that remote source-route bridging and local acknowledgment are configured correctly.
Error Message%QLLC-3-BADQLLCSTATE: Bad QLLC state - [chars]Explanation An invalid QLLC primitive was detected.
Recommended Action Verify that the partner QLLC device is configured correctly.
Error Message%QLLC-3-BADRSRBOPCODE: Bad opcode [hex] from [enet] to [enet]Explanation Either remote source-route bridging is incorrectly configured, or the other RSRB device is down.
Recommended Action Verify that remote source-route bridging is configured correctly with the right version of the IOS software.
Error Message%QLLC-3-BADSTATE: Bad QLLC state - [chars] - [enet]Explanation An invalid LLC primitive was detected.
Recommended Action Verify that the Token Ring ports and any participating LAN devices are configured correctly.
Error Message%QLLC-3-BADSTATEEVENT: Bad QLLC state - [chars] event - [chars] macaddr - [enet]Explanation The LLC primitive specified placed the router in an invalid state.
Recommended Action Verify that the Token Ring ports and any participating LAN devices are configured correctly.
Error Message%QLLC-3-BAD_SUBADDRESS: [chars] is not a subaddress of [chars]Explanation A remote X.25 device is calling the router for QLLC service using an X.121 address that is not a proper subaddress of the router's X.121 address.
Recommended Action Enable subaddressing on the router, and make sure that the remote X.25 device uses the correct subaddress for the QLLC service it will use.
Error Message%QLLC-3-DIFFPRTR: [enet] - Different partner - originally [enet] - now [enet]Explanation The partner for this QLLC virtual MAC address does not match the MAC address that was defined with the qllc partner command.
Recommended Action Verify that the qllc partner statement in the configuration file is correct.
Error Message%QLLC-3-GENERRMSG: [chars]Explanation The text string provided with this error message describes the specific QLLC problem.
Recommended Action Follow the instructions that appear with the error message. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%QLLC-3-IFRAME: [chars]Explanation An I-Frame was discarded due to network congestion.
Recommended Action Verify that the LAN is not beaconing and that it is not in a congested state. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%QLLC-3-INCALL_CFG: Incoming call: No QLLC Service Access Point Configured for x.25 subaddress [chars]Explanation A remote X.25 device is calling the router for QLLC service using a subaddress that was not configured by the X.25 routing facility. The subaddress was not configured for QLLC service.
Recommended Action Correct the QLLC configuration. Configure only the subaddress on the QLLC service, not the complete X.121 address that the remote X.25 device uses.
Error Message%QLLC-3-LNXNOTFOUND: lnx_remove_macaddr_hash did not find target lnxExplanation The qllc srb command was not defined for this interface.
Recommended Action Add a valid qllc srb statement for this serial interface.
Error Message%QLLC-3-NOLLC2: Unable to open an llc2 sessionExplanation An LLC2 session could not be established with the destination MAC address.
Recommended Action Verify that the qllc partner statement in the configuration file is correct, and that the partner is on the desired LAN.
Error Message%QLLC-3-NOMACADDR: No lnx entry for macaddr [enet]Explanation No virtual MAC address was defined for this interface.
Recommended Action Define the virtual MAC address, using either the x25 map qllc or the x25 pvc qllc command.
Error Message%QLLC-3-NOMEM: Not enough memory availableExplanation There is not enough memory in the system to complete this request.
Recommended Action Add more memory to the router. Otherwise, reduce the configuration or the load on the router.
Error Message%QLLC-3-NONULLXID: Couldn't make null xid - [enet] -[enet]Explanation An attempt to create an IEEE XID failed.
Recommended Action Verify that the qllc partner statement in the configuration file is correct, and that the partner is on the desired LAN.
Error Message%QLLC-3-NOPAKENQ: Pak enqueue failedExplanation A packet was not sent to the LAN.
Recommended Action Verify that the LAN partner is configured correctly, and that the partner is on the desired LAN.
Error Message%QLLC-4-NOQLLC: Unable to open qllc session; current statue is [chars]Explanation A QLLC session could not be established.
Recommended Action Verify that the qllc partner and the qllc xid commands are correct.
Error Message%QLLC-3-NO_QLLCBUFFER: M bit Reassembly failed - couldn't allocate a packetExplanation The router ran out of memory to allocate buffers.
Recommended Action Make sure that the router configuration is adequate for the service expected of it. You may want to tune the buffer pools, or upgrade to a larger router. At the very least you will need more memory.
Error Message%QLLC-3-NO_QSR: No QLLC Service Access Points defined, (10 * ONESEC)Explanation No QLLC services have been configured, even though the router will accept incoming calls for QLLC.
Recommended Action Configure the QLLC service required.
Error Message%QLLC-3-NO_RESOURCE: Incoming Call: Insufficient resources available, (10 * ONESEC)Explanation This message is reporting insufficient system memory.
Recommended Action Upgrade the memory.
Error Message%QLLC-3-NOXID2: Couldn't make xid - [enet] -[enet]Explanation The QLLC XID could not be forwarded to the LAN.
Recommended Action Verify that the qllc partner and the qllc xid commands are correct.
Error Message%QLLC-3-NULLPTR: [chars] ptr is nullExplanation The specified structure was not configured.
Recommended Action Confirm the configuration commands for the structure.
Error Message%QLLC-3-QLLCMAP_ERR: Incoming call: QLLC map entry not found, (10 * > ONESEC)Explanation A software error in the router code occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
QUICC Error Messages
MC68360 Quad Integrated Communications Controller error messages
Error Message%QUICC-5-COLL: Unit [dec], excessive collisions. Retry limit [dec] exceededExplanation An Ethernet cable is broken or unterminated.
Recommended Action Check cables for proper connections, termination, and so on.
Error Message%QUICC_ETHER-3-UNDERFLO: Unit [dec], underflow errorExplanation While transmitting a frame, the ethernet controller chip's local buffer got starved of data because data could not be transferred to the chip fast enough to keep pace with its output rate. Normally, such a problem is temporary, depending on transient peak loads within the system.
Recommended Action The system should recover. No action required.
If the problem reoccurs, it indicates a hardware error that may be related to data traffic patterns. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%QUICC-5-HBEAT: Unit [dec], heartbeat check failureExplanation The Ethernet transceiver is malfunctioning.
Recommended Action Replace the hardware.
Error Message%QUICC-5-LATECOLL: Unit [dec], late collision errorExplanation The Ethernet cable might be too long, or there could be too many repeaters such that the delay from one end to the other is too long. The Ethernet cable might be overloaded with too many users.
Recommended Action Verify that your Ethernet cable is the correct length and that you do not have too many repeaters in use. If these are not the problem, try removing hosts from the Ethernet segment to reduce the load.
Error Message%QUICC-5-LOSTCARR: Unit [dec], lost carrier. Transceiver problem?Explanation The Ethernet 10BaseT cable is unplugged.
Recommended Action Connect the 10BaseT Ethernet cable.
Error Message%QUICC-1-NOMEMORY, 0, msgtxt_nomemoryExplanation The 68360/QUICC CPU was not able to get the memory it needs to carry out its functions. Here are some possible causes.
•
•
•
Recommended Action Reduce system activity to ease the memory demand or upgrade to a larger memory configuration.
Error Message%QUICC-3-OWNERR: msgtxt_ownerrorExplanation An internal software error occurred.
Recommended Action Call your technical support representative to obtain a software upgrade.
Error Message%QUICC_SERIAL-3-CTSLOST: Unit [dec], Clear to Send LostExplanation This message indicates that the Clear To Send (CTS) input signal on a Data Terminal Equipment (DTE) serial interface became inactive while transmitting a frame. This problem stems from a communication line failure or cable disconnection.
Recommended Action Check the serial interface cable and or communication equipment such as the channel service unit/data service unit (CSU/DSU).
Error Message%QUICC_SERIAL-1-INITFAIL: msgtxt_initfailExplanation The serial interface controller of the QUICC chip could not be initialized/started for operation. There is probably a hardware problem.
Recommended Action Power cycle the system. If the error reoccurs, replace the unit.
Error Message%QUICC_SERIAL-5-LINEFLAP: Unit [dec], excessive modem control changesExplanation The system received too many modem control signal interrupts. Modem control signals are hardware handshake signals between Data Terminal Equipment (DTE) and Data Communications Equipment (DCE). The signals include either or both a Data Carrier Detect (DCD) and a Data Set Ready (DSR).
Recommended Action Check the serial interface cable. The error could occur if the cable were disconnected or had come loose and was picking up noise. If the cable appears to be connected correctly, check the equipment connected to the cable.
Error Message%QUICC_SERIAL-3-UNDERFLO: Unit [dec]Explanation While transmitting a frame, the serial controller chip's local buffer got starved of data because data could not be transferred to the chip fast enough to keep pace with its output rate. Normally, such a problem is temporary, depending on transient peak loads within the system.
Recommended Action The system should recover. No action required.
If the problem reoccurs, it indicates a hardware error that may be related to data traffic patterns. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%QUICC-3-UNDERFLO: Unit [dec], underflow errorExplanation The Ethernet hardware is requesting data faster than the system can supply it. This should never happen unless a serious malfunction has occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
RADIX Error Messages
Radix error messages
Error Message%RADIX-3-ADDMASK: Error adding mask entry, [chars], ONESECExplanation 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%RADIX-3-BADTREE: Invalid pointer to head of tree, [hex], ONESECExplanation A software programming error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%RADIX-3-DELETE: Error deleting trie entry, [chars], ONESECExplanation A software programming error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%RADIX-2-INIT: No memory for radix initialization: [chars]Explanation The system ran out of memory during initialization.This should only occur if an image is too large for the existing dynamic memory.
Recommended Action Use a smaller subset image or upgrade hardware.
Error Message%RADIX-2-NOMAXKEYLEN: Programmer error - maximum radix key length not setExplanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%RADIX-3-NOMEMORY: No memory available [chars]Explanation The system is out of memory.
Recommended Action Try one of these actions to correct the problem:
•
•
•
Error Message%RADIX-4-ORPHAN: Orphaned mask [hex], refcount=[dec] at [hex], next=[hex], 5*ONESECExplanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
RCMD Error Messages
Remote command error messages
Error Message%RCMD-4-INVALIDHOST: Invalid host addressExplanation The IP address of the incoming connection was not valid.
Recommended Action Add an entry to the rhost database or determine which client ip address is valid by examining the rhost database.
Error Message%RCMD-4-NOMEMORY: No memory available for RcmdExplanation There was not enough memory for RCP or RSH to allocate memory.
Recommended Action Wait for memory to become available, or add more memory.
Error Message%RCMD-4-NORSHPROC: Rsh Process Fork failedExplanation Creation of the rsh daemon failed. This is usually caused by a lack of resources such as memory or vty.
Recommended Action Wait for resources to become available.
Error Message%RCMD-4-RCMDDNSFAIL: DNS hostname/ip address mismatchExplanation The IP address for an incoming rcmd request is not registered with DNS.
Recommended Action Add the IP address to DNS.
Error Message%RCMD-4-RCPATTEMPTED: Remote copy deniedExplanation An attempt was made to connect to a router through RCP, but the router was not configured as an RCP server.
Recommended Action Configure an RCP server.
Error Message%RCMD-4-RSHATTEMPTED: Remote shell deniedExplanation An attempt was made to connect to a router through rsh, but the router was not configured as an rsh server.
Recommended Action Configure an rsh server.
Error Message%RCMD-4-RSHPORTATTEMPT: Attempted to connect to RSHELL portExplanation An attempt was made to connect to a router through the rshell port (514), but the router was not configured as an RSH or RCP server.
Recommended Action Configure an RSH or RCP server.
REGEXP Error Message
Regular expression parser error messages
Error Message%REGEXP-2-BADLIST: Regular expression access check with bad list [dec]Explanation An internal software error occurred.
Recommended Action If this message recurs, call your technical support representative for assistance.
RIP Error Message
IP Routing Information Protocol error message
Error Message%RIP-3-NOSOCKET: Unable to open socketExplanation 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.
RSP Error Messages
Route Switch Processor error messages
Error MessageHSA not supported in this release, please remove one RSP2Explanation High System Availability (HSA) supports two RSP2s on the router. One RSP2 operates as the master, and the other operates as the slave, which takes over if the master RSP2 fails.
Recommended Action For the HSA feature to function properly, both RSP2s require the same boot-ROM version, the same Cisco IOS release (Cisco IOS Release 11.1(4) or later), and the same DRAM configuration. The minimum DRAM required is 24 MB. Call your technical support representative to order software and memory components.
Error Message%RSP-3-AIPPANIC: Panic: [chars] [hex] [hex] [hex] [hex]Explanation This message occurs when an ATM Interface Processor (AIP) crashes and can send out a message indicating where and why it crashed.
Recommended Action Record the information and call your technical support representative for assistance. Reload the microcode into the AIP.
Error Message%RSP-3-BADHWREV: [chars] (slot [dec]) has wrong hardware revision [dec].[dec]Explanation The hardware in the indicated slot needs to upgraded for operation with the RSP.
Recommended Action Upgrade the board.
Error Message%RSP-4-COOKIE: Corrupt or missing MAC address cookie\n using random base [enet]Explanation This message indicates the part containing the MAC addresses allocated to this chassis could not be accessed or was found to be corrupt, either due to a hardware problem or manufacturing problem.
Recommended Action Report this error to your technical support representative.
Error Message%RSP-3-ERROR, 0, NULLExplanation This message can take many forms. It provides information about a software error.
Recommended Action Report this error to your technical support representative.
Error Message%RSP-3-FLASH: [chars] [chars] error [dec]Explanation The Flash MIB software detected an error.
Recommended Action Copy the error message exactly as it appears, along with the output from show version and the circumstances under which the error message was sent. Report this information to your technical support representative.
Error Message%RSP-3-FOREVER: cmd [dec] to [chars][dec] took [dec] usecs, done [hex]Explanation A command from the RSP to an IP took longer than expected.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%RSP-3-IDPROM: Bad or missing ID EEPROM, controller type [dec]Explanation The ID EEPROM on the RSP is missing or bad.
Recommended Action This message indicates a manufacturing error. Report this error to your technical support representative.
Error Message%RSP-3-INVRTN: Invalid return queue bufhdr [hex]: [hex] [hex] [hex] [hex]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%RSP-3-IPC: [chars] [chars]Explanation An Interprocess Communication (IPC) error occurred. The details about what was attempted and what went wrong will be printed.
Recommended Action Copy the error message exactly as it appears. Copy down the router's configuration along with any other relevant information. Contact your technical support representative for assistance.
Error Message%RSP-3-LOVEGIANT: Card [chars] wants [dec] byte love letters, but only got [dec] bytesExplanation An inconsistency between the microcode and the system code was detected.
Recommended Action Report this error to your technical support representative.
Error Message%RSP-3-LOVENOTE: corrupt lovenote [hex]: [hex] [hex] [hex] [hex] [hex] [hex] [hex]Explanation This message indicates miscommunication between the RSP and an IP.
Recommended Action Report this error to your technical support representative.
Error Message%RSP-3-MSDOG: Master/slave watchdog timed outExplanation The system software failed to reset the master/slave watchdog timer, causing it to time out. This behavior could indicate a software problem or a hardware problem.
Recommended Action Copy the error message exactly as it appears. Copy down the router's configuration along with any other relevant information. Contact your technical support representative for assistance.
Error Message%RSP-3-MSFIX: Fixing [chars] by setting to default [chars]Explanation The characters shown can be either on the slave RSP setting or on the master RSP setting.
The ROM monitor default slave RSP setting is not synchronized with the system configuration file specifications. During bootup, the system image detects the mismatch and modifies the ROM monitor setting to conform with these specifications.
This mismatch most likely occurred because a new RSP was being installed and booted in a high system availability (HSA) environment (dual RSPs) for the first time. Alternatively, in established HSA configurations, this message may result from a previous Interprocess Communication (IPC) error occurring while the HSA environment is reconfigured.
Recommended Action
1
2
If the slot number obtained in Step 1 is the same as the number obtained in Step 2, then no further action is required. You have configured HSA in simple hardware backup mode, and both RSPs are identical.
However, if the two slot numbers differ, you have configured HSA in software error protection mode, and will have different images running, depending on which RSP is currently the slave RSP. If the slot numbers discovered in Steps 1 and 2 differ, reload your router to ensure that the desired system image is running. After the reload, the actual slave RSP will match the default slave RSP specified in (or inferred from) the system configuration file.
For details of various HSA configuration modes consult the Configuration Fundamentals Configuration Guide, see the "Loading System Images, Microcode Images and Configuration Files" chapter, in the "Configuring High System Availability Operation" section (Cisco 7500 Series only).
Error Message%RSP-3-MSVERS: Master has m/s version [dec], slave has m/s version [dec]Explanation The master and slave are running incompatible software versions with regards to the master/slave exchange process.
Recommended Action If the slave image global configuration is used to overide the default slave image from the bundle, then the slave image is incompatible. Update either the master or slave image to ensure the two are compatible.
If the slave is running the image from the bundle, execute and record the output of show version, show running, and show controller cbus. Report this information and the error message to your technical support representative.
Error Message%RSP-3-NOIDB: bad vc %x on %xExplanation The router contains a MIP interface. An internal software error occurred on either the RSP or the MIP.
Recommended Action Call your technical support representative for assistance.
Error Message%RSP-3-NOLOVE: Corrupt lovenote: [hex] [hex] [hex] [hex]Explanation This message indicates miscommunication between the RSP and an IP.
Recommended Action Report this error to your technical support representative.
Error Message%RSP-3-NOMAC: Can't allocate MAC address for interface [dec]/[dec]Explanation No MAC address was available for allocation to the specified interface.
Recommended Action Report this error to your technical support representative.
Error Message%RSP-2-NOMEMORY: No memory available for [chars]Explanation An attempt at memory allocation failed.
Recommended Action Try these actions to remedy the problem:
•
•
•
In general, reduce other system activities to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%RSP-3-NORESTART: [chars]: unable to schedule restart for output queueExplanation 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%RSP-3-NOSTART: No microcode for [chars] card, slot [dec]Explanation No microcode is defined or available for the specified card.
Recommended Action Reconfigure the card to specify an existing microcode file.
Error Message%RSP-2-QAERROR: [chars] error, [chars] at addr [hex] ([chars])\n log [hex], data [hex] [hex]Explanation A software error was detected during packet switching.
Recommended Action Call your technical support representative for support.
Error Message%RSP-3-RESTART, 0, NULLExplanation The cBus buffer memory was reset and reallocated.
Recommended Action Report this error to your technical support representative, if memory is not reset manually (by changing the MTU on an interface, for example).
Error Message%RSP-3-RESTARTREQ: [chars]Explanation Some part of the software requested that cBus buffer memory be reset and reallocated.
Recommended Action Report this error to your technical support representative, if memory is not reset manually (by changing the MTU on an interface, for example).
Error Message%RSP-3-SLAVECHANGE: Slave changed state from [chars] to [chars]Explanation
The slave RSP has undergone a hardware state change. Both the old state and new state are shown.
Possible states are
•
•
•
•
Possible state changes indicated by the above message are
•
•
•
•
Any other combination is unexpected.
Recommended Action
Causes and recommended solutions:
•
•
CAUTION: Failure to ensure a consistent configuration on a freshly installed slave RSP, might result in undefined behavior if the router reloads.
•
•
Log out from the slave RSP's console port using Ctrl-c or Ctrl-z, and enter the slave reload global configuration command on the master RSP to bring the slave RSP back online.
•
Error Message%RSP-3-SLAVEMASTER: Slave stole mastershipExplanation The master RSP detected that the slave RSP had taken mastership of the router. The old master RSP will reload and become the slave RSP, letting the new master RSP take over. This indicates a software or hardware error.
Recommended Action Copy the error message exactly as it appears. Copy down the router's configuration along with any other relevant information. Contact your technical support representative for assistance.
Error Message%RSP-3-SLAVEROM: [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%RSP-5-SLAVEUP: Slave changed to state RunningExplanation This is an informational message to indicate that the slave RSP has started running the slave RSP image. This message after the router boots or after the slave reload global configuration command is issued on the master RSP.
Recommended Action No action required.
Error Message%RSP-2-STALL: partially inserted or removed IPs on cyBus[dec]Explanation Most likely, a board is not fully seated in the chassis. A less likely possibility is a hardware problem with the RSP or backplane.
Recommended Action Try reseating the boards. Call your technical support representative for assistance if this message persists.
Error Message%RSP-3-XBUFHDR: corrupt bufhdr [hex]: [hex] [hex] [hex] [hex]Explanation Miscommunication occurred between the RSP and an IP.
Recommended Action Report this error to your technical support representative.
RSRB Error Messages
Remote source-route bridging error messages
Error Message%RSRB-4-BADLEN: Peer [chars], [chars], bad length [dec], trn [dec]%RSRB-4-BADLENIP: Peer [dec]/[inet], [chars], bad length [dec],trn [dec]Explanation An internal software error occurred.
Recommended Action If either message recurs, call your technical support representative for assistance.
Error MessageRSRB-3-BADVERSIONFST: FST in: [chars]: version mismatch, mine [dec], theirs [dec]%RSRB-3-BADVERSIONIF: IF in: [chars]: version mismatch, mine [dec], theirs [dec]Explanation The remote end of a direct serial peer is running the wrong version of the system software. Either the local end, the remote end, or both are not up to date.
Recommended Action Call your technical support representative for an update.
Error Message%RSRB-3-BADVERSIONTCP: [chars]: [dec]/[inet]: version mismatch, mine [dec], theirs [dec]Explanation The remote end of a TCP remote peer is running the wrong version of the system software. Either the local end, the remote end, or both are not up to date.
Recommended Action Call your technical support representative for an update.
Error Message%RSRB-4-BADVRE: Bad vre type%RSRB-4-CONIPST: Peer [dec]/[inet], CONN, illegal state [dec]%RSRB-4-CONNILLSTATE: Peer [dec]/[inet], CONN, illegal state [dec]%RSRB-4-CONNSTAT: Peer [dec]/[interface], IFin, bad connection 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%RSRB-3-FSTERR: [char]: [char]: [inet], op [hex], len [dec], trn [dec]Explanation The remote end of a direct serial RSRB connection detected a configuration problem or traffic that is not recognized by the configuration.
Recommended Action Examine the configuration on both sides of the serial connection for possible problems. Examine the traffic being offered for propagation with respect to the configuration. The destination target ring is denoted by the value of trn.
Error Message%RSRB-3-HDRNOVRP: Peer [inet], HDR, no vrp%RSRB-4-HDRRECV: Peer [dec]/[inet], HDR, recv state invalid, not empty [dec]%RSRB-3-HDRVRP: Peer [dec]/[inet], HDR, vrp state wrong, [dec]Explanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%RSRB-3-IFERR: [chars]: [chars]: [chars], op [hex], len [dec], trn [dec]Explanation The remote end of a direct serial RSRB connection detected a configuration problem or traffic that is not recognized by the configuration.
Recommended Action Examine the configuration on both sides of the serial connection for possible problems. Examine the traffic being offered for propagation with respect to the configuration. The destination target ring is denoted by the value of trn.
Error Message%RSRB-4-ILLPEER: Peer [chars] [[hex]], illegal state [dec]%RSRB-4-LOCAL: Unit [dec], local/vring set simultaneously, vrn [dec]Explanation An internal software error occurred.
Recommended Action If either of these messages recur, call your technical support representative for assistance.
Error Message%RSRB-3-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%RSRB-3-NOTREM: Null idb and not remote%RSRB-4-OPTNULL: Remopened and t NULL%RSRB-4-PEERSTAT: Peer [chars], wrong 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%RSRB-4-RNGXFAIL: Ring exchange failure, resetting peer: [chars]Explanation The RSRB peer initiation logic failed due to a memory shortage or congestion condition.
Recommended Action The problem should clear and the peers should re-open without operator intervention.
Error Message%RSRB-3-SENDPUNTFST : [chars]: sent [chars] to [dec]/[chars]%RSRB-3-SENDPUNTIF: [chars]: sent [chars] to [dec]/[chars]Explanation The local end of a direct serial RSRB connection detected a configuration problem or traffic that is not recognized by the configuration.
Recommended Action Examine the configuration on both sides of the serial connection for possible problems. Examine the traffic being offered for propagation with respect to the configuration.
S4T68360 Error Messages
S4T68360 error messages relate to the 4 port synchronous serial adapter based on the 68360 processor
Error Message%S4T68360-1-DISCOVER: only found [dec] interfaces on bay [dec], shutting down bayExplanation A port adaptor (PA) hardware error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%S4T68360-1-DWNLDFL: s4t_msg_download_failExplanation The S4T hardware has failed. It could not download its operational microcode.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%S4T68360-1-INITFAIL: s4t_msg_initfailExplanation The S4T port adaptor (PA) failed to complete hardware initialization.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%S4T68360-1-NOTCMPLT: s4t_msg_download_ncmpltExplanation The S4T port adaptor (PA) hardware failed. It did not acknowledge the completion of the operational microcode download.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%S4T68360-1-NOTREADY: s4t_msg_notreadyExplanation The S4T port adaptor (PA) hardware failed. The S4T PA would not begin to download the operational microcode.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%S4T68360-3-NOTS4T68360: At [hex], device reported [hex]Explanation The S4T hardware failed. A non-S4T device pointed at the software for the S4T.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%S4T68360-3-OWNERR: msgtxt_ownerrorExplanation A software or hardware error occurred. The S4T driver detected that the transmit ring is an inconsistent and unrecoverable state.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%S4T68360-1-STARTFAIL: s4t_msg_startfailExplanation A software or hardware error occurred. The S4T interface is not responding to commands used to initialize it.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%S4T68360-1-STOPFAIL: s4t_msg_stopfail);Explanation The 4T Port Adaptor (PA) failed to respond to a request to disable an interface.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
SCHED Error Messages
Schedular error messages
Error Message%SCHED-2-ATTRCMD: Attempt to [chars] attribute [chars] on process [dec]., 30*ONESEC%SCHED-2-ATTRVALUE: Attempt to set bad [chars] value ([hex]) on process [dec].%SCHED-2-EDISMSCRIT: Critical priority process [chars] may not dismiss., 30*ONESEC%SCHED-3-LOSTWAKEUP: Wakeup information for process [chars] lost (maj [hex], min [hex])., 30*ONESEC%SCHED-2-NOATTR: Attempt to [chars] unknown process attribute [dec]., 30*ONESEC%SCHED-2-NOTWATCHTIMER: [chars] timer [hex] not being watched., 30*ONESEC%SCHED-3-PAGEZERO: Low memory modified by [chars] ([hex] = [hex]).Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SCHED-3-PRIORITY: Illegal priority ([dec]) specified for process [chars]., 30*ONESEC%SCHED-2-QUEUENOTEMPTY: Attempt to delete non-empty watched queue [chars] (address [hex])., 30*ONESEC%SCHED-2-SEMUNLOCK: [chars] attempted to unlock semaphore owned by [chars], 30*ONESEC%SCHED-3-STACKSIZE: Illegal stack size ([dec]) specified for process [chars]., 30*ONESEC%SCHED-3-STUCKMTMR: Sleep w/expired mgd timer [hex], time %#Ta (%TE ago)., ONEMIN%SCHED-3-UNEXPECTEDEVENT: Process received unknown event (maj [hex], min [hex])., 30*ONESEC%SCHED-3-UNEXPECTEDMESSAGE: Unknown message [hex] received (ptr arg [hex], num arg [hex])., 30*ONESEC%SCHED-2-WATCH: Attempt to [chars] uninitialized watched [chars] (address [hex])., 30*ONESEC%SCHED-2-WATCHTIMER: Request to watch [chars] timer [hex] ([chars] timer [hex] active)., 30*ONESEC%SCHED-3-UNEXPECTEDQUEUE: Queue event for unknown queue (index [dec])., 30*ONESEC%SCHED-3-UNEXPECTEDTIMER: Unknown timer expiration, timer = [hex], type [dec], 10 * ONESECExplanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
SDLC Error Messages
Synchronous Data Link Control error messages
Error Message%SDLC-4-CTRLBAD: Interface [chars], Invalid control fieldExplanation A bad SDLC frame was received.
Recommended Action If this message recurs, check the SDLC serial line and the devices attached to it.
Error Message%SDLC-4-DROPPED: Dropped SDLC packet from SDLC hold queue, 10Explanation An SDLC frame had to be dropped from the output hold queue, usually because of excessive congestion on the output link.
Recommended Action If this message occurs frequently, determine why your SDLC link is being overloaded with data and resolve the cause (typically by either increasing bandwidth to your SDLC line or reducing the load on your link).
Error Message%SDLC-4-FRAMEERR: Interface [chars], Frame error: CF [hex], VS [dec] [char] VR [dec], Reason [hex]Explanation A FRMR frame was received. This can be due to a noisy serial line, an overloaded SDLC device, or corrupted data.
Recommended Action If this message recurs, service the serial line and the devices attached to it.
Error Message%SDLC-2-ILLEGSTATE: Illegal state, [hex] [dec]Explanation An internal SDLC state violation was detected.
Recommended Action Record the entire error message and call your technical support representative for assistance.
Error Message%SDLC-4-INFOBAD: Interface [chars], Info field not permitted%SDLC-4-INVNR: Interface [chars], Invalid NR valueExplanation A bad SDLC frame was received.
Recommended Action If any of these messages recur, check the SDLC serial line and the devices attached to it.
Error Message%SDLC-4-INVLDGRPPOLL: Interface [chars], Invalid group-poll frame, 10Explanation An unnumbered poll (UP) was received with the wrong group poll address.
Recommended Action Make sure the group poll address configured on the router matches the one configured in the PU macro (GP3174=XX) in the NCP generate file.
Error Message%SDLC-2-NOBUF: Interface [chars], no buffer available to [chars]Explanation Insufficient memory available.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%SDLC-4-NOFRMRSPACE: Cannot allocate a FRMR frameExplanation The router needed to generate an FRMR frame but could not allocate the necessary memory for the frame.
Recommended Action The fact that memory is so low that it cannot allocate the frame is far more serious than the reason for generating the FRMR. Fix the cause of low memory, and if the problem still occurs, determine why the FRMR must be sent.
Error Message%SDLC-3-NOINPIDB: Input idb not setExplanation This is a software error. A frame was given to the SDLC handler to process, but the interface on which the frame arrived is not known.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SDLC-2-NOPOINTER: AW_SDLC_SEC with no sdllc_llc pointerExplanation An error condition occurred during SDLLC initiation.
Recommended Action No action is required. The SDLLC session will restart without operator intervention.
Error Message%SDLC-4-NOUA: Interface [chars], address [hex] non UA frame is received in response to SNRM, 99999Explanation The router received a frame other than a UA in response to a SNRM.
Recommended Action Check the end station to see if the SNA stack is up and running.
Error Message%SDLC-3-NULLPAK: Interface [chars], NULL packet ptr, rvr [dec], vs [dec], vr [dec]Explanation An internal software error occurred in the router's SDLC processing system.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SDLC-4-SDLC_ERR: SDLC_ERROR with no pollExplanation A protocol error was detected on a secondary station, but FRMR could not be sent because the station did not own the poll bit. This message indicates either poor line conditions or a faulty SDLC implementation.
Recommended Action If the message recurs, run traces on the SDLC line. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SDLC-4-UNKNOWNADDR: Received input for unknown addr/input addr [hex]. Tossing frame.Explanation SDLC frames were received from an unknown (unconfigured) SDLC address.
Recommended Action Either configure the station for SDLLC or STUN, or shut down the serial interface to disable the line. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SDLC-4-WRONGADDR: [interface], data from wrong address, expected [addr], received [addr]Explanation This condition typically occurs on multidropped lines when the T1 timer interval is too short or the sdlc line-speed command is not configured. In rare cases the RTS/CTS handshake can delay the transmission of a frame so long that a response is returned after the next station is polled.
Recommended Action Adjust the value of the sdlc line-speed statement in the configuration file. (Either take line traces to observe appropriate T1 timer intervals, or adjust empirically.)
SDLLC Error Messages
Synchronous Data Link Control/ Logical Link Control type 2 translation error messages
Error Message%SDLLC-5-ACT_LINK: SDLLC: [chars] LINK address [hex] ACTIVATED: [chars]Explanation An SDLLC media conversion session was activated.
Recommended Action No action is required.
Error Message%SDLLC-5-DACT_LINK: SDLLC: [chars] LINK address [hex] DEACTIVATED: [chars]Explanation An SDLLC media conversion session was deactivated. If deactivation is a result of an error condition, this message will include a reason.
Recommended Action If the message does not include a description of an error, the deactivation was normal and the message is for information only. If the message does include a description of an error, begin problem analysis. Determine whether session loss is related to LLC2 timers by issuing the debug llc2-err command. If the problem is related to LLC2 timers, consider using SDLLC with the local acknowledgment feature. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SDLLC-6-XID_DISPLAY: sa [enet] da [enet] ss [hex] ds [hex] [[hex][hex][hex][hex]]Explanation This message supplies the information for the received and rejected XID.
Recommended Action See the SDLLC-6-XID_NOMATCH error message.
Error Message%SDLLC-6-XID_FORMAT: Unsupported XID format received, format [dec]Explanation An inappropriate XID format was received for this mode of SDLLC operation. Review the type of devices you are connecting with SDLLC to make sure they are supported.
Recommended Action See the SDLLC-6-XID_NOMATCH error message.
Error Message%SDLLC-4-XID_NOMATCH: [chars], XID mismatch for [hex]. CONNECTION REJECTEDExplanation An inbound XID from a PU 2.0/PU 2.1 node was rejected. The targeted SDLC address is displayed. The XID information is displayed in a subsequent message—SDLLC-6-XID_DISPLAY or SDLLC-6-FORMAT.
Recommended Action This is a security feature. Additional information is displayed to help trace the source of the rejected XID. If the message is undesirable, simply remove the XID statement from the router configuration.
SEC Error Messages
IP security error messages
Error Message%SEC-6-IPACCESSLOGDP: list [dec] [chars] [chars] [inet] -> [inet] ([dec]/ [dec]), [dec] packet[chars]Explanation A packet matching the log criteria for the given access list was detected.
Recommended Action Informational message only. No action required.
Error Message%SEC-6-IPACCESSLOGNP: list [dec] [chars] [dec] [inet] -> [inet], [dec] packet[chars]Explanation A packet matching the log criteria for the given access list was detected.
Recommended Action Informational message only. No action required.
Error Message%SEC-6-IPACCESSLOGP: list [dec] [chars] [chars] [inet]([dec]) -> [inet]([dec]), [dec] packet[chars]Explanation A packet matching the log criteria for the given access list was detected.
Recommended Action Informational message only. No action required.
Error Message%SEC-3-NOMAX: No default for NLESO defined%SEC-2-NOOPT: Box secured, no option on internal packet%SEC-2-NOTSEC: First opt in tcb not BASIC security%SEC-2-SECINS: Security opt in tcb not SECINSERTExplanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%SEC-4-TOOMANY: Box secured, too many options on internal packetExplanation No room for all desired IP header options. Packet discarded.
Recommended Action Configure for fewer IP header options.
SLIP Error Messages
Serial Line IP error messages
Error Message%SLIP-2-BADQUOTE: Impossible quoted character [hex]%SLIP-2-BADSTATE: Impossible input state [hex]Explanation An internal software error occurred.
Recommended Action If either of these messages recurs, call your technical support representative for assistance.
SMF Error Message
Software MAC filter error message
Error Message%SMF-3-NO_MEM failed to create SMF entry for [sci_notation] on [chars] from chunk [chars]Explanation The preallocated memory resources for the SMF have been exhausted.
Recommended Action Reduce the number of interfaces on which transparent bridging is configured. Copy the error message exactly as it appears, and report it to your technical support representative.
SMRP Error Messages
Simple Multicast Routing Protocol error messages
Error Message%SMRP-2-ASSERTFAILED: SMRP assertion failed: [chars]Explanation The software detected an inconsistency. This is considered a serious error. The router attempts to continue, but SMRP processing may be impaired.
Recommended Action Copy the error message exactly as it appears, noting any SMRP problems that you are experiencing, and report it to your technical support representative.
Error Message%SMRP-7-DEBUGMSG: SMRP Debug: [chars]Recommended Action This message is generated by some debug commands to provide additional information about conditions in SMRP.
Recommended Action If you are experiencing problems in SMRP, these messages should be provided, along with any other information, in a report to your technical support representative.
Error Message%SMRP-5-NEIGHBORDOWN: [chars]: SMRP neighbor down - [chars]Explanation A neighboring SMRP router is now down.
Recommended Action Notification message only. No action required.
Error Message%SMRP-6-NEIGHBORUP: [chars]: SMRP neighbor up - [chars]Explanation A neighboring SMRP router has appeared.
Recommended Action Notification message only. No action required.
Error Message%SMRP-3-NOFDDICOMPAT: SMRP port [chars] disabled; pre-fdditalk not supportedExplanation SMRP cannot be started on an interface that is running pre-FDDITalk.
Recommended Action Use FDDITalk on the FDDI ring if possible.
Error Message%SMRP-5-PORTDOWN: [chars]: SMRP port down - [chars]Explanation An SMRP port is down and is no longer operational.
Notification message only. No action required.
Error Message%SMRP-6-PORTUP: [chars]: SMRP port up - [chars]Explanation An SMRP port has come up.
Recommended Action Notification message only. No action required.
SNAPSHOT Error Messages
Snapshot dial-on-demand routing error messages
Error Message%SNAPSHOT-2-BADSTATE: Bad state for Snapshot block [chars][[dec]], location [dec]Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SNAPSHOT-2-NOMEMORY: Unable to create Snapshot SAB. Updates will NOT be sentExplanation The router is running out of memory, which impacts the operation of snapshot.
Recommended Action Check memory usage of the router. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SNAPSHOT-2-TOOMANYDIALERS: Exceeded maximum dialer interfaces to watch. Ignoring [chars]Explanation Snapshot is being used over more than 100 DDR interfaces.
Recommended Action Do not use snapshot over more than 100 DDR interfaces.
SNMP Error Messages
Simple Network Management Protocol error messages
Error Message%SNMP-4-NOTRAPIP: SNMP trap source [chars] has no ip addressExplanation The user entered an snmp-server trap-source command. The interface requested for use as the source address has no address associated with it. The SNMP trap is being sent anyway, but without the source address that the user intended.
Recommended Action There are two possible solutions. Either enter a no snmp-server trap-source command to disable the request for a specific source IP address, or add an IP address to the interface referenced in the snmp-server trap-source configuration command.
Error Message%SNMP-3-SOCKET: can't open UDP socketExplanation The SNMP server was unable to open a port for receiving SNMP requests. This usually happens when the SNMP server is started using the snmp-server community configuration command on a router or communication server with an interface that has no IP address configured. Another possible cause is low memory.
Recommended Action Configure at least one interface with an IP address or specify the no snmp-server command to remove the SNMP server process. Call your technical support representative if problems persist or if it becomes necessary to add memory.
SSE Error Messages
Silicon switching engine error messages
Error Message%SSE-3-BADMEMORY: SSE memory failure detectedExplanation A memory error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SSE-1-BOGUSEQ: SSE bogus equal branch [hex], [hex], [dec] [hex]Explanation An internal inconsistency in the data structures used by the SSE occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SSE-6-COMPERR: SSE compilation failure -- [chars]Explanation A software failure occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SSE-2-HUNG: SSE hung -- [chars]Explanation The SSE is hung.
Recommended Action Reboot the SSE.
Error Message%SSE-2-HWFAILURE: SSE hardware failure-- [chars] code [hex]Explanation A hardware error occurred, indicating an unexpected condition on the silicon switch processor (SSP) board.
Recommended Action It might be necessary to replace the SSP. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SSE-2-MEMERROR: SSE memory failure, address [hex] expected [hex], got [hex]Explanation A hardware error occurred, indicating memory failure on the silicon switch processor (SSP) board.
Recommended Action It might be necessary to replace the SSP. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SSE-1-NESTADDR: SSE nested addresses detected, protocol [dec] [dec]Explanation An internal inconsistency in the data structures used by the SSE occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SSE-1-NOMATCH: SSE delete didn't end at a match node, type [char] value [dec], address [dec], bytecount [dec], high [dec], state [dec]Explanation An internal inconsistency in the data structures used by the SSE occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SSE-3-NOMEMORY: No memory available for [chars]Explanation An 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%SSE-2-NOTZERO: Program memory does not start at zeroExplanation A hardware error occurred, indicating an unexpected condition on the silicon switch processor (SSP) board.
Recommended Action It might be necessary to replace the SSP. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SSE-2-SWFAILURE: SSE software failure -- [chars] [hex]Explanation A software failure occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
STANDBY Error Messages
Hot Standby Router Protocol error messages
Error Message%STANDBY-3-BADAUTH: Bad authentication from [inet], remote state [chars]Explanation Two routers participating in the Hot Standby protocol disagree on the valid authentication string.
Recommended Action Use the standby authentication interface command to repair the Hot Standby protocol authentication discrepancy between the local system and the one whose IP address is reported.
Error Message%STANDBY-3-MISCONFIG: Attempt to change [chars] MAC address to [enet] when DECNET already runningExplanation 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%STANDBY-3-NOBUFFER: No buffer available for sending HELLOExplanation The Hot Standby protocol 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%STANDBY-3-NOMEMORY: No memory available for [chars]Explanation The system was unable to initialize the Hot Standby protocol on an interface. The system may be out of memory.
Recommended Action Record the output from the following commands: show proc mem (repeated twice), show mem, show version, write terminal. Provide this information to your technical support representative.
Error Message%STANDBY-3-NOSOCKET: Unable to open socketExplanation The system was unable to initialize an IP connection for the Hot Standby protocol.
Recommended Action Make sure that there is at least one interface configured to run IP.
STUN Error Messages
Serial tunneling error messages
Error Message%STUN-3-BADCONN: CONN: bad connection ([dec]), peer: [chars]%STUN-3-BADLENOP: [chars]: bad len or unknown op, op [dec], len [dec]%STUN-3-BADMAGIC: [chars]: wrong magic, mine [hex], theirs [hex] ([dec])%STUN-3-BADMAGICTCP: [chars]: peer [chars], wrong magic, min [hex], theirs [hex]%STUN-3-BADPASSIVEOPEN: passive open from [inet] ([dec]) -> [dec] failed%STUN-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%STUN-6-CONNOPENFAIL: CONN: peer [chars] open failed, [chars] [[dec]]Explanation An attempt to connect to a remote TCP STUN peer failed.
Recommended Action Verify that the remote peer is accessible from this router, that it is running software capable of supporting STUN, and that it is configured correctly.
Error Message%STUN-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%STUN-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 STUN group. If memory shortages persist, call your technical support representative for assistance.
Error Message%STUN-3-NOPROTMEM: No memory for STUN protocol definition of [chars]Explanation The system does not have sufficient memory to define a new STUN schema.
Recommended Action This error message should only print when the router is critically short of memory. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%STUN-3-NOTGEM: No memory for STUN protocol sdlc-tg definitionExplanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%STUN-2-NOTGI: Please remove and redefine protocol group [dec]Explanation An internal error occurred. The configuration is irregular.
Recommended Action Remove and reconfigure the STUN protocol group. Record the configuration and call your technical support representative for assistance.
Error Message%STUN-6-OPENED: [chars]: peer [chars] opened, [previous state [chars]]%STUN-6-OPENING: CONN: opening peer [chars], [dec]%STUN-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%STUN-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 STUN reconfiguration or disabling. This is good, expected behavior.
Recommended Action Informational message only. No action required.
Error Message%STUN-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%STUN-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%STUN-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 of these messages recurs, call your technical support representative for assistance.
Error Message%STUN-6-TCPFINI: peer [chars] closed [previous state [chars]]Explanation A remote peer closed a STUN 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%STUN-6-TCPPEERSHUT: [chars] [chars], [inet]([dec])Explanation This route closed a STUN 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.)
SUBSYS Error Messages
Software subsystem error messages
Error Message%SUBSYS-2-BADCLASS: Bad subsystem class [dec] - ignoring subsystemExplanation A software consistency check failed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SUBSYS-2-BADVERSION: Bad subsystem version number [dec] - ignoring subsystemExplanation A software consistency check failed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SUBSYS-2-MISMATCH: Kernel and subsystem version differ [dec.dec]Explanation A software consistency check failed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SUBSYS-2-NOTFOUND: Subsystem [chars] needs subsystem [chars] to startExplanation A software consistency check failed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
SYS Error Messages
Operating system error messages
Error Message%SYS-2-ALREADYFREE: Buffer [hex] already in free pool [chars]%SYS-3-BADBLOCK: Bad block pointer [hex]%SYS-3-BADDISP: Bad dispose code [hex] in [chars]%SYS-3-BADFREEMAGIC: Corrupt free block at [hex] (magic [hex])Explanation A block of memory is corrupt at the indicated location.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%SYS-3-BADFREEPTRS: Bad [chars] pointer [hex] at [hex] ([chars] = [hex]Explanation A pointer in the block header at the indicated location is corrupt.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%SYS-3-BADLINKTYPE: Unexpected linktype [dec]Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SYS-2-BADLIST: Regular expression access check with bad list [dec]Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SYS-3-BADMAGIC: Corrupt block at [hex] (magic [hex]Explanation The free memory pool is corrupted.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SYS-3-BADPARAM: Function [chars]: value [hex] passed in parameter [chars]Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SYS-2-BADPID: Bad pid [dec] for tty [t-line]%SYS-2-BADPOOL: Attempt to return buffer with corrupt pool pointer, ptr= [hex], pool= [hex]%SYS-2-BADPOOLMAGIC: Attempt to use pool pointer with corrupt header, pool= [hex]%SYS-2-BADSHARE: Bad sharecount in [chars], ptr=[hex],count=[hex]%SYS-2-BADSTACK: Process [chars] has trashed stack, old size [dec]%SYS-6-BLKINFO: [chars]blk [hex], words [dec], alloc [hex][chars] RZ offset [dec], dealloc [hex], rfcnt [hex]%SYS-2-CFORKLEV: cfork at level [dec]Explanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%SYS-3-BADPRINT: Process has no associated tty (in [chars])., 10*ONESECExplanation 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%SYS-3-BADRESID: Clock hardware returned bad residual [dec]Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SYS-2-BLOCKHUMG: Task hung with blocking disabled, value = [hex]Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SYS-2-CHUNKBOUNDS: Attempted to exceed freelist chunk bounds chunk [hex], data [hex],Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SYS-2-CHUNKFREE: Attempted to free non-chunk memory, chunk [hex], data [hex], 10 * ONESECExplanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SYS-2-CHUNKPARTIAL: Attempted to destroy partially full chunk, chunk [hex], 10 * ONESECExplanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SYS-2-CHUNKSIBLINGS: Attempted to destroy chunk with siblings, chunk [hex], 10 * ONESECExplanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SYS-5-CONFIG: Configured from [chars] by [chars]%SYS-5-CONFIG_I: Configured from [chars] by [inet]%SYS-5-CONFIG_L: Configured via LNM from [enet]%SYS-5-CONFIG_M: Configured via MOP from [chars] by [enet]Explanation The router's configuration was changed.
Recommended Action Notification messages only. No action required.
Error Message%SYS-4-CONFIG_NEWER: Configurations from version [dec].[dec] may not be correctly understood.Explanation The boot image parses the configuration saved in NVRAM and encounters a configuration file written by a newer IOS software version. (During the netboot process, the boot image will ignore the newer features.)
Recommended Action No action is required.
Error Message%SYS-5-CONFIG_NV: Non-volatile store configured from [chars] by [chars]%SYS-5-CONFIG_NV_M: Non-volatile store configured via MOP from [chars] by [enet]Explanation The configuration was written successfully through the Maintenance Operation Protocol (MOP).
Recommended Action No action required.
Error Message%SYS-3-CONFIG_NV_ERR: Non-volatile store write error - configuration failedExplanation The write of the nonvolatile configuration failed.
Recommended Action If this message recurs, contact your technical support representative for assistance.
Error Message%SYS-3-CPUHOG: Task ran for [dec] msec. Process = [chars], PC = [hex]Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SYS-4-DUAL_MESSAGE: SNMP system message request [dec] denied due to pending jobExplanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SYS-2-DUPEXPORT: Duplicate export vector [chars] registration attemptExplanation An internal software error occurred.
Recommended Action If this message recurs, contact your technical support representative for assistance.
Error Message%SYS-2-FREEBAD: Attempted to free memory at [hex], not part of buffer pool%SYS-2-FREEFREE: Attempted to free unassigned memory at[hex], alloc [hex] dealloc [hex]%SYS-2-GETBUF: Bad getbuffer, bytes= [dec]%SYS-3-HARIKARI: Process [chars] top-level routine exited%SYS-2-HEADER: Attempt to return buffer with invalid buffer header, ptr= [hex]Explanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%SYS-2-INLIST: Buffer in list, ptr= [hex]%SYS-2-INLIST1: Buffer in list, ptr= [hex], caller= [hex]%SYS-2-INPUTQ: INPUTQ set, but no idb, ptr=[hex]%SYS-2-INSCHED: [chars] within scheduler%SYS-2-INTSCHED: [chars] at level [dec]%SYS-3-INUSEFREE: Block [hex] on free list [dec] in useExplanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%SYS-3-INTPRINT: Illegal printing attempt from interrupt level., 10*ONESECExplanation 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%SYS-4-INVALID_IMAGE: Running invalid image for platform!Explanation The software image being run is for a different hardware architecture. This problem can occur on a 1003, 1004, or 1005. The 1003 and 1004 have a different image than the 1005.
Recommended Action Install the correct software image.
Error Message%SYS-3-INVMEMINT: Invalid memory action ([chars]) at interrupt levelExplanation This message indicates that a memory allocation or deallocation was attempted from an interrupt handler.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%SYS-2-LINKED: Bad enqueue of [hex] in queue [hex]%SYS-2-LINKED: Bad p_dequeue of [hex] in queue [hex]%SYS-2-LINKED: Bad p_requeue of [hex] in queue [hex]%SYS-2-LINKED: Bad requeue of [hex] in queue [hex]%SYS-2-LOWMEM: Low memory debug exception (limit =[dec] free = [dec])Explanation The router is running short on memory.
Recommended Action It may be necessary to free some memory by exiting a program. If this message recurs, call your technical support representative for assistance.
Error Message%SYS-2-MALLOCFAIL: Memory allocation of [dec] bytes failed from [hex], pool [chars], alignment [dec]Explanation The requested memory allocation is not available from the specified memory pool. The current system configuration, network environment or possibly a software error may have exhausted or fragmented the router's memory.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SYS-6-MEMDUMP: [hex]: [hex] [hex] [hex] [hex]Explanation This message is sent in conjunction with the %SYS-6-BLKINFO message. It provides additional data.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SYS-3-MGDTIMER: [chars][chars], timer = [hex], 10 * ONESECExplanation 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%SYS-3-MGDTIMEREXP: Unknown timer expiration, timer = [hex], type [dec], 10 * ONESECExplanation The process received an expiration notice for a timer that does not belong to it.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SYS-3-MSGLOST: [dec] messages lost due to queue overflowExplanation A software error occurred.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%SYS-6-MTRACE: [chars]: addr, pc [hex], [hex] [hex], [hex] [hex], [hex] [hex], [hex [hex], [hex] [hex], [hex] [hex], [hex] [hex], [hex]Explanation The free memory pool is corrupted.
Recommended Action If this message recurs, contact your technical support representative for assistance.
Error Message%SYS-2-NOBLOCK: [chars] with blocking disabledExplanation An internal software error occurred.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%SYS-6-NOBRIDGE: Bridging software not presentExplanation Your system is not equipped to be a bridge.
Recommended Action Install the bridging software option.
Error Message%SYS-1-NOECO: WARNING: This 500-CS cannot run this version of software. Please contact Customer Service for upgrade information. tele: 1 (800) 553-NETS 1 (415) 903-7208 email: cs-rep@cisco.com Hardware burned in address is [enet]Explanation An Error Change Order (ECO) is needed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SYS-2-NOMEMFRG: Memory fragmentation check debug exception (fragment size [dec])Explanation The system detected an error checking memory fragmentation.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%SYS-2-NOMEMORY: No memory available for [chars] [dec]Explanation An 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%SYS-3-NOPROC: Process table full%SYS-2-NOTDEAD: Rekilling process [chars], pid [dec]%SYS-2-NOTQ: p_unqueue didn't find [hex] in queue [hex]%SYS-2-NOTQ: unqueue didn't find [hex] in queue [hex]%SYS-3-NULLIDB: Null idb in [chars]Explanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%SYS-2-NOPROCESS: No such process [dec]Explanation An internal software error occurred.
Recommended Action If this message recurs, contact your technical support representative for assistance.
Error Message%SYS-3-NZREFCNT: Block [hex] on free list [dec] with ref count [dec]Explanation A block of memory in the free pool is actually in use. The number of processes using the memory block is indicated.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%SYS-5-OUTSETUP: Configuration file [chars] accepted, aborting setupExplanation A configuration was accepted through the network, so the setup session will be aborted.
Recommended Action No action required.
Error Message%SYS-3-OVERRUN: Block overrun at [hex] (redzone [hex])Explanation An internal software error occurred.
Recommended Action If this message recurs, contact your technical support representative for assistance.
Error Message%SYS-1-OVERTEMP: System detected OVER TEMPERATURE condition. Please resolve cooling problem immediately!Explanation The environmental monitor detected a high temperature condition.
Recommended Action Make sure room temperature is not too high and that air flow to the card is not blocked. If this condition persists, the environmental monitor may shut the system down. Call your technical support representative for assistance, if necessary.
Error Message%SYS-2-PAKCLIP: Bad pak_clip, bytes= [dec]Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SYS-2-QCOUNT: Bad dequeue [hex] count [dec]%SYS-2-QCOUNT: Bad p_dequeue [hex] count [dec]%SYS-2-QCOUNT: Bad p_unqueue [hex] count [dec]%SYS-2-QCOUNT: Bad unqueue [hex] count [dec]%SYS-2-QINSERT: Unable to add [chars] to queue - no elements%SYS-4-REGEXP: [chars]Explanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%SYS-3-REGARG: Registry service [chars] has too many arguments%SYS-3-REGCREA2: Attempt to create registry service [chars] twice%SYS-3-REGDFLT: Attempt to add default twice to registry service%SYS-3-REGNONE: Registry [dec] service [dec] doesn't exist - [chars]%SYS-3-REGTYPE: Registry service [chars] is wrong type, should be [dec]Explanation An internal software consistency check failed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SYS-5-RELOAD: Reload requested%SYS-5-RESTART: System restarted -- [chars]Explanation A reload or restart was requested.
Recommended Action Notification messages only. No action required.
Error Message%SYS-4-RELOAD_ATTEMPT: Attempt via SNMP failed; system-shutdown not configuredExplanation A software error occurred.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%SYS-2-RETBUF: Bad retbuffer, ptr= [hex]%SYS-2-RETBUF1: Bad retbuffer, ptr= [hex], caller= [hex]%SYS-2-SELF: s_setblock() on own process%SYS-2-SELFLINKED: Buffer [hex] linked to itself in free pool [chars]%SYS-2-SHARED: Attempt to return buffer with sharecount [dec],ptr= [hex]%SYS-2-SHARED1: Attempt to return buffer with sharecount [dec], ptr= [hex], caller= [hex]%SYS-3-SOCKUNKN: Unknown socket protocol [dec]%SYS-2-SPEC: Trying to set unknown special character [dec] to [dec]%SYS-6-STACKLOW: Stack for [chars] [chars] running low, [dec]/[dec]Explanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%SYS-2-SMASHED : Smashed block at 4085C, next 0, prev 0, size 3E80000 - Process = *Init*, level=5Explanation An internal software error occurred.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message% SYS-2-SMASHEDINFO : Smashed block last freed 0, allocated by 30000, nameExplanation A software error corrupted the memory.
Recommended Action Copy the message exactly as it appears and report it your technical support representative.
Error Message%SYS-4-SNMP_HOSTCONFIGSET: SNMP hostConfigSet request. Loading configuration from [int].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%SYS-4-SNMP_NETCONFIGSET: SNMP netConfigSet request. Loading configuration from [int].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%SYS-4-SNMP_WRITENET: SNMP WriteNet request. Writing current configuration to [int].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%SYS-2-SNMP0IDX: Attempt to [chars] snmpidb with if_index of 0.Explanation A software error occurred.
Recommended Action Copy the message exactly as it appears and report it your technical support representative.
Error Message%SYS-3-SUPNONE: Registry [dec] doesn't existExplanation A software error occurred.
Recommended Action Copy the message exactly as it appears and report it your technical support representative.
Error Message%SYS-2-SUPNOT: Can't create Registry [chars]Explanation An internal software consistency check failed.
Recommended Action Copy the message exactly as it appears and report it your technical support representative.
Error Message%SYS-5-TABLEERR: [chars] table [chars] damaged: [chars]Explanation An internal table entry became corrupted.
Recommended Action Copy the message exactly as it appears and report it your technical support representative.
Error Message%SYS-3-TIMERHOG: Timer callback ran long, PC = [hex], 10*ONESECExplanation A software error occurred.
Recommended Action Copy the message exactly as it appears and report it your technical support representative.
Error Message%SYS-3-TTYMEM: Tty[t-line], no memory to save tty default parametersExplanation 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%SYS-2-WATCHDOG: Process aborted on watchdog timeout, Process = [chars], ONESECExplanation The indicated process ran for such a long time without relinquishing the processor that the system killed it as a runaway.
Recommended Action If this error recurs, call your technical support representative for assistance.
Error Message%SYS-3-WRONGFREELIST: Block [hex], size [dec], on wrong free list ([dec], [dec])Explanation A freed buffer was placed on the wrong list of free buffers.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%SYS-2-WRONGPOOL: Buffer [hex] found in pool [hex], should be in pool [hex]Explanation A software error occurred.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
SYSMGT Error Messages
System Management error messages
Error Message%SYSMGT_RPC-3-IPC_ERROR: SYSMGT RPC - IPC [chars] [chars] failed ([chars])Explanation The Channel Interface Processor (CIP) card network management event processing subsystem failed to set up the Interprocess Communications port. Network management events will not be processed from installed CIP cards.
Recommended Action Report this error to your technical support representative.
Error Message%SYSMGT_RPC-3-NETMGT_EVENT: SYSMGT RPC - NETMGT Event: [chars] ([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%SYSMGT_SNALLC-3-EVENT_ERROR: SYSMGT SNA LLC - [chars] ([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.
TAC Error Messages
Terminal Access Controller Access Control System (TACACS) protocol error messages
Error Message%TAC-6-SENDTMO: Send type [dec] to [inet] timed outExplanation A background TACACS notification (enabled with the command tacacs notify) was not acknowledged by the TACACS server processor within the timeout period (5 minutes). The information contained in that notification was lost. This loss of information may interfere with accounting or auditing on the server.
This condition arises when the TACACS server is misconfigured, crashed, or became unreachable via the network.
Recommended Action Check the TACACS server and the network attached to it.
Error Message%TAC-4-UNEXREP: Reply for non-existent request, [dec] on queueExplanation The TACACS facility received a message it was not expecting. This may occur when a TACACS server sends duplicate responses or when it responds to a request that has already timed out. It also may be due to an internal software problem.
Recommended Action If this message recurs, call your technical support representative for assistance.
TBRIDGE Error Messages
Transparent bridging error messages
Error Message%TBRIDGE-4-GIANT, 0, Giant received on [chars], [dec] exceeds [dec]\n DA [enet] SA [enet] [[hex]], (5 * ONESEC)Explanation A packet was received that exceeds the expected maximum transmission unit (MTU) length for the receiving interface. The first four bytes of the packet following the source address are also provided to assist diagnosis.
Recommended Action Use the address and packet information provided to trace the source of these packets and reduce its MTU to conform to the standard for the given media.
Error Message%TBRIDGE-4-INVALIDMEDIA: Invalid media encountered for bridgingExplanation Transparent bridging was configured on an interface that does not support it.
Recommended Action Remove transparent bridging from the configuration on the specified interface.
Error Message%TBRIDGE-4-NOMEMORY: No memory available for transparent bridgingExplanation Packet memory was exhausted to the point that the few static buffers required for transparent bridging cannot be allocated.
Recommended Action Diagnose memory utilization using the show buffers and show memory commands.
Error Message%TBRIDGE-4-NOVCDROP: Destination VC unknown for packet, (5 * ONESEC)Explanation A transparently bridged packet destined for an ATM interface cannot be fully addressed.
Recommended Action Clear the bridge table to force re-learning of all addresses.
Error Message%TBRIDGE-4-NOVCFLOOD: No VC's configured for bridging on [chars], (5 * ONESEC)Explanation An ATM interface was configured for transparent bridging without also specifying the associated virtual circuits.
Recommended Action Configure the required virtual circuits on the specified interface.
Error Message%TBRIDGE-4-SMF_ACTION, 0, invalid action found for [sci_notation] on [chars] - [hex], (5 * ONESEC)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.
TCP Error Messages
Transmission Control Protocol error messages
Error Message%TCP-6-BADAUTH: Invalid MD5 digest from [inet]:[dec] to [inet]:[dec][chars]Explanation The system received a TCP packet with an invalid MD5 authentication digest on a connection endpoint. The message will end with the string "(RST)" if the incoming packet was a TCP reset packet.
Recommended Action Determine why the source of the packet is not generating correct digests on the connection. This could be due to either misconfiguration or security weaknesses.
Error Message%TCP-6-BADAUTH: No MD5 digest from [inet]:[dec] to [inet]:[dec][chars]Explanation The system received a TCP packet without an MD5 authentication digest on a connection endpoint which is expecting one. The message ends with the string "(RST)" if the incoming packet was a TCP reset packet.
Recommended Action Determine why the source of the packet is not generating digests on the connection. This could be due to either misconfiguration or security weaknesses.
Error Message%TCP-2-BUFFER: Tty[t-line], buffering bug%TCP-2-PUTBYTE: Tty[t-line], tcp_putbyte() with blocking disabledExplanation An internal software error occurred.
Recommended Action If either message recurs, call your technical support representative for assistance.
Error Message%TCP-6-NOTREADY: [chars] called but TCP not initializedExplanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%TCP-6-TOOBIG: Tty[t-line], too many bytes of options([dec])Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
TMQ Error Message
Inbound terminal port queuing error message
Error Message%TMQ-3-NOTFOUND: TMQ, Attempt to delete entry not in queueExplanation An attempt was made to delete an entry not in the queue.
Recommended Action Advisory message only. No action required.
TN Error Messages
Telnet error messages
Error Message%TN-2-BADLOGIN: Bad login string pointer [hex]%TN-3-BADSTATE: Illegal state [dec]%TN-3-READLINE: Unknown return code [dec] from telnet_readline()Explanation An internal software error occurred.
Recommended Action If any message recurs, call your technical support representative for assistance.
TR Error Messages
Token Ring error messages
Error Message%TR-3-ADPCHK: Interface [chars], 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%TR-3-ASYNCUSE: Unit [dec], [chars], async in useExplanation Another internal process is communicating with the given Token Ring interface.
Recommended Action Wait 1 minute and try again. If the condition persists, it probably indicates an internal software error. Copy the message exactly as it appears, and report it your technical support representative.
Error Message%TR-4-BADADAPT: Unit [dec], adapter not responding [hex] [hex][hex] [hex]Explanation A Token Ring interface is not responding to initialization.
Recommended Action Confirm the Token Ring card's configuration, and make sure it is in the correct slot. If the interface is in the correct slot, this message indicates a probable hardware failure. Copy the message exactly as it appears, and report it your technical support representative.
Error Message%TR-3-BADBRDGPARMS: Unit [dec], bad bridge parameters: bridge_num=[dec], max_rd= [dec]\nthisring=[dec], targetring=[dec]%TR-3-BADBUFFSIZE: Unit [dec], bad buffersize = [dec]%TR-3-BADFIRM: Unit [dec], Tokenring firmware download failed\n got [hex], expected [hex], at address [hex].[hex]%TR-3-BADFIRMTYPE: Unit [dec], bad firmware type code during [chars]. type=[hex], fw=[hex]%TR-3-BADFUNC: Unit [dec], bad functional address=[hex], ring mode=[hex]Explanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%TR-3-BADHEADER: RX - Unit [dec]: type [dec], size [hex], use [hex] flags [hex]Explanation The system detected corrupted data from the Token Ring interface card (CSC2R/1R and CSC-R16M only). There may be a hardware problem.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%TR-3-BADMUL: Unit [dec], Can't set TR address to hardware multicast address [enet]Explanation An attempt was made to set the Token Ring interface MAC address to a reserved multicast address.
Recommended Action Check your configuration. Make sure that your XNS and/or Novell Token Ring addresses have not inadvertently been set to reserved multicast addresses.
Error Message%TR-3-BADRNGNUM: Unit [dec], ring number ([dec]) doesn't match established number ([dec])Explanation The number you have configured for the local ring does not match the value currently in use on the ring.
Recommended Action Check the configuration to make sure you used the correct ring number. If it is correct, confirm the configuration of all other bridges on the ring to make sure they are using the same ring number.
Error Message%TR-3-BADSLOT: Unit [dec], Slot [dec] does not exist.Explanation This error message pertains only to the Cisco 4000. It is seen when software tries to access (discover) a network interface module (NIM) that is not in slot 1, 2, or 3. The software stalls trying to access the nonexistent slot. This message could indicate a card error.
Recommended Action If this message recurs, call your technical support representative for assistance or a replacement card.
Error Message%TR-3-BADSTART: Unit [dec], Start completion and wrong idb state -state= [dec]Explanation An internal software error occurred.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%TR-3-BADUNIT: Bad unit number [dec]Explanation This error message pertains only to the IGS. When displayed, it indicates that the system cannot find the chipset registers where it expects them to be. This is most likely a hardware error.
Recommended Action If this message recurs, call your technical support representative for assistance. It will be necessary to determine the hardware unit configuration.
Error Message%TR-4-BKGND: Unit [dec], bkgnd int: last packet out [dec]ms%TR-4-BKGNDINT: Unit [dec], bkgnd int: [hex][hex] [hex][hex][hex][hex] [hex][hex]Explanation An internal software error occurred.
Recommended Action If either of these messages recur, call your technical support representative for assistance.
Error Message%TR-3-BOGUSDATA: [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex]Explanation This message displays the first eight bytes of frame data if the data length is invalid. It is the second part of the %TR-3-BOGUSLENGTH error message that follows.
Recommended Action See recommended action for the %TR-3-BOGUSLENGTH error message.
Error Message%TR-3-BOGUSLENGTH: Unit [dec], bad input length [dec], [chars] code.Explanation This is the first message displayed when the frame data length is invalid. It is unique to the CSC-R16 Token Ring card for all system versions.
Recommended Action Display of both the %TR-3-BOGUSLENGTH and %TR-3-BOGUSDATA error messages indicates a serious problem on the interface between the Token Ring chipset, the SBE16 card, and the system driver. Copy the message exactly as it appears, and report it your technical support representative.
Error Message%TR-3-COMPFAIL: Unit [dec], Tbuf completion failure, result [hex]%TR-3-FILTFAIL: Unit [dec], SRB filter set failed: [hex] [hex][hex] [hex] (blk [hex]) downing%TR-3-GETCONF: Unit [dec], get_config failed, result [hex] [hex]Explanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%TR-3-DIAGFAIL: Interface [chars] failed init diags [hex] [hex], [chars]Explanation The microcode attempted to run its diagnostics on the chip and failed.
Recommended Action Issue a clear interface command. If this message recurs, call your technical support representative for assistance.
Error Message%TR-3-INCOM: Unit [dec], incompatible firmware: system [hex],interface [hex]Explanation The Token Ring interface contains firmware that is incompatible with the system software.
Recommended Action Call your technical support representative to upgrade the Token Ring Monitor firmware, the system software, or both.
Error Message%TR-3-INITFAIL: Unit [dec], init failed. result code=[hex], error code=[hex]Explanation The Token Ring hardware failed to initialize properly.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%TR-4-INTFAIL: Unit [dec] interface failure: [hex] [hex] [hex],idb state [dec]Explanation The Token Ring Monitor firmware detected a fatal error due either to an internal software problem or to a hardware failure.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%TR-3-MADGETX: Unit [dec], lost packet using Transmit Descriptor.Explanation This error message pertains only to the Cisco 4000. When displayed, it indicates that a packet was lost inside the Madge firmware, and the software lost the pointer to it.
Recommended Action This message indicates a software problem on the card. If this message recurs, call your technical support representative for assistance or a replacement card.
Error Message%TR-3-MODEFAIL: Unit [dec], change mode failed. result code=[hex], error code=[hex]%TR-3-MODFAIL: Unit [dec], tra_modify failed, result [hex] [hex]%TR-3-NOFIRM: Unit [dec], no TMS380 firmware present. eagle=[hex], magic=[hex]Explanation An internal 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%TR-3-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%TR-4-NOMOREPAGES: Unit [dec], Out of Pages for [chars].Explanation This error message pertains only to the Cisco 4000.When displayed, it indicates that the ability to switch the receive buffers for the Token Ring was halted due to an insufficient amount of memory.
Recommended Action Reduce other system activity to ease memory demands and then reset the Token Ring interface by entering a clear interface tokenring command. If these actions do not solve the problem, upgrade to a larger memory configuration or call your technical support representative for assistance.
Error Message%TR-3-NOPAK: Unit [dec], Tbuf completion and no pakoutExplanation An internal hardware or software error occurred.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%TR-3-OLDTRIF: Obsolete firmware in multibus TR unit [dec] - does not support fast switchingExplanation A firmware upgrade is needed.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%TR-3-OPENFAIL: Unit [dec], open failed: check the lobe cable DB-9 connectionExplanation The Token Ring interface was unable to insert itself into the ring. This is an indication of a busy or broken ring. The first character string in this error message indicates the stage of initialization at which the error occurred, and the second describes the error.
Recommended Action Try to open the interface again. This generally can be accomplished by issuing the clear interface tokenring command. If the error message recurs, call your technical support representative for assistance.
Error Message%TR-3-OPENFAIL2: Unit [dec], open failed: check the lobe cable connection.Explanation The Token Ring interface was unable to insert itself into the ring, and the error code returned indicates a wiring problem.
Recommended Action Check the cable connecting the router to the Token Ring MAU, and try to open the interface again. This generally can be accomplished by issuing the clear interface tokenring command. If the error message recurs, call your technical support representative for assistance.
Error Message%TR-3-PANIC: Unit [dec], panic [hex] [hex] [hex]Explanation The Token Ring monitor firmware detected a fatal error that indicates an impending interface failure.
Recommended Action Copy the error message and the interface message exactly as they appear and then report them to your technical support representative.
Error Message%TR-3-PANICINF: Unit [dec], PI [hex] [hex] [hex] [hex][hex] [hex]Explanation This message is similar to the %TR-3-PANIC error message, but indicates a nonfatal error. This message appears in very unusual situations that should not arise in normal operation.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%TR-3-PANICTYPE: Unit [dec], [chars] errorExplanation This message is similar to the %TR-3-PANIC error message, but indicates a nonfatal error. This message appears in very unusual situations that should not arise in normal operation.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%TR-3-RESETFAIL: Unit [dec], reset failed, error code [hex]Explanation An internal software error occurred.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%TR-3-RESETFAIL2: Unit [dec], reset failed, auxiliary processor init failedExplanation This message isolates a particular RESETFAIL condition from several other reset failure conditions. It is unique to the CSC-R16 Token Ring card for all system versions and indicates a state problem.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%TR-3-RIFBADMAGIC: Invalid magic number ([hex]) in RIF [chars] table entry [hex]%TR-3-RIFTBLTRASH: Trashed [chars] RIF table entry [hex] found and zeroedExplanation An internal software error occurred.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%TR-3-SETBRIDGEFAIL: Unit [dec], set bridge failed (code %#x)Explanation A hardware error occurred. The source routing accelerator (SRA) chip on the Token Ring card could not be initialized.
Recommended Action Call your technical support representative for assistance or a replacement card.
Error Message%TR-3-SETFAIL: Unit [dec], couldn't set interface to physical address [enet]Explanation An illegal MAC address was specified for this interface.
Recommended Action Normally the Token Ring interface uses the burned-in address contained in a PROM on the board. However, certain protocol stacks require the MAC address to be modified to an illegal value. Check your configuration for possible problems. If this message recurs, call your technical support representative.
Error Message%TR-3-SETFUNFAIL: Unit [dec], set functional address failed (code [hex])%TR-3-SETGRPFAIL: Unit [dec], set group address failed (code [hex])%TR-3-SETOPTFAIL: Unit [dec], set open options failed (code [hex])%TR-3-SMTSTATFAIL: Unit [dec], get_smt: get smt stats failed - result [hex]Explanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%TR-4-SNKBRIDG: Unit [dec], removing invalid bridgeExplanation The system could not start a Token Ring source-route bridge because the interface in question does not have the appropriate Token Ring Monitor firmware or hardware.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%TR-3-STARTFAILED: Unit [dec], start failed, result [hex],reason [hex]Explanation The Token Ring Monitor firmware attempted to insert the system into the ring, and the chipset detected a nonstandard fatal error.
Recommended Action This message indicates a problem with the Token Ring chipset hardware. Copy the message exactly as it appears, and report it your technical support representative.
Error Message%TR-3-STARTFAILED2: Unit [dec], start failed, auxiliary processor init failed.Explanation This error message isolates a particular STARTFAIL condition from several other reset failure conditions. It is unique to the CSC-R16 Token Ring card for all system versions and indicates a state problem.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%TR-6-STATE: TR[dec]: Ring Status: [chars]Explanation This message is displayed when the Token Ring's status changed as determined by the chipset. This information also is used to automatically determine whether the interface is still usable to propagate network traffic.
Recommended Action Informational message only. No action required.
Error Message%TR-3-STATFAIL: Unit [dec], get_static: get stats failed - Async: [hex] [hex] [hex] [hex]Explanation An internal software error occurred.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%TR-6-STATRING: TR[dec]: Ring Status: [chars] [chars] ([hex]) LIV [hex]Explanation This message is displayed when the Token Ring's status changed as determined by the chipset. This information also is used to automatically determine whether the interface is still usable to propagate network traffic. The meaning of each status code is shown in .
Recommended Action Check the Token Ring for the indicated condition.
Table 4 Token Ring Status Codes
Error Message%TR-3-TRACMD: tra_cmd: unit [dec] bad state: cmd [hex] [hex],result [hex] [hex] (blk [hex], iob [hex])%TR-4-UNKNOWNCOMP: Unit [dec], Unknown command completion:cmd [hex], rslt [hex]%TR-3-UNKNOWNT2M: Unit [dec], Unknown t2m command [hex] [hex]Explanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%TR-3-WIREFAULT: Unit [dec], wire fault: check the lobe cable MAU connectionExplanation The Token Ring hardware is reporting a wire fault condition.
Recommended Action Check the cable connecting the router to the Token Ring media attachment unit (MAU).
TUN Error Messages
Tunnel error messages
Error Message%TUN-4-BADOUTMODE: Interface [chars] unsupported output mode [dec] [chars]Explanation The tunnel interface was set to an encapsulation mode that is not supported.
Recommended Action Report the problem to your technical support representative and correct your configuration.
Error Message%TUN-4-RECURDOWN: [chars] temporarily disabled due to recursive routingExplanation When routing the same payload protocol over a carrier protocol (tunneling IP over IP, for example), it is possible to misconfigure your network so that you will try to route to the tunnel destination address via the tunnel. This is usually caused by a misconfiguration of the tunnel or a temporary instability due to route flapping elsewhere in your network. It is important to take steps to ensure that routing information between the carrier networks and the payload networks is not allowed to mix. If the router discovers a recursive routing problem, it will temporarily shut down the tunnel interface for a few minutes so that the situation that is causing this problem can resolve itself as routing protocols converge. If the problem is caused by misconfiguration, the link may oscillate indefinitely.
Recommended Action No action required.
Error Message%TUN-4-RECURSHUT: [chars] administratively disabled due to recursive routingExplanation If the recursive routing situation reported by the RECURDOWN message is not cleared up after ten bounces, the tunnel interface will be administratively shut down to avoid further flapping.
Recommended Action Determine the cause of the recursive routing situation, correct it, and then manually bring the interface back up using the no shutdown command.
UCODE Error Messages
Microcode error messages
Error Message%UCODE-3-BADCHKSUM: Bad checksum in [chars], found [hex] expected [hex]Explanation The microcode file is corrupted in some way; the checksum computed after reading the file from Flash does not match the one in the file. The file will not be downloaded, and the onboard ROM microcode will be used instead.
Recommended Action Reload the microcode. If the message recurs, call your technical support representative for assistance.
Error Message%UCODE-3-BADHWVER: Ucode file [chars] requires [chars] version [dec].x hardwareExplanation A mismatch was detected during an attempt to load a microcode file into an interface processor. The hardware requires a different version than the one specified.
Recommended Action Use the required microcode version.
Error Message%UCODE-3-HDRCORRUPT: Ucode header corrupted in [chars], found [hex] expected [hex]Explanation The microcode file is corrupted in some way; the checksum computed after reading the file from Flash does not match the one in the file. The file will not be downloaded, and the onboard ROM microcode will be used instead.
Recommended Action Reload the microcode. If the message recurs, call your technical support representative for assistance.
Error Message%UCODE-3-IPCBUFFAIL: Unable to obtain IPC resourcesExplanation The InterProcess Communication (IPC) service used to download microcode to certain interface processors has failed to obtain a buffer. Certain interface processors will not load properly.
Recommended Action Try the reload command again. If this message recurs, call your technical support representative for assistance.
Error Message%UCODE-3-IPCINITFAIL: Unable to initialize IPC [chars] servicesExplanation The InterProcess Communication (IPC) service used to download microcode to certain interface processors has failed to initialize. Certain interface processors will not load properly.
Recommended Action Reload the router.
Error Message%UCODE-3-IPCINVALID: Invalid IPC request [dec] received from [hex]Explanation The InterProcess Communication (IPC) service used to download microcode to certain interface processors has received an invalid message.
Recommended Action Verify that the proper revisions of code are selected.
Error Message%UCODE-3-LDFAIL: Unable to download ucode [chars] in slot [dec], installed ucode loadedExplanation For some reason, the microcode file specified by the configuration is not suitable for downloading, or another error occurred. The onboard ROM microcode will be loaded so the interface can remain operational.
Recommended Action Attempt to reload the microcode. If the message recurs, call your technical support representative for assistance.
Error Message%UCODE-3-NOBUF: Unable to allocate memory for ucode bufferExplanation A buffer is required to decompress microcode before loading it into an interface processor. This buffer could not be allocated for some reason.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%UCODE-3-NOFILE: Ucode file [chars] not found, installed ucode loaded in slot [dec]Explanation The file specified by the configuration was not found in Flash. The onboard ROM microcode will be loaded so the interface can remain operational.
Recommended Action Use show flash to determine if the file is located in Flash. If the file is there, attempt to reload the microcode. If the message recurs, call your technical support representative for assistance.
Error Message%UCODE-3-NOROM: Invalid attempt to load ROM ucode in slot [dec]Explanation Some interface processors cannot load microcode from ROM.
Recommended Action Remove the erroneous configuration statement.
Error Message%UCODE-5-OBSOLETE: FDDI unit [dec] has obsolete microcode: please upgrade itExplanation This message occurs when an FDDI interface processor is found running microcode that does not support microcode CMT, which is required for all software releases from 10.2 on.
Recommended Action Upgrade the microcode on the interface processor.
Error Message%UCODE-3-OLDHARD: Ucode file [chars] requires [chars] version [dec].[dec] hardware or laterExplanation The microcode specified requires a more recent version of the hardware than it found. The onboard ROM microcode will be loaded instead.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%UCODE-3-RDFAIL: Unable to read ucode file [chars] from flashExplanation For some reason, the microcode file was not read from Flash. Flash might be locked by another process or otherwise unavailable.
Recommended Action Use the show flash command to determine whether Flash is in use and issue another microcode reload when Flash is free. If the message recurs, call your technical support representative for assistance.
Error Message%UCODE-3-TOOBIG: File [chars] at length [dec] is too long for buffer size [dec]Explanation The file is too large for the buffer. The onboard ROM microcode will be loaded.
Recommended Action If the error message recurs after the onboard ROM microcode is loaded, call your technical support representative for assistance.
Error Message%UCODE-3-VERSIONCK: Inappropriate version [dec].[dec] for [chars]Explanation An attempt was made to load an inappropriate version of microcode.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%UCODE-3-WRONGHARD: [chars] is [chars] ucode not [chars], microcode/hardware mismatchExplanation The specified microcode file is for a different interface processor than specified in the configuration. The user has made a configuration error. The onboard ROM microcode will be loaded.
Recommended Action Reenter your microcode configuration command after confirming the interface type and reload the microcode.
UTIL Error Messages
Utility error messages
Error Message%UTIL-3-RANGEINCON: internal inconsistency [dec] [hex]Explanation A fatal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%UTIL-2-RANGERET: list [hex] no memory, can't return range [dec] [dec]Explanation A memory overflow error occurred.
Recommended Action Investigate memory usage. If memory usage is abnormal, call your technical support representative for assistance. Otherwise, increase router memory.
Error Message%UTIL-2-RANGEDUP: list [hex] already contains range [dec] [dec]Explanation A software error occurred.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%UTIL-3-RANGEINVERT: list [hex] low [dec] > high [dec]Explanation A software error occurred.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%UTIL-3-TREE: Data structure error--[chars], ONEMINExplanation A software error occurred, resulting in a data structure inconsistency.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative. Ask for their assistance in obtaining a version of code with the error fixed.
VINES Error Messages
Banyan Virtual Integrated Network Service error messages
Error Message%VINES-2-BADPARAM: [chars] called with [chars] parameter set to [chars]Explanation One of the VINES lookup functions was called with an illegal argument.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%VINES-2-BADTIMER: RTP timer for [chars] was found disabled, and was reset., 10*ONESECExplanation An internal interface timer is not running. This condition usually occurs after an interface reset.
Recommended Action None. The system automatically restarts the timer.
Error Message%VINES-2-CACHEFAILED:Cannot build cache entry ([dec] bytes) for [v-name] on [chars]Explanation The cache population routing for VINES fast switching determined that the MAC header on a packet is too large to fit into the cache.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%VINES-2-CACHEUNSUPP: Caching of [chars] not supported on [chars]Explanation The cache population routing for VINES fast switching was called for an interface that does not support VINES fast switching.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%VINES-2-CONSISTENCY: Error [chars]Explanation The VINES code ran into a situation that should not happen. For example, an IPC port number needs to be allocated, but all 65535 port numbers are currently in use.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%VINES-2-CORRUPTENTRY: Detected a corrupted entry in the [chars] tableExplanation The VINES code detected that an internal table entry was corrupted.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%VINES-2-DUPADDR: Duplicate address detected on interface [chars]Explanation The router detected that its VINES address is being used by another router.
Recommended Action Identify the other router that is using this address by manual inspection of the routers. Issue the command vines routing recompute on both routers. If a router does not support the recompute keyword, then on that router you must disable VINES, write the configuration to memory, reboot the router, and then reconfigure VINES.
Error Message%VINES-2-ENCAPFAILED: Encapsulation failed for [v-name] via [v-name] on [chars]Explanation The cache population routing for VINES fast switching encountered an encapsulation failure when building a cache entry for a neighbor.
Recommended Action Examine your configuration for causes of the encapsulation failure. Look for missing map statements, interfaces that have gone down, and so on.
Error Message%VINES-6-FNNOTFOUND: [chars] service [chars] routine missing [chars] vector.Explanation There is an inconsistency in the static VINES data structures for handling application-layer packets.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%VINES-2-INIT: Init code for [chars] doesn't match defined constant., 10*ONESECExplanation 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%VINES-2-INVALIDPATH: Bad [chars] in path for neighbor entry [v-name]Explanation While searching the neighbor table, the code determined that a pointer that should point to a VINES path structure actually points to some other structure.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%VINES-2-INVALIDROUTE: Bad [chars] in route for server entry [v-name]Explanation While searching the routing table, the code determined that a pointer that should point to a VINES route structure actually points to some other structure.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%VINES-6-IPCNOROUTINE: IPC port [dec] registered without an upcall [chars]Explanation There is an inconsistency in the active VINES data structure for handling IPC DATA messages. A message was received for a port that should have a listener, but the listener routine cannot be found.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%VINES-2-NEIGHBOR: vines_update called with null neighborExplanation An internal software error occurred.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%VINES-2-NOBUFFERS: No buffers available for [chars]Explanation There were no buffers available to send a packet.
Recommended Action Examine your system for memory or buffer leaks.
Error Message%VINES-2-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.
Error Message%VINES-2-NOVENCAP: Encapsulation failed on [chars], no vencap routineExplanation The VINES code tried to send a packet on an interface that does not have a new encapsulation routine.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%VINES-2-REASSEMBLY: SRTP reassembly code returned invalid result code [dec]., 10*ONESECExplanation An internal software occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%VINES-6-RPCNOSERVICE: IPC port [dec] registered without a service.Explanation There is an inconsistency in the active VINES data structure for handling Net RPC messages. A message was received for a port that should have a service description, but that service description cannot be found.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%VINES-6-RTNNOTFOUND: [chars] service [chars] routine not found while [chars].Explanation There is an inconsistency in the active VINES service description data structures. A service handler routine cannot find the description of its own service.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
VIP Error Messages
Versatile Interface Processor error messages
Error Message%VIP-3-BADMALUCMD: Unsupported MALU command [dec], arg=[hex], pascb=[hex]Explanation The Route Processor (RP) or the Route/Switch Processor (RSP) passed down a command that the software was not prepared to handle.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%VIP-3-CMDNOPASCB: PASCB Null for command [dec], arg=[hex]Explanation The Route Processor (RP) or the Route/Switch Processor (RSP) passed down a command that the software was unprepared to handle.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%VIP-3-NODISPATCH: Dispatch vector Null, cmd=[dec], dintf=[dec]Explanation No command dispatch vector was found for the specified interface.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%VIP-2-NOICBS: msg_noicbsExplanation No Switch Processor (SP) ICB structure was associated with the Port Adaptor (PA) or the interface.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%VIP-3-UNDEFIDBTYPE: Undefined idb type [dec]Explanation This message is sent from the VIP kernel when it sees a media type other than ethernet, token-ring, or serial. These are the media types supported by release 11.1 on the VIP. The message might be caused by having an older version of the software running on a device with a new VIP port adapter.
Recommended Action Check whether the version of the software being run supports the VIP port adapter. If that does not appear to be the problem, copy the error message exactly as it appears and report it to your technical support representative.
X25 Error Messages
X.25 error messages
Error Message%X25-3-ADDRESSBAD: Interface [chars], x25 address [chars] subaddress [char] is too long, X25_COMPLAIN_LEVELExplanation This message occurs when a subaddress is configured. When this subaddress is combined with the interface's X.121 address, the total address exceeds the limit of 15 characters.
Recommended Action Reconfigure the subaddress so that this does not happen.
Error Message%X25-3-BADCONFIG: Interface [chars], X.25 [chars], current configuration retained.Explanation The interface's X.25 configuration is not valid; the existing configuration was not changed.
Recommended Action Verify the following:
•
•
•
•
low/high parameter is also zero.•
Error Message%X25-4-BADMBIT: Interface [chars], VC [dec], partial data packet has M-bit setExplanation This message occurs when a virtual circuit is set up using the default maximum packet sizes, but the DTE and DCE are not configured with the same default values. A packet was received that had the M-bit set, signifying that more data follows, but the packet did not carry the maximum number of bytes allowed. Such partial data packets must have the M-bit cleared. The resulting loss of a message boundary might cause problems for the data recipient.
Recommended Action Verify the default flow control parameters of the DTE and the DCE. If this message recurs, call your technical support representative for assistance.
Error Message%X25-4-BADUPCALL: Interface [chars], Unexpected call ([chars]) from LLC2 DTE= [enet]%X25-4-DEBUG_LCI: LCI deleted at interrupt time%X25-2-ILLP4: Interface [chars], Illegal state [chars] when P4%X25-3-INTIMEQ: Interface [chars], LCN [dec] already in timer queue, new time [dec]%X25-3-NOLCI: Interface [chars], Delete: lci [dec] not found in [chars] table%X25-3-NOTFINDBH: Can't find bfe host address [inet] to delete%X25-3-NOTFINDI: Can't find address [inet] to delete%X25-3-NOTFINDS: Can't find address [chars] to delete%X25-3-SPURD1: Spurious D1 timer wakeup on LCI [dec]Explanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%X25-3-COMPERR: Interface [chars] LCI [dec] low-level stac compression error, X25_COMPLAIN_LEVELExplanation A Stacker compression algorithm internal error or shortage of buffer space was encountered during a compression operation. This should never happen.
Recommended Action Report the error to your technical support representative.
Error Message%X25-4-LARGEPKSIZE: Interface [chars], [chars] packet sizes [dec]/[dec] too large; lower values will be negotiated.Explanation The interface's default packet sizes or outgoing packet size facility values are too large to be carried by Link Access Procedure, Balanced (LAPB).
Recommended Action The router will negotiate lower packet size values automatically. The LAPB N1 value should be increased. For example, for an X.25 maximum packet size of 1024, modulo 8 X.25 operation will add 3 bytes of overhead and modulo 8 LAPB operation will add 4 bytes of overhead (the two bytes of CRC are defined to be included). This means that N1 must be at least 1031 bytes * 8 = 8248.
Error Message%X25-3-LCIBOGUS: in x25_timer NULL lci-idb [hex]Explanation An internal software error occurred.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%X25-5-NOBUF: Interface [chars] LCI [dec] [chars]Explanation This is a warning only (the compressed packet was not lost). However, an X.25 packet layer RNR (wait) was generated and packet-level transmission on the LCN will not resume (RR issued) until a decompression buffer becomes available.
Recommended Action If this message occurs frequently, you may need to modify the buffer pool. Copy the message exactly as it appears, and report it your technical support representative.
Error Message%X25-5-NOMEM: Interface [chars] LCI [dec] NO memory for dictionaryExplanation The 14K PBP history dictionaries could not be allocated. PBP compression is not enabled.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%X25-4-PARTIALMAP: Interface [chars], [chars] encapsulation call from [chars] partially mapped to [chars]Explanation An incoming X.25 call specified a protocol that was assigned to a multiprotocol map; the VC will not be able to carry the full set of protocols specified by the map.
Recommended Action Modify the configuration of the router or the far host to match the encapsulation method used.
Error Message%X25-5-PBPDBIT: Interface [chars] LCI [dec] PBP Compression does not support X25 D bit, X25_COMPLAIN_LEVELExplanation Compression is not enabled because D-bit support is configured for the LCI.
Recommended Action Reconfigure without D-bit support, or do not attempt to run with compression.
Error Message%X25-5-PBPHOLDQ: Interface [chars] LCI [dec] X25 Hold queue needs to be at least default size, X25_COMPLAIN_LEVELExplanation An attempt was made to configure the X.25 hold queue to less than the minimum value.
Recommended Action Configure the X.25 hold queue to be ten or more.
Error Message%X25-5-PBPNOEND: Interface [chars] LCI [dec] End system not configed for X25 PBP, X25_COMPLAIN_LEVELExplanation A compression or decompression operation was attempted by a router other than an end router. Only end routers can perform compression and decompression.
Recommended Action Reconfigure the routers so that only the end routers in the network perform compression and decompression.
Error Message%X25-3-PVCBAD: Interface [chars], PVC [dec], [chars]Explanation A switched PVC cannot be connected. The final [chars] text string in the message represents the state of the PVC. These text strings can also appear in show x25-vc output. For more information, refer to the show x25-vc documentation in the Router Products Command Reference publication.
Recommended Action Validate the configuration of the PVCs at both ends of the connection, and reconfigure them if necessary.
Error Message%X25-3-PVCDELETE: LCI for PVC [dec] being deleted!Explanation A PVC was using an x25 map entry that was deleted or the interface configuration changed to make the PVC number illegal; this forces the deletion of the PVC.
Recommended Action No action required. Note that some attached equipment may object to an inability to use the deleted PVC.
Error Message%X25-4-RANGEUNUSED: Interface [chars], [chars] VC range unused; set limits to zeroExplanation An outgoing-only or incoming-only virtual circuit range exactly overlaps the two-way virtual circuit range. This was the former method for specifying that a virtual circuit range was not used. The current method is to set the range limits to zero.
Recommended Action Use the privileged copy running-config startup-config command to write the configuration to memory. This will store the modified (zero) range limits.
Error Message%X25-3-SIZEBAD: Interface [chars] LCI [dec] Decompression size errorExplanation An internal software error occurred. The PBP header has an uncompressed packet size field. Each uncompressed packet size is checked against this field.
Recommended Action Contact your technical support representative for assistance.
Error Message%X25-3-SYNCBAD: Interface [chars] LCI [dec] Decompression sync error. Expected [dec], got [dec]Explanation An internal software error occurred. The PBP header has a sync field. The sync field (8 bits) is checked on each received packet.
Recommended Action Contact your technical support representative for assistance.
Error Message%X25-4-VCLOSTSYNC: Interface [chars], VC [dec] TCP connection [chars]Explanation An X.25 circuit that is being tunneled over a TCP connection between routers was cleared ungracefully. The last [chars] text string in the message can take one of two forms. If the text string is "closed unexpectedly," the router at the remote end of the connection was rebooted, or the connection failed. If the text string is "connection corrupted," it is likely that the connection was made to a router running an older software release.
Recommended Action If the text string is "closed unexpectedly," reestablish the connection after the remote router or intervening network is operational. If the text string is "connection corrupted," upgrade the router at the other end of the connection to a more recent software release.
Error Message%X25-3-VERSIONBAD: Interface [chars] LCI [dec] Compression Version mismatch. Expected [hex]; received [hex]Explanation An internal software error occurred. The PBP header has a mismatched version field. The version is checked on each received packet.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%X25-3-XOTPROTOCOL: XOT protocol error from [inet]: [chars]Explanation A protocol error was detected over an X.25-over-TCP (XOT) connection, causing the connected VC to close. A flaw may exist in the remote host's XOT implementation.
Recommended Action If this message recurs, call your technical support representative for assistance.
XNS Error Messages
Xerox Network Systems error messages
Error Message%XNS-3-BADPATHS: Invalid number of paths ([dec]) for [dec]%XNS-2-BADROUTE: Error [chars] route - null tableExplanation An internal software error occurred.
Recommended Action If either of these messages recur, call your technical support representative for assistance.
