PowerScale OneFS 9.2.1.0 CLI Administration Guide

PDF

Compatibilities

If there are compatibility restrictions between new nodes and the existing nodes in a node pool, OneFS cannot autoprovision the new nodes. To enable new nodes to join a compatible node pool, add the new node type to the existing node pool. You modify node pool compatibilities using the command-line interface.

For example, suppose that your cluster has an X410 node pool and you add a newer X410 node. OneFS attempts to autoprovision the new node to the X410 node pool. However, if the new X410 node has different RAM than the older X410 nodes, then OneFS cannot autoprovision the new node. To provision the new node into the existing X410 node pool, add the new X410 node type to the existing X410 node pool. Use the isi storagepool nodetypes list command to view the node types and their IDs, then isi storagepool nodepools modify <nodepool_name> --add-node-type-ids=<new_nodetype_id> to add the new node type to the existing node pool. For example, suppose that your X410 node pool name is x410_nodepool and isi storagepool nodetypes list shows the new node type ID as 12:

isi storagepool nodepools modify x410_nodepool --add-node-type-ids=12

You can also remove a node type from a node pool, for example, if you want to move that node type into its own pool. Using the above example, to remove the X410 nodes with a different RAM capacity and node type ID 12 from the X410 node pool:

isi storagepool nodepools modify x410_nodepool --remove-node-type-ids=12

Performance considerations and incompatible node types determine compatibility restrictions. For example:

Performance can be affected by adding a particular node type to an existing node pool.
A particular node type can be incompatible with the nodes in an existing pool.

In that case, OneFS generates a message describing the compatibility issue.

NOTE SSD compatibilities require that L3 cache is enabled on all nodes. If you attempt to move nodes with SSDs into a node pool on which L3 cache is not enabled, the process fails with an error message. Ensure that L3 cache is enabled for the existing node pool and try again. L3 cache can only be enabled on nodes that have fewer than 16 SSDs and at least a 2:1 ratio of HDDs to SSDs. On Generation 6 nodes that support SSD compatibilities, SSD count is ignored. If SSDs are used for storage, then SSD counts must be identical on all nodes in a node pool. If SSD counts are left unbalanced, node pool efficiency and performance can be less than optimal.

For example, the PowerScale F200 and F600 node types are incompatible with each other and with previous node types. You cannot add F200 or F600 nodes to a node pool containing any other node types (for example, S210 or F800 nodes). They are not hybrid nodes, so enabling L3 cache is not an option. They can be used as storage only.

The following table shows the compatibilities between specific PowerScale archive and hybrid nodes. Nodes in the same row of the table are compatible. Compatible nodes can be provisioned into the same node pool. Nodes that are not compatible cannot be provisioned into the same node pool.


PowerScale node	Compatible PowerScale node
A2000	A3000 (OneFS 9.2.1.0 and later)
A200	A300 (OneFS 9.2.1.0 and later)
H400	A300 (OneFS 9.2.1.0 and later)
H500	H700 (OneFS 9.2.1.0 and later)
H5600	H7000 (OneFS 9.2.1.0 and later)

A300 nodes are compatible with A200 and H400 nodes. However, A200 and H400 nodes are not compatible with each other.

See Compatibility restrictions for more information.