I don't think that it's 'My' problem, as others have seen the same thing. Since I've made the change, I no longer receive false up/down events from my Windows Boxes, the upTime is accurate instead of running away as it had been before. Previously in this thread I posted where I had rebooted several devices (Windows, Linux, Switches & Routers) all at the same times, and the Windows Boxes were the ones that were running away with the incorrect time.gilles wrote:i think NO don't touch that.streaker69 wrote:FOUND IT!mcutting wrote:Yes, which makes it inaccurate, which I have noticed before.
Read the info on the first image, then make the change from the second image. The wrong OID is being called resulting in the incorrect values for Windows boxes.
just look down in the code you post, there is the correct oid (MIB II).
if you launch manage from command line and it's outputting it use MIB, i think you have a problem.
to use MIB II, which is more accurate, use options (see my precedent post).
if you could confirm that...
To me, it seems to be more accurate and reliable than using the hrSystemUptime. I'd say, people are free to make the change or not based upon what they're seeing on their own systems. I just know what I found in my own results.