Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

State of the union

961 views

Published on

Cisco Theater presentation from Emc World 2013

Published in: Technology, Education

Comments are closed

  • Be the first to comment

  • Be the first to like this

State of the union

  1. 1. 1© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 1State of the Union for Fibre Channel and FibreChannel over Ethernet StandardsJ MetzCo-Sponsoredby Intel®
  2. 2. 2© 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicWhats New in the Fibre Channel and FCoE WorldAgendaNew ways to connect devices togetherNew ways to zoneNew ways to architect topologies
  3. 3. 3© 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicFirst Things First!How to Use StandardsStandards are designed to solve a particular problemIf you dont have that problem, you dont need astandard way to solve it!
  4. 4. 4© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential© 2010 Cisco and/or its affiliates. All rights reserved. Cisco ConfidentialWhere Are We Now?Whats Already Been Done?4
  5. 5. 5© 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicThe Grand-daddy of FCoE StandardsFC-BB-5Allows you to put Fibre Channel frames onto Ethernet topologiesCan duplicate Fibre Channel topologiesRequires a "Fibre Channel Forwarder" (FCF) somewhere-Devices need to be connected either directly or indirectly through a FIP-Snooping Bridge
  6. 6. 6© 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicAdding more tools to the toolboxFC-BB-6"How do you connect an initiator and atarget without using an FCF?"-BB6 Answer: PT2PT; VN2VN"How do you address scalabilityquestions of Domain ID sprawl"-BB6 Answer: FCoE Data-Plane Forwarder(FDFs)
  7. 7. 7© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential© 2010 Cisco and/or its affiliates. All rights reserved. Cisco ConfidentialNew Ways to Connect with FCoEVN2VN and PT2PT7
  8. 8. 8© 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicHow do you connect an initiator directly to a target?PT2PTIf you want to connect two devices-And only two!Like Fibre Channel, can connect directlytogether-Same thing as FC point-to-pointUnlike Fibre Channel, can be connectedthrough a (lossless DCB Ethernet) bridgeDCB Cloud
  9. 9. 9© 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicPlusses and MinusesPT2PTPlus:-No switch needed-Very fast initialization-Useful for Mainframe environments-Designed to support any two ports in a L2segment-Can operate independently of the type of LinkAggregation usedMinus:-No protection provided by zoning-No notification via RSCN if other devicesshould disappear or re-appear-Dependent on Link Keepalives (LKAs) andAdvertisements for discoveryDCB Cloud
  10. 10. 10© 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicLoopy loopyVN2VNSimilar to Fibre Channel Arbitrated Loop(FC-AL)Allows for multiple ports tocommunicate in a peer-to-peer mannerCan connect through a lossless DCBEthernet Layer 2 network/cloudFCoEInitiatorsFCoETargets
  11. 11. 11© 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicPlusses and MinusesVN2VNPlusses-No switch needed-Designed to support any two ports in a L2segment-Can operate independently of the type ofLink Aggregation usedMinuses-Same limitations as PT2PT, plus...-Each VN_Port needs to keep track of alllogins•I.e., each node keeps a copy of the entirename server-Each login takes time•"Multiple" devices doesnt mean "many"devicesFCoEInitiatorsFCoETargets
  12. 12. 12© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential© 2010 Cisco and/or its affiliates. All rights reserved. Cisco ConfidentialNew TopologiesIntroducing the FCoE Data Forwarder (FDF)12
  13. 13. 13© 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicHow do you handle Domain ID sprawl?FDFEach switch has a Domain ID-You can only have 239 per fabric!FCFFCFFCFFCFFCF
  14. 14. 14© 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicHow do you handle Domain ID sprawl?FDFEach switch has a Domain ID-You can only have 239 per fabric!This can be a problem in bladesystems which have their ownswitchesFCFFCFFCFFCFFCFFCFFCFFCFFCFFCFFCFFCF
  15. 15. 15© 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicHow do you handle Domain ID sprawl?FDFInstead, you have a "FCoE DataForwarder" instead of a full switchin the bladesFCFFCF
  16. 16. 16© 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicHow do you handle Domain ID sprawl?FDFInstead, you have a "FCoE DataForwarder" instead of a full switchin the bladesThere are two "Controlling FCFs"-So only two DomainIDsThese are the "brains" of the fabric-Instructs the FDFs how to behaveFull FC visibility throughout fabricFDFFDFFDFFDFFDFSAN ASAN BFCFFCF
  17. 17. 17© 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicSimilar method to avoiding DomainID sprawlFCoE NPVMechanisms are different, but endresult is the sameUpstream NPIV "Controlling FCFs"-So only two DomainIDsThese are the "brains" of the fabric-Maintain zoning, fabric logins, etcFull FC visibility throughout fabricFCoE NPVFCoE NPVFCoE NPVFCoE NPVFCoE NPVSAN ASAN BFCF NPIVFCF NPIV
  18. 18. 18© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential© 2010 Cisco and/or its affiliates. All rights reserved. Cisco ConfidentialNew Ways to ZonePeer-Based Zoning18
  19. 19. 19© 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicSomething funny and punny herePeer Based Zoning/Target Driven ZoningWritten by Cisco and EMC in the T11 CommitteeEffort to eliminate the manual task of zoning
  20. 20. 20© 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicRegistered State Change Notifications (RCSNs)Problems with Open Zones (i.e., No Zones)Any time a device is added toa fabric, everyone gets notified
  21. 21. 21© 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicRegistered State Change Notifications (RCSNs)Problems with Open Zones (i.e., No Zones)Any time a device is added toa fabric, everyone gets notifiedLikewise, any time a deviceleaves a fabric, everyone getsnotified
  22. 22. 22© 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicRegistered State Change Notifications (RCSNs)Problems with Open Zones (i.e., No Zones)Any time a device is added toa fabric, everyone gets notifiedLikewise, any time a deviceleaves a fabric, everyone getsnotifiedToo many devices mean thateveryone keeps hitting theName Server, effectivelycreating a Denial of Serviceattack
  23. 23. 23© 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicSegmentation and IsolationA-Zoning We Will GoZoning isolates these notifications to only those membersBut... it is painstaking workZone 1Zone 2
  24. 24. 24© 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicWhat If... We only had RSCNs communicated between the host and the target its 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? Its so crazy it might just work!– ... and it does!Zoneset:WWN1WWN2WWN3...WWN1WWN2WWN3Zone "TDZ"
  25. 25. 25© 2013 Cisco and/or its affiliates. All rights reserved. Cisco PublicAlways improving capabilitiesSummaryNew ways to connect-Direct attached-LoopsNew Topologies-Scaling out FCoE fabricsNew Zoning-Target drives the zonesWatch the Law of the Hammer-Not everything is a nail
  26. 26. Visit Cisco Booth 401Twitter: @ciscoDCFacebook.com/CiscoDCVideo: http://www.youtubecisco.com/datacenterCisco blog: http://blogs.cisco.com/datacenterSlideshare: http://slideshare.com/CiscoDataCenterIn Collaboration with Intel®Intel and the Intel logo are trademarks of Intel Corporation in the U.S. and/or other countries.
  27. 27. 27© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 27

×