Nexus DC Tec. Tomas Novak. BDM Sponsor. Sponsor. Sponsor Logo. Sponsor. Logo. Logo. Logo

Size: px

Start display at page:

Download "Nexus DC Tec. Tomas Novak. BDM Sponsor. Sponsor. Sponsor Logo. Sponsor. Logo. Logo. Logo"

Lee Ryan
5 years ago
Views:

1 Nexus DC Tec Tomas Novak BDM Sponsor Sponsor Sponsor Sponsor Logo Logo Logo Logo CIscoEXPO 1

2 Agenda Nexus 2000 update FEX designs FCoE designs 2

3 Agenda Nexus 2000 update FEX designs FCoE designs 3

Nexus 5000 + FEX Single Access Layer Nexus 5000 Parent Switch + Cisco Nexus 2000 FEX = Virtual Modular System Nexus 5000 + FEX combines logically as a Virtual

4 Nexus FEX Single Access Layer Nexus 5000 Parent Switch + Cisco Nexus 2000 FEX = Virtual Modular System Nexus FEX combines logically as a Virtual Modular System Nexus 2000 FEX is a Virtual Line Card to the Nexus 5000 Nexus 5000 maintains all management & configuration No Spanning Tree between FEX & Nexus

5 GE Fabric Extender highlights (N2248) 4 10GE SFP+ Uplinks /1000 RJ45 Downlinks 1. GE Fabric Extender 48x 100/1000M host interfaces; 4x 10GE on network interfaces Can mix-and-match with existing GE and next-gen GE FEX in network topologies 2. Host port-channel support 3. SPAN source/destination support 5

6 10GE Fabric Extender Highlights (N2232) 32 10GE/FCoE SFP+ Downlinks 8 10GE/FCoE SFP+ Uplinks 1.32x 1/10GE host interfaces; 8x 10GE on network interfaces 10GE interfaces support FCoE 2.Can mix-and-match with existing GE and next-gen GE FEX in network topologies 3.Host port-channel support 4.SPAN source/destination support 6

Cisco Nexus 2000 Fabric Extender (FEX) Platform Update Model Nexus 2148T Nexus 2248TP Nexus 2232PP Product Shipping Yes Q2CY10 Q2CY10 Form Factor 1 RU 1 RU 1 RU Uplink Ports 4 x 10GbE SFP+ 4 x 10GbE

7 Cisco Nexus 2000 Fabric Extender (FEX) Platform Update Model Nexus 2148T Nexus 2248TP Nexus 2232PP Product Shipping Yes Q2CY10 Q2CY10 Form Factor 1 RU 1 RU 1 RU Uplink Ports 4 x 10GbE SFP+ 4 x 10GbE SFP+ 8 x 10GbE SFP+ Uplink Transceivers Supported Host Facing Ports 48 x 1GbE RJ45 (note: 1000BaseT only) Copper CX-1 (passive): 1m, 3m, 5m. Optical: SR, LR [distance limited to 300m] 48 x 100/1000Base-T RJ45 32 x SFP+ (10G) (note: hw capable of 1GE SFP) FCoE N/A N/A Yes Dimensions 1.72 x 17.3 x 20.0 in 1.72 x 17.3 x 17.7in 1.72 x 17.3 x 17.7 in Operational Power 165W 110W 270W Power Supply N2K-PAC-200W N2K-PAC-400W N2K-PAC-400W Multiple PortChannel member ports on a FEX Not Supported Yes Yes 7

8 Nexus 2148T versus 2232 versus 2248 Features 2148T Host ports Fabric Ports Port speed 1 GigE only 10Gbps 1Gbps/100Mb Each port independent Etherchannels on Fabric Links Yes Hash up to L3 fields Yes 8 ports maximum Hash up to L4 ports Yes 8 ports maximum Hash up to L4 ports Etherchannels on Host Interfaces Not Supported Yes 8 ports maximum Hash up to L4 ports Yes 8 ports maximum Hash up to L4 ports #Etherchannels N/A Max 16 Port Channels / FEX 2232 Max 24 Port-Channels / FEX

9 Agenda Nexus 2000 update FEX designs FCoE designs 9

10 FEX topology 1.FEX have predefined Host Interfaces and Fabric ports 2.All traffic between any two ports flows through the upstream device 3.This ensures that most features that are available on the upstream switch are equally available to the FEX ports 4.All Host ports are Configured from the upstream Device N5k01 1,2,3,4 Fabric Ports Host Ports N GigE 10

11 software image, configuration FEX Inner Functioning 1.Fabric extender is discovered by switch using an L2 Satellite Discover Protocol (SDP) that is run on the uplink port of fabric extender 2.NX5K checks software image compatibility, assign an IP address and upgrade the fabric extender if necessary 3.N5K pushes programming data to Fabric Extender N5k01 1,2,3,4 N GigE 11

12 Fabric Extender Fabric Modes Fabric Extender associates (pins) a server side (1GE) port with an uplink (10GE) port 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 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 Static Pinning Port Channel Server Interface goes down Server Interface stays active 13

13 FEX Design Considerations Uplink Dual Homing Without support With support N5K-A N5K-B N5K-A N5K-B SDP exchange Err-disable 14

14 FEX Design Considerations Server Dual Homing provides two redundancy designs for the virtualized access switch Option 1 - MCEC connectivity from the server Two virtualized access switches bundled into a pair Logically a similar HA model to that currently provided by VSS Two Virtualized access switches Each with a Single Supervisor peers MCEC from server to the access switch 15

15 Data Center Access Architecture Redundancy Models Dual Supervisor 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 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 dual homed to redundant Nexus

16 Legacy Designs with FEX 2148T Peer Keepalive Peer Link Member Port Cisco Nexus 2000 Series Straight-Through Cisco Nexus 2000 Active-Active Primary Secondary Primary Secondary Fabric Links Fabric Links FEX100 HIF FEX120 HIF 1 2 FEX100 FEX120 HIF HIF With Cisco Nexus 2148T, 2 Gigabit Ethernet Ports Host PortChannel 17

17 Designs with FEX 2248 Peer Keepalive Peer Link Member Port Cisco Nexus 2000 Series Straight-Through Cisco Nexus 2000 Active-Active Primary Secondary Primary Secondary up to 4 ports Fabric Links up to 4 ports Fabric Links up to 4 ports up to 4 ports FEX100 HIF up to 8 ports FEX120 up to 8 ports HIF up to 24 PC per FEX up to 24 PC per FEX up to 8 ports FEX HIF up to 8 ports FEX120 HIF 18

18 Designs with FEX 2232 Peer Keepalive Peer Link Member Port Cisco Nexus 2000 Series Straight-Through Cisco Nexus 2000 Active-Active Primary Secondary Primary Secondary up to 8 ports Fabric Links up to 8 ports Fabric Links up to 8 ports up to 8 ports FEX100 HIF up to 8 ports FEX120 up to 8 ports HIF up to 16 PC per FEX up to 16 PC per FEX up to 8 ports FEX HIF up to 8 ports FEX120 HIF 19

19 Data Center Access Architecture Virtual Port Channel Design Considerations Two independent configurations are supported on the same N5K upstream to the N7K is independent of the downstream connecting the N2K Independent hashing decisions for the upstream and downstream traffic flows 21

20 Agenda Nexus 2000 update FEX designs FCoE designs 22

21 Current FCoE Deployments Direct Attached Topology Ethernet/LAN Core SAN A SAN B 1.Servers and FCoE targets are directly connected to the Nexus 5000 over 10Gig FCoE Nexus 5000 operates as the FCF FCoE Targets 2.Support for up to 52 10Gig/FCoE attached hosts or FCoE targets per Nexus 5000 Nexus 5000 FCF Nexus 5000 FCF 3.Native Ethernet LAN network and Native Fibre Channel network break off at the Nexus 5000 access layer FIP enabled CNAs FIP or Pre-FIP enabled CNAs Native Fibre Channel Ethernet LAN Enhanced Ethernet and FCoE 23

Current FCoE Deployments Multi-hop FCoE Ethernet/LAN Core Nexus 5000 FCF Blade Chassis SAN A SAN B FCoE Targets Nexus 5000 FCF Nexus 4000: FIP Snooping Bridge CNA mezzanine cards 1.

22 Current FCoE Deployments Multi-hop FCoE Ethernet/LAN Core Nexus 5000 FCF Blade Chassis SAN A SAN B FCoE Targets Nexus 5000 FCF Nexus 4000: FIP Snooping Bridge CNA mezzanine cards 1.Blade servers connect to Nexus 4000 over 10Gig FCoE Nexus 4000 is a FIP-Snooping Bridge 2.Nexus 4000 connects to Nexus 5000 over 10Gig FCoE Nexus 5000 operates as the FCF 3.Support for up to 192 FCoE attached blade servers per Nexus Native Ethernet LAN network and Native Fibre Channel network break off at the Nexus

23 Extending the FCoE Access Layer Supported Directly Attached Topologies Ethernet/LAN Core SAN A SAN B 1.Servers connect to FEX 2232 over 10Gig FCoE Server connections to the FEX can be Active/Standy or over a Nexus 5000 FCF FEX-2232 Nexus 5000 FCF FEX Support for up to Gig/FCoE attached hosts managed by a single Nexus FEX 2232 is single homed to upstream Nexus 5000 FEX 2232 can be connected with individual links or a port-channel FIP enabled CNAs 25

24 Extending the FCoE Access Layer Multi-hop Topologies Ethernet/LAN Core Nexus 5000 FCF FEX-2232 FCoE over an STP Cloud SAN A SAN B Nexus 5000 FCF FEX-2232 Nexus 4000: FIP Snooping Bridge or pass-through 1.Servers connection to the Nexus 4000 is Active/Standby 2.Servers connect to Nexus 4000 over 10Gig FCoE 3.PFC support at every hop to achieve flow-control 4.Support for up to Gig/FCoE attached hosts managed by a single Nexus FEX 2232 is single homed to upstream Nexus 5000 with single links or a port-channel CNA mezzanine cards 26

25 Extending the FCoE Access Layer Multi-hop Topologies Ethernet/LAN Core Nexus 5000 FCF FEX-2232 SAN A SAN B Nexus 5000 FCF FEX-2232 Nexus 4000: FIP Snooping Bridge or pass-through CNA mezzanine cards 1.Servers connection to the Nexus 4000 is Active/Standby 2.Servers connect to Nexus 4000 over 10Gig FCoE Separate 10 Gig links for native Ehetner and FCoE Native Ethernet links can connect to the FEX using single link, portchannel or virtual port-channel FCoE linkes can be connected to FEX using single link or portchannel 3.Support for up to Gig/FCoE attached hosts managed by a single Nexus

26 Optimizing Cabling for FCoE 1.Flexible cabling options can deploy either EOR or TOR 2.FCoE POD size is increased without added points for management 3.TOR cabling to the FEX-2232 with twin-ax offers CAPEX savings 4.EOR deployment of 5000 acts as EOR chassis and leverages existing EOR cabling.... Nexus 5000/2000 Mixed ToR & EoR Combination of EoR and ToR cabling 28

27 29

Design and Implementations of FCoE for the DataCenter. Mike Frase, Cisco Systems

Design and Implementations of FCoE for the DataCenter Mike Frase, Cisco Systems SNIA Legal Notice The material contained in this tutorial is copyrighted by the SNIA unless otherwise noted. Member companies