[ previous ] [ next ] [ threads ]
 
 From:  "Mitch \(WebCob\)" <mitch at webcob dot com>
 To:  waa dash m0n0wall at revpol dot com, m0n0wall at lists dot m0n0 dot ch
 Subject:  RE: [m0n0wall] m0n0wall v1.1, WRAP 1D1, SNMP sysUpTime.0 information incorrect
 Date:  Mon, 27 Sep 2004 09:01:54 -0700
I've got a guess for you.

The snmp is reporting timer ticks since boot. The old system Hz used to be
60 - the new system hz is 1000.

2.5 days * 1000 / 60 = 41 days

or thereabouts. Does that make sense?

m/

> -----Original Message-----
> From: William Arlofski [mailto:waa dash m0n0wall at revpol dot com]
> Sent: Monday, September 27, 2004 5:55 AM
> To: m0n0wall at lists dot m0n0 dot ch
> Subject: [m0n0wall] m0n0wall v1.1, WRAP 1D1, SNMP sysUpTime.0
> information incorrect
>
>
>
> I recently installed WRAP 1D1 board with m0n0wall v1.1, and noticed that
> the system uptime was incorrect when retreived  via SNMP. For instance,
> this system has really be up about 2 days. The Status-->System page in
> the webGui correctly shows:
>
> Name  	 fw.example.com
> Version 	1.1
> built on Sun Aug 22 11:41:15 CEST 2004
> Platform 	wrap
> Uptime 	2 days, 08:29
>
> Yet, an SNMPGET (which is what MRTG uses) incorrectly shows:
>
> $ snmpget -c public -v 2c 192.168.0.254 sysUpTime.0
> SNMPv2-MIB::sysUpTime.0 = Timeticks: (357526304) 41 days, 9:07:43.04
>
> So, my MRTG pages show that the system has been up 41 days, when in
> reality it has been up for 2 days 8 hours.
>
> I checked the list archives and the FAQ and found nothing specific
> relating to problems with this OID.
>
> A quick check using snmpwalk shows that these two OIDs also do not seem
> possible:
> ifLastChange.1 = Timeticks: (2055159851) 237 days, 20:46:38.51
> ifLastChange.2 = Timeticks: (0) 0:00:00.00
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
> For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch
>
>