Submit a ticketCall us

Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.

 

Home > Success Center > Network Performance Monitor (NPM) > Network paths in NetPath end early

Network paths in NetPath end early

Created by Anthony.Rinaldi, last modified by MindTouch on Jun 23, 2016

Views: 93 Votes: 1 Revisions: 5

Updated June 21, 2016

Overview

Network paths in NetPath are short, and do not show Internet hops or the true destination. End-to-end latency is usually low.

Environment

  • NPM 12.0 and later

Cause 

NetPath discovers the path of a network conversation, from source to destination.

Some specialized network appliances, such as web proxies and WAN optimizers, intercept TCP conversations and act as the endpoint. For example, a web proxy may be placed in the transit path of end users going to websites.

Google example

The web proxy may intercept a web browsing connection from an end user to Google. Rather than forwarding to Google, the proxy may respond as if it was Google so the user gets a faster response. The web proxy will open a second, separate network conversation to Google to get the content the user requested.

Because the web proxy completes the TCP connection and directly communicates with the end user, it is the destination of the network conversation. This is why NetPath shows it as the destination, though often with a spoofed public IP address.

Resolution

Because the web proxy uses two network connections, you must follow these steps to correctly monitor the end-to-end path:

  1. Create a network path going from your end users to the web proxy.
  2. Add a new NetPath probe in the same network segment as your web proxy.
  3. Set the probe to monitor websites that your end users access.

 

 

 

Last modified
22:45, 22 Jun 2016

Tags

Classifications

Public