To configure LLT when adding a node to the cluster

1. Create the file /etc/llthosts on the new node. You must also update it on each of the current nodes in the cluster.

   For example, suppose you add sys5 to a cluster consisting of sys1 and sys2:

   • If the file on one of the existing nodes resembles:

      0 sys1
      1 sys2

   • Update the file for all nodes, including the new one, resembling:

      0 sys1
      1 sys2
      2 sys5

2. Create the file /etc/llttab on the new node, making sure that line beginning "set-node" specifies the new node.

   The file /etc/llttab on an existing node can serve as a guide.

   The following example describes a system where node sys2 is the new node on cluster ID number 2:

   set-node sys2
   set-cluster 2
   link eth1 eth-00:04:23:AC:12:C4 - ether - -
   link eth2 eth-00:04:23:AC:12:C5 - ether - -

3. Copy the following file from one of the nodes in the existing cluster to the new node:

   /etc/sysconfig/llt

4. On the new system, run the command:

   For RHEL 7, SLES 12, and supported RHEL distributions:

   # systemctl start llt

   For earlier versions of RHEL, SLES, and supported RHEL distributions:

   # /etc/init.d/llt start

   In a setup that uses LLT over UDP, new nodes automatically join the existing cluster if the new nodes and all the existing nodes in the cluster are not separated by a router. However, if you use LLT over UDP6 link with IPv6 address and if the new node and the existing nodes are separated by a router, then do the following:

   • Edit the /etc/llttab file on each node to reflect the link information about the new node.

   • Specify the IPv6 address for UDP link of the new node to all existing nodes. Run the following command on each existing node for each UDP link:

     # /sbin/lltconfig -a set systemid device_tag address

To configure GAB when adding a node to the cluster

1. Create the file /etc/gabtab on the new system.

   • If the /etc/gabtab file on the existing nodes resembles:

     /sbin/gabconfig -c

     The file on the new node should be the same. Veritas recommends that you use the -c -nN option, where N is the total number of cluster nodes.

   • If the /etc/gabtab file on the existing nodes resembles:

     /sbin/gabconfig -c -n2

     The file on all nodes, including the new node, should change to reflect the change in the number of cluster nodes. For example, the new file on each node should resemble:

     /sbin/gabconfig -c -n3

     The -n flag indicates to VCS the number of nodes that must be ready to form a cluster before VCS starts.

2. Copy the following file from one of the nodes in the existing cluster to the new node:

   /etc/sysconfig/gab

3. On the new node, to configure GAB run the command:

   For RHEL 7, SLES 12, and supported RHEL distributions:

   # systemctl start gab

   For earlier versions of RHEL, SLES, and supported RHEL distributions:

   # /etc/init.d/gab start

To verify GAB

1. On the new node, run the command:

   # /sbin/gabconfig -a
   

   The output should indicate that port a membership shows all nodes including the new node. The output should resemble:

   GAB Port Memberships
   ====================================
   Port a gen a3640003 membership 012

2. Run the same command on the other nodes (sys1 and sys2) to verify that the port a membership includes the new node:

   # /sbin/gabconfig -a
   GAB Port Memberships
   ====================================
   Port a gen a3640003 membership 012
   Port h gen fd570002 membership 01
   Port h gen fd570002    visible ; 2