IBM Support

Removing Shared Storage Pool (SSP) Node From SSP Cluster With Mappings

How To


Summary

Before using rmnode command to remove a node from SSP cluster, it may be necessary to do some cleanup with vhost mapping and ODM.

Objective

Best way to safely remove the nodes from SSP cluster that is still configured with vSCSI mappings.

Environment

Any VIO releases and levels 2.X, 3.x, 4.X 

Steps

1. First remove nodes that is not a DBN, MFS or LEADER node.
   
      How to determine current CAA LEADER node
     $ oem_setup_env
        # pooladm dump node | grep -i leader
           whichever one returns "amILeader=1" is the leader node.
 
      How to determine current MFS node
     $ oem_setup_env
      # pooladm pool lsmfs /var/vio/SSP/[CLUSTER_NAME]/D_E_F_A_U_L_T_061310
      You can also get [CLUSTER_NAME] using:  $ cluser -status ( or $ df | grep SSP)
 
    How to determine DBN node
     $ cluster -status -verbose | grep -p DBN
2.  Check any mapping on that node using
     $ lsmap -all 
     or create a file using below from oem_setup_env (below shows one vhost. Repeat for all vhost/VTD with SSP LU backed.
     # /usr/ios/cli/ioscli lsmap -vadapter vhost[NN]  > virtual_vhost[NN].mappings.txt
    
    NOTE: Edit above file to update SSP backed LUs only in case  the clients also include traditional backed vSCSI devices.
3. If the client lpar is active or in use, shut down the lpar
    # shutdown 
4. $ rmdev -dev vhost[NN] -recursive -f
5. Cleanup ODM for CuAt and CuDv
     cat virtual_mappings.txt | grep vtscsi | awk '{print "odmdelete -q name="$2" -o CuAt"}' |sh
     cat virtual_mappings.txt | grep vtscsi | awk '{print "odmdelete -q name="$2" -o CuDv"}' |sh
6. Remove the node based on the FQN or shortname used to create these node.
    $ cluster -rmnode -f -clustername [CLUSTER_NAME] -hostname [hostname]
7. If the remaining nodes are DBN, MFS or LEADER, use clstatstop to move these over and restart the cluster services and apply steps above for removing 
that node.
     To stop cluster services.
     $ clstartstop -stop -n  [CLUSTER_NAME]  -m [hostname] 
    To restart cluser services.
    $ clstartstop -start -n  [CLUSTER_NAME]  -m [hostname] 
 Updated: 10/15/2025 - rajpat@us.ibm.com

Related Information

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB68","label":"Power HW"},"Business Unit":{"code":"BU070","label":"IBM Infrastructure"},"Product":{"code":"SSHQYKG","label":"PowerVM Enterprise Edition"},"ARM Category":[{"code":"a8m50000000L0aLAAS","label":"SSP-\u003EVIOS Node-\u003ESHARED STORAGE POOL (SSP)"}],"ARM Case Number":"TS017232129","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]

Document Information

Modified date:
15 October 2025

UID

ibm17171376