Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

PowerScale OneFS 9.5.0.0 Web Administration Guide

Compatibility restrictions

OneFS enforces pool and node type restrictions for cluster configuration and node compatibility. Restrictions represent the rules governing cluster configuration and node compatibility. They prevent performance degradation of the node types within a node pool.

OneFS supports the following restriction types.
  • Hard node type restriction: A rule that is not allowed. If you try to modify a cluster configuration in a way that generates a hard restriction, the modification fails. OneFS presents a message that describes the restrictions that result in denying the modification request.
  • Soft node type restriction: A rule that is allowed but requires confirmation before being implemented. If you try to modify a cluster configuration in a way that generates a soft restriction, OneFS presents an advisory notice. To continue, you must confirm the modification.
    NOTE:If the modification request results in both hard and soft restrictions, OneFS reports only the hard restrictions.
  • Pool restriction: A rule that exists for a node pool.
    • Hard pool restriction: A rule that represents an invalid change to a node group. For example, you cannot modify a manual node pool or modify a pool in a way that results in that pool being underprovisioned.
    • Soft pool restriction: A rule that represents a change to a node group that requires confirmation. Requesting a modification that results in a soft pool restriction generates an advisory notice. To continue, you must confirm the modification.
Some examples of hard and soft restrictions are as follows.
  • There are hard node type restrictions for the PowerScale F200 and F600 node types.
    • F200 and F600 node types are incompatible with each other and with previous node types.
    • F200 node types can form node pools only with other compatible F200 nodes.
    • F600 node types can form node pools only with other compatible F600 nodes.
    • F200 and F600 nodes are storage only nodes and cannot be used as L3 cache.
    • F200 nodes must have the same SSD size to be considered compatible.
    If you try to add F200 or F600 nodes to an incompatible node pool, the modification fails.
  • A300 nodes are compatible with A200 and H400 nodes. However, A200 and H400 nodes are not compatible with each other.
  • There is a soft node type restriction for different RAM capacities. Any difference in RAM is allowed and there are no RAM ranges for compatibilities. If you add a node to a node pool that has different RAM than existing nodes in that pool, OneFS displays an advisory notice. Confirm the operation to add the node to the node pool.

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\