Bug ID 2227657: In DSSM, the timestamp for DP1 is changed when all the three DSSM containers are restarted

Last Modified: Jul 28, 2026

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

Known Affected Versions:
2.2.1, 2.2.2, 2.2.3

Opened: Feb 23, 2026

Severity: 2-Critical

Symptoms

Restarting all three DSSM containers with pkill -15 causes new data to be lost; when the DSSM pods come back up, Redis loads the old data from the RDB file.

Impact

The new data that are not saved in the RDB file maybe lost.

Conditions

All the DSSM pods are restarted at the same time.

Workaround

When deploying or upgrading the DSSM Helm chart, the administrator should set aof_enabled to true in the DSSM override file. db: aof_enabled: "true"

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips