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

False Device Reboots

Can anyone assist with a little issue that I'm having with Orion 7.4

Currently I get alarms such as

device.domain.net rebooted at 9/2/2004 17:27

I get maybe 10 of these a day with devices ranging from Cisco 806's to Cisco 3550s to Juniper M10 routers. Most have uptimes over a year.

None of these devices are actually resetting or losing connectivity.

1. How does Orion determine that a device has rebooted?

2. How do I resolve this?

Thanks!

Find more posts tagged with

Accepted answers

All comments

iunderwo

The SysUpTime counter is a 32-bit counter, so it will register a reboot every time that counter rolls over...and that's not too far over a year AFAIK.

// Ian Underwood - Service Management
// Level 3 Communications

clerum

So I'm being punished for my stable network....

Perfect!

64 bit counters? Will that help (Cisco/Juniper)

clerum

Actually....

10/4/2004 08:37 XXXXXX.domain.net rebooted at 7/9/2004 18:53

Why is it throwing an alert for a reboot, 3 months ago...

XXXXX-2611XM uptime is 12 weeks, 3 days, 1 hour, 47 minutes
System returned to ROM by power-on
System restarted at 18:49:08 MDT Fri Jul 9 2004

I'm opening up a ticket on this...I'll let you all know.

bleearg13

I am experiencing this same problem with Win2K Server and 7.4. This started happening only after an upgrade to 7.2 and beyond. Please let me know if you get a decent answer to this. This issue is more than a little annoying.

clerum

Offical Word from SolarWinds....sounds like they are ontop of it.

"We have seen similar issues where devices have issues with the SysUptime counter MIB. Basically the counter will be increasing (like it should) and then decrease for a value or two and then begin increasing again. The Orion software sees the decrease as a reboot because the counter should never decrease unless the device rebooted or the counters have been reset. The development team has developed a workaround to these devices’ MIB issue, and the new Orion release is currently in Beta."