Skip to main content
Version: v25.07.31

Probing Tools Troubleshooting

The Probing Tools are designed to help verify connectivity, diagnose network issues, and ensure that configurations applied from the cloud are correctly reflected on the device. They provide automated tests such as Ping, TCP ping, and HTTP/HTTPS connectivity checks, and generate detailed reports for each task.

These tools are especially useful when:

  • A probing task assigned from the cloud does not work as expected or fails to report.
  • A probing tool report shows connectivity failure for a specific target.
  • You need to confirm that the configuration applied to the device matches the configuration stored in the cloud.

For a complete reference on Probing Tools, please see the official documentation: Probing Tools Reference Guide

When to use these tools?​

  • When a probing task assigned from the cloud does not work as expected or does not report.
  • When a probing tool report shows connectivity failure for a specific target.
  • To verify that the configuration applied to the device matches the configuration in the cloud.

Troubleshooting steps​

Cloud Configuration Verification​

This section details how to check the Probing Tool configurations made and applied from the cloud.

Access the CE Terminal​

Follow these steps to gain access to the CE device via the Command Line Interface.

sudo su -

The sudo su - command starts a shell session with superuser privileges, enabling execution of tasks that require elevated permissions.

Verify the Last Applied Configuration​

This command is used to view the details of the last successfully applied Probing Tool configuration from the stored response JSON file. The jq filter focuses on the networkDiagnosticsConfig section.

cat /tmp/last_config_response.json | jq .networkDiagnosticsConfig

This example output shows the last configuration done on diagnostics.

Example Response:​

{
    "taskId": "427665448e1f4ed6a7a511d285dd357b",
    "taskName": "test1",
    "sourceInterface": "eth0",
    "sourceIPAddress": "192.168.1.105",
    "templateId": "691ef0e83f1f4a667e0f750f",
    "taskCycle": "daily",
    "remark": null,
    "taskDateTime": "2025-11-29T00:00:00.000+00:00",
    "template": {
      "id": "691ef0e83f1f4a667e0f750f",
      "templateName": "test",
      "targets": [
        {
          "value": "1.1.1.1",
          "tests": [
            {
              "testType": "ping",
              "ports": []
            },
            {
              "testType": "tcpping",
              "ports": [
                80
              ]
            }
          ]
        }
      ],
      "remark": null
    }
  },
  {
    "taskId": "c4c9ad35047a4495a17d5f472607b2bf",
    "taskName": "test1",
    "sourceInterface": "eth0",
    "sourceIPAddress": "172.20.10.5",
    "templateId": "691ef0e83f1f4a667e0f750f",
    "taskCycle": "daily",
    "remark": null,
    "taskDateTime": "2025-11-28T20:25:00.000+00:00",
    "template": {
      "id": "691ef0e83f1f4a667e0f750f",
      "templateName": "test",
      "targets": [
        {
          "value": "1.1.1.1",
          "tests": [
            {
              "testType": "ping",
              "ports": []
            },
            {
              "testType": "tcpping",
              "ports": [
                80
              ]
            }
          ]
        }
      ],
      "remark": null
    }
  }

Verify the Last Probing Tool Report​

This command is used to view the last execution report for a specific task (e.g., test1). Replace test1 with the actual taskName if needed.

cat last_probing_tool_report_test1_request.json | jq

Example Response:​

{
  "deviceId": "69257f24b2a73a153e4f8edf",
  "deviceType": "CE",
  "startedAt": "2025-12-01T11:50:00",
  "taskId": "3f32bb726a2a46ee95c5bde183ebd905",
  "taskName": "test1",
  "targets": [
    {
      "value": "1.1.1.1",
      "tests": [
        {
          "testType": "ping",
          "executedAt": "2025-12-01T11:50:00",
          "result": {
            "output": "PING 1.1.1.1 (1.1.1.1): 56 data bytes\n64 bytes from 1.1.1.1: seq=0 ttl=53 time=74.582 ms\n\n--- 1.1.1.1 ping statistics ---\n1 packets transmitted, 1 packets received, 0% packet loss\nround-trip min/avg/max = 74.582/74.582/74.582 ms",
            "status": "success"
          }
        },
        {
          "testType": "tcpping",
          "executedAt": "2025-12-01T11:50:00",
          "port": 80,
          "result": {
            "output": "TCP PING 1.1.1.1 (1.1.1.1) tcp port 80\nBinding source interface: eth0\n1.1.1.1: seq=1 time=279.042 ms\n--- 1.1.1.1 tcp ping statistics ---\n1 pings, 1 success, 0 failed, 0.0% loss, total run time: 279.449 ms\nrtt min/ave/max/range/jitter = 279.042/279.042/279.042/0.000/0.000 ms",
            "status": "success"
          }
        }
      ]
    }
  ],
  "completedAt": "2025-12-01T11:50:00"
}
Q:1 How do I interpret the status field in test results?

The status field indicates the outcome of each probing test. Possible values: success → The test executed correctly, and connectivity was verified (e.g., ping reply received, TCP port open). failed → The test did not succeed, meaning connectivity issues, unreachable host, or blocked port. error → The test could not be executed due to misconfiguration or system-level problems. In the example provided, both ping and tcpping show "status": "success", confirming that the target (1.1.1.1) is reachable and responding as expected.

Q:2 What information is shown under targets?

The targets section provides details about the specific endpoints being tested: value → The target IP address or domain name (e.g., 1.1.1.1). tests → A list of diagnostic tests performed on the target, including: testType → The type of test (e.g., ping, tcpping, http, https). executedAt → Timestamp when the test was run. port (for TCP/HTTP/HTTPS tests) → The port number being checked (e.g., 80). result → Contains detailed output of the test (response times, packet loss, RTT statistics) and the status field showing success or failure. This section essentially maps which targets were tested, how they were tested, and what the results were, making it the core of the probing report.