<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: service guard upgrade in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-upgrade/m-p/4668998#M666802</link>
    <description>do I need to use new package config files or the ones currently being used for 11.14 can be used for 11.16?</description>
    <pubDate>Mon, 02 Aug 2010 11:48:27 GMT</pubDate>
    <dc:creator>abhishek8191</dc:creator>
    <dc:date>2010-08-02T11:48:27Z</dc:date>
    <item>
      <title>service guard upgrade</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-upgrade/m-p/4668996#M666800</link>
      <description>I have a two node cluster and planning to upgrade to 11.16 from 11.14&lt;BR /&gt;&lt;BR /&gt;I am thinking to switch the packages and upgrade one node at a time&lt;BR /&gt;&lt;BR /&gt;I am curious if I install new version of service guard will i loose all cluster and package config files on that node, or will they get upgraded with new version and data will remain intact</description>
      <pubDate>Mon, 02 Aug 2010 10:28:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-upgrade/m-p/4668996#M666800</guid>
      <dc:creator>abhishek8191</dc:creator>
      <dc:date>2010-08-02T10:28:18Z</dc:date>
    </item>
    <item>
      <title>Re: service guard upgrade</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-upgrade/m-p/4668997#M666801</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;You should at least have a downtime window set up and here is why.&lt;BR /&gt;&lt;BR /&gt;You can stay up and running by migrating all your packages to one node and upgrading the other.&lt;BR /&gt;&lt;BR /&gt;It gets a little tricky, because the newly minted 11.16 node can not join a cluster running 11.14. Therefore the cluster needs to briefly be halted while you bring up these same services on the new 11.16 node.&lt;BR /&gt;&lt;BR /&gt;Once the node is up and running all packages, the second node can be upgraded at your leisure.&lt;BR /&gt;&lt;BR /&gt;There are a few brave souls who have figured out how to do this upgrade without downtime, but most who tried have ended up with TOC on one node.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Mon, 02 Aug 2010 11:29:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-upgrade/m-p/4668997#M666801</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2010-08-02T11:29:31Z</dc:date>
    </item>
    <item>
      <title>Re: service guard upgrade</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-upgrade/m-p/4668998#M666802</link>
      <description>do I need to use new package config files or the ones currently being used for 11.14 can be used for 11.16?</description>
      <pubDate>Mon, 02 Aug 2010 11:48:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-upgrade/m-p/4668998#M666802</guid>
      <dc:creator>abhishek8191</dc:creator>
      <dc:date>2010-08-02T11:48:27Z</dc:date>
    </item>
    <item>
      <title>Re: service guard upgrade</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-upgrade/m-p/4668999#M666803</link>
      <description>Find the below link for your reference:-&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1050309" target="_blank"&gt;http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1050309&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1384357" target="_blank"&gt;http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1384357&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 02 Aug 2010 11:49:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-upgrade/m-p/4668999#M666803</guid>
      <dc:creator>Ishwar_1</dc:creator>
      <dc:date>2010-08-02T11:49:06Z</dc:date>
    </item>
    <item>
      <title>Re: service guard upgrade</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-upgrade/m-p/4669000#M666804</link>
      <description>Please have a look at the â  upgrading Serviceguardâ   and â  if you are upgrading from earlier releasesâ   section from Serviceguard Version A11.16 release notes:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://docs.hp.com/en/B3935-90078/B3935-90078.pdf" target="_blank"&gt;http://docs.hp.com/en/B3935-90078/B3935-90078.pdf&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Bhadresh&lt;BR /&gt;</description>
      <pubDate>Mon, 02 Aug 2010 12:00:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-upgrade/m-p/4669000#M666804</guid>
      <dc:creator>Bhadresh</dc:creator>
      <dc:date>2010-08-02T12:00:39Z</dc:date>
    </item>
    <item>
      <title>Re: service guard upgrade</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-upgrade/m-p/4669001#M666805</link>
      <description>doing an upgrade of Serviceguard does NOT touch the /etc/cmcluster directory, except when it updates the cmclconfig binary in that directory..&lt;BR /&gt;So, to answer your questions:&lt;BR /&gt;&amp;gt; will i loose all cluster and package config files &lt;BR /&gt;No, they stay there.&lt;BR /&gt;&amp;gt;will they get upgraded with new version &lt;BR /&gt;Only the cmclconfig file will be updated.&lt;BR /&gt;To use the new functionality/format f the SG A.11.16 pcakge control and config files, you would need to use cmmakepkg to create a new config and a new control script, then merge your current variable settings fo rthe package into the newer ones, and reapply them.&lt;BR /&gt;But they will continue to work with the old ones, you just do not get the newfunctionality etc.</description>
      <pubDate>Mon, 02 Aug 2010 13:21:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-upgrade/m-p/4669001#M666805</guid>
      <dc:creator>melvyn burnard</dc:creator>
      <dc:date>2010-08-02T13:21:21Z</dc:date>
    </item>
    <item>
      <title>Re: service guard upgrade</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-upgrade/m-p/4669002#M666806</link>
      <description>Note that what Steven says is NOT correct.&lt;BR /&gt;&lt;BR /&gt;You do not have to halt the entire cluster. The new 11.16 node CAN join the exiting running 11.14 cluster.&lt;BR /&gt;&lt;BR /&gt;This is clearly described in the Managing Serviceguard manual in appendix E. Rolling Software Upgrades. This is step 3 on page 395 of the 2nd edition of the 11.16 manual. To quote the text to demonstrate this:&lt;BR /&gt;&lt;BR /&gt;----&lt;BR /&gt;When upgrading is finished, enter the following command on node 1 to&lt;BR /&gt;restart the cluster on node 1.&lt;BR /&gt;&lt;BR /&gt;# cmrunnode -n node1&lt;BR /&gt;&lt;BR /&gt;At this point, different versions of the Serviceguard daemon (cmcld) are&lt;BR /&gt;running on the two nodes, as shown in Figure E-4.&lt;BR /&gt;----&lt;BR /&gt;&lt;BR /&gt;The key to note here is that when you are running a mixed revision cluster in the middle of an upgrade, you should run all commands (other than cmrunnode and cmhaltnode) from the higher revision node. i.e. if you need to move a package from the 11.14 node to the 11.16 node you should do this running commands from the 11.16 node.</description>
      <pubDate>Tue, 03 Aug 2010 07:39:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/service-guard-upgrade/m-p/4669002#M666806</guid>
      <dc:creator>John Bigg</dc:creator>
      <dc:date>2010-08-03T07:39:26Z</dc:date>
    </item>
  </channel>
</rss>

