Cisco Catalyst 6500 Supervisor 2T Architecture - Ipland

More documents

Recommendations

Info

White Paper6. Additional lookups may be performed by the fabric interface and replication ASIC (if this packet needsreplication services, such as SPAN, multicast, and others).7. The packet is then forwarded to the egress port ASIC (if the destination is local), or to the switch fabric (if thedestination is a port on a remote fabric-capable linecard), or to the bus replication ASIC (if the packetdestination is a linecard with connectivity only to the bus).Egress Packet Processing (Packets Received from Crossbar)1. Packets are received from one of the switch fabric channels.2. The switch fabric sends the packet to the fabric replication ASIC.3. The fabric replication ASIC stores the packet and sends the packet header information to the PFC4 forforwarding lookup processing.4. The PFC4 performs the lookup and sends the results back to the fabric replication ASIC.5. The fabric replication ASIC performs an additional lookup, if replication services are required.6. The fabric replication ASIC then forwards the packet (and replicated packets, if applicable) to the port ASIC,which contains destination information from PFC4.7. The port ASIC stores the packet in the packet buffer and performs egress checks on the packet.8. The port ASIC performs the packet rewrite and then forwards the packet to the CTS ASIC.9. If CTS is enabled, the CTS ASIC performs 802.1ae encryption, and the packet is forwarded to the PhysicalLayer Protocol (PHY), to be transmitted onto the cable.Egress Packet Processing (Packets Received from Shared Bus)1. Packets are received from the bus and are placed on the local bus.2. The Bus Replication ASIC stores the packet and sends packet header information to the PFC4 for forwardinglookup processing.3. The PFC4 performs the lookup and sends the results back to the bus replication ASIC.4. The bus replication ASIC performs an additional lookup, if replication services are required.5. The bus replication ASIC forwards the packet (and replicated packets, if applicable) to the port ASIC, whichcontains destination information from PFC4.6. The port ASIC stores the packet in the packet buffer, and performs egress checks on the packet.7. The port ASIC performs the packet rewrite and forwards the packet to CTS ASIC.8. If CTS is enabled, the CTS ASIC performs 802.1ae encryption, and the packet is forwarded to the PHY, to betransmitted onto the cable.The following sections provide more detail for each processing block.The Fabric and Bus ConnectorThe Catalyst 6500 supports two different switch backplanes, the crossbar switch fabric (top left in the abovediagram), and bus backplanes (top right in the above diagram). The crossbar switch fabric is the high-capacitybackplane that is used by the CEF720 and CEF2T generation of linecards to optimize switching performance. Thisbackplane refers to the 2 Terabit backplane that is contained within the Supervisor’s name. A second backplane(referred to as the “bus” backplane) is also present to support WS-X61xx linecards, supported service modules, andlinecards that do not utilize a local DFC4 for forwarding.The crossbar switch fabric provides a set of fabric channels (or data paths) that are assigned to the slots in thechassis where linecards are inserted. This is referred to collectively as the crossbar switch backplane. This array of© 2011-2012 Cisco and/or its affiliates. All rights reserved. This document is Cisco Partner Confidential Information. Page 10 of 46
White Paperfabric channels provides an any-to-any (full-mesh) connection option for the attached linecard to forward data over adedicated path to any other linecard installed in the chassis.The bus backplane is a 16 Gbps (full duplex) shared data bus that is used to provide a connection between attached“classic” linecards. The data bus operates at 62.5 Mhz and is 256 bits wide. The bridge ASIC provides the interfacethrough which those classic linecards can communicate with the PFC4 and MSFC5 for data processing services.Crossbar Switch FabricThe crossbar switch fabric on the Supervisor 2T provides 2080 Gbps of switching capacity. This capacity is based onthe use of 26 fabric channels that are used to provision data paths to each slot in the chassis. Each fabric channelcan operate at either 40 Gbps or 20 Gbps, depending on the inserted linecard. The capacity of the switch fabric iscalculated as follows:26 x 40 Gbps = 1040 Gbps1040 Gbps x 2 (full duplex) = 2080 GbpsThe 2080 Gbps number is a marketing number (common among all switch vendors) and is used in all literature todenote that full duplex transmission allows data traffic to be transmitted and received simultaneously. While theswitch fabric capacity is documented as a full duplex number, note that the per-slot capacity of the E-Series chassisis NOT a full duplex number.The 80 Gbps per slot nomenclature represents 2 x 40 Gbps fabric channels that are assigned to each slot providingfor 80 Gbps per slot in total. If marketing math were used for this per slot capacity, one could argue that the E-Serieschassis provides 160 Gbps per slot.Figure 3. Fabric Channel Layout in 6509-EFor every chassis (except the 6513-E), there are enough fabric channels to provide dual fabric channels to eachlinecard slot, including the two Supervisor slots. The exception is the 6513-E. For the 6513-E chassis, there are dualfabric channels provided for Slots 1 through 6 and for Slots 9 through 13. Slots 7 and 8 are designated Supervisoronlyslots. If a linecard is inserted in either of these Supervisor-only slots, it will not be powered up.© 2011-2012 Cisco and/or its affiliates. All rights reserved. This document is Cisco Partner Confidential Information. Page 11 of 46
Page 1: Cisco Catalyst 6500 Supervisor 2TAr
Page 4 and 5: White PaperA high-level overview of
Page 6 and 7: White PaperThe installation of the
Page 8 and 9: White PaperTable 6.DFC4 Field Upgra
Page 12 and 13: White PaperFigure 4. Fabric Channel
Page 14 and 15: White PaperIts other main function
Page 16 and 17: White PaperPFC4 and DFC4The PFC4 pr
Page 18 and 19: White PaperFunctional AreaFeatureUp
Page 20 and 21: White PaperLayer 3 - IPv6 Tunnellin
Page 22 and 23: White PaperLayer 3 - Egress NetFlow
Page 24 and 25: White PaperLayer 3 - Layer 2 + Laye
Page 26 and 27: White Paperspace should be used to
Page 28 and 29: White PaperWhile this is discussed
Page 30 and 31: White Paperinterfaces to 4096. The
Page 32 and 33: White PaperLayer 3 Feature PFC3B/PF
Page 34 and 35: White PaperPFC4 (and PFC4XL) Functi
Page 36 and 37: White PaperThe RPF processing block
Page 38 and 39: White Paperreserved for system use.
Page 40 and 41: White PaperThe rewrite info table c
Page 42 and 43: White PaperSubsequent to the Layer
Page 44 and 45: White PaperSwitch Fabric Architectu
Page 46: White PaperGlossaryThe following se

Cisco Catalyst 6500 Supervisor 2T Architecture - Ipland

Create successful ePaper yourself

Delete template?

Save as template?