Re: SNMP support starts on branch squid3-ipv6 !! [improved]

Rafael Martinez (Squid development) wrote:
>> But not in the intended way....:-(
>>
>> We should watch somewhat like :
>>
>> SNMPv2-SMI::enterprises.3495.1.4.1.1.1.64.233.183.99 = Gauge32: 7
>> SNMPv2-SMI::enterprises.3495.1.4.1.2.1.64.233.183.99 = Counter32: 11
>> SNMPv2-SMI::enterprises.3495.1.4.1.3.1.64.233.183.99 = Counter32: 0
>>
>
> Well, 4 index was not the intended subtree. Rather index 5.
>
> Last changeds : see what happens with next peer configuration !
>
> cache_peer www.google.es parent 80 0 no-query name=google
> acl googleSite dstdomain google.es
> cache_peer_access google deny !googleSite
> never_direct allow googleSite
>
>
> See the results are now :
>
> ¡ The tree spawns cache peer's nodes in rigth way ... !
>
> I need to more intensive tests with IPv6 cache_peers ! Amos ?
>

Hmm, the current CVS seems to have a few problems.
One I think is sorting related with the actual stored data:

./squid.conf:
cache_peer ipv4.cairo.treenetnz.com parent 3128 0 background-ping
proxy-only default name=cairo4
cache_peer rio.treenetnz.com parent 80 0 background-ping proxy-only
default name=rio

(cairo 192.168.0.14, rio 192.168.0.12)

./test.snmp
...
SNMPv2-SMI::enterprises.3495.1.5.1.1.1.192.168.0.14 = STRING:
"ipv4.cairo.treenetnz.com"
SNMPv2-SMI::enterprises.3495.1.5.1.1.1.192.168.0.12 = STRING:
"rio.treenetnz.com"
Error: OID not increasing:
SNMPv2-SMI::enterprises.3495.1.5.1.1.1.192.168.0.14
>= SNMPv2-SMI::enterprises.3495.1.5.1.1.1.192.168.0.12

The other IPv6-Address related:

./squid.conf:
cache_peer ipv4.cairo.treenetnz.com parent 3128 0 background-ping
proxy-only default name=cairo4
cache_peer ipv6.cairo.treenetnz.com parent 3128 0 background-ping
proxy-only default name=cairo6

./test.snmp
...
cacheSystem number five 5
SNMPv2-SMI::enterprises.3495.1.5.1.1.1.192.168.0.14 = STRING:
"ipv4.cairo.treenetnz.com"
SNMPv2-SMI::enterprises.3495.1.5.1.1.1.0.0.0.0 = STRING:
"ipv6.cairo.treenetnz.com"
Error: OID not increasing:
SNMPv2-SMI::enterprises.3495.1.5.1.1.1.192.168.0.14
>= SNMPv2-SMI::enterprises.3495.1.5.1.1.1.0.0.0.0

If you don't have a multi-machine test setup I'll give you login here.
I have been testing on a build server and peering a central server.

Amos
Received on Fri Nov 23 2007 - 03:55:35 MST