Fortinet black logo

Log Reference

System Event HA logs

Copy Link
Copy Doc ID a45c6ff5-b74f-11eb-b70b-00505692583a:512843
Download PDF

System Event HA logs

This chapter contains information regarding System Event HA (high availability) log messages.

Kevent HA log is a subtype log of the Event log type. Kevent HA log messages inform you of any high availability problems that may occur within a high availability cluster.

You can cross-search a System Event HA log message to get more information about it. For more information about log message cross search, see Log message cross search .

Example

If you send the FortiMail log messages to a remote Syslog server (including FortiAnalyzer), an HA log would look like the following and the log fields would appear in the following order:

date=2012-08-09 time=10:30:31 device_id=FE100C3909600504 log_id=0004001036 type=kevent subtype=ha pri=notice user=ha ui=ha action=none status=success msg="hahbd: heart beat status changed to primary-hearbeat-port1=FAILED;secondary-hearbeat-port2=OK"

Note

The list of event logs presented in this document is not exhaustive.

System Event HA logs

This chapter contains information regarding System Event HA (high availability) log messages.

Kevent HA log is a subtype log of the Event log type. Kevent HA log messages inform you of any high availability problems that may occur within a high availability cluster.

You can cross-search a System Event HA log message to get more information about it. For more information about log message cross search, see Log message cross search .

Example

If you send the FortiMail log messages to a remote Syslog server (including FortiAnalyzer), an HA log would look like the following and the log fields would appear in the following order:

date=2012-08-09 time=10:30:31 device_id=FE100C3909600504 log_id=0004001036 type=kevent subtype=ha pri=notice user=ha ui=ha action=none status=success msg="hahbd: heart beat status changed to primary-hearbeat-port1=FAILED;secondary-hearbeat-port2=OK"

Note

The list of event logs presented in this document is not exhaustive.