<?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: Node replacement in an active cluster in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/node-replacement-in-an-active-cluster/m-p/4843916#M699162</link>
    <description>Hi Eric:&lt;BR /&gt;&lt;BR /&gt;I'd opt for a cold install with current patches and follow the guidelines in document #UXSGKBAN00000071 ("Rejoining a Node To A Cluster After Hardware Upgrade").&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
    <pubDate>Wed, 17 Jan 2001 20:54:47 GMT</pubDate>
    <dc:creator>James R. Ferguson</dc:creator>
    <dc:date>2001-01-17T20:54:47Z</dc:date>
    <item>
      <title>Node replacement in an active cluster</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/node-replacement-in-an-active-cluster/m-p/4843915#M699161</link>
      <description>Hi everybody,&lt;BR /&gt;&lt;BR /&gt;I will have to replace a node in an MCSG cluster with a new one. The new node will have the same hpux 11, host name, IP, and other things than the old one : my purpose is just replacing the hardware.&lt;BR /&gt;&lt;BR /&gt;I thought of several ways to do that :&lt;BR /&gt;&lt;BR /&gt;1 : No break down : nice !&lt;BR /&gt;1a) just do fresh install on the new box (OS, applications, patches, ...)&lt;BR /&gt;1b) be aware of getting the same instance numbers with the special files of disks and lan cards (ioinit)&lt;BR /&gt;1c) make any necessary OS adjustements (hostname, IP, passwd, printers, lan services, ...)&lt;BR /&gt;1d) then, just copy /etc/cmcluster from the old box to the new one&lt;BR /&gt;1e) shutdown and unplug the old box from the lan then plug and start the new one.&lt;BR /&gt;&lt;BR /&gt;2 : Little break down&lt;BR /&gt;2a) just do fresh install on the new box (OS, applications, patches, ...)&lt;BR /&gt;2b) DO NOT be aware of getting the same instance numbers with the special files of disks and lan cards&lt;BR /&gt;2c) make any necessary OS adjustements (hostname, IP, passwd, printers, lan services, ...)&lt;BR /&gt;2d) copy all ascii configuration files from /etc/cmcluster from the old box to the new one&lt;BR /&gt;2e) make any necessary adjustements to cmcluster.ascii, package.ascii, control.sh due to the new hardware&lt;BR /&gt;2f) prevent the new box from starting the cluster at boot time&lt;BR /&gt;2g) stop the existing cluster&lt;BR /&gt;2h) shutdown and unplug the old box&lt;BR /&gt;2i) plug and start the new box&lt;BR /&gt;2j) do cmcheckconf, cmapplyconf from the new box&lt;BR /&gt;2k) restart the cluster&lt;BR /&gt;&lt;BR /&gt;3 : No break down, nothing to do : very nice !&lt;BR /&gt;3a) make_recovery from the old box&lt;BR /&gt;3b) intall the new box with&lt;BR /&gt;3c) stop and unplug the old box from the lan then plug and start the new one.&lt;BR /&gt;&lt;BR /&gt;Any comment ? Which way would you choose ? I suppose that the 3rd one is a just a beautiful dream ?&lt;BR /&gt;&lt;BR /&gt;Eric&lt;BR /&gt;&lt;BR /&gt;PBFWME : Please Be Fair With My English&lt;BR /&gt;</description>
      <pubDate>Wed, 17 Jan 2001 19:24:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/node-replacement-in-an-active-cluster/m-p/4843915#M699161</guid>
      <dc:creator>Eric SAUBIGNAC</dc:creator>
      <dc:date>2001-01-17T19:24:51Z</dc:date>
    </item>
    <item>
      <title>Re: Node replacement in an active cluster</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/node-replacement-in-an-active-cluster/m-p/4843916#M699162</link>
      <description>Hi Eric:&lt;BR /&gt;&lt;BR /&gt;I'd opt for a cold install with current patches and follow the guidelines in document #UXSGKBAN00000071 ("Rejoining a Node To A Cluster After Hardware Upgrade").&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
      <pubDate>Wed, 17 Jan 2001 20:54:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/node-replacement-in-an-active-cluster/m-p/4843916#M699162</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2001-01-17T20:54:47Z</dc:date>
    </item>
    <item>
      <title>Re: Node replacement in an active cluster</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/node-replacement-in-an-active-cluster/m-p/4843917#M699163</link>
      <description>you have missed one obvious other option, and that is to rebuild the cluster as a single node, i.e. do an on-line deletion of the node you are removing, replace the hardware after setting up the new system, ensure all connectivity is ok, adjust the cluster/package files as neceesary and add the new node on-line.</description>
      <pubDate>Thu, 18 Jan 2001 07:45:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/node-replacement-in-an-active-cluster/m-p/4843917#M699163</guid>
      <dc:creator>melvyn burnard</dc:creator>
      <dc:date>2001-01-18T07:45:24Z</dc:date>
    </item>
    <item>
      <title>Re: Node replacement in an active cluster</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/node-replacement-in-an-active-cluster/m-p/4843918#M699164</link>
      <description>Hi James &amp;amp; Melvyn,&lt;BR /&gt;&lt;BR /&gt;your answers are finally similar : i didn't know that it's possible to make some changes on an active cluster, since release 10.10. I was still working on an older basis ! So thanks for this information&lt;BR /&gt;&lt;BR /&gt;But ... as i don't know anything about the client's cluster / system / application configuration i will modify, i think i will try a mix :&lt;BR /&gt;&lt;BR /&gt;a) suppress the old node without stopping the cluster (as you suggested)&lt;BR /&gt;b) make some adjustements on the old box around MC/SG (as exporting cluster vg, ...)&lt;BR /&gt;c) make_recovery and install the new box with it&lt;BR /&gt;d) plug and start the new box&lt;BR /&gt;e) configure MC/SG with new hardware&lt;BR /&gt;f) add the node to the cluster without stopping the cluster&lt;BR /&gt;&lt;BR /&gt;expected result : no break down but maybe the transfert of the package ... good.&lt;BR /&gt;&lt;BR /&gt;I will tell there later (01/29/2001 ?) if it was a good idea to use make_recovery on an unknown system&lt;BR /&gt;&lt;BR /&gt;Thank's again&lt;BR /&gt;&lt;BR /&gt;Eric (PBFWME)</description>
      <pubDate>Thu, 18 Jan 2001 16:42:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/node-replacement-in-an-active-cluster/m-p/4843918#M699164</guid>
      <dc:creator>Eric SAUBIGNAC</dc:creator>
      <dc:date>2001-01-18T16:42:21Z</dc:date>
    </item>
    <item>
      <title>Re: Node replacement in an active cluster</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/node-replacement-in-an-active-cluster/m-p/4843919#M699165</link>
      <description>Late to close this post ... but it is never too late to make well !</description>
      <pubDate>Tue, 04 Oct 2005 06:25:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/node-replacement-in-an-active-cluster/m-p/4843919#M699165</guid>
      <dc:creator>Eric SAUBIGNAC</dc:creator>
      <dc:date>2005-10-04T06:25:08Z</dc:date>
    </item>
  </channel>
</rss>

