Bug ID 1023461: Multiple entries for CGNAT when PBA pools allocation is defined: for each request, a new entry is created

Last Modified: Apr 24, 2024

Affected Product(s):
BIG-IP AFM(all modules)

Known Affected Versions:
14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3,, 14.1.4,,,,,,, 14.1.5,,,,,, 15.1.3,, 15.1.4,, 15.1.5,, 15.1.6,, 15.1.7, 15.1.8,,, 16.0.0,, 16.0.1,,, 16.1.0, 16.1.1, 16.1.2,,, 16.1.3,,,,,, 16.1.4,,,

Fixed In:
17.0.0, 15.1.9

Opened: Jun 07, 2021

Severity: 3-Major


Two pools are configured, for example: A: any destination B: destination 1. Making connections and utilizing port block allocation (PBA) pool A works as expected; pools are correctly allocated and released as needed. 2. When a client has active PBA pool A allocated and requests pool B (because of connectivity to specific destination IP), then each subsequent connection request from that client results in new PBA pool B allocation.


If a request does not belong to the first pool then it will not belong any other, so the system creates a new pool.


Multiple rules are defined to configure PBA.



Fix Information

BIG-IP checks all allocated pools first before creating a new pool.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips