Fortinet Document Library

Version:

Version:

Version:

Version:


Table of Contents

Administration Guide

Download PDF
Copy Link

Understanding SD-WAN related logs

This topic lists the SD-WAN related logs and explains when the logs will be triggered.

Health-check detects a failure:
  • When health-check detects a failure, it will record a log:
    1: date=2021-04-20 time=17:06:31 eventtime=1618963591590008160 tz="-0700" logid="0100022921" type="event" subtype="system" level="critical" vd="root" logdesc="Routing information changed" name="test" interface="R150" status="down" msg="Static route on interface R150 may be removed by health-check test. Route:  (10.100.1.2->10.100.2.22 ping-down)"
  • When health-check detects a recovery, it will record a log:
    2: date=2021-04-20 time=17:11:46 eventtime=1618963906950174240 tz="-0700" logid="0100022921" type="event" subtype="system" level="critical" vd="root" logdesc="Routing information changed" name="test" interface="R150" status="up" msg="Static route on interface R150 may be added by health-check test. Route:  (10.100.1.2->10.100.2.22 ping-up)"
Health-check has an SLA target and detects SLA qualification changes:
  • When health-check has an SLA target and detects SLA changes, and changes to fail:
    1: date=2021-04-20 time=21:32:33 eventtime=1618979553388763760 tz="-0700" logid="0113022923" type="event" subtype="sdwan" level="notice" vd="root" logdesc="Virtual WAN Link status" eventtype="Health Check" healthcheck="test" slatargetid=1 oldvalue="2" newvalue="1" msg="Number of pass member changed."
    2: date=2021-04-20 time=21:32:33 eventtime=1618979553388751880 tz="-0700" logid="0113022923" type="event" subtype="sdwan" level="notice" vd="root" logdesc="Virtual WAN Link status" eventtype="Health Check" healthcheck="test" slatargetid=1 member="1" msg="Member status changed. Member out-of-sla."
    
  • When health-check has an SLA target and detects SLA changes, and changes to pass:
    1: date=2021-04-20 time=21:38:49 eventtime=1618979929908765200 tz="-0700" logid="0113022923" type="event" subtype="sdwan" level="notice" vd="root" logdesc="Virtual WAN Link status" eventtype="Health Check" healthcheck="test" slatargetid=1 oldvalue="1" newvalue="2" msg="Number of pass member changed."
    2: date=2021-04-20 time=21:38:49 eventtime=1618979929908754060 tz="-0700" logid="0113022923" type="event" subtype="sdwan" level="information" vd="root" logdesc="Virtual WAN Link status" eventtype="Health Check" healthcheck="test" slatargetid=1 member="1" msg="Member status changed. Member in sla."
    
SD-WAN calculates a link's session/bandwidth over/under its ratio and stops/resumes traffic:
  • When SD-WAN calculates a link's session/bandwidth over its configured ratio and stops forwarding traffic:
    1: date=2021-04-20 time=21:55:14 eventtime=1618980914728863220 tz="-0700" logid="0113022924" type="event" subtype="sdwan" level="notice" vd="root" logdesc="Virtual WAN Link volume status" eventtype="Volume" interface="R160" member="2" msg="Member enters into conservative status with limited ablity to receive new sessions for too much traffic."
  • When SD-WAN calculates a link's session/bandwidth according to its ratio and resumes forwarding traffic:
    2: date=2021-04-20 time=22:12:52 eventtime=1618981972698753360 tz="-0700" logid="0113022924" type="event" subtype="sdwan" level="notice" vd="root" logdesc="Virtual WAN Link volume status" eventtype="Volume" interface="R160" member="2" msg="Member resume normal status to receive new sessions for internal adjustment"
The SLA mode service rule's SLA qualified member changes:
  • When the SLA mode service rule's SLA qualified member changes. In this example R150 fails the SLA check, but is still alive:
    1: date=2021-04-20 time=22:40:46 eventtime=1618983646428803040 tz="-0700" logid="0113022923" type="event" subtype="sdwan" level="notice" vd="root" logdesc="Virtual WAN Link status" eventtype="Service" serviceid=1 service="test" seq="2,1" msg="Service prioritized by SLA will be redirected in sequence order."
  • When the SLA mode service rule's SLA qualified member changes. In this example R150 changes from fail to pass:
    2: date=2021-04-20 time=22:41:51 eventtime=1618983711678827920 tz="-0700" logid="0113022923" type="event" subtype="sdwan" level="notice" vd="root" logdesc="Virtual WAN Link status" eventtype="Service" serviceid=1 service="test" seq="1,2" msg="Service prioritized by SLA will be redirected in sequence order."
The priority mode service rule member's link status changes:
  • When priority mode service rule member's link status changes. In this example R150 changes to better than R160, and both are still alive:
    1: date=2021-04-20 time=22:56:55 eventtime=1618984615708804760 tz="-0700" logid="0113022923" type="event" subtype="sdwan" level="notice" vd="root" logdesc="Virtual WAN Link status" eventtype="Service" serviceid=1 service="test" metric="packet-loss" seq="2,1" msg="Service prioritized by performance metric will be redirected in sequence order."
  • When priority mode service rule member's link status changes. In this example R160 changes to better than R150, and both are still alive:
    2: date=2021-04-20 time=22:56:58 eventtime=1618984618278852140 tz="-0700" logid="0113022923" type="event" subtype="sdwan" level="notice" vd="root" logdesc="Virtual WAN Link status" eventtype="Service" serviceid=1 service="test" metric="packet-loss" seq="1,2" msg="Service prioritized by performance metric will be redirected in sequence order."
SD-WAN member is used in service and it fails the health-check:
  • When SD-WAN member fails the health-check, it will stop forwarding traffic:
    1: date=2021-04-20 time=23:04:32 eventtime=1618985072898756700 tz="-0700" logid="0113022923" type="event" subtype="sdwan" level="notice" vd="root" logdesc="Virtual WAN Link status" eventtype="Service" interface="R150" member="1" serviceid=1 service="test" gateway=10.100.1.1 msg="Member link is unreachable or miss threshold. Stop forwarding traffic. "
  • When SD-WAN member passes the health-check again, it will resume forwarding logs:
    2: date=2021-04-20 time=23:06:08 eventtime=1618985168018789600 tz="-0700" logid="0113022923" type="event" subtype="sdwan" level="notice" vd="root" logdesc="Virtual WAN Link status" eventtype="Service" interface="R150" member="1" serviceid=1 service="test" gateway=10.100.1.1 msg="Member link is available. Start forwarding traffic. "
Load-balance mode service rule's SLA qualified member changes:
  • When load-balance mode service rule's SLA qualified member changes. In this example R150 changes to not meet SLA:
    1: date=2021-04-20 time=23:10:24 eventtime=1618985425048820800 tz="-0700" logid="0113022923" type="event" subtype="sdwan" level="notice" vd="root" logdesc="Virtual WAN Link status" eventtype="Service" serviceid=1 service="test" member="2(R160)" msg="Service will be load balanced among members with available routing."
  • When load-balance mode service rule's SLA qualified member changes. In this example R150 changes to meet SLA:
    2: date=2021-04-20 time=23:11:34 eventtime=1618985494478807100 tz="-0700" logid="0113022923" type="event" subtype="sdwan" level="notice" vd="root" logdesc="Virtual WAN Link status" eventtype="Service" serviceid=1 service="test" member="2(R160),1(R150)" msg="Service will be load balanced among members with available routing."
SLA link status logs, generated with interval sla-fail-log-period or sla-pass-log-period:
  • When SLA fails, SLA link status logs will be generated with interval sla-fail-log-period:
    1: date=2021-04-20 time=23:18:10 eventtime=1618985890469018260 tz="-0700" logid="0113022925" type="event" subtype="sdwan" level="notice" vd="root" logdesc="Virtual WAN Link SLA information" eventtype="SLA" healthcheck="test" slatargetid=1 interface="R150" status="up" latency="0.061" jitter="0.004" packetloss="2.000%" inbandwidthavailable="0kbps" outbandwidthavailable="200.00Mbps" bibandwidthavailable="200.00Mbps" inbandwidthused="1kbps" outbandwidthused="1kbps" bibandwidthused="2kbps" slamap="0x0" metric="packetloss" msg="Health Check SLA status. SLA failed due to being over the performance metric threshold."
  • When SLA passes, SLA link status logs will be generated with interval sla-pass-log-period:
    2: date=2021-04-20 time=23:18:12 eventtime=1618985892509027220 tz="-0700" logid="0113022925" type="event" subtype="sdwan" level="information" vd="root" logdesc="Virtual WAN Link SLA information" eventtype="SLA" healthcheck="test" slatargetid=1 interface="R150" status="up" latency="0.060" jitter="0.003" packetloss="0.000%" inbandwidthavailable="0kbps" outbandwidthavailable="200.00Mbps" bibandwidthavailable="200.00Mbps" inbandwidthused="1kbps" outbandwidthused="1kbps" bibandwidthused="2kbps" slamap="0x1" msg="Health Check SLA status."

Understanding SD-WAN related logs

This topic lists the SD-WAN related logs and explains when the logs will be triggered.

Health-check detects a failure:
  • When health-check detects a failure, it will record a log:
    1: date=2021-04-20 time=17:06:31 eventtime=1618963591590008160 tz="-0700" logid="0100022921" type="event" subtype="system" level="critical" vd="root" logdesc="Routing information changed" name="test" interface="R150" status="down" msg="Static route on interface R150 may be removed by health-check test. Route:  (10.100.1.2->10.100.2.22 ping-down)"
  • When health-check detects a recovery, it will record a log:
    2: date=2021-04-20 time=17:11:46 eventtime=1618963906950174240 tz="-0700" logid="0100022921" type="event" subtype="system" level="critical" vd="root" logdesc="Routing information changed" name="test" interface="R150" status="up" msg="Static route on interface R150 may be added by health-check test. Route:  (10.100.1.2->10.100.2.22 ping-up)"
Health-check has an SLA target and detects SLA qualification changes:
  • When health-check has an SLA target and detects SLA changes, and changes to fail:
    1: date=2021-04-20 time=21:32:33 eventtime=1618979553388763760 tz="-0700" logid="0113022923" type="event" subtype="sdwan" level="notice" vd="root" logdesc="Virtual WAN Link status" eventtype="Health Check" healthcheck="test" slatargetid=1 oldvalue="2" newvalue="1" msg="Number of pass member changed."
    2: date=2021-04-20 time=21:32:33 eventtime=1618979553388751880 tz="-0700" logid="0113022923" type="event" subtype="sdwan" level="notice" vd="root" logdesc="Virtual WAN Link status" eventtype="Health Check" healthcheck="test" slatargetid=1 member="1" msg="Member status changed. Member out-of-sla."
    
  • When health-check has an SLA target and detects SLA changes, and changes to pass:
    1: date=2021-04-20 time=21:38:49 eventtime=1618979929908765200 tz="-0700" logid="0113022923" type="event" subtype="sdwan" level="notice" vd="root" logdesc="Virtual WAN Link status" eventtype="Health Check" healthcheck="test" slatargetid=1 oldvalue="1" newvalue="2" msg="Number of pass member changed."
    2: date=2021-04-20 time=21:38:49 eventtime=1618979929908754060 tz="-0700" logid="0113022923" type="event" subtype="sdwan" level="information" vd="root" logdesc="Virtual WAN Link status" eventtype="Health Check" healthcheck="test" slatargetid=1 member="1" msg="Member status changed. Member in sla."
    
SD-WAN calculates a link's session/bandwidth over/under its ratio and stops/resumes traffic:
  • When SD-WAN calculates a link's session/bandwidth over its configured ratio and stops forwarding traffic:
    1: date=2021-04-20 time=21:55:14 eventtime=1618980914728863220 tz="-0700" logid="0113022924" type="event" subtype="sdwan" level="notice" vd="root" logdesc="Virtual WAN Link volume status" eventtype="Volume" interface="R160" member="2" msg="Member enters into conservative status with limited ablity to receive new sessions for too much traffic."
  • When SD-WAN calculates a link's session/bandwidth according to its ratio and resumes forwarding traffic:
    2: date=2021-04-20 time=22:12:52 eventtime=1618981972698753360 tz="-0700" logid="0113022924" type="event" subtype="sdwan" level="notice" vd="root" logdesc="Virtual WAN Link volume status" eventtype="Volume" interface="R160" member="2" msg="Member resume normal status to receive new sessions for internal adjustment"
The SLA mode service rule's SLA qualified member changes:
  • When the SLA mode service rule's SLA qualified member changes. In this example R150 fails the SLA check, but is still alive:
    1: date=2021-04-20 time=22:40:46 eventtime=1618983646428803040 tz="-0700" logid="0113022923" type="event" subtype="sdwan" level="notice" vd="root" logdesc="Virtual WAN Link status" eventtype="Service" serviceid=1 service="test" seq="2,1" msg="Service prioritized by SLA will be redirected in sequence order."
  • When the SLA mode service rule's SLA qualified member changes. In this example R150 changes from fail to pass:
    2: date=2021-04-20 time=22:41:51 eventtime=1618983711678827920 tz="-0700" logid="0113022923" type="event" subtype="sdwan" level="notice" vd="root" logdesc="Virtual WAN Link status" eventtype="Service" serviceid=1 service="test" seq="1,2" msg="Service prioritized by SLA will be redirected in sequence order."
The priority mode service rule member's link status changes:
  • When priority mode service rule member's link status changes. In this example R150 changes to better than R160, and both are still alive:
    1: date=2021-04-20 time=22:56:55 eventtime=1618984615708804760 tz="-0700" logid="0113022923" type="event" subtype="sdwan" level="notice" vd="root" logdesc="Virtual WAN Link status" eventtype="Service" serviceid=1 service="test" metric="packet-loss" seq="2,1" msg="Service prioritized by performance metric will be redirected in sequence order."
  • When priority mode service rule member's link status changes. In this example R160 changes to better than R150, and both are still alive:
    2: date=2021-04-20 time=22:56:58 eventtime=1618984618278852140 tz="-0700" logid="0113022923" type="event" subtype="sdwan" level="notice" vd="root" logdesc="Virtual WAN Link status" eventtype="Service" serviceid=1 service="test" metric="packet-loss" seq="1,2" msg="Service prioritized by performance metric will be redirected in sequence order."
SD-WAN member is used in service and it fails the health-check:
  • When SD-WAN member fails the health-check, it will stop forwarding traffic:
    1: date=2021-04-20 time=23:04:32 eventtime=1618985072898756700 tz="-0700" logid="0113022923" type="event" subtype="sdwan" level="notice" vd="root" logdesc="Virtual WAN Link status" eventtype="Service" interface="R150" member="1" serviceid=1 service="test" gateway=10.100.1.1 msg="Member link is unreachable or miss threshold. Stop forwarding traffic. "
  • When SD-WAN member passes the health-check again, it will resume forwarding logs:
    2: date=2021-04-20 time=23:06:08 eventtime=1618985168018789600 tz="-0700" logid="0113022923" type="event" subtype="sdwan" level="notice" vd="root" logdesc="Virtual WAN Link status" eventtype="Service" interface="R150" member="1" serviceid=1 service="test" gateway=10.100.1.1 msg="Member link is available. Start forwarding traffic. "
Load-balance mode service rule's SLA qualified member changes:
  • When load-balance mode service rule's SLA qualified member changes. In this example R150 changes to not meet SLA:
    1: date=2021-04-20 time=23:10:24 eventtime=1618985425048820800 tz="-0700" logid="0113022923" type="event" subtype="sdwan" level="notice" vd="root" logdesc="Virtual WAN Link status" eventtype="Service" serviceid=1 service="test" member="2(R160)" msg="Service will be load balanced among members with available routing."
  • When load-balance mode service rule's SLA qualified member changes. In this example R150 changes to meet SLA:
    2: date=2021-04-20 time=23:11:34 eventtime=1618985494478807100 tz="-0700" logid="0113022923" type="event" subtype="sdwan" level="notice" vd="root" logdesc="Virtual WAN Link status" eventtype="Service" serviceid=1 service="test" member="2(R160),1(R150)" msg="Service will be load balanced among members with available routing."
SLA link status logs, generated with interval sla-fail-log-period or sla-pass-log-period:
  • When SLA fails, SLA link status logs will be generated with interval sla-fail-log-period:
    1: date=2021-04-20 time=23:18:10 eventtime=1618985890469018260 tz="-0700" logid="0113022925" type="event" subtype="sdwan" level="notice" vd="root" logdesc="Virtual WAN Link SLA information" eventtype="SLA" healthcheck="test" slatargetid=1 interface="R150" status="up" latency="0.061" jitter="0.004" packetloss="2.000%" inbandwidthavailable="0kbps" outbandwidthavailable="200.00Mbps" bibandwidthavailable="200.00Mbps" inbandwidthused="1kbps" outbandwidthused="1kbps" bibandwidthused="2kbps" slamap="0x0" metric="packetloss" msg="Health Check SLA status. SLA failed due to being over the performance metric threshold."
  • When SLA passes, SLA link status logs will be generated with interval sla-pass-log-period:
    2: date=2021-04-20 time=23:18:12 eventtime=1618985892509027220 tz="-0700" logid="0113022925" type="event" subtype="sdwan" level="information" vd="root" logdesc="Virtual WAN Link SLA information" eventtype="SLA" healthcheck="test" slatargetid=1 interface="R150" status="up" latency="0.060" jitter="0.003" packetloss="0.000%" inbandwidthavailable="0kbps" outbandwidthavailable="200.00Mbps" bibandwidthavailable="200.00Mbps" inbandwidthused="1kbps" outbandwidthused="1kbps" bibandwidthused="2kbps" slamap="0x1" msg="Health Check SLA status."