ha failover

Use the execute ha failover command group to manually trigger or clear a forced HA failover on a FortiWeb device. This mechanism overrides standard HA election behavior, allowing administrators to shift the current node to standby mode without requiring a failure condition.

This command is intended for controlled scenarios such as testing, troubleshooting, or temporary administrative operations. It is supported only in Active-Passive (AP), Active-Active-Standard (AAS), and Active-Active-High-Volume (AAH) HA modes.

The failover state does not persist across device reboots or HA mode changes. When cleared, the device resumes normal HA primary election based on link status, uptime, priority, and serial number.

Syntax

execute ha failover {set | unset | status}

set	Forces the current node to relinquish the primary role and enter standby.
unset	Clears the manual failover state and returns the node to standard HA election behavior.
status	Displays the current manual failover state of the node.

Operational Behavior

Scope and Availability

• Supported only in HA AP, AAS, or AAH modes.

• Not available in Standalone or Manager modes, including public cloud deployments.

Failover Control and Reset Conditions

• The manual failover state is automatically cleared under the following conditions:

  • The system reboots.

  • The HA mode is changed to Standalone.

HA Election Logic (when failover is cleared)

• The device resumes standard HA election based on:

  • Link status of monitor interfaces

  • HA uptime

  • HA priority

  • Serial number (used as a tie-breaker)

• If override is enabled, HA priority takes precedence.

Command Visibility and Logging

• Failover operations (set and unset) generate entries in the event log.

• The current manual failover state appears in the outputs of:

  • get system status

  • get system ha-status

Cluster Behavior

• If a new node joins a cluster where manual failover is enabled, the original HA election state is preserved.

• After full synchronization, member nodes retain their failover status unless explicitly reconfigured.