# Deploying Commvault Flex Open With Tagged vLAN and Bonding (Active-Backup or LACP)

Commvault Flex Open nodes can be deployed in environments with tagged virtual LANs (VLANs) with bonding.

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.com` | No
    Backup Gateway (default port) | `test.eastus2.cloudapp.azure.com` | Yes
    Backup Gateway (non-default port) | `test.eastus2.cloudapp.azure.com:443` | Yes

  - The credentials of an administrative user.

  - Confirmation that TCP ports 8400 and 443 are open between the nodes and the CommServe server.

- Verify that the hardware supports a Linux 9.7 distribution.

- Verify the requirements needed to setup the Bonded vLAN Topology in your environment.

Tip

Keep the network names and IP addresses listed in the Network Requirements section of Bonded vLAN Topology handy before you start the configuration.

## Procedure

1. 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.)

2. Launch the network configuration interface using the following command:

       # hssetup

   The Commvault Flex Open Installer page appears.

3. Click Start.

   The Network Configuration page appears.

4. Configure the routable data protection VLAN interface (bonded) as follows:

   1. Click Create bond.

      The Create bond dialog box appears.

      1. From the Interfaces list, select the 2 interfaces that will form the data protection bond. (For example, enpsf3 and enpsf5)

         Tip

         Hover the cursor over the interfaces to display the speed and MAC address of the physical interface.

      2. From Bonding mode list, select either active-backup (Mode 1) or LACP (Mode 4).

         Note

         The same bonding mode must be used for both the data protection and storage pool interfaces.

      3. Click CREATE.

      The bond1 interface appears in the Network Configuration page.

   2. Click Create VLAN.

      The Create VLAN dialog box appears.

      1. From the Interface list, click bond1.

      2. In the VLAN ID box, enter the VLAN ID associated with the routable VLAN network and then click CREATE.

      The bond1 interface appears with the VLAN ID in the Network Configuration page. (The VLAN ID will be different, depending on the VLAN ID in your environment.)

   3. From the Network Type list, select CommServe Registration.

      Note

      This network will perform the same role as the data protection network and will also be used to register the node to the CommServe server.

   4. Add the IP Address and Netmask in the respective boxes.

      Once completed your screen should be similar to the one shown in the following image:

5. Configure additional data protection VLAN interfaces (bonded) as follows:

   (Repeat this step to add all the VLANs available in your environment.)

   1. Click Create VLAN.

      The Create VLAN dialog box appears.

      1. From the Interface list, click bond1.

      2. In the VLAN ID box, enter the VLAN ID associated with the additional data protection VLAN network.

      3. Click CREATE.

      The new bond1 interface appears with the VLAN ID in the Node and Network Configuration page.

   2. From the Network Type list, select Data Protection.

   3. Add the IP Address and Netmask in the respective boxes.

   4. Repeat this step to configure ALL the VLANs available in your environment.

      Once completed your screen should be similar to the one shown in the following image: (The number of VLANs may vary depending on the number of VLANs available in your environment.)

6. Configure the DNS server(s) as follows:

   1. In the Default Gateway box, add the IP address associated with the default gateway.

   2. 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.

   3. Click CONFIGURE.

   The software validates the network. (This may take a few minutes to complete.)

   The Network Configuration Summary page appears.

7. Verify the network configuration and then click CONTINUE.

   Verify the following information.

   - VLAN for the CommServe Registration interface is included.

   - IP address and Netmask for the VLAN is accurate.

     Note

     Hostname and serial number associated with the node is accurate.

     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.

8. Add the following information:

   1. 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.

   2. In the Password for Restricted shell user - cvbackupadmin and Confirm cvbckupadmin password boxes, type a secure password for the cvbackupadmin user.

   3. Click NEXT.

   The Node Details page appears.

9. Add the following information:

   1. From the Time zone list, select the time zone in which the nodes are located.

   2. Optional: In the NTP Server/Pool box, type the IP address of the NTP server or NTP pool if available.

   3. Click NEXT.

      Note

      The setup process configures the network for the nodes. This will take some time to complete.

10. 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

11. To connect to an exsiting CommServe, complete the following steps:

    1. Select Connect to existing CommServe and click NEXT.

       The CommServe Credentials page appears.

    2. Add the following information:

       1. 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.com` | No
          Backup Gateway (default port) | `test.eastus2.cloudapp.azure.com` | Yes
          Backup Gateway (non-default port) | `test.eastus2.cloudapp.azure.com:443` | Yes

          Note

          TCP Ports 8400 & 443 must be open from the nodes to the CommServe server for the registration to work.

       2. In the Auth-code box, enter the authorization code to connect to the CommServe server.

       3. Click NEXT.

12. To connect to an exsiting Commvault Cloud SaaS instance, on the Deployment Information page, complete the following steps:

    1. Select Connect to Commvault Cloud SaaS, and then click NEXT.

       The CommServe Credentials page appears.

    2. Add the following information:

       1. 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.

       2. In the Auth-code box, enter the authorization code to connect to the instance.

       3. 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.

13. 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.

×

Loading...