Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > 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 Kevin Twomey on Jun 25, 2018

Views: 606 Votes: 1 Revisions: 6

Updated March 7, 2017

Overview

This article provides information on how the Availability table works.

Environment

NPM 11.5.3

Detail

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 the fast ping, 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% availability.

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

Tags

Classifications

Public