Technical Tip: Possible cause of HA monitor interface not triggering HA failover

[amahdi]

Description	This article describes a scenario where the user has an HA cluster with interface monitoring to trigger an HA failover when a monitored interface link goes down. The failover causes the cluster to renegotiate and re-select the primary unit. However, failover is not happening when one of the monitored interfaces goes down: config system ha     set group-name "NAME"     set mode a-p     set password ENC     set hbdev "a" 0 "b" 0     set route-ttl 60     set hb-interval 6     set hello-holddown 30     set session-pickup enable     set session-pickup-connectionless enable     set override enable     set priority 200     set override-wait-time 120     set monitor "internal" "wan2" <----- Failover is not happening when WAN2 is down.
Scope	FortiGate.
Solution	Check the ha failover status on the unit: SDWAN-PRI # execute ha failover status failover status: unset SDWAN-SEC # execute ha failover status failover status: set <----- Unset this. When checking the cluster status with the command 'get system ha status', there will be a failover because the 'EXE_FAIL_ OVER flag set'. get system ha status HA Health Status: OK Model: FortiGate-300E Mode: HA A-P Group: 13 Debug: 0 Cluster Uptime: 30 days 1:11:42 Cluster state change time: 2025-11-11 16:38:43 Master selected using: FGT3Exxxx-----3 is selected as the master because it has EXE_FAIL_ OVER flag set.  << ses_pickup: disable override: enable To disable it: execute ha failover unset 1 In a scenario where the HA-cluster does not initiate a failover when the 'wan2' interface goes down on the primary device, it can be because the number of interfaces down on the secondary device is higher than or equal to the number of interfaces down on the primary device. It is recommended to ensure that the number of monitoring interfaces down on the secondary device is lower than on the primary device to trigger an HA failover. get sys ha status  HA Health Status: WARNING: FG3EXXXX has mondev down; <- Secondary has more number of interface in down state.  MONDEV stats: FGEEXXXX (updated 1 seconds ago): wan2: physical/00, down, rx-bytes/packets/dropped/errors=2589/265879/0/0,  internal: physical/00, down, rx-bytes/packets/dropped/errors=8634/274869/0/0,