HP Serviceguard Extended Distance Cluster for Linux A.12.00.00 Deployment Guide, March 2014

resulting in the package not being able to start. By default, this parameter is set to 0. The
value set for this parameter must be more than the value set for the
xdc/xdc/raid_monitor_interval parameter.
Possible values are:
-1 To ignore the rpo_target check during startup.
Any positive integer including zero.
xdc/xdc/raid_monitor_interval
This parameter defines the time interval, in seconds, the raid monitor script waits between
each check to verify the accessibility of the component mirror disks. By default, this parameter
is set to 30 seconds.
xdc/xdc/raid_device
Specifies the mirror devices that are used by this package. The value for this parameter is the
name of the MD device. For more information on MD device, see the md(4) Linux manpage.
NOTE: Ensure that you specify the volume groups configured on the raid_device in vg
parameter of pkg_ascii_file.
xdc/xdc/device_0
Specifies the first mirror half of the MD device defined in the xdc/xdc/raid_device
parameter. The value for this parameter is the name of the first mirror half of the MD device
defined in the xdc/xdc/raid_device parameter.
xdc/xdc/device_1
Specifies the second mirror half of the MD device defined in the xdc/xdc/raid_device
parameter. The value for this parameter is the name of the second mirror half of the MD device
defined in the xdc/xdc/raid_device parameter.
VxVM disk group parameters
vxvm_dg
Specifies the disk group that has mirrored volumes. For more information on VxVM disk group
and other related parameters, see Managing HP Serviceguard A.12.00.00 for Linux.
fs_name
Specifies the mirrored volume. For more information on fs_name and other related parameters
such as fs_server, fs_directory, and fs_type, see Managing HP Serviceguard
A.12.00.00 for Linux.
NOTE: If you are using VxVM mirroring configuration RPO_TARGET parameters are not supported.
Specifying Node Order
Edit the node_name parameter in the package configuration file to specify the node order or
priority.
While specifying the order of nodes in the package configuration file, ensure that every node in
one site is followed by a node of the other site. In other words, you must ensure that the first node
and the second adoptive node for a package are in different sites. Similarly, the second node and
the third adoptive node must be in different sites. The third and the fourth adoptive nodes must
also be in different sites. With this configuration, if a packages fails on a node in one site, it is
targeted to startup on a node in a different site. Figure 5 (page 36) and Table 3 (page 36) elaborate
this configuration order.
5.1 Creating a serviceguard-xdc Modular Package 35