# Changing the IP Address for HyperScale MediaAgent Nodes

IP addresses associated with HyperScale nodes can be updated.

Note

Hostnames for the nodes cannot be changed and must remain the same.

## 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 to Maintenance mode.

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

4. Start hv_deploy mode:

       # su - admin
       # export HV_PUBKEY=$[1]
       # hv_deploy

5. Display the cluster name and record it:

       # show_all_clusters

   Cluster name appears as shown in the following sample output:

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

6. Log in to the cluster:

       # login_to_cluster $[cluster name]

   Example:

        # login_to_cluster $[HV13102021054000]

   When prompted, type the `root` password.

7. Stop the cluster:

       # stop_cluster

8. Exit the hv_deploy mode.

       # exit

9. Stop the Commvault services on the nodes:

       # commvault -all stop

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

10. Update the DNS entries on the nodes to use the new IP addresses for the Data Protection network and/or the storage pool network:

    1. Log in to a node using root credentials.

    2. Edit the following file to update the Data Protection network IP address:

           /etc/sysconfig/network-scripts/ifcfg-bond1

       Replace the value for IPADDR with the new IP address for Data Protection network.

       Example:

           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]"

    3. Edit the following file to update the storage pool network IP address:

           /etc/sysconfig/network-scripts/ifcfg-bond2

       Replace the value for IPADDR with the new IP address for storage pool network.

       Example:

           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]"

    4. Update the `/etc/hosts` file on all HyperScale nodes with the new IP addresses.

       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]

       5. Repeat these steps on all other nodes.

11. Reboot the nodes.

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

13. Confirm that the disk library NFS mount path is mounted automatically:

        # df -kh $[/ws/hedvig/*]

14. Verify that Commvault services are running:

        # commvault -all list

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

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

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

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

    For more information, see Controlling Activities.

17. Verify the network connections between the MediaAgents and CommCell entities by running the Check Readiness operation.

    For more information, see Checking Readiness.

18. Run a test backup to confirm that the configuration is successful and the storage pool is functional.

×

Loading...