MC Service Gaurd Upgardation

[santhanakrishnan_1]

Dear All,

Here we're currently having MCSG 11.14.Now the customer is insisting us to upgrade it to 11.17 or 11.16.The servers are in production.Anyone can help me how to go about it.OS is 11.11

[Arunvijai_4]

Hi,

Check these docs, it could be useful

http://docs.hp.com/en/B3935-90091/index.html
http://docs.hp.com/en/B3936-90100/index.html

-Arun

[Warren_9]

hi,

assume dual node config for rolling upgrade.

1. switch all packages from node1 to node2
2. upgrade the SG software on node1.
3. switch all packages from node2 to node1
(caution: all SG command should run from node1)
4. upgrade the SG on node2.
5. resume the package to normal.

GOOD LUCK!!

[Rajeev Shukla]

As said before you can find the documents to do this here http://docs.hp.com/en/B3936-90100/apes02.html?btnNext=next%A0%BB but there are some limitations of doing the upgrade in this way and what i will do or suggest is...say its a 2 node clutser (Node A and Node B)
fallback the package to other node (Node B)and remove the existing server from the cluster. Now you got MC/SG running on only (Node B)one server. Remove the MC/SG software from the Node A and install the new version of serviceguard on that node. Create a new cluster (single node cluster on Node A). Migrate the packages to this new cluster and free up the other node (node B) and do the similar process on node B. After the node B is updated with new version of MC/SG join it with the cluster running on node A.

[Steven E. Protter]

Shalom,

The general concept is called rolling upgrade.

You fail over all your packages to one node and then upgrade the other.

Then the fun comes when you fail your packages from the old node to the new node. If this works, you upgrade node1 in a no downtime situation.

I think based on increases network checking that I ran into with 11.16 in my lab, you would be best off to schedule some downtime, even if its only on an "if we need it" basis.

There is enough that can go wrong with this, that you need to be prepared for a service outage.

As always, full Ignite backups of each node before you start.

SEP

[santhanakrishnan_1]

HI,

Thanx for ur inputs.The activity is scheduled by next sunday.I am carrying out this upgration by taking 4 hrs downtime.Bcoz i want to upgrade for 6 clusters

[melvyn burnard]

As you have HP-UX 11.11 you can only upgrade to 11.16 of Serviceguard.
It is very simple to do, just follow the steps in the Release Notes or the Managing Servieguard Manual, Appendix E

[m saravanan]

SK,

Go through the 11.16 Releasenote carefully, like known issues & workaround. Since 11.16 is having role based access control (not file based access control), u've to modify the "Access control Policy parameters" in cluster ascii file & apply it to the cluster to reflect the change. This is to give the permission to users other than root, to have access to monitor, configure the service guard.


Regds,
Saravanan