I am running PAT on our core 7609 for all our private IP customers. For some reason I am constantly get a "%IPNAT-4-ADDR_ALLOC_FAILURE: Address allocation failed for 10.192.32.21, pool Inat might be exhausted" error message for one particluar ip. I know I haven't exhausted my NAT/PAT table, and I only seem to get the message on the same IP all the time.
Here is my NAT (PAT) config:
ip nat pool Inat x.x.238.2 x.x.238.6 prefix-length 29
ip nat inside source list 3 pool Inat overload
access-list 3 permit 10.190.0.0 0.0.255.255
access-list 3 permit 10.180.0.0 0.0.255.255
access-list 3 permit 10.189.0.0 0.0.255.255
access-list 3 permit 10.192.0.0 0.0.255.255
access-list 3 permit 10.194.0.0 0.0.255.255
access-list 3 permit 10.2.0.0 0.0.0.255
access-list 3 permit 10.32.0.0 0.0.255.255
access-list 3 permit 10.64.0.0 0.0.255.255
access-list 3 permit 10.128.0.0 0.0.255.255
access-list 3 permit 172.16.1.0 0.0.0.63
ET7609#sho ip nat st
Total active translations: 4638 (1 static, 4637 dynamic; 4634 extended)
Hits: 35298003 Misses: 815345
Expired translations: 814176
-- Inside Source
[Id: 1] access-list 3 pool Inat refcount 4637
pool Inat: netmask 255.255.255.248
start x.x.238.2 end x.x.238.6
type generic, total addresses 5, allocated 4 (80%), misses 280
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...