Come join our live training webinar every other Wednesday at 11am PST and hear LogicMonitor experts explain best practices and answer common questions. We understand these are uncertain times, and we are here to help!
EMC Isilon systems provide instrumentation via SNMP. As such, LogicMonitor Auto-Properties subsystem automatically discovers these devices and adds Isilon to the system.categories device property.
An exception is that in Isilon clusters we’re not able to automatically discover the master node. In this case you’ll need to add IsilonMaster to that device’s system.categories property.
These are the steps to monitor an Isilon cluster:
Each item is broken down into further details, below.
The following is extracted from the OneFS User Guide. From within the Isilon management interface:
Isilon (and LogicMonitor) recommends that you configure your network monitoring system (LogicMonitor) to query each node directly. This approach ensures that all nodes have external IP addresses and can respond to SNMP queries (and file requests). It also ensures that LogicMonitor can monitor and alert on data for each node (such as temperature sensors and hardware status), that may not be apparent if only a cluster address is monitored.
Add each node to LogicMonitor using an external IP address. So long as SNMP is enabled on the Isilon cluster, and the appropriate community string has been entered into LogicMonitor, no further action is required to monitor the individual nodes. Ideally, these IP addresses will be fixed to a specific node.
The final step is to add a cluster address to LogicMonitor. This address will be used to monitor cluster wide issues (Cluster CPU load; cluster wide IFS space usage, etc.) Because LogicMonitor cannot distinguish which Isilon node address should be used for cluster data collection, it is necessary to set the property “IsilonMaster” on this device.
(Cluster data is only collected from this single device, rather than all cluster nodes, to avoid getting an alert about cluster-wide issues from every single node in the cluster. Instead, only a single alert is generated.)
Add the cluster address as a device to LogicMonitor, but be sure to edit the property System.Categories property for this device to include the string IsilonMaster
This will trigger the association of cluster wide datasources with that device.
In This Article