PowerScale OneFS 9.8.0.0 Web Administration Guide

Node 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. Modify node pool compatibility using the command-line interface.

Add new node type to existing node pool

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

Can you add A300/A3000 nodes to an A200/A2000 node pool?

If you want to add a half chassis of A300 or A3000 to a given cluster of A2000 or A200, what are the requirements? Are you required to add a full chassis of A300 or A3000, or is the option of using a half-populated chassis of A300/A3000 or corresponding A300L/A3000L feasible?

• The answer is that it is possible to add only two nodes, however the drive capacities must match. In addition, the A300s that you are adding must be configured so that the cache to L3 matches the A200s.
• If you are using SSDs for cache, then they do not need to match, because mismatched SSDs perform correctly if you are using L3 cache. See the following table for compatibility requirements.

Remove a node type from a node pool

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

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.

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.