Submit a ticketCall us

AnnouncementsAre You “Flying Blind?”

When it comes to your complex IT infrastructure, you want to ensure you have a good grasp of what’s going on to avoid any fire drills that result from guesswork. Read our white paper to learn how proactively monitoring your IT environment can help your organization while giving you peace of mind.

Get your free white paper.

Home > Success Center > Network Automation Manager > Network Automation Manager Installation Guide > Requirements > Optional requirements > NetPath requirements

NetPath requirements

Created by Caroline Juszczak, last modified by Magdalena.Markova on Jun 22, 2018

Views: 2,673 Votes: 0 Revisions: 4

Probe computer

Probes are the source of network paths, and the paths are discovered by probes.

You create a probe on a source computer, which must meet the following requirements:

Type Requirements

Operating system

(64-bit only)

Windows Server 2008 R2 SP1

Windows Server 2012

Windows Server 2012 R2

Windows Server 2016

Windows 7

Windows 8

Windows 8.1

Windows 10 Professional and Enterprise

Windows 10 Home edition is not supported.

CPU cores

2 CPU cores for 20 paths

+1 CPU core per 10 additional paths

Hard drive space 1 GB


Open the following ports on your firewall for network connectivity used by NetPath™:

Port Protocol Source Destination Description


(ICMP Time Exceeded)

ICMP Networking devices along your path NetPath™ probe Used by the NetPath™ probe to discover network paths.
User configured TCP NetPath™ probe Endpoint service

Any ports of the monitored services that are assigned to the probe.

Used by the NetPath™ probe to discover service status.

43 TCP Main polling engine BGP data providers Used by NetPath™ to query IP ownership and other information about the discovered IP addresses.

Database storage

When calculating the size requirements in SQL Server for NetPath™, you must account for the probing interval and the complexity of the network path from the probe to the monitored service. The complexity of the path is divided into three groups:

  • Internal: services with fewer than 10 hops between the probe and the monitored service.
  • Intermediate: multiple paths ending in a single endpoint node. Examples are,, and
  • Complex: multiple paths (over 20) ending in multiple endpoint nodes. Examples are and

This table provides an estimate in megabytes (MB) of the amount of storage consumed by SQL Server over a 30-day period (the default retention time) when monitoring a single service.

Interval (in minutes) Internal (in MB) Intermediate (in MB) Complex (in MB)
1 520 1105 1615
2 325 645 1145
3 200 445 915
4 170 350 750
5 135 265 480
10 80 175 470

Example storage requirement calculation

Your monitoring setup contains the following:

  • Five internal monitors with a one-minute interval.
  • Three intermediate monitors with a five-minute interval.
  • Four complex monitors with a ten-minute interval.

The total storage requirement for SQL Server can be calculated as:

(5 × 520) + (3 × 265) + (4 × 470) = 5275 MB over a 30-day time period.

Cloud environment

When you place a probe in a public cloud, consider the following additional requirements:

Provider Requirements
  • Security group must be enabled on instances that host NetPath™ probes to allow inbound ICMP packets.
  • Probing services that host on Amazon Web Services (AWS) instances within the same cloud networks may not work.
  • Private Internet Protocol (PIP) must be enabled on instances that host NetPath™ probes.
  • Probing may work within VNET, but may not work if the path crosses the Azure Load Balancer.


The scalability of NetPath™ depends on the complexity of the paths you are monitoring, and the interval at which you are monitoring them.

In most network environments:

  • You can add up to 100 paths per polling engine.
  • You can add 10 - 20 paths per probe.

    NetPath™ calculates the recommended path count based on the performance of each probe, and displays it each time you deploy a new path to the probe.

Last modified