Re: Squid & MRTG possible?

> > You need to patch MRTG to get the data from the correct SNMP port for
> > Squid 2.0.
>
> No, you don't need to patch it: you need to get the current version of
> MRTG, and use its facilities for specifying the SNMP port in your
> configuration file. That way, you can have different SNMP port
> numbers for different plots (9161 for mrouted, for example ;-)
>
        Matija was refering to the latest version of MRTG. Those patches
are designed for 2.5.4. Which allow you to specify a port number, it also
changes the default to 3401. However the important part of that patch is
the perminute and perhour patches of Kostas. In this case it seems that
the port number has nothing to do with the error.

        You will need to change the entries for sysName/sysUptime to get
this to work. When MRTG first accesses a device it requires those two
entries as the error below points out:

        error status: noSuchName
    index 3 (OID: 1.3.6.1.2.1.1.3.0)

        Squid does not respond for system group OID's so MRTG can not run.
If you change these then you will have trouble monitoring any other
devices. Of course you can always change them back after the first run.

%snmpget::OIDS =
  ('sysDescr' => '1.3.6.1.2.1.1.1.0',
   'sysContact' => '1.3.6.1.2.1.1.4.0',
   'sysName' => '1.3.6.1.4.1.3495.1.2.1',
   'sysLocation' => '1.3.6.1.2.1.1.6.0',
   'sysUptime' => '1.3.6.1.4.1.3495.1.1.3',
   'ifNumber' => '1.3.6.1.2.1.2.1.0',
   ###################################

SNMP Error:
  Received SNMP response with error code
    error status: noSuchName
    index 3 (OID: 1.3.6.1.2.1.1.3.0)
  SNMPv1_Session (remote host: "proxy.euronet.be" [195.74.193.21].161

glenn
Received on Tue Nov 17 1998 - 12:24:07 MST