PowerScale OneFS 9.8.0.0 Web Administration Guide

SNMP monitoring

You can use SNMP to remotely monitor the PowerScale cluster hardware components, such as fans, hardware sensors, power supplies, and disks. Use the default Linux SNMP tools or a GUI-based SNMP tool of your choice for this purpose.

isi event channels create snmpchannel snmp --host=<snmp-receiver.example.com> --snmp-auth-password=<string> --snmp-security-name=<string> --snmp-priv-password=<string> --snmp-engine-id=<string>

The location where you send traps is specified in the isi event channels command. Event notification rules specify which types of event types are sent to those locations. By default, both SNMP version 2c and SNMP version 3 are turned off in OneFS . You must turn on the version you use. SNMP version 3 is recommended over SNMP version 2, as version 2 is considered less secure.

OneFS does not support SNMP version 1. Although the command isi snmp settings modify includes the option --snmp-v1-v2-access, OneFS monitors only through SNMP version 2c.

You can configure settings for SNMP version 3 alone or for both SNMP version 2c and version 3.

Elements in an SNMP hierarchy are arranged in a tree structure, similar to a directory tree. As with directories, identifiers move from general to specific as the string progresses from left to right. Unlike a file hierarchy, however, each element is not only named, but also numbered.

For example, the SNMP entity iso.org.dod.internet.private.enterprises.powerscale.cluster.clusterStatus.clusterName.0 maps to .1.3.6.1.4.1.12124.1.1.1.0. The element 12124 refers to the OneFS SNMP namespace. Anything further to the right of that number is related to OneFS-specific monitoring.

Management Information Base (MIB) documents define human-readable names for managed objects and specify their datatypes and other properties. You can download MIBs that are created for SNMP-monitoring of a PowerScale cluster from the OneFS web administration interface or manage them using the command-line interface (CLI). MIBs are stored in /usr/share/snmp/mibs/ on a OneFS node. The OneFS ISILON-MIBs serve two purposes:

• Augment the information available in standard MIBs.
• Provide OneFS-specific information that is unavailable in standard MIBs.

ISILON-MIB is a registered enterprise MIB. PowerScale clusters have two separate MIBs:

ISILON-MIB

Defines a group of SNMP agents that respond to queries from a network monitoring system (NMS) called OneFS Statistics Snapshot agents. These agents snapshot the state of the OneFS file system at the time that it receives a request and reports this information back to the NMS.

ISILON-TRAP-MIB

Generates SNMP traps to send to an SNMP monitoring station when relevant circumstances occur that are defined in the trap protocol data units (PDUs).

The OneFS MIB files map the OneFS-specific object IDs with descriptions. Download or copy MIB files to a directory where your SNMP tool can find them, such as /usr/share/snmp/mibs/.

To enable Net-SNMP tools to read the MIBs to provide automatic name-to-OID mapping, add -m All to the command, as in the following example:

snmpwalk -v2c I$ilonpublic -m All <node IP> isilon

During SNMPv2c configuration, it is required that you set the community string using a command similar to the following:

isi snmp settings modify -c <newcommunitystring>

You are not allowed to enable SNMPv2 unless the community string has been changed from the default.

If the MIB files are not in the default Net-SNMP MIB directory, specify the full path, as in the following example. All three lines are a single command.

snmpwalk -m /usr/local/share/snmp/mibs/ISILON-MIB.txt:/usr \
/share/snmp/mibs/ISILON-TRAP-MIB.txt:/usr/share/snmp/mibs \
/ONEFS-TRAP-MIB.txt -v2c -C c -c public isilon