[c-nsp] 6500: egress replication mix and match with non-forwarding line cards

[Ian Cox]

At 11:39 AM 3/28/2006 +0100, christian.macnevin at uk.bnpparibas.com wrote:

>   Cheers Ian! The caveats don't seem to bad here - just so long as 
> I'm not planning on using my 6816 ports as multicast-enabled
>interfaces, I should be safe.

You can also not have multicast ingress on that card either. You are 
allowed zero multicast on the card.


Ian

>Cheers
>Christian
>
>
>
>
>Internet
>icox at cisco.com
>
>27/03/2006 19:49
>To
>tstevens, Christian MACNEVIN, cisco-nsp
>cc
>Subject
>Re: [c-nsp] 6500: egress replication mix and match 
>with  non-forwarding line cards
>
>
>
>
>
>There was a feature added in 12.2(18)SXF that allows one to force the
>system into egress mode, with the caveat that no multicast is sourced
>or egresses the non-egress capable card.  Please make sure you
>understand what you are doing if you use this feature.
>
>http://www.cisco.com/en/US/products/hw/switches/ps708/products_configuration_guide_chapter09186a00804356a8.html#wp1076728
>
>The Enhanced FlexWAN, 7600-SIP-200, 7600-SIP-400, 7600-SIP-600 are
>also egress capable.
>
>Ian
>
>
>At 09:13 AM 3/27/2006 -0800, Tim Stevenson wrote:
> >At 06:43 AM 3/27/2006, christian.macnevin at uk.bnpparibas.com quipped:
> > >Hello,
> > >
> > >I'm aware that egress multicast replication only works on the 6500 if all
> > >cards are capable. But what if one of the
> > >cards isn't capable, but also isn't forwarding multicast? does this step
> > >around the issue? or do all of my line cards
> > >need to be 67 series, even if they're not intended for multicast?
> >
> >They all need to be 67xx cards.
> >
> >Tim
> >
> >
> > >(I'm guessing yes...)
> > >
> > >Cheers
> > >Christian
> > >
> > >
> > >This message and any attachments (the "message") is
> > >intended solely for the addressees and is confidential.
> > >If you receive this message in error, please delete it and
> > >immediately notify the sender. Any use not in accord with
> > >its purpose, any dissemination or disclosure, either whole
> > >or partial, is prohibited except formal approval. The internet
> > >can not guarantee the integrity of this message.
> > >BNP PARIBAS (and its subsidiaries) shall (will) not
> > >therefore be liable for the message if modified.
> > >
> > >*******************************************************************
> > ***************************
> > >
> > >BNP Paribas Private Bank London Branch is authorised
> > >by CECEI & AMF and is regulated by the Financial Services
> > >Authority for the conduct of its investment business in
> > >the United Kingdom.
> > >
> > >BNP Paribas Securities Services London Branch is authorised
> > >by CECEI & AMF and is regulated by the Financial Services
> > >Authority for the conduct of its investment business in
> > >the United Kingdom.
> > >
> > >BNP Paribas Fund Services UK Limited is authorised and
> > >regulated by the Financial Services Authority
> > >
> > >_______________________________________________
> > >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.
> >_______________________________________________
> >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/