Skip to main content
majid23
Staff
Staff
March 9, 2026

Technical Tip: Troubleshooting scheduled speed test issues on FortiGate

  • March 9, 2026
  • 1 reply
  • 429 views
Description This article describes troubleshooting commands when a scheduled speed test does not run on FortiGate.
Scope FortiGate, SD-WAN.
Solution

Devices with an SD-WAN Network Monitor license can run WAN speed tests on a schedule. The relevant configuration is found in 'config system speed-test-schedule', see Scheduled interface speed test.

In some cases, a speed test may not run as configured. Follow the steps below to troubleshoot the issue:

 

  1. Verify the SD-WAN Network Monitor license.

An SD-WAN Network Monitor license is required to use the speed test feature. The license status can be verified in GUI from the either the License widget or the System -> FortiGuard page.

  1. Verify manual speed test server download.

Run the following command to confirm the FortiGate can download the speed test server:

execute speed-test-server download

Example of timeout output:

 

FortiGate # execute speed-test-server download

Download timeout.

 

If Download timeout is seen, verify WAN connectivity and confirm the FortiGate has internet access. This may indicate a connectivity issue between the FortiGate and the speed test server.

 

Example of successful output:

 

FortiGate # execute speed-test-server download

Download completed.

  1. Check SD-WAN event logs:

     

To verify whether the recurring speed test ran successfully or failed, filter the event log for entries such as Log Description: 'SD-WAN Bandwidth Monitoring Result'. See the document System Events log page.

 

These logs help confirm whether the scheduled speed test was triggered and whether it completed successfully.

  1. Check crash logs:

If the issue persists, check for any related process crashes:

 

diagnose sys crashlog read | grep YYYY-MM

  1. Collect debug output for intermittent issues.

If the issue occurs intermittently, collect debug output while waiting for the problem to happen, see Technical Tip: How to create a log file of a session using PuTTY. Run the following commands from an SSH client connected to the FortiGate:

 

diagnose debug reset

diagnose debug console timestamp enable

diagnose debug duration 0

diagnose debug application speedtest -1

diagnose debug enable

diagnose sniffer packet any "host 1.2.3.4 and not host 1.2.3.4" 4 0 l <----- This sniffer is not to capture any packets, but to keep the SSH session open.

  1. View the speed test results:

show full system interface port1 | grep measure

set measured-upstream-bandwidth 116183
set measured-downstream-bandwidth 239242

set bandwidth-measure-time 1772495002

Note: The bandwidth-measure-time '1772495002' indicates when the bandwidth measurement was recorded and is stored in epoch time format. This value can be converted to a human-readable date and time using third-party timestamp converters such as Epochconverter.

 

Related documents:

    1 reply

    abays_FTNT
    Staff
    Staff
    April 23, 2026

    diagnose sys crashlog read | grep YYYY-MM does not work at 7.4.X, producing the following error:

     

    # diag sys crashlog read | grep 2026-04

     

    command parse error before 'crashlog'

    Command fail. Return code -61

     

    the working command is 

    diagnose debug crashlog read | grep YYYY-MM