Home > Storage > PowerScale (Isilon) > Product Documentation > Storage (general) > PowerScale OneFS: Cluster Composition, Quorum, and Group State > Interpreting group changes
Even in the example above we can be certain of several things:
In this case, a check of node 2 and 3’s logs will confirm whether they also rebooted simultaneously indicating a cluster-wide event.
At scale, the group state output can often be complex and difficult to comprehend. For example, consider the following group state report from a large cluster:
# sysctl efs.gmp.group
efs.gmp.group: <47,3501>: { 1:0-22, 2-3:0-17, 4, 5:0-11, 6-10:0-22, 11-13:0-23, 14:0-11,13-19,21-23, 15:0-22, 16-31:0-23, 32-38:0-17, 39-41:0-35, 42:0-14,16-35, 43-45:0-33, 46-48:0-35, 49-53:0-22, 54-69, 70-80:0-11, 81:0-10, 82-89,91-93,95-126:0-11, 127-129:0-10, 130-133:0-11, diskless: 4, 54-69, smb: 1-89,91-93,95-133, nfs: 1-89,91-93,95-133, hdfs: 1-89,91-93,95-133, all_enabled_protocols: 1-89,91-93,95-133, isi_cbind_d: 1-89,91-93,95-133, lsass: 1-89,91-93,95-133, s3: 1-89,91-93,95-133 }
From this output, the following determinations can be made:
If more detail is wanted, the sysctl efs.gmp.current_info command will report extensive current GMP info.