cmmodpkg command clarification

[Sagar Sirdesai]

Hi

There is a 2 node cluster configured using Service Guard.

The AUTO_RUN=YES is et so that package moves to the configured node.

I tested that the package switch is successful to the adoptive when it failes on the primary.
My Question once the package moves to adoptive node

Why we need to use enable switching again for the primary node using commodpkg command

[Aneesh Mohan · Accepted solution]

Hi Sagar,

As per my logic ,

If you switched a package from primary to adoptive or viceversa the switching attribute of the package for a particulare node will get disable.The command cmmodpkg will enable the package switching and node switch attributes manually.

> I tested that the package switch is successful to the adoptive when it failes on the primary.

See, again if the package fails on the secondary and the above intelligence is not there then it will automatically try to start on primary node ( Primary node already proved that it had some issue while running the package),so the operation keep on toggle mode.

So, this attribute allows to prevent the repeated switching unless untill we are informing the cluster that the node is ready for switching using cmmodpkg.


Regards,

Aneesh

[Duncan Edmonstone]

Lets put this in some simpler words...

if a package fails on a node, don't you think you need to determine *why* it failed on that node before allowing it to run there again?

That's the behaviour in Serviceguard. Your operational procedures should be such that following a failover an admin determines the cause of the failure and rectifies the problem. After the problem is fixed, cmmodpkg is run to enable the package to run on that node again.

HTH

Duncan

[Sagar Sirdesai]

Thanks to both of you for answers.

Sagar

[Sagar Sirdesai]

Thanks for the answers