HP Serviceguard Extended Distance Cluster for Linux A.01.01 Release Notes, Third Edition, May 2009

BUS="scsi", KERNEL="sd*", PROGRAM="/sbin/scsi_id",
RESULT="3600508b3009259e05c6fae06fd350002",
NAME="%k",SYMLINK="hpdev/mylink-sdb"
Then replace the single "=" to double "=" for the parameters BUS, KERNEL, and
RESULT to make it work for Red Hat 5.
With these changes, the rule will appear as follows:
BUS=="scsi", KERNEL=="sd*", PROGRAM="/sbin/scsi_id",
RESULT=="3600508b3009259e05c6fae06fd350002", NAME="%k",
SYMLINK="hpdev/mylink-sdb"
disks are resynchronized at all times
• What is the problem?
When data on two disks is not synchronized, Software RAID resynchronizes the
entire disk, rather than only updating the changed data. This may happen even
after a basic cluster failover.
• What is the workaround?
There is no workaround as this is expected behavior with an MD driver.
MD parameters in the package control script
• What is the problem?
The package control script has a few MD related parameters.
• What is the workaround?
Earlier versions of HP Serviceguard supported MD as a multipathing software.
As a result, the package control script includes certain configuration parameters
that are specific to MD. Do not use these parameters to configure XDC in your
environment. Following are the parameters in the configuration file that you must
not edit:
# MD (RAID) CONFIGURATION FILE
# Specify the configuration file that will be used to define
# the md raid devices for this package.
# NOTE: The multipath mechanisms that are supported for shared storage
# depend on the storage subsystem and the HBA driver in the
# configuration. Follow the documentation for those devices when setting
# up multipath. The MD driver was used with earlier versions of
# Serviceguard and may still be used by some storage system/HBA
# combinations. For that reason there are references to MD in the
# template files, worksheets, and other areas. Only use MD if your
# storage systems specifically calls out its use for multipath.
# If some other multipath mechanism is used (e.g. one built
# into an HBA driver), then references to MD, RAIDTAB, RAIDSTART, etc.
# should be commented out. If the references are in the comments, they
# can be ignored. References to MD devices, such as /dev/md0, should be
# replaced with the appropriate multipath device name.
# For example:
# RAIDTAB="/usr/local/cmcluster/conf/raidtab.sg"
Known Problems and Workarounds 15