-
Cisco IOS Release 12.0 System Message Guide
-
About the Cisco IOS Software Documentation
-
System Error Messages Overview
-
AAAA through APPN
-
ARAP through C1600
-
C2600 through CT3
-
DBCONN through FILESYS
-
FPGA through IPC_RSP_CBUS
-
IPFAST through LPD
-
M32X through NHRP
-
NIC100 through RTT
-
S4T68360 through SWITCH
-
SYS through TI1570
-
TIB through XCPA
-
CMCC-ADAPTER through CMCC-IPC_DRVR
-
CMCC-LOADER through CMCC-XCPA
-
System Failure Error Messages
-
Table Of Contents
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-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-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.
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