This method is checking if the SNMP service is running and since when.We have frequent errors on the SNMP-Service in Windows, so when you start the service after an error, NPM sees it as the node is rebooted, so the uptime is no longer correct. it shows 0 hours, and the server is up for 66days.There must be a counter in windows that counts uptime, in ticks, seconds, or another value, if you could use that reference for uptime instead of monitoring the SNMP-service it self would be great.It's strange that there is no correct answer on this forum although this is pretty important information of your servers.If anyone have suggestions, I would like to hear it!Thanks.
You are correct, Orion queries SNMP start values to determine uptime, which is faulty.
Do a search for a utility called UPTIME. You can put it in a batch file and write the resuluts to a test file. Or you could invest more time to dump the results to SQL.
This may provide you a more accure UPTIME result than ORION.
We marked this UPTIME issue as a flaw with ORION, but got back, that it is "function properly because we are pulling data from SNMP".
Hi Jussty,Thank you for your answer, I will test this, because uptime is important for us and strangely on a few servers SNMP keeps crashing.The most servers we are running are Dell servers, so I searched Dell in combination whit SNMP, and found someone that told me that "Dell Open Manage" is cousin this problem.. but we have a few HP servers as well, and thought that I had an error before whit a HP server.. So thats strange. So my thought on this is, that Orion is using SNMP at the same time as a different service, and that way this will generate an error. If the SNMP-service stays running, the uptime will be accurate enough. So knowing this my next question is.. Is there a way to control the exact polling time. So you can spread the load of the SNMP serice. Just a thought.. but hopefully it makes sense.. Thanks!