I/O fencing requires coordinator disks to be configured in a disk group that each cluster system can access. The use of coordinator disks enables the vxfen
driver to resolve potential split-brain conditions and prevent data corruption. A coordinator disk is not used for data storage, so it can be configured as the smallest LUN on a disk array to avoid wasting space.
Coordinator disks must meet the following requirements:
vxfentsthdw
utility to test for SCSI-3 PR support requires that disks be 1MB or greater. Smaller disks can be tested manually.
Contact Veritas support (http://support.veritas.com) for the procedure.
If you have already added and initialized disks you intend to use as coordinator disks, you can begin the following procedure at step 4.
To set up the disk group for coordinator disks
vxdisk
scandisks
command to scan the disk drives and their attributes. This command updates the VxVM device list and reconfigures DMP with the new devices. For example:
vxdisksetup
command to initialize a disk as a VxVM disk. The example command that follows specifies the CDS format:
# vxdisksetup -i
vxvm_device_name
format=cdsdisk
# vxdisksetup -i /dev/rdsk/c2t0d2s2 format=cdsdisk
Repeat this command for each disk you intend to use as a coordinator disk.
vxfencoorddg
. This group must contain an odd number of disks or LUNs and a minimum of three disks. Symantec recommends that you use only three coordinator disks, and that you use the smallest size disks or LUNs to conserve disk space.
For example, assume the disks have the device names c1t1d0
, c2t1d0
, and c3t1d0
.
See the Veritas Volume Manager Administrator's Guide.
Review the requirments for testing the coordinator disk group.
Review the following guidelines on testing support for SCSI-3:
If you did not configure ssh, enable each node to have remote rsh access to the other nodes during installation and disk verification. On each node, placing a "+" character in the first line of the /.rhosts
file gives remote access to the system running the install program. You can limit the remote access to specific nodes. Refer to the manual page for the /.rhosts
file for more information. Remove the remote rsh access permissions after the installation and disk verification process.
vxfentsthdw -n
command.
vxfenadm
-i
diskpath command to verify the disk serial number.
vxfentsthdw
utility has additional options suitable for testing many disks. You can test disks without destroying data using the -r
option. The options for testing disk groups (-g
) and disks listed in a file (-f
) are described in detail:
After Setting up the disk group for coordinator disks, test the coordinator disk group.
To test the coordinator disk group
# /opt/VRTSvcs/vxfen/bin/vxfentsthdw
Make sure system-to-system communication is functioning properly before performing this step.
After Testing the coordinator disk group, configure it for use.
-t
option to avoid automatically importing it when the nodes restart:
# echo "vxfencoorddg" > /etc/vxfendg
Do no use spaces between the quotes in the "vxfencoorddg" text.
This command creates the /etc/vxfendg
file, which includes the name of the coordinator disk group. Based on the contents of the /etc/vxfendg
file, the rc
script creates the /etc/vxfentab
file for use by the vxfen
driver when the system starts. The rc script also invokes the vxfenconfig
command, which configures the vxfen
driver to start and use the coordinator disks listed in /etc/vxfentab
. /etc/vxfentab
is a generated file; do not modify this file.
After I/O Fencing has been configured on all cluster nodes, copy the sample vxfenmode file over the /etc/vxfenmode file.
# cp /etc/vxfen.d/vxfenmode_scsi3_dmp /etc/vxfenmode
Enabling fencing involves editing the UseFence attribute in the VCS configuration file (main.cf
), verifying the configuration file syntax, copying the main.cf
to other nodes, and rebooting all nodes to start the fencing driver and VCS with fencing enabled.
main.cf
file:
vi
or another text editor to edit the main.cf
file. Modify the list of cluster attributes by adding the UseFence
attribute and assigning its value of SCSI3
:
/etc/VRTSvcs/conf/config/main.cf
file:
rcp
or another utility, copy the VCS configuration file from a node (for example, galaxy
) to the remaining cluster nodes. On each remaining node, type:
disabled
to scsi3
:
To ensure that I/O fencing is properly shut down, use the shutdown
command instead of the reboot
command.