Technical Tip: Command to find historic log of the performance SLA of SD-WAN member
Description
This article provides a command to find the historic log of the performance SLA via CLI.
Scope
FortiGate.
Solution
Command to find historic log of the Performance SLA of SD-WAN member.
V6.2 and v6.4:
dia sys virtual-wan-link sla-log <Health check name> <member id>
V7.0 and above:
dia sys sdwan sla-log <Health check name> <member id>
Command to find the member ID:
V6.2 and v6.4:
aegon-kvm20 # dia sys virtual-wan-link member
Member(1): interface: port2, gateway: 10.40.63.254, priority: 0, weight: 0 <----- 1 is the SD-WAN member id for port2.
Member(2): interface: port1, gateway: 10.40.31.254, priority: 0, weight: 0 <----- 2 is the SD-WAN member id for port1.
V7.0 and above:
aegon-kvm20 # dia sys sdwan member
Member(1): interface: port2, gateway: 10.40.63.254, priority: 0, weight: 0 <----- 1 is the SD-WAN member id for port2.
Member(2): interface: port1, gateway: 10.40.31.254, priority: 0, weight: 0 <----- 2 is the SD-WAN member id for port1.
Command to find the specific health-check name:
V6.2 andv 6.4:
aegon-kvm20 # dia sys virtual-wan-link health-check
Health Check(ping):
Seq(2): state(alive), packet-loss(0.000%) latency(8.768), jitter(0.228) sla_map=0x1
Seq(1): state(alive), packet-loss(0.000%) latency(8.658), jitter(0.221) sla_map=0x1
Health Check(ping2):
Seq(2): state(dead), packet-loss(100.000%) sla_map=0x0
Seq(1): state(dead), packet-loss(100.000%) sla_map=0x0
'ping' and 'ping2' is the name of the health-check.
Example:
dia sys virtual-wan-link sla-log ping 1 <00000 <----- This will provide the history log of the Performance SLA for port1.
Timestamp: Mon Apr 12 08:32:13 2021, vdom root, health-check ping, interface: port2, status: up, latency: 8.586, jitter: 0.073, packet loss: 0.000%.
Timestamp: Mon Apr 12 08:32:14 2021, vdom root, health-check ping, interface: port2, status: up, latency: 8.587, jitter: 0.073, packet loss: 0.000%.
Timestamp: Mon Apr 12 08:32:14 2021, vdom root, health-check ping, interface: port2, status: up, latency: 8.629, jitter: 0.116, packet loss: 0.000%.
Timestamp: Mon Apr 12 08:32:15 2021, vdom root, health-check ping, interface: port2, status: up, latency: 8.629, jitter: 0.160, packet loss: 0.000%.
Timestamp: Mon Apr 12 08:32:15 2021, vdom root, health-check ping, interface: port2, status: up, latency: 8.630, jitter: 0.158, packet loss: 0.000%.
V7.0 and above:
aegon-kvm20 # dia sys sdwan health-check
Health Check(ping):
Seq(2): state(alive), packet-loss(0.000%) latency(8.768), jitter(0.228) sla_map=0x1
Seq(1): state(alive), packet-loss(0.000%) latency(8.658), jitter(0.221) sla_map=0x1
Health Check(ping2):
Seq(2): state(dead), packet-loss(100.000%) sla_map=0x0
Seq(1): state(dead), packet-loss(100.000%) sla_map=0x0
'ping' and 'ping2' is the name of the health-check.
Example:
dia sys sdwan sla-log ping 1 <00000 <----- This will provide the history log of the Performace SLA for port1.
Timestamp: Mon Apr 12 08:32:13 2021, vdom root, health-check ping, interface: port2, status: up, latency: 8.586, jitter: 0.073, packet loss: 0.000%.
Timestamp: Mon Apr 12 08:32:14 2021, vdom root, health-check ping, interface: port2, status: up, latency: 8.587, jitter: 0.073, packet loss: 0.000%.
Timestamp: Mon Apr 12 08:32:14 2021, vdom root, health-check ping, interface: port2, status: up, latency: 8.629, jitter: 0.116, packet loss: 0.000%.
Timestamp: Mon Apr 12 08:32:15 2021, vdom root, health-check ping, interface: port2, status: up, latency: 8.629, jitter: 0.160, packet loss: 0.000%.
Timestamp: Mon Apr 12 08:32:15 2021, vdom root, health-check ping, interface: port2, status: up, latency: 8.630, jitter: 0.158, packet loss: 0.000%.