HPUX 11.0 : High Availability Configuration File

[LG Porter]

I have two K580 class servers in a MCSG configuration, running MCSG 11.12. I have two packages configured in this cluster: (pkga on Node A) and (pkgb on Node B). Each time the cluster is rebooted, both packages start on the Node A thus package pkgb has to manually switched over to Node B. Question (2 parts): A) Will editing the High Availability Configuration File (/etc/cmcluster/pkgb/pkgb.conf), in section defining the order of the nodes, will correct this problem so that pkgb starts on NODE B and pkga starts on NODE A each time the servers are rebooted?
... (pkgb.conf file ..near the FAILOVER_POLICY)
NODE_NAME NODE A
NODE_NAME NODE B

B)Can this change be made on online? (cmcheckconf -v -P pkgb.conf, cmapplyconf -v -P pkgb.conf)

[Mladen Despic · Accepted solution]

Hi,

Yes, that should fix the problem.

From the config file:

"# Enter the names of the nodes configured for this package. Repeat
# this line as necessary for additional adoptive nodes.
#
# NOTE: The order is relevant.
# Put the second Adoptive Node after the first one.
#
# Example : NODE_NAME original_node
# NODE_NAME adoptive_node
#
# If all nodes in cluster is to be specified and order is not
# important, "NODE_NAME *" may be specified.
#
# Example : NODE_NAME *

B) You should bring the package down first:

cmhaltpkg

Then run:

cmcheckconf -P
cmapplyconf -P

I don't think you need to bring the cluster down.


Mladen

[Vijeesh CTK]

hi

u can di this by editing package.ascii file

server Node1
Node2

package

pkg1
pkg2

in pkg1.ascii

NODE_NAME Node1
NODE_NAME Node2

in pkg2.ascii

NODE_NAME Node2
NODE_NAME Node1

then

cmapplyconf -C clusterconf.ascii file -P pkg1.ascii -P pkg2.ascii

CTK

[Jeff Schussele]

Hi LG,

Yes the order in the file defines what starts what by default & in a cluster > 2 it will also define the failover order.

And No you don't have to take the cluster down...unless you wish to test the startup.

Rgds,
Jeff

[melvyn burnard]

The first NODE_NAME in the package conf file is the PRIMARY node for the package, i.e. the node the package will start on first when a cluster starts.
The entry(ies) following that are the ADOPTIVE node, i.e. which nodes the package can fail over to.
Also, if you refer to the Manging ServiceGuard manul available at:
http://docs.hp.com/hpux/ha
there is a table of what can be modified online for a package in the Maintaing Packages section.
This is one of the modifications you can make while all is running.

[Geetha Alagappan]

Yes, you can change this in the package configuration file (pkg.conf or pkg.ascii). You can list the primary and adoptive nodes in this file
under NODE_NAME
-----------------------
# Enter the names of the nodes configured for this package. Repeat
# this line as necessary for additional adoptive nodes.
# Order IS relevant. Put the second Adoptive Node AFTER the first
# one.
# Example : NODE_NAME original_node
# NODE_NAME adoptive_node

NODE_NAME server1
NODE_NAME server2
----------------------------

No, you do not need to bring the package down to do this. You can modify the node failover order/startup order while the package is running with a cmapplyconf -v -P pkg.con

[Sanjay_6]

Hi,

you should apply the changed configuration once the changes have been made to the package conf file.

vi package conf file, save the changes. Check the package conf file using cmcheckconf and then do a cmapplyconf to apply the changes to the cluster configuration. you should not have to bring the package or the cluster down to do this change.

Hope this helps.

Regds