Monitoring system health by using the mmhealth command

The mmhealth command displays the results of the background monitoring for the health of a node and services that are hosted on the node. You can use the mmhealth command to view the health status of a whole cluster in a single view.

Every service that is hosted on an IBM Storage Scale node has its own health monitoring service. All the subcomponents like the file system or network interfaces are monitored through the monitoring service of their main component. Only the subcomponents of CES service such as NFS, SMB, Object, and authentication have their own health monitors. The mmhealth command gets the health details from these monitoring services. The role of a node in monitoring determines the components that need to be monitored. This is an internal node role, and a node can have more than one role. For example, a CES node can also be a node with file systems and performance monitoring. The role of the node also determines the monitoring service that is required on a specific node. For example, you do not need a CES monitoring on a non-CES node. The monitoring services are only started if a specific node role is assigned to the node. Every monitoring service includes at least one monitor.

Prerequisites

The following criteria must be met to use the health monitoring function on your GPFS cluster:
  • Only Linux® and AIX® nodes are supported.
  • All operating systems that are running IBM Storage Scale 5.1.x, including AIX nodes, must have Python 3.6 or later installed.
  • All operating systems that are running IBM Storage Scale 5.0.x, including AIX nodes, must have Python 2.7 installed.
  • CCR must be enabled.
  • The cluster must be able to use the mmhealth cluster show command.

Known limitations

The mmhealth command has the following limitations:
  • Only GPFS monitoring is supported on AIX.
  • The mmhealth command does not fully monitor Omni-Path connections.