1 K Cisco Nexus x 86 Nexus 2000

1 K Cisco Nexus x 86 Nexus 2000 Connectivity - Supported Topologies Presentation_ID © 2008 Cisco Systems, Inc. All rights reserved. Cisco Confidential 1

Nexus 5500 Platform 2 nd-Generation Nexus 5000 with L 3 support § Flexible port configurations § Latency: ~2 usec § Unified Port Concept: 1 G/10 G/FCo. E/DCB, 1/2/4/8 G FC, 1 GE § Cisco Fabric Path Support § Fix port not support FC, Module 16 x Unified Ports SFP+ § Standards-based T 11 FCo. E § IETF TRILL & Cisco L 2 MP § Hardware support for IEEE 1588 (Precision Time Protocol – µs accuracy & timestamp) § Front-to-back and back-to-front airflow § Layer 2 / Layer 3 support § Support for increased number of FEX per N 5500 § 4 K VLANs § 40 G Uplinks (future) § 32 K MAC Table Entries § Enhanced feature SPAN, multicast

Nexus 5548 Rear Panel 32 x Fixed ports 1/10 GE Expansion Module

Layer 3 on Nexus 5548 P Available Q 1 CY 11 § N 55 -D 160 L 3 field replaceable daughter card § Upgradeable in-rack § No un-mounting required § No reduction of front panel ports. 160 Gbps L 3 bandwidth Layer 3 Daughter card Front of the Switch Flexibility Choice Future Proofing

Install L 3 daughter card on Nexus 5548 2 Available Q 1 CY 11 Unscrew the IO Module Pull the IO Module out Front of the Switch 3 Plug and Screw the L 3 IO Module Plug and Screw the Fan Modules 1 Unscrew the Fan Modules Pull the Fan Modules out

Nexus 5596 2 nd Generation Nexus 5000 with L 3 support N 5596 96 x SFP+ (w/3 x Module) in 2 RU N 5196 P: 96 x SFP+ (w/ 3 x Modules) in 2 RU 96 Fixed Ports capable of 10 GE/1 GE/FCo. E/FC (Unified Port) Three Expansion Module Slots Modules Supports on Nexus 5500 Platform features AND unified ports on all ports 16 x 10 G/FCo. E/DCB SFP+ 8 x 10 G/FCo. E, 8 x 1/2/4/8 G FC 16 x Unified Ports SFP+ Presentation_ID © 2009 Cisco Systems, Inc. All rights reserved. Cisco Confidential 6

L 3 Support on Nexus 5596 N 5596 P: 96 x SFP+ (w/ 3 x Modules) in 2 RU Module 48 x Unified Ports SFP+ § Each L 3 module provides 160 Gbps L 3 forwarding bandwidth § L 3 module can only be used for Nexus 5596 § No front panel ports on L 3 module § At FCS nexus 5596 supports one L 3 module. Subsequent release will support three L 3 module with aggregation 480 Gbps L 3 throughput

L 3 Bandwidth and Packet Flow Layer 3 Daughter Card N 5548 P UPC 8 8 Intelligent Layer 3 Highlights X-Bar Fabric 8 UPC 8 8 UPC UPC 32 Fixed Ports 8 UPC Module Slot N 5596 P Layer 3 Module UPC 8 Module Slot Layer 3 Module UPC 8 UPC UPC 8 8 8 X-Bar Fabric 8 8 UPC UPC 48 Fixed Ports Available CY 11 UPC § UPC: 8 -port lookup/port ASIC § X-Bar Fabric: 100 x 100 crossbar fabric ASIC § X-Bar Fabric can scale up to 12 x UPC § L 3 Capability (field upgradeable): § 5548: 1 x daughter-card slot § 5596: Up to 3 x GEM module § Each daughter-card or GEM supports 160 Gbps of bidirectional bandwidth § Modules: § 16 x 10 G SFP+ § 8 x 10 G, 8 x 1/2/4/8 G FC § L 3 Module – 160 G (no front-panel ports)

L 3 Features § NX-OS Support Single Unified Layer 2/Layer 3 Management In Service Software Upgrade (ISSU) for Layer 3* MIBs and DCNM (Datacenter Network Manager) Layer 3 Feature Support Interfaces: Routed, SVI, port-channel Up to 16 K IPv 4 /32 Host Routing Table 16 -way L 3 ECMP 8 K IPv 4 LPM Routing Table IPv 4 Routing: Static, RIPv 2, OSPFv 2, EIGRP, BGP IPv 6 Routing: OSPFv 3, RIP-NG, EIGRP* Policy-based Routing (PBR)* IGMP v 1, v 2, v 3; PIM HSRP, VRRP, GLBP* 2 K L 3 IP Multicast groups RACL VRF-Lite (IP VPNs) Unicast RPF (u. RPF) Bcast/Mcast suppression Bi. Directional Forward Detection (BFD)* Qo. S marking, scheduling and policing (MQC) * Post FCS Support

N 5548/N 2 K Bundles Transition Summary § Provide an easy transition from N 5010/FEX and N 5020/FEX to Oxygen/FEX § Transition N 5010 P/4 FEX business to N 5548 P/4 FEX, Transition N 5020 P/6 FEX business to N 5548 P/6 FEX/GEM, transition N 5020 P/4 FEX-10 G to N 5548 P/4 FEX-10 G Bundle Type N 5 K/4 x. N 2248 T (192 p 100 M/1 G Ethernet bundles) N 5 K/6 x. N 2248 T (288 p 100 M/1 G Ethernet bundles) N 5 K/4 x. N 2232 PP (128 p 1/10 GE Ethernet Bundles) Current Bundle List Price N 5010 P/4 x. N 2248 T/32 x. FET $53, 000 N 5548 P/4 N 2248 T/32 x. FET $57, 000 N 5010 P/4 x. N 2248 T $46, 000 N 5548 P/4 N 2248 T $52, 000 N 5010 P/4 x. N 2248 T/20 x. SR $70, 000 N 5548 P/4 N 2248 T/20 x. SR $74, 000 N 5020 P/6 x. N 2248 T/48 x. FET $79, 500 N 5548 P/GEM/6 N 2248 T/48 x. FET $82, 000 N 5020 P/6 x. N 2248 T $69, 000 N 5548 P/GEM/6 N 2248 T $74, 500 N 5020 P/6 x. N 2248 T/30 x. SR $105, 000 N 5548 P/GEM/6 N 2248 T/30 x. SR $108, 000 N 5020 P/4 N 2232 P/64 x. FET $85, 500 N 5548 P/GEM /4 N 2232 P/64 x. FET $84, 000 Storage option for N 5548/N 2 K bundles: N 55 -48 PF-SSK 9 $12, 800 FCo. E Options for N 5 K/N 2 K Bundles Presentation_ID New BUNDLE © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 10

Cisco FEXlink: Virtualized Access Switch Changing the device paradigm § De-Coupling of the Layer 1 and Layer 2 Topologies § Simplified Management Model, plug and play provisioning, centralized configuration § Line Card Portability (N 2 K supported with Multiple Parent Switches – N 5 K, 6100, N 7 K) § Unified access for any server (100 M 1 GE 10 GE FCo. E): Scalable Ethernet, HPC, unified fabric or virtualization deployment . . . Virtualized Switch Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 11

Cisco FEXlink: Virtualized Access Switch Upgrade Flexibility § Nexus parent switch provides the forwarding functionality for the Virtualized Access Switch § Upgrading the parent switch upgrades the capabilities of the entire virtualized Access switch Migrating Parent Switches Nexus 7000 Parent Switch M 1 Line Card - 32 FEX, Layer 2 & 3 Ethernet Nexus 5000 Parent Switch 12 FEX, DCB, Layer 2 Ethernet, FCo. E, FC Nexus 5500 Parent Switch 16 FEX, DCB, Ethernet, FCo. E, NIV, Layer 2 & Layer 3 (1 HCY 11), Fabric. Path (2 HCY 11) Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential Nexus 7000 Parent Switch F 2 Line Card - DCB, Ethernet, FCo. E, NIV, Layer 2 & Layer 3, Fabric. Path (2 HCY 11) Future Evolution of Parent Switches 12

Nexus 5000 Parent Switch All Nexus 5000 are VNTag Capable Parent Switch FEX Capable Nexus 5020 12 12 Nexus 5010 16 Nexus 5548 Nexus 5596 (Q 1 CY 11) # FEX Q 1 CY 2011 16 Optics/Transceivers Supported Passive CX-1 SFP+ (1/3/5 m) Active CX-1 SFP+ (7/10 m) SR SFP+ (MMF) – OM 3 300 m LR SFP+ (SMF) – 300 m (FCo. E no drop)* FET SFP+ (MMF) – OM 2 20 m, OM 3 100 m LRM SFP+ - Not Supported * Potential to increase supported FEX to Nexus 5500 fabric link distances with 2248/2232 and Future FEX BRKDCT-2023 © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 13

Nexus 7000 Parent Switch FEX enabled line cards – VNTag Capable N 7 K Parent Switch I/O Module FEX / vn. Tag support Optics/Transceivers supported on N 7 K + N 2 K combination Passive CX-1 SFP+ (1 m/3 m/5 m): No Active CX-1 SFP+ (7 m/10 m): Yes SR SFP+ (MMF): Yes – OM 1 26 m OM 3 300 m LR SFP+ (SMF): Yes – up to 10 km LRM SFP+: No FET SFP+ (MMF): Yes – OM 2 25 m OM 3 100 m N 7 K-M 132 XP-12 32 -port SFP+ M 1 I/O module $70, 000 N 7 K-M 108 X 2 -12 L FEX not supported 8 -port X 2 M 1 I/O module $44, 000 Passive CX-1 SFP+ (1 m/3 m/5 m): Yes Active CX-1 SFP+ (7 m/10 m): Yes SR SFP+ (MMF): Yes – OM 1 26 m OM 3 300 m LR SFP+ (SMF): Yes – up to 10 km LRM SFP+: No FET SFP+ (MMF): Yes – OM 2 25 m OM 3 100 m N 7 K-M 132 XP-12 L 32 -port SFP+ M 1 XL I/O module $70, 000 N 7 K-F 132 XP-15 FEX not supported 32 -port D 1 I/O module $35, 000 N 7 K-F 2 series 2 HCY 2011 BRKDCT-2023 F 2 © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public Passive CX-1 SFP+ (1 m/3 m/5 m): Yes Active CX-1 SFP+ (7 m/10 m): Yes SR SFP+ (MMF): Yes – OM 1 26 m OM 3 300 m LR SFP+ (SMF): Yes – up to 10 km LRM SFP+: No FET SFP+ (MMF): Yes – OM 2 25 m OM 3 100 m 14

Nexus 5000 and Nexus 7000 Parent Switch FEX Support N 5 K Support N 7 K Support Number of FEX supported 16 32 N 2 K-C 2148 T-1 GE ü No N 2 K-C 2248 TP-1 GE ü ü N 2 K-C 2224 TP-1 GE ü Q 1 CY 11 N 2 K-C 2232 PP-10 GE ü Q 1 CY 11 N 2 K-C 2232 TP-10 GE Target Q 1 CY 11 Presentation_ID © 2009 Cisco Systems, Inc. All rights reserved. Cisco Confidential 15

Nexus 2148 T, 2248 TP, 2232 PP Capabilities Features 2148 2232 Fabric Ports (NIF) 4 4 8 Fabric Link Port Speed (NIF) 10 Gbps Port Channels on Fabric Links (NIF) 1 x 4 ports maximum Hash L 2/L 3 fields 1 x 4 ports maximum Hash L 2/L 3/L 4 1 x 8 ports maximum Hash L 2/L 3/L 4 Host Ports (HIF) 48 48 32 1 Gbps only 100 Mb/1 Gbps/10 Gbps (No 1 Gbps at FCS, 2 HCY 10) Local Port Channels on Host Ports (HIF) Not Supported Max 8 ports per port channel, Max of 24 port channels per 2248 Hash L 2/L 3/L 4 Max 8 ports per port channel, Max of 16 port channels per 2232 Hash L 2/L 3/L 4 FCo. E/DCB Servers No No Yes Nexus 5010/5020/5548 Nexus 7000 M 1 Nexus 5596 - Q 1 CY 11 Nexus 7000 F 2 – Nexus 5010/5020/5548 Nexus 5596 - Q 1 CY 11 Nexus 7000 M 1 – Q 1 CY 11 Nexus 7000 F 2 – Host Port Speeds (HIF) Supported Parent Switches Presentation_ID Nexus 5010/5020/5548 Nexus 5596 - Q 1 CY 11 © 2009 Cisco Systems, Inc. All rights reserved. Cisco Confidential

Nexus 5000 and Nexus 7000 Parent Switch FEX Capabilities Nexus 7000* Nexus 5000** # of 1 G Ports 32 x 2248 = 1536 (Q 4 CY 10) 12 x N 2 K = 576, 16 x N 2 K = 786 (Q 4 CY 10) # of 10 G Ports 32 x 2232 = 1024 (1 HCY 11) 12 x N 2 K = 384, 16 x N 2 K = 512 (Q 4 CY 10) Port Speed 100 M/1 G (10 G Q 1 CY 11) 100 M/1 G/10 G Fabric. Path Requires F 2 (2 HCY 11) Requires 5500 (1 HCY 11) and Fabric. Path 5 k capability (2 HCY 11) L 3 Support SVI (Q 4 CY 10), Routed Ports (CY 11) SVI (Q 1 CY 11), Routed Ports (CY 11) NIV Support Future 1 HCY 11 Requires F 2 (2 HCY 11) Yes 2 Tx/Rx + 14 Tx only 2 Tx/Rx, 4 Tx/Rx in Q 4 CY 10 (Nexus 5500) v. PC Support 1 HCY 11 Yes Host Port Channels 1 HCY 11 Yes (2248/2232) MAC address table 128 K 14 K (Nexus 5000), 32 K (Nexus 5500) Yes (1 HCY 11) No Unified I/O capable Total SPAN sessions Netflow * Scalability for Number of Routes, PACL/VACL/RACL is based on M 1 line card, N 7 K-M 132 XP-12 Yes (All ports in a FEX for are. Nexus in the 7000 same VDC No or N 7 K-M 132 XP-12 XL ** Scalability for Number of Routes, PACL/VACL/RACL VDC) for Nexus 5000 is dependent on selection of parent switch, Nexus 5000 or Nexus 5500 Presentation_ID © 2009 Cisco Systems, Inc. All rights reserved. Cisco Confidential

Cabling Plant Main Distribution Area – analogous to MDF Location of Core equipment and main cross -connect panels MDA HDA HDA EDA Location of the aggregation equipment and end of row cross-connect panel HDA EDA Horizontal Distribution Area Equipment Distribution Area Compute racks/cabinets and top of rack cross-connect panel HDA BACKBONE CABLING HDA HORIZONTAL CABLING Vertical Cabling: Patch cable to compute equipment Horizontal Cabling: from rack/cabinet to end of row cross-connect Backbone Cabling: from end of row cross-connect to main cross-connect Ø Recommendations • Use fiber as horizontal cabling to ease the transition from GE to 10 GE • Session_ID Vertical Cabling is just a patch cable top match access IO: GE, 10 GE, FCo. E, copper, fiber, etc Presentation_ID © 2008 Cisco Systems, Inc. All rights reserved. Cisco Public 18

Fabric Extender Roadmap Combined Platform Roadmap Nexus 7000 Nexus 5000 Hardware 1 H CY 2010 Presentation_ID Q 3 CY 10 Q 1 CY 11 Internal Cisco Only 2 HCY 11 • Fabric Extender Transceiver • Nexus 2232 PP 1/10 GE FEX • Nexus 2248 TP GE/FE FEX • Nexus 2224 TP 100 Mbps/1000 Base-T FEX • Stretch Goal: NEBS on N 2248 TP, N 2232 PP • Nexus 2232 TP 1/10 GT FEX • Stretch goal: Power Supply & FAN for back-to-front airflow • Stretch goal: 400 W DC Power Supply DEE WHY (Shipping) • FET • Nexus 2232 PP • Nexus 2248 TP • FEX ISSU • Local FEX Port Channels (N 22 xx only) • FCo. E & DCB on N 2232 FEX DEE WHY + (Shipping) • 1 G on Nexus 2232 • Nexus 2224 TP E-ROCKS (ECed) • SVI Routing (N 5500 platform) • Stretch goal: Nexus 2232 TP • Stretch goal: 20 FEX/N 5500 • Stretch goal: Power Supply & FAN for back-to-front airflow • Stretch goal: 400 W DC Power Supply FAIRHAVEN (Planning) • Fabric. Path • Dual Layer v. PC DELHI (5. 2 - ECed) • N 2232 PP-10 G 1/10 GE FEX (no FCo. E on M 1 card) • Stretch goal: Local FEX Port Channels, v. PC host-to-FEX, L 3 routed interfaces on FEX, PVLAN, SPAN source, Net. Flow, Nexus 2224 TP FREETOWN (6. 0 - CCed) • FEX support on F 2 Module (48 p 10 G, wirerate, FCo. E, Fabric. Path) • FCo. E on N 2232 PP • v. PC from FEX-to-N 7 K • FEX pre-provisioning EAGLEHAWK • v. PC sync (configuration sync) • FEX pre-provisioning • 16 FEX per N 5548 P CAIRO (5. 1) • N 2248 T-1 G support • N 2 K Support on M 132 XP and M 132 XP-XL • 32 FEX per N 7 K • FET Support • SVI Routing • HA: FEX ISSU, port-channel N 2 K-to-N 7 K, NIC teaming • VDC per FEX © 2009 Cisco Systems, Inc. All rights reserved. Cisco Confidential 19

Continuous Innovations to Simplify Configuration and Management HIF Config Sync § Config Sync enables changes on one switch to automatically synchronize to its peer switches § Config Sync works in conjunction with v. PC Port Profiles § Port-Profile feature consists of a configuration template which can be applied to an interface or a range of interfaces § Eliminates repetitive interface configurations FEX Pre-Provisioning § Admins will have the flexibility to pre-provision FEX host ports prior to the FEX physically present in the network. § Simplified FEX configuration § Ease of management for large number of interfaces Business Value § Flexible rollout to support heterogenous environment § Reduced operational costs Presentation_ID © 2009 Cisco Systems, Inc. All rights reserved. Cisco Confidential 20

Virtualized Switch Device Level Redundancy § Switch level High Availability needs to consider Redundant Supervisor – Nexus 5000/5500 running in v. PC mode or Nexus 7000 with dual supervisor § Control Plane § Supervisor Redundancy § Data Plane § Forwarding ASIC Redundancy § Fabric § Isolated/Redundant Paths § System Mechanical Redundancy § Power Supply § Fan BRKDCT-2023 1 – 32 Line Cards per virtual switch © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 10 – 80 Gbps via 1 – 8 redundant fabric links per line card (N 2 K) 21

Nexus 2000 Fabric Extender Fabric Redundancy Models § Fabric Extender associates (pins) a server side (1 GE) port with a fabric uplink § Server ports are either individually pinned to specific uplinks (static pinning) or all interfaces pinned to a single logical port channel § Behavior on FEX uplink failure depends on the configuration Server Interface goes down Static Pinning § Static Pinning – Server ports pinned to the specific uplink are brought down with the failure of the pinned uplink § Port Channel – Server traffic is shifted to remaining uplinks based on port channel hash Server Interface stays active Port Channel BRKARC-3452_c 1 © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 22

Virtualized Access Switch Supervisor Redundancy—v. PC Single Supervisor Based Virtual Switch Dual Supervisor Based Virtual Switch – 4. 1(3)N 1 Single Supervisor – 1 x N 5 K 1 – 12 Line Cards per virtual switch BRKDCT-2023 10 – 40 Gbps Fabric allocated per line card (N 2 K) © 2010 Cisco and/or its affiliates. All rights reserved. Dual Supervisor – 2 x N 5 K 1 – 12 Line Cards per virtual switch Cisco Public 20 – 40 Gbps Fabric allocated per line card (N 2 K) 23

Virtualized Access Switch v. PC Redundancy Models—Dual Chassis § v. PC provides two redundancy designs for the virtualized access switch § Option 1—MCEC connectivity from the server Two virtualized access switches bundled into a v. PC pair Full redundancy for supervisor, line card, cable or NIC failure Logically a similar HA model to that currently provided by VSS 802. 3 ad Link Aggregation Control Protocol (LACP) Two Virtualized access switches Each with a v. PC peers Single Supervisor MCEC from server to the access switch Multichassis Ether. Channel (MCEC) LACP BRKDCT-2023 © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 24

Virtualized Access Switch v. PC Redundancy Models—Dual Supervisor § v. PC Option 2—Fabric Extender connected to two Nexus 5000 From the server perspective a single access switch with each line card supported by redundant supervisors Full redundancy for supervisor, fabric via v. PC and cable or NIC failure via active/standby NIC redundancy Logically a similar HA model to that currently provided by dual supervisor based modular switch Fabric Extender N 2 K dual homed to redundant Nexus 5000 BRKDCT-2023 © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 25

Nexus 7000 Parent Switch System High Availability § Nexus 7000 provides chassis based high availability § All physical components physically redundant § NX-OS high availability § Fabric Port channel between a Nexus 2248 to a single Nexus 7000 Dual Sup and Chassis HA Fabric Port Channel Spans line cards § The port channel can span several I/O Modules for redundancy § Component level redundancy is similar to dual homed Nexus 5000/5500 with dual homing to 2 x Nexus 7000 BRKDCT-2023 © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 26

Nexus 5000 Parent Switch Virtualized Access Switch High Availability Models Switch Fabric + Network level and Server level HA v. PC Peer Link Switch Fabric + Control Plane + Network level and Server level HA v. PC Peer Links N 2 K MCEC Host MCEC – Running between Single Supervisor Based Virtual Switches BRKDCT-2023 © 2010 Cisco and/or its affiliates. All rights reserved. Dual Supervisor Based Virtual Switches Cisco Public 27

Nexus 7000 Parent Switch Virtualized Access Switch High Availability Models Switch Fabric + Control Plane + Network level and Server level HA BRKDCT-2023 © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 28

NIC Teaming Options Server Team view of HA 6 Options BRKDCT-2023 © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 29

NIC Teaming Options Server Team view of HA § Automatic: § 802. 3 ad requires v. PC and LACP This option figures out what is connected upstream and automatically configures the best teaming option § 802. 3 ad dynamic: This option requires LACP support and in this configuration v. PC since the NICs are split across FEXes § Switch Assisted Load Balancing: Translation = static port-channeling § Switch Assisted Load Balancing requires v. PC only § TLB works ALWAYS and provides increased bandwidth in the TX direction § Transmit Load Balancing: 1 Port RX all ports in the team TX § Network Fault Tolerance: Translation: Active/Standby BRKDCT-2023 © 2010 Cisco and/or its affiliates. All rights reserved. § NFT works always and provides not bandwidth benefits to the server Cisco Public 30

TLB Option BRKDCT-2023 © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 31

TLB All Links TX and One Link RX (and TX) 5 k 01 5 k 02 Peer-link primary secondary “fabric links” v. PC 1 FEX 100 HIF BRKDCT-2023 v. PC 2 FEX 120 HIF © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 32

Data Center Access Architecture Nexus 5000 and 2148 T Deployment Options For Your Reference Not Supported Without v. PC With v. PC 2 HCY 11(55 xx Only) BRKDCT-2023 © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 33

Data Center Access Architecture Nexus 5000 & 2248 T Deployment Options For Your Reference Not Supported Without v. PC With v. PC 2 HCY 11(55 xx Only) BRKDCT-2023 © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 34

Data Center Access Architecture Nexus 5000 & 2232 Deployment Options For Your Reference Not Supported Without v. PC With v. PC 2 HCY 11(55 xx Only) BRKDCT-2023 © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 35

Data Center Access Architecture Nexus 7000 & 2248/2232 Deployment Options N 7 K Cairo NX-OS – Q 4 CY 10 N 7 K Delhi NX-OS - Q 1 CY 11 active N active Y active stretch active © 2009 Cisco Systems, Inc. All rights reserved. active N N Presentation_ID N 7 K - 2 HCY 2011 (pre CC) Y Y active For Your Reference Cisco Confidential active Y active radar

Nexus 2000 Design Agenda § FEXLink and the Virtualized Switch – This material is covered on Day 1 (review as required) § Nexus 2000 Feature Support § High Availability and Switch Configurations § Server Redundancy § Spanning Tree and FEX § Support for enhanced edge capabilities (L 3, FCo. E, Fabric. Path) § Impact on Network Topology Presentation_ID © 2009 Cisco Systems, Inc. All rights reserved. Cisco Confidential 1 K Cisco Nexus x 86

Nexus Virtualized Access Switch Nexus STP Design Considerations § Access design needs to take into account topology and hardware capabilities of the current generation FEX § Currently all Fabric Extender server ports are hard coded as STP edge ports Fabric Extender ports are STP edge ports, BPDU Guard is enabled, downstream devices can not generate BPDU’s. § BPDU Guard is enabled and can not be disabled § Global BPDU Filtering is enabled on the Nexus 2000 HIF ports by default § Interface level BPDU Filtering can be configured § Edge ports DO count against the STP logical port count Data Center Access Cisco Confidential - Internal Only Flexlink or BPDU Filtering VM VMK SC 38

Nexus Virtualized Access Switch Nexus 2000 Design Considerations § N 2 K HIF ports have BPDU Guard enabled by default (it is not possible to disable currently) § If a BPDU is received port will transition to err-disable state § Global BPDU Filter compliments BPDU Guard § On link up port will send 10 -12 BPDUs and then stop (in order to reduce CPU load) § If BPDU is received the port will err-disable § This is NOT interface level BPDU Filtering E 2. BPDU Sent on Link-Up Port 1945 (Ethernet 155/1/25, v. PC) of MST 0000 is designated forwarding Port path cost 200, Port priority 128, Port Identifier 128. 1945 <snip> The port type is edge Link type is point-to-point by default, Internal Bpdu guard is enabled Bpdu filter is enabled by default PVST Simulation is enabled by default BPDU: sent 11, received 0 © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public E 1. XConnected patch cable dc 11 -5020 -3# show spanning-tree int eth 155/1/25 detail BRKDCT-2023 E 3. BPDU Guard errdisables edge port and prevents loop 4. BPDU are not sent once link is up and active 39

Nexus Virtualized Access Switch Nexus 2000 Design Considerations STP Logical Ports § Logical Ports = (# Trunks) x (# VLANs per trunk) § Nexus 7000 STP logical port scaling: Rapid-PVST+ limit = 16, 000* MST limit = 75, 000* § Nexus 5000 STP logical port scaling: Rapid-PVST+ limit = 12, 000* MST limit = 12, 000* Key Point: Ensure you count EDGE & EDGE TRUNK ports too a HW (Line Card, ASIC) limitation, SW improvements will increase this number, CPU upgrades will also increase scal © 2009 Cisco Systems, Inc. All rights reserved. Cisco Confidential 40

Nexus Virtualized Access Switch Stub Layer 2 Devices § When connecting any device to Nexus 2000 HIF ports ensure that the ‘stub’ switch is not running STP on the uplinks § Single homed with BPDU filtering enabled on the uplink § Dual homed with v. PC and BPDU filtering enabled on the port channel § Dual homed with Flexlink § These are supported designs BPDU Filtering § THESE ARE NOT RECOMMENED DESIGNS Data Center Access Cisco Confidential - Internal Only v. PC + BPDU Filtering Flexlink 41

Nexus Virtualized Access Switch Stub Layer 2 Devices § BPDU filtering on the uplinks of ‘stub’ switches enables connectivity to Nexus HIF ports § It is recommended that you do not disable STP on the ‘stub’ switches § Leverage port security, storm control, BPDU Guard and where appropriate 802. 1 x on ‘stub’ switch access ports Dual homed v. PC direct to N 5 K BPDU Filtering interface Gigabit. Ethernet 0/1 switchport trunk native vlan 100 switchport trunk allowed vlan 100, 200 switchport mode trunk spanning-tree bpdufilter enable Data Center Access v. PC + BPDU Filtering Flexlink interface Port-channel 1 switchport trunk native vlan 100 switchport trunk allowed vlan 100, 200 switchport mode trunk spanning-tree bpdufilter enable Cisco Confidential - Internal Only 42

Nexus Virtualized Access Switch Stub Layer 2 Devices § Design Topologies that do not require STP for downstream link recovery can be configured § Flexlink is one option for connecting a downstream switch that is STP independent § Flexlink disables Spanning Tree on the active and backup interfaces § BPDUs are dropped in HW on ingress and not transmitted upstream on the ‘flexlink’ ports BPDU Filtering v. PC + BPDU Filtering Flexlink interface Gigabit. Ethernet 0/1 switchport trunk native vlan 100 switchport trunk allowed vlan 100, 200 switchport mode trunk switchport backup interface Gi 0/2 multicast fast-convergence switchport backup interface Gi 0/2 prefer vlan 200 Data Center Access Cisco Confidential - Internal Only 43

Nexus Virtualized Access Switch Stub Layer 2 Devices § Spanning Tree should ‘not’ be disabled on either the Nexus 5000 nor the downstream switches (e. g. Cisco 2960) § DO NOT extend the downstream device topology (External devices can still create loops in the topology) § Harden the ‘stub’ switch access ports § This design suitable only for highly controlled environments § 1 GE Blade Switches interface Fast. Ethernet 0/24 switchport access vlan 200 switchport mode access switchport-security violation protect storm-control broadcast level pps 1 k storm-control multicast level pps 1 k spanning-tree bpduguard enable Data Center Access Cisco Confidential - Internal Only 44

Nexus 2000 Design Agenda § FEXLink and the Virtualized Switch – This material is covered on Day 1 (review as required) § Nexus 2000 Feature Support § High Availability and Switch Configurations 1 K Cisco Nexus x 86 § Server Redundancy § Spanning Tree and FEX § Support for enhanced edge capabilities (L 3, FCo. E, Fabric. Path) § Impact on Network Topology Data Center Access Cisco Confidential - Internal Only 45

Virtualized Access Switch - FCo. E Extending FCo. E – Nexus 2232 SAN A § FEX-2232 extends the reach of 10 Gig Ethernet/FCo. E to distributed line card (To. R) • Support for up to 384 10 Gig/FCo. E attached hosts managed by a single Nexus 5000 • Nexus 5000 is the FCF or can be in FIP Snooping + mode (when supported) • Currently Nexus 2232 needs to be single homed to upstream Nexus 5000 (straight through N 2 K) to ensure SAN ‘A’ and SAN ‘B’ isolation • Server Ethernet driver connected to the FEX in NIC Teaming (AFT, TLB) or with v. PC (802. 3 ad) Data Center Access SAN B Nexus 5000 as FCF or as E-NPV device Nexus 5000 Fabric Links Option 1: Single Homed Port Channel Nexus 2232 10 GE FEX Fabric Links Option 2: Static Pinned Nexus 2232 10 GE FEX Server Option 2: FCo. E on a v. PC member PC with a single link Cisco Confidential - Internal Only Requires FIP enabled CNAs Server Option 1: FCo. E on individual links. Ethernet traffic is Active/Standb y 46

Virtualized Access Switch - FCo. E Extending FCo. E – Nexus 2232 SAN A SAN B § It is possible to attach DCB capable blade switches to 10 G FEX ports (2232) § Same high availability design rules must be followed § Native Ethernet links from Nexus 4000 to FEX can be individual links or port-channeled § FCo. E links from Nexus 4000 to FEX can be single links or a single port-channel § FEX must be single homed to upstream Nexus 5000 § Not a recommended design due to difficulties in planning for oversubscription of LAN and SAN (including FLOGI scalability) Data Center Access Not Currently Recommended Nexus 5000 Nexus 2232 10 GE FEX BPDU Guard on Need BPDU N 2 K server is Filter onports IP N 4 k uplinks currently hard coded Single Homed Unified Wire Need BPDU Filter on N 4 k uplinks Cisco Confidential - Internal Only Nexus 5000 as FCF or as E-NPV device Nexus 5000 STP Edge Ports Dedicated FCo. E links STP not running on FCo. E VLAN FIP Snooping Nexus 4000 DCB Blade Switch 47

Virtualized Access Switch Nexus 7000 & Nexus 2232 § Nexus 7000 + Nexus 2232 provides 10 G classical Ethernet connectivity • Leverage existing SAN infrastructure SAN A SAN B • FCo. E is planned to be supported with the use of F 2 series line cards (2 HCY 11) Nexus 7000 Nexus 2232 10 GE FEX Data Center Access Cisco Confidential - Internal Only 48

Virtualized Access Switch Nexus 7000 Fabric. Path (Q 4 CY 10) § Fabric. Path is a ‘Routed’ layer 2 topology Fabric. Path – Migration to a ‘Routed’ Layer 2 Data Center Fabric § Flexibility of layer 2 to support compute workload migration and applications requirement § Scalability of routed fabric § Availability of a routed fabric § Nexus 7000 parent switch with F 1 and M 1 line cards will ‘not’ allow the use of Fabric. Path with attached FEX § Support for Fabric. Path with N 2 K is planned for F 2 (2 HCY 11) § ‘Ships in the Night’ support for FCo. E (Q 1 CY 11) Data Center Access Cisco Confidential - Internal Only Servers 49

Virtualized Access Switch Nexus 5500 & Nexus 2000 Fabric. Path – Migration to a ‘Routed’ Layer 2 Data Center Fabric § Fabric. Path is a ‘Routed’ layer 2 topology § Flexibility of layer 2 to support compute workload migration and applications requirement § Scalability of routed fabric § Availability of a routed fabric § Nexus 5500 parent switch will allow the use of Fabric. Path with attached FEX – 2 HCY 11 § Supported with all Nexus 2000 § No support planned for Nexus 5000 (5010/5020) § ‘Ships in the Night’ support for FCo. E Data Center Access FC Attached Storage Servers, FCo. E attached Storage Cisco Confidential - Internal Only Servers 50

Virtualized Access Switch Nexus 7000 & Nexus 2000 – Routed Access (Q 4 CY 10) § Routed Access support with Nexus 7000 and FEX (Q 4 CY 10) Layer 3 uplinks • Leverage existing SAN infrastructure • FCo. E is planned to be supported with the use of F 2 series line cards (2 HCY 11) SAN A SAN B L 3 L 2 Data Center Access Cisco Confidential - Internal Only 51

Virtualized Access Switch Nexus 5500 & Nexus 2000 – Routed Access (Q 1 CY 11) § Support for Routed Access Topologies with Nexus 5500 & Nexus 2000 (Q 1 CY 11) § Supported with all Nexus 2000 § No support planned for Nexus 5000 § ‘Ships in the Night’ support for FCo. E L 3 L 2 FC Attached Storage Servers, FCo. E attached Storage Data Center Access Cisco Confidential - Internal Only Servers 52

For More Information § SAVBU N 5 k/N 2 k webpage http: //savbu. cisco. com/index. php/nexus-5 k-homepage-side § Nexus bootcamp training slide and VOD http: //savbu. cisco. com/index. php/boot-camps/1167 -savbutmepm-led-bootcamps § QA alias ask-nexus 5000 -tme@cisco. com ask-nexus 5000 -pm@cisco. com Data Center Access Cisco Confidential - Internal Only 53

BRKARC-3452_c 1 © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 54