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

Last reboot time monitoring the SNMPD

I am using the Orion NPM LastBoot feature to monitor when our servers reboot.

This seems to work very well for our windows boxes, but I have just started monitoring a linux appliance and it has an interesting behaviour.

Every day it does a log refresh and during that process it restarts the SNMPD

This is what ORION monitors for the lastboot option.

so it appears the appliance is rebooting when it actually hasn't.

Has anyone else experienced this behaviour and have any idea how to resolve.

Our Orion is currently set to poll devices every 60 seconds so if a device reboots in this window it can miss it which has happened a lot.

So I setup the lasboot method but then we hit this issue.

Any advice from anyone on monitoring an appliance reboot effectivley?

Roger

Find more posts tagged with

Accepted answers

All comments

smargh

If a device reboots while Orion has it as "unmanaged", it won't alert for a reboot.

That's what I've found anyway. It might depend on whether you're using your own alert criterla - I use "lastboot changed", I think.

nding

dodgeyrog,

We look at sysUpTime to see if the value has changed - as what Smargh has indicated: LastBoot has changed

The following are some information in regards to the OID: http://tools.cisco.com/Support/SNMP/do/BrowseOID.do?local=en&translate=Translate&objectInput=sysUpTime

"The time (in hundredths of a second) since the
network management portion of the system was last
re-initialized."

And so, the restarting of the SNMP-agent actually cause the sysUpTime to change, thus causing the reboot alerts.

There were feature requests in place to update the OID that we are looking at to hrSystemUptime that will not change when the SNMP-agent restarts.

The following are more information in regards to hrSystemUptime: http://tools.cisco.com/Support/SNMP/do/BrowseOID.do?local=en&translate=Translate&objectInput=1.3.6.1.2.1.25.1.1

This is different as:

"The amount of time since this host was last
initialized. Note that this is different from
sysUpTime in the SNMPv2-MIB [RFC1907] because
sysUpTime is the uptime of the network management
portion of the system."

Hope that clarifies.

Dogeron

dodgeyrog and Andy NG,

I've had the same problems - any node that is *NIX based - Linux, Cisco, FreeBSD, et-al has this issue but Windows OS's don't.

It seems to me that Orion is polling OID 1.3.6.1.2.1.1.3 which work great for Windows devices but is (as we've found out) useless for *NIX's.

Orion needs to be changed so that the"Last Reboot" code tests for the OS and then polls the correct OID - 1.3.6.1.2.1.1.3 for Windows; 1.3.6.1.2.1.25.1.1 for *NIX's

There's a long thread here on the OpenNMS board that discusses what Windows is actually counting for this OID at some length so any code change to Orion would have to take the difference into account.

Best Wishes,

Dog