Fortinet white logo
Fortinet white logo

Step 6: Apply Certificates to Secondary Server

Step 6: Apply Certificates to Secondary Server

UI Method

Note: FortiNAC management processes are stopped twice using this method and may require a maintenance window.

  1. Force a failover to the Secondary Server.

    1. Login to the Secondary Server CLI as root and run the following command:

      hsIsSlaveActive

      Ensure slave is active is returned. If slave is inactive is returned, do not proceed. Contact Support for assistance.

      Example:

      > hsIsSlaveActive

      Host myFortinac

      SQL version 5.6.39,

      slave is active

  2. Run the following commands to start tailing logs in the Secondary Server CLI:

    logs

    tail –F output.processManager | grep –i “Slave In Control”

  3. In a window, login to Primary Server CLI as root and run the following command to stop processes and force failover:

    shutdownNAC -kill

    After roughly 3-5 minutes, the failover should complete. The Secondary Server CLI should return (Slave) Slave In Control Idle(false) in the log.

  4. Login to the Administration UI for the Secondary Server and install certificates using the steps in section Upload the Certificate to FortiNAC.

  5. In a window, login to Primary Server CLI as root and run the following command to
    restart processes in preparation to resume control:

    startupNAC

  6. Restore control to the Primary Server. Click the Resume Control button in the Summary Dashboard panel. This will take several minutes to complete.

Step 6: Apply Certificates to Secondary Server

Step 6: Apply Certificates to Secondary Server

UI Method

Note: FortiNAC management processes are stopped twice using this method and may require a maintenance window.

  1. Force a failover to the Secondary Server.

    1. Login to the Secondary Server CLI as root and run the following command:

      hsIsSlaveActive

      Ensure slave is active is returned. If slave is inactive is returned, do not proceed. Contact Support for assistance.

      Example:

      > hsIsSlaveActive

      Host myFortinac

      SQL version 5.6.39,

      slave is active

  2. Run the following commands to start tailing logs in the Secondary Server CLI:

    logs

    tail –F output.processManager | grep –i “Slave In Control”

  3. In a window, login to Primary Server CLI as root and run the following command to stop processes and force failover:

    shutdownNAC -kill

    After roughly 3-5 minutes, the failover should complete. The Secondary Server CLI should return (Slave) Slave In Control Idle(false) in the log.

  4. Login to the Administration UI for the Secondary Server and install certificates using the steps in section Upload the Certificate to FortiNAC.

  5. In a window, login to Primary Server CLI as root and run the following command to
    restart processes in preparation to resume control:

    startupNAC

  6. Restore control to the Primary Server. Click the Resume Control button in the Summary Dashboard panel. This will take several minutes to complete.