[c-nsp] Sup2T - poor netflow performance

Dan Brisson dbrisson at uvm.edu
Wed Mar 27 10:11:15 EDT 2013


netdr capture could lend some clues.  I don't think that's been 
suggested yet.  I've only used it on SUP720s, but I would think it will 
still work for SUP-2Ts.

-dan

On 3/27/2013 10:03 AM, Pete Lumbis wrote:
> I'd second this. My guess is there is a large amount of punted traffic and
> the problem is just being made worse by netflow export. I'd suggest
> engaging TAC to help you identify what's going on.
>
>
> On Wed, Mar 27, 2013 at 2:15 PM, Dobbins, Roland <rdobbins at arbor.net> wrote:
>
>> On Mar 27, 2013, at 7:50 PM, Mikael Abrahamsson wrote:
>>
>>>   For "Internet peering router at 10GE with typical eyeball traffic" my
>> opinion is that 6500/7600 doesn't have working netflow.
>>
>> Sup2T/DFC4 fixes these issues, as well as the uRPF mode limitation and
>> weird ACL threshold limitation.
>>
>> The problem the OP is experiencing is likely a result of configuration
>> issues, lots of punted traffic generating flows, or a bug.  The EARL8 ASIC
>> solves all the previous issues associated with 6500/7600 NetFlow.
>>
>> -----------------------------------------------------------------------
>> Roland Dobbins <rdobbins at arbor.net> // <http://www.arbornetworks.com>
>>
>>            Luck is the residue of opportunity and design.
>>
>>                         -- John Milton
>>
>>
>> _______________________________________________
>> cisco-nsp mailing list  cisco-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-nsp
>> archive at http://puck.nether.net/pipermail/cisco-nsp/
>>
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/



More information about the cisco-nsp mailing list