IPACCESS through MPLS_TP_LINK

IPACCESS through IPSEC

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 http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at https://mycase.cloudapps.cisco.com/case, or contact your Cisco technical support representative and provide the representative with the gathered information.


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 through IP_SNMP

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

%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_ADDRESS-3-RESERVED_INTFID : Removing [IPV6 address] from [chars] - contains reserved interface identifier. [chars]
Explanation Removing IPv6 global address contains the reserved interface identifier
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center 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 through IVR_NOSIGNALING

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


ISDN

%ISDN-6-CONNECT : Interface [chars] is now connected to [chars] [chars]
Explanation This is an informational message sent when a call is connected. The message displays the remote name and number, which it receives from the Point-to-Point Protocol (PPP) authentication or from where the dialer placed the call to.
Recommended Action No action is required.


%ISDN-6-DISCONNECT : Interface [chars] disconnected from [chars] [chars], call lasted [int] seconds
Explanation This is an informational message sent when a call is disconnected. The message displays the remote name and number, which it receives from the Point-to-Point Protocol (PPP) authentication or from where the dialer placed the call to. It also shows how long the call lasted.
Recommended Action No action is required.


%ISDN-1-NOMEMORY : no memory for [chars]
Explanation The requested operation could not be accomplished because of a low memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.


%ISDN-4-INVALID_SPID : Interface [chars], Spid[dec] was rejected
Explanation The SPID configured in the router has been rejected by the switch.
Recommended Action Determine the correct SPID, reenter the SPID and clear the BRI interface.


%ISDN-4-INVALID_CALLEDNUMBER : Interface [chars], Ignoring call, LDN and Called Party Number mismatch
Explanation The incoming ISDN call is ignored because the Called Party Number does not match the LDN numbers configured in the router.
Recommended Action Correct the LDN in the router to match the Called Party Number delivered in the incoming setup message.


%ISDN-4-INVALID_EID : Interface [chars], Ignoring call, EndPoint Identifier (EID) mismatch
Explanation The incoming ISDN call is ignored because the EID delivered in the incoming setup message cannot be matched.
Recommended Action If EID is delivered in the setup message, use the isdn debugs and show isdn status commands to determine the current EID values. You may need to contact the service provider.


%ISDN-6-LAYER2UP : Layer 2 for Interface [chars], TEI [int] changed to up
Explanation This is an informational message. It is sent when an ISDN Layer2 logical link is up. It also shows the TEI associated with this logical link.
Recommended Action No action is required.


%ISDN-3-LAYER2_UP : Layer 2 for Interface [chars], TEI [int] changed to up
Explanation This is an informational message but being logged as an ERR at request from some customers. It is sent when an ISDN Layer2 logical link is up. It also shows the TEI associated with this logical link.
Recommended Action No action is required.


%ISDN-6-LAYER2DOWN : Layer 2 for Interface [chars], TEI [int] changed to down
Explanation This is an informational message. It is sent when an ISDN Layer2 logical link is down. It also shows the TEI associated with this logical link.
Recommended Action No action is required.


%ISDN-3-LAYER2_DOWN : Layer 2 for Interface [chars], TEI [int] changed to down
Explanation This is an informational message but being logged as ERR at request from some customers. It is sent when an ISDN Layer2 logical link is down. It also shows the TEI associated with this logical link.
Recommended Action No action is required.


%ISDN-6-CHAN_UNAVAILABLE : Interface [chars] Requested Channel [dec] is not available
Explanation This is an informational message. It is sent when the requested channel is not available.
Recommended Action No action is required.


%ISDN-6-CALL_COLLISION : Interface [chars] Call Cid [hex] Cref [hex] collision on Channel [dec] in_use_cid [hex] cref [hex], Channel awarded to the received call
Explanation This is an informational message. It is sent when a Call is received that collides with an existing call on the same channel.
Recommended Action No action is required.


%ISDN-6-NO_TIMER : No Free Timer Entry, caller [hex], timers used [dec]
Explanation This could be an indication of low memory. It is sent when the ISDN protocol cannot start new timers for it's operation.
Recommended Action capture the show isdn mem, show isdn status output for possible debugging information. Reduce other system activity to ease the memory demands in the system.


%ISDN-6-INVALID_TIMER : [chars]: Invalid Timer Handle, caller [hex] handle %3d
Explanation This could be an indication of low memory. It is sent when an invalid ISDN timer handle is passed on for timer operations
Recommended Action capture the show isdn mem, show isdn status output for possible debugging information. Reduce other system activity to ease the memory demands in the system.


%ISDN-4-INVALID_EVENT : [chars]: Bad Event Received For Current State
Explanation The State Transition for the ISDN L2 Socket Process 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.


%ISDN-4-SPURIOUS_CONNECT : [chars]: Spurious Connection Accepted and Closed on port [int]
Explanation An unknown TCP connection was accepted and refused.
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.


%ISDN-4-GET_STATUS_STATE_FAIL : [chars]: isdn_get_status_state: Unknown DSL [int]
Explanation An attempt to retrieve the status of a DSL that is not currently configured.
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.


%ISDN-4-ISDN_L2_INTERFACE_NOT_REGISTERED : [chars]: isdn_to_L2: Unknown DSL [int] for command [chars]
Explanation The ISDN Stack has not registered its L2 Message Handler
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.


%ISDN-4-BAD_DSL_FOR_CREATE_DELETE_L2 : [chars]: isdn_create_delete_signalling_channel: Unknown DSL [int] for [chars]
Explanation The Creation/Deletion service for the L2 Signalling handlerfor the given DSL is missing
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.


%ISDN-4-OPEN_TEMP_SOCKET_FAIL : [chars]: Failed to Open Required Temporary Socket[chars]
Explanation The (Re)Open attempt for a required temporary socket failed,without this socket the L2 socket process will fail
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.


%ISDN-4-ISDN_UNEXPECTED_EVENT : [chars]: Occurred at [chars]:[dec]
Explanation An unexpected event of significance has occurred
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. 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.


%ISDN-4-RLM_STATUS_CHANGE : ISDN SC [chars]: Status Changed to: [chars].
Explanation ISDN has been notified by the RLM component of a status change in the RLM link
Recommended Action No action is required.


%ISDN-2-ISDN_GENERAL_TRACEBACK : [chars]:[dec]
Explanation A debug - traceback condition has occurred
Recommended Action No action is required.


%ISDN-3-ISDN_RESOURCE_UNAVAILABLE : [chars]: Resource not available, at [chars]:[dec]
Explanation Hardware resource could not be 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.


%ISDN-2-ISDN_FATAL : ISDN FATAL ERROR: file [chars], function [chars], message: [chars]
Explanation ISDN has detected a fatal system 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.


%ISDN-3-ISDN_CCB_FREE : [chars]: CCB with call id [hex] on b channel [dec] was leaked, but has been freed by ISDN Housekeeping. Reason: [chars]
Explanation A data structure internal to ISDN has leaked.
Recommended Action No action is required.


%ISDN-3-ISDN_CCB_FREE_FAILS : [chars]: CCB with call id [hex] on b channel [dec] was leaked (reason: [chars]), and can't be free'd by ISDN Housekeeping.
Explanation A data structure internal to ISDN has leaked and we can't fix it for some reason.
Recommended Action No action is required.


%ISDN-4-ISDN_CCB_LEAK : [chars]: CCB with callid [hex] on b channel [dec] has been leaked. Reason: [chars]
Explanation A data structure internal to ISDN has been leaked
Recommended Action No action is required.


%ISDN-4-SERVICE : Interface [chars] [chars] [chars] message for chan [dec] state [chars]
Explanation This is an informational message but will be logged as a warning message if so configured.
Recommended Action No action is required.


%ISDN-4-RESTART : Interface [chars] [chars] [chars] message with restart class of [chars] chan [dec]
Explanation This is an informational message but will logged as a warning message if so configured.
Recommended Action No action is required.


%ISDN-4-STATUS : Interface [chars] [chars] [chars] st [hex] ev [hex] cid [hex] cref [hex]
Explanation This is an informational message but being logged as a warning message if so configured.
Recommended Action No action is required.


%ISDN-4-SERV_AUDIT_C1 : Interface [chars] service audit trigger condition [dec] on channel [dec]
Explanation This is an informational message but will be logged as a warning message if so configured.
Recommended Action No action is required.


%ISDN-5-SERV_AUDIT_C2 : Interface [chars] service audit trigger condition [dec] on channel [dec]
Explanation This is an informational message but will be logged as a warning message if so configured.
Recommended Action No action is required.


%ISDN-6-SERV_AUDIT_C3 : Interface [chars] service audit trigger condition [dec] on channel [dec]
Explanation This is an informational message but will be logged as a warning message if so configured.
Recommended Action No action is required.


%ISDN-4-ISDN_NLCB_LEAK : [chars]: NLCB leak detected. nlcb [hex] call id [hex] reason: [chars]
Explanation A data structure internal to ISDN has not been freed
Recommended Action No action is required.


%ISDN-3-ISDN_NLCB_FREE : [chars]: NLCB with call id [hex] was leaked, but has been freed by ISDN Housekeeping. Reason: [chars]
Explanation A data structure internal to ISDN has leaked.
Recommended Action No action is required.


%ISDN-6-REPEATED_SETUP : Interface [chars] Call Cid [hex] Cref [hex] received a retransmitted setup on channel [dec] in_use_cid [hex] cref [hex].
Explanation This is an informational message sent when a duplicate SETUP message is received on a B-channel. This indicates that the rate of calls being received is momentarily greater than the rate calls can be processed. No action is required.
Recommended Action No action is required.


%ISDN-6-NFAS_STATUS_CHANGE : [chars] [chars] [chars] [chars]
Explanation The NFAS D-channel status has changed.
Recommended Action No action is required.


%ISDN-2-ISDN_EXIT : [chars]
Explanation The ISDN task has terminated execution for the specified reason, and may cause CISCO IOS to terminate.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


ISR4000_RP_NGIO_ATM

%ISR4000_RP_NGIO_ATM-4-SETUPVC : Interface [chars], VC ([dec]) setup failed, reason = [dec]
Explanation A command to setup a VC has failed on RP.
Recommended Action The SPA ATM driver has detected a problem creating the internal OAM VC. Reload the indicated SPA card to reconfigure the internal OAM VC. If the error messages persists, copy the error message exactly as it appears. Next research and attempt to resolve the issue using the SPA hardware troubleshooting documentation as well as the tools and utilities provided at http://www.cisco.com/public/support/tac/tools.shtml. If you still require assistance, open a case with the Technical Assistance Center via the Internet at https://mycase.cloudapps.cisco.com/case or contact your Cisco technical support representative. Be sure to provide the the information you have gathered and a 'show tech-support' to your support representative, or attach it to your case in non-zipped, plain text format (.txt).


%ISR4000_RP_NGIO_ATM-4-TEARDOWNVC : Interface [chars], VC ([dec]) teardown failed, (vc state = [dec]/[dec])
Explanation A command to remove a VC config has failed on RP.
Recommended Action The SPA ATM driver has detected a problem tearing down the internal OAM VC. Reload the indicated SPA card to do a clean tear down of the internal OAM VC. If the error messages persists, copy the error message exactly as it appears. Next research and attempt to resolve the issue using the SPA hardware troubleshooting documentation as well as the tools and utilities provided at http://www.cisco.com/public/support/tac/tools.shtml. If you still require assistance, open a case with the Technical Assistance Center via the Internet at https://mycase.cloudapps.cisco.com/case or contact your Cisco technical support representative. Be sure to provide the the information you have gathered and a 'show tech-support' to your support representative, or attach it to your case in non-zipped, plain text format (.txt).


%ISR4000_RP_NGIO_ATM-5-MPVCVPSETUP : Interface [chars] has a VC/VP ([dec]) configured already, VC/VP ([dec]) cannot be configured.
Explanation The SPA ATM driver supports configuring only one VC/VP under a point to multi point sub-interface. The sub-interface specified in the message already has VP/VC configured.
Recommended Action No action is required.


%ISR4000_RP_NGIO_ATM-3-ATM_FLOWID_GET_FAIL : Failed to get a flow control identifier for interface [chars] for index [dec]
Explanation The SPA driver is not able to obtain the datapath flow control identifier for the data path identifier under the interface specified in the message. This indicates a software error.
Recommended Action No action is required.


%ISR4000_RP_NGIO_ATM-3-ATM_DPIDB_ALLOC_FAIL : Failed to allocate a data plane identifier for interface [chars] for VCD [dec]
Explanation The SPA driver is not able to allocate the datapath identifier for the VCD under the interface specified in the message. This indicates a software error.
Recommended Action No action is required.


%ISR4000_RP_NGIO_ATM-3-ATM_VC_INGRESS_ID_ALLOC_FAIL : Failed to allocate VC ingress identifier on interface [chars] for VCD [dec] ebfc_id [dec] when [chars]
Explanation The ATM SHIM is not able to allocate the ingress identifier for the VCD under the interface specified in the message. This indicates a software error.
Recommended Action No action is required.


%ISR4000_RP_NGIO_ATM-3-ATM_DPIDB_GET_FAIL : Failed to get a data plane identifier for interface [chars] for VCD [dec]
Explanation The SPA driver is not able to obtain the datapath identifier for the VCD under the interface specified in the message. This indicates a software error.
Recommended Action No action is required.


%ISR4000_RP_NGIO_ATM-3-ATM_TXCHANL_GET_FAIL : Failed to get a valid tx_chan id for interface [chars] for VCD [dec]
Explanation The SPA driver is not able to obtain the datapath tx channel identifier for the VCD under the interface specified in the message. This indicates a SPA occur error.
Recommended Action No action is required.


%ISR4000_RP_NGIO_ATM-3-ATM_VC_SPA_SETUP_FAIL : SPA Error response on interface [chars] when [chars] for VCD [dec] ebfc_id [dec] ret_val [dec]
Explanation The SPA give a error response for ATM setup or response timeout in atm vc setup message. This indicates a SPA occur error.
Recommended Action No action is required.


%ISR4000_RP_NGIO_ATM-3-ATM_VC_CFG_SEND_FAIL : Error in sending message to SPA on interface [chars] when [chars] for VCD [dec] ebfc_id [dec]
Explanation The SPA give a error response for ATM setup or response timeout in atm vc setup message. This indicates a SPA occur error.
Recommended Action No action is required.


%ISR4000_RP_NGIO_ATM-3-ATM_VC_CORE_GET_FAIL : Failed to get a ATM VC core info for interface [chars] VCD [dec]
Explanation Could not get VC core information when get SPA VCOPEN or VCMODIRY response. This indicates a ATM information error.
Recommended Action No action is required.


%ISR4000_RP_NGIO_ATM-3-ATM_VC_ENCAP_GET_FAIL : Failed to get ATM encapsulation for interface [chars] ([dec]/[dec]) VCD [dec]
Explanation Could not get VC encapsulation information when get SPA VCOPEN or VCMODFY response This indicates ATM occur error.
Recommended Action No action is required.


%ISR4000_RP_NGIO_ATM-3-ATM_VC_ERROR_ENCAP_TYPE : Get ATM ERROR encapsulation for interface [chars] ([dec]/[dec]) VCD [dec]
Explanation Get a ERROR VC encapsulation information when get SPA VCOPEN or VCMODFY response This indicates ATM occur error.
Recommended Action No action is required.


%ISR4000_RP_NGIO_ATM-3-ATM_VC_CON_SET_FAIL : Failed set ATM con for interface [chars] ([dec]/[dec]) VCD [dec]
Explanation Could not get VC encapsulation information when get SPA VCOPEN or VCMODFY response This indicates ATM occur error.
Recommended Action No action is required.


%ISR4000_RP_NGIO_ATM-3-ATM_VC_EGRESSID_UPDATE_FAIL : Failed to update ATM egress id for interface [chars] VCD [dec] egress_id [dec]
Explanation Could not update VC egress id when get SPA VCOPEN or VCMODFY response This indicates ATM occur error.
Recommended Action No action is required.


%ISR4000_RP_NGIO_ATM-3-ATM_VC_DPIDX_GET_FAIL : Failed to get ATM dpidx for interface [chars] VCD [dec]
Explanation Could not get VC dpidx information when get SPA VCOPEN or VCMODFY response This indicates ATM occur error.
Recommended Action No action is required.


%ISR4000_RP_NGIO_ATM-3-PROCESS_FAIL : process creation failed for [chars]
Explanation The Periodic one second process creation failed. This indicates 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.


%ISR4000_RP_NGIO_ATM-3-ATM_SPA_AUTOVC_FAIL : [chars]: atm autovc discovery configuration failed, reason: [chars]
Explanation A command to configure the atm autovc discovery on an atm 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.


%ISR4000_RP_NGIO_ATM-3-ATM_SPA_VC_MAX_LIMIT_REACHED : total active atm vc reached system limitation of [dec]
Explanation total number of active atm vc has reached max limit allowed on the 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.


%ISR4000_RP_NGIO_ATM-4-ATM_SPA_VC_ABOVE_WM_WARNING : total active atm vc approaching [int] percent of system limitation of [dec]
Explanation total number of active atm vc is approaching the high water mark of sysyem limitation
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%ISR4000_RP_NGIO_ATM-5-ATM_SPA_VC_BELOW_WM_NOTICE : total active atm vc below [int] percent of system limitation of [dec]
Explanation total number of active atm vc below the high water mark of sysyem limitation
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%ISR4000_RP_NGIO_ATM-3-ATM_PER_SPA_MAX_VC_LIMIT_REACHED : total active atm vc per ATM SPA reached limitation of [dec]
Explanation total number of active atm vc per ATM SPA has reached max limit
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%ISR4000_RP_NGIO_ATM-3-ATM_FLOWID_OUT_OF_RANGE : Flow control identifiers for interface [chars] (chan lo [hex] chan hi [hex]) are out of range, Index [hex]
Explanation The flow control identifier received for the interface is out of range. This indicates SPA driver is responding with out of range flow control identifier
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


ISR_THROUGHPUT

%ISR_THROUGHPUT-3-SETUP_FAILED : Throughput upgrade license set up failed
Explanation An error occurred when setting up the throughput upgrade licenses.
Recommended Action


%ISR_THROUGHPUT-6-LEVEL : Throughput level has been set to [dec]00 kbps
Explanation Throughput level has been set to a number
Recommended Action


%ISR_THROUGHPUT-6-CRYPTO : Crypto level has been set to [dec]00 kbps
Explanation Crypto level has been set to a number
Recommended Action


%ISR_THROUGHPUT-6-UNTHROTTLED : Crypto level is unthrottled
Explanation Crypto level has been unthrottled
Recommended Action


%ISR_THROUGHPUT-3-CONF_FAILED : Configuration failed
Explanation An error occurred when the throughput configuration was attempted.
Recommended Action


%ISR_THROUGHPUT-3-EULA_NOT_ACCEPTED : The EULA has to be accepted prior to throughput configuration.
Explanation Users need to accept EULA to activate the license
Recommended Action Accept EULA for throughput license


%ISR_THROUGHPUT-3-INVALID_CONFIG : An invalid throughput config: [chars] kbps was selected.
Explanation The configured throughput is unknown
Recommended Action


ISSU

%ISSU-3-BOOT_SYNC : Problem with sync of ISSU boot state - [chars]
Explanation The ISSU state between two FRUs is not properly synchronized as a result of a boot error.
Recommended Action This message will automatically appear during certain events, such as during a FRU removal or if the FRU loses connectivity. In most cases, the router will resynchronize the ISSU state between the FRUs without any user intervention. If the ISSU state is not resynchronized after multiple attempts, the problem is likely a result of another problem. Monitor the other system messages to see if a more serious issue has occurred on your router. If you are unable to resolve this other issue and this message persists, gather the output of show tech-support and provide it to a Cisco technical support representative.


%ISSU-0-BOOT_SYNC_FAIL : Problem with sync of ISSU boot state - [chars]
Explanation The ISSU state between two FRUs is not properly synchronized as a result of a boot error.
Recommended Action This message will automatically appear during certain events, such as during a FRU removal or if the FRU loses connectivity. In most cases, the router will resynchronize the ISSU state between the FRUs without any user intervention. If the ISSU state is not resynchronized after multiple attempts, the problem is likely a result of another problem. Monitor the other system messages to see if a more serious issue has occurred on your router. If you are unable to resolve this other issue and this message persists, gather the output of show tech-support and provide it to a Cisco technical support representative.


%ISSU-0-PKG_INCONSIST : Reason: [chars]
Explanation A software consolidated package or sub-package has an error that indicates the sub-package should not be installed or used.
Recommended Action If this message is received, the desired consolidated package or sub-package should not be used. Upgrade using a different consolidated package or sub-package, and report the problem consolidated package or sub-package to Cisco technical support.


%ISSU-3-INCOMPAT : The packages in [chars] are not consistent
Explanation The sub-packages specified for running on the chassis are not compatible with one other.
Recommended Action Install a compatible set of packages to allow normal operation. This will require booting a known-good package set.


%ISSU-3-BOOT_UNCLEAN : Found reload log file, moved to [chars]
Explanation A log file was found at bootup indicating that all shutdown tasks were not performed on a previous reload.
Recommended Action No user action is necessary. The system will automatically resolve most issues related to the shutdown task as part of the bootup procedure. If a problem related to the tasks that did not shutdown occurs, another error message will occur providing information about that problem.


%ISSU-5-ISSU_STATE_INVALID : ISSU stored state found invalid and cleaned up: [chars]
Explanation The RP has corrected a failed ISSU install state that was detected at bootup.
Recommended Action No user action is necessary. This is an informative message indicating that the failed ISSU state has been corrected.


%ISSU-0-PKG_MNT_SCRIPT_FAIL : Package: [chars]
Explanation A consolidated package or sub-package has encountered an error indicating it is not usable.
Recommended Action Upgrade your software using a different consolidated package or sub-package.


%ISSU-5-ISSU_AUTO_ROLLBACK : ISSU rollback timer expired: initiating rollback
Explanation An ISSU upgrade has been rolled back because the rollback 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.


%ISSU-0-SOFTWARE_INVALID : Package for location [chars]: [chars]
Explanation The sub-packages have encountered an error related to the structure of the loaded software.
Recommended Action This error is likely caused by a failure of the boot or installation process or a corrupted provisioning file. If the system displays error messages related to the boot that can be addressed, address those messages. Downloading new software, if possible, may also help with the problem. If the problem persists, gather the output of show tech-support and provide it to a Cisco technical support representative.


%ISSU-0-RESET_FRU_FAIL : Problem with ISSU reset of remote FRU - [chars]
Explanation After a sub-package installation, one or more FRUs that were upgraded failed to initialize within the timeout period.
Recommended Action This problem is more likely to occur in routers with larger configurations, so if your router has a large configuration, you may want to wait a few more minutes to see if your hardware initializes. If the hardware continues to not initialize, reset the FRUs which failed to initialize. If resetting the FRUs fails to resolve the issue, gather the output of show tech-support and contact a Cisco technical support representative.


%ISSU-3-UCODE_INCOMPAT : Found mismatch for ucode feature - [chars]
Explanation During boottime microcode feature version check, a version mismatch was found for this feature.
Recommended Action Please ensure that versions of features in microcode are compatible by provisioning a different set of microcode files.


%ISSU-3-SYNC_ERR : Problem with sync of state - [chars]
Explanation The software state between two FRUs or switches is not properly synchronized as a result of a boot error.
Recommended Action This message may appear during certain events, such as during a FRU or switch removal or if the FRU or switch loses connectivity. In most cases, the router will resynchronize the software state between the FRUs or switches without any user intervention. If the software state is not resynchronized after multiple attempts, the problem is likely a result of another problem. Monitor the other system messages to see if a more serious issue has occurred on your router. If you are unable to resolve this other issue and this message persists, gather the output of show tech-support and provide it to a Cisco technical support representative.


IVR

%IVR-3-BAD_IVR_VERSION : Script requires version [dec].[dec], image supports [dec].[dec]
Explanation IVR Script requires a higher IVR infrastructure version
Recommended Action Upgrade IOS, or use a different script


%IVR-3-NOSCRIPT : Could not load IVR script [chars] errno=[dec]=[chars]
Explanation Could not read in the IVR script
Recommended Action Check that script exists on the server, and is readable.


%IVR-3-BADSCRIPT : Could not parse malformed IVR script: [chars]
Explanation Could not parse malformed IVR script
Recommended Action Check the script and fix the syntax error.


%IVR-3-ABNORMAL_EXIT : TCL IVR Process for this call with CallID [dec] exits , bad event: [chars] received
Explanation The TCL IVR call process exited for the specified call. The call process did not clear a prior call properly, so other events could not be handled. Only the specified call is affected
Recommended Action If problem persists for subsequent calls,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.


%IVR-3-LOW_MEMORY : IVR: Sytem running on low memory. Free memory: %l bytes. Call is rejected.
Explanation System does not have enough memory to accept calls
Recommended Action Check to see what is causing low system memory.


%IVR-3-LOW_MEMORY_RESOURCE : IVR: System running low on memory ([dec]/100 in use). Call (callID=[dec]) is rejected.
Explanation System does not have enough free memory to accept a new call
Recommended Action Ensure that the gateway has the recommended amount of memory for this IOS feature set and version.


%IVR-3-LOW_CPU_RESOURCE : IVR: System experiencing high cpu utilization ([dec]/100). Call (callID=[dec]) is rejected.
Explanation System does not have enough CPU resources available to accept a new call
Recommended Action Ensure that the call setup rate is within the supported capacity of this gateway.


%IVR-2-APP_CRIT_R : [chars]
Explanation A critical message was reported by an IVR Tcl application.
Recommended Action The remedy of the problem is application specific.


%IVR-3-APP_ERR_R : [chars]
Explanation An error message was reported by an IVR Tcl application.
Recommended Action The remedy of the problem is application specific.


%IVR-4-APP_WARN_R : [chars]
Explanation A warning message was reported by an IVR Tcl application.
Recommended Action The remedy of the problem is application specific.


%IVR-6-APP_INFO_R : [chars]
Explanation An informational message was reported by an IVR Tcl application.
Recommended Action The remedy of the problem is application specific.


%IVR-6-APP_PARALLEL : Cannot use dial-peer [dec] (parallel hunt-group) for a rotary or in a hunt-group call.
Explanation The dial-peer for parallel hunt-groups must have a unique pilot number.
Recommended Action Create a unique dial-peer destination-number for the parallel hunt-group.


%IVR-6-APP_SEQ_HUNT : Pilot hunt-group '[chars]' found in hunt-group list. Nested hunt-groups are allowed only as the hunt-group's final number.
Explanation Nested sequential hunt-group detected in dial-peer rotary. Nested hunt-groups is unsupported.
Recommended Action Do not create hunt-group lists that contain hunt-group pilot numbers.


%IVR-1-APP_PARALLEL_INVALID_LIST : Call terminated. Huntgroup '[dec]' does not contain enough valid SIP end-points to proceed with a parallel call.
Explanation The call to a parallel hunt-group was denied because less than two valid SIP end-points were found in the huntgroup list.
Recommended Action Check the hunt-group list's numbers. Remove any incorrect numbers or numbers that have a non-SIP dial-peer. If the numbers are from SIP phones, then verify whether the phones have registered to the system yet.


%IVR-2-INVALID_DSAPP_DIALPEER : Service dsapp contains an invalid dial peer tag: [chars]
Explanation An invalid dial peer tag has been configured for the dsapp service. The tag either is not in the range from 1 to 2147483647, or it belongs to a non-existent dial-peer.
Recommended Action Enter the show running-config or the show dial-peer voice command to find a valid dial peer tag. Reconfigure the dial peer with a valid tag or remove the dial peer tag completely to allow the system to match from the system dial peers.


%IVR-4-INVALID_DSAPP_BLINDTIME : Blind-xfer-wait-time [dec] is invalid. Resetting to [dec] seconds.
Explanation The configured value for blind-xfer-wait-time was outside of the acceptable range (0-10) and has been reset to the indicated value.
Recommended Action If the new value for blind-xfer-wait-time is unacceptable, you can change it from the command line interface.


%IVR-4-INVALID_DSAPP_TOGGLE_TIME : Disc-toggle-time [dec] is invalid. Resetting to [dec] seconds.
Explanation The configured value for disc-toggle-time was outside of the acceptable range (10-30) and has been reset to the indicated value.
Recommended Action If the new value for disc-toggle-time is unacceptable, you can change it from the command line interface.


%IVR-5-APP_CALL_PREEMPTION : CallID [dec] is being preempted
Explanation A notification message was reported by an IVR application on detecting callID %d being preempted.
Recommended Action This is not a problem but notifying syslog about preempted call.


%IVR-2-APP_CRIT : [chars]
Explanation A critical message was reported by an IVR Tcl application.
Recommended Action The remedy of the problem is application specific.


%IVR-3-APP_ERR : [chars]
Explanation An error message was reported by an IVR Tcl application.
Recommended Action The remedy of the problem is application specific.


%IVR-4-APP_WARN : [chars]
Explanation A warning message was reported by an IVR Tcl application.
Recommended Action The remedy of the problem is application specific.


%IVR-6-APP_INFO : [chars]
Explanation An informational message was reported by an IVR Tcl application.
Recommended Action The remedy of the problem is application specific.


%IVR-5-APP_MED_INACT_DETECTED : [chars]
Explanation A notification message was reported by an IVR application on detecting media inactivity.
Recommended Action This is not a problem but notifying syslog about media inactivity.


%IVR-5-APP_MED_REACT_DETECTED : [chars]
Explanation A notification message was reported by an IVR application on detecting media activity.
Recommended Action This is not a problem but notifying syslog about media activity.


%IVR-5-APP_LOG_DUR_CALL_DETECTED : [chars]
Explanation A notification message was reported by an IVR application on detecting long duration call.
Recommended Action This is not a problem but notifying syslog about long duration call.


IVR_MSB

%IVR_MSB-3-NOPROMPT : Could not create IVR prompt [chars] errno=[dec]=[chars]
Explanation Could not read in the IVR prompt
Recommended Action Check that prompt exists on the server, and is readable.


%IVR_MSB-3-NO_IO_MEMORY : [chars]: Failed to create pool_group [hex] buffer_pool [hex] platform_mc_buf_pool_count [dec]
Explanation No IO memory to create IVR private pak pool
Recommended Action Check to see if there is enough IO memory.


%IVR_MSB-3-INVALID_MAX_PROMPTS : [chars]: This version of IOS does not support prompt playout for IVR applications.
Explanation This error will be displayed if an IVR application is used on a gateway that does not support IVR prompt playout.
Recommended Action Ensure that this platform and IOS version support the IVR feature set.


%IVR_MSB-3-INVALID_PROMPT_SIZE : [chars]: Bad size for the prompt file [chars]. Read size [dec]. Expected size [dec].
Explanation Prompt file size error. File may be corrupted.
Recommended Action Replace the bad prompt file.


IVR_NOSIGNALING

%IVR_NOSIGNALING-3-LOW_MEMORY_RESOURCE : IVR: System running low on memory ([dec]/100 in use). Application cannot be instantiated.
Explanation System does not have enough free memory to spawn a new instance of IVR application
Recommended Action Ensure that the gateway has the recommended amount of memory for this IOS feature set and version.


%IVR_NOSIGNALING-3-LOW_CPU_RESOURCE : IVR: System experiencing high cpu utilization ([dec]/100). Application cannot be instantiated.
Explanation System does not have enough CPU capacity to spawn a new instance of IVR application
Recommended Action Ensure that the call setup rate is within the supported capacity of this gateway.


KERBEROS through LANMGR

KERBEROS

%KERBEROS-3-FORKFAIL : Failed to fork process for [chars].
Explanation Quite likely, we ran out of memory. Other explanations are possible.
Recommended Action If this message recurs, call your technical support representative for assistance.


KEYMAN

%KEYMAN-4-KEYSTR_CRYPTO_TYPE : Type [dec] encryption unknown. Interpreting keystring as literal
Explanation The format type was not recognized by the system. A keystring format type value of 0 (unencrypted keystring) or 7 (hidden keystring), followed by a space, can precede the actual keystring to indicate its format. An unknown type value will be accepted, but the system will consider the keystring as being unencrypted.
Recommended Action Use the correct format for the value type or remove the space following the value type


%KEYMAN-4-KEYSTR_BAD_CRYPTO : Bad encrypted keystring for key id [dec].
Explanation The system could not successfully decrypt an encrypted keystring. The keystring may have been corrupted during system configuration.
Recommended Action Re-enter the key-string command, and reconfigure the key string.


KEYSTORE

%KEYSTORE-3-IFS_OPEN_W : Failed to open file [chars] for writing software keystore. ([chars])
Explanation An error occurred while opening a file for persistent storage. CTS keys could not be saved to persistent storage.
Recommended Action


%KEYSTORE-3-IFS_WRITE : An error occurred while writing to the software keystore file.
Explanation CTS keys could not be saved to persistent storage.
Recommended Action


%KEYSTORE-3-IFS_OPEN_R : Failed to open file [chars] for reading software keystore. ([chars])
Explanation An error occurred while opening the keystore file for reading. CTS keys could not be retrieved.
Recommended Action


%KEYSTORE-3-IFS_READ : An error ([chars]) occurred while reading from the software keystore file.
Explanation CTS keys could not be retrieved from persistent storage.
Recommended Action


%KEYSTORE-3-BAD_MAGIC : Bad magic number [hex] in software keystore file [chars].
Explanation Keystore data file appears to have been corrupted. Keys can not be retrieved from persistent memory.
Recommended Action


%KEYSTORE-3-UNEXPECTED_EOF : Unexpected end of file while reading software keystore [chars].
Explanation Keystore data file appears to have been truncated. One or more keys can not be retrieved from persistent memory.
Recommended Action


%KEYSTORE-3-IPCPORT : Failed to create IPC port ([chars]) for keystore redundancy. [chars].
Explanation An error was encountered when trying to create an IPC port. This means that any updates made to the ACTIVE keystore cannot be pushed to the STANDBY keystore.
Recommended Action


%KEYSTORE-3-IPCOPEN : Failed to open IPC port to peer for keystore redundancy: [chars]
Explanation An error was encountered when trying to open an IPC port for keystore redundancy messages. This means that any updates made to the ACTIVE keystore cannot be pushed to the STANDBY keystore.
Recommended Action


%KEYSTORE-3-IPCNOCONN : No IPC communication path to peer available for keystore [chars].
Explanation No IPC connection to the peer was available for keystore redundancy messages. This means that any updates made to the ACTIVE keystore cannot be pushed to the STANDBY keystore.
Recommended Action


%KEYSTORE-3-IPCSEND : IPC send error ([chars]) while sending [chars].
Explanation An error occurred while sending an IPC message to the peer during a keystore redundancy operation. This means that any updates made to the ACTIVE keystore cannot be pushed to the STANDBY keystore.
Recommended Action


%KEYSTORE-3-ISSU_INCOMPAT : Standby incompatible for SSO.
Explanation The image on the standby failed ISSU message version negotiation. As a result, we will not be able to sync keystore updates to it and so it is disallowed from reaching hot standby status in SSO mode.
Recommended Action


%KEYSTORE-3-IPC_NO_PROC : Could not create a process to receive keystore redundancy messages.
Explanation An error was encountered when trying to create a process to handle incoming keystore redundancy messages. This means that any updates made to the ACTIVE keystore cannot be pushed to the STANDBY keystore.
Recommended Action


%KEYSTORE-3-NO_KEYSTORE : CTS hardware keystore is not responsive and software emulation is not enabled.
Explanation The CTS hardware keystore on the switch has failed and needs to be inspected. Since CTS credentials are stored in the keystore, this means that CTS authentication and authorization operations will fail. The following action is recommended: If the defect is shown on the Active Supervisor, try to switchover to Standby Supervisor. If the defect is shown on Standby Supervisor, try to reset the Standby. If the defect persists, there may be damage to the hardware keystore chip, please take appropriate action. In the meantime, you can configure the switch to use software keystore emulation. After you have enabled software keystore emulation, please re-configure CTS credentials to populate the software keystore.
Recommended Action


L2BD_PROXY

%L2BD_PROXY-3-L2BD_MEM_REQ_FAILED : L2BD IPC subtype: [dec]
Explanation Requesting more 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.


%L2BD_PROXY-3-L2BD_MEM_EXTEND_FAILED : L2BD IPC subtype: [dec]
Explanation Extending 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.


%L2BD_PROXY-4-PROXY_INVALID_MSG_LEN : QFP L2BD Proxy IPC invalid length, [dec]:[dec] len [dec] flags [hex] source [dec]
Explanation Cisco internal software error. QFP L2BD Proxy received invalid IPC message length from control plane. This message will be ignored.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%L2BD_PROXY-4-PROXY_INVALID_MSG : QFP L2BD Proxy received invalid message type [dec]
Explanation Cisco internal software error. QFP L2BD Proxy received an invalid message from control plane. This message will be ignored.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%L2BD_PROXY-2-PROXY_IPC_INIT_FAILED : QFP L2BD Proxy IPC interface initialization failure (result: [dec]).
Explanation Cisco internal software error. QFP L2BD Proxy initialization detected that the IPC interface initialization failed. QFP L2BD proxy will not be functional while this condition exists.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%L2BD_PROXY-3-PROXY_BAD_MSG : QFP L2BD Proxy received bad length message type [dec]
Explanation Cisco internal software error. QFP L2BD Proxy received a corrupted message from control plane. This message will be ignored.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%L2BD_PROXY-3-PROXY_IPC_ALLOC_FAILED : QFP L2BD Proxy [chars] message lost due to message buffer allocation failure.
Explanation Cisco internal software error. QFP L2BD Proxy message processing detected a message buffer allocation failure. The message is lost as the result of this 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.


%L2BD_PROXY-3-PROXY_IPC_SEND_FAILED : QFP L2BD Proxy [chars] message lost due to message sent failure (result: [dec]).
Explanation Cisco internal software error. QFP L2BD Proxy message processing detected a message sent failure. The message is lost as the result of this 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.


L2CTRL

%L2CTRL-3-ADD_REGISTRY_FAILED : Subsystem [chars] fails to add callback function [chars]
Explanation Other subsystem must have mistakenly add its own callback functions. This syslog is for debugging purpose.
Recommended Action No action is required.


L2FIB

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


%L2FIB-3-EVPN_ERROR : [chars]
Explanation EVPN encap 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.


L2TP

%L2TP-3-ILLEGAL : [chars]: [chars]
Explanation An illegal event has been processed by the L2TP subsystem.
Recommended Action No action is required.


%L2TP-3-CRITICAL : [chars]
Explanation An critical event has been processed by the L2TP subsystem.
Recommended Action No action is required.


%L2TP-5-IGNOREICMPMTU : Ignoring received ICMP Type 3 Code 4, due to pmtu min or max setting
Explanation An ICMP Type 3 Code 4 (fragmentation needed and DF set) packet has been received. This packet has specified a Next-Hop MTU that is smaller or greater than the current minimum or maximum path MTU discovery mtu value. The ICMP packet has been ignored and the MTU has not been changed.
Recommended Action If you want the ICMP packet to be accepted and used to decrease or increase the MTU then use the vpdn pmtu min command to decrease the minimum MTU allowed and enter the vpdn pmtu max command to increase the maximum MTU that is allowed. The minimum value specified is the minimum MTU that is allowed, and the maximum value specified is the maximum MTU that is allowed.


L2TP_HA

%L2TP_HA-3-SYNC : [chars]: code [dec]
Explanation An error occurred when syncing L2TP state to the Standby Route Processor. This may affect Non-Stop Forwarding capability on L2TP-based interfaces during and after switchover until the state is recovered through normal protocol operation.
Recommended Action Reset the standby processor to attempt the sync again. LOG_STD_RECUR_ACTION


%L2TP_HA-3-ISSU : [chars]: [chars]
Explanation A L2TP ISSU 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.


L4_INSPECT

%L4_INSPECT-3-INVALID_CHUNK_ID : Invalid chunk ID for protocol ([int])
Explanation Failed to determine chunk ID for specified protocol. Unable to free CFT feature object.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


LANMGR

%LANMGR-4-OLDTRAMON : Cannot run RPS on [chars], Old TRAMON code.
Explanation The software on this interface cannot support the functions required for LAN Network Manager.
Recommended Action Call your Cisco technical support representative about a firmware upgrade for this interface card.


%LANMGR-4-BADRNGNUM : Ring number mismatch on [chars], shutting down the interface
Explanation The router detected a conflict in assigned ring numbers for the specified Token Ring. The Ring Parameter Server (RPS) function was shut down to prevent potentially incorrect information from being sourced onto the ring.
Recommended Action Check all bridges connected to this Token Ring and ensure that they are using the same assigned ring number.


%LANMGR-4-BADUPCALL : Unexpected call ([chars]) from LLC2 for Bridge [hex]-[hex]-[hex]
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.


%LANMGR-4-NORING : No ring info for [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.


%LANMGR-2-NOMEMORY : No memory available: [chars]
Explanation The requested operation failed because of a low memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.


LAPB through LINEPROTO

LAPB

%LAPB-3-NULLPAK : Interface [chars], NULL packet ptr, rvr [dec], vs [dec], vr [dec]
Explanation An internal software error occurred.
Recommended Action If either of these messages recur, call your technical support representative for assistance.


%LAPB-3-NOINPIDB : Input idb not set
Explanation An internal software error occurred.
Recommended Action If either of these messages recur, call your technical support representative for assistance.


%LAPB-4-FRAMEERR : Interface [chars], Frame error: CF [hex], VS [dec] %c VR [dec], Reason [hex]
Explanation A FRMR frame was received, indicating that a protocol violation was detected. The Reason field will be interpreted by generating INFOBAD, CTRLBAD, N1TOOBIG, or INVNR messages immediately after this message; refer to the explanations for these messages for more information.
Recommended Action The protocol will recover by resetting the service. This will disrupt any network service on top of LAPB (for example, X.25 virtual circuits will be cleared). Follow the recommended action for any error message following the FRMR reports; if service becomes unacceptable, check the serial line and its attached devices.


%LAPB-4-INFOBAD : Interface [chars], Info field not permitted
Explanation A received FRMR frame reported that an information field was present in a frame where no information field is allowed.
Recommended Action Check the serial line and the device attached to the line.


%LAPB-4-CTRLBAD : Interface [chars], Invalid control field
Explanation A received FRMR reported a frame with an invalid control code.
Recommended Action Check the serial line and the devices attached to the line.


%LAPB-4-N1TOOBIG : Interface [chars], N1 too large
Explanation A received FRMR reported an information frame that was too long.
Recommended Action Verify that the equipment attached to the serial line is configured with the same N1 value. N1 is in bits and includes the entire frame plus 16 bits of CRC. However, some equipment may require configuration in octets, the omission of the two CRC octets, or the omission of the three octets of LAPB control information.


%LAPB-4-INVNR : Interface [chars], Invalid NR value
Explanation A received FRMR reported a frame with an invalid N(R) value.
Recommended Action Verify that the equipment attached to the serial line is configured with the same K value (maximum number of outstanding I frames).


%LAPB-2-NOBUF : Interface [chars], no buffer available to [chars]
Explanation There was insufficient memory for the LAPB protocol engine to send a message.
Recommended Action This message is acceptable if it occurs infrequently, because the LAPB protocol is designed to handle loss of frames. Frequent occurrences can cause disruption of service. The system can be configured to ease memory demands or, if conditions warrant, the system can be upgraded to a larger memory configuration.


%LAPB-3-BADPAYLOAD : Interface [chars], Invalid payload value: [chars]
Explanation An internal software error occurred.
Recommended Action If either of these messages recur, call your technical support representative for assistance.


%LAPB-3-CONTEXTERR : [chars]: [chars]
Explanation An internal software error occurred.
Recommended Action If either of these messages recur, call your technical support representative for assistance.


%LAPB-3-TIMERERR : LAPB timer task cannot be created
Explanation An internal software error occurred.
Recommended Action If either of these messages recur, call your technical support representative for assistance.


LAT

%LAT-3-NOSYNC : Tty%t, Output data ptrs out of sync with byte count
Explanation An internal software error occurred.
Recommended Action If this message recurs, contact your technical support representative.


%LAT-3-BADDATA : Tty%t, Data pointer does not correspond to current packet
Explanation An internal software error occurred.
Recommended Action If this message recurs, contact your technical support representative.


%LAT-3-REUSE : Tty%t, Attempt to re-use slot array, empty = [dec], fill = [dec]
Explanation An internal software error occurred.
Recommended Action If this message recurs, contact your technical support representative.


%LAT-3-QBSPACED : Queue block at [hex] not found for HI connection
Explanation An internal software error occurred.
Recommended Action If this message recurs, contact your technical support representative.


%LAT-3-BUFFULL : Tty%t, data buffer full with count [dec]
Explanation An internal software error occurred.
Recommended Action If this message recurs, contact your technical support representative.


%LAT-3-NULLIDB : Null IDB pointer with destination [enet]
Explanation An internal software error occurred.
Recommended Action If this message recurs, contact your technical support representative.


LAYER2_BRIDGE

%LAYER2_BRIDGE-3-INIT_FAILED : Initialization of the layer 2 bridging feature in QFP failed
Explanation Initialization of the layer 2 bridging feature in the QFP failed. This indicates a software 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.


%LAYER2_BRIDGE-3-ALLOC_FAILED : Allocation of [chars] memory failed for layer 2 bridging feature in QFP
Explanation Allocation of memory by the QFP layer 2 bridging feature microcode failed. The name of the memory chunk is specified in the message. This indicates a software 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.


%LAYER2_BRIDGE-3-PKT_REPLICA_INIT_FAILED : Failed to register with generic packet replication for layer 2 bridging feature in QFP
Explanation Layer 2 bridging initialization of packet replication registration 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.


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


%LAYER2_BRIDGE-3-HA_BULK_SYNC_FAIL : rg [dec], MSGDEF_LIMIT_MEDIUM
Explanation There was a failure such that Layer 2 bridge domain bulk sync did not occur
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


LAYER2_SVI

%LAYER2_SVI-3-INIT_FAILED : Initialization of the SVI feature in QFP failed
Explanation Initialization of the SVI feature in the QFP failed. This indicates a software 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.


%LAYER2_SVI-3-ALLOC_FAILED : Allocation of [chars] memory failed for SVI feature in QFP
Explanation Allocation of memory by the QFP SVI feature microcode failed. The name of the memory chunk is specified in the message. This indicates a software 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.


%LAYER2_SVI-3-PKT_REPLICA_INIT_FAILED : Failed to register with generic packet replication for SVI feature in QFP
Explanation SVI initialization of packet replication registration 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.


LED

%LED-3-VIDEO_SOURCE_CHANGE_FAILED : Video Multicast Source Switch Failed. Error [dec], Source ([hex], [hex]), LED [dec]
Explanation Video Input Source failed to switch to the next sourcee.
Recommended Action Check the failed input source, and check for service impact


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


%LED-2-INIT_FAILED : Video LED process initialization failed id [int]
Explanation Initialization of the Video LED process failed. This is an internal software error.
Recommended Action Retrieve and record the error message and other related information exactly as it appears on the console and/or the system log and IOS log. Search for resolved software issues using the Bug Toolkit at:http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at https://mycase.cloudapps.cisco.com/case, or contact your Cisco technical support representative and provide the representative with the gathered information.


%LED-2-VIPC_INIT_FAILED : VIPC initialization failed id [int]
Explanation Initialization of the Video LED process failed. This is an internal software error.
Recommended Action Retrieve and record the error message and other related information exactly as it appears on the console and/or the system log and IOS log. Search for resolved software issues using the Bug Toolkit at:http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at https://mycase.cloudapps.cisco.com/case, or contact your Cisco technical support representative and provide the representative with the gathered information.


%LED-2-VDMAN_IPC_INIT_FAILED : Vidman IPC initialization failed id [int]
Explanation Initialization of the Video LED process failed. This is an internal software error.
Recommended Action Retrieve and record the error message and other related information exactly as it appears on the console and/or the system log and IOS log. Search for resolved software issues using the Bug Toolkit at:http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at https://mycase.cloudapps.cisco.com/case, or contact your Cisco technical support representative and provide the representative with the gathered information.


%LED-2-ID_MISMATCH : LED ID mismatch Led id - [int], Instance - [int]
Explanation This is an internal software error.
Recommended Action Retrieve and record the error message and other related information exactly as it appears on the console and/or the system log and IOS log. Search for resolved software issues using the Bug Toolkit at:http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at https://mycase.cloudapps.cisco.com/case, or contact your Cisco technical support representative and provide the representative with the gathered information.


%LED-2-RESOURCE_ALLOCATION : Failed to Allocate memory, Led id [int]
Explanation This is an internal software error.
Recommended Action Retrieve and record the error message and other related information exactly as it appears on the console and/or the system log and IOS log. Search for resolved software issues using the Bug Toolkit at:http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at https://mycase.cloudapps.cisco.com/case, or contact your Cisco technical support representative and provide the representative with the gathered information.


%LED-2-INVALID_PSI_TYPE : Invalid PSI type, Led id [int]
Explanation This is an internal software error.
Recommended Action Retrieve and record the error message and other related information exactly as it appears on the console and/or the system log and IOS log. Search for resolved software issues using the Bug Toolkit at:http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at https://mycase.cloudapps.cisco.com/case, or contact your Cisco technical support representative and provide the representative with the gathered information.


%LED-2-DB_HA_ERROR : Database HA Error, Led id [int]
Explanation This is an internal software error.
Recommended Action Retrieve and record the error message and other related information exactly as it appears on the console and/or the system log and IOS log. Search for resolved software issues using the Bug Toolkit at:http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at https://mycase.cloudapps.cisco.com/case, or contact your Cisco technical support representative and provide the representative with the gathered information.


%LED-2-OUT_OF_CONTEXT_ERROR : LED Fell out of context loop, Led id [int]
Explanation This is an internal software error.
Recommended Action Retrieve and record the error message and other related information exactly as it appears on the console and/or the system log and IOS log. Search for resolved software issues using the Bug Toolkit at:http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at https://mycase.cloudapps.cisco.com/case, or contact your Cisco technical support representative and provide the representative with the gathered information.


%LED-2-GQILIB_INIT_FAILED : Failed to init GQI Lib, Led id [int]
Explanation This is an internal software error.
Recommended Action Retrieve and record the error message and other related information exactly as it appears on the console and/or the system log and IOS log. Search for resolved software issues using the Bug Toolkit at:http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at https://mycase.cloudapps.cisco.com/case, or contact your Cisco technical support representative and provide the representative with the gathered information.


%LED-2-TBLLIB_INIT_FAILED : Failed to init Table-based Lib, Led id [int]
Explanation This is an internal software error.
Recommended Action Retrieve and record the error message and other related information exactly as it appears on the console and/or the system log and IOS log. Search for resolved software issues using the Bug Toolkit at:http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at https://mycase.cloudapps.cisco.com/case, or contact your Cisco technical support representative and provide the representative with the gathered information.


%LED-2-VIPC_SEND_FAILURE : VIPC send failed, Led id [int]
Explanation This is an internal software error.
Recommended Action Retrieve and record the error message and other related information exactly as it appears on the console and/or the system log and IOS log. Search for resolved software issues using the Bug Toolkit at:http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at https://mycase.cloudapps.cisco.com/case, or contact your Cisco technical support representative and provide the representative with the gathered information.


%LED-3-LED_IPC_FLOW_CONTROL : Flow control turned [chars] for VIPC port [int], remote port [int], remote slot [int]
Explanation Flow control triggered on IPC link between LED and VDMAN.
Recommended Action Check the LED btrace logs


LFD

%LFD-3-CHUNKMGRALLOC : failed chunk alloc: [chars]
Explanation Chunk alloc() 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.


%LFD-3-CHUNKMGRDEALLOC : failed chunk dealloc: [chars]
Explanation Chunk free() 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.


%LFD-3-UPDATEHANDLERFPI : No handler installed: fpi=[dec] handler type=[chars]
Explanation No handler 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.


%LFD-3-UPDATEHANDLER2 : [chars] [hex] [hex]
Explanation Error in update 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.


%LFD-3-UPDATEHANDLER3 : [chars] [hex] [hex] [hex]
Explanation Error in update 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.


%LFD-4-NOFIBIDB : [chars] - ifnum [dec]
Explanation fibidb missing on linecard
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.


%LFD-3-REWMGR : Rewrite Manager: [chars] [hex]
Explanation Rewrite Manager 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.


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


%LFD-3-FPIHANDLER : LFD SSS Handler: [chars]
Explanation Error in fpi 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.


%LFD-2-FPIHANDLER3 : [chars] [hex] [hex] [hex]
Explanation FPI Handler 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.


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


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


%LFD-3-FPITYPEWRONG : Require fpi type [chars], get fpi type [chars]
Explanation Unmatched FPI 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.


%LFD-4-UNSUPPORTEDRW : Unexpected rewrites seen where MPLS is not supported by platform for this slot
Explanation MPLS is either not needed or not handled by the platform for this card and should not handle rewrites
Recommended Action No action is required.


%LFD-3-NORESOURCE : [chars] [dec]
Explanation Resource Failure: %s %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.


%LFD-6-RESOURCE : [chars]
Explanation MPLS software is disabled on LC
Recommended Action No action is required.


%LFD-3-LTABLEMEM : Cannot allocate new mpls table [dec] of size [dec] needed for entry [dec]
Explanation Not enough contiguous memory for mpls forwarding table
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.


%LFD-3-SM : [chars] [dec]
Explanation State Machine error: %s %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.


%LFD-3-SMBADEVENT : Unexpected event [chars] for state [chars]
Explanation The LFD received an unexpected event for its state. The state of the LFD, and the unexpected event, are specified in the message text.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


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


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


%LFD-2-AVL : [chars] [hex]
Explanation 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.


%LFD-3-CHUNKMGR : chunk mgr: [chars] [hex]
Explanation Chunk manager 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.


%LFD-3-INTFDB : intf db: [chars] [hex]
Explanation Interface db 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.


%LFD-3-INTFDB2 : intf db: [chars] [hex] [hex]
Explanation Interface db 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.


%LFD-3-BADFRRTYPE : illegal frr type: [dec]
Explanation FRR request type 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.


%LFD-4-OWNCHANGED : Owner changed for [chars] [dec]/[dec] from [dec] to [dec]
Explanation Label was previously installed by different installer
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%LFD-3-INVPLISTTYPE : Wrong plist_type expected [dec] for [dec]/[dec] update (was [dec])
Explanation Rewrite PLISTTYPE invalid for non-ip label table entry
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%LFD-3-INVRWID : Wrong rwid [dec] for non-ip LTE [dec]/[dec]
Explanation Rewrite ID invalid for non-ip label table entry
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


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


%LFD-3-INVIPLABELTYPE : Wrong label type [dec] for IP Label [dec], table [dec] prefix [chars], vrf [chars]
Explanation Label type is invalid for the indicated label table entry
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version and show running-config and contact your Cisco technical support representative.


%LFD-3-INVPLIST : Wrong path list type [dec] for label [dec]/[dec] [chars]
Explanation The path list type is set incorrectly for the label in question
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%LFD-3-BADSHORTLABELADD : Cannot add short label: path_idx [dec], moi_type [dec]
Explanation Unable to create MFI feature space in FIB entry, so unable to store short path extension information there.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%LFD-3-BADLABELADD : Cannot add label - [chars].
Explanation Unable to create label due to reason given.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%LFD-3-INVPATHLBL : [chars] [chars]
Explanation An invalid outgoing label is attached to the prefix
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version and show running-config and contact your Cisco technical support representative.


%LFD-3-NOOCE : Attempt to get labels from OCE failed - [chars].
Explanation Calling function has provided insufficient information to get labels.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%LFD-3-XDRBADMAGIC : xdr message for [chars] spilled out of allocated static storage
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.


%LFD-3-UNSUPPORTED_XDR : [chars]
Explanation Decoding of an XDR message revealed data or format that is unsupported in the current release.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%LFD-3-BROKERINITFAIL : Failed to initialise lte RP broker facility
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.


%LFD-3-LCXDRCLIENT : LTE distribution client: [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.


%LFD-3-NONIPINFO : Non-ip info: [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.


%LFD-3-RPXDRCLIENT : Invalid XDR Client: [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.


%LFD-3-ORPHANLTE : Label [dec]/[dec], plist [dec], LDM: [hex]
Explanation The LTE for the label was supposed to be deleted, but is still present
Recommended Action Collect the running configuration and output of show mpls forwarding-table labels label-num command and contact cisco technical service representative.


%LFD-3-RUNNING_TIMER : [chars] [dec] [chars] [dec]
Explanation The MPLS forwarding entry for the specified label was deleted prior to the expiry of its associated timer
Recommended Action If there is no matching bug for this problem, please collect the output of show mpls forwarding-table label <label> internal and the error message traceback and file a bug report.


%LFD-3-INVLABELUPDTYPE : Wrong label type [dec] for label [dec] table [dec] [chars] [chars]
Explanation An invalid Label type was encountered during the specified operation
Recommended Action If there is no matching bug for this problem, please collect the output of show mpls forwarding-table label <label> internal and the error message traceback and file a bug report.


%LFD-3-KEY_DB_INSERTFAIL : [chars], entry [hex], existing [hex]
Explanation The element could not be inserted into the LFD's key database.
Recommended Action If there is no matching bug for this problem, please collect the output of show mpls forwarding-table internal and the error message traceback and file a bug


%LFD-3-FIB_SRC : Label [[dec]/[dec]] [chars] [chars] [chars]
Explanation The fib entry could not be sourced for label in question.
Recommended Action If there is no matching bug for this problem, please collect the output of show mpls forwarding-table internal and show ip route [vrf <name>] <prefix> and the error message traceback and file a bug


%LFD-4-FIB_SRC1 : Label [[dec]/[dec]] [chars] [chars] [chars]
Explanation The fib entry could not be sourced for label in question.
Recommended Action If there is no matching bug for this problem, please collect the output of show mpls forwarding-table internal and show ip route [vrf <name>] <prefix> and the error message traceback and file a bug


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


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


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


%LFD-4-RE_ENTRANT : Re-entrancy detected: [chars]
Explanation lfd non ip recalculation has re-entrancy
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


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


%LFD-3-INVPEXTLEN : [chars] path ext : attempt to decode beyond XDR buffer, cp [hex], cp_end [hex], msg_type [dec], msg_size [dec], padding [dec]
Explanation Accessing memory beyond XDR buffer length while decoding path extensions
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%LFD-3-FIBIPINVALID : [chars], table: [dec] label: [dec]
Explanation IP path information is invalid for the indicated label table entry
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.


%LFD-3-FIBIPINVALIDAF : AF: [dec] [chars], table: [dec] label: [dec]
Explanation IP path information AF is invalid for the indicated label table entry
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.


%LFD-3-FIBNONIPINVALID : [chars], table: [dec] label: [dec]
Explanation Non IP path information is invalid for the indicated label table entry
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.


%LFD-3-PATHEXTENCODE : [chars] [chars], path list: [IPV6 address], path ext: [IPV6 address]
Explanation MPLS path extensions could not be encoded for distribution
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.


LI

%LI-3-MEM_INIT_FAILED : Allocation of [chars] memory failed for LI
Explanation LI Initialization of channel pool failed.
Recommended Action LOG_STD_ACTION


%LI-3-PKT_REPLICA_INIT_FAILED : Register to Generic Packet Replication failed for LI
Explanation LI Initialization of packet replication registration failed.
Recommended Action LOG_STD_ACTION


LICENSING

%LICENSING-6-LIC_MISMATCH : Configured license image level [chars] does not match the current level [chars]. Reload is required to bring the system up in [chars]
Explanation During boot-up of system, the configured license image level might mismatch with the current level. This could happen when customer copy a different startup-config to the system.
Recommended Action Reload is required to bring the system up in the configured license image level.


LIIN

%LIIN-3-VRFADD_FAIL : Problem creating vrf
Explanation The LIIN config process failed to allocate a mandatory iVRF. The LIIN interface will not operate properly and cannot be recovered. Persistent access features and interactive commands will not work.
Recommended Action LOG_STD_ACTION


%LIIN-3-VRFMODIFY_FAIL : Problem adding LIIN interface to vrf table
Explanation The LIIN config process failed to assign the LIIN interface to its mandatory iVRF. The LIIN interface will not operate properly and cannot be recovered. Persistent access features and interactive commands will not work.
Recommended Action LOG_STD_ACTION


%LIIN-3-SET_TABLEID_FAIL : Installing [chars] LIIN interface tableid failed
Explanation This error happens when IOS failed to set tableid into linux kernel, possibly due to either IOSd or kernel out of memory or corruption. In this case, LIIN interface will not have VRF installed for the associated address family. The LIIN interface will not operate properly and cannot be recovered. Persistent access features and interactive commands will not work.
Recommended Action LOG_STD_ACTION


%LIIN-3-SET_ACCESS_FAIL : Installing LIIN interface access control failed
Explanation This error happens when IOS failed to set the access control function for the LIIN, possibly due to IOSd out of memory or corruption. In this case, LIIN interface setup will not proceed, will not operate properly and cannot be recovered. Persistent access features and interactive commands will not work.
Recommended Action LOG_STD_ACTION


%LIIN-6-TELNET_ALLOWED : Telnet access allowed due to romvar: SR_INIT_SHELL
Explanation Telnet from shell to IOS allowed because rommon variable SR_INIT_SHELL is set with value aux_do_system_shell. Remove this value from SR_INIT_SHELL or unset SR_INIT_SHELL to disable the telnet access
Recommended Action No action is required.


LINEPROTO

%LINEPROTO-5-UPDOWN : Line protocol on Interface [chars], changed state to [chars]
Explanation The data link level line protocol changed state.
Recommended Action No action is required.


LSD_CLIENT through MCPRP_DAI

LSD_CLIENT

%LSD_CLIENT-3-UTIL2 : [chars]: [hex] [hex]
Explanation MFI Utilities error occurred
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version and show running-config and contact your Cisco technical support representative.


%LSD_CLIENT-3-PCHUNK2 : [chars]: [chars] [hex] [hex]
Explanation Parameterized Chunk Manager error occurred
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version, show running-config and show process memory and contact your Cisco technical support representative.


%LSD_CLIENT-2-MSGHANDLERERR : Client=[dec] Msg type=[dec] Error=[chars]
Explanation LSD Client API message handler error encountered
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version and show running-config and contact your Cisco technical support representative.


%LSD_CLIENT-3-CLIENTAPI : Client API error: [chars] [dec]
Explanation Unexpected Client API error
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version and show running-config and contact your Cisco technical support representative.


%LSD_CLIENT-3-INVALID_VAR : [chars]
Explanation Function received invalid parameters
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version and show running-config and contact your Cisco technical support representative.


%LSD_CLIENT-2-XDREXEC : [chars] [dec]
Explanation Illegal code execution in XDR path
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version and show running-config and contact your Cisco technical support representative.


%LSD_CLIENT-2-XDREXEC2 : [chars] [hex] [hex]
Explanation Illegal code execution in XDR path
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version and show running-config and contact your Cisco technical support representative.


%LSD_CLIENT-3-ISSU_MSG_CONV : [chars] [dec] [dec]
Explanation Could not convert received message type to known message
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version and show running-config and contact your Cisco technical support representative.


%LSD_CLIENT-3-ISSU_REG : ISSU client [chars] ([dec]), entity [dec], failed ISSU registration: [chars]
Explanation ISSU negotiation failed for this XDR client.
Recommended Action This error indicates a coding problem. It is an error that will occur every time this image is run, and requires a code change to fix it.


%LSD_CLIENT-3-ISSU_ENUM_ERROR : Enum for [chars] is not ISSU-compliant: [chars]
Explanation The given enumeration is not ISSU-compliant for the reason given. Unpredictable behaviour will result when interoperating with different IOS versions.
Recommended Action This requires a code fix before the image can be shipped or ISSU will be broken.


LSD_HA

%LSD_HA-2-RESOURCE : [chars]
Explanation System resource error occured
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.


%LSD_HA-4-CF : [chars][dec]
Explanation CF related 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.


%LSD_HA-2-RF : [chars][dec]
Explanation RF related 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.


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


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


%LSD_HA-3-UNSENT_MSG_DB : [chars]
Explanation Error happen in unsent msg 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.


%LSD_HA-3-LABEL_RANGE_DB : [chars]
Explanation Error happen in label range 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.


LSMPI

%LSMPI-4-INJECT_FEATURE_ESCAPE : Egress [chars] packet delivered via legacy inject path
Explanation A packet with a CPP supported L3 encapsulation (such as IP) was produced by IOS but delivered to CPP via the L2/legacy inject path instead of the proper L3 inject path. For this packet, outbound features will not be applied and packet accounting will likely be 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.


LUA_VM

%LUA_VM-2-INITIALIZATION : Cannot initialize the Lua Virtual Machine
Explanation The Lua Virtual Machine is a critical component of the shell-manager process. It is used to render responses to user commands. If this component cannot be initialized then the shell-manager will be unable to process any commands directed at the IOS-XE daemons.
Recommended Action The shell-manager process could not be started. Check the trace log files for more details as to why the virtual machine failed to initialize correctly. This may be an out of memory condition so rebooting the chassis may resolve the problem.


MAB

%MAB-5-SUCCESS :
Explanation MAB Authentication was successful.
Recommended Action No action is required.


%MAB-5-FAIL :
Explanation MAB Authentication was unsuccessful.
Recommended Action No action is required.


MACSEC

%MACSEC-4-RX_SC_EXCEED : (RX SCI [hex] : TX SCI [hex] : vport [dec] : secy vport [dec])
Explanation RX SC exceeds hardware limit.
Recommended Action No action required (normal operation).


%MACSEC-5-REPLAY_WINDOW_BREACHED : (RxSCI %19s) Replay Window Breached on interface [chars].
Explanation Multiple In Late Packets Received.
Recommended Action No action required (normal operation).


%MACSEC-4-TX_SC_EXCEED : (TX SCI [hex] : vport [dec])
Explanation TX SC exceeds hardware limit.
Recommended Action No action required (normal operation).


%MACSEC-4-IPMTU_OVERSIZE : MACsec enabled interface [chars] IP MTU can't be more than [dec]
Explanation User config IP MTU size over MACsec enabled interface allows.
Recommended Action Reconfigure IP MTU base on the suggested range.


%MACSEC-5-TX_SA_PN_EXPIRE : (TX SCI [hex] : AN [dec]) TX SA PN about to expire.
Explanation TX SA PN about to expire. Send a request to MKA to perform a SAK Rekey for the given TX SCI and AN.
Recommended Action No action required (normal operation).


%MACSEC-6-CREATE_TX_SC : ([chars] TX SCI [hex] : vport [dec])
Explanation MKA request MACsec PD to create a TX SC on the given TX SCI and vport.
Recommended Action No action required (normal operation).


%MACSEC-6-DEL_TX_SC : ([chars] TX SCI [hex] : vport [dec])
Explanation MKA request MACsec PD to delete a TX SC on the given TX SCI and vport.
Recommended Action No action required (normal operation).


%MACSEC-6-CREATE_RX_SC : ([chars] RX SCI [hex] : TX SCI [hex] : vport [dec] : secy vport [dec])
Explanation MKA request MACsec PD to create a RX SC on the given RX SCI and vport.
Recommended Action No action required (normal operation).


%MACSEC-6-DEL_RX_SC : ([chars] RX SCI [hex] : vport [dec])
Explanation MKA request MACsec PD to delete a RX SC on the given RX SCI and vport.
Recommended Action No action required (normal operation).No action required (normal operation).


%MACSEC-6-INSTALL_TX_SA : ([chars] TX SCI [hex] : vport [dec] : an [dec] : next_pn [hex])
Explanation MKA request MACsec PD to install a TX SA on the given TX SCI, vport and an.
Recommended Action No action required (normal operation).


%MACSEC-6-INSTALL_RX_SA : ([chars] RX SCI [hex] : vport [dec] : an [dec] : secy_vport [dec])
Explanation MKA request MACsec PD to install a RX SA on the given RX SCI, vport and an.
Recommended Action No action required (normal operation).


%MACSEC-6-DEL_RX_SA : ([chars] RX SCI [hex] : vport [dec] : an [dec])
Explanation MKA request MACsec PD to delete a RX SA on the given RX SCI, vport and an.
Recommended Action No action required (normal operation).


%MACSEC-6-POST_SUCC : ([chars] Power-On-System-Test success in Trial No.[dec])
Explanation MACSEC power-on-system-test successful
Recommended Action No action required (normal operation).


%MACSEC-6-POST_FAIL : ([chars] Power-On-System-Test failure in Trial No.[dec])
Explanation MACSEC power-on-system-test failed
Recommended Action No action required (normal operation).


MATM

%MATM-3-MAX_ENTRIES : The maximum number of MAC addresses has been reached:[dec]
Explanation The maximum number of MAC entries that can be programmed has been reached.
Recommended Action New MAC addresses will not be learned. Stop any redundant MAC incrementing traffic for extra streams.


%MATM-3-RECONCILIATION : Reconciliation post switchover failed : [chars]
Explanation Consistency check across modules shows inconsistency in data.
Recommended Action Find out more about the error by using the commands show platform matm recon_state and show tech-support and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems.


%MATM-3-HWERROR : Hardware [chars] failed
Explanation A hardware API access error message occurred.
Recommended Action Find out more about the error by using the commands show platform matm recon_state and show tech-support and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems.


%MATM-3-INVALID_EVENT : An invalid event :[dec] received in [chars], expected event:[dec]
Explanation MATM feature received invalid event on it's event handler
Recommended Action The condition is being recovered, no action is required


MBOX

%MBOX-3-REG_FAIL_BAD_PARM : event [hex], handler [hex]
Explanation Registration of handler function for a mailbox event failed due to a bad parameter.
Recommended Action LOG_STD_ACTION


%MBOX-3-REG_FAIL_HANDLER_EXISTS : event [hex], handler [hex]
Explanation Registration of handler function for a mailbox event failed because a handler is already registered for the event.
Recommended Action LOG_STD_ACTION


%MBOX-3-DEREG_FAIL_BAD_PARM : event [hex]
Explanation Deregistration of handler function for a mailbox event failed due to a bad parameter.
Recommended Action LOG_STD_ACTION


%MBOX-3-DEREG_FAIL_NO_HANDLER : event [hex], handler [hex]
Explanation Deregistration of handler function for a mailbox event failed because no handler was registered for the event.
Recommended Action LOG_STD_ACTION


%MBOX-3-NO_HANDLER_FOR_EVENT : events [hex] bad bit number [int]
Explanation Mailbox event is pending but no handler is registered for event.
Recommended Action LOG_STD_ACTION


MCPRP_CLI

%MCPRP_CLI-6-LICENSE_EXPIRED : Shell access disabled due to license expiration
Explanation Shell license is expired. Thus the shell access is disabled
Recommended Action Get and install another shell license


MCPRP_DAI

%MCPRP_DAI-4-ERR_DISABLE : DAI detected error on [chars], putting [chars] to err-disable
Explanation Dynamic ARP inspection has detected an error condition because ARP packets have exceeded the configured rate or burst
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


MCP_SYS through MFIB

MCP_SYS

%MCP_SYS-0-ASSERTION_FAILED : Assertion failed: [chars]
Explanation An internal state consistency check failed.Correct operation cannot be guaranteed, and the system has been halted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


MCT1E1

%MCT1E1-3-INITFAIL : MCT1E1 (bay [dec]), Init Failed at [chars] - line [dec] arg [hex]
Explanation The SPA failed to complete hardware initialization.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%MCT1E1-3-UNCOR_MEM_ERR : [chars]: [dec] uncorrectable [chars] memory error(s) encountered. The memory address of the most recent error is: [hex]. The SPA is being restarted.
Explanation The SPA driver detected an uncorrectable memory error condition on the SPA card. Packet corruption may result.
Recommended Action The SPA driver has encountered an uncorrectable memory error on the SPA card. The hexadecimal memory address of the most recent error is specified in the message text on the console or in the system log. Please power down and reseat the indicated SPA card. CTE1_STD_ACTION


%MCT1E1-3-BAD_SIZE_ERR : [chars]: [dec] [chars] events on HDLC Controller were encountered. The SPA is being Restarted.
Explanation The SPA driver detected an error event on the HDLC controller.
Recommended Action CTE1_STD_ACTION


%MCT1E1-3-HDLC_CTRL_ERR : [chars]: [dec] [chars] events on HDLC Controller were encountered.
Explanation The SPA driver detected an error event on the HDLC Controller.
Recommended Action The SPA driver has encountered an error event on the SPA card. CTE1_STD_ACTION


%MCT1E1-3-COR_MEM_ERR : [chars]: [dec] correctable [chars] memory error(s) encountered. The error has been corrected and normal processing should continue. The memory address of most the recent error is: [hex]
Explanation The SPA driver detected a correctable memory error on the SPA card.
Recommended Action The SPA has encountered a correctable memory error on the SPA card. The error has been corrected and normal processing should continue. The hexadecimal memory address of the most recent error is specified in the message text on the console or in the system log. CTE1_STD_ACTION


%MCT1E1-3-UNCOR_PARITY_ERR : [chars]: [dec] [chars] parity error(s) encountered. The address of the most recent error is: [hex]
Explanation The SPA driver detected an uncorrectable parity error condition on the SPA card. Packet corruption may result.
Recommended Action Please power down and reseat the indicated SPA card. CTE1_STD_ACTION


%MCT1E1-2-CMD_DROP : [chars], cmd: [dec], arg0: [dec], arg1: [dec] arg2: [dec], arg3: [dec], vc: [dec] reason: [chars]
Explanation The SPA driver dropped a configuration command. One or more interfaces or controllers associated with the SPA may not be configured correctly.
Recommended Action Please check the configuration of the interfaces and controllers and correct the configuration if necessary. If the condition persists, copy the error message exactly as it appears, and report it to your technical support representative. Please also supply a show tech-support at that time.


%MCT1E1-2-EV_DROP : [chars], cmd: [dec], arg0: [dec], arg1: [dec] arg2: [dec] arg3: [dec] reason [chars]
Explanation The SPA driver dropped an event notification command. Counters or line protocols for one or more interfaces or controllers may be incorrect.
Recommended Action Please restart any interfaces or controllers that are down. If the condition persists, copy the error message exactly as it appears, and report it to your technical support representative. Please also supply a show tech-support at that time.


%MCT1E1-3-FRMR_CLKFAIL : [chars]: Framer input clock failure detected, CTCLK = [chars]CTIVE, LREFCLK = [chars]CTIVE, SREFCLK = [chars]CTIVE, ctclk count [int] lrefclk count [int] srefclk count [int]
Explanation The SPA driver detected failure of one ore more input clocks to the framer chip. The T1/E1 Ports may not operate as expected.
Recommended Action The SPA driver has detected input clock failures on the framer chip. If the ports on the SPA are not operating as expected, power down and reseat the indicated SPA card. CTE1_STD_ACTION


%MCT1E1-3-BATCH_CMD_INVALID_TAG : [chars]: Invalid tag value [dec] at index [dec].
Explanation The SPA driver detected invalid tag value in a batch command.
Recommended Action The SPA driver has detected invalid command format from RP. If the ports on the SPA are not operating as expected, power down and reseat the indicated SPA card. CTE1_STD_ACTION


%MCT1E1-3-PERIODIC_PROCESS : [chars]: periodic process error [chars].
Explanation The SPA driver detected an error with periodic processing routine.
Recommended Action The SPA driver has detected problem with periodic routine. If the ports on the SPA are not operating as expected, power down and reseat the indicated SPA card. CTE1_STD_ACTION


%MCT1E1-3-CMD_FAILED : [chars]: Failed to send command '[chars]' to SPA - [chars].
Explanation The SPA driver could not successfully send a cmd to firmware.
Recommended Action The SPA driver has detected a command failure. If the ports on the SPA are not operating as expected, power down and reseat the indicated SPA card. CTE1_STD_ACTION


%MCT1E1-3-AUTODNR : [chars] failed for slot [dec] bay [dec] err [dec]
Explanation AUTODNR/USNDNR process has failed. The SPA and SIP are out of synchronization. This condition indicates 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.


%MCT1E1-3-TIMEOUT : [chars]: [chars] failed: [dec], state: [dec], ml_id: [dec] progress: [dec]
Explanation Linkrec is stuck at non ready. This condition indicates 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.


%MCT1E1-3-QUEUE_HALT_FAIL : [chars]: Could not suspend message ([dec]) or command ([dec]) queue
Explanation The Message/Command queue could not be stopped prior to the OIR removal of the SPA.
Recommended Action If the ports on the SPA are not operating as expected, power down and reseat the indicated SPA card. CTE1_STD_ACTION


%MCT1E1-3-SPI4_HW_ERR : [chars]: [chars] Hardware error was encountered.
Explanation The SPA driver detected a Hardware error condition on the SPA card. This might result in improper operation.
Recommended Action The SPA driver has encountered a Hardware error on the SPA's SPI4 bus. Please power down and reseat the indicated SPA card. CTE1_STD_ACTION


%MCT1E1-3-FPGA_CNTR_ERR : [chars]: [dec] [chars] error(s) encountered.
Explanation The SPA driver detected an FPGA error condition on the SPA card. Interface packet error counter corruption may result.
Recommended Action The SPA driver has encountered a parity error on the SPA card. The SPA should continue to function normally. If the error condition recurs, please reset the SPA by doing a physical OIR. CTE1_STD_ACTION


%MCT1E1-3-BERT_STOP_ERR : [chars]: Failed to stop BERT operation on interface [chars] - [chars].
Explanation The SPA failed to stop the BERT operation on the indicated interface. The interface might not be functional after this event, if that is the case, try to 'shutdown' and then 'no shutdown' the interface to recover from this failure.
Recommended Action If manual 'shutdown' and then 'no shutdown' of the interface does not restore the operation, then SPA will need to be reloaded to recover from this failure state.


%MCT1E1-3-BERT_OPERATION_ERR : [chars]: BERT operation error on interface [chars] - [chars].
Explanation The SPA reported failure during BERT operation. The current BERT operation will be terminated, but the affected interface might not be operational, if that is the case, try to 'shutdown' and then 'no shutdown' the interface to recover from this failure.
Recommended Action If manual 'shutdown' and then 'no shutdown' of the interface does not restore the operation, then SPA will need to be reloaded to recover from this failure state.


%MCT1E1-3-LOOP_UNSUPPORTED : [chars]: [chars] on port [dec]/[dec]/[dec] and it is not supported on SPA.
Explanation The SPA driver received 'loopback payload' request from the remote device on the SPA card. SPA does not support loopback payload.
Recommended Action The SPA driver has received 'loopback payload' request from the remote device on the SPA card. SPA does not support loopback payload. The remote request is ignored. Please unconfigure the command on the remote device.


%MCT1E1-3-LOOPBACK_CFG_ERR : [chars]: Loop [chars] configuration error on controller [chars] - [chars][chars].
Explanation The SPA reported failure during setting of loop up/down operation. The current loopback will be terminated, but the affected controller might not be operational, if that is the case, try to 'shutdown' and then 'no shutdown' the controller to recover from this failure.
Recommended Action If manual 'shutdown' and then 'no shutdown' of the controller does not restore the operation, then SPA will need to be reloaded to recover from this failure state.


MDNSPROXY

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


%MDNSPROXY-3-PORT_RESERVED_MDNS : [chars] Initialisation failure.
Explanation UDP Port 5353 Already reserved. Please disable the feature which uses 5353 and And Try Again.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


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


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


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


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


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


MDR

%MDR-5-CARD_RESTART : Minimal Disruptive Restart [chars] to acquire provisioned software
Explanation The FRU specified was not running the currently provisioned software, which it will acquire on Minimal Disruptive Restart.
Recommended Action No user action is necessary. This message indicates the system is functioning normally and is provided for informational purposes only.


%MDR-3-NO_ACTIVE_ESP : No active ESP was found when initiating Minimal Disruptive Restart
Explanation An unexpected error has occured where no active ESP was found to continue forwarinding traffic during the Minimal Disruptive Restart. All requested linecards and or modules were reset as normal.
Recommended Action Review the IOSd, RP and CC chassis manager logs for errors or linecard OIR.


%MDR-5-SIP_UNSUPPORTED : [chars] does not support Minimal Disruptive Restart
Explanation The linecard specified was restarted during an Minimal Disruptive Restart, however it does not support this feature either because of its type or there are no SPA's that support Minimal Disruptive Restart inserted. This linecard was reset as normal.
Recommended Action No user action is necessary.


%MDR-5-SPA_UNSUPPORTED : [chars] does not support Minimal Disruptive Restart
Explanation The module specified was restarted during an Minimal Disruptive Restart, however it does not support this feature either because of its type or software version. This module was reset as normal.
Recommended Action No user action is necessary.


%MDR-3-SIP_OFFLINE : [chars] is not online to perform Minimal Disruptive Restart
Explanation An unexpected error has occured where the specified linecard was to undergo Minimal Disruptive Restart however the linecard was not found to be online. The linecard was reset as normal.
Recommended Action Review the IOSd, RP and CC chassis manager logs for errors or linecard OIR.


%MDR-3-SPA_OFFLINE : [chars] in [chars] is not online to perform Minimal Disruptive Restart
Explanation An unexpected error has occured where the specified module was to undergo Minimal Disruptive Restart however the module was not found to be online. The module was reset as normal.
Recommended Action Review the IOSd, RP and CC chassis manager logs for errors or module OIR.


%MDR-3-SPA_IS_NOT_READY : [chars] in [chars] is not ready to perform Minimal Disruptive Restart
Explanation An unexpected error has occured where the specified module was to undergo Minimal Disruptive Restart however the module was not found to be ready. The module was reset as normal.
Recommended Action Review the IOSd, RP and CC chassis manager logs for errors or module OIR.


%MDR-3-SPA_WAS_NOT_READY : [chars] in [chars] was not ready to perform Minimal Disruptive Restart
Explanation An unexpected error has occured where the specified module was to undergo Minimal Disruptive Restart however the module was not found to be ready at the time it was checked. The module was reset was normal.
Recommended Action Review the IOSd, RP and CC chassis manager logs for errors or module OIR.


%MDR-3-NO_SPAS_IN_SIP : No Minimal Disruptive Restart compatible SPAs found in [chars]
Explanation An unexpected error has occured where the specified linecard that was to undergo Minimal Disruptive Restart did not contain any compatible SPAs. This linecard was reset as normal.
Recommended Action Review the IOSd, RP and CC chassis manager logs for errors or module OIR.


%MDR-3-RESTART_FAILED : Failed to perform Minimal Disruptive Restart on [chars]
Explanation An unexpected error has occured where the specified linecard or module failed to undergo a Minimal Disruptive Restart. This linecard or module was reset as normal.
Recommended Action Review the IOSd, RP and CC chassis manager logs for errors.


%MDR-3-READ_SIP_RESET : Failed to read a valid Minimal Disruptive Restart reset value for [chars]
Explanation An unexpected error has occured where either modules in or the specified linecard itself, was to undergo Minimal Disruptive Restart however a valid SIP reset value could not be read. This linecard was reset as normal.
Recommended Action Review the IOSd, RP and CC chassis manager logs for errors.


%MDR-3-READ_COMPAT_INFO : Failed to read valid Minimal Disruptive Restart compatibility information for [chars]
Explanation An unexpected error has occured where either modules in or the specified linecard itself, was to undergo Minimal Disruptive Restart however valid compatibility information could not be read prior to commencing Minimal Disruptive Restart. If the linecard itself was to go through Minimal Disruptive Restart, it and the modules within it were reset as normal. If only modules were going through Minimal Disruptuve Restart, all modules were reset as normal.
Recommended Action Review the IOSd, RP and CC chassis manager logs for errors.


%MDR-3-SOFTWARE_TRANSFER : Failed to receive upgrade software for [chars]
Explanation An unexpected error has occured where the specified linecard was to undergo Minimal Disruptive Restart however the linecard was not able to receive the upgrade software prior to commencing Minimal Disruptive Restart. The linecard was reset as normal.
Recommended Action Review the IOSd, RP and CC chassis manager logs for errors.


%MDR-3-SPA_BAY_INVALID : Could not perform Minimal Disruptive Restart on invalid [chars] in [chars]
Explanation An unexpected error has occured where the specified module was to undergo Minimal Disruptive Restart however the module was invalid.
Recommended Action Review the IOSd, RP and CC chassis manager logs for errors or module OIR.


%MDR-3-SPA_NOT_FOUND : [chars] in [chars] could not be found to perform Minimal Disruptive Restart
Explanation An unexpected error has occured where the specified module was to undergo Minimal Disruptive Restart however the module was not found. The module was reset as normal.
Recommended Action Review the IOSd, RP and CC chassis manager logs for errors or module OIR.


%MDR-3-SPA_TYPE_MISMATCH : Could not perform Minimal Disruptive Restart on [chars] in [chars] due to a SPA type mismatch
Explanation An unexpected error has occured where the specified module was to undergo Minimal Disruptive Restart however the module's SPA type was found to be different to what was expected. The module was reset as normal.
Recommended Action Review the IOSd, RP and CC chassis manager logs for errors or module OIR.


%MDR-3-NODE_ISSU_SIP_WAIT : Could not wait for [chars] to complete Minimal Disruptive Restart
Explanation An unexpected error has occured where the specified linecard was performing a Minimal Disruptive Restart using node ISSU, however Minimal Disruptive Restart did not complete before the next operation needed to commence. This linecard was reset as normal.
Recommended Action Review the IOSd, RP and CC chassis manager logs for errors or module OIR.


%MDR-3-NODE_ISSU_SPA_WAIT : Could not wait for [chars] in [chars] to complete Minimal Disruptive Restart
Explanation An unexpected error has occured where the specified module was performing a Minimal Disruptive Restart using node ISSU, however Minimal Disruptive Restart did not complete before the next operation needed to commence. This module was reset as normal.
Recommended Action Review the IOSd, RP and CC chassis manager logs for errors or module OIR.


MDT_SUBSCRIPTION

%MDT_SUBSCRIPTION-4-INVALID_ARGUMENTS :
Explanation Detailed explanation of why the subscription failed The value of the given parameter is invalid or not specified.
Recommended Action Correct the invalid parameter and try the subscription again.


%MDT_SUBSCRIPTION-4-NOT_SUPPORTED :
Explanation Detailed explanation of why the subscription failed The value of the given parameter is not supported.
Recommended Action Try the subscription again with a supported value.


%MDT_SUBSCRIPTION-4-XPATH_INVALID :
Explanation Detailed explanation of why the subscription failed The specified XPath filter is invalid.
Recommended Action Correct the XPath filter and try the subscription again.


%MDT_SUBSCRIPTION-4-OUTSIDE_LIMIT :
Explanation Detailed explanation of why the subscription failed The value of the parameter is outside of the allowable range.
Recommended Action Try the subscription again with a value within the allowable range.


MEM_MGR

%MEM_MGR-3-MEM_MGR_NOMEM : Out of memory
Explanation System 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.


%MEM_MGR-3-MEM_MGR_EXCEED_MAX : memory pool exceeds maximum ([dec] bytes) allowed.
Explanation An attempt was made to allocate a buffer from the specified memory pool which has reached its maximum limit
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%MEM_MGR-3-MEM_MGR_INVALID : The Memory Management code encounters an invalid parameter.
Explanation It appears that the Memory Management code has received an invalid parameter from its caller.
Recommended Action Copy the error message exactly has it appears, and report it to your technical support representative.


%MEM_MGR-2-DRAM_POOL_CREATE_ERR : return code [dec]
Explanation Creation of public DRAM memory pool failed.
Recommended Action LOG_STD_ACTION


%MEM_MGR-2-SRAM_POOL_CREATE_ERR : return code [dec]
Explanation Creation of public SRAM memory pool failed.
Recommended Action LOG_STD_ACTION


%MEM_MGR-2-DUP_DRAM_POOL_CREATE : pool exists
Explanation Request to create public DRAM memory pool failed because pool already exists.
Recommended Action LOG_STD_ACTION


%MEM_MGR-2-DUP_SRAM_POOL_CREATE : pool exists
Explanation Request to create public SRAM memory pool failed because pool already exists.
Recommended Action LOG_STD_ACTION


%MEM_MGR-3-POOL_CREATE_PARM_ERR : addr [hex], size [int]
Explanation Creation of memory pool failed due to bad parameter value.
Recommended Action LOG_STD_ACTION


%MEM_MGR-3-POOL_APPEND_PARM_ERR : pool handle [hex], addr [hex], size [int]
Explanation Append of additional memory to pool failed due to bad parameter value.
Recommended Action LOG_STD_ACTION


%MEM_MGR-3-POOL_STATS_PARM_ERR : pool handle [hex], stats addr [hex]
Explanation Read of memory pool statistics failed due to bad parameter value.
Recommended Action LOG_STD_ACTION


%MEM_MGR-3-MALLOC_PARM_ERR : pool handle [hex], size [int]
Explanation Memory allocation request failed due to bad parameter value.
Recommended Action LOG_STD_ACTION


%MEM_MGR-3-LOCK_PARM_ERR : pool handle [hex], addr [hex]
Explanation Request to lock memory pool element failed due to bad parameter value.
Recommended Action LOG_STD_ACTION


%MEM_MGR-3-FREE_PARM_ERR : pool handle [hex], addr [hex]
Explanation Memory deallocation request failed due to bad parameter value.
Recommended Action LOG_STD_ACTION


%MEM_MGR-3-DESTROY_PARM_ERR : pool handle [hex]
Explanation Request to delete memory pool failed due to bad parameter value.
Recommended Action LOG_STD_ACTION


%MEM_MGR-2-POOL_CORRUPT : pool handle [hex], magic value [hex], MSGDEF_LIMIT_MEDIUM
Explanation Memory pool data structure has been corrupted.
Recommended Action LOG_STD_ACTION


%MEM_MGR-2-ELEMENT_CORRUPT : pool handle [hex], addr 0x5x, magic value [hex], ref cnt [int], MSGDEF_LIMIT_MEDIUM
Explanation Memory element has been corrupted.
Recommended Action LOG_STD_ACTION


%MEM_MGR-3-MALLOC_NO_MEM : pool handle [hex], size [int], MSGDEF_LIMIT_MEDIUM
Explanation Memory pool allocation request failed due to insufficient memory being available.
Recommended Action LOG_STD_ACTION


%MEM_MGR-3-LOCK_MAX_REF_CNT : pool handle [hex], addr [hex], MSGDEF_LIMIT_MEDIUM
Explanation Request to lock memory pool element failed due to reference count for element already being at the maximum value.
Recommended Action LOG_STD_ACTION


MEM_PROXY

%MEM_PROXY-3-PROXY_IPC_PAK_ALLOC_FAILED :
Explanation Allocation of IPC packet failed.
Recommended Action LOG_STD_ACTION


%MEM_PROXY-3-PROXY_IPC_SEND_FAILED : [chars]
Explanation Could not send IPC request for more memory.
Recommended Action LOG_STD_ACTION


METS

%METS-3-BADMETHOD : Cannot process [chars] method [int]
Explanation A method list function encountered a method list that was unknown, or could not be handled.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%METS-3-NOREGION : No region found: [chars]
Explanation Resource failure: No region 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.


%METS-3-NULLPOOL : Can't process null pool: [chars]
Explanation Resource failure: Null pool in the region
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%METS-2-INITFAIL : Can't start analysis
Explanation The requested operation failed due to lack of resource, maybe temporarily
Recommended Action Reduce system resource/memory usage, and retry for the commands.


MFI

%MFI-3-REDISTMGR : Redistribution Manager: [chars] [hex]
Explanation Redistribution Manager 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.


%MFI-3-REDISTMGR2 : Redistribution Manager: [chars] [hex] [hex]
Explanation Redistribution Manager 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.


%MFI-4-REDISTMGR3 : Redistribution Manager: [chars] [hex]
Explanation Redistribution Manager 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.


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


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


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


%MFI-3-REPLYMSGSIZE : Reply message is too large: [chars]: [dec]
Explanation read update message won't fit into xdr buffer
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%MFI-3-EVTLOGCONTROL : [chars]: [dec]
Explanation General Event Logger Controller 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.


%MFI-3-BADREADUPDATESIZE : Read update reply message from RP has bad size: [dec]
Explanation read update message does not match the read message parse result
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%MFI-3-PNDMSGMGR : [chars] [chars] [dec] [dec] [dec]
Explanation Only one outstanding request is allowed from same 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.


%MFI-4-NOCLIENTREQ : [chars] [chars]: [dec] [dec] [dec]
Explanation Client reply could not find an outstanding request
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%MFI-3-LCPULSE : LC pulse failed: [chars] [dec]
Explanation LC pulse request 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.


%MFI-3-MFICOMM : [chars]
Explanation MFI General Communication 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.


%MFI-3-MFICOMM2 : [chars]: [hex] [hex]
Explanation MFI General Communication 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.


%MFI-3-MFICOMM3 : [chars]: [hex] [hex] [hex]
Explanation MFI General Communication 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.


%MFI-4-MFICOMM_WARN_1 : [chars]: [hex]
Explanation MFI General Communication 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.


%MFI-3-CLIENT_INTF : [chars]: [hex] [hex]
Explanation Client 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.


%MFI-3-MPLS_MTU_SET : [chars] [dec] [chars] [chars] [chars] [dec][chars]
Explanation Most drivers will be able to support baby giants and will gracefully drop packets that are too large. Certain drivers will have packet forwarding problems including data corruption.
Recommended Action Please increase the interface mtu on all routers connected to this interface to the needed mtu size using mtu bytes command.


MFIB

%MFIB-6-PAK_TTL_ONE_V4 : IPV4 Multicast Packet received with ttl <= 1
Explanation An IP non-linklocal multicast packet received with ttl 1
Recommended Action No action is required.


%MFIB-6-PAK_TTL_ONE_V6 : IPV6 Multicast Packet received with ttl <= 1
Explanation An IPv6 non-linklocal multicast packet received with ttl 1
Recommended Action No action is required.


%MFIB-6-PAK_TOO_SHORT : Packet too short from [chars], datagram size [dec], tl [dec]
Explanation An IP/IPv6 packet which is too short was received
Recommended Action No action is required.


%MFIB-3-NETWORK_GET_FAIL : MFIB can not get network offset: datagram [hex]; network [hex]
Explanation The MFIB failed to find a suitable packet network offset
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.


%MFIB-3-NETWORK_SET_FAIL : MFIB can not set network offset: datagram [hex]; length [dec]; offset [dec]
Explanation The MFIB failed to set offset within packet
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.


%MFIB-3-MFIB_CTXT_DEPTH_EXCEEDED :
Explanation MFIB has exceeded maximum number of switching contexts
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.


%MFIB-3-ADJ_GSB_REGISTER :
Explanation Could not register an adjacency GSB identifier
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.


%MFIB-3-ADJ_GSB_INIT :
Explanation Could not initialise the adjacency GSB memory pool
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.


%MFIB-3-SR_ADJ_GSB_REGISTER :
Explanation Could not register an SR adjacency GSB identifier
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.


%MFIB-3-SR_ADJ_INCORRECT_ADD : A different MFIB Service Reflect adj is being added
Explanation A different SR adjacency subblock is being added to the adjacency without first removing the existing one. This indicates that SR forwarding may no longer work correctly
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.


%MFIB-3-SR_ADJ_GSB_INIT :
Explanation Could not initialise the SR adjacency GSB memory pool
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.


%MFIB-3-MRIB_PROCESS : [chars][chars]
Explanation The MFIB process which intefaces with the MRIB failed to start. The MFIB will be unusable.
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.


%MFIB-6-MFIB_HEADER_LIMIT_EXCEEDED : [dec] at [chars]
Explanation MFIB attempted to exceed maximum number of replicated packet header buffers
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.


%MFIB-6-MFIB_POOL_GETBUFFER_FAILURE :
Explanation MFIB has failed in an attempt to retrieve a particular type of memory. The MFIB will continue using another memory area
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.


%MFIB-3-ILLEGALARGS : Illegal arguments - [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.


%MFIB-3-DECAP_OCE_CREATION_FAILED : Decap OCE creation failed for [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.


%MFIB-3-WIRE_LOOKUP_OR_ALLOC_FAILED : Lookup or allocation of MFIB wire failed
Explanation Lookup or allocation of MFIB wire 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.


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


MFIB_PLTF through MPLSMFISTATIC

MFIB_PLTF

%MFIB_PLTF-3-UPDATE_SET_MEMORY : [chars] [IPV6 address] -> [chars] [[IPV6 address] ([IPV6 address]/[chars])]
Explanation Failed to allocate memory for platform transaction.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.


%MFIB_PLTF-3-TRANSACTION_MEMORY : [dec] [dec]
Explanation Failed to allocate memory for platform transaction.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.


%MFIB_PLTF-3-HANDLE_CONSTRAINT : [chars] [IPV6 address]
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.


%MFIB_PLTF-3-TABLE_HANDLE_BAD : [chars]. [IPV6 address]
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.


%MFIB_PLTF-3-ENTRY_HANDLE_BAD : [chars]. [IPV6 address]
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.


%MFIB_PLTF-3-IOITEM_HANDLE_BAD : [chars]. [IPV6 address]
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.


%MFIB_PLTF-3-TABLE_LOCK_FAIL : [chars]. [chars] table [IPV6 address] [IPV6 address] ([IPV6 address]/[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.


%MFIB_PLTF-3-TABLE_UNLOCK_FAIL : [chars]. [chars] table [IPV6 address] [IPV6 address] ([IPV6 address]/[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.


%MFIB_PLTF-3-ENTRY_LOCK_FAIL : [chars]. [chars] entry [IPV6 address] [chars] [[IPV6 address] ([IPV6 address]/[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.


%MFIB_PLTF-3-ENTRY_UNLOCK_FAIL : [chars]. [chars] entry [IPV6 address] [chars] [[IPV6 address] ([IPV6 address]/[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.


%MFIB_PLTF-3-IOITEM_LOCK_FAIL : [chars]. [chars] ioitem [IPV6 address] [chars] [chars] [[IPV6 address] ([IPV6 address]/[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.


%MFIB_PLTF-3-IOITEM_UNLOCK_FAIL : [chars]. [chars] ioitem [IPV6 address] [chars] [chars] [[IPV6 address] ([IPV6 address]/[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.


%MFIB_PLTF-7-ENTRY_DUPLICATE_ADD : [chars] entry [chars] [[IPV6 address] ([IPV6 address]/[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.


%MFIB_PLTF-3-IOITEM_DUPLICATE_ADD : [chars] ioitem [chars] [chars] [[IPV6 address] ([hex]/[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.


%MFIB_PLTF-3-ANNOT_TOO_LONG : [chars] [IPV6 address] [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.


%MFIB_PLTF-3-CALLBACK_RETURN_INVALID : [chars]. [IPV6 address] [IPV6 address] [IPV6 address]
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.


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


%MFIB_PLTF-3-XDRISSUREGERROR : ISSU client [chars] ([dec]), entity [dec], failed ISSU registration: [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.


MFI_LABEL_BROKER

%MFI_LABEL_BROKER-3-UNREG_LDM : [chars]
Explanation An MPLS application requested label broker services without registering first.
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version<NoCmd Bold> and <CmdBold>show running-config and contact your Cisco technical support representative.


%MFI_LABEL_BROKER-3-DUPREG_LDM : [chars]
Explanation An MPLS application is registering multiple times with the label broker.
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version<NoCmd Bold> and <CmdBold>show running-config and contact your Cisco technical support representative.


%MFI_LABEL_BROKER-3-INVALID_PROC_EVT : [chars][dec][chars][dec]
Explanation The MFI Label Broker received an invalid process event from the IOS-on-Neutrino infrastructure.
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version<NoCmd Bold> and <CmdBold>show running-config and contact your Cisco technical support representative.


%MFI_LABEL_BROKER-3-INVALID_LDM : [dec]
Explanation The MFI Label Broker received a (un)registration request from an invalid MPLS application.
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version<NoCmd Bold> and <CmdBold>show running-config and contact your Cisco technical support representative.


%MFI_LABEL_BROKER-3-NULL_KEY :
Explanation The MFI Label Broker received a null key pointer
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version<NoCmd Bold> and <CmdBold>show running-config and contact your Cisco technical support representative.


%MFI_LABEL_BROKER-3-INVALID_PID : LDM([dec]), PID([dec])
Explanation The MFI Label Broker received a registration request with invalid PID.
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version<NoCmd Bold> and <CmdBold>show running-config and contact your Cisco technical support representative.


%MFI_LABEL_BROKER-3-INVALID_LABEL : [dec]
Explanation The MFI Label Broker received a request to allocate an invalid label.
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version<NoCmd Bold> and <CmdBold>show running-config and contact your Cisco technical support representative.


%MFI_LABEL_BROKER-3-INVALID_PARAM : [chars]
Explanation The MFI Label Broker received an invalid parameter in a request to allocate or free a local label.
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version<NoCmd Bold> and <CmdBold>show running-config and contact your Cisco technical support representative.


%MFI_LABEL_BROKER-3-MULTIPLE_BIND : Label [dec] in table [dec], [chars], [chars] [p/bm [dec]/[hex]],ldm request info: [chars]
Explanation The MFI Label Broker received a request to bind the label to a prefix, but the label is already bound to another prefix.
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version<NoCmd Bold>, <CmdBold>show running-config and show mpls forwarding-table and contact your Cisco technical support representative.


%MFI_LABEL_BROKER-3-DELETE_MOI_FAIL : Label [dec] in table [dec], [chars], [chars]
Explanation The MFI Label Broker could not honor a request to immediately handle the process restart of the application indicated. It will try to handle it in the background
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version<NoCmd Bold>, <CmdBold>show running-config and show mpls infrastructure label-broker ldm (this latter command is present only when service internal is enabled) and contact your Cisco technical support representative.


%MFI_LABEL_BROKER-3-IMMEDIATE_LDM_RESTART : application [chars]
Explanation
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version<NoCmd Bold> and <CmdBold>show running-config and contact your Cisco technical support representative.


%MFI_LABEL_BROKER-3-NO_ACTIVE_LABEL : [chars] Label [dec] in table [dec], [chars] [hex]
Explanation The MFI Label Broker encountered a situation where there is no currently active label for applications to use for the FEC indicated.
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version<NoCmd Bold>, <CmdBold>show running-config, show mpls forwarding-table internal and contact your Cisco technical support representative.


%MFI_LABEL_BROKER-3-LABEL_PROGRAM_FAIL : Label [dec] in table [dec], for [chars]
Explanation The MFI Label Broker was unable to program the label in question for the mentioned FEC.
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version<NoCmd Bold>, <CmdBold>show running-config, show mpls forwarding-table internal and contact your Cisco technical support representative.


%MFI_LABEL_BROKER-3-OS_NOTIFY : Process id [dec] [chars], error code [dec]
Explanation The MFI Label Broker was unable to notify the operating system about (un)registration of the specified process.
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version<NoCmd Bold>, <CmdBold>show running-config, show mpls infrastructure label-broker ldm and contact your Cisco technical support representative.


MGCP_APP

%MGCP_APP-6-PROCESS_CREATION_FAILED : Cannot create MGCP application process
Explanation Failed to create the MGCP application process.
Recommended Action Check the size of free memory to make sure there is enough memory.


%MGCP_APP-6-SOCKET_OPEN_FAILED : Failed to open UDP port for MGCP
Explanation Failed to open UDP port for the MGCP process.
Recommended Action Check if any other application use the same UDP port number (2427).


%MGCP_APP-6-CALL_REC_DATABASE_FAILED : Failed to create call record database
Explanation Failed to create call record database.
Recommended Action


%MGCP_APP-6-DIGIT_MAP_DATABASE_FAILED : Failed to create digit map database
Explanation
Recommended Action Check the size of free memory to make sure there is enough memory.


%MGCP_APP-6-TRANS_ID_DATABASE_FAILED : Failed to Trans Id database
Explanation Failed to create transaction id database.
Recommended Action Check the size of free memory to make sure there is enough memory.


%MGCP_APP-6-TIMER_QUEUE_FAILED : Failed to create Timer watched queue
Explanation Failed to create Timer watched queue.
Recommended Action Check the size of free memory to make sure there is enough memory.


%MGCP_APP-6-DNS_QUEUE_FAILED : Failed to create DNS message watched queue
Explanation Failed to create DNS message watched queue.
Recommended Action Check the size of free memory to make sure there is enough memory.


%MGCP_APP-6-TFTP_QUEUE_FAILED : Failed to create TFTP message watched queue
Explanation Failed to create TFTP message watched queue.
Recommended Action Check the size of free memory to make sure there is enough memory.


%MGCP_APP-6-SYS_QUEUE_FAILED : Failed to create MGCP system message watched queue
Explanation Failed to create MGCP system message watched queue.
Recommended Action Check the size of free memory to make sure there is enough memory.


%MGCP_APP-6-GEN_INIT_FAILED : Failed to initialize MGCP services
Explanation Failed to initialize MGCP services.
Recommended Action Check the size of free memory to make sure there is enough memory.


%MGCP_APP-6-GEN_INIT_NO_IP_INTF_FAILED : Suspended initialization of MGCP services. No IP interface up yet
Explanation Suspended initialization of MGCP services. No IP interface up yet
Recommended Action Make sure there is atleast one interface configured with an IP Address


%MGCP_APP-6-RTP_SERVICES_INIT_FAILED : Failed to start VOIP call leg
Explanation Failed to start VOIP call leg.
Recommended Action Check the size of free memory to make sure there is enough memory.


%MGCP_APP-6-NEDB_SETUP_FAILED : Failed to Initialize MGCP Notified Entity Database
Explanation Failed to Create Initialize MGCP Notified Entity Database Resources.
Recommended Action Check the size of free memory to make sure there is enough memory.


%MGCP_APP-6-CCAPI_APP_REGISTER_FAILED : Failed to register MGCP Application with CCAPI
Explanation Failed to register MGCP Application with CCAPI.
Recommended Action Check the size of free memory to make sure there is enough memory.


%MGCP_APP-6-EVT_NODE_ALLOC_FAILED : Failed to allocate memory for event node
Explanation Failed to allocate memory for event node.
Recommended Action Check the size of free memory to make sure there is enough memory.


%MGCP_APP-6-MGCP_SHUTDOWN_COMPLETE : MGCP Shutdown has completed
Explanation MGCP will complete shutdown after all voice interfaces go back onhook
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%MGCP_APP-6-MGCP_SHUTDOWN_FAILED : MGCP services intitialization in progress. Shutdown request failed.
Explanation Unable to shutdown MGCP services while initialization is in progress.
Recommended Action Wait for MGCP services initializtion to complete,. Retry shutdown.


%MGCP_APP-6-MGCP_CONTROL_BIND_REMOVED : MGCP control bind command is being removed, interface not found
Explanation Unable to find bound interface
Recommended Action Reconfigure control bind command for MGCP.


%MGCP_APP-6-MGCP_MEDIA_BIND_REMOVED : MGCP media bind command is being removed, interface not found.
Explanation Unable to find bound interface
Recommended Action Reconfigure media bind command for MGCP.


%MGCP_APP-6-MGCP_BIND_REMOVED : Bind commmand removed from this interface because of active SGCP/MGCP calls.
Explanation There are active calls because of this Bind command for control and media will be removed
Recommended Action Configure bind command when there are no active SGCP/MGCP calls.


%MGCP_APP-6-MGCPAPP_FALLBACK_DEACTIVATED : The gateway is out of fallback mode
Explanation Communication with call agent is reestablished
Recommended Action No action needed


%MGCP_APP-6-MGCPAPP_FALLBACK_ACTIVATED : The gateway is in fallback mode
Explanation Communication with call agent is disrupted
Recommended Action The connectivity between gateway and CA must be reestablished


%MGCP_APP-6-MGCPAPP_FALLBACK_TIMER_FAIL : Unable to start fallback timer
Explanation Failed to start the keepalive message timer
Recommended Action Check the size of free memory to make sure there is enough memory.


%MGCP_APP-6-MGCP_CHUNK_DESTROY_FAILED : Chunk pool [chars] ([IPV6 address]) could not be destroyed. Possible memory leak.
Explanation Chunks within the pool are probably still 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.


MLDP

%MLDP-2-PROCESS_ERR : Error initializing MLDP process
Explanation Can't start the MLDP process
Recommended Action No action is required.


%MLDP-2-MRIB_PROCESS_ERR : Error initializing MLDP MRIB process
Explanation Can't start the MLDP MRIB process
Recommended Action No action is required.


%MLDP-2-CHUNK_ERR : Error initializing MLDP db chunks
Explanation Error initializing MLDP db chunks
Recommended Action No action is required.


%MLDP-2-RADIX_DB_ERR : Error initializing MLDP DB radix tree
Explanation Error initializing MLDP_DB radix ree
Recommended Action No action is required.


%MLDP-2-FEC_ERR : Error, the FEC size is too large
Explanation The FEC size is too large
Recommended Action No action is required.


%MLDP-2-PEER_ERR : Received attached address [IP_address], but there is no LDP peer
Explanation Internal error
Recommended Action No action is required.


%MLDP-2-RADIX_BRANCH_ERR : Error initializing MLDP BRANCH radix tree
Explanation Internal error
Recommended Action No action is required.


%MLDP-5-ADD_BRANCH : [chars] Root: [IP_address], Add [chars] branch [chars] [chars]
Explanation Logging of changes to mLDP branch
Recommended Action No action is required.


%MLDP-5-MODIFY_BRANCH : [chars] Root: [IP_address], Modify [chars] branch [chars] [chars]
Explanation Logging of changes to mLDP branch
Recommended Action No action is required.


%MLDP-5-DELETE_BRANCH : [chars] Root: [IP_address], Delete [chars] branch [chars] [chars]
Explanation Logging of changes to mLDP branch
Recommended Action No action is required.


%MLDP-5-MODIFY_NBR : [chars] Root: [IP_address], Modify [chars] entry peer [chars] [chars]
Explanation Logging of changes to mLDP entry peer
Recommended Action No action is required.


%MLDP-4-DB_BRANCH_DEL_PENDING : [chars] tree, with LSM ID: [hex] has both IPv4 and IPv6 del_pending set
Explanation An mLDP database entry has both the IPv4 and IPv6 del_pending flags set to TRUE -- This is an inconsistent 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.


%MLDP-2-INTERNAL_ERR : Internal mLDP error
Explanation Internal error
Recommended Action No action is required.


%MLDP-5-ROUTING_LOOP : There is a routing loop for this root.
Explanation There is a routing loop for this root
Recommended Action No action is required.


%MLDP-2-FEC_CHUNK_ERR : Error initializing MLDP FEC chunks
Explanation Error initializing MLDP FEC chunks
Recommended Action No action is required.


%MLDP-2-FEC_TBL_ERR : Error initializing MLDP FEC tbl
Explanation Error initializing MLDP FEC tbl
Recommended Action No action is required.


%MLDP-2-FEC_NTF_ERR : Error initializing MLDP FEC notifier
Explanation Error initializing MLDP FEC notifier
Recommended Action No action is required.


%MLDP-2-FILTER_CHUNK_ERR : Error initializing MLDP filter chunks
Explanation Error initializing MLDP filter chunks
Recommended Action No action is required.


%MLDP-2-FILTER_TBL_ERR : Error initializing MLDP filter tbl
Explanation Error initializing MLDP filter tbl
Recommended Action No action is required.


%MLDP-2-FILTER_NTF_ERR : Error registering MLDP filter FEC notifier
Explanation Error registering MLDP filter FEC notifier
Recommended Action No action is required.


%MLDP-2-HA_INSERT_ERR : Error inserting node into MLDP HA radix tree
Explanation Error inserting node into MLDP HA radix tree
Recommended Action No action is required.


%MLDP-2-ID_RESERVE_ERR : Error reserving id for mldp database
Explanation Error reserving id for mldp database
Recommended Action No action is required.


%MLDP-2-PEER_NOT_FOUND : Peer doesn't exist while syncing to standby
Explanation Peer doesn't exist while syncing to standby
Recommended Action No action is required.


%MLDP-2-ROOT_NOT_FOUND : Root doesn't exist while syncing to standby.
Explanation Root doesn't exist while syncing to standby
Recommended Action No action is required.


MMA

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


%MMA-3-LIST : Failed to [chars] list [chars]
Explanation A list operation failed. This could be caused by memory corruption
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


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


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


%MMA-3-INV_MONITOR : The flow monitor pointer is invalid
Explanation An internal error occurred. The performance-monitor monitor pointer saved in the common monitor is NULL
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


%MMA-3-INV_COMMON_MONITOR : The common monitor pointer is invalid
Explanation An internal error occurred. The common monitor pointer saved in the performance-monitor monitor is NULL
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


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


%MMA-3-INV_DB_OBJ : Internal error, mma db pointer invalid
Explanation No valid pointer to mma 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.


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


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


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


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


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


%MMA-3-CHUNKMALLOC : Failed to malloc chunk memory for [chars]
Explanation Unable to malloc memory chunk, malloc 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.


%MMA-3-FLOW_EXCEED : The number of flows has exceeded 95%% of the configured maximum flow. [chars]
Explanation This is warning message if the flow size exceeds the maximum 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.


%MMA-3-FLOW_NONEXCEED : The number of flows is below 85%% of the configured maximum flow. [chars]
Explanation This is info message if the flow size falls below the maximum 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.


%MMA-3-CACHE_OVERFLOW : The number of flows has exceeded 95%% of the configured size, monitor [chars], please increase cache size
Explanation This is warning message if the flow size exceeds the maximum 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.


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


%MMA-3-INV_ACTION_OBJ : action object is not valid - [chars]
Explanation This is an internal error, the saved action object info is corrupted
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information.


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


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


%MMA-3-INV_ARG : The argument is not valid - [chars]
Explanation An internal error occurred. The argument for an internal API is not 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.


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


%MMA-3-IPC_OPEN_REPLY : IPC Open Reply failed, request [int]
Explanation For a request from upper MMA software stack layers it was not possible to open the reply buffer. The consequence of this could be a stuck binding 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


%MMA-3-IPC_NORES : No space for the IPC reply, size [int]
Explanation For a request from upper MMA 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 binding 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


%MMA-2-IPC_INIT : IPC message handler registration failure, rc [int]
Explanation Registering an IPC message handler for the MMA feature failed. This will cause the feature to not function.
Recommended Action This is normally a software issue. The consequences are that the MMA feature will not function. LOG_STD_ACTION


MN_SPA_PTP

%MN_SPA_PTP-6-CONFIG_CHANGE : Change in ToP configuration on [dec]/[dec]. This will result into Termination of all existing PTP sessions on [dec]/[dec].
Explanation To take effect of new/changed configuration requrie restart of PTP session
Recommended Action No further action required. (This is an INFORMATION message, not an error Message.)


%MN_SPA_PTP-3-SEMAHOG : SEMAHOG by SPA [chars] Process holding Sema is [chars]
Explanation SEMAPHORE LOCK ERROR
Recommended Action Remove the config which caused this


%MN_SPA_PTP-4-PTP_CLOCK_MODE : SPA [dec]/[dec] is working in PTP SLAVE or Boundary mode external clock on BITS port would be PTP recovered clock
Explanation Info regarding external clock in PTP slave mode
Recommended Action No further action required. (This is an INFORMATION message, not an error Message.)


%MN_SPA_PTP-6-SPLL_STATE_CHANGE : Recovered clock in [dec]/[dec] status changed to [chars]
Explanation Recovered clock status change info
Recommended Action No further action required. (This is an INFORMATION message, not an error Message.)


%MN_SPA_PTP-3-GMII_LINKUP_DOWN : GMII Links are [chars] and [chars] for ports 1 and 2 respectively on the SPA.
Explanation Error Message: GMII link status has changed on the SPA.
Recommended Action OIR the SPA to recover from the error.


%MN_SPA_PTP-3-BITS_CLOCK : [chars] : SPA bits transmit clock has encountered error : [hex] .
Explanation Error message regarding BITS transmit clock failure
Recommended Action OIR the SPA if the error is consistent


MODULE_STATE

%MODULE_STATE-3-MOD_TIMEOUT : Timeout waiting for modules to come on-line.
Explanation One or more modules can not come on-line.
Recommended Action


%MODULE_STATE-6-ALL_MODULES_UP : All modules are now on-line.
Explanation All modules are now on-line.
Recommended Action


MONITOR

%MONITOR-3-VPN_EVENT : ipsec : [chars] : [dec] events, MSGDEF_LIMIT_FAST
Explanation Crypto failure count hits limit. This message is just a warning, not an error.
Recommended Action LOG_STD_ACTION


%MONITOR-3-VARSETFAIL : ROM monitor variable set of [chars] failed.
Explanation The system could not set a ROM Monitor variable. This condition typically occurs when no ROM monitor memory is available to save the variable. The ROM monitor memory is most likely already filled with configuration boot commands.
Recommended Action Enter the show bootvar command and check the output to see if there is anything unusual with the system. Try to reduce the number of configuration boot commands.


%MONITOR-3-VARRESTFAIL : ROM monitor variable restoration of [chars], failed.
Explanation The new ROM monitor variable could not be written to memory, and the ROM monitor variable could not be restored to its original value.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support and show bootvar commands to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support and show bootvar command output, contact your Cisco technical support representative and provide the representative with the gathered information.


MPLSIFMIB

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


MPLSMFISTATIC

%MPLSMFISTATIC-3-FCALLFAILED : [chars]
Explanation MPLS MFI Static Application function call return error
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version and show running-config and contact your Cisco technical support representative.


%MPLSMFISTATIC-3-INVALIDPRAMS : [chars] [dec]
Explanation Unexpected MPLS MFI Static Application parameter error
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version and show running-config and contact your Cisco technical support representative.


%MPLSMFISTATIC-3-WRONGCODEPATH : [chars]
Explanation Unexpected MPLS MFI Static Application code path error
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version and show running-config and contact your Cisco technical support representative.


%MPLSMFISTATIC-3-CHUNKMGR : [chars] [hex]
Explanation MPLS MFI Static Application chunk manager error has occurred.
Recommended Action Problem may be due to a low memory condition on the device. Check system memory and minimum memory requirements for this release and configuration, and add memory if required. If memory appears to be sufficient and problem persists, refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show process memory, show version and show running-config and contact your Cisco technical support representative.