Creating a Metro Mirror volume pair that involves a 2105 using DS CLI

Complete this task to create a Metro Mirror volume pair using volumes from a 1750 and a 2105.

Before you begin, ensure that you meet the following requirements:

The license for the remote mirror and copy feature must be activated.
To create a Metro Mirror volume pair between Model types 1750 and a 2105, you must have added the 2105 Copy Services domain to your storage complex environment.
Ensure that paths are set up between the source and the target LSSs for the Metro Mirror volume pairs. The paths between the 2105 and the 1750 must be configured using Fibre Channel Protocol (FCP) ports.
The storage type of the source and target volumes on the 1750 and 2105 domain must have the same type. That is, if the source volumes are fixed block volumes, the target volumes must also be fixed block volumes.
The size of the volumes in the source LSS must be less than or equal to those of the target LSS.
Gather the following preliminary information:
- Open the ESS Specialist on the ESS 800 to determine the its WWNN. The WWNN is listed in 20 point font on the opening page. The format is 5005076300C08641.
- Determine the number of available volumes on the ESS 800 with the ESS 800 GUI.
- Document the LSS and volume mappings.
- Ensure that the volume sizes are matched and are -type ESS on the DS6000.

You can create Metro Mirror relationships using source and target volumes from the following machine types:

A 2107 and a 2107
A 1750 and a 1750
A 2107 and a 1750
A 2105 and a 1750
A 2105 and a 2107
A 2105 and a 2105

Note: If the source is a Copy Services 2105 domain, the Metro Mirror task is performed on the source domain. However, if you perform a "Suspend at target" action, the suspension occurs at the target domain.

Perform the following steps to create a Metro Mirror pair between a 1750 and a 2105. For this task, the source domain is a 2105 Model 800 or 750 and the target is a 1750. You can use this task if the target domain is a 2105 Model 800 or 750 and the source is a 1750 by switching the device IDs in the volume pairs. The example commands in this task are shown in two formats. The first format shows the type of information that the command requires. The second format provides the command with declared values for the variables.

Issue the lsavailpprcport command to list all of the available ports to the remote system to create a connection. It is recommended that you use ports that are not mapped to hosts for PPRC for increased performance, but sharing host ports with PPRC ports is supported. Specify the remote WWPN and device ID for the target cluster. Enter the lsavailpprcport command at the dscli command prompt with the following parameters and variables:
dscli>lsavailpprcport -dev storage_image_ID -remotedev storage_image_ID
-remotewwnn wwnn Source_LSS_ID:Target_LSS_ID

Example
```
dscli>lsavailpprcport -dev IBM.1750-13AB7DA -remotedev IBM.2105-18602 
-remotewwnn 5005076300C08642 10:10 
```
Issue the mkpprcpath command to create a path between LSSs on the DS6000 to the ESS 800. You associate an LSS on the DS6000 to the ESS 800 and specify specific ports. You can list multiple ports. You should create redundant port paths from both controllers of the DS6000 to both clusters of the ESS 800. Enter the mkpprcpath command at the dscli command prompt with the following parameters and variables:
dscli>mkpprcpath -dev storage_image_ID -remotedev storage_image_ID
-srclss source_LSS_ID -tgtlss target_LSS_ID –remotewwnn wwnn
-consistgrp source_port_ID:target_port_ID

Example
```
dscli>mkpprcpath -dev IBM.1750-68FA120 
-remotedev IBM.2105-18602 -srclss 01 -tgtlss 01 
–remotewwnn 12341234000A000F -consistgrp  I0100:I0100
```
Issue the lspprcpath command to display the created paths and their status. “Success” indicates that the path is valid, “failure” indicates that the path did not create correctly, or that the relationship has become separated. Enter the lspprcpath command at the dscli command prompt with the following parameters and variables: dscli> lspprcpath -dev IBM.1750-13AB7DA 10
Example
```
dscli>lspprcpath -dev storage_image_ID Source_LSS_ID
```
Issue the rmpprcpath command to remove a path. You must specify both the source and target device IDs and the source and destination LSS. Enter the rmpprcpath command at the dscli command prompt with the following parameters and variables:
dscli>rmpprcpath -dev storage_image_ID -remotedev storage_image_ID
source_LSS_ID:target_LSS_ID

Example
```
dscli>rmpprcpath -dev IBM.1750-13AB7DA -remotedev IBM.2105-18602 10:10
```
Issue the mkpprc command to create a relationship between a source and target volume. The volumes must be type ESS and be exactly the same size or the attempt to create the volume pair will fail. Enter the mkpprc command at the dscli command prompt with the following parameters and variables:
dscli>mkpprc -dev storage_image_ID -remotedev storage_image_ID
-type mmir SourceVolumeID:TargetVolumeID

Example
```
dscli>mkpprc -dev IBM.1750-13AB7DA -remotedev IBM.2105-18602
 -type mmir 1001:1001
```
Issue the lspprc command to list the pairs that are in existence. Upon creation, the volumes will be in the “copy pending” state. When the initial copy is complete, the volumes will show as “full duplex” on the primary and “target full duplex” on the secondary. If something interrupts the connection, the primary volumes indicate "suspended", but the target volumes still show "full duplex.” You can specify a range of volumes to list multiple pairs 1001 - 10ff. Enter the lspprc command at the dscli command prompt with the following parameters and variables:
dscli>lspprc -dev storage_image_ID SourceVolumeID:TargetVolumeID

Example
```
dscli>lspprc -dev IBM.1750.13AB7DA 1001-10ff
```

Creating a Metro Mirror volume pair between a 1750 and a 2105