<?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: MC/SG rolling upgrade in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/mc-sg-rolling-upgrade/m-p/2853752#M711541</link>
    <description>I am working with David on this project. Actually we were not upgrading the systems. We did cool install on them and then restore the configuration from the backups. That's why David mentioned restoring pkg file.&lt;BR /&gt;&lt;BR /&gt;We'd solved this problem by modifying the /var/adm/inetd.sec file. Originally, the following entry existed in the inetd.sec:&lt;BR /&gt;hacl-cfg allow NodeA NodeB&lt;BR /&gt;&lt;BR /&gt;We changed it into:&lt;BR /&gt;hacl-cfg allow NodeA NodeB 127.0.0.1&lt;BR /&gt;&lt;BR /&gt;And then the convertion completed successfully.&lt;BR /&gt;&lt;BR /&gt;What we still don't understand is why the 127.0.0.1 IP was not resolved as localhost or loopback but unknown by inetd according the error message from syslog. &lt;BR /&gt;&lt;BR /&gt;For the reason why it use 127.0.0.1 other than the primary IP address of the server, I guess it's because the convert utillity wants to must sure it's converting the local content. Can anybody confirm it? &lt;BR /&gt;&lt;BR /&gt;Thanks!</description>
    <pubDate>Wed, 27 Nov 2002 20:56:17 GMT</pubDate>
    <dc:creator>Glen Liu</dc:creator>
    <dc:date>2002-11-27T20:56:17Z</dc:date>
    <item>
      <title>MC/SG rolling upgrade</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mc-sg-rolling-upgrade/m-p/2853748#M711537</link>
      <description>Got a problem when I tried to convert old version cluster binary file to the new verion. &lt;BR /&gt;&amp;lt; unable="" to="" open="" local="" cluster="" handle.="" no="" such="" file="" or="" directory.=""&amp;gt;&lt;BR /&gt;Anybody know what's cluster handle?&lt;BR /&gt;Also got an entry in syslog.log&lt;BR /&gt;&lt;HACL-CFG&gt;&lt;BR /&gt;&lt;BR /&gt;Need help. &lt;BR /&gt;Thx&lt;BR /&gt;David&lt;/HACL-CFG&gt;</description>
      <pubDate>Wed, 27 Nov 2002 19:13:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mc-sg-rolling-upgrade/m-p/2853748#M711537</guid>
      <dc:creator>jh_yang</dc:creator>
      <dc:date>2002-11-27T19:13:09Z</dc:date>
    </item>
    <item>
      <title>Re: MC/SG rolling upgrade</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mc-sg-rolling-upgrade/m-p/2853749#M711538</link>
      <description>How about some more info, like what OS and SG versions involved, steps taken so far etc?</description>
      <pubDate>Wed, 27 Nov 2002 19:24:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mc-sg-rolling-upgrade/m-p/2853749#M711538</guid>
      <dc:creator>melvyn burnard</dc:creator>
      <dc:date>2002-11-27T19:24:53Z</dc:date>
    </item>
    <item>
      <title>Re: MC/SG rolling upgrade</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mc-sg-rolling-upgrade/m-p/2853750#M711539</link>
      <description>2 nodes cluster.&lt;BR /&gt;before upgrade: OS 10.20, SG: 10.11&lt;BR /&gt;after upgrade: OS 11.00, SG: 11.14&lt;BR /&gt;&lt;BR /&gt;Step1: Switch the pkg to Node B&lt;BR /&gt;Step2: Upgrade the Node A to OS 11.00 and SG 11.14.&lt;BR /&gt;Step3: Restore the cluster files to Node A&lt;BR /&gt;Step4: Convert the old binary file on Node A&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 27 Nov 2002 19:29:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mc-sg-rolling-upgrade/m-p/2853750#M711539</guid>
      <dc:creator>jh_yang</dc:creator>
      <dc:date>2002-11-27T19:29:17Z</dc:date>
    </item>
    <item>
      <title>Re: MC/SG rolling upgrade</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mc-sg-rolling-upgrade/m-p/2853751#M711540</link>
      <description>When you say:&lt;BR /&gt;Restore cluster files to node A&lt;BR /&gt;&lt;BR /&gt;why did you need to do htis, if you have done an upgrade, hten teh files would still be htere&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 27 Nov 2002 19:33:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mc-sg-rolling-upgrade/m-p/2853751#M711540</guid>
      <dc:creator>melvyn burnard</dc:creator>
      <dc:date>2002-11-27T19:33:51Z</dc:date>
    </item>
    <item>
      <title>Re: MC/SG rolling upgrade</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mc-sg-rolling-upgrade/m-p/2853752#M711541</link>
      <description>I am working with David on this project. Actually we were not upgrading the systems. We did cool install on them and then restore the configuration from the backups. That's why David mentioned restoring pkg file.&lt;BR /&gt;&lt;BR /&gt;We'd solved this problem by modifying the /var/adm/inetd.sec file. Originally, the following entry existed in the inetd.sec:&lt;BR /&gt;hacl-cfg allow NodeA NodeB&lt;BR /&gt;&lt;BR /&gt;We changed it into:&lt;BR /&gt;hacl-cfg allow NodeA NodeB 127.0.0.1&lt;BR /&gt;&lt;BR /&gt;And then the convertion completed successfully.&lt;BR /&gt;&lt;BR /&gt;What we still don't understand is why the 127.0.0.1 IP was not resolved as localhost or loopback but unknown by inetd according the error message from syslog. &lt;BR /&gt;&lt;BR /&gt;For the reason why it use 127.0.0.1 other than the primary IP address of the server, I guess it's because the convert utillity wants to must sure it's converting the local content. Can anybody confirm it? &lt;BR /&gt;&lt;BR /&gt;Thanks!</description>
      <pubDate>Wed, 27 Nov 2002 20:56:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mc-sg-rolling-upgrade/m-p/2853752#M711541</guid>
      <dc:creator>Glen Liu</dc:creator>
      <dc:date>2002-11-27T20:56:17Z</dc:date>
    </item>
    <item>
      <title>Re: MC/SG rolling upgrade</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mc-sg-rolling-upgrade/m-p/2853753#M711542</link>
      <description>well yes it does need that localhost.&lt;BR /&gt;&lt;BR /&gt;I am glad you fixed it, but have to alert you to the fact that in fact the method you have used to do a  "rolling upgrade" is not actually suported.</description>
      <pubDate>Thu, 28 Nov 2002 07:54:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mc-sg-rolling-upgrade/m-p/2853753#M711542</guid>
      <dc:creator>melvyn burnard</dc:creator>
      <dc:date>2002-11-28T07:54:16Z</dc:date>
    </item>
  </channel>
</rss>

