Search <book_title>...

Cluster Server 7.3.1 Configuration and Upgrade Guide - Solaris

Last Published: 2019-04-17

Product(s): InfoScale & Storage Foundation (7.3.1)

Platform: Solaris

Configuring LLT and GAB when adding a node to the cluster

Create the LLT and GAB configuration files on the new node and update the files on the existing nodes.

To configure LLT when adding a node to the cluster

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
```
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:
- For Solaris 11 SPARC
```
set-node sys2
set-cluster 2
link net1 /dev/net/net0 - ether - -
link net2 /dev/net/net0 - ether - -
```
For Solaris x64:
```
set-node  sys2
set-cluster 2
link e1000g0 e1000g:0 - ether - -
link e1000g1 e1000g:1 - ether - -
```
Copy the following file from one of the nodes in the existing cluster to the new node:
/etc/default/llt
On the new system, run the command:
```
# /sbin/lltconfig -c
```
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

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.
Copy the following file from one of the nodes in the existing cluster to the new node:
/etc/default/gab
On the new node, to configure GAB run the command:
```
# /sbin/gabconfig -c
```

To verify GAB

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
```

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