SNMP monitoring

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

You can enable SNMP monitoring on individual nodes on your cluster, and you can also monitor cluster information from any node. Generated SNMP traps are sent to your SNMP network. You can configure an event notification rule that specifies the network station where you want to send SNMP traps for specific events, so that when an event occurs, the cluster sends the trap to that server. OneFS supports SNMP in read-only mode. OneFS supports SNMP version 2c, which is the default value, and SNMP version 3.

Note: OneFS does not support SNMP v1. Although an option for v1/v2c may be displayed, if you select the v1/v2c pair, OneFS will only monitor through SNMP v2c.

You can configure settings for SNMP v3 alone or for both SNMP v2c and v3.

Note: If you configure SNMP v3, OneFS requires the SNMP-specific security level of AuthNoPriv as the default value when querying the cluster. The security level AuthPriv is not supported.

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.isilon.oneFSss.ssLocalNodeId.0 maps to .1.3.6.1.4.1.12124.3.2.0. The part of the name that refers to the OneFS SNMP namespace is the 12124 element. 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 data types and other properties. You can download MIBs that are created for SNMP-monitoring of an Isilon cluster from the web-administration interface or manage them using the command-line interface. MIBs are stored in /usr/local/share/snmp/mibs/ on a OneFS node. The OneFS ISILON-MIBs serve two purposes:

ISILON-MIB is a registered enterprise MIB. Isilon 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. As the name implies, 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 the 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/ or /usr/local/share/snmp/mibs, depending on the tool that you use.

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 -c public -m All <node IP> isilon

If the MIB files are not in the default Net-SNMP MIB directory, you may need to specify the full path, as in the following example. Note that all three lines are a single command.

snmpwalk -m /usr/local/share/snmp/mibs/ISILON-MIB.txt:/usr/local\
/share/snmp/mibs/ISILON-TRAP-MIB.txt:/usr/local/share/snmp/mibs \
/ONEFS-TRAP-MIB.txt -v2c -C c -c public <node IP> enterprises.onefs
Note: The previous examples are run from the snmpwalk command on a cluster. Your SNMP version may require different arguments.

Copyright © 2015 EMC Corporation. All rights reserved. Please help us improve this topic. Send your comments and suggestions to docfeedback@isilon.com.