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

OID used by NPM to determine system has rebooted?

What OID is polled by NPM to determine that a Windows server (or any other device type) has rebooted? Is it 1.3.6.1.2.1.25.1.1?

Find more posts tagged with

Accepted answers

RichardLetts

It should be TimeTicks (CentiSeconds), at least that is what the MIB says it should be:

Object	hrSystemUptime
OID	1.3.6.1.2.1.25.1.1
Type	TimeTicks
Permission	read-only
Status	current
MIB	HOST-RESOURCES-MIB
Description	"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."

I'm unsurprised by software writers being unable to interpret MIBS correctly: if your system returns it in thousands of a second adjust accordingly (and file a bug-report with the vendor).

All comments

RichardLetts

yes.

Use the following alerts and UnDP if you want to use the HOST-RESOURCES MIB variables instead (which indicate the ACTUAL system reboot, rather simply the restart of the SNMP agent)

hrSystemReboot.AlertDefinition

/RjL

borgan

Thank you Richard. One question please. The second trigger condition is "Rate is less than 60000". What exactly does that mean?

RichardLetts

60,000 centiseconds [the standard time unit in SNMP for some strange reason, quite why they didn't pick a standard SI prefix is beyond me]

Anyway 600 seconds or 10 minutes: has the node rebooted in the last 10 minutes.

/RjL

borgan

Yes, and I then tested the OID against a server I rebooted manually. The funny thing is, the number does not make sense unless you calculate a "time tick" as 1/1000 of a second, rather than 1/100. In other words, if I test the OID every 5 seconds and look at the output, it is definitely coming back in thousandths of a second.