Dynamic Network Address Translation (NAT) creates entries in the table when a packet crosses from the inside NAT interface to the outside NAT interface, or the other way around. These entries have a default timeout value of 86400 seconds (24 hours), after which they are removed from the table if there is no activity for the duration of the timeout. Static NAT entries never time out and always remain in the table.
When using dynamic NAT, reducing the timeout value may be necessary when the duration of communication between the end-hosts is short, and a small pool of global addresses is used for translating a larger pool of local addresses. This allows the existing NAT entries to expire quickly so that the global addresses can be reused by the local addresses.
To modify the timeout value from the default, issue the ip nat translation timeout seconds | never command from the global configuration mode. If NAT overloading is configured with dynamic translation, you can modify the timeout values on a protocol basis.
Configuring translation timeouts
ip nat translation timeout <seconds>
Dynamic translations time out after a period of non-use. When port translation is not configured, translation entries time out after 24 hours. This time can be adjusted with the above command or the following variations:
ip nat translation udp-timeout <seconds>
ip nat translation dns-timeout <seconds>
ip nat translation tcp-timeout <seconds>
ip nat translation finrst-timeout <seconds>
When port translation is configured, there is finer control over translation entry timeouts, because each entry contains more context about the traffic using it. Non-DNS UDP translations time out after 5 minutes; DNS times out in 1 minute. TCP translations time out after 24 hours, unless a RST or FIN is seen on the stream, in which case it times out in 1 minute.
• Showing active translations
show ip nat translations [ verbose ]
• Showing translation statistics
show ip nat statistics
• Clearing dynamic translations
clear ip nat translation *
Clears all dynamic translations.
clear ip nat translation <global-ip>
Clears a simple translation.
clear ip nat translation <global-ip> <local-ip> <proto> <global-port> <local-port>
Clears a particular dynamic translation.
debug ip nat [ <list> ] [ detailed ]
Hi folks,regarding border nodes types, as per my understanding Internal border: routes are redistributed from VRF routing table to correspondig LISP instanceExternal border: no routes are redistributed from VRF routing table to LISP instances at all....
Does the Cisco Catalyst 9300 & 9500 series have full Layer 3 Routing Capabilities? Reasons why I question are below:Do these terms mean full routing? "routed access" "Layer 3 forwarding" These terms are used in the data sheet and license details....
Currently we are in the process of migrating our legacy 7k/5k/2k environment to VXLAN EVPN. We have our 7k enviornment connected to two border gateways. We are connected at layer 2 (VPC) and layer3 (BGP). We have a desire to move SVI's b...
Has anyone setup VOIP Health for their spoke officesto measure voice quality to calls via Ring Central?Can you share what voip servers you plugged inas being targets of the health monitoring? Anyother issues to consider? https://documentation.meraki....
Hi all, At site A we have a core router and distrubution router Site A - AS number 100 (example)Core router - connected to ISP A with ebgp. Distribution router - we have done ibgp with core router and 103.*.*.1/24 prefix is used at si...