Help on File System > Storage Pools > SmartPools
The following information and controls are available at .
- Tiers & Node Pools
- Provides status information for node pools and tiers (groupings of node pools), as follows:
- Name
- Name of tier or node pool.
- State
- The current state of the tier or node pool: Good, Caution, Warning, or Unprovisioned.
- Nodes
- The numerical range of nodes in this node pool or tier.
- Requested Protection
- The current data protection setting for this node pool or tier.
- SSD/L3
- How SSDs, if any, are used in the node pool, as follows:
- L3 Cache
- Displayed if the node pool has SSDs that are used as L3 cache.
- Has SSDs
- Displayed if the node pool has SSDs that are not used as L3 cache.
- –
- Displayed if the node pool does not have any SSDs.
- HDD % Used
- The percentage of used space on hard disk drives on the cluster.
- SSD % Used
- The percentage of used space on solid-state drives on the cluster.
- Actions
- View or edit settings for a node pool or tier, or delete a tier. Node pools cannot be deleted.
- Create a Tier
- Enables you to group one or more node pools into a single named storage pool that can be configured to store a particular type of data. For example, you could assign a collection of Isilon S200 and S210 node pools to a tier specifically created to store data that requires high availability and fast access. You could create another tier containing Isilon NL400 and HD400 node pools specifically for archival storage. You can mix and match node pools into tiers that best suit your workflow. A node pool can belong to only one tier.
- Compatibilities
- This list provides the status of compatibilities on your cluster, as follows:
- Description
- Describes the effects of compatibilities created on the cluster.
- Action
- Enables you to delete a compatibility. You might delete a compatibility after you have obtained enough equivalence-class nodes to form their own node pool.
- Create a Compatibility
- Enables you to create a compatibility between similar Isilon nodes that are not considered equivalence-class nodes. This enables unprovisioned nodes to be provisioned, and therefore operational within your cluster. For example, if you had a node pool of three Isilon S200 nodes, and decided to add a single S210 node to your cluster, the S210 node would not be provisioned and therefore could not be used. However, if you created a compatibility between S200 and S210 nodes, the S210 would be provisioned as part of the S200 node pool, and would be fully functional.