Fortinet white logo
Fortinet white logo

Host hardware logging support for user information and event logs

Host hardware logging support for user information and event logs

You can configure host hardware logging to:

  • Include user information in hardware log messages to record information about logged in users accessing hyperscale firewall features.

  • Add event logs to hardware log messaging.

Only host hardware logging supports including user information in hardware log messages and event logs. As well both of these features are only supported for syslog messages.

Adding event logs to hardware log messages is only supported when the log mode is set to per NAT mapping. Per NAT mapping creates two log messages per session, one when the session allocates NAT mapping resources and one when NAT mapping resources are freed when the session ends.

CLI syntax:

config log npu-server

set log-processor host

config server-group

edit <group-name>

set log-mode {per-session | per-nat-mapping | per-session-ending}

set log-format syslog

set log-user-info {disable | enable}

set log-gen-event {disable | enable}

end

log-user-info enable to include user information in log messages. This option is only available if log-format is set to syslog.

log-gen-event enable to add event logs to hardware logging. This option is only available if log-format is set to syslog and log-mode is set to per-nat-mapping to reduce the number of log messages generated.

Host hardware logging support for user information and event logs

Host hardware logging support for user information and event logs

You can configure host hardware logging to:

  • Include user information in hardware log messages to record information about logged in users accessing hyperscale firewall features.

  • Add event logs to hardware log messaging.

Only host hardware logging supports including user information in hardware log messages and event logs. As well both of these features are only supported for syslog messages.

Adding event logs to hardware log messages is only supported when the log mode is set to per NAT mapping. Per NAT mapping creates two log messages per session, one when the session allocates NAT mapping resources and one when NAT mapping resources are freed when the session ends.

CLI syntax:

config log npu-server

set log-processor host

config server-group

edit <group-name>

set log-mode {per-session | per-nat-mapping | per-session-ending}

set log-format syslog

set log-user-info {disable | enable}

set log-gen-event {disable | enable}

end

log-user-info enable to include user information in log messages. This option is only available if log-format is set to syslog.

log-gen-event enable to add event logs to hardware logging. This option is only available if log-format is set to syslog and log-mode is set to per-nat-mapping to reduce the number of log messages generated.