PRIMECLUSTER Global File Services Configuration and Administration Guide 4.1 (Solaris(TM) 10 Operating System)

12.5.4 Procedure for setting GFS Shared File System applications as cluster applications

This section describes how to set GFS Shared File System applications as cluster applications when CIP settings are completed.

For details on setting, see the "PRIMECLUSTER Installation and Administration Guide (for Solaris Operating System)", "PRIMECLUSTER Reliant Monitor Services (RMS) with Wizard Tools (Solaris, Linux) Configuration and Administration Guide", and the "PRIMECLUSTER Global Disk Services Configuration and Administration Guide (Solaris(TM) Operating System)".

Procedure 1. Execution of automatic resource registration (common operation)

When automatic resource registration of disk equipment is not carried out yet, the following command is executed with a node, and a disk device is registered as a cluster resource.

# /etc/opt/FJSVcluster/bin/clautoconfig -r -n <Enter>

Procedure 2. GDS volume creation (node A (active node), node B (standby node))

Create the GDS volume using the following method.

GFS Shared File Systems require GDS volumes for management partitions. A disk class to which the GDS volume belongs as the management partition is different than that of the GDS volume that is used as a GDS resource of a cluster application.

The following explanation assumes the node A (active node) host name to be sunny and the node B (standby node) host name to be moony.

[When a mirror volume is to be created]

• Register a disk in the disk class on sunny by using the sdxdisk command.
  In the cluster system, specify a node name as the scope of the -a option and then specify shared as the class type.

sunny# sdxdisk -M -c gfs -d c0t1d0=DISK1,c0t2d0=DISK2 -a scope=sunny:moony,type=shared <Enter>
sunny# sdxdisk -M -c gfs01 -d c0t3d0=DISK3,c0t4d0=DISK4 -a scope=sunny:moony,type=shared <Enter>

• On sunny, disk connection to the mirror disk group is performed with the sdxdisk command.

sunny# sdxdisk -C -c gfs -g grp0001 -d DISK1,DISK2 <Enter>
sunny# sdxdisk -C -c gfs01 -g grp0002 -d DISK3,DISK4 <Enter>

• On sunny, GDS volume creation is performed with the sdxvolume command.
  Note that a volume of at least 40 megabytes is necessary for the management partition of the GFS Shared File System.

sunny# sdxvolume -M -c gfs -g grp0001 -v control -s 81920 <Enter>
sunny# sdxvolume -M -c gfs01 -g grp0002 -v volume01 -s 17563648 <Enter>

• On moony, activation of the GDS volume is performed with the sdxvolume command.

moony# sdxvolume -N -c gfs -v control <Enter>
moony# sdxvolume -N -c gfs01 -v volume01 <Enter>

[When a single volume is to be created]

• On sunny, disk registration in the disk class is performed with the sdxdisk command.
  In the cluster system, specify a node name as the scope of the -a option and then specify shared as the cluster type.

sunny# sdxdisk -M -c gfs -d c0t1d0=DISK1:single -a scope=sunny:moony,type=shared <Enter>
sunny# sdxdisk -M -c gfs -d c0t2d0=DISK2:single -a scope=sunny:moony,type=shared <Enter>

• On sunny, GDS volume creation is performed with the sdxvolume command.
  Note that a volume of at least 40 megabytes is necessary for the management partition of the GFS Shared File System.

sunny# sdxvolume -M -c gfs -d DISK1 -v control -s 81920 <Enter>
sunny# sdxvolume -M -c gfs01 -d DISK2 -v volume01 -s 17563648 <Enter>

• On moony, activation of the GDS volume is performed with the sdxvolume command.

moony# sdxvolume -N -c gfs -v control <Enter>
moony# sdxvolume -N -c gfs01 -v volume01 <Enter>

Procedure 3. GFS Shared File System creation (node A (active node), node B (standby node))

Create the GFS Shared File System on either one of the nodes.

Use mkfs_sfcfs(1M) to create the GFS Shared File System.

When the GFS Shared File System is created for the first time after installation, activation of the GFS Shared File System is necessary before file system creation.

• Create a management partition for the GFS Shared File System on either one of the nodes.

# sfcsetup -c /dev/sfdsk/gfs/rdsk/control <Enter>

• Register node information in the management partition of the GFS Shared File System on each node.

sunny# sfcsetup -a /dev/sfdsk/gfs/rdsk/control <Enter>
moony# sfcsetup -a /dev/sfdsk/gfs/rdsk/control <Enter>

• Activate the GFS Shared File System on each node.

sunny# sfcfrmstart <Enter>
moony# sfcfrmstart <Enter>

• Create the GFS Shared File System on either one of the nodes.

# mkfs -F sfcfs -o node=sunny,moony /dev/sfdsk/gfs01/rdsk/volume01 <Enter>

Procedure 4. Adding the relevant GFS Shared File System to /etc/vfstab (node A (active node), node B (standby node))

Add the mount information for the relevant GFS Shared File System to /etc/vfstab on each node. Be sure to specify "noauto" in the "mount options" field as a parameter of the mount information to be added.

/dev/sfdsk/gfs01/dsk/volume01 /dev/sfdsk/gfs01/rdsk/volume01 /sfcfs sfcfs - no -

Procedure 5. Setting the definition of switchover of the RMS application as the RMS configuration (node A (active node), node B (standby node))

Set up the RMS configuration by using the userApplication Configuration Wizard.

For details on setup, refer to "PRIMECLUSTER Configuration and Administration Guide" and

"PRIMECLUSTER RMS Configuration and Administration Guide."

In GFS Shared File System, the following measures are necessary in order to always use GDS volume by active state.

• For cluster application settings, a GDS resource "Gds:Global-Disk-Services" must not be registered in the GDS volume of the GFS Shared File System.
• For cluster application settings, an Fsystem resource "LocalFileSystems" must not be registered in the GFS Shared File System.
• For GDS volume, must not execute /usr/opt/reliant/bin/hvgdsetup.

Procedure 6. Confirming settings (node A (active node), node B (standby node))

After mounting the GFS Shared File System on each node, start RMS and then confirm whether the settings of the /etc/vfstab file and the RMS application are proper, paying attention to the following points:

• Whether the GFS Shared File System can be mounted on both nodes according to the /etc/vfstab file descriptions.
• Whether the RMS application switches over to a standby node at failover of the active node.

If mounting of the GFS Shared File System fails, the following may be the cause of the failure (apply the indicated solution):

• The type of the file system specified in the "/etc/vfstab" file is incorrect

Solution: Correct the /etc/vfstab file.

• The GDS volume is not ACTIVE

Solution: Activate the GDS volume.