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

Building a Metropolitan Cluster Using MetroCluster/CA
Preparing an MC/ServiceGuard Cluster for MetroCluster /CA
Chapter 3 87
Preparing an MC/ServiceGuard Cluster for
MetroCluster /CA
When the following procedures are completed, an adoptive node will be
able to access the data belonging to a package after it fails over.
Setting up the Hardware
Ensure that the XP Series disk arrays are correctly cabled using PV
links to each node in the cluster that will run packages accessing data on
the array.
• Configure the XP disk array for synchronous or asynchronous
operation. If you are using a fence level of ASYNC, you must configure
a side file using the Service Processor (SVP) attached to the XP
system. Synchronous operation does not require side file
configuration on the SVP.
• Use the ioscan command to determine what devices on the XP disk
array have been configured as command devices. The device-specific
information in the rightmost column of the ioscan output will have
the suffix -CM for these devices, for example, OPEN-3-CM.
If there are no configured command devices on the disk array, you
must create two before proceeding. Each command device must have
alternate links (PV links). The first command device is the primary
command device. The second command device is a redundant
command device and is used only upon failure of the primary
command device. The command devices must be mapped to the
various host interfaces by using the SVP (disk array console) or a
remote console.