Adding additional node to cluster

[wip]

Help -

Current Scenario

Two node cluster works 24/7

Need to migrate package to a new node and configure it as primary with out package service outage

Is this possible ,is it possible to configure a new node and configure it as primary node with out
bringing down the cluster.

Appreciate and will reward your valid immediate replay

Jayan

[Arunvijai_4]

Hi Jayan,

This doc should be helpful,

http://docs.hp.com/en/B3936-90079/ch04s01.html

Refer to the chapter on "Cluster and Package Maintenance" for more information about changing the cluster configuration dynamically, that is, while the cluster is running.

-Arun

[Sivakumar TS]

Hi Jayan,

You can adda node without having to shutdown the pkg.

check this for detailed procedure for the doing this,

http://docs.hp.com/en/B3936-90079/ch07s02.html

Regards,

Siva.

[John Bigg]

Yes this is possible.

What you need to do is to configure the new node ready for Serviceguard and the package and add it into your cluster ascii file. You can then add the new node into the package ascii file specifying it at the top of the list of configured nodes which will make this the primary.

Then all you need to do is to run cmapplyconf -v -C cluster.ascii -P package.ascii and this will add the new node into the cluster and make this new node the primary for the package (although the package will still be left running on the node it was running on at the time).

This can all be done online without halting either the package or the cluster.

[John Bigg]

Just a quick additional note. In order to get the package running on the new node you will then need to halt the package on the original node and re-start the package on the new node which will give a short period of package service outage, but I'm sure you understood this.

[Chan 007]

Jay,

Ensure that the MAX CONFIGURED PACKAGES parameter will allow you to do so to add a new package to a running clauter.

Also I got bit confused in your question,
"Miggrate a package to a NEW node".

That means, you have a package running that will be migrated to a new node to the cluster. If this is the case you need an outage as this disturbs the QUORUM of the cluster. As the new node will be an addition to the 2 nodes that are already running.

Chan

[John Bigg]

This is a reply to Chan 007's comments.

You are not adding a new package so the value of MAX CONFIGURED PACKAGES is irrelevant.

Adding a new node does not require downtime for quorum changes unless you have 2 specific configurations.

- A 1 node cluster with no cluster lock or quorum server defined would need downtime to add one of these if adding another node.
- A 4 node cluster with a cluster lock would need downtime to remove the cluster lock (and to possibly replace with quorum server) to add a node since cluster lock is only supported with up to 4 nodes.

It is perfectly possible to add a new node and specify the same cluster lock or quorum server as is being used by the other nodes apart from in these two specific configurations.

[Kent Ostby]

Jayan --

Take a look at this document in the database for this problem: UXSGKBRC00006816

[Chan 007]

Jay,

John is 100% correct, Mark my prev postinh a BIG FAT "0".

John,

Thanks a lot for pointing my mistake. I was splleing and thinking of my Org. clusters while posting.

Chan

[Stephen Doud]

Yes, you can add a node to a cluster and make it the primary server of a package while the cluster & package are running.

First, add the node to the cluster configuration ASCII file.
Either manually add all the necessary lines or create another ASCII file using cmquerycl on just the new node and then transfer the node-specific lines into the original cluster ASCII file.
In the original ASCII file, edit the lines to add a cluster lock disk if used, and alter STATIONARY_IP and HEARTBEAT_IP to match the other nodes in the original ASCII file.

# cmapplyconf -C

If this succeeds as it should, edit the package configuration file:
Locate the NODE_NAME reference and duplicate it.
Change the NODE_name reference listed first to the new node name. eg:
NODE_NAME helix
NODE_NAME helix
to
NODE_NAME torus
NODE_NAME helix

Copy the package directory to the new node
# cmapplyconf -P

Use cmviewcl -v -p to verify the package primary owner is the new node.