Bug ID 509108: CGNAT PBA may log port-block allocation and port-block release log messages for a port-block which is already allocated to a different subscriber

Last Modified: Apr 28, 2025

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

Known Affected Versions:
11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5

Fixed In:
12.0.0, 11.6.0 HF6

Opened: Feb 25, 2015

Severity: 2-Critical

Symptoms

CGNAT PBA may log port-block allocation(LSN_PB_ALLOCATED) and immediately followed by a port-block release(LSN_PB_RELEASE) log message for a port-block which is already allocated to a different subscriber.

Impact

Causes ambiguity in reverse mapping subscriber connections

Conditions

This can happen if subscriber traffic is received when blade is being added/removed or when blade is failing or while HA failover is in progress

Workaround

None

Fix Information

CGNAT PBA does not log port-block allocation and port-block release log messages for a port-block which is already allocated to a different subscriber during a blade add/remove/fail/HA failover

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips