On 16 Jun 2020, at 23:40, Brian Chernish wrote:
C:\Windows\system32>snmpwalk -v1 -c public 10.100.214.3
.1.3.6.1.4.1.9.9.13.1.3.1.3
SNMPv2-SMI::enterprises.9.9.13.1.3.1.3.1005 = Gauge32: 45
(This should be the actual temperature and 45C seems about what I
would expect)
C:\Windows\system32>snmpwalk -v1 -c public 10.100.214.3
.1.3.6.1.4.1.9.9.13.1.3.1.4
SNMPv2-SMI::enterprises.9.9.13.1.3.1.4.1005 = INTEGER: 68
(This should be the temperature threshold)
That's encouraging. I notice that the configuration you originally
posted referred
to a different pair of OIDs:
Target[10.100.214.3]:
1.3.6.1.2.1.2.2.1.14.1&1.3.6.1.2.1.2.2.1.20.1:[email protected]
and that the one in your latest post uses the same OIDs as you used with
snmpwalk.
I wonder whether you are still seeing the -1 values in the log file
since making
this correction.
If I recall correctly (and I'm not sure that I do), loading the MIB is
for convenience
rather than function; it allows reference to an OID by name rather than
by dotted tuple.
If I'm mistaken, I hope someone else on the list will put me right.
In any case, if you wish to load non-default MIBs, you just need to
refer to the
relevant files in the global 'LoadMIBs' option. I'm not familiar with
Windows, so
can't suggest where the 'natural' place in your file hierarchy for these
files
might be.
Each of the graphs is generated independently and scaled according to
the range of
values actually present; the MaxBytes parameter isn't taken into
account.
Niall
_______________________________________________
mrtg mailing list
[email protected]
https://lists.oetiker.ch/cgi-bin/listinfo/mrtg
