Set up Main Host HA in stacked FortiAnalyzer-BigData 4500F chassis

High Availability (HA) can be configured on the Main Hosts of stacked FortiAnalyzer-BigData 4500F chassis, ensuring system resilience by allowing for failover in the event of a Main Host failure. For more details, refer to FortiAnalyzer Administration Guide.

Backup your configuration before proceeding to the next steps. For steps to backup configuration, see the FortiAnalyzer Upgrade Guide.

To configure a Main Host HA cluster, go to System Settings > HA and configure the settings or change the cluster configuration. The configuration must be performed in the Main Hosts of the main and each extender chassis. The Main Host IP address must be set up for both the main and extender chassis to access the GUI and CLI.

There are two sections in System Settings > HA:

• Cluster Status: use this panel to monitor the Main Host HA cluster status.

• Cluster Settings: use this panel to create or change the Main Host HA cluster configuration. For more information, see Cluster Settings options.

To set up Main Host HA in stacked FortiAnalyzer-BigData 4500F chassis:

1. Configure the Primary host for the Main Host HA cluster.

   1. Connect to the GUI for the Main Host of the main chassis.

   2. Go to System Settings > HA.

   3. Configure the fields in Cluster Settings according to the descriptions in Cluster Settings options.

   4. Click Apply to save.

2. Configure the Secondary host(s) for the Main Host HA cluster.

   1. Connect to the GUI for the Main Host of each extender chassis.

   2. Go to System Settings > HA.

   3. Configure the fields in Cluster Settings according to the descriptions in Cluster Settings options.

   4. Click Apply to save.

3. Monitor the Cluster Status. Wait for the Configuration Sync of the Secondary Role to be "In-Sync". For example, see the image above.

Cluster Settings options

Cluster Settings
	Operation Mode	Select Active-Passive or Active-Active to configure the Main Host on each chassis for HA. Select Standalone to stop operating in HA mode.
	Preferred Role	Select the preferred role when this host first joins the Main Host HA cluster. If the preferred role is Primary, then this host becomes the primary host if it is configured first in a new Main Host HA cluster. If there is an existing primary host, then this host becomes a secondary host. The default is Secondary so that the host can synchronize with the primary host. A secondary host cannot become a primary host until it is synchronized with the current primary host.
Cluster Virtual IP
	IP Address	The IP address for which the Main Host HA cluster is to provide redundancy.
	Interface	The interface the Main Host HA cluster uses to provide redundancy.
	Action	Click the plus (+) to add another virtual IP. Click the x to remove a virtual IP from the list.
Cluster Settings
	Peer IP	If this is the Primary, type the internal IP address (e.g., 198.18.2.1) of Main Host of the extender chassis. If this is a Secondary, type the internal IP address (e.g., 198.18.1.1) of Main Host of the main chassis.
	Peer SN	Type the serial number of the Main Host for the chassis corresponding to the IP address used in the Peer IP.
	Action	Click the plus (+) to add another Main Host in the cluster. Click the x to remove a Main Host from the cluster.
	Group Name	Type a group name that uniquely identifies the Main Host HA cluster. All members in a cluster must have the same Group Name, Group ID, and Password.
	Group ID	Type a group ID from 1 to 255 that uniquely identifies the Main Host HA cluster.
	Password	A password for the Main Host HA cluster. All members of the Main Host HA cluster must have the same password.
	Heart Beat Interval	The time the primary host waits between sending heartbeat packets, in seconds. The heartbeat interval is also the amount of time that secondary hosts wait before expecting to receive a heartbeat packet from the primary host. By default, the Heart Beat Interval is set to 4.
	Heart Beat Interface	Select the interface used to send heartbeat packets.
	Failover Threshold	The number of seconds that one of the cluster hosts waits to receive HA heartbeat packets from other cluster hosts before assuming that the other cluster hosts have failed. This value corresponds to Heart Beat Interval x 3 and it is automatically updated based on the configured Heart Beat Interval. For example, the failure is detected after 12 seconds with the default settings: Heart Beat Interval: 4 Failover Threshold: 12 The Heart Beat Interval can be increased or decreased to adapt to latency conditions of your network and to detect legitimate failures.
	Priority	The priority or seniority of the secondary host in the cluster.
	Log Data Sync	This option is on by default. It provides real-time log synchronization among the peers in the cluster.