Alarms
Several preconfigured alarm rules are provided for the Dell EMC Isilon Integration. You can access them from the Alarms tab, and use them as‐is or modify them to meet your needs.
In addition to the preconfigured alarms, you can create alarms for any metric that you can report on. You can create a rule to alert you when entities in your environment are approaching or exceeding a specified threshold for a particular metric.
You can also set alarms on any Isilon metric that you can report on. You can create a rule to alert you when approaching or exceeding a specified threshold for a particular metric.
For example, you can set a custom threshold for "% Subscribe Capacity” on a Isilon node or storage pool and receive notification when the threshold is breached.
For more information, see Chapter 5 “Cases and Alarms” in the Virtana Infrastructure Performance Management User Guide.
The following table contains descriptions of the Dell EMC Isilon Integration preconfigured alarms and their default settings.
Name | Description | Settings | |||
Tier 0 Isilon Cluster Disk Unavailable exceeds 85% | Dell EMC recommends to not let a single Isilon Cluster consume more than 85% of its available space. This alarm alerts users to this condition. |
| |||
Tier 0 Isilon Cluster System CPU Usage exceeds 80% | Depending on your sales cycle, a cluster that is operating beyond the 80% utilization should be expanded. The goal is to keep your cluster below 90% utilized. This alarm is configured to ensure ample time to upgrade. |
| |||
Tier 0 Isilon Disk Usage exceeds 85% | A general rule of thumb is to keep disk utilization levels below 85%. This is done so if a drive failure occurs, the additional rebuild load will not impact performance. |
| |||
Tier 0 Isilon Node /ifs exceeds 90% Utilized | Best practices dictate that no single node should be beyond 90% consumed. Isilon has maintenance jobs designed to ensure an even spread of data across a cluster, but in certain instances nodes can become imbalanced. |
| |||
Tier 0 Isilon Node Max Open Files | The Dell EMC Isilon Best Practices guide notes that any single node can not exceed 315k open files. |
| |||
Tier 0 Isilon Node NFSv3 Client Count exceeds 1000 | According to the Dell EMC Guide for Best Practices: "As a conservative best practice, active NFS v3 or v4 connections should be kept under 1,000, where possible. Although no maximum limit for NFS connections has been established, the number of available TCP sockets can limit the number of NFS connections. The number of connections that a node can process depends on the ratio of active-to-idle connections as well as the resources available to process the sessions. Monitoring the number of NFS connections to each node helps prevent overloading a node with connections." |
| |||
Tier 0 Isilon Node NFSv4 Client Count exceeds 1000 | According to the Dell EMC Guide for Best Practices: "As a conservative best practice, active NFS v3 or v4 connections should be kept under 1,000, where possible. Although no maximum limit for NFS connections has been established, the number of available TCP sockets can limit the number of NFS connections. The number of connections that a node can process depends on the ratio of active-to-idle connections as well as the resources available to process the sessions. Monitoring the number of NFS connections to each node helps prevent overloading a node with connections." |
| |||
Tier 0 Isilon Power Supply Failure | This alarm will detect when a power supply has failed within an Isilon Node. |
|