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

Node is unable to join cluster while another node is being ejected
A cluster that is currently fencing out (ejecting) a node from the cluster prevents
a new node from joining the cluster until the fencing operation is completed. The
following are example messages that appear on the console for the new node:
...VxFEN ERROR V-11-1-25 ... Unable to join running cluster
since cluster is currently fencing
a node out of the cluster.
If you see these messages when the new node is booting, the vxfen startup script
on the node makes up to five attempts to join the cluster.
To manually join the node to the cluster when I/O fencing attempts fail
◆
If the vxfen script fails in the attempts to allow the node to join the cluster,
restart vxfen driver with the command:
# /sbin/init.d/vxfen stop
# /sbin/init.d/vxfen start
If the command fails, restart the new node.
System panics to prevent potential data corruption
When a node experiences a split-brain condition and is ejected from the cluster,
it panics and displays the following console message:
VXFEN:vxfen_plat_panic: Local cluster node ejected from cluster to
prevent potential data corruption.
See “How vxfen driver checks for preexisting split-brain condition” on page 179.
How vxfen driver checks for preexisting split-brain condition
The vxfen driver functions to prevent an ejected node from rejoining the cluster
after the failure of the private network links and before the private network links
are repaired.
For example, suppose the cluster of system 1 and system 2 is functioning normally
when the private network links are broken. Also suppose system 1 is the ejected
system. When system 1 restarts before the private network links are restored, its
membership configuration does not show system 2; however, when it attempts
to register with the coordinator disks, it discovers system 2 is registered with
them. Given this conflicting information about system 2, system 1 does not join
the cluster and returns an error from vxfenconfig that resembles:
179Troubleshooting SFCFS
Troubleshooting I/O fencing