Changing the IP Address For HyperScale MediaAgent Nodes

IP addresses associated with HyperScale nodes can be changed.

Note

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

Procedure

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

For more information, see Controlling Activities.
Suspend all running jobs to and from the MediaAgents associated with the nodes.

For more information, see Controlling Jobs.
Set the MediaAgents associated with the nodes in the Maintenance mode.

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

Start the hv_deploy mode using the following commands:

# su - admin
# export HV_PUBKEY=1
# hv_deploy

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

# login_to_cluster <cluster name>

For example:

# login_to_cluster HV13102021054000

When prompted, type the root password.

Stop the cluster.
```
# stop_cluster
    
```
Exit the the hv_deploy mode.
```
# exit
    
```
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
Change the DNS entries on the nodes to reflect the new IP address of the Data Protection network and/or the Storage Pool network as follows:
1. Login to a node using the root credentials.
2. Edit the following file to change the IP address associated with the Data Protection network:
```
/etc/sysconfig/network-scripts/ifcfg-bond1
    
```
  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"
    
```
3. Edit the following file to change the IP address associated with the Storage Pool network:
```
/etc/sysconfig/network-scripts/ifcfg-bond2
    
```
  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"
    
```
4. Update the /etc/hosts on all hyperscale nodes with the new 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
    
```
  5. Repeat these steps on the other nodes.
Reboot the nodes.
Verify that the new IP addresses are reachable from all nodes, using ping or any other DNS command / tool.
Verify that the disk library NFS mount path is mounted automatically using the following command:
```
# df -kh /ws/hedvig/*
    
```
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
Remove the MediaAgents associated with the nodes from the Maintenance mode.

For more information, see Setting the MediaAgent on Maintenance Mode.
Enable all activities and schedules on the MediaAgents associated with the nodes.

For more information, see Controlling Activities.
Verify the network connections between the MediaAgents and CommCell entities, by running a Check Readiness operation.

For more information, see Checking Readiness.
Run a test backup to ensure that the configuration is successful and the storage pool is functional.