Submit a ticketCall us

Announcing NPM 12.2
With NPM 12.2 you can monitor your Cisco ASA firewalls, to monitor VPN tunnels for basic visibility and troubleshooting tunnels. NPM 12.2 also uses the SolarWinds Orion Installer so you can easily install and upgrade one or more Orion Platform products simultaneously.
See new features and improvements.

Home > Success Center > Network Performance Monitor (NPM) > NetPath graph issue: Missing Internet nodes when connection reaches endpoint

NetPath graph issue: Missing Internet nodes when connection reaches endpoint

Created by Anthony.Rinaldi_ret, last modified by Anthony.Rinaldi_ret on Jan 04, 2017

Views: 70 Votes: 1 Revisions: 8

Updated December 8, 2016

Overview

The NetPath graph seems to be missing Internet nodes.

The NetPath graph has no timeout nodes, but many intermediate nodes are missing. For the external endpoint, the traces jump directly from an internal node to the endpoint without any nodes from ISP networks.

Environment

  • NPM 12.0 and later

Resolution

Step 1: Check the number of nodes between the NetPath probe and the endpoint

How many nodes are there?

Step 2: Check if the NetPath probe is running on VirtualBox with NAT enabled

  1. Open VirtualBox if the NetPath probe is running there.
  2. Click Settings > Network.
  3. Click the tab of the outgoing adapter, and check the value of the dropdown labeled Attached to.

    8-virtualbox.png

Is the NetPath probe running on VirtualBox with NAT enabled?

  • Yes: This is a known limitation due to VirtualBox resetting the TTL of outgoing packets. To work around this, change to a Bridged Adapter in Settings > Network.
  • No: Go to step 3.

Step 3: Check the NetPath graph for the same endpoint but non-web traffic

  1. Create a new service for the same endpoint on the same NetPath probe, but with the following settings:
    • Five-minute interval
    • A well-known non-web port, such as 25 or 53 (It is OK if those ports are not open on the endpoint)
  2. Wait 5 - 10 minutes, and then check the graph.
  3. Check if the graph contain external nodes, or if it has the same problem without any external nodes.

Does the graph contain external nodes?

Step 4: Recheck the probe and endpoint distance from step 1

Is the distance less than or equal to one?

Step 5: Check if the next node gateway has proxy or WAN optimizer enabled

  1. Do you have access to the default gateway configuration?
    • Yes: Check if the proxy or WAN optimizer is enabled.
    • No: Skip to the next step.
  2. Run a Trace Route from the NetPath probe to the endpoint, and count the number of response nodes. Check if there is more than one response node.

Is the proxy or WAN optimizer enabled?

Last modified
16:40, 4 Jan 2017

Tags

Classifications

Public