Designing Disaster Tolerant High Availability Clusters, 10th Edition, March 2003 (B7660-90013)

Building a Metropolitan Cluster Using MetroCluster/SRDF
Preparing a Cluster for MetroCluster/SRDF
Chapter 4152
NOTE The Symmetrix device number may be the same or different in each of
the Symmetrix units for the same logical device. In other words, the
device number for the logical device on the R1 side of the SRDF link may
be different from the device number for the logical device on the R2 side
of the SRDF link.
The Symmetrix logical device numbers in these examples were
configured to be the same number so that the cluster is easier to manage.
If you are reconfiguring an existing cluster, the
Dev and RDev devices will probably not be the same number.
When you are determining the configuration for the Symmetrix devices
for a new installation, it is recommended that you try to use the same
Symmetrix device number for the R1 devices and the R2 devices. It is
also recommended that the same target and LUN number be configured
for all nodes that have access to the same Symmetrix logical device.
Type R1
ID 95 c0t15d0
Dev# 040 c0t15d0
Type GK
ID 50 c3t15d1
Dev# 041 c5t15d1
Type GK
ID 95 c4t3d2
Dev# 028 c4t3d2
Type BCV n/a n/a
Table 4-6 Symmetrix Device and HP-UX Device Correlation (Continued)
Symmetrix
ID, device
#, and type
Node 1
/dev/rdsk
device file
name
Node 2
/dev/rdsk
device file
name
Node 3
/dev/rdsk
device file
name
Nodes 4
/dev/rdsk
device file
name