Bug ID 494743: Port exhaustion errors on VIPRION 4800 when using CGNAT

Last Modified: Sep 13, 2023

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

Known Affected Versions:
11.5.1 HF1, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.1 HF10, 11.5.1 HF11, 11.5.2 HF1, 11.5.3 HF1, 11.5.3 HF2, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.4.1, 11.5.0, 11.5.1, 11.5.2, 11.5.3, 11.6.0, 11.6.1, 11.6.2, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 12.1.0 HF1, 12.1.0 HF2, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2

Fixed In:
12.0.0, 11.6.0 HF6, 11.5.4

Opened: Dec 05, 2014

Severity: 2-Critical

Related Article: K17389

Symptoms

You may see the following on a VIPRION 4800 platform configured to use LSN deterministic NAT: crit tmm3[12240]: 01010201:2: Inet port exhaustion on ...

Impact

DNAT port exhaustion alert,

Conditions

VIPRION 4800 platform with multiple blades with LSN deterministic NAT

Workaround

Change LSN Pool members for LSN deterministic NAT pools, which will trigger a deterministic NAT data rebuild.

Fix Information

TMM translations after blade failure or startup can be properly reverse-mapped by dnatutil, which fixes the port exhaustion alerts.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips