The article shows how to fix "V-16-1-10037 VxFEN driver not configured" error

After rebooting the nodes in a cluster, Veritas Cluster Server (VCS) fails to start and the following messages are seen in the /var/VRTSvcs/log/engine_A.log file:

2007/10/22 05:16:47 VCS CRITICAL V-16-1-10037 VxFEN driver not configured. Retrying...
2007/10/22 05:17:02 VCS CRITICAL V-16-1-10037 VxFEN driver not configured. Retrying...
2007/10/22 05:17:17 VCS CRITICAL V-16-1-10037 VxFEN driver not configured. Retrying...
2007/10/22 05:17:33 VCS CRITICAL V-16-1-10037 VxFEN driver not configured. Retrying...
2007/10/22 05:17:48 VCS CRITICAL V-16-1-10037 VxFEN driver not configured. Retrying...
2007/10/22 05:18:03 VCS CRITICAL V-16-1-10037 VxFEN driver not configured. Retrying...
2007/10/22 05:18:18 VCS CRITICAL V-16-1-10029 VxFEN driver not configured. VCS Stopping. Manually restart VCS after configuring fencing


Attempting to start I/O Fencing manually results in the following error:

# ./S97vxfen start
Starting vxfen..
Starting vxfen.. Done
[/etc/rc2.d]# VCS FEN vxfenconfig NOTICE Driver will use SCSI-3 compliant disks.
VCS FEN vxfenconfig ERROR V-11-2-1016 There exists the potential for a preexisting split-brain
       The coordinator disks list no nodes which,
       are in the current membership.  However, they,
       also list nodes which are not in the,
       current membership.

       I/O Fencing Disabled!


This is a clear indication there are pre-existing keys left on the coordinator disks.

Resolution:

Clear these keys to start I/O fencing, using these commands:

# /opt/VRTSvcs/vxfen/bin/vxfenclearpre

# reboot