You are on page 1of 23

Veritas Cluster Server 6.

0 for UNIX:
Cluster Management
Lesson 2: Reconfiguring Cluster Membership

Lesson introduction
Lesson 1: Service Group Dependencies
Lesson 2: Reconfiguring Cluster Membership
Lesson 3: Startup and Failover Policies
Lesson 4: Alternate Network Configurations
Lesson 5: High Availability in the Enterprise

Lesson objectives

Topic

Objectives

Adding a system to a
Add a new system to a running VCS cluster.
cluster
Merging clusters

Merge two running VCS clusters.

Additional
reconfiguring tasks

Perform additional configuration tasks to


enable services to use additional cluster
nodes.

Adding a system to a
cluster
After completing this topic, you
will be able to add a system to a
cluster.

Adding a system to a running VCS cluster


Add a new system to a running
VCS cluster:
Keeping the application
services and VCS available
Enabling the new system to
run all of the application
services.

s3
s2

Assumptions:
Two or more systems
VCS software is not installed on the new system
Shared storage can be connected to all systems

s4

Preparing the new system for clustered


application services
1 Install any necessary application
1
software on the new system.

Ensure the new system is


capable of running application
services in the cluster.

2 Configure any application resources


1
necessary to support clustered
applications.

Example configuration tasks:


Create user accounts
Copy application
configuration files
Create mount points
Verify shared storage access

3 Physically cable cluster


1 interconnect.

Change from crossover cables


to hubs or switches, if
applicable.
Ensure that the private
network is not completely
disconnected while making
changes.

Installing VCS on a single system


On the new system
4 Verify system readiness on the new
1
system.

Log in as root and navigate


to the software distribution.
Change into the install
directory.
./installvcs -precheck

5 Install VCS on the new system.


1

Install VCS using install


option.
Do not configure VCS when
prompted.
./installvcs -install

Adding the newly installed system to the


cluster
6

Add the node to the existing cluster.

./installvcs -addnode

Discovers network interfaces


Creates llttab, sysname
Copies llthosts, gabtab
Configures disk- or server-based
fencing, if present on existing
cluster
Joins the new node to the cluster
membership

Note: If the original cluster


was installed with installsf,
run installsf with the
addnode option.

This assumes fencing is already


configured on other systems; therefore
SCSI-3 support has been verified.

Verifying the new system


On the newly added system
9 Verify service are running and
1
cluster membership includes all
nodes.
Port a, b, and h
memberships should include
all the original systems and
the new system.

lltconfig
lltstat nvv active
gabconfig -a
vxfenadm -d
vxfenconfig -l

Reconfigure service groups to


run on the new system, if
appropriate. See details later
in the lesson.

Merging clusters
After completing this topic, you
will be able to merge two running
VCS clusters.

Merging two running VCS clusters


Objective:

Assumptions:

Merge two running VCS


clusters while maximizing
application services and VCS
availability.

All systems have the same operating system


and Storage Foundation versions.
All service groups can run on all systems.
Private networks of both clusters are
isolated before the merger.
All systems can access shared storage.

Source
cluster
Configuration
to be
extracted
and added
to target
cluster

s3
s1

s2

s4

Target
cluster
Retain cluster
ID for
merged fournode cluster

Adding systems to the target cluster


configuration
On the target cluster
1

Modify VCS communication files on


each system in the target cluster to
recognize the systems to be added
from the source cluster.

2 Add the names of the systems in the


1
source cluster to the target cluster.

Edit /etc/llthosts to add


entries for the new systems
from the source cluster.
Edit /etc/gabtab to
increase the n option to
gabconfig by the number of
systems in the source
cluster.
haconf -makerw
hasys add s1
hasys -add s2
haconf dump -makero

You do not need to stop and restart LLT and


GAB on the systems in the target cluster
when you make these changes

Preparing systems for clustered


application services
3

Install and configure any additional


application software required to
support the merged configuration on
all systems.
Ensure each system is capable
of running appropriate
application services.

Installation may involve:


Freezing systems
Switching applications
Rebooting systems
Example configuration tasks:
Create user accounts
Copy application
configuration files
Create mount points
Verify shared storage access

4 Install any additional VCS agents on


1
each system.
5 Copy any additional custom agents to
1
all systems.

Agents should only be


installed; *types.cf are
included later.

Merging service group configurations


On the source cluster
6a Extract service group configurations
1
from the source cluster.

hacf cftocmd \
/etc/VRTSvcs/conf/config
Edit main.cmd.
Retain service group
configuration commands.
Retain *types.cf
includes.
Copy the filtered main.cmd
to a system in the target
cluster.

On the target cluster


6b Add the service group configurations
1
to the target cluster.
Execute the filtered
main.cmd

haconf -makerw
sh main.cmd
haconf dump -makero

Stopping cluster services in the source


cluster
On the source cluster
8

Stop cluster services (VCS, fencing,


GAB, LLT) on the systems in the
source cluster.

hastop all -force

/sbin/vxfen-shutdown
On each
system

Application services are left


running on the systems.

gabconfig -U
lltconfig -U

Modifying VCS communications on the


source cluster
On each system in the source cluster

Reconfigure VCS communication


modules on all systems in the
source cluster and physically
connect private networks.

Edit /etc/llttab and


modify the cluster id to be
the same as the target
cluster.
Edit /etc/llthosts to
ensure each system has a
unique entry in the
combined cluster.
Edit /etc/gabtab and set
the
n option to gabconfig to
the total number of systems
in the combined cluster.

There may be other directives in


/etc/llttab
that need modification, such as set-addr,
include, and exclude.

Starting cluster services on systems in the


source cluster
On each system in the source cluster
10

Start cluster services on systems in


the source cluster and verify cluster
membership.

lltconfig -c
sh /etc/gabtab
vxfen_startup_file
hastart

Port a, b, and h
memberships should include
the new system

Alternately, use LLT, GAB,


fencing, and VCS startup
files.

gabconfig a

Additional
reconfiguration tasks
After completing this topic, you
will be able to reconfigure other
components within a merged
cluster.

Installing agents and configuring triggers


1 Install any necessary VCS agents
1
that are not installed automatically
by CPI.
2 Copy custom agents to necessary
1
systems.
3 Copy and merge triggers, as
1
necessary.

Install, but do not configure,


VCS agents.

Because the trigger scripts


are in use on the existing
clusters, merge the scripts
in a temporary directory.
Depending on the changes
required, it may be
necessary to stop cluster
services on the systems
before copying the merged
trigger scripts.

Updating and testing service group and


resource configuration
4
1

Update service group and resource configurations to use the new


systems.
haconf -makerw
hagrp modify group SystemList add system priority
hagrp modify group AutoStartList add system
haconf dump -makero

5
1

Verify updates by running virtual fire drills and switching the


application services to the new systems.
havfd group sys system -v
hagrp switch group to system

Update localized resources


6
1

Update resource configurations to use the new systems.


haconf -makerw
hares local resource attribute
hares modify resource attribute sys system
haconf dump -makero

7
1

Verify updates.
havfd group sys system -v
hagrp switch group to system
Customized resource type attributes require special consideration.
See the Veritas Cluster Server Administrator's Guide.

Lesson summary
Key points
You can minimize downtime when reconfiguring cluster
members.
Use the procedures in this lesson as guidelines for adding or
removing cluster systems.

Reference materials
Veritas Cluster Server Installation Guide
Veritas Cluster Server User's Guide
Veritas Cluster Server: Install and Configure course

End of Presentation