Fortinet Document Library

Version:

Version:


Table of Contents

Administration Guide

Download PDF
Copy Link

Startup

Primary server startup

  1. The management process starts up.
  2. The condition of the secondary server is checked.
  3. If the secondary is in control, the secondary retains control until a manual recovery is performed to return control to the primary server. See Recovery.
  4. If the secondary is not in control, the startup of the primary continues and the primary is in control.

If any of the following processes does not start, the appliance is not in control: httpd, dhcpd, named, mysqld, sshd, TomcatAdmin and TomcatPortal. If any of these processes fail, then failover from primary to secondary is started.

Secondary server startup

  1. The management process starts up.
  2. The condition of the primary server is checked.
  3. If the primary is in control, database replication is started on the FortiNAC Server, FortiNAC Control Server, or FortiNAC Control Manager. Other processes are not started on the secondary.
  4. If the primary is not in control and the secondary is not idle then the startup of the secondary continues.
  5. The secondary remains in control until you manually perform the recovery that returns control to the primary server.

Management process

The Management process starts when the appliance is booted up or by running the following command: startupCampusMgr

If the appliance is in control the appropriate processes are started.

If any of the following processes does not start, the appliance is not in control: httpd, dhcpd, named, mysqld, sshd, TomcatAdmin and TomcatPortal. If any of these processes fail, then failover from primary to secondary is started.

Startup

Primary server startup

  1. The management process starts up.
  2. The condition of the secondary server is checked.
  3. If the secondary is in control, the secondary retains control until a manual recovery is performed to return control to the primary server. See Recovery.
  4. If the secondary is not in control, the startup of the primary continues and the primary is in control.

If any of the following processes does not start, the appliance is not in control: httpd, dhcpd, named, mysqld, sshd, TomcatAdmin and TomcatPortal. If any of these processes fail, then failover from primary to secondary is started.

Secondary server startup

  1. The management process starts up.
  2. The condition of the primary server is checked.
  3. If the primary is in control, database replication is started on the FortiNAC Server, FortiNAC Control Server, or FortiNAC Control Manager. Other processes are not started on the secondary.
  4. If the primary is not in control and the secondary is not idle then the startup of the secondary continues.
  5. The secondary remains in control until you manually perform the recovery that returns control to the primary server.

Management process

The Management process starts when the appliance is booted up or by running the following command: startupCampusMgr

If the appliance is in control the appropriate processes are started.

If any of the following processes does not start, the appliance is not in control: httpd, dhcpd, named, mysqld, sshd, TomcatAdmin and TomcatPortal. If any of these processes fail, then failover from primary to secondary is started.