Whenyou run the vxfen startup file to start I/O fencing,
thescript creates this /etc/vxfentab file on each node with
alist of all paths to each coordinator disk. The startup script
usesthe contents of the /etc/vxfendg and /etc/vxfenmode
files.
Thusany time a system is rebooted, the fencing driver
reinitializesthe vxfentab file with the current list of all
pathsto the coordinator disks.
Note: The/etc/vxfentab file is a generated file; do not
modifythis file.
Anexample of the /etc/vxfentab file on one node resembles
asfollows:
Rawdisk:
/dev/sdx
/dev/sdy
/dev/sdz
DMPdisk:
/dev/vx/rdmp/sdx
/dev/vx/rdmp/sdy
/dev/vx/rdmp/sdz
/etc/vxfentab
Insome cases you must remove disks from or add disks to an existing coordinator
disk group.
Warning: If you remove disks from an existing coordinator disk group, then be
sureto remove the registration and reservation keys from these disks before you
add the disks to another disk group.
Preparing to configure disk-based I/O fencing
Make sure you performed the following tasks before configuring I/O fencing for
VCS:
Install the correct operating system.
Install the VRTSvxfen RPM when you installed VCS.
Install a version of Veritas Volume Manager (VxVM) that supports SCSI-3
persistent reservations (SCSI-3 PR).
ConfiguringVCS clusters for data integrity
Preparingto configure disk-based I/O fencing
92