Bug ID 430114: The lsndb command may not delete all entries

Last Modified: Apr 10, 2019

Bug Tracker

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

Known Affected Versions:
11.2.1, 11.4.0

Fixed In:
11.5.0

Opened: Sep 09, 2013
Severity: 2-Critical
Related AskF5 Article:
K17337

Symptoms

On chassis with backplanes, the lsndb delete command may fail to delete all entries when large numbers of entries exist. Testing found this number to be around 500,000+ entries. This does not cause functional problems for the system, but the delete command may not delete all entries as expected.

Impact

When the conditions are met, and the lsndb delete command is used, it is possible for the lsndb delete command to return without deleting all of the entries in the LSN database. This may cause entries to still exist in the database when the issuer of the command is lead to believe they have all be removed.

Conditions

This issue can be hit on a chassis with a backplane, that has a CGNAT configuration, and enough traffic to cause somewhere in neighborhood of 500,000 entries in LSN database.

Workaround

Run the lsndb delete command multiple times until all entries are removed. The lsndb list command will correctly list all of entries in the database, so the delete can be verified by issuing the lsndb list command afterwards.

Fix Information

The lsndb delete command has been update to work correctly on chassis based systems by using a second connection for sending the delete requests.

Behavior Change