---
title: "Diagnostics"
id: "diagnostics"
project: "SC//Connect™ | OS v8.5"
url: "https://docs.scalecomputing.com/articles/sc-connect-os-v8-5/diagnostics"
updated: 2026-11-19T17:09:05Z
---

# Diagnostics

The **Diagnostics** section provides tools to monitor and troubleshoot network performance. It enables network administrators to perform tasks such as ping tests, speed tests, and packet captures to diagnose connectivity issues and ensure optimal network performance.

![](/resources/Storage/sc-connect-os-v8-5/diagnostics/diagnostics-2026-10-26.png)

The **Diagnostics** section is broadly divided into three sections to allow users to run different diagnostics and view the results. To begin with diagnostics, select the interface on which the diagnostics need to be run.

## **To select an interface**

In the **Interface Selection** drop-down menu, select an interface from the available options.****
* **Automatic** – Selecting this option routes the diagnostic traffic through the underlay links (internet links) without specifying a specific interface. The **Send diagnostic traffic through the tunnel** option is disabled, as the automatic selection ensures traffic is routed exclusively through the underlay and not through the tunnel.
* **Lan interface** – Select this interface to send the diagnostics over the LAN interface.
* **Wan interface (wan1, wan2, wan3)** – Selecting a WAN interface routes the diagnostic traffic through the underlay link connected to the respective WAN port.
* **wwan0** – This option represents wireless WAN (LTE) and is used to test LTE links.
* **Send Diagnostic Traffic Through the Tunnel** – When checked, the diagnostic traffic (e.g., ping tests) will be routed through the SD-WAN (Tunnel) instead of the underlay physical links.![Shape](data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAAAXNSR0IArs4c6QAAAARnQU1BAACxjwv8YQUAAAAJcEhZcwAADsMAAA7DAcdvqGQAAAANSURBVBhXY2BgYGAAAAAFAAGKM+MAAAAAAElFTkSuQmCC)
## **To run a ping test**

The **Ping** test allows you to test the connectivity to a specified IP address or domain.

1. Select the interface from the **Interface Selection** drop-down menu.
2. In the **Destination** field, enter the IP address or domain to be pinged.
3. Select the site of the ping packets in bytes using the **Payload [B]** field.
4. Select the duration of the test in seconds with **Duration [s]** field.
5. The **MTU Scan**option allows you to detect the maximum transmission unit (MTU) size. Selecting the checkbox displays the MTU value.
    1. If the Send diagnostic traffic through the tunnel option is selected, then MTU value is 1400.
![](/resources/Storage/sc-connect-os-v8-5/diagnostics/diagnostics-2026-10-26-2.png)
    2. If the Send diagnostic traffic through the tunnel option is not selected, then MTU value is 1500.
![](/resources/Storage/sc-connect-os-v8-5/diagnostics/diagnostics-2026-10-26-1.png)
6. Click **Start** to initiate the ping test and click **Stop** to stop the test.

## **To run a speed test**

The **Speed test** allows you to measure the upload and download speed of the link to a selected server.

1. Select the interface from the **Interface Selection** drop-down menu.
2. In the **Destination Server** drop-down menu, select the gateway closest to the location of site for the speed test.
3. Specify the direction of the speed test from the **Direction** drop-down menu. You can choose to test the upload, download or both directions.
4. Select the duration of test in seconds with **Duration [s]** field.
5. Click **Start** to initiate the speed test and click **Stop** to stop the test.
## **![Shape](data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAAAXNSR0IArs4c6QAAAARnQU1BAACxjwv8YQUAAAAJcEhZcwAADsMAAA7DAcdvqGQAAAANSURBVBhXY2BgYGAAAAAFAAGKM+MAAAAAAElFTkSuQmCC) To run a packet capture test**

The **Packet Capture** test capture network traffic for analysis.

1. Select the interface from the **Interface Selection** drop-down menu.
2. Deselect the **Send Diagnostic Traffic Through the Tunnel** option.
3. To filter the captured traffic based on specific criteria, use the **Filter** option.
The filter criteria must be formatted in the Wireshark-style syntax to enable precise traffic analysis. For example, to capture for a specific host, you can use the following filter: host 192.168.1.1. This will capture all traffic to and from the host with the IP address 192.168.1.1.
4. Select a value from **Packet Length [B]** drop-down to specify the maximum size of packets to capture.
By default, the value is **1500**, which is the MTU.
5. Select the duration of test in seconds with **Duration [s]** field.
6. Click **Start** to initiate the packet capture test and click **Stop** to end the test.
7. Click **Download** to download the captured traffic file in PCAP format.
* Ensure the capture process is complete before downloading. If you click **Stop** before the capture finishes, the file cannot be downloaded.
    * When the **Send Diagnostic Traffic Through the Tunnel** option is enabled, the capture may not provide relevant insights. This is because the traffic will be captured at the tunnel level, showing only UDP packets with the destination port 6666.