Fortinet Document Library

Version:

Version:


Table of Contents

Administration Guide

Download PDF
Copy Link

Monitor

Monitoring current status

Note

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

Note

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
Note

When the system confirms that the httpd service is running, the system then attempts to connect to ports 80 and 443. If the system fails to connect to either port, the service is restarted.

Process started events

Note

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 host where the process started. For example, if the named process started you would see the following message associated with the event:

A critical service (/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 events

Note

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

Monitoring current status

Note

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

Note

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
Note

When the system confirms that the httpd service is running, the system then attempts to connect to ports 80 and 443. If the system fails to connect to either port, the service is restarted.

Process started events

Note

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 host where the process started. For example, if the named process started you would see the following message associated with the event:

A critical service (/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 events

Note

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.