-
Cisco IOS Release 12.4 System Messages, Volume 1 of 2
-
System Messages Overview
-
AAA through ASPP
-
AT through BGP
-
BIT through C6KPWR
-
C6MSFC through CHOPIN_MAINBOARD_ASYNC_PQII
-
CI through COT
-
CPAD through DBUS
-
DCV through DSCREDCLK
-
DSI through ENT
-
ENV_MON through FR_FRAG
-
FR_LMI through GSR_ENV
-
GSRIPC through IF
-
IFINDEX through ISA
-
ISDN through LCCOREDUMP
-
LCINFO through MBRI
-
Volume 1 Glossary
-
Table Of Contents
IFINDEX Messages
The following are SNMP IF-MIB persistence messages.
Error Message%IFINDEX-4-NOIFINDEX : All SNMP if indices are exhausted
Explanation All SNMP Interface Group MIB Module (IF-MIB) indices are exhausted. Interfaces will not get an IF index to register to the IF-MIB.
Recommended Action Unavailable.
IFS Messages
The following are Cisco IOS file system 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) 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 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.
ILPM_FAULT Messages
The following are Inline Power Management (ILPM)-related messages.
Error Message%ILPM_FAULT-4-ILPM_ERROR : Error : [chars]
Explanation An error has occurred in the inline power management system.
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%ILPM_FAULT-5-ILPM_NOTICE : Notice: [chars]
Explanation This message provides information regarding inline power management.
Recommended Action This is an informational message only. No action is required.
Error Message%ILPM_FAULT-5-ILPM_WARNING : Warning: [chars]
Explanation This message provides warning-level information regarding inline power management. In general, this message informs the user of a problem that has occurred as a result of an invalid configuration. The specific message text provides more details on the exact nature of the problem.
Recommended Action Correct the invalid configuration as specified in the message text and retry the operation. 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.
IMA Messages
The following are inverse multiplexing over ATM (IMA) 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.
Error Message%IMA-4-CLOCK_MODE_COMMON_DELAY : Link [chars] 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-4-CLOCK_MODE_COMMON_SWITCH : Switching common transmit clock for group [chars] to link [chars].
Explanation The link providing the common transmit clock has been removed fromthe 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-4-TEST_LINK_DELAY : Link [chars] 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, thereby preventing the transmission of 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.
IMA_LINK Messages
The following are index object messages.
Error Message%IMA_LINK-3-LCD : [chars] [chars] [chars] [chars] [chars]
Explanation A loss of cell delineation has occurred on the user or network side of the IMA link. The local loop or switch of the carrier, or the router or other CPE equipment of the user has failed.
Recommended Action Check the ATM link layer and IMA configurations for accurate HEC or cell delineation settings, or 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.
INDXOBJ Messages
The following are index object messages.
Error Message%INDXOBJ-3-INTERRUPT : index object routine [chars] called from interrupt context
Explanation An inappropriate index object routine has been called from the
Recommended Action interrupt routine.
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.
INT Messages
The following are Channel Interface Processor (CIP) messages for the interrupt handler interface.
Error Message%INT-0-ADDFAST : Add: Invalid fast io code [dec]
Explanation A request was made to add an interrupt handler to the fast I/O path with an invalid interrupt type. This is a fatal internal logic 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.
Error Message%INT-0-ADDFLIH : Add: Invalid interrupt code [dec]
Explanation A request was made to add an interrupt handler with an invalid interrupt number. This is a fatal internal logic 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.
Error Message%INT-0-ADDFULL : Add: Invalid full io code [dec]
Explanation A request was made to add an I/O interrupt handler with an invalid interrupt code. This is a fatal internal logic 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.
Error Message%INT-0-ADDTRAP : Add: Invalid trap code [dec]
Explanation A request was made to add a system call handler with an invalid system call number. This is a fatal internal logic 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.
Error Message%INT-0-REMOVEFAST : Remove: Invalid fast io code [dec]
Explanation A request was made to remove an interrupt handler from the fast I/O path with an invalid interrupt type. This is a fatal internal logic 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.
Error Message%INT-0-REMOVEFLIH : Remove: Invalid interrupt code [dec]
Explanation A request was made to remove an interrupt handler with an invalid interrupt number. This is a fatal internal logic 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.
Error Message%INT-0-REMOVEFULL : Remove: Invalid full io code [dec]
Explanation A request was made to remove an I/O interrupt handler with an invalid interrupt code. This is a fatal internal logic 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.
Error Message%INT-0-REMOVETRAP : Remove: Invalid trap code [dec]
Explanation A request was made to add a system call handler with an invalid system call number. This is a fatal internal logic 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.
INTERFACE_API Messages
The following are 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-INVALIDSUBBLOCKPARAMETERS : Invalid subblock parameters for [chars] were supplied.
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 idb and show tech-support commands to gather data that may help identify the nature of the error. 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://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%INTERFACE_API-1-NAMESTRTOOLONG : Interface name [chars].[int] exceeded maximum allowed length [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, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%INTERFACE_API-3-NOADDSUBBLOCK : The [chars] subblock named [chars] was not added to [chars]
Explanation A software error has occurred. IDB subblocks could not be added.
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-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-NOMOREHWIDBNUMBERS : No more hardware IDB numbers can be issued. The maximum allowed numbers, [dec], has been reached for this platform.\n
Explanation No more hardware IDB numbers can be issued. The maximum allowed number of IDBs has been reached for this platform.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show idb command to gather data that may help identify the nature of the error. 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, show tech-support, and show idb commands and your pertinent troubleshooting logs.
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.
Error Message%INTERFACE_API-1-NOMORESWIDBNUMBERS : No more software IDB numbers can be issued. The maximum allowed numbers, [dec], has been reached for this platform.\n
Explanation No more hardware IDB numbers can be issued. The maximum allowed number of IDBs has been reached for this platform.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show idb command to gather data that may help identify the nature of the error. 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, show tech-support, and show idb commands and your pertinent troubleshooting logs.
Error Message%INTERFACE_API-3-NOSUBBLOCK : [chars] subblock does not exist on interface [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%INTERFACE_API-3-SUBNUMDBERR : subnum [hex] error in [chars]
Explanation A software error has occurred. A problem has occurred with a sub-number descriptor block.
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-4-TBLERROR : A error occurred while using the Index Table utility for [chars].
Explanation A software error has occurred. An index table feature could not be used successfully.
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 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.
IOS_RESILIENCE Messages
The following are Cisco IOS software image and configuration resilience messages.
Error Message%IOS_RESILIENCE-5-ARCHIVE_ERROR : Error creating archive on device [chars]
Explanation A condition that is required for configuring the Cisco IOS software resilience feature could not be met.
Recommended Action Check free space on storage device.
Error Message%IOS_RESILIENCE-5-CONFIG_RESIL_ACTIVE : Successfully secured config archive [[chars]]
Explanation The Cisco IOS software resilience feature has successfully obtained a copy of the running configuration.
Recommended Action No action is required.
Error Message%IOS_RESILIENCE-5-CONFIG_RESIL_INACTIVE : Disabled secure config archival [removed [chars]]
Explanation The Cisco IOS configuration resilience parameter has been disabled. The configuration archive has been removed.
Recommended Action No action is required.
Error Message%IOS_RESILIENCE-5-CONFIG_UPDATE : Config archive updated to [chars]
Explanation The Cisco IOS software resilience feature has successfully updated the archived configuration file.
Recommended Action No action is required.
Error Message%IOS_RESILIENCE-5-IMAGE_NOTFOUND : Running image not found on removable disk
Explanation A condition that is required for configuring the Cisco IOS software resilience feature was not met.
Recommended Action Ensure that the running image resides in local storage.
Error Message%IOS_RESILIENCE-5-IMAGE_RESIL_ACTIVE : Successfully secured running image
Explanation The Cisco IOS software resilience feature has obtained a copy of the running image.
Recommended Action No action is required.
Error Message%IOS_RESILIENCE-5-IMAGE_RESIL_INACTIVE : Disabled secure image archival
Explanation The Cisco IOS software resilience feature has been disabled. The image can now be deleted.
Recommended Action No action is required.
Error Message%IOS_RESILIENCE-5-IMAGE_UPDATE : Image archive updated to [chars]
Explanation The Cisco IOS software resilience feature has successfully updated the archived image file.
Recommended Action No action is required.
Error Message%IOS_RESILIENCE-5-INVALID_IMAGE : [chars] is not a valid cisco image
Explanation A condition that is required for configuring the Cisco IOS software resilience feature was not met.
Recommended Action Ensure that the Cisco IOS software image that resides in storage is not corrupted.
Error Message%IOS_RESILIENCE-5-NO_SUPPORTED_DEVICE : No ATA disk found for storing archives
Explanation A required storage device was not found on this router.
Recommended Action Insert an ATA-compliant disk in one of the storage slots of the router.
Error Message%IOS_RESILIENCE-5-NON_CONSOLE_ACCESS : Non console configuration request denied for command "[chars]"
Explanation An attempt was made to configure a function that requires console access.
Recommended Action Enter this command while in a console session only.
Error Message%IOS_RESILIENCE-5-NOSPACE : Not enough space on storage device to create [chars] archive
Explanation The storage device (disk0 or disk1) does not have sufficient free space to create a new archive.
Recommended Action Remove unused files from the storage device to create sufficient space for the new archive.
IP Messages
The following are IP 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 might 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 might 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-4-IPPOOLS : Detected a local pool and a DHCP pool with the same name: [chars]
Explanation A local pool and a DHCP pool have been configured with the same name. This condition may cause conflict during address allocations.
Recommended Action Change the name of one of the two pools.
Error Message%IP-3-LOOPPAK : Looping packet detected and dropped -\n src=[IP_address], dst=[IP_address], hl=[int], tl=[int], prot=[int], sport=[int], dport=[int]\n in=[chars], nexthop=[IP_address], out=[chars]\n options=[chars]
Explanation A software error 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-3-STCKYARPOVR : Attempt to overwrite Sticky ARP entry: [IP_address], hw: [enet] by hw: [enet]
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-5-TURBOACL : [chars]
Explanation An error occurred while the TURBO ACL function was being initialized.
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%IP-4-UNICASTRPF : IP unicast reverse-path check disabled on [chars]
Explanation The IP unicast RPF feature was disabled because CEF was disabled either through configuration or because of an internal error.
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%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.
IP_SNMP Messages
The following are Simple Network Management Protocol (SNMP) 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-4-NOTRAPIPV6 : SNMP trap source [chars] has no ipv6 address
Explanation The user entered an snmp-server trap-source command. The interface requested for use as the source address has no IPv6 address associated with it. The SNMP trap is being sent anyway, but without the source address that the user intended.
Recommended Action There are two possible solutions. Either enter a no snmp-server trap-source command to disable the request for a specific source IP address, or add an IPv6 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.
IP_VFR Messages
The following are IP Virtual Fragment Reassembly (VFR) subsystem messages.
Error Message%IP_VFR-4-FRAG_TABLE_OVERFLOW : [chars]: the fragment table has reached its maximum threshold [dec]
Explanation The number of datagrams being reassembled at any one time has reached it maximum limit.
Recommended Action Increase the maximum number of datagrams that can be reassembled by entering the ip virtual-reassembly max-reassemblies number command, with number being the maximum number of datagrams that can be reassembled at any one time.
Error Message%IP_VFR-3-INVALID_FRAG_LENGTH : [chars]: fragment length invalid - received from [IP_address], destined to [IP_address]
Explanation The router has encountered a "ping-of-death" type of attack
Recommended Action It is highly recommended to configure an ACL to drop any traffic from the sender of this attack.
Error Message%IP_VFR-3-OVERLAP_FRAGMENTS : [chars]: from the host [IP_address] destined to [IP_address]
Explanation The router has encountered overlap fragments. "Overlap fragment" means that the offset of one fragment overlaps the offset of another fragment. For example, if the offset of the first fragment is 0 and its length is 800, the offset of the second fragments offset must be 800. If the offset of the second fragment is less than 800, the second fragment overlaps the first fragment. This condition might indicate a hostile attack.
Recommended Action Configure a static ACL to prevent further overlap fragments from the sender.
Error Message%IP_VFR-3-SYSTEM_ERROR : [chars]: IP VFR System failure - [chars]
Explanation Miscellaneous errors have occurred in the VFR subsystem.
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%IP_VFR-4-TINY_FRAGMENTS : [chars]: from the host [IP_address] destined to [IP_address]
Explanation The router is receiving tiny fragments (the initial fragment does not have a complete layer 4 header).
Recommended Action This is an informational message only. No action is required.
Error Message%IP_VFR-4-TOO_MANY_FRAGMENTS : [chars]: Too many fragments per datagram (more than [dec]) - sent by [IP_address], destined to [IP_address]
Explanation The datagram that is being reassembled has received more fragments than its threshold value.
Recommended Action Check to see if the fragments that are being received are from a genuine source. If the fragments are coming from a genuine source, enter the ip virtual-reassembly max-fragments number command, with number being the maximum number of fragments that are allowed, to increase the fragment value.
IP_VRF Messages
The following are VPN routing and forwarding messages.
Error Message%IP_VRF-4-VRF_DELETE_WAIT : The VRF [chars] is getting deleted after a wait
Explanation There are routes remaining in the routing table of a deleted VRF, even after the system has waited for the deletion to complete. To ensure reusability of the same VRF, the routes in the VRF routing table are forcibly being cleared to complete the VRF deletion operation.
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.
IPA Messages
The following are Intelligent Port Adapter 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 might 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 might 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 might 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 can 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 might 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 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-3-SANITY_ERROR : [chars]
Explanation A sanity error occurred while the ACL was being configured on the RP or while the ACL configuration was being downloaded to the line card.
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%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 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.
IPC Messages
The following are interprocess communication (IPC) messages.
Error Message%IPC-2-BADSHARE : Bad refcount in [chars], ptr=[hex], count=[dec]
Explanation A reference count is used to track the usage of IPC messages. A function increments the count when it begins to use a message and decrements it when it finishes. When the count becomes zero, the data structure is freed. This message indicates that when the reference count was accessed, it was found to be zero or negative.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, include the stack trace, contact your Cisco technical support representative, and provide the representative with the gathered information.
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 might 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 This is a debug message. An action attempted by the IPC module has encountered an unexpected state in its data structures.
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%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 might 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 might 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 might 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 While processing an incoming message, IPC encountered invalid data in internal data structures.
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%IPC-5-INVALIDINPUT : [chars]
Explanation An invalid argument was used to call an IPC API.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support ipc command to gather data that may help identify the nature of the error. 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 ipc commands and your pertinent troubleshooting logs.
Error Message%IPC-2-INVALIDZONE : Invalid IPC Zone [hex].
Explanation An operation was attempted on a zone ID that is not known to the IPC process.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support ipc command to gather data that may help identify the nature of the error. 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 ipc commands and your pertinent troubleshooting logs.
Error Message%IPC-2-INVALSIZE : The IP fast path received an IPC message with an invalid size(size/type - [dec]/[dec])
Explanation The IP fast path switching module has received an IPC message with an invalid 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 might 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-LIMIT : [chars}
Explanation Several IPC messages are pending to be processed. If the number increases, it may result in the IPC header cache or EOBC buffers being exhausted.
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-2-LOCK : Lock done a deleted element [hex]
Explanation An internal inconsistency was found in some IPC data structures.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support ipc command to gather data that may help identify the nature of the error. 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 ipc commands and your pertinent troubleshooting logs.
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 might 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-4-MESSAGE_ERR : Consistency check failed for IPC Message. IPC message ([hex]) and port information ([hex]) differ
Explanation This message provides debugging information. An action attempted by the IPC module has encountered an unexpected state in either its data structures or the data structures of its clients.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show ipc ports command to gather data that may help identify the nature of the error. 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 ipc ports commands and your pertinent troubleshooting logs.
Error Message%IPC-5-MSG_NULL : [chars]
Explanation The IPC message is null.
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 might 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-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 might 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-NOBOOL : Boolean NULL in IPC message: [hex].
Explanation A watched boolean value that was allocated while sending the message, was found to be NULL when an acknowledgment (ACK) arrived.
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 might 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 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 might 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 might 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 might 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 might 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-NOPORT : Port Not Found. [hex] --> [hex], Index:[hex], Seq: [dec], flags: [hex], size: [dec]
Explanation IPC received a message that is destined for a port that cannot be found by IPC.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show ipc status, show ipc ports and debug ipc errors commands. 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%IPC-5-NULL : [chars] [chars]=0x[hex], [chars] 0x[hex]
Explanation The IPC module could not find an IPC entity that is expected always to be present.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support ipc command to gather data that may help identify the nature of the error. 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 ipc commands and your pertinent troubleshooting logs.
Error Message%IPC-5-NULLBPHANDLER : IPC flowcontrol back pressure handler is NULL
Explanation An application has attempted to register a function with a null value as a backpressure handler. IPC cannot register the function with a null value for the application in the IPC backpressure handler list.
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%IPC-5-NULLDELFUNC : Invalid registration
Explanation An IPC application has attempted to register a function with a null value in the IPC initialization list.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support ipc command to gather data that may help identify the nature of the error. 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 ipc commands and your pertinent troubleshooting logs.
Error Message%IPC-2-ONINT : Called from interrupt level: [chars]
Explanation This is a debug message. An IPC application attempted an IPC action that is prohibited at the interrupt level.
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 might 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-OUTPUT_FAIL : Num [dec] Func=[hex] Seat: ID=[hex] [chars] Sent [dec] Heard [dec]
Explanation The IPC output has failed in the function for a given seat with the specified sequence numbers for sending and receiving.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might 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 might 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 might 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-REGPORTFAIL : [chars] [chars]=[hex] [chars]=[hex]
Explanation IPC failed to register the control port.
Recommended Action If this error message recurs, copy the message exactly as it appears on the console or in the system log. Enter the show tech-support ipc command to gather data that may help identify the nature of the error. 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 ipc commands and your pertinent troubleshooting logs.
Error Message%IPC-5-RPCFULL : port: [hex], index: [dec], type: [hex]
Explanation An RPC request for an application could not be added to the RPC request table because pending requests have filled the RPC request table.
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 might 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-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-1-TNIPC_CALLBACK : TN3270 IPC callback error: [chars][chars]
Explanation The TN3270 server attempted to obtain information from the RP, but the TN3270 server detected an error while processing the response from the RP. This is an internal program logic 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.
Error Message%IPC-1-TNIPC_RPC : TN3270 IPC request error: [chars][chars]
Explanation The TN3270 server has failed to obtain information from 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%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.
Error Message%IPC-5-WATERMARK : [dec] messages pending in [chars] for the port [chars]([hex].[hex]) seat [hex]
Explanation Several IPC messages are waiting to be processed. If the number increases, this condition may result in the exhaustion of IPC header cache or buffers.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support ipc command to gather data that may help identify the nature of the error. 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 ipc commands and your pertinent troubleshooting logs.
IPC_DRVR Messages
The following are CMCC interprocess communication (IPC) driver messages.
Error Message%IPC_DRVR-2-DMAERR : DMA Error detected - [chars]([dec])
Explanation The IPC DRVR packet switch notification has detected a DMA transfer error.
Recommended Action The IPC subsystem is used by the channel adapter loader and channel adapter network management. A single DMA error will not impact these channel adapter functions. However, if you are experiencing problems loading the channel adapter or retrieving information from the channel adapter, you will have to reload the channel adapter microcode. In any case, report this message to your Cisco technical support representative.
Error Message%IPC_DRVR-4-NOMEM : Unable to obtain [chars]
Explanation The IPC DRVR transport 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, contact your Cisco technical support representative, and provide the representative with the gathered information.
IPC_RPM Messages
The following are interprocess communication (IPC) 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-4-ECC : WARNING: ECC Single Bit Error Correction
Explanation An ECC single-bit error has been detected and corrected.
Recommended Action Use the debug rpm ecc command to review the total number of ECC errors that have occurred since the system was booted. Use the debug rpm ecc count command to set the number of ECC errors that will cause a switchover to occur.
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-PORTREGFAIL : [chars]:[chars] Error:[chars]
Explanation The specified function was not able to register the port that was provided by the application.
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%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) 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.
IPC_URM Messages
The following are interprocess communication messages.
Error Message%IPC_URM-6-BFLASH : [chars]
Explanation Boot flash write protection is controlled from the IGX console. This informational message is displayed on the router console when the IGX user changes the mode.
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_URM-3-BFLASH_CHMOD_FAILED : [chars]
Explanation Boot flash write protection is controlled from IGX console. The IGX user has attempted to change the mode, but Cisco IOS software is unable to find the file descriptor for the boot flash device, and the operation 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%IPC_URM-3-INVMSG : [chars] ([dec])
Explanation An invalid IPC message type 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%IPC_URM-3-INVNUM : [chars] ([dec])
Explanation The IPC application tried to send a message that was larger than the IPC could process. 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_URM-3-INVTIMER : Invalid URM expired timer type [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, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IPC_URM-3-NOBUF : [chars]
Explanation The IPC has run out of memory 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.
IPCGRP Messages
The following are Route Processor (RP) interprocess communication (IPC) 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 attempt to create an IPC port on the RP 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%IPCGRP-3-ERROR : [chars]: [chars]
Explanation An IPC error has been detected.
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]/[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-INVALID_PARAMS : Invalid interface([int]/[int]/[int])
Explanation An invalid interface has been 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-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-6-NBLKCMD_Q_FULL : Nonblocking IPC command queue full ([dec] commands)
Explanation A nonblocking IPC command queue filled up and was flushed to avoid exhausting the buffer.
Recommended Action No action is required.
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 REXEC-On IPC command failure.
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-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 is generated.
Recommended Action To troubleshoot these error messages, it is important to figure out why the line card did not reply to the IPC message generated by the RP. This condition could be due to either a FIB reload of the LC due to some external event, a constantly high rate of CPU usage on the line card due to some specific features, or a software error in the Cisco IOS software release. The troubleshooting section of Troubleshooting Fabric Ping Timeouts and Failures on the Cisco 12000 Series Internet Router at the URL /en/US/products/hw/routers/ps167/products_tech_note09186a00800943b2.shtml#troubleshooting should provide additional information about this error 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.
IPCOIR Messages
The following are interprocess communication (IPC) online insertion and removal (OIR) 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-3-CARD_BADIDPROM : Card in slot [dec]/[dec] has an invalid card type in IDPROM
Explanation The specified line card ID PROM has not been programmed or has failed.
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-CARD_DETECTED : Card type [chars] ([hex]) in slot [dec]/[dec]
Explanation A card has been detected in the slot and subslot specified in the message text.
Recommended Action No action is required.
Error Message%IPCOIR-3-CARD_GET_VERSION_RESPONSE : Unsolicited response from slot [int]/[int], oir_state = [chars]
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-CARD_UNSUPPORTED : Unsupported card type ([hex]) in slot [dec]/[dec].
Explanation The line card is not supported by this version of Cisco IOS software.
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-2-CARD_UP_DOWN : Card in slot [dec]/[dec] is [chars]. Notifying [chars] driver.
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%IPCOIR-3-CARDCRASH : Card crashed in slot [dec]/[dec].
Explanation An IPC message reporting an invalid version has been received from an operational card.
Recommended Action Unavailable.
Error Message%IPCOIR-3-CRE_INIT_FAIL : Unable to initialize PRE ports.
Explanation The PRE plug-in initialization sequence has failed.
Recommended Action Determine and fix the cause of the problem.
Error Message%IPCOIR-2-CREATEFAIL : Couldn't create [chars]
Explanation The specified resource could not be created.
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-FLASHFAIL : Couldn't load [chars]...
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-4-IPC_GET_MSG_BUF : Get IPC msg buf failed [dec] time(s): slot [int]/[int] - retry in [dec] sec
Explanation The Cisco IOS software IPC buffer pool was temporarily empty.
Recommended Action Consider installing more processor SDRAM into the PRE.
Error Message%IPCOIR-3-IPC_GET_MSG_BUF_FAIL : Unable to get an IPC msg buffer in [dec] tries: slot [int]/[int]
Explanation The Cisco IOS software IPC buffer pool was empty for an extended period of time.
Recommended Action Install more processor SDRAM in the PRE.
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-PLUGIN_INIT_FAIL : Unable to create driver plugin in slot [dec]/[dec].
Explanation An attempt to create a valid line card driver plug-in has failed. This condition might have been caused by a memory allocation failure.
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-2-PLUGIN_PREANALYZE_FAIL : Unable to preanalyze driver plugin in slot [dec]/[dec].
Explanation An attempt to preanalyze a valid line card driver has failed. This condition might have been caused by incompatible card types.
Recommended Action Check the compatibility of the different cards in 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-4-REPEATMSG : IPC handle already exists for [dec]/[dec]
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...
Explanation The indicated image is inaccessible.
Recommended Action Check file permissions and the connectivity of the network.
Error Message%IPCOIR-3-TIMEOUT : Timeout waiting for a response from slot [dec]/[dec].
Explanation Unavailable.
Recommended Action Unavailable.
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.
Error Message%IPCOIR-3-WRONGCARDTYPE : Wrong card type in slot [dec]/[dec].
Explanation An IPC message reporting an incorrect card type has been received from an operational card.
Recommended Action Unavailable.
IPDCAPP Messages
The following are messages that refer to the Internet Protocol Device Control (IPDC) application or its TCP connection.
Error Message%IPDCAPP-6-IPDC_PACKET_OVERFLOW : The packet size [dec] overflows the pre-defined size [dec]
Explanation The packet size is larger than the predefined size, causing the TCP connection to shut down. An attempt to reconnect will be initiated.
Recommended Action Check the network connection.
Error Message%IPDCAPP-6-PROCESS_CREATION_FAILED : Cannot create IPDC application [chars]
Explanation An attempt to create the IPDC application process or TCP process has failed.
Recommended Action Check the amount of free memory to ensure that enough memory is available.
Error Message%IPDCAPP-6-PROCESS_INIT_FAILED : Failed to initialize the IPDC application process due to [chars]
Explanation The IPDC application process has failed to initialize.
Recommended Action Check the amount of free memory to ensure that enough memory is available.
Error Message%IPDCAPP-6-SESSION_DISCONNECTED : The TCP connection between [chars] and NAS is disconnected
Explanation The TCP connection between the NAS and the Softswitch is disconnected. The NAS will attempt to reconnect the TCP connection.
Recommended Action Check the Softswitch status.
Error Message%IPDCAPP-6-SOCKET_OPEN_FAILED : Failed to open socket for IPDC application due to errno [dec]
Explanation The application failed to open the socket for the IPDC TCP process.
Recommended Action Check that the IP address and TCP port are configured correctly.
IPFAST Messages
The following are IP fast switching 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 might 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-INVALSIZE : The IP fast path received an IPC message with an invalid size(size/type - [dec]/[dec])
Explanation The IP fast path switching module has received an IPC message with an invalid size.
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%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 might 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 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 might 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 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 might 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-3-DISABLEFLOWEXPORT : NULL
Explanation Flow export is disabled because the export destination address is the same as the IP address of one of the interfaces.
Recommended Action Check the IP addresses of all the interfaces to locate the address conflict. When setting IP addresses, make sure that none of them match with the flow export destination IP address.
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.
Error Message%IPFLOW-2-TEMPLATETBL_INIT : Error initializing Flow Export Template Table
Explanation Initialization of the flow export template table could not be accomplished because of a low memory condition.
Recommended Action Reduce other system activitiy to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%IPFLOW-4-V9_TEMPLATE_EXPORT : Error creating [chars]
Explanation Version 9 export template length is zero.
Recommended Action This is a debug message only. No action is required.
IPM_C54X Messages
The following are Voice over IP (VoIP) driver messages.
Error Message I%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_MEMORY : DSP [dec] on SPMM [dec]: Not enough memory to load firmware
Explanation The specified DSP firmware requires SPMMs with more memory.
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.
Error Message%IPM_C54X-4-UNSUPPORTED_PVDM : Unsupported or Bad PVDM in SPMM slot [hex]\n
Explanation The type of packet voice DSP module present in the slot indicated in the error message is not supported.
Recommended Action Replace the unsupported packet voice DSP module, or upgrade to a version of Cisco IOS software that supports the PVDM present in the system. Refer to documentation to determine what type of PVDMs are supported with which versions on this router.
IPM_DSPRM Messages
The following are Digital Signal Processor (DSP) Resource Manager messages.
Error Message%IPM_DSPRM-5-CODEC_CMPLX_CLI : Codec Complexity for VIC card in slot [dec] is changed.
Explanation The codec complexity for a VIC has been changed. As a result of this change in codec complexity for an analog VIC, the number of analog voice ports supported may be changed.
Recommended Action If some voice ports were lost by changing to a higher-complexity codec, these voice ports and their associated configurations can be regained by moving back to a lower-complexity image.
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 might 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 might 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 might 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-INSUFFICIENT : Insufficient DSP resources for timeslot [dec] on port [chars]
Explanation The configuration requires more DSP resources than are available.
Recommended Action Change the configuration to specify fewer used time slots. Install additional DSP resources to allow for more complex configurations.
Error Message%IPM_DSPRM-3-MAX_DSP_RESOURCES : Supports up to 8 DSPs due to HW limitation.
Last [dec] DSPs are not useful.Explanation A maximum of eight DSPs can be used on the Cisco 1751 because of a hardware limitation.
Recommended Action Limit the number of DSPs to eight.
Error Message%IPM_DSPRM-5-SETCODEC : Configured codec [dec] is not supported with this dsp image.
Explanation Codec negotiation has failed.
Recommended Action Change the DSP image to a high-complexity image.
Error Message%IPM_DSPRM-3-SLIC_VIC_POWER : Vic card in slot [dec] is unusable as DSP [dec] in group [dec] failed to come up
Explanation Since some DSPs failed to come up, the power is off for the SLIC on the VIC that is serviced by that DSP. All DSPs serving this VIC slot must be operational.
Recommended Action Check to see if the DSP has failed, and reload the trunk. 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%IPM_DSPRM-5-TRANSCODING_SESS_ALLOCATE : [dec] transcoding sessions are allocated.
Explanation This message displays the actual number of transcoding channels that have been opened. The actual number may be more than the number that is required, because active calls occupy more DSPs.
Recommended Action Check the DSP resources by entering the show voice dsp command. Reconfigure transcoding sessions when active transcoding sessions have been reduced.
Error Message%IPM_DSPRM-5-TRANSCODING_SESS_REDUCED : Number of transcoding sessions were reduced to [dec] after group change
Explanation A group change from one to two groups caused the number of transcoding sessions to be reduced. Some DSP resources are not available.
Recommended Action Change the TDM clock configuration to restore some digital signaling channels and reconfigure the transcoding sessions.
IPM_NV_EEPROM Messages
The following are integrated port module NVRAM driver 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 might 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.
Error Message%IPMCAST_LIB-6-EVENT_Q_SIZE : The event queue size has exceeded [dec]
Explanation The event queue has reached a significant threshold. Processing might become slower.
Recommended Action No action is required.
Error Message%IPMCAST_LIB-4-RPF_DEPTH_ERR : Depth for rpf lookup greater than [dec] for [chars]
Explanation The number of recursions for resolution of a given route has exceeded the allowed maximum. This condition is usually due to a system misconfiguration.
Recommended Action Review and fix the router configuration. If you require further assistance, 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%IPMCAST_LIB-4-RPF_STATIC_ERR : No match for RIB static route[paddr]/[dec] in static table for root[paddr]
Explanation An internal error has occurred.
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%IPMCAST_LIB-6-TIMER_BUSY : Timer drift is accumulating, [dec] msecs
Explanation The system is experiencing large amount of processing load, and the timers are accumulating a delay. The period of the delay is specified in the message text.
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%IPMCAST_LIB-6-TIMER_BUSY_ERR : Timer drift is accumulating, [time-stamp]
Explanation Unavailable.
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%IPMCAST_LIB-3-TIMER_ERR : Unexpected error in the timer library: [chars]
Explanation An internal error has occurred.
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%IPMCAST_LIB-4-UNKNOWN_EVENT_ERR : Unexpected event received: [dec]
Explanation A handler has not been found for the event.
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.
IPMOBILE Messages
The following are IP Mobility messages.
Error Message%IPMOBILE-2-ASSERTFAILED : IPMOBILE assertion failed: [chars]
Explanation The software has detected an inconsistency. This is considered a serious error. The router will attempt 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-6-DUPMOBNET : Unable to [chars] dynamic mobile network [IP_address] [IP_address] for MR [IP_address]; already [chars] MR [chars]
Recommended Action An attempt by a mobile router to dynamically add or delete a mobile network has failed because that mobile network was already statically configured for or dynamically registered by another mobile router. A mobile network may be configured or registered for only one mobile router.
Recommended Action To avoid duplication errors, check the static mobile network configuration on the Home Agent or the dynamic mobile network configuration on the mobile router or routers.
Error Message%IPMOBILE-6-DUPVIRTNET : Unable to [chars] dynamic mobile network [IP_address] [IP_address] for MR [chars]; already configured as a virtual network
Explanation A mobile router's attempt to dynamically add or delete a mobile network failed because that mobile network was already configured as a virtual network in the home agent.
Recommended Action To avoid duplication errors, make sure that the virtual network configuration on the home agent and the dynamic mobile network configuration on the mobile router do not have any overlapping network prefixes.
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-REDUPDATEFAIL : Too many redundancy update failures ([dec]) in the last minute.
Explanation The standby Home Agent has attempted to update its binding table by contacting the active Home Agent several times per minute. Some or all of these attempts have failed, and the number of failures have exceeded the threshold number.
Recommended Action Ensure that there is connectivity between the active Home Agent and the standby Home Agent. Also make sure that the clocks are synchronized between the two Home Agents and that the security associations are properly set between the two. If the preemption delay is set, try setting it to a shorter time period.
Error Message%IPMOBILE-3-SA_PARSE_FAILED : Error in parsing the security association for [chars]
Explanation The mobile IP home agent encountered an error while it was processing the security association in the RADIUS access-accept message.
Recommended Action Check the RADIUS profile configuration for the mobile node for which the processing of the security association failed.
Error Message%IPMOBILE-6-SECURE : Security violation on [chars] from [chars] [chars] - errcode [chars] ([dec]), reason [chars] ([dec])
Explanation A security violation has occurred during a registration attempt.
Recommended Action This message is for informational purpose only. No action is required.
IPNAT Messages
The following are IP Network Address Translation (IPNAT) messages.
Error Message%IPNAT-6-NATCREATE : [chars]
Explanation A NAT entry has been created in the NAT database.
Recommended Action No action is required.
Error Message%IPNAT-6-NATDELETED : [chars]
Explanation A NAT entry has been deleted from the NAT database because of either user-entered CLI or a timeout.
Recommended Action No action is required.
IPP Messages
The following are CMCC messages for the encryption feature.
Error Message%IPP-3-PKT_EXCEEDS_MTU : [chars]: Outbound Packet size [dec] exceeds max MTU size for CMCC
Explanation An outbound CMPC packet is larger than the MTU size for the CMCC.
Recommended Action Investigate why the host is sending packets that are larger than the configured MTU size on the CMCC.
IPPHONE Messages
The following are IP Phone register/unregister messages.
Error Message%IPPHONE-6-REG_ALARM : [chars]
Explanation The skinny client is informing the server of its software version and the reason for the last disconnect. If "Max phone count exceeded in SRST" is specified, you have exceeded the maximum number of ephones that the SRST router supports.
Recommended Action Do not attempt to configure more than the maximum number of ephones that are supported by the SRST router. Otherwise, this is an informational message only. No action is required.
Error Message%IPPHONE-6-REGISTER : ephone-[dec]:[chars] IP:[IP_address] Socket:[dec] DeviceType:[chars] has registered.
Explanation The configured IP phone has been registered.
Recommended Action No action is required.
Error Message%IPPHONE-6-REGISTER_NEW : ephone-[dec]:[chars] IP:[IP_address] Socket:[dec] DeviceType:[chars] has registered.
Explanation An IP phone has been registered. The phone is not yet in current running configuration.
Recommended Action No action is required.
Error Message%IPPHONE-6-UNREGISTER_ABNORMAL : ephone-[dec]:[chars] IP:[IP_address] Socket:[dec] DeviceType:[chars] has unregistered abnormally.
Explanation An IP phone has been unregistered without sending an unregister message.
Recommended Action No action is required.
Error Message%IPPHONE-6-UNREGISTER_NORMAL : ephone-[dec]:[chars] IP:[IP_address] Socket:[dec] DeviceType:[chars] has unregistered normally.
Explanation An IP phone has successfully been unregistered.
Recommended Action No action is required.
IPRT Messages
The following are IP routing 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-4-BADTRACKOBJECTTYPE : can't track this type of object
Explanation Route maps only support state-type objects. This track object is not a state-type object.
Recommended Action Reconfigure the track object to make it a state-type object.
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-4-IDBROUTECOUNTNEGATIVE : Interface IP route counter negative - [chars]
Explanation An attempt to decrement a per-interface IP route counter to a negative value 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%IPRT-4-IPROUTING_INT_ERR : Illegal call flow in interrupt path.Caller needs to change its code path.
Explanation An internal software error has occurred.
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%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.
Error Message%IPRT-4-REDIST_MAX_PFX : Redistribution prefix limit has been reached "[chars]" - [dec] prefixes
Explanation The maximum number of redistributed prefixes has been reached.
Recommended Action Check to be sure that the redistribution of a large number of prefixes is intentional and has not been configured in error.
Error Message%IPRT-4-REDIST_THR_PFX : Redistribution prefix threshold has been reached "[chars]" - [dec] prefixes
Explanation The threshold number of redistributed prefixes has been reached.
Recommended Action Check to be sure that the redistribution of large number of prefixes is intentional and has not been configured in error.
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.
Error Message%IPRT-3-STATICROUTESACROSSVRF : Un-installing static route [IP_address][IP_netmask] from [chars] routing table with outgoing interface [chars]
Explanation The system is restricting the access of static routes that point across VRFs.
Recommended Action Remove the static routes that are pointing across the VRF interfaces.
IPS Messages
The following are Intrusion Prevention System (IPS) messages.
Error Message%IPS-6-BUILTIN_SIGS : [chars] to load builtin signatures
Explanation The router is loading the built-in signatures.
Recommended Action No action is required.
Error Message%IPS-3-BUILTIN_SIGS_FAILED : Failed to load builtin signatures
Explanation The built-in signatures have failed to load.
Recommended Action The builtin signatures should build on all platforms that support IPS. This error indicates that something is wrong with the image.
Error Message%IPS-2-DISABLED : [chars] - IPS disabled
Explanation The IPS has been disabled. The message text should provide more information on the specific nature of the problem, which could include one or more of the following:
–
IPS configuration has been removed from all the interfaces on the router.
–
–
Recommended Action Perform actions that correspond to the reason for the IPS failure condition.
Error Message%IPS-6-ENGINE_BUILD_DONE : Finished building all engines
Explanation This is an informational message that occurs when all engines are built, with or without failures, after successfully loading an SDF file.
Recommended Action No action is necessary.
Error Message%IPS-3-ENGINE_BUILD_FAILED : [chars] - [dec] ms - engine build failed - [chars]
Explanation One of the engines could not be built after an SDF file was loaded. One such message for each failed engine is sent. The most likely reason for this failure is low system memory.
Recommended Action Increase the amount of memory on the router to attempt to alleviate the problem, or attempt to load the SDF file immediately after a system reboot when more system resources are available.
Error Message%IPS-6-ENGINE_BUILDING : [chars] - [dec] signatures - [dec] of [dec] engines
Explanation The SME has begun building.
Recommended Action No action is required.
Error Message%IPS-6-ENGINE_BUILD_SKIPPED : [chars] - there are no new signature definitions for this engine
Explanation There are no signature definitions or no changes to the existing signature definitions of an IPS SME.
Recommended Action No action is required.
Error Message%IPS-6-ENGINE_READY : [chars] - [dec] ms - packets for this engine will be scanned
Explanation An IPS SME has been built and is ready to scan packets.
Recommended Action No action is required.
Error Message%IPS-7-ENGINE_UNKNOWN : [chars] - unknown engine encountered while parsing SDF
Explanation An unknown and unsupported SME was encountered while the SDF file was being parsed.
Recommended Action Ensure that the SDF file being loaded on the router does not contain any engines that are not supported by the Cisco IOS software IPS.
Error Message%IPS-3-INVALID_TYPEDEFS : [chars]
Explanation Typedefs processing error.
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 that 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%IPS-3-IPS_CONCURRENT_ACCESS: [ [chars]
Explanation Multiple processes are attempting to access the same data structures.
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 that 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%IPS-3-IPS_FILE_OPEN_ERROR: [chars] - [chars]
Explanation Error occurred opening IPS file.
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 that 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%IPS-4-LOST_CONNECT : PO: Connection to HostID:[int] OrgID:[int]
Explanation A connection has been dropped and there is no previous connection. IPS cannot communicate with the director.
Recommended Action Check the connectivity to the director and check the post office configuration on both the router and the director.
Error Message%IPS-5-PACKET_DROP : [chars] - fail closed - packets dropped
Explanation Packets have been dropped by an IPS module that has failed and has been closed as mandated by the system configuration.
Recommended Action No action is required.
Error Message%IPS-5-PACKET_UNSCANNED : [chars] - fail open - packets passed unscanned
Explanation Packets have been passed that were unscanned by an IPS module that has failed and has been closed as mandated by the system configuration.
Recommended Action No action is required.
Error Message%IPS-4-SDF_LOAD_FAILED : failed to [chars] SDF from [chars]
Explanation An SDF could not be loaded. Possible reasons for this failure are as follows:
–
–
–
Recommended Action Ensure that the server on which SDF is available is reachable by the router and that the SDF has the correct read permissions.
Error Message%IPS-6-SDF_LOAD_SUCCESS : SDF loaded successfully from [chars]
Explanation An SDF file has been loaded successfully from a specified location.
Recommended Action No action is required.
Error Message%IPS-4-SDF_PARSE_FAILED : [chars] at Line [dec] Col [dec] Byte [dec] Len [dec]
Explanation An SDF file was not parsed correctly. This condition indicates that the SDF may be corrupted or could not be properly loaded on the router.
Recommended Action Ensure that the proper SDF is being loaded on the router and that the router is able to access and read it correctly.
Error Message%IPS-4-SIGNATURE : Sig:[dec] Subsig:[dec] Sev:[dec] [chars] [[IP_address]:[dec] -> [IP_address]:[dec]]
Explanation An IPS signature has been triggered.
Recommended Action Refer to the signature code in the message text, then refer to the Cisco Security Center at http://www.cisco.com/security for more details and for recommended actions.
Error Message%IPS-3-SIGNATURE_COMPILE_FAILURE: [[chars] [dec]
Explanation This error occurs when compilation fails for a signature. The signature is disabled.
Recommended Action Most likely cause of a compile failure is a complicated regular expression. Increasing the amount of memory on the router may help alleviate the problem. 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 that 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%IPS-4-SIG_SUMMARY : Sig:[dec] Subsig:[dec] Global Summary: [dec] alarms in this interval
Explanation A flood of IPS signatures of the same code have been detected and summarized.
Recommended Action Refer to the signature code in the message text, then refer to the Cisco Security Center at http://www.cisco.com/security for more details and for recommended actions.
Error Message%IPS-4-SYSERROR : Unexpected error ([chars]) at line [dec] func [chars]() file [chars]
Explanation An unexpected internal system error has occurred.
Recommended Action Contact the IPS development team by opening 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%IPS-3-UNKNOWN_NAME : [chars] ] [chars]
Explanation Unknown parameter or XML element name.
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 that 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%IPS-7-UNSUPPORTED_PARAM : [chars] [dec]:[dec] [chars]=[chars] - This parameter is not supported
Explanation An unsupported parameter was encountered while the SDF file was being parsed. IPS will scan for the signature without using this parameter.
Recommended Action Ensure that the SDF file that is being loaded on the router does not contain any parameters that are not supported by the Cisco IOS software IPS.
Error Message%IPS-4-UNSUPPORTED_SIG : [chars] [dec]:[dec] [chars]=[chars] - This signature cannot be supported
Explanation An unsupported parameter was encountered while an SDF file was being parsed. The unsupported parameter is a required parameter for the signature. The entire signature has been deleted.
Recommended Action Ensure that the SDF file that is being loaded on the router does not contain any parameters that are not supported by the Cisco IOS software IPS.
IPSECV6 Messages
The following are encryption feature messages.
Error Message%IPSECV6-4-RECVD_PKT_NOT_IPSECV6 : Rec'd packet not an IPSEC packet. (ip) dest_addr=[paddr], src_addr=[paddr], prot= [dec]
Explanation A packet was received that the encryption (crypto) map ACL, but is not IPSec-encapsulated. The IPSec peer is sending unencapsulated packets. There may be a policy setup error on the peer, or this condition might be considered a hostile event.
Recommended Action Contact the administrator of the peer to compare policy settings.
Error Message%IPSECV6-4-RECVD_PKT_V6_INV_PROT : decapsulate: packet missing [chars], destadr[paddr], actual prot=[dec]
Explanation An IPSec packet was received that was missing an expected AH or ESP header. The peer is sending packets that do not negotiate security policy. This might be considered a hostile event.
Recommended Action Contact the administrator of the peer.
Error Message%IPSECV6-4-RECVD_PKT_V6_INV_SPI : decaps: rec'd IPSEC packet has invalid spi for destaddr[paddr], prot=[dec], spi=[hex]([dec]), srcaddr[paddr]
Explanation An IPSec packet was received that specifies SPI that does not exist in the SADB. This may be a temporary condition due to slight differences in aging of SAs between the IPSec peers, or it may be because the local SAs have been cleared. It may also be because of bogus packets sent by the IPSec peer. This might be considered a hostile event.
Recommended Action If the local SAs have been cleared, the peer may not be aware of the new condition. In this case, if a new connection is established from the local router, the two peers may reestablish successfully. If the problem occurs for more than a brief period, either attempt to establish a new connection or contact the administrator of the peer.
Error Message%IPSECV6-4-RECVD_PKT_V6_MSG_LEN_ERR : decapsulate: packet has bad [chars] length destadr[paddr], prot=[dec], len=[dec]
Explanation An IPSec packet was received that is malformed. A possible reason for this condition is an encapsulation error. The peer is sending malformed packets. It may be due to a decryption error. This might be considered a hostile event.
Recommended Action Contact the administrator of the peer.
IPV6 Messages
The following are IPv6 messages.
Error Message%IPV6-3--1 : Cannot start the IPv6 process; router will not process IPv6 packets.
Explanation The IPv6 process could not be started. The machine on which this error occurred will not be able to process any IPv6 packets.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%IPV6-3-(-1) : Cannot start the IPv6 process; router will not process IPv6 packets.
Explanation The IPv6 process could not be started. This machine on which this error occurred will not be able to process any IPv6 packets.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%IPV6-6-ACCESSLOGDP : list [chars]/[dec] [chars] [chars][ipv6_addr] [chars]->[ipv6_addr] ([dec]/[dec]), [dec] packet[chars]
Explanation A packet matching the log criteria for the access list specified in the error message was detected.
Recommended Action No action is required.
Error Message%IPV6-6-ACCESSLOGNP : list [chars]/[dec] [chars] [dec][ipv6_addr] [chars]->[ipv6_addr], [dec] packet[chars]
Explanation A packet matching the log criteria for the access list specified in the error message was detected.
Recommended Action No action is required.
Error Message%IPV6-6-ACCESSLOGP : list [chars]/[dec] [chars] [chars][ipv6_addr]([dec]) [chars]->[ipv6_addr]([dec]), [dec] packet[chars]
Explanation A packet matching the log criteria for the access list specified in the error message was detected.
Recommended Action No action is required.
Error Message%IPV6-4-DUPLICATE : Duplicate address[ipv6_addr] on [chars]
Explanation Another system is using the IPv6 address that was specified.
Recommended Action Change the IPv6 address of one of the two systems.
Error Message%IPV6-4-IDB : Interface [chars] state mismatch. [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%IPV6-3-INTERNAL : Internal error, [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. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. 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://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IPV6-3-MIN_MTU : The link MTU of [chars] is below the [int]-byte minimum IPv6 link MTU. IPv6 may not work correctly on this interface.
Explanation IPv6 requires that every link have an MTU of at least 1280 as specified in the IPV6 standard. Because the MTU for this link is less than 1280, IPv6 has been disabled on this interface.
Recommended Action No action is required.
Error Message%IPV6-3-MIN_MTU : The link MTU of [chars] is below the minimum IPv6 link MTU. IPv6 may not work correctly on this interface.
Explanation As specified in the standard, IPv6 requires that every link have an MTU of at least 1280 bytes. Because the MTU of the specified link is below 1280 bytes, IPv6 must be disabled on this interface.
Recommended Action No action is required.
Error Message%IPV6-4-MULTICAST : Application does not support multicast destination address [ipv6_addr], packet dropped.
Explanation An internal software error has occurred. A multicast destination address was used in a local application that does not yet handle IPv6 multicast.
Recommended Action Use a unicast address in commands on the router. If the problem persists, or you feel that the command should support multicast, then contact the TAC with the failing command line.
Error Message%IPV6-3-NO_PROCESS : Cannot start the IPv6 process; router will not process IPv6 packets.
Explanation The IPv6 process could not be started. This machine will not be able to process any IPv6 packets.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%IPV6-3-NO_UNIQUE_IDENTIFIER : Cannot determine an unique IPv6 identifier for the system.IPv6 will not be started.
Explanation A unique IPv6 identifier could not be determined for the system. Therefore, the IPv6 process will not be started. The machine on which this error occurred will not be able to process any IPv6 packets.
Recommended Action Make sure that there is at least one interface in this machine that supports IEEE-style addresses.
Error Message%IPV6-3-NULLIDB : Uninitialized interface pointer - [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%IPV6-3-NULLPAK : Uninitialized buffer pointer - [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%IPV6-3-UNFRAGMENTABLE : Cannot fragment packet: unfragmentable part length [dec], MTU of [dec]
Explanation An internal software error has occurred. A single packet that was originated by this system could not be fragmented and has been dropped. Normal system operation will continue.
Recommended Action This is a transient error; however, this condition indicates other errors in the software that will require further examination by your Cisco technical support representative. 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.
IPV6_FW Messages
The following are IPv6 Inspection subsystem messages.
Error Message%IPV6_FW-4-ALERT_OFF : [chars], count ([dec]/[dec]) current 1-min rate: [dec]
Explanation Either the number of half-open connections have dropped below the low threshold, or the new connection initiation rate has dropped below the low threshold. This message may indicate that an attack has stopped.
Recommended Action No action is required.
Error Message%IPV6_FW-4-ALERT_ON : [chars], count ([dec]/[dec]) current 1-min rate: [dec]
Explanation Either the high threshold of half-open connections has been exceeded, or the new connection initiation rate has been exceeded. This message indicates that an unusually high rate of new connections is coming through the firewall, and a DOS attack may be in progress. This message is for informational purposes only, but may indicate a security problem.
Recommended Action If an attack is suspected, perform actions to block the security attack.
Error Message%IPV6_FW-2-BLOCK_HOST : Blocking new TCP connections to host[p] for [dec] minute[chars] (half-open count [dec] exceeded).
Explanation The threshold of half-open TCP connections has been exceeded, and the blocking option will now block any subsequent new connections. The blocking will be removed when the configured block-time expires. This message is for informational purposes only, but may indicate that a SYN flood attack was attempted.
Recommended Action If a SYN attack is suspected, perform actions to block a SYN attack.
Error Message%IPV6_FW-3-FTP_NON_MATCHING_IP_ADDR : Non-matching address[p] used in [chars] -- FTP client[p] FTP server[p]
Explanation An FTP client attempted to use a port command, or the FTP server attempted to use a response to a PASV command to trick the firewall into opening access to a third-party host that is different from the two hosts that are engaged in the FTP connection. This message indicates that a suspicious violation was detected while an attempt to modify the security policy was being made in the firewall. The command is rejected and the connection is reset by the firewall. This message is for informational purposes only, but may indicate that an attempt was made to grant or open access to unauthorized hosts.
Recommended Action If this is an expected message, no action is required. If this message is unexpected, or you determine that this condition is the result of a malicious attempt to breach the firewall, perform actions to correct the problem.
Error Message%IPV6_FW-3-FTP_PRIV_PORT : Privileged port [dec] used in [chars] -- FTP client[p] FTP server[p]
Explanation An FTP client attempted to use a port command, or the FTP server attempted to use a response to a PASV command to trick the firewall into opening access to a privileged port. This message indicates that a suspicious violation was detected from the FTP client or server that was attempting to modify the security policy in the firewall. The command is rejected and the connection is reset by the firewall. This message is for informational purposes only, but may indicate that an attempt was made to gain access to privileged ports.
Recommended Action If this is an expected message, no action is required. If this message is unexpected, or you determine that this condition is the result of a malicious attempt to breach the firewall, perform actions to correct the problem.
Error Message%IPV6_FW-3-FTP_SESSION_NOT_AUTHENTICATED : Command issued before the session is authenticated -- FTP client[p] FTP server[p]
Explanation An FTP client attempted to use the port command or an FTP server attempted to use the response to a PASV command to open a data channel in the firewall before the client could be successfully authenticated with the server. This condition is a suspicious attempt by the client or server to trick the firewall into opening a hole so that outside attackers can take advantage of the firewall opening. This message indicates that a suspicious violation was detected, and the port or PASV command or response has been rejected by the firewall. The data channel in the firewall will not be opened until the authentication is performed successfully. This message is for informational purposes only, but may indicate that an illegal attempt was made to modify the firewall security policy.
Recommended Action If this is an expected message, no action is required. If this message is unexpected, or you determine that this condition is the result of a malicious attempt to breach the firewall, perform actions to correct the problem.
Error Message%IPV6_FW-4-HOST_TCP_ALERT_ON : Max tcp half-open connections ([dec]) exceeded for host[p].
Explanation The maximum limit of half-open TCP connections has been exceeded. A high number of half-open connections is being received by the protected server. This condition may indicate that a SYN flood attack is in progress and is targeted to the specified server host. This message is for informational purposes only, but may indicate that a SYN flood attack was attempted.
Recommended Action If this alert is issued frequently and identified to be mostly false alarms, then the max-incomplete host threshold value is probably set too low, and there is a lot of legitimate traffic coming in to that server. In this case, set the max-incomplete host parameter to a higher number to avoid false alarms.
Error Message%IPV6_FW-3-NOTFOUND : Session context for Unrecognized format `(%P':[dec]) => Unrecognized format `(%P':[dec]) not found.
Explanation The CBAC code was searching its database for information for a particular inspection session, but this information was not found.
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%IPV6_FW-6-SESS_AUDIT_TRAIL : [chars] session initiator Unrecognized format `(%P':[dec]) sent [int] bytes -- responder Unrecognized format `(%P':[dec]) sent [int] bytes
Explanation This message documents the per-session transaction log of network activities. The message is issued at the end of each inspected session and it records the source and destination addresses and ports, as well as the number of bytes transmitted by the client and server. This message is for informational purposes only, and can be used to collect basic accounting information for inspected sessions.
Recommended Action No action is required.
Error Message%IPV6_FW-4-UNBLOCK_HOST : New TCP connections to host[p] no longer blocked
Explanation New TCP connection attempts to the specified host are no longer blocked. This message indicates that the blocking of new TCP attempts to the specified host has been lifted. This message is for informational purposes only, but may indicate that a SYN flood attack was previously attempted to the host.
Recommended Action No action is required.
IPV6_VFR Messages
The following are IPv6 virtual fragment reassembly subsystem messages.
Error Message%IPV6_VFR-4-FRAG_TABLE_OVERFLOW : the fragment table has reached its maximum threshold [dec]
Explanation The number of datagrams being reassembled has reached its maximum limit.
Recommended Action , increase the maximum datagram value by entering the ip virtual-reassembly max-datagram number, with number being the maximum number of datagrams that can be assembled.
Error Message%IPV6_VFR-3-INVALID_FRAG_LENGTH : fragment length invalid - received from[p], destined to[p]
Explanation The router has encountered activity that indicates that a "ping-of-death" attack is being initiated.
Recommended Action To prevent further attacks, we strongly recommend that you configure an ACL to drop any traffic from the sender of this attack.
Error Message%IPV6_VFR-3-OVERLAP_FRAGMENTS : from the host[p] destined to[p]
Explanation The router has encountered overlapping fragments. An offset of one fragment has overlapped the offset of another fragment. For example, if the offset of the first fragment is 0 and its length is 800, the offset of the second fragment must be 800. If the offset of the second fragment is smaller than 800, that means that the second fragment overlaps the first fragment. This condition could possibly indicate a hostile attack.
Recommended Action Configure a static ACL to prevent further overlapping fragments from the sender.
Error Message%IPV6_VFR-3-SYSTEM_ERROR : IP VFR System failure - [chars]
Explanation Miscellaneous errors have occurred in the VFR subsystem.
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%IPV6_VFR-4-TINY_FRAGMENTS : from the host[p] destined to[p]
Explanation The router is receiving tiny fragments. The initial fragment does not have a complete layer 4 header.
Recommended Action No action is required.
Error Message%IPV6_VFR-4-TOO_MANY_FRAGMENTS : Too many fragments per datagram (more than [dec]) - sent by[p], destined to[p]
Explanation The datagram being reassembled has received more fragments than its threshold value allows.
Recommended Action Check to see if the fragments that have been received are from a genuine source. If the received fragments are from a genuine source, increase the value of maximum fragments per datagram by entering the virtual-reassembly fragments-per-datagram number command, with number being the number of maximum fragments allowed per datagram.
IPV6FIB Messages
The following are IPv6 CEF messages.
Error Message%IPV6FIB-3-ASSERT : assertion '[chars]' failed [chars] line [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, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IPV6FIB-4-FIBCBLK : Missing cef table for tableid [int] during [chars] event
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%IPV6FIB-2-FIBDOWN : IPv6 CEF has been disabled due to a low memory condition.
It can be re-enabled by configuring "ipv6 cef [distributed]"Explanation IPv6 CEF has been disabled because of a low memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade the RP so that it has more DRAM.
Error Message%IPV6FIB-4-FIBIDB : Missing cef idb for [chars] during [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%IPV6FIB-4-FIBIDBINDEX : Missing CEF idb for interface index [dec] during [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%IPV6FIB-4-FIBREMOVE : Fibtype deletion execption: [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%IPV6FIB-4-FIBSPECIALPREFIX : Invalid Special Prefix Type. Type [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, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IPV6FIB-3-FIBTABLEINIT : CEF table creation failure - [chars], tableid [int]
Explanation An internal software error has occurred and prevented the creation of a new CEF 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%IPV6FIB-4-FIBXDRINV : Invalid format. [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%IPV6FIB-4-FIBXDRLEN : Invalid XDR length. Type/event [dec]/[chars]. XDR [dec], buffer [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, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IPV6FIB-3-GLOBALSTATE : Inconsistent global state '[chars]' [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%IPV6FIB-3-MAXPATHS_EXCEEDED : Max paths is [dec], [dec] attempted. Address was [IP_address], mask was [IP_address]
Explanation An internal software error has occurred. There was an attempt to set up more than the supported number of routing paths. CEF switching has been disabled on this slot.
Recommended Action Investigate why the number of routing paths was exceeded.
Error Message%IPV6FIB-3-NDB : Prefix [IP_address][IP_netmask] received with zero total traffic count
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%IPV6FIB-3-NOMEM : Malloc Failure, disabling [chars]
Explanation An internal software error has occurred. CEF switching has been disabled on this 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%IPV6FIB-5-NOPUNTINTF : CEF resuming switching packets to [chars]
Explanation CEF had been punting packets that were switched to this interface to the next-slower switching path. The interface configuration has changed, and CEF can now resume switching to this interface.
Recommended Action No action is required.
Error Message%IPV6FIB-4-PUNTINTF : CEF punting packets switched to [chars] to next slower path
Explanation Because of the current configuration, CEF cannot switch some or all packets out this interface. CEF will punt packets switched to this interface to the next-slower switching path.
Recommended Action If possible, configure CEF-supported and non-CEF-supported features on different subinterfaces. 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%IPV6FIB-2-RADIXINIT : Error initializing IPv6 CEF radix tree
Explanation Initialization of the radix tree could not be accomplished because of a low memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%IPV6FIB-4-RADIXINSERT : Error trying to insert prefix entry for [IP_address]/[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, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IPV6FIB-3-THREAD : Thread processing error: [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.
IPX Messages
The following are Internetwork Packet Exchange (IPX) 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 help
Explanation 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-NOVNOSTART : IPX Failed to Start due to insufficient memory
Explanation The Novell IPX routing subsystem failed to initialize properly because of memory allocation errors. This condition is usually caused by an insufficient amount of available memory.
Recommended Action Reduce other system activity to ease memory demands, look for a possible memory leak, or upgrade to a larger memory configuration.
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.
IRONBUS Messages
The following are IronBus messages.
Error Message%IRONBUS-2-INIT_FAILED : Ironbus initialization failed on slot [dec], triggering PXF exception.
Explanation The IronBus could not be initialized. No traffic is passing from the line card. A PXF exception is being triggered to restart the PXF microcode and related subsystems to remedy this situation.
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.
ISA Messages
The following are Integrated Services Adapter (ISA) 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.