This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
aix:vios_ssp [2025/10/16 16:40] manu |
aix:vios_ssp [2025/11/17 18:01] (current) manu |
||
|---|---|---|---|
| Line 4: | Line 4: | ||
| https://www.ibm.com/support/pages/shared-storage-pool-ssp-best-practice | https://www.ibm.com/support/pages/shared-storage-pool-ssp-best-practice | ||
| + | |||
| + | https://www.ibm.com/support/pages/shared-storage-pools-cheat-sheet | ||
| + | |||
| + | ===== What is a SSP ? ===== | ||
| + | |||
| + | It can be compared to a datastore into the VMware world, with some differences | ||
| + | |||
| + | {{:aix:vios_ssp01.png?800|}} | ||
| ===== Stop/start a cluster SSP ===== | ===== Stop/start a cluster SSP ===== | ||
| Line 324: | Line 332: | ||
| Get the redirection wrong and you will destroy your LU data | Get the redirection wrong and you will destroy your LU data | ||
| </code> | </code> | ||
| + | |||
| + | ===== Removing Shared Storage Pool (SSP) Node From SSP Cluster With Mappings ===== | ||
| + | |||
| + | https://www.ibm.com/support/pages/removing-shared-storage-pool-ssp-node-ssp-cluster-mappings | ||
| + | |||
| + | ===== Node Types (roles) In Shared Storage Pool Cluster ===== | ||
| + | |||
| + | In a SSP cluster, some nodes perform key roles handled in certain layers. These layers are classified as: | ||
| + | * Cluster Aware AIX (CAA) | ||
| + | * Database (DBN) | ||
| + | * Message Format Service (MFS) | ||
| + | |||
| + | === How to determine current CAA LEADER node === | ||
| + | |||
| + | <cli prompt='#'> | ||
| + | $ oem_setup_env | ||
| + | # pooladm dump node | grep -i leader | ||
| + | whichever one returns "amILeader=1" is the leader node. | ||
| + | </cli> | ||
| + | |||
| + | === How to determine current MFS node === | ||
| + | |||
| + | <cli prompt='#'> | ||
| + | $ oem_setup_env | ||
| + | # pooladm pool lsmfs /var/vio/SSP/[CLUSTER_NAME]/D_E_F_A_U_L_T_061310 | ||
| + | </cli> | ||
| + | |||
| + | === How to determine DBN node === | ||
| + | |||
| + | <cli prompt='$'> | ||
| + | $ cluster -status -verbose | grep -p DBN | ||
| + | </cli> | ||