|
|
This appendix documents all system error messages, as of software release 8.3, for the router, terminal server, and protocol translator products. These are the error messages which the system software sends to the console (and, optionally, to a logging server on another system) during operation.
Not all of these messages indicate problems with your system. Some are purely informational, while others may help to diagnose problems with communications lines, internal hardware, or the system software.
All messages begin with a percent sign, and are displayed in the following format:
%FACILITY-SEVERITY-MNEMONIC: Message-text
FACILITY is a code, consisting of two to five uppercase letters, indicating the facility to which the message refers. A facility may be a hardware device, a protocol, or a module of the system software. Table A-1 lists the codes for all of the system facilities.
SEVERITY is a single-digit code from 0 to 7 which reflects the severity of the condition. The lower the number, the more serious the situation. Table A-2 lists the severity levels.
MNEMONIC is a code, consisting of uppercase letters, that uniquely identifies the message.
Message-text is a text string describing the condition. This portion of the message sometimes contains detailed information about the event being reported, including terminal port numbers, network addresses, or addresses that correspond to locations in the system's memory address space. Because the information in these variable fields changes from message to message, it is represented here by short strings enclosed in square brackets ([ ]). For example, a decimal number is represented as [dec]. A complete list of the kinds of variable fields, and the information contained in them, appears in Table A-3 .
If one or more error messages recur after you take the recommended action, contact Cisco or contact your local field service organization.
Use the following tables to interpret the facility codes that begin each message, the severity level numbers associated with each message, and the variables fields contained in some of the messages.
Code Facility
AT AppleTalk
BGP Border Gateway Protocol
CBUS The cBus controller
CHAOS CHAOSnet
CLNS OSI Connectionless Network Services
CSC2 CSC2/CSC3 CPU card
DNET DECnet
EGP Exterior Gateway Protocol
HELLO HELLO Protocol
HSSI High Speed Serial Interface Card
IGRP Interior Gateway Routing Protocol
ILAN Interlan Ethernet controller
IMP Interface Message Processor
IP Internet Protocol
IPRT IP Routing
LANCE STS-10x or IGS Ethernet Interface
LAPB X.25 Link Access Protocol - Binary
LAT DEC LAT (Local Area Transport)
LINK Data Link
MAILBOX Chipcom Mailbox Support
MCI Multiport Communications Interface
MK5 MK5025 serial controller
PAD X.25 Packet Assembler/Disassembler
PPP Point-to-Point Protocol
PR Parallel Printer devices
PUP Xerox PARC Universal Packet protocol
RIP BSD IP Routing Information Protocol
RSRB Remote Source Routing Bridge
SBE SBE serial interface
SEC IP Security
SLIP Serial Link IP
SRB Source Routing Bridge
STUN Serial Tunneling
SYS Operating system
TAC Terminal Access Control protocol
TCP Transmission Control Protocol
TMQ Inbound Terminal Port Queuing
TN Telnet
TR Token Ring
ULTRA Ultranet card
VINES Banyan VINES
X25 X.25
XNS Xerox Network Services
Number Explanation
0 System is unusable.
1 Action must be taken immediately.
2 Critical condition.
3 Functionality may be affected.
4 Warning condition.
5 Normal but significant condition.
6 Informational message.
7 Appears during debugging only.
Representation Type of Information
[dec] Decimal number
[hex] Hexadecimal number
[char] Single character
[chars] Character string
[enet] Ethernet address (for example, 0000.DEAD.00C0)
[inet] Internet address (for example, 12.128.2.16)
[t-line] terminal line number in octal (or decimal if the decimal-tty
service is enabled)
Some error messages which describe internal errors contain traceback information. This information is very important and should be included when you report a problem to Cisco Systems.
The following sample error message includes traceback information.
-Process= "Exec", level= 0, pid= 17
-Traceback= 1A82 1AB4 6378 A072 1054 1860
Explanation:
The initial hint address was in use. A search will be made for a valid address.
Recommended Action:
No action required.
Error Message: %AT-6-ADDRUSED [chars]: using AppleTalk address [network].[node]Explanation:
No hint address or a bad hint address was specified. This message indicates the AppleTalk address that will be used.
Recommended Action:
No action required.
Error Message: %AT-6-AQUIREMODE [chars]: AppleTalk querying network for configurationError Message: %AT-5-BADNEIGHBOR: [chars]:AppleTalk neighbor (advertising [chars]) is misconfigured, ignored
Explanation:
A neighboring router's AppleTalk configuration does not agree with this router's AppleTalk configuration. This can be due to the neighbor's network range not matching this router's network range.
Recommended Action:
Modify this router or the neighboring router's configuration so that the network ranges agree.
Error Message: %AT-6-BADROUTE AppleTalk route to net [chars] has been marked badExplanation:
The system has not heard about a route within the required time-out period. The route has therefore been marked as bad. This may mean that a network has become unreachable for some reason--perhaps a broken connection. This message does not necessarily reflect an error condition.
Error Message: %AT-5-COMPATERR1: [chars]: Neighbor at [chars] only supports AppleTalk internets in compatibility mode
Explanation:
A neighboring router only supports extended AppleTalk networks with a cable range of 1, example: 25-25.
Recommended Action:
Configure the interface via which the Cisco router communicates with the neighboring router to have a cable range of one.
Error Message: %AT-5-COMPATERR2: Zones for net [chars] are incompatible with some AppleTalk routers in internetExplanation:
One or more seed routers in the AppleTalk network have zone lists which are missing some zone names.
Recommended Action:
Be sure that all seed routers in an AppleTalk network are configured with identical zone lists.
Error Message: %AT-5-COMPATERR3: Cable range [chars] is incompatible with some AppleTalk routers in internetExplanation:
One or more routers in the AppleTalk network has a cable range configuration which is not the same as the cable range configuration on this router.
Recommended Action:
It will be necessary to properly configure all routers to have identical cable ranges for a common cable.
Error Message: %AT-6-CONFIGOK [chars]: AppleTalk configuration verified by [dec].[dec], port activatedExplanation:
The AppleTalk configuration was verified by consulting the indicated router.
Recommended Action:
No action required.
Error Message: %AT-5-DUPADDR: [chars]: Our AppleTalk node address used by [enet], restarting line protocolExplanation:
Another AppleTalk node on a common network interface has claimed the same AppleTalk address which this router was already using.
Recommended Action:
None. This Cisco router will restart AppleTalk processing on the common network interface to resolve the address conflict.
Error Message: %AT-3-IFCONFLICT: [chars]: Configuration conflicts with port [chars] (interface [chars])Explanation:
An attempt was made to configure an interface to have the same 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]: Interface cleared, AppleTalk port reinitializingExplanation:
This message is generated by performing the EXEC command clear interface with the interface type on an interface currently routing AppleTalk.
Recommended Action:
None. This message is for informational purpose.
Error Message: %AT-5-INTDOWN [chars]: AppleTalk port disabled, Line protocol went downExplanation:
An AppleTalk hardware interface has been disabled due to a bad serial line, a configuration command, or a bad interface.
Recommended Action:
If the port has not been intentionally disabled, this message may reflect a hardware problem. If so, service the hardware.
Error Message: %AT-6-INTUP [chars]: AppleTalk port reinitializing, Line protocol came upExplanation:
An AppleTalk port that was previously shut down has been restarted.
Error Message: %AT-6-LOSTNEIGHBOR AppleTalk neighbor at [network].[node]has been deleted
Explanation:
A peer router has become unreachable.
Error Message: %AT-3-MCMISMATCH [chars]: Netinfo zone multicast address disagrees with us (theirs=[enet], ours=[enet])
Explanation:
A computed multicast address disagrees with that provided by another AppleTalk router. The other AppleTalk router may be misconfigured or faulty.
Recommended Action:
Correct the problem at the other router.
Error Message: %AT-6-NEIGHBORUP: [chars]: AppleTalk neighbor at [chars] has restartedExplanation:
A neighboring router was to which this router previously lost connectivity, has reappeared on the network.
Recommended Action:
None. This is an informational message.
Error Message: %AT-3-NETDISAGREES [chars]: Net range does not match other routers, port disabledExplanation:
The configurations of one or more other AppleTalk routers are inconsistent with the configuration of this router.
Recommended Action:
Reconfigure one or more of the routers.
Error Message: %AT-4-NETINVALID [chars]: Net [chars] is not valid for current AppleTalk internet, port disabledExplanation:
The network range overlaps with that of other networks in the internet.
Recommended Action:
Reconfigure the router.
Error Message: %AT-6-NEWNEIGHBOR AppleTalk neighbor at [network].[node] has been addedExplanation:
The router discovered a new peer AppleTalk router.
Error Message: %AT-6-NEWROUTE AppleTalk net [chars] has been added, [dec]hops, reported by [network].[node]
Explanation:
A new network has come up.
Error Message: %AT-3-NOADDRSAVAIL [chars]: Couldn't assign any AppleTalk address
Explanation:
No free node could be found on the interface.
Recommended Action:
If there are less than 250 nodes on your AppleTalk network, contact Cisco. Otherwise, you must split your AppleTalk network into smaller ones.
Error Message: %AT-6-NODEWRONG: AppleTalk node [chars] is not valid for [chars], sent correct configurationExplanation:
An AppleTalk node has sent a GetNet Info request to this router, specifying an invalid network number for the source of the GetNet Info request.
Recommended Action:
None. This is an information message.
Error Message: %AT-3-NOSRCADDR: [chars]: No AppleTalk node address available to use as packet sourceExplanation:
The interface out which a newly created AppleTalk packet is destined to be sent has no AppleTalk address.
Recommended Action:
Verify that the interface specified in the error message is properly configured.
Error Message: %AT-3-NOTRUNNING AppleTalk not runningExplanation:
You have tried to show or change the AppleTalk configuration, but AppleTalk routing was not turned on.
Recommended Action:
Change the configuration to activate AppleTalk routing.
Error Message: %AT-5-NOTSUPPORTED: [chars]: line protocol does not support this AppleTalk port configurationExplanation:
The interface specified has an encapsulation method which does not support fast switching.
Recommended Action:
This is an informational message. No action required.
Error Message: %AT-5-OLDMCI: [chars]: AppleTalk route cache disabled, MCI firmware is obsoleteExplanation:
The firmware on the MCI controller card does not support fast switching of AppleTalk.
Recommended Action:
Verify that the MCI controller firmware for the interface specified in the error message is at level 1.7 or higher.
Error Message: %AT-6-ONLYROUTER [chars]: No other AppleTalk router found, port activatedExplanation:
No other AppleTalk routers were found on the network attached to the port.
Error Message: %AT-6-ROUTENOTIFY AppleTalk route to net [chars] reported bad by [dec].[dec]
Explanation:
A router has gone down somewhere on the AppleTalk network. The specified peer notified this router of the change.
Error Message: %AT-6-ROUTEOK: AppleTalk route to net [chars] has been restored
Explanation:
A routing update has been received for a previously suspect route.
Recommended Action:
This message is for informational purposes only.
Error Message: %AT-3-ZONEDISAGREES [chars]: Zone does not match other routers, port disabledExplanation:
The configurations of one or more other routers are inconsistent with the configuration of this router.
Recommended Action:
Reconfigure one of the routers.
Error Message: %AT-6-ZONEGC: AppleTalk zone, [chars], has been discardedExplanation:
The router has purged an unused zone from the zone table.
Recommended Action:
This message is for informational purposes only.
Error Message: %CBUS-3-BUFFER: Controller [dec], Error ([hex]), Buffersize = [dec], Bufferpool = [dec], number [dec]
Explanation:
An internal software error has occurred.
Recommended Action:
Contact Cisco Systems for assistance.
Error Message: %CBUS-3-CORRUPT Controller [dec], wrote 0x[hex], read 0x[hex], loc0x[hex] - dci_memtest() %CBUS-3-DAUGHTER Unit [dec], daughter controller [dec] failed[chars] test - interface disabledError Message: %CBUS-3-FDDIRSET Interface [chars], Error ([hex]) [chars] -fddi_reset() %CBUS-3-FDDIRSETU Unit [dec], Error ([hex]) [chars] - fddi_reset() %CBUS-3-INITERR Interface [dec], Error ([hex]) [chars] - cbus_init() %CBUS-4-INTR Interface [dec], [chars] - cbus_interrupt()
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:
Contact Cisco Systems for assistance.
Error Message: %CBUS-3-HSSIRSETU: Unit [dec], Error ([hex]) [chars] - hssi_reset()Explanation:
A hardware component did not respond to a reset command.
Recommended Action:
Contact Cisco Systems for assistance.
Error Message: %CBUS-3-NOMEMORY No memory for [chars]Error Message: %CBUS-4-OUTHUNG Interface [chars] output hung, restarting cBus[dec] controller - mci_output()
Explanation:
A cBus controller took too long to respond to a command, and was restarted by software.
Recommended Action:
If this message recurs, service the hardware.
Error Message: %CBUS-3-TESTFAIL Unit [dec], failed [chars] test - interface disabledError Message: %CBUS-3-TXALLOC Error ([hex]) tx_allocate - cbus_init()
Error Message: %CBUS-3-ULTRARSET: Interface [chars], Error ([hex]) [chars] - ultra_reset()
Explanation:
A hardware component did not respond to a reset command.
Recommended Action:
Contact Cisco Systems for assistance.
Error Message: %CBUS-3-ULTRARSETU: Unit [dec], Error ([hex]) [chars] - ultra_reset()Explanation:
A hardware component did not respond to a reset command.
Recommended Action:
Contact Cisco Systems for assistance.
Explanation:
This message may occur when an interface is down and there is a static neighbor entry 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 or there is no static neighbor entry for that interface, contact Cisco Systems.
Error Message: %CLNS-3-NSAPES Invalid NSAP type in ES table: [hex] for [chars] %CLNS-4-NSAPIS Invalid NSAP type in IS table: [hex] [dec] %CLNS-4-REDIRECT Redirect found for non-route entry, dst=[chars], next-hop= [chars]
Explanation:
The UART (Universal Asynchronous Receiver/Transmitter) in the console serial interface is malfunctioning.
Recommended Action:
Service the console serial port hardware.
Explanation:
The system is receiving its own DECnet packets. Possible causes:
1) A serial line is looped back
2) Another host with the same DECnet address is already present on the Ethernet
Recommended Action:
Check the serial lines (if present) and the DECnet configuration.
Error Message: %DNET-4-MAPCON Map entry [dec].[dec] conflicts with adjacency to[dec].[dec]Explanation:
Your DECnet configuration is incorrect. A host which is specified as nonlocal is present on your local network.
Recommended Action:
Correct the configuration.
Error Message: %DNET-3-NOMEMORY No memory available for [chars]
Error Message: %EGP-3-TOOBIG Insufficient ([dec]) buffering for update message
Explanation:
An EGP update message was too large to fit into a single buffer.
Recommended Action:
Contact Cisco Systems for assistance.
Explanation:
An internal software error has occurred.
Recommended Action:
Contact Cisco Systems for assistance.
Explanation:
The InterLAN Ethernet controller was unable to reset.
Recommended Action:
Repair or replace the controller.
Explanation:
The Internet Message Processor has received corrupted data. This may be due to cable problems, a hardware problem in the IMP, or a malfunctioning IMP interface.
Recommended Action:
If this message recurs, service the hardware.
Error Message: %IMP-6-GDOWN Interface [chars], PSN going down [chars]Explanation:
The Internet Message Processor has received corrupted data. This may be due to cable problems, a hardware problem in the IMP, or a malfunctioning IMP interface.
Recommended Action:
If this message recurs, service the hardware.
Error Message: %IMP-3-HDHBADMSG Interface [chars], HDH bad message modeExplanation:
The system received bad data from the IMP.
Recommended Action:
If this message recurs, service the IMP and interface hardware.
Error Message: %IMP-3-HDHHIOFF Interface [chars], HDH H/I bit offExplanation:
The IMP origin bit was not set when it should have been.
Recommended Action:
If this message recurs, service the IMP and interface hardware.
Error Message: %IMP-3-LEADERR Interface [chars], PSN leader error, subtype [dec] %IMP-3-LEADFMT Interface [chars], PSN unknown leader format %IMP-3-LEADTYPE Interface [chars], PSN unknown leader type [dec] imperrorExplanation:
The Internet Message Processor has received corrupted data. this may be due to cable problems, a hardware problem in the IMP, or a malfunctioning IMP interface.
Recommended Action:
If this message recurs, service the hardware.
Error Message: %IMP-5-PSNSTATE: Interface [chars], PSN is [chars]Explanation:
The connection has gone up or down, depending upon the message in [chars]
Recommended Action:
Determine why the PSN has changed state and take appropriate action.
Error Message: %IMP-6-RESET Interface [chars], PSN interface reset
Error Message: %IP-3-DESTHOST src=[inet], dst=[inet], NULL desthost
Error Message: %IP-4-DUPADDR Duplicate address [inet] on [chars], sourced by [enet]
Explanation:
Another system is using your IP address.
Recommended Action:
Change the IP address of one of the two systems.
Error Message: %IPRT-3-NOMEMORY No memory available for [chars]
Error Message: %IPRT-4-SAMENET [chars] and [chars] are on the same network or subnet
Explanation:
The system configuration is inconsistent with the structure of the internet.
Recommended Action:
Change the system configuration to reflect the actual network topology.
Explanation:
An Ethernet interface is malfunctioning.
Recommended Action:
Service the hardware.
Error Message: %LANCE-3-BADENCAP Unit [dec], bad encapsulation in idb->enctype= 0x[hex]Error Message: %LANCE-3-BADUNIT Bad unit number [dec]
Error Message: %LANCE-5-COLL Unit [dec], excessive collisions. TDR=[dec]
Explanation:
An Ethernet cable is broken or unterminated, or the transceiver is unplugged.
Recommended Action:
Service the hardware.
Error Message: %LANCE-0-INITFAIL Unit [dec], initialization timeout failure,csr[dec]=0x[hex]Error Message: %LANCE-5-LATECOLL Unit [dec], late collision error
Explanation:
An Ethernet transceiver is malfunctioning, or the Ethernet is overloaded, or the Ethernet cable is too long.
Recommended Action:
Service the hardware.
Error Message: %LANCE-5-LOSTCARR Unit [dec], lost carrier. Transceiver problem?Explanation:
An Ethernet transceiver is unplugged or faulty.
Recommended Action:
Service the hardware.
Error Message: %LANCE-0-MEMERR Unit [dec], memory error, csr0 = 0x[hex]Explanation:
An Ethernet interface detected a hardware problem.
Recommended Action:
Service the hardware.
Error Message: %LANCE-0-NOMEMORY Unit [dec], no memory for [chars]Error Message: %LANCE-3-OWNERR Unit [dec], buffer ownership error
Explanation:
An Ethernet interface is malfunctioning or an internal software error has occurred.
Recommended Action:
Service the hardware or contact Cisco Systems.
Error Message: %LANCE-3-SPURIDON Unit [dec], spurious IDON interruptExplanation:
An Ethernet interface generated a spurious Initialization Done interrupt.
Recommended Action:
Service the hardware.
Error Message: %LANCE-3-SPURINT Unit [dec], spurious interrupt, csr0 = 0x[hex]Explanation:
An Ethernet interface detected a spurious interrupt.
Recommended Action:
Service the hardware.
Error Message: %LANCE-3-UNDERFLO Unit [dec], underflow errorExplanation:
The Ethernet hardware is requesting data faster than the system can supply it. This should never happen unless a serious malfunction has occurred.
Recommended Action:
Contact Cisco Systems.
Explanation:
A bad X.25 packet was received.
Recommended Action:
If this message recurs, check the X.25 serial line and the devices attached to that line.
Error Message: %LAPB-4-FRAMEERR Interface [chars], Frame error: CF 0x[hex], VS[dec] [char] VR [dec], Reason 0x[hex]Explanation:
A FRMR packet was received. This may be due to a noisy serial line, an overloaded X.25 packet switch, or corrupted data.
Recommended Action:
If this message recurs, service the serial line and other devices attached to that line.
Error Message: %LAPB-4-INFOBAD Interface [chars], Info field not permitted %LAPB-4-INVNR Interface [chars], Invalid NR value %LAPB-4-N1TOOBIG Interface [chars], N1 too largebadx25pktExplanation:
A bad X.25 packet was received.
Recommended Action:
If this message recurs, check the X.25 serial line and the devices attached to that line.
Error Message: %LAPB-3-NOINPIDB Input idb not setError Message: %LAPB-3-NULLPAK Interface [chars], NULL packet ptr, rvr [dec],vs [dec], vr [dec]
Error Message: %LAPB-6-OUTPUT Interface [chars], LAPB O [chars] [chars]
Explanation:
An FRMR packet was discarded due to congestion.
Recommended Action:
If this message recurs, contact Cisco Systems.
Error Message: %LAT-3-ETHERNET No Ethernet to run LAT over
Explanation:
The LAT facility cannot be used unless the system is connected to and active on an Ethernet.
Recommended Action:
Make sure your system is configured correctly, and that the Ethernet interface, if present, is operational.
Error Message: %LAT-3-ETHERNET Tty[t-line], Output data ptrs out of sync with byte count %LAT-3-NULLIDB: Null IDB pointer with destination [enet] %LAT-3-QBSPACED Queue block at [hex] not found for HI connection %LAT-3-REUSE Tty[t-line], Attempt to re-use slot array, empty =[dec], fill = [dec] %LAT-3-SIGERR Tty[t-line], Unknown signal [dec] in [chars]
Error Message: %LINK-5-CHANGED Interface [chars], changed state to [chars]
Error Message: %LINK-2-NOSOURCE Source idb not set %LINK-3-TOOBIG Interface [chars], Output packet size of [dec] bytes too big %LINK-2-UENCAP Unknown line encapsulation code [dec]
Explanation:
A hardware problem was detected in a Chipcom interface board.
Recommended Action:
If this message recurs, contact Cisco Systems for assistance.
Error Message: %MAILBOX-3-FLAGSTAT: Timeout while waiting for FLAGSTAT, status=0x[hex]Explanation:
A hardware problem was detected in a Chipcom interface board.
Recommended Action:
If this message recurs, contact Cisco Systems for assistance.
Error Message: %MAILBOX-3-INITPC2: Timeout waiting for PC2 during initialization, status=0x[hex]Explanation:
A hardware problem was detected in a Chipcom interface board.
Recommended Action:
If this message recurs, contact Cisco Systems for assistance.
Error Message: %MAILBOX-3-INTERR: Bad mailbox interrupt = 0x[hex]Explanation:
A hardware problem was detected in a Chipcom interface board.
Recommended Action:
If this message recurs, contact Cisco Systems for assistance.
Error Message: %MAILBOX-3-MAIL020: Timeout while waiting for MAIL020, status=0x[hex]Explanation:
A hardware problem was detected in a Chipcom interface board.
Recommended Action:
If this message recurs, contact Cisco Systems for assistance.
Error Message: %MAILBOX-3-MAILFAIL: Mailbox failed to initializeExplanation:
A hardware problem was detected in a Chipcom interface board.
Recommended Action:
If this message recurs, contact Cisco Systems for assistance.
Error Message: %MAILBOX-3-PC2: Timeout while waiting for PC2, status=0x[hex]Explanation:
A hardware problem was detected in a Chipcom interface board.
Recommended Action:
If this message recurs, contact Cisco Systems for assistance.
Error Message: %MAILBOX-3-SPURINT: Spurious mailbox interrupt = 0x[hex], MAIL020 not assertedExplanation:
A hardware problem was detected in a Chipcom interface board.
Recommended Action:
If this message recurs, contact Cisco Systems for assistance.
Explanation:
The input error rate was so high that the interface was temporarily disabled. The interface will be automatically re-enabled in 30 seconds.
Recommended Action:
If this message recurs, check the communications lines.
Error Message: %MCI-4-NOKEEPALIVE Interface [chars] keepalive not sentError Message: %MCI-5-OBSOLETE Obsolete MCI firmware: can't route [chars] and bridge simultaneously
Explanation:
The firmware on your MCI controller card is out of date.
Recommended Action:
Upgrade your MCI firmware.
Error Message: %MCI-4-RSETFAIL Interface [chars] failed to reset properly in[chars], code 0x[hex] %MCI-3-RXINDEX Unit [dec], invalid RX index [dec] %MCI-3-SETUPERR Unit [dec], Error ([hex]) on setup, index [hex],restarting controller - mci_interrupt()Error Message: %MCI-4-TESTFAIL Unit [dec] failed [chars] test, skipping
Error Message: %MK5-3-BADUNIT Bad unit number [dec]
Error Message: %MK5-0-INITFAIL Unit [dec], initialization timeout failure,csr[dec]=0x[hex] %MK5-0-INITNOPPRIM Unit [dec], initialization failure - NoCSR1_PPRIM_INIT_CONF, csr1 = 0x[hex] %MK5-0-INITUERR Unit [dec], initialization CSR1_UERR failure,csr1=0x[hex]
Error Message: %MK5-0-MEMERR Unit [dec], memory error, csr0 = 0x[hex]
Explanation:
A network serial interface detected a hardware problem.
Recommended Action:
Service the hardware.
Error Message: %MK5-0-NOMEMORY Unit [dec], no memory for [chars]Error Message: %MK5-3-ODDSTART Interface [chars], Odd datagram start = 0x[hex], pak =0x[hex]
Error Message: %MK5-3-OUTENCAP Unit [dec], bad output packet encapsulation: 0x[hex]
Error Message: %MK5-3-PLOSTERR Unit [dec], provider primitive lost,csr0 = 0x[hex], csr1 = 0x[hex] %MK5-3-PPRIMERR Unit [dec], unexpected provider primitive,csr0 = 0x[hex], csr1 = 0x[hex] csr0 = 0x[hex], csr1 = 0x[hex] %MK5-3-SPURPPRIMERR Unit [dec], spurious provider primitive,csr0 = 0x[hex], csr1 = 0x[hex] %MK5-3-UPRIMERR Unit [dec], user primitive error,csr0 = 0x[hex], csr1 = 0x[hex]
Explanation:
A network serial interface detected a hardware problem.
Recommended Action:
Service the hardware.
Error Message: %PPP-6-LOOPED The line appears to be looped back
Explanation:
The communications line appears to be echoing the characters that are sent to it.
Recommended Action:
Check your data communications equipment to make sure it is configured correctly.
Explanation:
An internal software error has occurred.
Recommended Action:
If this message recurs, contact Cisco Systems for assistance.
Error Message: %PR-3-WRONGWATCH: Tty [t-line], lptwatch called for non-lptExplanation:
An internal software error has occurred.
Recommended Action:
If this message recurs, contact Cisco Systems for assistance.
Explanation:
The IP network used in the pup map command is not subnetted.
Recommended Action:
Enter a subnetted IP address as required by the pup map command.
Error Message: %RSRB-3-BADVERSIONIF IFin: [chars]: version mismatch, mine [dec], theirs [dec]
Explanation:
The remote end of a direct serial peer is running the wrong version of the system software. Either the local end, the remote end, or both are not up to date.
Recommended Action:
Call Cisco Systems for an update.
Error Message: %RSRB-3-BADVERSIONTCP [chars]: [dec]/[inet]: version mismatch, mine [dec], theirs [dec]Explanation:
The remote end of a TCP remote peer is running the wrong version of the system software. Either the local end, the remote end, or both are not up to date.
Recommended Action:
Call Cisco Systems for an update.
Error Message: %RSRB-4-BADVRE Bad vre type %RSRB-4-CONIPST Peer [dec]/[inet], CONN, illegal state [dec] %RSRB-4-CONNILLSTATE Peer [dec]/[inet], CONN, illegal state [dec] %RSRB-4-CONNSTAT Peer [dec]/[interface], IFin, bad connection state [dec] %RSRB-3-HDRNOVRP Peer [inet], HDR, no vrp %RSRB-4-HDRRECV Peer [dec]/[inet], HDR, recv state invalid, not empty [dec] %RSRB-3-HDRVRP Peer [dec]/[inet], HDR, vrp state wrong, [dec]Error Message: %RSRB-3-IFERR [chars]: [chars]: [chars], op [hex], len [dec], trn [dec]
Explanation:
The remote end of a direct serial RSRB connection has detected a configuration problem or traffic that is not recognized by the configuration.
Recommended Action:
Examine the configuration on both sides of the serial connection for possible problems. Examine the traffic being offered for propagation with respect to the configuration. The destination target ring is denoted by the value of trn.
Error Message: %RSRB-4-ILLPEER Peer [chars] [[hex]], illegal state [dec] %RSRB-4-LOCAL Unit [dec], local/vring set simultaneously,vrn [dec]Error Message: %RSRB-3-NOMEMORY Unit [dec], no memory for [chars]
Error Message: %RSRB-3-NOTREM Null idb and not remote %RSRB-4-PEERSTAT Peer [chars], wrong state [dec] %RSRB-4-OPTNULL: Remopened and t NULL
Error Message: %RSRB-3-SENDPUNTIF [chars]: sent [chars] to [dec]/[chars]
Explanation:
The local end of a direct serial RSRB connection has detected a configuration problem or traffic that is not recognized by the configuration.
Recommended Action:
Examine the configuration on both sides of the serial connection for possible problems. Examine the traffic being offered for propagation with respect to the configuration.
Error Message: %SBE-5-HUNGUP Interface [chars], hung up - resetting %SBE-4-RSETFAIL Failed to reset interface Serial[dec]
Explanation:
The SBE hardware is malfunctioning, or the firmware is improperly inserted.
Recommended Action:
Service the hardware.
Error Message: %SEC-4-TOOMANY Box secured, too many options on internal packet
Explanation:
No room for all desired IP header options. Packet discarded.
Recommended Action:
Configure for fewer IP header options.
Explanation:
An internal software error has occurred.
Recommended Action:
If any of these messages recur, contact Cisco Systems for assistance.
Error Message: %STUN-6-CONNOPENFAIL: CONN: peer [chars] open failed, [chars] [[dec]]Explanation:
An attempt to connect to a remote TCP STUN peer has failed.
Recommended Action:
Verify that the remote peer is accessible from this router, that it is running software capable of supporting the Serial Tunnel, and that it is configured correctly.
Error Message: %STUN-6-ERR: [chars]: [chars]: [chars], op [hex], len [dec]Explanation:
An internal software error has occurred.
Recommended Action:
If this message recurs, contact Cisco Systems for assistance.
Error Message: %STUN-3-NOPROTMEM: No memory for STUN protocol definition of [chars]Explanation:
The system does not have sufficient memory to support some or all of the Serial Tunnel configuration.
Recommended Action:
Reduce system configuration and take other actions as appropriate to increase memory available for Serial Tunnel operations.
Error Message: %STUN-6-OPENED: [chars]: peer [chars] opened, [previous state [chars]] %STUN-6-OPENING: CONN: opening peer [chars], [dec] %STUN-6-PASSIVEOPEN: passive open [inet]([dec]) -> [dec]Explanation:
A connection attempt to a remote peer has completed (OPENED, PASSIVEOPEN) successfully or is in the process of being opened (OPENING).
Recommended Action:
This is good, expected behavior. Nothing need be done.
Error Message: %STUN-6-PEERSHUTDOWN: shutting down peer [chars] on [chars]Explanation:
A connection to a remote peer is being shut down. This is typically the result of user intervention in Serial Tunnel reconfiguration or disabling.
Recommended Action:
This is good, expected behavior. Nothing need be done.
Error Message: %STUN-4-PEERSTATE: Peer [chars], wrong state [dec] ([dec])Explanation:
An internal software error has occurred.
Recommended Action:
If this message recurs, contact Cisco Systems for assistance.
Error Message: %STUN-6-RECONNECT: PHDR: reconnect from peer [chars]Explanation:
A remote peer has reestablished a connection to this router.
Recommended Action:
This is good, expected behavior. Nothing needs be done.
Error Message: %STUN-3-SENDPUNT: [chars]: sent [chars] to [chars] %STUN-3-SENDPUNTTCP: [chars]: sent [chars] to ([[dec]])[inet]Explanation:
An internal software error has occurred.
Recommended Action:
If any one of these messages recurs, contact Cisco Systems for assistance.
Error Message: %STUN-6-TCPFINI: peer [chars] closed [previous state [chars]]Explanation:
A remote peer has closed a Serial Tunnel connection with this router.
Recommended Action:
Examine the other router to see why it closed this connection with this peer. (This can be caused by normal events, such as reconfiguration.)
Error Message: %STUN-6-TCPPEERSHUT: [chars] [chars], [inet]([dec])Explanation:
This route has closed a Serial Tunnel 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: %SYS-6-NOBRIDGE Bridging software not present
Explanation:
Your system is not equipped to be a bridge.
Recommended Action:
Install the bridging software option.
Error Message: %SYS-3-NOPROC Process table full %SYS-2-NOTDEAD Process self-destruction failed %SYS-2-NOTQ p_unqueue didn't find [hex] in queue [hex] %SYS-2-NOTQ unqueue didn't find [hex] in queue [hex] %SYS-3-NULLIDB Null idb in [chars] %SYS-2-QCOUNT Bad dequeue [hex] count [dec] %SYS-2-QCOUNT Bad p_dequeue [hex] count [dec] %SYS-2-QCOUNT Bad p_unqueue [hex] count [dec] %SYS-2-QCOUNT Bad unqueue [hex] count [dec] %SYS-4-REGEXP [chars]Error Message: %SYS-5-RELOAD Reload requested %SYS-5-RESTART System restarted
Error Message: %SYS-2-RETBUF Bad retbuffer, ptr= [hex] %SYS-2-RETBUF1: Bad retbuffer, ptr= [hex], caller= [hex] %SYS-2-SELF s_setblock() on own process %SYS-2-SELFLINKED: Buffer [hex] linked to itself in free pool [chars] %SYS-2-SHARED Attempt to return buffer with sharecount [dec],ptr= [hex] %SYS-2-SHARED1: Attempt to return buffer with sharecount [dec], ptr= [hex], caller= [hex] %SYS-2-SMASHED Smashed block at [hex], next [hex], prev [hex],size [dec] %SYS-2-SMASHEDINFO: Smashed block last freed [hex], allocated by [hex], name [chars] %SYS-3-SOCKUNKN Unknown socket protocol [dec] %SYS-6-STACKLOW Stack for [chars] [chars] running low, [dec]/[dec] %SYS-2-SPEC Trying to set unknown special character [dec] to [dec]
Error Message: %SYS-3-TTYMEM Tty[t-line], no memory to save tty default parameters
Explanation:
A background TACACS notification (enabled with the command tacacs notify) was not acknowledged by the TACACS server processor within the timeout period (five minutes). The information contained in that notification has been lost. This may interfere with accounting or auditing on the server.
This condition arises when the TACACS server is misconfigured, has crashed, or has become unreachable via the network.
Recommended Action:
Check the TACACS server and the network attached to it.
Error Message: %TAC-4-UNEXREP Reply for non-existent request, [dec] on queueExplanation:
The TACACS facility received a message it was not expecting. This may occur when a TACACS server sends duplicate responses, or when it responds to a request which has already timed out. It may also be due to an internal software problem.
Recommended Action:
If this message recurs, contact Cisco Systems.
Explanation:
An attempt was made to delete an entry not in the queue.
Recommended Action:
Informational message only.
Explanation:
Another internal process is communicating to the given Token Ring interface.
Recommended Action:
Wait one minute and try again. If the condition persists then it probably indicates an internal software error. Contact Cisco Systems.
Error Message: %TR-4-BADADAPT Unit [dec], adapter not responding 0x[hex] 0x[hex]0x[hex] 0x[hex]Explanation:
The Token Ring interface is not responding to initialization.
Recommended Action:
Check the Token Ring card's configuration and make sure it is in the correct slot. The Token Ring card (CSC-R) is a Multibus master; it must be part of a contiguous group of bus master cards that includes the CPU. In most configurations the Token Ring interface will be the card immediately adjacent to the CPU. If the interface is in the correct slot, this message indicates a probable hardware failure. Contact Cisco Systems.
Error Message: %TR-3-BADMUL Unit [dec], Can't set TR address to hardware multicast address [enet]Explanation:
An attempt was made to set the Token Ring interface MAC address to a reserved multicast address.
Recommended Action:
Check your configuration. Make sure that your XNS and/or Novell Token Ring addresses have not inadvertently been set to reserved multicast addresses.
Error Message: %TR-3-BADRNGNUM: Unit [dec], ring number ([dec]) doesn't match established number ([dec])Explanation:
The number you have configured for the local ring does not match the value currently in use on the ring.
Recommended Action:
Check the configuration to make sure you used the correct ring number. If it is correct, check the configuration of all other bridges on the ring to make sure they are using the same ring number.
Error Message: %TR-3-BADSTART Unit [dec], Start completion and wrong idb state -state= [dec] %TR-4-BKGND Unit [dec], bkgnd int: last packet out [dec]ms %TR-4-BKGNDINT Unit [dec], bkgnd int: [hex][hex] [hex][hex][hex][hex] [hex][hex] %TR-3-COMPFAIL Unit [dec], Tbuf completion failure, result 0x[hex] %TR-3-FILTFAIL Unit [dec], SRB filter set failed: 0x[hex] 0x[hex]0x[hex] 0x[hex] (blk 0x[hex]) downing %TR-3-GETCONF Unit [dec], get_config failed, result 0x[hex] 0x[hex]Error Message: %TR-3-INCOM Unit [dec], incompatible firmware: system 0x[hex],interface 0x[hex]
Explanation:
The Token Ring interface contains firmware that is incompatible with the system software.
Recommended Action:
Call Cisco Systems to upgrade the Token Ring Monitor firmware and/or the system software.
Error Message: %TR-4-INTFAIL Unit [dec] interface failure: 0x[hex] 0x[hex] 0x[hex],idb state [dec]Explanation:
The Token Ring Monitor firmware has detected a fatal error due either to an internal software problem or a hardware failure.
Recommended Action:
The error message should be copied down exactly as it appears and conveyed to Cisco Systems.
Error Message: %TR-3-MODFAIL Unit [dec], tra_modify failed, result 0x[hex] 0x[hex]Error Message: %TR-3-NOMEMORY Unit [dec], no memory for [chars]
Error Message: %TR-3-NOPAK Unit [dec], Tbuf completion and no pakout
Error Message: %TR-3-OPENFAIL Unit [dec], open failed: [chars], [chars] (0x[hex])
Explanation:
The Token Ring interface was unable to insert itself into the ring. This is an indication of a busy or broken ring. The first character string in this error message will indicate the stage of initialization at which error occurred, and the second will describe the error.
Recommended Action:
Try to open the interface again. This can generally be accomplished by issuing the clear interface tokenring command. If the error message recurs, contact Cisco Systems.
Error Message: %TR-3-OPENFAIL2: Unit [dec], open failed: check the lobe cable connection.Explanation:
The Token Ring interface was unable to insert itself into the ring, and the error code returned indicates a wiring problem.
Recommended Action:
Check the cable connecting the router to the Token Ring MAU, and try to open the interface again. This can generally be accomplished by issuing the clear interface tokenring command. If the error message recurs, contact Cisco Systems.
Error Message: %TR-3-PANIC Unit [dec], panic [hex] [hex] [hex]Explanation:
The Token Ring Monitor firmware has detected a fatal error which indicates an impending interface failure.
Recommended Action:
The error message should be copied down exactly as it appears and included together with the interface error message. All this information should be conveyed to Cisco Systems.
Error Message: %TR-3-PANICINF Unit [dec], PI [hex] [hex] [hex] [hex][hex] [hex]Explanation:
This message is similar to the TR-3-PANIC error message but indicates a nonfatal error. This message appears in very unusual situations that should not arise in normal operation.
Recommended Action:
The error message should be copied down exactly as it appears and conveyed to Cisco Systems.
Error Message: %TR-3-PANICTYPE: Unit [dec], [chars] errorExplanation:
This message is similar to the TR-3-PANIC error message but indicates a nonfatal error. This message appears in very unusual situations that should not arise in normal operation.
Recommended Action:
The error message should be copied down exactly as it appears and conveyed to Cisco Systems.
Error Message: %TR-3-RESETFAIL: Unit [dec], reset failed, error code [hex].Explanation:
An internal software error occurred.
Recommended Action:
If message recurs, contact Cisco Systems.
Error Message: %TR-4-SNKBRIDG Unit [dec], removing invalid bridgeExplanation:
The system could not start a Token Ring source-route bridge because the interface in question does not have the appropriate Token Ring Monitor firmware or hardware.
Recommended Action:
Call Cisco Systems.
Error Message: %TR-3-SETFAIL Unit [dec], couldn't set interface to physical address [enet] (0x[hex])Explanation:
An illegal MAC address was specified for this interface.
Recommended Action:
Normally the Token Ring interface uses the burned-in address contained in a PROM on the board. However certain protocol stacks require the MAC address to be modified to an illegal value. Check your configuration for possible problems. If the problem persists call Cisco Systems.
Error Message: %TR-3-SETFUNFAIL: Unit [dec], set functional address failed (code [hex])Explanation:
An internal software error occurred.
Recommended Action:
If message recurs, contact Cisco Systems.
Error Message: %TR-3-SETGRPFAIL: Unit [dec], set group address failed (code [hex])Explanation:
An internal software error occurred.
Recommended Action:
If message recurs, contact Cisco Systems.
Error Message: %TR-3-SMTSTATFAIL: Unit [dec], get_smt: get smt stats failed - result [hex]Explanation:
An internal software error occurred.
Recommended Action:
If message recurs, contact Cisco Systems.
Error Message: %TR-3-STARTFAILED Unit [dec], start failed, result 0x[hex],reason 0x[hex]Explanation:
The Token Ring Monitor firmware attempted to insert the system into the ring and the chip set detected a non-standard fatal error.
Recommended Action:
This message indicates a problem with the Token Ring chip set hardware. Call Cisco Systems.
Error Message: %TR-6-STATE [chars]Explanation:
This message is displayed when the Token Ring's status has changed as determined by the chip set. This information is also used to automatically determine if the interface is still usable to propagate network traffic.
Recommended Action:
This is an advisory message only. No action is required.
Error Message: %TR-3-STATFAIL Unit [dec], get_static: get stats failed -Async: [hex] [hex] [hex] [hex]Error Message: %TR-6-STATRING [chars] ([hex]) LIV 0x[hex]
Explanation:
This message is displayed when the Token Ring's status has changed as determined by the chip set. This information is also used to automatically determine if the interface is still usable to propagate network traffic.
If the hexadecimal status code in this message is zero (0), it indicates that the ring has returned to a normal state. Otherwise, the first hexadecimal number is the sum of one or more status codes which indicate unusual conditions on the ring. The meaning of each status code is shown in Table A-4 .
Code Explanation Fatal?
0x8000 Signal loss Yes
0x4000 Hard error Yes
0x2000 Soft error No
0x1000 Transmit beacon Yes
0x0800 Lobe wire fault Yes
0x0400 Auto removal error Yes
0x0100 Remove request received Yes
0x0080 Counter overflow No
0x0040 Single station No
0x0020 Ring recovery No
Recommended Action:
Check the ring for the indicated condition.
Error Message: %TR-3-TRACMD tra_cmd: bad state: cmd 0x[hex] 0x[hex],result 0x[hex] 0x[hex] (blk 0x[hex], iob 0x[hex]) %TR-4-UNKNOWNCOMP Unit [dec], Unknown command completion:cmd 0x[hex], rslt 0x[hex] %TR-3-UNKNOWNT2M Unit [dec], Unknown t2m command [hex] [hex]
Error Message: %VINES-2-ROUTEADD: Cannot add route for [hex]:[hex], neighbor doesn't exist.
Explanation:
An internal software error has occurred.
Recommended Action:
If this message recurs, contact Cisco Systems for assistance.
|
|