Configure the isolated recovery environment (IRE) network on each node in the Air Gap Protect vault.
Configure network interfaces
The IRE network must allow communication between the Air Gap Protect vault nodes and the recovery destination.
-
Connect to the node using the IPMI console.
-
Launch the HyperScale X network configuration tool:
./cvhsx_launch_nwconfig.sh -
Create a data protection network.
While configuring the data protection network:
-
Use the VLAN dedicated to the IRE.
-
Select the network interface that is configured for the IRE.
The replication network supports single interfaces, bonded interfaces, and VLAN-tagged interfaces.
-
-
Verify that the VMware ESXi server is configured on the same IRE VLAN as the Air Gap Protect vault nodes.
-
Verify that the ESXi server is added to vSphere.
-
Apply the changes and exit.
Update firewall and services
Update the node configuration so that Air Gap Protect does not manage the IRE network interface.
-
Reconfigure the firewall to add the replication interface to the block zone.
-
Stop Commvault services:
commvault stop -
Edit the HyperScale X network configuration file:
/etc/CommVaultRegistry/Galaxy/Instance001/MediaAgent/.hyperscalenw.cfg -
Remove the newly added
dataProtectionnetwork.The IRE network must not be included in the configuration used by Air Gap Protect. Air Gap Protect automatically disables ports for managed networks. Removing the IRE network prevents Air Gap Protect from interfering with cleanroom recovery and testing activities.
Before editing, the configuration might look similar to the following:
[network_types] bond2 = storagePool bond3 = commServeRegistration bond4 = dataProtectionAfter editing, the configuration should look similar to the following:
[network_types] bond2 = storagePool bond3 = commServeRegistrationNote
Interface names vary by environment. Use the interface that is configured for the IRE network.
-
Restart networking and Commvault services:
systemctl restart network commvault start