Add IP addresses to a
PowerFlex system
Optionally, add IP addresses to a three-node MDM cluster
PowerFlex system after deployment. This topic explains how to do so in an ESXi environment.
Prerequisites
Prepare the IP addresses and networking required for your environment.
Configure the new IP addresses/networks on all systems.
Verify connectivity between all components, using the new network.
NOTE: Use the ping command to check connectivity, including the relevant MTU size in the command.
About this task The following example shows how to configure a system for an IPv6 network.
Network
IPv6 Addresses
SVM Management
2a01:6f40:2003:104:10:54:80:121 (Gateway)
2a01:6f40:2003:104:10:54:80:122
2a01:6f40:2003:104:10:54:80:127
2a01:6f40:2003:104:10:54:80:128
ESXi Management
2a01:6f40:2003:104:10:54:80:124
2a01:6f40:2003:104:10:54:80:125
2a01:6f40:2003:104:10:54:80:126
SVM Data
NOTE: Data IP addresses are used for MDMs, SDSs, and SDRs
A virtual IP address is only used for the MDM Virtual IP address.
2a01:6f40:2003:192:192:168:73:6
2a01:6f40:2003:192:192:168:73:5 (Gateway)
2a01:6f40:2003:192:192:168:73:7
2a01:6f40:2003:192:192:168:73:8
2a01:6f40:2003:192:192:168:73:10 (Virtual IP address)
ESXi Data (Data IP addresses are used for SDCs)
2a01:6f40:2003:192:192:168:73:1
2a01:6f40:2003:192:192:168:73:2
2a01:6f40:2003:192:192:168:73:3
SDR External IP Addresses
2a01:6f40:2003:192:172:168:73:6
2a01:6f40:2003:192:172:168:73:7
2a01:6f40:2003:192:172:168:73:8
Steps
Open a CLI session with the primary MDM:
scli --login --username <NAME> [--password <PASSWORD>] [--ldap_authentication | --native_authentication] [(--approve_certificate_once | --approve_certificate]
--accept_banner_by_scripts_only
Query the cluster, and keep a note of the output for later use:
Output example:
Cluster:
Name: SIO-DEVOPS, Mode: 3_node, State: Normal, Active: 3/3, Replicas: 2/2
Virtual IPs: 192.168.73.10
Master MDM:
Name: Manager2, ID: 0x1e143dda22790f31
IPs: 192.168.73.7, Management IPs: 10.54.80.127, Port: 9011, Virtual IP interfaces: eth1
Version: 2.6.10000
Slave MDMs:
Name: Manager1, ID: 0x1788ff920173be80
IPs: 192.168.73.6, Management IPs: 10.54.80.122, Port: 9011, Virtual IP interfaces: eth1
Status: Normal, Version: 2.6.10000
Tiebreakers:
Name: TB1, ID: 0x4ec52e035f72ea42
IPs: 192.168.73.8, Port: 9011
Status: Normal, Version: 2.6.10000
Switch MDM cluster mode to single mode:
scli --switch_cluster_mode --cluster_mode 1_node --remove_slave_mdm_id <SLAVE_ID> --remove_tb_id <TIE_BREAKER_ID>
For example:
scli --switch_cluster_mode --cluster_mode 1_node --remove_slave_mdm_id 0x1788ff920173be80 --remove_tb_id 0x4ec52e035f72ea42
The secondary and
tiebreaker have been reverted to standby mode.
Remove the standby MDMs mentioned in the previous step:
scli --remove_standby_mdm --remove_mdm_id <STANDBY_ID>
scli --remove_standby_mdm --remove_mdm_id <STANDBY_ID>
For example:
scli --remove_standby_mdm --remove_mdm_id 0x4ec52e035f72ea42
scli --remove_standby_mdm --remove_mdm_id 0x1788ff920173be80
Add the removed secondary MDM back to the system as a standby MDM, using the old and the additional IP addresses.
scli --add_standby_mdm --mdm_role <ROLE> --new_mdm_ip <DATA_IP_ADDRESSES> --new_mdm_management_ip <MANAGEMENT_IP_ADDRESSES> --allow_asymmetric_ips --force_clean --new_mdm_virtual_ip_interface <INTERFACE_NAMES>
For example:
scli --add_standby_mdm --mdm_role manager --new_mdm_ip 192.168.73.6,2a01:6f40:2003:192:192:168:73:6 --new_mdm_management_ip 10.54.80.122,2a01:6f40:2003:104:10:54:80:122 --allow_asymmetric_ips --force_clean --new_mdm_virtual_ip_interface eth1,eth3
Add the removed
tiebreaker back to the system as a standby MDM, using the old and the additional IP addresses.
scli --add_standby_mdm --mdm_role tb --new_mdm_ip <DATA_IP_ADDRESSES> --allow_asymmetric_ips --force_clean
For example:
scli --add_standby_mdm --mdm_role tb --new_mdm_ip 192.168.73.8,2a01:6f40:2003:192:192:168:73:8 --allow_asymmetric_ips --force_clean
Switch MDM cluster operation mode back to three-node cluster mode.
scli --switch_cluster_mode --cluster_mode 3_node --add_slave_mdm_id <ID> --add_tb_id <ID>
For example:
scli --switch_cluster_mode --cluster_mode 3_node --add_slave_mdm_id 0x0041f4ba31fbde70 --add_tb_id 0x6a1d2a0645dfd6c2
To verify cluster functionality, switch MDM ownership:
Switch ownership:
scli --switch_mdm_ownership --new_master_mdm_id <ID>
For example:
scli --switch_mdm_ownership --new_master_mdm_id 0x0041f4ba31fbde70
Query the MDM cluster to get the current cluster state/health:
Repeat steps 3 to 8 for the secondary MDM (the one that was initially the primary MDM).
All the IP addresses have now been added, and the initial primary MDM is now the primary MDM again, in a three-node MDM cluster.
Add virtual IP addresses to the MDM cluster. In the command, include both the existing IP addresses, and the new ones.
scli --modify_cluster_virtual_ips --cluster_virtual_ip <VIRTUAL_IP_ADDRESSES>
For example:
scli --modify_cluster_virtual_ips --cluster_virtual_ip 192.168.73.10,2a01:6f40:2003:192:192:168:73:10
Update the SDCs with the old and new virtual IP addresses. On each ESXi host in the
PowerFlex system, perform the following steps:
Find the host's IniGuidStr:
esxcli system module parameters list -m scini
Add the new IP addresses to the ESXi host. In the command, include both the old and the new virtual IP addresses:
esxcli system module parameters set -m scini -p "IoctlIniGuidStr=<INI_GUID_STRING> IoctlMdmIPStr=<IP_ADDRESSES> "
For example:
esxcli system module parameters set -m scini -p "IoctlIniGuidStr=86dbe022-d0fd-4a4c-927a-cbf7eb4549f2 IoctlMdmIPStr=192.168.73.10,2a01:6f40:2003:192:192:168:73:10"
After modifying the IP addresses, a reboot cycle is needed for the changes to take effect. For all ESXi SDCs, gracefully reboot one node at a time.
Procedures for gracefully rebooting a node are described in "Gracefully shut down or reboot a node" in the "Reference" section of the
Upgrade
PowerFlex Guide .
Add new IP addresses to SDSs and SDRs.
Add the new IP addresses to SDSs, using the command:
scli --add_sds_ip (--sds_id <ID> | --sds_name <NAME> | --sds_ip <IP> [--sds_port <PORT> ]) --new_sds_ip <IP>
[--sds_ip_role {sdc_only | sds_only | all }] [--force_add_ip]
For example:
scli --mdm_ip 192.168.73.7 --add_sds_ip --sds_ip 192.168.73.4 --new_sds_ip 192.168.73.24
Add SDRs, using the command:
scli --add_sdr_ip (--sdr_id <ID> | --sdr_name <NAME> | --sdr_ip <IP> [--sdr_port <PORT> ]) --new_sdr_ip <IP> [--sdr_ip_role <ROLE> ]
For example:
scli --mdm_ip 192.168.73.7 --add_sdr_ip --sdr_ip 192.168.73.4 -- new_sdr_ip 192.168.73.24
Verify that the new SDS IP addresses are being used, using the command:
scli --query_sds_connectivity_status (--protection_domain_id <ID> | --protection_domain_name <NAME> )
For example:
scli --query_sds_connectivity_status --protection_domain_name pd_18
Verify that the new SDR IP addresses are being used, using the command:
For example:
scli --query_all_sdr
Example output:
Query-all-SDR returned 3 SDR nodes.
Protection Domain ID: a0e7ba3500000000
SDR ID: 24fc609400000000 Name: sdr49 State: Connected, Joined IP: 192.168.73.4,192.168.73.24 Port: 11088 Version: 3.5.0
SDR ID: 24fc609500000001 Name: sdr50 State: Connected, Joined IP: 192.168.73.5 Port: 11088 Version: 3.5.0
SDR ID: 24fc609600000002 Name: sdr51 State: Connected, Joined IP: 192.168.73.6 Port: 11088 Version: 3.5.0
Verify that the SDCs are using the new SDS IP addresses by running the following command on each SDC:
If required, remove the old IP addresses from the SDSs, using the command:
scli --remove_sds_ip (--sds_id <ID> | --sds_name <NAME> | --sds_ip <IP_ADDRESS> [--sds_port <PORT> ]) --sds_ip_to_remove <IP_ADDRESS>
For example:
scli --mdm_ip 192.168.73.7 --remove_sds_ip
--sds_ip 192.168.73.24 --sds_ip_to_remove 192.168.73.4
If required, remove the old IP addresses from each SDR, using the command:
scli --remove_sdr_ip (--sdr_id <ID> | --sdr_name <NAME> | --sdr_ip <IP_ADDRESS> [--sdr_port <PORT> ]) --sdr_ip_to_remove <IP_ADDRESS>
For example:
scli --mdm_ip 192.168.73.7 --remove_sdr_ip
--sdr_ip 192.168.73.24 --sdr_ip_to_remove 192.168.73.4
Next steps
After you have added a new IP network to the system, you can use this procedure to remove the old IP network, if it is no longer used. A typical scenario is moving systems from IPv4 networks to IPv6 based networks.
In the relevant MDM steps, the old MDM IP addresses need to be omitted during the removal process.
In the relevant SDC steps, after the old MDM virtual IP addresses are no longer in use, remove them from the
esxcli system module parameters set -m scini -p command in the
IoctlMdmIPStr=<IP_ADDRESSES> section.
For the SDSs, use the
scli --remove_sds_ip command to remove the old IP addresses.