IBM XIV Storage System Copy Services and Migration

zone: nextrazap_dolly_fcs110:00:00:00:c9:53:da:b250:01:73:80:00:23:01:6150:01:73:80:00:23:01:71We then create the migration connections between the XIV and the ESS 800. An example ofusing the XIV GUI to do this was shown in “Define target connectivity (Fibre Channel only).”on page 203. In Example 7-20 we use the XCLI to define a target, then the ports on thattarget, then the connections between XIV and the target (ESS 800). Finally, we check that thelinks are active=yes and up=yes. We can use two ports on the ESS 800 because it is anactive/active storage device.Example 7-20 Connecting ESS 800 to XIV for migration using XCLI>> target_define protocol=FC target=ESS800 xiv_features=noCommand executed successfully.>> target_port_add fcaddress=50:05:07:63:00:c9:0c:21 target=ESS800Command executed successfully.>> target_port_add fcaddress=50:05:07:63:00:cd:0c:21 target=ESS800Command executed successfully.>> target_connectivity_define local_port=1:FC_Port:5:4fcaddress=50:05:07:63:00:c9:0c:21 target=ESS800Command executed successfully.>> target_connectivity_define local_port=1:FC_Port:7:4fcaddress=50:05:07:63:00:cd:0c:21 target=ESS800Command executed successfully.>> target_connectivity_listTarget Name Remote Port FC Port IP Interface Active UpESS800 5005076300C90C21 1:FC_Port:5:4 yes yesESS800 5005076300CD0C21 1:FC_Port:7:4 yes yesWe now define the XIV as a host to the ESS 800. In Figure 7-27 we have defined the twoinitiator ports on the XIV (with WWPNs that end in 53 and 73) as Linux (x86) hosts calledNextra_Zap_5_4 and NextraZap_7_4.Figure 7-27 Define the XIV to the ESS 800 as a host234 IBM XIV Storage System: Copy Services and Migration