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 |