[c-nsp] ASR9k - input drops

[Lincoln Dale]

On 17/02/2011, at 7:48 AM, Oliver Boehmer (oboehmer) wrote:

>> That helps a lot. Any idea what those counters actually count? We seem
>> to have a very high PARSE_INGRESS_DROP_CNT (around 1000pps) and
>> UIDB_TCAM_MISS_AGG_DROP (another 1000pps)?
> 
> I'm not an expert, but these two could be related: UIDB_TCAM_MISS_AGG_DROP reports packets hitting the main interface failing classification by any of its subinterface. Is this a trunk and you receive dot1q-tagged traffic which you don't have a matching subinterface or EVC?

actually, my uneducated guess is that  UIDB_TCAM_MISS_AGG_DROP is likely where its a FIB miss, i.e. no FIB match.  e.g. a packet destined for a prefix not in the FIB.

PARSE_INGRESS_DROP_CNT probably matches what you describe, dot1q tagged frames arriving either on L2 interfaces matching a non active or suspended vlan or on L3 subinterfaces with no equivalent L3 dot1q tag present.

(i have nothing to do with ASR9K but do work on other platforms with similar counters with similar names...).


cheers,

lincoln.