Description
This article describes the Config Wizard configurations that do not synchronize between servers that are member of an HA cluster.
Scope
FortiNAC.
Solution
After running Config Wizard on the Primary Server, the Secondary Server's Config Wizard settings do not reflect the changes. This is expected behavior.
In a High Availability (HA) environment, Config Wizard does not synchronize settings between the Primary and Secondary Servers.
Config Wizard need to be run on both Primary and Secondary Server in System -> Config Wizard:
Config Wizard need to be run on both Primary and Secondary Server in System -> Config Wizard:
The recommended procedure is to make the changes firstly in the primary node and than proceed on the secondary node. After making the changes a reboot is required. After the reboot the control should be changed to the secondary node, more information is shown at the High Availability guide or this section of the guide Perform failover. This method is recommended because the changes can also be tested when the secondary node is in control. This will require a maintenance window at least for 30 minutes.
The second option is to follow the procedure that enables the Admin UI in the secondary node and does not require a failover. This can configured by running the following command in the secondary node CLI:
> systemctl start nac-secondary-admingui
More information about the second method can be found in this article: Technical Tip: Access Secondary Server Configuration Wizard with shared IP (9.4 and greater).
Related articles:
Related articles:
