Adding nodes using the VCS installer


Adding nodes using the VCS installer
Prev	Adding a node to a multi-node VCS cluster	Next

The VCS installer performs the following tasks:

Verifies that the node and the existing cluster meet communication requirements.
Verifies the products and RPMs installed on the new node.
Discovers the network interfaces on the new node and checks the interface settings.
Creates the following files on the new node:

/etc/llttab

/etc/VRTSvcs/conf/sysname
Updates the following configuration files and copies them on the new node:

/etc/llthosts

/etc/gabtab

/etc/VRTSvcs/conf/config/main.cf
Copies the following files from the existing cluster to the new node

/etc/vxfenmode

/etc/vxfendg

/etc/vx/.uuids/clusuuid

/etc/sysconfig/llt

/etc/sysconfig/gab

/etc/sysconfig/vxfen
Configures disk-based or server-based fencing depending on the fencing mode in use on the existing cluster.

At the end of the process, the new node joins the VCS cluster.

Note:

If you have configured server-based fencing on the existing cluster, make sure that the CP server does not contain entries for the new node. If the CP server already contains entries for the new node, remove these entries before adding the node to the cluster, otherwise the process may fail with an error.

To add the node to an existing VCS cluster using the VCS installer

Log in as the root user on one of the nodes of the existing cluster.
Run the VCS installer with the -addnode option.
```
# cd /opt/VRTS/install
```
```
# ./installer  -addnode
```
The installer displays the copyright message and the location where it stores the temporary installation logs.

Enter the name of a node in the existing VCS cluster. The installer uses the node information to identify the existing cluster.

Enter the name of any one node of the InfoScale Availability cluster where you
would like to add one or more new nodes:  sys1

Review and confirm the cluster information.
Enter the name of the systems that you want to add as new nodes to the cluster.
```
Enter the system names separated by spaces 
to add to the cluster: sys5
```
The installer checks the installed products and RPMs on the nodes and discovers the network interfaces.

Enter the name of the network interface that you want to configure as the first private heartbeat link.

Note:

The LLT configuration for the new node must be the same as that of the existing cluster. If your existing cluster uses LLT over UDP, the installer asks questions related to LLT over UDP for the new node. If your existing cluster uses LLT over RDMA, the installer asks questions related to LLT over RDMA for the new node.

See Configuring private heartbeat links.

Enter the NIC for the first private heartbeat 
link on sys5: [b,q,?] eth1

Enter the name of the network interface that you want to configure as the second private heartbeat link.
```
Enter the NIC for the second private heartbeat link 
on sys5: [b,q,?] eth2
```
Depending on the number of LLT links configured in the existing cluster, configure additional private heartbeat links for the new node.
The installer verifies the network interface settings and displays the information.
Review and confirm the information.
If you have configured SMTP, SNMP, or the global cluster option in the existing cluster, you are prompted for the NIC information for the new node.
```
Enter the NIC for VCS to use on sys5: eth3
```

If you have enabled security on the cluster, the installer displays the following message:

Since the cluster is in secure mode, check the main.cf 
whether you need to modify the usergroup that you would 
like to grant read access. If needed, use the following
commands to modify:

haconf -makerw
hauser -addpriv <user group> GuestGroup
haconf -dump -makero