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

After a power outage, nodes are marked as down which are up.

After a power outage, nodes are marked as down which are up. This has happened in the past and it took NPM several hours to catch up. Interestingly, the Alerts view only shows 6 nodes down (which are up) while the All Nodes widget shows about 70 devices still down. I can click the Poll Now button on each device individually and it polls successfully but the device still shows down.

Where do I need to look to debug this?

Find more posts tagged with

Accepted answers

All comments

mcbridea

The up/down status is determined by ping. Can you ping from the NPM server to any of these devices?

FunkBuddha

Yes. At the time I could ping them from NPM.

After about 5 hours they were all green again.

mcbridea

Wow - that's a long time. Have you looked at the polling completion rates? If they are low then the server could be overtaxed. How many elements do you monitor?

FunkBuddha

I think we're on to something. I'm monitoring 2800 elements. My max status polls per second is set at 30 and I imagine this is what is backing up. What are the consequences of increasing that number? My Avg. CPU on my polling engine is around 30%.