Verify cluster health

Download PDF of this page

Before you upgrade a cluster, you should verify that the nodes are healthy and eligible to participate in the cluster, and that the cluster is in quorum.

  1. Verify that the nodes in the cluster are online and are eligible to participate in the cluster: cluster show

    cluster1::> cluster show
    Node                  Health  Eligibility
    --------------------- ------- ------------
    node0                 true    true
    node1                 true    true

    If any node is unhealthy or ineligible, check EMS logs for errors and take corrective action.

  2. Set the privilege level to advanced: set -privilege advanced

  3. Enter y to continue.

  4. Verify the configuration details for each RDB process.

    • The relational database epoch and database epochs should match for each node.

    • The per-ring quorum master should be the same for all nodes.

      Note that each ring might have a different quorum master.

      To display this RDB process…​ Enter this command…​

      Management application

      cluster ring show -unitname mgmt

      Volume location database

      cluster ring show -unitname vldb

      Virtual-Interface manager

      cluster ring show -unitname vifmgr

      SAN management daemon

      cluster ring show -unitname bcomd

      This example shows the volume location database process:

    cluster1::*> cluster ring show -unitname vldb
    Node      UnitName Epoch    DB Epoch DB Trnxs Master    Online
    --------- -------- -------- -------- -------- --------- ---------
    node0     vldb     154      154      14847    node0     master
    node1     vldb     154      154      14847    node0     secondary
    node2     vldb     154      154      14847    node0     secondary
    node3     vldb     154      154      14847    node0     secondary
    4 entries were displayed.
  5. If you are operating in a SAN environment, verify that each node is in a SAN quorum: event log show -messagename scsiblade.*

    The most recent scsiblade event message for each node should indicate that the scsi-blade is in quorum.

    cluster1::*> event log show -messagename scsiblade.*
    Time                Node             Severity      Event
    ------------------- ---------------- ------------- ---------------------------
    MM/DD/YYYY TIME  node0            INFORMATIONAL scsiblade.in.quorum: The scsi-blade ...
    MM/DD/YYYY TIME  node1            INFORMATIONAL scsiblade.in.quorum: The scsi-blade ...
  6. Return to the admin privilege level: set -privilege admin

Related information