HMAN through IRECAGENTSERVER

HMAN through HW_FLOWDB

HMAN

%HMAN-3-CONSOLE_SETUP_FAILED : Failed to setup console service. It should be enabled on [chars]
Explanation Setup of a console service failed.
Recommended Action Check the host manager launch parameters and correct as required.


%HMAN-3-HOSTNAME_SET_FAILED : Failed to set hostname: [chars]
Explanation The host manager received notification that the system hostname has been set. The host manager failed to pass this value to the ASR kernel.
Recommended Action Repeat the process to configure the hostname. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center via the Internet athttps://mycase.cloudapps.cisco.com/case, or contact your Cisco technical support representative and provide the representative with the gathered information.


%HMAN-2-INITIALIZATION_FAILED : Host Manager initialization failed.
Explanation Initialization of the host manager failed.
Recommended Action Review Host Manager logs taking note of the timestamp information to select specific information to review. Copy the message and other related information exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center via the Internet athttps://mycase.cloudapps.cisco.com/case, or contact your Cisco technical support representative and provide the representative with the gathered information.


HMAN_CPU

%HMAN_CPU-3-PAGE_FAULT_HIGH : CPU Usage due to Memory Pressure exceeds threshold on [chars]. Below are the top 5 memory consuming processes: [chars] (PID=[dec] RSS=[dec] MB),
Explanation When CPU usage due to Major Page Fault exceeds a pre-defined threshold for a CPU core, this error message is emitted.
Recommended Action No action is needed if system continues to perform as expected. If sytem performance deteriorate (and eventually, system reloads due to unspecified reason) around the time when this message is observed, open a case with the Technical Assistance Center via the following Internet link, or contact your Cisco technical support representative:https://mycase.cloudapps.cisco.com/case


HPI

%HPI-3-FAILED_START : channel:[chars] DSP ID:[hex], failed mode [dec] for service [dec]
Explanation Failed to start DSP services
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%HPI-3-INVALID_PAYLOAD : wrong payload size, channel:[chars] DSP ID:[hex], failed mode [dec] for service [dec]
Explanation Failed to start DSP services
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%HPI-3-CODEC_NOT_LOADED : channel:[chars] DSP ID:[hex], command failed as codec not loaded [dec]
Explanation Sending messages to DSP without a loaded codec can result with the DSP failing
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%HPI-4-INVALID_CODEC_LOAD : channel:[chars] DSP ID:[hex], invalid hpi mode [dec] for loading codec [dec]
Explanation Attempt to load codec when the DSP is in an invalid mode which can result with DSP failure
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%HPI-4-NO_CLOSE : channel:[chars] DSP ID:[hex]
Explanation Attempt to release DSP without sending close message
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%HPI-4-INVALID_ECAN_TYPE : [chars] ECAN is not available in voice-card [dec], [chars] ECAN will be used
Explanation All voice cards participated in DSPFarm must have the same echo canceller type
Recommended Action Make sure all voice cards participated in DSPFarm have the same echo canceller type configured


%HPI-3-GSMAMRNB_LICENSE_NOT_ACTIVATED : ********************************************************* GSM AMR-NB License is not yet activated. Please configure 'license feature gsmamrnb-codec-pack' and accept the EULA to activate the license. *********************************************************
Explanation Failed to start DSP services for GSM AMR-NB codec
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%HPI-6-SRTP_EVAL_LIMIT : The SRTP bandwidth and tunnels usage exceed the license limits
Explanation The SRTP bandwidth and tunnels exceed the license limits
Recommended Action No action is required.


%HPI-3-SRTP_EVAL_FREE_ERROR : Error encountered on release SRTP bandwidth and tunnels reservation
Explanation Error encountered on release SRTP bandwidth and tunnels
Recommended Action No action is required.


%HPI-3-NACK_HIGH : DSP to IOS Nack message with severity [chars] [chars] [chars]
Explanation DSP to IOS Nack message with high severity
Recommended Action Check the NACKed message's parameters for configuration errors. These messages tend to affect call flow, thus they are labeled with high severity.


%HPI-4-NACK_MED : DSP to IOS Nack message with severity [chars] [chars] [chars]
Explanation DSP to IOS Nack message with medium severity
Recommended Action Check the NACKed message's parameters for minor configuration errors.


%HPI-6-NACK_LOW : DSP to IOS Nack message with severity [chars] [chars] [chars]
Explanation DSP to IOS Nack message with low severity
Recommended Action Information only, displaying NACKed messages that are for debugging purposes.


%HPI-6-NACK : DSP to IOS Nack message [chars] [chars]
Explanation DSP to IOS Nack message with no severity in order to work with dspware without Nack severity implementation
Recommended Action Information only, displaying NACKed messages.


HSRP

%HSRP-3-NOSOCKET : Unable to open socket
Explanation 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-BADAUTH : Bad authentication from [chars], 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.


%HSRP-4-BADAUTH2 : Bad authentication from [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.


%HSRP-3-MISCONFIG : Attempt to change [chars] MAC address to [enet] when DECNET already running
Explanation An HSRP group attempted to become active on an interface that can only support a single MAC address and which is running DECnet. If standby use-bia is not configured then HSRP would normally set the interface MAC address to the HSRP virtual MAC address, but this is not allowed if DECnet is running.
Recommended Action Enable standby use-bia on the interface.


%HSRP-5-STATECHANGE : [chars] Grp [dec] state [chars] -> [chars]
Explanation The router has changed state
Recommended Action No action is required.


%HSRP-4-DUPADDR : Duplicate address [chars] 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. Enable standby use-bia so that the error message displays the interface MAC address of the sending router. This can be used to determine if the error message is caused by a misconfigured router or a network loop.


%HSRP-4-DUPVIP1 : [chars] Grp [dec] address [chars] is already assigned to [chars] group [dec]
Explanation The HSRP virtual IP address contained in the Hello message cannot be learnt 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.


%HSRP-4-DUPVIP2 : [chars] Grp [dec] address [chars] is already assigned on this interface
Explanation The HSRP virtual IP address contained in the Hello message cannot be learnt 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.


%HSRP-4-DUPVIP3 : [chars] Grp [dec] address [chars] is already assigned to, or overlaps with, an address on another interface or application
Explanation The HSRP virtual IP address contained in the Hello message cannot be learnt 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-4-BADVIP : [chars] Grp [dec] address [chars] is in the wrong subnet for this interface
Explanation The HSRP virtual IP address contained in the Hello message cannot be learnt 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.


%HSRP-4-DIFFVIP1 : [chars] Grp [dec] active routers virtual IP address [chars] is different to the locally configured address [chars]
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.


HTSP

%HTSP-3-NOEVENT : no free event structure available from [chars] for DSP message
Explanation 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.


%HTSP-3-CAPABILITYMISMATCH : voice port [chars]: call connection id [[hex] [hex] [hex] [hex]]
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.


%HTSP-3-DSPALARM : voice port [chars]: status=[hex] message=[hex] text=[chars]
Explanation 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-3-TRUNKNOTSUPPORTED : voice port [chars]: Ground Start trunking not supported
Explanation 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.


%HTSP-5-UPDOWN : Trunk port(channel) [[chars]] is [chars]
Explanation Trunk port:channel changed state.
Recommended Action No action is required.


%HTSP-3-CADENCENOTSUPPORTED : voice port [chars]: ring cadence not suitable for caller id. on_time_first=[dec] off_time_first=[dec] on_time_second=[dec] off_time_second=[dec]
Explanation Ring off period is not sufficient for caller id transmission. If caller id transmission during ring is configured make sure that the ring off duration is long enough.
Recommended Action If caller id transmission during ring is configured make sure that the ring off duration is long enough. Make sure that the cptone setting and caller-id alerting settings are correct.


%HTSP-5-VPM_BUSYOUT : voice port [chars]: [chars] busyout
Explanation voice port busyout status changed
Recommended Action use SHOW VOICE BUSYOUT to find out the reason why voice port busyout monitoring is triggered


%HTSP-5-VPM_PCM_CAPTURE : User trigger PCM capture is [chars] on voice port [chars]
Explanation User trigger PCM capture is enabled or disable on this voice port
Recommended Action This is just for information only


%HTSP-5-VPM_CABLE_STAT : voice port [chars]: cable [chars]
Explanation Cable for analog voice port is reconnected or removed
Recommended Action Check the cable connection for this analog voice port


HTTP

%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.


%HTTP-4-SERVER_CONN_RATE_EXCEED : Number of connections per minute has exceeded the maximum limit([dec]) as specified by the platform.
Explanation The message indicates that the current number of connections requested per minute has exceeded the limit specified by the platform. HTTP server will resume accepting the connections 15 seconds from the time the message is issued. This restriction is done as per the HTTP throttling functionality.
Recommended Action Reduce connection rate to the server.


%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.


%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.


%HTTP-6-SERVER_SETUP_FAILED : Server setup failed
Explanation Setup of the HTTP(S) 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.


HTTPC

%HTTPC-3-PROC_NOCREAT : Unable to create HTTP Client process.
Explanation
Recommended Action


%HTTPC-3-OUTOF_MEM : HTTP Client out of memory.
Explanation
Recommended Action


%HTTPC-3-CACHE_MEM : HTTP Client Cache Init out of memory.
Explanation
Recommended Action


%HTTPC-3-INIT_FAIL : HTTP Client Process Init failed.
Explanation
Recommended Action


%HTTPC-3-OUTOF_SYNC : HTTP Client header tables out of sync.
Explanation
Recommended Action


%HTTPC-6-CONNECT_FAILED : The connection to server [IP_address] failed
Explanation
Recommended Action


%HTTPC-3-RECEIVE_SOCK_READ_EVENT_WHILE_DISABLED : Received socket read event while read interest is disabled callID([dec]) fd([dec]) - closing socket.
Explanation The HTTP Client is receiving the socket READ event while the READ interest is being disabled. Something has gone wrong between the http client and the socket interfaced.
Recommended Action Record the error and report it to the system administrator.


%HTTPC-3-CONNECT_NULL : NULL connection structure for fd([dec]) - closing socket.
Explanation The HTTP Client is receiving the socket READ event but it fails to locate the connection structure for this file descriptor(fd). If this is seen continuously in a loop, it is an indication that something has gone wrong in the socket code. Since the socket is immediately closed after this event, the HTTP client should stop seeing READ event.
Recommended Action Record the error and traceback and report it to the system administrator.


%HTTPC-6-REQUEST_FAILED : request URI [chars] failed
Explanation
Recommended Action


%HTTPC-6-CLOSE_SRV_CONNECT : The connection to server [IP_address] appears to be hung and will be closed.
Explanation Messages are being backed up in the HTTP Client's write queue in the connection with the specified server. The connection is assumed to have gone bad and the HTTP Client is closing the connection.
Recommended Action Check with the specified server for possible connection error.


%HTTPC-3-COOKIE_MEM : HTTP Client runs out of allowable memory to store cookies.
Explanation The total memory allocated for storing cookies has run out. All cookies received from the HTTP server will be dropped. Users may no longer be able to interact with a session-based origin server until memory is freed up.
Recommended Action Users may want to try their requests at a later time or contact the system administrator to increase the maximum RAM allowed for saving HTTP cookies.


HUNTGRP

%HUNTGRP-3-INVALID_URL : Could not open the file provided in URL: <[chars]>
Explanation URL path provided can't be accessed. This usually indicates that path provided is invalid but may also be because the the path doesn't allow anonymous access to create files or open it in write mode
Recommended Action Check that the url path provided is valid


%HUNTGRP-3-WRITE_FAIL : Could not write data to the URL: <[chars]>t %%bytes written=[dec] out of [dec]
Explanation Write attempt to the url path provided was unsuccessful. This usually indicates that the file was successfully opened with write and append permissions but writing all the content from buffer or may be some of it to the file failed.
Recommended Action


HW_API

%HW_API-3-RESILIENCE_NO_HANDLER : No handlers in place for [chars] sw object creation failure.
Explanation COMMON_HW_API_INTERNAL_ERROR
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%HW_API-3-INVALID_OBJ : Invalid object [hex]
Explanation HW_API_INTERNAL_ERROR
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%HW_API-3-INVALID_TYPE : Invalid type [dec]
Explanation HW_API_INTERNAL_ERROR
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%HW_API-3-INVALID_WALK_SPEC : Invalid walk spec [hex]
Explanation HW_API_INTERNAL_ERROR
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%HW_API-3-WALK_MODE_UNSUPPORTED : Walk mode '[chars]' unsupported
Explanation HW_API_INTERNAL_ERROR
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%HW_API-3-INVALID_CONTEXT : Invalid context [hex]
Explanation HW_API_INTERNAL_ERROR
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%HW_API-3-BACKWALK_REQUEST : Backwalk request failed, [chars]
Explanation A request to walk internal data structures has failed. Depending on criticality of the data, accuracy of forwarding may impacted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%HW_API-3-BACKWALK_REQUEST_VALUE : Backwalk request failed, [chars] ([hex])
Explanation A request to walk internal data structures has failed. Depending on criticality of the data, accuracy of forwarding may impacted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%HW_API-3-VECTOR : Failed to set [chars] vector for [chars], [chars]
Explanation HW_API_INTERNAL_ERROR
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%HW_API-3-NO_OBJ_TYPE_LIST_ENTRY : Invalid sw_obj_type ([dec]) used with obj_type_list
Explanation HW_API_INTERNAL_ERROR
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%HW_API-3-NO_OBJ_TYPE_LIST_ENTRY2 : Invalid sw_obj_link_type ([dec]) used with obj_type_list
Explanation HW_API_INTERNAL_ERROR
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%HW_API-3-INIT_FAIL : HW-API init [chars] failed[chars]
Explanation HW_API_INTERNAL_ERROR
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


HW_FLOWDB

%HW_FLOWDB-3-HW_FLOWDB_OOM : FlowDB memory usage exceeded 95[int]sage. OOM condition can occur.
Explanation FlowDB running low on memory. Out-of-memory condition can occur
Recommended Action Check sw-distrib for actual utilization of FlowDB memory


HW_IDPROM_ENVMON through IFDAMP

HW_IDPROM_ENVMON

%HW_IDPROM_ENVMON-3-HW_IDPROM_FIELD_INVALID : The idprom contains an invalid environmental monitoring field.
Explanation If this error occurs then parsing of the environmental monitoring data is aborted. Environmental monitoring will be either incomplete or absent entirely.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%HW_IDPROM_ENVMON-3-HW_IDPROM_CHECKSUM_INVALID : The idprom contains an invalid checksum in a sensor entry. Expected: [hex], calculated: [hex]
Explanation If this error occurs then parsing of the environmental monitoring data is aborted. Environmental monitoring will be either incomplete or absent entirely.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%HW_IDPROM_ENVMON-2-ACT2_UDI_DATA_INVALID : The act2 udi secure area format mismatch with unsecure area
Explanation This Router may not have been manufactured by Cisco or with Cisco's authorization. This product may contain software that was copied in violation of Cisco's license terms. If your use of this product is the cause of a support issue, Cisco may deny operation of the product, support under your warranty or under a Cisco technical support program such as Smartnet. Please contact Cisco's Technical Assistance Center for more information.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%HW_IDPROM_ENVMON-3-PS_IDPROM_INVALID_PID : [chars] in slot PFU[dec] has INVALID PID [chars] and it needs to be replaced immediately
Explanation The PID read from the PEM IDPROM is not supported in this hardware configuration. It will be allowed to continue but immediate replacement is required
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


HW_PFU

%HW_PFU-3-PFU_IDPROM_READ_ERR : Could not read the PEM/FM idprom in slot P[dec].The system will run without environmental monitoring for this component
Explanation The idprom contains information required in order to properly operate the environmental monitoring subsystems. The idprom could not be read, therefore no monitoring will take place.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%HW_PFU-3-PFU_IDPROM_CORRUPT : The PEM/FM idprom could be read, but is corrupt in slot P[dec] The system will run without environmental monitoring for this component
Explanation The idprom contains information required in order to properly operate the environmental monitoring subsystems. The idprom could not be read, therefore no monitoring will take place.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%HW_PFU-3-PFU_IDPROM_INVALID_PID : The PEM/FM idprom has invalid PID in slot PFU[dec] The system will run without environmental monitoring for this component
Explanation The idprom contains PID information required in order to properly operate the environmental monitoring subsystems. The idprom PID is invalid , therefore no monitoring will take place.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


ICC

%ICC-2-NOMEM : No memory available for [chars]
Explanation The ICC subsystem could not obtain the memory it needed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. 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 (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%ICC-4-CONSISTENCY : Internal consistency check: [chars]
Explanation An internal inconsistency was found in some ICC data structures.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. 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 (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%ICC-4-COMM : Communication failure occurred while [chars]
Explanation
Recommended Action


%ICC-4-BAD_ACCOUNTING : ICC received a bad class [dec]
Explanation A communication failure has occurred between this card and another card in the system.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. 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 (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%ICC-4-HEARTBEAT : Card [dec] failed to respond to heartbeat
Explanation A communication failure has occurred between the primary and the specified line card.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. 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 (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%ICC-5-WATERMARK : [dec] [chars] [chars] pkts for class [chars] are waiting to be processed
Explanation Processor got packets for the class and are waiting to be procssed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%ICC-2-OPEN : ICC Create Session Failed for card <[hex]> Queue <[chars]>
Explanation ICC was not able to create a session for the destination seat
Recommended Action collect output from 'show oir debug swover_global_mask' from SP


%ICC-2-JOIN : ICC mcast joining failed member <[hex]> to group <[hex]> with ipc error <[chars]>
Explanation ICC was not able to join a member for the mcast group
Recommended Action collect output 'show icc mcast status' from RP


%ICC-5-HUGE_BUFFER : Class [[chars]] with Request id [dec] requested a huge buffer of Size [dec].
Explanation Huge packet requests would deplete the memory at the linecards
Recommended Action ICC client is trying to request huge packet buffer Please use the command Show icc internal to get get the traceback and file a DDTS against the component


%ICC-3-MAST_BAD_FREE : ICC multicast memory already freed
Explanation One of the ICC multicast request's memory was found to be free when response arrived
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


IDBMAN

%IDBMAN-3-VLANINUSE : [chars]: Vlan [dec] is in use by [chars]
Explanation 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 No action is required.


%IDBMAN-3-INVALIDVLAN : [chars]: trying to use invalid Vlan [dec]
Explanation There is an internal error that caused an invalid Vlan to be used by the software.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IDBMAN-3-VLANNOTSET : [chars]: Vlan [dec] not set since it already has Vlan [dec]
Explanation There is an internal error that caused an interface to not have its Vlan set to the requested value
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IDBMAN-6-VLANMAPPED : Vlan [dec] is mapped to [chars]
Explanation Informational message indicating that the given Vlan is mapped to the given interface
Recommended Action No action is required.


%IDBMAN-3-AGGPORTMISMATCH : [chars]([dec] / [dec]) does match internal slot/port state [chars]([dec] / [dec])
Explanation There is an internal error that caused an invalid aggregate port to be used by the software.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IDBMAN-3-INVALIDAGGPORTBANDWIDTH : [chars]([dec] / [dec]) has an invalid bandwidth value of [dec]
Explanation There is an internal error that caused an invalid bandwidth to be used for an aggregate port.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IDBMAN-3-DELETEDAGGPORT : [chars]([dec] / [dec]) Group [dec] 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 error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IDBMAN-3-NOTANAGGPORT : [chars]( [dec] / [dec] ) is not an aggregate port
Explanation 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 error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IDBMAN-3-INVALIDPORT : [chars]: trying to use invalid port number [dec] ( Max [dec] )
Explanation There is an internal error that caused an invalid port numer to be used by the software.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IDBMAN-4-ACTIVEPORTSINAGGPORT : [chars]( [dec] / [dec] ) has [dec] active ports, but is being removed
Explanation There is an internal error that caused an aggregate port with active ports to be removed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IDBMAN-3-PORTNOTINAGGPORT : [chars]([dec] / [dec]) is not present in Aggport [chars]([dec] / [dec])
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 error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IDBMAN-4-REMOVED_NONDEFAULT_CONFIG : Removed non default configuration for interfaces in slot [dec]
Explanation In SSO mode, the non-default configuration for any removed linecard is not synced to the standby during the bulk sync, and it is removed from the configuration to avoid a config mismatch between active and standby supervisors.
Recommended Action No action is required.


%IDBMAN-3-IIF_ID_REGISTRATION_FAILED : IIF_ID registration failed for Port [chars] due to memory allocation failure. Port has been shutdown
Explanation The system is low on memory due to which IIF-ID registration failed. This results in failure to apply polices such as QoS and Security acls on this port.
Recommended Action LOG_STD_REDUCE_ACTION Once memory is available, run 'no shutdown' on the port.


IDB_IDENTITY

%IDB_IDENTITY-3-MALLOC : Memory allocation failure for HWIDB type [dec]
Explanation 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 error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


IDB_SGI

%IDB_SGI-2-XDRREG : [chars]
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IDB_SGI-2-MEMREQ : [chars]
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IDB_SGI-3-BADPTR : [chars] of interface with ifindex [int] is invalid
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IDB_SGI-3-MEMFAIL : [chars]
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IDB_SGI-4-MEMBERREQ : member request failure for interface with ifindex [int] returned err - [chars]
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IDB_SGI-3-XDRREQ : [chars]
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IDB_SGI-4-INTERR : [chars] for interface with ifindex [int]
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IDB_SGI-4-UNEXPINP : [chars]
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


IDMGR

%IDMGR-3-MALLOC_FAILURE : [chars]
Explanation A malloc failure occured in ID Manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IDMGR-3-INTERRUPT : [chars]
Explanation An id_get attempted at interrupt level.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IDMGR-3-INVALID_ID : bad id in [chars] (id: [hex])
Explanation An ID Manager error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IDMGR-3-INVALID_ID_TABLE_SIZE : bad new ID table size
Explanation A bad new table request to ID Manager occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IDMGR-3-ID_MANAGER_INTERNAL_ERROR : [chars]
Explanation Internal Error occured with ID Manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


IEDGE

%IEDGE-4-PBHK_DEPLETED_INDICES : No more portbundles can be allocated
Explanation The source interfaces configured for Portbundle Hostkey feature are not sufficient and the number of portbundles available are all used up. Add more source interfaces in the configuration.
Recommended Action Check configuration on the ISG


%IEDGE-4-TC_UNDEFINED_ACL : Traffic class ACL [chars] is not defined, creating permit all ACL
Explanation The ACL specified for classification of traffic is not configured on the ISG. Creating a permit all ACL. ACL should be configured on the ISG.
Recommended Action Configure the ACL on the ISG


%IEDGE-4-CLOCK_CHANGE_TIMER_INV : A Local clock change has caused a running timer to be invalid
Explanation A change in local clock has made a currently running timer to be invalid
Recommended Action Check the clock configuration


%IEDGE-3-CH_INTERNAL_ERROR : Internal error in command processing - session handle=[hex]
Explanation There has been an internal error relating to CoA command processing.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%IEDGE-3-CH_REGISTER_ERROR : CoA registration error in command processing - type '[chars]'
Explanation There has been an internal error relating to CoA command processing.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


IF

%IF-3-IDB_LIST_BAD_REF_COUNT : A bad reference count was encountered in an idb list element.
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%IF-2-IDB_TABLE_INIT : Malloc failed while initializing idb table
Explanation
Recommended Action


%IF-3-BAD_MTU : Internal error. MTU on [chars] too large or negative. Truncating from %ld to [int].
Explanation An internal software error occurred. The system attempted to set the MTU on an interface to an invalid value.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%IF-3-BADLOCK : Invalid lock use for [chars]: [chars][chars]
Explanation Application layer code attempted to access an unlocked interface.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IF-3-BADHWUNLOCK : ([chars]) attempted to unlock [chars] ([dec]). Locked by [chars] ([dec]).
Explanation Attempt to release semaphore held by another process.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IF-3-SEMAHOG : ([chars]) could not get [chars] semaphore. Held by ([chars]).
Explanation Unable to obtain interface semaphore.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%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 error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.


%IF-3-BADMACADDRTYPE : illegal mac address type, [dec]
Explanation This is an interal error that was recovered gracefully.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%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.
Recommended Action An interface on the router may have missed a request to bring itself up. If that happens, it may be necessary to reset the interface using a shutdown operation and then a no shutdown.


IFDAMP

%IFDAMP-5-UPDOWN : interface [chars] update [chars] state to [chars], interface is [chars]suppressed
Explanation dampening interface changed state.
Recommended Action No action is required.


%IFDAMP-5-ZERODELAY : dampening reuse timer is updated with 0 delay time
Explanation Inconsistency of dampening reuse timer wheel
Recommended Action No action is required.


IFMAP through INSTALL

IFMAP

%IFMAP-3-CAUSE_CFG : hash table not initialized
Explanation PAL interface handle to uidb hash table not initialized
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


IFMGR

%IFMGR-3-IFINDEX_PERSIST_ENTRY_CORRUPT : [chars] seems to be corrupted. Trying to read [dec] size
Explanation The ifIndex-table seems to be corrupted.
Recommended Action Delete the ifindex-table.


%IFMGR-3-INVALID_PERSISTENT_DATA : Invalid persistent data
Explanation Trying to write invalid persistent data
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%IFMGR-3-NOVECTOR : Interface manager failed to allocate IF vector. size [dec]
Explanation The interface vector was not able to be allocated with the number of elements required--initially or resize (see size in the error message).
Recommended Action TBD


%IFMGR-3-VECTOREXD : IF manager attempted to use interface [dec] outside vector range.
Explanation This message indicates that an interface with too large of an ifIndex value was attempted to be added to the IF-MGR DB.
Recommended Action Additional IF-MGR warning and/or error messages should accompany indication of this error. These additional messages should provide more details on the effected interface.


%IFMGR-3-VECTORPOSUSED : IF manager attempted to add interface [dec] which was already added.
Explanation This message comes from the IF-MGR DB when it is trying to add an ifIndex value for this interface which already exists in the ifIndex DB.
Recommended Action TBD


%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 TBD


%IFMGR-3-IFDB : IF manager interface database [chars] failure- [dec]
Explanation
Recommended Action TBD


%IFMGR-3-IFTDB : IF manager interface table database [chars] failure- [dec]
Explanation
Recommended Action TBD


%IFMGR-3-NOTYPEVECTOR : Interface manager failed to allocate IF type vector. size [dec]
Explanation The interface type vector was not able to be allocated with the number of elements required--initially or resize.
Recommended Action TBD


%IFMGR-3-NOIMACP : IF manager control process failed to start
Explanation
Recommended Action TBD


%IFMGR-4-NOIFINDEX : All SNMP if indices are exhausted
Explanation All SNMP MIB indices 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, contact your Cisco technical support representative, and provide the representative with the gathered information.


%IFMGR-3-BADIFINDEXTABLE : The file nvram:ifIndex-table is corrupt.
Explanation The file is not in the expected format.
Recommended Action If possible, please delete the file.


%IFMGR-4-NOSYNC : ifIndex not being synced between active and standby
Explanation When the standby comes up, then the tuple of ifIndex and ifDescr is synced so that when interfaces comes up they get the same ifIndex. This error happens when the interface doesn't get the ifIndex for the given ifDescr
Recommended Action Inform the technical support to raise the ddts


%IFMGR-5-RESTART : [chars]
Explanation The IF MGR process has restarted
Recommended Action This is an informational message. The system should recover on its own.


%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 where this message is generated is also shown in the message
Recommended Action Inform the technical support to raise the ddts


%IFMGR-3-DUP_IFINDEX : Duplicate ifIndex ([dec]) found for ifDescr [chars]; exists in ifTable for ifDescr [chars].
Explanation Interfaces have same ifIndex in IF-MGR assigned list. The 2nd interface registered with IF-MGR will be assigned with new index
Recommended Action 1. No Action, if ifIndex persist is not required. 2. Reload the standby RP, if ERR msg only seen in standby RP 3. Reload the router with the proper ifindex-table and image


%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

%IFS-4-FILEMAX : Failed to open [chars], maximum open files [dec])
Explanation The router has reached the maximum number of files that may be open at one time.
Recommended Action Close some files and try again. If this messages recurs, contact your technical support representative.


%IFS-3-FSMAX : Failed to add [chars], maximum filesystems [dec]
Explanation The router has reached the maximum number of file systems that can be supported at one time.
Recommended Action Contact your technical support representative.


%IFS-3-FSDUP : Failed to add [chars], filesystem prefix exists
Explanation A file system cound not be added because another file system exists with the same name.
Recommended Action Contact your technical support representative.


%IFS-3-FS_CREATE_FAIL : Failed to create [chars] file system, [chars]
Explanation An internal software error occurred.
Recommended Action Call your technical support representative for assistance.


%IFS-3-FS_CREATE_FAIL2 : Failed to create [chars] simple file system, [chars]
Explanation An internal software error occurred.
Recommended Action Call your technical support representative for assistance.


%IFS-3-FS_MISSING_FUNCTIONS : '[chars]' file system missing required functions, not created
Explanation 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.


%IFS-3-FS_STRUCT_ERROR : Data does not match expected internal representation
Explanation 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.


IKEV2

%IKEV2-5-OSAL_INITIATE_TUNNEL : NULL
Explanation
Recommended Action


%IKEV2-5-RECV_CONNECTION_REQUEST : NULL
Explanation
Recommended Action


%IKEV2-3-NEG_ABORT : NULL
Explanation
Recommended Action


%IKEV2-1-SEND_COOKIE_CHALLENGE : NULL
Explanation
Recommended Action


%IKEV2-5-IPSEC_COLLISION : NULL
Explanation
Recommended Action


%IKEV2-5-SA_UP : NULL
Explanation
Recommended Action


%IKEV2-5-SA_DOWN : NULL
Explanation
Recommended Action


%IKEV2-5-SA_REJECTED_RESOURCE_LOW : NULL
Explanation
Recommended Action


%IKEV2-5-SA_REJECTED_LIMIT_REACHED : [chars]
Explanation
Recommended Action


%IKEV2-5-INCREASE_PEER_WINDOW_SIZE : NULL
Explanation
Recommended Action


ILPOWER

%ILPOWER-3-ILPOWER_INTERNAL_IF_ERROR : Inline Power internal error, interface [chars]: [chars]
Explanation A software check failed during Power over Ethernet (PoE) processing.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%ILPOWER-5-ILPOWER_POWER_DENY : Interface [chars]: inline power denied. Reason: [chars]
Explanation There is not enough power remaining in the switch to supply to the Power over Ethernet (PoE) port.
Recommended Action No action is required.


%ILPOWER-5-ILPOWER_POWER_CDP_SHUT : Interface [chars]: inline power shut
Explanation Inline power is shut because cdp consumption power on this Power over Ethernet (PoE) port is greater than 1. allocation power or 2. hardware interface limit or 3. user configured max power or 4. available power on this switch.
Recommended Action No action is required.


%ILPOWER-3-CONTROLLER_ERR : Controller error, Controller number [dec]: [chars]
Explanation An error reported or caused by the Power over Ethernet (PoE) controller is detected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%ILPOWER-3-CONTROLLER_POST_ERR : Inline Power Feature is disabled on this switch because Power On Self Test (POST) failed on this switch. Please consult TECH support for further assistance
Explanation An error reported or caused by the Power over Ethernet (PoE) controller is detected during POST.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%ILPOWER-3-CONTROLLER_IF_ERR : Controller interface error, [chars]: [chars]
Explanation An interface error is detected between the Power over Ethernet (PoE) controller and system.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%ILPOWER-3-CONTROLLER_PORT_ERR : Controller port error, Interface [chars]: [chars]
Explanation A port error reported by the Power over Ethernet (PoE) controller is detected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%ILPOWER-5-POWER_GRANTED : Interface [chars]: Power granted
Explanation There is enough power available in the switch, and the switch is providing power on the interface.
Recommended Action No action is required.


%ILPOWER-5-LINKDOWN_DISCONNECT : Interface [chars]: Link down disconnect
Explanation The powered device is no longer connected to the switch, or the connected powered device is being powered by an external AC power source. The switch is no longer providing power on the interface.
Recommended Action No action is required.


%ILPOWER-5-IEEE_DISCONNECT : Interface [chars]: PD removed
Explanation The powered device is no longer connected to the switch, or the connected powered device is being powered by an external AC power source. The switch is no longer providing power on the interface.
Recommended Action No action is required.


%ILPOWER-7-DETECT : Interface [chars]: Power Device detected: [chars]
Explanation The switch has detected the attached power device.
Recommended Action No action is required.


%ILPOWER-5-INVALID_IEEE_CLASS : Interface [chars]: has detected invalid IEEE class: [dec] device. Power denied
Explanation The power device has invalid IEEE class. switch won't powerup the device
Recommended Action No action is required.


%ILPOWER-3-SHUT_OVERDRAWN : Interface [chars] is shutdown as it is consuming more than the maximum configured power ([dec]) milliwatts.
Explanation Interface is shutdown because it is consuming more than the maximum configured power
Recommended Action Make sure correct power is budgeted for this interface based on the power device electrical specifications or ratings. It is recommended to change the police cutoff power to a higher value to keep the device powered on


%ILPOWER-4-LOG_OVERDRAWN : Interface [chars] is overdrawing power. it is consuming [dec] milliwatts where as maximum configured power is ([dec]) milliwatts.
Explanation
Recommended Action Make sure correct power is budgeted for this interface based on the power device electrical specifications or ratings. Otherwise you might risk overloading the switch. It is recommended to change the police cutoffpower appropriately if needed


%ILPOWER-5-CLR_OVERDRAWN : Interface [chars] is NOT overdrawing power. it is consuming [dec] milliwatts where as maximum configured value is ([dec]) milliwatts.
Explanation
Recommended Action No action is required.


%ILPOWER-5-POLICE_POWER_INVALID : Interface [chars]: invalid power police [dec] milliwatts current [dec] mA voltage [dec] mV
Explanation power policing current or voltage value is invalid.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%ILPOWER-5-SENSE_POWER_INVALID : Interface [chars]: invalid power sense [dec] milliwatts current [dec] mA voltage [dec] mV
Explanation power sensing current or voltage value is invalid.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%ILPOWER-4-ILPOWER_POWER_SUPPLY : PoE Power Supply [chars]: [chars]
Explanation The power supply for PoE is OIR
Recommended Action Make sure power supply to PoE input is inserted after removal


%ILPOWER-4-ILPOWER_PS_ABSENCE : PoE module Power Supply not present Inline Power Feature is disabled on [chars] because Power On Self Test (POST) failed : [chars]
Explanation The power supply for PoE expansion module is not present or not inserted properly or faulty
Recommended Action Make sure power supply to expansion module is inserted properly and reload the switch with PoE power supply present


%ILPOWER-5-PWRGOOD_SPARE_PAIR : Interface [chars]: spare pair power good
Explanation Spare pair power request was successful and power is available on spare pair
Recommended Action No action is required.


%ILPOWER-5-TSTART_SPARE_PAIR : Interface [chars]: spare pair power error: TSTART
Explanation spare pair tstart error has occurred, power on spare pair will not be supplied
Recommended Action No action is required.


%ILPOWER-5-PGOOD_TIMEOUT_SPARE_PAIR : Interface [chars]: spare pair power good timeout error
Explanation spare pair power good timeout error has occurred, power on spare pair will not be supplied
Recommended Action No action is required.


%ILPOWER-5-DET_SHORT_SPARE_PAIR : Interface [chars]: spare pair short detected
Explanation spare pair short detect error has occurred, power on spare pair will not be supplied
Recommended Action No action is required.


%ILPOWER-5-DET_TIMEOUT_SPARE_PAIR : Interface [chars]: spare pair detect timeout
Explanation spare pair timeout detect error has occurred, power on spare pair will not be supplied
Recommended Action No action is required.


%ILPOWER-6-SET_ILPOWER : Set power allocated to POE to [dec] for slot [dec]
Explanation The power allocated to POE has changed
Recommended Action No action is required.


IM

%IM-0-UIPEER_CREATE : Failed to create user interface peer.
Explanation The system failed to create a user interface peer.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%IM-2-INITIALIZATION_FAILED :
Explanation Initialization of IOx Manager process failed.
Recommended Action Review ioxman logs taking note of the timestamp information to select specific information to review. Copy the message and other related information exactly as it appears on the console or in the system log.


%IM-0-EVENT_LIBRARY :
Explanation An event facility initialization or maintenance function failed. This could be due to a software defect or system resource exhaustion.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%IM-2-INVALID_ACT_MSG : Virtualization Service[chars]
Explanation The virtualization service activate message was received, however, the data it contained could not be interpreted
Recommended Action Enable the IOx-manager trace logs and repeat the activation of the virtualization service. Collect the IOx-manager logs and scan them for the cause.


%IM-2-INVALID_DEACT_MSG : Failed to process virtualization service deactivate message
Explanation The virtualization service deactivate message was received, however, the data it contained could not be interpreted
Recommended Action Enable the IOx-manager trace logs and repeat the activation of the virtualization service. Collect the IOx-manager logs and scan them for the cause.


%IM-2-ALLOC_VIRT_INST_RCS : Virtualization Service[chars]
Explanation A memory allocation request failed to allocate a data structure required to activate the virtualization service.
Recommended Action Enable the IOx-manager trace logs and repeat the activation of the virtualization service. Collect the IOx-manager logs and scan them for the cause.


%IM-2-START_FAILED : Virtualization Service[chars]
Explanation The named virtualization service failed to start.
Recommended Action Enable the IOx-manager trace logs and repeat the activation of the virtualization service. Collect the IOx-manager logs and scan them for the cause.


%IM-2-VIRT_INST_MEMORY : Virtualization Service[chars]
Explanation The virtualization service requires physical memory in excess of the free memory available to virtualization services.
Recommended Action Enable the IOx-manager trace logs and repeat the activation of the virtualization service. Collect the IOx-manager logs and scan them for the cause.


%IM-2-VIRT_INST_DISK : Virtualization Service[chars]
Explanation The virtualization service requires Disk Storage in excess of the Free Disk Storage available to virtualization services.
Recommended Action Enable the IOx-manager trace logs and repeat the activation of the virtualization service. Collect the IOx-manager logs and scan them for the cause.


%IM-2-MEMORY_LIMIT : Virtualization Service[chars]
Explanation The virtualization service machine definition file is requesting more memory than the system has available for virtualization services.
Recommended Action Enable the IOx-manager trace logs and repeat the activation of the virtualization service. Collect the IOx-manager logs and scan them for the cause.


%IM-2-VCPU_LIMIT : Virtualization Service[chars]
Explanation The virtualization service machine definition file is requesting more VCPUs than the system has reserved for virtualization services.
Recommended Action Enable the IOx-manager trace logs and repeat the activation of the virtualization service. Collect the IOx-manager logs and scan them for the cause.


%IM-2-DISK_IMAGE_PATH : Virtualization Service[chars]
Explanation The virtualization service machine definition file contains an invalid disk image path for one of the disk devices. This may be a Harddisk, CDROM or USB storage device.
Recommended Action Enable the IOx-manager trace logs and repeat the activation of the virtualization service. Collect the IOx-manager logs and scan them for the cause.


%IM-2-VIRT_INST_LOG_UNTHROTTLE : Failed to unthrottle the log for virtualization service [chars]
Explanation The named virtualization service had sent overwhelming sys log messages and its log had been throttled as a result, but system has failed to unthrottle it for some reason.
Recommended Action For debugging collect the iox-manager logs and scan them for the cause.


%IM-2-VIRT_INST_STATE : Virtualization Service[chars]
Explanation The named virtualization service has failed. It is no longer running either because the guest OS has failed, the guest OS has shut down the machine or the emulator has failed.
Recommended Action An attempt at restarting the virtualization service can be made from the IOS configuration by doing a no activate/activate. For debugging collect the IOx-manager logs and scan them for the cause.


%IM-2-FIND_VIRT_INST_ENTRY : Failed to find virtualization service with id [int] in the IOx-manager list
Explanation The virtualization service with the ID named could not be located in the IOx-manager list.
Recommended Action Enable the IOx-manager trace logs and repeat the activation of the virtualization service. Collect the IOx-manager logs and scan them for the cause.


%IM-5-AUX : Virtualization Service[chars]
Explanation The AUX login to a virtualization service may allow the user access to system functions that may not have been tested or may interact with the system in unintended ways. Use with caution.
Recommended Action No action is required


%IM-2-INVALID_UNPROV_MSG : Failed to process virtualization service unprovision message
Explanation The virtualization service unprovision message was received, however, the data it contained could not be interpreted
Recommended Action Enable the IOx-manager trace logs and repeat the activation followed by deactivation and then unprovision of the virtualization service. Collect the IOx-manager logs and scan them for the cause.


%IM-2-VCPU_INVALID : Virtualization Service[chars]
Explanation The virtualization service machine definition file is requesting invalid VCPU value.
Recommended Action Enable the IOx-manager trace logs and repeat the activation of the virtualization service. Collect the IOx-manager logs and scan them for the cause.


%IM-2-CPUSHARES_LIMIT : Virtualization Service[chars]
Explanation The virtualization service machine definition file is requesting more CPU shares than the system has available for virtualization services.
Recommended Action Deactivate any other virtualization services to free up CPU share resources and activate this virtualization service. If that does not address the problem, then enable the IOx-manager trace logs and repeat the activation of the virtualization service. Collect the IOx-manager logs and scan them for the cause.


%IM-2-INSTALL_FAILURE : Virtualization Service[chars]
Explanation The installation of the virtualization service failed.
Recommended Action Enable the IOx-manager trace logs and repeat the installation of the virtualization service. Collect the IOx-manager logs and scan them for the cause.


%IM-2-INSTALL_MEDIA_RETRY : VM install media still unavailable.[chars]
Explanation The install media was not detected. Waiting for udev to complete install media(harddisk) detection.
Recommended Action After IOx-manager exceeds the maximum retry limit, verify if install media (harddisk) is accessible and retry the installation again.


%IM-2-VIRT_INST_MGMT_INTERFACE : Virtualization service [chars] has no management interface defined but it is configured in CLI.
Explanation A management interface is configured but none is defined.
Recommended Action Deactivate the virtualization service, remove the management interface configuration CLI, and reactivate the virtual-service.


%IM-2-GENERAL_FAILURE : Virtualization Service[chars]
Explanation The named virtualization service has triggered the log. Please interpret the log in the context of the virtualization services.
Recommended Action No action is required


%IM-3-SDWRAP_ERR : Description: [chars], errcode: [dec]
Explanation Debug infrastructure error
Recommended Action Collect the IOx-manager logs and scan them for the cause.


%IM-3-PSS_ERR : Purpose: [chars], URI: [chars], errcode: [dec]
Explanation Persistent Storage Service handling error
Recommended Action Collect the IOx-manager logs and scan them for the cause.


%IM-3-PSS_SNAPSHOT_ERR : Source URI: [chars], Destination URI: [chars], errcode: [dec]
Explanation Persistent Storage Service snapshot error
Recommended Action Collect the IOx-manager logs and scan them for the cause.


%IM-2-NETWORK_CONFIG_ERROR : Virtualization Service[chars]
Explanation A network configuration error has been detected for the named virtualization service.
Recommended Action No action is required


%IM-2-INSTALL_LOG : [chars] [chars] [chars] [chars]
Explanation The installation log of the named virtualization service, is to provide more information about long running operation, that could affect the control of CLI
Recommended Action No action is required


%IM-2-UPGRADE_LOG : [chars] [chars] [chars] [chars]
Explanation The upgrade log of the named virtualization service, is to provide more information about long running operation, that could affect the control of CLI
Recommended Action No action is required


%IM-2-INSTALL_STATE : [chars] '[chars]'[chars] [chars]
Explanation The installation state of the named virtualization service has changed as notified by IOx-manager.
Recommended Action In the failed case, check IOx-manager's logs for the cause of the failure. In the successful case, this notification can be ignored.


%IM-2-UNINSTALL_ALL_VMS : All Virtualization Services are being uninstalled [chars][chars] [chars]
Explanation All virtualization services are being uninstalled by IOx-manager.
Recommended Action Examine the reason given as to why all virtualization services are being uninstalled for more information. If the reason indicated is due to some error condition, check IOx-manager's logs for the cause of the failure.


%IM-2-ACTIVATION_STATE : [chars] '[chars]' [chars] [chars]
Explanation The activation state of the named virtualization service has changed as notified by IOx-manager.
Recommended Action In the failed case, check IOx-manager's logs for the cause of the failure. In the successful case, this notification can be ignored.


%IM-4-WATCHDOG_TIMER : [chars] '[chars]' [chars] [chars]
Explanation The watchdog timer configured for the named virtual service has expired.
Recommended Action Check any logs produced by the virtualization service to determine the cause.


%IM-2-HA_SYNC_ERR : [chars] '[chars]' [chars]
Explanation The ha-sync persistent storage disk for the virtualization service cannot be watched for sync to standby RP.
Recommended Action Collect the IOx-manager logs and scan them for the cause.


%IM-2-DEACT_FOR_ISSU : [chars] Max ([int]s)
Explanation An ISSU event is pending. Any active VMs will be automatically deactivated to allow ISSU preprocessing to validate the environment. Any ISSU-deactivated VMs will be automatically restarted if the ISSU is cancelled.
Recommended Action None. Allow the ISSU to continue and the VMs will restart when the ISSU completes or cancel the ISSU and IOx-manager will automatically


%IM-2-RESET_FORCE : Virtualization Services non-recoverable reset command processed
Explanation A 'virtualization service reset force' command has been entered and processed. This action initiates a cleanup of last resort. Occasionally a VM will get into an unrecoverable state that prevents it from activating but also from uninstalling. This is a rare event but when it happens the only resort may be to remove the .conf control file and reboot, which forces a cleanup of all previously installed VM files and artifacts. Note that once this command is used, current VMs are considered to be in an unstable or unpredictable state, and all future install, uninstall, upgrade, and activation commands will be blocked.
Recommended Action Once the command is entered and accepted, there is no recourse but to restart the system.


%IM-2-MOVE_STATE : [chars] '[chars]' [chars] [chars]
Explanation The move of the core or log file of the named virtualization service has as been successful or failed as notified by IOx-manager.
Recommended Action In the failed case, check IOx-manager's logs for the cause of the failure. In the successful case, this notification can be ignored.


%IM-2-RSYNC_STATE : [chars] [chars] [chars] [chars]
Explanation IOx-manager tries to remote sync the virtual-instance configuration file and the OVA repository to all online nodes. If rsync fails even after consecutive retries, this notification would be raised.
Recommended Action In the failed case, check IOx-manager's logs for the cause of the failure. Check for the rsync error code and root cause the same.


%IM-2-HA_SYNC_THREAD_STATE : HA remote sychronize thread has failed and exited.
Explanation IOx-manager tries to remote sync the OVA repository to all online nodes using a separate thread. If that thread fails, this notification would be raised.
Recommended Action In the failed case, check IOx-manager's logs for the cause of the failure. Check for the pthread error msg and root cause the same.


%IM-2-HA_STATE : [chars] [chars] [chars] [chars]
Explanation IOx-manager tries to detect the role/slot of various nodes on HA events from the platform. If any of those event callbacks fail, this notification would be raised.
Recommended Action In the failed case, check IOx-manager's logs for the cause of the failure. Check for the HA event error msg and root cause the same.


%IM-2-HA_SWITCHOVER_STATE : [chars] [chars] [chars] [chars]
Explanation IOx-manager HA switchover state related messages for a virtual-service whilst it is being recovered on newly active RP after a HA switchover.
Recommended Action In the failed case, check IOx-manager's logs for the cause of the failure. Check for the HA event error msg and root cause the same.


%IM-4-HA_SYNC_NEEDED : If using the guest shell, please use 'guestshell sync' if you want to preserve state on standby in case of supervisor switchover
Explanation Message notifying user that he needs to manually synchronize the Virtualization service contents to standby supervisor in order to preserve these contents in case of a supervisor switchover. Currently only applicable to the guest shell
Recommended Action User can type the 'guestshell sync' command on active supervisor to synchronize it's contents to the standby supervisor if desired.


%IM-2-RESIZE_OPER_STATE : Virtualization service '[chars]' [chars][chars] to '[int]' [chars]
Explanation IOx-manager attempts to resize various VM parameters like rootfs size, CPU share, memory if requested by user. Success/failure status messages for these resize operations are communicated by this syslog.
Recommended Action In the failed case, check IOx-manager's logs for the cause of the failure. Check for the HA event error msg and root cause the same.


%IM-2-GUESTSHELL_ENABLED : The guest shell has been enabled. The command '[chars]' may be used to access it, '[chars] destroy' to remove it.
Explanation Informs the user that the guest shell virtualization service has been enabled (which is done by default).
Recommended Action The user may use or remove the guest shell with the commands specified.


%IM-5-PERMISSION_DENIED : Virtualization Service '[chars]' is not owned by client IOSd
Explanation An attempt was made to modify a virtual-service that is not owned by by the client. The request was rejected.
Recommended Action No action is required.


%IM-2-IOX_INST_CRIT : IOX SERVICE [chars] LOG: [chars]
Explanation The named virtual service has triggered the log. Please interpret the log in the context of the virtual services.
Recommended Action No action is required


%IM-3-IOX_INST_ERR : IOX SERVICE [chars] LOG: [chars]
Explanation The named IOX service has triggered the log. Please interpret the log in the context of the IOX services.
Recommended Action No action is required


%IM-4-IOX_INST_WARN : IOX SERVICE [chars] LOG: [chars]
Explanation The named IOX service has triggered the log. Please interpret the log in the context of the IOX services.
Recommended Action No action is required


%IM-5-IOX_INST_NOTICE : IOX SERVICE [chars] LOG: [chars]
Explanation The named IOX service has triggered the log. Please interpret the log in the context of the IOX services.
Recommended Action No action is required


%IM-6-IOX_INST_INFO : IOX SERVICE [chars] LOG: [chars]
Explanation The named IOX service has triggered the log. Please interpret the log in the context of the IOX services.
Recommended Action No action is required


%IM-7-IOX_INST_DEBUG : IOX SERVICE [chars] LOG: [chars]
Explanation The named IOX service has triggered the log. Please interpret the log in the context of the IOX services.
Recommended Action No action is required


%IM-2-IOX_INST_LOG_UNTHROTTLE : Failed to unthrottle the log for IOX service [chars]
Explanation The named IOX service had sent overwhelming sys log messages and its log had been throttled as a result, but system has failed to unthrottle it for some reason.
Recommended Action For debugging collect the ioxman logs and scan them for the cause.


%IM-6-IOX_RECONCILE_INFO : App-hosting application reconcile process [chars]
Explanation Indicates stage of reconcile (application recovery) process.
Recommended Action No action is required


IMGR

%IMGR-0-FIPS_FMFP_BYPASS_TEST : NIST bypass test failed for [chars].
Explanation Forwarding Manager IPsec component detected a discrepancy when adding or deleting a security sensitive object. This could be due to a hardware or software resouce limitation or a software defect.
Recommended Action Check the logs for information on the relevant object download states. Remove the object or a parent object in question. If the problem persists reboot the forwarding processor (ESP).


%IMGR-6-FIPS_FMFP_CRNG_TEST : continuous [chars]approved RNG test failed.
Explanation Forwarding Manager IPsec component detected two identical random number sequences. This could be due to a hardware mulfunction or a software defect.
Recommended Action If the problem persists reboot the forwarding processor (ESP).


%IMGR-6-FIPS_FMFP_OLAP_TEST : FIPS-approved RNG key seed and state overlap.
Explanation Forwarding Manager IPsec component detected an overlap in FIPS-approved RNG key seed and state. This could be due to a hardware mulfunction or a software defect.
Recommended Action If the problem persists reboot the forwarding processor (ESP).


%IMGR-6-FIPS_FMFP_KAT_TEST : power up cryptographic self-test didnot run to completion: [chars].
Explanation Forwarding Manager power up known answer self-test (KAT) failed. This could be due to a hardware malfunction or a software defect.
Recommended Action If using ipsec, reboot the forwarding processor (ESP).


%IMGR-0-FIPS_CPP_CLIENT_BYPASS_TEST : CPP Client FIPS bypass test failed for [chars].
Explanation Forwarding Manager CPP client IPSEC bypass test failed. This could be due to a hardware malfunction or a software defect.
Recommended Action If the problem persists reboot the forwarding processor (ESP).


%IMGR-6-FIPS_FMFP_N2_ERR_FAIL : Cryptographic coprocessor non-critical failure: [chars].
Explanation Cryptographic coprocessor non-critical operation failed. If the problem persists reboot the forwarding processor(ESP)
Recommended Action If the problem persists reboot the forwarding processor (ESP).


%IMGR-0-FIPS_FMFP_N2_SEVERE_ERR_FAIL : Cryptographic coprocessor severe failure: [chars].
Explanation Cryptographic coprocessor critical operation failed. Further data processing on ESP is halted
Recommended Action forwarding processor (ESP) is rebooted automatically. no action needed


%IMGR-6-FMFP_KAT_TEST_RESULT : crypto self-test for algorithm: ([chars] ... passed).
Explanation Forwarding Manager power up known answer self-test (KAT) success. This is not an error message
Recommended Action No action needed.


%IMGR-6-FMFP_IPSEC_MIN_MTU_INFO : MTU smaller than minimum IPSec MTU, [chars].
Explanation Minimum MTU supported by crypto processor is 256B, MTU lower than 256B is set to 256B
Recommended Action No action needed


%IMGR-6-FMFP_IPSEC_UNSUPPORTED_CIPHER : Cipher [chars] is not supported on this ESP.
Explanation This ESP does not support this IPSec cipher
Recommended Action No action needed


%IMGR-6-FMFP_IPSEC_CRYPTO_CTRL_THROTTLED : IPsec Control Plane Overload Crypto Device: [chars].
Explanation This ESP crypto device is overloaded.
Recommended Action May need to config platform ipsec control-plane medium|heavy


INDXOBJ

%INDXOBJ-3-INTERRUPT : index object routine [chars] called from interrupt context
Explanation inappropriate index object routine called from interrupt routine.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%INDXOBJ-3-ADD_ERROR : index add for [chars] failed: [chars]
Explanation index object routine error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


INFRA

%INFRA-3-INVALID_GPM_ACCESS : Invalid GPM [chars] at [hex] HAL start [hex] HAL end [hex] INFRA start [hex] INFRA [hex] NET [hex], MSGDEF_LIMIT_MEDIUM
Explanation Processing packet went beyond valid packet data, packet was possibly invalid, ppe info and encrypted pkt dump follow
Recommended Action LOG_STD_ACTION


%INFRA-3-INVALID_GPM_ACCESS_INFO : [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex]
Explanation Registers associated with previous exception error
Recommended Action LOG_STD_ACTION


%INFRA-3-INVALID_GPM_ACCESS_DATA :
Explanation Packet associated with previous exception error The packet data has been encrypted
Recommended Action LOG_STD_ACTION


INSTALL

%INSTALL-5-OPERATION_START_INFO : Started [chars] package [chars]
Explanation This message is used to indicate the beginning of operations.
Recommended Action No action required. This is not an error, it is an indication that the system is starting the operation.


%INSTALL-5-OPERATION_COMPLETED_INFO : Completed [chars] package [chars]
Explanation This message is used to indicate the completion of operations.
Recommended Action No action required. This is not an error, it is an indication that the system completed the operation.


%INSTALL-3-OPERATION_ERROR_MESSAGE : Failed to [chars] package [chars], Error: [chars]
Explanation This message is used to inform the failure reason.
Recommended Action Please refer to the error message to analyze the cause of failure.


%INSTALL-5-INSTALL_START_INFO : Started [chars] [chars] [chars]
Explanation This message is used to indicate the beginning of install operations.
Recommended Action No action required. This is not an error, it is an indication that the system is starting this operation.


%INSTALL-5-INSTALL_COMPLETED_INFO : Completed [chars] [chars] [chars]
Explanation This message is used to indicate the completion of install operations.
Recommended Action No action required. This is not an error, it is an indication that the system completed this operation.


%INSTALL-3-INSTANT_ERROR_MESSAGE : Error Message: [chars]
Explanation This message is used to send a instant erorr message.
Recommended Action No action required.


%INSTALL-5-INSTALL_AUTO_ABORT : Install auto abort timer expired: initiating abort
Explanation An install operation has been aborted because the auto abort timer has expired.
Recommended Action No user action is needed. If you want to commit the ISSU upgrade, redo the upgrade. Otherwise, this is an informational message only.


%INSTALL-5-INSTALL_AUTO_ABORT_TIMER_PROGRESS : Install auto abort timer will expire in [dec] seconds
Explanation An install operation will be aborted after specified seconds of time.
Recommended Action No user action is needed. If you want to commit the ISSU upgrade, redo the upgrade. Otherwise, this is an informational message only.


INTERCHASSIS_REDUNDANCY through IOSXE_FMANRP

INTERCHASSIS_REDUNDANCY

%INTERCHASSIS_REDUNDANCY-4-STDBY_PRESENT : Removal of standby RP in location [chars] is recommended for inter-chassis redundancy configuration
Explanation Removal of standby RP from the chassis is recommended for inter-chassis redundancy
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


INTERFACE_API

%INTERFACE_API-4-BADSWIDB : [chars] may not be referencing the correct swidb
Explanation An internal software error occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%INTERFACE_API-4-BADPAKINPUT : pak->if_input is not initialized
Explanation An internal software error occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%INTERFACE_API-1-NAMESTRTOOLONG : Interface name [chars].[int] exceeded maximum allowed length [dec]
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%INTERFACE_API-3-NOADDSUBBLOCK : The [chars] subblock named [chars] was not added to [chars]
Explanation A software error has occured, this message is displayed when IDB subblocks cannot be added.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%INTERFACE_API-3-INVALIDSUBBLOCKPARAMETERS : Invalid subblock parameters for [chars] were supplied.
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show idb and show tech-support commands to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit BUG_TOOLKIT . If you still require assistance, open a case with the Technical Assistance Center via the Internet TAC_CASE_OPEN , or contact your Cisco technical support representative and provide the representative with the gathered information.


%INTERFACE_API-3-SUBNUMDBERR : subnum [hex] error in [chars]
Explanation A software error has occured, this message is displayed when a problem has occured with a sub_number db.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%INTERFACE_API-1-NOMORESWIDB : No more SWIDB can be allocated, maximum allowed [dec]
Explanation No more Interfaces can be created because the maximum number of SWIDB allowed for this platform has been reached
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%INTERFACE_API-1-NOMORE_HASWIDBS : No more IDBS can be created. The maximum allowed numbers, [int], has been reached on Standby Please force redundancy mode to RPR if full Active Capacity, [int], is needed
Explanation No more Software IDB numbers can be Created. The maximum allowed numbers has been reached for this High Available System.
Recommended Action


%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 numbers has been reached for this platform.
Recommended Action In addition to the following, copy the information from show idb. LOG_STD_ACTION


%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 numbers has been reached for this platform.
Recommended Action In addition to the following, copy the information from show idb. LOG_STD_ACTION


%INTERFACE_API-4-BADPAKOUTPUT : pak->if_output is not initialized on interface [chars]
Explanation An internal software error occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%INTERFACE_API-4-BADPOINTER : Function [chars] detected an invalid [chars] pointer of %08lX, ignoring
Explanation A software error has occurred, this message is displayed when an invalid pointer is detected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%INTERFACE_API-3-NODESTROYSUBBLOCK : The [chars] subblock named [chars] was not removed
Explanation A software error has occured, this message is displayed when IDB subblocks cannot be removed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%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 error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%INTERFACE_API-3-NOSUBBLOCK : [chars] subblock does not exist on interface [chars]
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%INTERFACE_API-4-TBLERROR : A error occurred while using the Index Table utility for [chars].
Explanation A software error has occurred; this message is displayed when an Index table feature could not be used successfully.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%INTERFACE_API-3-BADIDBSTATUSCHANGECALL : Invalid function call at interrupt level.
Explanation An internal function was illegally called at interrupt level. This error might be caused by incorrectly coded creation or deletion of an interface, or during an OIR operation.
Recommended Action Perform a search of the Bug Toolkit, BUG_TOOLKIT . If you still require assistance, copy the error message exactly as it appears on the console or in the system log. Issue the show tech command and copy the output. If you performed any actions before the error message appeared, make a note of this. Open a case with the Technical Assistance Center via the Internet TAC_CASE_OPEN , or contact your Cisco technical support representative and provide the representative with the gathered information.


%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. This message is displayed when an operation on the if_number to idb mapping table could not be performed successfully.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%INTERFACE_API-3-HWIDBQREENTRANT : [chars] in progress of being inserted/removed, ignoring new request to [chars]
Explanation A software error has occurred while attempting to insert or remove the interface into the system as there's already another attempt in progress to insert or remove this interface. The first attempt must complete before a new attempt can be started. The user should retry this operation at a later time.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


IOMD_INFRA

%IOMD_INFRA-4-BADPOINTER : Function [chars] detected an invalid [chars] pointer of %08lX, ignoring
Explanation A software error has occurred, this message is displayed when an invalid pointer is detected.
Recommended Action Examine the logs for IOMD. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center via the Internet athttps://mycase.cloudapps.cisco.com/case, or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOMD_INFRA-3-IPCSENDFAIL : IOMD failed to send a message [chars] reason: [chars]
Explanation IOMD failed to send message to the RP
Recommended Action Examine the logs for IOMD. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center via the Internet athttps://mycase.cloudapps.cisco.com/case, or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOMD_INFRA-3-IPCALLOCFAIL : Failed to allocate IPC buffer [chars]
Explanation The IM failed to allocate a buffer for communication with RSP
Recommended Action Examine the logs for IOMD. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center via the Internet athttps://mycase.cloudapps.cisco.com/case, or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOMD_INFRA-6-TDLMSG_INCOMPATIBLE : Failed to copy message [chars] to buffer, not allowed for current domain.
Explanation Failure to marshal a message indicates an incompatibility \ with the intended recipient.
Recommended Action Examine the logs for IOMD. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center via the Internet athttps://mycase.cloudapps.cisco.com/case, or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOMD_INFRA-3-INVALID_SLOT_NUM : An invalid slot number is specified in one of the internal APIs. slot=[dec] max_slot=[dec]
Explanation Invalid slot number to find the TDL domain
Recommended Action Examine the logs for IOMD. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center via the Internet athttps://mycase.cloudapps.cisco.com/case, or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOMD_INFRA-3-INVALID_BAY_NUM : An invalid bay number is specified in one of the internal APIs. bay=[dec] max_bay=[dec]
Explanation Invalid bay number to find the TDL domain
Recommended Action Examine the logs for IOMD. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center via the Internet athttps://mycase.cloudapps.cisco.com/case, or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOMD_INFRA-4-INTR_OVER_LIMIT : IOMd main thread disabled interrupt for [int] msec.
Explanation IOMd main thread process disabled interrupt too long
Recommended Action Examine the logs for IOMD. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center via the Internet athttps://mycase.cloudapps.cisco.com/case, or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOMD_INFRA-3-INTR_EVENT : IOMd fast thread event ([dec]).
Explanation IOMd fast thread event
Recommended Action Examine the logs for IOMD. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center via the Internet athttps://mycase.cloudapps.cisco.com/case, or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOMD_INFRA-3-I2C_WRITE : An I2C write has failed because [chars]
Explanation An I2C write has failed. This could be due to a hardware or software defect.
Recommended Action Note the time of the error message and examine the logs for I2C errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%IOMD_INFRA-3-I2C_READ : An I2C read has failed because [chars]
Explanation An I2C read has failed. This could be due to a hardware or software defect.
Recommended Action Note the time of the error message and examine the logs for I2C errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%IOMD_INFRA-3-LINECARDDIAGSFAILED : Module [chars] in Slot [dec] failed online diagnostics. Please use 'show post' for more details
Explanation Online Diag has failed. This could be due to a hardware or software defect.
Recommended Action Note the time of the error message and examine the logs for errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


IOSD

%IOSD-3-BIPC_REJECT : Could not accept ipc connection: [chars]
Explanation This error occurs if shell-manager has denied an ipc connection request from IOS.
Recommended Action Check the connection request parameters.


%IOSD-3-TDL_PROPERTIES : Could not set message properties for connection: [chars]
Explanation This error occurs if shell-manager is unable to set message properties for the IOS-sman connection
Recommended Action Check the connection request parameters.


IOSD_INFRA

%IOSD_INFRA-6-IFS_DEVICE_OIR : Device [chars] [chars]
Explanation USB inserted/removed
Recommended Action No action is required.


%IOSD_INFRA-3-IFS_DEVICE_DETECT_FAIL : Device [chars] [chars]
Explanation USB detection failed
Recommended Action USB Insertion could not be handled completely. Device needs to be removed and re-inserted


IOSXE_APS

%IOSXE_APS-3-GROUP_CONFIG_FAIL : Group change for interface [chars] Group [dec] failed
Explanation Group change for interface has failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_APS-3-CONFIG_FAIL : config change for interface [chars] Group [dec] failed
Explanation config for an interface to forwarding plane has failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_APS-3-FLOWIDDELETIONFAILED : Deletion of APS flow ID with manager failed for interface [chars] group [dec]
Explanation An unexpected condition has occurred that deletion of APS flow ID.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show interface command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_APS-3-FLOWIDALLOCFAILED : Allocation of APS flow ID with manager failed for interface [chars] group [dec]
Explanation An unexpected condition has occurred that allocation of APS flow ID. failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show interface command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_APS-3-PAIR_CONFIG_FAIL : Pair config for interface [chars] Group [dec] failed
Explanation Pair config for interface has failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_APS-3-CCCONFIGFAILED : Pair config for interface [chars] Group [dec] failed
Explanation Pair config for interface has failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_APS-3-FLOWCONFIGTOCCFAILED : Flow id to cc for interface [chars] Group [dec] failed
Explanation Flow id to cc for an interface has failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_APS-3-DOWNLOADFAIL : Unable to download [chars] message to [chars]
Explanation An unexpected condition has occurred which resulted in a configuration not being sent to the reported process.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


IOSXE_CXSC

%IOSXE_CXSC-3-ALLOC : Failed to allocate message for proposition
Explanation When attempting to program the dataplane with a CXSC proposition object, there was no enough memory to allocate the message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_CXSC-3-MESSAGE : Failed to send message for proposition
Explanation When the proposition was being prepared for sending to the data plane, there was an error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_CXSC-3-ACTION : Unknown proposition action ([dec])
Explanation When the proposition was being sent to the data plane, the action was unknown error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_CXSC-3-BAD_PROPOSITION : Proposition obj corrupt
Explanation When the proposition was being sent to the data plane, the object itself is corrupt.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_CXSC-3-BAD_SUMMARY : Summary obj corrupt
Explanation When the proposition summary was being sent to the data plane, the object itself is corrupt.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_CXSC-4-DUAL_RP_UNSUPPORTED : Dual RPs are not supported in conjunction with CXSC
Explanation CXSC is not supported in a dual RP environment. To resolve this warning, either unconfigure CXSC or remove the redundant Route Processor.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_CXSC-3-RF_INIT : Failed to initialize CXSC Redundancy Facility client
Explanation An unexpected condition occurred where the CXSC Redundancy Facility failed to initialize.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_CXSC-3-STILE_ACTIVATE : Failed to activate NBAR classification: ([dec])
Explanation An unexpected condition occurred where the CXSC NBAR protocol classification failed to activate.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_CXSC-3-STATISTICS_ALLOCATION : Unable to allocate space for statistics
Explanation During initialization, there was failure in the allocation of the memory to gather the statistics. It is non fatal, but after seeing this message, the CXSC subsystem will not be able to gather statistics.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_CXSC-3-BAD_PROTOCOLPACK : Invalid Protocol Pack object
Explanation When the Protocol Pack was being sent to the data plane, the object's contents were invalid.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_CXSC-3-FILESYSTEM_ERR : FileSystem Error ([chars]): Unable to Copy File from [chars] to [chars]
Explanation Unable to copy the NBAR Protocol Pack File to the file system for subsequent loading. The system will revert to the previously loaded Protocol Pack.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_CXSC-3-INSUFFICIENT_ALLOC_IOSXE_VER : Insufficent memory allocated for IOSXE version String
Explanation The input IOSXE Version String has insufficient memory to hold the IOSXE Version.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_CXSC-3-INSUFFICIENT_ALLOC_NBAR_VER : Insufficent memory allocated for NBAR Engine Version String
Explanation The input NBAR Engine Version string has insufficient memory to hold the NBAR Engine Version.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_CXSC-3-PLATFORM_TYPE : Unrecognised platform type. CPU ID [dec]
Explanation The platform that the cxsc service is being installed on is not recognised. The most likely cause is that this platform is not supported.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


IOSXE_ETHERCHAN

%IOSXE_ETHERCHAN-6-LINK_MTU : Interface [chars] MTU set to port-channel [chars] MTU [dec]
Explanation The MTU for the interface mentioned in the message is changed to match the MTU configured on the port channel interface
Recommended Action No action is required.


%IOSXE_ETHERCHAN-3-LINK_MTU_FAIL : Failure in changing MTU of interface [chars] to port-channel [chars] MTU
Explanation The MTU for the interface mentioned in the message cannot be changed to match the MTU configured on the port channel interface
Recommended Action Remove the link mentioned in the message from the port-channel group


IOSXE_EZMENU

%IOSXE_EZMENU-3-VIRT_SRVC_REGISTER : Failed to register '[chars]' with virtual service manager
Explanation An unexpected error has occured while trying to register this virtual service with the virtual service manager. This has prevented the virtual service from being enabled/disabled.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


IOSXE_FMANRP

%IOSXE_FMANRP-4-MSGDISPATCHNULL : TDL messages NULL from IOS.
Explanation An unexpected condition has occurred while IOS trying to dispatch the TDL message handler functions for received TDL messages from Forwarding Manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_FMANRP-4-MSGDISPATCH : Unable to dispatch received TDL message '[chars]' from Forwarding Manager. LUID: [chars]
Explanation An unexpected condition has occurred while IOS trying to dispatch the TDL message handler functions for received TDL messages from Forwarding Manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_FMANRP-4-MSGIPCERR : Unable to process received IPC messages from Forwarding Manager, error: [chars].
Explanation An unexpected condition has occurred while IOS trying to process received IPC message from Forwarding Manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_FMANRP-3-EPOCHTDLMSGMARSHAL : Failed to copy epoch TDL message to IPC buffer, epoch number [dec]
Explanation This operation to build a TDL messages for epoch message has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_FMANRP-3-MSGMARSHALERR : Unable to copy IPC messages into transport buffer. Message: [chars]
Explanation An unexpected condition has occurred while IOS trying to copy IPC message to transport buffer in order to send the message from IOSd to Forwarding Manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_FMANRP-3-MSGENQERR : Unable to enqueue IPC messages to IOS IPC queue. Message: [chars].
Explanation An unexpected condition has occurred while IOS trying to enqueue IPC message to IOS IPC queue in order to send the message to Forwarding Manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_FMANRP-4-MSGNONTDLSTATSERR : Unable to process received non-TDL stats message from Forwarding Manager, error: [chars] ([dec]).
Explanation An unexpected condition has occurred while IOS trying to process received non-TDL stats message from Forwarding Manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


IOSXE_FMANRP_ADJ through IOSXE_INFRA

IOSXE_FMANRP_ADJ

%IOSXE_FMANRP_ADJ-3-NOADJ : Adjacency entry is null
Explanation An unexpected condition has occurred which is due to the absence of an adjacency entry structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show adjacency command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_FMANRP_ADJ-3-NOFIBHWIDB : FIB Interface [chars] is null
Explanation An unexpected condition has occurred which is due to the absence of a FIB interface structure.
Recommended Action LOG_STD_SH_CMD_ACTION(show adj)


%IOSXE_FMANRP_ADJ-3-ENQUEFAIL : Unable to send [chars] [chars] message to Forwarding Manager Process
Explanation An unexpected condition has occurred which resulted in a configuration not being sent to the Forwarding Manager Processs.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_FMANRP_ADJ-3-ENCSIZE : Invalid encap length [dec] which is larger than max allowed [dec] bytes
Explanation An unexpected condition has occurred which is due to invalid adjacency encapsulation size being larger than the maximum value allowed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


IOSXE_FMANRP_CCE

%IOSXE_FMANRP_CCE-4-CCE_STACK_LIMIT : Failed to create class [dec] filter list
Explanation An operation to send a filter list to the forwarding processor for a particular class has failed due to a resource issue. This may imply that the notification was dropped.
Recommended Action LOG_STD_SH_CMD_ACTION(show class-map [type <class type> <name>])


%IOSXE_FMANRP_CCE-3-CCE_INVALID_FILTER_RELN : Invalid filter relation [int]
Explanation An internal error occured when trying to build class-map information for one of the classes in a policy-map.
Recommended Action LOG_STD_SH_CMD_ACTION(show policy-map [type <policy type> <name>])


%IOSXE_FMANRP_CCE-3-CCE_FILTER_OVERFLOW : Filter list overflow at type [chars]
Explanation An internal error occured when trying to build class-map information for one of the classes in a policy-map.
Recommended Action LOG_STD_SH_CMD_ACTION(show class-map [type <class type> <name>])


%IOSXE_FMANRP_CCE-3-CCE_CLASS_CREATE : Unable to create class [int].[int]
Explanation An error occured when trying to create a class-map.
Recommended Action LOG_STD_SH_CMD_ACTION(show policy-map [type <policy type> <name>])


%IOSXE_FMANRP_CCE-4-CCE_NESTED_CLASS_LIMIT : Nested class [dec] layers cannot exceed 4
Explanation When configure nested classes as match statements, the total levels of nested classes cannot exceed 4 layers
Recommended Action LOG_STD_SH_CMD_ACTION(show class-map [type <class type> <name>])


IOSXE_FMANRP_CEF

%IOSXE_FMANRP_CEF-3-NOFIB : FIB entry is null
Explanation An unexpected condition has occurred which is due to the absence of a FIB entry structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show ip cef command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_FMANRP_CEF-3-NOFIBSB : FIB SB entry is null
Explanation An unexpected condition has occurred which is due to the absence of a FIB SB entry structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show ip cef command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_FMANRP_CEF-3-NOFIBTABLE : FIB table is null
Explanation An unexpected condition has occurred which is due to the absence of a FIB table structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show ip cef command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_FMANRP_CEF-3-NOFIBIDB : FIB interface is null
Explanation An unexpected condition has occurred which is due to the absence of a FIB interface structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show ip cef command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_FMANRP_CEF-3-ENQUEFAIL : Unable to send [chars] [chars] message to Forwarding Manager Process
Explanation An unexpected condition has occurred which resulted in a configuration not being sent to the Forwarding Manager Processs.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_FMANRP_CEF-4-UPDFRAGSTATSERR : Update IP Fragmentation statistics error
Explanation An unexpected condition has occurred when updating fragmentation statistics
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_FMANRP_CEF-4-UPDREASSSTATSERR : Update IP Reassembly statistics error
Explanation An unexpected condition has occurred when updating reassembly statistics
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_FMANRP_CEF-4-UPDSTATSERR : Update CEF statistics error
Explanation An unexpected condition has occurred when updating cef statistics
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_FMANRP_CEF-3-ROUTEMSGMARSHAL : Failed to copy route essage to IPC buffer for prefix [chars]/[dec] - [chars]
Explanation This operation to build a TDL messages for route download has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_FMANRP_CEF-3-NOFIBPUSHCNT : FIB push counter is null
Explanation An unexpected condition has occurred which is due to the absence of a FIB push counter structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show ip cef command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_FMANRP_CEF-3-NONATADDR : NAT address is null
Explanation An unexpected condition has occurred which is due to the absence of an NAT address.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show ip alias command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


IOSXE_FMANRP_FPM

%IOSXE_FMANRP_FPM-4-INVALIDLENTYPE : Field length type in PHDF file is invalid
Explanation An unexpected condition has occurred which is due to the invalid field length type in PHDF file.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_FMANRP_FPM-4-INVALIDMATCHTYPE : FPM match type is invalid [dec]
Explanation An unexpected condition has occurred which is due to the invalid FPM match type in one of FPM class-map filter match entry
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_FMANRP_FPM-4-INVALIDACTION : FPM feature action is invalid [dec]
Explanation An unexpected condition has occurred which is due to the invalid action type when trying to bind FPM action with target class group.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_FMANRP_FPM-3-NOSTATUPDATE : Failed to update class-map statistics during periodic update
Explanation A statistics update for a class-map has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


IOSXE_FMANRP_OBJID

%IOSXE_FMANRP_OBJID-5-DUPCREATE : Duplicate forwarding object creation obj_handle [hex], type [int], existing obj_id [hex], type [int]
Explanation An unexpected condition has occurred which results in duplicate forwarding object creation.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


IOSXE_FMANRP_OBJID2

%IOSXE_FMANRP_OBJID2-3-DUPCREATE : Duplicate forwarding object creation obj_handle [hex], type [int], existing obj_id [hex], type [int]
Explanation An unexpected condition has occurred which results in duplicate forwarding object creation with different object types.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


IOSXE_FMANRP_RTMAP

%IOSXE_FMANRP_RTMAP-3-RTMAPNULL : The route-map structure for [chars] is null
Explanation An unexpected condition has occurred which is due to the absence of a route-map data structure.
Recommended Action show route-map


%IOSXE_FMANRP_RTMAP-4-UNKOWNCLIANT : Unknown client type [dec] received
Explanation An unexpected known client type is received for route-map download.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_FMANRP_RTMAP-3-INVALID_LIST : NULL
Explanation An internal list structure has been detected as invalid.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_FMANRP_RTMAP-3-RTMAP_UNSUPPORTED : Routemap ([chars]) contain unsupported match/set clause, ignored
Explanation A map contains unsupported match or set clause
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


IOSXE_FMANRP_URPF

%IOSXE_FMANRP_URPF-4-NOV4SWIDB : v4 sub-interface is null
Explanation An unexpected condition has occurred which is due to the absence of a v4 swidb structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show ip interface command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_FMANRP_URPF-4-NOV6SWIDB : v6 sub-interface is null
Explanation An unexpected condition has occurred which is due to the absence of a v6 swidb structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show ipv6 interface command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_FMANRP_URPF-3-INVALIDIFHDL : Invalid interface handle [int] for interface (number= [int], swidb= [hex], name= [chars])
Explanation An unexpected condition has occurred which is due to an invalid interface handle
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_FMANRP_URPF-4-UPDV4STATSERR : Update v4 URPF statistics error
Explanation An unexpected condition has occurred when updating v4 URPF statistics
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show ip interface <name> command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_FMANRP_URPF-4-UPDV6STATSERR : Update v6 URPF statistics error
Explanation An unexpected condition has occurred when updating v6 URPF statistics
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show ipv6 interface <name> command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


IOSXE_FMANRP_ZONES

%IOSXE_FMANRP_ZONES-3-NOSTATUPDATE : Failed to update zone-pair statistics during periodic update (zone [chars], class [int])
Explanation A statistics update for a zone-pair has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


IOSXE_INFRA

%IOSXE_INFRA-3-INVALID_ERRMSG : Error message type [dec] not defined
Explanation Error message type used is not defined in IOSXE infrastruction
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_INFRA-3-SHIM_INIT_WQ_FAIL : IOSXE shim layer initialization failed: Can not create receiving queues
Explanation IOSXE IOS shim layer initialization of watched queue failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_INFRA-3-SHIM_INIT_WQ_CHASFS_FAIL : IOSXE shim layer initialization failed: Can not create receiving chasfs watched queue
Explanation IOSXE IOS shim layer initialization of watched queue failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_INFRA-3-SHIM_INIT_PROC_FAIL : IOSXE shim layer initialization failed: Dispatch process creation failed
Explanation IOSXE IOS shim layer initialization creating dispatch process failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_INFRA-3-SHIM_INIT_MEM_FAIL : IOSXE shim layer initialization failed: Memory initialization failed.
Explanation IOSXE IOS shim layer initialization of memory failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_INFRA-3-SHIM_NO_IPC_DISPATCH_HDL : IOSXE shim layer [chars] process message without IPC dispatch handler.
Explanation IOSXE IOS shim layer has no ipc dispatch handler set
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_INFRA-3-SHIM_RXMSG_NO_IPC_HDL : IOSXE shim layer without IPC handler for fd [dec], seqnum [dec].
Explanation IOSXE IOS shim layer cannot find ipc handler
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_INFRA-3-SHIM_INIT_TDL_FAIL : IOSXE shim layer initialization TDL Lib [chars] failed.
Explanation IOSXE IOS shim layer initialization of TDL library
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_INFRA-3-SHIM_INIT_DISPATCH_INIT_FAIL : IOSXE shim layer initialization, dispatch path init failed.
Explanation IOSXE IOS shim layer initialization of TDL disatch path
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_INFRA-3-INVALID_RUNTIME_IDX : Thread runtime index [dec] is not valid
Explanation Export the thread's running time failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_INFRA-6-THEAD_SELECT_ERR : Inbound message or packet select error, [chars].
Explanation Socket select operation error in threads
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_INFRA-3-INJECT_HDR_LENGTH_ERR : Inject hdr size [int] exceeds limit
Explanation Inject header length exceeds pak header space
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_INFRA-3-INJECT_EMBEDDED_HDR_LENGTH_ERR : Can't allot space needed for embedded inject hdr size [int] exceeds limit
Explanation Can't allot space needed for embedded inject header, exceeds pak header space
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_INFRA-3-INJECT_NO_IF_OUTPUT_ERR : Output intf is NULL, [chars]
Explanation Output intf is requred to proceed, else skip the feautre
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_INFRA-4-PUNT_KEEPALIVE_LOG_ERR_INV_PARAM : Invalid parameter: [chars]
Explanation Invalid parameter was passed when generating punt err log
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_INFRA-4-PUNT_KEEPALIVE_LOG_ERR_GET_FILE_NAME : Failed to get file name: [chars]
Explanation Could not form a file name when generating punt err logPunt keepalive log error seen
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_INFRA-4-PUNT_KEEPALIVE_LOG_ERR_INV_FILE_ID : Invalid file descriptor: [dec]
Explanation Invalid file descriptor was found when generating punt err log
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_INFRA-3-PUNT_KEEPALIVE_LOG_ERR_OPEN_FILE : Failed to open file: [chars]
Explanation Failed to open file when generating punt err log
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_INFRA-4-PUNT_KEEPALIVE_LOG_ERR_CLOSE_FILE : Failed to close file with descriptor: [dec]
Explanation Closing of file failed when generating punt err log
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_INFRA-3-PUNT_KEEPALIVE_LOG_ERR_WRITE_TO_FILE : Write to file Id [dec] failed [dec] bytes, expected [dec] bytes
Explanation Write to file failed when generating punt err log
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_INFRA-3-PUNT_KEEPALIVE_LOG_ERR_ALLOC_TTY : Failed to allocate a tty
Explanation Can't allocate a TTY when generating punt err log
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_INFRA-3-PUNT_KEEPALIVE_LOG_ERR_ALLOC_CSB : Failed to allocate a csb
Explanation Can't allocate a csb when generating punt err log
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_INFRA-3-PUNT_KEEPALIVE_LOG_ERR_PARSE_CMD : Failed to parse command: [chars]
Explanation Failed to parse a command when generating punt err log
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_INFRA-4-PUNT_KEEPALIVE_LOG_ERR_GET_PROCID : Failed to get process id
Explanation Can't get identifier of the process generating punt err log
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_INFRA-4-PUNT_KEEPALIVE_LOG_ERR_INV_PROCID : Invalid proc id [dec], expected [dec]
Explanation Invalid process trying to generate punt err log
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_INFRA-4-NO_PUNT_KEEPALIVE : Keepalive not received for [int] seconds
Explanation Punt Inject keepalive message was not received
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_INFRA-2-FATAL_NO_PUNT_KEEPALIVE : Keepalive not received for [int] seconds resetting
Explanation Punt Inject keepalive message was not received
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_INFRA-3-INJECT_GSB_CTL_INIT_FAIL : Inject adjacency subblock init failed
Explanation Adj subblock control or register failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_INFRA-3-PUNT_ADDR_RES_ENCAP_ERR : Punted address resolution packet with unknown encap [chars]
Explanation Punted packet for ARP/ND with encap not supported
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_INFRA-3-PUNT_SVC_PROC_ERR : Punt service [chars] create failed
Explanation Punt service process can not be created
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_INFRA-3-VM_PAGE_TABLE_ERR : VM guarded page operation failed, address [hex], [chars]
Explanation VM guarded page avl tree operation error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_INFRA-3-PUNT_SVC_TYPE_UNKNOWN : Punted packet with unknown service type [int]
Explanation Punted pak with an unsupported service type
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_INFRA-5-PUNT_SVC_CANT_ENQUEUE : Punted pak can't be enqueued for service
Explanation Punted pak enqueue failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_INFRA-5-PUNT_SVC_INVALID_OPT_PKT : Invalid IPv4 options packet punted to RP
Explanation Invalid IPv4 options packet dropped in RP
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_INFRA-4-INJECT_TUN_NONIP_WARN : pak with linktype [chars] gets into non-ip tunnel
Explanation IP/IPv6/MPLS packet should to go through GRE tunnel for non-IP payload
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_INFRA-3-INJECT_FEATURE_ESS_ERR : ESS segment not found, type [dec] hdl [hex]
Explanation Packets to be injected to an unsupported ESS segment
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_INFRA-6-PROCPATH_CLIENT_HOG : IOS shim client '[chars]' has taken %ld msec (runtime: %ld msec) to process a '[chars]' message
Explanation The specified IOSXE IOS shim client has taken too long to process a received IPC or chasfs message
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_INFRA-6-AUXTHD_REQUEST : Too many outstanding requests for file system access
Explanation Resource temporarily unavailable
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_INFRA-3-APP_SESS_OPEN_FAILED : An attempt to open [chars] with handle number [dec] has failed ([dec])
Explanation Application session between processes failed to estabish.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_INFRA-3-CONSOLE_DBUG_DROP : System dropped [dec] bytes of console debug messages.
Explanation Debugging messages are being generated faster than they can be displayed on the console. The messages can not be guaranteed to be seen so this message replaces the lost messages.
Recommended Action Consider using conditional debugging or turning off console logging.


%IOSXE_INFRA-3-PUNT_INCOMP_WRONG_ADJID : Punted address resolution packet linktype [chars], adj-id [dec] is with linktype [chars]
Explanation CPP needs to punt incomplete adjacency for resolution by specifying the adjacency-id, but the included adjacency-id does not match the incomplete adjacency this packet triggered.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_INFRA-3-IFS_EXTLINK_ADD_FAIL : Could not add filesystem [chars] to IFS links
Explanation Attempt to add filesystem root to allow for links failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_INFRA-3-IFS_UDEV_REMOVE_FAIL : Could not remove udev device [chars]
Explanation Attempt to remove udev device failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_INFRA-3-IFS_DFLT_FS_REG_FAIL : Unable to set [chars] as a default file system.
Explanation IOSXE's platform dependent code failed to register the default file system.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_INFRA-3-IFS_INIT_HIDDEN_FAIL : IOSXE shim layer initialization failed: Can not create receiving queues
Explanation IOSXE IOS shim layer initialization of hidden path watch failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_INFRA-3-BSO_MSG_HDR_LENGTH_ERR : BSO message header length [int] is incorrect
Explanation BSO message header length is incorrect
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_INFRA-3-BSO_MSG_HDR_MSGTYPE_ERR : BSO message header msgtype [int] is incorrect
Explanation BSO message header msgtype is incorrect
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_INFRA-3-BSO_MSG_UNMARSHAL_ERR : BSO message unmarshalling has failed
Explanation BSO message unmarshalling has failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_INFRA-3-BSO_MSG_CACHE_ERR : BSO message query cache update error - [chars]
Explanation BSO message query cache update error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_INFRA-4-BSO_MSG_RIB_WATCH_WARN : BSO message RIB watch start error
Explanation BSO message RIB watch start error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_INFRA-3-RELOAD_INFO_SAVE_FAIL : Unable to save reload information: [dec]: [chars].
Explanation IOSXE's platform dependent code failed to save the reload information.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_INFRA-3-SN_IPFRR_PROC_ERR : Static Nexthop IPFRR [chars] create failed
Explanation SN IPFRR process can not be created
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_INFRA-6-CONSOLE_ACTIVE : [chars]
Explanation Indicates that the current instance of IOS is assuming active control of the console. This is informational.
Recommended Action No action is required.


%IOSXE_INFRA-6-PLATFORM_RELOAD : [chars]
Explanation Indicates that the current instance of IOS is being reset by the platform code. This is part of a normal reset sequence and the message is informational.
Recommended Action No action is required.


%IOSXE_INFRA-6-CHASFS_CLOCK_SET_FAIL : Failed to set Chasfs property on system time change
Explanation Unable to set chasfs property on system time change
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_INFRA-3-CYAN_API_ERROR : Failed to retrieve platform dependent value of [chars] (err=[dec])
Explanation CYAN API function failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_INFRA-6-SHIM_RXMSG_IPC_INFO : IOS shim layer process IPC msg for fd [dec], seq_num [dec], ipc_status [dec]
Explanation
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_INFRA-3-SHIM_IPC_NOT_PROCESSED : msg handler returned FALSE for IPC msg for fd [dec], seq_num [dec], service [chars]
Explanation
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_INFRA-3-SWIFT_ORCH_PROC_FAIL : IOSXE SWIFT Orchestrator process creation failed
Explanation The SWIFT Orchestrator process could not be created
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_INFRA-3-BAD_GLIBC_BUF_FREE : An IOS buffer is freed into GLIBC buffer pool, buffer blockmagic [hex], flags [hex]
Explanation An IOS buffer is freed into GLIBC buffer pool.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_INFRA-3-BIPC_MGS_ALLOC_FAIL : Allocating [dec] byte for IPC [chars] msg failed: out of memory
Explanation system is out of memory
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


IOSXE_MEMPOOL_MIB through IOSXE_RP_IF_FLOW_IDS

IOSXE_MEMPOOL_MIB

%IOSXE_MEMPOOL_MIB-3-BUFFPOOL_REG_ERROR : Bufferpool register data exceeds allocated memory; Retrieved only [dec] entries.
Explanation Memory allocated is not enough
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


IOSXE_MGMTVRF

%IOSXE_MGMTVRF-3-PROCESS_CREATE_FAIL : Management VRF process creation failed, [chars]
Explanation Can not create IOS process for mgmt port init
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_MGMTVRF-3-VRF_CREATE_FAIL : Management VRF creation failed [chars]
Explanation Can not create mgmt vrf during system init
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_MGMTVRF-3-AFI_ATTACH_FAIL : Management VRF AFI [chars] attach failed
Explanation Can not create afi subblock for mgmt vrf
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_MGMTVRF-3-INTF_ATTACH_FAIL : Management VRF attach to mgmt [chars] failed
Explanation Can not associate mgmt port to mgmt vrf
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_MGMTVRF-3-SET_TABLEID_FAIL : Installing [chars] Management interface tableid [hex] failed
Explanation Fail to set mgmt port tableid into Linux kernel
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_MGMTVRF-6-CREATE_SUCCESS_INFO : Management vrf [chars] created with ID [dec], ipv4 table-id [hex], ipv6 table-id [hex]
Explanation mgmt vrf and ipv4, ipv6 tables created for mgmt port
Recommended Action


IOSXE_MLP

%IOSXE_MLP-3-ENQUEFAIL : Unable to send [chars] [chars] message to Forwarding Manager Process
Explanation An unexpected condition has occurred which resulted in a configuration not being sent to the Forwarding Manager Processs.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_MLP-4-UPDSTATSERR : Update MLP statistics error
Explanation An unexpected condition has occurred when updating mlp statistics
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_MLP-2-DB_ENTRY_ALLOC_FAIL : MLP link db entry allocation for link [chars] failed
Explanation MLP link database error. Memory chunk allocation for MLP link database entry has failed.
Recommended Action Check for accurate memory management. Perform memory leak checks and look for memory corruption causes. Execute 'show proc memory' command.


%IOSXE_MLP-2-DB_INSERT_FAIL : MLP link db entry add for interface [chars] failed
Explanation MLP link database error. Insertion of a new entry into MLP link database has failed.
Recommended Action Check for accurate memory management. Perform memory leak checks, look for memory corruption causes, verify correct database management. Execute 'show proc memory' command.


%IOSXE_MLP-2-DB_DELETE_FAIL : MLP link db entry delete for link [chars] failed
Explanation MLP link database error. Removal of entry from MLP link database has failed.
Recommended Action Check for accurate memory management. Perform memory leak checks, look for mamory corruption causes and check for correct database management. Execute 'show proc memory' command.


%IOSXE_MLP-2-DB_ENTRY_FREE_FAIL : MLP link entry free failed
Explanation MLP link database error. Memory chunk free of MLP link database entry has failed.
Recommended Action Check for accurate memory management. Perform memory leak checks and look for memory corruption causes. Execute 'show proc memory' command.


%IOSXE_MLP-2-DB_ALLOC_FAIL : MLP link db allocation failed
Explanation MLP link database error. Memory chunk creation for MLP link database has failed.
Recommended Action Check for accurate memory management. Perform memory leak checks and look for memory corruption causes. Execute 'show proc memory' command.


%IOSXE_MLP-2-DB_DESTROY_FAIL : MLP link database destroy failed
Explanation MLP link database error. Memory chunk destroy has failed for MLP link database.
Recommended Action Check for accurate memory management. Perform memory leak checks and look for memory corruption causes. Execute show proc memory command.


IOSXE_OIR

%IOSXE_OIR-6-INSCARD : Card ([chars]) inserted in [chars]slot [chars]
Explanation The OIR facility detected the insertion of a card in the slot number specified in the message.
Recommended Action No action is required.


%IOSXE_OIR-6-REMCARD : Card ([chars]) removed from [chars]slot [chars]
Explanation The OIR facility detected the removal of a card from the slot number specified in the message.
Recommended Action No action is required.


%IOSXE_OIR-6-ONLINECARD : Card ([chars]) online in [chars]slot [chars]
Explanation The OIR facility detected the state change to online for the card in the slot number specified in the message.
Recommended Action No action is required.


%IOSXE_OIR-6-OFFLINECARD : Card ([chars]) offline in [chars]slot [chars]
Explanation The OIR facility detected the state change to offline for the card in the slot number specified in the message.
Recommended Action No action is required.


%IOSXE_OIR-3-CARDERR : Could not read state property for [chars] slot [dec]
Explanation The OIR facility detected a failure for exceeding the number of retries to find state chasfs property.
Recommended Action No action is required.


%IOSXE_OIR-6-SOFT_STARTSPA : SPA([chars]) restarted in [chars]
Explanation The SPA in the specified subslot is restarted by the command hw-module subslot slot#/subslot# start
Recommended Action No action is required.


%IOSXE_OIR-3-SPA_INTF_ID_ALLOC_FAILED : Failed to allocate interface identifiers for SPA([chars]) in slot/bay: [int]/[int]
Explanation Failed to get CC buffer and flow control identifiers for the SPA in the specified subslot Traffic cannot flow through the SPA under this failure condition. This can happen if the system runs out of available identifiers.
Recommended Action Try to reduce the number of interfaces configured in the system either by physically removing the SPAs or by changing the system configuration


%IOSXE_OIR-6-SOFT_STOPSPA : SPA([chars]) stopped in [chars], interfaces disabled
Explanation The SPA in the specified subslot is stopped by the command hw-module subslot slot#/subslot# stop The interfaces on that processor will be administratively shut down and marked as removed. The routing table will be flushed of any routes through the removed interfaces.
Recommended Action No action is required.


%IOSXE_OIR-6-SOFT_RELOADSPA : SPA([chars]) reloaded on [chars]
Explanation The SPA in the specified subslot is reloaded by the command hw-module subslot slot#/subslot# reload
Recommended Action No action is required.


%IOSXE_OIR-6-SYNCSPA : SPA ([chars]) reloading to come up in [chars] mode
Explanation The SPA in the specified subslot is reloaded by the command hw-module subslot slot#/subslot# reload
Recommended Action No action is required.


%IOSXE_OIR-6-INSSPA : SPA inserted in [chars]/[int]
Explanation The OIR facility detected the insertion of a SPA in the subslot number specified in the message.
Recommended Action No action is required.


%IOSXE_OIR-6-REMSPA : SPA removed from [chars]/[int], interfaces disabled
Explanation The OIR facility detected the removal of a SPA from the subslot number specified in the message. The interfaces on that processor will be administratively shut down and marked as removed. The routing table will be flushed of any routes through the removed interfaces.
Recommended Action No action is required.


%IOSXE_OIR-6-INSSSFP : Smart SFP inserted in port [chars]
Explanation The OIR facility detected the insertion of TSoP/VCoP SSFP in the port number specified in the message.
Recommended Action No action is required.


%IOSXE_OIR-6-REMSSFP : Smart SFP removed from port [chars]
Explanation The OIR facility detected the removal of TSoP/VCoP SSFP in the port number specified in the message.
Recommended Action No action is required.


%IOSXE_OIR-6-SPARELOAD : SPA reloaded on subslot [int]/[int]
Explanation The SPA in the specified subslot is reloaded.
Recommended Action No action is required.


%IOSXE_OIR-6-CARDRECONCILE : SPA type changed on subslot [int]/[int] from [int] to [int]
Explanation The SPA in the specified subslot has been initialized, and it has been detected that it is of a different type to the SPA that was previously in this subslot.
Recommended Action No action is required.


%IOSXE_OIR-3-OIRTWICE : Subslot [int]/[int] OIR insertion/removal not paired up: [chars]
Explanation An internal OIR-related error occured for the specified SPA.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_OIR-3-QUIESCE_FAIL : Quiesce failed for subslot [int]/[int] (error = [dec])
Explanation The RP failed to contact the SPA during failover. The SPA will be reset.
Recommended Action No action is required.


%IOSXE_OIR-3-UNQUIESCE_FAIL : Unquiesce failed for subslot [int]/[int] (error = [dec])
Explanation The RP failed to unquiesce the SPA in the specified subslot. The SPA will be reset.
Recommended Action No action is required.


%IOSXE_OIR-3-POWER_CYCLE_IMMINENT : The SPA in subslot [int]/[int] will be power cycled in [dec] seconds.
Explanation The SPA in the specified subslot will be power cycled in the amount of time specified in the error message.
Recommended Action No action is required.


%IOSXE_OIR-3-PROCMSG : Process msg send failed for process[dec]
Explanation Process message send failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_OIR-3-MODULE : Missing [chars] for [chars]
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_OIR-3-SPA_MDR_FAIL : Minimal Disruptive Restart process failed for SPA in subslot [int]/[int], reason [chars].
Explanation The SPA in the subslot failed Minimal Disruptive Restart. Minimal Disruptive Restart process is aborted and an attempt will be made to recover the SPA by resetting the SPA hardware.
Recommended Action No action is required.


IOSXE_PEM

%IOSXE_PEM-6-INSPEM_FM : PEM/FM [chars] inserted
Explanation The platform detected the insertion of a power/fan module in the slot number specified in the message.
Recommended Action No action is required.


%IOSXE_PEM-6-REMPEM_FM : PEM/FM [chars] removed
Explanation The platform detected the removal of a power/fan module in the slot number specified in the message.
Recommended Action No action is required.


%IOSXE_PEM-6-PEMOK : The PEM in [chars] is functioning properly
Explanation The PEM hardware may have been either switched off, or reporting a failure condition. This message indicates that the PEM is no longer either switched off, or reporting a failure
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_PEM-3-PEMFAIL : The PEM in [chars] is switched off or encountering a failure condition.
Explanation The PEM hardware has been either switched off, or is reporting a failure condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_PEM-6-FANOK : The fan in [chars]/[dec] is functioning properly
Explanation The fan was reporting a failure condition. This message indicates that the fan is no longer reporting a failure
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_PEM-3-FANFAIL : The fan in [chars]/[dec] is encountering a failure condition
Explanation The fan's hardware is reporting that the fan is failing. This is most likely because the hardware detects the fan as spinning below the minimum speed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_PEM-3-PEMCHASFSERR : The PEM in [chars] has encountered a system software error.
Explanation The PEM's underlying software for storing PEM state is not working properly.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_PEM-3-TEMPERATURE_RAISE : Sensor [chars] has reached maximum temeprature value, Leads to shutdown the system
Explanation The Temperature sensor reaching maximum threshold value working properly.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_PEM-3-FAN_FAIL_SHUTDOWN : More thatn one [chars] has failed, Leads to shutdown the system
Explanation The Temperature sensor reaching maximum threshold value working properly.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_PEM-3-SSFP_TEMPERATURE_RAISE : [chars] transceiver temeprature reached threshold value, Leads to shutdown the system
Explanation The Temperature sensor reaching maximum threshold value working properly.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_PEM-3-PEMREDLOWSTANDBY : Cannot activate [chars] configuration. Total power budget of standby power supplies is [dec]W. Standby power must be greater than or equal to the largest power supply capacity ([dec]W).
Explanation Operating in unprotected mode Should insert at least one ps in standby slots with a capacity greater than or equal to the largest capacity power supply in the system. The configuration will be applied automatically once requirements are met.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_PEM-3-PEMREDNOPWR : Cannot enable power redundancy mode [chars] because config would create mode with insufficient [chars] power
Explanation Configuration set by user is not valid as power supplies in the active slots do not contain enough power to meet the power requirements
Recommended Action Insert additional power supplies and configure them to be active or configure current standby power supplies to active such that power requirements are met


IOSXE_QFP

%IOSXE_QFP-2-LOAD_EXCEED : Slot: [int], QFP:[int], Load [int]%[hex]ceeds the setting threshold.
Explanation QFP Load exceeds setting threshold.
Recommended Action Monitor the traffic load.


%IOSXE_QFP-2-LOAD_RECOVER : Slot: [int], QFP:[int], Load [int]%% recovered.
Explanation QFP Load recovered.
Recommended Action No action required (normal operation).


IOSXE_RP_ALARM

%IOSXE_RP_ALARM-6-INFO : [chars] [chars] [chars]: [chars] [chars]
Explanation
Recommended Action


%IOSXE_RP_ALARM-6-INFO : [chars] [chars] [chars] [chars] [chars]
Explanation Alarm assertion or deassertion information.
Recommended Action No action is required.


%IOSXE_RP_ALARM-2-PEM : [chars] [chars] [chars]: [chars] [chars]
Explanation
Recommended Action


%IOSXE_RP_ALARM-2-PEM : [chars] [chars] [chars] [chars] [chars]
Explanation Power Entity Module missing information
Recommended Action No action is required.


%IOSXE_RP_ALARM-2-ESP : [chars] [chars] [chars]: [chars] [chars]
Explanation
Recommended Action


%IOSXE_RP_ALARM-2-ESP : [chars] [chars] [chars] [chars] [chars]
Explanation No ESP running alarm information
Recommended Action No action is required.


IOSXE_RP_CFG_NOT

%IOSXE_RP_CFG_NOT-3-MSGNOCAND : Can not construct a candidate entry for configuration export
Explanation This error usually indicates either an out of memory condition or a TDL error. If ample memory is available, then the the TDL error may indicate a version conflict with respect to configuration.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_CFG_NOT-3-MSGNOPWARR : Can not construct an array for configuration export
Explanation This error usually indicates either an out of memory condition or a TDL error. If ample memory is available, then the the TDL error may indicate a version conflict with respect to configuration.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_CFG_NOT-3-MSGNOUPDATEMSG : Can not construct an update message for configuration export
Explanation This error usually indicates either an out of memory condition or a TDL error. If ample memory is available, then the the TDL error may indicate a version conflict with respect to configuration.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_CFG_NOT-3-MSGNOREPLMSG : Can not construct a replace message for configuration export
Explanation This error usually indicates either an out of memory condition or a TDL error. If ample memory is available, then the the TDL error may indicate a version conflict with respect to configuration.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_CFG_NOT-2-MSGNOEXP : Can not construct a '[chars]' message for configuration export: [chars]
Explanation This error usually indicates either an out of memory condition or a TDL error. If ample memory is available, then the the TDL error may indicate a version conflict with respect to configuration.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_CFG_NOT-2-MSGTDLINITERROR : Configuration Notification messaging module initialization failed: Unable to initialize messaging: [chars]
Explanation The Configuration Notification subsystem has failed to initialize the infrastructure for messaging with the Pluggable Services Daemon. Notification of configuration to critical modules cannot proceed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_CFG_NOT-2-MSGTDLERROR : Error processing TDL message. [dec]
Explanation An unexpected condition in which IOS has received a TDL message which it can not process.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_CFG_NOT-2-MSGIPCINITERROR : Error initializing IPC queue
Explanation An unexpected condition in which IOS could not initialize a message queue to the PSD.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_CFG_NOT-3-MSGIPCTXERROR : IPC transmit error. [dec]
Explanation An unexpected condition in which IOS encountered an error trying to send a message to another process. %d
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_CFG_NOT-3-MSGOBJNULL : An unexpected condition in which IOS has received a null pointer that it expects to be non-null.
Explanation An unexpected condition has occurred while IOS is trying to process a username command.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_CFG_NOT-3-MSGENCRYPTINVALID : The mcprp_cfg_notify subsystem has seen an encryption type it does not recognize. [dec]
Explanation An unexpected condition has occurred while IOS is trying to process a username command.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_CFG_NOT-3-NVWRITE_EXPORT : Failed to export [chars] notification: [dec]
Explanation When a 'write memory' or 'write erase' operation occurs, the Configuration Notification subsystem exports this event into the chassis file system. This message indicates that the export failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_CFG_NOT-3-MCP_DBPERSIST_STAT : Failed to read [chars] property: [dec]
Explanation When a 'reload' operation occurs, this chasfs property is read to determine the status of the DB persist/restore/delete operation. This message indicates that the read failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_CFG_NOT-3-MCP_DBPERSIST_ERROR : System configuration update could not complete
Explanation When a 'reload' operation occurs, this chasfs property is read to determine the status of the DB persist/restore/delete operation. This message indicates that the operation failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_CFG_NOT-3-MCP_FRU_LOCATION : Failed to get local FRU location: [dec]
Explanation Unable to get local FRU location
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_CFG_NOT-3-MCP_FRU_INVALID : Unknow FRU location: [chars]
Explanation Unknown FRU location
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_CFG_NOT-3-BOOT_VAR_NOT_SET : Boot variable either does not exist or buffer is too small. Keeping it blank.
Explanation Boot variable either does not exist or buffer is too small. Not able to set boot variable. Ignoring it.Aborting reload.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_CFG_NOT-3-BOOT_IMAGE_NOT_FOUND : Primary image is not found, the system is going to reload as per user request.
Explanation Primary image which is set in boot statement either does not exist or not found. Primary image is not found, it should prompt the user to see if they wish to proceed. Aborting reload.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_CFG_NOT-6-IOX_SERVICE_NOTSUPPORTED : IOx service not supported.
Explanation IOx service is not supported in this platform currently. This may be either due to the feature unavailability or due the current inadequate license level of the system.
Recommended Action


IOSXE_RP_DPIDB

%IOSXE_RP_DPIDB-3-IDXBADRANGE : Datapath IDB index [dec] is not in a valid range
Explanation An unexpected condition has occurred as the index of a datapath IDB is not valid.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show interface command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_DPIDB-3-IDXALLOCFAILED : Datapath IDB index allocation failed: [chars]
Explanation An unexpected condition has occurred as all the available of datapath IDB indices are used.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show interface command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_DPIDB-3-IDXINSERTFAILED : Insertion of datapath IDB index [dec] into database failed
Explanation An unexpected condition has occurred that insertion of datapath IDB indices failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show interface command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_DPIDB-3-IDXLOOKUPFAILED : Lookup of datapath IDB index from the database failed ([chars])
Explanation An unexpected condition has occurred that lookup of datapath IDB indices failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show interface command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_DPIDB-3-IDXDELETIONFAILED : Deletion of datapath IDB index from the database failed ([chars] - [hex]) rc [dec]
Explanation An unexpected condition has occurred that deletion of datapath IDB indices failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show interface command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_DPIDB-3-NOHWSUBBLOCK : HWIDB [chars] does not have a hardware subblock
Explanation An unexpected condition has occurred that no hardware subblock was previously allocated for a HWIDB.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show interface command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_DPIDB-3-NOSWSUBBLOCK : SWIDB [chars] does not have a software subblock
Explanation An unexpected condition has occurred that no software subblock was previously allocated for a SWIDB.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show interface command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_DPIDB-3-IDBBADTYPE : Datapath IDB type [dec] is not valid
Explanation An unexpected condition has occurred as the type of a datapath IDB is not valid.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show interface command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_DPIDB-3-IDBEXIST : Datapath IDB already exists in this mapping entry: [chars]-[dec]
Explanation An unexpected condition has occurred that an attempt is made to save datapath IDB in a mapping entry filled by another.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show interface command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_DPIDB-3-IDBNONEXIST : Datapath IDB does not exist in this mapping entry: [chars]-[dec]
Explanation Datapath IDB lookup points to empty mapping entry.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show interface command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_DPIDB-3-RF : Datapath IDB RF operation failed - [chars]
Explanation Failure in some datapath ID RF activity.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show interface command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_DPIDB-3-CF : Datapath IDB CF operation failed - [chars]
Explanation Failure in some datapath ID CF activity.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show interface command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_DPIDB-3-RPC : Datapath IDB RPC operation failed - [chars]
Explanation Failure in some datapath ID RPC activity.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show interface command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_DPIDB-3-REGISTRATION : ISSU [chars] failed for [chars]; [chars]
Explanation An ISSU registration for the set of initial capabilities and sessions failed due to the reason specified. This will have the effect of the DPIDX ISSU support being unavailable between peers.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_DPIDB-3-ISSU : [chars] [chars] failed; [chars]
Explanation An operation pertaining to the ISSU support for DPIDX failed to complete using either the CF or IPC transport context with the reason specified
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_DPIDB-3-TRANSFORM : [chars] of [chars] via [chars] failed for dpidx [int]
Explanation An attempt to either encode or decode a versioned synchronization message has failed due to an internal error encountered by the ISSU component.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_DPIDB-3-RECEIVE : Message via [chars] is [chars]
Explanation An attempt to receive and process a versioned negotiation or synchronization message has failed due to an internal error being detected by the information received from the IPC or CF components.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_DPIDB-3-TRANSMIT : Unable to send via [chars] [chars] [chars] [chars]; [chars]
Explanation An attempt to send a versioned negotiation or synchronization message has failed due to an internal error encountered by the IPC or CF components.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_DPIDB-3-NEGOTIATION : Failed to start ISSU [chars] session negotiation; [chars]
Explanation The ISSU negotiation with the peer failed to start for either the CF or IPC transport with the reason specified.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_DPIDB-6-READY : [chars] peer not ready, discarding [chars]
Explanation The synchronization attempt for the message has determined that the transport has lost communication with its peer. This is a normal situation which indicates that the standby route-processor is currently out of service implying a simplex redundancy mode.
Recommended Action


%IOSXE_RP_DPIDB-6-RELOAD : [chars], reloading [chars]
Explanation A synchronization attempt between the active and standby RP peers has failed with the reason indicated. The standby peer is reloaded in an attempt to resynchronize when operating in a stateful redundant mode.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_DPIDB-3-DECODE : Decode via [chars] of [chars] failed
Explanation A message of the transport and type described failed in its attempt to be decoded on the standby. The resultant action taken by the standby route processor is an attempt to resynchronize.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_DPIDB-3-PROGRESSION : Unable to inform RF of bulk sync completion; [chars]
Explanation The active route processor has sent a notification to the standby to inform of the completion of the bulk synchronization of the DPIDX configuration. The standby has failed to respond to the active informing that it received the notification noting the reason for the failure. The resultant action taken by the standby route processor is an attempt to resynchronize.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_DPIDB-3-BULK_SYNC : Failed to send [chars] information to peer
Explanation The bulk synchronization of the DPIDX configuration to the standby RP has failed to complete successfully; DPIDX has therefore taken the action which will result in a reload of the peer in order to once more attempt to successfully synchronize the configuration state which may have failed initially to a transient condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_DPIDB-3-DYN_SYNC : Failed to process [chars] dynamic state
Explanation The incremental synchronization of the DPIDX configuration to the standby RP has failed to complete successfully. This implies that the configuration state between the active and standby RP is inconsistent.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show interfaces command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_DPIDB-6-TIMEOUT : Bulk sync is flow controlled by [chars]
Explanation The bulk synchronization of the DPIDX configuration to the standby RP has encountered a flow control condition which has effected a timeout awaiting the condition to clear. This will result in a reload of the standby RP to allow the bulk synchronization to restart.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_DPIDB-3-IDBNOTVAI : Invalid API call for [chars]
Explanation Failure in an internal API
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show interface command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_DPIDB-3-NULLTIMER : NULL timer
Explanation A timer is NULL
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show interface command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_DPIDB-3-LIST : List [chars] failed for [chars]
Explanation List enqueue or removal failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show interface command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_DPIDB-3-FASTNOTIFY : Fast notify failed for [chars]
Explanation A fast notify message failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show interface command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_DPIDB-3-DOWNLOADFAIL : Unable to download [chars] message to [chars]
Explanation An unexpected condition has occurred which resulted in a configuration not being sent to the reported process.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_DPIDB-3-FRRLDFLOWIDDELETIONFAILED : Deletion of fast-reroute flow ID with manager failed
Explanation An unexpected condition has occurred that deletion of fast-reroute flow ID.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show interface command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_DPIDB-3-EFPSTATSFAILED : EFP stats message data get error: ([dec]) for EFP [int] on [chars]
Explanation An unexpected error occurred extracting fields from an EFP stats message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_DPIDB-3-MTU_ALLOC_FAIL : No hardware resources for [int] byte MTU on [chars]
Explanation We reached to the threshold of maximum supported unique MTU on this platform.
Recommended Action No action is required.


%IOSXE_RP_DPIDB-3-IP_MTU_ALLOC_FAIL : No hardware resources for [int] byte IP MTU on [chars]
Explanation We reached to the threshold of maximum supported unique IP MTU on this platform.
Recommended Action No action is required.


IOSXE_RP_IF_FLOW_IDS

%IOSXE_RP_IF_FLOW_IDS-3-NO_BUFF_FOR_SYNC : The Checkpoint Faclity reported the error [chars] during a request for a buffer length of [dec]. This [chars] CF client has failed to synchronize a transaction to the Standby RP.
Explanation This error indicates that the buffer management within the Checkpoint Facility has either run out of buffers, or has some other problem. If this occurs during Bulk Sync then Bulk Sync will terminate without completing. Otherwise the incremental Sync will fail.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_IF_FLOW_IDS-3-BUFF_OFFSET_NULL : Unable to utilize the memory buffer provided by the Checkpoint Facility. This [chars] CF client has failed to Bulk Sync.
Explanation This error indicates the Checkpoint Facility is having problems recognizing its own buffer layout. If this occurs during Bulk Sync then Bulk Sync will terminate without completing. Otherwise the incremental Sync will fail.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_IF_FLOW_IDS-3-CF_SEND_BULK_NONBLOCKED : The Checkpoint Facility reported the error [chars] while attempting to send a message. Bulk Sync of this [chars] CF client is terminating.
Explanation This error indicates the Checkpoint Facility has internal problems related to IPC, and cannot perform a non-blocked send operation.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_IF_FLOW_IDS-3-DEFERRED_DURING_BULK_SYNC : Encountered error [chars] while trying to place an [chars] transaction on the Deferred list during Bulk Sync for the [chars] CF client.
Explanation Unable to cache a deferred transaction while Bulk Sync is underway. This can adversely impact SSO state on the Standby RP.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_IF_FLOW_IDS-3-CF_SEND_INCR_NONBLOCKED : The Checkpoint Facility reported the error [chars] while attempting to send a non-blocked message. The Incremental Sync transaction for this [chars] CF client cannot be sent to the Standby RP.
Explanation This error indicates the Checkpoint Facility has internal problems related to IPC.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_IF_FLOW_IDS-6-CFPEER_CANNOT_RECV : The Checkpoint Peer is not ready to receive messages. The Incremental Sync transaction for this [chars] CF client will not occur.
Explanation This error indicates the Checkpoint Facility has signalled the peer has gone away.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_IF_FLOW_IDS-3-SEND_FAIL_RELOAD : Checkpoint Facility Failed to send a [chars] transaction for this [chars] CF client. Reloading the Standby RP.
Explanation This indicates the underlying Checkpoint Facility could not deliver a message sent from the active RP to the standby RP. The process will automatically reload the standby RP.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_IF_FLOW_IDS-4-DEF_LIST_REMOVE : Failed to remove one entry from the Deferred Sync list, for the [chars] CF client.
Explanation An unexpected condition occured during list maintenance.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_IF_FLOW_IDS-3-CF_CANNOT_REGISTER : The call to add this [chars] CF client to the Checkpoint Facility failed with the error [chars]. This client is unable to proceed and will not be registered.
Explanation For some reason the Checkpoint Facility will not register this client. As a result the Standby will never receive synchronized state from this CF client on the Active RP, The system is not capable of SSO and HA switchover.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_IF_FLOW_IDS-3-RF_PEER_EVENT_BUFFER : This [chars] RF client is unable to acquire an event buffer to send an RF peer message, the error [chars] was returned.
Explanation This indicates the RF facility is unable to provide a message buffer needed to communicate with the RF peer. As a consequence the RF progression may be compromised.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_IF_FLOW_IDS-3-RF_SEND_PEER : This [chars] RF client encountered error [chars], when attempting to send a peer message.
Explanation This indicates the RF facility could not send a message to the RF peer. As a consequence the RF progression may be compromised.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_IF_FLOW_IDS-3-RF_PROCESS_FAILED : This [chars] RF client Failed to create the Bulk Sync Process.
Explanation The background process which performs the RF Bulk Sync failed to be created. As a consequence the Standby will never obtain the relevent SSO state to enable HA switchover.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_IF_FLOW_IDS-3-RF_POOL_REGEN_PROCESS_FAILED : The [chars] RF client Failed to create the Id Pool Regeneration process.
Explanation The background process which performs Flow Control Id Pool regeneration failed to start. As a consequence the Standby will never obtain the relevent SSO state to enable HA switchover.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_IF_FLOW_IDS-3-RF_POOL_REGEN_ERROR : Id Pool Regeneration encountered error code [dec], cannot switchover.
Explanation The background process which performs Flow Control Id Pool regeneration encountered an error. As a consequence the Standby does not have valid Flow Id pools and cannot progress to Active state.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_IF_FLOW_IDS-3-RF_SPA_ID_REGEN_ERROR : Error code [dec] encountered trying to regenerate spa [chars] identifier in slot/subslot ([int]/[int])
Explanation The background process which performs Flow Control Id Pool regeneration encountered an error. As a consequence the Standby does not have valid Id pools and cannot progress to Active state.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_IF_FLOW_IDS-3-RF_IF_ID_REGEN_ERROR : Error code [dec] encountered trying to regenerate interface flow-control identifer. If id [int] resides in slot/subslot/port ([int]/[int]/[int]).
Explanation The background process which performs Flow Control Id Pool regeneration encountered an error. As a consequence the Standby does not have valid Id pools and cannot progress to Active state.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_IF_FLOW_IDS-3-RF_ADD_CLIENT_FAILED : The RF facility failed to add this [chars] client, reason given is [chars].
Explanation This indicates the RF facility could not add the client.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_IF_FLOW_IDS-3-REGISTRATION : ISSU [chars] failed for [chars]; [chars]
Explanation An ISSU registration for the set of initial capabilities and sessions failed due to the reason specified. This will have the effect of the SPA MARMOT ID ISSU support being unavailable between peers.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_IF_FLOW_IDS-3-ISSU_OP : [chars] [chars] failed; [chars]
Explanation An operation pertaining to the ISSU support for SPA MARMOT IDs failed to complete using the CF transport context with the reason specified
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_IF_FLOW_IDS-3-TRANSFORM : [chars] of [chars] via CF failed
Explanation An attempt to either encode or decode a versioned synchronization message has failed due to an internal error encountered by the ISSU component.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_IF_FLOW_IDS-3-TRANSMIT : Unable to send via [chars] [chars] [chars] [chars]; [chars]
Explanation An attempt to send a versioned negotiation or synchronization message has failed due to an internal error encountered by the CF component.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_IF_FLOW_IDS-3-NEGOTIATION : Failed to start ISSU [chars] session negotiation; [chars]
Explanation The ISSU negotiation with the peer failed to start for either the CF or IPC transport with the reason specified.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_IF_FLOW_IDS-6-READY : [chars] peer not ready, discarding [chars]
Explanation The synchronization attempt for the message has determined that the transport has lost communication with its peer. This is a normal situation which indicates that the standby route-processor is currently out of service implying a simplex redundancy mode.
Recommended Action


%IOSXE_RP_IF_FLOW_IDS-3-DECODE : Decode via CF of [chars] failed
Explanation A message sent via the CF transport failed in its attempt to be decoded on the standby. The resultant action taken by the standby route processor is an attempt to resynchronize.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_IF_FLOW_IDS-3-RECEIVE : Client reports message CF is [chars]
Explanation An attempt to receive and process a versioned negotiation or synchronization message has failed due to an internal error being detected by the information received from the CF component.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


IOSXE_RP_MGMTE through IOSXE_UTD

IOSXE_RP_MGMTE

%IOSXE_RP_MGMTE-3-MSGCREATENULL : Cannot allocate [chars] TDL message
Explanation An unexpected condition in which IOS cannot allocate TDL message for Management ethernet.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_MGMTE-3-MSGTDLINITERROR : Management ethernet interface messaging module initialization failed: Unable to initialize messaging: [chars]
Explanation The Management ethernet interface subsystem has failed to initialize the infrastructure for messaging with the Pluggable Services Daemon. Configuration of management ethernet modules cannot proceed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_MGMTE-3-PROCESS_CREATE_FAIL : Management ethernet statistics process creation failed
Explanation Can not create IOS process for RP management ethernet port statistics collection
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


IOSXE_RP_NV

%IOSXE_RP_NV-3-NV_ACCESS_FAIL : Initial read of NVRAM contents failed
Explanation This error happens when the contents of the NVRAM cannot be read during system initialization. The failure may be due to data corruption of the NVRAM contents. The initial configuration dialog will be entered and the configuration must be restored.
Recommended Action LOG_STD_ACTION


%IOSXE_RP_NV-3-BACKUP_NV_ACCESS_FAIL : Initial read of backup NVRAM contents failed
Explanation This error happens when the contents of the backup NVRAM cannot be read during system initialization. The failure may be due to data corruption of the backup NVRAM contents. The primary nvram contents will be backed up here again.
Recommended Action LOG_STD_ACTION


IOSXE_RP_SPA

%IOSXE_RP_SPA-3-SEND_NGIO_MSG_FAIL : NGIO Module message send failed for slot [dec] subslot [dec]
Explanation Failed to send ngio msg to iomd.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_SPA-3-MAC_FILTER_ADD_FAIL : All the available [dec] mac filters for [chars] have been consumed. Failed to add [enet] for interface [chars]
Explanation The hardware cannot support any more filters.
Recommended Action The interface configuration should be reworked to not cross the limit set by the hardware. If the error is still seen please LOG_STD_SH_TECH_ACTION


%IOSXE_RP_SPA-3-SEND_L2_HDR_MSG_FAIL : slot [dec] subslot [dec]
Explanation Failed to send ngio L2 header to iomd.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_SPA-3-NO_HOST_INFO : slot [dec] subSlot [dec], spaType [hex]
Explanation Failed to get information about the host linecard.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_SPA-3-MAX_SPA : Power to IPSEC-SPA-2G in [chars] is denied because it has exceeded the number allowed([dec])
Explanation The number of IPSEC-SPA-2G in a chassis is limited. This message is displayed when the number of IPSEC-SPA-2G in the chassis has exceeded this limit.
Recommended Action Use only the number of supported IPSEC-SPA-2G


%IOSXE_RP_SPA-3-SPA_NO_HOST_INFO : slot [dec] subSlot [dec], PID [chars]
Explanation Failed to get information about the host linecard.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_SPA-3-HWIDB_FAILURE : Creation: slot [dec] subSlot [dec] port [dec] vc [dec]
Explanation Failed to create an interface hwidb.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_SPA-3-INVALID_PORT_NUM : slot=[dec] port=[dec], hwidbType=[hex], max_port_num=[dec], LCtype=[hex]
Explanation The port number is out of range.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_SPA-4-SPA_RESP_CMD_MISMATCH : [chars]: Expecting response to interface configuration command [int] but received response to command [int].
Explanation An internal synchronization error occurred while configuring the interface. The configuration may not have succeeded.
Recommended Action Check that the running configuration for the interface is correct. If this message occurred on the standby, try reloading the standby to ensure that its configuration is in sync. If this message is repeatable, please LOG_STD_SH_TECH_ACTION


%IOSXE_RP_SPA-6-CARDRELOAD : Module [int] reload due to SPA insert in [int]/[int].
Explanation When inserting a SPA on this carrier card, the card is reset.
Recommended Action No action is required.


%IOSXE_RP_SPA-6-CTRLRSWITCH : switching controller type from [chars]([dec]) to [chars]([dec]) for subslot [int]/[int].
Explanation When IOSXE-SIP40 is inserted in the slot previously occupied by IOSXE-SIP10 or vice-versa the controller type of the card is overwritten to reflect the current SIP.
Recommended Action No action is required.


%IOSXE_RP_SPA-4-SPA_CMD_NO_RESP : [chars]: No response for interface configuration command [int]
Explanation A timeout occurred while RP was waiting for a response from line card. This may happen due to line card CPU being too busy to respond to the command.
Recommended Action No action is required.


%IOSXE_RP_SPA-3-IPCALLOCFAIL : Failed to allocate IPC buffer [chars]
Explanation The RP failed to allocate a buffer for communication with a SPA
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_SPA-3-DPIDX_LKUP_FAIL : Failed to retrieve datapath identifier for interface [chars]
Explanation The SPA driver is not able to retrieve the datapath identifier for the interface specified in the message. This indicates a software error.
Recommended Action No action is required.


%IOSXE_RP_SPA-3-FLOWID_ALLOC_FAIL : Failed to allocate a flow control identifier for interface [chars]
Explanation The SPA driver is not able to allocate the datapath flow control identifier for the interface specified in the message. This indicates a software error.
Recommended Action No action is required.


%IOSXE_RP_SPA-3-FLOWID_RELEASE_FAIL : Failed to release a flow control identifier for interface [chars] (status = [dec])
Explanation The SPA driver is not able to release the datapath flow control identifier for the interface specified in the message. This indicates a software error.
Recommended Action No action is required.


%IOSXE_RP_SPA-3-VC_PROV_FAIL : Failed to provision interface [chars]
Explanation The SPA driver is not able to provision the interface specified in the message. Verify that the SPA hardware is not provisioned above the supported limit. Otherwise, this indicates a hardware error.
Recommended Action No action is required.


%IOSXE_RP_SPA-3-CI_UPDATE_FAIL : Failed to update connection identifier for interface [chars]
Explanation The SPA driver is not able to update the datapath connection identifier for the interface specified in the message. This indicates a software error.
Recommended Action No action is required.


%IOSXE_RP_SPA-3-NULL_DATA_STRUCTURE : common_str_empty_str
Explanation A SPA driver is not able to retrieve the data structure mentioned in the message. This indicates a software error.
Recommended Action No action is required.


%IOSXE_RP_SPA-3-HWIDB_INIT_FAIL : Failed to initialize data structure for SPA port [dec]/[dec]/[dec]
Explanation A SPA driver was not able to properly initialize a data structure mentioned in the message. This indicates a software error.
Recommended Action No action is required.


%IOSXE_RP_SPA-3-ERROR : common_str_empty_str
Explanation This message can take many forms. It provides information about a software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_SPA-4-LCLOG_TOOLONG : Message too long from slot [int]/[int]: [int] bytes
Explanation The SPA module passed down a logger message that is too long for the RP to handle.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_SPA-4-LCLOG_PARSE_ERR : Error parsing logger message: [chars] from subslot [int]/[int]
Explanation The SPA module passed down a logger message that could not be parsed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_SPA-3-BAD_IFCOMTYPE : Bad ifcom message type=[int]
Explanation A SPA module passed down a message that the RP software was not prepared to handle.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_SPA-4-IPCFAILED : IPC failed to send RPC message to SPA module
Explanation The RP failed to send an RPC message via IPC to a SPA module.
Recommended Action No action is required.


%IOSXE_RP_SPA-3-FOREVER : cmd [int] to [chars] (slot [int]/[int]) took [int]secs, done [hex]
Explanation A CCB command from the RP to a SPA module took longer than expected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_SPA-4-SEMAHOG : Process [dec] ([chars]) hogging [chars]! calling proc [dec] ([chars])
Explanation The RP waited too long for a reply to a command sent to a SPA module.
Recommended Action No action is required.


%IOSXE_RP_SPA-3-IPCPORTFAIL : Failed to open IPC port '[chars]' with error [chars]
Explanation The RP failed to open a port for communication with a SPA module.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_SPA-4-CCB_PLAYBACK_ERROR : CCB playback failed for slot [dec].
Explanation The High Availability component for SPA modules failed to synchronize some new state information for the specified slot.
Recommended Action Reload the standby supervisor module to force a fresh bulk synchronization. If this error recurs, LOG_STD_ACTION


%IOSXE_RP_SPA-4-CCB_RECORD_ERROR : CCB record failed for slot [dec].
Explanation The High Availability component for SPA modules failed to record some new state information for the specified slot.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_SPA-3-IPCSENDFAIL : Failed to send IPC message [chars]
Explanation The RP failed to send a message to a SPA module.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_SPA-3-IFCFG_NO_UNIQUE_KEY : No unique-key generator registered for interface configuration command [int].
Explanation The High Availability component for SPA modules is unable to properly synchronize state information for the current configuration.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_SPA-3-IFCFG_FOREVER : to [chars] (slot [int]/[int]) took [int]secs, ret_val [int]
Explanation A interface config command from the RP to a SPA module took longer than expected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_SPA-4-IFCFG_CMD_TIMEOUT : Interface configuration command ([hex]) to slot [int]/[int] timed out
Explanation The RP sent an configuration command to the slot specified in the error message and received no confirmation for the command.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_SPA-3-IFCFG_CMD_NOT_OWNER : Process '[chars]' waiting for interface configuration command ([hex]) to slot [int]/[int] without acquiring lock owned by process '[chars]'
Explanation A process on the RP sent an configuration command to the slot specified in the error message and a different process waited for the result. This could cause incorrect line card configuration states.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_SPA-4-IFCFG_DFLT_LIST_ERROR : For Interface Configuration command [int], default retval list search resulted [hex] for slot [int]/[int]
Explanation The High Availability component for SPA modules failed to synchronize some new state information for the specified slot.
Recommended Action LOG_STD_SH_CMD_ACTION(show platform redundancy if-config default-retvals)


%IOSXE_RP_SPA-4-IFCFG_PLAYBACK_ERROR : Interface Configuration command [int] playback failed for slot [int]/[int].
Explanation The High Availability component for SPA modules failed to synchronize some new state information for the specified slot.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_SPA-4-IFCFG_RECORD_ERROR : Interface Configuration command [int] record failed for slot [int]/[int].
Explanation The High Availability component for SPA modules failed to record some new state information for the specified slot.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_SPA-4-INCR_CFG_SYNC_FAIL : [chars] incremental running-config sync for [[dec]/[dec]] failed - [chars]([dec]) , Reload Standby
Explanation The specified IOSXE incremental running-config sync failed
Recommended Action Power cycle the redundant supervisor


%IOSXE_RP_SPA-3-IPCPORT : Failed to [chars] IPC port '[chars]', error [chars]
Explanation The Linecard failed to create a port for communication with the Route Processor (IOSXE-RP).
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%IOSXE_RP_SPA-3-PROGRESSION : Unable to inform RF of bulk sync completion; [chars]
Explanation The standby has failed to notify the active that its bulks synchronization of the SPA TSM has completed. The resultant action taken by the standby route processor is an attempt to resynchronize.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_SPA-3-VC_FLOWID_ALLOC_FAIL : Failed to allocate a flow control identifier for VC [dec] under interface [chars]
Explanation The SPA driver is not able to allocate the datapath flow control identifier for the VC/interface specified in the message. This indicates a software error.
Recommended Action No action is required.


%IOSXE_RP_SPA-3-VC_INGID_ALLOC_FAIL : Failed to allocate a ingress identifier for VC [dec] interface [chars]
Explanation The SPA driver is not able to allocate the datapath ingress identifier for the VC/interface specified in the message. This indicates a software error.
Recommended Action No action is required.


%IOSXE_RP_SPA-4-SPA_RESP_CMD_ERR : [chars]: Received response to interface configuration command [chars] with wrong return value [int].
Explanation An internal error occurred while configuring the interface. The configuration may not have succeeded.
Recommended Action Check that the running configuration for the interface is correct. If this message is repeatable, please LOG_STD_SH_TECH_ACTION


%IOSXE_RP_SPA-3-FRR_CFG_REC_FAIL : Failed to record fast reroute conifguration on [chars]: [chars]
Explanation This message is displayed when a fast reroute configuration is not properly recorded.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_SPA-3-MISSING_SPA_PKG_ERR : sipspa[chars] package is not installed for slot = [dec] and subslot = [dec], SPA bootup failed.
Explanation This message is displayed when attempting to bootup a SPA without installing a subpackage required for the same.
Recommended Action Download the sub-package required for the affected SPA from the Cisco CCO software download site and install the same. This SPA can be booted in sub-package mode only. Please refer to the Cisco ASR platform documentation for obtaining and installing sub-packages.


%IOSXE_RP_SPA-3-UNSUPPORTED_SRVCS_SPA : Service SPA ([hex]) in [dec]/[dec] is not supported. SPA bootup failed.
Explanation This message is displayed when attempting to bootup any service SPA in router running non K9 image, i.e., non-crypto image.
Recommended Action Download the K9 IOS XE sub-packages and the required sub-package for the given service SPA from the Cisco CCO software download site and install the same. This SPA can be booted in sub-package mode only. Please refer to the Cisco ASR platform documentation for obtaining and installing sub-packages.


%IOSXE_RP_SPA-3-MISSING_SPA_PKG_WARN : sipspa[chars] package is not installed in standby for slot = [dec] and subslot = [dec].
Explanation This message is displayed in standby console when attempting to bootup or restart or reload a WMA SPA without installing a subpackage in the standby RP, although the SPA is or will be operational due to prior wma spa package installation in active RP. If switchover takes place the WMA SPA will still be operational. But any subsequent soft or hard oir of the SPA will fail due to missing sub package required to boot up the SPA. Hence it is recommended to complete the wma spa package installation in standby also before switchover or immidiately after switchover.
Recommended Action Download the sub-package required for the affected SPA from the Cisco CCO software download site and install the same for the standby RP as is done on active RP. Please refer to the Cisco ASR platform documentation for obtaining and installing sub-packages.


%IOSXE_RP_SPA-3-SPA_WRONGTYPE : Mismatched SPA type ([dec]) in slot [dec]/[dec]. Expected type [dec]. Use 'no card [dec]/[dec]' command to override preprovisioning and update card type.
Explanation The SPA inserted does not match the currently provisioned SPA type.
Recommended Action Replace wrong SPA with currently provisioned SPA type, or type 'no card' to allow new card type to be discovered.


%IOSXE_RP_SPA-6-MEDIA_AUTOFAILOVER : Media Fail over from ([chars]) to ([chars])
Explanation Gige Media Failover.
Recommended Action This is inforamtional message, Not an error message. Use 'show interface gig' to see the current active media type.


%IOSXE_RP_SPA-3-SONET_ALARM_PROC_ERR : [chars] Error has occurred while processing in the sonet alarm-proc
Explanation Either free/create of the memory failed in SONET alarm proc
Recommended Action


%IOSXE_RP_SPA-3-LIC_REQ_FAILED : [int]/[int]/[int]: Interface enable not allowed - license request failed , err=[hex]
Explanation A 10 Gig License is required to enable this port. License request has been denied by license manager
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_SPA-3-LIC_REL_FAILED : [int]/[int]/[int]: Failed to release license feature [chars], handle=[hex], err=[hex]
Explanation License release has been denied by license manager
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_SPA-3-LIC_REG_FAILED : [int]/[int]/[int]: Failed to register license feature [chars], err=[hex]
Explanation License registration has been denied by license manager
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


IOSXE_RP_VTYMGT

%IOSXE_RP_VTYMGT-3-MSGDISPATCHNULL : Received NULL TDL message
Explanation An unexpected condition in which IOS has received a NULL TDL message for Vty Management.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_VTYMGT-3-MSGDISPATCH : Unable to dispatch received TDL messages for Vty Management
Explanation An unexpected condition has occurred while IOS is trying to dispatch to the TDL message handler functions for received TDL messages for Vty Management.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_VTYMGT-3-MSGMISSINGFIELD : Missing field '[chars]' in TDL Vty Management message '[chars]' received
Explanation A message missing a required field was received for Vty Management
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_VTYMGT-3-MSGINVALIDFIELDINT : Invalid field '[chars]' in TDL message '[chars]' received: value '[int]' for Vty Management
Explanation A message with an invalid field value was received for Vty Management
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_VTYMGT-3-MSGINVALIDFIELDSTR : Invalid field '[chars]' value '[chars]' in TDL message '[chars]' received for Vty Management
Explanation A message with an invalid field value was received for Vty Management
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_VTYMGT-3-MSGERROR : Error '[dec]' handling a received TDL message '[chars]' for Vty Management: [chars]
Explanation An unexpected condition has occurred while IOS is processing a received Vty Management TDL message
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_VTYMGT-3-MSGBUILDERROR : Error '[dec]' building TDL Vty Management message '[chars]': [chars]
Explanation An unexpected condition has occurred while IOS is building a TDL response message for Vty Management
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_VTYMGT-3-MSGMARSHALERROR : Error '[dec]' marshaling TDL Vty Management message '[chars]': [chars]
Explanation An unexpected condition has occurred while IOS is marshaling TDL response message for Vty Management
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_VTYMGT-3-MSGENQUEUEERROR : Error queueing TDL Vty Management message '[chars]'
Explanation An unexpected condition has occurred when IOS attempted to queue a TDL response message for Vty Management
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_VTYMGT-3-MSGBIPCERR : Unable to process received BIPC messages for Vty Management, error: [chars]
Explanation An unexpected condition has occurred while IOS was trying to process a received BIPC message for Vty Management.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_VTYMGT-3-MSGBIPCBUFFER : Unable to acquire a BIPC buffer of length [dec] for sending messages.
Explanation A message was to be sent by IOS, but no BIPC buffer was available. The message to be sent has been discarded and the associated operation failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_VTYMGT-3-MSGEXTAPPUPDATE : Unable to update external application data for line '[dec]'
Explanation An attempt to update the external application for a line failed unexpectedly. The line update failed and if the line number specified is valid, the line was released.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_VTYMGT-3-MSGVTYSVCINIT : Unable to initialize the Vty Management service listen port
Explanation The platform IPC services failed to register the Vty Management service's need for a listen port. The Vty Management service will be unable to process requests. IOS services will be unavailable to external access methods.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_VTYMGT-3-MSGVTYCOUNT : Invalid vty count [dec] detected on initialization
Explanation Upon initialization, the Vty Management subsystem checks that the number of available vtys for the platform is valid.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_RP_VTYMGT-3-SET_ACCESS_FAIL : Installing LIIN interface access control failed
Explanation This error happens when the Vty Management subsystem failed to set the access control function for the LIIN, possibly due to IOS out of memory or corruption. Persistent access features into IOS will not work.
Recommended Action LOG_STD_ACTION


IOSXE_SERVICE_ENGINE

%IOSXE_SERVICE_ENGINE-3-MSGOPENFAIL : Cannot open interface [chars] ([dec])
Explanation During the creation of a Service-Engine interface, it is necessary to program the system parameters in the driver. The driver cannot be opened.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_SERVICE_ENGINE-3-MSGSETFAIL : Set id on interface [chars] ([dec])
Explanation During the creation of a Service-Engine interface, it is necessary to program the system parameters in the driver. The failed to accept the programming.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_SERVICE_ENGINE-3-MSGINITFAIL : Initialization of interface [chars] failed
Explanation The initialization of the interface mentioned in the error message has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


IOSXE_SPA

%IOSXE_SPA-3-CREATION_FAILURE : slot=[dec] subslot=[dec], spa_type=[hex], lc_type=[hex].
Explanation Failed to create a SPA object.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_SPA-3-SPA_CREATION_FAILURE : slot=[dec] subslot=[dec], PID=[chars] lc_type=[hex].
Explanation Failed to create a SPA object.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_SPA-3-NULL_VFT : [chars] virtual function table is not initialized. spaType=[hex]
Explanation A required function table is not initialized
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_SPA-3-NULL_VFUNC : [chars] vector is not initialized. spaType=[hex]
Explanation A required function vector is not initialized
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_SPA-3-MEM_ALLOC_ERROR : [chars]
Explanation Memory allocation error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_SPA-3-NULL_SPA_PTR :
Explanation Pointer to a SPA object is NULL.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_SPA-3-NULL_BAY_PTR :
Explanation Pointer to SPA bay is NULL.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_SPA-3-INVALID_SLOT_NUM : slot= [dec], max slot = [dec]
Explanation An invalid slot number is specified in one of the internal APIs.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_SPA-3-INVALID_SUBSLOT_NUM : subslot= [dec], max subslot = [dec]
Explanation An invalid subslot number is specified in one of the internal APIs.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_SPA-3-INVALID_DB_NUM : db = [dec], max db = [dec], db intf = [dec], max db intf = [dec]
Explanation An invalid daughter board number is specified in one of the internal APIs.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_SPA-3-INVALID_RP_SLOT_NUM : slot= [dec], max slot = [dec]
Explanation An invalid RP slot number is specified in one of the internal APIs.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_SPA-3-INVALID_CPU_NUM : cpu= [dec], max cpu = [dec]
Explanation An invalid CPU number is specified in one of the internal APIs.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_SPA-3-INVALID_SLOTUNIT_NUM : cardwide-port = [dec], max cardwide-port = [dec]
Explanation An invalid cardwide-port number is specified in one of the internal APIs.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_SPA-3-INVALID_INDX_RANGE : index1= [dec], index2= [dec], maxIndex= [dec]
Explanation An invalid index range is specified in one of the internal APIs.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_SPA-3-INVALID_IF_INDEX : index= [dec], spaType=[hex], slot [dec] subSlot [dec] slotunit [dec] vc [dec]
Explanation Index for the interface is not valid.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_SPA-3-INVALID_DATA_INSTANCE : interface type [chars], slot [dec] port [dec] vc [dec] : [chars]
Explanation Data required to support the interface is not available.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_SPA-3-POWER_CYCLE : [chars] occurred on Shared Port Adapter [int]/[int]
Explanation An error has occurred which will cause the Shared Port Adapter to be power cycled
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_SPA-3-DIAG_CONFIG : [chars] did not complete [dec]/[dec]
Explanation An error has occured during diagnostic test.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_SPA-3-UNSUPPORTED_DATA : Data conversion error ([chars], [hex])
Explanation An internal software error has occured when converting the data specified in the message from one representation to another.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_SPA-3-IPC_FAILURE : IPC failure while [chars]
Explanation An error has occurred while prepareing or sending an IPC message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_SPA-3-SENDCFGFAIL : Failed to send configuration for [chars] to carrier-card for subslot=[dec]/[dec]
Explanation Sending configuration failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_SPA-3-CREATE_TDLH_FAILURE : Failed to create SPA [dec]/[dec] handle
Explanation Failed to create message handle for SPA communication.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_SPA-3-DOMAIN_TDLH_FAILURE : [chars], rc = [dec]
Explanation Failed to bind message handle for SPA communication.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_SPA-3-SETUP_TDLH_FAILURE : Failed to set the alloc/free handler for SPA [dec]/[dec] handle
Explanation Failed to set the alloc/free handler for SPA communication.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_SPA-3-DISPATCH_INIT_TDLH_FAILURE : Failed to initialize dispatch path for SPA [dec]/[dec] handle
Explanation Failed to initialize dispatch path handle for SPA communication.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_SPA-3-INVALID_SPA_TDL_CCAPI_USAGE :
Explanation Incorrect usage of an internal API that should only be used on CC.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_SPA-6-TDLMSG_INCOMPATIBLE : Failed to copy message [chars] to buffer, not allowed for current domain.
Explanation Failure to marshal a message indicates an incompatibility with the intended recipient.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_SPA-3-CREATE_TDLMSG_FAILURE : Failed to create [chars] message for [chars].
Explanation Failed to create/allocate necessary TDL message for SPA communication.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_SPA-3-INVALID_HANDLE : Failed to get a valid IPC handle for type [int], slot [dec], subslot [dec].
Explanation The client handle was found to be NULL for the given type/slot/subslot.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_SPA-6-UPDOWN : Interface [chars], link down due to [chars]
Explanation Ethernet link is down due to remote/local fault.
Recommended Action Replace the faulty cable.


%IOSXE_SPA-6-DUAL_RATE_CHANGE : [chars]: [chars]
Explanation Change in rate of the link.
Recommended Action No action is required.


%IOSXE_SPA-3-SPA_SETUP_FAILURE : Failed to properly setup for SPA communication on slot [dec], subslot [dec].
Explanation Discovery of the linux interface used to communicate with a SPA failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_SPA-3-ABANDON_SPA_CONFIGURATION : Abandon configuration for subslot [dec]/[dec], the SPA type([dec]) is NOT match with SUP card.
Explanation Abandon SPA configuration.
Recommended Action Please check the startup configuration, use no card command to override wrong card configuration and update card type.


IOSXE_TIMESTAMP_ENGINE

%IOSXE_TIMESTAMP_ENGINE-4-ERROR : NULL
Explanation An unexpected condition has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_TIMESTAMP_ENGINE-3-TSU_ERR : An unexpected condition has occurred at module ([chars])
Explanation An unexpected condition has occurred at the Interface Module TSU.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


IOSXE_UPGRADE_ROMMON

%IOSXE_UPGRADE_ROMMON-0-ROMMON_UPGRADE_FAIL : ROMMON upgrade failed: partition [chars]
Explanation An attempt to upgrade the ROMmon failed.
Recommended Action Check the system messages to see if any messages appeared that might indicate the source of the ROMmon problem. If you do not find any additional information indicating a correctable problem, collect all output on the screen, in particular the console port output after the upgrade rom-monitor command was entered and the output of show rom-monitor, and provide the collected information to a Cisco technical support representative.


%IOSXE_UPGRADE_ROMMON-0-ROMMON_LOADTEST_FAIL : ROMMON FIPS_140-3 Load test *FAILED*: file [chars]
Explanation FIPS 140-3 Related Load test failed for the ROMmon.
Recommended Action Check the system messages to see if any messages appeared that might indicate the source of the ROMmon Load test problem. If you do not find any additional information indicating a correctable problem, collect all output on the screen, in particular the console port output after the upgrade rom-monitor command was entered and the output of show rom-monitor, and provide the collected information to a Cisco technical support representative.


IOSXE_USB

%IOSXE_USB-3-ESHOW_USB : Internal Error locating database for USB Devices.
Explanation The mcp_usb_devices is incorrect and needs to be changed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


IOSXE_UTD

%IOSXE_UTD-3-ALLOC : Failed to allocate message
Explanation When attempting to program the dataplane there was not enough memory to allocate the message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_UTD-3-MESSAGE : Failed to send message
Explanation When the message was being prepared for sending to the data plane, there was an error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_UTD-4-VERSION_INCOMPATIBILITY : UTD OVA version ([chars]) does not match supported UTD version ([chars])
Explanation The UTD OVA version does not match the required UTD version embedded in this IOS-XE version. This is an unsupported configuration and may behave unexpectedly.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_UTD-4-SIG_UPDATE_CFG : UTD signature updates have been configured - A brief service interruption at the time of update is expected
Explanation The UTD service will be restarted if a new signature package is found. During this time, if fail-close has been configured (recommended), traffic that would be inspected by UTD will be dropped. Otherwise (default), traffic that would be inspected by UTD will be allowed to pass uninspected. To minimize this service interruption, it is recommended to schedule this operation outside of normal business hours.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_UTD-4-SIG_UPDATE_EXEC : UTD signature update has been executed - A brief service interruption is expected
Explanation The UTD service will be restarted if a new signature package is found. During this time, if fail-close has been configured (recommended), traffic that would be inspected by UTD will be dropped. Otherwise (default), traffic that would be inspected by UTD will be allowed to pass uninspected. To minimize this service interruption, it is recommended to execute this operation outside of normal business hours.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_UTD-4-MT_CONFIG_DOWNLOAD : UTD MT configuration download has [chars]
Explanation In UTD multitenancy mode, the configuration download to the container can take a while. Please be patient.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_UTD-4-MT_CONTAINER_MESSAGE_TIMEOUT : UTD message sent to the container has timed out
Explanation The UTD message sent to the container has timed out.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_UTD-4-MT_CONTAINER_MESSAGE_NAK : Container responded to UTD message with an error: [dec]
Explanation The container rejected the UTD message
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_UTD-4-MT_CONTAINER_SESSION_TIMEOUT : UTD container download has timed out
Explanation The container did not respond with an up/down status before the session timed out.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_UTD-4-MT_CONTAINER_STATUS_DOWN : UTD poll: container status is DOWN
Explanation The container sent a down status to the poll message
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


IOSXE_VMAN through IPC_LOG

IOSXE_VMAN

%IOSXE_VMAN-3-MSGINITFAIL : Failed to initialize required Virt-manager resource: [chars]
Explanation During the initialization of the resources required by Virt-manager, a failure occurred. This has prevented virtual services from being activated.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_VMAN-3-MSGDISPATCH : Unable to dispatch received TDL message from Virt-manager
Explanation An unexpected condition has occurred while IOS was trying to dispatch a TDL message received from Virt-manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_VMAN-3-RSPMSGHDLR : Failed to deliver response message: [chars]
Explanation An unexpected condition has occurred while IOS was trying to deliver a response message to a virtual service received from Virt-manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


IOSXE_WCCP

%IOSXE_WCCP-4-NOINPUT : NULL input, [chars]
Explanation An unexpected condition has occurred which is due to the NULL value of the input parameter.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show ip wccp command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_WCCP-4-NOSVCGRP : [chars] Service Group ([dec], [dec], [int]) NOT exist
Explanation An unexpected condition has occurred which is due to the absence of the service group structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show ip wccp command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_WCCP-4-NOACL : Access list is null
Explanation An unexpected condition has occurred which is due to the absence of an access list structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show ip access-lists command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_WCCP-4-ACELIMIT : Too many ACEs in MASK ACL, please switch to Hash mode
Explanation Mask merged ACL generate too many ACEs.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show ip access-lists command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_WCCP-4-BADACE : Access list contains invalid ace
Explanation An unexpected condition has occurred which is due to an invalid statement in the access list structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show ip access-lists command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_WCCP-4-NOINTF : No [chars] interface info for Service Group ([dec], [dec], [int])
Explanation An unexpected condition has occurred which is due to the absence of MCP WCCP interface info for the specific service group.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show platform software wccp command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_WCCP-4-UNKNOWNDIR : Unknown [chars] interface direction [hex] for Service Group ([dec], [dec], [int])
Explanation An unexpected condition has occurred which is due to the unknown direction has been applied to the interface for the service group.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show platform software wccp command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_WCCP-4-NOSTATS : WCCP [chars] message error
Explanation An unexpected condition has occurred which is due to the error in receiving WCCP stats update message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show platform software wccp <id> counters command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_WCCP-4-NOSTATSSVC : Service Group ([dec], [dec], [int]) not exist for the stats message
Explanation An unexpected condition has occurred which can't find the service group for the service group stats message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show platform software wccp command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOSXE_WCCP-4-NOSTATSINTF : Interface handle [int] not exsit for the stats message
Explanation An unexpected condition has occurred which can't find the interface handle for the interface stats message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show platform software wccp <id> int counters command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


IOSXE_WD

%IOSXE_WD-2-HEARTBEAT_FAIL : Heartbeat is not emitted. Heartbeat count:[dec]
Explanation Failure in IOS to generate a heartbeat is an abnormal condition
Recommended Action This message may be related to an abnormal configuration and system load, or transient high processing demand. When reporting this message, copy the message text exactly as it appears, include the stack trace and report to your technical support representative


%IOSXE_WD-2-HOG_DETECT_FAIL : CPUHOG detection failed to start.
Explanation Failure in setting up CPUHOG detection mechanism is an abnormal condition
Recommended Action This message may be related to an abnormal configuration and system load, or transient high processing demand. When reporting this message, copy the message text exactly as it appears, include the stack trace and report to your technical support representative


IOS_LICENSE_IMAGE_APPLICATION

%IOS_LICENSE_IMAGE_APPLICATION-3-FAILED : [chars]
Explanation 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-3-UNKNOWN_EVENT : [chars]
Explanation 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


%IOS_LICENSE_IMAGE_APPLICATION-3-UNKNOWN_VERSION : [chars]
Explanation
Recommended Action


%IOS_LICENSE_IMAGE_APPLICATION-6-NO_LICENSE : No valid license available: [chars] = [chars]; [chars] = [dec]; [chars] = [chars]:[chars]
Explanation The ios image licensing subsystem received an event for an unknown version of a feature There is no valid license available on the box and we are running on a default feature
Recommended Action please capture the error msg and forward it to the appropriate licensing component please purchase a license to activate required features


%IOS_LICENSE_IMAGE_APPLICATION-6-LICENSE_LEVEL : Module name = [chars] Next reboot level = [chars] and License = [chars]
Explanation 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


%IOS_LICENSE_IMAGE_APPLICATION-6-LICENSE_LEVEL_CONFIG : Please issue 'license boot' config command to make extension license ([chars]) 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


%IOS_LICENSE_IMAGE_APPLICATION-6-LICENSE_CONFIG : EULA must be accepted for license level = [chars]
Explanation 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


IOXN_APP

%IOXN_APP-3-INITFAIL : Failed to create chasfs property ioxman (rc =[chars]) or caf (rc = [chars]) is not up
Explanation An unexpected condition resulted into failure to start an application.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOXN_APP-3-CLEANUPFAIL : Failed to create chasfs property to indicate cleanup of previous app installation (rc = [chars])
Explanation An unexpected condition resulted in failure to setup the start of an application.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOXN_APP-3-GSFAIL : [chars] [int]
Explanation An unexpected condition resulted into failure to start an application.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOXN_APP-3-CFGFAIL : [chars] [chars]
Explanation An unexpected condition resulted into failure to apply auto config
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOXN_APP-3-PREVOPFAIL : Overriding previous operation ([chars] iox) that is taking longer than [int] secs to complete
Explanation An unexpected condition resulted in failure to apply iox config
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IOXN_APP-3-MSGFAIL : Message dispatch failure ([chars]).
Explanation Message could not be dispatched to an application.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


IP

%IP-4-CLASS : Bad IP address and mask [IP_address]%m in class_resolve()
Explanation An internal software error occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IP-4-DUPADDR : Duplicate address [IP_address] on [chars], sourced by [enet]
Explanation Another system is using your IP address.
Recommended Action Change the IP address of one of the two systems.


%IP-4-ZERO_ADDR : Zero MAC address for [IP_address] in ARP cache
Explanation 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-3-DESTHOST : src=[IP_address], dst=[IP_address], NULL desthost
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IP-3-BADIPALIGN : Invalid alignment in packet for IP. [chars]=[hex]
Explanation The packet data structure is misaligned. This condition may result in a small amount of overhead in processing IP traffic.
Recommended Action Enter a show hardware command and report the output, along with this error message, to your technical support representative.


%IP-3-BADSROUTE : Improper source route. Length [dec] Ptr [dec]
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IP-6-PHYBCASTDROP : Physical broadcast packet detected and dropped, src=[IP_address], dst=[IP_address]
Explanation Physical broadcast packet was dropped.
Recommended Action No action is required.


%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.


%IP-3-LOOPPAK : Looping packet detected and dropped - src=[IP_address], dst=[IP_address], hl=[int], tl=[int], prot=[int], sport=[int], dport=[int] in=[chars], nexthop=[IP_address], out=[chars]options=[chars]
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IP-5-WEBINST_START : Attempting web install from host [IP_address]
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%IP-5-WEBINST_KILL : Terminating DNS process
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IP-5-WEBINST_COMP : Selected IP address [IP_address]
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IP-5-WEBINST_RESP : Sending DNS response to [IP_address] (request was for [IP_address])
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IP-3-CNTRFULL : IP counter block is full (setting protocol [dec])
Explanation An internal software error occured.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IP-5-TURBOACL : [chars]
Explanation Error occured in intialisation of TURBOACL.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show process command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IP-5-ACL : [chars]
Explanation Error occured in IP access checks.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IP-4-UNICASTRPF : IP unicast reverse-path check disabled on [chars]
Explanation 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 error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IP-3-LOOPOUTIF : Output interface for packet has been changed for [dec] times and dropped - src=[IP_address], dst=[IP_address], hl=[int], tl=[int], prot=[int], in=[chars], nexthop=[IP_address], out=[chars]
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%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.


%IP-4-IPPOOLS : Detected a local pool and a DHCP pool with the same name: [chars]
Explanation A local pool and a DHCP pool have been configured with the same name. This may cause conflict during address allocations.
Recommended Action Change the name of one of the two pools


%IP-3-ICMPRATELIMIT : [int]nreachables rate-limited within [int] milliseconds on [chars]. [int] log messages suppressed since last log message displayed on [chars]
Explanation An excessive number of packets are triggering log messages on this interface
Recommended Action change the log threshold with the icmp rate-limit command or find the source of the packets and block the packets from this router


%IP-3-ICMPRATELIMITDF : [int] DF unreachables rate-limited within [int] milliseconds on [chars]. [int] DF log messages suppressed since last log message displayed on [chars]
Explanation An excessive number of packets are triggering log messages on this interface
Recommended Action change the log threshold with the icmp rate-limit command or find the source of the packets and block the packets from this router


%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 error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IP-3-NONALIAS : non-alias address [IP_address] in table [chars] found in IP alias list
Explanation The IP alias list holds IP aliases only but non-alias entries are found.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IP-3-IPTOPOID : Topology ID [hex] is invalid, can't get the base topology ID.
Explanation An internal software error occurred
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IP-3-SBINIT : Error initializing [chars] subblock data structure. [chars]
Explanation Initialization of the specified subblock data structure could not be accomplished.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


IPA

%IPA-3-PORTCONN : bay [[int]] failed to establish [chars] connection ([hex])
Explanation An attempt to establish the console or debugger connection with the channel port adapter failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPA-3-PORTIOKILL : Port IO [chars] process terminating.
Explanation Unexpected termination of a port io process.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPA-3-NEVER : bay [[chars]] mailbox response timed out after ([int] + [int]) usecs, mbx=[hex]
Explanation 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. <Body><par>If the error still occurs, record the output from the following commands: <Bullet><par>show tech <Bullet><par>dir slot0: <Bullet><par>dir slot1: <Bullet><par>show log <Body><par>Provide this information to your technical support representative.


%IPA-3-UKNMBXCMD : [chars]: unknown mailbox command: [hex] [hex] [hex] [hex]
Explanation 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 error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPA-3-INVMBXCMD : [chars]: invalid mailbox command: [hex]
Explanation A subsytem attempted to register a mailbox command that is out of range.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


IPACCESS

%IPACCESS-2-NOMEMORY : Alloc fail for acl-config buffer. Disabling distributed mode on lc
Explanation 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.


%IPACCESS-2-WRONGREQUEST : Invalid request to allocate chunk of size [dec]
Explanation We only allow acl chunks of max size IPACCESS_LARGE_CHUNK_SZ
Recommended Action


%IPACCESS-2-WRONGSIZE : Incorrect length acl ipc xdr of type=[chars] len=[dec] received
Explanation Received an acl message of the wrong size for that type
Recommended Action Report this error message, to your tech support representative.


%IPACCESS-4-INVALIDACL : Invalid ACL field: [chars] is [dec]
Explanation An internal software error occurred.
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative.


%IPACCESS-3-SANITY_ERROR : [chars]
Explanation A sanity error occurred while the ACL was being configured on the RP, or while the ACL configuration was being downloaded to the line card.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPACCESS-3-XDRREGISTRATION : Failed to register [chars] XDR client due to [chars]
Explanation Failure to register the said XDR client.
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative.


IPC

%IPC-3-LOG_ERR : [chars] CPP QoS Client Proxy failure
Explanation QoS proxy failed because of receiving invalid sub-type or failed to allocate ipc response buffer.
Recommended Action LOG_STD_ACTION


IPC_LOG

%IPC_LOG-3-IPC_LOGWRITE_FAILED : ipc log write [int] bytes failed because [chars]
Explanation An internal logging mechanism failed to write a message.
Recommended Action No action is required. However, if router performance is noticeably degraded, contact Cisco Technical 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 https://bst.cloudapps.cisco.com/bugsearch/. If you still require assistance, open a case with the Technical Assistance Center via the Internet athttps://mycase.cloudapps.cisco.com/case, or contact your Cisco technical support representative and provide the representative with the gathered information.


IPC_TEST through IPV6_ACL

IPC_TEST

%IPC_TEST-3-INVALID_SUBTYPE : CPP IPC TEST Proxy subtype [int]
Explanation IPC test proxy failed because of receiving invalid sub-type.
Recommended Action LOG_STD_ACTION


%IPC_TEST-3-REPLY_FAILED : CPP IPC TEST Proxy send reply
Explanation IPC test proxy failed because the reply failed to send.
Recommended Action


%IPC_TEST-3-MEM_ALLOC_FAILED : CPP IPC TEST Proxy mem alloc
Explanation IPC test proxy failed because the GPM allocation failed.
Recommended Action


IPFAST

%IPFAST-2-RADIXINIT : Error initializing IP fast cache structures
Explanation A programming error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPFAST-2-IPCACHEINIT : Error initializing IP fast cache structures
Explanation A programming error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%IPFAST-2-MSGDROP : IPC queue limit is reached and message is dropped. queue limit = [dec] cumulative drops = [dec]
Explanation IPC raw queue limit for IP fast path is reached.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPFAST-6-PAKSHORT : Packet too short from [IP_address], datagram size [dec], tl [dec]
Explanation An IP packet which is too short was received
Recommended Action No action is required.


%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 error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPFAST-2-FAILOPENIPCPORT : Could not open the IPC ports. [chars]
Explanation ipfast could not open the ipc port to communicate to the LC/RRP/SP.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


IPFLOW

%IPFLOW-2-QUEUEINIT : Error initializing Flow feature queue
Explanation 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.


%IPFLOW-3-DISABLEFLOWEXPORT : NULL
Explanation 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-2-PROCESSINIT : Error initializing Flow background process
Explanation 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.


%IPFLOW-2-CACHEINIT : Error initializing IP flow cache
Explanation Initialization of the Flow cache could not be accomplished because of a low memory condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPFLOW-2-EXPORTINIT : Error initializing Flow Export queue
Explanation 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.


%IPFLOW-2-TEMPLATETBL_INIT : Error initializing Flow Export Template Table
Explanation Initialization of the Flow export template table could not be accomplished because of a low memory condition.
Recommended Action Reduce other system activitiy to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.


%IPFLOW-4-V9_TEMPLATE_EXPORT : Error creating [chars]
Explanation Version 9 export template length is zero
Recommended Action This is a debug message only. No action is required.


%IPFLOW-3-SBINIT : Error initializing [chars] subblock data structure. [chars]
Explanation Initialization of the specified subblock data structure could not be accomplished.
Recommended Action


IPMOBILE

%IPMOBILE-6-REDUPDATEFAIL : Too many redundancy update failures ([dec]) in the last minute.
Explanation The standby HA attempts to update its binding table by contacting the active HA several times each minute. Some or all of these attempts failed and the number of failures exceeded a threshhold number.
Recommended Action Ensure connectivity between the active HA and the standby HA. Also make sure the clocks are in sync between the two and that the security associations are properly set between the two. If the preemption delay is set, try setting it to a shorter time period.


%IPMOBILE-6-DUPMOBNET : Unable to [chars] dynamic mobile network [IP_address] [IP_address] for MR [chars]; already [chars] MR [chars]
Explanation A mobile router's attempt to dynamically add or delete a mobile network failed because that mobile network was already statically configured for or dynamically registered by another mobile router. A mobile network may be configured or registered for only one mobile router.
Recommended Action To avoid duplication errors, check the static mobile network configuration on the HA or the dynamic mobile network configuration on the mobile router(s).


%IPMOBILE-6-DUPVIRTNET : Unable to [chars] dynamic mobile network [IP_address] [IP_address] for MR [chars]; already configured as a virtual network
Explanation A mobile router's attempt to dynamically add or delete a mobile network failed because that mobile network was already configured as a virtual network in the home agent.
Recommended Action To avoid duplication errors, make sure that the virtual networks configuration on the home agent and the dynamic mobile network configuration on the mobile router do not have any overlapping network prefixes.


%IPMOBILE-3-NOSOCKET : Unable to open socket
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.


%IPMOBILE-6-SECURE : Security violation on [chars] from [chars] [chars] - errcode [chars] ([dec]), reason [chars] ([dec])
Explanation A security violation occurred during registration attempt.
Recommended Action This is for informational purpose only.


%IPMOBILE-2-ASSERTFAILED : IPMOBILE assertion failed: [chars]
Explanation 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 error message exactly as it appears, noting any IP Mobility problems that you are experiencing, and report it to your technical support representative.


%IPMOBILE-3-CONFIGERROR : Standby FA configuration is not in sync with the active
Explanation The software detected an inconsistency in configuration between the standby and the active. Standby FA may not proceed with the sync for this visitor.
Recommended Action Re-configure standby FA and make sure the configuration between the standby and the active is in sync.


%IPMOBILE-3-NOTUNNEL : Maximum number of tunnels [dec] reached
Explanation The number of Mobile IP tunnels allowed on the box is reached.
Recommended Action This occures if the HA/FA is overloaded. If you suspect this condition contact technical support representative with the output of show tech


%IPMOBILE-5-MIP_TUNNELDELETE : Mobile IP tunnel [chars] deleting
Explanation The Mobile IP tunnel is going to be deleted.
Recommended Action This occurs if the active mobile ip binding is deleted. If you suspect this condition contact technical support representative with the output of show tech


%IPMOBILE-0-NOPROCESS : [chars]
Explanation A Process could not be started
Recommended Action Please contact your technical support representative with the error message you got and with the output of 'show process '.


%IPMOBILE-0-IPMOBILE_DHCP : [chars]
Explanation Two reasons for this error message, 1. DHCP Client failed to get started, this could be because of malloc failures. 2. IPMOBILE DHCP Process failed to start
Recommended Action If this error message is seen it is recommended not to use this HA for binding creation with DHCP Address Allocation. Check the available memory in the box and for the first reason try to get 'debug dhcp detail' before the failure. Contact your technical support representative with the error message you got.


%IPMOBILE-3-SA_PARSE_FAILED : Error in parsing the security association for [chars]
Explanation The Mobile IP Home Agent encountered an error while processing the Security Association in the RADIUS Access-Accept message.
Recommended Action Check the Radius profile config for the Mobile Node for which the processing of the Security Association failed.


IPNAT

%IPNAT-4-ADDR_ALLOC_FAILURE : Address allocation failed for [IP_address], pool [chars] might be exhausted
Explanation 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 misses will be incremented for these packets.
Recommended Action Check to see 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 clear ip nat translation *


%IPNAT-3-SYSSTATSNULL : NAT global/system statistics structure from platform is nul
Explanation The structure for passing global/systems statistics from platform is nul which is invalid. This condition can cause the NAT global statistic counters in inaccurate on the RP
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPNAT-3-POOLSTATSNULL : NAT pool statistics structure from platform is nul
Explanation The structure for passing global/systems stats from platform is nul which is invalid. This condition can cause the statistic counters for NAT pool to be inaccurate on the RP
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPNAT-3-BADMAPPINGTYPE : NAT mapping type [dec] for mapping statistics from platform is invalid
Explanation The mapping type for passing mapping statistics from platform is not for static nor dynamic mapping type which is invalid. This condition can cause the statistic counters for NAT mapping to be inaccurate on the RP
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPNAT-3-MAPPINGSTATSNULL : NAT mapping statistics structure from platform is nul
Explanation The structure for passing mapping statistics from platform is nul which is invalid. This condition can cause the statistic counters for NAT mapping to be inaccurate on the RP
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPNAT-3-LIMITSTATSNULL : NAT mexentry statistics structure from platform is nul
Explanation The structure for passing maxentry limit statistics from platform is nul which is invalid. This condition can cause the statistic counters for NAT maxentry limit to be inaccurate on the RP
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPNAT-3-PORTNULL : Start port or end port for port block allocation request is nul
Explanation Start port or end port for port block allocation request is nul, This condition can cause the new translations to fail in the data path
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPNAT-3-PORTLISTNULL : Portlist for address [IP_address] proto [dec] is nul
Explanation The portlist for the address which requests more port blocks is nul which is invalid. This condition can cause the new translations to fail in the data path
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPNAT-3-WLANSESSNULL : NAT WLAN session structure for session [chars] from platform is nul
Explanation The structure for passing WLAN session from platform is nul which is invalid. This condition can cause the NAT WLAN session to fail in the data path
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPNAT-6-ID : [chars] identifier has wrapped
Explanation The identifier which is assigned to that which is resultant from the configuration in question has cycled through the available number space and is now allocating from its initial value again.
Recommended Action No action is required.


%IPNAT-3-RTMAPNULL : route-map for configuration download is nul
Explanation The route-map structure is nul which is invalid. This condition can cause the new translations to fail in the data path
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPNAT-3-CSBNULL : Parser structure for route-map [chars] configuration is nul
Explanation The parser structure for route-map configuraion is nul which is invalid. This condition can cause the new translations to fail in the data path
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPNAT-3-RTMAPNAMENULL : Route-map name for [chars] configuration is nul
Explanation The route-map name is nul which is invalid. This condition can cause the new translations to fail in the data path
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPNAT-6-ENTRIES : Static translation count reset, inside/outside source/destination [int]/[int] [int]/[int]
Explanation Upon the removal of the last remaining static translation from the configuration it has been determined that there is a discrepancy with the internal accounting as regards the previous provisioning of inside source/destination versus outside source entries. The internal accounting has been reset to indicate that there are no translations of any type currently.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPNAT-3-CONFIG : Unable to [chars] the configuration of dynamic mappings
Explanation An internal operation relating to the configuration of the dynamic mappings has failed. This may imply that the mapping has not been installed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPNAT-6-PORT_ALLOC : Port allocation via [chars] for [int] [chars] [chars] ports, min [int] max [int]
Explanation A port allocation request for the specified range of ports has been attempted from the named party on the standby RP. This is an informational message which tracks the request source.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPNAT-3-SBINIT : Error initializing [chars] subblock data structure. [chars]
Explanation Initialization of the specified subblock data structure could not be accomplished.
Recommended Action


%IPNAT-3-IF_UP : Error in sending interface UP event for [chars] to the ager process
Explanation An internal operation relating to the interface UP event has failed which is unexpected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPNAT-3-UNEXPECTED_MAPPING_FLAG : Unexpected mapping flag %#04x received
Explanation An internal operation relating to notifying the platform about a mapping has provided an unexpected input.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPNAT-3-MAPPING_NULL : Unexpected NULL pointer received as input.
Explanation An internal operation relating to notifying the platform about a mapping has provided an unexpected input.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPNAT-3-UNEXPECTED_ADDRESS : NULL
Explanation An address contained an unexpected value.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


IPNAT_HA

%IPNAT_HA-3-MISMATCH : [chars] [chars] mismatch with id [int]
Explanation The specified synchronization operation has failed to complete on the standby route processor due to an inconsistency in the internal id which would have resulted in an inconsistent configuration between active and standby. The resultant action taken by the standby route processor is an attempt to resynchronize.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPNAT_HA-6-MAPPING_EXISTS : [chars] [chars] [chars] mapping id [int]
Explanation The specified synchronization operation on the standby route processor has detected the presence of an existing matching mapping. This may be associated with any observed PRC failures on the standby.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPNAT_HA-6-MAPPING_COMPARE : [chars] [chars] [chars] mapping id [int] comparing [chars] [chars] [chars] mapping id [int]
Explanation The specified synchronization operation on the standby route processor has detected an internal condition with respect to the properities of dynamic mappings. This is informational.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPNAT_HA-3-TRANSFORM : [chars] of [chars] via [chars] failed [chars]
Explanation An attempt to either encode or decode a versioned synchronization message has failed due to an internal error encountered by the ISSU component.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPNAT_HA-3-RECEIVE : Message via [chars] is [chars]
Explanation An attempt to receive and process a versioned negotiation or synchronization message has failed due to an internal error being detected by the information received from the IPC or CF components.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPNAT_HA-3-TRANSMIT : Unable to send via [chars] [chars] [chars] [chars]; [chars]
Explanation An attempt to send a versioned negotiation or synchronization message has failed due to an internal error encountered by the IPC or CF components.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPNAT_HA-3-PROGRESSION : Unable to inform RF of bulk sync completion; [chars]
Explanation The active route processor has sent a notification to the standby to inform of the completion of the bulk synchronization of the NAT configuration. The standby has failed to respond to the active informing that it received the notification noting the reason for the failure. The resultant action taken by the standby route processor is an attempt to resynchronize.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPNAT_HA-3-ISSU : [chars] [chars] failed; [chars]
Explanation An operation pertaining to the ISSU support for NAT failed to complete using either the CF or IPC transport context with the reason specified
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPNAT_HA-3-NEGOTIATION : Failed to start ISSU [chars] session negotiation; [chars]
Explanation The ISSU negotiation with the peer failed to start for either the CF or IPC transport with the reason specified.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPNAT_HA-3-REGISTRATION : ISSU [chars] failed for [chars]; [chars]
Explanation An ISSU registration for the set of initial capabilities and sessions failed due to the reason specified. This will have the effect of the NAT ISSU support being unavailable between peers.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPNAT_HA-3-DECODE : Decode via [chars] of [chars] failed
Explanation A message of the transport and type described failed in its attempt to be decoded on the standby. The resultant action taken by the standby route processor is an attempt to resynchronize.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPNAT_HA-3-BULK_SYNC : Failed to send [chars] information to peer
Explanation The bulk synchronization of the NAT configuration to the standby RP has failed to complete successfully; NAT has therefore taken the action which will result in a reload of the peer in order to once more attempt to successfully synchronize the configuration state which may have failed initially to a transient condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPNAT_HA-3-DYN_SYNC : Failed to process [chars] dynamic state
Explanation The incremental synchronization of the NAT configuration to the standby RP has failed to complete successfully. This implies that the configuration state between the active and standby RP is inconsistent.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show ip nat ha command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPNAT_HA-3-DYN_DEFERQ : [chars] failed to defer[chars]
Explanation The incremental synchronization of the NAT dynamic state to the standby RP has failed to add the information to the deferral queue for later processing during the time where the standby RP is progressing to it's hot standby redundant state. This implies that the runtime state between the active and standby RP would be inconsistent once the standby has been fully initialized.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show ip nat ha command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPNAT_HA-6-TIMEOUT : Bulk sync is flow controlled by [chars]
Explanation The bulk synchronization of the NAT configuration to the standby RP has encountered a flow control condition which has effected a timeout awaiting the condition to clear. This will result in a reload of the standby RP to allow the bulk synchronization to restart.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPNAT_HA-3-CLIENT : Failed to register with [chars], [chars]
Explanation The NAT High Availability has failed to register with the specified component during initialization. This is an internal error which indicates that the NAT HA services will be unavailable.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPNAT_HA-6-READY : [chars] peer not ready, discarding [chars]
Explanation The synchronization attempt for the message has determined that the transport has lost communication with its peer. This is a normal situation which indicates that the standby route-processor is currently out of service implying a simplex redundancy mode.
Recommended Action


%IPNAT_HA-6-RELOAD : [chars], reloading [chars]
Explanation A synchronization attempt between the active and standby RP peers has failed with the reason indicated. The standby peer is reloaded in an attempt to resynchronize when operating in a stateful redundant mode.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPNAT_HA-6-RELOAD_DISABLED : Standby reload has been disabled, NAT RP state is out of sync and the standby should be reloaded manually
Explanation The active and standby RPs are out of sync and the standby RP would have been reloaded, but this reload was suppressed based on the configured environment.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPNAT_HA-3-ATTRIBUTE : Bulk sync of [chars] via [chars], [chars] is invalid for [chars]
Explanation An attempt to bulk sync an address pool or a dynamic/static translation has detected that the entity which is to be sent to the standby RP when acting in a stateful redundant mode contains an invalid owner property and hence cannot be synchronized. The detection of this case will result in a failure of the bulk sync.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPNAT_HA-3-PURGE : Failed to purge [chars] information
Explanation The synchronization of the NAT configuration state to the standby RP has failed to purge an entry which has been deemed to be stale; NAT has therefore taken the action which will result in a reload of the peer in order to once more attempt to successfully synchronize the configuration state which may have failed initially to a transient condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPNAT_HA-6-INTERFACE : [chars] type/slot [hex] uint [int] num [int] channel [int]
Explanation An attempt to sync a dynamic translation or address change has detected that the interface which was encoded on the active RP is not present on the standby RP. The detection of this case may result in a failure of the bulk or LBL sync.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPNAT_HA-3-INTERFACE_TYPE : [chars] type/slot [hex] unit [int] num [int] channel [int] value [int]
Explanation An attempt to sync a dynamic translation or address change has detected that the interface which was encoded on the active RP has a different type the standby RP. The detection of this case will result in a failure of the bulk or LBL sync.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPNAT_HA-6-ADDR_CHANGE : [chars] unable to encode data descriptor for interface [chars]
Explanation An attempt to sync an address change to the standby RP has detected that the interface which was to be encoded on the active RP is no longer present or does not support encoding. The interface may have been removed from the configuration or may not support encoding.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


IPSEC

%IPSEC-3-SA_SOFT_BYTE : SA ([hex],[hex])
Explanation SA Softbyte Lifetime expiry event.
Recommended Action LOG_STD_ACTION


%IPSEC-3-SA_HARD_BYTE : SA ([hex],[hex])
Explanation SA Hardbyte Lifetime expiry event.
Recommended Action LOG_STD_ACTION


%IPSEC-3-IPC_ERR_SA : rc [hex]
Explanation An error has occurred sending SA Byte Lifetime expiry event.
Recommended Action LOG_STD_ACTION


%IPSEC-3-ANTI_REPLAY : SA ([hex],[hex])
Explanation Anti Replay check failed for the SA.
Recommended Action LOG_STD_ACTION


%IPSEC-3-SEQNO_OVERFLOW : SA ([hex],[hex])
Explanation Sequence Number overflow for the SA.
Recommended Action LOG_STD_ACTION


%IPSEC-3-UNEXPECTED_ERROR : orh.w0 [hex], error_op [hex], SA ([hex],[hex])
Explanation Unexpected error for the SA.
Recommended Action LOG_STD_ACTION


%IPSEC-3-INVALID_SPI : spi [hex]
Explanation Got an invalid SPI value.
Recommended Action LOG_STD_ACTION


%IPSEC-3-IN_POLICY_MISS : sa [hex], cp sa [hex]
Explanation TCAM miss.
Recommended Action LOG_STD_ACTION


%IPSEC-3-IN_POLICY_FAIL : out sa ([hex],[hex]), out sp ([hex],[hex]), in sa ([hex],[hex]), in sp ([hex],[hex])
Explanation In-Out SP mis-match.
Recommended Action LOG_STD_ACTION


%IPSEC-3-IPC_PAK_ALLOC_SA_EVENT : event [hex], sa [hex]
Explanation IPC pak allocation failed.
Recommended Action LOG_STD_ACTION


%IPSEC-3-IPC_PAK_SEND_SA_EVENT : rc [hex], event [hex], sa [hex]
Explanation IPC send failed.
Recommended Action LOG_STD_ACTION


%IPSEC-3-IKE_TED_MSG_LIMIT : cnt [dec], sp [hex], cp sp [hex]
Explanation IKE TED Message Limit exceeded.
Recommended Action LOG_STD_ACTION


%IPSEC-3-IKE_TED_MSG_RATE : cnt [dec], sp [hex], cp sp [hex]
Explanation IKE TED Message Rate exceeded.
Recommended Action LOG_STD_ACTION


%IPSEC-3-IPC_PAK_ALLOC : sp [hex], cp sp [hex]
Explanation IPC pak allocation failed.
Recommended Action LOG_STD_ACTION


%IPSEC-3-IPC_PAK_SEND : rc [hex], sp [hex], cp sp [hex]
Explanation IPC send failed.
Recommended Action LOG_STD_ACTION


%IPSEC-3-INVALID_VAL : val [hex]
Explanation Invalid value seen.
Recommended Action LOG_STD_ACTION


%IPSEC-3-IPC_HANDLER_ERR : rc [hex]
Explanation Error setting IPC Handler.
Recommended Action LOG_STD_ACTION


%IPSEC-3-DROP : result type [hex]
Explanation Classification results in Drop.
Recommended Action LOG_STD_ACTION


%IPSEC-3-INVALID_SA : sa [hex], cp sa [hex]
Explanation SA is invalid.
Recommended Action LOG_STD_ACTION


%IPSEC-3-SA_NOT_FOUND :
Explanation SA not found.
Recommended Action LOG_STD_ACTION


%IPSEC-3-FOR_US_CLEARTEXT_POLICY_FAIL :
Explanation Policy fail for For-Us cleartext packet.
Recommended Action LOG_STD_ACTION


%IPSEC-3-TRANSIT_POLICY_FAIL :
Explanation Policy fail for transit ipsec packet.
Recommended Action LOG_STD_ACTION


%IPSEC-3-INTF_NOT_CFG :
Explanation Got an encrypted packet on an interface on which ipsec is not configured.
Recommended Action LOG_STD_ACTION


%IPSEC-3-FRAG_MPASS :
Explanation Multipass Error
Recommended Action LOG_STD_ACTION


%IPSEC-3-INVALID_PROT : invalid ipsec prot [hex]
Explanation Got an invalid IPSEC protocol value.
Recommended Action LOG_STD_ACTION


%IPSEC-3-NO_MEMORY : No memory [hex]
Explanation No memory to send response back.
Recommended Action LOG_STD_ACTION


%IPSEC-3-MEM_REQ_FAILED : IPC type [hex]
Explanation Requesting more memory failed.
Recommended Action LOG_STD_ACTION


%IPSEC-3-CHUNK_CREATE_FAIL :
Explanation Chunk creation failed
Recommended Action LOG_STD_ACTION


%IPSEC-3-CHUNK_DESTROY_FAIL :
Explanation Chunk destroy failed
Recommended Action LOG_STD_ACTION


%IPSEC-3-CHUNK_DESTROY_ERROR :
Explanation Chunk destroy error, force cleanup
Recommended Action LOG_STD_ACTION


%IPSEC-3-MEM_EXTEND_FAILED : IPC type [hex]
Explanation Extending memory failed
Recommended Action LOG_STD_ACTION


%IPSEC-3-IPC_INVALID_MSG_LEN : [dec]:[dec] len [dec] flags [hex] source [dec]
Explanation Invalid IPC message length
Recommended Action LOG_STD_ACTION


%IPSEC-3-MEM_ALLOC_REACHED_LIMIT : IPC type [hex]
Explanation Cannot allocate more memory to store state for IPSec Traffic, reached upper limit.
Recommended Action LOG_STD_ACTION


%IPSEC-3-PKT_TOO_BIG : IPSec Packet size [dec] larger than maximum supported size [dec] hence dropping it, MSGDEF_LIMIT_GLACIAL
Explanation Maximum size for packet with IPSEC encapsulation is 9K, This packet exceeded the size limit hence dropping it.
Recommended Action LOG_STD_ACTION


%IPSEC-3-REPLAY_ERROR : IPSec SA receives anti-replay error, DP Handle [dec], src_addr %Ci, dest_addr %Ci, SPI [hex], MSGDEF_LIMIT_GLACIAL
Explanation Anti-replay error is encountered for this IPSec session.
Recommended Action LOG_STD_ACTION


%IPSEC-3-REPLAY_ERROR_IPV6 : IPSec SA receives anti-replay error, DP Handle [dec], ipv6 src_addr %CI, ipv6 dest_addr %CI, SPI [hex], MSGDEF_LIMIT_GLACIAL
Explanation Anti-replay error is encountered for this IPSec session.
Recommended Action LOG_STD_ACTION


%IPSEC-3-RECVD_PKT_NOT_IPSEC : Rec'd packet not an IPSEC packet, dest_addr= %Ci, src_addr= %Ci, prot= [dec], MSGDEF_LIMIT_GLACIAL
Explanation Rec'd packet matched crypto map ACL, but is not IPSEC-encapsulated.
Recommended Action LOG_STD_ACTION


%IPSEC-3-RECVD_PKT_NOT_IPSECV6 : Rec'd packet not an IPSEC packet, dest_addr= %CI, src_addr= %CI, prot= [dec], MSGDEF_LIMIT_GLACIAL
Explanation Rec'd packet matched crypto map ACL, but is not IPSEC-encapsulated.
Recommended Action LOG_STD_ACTION


%IPSEC-3-HMAC_ERROR : IPSec SA receives HMAC error, DP Handle [dec], src_addr %Ci, dest_addr %Ci, SPI [hex], MSGDEF_LIMIT_GLACIAL
Explanation HMAC calculation error is encountered for this IPSec session.
Recommended Action LOG_STD_ACTION


%IPSEC-3-HMAC_ERROR_V6 : IPSec SA receives HMAC error, DP Handle [dec], ipv6 src_addr %CI, ipv6 dest_addr %CI, SPI [hex], MSGDEF_LIMIT_GLACIAL
Explanation HMAC calculation error is encountered for this IPSec session.
Recommended Action LOG_STD_ACTION


%IPSEC-3-FRAG_ERROR : IPSec SA received fragmented ESP packet, DP Handle [dec], src_addr %Ci, dest_addr %Ci, SPI ([hex]), MSGDEF_LIMIT_GLACIAL
Explanation Fragmented ESP packet is received for this IPSec session.
Recommended Action LOG_STD_ACTION


%IPSEC-3-FRAG_ERROR_IPV6 : IPSec SA received fragmented ESP packet, DP Handle [dec], ipv6 src_addr %CI, ipv6 dest_addr %CI, SPI ([hex]), MSGDEF_LIMIT_GLACIAL
Explanation Fragmented ESP packet is received for this IPSec session.
Recommended Action LOG_STD_ACTION


IPV4_FORWARDING

%IPV4_FORWARDING-2-CAUSE_THROTTLE_ERR : Allocation of ipv4 throttle [chars] memory failed
Explanation Allocation of memory resource use by ipv4 throttle fail
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPV4_FORWARDING-3-CAUSE_LINKTYPE_ERR : Unsupported link type - linktype = [dec], dropping packet
Explanation Link type is unsupported at the current time.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPV4_FORWARDING-4-CHECKSUM_ERR : Checksum buffer walk failed
Explanation Internal problem occured during calculating segmented packet checksum.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPV4_FORWARDING-3-TABLE_ID_SZ_ERR : Table ID size configured incorrectly: [dec]
Explanation Table ID size must be less than or equal to 16 or 32 bits.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPV4_FORWARDING-3-TRAFFIC_IDX_ERR : Traffic index invalid value: [dec] Buckets allocated: [dec]
Explanation Traffic index is greater than or equal to the buckets allocated
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


IPV4_REASS_PROXY

%IPV4_REASS_PROXY-3-PROXY_IPC_FRAG_INFO_MEM_INIT_FAILED :
Explanation Initialization of fragment information pool failed.
Recommended Action LOG_STD_ACTION


%IPV4_REASS_PROXY-3-PROXY_IPC_FRAG_INFO_MEM_EXTEND_FAILED :
Explanation Increasing of fragment information pool failed.
Recommended Action LOG_STD_ACTION


%IPV4_REASS_PROXY-3-PROXY_IPC_INIT_FAILED : [dec]
Explanation IPC handler initialization failed.
Recommended Action LOG_STD_ACTION


%IPV4_REASS_PROXY-4-PROXY_IPC_INVALID_MSG : [hex]
Explanation Received an invalid IPC messages subtype.
Recommended Action LOG_STD_ACTION


IPV6_ACL

%IPV6_ACL-6-ACCESSLOGNP : list [chars]/[dec] [chars] [dec] [IPV6 address] [chars]-> [IPV6 address], [dec] packet[chars]
Explanation A packet matching the log criteria for the given access list was detected.
Recommended Action No action is required.


%IPV6_ACL-6-ACCESSLOGDP : list [chars]/[dec] [chars] [chars] [IPV6 address] [chars]-> [IPV6 address] ([dec]/[dec]), [dec] packet[chars]
Explanation A packet matching the log criteria for the given access list was detected.
Recommended Action No action is required.


%IPV6_ACL-6-ACCESSLOGSP : list [chars]/[dec] [chars] [chars] [IPV6 address] [chars]-> [IPV6 address], [dec] packet[chars]
Explanation A packet matching the log criteria for the given access list was detected.
Recommended Action No action is required.


%IPV6_ACL-6-ACCESSLOGP : list [chars]/[dec] [chars] [chars] [IPV6 address]([dec]) [chars]-> [IPV6 address]([dec]), [dec] packet[chars]
Explanation A packet matching the log criteria for the given access list was detected.
Recommended Action No action is required.


IPV6_ADDRESS through IRECAGENTSERVER

IPV6_ADDRESS

%IPV6_ADDRESS-3-INTERNAL : Internal error, [chars]
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPV6_ADDRESS-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.


%IPV6_ADDRESS-3-NO_PROCESS : Cannot start an IPv6 process; router will not process IPv6 packets.
Explanation An 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.


%IPV6_ADDRESS-3-ADDRESS_CFG : [IPV6 address]/[dec] can not be configured on [chars], [chars]
Explanation An error was encountered while configuring an IPv6 address
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPV6_ADDRESS-3-NULLIDB : Uninitialized interface pointer - [chars]
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPV6_ADDRESS-3-OPINPROGRESS : Operation in progress - [chars]
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


IPV6_ADDRMGR

%IPV6_ADDRMGR-3-INTERNAL : Internal error, [chars]
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


IPV6_FORWARDING

%IPV6_FORWARDING-2-CAUSE_THROTTLE_ERR : Allocation of ipv6 throttle [chars] memory failed
Explanation Allocation of memory resource use by ipv6 throttle fail
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPV6_FORWARDING-3-CAUSE_LINKTYPE_ERR : Unsupported link type [chars], dropping packet
Explanation Link type is unsupported at the current time.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPV6_FORWARDING-4-CHECKSUM_ERR : Checksum buffer walk failed
Explanation Internal problem occured during calculating segmented packet checksum.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPV6_FORWARDING-3-TABLE_ID_SZ_ERR : Table ID size configured incorrectly: [dec]
Explanation Table ID size must be less than or equal to 16 or 32 bits.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


IPV6_POLICY_API

%IPV6_POLICY_API-4-IPV6_POLICYOVERIDE : Dynamic policy overriding static on intf:[chars]
Explanation Static policy and dynamic policy are configured on the interface. The dynamic policy will override the static policy.
Recommended Action Remove the static policy config if desired.


%IPV6_POLICY_API-4-IPV6_LOCALPOLICYOVERIDE : Local dynamic policy overriding static local policy
Explanation Static policy and dynamic local policy are configured. The dynamic local policy will override the static local policy.
Recommended Action Remove the static local policy config if desired.


IPV6_REASS_PROXY

%IPV6_REASS_PROXY-3-PROXY_IPC_FRAG_INFO_MEM_INIT_FAILED :
Explanation Initialization of fragment information pool failed.
Recommended Action LOG_STD_ACTION


%IPV6_REASS_PROXY-3-PROXY_IPC_FRAG_INFO_MEM_EXTEND_FAILED :
Explanation Increasing of fragment information pool failed.
Recommended Action LOG_STD_ACTION


%IPV6_REASS_PROXY-3-PROXY_IPC_INIT_FAILED : [dec]
Explanation IPC handler initialization failed.
Recommended Action LOG_STD_ACTION


%IPV6_REASS_PROXY-4-PROXY_IPC_INVALID_MSG : [hex]
Explanation Received an invalid IPC messages subtype.
Recommended Action LOG_STD_ACTION


IPV6_RIP

%IPV6_RIP-3-NULLIDB : Uninitialized interface pointer - RIPv6
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPV6_RIP-3-NULLPAK : Uninitialized packet pointer - RIPv6
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPV6_RIP-3-NULLPDB : Uninitialized PDB pointer - RIPv6
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPV6_RIP-3-NULLIPDB : Uninitialized iPDB pointer - RIPv6
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPV6_RIP-3-NULLPROTO : Uninitialized protocol pointer - RIPv6
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPV6_RIP-3-NULLSOC : Uninitialized socket pointer - RIPv6
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPV6_RIP-3-ALLOC_PDB : Can't alloc PDB structure - RIPv6
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPV6_RIP-3-ALLOC_IPDB : Can't alloc iPDB structure - RIPv6
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPV6_RIP-3-PROCESS_CREATE : Can't create process - RIPv6
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPV6_RIP-3-ALLOC_ERR : Memory allocation problem - RIPv6
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%IPV6_RIP-3-PROCESS_MSG_SEND : Can't send message to process - RIPv6
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


IP_SNMP

%IP_SNMP-3-SOCKET : can't open UDP socket
Explanation The SNMP server was unable to open a port for receiving or transmitting SNMP requests. This usually happens when the SNMP server is started using the snmp-server community configuration command on a router or communication server with an interface that has no IP address configured. Another possible cause is low memory.
Recommended Action Configure at least one interface with an IP address or specify the no snmp-server command to remove the SNMP server process. Call your technical support representative if problems persist or if it becomes necessary to add memory.


%IP_SNMP-4-NOTRAPIP : SNMP trap source [chars] has no ip address
Explanation 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.


%IP_SNMP-4-NOTRAPIPV6 : SNMP trap source [chars] has no ipv6 address
Explanation The user entered an snmp-server trap-source command. The interface requested for use as the source address has no ipv6 address associated with it. The SNMP trap is being sent anyway, but without the source address that the user intended.
Recommended Action There are two possible solutions. Either enter a no snmp-server trap-source command to disable the request for a specific source IP address, or add an IPV6 address to the interface referenced in the snmp-server trap-source configuration command.


%IP_SNMP-4-TOOBIG : Oversize message from [IP_address], datagram size [int], udp length [int]
Explanation An incoming SNMP packet had a length field so large that the system had to assume it was in error. This system 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.


IP_TUNNEL

%IP_TUNNEL-3-IPC_OPEN_REPLY : IPC Open Reply failed, request [int]
Explanation For a request from upper TUNNEL software stack layers it was not possible to open the reply buffer. The consequence of this could be a stuck monitor that cannot be established etc. In rare cases this could also affect other operations such as feature activation.
Recommended Action This is normally a software issue. LOG_STD_RECUR_ACTION


%IP_TUNNEL-3-IPC_NORES : No space for the IPC reply, size [int]
Explanation For a request from upper TUNNEL software stack layers it was not possible to allocate space for a reply for the specified size. The consequence of this could be a stuck monitor that cannot be established etc. In rare cases this could also affect other operations such as feature activation.
Recommended Action This is normally a software issue. LOG_STD_RECUR_ACTION


%IP_TUNNEL-2-IPC_INIT : IPC message handler registration failure, rc [int]
Explanation Registering an IPC message handler for the Tunnel feature failed. This may cause the feature to not function.
Recommended Action This is normally a software issue. The consequences are that the tunnel feature may not function. LOG_STD_ACTION


IP_VFR

%IP_VFR-4-TINY_FRAGMENTS : [chars]: from the host [IP_address] destined to [IP_address]
Explanation This message indicates that the router is receiving tiny fragments - meaning the initial fragment does not have complete layer 4 header
Recommended Action This is an informational message


%IP_VFR-3-OVERLAP_FRAGMENTS : [chars]: from the host [IP_address] destined to [IP_address]
Explanation This message is logged whenever the router encounters overlap fragments. Overlap fragment means, offset of one fragment overlaps the offset of another fragment. For example, if first fragment's offset is 0 and length is 800, then the second fragments offset must be 800. If second fragment's offset is less than 800, that means the second fragment overlaps the first fragment.
Recommended Action This could possibly be an attack, configure a static ACL to prevent further overlap fragments from the sender


%IP_VFR-4-FRAG_TABLE_OVERFLOW : [chars]: the fragment table has reached its maximum threshold [dec]
Explanation This means the number of datagrams reassembled at a time reached its maximum limit, increase the value of max-reassemblies using ip virtual-reassembly max-reassemblies <number>
Recommended Action


%IP_VFR-4-TOO_MANY_FRAGMENTS : [chars]: Too many fragments per datagram (more than [dec]) - sent by [IP_address], destined to [IP_address]
Explanation This message indicates the datagram being reassembled has received more fragments than its threshold value
Recommended Action Check if the fragments received are from a genuine source, if so increase the value of max-fragments using the CLI ip virtual-reassembly max-fragments <number>


%IP_VFR-3-INVALID_FRAG_LENGTH : [chars]: fragment length invalid - received from [IP_address], destined to [IP_address]
Explanation This message indicates that the router has encountered a ping-of-death sort of an attack
Recommended Action To prevent further attacks, its highly recommendated that an ACL be configured to drop any traffic from the sender


%IP_VFR-3-SYSTEM_ERROR : [chars]: IP VFR System failure - [chars]
Explanation This message indicates the misc errors in the VFR subsystem
Recommended Action


IRECAGENTSERVER

%IRECAGENTSERVER-3-NOINIT : Can't initialize iREC agent server
Explanation Internal problems with initializing ports for the iREC agentserver
Recommended Action Make sure the iREC agent server port is available on the localmachine.


%IRECAGENTSERVER-3-NOMEM : Can't initialize memory for iREC agent server
Explanation Insufficient Memory for iREC agent server
Recommended Action Increase amount of available memory


%IRECAGENTSERVER-3-NOSOCKETS : Max Number of iREC agent Server sockets exceeded
Explanation There are too many iREC agent clients requesting service
Recommended Action Reduce number of iREC agent requesting service


%IRECAGENTSERVER-3-NOPROC : Could not start iREC agent Server
Explanation Internal Problem in process creation
Recommended Action None