Forum Discussion

tanislavm's avatar
tanislavm
Level 6
11 years ago

vcs upgrade

Hi, Please I like to find out how I should upgrade vcs on 2 nodes cluster.I run that on solaris 10. The steps are like: - hastop -local -evacuate ;stop vcs on node a and evacuate group on node b who runs vcs. - init 1, single user in node a - apply patch - reboot node a - hastart ;start vcs on node a - hastop -local -evacuate;stop vcs on node b and evacuate groups on node a - init 1;node b on single user mode -apply patch - reboot node b - hagrp -switch to tnx so much, marius
  • With active node being node "a"

    If you choose "a" first, then you create an outage straight away when you switch the group to "b" and then after you have upgrade "a", you create a second outage as you switch group back to "a", so you can upgrade "b"

    Where as if you upgrade "b" first, then there is no initial outage, and then after you have upgrade "b", you create your first and only outage as you switch to "b", so you can upgrade "a".  Note there should be no need to switch group from "b" to "a" after upgrading "a" as your service groups should be equally capable of running on either node.

    Mike

16 Replies

  • Hi Mike, Please in the case with minimum downtime,we also should patch Solaris 10 and VCS,tell me what are the steps with 2 nodes vcs 5.1. tnx so much, marius
  • For minimum downtime:
     

     

    Run "hastop -all -force", this stops "had" daemon and VCS agents, but does NOT stop applications, so they remain running - you can then stop and LLT (gabconfig -U and lltconfig -U) and unload GAB and LLT from kernel (modinfo to get ids and then use modunload).

    Then you can upgrade VCS to 6.x while applications are running and once VCS upgrade is complete, just start, LLT, GAB and VCS.

    Then patch O/S - choose node which has the least service groups running first (example in an active-passive) cluster - choose the passive node) - suppose this is node a - then:

    - hastop -local -evacuate ;stop vcs on node a and evacuate group (if any running) to node b who runs vcs.
    - init 1, single user in node a
    - apply patch
    - reboot node a
    - hastart ;start vcs on node a
    - hastop -local -evacuate;stop vcs on node b and evacuate groups to node a
    - init 1;node b on single user mode
    -apply patch
    - reboot node b

     

    Mike

  • Hi Mike, I wish to check with you the following. you wrote "Then patch O/S - choose node which has the least service groups running first (example in an active-passive) cluster - choose the passive node) - suppose this is node a". I agreed. Please why I should patch the passive node first and not the active node first? tnx so much, marius
  • With active node being node "a"

    If you choose "a" first, then you create an outage straight away when you switch the group to "b" and then after you have upgrade "a", you create a second outage as you switch group back to "a", so you can upgrade "b"

    Where as if you upgrade "b" first, then there is no initial outage, and then after you have upgrade "b", you create your first and only outage as you switch to "b", so you can upgrade "a".  Note there should be no need to switch group from "b" to "a" after upgrading "a" as your service groups should be equally capable of running on either node.

    Mike

  • Hi Mike, I wish to check with you a thing. When a resource is added from one vcs node with: haconf -makerw hagrp -add groupw hares -add diskgroup haconf -dump -makero Then all the above commands are executed on all vcs nodes.right?had from every vcs nodes using gab knows that now should to execute the above commands. when a new node join to an vcs then all the information regarding nodes,resource group so on are loaded into memory from the remote vcs nodes.right? tnx so much, marius
  • Hi marius,

    There is no way you can upgrade a sol 10 host to sol 11.

    Oracle Solaris do not provide a way for this. Solaris 11 install has to be a fresh install.