Description
The following steps restart the NAC processes in a High Availability (HA) Environment. Note the following:
- 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.
Scope
Solution
1) SSH as root to the Primary Control Server or Primary Control/Application Server.
2) Shut down the processes. Enter the following command:
shutdownNAC
3) Enter the following command:
jps --->(use the jps command until you no longer see any 'Yams' process running, this could take 5 - 20 seconds)
4) Shut down the control process. Enter the following command:
shutdownNAC -kill
5) If this is a Control/Application Server then proceed to step 10. If the Control & Application Servers are separate appliances, SSH as root to the Primary Application Server and continue to step 6.
6) Shut down the processes. Enter the following command:
shutdownNAC
7) Enter the following command:
jps
(use the jps command to validate there are no 'Yams' process running)
8) Shut down the control process. Enter the following command:
shutdownNAC -kill
9) SSH as root to the Primary Control Server.
10) 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.
Related Articles
Technical Note: Reboot Control and Application Servers Configured for High Availability
Technical Note: How to restart processes via CLI
