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

Unmanage a node changes Last Boot time?

syncopix

Hello.

I've noticed that when a node is unmanaged the Last Boot time is changed.

Before the node is unmanaged:

After some time (maybe a poll interval?) the Last Boot gets changed:

(the node isn't actually rebooted and SNMP isn't restarted)

The node is then managed again and polled and the Last Boot goes back to how it was before it was unmanaged.

This then causes any alerts to trigger that make use of the "Last Boot has changed" event.

Is this by design or a bug? Seeing this in NPM 11.5. I hadn't noticed it with previous versions (not to say it wasn't there!).

Find more posts tagged with

Accepted answers

syncopix

I opened a support ticket. This is a known bug in NPM 11.5 and will be fixed in due course. For now the following workaround can be used to stop alerts from triggering when a node is unmanaged:

Change "Last Boot has changed" event in the trigger condition and set event filtering so that "New Last Boot Is Not Empty".

All comments

syncopix

I opened a support ticket. This is a known bug in NPM 11.5 and will be fixed in due course. For now the following workaround can be used to stop alerts from triggering when a node is unmanaged:

Change "Last Boot has changed" event in the trigger condition and set event filtering so that "New Last Boot Is Not Empty".

FormerMember

Hey syncopix‌,

Would you mind posting the ticket number? Thanks!

syncopix

maria.bungau‌, the ticket number was 775735. Hope this helps.