[c-nsp] ME3600X architecture

[Jeff Bacon]

Hello Waris - 

Thank you for the insight. I am curious about how much latency there is
when applied as a 10G-only device (e.g. a L3 border device linking a 10G
LAN to a 10G WAN ring, thus all traffic on the same ASIC) vs the normal
intended flow (1G aggregation). I just don't have the time to test it
at the moment. 

Rosen-MVPN has been brought up here as a "coming soon". Is the support
for GRE-encap in the ASIC already and just not coded for yet, or would
any putative Rosen-MVPN support need to use s/w-based encap - and would
it require a "recirc" a la 6500s?

Many thanks,
-bacon


> Hi,
> The architecture details are currently not available on CCO.
> ME3800X/ME3600X has Cisco Carrier Ethernet ASIC. It is a Cisco ASIC
> and it has all the features (QOS, MPLS, EVC) hardwired. The
> forwarding is TCAM based hence NO performance impact upon enabling
> multiple features at the same time. Scale advertised is
> multidimensional meaning number of IPv4 routes and IPv6 can coexist
> at the same time since every feature has its own TCAM space
> reserved. Push/pop/swap of MPLS labels won't have any performance
> impact and same is true for QoS policies.
> There are two Cisco Carrier Ethernet ASICs on the platform, one for
> the 24x1Gig and another one for the 2x10Gig SFP+ ports (you were
> right about the ASIC distribution). There is a non blocking
> connectivity between the two ASICs. 10Gig SFP+ ports also support
> 1xGig Fiber SFP without license.
> Multicast is done in the egress path and has no performance impact.
> 
> -Waris