<div>I'm glad it worked out! <div><br></div><div>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?</div>
<div><br></div><div>I'm amazed at just how difficult finding a tool that you can give an oid and say 'just graph it!' is.</div><div><br></div><div>Todd.</div><br><div class="gmail_quote">On Wed, Jun 1, 2011 at 5:50 PM, chip <span dir="ltr"><<a href="mailto:chip.gwyn@gmail.com">chip.gwyn@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div><div></div><div class="h5">On Wed, Jun 1, 2011 at 4:58 PM, Todd Snyder <<a href="mailto:todd@borked.ca">todd@borked.ca</a>> wrote:<br>
> I had some confusion around getting this working - I couldn't figure out<br>
> what the values actually meant which made it hard to determine what I needed<br>
> to gather.<br>
> So for others who may be trying to sort this out, I ended up updating our<br>
> IP-MIB and the INET-ADDRESS-MIB from <a href="ftp://ftp.cisco.com/pub/mibs/v2/" target="_blank">ftp://ftp.cisco.com/pub/mibs/v2/</a><br>
> That now gives me:<br>
> snmpwalk -v 2c -c xxx router .1.3.6.1.2.1.4.31.3.1.6<br>
> IP-MIB::ipIfStatsHCInOctets.ipv6.37 = Counter64: 1117948<br>
> IP-MIB::ipIfStatsHCInOctets.ipv6.47 = Counter64: 998370<br>
> I have also poked Cisco to update their SNMP object browser with the newer<br>
> MIB(s) so it contains the ipv6/ipv4 additions beyond ipIfStatsHCInOctets<br>
> (<a href="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" target="_blank">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</a>)<br>
> Cheers,<br>
> Todd.<br>
> -----Original Message-----<br>
> From: ipv6-ops-bounces+frnkblk=<a href="http://iname.com" target="_blank">iname.com</a>@<a href="http://lists.cluenet.de" target="_blank">lists.cluenet.de</a><br>
> [mailto:<a href="mailto:ipv6-ops-bounces%2Bfrnkblk">ipv6-ops-bounces+frnkblk</a>=<a href="http://iname.com" target="_blank">iname.com</a>@<a href="http://lists.cluenet.de" target="_blank">lists.cluenet.de</a>] On Behalf Of<br>
> Tassos Chatzithomaoglou<br>
> Sent: Wednesday, May 25, 2011 12:44 AM<br>
> To: <a href="mailto:ipv6-ops@lists.cluenet.de">ipv6-ops@lists.cluenet.de</a><br>
> Subject: Re: Lack of IPv6 traffic stats makes judging progress difficult<br>
><br>
> ok, i managed to ipv6 stats per interface on a CRS by<br>
> queryingipIfStatsHCIn/OutOctets:<br>
><br>
> i.e.<br>
> snmpwalk -v2c -c xxx router .1.3.6.1.2.1.4.31.3.1.6<br>
> ip.31.3.1.6.2.75 = Counter64: 193498077<br>
> ip.31.3.1.6.2.82 = Counter64: 1372480387<br>
> ip.31.3.1.6.2.85 = Counter64: 1026814419<br>
> ip.31.3.1.6.2.88 = Counter64: 30528758<br>
> ip.31.3.1.6.2.89 = Counter64: 1319486<br>
> ip.31.3.1.6.2.90 = Counter64: 278863122<br>
> ip.31.3.1.6.2.91 = Counter64: 61462823<br>
<br>
</div></div>Todd,<br>
<br>
You're my hero! Looks like it works on 6500/7600 under SRE1 as<br>
well. I haven't compared it to my 'show interfaces accounting'<br>
numbers yet to see if it matches hardware vs process switched packets,<br>
but initial indication is that it's all good.<br>
<br>
--chip<br>
<font color="#888888"><br>
--<br>
Just my $.02, your mileage may vary, batteries not included, etc....<br>
</font></blockquote></div><br></div>