[mrtg] Re: Need a hint on SNMP-Problem

[Brander, Eric]

You have the maxbytes setting too low for the humidity, so MRTG discarded
it.  Both maxbytes settings should be set to something higher, or else if
you do have a temp problem, you won't see it because MRTG will discard the
high numbers.

Another option would be to have your maxbytes set to what you think is an
"ideal" number, and then use a high AbsMax setting.  Then you could remove
the nopercent option and MRTG will chart what % it is off from nominal.  Its
nothing truly useful really, but kind of neat.  Try it, play with it...
playing with MRTG graphing helps to learn the program.  That's what I did. 

HTH

Eric

-----Original Message-----
From: Andre Timmermann [mailto:timmerma at ba-loerrach.de]
Sent: Monday, January 13, 2003 5:05 AM
To: mrtg at list.ee.ethz.ch
Subject: [mrtg] Need a hint on SNMP-Problem



Hello List,

I'm using mrtg-2.9.17, which comes with my debian.

I want to monitor some values coming from a rack monitorin system with snmp.
At first i need to track the temperatre and the humidity values delivered
by the sensors in the rms.

Here is the snmpget for the temperature:
# snmpget -v 1 -c public rms1 1.3.6.1.4.1.2769.10.4.1.1.3.1
SNMPv2-SMI::enterprises.2769.10.4.1.1.3.1 = INTEGER: 25

This is the snmpget for the humidity:
# snmpget -v 1 -c public rms1 1.3.6.1.4.1.2769.10.5.1.1.3.1
SNMPv2-SMI::enterprises.2769.10.5.1.1.3.1 = INTEGER: 35

So it seemes that snmp is working correctly.

I have put this in my config:

# temperature
Target[rms1_2]:
1.3.6.1.4.1.2769.10.4.1.1.3.1&1.3.6.1.4.1.2769.10.4.1.1.3.1:public at rms1:
MaxBytes[rms1_2]: 30
Unscaled[rms1_2]:  dwym
YLegend[rms1_2]:  Temp
Options[rms1_2]: gauge,nopercent,growright


# humidity
Target[rms1_3]:
1.3.6.1.4.1.2769.10.5.1.1.3.1&1.3.6.1.4.1.2769.10.5.1.1.3.1:public at rms1:
MaxBytes[rms1_3]: 30
Unscaled[rms1_3]:  dwym
YLegend[rms1_3]:  Hygro
Options[rms1_3]: gauge,growright

Now I get the data and graphs for the temperature, but not for the humidity.

The log for humidity shows:
# head rms1_3.log
1042453203 35 35
1042453203 0 0 0 0
1042452904 0 0 0 0
1042452900 0 0 0 0
1042452600 0 0 0 0
1042452300 0 0 0 0
1042452000 0 0 0 0
1042451700 0 0 0 0
1042451400 0 0 0 0
1042451100 0 0 0 0

So only the first line seemes to be updated, but I do not know why.

I have tried to use an external monitoring script to make shure, that mrtg
has no problem with the rms, but this did not help.

I just need a hint to find a solution, please ;o)

Greetz,
Andre Timmermann

--
Andre Timmermann
Berufsakademie Loerrach
Student Wirtschaftsinformatik


    \-^-/
    (o o)
ooO--(_)--Ooo-





--
Unsubscribe mailto:mrtg-request at list.ee.ethz.ch?subject=unsubscribe
Archive     http://www.ee.ethz.ch/~slist/mrtg
FAQ         http://faq.mrtg.org    Homepage     http://www.mrtg.org
WebAdmin    http://www.ee.ethz.ch/~slist/lsg2.cgi

--
Unsubscribe mailto:mrtg-request at list.ee.ethz.ch?subject=unsubscribe
Archive     http://www.ee.ethz.ch/~slist/mrtg
FAQ         http://faq.mrtg.org    Homepage     http://www.mrtg.org
WebAdmin    http://www.ee.ethz.ch/~slist/lsg2.cgi