-
Cisco IOS System Error Messages, Volume 1 of 2
-
About Cisco IOS Software
-
System Error Messages Overview
-
AT through BERT
-
BGP through C6KPWR
-
C6MSFC through CHOPIN_MAINBOARD_ASYNC_PQII
-
CI through COT
-
CPAD through DBCONN
-
DBUS through DSCREDCLK
-
DSC_REDUNDANCY through ENT_API
-
ENVM through FR_FRAG
-
FR_LMI through GSR_ENV
-
GSRIPC through IF
-
IFS through ISA
-
ISDN through LCCOREDUMP
-
LCFE through MBRI
-
MBUS through MODEM
-
MODEMCALLRECORD through NSP
-
Glossary of Acronyms
-
Table Of Contents
IFS Messages
The following are Cisco IOS file system error messages.
Error Message%IFS-4-FILEMAX : Failed to open [chars], maximum open files [dec])
Explanation The router has reached the maximum number of files that may be open at one time.
Recommended Action Close some files and try the operation again. If this messages recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IFS-3-FS_CREATE_FAIL : Failed to create [chars] file system, [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, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IFS-3-FS_CREATE_FAIL2 : Failed to create [chars] simple file system, [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, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IFS-3-FSDUP : Failed to add [chars], filesystem prefix exists
Explanation A file system could not be added because another file system exists with the same name.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IFS-3-FSMAX : Failed to add [chars], maximum filesystems [dec]
Explanation The router has reached the maximum number of file systems that can be supported at one time.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IFS-3-FS_MISSING_FUNCTIONS : '[chars]' file system missing required functions, not created
Explanation Some file systems require a certain set of functions to be present in order to be usable. This file system does not support all the mandatory functionality.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
IGRP Messages
The following are Interior Gateway Routing Protocol (IGRP) error messages.
Error Message%IGRP-3-NOSOCKET : Unable to open socket for AS [dec]
Explanation 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.
ILACC Messages
The following are ILACC driver error messages.
Error Message%ILACC-4-BABBLE : Unit [dec], babble error, csr0 = [hex]
Explanation An Ethernet interface has malfunctioned.
Recommended Action Determine whether the malfunction stems from a software or hardware error by turning off all fast switching. Error messages showing that the packet is too large for the link indicate a software error at a high level. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information. Receiving no error messages indicates a hardware error. Repair or replace the controller.
Error Message%ILACC-3-BADUNIT : Bad unit number [dec]
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ILACC-5-COLL : Unit [dec], excessive collisions. TDR=[dec]
Explanation An Ethernet cable is broken or is not terminated, or the transceiver is unplugged. The TDR counter is an internal ILACC counter that counts the time (in ticks of 100 ns each) from the start of the 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%ILACC-1-INITFAIL : Unit [dec], initialization timeout failure, csr[dec]=[hex]
Explanation The hardware failed to initialize correctly.
Recommended Action Repair or replace the controller.
Error Message%ILACC-5-LATECOLL : Unit [dec], late collision error
Explanation An Ethernet transceiver is malfunctioning, the Ethernet is overloaded, or the Ethernet cable is too long.
Recommended Action Repair or replace the controller.
Error Message%ILACC-5-LOSTCARR : Unit [dec], lost carrier. Transceiver problem?
Explanation An Ethernet transceiver is unplugged or faulty.
Recommended Action Repair or replace the controller.
Error Message%ILACC-1-MEMERR : Unit [dec], memory error, csr[dec]=[hex]
Explanation An Ethernet interface has detected a hardware problem.
Recommended Action Repair or replace the controller.
Error Message%ILACC-3-OWNERR : Unit [dec], buffer ownership error, pak = [hex]
Explanation An Ethernet interface is malfunctioning, or an internal software error has occurred.
Recommended Action Repair or replace the controller.
Error Message%ILACC-3-SPURIDON : Unit [dec], spurious IDON interrupt, csr[dec]=[hex]
Explanation An Ethernet interface has generated a spurious Initialization Done interrupt.
Recommended Action Repair or replace the controller.
Error Message%ILACC-3-UNDERFLO : Unit [dec], underflow error
Explanation The Ethernet hardware is requesting data faster than the system can supply it. This condition might indicate that the system is at the limit of its performance.
Recommended Action A small number of underflows might not be a cause for concern. You can monitor underflows with the show interface command. Reducing the load on the router or installing a higher-performance router should alleviate this problem.
IMA Messages
The following are inverse multiplexing over ATM (IMA) error messages.
Error Message%IMA-5-ACTIVE_LINK_CHANGE : IMA Group [chars] now has [dec] active links, active link bitmap is [hex].
Explanation Active links were added or removed from the group; thereby changing its bandwidth.
Recommended Action No action is required.
Error Message%IMA-1-BAD_CMD : Command opcode [hex] on channel [dec] on slot [dec] was rejected.
Explanation The IMA firmware has rejected the command because of the current protocol state of the interface, or the opcode is undefined.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IMA-4-CLOCK_MODE_COMMON_DELAYED : Link [dec] will become the common transmit clock once it is added to group [chars]
Explanation The link configured as the common transmit clock is not a member of the group, so it cannot provide the clock. The group will use a common transmit clock that is automatically chosen from one of the other active links.
Recommended Action No action is required.
Error Message%IMA-1-DISCOVER : The Network Module in slot [dec] did not initialize.
Explanation The network module has failed its initialization.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IMA-1-DOWNLOAD_FAILED : Download of [chars] to failed to at [hex] on IMA Network Module in slot [dec].
Explanation An error occurred during the download of firmware to the IMA network module.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IMA-1-FPGA_DOWNLOAD_FAIL : FPGA Download on module in slot [dec] failed.
Explanation An error occurred during the download of the FPGA on the IMA network module.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IMA-1-INVALID_PCI_ID : The Network Module in slot [dec] reports an invalid [chars] device id of [hex].
Explanation The IMA network module hardware may be defective.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IMA-1-MAILBOX_FULL : The mailbox for channel [dec] on IMA Network Module in slot [dec] is completely full. Message [dec] was dropped.
Explanation The IMA network module mailboxes are full and cannot accept any more requests.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IMA-1-NETWORK_PROCESSOR_NOT_READY : Network processor on module in slot [dec] failed to come up.
Explanation An error has occurred during reset of the IMA network module.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IMA-1-NO_ATM_CHANNEL_AVAILABLE : Delaying activation of [chars] until a currently active interface is shutdown.
Explanation The IMA network module can support a maximum of four active interfaces at one time. Once more than four interfaces have been activated with the no shutdown command, each interface will wait for an existing interface to be shut down before becoming activated.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IMA-5-NO_LINK_MEMBERS : [chars] is using channel [dec] but has no configured links.
Explanation The IMA interface has been configured as Up, but it has no link members. The IMA interface cannot become active until active links are added to the group.
Recommended Action No action is required.
Error Message%IMA-1-NO_MAIL_REPLY : Timed out waiting for a response to command [hex] from slot [dec].
Explanation The IMA network module has failed to respond with the requested information. Information to be displayed by requesting an EXEC command or SNMP manager is incomplete. This is an extremely rare event and should only happen under severe system load.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IMA-1-PCMCIA : The IMA Network Module in slot [dec] is incompatible with the PCMCIA controller in the router.
Explanation The PCMCIA controller is contains downlevel software and is incompatible with the specified IMA network module.
Recommended Action Copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IMA-1-PROCESS_NEVER_RECEIVED_MAIL_REPLY : Previous process [dec] never received mail response from slot [dec].
Explanation The previous process request was terminated before receiving a mail reply.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IMA-1-SHARED_MEMORY_ERROR : Module in slot [dec] had a shared memory error.
Explanation The memory on the network module has failed the power-on diagnostic check.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IMA-4-TEST_LINK_DELAYED : Link [dec] will initiate the test pattern procedure once its added to group [chars].
Explanation The link chosen to transmit the test pattern is not a member of the group; therefore, the link cannot transmit the test pattern.
Recommended Action No action is required.
Error Message%IMA-4-TEST_LINK_STOPPED : Stopping test pattern procedure on group [chars].
Explanation The link transmitting the test pattern has been removed from the group, thereby stopping the transmission of the test pattern.
Recommended Action No action is required.
INTERFACE_API Messages
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 initialized
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%INTERFACE_API-4-BADPAKOUTPUT : pak->if_output is not initialized
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log, contact 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 [hex], ignoring
Explanation 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 help identify 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 swidb
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%INTERFACE_API-3-NODESTROYSUBBLOCK : The [chars] subblock named [chars] was not removed
Explanation A software error has occurred. This message is displayed when IDB subblocks cannot be removed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact 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, contact your Cisco technical support representative, and provide the representative with the gathered information.
IOCARD Messages
The following are I/O card-specific error messages.
Error Message%IOCARD-3-IONOT0 : IO card discovered in non-zero 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, contact 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] chassis
Explanation The software has identified and disabled the FE on the I/O card.
Recommended Action No action is required.
IP Messages
The following are IP error messages.
Error Message%IP-5-ACL : [chars]
Explanation An error 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 help identify 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, contact 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, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IP-4-CLASS : Bad IP address and mask [IP_address][IP_netmask] in class_resolve()
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log, contact 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 help identify 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, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IP-3-DESTHOST : src=[IP_address], dst=[IP_address], NULL desthost
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, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IP-4-DUPADDR : Duplicate address [IP_address] on [chars], sourced by [enet]
Explanation Another system is using your IP address.
Recommended Action Change the IP address of one of the two systems.
Error Message%IP-3-LOOPPAK : Looping packet detected and dropped -\nsrc=[IP_address], dst=[IP_address], hl=[int], tl=[int], prot=[int], sport=[int], dport=[int]
in=[chars], nexthop=[IP_address], out=[chars]\noptions=[chars]Explanation A looping packet has been detected. A very common cause is a misconfiguration of an IP helper address. The helper address should be the same address as that of the server of the intended service. Putting the address of the router in the helper address causes a routing loop to be created.
Recommended Action Analyze the source and destination address of the looped packets and verify that the configuration of IP helper addresses in the router is correctly pointing to the right device and is not pointing to the router itself.
Error Message%IP-3-STCKYARPOVR : Attempt to overwrite Sticky ARP entry: [IP_address], hw: [enet] by hw: [enet]\n
Explanation Multiple stations are configured with the same IP in a private VLAN. IP address stealing might have occurred.
Recommended Action Change the IP address of one of the two systems.
Error Message%IP-4-UNICASTRPF : IP unicast reverse-path check disabled on [chars]
Explanation Unicast Reverse Path Forwarding, which is invoked by entering the ip verify unicast reverse-path command, was disabled because 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 help identify 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, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IP-5-WEBINST_COMP : Selected IP address [IP_address]
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, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IP-5-WEBINST_KILL : Terminating DNS process
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, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IP-5-WEBINST_RESP : Sending DNS response to [IP_address] (request was for [IP_address])
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, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IP-5-WEBINST_START : Attempting web install from host [IP_address]
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, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IP-4-ZERO_ADDR : Zero MAC address for [IP_address] in ARP cache
Explanation An entry in the ARP cache has a null MAC address.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
IPA Messages
The following are Intelligent Port Adapter error messages.
Error Message%IPA-3-INVMBXCMD : [chars]: invalid mailbox command: [hex]
Explanation A subsystem has attempted to register a mailbox command that is out of range.
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 help identify 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, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IPA-3-NEVER : bay [[chars]] mailbox response timed out after ([int] + [int]) usecs, mbx=[hex]
Explanation A mailbox command that was sent from the driver to the channel port adapter was not completed within the expected time limit. As a result of this error, the channel port adapter driver will reset the port adapter and reload microcode to it.
Recommended Action The reset and reload should rectify the problem. If the problem is not fixed, reenter the microcode reload command.
If this error recurs, record the output from the following commands to gather data that may help identify the nature of the error:
show tech
dir slot0:
dir slot1:
show logIf you cannot determine the nature of the error from the error message text or from the output of these commands, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IPA-3-PORTCONN : bay [[int]] failed to establish [chars] connection ([hex])
Explanation An attempt to establish a console or debugger connection with the channel port adapter 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 help identify 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, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IPA-3-PORTIOKILL : Port IO [chars] process terminating.
Explanation An unexpected termination of a port I/O process 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 help identify 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, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IPA-3-UKNMBXCMD : [chars]: unknown mailbox command: [hex] [hex] [hex] [hex]
Explanation The channel port adapter has sent a mailbox command that the driver did not expect. This error may occur if there is a version mismatch between the system image and the microcode.
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 help identify 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, contact your Cisco technical support representative and provide the representative with the gathered information.
IPACCESS Messages
The following are IP security error messages.
Error Message%IPACCESS-2-NOMEMORY : Alloc fail for acl-config buffer. Disabling distributed mode on lc
Explanation A buffer could not send access-list configuration to the line cards because memory could not be allocated to the buffer.
Recommended Action Enter the 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 ACL chunk was received but was rejected because it was larger than the maximum size allowed. The maximum size allowed for an ACL chunk is IPACCESS_LARGE_CHUNK_SZ.
Recommended Action No action is required.
Error Message%IPACCESS-2-WRONGSIZE : Incorrect length acl ipc xdr of type=[chars] len=[dec] received
Explanation The RP has sent an ACL configuration message that was 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, contact your Cisco technical support representative, and provide the representative with the gathered information.
IPC Messages
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 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 help identify 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, contact 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 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 help identify 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, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IPC-3-DELETED : Attempt to delete an IPC message ([hex]) a second time
Explanation An internal inconsistency was found in some IPC data structures.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show ipc status and show ipc queue commands to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show ipc status and show ipc queue command output, contact 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 memory 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 help identify 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, contact 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 has requested a message that is too large for the IPC system.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show ipc status command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show ipc status command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IPC-5-INVALID : [chars] [chars]=[hex]
Explanation An IPC message that has an 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 help identify 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, contact 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 IPC message with an invalid size has been 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 help identify 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, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IPC-2-LOCK : Lock done a deleted element
Explanation An internal inconsistency was found in some 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 help identify 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, contact 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 IPC message header cache has fallen 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 ipc status command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show ipc status command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IPC-2-NO_ACK_HANDLER : No handler for ACK with data.
Explanation A preview function appended data to an acknowledgment at the sender, but there is no corresponding acknowledgment handler at the receiver.
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 help identify 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, contact 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 emptied
Explanation The specified 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 ipc status command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show ipc status command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IPC-5-NODELFUNC : Delayed init function not available
Explanation The IPC application cannot be initialized because its initialization function does not appear in the IPC initialization function list.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify 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, contact 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 routine
Explanation The 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 help identify 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 output, contact 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 IPC protocol subsystem could not obtain the memory it needed.
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 help identify 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, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IPC-5-NULL : [chars] [chars]=[hex], seq = [hex]
Explanation An 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 help identify 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, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IPC-5-NULLDELFUNC : Passed Null Delayed function to register
Explanation 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 help identify 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, contact 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 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 ipc status command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show ipc status command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IPC-5-OUTPUT_FAIL : Num [dec] Func=[hex] Seat: ID=[hex] [chars] Sent [dec] Heard [dec]
Explanation The IPC output has failed in the function for the 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 help identify 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, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IPC-2-PRECLOSE : IPC port pre-closure overflow : [hex] : [hex]
Explanation the IPC defer table has overflowed because an application tried to close an IPC port when there were messages pending in the retransmit queue.
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 help identify 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, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IPC-5-QFULL : Q=[hex] [chars] [dec]
Explanation The 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 help identify 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, contact 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 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 help identify 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, contact 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 VIP card generated this message. The error message has been passed up to the RP or RSP for display. This message appears only if the user has entered the service slave-log global configuration command.
Recommended Action The console will start displaying the log messages generated by the VIP card. The message generated from the VIP card along with the output generated by entering the show tech-support command will help to identify the nature of the problem.
Error Message%IPC-2-TEST : IPC test: [chars]
Explanation The IPC test routines have finished running.
Recommended Action This message is an IPC test message only. No action is required.
Error Message%IPC-2-UNLOCK : Unlock done on already unlocked element
Explanation An internal inconsistency was found in some IPC data structures.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
IPCGRP Messages
The following are Route Processor interprocess communication error messages.
Error Message%IPCGRP-3-CARDERR : [chars]
Explanation An IPC card has registered itself to the IPC master twice. The card malfunctioned and its IPC is not active.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact 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 Operational errors occurred when the IPC was processing a command.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IPCGRP-3-CREATE_FAIL : [chars] [chars]
Explanation An IPC port has failed to be created on the RP.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact 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 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, contact 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 REXEC-On IPC command was the wrong size.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IPCGRP-3-INVNUM : [chars] ([int])
Explanation The IPC application tried to send a message that was larger than IPC could handle. The message was not transmitted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IPCGRP-3-MSGERR : [chars] ([int])
Explanation The slave 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, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IPCGRP-3-NBLKCMD : [chars]
Explanation A nonblocking 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, contact 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 IPC message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IPCGRP-3-NULLMSG : Null [chars] ipc message
Explanation An unexpected empty IPC message was received.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IPCGRP-3-NULLREXECCMD : Received empty ipc rexec cmd message
Explanation A REXEC-On IPC command failure has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IPCGRP-3-REXEC : [chars]
Explanation A REXEC-On Interprocess Communication command failure has occurred. This message appears very often along with %IPCGRP-3-SYSCALL messages; however, the same troubleshooting procedure applies. This message might appear if the primary and standby Gigabit Route Processors do not have the same Cisco IOS software release.
Recommended Action Ensure that the primary and standby Gigabit Route Processors are using the same Cisco IOS software image and synchronize the images if necessary. Follow the Recommended Action for the %IPCGRP-3-SYSCALL message. It is also strongly recommended to search for all known software errors with the Software Bug Toolkit. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact 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 IPC card is either 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, contact 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 IPC kernel system call error has occurred. This condition can occur if certain IPC messages sent from the RP to the LC block IPC messages. The RP sets a timer waiting for a response. If it does not receive a response in the given timeout period, the message will be generated.
IPCLC Messages
The following are Internet Router line card interprocess communication error messages.
Error Message%IPCLC-3-EVENT : Event ([int]) [chars] error
Explanation 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, contact 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 An 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, contact 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 An IPC event processing error has occurred at the line card interrupt level.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IPCLC-3-MSGERR : [chars] ([dec])
Explanation The line card IPC cannot register with the route processor and therefore it cannot exchange messages with the route processor.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact 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, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IPCLC-3-REPLY : Reply (to cmd [int]) [chars] error
Explanation 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, contact 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-RP-command operation error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
IPCOIR Messages
The following are interprocess communication (IPC) online insertion and removal (OIR) error messages.
Error Message%IPCOIR-3-BADIPHOST : Bad IP address or host name [chars]
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%IPCOIR-3-BADLCAPI : Incorrect API message version [hex]
Explanation The line card and Cisco IOS software images have lost their synchronization.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%IPCOIR-3-BADMESSVER : Incorrect message version obj [hex] op [hex] version [hex]
Explanation The line card and Cisco IOS software images have lost their synchronization.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%IPCOIR-3-BOGUSCARD : Bogus cardtype [dec]
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%IPCOIR-5-CARD_LOADING : Loading card [dec]
Explanation Software is being downloaded to a line card.
Recommended Action No action is required.
Error Message%IPCOIR-3-FLASHFAIL : Couldn't load [chars]...\n
Explanation The indicated image is inaccessible.
Recommended Action Check the file name of the image.
Error Message%IPCOIR-3-IMAGEVERSION : Image version stamp missing
Explanation The image that was loaded did not contain a recognizable version stamp.
Recommended Action Replace the image with bits that are known as good, and retry the operation.
Error Message%IPCOIR-3-IPC_DOWN_BUG : [chars]: IPC unexpectedly down
Explanation An internal error has occurred. The system should retry this operation and normal system operation will continue.
Recommended Action No action is required.
Error Message%IPCOIR-3-LOADER_DAEMON_FAIL : Couldn't create card loader daemon, type [dec] slot [dec]
Explanation The firmware for the line card could not be loaded.
Recommended Action Reboot the DSLAM.
Error Message%IPCOIR-3-LOADER_DNLD_NOBUF : Buffer allocation failed
Explanation The buffer downloader could not allocate a message buffer.
Recommended Action Reboot the chassis.
Error Message%IPCOIR-3-LOADER_DNLD_REJECT : Buffer download to slot [dec] rejected
Explanation The line card buffer download server has rejected the download.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%IPCOIR-5-LOADER_ENTER_BOOT : Linecard entering boot image, download will restart, slot [dec]
Explanation The line card is entering the boot image. If the line card contains 32kb of SRAM, this process might take a long period of time to complete.
Recommended Action Wait for the process to complete.
Error Message%IPCOIR-3-LOADER_IPC_FAIL : IPC failed, slot [dec]
Explanation The IPC protocol for the Cisco IOS software has reported an unexpected error.
Recommended Action Ensure that the specified card is still plugged in.
Error Message%IPCOIR-3-LOADER_SERVER_FAIL : Remote server refused to load slot [dec]
Explanation The remote server could not load the line card software. The loading attempt will be retried.
Recommended Action Reseat the line card. If the message recurs, reboot the chassis.
Error Message%IPCOIR-3-RECEIVE_CALLBACK_BUG : Cardoir_receive_callback: slot ([dec]) unsupported cardtype [dec]
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%IPCOIR-3-RECEIVE_CALLBACK_CARD_MISMATCH : Cardoir_receive_callback: slot ([dec]) provisioned cardtype is different than [dec]
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%IPCOIR-3-RECEIVE_CALLBACK_UNSOLICITED : Cardoir_receive_callback: slot [dec] unsolicited case!
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%IPCOIR-3-STATE_MACHINE_BUG : Cardoir_loading called, should never happen, recovering.
Explanation The state of the line card could not be recognized. The line card is being reloaded.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%IPCOIR-3-STATE_MACHINE_BUG2 : Cardoir_insert_card: already have [hex], removing.
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%IPCOIR-3-TFTPFAIL : Loading [chars] failed...\n
Explanation The indicated image is inaccessible.
Recommended Action Check file permissions and the connectivity of the network.
Error Message%IPCOIR-3-WAKEUP_REASON_BUG : [chars]: unexpected wakeup major [hex] minor [hex]
Explanation An internal error has occurred.
Recommended Action Reboot the chassis.
IPC_RPM Messages
The following are interprocess communication (IPC) error messages.
Error Message%IPC_RPM-3-CARDERR : [chars]
Explanation The IPC card has 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, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IPC_RPM-3-ECC : WARNING: ECC Single Bit Error Correction
Explanation An ECC single-bit error was detected and corrected.
Recommended Action Enter the debug rpm ecc command to look at the total number of ECC errors that have occurred since the system was booted. Enter the debug rpm ecc command with the number argument, where number is the number of ECC errors that will cause a switchover, to set the number of ECC errors that will cause a switchover.
Error Message%IPC_RPM-3-INVMSG : [chars] ([dec])
Explanation An invalid IPC message was received during cc command execution.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IPC_RPM-3-INVNUM : [chars] ([dec])
Explanation The IPC application tried to send a message that was larger than IPC could handle. The message was not transmitted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IPC_RPM-3-NOBUF : [chars]
Explanation The IPC has run out of MEMD buffers.
Recommended Action Reduce the number of applications currently running on the IPC. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IPC_RPM-3-SEATERR : [chars] [chars]
Explanation The ID associated with an 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, contact your Cisco technical support representative, and provide the representative with the gathered information.
IPC_RSP_CBUS Messages
The following are interprocess communication (IPC) ciscoBus (CBUS) error messages.
Error Message%IPC_RSP_CBUS-3-CARDERR : [chars]
Explanation An IPC card has registered itself to the IPC master twice. The card malfunctioned, and its IPC is not active.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IPC_RSP_CBUS-3-INVNUM : [chars] ([dec])
Explanation The IPC application tried to send a message that was larger than the IPC could handle. Therefore, the message was not transmitted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact 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 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, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IPC_RSP_CBUS-3-NOBUF : [chars]
Explanation The IPC has run out of memory device (MEMD) buffers.
Recommended Action Reduce the number of applications currently running on the IPC. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%IPC_RSP_CBUS-3-NOHWQ : Hardware queue for card at slot [dec] not found
Explanation The IPC messages cannot be transmitted because of a missing hardware queue. The messages were discarded and subsequent messages will not be transmitted to the specified card.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact 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 IPC card is either missing, duplicated, or cannot be created.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
IPFAST Messages
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 help identify 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, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IPFAST-3-INTLEV : Cache update request at interrupt level: [IP_address]([chars])->[IP_address]([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, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IPFAST-4-INVALFAIL : Error invalidating IP fast cache due to memory shortage
Explanation A memory shortage has occurred and could result in incorrect switching decisions. This message is for debugging purposes only.
Recommended Action Upgrade the router memory. If this message persists, indicating a continued condition, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IPFAST-3-INVALIDADDR : Invalid cache destination [IP_address]/[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, contact 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 the specified interface.
Recommended Action No action is required.
Error Message%IPFAST-6-INVALREQ : Cache invalidation request for [chars]
Explanation The system is invalidating all cache requests for the specified interface.
Recommended Action No action is required.
Error Message%IPFAST-2-IPCACHEINIT : Error initializing IP fast cache structures
Explanation A programming error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IPFAST-6-PAKSHORT : Packet too short from [IP_address], datagram size [dec], tl [dec]
Explanation An IP packet that is too short was received.
Recommended Action No action is required.
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 help identify 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, contact 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 [IP_address]/[dec] (expected [hex], got [hex])
Explanation A problem has occurred with the IP route cache.
Recommended Action This message is for debugging purposes only. 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 on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IPFAST-2-RADIXINIT : Error initializing IP fast cache structures
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 help identify 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, contact 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 [IP_address]/[dec] (expected [hex], got [hex])
Explanation A problem has occurred with the IP route cache.
Recommended Action This message is for debugging purposes only. 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 on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IPFAST-3-SANITY : Found existing [chars] specific entry [IP_address][IP_netmask]..[IP_netmask]->[IP_address] ([chars]) when attempting to create [IP_address][dec]..[dec]->[IP_address] ([chars])
Explanation A problem has occurred with the IP route cache.
Recommended Action This message is for debugging purposes only. 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 on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
IPFLOW Messages
The following are IP flow error messages.
Error Message%IPFLOW-2-CACHEINIT : Error initializing IP flow cache
Explanation Initialization of the flow cache could not be accomplished because of low 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 help identify 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, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IPFLOW-2-EXPORTINIT : Error initializing Flow Export queue
Explanation The initialization of the flow export queue 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%IPFLOW-2-PROCESSINIT : Error initializing Flow background process
Explanation The initialization of the flow background process 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.
IPM_C54X Messages
The following are Voice over IP (VoIP) driver error messages.
Error Message%IPM_C54X-3-DSP_ALARM_INDICATION : DSP [dec] Sending alarm indication
Explanation The 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, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IPM_C54X-1-DSP_TIMEOUT : dsp [dec] NOT RESPONDING.
Explanation The DSP driver cannot queue messages up to the DMA engine for transmission.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information. Reset the DSPs on this port module.
Error Message%IPM_C54X-3-EPIC_NOT_RESPONDING : Epic TDM Switch failure\n
Explanation The EPIC 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, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IPM_C54X-3-ERROR_INIT_BLDR : DSP [dec] Unable to download the Boot loader firmware, ret = [hex]
Explanation An error occurred during initialization of the DSP with the bootloader firmware.
Recommended Action Power down the system, reinsert the port module, and reboot the system. If this message recurs, copy the message exactly as it appears on the console or in the system log, contact 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 [hex]
Explanation An error occurred during initialization of the DSP with the application overlay firmware.
Recommended Action Power down the system, reinsert the port module, and reboot the system. If this message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IPM_C54X-3-HOST_XMIT_BLOCKED : Host is unable to transmit packets to DSP [dec]
Explanation The software is unable to communicate with one of the DSPs.
Recommended Action Reload the Cisco IOS software image running on the host. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IPM_C54X-3-IDB_CREATE : Unable to allocate IDB\n
Explanation The DSP Interface IDB cannot be allocated.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact 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 indication
Explanation The DSP is unable 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, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IPM_C54X-3-INSUFICIENT_SPMMS : [dec] SPMM Modules to support this configuration
Explanation More than one SPMM module is required for the specified configuration.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IPM_C54X-3-NO_BUFFERS : No buffers available for DSP buffer pool
Explanation Buffers to the 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, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IPM_C54X-3-NODSP : Can't get dsp resources\n
Explanation There are more VICs in the router than the DSPs can support.
Recommended Action Enter the show diag command to determine how many DSPs are present in the router. Upgrade the DSP module to obtain more DSPs.
Error Message%IPM_C54X-1-NO_RING_DESCRIPTORS : No more ring descriptors available on [dec] slot.
Explanation The DSP driver cannot queue messages up to the DMA engine for transmission.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information. Reset the DSPs on this port module.
Error Message%IPM_C54X-1-TOOBIG : DSP [dec], packet(size [dec]) too big.
Explanation A packet greater than 256 bytes has been received on this interface.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
IPMCAST Messages
The following are Cisco 12000 series Internet router line card IP multicast error messages.
Error Message%IPMCAST-5-ERR : [chars] [chars]=[hex]
Explanation An error has occurred while processing an IP multicast packet.
Recommended Action Copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
IPM_DSPRM Messages
The following are Digital Signal Processor (DSP) Resource Manager error messages.
Error Message%IPM_DSPRM-3-ERROR_DSP_BOOTLDR_DNLD : Boot loader dwonload failed for dsp [dec] in dsp group [dec]
Explanation The DSP boot loader firmware download was not successful.
Recommended Action Remove and reinstall the DSP module. If removal and reinstallation does not resolve the error, replace the DSP module.
Error Message%IPM_DSPRM-3-ERROR_DSP_FW_DNLD : BAD restart indication received from dsp [dec] in dsp group [dec]
Explanation The DSP firmware download was not successful.
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 help identify 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, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IPM_DSPRM-3-ERROR_DSP_INIT : BAD init config response received from dsp [dec] in dsp group [dec]
Explanation The initial configuration has failed in the DSP firmware.
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 help identify 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, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IPM_DSPRM-3-ERROR_DSP_OPERATION : ALARM indication received from dsp [dec] in dsp group [dec]
Explanation The DSP has failed and has started an alarm.
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 help identify 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, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IPM_DSPRM-3-ERROR_FIRMWARE_DOWNLOAD : Could not bring DSP [dec] in DSP group [dec] in service
Explanation The DSP did not start after repeated attempts to download the firmware.
Recommended Action Check to see if the DSP has failed and reload the trunk. However, if this message persists, indicating a continuing condition, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IPM_DSPRM-3-ERROR_NO_DSP_RESOURCES : Insufficient DSP resources [chars]
Explanation DSP resources are not available either to open a voice channel or to run a voice codec.
Recommended Action Check the DSP resource usage and see if the total number of active calls has exceeded the limits.
Error Message%IPM_DSPRM-3-ERROR_PORT_NOT_FOUND : Port [dec]/[dec] not found in any DSP group
Explanation A T1 port has not been added to any DSP group.
Recommended Action Check if tdm-clock has been configured for this port.
IPM_NV_EEPROM Messages
The following are integrated port module NVRAM driver error messages.
Error Message%IPM_NV_EEPROM-3-BADNV : Detected invalid NVRAM size: [dec] bytes
Explanation The size of the specified NVRAM is not supported. The NVRAM may be defective.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IPM_NV_EEPROM-3-NVERASEFAIL : Failed to erase config due to internal error
Explanation The password protection feature has failed to erase the configuration because of an internal error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
IPMOBILE Messages
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 system is attempting to continue, but IP Mobility processing may be impaired.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, noting any IP Mobility problems that you are experiencing. Contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IPMOBILE-3-NOSOCKET : Unable to open socket
Explanation 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] [IP_address] - errcode [chars] ([dec]), reason [chars] ([dec])
Explanation A security violation occurred during a registration attempt.
Recommended Action This is an informational message only. No action is required.
IPRT Messages
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 BGP community list number.
Recommended Action Check the system configuration to ensure that the specified community list falls within the valid range.
Error Message%IPRT-2-COMPRESS : Bad route_compress() call, sdb= [hex]
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log, contact 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 is preventing 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, contact 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 [IP_address], [dec] max
Explanation A software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Message%IPRT-3-RIB_LOOP R Resolution loop formed by routes in RIB
Explanation RIB route producers have installed routes in the RIB that form a loop during resolution.
Recommended Action Resolve the RIB route loop:
1) Determine which routes are involved in the loop be entering the show ip route loops command.
2) Correct the protocols owning the routes involved in the loop in order to modify or remove one of the routes so the loop is broken.
If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IPRT-4-ROUTECOUNTNEGATIVE : IP route counter negative - [chars], [IP_address] Attempt: [dec]
Explanation An attempt was made to decrement the IP route counter into a negative value.
Recommended Action Use the clear ip route * command to reset the route counter. If this message persists, indicating a continuing condition, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IPRT-3-ROUTELIMITEXCEEDED : IP routing table limit exceeded - [chars], [IP_address][IP_netmask]
Explanation The number of routes in the specified 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.
IP_SNMP Messages
The following are Simple Network Management Protocol (SNMP) error messages that are specific to IP.
Error Message%IP_SNMP-4-NOTRAPIP : SNMP trap source [chars] has no ip address
Explanation The user entered an snmp-server trap-source command. The interface that was requested to be used as the source address has no address associated with it. The SNMP trap is being sent anyway, but with a different source address from the one the user intended.
Recommended Action There are two possible solutions. Either enter a no snmp-server trap-source command to disable the request for a specific source IP address or add an IP address to the interface referenced in the snmp-server trap-source configuration command.
Error Message%IP_SNMP-3-SOCKET : can't open UDP socket
Explanation The SNMP server was unable to open a port for receiving or transmitting SNMP requests. This 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 low memory.
Recommended Action Configure at least one interface with an IP address or specify the no snmp-server command to remove the SNMP server process. Contact 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 [IP_address], datagram size [int], udp length [int]
Explanation An incoming SNMP packet had a length field that was so large that the system assumed it was in error. The system reacted correctly to bad external data. Since SNMP packets should originate from systems under the same administration, this situation may indicate that there was a problem in the networking layer of the network host used to originate the SNMP request. However, if the SNMP packet originated outside the local administrative domain, the error could indicate a failed attempt at security penetration, in which case that site should be watched more closely.
Recommended Action If the origin is local, no action is required. If the origin is determined to be malicious, either contact the administrator of the originating site or install filters to prevent access by that site, as circumstances warrant.
IPX Messages
The following are Internetwork Packet Exchange (IPX) error messages.
Error Message%IPX-3-BADCOUNT : Bad IPX server count. [chars] [dec], [chars] [dec]
Explanation The internal SAP service count does not match the number of services currently present and displayed by the show ipx servers command.
Recommended Action If this message recurs, report the problem to your Cisco technical support representative, along with the output of the show ipx servers command taken before the message appeared and again after the message appeared, and provide the representative with the gathered information.
Error Message%IPX-3-BADHASHTABLE : Consistency check failed for SAP table [dec].
Explanation An internal SAP table consistency check has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact 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 SAP update could not be sent because sending the update might cause the SAP tables between peers to lose synchronization.
Recommended Action Increase the output SAP delay on the listed interface to reduce buffer usage. If the message remains after changing the delay, copy the error message exactly as it appears on the console or in the system log, contact 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 an 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 on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information. 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][hex] [chars][hex] [chars][dec] [chars][hex] [chars][hex] [chars][hex]
Explanation The user attempted to add an IPX SAP service entry that already exists in the current internal table.
Recommended Action Report the error messages and the tracebacks following them exactly as they appear on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IPX-3-BADPATHS : Invalid number of paths ([dec]) for [APOLLO/XNS/UB]
Explanation An internal inconsistency was detected in the IPX routing table structure.
Recommended Action Copy and save this message. If possible, clear the IPX routing table by issuing the clear ipx route command. (This actions will result in the loss of connectivity until the routing table is rebuilt.) If this message recurs, copy the error message exactly as it appears on the console or in the system log including information from the show ipx route command. Contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IPX-3-BADRDBDATA : Inconsistency in the [chars] LSP Linkage data structure detected.
Explanation An internal inconsistency was detected in the data area used by the NLSP to link LSPs in the RDB or SRDB internal routing table structure.
Recommended Action Copy and save this message. If NLSP is not running, this message could mean that there is a software or hardware problem that is corrupting memory. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IPX-6-NOVACCESSLOG : [chars] [chars] [chars] [chars] [hex].[enet] [chars] [hex].[enet] [dec] pkt[chars]
Explanation If IPX access violation logging is enabled, this message is 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 networks. The number of directly connected IPX networks cannot exceed [dec]
Explanation The limit of connected IPX networks has been reached. There can be a maximum of 200 directly connected IPX networks. Additional IPX interfaces cannot be configured.
Recommended Action Do not configure IPX on additional interfaces. Remove IPX configuration commands from inactive interfaces.
ISA Messages
The following are Integrated Services Adapter (ISA) error messages.
Error Message%ISA-1-ALIGN : Alignment failure on packet buffer: [hex]
Explanation A software error has occurred. The ISA driver detected that the buffer is not aligned correctly.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ISA-1-ERROR : [chars]
Explanation An error occurred in the application using ISA.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ISA-6-INFO : [chars]
Explanation This is an informational message from ISA.
Recommended Action No action is required.
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 ISA driver has failed to initialize at the specified point.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ISA-1-INITFAIL : Slot [dec]: [chars]
Explanation The ISA driver has failed to initialize at the specified point.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ISA-1-NOMEMORY : [chars] creation failed for slot [dec]
Explanation The 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 on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ISA-1-OWNER : [chars] packet buffer, pak=[hex]
Explanation A software or hardware error has occurred. The ISA driver detected that the buffer ring is in an inconsistent and unrecoverable state.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ISA-6-SHUTDOWN : [chars] shutting down
Explanation The specified 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 system has received a packet that is larger than the allowed size.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.