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

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 182.
3
Make any necessary repairs to system 2.
4
Restart system 2.
Apparent potential
split-brain conditionsystem
2 is down and system 1 is
ejected
Cluster ID on the I/O fencing key of coordinator disk does not match
the local clusters 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
The warning implies that the local cluster with the cluster ID 57069 has keys.
However, the disk also has keys for cluster with ID 48813 which indicates that
nodes from the cluster with cluster ID 48813 potentially use the same coordinator
disk.
You can run the following commands to verify whether these disks are used by
another cluster. Run the following commands on one of the nodes in the local
cluster. For example, on galaxy:
galaxy> # lltstat -C
57069
galaxy> # cat /etc/vxfentab
/dev/vx/rdmp/disk_7
/dev/vx/rdmp/disk_8
181Troubleshooting SFCFS
Troubleshooting I/O fencing