Manually installing the performance monitoring tool
The performance monitoring tool is automatically installed by the installation toolkit. You can also install the performance monitoring tool manually for the releases that are not supported by the installation toolkit.
For more information, see Understanding the installation toolkit options. For more information about the performance monitoring tool, see Configuring the performance monitoring tool.
- Download the installation images and install the performance monitoring packages.
For information on the default directories in which these packages are extracted, see Location of extracted packages.
Performance monitoring packages
Then, use your operating system’s native package management mechanism to install the packages.gpfs.gss.pmsensors-version_release.os.target_arch.file_format gpfs.gss.pmcollector-version_release.os.target_arch.file_format
For example:
- To install 5.0.*-0 sensors on a Red Hat 7
x86_64 node, use the following
command:
rpm -ivh gpfs.gss.pmsensors-5.0.*-0.el7.x86_64.rpm
- To install 5.0.*-0 sensors on a SLES 12
x86_64 node, use the following
command:
rpm -ivh gpfs.gss.pmsensors-5.0.*.sles12.x86_64.rpm
- To install 5.0.*-0 sensors on an Ubuntu
amd64 node, use the following
command:
dpkg -i gpfs.gss.pmsensors_5.0.*-0.U*amd64.deb
- To install a 5.0.*-0 collector on a Red Hat
7 PPC64LE node, use the following
command:
rpm -ivh gpfs.gss.pmcollector-5.0.*-0.el7.ppc64le.rpm
- To install 5.0.*-0 sensors on a Red Hat 7
x86_64 node, use the following
command:
- To configure performance monitoring after the packages have been installed on all the selected
nodes, use the following
commands:
mmperfmon config generate --collectors collectorNode1[,collectorNode2,...] mmchnode --perfmon –N sensorNode1[,sensorNode2...]
- To enable performance monitoring on a protocol node for NFS, SMB, or Object, follow the given steps.
- For NFS:
- Install the
pm-ganesha
package as follows:- RHEL or SLES: rpm -ivh gpfs.pm-ganesha_version-release.os.target_arch.rpm
- Ubuntu: dpkg -i gpfs.pm-ganesha_version-release.deb
- Ensure that the /opt/IBM/zimon/defaults/ZIMonSensors_nfs.cfg sensor is
created as
shown:
sensors={ name = "NFSIO" period = 10 type = "Generic" restrict = "cesNodes" }
- Run the following command to add the
sensor:
mmperfmon config add --sensors /opt/IBM/zimon/defaults/ZIMonSensors_nfs.cfg
- Run the following code to ensure that the newly added sensor is made visible to the
system:
mmhealth node show nfs --refresh -N cesNodes
- Install the
- For SMB:
- Run the following command to add the
sensor:
mmperfmon config add --sensors /opt/IBM/zimon/defaults/ZIMonSensors_smb.cfg
Note: No additional sensor package is needed for the SMB sensors. - Run the following code to ensure that the newly added sensor is made visible to the
system:
mmhealth node show smb --refresh -N cesNodes
- Run the following command to add the
sensor:
- For Object:
- Install the
pmswift
package as follows:- RHEL:
rpm -ivh pmswift-version-release.noarch.rpm
- Ubuntu:
dpkg -i pmswift_version-release.deb
Where version is equal to or greater than 4.2 and release is equal to or greater than 0.
The installation of the pmswift RPM also copies SWIFT related sensors configuration files, namely, SwiftAccount.cfg, SwiftContainer.cfg, SwiftObject.cfg, and SwiftProxy.cfg to the performance monitoring tool’s installation directory, /opt/IBM/zimon/. The pmswift package converts the operational metrics for Object into a form that is usable by the performance monitoring tool.
- RHEL:
- Edit the Object configuration files for all Object servers that reside in the cluster
configuration repository (CCR), using the following command:
CCR then propagates the modified configuration files to/usr/local/pmswift/bin/pmswift-config-swift set
/etc/swift/
directory on all the protocol nodes within the cluster. The modified configuration files are:- account - *.conf
- container - *.conf
- object - *.conf
- proxy - *.conf
- Use the
/usr/local/pmswift/bin/pmswift-config-zimon set
command to edit the sensors configuration information stored in the CCR. This adds the SWIFT related following sensors entries:
These entries are then automatically propagated to the ZIMonSensors.cfg file in /opt/IBM/zimon on all the nodes in the cluster.{ # SwiftAccount operational metrics name = "SwiftAccount" period = 1 type = "generic" }, { # SwiftContainer operational metrics name = "SwiftContainer" period = 1 type = "generic" }, { # SwiftObject operational metrics name = "SwiftObject" period = 1 type = "generic" }, { # SwiftProxy operational metrics name = "SwiftProxy" period = 1 type = "generic" },
- Start the pmswiftd.service by using the following command:
systemctl start pmswiftd.service
- Start or restart the pmsensors.service by using the following command:
systemctl start|restart pmsensors.service
- Install the
pmswift
, see the Manually upgrading pmswift topic. - For NFS:
- If the protocol sensors are enabled on a GPFS-only node, you see an error message stating that the sensors are unavailable. However, the other sensors continue to run.
- Start the sensors on each node using the systemctl start pmsensors.service command.
- On the collector nodes, start the collector, using the systemctl start pmcollector.service command.
- To ensure that sensors and collectors are restarted after the node reboots, you can enable them
using the following commands:
- Sensors
- To enable sensors, use the systemctl enable pmsensors.service command.
- Collector
- To enable the collector, use the systemctl enable pmcollector.service command.
pmsensor
and
pmcollector
services are activated automatically.Metrics can be retrieved from any node in the system by using the mmperfmon query command. For more information, see mmperfmon command.
For more information about the performance monitoring tool, see Configuring the performance monitoring tool.