This section describes procedures for installing PRIMECLUSTER between guest OSes on multiple ESXi hosts in a VMware environment.
Note
The I/O fencing function must be set up at the earlier stage of configuring the cluster application.
The I/O fencing function uses the LUN on the shared disk unit registered to GDS disk class, or uses the LUN which contains the file system managed by the Fsystem resource. When using the I/O fencing function, register the GDS resource of the disk class containing the LUN or the disk, or register the Fsystem resource to the cluster application.
The I/O fencing function cannot be used in the environment where the Gds resources and Fsystem resources are respectively registered in the multiple cluster applications.
In the cluster application where a disk is not managed by the Fsystem resource or GDS, do not set the I/O fencing function.
Set the path policy for the Native Multipathing (NMP) as "Most Recently Used" or "Round Robin". No other settings are supported.
When using the file system that is created on the shared disk as Fsystem resources, you need to register all the file systems that are created on the same disk (LUN) or on the same disk class to the same userApplication. Due to the restriction of the I/O fencing function, you cannot create multiple file systems on one disk (LUN) or on one disk class and register each file system to the different userApplications to monitor and control them.
In /etc/fstab.pcl file, add either of the following description formats to specify the devices of the file systems controlled by Fsystem resources.
When using GDS
/dev/sfdsk/<disk_class_name>/dsk/<volume_name>
Without using GDS
/dev/disk/by-id/ name
/dev/disk/by-path/ name
LABEL=<file_system_label_name>
UUID=<file_system_UUID>
/dev/sd name
