HP Serviceguard for Linux Version A.11.18 Deployment Guide, August 2008

34
NOTE: When using Device Mapper Multipath, the path to the cluster Lock LUN, for example
/dev/mapper/mpath0, must be the same on each node.
9. Select Check Configuration. Look for any errors.
NOTE: You may get a warning about the default NODE_TIMEOUT value. This warning can
be ignored here, but refer to the documentation when finalizing your cluster.
10. Select Apply Configuration. Select “OK” in the pop-up dialog box.
11. To verify the cluster configuration, run the following options from Administration menu of the
HP Serviceguard Manager Summary page to test that each node can run the cluster in the
event that the other node fails:
a. Administration -> Run Cluster (on both nodes)
b. Administration -> Halt Node (select adam)
c. Administration -> Run Node (on adam)
d. Administration -> Halt Node (select eve)
Configure the consolidated log package
The consolidated logging tool is used to consolidate syslog and package log files from all nodes in
the cluster. Configuration is done through a wizard in the Serviceguard Manager to create a clog
package in Serviceguard. This makes the consolidated logging tool highly available.
1. In your browser on the HP Serviceguard Manager Summary page, go to the “Configuration”
menu and select “Configure Log Consolidation Tool…”
2. Enter the “Package Storage Parameters”, for example:
Volume Group /dev/vgclog
Logical Volume /dev/vgclog/lvol1
Mount Point /clog
Filesystem Type ext3
Mount Options -o rw
3. Enter the “Package Network Parameters” (Package Relocatable IP address and subnet mask),
for example:
IP Address 16.89.84.233
Subnet Address 16.89.84.128
4. Select “Perform package log consolidation” by putting a check in the box.
5. Select “Use TCP?” by putting a check in the box. Then enter the free TCP port number
identified earlier.
6. Click “OK”.
7. Click “Yes” in the pop-up dialog box to apply this configuration.
8. Check the operations log to verify success. The operations log should appear in a separate
pop-up window.
NOTE: You may see the following errors in the operations log:
ERROR: Command /etc/init.d/syslog-ng start
failed on node adam.
ERROR: Command /etc/init.d/syslog-ng start
failed on node eve.
To remedy this error, try starting the service manually on each node using the
following command:
/etc/init.d/syslog-ng start
Once syslog-ng has been started on each node, click “OK” on the “Configure Log
Consolidation Tool” page to reapply the configuration from Serviceguard Manager.