Home > Veritas Cluster Server Manual Pages
Table of contents
vxfenconfig - Configure the vxfen driver used in I/O fencing.
vxfenconfig -c [-s]
command configures the vxfen driver using parameters found in
file. For a list of possible parameters and usage information please see the manpage for
file. If this file is omitted I/O Fencing defaults to SCSI3 functionality.
When running in scsi3 mode,
command configures the vxfen driver using the coordinator disks
listed in the
file. Disks must be listed by the full file name of the raw or DMP device.
A minimum of three coordinator disks must be used (unless the -s
option is specified to configure the driver); in total, an odd
number of disks must be used.
Configure the vxfen driver.
Configure the vxfen driver for use with only a single coordinator disk.
The default (and Veritas recommendation) is three coordinator disks.
WARNING: When I/O fencing is configured to use only one coordinator
disk, the loss of the single coordinator disk results in the loss of
the availability of all applications in the cluster.
Unconfigure the vxfen driver.
List the coordinator disks used by vxfen driver.
Print out the version information.
Contains the list of coordinator disks, each of which is identified by
the full file name of the raw device. A minimum of three disks must be
configured in normal cases (except in the case of the [-s] option).
Multiple paths can also be listed. The
file is created by the rc script based on the contents of the
An example /etc/vxfentab file may contain the following lines:
Contains the name of the disk group containing the coordinator disks.
Typically, this disk group is vxfencoorddg. /etc/vxfendg
must exist on each system in the cluster.
To run I/O Fencing in disabled mode, add the following line to
WARNING: Veritas does not support SFRAC clusters using I/O fencing
in the disabled mode (vxfen_mode=disabled).
To run I/O Fencing in customized/sanvm mode, add the following lines to
vxfenadm(1M), vxfentsthdw(1M), vxfendebug(1M), vxfenmode(4M), vxfenclearpre(1M)
Last updated: Jan 2009
Copyright ©2009 Symantec Corporation
All rights reserved.