Image. using. IBM SAN Volume Controller. Version Date: Organization. Copyright IBM. C (Chuck) Laing. Donald.

Transcription

1 Image mode migration by using IBM SVC from IBM and non IBM storage subsystems to IBM SAN Volume Controller This document can be found on the web, Search for document number WP# ##### under the category of White Papers. Version Date: November 18 th 2013 Organization Donald C (Chuck) Laing Kameswara AK Bhaskarabhatla dlaing@us.ibm.com kamebhas@in.ibm.com Senior Technical Staff Member (STSM) IBM Expert (Level2) Certified IT Specialist Copyright IBM Corporation, 2013

2 Special Notices (example, not always required) This document reflects the image mode migration from IBM and non IBM storage subsystems to IBM storage subsystems by using the IBM SAN Volume Controller (IBM SVC). It was produced and reviewed by the members of IBM organization. This document is presented As-Is and IBM does not assume responsibility for the statements expressed herein. Trademarks (example) The following terms are registered trademarks of International Business Machines Corporation in the United States and/or other countries: AIX, AS/400, DB2, IBM, Micro Channel, MQSeries, Netfinity, NUMA-Q, OS/390, OS/400, Parallel Sysplex, PartnerLink, POWERparallel, RS/6000, S/390, Scalable POWERparallel Systems, Sequent, SP2, System/390, ThinkPad, WebSphere. The following terms are trademarks of International Business Machines Corporation in the United States and/or other countries: DB2 Universal Database, DEEP BLUE, e-business (logo), ~, GigaProcessor, HACMP/6000, Intelligent Miner, iseries, Network Station, NUMACenter, POWER2 Architecture, PowerPC 604,pSeries, Sequent (logo), SmoothStart, SP, xseries, zseries. A full list of U.S. trademarks owned by IBM may be found at NetView, Tivoli and TME are registered trademarks and TME Enterprise is a trademark of Tivoli Systems, Inc. in the United States and/or other countries. Oracle, MetaLink are registered trademarks of Oracle Corporation in the USA and/or other countries. Microsoft, Windows, Windows NT and the Windows logo are registered trademarks of Microsoft Corporation in the United States and/or other countries. UNIX is a registered trademark in the United States and other countries licensed exclusively through The Open Group. LINUX is a registered trademark of Linus Torvalds. Intel and Pentium are registered trademarks and MMX, Pentium II Xeon and Pentium III Xeon are trademarks of Intel Corporation in the United States and/or other countries. Java and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc. in the United States and/or other countries. Other company, product and service names may be trademarks or service marks of others.

3 Steps to follow migrating storage from IBM DS8000 to IBM SVC in image mode Step 1: Identify the controller (IBM DS8000 series) that is to be migrated to the IBM SVC Step 2: Check and make sure that IBM DS8000 and IBM SVC are plugged into same SAN fabrics Step 3: Make sure that the IBM DS8000 plugged into both SAN fabrics Step 4: Create zoning between IBM DS8000 and the IBM SVC. Step 5: Make sure that every SVC node port zoned with DS HA port. Step 6: Please note that the maximum number of DS HA ports that can be zoned with IBM SVC are 16. Step 7: Define IBM SVC as a host on the DS Make sure that all IBM SVC node ports are defined on the IBM DS. Step 8: Create and add all SVC host connections to one volume group. Step 9: Identify the hosts that are to be migrated. Step10: Collect the output of datapath query device, datapath query adapter, datapath query wwpn and datapath query version Total Devices : 3 DEV#: 0 DEVICE NAME: Disk1 Part0 TYPE: POLICY: OPTIMIZED SERIAL: 75BBRW10716 LUN IDENTIFIER: 0 * Scsi Port2 Bus0/Disk1 Part0 OPEN NORMAL * Scsi Port2 Bus0/Disk1 Part0 OPEN NORMAL Scsi Port3 Bus0/Disk1 Part0 OPEN NORMAL Scsi Port3 Bus0/Disk1 Part0 OPEN NORMAL DEV#: 1 DEVICE NAME: Disk2 Part0 TYPE: POLICY: OPTIMIZED SERIAL: 75BBRW10417 LUN IDENTIFIER: 0 * Scsi Port2 Bus0/Disk2 Part0 OPEN NORMAL * Scsi Port2 Bus0/Disk2 Part0 OPEN NORMAL Scsi Port3 Bus0/Disk2 Part0 OPEN NORMAL Scsi Port3 Bus0/Disk2 Part0 OPEN NORMAL

4 DEV#: 2 DEVICE NAME: Disk3 Part0 TYPE: POLICY: OPTIMIZED SERIAL: 75BBRW10517 LUN IDENTIFIER: 0 * Scsi Port2 Bus0/Disk3 Part0 OPEN NORMAL * Scsi Port2 Bus0/Disk3 Part0 OPEN NORMAL Scsi Port3 Bus0/Disk3 Part0 OPEN NORMAL Scsi Port3 Bus0/Disk3 Part0 OPEN NORMAL Step11: Check for the compatibility of multipathing (IBM SDD) driver version Step12: Stop the application on the server Step13: Unmap the IBM DS 8000 LUN s on the server. Step14: Disable the ports of the server on the SAN fabrics. Step15: Remove the zoning between the host and the IBM DS 8000 Step16: Create the zoning between the host and the IBM SVC Step17: If the version of drivers is not in compatible level, install / upgrade compatible drivers. Step18: Unmap the LUN s from host volume group on the IBM DS 8000 Step19: Map the LUN s that is unmapped from host volume group to the IBM SVC volume group Step20: On the IBM SVC detect the LUN s as mdisks by running svctask detectmdisk command Step21: Create a temporary mdisk group on the SVC Note: Please do not add mdisks to mdisk group. To create image mode vdisks, mdisks must be in unmanaged mode Step22: Create image mode vdisk out of unmanaged mode mdisk and add to the temporary mdisk group. svctask mkvdisk -mdiskgrp TEMP_MDISK_GRP -iogrp 0 -mdisk DS_MDISK -vtype image name VDISK IBM_2145:SVC:admin>svcinfo lsmdisk -filtervalue mdisk_grp_name=temp_mdisk_grp id name status mode mdisk_grp_id mdisk_grp_name capacity ctrl_lun_# controller_name UID 0 DS_0102 online image 2 TEMP_MDISK_GRP 300.0GB DS_DS8100_P10K ffc DS_0B01 online image 2 TEMP_MDISK_GRP 32.0GB 400B DS_DS8100_P10K ffc b DS_0202 online image 2 TEMP_MDISK_GRP 300.0GB DS_DS8100_P10K ffc IBM_2145:SVC:admin> Step23: Create logical host definition on the IBM SVC

5 Step24: Map the image mode virtual disk to the host Note: While mapping vdisks to host please use -scsi parameter, use the same scsi ID Step25: Contact the system administrator to get the update about the multipating Step26: Enable the SAN ports on the fabrics Step27: Contact the system administrator to rescan the disks and to perform relevant health checks on the server Step28: After performing health checks, ask the system administrator to start the application / Data base Step29: Collect the information about datapath query device C:\Program Files\IBM\Subsystem Device Driver>datapath query device -l Total Devices : 2 DEV#: 0 DEVICE NAME: Disk1 Part0 TYPE: POLICY: OPTIMIZED SERIAL: 75BBRW10716 LUN IDENTIFIER: FFC Scsi Port2 Bus0/Disk1 Part0 OPEN NORMAL Scsi Port2 Bus0/Disk1 Part0 OPEN NORMAL Scsi Port3 Bus0/Disk1 Part0 OPEN NORMAL Scsi Port3 Bus0/Disk1 Part0 OPEN NORMAL DEV#: 1 DEVICE NAME: Disk2 Part0 TYPE: POLICY: OPTIMIZED SERIAL: 75BBRW10417 LUN IDENTIFIER: FFC Scsi Port2 Bus0/Disk2 Part0 OPEN NORMAL Scsi Port2 Bus0/Disk2 Part0 OPEN NORMAL Scsi Port3 Bus0/Disk2 Part0 OPEN NORMAL Scsi Port3 Bus0/Disk2 Part0 OPEN NORMAL Step30: Migrate the image mode vdisks to striped mode on the IBM SVC Step31: After successful migration from image mode to striped, remove the mdisks from mdisk group on the SVC and delete the temporary mdisk group Step32: Unmap the vdisks on IBM DS8000 from the SVC volume group Step33: Follow the GTS process to ensure a 48 hour waiting period before deleting the LUN s on the DS8000.

6

7 Steps to follow migratingg SAN boot hosts from IBM DS8000 to IBM SVC in image mode Flow chart of the migration from DS to the IBM SVC

8 Step 1: Identify the controller (IBM DS8000 series) that is to be migrated to the IBM SVC Step 2: Check and make sure that IBM DS8000 and IBM SVC are plugged into same SAN fabrics Step 3: Make sure that the IBM DS8000 plugged into both SAN fabrics Step 4: Create zoning between IBM DS8000 and the IBM SVC. Step 5: Make sure that every SVC node port zoned with DS HA port. Step 6: Please note that the maximum number of DS HA ports that can be zoned with IBM SVC are 16. Step 7: Define IBM SVC as a host on the DS Make sure that all IBM SVC node ports are defined on the IBM DS. Step 8: Create and add all SVC host connections to one volume group. Step 9: Identify the hosts that are to be migrated. Step10: Collect the output of datapath query device, datapath query adapter, datapath query wwpn and datapath query version Total Devices : 3 DEV#: 0 DEVICE NAME: Disk1 Part0 TYPE: POLICY: OPTIMIZED SERIAL: 75BBRW10716 LUN IDENTIFIER: 0 * Scsi Port2 Bus0/Disk1 Part0 OPEN NORMAL * Scsi Port2 Bus0/Disk1 Part0 OPEN NORMAL Scsi Port3 Bus0/Disk1 Part0 OPEN NORMAL Scsi Port3 Bus0/Disk1 Part0 OPEN NORMAL DEV#: 1 DEVICE NAME: Disk2 Part0 TYPE: POLICY: OPTIMIZED SERIAL: 75BBRW10417 LUN IDENTIFIER: 0 * Scsi Port2 Bus0/Disk2 Part0 OPEN NORMAL * Scsi Port2 Bus0/Disk2 Part0 OPEN NORMAL Scsi Port3 Bus0/Disk2 Part0 OPEN NORMAL Scsi Port3 Bus0/Disk2 Part0 OPEN NORMAL

9 DEV#: 2 DEVICE NAME: Disk3 Part0 TYPE: POLICY: OPTIMIZED SERIAL: 75BBRW10517 LUN IDENTIFIER: == =========== =========== =========== =========== =========== =========== =========== ==== Path# Adapter/Hard Disk State Mode Select Errors 0 * Scsi Port2 Bus0/Disk3 Part0 OPEN NORMAL * Scsi Port2 Bus0/Disk3 Part0 OPEN NORMAL Scsi Port3 Bus0/Disk3 Part0 OPEN NORMAL Scsi Port3 Bus0/Disk3 Part0 OPEN NORMAL Step11: Check for the compatibility of multipathing (IBM SDD) driver version Step12: Stop the application on the server Step13: If the version of drivers is not in compatible level, install / upgrade compatible drivers. Step14: Before shut down of the host please run the command datapath set bootdiskmigrate 2145 Figure1: Example of successful configuration of host for migration to 2145 (IBM SVC) device. Step15: Unmap the IBM DS 8000 LUN s on the server. Step16: Disable the ports of the server on the SAN fabrics. Step17: Remove the zoning between the host and the IBM DS Step18: Create the zoning between the host and the IBM SVC with single path. Note: Please zone single host adapter with single node portt of the SVC to get single path Step19: Unmap the LUN s from host volume group on the IBM DS 8000 Step20: Map Only Boot disk that is unmapped from host volume group to the IBM SVC volume group Step21: On the IBM SVC detect the LUN s as mdiskss by running svctask detectmdisk command Step22: Create a temporary mdisk group on the SVC Note: Please do not add mdisks to mdisk group. To create image mode vdisks, mdisks must be in unmanaged mode Step23: Create image mode vdisk out of unmanaged mode mdisk and add to the temporary mdisk group. svctask mkvdisk -mdiskgrp TEMP_MDISK_GRP -iogrp 0 -mdisk DS_MDISK -vtype image name VDISK IBM_2145:SVC:admin> svcinfo lsmdisk -filtervalue mdisk_grp_nam me=temp_mdisk_grp id name status mode mdisk_grp_id mdisk_grp_name capacity ctrl_lun_# controller_name UID 0 DS_0102 online image 2 TEMP_MDISK_GRP 300.0GB DS_DS8100_P10K ffc DS_0B01 online image 2 TEMP_MDISK_GRP 32. 0GB 400B DS_DS8100_P10K ffc b

10 2 DS_02022 online image 2 TEMP_MDISK_GRP 300.0GB DS_DS8100_P10K ffc IBM_2145:SVC:admin> Step24: Create logical host definition on the IBM SVC Step25: Map the image mode virtual disk to the host Note: While mapping vdisks to host please use -scsi parameter, use the same scsi ID Step26: Contact the system administrator to power on the server and to go to BOIS of the serverr Note: After rebooting the server if blue screen appears that means the boot disk change command did not run, see the example image shown heree in Figure 2 Figure 2: Example of a blue screen out showing the boot disk command failed to run Step27: Enable one SAN port on the fabric to pick the HBA to boot from. Providee the WWPN to the server administrator as shown in Figure 3 Figure 3: Example of selecting Host Bus Adapter (HBA) to boot Step28: If server administrator tires to boot from adapter that is disabled on the SAN, server willl spit an error message as shown in Figure 4

11 Figure 4: Example showing the disabledd adapter on the server Step29: As shown in Figure 5 additional parameters to choose boot disk from the IBM SVC (2145) Figure 5: Example showing the additional options to insert IBM SVC WWPN Step30: As shown in Figure 6, note thatt besides SVC WWPN s hexaa of where SVC is cabled can be seen too Figure 6: Example of selected WWPN of IBM SVC to access the boot device Step31: After choosing the all parameters save and exit from server BIOS Step32: After performing relevant health checks on the server shutdown the serverr

12 Step33: On the IBM DS8000 map remaining disks to the IBM SVC volume group Step34: On the SAN correct the zoning to get the dual path and enable other SAN port to get 4 paths per vdisk Step35: Contact the server administrator to power on the server and to rescan for the remaining disks Step36: Collect the output of datapath query device, datapath query adapter, datapath query wwpn and datapath query version C:\Program Files\IBM\Subsystem Device Driver>datapath query device -l Total Devices : 3 DEV#: 0 DEVICE NAME: Disk1 Part0 TYPE: POLICY: OPTIMIZED SERIAL: 75BBRW10716 LUN IDENTIFIER: FFC Scsi Port2 Bus0/Disk1 Part0 OPEN NORMAL Scsi Port2 Bus0/Disk1 Part0 OPEN NORMAL Scsi Port3 Bus0/Disk1 Part0 OPEN NORMAL Scsi Port3 Bus0/Disk1 Part0 OPEN NORMAL DEV#: 1 DEVICE NAME: Disk2 Part0 TYPE: POLICY: OPTIMIZED SERIAL: 75BBRW10417 LUN IDENTIFIER: FFC Scsi Port2 Bus0/Disk2 Part0 OPEN NORMAL Scsi Port2 Bus0/Disk2 Part0 OPEN NORMAL Scsi Port3 Bus0/Disk2 Part0 OPEN NORMAL Scsi Port3 Bus0/Disk2 Part0 OPEN NORMAL

13 DEV#: 2 DEVICE NAME: Disk3 Part0 TYPE: POLICY: OPTIMIZED SERIAL: 75BBRW10517 LUN IDENTIFIER: FFC Scsi Port2 Bus0/Disk3 Part0 OPEN NORMAL Scsi Port2 Bus0/Disk3 Part0 OPEN NORMAL Scsi Port3 Bus0/Disk3 Part0 OPEN NORMAL Scsi Port3 Bus0/Disk3 Part0 OPEN NORMAL Step37: Migrate the image mode vdisks to striped mode on the IBM SVC Step38: After successful migration from image mode to striped, remove the mdisks from mdisk group on the SVC and delete the temporary mdisk group Step39: Unmap the vdisks on IBM DS8000 from the SVC volume group Step40: Follow the STQRP process and delete the host definition and LUN s on the DS8000 after 3 days.

14 Steps to follow migratingg storage from EMC to IBM SVC in image mode Step 1: Identify the controller EMC that is to be migrated to the IBM SVC Step 2: Check and make sure that EMC and IBM SVC are plugged into same SAN fabrics Step 3: Make sure that the EMC plugged into both SAN fabrics Step 4: Identify the EMC ports which are not zoned with any host Note: Target ports (EMC ports) should not be shared with any host port. Step 4: Create zone between EMC ports and the IBM SVC. Step 5: Make sure that every SVC node port zoned with EMC port. Step 6: Please note that the maximum number of EMC ports that cann be zoned with IBM SVC are 16. Note: On the IBM SVC each EMC node port will be visiblee as WWNN. Step 7: Define IBM SVC as a host on the EMC. Make sure that all IBM SVC nodee ports are defined on the EMC. Step 8: List the WWPN s of SVC on the EMC by using command symmask Step 9: Identify the hostss that are to be migrated. Step10: Stop the application on the server and unmap the LU s on the EMC from the host Step11: Check for the compatibility of multipathing (IBM SDD) driver version Step12: Uninstall power path and install compatible IBM SDD drivers on the hostt Step13: Shutdown the server Step14: Use the symmaskdb command to display the volumes forr the server. The server is the WWPN s ending with 81C7 & 1FD2 and the devices thatt are defined for each server HBA are 0088, 00DC and 00F7.

15 Step15: Disable the ports of the server on the SAN fabrics. Step16: Remove the zoning between the host and the EMC Step17: Create the zoning between the host and the IBM SVC Step18: Change LU masking on the EMC from the host the IBM SVC Note: > Host WWPN ff -> SVC node port 5b -> EMC node port 0088,00cd & oof7 -> LU s Step19: Repeat the step18 for all the host adapters available on the EMC Step20: Apply changes on the EMC by running symmask for all the host adapters. Note: Changes made will not be active until applying them by using symmask refresh

16 0975 -> Host WWPN Step21: On the IBM SVC detect the LUN s as mdiskss by running svctask detectmdisk command Step22: Create a temporary mdisk group on the SVC Note: Please do not add mdisks to mdisk group. To create image mode vdisks, mdisks must be in unmanaged mode Step23: Create image mode vdisk out of unmanaged mode mdisk and add to the temporary mdisk group. svctask mkvdisk -mdiskgrp TEMP_MDISK_GRP -iogrp 0 -mdisk DS_MDISK -vtype image name VDISK IBM_2145:SVC:admin> svcinfo lsmdisk -filtervalue mdisk_grp_nam me=temp_mdisk_grp id name status mode mdisk_grp_id mdisk_grp_name capacity ctrl_lun_# controller_name UID 0 DS_0102 online image 2 TEMP_MDISK_GRP 300.0GB DS_DS8100_P10K ffc DS_0B01 online image 2 TEMP_MDISK_GRP 32. 0GB 400B DS_DS8100_P10K ffc b DS_02022 online image 2 TEMP_MDISK_GRP 300.0GB DS_DS8100_P10K ffc IBM_2145:SVC:admin> Step24: Create logical host definition on the IBM SVC Step25: Map the image mode virtual disk to the host Note: While mapping vdisks to host please use -scsi parameter, use the same scsi ID Step26: Power on the server. Step27: Enable the SAN ports on the fabrics Step28: Contact the system administrator to rescan the disks and to perform relevant health checks on the server Step29: After performing health checks, ask the system administrator to start the application / Data base Step30: Collect the information about datapath query device

17 C:\Program Files\IBM\Subsystem Device Driver>datapath query device -l Total Devices : 3 DEV#: 0 DEVICE NAME: Disk1 Part0 TYPE: POLICY: OPTIMIZED SERIAL: 75BBRW10716 LUN IDENTIFIER: FFC Scsi Port2 Bus0/Disk1 Part0 OPEN NORMAL Scsi Port2 Bus0/Disk1 Part0 OPEN NORMAL Scsi Port3 Bus0/Disk1 Part0 OPEN NORMAL Scsi Port3 Bus0/Disk1 Part0 OPEN NORMAL DEV#: 1 DEVICE NAME: Disk2 Part0 TYPE: POLICY: OPTIMIZED SERIAL: 75BBRW10417 LUN IDENTIFIER: FFC Scsi Port2 Bus0/Disk2 Part0 OPEN NORMAL Scsi Port2 Bus0/Disk2 Part0 OPEN NORMAL Scsi Port3 Bus0/Disk2 Part0 OPEN NORMAL Scsi Port3 Bus0/Disk2 Part0 OPEN NORMAL DEV#: 2 DEVICE NAME: Disk3 Part0 TYPE: POLICY: OPTIMIZED SERIAL: 75BBRW10517 LUN IDENTIFIER: FFC Scsi Port2 Bus0/Disk3 Part0 OPEN NORMAL Scsi Port2 Bus0/Disk3 Part0 OPEN NORMAL Scsi Port3 Bus0/Disk3 Part0 OPEN NORMAL Scsi Port3 Bus0/Disk3 Part0 OPEN NORMAL Step31: Migrate the image mode vdisks to striped mode on the IBM SVC Step32: After successful migration from image mode to striped, remove the mdisks from mdisk group on the SVC and delete the temporary mdisk group Step32: Unmap the LU on the EMC from the SVC WWPN s Step33: Follow the GTS process to ensure a 48 hour waiting period before deleting the LUN s on the EMC.

18 Steps to follow migratingg SAN boot hosts image mode from EMC to IBM SVC in Step 1: Identify the controller EMC that is to be migrated to the IBM SVC Step 2: Check and make sure that EMC and IBM SVC are plugged into same SAN fabrics Step 3: Make sure that the EMC plugged into both SAN fabrics Step 4: Identify the EMC ports which are not zoned with any host Note: Target ports (EMC ports) should not be shared with any host port. Step 5: Create zone between EMC ports and the IBM SVC. Step 6: Make sure that every SVC node port zoned with EMC port. Step 7: Please note that the maximum number of EMC ports that cann be zoned with IBM SVC are 16. Note: On the IBM SVC each EMC node port will be visiblee as WWNN. Step 8: Define IBM SVC as a host on the EMC. Make sure that all IBM SVC nodee ports are defined on the EMC. Step 9: List the WWPN s of SVC on the EMC by using command symmask Step10: Identify the hostss that are to be migrated. Step11: Stop the application on the server and unmap the LU s on the EMC from the host Step12: Check for the compatibility of multipathing (IBM SDD) driver version Step13: Uninstall power path and install compatible IBM SDD drivers on the hostt Step14: Before shut down of the host please run the command datapath set bootdiskmigrate 2145 as shown in Figure 7

19 Figure 7: Example of successful configuration of host for migration to 2145 (IBM SVC) device. Step15: Shutdown the server Step16: Use the symmaskdb command to display the volumes forr the server. The server is the WWPN s ending with 81C7 & 1FD2 and the devices thatt are defined for each server HBA are 0088, 00DC and 00F7. Step17: Disable the ports of the server on the SAN fabrics. Step18: Remove the zoning between the host and the EMC Step19: Create the zoning between the host and the IBM SVC Step20: Change LU masking on the EMC from the host the IBM SVC Note: > Host WWPN ff -> SVC node port 5b -> EMC node port 0088,00cd & oof7 -> LU s

20 Step21: Repeat the step19 for all the host adapters available on the EMC Step22: Apply changes on the EMC by running symmask for all the host adapters. Note: Changes made will not be active until applying them by using symmask refresh > Host WWPN Step23: Map Only Boot disk that is unmapped from host volume group to the IBM SVC volume group Step24: On the IBM SVC detect the LUN s as mdiskss by running svctask detectmdisk command Step25: Create a temporary mdisk group on the SVC Note: Please do not add mdisks to mdisk group. To create image mode vdisks, mdisks must be in unmanaged mode Step26: Create image mode vdisk out of unmanaged mode mdisk and add to the temporary mdisk group. svctask mkvdisk -mdiskgrp TEMP_MDISK_GRP -iogrp 0 -mdisk DS_MDISK -vtype image name VDISK IBM_2145:SVC:admin> svcinfo lsmdisk -filtervalue mdisk_grp_nam me=temp_mdisk_grp id name status mode mdisk_grp_id mdisk_grp_name capacity ctrl_lun_# controller_name UID 0 DS_0102 online image 2 TEMP_MDISK_GRP 300.0GB DS_DS8100_P10K ffc DS_0B01 online image 2 TEMP_MDISK_GRP 32. 0GB 400B DS_DS8100_P10K ffc b DS_02022 online image 2 TEMP_MDISK_GRP 300.0GB DS_DS8100_P10K ffc IBM_2145:SVC:admin> Step27: Create logical host definition on the IBM SVC Step28: Map the image mode virtual disk to the host Note: While mapping vdisks to host please use -scsi parameter, use the same scsi ID Step29: Contact the system administrator to power on the server andd to go to BOIS of the server Note: After rebooting the server, as shown in Figure 8, if blue screenn appears that means boot disk change command did not ran

21 Figure 8: Example of a blue screen out showing the boot disk command failed to run Step30: Enable one SAN port on the fabric to pick the HBA to boot from. As shown in Figure 9, Provide the WWPN to the server administrator Figure 9: Example of selecting Host Bus Adapter (HBA) to boot Step31: Figure 10 shows that server administrator tired to boot from adapter that iss disabled on the SAN Figure 10: Example showing the disabled adapter on the server

22 Step32: Figure 11 shows additional parameters to choose boot disk from the IBM SVC (2145) Figure 11: Example showing the additional options to insert IBM SVC WWPN Step33: As shown in Figure 12, note that besides SVC WWPN s hexa of where SVC is cabled can be seen too Figure 12: Example of selected WWPN of IBM SVC to access the boot device Step34: After choosing the all parameters save and exit from server BIOS Step35: After performing relevant health checks on the server shutdown the serverr Step36: On the IBM DS8000 map remaining disks to the IBM SVC volume group Step37: On the SAN correct the zoning to get the dual path and enable other SAN port to get 4 paths per vdisk Step38: Contact the server administrator to power on the server and to rescan for the remaining disks Step39: Collect the outpu of datapath query device, datapath query adapter, datapath query wwpn and datapath query version

23 C:\Program Files\IBM\Subsystem Device Driver>datapath query device -l Total Devices : 3 DEV#: 0 DEVICE NAME: Disk1 Part0 TYPE: POLICY: OPTIMIZED SERIAL: 75BBRW10716 LUN IDENTIFIER: FFC Scsi Port2 Bus0/Disk1 Part0 OPEN NORMAL Scsi Port2 Bus0/Disk1 Part0 OPEN NORMAL Scsi Port3 Bus0/Disk1 Part0 OPEN NORMAL Scsi Port3 Bus0/Disk1 Part0 OPEN NORMAL DEV#: 1 DEVICE NAME: Disk2 Part0 TYPE: POLICY: OPTIMIZED SERIAL: 75BBRW10417 LUN IDENTIFIER: FFC Scsi Port2 Bus0/Disk2 Part0 OPEN NORMAL Scsi Port2 Bus0/Disk2 Part0 OPEN NORMAL Scsi Port3 Bus0/Disk2 Part0 OPEN NORMAL Scsi Port3 Bus0/Disk2 Part0 OPEN NORMAL DEV#: 2 DEVICE NAME: Disk3 Part0 TYPE: POLICY: OPTIMIZED SERIAL: 75BBRW10517 LUN IDENTIFIER: FFC Scsi Port2 Bus0/Disk3 Part0 OPEN NORMAL Scsi Port2 Bus0/Disk3 Part0 OPEN NORMAL Scsi Port3 Bus0/Disk3 Part0 OPEN NORMAL Scsi Port3 Bus0/Disk3 Part0 OPEN NORMAL Step40: Migrate the image mode vdisks to striped mode on the IBM SVC Step41: After successful migration from image mode to striped, remove the mdisks from mdisk group on the SVC and delete the temporary mdisk group Step42: Unmap the LU s on EMC from the SVC WWPN s Step43: Follow the GTS process to ensure a 48 hour waiting period before deleting the LUN s on the EMC.

24 Steps to follow migratingg storage from Hitachi HDS to IBM SVC in image mode Step 1: Identify the controller Hitachi HDS that is to be migrated to the IBM SVC Step 2: Check and make sure that Hitachi HDS and IBM SVC are plugged into same SAN fabrics Step 3: Make sure that the Hitachi HDS plugged into both SAN fabrics Step 4: Check for the compatibility of the firmware version with thee IBM SVC Step 5: Identify the Hitachi HDS ports which are not zoned with anyy host Note: Target ports (HDS ports) should not be shared with any host port. Step 6: Make sure that every SVC node port zoned with HDS port. Step 7: The IBM SVC resolves up to four WWNN per subsystem and allows up to 512 LUNs per WWNN. Step 8: As shown in Figures 13, Figure 14, Figure 15, Figure 16, Figure 17, Figuree 18, and Figure 19, define IBM SVC as a host on the Hitachi HDS. Make sure that alll IBM SVC node ports are defined on the Hitachi HDS Figure 13: Example of Storage Navigator

25 Figure 14: Example showing adding new Host Group

26 Figure 15: Example showing Adding new WWPN

27 Figure 16 Example showing selecting the new WWPN Figure 17: Example showing naming the new WWPN

28 Figure 18: Example showing adding the new WWPN to the system

29 Figure 19: Example showing the SVC WWPN in the system Step 9: As shown in Figure 20, Identify the hosts that are to be migrated. Figure 20: Example showing selecting the volumes that to be migrated Step 10: Stop the application / data base on the server. Step11: Check for the compatibility of multipathing (IBM SDD) driver version Step12: Uninstall the PVlink multipathing and install IBM SDD drivers on the server Step13: Shutdown the server

30 Step14: Disable the ports of the server on the SAN fabrics. Step15: As shown in Figure 21, change the path from host to the IBM SVC Figure 21: Example showing copying the selected paths Step16: As shown in Figure 22, map the paths to the IBM SVC.

31 Figure 22: Example showing providing paths to the IBM SVC

32 Figure 23: Example showing successful copy of paths from host to IBM SVC Step17: Remove the zoning between the host and the Hitachi HDS Step18: Create the zoning between the host and the IBM SVC Step19: On the IBM SVC detect the LUN s as mdiskss by running svctask detectmdisk command Step20: Create a temporary mdisk group on the SVC Note: Please do not add mdisks to mdisk group. To create image mode vdisks, mdisks must be in unmanaged mode Step21: Create image mode vdisk out of unmanaged mode mdisk and add to the temporary mdisk group. svctask mkvdisk -mdiskgrp TEMP_MDISK_GRP -iogrp 0 -mdisk DS_MDISK -vtype image name VDISK IBM_2145:SVC:admin> svcinfo lsmdisk -filtervalue mdisk_grp_nam me=temp_mdisk_grp id name status mode mdisk_grp_id mdisk_grp_name capacity ctrl_lun_# controller_name UID 0 DS_0102 online image 2 TEMP_MDISK_GRP 300.0GB DS_DS8100_P10K ffc DS_0B01 online image 2 TEMP_MDISK_GRP 32. 0GB 400B DS_DS8100_P10K ffc b DS_02022 online image 2 TEMP_MDISK_GRP 300.0GB DS_DS8100_P10K ffc IBM_2145:SVC:admin>

33 Step22: Create logical host definition on the IBM SVC Step23: Map the image mode virtual disk to the host Note: While mapping vdisks to host please use -scsi parameter, use the same scsi ID Step24: Contact the system administrator to get the update about the multipating Step25: Enable the SAN ports on the fabrics Step26: Contact the system administrator to power on the server Step27: After performing health checks, ask the system administrator to start the application / Data base Step28: Collect the information about datapath query device C:\Program Files\IBM\Subsystem Device Driver>datapath query device -l Total Devices : 3 DEV#: 0 DEVICE NAME: Disk1 Part0 TYPE: POLICY: OPTIMIZED SERIAL: 75BBRW10716 LUN IDENTIFIER: FFC Scsi Port2 Bus0/Disk1 Part0 OPEN NORMAL Scsi Port2 Bus0/Disk1 Part0 OPEN NORMAL Scsi Port3 Bus0/Disk1 Part0 OPEN NORMAL Scsi Port3 Bus0/Disk1 Part0 OPEN NORMAL DEV#: 1 DEVICE NAME: Disk2 Part0 TYPE: POLICY: OPTIMIZED SERIAL: 75BBRW10417 LUN IDENTIFIER: FFC Scsi Port2 Bus0/Disk2 Part0 OPEN NORMAL Scsi Port2 Bus0/Disk2 Part0 OPEN NORMAL Scsi Port3 Bus0/Disk2 Part0 OPEN NORMAL Scsi Port3 Bus0/Disk2 Part0 OPEN NORMAL

34 DEV#: 2 DEVICE NAME: Disk3 Part0 TYPE: POLICY: OPTIMIZED SERIAL: 75BBRW10517 LUN IDENTIFIER: FFC Scsi Port2 Bus0/Disk3 Part0 OPEN NORMAL Scsi Port2 Bus0/Disk3 Part0 OPEN NORMAL Scsi Port3 Bus0/Disk3 Part0 OPEN NORMAL Scsi Port3 Bus0/Disk3 Part0 OPEN NORMAL Step29: Migrate the image mode vdisks to striped mode on the IBM SVC Step30: After successful migration from image mode to striped, remove the mdisks from mdisk group on the SVC and delete the temporary mdisk group Step31: Delete the paths on Hitachi HDS from the IBM SVC Step32: Follow the STQRP process to delete host and LUN s on the Hitachi HDS after 3 days.

35 Thank you