1 / 56

Architecting Fibre Channel HA Solutions

Architecting Fibre Channel HA Solutions. Rick Jooss richard.jooss@netapp.com. Agenda. CFModes Single System Imagine Multipathing Host Clustering Storage System Backend HA Q&A. Agenda. CFModes Single System Image Multipathing Host Clustering Storage System Backend HA Q&A.

arella
Télécharger la présentation

Architecting Fibre Channel HA Solutions

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Architecting Fibre Channel HA Solutions Rick Jooss richard.jooss@netapp.com

  2. Agenda • CFModes • Single System Imagine • Multipathing • Host Clustering • Storage System Backend HA • Q&A

  3. Agenda • CFModes • Single System Image • Multipathing • Host Clustering • Storage System Backend HA • Q&A

  4. CFMODE – Cluster Failover Mode • What is CFMODE? • FCP Setting • Determines behavior of FC Target Ports, particularly during a CFO event • Why is there more than one CFMODE? • Original CFMODE (standby) did not work for all host types (HP-UX, AIX) • Original CFMODE did not work with the 270C because it only has a single FC port

  5. Available Paths- Standby Mode 0c 0d 0a 0b 0c 0d 0a 0b HA Configuration Controller 1 Controller 2 Host Switch/Fabric 1 Switch/Fabric 2 Solid Blue are paths to the LUNs being served by Controller 1 Dashed Purple are paths to the LUNs being served by Controller 2 LUNs LUNs

  6. Path Access (Switch Failure) – Standby Mode 0c 0d 0a 0b 0c 0d 0a 0b HA Configuration Controller 1 Controller 2 Host MP layer works around the failure Switch/Fabric 1 will experience a failure Switch/Fabric 1 Switch/Fabric 2 Solid and Blue are paths to the LUNs being served by Controller 1 Dashed and Purple are paths to the LUNs being served by Controller 2 LUNs LUNs

  7. Path Access (CFO event)- Standby Mode 0c 0d 0a 0b 0c 0d 0a 0b HA Configuration Controller 1 Controller 2 Host Conntroller 1 will experience a failure Controller 2 Takes over all operations Switch/Fabric 1 Switch/Fabric 2 Solid and Blue are paths to the LUNs being served by Controller 1 Dashed and Purple are paths to the LUNs being served by Controller 2 LUNs LUNs

  8. Path Access (CFO event)- Standby Mode 0c 0d 0a 0b 0c 0d 0a 0b HA Configuration Controller 1 Controller 2 Host Filer Head 2 Takes over all operationsMP layer is not involved in switchover Controller 1 will experience a failure Switch/Fabric 1 Switch/Fabric 2 Solid and Blue are paths to the LUNs being served by Controller 1 WWN1 WWN2 WWN3 WWN4 WWN5 WWN6 WWN7 WWN8 Dashed and Purple are paths to the LUNs being served by Controller 2 LUNs LUNs

  9. Available Paths - Partner Mode Host Switch/Fabric 1 Switch/Fabric 2 Solid Blue are paths to the LUNs being served by Controller 1 Dashed Purple are paths to the LUNs being served by Controller 2 0c 0d 0a 0b 0c 0d 0a 0b HA Configuration Controller 1 Controller 2 LUNs LUNs

  10. Available Paths - Partner Mode – FAS3000 Default Configuration Host Switch/Fabric 1 Switch/Fabric 2 Solid Blue are paths to the LUNs being served by Controller 1 Dashed Purple are paths to the LUNs being served by Controller 2 0c 0d 0c 0d HA Configuration Controller 1 Controller 2 LUNs LUNs

  11. Available Paths - Dual Fabric Host Switch/Fabric 1 Switch/Fabric 2 Solid Blue are paths to the LUNs being served by Controller 1 0c_0 0c_2 0c_2 0c_0 Dashed Purple are paths to the LUNs being served by Controller 2 HA Configuration Controller 1 Controller 2 LUNs LUNs

  12. Agenda • CFModes • Single System Imagine • Multipathing • Host Clustering • Storage System Backend HA • Q&A

  13. What is the single system image cfmode? • Universal cfmode • Works on all HA storage systems • Works on all switches • Presents the HA configuration as a single target • All LUNs are visible on all controller ports • All hosts require multipathing software

  14. Available Paths - Single System Image – Single Card 0c 0d 0c 0d HA Configuration Controller 1 Controller 2 Host Switch/Fabric 1 Switch/Fabric 2 Solid Blue are paths to the LUNs being served by Controller 1 Dashed Purple are paths to the LUNs being served by Controller 2 LUNs LUNs

  15. Path Access (Switch Failure) - Single System Image – Single Card 0c 0d 0c 0d HA Configuration Controller 1 Controller 2 Host Switch/Fabric 1 will experience a failure MP layer works around the failure Switch/Fabric 1 Switch/Fabric 2 Solid and Blue are paths to the LUNs being served by Head 1 Dashed and Purple are paths to the LUNs being served by Head 2 LUNs LUNs

  16. Path Access (CFO event) - Single System Image – Single Card 0c 0d 0c 0d HA Configuration Controller 1 Controller 2 Host Controller 2 takes over all operations MP layer works around the failure Controller 1 will experience a failure Switch/Fabric 1 Switch/Fabric 2 Solid Blue are paths to the LUNs being served by Controller 1 Dashed Purple are paths to the LUNs being served by Controller 2 LUNs LUNs

  17. Available Paths - Single System Image – Single Port Host Switch/Fabric 1 Switch/Fabric 2 Solid Blue are paths to the LUNs being served by Controller 1 0d 0d Dashed Purple are paths to the LUNs being served by Controller 2 HA Configuration Controller 1 Controller 2 LUNs LUNs

  18. Available Paths - Single System Image – Single Port Host Solid Blue are paths to the LUNs being served by Controller 1 Loop Mode Loop Mode 0d 0d Dashed Purple are paths to the LUNs being served by Controller 2 HA Configuration Controller 1 Controller 2 LUNs LUNs

  19. Why SSI mode? • Works in all configurations • Makes us look more like other SAN vendors • Reduces port burn without using FC Loop • Fully redundant config requires only 1 “wire” per controller, instead of 2. • Simpler wiring, no a/b port distinctions and no requirement to run the same cables from each controller to the same switch.

  20. Management changes • Unified LUN mapping address space across the HA configuration. • Controller prevents these conflicts by checking with the partner controller. • If the controller interconnect is down, some operations are disabled by default • Igroup add, lun map, lun online, igroup set ostype

  21. SSI Roadmap • Introduced in ONTAP 7.1 • Refer to FCP host compatibility matrix http://now.netapp.com/NOW/knowledge/docs/san/fcp_iscsi_config/index.shtmlfor specific host support

  22. Agenda • CFModes • Single System Imagine • Multipathing • Host Clustering • Storage System Backend HA • Q&A

  23. Multipathing • Multipathing provides multiple paths from the host to the external storage device • Provides High-Availability • Protects against path failures • Ensures high availability of applications and data by eliminating single points of failure • Provides Improved Performance • Increases potential performance by utilizing multiple paths

  24. Multipathing 0c 0d 0c 0d HA Configuration Controller 1 Controller 2 Host Switch/Fabric 1 Switch/Fabric 2 LUNs LUNs

  25. A/P (active passive) policy – Single LUN 0c 0d 0c 0d HA Configuration Controller 1 Controller 2 Hosts Switch/Fabric 1 Switch/Fabric 2 LUNs LUNs

  26. A/P (active passive) policy – No Round Robining Hosts Switch/Fabric 1 Switch/Fabric 2 0c 0c 0d 0d HA Configuration Controller 1 Controller 2 LUN4 LUN3 LUN2 LUN1

  27. A/P (active passive) policy - Round Robining Hosts Switch/Fabric 1 Switch/Fabric 2 0d 0c 0c 0d HA Configuration Controller 1 Controller 2 LUN4 LUN3 LUN2 LUN1

  28. A/P (active/passive) • Active/Passive Configuration • 1 active path to a single LUN • Performance to a LUN is limited by that paths capability (HBA, switch, target port) • Possible to round robin multiple LUNs across multiple paths • All other paths to the LUN are passive • On failover • Primary paths are tried first • Secondary paths are used if no primary paths are available

  29. A/A (Active active) policy (cfmode = standby) 0c 0d 0a 0b 0c 0d 0a 0b HA Configuration Controller 1 Controller 2 Hosts Switch/Fabric 1 Switch/Fabric 2 LUNs LUNs

  30. A/A (active/active) • Host accessing data from a single LUN across multiple paths simultaneously • Typically used for load balancing • Round Robin • Least Queue Depth • Weighted • On failure I/Os are sent down remaining available paths

  31. A/A/A (asymmetric active active) 0c 0d 0c 0d HA Configuration Controller 1 Controller 2 Host Switch/Fabric 1 Switch/Fabric 2 LUNs LUNs

  32. A/A/A (asymmetric active active) • Distinguishes between primary and secondary paths • Does active/active across primary paths only • Only uses secondary paths when no primary are available

  33. NetApp’s Multipathing Strategy • 2 pronged strategy • Support for “native” solutions • What most customers rightly feel best about • Support for host and storage independent solution • VERITAS • Allows common solution across various server as well as storage variants

  34. Multipathing For Windows • Windows MPIO • Uses the Microsoft standard infrastructure • A/P Policy • Automatically chooses primary paths for failover before trying proxy ones • In standby the LUNS are automatically round robined across all paths

  35. MultiPathing For Solaris

  36. MultiPathing For Solaris • VERITAS DMP 4.0 • NetApp ASL 4.0 • Supports A/P, A/A, & A/A/A (Active Passive Concurrent) • SUN Native MPxIO • Not supported with standby cfmode • Supports A/P • Can be A/A but required manual failback • Manual configuration required • Round Robining of the LUNs possible • Sometimes called • Traffic Manager • Leadville Stack

  37. MultiPathing For Linux • Qlogic • A/P Policy • Manually configured • Round Robining of LUNs is possible • DCM • Linux native solution

  38. MultiPathing For AIX

  39. MultiPathing For AIX • SANpath • A/A/A • Automatically chooses primary paths for failover before trying proxy ones • Special policy for SCSI-2 reservation • Required for host clustering HACMP • Can only use A/P • VERITAS DMP 4.0 • Only supports A/A/A • IBM MPIO • IBM native solution with NetApp PCM

  40. Multipathing for HP-UX DMP 3.5 PVLinks

  41. Multipathing for HP-UX • PVlinks/LVM • A/P policy • Single active path per LUN, user controlled • Ordering for remaining paths for failover • ntap_config_paths • NETAPP script to define path ordering based on filer path types: primary, proxy • automatically round robin primary paths among all LUNS • Supports both FCP and iSCSI paths • VERITAS DMP 3.5 • A/P Policy

  42. Multipathing for VMware • VMware • A/P Policy • Manually configured • Round Robining of LUNs possible

  43. Multipathing for Netware • Novell • A/P Policy • Manually configured • Round Robining of LUNs possible

  44. Fibre Channel SAN Host Support Dual Fabric cfmode Standby cfmode Partner/SSI cfmode Windows“NTAP DSM” A/P A/P A/P Linux: Qlogic “Failover Mode” A/P A/P A/P VMware Multipathing A/P A/P A/P Solaris “DMP” A/A/A A/P A/A Solaris “MPxIO” A/P N/A A/P AIX “SANpath” A/P A/A/A N/A HP-UX “PVLinks” A/P N/A A/P Novell A/P A/P A/P

  45. Agenda • CFModes • Single System Imagine • Multipathing • Host Clustering • Storage System Backend HA • Q&A

  46. Host Clustering & Storage • LUNs need to be made visible to host simultaneously • Some Host Clustering solutions require SCSI reservations to avoid to split brain

  47. Host Clustering for Microsoft • Microsoft Cluster • SnapDrive is integrated to help configuration • WIN2K3 allows single HBA for both boot device & shared storage • Cannot grow LUN online in cluster • SnapDrive ability to very quickly grow a LUN minimizes the pain caused by this

  48. Host Clustering for VERITAS • VCS • By default does not us I/O fencing to protect against split brain • I/O fencing requires SCSI-3 reservations • 7.0.3 will have SCSI-3 reservations that are compatible with VERITAS • Does not do failover on FC links

  49. Host Clustering for HP-UX • ServiceGuard • 1 to 3 node clusters using SCSI-2 locks as arbitrator to avoid split brain • Does not do failover in dead FC links

  50. Host Clustering for AIX • HACMP • Uses SCSI-2 locks as arbitrator to avoid split brain • “setsp –b2” to enable locks with SANpath • SCSI-2 locks to active/active are mutually exclusive

More Related