PowerFlex 3.X: How To Change/Remove Data IP from Primary MDM in Single-node Cluster
Summary: User wanted to remove data IP of obsolete network from Cluster Use in Single node Cluster.
Instructions
When using one management network (mgmt. IP) and two Data Networks (data1, data2 IPs) While in single-node mode, data2 Network became faulty and could not switch mode to 3-node Cluster as a result.
To go around this, we remove all data2 IPs from the system.
mgmt. IP: 10.66.0.x
data1 IP: 100.100.0.x
data2 IP: 200.200.0.x (network to be removed)
Primary_mdm_name: MDM2 (10.66.0.102, 100.100.0.102)
Standby_mdm_name: MDM1 (10.66.0.101, 100.100.0.101)
Standby_mdm_name: TB1 (100.100.0.200)
Steps:
1- Remove data2 IP from all SDSs using ScaleIO GUI or using CLI command:
scli --remove_sds_ip (--sds_id | --sds_name | --sds_ip [--sds_port ]) --sds_ip_to_remove
2-remove all Standby Nodes. Scli --remove_standby_mdm --remove_mdm_name ie.
scli --remove_standby_mdm --remove_mdm_name MDM1 scli --remove_standby_mdm --remove_mdm_name TB1
3- Re-add Standby nodes without data2 IP
scli --add_standby_mdm --mdm_role --new_mdm_ip [--new_mdm_management_ip ] --new_mdm_name --allow_asymmetric_ips --force_clean --allow_asymmetric_ips -> Allow the added node to have a different number of IPs from the primary node --force_clean -> Clean previous configuration of the MDM ie. scli --add_standby_mdm --mdm_role manager --new_mdm_ip 100.100.0.101 --new_mdm_management_ip 10.66.0.101 --new_mdm_name MDM1 --allow_asymmetric_ips --force_clean scli --add_standby_mdm --mdm_role tb --new_mdm_ip 100.100.0.200 --new_mdm_name TB1 --allow_asymmetric_ips --force_clean
4- Switch cluster mode from single-node to 3-node cluster
scli --switch_cluster_mode --cluster_mode --add_slave_mdm_name --add_tb_name ie. scli --switch_cluster_mode --cluster_mode 3-node --add_slave_mdm_name MDM1 --add_tb_name TB1
5- Switch Ownership of Primary MDM to the newly added mdm node
scli --switch_mdm_ownership --new_master_mdm_name ie. scli --switch_mdm_ownership --new_master_mdm_name MDM1
6- Switch Cluster to a single-node.
scli --switch_cluster_mode --cluster_mode --remove_slave_mdm_name --remove_tb_name ie. scli --switch_cluster_mode --cluster_mode 1_node --remove_slave_mdm_name MDM2 --remove_tb_name TB1
7- Remove Standby mdm Node containing the data2 IP.
scli --remove_standby_mdm --remove_mdm_name ie. scli --remove_standby_mdm --remove_mdm_name MDM2
8- Re-add Standby mdm Node without data2 IP
scli --add_standby_mdm --mdm_role --new_mdm_ip [--new_mdm_management_ip ] --new_mdm_name --allow_asymmetric_ips --force_clean --allow_asymmetric_ips -> Allow the added node to have a different number of IPs from the primary node --force_clean -> Clean previous configuration of the MDM ie. scli --add_standby_mdm --mdm_role manager --new_mdm_ip 100.100.0.102 --new_mdm_management_ip 10.66.0.102 --new_mdm_name MDM2 --allow_asymmetric_ips --force_clean
9- Switch Cluster to 3-nodes.
scli --switch_cluster_mode --cluster_mode --add_slave_mdm_name --add_tb_name ie. scli --switch_cluster_mode --cluster_mode 3_node --add_slave_mdm_name MDM2 --add_tb_name TB1
10- (Optional) Switch ownership of Primary MDM back to original Node
scli --switch_mdm_ownership --new_master_mdm_name MDM2
Additional Information
- The same steps work if switching from single-node to 5-node.
- This Method Has been Tested with no Virtual IPs Configured for the Cluster.
- If Virtual IPs are configured, then all virtual IPs must be removed first
Also:
In PowerFlex 4.X The words Master and Slave are changed to Primary and Secondary
Example: Add or remove Nodes to the MDM cluster to swicth from 3 to 5 node cluster
3.x
#scli --switch_cluster_mode --cluster_mode 3_node --remove_slave_mdm_name XXXX --remove_tb_name YYY
#scli --switch_cluster_mode --cluster_mode 5_node --add_slave_mdm_name XXXX --add_tb_name YYY4.x
#scli --switch_cluster_mode --cluster_mode 3_node --remove_secondary_mdm_name XXXX --remove_tb_name YYY
#scli --switch_cluster_mode --cluster_mode 5_node --add_secondary_mdm_name XXXX --add_tb_name YYY