Description |
This article explains a scenario where the user has an HA cluster with interface monitoring to trigger an HA fail-over when a monitored interface link goes down.
The fail-over causes the cluster to renegotiate and re-select the primary unit. However, fail-over is not happening when one of the monitored interfaces goes down:
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 |
1. Check the ha failover status on the secondary unit: failover status: set <----- Need to be disabled.
To disable:
execute ha failover unset 1
It is recommended to ensure that the number of monitoring interfaces down on the Slave device is lower than on the master device to trigger an HA failover.
# get sys ha status HA Health Status: MONDEV stats:
# diag sys ha history read |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.