![]() Because the returned uptime value is given in hundreds of seconds (1/100), the maximum possible uptime that the sensor can display is 497 days (which is 4294967296 hundreds of seconds). This means that the maximum value that these counters can have is 2^32 (2 to the power of 32), which is the integer 4294967296. Wrong uptime values because of 32-bit countersīoth OIDs that the sensor can query for system uptime are 32-bit counters. There are two possible reasons for this: 1. However, in specific cases, PRTG reports an uptime that is lower than the real uptime of the monitored device. The sensor queries hrSystemUptime if available and uses sysUpTimeInstance as fallback, so the SNMP System Uptime sensor usually reports the correct uptime value. ![]() There are two possible OIDs to query uptime data from a device via SNMP: For a general introduction, see How do SNMP, MIBs, and OIDs work? For this purpose, PRTG queries the data from the device via the Simple Network Management Protocol (SNMP) and uses specific object identifiers (OIDs) to get the corresponding values. ![]() ![]() The SNMP System Uptime sensor monitors the time that a device runs. This article applies as of PRTG 22 Incorrect system uptime via SNMP ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |