Bug ID 1589133: Virtual address status, under certain conditions, is not changed on the Standby device

Last Modified: Mar 12, 2025

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

Known Affected Versions:
17.1.1.3, 17.1.1.4, 17.1.2, 17.1.2.1

Opened: May 23, 2024

Severity: 4-Minor

Symptoms

The Standby device is not sync with the Active unit

Impact

The Standby device does not mark the virtual address as RED (offline).

Conditions

A virtual-address has these following conditions met - 1. Route-advertisement set to 'any' 2. Has a custom name (instead of just the IP itself as a name) 3. Has at least two virtual-servers associated with it (and both virtual servers with pools) 4. All pool members are removed from both pools 5. Auto-sync is enabled (incremental)

Workaround

Workaround #1: Force full sync after an incremental sync is detected: 1. edit /config/user_alert.conf on all HA peers to add the line below: alert trigger_full_sync "Incremental sync complete" { exec command="sleep 30; tmsh run cm config-sync force-full-load-push to-group <failover-group>" } 2. restart the alert daemon using this command to activate the above change: bigstart restart alertd Workaround #2: Do not use a custom name as the virtual-address name. (will not work for AS3 as you need a custom name when using AS3).

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips