We experienced an outage which was later discovered as a result of xlate table entry containing a dynamic NAT for a given IP.
I've perform additional research and found that NAT table contains additional 3-4 other entries with similar cases as I've provided below. In my samples, both hosts belong to a remote site which are reachable via an IPSEC tunnel.
NAT from inside:10.5.22.45 to inside:10.5.22.45 flags iI
NAT from inside:126.96.36.199 to inside:188.8.131.52 flags iI
Upoin issuing "clear xlate global 10.5.22.45", the problem get's resolved immidiately but the root-cause hasn't been determined yet.
On the FW, I'm enforcing NAT control therefore the NAT-0 ACLs include entries to prevent the FW from translating the traffic.
I also have ACLs built for the above IPs as part of the crypto-map.
I am hoping someone could shed some light on what could be causing the FW to built a dynamic NAT rules?
Could it be a configuration or routing issue on the FW?
Cisco Adaptive Security Appliance Software Version 8.0(4)43