[c-nsp] WS-6748-SFP with or without DFC?

[christian.macnevin at uk.bnpparibas.com]

Definitely useful, thanks.

When you say 'efficient egress replication', it seems as though it already 
does egress replication on the
67 line cards, as the MET is distributed, no? If so, what's the 
difference?

With NF, does it record total multicast output to a group accurately when 
you're doing egress replication? Or does that
require the DFC?





Internet
tstevens at cisco.com

13/03/2006 11:35

To
Christian MACNEVIN, cisco-nsp
cc

Subject
Re: [c-nsp] WS-6748-SFP with or without DFC?






DFC distributes *everything* from the PFC - L2, IP, MPLS, ACLs/QoS, & 
netflow. The PFC & DFC ASICs are the same.

With respect to multicast, DFCs give you efficient egress multicast 
replication, saving fabric b/w, and increase the aggregate multicast 
lookup throughput for the system.

With respect to NF, DFCs give you a dedicated NF table on each DFC + 
on the PFC - each fwding engine maintains its own NF table. So you 
can collect stats for many more flows than w/a centralized fwding 
engine system.

Note that w/NFv9, we can now export IPv4 multicast flow data from 
6500, which may be of use to you based on the requirements you outlined.

Tim

At 05:22 PM 3/13/2006, christian.macnevin at uk.bnpparibas.com vociferated:
>Hi,
>
>Just looking at one of Tim's presentations from Power sessions, and the
>CEF720 module architecture.
>What functionality does the DFC add/distribute on the 67XX cards? This is
>relevant to a high-performance
>multicast enabled LAN environment where we're starting to consider 
NetFlow
>as a potentially major
>source of information.
>
>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.