[mrtg] Re: Ongoing problem

[Webmaster]

Did you read the manual ???????????????????

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


Greetings Eric - Italy


-----Original Message-----
From: Darryl Kegg [mailto:Darryl.kegg at thehortongroup.com]
Sent: Wednesday, 11 September, 2002 23:38
To: mrtg at list.ee.ethz.ch
Subject: [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

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