IBM DS6000 Manual Do Utilizador
Chapter 28. Interoperability between DS6000 and DS8000
421
Even when you have successfully added one complex to another, new user IDs created in
one complex do not mirror to the other complex. They must be manually created and
managed in each complex.
one complex do not mirror to the other complex. They must be manually created and
managed in each complex.
Storage management
You cannot use the DS8000 DS GUI to perform storage configuration on a DS6000.
Likewise, you cannot use the DS6000 DS GUI to perform storage configuration on a DS8000.
You can only perform Copy Services management tasks on the alternative device. If you are
logged on to the DS6000 DS GUI and wish to configure some storage on the DS8000, you
must log off and then log on to the DS8000 DS GUI. The same applies if you are logged on to
the DS8000 DS GUI and wish to configure storage on the DS6000. You must log on to the
DS6000 DS GUI to do this.
Likewise, you cannot use the DS6000 DS GUI to perform storage configuration on a DS8000.
You can only perform Copy Services management tasks on the alternative device. If you are
logged on to the DS6000 DS GUI and wish to configure some storage on the DS8000, you
must log off and then log on to the DS8000 DS GUI. The same applies if you are logged on to
the DS8000 DS GUI and wish to configure storage on the DS6000. You must log on to the
DS6000 DS GUI to do this.
28.2.7 Volume size considerations for Remote Mirror Copy
When you use RMC (PPRC) to copy the contents of a CKD volume from one storage device
to another, it is possible for the RMC target volume to be larger than the RMC source volume.
However, if an attempt is made to reverse the relationship (so that the source becomes the
target), this attempt will fail because now the source is larger than the target. Clearly the best
way to avoid this is to ensure the source and target are exactly the same size.
to another, it is possible for the RMC target volume to be larger than the RMC source volume.
However, if an attempt is made to reverse the relationship (so that the source becomes the
target), this attempt will fail because now the source is larger than the target. Clearly the best
way to avoid this is to ensure the source and target are exactly the same size.
28.2.8 Determining DS6000 and DS8000 CKD volume size
When CKD volumes are created on a DS6000 or DS8000, the size must be specified in
cylinders. In Example 28-3, two CKD volumes of 3339 cylinders are created. This means that
if we use these volumes in a PPRC relationship, their partner volumes should also be 3339
cylinders.
cylinders. In Example 28-3, two CKD volumes of 3339 cylinders are created. This means that
if we use these volumes in a PPRC relationship, their partner volumes should also be 3339
cylinders.
Example 28-3 CKD volume size in DS CLI
dscli> mkckdvol -extpool P2 -cap 3339 -name av_6K_CKD_#h 0600-0601
Date/Time: 8 November 2005 22:58:31 IBM DSCLI Version: 5.1.0.204 DS: IBM.1750-1300247
CMUC00021I mkckdvol: CKD Volume 0600 successfully created.
CMUC00021I mkckdvol: CKD Volume 0601 successfully created.
dscli> lsckdvol -lcu 06
Date/Time: 9 November 2005 3:58:42 IBM DSCLI Version: 5.1.0.204 DS: IBM.1750-1300247
Name ID accstate datastate configstate deviceMTM voltype orgbvols extpool cap (cyl)
================================================================================================
av_6K_CKD_0600 0600 Online Normal Normal 3390-3 CKD Base - P2 3339
av_6K_CKD_0601 0601 Online Normal Normal 3390-3 CKD Base - P2 3339
Date/Time: 8 November 2005 22:58:31 IBM DSCLI Version: 5.1.0.204 DS: IBM.1750-1300247
CMUC00021I mkckdvol: CKD Volume 0600 successfully created.
CMUC00021I mkckdvol: CKD Volume 0601 successfully created.
dscli> lsckdvol -lcu 06
Date/Time: 9 November 2005 3:58:42 IBM DSCLI Version: 5.1.0.204 DS: IBM.1750-1300247
Name ID accstate datastate configstate deviceMTM voltype orgbvols extpool cap (cyl)
================================================================================================
av_6K_CKD_0600 0600 Online Normal Normal 3390-3 CKD Base - P2 3339
av_6K_CKD_0601 0601 Online Normal Normal 3390-3 CKD Base - P2 3339
28.3 RMC: Establishing paths between DS6000 and DS8000
To create a PPRC relationship between a DS8000 and an DS6000, you must first create
logical paths (over the physical Fibre Channel connections). If you are using the DS GUI, then
provided you added the other machines Storage Complex, you can establish paths in either
direction (DS6000 to DS8000 or DS8000 to DS6000).
logical paths (over the physical Fibre Channel connections). If you are using the DS GUI, then
provided you added the other machines Storage Complex, you can establish paths in either
direction (DS6000 to DS8000 or DS8000 to DS6000).
28.3.1 Decoding port IDs
When viewing port IDs in the DS GUI or DS CLI, the port IDs can be decoded to show which
physical port on the DS8000 or DS6000 is in use.
physical port on the DS8000 or DS6000 is in use.