nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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
Store

Node warning level and when a Node is marked down

foleyjm

Question regarding node warning level and how soon a node is marked as down.

I am using the defaults of 120 seconds for polling and 120 seconds for Node Warning Level.

(the numbers on the left represent seconds after the first failed poll/ping)

From what I have read, the way things should work is:

000 - NPM Pings device, ping fails - node status is marked: Warning. Polling goes into fast polling mode for 120 seconds. I assume this is where it shows packet loss at 10%, 20%, 30%, etc...

010 - Fast polling ping #1

020 - Fast polling ping #2

030 - Fast polling ping #3

etc...

120 - After fast polling has completed - Node status is marked: Down.

What I'm seeing is:

000 - NPM Pings device, ping fails - node status is marked: Warning. Polling goes into fast polling mode for 120 seconds. I assume this is where it shows packet loss at 10%, 20%, 30%, etc...

010 - Fast polling ping #1

020 - Fast polling ping #2

030 - Fast polling ping #3

etc...

120 - Node still shows status Warning - packet loss is shown at 100%

240 - Node finally shows status Down.

Why is there an extra 120 second delay after fast polling is finished and when the node is marked as down?