- Notes, cautions, and warnings
- Introduction to this guide
- InsightIQ overview
- Cluster monitoring
- Performance reports
- Performance reports overview
- Live Performance Reports overview
- Cluster Performance report overview
- Node Performance report overview
- Network Performance report overview
- Client Performance report overview
- Disk Performance report overview
- File System Performance report overview
- File System Cache Performance report overview
- Cluster Capacity Performance report overview
- Deduplication Performance report overview
- Cluster Events Performance report overview
- Jobs and Services Performance report overview.
- Live Performance reports
- Publish reports
- Scheduling Performance reports
- Interpreting Performance reports
- File System reports
- Creating custom reports
- InsightIQ export data
Isilon InsightIQ User Guide
Active Clients report
The Active Clients report shows the number of unique client addresses that generate protocol traffic on the monitored cluster.
Clients that are connected, but not generating any traffic, are not counted in this report. You can optionally break out this data by node or protocol.
The recommended number of active clients that are supported for NFS is approximately 1,000 per node (OneFS 7.1.1 and earlier).
For SMB 2.0 and later, the number of active clients that are supported depends on the version of OneFS.
| OneFS version | Number of active clients per node (SMB 2.0 or later) |
|---|---|
| 7.0 Through 7.1 | 1,000 |
| 7.1.1 and later | 1,500 |
Depending on usage details, exceeding the recommendations in OneFS 7.1.0 and earlier can lead to dropped connections or other performance problems. Generally speaking, if the number of active connections exceeds 90 percent of the limits, add nodes to the cluster when possible.
In OneFS 7.1.1 and later, over allocation is handled differently. Connection requests are denied when the total number of clients equals 90 percent of the total recommended limit for the cluster. If there many active clients, and if that quantity is near the supported limit, check each node to ensure that the load is evenly distributed. Verify that any one node is not oversubscribed.
Keep these limits in mind when you perform maintenance on a node so that you do not exceed the pool or cluster limit when you take nodes offline.
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\