Deploying Linux CommServe Bare Metal With Bonding (Active-Backup or LACP)

You can deploy a Linux CommServe Bare Metal node 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.

Before You Begin

Verify the requirements needed for setting up the Bonded Topology in your environment.

Procedure

1. Log on to the node using the system console as described in Setting up the installation media. (Do not use PuTTy / SSH to setup the nodes.)

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

   # hssetup
   

   The CommServe Installer page appears.

   

3. Click Start.

   The Network Configuration page appears.

   

4. Create a data protection interface bond as follows:

   1. Click Create bond.

      The Create bond dialog box appears.

   2. From the Interfaces list, select the data protection interfaces. (enpsf3 or enpsf5)

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

   4. Click CREATE.

      The bond1 interface appears in the Network Configuration page.

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

   

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

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

      If the IP address of the interface belongs to the same subnet as the specified gateway, then the Has Default Gateway check box is automatically selected.

   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.

6. Click NEXT

   The software validates the network and will take a few minutes to complete.

   The Network Configuration Summary dialog box appears.

   

7. Verify the network configuration and then click PROCEED.

8. To install a primary CommServer, in the Setup Type dialog box, select Primary CommServe.

   

   To install a standby CommServe, select Standby CommServe.

9. Click NEXT.

   The Server Details dialog box appears.

   

10. Add the following information:

    1. In the CommServe FQDN box, type type the fully qualified domain name of the CommServe node.

    2. In the Root password and Confirm password boxes, type a secure password for the node.

       Tip

       Hover the cursor over the Root password box to view the password requirements.

       If you are installing a Standby CommServe, enter the domain name and root password credentials for the primary CommServe.

       

    3. From the Time zone list, select the time zone in which the node is located.

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

    5. Click NEXT.

       Note

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

    The CommServe Details page appears.

    

    A default username admin is created to log on to the Command Center.

11. Add the following information:

    1. In the Admin user email box, enter the email address for the admin user.

    2. In the Admin user password and Confirm Admin user password boxes, enter the credentials for the admin user.

    3. Click NEXT.

    The software validates the information and will start the installation process. This process may take some time (approximately 30 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.

    

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