snmp errors generated by mrtg

Hi,

A short while ago, somebody posted reporting snmp errors generated by
mrtg while trying to monitor squid. I have had the similar sort of
errors from mrtg trying to monitor Squid 1.2.beta20. (I have deleted the
hostname and ip address from the sample error messages.)

SNMP Error:
Received SNMP response with error code
  error status: noSuchName
  index 2 (OID: 1.3.6.1.3.25.17.3.2.1.15)
SNMPv1_Session (remote host: "deleted" [deleted].3401
                  community: "public"
                 request ID: 89196578
                PDU bufsize: 8000 bytes
                    timeout: 2s
                    retries: 5
                    backoff: 1)
SNMPGET: Failed to reach target:
"cacheHttpMedianSvcFiveMin&cacheDNSMedianSvcFiveMin:public@deleted". I
tri
ed multiple times!
SNMP Error:
Received SNMP response with error code
  error status: noSuchName
  index 4 (OID: 1.3.6.1.2.1.1.5.0)
SNMPv1_Session (remote host: "deleted" [deleted].3401
                  community: "public"
                 request ID: 1528783534
                PDU bufsize: 8000 bytes
                    timeout: 2s
                    retries: 5
                    backoff: 1)
SNMPGET: Failed to reach target:
"cacheCpuUsage&cacheSysPageFaults:public@deleted". I tried multiple
times!

In the cache.log file, I found a message indicating that Squid is
accepting SNMP messages on port 3401 and a string of other entries which
may or may not be relevant, eg.:

1998/05/14 13:45:58| CACHEMGR: <unknown>@127.0.0.1 requesting
'utilization'
1998/05/14 13:46:00| CACHEMGR: <unknown>@127.0.0.1 requesting 'menu'
1998/05/14 13:46:07| CACHEMGR: <unknown>@127.0.0.1 requesting
'digest_stats'
1998/05/14 13:46:08| CACHEMGR: <unknown>@127.0.0.1 requesting 'menu'
1998/05/14 13:46:12| CACHEMGR: <unknown>@127.0.0.1 requesting 'counters'
1998/05/14 13:46:13| CACHEMGR: <unknown>@127.0.0.1 requesting 'menu'
1998/05/14 13:46:15| CACHEMGR: <unknown>@127.0.0.1 requesting 'io'
1998/05/14 13:46:16| CACHEMGR: <unknown>@127.0.0.1 requesting 'menu'
1998/05/14 13:46:18| CACHEMGR: <unknown>@127.0.0.1 requesting
'vm_objects'
1998/05/14 13:46:25| CACHEMGR: <unknown>@127.0.0.1 requesting 'menu'
1998/05/14 13:46:28| CACHEMGR: <unknown>@127.0.0.1 requesting 'ipcache'
1998/05/14 13:46:36| CACHEMGR: <unknown>@127.0.0.1 requesting 'menu'
1998/05/14 13:46:41| CACHEMGR: <unknown>@127.0.0.1 requesting 'objects'
1998/05/14 13:46:44| CACHEMGR: <unknown>@127.0.0.1 requesting 'menu'
1998/05/14 13:46:57| CACHEMGR: <unknown>@127.0.0.1 requesting 'dns'
1998/05/14 13:47:04| CACHEMGR: <unknown>@127.0.0.1 requesting 'menu'
1998/05/14 13:47:09| CACHEMGR: <unknown>@127.0.0.1 requesting
'fqdncache'
1998/05/14 13:47:11| CACHEMGR: <unknown>@127.0.0.1 requesting 'menu'
1998/05/14 13:47:54| CACHEMGR: <unknown>@127.0.0.1 requesting 'menu'
1998/05/14 13:47:57| CACHEMGR: <unknown>@127.0.0.1 requesting
'http_headers'
1998/05/14 13:48:05| CACHEMGR: <unknown>@127.0.0.1 requesting 'menu'
1998/05/14 13:48:23| CACHEMGR: <unknown>@127.0.0.1 requesting '60min'
1998/05/14 13:48:38| CACHEMGR: <unknown>@127.0.0.1 requesting 'menu'

Any ideas what causes the snmp errors? Have I missed something simple in
the configuration?

Thanks,
C Lau
Received on Thu May 14 1998 - 06:25:17 MDT