Loading...

Enabling IPv6 Communication on Commvault HyperScale Appliance

IPv6 protocol can be enabled on Commvault HyperScale Appliance for data protection and other operations.

Procedure

Commvault HyperScale Appliance can be setup to communicate using the IPv6 protocol for data protection and other operations.

  1. Configure the IPv6 network interface by creating the /etc/sysconfig/network-scripts/ifcfg-* file.

    For example, to configure the IPv6 network interface for eno3, create the following file:

    /etc/sysconfig/network-scripts/ifcfg-eno3

    For additional information about configuring network interface on IPv6, see https://access.redhat.com/solutions/347693.

    • Contents of /etc/sysconfig/network-scripts/ifcfg-eno3:

      TYPE=Ethernet
      BOOTPROTO=none
      DEFROUTE=yes
      IPV4_FAILURE_FATAL=no
      IPV6INIT=yes
      IPV6_AUTOCONF=no
      IPV6_DEFROUTE=yes
      IPV6_FAILURE_FATAL=no
      NAME=eno3
      DEVICE=eno3
      ONBOOT=yes
      DNS1=127.0.0.1
      DNS2=127.0.0.1
      IPV6ADDR=XXXXX
      IPV6_DEFAULTGW=XXXXX
      IPV6_PRIVACY=no

      Substitute the values for the following parameters with appropriate values:

      NAME=
      DEVICE=

      DNS1=
      DNS2=

      IPV6ADDR=
      IPV6_DEFAULTGW=

    • Contents of /etc/sysconfig/network-scripts/ifcfg-eno3 with bonding on network interfaces:

      Data protection Network –Public Interface
      DEVICE=eno3
      NAME=eno3
      TYPE=Ethernet
      BOOTPROTO=none
      ONBOOT=yes
      MASTER=bond0
      SLAVE=yes
      ----------------------
      DEVICE=bond0
      NAME=bond0
      BONDING_OPTS="mode=active-backup"
      TYPE=Bond
      BONDING_MASTER=yes
      IPV6ADDR=XXXXX
      IPV6INIT=yes
      IPV6_AUTOCONF=no
      IPV6_DEFROUTE=yes
      IPV6_FAILURE_FATAL=no
      IPV6_PRIVACY=no
      ONBOOT=yes
      BOOTPROTO=none
      Storage Pool network-Private NW
      DEVICE=eno3
      NAME=eno3
      TYPE=Ethernet
      BOOTPROTO=none
      ONBOOT=yes
      MASTER=bond1
      SLAVE=yes
      ---------------------
      DEVICE=bond1
      NAME=bond1
      BONDING_OPTS="mode=active-backup"
      TYPE=Bond
      BONDING_MASTER=yes
      IPADDR=XXXXX
      PREFIX=24
      ONBOOT=yes
      BOOTPROTO=none

      Substitute the values for the following parameters with appropriate values:

      NAME=
      DEVICE=

      IPV6ADDR=

      IPADDR=

  2. Create necessary entries in the /etc/hosts file with appropriate hostname and IPv6 address on the CommServe and the MediaAgent nodes.
  3. To the CommServe and the MediaAgent nodes, add the nPreferredIPFamily additional setting as shown in the following table.

    For instructions about adding an additional setting from the CommCell Console, see Adding or Modifying Additional Settings from the CommCell Console.

    Property

    Value

    Name

    nPreferredIPFamily

    Category

    Session

    Type

    Integer

    Value

    0

  4. Restart the services on both the CommServe and the MediaAgent nodes after setting the registry keys.
  5. Check network connectivity between the CommServe and the MediaAgent nodes using the following command:

    ping -6 <IPv6_address>

  6. Configure the IPv4 network interface for the storage pool network.

    For example, to configure the IPv4 network interface for eno4, create the following file:

    /etc/sysconfig/network-scripts/ifcfg-eno4

  7. Check network connectivity between the storage pool interfaces using the ping command.
  8. Navigate to the following folder:

    /opt/commvault/MediaAgent

  9. Register the nodes using the following command:

    ./registertocs.py

    When prompted, provide the following information:

    • CommServe name: Type the fully qualified host name for the CommServe computer.
    • CommServe user name and password: Type the credentials to access the CommServe.
  10. Once the nodes are successfully registered, perform a readiness check to the MediaAgent nodes from the Commcell Console.

    For more information about performing the readiness check, see Viewing the Check Readiness for File System Clients, Database Clients, and Pseudo Client.

  11. After a successful readiness check, if required, create the Storage Pool using the MediaAgent nodes.

    For more information about creating a storage pool, see Configuring a Scale-Out Storage Pool.

Last modified: 8/20/2019 9:14:05 PM