SLES10 SP2 and OES2 SP2 cluster upgrade

Hey guys,

I'm having to upgrade our 3 node cluster tonight, and I just wanted to make sure I have everything covered. We are running a pretty old patch level, because its in our cluster i've always taken a "if it aint broke, don't fix it approach" but we need some of the features of OES2 SP3 now.

I just want to make sure i've got the order right and if anyone is aware of any pitfalls I should know about.

1. I'm going to cluster leave one of the nodes.
2. Apply the remaining patches for both sles 10 sp2 and oes2 sp2
3. Reboot the box
4. make sure it hasn't rejoined the cluster
5. Upgrade to sles 10 sp3 from the media
6. Fully patch sles
7. reboot
8. Upgrade to sles 10 sp4 from the media
9. reboot
10. Upgrade to oes2 sp3 from the media

Does that all sound ok, I've read the upgrade document, but I'm not sure how the cluster would cope with nodes on different service packs, or if there is anything special I need to do with them. I'm planning to take the whole lot down tonight, do one node at a time, and make sure cluster services can all load on a single node once they are patched, and then when i'm happy with that, bring all the nodes up together, and check things like failover are still working.

What do you guys think, does that all sound ok?
  • Hi.

    On 06.03.2012 12:46, Cptdave wrote:
    >
    > I just want to make sure i've got the order right and if anyone is
    > aware of any pitfalls I should know about.
    >
    > 1. I'm going to cluster leave one of the nodes.
    > 2. Apply the remaining patches for both sles 10 sp2 and oes2 sp2


    Yes. You *are* aware you're running an unsupported mix of versions to
    boot with? Only OES2 SP1 is supported on SLES10SP2.

    > 3. Reboot the box
    > 4. make sure it hasn't rejoined the cluster
    > 5. Upgrade to sles 10 sp3 from the media


    No. You *must* include the addon of OES2SP3 *during* the upgrade at this
    stage. Don't update SLES individually here.


    > 6. Fully patch sles


    And OES2SP3.

    > 7. reboot
    > 8. Upgrade to sles 10 sp4 from the media


    Either that, or just use the "move-to-sp4" online update at this point.
    It works fine.

    > Does that all sound ok, I've read the upgrade document, but I'm not
    > sure how the cluster would cope with nodes on different service packs,
    > or if there is anything special I need to do with them. I'm planning to
    > take the whole lot down tonight, do one node at a time, and make sure
    > cluster services can all load on a single node once they are patched,
    > and then when i'm happy with that, bring all the nodes up together, and
    > check things like failover are still working.


    Some services in a cluster need to run during OES patches to be properly
    updated. iPrint being a prime example. If you have iPrint clustered, at
    least on one server iPrint must be running *while* OES is patched.
    That's because the iPrint patches put files on the NSS volume used for
    iPrint.

    CU,
    --
    Massimo Rosen
    Novell Knowledge Partner
    No emails please!
    http://www.cfc-it.de
  • Thanks for the response Massimo,

    Yep, it was installed for us by an outside firm, and looking through all the doc's i've never found mention of OES2 sp2 on anything less than SLES 10 SP3. The rest of our Novell estate is running SLES 10 SP3, but the cluster went in first, so I don't know if it was just a matter of timing.

    We are only really after the CIFS shadow volume support that comes with OES2 SP3, so I guess if we can get to SP3 with SLES 10 SP3, I might stop there for now, it feels like way too many patches in one hit.

    I'll have to stick to the physical media unfortunately, we use a ZLM sever for patching and the "Move-to" patches never seem to appear.

    Thanks for all you're help.
    Dave
  • Sorry last question,

    So you're saying I should patch the cluster with all the resources up and running on it. Its a bit scary. We dropped iPrint a while back, but i'm guessing there will be other things that will catch us out.

    So would you say patch one node at a time with all the cluster resources running on it, or patch all the nodes at the same time? I was hoping to do one at a time incase we had problems.
  • Cptdave;2179807 wrote:
    Yep, it was installed for us by an outside firm, and looking through all the doc's i've never found mention of OES2 sp2 on anything less than SLES 10 SP3. The rest of our Novell estate is running SLES 10 SP3, but the cluster went in first, so I don't know if it was just a matter of timing.


    Whoever, however, OES2 SP2 on SLES10 SP2 is an unsupported combination so all bets are off.

    To be supported you need to get to a supported combo, OES2 SP2 on SLES10 SP3, so I'd be inclined to, in turn, reinstall each node correctly. Then you have a supported platform to move to OES2 SP3 on SLES10 SP4.

    HTH.
  • Hi.

    On 06.03.2012 14:16, Cptdave wrote:
    >
    > We are only really after the CIFS shadow volume support that comes with
    > OES2 SP3, so I guess if we can get to SP3 with SLES 10 SP3, I might stop
    > there for now, it feels like way too many patches in one hit.


    You shouldn't even consider this. Sles10SP3 is out of support, and no
    longer receives any (security) patches.


    CU,
    --
    Massimo Rosen
    Novell Knowledge Partner
    No emails please!
    http://www.cfc-it.de
  • Sorry Guys, I've rifled through the documentation of the guys who installed the cluster for us. I think the nodes are on SLES 10 SP3, The original docs say it was built on SP3, but when I do an SPident -v I get found SLE-10-x86_64-SP2 "online updates". However cat'ing /etc/SuSE-release says PATCHLEVEL 3.

    Sorry guys
    Dave
  • Cptdave;2179883 wrote:
    Sorry Guys, I've rifled through the documentation of the guys who installed the cluster for us. I think the nodes are on SLES 10 SP3, The original docs say it was built on SP3, but when I do an SPident -v I get found SLE-10-x86_64-SP2 "online updates". However cat'ing /etc/SuSE-release says PATCHLEVEL 3.


    What does "cat /etc/*release" report? That will give us output of both /etc/SuSE-release and /etc/novell-release which should match what your server is actually running.

    HTH.
  • Thanks Simon, it comes back with the below, so hopefully I should be fine to go straight SLES10 SP4, OES2 SP3 :

    HO-OES-N3:~ # cat /etc/*release
    SUSE Linux Enterprise Server 10 (x86_64)
    VERSION = 10
    PATCHLEVEL = 3
    LSB_VERSION="core-2.0-noarch:core-3.0-noarch:core-2.0-x86_64:core-3.0-x86_64"
    Novell Open Enterprise Server 2.0.2 (x86_64)
    VERSION = 2.0.2
    PATCHLEVEL = 2
    BUILD = FCS
    HO-OES-N3:~ #
  • All upgraded now, sorry I was panicking over nothing. thanks guys
  • On 06.03.2012 19:36, Cptdave wrote:
    >
    > All upgraded now, sorry I was panicking over nothing. thanks guys


    Not a problem. Thanks for the report back, glad it worked flawlessly.

    CU,
    --
    Massimo Rosen
    Novell Knowledge Partner
    No emails please!
    http://www.cfc-it.de