Top Banner
1 © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 1 State of the Union for Fibre Channel and Fibre Channel over Ethernet Standards J Metz, Ph.D – Sr. Product Manager @drjmetz
27

State of the Union for Fibre Channel and Fibre Channel over Ethernet Standards

Jun 27, 2015

Download

Technology

State of the Union for Fibre Channel and Fibre Channel over Ethernet Standards presentation from VMworld Barcelona 2013.
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
  • 1. State of the Union for Fibre Channel and Fibre Channel over Ethernet Standards J Metz, Ph.D Sr. Product Manager@drjmetz 2010 Cisco and/or its affiliates. All rights reserved.Cisco Confidential1

2. Agenda What's New in the Fibre Channel and FCoE World New ways to connect devices together New ways to zone New ways to architect topologiesState of the Standards 2013 Cisco and/or its affiliates. All rights reserved.Cisco Public2 3. How to Use Standards First Things First! Standards are designed to solve a particular problem If you don't have that problem, you don't need a standard way to solve it! 2013 Cisco and/or its affiliates. All rights reserved.Cisco Public3 4. Where Are We Now? What's Already Been Done? 2010 Cisco and/or its affiliates. All rights reserved.Cisco Confidential4 5. FC-BB-5 The Grand-daddy of FCoE Standards Allows you to put Fibre Channel frames onto Ethernet topologies Can duplicate Fibre Channel topologies Requires a "Fibre Channel Forwarder" (FCF) somewhere -Devices need to be connected either directly or indirectly through a FIP-Snooping BridgeState of the Standards 2013 Cisco and/or its affiliates. All rights reserved.Cisco Public5 6. FC-BB-6 Adding more tools to the toolbox "How do you connect an initiator and a target without using an FCF?" -BB6 Answer: PT2PT; VN2VN "How do you address scalability questions of Domain ID sprawl" -BB6 Answer: FCoE Data-Plane Forwarder (FDFs)State of the Standards 2013 Cisco and/or its affiliates. All rights reserved.Cisco Public6 7. New Ways to Connect with FCoE VN2VN and PT2PT 2010 Cisco and/or its affiliates. All rights reserved.Cisco Confidential7 8. PT2PT How do you connect an initiator directly to a target? If you want to connect two devices -And only two!Like Fibre Channel, can connect directly together -Same thing as FC point-to-point Unlike Fibre Channel, can be connected through a (lossless DCB Ethernet) bridge DCB CloudState of the Standards 2013 Cisco and/or its affiliates. All rights reserved.Cisco Public8 9. PT2PT Plusses and Minuses Plus: -No switch needed -Very fast initialization -Useful for Mainframe environments -Designed to support any two ports in a L2 segment -Can operate independently of the type of Link Aggregation usedDCB CloudMinus: -No protection provided by zoning -No notification via RSCN if other devices should disappear or re-appear -Dependent on Link Keepalives (LKAs) and Advertisements for discoveryState of the Standards 2013 Cisco and/or its affiliates. All rights reserved.Cisco Public9 10. VN2VN Loopy loopy Similar to Fibre Channel Arbitrated Loop (FC-AL)Allows for multiple ports to communicate in a peer-to-peer manner Can connect through a lossless DCB Ethernet Layer 2 network/cloudFCoE InitiatorsState of the Standards 2013 Cisco and/or its affiliates. All rights reserved.FCoE TargetsCisco Public10 11. VN2VN Plusses and Minuses Plusses -No switch needed -Designed to support any two ports in a L2 segment -Can operate independently of the type of Link Aggregation usedMinuses -Same limitations as PT2PT, plus... -Each VN_Port needs to keep track of all logins I.e., each node keeps a copy of the entire name serverFCoE InitiatorsFCoE Targets-Each login takes time "Multiple" devices doesn't mean "many" devices State of the Standards 2013 Cisco and/or its affiliates. All rights reserved.Cisco Public11 12. New Topologies Introducing the FCoE Data Forwarder (FDF) 2010 Cisco and/or its affiliates. All rights reserved.Cisco Confidential12 13. FDF How do you handle Domain ID sprawl? Each switch has a Domain ID -You can only have 239 per fabric!FCFFCFFCFFCFFCF 2013 Cisco and/or its affiliates. All rights reserved.Cisco Public13 14. FDF How do you handle Domain ID sprawl? FCFFCFEach switch has a Domain ID -You can only have 239 per fabric!FCFFCF FCFFCF FCFThis can be a problem in blade systems which have their own switchesFCFFCFFCFFCFFCF 2013 Cisco and/or its affiliates. All rights reserved.Cisco Public14 15. FDF How do you handle Domain ID sprawl? Instead, you have a "FCoE Data Forwarder" instead of a full switch in the blades FCFFCFState of the Standards 2013 Cisco and/or its affiliates. All rights reserved.Cisco Public15 16. FDF How do you handle Domain ID sprawl? Instead, you have a "FCoE Data Forwarder" instead of a full switch in the bladesSAN AFDF FCFFDFThese are the "brains" of the fabric -Instructs the FDFs how to behaveFDF FDFFDFState of the StandardsThere are two "Controlling FCFs" -So only two DomainIDsFCFFull FC visibility throughout fabricSAN B 2013 Cisco and/or its affiliates. All rights reserved.Cisco Public16 17. FCoE NPV Similar method to avoiding DomainID sprawl Mechanisms are different, but end result is the sameSAN AFCoE NPVFCoE NPVUpstream NPIV "Controlling FCFs" -So only two DomainIDsFCoE NPVThese are the "brains" of the fabric -Maintain zoning, fabric logins, etcFCF NPIVFCoE NPVFCoE NPVState of the StandardsFCF NPIVFull FC visibility throughout fabricSAN B 2013 Cisco and/or its affiliates. All rights reserved.Cisco Public17 18. New Ways to Zone Peer-Based Zoning 2010 Cisco and/or its affiliates. All rights reserved.Cisco Confidential18 19. Peer Based Zoning/Target Driven Zoning Targeting the Stress Zone Written by Cisco and EMC in the T11 CommitteeEffort to eliminate the manual task of zoningState of the Standards 2013 Cisco and/or its affiliates. All rights reserved.Cisco Public19 20. Problems with Open Zones (i.e., No Zones) Registered State Change Notifications (RCSNs) Any time a device is added to a fabric, everyone gets notifiedState of the Standards 2013 Cisco and/or its affiliates. All rights reserved.Cisco Public20 21. Problems with Open Zones (i.e., No Zones) Registered State Change Notifications (RCSNs) Any time a device is added to a fabric, everyone gets notifiedLikewise, any time a device leaves a fabric, everyone gets notifiedState of the Standards 2013 Cisco and/or its affiliates. All rights reserved.Cisco Public21 22. Problems with Open Zones (i.e., No Zones) Registered State Change Notifications (RCSNs) Any time a device is added to a fabric, everyone gets notifiedLikewise, any time a device leaves a fabric, everyone gets notified Too many devices mean that everyone keeps hitting the Name Server, effectively creating a Denial of Service attackState of the Standards 2013 Cisco and/or its affiliates. All rights reserved.Cisco Public22 23. A-Zoning We Will Go Segmentation and IsolationZone 1Zone 2Zoning isolates these notifications to only those members But... it is painstaking work State of the Standards 2013 Cisco and/or its affiliates. All rights reserved.Cisco Public23 24. What If... We only had RSCNs communicated between the host and the target it's logged into? The target told the switch to only send RSCNs to its logged-in hosts? Come to think of it... The target has a list of approved hosts anyway Why not have it tell the switch to create a zone based on that info? It's so crazy it might just work! ... and it does!Zoneset: WWN1WWN1WWN2WWN2 WWN3...WWN3State of the Standards 2013 Cisco and/or its affiliates. All rights reserved.Zone "TDZ"Cisco Public24 25. Summary Always improving capabilities New ways to connect -Direct attached -Loops New Topologies -Scaling out FCoE fabrics New Zoning -Target drives the zones Watch the Law of the Hammer -Not everything is a nailState of the Standards 2013 Cisco and/or its affiliates. All rights reserved.Cisco Public25 26. Visit Cisco Booth D209 Twitter: @ciscoDC, #vmworld 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: http://www.linkedin.com search Cisco Data Center group Google +: http://goo.gl/irm4b In Collaboration with Intel Intel, the Intel logo, Xeon and Xeon inside are trademarks of Intel Corporation in the U.S. and other countries. 27. 2010 Cisco and/or its affiliates. All rights reserved.Cisco Confidential27