IP Source NAT Exhausted ??

anilperumandlaanilperumandla Member ✭
in ADC - Application Delivery

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


Tagged:

Comments

  • mdunnmdunn Member, A10ers ✭✭✭

    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.

  • anilperumandlaanilperumandla Member ✭

    Thanks @mdunn 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?

  • mdunnmdunn Member, A10ers ✭✭✭

    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.

Sign In or Register to comment.

© Copyright 2024 - A10 Networks Community - All Rights Reserved. | Legal