Use the "-Cc" switch to snmpwalk the whole Squid SNMP address space.
>From the man page: -Cc Don't Check whether the returned OID's are increasing. 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 out of order and can cause snmpwalk to loop infinitely until stopped. By default, snmpwalk tries to detect this behavior and warns you when it hits an agent acting illegally. Use -Cc to turn off this behavior. It's not a cause for concern, and you aren't missing much. Chris -----Original Message----- From: John Hardin [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 23, 2004 2:02 PM To: [EMAIL PROTECTED] Subject: [squid-users] snmpwalk gets "OID not increasing" error I'm running 2.5.STABLE4 and get the following "OID not increasing" error when I do an snmpwalk of the Squid MIB. The agent code appears to list the 127.0.0.1 first, regardless of the IP address of the server. If your server IP address starts with something < 127 you will get this error: . . . SQUID-MIB::cachePeerState.127.0.0.1 = INTEGER: 1 SQUID-MIB::cachePeerPingsSent.127.0.0.1 = Counter32: 0 SQUID-MIB::cachePeerPingsAcked.127.0.0.1 = Counter32: 0 SQUID-MIB::cachePeerFetches.127.0.0.1 = Counter32: 0 SQUID-MIB::cachePeerRtt.127.0.0.1 = INTEGER: 0 SQUID-MIB::cachePeerIgnored.127.0.0.1 = Counter32: 0 SQUID-MIB::cachePeerKeepAlSent.127.0.0.1 = Counter32: 0 SQUID-MIB::cachePeerKeepAlRecv.127.0.0.1 = Counter32: 0 SQUID-MIB::cacheClientAddr.127.0.0.1 = IpAddress: 127.0.0.1 SQUID-MIB::cacheClientAddr.10.1.0.39 = IpAddress: 10.1.0.39 Error: OID not increasing: SQUID-MIB::cacheClientAddr.127.0.0.1 >= SQUID-MIB::cacheClientAddr.10.1.0.39 Anyone know if this is a known problem? I didn't find any reference to it in the mail archives. Thanks. -John
