Submit a ticketCall us

Announcing NCM 7.7
With NCM 7.7, you can examine the rules that make up an access control list for a Cisco ASA device. Then you can apply filters to display only rules that meet the specified criteria, order the rules by line number or by the hit count, and much more.
See new features and improvements.

Home > Success Center > Network Performance Monitor (NPM) > 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: 668 Votes: 1 Revisions: 8

Overview

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

Environment

All NPM versions 

Cause 

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.

Resolution

  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. 
    http://downloads.solarwinds.com/sola...lset-v10.9.zip
    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
09:29, 25 Jul 2017

Tags

Classifications

Public