FortiNAC-F is a zero-trust network access solution that provides users with enhanced visibility into the Internet of Things (IoT) devices on their enterprise networks. For legacy FortiNAC articles prior to FortiNAC-F 7.2, see FortiNAC.
This article describes how to resolve DB replication issues after migrating to v7.4 FortiNACOS from CentOS.
Scope
FortiNAC-F v7.4.
Solution
After migration is completed, testing DB replication can be performed by first checking the slave status in CLI.
From CLI and execute enter-shell:
====================================== dc000vpfn01:/var/lib/mysql$ sudo hsIsSlaveActive Host dc900vpfn01 SQL version 10.7.8-MariaDB, slave is inactive <---indicates trouble with replication ======================================
Also, event logs in the admin UI will likely show db replication errors if that event is enabled.
Another clue would be the absence of the file /bsc/.my-bsiadmin.cnf which gets created when the HA configuration is done. This file should exist on both systems.
Another clue is the database table files in the /var/lib/mysql/bsc/ directory will not be currently looking at time/date stamps.
If this is the case, reapply the HA configuration under System -> Settings -> System Management -> High Availability.
