# IP Source NAT Exhausted ??

**URL:** <https://community.a10networks.com/t/ip-source-nat-exhausted/789>\
**Category:** ADC - Application Delivery\
**Tags:** snat\
**Created:** [July 25, 2023, 4:53pm UTC](https://community.a10networks.com/t/ip-source-nat-exhausted/789 "2023-07-25T16:53:02Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![anilperumandla](https://avatars.discourse-cdn.com/v4/letter/a/c57346/32.png) [@anilperumandla](https://community.a10networks.com/u/anilperumandla)\
**Post date:** [July 25, 2023, 4:53pm UTC](https://community.a10networks.com/t/ip-source-nat-exhausted/789/1 "2023-07-25T16:53:02Z")

</div>

Is this IP Source NAT pool exhausted ??  
Can some help to resolve this if so ? Is that the only way to increase the pool ??

 ![Source NAT-A10.png](https://us1.discourse-cdn.com/flex002/uploads/a10_community/original/1X/cfe702875eab6ab9dfcc3be994e359c437c74d23.png)

---

<div class="post-metadata">

**Author:** ![mdunn](https://avatars.discourse-cdn.com/v4/letter/m/87869e/32.png) [@mdunn](https://community.a10networks.com/u/mdunn)\
**Post date:** [July 27, 2023, 4:05pm UTC](https://community.a10networks.com/t/ip-source-nat-exhausted/789/2 "2023-07-27T16:05:58Z")

</div>

Yes, failures can indicate that the Pool reached an exhausted state. There should be syslog messages indicating NAT exhaustion as well. If exhaustion is taking place, either we need less connections to NAT, or we need more NAT Addresses available. Traffic types can also influence this, such as long-lived idle connections.

---

<div class="post-metadata">

**Author:** ![anilperumandla](https://avatars.discourse-cdn.com/v4/letter/a/c57346/32.png) [@anilperumandla](https://community.a10networks.com/u/anilperumandla)\
**Post date:** [July 27, 2023, 4:35pm UTC](https://community.a10networks.com/t/ip-source-nat-exhausted/789/3 "2023-07-27T16:35:22Z")

</div>

Thanks for your reply. Surprising part here is we are seeing failure only on first IP Address (.162) and we have range till 165 no one has any failure only I see on 162., not sure why ?  
any thoughts?

---

<div class="post-metadata">

**Author:** ![mdunn](https://avatars.discourse-cdn.com/v4/letter/m/87869e/32.png) [@mdunn](https://community.a10networks.com/u/mdunn)\
**Post date:** [August 29, 2023, 4:01am UTC](https://community.a10networks.com/t/ip-source-nat-exhausted/789/4 "2023-08-29T04:01:27Z")

</div>

The failures are not reported per address in a NAT pool range. It is a single counter for that entire pool. From the CLI, you can use “show ip nat pool statistics” to see port-usage per address, though. Aside from port exhaustion, network connectivity issues on the NAT Outside could manifest as failures.
