Table Of Contents
GRIP Error Messages
Xerox Network Systems (XNS) Routing Protocol error messages
Error Message%GRIP-3-BADPATHS: Invalid number of paths [dec] for [dec]Explanation An internal inconsistency was detected in the XNS routing table structure.
Recommended Action Note the parameters associated with this message and call your technical support representative for assistance.
Error Message%GRIP-2-BADROUTE: Error [chars] route - null tableExplanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
HD Error Messages
HD64570 serial controller error messages
Error Message%HD-3-BADENCAP: msgtxt_badencap%HD-1-BADENCAP: Unit [dec], bad encapsulation in idb->enctype = [hex]%HD-1-BADRING: Bad [chars] ring size%HD-3-BADUNIT: Bad unit number [dec]Explanation An internal software error occurred.
Recommended Action If message recurs, call your technical support representative for assistance.
Error Message%HD-1-BADLOOPCABLE: msgtxt_badloopcableExplanation Loopback mode is not allowed when using an X.21 DTE cable on a Quad serial NIM port.
Recommended Action Do not enable loopback, or use a different cable type.
Error Message%HD-1-BADPORT: [chars]Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%HD-1-BADPORTADAPTER: [chars]Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%HD-0-INITFAIL: Unit [dec], initialization timeout failure,csr[dec]=[hex]Explanation The hardware failed to initialize correctly.
Recommended Action Repair or replace the controller.
Error Message%HD-5-LINEFLAP: Unit [dec] excessive modem control changesExplanation Too many modem control interrupts have been received. The port was disabled to prevent excessive use of the CPU.
Recommended Action Check the cable on the serial port.
Error Message%HD-1-MEMERR: Unit [dec], memory error, csr0 = [hex]Explanation A network serial interface detected a hardware problem.
Recommended Action Repair or replace the controller.
Error Message%HD-1-NOMEMOR: msgtxt_nomemoryExplanation The requested operation could not be accomplished because of a low memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%HD-0-NOMEMORY: Unit [dec], no memory for [chars]Explanation The requested operation could not be accomplished because of a low memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%HD-3-ODDSTART: Interface [chars], Odd datagram start = [hex], pak =[hex]%HD-3-OUTENCAP: Unit [dec], bad output packet encapsulation: [hex]Explanation An internal software error occurred.
Recommended Action If either of these messages recur, call your technical support representative for assistance.
Error Message%HD-3-OWNERR: Unit [dec], buffer ownership errorExplanation An Ethernet interface is malfunctioning, or an internal software error occurred.
Recommended Action Repair or replace the controller.
HUB Error Messages
Cisco Ethernet hub error messages
Error Message%HUB-1-BADHUB: Invalid hub type [dec] and number [dec]Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%HUB-1-BADUNIT: Bad port number [dec]Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%HUB-1-NOMEMORY: msgtxt_nomemoryExplanation The system detected that there is not enough memory for the hub initialization.
Recommended Action If conditions warrant, upgrade to larger memory configuration.
Error Message%HUB-1-READERR: Read op [dec] not allowedExplanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%HUB-1-WRITEERR: Write op [dec] not allowedExplanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
IBM2692 Error Messages
Error messages which refer to an IBM Token Ring chip set
Error Message%IBM2692-1-ADP_CHK: msg_adaptor_checkExplanation A hardware failure occurred. The port is disabled.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%IBM2692-1-ICDB_PERROR: msg_icdb_perrorExplanation A hardware failure occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%IBM2692-1-INITFAIL: msg_initfailExplanation A hardware failure occurred. The port failed to initialize.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%IBM2692-1-NOPCIMEMORY: msg_nopcimemoryExplanation The router or access server could not allocate memory for the descriptors.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%IBM2692-1-NOSYSMEMORY: msg_nosysmemoryExplanation The router or access server ran out of system memory.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%IBM2692-1-PCI_PERROR: msg_pci_perrorExplanation The protocol control information (PCI) bus failed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%IBM2692-1-RX_HALT: msg_rx_haltExplanation The receiving (RX) channel has shut down.
Recommended Action The software should recover. Record the message for later reference.
IGRP Error Message
Interior Gateway Routing Protocol error message
Error Message%IGRP-3-NOSOCKET: Unable to open socket for AS [dec]Explanation The requested operation could not be accomplished because of a low memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
IP Error Messages
Internet Protocol error messages
Error Message%IP-3-BADIPALIGN: Invalid alignment in packet for IP. [chars]=[hex]Explanation The packet data structure is misaligned. This condition may result in a small amount of overhead in processing IP traffic.
Recommended Action Enter a show hardware command and report the output, along with this error message, to your technical support representative.
Error Message%IP-3-BADSROUTE: Improper source route. Length [dec] Ptr [dec]Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%IP-4-CLASS: Bad IP address [inet] and mask [inet] in class_resolve()%IP-3-DESTHOST: src=[inet], dst=[inet], NULL desthostExplanation An internal software error occurred.
Recommended Action If either of these messages recur, call your technical support representative for assistance.
Error MessageIP-3-DESTHOST: src=[int], dst=[int], NULL desthostExplanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%IP-4-DUPADDR: Duplicate address [inet] on [chars], sourced by [enet]Explanation Another system is using your IP address.
Recommended Action Change the IP address of one of the two systems.
Error Message%IP-3-LOOPPAK: Looping packet detected and dropped - \nsrc=[int], dst=[int], hl=[int], tl=[int], prot=[int], sport=[int], dport=[int] \nin=[chars], nexthop=[int], out=[chars]\noptions=[chars], 1 * ONEMINExplanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%IP-5-WEBINST_COMP: Selected IP address [int]Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%IP-5-WEBINST_KILL: Terminating DNS processExplanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%IP-5-WEBINST_RESP: Sending DNS response to [int] (request was for [int])Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%IP-5-WEBINST_START: Attempting web install from host [int]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.
IPC Error Messages
Interprocess Communication error messages
Error Message%IPC-2-CANT_SEND: Cannot send IPC message: [chars]Explanation An error occurred in the IPC slave discovery mechanism. It might result in a malfunction in the operation of the IPC.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%IPC-2-CONSISTENCY: Message failed consistency check: [chars]Explanation An internal inconsistency was found in some IPC data structures.
Recommended Action Informational message only. No action required.
Error Message%IPC-2-DELETED: Attempt to delete an IPC message ([hex]) a second time.Explanation An internal inconsistency was found in some IPC data structures.
Recommended Action Informational message only. No action required.
Error Message%IPC-2-LOCK: Lock done a deleted elementExplanation An internal inconsistency was found in some IPC data structures.
Recommended Action Informational message only. No action required.
Error Message%IPC-2-NOBUFFER: Could not fetch a new message buffer.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%IPC-5-NODELFUNC: Delayed init function not availableExplanation The IPC application cannot be initialized because its initialization function does not appear in the IPC initialization function list.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%IPC-2-NODISPATCH: Message from [dec].[dec] has no receive queue or dispatch routine.Explanation The IPC user failed to provide any means of handling the received message.
Recommended Action Informational message only. No action required.
Error Message%IPC-2-NOMEM: No memory available for [chars].Explanation The IPC protocol subsystem could not obtain the memory it needed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%IPC-2-ONINT: Called from interrupt level: [chars]Explanation The IPC user attempted a prohibited call into IPC while IPC was running on the interrupt stack.
Recommended Action Informational message only. No action required.
Error Message%IPC-5-SLAVELOG: VIP-SLOT[dec] [chars]Explanation The Cisco IOS software, running on a Versatile Interface Processor (VIP) card, generated this message. The error message has been passed up to the Route Processor or Route Switch Processor (RP/RSP) for display. This message appears only if the user has configured service slavelog.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%IPC-2-UNLOCK: Unlock done on already unlocked element.Explanation An internal inconsistency was found in some IPC data structures.
Recommended Action Informational message only. No action required.
Error Message%IPC_RSP_CBUS-3-CARDERR: [chars]Explanation An IPC card has registered itself to the IPC master twice. The card malfunctioned and its IPC is not active.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%IPC_RSP_CBUS-3-INVNUM: [chars] ([dec])Explanation The IPC application tried to send a message that was larger than IPC could handle. The message was not transmitted.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%IPC_RSP_CBUS-3-MSGERR: [chars] ([dec])Explanation The slave IPC cannot register with master. It cannot exchange messages with the master.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%IPC_RSP_CBUS-3-NOBUF: [chars]Explanation The IPC ran out of memory device (MEMD) buffers.
Recommended Action Reduce the number of applications currently running on the IPC. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%IPC_RSP_CBUS-3-NOHWQ: Hardware queue for card at slot [dec] not foundExplanation IPC messages cannot be transmitted due to a missing hardware queue. The messages were discarded, and subsequent messages will not be transmitted to that card.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%IPC_RSP_CBUS-3-PROC: [chars] ([dec])Explanation IPC processes cannot be created due to operating system errors. The IPC will be inactive.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%IPC_RSP_CBUS-3-SEATERR: [chars] ([dec])Explanation The ID associated with an IPC card is either missing, duplicated, or cannot be created.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
IPFAST Error Messages
IP fast-switching error messages
Error Message%IPFAST-2-BADIF: No support available for interface [chars] (programming error), 30*ONESECExplanation A programming error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%IPFAST-7-INTLEV: Cache update request at interrupt level: [inet]([chars])->[inet]([chars]), 5*ONESECExplanation A programming error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%IPFAST-6-INVALIDATE: Cache invalidation occurring for [chars], ONESECExplanation The system is invalidating all cache entries for a given interface.
Recommended Action Informational message only. No action required.
Error Message%IPFAST-6-INVALREQ: Cache invalidation request for [chars]Explanation The system is invalidating all cache requests for a given interface.
Recommended Action Informational message only. No action required.
Error Message%IPFAST-4-RADIXDELETE: Error trying to delete prefix entry for [dec] [dec] (expected [hex], got [hex])Explanation Problems related to the IP route cache triggered this debugging message.
Recommended Action The router should correct for this error. If the router cannot forward packets properly or is experiencing other problems, copy the error message exactly as it appears and report it to your technical support representative.
Error Message%IPFAST-2-RADIXINIT: Error initializing IP fast cache structuresExplanation A programming error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%IPFAST-4-RADIXINSERT: Error trying to insert prefix entry for [dec] [dec] (expected [hex], got [hex])Explanation Problems related to the IP route cache triggered this debugging message.
Recommended Action The router should correct for this error. If the router cannot forward packets properly or is experiencing other problems, copy the error message exactly as it appears and report it to your technical support representative.
Error Message%IPFAST-3-SANITY: Found existing [chars] specific entry [dec] [ip mask]..[ipmask]->[dec] ([chars]) when " "attempting to create [dec] [ipmask]..[ipmask]->[dec] ([chars])Explanation Problems related to the IP route cache triggered this debugging message.
Recommended Action The router should correct for this error. If the router cannot forward packets properly or is experiencing other problems, copy the error message exactly as it appears and report it to your technical support representative.
IPRT Error Messages
Internet Protocol routing error messages
Error Message%IPRT-3-BADCOMLIST: Community list check with bad list [dec], 10*ONESECExplanation A user specified an invalid BGP community list number.
Recommended Action Check the system configuration to make sure that the community list specified falls within the valid range.
Error Message%IPRT-2-COMPRESS: Bad route_compress() call, sdb= [hex]Explanation An internal software error occurred.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%IPRT-3-NOMEMORY: No memory available for [chars]Explanation The requested operation failed because of a low memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%IPRT-3-PATHIDX: Bad path index of [dec] for [inet], [dec] max, ONEMINExplanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%IPRT-3-TOOMANYNETS: Too many networks in [char] [dec] (limit [dec])Explanation Too many network subcommands have been entered for this routing protocol.
Recommended Action Advisory message only. No action required.
IPX Error Messages
Internetwork Packet Exchange error messages
Error Message%IPX-3-BADCOUNT: Bad IPX server count. [chars] [dec], [chars] [dec]Explanation The internal SAP service count does not match the number of services currently present and displayed by the show ipx servers command.
Recommended Action You can report the problem to your technical support representative, but no corrective action is necessary.
Error Message%IPX-3-BADIGRPSAP: Cannot send incremental SAP update to peer on interface [chars]. Increase buffers or increase output-sap-delay.Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%IPX-3-BADIGRPSAPTYPE: Unsupported SAP type for EIGRP being [chars] - type [hex]Explanation There are two types of service access points (SAPs), general queries and general responses. This message is sent when you receive or attempt to send an SAP with a type code which is not a general query or a general response. It is also sent when you receive a general query not addressed to the broadcast address.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%IPX-3-BADPATHS: Invalid number of paths [dec] for [hex]Explanation An internal inconsistency was detected in the IPX routing table structure.
Recommended Action Note the parameters associated with this message. If possible, clear the IPX routing table by issuing the clear ipx route command. (This will result in lost connectivity until the routing table is rebuilt.) If the message recurs, note the parameters and call your technical support representative for assistance.
Error Message%IPX-3-NOMEMORY: Unable to allocate memory for [event]Explanation The system failed to allocate memory for an event. The event variable will be one of the following procedures which attempts to allocate memory:
SAP queue routing table SAP update SAP update queue entry RIP update queue entry SAP heap sort pointer array RIP update EIGRP process route entryRecommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
ISDN Error Messages
Integrated Services Digital Network (ISDN) error messages
Error Message%ISDN-6-CONNECT: Interface [chars] is now connected to [chars] [chars]Explanation This is an informational message. It is sent when a call is connected. The message displays the remote name and number, which it receives from the Point-to-Point Protocol (PPP) authentication or from where the dialer placed the call to.
Recommended Action No action is required.
Error Message%ISDN-6-DISCONNECT: Interface [chars] disconnected from [chars] [chars], call lasted [int] secondsExplanation This is an informational message. It is sent when a call is disconnected. The message displays the remote name and number, which it receives from the Point-to-Point Protocol (PPP) authentication or from where the dialer placed the call to. It also shows how long the call lasted.
Recommended Action No action is required.
LANCE Error Messages
Local area network controller Ethernet interface error messages
Error Message%LANCE-4-BABBLE: Unit [dec], babble error, csr0 = [hex]Explanation An Ethernet interface is malfunctioning.
Recommended Action
1
Determine whether the malfunction stems from a software or hardware error by turning off all fastswitching.
2
•
3
•
Error Message%LANCE-3-BADENCAP: Unit [dec], bad encapsulation in idbenctype = [hex]%LANCE-3-BADUNIT: Bad unit number [dec]Explanation An internal software error occurred.
Recommended Action If either message recurs, call your technical support representative for assistance.
Error Message%LANCE-5-COLL: Unit [dec], excessive collisions. TDR=[dec]Explanation An Ethernet cable is broken or unterminated, or the transceiver is unplugged. The time delay reflectometer (TDR) counter is an internal LANCE counter that counts the time (in "ticks" of 100 ns each) from the start of a transmission to the occurrence of a collision. Because a transmission travels about 35 feet per tick, this value is useful to determine the approximate distance to a cable fault.
Recommended Action If the transceiver appears to be properly terminated, repair or replace the Ethernet interface card.
Error Message%LANCE-1-INITFAIL: Unit [dec], initialization timeout failure, csr[dec] = [hex]Explanation The hardware failed to initialize correctly.
Recommended Action Repair or replace the controller.
Error Message%LANCE-5-LATECOLL: Unit [dec], late collision errorExplanation An Ethernet transceiver is malfunctioning, the Ethernet is overloaded, or the Ethernet cable is too long.
Recommended Action Repair or replace the controller.
Error Message%LANCE-5-LOSTCARR: Unit [dec], lost carrier. Transceiver problem?Explanation An Ethernet transceiver is unplugged or faulty.
Recommended Action Repair or replace the controller.
Error Message%LANCE-1-MEMERR: Unit [dec], memory error, csr0 = [hex]Explanation An Ethernet interface detected a hardware problem.
Recommended Action Repair or replace the controller.
Error Message%LANCE-1-NOMEMORY: Unit [dec], no memory for [chars]Explanation The requested operation could not be accomplished because of a low memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%LANCE-3-OWNERR: Unit [dec], buffer ownership errorExplanation An Ethernet interface is malfunctioning, or an internal software error occurred.
Recommended Action Repair or replace the controller.
Error Message%LANCE-3-SPURIDON: Unit [dec], spurious IDON interruptExplanation An Ethernet interface generated a spurious Initialization Done interrupt.
Recommended Action Repair or replace the controller.
Error Message%LANCE-3-UNDERFLO: Unit [dec], underflow errorExplanation The Ethernet hardware is requesting data faster than the system can supply it. This condition might indicate that the system is at the limit of its performance.
Recommended Action A small number of underflows might not be a cause for concern. You can monitor underflows with the show interface command. Reducing the load on the router or installing a higher-performance router should alleviate this problem.
LANE Error Messages
LAN emulation error messages
Error Message%LANE-3-BADILMI: Unexpected ILMI event [dec]Explanation An internal error occurred.
Recommended Action This error should not occur. Download the system error log, then call your technical support representative and provide the log, the error message, and the router configuration.
Error Message%LANE-3-BADNAME: ELAN name must be 1-32 characters longExplanation An emulated LAN (ELAN) name was entered in a command that is longer than 32 characters. The LANE standard v1.0 requires a name that is 32 characters or less in length.
Recommended Action Re-enter a shorter name.
Error Message%LANE-3-BADTYPE: LAN Emulation supports only Ethernet typeExplanation The user specified a Token-Ring-emulated LAN, which is not currently supported.
Recommended Action Specify an Ethernet-emulated LAN. Future software releases will support Token Ring ELANs.
Error Message%LANE-3-LANE_LESBUS_UP: LES/BUS coming up from previous commandExplanation The lane server-bus command was reissued to start the LANE service components while the router was trying to execute a previously issued lane server-bus command.
Recommended Action Wait for the initial lane server-bus command to either succeed or fail. The status of the server bus can be checked via the show lane server-bus interface sub-interface name command. The previous command can also be cancelled with the no lane server-bus command. If these steps fail to clear the problem, issue the shutdown command followed by a no shutdown command cycle on the subinterface, or on the whole interface. As a last resort, issue the no interface sub-interface name command followed by the shutdown, no shutdown command cycle.
Error Message%LANE-3-LANE_SIG_CHAIN: not in [chars] chain ([hex] [hex])Explanation An internal error occurred while system routines were handling ATM signaling messages for LANE.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LANE-3-LANE_SIG_ERR: [chars]Explanation An internal error occurred while system routines were handling ATM signaling messages for LANE.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LANE-3-LANE_SIG_INV_MSG: invalid msg received ([hex] [hex] [hex])Explanation An internal error occurred while system routines were handling ATM signaling messages for LANE.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LANE-3-LANE_SIG_INV_STATE: invalid [chars] req in state [dec] ([hex])Explanation An internal error occurred while system routines were handling ATM signaling messages for LANE.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LANE-6-LEC: [chars]Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LANE-3-LEC_BADAD: [chars] LEC unable to compute ATM addressExplanation The client cannot obtain an ATM address from the given configuration, or auto-assignment failed to get an ATM prefix from the switch.
Recommended Action If you expect the switch to assign the prefix to the router, check that the Interim Local Management Interface (ILMI) is functional and the switch has a prefix configured. Otherwise, confirm that the client has an address in the NVRAM configuration.
Error Message%LANE-3-LEC_CFG: [chars] CFG_REQ failed, [chars] (LECS returned [dec])Explanation A software or hardware error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LANE-3-LEC_CONTROL_MSG: Received bad control message on interface > [chars], 10*ONESECExplanation The client received a control message over one of its control virtual channel connections (VCCs) that failed the header check.
Recommended Action This message indicates a noninteroperable LANE configuration server, LANE server, or LANE client implementation on the emulated LAN.
Error Message%LANE-3-LEC_ERR: [chars], 10*ONESECExplanation A software or hardware error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LANE-6-LEC_INFO: [chars]Explanation A software or hardware error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LANE-3-LEC_JOIN: [chars] JOIN failed, [chars] (LES returned [dec])Explanation A software or hardware error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LANE-3-LEC_LISTEN: [chars] listen failed on [chars]Explanation The client failed an attempt to listen on a particular ATM address.
Recommended Action Reconfigure the client ATM address. It is conflicting with another component on the ATM Interface Processor (AIP) for the same ATM address.
Error Message%LANE-3-LEC_SIGNAL: Unexpected SigAPI event [dec], 10*ONESECExplanation ATM signaling sent the client an unexpected message type.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LANE-4-LEC_STATE_ERROR: State: [dec], Event [dec]Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LANE-6-LEC_TIMER: Timer [chars] expiredExplanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LANE-3-LECS_ERR: [chars]Explanation An internal consistency error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LANE-4-LECS_WARN: [chars]Explanation The LANE configuration server address could not be registered with or de-registered from the switch, using Interim Local Management Interface (ILMI).
Possible causes
•
•
•
•
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LANE-3-LSV_ADDR: [chars] elan [chars] unable to register LES/BUS ATM addrExplanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LANE-3-LSV_BADAD: <interface> elan <ELAN name> unable to compute [chars] ATM addressExplanation Software was unable to compute an ATM address based on the ATM address template given. The characters in
chars(see above display) will be either "BUS" (broadcast-and-unknown), "server," or "config server" in the actual error message.Recommended Action Enter a correct ATM address template for the LANE component ("BUS," "server," or "config server") named in the error message.
Error Message%LANE-3-LSV_CRASH: <interface> elan <ELAN name> unrecoverable error [chars]Explanation An internal error occurred.
Recommended Action This error should not occur. Download the system error log, then call your technical support representative and provide the log, the error message, and the router configuration.
Error Message%LANE-3-LSV_DUPATM: <interface> elan <ELAN name> client [dec] duplicate ATM address registration <ATM address>Explanation An attempt was made by the specified LANE client to register a MAC address and ATM address pair that duplicated an ATM address already registered to another LANE client.
Recommended Action Use the show lane server command to list the registered addresses in the LANE server reporting the error. Correct one of the two LANE clients that is trying in error to use the same ATM address.
Error Message%LANE-3-LSV_DUPID: <interface> elan <ELAN name> duplicate LECID [dec]Explanation An attempt was made to define two different server-direct PVCs both on the same subinterface (same LANE server) and both for the same client (LECID).
Recommended Action Delete one of the lane pvc commands that has this duplicated LECID.
Error Message%LANE-3-LSV_DUPMAC: <interface> elan <ELAN name> client [dec] duplicate MAC address registration [enet]Explanation An attempt was made by the specified LANE client to register a MAC address and ATM address pair that duplicated a MAC address already registered to another LANE client.
Recommended Action Use the show lane server command to list the registered addresses in the LANE server reporting the error. Correct one of the two LANE clients that is trying in error to use the same MAC address.
Error Message%LANE-4-LSV_LECID: <interface> elan <ELAN name> LECIDs exhausted, 10*ONESECExplanation The LANE server specified has 65279 clients. No more can be added.
Recommended Action Change the configurations to avoid trying to have more than 65279 LANE clients on this server.
Error Message%LANE-3-LSV_MCAST: <interface> elan <ELAN name> unable to create [chars] MC groupExplanation An internal error occurred.
Recommended Action This error should not occur. Download the system error log, then call your technical support representative and provide the log, the error message, and the router configuration.
Error Message%LANE-3-LSV_NOREG: <interface> elan <ELAN name> client [dec] unable to register MAC address [enet]Explanation An internal error occurred.
Recommended Action This error should not occur. Download the system error log, then call your technical support representative and provide the log, the error message, and the router configuration.
Error Message%LANE-6-MAKE17: Created vcd [dec] (PVC [dec]/[dec]) for config server accessExplanation The LANE software created a PVC (normally 0/17) for accessing the LANE configuration server.
Recommended Action Informational message only. No action required.
Error Message%LANE-3-NAMECHG: Attempt to change ELAN nameExplanation Both the LANE client and the LANE server/broadcast-and-unknown server may have an emulated LAN name specified in the configuration via the lane server-bus and lane client commands. If both specify the emulated LAN name, then the name cannot be changed by re-entering just one of the commands.
Recommended Action Use the no lane server-bus command to delete the server/broadcast-and-unknown server or the no lane client command to delete the client. Then, the other of the two commands can be re-entered with another emulated LAN name. Finally, re-enter the deleted command with the new emulated LAN name.
Error Message%LANE-3-NEWPREF: <interface> elan <ELAN name> ATM address prefix [chars]Explanation Entering a new ATM address template for some LANE component caused the specified LANE server or bus to drop all clients and restart.
Recommended Action Informational message only. No action required.
Error Message%LANE-3-NOILMI: ILMI service registration failedExplanation The Interim Local Management Interface (ILMI) feature is not included in the software build running on the router.
Recommended Action Reload router with software that includes the ILMI feature.
Error Message%LANE-3-NOINT: <interface> still destroying old sub-interfaceExplanation An attempt was made to create a new subinterface while a previous version of the subinterface was still being destroyed.
Recommended Action Wait a minute and try again. If failure still occurs, try shutting down the main interface. Rebooting may be required to recover in extreme cases.
Error Message%LANE-3-NOREGATM: <interface> cannot register <ATM address> with ILMIExplanation An attempt to register the given ATM address with the ATM switch failed. This failure can occur because the ATM switch is down or misconfigured. The registration will be retried.
Recommended Action If the situation persists after a number of attempts, and the switch is up, the configuration of the switch and router must be examined. The most likely cause is that ATM address being registered is not compatible with the parameters — for example, the ATM address prefix — configured in the switch. Correct the configuration.
Error Message%LANE-3-NOVCD: VCDs exhaustedExplanation When trying to create PVC 0/17, the router ran out of PVC resources.
Recommended Action The number of PVCs can be increased with the atm maxvc command.
Error Message%LANE-3-PVCBAD: <interface> elan <ELAN name> PVC vcd [dec] has no [chars] assignedExplanation The characters in
chars(see above display) will be either "ATM address" or "LECID." This message is reported when a permanent virtual circuit (PVC) is created without all the necessary information included in the lane pvc command.Recommended Action Include a lane pvc command with the information appropriate for the PVC.
Error Message%LANE-3-PVCLECS: Unable to create PVC [dec]/[dec]Explanation An attempt to create the named PVC failed. The most likely reason is that a PVC was defined on the same or another subinterface with the same virtual path identifier-virtual channel identifier (VPI-VCI) pair, but with a different encapsulation or usage type.
Recommended Action Correct the configuration.
Error Message%LANE-3-REGSTATE: ILMI event in state [dec]Explanation An internal error occurred.
Recommended Action This error should not occur. Download the system error log, then call your technical support representative and provide the log, the error message, and the router configuration.
Error Message%LANE-3-TYPECHG: Attempt to change ELAN typeExplanation Both the LANE client and the LANE Server/BUS may have an ELAN type specified in the configuration via the lane server-bus and lane client commands as either Ethernet or Token Ring. If both, specify the type; the type cannot be changed by re-entering just one of the commands.
Recommended Action Use the no lane server-bus command to delete the server-bus or the no lane client command to delete the client. Then, the other of the two commands can be re-entered with a new type. Finally, re-enter the deleted command with the new type.
Error Message%LANE-5-UPDOWN: [chars] [chars] [chars]: [chars] changed state to [chars]Explanation A software or hardware error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
LANMGR Error Messages
IBM LAN Network Manager error messages
Error Message%LANMGR-4-BADRNGNUM: Ring number mismatch on [chars], shutting down RPS.Explanation The router detected a conflict in assigned ring numbers for the specified Token Ring. The Ring Parameter Server (RPS) function was shut down to prevent potentially incorrect information from being sourced onto the ring.
Recommended Action Check all bridges connected to this Token Ring and ensure that they are using the same assigned ring number.
Error Message%LANMGR-4-BADUPCALL: Unexpected call ([chars]) from LLC2 for Bridge [hex]-[hex]-[hex].Explanation An internal software error occurred.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%LANMGR-4-OLDTRAMON: Cannot run RPS on [chars], Old TRAMON code.Explanation The software on this interface cannot support the functions required for LAN Network Manager.
Recommended Action Call your technical support representative about a firmware upgrade for this interface card.
LAPB Error Messages
X.25 Link Access Procedure, Balanced error messages
Error Message%LAPB-4-CTRLBAD: Interface [chars], Invalid control fieldExplanation A received FRMR reported a frame with an invalid control code.
Recommended Action Check the serial line and the devices attached to the line.
Error Message%LAPB-4-FRAMEERR: Interface [chars], Frame error: CF [hex], VS[dec] [char] VR [dec], Reason [hex]Explanation A FRMR frame was received, indicating that a protocol violation was detected. The Reason field will be interpreted by generating INFOBAD, CTRLBAD, N1TOOBIG, or INVNR messages immediately after this message; refer to the explanations for these messages for more information.
Recommended Action The protocol will recover by resetting the service. This will disrupt any network service on top of LAPB (for example, X.25 virtual circuits will be cleared). Follow the recommended action for any error message following the FRMR reports; if service becomes unacceptable, check the serial line and its attached devices.
Error Message%LAPB-4-INFOBAD: Interface [chars], Info field not permittedExplanation A received FRMR frame reported that an information field was present in a frame where no information field is allowed.
Recommended Action Check the serial line and the device attached to the line.
Error Message%LAPB-4-INVNR: Interface [chars], Invalid NR valueExplanation A received FRMR reported a frame with an invalid N(R) value.
Recommended Action Verify that the equipment attached to the serial line is configured with the same K value (maximum number of outstanding I frames).
Error Message%LAPB-4-N1TOOBIG: Interface [chars], N1 too largeExplanation A received FRMR reported an information frame that was too long.
Recommended Action Verify that the equipment attached to the serial line is configured with the same N1 value. N1 is in bits and includes the entire frame plus 16 bits of CRC. However, some equipment may require configuration in octets, the omission of the two CRC octets, or the omission of the three octets of LAPB control information.
Error Message%LAPB-2-NOBUF: Interface [chars], no buffer available to [chars]Explanation There was insufficient memory for the LAPB protocol engine to send a message.
Recommended Action This message is acceptable if it occurs infrequently, because the LAPB protocol is designed to handle loss of frames. Frequent occurrences can cause disruption of service. The system can be configured to ease memory demands or, if conditions warrant, the system can be upgraded to a larger memory configuration.
Error Message%LAPB-3-NOINPIDB: Input idb not set%LAPB-3-NULLPAK: Interface [chars], NULL packet ptr, rvr [dec],vs [dec], vr [dec]Explanation An internal software error occurred.
Recommended Action If either of these messages recur, call your technical support representative for assistance.
LAT Error Messages
DEC Local Area Transport error messages
Error Message%LAT-3-BADDATA: Tty[t-line], Data pointer does not correspond to current packet%LAT-3-BUFFULL: Tty[t-line], data buffer full with count [dec]Explanation An internal software error occurred.
Recommended Action If either of these messages recur, call your technical support representative for assistance.
Error Message%LAT-3-NOSYNC: Tty[t-line], Output data ptrs out of sync with byte countExplanation An internal software error occurred.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%LAT-3-NULLIDB: Null IDB pointer with destination [enet]%LAT-3-QBSPACED: Queue block at [hex] not found for HI connection%LAT-3-REUSE: Tty[t-line], Attempt to re-use slot array, empty =[dec], fill = [dec]Explanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
LEX Error Messages
LAN extension error messages
Error Message%LEX-3-NOTSENT: Serial line down, [chars] : [chars] not sentExplanation The serial line went down, and the specified command was not sent to the LAN Extender.
Recommended Action Determine why the serial line went down. For example, was the cable was pulled, or the LAN Extender powered off? The command will automatically be re-sent once the serial interface is operational.
Error Message%LEX-3-RCMDNAK: [chars] : [chars] could not be processed by LAN ExtenderExplanation The LAN Extender could not process the command from the host router. Possible causes are:
•
•
•
•
Recommended Action If the command was copy tftp lex unit-number or copy flash lex unit-number, make sure that the correct file, that is, a FLEX image file, is specified. Only a single copy request can be handled at one time. If the problem was caused by a temporary out-of-memory condition on the LAN Extender, re-enter the command.
Error Message%LEX-3-RCMDREJ: [chars] : [chars] could not be processed by LAN ExtenderExplanation The LAN Extender did not recognize the code for the specified remote command. This might occur if the user is running old LAN Extender software with newer host router software that has support for new LEX remote commands.
Recommended Action Update the LAN Extender software.
Error Message%LEX-3-TIMEOUT: Retry count exceeded for [chars] : [chars]Explanation The host router re-sent the given message as many times as specified in the lex retry-count command configuration variable, without receiving an acknowledgment from the LAN Extender. At this point, the host router gives up trying to send this particular remote command message.
Recommended Action Use the LEDs on the LAN Extender to determine if it is operational. Confirm that the lex timeout configuration command is set appropriately for the speed of the link.
LINEPROTO Error Message
Line Protocol error message
Error Message%LINEPROTO-5-UPDOWN: Line protocol on Interface [chars], changed state to [chars]Explanation The data link level line protocol changed state.
Recommended Action Notification message only. No action required.
LINK Error Messages
Data link error messages
Error Message%LINK-3-BADENCAP: Interface [chars] Bad encapsulation code [dec]Explanation The lower level software was unable to write a MAC header for a datagram. A probable cause is configuration error.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LINK-3-BADETHER: Interface [chars], Bad ethernet encap codeExplanation An internal software error occurred.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%LINK-3-BADMACREG: Interface [chars], non-existent MACADDR registry for link [dec]Explanation An attempt to map a network level address to a MAC level address failed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LINK-2-BADVCALL: Interface [chars], undefined entry pointExplanation An internal software error occurred. The high-level system code tried to use an unimplemented entry point with the virtual interface descriptor block (IDB) driver.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%LINK-3-BOGUSENCAP: msgtxt_badencapExplanation A serial interface has been configured with an unknown encapsulation.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LINK-5-BOOTP: [chars] address [inet], resolved by [inet]Explanation An interface's IP address was successfully learned dynamically through BootP. The first address is the learned IP address. The second IP address is the IP address of the BootP server that provided the information.
Recommended Action No action required.
Error Message%LINK-4-BRIDGECONFLICT: [char], encapsulated BPDU recvd from [enet]Explanation A FDDI interface running in nonencapsulating transparent mode detected an FDDI bridge running in encapsulation mode on the same fiber. This is an unstable situation and should be corrected. The incoming interface is displayed, along with the FDDI MAC address in standard form.
Recommended Action Upgrade the errant interface to full transparent mode. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LINK-5-CHANGED: Interface [chars], changed state to [chars]Explanation The interface hardware changed state.
Recommended Action Notification message only. No action required.
Error Message%LINK-3-COMPREG: Interface [chars], non-existent (de)compression registry. Packet droppedExplanation A software or hardware error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LINK-4-FDDISTAT: Interface [chars], FDDI state [chars] detectedExplanation There was a state change on the FDDI ring.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LINK-4-FDDIUNK: [chars]: unknown [hex] len [dec]Explanation An unknown FDDI datagram was received.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LINK-2-LINEST: No linestate vector for [chars]Explanation An internal software inconsistency occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LINK-4-NOMAC: A random default MAC address of [enet] has\n been chosen.Explanation An addressing inconsistency occurred.
Recommended Action Make sure that this address is unique, or specify MAC addresses for commands such as novell routing that allow the use of this address as a default.
Error Message%LINK-2-NOSOURCE: Source idb not set%LINK-3-TOOBIG: Interface [chars], Output packet size of [dec] bytes too big%LINK-3-TOOSMALL: Interface [chars], Output packet size of [dec] bytes too small. Changed to [dec] bytes%LINK-2-UENCAP: Unknown line encapsulation code [dec]Explanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%LINK-5-RARP: [chars] address [inet], resolved by [inet]Explanation The Reverse Address Resolution Protocol (RARP) resolved an IP address.
Recommended Action Notification message only. No action required.
Error Message%LINK-3-REMLOOP: Interface [chars], remote loop [chars] [chars]Explanation The interface entered or exited a remote loopback.
Recommended Action Notification message only. No action is required.
Error Message%LINK-5-SLARP: [chars] address [inet], resolved by [inet]Explanation The Serial Line Address Resolution Protocol (SLARP) resolved an IP address.
Recommended Action Notification message only. No action required.
Error Message%LINK-3-UPDOWN: Interface [chars], changed state to [chars]Explanation The interface hardware went either up or down.
Recommended Action If the state change was unexpected, confirm the configuration settings for the interface.
LLC2 Error Messages
Logical Link Control, type 2 error messages
Error Message%LLC-4-T1_ERR: LLC2: [chars] INCREASE LLC TIMERSExplanation The T1 timer popped for an LLC2 session. However, the frame which is to be retransmitted is still on a queue inside the router awaiting transmission over RSRB, Frame Relay, or other protocol. If the retransmission occurs, the LLC2 session will probably fail due to N2 retry failures.
Recommended Action Increasing the LLC2 acknowledgment timers decreases the likelihood of failure. In addition, investigate sporadic congestion in a routed network.
Error Message%LLC-2-UNEXPECT: LLC2: [chars] UNEXPECTED EVENTExplanation An internal software error was found. A software component is trying to use LLC2 structures that do not exist.
Recommended Action Record the configuration and any information that would be useful in recreating the error and call your technical support representative.
LNMC Error Messages
LAN network manager system error messages
Error Message%LNMC-3-BADCLSI: [chars] primitive not valid for lnm [hex] [hex]%LNMC-3-BADCLSICNF: [chars] Invalid confirm [chars] [cha [chars]%LNMC-3-BADCLSIDATALEN: [chars] Bad data len =[dec] [hex]%LNMC-3-BADCLSIHDRLEN: [chars] Bad header len = [hex] [hex] [chars]%LNMC-3-BADCLSIIDTYPE: [chars] Invalid ID type = [hex] [hex] [chars]%LNMC-3-BADCLSIIND: [chars] Invalid indication [chars], [chars]%LNMC-3-BADCLSIPRIMTYPE: [chars] Invalid primitive type = [hex] [hex] [chars]%LNMC-3-BADCLSIRET: [chars] Invalid ret code [hex] [hex] [chars] [chars]%LNMC-3-BADCLSISAP: [chars] Bad clsi SAP id = [hex] [chars]Explanation A LAN network manager system error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
LPD Error Message
Line printer daemon error message
Error Message%LPD-3-MANYLF: Line [t-line], packet has too many newlines to convertExplanation An internal buffer did not have enough room to add all the necessary carriage returns to a packet of LPD data destined for a printer configured with a newline-convert command. This message is unlikely to occur with a file containing valid data.
Recommended Action Check the file being printed to see whether it contains valid, printable data.