Table Of Contents
ARAP Error Messages
Apple Remote Access Protocol error messages
Error Message%ARAP-3-ABORTED : TTY [dec]: arap callback aborted
Explanation An unexpected message was received during the Microcom Networking Protocol version 4 (MNP4) link setup.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%ARAP-6-ADDRFREE : TTY [dec]: ARAP ended for user [chars]; address [atalk_address]; [dec] seconds connected
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 command
Explanation 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 caused by 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_msg
Explanation 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 because of a configuration problem on the server. The error message should indicate the problem. This message does not indicate access denials caused by bad passwords.
Recommended Action Investigate the problem reported in the error message.
Error Message%ARAP-0-DEFAULT : TTY [dec]
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%ARAP-5-INITCONFUSED : TTY [dec]: ARAP unexpected initialization packet [chars]
Explanation The startup negotiation between a client and the ARA Protocol server fell out of order. If this message is received sporadically, it indicates line noise.
Recommended Action If this message recurs, reinstall the ARA client software.
Error Message%ARAP-6-LRPHASERROR : TTY [dec]: Received LT in CONNECTION PHASE
Explanation The router received an invalid packet during ARA connection setup phase.
Recommended Action Check for excessive line noise. Check the ARAP client software configuration for possible problems.
Error Message%ARAP-6-MAXRESENDS : TTY [dec]
Explanation The router resent MNP4 packets the maximum number of times without receiving an acknowledgment.
Recommended Action To determine the cause of the disconnection, correlate the receipt of this message with the user problem reports.
Error Message%ARAP-6-MNP4RCVDISC : TTY [dec]: MNP4 input disconnect
Explanation This indicates that the router received a disconnect request from the remote Macintosh client.
Recommended Action No action is required.
Error Message%ARAP-6-MNP4T401 : TTY [dec]: T401 [dec] baud rate [dec]
Explanation This message indicates that the router received MNP4 connection request. MNP4 acknowledgment timer value is also indicated.
Recommended Action No action is required.
Error Message%ARAP-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-2-NOLOG : TTY [dec]: Could not malloc log
Explanation Memory not available for internal MNP4 logging.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%ARAP-0-NOTNULLRESEND : TTY [dec]
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%ARAP-0-NULLRESEND : TTY [dec]
Explanation An internal software error occurred.
Recommended Action Report this error to your technical support representative.
Error Message%ARAP-5-PAKINVALID : TTY [dec]: ARAP invalid packet received
Explanation A corrupted packet reached the ARA Protocol code.
Recommended Action Check for excessive CPU usage or excessive line noise.
Error Message%ARAP-6-RCVGIANT : TTY [dec]: Rcv giant. dropping frame
Explanation The router received an oversized MNP4 frame.
Recommended Action Check for excessive line noise. Check the ARAP client software configuration for possible problems.
Error Message%ARAP-6-RCVNOPAK : TTY [dec]: Receive getbuffer failure. dropping frame
Explanation No buffer exists for an incoming packet.
Recommended Action Examine buffer usage statistics. Possibly more memory is required.
Error Message%ARAP-3-REMOTEERROR : TTY [dec]: arap input error
Explanation ARAP connection was terminated without a known cause.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%ARAP-6-RESENDSLOW : TTY [dec]
Explanation The router repeated resending of MNP4 packets as the Macintosh client failed to acknowledge previously resent packets.
Recommended Action If this error message persists for several ARAP connections, report it to your technical support representative.
Error Message%ARAP-3-TIMEOUT : TTY [dec]: arap expected message timeout
Explanation The software timed out during the MNP4 link setup.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%ARAP-6-TIMERERROR : TTY [dec]: MNP4 timeout error
Explanation The router is dropping the connection after doing maximum resends.
Recommended Action To determine the cause of the disconnection, correlate the receipt of this message with the user problem reports.
Error Message%ARAP-0-VSERROR : TTY [dec]: VS queued error
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%ARAP-0-WAITBADMSG : TTY [dec]: arg msg bad [hex]
Explanation The router received an invalid packet during ARAP MNP4 connection setup phase.
Recommended Action Check for excessive line noise. Check the ARAP client software configuration for possible problems.
Error Message%ARAP-6-XTICKLE : TTY [dec]: exited user [chars]: Other side stopped answering ARAP tickles (mnp4 pak resent [dec] mnp4 pak sent [dec] last [dec] now [dec])
Explanation The router disconnected as the remote Macintosh client stopped sending ARAP tickle or data packets.
Recommended Action To determine the cause of the disconnection, correlate the receipt of this message with the user problem reports.
ASPP Error Message
Asynchronous Security Protocol error message
Error Message%ASPP-3-NOTTY : [chars]: Unable to set Rx/Tx tty async service hooks
Explanation This message occurs only when ASP is configured. It indicates the serial interface using ASP is configured incorrectly or does not support asynchronous mode.
Recommended Action Verify the correct hardware interface type is being used.
AT Error Messages
AppleTalk error messages
Error Message%AT-6-ACQUIREMODE : [chars]: AppleTalk interface initializing; acquiring [chars]
Explanation The interface is determining the correct configuration. This message is displayed when discovery mode is enabled and no other router is detected.
Recommended Action No action is required.
Error Message%AT-5-ADDRINUSE : [chars]: AppleTalk node warning; address [atalk_address] already in use
Explanation The initial hint address was in use. A search will be made for a valid address.
Recommended Action No action is required.
Error Message%AT-5-ADDRINVALID : [chars]: AppleTalk node warning; address [atalk_address] is invalid
Explanation The hint address specified for the interface was not valid for the current configuration.
Recommended Action The hint address is ignored and a random valid hint address is automatically computed. No action is required.
Error Message%AT-6-ADDRUSED : [chars]: AppleTalk node up; using address [atalk_address]
Explanation No hint address or a bad hint address was specified. This message indicates which AppleTalk address will be used for the interface.
Recommended Action No action is required.
Error Message%AT-2-ASSERTFAILED : AppleTalk assertion failed: [chars]
Explanation The software detected an inconsistency. Although this error is serious, the router attempts to continue. AppleTalk processing might be impaired.
Recommended Action Copy the message exactly as it appears, note any AppleTalk problems you experience, and call your technical support representative.
Error Message%AT-5-BADNEIGHBOR : [chars]: AppleTalk neighbor ignored; [atalk_address] is misconfigured
Explanation 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_address] has gone bad
Explanation The system did not detect a route within the required timeout period. Therefore, the route is marked as bad. A network might have become unreachable for some reason, perhaps because of a broken connection. This message does not necessarily indicate an error condition.
Recommended Action No action is required.
Error Message%AT-7-BUGREPORT : AppleTalk bug: [chars]
Explanation The software detected an unexpected condition. The router takes corrective action and continues.
Recommended Action Copy the message exactly as it appears, note any AppleTalk problems you experience, and call your technical support representative.
Error Message%AT-3-CANTDEL : Cannot delete [chars] route [dec] by clearing; remove it by reconfiguring
Explanation You attempted to remove a route from the routing table by issuing the clear appletalk route command. The command failed because the route was on a directly connected interface (it was created when you configured the router).
Recommended Action Remove the route by reconfiguring the directly connected interface with which it is associated.
Error Message%AT-5-COMPATERR1 : [chars]: AppleTalk internet compatibility mode required by [atalk_address]
Explanation A neighboring router supports only extended AppleTalk networks with a cable range of 1 and with one assigned zone (for example, 25-25).
Recommended Action Upgrade the routers that support only the original AppleTalk specification. In the meantime, observe the compatibility rules for AppleTalk Phase 1 and Phase 2 routers.
Error Message%AT-5-COMPATERR2 : AppleTalk neighbor incompatibility; [atalk_address] has multiple zones
Explanation Although this router has neighbors that require your internetwork to observe compatibility rules, AppleTalk has learned of a route with multiple zone names defined. This condition can cause node inconsistencies on your AppleTalk network.
Recommended Action Upgrade the routers that support only the original AppleTalk specification. In the meantime, observe the compatibility rules for AppleTalk Phase 1 and Phase 2 routers.
Error Message%AT-5-COMPATERR3 : AppleTalk neighbor incompatibility; [atalk_address] has wide cable range
Explanation Although this router has neighbors that require your internetwork to observe compatibility rules, AppleTalk has learned of a route that has a cable range greater than 1. This condition can cause node inconsistencies on your AppleTalk network.
Recommended Action Upgrade the routers that support only the original AppleTalk specification. In the meantime, observe the compatibility rules for AppleTalk Phase 1 and Phase 2 routers.
Error Message%AT-5-COMPATERR4 : AppleTalk EIGRP neighbor incompatibility; [atalk_address] has same router ID ([dec])
Explanation Two routers on the network have the same router ID.
Recommended Action Reconfigure the router to have a unique router ID. If the problem recurs, copy the error message exactly as it appears and report it to your technical support representative.
Error Message%AT-6-CONFIGOK : [chars]: AppleTalk interface enabled; verified by [atalk_address]
Explanation The AppleTalk configuration was verified by consulting the indicated router.
Recommended Action No action is required.
Error Message%AT-7-DEBUGMSG : AppleTalk debug: [chars]
Explanation This message is generated by a debug command and provides additional information about an AppleTalk condition.
Recommended Action Copy the message exactly as it appears, note any AppleTalk problems you experience, and call your technical support representative.
Error Message%AT-3-DEFZONEERR : [chars]: AppleTalk interface warning; default zone differs from [atalk_address]
Explanation During the verification startup process, a disagreement occurred between the default zone (the first zone defined after the appletalk cable-range command) and the router that confirmed the configuration. When an AppleTalk end node is first connected to a network, it joins the default zone until it is overridden.
Recommended Action Use the appletalk zone command to correct the configuration so that all routers are advertising the same default zone. Note that several router implementations are known to mismanage the default zone.
Error Message%AT-6-DELROUTE : AppleTalk network deleted; [atalk_address] removed from routing table
Explanation A route on the AppleTalk network aged out.
Recommended Action No action is required.
Error Message%AT-3-DISCOFF : [chars]: AppleTalk node warning; discovery mode disabled
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%AT-3-DOMLOOP : Loop detected on domain [dec] [[chars]]
Explanation The domain router detected a routing loop. Routing loops are not allowed. The domain router runs a background loop detection process. The domain router starts this process when it receives a new zone list from a domain that is identical to the list in the main routing table and whose network range length matches that in this list. The loop detection process sends several AppleTalk Name Binding Protocol (NBP) loopback packets. When one of these packets is received on an interface that does not belong to the original domain, the domain router first shuts off all the domains involved in the loop, and then shuts off all the interfaces in these domains. The loop detection does not catch all types of loops. It is your responsibility to make sure that no loop exists.
Recommended Action Disable the cause of the routing loop. Then use the clear appletalk command to restart the interfaces involved.
Error Message%AT-3-DOMOVERFLOW : Remap range overflow for [chars] domain [dec]
Explanation The remap range overflowed. If a network (range) cannot fit inside the remapping range, the network or cable range being advertised by a neighboring router is not accepted. When an overflow occurs, all interfaces in the domain are disabled.
Recommended Action Use the appletalk domain remap-range command to increase the remapping range. Then restart the interfaces.
Error Message%AT-5-DUPADDR : [chars]: AppleTalk interface restarting; node address taken by [sci_notation]
Explanation Another AppleTalk node on a common network interface claimed the same AppleTalk address used by this router. This error indicates a serious, unexpected problem. If it recurs, a physical network problem might exist in which the nodes cannot communicate with each other.
Recommended Action The interface on this router restarts AppleTalk processing on the common network interface to resolve the address conflict. No action is required.
Error Message%AT-6-EIGRPLINKDN : AppleTalk EIGRP link down: [chars]
Explanation An AppleTalk hardware interface was disabled.
Recommended Action No action is required.
Error Message%AT-6-EIGRPLINKUP : Appletalk EIGRP link up: [chars]
Explanation An AppleTalk Enhanced IGRP interface that was previously shut down was restarted.
Recommended Action No action is required.
Error Message%AT-6-EIGRPLOG : EIGRP logging: [chars] from [atalk_address] ([int]) on [chars] for network [atalk_address], metric [int] / [int]
Explanation A new AppleTalk Enhanced IGRP path has been learned. The message indicates the source of the path, its distance in hops, its metric, and the type of path.
Recommended Action No action is required.
Error Message%AT-4-EIGRPLOTSOWORK : AppleTalk EIGRP WorkQ processed [int] entries, required [int] ms, did [chars] suspend
Explanation AppleTalk Enhanced IGRP did not have enough time to process packets.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%AT-6-EIGRPPEERDN : AppleTalk EIGRP peer down: [atalk_address], router ID: [int], just lost on [chars]
Explanation A peer router is unreachable.
Recommended Action No action is required.
Error Message%AT-6-EIGRPPEERUP : AppleTalk EIGRP peer up: [atalk_address], router ID: [int], newly heard on [chars]
Explanation A new neighbor appeared on the network.
Recommended Action No action is required.
Error Message%AT-5-FDDICOMPAT : AppleTalk FDDI neighbor [atalk_address] using obsolete FDDI addressing
Explanation Another AppleTalk router on the FDDI ring is running a release of the router software earlier than 9.0(2). Routers running these early software releases use an encapsulation for AppleTalk on FDDI rings that is not compatible with the Apple FDDITalk implementation.
Recommended Action Upgrade the routers running the software releases that use the pre-FDDITalk encapsulation for AppleTalk on FDDI rings.
Error Message%AT-3-IFCONFLICT : [chars]: AppleTalk interface disabled; conflicts with interface [chars]
Explanation An attempt was made to configure an interface to have 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 interface restarting; interface cleared
Explanation A clear interface command was issued on an interface that is currently routing AppleTalk.
Recommended Action No action is required.
Error Message%AT-5-INTDOWN : [chars]: AppleTalk node down; line protocol down
Explanation An AppleTalk hardware interface was disabled because of a bad serial line, a configuration command, or a bad interface.
Recommended Action If the interface was not intentionally disabled, this message indicates a hardware problem. In this case, repair or replace the applicable hardware.
Error Message%AT-5-INTRESTART : [chars]: AppleTalk interface restarting; protocol restarted
Explanation The hardware interface was reset because of a configuration change. After the reset, AppleTalk automatically reinitialized the interface.
Recommended Action No action is required.
Error Message%AT-6-INTUP : [chars]: AppleTalk interface restarting; line protocol came up
Explanation An AppleTalk interface that was previously shut down was restarted.
Recommended Action No action is required.
Error Message%AT-3-INVNBPCMD : Invalid NBPtest command [chars]
Explanation An unrecognized command was specified in the Name Binding Protocol (NBP) test facility.
Recommended Action Enter a valid command.
Error Message%AT-5-LOSTNEIGHBOR : [chars]: AppleTalk neighbor down; lost contact with [atalk_address]
Explanation A peer router is unreachable.
Recommended Action No action is required.
Error Message%AT-4-MACIPBADCONF : [chars]: MacIP inoperable configuration, [int]
Explanation If the appletalk event-logging command is configured, this message appears on the console when a MacIP server cannot begin or recover operations because of an invalid IP address configuration. This condition only occurs when the configured MacIP server's IP address is not valid on the same cable of any operable IP interface. The AppleTalk zone served by the MacIP server replaces the zone specified in the appletalk zone command. The IP address configured on the MacIP server replaces the IP address configured by the ip address command. When this error occurs, the MacIP configuration is considered invalid and is deleted.
Recommended Action No action is required.
Error Message%AT-6-MACIPDOWN : [chars]: MacIP server shutting down, [int]
Explanation If the appletalk event-logging command is configured, this message appears on the console when a MacIP server is no longer operational for any reason. MacIP servers shut down in response to MacIP configuration changes or errors, or a change in the condition or configuration of an AppleTalk or IP interface for which the MacIP server is providing service. The AppleTalk zone served by the MacIP server replaces the zone specified in the appletalk zone command. The IP address configured on the MacIP server replaces the IP address configured by the ip address command.
Recommended Action No action is required.
Error Message%AT-4-MACIPNOCABLE : [chars]: MacIP inoperable IP interface, [int]
Explanation If the appletalk event-logging command is configured, this message appears on the console when a MacIP server can no longer operate because of a change in the condition of the IP interface it serves. This condition can occur if IP routing is shut down on the interface, or the IP address of the interface is changed so that the MacIP server's IP address is no longer valid on the same cable. The AppleTalk zone served by the MacIP server replaces the zone specified in the appletalk zone command. The IP address configured on the MacIP server replaces the IP address configured by the ip address command.
Recommended Action No action is required.
Error Message%AT-6-MACIPUP : [chars]: MacIP server operational, [int]
Explanation If the appletalk event-logging command is configured, this message appears on the console when a MacIP server is fully initialized and is ready to accept client requests. The AppleTalk zone served by the MacIP server replaces the zone specified in the appletalk zone command. The IP address configured on the MacIP server replaces the IP address configured by the ip address command.
Recommended Action No action is required.
Error Message%AT-3-MCMISMATCH : [chars]: AppleTalk interface warning; zone multicast [sci_notation] differs from our multicast [sci_notation]
Explanation A computed multicast address disagrees with that provided by another AppleTalk router. The other AppleTalk router might be misconfigured or faulty.
Recommended Action Correct the problem at the other router.
Error Message%AT-6-NBRDELETED : Neighbor entry for [atalk_address] deleted
Explanation The clear appletalk neighbor command displays this command when it completes successfully.
Recommended Action No action is required.
Error Message%AT-6-NEIGHBORUP : [chars]: AppleTalk neighbor up; [atalk_address] has restarted
Explanation A neighboring router to which this router previously lost connectivity reappeared on the network.
Recommended Action No action is required.
Error Message%AT-3-NETDISAGREES : [chars]: AppleTalk interface disabled; network incompatible with [atalk_address]
Explanation The interface was disabled because the configured AppleTalk address or cable range for the interface conflicts with that of another router on the attached network.
Recommended Action Reconfigure the affected routers so that there are no conflicting addresses or cable ranges on the attached network.
Error Message%AT-4-NETINVALID : [chars]: AppleTalk node down; conflicts with active internet
Explanation The configuration specified for the interface conflicts with the active AppleTalk internetwork. For example, a cable range might be configured that overlaps an existing route but does not match the entry exactly.
Recommended Action Use the appletalk cable-range command to reconfigure the interface so that there are no conflicts with the existing AppleTalk network, or take any other actions necessary to resolve the conflict. AppleTalk will periodically attempt to restart the interface.
Error Message%AT-6-NEWNEIGHBOR : [chars]: AppleTalk neighbor added; [atalk_address] is operational
Explanation The router discovered a new AppleTalk router on the network.
Recommended Action No action is required.
Error Message%AT-6-NEWROUTE : [chars]: AppleTalk network added; [atalk_address] via [atalk_address] ([dec] hop [chars])
Explanation A new AppleTalk route was learned. The message indicates the source of the route and its distance in hops.
Recommended Action No action is required.
Error Message%AT-6-NEWZONE : AppleTalk zone added; zone [chars] defined
Explanation A new AppleTalk zone was created.
Recommended Action No action is required.
Error Message%AT-3-NOADDRSAVAIL : [chars]: AppleTalk node down; no addresses available
Explanation No free node could be found on the interface.
Recommended Action If your AppleTalk network has less than 250 nodes, issue the debug appletalk errors command and then call your technical support representative. If your AppleTalk network has more than 250 nodes, split it into smaller networks by creating new segments and moving some nodes into the new segments.
Error Message%AT-3-NOBESTPATH : Could not compute best path for network [atalk_address]
Explanation A path to the specified network could not be found.
Recommended Action Use the show appletalk route command to verify that a path to the specified network exists. If it does, copy the error message exactly as it appears, and report it along with the output of the show appletalk route command to your technical support representative.
Error Message%AT-6-NODEWRONG : [chars]: AppleTalk node [atalk_address] misconfigured; reply has been broadcast
Explanation An AppleTalk node sent a GetNet Info request to this router specifying an invalid network number for the source of the GetNet Info request. This situation occurs when an AppleTalk end node is moved to another network and is, therefore, misconfigured for the current network.
Recommended Action No action is required.
Error Message%AT-1-NOMEM : Could not allocate memory for [chars] at line [dec] in [chars]
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%AT-6-NOPROXY : AppleTalk proxy deleted; zone [chars] freed network [atalk_address]
Explanation A previously configured Name Binding Protocol (NBP) proxy was deleted. The router can no longer convert NBP requests to a format understood by routers that support only the original AppleTalk specification.
Recommended Action No action is required.
Error Message%AT-3-NOROUTE : No route to destination [atalk_address]
Explanation The router could not deliver a packet to a destination because it did not know where to send it.
Recommended Action Use the show appletalk route command to verify that a path to the destination exists. If it does, copy the error message exactly as it appears, and report it with the output of the show appletalk route command to your technical support representative.
Error Message%AT-3-NOSRCADDR : [chars]: AppleTalk packet error; no source address available
Explanation The router could not generate an AppleTalk packet because no valid AppleTalk source address was available to identify this router in the packet.
Recommended Action Configure an interface to have an address or cable range. Use the show appletalk command to verify that the interface is operational.
Error Message%AT-3-NOSUCHNBR : No such neighbor, [atalk_address]
Explanation You specified a nonexistent neighbor address in a show appletalk neighbor or clear appletalk neighbor command.
Recommended Action Specify a valid neighbor address (one that appears in the output of the show appletalk neighbor command).
Error Message%AT-5-NOSUCHROUTE : No such route [dec]
Explanation You specified a nonexistent route in a show appletalk route or clear appletalk route command.
Recommended Action Specify a valid route (one that appears in the output of the show appletalk route command).
Error Message%AT-3-NOTRUNNING : AppleTalk not running
Explanation You tried to show or change the AppleTalk configuration when AppleTalk routing was not turned on.
Recommended Action Issue the appletalk routing command before issuing any other AppleTalk configuration or display command.
Error Message%AT-5-NOTSUPPORTED : [chars]: AppleTalk node down; line protocol not supported
Explanation An encapsulation method on the specified interface does not support AppleTalk.
Recommended Action No action is required.
Error Message%AT-3-NOVIRTUAL : [chars]: client tried to connect, but no virtual network is declared
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-OLDMCI : [chars]: AppleTalk route cache disabled; firmware is obsolete
Explanation The firmware on the MCI controller card does not support AppleTalk fast switching.
Recommended Action No corrective action is required. Normal AppleTalk operation continues, but the fast-switching cache is disabled for the interface associated with the MCI card. If this message is unexpected, verify that the MCI firmware for the interface specified in the error message is at level 1.7 or higher.
Error Message%AT-6-ONLYROUTER : [chars]: AppleTalk interface enabled; no neighbors found
Explanation No other AppleTalk routers were found on the network attached to the interface.
Recommended Action No action is required.
Error Message%AT-3-OUTOFSYNC : [chars]: AURP connection out of sync...terminating
Explanation AppleTalk Update-Based Routing Protocol (AURP) detected packets that were out of sequence. This might be caused by a lost connection.
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_address] added; via [atalk_address] (metric [dec])
Explanation A new AppleTalk path has been learned. The message indicates the source of the path, its distance in hops, its metric, and the type of path.
Recommended Action No action is required.
Error Message%AT-5-PATHCHANGE : Route to [atalk_address] is now using path of type [chars] on [chars] via [atalk_address]
Explanation The path to a network changed because either the old path went down or the new path was better.
Recommended Action No action is required.
Error Message%AT-6-PATHDEL : [chars]: AppleTalk [chars] path to [atalk_address] via [atalk_address] has been deleted
Explanation A path on the AppleTalk network aged out.
Recommended Action No action is required.
Error Message%AT-6-PATHNOTIFY : [chars]: AppleTalk [chars] path to [atalk_address] down; reported bad by [atalk_address]
Explanation A router went down somewhere on the AppleTalk network. The indicated peer notified this router of the change.
Recommended Action No action is required.
Error Message%AT-4-PATHREJECTED : AURP path [atalk_address] rejected; conflict detected
Explanation The router detected a conflicting cable range. A router is configured with a cable range that overlaps with an existing range, but does not match the entry exactly.
Recommended Action Use the show appletalk command to identify the overlapped cable range, and then reconfigure the misconfigured router.
Error Message%AT-6-REGPENDING : NBP registration of [chars] at [[chars]] pending
Explanation A name registration call is being performed.
Recommended Action No action is required.
Error Message%AT-6-ROUTEDOWN : [chars]: AppleTalk network down; interface to [atalk_address] disabled
Explanation A connected route is being advertised as down (also known as "notify neighbor") because the configured interface is no longer operational.
Recommended Action No action is required.
Error Message%AT-6-ROUTENOTIFY : [chars]: AppleTalk network down; [atalk_address] reported bad by [atalk_address]
Explanation A router went down somewhere on the AppleTalk network. The indicated peer notified this router of the change.
Recommended Action No action is required.
Error Message%AT-6-ROUTEOK : [chars]: AppleTalk network up; [atalk_address] via [atalk_address] ([dec] hop [chars])
Explanation A routing update was received for a previously suspect route.
Recommended Action No action is required.
Error Message%AT-5-RTMPSTATE : [chars]: RTMP path to [atalk_address] via [atalk_address] now in [chars] state (metric [dec], [dec] hops)
Explanation The state of a path changed.
Recommended Action No action is required.
Error Message%AT-3-SUBROUTINE_ERROR : AppleTalk error: [chars]
Explanation An internal error occurred. Specifically, a programming assertion in the AppleTalk networking code was violated.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%AT-3-ZONEDISAGREES : [chars]: AppleTalk interface disabled; zone list incompatible with [atalk_address]
Explanation The zone list of the configured interface is inconsistent with the zone list of other routers.
Recommended Action Reconfigure the zone list on the router so that it does not conflict with that the zone lists on other routers.
Error Message%AT-6-ZONEGC : AppleTalk zone deleted; zone [chars] released
Explanation The router removed an unused zone from the zone table.
Recommended Action No action is required.
Error Message%AT-6-ZONEPROXY : AppleTalk proxy defined; zone [chars] using network [atalk_address]
Explanation This message reports the zone name and network number that are being advertised to support the appletalk nbp-proxy command.
Recommended Action When proxy service is initiated, this message is generated each time the appletalk nbp-proxy command is issued. No action is required.
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 the following unrelated reasons. Each reason is accompanied by a recommended action.
•
The virtual circuit descriptor (VCD) exceeded the maximum available memory. Use a smaller VCD number.
•
•
•
•
•
•
•
Recommended Action If none of the previous actions fix the problem, copy the error message exactly as it appears and report it to your Cisco technical support representative.
Error Message%ATM-4-ILMICONFIGCHANGE : ILMI([chars]): Restarting interface. Peer Configuration change detected
Explanation Configuration of adjacent peer device has been changed.
Recommended Action Wait for the interface to restart itself.
Error Message%ATM-4-ILMIKEEPALIVEFAIL : ILMI([chars]): Restarting interface. Keepalive failure detected
Explanation Adjacent peer device is not responding to Interim Local Management Interface (ILMI) Keepalive polling.
Recommended Action Check the connection of the ATM interface and the status of the adjacent peer device. Correct them if necessary. Wait and check if ILMI Keepalive comes up again. If the problem persists, copy this warning message exactly as it appears, and report it to your technical support representative.
Error Message%ATM-4-MTUCALLMISMATCH : Call from: ATM NSAP - [chars] has mismatched PDU size - forward size is [dec] - backward size is [dec], int [chars] PDU size [chars] [chars]
Explanation The calling or called party has a maximum transmission unit (MTU) size configured that is different from the MTU size on the current interface.
Recommended Action Either change the configured MTU size on the current interface to that of the caller's or called party's interface, or change the caller's or called party's interface to match the current interface.
Error Message%ATM-3-OVERSUBSCRIBED : Interface [chars]: Total [chars] allocation [int][chars] exceeded maximum [chars] of [int][chars]
Explanation A software or hardware error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
BAP Error Messages
PPP Bandwidth Allocation Protocol error messages
Error Message%BAP-4-NOSTATE : [chars] [chars] [chars] in illegal state [dec]
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.)
Error Message%BAP-4-WAVL : Failed to initialize AVL tree, BAP not started
Explanation BAP will not be operational and will not be negotiated.
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.)
BGP Error Messages
Border Gateway Protocol error messages
Error Message%BGP-3-ADDROUTE : Unable to add route for [inet] to radix trie
Explanation An addition to the radix trie could not be completed because of an error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%BGP-6-ASPATH : Invalid AS path [chars] received from [int]: [chars]
Explanation The remote BGP peer sent in an update with an invalid AS path.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%BGP-3-BADMASK : Attempt to install route for [int] without valid mask in [chars]
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%BGP-3-DELPATH : Attempted to delete path from an empty net for [inet]
Explanation A BGP path could not be deleted because of an error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%BGP-3-DELROUTE : Unable to remove route for [inet] from radix trie
Explanation A deletion from the radix trie could not be completed because of an error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%BGP-2-INSUFMEM : Insufficient memory for [chars] entry
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%BGP-3-MAXPATHS : Too many parallel paths for [inet], maximum is [dec]
Explanation The number of parallel paths exceeds the configured limit.
Recommended Action Increase the number of parallel paths allowed.
Error Message%BGP-6-NEXTHOP : Invalid next hop ([int]) received from [int]: [chars]
Explanation The remote BGP peer sent in a route with an illegal next hop. The given route was ignored.
Recommended Action No action is required.
Error Message%BGP-2-NOMEMORY : No memory for [chars] entry, resetting
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%BGP-3-RADIXINIT : Radix trie initialization failed
Explanation Initialization of the radix trie 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-1-INITFAIL : msgtxt_initfail
Explanation The hardware failed to initialize correctly.
Recommended Action Repair or replace the controller.
Error Message%BRI-1-NOMEMORY : msgtxt_nomemory
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%BRI-4-NOSWITCH : msgtxt_initfail
Explanation ISDN leased line requires an ISDN switch type configure.
Recommended Action Choose and configure a BRI switch type; if unsure, choose any switch.
BRIMUX Error Messages
AS5200 BRIMUX board error messages
Error Message%BRIMUX-3-BADBRIMUX : Slot [dec] [chars]
Explanation A BRIMUX firmware problem may be present.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%BRIMUX-1-BADCODE : Software error: [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%BRIMUX-3-BADDLACK : Slot [dec] BRIC, failed to acknowledge download data block [dec]
Explanation A BRIMUX firmware problem may be present.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%BRIMUX-3-BADDPM : Slot [dec] DPM, test failed at offset 0x[hex], expect 0x[hex], read 0x[hex]
Explanation A BRIMUX board hardware problem may be present.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%BRIMUX-3-CHANUPDOWN : B[dec] of BRI[dec] on slot [dec] BRIC, changed state to [chars]
Explanation A B-channel on the BRIMUX board changed state.
Recommended Action No action is required.
Error Message%BRIMUX-4-HEARTBEAT : Slot [dec] BRIC, lost heartbeat for [dec] seconds
Explanation A BRIMUX board hardware or firmware problem may be present.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%BRIMUX-3-PORTUPDOWN : BRI[dec] on slot [dec] BRIC, changed state to [chars]
Explanation A port on the BRIMUX board changed state.
Recommended Action No action is required.
Error Message%BRIMUX-3-UPDOWN : Slot [dec] BRIC, changed state to [chars]
Explanation A BRIMUX board changed state.
Recommended Action No action is required.
BSC Error Messages
Binary Synchronous Communications (Bisync) protocol error messages
Error Message%BSC-3-BADLINESTATE : Line state Tx when receiving non-Tx event: [dec]. On line: [chars]
Explanation An unexpected receive occurred during a transmission.
Recommended Action Verify that the line has been consistently defined with regard to the carrier. If the message is continuously reported, issue the shut and no shut commands to restart the bisynchronous interface in question. If the frequency of the message is once every couple minutes and CPU utilization is high, this message can be disregarded.
Error Message%BSC-3-BADPEERTYPE : Peer [chars] is incorrect type
Explanation This message occurs only when BSC local acknowledgment is configured. It indicates the serial interfaces that are using the BSTUN tunnel are configured incorrectly (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]
Explanation An internal software error occurred.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%BSTUN-3-BADLENOP : [chars]: bad len or unknown op, op [dec], len [dec]
Explanation An internal software error occurred.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%BSTUN-3-BADMAGIC : [chars]: wrong magic, mine [hex], theirs [hex] ([dec])
Explanation An internal software error occurred.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%BSTUN-3-BADMAGICTCP : [chars]: peer [chars], wrong magic, mine [hex], theirs [hex]
Explanation An internal software error occurred.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%BSTUN-3-BADPASSIVEOPEN : passive open from [int]([dec]) - [dec] failed
Explanation An internal software error occurred.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%BSTUN-3-CONNILLSTATE : CONN: Peer [chars], illegal state [dec]
Explanation An internal software error occurred.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%BSTUN-6-CONNOPENFAIL : CONN: peer [chars] open failed, [chars] [[int]]
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 the message recurs, copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%BSTUN-3-IFNOTSETUP : Could not setup interface for protocol [chars]
Explanation BSTUN was unable to start the interface for handling the specified protocol traffic.
Recommended Action If this message appears while you are configuring BSTUN, check for other system errors (such as no available memory in the router, or the interface shutting down). If no obvious problem can be detected, record all the displayed values and any other BSTUN error messages, and contact your technical support representative.
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 that 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-NOPEER : No peer configured to route frame with destination address [chars] (bstun group [dec])
Explanation A BSTUN route has not been configured for the frame with a destination address.
Recommended Action If this message appears while you are debugging BSTUN, it indicates that no specific BSTUN route has been configured for the frames being received with the device address listed in the packet debug trace. You may choose to configure a BSTUN route, or ignore this message.
Error Message%BSTUN-6-OPENED : [chars]: peer [chars] opened, [previous state [chars]]
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 No action is required.
Error Message%BSTUN-6-OPENING : CONN: opening peer [chars], [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 No action is required.
Error Message%BSTUN-6-PASSIVEOPEN : passive open [int]([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 No action is 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 No action is required.
Error Message%BSTUN-4-PEERSTATE : Peer [chars], wrong state [dec] ([dec])
Explanation An internal software error occurred.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
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 message appears while you are unconfiguring BSTUN, no action is required. Otherwise, record all the displayed values and any other BSTUN error messages, and 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 No action is required.
Error Message%BSTUN-3-SENDPUNT : [chars]: sent [chars] to [chars]
Explanation An internal software error occurred.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%BSTUN-4-SENDPUNTTCP : [chars]: sent [chars] to ([[int]])[int]
Explanation An internal software error occurred.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
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], [int]([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 An event passed to the BSTUN layer for processing could not be decoded.
Recommended Action Perform a hard restart on the indicated interface.
C1600 Error Messages
Cisco 1600 platform error messages
Error Message%C1600-4-BADINTFC : Interface [dec], (0-1 Onboard interfaces 2=WIC) Invalid interface (Unknown, Uninitialized or Bad Cookie value read)
Explanation Your router is functional. However, there is an interface that the software does not recognize.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%C1600-4-INTFCNOFLH : Unable to load images or communicate over interface
Explanation The operation might have failed because of a transient network problem.
Recommended Action Retry the operation. If the problem persists, call your technical support representative for assistance.
C3600 Error Messages
Cisco 3600 platform error messages
Error Message%C3600-3-ACFAIL : System detected Redundant Power System AC FAIL condition
Explanation The Redundant Power System experienced an AC failure.
Recommended Action One of the AC inputs has failed on the Redundant Power Supply. The "AC Input" LED on the front of the Redundant Power Supply will identify which AC input has failed. Ensure that the AC circuit in your building is operational, verify that the power cord is plugged into the Redundant Power Supply, and ensure that the AC power switch on the Redundant Power Supply is on.
Error Message%C3600-3-ACOK : Redundant Power System AC condition is now normal
Explanation The Redundant Power System AC is normal.
Recommended Action This is an informational message only. No action is required.
Error Message%C3600-3-BADNV : Detected invalid NVRAM size: [dec] bytes
Explanation The detected size of nonvolatile RAM (NVRAM) is not one of the supported sizes. The NVRAM may be bad.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%C3600-3-DCFAIL : System detected Redundant Power System DC FAIL condition
Explanation The Redundant Power System experienced a DC failure.
Recommended Action One of the DC outputs has failed on the Redundant Power Supply. The "DC Status" LED on the front of the Redundant Power Supply will identify which DC output has failed. When there is a DC failure, you must replace the Redundant Power Supply.
Error Message%C3600-3-DCOK : Redundant Power System DC condition is now normal
Explanation The Redundant Power System DC is normal.
Recommended Action This is an informational message only. No action is required.
Error Message%C3600-3-MULTFAIL : There is more than one failure with the Redundant Power System; please resolve problems immediately
Explanation The Redundant Power System experienced multiple failures. This is a critical condition.
Recommended Action There are multiple failures on the Redundant Power Supply. Examine the LEDs on the front of the Redundant Power Supply to find out which failures have occurred.
Error Message%C3600-3-OVERTEMP_OK : System temperature is now normal
Explanation The system is operating at a normal temperature.
Recommended Action The system previously detected an over-temperature condition, which has now cleared. This is most likely because of a high ambient temperature where the router is located.
Error Message%C3600-3-RPSOK : Redundant Power System is now normal
Explanation The Redundant Power System is operating normally.
Recommended Action This is an informational message only. No action is required.
Error Message%C3600-3-THERMAL : System detected Redundant Power System THERMAL FAIL condition
Explanation The Redundant Power System experienced either a fan failure or an over-temperature condition.
Recommended Action Look at the "FAN" and "TEMP" LEDs on the front of the Redundant Power Supply. If the "FAN" LED is amber, one of the fans has failed and you should replace the Redundant Power Supply. If the "TEMP" LED is amber, the ambient temperature is too high.
Error Message%C3600-3-THERMOK : Redundant Power System THERMAL condition is now normal
Explanation The Redundant Power System THERMAL is now normal.
Recommended Action The Redundant Power Supply previously detected an over-temperature condition, which has now cleared. This is most likely because of a high ambient temperature where the Redundant Power Supply is located. A Redundant Power System thermal failure can also be caused by a fan failure in the Redundant Power Supply.
C5RSP Error Messages
Cisco Catalyst 5000 platform error messages
Error Message%C5RSP-6-BRIDGE_AFU : vlan [dec] could/could not be configured for bridging
Explanation A virtual LAN (VLAN) could not be reset with the proper bridging information.
Recommended Action To remedy the problem, configure the VLAN with or without bridging.
Error Message%C5RSP-3-C5_BADIPC : bad message received from the NMP
Explanation An unsolicited in-band IPC message was received by the router from the Network Management Processor (NMP).
Recommended Action No action is required.
Error Message%C5RSP-3-C5IP_SLOTFAIL : can't get Catalyst 5000 Slot number of router
Explanation An attempt by the RSP to query the C5IP for the lot it is plugged into has failed.
Recommended Action To remedy the problem, reset the router from the Network Management Processor's (NMP) console. If the problem persists, contact Cisco for replacement.
Error Message%C5RSP-3-C5_MACADRFAIL : can't get C5 Line Card Mac Addr
Explanation An attempt by the RSP to query the C5IP for Vlan 0 IP address failed.
Recommended Action To remedy the problem, reset the router from the Network Management Processor's (NMP) console. If the problems persist, contact Cisco for replacement.
Error Message%C5RSP-3-C5_NMPMACADRFAIL : can't get NMP Mac Addr
Explanation An attempt by the RSP to query the C5IP for Vlan 0 MAC address failed.
Recommended Action To remedy the problem, reset the router from the Network Management Processor's (NMP) console. If the problems persist, contact Cisco for replacement.
Error Message%C5RSP-3-C5_SAGE0FAIL : Length error occurred on dma channel 0
Explanation A hardware error has occurred on DMA channel 0.
Recommended Action Report this error to your technical support representative.
Error Message%C5RSP-3-C5_SAGE1FAIL : Length error occurred on dma channel 1
Explanation A hardware error has occurred on DMA channel 1.
Recommended Action Report this error to your technical support representative.
Error Message%C5RSP-3-CANT_CREATE_VLAN : vlan [dec] cannot be created. media not supported
Explanation An attempt to create a virtual LAN (VLAN) of a media that is not supported has failed.
Recommended Action To remedy the problem, configure the VLAN with a different media type.
Error Message%C5RSP-3-INVALID_LOVE_LETTER : Invalid loveletter type, [dec], sent by c5ip
Explanation Cisco IOS is receiving bogus messages from the C5IP.
Recommended Action No action is required. If problems persists, contact your Cisco technical support representative.
Error Message%C5RSP-3-MAXVLAN_EXCEEDED : can't configure more than 256 VLANS
Explanation The Vlan Router product can configure a maximum of 256 virtual LANs.
Recommended Action To remedy the problem, delete unused VLANs before configuring new ones.
Error Message%C5RSP-3-NMP_DELETE_VLAN : having problems deleting vlan [dec] on the NMP
Explanation An in-band IPC message to the Network Management Processor (NMP) from the router to delete a virtual LAN (VLAN) has failed.
Recommended Action To remedy the problem, check the state of VLAN 0, check the state of the C5IP via the front-panel LED, and check the state of the NMP. Reset the router.
Error Message%C5RSP-3-NMP_INIT_FAIL : can't talk to NMP during initialization
Explanation An in-band IPC router initialization message to the Network Management Processor (NMP) has failed.
Recommended Action To remedy the problem, check the state of VLAN 0, check the state of the C5IP via the front-panel LED, and check the state of the NMP. Reset the router.
Error Message%C5RSP-3-NMP_PROG_FAIL : NMP won't allow vlan [dec] configuration
Explanation An in-band IPC message to the Network Management Processor (NMP) from the router to create a virtual LAN (VLAN) has failed.
Recommended Action To remedy the problem, check the state of VLAN 0, check the state of the C5IP via the front-panel LED, and check the state of the NMP. Reset the router.
Error Message%C5RSP-6-NOSWIDB : vlan [dec] missing IDB
Explanation Internal data structure of the virtual LAN (VLAN) is missing.
Recommended Action Contact your Cisco technical support representative.
Error Message%C5RSP-3-UNKNOWN_NMP_PROG : unknown timer for NMP programming
Explanation An unknown timer event has expired.
Recommended Action No action is required.
Error Message%C5RSP-6-VLAN_INFO_MISSING : vlan [dec] info errant. something very wrong
Explanation Internal information about the virtual LAN (VLAN) is missing.
Recommended Action Contact your Cisco technical support representative.
CBUS Error Messages
CiscoBus controller error messages
Error Message%CBUS-3-ADDRFILTR : Interface [chars], address filter [chars] command failed, code [hex]
Explanation The specified address filter command sent to the specified interface failed with the displayed error code.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CBUS-3-AIPINVPLIM : Interface [chars], Invalid PLIM detected. Interface downed
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CBUS-4-BADENCAPSZ : [chars]: CIP encapsulated msg size ([dec]) exceeds max ([dec] truncated
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 on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CBUS-3-BADVC : [chars] [dec]/[dec] got bad VC packet [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex]
Explanation An interface received a packet with bad VC encapsulation. This indicates either a software or hardware problem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%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 on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CBUS-3-CATMCFG : Interface [chars], Cannot config interface, CBus ATM MEM 0x[hex], status [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%CBUS-3-CATMREJCMD : [chars] [chars] command failed (error code 0x[hex])
Explanation The ciscoBus ATM 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 on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CBUS-3-CATMRSET : Interface [chars], Error ([hex]) [chars] - aip_reset()
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CBUS-3-CATMRSETU : Unit [dec], Error ([hex]) [chars] - cbus_atm_reset()
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CBUS-3-CBUSBCE : Failed to select a BCE, response 0x[hex] - cbus_bce_update_ifa()
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CBUS-3-CBUSBCEPERM : Failed to select a BCE, response 0x[hex] - cbus_bce_permissions_update()
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CBUS-3-CCBCMDFAIL0 : Controller [dec], cmd ([dec]) failed (0x[hex])
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. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CBUS-3-CCBCMDFAIL1 : Controller [dec], cmd ([dec] 0x[hex]) failed (0x[hex])
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. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CBUS-3-CFGCMDDROPPED : Config queue is full, command was dropped, slot [dec]
Explanation Sending a configuration command was retried. The receiving queues were still full after retries therefore the command was dropped.
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 removing the CIP and reinstalling it.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CBUS-4-CIPCFGFAIL : [chars]: configuration command [chars] [chars] failed
Explanation A configuration command sent to the CIP after a reset failed to complete successfully.
Recommended Action Reissue the configuration command.
Error Message%CBUS-4-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-CIPENABLE : [chars]: No pre-allocated buffers available; enable not sent
Explanation An attempt to get a pre-allocated buffer for the CIP enable command was unsuccessful. This CIP interface will not be enabled.
Recommended Action Reload the router to get the CIP interface enabled again. Report this error to your technical support representative.
Error Message%CBUS-2-CIPENCAP : [chars]: No elements available for message ([hex] [hex] resetting interface
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 on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CBUS-4-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 Reissue the configuration command.
Error Message%CBUS-3-CIPRSET : Interface [chars], Error ([hex]) [chars] - cip_reset()
Explanation The CIP did not respond to a reset request from the Route Processor (RP).
Recommended Action Try each of the following fixes in sequence. If a fix corrects the problem, the remaining tasks do not need to be performed.
•
•
•
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-CORRUPT : Controller [dec], wrote 0x[hex], read 0x[hex], loc 0x[hex] - dci_memtest()
Explanation A hardware component failed an internal diagnostic test.
Recommended Action Replace the malfunctioning device.
Error Message%CBUS-3-CT3DSX3ERR : ([chars])Illegal dsx3 value - unit is [dec]
Explanation Internal data structure is corrupted, which causes the love letter to drop.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CBUS-3-CTRACHECK : 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 the message recurs, copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%CBUS-3-CTRBADLOVE1 : Interface [chars], SRB_COMPLETE lovenote received with unknown command (0x[hex])
Explanation The system received a message from the Token Ring interface but does not recognize the message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CBUS-3-CTRBADLOVE1_DUMP : Dump of MEMB follows-SRB_ADDR: [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex]
Explanation The system is printing codes related to a previous love note error message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CBUS-4-CTRBADLOVE2 : Interface [chars], Unexpected SRB_COMPLETE lovenote, command=0x[hex], result=0x[hex]
Explanation The system received an unsolicited message from the Token Ring interface. The system ignored the message and continued normal processing.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%CBUS-3-CTRCMDFAILED : Interface [chars], CTR Command [chars] Failed, [chars] ([hex])
Explanation A command sent from the system to the Token Ring interface failed to complete successfully.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CBUS-3-CTRCMDFAILED2 : Interface [chars], CTR Command [chars] Failed, Code [hex]
Explanation A command sent from the system to the Token Ring interface failed to complete successfully.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CBUS-3-CTRINIT : Interface [chars], CTR Initialization Failed - [chars]
Explanation The Token Ring interface failed one of its internal self-tests.
Recommended Action Issue a clear interface command. If the message recurs, copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%CBUS-3-CTRLRCMDFAIL0 : Controller [dec], cmd ([dec]) failed (0x[hex]) 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. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CBUS-3-CTRLRCMDFAIL1 : Controller [dec], cmd ([dec] 0x[hex]) failed (0x[hex]) 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. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CBUS-3-CTRRAMTEST : Interface [chars], RAM Addressing Test Failed - [chars]
Explanation The Token Ring interface failed its memory diagnostic tests.
Recommended Action Issue a clear interface command. If the message recurs, copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%CBUS-3-CTRRSET : Interface [chars] failed to initialize
Explanation The Token Ring interface failed to insert into the Token Ring. The interface is placed into reset state and will not automatically try to re-insert itself.
Recommended Action Issue a clear interface command. If the message recurs, copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%CBUS-3-CTRUCHECK : Interface [chars], Microcode Check Error
Explanation The Token Ring interface microcode detected an unrecoverable error.
Recommended Action Issue a clear interface command. If the message recurs, copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%CBUS-3-DAUGHTER : Unit [dec], daughter controller [dec] failed [chars] test - interface disabled
Explanation 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 a slot number in the Cisco 7000.
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 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 memory device tests failed. The daughter card must be able to write to some memory device 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 (0x[hex]) - disabled
Explanation 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, 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, ensure that the daughter card is properly seated in its Multibus and ciscoBus connectors. If the message recurs, call your technical support representative.
Error Message%CBUS-3-FCICMDFAIL0 : Controller [dec], cmd ([dec]) failed (0x[hex]) 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. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CBUS-3-FCICMDFAIL1 : Controller [dec], cmd ([dec] 0x[hex]) failed (0x[hex]) 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. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CBUS-5-FDDICMD : '[chars]' is not supported on [chars]
Explanation This command is not supported on this FDDI interface.
Recommended Action No action is required.
Error Message%CBUS-3-FDDIRSET : Interface [chars], Error ([hex]) [chars] - fddi_reset()
Explanation A hardware device did not respond appropriately to a request.
Recommended Action Ensure that the device is functioning and is configured correctly.
Error Message%CBUS-3-FDDIRSETU : Unit [dec], Error ([hex]) [chars] - fddi_reset()
Explanation A hardware device did not respond appropriately to a request.
Recommended Action Ensure that 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-HSSIRSET : Interface [chars], 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 on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CBUS-3-INITERR : Interface [dec], Error ([hex]), idb [hex] [dec] [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 Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CBUS-3-INTR : Interface [dec], idb [hex] [dec] [chars] - cbus_interrupt()
Explanation The switch processor or ciscoBus controller returned a nonsensical value.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CBUS-4-NOCOOKIE : [chars]-[dec] controller missing configuration data - disabled
Explanation The controller type was derived from a hardware probe. The controller number indicates the ciscoBus relative slot number. This is a hardware error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CBUS-3-OUTHUNG : [chars]: tx[char] output hung ([hex] - [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-3-POLLFAIL : Interface [chars] failed to respond, debug info follows
Explanation A Token Ring interface card failed to respond to periodic polling. This can indicate a software or hardware problem. See CBUS-3-POLLFAILDAT for the syntax of this message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%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 This is a debug message only. No action is required.
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 No action is required.
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.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CBUS-3-SERRSET : Interface [chars], Error ([hex]) [chars] - serial_reset()
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CBUS-3-TESTFAIL : Unit [dec], failed [chars] test - interface disabled
Explanation 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 Ensure that the device is functioning and is configured correctly.
Error Message%CBUS-3-UNKENC : Interface [chars], unknown encaps type [hex]
Explanation 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 on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
CDM Error Messages
Cable Data Modem subsystem error messages
Error Message%CDM-3-CONFIG : Interface [chars] must be ACIP to run cable application
Explanation The named interface is not an ATM Cable Interface Processor (ACIP) interface.
Recommended Action An ACIP is required to run the cable data modem (CDM) application. Check than an ACIP is installed in the system.
Error Message%CDM-3-INIT : ACIP required to run this Cisco IOS image
Explanation No ATM Cable Interface Processor (ACIP) is installed in the system.
Recommended Action An ACIP is required to run the cable data modem (CDM) application. Install ACIP.
CI Error Messages
Chassis Interface (CI) (Cisco 75xx platform environmental monitor card) error messages
Error Message%CI-3-BLOWER : [chars] fan failure
Explanation 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] seconds
Explanation One of the six blowers in a five-slot chassis has failed. Because 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 2 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 [int] differs from NVRAM type [int]
Explanation The chassis type as reported by the CI is different from that programmed into nonvolatile RAM (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 [int] recent soft power shutdowns (or system just powered-on)
Explanation A soft shutdown occurs when the router powers itself down because of a detected over-temperature condition. When the temperature goes up past the board shutdown trip point, the cards are shut down, but the power supplies, fans, and CI continue to run.
When the system cools past the restart trip point, the system will restart. The system counts the number of times this happens to keep the up/down cycle from repeating indefinitely. If the counter reaches zero, the system undergoes a hard shutdown, which requires a power cycle to recover. The soft shutdown counter is reset to its maximum value after the system has been up for six hours.
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-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-4-NOTFOUND : Chassis Interface not found
Explanation 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 [int] 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 [int] failure
Explanation 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 [chars] 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.
CIRRUS_PM Error Messages
Slow-speed asynchronous/synchronous port module error messages
Error Message%CIRRUS_PM-3-BADLOOPCABLE : Loopback not supported for DTE/X.21 port [dec] in slot [dec]
Explanation The DTE/X.21 cable does not support loopback.
Recommended Action Use proper cable for loopback testing.
Error Message%CIRRUS_PM-3-DISCOVER : CIRRUS PM at slot [dec]: PCI discovery failed
Explanation The software failed to initialize the network module.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CIRRUS_PM-2-NOBUFPOOL_ASYNC : Unable to create buffer pool for async mode interface
Explanation There is not enough memory for a per-channel control block of the CD2430 asynchronous driver.
Recommended Action Ensure that sufficient memory is available in the router. If the message recurs, copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CIRRUS_PM-3-NOTCD2430 : Device reported [hex]
Explanation The network module hardware reports that a non-low-speed port module was detected.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CIRRUS_PM-3-UNKNOWNPLATFORM : Unknown Platform type to support CD2430 interfaces
Explanation The network module is not compatible with the current platform into which it is being plugged.
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 The counters have been cleared on the interface(s).
Recommended Action No action is required.
CLNS Error Messages
OSI Connectionless Network Service error messages
Error Message%CLNS-5-ADJCHANGE : [chars]: Adjacency to [chars] ([chars]) [chars], [chars]
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 appears only if the log-adjacency-changes command is configured for the ISIS or NLSP process.
Recommended Action This informational message normally appears as routers and links go up or down. However, unexpected adjacency loss might 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 their configured area addresses into a single set. If the resulting set includes 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-3-BADIFNUM : ISIS: Bad if number, pdb [hex], idb [hex], if [hex]
Explanation An internal error occurred in the Intermediate System-to-Intermediate System (ISIS) or NetWare Link Services Protocol (NLSP). An inconsistency was detected in an internal data structure related to tracking protocol/interface state, possibly related to enable/disable of the protocol on an interface.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CLNS-3-BADPACKET : [chars]: [chars], [chars][chars] from [chars] ([chars])
Explanation An invalid packet was received from a neighboring router.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco 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 on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%CLNS-3-CKSUMERR : [chars]: L[dec] LSP [chars] database checksum error, restarting
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%CLNS-4-DUPSYSTEM : [chars]: possible duplicate system ID [chars] detected
Explanation This is a configuration error.
Recommended Action One of the duplicate IDs must be corrected.
Error Message%CLNS-4-EDATFAIL : Encapsulation failed, dst= [chars]
Explanation This 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 on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%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 on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%CLNS-4-LSPCKSUM : [chars]: Bad L[dec] LSP [chars] checksum [hex] received on [chars], length [dec], should be [hex], bad count [dec]
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 passed the data-link 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 message usually indicates data corruption occurring on a link, but might also indicate data corruption in a neighboring router's memory.
Recommended Action If the error is in a neighboring router's memory, the problem will correct itself within 15 minutes. 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. The same LSP ID might appear in this message on other routers as well. If data-link corruption has caused the error, check the link for errors and deal with them 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 on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CLNS-3-LSPFULL : [chars]: L[dec] LSP filled to capacity, dropping routes
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco 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 on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%CLNS-3-LSPIXARRNULL : [chars]: LSPix entry [dec] should be null, is [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 on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%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 on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%CLNS-3-LSPTOOBIG : [chars]: L[dec] LSP [chars] size [dec] bigger than interface [chars] MTU [dec], LSP dropped
Explanation A software or hardware error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%CLNS-5-MULTICAST : [chars]: [chars]cast address in use on [chars]
Explanation A NetWare Link Services Protocol (NLSP) adjacency with a neighboring router has either come up or gone down. The message describes whether the NLSP multicast address is in use for future updates sent on the LAN. This message appears only if the log-adjacency-changes command is configured for the NLSP process.
Recommended Action This message is primarily informational and appears normally as routers and links go up or down. No action is required.
Error Message%CLNS-3-NSAPES : Invalid NSAP type in ES table: [hex] for [chars]
Explanation An internal software error occurred.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%CLNS-4-NSAPIS : Invalid NSAP type in IS table: [hex] [dec]
Explanation An internal software error occurred.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%CLNS-3-ONLIST : ISIS: 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 on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%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, copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%CLNS-3-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 on the console or in the system log, and report it to your Cisco 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 on the console or in the system log, and report it to your Cisco technical support representative.
CLSDR Error Messages
Cisco Link Services driver error messages
Error Message%CLSDR-3-ERRRTN : [chars] failed error 0x[hex]
Explanation An error was returned from Cisco Link Services I (CLSI) to the destination logical unit (DLU) because CLSI did not perform the action desired by the DLU.
Recommended Action Refer to CLSI software documentation for more information about this error. Report this error to your technical support representative.
Error Message%CLSDR-3-INCORRECTPORT : Incorrect port pointer in USapId
Explanation Cisco Link Services I (CLSI) returned an incorrect port pointer in the USapID.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%CLSDR-3-MSGERR : [chars] couldn't get a message
Explanation 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 Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%CLSDR-3-NOCEP : Cannot found cep in free pool
Explanation A software or hardware error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%CLSDR-3-NOCLSSERVER : unable to start the Server process
Explanation The CLSDRIVER process could not be started, possibly because of 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 to reboot the system. Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco 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 Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%CLSDR-3-NOINIT : CLSDRIVER not initialized
Explanation 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. Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%CLSDR-3-NOPORTCREATE : Cannot create PORT structure
Explanation The CLSDRIVER cannot enable this port for processing.
Recommended Action Try rebooting the router. Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%CLSDR-3-NOREMOVECEP : RemoveCep : Cep 0x[hex] not on list
Explanation 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 Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%CLSDR-3-NOREMOVEPORT : RemovePort: port 0x[hex] not on list
Explanation 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 Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%CLSDR-3-WRONGMSG : Should never be here, cls message type unknown 0x[hex]
Explanation The CLS message type is unknown to the destination logical unit (DLU).
Recommended Action Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
COMP Error Messages
Compression error messages
Error Message%COMP-3-BADCOMP : Interface [chars] Bad status returned from packet compression operation
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%COMP-3-BADCRC : Interface [chars] Decompression check-byte data is incorrect
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%COMP-3-BADSEQNUM : Interface [chars] Unexpected compressed packet sequence number
Explanation Perhaps a packet drop or transient line error has occurred.
Recommended Action This problem should self-correct.
Error Message%COMP-3-CONFIGBAD : Interface [chars] Compression internal configuration error
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%COMP-3-DESTEXST : Interface [chars] Destination decompression buffer ran out of space
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%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-NOEND : Interface [chars] No end-bit detected on compressed packet
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%COMP-3-SIZEBAD : Interface [chars] Decompression size error
Explanation One interface is configured for predictor compression; the other is not.
Recommended Action Configure both interfaces for predictor compression.
Error Message%COMP-3-SRCREMAINS : Interface [chars] Not all packet data was used by decompressor
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%COMP-3-SYNCBAD : Interface [chars] Decompression sync error
Explanation One interface is configured for predictor compression; the other is not.
Recommended Action Configure both interfaces for predictor compression.
Error Message%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 down
Explanation A controller stopped responding to commands over the ciscoBus, so the controller was put into shutdown mode.
Recommended Action Re-enable the controllers by issuing the no shut command on all controllers on the card, or hotswap out the bad card and install the new one. You must still manually issue the no shut command to 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 on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CONTROLLER-5-LOOPSTATUS : Controller [chars], [chars]
Explanation This message indicates a configurable controller loopback status.
Recommended Action No action is required.
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 on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CONTROLLER-5-REMLOOP : Controller [chars], remote loop [chars] [chars]
Explanation A configurable controller entered remote loopback.
Recommended Action No action is required.
Error Message%CONTROLLER-5-UPDOWN : Controller [chars], changed state to [chars]
Explanation A configurable controller changed its state.
Recommended Action No action is required.
CPAD Error Messages
Compression service adapter error messages
Error Message%CPAD-1-ERROR : [chars]: [chars]
Explanation An error occurred in the application using the compression service adapter (CSA).
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CPAD-1-INITFAIL : bay [dec]: [chars]
Explanation The compression service adapter (CSA) driver failed to initialize at the specified point.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CPAD-1-NOMEMORY : bay [dec]: out of memory: could not allocate [chars]
Explanation The compression service adapter (CSA) driver, in its initialization phase, could not allocate memory for the specified data structure.
Recommended Action Consider adding more shared memory. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CPAD-1-PLXINIT : bay [dec] Invalid vendor/device id [dec]
Explanation The compression service adapter (CSA) driver, in its initialization phase, encountered a communication failure with the CSA in the specified bay.
Recommended Action Consider reseating the specified CSA. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CPAD-6-SHUTDOWN : [chars] shutting down
Explanation The specified compression service adapter (CSA) is shutting down. It may have been physically removed.
Recommended Action This is an informational message only and occurs in normal operation. No action is required.
Error Message%CPAD-6-STARTUP : [chars] starting up
Explanation The specified compression service adapter (CSA) has initialized successfully.
Recommended Action This is an informational message only and occurs in normal operation. No action is required.
CPM Error Messages
Combo Port Module device driver error messages
Error Message%CPM-3-DISCOVER : CPM at slot [dec]: PCI discovery failed count = [dec]
Explanation One of the interface controller devices on the module did not initialize properly.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CPM-3-INCORRECT_ID : CPM at slot [dec]: PCI device not supported
Explanation An interface controller device did not report the correct protocol control information (PCI) device ID.
Recommended Action Power down, reinsert the port module, and reboot. If the message recurs, call your technical support representative for assistance.
CSC2 Error Message
CPU card error message
Error Message%CSC2-4-BREAK : AUX port hung because 'Transmit Break' would not clear
Explanation The Universal Asynchronous Receiver/Transmitter (UART) in the console serial interface is malfunctioning.
Recommended Action Service the console serial port hardware.
CT3 Error Messages
Channelized T3 port adapter error messages
Error Message%CT3-3-BADMSG : Received unexpected mailbox message (id = [dec])
Explanation Unexpected message was received from CT3 firmware.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CT3-1-CONFIGURE : CT3: Fail to configure [dec] interfaces on bay [dec], shutting down bay
Explanation The CT3 hardware failed. Some components on the board failed to initialize.
Recommended Action Replace the CT3 port adapter.
Error Message%CT3-2-CT3FWCRASHED : CT3 F/W crashed: [hex] - VIP reset
Explanation CT3 firmware does not update the software watchdog.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CT3-3-CT3NOACC : [chars] - Accumulator is not available
Explanation An invalid TX accumulator is detected.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CT3-1-DISCOVER : CT3: only found [dec] interfaces on bay [dec], shutting down bay
Explanation The CT3 hardware failed. Some components on the board failed to initialize.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CT3-1-DWNLDFL : PA down load failed
Explanation Failed to download firmware into the CT3 port adapter.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CT3-3-ERROR : [chars]
Explanation This is a general error information.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CT3-1-INITFAIL : Bay [dec]: Init failed at [chars]
Explanation This message indicates a CT3 firmware initialization failure.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CT3-1-INITFAILP : [chars]: Init failed at [chars]
Explanation This message indicates a CT3 initialization failure.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CT3-3-LOVEFAIL : [chars]: failed to send [chars] love letter
Explanation A love letter was not sent to the RSP.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CT3-3-MBOXRECV : Bay [dec]: fail receiving mbox reply [dec]
Explanation A message was not received from CT3 firmware.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CT3-3-MBOXRECVP : Bay [dec]: fail receiving mbox reply [dec] for port [dec]
Explanation A message to configure the port was not received from CT3 firmware.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CT3-3-MBOXSEND : Bay [dec]: fail sending mbox msg [dec]
Explanation A message was not sent to CT3 firmware.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CT3-3-MBOXSENDP : Bay [dec]: fail sending mbox msg [dec] for port [dec]
Explanation A port related message was not sent from CT3 firmware.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CT3-3-NOTMXT : Device is not MX - Device reported [hex]
Explanation This message indicates a failure to detect the HDLC controller on the CT3.
Recommended Action Replace the CT3 port adapter.
Error Message%CT3-3-NOTPLX : Device is not PLX 9060 - Device reported [hex]
Explanation The PLX 9060 was not detected on the CT3.
Recommended Action Replace the CT3 port adapter.
Error Message%CT3-1-NOTREADY : Not ready for download
Explanation An error was detected on the communication path between VIP and CT3.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CT3-2-NOVC : [chars]: packet received for non-exist VC [dec]
Explanation The virtual channel encapsulation is corrupted.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CT3-3-OWNERR : CT3 serial ([dec]), Buffer ownership error, pak=0x[hex]
Explanation A software or hardware error occurred. The CT3 driver detected that the transmit ring is in 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%CT3-1-RESTARTFAIL : [chars]: Start failed at [chars]
Explanation The restart failed to reset the interface.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CT3-1-STARTFAIL : [chars]: Start failed at [chars]
Explanation The restart failed to enable the interface.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%CT3-1-STOPFAIL : [chars]: Stop failed at [chars]
Explanation The shutdown failed to disable the interface.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.