FortiNAC
NOTE: FortiNAC is now named FortiNAC-F. For post-9.4 articles, see FortiNAC-F. FortiNAC is a zero-trust network access solution that provides users with enhanced visibility into the Internet of Things (IoT) devices on their enterprise networks.
FortiKoala
Staff
Staff
Article Id 196678

Description

 

This article describes the potential triggers for a system to fail over.


Scope


Version: All


Solution

 

A common cause for failovers in a High Availability configuration is a loss of communication between the Primary and Secondary appliances.  This can happen if there's a network traffic interruption (such as a router or switch failure) or the Primary appliance was powered down or rebooted.

A failover can also be triggered if services required for functionality stop running and are unable to be restarted.  If a failover occurs due to a service failure, one or more of the following events may be generated:
Service Down - Tomcat Admin
Service Down - Tomcat Portal
Service Down -dhcpd
Service Down -httpd
Service Down -mysqld
Service Down -named
Service Down -sshd

To help determine what caused a fail over, review the events:
 
1) Version 8.x:  Navigate to Logs - > Events.
    Version 9.x and above: Navigate to Logs - > Events & Alarms.

2) Filter on event System Fail Over to verify the time of the occurrence.

3) Once the time of the fail over has been verified, filter on the date and time to view the events reported just prior to the fail over.
 
Contact Support if additional assistance is needed.
 
For possible triggers to force a failover for testing purposes, see KB article 191519.  
For full configuration and functionality details, see the High Availability reference manual in the Document Library. 
Contributors