1 / 73

GIG Tech Summit – Session 344 SAN

GIG Tech Summit – Session 344 SAN. Muller Wiehahn April 4-5, 2007. Agenda. SAN Migration and Interoperability BLADE Servers Cisco DPVM. SAN Migration and Interoperability. Session Objectives. At the end of the session, the participants should be able to:

nida
Télécharger la présentation

GIG Tech Summit – Session 344 SAN

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. GIG Tech Summit – Session 344SAN Muller Wiehahn April 4-5, 2007

  2. Agenda • SAN Migration and Interoperability • BLADE Servers • Cisco DPVM

  3. SAN Migration and Interoperability

  4. Session Objectives At the end of the session, the participants should be able to: • Understand the process of a migration • Describe the different types of migrations • Understand the four Interoperability Modes

  5. Agenda • Migration Drivers • Fibre Channel Fundamentals • Migration Process Overview • Third party switches to MDS migration scenarios • OS Specific Migration Requirements • Non Interop Migration • Rip and Replace • Cap And Grow • Interop mode Migration http://www.cisco.com

  6. “ Migration Is the Act of Moving Servers, Storage Arrays and/or Switches from the Current to a New Configuration.”

  7. Major business drivers: Operational cost reduction Improved scalability Performance Manageability Director class switches are used to consolidate multiple and disperse SAN islands Logical fabrics over a single physical SAN infrastructure SAN Islands Engineering SAN CRM SAN CRM VSAN HR VSAN Eng VSAN SAN Consolidation HR SAN

  8. Major drivers: Disaster Recovery Data Replication Data center consolidation Multi-protocol requirements (FCIP, iSCSI) Distributed SAN Site A Site A Site B SAN A DWDM Site B SAN B Multi-Site SAN Consolidation

  9. Agenda • Migration Drivers • Fibre Channel Fundamentals • Migration Process Overview • Third party switches to MDS migration scenarios • OS Specific Migration Requirements • Non Interop Migration • Rip and Replace • Cap And Grow • Interop mode Migration http://www.cisco.com

  10. Fibre Channel Fundamentals • A storage area network (SAN) is a specialized network that provides access between servers and storage subsystems, using block level storage protocols • A fabric is a set of one or more interconnected fibre channel switches • Multiple fibre channel switches can be connected together through inter-switch links (ISLs) • Virtual SAN (VSAN) provide logical segmentation of a physical fabric • IVR enables members of different VSANs to communicate http://www.cisco.com

  11. Fibre Channel Fundamentals • Domain ID is a fundamental component of addressing in fibre channel • Each switch in a SAN must have a unique domain ID • If a switch participates in multiple VSAN, it has one domain ID for each VSAN • Domain ID changes force all the end devices (hosts and storage ports) to stop traffic, log out and log back in to the fabric Domain Identifier (Domain ID) http://www.cisco.com

  12. Fibre Channel Fundamentals • It is a 24 bit value assigned to each device in the fabric • The FCID consists of domain ID, area ID and port ID • When the domain ID changes the FCID changes • To acquire a new FCID, the end devices will have to log out and log back into the fabric Fibre Channel ID (FCID) http://www.cisco.com

  13. Fibre Channel Fundamentals • Zones are the primary fibre channel access control mechanism • Zones group together end devices enabling them to communicate with each other • Zones are grouped in zoneset • Zoneset is a collection of zones applied to a fabric or a VSAN • Multiple zonesets can be defined in a fabric or a VSAN • Only one zoneset can be active at any given time in a fabric or VSAN Zoning http://www.cisco.com

  14. Agenda • Migration Definition • Fibre Channel Fundamentals • Migration Process Overview • Third party switches to MDS migration scenarios • OS Specific Migration Requirements • Non Interop Migration • Rip and Replace • Cap And Grow • Interop mode Migration http://www.cisco.com

  15. Migration Lifecycle • Analyze the current storage infrastructure • Analyze business requirements and risks Prepare • Identify migration options • Create migration strategy Optimize Plan • Continually identify and mitigate risk • Tune the infrastructure to accommodate new projects andapplications • High-level design • Low-level design Operate Design Implement • Create migration plan • Negotiate change windows with the business partners • Execute the migration

  16. Pre-Migration Check List • Check and verify that the host can access all storage (LUNs) through at least two paths • Check and verify that the multipath software is functional on the server that is to be migrated over to the MDS switches • Verify that all the required HBA drivers and the switch firmware are up-to-date accordingly to the latest device interoperability matrix • Zone configuration from the 3rd party switches can be migrated over to the MDS using the Zone Migration Wizard in Fabric Manager • Gather the domain ID configured on the 3rd party switches, along with the FCID of the storage ports that are in use by AIX and HP-UX hosts http://www.cisco.com

  17. Pre-Migration Check List • For HP-UX and AIX hosts, the FCID of the storage ports on the old switches needs to be preconfigured on the MDS for non-disruptive migration • For Solaris hosts, ensure that the persistent binding is enabled • If there are single HBA attached servers, non- disruptive migration is not possible and down time has to be planned http://www.cisco.com

  18. Zone Alone 3: Using the Wizard

  19. Zone Migration Wizard • FM based application which telnets to the brocade/mcdata and retrieves the zoning configuration.

  20. Zone Migration Wizard • Convert domain,port based zone members MDS interface based zone members. • If any zonemember types are unknown you can manually change them.

  21. Zone Migration Wizard • MDS CLI compatible script is produced which can either be automatically applied to the switch, or saved to a text file for future use.

  22. Zone Migration Wizard • Finally, select which MDS switches to apply the zoning configuration to. • Note this is not related to FMs seed switch.

  23. Agenda • Migration Definition • Fibre Channel Fundamentals • Migration Process Overview • Third party switches to MDS migration scenarios • OS Specific Migration Requirements • Non Interop Migration • Rip and Replace • Cap And Grow • Interop mode Migration http://www.cisco.com

  24. OS-Specific Migration Requirements • HP UX • AIX • Solaris • Windows

  25. Migrating HP-UX Host/Storage to MDS • HP-UX • Hardware path structure in HP-UX • The hardware path to SAN attached disks on a HP-UX system contains the FCID of the associated storage port http://www.cisco.com

  26. Migrating HP-UX Host/Storage to MDS • HP-UX reserves domain ID 8 to represent private loop devices. Hence domain ID 8 cannot be the domain ID of a switch/vsan into which a HP-UX host or storage is connected • The disk address (ctd) on HP-UX servers are associated with the FCID of the target storage port • When the FCID of the target storage port changes, the ctd numbering of the disks on the server is changed Device Numbering on HP-UX Servers http://www.cisco.com

  27. Migrating HP-UX Host/Storage to MDS • HP-UX server migration to MDS switches • Persistent FCID feature can be used to configure static FCID on the MDS to facilitate non-disruptive migration from 3rd party switches to MDS • Disk address (controller, target, drive) changes require volume groups to be reconfigured (imported then exported) http://www.cisco.com

  28. Migrating HP-UX Host/Storage to MDS • Non disruptive HP-UX migration to MDS switches • Topology before migration Switch 1 Domain ID 97 HP Server Storage Array Switch 2 Domain ID 4 http://www.cisco.com

  29. Migrating HP-UX Host/Storage to MDS • Step 1: Gather the all path information from host to storage • Step 2: Gather the domain ID of the switches and the FCID of all storage involved in this migration • Step 3: Configure the correct VSAN on MDS and using static domainIDs and persistent FCIDs, pre-configure the FCID of the storage array port on MDS

  30. Creating VSAN 40 and adding port to the VSAN MDS1(config-vsan-db)# vsan 40 name hpMDS MDS1(config-vsan-db)# vsan 40 interface fc 3/8 MDS1(config-vsan-db)# vsan 40 interface fc 8/25 Configuring domain ID 4 for VSAN 40 MDS1(config)# fcdomain domain 4 static vsan 40 MDS1(config)# fcdomain restart disruptive vsan 40 Configuring persistent FCID for the storage port MDS1(config)# fcdomain fcid persistent vsan 40 MDS1(config)# fcdomain fcid database MDS1(config-fcid-db)# vsan 40 wwn 50:06:04:82:bf:d1:db:cd fcid 0x040000 Configure the required zones in VSAN 40 and activate the zoneset Migrating HP-UX Host/Storage to MDS

  31. Step 4: Move the path between HP server and storage through the 3rd party switch over to MDS Creating VSAN 50 and adding port to the VSAN MDS1(config-vsan-db)# vsan 50 name hpMDS MDS1(config-vsan-db)# vsan 50 interface fc 3/8 MDS1(config-vsan-db)# vsan 50 interface fc 8/25 Configuring Domain ID 4 for VSAN 50 MDS1(config)# fcdomain domain 97 static vsan 50 MDS1(config)# fcdomain restart disruptive vsan 50 Configuring persistent FCID for the storage port MDS1(config)# fcdomain fcid persistent vsan 50 MDS1(config)# fcdomain fcid database MDS1(config-fcid-db)# vsan 50 wwn 50:06:04:82:bf:d1:db:d2 fcid 0x610413 Configure the required zones in VSAN 50 and activate the zoneset Migrating HP-UX Host/Storage to MDS

  32. Migrating HP-UX Host/Storage to MDS • Step 5: configure the correct VSAN on the other MDS and pre-configure the FCID of the storage array port on MDS • Step 6: move the other path between HP server and storage through remaining 3rd party switch over to the MDS • This completes the migration

  33. Migrating HP-UX Host/Storage to MDS • Non disruptive HP-UX migration to MDS switches • Topology after migration MDS1 VSAN 50 Domain ID 97 HP Server Storage Array MDS2 VSAN40 Domain ID 4 http://www.cisco.com

  34. Migrating AIX Host/Storage to MDS • The hdisk on AIX server is derived in conjunction with the FCID of the target storage port • When the FCID of the target storage port changes, the hdisk numbering on the AIX server changes • Persistent FCID feature can be used to configure static FCID on the MDS, to facilitate non-disruptive migration from 3rd party switches to MDS • With LVM, when hdisk number changes, the volume group has to be varyoff the volume group and then manually varyon the volume group Device Numbering on AIX Servers http://www.cisco.com

  35. Migrating AIX Host/Storage to MDS • AIX • The hdisk on a AIX system is encoded with the FCID of the associated storage port. • ca-aix2:/ >lsattr -El hdisk2 • location Location Label True • lun_id 0x0 Logical Unit Number ID False • node_name FC Node Name False • pvid none Physical volume identifier False • q_type simple Queuing TYPE True • queue_depth 20 Queue DEPTH True • rw_timeout 60 READ/WRITE time out value True • scsi_id 0xa90000 SCSI ID False • start_timeout 180 START UNIT time out value True • ww_name 0x2231000c85e9d2c2 FC World Wide Name False http://www.cisco.com

  36. Migrating AIX Host/Storage to MDS • Migration of the host and storage to MDS switches is very similar to that of HP-UX • The Multipath driver is used to quiesce one of the path and migrate it over to the MDS and then the path is re-enabled using the multi path software • After the migration of the first path, the second path is quiesced and migrated over MDS and then re-enabled • This allows for the non-disruptive migration of the host and storage ports over to the MDS switches http://www.cisco.com

  37. Migrating Solaris / Windows Host/Storage to MDS • Solaris migration • In Solaris server it is recommended to use persistent binding to bind the target ID to a HBA instance when using 3rd party HBA drivers (Qlogic, Emulex) • Leadville driver stack automatically manages the device numbering without requiring persistent binding • Windows • No special requirements http://www.cisco.com

  38. Agenda • Migration Definition • Fibre Channel Fundamentals • Migration Process Overview • Third party switches to MDS migration scenarios • OS Specific Migration Requirements • Non Interop Migration • Rip and Replace • Cap And Grow • Interop mode Migration http://www.cisco.com

  39. Non Interop Migration (Rip and Replace) What is Rip and replace ? • In Rip and replace method of migration, the 3rd party switches are replaced by MDS switches one fabric at a time • This migration strategy also allows for a phased migration. SAN functions with one half of the fabric on MDS switches and the other half continues to reside on the 3rd party switches. • Final step the other non-MDS fabric is replaced with a MDS Fabric

  40. Migrate the zone database from the switch1 and switch to the MDS switches Quiesce the path to the storage through switch1 using either DMP, Power Path, SDD or MPIO. Now I/O is flowing through switch2 Move the cables connecting the host and storage to switch1 to MDS1 Verify that the host and the storage port log on to MDS1 and are in the correct VSAN and part of the right zone and zoneset Now resume I/O on the path through MDS1 using the multi path software. Now data will be flowing through MDS1 and switch2 Follow the above steps to migrate the path through switch2 to MDS2 MDS1 Switch 1 Host Storage Switch 2 MDS2 Non Interop Migration (Rip and Replace) http://www.cisco.com

  41. Pros and Cons of Rip and Replace • This method allows for a phased migration approach • This is also less risky as only one half of the fabric is changed at a time • This allows time for the SAN administrators to familiarize themselves with the MDS switches, while having one half of the SAN on the legacy 3rd party switches • As only one of the two paths is replaced at a time, this method allows for migration to happen with the least amount of downtime if any is required • This also allows for the a quick roll back if one is required as the other half of the fabric is not disturbed Pros

  42. Pros and Cons of Rip and Replace • Having to deal with two vendor fabrics till the migration is complete • If hosts are not multi-path enabled, then the migration for those hosts becomes disruptive Cons

  43. Agenda • Migration Definition • Fibre Channel Fundamentals • Migration Process Overview • Third party switches to MDS migration scenarios • OS Specific Migration Requirements • Non Interop Migration • Rip and Replace • Cap And Grow • Interop mode Migration http://www.cisco.com

  44. Storage Array Switch 1 Switch 2 Host Storage Array MDS A MDS B Host Non Interop Migration (Cap and Grow) What is Cap and Grow? • In this type of migration the MDS switches are introduced in parallel with the existing SAN infrastructure • All New storage and hosts are connected to the new MDS switches • Migrate the storage and hosts from existing switches to the MDS infrastructure.

  45. Pros And Cons of Cap and Grow • Pros • This method allows for a phased migration approach • This allows time for the SAN administrators to familiarize themselves with the MDS switches • Cons • Multiple vendor SAN • Two parallel infrastructures

  46. Agenda • Migration Definition • Fibre Channel Fundamentals • Migration Process Overview • Third party switches to MDS migration scenarios • OS Specific Migration Requirements • Non Interop Migration • Rip and Replace • Cap And Grow • Interop mode Migration http://www.cisco.com

  47. What Is Interop Migration? • Interop migration involves introducing the MDS switch into an existing 3rd party fabric • The MDS can interoperate with both Brocade and McData switches natively • Enables the SAN to expand scalability and functionality • Over a period of time, the ports on the third party switches are then migrated over to the MDS

  48. Storage Array MDS A MDS B Switch 2 Switch 1 Host Interoperate with 3rd Party Switches • In this mode of migration the MDS switches are introduced in the fabric • Interop VSAN is created on the MDS switches and set in the appropriate mode (Brocade/McData) • The Brocade/McData islands are then connected into the MDS switch and made part of the interop VSAN • Any host/storage port now connected to the MDS switch has access to all the other ports in the current fabric • Also, features like IVR, VSAN, FCIP, iSCSI can be used in conjunction with the legacy SAN infrastructure • The hosts/storage connection to the third party switches can be gradually migrated to the MDS fabric one fabric at a time http://www.cisco.com

  49. Pros and Cons • Pros • Allows for the immediate port expansion to the SAN • MDS interop VSANs and non-interop VSANs can be concurrently used in the same fabric • No down time required to connect the MDS switches to the fabric • Cons • Multi-vendor switches interacting in the same fabric • Firmware upgrade/downgrade on the 3rd party switches may be required

  50. MDS Operating Modes The MDS operating modes • MDS Native Mode (Default mode of all VSAN) • MDS also has 4 different modes of interoperability • Interop Mode 1 (all vendor switches need to be in their respective interop modes) • Interop mode 2 (Brocade switches operating in Core PID 0) • Interop mode 3 ( Brocade switches operating in Core PID1) • Interop mode 4 (McData switches)

More Related