Create a node class compatibility

OneFS automatically adds a new node of the same equivalence class to an existing node pool. For new nodes that are not equivalence-class, you can create a node class compatibility to add these nodes to an existing node pool.

About this task

The following compatibilities are currently supported: S200/S210, X200/X210, X400/X410, and NL400/NL410. For example, if you have a node pool made up of three or more S200 nodes, you can create a compatibility so that new S210 nodes are automatically added to the S200 node pool.
Note Image

New nodes must have compatible RAM and the same drive configurations as their older counterparts to be provisioned into existing node pools. If drive configurations are not the same because of SSD capacity or SSD count differences, you can create SSD compatibilities, as well.

Procedure

  1. Select File System > Storage Pools > SmartPools.
    The SmartPools tab displays two lists: Tiers & Node Pools and Compatibilities.
  2. Click Create a compatibility.
    The Create a Compatibility dialog box displays a drop-down list of compatibility types.
  3. From the Compatibility Type list, select Node Class.
    Two additional drop-down lists are added, First Node Class and Second Node Class.
  4. In the First Node Class list, accept the current selection, or make a new selection.
  5. In the Second Node Class list, accept the current selection, or make a new selection.
  6. Click Create Compatibility.
    A Confirm Create Compatibility dialog box appears, with one or more check boxes that you must select before proceeding. The check boxes describe the results of the operation.
  7. Select all check boxes, and then click Confirm.

Results

The node class compatibility is created, and is also described in the Compatibilities list. For example, a message such as "The S200 Node Class is now considered compatible with the S210 Node Class" is displayed. The result of the new compatibility appears in the Tiers & Node Pools list. If the new nodes are node-class compatible, but remain unprovisioned, you still need to create an SSD compatibility for the new nodes. If L3 cache is disabled on the targeted node pool, the new nodes remain unprovisioned, and an error message is generated.