[mrtg] Antwort: Ongoing problem

[Stefan.Heins at seb.de]

Hi Darryl,
I don't know what the problem is but you can try to change your timeout and
the retries of the SNMP.
This is taken from the reference.html from MRTG\doc.

Cheers
Stefan
SnmpOptions


Apart form the per target timeout options, you can also configure the
behaviour of the snmpget process on a more profound level. SnmpOptions
accepts a hash of options. The following options are currently supported:


 timeout                   => $default_timeout,
 retries                   => $default_retries,
 backoff                   => $default_backoff,
 default_max_repetitions   => $max_repetitions,
 lenient_source_port_matching => 0,
 lenient_source_address_matching => 1


The values behind the options indicate the current default value. Note that
these settings OVERRIDE the per target timeout settings.


Example:


SnmpOptions: retries => 2, only_ip_address_matching => 0


Note that AS/400 snmp seems to be broken in a way which prevents mrtg from
working with it unless


 SnmpOptions: lenient_source_port_matching => 1


is set.






Darryl Kegg <Darryl.kegg at thehortongroup.com>@list.ee.ethz.ch am 11.09.2002
23:38:20

Gesendet von:  mrtg-bounce at list.ee.ethz.ch


An:   mrtg at list.ee.ethz.ch
Kopie:     (Blindkopie: Stefan Heins/501174/Zentrale/SEB-AG)

Thema:    [mrtg] Ongoing problem

I know I've posted this before, but I am going crazy...



Regardless of the PC I run MRTG on I have sporadic problems trying to graph
a series of Dell PowerConnect switches.  Things will hum along nicely for
days / weeks and suddenly I'll start getting the following error...



SNMP Error:

no response received

SNMPv1_Session (remote host: "137.2.120.2" [137.2.120.2].161)

               community: "public"

              request ID: -747181493

              PDU bufsize: 8000 bytes

                 timeout: 2s

                 retries: 5

                 backoff: 1)

SNMPGET Problem for ifInOctets.1 ifOutOctets.1 sysUptime sysName on
public at 137.2.120.2:

WARNING: skipping because at least the query for ifInOctets.1 on
137.2.120.2 did not succeed



          Stopping MRTG and restarting it several times in a row sometimes
fixes the problem, other times I have to wait a day or so and then it will
work, but obviously having big gaps in my graphs isn't very useful.



          Is it possible the switches are just getting overloaded and
can't respond to MRTG in time?  Is there a way to increase the timeout
threshold for MRTG so it will wait a bit longer or retry the SNMP get?  I
see the timeout and retries on the error, how do I bump these up?  Or am I
way off base here.





--
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

Mit freundlichem Gruß / best regards / med vänlig hälsning
Stefan Heins
Fone: +49 69 258 9008
Fax:    +49 69 258 8979
SEB IT Service - Network/Internet
---------------------------------------
http://inet.seb.de/nmgmt
---------------------------------------



--
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