SSD compatibilities

OneFS cannot autoprovision new nodes if they have different SSD capacities or SSD counts from the other nodes in a node pool. To enable new nodes with different SSD capacities or counts to join a compatible node pool, you can create SSD compatibilities.

For example, if your cluster already has an S200 node pool, and you add a new S200 node, OneFS would attempt to autoprovision the new node to the S200 node pool. However, if the new S200 node has higher-capacity SSDs than the older S200 nodes, or a different number of SSDs, then OneFS cannot autoprovision the new node. To enable the new node to be autoprovisioned, you can create SSD compatibilities for the S200 node type.

As with node class compatibilities, SSD compatibilities require the nodes to be compatible, as shown in the following table:

Existing node pool
SSD compatibilities that can be created
S200, S210*
X200, X210*
X400, X410*
NL400, NL410*
S210, S200*
X210, X210*
X410, X410*
NL410, NL400*
Generation 6-F800
All-flash system; SSD compatibilities not supported
Generation 6-H600
Gen 6-H600
Generation 6-H500
Gen 6-H500
Generation 6-H400
Gen 6-H400
Generation 6-A2000
Gen 6-A2000
Generation 6-A200
Gen 6-A200
* Also requires a node class compatibility with the existing node pool class.
Note Image

For SSD compatibilities to be created, all nodes must have L3 cache enabled. If you attempt to create a node class compatibility and appropriate SSD compatibilities, and the process fails with an error message, make sure that the existing node pool has L3 cache enabled. Then try again to create the compatibility. 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 Infinity models 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 will be less than optimal.