Troubleshooting Tip: FortiNAC Control Server/Application Server HA Pair restart without causing failover

Description
This article describes how to troubleshoot the fact that a FortiNAC running on HA (Control Server/Application Server Pair), which requires a reboot for maintenance, does not perform a failover.

Solution
Important: For L2 HA configurations, do not use the Virtual IP

To stop all processes, execute the following commands via CLI:

1) SSH as root to the Primary Control Server and type:

shutdownCampusMgr

2) Type:

jps

(use the jps command until no "Yams" process is running, this could take 5 - 20 seconds)

3) Type

shutdownCampusMgr -kill

4) SSH as root to the Primary Application Server and type:

jps

(use the jps command to validate there is no "Yams" process running.)

5) Type:

shutdownCampusMgr -kill

6) Repeat steps 1-5 for Secondary Control and Application Servers

Now follow these steps to reboot the appliances:

1) In Primary Application Server CLI type:

reboot

2) Wait 30 seconds

3) In the Primary Control Server CLI type:

reboot

4) Wait until the Primary Control Server is up and running (by confirming that SSH access and Admin UI access are possible)

Note: It may take about 5 to 10 minutes to start. It is advisable to wait that long before attempting to access the Administrative UI.

5) In Secondary Application Server CLI type:

reboot

6) Wait 30 seconds

7) In the Secondary Control Server CLI type:

reboot

After 4-5 minutes, confirm that the Admin UI dashboard shows all servers up.