VCS : Adding new node to the existing cluster

Install the  VCS software manually  on server check the  packages  and install the license key.

1. ./Installvcs -installonly

Configuring LLT and GAB: Create the LLT and GAB configuration files on the new node and update the files on the existing nodes.
To configure LLT 1 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 are adding east to a cluster consisting of north and south:

–  If the file on one of the existing nodes resembles: file /etc/llthosts

0 north
1 south

– Update the file for all nodes, including the new one, resembling: file /etc/llthosts

0 north
1 south
2 east

2.  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 east is the new node on cluster number 2:

set-node east
set-cluster 2
link qfe0 qfe:0 – ether – link
qfe1 qfe:1 – ether – 3

On the new system, run the command:

# /sbin/lltconfig -c

To configure GAB

1. Create the file /etc/gabtab on the new system.

–  If the /etc/gabtab file on the existing nodes resembles:

# /sbin/gabconfig –c

Then the file on the new node should be the same, although it is recommended to use the -c-nN option, where “N” is the number of cluster nodes.

– If the /etc/gabtab file on the existing nodes resembles:

# /sbin/gabconfig -c -n2

Then, 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 required to be ready to form a cluster before VCS starts.

2. On the new node, run the command, to configure GAB:

# /sbin/gabconfig -c

To verify GAB

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

2. Run the same command on the other nodes (north and south) 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

** Adding the node to the existing cluster:
Perform these tasks on one of the existing nodes in the cluster.

To add the new node to the existing cluster;

1. Enter the command:

# haconf -makerw

2. Add the new system to the cluster:

# hasys -add east

3. Stop VCS on the new node:

# hastop -sys east

4. Copy the main.cf file from an existing node to your new node:

# rcp /etc/VRTSvcs/conf/config/main.cf east:/etc/VRTSvcs/conf/config/

5. Start VCS on the new node:

# hastart

6. If necessary, modify any new system attributes.

7. Enter the command:


# haconf -dump -makero

 

Starting VCS and verifying the cluster

Start VCS after adding the new node to the cluster and verify the cluster.

To start VCS and verify the cluster
1. From the new system, start VCS with the new system added to the cluster:

 

# hastart

2 . Run the GAB configuration command on each node to verify that Port “a” and Port “h” include the new node in the membership:

# /sbin/gabconfig -a
GAB Port Memberships
===================================
Port a gen a3640003 membership 012
Port h gen fd570002 membership 012

Ramdev

Ramdev

I have started unixadminschool.com ( aka gurkulindia.com) in 2009 as my own personal reference blog, and later sometime i have realized that my leanings might be helpful for other unixadmins if I manage my knowledge-base in more user friendly format. And the result is today's' unixadminschool.com. You can connect me at - https://www.linkedin.com/in/unixadminschool/

7 Responses

  1. Jayapal says:

    nice one

  2. Pal says:

    Does we need to edit the main.cf file in exidting nodes prior to copy to new node ?

    • Ramdev Ramdev says:

      you don’t need to touch main.cf, if you are modifying the configuration with ha commands. but make sure you follow the sequence

      >>> open the configuration in read write mode with : haconf -makerw

      >>> Make the modifications

      >>> save the configuratio into main.cf : haconf -dump -makero

  3. Abhishek says:

    Is it necessary to copy main.cf from running node to new node ? I mean, on new node, if llt and gab starts, hastart  will look for configuration files on running cluster and update it’s local config files accordingly .  
    If not,
    If main.cf is copied, types.cf should also be copied. what say Rama..?? 

  4. Ramdev Ramdev says:

    Abhishek,

    is it necessary to copy main.cf from running node to new node ? 

    copying is something we wan’t do when we have more numbers of changes to replicate over.  Alternatively you can copy the running config to the local files using  “haconf -dump -makero”., if those changes were made when the running config in write mode.

    If main.cf is copied, types.cf should also be copied. what say Rama..?? 

    if you are not using the customized types.cf, the default one work’s well , because we anyway manage same level of VCS and supporting packages for all the cluster nodes.

  1. May 23, 2013

    VCS: Alter Cluster and Replace Faulty Node…

    Adding and Removing Cluster Nodes Adding and remov…

  2. September 18, 2015

    […] Read – VCS for Beginners –  Adding new node to the existing cluster […]

What is in your mind, about this post ? Leave a Reply

Close
  Our next learning article is ready, subscribe it in your email

What is your Learning Goal for Next Six Months ? Talk to us