# Setting up the HyperScale 1.5 Appliance with Tagged vLAN Link for the 10G Data Protection Network and a 10G Storage Pool Network

The HyperScale 1.5 Appliance can be setup using 4 10GigE ports per node as follows:

- 2 ports for Data Protection

  - 2 or more vLANs per Data Protection port

  - 2 or more IP addresses per Data Protection port

- 2 bonded ports for internal Storage Pool

Note

Configuring a bonded port with multiple tagged VLAN's for data protection is not supported.

The number of IP addresses required for this setup depends on the number of vLANs. For example, if you have 2 vLANs (For example, 96 and 100) then you will require 4 IP addresses per node, as follows:

- 1 for the Storage Pool network

- 1 for CommServe Registration

- 2 for the vLAN, which will be used for Data Protection network. (If you have additional vLANs, you will need additional IP addresses for each additional vLAN.)

Note

Interfaces with tagged vLAN ID cannot be used as Management Network or CommServe Registration network. In cases where an interface with a tagged vLAN ID needs to be used either as Management network or Commserve Registration network, then configure the underlying network port as access port with a default vLAN ID on the switch. (Currently, Redhat virtualization Manager does not support creating virtual networks over tagged vLANs and hence this limitation.) For example:

- If a tagged vLAN (like eno2.20) needs to be used for Management network, then configure the switch port corresponding to eno2 as access port with the default vLAN ID as 20.

- Similarly, if a tagged vLAN (like eno3.100) needs to be used for CommServe Registration network, then configure the switch port corresponding to eno3 as access port with the default vLAN ID as 100.

Note

The Commvault HyperScale wizard uses DHCP to automatically detect and setup the nodes and the CommServe.

## Before You Begin

- Use the data collected in the Pre-Installation Checklist to setup the nodes.

- Using `ping` or any other DNS command / tool, ensure that the DNS entries are available for the CommServe, Control Host and each of the MediaAgent nodes.

  Ensure that both the forward and reverse lookups are available for these entities.

- Power on the nodes.

  The node will automatically boot to Red Hat Enterprise Linux Server.

  Important

  Power on 3 nodes at a time.

- Run the `ifconfig` command from each node and note down the IP address and the corresponding network interfaces.

  Click here to view a sample output of the command.

- Run the `ethtool` on each of the specific interfaces to verify that they correspond to the 10 GB network interface.

  Click here to view a sample output of the command.

- Make sure that the firewall ports are enabled between the data protection and iRMC management networks. Mainly the nodes should be able to communicate with the iRMC ports. The setup will fail if there is a communication failure between these ports. For information about ports required by iRMC, see Firewall Port Requirements.

- If you plan to attach the nodes to an existing CommServe, make sure that you are logged in as an user with necessary permissions on the CommServe to install the software. For more information about the permissions needed to setup the node as a client in the CommServe, see User Security Permissions by Feature - Deployment. (If necessary, the deployment permission can be removed for the user after the installation, as this permission check is performed only when the nodes are registered in the CommServe.)

## Procedure

1. Open a Web browser from any computer that can connect to the nodes.

2. Type the IP address associated with any one of the nodes.

   The Commvault HyperScale wizard is displayed.

3. Type root as the Username and cvadmin as the Password.

   The Provide Node Information page is displayed.

4. Add the Root password / Confirm password for the node(s).

   Optional: Click the Use different root password for each node toggle key to setup unique passwords for each node.

5. Click and enable the Advanced Settings toggle key.

   The Node 1, Node 2 and Node 3 tabs will be displayed. The serial numbers associated with each node is also displayed.

   All the network interfaces in the hardware is displayed. (Typically, for the standard hardware, a total of 6 interfaces, which includes 4 - 10 GigE interfaces, and 2 - 1 GigE interfaces, are displayed for each node.)

   Tip

   Hover the cursor over the check box associated with the interface to display the network capacity and other information associated with the interface.

6. Set the Data Protection interface, with the tagged vLAN IDs using the following steps:

   1. Select the check box associated with a 10 GigE interface.

   2. Verify and validate the IP Address and Netmask addresses associated with the interface using the data collected in the Pre-Installation Checklist.

      If necessary, edit the information to make sure that the correct IP addresses are provided.

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

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

   4. Click the Create VLANS button to set the vLAN ID for Data Protection.

      The VLANs ID pop-up will be displayed.

   5. Type the VLAN ID that must be used for the interface.

   6. Optional: Click the Add More button to add multiple VLAN IDs for the interface.

   7. Click Enter, when you are done.

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

   8. Select check box associated with the vLAN interface. (For example, eno3.100.)

   9. Verify and validate the IP Address and Netmask addresses associated with the interface using the data collected in the Pre-Installation Checklist.

      If necessary, edit the information to make sure that the correct IP addresses are provided.

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

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

   11. Clear the check box associated with the vLAN Data Protection interface.

   12. Repeat the above 3 steps to configure the other vLAN interfaces, if multiple VLAN interfaces were added.

7. Make sure to clear the check box associated with the vLAN interface(s), if it is selected.

8. Set the Storage Pool interface using the following steps:

   1. Select the check box associated with a 10 GigE interface.

   2. Verify and validate the IP Address and Netmask addresses using the data collected in the Pre-Installation Checklist.

      If necessary, edit the information to make sure that the IP addresses are provided.

   3. From the Network Type list, select StoragePool.

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

9. Clear the check box associated with the Storage Pool interface.

10. Repeat the process of defining the interfaces (starting from step 6 to step 9) on the other nodes.

11. Click Next.

    The Provide Network Information page is displayed.

12. The IP addresses associated with the Default Gateway, Netmask, DNS Servers, and Cluster Netmask is displayed.

    Verify and validate the information using the data collected in the Pre-Installation Checklist.

    If necessary, edit the information to make sure that the correct network related information is provided.

    Note

    DNS 1 and DNS 2 are mandatory. The setup will fail if only one DNS Server is available. If you have additional DNS Servers, click the Add DNS link to add additional DNS servers.

13. Click Next.

    This process may take some time to complete.

    The CommServe Information page is displayed.

14. Choose one of the following CommServe setup options:

    Attach the nodes to an Existing CommServe (Default)

    Note

    If the CommServe is located behind a firewall, you must perform additional steps to connect to the CommServe. For more information, see Connecting To a CommServe Behind a Firewall During Setup.

    1. In the CommServe Host Name (FQDN) box, enter a fully qualified domain name for the CommServe computer.

    2. In the Username box, enter the user name that must be used to access the CommServe server.

    3. In the Password box, enter the password associated with Username.

    Setup a Primary CommServe in the nodes

    1. Enable the Deploy Primary CommServe option.

       The CommServe Information page will display the following options:

    2. In the CommServe HostName (FQDN) box, enter a fully qualified host name for the primary CommServe computer.

    3. In the Password / Confirm Password boxes, enter a password for the CommServe server.

       Note

       This is the 'Admin' password which must be used later to login to the CommServe computer and to access the Command Center and the Control Host.

    4. In the Windows Product Key box, enter the Windows product key provided in the package.

       Note

       Make sure to accurately type the Windows Product Key. If the key is typed with incorrect number of characters, the interface will be stuck. To overcome the issue, refresh the web browser and re-start the installation.

    5. In the Control Host Hostname (FQDN) box, enter a fully qualified host name for the control node.

    Setup a Standby Disaster Recovery (DR) CommServe in the nodes

    1. Enable the Deploy Standby CommServe option.

       The CommServe Information page will display the following options:

    2. In the CommServe HostName (FQDN) box, enter a fully qualified host name for the standby CommServe computer.

    3. In the Password / Confirm Password boxes, enter a password for the standby CommServe server.

    4. In the Windows Product Key box, enter the Windows product key provided in the package.

       Note

       Make sure to accurately type the Windows Product Key. If the key is typed with incorrect number of characters, the interface will be stuck. To overcome the issue, refresh the web browser and re-start the installation.

    5. In the Control Host Hostname (FQDN) box, enter a fully qualified host name for the control node.

    6. In the Primary CommServe HostName (FQDN) box, enter a fully qualified host name associated with the primary CommServe computer.

    7. In the Username box, enter the user name that must be used to access the CommServe server.

    8. In the Password box, enter the password associated with Username.

15. Click Save.

    The software will start the installation process.

    If you are setting up a Primary or standby CommServe, a virtual machine is setup as the CommServe host. 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.

    Tip

    In the course of the installation, the IP address used in the Web browser to access the Commvault HyperScale wizard will switch to the static IP address associated with one of the nodes. If you have to restart the setup, use the FQDN associated with that node to re-launch the wizard in the Web browser.

    This completes the setup.

## What to Do Next

- Launch the Command Center as described in Opening the Command Center.

- Launch the Virtualization Manager and set the value of Total Virtual CPUs to 16 for the HE (Hosted Engine) VM. For more information, see HE Migration Error.

- If you have attached the nodes to an existing CommServe, make sure that you have the necessary permissions to configure and manage the HyperScale Storage pools. For more information about HyperScale permissions , see User Security Permissions by Feature - HyperScale.

## Additional Notes

- Snapshots or VSA backups of HyperScale Appliance hosted Commserve VM within RHV is not supported. Do not setup snapshot or VSA backups of the Commserve VM as this can render the Commserve unrecoverable. Setup Disaster Recovery backups and/or CommServe LiveSync operation to protect and recover the CommServe.

- When you setup the standby DR (Disaster Recovery) CommServe host on the nodes, the nodes must be setup as a new storage pool . The nodes cannot be added as additional nodes to an existing Storage Pool. For more information on configuring a new HyperScale storage pool, see Configuring a Scale-Out Storage Pool.

×

Loading...