Loading...

Changing IP Addresses for the Storage Pool (Private) Network

IP addresses associated with the Storage Pool (Private) network can be changed.

Before You Begin

  • The following procedure can be used to address network changes that demand IP address changes.

    Note: The following procedure cannot be used to change IP address resulting from moving a Data Center.

  • Update the DNS to reflect the new IP address of the Storage Pool network.
  • Using the CommCell Console, set the Disk libraries associated with the nodes in the Maintenance mode.
  • Set the MediaAgents associated with the nodes in the Maintenance mode. For more information on setting the MediaAgents in the Maintenance mode, see Setting the MediaAgent on Maintenance Mode.
  • Verify and ensure that the gluster uses hostnames for resolution and does not use the IP addresses directly. Use the following command to verify gluster hostnames:

    gluster peer status

    The above command should list the hostnames associated with the nodes. (IP addresses should not be displayed.)

Procedure

  1. Stop the gluster volumes using the following command:

    gluster volume stop <volume_name>

  2. Update the relevant network configuration file for the private network interface with the new IP address, bonded and non-bonded, as follows:
    1. Navigate to the following folder:

      /etc/sysconfig/network-scripts

    2. Modify the following file:

      ifcfg-<Interface name>n

    3. Update /etc/hosts.
  3. Restart the network service to reflect the new IP using the following command:

    systemctl restart network

  4. Restart the volume using the following command:

    gluster volume start <volume name>

Changing the IP Address of the Data Protection (Public) Network

  1. Update the relevant network configuration file for the public network interface with the new IP address - bonded and non-bonded as follows:
    1. Navigate to the following folder:

      /etc/sysconfig/network-scripts

    2. Modify the following file:

      ifcfg-<Interface name>n

What to Do Next

  • Remove the Disk libraries and MediaAgents from the Maintenance mode.
  • Run the Recovery Readiness Report and verify that the HyperScale nodes are available. For more information on running this report, see Recovery Readiness Report.

Last modified: 12/20/2018 9:19:41 PM