In Share Out mode, Volume Client systems use I/O fencing with coordinator volumes as described above. Volume Server systems, however, use I/O fencing with coordinator disks.
Note You cannot use coordinator volume and coordinator disks together for I/O fencing on the same system or in the same cluster.
See About I/O fencing in a SFVS environment.
The following steps are to be executed on a volume server system:
vxdg -o dgtype=san init sample_cvol_dg newdg01=Disk_1
Where sample_cvol_dg is the disk group name; and the disk group is of a SAN type.
vxassist -g sample_cvol_dg make sample_cvol 10m
Where sample_cvol_dg is the disk group name; sample_cvol is the SAN volume, and 10m is the size of the volume.
vxadm -g sample_cvol_dg volume export sample_cvol vcssysA.veritas.com exportperms=RDWR
Where vcssysA.veritas.com is a Volume Client system that the SAN volume sample_cvol is being exported to.
Once you have set up the coordinator volume, you need to initialize it using the /opt/VRTSvcs/vxfen/bin/vxfencvol utility. Attach the SAN volume, and then initialize it with the following commands:
To attach the SAN volume and initialize the volume
vxadm -g sample_cvol_dg volume attach sample_cvol sysA.example.com access_policy=RDWR io_access=ANY
/opt/VRTSvcs/vxfen/bin/vxfencvol -init -cvol /dev/vx/rdsk/vol_server/sample_cvol_dg/sample_cvol
vxadm -g sample_cvol_dg volume unattach sample_cvol sysA.example.com.
Before you start to modify the vxfenmode file, you must stop fencing. You then need to modify the vxfenmode file. The file is in /etc/vxfenmode.
The following code is a sample configuration for SANVM in the vxfenmode file:
vs_host=vol_server.example.com
To edit the VCS configuration to add the UseFence attribute
SCSI3
. For example, with the attribute added this portion of the file resembles:
rcp
, or some other available utility, copy the VCS configuration file to the other nodes. For example, on each node:
Note
To ensure that I/O fencing is shut down properly, use the shutdown
command instead of the reboot
command.