Adding a node to a cluster using the product installer


Adding a node to a cluster using the product installer
Prev	Adding a node to a cluster	Next

You can add a node using the - addnode option with the product installer.

The product installer performs the following tasks:

Verifies that the node and the existing cluster meet communication requirements.
Verifies the products and packages 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
Copies the following files on the new node:

/etc/llthosts

/etc/gabtab

/etc/VRTSvcs/conf/config/main.cf
Copies the following files on the new node:

/etc/llthosts

/etc/gabtab

/etc/VRTSvcs/conf/config/main.cf

/etc/vxfenmode

/etc/vxfendg

/etc/vx/.uuids/clusuuid

/etc/default/llt

/etc/default/gab

/etc/default/vxfen

/etc/vcsmmtab
Generates security credentials on the new node if the CPS server of existing cluster is secure
Configures disk-based or server-based fencing depending on the fencing mode in use on the existing cluster.

Configures disk-based fencing.
Adds the new node to the CVM, ClusterService, and VxSS service groups in the VCS configuration.

Note:

For other service groups configured under VCS, update the configuration for the new node manually.

Note:
Starts product processes and configures CVM and CFS on the new node.

Note:

At the end of the process, the new node joins the existing 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 cluster using the installer

Log in as the root user on one of the nodes of the existing cluster.
Run the product installer with the -addnode option.
```
# cd /opt/VRTS/install
```
```
# ./installsfcfsha -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 cluster.
The installer uses the node information to identify the existing cluster.
```
Enter one node of the SFCFSHA cluster to which 
you would like to add one or more new nodes: galaxy
```
Review and confirm the cluster information.
Enter the names 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: saturn
```
The installer checks the installed products and packages 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 network interface names used for the private interconnects on the new node must be the same as that of the existing nodes in the cluster. The LLT configuration for the new node must be the same as that of the existing cluster.

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

Enter the NIC for the second private heartbeat 
link on saturn: [b,q,?] bge2

Note:

At least two private heartbeat links must be configured for high availability of the cluster.

Depending on the number of LLT links configured in the existing cluster, configure additional private heartbeat links for the new node.
The product 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 saturn: bge3
```
The installer prompts you with an option to mount the shared volumes on the new node. Select y to mount them.

When completed, the installer confirms the volumes are mounted indicates the location of the log file with details of the actions performed.
If the existing cluster uses server-based fencing in secure mode, the installer will configure server-based fencing in secure mode on the new nodes.
The installer then starts all the required Veritas processes and joins the new node to cluster.
Confirm that the new node has joined the existing cluster using lltstat -n and gabconfig -a commands.

Prev	Up	Next
Before adding a node to a cluster	Home	Adding a node using the Web-based installer