|
|
The following are error messages for the Binary API for the interface descriptor block.
Error Message
%INTERFACE_API-4-BADPAKINPUT: pak->if_input is not initializedExplanation An internal software error has 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
%INTERFACE_API-4-BADPAKOUTPUT: pak->if_output is not initializedExplanation An internal software error has 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
%INTERFACE_API-4-BADPOINTER: Function [chars] detected an invalid [chars] pointer of %08lX, ignoringExplanation A software error has occurred. This message is displayed when an invalid pointer is detected.
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 command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%INTERFACE_API-4-BADSWIDB: [chars] may not be referencing the correct swidbExplanation An internal software error has 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
%INTERFACE_API-1-NOMORESWIDB: No more SWIDB can be allocated, maximum allowed [dec]Explanation No more interfaces can be created because the maximum number of SWIDB allowed for this platform has been reached.
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.
The following are I/O card-specific error messages.
Error Message
%IOCARD-3-IONOT0: IO card discovered in nonzero slot [dec]Explanation An I/O card was detected in a nonzero slot.
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
%IOCARD-3-UNSUPPORTED: [chars] in slot[dec] is not supported on [chars] chassisExplanation The software identified and disabled the Fast Ethernet (FE) on the I/O card.
Recommended Action No action is required.
The following are Internet Protocol (IP) error messages.
Error Message
%IP-5-ACL: [chars]Explanation An error has occurred during the IP access check.
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 command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%IP-3-BADIPALIGN: Invalid alignment in packet for IP. [chars]=[hex]Explanation The packet data structure is misaligned. This condition may result in a small amount of overhead in processing IP traffic.
Recommended Action Enter the show hardware command and report the output, along with this error message, to your Cisco technical support representative.
Error Message
%IP-3-BADSROUTE: Improper source route. Length [dec] Ptr [dec]Explanation A hardware or software error has 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
%IP-4-CLASS: Bad IP address and mask [int][inet] in class_resolve()Explanation An internal software error has 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
%IP-3-CNTRFULL: IP counter block is full (setting protocol [dec])Explanation An internal software error has 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 command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%IP-3-DESTHOST: src=[int], dst=[int], NULL desthostExplanation An internal software error has 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
%IP-4-DUPADDR: Duplicate address [int] on [chars], sourced by [sci_notation]Explanation Another system is using your IP address.
Recommended Action Change the IP address of one of the two systems.
Error Message
%IP-3-LOOPPAK: Looping packet detected and dropped - src=[int], dst=[int], hl=[int], tl=[int], prot=[int], sport=[int], dport=[int] in=[chars], nexthop=[int], out=[chars]options=[chars]Explanation A software error has 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
%IP-4-UNICASTRPF: IP unicast reverse-path check disabled on [chars]Explanation The IP Verify Unicast Reverse-Path Feature was disabled because Cisco express forwarding (CEF) was disabled either through configuration or because of an internal error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%IP-5-WEBINST_COMP: Selected IP address [int]Explanation A hardware or software error has 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
%IP-5-WEBINST_KILL: Terminating DNS processExplanation A hardware or software error has 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
%IP-5-WEBINST_RESP: Sending DNS response to [int] (request was for [int])Explanation A hardware or software error has 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
%IP-5-WEBINST_START: Attempting web install from host [int]Explanation A hardware or software error has 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
%IP-4-ZERO_ADDR: Zero MAC address for [int] in ARP cacheExplanation An entry in the ARP cache has a null MAC address.
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.
The following are IP security error messages.
Error Message
%IPACCESS-2-NOMEMORY: Alloc fail for acl-config buffer. Disabling distributed mode on lcExplanation A buffer could not send access-list configuration down to line cards because no memory could be allocated to the buffer.
Recommended Action Enter a show chunks command and report the output, along with this error message, to your Cisco technical support representative.
Error Message
%IPACCESS-2-WRONGREQUEST: Invalid request to allocate chunk of size [dec]Explanation A request for an Access Control List (ACL) chunk of an incorrect size has been received. Cisco IOS software only allows ACL chunks of a maximum size of IPACCESS_LARGE_CHUNK_SZ.
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
%IPACCESS-2-WRONGSIZE: Incorrect length acl ipc xdr of type=[chars] len=[dec] receivedExplanation The Route Processor (RP) sent an Access Control List (ACL) configuration message of the wrong size for the specified type.
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.
The following are interprocess communication (IPC) error messages.
Error Message
%IPC-2-CANT_SEND: Cannot send IPC message: [chars]Explanation An error has occurred in the interprocess communication (IPC) slave discovery mechanism. This error might result in a malfunction in the operation of the IPC.
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 command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%IPC-4-CONSISTENCY: Message failed consistency check: [chars]Explanation An internal inconsistency was found in some interprocess communication (IPC) data structures.
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 command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%IPC-3-DELETED: Attempt to delete an IPC message (0x[hex]) a second timeExplanation An internal inconsistency was found in some interprocess communication (IPC) data structures.
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 command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%IPC-4-GET_PAK_MSG: Failed for message size=[dec]Explanation System is out of the pak type buffers of the required size.
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
%IPC-3-GIANT: Request for giant IPC packet denied. Request size = [dec]Explanation A user requested a message that was too large for the interprocess communication (IPC) system.
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 command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%IPC-5-INVALID: [chars] [chars]=0x[hex]Explanation An interprocess communication (IPC) message having invalid seat, port, or callback was received.
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 command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%IPC-2-INVALSIZE: IPC message received with invalid size(size/type - [dec]/[dec])Explanation An interprocess communication (IPC) message with invalid size was received.
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 command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%IPC-2-LOCK: Lock done a deleted elementExplanation An internal inconsistency was found in some interprocess communication (IPC) data structures.
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 command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%IPC-3-LOWBUFF: The main IPC message header cache below application reserve count ([dec])Explanation The main interprocess communication (IPC) message header cache fell below the application reserve count.
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 command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%IPC-3-NOBUFF: The [chars] IPC message header cache has emptiedExplanation The specified interprocess communication (IPC) message header cache has emptied.
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 command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%IPC-5-NODELFUNC: Delayed init function not availableExplanation The interprocess communication (IPC) application cannot be initialized because its initialization function does not appear in the IPC initialization function list.
Recommended Action Copy the error message exactly as it appears 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
%IPC-2-NODISPATCH: Message for [dec].[dec] has no receive queue or dispatch routineExplanation The interprocess communication (IPC) user has failed to provide any means of handling the received message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show ipc ports 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 ports command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%IPC-2-NOMEM: No memory available for [chars]Explanation The interprocess communication (IPC) protocol subsystem could not obtain the memory it required.
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 command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%IPC-5-NULL: [chars] [chars]=0x[hex]Explanation An interprocess communication (IPC) message has a null seat, port, or callback.
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 command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%IPC-5-NULLDELFUNC: Passed Null Delayed function to registerExplanation Interprocess communication (IPC) cannot register the NULL function of an application in the IPC initialization function list.
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 command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%IPC-2-ONINT: Called from interrupt level: [chars]Explanation The interprocess communication (IPC) user attempted a prohibited call into IPC while IPC was running on the interrupt stack.
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 command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%IPC-5-OUTPUT_FAIL: Num [dec] Func=0x[hex] Seat: ID=[hex] %10s Sent %6d Heard %6dExplanation The interprocess communication (IPC) output has failed in the function for a given seat with the specified sequence numbers for sending and receiving.
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 command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%IPC-5-QFULL: Q=0x[hex] [chars] [dec]Explanation The interprocess communication (IPC) queue is full.
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 command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%IPC-5-SEQ_ERR: [chars] Num [dec] From [hex],[hex]Explanation Errors have occurred in the interprocess communication (IPC) message sequence numbers.
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 command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%IPC-5-SLAVELOG: VIP-[chars]Explanation The Cisco IOS software, running on a Versatile Interface Processor (VIP) card, generated this message. The error message has been passed up to the Route Processor (RP) or Route Switch Processor (RSP) for display. This message appears only if the user has entered the service slavelog command.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%IPC-2-TEST: IPC test: [chars]Explanation The interprocess communication (IPC) test routines have run.
Recommended Action No action is required.
Error Message
%IPC-2-UNLOCK: Unlock done on already unlocked elementExplanation An internal inconsistency was found in some interprocess communication (IPC) data structures.
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.
The following are Route Processor interprocess communication (IPCRP) error messages.
Error Message
%IPCGRP-3-CARDERR: [chars]Explanation An interprocess communication (IPC) card has registered itself to the IPC master twice. The card has malfunctioned and its IPC is not active.
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
%IPCGRP-3-CMDOP: IPC command [int] (slot[int]/[int]): [chars]Explanation Interprocess communication (IPC) command processing operational errors have 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
%IPCGRP-3-CREATE_FAIL: [chars] [chars]Explanation An interprocess communication (IPC) port was not created on the Route Processor (RP).
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
%IPCGRP-3-EVENTOP: Event [int] from slot[int]: [chars]Explanation Interprocess communication (IPC) event processing operational errors have 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
%IPCGRP-3-EXECCMDMSG: Incorrect msg size (size=[int])Explanation The message size is incorrect for an EXEC interprocess communication (IPC) command.
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
%IPCGRP-3-INVNUM: [chars] ([int])Explanation The interprocess communication (IPC) application tried to send a message that was larger than IPC could handle. The message was not transmitted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%IPCGRP-3-MSGERR: [chars] ([int])Explanation The slave interprocess communication (IPC) cannot register with the master. It cannot exchange messages with the master.
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
%IPCGRP-3-NBLKCMD: [chars]Explanation A nonblocking interprocess communication (IPC) command queue initialization failure has 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
%IPCGRP-3-NOHWIDB: Cannot find hwidb for interface([int]/[int])Explanation An interface identifier does not exist for the interface addressed by the corresponding interprocess communication (IPC) message.
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
%IPCGRP-3-NULLMSG: Null [chars] ipc messageExplanation An unexpected empty interprocess communication (IPC) message was received.
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
%IPCGRP-3-NULLREXECCMD: Received empty ipc rexec cmd messageExplanation An interprocess communication (IPC) command failure has 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
%IPCGRP-3-REXEC: [chars]Explanation An interprocess communication (IPC) command failure has 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
%IPCGRP-3-SEATERR: [chars] ([int])Explanation The ID associated with an interprocess communication (IPC) card either is missing, is duplicated, or cannot be created.
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
%IPCGRP-3-SYSCALL: System call for command [int] (slot[int]/[int]) : [chars] (Cause: [chars])Explanation An interprocess communication (IPC) kernel system call error has 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.
The following are Gigabit Switch Router line card IP multicast error messages.
Error Message
%IPCLC-3-EVENT: Event ([int]) [chars] errorExplanation A command or event processing operational error has 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
%IPCLC-3-EVENTSYS: Event ([int]) system call [chars] error (cause: [chars])Explanation Interprocess communication (IPC) kernel system call errors have 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
%IPCLC-3-INTRLVL: LC interrupt level IPC event, [chars]Explanation Interprocess communication (IPC) event processing errors at the LC interrupt level have 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
%IPCLC-3-MSGERR: [chars] ([dec])Explanation The line card interprocess communication (IPC) cannot register with the Route Processor (RP). It cannot exchange messages with the RP.
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
%IPCLC-3-OP: [chars]Explanation A command or event processing operation error has 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
%IPCLC-3-REPLY: Reply (to cmd [int]) [chars] errorExplanation A command or event processing operation error has 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
%IPCLC-3-REPLYSYS: Reply (to cmd [int]) system call [chars] error (cause: [chars])Explanation A Reply-to-Route Processor (RP)-command operation error has 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.
The following are interprocess communication (IPC) error messages.
Error Message
%IPC_RPM-3-CARDERR: [chars]Explanation An interprocess communication (IPC) card registered itself to the IPC master twice.
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
%IPC_RPM-3-INVMSG: [chars] ([dec])Explanation An invalid interprocess communication (IPC) message was received during execution of the cc command.
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
%IPC_RPM-3-INVNUM: [chars] ([dec])Explanation The interprocess communication (IPC) application tried to send a message that was larger than IPC could handle. The message was not transmitted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%IPC_RPM-3-NOBUF: [chars]Explanation The interprocess communication (IPC) does not have adequate memory buffers.
Recommended Action Reduce the number of applications currently running on the IPC. Copy the error message exactly as it appears, and report it to your Cisco technical support representative.
Error Message
%IPC_RPM-3-SEATERR: [chars] [chars]Explanation The ID associated with an interprocess communication (IPC) card either is missing, is duplicated, or cannot be created.
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.
The following are interprocess communication (IPC) ciscoBus (CBUS) error messages.
Error Message
%IPC_RSP_CBUS-3-CARDERR: [chars]Explanation An interprocess communication (IPC) card has registered itself to the IPC master twice. The card malfunctioned and its IPC is not active.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%IPC_RSP_CBUS-3-INVNUM: [chars] ([dec])Explanation The interprocess communication (IPC) application tried to send a message that was larger than IPC could handle. The message was not transmitted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%IPC_RSP_CBUS-3-MSGERR: [chars] ([dec])Explanation The slave interprocess communication (IPC) cannot register with the master and therefore cannot exchange messages with the master.
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
%IPC_RSP_CBUS-3-NOBUF: [chars]Explanation The interprocess communication (IPC) does not have adequate memory device (MEMD) buffers.
Recommended Action Reduce the number of applications currently running on the IPC. 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
%IPC_RSP_CBUS-3-NOHWQ: Hardware queue for card at slot [dec] not foundExplanation Interprocess communication (IPC) messages cannot be transmitted because of a missing hardware queue. The messages were discarded, and subsequent messages will not be transmitted to that card.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%IPC_RSP_CBUS-3-SEATERR: [chars] ([dec])Explanation The ID associated with an interprocess communication (IPC) card either is missing, is duplicated, or cannot be created.
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.
The following are IP fast switching error messages.
Error Message
%IPFAST-2-BADIF: No support available for interface [chars] (programming error)Explanation A programming error has 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 command command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%IPFAST-2-PAKSTICK: Corrupted pak header for [chars], flags [hex]Explanation A programming error has 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 command 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 has 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
%IPFAST-3-INVALIDADDR: Invalid cache destination [int]/[dec]Explanation The system has 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, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message
%IPFAST-6-INVALIDATE: Cache invalidation occurring for [chars]Explanation The system is invalidating all cache entries for a given interface.
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
%IPFAST-6-INVALREQ: Cache invalidation request for [chars]Explanation The system is invalidating all cache requests for a given interface.
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
%IPFAST-6-PAKSHORT: Packet too short from [int], datagram size [dec], tl [dec]Explanation An IP packet that is too short was received.
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
%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 structuresExplanation A programming error has 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 command 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.
The following are IP flow error messages.
Error Message
%IPFLOW-4-ACTIVATE: Error activating [chars]([dec]) in slot [dec]Explanation The activation of a flow-accelerated feature has failed.
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
%IPFLOW-4-ACTIVATENOMEM: Error activating [chars]([dec])Explanation The activation of a flow-accelerated feature has failed because of insufficient memory.
Recommended Action Reduce other system activities to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message
%IPFLOW-2-CACHEINIT: Error initializing IP flow cacheExplanation Initialization of the flow cache could not be accomplished because of insufficient memory.
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 command 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 has failed.
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
%IPFLOW-4-DEACTIVATENOMEM: Error deactivating feature [dec]Explanation Deactivation of a flow-accelerated feature has failed because of insufficient memory.
Recommended Action Reduce other system activities to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message
%IPFLOW-2-EXPORTINIT: Error initializing Flow Export queueExplanation Initialization of the flow export queue could not be accomplished because of insufficient memory.
Recommended Action Reduce other system activities to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message
%IPFLOW-2-PROCESSINIT: Error initializing Flow background processExplanation Initialization of the flow background process could not be accomplished because of insufficient memory.
Recommended Action Reduce other system activities to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message
%IPFLOW-2-QUEUEINIT: Error initializing Flow feature queueExplanation Initialization of the flow feature queue could not be accomplished because of insufficient memory.
Recommended Action Reduce other system activities to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
The following are Gigabit Switch Router line card IP multicast error messages.
Error Message
%IPMCAST-5-ERR: [chars] [chars]=0x[hex]Explanation Errors have occurred during the processing of an IP multicast packet.
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.
The following are IP Mobility error messages.
Error Message
%IPMOBILE-2-ASSERTFAILED: IPMOBILE assertion failed: [chars]Explanation The software has detected an inconsistency that is considered a serious error. The router attempts to continue, but IP Mobility processing may be impaired.
Recommended Action Copy the error message exactly as it appears, noting any IP Mobility problems that you are experiencing, and report it to your Cisco technical support representative.
Error Message
%IPMOBILE-3-NOSOCKET: Unable to open socketExplanation The requested operation could not be accomplished because of insufficient memory.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message
%IPMOBILE-6-SECURE: Security violation on [chars] from [chars] [int] - errcode [chars] ([dec]), reason [chars] ([dec])Explanation A security violation has occurred during a registration attempt.
Recommended Action This is an informational message only. No action is required. However, if an unauthorized user attempted the registration, take the necessary security measures to block the source.
The following are Voice over IP driver error messages.
Error Message
%IPM_C54X-3-DSP_ALARM_INDICATION: DSP [dec] Sending alarm indicationExplanation The digital signal processor (DSP) is indicating that an unexpected event has occurred and it may not continue to process calls.
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
%IPM_C54X-1-DSP_TIMEOUT: dsp [dec] NOT RESPONDINGExplanation The digital signal processor (DSP) driver cannot queue messages up to the direct memory access (DMA) engine for transmission.
Recommended Action Reset the DSPs on this port module. If this message recurs, 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
%IPM_C54X-3-EPIC_NOT_RESPONDING: Epic TDM Switch failureExplanation The EPIC time-division multiplexing (TDM) switch has failed to acknowledge a command.
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
%IPM_C54X-3-ERROR_INIT_BLDR: [chars] Unable to download the Boot loader firmware, ret = 0x[hex]Explanation An error has occurred during initialization of the digital signal processor (DSP) with the bootloader firmware.
Recommended Action Power down, reinsert the port module, and reboot the system. If the message recurs, 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
%IPM_C54X-3-ERROR_INIT_OVERLAY: [chars] Unable to download the Application overlay firmware. Status returned 0x[hex]Explanation An error has occurred during the initialization of the digital signal processor (DSP) with the application overlay firmware.
Recommended Action Power down, reinsert the port module, and reboot the system. If the message recurs, 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
%IPM_C54X-3-IDB_CREATE: Unable to allocate IDBExplanation The digital signal processor (DSP) interface descriptor block (IDB) cannot be allocated.
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
%IPM_C54X-3-INIT_CONFIG_FAILED: DSP [dec] Sending alarm indicationExplanation The digital signal processor (DSP) is indicating that it is not able to properly initialize the ports that it services.
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
%IPM_C54X-3-NODSP: Can't get dsp resourcesExplanation There are not enough digital signal processors (DSPs) for all the voice interface cards (VICs) in the router.
Recommended Action There are more VICs in the router than the DSPs can support. You must upgrade your DSP module to get more DSPs. To confirm how many DSPs are on a router, use show diag command.
Error Message
%IPM_C54X-3-NO_BUFFERS: No buffers available for DSP buffer poolExplanation Buffers to the digital signal processor (DSP) receive buffer pool could not be allocated.
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
%IPM_C54X-1-NO_RING_DESCRIPTORS: No more ring descriptors available on [dec] slotExplanation The digital signal processor (DSP) driver cannot queue messages up to the direct memory access (DMA) engine for transmission.
Recommended Action Reset the DSPs on this port module. If this message recurs, 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
%IPM_C54X-1-TOOBIG: [chars], packet(size [dec]) too bigExplanation A packet greater than the 256 byte maximum was received on this interface.
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.
The following are IP routing error messages.
Error Message
%IPRT-3-BADCOMLIST: Community list check with bad list [dec]Explanation A user has specified an invalid Border Gateway Protocol (BGP) community list number.
Recommended Action Check the system configuration to ensure that the specified community list specified falls within the valid range.
Error Message
%IPRT-2-COMPRESS: Bad route_compress() call, sdb= [hex]Explanation An internal software error has 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
%IPRT-3-IPTABLEINIT: IP routing table creation failure - [chars]Explanation An internal software error has occurred and has prevented the creation of a new IP routing table.
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
%IPRT-3-NOMEMORY: No memory available for [chars]Explanation The requested operation has failed because of insufficient memory.
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] maxExplanation A software error has 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
%IPRT-3-ROUTELIMITEXCEEDED: IP routing table limit exceeded - [chars], [int][inet]Explanation The number of routes in the named IP routing table has reached the configured limit. No further routes will be added to the table.
Recommended Action Reduce the number of routes in the table, or reconfigure the limit.
Error Message
%IPRT-3-ROUTELIMITWARNING: IP routing table limit warning - [chars]Explanation The number of routes in the named IP routing table has reached the configured warning limit.
Recommended Action Reduce the number of routes in the table, or reconfigure the limit.
The following are Novell Internetwork Packet Exchange (IPX) protocol error messages.
Error Message
%IPX-3-BADCOUNT: Bad IPX server count. [chars] [dec], [chars] [dec]Explanation The internal service access point (SAP) service count does not match the number of services currently present and displayed by the show ipx servers command.
Recommended Action Report the problem to your Cisco technical support representative, along with the output of the show px servers command gathered before this message appeared and again after this message appeared.
Error Message
%IPX-3-BADHASHTABLE: Consistency check failed for SAP table [dec].Explanation An internal service access point (SAP) table consistency check has failed.
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
%IPX-3-BADIGRPSAP: Cannot send incremental SAP update to peer on [chars]. Increasing output-sap-delay may helpExplanation An incremental service access point (SAP) update could not be sent, because receipt of the update might cause the SAP tables between the peers to lose synchronization.
Recommended Action Increase the output SAP delay on the listed interface to reduce buffer usage. If the message recurs, 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
%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 service access point SAP with a type code that is neither a general query nor a general response. This message will also be sent when you receive a general query that is not addressed to the broadcast address.
Recommended Action Copy the error message exactly as it appears and report it to your Cisco 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-BADINSERT: Duplicate SAP entry insert attempted. [chars][chars] [chars]0x[hex] [chars]0x[hex] [chars][dec] [chars]0x[hex] [chars]0x[hex] [chars]0x[hex]Explanation A user attempted to add a Novelle IPX service access point (SAP) service entry that already exists in the current internal table.
Recommended Action Report the error messages and the tracebacks that follow them to your Cisco technical support representative.
Error Message
%IPX-3-BADPATHS: Invalid number of paths ([dec]) for %qExplanation An internal inconsistency was detected in the Novelle 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 Cisco 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 Novelle 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 access as defined in the access list.
Error Message
%IPX-3-TOOMANYNETS: Too many networksExplanation The limit of connected Novelle IPX networks has been reached. Additional IPX interfaces cannot be configured.
Recommended Action Do not configure IPX on additional interfaces. Remove the IPX configuration commands from the inactive interfaces.
The following are error messages for Simple Network Management Protocol (SNMP) specific to IP.
Error Message
%IP_SNMP-4-NOTRAPIP: SNMP trap source [chars] has no ip addressExplanation The user entered the 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 socketExplanation The SNMP server was unable to open a port for receiving or transmitting SNMP requests. This error usually occurs 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 insufficient 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 Cisco technical support representative if 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 has made a correct response to invalid external data. Since SNMP packets should originate from systems under the same administration, this message 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 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.
The following are Integrated Services Adapter (ISA) error messages.
Error Message
%ISA-1-ALIGN: Alignment failure on packet buffer: 0x[hex]Explanation A software error has occurred. The Integrated Services Adapter (ISA) driver detected that the buffer is not aligned correctly.
Recommended Action Copy the error message exactly as it appears, and report it to your Cisco 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
%ISA-1-ERROR: [chars]Explanation An error has occurred in the application using the Integrated Services Adapter (ISA).
Recommended Action Copy the error message exactly as it appears, and report it to your Cisco 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
%ISA-1-INITDESCRING: Slot [dec]: The ISA driver failed to allocate descriptor offsets write_offsets: [hex], read_offsets: [hex], stored_offsets: [hex]Explanation The Integrated Services Adapter (ISA) driver has failed to initialize at the specified point.
Recommended Action Copy the error message exactly as it appears, and report it to your Cisco 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
%ISA-1-INITFAIL: Slot [dec]: [chars]Explanation The Integrated Services Adapter (ISA) driver has failed to initialize at the specified point.
Recommended Action Copy the error message exactly as it appears, and report it to your Cisco 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
%ISA-1-NOMEMORY: [chars] creation failed for slot [dec]Explanation The Integrated Services Adapter (ISA) driver, in its initialization phase, could not allocate memory for the specified data structure.
Recommended Action Consider adding more shared memory. Copy the error message exactly as it appears, and report it to your Cisco technical support representative.
Error Message
%ISA-1-OWNER: [chars] packet buffer, pak=0x[hex]Explanation A software or hardware error has occurred. The Integrated Services Adapter (ISA) driver has detected that the buffer ring is in an inconsistent and unrecoverable state.
Recommended Action Copy the error message exactly as it appears, and report it to your Cisco 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
%ISA-6-SHUTDOWN: [chars] shutting downExplanation The specified Integrated Services Adapter (ISA) is shutting down. It may have been physically removed.
Recommended Action No action is required.
Error Message
%ISA-1-TOOBIG: [chars] received a packet with size [dec]Explanation The packet received was too large.
Recommended Action Copy the error message exactly as it appears, and report it to your Cisco 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.
The following are ISDN error messages.
Error Message
%ISDN-4-BAD_DSL_FOR_CREATE_DELETE_L2: [chars]: isdn_create_delete_signalling_channel: Unknown DSL [int] for [chars]Explanation The creation or deletion service for the L2 signalling handler or the given digital subscriber line (DSL) is missing.
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 command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%ISDN-6-CALL_COLLISION: Interface [chars] Call Cid 0x[hex] Cref 0x[hex] collision on Channel [dec] in_use_cid 0x[hex] cref 0x[hex], Channel awarded to the received callExplanation A call has been received and has collided with an existing call on the same channel.
Recommended Action No action is required.
Error Message
%ISDN-6-CALL_EXISTS: Interface [chars] Call exists for bchan [dec] in_use_cid 0x[hex] in_use_cref 0x[hex] new_cid 0x[hex] new_cref 0x[hex]Explanation The channel specified for the new call is already in use.
Recommended Action No action is required.
Error Message
%ISDN-6-CHAN_UNAVAILABLE: Interface [chars] Requested Channel [dec] is not availableExplanation The requested channel is not available.
Recommended Action 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 the location at which 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] secondsExplanation This is an informational message sent when a call is disconnected. This message displays the remote name and number, which it receives from the Point-to-Point Protocol (PPP) authentication or from the location at which the dialer placed the call. This message also reports the duration of the call.
Recommended Action No action is required.
Error Message
%ISDN-4-GET_STATUS_STATE_FAIL: [chars]: isdn_get_status_state: Unknown DSL [int]Explanation An attempt to retrieve the status of a digital subscriber line (DSL) that is not currently configured has failed.
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 command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%ISDN-4-INVALID_CALLEDNUMBER: Interface [chars], Ignoring call, LDN and Called Party Number mismatchExplanation The incoming ISDN call is ignored because the Called Party Number does not match the local directory number (LDN) number that is configured in the router.
Recommended Action Correct the LDN number 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) mismatchExplanation The incoming ISDN call is ignored because the endpoint identifier (EID) delivered in the incoming setup message cannot be matched.
Recommended Action If the EID is delivered in the setup message, use the isdn debugs and show isdn status commands to determine the current EID values. You should contact the service provider.
Error Message
%ISDN-4-INVALID_EVENT: [chars]: Bad Event Received For Current StateExplanation The state transition for the ISDN L2 socket process has failed.
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 command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%ISDN-4-INVALID_SPID: Interface [chars], Spid[dec] was rejectedExplanation 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 Basic Rate Interface (BRI).
Error Message
%ISDN-6-INVALID_TIMER: [chars]: Invalid Timer Handle, caller 0x[hex] handle %3dExplanation An invalid ISDN timer handle has been passed on for timer operations. This message may indicate a low memory condition.
Recommended Action Enter the show isdn mem and show isdn status commands to gather debugging information. Reduce other system activity to ease the memory demands on the system.
Error Message
%ISDN-2-ISDN_GENERAL_TRACEBACK: [chars]:[dec]Explanation A debug traceback condition has occurred.
Recommended Action No action is required.
Error Message
%ISDN-4-ISDN_L2_INTERFACE_NOT_REGISTERED: [chars]: isdn_to_L2: Unknown DSL [int] for command [chars]Explanation The ISDN stack has not registered its L2 message handler.
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 command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%ISDN-4-ISDN_UNEXPECTED_EVENT: [chars]: Occurred at [chars]:[dec]Explanation An unexpected event of significance has 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 command output, call your Cisco technical support
%ISDN-6-LAYER2DOWN: Layer 2 for Interface [chars], TEI [int] changed to downExplanation An ISDN Layer2 logical link is down. The terminal endpoint identifier (TEI) associated with this logical link is shown.
Recommended Action No action is required.
Error Message
%ISDN-6-LAYER2UP: Layer 2 for Interface [chars], TEI [int] changed to upExplanation An ISDN Layer2 logical link is up. The terminal endpoint identifier (TEI) associated with this logical link is shown.
Recommended Action No action is required.
%ISDN-1-NOMEMORY: msgtxt_nomemoryExplanation The requested operation could not be accomplished because of insufficient memory.
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 The ISDN protocol cannot start new timers for its operation. This message may indicate a low memory condition.
Recommended Action Enter the show isdn mem and show isdn status commands to gather debugging information. Reduce other system activity to ease the memory demands on the system.
Error Message
%ISDN-4-OPEN_TEMP_SOCKET_FAIL: [chars]: Failed to Open Required Temporary Socket[chars]Explanation The reopen attempt for a required temporary socket has failed. Without this socket, the L2 socket process will fail.
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 command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%ISDN-4-RLM_STATUS_CHANGE: ISDN SC [chars]: Status Changed to: [chars]Explanation ISDN has been notified by the Redundant Link Manager (RLM) component of a status change in the RLM link.
Recommended Action No action is required.
Error Message
%ISDN-4-SPURIOUS_CONNECT: [chars]: Spurious Connection Accepted and Closed on port [int]Explanation An unknown TCP connection was accepted and then refused.
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 command output, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are Interactive Voice Response (IVR) error messages.
Error Message
%IVR-3-BAD_IVR_SIG: Script signature is invalid[chars] [chars]Explanation This script does not have a valid signature.
Recommended Action Make sure the script is Cisco-approved with a signature.
Error Message
%IVR-3-INVALID_SCRIPT: App [chars]: Invalid IVR script to handle callID [dec]Explanation The call will be dropped because of an invalid script.
Recommended Action Ensure that script exists on the server, is readable, and is supported.
Error Message
%IVR-3-LOW_MEMORY: IVR: Sytem running on low memory. Free memory: %l bytes. Call is rejected.Explanation The system does not have enough memory to accept calls.
Recommended Action Check to see what condition is causing low system memory.
Error Message
%IVR-3-NOPROMPT: Could not create IVR prompt [chars] errno=[dec]=[chars]Explanation The Interactive Voice Response (IVR) prompt could not be read.
Recommended Action Ensure that the prompt exists on the server and is readable.
Error Message
%IVR-3-NOSCRIPT: Could not open IVR script [chars] errno=[dec]=[chars]Explanation The Interactive Voice Response (IVR) script could not be read.
Recommended Action Ensure that the script exists on the server and is readable.
Error Message
%IVR-3-NO_IO_MEMORY: [chars]: Failed to create pool_group [hex] buffer_pool [hex]Explanation There is not enough I/O memory to create the Interactive Voice Response (IVR) private pak pool.
Recommended Action Ensure that there is enough I/O memory.
The following are error messages for Voice over IP for Cisco AS5800.
Error Message
%KERBEROS-3-FORKFAIL: Failed to fork process for [chars].Explanation The system could not start a process. This message may indicate a low memory condition.
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.
The following are Voice over IP for Cisco AS5800 error messages.
%KINEPAK-3-CONTIGUOUS: Contiguous packet sent for transmitExplanation A software error has occurred, causing an unexpected packet to be prepared for transmission and then dropped.
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
%KINEPAK-3-ERR_DSPWARE_DNLD: dsp[dec] cannot download dspware [chars]Explanation A software error has occurred and has caused a failure to download a digital signal processor (DSP) component.
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
%KINEPAK-3-ERR_DSPWARE_IMG: Cannot find dspware [chars] componentExplanation A software error has occurred and has caused a failure to download a digital signal processor (DSP) component.
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
%KINEPAK-3-NODSPENTRY: No dsp entry in dsp listExplanation The software structure that is used to maintain the digital signal processor (DSP) instance is missing.
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
%KINEPAK-3-NOMAILELEMENTS: Cannot create message bufferExplanation A software error has occurred, resulting in failure to create the message buffer that sends messages among processes.
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
%KINEPAK-3-NOPARTICLE: No particle available for ingress packetExplanation A software error has occurred, resulting in failure to obtain a particle to hold an ingress packet from the digital signal processor (DSP).
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
%KINEPAK-3-NOPARTICLEPOOL: Cannot create particle poolExplanation A software error has occurred, resulting in failure to create the particle pool that receives packets from the digital signal processor (DSP).
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
%KINEPAK-3-NORXPAK: Static receive paktype unavailableExplanation A software structure was found in an unexpected state during the run-time for the specified digital signal processor (DSP).
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.
The following are Local Area Network Controller Ethernet (LANCE) 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. Receiving no error messages indicates a hardware error. Repair or replace the controller. If you receive an error message, copy the error message exactly as it appears, and report it to your Cisco technical support representative.
Error Message
%LANCE-3-BADCABLE: msgtxt_badcableExplanation The Ethernet cable is not connected.
Recommended Action Check Ethernet cable connection.
Error Message
%LANCE-3-BADUNIT: msgtxt_badunitExplanation An internal software error has 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
%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_initfailExplanation The hardware has failed to initialize correctly.
Recommended Action Repair or replace the controller.
Error Message
%LANCE-5-LATECOLL: Unit [dec], late collision errorExplanation An Ethernet transceiver is malfunctioning, the Ethernet is overloaded, or the Ethernet cable is too long.
Recommended Action Repair or replace the controller.
Error Message
%LANCE-5-LOSTCARR: Unit [dec], lost carrier. Transceiver problemExplanation An Ethernet transceiver is unplugged or defective.
Recommended Action Repair or replace the controller.
Error Message
%LANCE-1-MEMERR: msgtxt_memoryerrorExplanation An Ethernet interface has detected a hardware problem.
Recommended Action Repair or replace the controller.
Error Message
%LANCE-3-OWNERR: msgtxt_ownerrorExplanation An Ethernet interface is malfunctioning, or an internal software error has 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 has generated a spurious Initialization Done interrupt.
Recommended Action Repair or replace the controller.
Error Message
%LANCE-3-UNDERFLO: Unit [dec], underflow errorExplanation The Ethernet hardware is requesting data faster than the system can supply it. This condition might indicate that the system is at the limit of its performance.
Recommended Action A small number of underflows might not be a cause for concern. You can monitor underflows with the show interface command. Reducing the load on the router or installing a higher-performance router should alleviate this problem.
The following are LAN emulation (LANE) error messages.
Error Message
%LANE-3-BADILMI: Unexpected ILMI event [dec]Explanation An internal error has occurred.
Recommended Action Download the system error log. Then call your Cisco technical support representative, and provide the log, the error message, and the router configuration.
Error Message
%LANE-3-BADNAME: ELAN name must be 1-32 characters longExplanation A name identifying a LAN emulation (LANE) component that is longer than 32 characters has been entered by the user.
Recommended Action Reenter a shorter name.
Error Message
%LANE-3-BADTYPE: Inappropriate LAN typeExplanation An unexpected LAN type has been specified for a LAN emulation (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 LAN emulation (LANE) subsystem.
Recommended Action No action is required.
Error Message
%LANE-3-LANE_ERROR: [chars]Explanation An internal error has occurred, indicating an inconsistency in the system that requires attention.
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
%LANE-3-LANE_SIG_ERR: [chars]Explanation An internal error has occurred while system routines were handling ATM signalling messages for LAN emulation (LANE).
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
%LANE-3-LECS_ERROR: [chars]Explanation An internal consistency error has 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
%LANE-6-LECS_INFO: [chars]Explanation This is an informational message about the LAN Emulation Configuration Server (LECS).
Recommended Action No action is required.
Error Message
%LANE-4-LECS_WARNING: [chars]Explanation The LAN Emulation Configuration Server (LECS) address could not be registered with or deregistered from the switch, using Interim Local Management Interface (ILMI). Possible causes:
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
%LANE-3-LEC_BADAD: [chars] LEC unable to compute ATM addressExplanation The client cannot obtain an ATM address from the given configuration, or the auto-assignment has failed to get an ATM prefix from the switch.
Recommended Action If you expect the switch to assign the prefix to the router, ensure that the Interim Local Management Interface (ILMI) is functional and the switch has a prefix configured. Otherwise, confirm that the client has an address in the NVRAM configuration.
Error Message
%LANE-3-LEC_BAD_CTL_DIST_TYPE: [chars] CTL DIST blli type wrongExplanation An incorrect Broadband Low Level Information (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 LAN emulation (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 LAN Emulation Configuration Server (LECS) has refused the configuration request of the LAN Emulation Client (LEC).
Recommended Action Check your LECS configurations.
Error Message
%LANE-3-LEC_CONTROL_MSG: Received bad control message on interface [chars]Explanation The LAN emulation (LANE) client has received an unexpected or inappropriate control message over one of its virtual circuits (VCs).
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
%LANE-3-LEC_ERR: [chars]Explanation A LAN emulation (LANE) client software or hardware error has 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
%LANE-3-LEC_JOIN: [chars] JOIN failed, [chars] (LES returned [dec])Explanation The request of a LAN emulation (LANE) client to join its emulated LAN (ELAN) has been rejected.
Recommended Action This message is usually the result of user configuration errors (such as that the LANE client attempted to join an incorrect ELAN or the ELAN was not configured in the LAN Emulation Server) or there were validation failures with the LAN Emulation Configuration Server (LECS).
Error Message
%LANE-3-LEC_LISTEN: [chars] listen failed on [chars]Explanation The LAN emulation (LANE) client could not register its address with ATM signalling in order to be able to accept calls on that address.
Recommended Action Reconfigure the client ATM address. It may be in conflict with another component that has the same ATM address.
Error Message
%LANE-3-LEC_RD_REGISTER: [chars] RD REGISTER failed for Route Descriptor [hex]Explanation A software or hardware error has 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
%LANE-3-LEC_REGISTER: [chars] REGISTER failed, [chars] (LES returned [dec])Explanation An attempt to register a MAC-ATM address binding with the LAN Emulation Server (LES) has failed.
Recommended Action The LAN Emulation Server (LES) has already registered the requested MAC address ----ATM address binding.
Error Message
%LANE-3-LEC_SIGNAL: Unexpected SigAPI event [dec]Explanation ATM signalling has sent the LAN emulation (LANE) client an unexpected message type.
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
%LANE-3-LEC_WRONG_ELAN_ID: [chars]: elan id mismatch: LECS indicates [int], LES indicates [int]Explanation The emulated LAN (ELAN) ID returned by the LAN Emulation Server (LES) does not match the value given by the LAN Emulation Configuration Server (LECS) or by the command line interface (CLI).
Recommended Action Check the ELAN-ID configurations specified in the LECS database and the LES. The mismatch may be the result of misconfiguration.
Error Message
%LANE-3-LES_ERROR: [chars]Explanation A serious internal error has occurred with the LAN Emulation Server (LES) or BUS.
Recommended Action Download the system error log. Then call your Cisco technical support representative, and provide the log, the error message, and the router configuration.
Error Message
%LANE-6-LEC_INFO: [chars]Explanation This is an informational message about the LAN Emulation Configuration Server (LECS).
Recommended Action No action is required.
Error Message
%LANE-6-LES_INFO: [chars]Explanation This is an informational message about the LAN Emulation Server (LES).
Recommended Action No action is required.
Error Message
%LANE-3-LSV_ADDR: [chars] elan [chars] unable to register LES/BUS ATM addrExplanation The LAN emulation (LANE) server or BUS could not register its address with the Interim Local Management Interface (ILMI).
Recommended Action Investigate why this error has occurred. The error may have occurred because a user defined override address does not conform to the switch prefix or because there is a problem with the ATM switch with which the entity is registering.
Error Message
%LANE-3-LSV_BADAD: [chars] elan [chars] unable to compute [chars] ATM addressExplanation The software was unable to compute an ATM address based on the ATM address template given. The text in [chars] will be either be BUS (broadcast-and-unknown), server, or config server in the actual error message.
Recommended Action Enter a correct ATM address template for the LAN emulation (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 serious LAN Emulation Server (LES) or BUS internal error has occurred.
Recommended Action Download the system error log. Then call your Cisco technical support representative, and provide the log, the error message, and the router configuration.
Error Message
%LANE-4-LSV_LECID: [chars] elan [chars] LECIDs exhaustedExplanation The LAN emulation (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 nameExplanation Both the LAN emulation (LANE) client and the LANE server or BUS may have an emulated LAN name specified in the configuration as a result of using the lane server-bus and lane client commands. If both specify the emulated LAN name, then the name cannot be changed by reentering just one of the commands.
Recommended Action Use the no lane server-bus command to delete the LANE server or BUS or the no lane client command to delete the client. Then reenter the other of the two commands with another emulated LAN name. Finally, reenter the deleted command with the new emulated LAN name.
Error Message
%LANE-3-NOILMI: ILMI service registration failedExplanation The Interim Local Management Interface (ILMI) feature is either not included in the Cisco IOS software image running on the router or is not functioning properly.
Recommended Action Download the system error log. Then call your Cisco technical support representative, and provide the log, the error message, and the router configuration.
Error Message
%LANE-3-NOINT: [chars] still destroying old sub-interfaceExplanation An attempt was made to create a new subinterface while a previous version of the subinterface was still being destroyed.
Recommended Action Wait a minute and try again. If failure still occurs, try shutting down the main interface. In extreme cases, recovery may require rebooting.
Error Message
%LANE-3-NOREGILMI: [chars] [chars] cannot register %Cj with ILMIExplanation An attempt to register the given ATM address with the ATM switch has failed. This failure can occur because the ATM switch is down or configured incorrectly. 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 typeExplanation Both the LAN emulation (LANE) client and the LANE Server or BUS may have an ELAN type specified in the configuration as a result of using 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 reentering just one of the commands.
Recommended Action Use the no lane server-bus command to delete the BUS or the no lane client command to delete the client. Then the other of the two commands can be reentered with a new type. Finally, reenter the deleted command with the new type.
Error Message
%LANE-5-UPDOWN: [chars] [chars] [chars]: [chars] changed state to [chars]Explanation A LAN emulation (LANE) component has changed state to up or down.
Recommended Action If this event is expected, then take no action. Otherwise, contact a Cisco technical support representative.
The following are IBM LAN Network Manager error messages.
Error Message
%LANMGR-4-BADRNGNUM: Ring number mismatch on [chars], shutting down the interfaceExplanation The router has detected a conflict in the 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 has 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
%LANMGR-2-NOMEMORY: No memory available: [chars]Explanation The requested operation has 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 has 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
%LANMGR-4-OLDTRAMON: Cannot run RPS on [chars], Old TRAMON code.Explanation The software on this interface cannot support the functions required for the LAN Network Manager (LNM).
Recommended Action Call your Cisco technical support representative about a firmware upgrade for this interface card.
The following are X.25 Link Access Procedure, Balanced (LAPB), error messages.
Error Message
%LAPB-3-BADPAYLOAD: Interface [chars], Invalid payload value: [chars]Explanation An internal software error has 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
%LAPB-4-CTRLBAD: Interface [chars], Invalid control fieldExplanation A received Frame REJECT(FRMR) has reported a frame that has 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 has been detected. The Reason field will be interpreted by generating INFOBAD, CTRLBAD, N1TOOBIG, or INVNR messages immediately after this message; refer to the explanations of these messages for more information.
Recommended Action The protocol will recover by resetting the service. Resetting the device will disrupt any network service on top of FRMR. For example, X.25 virtual circuits will be cleared. Follow the recommended action for any error message following the FRMR reports. If service becomes unacceptable, check the serial line and its attached devices.
Error Message
%LAPB-4-INFOBAD: Interface [chars], Info field not permittedExplanation A received 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 valueExplanation A received Frame REJECT (FRMR) reported a frame having an invalid N(R) value.
Recommended Action Verify that the equipment attached to the serial line is configured with the same K value (maximum number of outstanding I frames).
Error Message
%LAPB-4-N1TOOBIG: Interface [chars], N1 too largeExplanation A received 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 cyclic redundancy check (CRC). However, some equipment may require configuration in octets, the omission of the two CRC octets, or the omission of the three octets of Link Access Procedure, Balanced (LAPB) control information.
Error Message
%LAPB-2-NOBUF: Interface [chars], no buffer available to [chars]Explanation There was insufficient memory for the Link Access Procedure, Balanced (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 the loss of frames. However, frequent occurrences of the problem can cause a disruption of service. Configured the system to ease the memory demands or, if conditions warrant, upgrade the system to a larger memory configuration.
Error Message
%LAPB-3-NOINPIDB: Input idb not setExplanation An internal software error has 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
%LAPB-3-NULLPAK: Interface [chars], NULL packet ptr, rvr [dec], vs [dec], vr [dec]Explanation An internal software error has 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.
The following are DEC local-area transport (LAT) error messages.
Error Message
%LAT-3-BADDATA: Tty[t-line], Data pointer does not correspond to current packetExplanation An internal software error has 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
%LAT-3-BUFFULL: Tty[t-line], data buffer full with count [dec]Explanation An internal software error has 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
%LAT-3-NOSYNC: Tty[t-line], Output data ptrs out of sync with byte countExplanation An internal software error has 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
%LAT-3-NULLIDB: Null IDB pointer with destination [sci_notation]Explanation An internal software error has 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
%LAT-3-QBSPACED: Queue block at [hex] not found for HI connectionExplanation An internal software error has 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
%LAT-3-REUSE: Tty[t-line], Attempt to re-use slot array, empty = [dec], fill = [dec]Explanation An internal software error has 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.
Posted: Fri Jun 16 11:51:18 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.