> > By the way, it also works for "several peers on a same IP". See > result2.txt > > >> I am fine with dropping the IP based index in Squid-3 entirely if it >> simplifies things. > OK. >> The only reason why it's in Squid-2 is for legacy >> reasons to not break existing SNMP data collectors using the data. >> >> > However, in Squid-3, we have to, since new OID's like addr_type are > mandatory. > >> Regards >> Henrik > > Regards Rafa >
Is there any reason why the PeerIndex is below the field type? SNMPv2-SMI::enterprises.3495.1.5.1.1.1.1 = INTEGER: 1 SNMPv2-SMI::enterprises.3495.1.5.1.1.1.2 = INTEGER: 2 SNMPv2-SMI::enterprises.3495.1.5.1.1.2.1 = STRING: "www.google.es" SNMPv2-SMI::enterprises.3495.1.5.1.1.2.2 = STRING: "www.google.es" SNMPv2-SMI::enterprises.3495.1.5.1.1.3.1 = INTEGER: 1 SNMPv2-SMI::enterprises.3495.1.5.1.1.3.2 = INTEGER: 1 SNMPv2-SMI::enterprises.3495.1.5.1.1.4.1 = STRING: "64.233.183.104" SNMPv2-SMI::enterprises.3495.1.5.1.1.4.2 = STRING: "64.233.183.104" I kind of expected it to be ordered like this: SNMPv2-SMI::enterprises.3495.1.5.1.1.1.1 = INTEGER: 1 SNMPv2-SMI::enterprises.3495.1.5.1.1.2.1 = STRING: "www.google.es" SNMPv2-SMI::enterprises.3495.1.5.1.1.3.1 = INTEGER: 1 SNMPv2-SMI::enterprises.3495.1.5.1.1.4.1 = STRING: "64.233.183.104" ... SNMPv2-SMI::enterprises.3495.1.5.1.1.1.2 = INTEGER: 2 SNMPv2-SMI::enterprises.3495.1.5.1.1.2.2 = STRING: "www.google.es" SNMPv2-SMI::enterprises.3495.1.5.1.1.3.2 = INTEGER: 1 SNMPv2-SMI::enterprises.3495.1.5.1.1.4.2 = STRING: "64.233.183.104" ... (but with the last two .detail.peer entries int reversed order .peer.detail) Otherwise it looks good. Amos