Technical Tip: How to restart processes via CLI in High Availability (HA) Environment
Description
This article describes how to restart control processes via CLI in a HA environment.
Scope
FortiNAC.
Solution
The following steps restart the NAC processes in a HA Environment:
- SSH as root to the Primary Control Server or Primary Control/Application Server.
- Shut down the processes. Enter the following command:
shutdownNAC
- Enter the following command:
jps --->(use the jps command until you no longer see any 'Yams' process running, this could take 5 - 20 seconds)
- Shut down the control process. Enter the following command:
shutdownNAC -kill
- If this is a Control/Application Server then proceed to step 10. If the Control & Application Servers are separate appliances, SSH is the root of the Primary Application Server and continues to step 6.
- Shut down the processes. Enter the following command:
shutdownNAC
- Enter the following command:
jps <----- Use the jps command to validate there are no 'Yams' process running.
- Shut down the control process. Enter the following command:
shutdownNAC -kill
- SSH as root to the Primary Control Server.
- Start back up the processes. Enter the following command:
startupNAC
The message 'Master Process is Running' should appear.
Note:
- The startup could take anywhere between roughly 5-10 minutes. Suggest waiting that long before attempting to access the Administrative UI.
- This does not reboot the appliance.
- This does not trigger a failover in a High Availability (HA) environment.
- NAC will not switch VLANs, serve Captive Portal pages or respond to RADIUS requests until processes are back up.
Related articles
Technical Note: Reboot Control and Application Servers Configured for High Availability