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

Last Modified: Jan 30, 2023

Bug Tracker

Affected Product:  See more info
BIG-IP AFM(all modules)

Known Affected Versions:
15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 16.0.0, 16.0.0.1, 16.0.1, 16.0.1.1, 16.0.1.2, 16.1.0, 16.1.1, 16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3

Fixed In:
17.0.0

Opened: Jun 07, 2021
Severity: 3-Major

Symptoms

Two pools are configured, for example: A: any destination B: destination 8.8.8.8 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.

Impact

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

Conditions

Multiple rules are defined to configure PBA.

Workaround

None

Fix Information

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

Behavior Change