6.3.4 Shared Disk Unit Resource Registration Procedure

Perform the following procedure on a node that composes the cluster system.

Logging in with system administrator access privileges
Log in to a node that composes the cluster system using system administrator access privileges.
Creating a shared disk definition file
A shared disk definition file is a file to declare physical connection configuration of nodes in a cluster system and shared disk units. Use the following format.
Resource key name Device name Node identification name Resource key name Device name Node identification name :
- Describe "Resource key name, Device name, and Node identification name" in one line for every shared disk unit connected to each node.
- "Resource key name", "Device name", and "Node identification name" are space delimited.
- Specify values as follows for "Resource name", "Device name", and "Node identification name".
  Resource key name
  For a resource key name, specify a resource name that indicates a shared relationship for every shared disk unit. The name should be the same by device shared between nodes. The resource key name is specified in "shd number" format. "shd" is a fixed text string. "number" can contain any 4-digit figure. When multiple shared disks exist, specify different "number"s.
  [Example] When /dev/sdb and /dev/sdc are connected to and shared between multiple nodes
```
    Resource key name of /dev/sdb: shd0001
    Resource key name of /dev/sdc: shd0002
```
  Device name
  For a device name, specify the device path of a shared disk unit in the full path.
  When using the mirroring among servers, specify the device path of the iSCSI devices that are created in "4.6 Disk Setting for Performing Mirroring among Servers [4.3A40 or later] [RHEL6]" in the full path. Maximum 16 iSCSI devices can be described. Describe the pair of the iSCSI devices to be mirrored. Do not register only one of the pair of the iSCSI devices to be mirrored.
  [Example] When the device is /dev/sdb.
```
    /dev/sdb
```
  Note
  - When using DM-MP
    - Describe a device name with /dev/mapper/mpathX format.
    - Do not describe a device name with /dev/dm-X format.
    - Do not describe a native device (sd device) which composes mpath devices.
  - For a guest in the virtual environment
    - Describe a device name for a guest. For example, for the virtio block device of the KVM guest, describe the device name for the KVM guest /dev/vdX, not the device name for the host OS /dev/sdX.
  Node identification name
  For a node identification name, specify the ID number of a node where the shared disk unit resides. The node identification names can be checked with the clgettree(1) command.
  See
  For details on the clgettree(1) command, see the clgettree(1) command manual.
  
  [Example] In the following example, node1 and node2 are node identification names.
  # /etc/opt/FJSVcluster/bin/clgettree Cluster 1 cluster Domain 2 PRIME Shared 7 SHD_PRIME Node 3 node1 ON Node 5 node2 ON
  The following example shows a shared disk definition file created when "/dev/sdb" and "dev/sdc" are shared between node1 and node2.
  shd0001 /dev/sdb node1 shd0001 /dev/sdb node2 shd0002 /dev/sdc node1 shd0002 /dev/sdc node2
- When adding a shared disk device and registering the added shared disk device on the resource database, define only the information of the added shared disk device.
  Example: When registering the added disk device /dev/sdd (*1) on the resource database after shd0001 and shd0002 are already registered on the resource database:
```
    shd0003 /dev/sdd node1
    shd0003 /dev/sdd node2
```
  *1) Note
  The device name of the added shared disk device may not follow the device name of the registered device in alphabetical order. Make sure to check the device name of the added shared disk device before defining the information of the added disk device.
Resource registration with the clautoconfig(8) command
Execute the clautoconfig(8) command to register information in the shared disk definition file created in step 2. with the resource database using the following format:
[Format]
```
    /etc/opt/FJSVcluster/bin/clautoconfig -f Full_path_of_the_shared_disk_definition_file
```
[Example]
# /etc/opt/FJSVcluster/bin/clautoconfig -f /var/tmp/diskfile
Note
- If the clautoconfig(8) command terminates abnormally, take corrective actions as indicated in a displayed message. For clautoconfig(8) command messages, see the following documentation.
  - 4.3A20 or earlier
    "PRIMECLUSTER Cluster Foundation (CF) Configuration and Administration Guide."
  - 4.3A30 or later
    "PRIMECLUSTER Messages."
- If a device name of a shared disk unit varies depending on nodes, execute the clautoconfig(8) command on the node where all the device files described in the shared disk definition file exist. If the device files described in the shared disk definition file do not exist on the node where the clautoconfig(8) command was executed, the following error messages are output and the resource registration fails.
```
FJSVcluster: ERROR: clautoconfig: 6900: Automatic resource registration processing terminated abnormally. (detail: /dev/sdX)
```
  Example) The case where the following device files exist in each node is described.
  Node
  Internal disk
  Shared disk
  node1
  sda, sdb, and sdc
  sdd and sde
  node2
  sda and sdb
  sdc and sdd
  In this case, the contents of the shared disk definition file is as follows:
  shd0001 /dev/sdd node1 shd0001 /dev/sdc node2 shd0002 /dev/sde node1 shd0002 /dev/sdd node2
  In the shared definition file, device files of sdc, sdd, and sde are described.
  Device files of sdc, sdd, and sde exist on node node1, however the device file of sde does not exist on node node2. Therefore, in this example, you need to execute the clautoconfig(8) command on node node1.

Node	Internal disk	Shared disk
node1	sda, sdb, and sdc	sdd and sde
node2	sda and sdb	sdc and sdd

Confirming resource registration

Check information of the shared disk units registered with the resource database using the clgettree(1) command.

[Example]

The following example shows clgettree(1) command output generated when resource registration is performed using the shared disk definition file shown as an example in step 2.

The resources in the "DISK" class are shared disk unit resources. The resources in the "SHD_DISK" class are resources that indicate shared disk unit shared relationships.

# /etc/opt/FJSVcluster/bin/clgettree
    Cluster 1 cluster
      Domain 2 PRIME
         Shared 7 SHD_PRIME
                SHD_DISK 14 SHD_Disk14 UNKNOWN
                        DISK 15 sdb UNKNOWN node1
                        DISK 16 sdb UNKNOWN node2
                SHD_DISK 17 SHD_Disk17 UNKNOWN
                        DISK 18 sdc UNKNOWN node1
                        DISK 19 sdc UNKNOWN node2
         Node 3 node1 ON
                DISK 15 sdb UNKNOWN
                DISK 18 sdc UNKNOWN
         Node 5 node2 ON
                DISK 16 sdb UNKNOWN
                DISK 19 sdc UNKNOWN

Note

The clautoconfig(8) command does not check shared disk units in a specified shared disk definition file whether they are physically connected to nodes. If any error is found in the shared disk definition file after clautoconfig(8) command execution, it is necessary to perform the recovery procedure as follows on all nodes that compose the cluster system and then perform resource registration again. In a situation where hardware unit resources other than shared disk units are registered, it is also necessary to register those resources again.

[Recovery procedure]

Resetting the resource database
Reset the resource database using the clinitreset(8) command.
See
For details, see the clinitreset(8) command manual.
Rebooting the node
Reboot the node.