FortiGate
FortiGate Next Generation Firewall utilizes purpose-built security processors and threat intelligence security services from FortiGuard labs to deliver top-rated protection and high performance, including encrypted traffic.
seyuboglu
Staff
Staff
Article Id 394443
Description This article outlines an issue with the SD-WAN speed test feature in the FortiGate GUI, where the test intermittently fails with an 'Internal Server Error'.
Scope FortiGate v7.2.10, v7.4.6 and v7.6.1.
Solution

SD-WAN Network Monitor is a licensed feature to determine upload and download speed by executing an automatic speed test on WAN links. Detailed information about the service can be found in this document: SD-WAN Network Monitor service

 

In some cases, this feature is not working as expected. The first speed test attempt may be completed successfully as shown below: 

 

  • Start the test by selecting the 'Execute speed test' button on the GUI. 'Estimated bandwidth' is 0 before tests.

 

Capture3.jpg

 

  • After the test is completed results will be updated successfully. Estimated bandwidth information will be populated with the results. 

 

Capture4.jpg

 

  • Start another test after the first one is completed. An 'Internal Server Error' may be presented by the GUI (Estimated bandwidth information, upstream and downstream results of the previous test are made available under the interface settings).

 

Capture2.JPG

 

The error code for this issue is not visible in the GUI but can be found when CLI debugging is enabled. Execute the commands below in the CLI.

 

FortiGate # diagnose netlink interface speed-test-result-clear
FortiGate # config system speed-test-server
FortiGate (speed-test-server) # purge
This operation will clear all table!
Do you want to continue? (y/n)y

FortiGate (speed-test-server) # end

FortiGate # execute speed-test-server download
Download completed.
FortiGate # diagnose debug console timestamp enable
FortiGate # diagnose debug application speedtest -1
Debug messages will be on for 30 minutes.
FortiGate # diagnose debug enable

 

After enabling debugging, start a new test in the GUI to capture an unsuccessful speed test. 

 

Example output is shown below : 

 

FortiGate # 2025-03-05 14:45:46 fcron_speedtest_dispatch()-460: No speed test to run
2025-03-05 14:45:56 fcron_speedtest_dispatch()-460: No speed test to run
2025-03-05 14:45:57 fcron_speedtest_dispatch()-539: [21496] Run test 50095 for 'wan' to cloud server

2025-03-05 14:45:57 speedtest_on_ike_event()-1532: on ike event tunnel up
2025-03-05 14:45:57 speedtest_on_ike_event()-1541: interface not found.
2025-03-05 14:45:57 speedtest_on_ike_event()-1532: on ike event tunnel up
2025-03-05 14:45:57 speedtest_on_ike_event()-1541: interface not found.
2025-03-05 14:45:57 speedtest_on_ike_event()-1532: on ike event tunnel up
2025-03-05 14:45:57 speedtest_on_ike_event()-1541: interface not found.
2025-03-05 14:45:57 speedtest_on_ike_event()-1532: on ike event tunnel up
2025-03-05 14:45:57 speedtest_on_ike_event()-1541: interface not found.
2025-03-05 14:46:07 fcron_speedtest_dispatch()-460: No speed test to run
2025-03-05 14:46:17 fcron_speedtest_dispatch()-460: No speed test to run
2025-03-05 14:46:27 fcron_speedtest_dispatch()-460: No speed test to run
2025-03-05 14:46:37 fcron_speedtest_dispatch()-460: No speed test to run
2025-03-05 14:46:37 fcron_speedtest_notify_func()-1300: Speed test pid=21496 done

 

Start the same tests on CLI on different servers with the command below:

 

FortiGate# execute speed-test wan FTNT_FR_Paris
Speed test quota for 12/23 is 1
bind to local ip 161.144.154.111 (wan IP on FortiGate) 
current vdom=root
Run in uploading mode.
Connecting to host 154.52.13.43, port 5200
[ 11] local 161.144.154.111 port 8188 connected to 154.52.13.43 port 5200
[ 13] local 161.144.154.111 port 8189 connected to 154.52.13.43 port 5200
[ 15] local 161.144.154.111 port 8190 connected to 154.52.13.43 port 5200
[ 17] local 161.144.154.111 port 8191 connected to 154.52.13.43 port 5200
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 11] 0.00-1.01 sec 741 KBytes 6.03 Mbits/sec 0 74.9 KBytes
[ 13] 0.00-1.01 sec 492 KBytes 4.00 Mbits/sec 1 35.4 KBytes
[ 15] 0.00-1.01 sec 564 KBytes 4.59 Mbits/sec 4 38.2 KBytes
[ 17] 0.00-1.01 sec 663 KBytes 5.40 Mbits/sec 0 65.0 KBytes
[SUM] 0.00-1.01 sec 2.40 MBytes 20.0 Mbits/sec 5

 

FortiGate# execute speed-test wan FTNT_DE_Frankfurt
Speed test quota for 12/23 is 2
bind to local ip 161.144.154.111
current vdom=root
Run in uploading mode.
Connecting to host 154.52.2.87, port 5200
[ 10] local 161.144.154.111 port 13855 connected to 154.52.2.87 port 5200
[ 12] local 161.144.154.111 port 13856 connected to 154.52.2.87 port 5200
[ 14] local 161.144.154.111 port 13857 connected to 154.52.2.87 port 5200
[ 16] local 161.144.154.111 port 13858 connected to 154.52.2.87 port 5200
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 10] 0.00-1.01 sec 297 KBytes 2.42 Mbits/sec 1 41.0 KBytes
[ 12] 0.00-1.01 sec 284 KBytes 2.32 Mbits/sec 0 52.3 KBytes
[ 14] 0.00-1.01 sec 308 KBytes 2.51 Mbits/sec 0 53.7 KBytes
[ 16] 0.00-1.01 sec 284 KBytes 2.32 Mbits/sec 0 49.5 KBytes
[SUM] 0.00-1.01 sec 1.15 MBytes 9.57 Mbits/sec 1

 

All tests are completed successfully when initiated via the CLI. These results confirm that the speed test is unstable when started from the GUI, but consistently functions as expected when run from the CLI.

 

This is a known issue and has been fixed in v7.4.8 and v7.6.3.