Submit a ticketCall us

AnnouncementsTHWACKcamp 2018 is here

2018 is the seventh year for THWACKcamp™, and once again we’ll be live October 17 – 18 with packed session tracks covering everything from network monitoring and management, to change control, application management, storage, cloud and DevOps, security, automation, virtualization, mapping, logging, and more.

Register for online sessions.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > False Alert for packet loss from few Nodes

False Alert for packet loss from few Nodes

Created by Malik Haider, last modified by Matthew.Orr on Jul 25, 2017

Views: 3,944 Votes: 1 Revisions: 8


This article provides brief information and steps to resolve the issue when Orion sends false alerts for packet loss from few or some nodes. 


All NPM versions 


For some reasons, this could be an issue with the network layer/device itself. However, the below steps will further isolate the issue where we can use Engineer Toolset to find the root cause which is unknown at this stage.


  1. Install Engineer Toolset and start to monitor the effected node as below in order to isolate the issue further to compare the historical polling data . 
    Note: you can download the free version of the tool as below and install on multiple systems including Orion and monitor the Response Time from the effected Nodes.
    Install on the Orion server skip the license using evaluation version. 
  2. Go to Start > All Programs > Solarwinds Engineer's Toolset > Classic Tools > Network Monitoring >Network Performance Monitor 
    Or Ping & Diagnostics
  3. Change the same polling of effected Node in Orion NPM.
    Changing Fast ICMP Polling for Node. 
    a. Go to the Node Details Page on Orion Web Console 
    b. Click on Edit Node.
    c. Change the Node Status Polling "10" Second 
    ************** Monitoring ICMP Graphs **************

    Leave it running and compare the graph with NPM Orion once you have the false alert for the node . In this way, you can easily isolate the issue further if the node is not responding for the packets it should be reported same in the NPM and Toolset. 


Last modified