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

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

Note

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

Before You Begin

Perform a Disaster Recovery (DR) Backup and verify that the latest version is stored in an accessible location. For more information, see Performing a DR Backup.

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.

For more information, see Controlling Jobs.
Set the MediaAgents to the Maintenance mode.

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

Start hv_deploy mode:

# su - admin
# export HV_PUBKEY=1
# hv_deploy

Display the cluster name and record it.

# show_all_clusters

Cluster name appears.

Example:

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

# login_to_cluster cluster name

Example:

# login_to_cluster HV13102021054000

When prompted, enter the root password.

Stop the cluster:
```
# stop_cluster
```
Exit hv_deploy mode:
```
# exit
```
Stop the Commvault services on the nodes:
```
# commvault -all stop
```
For more information, see Commands to Control Services on UNIX Clients
On the CommServe VM, verify the firewall status. If necessary, disable it from Windows Control Panel \ System and Security.
Change the network profile of the CommServe VM to Private using Windows PowerShell:
- To view the current profile:
```
C:\Users\Administrator> Get-NetConnectionProfile
```
  The NetworkCategory field indicates whether the profile is Public or Private.
- If the profile is Public, change it to Private:
```
Set-NetConnectionProfile - Name Network_name -NetworkCategory Private
```
  Replace <network_name> with the name of the network.
Update the CommServe VM IP address from Windows Control Panel\Network and Internet\Network Connections.

Do not update DNS at this stage.
Shut down the CommServe VM from the HyperScale node.

For more information, see Starting and Stopping the CommServe VM.
Update DNS entries on the nodes to reflect the new IP addresses for the CommServe, Data Protection, and/or storage pool networks:
1. Log in to the node hosting the CommServe VM with root credentials.
  
  Verify whether the node is hosting the CommServe VM or not:
```
virsh list --all
```
  For more information, see Starting and Stopping the CommServe VM.
2. Edit the bridge network file (ifcfg-br0) to update the IP address associated with the CommServe VM:
```
/etc/sysconfig/network-scripts/ifcfg-br0
```
  Replace the value for IPADDR with the new IP address of the CommServe VM.
  Example:
```
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 update the IP address for the Data Protection network:
```
/etc/sysconfig/network-scripts/ifcfg-enpsf3
```
  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"
```
4. Edit the following file to update the IP address for the storage pool network:
```
/etc/sysconfig/network-scripts/ifcfg-enpsf4
```
  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"
```
5. Update the /etc/hosts file on all HyperScale nodes with the new Storage Pool 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
```
Log in to the other nodes and change the IP address of the Data Protection and/or the storage pool network. (Steps 14c to 14e above.)
Reboot the nodes.
Verify that the new IP addresses are reachable from all nodes using ping or any DNS command / tool.
On the node hosting the CommServe VM:
1. Shut down the CommServe VM:
```
 
virsh shutdown virtual_machine
```
  For more information, see Starting and Stopping the CommServe VM.
2. Stop the libvrtd daemon:
```
systemctl stop libvirtd
```
  Note
  
  Allow approximately 5–7 minutes for the daemon to stop.
3. Start the libvrtd daemon:
```
systemctl start libvirtd
```
4. Start the CommServe VM:
```
 
virsh start virtual_machine
```
  For more information, see Starting and Stopping the CommServe VM.
5. Verify that the CommServe is reachable using its new IP address with ping or any other DNS command / tool.
  
  Confirm that you can access the CommServe VM using a Remote Desktop Connection (RDP).
Verify that the disk library NFS mount path is mounted automatically:
```
# df -kh /ws/hedvig/*
```
Verify that Commvault services are running:
```
# commvault -all list
```
For more information, see Viewing Services - Viewing Services on UNIX
Remove the MediaAgents from Maintenance mode.

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

For more information, see Controlling Activities.
Run a Check Readiness operation to verify network connections between the MediaAgents and CommCell entities.

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

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

Before You Begin

Procedure

Page contents