Description | This article describes the behavior when changing the configuration on the Secondary unit of the HA Cluster. |
Scope | FortiGate. |
Solution |
Two FortiGates can provide redundancy by configuring the units within the same HA Cluster. One will become the Primary unit and the other is the Secondary unit.
In a general scenario, configuration change can only be done on the Primary unit. For the FortiGate HA cluster, there is no such restriction.
Configuration change can be done on the Secondary unit, and it will sync up to the Primary unit.
Configuration change on Secondary unit:
FGT-02 # 2024-12-08 19:25:18 <hatalk> vcluster_1: ha_prio=1(secondary), state/chg_time/now=3(standby)/1733714416/1733714718 2024-12-09 10:25:48 0: config system interface 2024-12-09 10:25:48 0: end 2024-12-09 10:25:48 0: end
At the same time, the change gets reflected in the Primary unit:
FGT-01 # 2024-12-09 10:25:07 <hatalk> vcluster_1: ha_prio=0(primary), state/chg_time/now=2(work)/1733714394/1733714707
FGT-01 # sh sys int port3
Important Note: To make sure of the consistency in configuration, it is highly recommended to always make a configuration change on the Primary unit. Making any changes from the Secondary unit may cause some unpredictable issues, even though it is technically possible. |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.