Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > Network Performance Monitor (NPM) > Availability table: 100% availability in report but also 100% packet loss

Availability table: 100% availability in report but also 100% packet loss

Table of contents
Created by Dennis Harnett, last modified by Karen Valdellon on Apr 19, 2017

Views: 56 Votes: 0 Revisions: 5

Updated March 7, 2017


This article provides information on how the Availability table works.


NPM 11.5.3


By default, we poll every 120 seconds for availability. This is done with ICMP (Ping). If the node responds, it is marked as 100% available and the response time is stored. If the node does not respond, a fast ping is sent. This repeats according to the Response Time Retry Count value for your polling engine. This setting designates the number of times Orion retries ICMP pings on a monitored device before packet loss is reported. If the node responds to this, it is marked as 100% available and 100% packet loss to represent that it responded, but not to the main ICMP poll. The response time is not stored. 

If the node does not respond to any of the above, it will be marked as 100% loss and 0% available for that poll. As such it is possible to have 100% packet loss and 100% available. As ICMP is a low priority packet, the node may be too busy to respond to the poll but the node appears to be operating fine.



Last modified
22:41, 18 Apr 2017