- CLUSTER_NAME
The name of the cluster as it will appear in the output of cmviewcl and other commands, and as it appears in the cluster
configuration file.
The cluster name must not contain any of the following illegal
characters: space, slash (/), backslash (\), and asterisk
(*). All other characters are legal. The cluster name can contain
up to 40 characters.
- QS_HOST
The name or IP address of a host system outside
the current cluster that is providing quorum server functionality.
This parameter is only used when you employ a quorum server for
tie-breaking services in the cluster.
- QS_POLLING_INTERVAL
The time (in microseconds) between attempts to contact the
quorum server to make sure it is running. Default is 300,000,000
microseconds (5 minutes).
- QS_TIMEOUT_EXTENSION
The quorum server timeout is the time during which the quorum
server is not communicating with the cluster. After this time, the
cluster will mark the quorum server DOWN. This time is calculated based on ServiceGuard
parameters, but you can increase it by adding an additional number
of microseconds as an extension.
The QS_TIMEOUT_EXTENSION is an optional parameter.
- FIRST_CLUSTER_LOCK_VG, SECOND_CLUSTER_LOCK_VG
The volume group containing the physical disk volume on which
a cluster lock is written. This parameter is only used if you are
using a lock disk as the cluster lock in a cluster of up to four
nodes. If you are using dual cluster locks, enter a lock volume
group name for each lock.
Use FIRST_CLUSTER_LOCK_VG for the first lock volume group. If there is a
second lock volume group, the parameter SECOND_CLUSTER_LOCK_VG is included in the file on a separate line. The
lock volume group identifier can contain up to 40 characters.
 |
| |
|
 | NOTE: Lock volume groups must also be defined in VOLUME_GROUP or OPS_VOLUME_GROUP parameters in the ASCII configuration file. |
|
| |
|
- NODE_NAME
The hostname of each system that will be a node in the cluster.
The node name can contain up to 40 characters.
- NETWORK_INTERFACE
The name of each LAN that will be used for heartbeats or for
user data. An example is lan0.
- HEARTBEAT_IP
IP notation indicating the subnet that will carry the cluster
heartbeat. Note that heartbeat IP addresses must be on the same
subnet on each node.
If you will be using VERITAS CVM disk groups for storage,
you can only use a single heartbeat subnet.
In this case, the heartbeat should be configured with standby LANs
or as a group of aggregated ports.
- STATIONARY_IP
The IP address of each monitored subnet that does not carry
the cluster heartbeat. You can identify any number of subnets to
be monitored. If you have an application network that does not carry
heartbeat, define it as a monitored non-heartbeat subnet.
- FIRST_CLUSTER_LOCK_PV, SECOND_CLUSTER_LOCK_PV
The name of the physical volume within the Lock Volume Group
that will have the cluster lock written on it. This parameter is FIRST_CLUSTER_LOCK_PV for the first physical lock volume and SECOND_CLUSTER_LOCK_PV for the second physical lock volume. If there
is a second physical lock volume, the parameter SECOND_CLUSTER_LOCK_PV is included in the file on a separate line.
Enter the physical volume name as it appears on each node
in the cluster (the same physical volume may have a different name
on each node). If you are creating two cluster locks, enter the
physical volume names for both locks. The physical volume group
identifier can contain up to 40 characters.
- SERIAL_DEVICE_FILE
The name of the device file that corresponds to the serial
(RS232) port that you have chosen on each node. Specify this parameter
when you are using RS232 as a heartbeat line.
In the ASCII cluster configuration file, this parameter is SERIAL_DEVICE_FILE. The device file name can contain up to 40 characters.
- HEARTBEAT_INTERVAL
The normal interval between the transmission of heartbeat
messages from one node to the other in the cluster. Enter a number
of seconds.
In the ASCII cluster configuration file, this parameter is HEARTBEAT_INTERVAL, and its value is entered in microseconds.
Default value is 1,000,000 microseconds in the ASCII file
(1 second in SAM); setting the parameter to a value less than the
default is not recommended.
The default should be used where possible. The maximum value
recommended is 15 seconds, and the maximum value supported is 30
seconds. This value should be at least half the value of Node Timeout (below).
- NODE_TIMEOUT
The time after which a node may decide that the other node
has become unavailable and initiate cluster reformation. Enter a
number of seconds in SAM. In the ASCII cluster configuration file,
this parameter is entered in microseconds.
Default value is 2,000,000 microseconds in the ASCII file
(2 seconds in SAM). Minimum is 2 * (Heartbeat Interval). The maximum
recommended value for this parameter is 30,000,000 in the ASCII
file, or 30 seconds in SAM. The default setting yields the fastest cluster
reformations. However, the user of the default value increases the
potential for spurious reformations due to momentary system hangs
or network load spikes. For a significant portion of installations,
a setting of 5,000,000 to 8,000,000 (5 to 8 seconds) is more appropriate.
The maximum value recommended is 30 seconds and the maximum
value supported is 60 seconds.
- AUTO_START_TIMEOUT
The amount of time a node waits before it stops trying to
join a cluster during automatic cluster startup. All nodes wait
this amount of time for other nodes to begin startup before the
cluster completes the operation. The time should be selected based
on the slowest boot time in the cluster. Enter a value equal to
the boot time of the slowest booting node minus the boot time of
the fastest booting node plus 600 seconds (ten minutes).
Default is 600,000,000 microseconds in the ASCII file (600
seconds in SAM).
- NETWORK_POLLING_INTERVAL
The frequency at which the networks configured for ServiceGuard are
checked.
Default is 2,000,000 microseconds in the ASCII file (2 seconds
in SAM). Thus every 2 seconds, the network manager polls each network
interface to make sure it can still send and receive information.
Changing this value can affect how quickly a network failure is detected.
The minimum value is 1,000,000 (1 second). The maximum value
recommended is 15 seconds, and the maximum value supported is 30
seconds.
- MAX_CONFIGURED_PACKAGES
This parameter sets the maximum number of packages that can
be configured in the cluster. In the ASCII cluster configuration
file, this parameter is known as MAX_CONFIGURED_PACKAGES.
Default is 0, which means that you must set this parameter
if you want to use packages. The minimum value is 0, and the maximum
value is 60.
Set this parameter to a value that is high enough to accommodate
a reasonable amount of future package additions without the need
to bring down the cluster to reset the parameter. However, be sure
not to set the parameter so high that memory is wasted. The use
of packages requires 6MB of lockable memory on all cluster nodes,
in addition to about 80KB per package.
Be sure to include all the OPS instance packages as well as
non-OPS packages in the total. Add one for the CVM-VxVM-PKG if you
are using CVM disk storage.
Default: 0. The minimum value is 0. The maximum value is 60.
|
| |
|
| NOTE: Remember to tune HP-UX kernel parameters on each node
to ensure that they are set high enough for the largest number of
packages that will ever run concurrently on that node. |
|
| |
|
- VOLUME_GROUP
The
name of an LVM volume group whose disks are attached to at least
two nodes in the cluster. Such disks are considered cluster aware.
The volume group name can contain up to 40 characters.
- OPS_VOLUME_GROUP
The name of an LVM volume group whose disks are attached to
at least two nodes in the cluster; the disks will be accessed by
more than one node at a time using SLVM with concurrency control
provided by OPS. Such disks are considered cluster aware.
Volume groups listed under this parameter are marked for activation
in shared mode. The VGname can contain up to 40 characters.
Printable version
