Skip to main content
Version: v25.07.31

Diagnostics

This document gives a summary of the Diagnostics feature for Provider Edge (PE) devices. Although it works similarly to the diagnostics on Customer Edge (CE) devices, this guide focuses on the specific options and details available in the PE diagnostics menu.

The Diagnostics tool helps network administrators check connections and fix problems from the cloud using three easy-to-use tools: Ping, Traceroute, and NSLookup. It eliminates the need for complex commands on local devices.

Check the CE Diagnostics guide for all the step-by-step details. The same settings and steps apply whether working with a CE or a PE device.

Link to CE Diagnostics Documentation: CE Diagnostics Document


Key Concepts of PE Diagnostics

Below are the primary functions available in the PE Diagnostics tool:

ToolPurposeUse CaseAccess Path
PingTests connectivity and measures response time.Verify if a device or host is online.Login → PE Devices → Select PE Device → Diagnostics → Ping
TracerouteTracks the path of packets from source to destination.Identify network bottlenecks or points of failure.Login → PE Devices → Select PE Device → Diagnostics → Traceroute
NSLookupQueries DNS for domain-to-IP mapping.Confirm that a domain resolves to the correct IP.Login → PE Devices → Select PE Device → Diagnostics → NSLookup

Basic Process for Running Diagnostics

The general procedure for executing diagnostics on a PE device mirrors that of a CE device:

  • Accessing Diagnostics: Navigate to the Diagnostics tab within the PE device’s management.
  • Selecting a Tool: Choose Ping, Traceroute, or NSLookup from the dropdown menu.
  • Entering Input: Provide the required IP address or domain name depending on the selected tool.
  • Starting the Test: Click the Start button to initiate the diagnostic process.
  • Stopping the Test: Click the Stop button once sufficient results have been collected.

Important Notes for Users

  • Use Diagnostics for Troubleshooting Only:- These tools are designed to verify connectivity and identify issues. Avoid running continuous or unnecessary tests.
  • Ensure Correct Input:- Enter valid IP addresses and domain names to avoid false results or test failures.
  • Results Reflect Network Conditions at That Moment:- Latency or packet loss may vary depending on traffic and routing paths.
  • Permissions May Apply:- Only authorized users may access diagnostics for security reasons.
  • Does Not Modify Configuration:- Diagnostics are read-only tools and do not change device settings.
  • Use NSLookup for DNS-Related Issues Only:- If a domain does not resolve, verify DNS before checking routing.
  • Contact Support When Needed:- If diagnostics repeatedly show failure, escalate to your network administrator.