Search
Active

1
Sign in to vote
0
Sign in to vote
Sign in
to vote
Type: Bug
ID: 504908
Opened: 10/28/2009 2:15:35 AM
Access Restriction: Public
0
Workaround(s)
2
User(s) can reproduce this bug
With the SNMP service installed I obtained the following result with the Net-SNMP utility "snmpgetnext" for a system that had been booted 2071 seconds ago:

snmpgetnext -On -v2c -cpublic localhost hrSystemUptime
.1.3.6.1.2.1.25.1.1.0 = Timeticks: (2071328) 5:45:13.28

As you can see the reported value is in milliseconds while it should be in centiseconds: the SNMP service should return the value 207132 instead of 2071328.

This issue occurs at least on Windows XP and Windows 2003, and has been reported several times in public discussion forums. See e.g. http://fixunix.com/snmp/64367-re-interpreting-hrsystemuptime.html or http://forums.cacti.net/about22137.html&highlight=.
Details (expand)
What is your OneCare version?
(To check your build version; open Windows Live OneCare, in the upper right click Help, then select About Windows Live OneCare... Your version will be listed near the top).
I don't know or other
Operating System
Windows Server
Bug Type
Other
SubType
Other
How often does this happen?
Always Happens
Have you seen this problem before in this product?
Yes, this happens in all previous versions
Reproduction Steps
Install the Net-SNMP client tools (not the agent), open a command prompt and run the following command:

snmpgetnext -On -v2c -cpublic localhost hrSystemUptime
Expected Results
System uptime in centiseconds instead of milliseconds.

A quote from RFC 1213 (http://www.ietf.org/rfc/rfc1213.txt):
sysUpTime OBJECT-TYPE
SYNTAX TimeTicks
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The time (in hundredths of a second) since the
network management portion of the system was last
re-initialized."

A quote from http://msdn.microsoft.com/en-us/library/aa915261.aspx:
hrSystemUptime, TimeTicks, R/W, Time since the host was initialized last (1/100 sec).
File Attachments
0 attachments
Sign in to post a comment.