Lack of IPv6 traffic stats makes judging progress difficult
chip.gwyn at gmail.com
Fri Jun 3 19:25:34 CEST 2011
I'm working on that at this moment. I think I've got the xml qeury
worked out, just need to plug the rest in. Hoping to have this
working by v6 Day. I'll be happy to share what I've come up with once
it's working. Hopefully by Monday-ish.
On Fri, Jun 3, 2011 at 1:22 PM, Todd Snyder <todd at borked.ca> wrote:
> I'm glad it worked out!
> My next challenge is trying to get something to graph this data meaningfully
> - I've started poking at Cacti. Has anyone invested the time in Cacti to
> write the template, before I start doing it?
> I'm amazed at just how difficult finding a tool that you can give an oid and
> say 'just graph it!' is.
> On Wed, Jun 1, 2011 at 5:50 PM, chip <chip.gwyn at gmail.com> wrote:
>> On Wed, Jun 1, 2011 at 4:58 PM, Todd Snyder <todd at borked.ca> wrote:
>> > 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 .126.96.36.199.188.8.131.52.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=184.108.40.206.220.127.116.11.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 .18.104.22.168.22.214.171.124.3.1.6
>> > ip.126.96.36.199.2.75 = Counter64: 193498077
>> > ip.188.8.131.52.2.82 = Counter64: 1372480387
>> > ip.184.108.40.206.2.85 = Counter64: 1026814419
>> > ip.220.127.116.11.2.88 = Counter64: 30528758
>> > ip.18.104.22.168.2.89 = Counter64: 1319486
>> > ip.22.214.171.124.2.90 = Counter64: 278863122
>> > ip.126.96.36.199.2.91 = Counter64: 61462823
>> You're my hero! Looks like it works on 6500/7600 under SRE1 as
>> well. I haven't compared it to my 'show interfaces accounting'
>> numbers yet to see if it matches hardware vs process switched packets,
>> but initial indication is that it's all good.
>> Just my $.02, your mileage may vary, batteries not included, etc....
Just my $.02, your mileage may vary, batteries not included, etc....
More information about the ipv6-ops