MC/ Service Guard package configuration

[Manoj P.U.]

Hello All,

Can anyone please help to know whether or not following MCSG package configuration is possible?

Operating system: HP-UX B.11.11
MC / ServiceGuard: A.11.15.00

Package name Node name list Failover policy Failback policy
pkgA node1, node2 MIN_PACKAGE_NODE Manual
pkgB node3,node2,node1 MIN_PACKAGE_NODE Manual


If above configuration possible please correct me if my understanding is wrong.

During initial start-up:
Package would prefer to start on any node listed in the configuration file where no other package is running, i.e. pkgA - node1 or node2, pkgB – node3 or node2 or node1
In case no package is running on any of the node, then package would prefer to start on 1st node listed in the configuration file, i.e. pkgA - node1, pkgB - node3

Failover:
Package would prefer to failover to any node listed in the configuration file where no other package is running. And the node which had problem, when it is brought back to cluster after repair will become standby node.

Failback:
Package would not failback to the previous node that had problem when it is brought back to the cluster after repair. However it will become the new standby node.


Thanks & regards
Manoj

[Manoj P.U.]

Just to make the configuration list with more clarity.

Package: pkgA
Node list: node1, node2
Failover policy: MIN_PACKAGE_NODE
Failback policy: Manual

Package: pkgB
Node list: node3, node2, node1
Failover policy: MIN_PACKAGE_NODE
Failback policy: Manual

Thanks & Regards
Manoj

[Basheer_2]

Hello Manoj,

Yes its possible. this can be configured.

What issues you are having.

[Duncan Edmonstone · Accepted solution]

whilst technically this will work, the fact that Serviceguard 11.15 has been out of support for 3 years might present a problem...

You need to upgrade to Serviceguard 11.16, which is the only supported verion on HP-UX 11.11

HTH

Duncan

[Steven E. Protter]

Shalom,

I do recommend going to Service Guard 11.16.

Then you have two choices.

You can monkey around with the packages to achieve your goal, or you can go into sam and try and to do it with menu assist.

If you are new trying it out with sam and seeing how the package scripts come out is a good way to learn.

SEP

[Proboi]

Package: pkgA
Node list: node1, node2
Failover policy: MIN_PACKAGE_NODE
Failback policy: Manual

Package: pkgB
Node list: node3, node2, node1
Failover policy: MIN_PACKAGE_NODE
Failback policy: Manual

<<<<<<<<<<<<<<<<<<<

FAILOVER POLICY
package A will run on the node running the minimum number of packages ( does not necessarily mean the least load )

ie fails over to withever node ( node1 or node2 ) has the least NUMBER/fewest packages running


package B
for argument sake node3 is running 3 packages, node2=2 and node1=1 package each

and package B is currently running on node1 and failed it would fail over to node2 as it is running the least number of pkg's= 2 compared to node3 =3

after failover it would be node3=3 node2=3
and packageB would be running in node2

NOTE:- servicegaurd 11.15 does not look at the load each package exerts on the server inturn Just looks at the each package with equal weightage or load on server, so it looks at the number of packages running and switches over to the one running the least number of packages

FAILBACK POLICY
MANUAL - means whenever the original node ( from which the failover happened ) becomes operational the package wont switch back automatically

AUTOMATIC-
( you have not asked for this ) taking the above example , packageB
node1= 0 packages, node2=3pkg's, node3=3 pkgs running


pkgB that failed from node1 to node2, now if node1 comes up the package would automatically switch back to its original node node1

>>>>>>>>>>>>>


Please dont forget to assign points

[Manoj P.U.]

All,
Thanks a million!!! For your help.

Basheer, I am looking for this information for a new requirement.

Best regards,
Manoj