| Description | This article describes the behavior when the FGCP monitor interface is running together with fail-detect on the same interface. |
| Scope |
FortiGate HA FGCP, fail-detect are running on the same interface (port1). |
| Solution |
Additional reference: Fortigate FGCP monitor interface can trigger failover when the monitored interface is down Introduction to the FGCP cluster
Using FortiOS v7.0.X, failover is triggered immediately (<1 second) once the monitored interface goes down:
The fail-detect feature will detect if one interface goes down, then it will trigger corresponding fail-alert interface changes to down Fail-detect reaction time takes around 2 seconds after interface goes down, and 1 second after interface goes up:
Testing scenario:
config system ha set override disable set monitor "port1"
config system interface
Testing result: The fail-detect feature only works on the Primary Firewall. On the secondary firewall, if port1 goes down, the corresponding fail-alert interface (port3) is still up:
HA monitor interface will run the first failover triggered if the primary firewall interface port1 goes down.
Status on FG2 (New Primary/Active) - port1 up, port3 up:
When FG1 port1 still down, bring down FG2 port1:
FG1 becomes primary, and port3 becomes down because fail-detect is working on the primary unit:
|
