FortiGate
FortiGate Next Generation Firewall utilizes purpose-built security processors and threat intelligence security services from FortiGuard labs to deliver top-rated protection and high performance, including encrypted traffic.
adecottignies_FTNT
Article Id 365206
Description This article explains how to manually trigger a failover for a FortiGate 6000 cluster.
Scope FortiGate 6000.
Solution

FortiGate-6000 devices support High availability in Active-Passive mode with only two devices.
Depending on the HA configuration, changing the priority or resetting the ha uptime triggers a failover.

To check the current HA configuration through the CLI:

config global
show full-configuration system ha

Priority, override, and monitor are the important elements to look at.


During the primary unit election in the 6000 cluster, if the override is disabled, the following criteria are considered:

Override Disabled: Any Active FPCs -> Connected Monitored Ports -> Number of Active FPCs -> HA uptime -> Priority -> Serial Number.

While the number of connected monitor ports, and Active FPCs are identical, it’s the HA uptime that acts as a tiebreak.

To force a failover, it is necessary to reset the HA uptime on the current primary:


config global
diag sys ha reset-uptime

 

If the override is enabled, the following criteria are considered:


Override Enabled: Any Active FPCs -> Connected Monitored Ports -> Number of Active FPCs -> Priority -> HA uptime -> Serial Number.


To force a failover, it is necessary to change the priority.


config global
config system ha

set priority <priority number>


The unit with the highest priority will become primary.


Related articles:
Technical Tip: Understanding the HA uptime for Chassis based device
Technical Tip: HA Master Election Process on FortiGate-6000/7000 Series