[c-nsp] Filtering Layer 2 Multicasts on 6509

Max Pierson nmaxpierson at gmail.com
Wed Jan 19 16:46:30 EST 2011


Here's more info on VACL's ...

http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/ios/12.2SXF/native/configuration/guide/vacl.html

<http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/ios/12.2SXF/native/configuration/guide/vacl.html>Apply
the VACL to only drop the traffic if its destination to your RP MAC. If it's
true L2 multicast, it shouldn't be hitting your RP from my understanding of
L2 Multicast. (Someone please correct me if i'm wrong).

On Wed, Jan 19, 2011 at 2:40 PM, Devin Kinch <devinkinch at gmail.com> wrote:

>
> But then the traffic would also be filtered out as in enters the VLAN... I
> still need the traffic to pass through the trunk links to the edge
> aggregation switches at each site.  I just need to keep it from hitting the
> RP.
>
> Unless I'm confused about where VACLs apply filtering...
>
> On 2011-01-19, at 12:23 PM, Max Pierson wrote:
>
> VACL's should do the trick for you here. If you know the value of the
> Ethertype frame, you should still be able to filter on it even though it's
> proprietary. If you don't, time to break out the shark! I would start off by
> trying to filter based on ethertype since that won't be common to any other
> traffic on the wire.
>
> Max
>
> On Wed, Jan 19, 2011 at 1:54 PM, Devin Kinch <devinkinch at gmail.com> wrote:
>
>> I have a network running two 6509's with VSS in the core of the network.
>>  Several of the attached VLANs are used by an application that transmits
>> audio with a non-IP based layer 2 multicast (016b.68xx.xxxx or something
>> like that) stream.  It uses many different destination MAC addresses and the
>> frames have their own vendor proprietary Ethertype.  We also need layer 3
>> routing in the same VLANs to manage these devices.
>>
>> The issue I have is that all these layer 2 multicasts are causing the CPU
>> usage on the Sup to hover at around 70-80%.  It isn't causing any noticeable
>> impact to the network today, but it may impact future scalability.  I've
>> tried using CoPP (which doesn't support L2 filtering)... is there an
>> obvious, elegant way of filtering this traffic from hitting the RP, while
>> still forwarding at layer 2?  Perhaps static MAC entries?
>>
>>
>> Devin Kinch
>> _______________________________________________
>> 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