User Tools

Site Tools


gpfs:gpfs_ces

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
gpfs:gpfs_ces [2024/04/19 12:00]
manu [enable SMB / NFS]
gpfs:gpfs_ces [2025/04/28 12:07] (current)
manu [enable SMB / NFS]
Line 151: Line 151:
 Add IP address for cluster NFS and CIFS Add IP address for cluster NFS and CIFS
 <cli prompt='#'>​ <cli prompt='#'>​
-mmces address policy [even-coverage | balanced-load | node-affinity | none]+mmces address policy [even-coverage | balanced-load | node-affinity | none]
 </​cli>​ </​cli>​
  
-  * even-coverage+  ​* **even-coverage**
   Distributes the addresses among the available nodes. The even-coverage policy is the default address distribution policy. ​   Distributes the addresses among the available nodes. The even-coverage policy is the default address distribution policy. ​
-  * balanced-load+  ​* **balanced-load**
   Distributes the addresses to approach an optimized load distribution. The load (network and CPU) on all the nodes are monitored. Addresses are moved based on given policies for optimized load throughout the cluster.   Distributes the addresses to approach an optimized load distribution. The load (network and CPU) on all the nodes are monitored. Addresses are moved based on given policies for optimized load throughout the cluster.
-  * node-affinity+  ​* **node-affinity**
   Attempts to keep an address on the node to which the user manually assigned it. If the mmces address add command is used with the --node option, the address is marked as being associated with that node. Similarly, if an address is moved with the mmces address move command, the address is marked as being associated with the destination node. Any automatic movement, such as reassigning a down node's addresses, does not change this association. Addresses that are enabled with no node specification do not have a node association.   Attempts to keep an address on the node to which the user manually assigned it. If the mmces address add command is used with the --node option, the address is marked as being associated with that node. Similarly, if an address is moved with the mmces address move command, the address is marked as being associated with the destination node. Any automatic movement, such as reassigning a down node's addresses, does not change this association. Addresses that are enabled with no node specification do not have a node association.
  
   Addresses that are associated with a node but assigned to a different node are moved back to the associated node if possible.   Addresses that are associated with a node but assigned to a different node are moved back to the associated node if possible.
  
 +Force the balance
 +<cli prompt='#'>​
 +# mmces address move --rebalance
 +</​cli>​
 +
 +Or
 +
 +<cli prompt='#'>​
 +# mmces address move --ces-ip {IP[,​IP...]} --ces-node Node
 +</​cli>​
 +
 +<cli prompt='#'>​
 +# mmces address list --full-list
 +cesAddress ​   cesNode ​                 attributes ​                                  ​cesGroup ​    ​cesPrefix ​  ​preferredNode ​           unhostableNodes
 +------------- ------------------------ -------------------------------------------- ------------ ----------- ------------------------ -----------------
 +172.128.1.171 ​  ​gpfsa01.mydom.lu ​  ​object_database_node,​object_singleton_node ​  ​nfsgroup01 ​  ​none ​       gpfsa01.mydom.lu ​  none
 +172.128.1.172 ​  ​gpfsb01.mydom.lu ​  ​none ​                                        ​nfsgroup01 ​  ​none ​       gpfsb01.mydom.lu ​  none
 +
 +</​cli>​
  
 +https://​www.ibm.com/​docs/​en/​storage-scale/​5.1.8?​topic=reference-mmces-command
 ==== configure authentification ==== ==== configure authentification ====
  
gpfs/gpfs_ces.1713520843.txt.gz · Last modified: 2024/04/19 12:00 by manu