Description
This article describes how to upgrade a FortiNAC CA cluster.
Scope
FortiNAC.
Solution
- Make sure no 'README' file is available in the "find /bsc/campusMgrUpdates/ -name README" directory:
up is an alias that will direct immediately to the campusMgrUpdates directory, and there it is also possible to type 'll' which will display all the files available.
If 'README' file was found, stop the upgrade and contact Fortinet Technical support for assistance.
-
Check the CentOS version if it needs an update before downloading/installing the Firmware.
To download the FortiNAC image from GUI.
Do not forget to run yum update after changing the download protocol.
Download Phase:
To download the FortiNAC version, type the version in the Product Distribution Directory: Version_9_1.
Select 'Download' and select the FortiNAC version to download.
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':
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 FortiNAC.
- 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.
Check the Dashboard after the upgrade, it should look like this:
Verify the Engine Version after the upgrade by running 'sysinfo' on both FortiNAC.
Related articles:
Technical Tip: Upgrade FortiNAC from CLI
Technical Note: How to reboot Control and Application servers via CLI
Technical Note: Reboot Control and Application Servers Configured for High Availability
Technical Tip: Upgrade FortiNAC-F through the CLI
Technical Tip: Upgrade FortiNAC from GUI Failed, Errors occurred during image upgrade. ret='-1'