IBM XIV Storage System Copy Services and Migration

You can now create a host definition on the DS4000 for the XIV. If you have zoned the XIV toboth DS4000 controllers you can add both XIV initiator ports to the host definition. Thismeans that the host properties should look similar to Figure 7-25. After mapping yourvolumes to the XIV migration host, you must take note of which controller each volume isowned by. When you define the data migrations on the XIV, the migration should point to thetarget that matches the controller that owns the volume being migrated.Figure 7-25 XIV defined to the DS4000 as a host.7.12.6 IBM ESS E20/F20/800The following considerations were identified for ESS 800.LUN0There is no requirement to map a LUN to LUN ID 0 for the ESS to communicate with the XIV.LUN numberingThe LUN IDs used by the ESS are in hexadecimal, so they must be converted to decimalwhen entered as XIV data migrations. It is not possible to specifically request certain LUNIDs. In Example 7-14 there are 18 LUNs allocated by an ESS 800 to an XIV host calledNextraZap_ITSO_M5P4. You can clearly see that the LUN IDs are hex. The LUN IDs given inthe right-hand column were added to the output to show the hex-to-decimal conversionneeded for use with XIV. An example of how to view LUN IDs using the ESS 800 Web GUI isshown in Figure 7-23 on page 217.Restriction: The ESS can only allocate LUN IDs in the range 0 to 255 (hex 00 to FF). Thismeans that only 256 LUNs can be migrated at one time.Example 7-14 Listing ESS 800 LUN IDs using ESSCLIC:\esscli -s 10.10.1.10 -u storwatch -p specialist list volumeaccess -d"host=NextraZap_ITSO_M5P4"Tue Nov 03 07:20:36 EST 2009 IBM ESSCLI 2.4.0Volume LUN Size(GB) Initiator Host------ ---- -------- ---------------- -------------------100e 0000 10.0 5001738000230153 NextraZap_ITSO_M5P4 (LUN ID is 0)100f 0001 10.0 5001738000230153 NextraZap_ITSO_M5P4 (LUN ID is 1)1010 0002 10.0 5001738000230153 NextraZap_ITSO_M5P4 (LUN ID is 2)Chapter 7. Data migration 229