Description
This article describes how to upgrade a FortiNAC CA cluster.
Solution
1) Make sure no 'README' file is available in the "find /bsc/campusMgrUpdates/ -name README" directory:
up is an alias that will take you immediately to campusMgrUpdates directory, and there you can also type "ll" which will display all the files available.
If 'README' file was found, stop the upgrade and contact Fortinet Technical support for assistance.
2) Check CentOS version if it needs update before downloading/installing the Firmware.
To download FNAC image from GUI.
Check page 19 to change the download protocol.
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/c5482855-2898-11e9-94bf-005056...
https://fortinetweb.s3.amazonaws.com/docs.fortinet.com/v2/attachments/c5482855-2898-11e9-94bf-005056...
Do not forget to run # yum update after changing the download protocol.
Download Phase:
In order to download the FortiNAC version, type the version in the Product Distribution Directory: Version_9_1.
In order to download the FortiNAC version, type the version in the Product Distribution Directory: Version_9_1.
For the reference check the FortiNAC release notes https://docs.fortinet.com/document/fortinac/9.1.0/release-notes/195805/system-update-settings
Select 'Download' and select the FortiNAC version to download.
Once the download image has been completed, this message will appear in another tab:
Once the download image has been completed, this message will appear in another tab:
Installation Phase
Now select 'Install tab' to select the downloaded version and select 'Update':
Now select 'Install tab' to select the downloaded version and select 'Update':
Note:
Do not close this tab.
- Primary will first start the Engine version installation; once the update is done the installation file will be automatically pushed to secondary for installation. The installation will also start automatically on the Secondary FNAC.
- No need to turn off any processes.
Do not close this tab.
- Primary will first start the Engine version installation; once the update is done the installation file will be automatically pushed to secondary for installation. The installation will also start automatically on the Secondary FNAC.
- No need to turn off any processes.
Note: During firmware upgrade only processes restarted. FortiNAC VM does not reboot.
When Primary finishes the update, the installation automatically starts on the secondary.
When Primary finishes the update, the installation automatically starts on the secondary.
Check the Dashboard after the upgrade, it should look like this:
Verify the Engine Version after the upgrade by running 'sysinfo' on both FortiNAC.
Useful Articles:
https://community.fortinet.com/t5/FortiNAC/Technical-Tip-Upgrade-FortiNAC-from-CLI/ta-p/190662
https://community.fortinet.com/t5/FortiNAC/Technical-Note-How-to-reboot-Control-and-Application-serv...
https://community.fortinet.com/t5/FortiNAC/Technical-Note-Reboot-Control-and-Application-Servers-Con...
