[nsp] Tcam capacity on 7603/Sup2/Msfc2

[Tim Stevenson]

Yes, that is the right counter for ACL labels. Something else strange is going on. I don't see any bugs matching these errors. What code are you running & what h/w config? 

Could be the best approach is a TAC case.

Tim 

At 12:33 PM 3/5/2004, Konstantin Barinov contended:

>14 ACL's, of them 2 applied to interface, 6 used for qos.
>2 interfaces with "service-policy input"
>3 route maps, 2 of them for bgp, 1 applied to interface.
>
>And:
>
>#sh tcam counts
>           Used        Free        Percent Used       Reserved
>           ----        ----        ------------       --------
>Labels:      4         508            0
>
>
>This counter is wrong? Or it is a wrong counter? :)
>
>
>
>br
>--
>Konstantin Barinov
>INFONET AS, Tallinn, Estonia
>
>Friday, March 5, 2004, 10:05:12 PM, you wrote:
>
>TS> ODM will probably not help, it looks like you are running out
>TS> of ACL labels, which most likely means you have too many ACLs
>TS> configured.
>
>TS> How many unique ACLs are configured? Also, how many PBR and QoS enabled interfaces?
>
>TS> Each L3 interface with a *unique* combination of ACLs, PBR, &
>TS> QoS will consume one of the 512 available labels.
>
>TS> Tim
>
>TS> At 11:35 AM 3/5/2004, cisco-nsp-request at puck.nether.net contended:
>>>Message: 10
>>>Date: Fri, 05 Mar 2004 11:27:59 -0800
>>>From: Steve Francis <steve at expertcity.com>
>>>Subject: Re: [nsp] Tcam capacity on 7603/Sup2/Msfc2
>>>To: Konstantin Barinov <sbr at infonet.ee>
>>>Cc: cisco-nsp at puck.nether.net
>>>Message-ID: <4048D4BF.50600 at expertcity.com>
>>>Content-Type: text/plain; charset=us-ascii; format=flowed
>>>
>>>Konstantin Barinov wrote:
>>>
>>>>Hi,
>>>>
>>>>Any guru of 6500/7600 can help? System is 7603/Sup2/Msfc2, IOS 12.1(20)E2
>>>>  
>>>>
>>>Try
>>>mls aclmerge algorithm odm
>>>
>>>See 
>>>http://cio.cisco.com/en/US/customer/products/hw/switches/ps708/products_white_paper09186a00800c9470.shtml
>>>Much more efficient in my experience...
>>>
>>>>
>>>>Mar  5 20:05:31: %QM-4-TCAM_LABEL: Hardware TCAM label capacity exceeded
>>>>Mar  5 20:05:31: %QM-SP-4-WARNING: TCAM request replace [lkup=1] status:6
>>>>
>>>>After this mls qos and policy routing stops.
>>>>
>>>>Access-lists are small, maybe 250 lines all together.
>>>>
>>>>#sh tcam counts
>>>>           Used        Free        Percent Used       Reserved
>>>>           ----        ----        ------------       --------
>>>> Labels:      4         508            0
>>>>
>>>>ACL_TCAM
>>>>  Masks:     36        4060            0                     0
>>>>Entries:     71       32697            0                     0
>>>>
>>>>QOS_TCAM
>>>>  Masks:     50        4046            1                     0
>>>>Entries:     84       32684            0                     0
>>>>
>>>>    LOU:     12          52           18
>>>>  ANDOR:      1          15            6
>>>>  ORAND:      0          16            0
>>>>    ADJ:      1        1023            0
>>>>
>>>>
>>>>    
>>>>br
>>>>--
>>>>Konstantin Barinov
>>>>INFONET AS, Tallinn, Estonia
>>>>
>>>>_______________________________________________
>>>>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/
>>>>  
>>>>
>
>
>TS> Tim Stevenson, tstevens at cisco.com
>TS> Routing & Switching CCIE #5561
>TS> Technical Marketing Engineer, Catalyst 6500
>TS> Cisco Systems, http://www.cisco.com
>TS> IP Phone: 408-526-6759
>TS> ********************************************************
>TS> The contents of this message may be *Cisco Confidential*
>TS> and are intended for the specified recipients only.
>
>TS> _______________________________________________
>TS> cisco-nsp mailing list  cisco-nsp at puck.nether.net
>TS> https://puck.nether.net/mailman/listinfo/cisco-nsp
>TS> 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.