Lack of IPv6 traffic stats makes judging progress difficult

[chip]

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.

http://tools.cisco.com/Support/CLILookup/cltSearchAction.do?AT=gD&BM=t&CN=%22show%20interfaces%20acc
ounting%22&IndexOptionId=12.2SR&IndexId=IOS

http://tinyurl.com/3odcvnc

--chip

On Tue, May 24, 2011 at 3:02 PM, Jared Mauch <jared at puck.nether.net> wrote:
>
> On May 24, 2011, at 12:28 PM, Eugen Leitl wrote:
>
>> On Tue, May 24, 2011 at 12:21:19PM -0400, Steven J. Vaughan-Nichols wrote:
>>> A link and the first paragraph or so would have been fine. You didn't
>>> need to copy and paste the whole article.
>>
>> Saves time, and avoids media breaks (many people are text-based).
>> Also, web content tends to be ephemeral. Here today, and gone tomorrow.
>
> I'm hoping to present traffic stats from our v6 enabled devices that do flow covering the 72 hours around (before, during and after) ipv6 day.
>
> The work continues to march forward.
>
> I'm seeing about an average of 7-8 new autnums a day showing up in the routing table.  Hopefully that rate will increase.  That rate seems to stop/slow on the weekends.
>
> - Jared

-- 

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.

http://tools.cisco.com/Support/CLILookup/cltSearchAction.do?AT=gD&BM=t&CN=%22show%20interfaces%20acc
ounting%22&IndexOptionId=12.2SR&IndexId=IOS

http://tinyurl.com/3odcvnc

I haven't been able to locate an SNMP MIB to poll this, haven't looked
real hard either....so...

--chip

Just my $.02, your mileage may vary,  batteries not included, etc....