Veritas Storage Foundation 5.1 SP1 for Oracle RAC Administrator"s Guide (5900-1512, April 2011)

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:
1
Determine if system1 is up or not.
2
If system 1 is up and running, shut it down and
repair the private network links to remove the
split-brain condition.
3
Restart system 1.
Actual potential split-brain
condition—system 2 is up and
system 1 is ejected
1
Physically verify that system 2 is down.
Verify the systems currently registered with the
coordinator disks. Use the following command:
# vxfenadm -s all -f /etc/vxfentab
The output of this command identifies the keys
registered with the coordinator disks.
2
Clear the keys on the coordinator disks as well as
the data disks using the vxfenclearpre
command.
See “Clearing keys after split-brain using
vxfenclearpre command” on page 205.
3
Make any necessary repairs to system 2.
4
Restart system 2.
Apparent potential
split-brain condition—system
2 is down and system 1 is
ejected
Cluster ID on the I/O fencing key of coordinator disk does not match
the local cluster’s ID
If you accidentally assign coordinator disks of a cluster to another cluster, then
the fencing driver displays an error message similar to the following when you
start I/O fencing:
000068 06:37:33 2bdd5845 0 ... 3066 0 VXFEN WARNING V-11-1-56
Coordinator disk has key with cluster id 48813
which does not match local cluster id 57069
Troubleshooting SF Oracle RAC
Troubleshooting I/O fencing
204