Paulo Matos wrote:
> hno> (-Cc is due to a minor bug in Squid on these tables)
> Don't have Cc flag on snmpwalk...
>
> -C <APPOPTS> Toggle various application specific behaviour:
> APPOPTS values:
> p: Print the number of variables found.
> i: Include the requested OID in the search range.
Then you probably don't need it... this option is to disable a check added in
later versions of the snmp package..
My manual says
-Cc Don't Check whether the returned OID's are increas
ing. Some agents (LaserJets are an example)
returns OID's out of order, but can complete the
walk anyway. Other agent's return OIDs that are
[...]
>
> hno>
> enterprises.nlanr.squid.cacheMesh.cacheClientTable.cacheClientEntry.cacheCl
>ientHttpRequests hno> is the OID .1.3.6.1.4.1.3495.1.5.2.1.2
>
> Got the same result!!
> Yes I do have clients accessing squid (looking at access.log), or
> through cacheProtoClientHttpRequests
At least works here using Squid-HEAD (2.6), but I have a small memory of
toying with the cacheClientTable counters in Squid-2.4 as well...
> enterprises.nlanr.squid.cachePerf.cacheProtoStats.cacheProtoAggregateStats.
>cacheProtoClientHttpRequests = Counter32: 1782912
>
> Can't understand this...
Why you don't get any responses from the cacheClientTable, or the relation to
cacheProtoClientHttpRequests?
Regards
Henrik
Received on Fri Jun 07 2002 - 12:10:52 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:08:30 MST