|
At the time of the issue, there is no actual packet lost against configured SD wan SLA servers, this can be confirmed by running sniffers, or debug flows on the FortiGate console session.
This is a known issue #1023878 on 7.2.8 and 7.4 and resolved in 7.2.9, 7.4.5, 7.6.0.
To confirm the match, run the link-monitor debugs on an SSH session on the FortiGate for a few hours.
Check for seq_no=32768 and above with a correlation to the time of SLA failure.
Example:
Link-monitor debug at time of loss:
2024-04-25 19:31:30 lnkmtd::monitor_proto_peer_send_request(625): ---> SLA_Internet-1-VIRTUAL_WAN_LINK-1(9.9.9.9:ping) send probe packet, fail count(0)
2024-04-25 19:31:30 2024-04-25 19:31:30 lnkmtd::ping_send_msg(435): ---> ping 8.8.8.8 seq_no=32768, icmp id=4893, send 20 bytes
2024-04-25 19:31:30 lnkmtd::monitor_proto_peer_send_request(625): ---> SLA_Internet-2-VIRTUAL_WAN_LINK-2(8.8.8.8:ping) send probe packet, fail count(0)
2024-04-25 19:31:30 2024-04-25 19:31:30 lnkmtd::ping_send_msg(435): ---> ping 9.9.9.9 seq_no=32768, icmp id=4897, send 20 bytes
Link monitor debug command:
diagnose debug app link-monitor -1
diagnose debug console time enable
diagnose debug enable
Related article:
Technical Tip: How to create a log file of a session using PuTTY
|
