Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > Network Performance Monitor (NPM) > NPM 12.2 Administrator Guide > Discover your network paths > Troubleshoot my network with Orion path data

Troubleshoot my network with Orion path data

Table of contents
No headers
Created by Caroline Juszczak, last modified by Magdalena.Markova on Nov 02, 2016

Views: 508 Votes: 0 Revisions: 5

You can use NetPath to diagnose a slow connection caused by your internal network. This example shows a node that stopped working properly after a change to its config file.

  1. Click My Dashboards > Network > NetPath Services.
  2. Expand the service that your users reported as slow or unreachable.
  3. Click the probe from the office or location that reported the issue.
  4. Under Path History, locate the date and time for when your users reported the issue. Here, there is a red critical entry at 3:26 p.m. on April 14.


  5. Click the red bar at 3:26 p.m. in the chart.
  6. The problem is in the internal network. There is a high latency between nodes R3 and R5.


  7. Point to the red connection between the two nodes to see that Transit Likelihood is 45%. This means that just under half of your users are likely to experience the problem.


  8. NCM is installed, so the Orion integration with NetPath displays information about a config change to node R5. Click the Config Change notification.


  9. In the config comparison window, scroll down until you see the highlighted change.


  10. A new command was added on line 78 for interface Ethernet1/0. This is the problem. Note the change, and close the config comparison window.
  11. Use NCM to revert the config file, or log in to the device and remove the incorrect configuration.
Last modified