|
Here is the config example:
config sys sdwan
config health-check
edit <Performance SLA Name>
set sla-fail-log-period <x>
set sla-pass-log-period <y>
next
end
end
<sla-fail-log-period> Enter an integer value from <0> to <3600> <----- Log frequency in seconds.
For example:
config sys sdwan
(sdwan) # config health-check
(health-check) # edit SLA
(SLA) # set sla-fail-log-period 30
(SLA) # set sla-pass-log-period 30
(SLA) # end
It is possible to enable the SLA fails and SLA pass log with the above configuration for a specific Performance SLA.
Once configured, FortiGate will store the SLA information at the frequency defined in the configuration.
FortiGate will keep the logs for 10 minutes. For longer retention, there should be an external storage like FortiAnalyzer.
The generated logs sent to FortiAnalyzer or FortiManager with FortiAnalyzer functions enabled will be used for SD-WAN-related reports and widgets (FortiView -> SD-WAN).
View the stored SLA logs via CLI:
diagnose sys sdwan sla-log <name> <seq-num>
To display the SLA logs per interface, use the following command:
diagnose sys sdwan intf-sla-log <name>
Here is an example:
diagnose sys sdwan sla-log SLA 1
Timestamp: Thu Sep 14 08:31:14 2023, vdom root, health-check SLA, interface: port9, status: down, latency: 0.000, jitter: 0.000, packet loss: 100.000%, mos: 0.000.
Timestamp: Thu Sep 14 08:31:14 2023, vdom root, health-check SLA, interface: port9, status: down, latency: 0.000, jitter: 0.000, packet loss: 100.000%, mos: 0.000.
nitrogen-kvm82 # diagnose sys sdwan intf-sla-log port9
Timestamp: Thu Sep 14 08:34:01 2023, used inbandwidth: 40bps, used outbandwidth: 42bps, used bibandwidth: 82bps, tx bytes: 370742bytes, rx bytes: 712567bytes.
Timestamp: Thu Sep 14 08:34:11 2023, used inbandwidth: 80bps, used outbandwidth: 21bps, used bibandwidth: 101bps, tx bytes: 370742bytes, rx bytes: 712820bytes.
|
