Veritas Storage Foundation 5.1 SP1 Cluster File System Administrator"s Guide (5900-1738, April 2011)

vxfenconfig: ERROR: 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!

Note: During the system boot, because the HP-UX rc sequencer redirects the stderr

of all rc scripts to the file /etc/rc.log, the error messages will not be printed on

the console. It will be logged in the /etc/rc.log file.

Also, the following information is displayed on the console:

<date> <system name> vxfen: WARNING: Potentially a preexisting

<date> <system name> split-brain.

<date> <system name> Dropping out of cluster.

<date> <system name> Refer to user documentation for steps

<date> <system name> required to clear preexisting split-brain.

<date> <system name> I/O Fencing DISABLED!

<date> <system name> gab: GAB:20032: Port b closed

Note: If syslogd is configured with the -D option, then the informational message

will not be printed on the console. The messages will be logged in the system

buffer. The system buffer can be read with the dmesg command.

However, the same error can occur when the private network links are working

and both systems go down, system 1 restarts, and system 2 fails to come back up.

From the view of the cluster from system 1, system 2 may still have the

registrations on the coordinator disks.

To resolve actual and apparent potential split-brain conditions

◆

Depending on the split-brain condition that you encountered, do the following:

Determine if system1 is up or not.

If system 1 is up and running, shut it down and

repair the private network links to remove the

split-brain condition.

Restart system 1.

Actual potential split-brain

condition—system 2 is up and

system 1 is ejected

Troubleshooting SFCFS

Troubleshooting I/O fencing

180