Designing Disaster Recovery Clusters using Metroclusters and Continentalclusters, Reprinted October 2011 (5900-1881)

Issue the above command on nodes attached to the R1 side.
# symdg create -type RDF2 devgroupname
Issue the above command on nodes attached to the R2 side.
The group name must be the same on each node on the R1 and R2 side. The devgroup name
used will be later placed in variable DEVICE_GROUP defined in pkg.env file.
2. Use the symld command to add all LUNs that comprise the Volume Group for that package
on that host. The HP-UX device file names for all Volume Groups that belong to the package
must be defined in one Symmetrix device group. All devices belonging to Volume Groups that
are owned by an application package must be added to a single Symmetrix device group.
# symld -g devgroupnameadd dev devnumber1
# symld -g devgroupnameadd dev devnumber2
At this point, it will be helpful to refer to Table 22 (page 261). Although, the HP-UX device file
names on each node specified may be different, the device group must be the same on each
node.
When creating the Symmetrix device groups, specify only one HP-UX path to a particular
Symmetrix device. Do not specify alternate paths (PVLinks). The EMC Solutions Enabler uses
the HP-UX path only to determine to which Symmetrix device you are referring. The Symmetrix
device may be added to the device group only once.
NOTE: Symmetrix Logical Device names must be the default names of the form DEVnnn (for
example, DEV001). Do not use this option for creating your own device names.
The script must be customized for each system including:
• Particular HP-UX device file names.
• Symmetrix device group name (an arbitrary, but unique name may be chosen for each group
that defines all of the volume groups (VGs), which belong to a particular Serviceguard
package).
• Keyword RDF1 or RDF2.
Configuring Gatekeeper Devices
Gatekeeper devices must be unique per Serviceguard package to prevent contention in the
Symmetrix when commands are issued, such as two or more packages starting up at the same
time. Gatekeeper devices are unique to a Symmetrix unit. They are not replicated across the SRDF
link. Gatekeeper devices are marked GK in the syminq output, and are usually 2880 KB in size.
NOTE: The sample scripts mk4gatekpr.nodename can be modified to automate these steps.
1. Define at least two gatekeepers per package per node (assuming PV links are used). They
will only be available for use by that node. Each gatekeeper device is configured on different
physical links.
# symgate -sid sidnumber1 define dev devnumber1
# symgate -sid sidnumber2 define dev devnumber2
2. Associate the gatekeeper devices with the Symmetrix device group for that package.
# symgate -sid sidnumber1 -g devgroupname \associate dev devnumber1
# symgate -sid sidnumber2 -g devgroupname \associate dev devnumber2
3. Define a pool of four or more additional gatekeeper devices that are not associated with any
particular node. The EMC Solutions Enabler will switch to an alternate gatekeeper device if
the path to the primary gatekeeper device fails.
Building a Metrocluster Solution with EMC SRDF 263