-
12.3 T System Message Guide
-
System Message Overview
-
AAA through BSTUN messages
-
C10K through CALL_CONTROL messages
-
CALLRECORD through CPOS messages
-
CRYPTO through DMA messages
-
DNET through ENVM messages
-
ENVMON through FDM_HA messages
-
FECPM through GT96K_TDM messages
-
GTP through HEALTH_MONITOR messages
-
HHM through IPSECV6 messages
-
IPV6 through MICA messages
-
MIPC through NP_VPD messages
-
NRP through PIF messages
-
PIM through PVDM2 messages
-
PXF through RPM_BULK messages
-
RPM_CONN_MGMT through SEC_LOGIN messages
-
SENSOR through SWITCH_IF messages
-
SWITCHOVER through Y88E8K messages
-
Glossary of Acronyms
-
Table Of Contents
HHM Messages
The following are Cisco AS5400 health monitor messages.
Error Message%HHM-3-INTFWEDGE : [chars] [chars]
Explanation The interface hold queues have reached their limit and are stuck. Packets cannot be transmitted in or out of this interface.
Recommended Action Collect the interface-related information and reset the interface. Clear the counters of the interface to retransmit the packets. If the problem persists, 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%HHM-1-PROCFAIL : [chars]
Explanation During system initialization, the system was unable to create the periodic check process for the Cisco AS5400 health monitor because of a low-memory condition. The router memory has been exhausted or the memory may be fragmented. This condition may be caused by the current system configuration, the network environment, or a software error.
Recommended Action Check the minimum memory requirements for your system configuration. If a memory problem is suspected, reduce other activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.If your system meets the minimum memory requirements, this message is most likely caused by a software failure. If the problem persists, copy the error message text exactly as it appears on the console or in the system log. Enter the show tech-support, show log, show process memory and show memory summary commands. 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.
HPI Messages
The following are Host Port Interface messages.
Error Message%HPI-4-INVALID_ECAN_TYPE : [chars] ECAN is not available in voice-card [dec], [chars] ECAN will be used
Explanation All voice cards that are participating in DSPFARM must have the same echo canceller type.
Recommended Action Ensure that all voice cards that are participating in DSPFARM have the same echo canceller type configured.
Error Message%HPI-3-INVALID_PAYLOAD : wrong payload size, channel:[chars] DSP ID:[hex], failed mode [dec] for service [dec]
Explanation DSP services could not be started.
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.
HSRP Messages
The following are Hot Standby Router Protocol (HSRP) messages.
Error Message%HSRP-4-BADAUTH : Bad authentication from [IP_address], group [dec], remote state [chars]
Explanation Two routers participating in HSRP disagree on the valid authentication string.
Recommended Action Enter the standby authentication command to repair the discrepancy in HSRP authentication between the local system and the one whose IP address has been reported.
Error Message%HSRP-4-BADAUTH2 : Bad authentication from [IP_address]
Explanation Two routers participating in HSRP disagree on the valid authentication string.
Recommended Action Enter the standby authentication command to repair the HSRP authentication discrepancy between the local system and the one whose IP address is reported.
Error Message%HSRP-4-DIFFVIP1 : [chars] Grp [dec] active routers virtual IP address [IP_address] is different to the locally configured address [IP_address]
Explanation The HSRP virtual IP address contained in the hello message from the active router is different from the virtual IP address that is configured locally.
Recommended Action Check the configuration on all HSRP routers in the group and ensure that they are all configured with the same virtual IP address.
Error Message%HSRP-4-DUPADDR : Duplicate address [IP_address] on [chars], sourced by [enet]
Explanation The IP address in an HSRP message that was received on the specified interface is the same as the IP address of the router. Another router might be configured with the same IP address. The most likely cause of this condition is a network loop or a misconfigured switch that is causing the router to see its own HSRP hello messages.
Recommended Action Check the configurations on all the HSRP routers to ensure that the interface IP addresses are unique. Make sure that no network loops exist. If port channels are configured, check that the switch is correctly configured for port channels. Enter the standby use-bia command so that the error message displays the interface MAC address of the sending router, which can be used to determine if the error message is caused by a misconfigured router or a network loop.
Error Message%HSRP-4-DUPVIP1 : [chars] Grp [dec] address [IP_address] is already assigned to [chars] group [dec]
Explanation The HSRP virtual IP address contained in the hello message cannot be learned; it is already assigned to a different HSRP group.
Recommended Action Check the configuration on all HSRP routers and ensure that the virtual IP address of each HSRP group is unique.
Error Message%HSRP-4-DUPVIP2 : [chars] Grp [dec] address [IP_address] is already assigned on this interface
Explanation The HSRP virtual IP address contained in the hello message cannot be learned; it is already assigned to this interface.
Recommended Action Check the configuration on all HSRP routers and ensure that the virtual IP address of each HSRP group is unique.
Error Message%HSRP-4-DUPVIP3 : [chars] Grp [dec] address [IP_address] is already assigned to, or overlaps with, an address on another interface or application
Explanation The HSRP virtual IP address that is contained in the hello message cannot be learned; it is already assigned to or overlaps with an address on another interface or application.
Recommended Action Check the configuration on all HSRP routers and ensure that the virtual IP address of each HSRP group is unique.
Error Message%HSRP-3-MISCONFIG : Attempt to change [chars] MAC address to [enet] when DECNET already running
Explanation An HSRP group attempted to become active on an interface that can support only a single MAC address and that is running DECnet. If the standby use-bia command has not been entered on the interface, HSRP would normally set the interface MAC address to the HSRP virtual MAC address, but this configuration is not allowed if DECnet is running.
Recommended Action Enter the standby use-bia command on the interface.
HTTPC Messages
The following are HTTP client messages.
Error Message%HTTPC-3-CONNECT_NULL : NULL connection structure for fd([dec]) - closing socket.
Explanation The HTTP client is receiving a read event from the socket, but the client cannot locate the connection structure for the file descriptor. If this condition is detected continuously in a loop, it indicates a problem with the socket code. Since the socket should be closed immediately after the read event, the HTTP client should not be receiving any additional read events.
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%HTTPC-3-RECEIVE_SOCK_READ_EVENT_WHILE_DISABLED : Received socket read event while read interest is disabled callID([dec]) fd([dec]) - closing socket.
Explanation The HTTP client is receiving a read event from the socket while the read interest is being disabled. This condition indicates a problem between the HTTP client and the socket interface.
Recommended Action Record the error and report it to the system administrator.
HW_VPN Messages
The following are Encryption Advanced Interface Module (EAIM) messages.
Error Message%HW_VPN-1-HPRXERR : [chars]: Packet Encryption/Decryption error([int]):[chars]
Explanation An unexpected error occurred during the encryption or decryption of a packet.
Recommended Action This message can occur during the transition to a new session key for a Security Association, in which case this message indicates normal system operation and no action is required. If this message occurs frequently or is associated with traffic disruption, make a note of the status value and 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. The EAIM will most likely require replacement.
HWECAN Messages
The following are HWECAN echo canceller messages.
Error Message%HWECAN-5-DEVICE : HWECAN Device [dec] in slot [dec] [chars] [dec], changed state to [chars]
Explanation The HWECAN individual device has changed state.
Recommended Action No action is required.
Error Message%HWECAN-5-INITFAILURE : HWECAN in slot [dec] [chars] [dec], Initialization Failed: [chars]
Explanation Initialization of the HWECAN echo canceller has failed.
Recommended Action 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.
Error Message%HWECAN-5-INSUFFICIENT : Insufficient EC channel resource to allocate for slot [dec] port [dec] ts [dec]
Explanation A free HWECAN channel is not available for allocation to the voice channel.
Recommended Action Change the tail-length configuration to get more ECAN channels. Specify fewer time slots for voice configuration. Install or replace additional HWECAN resources to allow more complex configurations.
Error Message%HWECAN-5-NACK : HWECAN in slot [dec] [chars] [dec] NACKed the Command/Query [hex]
Explanation The command or the query is not understood by the HWECAN device.
Recommended Action Retry the query or command. 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%HWECAN-5-NOMSGPOOL : HWECAN in slot [dec] [chars] [dec], Failed to get [chars] Msg buffer Pool
Explanation A buffer pool for Tx or Rx message communication could not be allocated.
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%HWECAN-5-TIMEOUT : HWECAN in slot [dec] [chars] [dec] failed to return response for Command/Query [hex]
Explanation A response to the previous command was not received in a timely manner.
Recommended Action Check the status of the HWECAN echo canceller and replace it, if required.
Error Message%HWECAN-5-UPDOWN : HWECAN in slot [dec] [chars] [dec], changed state to [chars] with [dec] Channels
Explanation The HWECAN has changed state.
Recommended Action No action is required.
HWIC_1GE_SFP Messages
The following are Gigabit Ethernet High-speed WAN Interface Card (HWIC) messages.
Error Message%HWIC_1GE_SFP-3-BAD_CLOCK : PL3 clock is missing at FPGA
Explanation An attempt by MAC to acquire clocks on the system bus has failed. This condition indicates a hardware problem.
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%HWIC_1GE_SFP-3-DUPLICATE_SN : SFP in interface [chars] has the same serial number as another SFP
Explanation The serial number of the SFP matches that of another interface on the system. Cisco SFPs are assigned unique serial numbers.
Recommended Action Verify that the SFP was obtained from Cisco or a supported vendor.
Error Message%HWIC_1GE_SFP-3-ID_MISMATCH : SFP in interface [chars] failed identification check
Explanation The system was unable to verify the identity of the SFP.
Recommended Action Verify that the SFP was obtained from Cisco or from a supported vendor. Use the Cisco Software Advisor tool to check if the Cisco IOS software that is running on the system supports the SFP. If the SFP is newer, a system software upgrade might be required.
Error Message%HWIC_1GE_SFP-3-INVALID_FPGA_VER : Incorrect FPGA version. Expected [hex] Read [hex]\n
Explanation One or more of the following errors have occurred:
–
An invalid FPGA or download has occurred.
–
–
Recommended Action Attempt to reload the router. 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%HWIC_1GE_SFP-1-NOMEMORY : HWIC_1GE_SFP [dec]: Memory allocation failure; could not allocate [chars]
Explanation An attempt to allocate memory for the specified HWIC-1GE-SFP has failed.
Recommended Action Additional RAM may be required in order to execute this image. 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%HWIC_1GE_SFP-3-SFP_BAD_CC : Interface [chars] SFP [chars] ID fields check sum failed.
Explanation The specified SFP ID fields failed a checksum operation.
Recommended Action Reinsert or replace the SFP.
Error Message%HWIC_1GE_SFP-6-SFP_IN : Interface [chars] [chars] SFP has been inserted.
Explanation An HWIC-1GE-SFP interface SFP has been inserted.
Recommended Action No action is required.
Error Message%HWIC_1GE_SFP-4-SFP_INTERR : Interface [chars] internal error occurred in setup for SFP
Explanation The system could not allocate resources, or had some other problem, while the specified SFP interface was being set up.
Recommended Action Reload the system. If the problem persists, 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%HWIC_1GE_SFP-6-SFP_OUT : Interface [chars] SFP has been removed.
Explanation An HWIC-1GE-SFP interface SFP has been removed.
Recommended Action No action is required.
Error Message%HWIC_1GE_SFP-6-STARTUP : [chars] initialized
Explanation The specified HWIC-1GE-SFP has initialized successfully.
Recommended Action No action is required.
Error Message%HWIC_1GE_SFP-3-UNRECOGNIZED_VENDOR : SFP in interface [chars] is manufactured by an unrecognized vendor
Explanation The system was unable to match the SFP manufacturer with one on the known list of Cisco SFP vendors.
Recommended Action Verify that the SFP was obtained from Cisco or a supported vendor. Use the Software Advisor tool to check if the Cisco IOS software running on the system supports the SFP. If the SFP is newer, a system software upgrade might be required.
Error Message%HWIC_1GE_SFP-3-VN_DATA_CRC_ERROR : SFP in interface [chars] has bad crc
Explanation The SFP does not contain a valid CRC in the EEPROM data.
Recommended Action Reinsert or replace the SFP.
HWIC_HOST Messages
The following are High-speed WAN Interface Card (HWIC) host driver library messages.
Error Message%HWIC_HOST-1-BAD_HWIC_INT : HWIC_HOST: Invalid Interrupt Table [dec]
Explanation The interrupt table number is not supported by the HWIC library. This condition indicates a software 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%HWIC_HOST-1-BAD_HWIC_INTERFACE_NUM : HWIC_HOST: Invalid Interface Number [dec]
Explanation The HWIC Library API function does not recognize this interface. This condition indicates a software 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%HWIC_HOST-1-BAD_HWIC_SLOT : HWIC_HOST: Invalid HWIC slot [dec]
Explanation The HWIC slot is not supported on this platform. This condition indicates a software 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%HWIC_HOST-1-BAD_IDB : HWIC_HOST: Invalid Interface Descriptor Block [hex]
Explanation The IDB that was passed to an HWIC host driver library API is of a null value or contains invalid null pointers. This condition indicates a software 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%HWIC_HOST-1-DMA_ERROR : HWIC_HOST: Host termination logic experienced a DMA error for Interface Descriptor Block [hex]
Explanation The host termination logic has encountered an HWIC read or write error for the interface described by the IDB. This condition indicates a software 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%HWIC_HOST-1-REG_RW_ERROR : HWIC_HOST: Host termination logic experienced an HWIC read/write error for Interface Descriptor Bl \nock [hex]
Explanation The host termination logic has encountered an HWIC read or write error for the interface specified by the IDB. This condition indicates a software 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%HWIC_HOST-1-REG_RW_TIMEOUT_ERROR : HWIC_HOST: Host termination logic experienced an HWIC read/write timeout error for Interface Descriptor Block [hex]
Explanation The host termination logic has encountered a timeout error during an HWIC read or write operation for the interface specified by the IDB. This condition indicates a software 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%HWIC_HOST-1-RXCLK_MISSING_ERROR : HWIC_HOST: The HWIC Receive Clock signal was not detected for Interface Descriptor Block [hex]
Explanation The host termination logic has encountered a fatal error. The logic could not detect the HWIC receive clock for the interface specified by the IDB. This condition indicates a software 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%HWIC_HOST-1-RX_CRC_ERROR : HWIC_HOST: Host termination logic experienced an HWIC CRC error for Interface Descriptor Block [hex]
Explanation The host termination logic has encountered an HWIC CRC error for the interface specified by the IDB. This condition indicates a software 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%HWIC_HOST-1-RX_DONE_ERROR : HWIC_HOST: Improper DONE bit setting in Receive Ring for Interface Descriptor Block [hex]
Explanation The host termination logic has encountered a invalid setting for a Done bit in the buffer descriptor for the interface specified by the IDB. This condition indicates a software 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%HWIC_HOST-1-RX_FORMAT_ERROR : HWIC_HOST: Host termination logic experienced an HWIC Format error for Interface Descriptor Block [hex]
Explanation The host termination logic has encountered an HWIC format error for the interface specified by the IDB. This condition indicates a software 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%HWIC_HOST-1-RX_OVERRUN_ERROR : HWIC_HOST: Host termination logic experienced a Receive FIFO overrun for Interface Descriptor Block [hex]
Explanation The host termination logic has encountered a FIFO overrun during a receive operation for the interface specified by the IDB. This condition indicates a software 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%HWIC_HOST-1-TX_DONE_ERROR : HWIC_HOST: Improper DONE bit setting in Transmit Ring for Interface Descriptor Block [hex]
Explanation The host termination logic has encountered a invalid setting for a Done bit in the buffer descriptor for the interface specified by the IDB. This condition indicates a software 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%HWIC_HOST-1-TX_FIRST_LAST_ERROR : HWIC_HOST: Improper First/Last sequence in Transmit Ring for Interface Descriptor Block [hex]
Explanation The host termination logic has encountered an invalid first or last sequence in the buffer descriptor for the interface specified by the IDB. This condition indicates a software 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.
HWIC_SERIAL Messages
The following are High-speed WAN Interface Card (HWIC) serial device driver messages.
Error Message%HWIC_SERIAL-3-BSCHUNT : BSC HUNT cmd for int [dec]/[dec] failed
Explanation An internal 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 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 gathered information.
Error Message%HWIC_SERIAL-4-DCD_CHANGE : Unexpected DCD transition interrupt on wic [dec] port [dec] occured
Explanation Unexpected event has been detected by the software. This should just be a transient condition.
Recommended Action The System should recover. No action is required.
Error Message%HWIC_SERIAL-1-DISCOVER : NM slot [dec]: only [dec] PCI dev found
Explanation Some of the interface controller devices on HWIC_SERIAL NM did not initialize properly.
Recommended Action Power down, reinsert the port module, and reboot.If this message recurs, 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 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 gathered information.
Error Message%HWIC_SERIAL-1-FPGA_DNLD_FAIL : FPGA download failed for NM slot [dec] HWIC slot [dec]
Explanation The firmware/FPGA download has failed for this module.
Recommended Action Check the part number on the WIC card to verify that it is supported
in the IOS release operational on the router.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%HWIC_SERIAL-4-FREQ_OUT_OF_RANGE : [chars] Frequency not in Range.
Explanation Frequency in not in range.
Recommended Action ensure that the DCE side is up and providing clock. No action is required.
Error Message%HWIC_SERIAL-3-INVALID_CABLE : [chars]: Cable connected is not supported on this interface.
Explanation The HWIC-16A supports only octal RS232 RJ45 cables. All other cables are invalid.
Recommended Action Connect the proper cable.
Error Message%HWIC_SERIAL-3-INVALID_CLOCKRATE : Unsupported clock rate req on int [dec]/[dec] - index [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. 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%HWIC_SERIAL-3-INVALID_SCC : Config req for invalid SCC via int [dec]/[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. 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%HWIC_SERIAL-3-INVALID_TXRX : NM slot [dec], WIC card [dec] doesn't support different tx speed ([dec]) and rx speed ([dec])
Explanation The software does not support different TX and RX speeds.
Recommended Action Configure the TX speed and the RX speed to be equivalent.
Error Message%HWIC_SERIAL-4-MISMATCH_FREQ : [chars] Mismatch between configured and measured Freq.
Explanation There was a mismatch between the configured and the measured frequency.
Recommended Action Re-configure the clock rate network on the serial interface.
Error Message%HWIC_SERIAL-3-NOMEMORY : No memory for [chars] of unit [dec]
Explanation The router does not have enough memory to perform the function.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%HWIC_SERIAL-6-NOT_IN_SYNC_MODE : [chars] not in sync mode
Explanation The network clocking commands are configured for an asynchronous interface.
Recommended Action Change the mode to synchronous.
Error Message%HWIC_SERIAL-3-OWNERR : Buffer owner ship error on int [chars], pak=[hex]
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. 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%HWIC_SERIAL-2-SCCFAIL : Init of SCC[dec] for int [dec]/[dec] failed to do [chars]
Explanation The software failed to initialize or restart an SCC of a serial interface on HWIC_SERIAL.
Recommended Action Clear the serial interface. 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%HWIC_SERIAL-3-SCCRESET : SCC reset for int [dec]/[dec]/[dec] at [chars] failed
Explanation An internal 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%HWIC_SERIAL-3-SPI_OP_FAILED : NM base addr - [hex], WIC slot - [dec], SPI op failed
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%HWIC_SERIAL-6-STARTUP : [chars] initialized
Explanation The specified HWIC_SERIAL has initialized successfully.
Recommended Action This is an informational message only. It occurs in normal operation. No action is required.
Error Message%HWIC_SERIAL-6-SYNC_IDB_NULL : sync idb not found
Explanation A null IDB has been encountered
Recommended Action No action is required.
Error Message%HWIC_SERIAL-5-TOOBIG : On int [chars], tx pak is [dec] bytes
Explanation A packet greater than the assigned MTU of this serial interface was queued for transmission.
Recommended Action The system should recover. 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%HWIC_SERIAL-5-TOOSMALL : On int [dec]/[dec], tx pak size is [dec] bytes
Explanation A small packet (less than two bytes) was queued for transmission. The interface cannot handle such small packets for transmission.
Recommended Action The system should recover. 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.
Recommended Action
Error Message%HWIC_SERIAL-3-TXCOMPNOTIFY : On int [dec]/[dec], tx_comp_notify vector is not set
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%HWIC_SERIAL-3-UFHANDLE : UnderFlow handling on int [dec]/[dec] failed.
Explanation An internal 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%HWIC_SERIAL-5-UNDERFLOW : Transmit underflow on int [chars]
Explanation While transmitting a frame, the controller chip's local buffer received insufficient data because data could not be transferred to the chip fast enough to keep pace with its output rate. Normally, such a problem is temporary, depending on transient peak loads within the system.
Recommended Action The system should recover. No action is required.
Error Message%HWIC_SERIAL-1-UNKNOWN_WIC : NM slot [dec], wic card has an unknown id [hex]
Explanation The software does not recognize the type of WIC card that is plugged into the port module.
Recommended Action Check the part number on the WIC card to verify that it is supported in the IOS release operational on the router.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 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 gathered information.
I82543 Messages
The following are Intel 82543 Ethernet/Fast Ethernet/Gigabit Ethernet controller messages.
Error Message%I82543-1-BAD_SB_NOMEM : [chars] - Cannot create IDB subblock due to insufficient memory
Explanation Available system memory was insufficient for creation of the subblock.
Recommended Action Upgrade the router to a larger memory configuration. 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%I82543-5-WATCHDOG : I82543([dec]/[dec]), enormous packet received
Explanation Unavailable.
Recommended Action Unavailable
I82544 Messages
The following are I82544 Fast Ethernet controller messages.
Error Message%I82544-3-BAD_POOL : Could not init buffer pools
Explanation The driver could not obtain a pool of buffers from the 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%I82544-3-EEPROM : EEPROM access failed
Explanation The driver could not perform a read or write operation to the EEPROM for the i82544 device.
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%I82544-3-INITFAIL_NOMEM : [chars], initialization failed, no memory
Explanation The Ethernet port could not be initialized because insufficient system memory was available.
Recommended Action Upgrade the memory in the chassis. 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%I82544-3-NOTI82544 : Bay [dec] device ID seen as [hex], expected [hex]
Explanation The Fast Ethernet driver failed to initialize.
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%I82544-3-NOTI82544PHY : Bay [dec] PHY device ID seen as [hex], expected [hex]
Explanation The Fast Ethernet driver failed to initialize.
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%I82544-3-TOOBIG : [chars], packet too big ([dec]), from [enet]
Explanation The interface has detected a packet larger than the configured MTU size. This condition indicates a software 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.
I82559FE Messages
The following are Intel 82559 Fast Ethernet controller messages.
Error Message%I82559FE-1-NOT82559 : NM slot [dec]: PCI device ID seen as [hex], expected [hex]
Explanation The Cisco IOS software could not recognize the I82559 Fast Ethernet controller.
Recommended Action Power down the system, reseat the interface card, and reboot the system. 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%I82559FE-3-UNEXPECTEDINTR : NM slot [dec]: Unexpected I82559FE [chars] interrupt
Explanation The I82559 Fast Ethernet controller issued an unexpected interrupt.
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.
ICC Messages
The following are Inter-Card Communication messages.
Error Message%ICC-4-COMM : Communication failure occurred while [chars]
Explanation A communication failure has occurred between this card and another card in the system.
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. Enter the show tech-support command 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%ICC-4-CONSISTENCY : Internal consistency check: [chars]
Explanation An internal inconsistency was found in some ICC data structures.
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. Enter the show tech-support command 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%ICC-4-HEARTBEAT : Card [dec] failed to respond to heartbeat
Explanation A communication failure has occurred between the primary and the specified line card.
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. Enter the show tech-support command 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%ICC-2-NOMEM : No memory available for [chars]
Explanation The ICC 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. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Enter the show tech-support command 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.
IDCONF Messages
The following are Intrusion Detection Configuration messages.
Error Message%IDCONF-4-HTTP_ERROR : IDCONF: HTTP returned error [dec] when registering
Explanation IDCONF received an error message from HTTP during initialization.
Recommended Action This message indicates that IDCONF was not able to successfully register with the HTTP server.
Error Message%IDCONF-4-PARSE_ERROR : IDCONF: Parse error while parsing xml parser
Explanation Intrusion Detection Configuration has received an error while parsing an XML configuration document.
Recommended Action Check the XML document and make sure that it complies with the IDCONF data format standard.
IDS Messages
The following are IP datagram subsystem (IDS) messages.
Error Message%IDS-6-BUILTIN_SIGS : [chars] to load builtin signatures
Explanation The router is about to load the built-in signatures.
Recommended Action No action is required.
Error Message%IDS-2-DISABLED : [chars] - IDS disabled
Explanation IDS has been disabled. The message provides more information on the specific cause. IDS will be disabled for a number of reasons, including the following: IDS configuration is removed from all the interfaces on the router, IDS cannot load a signature file, or IDS cannot allocate memory for a critical resource.
Recommended Action If this was a user-initiated or normal system-initiated operation, no action is required. Otherwise, perform actions to determine the cause of the problem, depending on the message text.
Error Message%IDS-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 message is sent for each engine build failure. The most likely cause of an engine build failure is low memory.
Recommended Action Increase the amount of memory in the router, or attempt to load the affected SDF file immediately after a reboot once additional system resources are available.
Error Message%IDS-6-ENGINE_BUILDING : [chars] - [dec] signatures - [dec] of [dec] engines
Explanation The SME has begun building.
Recommended Action No action is required.
Error Message%IDS-6-ENGINE_BUILD_SKIPPED : [chars] - there are no new signature definitions for this engine
Explanation No signature definitions are available, or there are no changes to the existing signature definitions of an IDS SME.
Recommended Action No action is required.
Error Message%IDS-6-ENGINE_READY : [chars] - [dec] ms - packets for this engine will be scanned
Explanation An IDS SME has been built and is ready to scan packets.
Recommended Action No action is required.
Error Message%IDS-7-ENGINE_UNKNOWN : [chars] - unknown engine encountered while parsing SDF
Explanation An unknown and therefore unsupported SME has been encountered while an SDF file was being parsed.
Recommended Action Ensure that the SDF file that is being loaded on the router contains only engines that are supported by the IDS in the Cisco IOS software.
Error Message%IDS-4-LOST_CONNECT : PO: Connection to HostID:[int] OrgID:[int]
Explanation A connection has been dropped, and there was no previous connection. This condition indicates that the IDS 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%IDS-5-PACKET_DROP : [chars] - fail closed - packets dropped
Explanation An IDS module has failed. Packets has been dropped by the failed IDS module. As a result of this condition, the system configuration specifies that a "fail closed" operation will occur.
Recommended Action No action is required.
Error Message%IDS-5-PACKET_UNSCANNED : [chars] - fail open - packets passed unscanned
Explanation An IDS module has failed. Packets that were not scanned by the failed IDS module have been passed. As a result of this condition, the system configuration specifies that a "fail closed" operation will occur.
Recommended Action No action is required.
Error Message%IDS-4-SDF_LOAD_FAILED : failed to [chars] SDF from [chars]
Explanation An SDF file has failed to load. This condition may occur if the SDF file is on an unreachable network server, if the SDF file does not have the correct read permissions, or if the decryption routines for the SDF file have failed.
Recommended Action Ensure that the server on which the SDF resides is reachable by the router and that the SDF has the correct read permissions.
Error Message%IDS-6-SDF_LOAD_SUCCESS : SDF loaded successfully from [chars]
Explanation An SDF file has been loaded successfully from the location specified in the message text.
Recommended Action No action is required.
Error Message%IDS-4-SDF_PARSE_FAILED : [chars] at Line [dec] Col [dec] Byte [dec] Len [dec]
Explanation An SDF file was not parsed correctly. 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%IDS-4-SIGNATURE : Sig:[dec] Subsig:[dec] Sev:[dec] [chars] [[IP_address]:[dec] -> [IP_address]:[dec]]
Explanation An IDS signature has been triggered.
Recommended Action Refer to the Cisco Network Security Database for more details and recommended actions specific to each signature.
Error Message%IDS-4-SIG_SUMMARY : Sig:[dec] Subsig:[dec] Global Summary: [dec] alarms in this interval
Explanation A flood of the specified IDS signature has been detected and summarized.
Recommended Action Refer to the Cisco Network Security Database for more details and recommended actions specific to each signature.
Error Message%IDS-4-SYSERROR : Unexpected error ([chars]) at line [dec] func [chars]() file [chars]
Explanation An unexpected internal system 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%IDS-7-UNSUPPORTED_PARAM : [chars] [dec]:[dec] [chars]=[chars] - This parameter is not supported
Explanation An unsupported parameter has been encountered while an SDF file was being parsed. IDS 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 IDS in the Cisco IOS software.
Error Message%IDS-4-UNSUPPORTED_SIG : [chars] [dec]:[dec] [chars]=[chars] - This signature cannot be supported
Explanation An unsupported parameter has been encountered an SDF file was being parsed. The unsupported parameter is required 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 IDS in the Cisco IOS software.
IF Messages
The following are Interface messages.
Error Message%IF-4-BACKWARD_COUNTERS : Corrected for backward [chars] counters ([int] -> [int]) on [chars]
Explanation A packet counter for the interface specified in the message has decreased in number. This condition can occur if a packet is counted and then dropped. This event was detected and corrected.
Recommended Action If this condition persists, 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%IF-3-BAD_MTU : Internal error. MTU on [chars] too large or negative. Truncating from [dec] to [int].\n
Explanation An internal software error has occurred. The system attempted to set the MTU on an interface to an invalid value.
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%IF-2-IDB_TABLE_INIT : Malloc failed while initializing idb table
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%IF-4-NOBGPROCESS : Network background process not running. [chars]
Explanation A process that manages network interface background processing is not yet running, but another system process has tried to send the process a message.
Recommended Action An interface on the router may have missed a request to bring itself up. If that happens, it may be necessary to reset the interface by entering the shutdown command followed by the no shutdown command.
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.
INTERFACE_API Messages
The following are binary API for the interface descriptor block messages.
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-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.
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-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.
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.
IP Messages
The following are IP messages.
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.
IP_SNMP Messages
The following are Simple Network Management Protocol (SNMP) messages that are specific to IP.
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.
IPACCESS Messages
The following are IP security messages.
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-WRONGSIZE : Incorrect length acl ipc xdr of type=[chars] len=[dec] received
Explanation An ACL message has been received that is of the wrong size for its 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 the function 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 count was accessed, it was found to be zero or negative.
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-CANT_SEND : [chars]: Cannot send IPC message from [hex] to [hex]: info [hex]
Explanation An error occurred while an IPC message was being sent.
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-4-CONSISTENCY : Consistency check failed for [chars] [hex]
Explanation This message provides debugging information. An action that was 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 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-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 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-4-GET_PAK_MSG : Failed for message size [dec]
Explanation The system was unable to allocate an IPC message of the required size.
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.
Enter the following commands to attempt to gather more information on the nature of the problem:–
–
–
Error Message%IPC-3-GIANT : Request for giant IPC packet denied. Request size = [dec]
Explanation A message that was too large for the IPC system has been requested.
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-INVALID : [chars] Dest Port [hex] Session [hex] Source [hex]
Explanation IPC encountered invalid data in its internal data structures while an incoming message was being processed.
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-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-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 went below the application reserve count.
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-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 An IPC message that was returned is of a null value.
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-NO_ACK_HANDLER : No handler for ACK with data for port [hex].
Explanation The IPC receiver appended data to an ACK message, but the corresponding ACK message could not be processed at the sender.
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-NOBOOL : Boolean NULL in IPC message: [hex].
Explanation A watched Boolean operator that was allocated during the sending of the message was found to be null when an ACK message arrived.
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-3-NOBUFF : The [chars] IPC message header cache is empty
Explanation The specified IPC message header cache is empty, and an incoming IPC message may be dropped as a result.
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-NODELFUNC : Failed to intialize IPC client
Explanation An IPC application cannot be initialized because its initialization function does not appear 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-NODISPATCH : Message for [dec].[dec] has no receive queue or dispatch routine
Explanation The IPC user failed to provide any means of processing the received message.
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-2-NOMEM : No memory available for [chars]
Explanation The IPC protocol subsystem could not obtain the memory it needed.
Recommended Action If this error message recurs, attempt to reduce memory usage by reducing the number of router features or interfaces, enabled. Alternatively, add more memory.
Enter the following commands to attempt to gather more information on the nature of the problem:–
–
–
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 : Invalid operation at interrupt level: [chars] [hex]
Explanation This message provides debugging information. An IPC application has attempted an IPC action that has been prohibited from being performed at the interrupt level.
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-2-PRECLOSE : IPC port pre-closure overflow : [hex] : [hex]
Explanation An application has attempted to close an IPC port when there are messages still pending in the retransmit queue. As a result of this condition, the IPC defer table has overflowed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show ipc ports open 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 open commands and your pertinent troubleshooting logs.
Error Message%IPC-5-QFULL : Q=[hex] [chars] [dec]
Explanation The IPC queue is full. This condition could be due to high IPC traffic or high CPU utilization.
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-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 : Cannot hold RPC message 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 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-UNLOCK : Unlock done on already unlocked 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-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.
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 has malfunctioned, and its IPC is not active.
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%IPCGRP-3-CMDOP : IPC command [int] (slot[int]/[int]): [chars]
Explanation IPC command processing operational errors have 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%IPCGRP-3-CREATE_FAIL : [chars] [chars]
Explanation An IPC port could not be created on the RP.
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%IPCGRP-3-ERROR : [chars]: [chars]
Explanation An IPC error was detected.
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%IPCGRP-3-EVENTOP : Event [int] from slot[int]/[int]: [chars]
Explanation IPC event processing operational errors have 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%IPCGRP-3-EXECCMDMSG : Incorrect msg size (size=[int])
Explanation A REXEC-On IPC command of the wrong size was encountered.
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%IPCGRP-3-INVALID_PARAMS : Invalid interface([int]/[int]/[int])
Explanation The IPC message corresponding to this message contained an invalid interface address.
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%IPCGRP-3-INVNUM : [chars] ([int])
Explanation The IPC application tried to send a message that too large for the IPC to process. The message was not transmitted.
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%IPCGRP-3-MSGERR : [chars] ([int])
Explanation The slave IPC cannot register with the master. It cannot exchange messages with the master.
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%IPCGRP-3-NBLKCMD : [chars]
Explanation A nonblocking IPC command queue initialization failure 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%IPCGRP-6-NBLKCMD_Q_FULL : Nonblocking IPC command queue full ([dec] commands)
Explanation A nonblocking IPC command queue has filled up and was flushed to avoid overflow of 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 corresponding IPC message interface address.
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%IPCGRP-3-NULLMSG : Null [chars] ipc message
Explanation An empty IPC message was received. This message was not expected to be received.
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%IPCGRP-3-NULLREXECCMD : Received empty ipc rexec cmd message
Explanation A REXEC-On IPC command failure 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%IPCGRP-3-REXEC : [chars]
Explanation A REXEC-On IPC command failure 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%IPCGRP-3-SEATERR : [chars] ([int])
Explanation The ID associated with an IPC card either is missing, is duplicated, or cannot 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%IPCGRP-3-SYSCALL : System call for command [int] (slot[int]/[int]) : [chars] (Cause: [chars])
Explanation An IPC kernel system call 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.
IPCOIR Messages
The following are 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 are out of phase.
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 are out of phase.
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-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-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 in slot [int]/[int]
Explanation The card in the slot and subslot is being loaded.
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-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-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-3-FLASHFAIL : Couldn't load [chars]...\n
Explanation The specified image is inaccessible or cannot be found.
Recommended Action Check the filename.
Error Message%IPCOIR-3-IMAGEVERSION : Image version stamp missing
Explanation The loaded image did not contain a recognizable version stamp.
Recommended Action Replace the image with one that contains bits that are known to be good (good-known bits). Retry the operation.
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_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 [int]/[int] rejected
Explanation The line card buffer download server has rejected the download.
Recommended Action Unavailable.
Error Message%IPCOIR-3-LOADER_IPC_FAIL : IPC failed ([chars]) [chars] slot [int]/[int]
Explanation The Cisco IOS software IPC protocol has reported an unexpected error.
Recommended Action Make sure the indicated card is still plugged in.
Error Message%IPCOIR-3-LOADER_SERVER_FAIL : Remote server refused to load slot [int]/[int]
Explanation Unavailable.
Recommended Action Unavailable.
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-4-REPEATMSG : IPC handle already exists for [dec]/[dec]
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%IPCOIR-3-STATE_MACHINE_BUG : card_oir_loading() called, should never happen, recovering.
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%IPCOIR-3-STATE_MACHINE_BUG2 : card_oir_insert_card: already have [hex], removing.
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%IPCOIR-3-TFTPFAIL : TFTP of [chars] from [chars] failed...\n
Explanation The indicated Cisco IOS software image is inaccessible.
Recommended Action Check permissions for the file and the network connectivity.
Error Message%IPCOIR-3-TIMEOUT : Timeout waiting for a response from slot [dec]/[dec].
Explanation Unavailable.
Recommended Action Unavailable.
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.
IPC_RPM Messages
The following are interprocess communication (IPC) messages.
Error Message%IPC_RPM-3-INVMSG : [chars] ([dec])
Explanation An invalid IPC message was received while the change card (cc) command was being processed.
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-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.
IPC_URM Messages
The following are interprocess communication messages.
Error Message%IPC_URM-3-INVTIMER : Invalid URM expired timer type [dec]
Explanation The system has detected an invalid URM expired timer 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.
IPFAST Messages
The following are IP fast switching messages.
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.
IPMCAST_LIB Messages
The following are IP Multicast library messages.
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-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-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.
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.
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.
Recommended Action 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-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-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-PATHIDX : Bad path pointer of [hex] for [IP_address], [dec] max
Explanation A 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-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.
IPS Messages
The following are 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 IP storage 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:
–
–
–
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-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-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-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.