- About LogicMonitor
- Cloud Monitoring
- Dashboards and Widgets
- Getting Started
- LM Service Insight
- Backup and Recovery Systems
- Cloud Resources
- Networking & Firewalls
- Cisco VoIP Monitoring
- Cisco UCS Monitoring
- Brocade Application Delivery Controllers
- Checkpoint Firewalls
- Cisco APIC Monitoring
- Cisco ASA/ASR
- Cisco Device SNMP and NTP Configuration
- Cisco Firepower Chassis Manager Monitoring
- Cisco IP SLA Monitoring
- Citrix NetScalers
- Dell Switch Monitoring
- F5 BIG-IP Monitoring
- Fortinet Fortigate Firewalls
- Infoblox Monitoring
- Interface Status alerting and Bandwidth Utilization
- Juniper SRX
- Kemp LoadMaster Load Balancers
- Meraki Cloud Access Controllers
- NetFlow Monitoring
- Palo Alto Firewalls
- pfSense Firewalls
- Sonicwall Firewalls
- Operating Systems & Virtualization
- VMware Horizon Monitoring
- Citrix XenServer Monitoring
- Citrix XenApp/XenDesktop Monitoring
- ESXi Servers and vCenter/vSphere Monitoring
- Linux Disk Performance
- Linux File Systems reporting more than 100% usage
- Linux Inodes
- Linux Interface Bandwidth Utilization
- Linux NFS Server
- Monitoring a Domain Controller (DC)
- Monitoring Remote Linux Files
- NTP Configuration
- NTP Monitoring
- Nutanix HyperConverged Infrastructure
- SNMP v1/v2 Configuration
- SNMPv3 Configuration
- Solaris Monitoring
- Troubleshooting Perfmon Access
- Troubleshooting SNMP
- Troubleshooting WMI
- VMware vCenter Server Appliance (VCSA) Monitoring
- Windows Cluster Monitoring
- Windows Firewall Issues
- Windows Server 2000
- Windows XP
- Applications & Databases
- Microsoft Office 365 Monitoring
- OpenMetrics Monitoring
- Zoom Monitoring
- Apache Monitoring
- Cassandra Monitoring
- ConnectWise Monitoring
- Email Service Monitoring
- Java Applications
- Lighttpd Monitoring
- Microsoft Exchange Monitoring
- Microsoft SQL Server Monitoring
- MongoDB Monitoring
- MySQL Monitoring
- Nginx Monitoring
- Oracle Monitoring
- Pick & D3
- Postfix Monitoring
- PostgreSQL Monitoring
- RabbitMQ Monitoring
- Redis Monitoring
- Twilio Monitoring
- Varnish HTTP Accelerator
- Server & Operations Hardware
- Storage Systems
- Cisco HyperFlex Monitoring
- Apache Hadoop Monitoring
- EMC ECS
- EMC Isilon Monitoring
- EMC Unity Monitoring
- EMC VMAX
- EMC VNX/Clariion SAN
- EMC VNXe
- EMC VPLEX
- EMC XtremIO
- HPE 3PAR Storage
- HP MSA / StorageWorks / P2000
- HP P4000/Lefthand SANs
- NetApp E/EF-Series Monitoring
- NetApp Monitoring
- Nimble Storage
- Panzura Cloud Storage
- Quantum Small Tape Libraries
- VMware vSAN Monitoring
- Rest API Developers Guide
- RPC API Developers Guide - Deprecated
- Servicenow CMDB Integration
- Terminology and Syntax
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:
- configure SNMP on the cluster
- add each node to LogicMonitor
- add a cluster address, and configure it with the IsilonMaster category. (IMPORTANT!!)
Each item is broken down into further details, below.
Configure SNMP Monitoring
The following is extracted from the OneFS User Guide. From within the Isilon management interface:
- On the Cluster menu, point to Cluster Settings, and then click SNMP Monitoring. The SNMP Monitoring page appears.
In the Service area, enable SNMP monitoring as needed. The default setting is SNMP is enabled.
- To enable SNMP monitoring, select Enable. The SNMP process is enabled for the entire cluster.
In the Settings area, under General Settings, configure settings as needed.
To enable or disable the version or versions of the SNMP protocol to which the nodes respond, next to Protocol access, select a protocol choice from the list of three options. SNMP v3 access is enabled or disabled independently of v1 and v2c.
- Allow access via SNMP v1 and SNMP v2c only
- Allow access via SNMP v3 only
- Allow access via SNMP v1, SNMP v2c and SNMP v3
- In the System location box, type the system location name. This setting is the value that the node reports when responding to queries for the OID SNMPv2-MIb::sysLocation.0. Type any name that helps to identify the location of the node.
- To enable or disable the version or versions of the SNMP protocol to which the nodes respond, next to Protocol access, select a protocol choice from the list of three options. SNMP v3 access is enabled or disabled independently of v1 and v2c.
In the Settings area, configure protocol settings as needed.
- In the Settings area, under SNMP v1/v2c Settings , type the name of the community to which you are granting read-only rights. The default setting is public.Note: You must enable v1/v2c protocols in the General Settings section to ensure that the settings are active.
- In the Settings area, under SNMP v3 Settings, choose a user with read-only permissions and choose an SNMP v3 password.To change the name of the user with read-only permissions, in the Read-only user box, type the SNMP v3 security name. Do not include any space characters in the Read-only user setting. The default read-only user is “general.”If you want to set a new SNMP v3 authentication password, in the SNMP v3 password box, type the new password for the read-only user. The password must contain at least eight characters, and must not contain any space characters. The default password is “password.” In the Confirm password box, retype the SNMP v3 authentication password. Note: You must enable v3 protocols in the General Settings section to ensure that the settings are active.
- Click Submit.
Add Each Node to LogicMonitor
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.
Add a Cluster Address to LogicMonitor (IMPORTANT)
The final step is to add a SmartPool 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 SmartPool address as a device to LogicMonitor, but be sure to edit the property System.Categories for this device to include the string IsilonMaster
This will trigger the association of cluster wide datasources with that device.
In this Article: