Setting up an HP SIM server 6.0 or greater on a Linux-based Serviceguard Cluster White Paper 444847-004, February 2010

19
# GFS6.0 uses pool for logical volume management whereas GFS6.1 uses
LVM2.
# Their device name formats differ and an example for each is shown
below.
# Please use the appropriate one.
# Pool : /dev/pool/pool1 (GFS 6.0) O
R
# LVM2 : /dev/mapper/vgX
-
lvY (GFS6.1)
# mount point : /pkg1a
# filesystem type : gfs
# mount options : read/write
#
# Then the following would be entered:
# LV[0]=/dev/pool/pool1; (GFS6.0) OR
# LV[0]=/dev/mapper/
vgX
-
lvY; (GFS6.1)
# FS[0]=/pkg1a; FS_TYPE[0]="gfs";
# FS_MOUNT_OPT[0]="
-
o rw";
#
LV[0]="/dev/vgsg/lvsg"; FS[0]="/hpsimlnx"; FS_TYPE[0]="ext3";
FS_MOUNT_OPT[0]=""
FS_UMOUNT_OPT[0]=""; FS_FSCK_OPT[0]=""
# FILESYSTEM UNMOUNT COUNT
# Specify the number
of unmount attempts for each filesystem during
package
# shutdown. The default is set to 1.
#
# This particular variable is ignored if the underlying file system
# is Red Hat GFS.
#
FS_UMOUNT_COUNT=1
# FILESYSTEM MOUNT RETRY COUNT.
# Specify the number o
f mount retrys for each filesystem.
# The default is 0. During startup, if a mount point is busy
# and FS_MOUNT_RETRY_COUNT is 0, package startup will fail and
# the script will exit with 1. If a mount point is busy and
# FS_MOUNT_RETRY_COUNT is greate
r than 0, the script will attempt
# to kill the process(s) responsible for the busy mount point
# and then mount the file system. It will attempt to kill user and
# retry mount, for the number of times specified in
FS_MOUNT_RETRY_COUNT.
# If the mount s
till fails after this number of attempts, the script
# will exit with 1.
# NOTE: If the FS_MOUNT_RETRY_COUNT > 0, the script will execute
# "fuser
-
kuv" to freeup busy mount point.
#
# FS_MOUNT_RETRY_COUNT must be set to zero (default), if the underlying
#
file system is of type Red Hat GFS.
#
FS_MOUNT_RETRY_COUNT=0
#
# Configuring the concurrent operations below can be used to improve
the
# performance for starting up or halting a package. The maximum value
for
# each concurrent operation parameter is 10
24. Set these values
carefully.
# The performance could actually decrease if the values are set too
high