Re: [squid-users] hel required for squid and mrtg to work

Pranoy Pradhan wrote:
>
> i tried to use port 3401 but i get the same output as i attached when i
> used snmpwalk -p 3401 ipaddress communitystring system
> regards pranoy

  First you need to ask, yourself, what you want to test
 using snmpwalk in the context of using squid with snmp and 'talking to'
 mib variables.

 Secondly you will need to specify the squid mib using the '-m' when
 using snmpwalk and then asking snmpwalk to tell something about squid
 related mib variables.

 This usually assumes that the squid mib has some relevant name
 and is in the 'path' where snmpwalk expects the location
 of mib file(s).

 M.

>
> On Tue, 13 May 2003, Marc Elsen wrote:
>
> >
> >
> > pranoy wrote:
> > >
> > > hi
> > > i want to use mrtg to monitor squid
> > > my squid is in one linux server and mrtg in another linux server
> > > settings in my squid.conf file
> > > snmp_port 161
> > > snmp_access allow snmppublic all
> > > settings in my /etc/services file in my squid
> > > snmp 161
> > > output when i user snmpwalk -p 161 ipaddressofsquid public system
> > >
> > > system.sysDescr.0 = "Linux snppoy 2.4.7-10 #1 Thu Sep 6 17:27:27 EDT
> > > 2001 i686"
> > > system.sysObjectID.0 = OID: enterprises.ucdavis.ucdSnmpAgent.linux
> > >....
> >
> >
> > You seem to be using the standard snmp port in squid.conf,
> > which in this case it 'occupied' by your system's snmp daemon.
> >
> > 1) Try using an other snmp port for squid , then 161.
> >
> > 2) When using mrtg check, error output for one run, or mrtg.log
> > file when in daemon mode
> >
> > M.
> >

-- 
 'Love is truth without any future.
 (M.E. 1997)