Bug ID 2150489: Most DB keys encrypted by SecureVault master key are not persisted to BigDB.dat when the system master key is changed.

Last Modified: Dec 19, 2025

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

Known Affected Versions:
15.1.9, 15.1.9.1, 15.1.10, 15.1.10.2, 15.1.10.3, 15.1.10.4, 15.1.10.5, 15.1.10.6, 15.1.10.7, 15.1.10.8, 16.1.6, 16.1.6.1, 17.5.0, 17.5.1, 17.5.1.2, 17.5.1.3, 21.0.0

Opened: Nov 10, 2025

Severity: 3-Major

Symptoms

After restarting mcpd, mcpd is stuck in a restart loop.

Impact

BIG-IP is in inoperative state , MCPD in a restart loop

Conditions

-- You set a DB variable that's encrypted ( proxy.password, configsync.password) -- Change the SecureVault master key and save the configuration

Workaround

If a system is affected by this issue, set the DB key back to its default value. Once the configuration is loaded, set the DB key back to the correct value: - tmsh modify /sys db config.auditing.forward.sharedsecret value '<null>' After changing the SecureValue master key but before encountering the issue, run the following command to update the value of the DB key on-disk: setdb config.auditing.forward.sharedsecret "$(getdb config.auditing.forward.sharedsecret)"

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips