Полезная информация

cc/td/doc/product/software/ios120/12supdoc
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

IPFAST Error Messages
IPFLOW Error Messages
IPMCAST Error Message
IPRT Error Messages
IP_SNMP Error Messages
IPX Error Messages
ISDN Error Messages
LANCE Error Messages
LANE Error Messages
LANMGR Error Messages
LAPB Error Messages
LAT Error Messages
LC Error Messages
LCCEF Error Messages
LCCOREDUMP Error Messages
LCINFO Error Messages
LCLOG Error Messages
LCPLIM Error Messages
LCPOS Error Messages
LES_FDDI Error Message
LEX Error Messages
LINEPROTO Error Message
LINK Error Messages
LLC2 Error Message
LLIST Error Messages
LNMC Error Messages
LPD Error Message

IPFAST Error Messages

IP fast-switching error messages


Error Message   
%IPFAST-2-BADIF: No support available for interface [chars] (programming error)

Explanation   A programming error occurred.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.


Error Message   
%IPFAST-3-INTLEV: Cache update request at interrupt level: [int]([chars])-[int]([chars])

Explanation   A programming error occurred.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.


Error Message   
%IPFAST-3-INVALIDADDR: Invalid cache destination [int]/[dec]

Explanation   The system attempted to add a cache entry for an invalid address.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.


Error Message   
%IPFAST-6-INVALIDATE: Cache invalidation occurring for [chars]

Explanation   The system is invalidating all cache entries for a given interface.

Recommended Action   No action is 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   No action is required.


Error Message   
%IPFAST-4-RADIXDELETE: Error trying to delete prefix entry for [int]/[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 Cisco technical support representative.


Error Message   
%IPFAST-2-RADIXINIT: Error initializing IP fast cache structures

Explanation   A programming error occurred.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.


Error Message   
%IPFAST-4-RADIXINSERT: Error trying to insert prefix entry for [int]/[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 Cisco technical support representative.

IPFLOW Error Messages

IP flow error messages


Error Message   
%IPFLOW-4-ACTIVATE: Error activating [chars]([dec]) in slot [dec]

Explanation   Activation of a flow accelerated feature failed because of a sanity check.

Recommended Action   Copy the message exactly as it appears and report it to your technical support representative.


Error Message   
%IPFLOW-4-ACTIVATENOMEM: Error activating [chars]([dec])

Explanation   Activation of a flow accelerated feature failed because of low memory.

Recommended Action   Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.


Error Message   
%IPFLOW-2-CACHEINIT: Error initializing IP flow cache

Explanation   Initialization of the Flow cache could not be accomplished because of a low memory condition.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.


Error Message   
%IPFLOW-4-DEACTIVATE: Error deactivating feature [dec] in slot [dec]

Explanation   Deactivation of a flow accelerated feature failed because of a sanity check.

Recommended Action   Copy the message exactly as it appears and report it to your technical support representative.


Error Message   
%IPFLOW-4-DEACTIVATENOMEM: Error deactivating feature [dec]

Explanation   Deactivation of a flow accelerated feature failed because of low memory.

Recommended Action   Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.


Error Message   
%IPFLOW-2-EXPORTINIT: Error initializing Flow Export queue

Explanation   Initialization of the Flow export queue 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   
%IPFLOW-2-PROCESSINIT: Error initializing Flow background process

Explanation   Initialization of the Flow background process 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   
%IPFLOW-2-QUEUEINIT: Error initializing Flow feature queue

Explanation   Initialization of the Flow feature queue 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.

IPMCAST Error Message

Gigabit Switch Router line card IP multicast error message


Error Message   
%IPMCAST-5-ERR: [chars] [chars]=0x[hex]

Explanation   Errors occurred while processing an IP multicast packet.

Recommended Action   Copy the error message exactly as it appears on the console, 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]

Explanation   A user specified an invalid BGP community list number.

Recommended Action   Check the system configuration to ensure that the specified community list 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 the message recurs, copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.


Error Message   
%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 [int], [dec] max

Explanation   A software error occurred.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.

IP_SNMP Error Messages

Simple Network Management Protocol specific to IP error messages


Error Message   
%IP_SNMP-4-NOTRAPIP: SNMP trap source [chars] has no ip address

Explanation   The user entered an snmp-server trap-source command. The interface requested for use as the source address has no address associated with it. The SNMP trap is being sent anyway, but without the source address that the user intended.

Recommended Action   There are two possible solutions. Either enter a no snmp-server trap-source command to disable the request for a specific source IP address, or add an IP address to the interface referenced in the snmp-server trap-source configuration command.


Error Message   
%IP_SNMP-3-SOCKET: can't open UDP socket

Explanation   The SNMP server was unable to open a port for receiving or transmitting SNMP requests. This usually happens when the SNMP server is started using the snmp-server community configuration command on a router or communication server with an interface that has no IP address configured. Another possible cause is low memory.

Recommended Action   Configure at least one interface with an IP address or specify the no snmp-server command to remove the SNMP server process. Call your technical support representative if the problems persist or if it becomes necessary to add memory.


Error Message   
%IP_SNMP-4-TOOBIG: Oversize message from [int], datagram size [int], udp length [int]

Explanation   An incoming SNMP packet had a length field so large that the system had to assume it was in error. This system made a correct reaction to bad external data. Since SNMP packets should originate from systems under the same administration, this may indicate that the network host used to originate the SNMP request had a problem in its networking layer. Alternatively, if the SNMP packet originated from outside the local administrative domain, it could indicate a failed attempt at security penetration and that site should be watched more closely.

Recommended Action   If the origin is local, no action is required. If the origin is determined to be malicious, either contact the administrator of the originating site or install filters to prevent access by that site, as circumstances warrant.

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   If this message recurs, report the problem to your technical support representative, along with the output of the show px servers command taken before the message appeared and again after the message appeared.


Error Message   
%IPX-3-BADIGRPSAP: Cannot send incremental SAP update to peer on [chars]. Increasing output-sap-delay may help

Explanation   An incremental SAP update could not be sent, because this might cause the SAP tables between peers to become out of synch.

Recommended Action   Increase the output SAP delay on the listed interface to reduce buffer usage. If, after changing the delay, the message remains, 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 a SAP with a type code that 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. If possible, also provide the output of the debug ipx sap activity and debug ipx sap event commands for the period during which this message appeared.


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   Copy and save 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, copy and save the message, along with the output from the show ipx route, and call your technical support representative for assistance.


Error Message   
%IPX-6-NOVACCESSLOG: [chars] [chars] [chars] [chars] [hex].[sci_notation] [chars] [hex].[sci_notation] [dec] pkt[chars]

Explanation   If IPX access violation logging is enabled, these messages are displayed when an access list logging event has occurred.

Recommended Action   Verify that the host system is permitted or denied, as defined in the access list.


Error Message   
%IPX-3-TOOMANYNETS: Too many networks

Explanation   The limit of connected IPX networks has been reached. Additional IPX interfaces cannot be configured.

Recommended Action   Do not configure IPX on additional interfaces. Remove IPX configuration commands from inactive interfaces.

ISDN Error Messages

Integrated Services Digital Network (ISDN) error messages


Error Message   
%ISDN-6-CHAN_UNAVAILABLE: Interface [chars] Requested Channel [dec] is not available

Explanation   The requested channel is not available.

Recommended Action   This is an informational message only. No action is required.


Error Message   
%ISDN-6-CONNECT: Interface [chars] is now connected to [chars] [chars]

Explanation   This is an informational message 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.

Recommended Action   No action is required.


Error Message   
%ISDN-6-DISCONNECT: Interface [chars] disconnected from [chars] [chars], call lasted [int] seconds

Explanation   This is an informational message 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. It also shows how long the call lasted.

Recommended Action   No action is required.


Error Message   
%ISDN-4-INVALID_CALLEDNUMBER: Interface [chars], Ignoring call, LDN and Called Party Number mismatch

Explanation   The incoming ISDN call is ignored because the Called Party Number does not match the LDN numbers configured in the router.

Recommended Action   Correct the LDN in the router to match the Called Party Number delivered in the incoming setup message.


Error Message   
%ISDN-4-INVALID_EID: Interface [chars], Ignoring call, EndPoint Identifier (EID) mismatch

Explanation   The incoming ISDN call is ignored because the EID delivered in the incoming setup message cannot be matched.

Recommended Action   If EID is delivered in the setup message, use the isdn debugs and show isdn status commands to determine the current EID values. You may need to contact the service provider.


Error Message   
%ISDN-4-INVALID_SPID: Interface [chars], Spid[dec] was rejected

Explanation   The service profile identifier (SPID) configured in the router has been rejected by the switch.

Recommended Action   Determine the correct SPID, reenter the SPID and clear the BRI interface.


Error Message   
%ISDN-6-INVALID_TIMER: [chars]: Invalid Timer Handle, caller 0x[hex] handle %3d

Explanation   This message could indicate low memory. It is sent when an invalid ISDN timer handle is passed on for timer operations.

Recommended Action   Capture the show isdn memory and show isdn status output for possible debugging information. Reduce other system activity to ease the memory demands in the system.


Error Message   
%ISDN-6-LAYER2DOWN: Layer 2 for Interface [chars], TEI [int] changed to down

Explanation   This is an informational message. It is sent when an ISDN Layer 2 logical link is down. It also shows the terminal endpoint identifier (TEI) associated with this logical link.

Recommended Action   No action is required.


Error Message   
%ISDN-6-LAYER2UP: Layer 2 for Interface [chars], TEI [int] changed to up

Explanation   This is an informational message. It is sent when an ISDN Layer 2 logical link is up. It also shows the terminal endpoint identifier (TEI) associated with this logical link.

Recommended Action   No action is required.


Error Message   
%ISDN-1-NOMEMORY: msgtxt_nomemory

Explanation   The requested operation could not be accomplished because of a low-memory condition.

Recommended Action   Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.


Error Message   
%ISDN-6-NO_TIMER: No Free Timer Entry, caller 0x[hex], timers used [dec]

Explanation   This message could indicate low memory. It is sent when the ISDN protocol cannot start new timers for its operation.

Recommended Action   Capture the show isdn memory and show isdn status output for possible debugging information. Reduce other system activity to ease the memory demands in the system.


Error Message   
%ISDN-6-SETUP_PENDING: Interface [chars] Received SETUP on [dec] Channel when another SETUP is pending

Explanation   A SETUP was received on top of a pending SETUP.

Recommended Action   This is an informational message only. 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 = 0x[hex]

Explanation   An Ethernet interface is malfunctioning.

Recommended Action   Determine whether the malfunction stems from a software or hardware error by turning off all fast switching. Error messages showing that the packet is too large for the link indicate a software error at a high level. Copy the error message exactly as it appears, and report it to your technical support representative. Receiving no error messages indicates a hardware error. Repair or replace the controller.


Error Message   
%LANCE-3-BADCABLE: msgtxt_badcable

Explanation   Ethernet cable is not connected.

Recommended Action   Check Ethernet cable connection.


Error Message   
%LANCE-3-BADUNIT: msgtxt_badunit

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: msgtxt_initfail

Explanation   The hardware failed to initialize correctly.

Recommended Action   Repair or replace the controller.


Error Message   
%LANCE-5-LATECOLL: Unit [dec], late collision error

Explanation   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: msgtxt_memoryerror

Explanation   An Ethernet interface detected a hardware problem.

Recommended Action   Repair or replace the controller.


Error Message   
%LANCE-3-OWNERR: msgtxt_ownerror

Explanation   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 interrupt, csr[dec]=0x[hex]

Explanation   An Ethernet interface generated a spurious Initialization Done interrupt.

Recommended Action   Repair or replace the controller.


Error Message   
%LANCE-3-UNDERFLO: Unit [dec], underflow error

Explanation   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 long

Explanation   A name identifying a LANE component has been entered by the user that is longer than 32 characters.

Recommended Action   Re-enter a shorter name.


Error Message   
%LANE-3-BADTYPE: Inappropriate LAN type

Explanation   An unexpected LAN type has been specified for a LANE component. Only Ethernet and Token Ring ELANs are supported.

Recommended Action   Specify a valid LAN type.


Error Message   
%LANE-6-INFO: [chars]

Explanation   This is an informational message about the LANE subsystem.

Recommended Action   No action is required.


Error Message   
%LANE-3-LANE_ERROR: [chars]

Explanation   An internal error occurred, which reflects an inconsistency in the system and needs attention.

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-LEC_BADAD: [chars] LEC unable to compute ATM address

Explanation   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 nonvolatile RAM (NVRAM) configuration.


Error Message   
%LANE-3-LEC_BAD_CTL_DIST_TYPE: [chars] CTL DIST blli type wrong

Explanation   An incorrect BLLI value was specified on the incoming circuit.

Recommended Action   The originator of the circuit is not using the correct BLLI value for this type of circuit. The LANE standard defines these values, and the originator is violating the standard.


Error Message   
%LANE-3-LEC_CFG: [chars] CFG_REQ failed, [chars] (LECS returned [dec])

Explanation   The master LECS refused the LEC's configuration request.

Recommended Action   Check your LECS configurations.


Error Message   
%LANE-3-LEC_CONTROL_MSG: Received bad control message on interface [chars]

Explanation   The LANE client received an unexpected or inappropriate control message over one of its VCs.

Recommended Action   Copy the error message exactly as it appears, and report it to your technical support representative.


Error Message   
%LANE-3-LEC_ERR: [chars]

Explanation   A LANE client 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   This is an informational LANE message.

Recommended Action   No action is required.


Error Message   
%LANE-3-LEC_JOIN: [chars] JOIN failed, [chars] (LES returned [dec])

Explanation   A LANE client's request to join its ELAN was rejected.

Recommended Action   This message is usually the result of user configuration errors (such as the LANE client attempted to join an incorrect ELAN or the ELAN was not configured in the LES) or there were validation failures with the LECS.


Error Message   
%LANE-3-LEC_LISTEN: [chars] listen failed on [chars]

Explanation   The LANE client could not register its address with ATM signalling to be able to accepts calls on that address.

Recommended Action   Reconfigure the client ATM address. It may be conflicting with another component with the same ATM address.


Error Message   
%LANE-3-LEC_REGISTER: [chars] REGISTER failed, [chars] (LES returned [dec])

Explanation   An attempt to register a MAC-ATM address binding with LES failed.

Recommended Action   The LES had already registered the requested MAC address - ATM address binding.


Error Message   
%LANE-3-LECS_ERROR: [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-3-LEC_SIGNAL: Unexpected SigAPI event [dec]

Explanation   ATM signaling sent the LANE 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-6-LECS_INFO: [chars]

Explanation   This is an informational LECS message.

Recommended Action   No action is required.


Error Message   
%LANE-4-LECS_WARNING: [chars]

Explanation   The LANE Configuration Server address could not be registered with or de-registered from the switch, using Interim Local Management Interface (ILMI). The following are possible causes. The switch prefix is not available. The address is not acceptable to the switch (the prefix does not conform). The interface over which this operation should take place is down. The ILMI subsystem on the router is not completely initialized.

Recommended Action   Copy the error message exactly as it appears, and report it to your technical support representative.


Error Message   
%LANE-3-LEC_WRONG_ELAN_ID: [chars]: elan id mismatch: LECS indicates [dec], LES indicates [dec]

Explanation   The ELAN-ID returned by LES does not match the value given by LECS or by the CLI.

Recommended Action   Check the ELAN-ID configurations specified in the LECS database and the LES. The mismatch must be the result of misconfiguration.


Error Message   
%LANE-3-LES_ERROR: [chars]

Explanation   A serious internal occurred with LES/BUS.

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_ADDR: [chars] elan [chars] unable to register LES/BUS ATM addr

Explanation   A LANE server or BUS could not register its address with ILMI.

Recommended Action   Investigate why this error occurred. It may be because a user defined override address does not conform to the switch prefix, or that there is a problem with the ATM switch with whom the entity is registering.


Error Message   
%LANE-3-LSV_BADAD: [chars] elan [chars] unable to compute [chars] ATM address

Explanation   Software was unable to compute an ATM address based on the ATM address template given. The characters in [chars] 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: [chars] elan [chars] unrecoverable error [chars]

Explanation   A very serious LES/BUS 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-4-LSV_LECID: [chars] elan [chars] LECIDs exhausted

Explanation   The LANE server specified has 65,279 clients. No more can be added.

Recommended Action   Change the configurations to avoid trying to have more than 65,279 LANE clients on this server.


Error Message   
%LANE-3-NAMECHG: A LANE Client is already running here using another elan name

Explanation   Both the LANE client and the LANE server/BUS 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-bus 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-NOILMI: ILMI service registration failed

Explanation   The Interim Local Management Interface (ILMI) feature is either not included in the software image running on the router, or is having other problems.

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-NOINT: [chars] still destroying old sub-interface

Explanation   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-NOREGILMI: [chars] [chars] cannot register [ATM address] with ILMI

Explanation   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 should be examined. A likely cause is that the ATM address being registered is not compatible with the parameters configured in the switch. Correct the configuration.


Error Message   
%LANE-3-TYPECHG: A LANE Client is already running here using another elan type

Explanation   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 are configured, 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 LANE component changed its state to up or down.

Recommended Action   If this event is expected, then take no action. Otherwise, contact a technical support representative.

LANMGR Error Messages

IBM LAN Network Manager error messages


Error Message   
%LANMGR-4-BADRNGNUM: Ring number mismatch on [chars], shutting down the interface

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 the message recurs, copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.


Error Message   
%LANMGR-2-NOMEMORY: No memory available: [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   
%LANMGR-4-NORING: No ring info for [chars]

Explanation   An internal software error occurred.

Recommended Action   If the message recurs, copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.


Error Message   
%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 Cisco 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 field

Explanation   A received Frame Reject (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 Frame Reject (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 permitted

Explanation   A received Frame Reject (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 value

Explanation   A received Frame Reject (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 large

Explanation   A received Frame Reject (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

Explanation   An internal software error occurred.

Recommended Action   If either of these messages recur, call your technical support representative for assistance.


Error Message   
%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

Explanation   An internal software error occurred.

Recommended Action   If this message recurs, contact your technical support representative.


Error Message   
%LAT-3-BUFFULL: Tty[t-line], data buffer full with count [dec]

Explanation   An internal software error occurred.

Recommended Action   If this message recurs, contact your technical support representative.


Error Message   
%LAT-3-NOSYNC: Tty[t-line], Output data ptrs out of sync with byte count

Explanation   An internal software error occurred.

Recommended Action   If this message recurs, contact your technical support representative.


Error Message   
%LAT-3-NULLIDB: Null IDB pointer with destination [sci_notation]

Explanation   An internal software error occurred.

Recommended Action   If this message recurs, contact your technical support representative.


Error Message   
%LAT-3-QBSPACED: Queue block at [hex] not found for HI connection

Explanation   An internal software error occurred.

Recommended Action   If this message recurs, contact your technical support representative.


Error Message   
%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 this message recurs, contact your technical support representative.

LC Error Messages

Line card error messages


Error Message   
%LC-3-BMABUFF: [chars] BMA has [int] buffers in queue [int] when maximum of [int] are allowed

Explanation   The number of buffers in one of the BMA queues has overflowed.

Recommended Action   Copy the error message exactly as it appears, and report it to your technical support representative


Error Message   
%LC-3-BMACMDFTCH: Problem in BMA command fetching, status=[dec] [chars] BMA

Explanation   The BMA encountered problems while trying to fetch the given command. If the message appears more than once you may have a hardware problem. The GRP should recognize that communication has been lost with the line card and reload it.

Recommended Action   Copy the error message exactly as it appears, and report it to your technical support representative.


Error Message   
%LC-3-BMACMDLOST: [chars] BMA has lost a command

Explanation   The given BMA has lost a command. If the message appears more than once you may have a hardware problem. The GRP should recognize that communication has been lost with the line card and reload it.

Recommended Action   Copy the error message exactly as it appears, and report it to your technical support representative.


Error Message   
%LC-3-BMACMDRPLY: Problem in BMA reply to command type [dec] [chars] BMA sequence no=[dec]

Explanation   There was a problem in the reply to the given BMA command. If the message appears more than once you may have a hardware problem. The GRP should recognize that communication has been lost with the line card and reload it.

Explanation   Copy the error message exactly as it appears, and report it to your technical support representative


Error Message   
%LC-3-BMAERR: [chars] BMA error: msstat [hex] dma0 [hex] dma1 [hex] dma2 [hex] qm [hex] plim [hex] fia [hex] l3 [hex] ms [hex] sdram [hex]

Explanation   There is an error in the BMA (reg. information).

Recommended Action   Copy the error message exactly as it appears, and report it to your technical support representative


Error Message   
%LC-3-BMAERRS: [chars] BMA [chars] error [hex]

Explanation   There is an error in the BMA.

Recommended Action   Copy the error message exactly as it appears, and report it to your technical support representative


Error Message   
%LC-3-BMAERRSS: [chars] BMA [chars] error [hex] [chars] [hex]

Explanation   There is an error in the BMA.

Recommended Action   Copy the error message exactly as it appears, and report it to your technical support representative


Error Message   
%LC-3-BMAUCODE_GET: [chars] BMA: feature [chars], line card type [chars], could not get [chars] BMA microcode

Explanation   When the BMA microcode download command was issued, the given BMA microcode bundled in the image was not retrieved.

Recommended Action   Copy the error message exactly as it appears, and report it to your technical support representative


Error Message   
%LC-3-BMAUCODE_LCTYPE: [chars] BMA: feature [chars], specified linecard type(s) ([hex]) != current ([hex])

Explanation   When the BMA microcode download command was issued, there was a mismatch between what was specified in the BMA microcode file and the current type of line card

Recommended Action   Copy the error message exactly as it appears, and report it to your technical support representative


Error Message   
%LC-3-BMAUCODE_NULL: Null downloaded BMA microcode

Explanation   When the BMA microcode download command was issued, the given BMA microcode bundled in the image was not retrieved because it is null.

Recommended Action   Copy the error message exactly as it appears, and report it to your technical support representative


Error Message   
%LC-3-CARVE_BUFHDRS: [chars] BMA: out of SDRAM buffer headers

Explanation   The system ran out of available SDRAM buffer headers while attempting to carve buffers. This could be a cause of SDRAM buffer carve failure.

Recommended Action   Copy the error message exactly as it appears, and report it to your technical support representative


Error Message   
%LC-3-CARVE_BUFSIZE: [chars] BMA: illegal specified/real SDRAM buffer size(s) = ([unsigned long],[unsigned long]). Range=([dec],[dec])

Explanation   The calculated SDRAM buffer size (in bytes, including header and data portions) is not within the given range. This could be a cause of SDRAM buffer carve failure.

Recommended Action   Copy the error message exactly as it appears, and report it to your technical support representative.


Error Message   
%LC-3-CARVE_EXBUFS: [chars] BMA: [int] SDRAM buffers > max ([int])

Explanation   The maximum number of SDRAM buffer headers is limited to a maximum number that has been exceeded. This could be a cause of SDRAM buffer carve failure.

Recommended Action   Copy the error message exactly as it appears, and report it to your technical support representative.


Error Message   
%LC-3-CARVE_EXFREEQS: [chars] BMA: [int] free queues > max ([int])

Explanation   The number of free queues allowed for SDRAM buffer carving has been exceeded. This could be a cause of SDRAM buffer carve failure.

Recommended Action   Copy the error message exactly as it appears, and report it to your technical support representative.


Error Message   
%LC-3-CARVE_EXPCT: [chars] BMA: [int] sum SDRAM buffer percentages > 100

Explanation   The sum of percentages per SDRAM buffer size has exceeded 100. This could be a cause of SDRAM buffer carve failure.

Recommended Action   Copy the error message exactly as it appears, and report it to your technical support representative.


Error Message   
%LC-3-CARVE_EXSDRAM: [chars] BMA: used SDRAM ([unsigned long long] bytes) > available for carve ([unsigned long] bytes)

Explanation   The calculated sum of SDRAM to be carved is larger than the available SDRAM for carving. This could be a cause of SDRAM buffer carve failure.

Recommended Action   Copy the error message exactly as it appears, and report it to your technical support representative.


Error Message   
%LC-4-CARVE_JVMASK: [chars] BMA: suspect return value [dec] on quiesce-for-carve

Explanation   The BMA quiesce-for-carve algorithm retrieved a bad jump vector mask return value. This message could indicate an error in the quiesce.

Recommended Action   Copy the error message exactly as it appears, and report it to your technical support representative.


Error Message   
%LC-3-CARVE_NOFREEQS: [chars] BMA: no more free queues

Explanation   There are no more available free queues that can be used for SDRAM buffer carve. This could be a cause of SDRAM buffer carve failure.

Recommended Action   Copy the error message exactly as it appears, and report it to your technical support representative.


Error Message   
%LC-3-CARVE_PARMS: [chars] BMA: >= 1 SDRAM bufmem parameters == 0

Explanation   This is an internal parameter error with one or more SDRAM buffer memory parameters: maximum buffer header count or SDRAM sizes (total, not available for carve, and available for carve).

Recommended Action   Copy the error message exactly as it appears, and report it to your technical support representative.


Error Message   
%LC-3-CARVE_QELEM: [chars] BMA: [int] Queue Manager SRAM elements > max ([int])

Explanation   The system ran out of Queue Manager elements, which are used for SDRAM buffer carving. This could be a cause of SDRAM buffer carve failure.

Recommended Action   Copy the error message exactly as it appears, and report it to your technical support representative.


Error Message   
%LC-3-CARVE_QMREAD: BMA address [hex]: Queue Manager SRAM [hex], read error(s)

Explanation   An error occurred during Queue Manager SRAM initialization. Reading one or more zeroed Queue Manager SRAM locations gave a non-zero result. Possible errors could be in head, tail, length, length threshold, buffer address, next queue element, or scratch RAM locations.

Recommended Action   Copy the error message exactly as it appears, and report it to your technical support representative.


Error Message   
%LC-4-CARVE_TIME: [chars] BMA: quiesce-for-carve exceeded timeout ([dec] ms) in [chars] loop, [dec] times

Explanation   The BMA quiesce-for-carve algorithm waits an allotted time for line card queues to flush. One or more waits exceeded this allotted time. These queues are specific to the line card's ASICs. This error message might not actually indicate an error, but that the allotted time might not be sufficient and should be increased.

Recommended Action   Copy the error message exactly as it appears, and report it to your technical support representative.


Error Message   
%LC-3-DOWNREV: BMA is an old version.

Explanation   The system software detected an old version of the BMA.

Recommended Action   Call your technical support for an upgraded version.


Error Message   
%LC-3-INIT_CARD_TYPE: Unknown card type (0x[hex])

Explanation   A card was either manufactured improperly, failed, or is newer than the software.

Recommended Action   Replace the card or upgrade the software.


Error Message   
%LC-3-INIT_MEM: Memory failure, addr [hex], read [hex][hex], not [hex][hex]

Explanation   Initialization of the memory address failed.

Recommended Action   Copy the error message exactly as it appears, and report it to your technical support representative.


Error Message   
%LC-3-INIT_READ: Error reading memory at 0x[hex]

Explanation   The given memory location could not be read.

Recommended Action   Copy the error message exactly as it appears, and report it to your technical support representative.


Error Message   
%LC-3-INIT_RESET: Failed to take line card out of reset

Explanation   Initialization of the line card I/O registers failed.

Recommended Action   Copy the error message exactly as it appears, and report it to your technical support representative.


Error Message   
%LC-3-INIT_ZERO: No bytes to write to location 0x[hex]

Explanation   No bytes were written to the given location.

Recommended Action   Copy the error message exactly as it appears, and report it to your technical support representative.


Error Message   
%LC-3-INVQ: Invalid local output queue: [hex] [hex] [hex] [hex] [hex] [hex]

Explanation   The above packet was routed to an invalid queue. The data shown is the packet header.

Recommended Action   Copy the error message exactly as it appears, and report it to your technical support representative.


Error Message   
%LC-3-L3FEERR: L3FE error: rxbma [hex] addr [hex] txbma [hex] addr [hex] dram [hex] addr [hex] io [hex] addr [hex]

Explanation   An error occurred in the line card's L3FE ASIC (reg. information).

Recommended Action   Copy the error message exactly as it appears, and report it to your technical support representative


Error Message   
%LC-3-L3FEERRS: L3FE [chars] error [hex] address [hex]

Explanation   An error occurred in the line card's L3FE ASIC.

Recommended Action   Copy the error message exactly as it appears, and report it to your technical support representative


Error Message   
%LC-3-LC_CODE_DLD_ALLOC: Failed buffer allocation for code download

Explanation   The system could not allocate a data buffer to contain contents of the given line card file that was downloaded. There may be insufficient DRAM.

Recommended Action   Copy the error message exactly as it appears, and report it to your technical support representative.


Error Message   
%LC-3-LC_CODE_DLD_CHKSUM: code download IPC data checksum error

Explanation   For the GLC code download command, the checksum verification failed.

Recommended Action   Copy the error message exactly as it appears, and report it to your technical support representative


Error Message   
%LC-3-LC_CODE_PROG: no downloaded code to program

Explanation   For the GLC code program command, there is no downloaded code to program.

Recommended Action   Copy the error message exactly as it appears, and report it to your technical support representative


Error Message   
%LC-3-SELECTOR: [dec]: unknown BMA selector value

Explanation   An unknown BMA selector value was encountered.

Recommended Action   Copy the error message exactly as it appears, and report it to your technical support representative.


Error Message   
%LC-1-TESTALERT: [chars]

Explanation   This is test message for a software test.

Recommended Action   Stop issuing the test gsr logger command.


Error Message   
%LC-2-TESTCRIT: [chars]

Explanation   This is test message for a software test.

Recommended Action   Stop issuing the test gsr logger command.


Error Message   
%LC-7-TESTDEBUG: [chars]

Explanation   This is test message for a software test.

Recommended Action   Stop issuing the test gsr logger command.


Error Message   
%LC-0-TESTEMERG: [chars]

Explanation   This is test message for a software test.

Recommended Action   Stop issuing the test gsr logger command.


Error Message   
%LC-3-TESTERR: [chars]

Explanation   This is test message for a software test.

Recommended Action   Stop issuing the test gsr logger command.


Error Message   
%LC-6-TESTINFO: [chars]

Explanation   This is test message for a software test.

Recommended Action   Stop issuing the test gsr logger command.


Error Message   
%LC-5-TESTNOTICE: [chars]

Explanation   This is test message for a software test.

Recommended Action   Stop issuing the test gsr logger command.


Error Message   
%LC-4-TESTWARNING: [chars]

Explanation   This is test message for a software test.

Recommended Action   Stop issuing the test gsr logger command.

LCCEF Error Messages

ATM Cisco Express Forwarding (CEF) adjacency error messages


Error Message   
%LCCEF-3-MACSTR: adjacency ([chars]) has incorrect high word (0x[hex]) in its mac string

Explanation   The line card CEF received an adjacency with the incorrect mac rewrite string. Packets forwarded to that adjacency will be dropped.

Recommended Action   Copy the error message exactly as it appears, and report it to your technical support representative.


Error Message   
%LCCEF-3-OUTINFO: adjacency ([chars]) has incorrect output_info (0x[hex]) field

Explanation   The line card CEF received an adjacency with the incorrect output_info field. Packets forwarded to that adjacency will be dropped.

Recommended Action   Copy the error message exactly as it appears, and report it to your technical support representative.

LCCOREDUMP Error Messages

Line card core dump error messages


Error Message   
%LCCOREDUMP-3-BADCLOSE: Can't close slave core socket for slot [dec]

Explanation   The system just finished dumping a core file from a line card. It tried to close this file on the remote system and failed.

Recommended Action   Debug network connections and user privileges.


Error Message   
%LCCOREDUMP-3-BADOPEN: Can't open slave core socket for slot [dec]

Explanation   The system wants to dump a core file to a remote system, but it is unable to open the remote file.

Recommended Action   Ensure that the remote system is accessible and the protocol is set up correctly.


Error Message   
%LCCOREDUMP-3-BADWRITE: Can't write [chars] to slave core socket for slot [dec]

Explanation   The system is trying to write a core dump file to a remote system. The file was opened, and an error occurred during a write to the file.

Recommended Action   Check network and disk space available.


Error Message   
%LCCOREDUMP-2-EOM: Cannot allocation memory for [chars]

Explanation   The system cannot allocate memory for the coredump subsystem.

Recommended Action   Add more memory.


Error Message   
%LCCOREDUMP-3-ILLNVGEN: Illegal call to bflc_cfg_coredump_nvgen

Explanation   The NVGEN routine was called, but NVGEN was not set.

Recommended Action   Gather information about the processes running on this GSR, including the traceback, and file a bug.


Error Message   
%LCCOREDUMP-3-ILLPAK: Coredump packet received from slot [dec] (not in dump state)
0x[hex] 0x[hex] 0x[hex] 0x[hex]
0x[hex] 0x[hex] 0x[hex] 0x[hex]
0x[hex] 0x[hex] 0x[hex] 0x[hex]
0x[hex] 0x[hex] 0x[hex] 0x[hex]

Explanation   The RP received a core dump packet from a line card that should not be dumping core.

Recommended Action   Gather information about the state of the line cards and file a bug.


Error Message   
%LCCOREDUMP-3-ILLTD: Testdump only valid on line cards (not allowed on RPs)

Explanation   You cannot run a line card coredump test for an RP.

Recommended Action   Do not run a line card coredump test for an RP.


Error Message   
%LCCOREDUMP-6-LERP: Cannot configure linecard exceptions for [chars] RP

Explanation   The exception linecard commands can only be used to configure exceptions on a line card. Configuring RP linecard exceptions is not allowed.

Recommended Action   Use the exception command without linecard to configure RP core dumps.


Error Message   
%LCCOREDUMP-3-NOMCP: Cannot malloc memory for mbus core dump message to slot [dec]

Explanation   The system is trying to write a core dump file to a remote system. It could not allocate memory to create the message that starts the dump on the line card.

Recommended Action   Add memory.


Error Message   
%LCCOREDUMP-4-NOMDD: [chars] core dump for slot [dec] (Cannot modify during dump)

Explanation   The system is currently dumping a core file for this line card. You cannot modify core dump configuration during a dump.

Recommended Action   Wait for the core dump to finish.


Error Message   
%LCCOREDUMP-3-NOPAK: No packet on queue (0x[hex] [dec])

Explanation   The RP received a core dump packet from a line card that the should not be dumping core.

Recommended Action   Gather information about the state of the line cards and file a bug.


Error Message   
%LCCOREDUMP-3-NOPROC: Unable to create data handler process

Explanation   The system wants to write a core dump file to a remote system but it is unable to start a process to dump the file.

Recommended Action   Gather information about the number of processes running, including the amount of memory in the system, and file a bug.


Error Message   
%LCCOREDUMP-3-NOQUEUE: Cannot create queue to receive dump packets for slot [dec]

Explanation   The system is trying to write a core dump file to a remote system. It could not create a queue to hold dump data coming from the line cards.

Recommended Action   Add memory.


Error Message   
%LCCOREDUMP-4-TIMEOUT: [chars] (0x[hex] [dec])

Explanation   The system is trying to write a core dump file, but the RP timed out while waiting for data from the line card.

Recommended Action   Gather information about the line card and file a bug.

LCINFO Error Messages

Line card information error messages


Error Message   
%LCINFO-3-CRASH: Line card in slot [int] crashed

Explanation   The line card in the indicated slot crashed and sent a CRASH_START message to the RP. The RP is now waiting for the rest of the crash information from the line card to be sent via the MBUS (stack trace, context, version, and so forth). This should happen in a few milliseconds after receiving the CRASH_START message. The RP software has not otherwise been notified of the line card crash---that will happen after all the crash information has been sent to the RP. In the unlikely event that the subsequent crash information messages are not received by the RP within a reasonable time limit (perhaps 10 seconds), the RP will print a TIMEOUT error message indicating such and tell the rest of the RP software that the line card has crashed.

Recommended Action   Report this defect with as much information about the line card as possible, including the output of the show context summary, show context slot, and show tech-support commands, as well as the show tech-support command output from the RP.


Error Message   
%LCINFO-3-INVDEV: Invalid line card number in MBUS callback (LC=[int])

Explanation   The line card crash information subsystem on the RP was called from the MBUS subsystem with an invalid DEVICE identifier. The DEVICE in this case is supposed to be the slot number of the line card, but it was out of range. This indicates a software defect in the system.

Recommended Action   Report this defect with as much information about the MBUS subsystem as possible. There is no adverse effect to the RP---it ignores the bad callback and continues. If the problem persists, reboot the router. It is unlikely but possible that the problem is the result of bad MBUS hardware somewhere in the system (most likely the RP MBUS module).


Error Message   
%LCINFO-3-INVSTATE: Line card crash server in bad state (LC=[int],state=[int])

Explanation   The line card crash information subsystem for the line card indicated it is in an unknown state. This is because of a software defect in that subsystem.

Recommended Action   Report this defect with as much information about the MBUS subsystem and the line card crash information subsystem as possible.


Error Message   
%LCINFO-3-NOBUF: Could not malloc line card crash structures on RP (size=[int])

Explanation   The RP could not allocate memory for line card crash data structures at startup time. By itself, this is not a serious problem, but the underlying memory shortage at startup time will probably prevent the router from running well, if at all.

Recommended Action   Debug the memory shortage problem and add more memory if necessary.


Error Message   
%LCINFO-3-NOBUFLC: Could not malloc line card crash info buffer on RP (LC=[int],bufnum=[int],size=[int])

Explanation   The RP could not allocate memory for one or more buffers to hold line card crash information at startup time. By itself, this is not a serious problem, but the underlying memory shortage at startup time will probably prevent the router from running well, if at all.

Recommended Action   Debug the memory shortage problem and add more memory if necessary. Possibly reduce the size of or the number of crash information buffers allocated per line card to hold crash information. (As of this writing, it is not known whether the size or number will be configurable.)


Error Message   
%LCINFO-3-NOPROCESS: Failed creating line card complete process

Explanation   When creating the crash complete process for the crash information subsystem, the create_process call failed. The failure is probably because of a software defect or hardware failure and should only occur during initialization.

Recommended Action   Reboot the system. If the condition persists on subsequent reloads of the system, a bug should be filed and the system should be reloaded with a different image.


Error Message   
%LCINFO-3-TIMEOUT: Timeout waiting for crash info from slot [int]

Explanation   The crash information complete timer expired. When a line card crashes, it sends information to the RP for debugging and analysis. When the START OF CRASH message is received, a timer is set for approximately 10 seconds. The line card has 10 seconds to send all the crash information to the RP. This is not a crash dump---it is a small amount of information that usually includes context, stack trace, and so forth. It is less than 8K bytes of information. If an END OF CRASH information message is not received before the timer goes off, the crash information record is closed (containing partial information), this message is displayed, and the rest of the system is notified that the line card crashed (at which point it is probably reloaded). If the line card sends more crash information after the timer goes off and before the system resets the line card, additional UNXMSG error messages might be displayed.

Recommended Action   No action is required specifically because this message was displayed; however, because the line card crashed, there might be other defects to report. If this message is seen without a line card crashing, report this message and the output of the show tech-support on the RP and on the line card that did not crash but was mentioned in this error message.


Error Message   
%LCINFO-4-TRUNC: Crash record ([int]=[chars]) truncated (expected=[int],actual=[int])

Explanation   A line card crashed and sent crash information to the RP. The RP received a CRASH RECORD START message that indicated the data would be so many bytes long. Before that amount of bytes were received, the RP received another CRASH RECORD START message indicating the start of another record. The current record is marked as truncated, and the next record is received, but the anomaly is noted in this error message. This is a problem, but because what started this process was a line card crashing, this might only be a symptom of another underlying problem.

Recommended Action   Report this defect with as much information about the MBUS subsystem and the line card crash information subsystem as possible.


Error Message   
%LCINFO-4-UNXMSG: Unexpected crash info msg type ([chars]) in state [chars] (LC=[int])

Explanation   The line card crash information subsystem received an unexpected message for the state it is in. The state and message type are given in the error message. This does not have any adverse effect on the RP since it ignores and/or recovers from this occurrence. The sender of this message is a line card that is crashing. The source of the crash on the line card is more interesting. If this occurs without a line card crash, it is because of a stray/errant MBUS message that should be pursued. This problem could also be the result of a dropped MBUS message.

Recommended Action   Find the source of the crash on the line card if one was crashing when the message occurred. If no line card crashed, report this defect with as much information about the MBUS subsystem and the line card crash information subsystem as possible. If this message recurs, reboot the router to remove this message.

LCLOG Error Messages

Line card log error messages


Error Message   
%LCLOG-3-INVDEV: Invalid line card number in MBUS callback (LC=[int])

Explanation   The line card crash info subsystem on the RP was called from the MBUS subsystem with an invalid DEVICE identifier. The DEVICE in this case is supposed to be the slot number of the line card, but it was out of range. This indicates a software defect in the system.

Recommended Action   Report this defect with as much information about the MBUS subsystem as possible. There is no adverse effect to the RP---it ignores the bad callback and continues. If the problem recurs, reboot the router. It is unlikely but possible that the problem is because of bad MBUS hardware somewhere in the system (most likely the RP MBUS module).


Error Message   
%LCLOG-3-INVSTATE: LC logger in bad state (LC=[int],state=[chars],msg=[chars])

Explanation   The line card logger subsystem for the indicated line card is not in the state expected for the message it received. This is probably because of a software defect in that subsystem. This message could also be caused by a dropped MBUS message.

Recommended Action   Report this defect with as much information about the MBUS subsystem and the line card logger subsystem as possible.


Error Message   
%LCLOG-3-MSGGIANT: LC log msg larger than max allowed (LC=[int],length=[int])

Explanation   The RP part of the line card logger server has received a log start message that is larger than the maximum log buffer allows. This is probably caused by a software defect.

Recommended Action   Report this defect with as much information about the MBUS subsystem and the line card logger subsystem as possible.


Error Message   
%LCLOG-3-MSGTOOBIG: LC log msg longer than expected (LC=[int],len=[int],exp=[int])

Explanation   The RP part of the line card logger server received more text for a message than the start message indicated. This is probably caused by a software defect.

Recommended Action   Report this defect with as much information about the MBUS subsystem and the line card logger subsystem as possible.


Error Message   
%LCLOG-3-OVERFLOW: LC log msg longer than msg buffer (LC=[int],len=[int],max=[int])

Explanation   The RP part of the line card logger server received more text for a message than will fit in the message log buffer. This is probably caused by a software defect.

Recommended Action   Report this defect with as much information about the MBUS subsystem and the line card logger subsystem as possible.

LCPLIM Error Messages

Line Card Physical Layer Interface Module error messages


Error Message   
%LCPLIM-2-BADIDB: PLIM interface idb incorrect, [hex]

Explanation   A NULL POS line card instance was found.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log. Issue the execute-on slot number show controller command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the execute-on slot number show controller output, call your Cisco technical support representative and provide the representative with the gathered information.


Error Message   
%LCPLIM-2-BADINTERFACE: Out of range LC interface, [dec] on slot [dec]

Explanation   The number of interfaces exceeds the maximum limit for this line card.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log. Issue the show version, show gsr, show diags, show interfaces, execute-on slot number show controller, and execute-on slot number show subsys commands to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the output of these commands, call your Cisco technical support representative and provide the representative with the gathered information.


Error Message   
%LCPLIM-3-UNDEFCMD: Interface [dec]: unsupported [chars] command =0x[hex]

Explanation   Undefined command received for this interface

Recommended Action   Copy the error message exactly as it appears on the console or in the system log. Issue the show ipc status command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show ipc status output, call your Cisco technical support representative and provide the representative with the gathered information.


Error Message   
%LCPLIM-2-UNDEFPLIM: Undefined PLIM type [dec] in slot [dec]

Explanation   An undefined GSR card type was found.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log. Issue the show version, show gsr, show diags, show interfaces, and execute-on slot number show subsys commands to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the output of these commands, call your Cisco technical support representative and provide the representative with the gathered information.

LCPOS Error Messages

Line Card Packet-Over-SONET error messages


Error Message   
%LCPOS-3-BMAENG: [chars] POS, [chars] [chars][chars]. (src=0x[hex], det1=0x[hex], det2=0x[hex])

Explanation   POS BMA engine hardware errors occurred.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log. Run diagnostics on the line card in the indicated slot. If diagnostics pass, call your Cisco technical support representative and provide the representative with the gathered information.


Error Message   
%LCPOS-3-BMAPAR: [chars] POS, [chars]. BMA_DATA[3:0]=0x[hex]. (src=0x[hex], det1=0x[hex], det2=0x[hex])

Explanation   A parity error occurred on the POS ASIC BMA engine.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log. Run diagnostics on the line card in the indicated slot. If diagnostics pass, call your Cisco technical support representative and provide the representative with the gathered information.


Error Message   
%LCPOS-1-INITFAIL: LCPOS([dec]/[dec]), initialization timeout failure

Explanation   The line card POS ASIC and framer initialization failed.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log. If you cannot determine the nature of the error from the error message text, call your Cisco technical support representative and provide the representative with the gathered information.


Error Message   
%LCPOS-3-LINKBADEVT: Unexpected event woke up LC POS link process.

Explanation   The line card POS link report process received an unexpected event.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log. Issue the show subsys command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show subsys output, call your Cisco technical support representative and provide the representative with the gathered information.


Error Message   
%LCPOS-3-LINKNOPRC: LCPOS, lcpos_add_process: Unable to create lcpos_link_report process

Explanation   The line card POS link report process cannot be created.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log. Issue the show subsys command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show subsys output, call your Cisco technical support representative and provide the representative with the gathered information.


Error Message   
%LCPOS-3-LINKPROC: LCPOS, lcpos_link_report process: Could not get argument

Explanation   The line card POS link report process stopped working.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log. Issue the show subsys and show memory summary commands to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the output from these commands, call your Cisco technical support representative and provide the representative with the gathered information.


Error Message   
%LCPOS-3-POSENG: [chars] POS, [chars]. [chars], port [dec]. (src=0x[hex], det1=0x[hex], det2=0x[hex])

Explanation   POS engine hardware errors occurred.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log. Run diagnostics on the line card in the indicated slot. If diagnostics pass, call your Cisco technical support representative and provide the representative with the gathered information.


Error Message   
%LCPOS-3-RXPOSTO: LCPOS([dec]/[dec]), RX POS engine shutdown failed

Explanation   The software was trying to shutdown the Rx POS engine. The POS engine refused to shutdown and the software timed out.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log. Run diagnostics on the line card in the indicated slot. If diagnostics pass, issue the execute-on slot number show controller pos registers command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the output of this command, call your Cisco technical support representative and provide the representative with the gathered information.


Error Message   
%LCPOS-3-SRAMPAR: [chars] POS, [chars]. [chars]=0x[hex][chars]. (src=0x[hex], det1=0x[hex], det2=0x[hex])

Explanation   A parity error occurred on POS ASIC SRAM.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log. Run diagnostics on the line card in the indicated slot. If diagnostics pass, call your Cisco technical support representative and provide the representative with the gathered information.


Error Message   
%LCPOS-3-TXPOSTO: LCPOS([dec]/[dec]), TX POS engine shutdown failed

Explanation   The software was trying to shutdown the Tx POS engine. The POS engine refused to shutdown and the software timed out

Recommended Action   Copy the error message exactly as it appears on the console or in the system log. Run diagnostics on the line card in the indicated slot. If diagnostics pass, issue the execute-on slot number show controller pos registers command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the output of this command, call your Cisco technical support representative and provide the representative with the gathered information.

LES_FDDI Error Message

LAN Emulation Server/Fiber Distributed Data Interface error message


Error Message   
%LES_FDDI-2-ILLEGAL: msgtxt_fddi_illegal

Explanation   The router does not have enough I/O memory to support a FDDI interface. The FDDI interface requires at least 4MB of I/O memory.

Recommended Action   Install the required amount of I/O memory. For maximum performance, Cisco recommends installing 8Mb of I/O memory for a single FDDI NIM, and 16MB of I/O memory if 2 FDDI NIMs are installed. With 4MB of I/O memory the system will create 256 FDDI buffers for one FDDI interface or 384 buffers for two FDDI interfaces. With 8MB of I/O memory the system will create 512 FDDI buffers for either one or two FDDI interfaces. With 16MB of I/O memory the system will create 512 FDDI buffers for one FDDI interface or 1024 buffers for two FDDI interfaces.

LEX Error Messages

LAN extension error messages


Error Message   
%LEX-3-NOTSENT: Serial line down, [chars] : [chars] not sent

Explanation   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 Extender

Explanation   The LAN Extender could not process the command from the host router. Possible causes are as follows. The LAN Extender ran out of memory. The message from the host router is malformed. A request to write Flash memory occurred while the LAN Extender was busy writing Flash memory for a previous request. The size of a file to be downloaded is greater than the amount of Flash memory available.

Recommended Action   If the command was copy tftp lex unit-number or copy flash lex unit-number, ensure that the correct file (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 Extender

Explanation   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   No action is 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 on the console or in the system log, and report it to your Cisco technical support representative.


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 on the console or in the system log, and report it to your Cisco technical support representative.


Error Message   
%LINK-4-BADQID: Interface [chars], bad output queue ID specified ([dec]) Packet dropped

Explanation   An internal software error occurred.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.


Error Message   
%LINK-2-BADVCALL: Interface [chars], undefined entry point

Explanation   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   Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.


Error Message   
%LINK-6-BERTSTATUS: Interface [chars], [chars]

Explanation   BERT is completed for this interface.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.


Error Message   
%LINK-3-BOGUSENCAP: msgtxt_badencap

Explanation   A serial interface has been configured with an unknown encapsulation.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.


Error Message   
%LINK-5-BOOTP: [chars] address [int], resolved by [int]

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   Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.


Error Message   
%LINK-4-BRIDGECONFLICT: Interface [chars], encapsulated BPDU recvd from [sci_notation]

Explanation   An FCIT running in nonencapsulating transparent mode detected an FDDI bridge running in encapsulation mode on the same fiber. This is an unstable situation and should be corrected. The incoming interface is displayed, along with the FDDI MAC address in 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 Cisco technical support representative.


Error Message   
%LINK-5-CHANGED: Interface [chars], changed state to [chars]

Explanation   The interface hardware changed state.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.


Error Message   
%LINK-3-COMPREG: Interface [chars], non-existent (de)compression registry. Packet dropped

Explanation   A software or hardware error occurred.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.


Error Message   
%LINK-3-EMPTYPAK: Interface [chars], empty packet dequeued; linktype [dec], queue [dec]

Explanation   An internal software error occurred.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.


Error Message   
%LINK-4-FDDISTAT: Interface [chars], FDDI state [chars] detected

Explanation   A state change occurred on the FDDI ring.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.


Error Message   
%LINK-3-IDBLISCRE: Unable to create [chars] interface list

Explanation   An internal software error occurred.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.


Error Message   
%LINK-3-IDBLISINS: Not able to insert interface [chars] into [chars] list

Explanation   An internal software error occurred.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.


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 on the console or in the system log, and report it to your Cisco technical support representative.


Error Message   
%LINK-5-LOOPSTATUS: Interface [chars], [chars]

Explanation   The interface entered or exited loopback.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.


Error Message   
%LINK-4-NOMAC: A random default MAC address of [sci_notation] has been chosen. Ensure 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.

Explanation   An addressing inconsistency occurred.

Recommended Action   Ensure 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

Explanation   An internal software error occurred.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.


Error Message   
%LINK-5-RARP: [chars] address [int], resolved by [int]

Explanation   The Reverse Address Resolution Protocol (RARP) resolved an IP address.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.


Error Message   
%LINK-5-REMLOOP: Interface [chars], remote loop [chars] [chars]

Explanation   The interface entered or exited a remote loopback.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.


Error Message   
%LINK-5-SLARP: [chars] address [int], resolved by [int]

Explanation   The Serial Line Address Resolution Protocol (SLARP) resolved an IP address.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.


Error Message   
%LINK-4-TOOBIG: Interface [chars], Output packet size of [dec] bytes too big

Explanation   An internal software error occurred.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.


Error Message   
%LINK-3-TOOSMALL: Interface [chars], Output runt packet of [dec] bytes

Explanation   An output packet was detected that was smaller than the minimum allowable datagram size. An error in another driver or an error in the system software probably triggered this error message.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.


Error Message   
%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 Message

Logical Link Control, type 2 error message


Error Message   
%LLC-2-UNEXPECT: LLC2: [chars] UNEXPECTED EVENT

Explanation   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 re-creating the error and call your technical support representative.

LLIST Error Messages

Linked list facility error messages


Error Message   
%LLIST-3-OFFLIST: [chars] from 0x[hex], 0x[hex] not on list

Explanation   An internal inconsistency was detected when an attempt was made to remove an item from a list not on the list.

Recommended Action   Copy the message exactly as it appears and report it to your technical service representative.


Error Message   
%LLIST-3-ONLIST: [chars] to 0x[hex], 0x[hex] on list

Explanation   An internal inconsistency was detected when an attempt was made to add an item to a list already on the list.

Recommended Action   Copy the message exactly as it appears and report it to your technical service representative.

LNMC Error Messages

LAN network manager system error messages


Error Message   
%LNMC-3-BADCLSI: [chars] primitive not valid for lnm [chars] [chars]

Explanation   A LAN network manager system error occurred.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.


Error Message   
%LNMC-3-BADCLSICNF: [chars] Invalid confirm [chars] [chars]

Explanation   A LAN network manager system error occurred.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.


Error Message   
%LNMC-3-BADCLSIDATALEN: [chars] Bad data len = [dec] [chars]

Explanation   A LAN network manager system error occurred.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.


Error Message   
%LNMC-3-BADCLSIHDRLEN: [chars] Bad header len = 0x[hex] [chars]

Explanation   A LAN network manager system error occurred.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.


Error Message   
%LNMC-3-BADCLSIIDTYPE: [chars] Invalid ID type = 0x[hex] [chars]

Explanation   A LAN network manager system error occurred.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.


Error Message   
%LNMC-3-BADCLSIIND: [chars] Invalid indication [chars], [chars]

Explanation   A LAN network manager system error occurred.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.


Error Message   
%LNMC-3-BADCLSIPRIMTYPE: [chars] Invalid primitive type = 0x[hex] [chars]

Explanation   A LAN network manager system error occurred.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.


Error Message   
%LNMC-3-BADCLSIRET: [chars] Invalid ret code (0x[hex]) [chars], [chars]

Explanation   A LAN network manager system error occurred.

Recommended Action   Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.


Error Message   
%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 on the console or in the system log, and report it to your Cisco 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 convert

Explanation   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.


hometocprevnextglossaryfeedbacksearchhelp
Copyright 1989-1998 © Cisco Systems Inc.