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 what to look at first when doing a migration and the Admin UI on the new servers will not load, and how to resolve this.
Scope
FortiNAC-F v7.2, v7.4
Solution
The only required files are the /bsc/campusMgr/bin/.networkconfig file and the created backup from the migration script.(eg. /centos-backup-2024_0 5_23_11_46_00.zip).
Once the migration has been completed per the migration guide: Cutover to New Appliances after the execute restore legacy-migrate local step has been completed, the server will reboot.
Once the server has fully rebooted, and started all services, an attempt to open the admin UI may result in a connection refused error.
Verify the .networkconfig file and the /etc/hosts files after executing the enter-shell.
what has been seen is that the IP is the same for primary and secondary servers in the .networkconfig files. This also causes the host file to be wrong.
The quickest way to resolve this is to manually copy the .network file from the centos-backup that was copied over to the system location.
shutdownNAC
shutdownNAC -kill
unzip the file which will recreate the file structure.
Once the previous steps are completed, the Primary server should be able to be accessed via Admin UI without any errors. Completing the migration on the secondary should be ok from here.
