Description
This article describes a procedure that reboots appliances in the proper order via CLI. If CLI access is not available, contact support for assistance.
Note the following:
- To reboot using the Administration UI, refer to the Power Management section of the Administration Guide in the Fortinet Document Library.
- Regardless of the method used, the reboot should first be initiated on the Application Server to ensure proper communication between the Control and Application servers when the control processes resume.
- During this process, all management functionality is stopped:
- VLAN switching.
- Captive Portal pages.
- RADIUS processing.
- Registration of endpoints.
Scope
FortiNAC.
Solution
- Stop control processes. On all servers type:
shutdownNAC
- Wait 30 seconds.
- Kill management processes. On all servers type:
shutdownNAC -kill
- Reboot the Application Server. On Application Server type:
reboot
- Wait 30 seconds.
- Reboot the Control Server. On Control Server, type:
reboot
- After 5-10 minutes, confirm that the Admin UI dashboard is accessible.
On FortiNAC-F the above commands needs to be executed on shell using the following command:
execute enter-shell
$shutdownNAC
$shutdownNAC -kill
$reboot
Related documents:
Technical Note: Reboot Control and Application Servers Configured for High Availability
Guide: CLI reference manual
