I'm finding that xlate entries never timeout, leading to a continual increase in the xlate table (last seen at 14K entries - for only 300 or so clients). We use NAT for most connections, with only a couple of static values, but have a single address put aside for PAT - which is getting hammered. What am I missing?
Yep, clear xlate is a regular entry from command line here, and it does work. It was last run around 4 hours ago, and we're already back up to over 760 xlate values, mainly on the PAT address. I also have documented xlate entries that persist (although idle) well past the theoretical 1 hour 45 min limit set by the conn + xlate timeouts
We started with the defaults, and I've been trying to reduce it down. At the moment, a reboot would not go down well - delivery schedules etc are looming rather heavily. And internal policy prevents me from releasing the config.
However, rather than looking at the symptoms, I've been addressing the cause - it seems that many of our nice new WinXP boxes have been confgured to ask for NTP synchronization from outside of the building, so I've been going round amending this and then run a clear xlate. Things are not getting any worse, so that may be all that is necessary to prevent the overload. This means that the NAT addresses won't be over-stretched for what should be an internal function, leaving space for the real connections to take their place. We ought to have more than enough NAT addresses for the necessary functions (web proxy, SMTP, DNS servers etc).
If this works, the problem won't exist any longer, although I'd like to understand why the slots weren't being released. In any case, thanks for the help and suggestions - if/when the opportunity arises, I will reload with default setting again and see how it goes.
DocumentationCode download linksGoalRequirementLimitationsSupported ISR
and UCS-E ModelSupported ISRG2 and UCS-E Blades:Supported ISR4K and
UCS-E Blades:Step by Step ConfigurationConfigure one of the connectivity
options to access the Cisco IMC from the n...
Firepower Threat Defense (NGFWv) on UCS E-series - Transparent Mode in
HA DocumentationCode download linksGoalRequirementLimitationsSupported
ISR and UCS-E ModelSupported ISRG2 and UCS-E Blades:Supported ISR4K and
UCS-E Blades:Step by Step ConfigurationCo...
Question I am currently unable to specify "crypto keyring" command when
configuring VPN connection on my cisco 2901 router. The following
licenses have been activated on my router :