Package modification and switching

[simon_164]

I am opening a discussion here so that everyone would add with his experience.
1- while the cluster is online we can:
a-add a node
b-delete a node
c-add a package
d-delete a package
e-change cluster configuration file related to failover policy and failback policy.
what else?

2- what is the full story about global switching and local switching.
a- If global switching = 0 ; packages will not be switched.
b- If global switching = 1 ; local switching on a particular node = 1: switching can happen on this node.
c- If global switching = 1 ; local switching on a particular node = 0; switching cannot happen on that particular node.
d- After halting a package for maintenance the global switching is disabled.
e- Any failure of a run / halt scripts will cause global switching to be disabled for that package.
f- After that the package switches on another node due to a service failure , local switching will be disabled.
g- if the package switches to the other node because of a subnet failure than package manager will switch the package nicely

what else ?

please reply with some smart answers !! cheers!

[simon_164]

You can add this to the above information:
1-The following modifications are allowed online:
Modify node failover order
Remove a node
Add a node
Modify package time-outs
Modify package parameters (switching, failfast)
-The following modifications are not allowed online:
Add or remove Service
Add or remove Subnet
Add or remove Resource

[Stephen Doud · Accepted solution]

See page 341 in the online "Managing Serviceguard" manual http://docs.hp.com/en/B3936-90100/B3936-90100.pdf for a list of cluster parameters and whether they can be modified while the cluster is running.