Bug ID 456508: CGNAT: Deleting persistence entries via iRules LSN::persistence-entry delete might not complete remove persistence entry in PBA mode

Last Modified: Oct 17, 2023

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

Known Affected Versions:
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.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2, 12.1.0, 12.1.1, 12.1.2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1

Opened: Apr 09, 2014

Severity: 4-Minor

Symptoms

Deleting persistence entries using iRules in Port block allocation (PBA) mode does not completely remove persistence. This occurs because having a PBA block implies that some persistence exists.

Impact

Using lsndb to view persistence entries may cause confusion as the deleted persistence entries might still be present. These persistence entries go away when they timeout.

Conditions

This occurs when the following conditions are met: -- LSN mode equals PBA. -- iRules use LSN::persistence-entry to create and delete address persistence entries

Workaround

None.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips