1. Support
  2. Knowledge base
  3. 100026825

VCS will not start, citing the following error: "V-16-1-10037 VxFEN driver not configured"

Article: 100026825
Last Published: 2020-07-21
Ratings: 3 1
Product(s): Appliances, InfoScale & Storage Foundation

Problem

After rebooting the server, VCS will not start and reports the following error messages:

2010/09/05 11:16:30 VCS CRITICAL V-16-1-10037 VxFEN driver not configured.
Retrying...
2010/09/05 11:16:45 VCS CRITICAL V-16-1-10037 VxFEN driver not configured.
Retrying...
2010/09/05 11:17:00 VCS CRITICAL V-16-1-10037 VxFEN driver not configured.
Retrying...
2010/09/05 11:17:15 VCS CRITICAL V-16-1-10031 VxFEN driver not configured.
VCS Stopping. Manually restart VCS after configuring fencing
 

Error Message

2010/09/05 11:17:00 VCS CRITICAL V-16-1-10037 VxFEN driver not configured.
Retrying...
2010/09/05 11:17:15 VCS CRITICAL V-16-1-10031 VxFEN driver not configured.
VCS Stopping. Manually restart VCS after configuring fencing

Cause

There are pre-existing keys left on disks.
 

When attempting to start I/O Fencing manually, vxfen will report the following:

# systemctl start vxfen
Starting vxfen..
Starting vxfen.. Done
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!
 

Solution


 Clear the keys on the node where you have the problem using the following example:
 

 

1. Start a "ksh" shell:
# ksh
 
2. Create a file of all disks on the system.
# ls /dev/rdsk | egrep '^c[12345678].*s2$' | while read disk
do
echo "/dev/rdsk/$disk" >> /tmp/file1
done
 
3.Validate file
# cat /tmp/file1
 
(OR vxfenadm –g all –f /etc/vxfentab  ) to just check
4. Validate vxfenadm
# vxfenadm -g all -f /tmp/file1
 
5. Register and ignore
# vxfenadm -a -k TMP -f /tmp/file1
 
6. Validate vxfenadm
# vxfenadm -g all -f /tmp/file1
 
7. Clear and abort keys
# vxfenadm -c -k TMP -f /tmp/file1
 
8. Validate vxfenadm
# vxfenadm -g all -f /tmp/file1
 
9. Exit the shell
# exit
 
****************************************************
****************************************************
ALTERNATE PROCEDURE
 
5. Register and ignore
# vxfenadm -m -k TMP -f /tmp/file1
 
7. Clear and abort keys
# vxfenadm -x -k TMP -f /tmp/file1
 
****************************************************
To pre-empt and abort the victim keys
vxfenadm –p –k TMP –V65,86,67,83,0,0,0,0 –f /tmp/file1
OR
vxfenadm –p –k TMP –vAVCS –f /tmp/file1 (Note – may not work)
 

 

 

 

Was this content helpful?

Article Languages