Bug ID 1779181: Unable to get CGNAT entries from dSSM through MRFDB tool

Last Modified: Nov 29, 2025

Affected Product(s):
BIG_IP_NEXT(CNF) CNF(all modules)

Fixed In:
1.4.0

Opened: Dec 20, 2024

Severity: 3-Major

Symptoms

Unable to get CGNAT entries from dSSM through MRFDB tool.

Impact

Unable to read any CGNAT entries from MRFDB tool.

Conditions

* At least one NAT policy CR is created on the cluster. * Any combination of the following actions are done for around 16 times or more: * TMM is scaled up. * TMM is scaled down. * TMM is restarted. * NAT policy CR field `spec.sourceTranslation.addresses` is updated. * Traffic is sent in large bursts.

Workaround

1. Delete all NAT policy CRs from the cluster. 2. Re-create all NAT policy CRs on the cluster. It is also possible to re-create the NAT policy CRs one-by-one, based on the NAT policy name that shows up in the errors.

Fix Information

MRFDB tool no longer fails to read CGNAT entries after too many modifications by TMM.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips