Lack of IPv6 traffic stats makes judging progress difficult

[Todd Snyder]

I had some confusion around getting this working - I couldn't figure out
what the values actually meant which made it hard to determine what I needed
to gather.

So for others who may be trying to sort this out, I ended up updating our
IP-MIB and the INET-ADDRESS-MIB from ftp://ftp.cisco.com/pub/mibs/v2/

That now gives me:

snmpwalk -v 2c -c xxx router .1.3.6.1.2.1.4.31.3.1.6
IP-MIB::ipIfStatsHCInOctets.ipv6.37 = Counter64: 1117948
IP-MIB::ipIfStatsHCInOctets.ipv6.47 = Counter64: 998370

I have also poked Cisco to update their SNMP object browser with the newer
MIB(s) so it contains the ipv6/ipv4 additions beyond ipIfStatsHCInOctets
(
http://tools.cisco.com/Support/SNMP/do/BrowseOID.do?objectInput=1.3.6.1.2.1.4.31.3.1.6&translate=Translate&submitValue=SUBMIT&submitClicked=true
)

Cheers,

Todd.

-----Original Message-----
From: ipv6-ops-bounces+frnkblk=iname.com at lists.cluenet.de
[mailto:ipv6-ops-bounces+frnkblk=iname.com at lists.cluenet.de] On Behalf Of
Tassos Chatzithomaoglou
Sent: Wednesday, May 25, 2011 12:44 AM
To: ipv6-ops at lists.cluenet.de
Subject: Re: Lack of IPv6 traffic stats makes judging progress difficult

ok, i managed to ipv6 stats per interface on a CRS by
queryingipIfStatsHCIn/OutOctets:

i.e.
snmpwalk -v2c -c xxx router .1.3.6.1.2.1.4.31.3.1.6
ip.31.3.1.6.2.75 = Counter64: 193498077
ip.31.3.1.6.2.82 = Counter64: 1372480387
ip.31.3.1.6.2.85 = Counter64: 1026814419
ip.31.3.1.6.2.88 = Counter64: 30528758
ip.31.3.1.6.2.89 = Counter64: 1319486
ip.31.3.1.6.2.90 = Counter64: 278863122
ip.31.3.1.6.2.91 = Counter64: 61462823
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.cluenet.de/pipermail/ipv6-ops/attachments/20110601/f55df0cc/attachment.htm>