10.07.2015 Views

Cisco Catalyst 6500 Supervisor 2T Architecture - Ipland

Cisco Catalyst 6500 Supervisor 2T Architecture - Ipland

Cisco Catalyst 6500 Supervisor 2T Architecture - Ipland

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

White PaperLayer 3 Feature PFC3B/PFC3BXL PFC3C/PFC3CXL PFC4/PFC4XLPort ACLs 2 K 2 K 8 KACL accounting statistics None None 4 KRPF interface check 2 2 16Hardware rate limiters 8 (L3) 8 (L3) 32 (L3)Aggregate policers 1023 1023 16 KAggregate policer profile N/A N/A 1 KMicroflow policer buckets Up to 256 K Up to 256 K 512 K IFE and 512 K OFE*Shared microflow policers 63 63 512Egress microflow policing No No YesDistributed policers No No 4 KPacket or byte-based policing No No YesQoS policy groups 0 0 128DSCP mutation maps 1 1 14 Ingress16 Egress* IFE and OFE are defined in the next sectionLayer 3 Forwarding Engine Processing PathsThe Layer 3 forwarding engine has two basic processing paths (also referred to as pipelines): one for ingress (orinput) forwarding (IFE) and one for egress (or output) forwarding (OFE). These two pipelines perform the followingfunctions:● The IFE pipeline performs ingress functions, including input classification, input QOS, ACLs, RPF checks,ingress NetFlow, and L3 FIB-based forwarding.● The OFE pipeline performs egress functions, including adjacency lookup, egress classification, and rewriteinstruction generation.When a packet header enters the L3 ASIC, the IFE pipeline is the first pipeline to process the packet. Aftercompletion of IFE processing, the header is then passed onwards to the OFE pipeline, along with the results of theIFE processing. This can be seen in the following diagram.Figure 11.Layer 3 Forwarding Engine Processing Pipelines© 2011-2012 <strong>Cisco</strong> and/or its affiliates. All rights reserved. This document is <strong>Cisco</strong> Partner Confidential Information. Page 32 of 46

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!