Last Modified: Apr 17, 2024
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 13.1.3.5, 13.1.3.6, 13.1.4, 13.1.4.1, 13.1.5, 13.1.5.1, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.0.1.1, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 14.1.3.1, 14.1.4, 14.1.4.1, 14.1.4.2, 14.1.4.3, 14.1.4.4, 14.1.4.5, 14.1.4.6, 14.1.5, 14.1.5.1, 14.1.5.2, 14.1.5.3, 14.1.5.4, 14.1.5.6, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 15.1.8.2, 15.1.9, 15.1.9.1, 15.1.10, 15.1.10.2, 15.1.10.3, 15.1.10.4
Opened: Feb 06, 2019 Severity: 4-Minor
In a high availability (HA) pair set up with gateway failsafe, modifying the gateway failsafe configuration fails to remove the previously configured monitor. Only the unit specified in a pools gateway-failsafe-device parameter should be monitoring the pools members.
At minimum, the impact is confusion and a misleading configuration. There might be other, unexpected results.
HA pair is configured in gateway failsafe mode.
On the unit where the incorrect monitors exist, modify the gateway-failsafe-device to be the local unit and set the min-up-members to 0. Then sync back from the peer (with overwrite) to correct the config. On the 'broken' system (system2): [root@system2:Standby:In Sync] config # tmsh modify ltm pool gateway1 gateway-failsafe-device system2.siterequest.local min-up-members 0 [root@system2:Standby:Changes Pending] config # tmsh show sys ha-status all-properties| egrep '(-----|Status|Feature|Enabled|hardware|pool-mbr)' ------------------------------------------------------------------------------------------------------------------- Sys::HA Status Feature Key Action Fail Feature Take Client Proc Timeout Enabled Act Data (sec) ------------------------------------------------------------------------------------------------------------------- hardware-failover sod go-active no yes no 1 sod 0 pool-mbr-down gateway2 failover no yes no 1 mcpd 0 But the config is now incorrect: [root@system2:Standby:Changes Pending] config # tmsh list ltm pool gateway1 ltm pool gateway1 { gateway-failsafe-device system2.siterequest.local members { 10.2.63.146:any { address 10.2.63.146 session monitor-enabled state up } } min-up-members-checking enabled monitor gateway_icmp } Sync from peer with overwrite: [root@system2:Active:Changes Pending] config # tmsh run cm config-sync to-group dg-sync-fail force-full-load-push Now on system2, all is correct: [root@system2:Standby:Changes Pending] config # tmsh show sys ha-status all-properties| egrep '(-----|Status|Feature|Enabled|hardware|pool-mbr)' ------------------------------------------------------------------------------------------------------------------- Sys::HA Status Feature Key Action Fail Feature Take Client Proc Timeout Enabled Act Data (sec) ------------------------------------------------------------------------------------------------------------------- hardware-failover sod go-active no yes no 1 sod 0 pool-mbr-down gateway2 failover no yes no 1 mcpd 0 [root@system2:Standby:In Sync] config # tmsh list ltm pool gateway1 ltm pool gateway1 { gateway-failsafe-device system2.siterequest.local members { 10.2.63.146:any { address 10.2.63.146 } } min-up-members 1 min-up-members-checking enabled monitor gateway_icmp }
None