Vxfen can't start with warning "Cluster presently fencing out a node"

book

Article ID: 100005074

calendar_today

Updated On:

Description

Error Message

Console error:

Host1:~ Cluster presently fencing out a node.\n\tOperation will be retried.
 

Cause

There was fencing key left in the disk.

Resolution

1) Stop VCS

Host 1:~ # hastatus -sum
VCS ERROR V-16-1-10600 Cannot connect to VCS engine
VCS WARNING V-16-1-11046 Local system not available

2) Execute vxfenclearpre command

Host1:~ # vxdg import vxfencoorddg

Host1:~ # /opt/VRTSvcs/vxfen/bin/vxfenclearpre

This script recovers from a preexisting split brain condition.
This script removes the SCSI-3 registrations and reservations on
the coordinator disks as well as the data disks contained in shared
disk groups.

        ******** WARNING!!!!!!!! ********

THIS SCRIPT CAN ONLY BE USED IF THERE ARE NO OTHER ACTIVE NODES IN
THE CLUSTER!  VERIFY ALL OTHER NODES ARE POWERED OFF OR INCAPABLE OF
ACCESSING SHARED STORAGE.

If this is not the case, data corruption will result.

Do you still want to continue: [y/n] (default : n) y

Cleaning up the coordinator disks...


Cleaning up the data disks for all shared disk groups...


Successfully removed SCSI-3 persistent registration and reservations
from the coordinator disks as well as the shared data disks.

You can retry starting fencing module. In order to restart the whole
product, you might want to restart the system.

 

Applies To

SLES linux 10 SP3

SF_HA5.0MP4

Issue/Introduction

Customers can start vxfen: Host1:~ # /etc/init.d/vxfen start
Starting VxFEN:
Loaded 2.6.16.60-0.54.5-smp on kernel 2.6.16.60-0.69.1-smp
Warning: No modules found for 2.6.16.60-0.69.1-smp, using compatible
modules for 2.6.16.60-0.54.5-smp.
Starting vxfen.. Done


VCS did not start after adding "UseFence = SCSI3" in the main.cf