[c-nsp] netflow & Sup32 with native IOS

matthew zeier mrz at velvet.org
Mon Aug 7 01:30:12 EDT 2006


that was it, thanks!

Tim Stevenson wrote:
> You need to change your h/w flow mask to something useful like "mls flow 
> ip interface-full" and you need "mls nde sender version 5" to enable 
> export of h/w stats. Probably you'll also want to muck w/the aging 
> timers: "mls aging normal|fast|long".
> 
> Right now you're only get stats for s/w switched traffic.
> 
> Tim
> 
> At 09:24 PM 8/4/2006 -0700, matthew zeier contended:
> 
>> Is there a trick to get Netflow working on a Sup32 running native IOS?
>>
>> I'm using ehnt to view top destination ASNs. I have the following 
>> config and
>> am getting data sent, however, the traffic counts are far below what I'm
>> actually pushing (>200Mbps).
>>
>> For instance,
>>
>> |---------------Dest----------------|
>> |----AS Name/Num----|-bw,% of total-|
>>   VZGNI-TRANSIT(19262)    174k;  39.00%
>>          KOMTEL( 8881)     13k;   2.93%
>>       <unknown>(28573)     12k;   2.64%
>>     CNCGROUP-BB( 4837)     11k;   2.51%
>>     ALTERNET-AS(  701)     11k;   2.49%
>>
>>
>> I can't tell if my config is wrong or there's some limitation of the 
>> Sup32.
>> The bw figures are way low.
>>
>> ip flow-export source Loopback0
>> ip flow-export version 5 origin-as
>> ip flow-export destination blah 4444
>>
>>
>> interface Port-channel1
>>   description to_core1:po1
>>   ip address blah
>>   ip route-cache flow
>>   ip ospf authentication message-digest
>>   ip ospf authentication-key
>>   ipv6 enable
>> end
>> _______________________________________________
>> 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/
> 
> 
> 
> Tim Stevenson, tstevens at cisco.com
> Routing & Switching CCIE #5561
> Technical Marketing Engineer, Catalyst 6500
> Cisco Systems, http://www.cisco.com
> IP Phone: 408-526-6759
> ********************************************************
> The contents of this message may be *Cisco Confidential*
> and are intended for the specified recipients only.


More information about the cisco-nsp mailing list