Select High Availability to configure the FortiAnalyzer unit for HA.

Select Standalone to stop operating in HA mode.

Select the preferred role when this unit first joins the HA cluster.

If the preferred role is Primary, then this unit becomes the primary unit if it is configured first in a new HA cluster. If there is an existing primary unit, then this unit becomes a secondary unit.

The default is Secondary so that the unit can synchronize with the primary unit. A secondary unit cannot become a primary unit until it is synchronized with the current primary unit.

Cluster Virtual IP

The interface the FortiAnalyzer HA unit uses to provide redundancy.

The IP address for which the FortiAnalyzer HA unit is to provide redundancy.

Cluster Settings

Type the IP address of another FortiAnalyzer unit in the cluster.

Type the serial number of the FortiAnalyzer unit corresponding to the entered IP address.

Type a group name that uniquely identifies the FortiAnalyzer HA cluster. All units in a cluster must have the same Group Name, Group ID and Password.

Type a group ID from 1 to 255 that uniquely identifies the FortiAnalyzer HA cluster.

A password for the HA cluster. All members of the HA cluster must have the same password.

The time the primary unit waits between sending heartbeat packets, in seconds. The heartbeat interval is also the amount of time that secondary units waits before expecting to receive a heartbeat packet from the primary unit.

By default, the Heart Beat Interval is set to 1.

The number of heartbeat intervals that one of the cluster units waits to receive HA heartbeat packets from other cluster units before assuming that the other cluster units have failed. The default failover threshold is 3.

In most cases you do not have to change the heartbeat interval or failover threshold. The default settings mean that if the A unit fails, the failure is detected after 3 x 1 or 3 seconds; resulting in a failure detection time of 3 seconds.

If the failure detection time is too short, the HA cluster may detect a failure when none has occurred. For example, if the primary unit is very busy it may not respond to HA heartbeat packets in time. In this situation, the backup unit may assume the primary unit has failed when the primary unit is actually just busy. Increase the failure detection time to prevent the backup unit from detecting a failure when none has occurred.

If the failure detection time is too long, administrators will be delayed in learning that the cluster has failed. In most cases, a relatively long failure detection time will not have a major effect on operations. But if the failure detection time is too long for your network conditions, then you can reduce the heartbeat interval or failover threshold.

In FortiAnalyzer 7.0.6, this setting cannot be configured in the GUI or CLI.

The priority or seniority of the secondary unit in the cluster.