MPLS_TP_LSP through NAT
MPLS_TP_LSP
%MPLS_TP_LSP-3-UPDOWN : [chars] LSP [chars] is [chars][chars][chars] | |
---|---|
Explanation | The indicated MPLS-TP LSP has gone up or down. If the LSP went down, the failure condition, and the fault source information is provided. |
Recommended Action | Examine the failure condition and source information to determine why the LSP went down. |
%MPLS_TP_LSP-5-LOCKOUT : [chars] LSP [chars] [chars] lockout state | |
---|---|
Explanation | The indicated LSP has entered or exited lockout state due to administrative action at one endpoint |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%MPLS_TP_LSP-5-CONFIG_CHANGED : LSP [chars] is [chars] | |
---|---|
Explanation | The configuration of the MPLS-TP midpoint LSP has changed. This message is to notify the NMS of changes. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
MPLS_TP_LSP_FSM
%MPLS_TP_LSP_FSM-3-LSP_FSM_ERROR : LSP FSM Error occurred. Received event:[chars] in state:[chars] | |
---|---|
Explanation | An erroneous event was received by the TP LSP. This is an error internal to MPLS-TP |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
MPLS_TP_MEM
%MPLS_TP_MEM-3-NO_MEM : Could not allocate memory for MPLS-TP context | |
---|---|
Explanation | Could not allocate memory for MPLS-TP context. This is an internal issue to MPLS-TP |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
MPLS_TP_PROC
%MPLS_TP_PROC-3-PROC_CREATE_FAIL : [chars] [chars] [dec] | |
---|---|
Explanation | Could not create MPLS-TP process. This is an internal issue to MPLS-TP |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%MPLS_TP_PROC-3-UNKNOWN_MESSAGE : Received unknwon message:[dec] | |
---|---|
Explanation | An unknown message was posted to the MPLS-TP process. This is an internal issue to MPLS-TP |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%MPLS_TP_PROC-3-UNKNOWN_EVENT : Received unknown event: Major:[dec] Minor:[dec] | |
---|---|
Explanation | An unknown event was posted to the MPLS-TP queue. This is an internal issue to MPLS-TP. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
MPLS_TP_TIMER
%MPLS_TP_TIMER-3-UNKNOWN_TIMER_TYPE_EXPIRY : Unknown timer type expired:[dec] | |
---|---|
Explanation | An unknown MPLS-TP timer type expired. This is an issue internal to MPLS-TP |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
MSG_FIFO
%MSG_FIFO-2-MSG_FIFO_CREATE : [chars]: Bad parameter to message fifo creaate [chars] = [hex] | |
---|---|
Explanation | Failed to create message fifo, invalid memory size or other parameter. |
Recommended Action | LOG_STD_ACTION |
MSG_POS_OC3_OC12_SPA
%MSG_POS_OC3_OC12_SPA-3-IOFPGA_INIT : [chars] (slot [dec]; bay [dec]) Device IOFPGA initialization failed. | |
---|---|
Explanation | IOFPGA Device initialization failed. It indicates FPGA associated PLL lock or interrupt issues. It may also indicate a hardware failure. |
Recommended Action | Change the hardware or copy the error message exactly as it appears, and report it to your technical support representative. |
%MSG_POS_OC3_OC12_SPA-3-FRAMER_INIT : [chars] (slot [dec]; bay [dec]) Device Framer initialization failed. | |
---|---|
Explanation | Framer device initialization failed. It indicates a hardware failure. |
Recommended Action | Change the hardware or copy the error message exactly as it appears, and report it to your technical support representative. |
%MSG_POS_OC3_OC12_SPA-3-SPI42_INIT : [chars] (slot [dec]; bay [dec]) Device SPi42 initialization failed. | |
---|---|
Explanation | SPi42 Device initialization failed. It indicates a hardware failure. |
Recommended Action | Change the hardware or copy the error message exactly as it appears, and report it to your technical support representative. |
%MSG_POS_OC3_OC12_SPA-3-AUXC2W_INIT : [chars] (slot [dec]; bay [dec]) Device Auxiliary C2W initialization failed. | |
---|---|
Explanation | Auxiliary C2W bus initialization failed. It indicates a hardware failure. |
Recommended Action | Change the hardware or copy the error message exactly as it appears, and report it to your technical support representative. |
%MSG_POS_OC3_OC12_SPA-3-SMM665_INIT : [chars] (slot [dec]; bay [dec]) Device SMM665 initialization failed. | |
---|---|
Explanation | SMM665 Summit Controller initialization failed. It indicates a hardware failure. |
Recommended Action | Change the hardware or copy the error message exactly as it appears, and report it to your technical support representative. |
%MSG_POS_OC3_OC12_SPA-3-MAX1668_INIT : [chars] (slot [dec]; bay [dec]) Device MAX1668 initialization failed. | |
---|---|
Explanation | MAX1668 temperature sensor initialization failed. It indicates a hardware failure. |
Recommended Action | Change the hardware or copy the error message exactly as it appears, and report it to your technical support representative. |
%MSG_POS_OC3_OC12_SPA-3-DS1844_INIT : [chars] (slot [dec]; bay [dec]) Device DS1844 initialization failed. | |
---|---|
Explanation | DS1844 potentiometer initialization failed. It indicates a hardware failure |
Recommended Action | Change the hardware or copy the error message exactly as it appears, and report it to your technical support representative. |
%MSG_POS_OC3_OC12_SPA-3-RESOURCE_ERROR : [chars] ([hex], [hex], [hex]) [chars] | |
---|---|
Explanation | Failed to get required interface. |
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. |
%MSG_POS_OC3_OC12_SPA-3-IOFPGA_CREATE : [chars] (slot [dec]; bay [dec]) Device IOFPGA creation failed. | |
---|---|
Explanation | IOFPGA Device creation failed. |
Recommended Action | Change the hardware or copy the error message exactly as it appears, and report it to your technical support representative. |
%MSG_POS_OC3_OC12_SPA-3-FRAMER_CREATE : [chars] (slot [dec]; bay [dec]) Device Framer creation failed. | |
---|---|
Explanation | Framer device creation failed. |
Recommended Action | Change the hardware or copy the error message exactly as it appears, and report it to your technical support representative. |
%MSG_POS_OC3_OC12_SPA-3-SPI42_CREATE : [chars] (slot [dec]; bay [dec]) Device SPi42 creation failed. | |
---|---|
Explanation | SPi4.2 Device creation failed |
Recommended Action | Change the hardware or copy the error message exactly as it appears, and report it to your technical support representative. |
%MSG_POS_OC3_OC12_SPA-3-XCVR_RATE_NOTSUPPORTED : [chars] (slot [dec]; bay [dec]) Tranceiver rate not supported on the SPA. | |
---|---|
Explanation | Tranceiver rate not supported on the SPA. |
Recommended Action | Remove the tranceiver module and insert a valid module with rate that is supported on the SPA. |
%MSG_POS_OC3_OC12_SPA-3-XCVR_ANALYZE : [chars] (slot [dec]; bay [dec]; port [dec]) Tranceiver analyze failed. | |
---|---|
Explanation | Tranceiver analyze failed |
Recommended Action |
MTRIE
%MTRIE-4-MTRIECORRUPTLEAF : [IP_address]/[dec] - [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. |
%MTRIE-4-MTRIELEAFOPFAIL : [IP_address]/[dec] - [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. |
%MTRIE-4-PLACEALLOC : Failed to allocate place holder | |
---|---|
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. |
%MTRIE-4-MTRIEMISALIGNEDNODEPTR : [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. |
MX
%MX-6-NOMEM : [chars] bufhdr allocation failure, MSGDEF_LIMIT_MEDIUM | |
---|---|
Explanation | An attempt to allocate memory failed. This could cause features that manage packets in multiple pieces, or that directly export data, not to work properly in some cases. |
Recommended Action | LOG_STD_ACTION |
%MX-3-CARVE : [chars]: size [int] too small | |
---|---|
Explanation | A software error resulted in an attempt to create buffers in an area of memory that was too small. |
Recommended Action | LOG_STD_ACTION |
%MX-3-RESIZE : [chars]: non-contiguous resize: orig [hex]/[hex], new [hex]/[hex], MSGDEF_LIMIT_MEDIUM | |
---|---|
Explanation | A software error was detected during a resize operation on the specified memory region. |
Recommended Action | LOG_STD_ACTION |
%MX-6-NOBUFHDR : [chars] | |
---|---|
Explanation | An attempt to add buffers within a memory region failed. |
Recommended Action | LOG_STD_ACTION |
%MX-3-MAXPOOLS : too low | |
---|---|
Explanation | A source code inconsistency was detected. |
Recommended Action | Increase the number of pools allowed. |
%MX-3-INITBUFHDR : [chars]: mgmt memory allocation failure (size [int]) | |
---|---|
Explanation | insufficient mgmt memory provided for initialization of the external memory manager, which will cause features that manage packets in multiple pieces, or that directly export data, not to work properly. |
Recommended Action | LOG_STD_ACTION |
%MX-3-BADSTART : [chars]: [hex] (current [hex], size [int]) | |
---|---|
Explanation | A software error was detected during an attempt to increase the size of an external memory region. |
Recommended Action | LOG_STD_ACTION |
%MX-3-BADPOOL : [chars]: [int] | |
---|---|
Explanation | Software detected the use of an invalid pool index, which may be the result of incompatible software versions on different system components. |
Recommended Action | LOG_STD_ACTION |
%MX-3-BADFEAT : [chars]: [dec] | |
---|---|
Explanation | Software detected the use of an invalid feature enumeration, which may be the result of incompatible software versions on different system components. |
Recommended Action | LOG_STD_ACTION |
%MX-3-BADMAGIC : [chars]: [hex] in [hex], MSGDEF_LIMIT_MEDIUM | |
---|---|
Explanation | A data structure inconsistency was detected in a buffer header, perhaps as the result of memory corruption. A buffer has been dropped because of this, resulting in a memory leak and potential system unreliability. |
Recommended Action | Please report the problem Cisco technical support, along with the text of the error message. If the system becomes unstable, restarting or reloading the affected component should correct the instability. |
%MX-3-SUBRGNINDX : [chars]: Subregion Index allocation failure | |
---|---|
Explanation | Unable to obtain a sub region index so unable add sw managed memory |
Recommended Action | LOG_STD_ACTION |
NAT
%NAT-3-ALLOC_FAIL : data [hex], MSGDEF_LIMIT_GLACIAL | |
---|---|
Explanation | A request exceeded for memory allocation failed |
Recommended Action | LOG_STD_ACTION |
%NAT-3-RMAP_OP_FAIL : Routemap hash table not set up (attempted [chars]), MSGDEF_LIMIT_MEDIUM | |
---|---|
Explanation | An operation was attempted on the route map hash table, but the hash table hash not yet been initialized. |
Recommended Action | LOG_STD_ACTION |
%NAT-3-MAPPING_REFCNT_FAIL : refcount [dec], MSGDEF_LIMIT_MEDIUM | |
---|---|
Explanation | The mapping reference count is below zero. This indicates that the reference count incrementing and decrementing operations are out of sync |
Recommended Action | LOG_STD_ACTION |
%NAT-3-DYN_PAT_MAP_UPD_OR_ADD_FAIL : rc [dec], MSGDEF_LIMIT_MEDIUM | |
---|---|
Explanation | The add or update of a dynamic pat mapping failed with the assoicated return code. This will generally mean that the IOS configuration is now out of sync with the data plane. The mapping should be removed from the configuration to try to get things back in sync. |
Recommended Action | LOG_STD_ACTION |
%NAT-3-EMPTY_CHUNK : id [int], MSGDEF_LIMIT_MEDIUM | |
---|---|
Explanation | The memory provided by the client to the datapath initilization is NULL |
Recommended Action | LOG_STD_ACTION |
%NAT-3-CHUNK_ID_MISMATCH : id [int] not found, MSGDEF_LIMIT_MEDIUM | |
---|---|
Explanation | The chunk ID provided by the client doesn't match any of the available chunk IDs. Hence a valid chunk could not be found for the given chunk ID. |
Recommended Action | LOG_STD_ACTION |
%NAT-3-HA_NO_BUF : , MSGDEF_LIMIT_MEDIUM | |
---|---|
Explanation | There was not enough memory to send the HA record |
Recommended Action | LOG_STD_ACTION |
%NAT-3-HA_BULK_SYNC_FAIL : flags [hex] rg [dec], MSGDEF_LIMIT_MEDIUM | |
---|---|
Explanation | There was a failure such that NAT Bulk Sync did not occur |
Recommended Action | LOG_STD_ACTION |
%NAT-3-HA_COULD_NOT_FIND_SESS : in_orig adr [hex] port [hex] out_trans adr [hex] port [hex] vrf [hex] prot [hex] cook [hex] [hex], MSGDEF_LIMIT_MEDIUM | |
---|---|
Explanation | Standby could not find the session indicated by the HA message |
Recommended Action | LOG_STD_ACTION |
%NAT-3-HA_COULD_NOT_FIND_MATCHING_SESS : values (msg/sess): in_orig adr ([hex]/[hex]) port ([hex]/[hex]) out_trans adr ([hex]/[hex]) port ([hex].[hex]), MSGDEF_LIMIT_MEDIUM | |
---|---|
Explanation | Standby could not find the matching session indicated by the HA message |
Recommended Action | LOG_STD_ACTION |
%NAT-3-HA_STANDBY_CLR_DB_FAILED : rc=[dec], MSGDEF_LIMIT_MEDIUM | |
---|---|
Explanation | Standby failed trying to clear databased with indicated return code |
Recommended Action | LOG_STD_ACTION |
%NAT-3-HA_COULD_NOT_CREATE_SESS : in_orig adr [hex] port [hex] out_trans adr [hex] port [hex] vrf [hex] prot [hex] cook [int] rg [dec], MSGDEF_LIMIT_MEDIUM | |
---|---|
Explanation | Standby could not create the session indicated by the HA message |
Recommended Action | LOG_STD_ACTION |
%NAT-3-HA_COULD_NOT_LOCK_PARENT : in_orig adr [hex] port [hex] out_trans adr [hex] port [hex] vrf [hex] prot [hex] cook [int], MSGDEF_LIMIT_MEDIUM | |
---|---|
Explanation | Standby could not lock parent of the session; thus session not created |
Recommended Action | LOG_STD_ACTION |
%NAT-3-HA_COULD_NOT_CREATE_BIND : idomain [dec] orig adr [hex] port [hex] trans adr [hex] port [hex] vrf [hex] prot [hex] rg [dec], MSGDEF_LIMIT_MEDIUM | |
---|---|
Explanation | Standby could not create the bind indicated by the HA message |
Recommended Action | LOG_STD_ACTION |
%NAT-3-HA_INVALID_MSG_RCVD : invalid value [dec] opcode [hex] version [hex], MSGDEF_LIMIT_MEDIUM | |
---|---|
Explanation | Standby received an invalid NAT HA message |
Recommended Action | LOG_STD_ACTION |
%NAT-4-HA_INVALID_MSGVER_RCVD : invalid version [dec], MSGDEF_LIMIT_GLACIAL | |
---|---|
Explanation | Standby received an invalid NAT HA message |
Recommended Action | LOG_STD_ACTION |
%NAT-3-HA_INVALID_STATE : state [dec], MSGDEF_LIMIT_MEDIUM | |
---|---|
Explanation | An invalid HA state was received from the HA infrastructure. |
Recommended Action | LOG_STD_ACTION |
%NAT-3-HA_COULD_NOT_ALLOC_ADDR : addr %Ci port [hex], MSGDEF_LIMIT_MEDIUM | |
---|---|
Explanation | The standby NAT could not allocate the address requested by the active |
Recommended Action | LOG_STD_ACTION |
%NAT-3-HA_COULD_NOT_FIND_POOL : pool_id [dec], MSGDEF_LIMIT_MEDIUM | |
---|---|
Explanation | The standby NAT could find the pool indicated by the active |
Recommended Action | LOG_STD_ACTION |
%NAT-3-HSL_ALLOC_FAIL : [chars], MSGDEF_LIMIT_MEDIUM | |
---|---|
Explanation | High Speed logging memory allocation failed. When this happens the event will not be exported to the collector. This indicates a temporary condition when the system runs low on memory. The failure does not have any effects on the operation of NAT |
Recommended Action | LOG_STD_ACTION |
%NAT-6-LOG_TRANSLATION : [chars] Translation [chars] %Ci:[dec] %Ci:[dec] %Ci:[dec] %Ci:[dec] [dec] | |
---|---|
Explanation | A translation was created as a result of either a configuration or traffic flowing through the NAT subsystem |
Recommended Action | This message is for debugging purposes only and gets logged only when logging is turned on |
%NAT-3-STATIC_MAP_ADD_FAIL : local addr %Ci global addr %Ci [chars], MSGDEF_LIMIT_MEDIUM | |
---|---|
Explanation | An add of a static NAT mapping failed due to listed reason. This mapping will be in the IOS configuration, but is not active in the data plane. It is recommended to remove the mapping from the configuration |
Recommended Action | LOG_STD_ACTION |
%NAT-4-DEFAULT_MAX_ENTRIES : default maximum entries value [dec] exceeded; frame dropped, MSGDEF_LIMIT_MEDIUM | |
---|---|
Explanation | This is an information message which occurs when NAT is configured and a frame is dropped due to the default maximum entries limit. Starting with release 5, XNE, NAT will use a default max-entries in the data plane based on the ESP type. This will not show in the configuration and is overriden by any user configuration of 'ip nat trans max-entries <value>'. The purpose of the default data plane limit is to protect the box from memory exhaustion which could occur if no limit is enforced. |
Recommended Action |
%NAT-6-ADDR_ALLOC_FAILURE : Address allocation failed; pool [dec] may be exhausted [[dec]], MSGDEF_LIMIT_MEDIUM | |
---|---|
Explanation | This message indicates that an address could not be allocated from a pool because there were no free addresses in the pool at that time. |
Recommended Action |
%NAT-6-POOL_WATERMARK_HIGH : [chars] High watermark reached for pool [dec], MSGDEF_LIMIT_FAST/100 | |
---|---|
Explanation | This message indicates that pool usage has crossed its high watermark. Pool may exhaust soon. |
Recommended Action |
%NAT-6-CLEAR_FAIL_TRANS_IN_USE : , MSGDEF_LIMIT_MEDIUM | |
---|---|
Explanation | The requested clear failed because the transaction was in use. Some clear commands support a 'forced' keyword which allows you to override this. |
Recommended Action | LOG_STD_ACTION |
%NAT-3-PER_VFR_HSL_ADD_FAILED : , MSGDEF_LIMIT_MEDIUM | |
---|---|
Explanation | The attempt to turn on NAT HSL for a vrfid %d failed. Please remove configuration and try again. |
Recommended Action | LOG_STD_ACTION |
%NAT-3-POOL_ADD_FAIL : pool-id [dec] rc [dec], MSGDEF_LIMIT_MEDIUM | |
---|---|
Explanation | A request to the data plane to add or update a pool has failed To clean up remove pool configuration and try re-adding it |
Recommended Action | LOG_STD_ACTION |
%NAT-3-HA_COULD_NOT_CLR : Standby temporarily unable to process clear; please retry, MSGDEF_LIMIT_MEDIUM | |
---|---|
Explanation | A request from the active to process a clear translation failed. Please retry. |
Recommended Action | LOG_STD_ACTION |
%NAT-3-SHOW_TRANS_FAIL : unable to show [dec] entries from bucket [int], MSGDEF_LIMIT_MEDIUM | |
---|---|
Explanation | Unable to show some entries from session database. If using verbose, try using non-verbose. Otherwise situation is likely to be temporary. Or it may be wise to do 'clear ip nat trans *' as a very odd session distribution has occurred. |
Recommended Action | LOG_STD_ACTION |
%NAT-3-SHOW_LIMIT_FAIL : unable to show [int] entries from bucket [int], MSGDEF_LIMIT_MEDIUM | |
---|---|
Explanation | Unable to show some entries from limit database. The situation is likely to be temporary. Or it may be wise to do 'clear ip nat trans *' as a very odd limit entry distribution has occurred. |
Recommended Action | LOG_STD_ACTION |
%NAT-4-SHOW_BIND_NOT_COMPLETE : Unable to show all of NAT binds due to internal error; try again, MSGDEF_LIMIT_MEDIUM | |
---|---|
Explanation | This is an information message which occurs when NAT is unable to show all address binds due to an internal error. Please try operation again. |
Recommended Action |
%NAT-3-STATIC_MAP_ADD_FAILED : local addr %Ci global addr %Ci [chars], MSGDEF_LIMIT_MEDIUM | |
---|---|
Explanation | An add of a static NAT mapping failed due to listed reason. This mapping will be in the IOS configuration, but is not active in the data plane. It is recommended to remove the mapping from the configuration |
Recommended Action | LOG_STD_ACTION |
%NAT-3-DYN_MAP_ADD_FAIL : [chars], MSGDEF_LIMIT_MEDIUM | |
---|---|
Explanation | The add of a dynamic mapping failed. This will generally mean that the IOS configuration is now out of sync with the data plane. The mapping should be removed and then re-added to try to get things back in sync. |
Recommended Action | LOG_STD_ACTION |
%NAT-4-FORCED_DEL_BIND_FAILED : Unable to find bind to forcibly delete, MSGDEF_LIMIT_MEDIUM | |
---|---|
Explanation | This is an information message which occurs when NAT is unable to find a bind even though IOS thinks the bind exists. Please try other methods of clearing transaction. |
Recommended Action |
%NAT-3-DP_REL_FAIL : DP REL FAIL, retry count [dec] exceeded max, MSGDEF_LIMIT_MEDIUM | |
---|---|
Explanation | The dp release fail due to too many retry on freeing session chunk |
Recommended Action | LOG_STD_ACTION |
%NAT-4-SEQ_DELTA_LIST_CORRUPT : Sequence Delta list tail pointer null in error, MSGDEF_LIMIT_MEDIUM | |
---|---|
Explanation | For unknown reasons, sequence delta list tail pointer is null |
Recommended Action | LOG_STD_ACTION |