Fortinet black logo

Control Manager

Monitor high availability

Copy Link
Copy Doc ID c0e495af-7299-11e9-81a4-00505692583a:521115
Download PDF

Monitor high availability

Monitoring current status

These events are not generated for the FortiNAC Control Manager.

The status of your High Availability appliances can be viewed on the Dashboard in a Summary panel.

The High Availability appliances also write to a date stamped log file named

output.processManager.<datestamp>

located in this directory: /bsc/logs/processManager

The file shows current status as well as debug output.

Process down events

These events are not generated for the FortiNAC Control Manager.

FortiNAC generates events and alarms whenever any of the required processes fails or does not start as expected. FortiNAC tries to restart the process every 30 seconds. In a High Availability environment failover occurs after the fourth failed restart attempt. These events are enabled by default and each event has a corresponding alarm.

Events for failed processes include:

  • Service Down - Tomcat Admin
  • Service Down - Tomcat Portal
  • Service Down -dhcpd
  • Service Down -httpd
  • Service Down -mysqld
  • Service Down -named
  • Service Down -sshd

Process started events

These events are not generated for the FortiNAC Control Manager.

FortiNAC generates events whenever any of the required processes is started. These events are enabled by default and each event has a corresponding alarm. Alarms for process started events are not typically enabled. They can be enabled manually using Alarm Mappings.

In the Event View, event messages for started processes include the name of the process and the IP address of the machine where the process started. For example, if the named process started you would see the following message associated with the event.

A critical serdsvice (/bsc/services/named/sbin/named) on 192.168.5.228 was not running and has been started.

Events for started processes include:

  • Service Started - Tomcat Admin
  • Service Started - Tomcat Portal
  • Service Started -dhcpd
  • Service Started -httpd
  • Service Started -mysqld
  • Service Started -named
  • Service Started -sshd

Other high availability events

These events are not generated for the FortiNAC Control Manager.

An Event appears in the Events view and can have an alarm configured to send email to you when it occurs.

  • Database Replication Error — This event is generated if the database on the secondary appliance is not replicating.
  • System Failover — This event is generated when a failover occurs.

Monitor high availability

Monitoring current status

These events are not generated for the FortiNAC Control Manager.

The status of your High Availability appliances can be viewed on the Dashboard in a Summary panel.

The High Availability appliances also write to a date stamped log file named

output.processManager.<datestamp>

located in this directory: /bsc/logs/processManager

The file shows current status as well as debug output.

Process down events

These events are not generated for the FortiNAC Control Manager.

FortiNAC generates events and alarms whenever any of the required processes fails or does not start as expected. FortiNAC tries to restart the process every 30 seconds. In a High Availability environment failover occurs after the fourth failed restart attempt. These events are enabled by default and each event has a corresponding alarm.

Events for failed processes include:

  • Service Down - Tomcat Admin
  • Service Down - Tomcat Portal
  • Service Down -dhcpd
  • Service Down -httpd
  • Service Down -mysqld
  • Service Down -named
  • Service Down -sshd

Process started events

These events are not generated for the FortiNAC Control Manager.

FortiNAC generates events whenever any of the required processes is started. These events are enabled by default and each event has a corresponding alarm. Alarms for process started events are not typically enabled. They can be enabled manually using Alarm Mappings.

In the Event View, event messages for started processes include the name of the process and the IP address of the machine where the process started. For example, if the named process started you would see the following message associated with the event.

A critical serdsvice (/bsc/services/named/sbin/named) on 192.168.5.228 was not running and has been started.

Events for started processes include:

  • Service Started - Tomcat Admin
  • Service Started - Tomcat Portal
  • Service Started -dhcpd
  • Service Started -httpd
  • Service Started -mysqld
  • Service Started -named
  • Service Started -sshd

Other high availability events

These events are not generated for the FortiNAC Control Manager.

An Event appears in the Events view and can have an alarm configured to send email to you when it occurs.

  • Database Replication Error — This event is generated if the database on the secondary appliance is not replicating.
  • System Failover — This event is generated when a failover occurs.