Fortinet black logo

Session-Aware Load Balancing Cluster Guide

Selecting the primary FortiController (and the primary chassis)

5.2.10
Copy Link
Copy Doc ID 31a89d05-200d-11e9-b6f6-f8bc1258b856:661628
Download PDF

Selecting the primary FortiController (and the primary chassis)

In a single chassis cluster the FortiController with the longest up time becomes the primary unit (also called the master). If you start configuring the cluster by configuring the FortiController in chassis slot 1 first, this FortiController would typically be the primary unit when the cluster is first up and running. If the FortiController in chassis slot 1 is restarted, its uptime is lower so the FortiController in chassis slot 2 becomes the primary unit.

If the FortiControllers all have the same up time, the FortiController with the lowest serial number becomes the primary unit.

In a two chassis cluster, the FortiController with the highest uptime also becomes the primary FortiController, also making the chassis it is in the primary chassis.

The other factor that contributes to selecting the primary chassis is comparing the number of active workers. The chassis with the most active workers becomes the primary chassis and the primary FortiController in that chassis becomes the primary FortiController for the cluster.

The primary FortiController is the one you log into when you connect to the FortiController management IP address. Configuration changes made to this FortiController are synchronized to the other FortiController(s) in the cluster.

You can change the HA Device Priority of individual FortiControllers. The FortiController with the highest device priority becomes the primary unit. The device priority is not synchronized among all FortiControllers in the cluster so if you want one FortiController to become the primary unit you can set its device priority higher.

Just changing the device priority will not cause the cluster to select a new primary unit. The FortiController with the highest device priority will become the primary unit the next time the cluster negotiates to select a new primary FortiController. You can force the cluster to renegotiate by selecting the Enable Override configuration option. This will cause the cluster to re-negotiate more often. The Enable Override setting is synchronized to all FortiControllers in a cluster.

If it doesn’t matter which FortiController becomes the primary unit there is no need to adjust device priorities or select Enable Override. Selecting Enable Override can cause the cluster to negotiate more often, potentially disrupting traffic.

Selecting the primary FortiController (and the primary chassis)

In a single chassis cluster the FortiController with the longest up time becomes the primary unit (also called the master). If you start configuring the cluster by configuring the FortiController in chassis slot 1 first, this FortiController would typically be the primary unit when the cluster is first up and running. If the FortiController in chassis slot 1 is restarted, its uptime is lower so the FortiController in chassis slot 2 becomes the primary unit.

If the FortiControllers all have the same up time, the FortiController with the lowest serial number becomes the primary unit.

In a two chassis cluster, the FortiController with the highest uptime also becomes the primary FortiController, also making the chassis it is in the primary chassis.

The other factor that contributes to selecting the primary chassis is comparing the number of active workers. The chassis with the most active workers becomes the primary chassis and the primary FortiController in that chassis becomes the primary FortiController for the cluster.

The primary FortiController is the one you log into when you connect to the FortiController management IP address. Configuration changes made to this FortiController are synchronized to the other FortiController(s) in the cluster.

You can change the HA Device Priority of individual FortiControllers. The FortiController with the highest device priority becomes the primary unit. The device priority is not synchronized among all FortiControllers in the cluster so if you want one FortiController to become the primary unit you can set its device priority higher.

Just changing the device priority will not cause the cluster to select a new primary unit. The FortiController with the highest device priority will become the primary unit the next time the cluster negotiates to select a new primary FortiController. You can force the cluster to renegotiate by selecting the Enable Override configuration option. This will cause the cluster to re-negotiate more often. The Enable Override setting is synchronized to all FortiControllers in a cluster.

If it doesn’t matter which FortiController becomes the primary unit there is no need to adjust device priorities or select Enable Override. Selecting Enable Override can cause the cluster to negotiate more often, potentially disrupting traffic.