Adding a node to a cluster using the SFHA installer

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

The SFHA installer performs the following tasks:

At the end of the process, the new node joins the SFHA 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

  1. Log in as the root user on one of the nodes of the existing cluster.
  2. Run the SFHA installer with the -addnode option.
    # cd /opt/VRTS/install
    # ./installsfha<version> -addnode

    Where <version> is the specific release version.

    See About the Veritas installer.

    The installer displays the copyright message and the location where it stores the temporary installation logs.

  3. Enter the name of a node in the existing SFHA cluster.

    The installer uses the node information to identify the existing cluster.

    Enter one node of the SFHA cluster to which 
    you would like to add one or more new nodes: sys1
  4. Review and confirm the cluster information.
  5. 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 packages on the nodes and discovers the network interfaces.

  6. 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 sys5: [b,q,?] bge1
    Enter the NIC for the second private heartbeat 
    link on sys5: [b,q,?] bge2

    Note:

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

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

  8. Review and confirm the information.
  9. 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: bge3
    SFHA is configured on the cluster. Do you want to 
    configure it on the new node(s)? [y,n,q] (y) n

  10. 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.

    The installer indicates the location of the log file, summary file, and response file with details of the actions performed.

  11. Confirm that the new node has joined the SFHA cluster using lltstat -n and gabconfig -a commands.

    If the new node has not joined the cluster, verify if it has been added to the SystemList.