Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Node Status is Warning

Hi,

I have this issue which appeared to me recently. I have advanced email alerts set to alert me when a node goes down, i have the alert trigger condition to alert me if the node status is not up, so recently i started receiving many alerts stating that the node status is warning, while i know the node is down because i disconnected it. In the node details view it shows for example 80% or 90% packet loss, I dont know if it only reports the node down at 100% packet loss, but i dont like it that way.

I have the alerts go to the owners of the devices, and they dont understand what Warning means they always ask me about it, then they started losing credibility of the alerts.

I need to know the reason and why doesnt it report the node is down.

Find more posts tagged with

Accepted answers

mcbridea

Hello,

The NPM Admin Guide has a section on this. Here is the short answer from there. The longer version starts at page 101. Basically, the warning time is set of 120 seconds but you can change it if needed. The node will not be marked as down until the warning time expires.

Setting the Node Warning Interval

A device may drop packets or fail to respond to a poll for many reasons. Should the device fail to respond, the device status is changed from Up to Warning. On the Node Warning Interval tab, you specify how long it will remain in the Warning status before it is marked as Down. During the interval specified, the service performs "fast polling" to continually check the node status.

All comments

mcbridea

Hello,

Setting the Node Warning Interval

GoldTipu

Also here is some info on how warning Status Works:
**************************************************
Node warning Interval:

When devices stop responding or are simply dropping packings.
NPM will switch Node status from UP to WARNING.
If device does not respond within the Fast Polling Interval, The device Status is set as Down.

Fast polling interval is applied when a ping/snmp-query failed for the first time.

The default value for fast-polling is 120 seconds.

Fast Polling Interval is hard coded into the System,
and it does this every 10 seconds, for i.e. 120 seconds.

You can only change the DURATION of the Fast Polling,
by adjusting the setting in Advanced Settings, Node Warning Interval.
This changes the time period that Orion will Fast Poll until it marks the node down.

So if your Alert is to send an email if a Node goes Down,
it might have to be down for at least 2-3 minutes before Node is marked as down.
**************************************************

Setting the Node Warning Interval

Notes:

• To reduce the amount of packet loss reported by Orion NPM, configure the polling engine to retry ICMP pings a specific number of times before reporting packet loss. To do this, add the string value: “Response Time Retry Count” to the Windows Registry in the Settings folder of: HKEY_LOCAL_MACHINE/SOFTWARE/SolarWinds.Net/SWNetPerfMon/. Set the value data to the number of retries you prefer.

• You may see events or receive alerts for down nodes that are not actually down. This can be caused by intermittent packet loss on the network. Set the Node Warning Interval to a higher value to avoid these false notifications.