Virtual TapeServer 6.04.04 for NonStop Servers Supplemental Installation Guide

6 | Installing GFS
where -p lock_dlm argument sets the lock manager to DLM, -cluster_name specifies
the cluster name, and journals specifies the number of journals to create, which
should be the number of nodes plus two.
b. When prompted, enter y to proceed. Output similar to the following is displayed:
Device: /dev/gfsvg1/lv1
Blocksize: 4096
Filesystem Size: 4394620
Journals: 3
Resource Groups: 68
Locking Protocol: lock_dlm
Lock Table: cma:01
Syncing...
All Done
12. Start ricci and luci.
For more information about these GFS services, refer to http://www.redhat.com/docs/
manuals/enterprise/RHEL-5-manual/en-US/RHEL510/Cluster_Administration/s1-start-
luci-ricci-conga-CA.html.
These services must be configured in the cluster before you can mount the newly created
GFS volume. Complete the following steps to start the services.
a. Make sure that the luci system has a proper /etc/hosts file. Here is an example
command to confirm the contents of the file:
cat /etc/hosts
Here is an example of the file:
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost
192.168.80.2 vtsdev27.commstor.crossroads.com vtsdev27
The file should list all cluster nodes. The localhost entry is for the system you are
using and the other entries are for the cluster nodes.
b. On each node, start ricci:
chkconfig ricci on
service ricci start
To confirm that ricci is running, enter the following:
service ricci status
c. On one (and only one) of the cluster servers, configure and start the luci service. Red
Hat recommends configuring luci on a non-cluster node. It will function properly on a
cluster node, though web connectivity is lost while the system is rebooting. If the luci
node goes down, the cluster cannot be administered with luci.
luci_admin init
When prompted, enter a new password.
Then, restart the luci service:
service luci restart