[c-nsp] 3550 high cpu & process switched traffic

Tassos Chatzithomaoglou achatz at forthnet.gr
Fri Aug 18 17:11:44 EDT 2006


Thanks a lot Clinton and everyone else for your answers...

Since i would like first to test a quick "solution" for the routing size problem before i find a 
permanent solution for decreasing its size, if i use a in distribute-list under ospf which denies 
everything (so everything goes out through the default gateway), will that make the routing table 
shorter?

Regards,
Tassos

Clinton Work wrote on 18/8/2006 10:03 μμ:
> 
> Your problem is too many routes for the default SDM template. The 
> default template is limited to 8K Unicast routes.  If you change the SDM 
> template to routing you can probably fit the 11K routes into the TCAM.  
> The routing template is 24K for the 3550-12G and 16K routes for the 
> regular 3550s.
> 
> Please check "show sdm prefer".
> 
> 3550#show sdm prefer
>  The current template is the default template.
>  The selected template optimizes the resources in
>  the switch to support this level of features for
>  16 routed interfaces and 1K VLANs.
> 
>  number of unicast mac addresses:   6K
>  number of igmp groups:             6K
>  number of qos aces:                2K
>  number of security aces:           2K
>  number of unicast routes:          12K
>  number of multicast routes:        6K
> 
> 
> Note, seeing a high pps of routing packets under "show controller cpu" 
> is bad. It means that the IP packets are being punted to the CPU for 
> forwarding. You will see some due to IP options that can't be processed 
> in the TCAM IP forwarding.
> 
> 3550#sh contr cpu
> routing packets : 3323805100 retrieved, 0 dropped, 0 errors
> 
> Example from a 3550 routing about 50Mbps of Internet traffic and the CPU 
> is at 2%.  Each of these commands is a couple of seconds apart. The 
> router is forwarding about 20,000 pps of Internet traffic.
> 
> 
> 3550#show controllers cpu-interface  | inc routing
> routing protocol packets : 21492556 retrieved, 0 dropped
> routing packets : 297482820 retrieved, 0 dropped
> 
> 3550#show controllers cpu-interface  | inc routing
> routing protocol packets : 21492557 retrieved, 0 dropped
> routing packets : 297482826 retrieved, 0 dropped
> 
> 3550#show controllers cpu-interface  | inc routing
> routing protocol packets : 21492557 retrieved, 0 dropped
> routing packets : 297482831 retrieved, 0 dropped
> 
> 3550#show controllers cpu-interface  | inc routing
> routing protocol packets : 21492557 retrieved, 0 dropped
> routing packets : 297482837 retrieved, 0 dropped
> 
> 3550#show controllers cpu-interface  | inc routing
> routing protocol packets : 21492557 retrieved, 0 dropped
> routing packets : 297482845 retrieved, 0 dropped
> 
> 
> 
> 
> Tassos Chatzithomaoglou wrote:
>>
>> 3550#sh ip cef sum
>> IP CEF with switching (Table Version 2714880), flags=0x0
>>   11194 routes, 0 reresolve, 0 unresolved (0 old, 0 new), peak 3
>>   11197 leaves, 683 nodes, 2233168 bytes, 2714439 inserts, 2703242 
>> invalidations
>>   1 load sharing elements, 336 bytes, 1 references
>>   universal per-destination load sharing algorithm, id BAF66A0D
>>   2(0) CEF resets, 446 revisions of existing leaves
>>   Resolution Timer: Exponential (currently 1s, peak 1s)
>>   444 in-place/0 aborted modifications
>>   refcounts:  196815 leaf, 175104 node
>>
>>   Table epoch: 0 (11197 entries at this epoch)
> 
> 


More information about the cisco-nsp mailing list