Lack of IPv6 traffic stats makes judging progress difficult
achatz at forthnet.gr
Wed May 25 07:44:28 CEST 2011
ok, i managed to ipv6 stats per interface on a CRS by queryingipIfStatsHCIn/OutOctets:
snmpwalk -v2c -c xxx router .188.8.131.52.184.108.40.206.3.1.6
ip.220.127.116.11.2.75 = Counter64: 193498077
ip.18.104.22.168.2.82 = Counter64: 1372480387
ip.22.214.171.124.2.85 = Counter64: 1026814419
ip.126.96.36.199.2.88 = Counter64: 30528758
ip.188.8.131.52.2.89 = Counter64: 1319486
ip.184.108.40.206.2.90 = Counter64: 278863122
ip.220.127.116.11.2.91 = Counter64: 61462823
7200 with latest SRE also returns those.
IPv4 stats from the same MIB are either not available or zero, so we'll
stick with ifHCIn/OutOctets for those.
Tassos Chatzithomaoglou wrote on 24/05/2011 23:32:
> Anyone tried ipIfStatsIPVersion under IP-MIB?
> That (in combination with other oids) should do the job, but i haven't
> found a single platform that supports it, although CCO says otherwise.
> Gert Doering wrote on 24/05/2011 23:00:
>> On Tue, May 24, 2011 at 03:16:09PM -0400, chip wrote:
>>> As a note, if you're collecting traffic on 6500/7600's you can get
>>> this by running the 'show interfaces accounting' command. But you can
>>> only use the outbound counters, the inbound counters do not include
>>> hardware switched packets.
>> Actually, it's worse - hardware switched IPv6 packets are counted on
>> the IP*v4* counters.
>> Cisco says it's a chip limitation...
>> (We noticed this when we had a backbone link that only transitted IPv6
>> packets, but the IPv4 counters increased happily... opened a TAC case,
>> TAC could reproduce it, engineering came back with "wontfix" and so
>> the documentation was adjusted...)
>> Gert Doering
>> -- NetMaster
More information about the ipv6-ops