Fortinet white logo
Fortinet white logo

Hyperscale Firewall Guide

Adding event logs to hardware logging

Adding event logs to hardware logging

Only CPU or host hardware logging supports adding event logs to hardware log messages. As well, event log messages are 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 to add event logs to hardware logging. Enable log-gen-event 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.

config log npu-server

set log-processor host

config server-group

edit <group-name>

set log-mode per-nat-mapping

set log-format syslog

set log-gen-event enable

end

Adding event logs to hardware logging

Adding event logs to hardware logging

Only CPU or host hardware logging supports adding event logs to hardware log messages. As well, event log messages are 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 to add event logs to hardware logging. Enable log-gen-event 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.

config log npu-server

set log-processor host

config server-group

edit <group-name>

set log-mode per-nat-mapping

set log-format syslog

set log-gen-event enable

end