This chapter defines and describes the LEFTCLUSTER state.
Occasionally, while CF is running, you may encounter the LEFTCLUSTER state, as shown by running the cftool -n command. A message will be printed to the console of the remaining nodes in the cluster. This can occur under the following circumstances:
All cluster interconnects going to another node (or nodes) in the cluster are broken.
A node panics.
Node in kernel debugger
A node is left in the kernel debugger for too long and heartbeats are missed.
Entering the firmware monitor OBP
Will cause missed heartbeats and will result in the LEFTCLUSTER state.
Shutting down a node with the reboot command.
Note
Nodes running CF should normally be shut down with the shutdown command or with the init command.
These commands will run the rc scripts that will allow CF to be cleanly shut down on that node. If you run the reboot command, the rc scripts are not run, and the node will go down while CF is running. This will cause the node to be declared to be in the LEFTCLUSTER state by the other nodes.
If SF is fully configured and running on all cluster nodes, it will try to resolve the LEFTCLUSTER state automatically. If SF is not configured and running, or the SF fails to clear the state, the state has to be cleared manually. This section explains the LEFTCLUSTER state and how to clear this state manually.
