Feedback
Table Of Contents
IOS_LICENSE_IMAGE_APPLICATION-3
IOS_LICENSE_IMAGE_APPLICATION-6
HA_IFINDEX Messages
This section contains high availability system messages.
Error Message %HA_IFINDEX-2-INIT_ERROR: [chars]Explanation This is a critical error message about a high availability system initilization status or condition. A message of this type indicates that a failure occurred during high availability system initialization.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
HARDWARE Messages
This section contains hardware resources messages.
HARDWARE-3
Error Message %HARDWARE-3-ASICNUM_ERROR: Port-ASIC number [dec] is invalidExplanation Each port ASIC is identified by an ID. The port ASIC number that is specified in the message text is invalid. This condition indicates 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HARDWARE-3-INDEX_ERROR: Index value [dec] is invalidExplanation An index was attempted to be placed into the hardware table, but that index is out of the configured range.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HARDWARE-3-INTRNUM_ERROR: Port-ASIC Interrupt number [dec] is invalidExplanation An interrupt ID that was used for a port ASIC is invalid.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HARDWARE-3-PORTNUM_ERROR: port number [dec] is invalidExplanation Each interface in a given port ASIC is identified by an index value. The port number used is not within the specified range.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HARDWARE-3-STATS_ERROR: Statistics ID [dec] is invalidExplanation Each statistic that is supported by the port ASIC is identified using an ID. The ID provided by the caller is not within the configured range.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
HAWKEYE-1
Error Message %HAWKEYE-1-UNAVAILABLE: HAWKEYE(bay %d), Port adapter requires Rev 2 CPU, shutting down bayExplanation This message is specific to Cisco 7200 series router platforms. It indicates that the device driver has detected an NPE150 CPU version earlier than revision 2. The token ring device driver requires capabilities of a NPE150 revision 2 and later CPU.
Recommended Action Upgrade the 7200 router processor to an NPE150 Revision 2 or later.
Error Message %HAWKEYE-1-UNAVAILABLE: Only found %d interfaces on bay %d, shutting down bayExplanation This message may be emitted during IOS initialization or after a token ring port adapter/module is OIR inserted. The message indicates that the token ring device driver was unable to communicate with all of the interfaces expected to be on the port adapter/module. This could mean that one or more of the interfaces is not functioning.
Recommended Action Re-seat the port adapter/module in the slot. Also try installing it in another slot if available. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HAWKEYE-1-UNAVAILABLE: PCI memory unavailable for %sExplanation The device driver for this interface was unable to allocate the necessary amount of shared memory between the driver and the interface hardware. This condition can occur if the system contains less than the recommended minimum amount of SRAM for the current interface combination. Shared memory blocks are required for the interface to function. So, this interface will be inoperable until the memory shortage is corrected.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
HAWKEYE-3
Error Message %HAWKEYE-3-UNAVAILABLE: %s failed to initialize - %sExplanation The token ring interface encountered an error while attempting to open a connection to the ring. The specific error that occured is described in the last half of the error message as one of the following: 1) 'microcode checksum failed' - the MAC microcode was found to be corrupted inside the interface's local memory. 2) 'failed to build receive descriptor ring' - there was not enough system memory available to allocate receive buffers for packets. 3) 'init failed' - the interface hardware rejected the device driver's request to configure and open the interface.
Recommended Action Reset the interface using the 'clear interface token' exec command. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HAWKEYE-3-UNAVAILABLE: Interface %s, adapter check errorExplanation The token ring interface encountered an unrecoverable error condition while it was operating and connected to the ring. The interface will automatically shut itself down.
Recommended Action Issue the 'clear interface token' command to restart the interface. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
HA_CONFIG_SYNC-3
Error Message %HA_CONFIG_SYNC-3-UNAVAILABLE: %sExplanation Active and Standby configuration out of sync LBL what was attempted and what went wrong will be printed.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HA_CONFIG_SYNC-3-UNAVAILABLE: %sExplanation Bulk config sync failure, the reason for the failure will be provided in the string
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HA_CONFIG_SYNC-3-UNAVAILABLE: %sExplanation General Config Sync 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HA_CONFIG_SYNC-3-UNAVAILABLE: %sExplanation Line by Line sync failure what was attempted and what went wrong will be printed.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HA_CONFIG_SYNC-3-UNAVAILABLE: %s [%s]Explanation Bulk config sync filesys failure, the reason for the failure will be provided in the string
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HA_CONFIG_SYNC-3-UNAVAILABLE: %s with error code [ %s ]Explanation An ISSU Config Sync Registration Error occurred. The details about what was attempted and what went wrong will be printed.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HA_CONFIG_SYNC-3-UNAVAILABLE: CONFIG SYNC %s msg_type[%d], rc[%d]Explanation An ISSU Config Sync failed to transform messge. The details about what was attempted and what went wrong will be printed.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HA_CONFIG_SYNC-3-UNAVAILABLE: CONFIG SYNC Failed to get MTU Size for session[%d] msg_type[%d], MTU[%d], rc[%d]Explanation An ISSU Config Sync failed to get Messge MTU. The details about what was attempted and what went wrong will be printed.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HA_CONFIG_SYNC-3-UNAVAILABLE: Cannot communicate boot variable to standby (%s)Explanation Active failed to send the boot variable specified to standby. A reload or a switchover operation will likely result in the standby booting a wrong image.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HA_CONFIG_SYNC-3-UNAVAILABLE: Cannot communicate config register to standbyExplanation Active failed to send the config register to standby. The active and standby supervisors won't have the same config registers.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HA_CONFIG_SYNC-3-UNAVAILABLE: IPC operation failed for [ %s ] with error code [ %s ]Explanation A config sync error occurred. The details about what was attempted and what went wrong will be printed.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HA_CONFIG_SYNC-6-UNAVAILABLE: Bulk Sync succeededExplanation Bulk Sync has succeeded
Recommended Action No action necessary
Error Message %HA_CONFIG_SYNC-6-UNAVAILABLE: CONFIG SYNC : Subcode not matching for command %s Active subcode[0x%x], Standby subcode[0x%x]Explanation The line by line synchronization of a command has succeeded. A command entered on the active system was successfully synchronized with the standby system. However, the sub code of Parser Return Code, that were returned by the Active and Standby systems were different. However, the sub code of Parser Return Code, that were returned by the Active and Standby systems where different.
Recommended Action Normally, no action is required. If, however, any problems with line by line synchronization are found, copy this message exactly as it appears on the console or in the system log and contact your Cisco technical support representative.
HA_EM-3
Error Message %HA_EM-3-UNAVAILABLE: %s: Checksum error for policy %s - this policy will not be runExplanation The checksum computed for the specified policy does not match the original checksum computed when the policy was registered.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-3-UNAVAILABLE: %s: Error attempting to fetch event information: %s.Explanation The Embedded Event Manager Policy Director failed to receive event info for a callback.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-3-UNAVAILABLE: %s: Error occurred while fetching TTY number.Explanation The Embedded Event Manager failed to fetch a TTY number.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-3-UNAVAILABLE: %s: Error occurred while fetching action information: %d.Explanation The Embedded Event Manager Policy Director failed to gather action information registered for the event.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-3-UNAVAILABLE: %s: Error occurred while fetching variable information: %d.Explanation The Embedded Event Manager Policy Director was unable to set the variable with the requested information.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-3-UNAVAILABLE: %s: Error occurred while performing action: %s.Explanation The Embedded Event Manager Policy Director failed to perform an action for the registered event.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-3-UNAVAILABLE: %s: Failed to create processExplanation The process create function reports an error
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-3-UNAVAILABLE: %s: Failed to look up in the table the registration specification for policy %s.Explanation A table lookup for the registration specification for the policy failed.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-3-UNAVAILABLE: %s: Failed to perform CNS action: %sExplanation The Embedded Event Manager failed attempting to send a CNS message.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-3-UNAVAILABLE: %s: No such event id found.Explanation An internal software error occurred.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-3-UNAVAILABLE: %s: No such event spec id found.Explanation The Embedded Event Manager Policy Director could not find the event for the event spec. ID.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-3-UNAVAILABLE: %s: Published event type does not match event spec.Explanation The Embedded Event Manager Policy Director detected a mis-match in event type between the published event and the event spec.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-3-UNAVAILABLE: %s: The %s event detector I/O queue empty.Explanation The I/O queue is empty at this point, and should not be.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-3-UNAVAILABLE: %s: The I/O queue empty.Explanation The I/O queue is empty at this point, and should not be.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-3-UNAVAILABLE: %s: The Unable to enqueue packet onto queue.Explanation The queue is not in a state to handle enqueues.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-3-UNAVAILABLE: %s: The Unable to initialize queue.Explanation The queue cannot be initialized.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-3-UNAVAILABLE: %s: The following oid has become unavailable: %sExplanation The registered oid is no longer available in the system.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-3-UNAVAILABLE: %s: The hash computation routine reported an error; %sExplanation The fh_hash_md5_fd() function reported the specified error.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-3-UNAVAILABLE: %s: This processor is not in ACTIVE state (state = %d). Switchover must be performed on ACTIVE processor.Explanation Switchovers must occur on ACTIVE unit, not STANDBY unit.
Error Message %HA_EM-3-UNAVAILABLE: %s: Unable to initialize queue;Explanation The queue initialization function reported an error.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-3-UNAVAILABLE: %s: Unable to open %s; %sExplanation The open function reported an error.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-3-UNAVAILABLE: %s: Unable to open connection to CNS Event Agent: %dExplanation The CNS Action process failed to open CNS handle to Event Agent.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-3-UNAVAILABLE: %s: Unknown event type found in applet.Explanation The Embedded Event Manager applet had an unknown event type.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-3-UNAVAILABLE: %s: callback handler process create failed for eid: %dExplanation The process_create function reported an error trying to create the callback handler process.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-3-UNAVAILABLE: %s: could not find environment variable: %sExplanation The Embedded Event Manager policy director could not find the environment variable specified in the action message.
Recommended Action Only use well known Embedded Event Manager environment variables. If the message continues to occur, copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-3-UNAVAILABLE: %s: could not initialize Embedded Event Manager service: %sExplanation An internal error was detected when initializing Embedded Event Manager service.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-3-UNAVAILABLE: %s: could not initialize queueExplanation An internal error was detected when initializing Embedded Event Manager queue.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-3-UNAVAILABLE: %s: error processing xml bufferExplanation An error occurred processing the event publish information xml buffer.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-3-UNAVAILABLE: %s: failed to create an IPC port: %sExplanation Embedded Event Manager failed to create an IPC port.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-3-UNAVAILABLE: %s: failed to execute callbackExplanation Failed to execute callback routine.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-3-UNAVAILABLE: %s: failed to open an IPC port: %sExplanation Embedded Event Manager failed to open an IPC port.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-3-UNAVAILABLE: %s: failed to register an IPC port: %sExplanation Embedded Event Manager failed to register an IPC port.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-3-UNAVAILABLE: %s: fh_init failed : %dExplanation The fh_init function reported an error trying to initialize EEM for a callback process.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-3-UNAVAILABLE: %s: file checksum mismatchExplanation The checksum value of an installed policy does not match the value provided by the installation manager.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-3-UNAVAILABLE: %s: unable to set state for tracking object number %u; object does not exist or is not a stub-object.Explanation The Embedded Event Manager applet attempted to set the state of a tracking object that does not exist.
Recommended Action Only set the state of tracking objects that have already been configured in the system. If the message continues to occur, copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-3-UNAVAILABLE: Error attempting to access an unopened CLI session: %sExplanation An error occurred attempting to access an unopened CLI session: %s
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HA_EM-3-UNAVAILABLE: Error disconnecting from CLI session: %sExplanation An error occurred while disconnecting from the CLI session.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HA_EM-3-UNAVAILABLE: Error executing applet %s statement %sExplanation The Embedded Event Manager policy director found an error when processing an applet.
Recommended Action Check syntax of applet statement. If the message continues to occur, copy the message exactly as it appears, and report it your technical support representative.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HA_EM-3-UNAVAILABLE: Error occurred when sending mail to SMTP server: %s : %sExplanation An unexpected error occurred when sending mail to SMTP server.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HA_EM-3-UNAVAILABLE: Unable to establish CLI session: %sExplanation Unable to establish CLI session.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HA_EM-3-UNAVAILABLE: Unable to read CLI response: %sExplanation Unable to read CLI response.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HA_EM-3-UNAVAILABLE: Unable to send CLI command: %sExplanation Unable to send CLI command.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HA_EM-3-UNAVAILABLE: Unable to send notification using all SMTP serversExplanation An unexpected error occurred when sending mail to all SMTP servers.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HA_EM-3-UNAVAILABLE: Use of the rack keyword in the correlate statement is not supported in this image.Explanation The Embedded Event Manager Track ED is not supported in this image.
Recommended Action Track ED is not available in this image
HA_EM-4
Error Message %HA_EM-4-UNAVAILABLE: %s: No tag %s found corresponding to this event publish.Explanation The Embedded Event Manager policy director could not associate the tagname with a published event.
Recommended Action Only use tagnames in the action info type event reqinfo command which correspond to the published event.
Error Message %HA_EM-4-UNAVAILABLE: %s: failed to allocate an IPC bufferExplanation Embedded Event Manager failed to allocate a buffer from IPC.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-4-UNAVAILABLE: %s: failed to create an event: %sExplanation Failed to create an Embedded Event Manager event.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-4-UNAVAILABLE: %s: failed to register an event: %sExplanation Failed to register an Embedded Event Manager event.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-4-UNAVAILABLE: %s: failed to send an IPC message: %sExplanation Embedded Event Manager failed to send a message through IPC.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-4-UNAVAILABLE: Cisco Signature not found or invalid. %s has been registered as a user policy.Explanation Cisco Signature not found or invalid.
Recommended Action Sign with Cisco signature.
Error Message %HA_EM-4-UNAVAILABLE: No action configured for applet %sExplanation No action has been configured for this applet.
Recommended Action Configure at least one action for this applet.
Error Message %HA_EM-4-UNAVAILABLE: No event configured for applet %sExplanation No event has been configured for this applet.
Recommended Action Configure an event for this applet.
Error Message %HA_EM-4-UNAVAILABLE: No threads are configured to service event class %sExplanation The Embedded Event Manager has no scheduler threads to service this event class.
Recommended Action Configure threads for the event class using the 'event manager scheduler' command.
HA_EM-6
Error Message %HA_EM-6-UNAVAILABLE: %s: %sExplanation The Embedded Event Manager reports an error on Event Manager configuration
Recommended Action Check the EEM applet or policy configuration
Error Message %HA_EM-6-UNAVAILABLE: %s: Cannot change a class %s %s to priority LAST. LAST is for default policies onlyExplanation Embedded Event Manager Scheduler Command can only change a default policy to priority LAST.
Recommended Action The command is applicable to default policies only.
Error Message %HA_EM-6-UNAVAILABLE: %s: Cannot modify a LAST policy to class %s. LAST policies are for class default only.Explanation Embedded Event Manager LAST policy is for default class only.
Recommended Action The command is applicable to default policies only.
Error Message %HA_EM-6-UNAVAILABLE: %s: Error adding trapvar to queue %sExplanation The trap variable was not added to the queue.
Recommended Action Check the EEM applet or policy configuration
Error Message %HA_EM-6-UNAVAILABLE: %s: No variable %sExplanation The variable is not defined.
Recommended Action Check the EEM applet or policy configuration
Error Message %HA_EM-6-UNAVAILABLE: %s: Policy has requested a hardware switchoverExplanation An Embedded Event Manager policy requested that a hardware switchover occur.
Error Message %HA_EM-6-UNAVAILABLE: %s: Policy has requested a hardware switchoverExplanation An Embedded Event Manager policy requested that a hardware switchover occur.
Recommended Action None
Error Message %HA_EM-6-UNAVAILABLE: %s: Policy has requested a system reload;Explanation An Embedded Event Manager policy requested that the system be reloaded.
Error Message %HA_EM-6-UNAVAILABLE: %s: cannot %s a running policy with jobid %d.Explanation Embedded Event Manager Scheduler Command cannot change a running policy.
Recommended Action The command is not applicable to a running policy.
Error Message %HA_EM-6-UNAVAILABLE: %s: duplicate oidExplanation The oid is a duplicate
Recommended Action Check the EEM applet or policy configuration
Error Message %HA_EM-6-UNAVAILABLE: %s: number of values exceeded %dExplanation The number of values per variable exceeded the maximum
Recommended Action Check the EEM applet or policy configuration
Error Message %HA_EM-6-UNAVAILABLE: %s: unable to modify the policy to class %s: scheduling rule unavailable.Explanation There is no scheduler rule configured to service this event class.
Recommended Action Please configure a scheduler rule before modifying the event.
Error Message %HA_EM-6-UNAVAILABLE: Error compiling regular expression: %sExplanation An error was encountered when compiling the given regular expression.
Recommended Action Check syntax of regular expression pattern. If the message continues to occur, copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-6-UNAVAILABLE: Failed to retrieve context for key %s: %sExplanation Failed to context retrieve variable information for event.
Recommended Action Ensure context information with the given key is saved. If the message continues to occur, copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-6-UNAVAILABLE: Failed to save variable context for key %s: %sExplanation Failed to context save variable information for event.
Recommended Action Ensure context information with the same key is not already saved. If the message continues to occur, copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-6-UNAVAILABLE: Invalid operand in action, expected value within range %ld to %ld, received: %sExplanation Arithmetic actions only accept valid long integer values.
Recommended Action Ensure value provided to action is long integer.
Error Message %HA_EM-6-UNAVAILABLE: Invalid operand in arithmetic division, cannot divide by zeroExplanation Arithmetic division does not allow divide by zero.
Recommended Action Ensure denominator provided to division action is non-zero.
Error Message %HA_EM-6-UNAVAILABLE: Policy update has copied %d bytes from %s to %sExplanation An EEM policy has been copied as a result of an event manager update command
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HA_EM-6-UNAVAILABLE: Policy update has failed to register policy %s %sExplanation An EEM policy has failed to be registered as a result of an event manager update command
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HA_EM-6-UNAVAILABLE: Policy update has failed to unregister policy %s %sExplanation An EEM policy has failed to be unregistered as a result of an event manager update command
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HA_EM-6-UNAVAILABLE: Policy update has successfully re-registered policy %sExplanation An EEM policy has been successfully re-registered as a result of an event manager update command
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
HA_EM-7
Error Message %HA_EM-7-UNAVAILABLE: %sExplanation Internal error. The event detector has failed to get a free history list entry.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-7-UNAVAILABLE: %s: %dExplanation The event detector has exceeded its maximum number of retries to send a pulse to the embedded event manager to notify of an event publish.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-7-UNAVAILABLE: %s: %sExplanation Internal error. The event detector has failed to rebuild the metric list from the checkpointed records.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-7-UNAVAILABLE: %s: %sExplanation The SNMP error code.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-7-UNAVAILABLE: %s: %s guard word corrupted; %pExplanation The guard word for the specified control block does not contain what is expected.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-7-UNAVAILABLE: %s: %s[%d]Explanation Internal error. The event detector has failed to fetch a data element from the statistics data engine.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-7-UNAVAILABLE: %s: Application client library unable to handle message receive.Explanation The API received a msg reply when it was not in a state to accept such messages.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-7-UNAVAILABLE: %s: CNS Event Agent not available: %dExplanation The CNS Event Agent is currently not available.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-7-UNAVAILABLE: %s: Class %s: Maximum number of %d %s publish entries exceeded; some events have been discardedExplanation An attempt to publish an event failed because there is no more room in the publish queue.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-7-UNAVAILABLE: %s: Failed to allocate Event Detector context control block; %sExplanation The get_fd function reported an error trying to allocate a Event Detector context control block.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-7-UNAVAILABLE: %s: Failed to duplicate string %s; %sExplanation The strdup function reported an error.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-7-UNAVAILABLE: %s: Failed to open Event Detector context control blockExplanation The open_fd function reported an error trying to open a Event Detector context control block.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-7-UNAVAILABLE: %s: Illegal SNMP address typeExplanation The SNMP address is illegal.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-7-UNAVAILABLE: %s: Invalid SNMP oid length %dExplanation The SNMP oid has invalid length
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-7-UNAVAILABLE: %s: Invalid argument string: %sExplanation An invalid argument string was passed to the specified function.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-7-UNAVAILABLE: %s: Policy execution %sExplanation The Embedded Event Manager policy excution state has been changed to the state named in the message.
Error Message %HA_EM-7-UNAVAILABLE: %s: SNMP IPV6 address is not supportedExplanation The IPV6 address is not supported.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-7-UNAVAILABLE: %s: SNMP build pdu failedExplanation The SNMP pdu build has failed.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-7-UNAVAILABLE: %s: SNMP make pdu failedExplanation The SNMP pdu make has failed.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-7-UNAVAILABLE: %s: SNMP proxy exec got event, but queue is emptyExplanation The SNMP proxy got event but the queue is empty.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-7-UNAVAILABLE: %s: SNMP request failedExplanation The SNMP request has failed.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-7-UNAVAILABLE: %s: SNMP response cancelledExplanation The SNMP response has been cancelled.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-7-UNAVAILABLE: %s: SNMP response error; error_status = %dExplanation The SNMP response has error.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-7-UNAVAILABLE: %s: SNMP response has timed outExplanation The SNMP response has timed out.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-7-UNAVAILABLE: %s: The script name is NULLExplanation An invalid script name was passed as an argument into the specified function.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-7-UNAVAILABLE: %s: The system is unable to switch to standby processor. Switchover cancelled.Explanation Switchovers must occur when STANDBY is available and ready.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-7-UNAVAILABLE: %s: Unable to add %s event detector command;Explanation The Event detector failed to add command.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-7-UNAVAILABLE: %s: Unable to add action %s command;Explanation Failed to add action command.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-7-UNAVAILABLE: %s: Unable to allocate %s; %sExplanation The malloc function reported an error.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-7-UNAVAILABLE: %s: Unable to allocate %s;Explanation The malloc function reported an error.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-7-UNAVAILABLE: %s: Unable to allocate memory for event publish timer blockExplanation Internal error. The event detector has failed to allocate memory for the event publish timer block.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-7-UNAVAILABLE: %s: Unable to build an oid string into a SNMP oid; oid = %sExplanation The oid string was not able to build into a SNMP oid
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-7-UNAVAILABLE: %s: Unable to clear restart callback;Explanation The CNS Action process failed to clear restart callback.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-7-UNAVAILABLE: %s: Unable to create SNMP octet community string; string = %sExplanation The community string was not able to build into a SNMP octet string
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-7-UNAVAILABLE: %s: Unable to create a SNMP message; community = %sExplanation The SNMP message failed to be created
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-7-UNAVAILABLE: %s: Unable to create a SNMP varbindExplanation The oid failed to make into a SNMP varbind
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-7-UNAVAILABLE: %s: Unable to enqueue %s;Explanation The enqueue function reported an error.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-7-UNAVAILABLE: %s: Unable to locate reg callback entry for pulse code %dExplanation The registration callback handler was unable to validate the pulse code received.
Recommended Action The pthread_create function reported an error.
Error Message %HA_EM-7-UNAVAILABLE: %s: Unable to reallocate %s; %sExplanation The realloc function reported an error.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-7-UNAVAILABLE: %s: Unable to send response for FH_MSG_CALLBACK_DONE %sExplanation The registration callback handler was unable to send the FH_MSG_CALLBACK_DONE message to the Embedded Event Manager Server.
Recommended Action The pthread_create function reported an error.
Error Message %HA_EM-7-UNAVAILABLE: %s: Unable to set restart callback;Explanation The CNS Action process failed to set the restart callback.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-7-UNAVAILABLE: %s: Unknown SNMP operation or response type %dExplanation The operation or response type is unknown.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-7-UNAVAILABLE: %s: could not create a leaf timerExplanation Internal error. The event detector has failed to create a managed leaf timer.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-7-UNAVAILABLE: %s: could not create an occurrence entryExplanation Internal error. The event detector has failed to create an entry for the matched occurrence list.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-7-UNAVAILABLE: %s: could not remove an occurrence entryExplanation Internal error. The event detector has failed to remove an entry for the matched occurrence list.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-7-UNAVAILABLE: %s: create_watched_boolean failed: %sExplanation The create_watched_boolean function reported an error trying to create the watched boolean.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-7-UNAVAILABLE: %s: create_watched_boolean failed; %sExplanation The create_watched_boolean function reported an error trying to create the watched boolean.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-7-UNAVAILABLE: %s: create_watched_queue failed; %sExplanation The create_watched_queue function reported an error trying to create the watched queue.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-7-UNAVAILABLE: %s: delete_watched_boolean failed: %sExplanation The delete_watched_boolean function reported an error trying to delete the watched boolean.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-7-UNAVAILABLE: %s: error attemting to format time stringExplanation Format time failure.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-7-UNAVAILABLE: %s: invalid comparison operator: %dExplanation Internal error. The value comparison operator is invalid or not supported.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-7-UNAVAILABLE: %s: invalid last policy name replied %sExplanation Internal error. The last policy name the script director replied to show fm policy registered command is an invalid policy name.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-7-UNAVAILABLE: %s: invalid statistics value type: %dExplanation Internal error. The statistics data type is invalid or not supported.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-7-UNAVAILABLE: %s: invalid timer type: %dExplanation Internal error. The timer type is invalid or not supported.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-7-UNAVAILABLE: %s: invalid timer: type=%d, timer=%pExplanation Internal error. The timer value is invalid or not as expected.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-7-UNAVAILABLE: %s: not enough memory: %sExplanation Allocating memory failed due to a low-memory condition.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-7-UNAVAILABLE: %s: resource_monitor_register failed; return code = %dExplanation The resource_monitor_register function reported an error trying to register for RMI notifications.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message %HA_EM-7-UNAVAILABLE: %s: unknown event type %dExplanation An unknown Embedded Event Manager even type was detected.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
HD-1
Error Message %HD-1-UNAVAILABLE: 4T Port Adapter fault on port %d in slot %dExplanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %HD-1-UNAVAILABLE: Loopback not supported for a 4T DTE/X.21, port %d in slot %dExplanation Loopback mode is not allowed when using an X.21 DTE cable on a Quad serial NIM port.
Recommended Action Do not enable loopback, or use a different cable type.
Error Message %HD-1-UNAVAILABLE: msgtxt_badringsizeExplanation An internal software error occurred.
Recommended Action If message recurs, call your technical support representative for assistance.
HD-5
Error Message %HD-5-UNAVAILABLE: Unit %d excessive modem control changesExplanation Too many modem control interrupts have been received. The port was disabled to prevent excessive use of the CPU.
Recommended Action Check the cable on the serial port.
HA_WD Messages
This section contains high availability system messages.
HA_WD-3
Error Message %HA_WD-3-DM_SEND_PULSE: [chars]: could not send priority pulse to receiver: [chars]Explanation An attempt to send a priority pulse to the receiver 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HA_WD-3-PROCFS_PASS: [chars]: procfs pass ended in error after five consecutive passesExplanation A call to the wd_procfs_per_process() function ended in error after five consecutive passes.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HA_WD-3-PTHRD_SETDETACHSTATE: [chars]: could not set detach state of a POSIX thread: [chars]Explanation An internal error was detected when trying to set the detach state of a POSIX thread.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HA_WD-3-PTHRD_SETSCHEDPARAM: [chars]: could not set scheduler param of a POSIX thread: [chars]Explanation An internal error was detected when trying to set the scheduler parameter of a POSIX thread.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HA_WD-3-RESTART_WDSYSMON: [chars]: Error returned from sysmgr_restart_self() [chars]Explanation An error was returned from the sysmgr_restart_self API.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
HA_WD-6
Error Message %HA_WD-6-BLOCKED_THREAD: A default priority thread CPU starvation condition was detectedExplanation Some higher priority threads are blocking the CPU.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HA_WD-6-CPU: [chars]Explanation The CPU is blocked by one or more high priority threads.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HA_WD-6-DLK: [chars]Explanation An unresolved process or Cisco IOS scheduler deadlock 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
HA_WD-7
Error Message %HA_WD-7-GUARD_WORD_CORRUPTED: [chars]: [chars] guard word corrupted [hex]Explanation The named control block guard word was corrupted.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
HDLC Messages
This section contains high-level data link control (HDLC) messages.
HDLC-1
Error Message %HDLC-1-ISSU_NOMEMORY: Unit [dec], no memory for [chars]Explanation The requested operation could not be accomplished because of a low-memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
HDLC-4
Error Message %HDLC-4-ISSU_INCOMPATIBLE: hdlc-issu-compat: returned FALSEExplanation The compatibility checking 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HDLC-4-ISSU_SENDFAILED: HDLC ISSU: send message failed, rc = [dec]Explanation An attempt to send a message 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HDLC-4-ISSU_XFORM: [chars]: failed, rc=[chars]Explanation The transform 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
HDV-1
Error Message %HDV-1-UNAVAILABLE: HDV in slot %d: No PCI memory available.Explanation The system is experiencing memory exhaustion in the PCI/packet memory. This is probably due to heavy traffic congestion but could also be a software error.
Recommended Action Review the configuration for performance bottlenecks. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HDV-1-UNAVAILABLE: HDV in slot %d: VIC daughter card (%s/0x%x) is unsupportedExplanation The VIC card plugged into the HDV is not of a supported type
Recommended Action Replace this VIC with a type that is supported by this version of IOS, or change the version of IOS to support this VIC type.
Error Message %HDV-1-UNAVAILABLE: HDV in slot %d: VIC daughter card has an unknown id of 0x%xExplanation The software did not recognize the type of VIC card plugged into the HDV Port Module.
Recommended Action Check the part number on the VIC card to see if it is supported in the version of IOS operational on the router or contact your technical support representative.
Error Message %HDV-1-UNAVAILABLE: HDV in slot %d: no VIC card is inserted in the HDV.Explanation The software did not detect the presence of a VIC card inserted in the HDV Port Module.
Recommended Action Check that there is a VIC card inserted properly into the HDV. If so, then check the part number on the VIC card to see if it is supported in the version of IOS operational on the router or contact your technical support representative.
Error Message %HDV-1-UNAVAILABLE: HDV in slot %d: packet size (%d) too big.Explanation A packet greater than the 256 bytes received on this interface.
Recommended Action The system should recover. No action is required. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
HDV-2
Error Message %HDV-2-UNAVAILABLE: HDV in slot %d: An unrecoverable error occurred.Explanation The HDV card experienced an internal unrecoverable error. This may be due to a internal firmware error or bad HDV hardware.
Recommended Action Power down, reinsert the network module and reboot. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
HDV-3
Error Message %HDV-3-UNAVAILABLE: HDV in slot %d: Incorrect %d PM-ID device not supported.Explanation A interface controller device did not have the correct PM-ID.
Recommended Action Check that the HDV is inserted properly. If necessary, turn off the router and reinsert the HDV Port Module. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HDV-3-UNAVAILABLE: HDV in slot %d: reports an invalid device id of %#x.Explanation The HDV port module hardware may be bad or improperly seated.
Recommended Action Power down, reinsert the network module and reboot. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HDV-3-UNAVAILABLE: HDV in slot %d: the HDV failed to initialize properly.Explanation An initialization action failed for the HDV. This can be caused by a lack of system resources, improper or no VIC installed in the port module, or it may be bad HDV hardware.
Recommended Action Power down. Check that a supported VIC module is properly installed in the HDV module. Reinsert the VIC module. Then reinsert the Port Module and reboot 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HDV-3-UNAVAILABLE: HDV in slot %d: the firmware on the port module did start properly.Explanation The firmware on the card did not start after a reset. This is usually caused by a bad HDV module or improperly seated HDV module.
Recommended Action Power down. Reinsert the HDV port module and reboot 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HDV-3-UNAVAILABLE: HDV in slot %d: the port module did not reset and start up properly.Explanation The hardware on the card did not start after a reset. This is usually caused by a bad HDV module or improperly seated HDV module.
Recommended Action Power down. Reinsert the HDV port module and reboot 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
HDX-3
Error Message %HDX-3-UNAVAILABLE: On int %d/%d, unexpected state %d, event %dExplanation A bad state, event pair is detected in the rx/tx half duplex state machine.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
HLFM Messages
This section contains Forwarding Manager messages.
HLFM-3
Error Message %HLFM-3-MACFREE_ERROR: MAC address [enet], vlad [dec] is still referenced; cannot freeExplanation An attempt was made to free a MAC address before all references to it had been released.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HLFM-3-MAP_ERROR: IP address [IP_address] not in mac tables, mac-address [enet], vlan [dec]Explanation The IP address and MAC address tables have lost their synchronization.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HLFM-3-MOD_SD: Failed to modify Station Descriptor with index [dec], vlan [dec], di [dec], error [dec], mad [dec], ref-count [dec]Explanation The forwarding manager is attempting to modify a station descriptor that is no longer in use or is invalid.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
HMM_ASYNC-3
Error Message %HMM_ASYNC-3-UNAVAILABLE: Digital modem %d/%d on Simm %d failed power on diagnostics.Explanation Digital modem failed to pass power on diagnostics. It will not be used.
Recommended Action If remaining Simm(s) passed diagnostics, remove or replace this problem Simm before continuing. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %HMM_ASYNC-3-UNAVAILABLE: HMM Digital Modem Card %d experienced a TDM Synthesis Error.Explanation Digital Modem Card failed to send or receive PCM data in time to avoid data loss. This may cause the modems to speed shift, retrain, or hangup.
Recommended Action Verify that the DS1 interface(s) share a common clock source. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HMM_ASYNC-3-UNAVAILABLE: HMM Modem %d/%d Mailbox is Full, command %#x not sent.Explanation Error delivering commands to Modem Module. This may be a transient failure. If this message repeats every 30 seconds it may indicate a failed Modem Module.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HMM_ASYNC-3-UNAVAILABLE: HMM Modem %d/%d failed to accept a new command.Explanation Modem failed to accept a new command. This may be a transient failure or the modem may remain unusable until a system reset.
Recommended Action You may try to reset the modem by issuing the clear modem slot/port command. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HMM_ASYNC-3-UNAVAILABLE: HMM: Digital Modem Card %d hardware exception : %sExplanation This may be an intermittent or permanent hardware 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HMM_ASYNC-3-UNAVAILABLE: No memory for %s of unit %dExplanation The router does not have enough memory to perform the function
Recommended Action Consider adding more shared memory. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HMM_ASYNC-3-UNAVAILABLE: Received unknown message 0x%x at mail offset %d from modem %d/%d.Explanation Received unidentifed message from modem. This is symtomatic of running with an incompatible version of modem firmware.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HMM_ASYNC-3-UNAVAILABLE: Simm %d in slot %d has halted due to a Runtime Error.Explanation The Portware running on the Simm was halted due a runtime error. The six modems contained on the Simm have been marked Bad and are no longer usable until the system is reloaded.
Recommended Action Copy the error message exactly as it appears, along with show modem and show modem log output, and report it to your technical support representative.
Error Message %HMM_ASYNC-3-UNAVAILABLE: Unable to creaet pool %d raw Tx mode buffersExplanation The router does not have enough I/O memory for buffers
Recommended Action Consider adding more shared memory. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HMM_ASYNC-3-UNAVAILABLE: Unable to create TTY structure for line %dExplanation Unable to create tty line control block for the specified line This may be due to not having enough memory in the router
Recommended Action Consider adding more shared memory. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HMM_ASYNC-3-UNAVAILABLE: Unable to create pool for %d raw Rx mode buffersExplanation The router does not have enough I/O memory for buffers
Recommended Action Consider adding more shared memory. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HMM_ASYNC-3-UNAVAILABLE: Unable to download firmware image to digital modem card in slot %d.Explanation Failed to bring up the processor on the digital modem 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HMM_ASYNC-3-UNAVAILABLE: Unable to download modem firmware image to Simm %d in slot %d.Explanation Failed to load modem firmware into the Simm.
Recommended Action If firmware successfully loaded into remaining Simm(s), remove or replace this problem Simm before continuing. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HMM_ASYNC-3-UNAVAILABLE: Unknown Platform type to support HMM Network ModuleExplanation The Network Module is not compatible with the current platform that it is plugged into.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
HMM_ASYNC-4
Error Message %HMM_ASYNC-4-UNAVAILABLE: HMM Digital Modem Card %d contains no active modems.Explanation There are no modems installed on the network module.
Recommended Action Make sure the network module contains properly installed MICA-6DM Simm(s).
HOOD-3
Error Message %HOOD-3-UNAVAILABLE: msgtxt_badunitExplanation An internal software error occurred.
Recommended Action If the message recurs, call your technical support representative for assistance.
HOOD-5
Error Message %HOOD-5-UNAVAILABLE: Unit %d, HP100VG, cable error. Training failedExplanation A 100VG cable or hub is faulty.
Recommended Action If the message recurs, and either the cable or hub appears to be good, repair or replace the router module.
Error Message %HOOD-5-UNAVAILABLE: Unit %d, HP100VG, no tone detected. Check cable, hubExplanation A 100VG cable is faulty.
Recommended Action If the message recurs, and either the cable or hub appears to be good, repair or replace the router module.
Error Message %HOOD-5-UNAVAILABLE: Unit %d, excessive collisionsExplanation An Ethernet cable is broken or unterminated, or the transceiver is unplugged.
Recommended Action If the transceiver appears to be properly terminated, repair or replace the router.
Error Message %HOOD-5-UNAVAILABLE: Unit %d, lost carrier. Transceiver problem?Explanation An Ethernet transceiver is unplugged or faulty.
Recommended Action Repair or replace the controller.
HP100VG Messages
HP100VG
Error Message %HP100VG-1-UNAVAILABLE: %s access to network deniedExplanation Access to the network is denied because of incompatible configuration.
Recommended Action Check the configuration of the hub for Frame Format, Promiscuous, and Repeater bit to indicate proper configuration.
Error Message %HP100VG-1-UNAVAILABLE: %s configuration not compatible with the networkExplanation Configuration of the router module is not compatible to the network
Recommended Action Check the configuration of the hub for Frame Format, Promiscuous, and Repeater bit to indicate proper configuration
Error Message %HP100VG-1-UNAVAILABLE: %s unable to login to the hubExplanation Unable to login to the hub.
Recommended Action Take action based on the following error messages.
Error Message %HP100VG-1-UNAVAILABLE: On %s LAN segmentExplanation Two VG devices on the same LAN segment have the same MAC address.
Recommended Action Check router configuration to make sure that no duplicate MAC address is configured.
Error Message %HP100VG-1-UNAVAILABLE: Only found %d interfaces on bay %d, shutting down bayExplanation No VG interface detected.
Recommended Action Make sure 100VG PA is properly seated in the slot. Otherwise repair or replace the 100VG PA interface module.
HP100VG-3
Error Message %HP100VG-3-UNAVAILABLE: %s hardware CAM device not foundExplanation Could not find Hardware CAM on the PA module
Recommended Action Repair or replace the 100VG PA interface module.
Error Message %HP100VG-3-UNAVAILABLE: %s packet buffer, pak=0x%xExplanation A software or hardware error occurred. The HP100VG driver detected that the buffer ring is in an inconsistent and unrecoverable state.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %HP100VG-3-UNAVAILABLE: Bay %d device ID seen as %#x, expected %#xExplanation Could not find 100VG PCI device
Recommended Action Make sure 100VG PA is properly seated in the slot. Otherwise repair or replace the 100VG PA interface module.
HP100VG-5
Error Message %HP100VG-5-UNAVAILABLE: %s cable fault; tone not detectedExplanation An 100VG cable is faulty.
Recommended Action Repair or replace the cable. If either the cable appears to be good, repair or replace the VG PA interface module.
Error Message %HP100VG-5-UNAVAILABLE: %s cable/hub problem?Explanation The VG controller detects link to the hub is down due to cable, hub or vg controller problem.
Recommended Action Repair or replace the cable or hub. If either the cable or hub appears to be good, repair or replace the VG PA interface module.
Error Message %HP100VG-5-UNAVAILABLE: %s training failedExplanation An 100VG cable or hub is faulty.
Recommended Action Repair or replace the cable or hub. If the cable or hub appears to be good, repair or replace the VG PA interface module.
HSRP Messages
This section contains Hot Standby Router Protocol (HSRP) messages.
HSRP-3
Error Message %HSRP-3-MISCONFIG: Attempt to change [chars] MAC address to [enet] when DECNET already runningExplanation An HSRP group attempted to become active on an interface that can only support 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.
Error Message %HSRP-3-NOSOCKET: Unable to open socketExplanation The system was unable to initialize an IP connection for the Hot Standby protocol.
Recommended Action Make sure that there is at least one interface configured to run IP.
HSRP-4
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 Use 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-BADAUTH2: Bad authentication from [IP_address]Explanation Two routers participating in HSRP disagree on the valid authentication string.
Recommended Action Use 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-BADVIP: [chars] Grp [dec] address [IP_address] is in the wrong subnet for this interfaceExplanation The HSRP virtual IP address contained in the Hello message cannot be learned as it is not within a subnet configured on the interface.
Recommended Action Check the configuration on all HSRP routers and ensure that the virtual IP address is within a configured subnet.
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 configured locally.
Recommended Action Check the configuration on all HSRP routers in the group and ensure 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 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 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. Check 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 as 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 interfaceExplanation The HSRP virtual IP address contained in the Hello message cannot be learned as 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 applicationExplanation The HSRP virtual IP address contained in the Hello message cannot be learned as 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.
HSRP-5
Error Message %HSRP-5-STATECHANGE: [chars] Grp [dec] state [chars] -> [chars]Explanation The router has changed state.
Recommended Action No action is required.
HTSP-3
Error Message %HTSP-3-UNAVAILABLE: no free event structure available from %s for DSP messageExplanation There were no event structures remaining in the system pools to alert the router of a voice or signaling event.
Recommended Action Check that the voice port for which the event was reported is still operational. If not, clear the voice port.
Error Message %HTSP-3-UNAVAILABLE: voice port %s: Ground Start trunking not supportedExplanation This voice port does not support the 'connection trunk' command when ground start signaling is configured. Trunking mode on this voice is supported when using loop start signaling.
Recommended Action Shut down the voice port, remove the 'connection trunk' and/or 'signal groundStart' command from the voice port configuration, and unshut the voice port.
Error Message %HTSP-3-UNAVAILABLE: voice port %s: call connection id [0x%x 0x%x 0x%x 0x%x]Explanation There was a capabilities mismatch between the two call legs. capabilities are negotiated between call legs for CODEC, VAD and FAX rate.
Recommended Action Check that the dial peer configuration is appropriate for the interface in question. Also check that and configuration on the interface is correct.
Error Message %HTSP-3-UNAVAILABLE: voice port %s: status=0x%x message=0x%x text=%sExplanation The DSP reported a fatal error. All calls on the DSP were dropped and a DSP reload was attempted.
Recommended Action Verify that the DSP reloaded properly by attempting to place a call on the affected voice port. Contact your technical support representative, include the full text of the error message.
HTSP-5
Error Message %HTSP-5-UNAVAILABLE: Trunk port(channel) [%s] is %sExplanation Trunk port:channel changed state.
Recommended Action LOG_STD_NO_ACTION
HTTP Messages
This section contains Hypertext Transfer Protocol (HTTP) messages.
HTTP-3
Error Message %HTTP-3-INIT_FAIL: HTTP Process Init failed.Explanation Initialization of the HTTP subsystem has failed.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message %HTTP-3-OUTOF_MEM: HTTP out of memory.Explanation An error occurred during initialization of the HTTP process. The HTTP process could not create crucial internal data structures that are required for operation of the HTTP subsystem. The most likely reason for this condition is an exhaustion of system memory.
Recommended Action Reduce other system activity to ease memory demands. if conditions warrant, upgrade to a larger memory configuration.
Error Message %HTTP-3-PROC_NOCREAT: Unable to create HTTP process.Explanation An error occurred during initialization of the HTTP process. The HTTP process that processes all HTTP requests and responses could not be created.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message %HTTP-3-SERVER_RESTART_FAILED: Server restart failed. Disabling HTTP server.Explanation TCP process was restarted affecting the HTTP server. Attempts to restart HTTP server failed.
Recommended Action Check status of TCP process. Enable the HTTP server after TCP process has started.
HTTP-6
Error Message %HTTP-6-SERVER_SETUP_FAILED: Server setup failedExplanation Setup of the HTTP or HTTPS server to listen on the specified port number has failed.
Recommended Action Disable the server, verify that port number is correct and enable the server. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
HUB-1
Error Message %HUB-1-UNAVAILABLE: Bad port number %dExplanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %HUB-1-UNAVAILABLE: Invalid hub type %d and number %dExplanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %HUB-1-UNAVAILABLE: Read op %d not allowedExplanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %HUB-1-UNAVAILABLE: Write op %d not allowedExplanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %HUB-1-UNAVAILABLE: msgtxt_nomemoryExplanation The system detected that there is not enough memory for the hub initialization.
Recommended Action If conditions warrant, upgrade to larger memory configuration.
HUJR-3
Error Message %HUJR-3-UNAVAILABLE: Read/write failed [%s]Explanation A read/write error occurred when accessing the hardware
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
HW Messages
This section contains hardware messages.
HW-2
Error Message %HW-2-OBSOLETE_HW_VER: Module Version in [chars] is obsolete ********************************************************************* * IMPORTANT !!! * * The module in [chars] is obsolete and must be returned * * via RMA to Cisco Manufacturing. If it is a lab unit, * * it must be returned to Proto Services for upgrade. * *********************************************************************Explanation The specified hardware is obsolete and needs to be replaced.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
HWMATM_MOD-3
Error Message %HWMATM_MOD-3-UNAVAILABLE: Unexpected null pointer in %s at %dExplanation An internal software error 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
HW_API Messages
This section contains hardware API messages.
HW_API-3
Error Message %HW_API-3-BACKWALK_REQUEST: Backwalk request failed, [chars]Explanation A request to walk internal data structures has failed. Depending on the criticality of the data, the accuracy of forwarding may be affected.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HW_API-3-BACKWALK_REQUEST_VALUE: Backwalk request failed, [chars] ([hex])Explanation A request to walk internal data structures has failed. Depending on the criticality of the data, the accuracy of forwarding may be affected.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HW_API-3-INVALID_CONTEXT: Invalid context [hex]Explanation An internal API 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HW_API-3-INVALID_OBJ: Invalid object [hex]Explanation An internal API 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HW_API-3-INVALID_TYPE: Invalid type [dec]Explanation An internal API 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HW_API-3-INVALID_WALK_SPEC: Invalid walk spec [hex]Explanation An internal API 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HW_API-3-NO_OBJ_TYPE_LIST_ENTRY: Invalid sw_obj_type ([dec]) used with obj_type_listExplanation An internal API 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HW_API-3-NO_OBJ_TYPE_LIST_ENTRY2: Invalid sw_obj_link_type ([dec]) used with obj_type_listExplanation An internal API 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HW_API-3-RESILIENCE_NO_HANDLER: No handlers in place for [chars] sw object creation failure.Explanation An internal software error 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HW_API-3-VECTOR: Failed to set [chars] vector for [chars], [chars]Explanation An internal API 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HW_API-3-WALK_MODE_UNSUPPORTED: Walk mode '[chars]' unsupportedExplanation An internal API 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
HW_VPN-1
Error Message %HW_VPN-1-UNAVAILABLE: %s: Command 0x%x failed with status 0x%xExplanation A command was sent to the Encryption AIM, and it responded that the command had an error. The details of the failure depend upon the circumstances, but in all likelihood the Encryption AIM is faulty and should be replaced.
Recommended Action Make a note of the error message and contact a Cisco representative. The EAIM will most likely need to be replaced.
Error Message %HW_VPN-1-UNAVAILABLE: %s: EAIM responded incorrectly to hello: received 0x%x expected 0x%xExplanation A command was sent to the Encryption AIM, and it was expected to echo back the data that was sent to it. Instead of receiving the expected data, the indicated data was received instead.
Recommended Action Make a note of the error message and contact a Cisco representative. The EAIM will most likely need to be replaced.
Error Message %HW_VPN-1-UNAVAILABLE: %s: Invalid Amount of RAM for PA ID, memsize = 0x%xExplanation The Power On Self Test (POST) reported an incorrect memory size.
Recommended Action The EAIM must be replaced.
Error Message %HW_VPN-1-UNAVAILABLE: %s: Invalid command reply: expected 0x%x received 0x%sExplanation A command was sent to the Encryption AIM, and it's replay contained an unexpected reply code. The details of the failure depend upon the circumstances, but in all likelihood the Encryption AIM is faulty and should be replaced.
Recommended Action Make a note of the error message and contact a Cisco representative. The EAIM will most likely need to be replaced.
Error Message %HW_VPN-1-UNAVAILABLE: %s: Key management error, cmd=0x%x status=0x%xExplanation An unexpected error occurred during the execution of a key management command by the EAIM.
Recommended Action Make a note of the status value and contact a Cisco representative. The EAIM will most likely need to be replaced.
Error Message %HW_VPN-1-UNAVAILABLE: %s: Packet Encryption/Decryption error, status=%uExplanation An unexpected error occurred during the encryption and/or decryption of a packet.
Recommended Action This message can occur occasionally during normal operation of the system. It may occur during the transition to a new session key for a Security Association. In such cases, it may be ignored. However, if it happens frequently, or is associated with traffic disruption, then make a note of the status value and contact a Cisco representative. The EAIM will most likely need to be replaced.
Error Message %HW_VPN-1-UNAVAILABLE: %s: Power On Self Test failed, alert status = 0x%xExplanation The Power On Self Test (POST) for the EAIM failed.
Recommended Action The EAIM must be replaced.
Error Message %HW_VPN-1-UNAVAILABLE: %s: Timeout on reply to command to Encryption AIMExplanation A command has been sent to the Encryption AIM, and there has not been a reply to the command in a reasonable amount of time. The Encryption AIM is faulty and should be replaced.
Recommended Action Make a note of the error message and contact a Cisco representative. The EAIM will most likely need to be replaced.
Error Message %HW_VPN-1-UNAVAILABLE: AIM in slot %u not supported by this HW revision.Explanation The revision level of the C2600 'Elmer' PLD does not support encryption AIM. The PLD needs to be reprogrammed.
Recommended Action The C2600 'Elmer' PLD needs to be reprogrammed to a later revision. Refer to CCO Release Notes for the C2600 and Encryption AIM for an explanation of how to reprogram the PLD.
Error Message %HW_VPN-1-UNAVAILABLE: EAIM: Device Initialization failureExplanation The EAIM failed to respond properly to attempts at initialization.
Recommended Action The EAIM must be replaced.
Error Message %HW_VPN-1-UNAVAILABLE: EAIM: Initialization failed at %sExplanation The EAIM device would not reset properly. Indicative of a hardware failure.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative. The EAIM will need to be replaced.
Error Message %HW_VPN-1-UNAVAILABLE: EAIM: Invalid PCI device ID: %uExplanation The EAIM device has improperly identified itself on the router bus
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative. The EAIM will need to be replaced.
Error Message %HW_VPN-1-UNAVAILABLE: Encryption AIM busyExplanation You have entered a command which involves an Encryption AIM, but the Encryption AIM is busy executing another command.
Recommended Action Wait until the present command has completed. If the present command doesn't seem to complete in a reasonable amount of time, then the Encryption AIM is defective and must be replaced.
Error Message %HW_VPN-1-UNAVAILABLE: Encryption AIM not present in systemExplanation You have entered a command which involves an Encryption AIM, but no encryption AIM is present in the system.
Recommended Action Don't enter encryption AIM commands unless an Encryption AIM is present. If an encryption AIM is installed, then it is defective and must be replaced.
Error Message %HW_VPN-1-UNAVAILABLE: This Encryption AIM type not supported on this router platformExplanation You have installed an encryption AIM designed for one particular type of router platform (e.g. C2600) on another router platform (e.g. C3620). Different Encryption AIMs are supported by each router platform.
Recommended Action The Encryption AIM must be removed and one compatible with your router must be installed in its place.
HW_VPN-6
Error Message %HW_VPN-6-UNAVAILABLE: %s: disabledExplanation The EAIM has been disabled
Recommended Action The EAIM will need to be replaced.
Error Message %HW_VPN-6-UNAVAILABLE: %s: starting upExplanation The specified EAIM has initialized successfully.
Recommended Action This is an informational message only. It occurs in normal operation.
Error Message %HW_VPN-6-UNAVAILABLE: Cannot support more than one Encryption AIMsExplanation A second Encryption AIM was discovered present in the system. The Encryption AIM software only supports a single Encryption AIM. All other Encryption AIMs installed will be ignored.
Recommended Action Remove one of the Encryption AIMs installed in your system.
HWIF_QOS Messages
This section contains HWIF QoS messages.
Error Message %HWIF_QOS-6-EOM_FORCE_TRUSTED: EoMPLS on [chars] caused install of 'trust cos' stateExplanation If EoMPLS is configured on the interface or any of its subinterfaces, the no trust state is automatically replaced by trust cos.
Recommended Action Remove all EoMPLS configurations from the interface to restore the no trust state.
Error Message %HWIF_QOS-6-EOM_RESTORE_UNTRUSTED: The 'no trust' state is restored on EoMPLS removal from [chars]Explanation If EoMPLS is unconfigured on the interface and all its subinterfaces, the configured no trust state is restored.
Recommended Action This is an informational message only. No action is required.
Error Message %HWIF_QOS-6-EOM_TRUST_NOT_INSTALLED: 'no trust' command is not installed on [chars] in presence of EoMPLSExplanation If EoMPLS is configured on the interface or any of its subinterfaces, the no trust command is not installed.
Recommended Action Remove all EoMPLS configurations from the interface.
HYPERION Messages
This section contains Hyperion ASIC (HYPERION) messages.
HYPERION-3
Error Message %HYPERION-3-FAILURE_INTR_CFG: Failure to setup the Hyperion device interrupts.Explanation The internal ASIC on a line card could not be initialized. The device is not operational and has been disabled. The data path is not operational.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
HYPERION-4
Error Message %HYPERION-4-EARL_BUS_SYNC_ERR: Failed to sync Earl bus, Hyperion version [dec]Explanation The HYPERION ASIC in the line card failed to synchronize with the Earl bus.
Recommended Action If traffic recovers, no action is required. Otherwise, copy the message exactly as it appears on the console or in the system log. Enter the show platform hardware hyperion all command to gather data that may help identify the cause 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HYPERION-4-HYP_RESET: Hyperion Error Interrupt. Resetting ASIC.Explanation The Hyperion ASIC in the SPA or Enhanced FlexWAN module has received a fatal error. The ASIC is automatically reset, and the SPA or Enhanced FlexWAN module attempts to continue normal operation.
Recommended Action No action is required if traffic recovers. If traffic does not recover, copy the error message exactly as it appears on the console or in the system log. Enter the show platform hardware hyperion all command to gather data that may help identify the cause of the error. If you cannot determine the cause of the error from the error message text or from the show platform hardware hyperion all output, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HYPERION-4-HYP_RESET: Hyperion ASIC reset, interrupt [chars]Explanation The Hyperion ASIC in the SPA or Enhanced FlexWAN module has received a fatal error. The ASIC is automatically reset, and the SPA or Enhanced FlexWAN module attempts to continue normal operation.
Recommended Action No action is required if traffic recovers. If traffic does not recover, copy the error message exactly as it appears on the console or in the system log. Enter the show platform hardware hyperion all command to gather data that may help identify the cause of the error. If you cannot determine the cause of the error from the error message text or from the show platform hardware hyperion all output, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HYPERION-4-UNEXPECTED_VERSION: Unexpected Hyperion version.Explanation The line card is unable to recognize the version of the Hyperion ASIC.
Recommended Action No action is required if traffic passes through the line card. If traffic does not pass through the line card, check the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl to determine in which version this problem is fixed and upgrade accordingly. If traffic does not pass after the upgrade, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
HYPERION-5
Error Message %HYPERION-5-BUS_MODE_CHANGE: The System Switching Bus Mode changed to [chars] modeExplanation The system switching bus interface device mode changed switching bus modes. The mode is specified in the system message.
Recommended Action The supervisor engine instructed the module to change the mode on the switching bus. No action is required.
Error Message %HYPERION-5-BUS_SEQ_ERR: Constellation bus Sequence Error. Resetting Hyperion ASIC.Explanation The switch processor has detected a sequence error on the backplane bus. A reset sequence from the EARL has been called to recover from this error. System traffic should recover and continue normally.
Recommended Action If traffic recovers, no action is required. If traffic does not recover, copy the error message exactly as it appears on the console or in the system log. Enter the show platform hardware hyperion all command to gather data that may help identify the cause of the error. If you cannot determine the cause of the error from the error message text or from the show platform hardware hyperion all output, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HYPERION-5-HYP_INIT_FAILURE: The Hyperion ASIC initialization failedExplanation The Hyperion ASIC initialization was not successful. The Hyperion ASIC is not operational and is disabled.
Recommended Action If traffic recovers, no action is required. If traffic does not recover, copy the error message exactly as it appears on the console or in the system log. Enter the show platform hardware hyperion all command to gather data that may help identify the cause of the error. If you cannot determine the cause of the error from the error message text or from the show platform hardware hyperion all output, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HYPERION-5-HYP_INTR_INFO: [chars]Explanation This message provides more information about the interrupts from the backplane bus ASIC to the line card CPU.
Recommended Action If traffic recovers, no action is required . Otherwise, 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HYPERION-5-HYP_RESET_INFO: [chars]Explanation This message provides more information about the interrupts leading to the reset of the backplane bus ASIC.
Recommended Action If traffic recovers, no action is required . Otherwise, 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %HYPERION-5-NULL_HYP_OBJECT: The Hyperion device object pointer is set to NULLExplanation The memory location of the Hyperion ASIC device object is invalid. The Hyperion ASIC operation is disabled, and the device interrupt is now masked.
Recommended Action If traffic recovers, no action is required. If traffic does not recover, copy the error message exactly as it appears on the console or in the system log. Enter the show platform hardware hyperion all command to gather data that may help identify the cause of the error. If you cannot determine the cause of the error from the error message text or from the show platform hardware hyperion all output, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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
This section contains Inter-Card Communication (ICC) messages.
ICC-3
Error Message %ICC-3-MAST_BAD_FREE: ICC multicast memory already freedExplanation One of the ICC multicast request's memory was found to be free when response 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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-4
Error Message %ICC-4-BAD_ACCOUNTING: ICC received a bad class %dExplanation The intercard communication (ICC) process received an invalid class and therefore cannot account for the message.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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-5
Error Message %ICC-5-REQ_WATERMARK: [dec] pkts for class [chars] request [dec] are waiting to be processedExplanation The processor has received packets for the class request and the packets are waiting to be 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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-6
Error Message %ICC-6-INFO: [chars] [hex] [hex] [hex]Explanation This message provides ICC subsystem generic information or error information.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %ICC-6-MCAST_TIMEOUT: ICC multicast request timed outExplanation One of the ICC multicast request timed out without response.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
I82543-1
Error Message %I82543-1-UNAVAILABLE: %s - Cannot create IDB subblock due to insufficient memoryExplanation There was insufficent system memory to create the subblock.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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-1-UNAVAILABLE: %s - Could not install or use i82543 IDB subblockExplanation An internal IOS error prevented the IDB subblock from being installed or used.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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-1-UNAVAILABLE: %s, initialization failed, no buffer memoryExplanation The Ethernet port initialization failed due to insufficient memory
Recommended Action The router requires more packet memory - consider upgrade. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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-1-UNAVAILABLE: Could not init buffer poolsExplanation The driver failed to get a pool of buffers from IOS
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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-1-UNAVAILABLE: Could not initialize structureExplanation The driver failed to initialize a structure
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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-1-UNAVAILABLE: Invalid Interface Descriptor BlockExplanation The driver tried to fetch the interface's IDB and 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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-1-UNAVAILABLE: MAC Still in ResetExplanation An attempt was made to access the MAC while it was in reset
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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-1-UNAVAILABLE: Only found %d interfaces on bay %d, shutting down bayExplanation Possible hardware error resulted in too few interfaces discovered
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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-1-UNAVAILABLE: Plugin function table incomplete or missingExplanation The driver could not access the PA's specific function table
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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-1-UNAVAILABLE: Problem getting particle sizeExplanation The driver was unable to get the particle size for this interface
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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-1-UNAVAILABLE: Unknown IDBTYPE while starting i82543Explanation The IDBTYPE in the interface's instance structure is undefined for this driver
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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-1-UNAVAILABLE: Unknown media-type in subblockExplanation The media-type specified in the driver subblock is invalid
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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-1-UNAVAILABLE: Unknown or invalid chip mode (MII/TBI)Explanation The driver subblock contains an invalid or undefined chip operating mode (MII or TBI mode)
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
I82543-2
Error Message %I82543-2-UNAVAILABLE: Interface %s does not support ISLExplanation ISL is not supported on the specified interface's hardware.
Recommended Action LOG_STD_NO_ACTION
Error Message %I82543-3-UNAVAILABLE: %s, error interrupt, csr_STATUS=%#xExplanation The i82543 controller has signalled an error condition.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %I82543-3-UNAVAILABLE: %s, packet too big (%d), src %e, dst %eExplanation The interface detects a packet larger than what is defined by MTU
Recommended Action Check the other station's MTU setting LOG_STD_NO_ACTION
Error Message %I82543-3-UNAVAILABLE: Bay %u, device number %u: unknown device (%#x)Explanation Somehow the PA does not contain an Intel 82543 controller chip
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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-3-UNAVAILABLE: Interface %s has an unsupported PHYExplanation The specified interface has an unsupported PHY chip on the board
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
IBM2692-1
Error Message %IBM2692-1-UNAVAILABLE: %s %s creation failedExplanation The router or access server could not allocate memory for the descriptors.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %IBM2692-1-UNAVAILABLE: Bay %d port adapter requires Rev 2 CPUExplanation The Token Ring PCI Port Adapter driver depends on capabilities of the Revision 2 processor.
Recommended Action Upgrade the processor to Revision 2.
Error Message %IBM2692-1-UNAVAILABLE: IBM2692 (%d/%d), LL queue overflow.Explanation A packet buffer queue overflowed. This message indicates a packet was lost, probably due to traffic congestion.
Recommended Action A small number of queue overflows might not be a cause for concern. Reducing the load on the router or installing a higher-performance router should alleviate this problem.
Error Message %IBM2692-1-UNAVAILABLE: Only found %d interfaces on bay %d, shutting down bayExplanation One of the interface controller devices on the module did not initialize properly.
Recommended Action Power down, reinsert the network module, and reboot. If the message recurs, call your technical support representative for assistance.
ICE-3
Error Message %ICE-3-UNAVAILABLE: %sExplanation Error Messages
Recommended Action try debug command
ICC_ISSU_NEGO Messages
This section contains Inter-Card Communication (ICC) in-service software upgrade (ISSU) negotiation messages.
ICC_ISSU_NEGO-3
Error Message %ICC_ISSU_NEGO-3-CLIENT_EVENT_QUEUE_CREATE: Failed to create ICC nego client queue (client %d, endpoint 0x%x)Explanation The intercard communication (ICC) ISSU negotiation process failed to create a client watched queue.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %ICC_ISSU_NEGO-3-CLIENT_FREE_EVENTS_ALLOCATION: Failed to allocate ICC Nego free events (client %d, endpoint 0x%x)Explanation The ICC negotiation process failed to allocate ICC negotiation free 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %ICC_ISSU_NEGO-3-CLIENT_FREE_EVENT_ENQUEUE: Failed to enqueue event to free event queue (type %d, client %d, endpoint 0x%x)Explanation The ICC negotiation process failed to enqueue an event to the free event queue.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %ICC_ISSU_NEGO-3-CLIENT_FREE_EVENT_QUEUE_CREATE: Failed to create ICC nego client queue (client %d, endpoint 0x%x)Explanation The ICC negotiation process failed to create a client free events queue.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %ICC_ISSU_NEGO-3-CLIENT_PROCESS_CREATE: Failed to create ICC nego client process (client %d, endpoint 0x%x)Explanation The ICC negotiation process failed to create a client process.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %ICC_ISSU_NEGO-3-DROPPING_MSG: Dropping message (client %d)Explanation The ICC negotiation process dropped a client message.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %ICC_ISSU_NEGO-3-ICC_INIT_SEND: Failed to send the ICC Nego Init message (endpoint 0x%x)Explanation The ICC negotiation process failed to send the negotiation initialization message.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %ICC_ISSU_NEGO-3-INCONSISTENT_MEDMAN_DATA: Inconsistent MEDMan data (unique key %d)Explanation The ICC negotiation process Multiple Endpoint Data Manager (MEDMan) data is inconsistent.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %ICC_ISSU_NEGO-3-INTERNAL_ICC_PAK: Failed to get an ICC pak (internal message %d, size %dExplanation The ICC negotiation process failed to get an ICC packet for an internal message.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %ICC_ISSU_NEGO-3-INVALID_CLIENT: Invalid client %dExplanation The ICC negotiation client is invalid.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %ICC_ISSU_NEGO-3-INVALID_CLIENT_PID_GENERIC: Invalid client process pid, can't be the generic process (client %d, endpoint 0x%x, pid %d)Explanation An attempt was made to send a client process message to the ICC negotiation generic process.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %ICC_ISSU_NEGO-3-INVALID_DS: Invalid ICC Nego data structureExplanation The internal ICC negotiation data structure is invalid.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %ICC_ISSU_NEGO-3-INVALID_DS_CLIENT: Invalid ICC Nego data structure (client %d)Explanation The internal ICC negotiation data structure is invalid.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %ICC_ISSU_NEGO-3-INVALID_MSG: Invalid message (type %d)Explanation The ICC negotiation message is invalid.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %ICC_ISSU_NEGO-3-INVALID_PCOL_DS: Invalid ICC Nego process collector data structure (client %d, endpoint 0x%x)Explanation The ICC negotiation process collector data structure is invalid.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %ICC_ISSU_NEGO-3-INVALID_QUEUE: Invalid ICC Nego client queue (client %d)Explanation The internal ICC negotiation watched queue is invalid.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %ICC_ISSU_NEGO-3-INVALID_STATUS: Invalid client negotiation status (client %d, status %s)Explanation The ICC negotiation client negotiation status is invalid.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %ICC_ISSU_NEGO-3-MEDMAN_DS_CREATION: Failed to create the client data structure in MEDMan (client %d, endpoint 0x%x, error %s)Explanation The ICC negotiation process could not create the client data structure in the Multiple Endpoint Data Manager (MEDMan).
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %ICC_ISSU_NEGO-3-MEDMAN_REGISTRATION: Failed to register with MEDManExplanation The ICC negotiation process failed to register with the Multiple Endpoint Data Manager (MEDMan).
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %ICC_ISSU_NEGO-3-MSG_ENQUEUING: Failed to enqueue msg to the ICC Nego generic process (client %d)Explanation The ICC negotiation process failed to enqueue a process message to the ICC negotiation generic process.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %ICC_ISSU_NEGO-3-MSG_ENQUEUING_CLIENT: Failed to enqueue msg to the ICC Nego generic process (client %d, e_id 0x%x, type %d)Explanation The ICC negotiation process failed to enqueue a process message to an ICC negotiation client process.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %ICC_ISSU_NEGO-3-NEGO_CANNOT_COMPLETE: Negotiation cannot complete (endpoint 0x%x)Explanation The ICC negotiation cannot complete.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %ICC_ISSU_NEGO-3-NOTIFY_CLIENT: Failed to notify client %d (e_id 0x%x)Explanation The ICC negotiation process failed to notify a client.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %ICC_ISSU_NEGO-3-NO_FREE_EVENT: Couldn't get a free event (type %d, client %d, e_id 0x%x)Explanation The ICC negotiation process failed to get a free event for a client.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %ICC_ISSU_NEGO-3-NO_INTERNAL_CB: No callback for internal message %dExplanation No ICC negotiation callback has been defined for this internal message.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %ICC_ISSU_NEGO-3-NO_QUEUE: Couldn't get an event queue (type %d, client %d, e_id 0x%x)Explanation The ICC negotiation process failed to get an event queue for a client.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %ICC_ISSU_NEGO-3-NO_UK: Couldn't retreive the unique keyExplanation The ICC negotiation process failed to retrieve the unique key for a client endpoint pair.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %ICC_ISSU_NEGO-3-NVI_EMPTY_MSG: Received an empty NVI ICC messageExplanation The ICC negotiation process received an empty NVI ICC message.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %ICC_ISSU_NEGO-3-NVI_ICC_SEND: Failed to send the ICC Nego NVI ICC message (endpoint 0x%x)Explanation The ICC negotiation process failed to send the NVI ICC message.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %ICC_ISSU_NEGO-3-NVI_REQ_PAK: Failed to get an ICC req pak for the ICC Nego NVI messageExplanation The ICC negotiation process failed to get an ICC request packet for the NVI internal message.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %ICC_ISSU_NEGO-3-NVI_RESP_PAK: Failed to get an ICC resp pak for the ICC Nego NVI messageExplanation The ICC negotiation process failed to get an ICC response packet for the NVI internal message.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %ICC_ISSU_NEGO-3-OPEN_PORT_RELIABLE: Can't open reliable port (endpoint 0x%x, client %s - %d)Explanation The ICC negotiation process cannot open a reliable port to the endpoint for the ISSU client. The ISSU client might not be able to negotiate.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %ICC_ISSU_NEGO-3-OPEN_PORT_UNRELIABLE: Can't open unreliable port (endpoint 0x%x, client %d)Explanation The ICC negotiation process cannot open an unreliable port to the endpoint for the ISSU client. The ISSU client might not be able to negotiate.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %ICC_ISSU_NEGO-3-OUT_OF_MEMORY: System is running out of memoryExplanation There is not enough available memory in the 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %ICC_ISSU_NEGO-3-PCOL_INCONSISTENT_PID: Inconsistent ICC Nego process collector process id (client %d, endpoint 0x%x)Explanation The ICC negotiation process collector process ID is inconsistent.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %ICC_ISSU_NEGO-3-PROCESS_CREATE: Failed to create ICC nego processExplanation The ICC negotiation failed to create a process to handle the messages.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %ICC_ISSU_NEGO-3-PROCESS_KILL_INTERNAL: Internal process kill failed (pid %d, process collector pid %d)Explanation The ICC negotiation process failed to terminate an internal process due to an inconsistent process ID.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %ICC_ISSU_NEGO-3-PROC_LEVEL_MSG_GENERIC: Invalid process level message in the generic process (client %d, level %d)Explanation The level of messages for the ICC negotiation process is invalid in the generic process.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %ICC_ISSU_NEGO-3-PROC_LEVEL_MSG_INTERRUPT: Invalid process level message in the ICC interrupt (client %d, level %d)Explanation The level of messages for the ICC negotiation process is invalid in the ICC interrupt.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %ICC_ISSU_NEGO-3-SEND_UK: Failed to send unique key to process (client %d, endpoint 0x%xExplanation The ICC negotiation process failed to send the unique key to the new client process.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %ICC_ISSU_NEGO-3-TIMER_NOT_AWAKE: ICC Nego pcol timer was not awake when getting a timer eventExplanation The ICC negotiation process collector timer was not awake when receiving a timer 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %ICC_ISSU_NEGO-3-TIMER_NOT_RUNNING: ICC Nego pcol timer was not running when getting a timer eventExplanation The ICC negotiation process collector timer was not running when getting a timer 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %ICC_ISSU_NEGO-3-WATCHED_QUEUE_CREATION: Failed to create the watched queueExplanation The ICC negotiation process could not create the watched queue.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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_ISSU_TAGGING Messages
This section contains Inter-Card Communication (ICC) in-service software upgrade (ISSU) tagging messages.
ICC_ISSU_TAGGING-3
Error Message %ICC_ISSU_TAGGING-3-NOT_XFORM: Untransformed message detected (class:%d, request:%d, sender:%x)Explanation During runtime, the intercard communication (ICC) ISSU tagging process detected an untransformed ICC message. This message must be transformed or suspended to support ISSU.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
IDBINDEX_SYNC Messages
This section contains Interface Descriptor Block (IDB) index synchronizationmessages.
IDBINDEX_SYNC-3
Error Message %IDBINDEX_SYNC-3-IDBINDEX_ASSIGN: Failed to assign an index to IDB type %d, for interfaceExplanation An interface index cannot be allocated for this interface due to an internal software error. This is an unrecoverable error that results in this interface not being usable for traffic.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IDBINDEX_SYNC-3-IDBINDEX_ENTRY_MISMATCH: An interface index mismatched its active table entry:Explanation An interface index was found which did not match the active interface descriptor block (IDB) index table entry with the corresponding synchronization key. This condition is due to an internal 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IDBINDEX_SYNC-3-IDBINDEX_LINK: Driver for IDB type '%d' changed the Identity of interfaceExplanation The interface index table cannot be updated with the new identity provided for this interface due to an internal software error. The driver might not have deleted the old identity first, or the driver might have accidentally changed the identity.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IDBINDEX_SYNC-3-IDBINDEX_RETRIEVE: Cannot retrieve if-index for this interface:Explanation The interface index number was not found in the interface index table for the interface specified in the error message. This condition might have been caused by the interface index number not being properly synchronized by the primary processor 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IDBINDEX_SYNC-3-INIT_ERR: %sExplanation The interface index synchronization ISSU client has an initialization 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IDBINDEX_SYNC-3-IPC_ERR: %s: %s.Explanation The interface index synchronization interprocess communication (IPC) session has an 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IDBINDEX_SYNC-3-ISSU_ERR: %s%s, rc=%dExplanation The interface index synchronization ISSU client has an 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IDBINDEX_SYNC-3-RF_ERR: %s %d.Explanation An error occurred in the interface index synchronization of the redundancy facility (RF) client.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IDBINDEX_SYNC-3-TRANSFORM: Require IF-Index ISSU transformation function %s %sExplanation The interface index synchronization process has identified a missing ISSU transformation function. This condition may lead to misoperation.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IDBINDEX_SYNC-3-VALIDATE: Cannot validate if-index for this interface:Explanation The identity of this interface could not be validated against the stored identity within the interface descriptor block (IDB) index table. This condition probably occurred due to the identity of the IDB changing without first explicitly unlinking the previous identity.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
IDBINDEX_SYNC-4
Error Message %IDBINDEX_SYNC-4-RESERVE: Failed to lookup existing ifindex for an interface on the Standby, allocating a new ifindex from the Active (ifindex=%d, idbtype=%s)Explanation A lookup failure occurred for an interface on the standby unit. An attempt was made to resolve the issue by reserving a new interface index on the active unit. If this failure was caused by a defect in the key encoding, then traffic may stop on this interface if the system switches over.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IDBINDEX_SYNC-4-TRUNCATE: Overflow in %s when encoding interface sync key, got %d maximum is %dExplanation During the creation of a unique synchronization key to represent an interface, one of the attributes making up the key was truncated to fit in the allocated space in the key. This condition might lead to overlapping key allocations, which would cause an 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
IDBINDEX_SYNC_KEY Messages
This section contains Interface Descriptor Block (IDB) key synchronizationmessages.
IDBINDEX_SYNC_KEY-3
Error Message %IDBINDEX_SYNC_KEY-3-UNKNOWN_TYPE: Interface type is unknown and cannot be synced:Explanation An internal software error has occurred related to the interface descriptor block (IDB) key synchronization.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
IDBMAN-3
Error Message %IDBMAN-3-UNAVAILABLE: %s( %d / %d ) is not an aggregate portExplanation There is an internal error that caused an interface that is not an aggregate port to be used for aggregate port operations
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IDBMAN-3-UNAVAILABLE: %s(%d / %d) Group %d has been deleted, but is being reused.Explanation There is an internal error that caused an interface that has been deleted to be reused for a new aggregate port.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IDBMAN-3-UNAVAILABLE: %s(%d / %d) has an invalid bandwidth value of %dExplanation There is an internal error that caused an invalid bandwidth to be used for an aggregate port.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IDBMAN-3-UNAVAILABLE: %s(%d / %d) is not present in Aggport %s(%d / %d)Explanation There is an internal error that caused an invalid port to be referred to be part of an aggregate port.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IDBMAN-3-UNAVAILABLE: %s: %s(%d / %d) does match internal slot/port state %s(%d / %d)Explanation There is an internal error that caused an invalid aggregate port to be used by the 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IDBMAN-3-UNAVAILABLE: %s: Vlan %d is in use by %sExplanation Each L3 interface has a Vlan associated with it. This message indicates that the Vlan associated with the interface is being used by some other L3 Interface, which is not anticipated to happen
Recommended Action LOG_STD_NO_ACTION
Error Message %IDBMAN-3-UNAVAILABLE: %s: Vlan %d not set since it already has Vlan %dExplanation There is an internal error that caused an interface to not have its Vlan set to the requested 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IDBMAN-3-UNAVAILABLE: %s: trying to use invalid Vlan %dExplanation There is an internal error that caused an invalid Vlan to be used by the 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IDBMAN-3-UNAVAILABLE: %s: trying to use invalid port number %d ( Max %d )Explanation There is an internal error that caused an invalid port numer to be used by the 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
IDBMAN Messages
This section contains Interface Descriptor Block Manager (IDBMAN) messages.
IDBMAN-4
Error Message %IDBMAN-4-CONFIG_WRITE_FAIL: FFailed to generate configuration for interface [chars]Explanation The system failed to generate a configuration for the specified interface because of a problem with the file system. The active and standby supervisor engines will have configurations that do not match.
Recommended Action The standby supervisor engine is reloaded automatically to recover from the problem. If the standby supervisor engine does not recover, 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IDBMAN-4-IDB_LIMIT: Maxinum interface count reached the limit of [dec]([dec]+[dec]). Module is disabled.Explanation The number of interfaces has reached the maximum limit and the module has been disabled.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
IDBMAN-6
Error Message %IDBMAN-6-UNAVAILABLE: Vlan %d is mapped to %sExplanation Informational message indicating that the given Vlan is mapped to the given interface
Recommended Action LOG_STD_NO_ACTION
IDB_IDENTITY-3
Error Message %IDB_IDENTITY-3-UNAVAILABLE: Memory allocation failure for HWIDB type %dExplanation A memory allocation failure occured when trying to allocate the identity for this HWIDB. This HWIDB will not be allocated an IF Index which will prevent it from being used for forwarding data.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
IDMGR Messages
This section contains ID manager messages.
IDMGR-3
Error Message %IDMGR-3-UNAVAILABLE: %sExplanation A malloc failure occured in ID Manager.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IDMGR-3-UNAVAILABLE: %sExplanation An id_get attempted at interrupt level.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IDMGR-3-UNAVAILABLE: bad id in %s (id: 0x%llX)Explanation An ID Manager error 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IDMGR-3-UNAVAILABLE: bad new ID table sizeExplanation A bad new table request to ID Manager 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
IDPROM-3
Error Message %IDPROM-3-UNAVAILABLE: Corrupt or missing IDPROM ChecksumExplanation This message indicates the IDPROM of this unit could not be accessed or was found to be corrupt, either due to a hardware problem or manufacturing problem.
Recommended Action Report this error to your technical support representative.
IDPROM-4
Error Message %IDPROM-4-UNAVAILABLE: Corrupt or missing IDPROM Magic numberExplanation This message indicates the IDPROM of this unit could not be accessed or was found to be corrupt, either due to a hardware problem or manufacturing problem.
Recommended Action Report this error to your technical support representative.
IDS-4
Error Message %IDS-4-UNAVAILABLE: Connection to HostID:%u OrgID:%uExplanation Triggers when a connection drops and there is no previous connection.
Recommended Action This message indicates that the IDS cannot communicate with the Director. Check connectivity to the Director and check Postofficeconfiguration on both the router and the Director.
Error Message %IDS-4-UNAVAILABLE: Invalid SMTP command - from %i to %iExplanation Triggers on an invalid SMTP command in the SMTP connection. This message indicates that a suspicious violation was detetected that may be an attack to the mail server system.
Recommended Action This is unusual traffic and may warrant investigation.
Error Message %IDS-4-UNAVAILABLE: Sig:1000:Bad IP Option List - from %i to %iExplanation Triggers on receipt of an IP datagram where the list of IP options in the IP datagram header is incomplete or malformed. No known exploits purposely incorporate this option.
Recommended Action There is no legitimate use for malformed datagrams. This may be indicative of systems that are experiencing problems with their kernel or NIC cards. This is unusual traffic and warrants investigation. When non-specific network traffic of this type is encountered, the most prudent action from a security perspective is to shun or disallow it. If the source of this traffic is legitimate the user will then identify him or herself.
Error Message %IDS-4-UNAVAILABLE: Sig:1001:IP options-Record Packet Route - from %i to %iExplanation The IP options list contains one or more options that perform various network management or debugging tasks. This alarm may indicate a reconnaissance attack is in progress against your network.
Recommended Action While network troubleshooting may require the legitimate use of this feature, this is unusual traffic that warrantsinvestigation. When non-specific network traffic of this type is encountered, the most prudent action from a security perspective is to shun or disallow it. If the source of this traffic is legitimate the user will then identify him or herself.
Error Message %IDS-4-UNAVAILABLE: Sig:1002:IP options-TimeStamp - from %i to %iExplanation Triggers on receipt of an IP datagram where the IP option list for the datagram includes option 4 (Timestamp). This alarm indicates that a reconnaissance attack may be in progress against your network.
Recommended Action While network troubleshooting may require the legitimate use of this feature, this is unusual traffic that warrantsinvestigation. When non-specific network traffic of this type is encountered, the most prudent action from a security perspective is to shun or disallow it. If the source of this traffic is legitimate the user will then identify him or herself.
Error Message %IDS-4-UNAVAILABLE: Sig:1003:IP options-Provide s,c,h,tcc - from %i to %iExplanation Triggers on receipt of an IP datagram where the IP option list for the datagram includes option 2. No known exploit exists.
Recommended Action This signature will trigger if you have implemented IP security options on your network However, this is rarely, if ever, implemented . When non-specific network traffic of this type is encountered, the most prudent action from a security perspective is to shun or disallow it. If the source of this traffic is legitimate the user will then identify him or herself.
Error Message %IDS-4-UNAVAILABLE: Sig:1004:IP options-Loose Source Route - from %i to %iExplanation Triggers on receipt of an IP datagram where the IP option list for the datagram includes option 3 (Loose Source Route). This option may be misused to defeat authentication mechanisms that rely on IP addresses as their basis for trust relationships.
Recommended Action While network troubleshooting may require the legitimate use of this feature, this type of traffic is rarely if ever noted and should comprise much less than 1% of network traffic. Small amounts of source routed traffic most probably indicates that a network problem is being investigated. Large amounts of source routed traffic is more suspicious and a thorough investigation of the source and reason is indicated.
Error Message %IDS-4-UNAVAILABLE: Sig:1005:IP options-SATNET ID - from %i to %iExplanation Triggers on receipt of an IP datagram where the IP option list for the datagram includes option 8 (SATNET stream identifier). No known exploit exists.
Recommended Action This option is obsolete and should not be encountered. Whennon-specific network traffic of this type is encountered, the most prudent action from a security perspective is to shun or disallow it. If the source of this traffic is legitimate the user will then identify him or herself.
Error Message %IDS-4-UNAVAILABLE: Sig:1006:IP options-Strict Source Route - from %i to %iExplanation Triggers on receipt of an IP datagram in which the IP option list for the datagram includes option 2 (Strict Source Routing). This option may be misused to defeat authentication mechanisms that rely on IP addresses as their basis for trust relationships.
Recommended Action While network troubleshooting may require the legitimate use of thisfeature, this type of traffic is rarely if ever noted and should comprise much less than 1% of network traffic. Small amounts of source routed traffic most probably indicates that a network problem is being investigated. Large amounts of source routed traffic is more suspicious and a thorough investigation of the source and reason is indicated.
Error Message %IDS-4-UNAVAILABLE: Sig:1100:IP Fragment Attack - from %i to %iExplanation Triggers when any IP datagram is received with the 'more fragments' flag set to 1 or if there is an offset indicated in the offset field.
Recommended Action IP datagrams may be fragmented normally as theyare transported across the network. This is not uncommon, but is unusual enough that the traffic should be investigated. This is especially important if the network is protected by a packet filtering firewall.
Error Message %IDS-4-UNAVAILABLE: Sig:1101:Unknown IP Protocol - from %i to %iExplanation Triggers when an IP datagram is received with the protocol field set to 101 or greater. The use of these protocol types is highly unusual and should be investigated.
Recommended Action Locally developed protocols that may use these protocol types will trigger the signature. The use of these protocol types is highly unusual and should be investigated. When non-specific network traffic of this type is encountered, the most prudent action from a security perspective is to shun or disallow it.If the source of this traffic is legitimate the user will then identify him or herself.
Error Message %IDS-4-UNAVAILABLE: Sig:1102:Impossible IP Packet - from %i to %iExplanation This triggers when an IP packet arrives with source equal to destination address. This signature will catch the so-called Land Attack.
Recommended Action This should never occur in legitimate traffic.
Error Message %IDS-4-UNAVAILABLE: Sig:2000:ICMP Echo Reply - from %i to %iExplanation Triggers when a IP datagram is received with the ''protocol'' field of the IP header set to 1 (ICMP) and the ''type'' field in the ICMP header set to 0 (Echo Reply).
Recommended Action This is extremely common network traffic. Suspicion should beraised when a large number of these packets are found on the network. If nolegitimate reason for this traffic can be identified, prudent securitypractices would suggest that the source be shunned.
Error Message %IDS-4-UNAVAILABLE: Sig:2001:ICMP Host Unreachable - from %i to %iExplanation Triggers when an IP datagram is received with the ''protocol'' field of the IP header set to 1 (ICMP) and the ''type'' field in the ICMP header set to 3 (Host Unreachable). This is the common responseLarge numbers of this datagram type on the network are indicative of network difficulties or may be indicative of hostile actions.
Recommended Action This is the common response provided to a client when thereis no path available to the requested host. This is a very common type ofnetwork traffic. Large numbers of this datagram type on the network areindicative of network difficulties or may be indicative of hostile actions.If no network problems can be identified to account for the traffic prudentsecurity practices would suggest that the source be shunned.
Error Message %IDS-4-UNAVAILABLE: Sig:2002:ICMP Source Quench - from %i to %iExplanation Triggers when an IP datagram is received with the ''protocol'' field of the IP header set to 1 (ICMP) and the ''type'' field in the ICMP header set to 4 (Source Quench). This datagram may be used in network management to provide congestion control. Large numbers of this datagram type on the network are indicative of network difficulties or may be indicative of hostile actions.
Recommended Action This datagram may be used in network management to providecongestion control. A source quench packet will be issued when a router isbeginning to lose packets due to the transmission rate of a source. Thesource quench is a request to the source to reduce the rate of datagramtransmission. This datagram type is rarely if ever seen on networks and somesystems do not even support it. Large numbers of this datagram type on thenetwork are indicative of network difficulties or may be indicative ofhostile actions. If no network problems can be identified to account for thetraffic prudent security practices would suggest that the source be shunned.
Error Message %IDS-4-UNAVAILABLE: Sig:2003:ICMP Redirect - from %i to %iExplanation Triggers when a IP datagram is received with the ''protocol'' field of the IP header set to 1 (ICMP) and the ''type'' field in the ICMP header set to 5 (Redirect).
Recommended Action The redirect message may be issued from a router to informa host of a better route to a requested destination. The host then updatesits routing table to include this route. This method of updating routingtables is an uncommon practice today. When non-specific network traffic ofthis type is encountered, the most prudent action from a securityperspective is to shun or disallow it. If the source of this traffic islegitimate the user will then identify him or herself.
Error Message %IDS-4-UNAVAILABLE: Sig:2004:ICMP Echo Request - from %i to %iExplanation Triggers when a IP datagram is received with the ''protocol'' field of the IP header set to 1 (ICMP) and the ''type'' field in the ICMP header set to 8 (Echo Request). Commonly used to perform reconnaissance sweeps. Suspicion should be raised when a large number of these packets are found on the network.
Recommended Action The ICMP Echo Request is issued by the source to determineif the destination is ''alive''. When the destination receives the requestit will reply with an ICMP Echo Reply. This request/reply pair is mostcommonly implemented via the ''ping'' utility. Many network management toolsuse this utility or some derivative. This is extremely common networktraffic. Suspicion should be raised when a large number of these packets arefound on the network. If no legitimate reason for this traffic can beidentified, prudent security practices would suggest that the source beshunned.
Error Message %IDS-4-UNAVAILABLE: Sig:2005:ICMP Time Exceeded for a Datagram - from %i to %iExplanation Triggers when a IP datagram is received with the ''protocol'' field of the IP header set to 1 (ICMP) and the ''type'' field in the ICMP header set to 11(Time Exceeded for a Datagram). No known exploits incorporate this option.
Recommended Action ICMP Time Exceeded datagrams are issued when a router hashad to drop a datagram whose Time to Live (TTL) flag has expired. This is anormal and necessary type of network traffic. Large numbers of this datagramtype on the network are indicative of network difficulties or may beindicative of hostile actions. If no network problems can be identified toaccount for the traffic prudent security practices would suggest that thesource be shunned.
Error Message %IDS-4-UNAVAILABLE: Sig:2006:ICMP Parameter Problem on Datagram - from %i to %iExplanation Triggers when a IP datagram is received with the ''protocol'' field of the IP header set to 1 (ICMP) and the ''type'' field in the ICMP header set to 12 (Parameter Problem on Datagram). No known exploits incorporate this option.
Recommended Action ICMP Parameter Problem datagrams are issued when a routerhas had to drop a datagram because it was malformed. This is a normal andnecessary type of network traffic. Large numbers of this datagram type onthe network are indicative of network difficulties or may be indicative ofhostile actions. If no network problems can be identified to account for thetraffic prudent security practices would suggest that the source be shunned.
Error Message %IDS-4-UNAVAILABLE: Sig:2007:ICMP Timestamp Request - from %i to %iExplanation Triggers when a IP datagram is received with the ''protocol'' field of the IP header set to 1 (ICMP) and the ''type'' field in the ICMP header set to 13 (Timestamp Request). ICMP Timestamp Requests could be used to perform reconnaissance sweeps of networks. No known exploits incorporate this option.
Recommended Action The ICMP Timestamp Request/Reply pair can be used tosynchronize system clocks on the network. The requesting system issues theTimestamp Request bound for a destination, the destination system respondswith a Timestamp Reply message. This is normal network traffic, but isuncommon on most networks. Suspicion should be raised when a large number ofthese packets are found on the network. If no legitimate reason for thistraffic can be identified prudent security practices would suggest that thesource be shunned.
Error Message %IDS-4-UNAVAILABLE: Sig:2008:ICMP Timestamp Reply - from %i to %iExplanation Triggers when a IP datagram is received with the ''protocol'' field of the IP header set to 1 (ICMP) and the type field in the ICMP header set to 14 (Timestamp Reply). No known exploits incorporate this option.
Recommended Action The ICMP Timestamp Request/Reply pair can be used tosynchronize system clocks on the network. The requesting system issues theTimestamp Request bound for a destination, the destination system respondswith a Timestamp Reply message. This is normal network traffic, but isuncommon on most networks. Suspicion should be raised when a large number ofthese packets are found on the network. If no legitimate reason for thistraffic can be identified prudent security practices would suggest that thesource be shunned.
Error Message %IDS-4-UNAVAILABLE: Sig:2009:ICMP Information Request - from %i to %iExplanation Triggers when a IP datagram is received with the ''protocol'' field of the IP header set to 1 (ICMP) and the ''type'' field in the ICMP header set to 15 (Information Request).
Recommended Action This datagram type is obsolete and should not beencountered. When non-specific network traffic of this type is encountered,the most prudent action from a security perspective is to shun or disallowit. If the source of this traffic is legitimate the user will then identifyhim or herself.
Error Message %IDS-4-UNAVAILABLE: Sig:2010:ICMP Information Reply - from %i to %iExplanation Triggers when a IP datagram is received with the ''protocol'' field of the IP header set to 1 (ICMP) and the ''type'' field in the ICMP header set to 16 (ICMP Information Reply). No known exploit exists.
Recommended Action This datagram type is obsolete and should not beencountered. When non-specific network traffic of this type is encountered,the most prudent action from a security perspective is to shun or disallowit. If the source of this traffic is legitimate the user will then identifyhim or herself.
Error Message %IDS-4-UNAVAILABLE: Sig:2011:ICMP Address Mask Request - from %i to %iExplanation Triggers when a IP datagram is received with the ''protocol'' field of the IP header set to 1 (ICMP) and the ''type'' field in the ICMP header set to 17 (Address Mask Request). ICMP Address Mask Requests could be used to perform reconnaissance sweeps of networks.
Recommended Action The ICMP Address Mask Request/Reply pair can be used todetermine the subnet mask used on the network. The requesting system issuesthe Address Mask Request bound for a destination, the destination systemresponds with an Address Mask Reply message. This is normal network traffic,but is uncommon on most networks. Suspicion should be raised when a largenumber of these packets are found on the network. If no legitimate reasonfor this traffic can be identified prudent security practices would suggestthat the source be shunned.
Error Message %IDS-4-UNAVAILABLE: Sig:2012:ICMP Address Mask Reply - from %i to %iExplanation Triggers when a IP datagram is received with the ''protocol'' field of the IP header set to 1 (ICMP) and the ''type'' field in the ICMP header set to 18 (Address Mask Reply). No known exploits incorporate this option.
Recommended Action The ICMP Address Mask Request/Reply pair can be used todetermine the sublet mask used on the network. The requesting system issuesthe Address Mask Request bound for a destination, the destination systemresponds with an Address Mask Reply message. This is normal network traffic,but is uncommon on most networks. Suspicion should be raised when a largenumber of these packets are found on the network. If no legitimate reasonfor this traffic can be identified prudent security practices would suggestthat the source be shunned.
Error Message %IDS-4-UNAVAILABLE: Sig:2150:Fragmented ICMP Traffic - from %i to %iExplanation Triggers when a IP datagram is received with the protocol field of the IP header set to 1 (ICMP) and either the more fragments flag is set to 1 (ICMP) or there is an offset indicated in the offset field.
Recommended Action IP datagrams may be fragmented normally as they aretransported across the network, but ICMP is rarely fragmented. The trafficshould be investigated. If no legitimate reason for the fragmentation can befound and especially if the packets seem to be originating from a singlesource, prudent security practices would suggest that the host be shunned.
Error Message %IDS-4-UNAVAILABLE: Sig:2151:Large ICMP Traffic - from %i to %iExplanation While it is possible to receive ICMP datagrams that have a size greater than 1024 bytes, this is a highly unusual occurrence that warrants investigation.
Recommended Action While it is possible to receive ICMP datagrams that have asize greater than 1024 bytes, this is a highly unusual occurrence thatwarrants investigation. If no legitimate reason for the large packet sizecan be found and especially if the packets seem to be originating from asingle source, prudent security practices would suggest that the host beshunned.
Error Message %IDS-4-UNAVAILABLE: Sig:2154:ICMP Ping of Death Attack - from %i to %iExplanation Triggers when a IP datagram is received with the protocol field of the IP header set to 1(ICMP), the Last Fragment bit is set, and ( IP offset * 8 ) + ( IP data length) 65535 that is to say, the IP offset (which represents the starting position of this fragment in the original packet, and which is in 8 byte units) plus the rest of the packet isgreater than the maximum size for an IP packet. This indicates a denial of service attack.
Recommended Action This indicates a denial of service attack. It is likely that the sourceaddress has been spoofed making shunning ineffective
Error Message %IDS-4-UNAVAILABLE: Sig:3040:TCP - No bits set in flags - from %i to %iExplanation Triggers when a TCP packet is received with no bits set in the flags field.
Recommended Action There is no legitimate use for malformed TCP datagrams. This is unusual traffic and warrants investigation. Hacker tools will generateTCP packets with no bits set in the flags field in an attempt to eludeintrusion dection. When non-specific network traffic of thistype is encountered, the most prudent action from a security perspectiveis to shun or disallow it. If the source of this traffic is legitimatethe user will then identify him or herself.
Error Message %IDS-4-UNAVAILABLE: Sig:3041:TCP - SYN and FIN bits set - from %i to %iExplanation Triggers when a TCP packet is received with both the SYN and FIN bits set in the flags field.
Recommended Action There is no legitimate use for malformed TCP datagrams. This is unusual traffic and warrants investigation. Hacker tools will generateTCP packets with the SYN and FIN bits set in the flags field in an attempt to eludeintrusion dection. When non-specific network traffic of thistype is encountered, the most prudent action from a security perspectiveis to shun or disallow it. If the source of this traffic is legitimatethe user will then identify him or herself.
Error Message %IDS-4-UNAVAILABLE: Sig:3042:TCP - FIN bit with no ACK bit in flags - from %i to %iExplanation Triggers when a TCP packet is received with the FIN bit set but with no ACK bit set in the flags field.
Recommended Action There is no legitimate use for malformed TCP datagrams. This is unusual traffic and warrants investigation. Hacker tools will generateTCP packets with the FIN bit set but with no ACK bit set in the flags field in an attempt to elude intrusion dection. When non-specific network traffic of this type is encountered, the most prudent action from a security perspective is to shun or disallow it. If the source of this traffic is legitimate the user will then identify him or herself.
Error Message %IDS-4-UNAVAILABLE: Sig:3050:Half-Open Syn Flood - from %i to %iExplanation Triggers when the number of half-open TCP connections exceeds the high-water mark or the one minute high rate mark
Recommended Action There are no known sources that would legitimately generatethis traffic pattern. This may be indicative of some type of network problemand should be investigated. To avoid depletion of your network resources itis recommended that the source be shunned during the course of theinvestigation. If no network problems are discovered prudent securitypractices would suggest that the source be shunned permanently.
Error Message %IDS-4-UNAVAILABLE: Sig:3100:Smail Attack - from %i to %iExplanation Triggers on the very common ''smail'' attack against e-mail servers. This attack attempts to cause e-mail servers to execute programs on the attacker's behalf.
Recommended Action For security reasons users should not be allowed to executeprograms via e-mail servers. This is a very serious indication that yournetwork may be under attack and the source should be shunned immediately.
Error Message %IDS-4-UNAVAILABLE: Sig:3101:Sendmail Invalid Recipient - from %i to %iExplanation Triggers on any mail message with a ' 'pipe'' (|) symbol in the recipient field.
Recommended Action For security reasons users should not be allowed to executeprograms via e-mail servers. This is a very serious indication that yournetwork may be under attack and the source should be shunned immediately.
Error Message %IDS-4-UNAVAILABLE: Sig:3102:Sendmail Invalid Sender - from %i to %iExplanation Triggers on any mail message with a ''pipe'' (|) symbol in the ''From:'' field.
Recommended Action For security reasons users should not be allowed to executeprograms via e-mail servers. This is a very serious indication that yournetwork may be under attack and the source should be shunned immediately.
Error Message %IDS-4-UNAVAILABLE: Sig:3103:Sendmail Reconnaissance - from %i to %iExplanation Triggers when ''expn'' or ''vrfy'' commands are issued to the SMTP port.
Recommended Action These commands are commonly used to verify that a user mailaccount exists on the server or to expand an alias to determine who theactual recipients of a message may be. Users that use the EXPN and VRFYfunctions for legitimate purposes will trigger this signature. Theinformation that can be obtained is useful, but not dangerous on its own.Monitoring of future traffic for patterns of misuse is recommended.
Error Message %IDS-4-UNAVAILABLE: Sig:3104:Archaic Sendmail Attacks - from %i to %iExplanation Triggers when ''wiz'' or ''debug'' commands are sent to the SMTP port.
Recommended Action There is no reason for this type of traffic to be seen onmodern networks. There is little chance that there will be any adverseeffects from someone attempting these ''old'' hacks. Prudent securitypractices would suggest that the source of this attempt be shunned.
Error Message %IDS-4-UNAVAILABLE: Sig:3105:Sendmail Decode Alias - from %i to %iExplanation Triggers on any mail message with '': decode@'' in the header. The decode alias is used to uudecode files and is primarily implemented as a convenience for system administration.
Recommended Action The decode alias is used to uudecode files and is primarilyimplemented as a convenience for system administration. For securitypurposes this should not be allowed and the service should be disabled. Ifallowed, users that mail to the alias will trigger this signature. Recommendshunning of hosts that attempt to mail to this alias especially if they areoutside of your network.
Error Message %IDS-4-UNAVAILABLE: Sig:3106:Excessive Rcpt to: (SPAM) - from %i to %iExplanation Parse for RCPT TO: in header. Alarm on threshold.
Recommended Action Some mailing list software may trigger this signature.
Error Message %IDS-4-UNAVAILABLE: Sig:3107:Majordomo Execute Attack - from %i to %iExplanation A bug in the Majordomo program will allow remote users to execute arbitrary commands at the privilege level of the server.
Recommended Action Prudent security practices would suggest that the source of this attempt be shunned.
Error Message %IDS-4-UNAVAILABLE: Sig:3150:FTP Remote Command Execution - from %i to %iExplanation Triggers when someone tries to execute the FTP SITE command.
Recommended Action The FTP Site command allows a user to execute a limitednumber of commands via the FTP server on the host machine. No authenticationis required to execute the command. The commands that may be executed varyfrom system to system and on many systems the SITE command is notimplemented. Recommend that the SITE command be disabled on FTP servers ifpossible. If this signature is triggered from a source outside of yournetwork prudent security practices would suggest that the source be shunned.
Error Message %IDS-4-UNAVAILABLE: Sig:3151:FTP SYST Command Attempt - from %i to %iExplanation Triggers when someone tries to execute the FTP SYST command.
Recommended Action The FTP SYST command returns the type of operating systemthat the FTP server is running. Authentication is not required to executethis command. SYST provides information that may be used to refine attackmethods. FTP from Linux causes SYST signature to fire. Some proxies, such asthe TIS Toolkit, issue the SYST command as a matter of course. Running anFTP version with SYST disabled.
Error Message %IDS-4-UNAVAILABLE: Sig:3152:FTP CWD ~root - from %i to %iExplanation Triggers when someone tries to execute the CWD ~root command.
Recommended Action There is no known reason that this command should ever beexecuted. If this signature is triggered from a source outside of yournetwork prudent security practices would suggest that the source be shunned.
Error Message %IDS-4-UNAVAILABLE: Sig:3153:FTP Improper Address Specified - from %i to %iExplanation Triggers if a port command is issued with an address that is not the same as the requesting host.
Recommended Action Triggers if a port command is issued with an address that isnot the same as the requesting host.
Error Message %IDS-4-UNAVAILABLE: Sig:3154:FTP Improper Port Specified - from %i to %iExplanation Triggers if a port command is issued with a data port specified that is 65535.
Recommended Action Triggers if a port command is issued with a data port specifiedthat is 65535.
Error Message %IDS-4-UNAVAILABLE: Sig:4050:UDP Bomb - from %i to %iExplanation Triggers when the UDP length specified is less than the IP length specified. This malformed packet type is associated with a denial of service attempt.
Recommended Action There is no legitimate use for malformed datagrams. Thismay be indicative of systems that are experiencing problems with theirkernel or NIC cards. This is unusual traffic and warrants investigation.When non-specific network traffic of this type is encountered, the mostprudent action from a security perspective is to shun or disallow it. If thesource of this traffic is legitimate the user will then identify him orherself.
Error Message %IDS-4-UNAVAILABLE: Sig:4100:Tftp Passwd File - from %i to %iExplanation Triggered when someone tries to tftp a password file.
Recommended Action System administrators might use this service to updatesystem files. It is a high security risk if this is normal practice andshould be avoided. No other benign triggers exist for this signature. Ifafter investigation the alarm was not generated by a system administrator,prudent security practices would suggest that the source be shunned.
Error Message %IDS-4-UNAVAILABLE: Sig:6100:RPC Port Registration - from %i to %iExplanation Triggers when attempts are made to register new RPC services on a target host.
Recommended Action No benign triggers exist for this signature. Prudentsecurity practices suggest that the source of this attempt should beshunned.
Error Message %IDS-4-UNAVAILABLE: Sig:6101:RPC Port Unregistration - from %i to %iExplanation Triggers when attempts are made to unregister new RPC services on a target host.
Recommended Action No benign triggers exist for this signature. Prudentsecurity practices suggest that the source of this attempt should beshunned.
Error Message %IDS-4-UNAVAILABLE: Sig:6102:RPC Dump - from %i to %iExplanation Triggers when an RPC dump request isissued to a target host.
Recommended Action This is a common procedure performed by many systemadministrators and wary users to determine which RPC services are beingoffered. Executing this procedure is most likely due to curiosity on thepart of a novice user or a system administrator performing systemmaintenance. If upon investigation no valid user can be associated with thisevent, prudent security practices would suggest shunning the source.
Error Message %IDS-4-UNAVAILABLE: Sig:6103:Proxied RPC Request - from %i to %iExplanation Triggers when a proxied RPC request is sent to the portmapper of a target host.
Recommended Action If this procedure is allowed on your network those usersthat employ it will trigger the signature. This may be a serious attempt atgaining unauthorized access and if the source of the attempt is not withinyour network they should be shunned.
Error Message %IDS-4-UNAVAILABLE: Sig:6150:RPC ypserv Portmap Request - from %i to %iExplanation Triggers when a request is made to the portmapper for the YP server daemon (ypserv) port.
Recommended Action If this procedure is allowed on your network those usersthat employ it will trigger the signature. This may be a serious attempt atgaining unauthorized access and if the source of the attempt is not withinyour network they should be shunned.
Error Message %IDS-4-UNAVAILABLE: Sig:6151:RPC ypbind Portmap Request - from %i to %iExplanation Triggers when a request is made to the portmapper for the YP bind daemon (ypbind) port.
Recommended Action If this procedure is allowed on your network those usersthat employ it will trigger the signature. This may be a serious attempt atgaining unauthorized access and if the source of the attempt is not withinyour network they should be shunned.
Error Message %IDS-4-UNAVAILABLE: Sig:6152:RPC ypbind yppasswdd Portmap Request - from %i to %iExplanation Triggers when a request is made to the portmapper for the YP password daemon (yppasswdd) port.
Recommended Action If this procedure is allowed on your network those usersthat employ it will trigger the signature. This may be a serious attempt atgaining unauthorized access and if the source of the attempt is not withinyour network they should be shunned.
Error Message %IDS-4-UNAVAILABLE: Sig:6153:RPC ypupdated Portmap Request - from %i to %iExplanation Triggers when a request is made to the portmapper for the YP update daemon (ypupdated) port.
Recommended Action If this procedure is allowed on your network those usersthat employ it will trigger the signature. This may be a serious attempt atgaining unauthorized access and if the source of the attempt is not withinyour network they should be shunned.
Error Message %IDS-4-UNAVAILABLE: Sig:6154:RPC ypxfrd Portmap Request - from %i to %iExplanation Triggers when a request is made to the portmapper for the YP transfer daemon (ypxfrd) port.
Recommended Action If this procedure is allowed on your network those usersthat employ it will trigger the signature. This may be a serious attempt atgaining unauthorized access and if the source of the attempt is not withinyour network they should be shunned.
Error Message %IDS-4-UNAVAILABLE: Sig:6155:RPC mountd Portmap Request - from %i to %iExplanation Triggers when a request is made to the portmapper for the mount daemon (mountd) port.
Recommended Action If this procedure is allowed on your network those usersthat employ it will trigger the signature. This may be a serious attempt atgaining unauthorized access and if the source of the attempt is not withinyour network they should be shunned.
Error Message %IDS-4-UNAVAILABLE: Sig:6175: RPC rexd Portmap Request - from %i to %iExplanation Triggers when a request is made to the portmapper for the remote execution daemon (rexd) port. The remote execution daemon is the serverresponsible for remote program execution. This may be indicative of an attempt to gain unauthorized access to system resources.
Recommended Action If this procedure is allowed on your network, those userswho employ it will trigger the signature. This may be a serious attempt atgaining unauthorized access and if the source of the attempt is not withinyour network, it should be shunned.
Error Message %IDS-4-UNAVAILABLE: Sig:6180:RPC rexd Attempt - from %i to %iExplanation Triggers when a call to the rexd program is made. The remote execution daemon is the server responsible for remote program execution. Thismay be indicative of an attempt to gain unauthorized access to system resources.
Recommended Action If this service is being used legitimately, this alarm willfire. For security purposes, this service really should not be used.
Error Message %IDS-4-UNAVAILABLE: Sig:6190:statd Buffer Overflow - from %i to %iExplanation Triggers when a large statd request is sent.
Recommended Action You should not see this in legitimate traffic.
Error Message %IDS-4-UNAVAILABLE: Sig:8000:FTP Retrieve Password File - from %i to %iExplanation Triggers on string ''passwd'' issued during an FTP session.
Recommended Action System administrators might use this service to updatesystem files. It is a high security risk if this is normal practice andshould be avoided. No other benign triggers exist for this signature. Ifafter investigation the alarm was not generated by a system administrator,prudent security practices would suggest that the source be shunned.
IDTATM25-1
Error Message %IDTATM25-1-UNAVAILABLE: IDTATM25(%d/%d), Init failed at %s.Explanation The ATM25 network module hardware may be bad
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %IDTATM25-1-UNAVAILABLE: IDTATM25(%d/%d), Init failed, CSR%d=0x%04x.Explanation The ATM25 network module hardware may be bad
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %IDTATM25-1-UNAVAILABLE: Only found %d interfaces on bay %d, shutting down bayExplanation The ATM25 network module hardware may be bad
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
IDTATM25-3
Error Message %IDTATM25-3-UNAVAILABLE: Device reported %#xExplanation The ATM25 network module hardware may be bad
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %IDTATM25-3-UNAVAILABLE: IDB= %s, RX lost sync, Interface resetExplanation RX hang
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %IDTATM25-3-UNAVAILABLE: IDB= %s, TX hang, Interface resetExplanation TX hang
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %IDTATM25-3-UNAVAILABLE: Interface %s, %s not supportedExplanation The ATM25 network module hardware may be bad
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %IDTATM25-3-UNAVAILABLE: Interface %s, Failed to down vc %d (Cause: %s)Explanation The ATM25 network module hardware may be bad
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %IDTATM25-3-UNAVAILABLE: Interface %s, Failed to setup vc %d (Cause: %s)Explanation The ATM25 network module hardware may be bad
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
IDTATM25-6
Error Message %IDTATM25-6-UNAVAILABLE: ATM transmit bandwidth is limited to smallest shaped value.Explanation Any PVC configured with traffic shaping will limit the entire ATM interface to not exceed the bandwidth of any traffic shaped pvc.
IF Messages
This section contains interface messages.
IF-2
Error Message %IF-2-IDB_TABLE_INIT: Malloc failed while initializing idb tableExplanation A memory allocation failure occurred while an IDB table was being initialized.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
IF-3
Error Message %IF-3-BADMACADDRTYPE: illegal mac address type, [dec]Explanation This is an internal error that was recovered gracefully.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
IF-4
Error Message %IF-4-BACKWARD_COUNTERS: Corrected for backward [chars] counters ([int] -> [int]) on [chars]Explanation The interface specified in the message has a packet counter that 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IF-4-NOBGPROCESS: Network background process not running. [chars]Explanation A process which manages network interface background processing is not yet running, but another system process has tried to send the process a message. An interface on the router may have missed a request to bring itself up.
Recommended Action Reset the interface by entering a shutdown command followed by a no shutdown command.
IFDAMP Messages
This section contains interface dampening (IFDAMP) messages.
IFDAMP-5
Error Message %IFDAMP-5-ZERODELAY: dampening reuse timer is updated with 0 delay timeExplanation An inconsistency was detected in the dampening reuse timer wheel.
Recommended Action No action is required.
IFMGR Messages
This section contains interface manager messages.
IFMGR-3
Error Message %IFMGR-3-BADIFINDEXTABLE: The file nvram:ifIndex-table is corrupt.Explanation The file is not in the expected format.
Recommended Action If possible, delete the file. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IFMGR-3-DUP_IFINDEX: Duplicate ifIndex (%d) found for ifDescrExplanation Two interfaces have the same interface index in the interface manager assigned list. The second interface registered with the interface manager will be assigned a new index.
Recommended Action If interface index persistence is not required, then no action is required. Otherwise, reload the router with the proper interface index table and image. If the error message only appears from the standby route processor (RP), reload the standby RP.
Error Message %IFMGR-3-IFDB: IF manager interface database [chars] failure- [dec]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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IFMGR-3-IFINDEX_PERSIST_ENTRY_CORRUPT: [chars] seems to be corrupted. Trying to read [dec] sizeExplanation The ifIndex table is corrupted.
Recommended Action Delete the ifindex table.
Error Message %IFMGR-3-INVALID_PERSISTENT_DATA: Invalid persistent dataExplanation An attempt was made to write invalid persistent data.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IFMGR-3-NOIMACP: IF manager control process failed to startExplanation 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IFMGR-3-NOVECTOR: Interface manager failed to allocate IF vector. size %dExplanation The interface vector could not be allocated with the number of elements required, either initially or by a resize operation.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IFMGR-3-VECTOREXD: IF manager attempted to use interface [dec] outside vector range.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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IFMGR-3-VECTORIFSUSPECT: IF manager added interface %d which is unexpectedly large.Explanation The ifIndex allocation scheme is trying to add an ifIndex value much larger than the former greatest ifIndex value in the DB. It should assign sequential ifIndex values.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IFMGR-3-VECTORPOSUSED: IF manager attempted to add interface [dec] which was already added.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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
IFMGR-4
Error Message %IFMGR-4-NOIFINDEX: All SNMP if indices are exhaustedExplanation All SNMP MIB indexes have been exhausted. Interfaces will not be able to obtain an interface index that they can use to register with the interface MIB.
Recommended Action Attempt a system reload. If the problem persists after the system reload, 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IFMGR-4-NOSYNC: ifIndex not being synced between active and standbyExplanation When the standby module comes up, the tuple of ifIndex and ifDescr is synchronized so that interfaces get the same ifIndex when they come up. This error happens when the interface does not get the ifIndex for the given ifDescr.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IFMGR-4-STACK_RELATIONSHIP_ADD_ERROR: [chars]: Request for creating invalid stack relationship [dec], [dec]Explanation The IF MGR received the call to add invalid stack relationship. The higher and lower ifIndex are shown in the message. The module of the IF MGR from which this message is generated is also shown in the message.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IFMGR-4-VECTORIFSUSPECT: IF manager added interface [dec] which is unexpectedly large.Explanation The ifIndex allocation scheme gives out sequential ifIndex values. This message comes from the IF-MGR DB when it is trying to add an ifIndex value much larger than the former greatest ifIndex value in the DB.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
IFMGR-7
Error Message %IFMGR-7-NO_IFINDEX_FILE: Unable to open [chars] [chars]Explanation This is a informational message. This means system found no saved ifIndex information, and ifIndex is not persisted across reboots. The ifIndices will be reassigned.
Recommended Action 1. No Action, if 'snmp-server ifIndex persist' is not configured. 2. If 'snmp-server ifindex persist' is configured then copy the error message exactly as it appears, and report it to your technical support representative.
IFS Messages
This section contains Cisco IOS file system messages.
IFS-3
Error Message %IFS-3-UNAVAILABLE: '%s' file system missing required functions, not createdExplanation Some file systems require a certain set of function to be present in order to be usable. This file sustem does not support all the mandatory functionality.
Recommended Action Call your technical support representative for assistance.
Error Message %IFS-3-UNAVAILABLE: Data does not match expected internal representationExplanation A mismatch exists between the representation of data extracted from the filesystem and the expectation of its formatting. This may occur when running in a dual-RP environment, with different IOS versions running on the two RPs.
Recommended Action Ensure both RPs are running the IOS same version, if running in a dual-RP environment. If not, call your technical support representative for assistance.
Error Message %IFS-3-UNAVAILABLE: Failed to add %s, filesystem prefix existsExplanation A file system cound not be added because another file system exists with the same name.
Recommended Action Contact your technical support representative.
Error Message %IFS-3-UNAVAILABLE: Failed to add %s, maximum filesystems %dExplanation The router has reached the maximum number of file systems that can be supported at one time.
Recommended Action Contact your technical support representative.
Error Message %IFS-3-UNAVAILABLE: Failed to create %s file system, %sExplanation An internal software error occurred.
Recommended Action Call your technical support representative for assistance.
Error Message %IFS-3-UNAVAILABLE: Failed to create %s simple file system, %sExplanation An internal software error occurred.
Recommended Action Call your technical support representative for assistance.
IFS-4
Error Message %IFS-4-UNAVAILABLE: Failed to open %s, maximum open files %d)Explanation The router has reached the maximum number of files that may be open at one time.
Recommended Action Close some files and try again. If this messages recurs, contact your technical support representative.
IGMP Messages
This section contains Internet Group Management Protocol (IGMP) messages.
IGMP-3
Error Message %IGMP-3-NO_DNS_SERVER: No DNS server is configured. DNS-based SSM mapping should be disabled if no DNS server is configured.Explanation No domain name service (DNS) server is present. Processing of Internet Group Management Protocol (IGMP) packets may be delayed if the DNS lookup is done continuously.
Recommended Action Disable DNS-based source specific multicast (SSM) mapping if no DNS server is present in the network.
Error Message %IGMP-3-QUERY_INT_MISMATCH: Received a non-matching query interval %d, from querier address %iExplanation An IGMP version mismatch was detected between routers.
Recommended Action Configure both interfaces with the same IGMP version.
IGMP-6
Error Message %IGMP-6-IGMP_CHANNEL_LIMIT: IGMP limit exceeded for channel (%i, %i) on %s by host %iExplanation The allowed number of IGMP joiners reached the configured limit. New joiners cannot be allowed unless the configuration is changed.
Recommended Action Enter the global or interface ip igmp limit command to adjust the allowed number of IGMP joiners. If the exceeding of current limits was unexpected, find the IP address of the denied host in the system log.
Error Message %IGMP-6-IGMP_GROUP_LIMIT: IGMP limit exceeded for group (*, %i) on %s by host %iExplanation The allowed number of IGMP joiners has exceeded the configured limit. New joiners cannot be allowed unless the configuration is changed.
Recommended Action Enter the global or interface ip igmp limit command to adjust the allowed number of IGMP joiners. If the exceeding of current limits was unexpected, find the IP address of the denied host in the system log.
ILACC Messages
This section contains the initial mesages.
ILACC-1
Error Message %ILACC-1-UNAVAILABLE: msgtxt_initfailExplanation The hardware failed to initialize correctly.
Recommended Action Repair or replace the controller.
Error Message %ILACC-1-UNAVAILABLE: msgtxt_memoryerrorExplanation An Ethernet interface detected a hardware problem.
Recommended Action Repair or replace the controller.
ILACC-3
Error Message %ILACC-3-UNAVAILABLE: Unit %d, spurious IDON interrupt, csr%d=0x%04xExplanation An Ethernet interface generated a spurious Initialization Done interrupt.
Recommended Action Repair or replace the controller.
Error Message %ILACC-3-UNAVAILABLE: Unit %d, underflow errorExplanation The Ethernet hardware is requesting data faster than the system can supply it. This condition might indicate that the system is at the limit of its performance.
Recommended Action A small number of underflows might not be a cause for concern. You can monitor underflows with the show interface command. Reducing the load on the router or installing a higher-performance router should alleviate this problem.
Error Message %ILACC-3-UNAVAILABLE: msgtxt_badunitExplanation An internal software error occurred.
Recommended Action If this message recurs, contact your technical support representative.
Error Message %ILACC-3-UNAVAILABLE: msgtxt_ownerrorExplanation An Ethernet interface is malfunctioning, or an internal software error occurred.
Recommended Action Repair or replace the controller.
ILACC-4
Error Message %ILACC-4-UNAVAILABLE: Unit %d, babble error, csr0 = 0x%xExplanation An Ethernet interface is malfunctioning.
Recommended Action Determine whether the malfunction stems from a software or hardware error by turning off all fast switching. Error messages showing that the packet is too large for the link indicate a software error at a high level. Copy the error message exactly as it appears, and report it to your technical support representative. Receiving no error messages indicates a hardware error. Repair or replace the controller.
ILACC-5
Error Message %ILACC-5-UNAVAILABLE: Unit %d, excessive collisions. TDR=%dExplanation An Ethernet cable is broken or unterminated, or the transceiver is unplugged. The time delay reflectometer (TDR) counter is an internal ILACC counter that counts the time (in ticks of 100 ns each) from the start of a transmission to the occurrence of a collision. Because a transmission travels about 35 feet per tick, this value is useful to determine the approximate distance to a cable fault.
Recommended Action If the transceiver appears to be properly terminated, repair or replace the Ethernet interface card.
Error Message %ILACC-5-UNAVAILABLE: Unit %d, late collision errorExplanation An Ethernet transceiver is malfunctioning, the Ethernet is overloaded, or the Ethernet cable is too long.
Recommended Action Repair or replace the controller.
Error Message %ILACC-5-UNAVAILABLE: Unit %d, lost carrier. Transceiver problem?Explanation An Ethernet transceiver is unplugged or faulty.
Recommended Action Repair or replace the controller.
ILPOWER Messages
This section contains inline power messages.
ILPOWER-3
Error Message %ILPOWER-3-CONTROLLER_ERR: Controller error, Controller number [dec]: [chars]Explanation An error involving the inline power controller 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %ILPOWER-3-CONTROLLER_IF_ERR: Controller interface error, [chars]: [chars]Explanation An interface error has been detected between the inline power controller and the 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %ILPOWER-3-CONTROLLER_PORT_ERR: Controller port error, Interface [chars]: [chars]Explanation A port error has been reported by the inline power controller.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
ILPOWER-5
Error Message %ILPOWER-5-AC_DISCONNECT: Interface [chars]: AC disconnectExplanation The AC power has been disconnected.
Recommended Action No action is required.
Error Message %ILPOWER-5-DC_DISCONNECT: Interface [chars]: DC disconnectExplanation The DC power has been disconnected.
Recommended Action No action is required.
Error Message %ILPOWER-5-ILPOWER_MISCONFIG: Interface [chars] is denied power as it requires more power than configured maximum wattage([dec]).Explanation The interface is denied power as it requires more power than the configured maximum wattage.
Recommended Action No action is required.
Error Message %ILPOWER-5-ILPOWER_NOPOWER_AVAIL: Interface [chars] is denied power because either the system ran out of power or module limit reached.Explanation There is not enough power left in the system to supply to the interface specified in the error message.
Recommended Action No action is required.
Error Message %ILPOWER-5-ILPOWER_POWEROVERDRAWN: Interface [chars] is shutdown as it is consuming more power ([dec]) than the configured maximum value ([dec]).Explanation The specified interface is shut down because it is consuming more power than the configured maximum value.
Recommended Action No action is required.
Error Message %ILPOWER-5-LINKDOWN_DISCONNECT: Interface [chars]: Link down disconnectExplanation A link has been disconnected.
Recommended Action No action is required.
Error Message %ILPOWER-5-POWER_GRANTED: Interface [chars]: Power grantedExplanation Power has been granted for the interface specified.
Recommended Action No action is required.
ILPOWER-7
Error Message %ILPOWER-7-DETECT: Interface [chars]: Power Device detected: [chars]Explanation A power device has been detected.
Recommended Action No action is required.
ILPOWER_RF Messages
This section contains inline power redundancy facility (RF) messages.
ILPOWER_RF-3
Error Message %ILPOWER_RF-3-CREATE_PROCESS: Inline power RF client failed to create %s processExplanation The inline power redundancy facility (RF) client could not create a process. This condition will cause bulk synchronization to fail.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
IMAGEMGR Messages
This section contains image manager messages.
IMA-1
Error Message %IMA-1-UNAVAILABLE: Command opcode %#x on channel %d on slot %d was rejected.Explanation The IMA firmware has rejected the command because of the current protocol state of the interface, or the opcode is undefined.
Recommended Action Copy the 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IMA-1-UNAVAILABLE: Delaying activation of %s until a currently active interface is shutdown.Explanation The IMA network module cannot only support up to 4 activate interfaces at one time. Once more that 4 are no shutdown, each interface will wait for an existing interface to be shutdown before becoming activated.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IMA-1-UNAVAILABLE: Download of %s to failed to at %#x on IMA Network Module in slot %d.Explanation An error occured during the download of firmware to the IMA NM.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IMA-1-UNAVAILABLE: FPGA Download on module in slot %d failed.Explanation An error occured during the download of the FPGA on the IMA NM.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IMA-1-UNAVAILABLE: Module in slot %d had a shared memory error.Explanation Memory on the NM failed power-on diagnostic check.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IMA-1-UNAVAILABLE: Network processor on module in slot %d failed to come up.Explanation An error occured during reset of the IMA NM.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IMA-1-UNAVAILABLE: Previous process %d never received mail response from slot %d.Explanation The previous requesting process was terminated before receiving a mail reply.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IMA-1-UNAVAILABLE: The IMA Network Module in slot %d is incompatible with the PCMCIA controller in the router.Explanation The PCMCIA controller is down level.
Recommended Action Copy the error message exactly as it appears, and contact your technical support representative for upgrade information.
Error Message %IMA-1-UNAVAILABLE: The Network Module in slot %d did not initialize.Explanation The Network Module has failed its initialization.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IMA-1-UNAVAILABLE: The Network Module in slot %d reports an invalid %s device id of %#x.Explanation The IMA network module hardware may be bad.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IMA-1-UNAVAILABLE: The mailbox for channel %d on IMA Network Module in slot %d is completely full. Message %d was dropped.Explanation The IMA NM mailboxes are full and cannot accept any more requests.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IMA-1-UNAVAILABLE: Timed out waiting for a response to command %#x from slot %d.Explanation The IMA NM failed to respond with the requested information. Information to be displayed by requesting exec command or SNMP manager is incomplete. This is an extremely rare event and should only happen under severe system load.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
IMA-4
Error Message %IMA-4-UNAVAILABLE: Link %d will become the common transmit clock once it is added to group %sExplanation The link configured as the common transmit clock is not a member of the group, so it cannot provide the clock. The group will use a common transmit clock that is automatically chosen from one of the other active links.
Recommended Action LOG_STD_NO_ACTION
Error Message %IMA-4-UNAVAILABLE: Link %d will initiate the test pattern procedure once its added to group %s.Explanation The link chosen to transmit the test pattern is not a member of the group, thereby preventing the transmission of the test pattern.
Recommended Action LOG_STD_NO_ACTION
Error Message %IMA-4-UNAVAILABLE: Stopping test pattern procedure on group %s.Explanation The link transmitting the test pattern has been removed from the group, thereby stopping the transmission of the test pattern.
Recommended Action LOG_STD_NO_ACTION
IMA-5
Error Message %IMA-5-UNAVAILABLE: %s is using channel %d but has no configured links.Explanation The IMA interface has been configured Up but has no link members. It cannot become active until active links are added to the group.
Recommended Action LOG_STD_NO_ACTION
Error Message %IMA-5-UNAVAILABLE: IMA Group %s now has %d active links, active link bitmap is %#x.Explanation Active Links were added or removed from the Group, changing its bandwidth.
Recommended Action LOG_STD_NO_ACTION
IMAGEMGR-6
Error Message %IMAGEMGR-6-AUTO_ADVISE_SW: [chars]Explanation A line of output from the auto-advise-software process is being displayed.
Recommended Action No action is required.
Error Message %IMAGEMGR-6-AUTO_ADVISE_SW_INITIATED: Auto-advise-software process initiated for switch number(s) [chars]Explanation Systems with incompatible software have been detected in the stack. The stack will now determine whether or not software is available to be copied to the incompatible systems, and if so, advise the user how to copy it. Otherwise, the system lets the user know that the software on the stack needs to be updated.
Recommended Action No action is required.
Error Message %IMAGEMGR-6-AUTO_COPY_SW: [chars]Explanation A line of output from the auto-copy-software process is being displayed.
Recommended Action No action is required.
Error Message %IMAGEMGR-6-AUTO_COPY_SW_INITIATED: Auto-copy-software process initiated for switch number(s) [chars]Explanation Systems with incompatible software have been detected in the stack. The stack determines whether or not software is available to be copied to the incompatible systems, and whether or not it is appropriate to copy the software automatically.
Recommended Action No action is required.
Error Message %IMAGEMGR-6-AUTO_DOWNLOAD_SW: [chars]Explanation A line of output from the automatic software download process is being displayed.
Recommended Action No action is required.
Error Message %IMAGEMGR-6-AUTO_DOWNLOAD_SW_INITIATED: Auto-download-software process initiated for switch number(s) [chars]Explanation Systems with incompatible software have been detected in the stack. The stack attempts to download software from a previously configured location, and install it to make the systems compatible.
Recommended Action No action is required.
IMAGE_SIMFS Messages
This section contains In-Memory System Image File System messages.
IMAGE_SIMFS-3
Error Message %IMAGE_SIMFS-3-NOPROCESS: Failure spawning Memory Reclaim processExplanation The creation of an Cisco IOS process to compact memory previously held by in-memory image files has failed, probably due to a software defect.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
IMAGE_VFS Messages
This section contains Image Virtual File System messages.
Error Message %IMAGE_VFS-3-UNAVAILABLE: %s image checksum mismatch.Explanation The checksum of the image in memory is different from the expected checksum
Recommended Action Check whether the image file is complete and uncorrupted
Error Message %IMAGE_VFS-3-UNAVAILABLE: Failed to locate all the Image files,on bootupExplanation The relevant image file is missing or it couldn't be extracted(due to corruption), or the router has insufficient memory to load the entire image
Recommended Action If the TAR file is part of a system image, enter the show image contents file archive-name, where archive-name is the name of the archive. Enter the show region and show version 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.
Error Message %IMAGE_VFS-3-UNAVAILABLE: Failed to open %s, which was loaded from archive %sExplanation The relevant image file is missing or it could'nt be extracted(due to corruption), or the Archive itself is missing(In case of Flash based access)
Recommended Action If the file is not in memory, check the archive file. If the file is a TAR archive file and not part of a system software image, enter the archive tar table archive-name command, where archive-name is the name of the TAR archive. If the TAR file is part of a system image, enter the show image contents file archive-name, where archive-name is the name of the archive. Enter the dir all and show version 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.
Error Message %IMAGE_VFS-3-UNAVAILABLE: Failure spawning No Cache processExplanation The creation of an IOS process to delete in-memory Image files 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IMAGE_VFS-3-UNAVAILABLE: archive verification failed for file %s & archive %s.Explanation The archive in the local device is different from the version whose image file has been loaded into memory. This can happen if the archive was deleted from the local device &/or replaced by another file of the same name
Recommended Action Check whether the archive file is complete and uncorrupted.Also check if the size of the archive & the last modification time (if available) is what you expect it to be. Enter the dir all and show version commands.
INBAND Messages
This section contains inband management messages.
INBAND-3
Error Message %INBAND-3-BAD_PAK: Possibly un-encapsulated packet passed to Mistral: int [chars] type [int] stat [hex] flags [hex] size [dec] offset [dec] requeue_token [int] r1 [int] r2 [int] total detected [int]Explanation There is a badly encapsulated packet from the process level.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %INBAND-3-INVALID_SEND: Invalid send operation (packet on [chars])Explanation An internal error caused illegal call to device driver: normal operation continues.
Recommended Action 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. Issue 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/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.
Error Message %INBAND-3-NO_BUFFER_POOLS: Initialization of private buffer pools failedExplanation Private buffer pools were not created for etsec ibc.
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. Issue 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/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.
Error Message %INBAND-3-TOOBIG: An attempt made to send giant packet on [chars] ([dec] bytes from [hex], max allowed [dec])Explanation An attempt was made to send an oversized packet.
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. Issue 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/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.
INBAND-6
Error Message %INBAND-6-UNAVAILABLE: Bad idb for vector %s: %s vlan %d total %dExplanation Bad idb returned from get_l3_swidb
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
INBAND_or_EOBC-3
Error Message %INBAND_or_EOBC-3-UNAVAILABLE: Invalid send operation (packet on %s)Explanation Internal error caused illegal call to device driver:normal operation continues
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
INDXOBJ-3
Error Message %INDXOBJ-3-UNAVAILABLE: index object routine %s called from interrupt contextExplanation inappropriate index object routine called from interrupt routine.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
INTERFACE_API Messages
This section contains binary API for the interface descriptor block messages.
INTERFACE_API-1
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.Explanation No more hardware IDB numbers can be issued. The maximum allowed number has been reached for this platform.
Recommended Action In addition to the following, copy the information from the show idb command output. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %INTERFACE_API-1-NOMORESWIDBNUMBERS: No more software IDB numbers can be issued. The maximum allowed numbers, [dec], has been reached for this platform.Explanation No more software IDB numbers can be issued. The maximum allowed number has been reached for this platform.
Recommended Action In addition to the following, copy the information from the show idb command output. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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-3
Error Message %INTERFACE_API-3-CANNOTGETMTU: Error [dec] received while getting MTU: [chars]. Using default [int]Explanation A software error has occurred while attempting to retrieve the MTU value from the interface.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %INTERFACE_API-3-IFNUMTOIDBERROR: Error occurred while using the ifnum to idb table for interface [chars], if number [dec], during [chars]Explanation A software error has occurred. An operation on the interface number to the IDB mapping table could not be performed successfully.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %INTERFACE_API-3-INVALIDSUBBLOCKPARAMETERS: Invalid subblock parameters for [chars] were supplied.Explanation An internal software error 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %INTERFACE_API-3-NOADDSUBBLOCK: The [chars] subblock named [chars] was not added to [chars]Explanation A software error has occurred. IDB subblocks could not be added.
Recommended Action Copy the 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %INTERFACE_API-3-SUBNUMDBERR: subnum [hex] error in [chars]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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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-4
Error Message %INTERFACE_API-4-UNAVAILABLE: %s may not be referencing the correct swidbExplanation An internal software error 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %INTERFACE_API-4-UNAVAILABLE: A error occurred while using the Index Table utility for %s.Explanation A software error has occurred; this message is displayed when an Index table feature could not be used successfully.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %INTERFACE_API-4-UNAVAILABLE: Function %s detected an invalid %s pointer of %08lX, ignoringExplanation A software error has occurred, this message is displayed when an invalid pointer is 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %INTERFACE_API-4-UNAVAILABLE: pak-if_input is not initializedExplanation An internal software error 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %INTERFACE_API-4-UNAVAILABLE: pak-if_output is not initializedExplanation An internal software error 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
INTF_SYNC-2
Error Message %INTF_SYNC-2-UNAVAILABLE: %sExplanation A software error occurred during initialization of the Interface Sync RF subsystem
Recommended Action Check for sufficient processor memory. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
INTF_SYNC-3
Error Message %INTF_SYNC-3-UNAVAILABLE: Incorrectly formatted message (0x%x, 0x%x) received by %sExplanation Inconsistent message data was received from the peer CPU, possibly due to an incompatible image version.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %INTF_SYNC-3-UNAVAILABLE: Unable to transmit message type %d from %sExplanation A transmit error occurred while sending msg to other CPU, due to msg translation
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %INTF_SYNC-3-UNAVAILABLE: Unable to transmit message type %d from %sExplanation A transmit error occurred while sending msg to other CPU, due to non-availability of buffer
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %INTF_SYNC-3-UNAVAILABLE: Unknown message type 0x%x received by %sExplanation An unknown message type was received from the peer CPU, possibly due to an incompatible image version.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
INTF_SYNC-5
Error Message %INTF_SYNC-5-UNAVAILABLE: Msgtype %s sent by %s unsupported by peer.Explanation Peer responded that it didn't recognize a message sent by this CPU, possibly due to a different image version.
Recommended Action May require a software upgrade on the Standby CPU. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
INTR_MGR Messages
This section contains interrupt manager messages.
Error Message %INTR_MGR-3-BURST: [chars] [chars] [[dec]]Explanation A burst of hardware interrupts of the specified type has occurred.
Recommended Action The message text on the console or in the system log provides more information on the specific cause of the error. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %INTR_MGR-3-INTR: [chars] [chars]Explanation The specified interrupt event has been detected.
Recommended Action The message text on the console or in the system log provides more information on the specific cause of the error. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %INTR_MGR-3-MAXBURST: [chars] [chars] [[dec]]Explanation The specified hardware interrupt has exceeded the maximum allowed number of bursts.
Recommended Action The message text on the console or in the system log provides more information on the specific cause of the error. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
IOCARD-3
Error Message %IOCARD-3-UNAVAILABLE: %s in slot%d is not supported on %s chassisExplanation The software identified and disabled the FE on the I/O card
Recommended Action No action required.
Error Message %IOCARD-3-UNAVAILABLE: IO card discovered in non-zero slot %dExplanation An IO card was detected in a non-zero slot.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
IOS_LICENSE-2
Error Message %IOS_LICENSE-2-UNAVAILABLE: No memory available for %sExplanation The Ios licensing 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. To display total memory usage for a router enter show memory summary at the privileged command line prompt. To display buffer usage enter show buffers at the prompt.
Error Message %IOS_LICENSE-2-UNAVAILABLE: No valid license avaiable to run any featureExplanation The Ios licensing subsystem could not get a valid license to run any feature on the box, please purchase a license.
Recommended Action Purchase a valid license to run the features you requier on the box. You should contact the cisco portal or a TAC engineer to get a license. You can do a show license at the privileged command line prompt to get the list of availabe feature in the box
IOS_LICENSE-3
Error Message %IOS_LICENSE-3-UNAVAILABLE: %sExplanation The ios licensing subsystem failed to create a process/watched boolean etc to watch request from the remote show subsys license commands
Recommended Action please capture the error msg and forward it to the appropriate licensing component
Error Message %IOS_LICENSE-3-UNAVAILABLE: %s failedExplanation The rttys calls in the Ios licensing subsystem failed for some reason, please capture the error msg and forward it to the appropriate licensing component
Recommended Action please capture the error msg and forward it to the appropriate licensing component
Error Message %IOS_LICENSE-3-UNAVAILABLE: %s failed with an error = %sExplanation The ipc calls in the Ios licensing subsystem failed for some reason, please capture the error msg and forward it to the appropriate licensing component
Recommended Action please capture the error msg and forward it to the appropriate licensing component
Error Message %IOS_LICENSE-3-UNAVAILABLE: an unknown message type was received, dropping it, msg_type = %dExplanation Ios licensing subsystem received a msg type which it does not recognizes or support
Recommended Action please capture the error msg and forward it to the appropriate licensing component.
IOS_LICENSE_IMAGE_APPLICATION-3
Error Message %IOS_LICENSE_IMAGE_APPLICATION-3-UNAVAILABLE: %sExplanation The ios image licensing subsystem received an event for an unknown version of a feature
Recommended Action please capture the error msg and forward it to the appropriate licensing component
Error Message %IOS_LICENSE_IMAGE_APPLICATION-3-UNAVAILABLE: %sExplanation The ios image licensing subsystem received an event which it does not understand or recognizes
Recommended Action please capture the error msg and forward it to the appropriate licensing component
Error Message %IOS_LICENSE_IMAGE_APPLICATION-3-UNAVAILABLE: %sExplanation The ios licensing subsystem failed to create a process/watched boolean etc to watch request from the remote show subsys license commands
Recommended Action please capture the error msg and forward it to the appropriate licensing component
IOS_LICENSE_IMAGE_APPLICATION-6
Error Message %IOS_LICENSE_IMAGE_APPLICATION-6-UNAVAILABLE: %s %s.Explanation There is no valid license available on the box and we are running on a default feature
Recommended Action please purchase a license to activate required features
Error Message %IOS_LICENSE_IMAGE_APPLICATION-6-UNAVAILABLE: EULA must be accepted for license level = %sExplanation This is an informational message to inform user that the user needs to reissue the command from an interactive terminal
Recommended Action This is an informational message, no action is required
Error Message %IOS_LICENSE_IMAGE_APPLICATION-6-UNAVAILABLE: Module name = %s Next reboot level = %s and License = %sExplanation This is an informational message to display the change in the next reboot license level
Recommended Action This is an informational message, no action is required
Error Message %IOS_LICENSE_IMAGE_APPLICATION-6-UNAVAILABLE: Please issue 'license boot' config command to make extension license (%s) available for use.Explanation This is an informational message to info user that to make extension license available to support image level, licensing image level needs to be configured
Recommended Action This is an informational message, no action is required
IP Messages
This section contains Internet Protocol (IP) messages.
IP-3
Error Message %IP-3-LOOPPAK: Looping packet detected and dropped src=[IP_address], dst=[IP_address],hl=[int], tl=[int], prot=[int], port=[int], dport=[int] in=[chars], nexthop=[IP_address], out=[chars] options=[chars]Explanation A looping packet was detected. A common cause is a misconfiguration of an IP helper address. The helper address should be the same address as that of the server of the intended service. Putting the address of the router in the helper address causes a routing loop to be created.
Recommended Action To resolve this issue, analyze the source and destination address of the looped packets. Verify that the configuration of IP helper addresses in the switch correctly point to the right device (for example the DHCP server, the DNS server, or WINS server).
Error Message %IP-3-MAXIRDP: Attempt to send IRDP to proxies exceeding configurable limit: [dec], interface: [chars], secondary = [dec], proxy = [dec]Explanation The sum of configured secondary addresses and configured proxy addresses exceeds the number of total addresses that the IRDP can support in its implementation.
Recommended Action Reduce the number of either the secondary IP addresses or proxy addresses configured for the interface.
Error Message %IP-3-NOOUTINTF: Output interface not available. source address: [IP_address], destination address: [IP_address], routing type: [int]Explanation The output interface for this packet is not set.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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-4
Error Message %IP-4-UNAVAILABLE: Bad IP address and mask %i%m in class_resolve()Explanation An internal software error 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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-UNAVAILABLE: Duplicate address %i on %s, sourced by %eExplanation Another system is using your IP address.
Recommended Action Change the IP address of one of the two systems.
Error Message %IP-4-UNAVAILABLE: IP unicast reverse-path check disabled on %sExplanation The IP verify unicast reverse-path feature was disabled because CEF was disabled (either through configuration or due to 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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-UNAVAILABLE: Zero MAC address for %i in ARP cacheExplanation An entry in the ARP cache have a NULL MAC address
Recommended Action If this message recurs, call your technical support representative for assistance.
IP-5
Error Message %IP-5-UNAVAILABLE: %sExplanation Error occured in IP access checks.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %IP-5-UNAVAILABLE: %sExplanation Error occured in intialisation of TURBOACL.
Recommended Action Show process. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %IP-5-UNAVAILABLE: Attempting web install from host %iExplanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %IP-5-UNAVAILABLE: Selected IP address %iExplanation A hardware or software error 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IP-5-UNAVAILABLE: Sending DNS response to %i (request was for %i)Explanation A hardware or software error 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IP-5-UNAVAILABLE: Terminating DNS processExplanation A hardware or software error 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
IP-6
Error Message %IP-6-L2MCASTDROP: Layer 2 Multicast packet detected and dropped, src=[IP_address], dst=[IP_address]Explanation Layer 2 Multicast packet with Layer3 Unicast Destination was dropped.
Recommended Action No action is required.
Error Message %IP-6-PHYBCASTDROP: Physical broadcast packet detected and dropped, src=[IP_address], dst=[IP_address]Explanation Layer 2 Broadcast packet with Layer3 Unicast Destination was dropped.
Recommended Action No action is required.
IPA-3
Error Message %IPA-3-UNAVAILABLE: %s: invalid mailbox command: %02XExplanation A subsytem attempted to register a mailbox command that is out of range.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IPA-3-UNAVAILABLE: %s: unknown mailbox command: %02X %02X %02X %02XExplanation The channel port adapter sent a mailbox command that the driver did not expect. This may occur if there is a version mismatch between the system image and the microcode.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IPA-3-UNAVAILABLE: Port IO %s process terminating.Explanation Unexpected termination of a port io process.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IPA-3-UNAVAILABLE: bay [%s] mailbox response timed out after (%u + %u) usecs, mbx=%08XExplanation A mailbox command sent from driver to the channel port adapter never completed within the expected time limit. As a result of this error, the channel port adapter driver will reset the port adapter and reload microcode to it.
Recommended Action The reset and reload rectified the problem. If that did not occur, then try the microcode reload operation again. If the error still occurs, record the output from the following commands:
–
show tech
–
–
–
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IPA-3-UNAVAILABLE: bay [%u] failed to establish %s connection (%04X)Explanation An attempt to establish the console or debugger connection with the channel port adapter 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
IPACCESS Messages
This section contains IP security messages.
IPACCESS-2
Error Message %IPACCESS-2-UNAVAILABLE: Alloc fail for acl-config buffer. Disabling distributed mode on lcExplanation Unable to malloc a buffer to send access-list configuration down to linecards.
Recommended Action Enter a show chunks command and report the output, along with this error message, to your technical support representative.
Error Message %IPACCESS-2-UNAVAILABLE: Incorrect length acl ipc xdr of type=%s len=%d receivedExplanation Received an acl message of the wrong size for that type
Recommended Action Report this error message, to your tech support representative.
Error Message %IPACCESS-2-UNAVAILABLE: Invalid request to allocate chunk of size %dExplanation We only allow acl chunks of max size IPACCESS_LARGE_CHUNK_SZ
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
IPACCESS-4
Error Message %IPACCESS-4-INVALIDACL: Invalid ACL field: [chars] is [dec]Explanation An internal software error 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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
This section contains InterProcessor Communication (IPC) messages.
IPC-2
Error Message %IPC-2-UNAVAILABLE: %s: Cannot send IPC message from 0x%x to 0x%x: info 0x%xExplanation An error occurred when sending IPC message
Recommended Action Show tech-support ipc. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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-2-UNAVAILABLE: Bad refcount in %s, ptr=%x, count=%dExplanation A reference count is used to track the usage of IPC messages.A function increments the count when it begins to use a message and decrements it when it finishes. When the count becomes zero, the data structure is freed. This message indicates that when the count was accessed, it was found to be zero or negative.
Recommended Action Show tech-support ipc. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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-2-UNAVAILABLE: Boolean NULL in IPC message: %x.Explanation A watched boolean that was allocated while sending the message is found to be NULL, when an ACK arrived.
Recommended Action Show tech-support ipc. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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-2-UNAVAILABLE: IPC port pre-closure overflow : 0x%x : 0x%xExplanation An application attempts to close an ipc port when there are messages pending in retransmit queue and ipc defer table overflows.
Recommended Action Show ipc ports open. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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-2-UNAVAILABLE: IPC test: %sExplanation The IPC test routines.
Recommended Action IPC test only - no action required.
Error Message %IPC-2-UNAVAILABLE: Invalid IPC Zone 0x%x.Explanation Some operation is attempted on a zone ID not known to IPC
Recommended Action Show tech-support ipc. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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-2-UNAVAILABLE: Invalid operation at interrupt level: %s %xExplanation Debug Message. An IPC application has attempted an IPC action which has been prohibited from being performed at the interrupt level.
Recommended Action Show ipc ports. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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-2-UNAVAILABLE: Lock done a deleted element 0x%xExplanation An internal inconsistency was found in some IPC data structures.
Recommended Action Show tech-support ipc. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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-2-UNAVAILABLE: Message for %x.%x has no receive queue or dispatch routineExplanation The IPC user failed to provide any means of handling the received message.
Recommended Action Show ipc ports. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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-2-UNAVAILABLE: No handler for ACK with data for port %x.Explanation The IPC receiver appended data to an ACK. But at the sender, there is no corresponding ACK handler.
Recommended Action Show tech-support ipc. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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-2-UNAVAILABLE: No memory available for %sExplanation 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. To display total memory usage for a router enter show memory summary at the privileged command line prompt. To display buffer usage enter show buffers at the prompt. To display IPC usage enter show ipc queue at the prompt
Error Message %IPC-2-UNAVAILABLE: Unlock done on already unlocked element 0x%xExplanation An internal inconsistency was found in some IPC data structures.
Recommended Action Show tech-support ipc. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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-3
Error Message %IPC-3-INVALID_PORT_INFO: Invalid port_info in the retry queue message - SRC_PORT = [hex], DEST_PORT = [hex], MSG_TYPE = [hex]Explanation The IPC protocol subsystem detected that the port information is inconsistent. The port information is probably already freed by the application.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech ipc command from the master and the slave, to gather data that may help identify the cause 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IPC-3-ISSU_API_ERR: [chars] failed with error code [dec]Explanation An ISSU API could not perform an operation for the IPC layer. The message text includes the error code from ISSU library.
Recommended Action Enter the show issu client command. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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-ISSU_ERROR: [chars] failed with error code [dec] for seat [hex]Explanation An ISSU API could not perform an operation for the IPC layer. The message text includes the error code from ISSU library.
Recommended Action Enter the show issu fsm command. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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-4
Error Message %IPC-4-MSGMAXTIMEOUT: Invalid maximum timeout value [dec] seconds; Period - [dec]; Retries - [dec]Explanation The maximum message timeout for an IPC message exceeds 2 minutes.
Recommended Action Enter the show version command. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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-4-NOPORT: Port Not Found. [hex] --> [hex], Index:[hex], Seq: [dec], flags: [hex], size: [dec]Explanation IPC received a message which 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 to gather data that may help identify the cause 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IPC-4-UNAVAILABLE: Failed for message size %dExplanation System unable to allocate IPC message of required size.
Recommended Action If this error message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative with the gathered information. To display total memory usage for a router enter show memory summary at the privileged command line prompt. To display buffer usage enter show buffers at the prompt. To display IPC usage enter show ipc queue at the prompt
Error Message %IPC-4-UNAVAILABLE: Invalid maximum timeout value %d seconds; Period - %d; Retries - %dExplanation The maximum message timeout for an IPC message exceeds 2 minutes
Recommended Action Capture 'sh version' and contact TAC
Error Message %IPC-4-UNAVAILABLE: Port Not Found. %x -- %x, Index:%x, Seq: %d, flags: %x, size: %dExplanation IPC Received a message which is destined for a port that cannot be found by IPC
Recommended Action Capture 'sh ipc status', 'sh ipc ports' and 'deb ipc errors' outputs and contact TAC
IPC-5
Error Message %IPC-5-UNAVAILABLE: %d messages pending in %s for the port %s(%x.%x) seat %xExplanation Several IPC messages are pending to be processed. If the number increases, it may result in the IPC header cache or buffers being exhausted.
Recommended Action Show tech-support ipc. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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-UNAVAILABLE: %s %s=0x%x %s=0x%xExplanation IPC failed to register the control port
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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-UNAVAILABLE: %s %s=0x%x, %s 0x%xExplanation IPC module could not find an IPC entity that is expected to be existing always
Recommended Action Show tech-support ipc. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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-UNAVAILABLE: %sExplanation IPC API is called with invalid argument.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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-UNAVAILABLE: %sExplanation IPC message returned is Null
Recommended Action Show tech-support ipc. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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-UNAVAILABLE: %s Dest Port 0x%x Session 0x%x Source 0x%xExplanation While processing an incoming message, IPC encountered invalid data in its internal data structures.
Recommended Action Show tech-support ipc. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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-UNAVAILABLE: %s: Flow control callback function is not provided by IPC Client %sExplanation An IPC application cannot be controlled if flow need to be slowed down. This might result in drop of IPC packets
Recommended Action Show ipc ports. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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-UNAVAILABLE: Cannot hold RPC message port: %#x, index: %d, type: %#xExplanation 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 Show tech-support ipc. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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-UNAVAILABLE: Failed to intialize IPC clientExplanation An IPC application cannot be initialized because its initialization function does not appear in the IPC initialization list.
Recommended Action Show tech-support ipc. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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-UNAVAILABLE: Invalid registrationExplanation An IPC application has attempted to register NULL function in the IPC initialization list.
Recommended Action Show tech-support ipc. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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-UNAVAILABLE: Passed Null backpressure handlerExplanation IPC cannot register application's NULL function 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IPC-5-UNAVAILABLE: Q=0x%x %s %dExplanation IPC queue is full.
Error Message OUTPUT_INTERPRETER%IPC-5-UNAVAILABLE: Send message to peer for %s failed. Reason: %sExplanation Client using IPC App Port has not been able to send message
Recommended Action If the reason is 'no such port', then this may be caused because of the difference in the versions of IOS running on Active and the standby. Any other reason, please collect 'sh ipc stat' 'sh ipc rpc', 'sh ipc port' on active and standby RPs and contact tac
Error Message %IPC-5-UNAVAILABLE: VIP-%sExplanation The Cisco IOS software, running on a Versatile Interface Processor (VIP) card, generated this message. The error message has been passed to the Route Processor (RP) or Route Switch Processor (RSP) for display. This message appears only if the user has configured the service slavelog command.
Recommended Action This is actually a Cisco IOS error message from a VIP. Handle it as indicated by the text after the 'VIP-' string in the error message.
IPC-6
Error Message %IPC-6-MAXRPCTIMEOUT: Maximum RPC timeout value [dec] seconds set for port [hex]Explanation The maximum RPC timeout for an IPC message exceeds the maximum expected value of 10 minutes.
Recommended Action Enter the show techsupport ipc command. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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-6-STATEFUL: %sExplanation A stateful interprocess communication (IPC) event occurred.
Recommended Action No action is required.
IPCGRP-3
Error Message %IPCGRP-3-UNAVAILABLE: %s %sExplanation Failed to create IPC port on 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IPCGRP-3-UNAVAILABLE: %s (%u)Explanation The ID associated with an IPC card is either missing, 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IPCGRP-3-UNAVAILABLE: %s (%u)Explanation The IPC application tried to send a message that was larger than IPC could handle. The message was not transmitted.
Recommended Action Copy the 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IPCGRP-3-UNAVAILABLE: %s (%u)Explanation The slave IPC cannot register with 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IPCGRP-3-UNAVAILABLE: %sExplanation An IPC card has registered itself to the IPC master twice. The card 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IPCGRP-3-UNAVAILABLE: %sExplanation Nonblocking IPC command queue initialization 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IPCGRP-3-UNAVAILABLE: %sExplanation REXEC-On IPC command 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IPCGRP-3-UNAVAILABLE: %s: %sExplanation An IPC error was detected
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %IPCGRP-3-UNAVAILABLE: Cannot find hwidb for interface(%u/%u)Explanation Interface identifier does not exist for the interface addressed by the corresponding IPC message.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IPCGRP-3-UNAVAILABLE: Event %u from slot%u/%u: %sExplanation IPC event processing operational errors.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IPCGRP-3-UNAVAILABLE: IPC command %u (slot%u/%u): %sExplanation IPC command processing operational errors.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IPCGRP-3-UNAVAILABLE: Incorrect msg size (size=%u)Explanation Wrong size of a REXEC-On IPC command.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IPCGRP-3-UNAVAILABLE: Invalid interface(%u/%u/%u)Explanation Invalid interface addressed by the corresponding IPC message.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IPCGRP-3-UNAVAILABLE: Null %s ipc messageExplanation An empty IPC message, which is 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IPCGRP-3-UNAVAILABLE: Received empty ipc rexec cmd messageExplanation REXEC-On IPC command 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IPCGRP-3-UNAVAILABLE: System call for command %u (slot%u/%u) : %s (Cause: %s)Explanation IPC kernel system call 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
IPCOIR-3
Error Message %IPCOIR-3-UNAVAILABLE: Card in slot %d/%d has an invalid card type in IDPROMExplanation The linecard IDPROM is unprogrammed or has failed.
Recommended Action Contact customer support.
Error Message %IPCOIR-3-UNAVAILABLE: Couldn't load %s...Explanation The indicated image is inaccessible
Recommended Action Check the filename.
Error Message %IPCOIR-3-UNAVAILABLE: IPC failed (%s) %s slot %u/%uExplanation The IOS IPC protocol reported an unexpected error.
Recommended Action Make sure the indicated card is still plugged in.
Error Message %IPCOIR-3-UNAVAILABLE: Image version stamp missingExplanation The loaded image did not contain a recognizable version stamp
Recommended Action Replace the image with known-good bits, and try again.
Error Message %IPCOIR-3-UNAVAILABLE: Incorrect API message version 0x%xExplanation The linecard and IOS images are badly out of phase.
Recommended Action Contact customer support.
Error Message %IPCOIR-3-UNAVAILABLE: Incorrect message version obj 0x%x op 0x%x version 0x%xExplanation The linecard and IOS images are badly out of phase.
Recommended Action Contact customer support.
Error Message %IPCOIR-3-UNAVAILABLE: Remote server refused to load slot %u/%uError Message %IPCOIR-3-UNAVAILABLE: TFTP of %s from %s failed...Explanation The indicated image is inaccessible
Recommended Action Check file permissions, network connectivity.
Error Message %IPCOIR-3-UNAVAILABLE: Unable to create driver plugin in slot %d/%d.Explanation A valid linecard driver plugin create failed.
Recommended Action Perhaps a memory allocation failure, should not happen.
Error Message %IPCOIR-3-UNAVAILABLE: Unable to get an IPC msg buffer in %d tries: slot %u/%uExplanation The IOS IPC buffer pool was empty for a sustained period of time.
Recommended Action Install more processor SDRAM in the PRE.
Error Message %IPCOIR-3-UNAVAILABLE: Unable to initialize PRE ports.Explanation The PRE plugin init sequence failed.
Recommended Action Determine and fix cause.
Error Message %IPCOIR-3-UNAVAILABLE: Unable to preanalyze driver plugin in slot %d/%d.Explanation A valid linecard driver preanalyze failed.
Recommended Action Possibly incompatible card types
Error Message %IPCOIR-3-UNAVAILABLE: Unsupported card type (0x%x) in slot %d/%d.Explanation The linecard is not supported by this version of IOS
Recommended Action Contact customer support.
IPCOIR-4
Error Message %IPCOIR-4-UNAVAILABLE: Get IPC msg buf failed %d time(s): slot %u/%u - retry in %d secExplanation The IOS IPC buffer pool was temporarily empty.
Recommended Action Consider installing more processor SDRAM in the PRE.
IPC_RPM-3
Error Message %IPC_RPM-3-UNAVAILABLE: %s %sExplanation The ID associated with an IPC card is either missing, duplicated, or cannot be created.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %IPC_RPM-3-UNAVAILABLE: %s (%d)Explanation An invalid IPC message was received during cc command exection
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IPC_RPM-3-UNAVAILABLE: %s (%d)Explanation The IPC application tried to send a message that was larger than IPC could handle. The message was not transmitted.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %IPC_RPM-3-UNAVAILABLE: %sExplanation IPC card registered itself to the IPC master twice.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %IPC_RPM-3-UNAVAILABLE: %sExplanation The IPC ran out of memory buffers.
Recommended Action Reduce the number of applications currently running on the IPC. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %IPC_RPM-3-UNAVAILABLE: WARNING: ECC Single Bit Error CorrectionExplanation A ECC Single Bit Error was detected and corrected.
Recommended Action Use the command 'debug rpm ecc' to look at the total number of ECC errors since the system was booted. 'debug rpm ecc count' will set the number of ECC errors that will cause a Switch Over.
IPC_RSP_CBUS-3
Error Message %IPC_RSP_CBUS-3-UNAVAILABLE: %s (%d)Explanation System controller Bengal has reported an error/event
Recommended Action Read error reports. SBE are generally not fatal. Most others are
Error Message %IPC_RSP_CBUS-3-UNAVAILABLE: %s (%d)Explanation The ID associated with an IPC card is either missing, duplicated, or cannot be created.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %IPC_RSP_CBUS-3-UNAVAILABLE: %s (%d)Explanation The IPC application tried to send a message that was larger than IPC could handle. The message was not transmitted.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %IPC_RSP_CBUS-3-UNAVAILABLE: %sExplanation An IPC card has registered itself to the IPC master twice. The card malfunctioned and its IPC is not active.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %IPC_RSP_CBUS-3-UNAVAILABLE: %sExplanation The IPC ran out of memory device (MEMD) buffers.
Recommended Action Reduce the number of applications currently running on the IPC. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message %IPC_RSP_CBUS-3-UNAVAILABLE: Hardware queue for card at slot %d not foundExplanation IPC messages cannot be transmitted due to a missing hardware queue. The messages were discarded, and subsequent messages will not be transmitted to that card.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
IP_DEVICE_TRACKING Messages
This section contains switch IP host tracking HA (IP_DEVICE_TRACKING) messages.
IP_DEVICE_TRACKING-4
Error Message %IP_DEVICE_TRACKING-4-TABLE_LOCK_FAILED: Table already locked by process-id [dec]([chars])Explanation The IP device tracking table could not be updated because of another process holds a lock on the table.
Recommended Action No action is required.
Error Message %IP_DEVICE_TRACKING_HA-4-ENTRY_OUT_OF_SYNC: Host mac-address [enet] ip-address [IP_address] interface [chars]Explanation An inconsistency has been detected between the active supervisor engine IP device tracking table and the standby supervisor engine IP device tracking table for this host.
Recommended Action No action is required.
IP_DEVICE_TRACKING_HA-3
Error Message %IP_DEVICE_TRACKING_HA-3-UNAVAILABLE: %sExplanation A run-time module could not obtain the resources that are required to complete a task. The failure most likely occurred because of a software error or a lack of system memory. Additional details on the nature of the error are specified in the message text on the console or in the system log. The system state between the active and standby units might not be properly synchronized.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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_DEVICE_TRACKING_HA-3-UNAVAILABLE: Failed to send %s message to active for %s, %sExplanation The specified synchronization message, which is an internal IPC message, could not be sent to the active unit in the specified run-time module. The failure most likely occurred because of a software error. Additional details on the nature of the error are specified in the message text on the console or in the system log. The system state between the active and standby units might not be properly synchronized.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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_DEVICE_TRACKING_HA-4-UNAVAILABLE: Host mac-address %e ip-address %i interface %sExplanation An inconsistency has been detected in the IP device tracking table for this host between active and standby
Recommended Action LOG_STD_NO_ACTION
IPFAST Messages
This section contains IP fast-switching (IPFAST) messages.
IPFAST-2
Error Message %IPFAST-2-FAILOPENIPCPORT: Could not open the IPC ports. [chars]Explanation The IPFAST process could not open the IPC port to communicate to the line card or route processor.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IPFAST-2-FASTPORTCREATEERR: Attempt to create [chars] failed after [dec] retries (last error:[chars])Explanation The line card attempted to create a port to the route processor but has failed after a few retries. This condition might result in the CEF becoming disabled on 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %IPFAST-2-FASTPORTOPEN: Requested to open [chars], id [int] when already open. Attempting to re-open.Explanation The line card is attempting to open a port to the route processor when one is already open. This behavior could be transient but might result in multiple ports opened for the same purpose.
Recommended Action The router should be able to recover from this situation. If CEF problems develop for this line card, 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %IPFAST-2-FASTPORTOPENERR: Attempt to open [chars] failed after [dec] retries (last error:[chars])Explanation The line card attempted to open a port to the route processor but has failed after a few retries. This condition might result in the CEF becoming disabled on 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %IPFAST-2-FASTPORTREGISTERERR: Attempt to register [chars] failed after [dec] retries (last error:[chars])Explanation The line card attempted to register a port to the route processor but has failed after a few retries. This condition might result in the CEF becoming disabled on 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %IPFAST-2-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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IPFAST-2-MSGDROP: IPC queue limit is reached and message is dropped. queue limit = [dec] cumulative drops = [dec]Explanation The IPC raw queue limit for IP fast path has been reached.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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-3
Error Message %IPFAST-3-UNAVAILABLE: Cache update request at interrupt level: %i(%s)-%i(%s)Explanation A programming error 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IPFAST-3-UNAVAILABLE: Found existing %s specific entry %i%m..%m-%i (%s) when attempting to create %i%d..%d-%i (%s)Explanation Problems related to the IP route cache triggered this debugging message.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IPFAST-3-UNAVAILABLE: Invalid cache destination %i/%dExplanation The system attempted to add a cache entry for an invalid 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
IPFAST-4
Error Message %IPFAST-4-UNAVAILABLE: Attempt to create %s failed. Will be retried %d times (last error:%s)Explanation The Linecard is attempting to create a port to the Route processor but has failed. This could be a transient behavior and hence retries will be attempted
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IPFAST-4-UNAVAILABLE: Attempt to open %s failed. Will be retried %d times (last error:%s)Explanation The Linecard is attempting to open a port to the Route processor but has failed. This could be a transient behavior and hence retries will be attempted
Recommended Action The router should be able to recover from this situation. If CEF gets disabled for this line card 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IPFAST-4-UNAVAILABLE: Attempt to open the IPC ports failed. %s
Explanation ipfast failed an attempt to open the ipc port to communicate to the LC/RRP/SP.
Recommended Action LOG_STD_NO_ACTION
Error Message %IPFAST-4-UNAVAILABLE: Attempt to register %s failed. Will be retried %d times (last error:%s)Explanation The Linecard is attempting to register a port to the Route processor but has failed. This could be a transient behavior and hence retries will be attempted
Recommended Action The router should be able to recover from this situation. If CEF gets disabled for this line card, copy the error message exactly as it appears and report it to your Cisco technical support representative
Error Message %IPFAST-4-UNAVAILABLE: Error invalidating IP fast cache due to memory shortageExplanation Running short of memory triggered this debugging message. This could result in wrong switching decisions.
Recommended Action The router memory should be upgraded and if the problem persists copy the error exactly as it appears and report it to your technical support representative.
Error Message %IPFAST-4-UNAVAILABLE: Error trying to delete prefix entry for %i/%d (expected %#x, got %#x)Explanation Problems related to the IP route cache triggered this debugging message.
Recommended Action The router should correct for this error. If the router cannot forward packets properly or is experiencing other problems, copy the error message exactly as it appears and report it to your Cisco technical support representative.
Error Message %IPFAST-4-UNAVAILABLE: Error trying to insert prefix entry for %i/%d (expected %#x, got %#x)Explanation Problems related to the IP route cache triggered this debugging message.
Recommended Action The router should correct for this error. If the router cannot forward packets properly or is experiencing other problems, copy the error message exactly as it appears and report it to your Cisco technical support representative.
IPFAST-5
Error Message %IPFAST-5-SUCCEEDOPENIPCPORT: Attempt to open the IPC ports succeeded. [chars]Explanation The IP fast switching has succeeded in an attempt to open the IPC port to communicate with the line card or route processor.
Recommended Action No action is required.
IPFAST-6
Error Message %IPFAST-6-UNAVAILABLE: Cache invalidation request for %sExplanation The system is invalidating all cache requests for a given interface.
Recommended Action LOG_STD_NO_ACTION
Error Message %IPFAST-6-UNAVAILABLE: Packet too short from %i, datagram size %d, tl %dExplanation An IP packet which is too short was received
Recommended Action LOG_STD_NO_ACTION
IPFLOW-2
Error Message %IPFLOW-2-UNAVAILABLE: Error initializing Flow Export Template TableExplanation Initialization of the Flow export template table could not be accomplished because of a low memory condition.
Recommended Action Reduce other system activitiy to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message %IPFLOW-2-UNAVAILABLE: Error initializing Flow Export queueExplanation Initialization of the Flow export queue could not be accomplished because of a low memory condition.
Recommended Action Reduce other system activitiy to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message %IPFLOW-2-UNAVAILABLE: Error initializing Flow background processExplanation Initialization of the Flow background process could not be accomplished because of a low memory condition.
Recommended Action Reduce other system activitiy to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message %IPFLOW-2-UNAVAILABLE: Error initializing Flow feature queueExplanation Initialization of the Flow feature queue could not be accomplished because of a low memory condition.
Recommended Action Reduce other system activitiy to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message %IPFLOW-2-UNAVAILABLE: Error initializing IP flow cacheExplanation Initialization of the Flow cache could not be accomplished because of a low memory condition.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
IPFLOW-3
Error Message %IPFLOW-3-UNAVAILABLE: NULLExplanation Flow export is disabled because export destination address matches with one of the interface's IP addresses
Recommended Action IP addresses of all the interfaces must be checked to make sure none of them matches with flow export destination IP address.
IPFLOW-4
Error Message %IPFLOW-4-UNAVAILABLE: Error creating %sExplanation Version 9 export template length is zero
Recommended Action LOG_STD_DBG_ACTION
IPMCAST_LIB-3
Error Message %IPMCAST_LIB-3-UNAVAILABLE: Failed to sync multicast limit state to the standby RPExplanation An internal failure prevented sending of multicast limit information to the standby RP. Some multicast traffic disruption is possible following a route processor failover.
Recommended Action LOG_STD_NO_ACTION
IPMCAST_LIB-4
Error Message %IPMCAST_LIB-4-UNAVAILABLE: Adding %s interface '%s' denied for (%s,%s)Explanation The maximum number of times the given interface appears as incoming or outgoing for some multicast state is reached.
Recommended Action LOG_STD_NO_ACTION
IP_HOST_ISSU Messages
This section contains IP host in-service software upgrade (ISSU) messages.
IP_HOST_ISSU-2
Error Message %IP_HOST_ISSU-2-GET_BUFFER: IP Host ISSU client failed to get buffer for message. Error: %d (%s)Explanation The IP host ISSU client failed to get buffer space for building a negotiation message. A negotiation message cannot be sent to the standby device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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, show logging, and show checkpoint client commands and your pertinent troubleshooting logs.
Error Message %IP_HOST_ISSU-2-INIT: IP Host ISSU client initialization failed to %s. Error: %d (%s)Explanation The IP host ISSU client could not be initialized. This initialization failure must be addressed before an in-service software upgrade or downgrade can be performed successfully. Otherwise, a software upgrade or downgrade will result in downtime.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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_HOST_ISSU-2-SEND_NEGO_FAILED: IP Host ISSU client failed to send negotiation message. Error: %d (%s)Explanation The IP host ISSU client failed to send a session negotiation message to the peer device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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, show logging, and show checkpoint client commands and your pertinent troubleshooting logs.
Error Message %IP_HOST_ISSU-2-SESSION_NEGO: IP Host ISSU client encountered unexpected client nego_done. Error: %d (%s)Explanation The IP host ISSU client encountered a client negotiation done state that was unexpected. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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, show logging, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs.
Error Message %IP_HOST_ISSU-2-SESSION_REGISTRY: IP Host ISSU client failed to register session information. Error: %d (%s)Explanation The IP host ISSU client failed to register session information. If a problem occurs with the ISSU session registration, the standby device cannot be brought up properly.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs.
IP_HOST_ISSU-3
Error Message %IP_HOST_ISSU-3-CAP_INVALID_SIZE: IP_HOST ISSU client capability list is empty.Explanation The IP host ISSU client capability exchange list is empty, which is an invalid condition.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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, show logging, and show issu capability entries commands and your pertinent troubleshooting logs.
Error Message %IP_HOST_ISSU-3-CAP_NOT_COMPATIBLE: IP Host ISSU client capability exchange result incompatible.Explanation Based on the results of the capability exchange, the IP host ISSU client is not compatible with the peer.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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, show logging, and show issu negotiated capability commands and your pertinent troubleshooting logs.
Error Message %IP_HOST_ISSU-3-INVALID_SESSION: IP Host ISSU client does not have a valid registered session.Explanation The IP host ISSU client does not have a valid registered session.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs.
Error Message %IP_HOST_ISSU-3-MSG_NOT_OK: IP Host ISSU client 'Message Type %d' is not compatibleExplanation The IP host ISSU client received an incompatible message from the peer device. The message cannot be 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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, show logging, show issu session, show issu message group, and show issu negotiated version commands and your pertinent troubleshooting logs.
Error Message %IP_HOST_ISSU-3-MSG_SIZE: IP Host ISSU client failed to get the MTU for Message Type %d. Error: %d (%s)Explanation The IP host ISSU client was unable to calculate the MTU for the specified message. As a result, the client is not able to send the message to the standby 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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, show logging, show issu session, show issu message group, and show issu negotiated version commands and your pertinent troubleshooting logs.
Error Message %IP_HOST_ISSU-3-SESSION_UNREGISTRY: IP Host ISSU client failed to unregister session information. Error: %d (%s)Explanation The IP host ISSU client failed to unregister session information.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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, show logging, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs.
Error Message %IP_HOST_ISSU-3-TRANSFORM_FAIL: IP Host ISSU client %s transform failed for 'Message Type %d'. Error: %d (%s)Explanation The IP host ISSU client could not transform the specified message type. If the transmit transformation failed, the checkpoint message was not sent to the standby device. If the receive transformation failed, the checkpoint message was not applied on the standby device. In either case, the IP host state between the active device and the standby device is not identical.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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, show logging, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs.
IPMCAST_LIB Messages
This section contains IP multicast library messages.
IPMCAST_LIB-4
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 is usually due to 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IPMCAST_LIB-4-RPF_STATIC_ERR: No match for RIB static route [ipv6_addr]/[dec] in static table for root [ipv6_addr]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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
IPMCAST_LIB-6
Error Message %IPMCAST_LIB-6-TIMER_BUSY: Timer drift is accumulating, [dec] msecsExplanation There is large amount of processing load and the timers are accumulating delay.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
IPMOBILE-2
Error Message %IPMOBILE-2-UNAVAILABLE: IPMOBILE assertion failed: %sExplanation The software detected an inconsistency. This is considered a serious error. The router attempts to continue, but IP Mobility processing may be impaired.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
IPMOBILE-3
Error Message %IPMOBILE-3-UNAVAILABLE: Unable to open socketExplanation The requested operation could not be accomplished because of a low memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
IPM_C54X-1
Recommended Action
Error Message %IPM_C54X-1-UNAVAILABLE: DSP %d, packet(size %d) too big.Explanation A packet greater than the 256 bytes received on this interface.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IPM_C54X-1-UNAVAILABLE: No more ring descriptors available on %d slot.Explanation The DSP driver cannot queue messages up to the dma engine for transmit.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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. Reset the DSP's on this port module.
Error Message %IPM_C54X-1-UNAVAILABLE: dsp %d NOT RESPONDING.Explanation The DSP driver cannot queue messages up to the dma engine for transmit.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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. Reset the DSP's on this port module.
IPM_C54X-3
Error Message %IPM_C54X-3-UNAVAILABLE: %d SPMM Modules to support this configurationExplanation Certain configurations require more than 1 SPMM module
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IPM_C54X-3-UNAVAILABLE: %s Unable to download the Application overlay firmware. Status returned 0x%xExplanation Error initializing the DSP with the application/overlay firmware.
Recommended Action Power down, reinsert the Port Module and reboot. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IPM_C54X-3-UNAVAILABLE: Can't get dsp resourcesExplanation There are not enough DSP's for all the VIC's in the router.
Recommended Action There are more VIC's in the router than the DSP's can support. You need to upgrade your DSP module to get more DSP's. You can run 'show diag' to figure out how many DSP's the router has.
Error Message %IPM_C54X-3-UNAVAILABLE: DSP %d Sending alarm indicationExplanation The dsp is indicating and unexpected event has occurred and may not continue to process calls.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IPM_C54X-3-UNAVAILABLE: DSP %d Sending alarm indicationExplanation The dsp is indicating that it is not able to properly initialize the port(s) it services.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IPM_C54X-3-UNAVAILABLE: DSP %d Unable to download the Boot loader firmware, ret = 0x%xExplanation Error initializing the DSP with the bootloader firmware.
Recommended Action Power down, reinsert the Port Module and reboot. 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IPM_C54X-3-UNAVAILABLE: Epic TDM Switch failureExplanation The EPIC TDM switch failed to acknowledge a command
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IPM_C54X-3-UNAVAILABLE: Host is unable to transmit packets to DSP %dExplanation IOS is unable to communicate with one of the DSPs
Recommended Action Reload the IOS image running on the host and Copy the error message exactly as it appears, and .
Error Message %IPM_C54X-3-UNAVAILABLE: No buffers available for DSP buffer poolExplanation Unable to allocate buffers to DSP receive buffer pool.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IPM_C54X-3-UNAVAILABLE: Unable to allocate IDBExplanation Unable to allocate DSP Interface IDB.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
IPM_C54X-4
Error Message %IPM_C54X-4-UNAVAILABLE: Unsupported or Bad PVDM in SPMM slot %xExplanation The type of Packet Voice DSP Module present is not supported.
Recommended Action You may need to replace the unsupported Packet Voice DSP Module, or upgrade to a version of IOS that supports the PVDM you have. Please refer to documentation to find out what type of PVDMs are supported with which versions on this router.
IPM_DSPRM-3
Error Message %IPM_DSPRM-3-UNAVAILABLE: ALARM indication received from dsp %d in dsp group %dExplanation DSP has failed and indicated an alarm.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IPM_DSPRM-3-UNAVAILABLE: BAD init config response received from dsp %d in dsp group %dExplanation Initial configuration failed in dsp firmware.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IPM_DSPRM-3-UNAVAILABLE: BAD restart indication received from dsp %d in dsp group %dExplanation DSP firmware download is not successful.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IPM_DSPRM-3-UNAVAILABLE: Boot loader download failed for dsp %d in dsp group %dExplanation DSP boot loader firmware download is not successful.
Recommended Action Remove/put back DSP module or replace it
Error Message %IPM_DSPRM-3-UNAVAILABLE: Could not bring DSP %d in DSP group %d in serviceExplanation DSP did not come up after repeated attempts to downloadfirmware.
Recommended Action Check if the dsp is not bad and reload the trunk. Ifproblem persists call support
Error Message %IPM_DSPRM-3-UNAVAILABLE: Insufficient DSP resources %sExplanation DSP resources are not availabe to open a voice channel or to run a voice codec.
Recommended Action Check dsp resource usage and see if number of active calls exceede the limits.
Error Message %IPM_DSPRM-3-UNAVAILABLE: Port %d/%d not found in any DSP groupExplanation T1 port is not added to any dsp group.
Recommended Action Check if tdm-clock has been configured for this port.
IPM_NV_EEPROM-3
Error Message %IPM_NV_EEPROM-3-UNAVAILABLE: Detected invalid NVRAM size: %d bytesExplanation The detected size of NVRAM is not one of the supported sizes.The NVRAM may be bad.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IPM_NV_EEPROM-3-UNAVAILABLE: Failed to erase config due to internal errorExplanation Password protection feature failed to erase config due to 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
IPNAT Messages
This section contains IP Network Address Translation (IPNAT) messages.
IPNAT-4
Error Message %IPNAT-4-ADDR_ALLOC_FAILURE: Address allocation failed for [IP_address], pool [chars] might be exhaustedExplanation An address could not be allocated from the IP NAT pool. This condition can cause a translation failure and might result in packets being dropped. The counter for missed packets will be incremented.
Recommended Action Determine if the NAT pool has been exhausted. To reuse any existing addresses in the NAT pool for new packet flows, clear the current NAT entries using the clear ip nat translation command.
IPNAT-6
Error Message %IPNAT-6-CREATED: [chars]Explanation A NAT flow entry was created.
Recommended Action No action is required.
Error Message %IPNAT-6-DELETED: [chars]Explanation A NAT flow entry was deleted.
Recommended Action No action is required.
IPRT Messages
This section contains IP routing (IPRT) messages.
IPRT-2
Error Message %IPRT-2-UNAVAILABLE: Bad route_compress() call, sdb= %xExplanation An internal software error 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
IPRT-3
Error Message %IPRT-3-UNAVAILABLE: Bad path pointer of %x for %i, %d maxExplanation A software error 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IPRT-3-UNAVAILABLE: Community list check with bad list %dExplanation A user specified an invalid BGP community list number.
Recommended Action Check the system configuration to make sure that the community list specified falls within the valid range.
Error Message %IPRT-3-UNAVAILABLE: IP routing table creation failure - %sExplanation An internal software error occurred preventing the creation of new IP routing table.
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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-UNAVAILABLE: IP routing table limit exceeded - %s, %i%mExplanation The number of routes in the named IP routing table has reached the configured limit. No further routes will be added to the table
Recommended Action Reduce the number of routes in the table, or reconfigure the limit
Error Message %IPRT-3-UNAVAILABLE: IP routing table limit warning - %sExplanation The number of routes in the named IP routing table has reached the configured warning limit.
Recommended Action Reduce the number of routes in the table, or reconfigure the limit
Error Message %IPRT-3-UNAVAILABLE: No memory available for %sExplanation The requested operation failed because of a low memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message %IPRT-3-UNAVAILABLE: Un-installing static route %i%m from %s routing table with outgoing interface %sExplanation Restricting the access of static routes that point across vrfs
Recommended Action Remove the static routes that are pointing accross VRF interfaces
Error Message %IPRT-3-UNAVAILABLE: Unable to register IP Routing as a client of RF.Explanation This is a severe error as far as IP routing NSF is concerned
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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
IPRT-4
Error Message %IPRT-4-TRACKOBJECTNONE: Illegal tracking number 0 on static route %i%m [%d/0] via %i, table %d, client %dExplanation The tracking number 0 was assigned to a static route, but 0 is not a legal 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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-UNAVAILABLE: Redistribution prefix limit has been reached %s - %d prefixesExplanation We have reached the maximum number of redistributed prefixes
Recommended Action Check if redistribution of large number of prefixes is desired and has not been configured by mistake
Error Message %IPRT-4-UNAVAILABLE: Redistribution prefix threshold has been reached %s - %d prefixesExplanation We have reached the threshold level of number of redistributed prefixes
Recommended Action Check if redistribution of large number of prefixes is desired and has not been configured by mistake
Error Message %IPRT-4-UNAVAILABLE: can't track this type of objectExplanation Route maps only support STATE type track objects.This object is not a STATE object
Recommended Action Reconfigure the track object to make it a STATE object.
IPSECV6 Messages
This section contains encryption feature messages.
IPSECV6-4
Error Message %IPSECV6-4-UNAVAILABLE: IP protocol in packet mismatched with tunnel mode, packet from %s to %s dropped by %sExplanation We tried to send an IPv4 packet into an IPSec-IPv6 tunnel, or an IPv6 packet into an IPSec-IPv4 tunnel. The tunnel cannot handle this type of packet, and so the packet is dropped.
Recommended Action Modify the tunnel configuration, either by removing the incorrect IP address type from the tunnel interface, or by changing the tunnel mode to match the IP address type.
Error Message %IPSECV6-4-UNAVAILABLE: Rec'd packet not an IPSEC packet. (ip) dest_addr= %P, src_addr= %P, prot= %dExplanation Rec'd packet matched crypto map ACL, but is not IPSEC-encapsulated. IPSEC Peer is sending unencapsulated packets. There may simply be a policy setup error on the peer. Some might consider this a hostile event.
Recommended Action Contact the peer's administrator to compare policy settings.
Error Message %IPSECV6-4-UNAVAILABLE: decaps: rec'd IPSEC packet has invalid spi for destaddr=%P, prot=%d, spi=0x%x(%d), srcaddr=%PExplanation Rec'd IPSEC packet specifies SPI that doesn't exist in 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. Some might consider this a hostile event.
Recommended Action If the local SAs have been cleared, the peer may not know this. In this case, if a new connection is established from the local router, the two peers may reestablish successfully. Otherwise if the problem occurs for more than a brief period, either attempt to establish a new connection or contact the peer's administrator.
Error Message %IPSECV6-4-UNAVAILABLE: decapsulate: packet has bad %s length destadr=%P, prot=%d, len=%dExplanation Rec'd IPSEC packet is malformed: possibly encapsulation error? The peer is sending malformed packets. It may be due to a decryption error. Some might consider this a hostile event.
Recommended Action Contact the peer's administrator.
Error Message %IPSECV6-4-UNAVAILABLE: decapsulate: packet missing %s, destadr=%P, actual prot=%dExplanation Rec'd IPSEC packet missing an expected AH or ESP header The peer is sending packets that don't match the negotiated security policy. Some might consider this a hostile event.
Recommended Action Contact the peer's administrator.
IPV6FIB-3
Error Message %IPV6FIB-3-UNAVAILABLE: Inconsistent global state '%s' %sExplanation IPV6FIB_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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
IPV6FIB-4
Error Message %IPV6FIB-4-UNAVAILABLE: Invalid XDR length. Type/event %d/%s. XDR %d, buffer %dExplanation IPV6FIB_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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IPV6FIB-4-UNAVAILABLE: Invalid format. %sExplanation IPV6FIB_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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IPV6FIB-4-UNAVAILABLE: Missing cef idb for %s during %sExplanation IPV6FIB_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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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 %IPV6FIB-4-UNAVAILABLE: Missing cef table for tableid %lu during %s eventExplanation IPV6FIB_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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, 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.
IP_SNMP Messages
This section contains IP Simple Network Management Protocol (SNMP) messages.
IP_SNMP-4
Error Message %IP_SNMP-4-UNAVAILABLE: Oversize message from %i, datagram size %u, udp length %uExplanation An incoming SNMP packet had a length field so large that the system had to assume it was in error. This system made a correct reaction to bad external data. Since SNMP packets should originate from systems under the same administration, this may indicate that the network host used to originate the SNMP request had a problem in its networking layer. Alternatively, if the SNMP packet originated from outside the local administrative domain, it could indicate an failed attempt at security penetration and that site should be watched more closely.
Recommended Action If the origin is local, no action is required. If the origin is determined to be malicious, either contact the administrator of the originating site or install filters to prevent access by that site, as circumstances warrant.
Error Message %IP_SNMP-4-UNAVAILABLE: SNMP trap source %s has no ip addressExplanation The user entered an snmp-server trap-source command. The interface requested for use as the source address has no ipv4 address associated with it. The SNMP trap is being sent anyway, but without the source address that the user intended.
Recommended Action There are two possible solutions. Either enter a no snmp-server trap-source command to disable the request for a specific source IP address, or add an IP address to the interface referenced in the snmp-server trap-source configuration command.
Error Message %IP_SNMP-4-UNAVAILABLE: SNMP trap source %s has no ipv6 addressExplanation 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.
IPV6 Messages
This section contains IP version 6 messages.
IPV6-3
Error Message %IPV6-3-(-1): Cannot start the IPv6 process; router will not process IPv6 packets.Explanation The IPv6 process could not be started. This machine will not be able to process any IPv6 packets.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message %IPV6-3-INTERNAL: Internal error, [chars]Explanation An internal software error 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %IPV6-3-INTERNAL_PAK: Internal error ([chars]): [hex] [hex] [chars]Explanation An internal software error 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %IPV6-3-NO_UNIQUE_IDENTIFIER: Cannot determine an unique IPv6 identifier for the system.IPv6 will not be started.Explanation An unique IPv6 Identifier could not be determined for the system. Therefore the IPv6 process will not be started.This machine will not be able to process any IPv6 packets.
Recommended Action Verify that there is at least one interface in this machine that supports IEEE-style addresses.
Error Message %IPV6-3-RIB: [chars]Explanation An internal software error 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %IPV6-3-UNFRAGMENTABLE: Cannot fragment packet: unfragmentable part length [dec], MTU of [dec]Explanation An internal software error occurred. A single packet originated by this system could not be fragmented and has been dropped. Normal system operation continues.
Recommended Action This is a transient error. However, this condition indicates other errors in the software that will require further examination by your Cisco technical support representative. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
IPV6-4
Error Message %IPV6-4-DUPLICATE_OPTIMISTIC: Duplicate address %P on %sExplanation You have elected not to run duplicate address detection (DAD), but another system is using your IPv6 address.
Recommended Action Change the IPv6 address of one of the two systems.
Error Message %IPV6-4-LLA_CONFLICT: LLA conflict for static neighbor on [chars] : [chars]Explanation A neighborhood discovery (ND) message from the specified neighbor carries a link-layer address (LLA) other than the configured address.
Recommended Action Reconfigure the static neighbor with the correct link-layer address.
Error Message %IPV6-4-MAXPDB: Exceeded maximum supported IPv6 Routing Protocol instancesExplanation Configuration of a routing protocol has failed because it would exceed the maximum supported number of routing protocols.
Recommended Action Reduce the number of IPv6 routing protocol instances configured.
IPV6-6
Error Message %IPV6-6-ACCESSLOGSP: list [chars]/[dec] [chars] [chars] [chars]->, [dec] packet[chars]Explanation A packet matching the log criteria for the given access list was detected.
Recommended Action No action is required.
Error Message %IPV6-4-MULTICAST: Application does not support multicast destination address , packet dropped.Explanation An internal software error occurred. A multicast destination address was used in an local application which does not yet handle IPv6 multicast.
Recommended Action Use a unicast address in commands on the router. If the problem persists, or you feel the command should support multicast, 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/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
IPV6_ACL-6
Error Message %IPV6_ACL-6-UNAVAILABLE: list %s/%d %s %d %P %s- %P, %d packet%sExplanation A packet matching the log criteria for the given access list was detected.
Recommended Action LOG_STD_NO_ACTION
Error Message %IPV6_ACL-6-UNAVAILABLE: list %s/%d %s %s %P %s- %P (%d/%d), %d packet%sExplanation A packet matchi