Cisco Catalyst SD-WAN Troubleshooting Guide

PDF

Cisco Catalyst SD-WAN Troubleshooting Guide

Troubleshoot speed test issues

Want to summarize with AI?

Log in

Provides troubleshooting information for resolving common speed test issues including DNS resolution, server connectivity, and configuration problems.


The speed test uses iperf3 with the TCP protocol. The speed test result depends on the latency and packet loss between the client and server.

The built-in speed test servers are not based on geographic proximity, so end users are highly recommended to input and use an iPerf3 server located near them.

Table 1. Troubleshooting scenarios

Error Information

Possible Root Cause

Failed to resolve iperf server address

DNS server is not configured at edge device or is unable to resolve the iperf server from the configured DNS server at edge device.

Speed test servers not reachable

The speed test server ping failed. The edge device cannot reach the server IP.

iPerf client: unable to connect stream: Resource temporarily unavailable

Unable to connect to the speed test server. Access may be blocked by access-control list (ACL) permissions.

iPerf client: unable to connect to server

The iPerf3 server is not providing the test service at the user-specified port or default port 5201.

Device Error: Speed test in progress

The selected source or destination device is performing a speed test and cannot start a new one.

Device error: Failed to read server configuration

The data stream configuration is missing.

Workaround: Running a CLI command at the edge device and clearing the Cisco Catalyst SD-WAN control connections can fix the issue.

Speed test session has timed out

The speed test has not successfully completed in 180 seconds. This might be because the edge device has lost the control connection to Cisco SD-WAN Manager during the speed testing.