Commvault Flex Open node can be deployed with active backup or Link Aggregation Control Protocol (LACP) bonding mode.
With active backup, the interfaces are bonded for redundancy (or fault tolerance mode). Only one interface works at any moment and the other one will work when the first one fails.
When using LACP, each pair of ports should be configured as an active port-channel, and not configured to negotiate the aggregation protocol.
Note
When the deployment is complete, the password based root access is disabled and firewall and ransomware protection settings are enabled on the node automatically.
Before You Begin
-
If you plan to connect to an existing CommServe server, gather the following information before you begin:
-
The fully qualified domain name (FQDN) of the CommServe server based on the endpoint type used in your deployment.
Endpoint Type Example Applicable to SaaS Deployment CommServe FQDN Registration test.commvault.comNo Backup Gateway (default port) test.eastus2.cloudapp.azure.comYes Backup Gateway (non-default port) test.eastus2.cloudapp.azure.com:443Yes -
The credentials of an administrative user.
-
Confirmation that TCP ports 8400 and 443 are open between the nodes and the CommServe server.
-
-
Verify the requirements needed for setting up the Bonded Topology in your environment.
Tip
Keep the network names and IP addresses listed in the Network Requirements section of Bonded Topology handy before you start the configuration.
Procedure
-
Log on to the node as root user using the system console as described in Setting up a Static IP For IPMI. (Do not use PuTTy / SSH to setup the nodes.)
-
Launch the network configuration interface using the following command:
The Commvault Flex Open Installer page appears.# hssetup
-
Click Start.
The Network Configuration page appears.

-
Create a CommServe Registration interface bond as follows:
-
Click Create bond.
The Create bond dialog box appears.

-
From the Interfaces list, select the network interfaces that you want to configure.
-
From Bonding mode list, select either active-backup (Mode 1) or LACP (Mode 4).
-
Click CREATE.
The bond1 interface appears in the Network Configuration page.
-
From the Network Type list, select CommServe Registration
-
Add the IP Address and Netmask in the respective boxes.
-
Configure the DNS server(s) as follows:
-
In the Default Gateway box, add the IP address associated with the default gateway.
-
In the DNS Servers box, add the IP address associated with the DNS Server.
Click the ADD button to add additional DNS servers. A maximum of 3 DNS servers can be added.
Note
Multiple DNS servers are recommended.
Once completed your screen should be similar to the one shown in the following image:

-
-
Click CONFIGURE.
The software validates the network. (This may take a few minutes to complete.)
The Network Configuration Summary page appears.

-
-
Verify the network configuration and then click CONTINUE.
Verify the following information.
-
IP address and netmask for the CommServe Registration interface is accurate.
-
Hostname and serial number associated with the node is accurate.
Note
If you need to change the Hostname do so now. To change the hostname modify and correct the DNS records, (forward and reverse records) as discussed in Setting Up the DNS.
-
Default gateway and DNS servers are accurately configured.
Note
If an error is found, or if the hostname was changed, click CHANGE CONFIGURATION to go back and correct the values.
The Server Credentials page appears.

-
-
Add the following information:
-
In the Root password and Confirm password boxes, type a secure password for the nodes.
Tip
Hover the cursor over the Root password box to view the password requirements.
-
In the Password for Restricted shell user - cvbackupadmin and Confirm cvbckupadmin password boxes, type a secure password for the cvbackupadmin user.
-
Click NEXT.
The Node Details page appears.

-
-
Add the following information:
-
From the Time zone list, select the time zone in which the nodes are located.
-
Optional: In the NTP Server/Pool box, type the IP address of the NTP server or NTP pool if available.
-
Click NEXT.
Note
The setup process configures the network for the nodes. This will take some time to complete.
-
-
On the Warning popup that appears, read the information, and then click CONTINUE.
Note
If an error is found, hover your cursor over the status icon to view more information on the error. If a node is missing, exit the installer and confirm that all the nodes can ping each other on the storage pool network.
The Deployment Information page appears

-
To connect to an exsiting CommServe, complete the following steps:
-
Select Connect to existing CommServe and click NEXT.
The CommServe Credentials page appears.
-
Add the following information:
-
In the CommServeGateway Hostname box, enter the fully qualified domain name (FQDN) of the CommServe server based on the endpoint type used in your deployment.
Endpoint Type Example Applicable to SaaS Deployment CommServe FQDN Registration test.commvault.comNo Backup Gateway (default port) test.eastus2.cloudapp.azure.comYes Backup Gateway (non-default port) test.eastus2.cloudapp.azure.com:443Yes Note
TCP Ports 8400 & 443 must be open from the nodes to the CommServe server for the registration to work.
-
In the Auth-code box, enter the authorization code to connect to the CommServe server.
-
Click NEXT.
-

-
-
To connect to an exsiting Commvault Cloud SaaS instance, on the Deployment Information page, complete the following steps:
-
Select Connect to Commvault Cloud SaaS, and then click NEXT.
The CommServe Credentials page appears.
-
Add the following information:
-
In the Commvault Cloud SaaS proxy hostname box, enter a fully qualified host name of the SaaS instance that you are connecting to.
Note
TCP Ports 8400 & 443 must be open from the nodes to the CommServe server for the registration to work.
-
In the Auth-code box, enter the authorization code to connect to the instance.
-
Click NEXT.
-

The software validates the information and will start the installation process. This process may take some time (approximately 45 minutes) to complete. You can monitor the progress using the progress bar.
Caution
Do not reboot or stop the installation during this process.
Once the installation is completed, the Installation page appears.

-
-
Click CLOSE.
What to Do Next
Complete the additional configurations that may be required to customize your environment. For more information, see What to do Next.