Alarms and Events

Process Down Events

FortiNAC generates events and alarms whenever any of the required processes fail or do not start as expected. FortiNAC tries to restart the problematic 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.

In the Event View, event messages for failed processes include the name of the process and the IP address of the machine where the process failed. For example, if the named process failed 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.

Events for failed processes include:

Service Down - dhcpd

Service Down - httpd

Service Down - mysqld

Service Down - named

Service Down - SSHd

Process Started Events

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 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 - dhcpd

Service Started - httpd

Service Started - mysqld

Service Started - named

Service Started - SSHd

Other High Availability Events

Important: 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.