> Software > Storage for Backups > HyperScale X > Maintenance > Changing the IP Address For HyperScale Nodes

Changing the IP Address For HyperScale MediaAgent Nodes With the CommServe VM

IP addresses associated with HyperScale nodes, CommServe VM, and CommServe can be changed.

Note

Hostnames associated with the nodes, CommServe VM and CommServe cannot be changed and must remain the same.

Before You Begin

Important: Perform a DR Backup and make sure that you have the latest version of the DR backup in an accessible location. For more information, see Performing a DR Backup.

Procedure

  1. Disable all activities and schedules on the MediaAgents associated with the nodes.

    For more information, see Controlling Activities.

  2. Suspend all running jobs to and from the MediaAgents associated with the nodes.

    For more information, see Controlling Jobs.

  3. Set the MediaAgents associated with the nodes in the Maintenance mode.

    For more information, see Setting the MediaAgent on Maintenance Mode.

  4. Start the hv_deploy mode using the following commands:

    # su - admin
# export HV_PUBKEY=1
# hv_deploy

  5. Display the cluster name and note down the name.

    # show_all_clusters

    This will display the cluster name, as shown in the following sample output:

     
    Cluster name: HV13102021054000 - owner: unowned - version: v-4.5.0.0.2.3597.00320e0ba9:06aca75bc4db06170a13ef14cbfe8446

  6. Login to the cluster.

    # login_to_cluster cluster name

    For example:

     
    # login_to_cluster HV13102021054000

    When prompted, type the root password.

  7. Stop the cluster.

    # stop_cluster

  8. Exit the the hv_deploy mode.

    # exit

  9. Stop the Commvault services on the nodes using the following command:

    # commvault -all stop

    For more information, see Commands to Control Services on UNIX Clients

  10. Verify, and if necessary turn off firewall in the CommServe VM from the Windows Control Panel \ System and Security.

  11. Change network profile to Private for the Windows network interface using the following commands from Windows PowerShell:

    • Get the connection profile, use the following command:

      C:\Users\Administrator> Get-NetConnectionProfile

      The NetworkCategory: option in the output will display whether the network is Public or Private.

    • If NetworkCategory: is Public, then set the profile as Private using the following command:

      Set-NetConnectionProfile - Name Network_name -NetworkCategory Private

      Replace <network_name> with the name of the network.

  12. Change the IP address of the CommServe VM to reflect the new IP address, from the Windows Control Panel\Network and Internet\Network Connections.

    DNS update is not required at this point.

  13. Shut down the CommServe VM from the HyperScale node .

    For more information, see Starting and Stopping the CommServe VM.

  14. Change the DNS entries on the nodes to reflect the new IP address of the CommServe, Data Protection network and/or the Storage Pool network as follows:

    1. Login to a node hosting the CommServe VM, using the root credentials.

      Use the following command to verify whether the node is hosting the CommServe VM:

      virsh list --all

      For more information, see Starting and Stopping the CommServe VM.

    2. Edit the bridge network file (ifcfg-br0), to change the IP address associated with the CommServe VM:

      /etc/sysconfig/network-scripts/ifcfg-br0

      Replace the value for IPADDR with the new IP address for the CommServe VM. For example, the entries in this file should be similar to the following:

      DEVICE=br0
TYPE=Bridge
BOOTPROTO=none
ONBOOT=yes
USERCTL=no
NM_CONTROLLED=no
IPADDR=XXX.XXX.XXX.XXX
NETMASK=
GATEWAY=
DNS1=
DNS2=

    3. Edit the following file to change the IP address associated with the Data Protection network:

      /etc/sysconfig/network-scripts/ifcfg-enpsf3

      Replace the value for IPADDR with the new IP address for Data Protection network. For example, the entries in this file should be similar to the following:

      DEVICE=bond1
BOOTPROTO=none
IPADDR=XXX.XXX.XXX.XXX
NETMASK=XXX.XXX.XXX.XXX
GATEWAY=XXX.XXX.XXX.XXX
ONBOOT=yes
USERCTL=no
NM_CONTROLLED=no
IPV6INIT=no
DNS1=
DNS2=
TYPE=Bond
BONDING_MASTER=yes
BONDING_OPTS="fail_over_mac=active miimon=100 mode=activebackup"

    4. Edit the following file to change the IP address associated with the Storage Pool network:

      /etc/sysconfig/network-scripts/ifcfg-enpsf4

      Replace the value for IPADDR with the new IP address for Storage Pool network. For example, the entries in this file should be similar to the following:

      DEVICE=bond2
BOOTPROTO=none
IPADDR=XXX.XXX.XXX.XXX
NETMASK=XXX.XXX.XXX.XXX
ONBOOT=yes
USERCTL=no
NM_CONTROLLED=no
IPV6INIT=no
TYPE=Bond
BONDING_MASTER=yes
BONDING_OPTS="fail_over_mac=active miimon=100 mode=activebackup"

    5. Update the /etc/hosts on all hyperscale nodes with the new Storage Pool IP address of all the nodes.

      For example:

      XXX.XXX.XXX.XXX MyMA1.company.com MyMA1
XXX.XXX.XXX.XXX MyMA2.company.com MyMA2
XXX.XXX.XXX.XXX MyMA3.company.com MyMA3

  15. Login to the other nodes and change the IP address of the Data Protection and/or the Storage Pool network. (Steps 9c to 9f above.)

  16. Reboot the nodes.

  17. Verify that the new IP addresses are reachable from all nodes, using ping or any other DNS command / tool.

  18. Login to a node hosting the CommServe VM, and perform the following steps:

    1. Stop the CommServe VM, using the following command:

       
      virsh shutdown virtual_machine

      For more information, see Starting and Stopping the CommServe VM.

    2. Stop the libvrtd deamon using the following command:

      systemctl stop libvirtd

      Note

      Wait for a few minutes, 5-7 minutes approximately, for the deamon to stop.

    3. Start the libvrtd deamon using the following command:

      systemctl start libvirtd

    4. Start the CommServe VM, using the following command:

       
      virsh start virtual_machine

      For more information, see Starting and Stopping the CommServe VM.

    5. Verify the CommServe is reachable with the new IP address, using ping or any other DNS command / tool.

      Make sure that you are able to access the CommServe VM using the Remote Desktop Connection (RDP) session.

  19. Verify that the disk library NFS mount path is automatically mounted on the nodes using the following command: 

    # df -kh /ws/hedvig/*

  20. Verify that the Commvault services are running on the nodes using the following command:

    # commvault -all list

    For more information, see Viewing Services - Viewing Services on UNIX

  21. Remove the MediaAgents associated with the nodes from the Maintenance mode.

    For more information, see Setting the MediaAgent on Maintenance Mode.

  22. Enable all activities and schedules on the MediaAgents associated with the nodes.

    For more information, see Controlling Activities.

  23. Verify the network connections between the MediaAgents and CommCell entities, by running a Check Readiness operation.

    For more information, see Checking Readiness.

  24. Run a test backup to ensure that the configuration is successful and the storage pool is functional.

Page contents

×

Loading...