Changing IP Addresses for the Data Protection (Public) Network

IP addresses associated with the Data Protection (Public) network of CommServe, Hosted Engine and MediaAgent nodes, can be changed.

Before You Begin

• Set the MediaAgent nodes in the Maintenance mode. For more information on setting a MediaAgent in the Maintenance mode, see Setting the MediaAgent on Maintenance Mode.

• Backup the CommServe databases by performing a Disaster Recovery backup.

• Perform a backup of the Hosted Engine, using the following command:

  engine-backup --mode=backup --scope=all --file=engine_backup.dat --log=engine_backup.log

  Note

  The above command is applicable for RHEV Version 4.1.

• Update the DNS to reflect the new IP address of the Data Protection network.

• 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

Changing the IP Address of the MediaAgent Nodes

1. Login to one of the MediaAgent nodes and set the hosted engine in the maintenance mode using the following command:

   hosted-engine --set-maintenance --mode=global

2. Verify that the gluster is in maintenance mode using the following command:

   hosted-engine --vm-status
   

3. Using the Virtualization Manager, perform the following task for each node:

   1. Locate the control node and migrate it to another node as follows:

      System -> Virtual Machines -> HostedEngine and cvhcics -> Migrate -> <one of the other nodes>

   2. Set the node (for which IP is being changed) to Maintenance as follows:

      System -> Hosts -> <current host> -> Management -> Maintenance

   3. Run the following vdsm-client command:

      Bonded Interface

      echo '{"networks": {"ovirtmgmt": {"bonding": "bond0", "bridged": true, "ipaddr": "New IP", "netmask": "Netmask", "gateway": "gateway", "defaultRoute": true}}, "bondings": {}, "options": {"connectivityCheck": false}}' | vdsm-client -f - Host setupNetworks

      vdsm-client Host setSafeNetworkConfig
      

      Unbound Interface

      echo '{"networks": {"ovirtmgmt": {"nic": "eno3", "bridged": true, "ipaddr": "New IP", "netmask": "Netmask", "gateway": "gateway", "defaultRoute": true}}, "bondings": {}, "options": {"connectivityCheck": false}}' | vdsm-client -f - Host setupNetworks

      vdsm-client Host setSafeNetworkConfig
      

   4. If control node web console is inaccessible, check for VM status using the following command:

      hosted-engine --vm-status
      

      If the hosted engine is not running, start it on the node where it was migrated to using the following command:

      hosted-engine --vm-start
      

   5. Update the console with the new IP for the node as follows:

      System -> Hosts -> <current node> -> Network Interfaces -> set up host networks -> ovirtmgmt

   6. Activate the node as follows:

      System -> Hosts -> <current node> -> Management -> Activate

      System -> Hosts -> <current node> -> Management -> Confirm node has been rebooted

4. Login to one of the MediaAgent nodes and remove the hosted engine from the maintenance mode using the following command:

   hosted-engine --set-maintenance --mode=none

5. Verify that the gluster to make sure that it is not in the maintenance mode using the following command:

   hosted-engine --vm-status
   

Changing the IP Address of the CommServe

1. Change the IP address of the CommServe computer.

   For more information, see https://support.microsoft.com/en-us/help/15089/windows-change-tcp-ip-settings

Changing the IP Address of the Hosted Engine

1. Change the IP in the following network configuration file:

   /etc/sysconfig/network-scripts/ifcfg-eth0

2. Restart network using the following command:

   systemctl restart network
   

What to Do Next

• Remove the MediaAgents from Maintenance mode. For more information on removing a MediaAgent in the Maintenance mode, see Setting the MediaAgent on 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.