Hide this message
Last Updated: 6-7-2016
NetPath allows you to discover and troubleshoot network paths hop-by-hop – not just the part of the network that you manage, but also nodes and links of your providers.
NTA 4.2 and NCM 7.4.1 are the minimum required versions to use the Orion integration features with NetPath.
In this scenario, Salesforce has been slow, and you want to analyze the path to find out where the problem is.
login.salesforce.com, and in the Port field, enter
Salesforceas the alias.
Probing frequency determines how often Orion discovers the path and measures the path's performance.
The Orion main poller includes a probe you can use, or you can add a probe to a Windows device.
It takes the system at least the probing interval to map the path.
Once NetPath maps the path, you can see your internal network, traversed segments of ISP network(s), and the destination network, plus the details and statuses of the objects on the route.
You can use the controls in the top left of the page to zoom in and out, and to control the level of detail shown. The path between SolarWinds’ Austin HQ and Salesforce shows the maximum level of detail.
NetPath monitors paths at regular intervals (the probing interval) and keeps historical data, which is shown in the Path History section at the bottom of the page. You can see in this example that the path is fine now, but was red a few intervals ago.
Click the red bar to see the path at that time.
Notice that the path is different during this time period than the current time. That’s normal. Paths can and do change over time.
If you look closely at the red object, you can see that it’s actually two objects.
Double-click on the object to expand it.
If you single-click on the individual device that’s causing the problem, the Object Inspector opens.
It looks like this device had high packet loss during this 10 minute time period, but the problem seems to be resolved. If you had caught this while it was happening, the information in the Object Inspector would allow you to contact the device’s owner and report the problem. And because NetPath keeps a history of each path, you can identify trends over time, and troubleshoot intermittent problems.