Search <book_title>...

InfoScale™ 9.0 Storage Foundation and High Availability Configuration and Upgrade Guide - Linux

Last Published: 2025-04-18

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

Platform: Linux

Section I. Introduction to SFHA
1. Introducing Storage Foundation and High Availability
Section II. Configuration of SFHA
Section III. Upgrade of SFHA
Section IV. Post-installation tasks
1. Performing post-installation tasks
  1. Switching on Quotas
  2. About configuring authentication for SFDB tools
    1. Configuring vxdbd for SFDB tools authentication
Section V. Adding and removing nodes
1. Adding a node to SFHA clusters
2. Removing a node from SFHA clusters
  1. Removing a node from a SFHA cluster
Section VI. Configuration and upgrade reference

Adding a node to a cluster using the Veritas InfoScale installer

You can add a node to a cluster using the -addnode option with the Veritas InfoScale installer.

The Veritas InfoScale installer performs the following tasks:

Verifies that the node and the existing cluster meet communication requirements.
Verifies the products and RPMs installed but not configured 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 and copies the following files to the new node from the existing 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 SFHA cluster.

Prerequisite

Enable the required LLT ports on the firewall.

See Enabling LLT ports in firewall.

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.

See Removing the node configuration from the CP server.

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 Veritas InfoScale 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 SFHA cluster.
The installer uses the node information to identify the existing cluster.
```
Enter the name of any one node of the InfoScale ENTERPRISE 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
```
Confirm if the installer prompts if you want to add the node to the cluster.
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.
```
Enter the NIC for the first private heartbeat 
link on sys5: [b,q,?] eth1
```
```
Enter the NIC for the second private heartbeat 
link on sys5: [b,q,?] eth2
```
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 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 the existing cluster uses server-based fencing, the installer will configure server-based fencing on the new nodes.
The installer then starts all the required processes and joins the new node to cluster.
The installer indicates the location of the log file, summary file, and response file with details of the actions performed.
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
```
Confirm that the new node has joined the SFHA cluster using lltstat -n and gabconfig -a commands.