Re: mrtg and squid

>From: "Alan J. Flavell" <flavell@a5.ph.gla.ac.uk>
>To: carlos <carlos@vision.net.id>
>Subject: Re: mrtg and squid
>Date: Tue, 22 Dec 1998 3:39 AM
>

>On Mon, 21 Dec 1998, carlos wrote:
>
>> I Got Strange problem when invoking squid 2.1 SNMP
>> to MRTG 2.5.4c (with snmp parameter supported).
>
>> Target[squid]:
>> 1.3.6.1.4.1.3495.1.3.1.5&1.3.6.1.4.1.3495.1.3.1.5:public@IPnumber:3401::4
>..
>> Received SNMP response with error code
>> error status: noSuchName
>> index 3 (OID: 1.3.6.1.2.1.1.3.0)
>> ..
>
>You are trying to query the sysUpTime from port 3401, and squid's SNMP
>doesn't support that OID.
>
>As long as the platform where squid runs also has a normal SNMP
>port (161) active, you need the following configuration entry:
>
>routerUptime[squid]: public@IPnumber
>
>to tell MRTG to fetch the uptime and the system name from the normal
>SNMP port, instead of fetching it from port 3401 (squid). Check the
>MRTG docuemntation for details of this config entry.
>
>Of course, this will tell you the platform's uptime (i.e since last
>reboot) rather than the uptime of squid itself, but it seems to be the
>best one can do. If the platform isn't running the normal SNMP port,
>I suppose you could use "Options noinfo", although I haven't actually
>tried that myself.
>
>good luck
>

I had exactly the same problem. Doing the Router Uptime didn't seem to help
me because it came up with more errors. I don't understand how Alan has
used this system successfully & would really like to...

The way I fixed it was to apply the patch in the SNMP section of the home
page. This patch had 3 purposes (1) the ability to graph per hour or minute
(2) to change the default port to 3401 & (3) to supply the correct OIDs.

Purpose 1 worked great. Graphing HTTP hits vs all requests gives
interesting info sure enough.

Purpose 2 worked well too

Purpose 3 would have worked execpt the OIDs where not the same as in Squid
2. So I had to actually edit my copy of my patched MRTG to change the OIDs
to Squid 2s.

Then there was the other problem. The patch was made for MRTG 2.5.1 not
2.5.4c. Because my MRTG 2.5.4c was doing quite enough already anyway &
because the differences between what I wanted to monitor were so
wide-stretched, I decided to run both - MRTG 2.5.1 (patched & edited) &
2.5.4c as is.

I don't think it will be too long before someone posts a patch to support
Squid without editing. It would be my hope that those brilliantly talented
programmers would build squid support in by default!

Cheers, Marc Lucke
Received on Mon Dec 21 1998 - 15:44:53 MST