Last Modified: Jul 28, 2026
Affected Product(s):
BIG-IP APM
Fixed In:
21.0.0.3, 17.5.1.8
Opened: Apr 14, 2026 Severity: 2-Critical
Local database users created on the Active device are not synchronized to the Standby device in a High Availability setup. Only the local database instances are synced, but the users within those instances are not visible on the Standby device
Authentication failures may occur during failover scenarios as user credentials exist only on the Active device and are not available on the Standby device. This can result in service disruption during device transitions.
- High Availability (HA) setup with Active-Standby configuration - Local database instances configured with users - Issue occurs after failover or reboot events - Affects both Virtual Edition (VE) and Hardware platforms
Restart the localdbmgr process using: bigstart restart localdbmgr
An issue has been resolved where local database users created on the Active device were not being synchronized to the Standby device in High Availability (HA) setups. The synchronization mechanism has been improved to ensure that both local database instances and their associated users are accurately replicated to the standby devices during HA operations, including failover, reboot, and device role transitions This fix also resolves related issues where users created via the GUI would disappear after approximately one hour, and deleted user accounts would remain in the database