Dynamic FCoE
J Metz, Ph.D
Sr. Product Manager, Data Center Group
2© 2013-2014 Cisco and/or its affiliates. All rights reserved.
Table of Contents
Quick History
What Is Dynamic FCoE?
How It Works
3© 2013-2014 Cisco and/or its affiliates. All rights reserved.© 2013-2014 Cisco and/or its affiliates. All rights reserved.
Using Fibre Channel over Ethernet to Provide Consolidated I/O
History of Convergence
Traditional Data Centers had separation at the host Separate Ethernet-based networks and
Fibre Channel-based networks Multiple cards per server
2 HBAs Average of 6 (or more!) NICs per server High underutilization drives up unnecessary
power, cooling, and asset costs
* not to scale
4© 2013-2014 Cisco and/or its affiliates. All rights reserved.© 2013-2014 Cisco and/or its affiliates. All rights reserved.
Using Fibre Channel over Ethernet to Provide Consolidated I/O
History of Convergence
Access-Layer Convergence Consolidate I/O on 10G links Drastically reduced CapEx and OpEx Multiprotocol connectivity eased
purchasing decisions for server refreshes
Prepared Data Centers for VM mobility requirements Any VM could connect to FC storage if
necessary, not just the ones with HBAs pre-installed
* not to scale
5© 2013-2014 Cisco and/or its affiliates. All rights reserved.© 2013-2014 Cisco and/or its affiliates. All rights reserved.
Using Fibre Channel over Ethernet to Provide Consolidated I/O
History of Convergence
Multihop Convergence Standardize on Ethernet assets
One physical infrastructure Keeps best practices for both Ethernet
and Fibre Channel
Reduction of Additional Equipment
Protected investment and future-proofed deployments
* not to scale
6© 2013-2014 Cisco and/or its affiliates. All rights reserved.
Case Study
Boeing Aerospace and Defense
Reduced deployment times for each server by 25%
Saved 35% in Cap-ex and cut 90% of Power costs “…utilizing the cores better, and increasing I/O with fewer cables and switches” “…use our existing personnel to manage both IP and FCoE resources quickly and efficiently, increasing their value within the
company
CORE
SAN BSAN A
FCoE FCoE
EthernetFibre ChannelDedicated FCoE Converged Link
Multi-Hop FCoE End-to-End FCoE
http://www.cisco.com/en/US/solutions/collateral/ns340/ns517ns224//boeing.pdf
7© 2013-2014 Cisco and/or its affiliates. All rights reserved.
FCoE So far...
Replicating Fibre Channel architectures
Maintain best practices
8© 2013-2014 Cisco and/or its affiliates. All rights reserved.
Is That All?
What’s next!?
Changes in hardware and software are affecting future topologies
• How to address new topologies?• What about multiprotocol storage?• Can we get true consolidated I/O
throughout the fabric?
9© 2013-2014 Cisco and/or its affiliates. All rights reserved.
Introducing
Dynamic FCoE
10
© 2013-2014 Cisco and/or its affiliates. All rights reserved.
What is Dynamic FCoE?
Standard Fibre Channel over Ethernet that uses FabricPath forwarding for: Greater resilience Faster fabric convergence Higher scalability
Why is it “Dynamic?” Links between switches (Inter-Switch
Links) are dynamically created between end-points Fewer configuration errors
Fabric Ports are dynamically configured to create “virtual Fibre Channel” interfaces
FCoE as Storage Network Overlay
11
© 2013-2014 Cisco and/or its affiliates. All rights reserved.
Leaf
Spine
How to address new topologies?
Evolution of Ethernet Fabrics
What about multiprotocol storage?
Can we get true consolidated I/O throughout the fabric?
Access/Aggregation/Core Leaf/Spine
Access
Aggregation
Core
40/100GbE
12
© 2013-2014 Cisco and/or its affiliates. All rights reserved.
Reliability and Resilience at Greater Scale
Why Use Dynamic FCoE?
Use Ethernet Equal-Cost Multipathing (ECMP) to provide load-balanced traffic across entire topology
Greater resiliency and robustness across core (spine)
Dynamic configuration of Inter-Switch Links (ISLs)
iSCSI/NFS FCoE
FibreChannel
MultiprotocolServer
13
© 2013-2014 Cisco and/or its affiliates. All rights reserved.
Evolution of Convergence
Use IEEE ETS to guarantee bandwidth for traffic types
Use IEEE PFC to create lossless traffic for FCoE
Use advanced Ethernet fabric forwarding for ECMP traffic flows
Use Ethernet infrastructure for all kinds of storage (including connections to traditional FC storage environments)
Increase IT agility and operational and resource efficiency while speeding delivery of services to application owners
Improve scalability for all application needs and maintain high, consistent performance for all traffic types, not just storage
14
© 2013-2014 Cisco and/or its affiliates. All rights reserved.
How does it work?
15
© 2013-2014 Cisco and/or its affiliates. All rights reserved.
Rethinking Storage Networking
Typical Fibre Channel topology: Edge/Core/Edge not
uncommon
Dual SANs for Redundancy
SAN A SAN B
16
© 2013-2014 Cisco and/or its affiliates. All rights reserved.
Rethinking Storage Networking
Typical Fibre Channel topology: Edge/Core/Edge not
uncommon
Dual SANs for Redundancy If path breaks or core
switch goes down, SAN fails over to SAN B
SAN A SAN BX
17
© 2013-2014 Cisco and/or its affiliates. All rights reserved.
Rethinking Storage Networking
Typical Fibre Channel topology: Edge/Core/Edge not
uncommon
Dual SANs for Redundancy If path breaks or core
switch goes down, SAN fails over to SAN B
Meaning, if a core switch goes down, the entire SAN side goes down
SAN A SAN BX
18
Logical Separation of SAN A/B
Storage nodes reside on the leafs
SAN A/B separation occurs at the most vulnerable part of the network – the server to the access layer switch (i.e., leaf)
What the topology is
© 2013-2014 Cisco and/or its affiliates. All rights reserved.
19
Logical Separation of SAN A/B
Storage sees an edge-core topology equivalence
Complete, load-balance ISLs dynamically created between FCF leafs
What Fibre Channel sees
© 2013-2014 Cisco and/or its affiliates. All rights reserved.
20
© 2013-2014 Cisco and/or its affiliates. All rights reserved.
Rethinking Storage Networking
Logical separation instead of physical separation
SAN A SAN B SAN A SAN B
21
© 2013-2014 Cisco and/or its affiliates. All rights reserved.
Rethinking Storage Networking
Logical separation instead of physical separation
Dynamically creates relationships between Fibre Channel Forwarders (FCFs)
SAN A SAN B SAN A SAN B
FCF FCF FCF FCF
22
© 2013-2014 Cisco and/or its affiliates. All rights reserved.
Rethinking Storage Networking
Logical separation instead of physical separation
Dynamically creates relationships between Fibre Channel Forwarders (FCFs)
Dynamically configures the ports for Inter-Switch Links (ISLs)
SAN A SAN B SAN A SAN B
FCF FCF FCF FCF
VE_Port VE_Port
23
© 2013-2014 Cisco and/or its affiliates. All rights reserved.
Rethinking Storage Networking
Logical separation instead of physical separation
Dynamically creates relationships between Fibre Channel Forwarders (FCFs)
Dynamically configures the ports for Inter-Switch Links (ISLs)
Increases redundancy and resiliency Storage traffic is load-
balanced across Equal-Cost Multipathing Topology
SAN A SAN B SAN A SAN B
FCF FCF FCF FCF
VE_Port VE_Port
24
© 2013-2014 Cisco and/or its affiliates. All rights reserved.
Rethinking Storage Networking
Logical separation instead of physical separation
Dynamically creates relationships between Fibre Channel Forwarders (FCFs)
Dynamically configures the ports for Inter-Switch Links (ISLs)
Increases redundancy and resiliency Storage traffic is load-balanced
across Equal-Cost Multipathing Topology
If a spine switch fails, SAN A is not interrupted!
SAN A SAN B SAN A SAN B
FCF FCF FCF FCF
VE_Port VE_Port
X
25
© 2013-2014 Cisco and/or its affiliates. All rights reserved.
Rethinking Storage Networking
SAN A SAN B SAN A SAN B
FCF FCF FCF FCF
VE_PortVE_Port
X
If a FCF Leaf switch fails, MPIO software fails over as normal
Do not lose entirety of “SAN A” bandwidth capability
26
© 2013-2014 Cisco and/or its affiliates. All rights reserved.
Availability
Dynamic FCoE
Hardware Nexus 5500 (Leaf) - Now! Nexus 5600 (Leaf/Spine) - Now! Nexus 6001 (Leaf/Spine) - Now! Nexus 6004 (Leaf/Spine) - Now! Nexus 7000 (Spine) - Q3 2014 Nexus 7700 (Spine) - Q3 2014
Software R7.0(1)N1(1) - Now!
Nexus 5500
Nexus 5672
Nexus 56128
Nexus 6004
Nexus 6001
27
© 2013-2014 Cisco and/or its affiliates. All rights reserved.
Allows maximum convergence with leaf/spine topologies Maximizes bandwidth Inherently scalable Capitalizes on 40/100G Ethernet backbones (when
available) Deterministic, predictable performance across network
Does not change well-understood Fibre Channel rules: In-order delivery Error recovery Load balancing Failover
Adds to the list of flexible deployment options Optimal for East-West network deployments Compatible with Classical “hybrid” multihop solutions Ideal for “pod” environments, with or without high degree of
VM mobility
Dynamic FCoE Summary
Thank you.
29
© 2013-2014 Cisco and/or its affiliates. All rights reserved.
Cisco Data Center Social Map
Twitter: @ciscoDC
Facebook: http://www.facebook.com/CiscoDC
Youtube: http://www.youtubecisco.com/datacenter
Cisco DCC Blog: http://blogs.cisco.com/datacenter
Slideshare: http://slideshare.com/CiscoDataCenter
Community: https://communities.cisco.com/community/technology/datacenter
Pinterest: http://pinterest.com/ciscosystems/data-center
LinkedIn: https://www.linkedin.com/company/cisco-data-center-and-cloud
Google +: http://goo.gl/irm4b
Top Related