Solaris Cluster "lost operational quorum; aborting" Panic on Node/System/Server Resolution Path
(Doc ID 1020625.1)
Last updated on NOVEMBER 21, 2017
Solaris Cluster - Version 3.1 to 4.3 [Release 3.1 to 4.3] Solaris Cluster Geographic Edition - Version 3.1 to 4.3 [Release 3.1 to 4.3] Oracle Solaris on SPARC (64-bit) Oracle Solaris on x86-64 (64-bit)
This document will guide you through first steps in troubleshooting Sun/Solaris Cluster 3.x/4.x panics due to "lost operational quorum" Symptoms: Solaris Cluster node panics with the following message:
Aug 12 13:19:42 node1 unix: [ID 265925 kern.notice] CMM: Cluster lost operational quorum; aborting.
Explanation: A Solaris Cluster framework can stay up if the number of quorum votes present are one vote more than half the possible votes. Otherwise, the remaining cluster hosts(nodes) will panic with the above message. Each cluster node is assigned 1 vote. The number of votes for the quorum devices is determined by Solaris Cluster software based on the number of nodes and quorum devices (QD) attached such that, when all nodes except one go down, the votes present is sufficient for the remaining node to stay in the cluster. For example, in a 3 node cluster with 1 quorum device, each node has 1 vote whereas the only quorum device has 2 votes. Therefore, one node and the quorum device will form 3 votes out of possible 5.
See also: <Document 1010549.1> Solaris Cluster "lost operational quorum" Panic Explained
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!