Device Connectivity Data and Tests Results

To access the Connectivity accordion, navigate to the Observability > Health > Troubleshoot Devices page. Click a device name to access the Device-Name page. Click the Connectivity (accordion) in the Overview tab.

The connectivity accordion on the Device-Name page displays the health of connections from a device in your network to a remote device. The accordion displays the overall status of the device connections at the top-right corner. The status displays Urgent Action Needed if critical events occur within the last seven days or Healthy if no connection issues are detected. You can view connection-specific details when you expand the accordion. You have the flexibility to configure automated connectivity tests when you plan device onboarding or use the Retest button in the connectivity accordion to run connectivity tests after onboarding devices. You can run the tests on all connections (ports) of devices or select connections on which you want to run the test.

After the tests are complete, you can view the results of these tests as links in the Connectivity accordion on the Device-Name page. Table 2 describes the fields in the Connectivity accordion.

Click the health status links for a connection to view details about the faulty connections on the Connectivity Details Page. On the Connectivity Details page, you can rerun tests for specific or all remote endpoints after you resolve the connectivity issues.

The following list explains terms associated with connectivity tests:

• Metrics—Metrics such as delay, delay variance, HTTP timeout, ping (packet) loss, and round trip time (RTT) enable Routing Director to collect quantitative measurements to evaluate the quality of a connection.

• Protocols—Protocols such as HTTP, ping, and DNS are used to measure the metrics in a connectivity test. Ping is used to test connectivity from a device in your network to neighboring devices, edge devices, and known hosts in the cloud provider's network. HTTP and DNS protocols are used to test connectivity to Internet endpoints such as DNS service, HTTP service, or other web services.

• Types of remote endpoints—Types of remote devices to which test agents check connectivity. Remote endpoints can be neighboring devices, edge devices, Internet endpoints (DNS servers or web servers), and devices (external hosts) in the cloud.

• Connection—Connections are unidirectional flows of synthetic traffic from a test agent installed on a device to a test agent on another device, from a test agent to a reflector (BGP peering), or from a test agent to an external host in a public cloud. A connectivity test to a remote endpoint, such as neighboring devices, include multiple connections. Depending on the remote endpoint, each connection uses a protocol (such as ping) to check for select metrics (such as RTT). If a single connection (unidirectional traffic flow) experiences issues, the test fails.

• Test Result—Test Results are shown as timeline graphs of multiple key performance indicators (KPIs)—such as error seconds, response time, and packet loss—that indicate the health of a connection type. The KPIs are calculated based on the metric data collected for delay, delay variance, ping packet loss, round trip time, HTTP/ping response time, and HTTP timeout.

Note:

Connectivity tests are not supported on third-party devices. As a result, the connectivity test results for third-party devices are not available on the Overview Tab.

Table 1: View Connectivity Information

Connection	Description
Neighbors	Neighbors are routers that use dynamic routing protocols to discover each other in a network topology. Neighbors can use multicast messages or unicast messages depending on the network configuration. Displays the number of neighboring devices connected to the device and the health of their connection (healthy or unhealthy) to the device.
Edges	Edge devices are devices at the perimeter that connect your network to another network. An edge device can be peering devices in your local network, an Internet Gateway, a customer edge (CE) or a provider edge (PE) device, an area border router (ABR), or an autonomous system border router (ASBR). Displays the number of edge devices (routers) connected to the device and the health of their connection (healthy or unhealthy) to the device.
Internet Endpoints	Endpoints are URLs that locate a service that is hosted on a remote server. Examples of services are HTTP service, DNS service, or other web services that you want to access. Displays the number of Internet endpoints (servers) and the health of their connection (healthy or unhealthy) to the device.
Cloud Providers	If you enable connectivity tests to public cloud providers in a device profile, test agents initiate a connectivity test from the device to known hosts in a public cloud provider's network. Displays the number of regions to which connectivity tests are initiated for Amazon Web Services, Google Cloud Platform, and Microsoft Azure. View the status of the connectivity (healthy or unhealthy) from the cloud host to the device.
Relevant Events	You can access events of varying severity that are generated for the tests within the last seven days. Click Details to view the device name, test description, and start time and end time of the tests. Click View All Relevant Events to open the Events for Device-Name page that displays all events generated for different connections from the device. The Events for Device-Name page contains the following information: Severity—Displays Informational events for tests that pass and Critical events for tests that fail. Time Stamp—Displays the date and time when test agents initiate the test. Type—Displays the event type as Active Assurance. Description—Specifies the test protocol, remote endpoint, and result of the test.
Retest	To re-run connectivity tests, click Retest and select All Connections if you want Routing Director to re-run connectivity tests on all the connections.

To access the Connectivity accordion, navigate to the Observability > Health > Troubleshoot Devices page. Click a device name to access the Device-Name page. Click the Connectivity (accordion) in the Overview tab. Click any hyperlink in the accordion and you are directed to the Connectivity Details page.

The Connectivity Details page contains the following sections:

• Relevant Events—After completing connectivity tests, Routing Director generates Critical and Information events for connectivity tests and bad cables. An Informational event denotes that the test passed, and a critical event denotes that the test failed. Click View all Relevant Events to view events triggered for all tests to the device's connections.

• Refresh—Routing Director automatically refreshes the data every 10 minutes and displays the time for the upcoming round of connectivity data refresh. Alternatively, click the Refresh icon to refresh the connectivity data for the device connections.

• Show Connections Between—Displays the category of remote endpoint (such as edge devices, neighboring devices, and cloud providers), and the number of devices in each remote endpoint category.

  Enable the toggle button corresponding to a connection type to view the health of the connection in the topology view.

• Connections Between Devices—Displays a topology view of all connections from a device. For a remote endpoint, the topology view shows a single line that represents all connections from a device to multiple remote devices. You can perform the following tasks that are related to connections:

  • Access details of faulty connections on the topology map—After the connectivity tests are run on the onboarded device, the topology view displays the count of faulty connections. Faulty connections appear as red icons on the lines that indicate the connections. You can hover your cursor over the count icon to obtain details of the faults for a connection type.

  • Run connectivity tests—To re-run connectivity tests, click Retest and select All Connections if you want Routing Director to re-run connectivity tests on all the connections. Alternatively, you can select a specific connection (Neighbors, Edges, Internet Endpoints, or Cloud Providers) to which you want to re-run the test from the device.

    After the test is complete, the topology view is automatically updated. In addition, the Connections table below the topology view displays the updated information.

    To view additional details (such as a detailed view of the logs raised for events, errors, protocols used, and so on) of a test, click the details icon that appears when you hover your hover over the time range of the test.

• Connections—Displays a table with details about the connectivity tests run on the device. Table 2 describes the fields you see in the Connections table.

Table 2: Fields in the Connections Table

Field	Description
Status	Displays the status of the connection: Scheduled—Displays SCHEDULED when a test agent is scheduled to trigger a connectivity test. Running—Displays RUNNING when a test agent runs a connectivity test. Waiting—Displays WAITING when the test agent is not ready for performing a test. For example, a user triggers a test but when the test agent is not available or offline, Routing Director displays WAITING until the default maximum timeout duration of 300 seconds and then displays the ERROR status. Error—Displays ERROR when the test agent does not trigger a test connection. For example, when an interface goes down or the test agent goes offline, Routing Director displays the ERROR status. Hover over the error status to see the cause of the error. Failed—Displays FAILED when an HTTP or ping connectivity test fails. The FAILED status is caused by test metrics such as delay, delay variance, or packet loss exceeding the threshold for a connection. Passed—Displays PASSED if all connections to a remote endpoint is healthy (no errors or failures).
Test Time Range	Displays the date and time range when a test is executed. The date is displayed in the DD/MM/YYYY format and the time as Minutes:Seconds, with the time zone.
Source	Displays the name of the device from which the synthetic traffic is sent.
Source Interface	Displays the name of the interface on the source device from which the synthetic traffic is sent.
Destination	Name of the cloud provider and the region you previously configured for the connectivity test.
Remote End Point	Displays the name or management IP address of the remote device to which Routing Director initiates a connectivity test, along with its management interface name. Example: Device-name:10.1.1.1
Logs	Displays the number of logs generated for the connection from the device.
Protocol	Displays the protocol used for the test connection initiated by the test agent, such as HTTP, DNS, or Ping.
Type	Displays the type of remote endpoint to which the test agent initiates the connectivity test. For example, Internet Endpoints DNS, Cloud Endpoints Reachability, Edge Reachability, or Neighbor reachability.