<?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: IP Address change on Cluster in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/ip-address-change-on-cluster/m-p/3849762#M10355</link>
    <description>Hi Zahid&lt;BR /&gt;&lt;BR /&gt;I think it's not required to rebuild the cluster&lt;BR /&gt;&lt;BR /&gt;During this year we changed hardware at 7 sites. The old hardware was AlphaServer 4100 2 Node cluster, the new hardware is ES45 2 node cluster with MSA100.&lt;BR /&gt;&lt;BR /&gt;I built a systemdisk which I use to build all the 7 configurations. (For this hardware change we have a time slot of only 4 hours!)&lt;BR /&gt;&lt;BR /&gt;What I do is the following:&lt;BR /&gt;- We install the hardware in a test room. Then I use the systemdisk, I mentioned before and I change the nodenames, the DECnet addresses and the IP Addresses (we use FailSafe IP with 4 interfaces in each machine)&lt;BR /&gt;&lt;BR /&gt;To change the Nodename, I have to modify SCSNODE and SCSSYSTEMID an do autogen  with reboot (The licenses must also be modified if the nodename change).&lt;BR /&gt;&lt;BR /&gt;Then I do a NET$CONFIGURE ADVANCED for changing the DECnet environment.&lt;BR /&gt;&lt;BR /&gt;To Change the IP Adresses I do a BACKUP/DELET SYS$SYSDEVICE:[000000...]TCPIP$*.DAT save_location:tcpipdat.bck/sav&lt;BR /&gt;&lt;BR /&gt;Then I reboot the machine without to start TCPIP. Finnaly I do a TCPIP$CONFIG. &lt;BR /&gt;&lt;BR /&gt;After this configuration, we transport the machine to the final destination and during a timeslot of 4 hours, we exchange the hardware, by  first copying some files like sysuaf.dat, rightslist.dat from the old to the new config, then shuting down the old config and booting the new config.&lt;BR /&gt;&lt;BR /&gt;This is a (very) short description of what I'm doing to change Names and Addresses of a OpenVMS Machine.&lt;BR /&gt;&lt;BR /&gt;In Your case you have only to change the IP Addresses. In this case it's not required to delete all the old TCPIPxy.DAT-files. Or optionally you can also restore some of the TCPIP$xx.DAT form tha backup made in the beginning, (eg. TCPIP$EXPORT, TCPIP$PRINTCAP....) after configuring TCPIP&lt;BR /&gt;&lt;BR /&gt;I hope that helps a litle bit.&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;&lt;BR /&gt;Heinz</description>
    <pubDate>Thu, 24 Aug 2006 08:19:33 GMT</pubDate>
    <dc:creator>Heinz W Genhart</dc:creator>
    <dc:date>2006-08-24T08:19:33Z</dc:date>
    <item>
      <title>IP Address change on Cluster</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/ip-address-change-on-cluster/m-p/3849761#M10354</link>
      <description>We have a 4-node split site cluster with Loadbroker for load balancing, TCP/IP 5.4 , Failover IP. We are planning to change our network. This would require new ip addresses. Our users are scattered over uk.&lt;BR /&gt;My first thought was that we could NAT our external addresses leaving the cluster as it is. BUT it looks as though load braoker etc can not work on NATted addresses.&lt;BR /&gt;Am I correct in assuming that I will have to rebuilt the cluster after adding new IP addresses or is there a less ardous way of achieving this.</description>
      <pubDate>Thu, 24 Aug 2006 07:36:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/ip-address-change-on-cluster/m-p/3849761#M10354</guid>
      <dc:creator>Zahid Ghani</dc:creator>
      <dc:date>2006-08-24T07:36:58Z</dc:date>
    </item>
    <item>
      <title>Re: IP Address change on Cluster</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/ip-address-change-on-cluster/m-p/3849762#M10355</link>
      <description>Hi Zahid&lt;BR /&gt;&lt;BR /&gt;I think it's not required to rebuild the cluster&lt;BR /&gt;&lt;BR /&gt;During this year we changed hardware at 7 sites. The old hardware was AlphaServer 4100 2 Node cluster, the new hardware is ES45 2 node cluster with MSA100.&lt;BR /&gt;&lt;BR /&gt;I built a systemdisk which I use to build all the 7 configurations. (For this hardware change we have a time slot of only 4 hours!)&lt;BR /&gt;&lt;BR /&gt;What I do is the following:&lt;BR /&gt;- We install the hardware in a test room. Then I use the systemdisk, I mentioned before and I change the nodenames, the DECnet addresses and the IP Addresses (we use FailSafe IP with 4 interfaces in each machine)&lt;BR /&gt;&lt;BR /&gt;To change the Nodename, I have to modify SCSNODE and SCSSYSTEMID an do autogen  with reboot (The licenses must also be modified if the nodename change).&lt;BR /&gt;&lt;BR /&gt;Then I do a NET$CONFIGURE ADVANCED for changing the DECnet environment.&lt;BR /&gt;&lt;BR /&gt;To Change the IP Adresses I do a BACKUP/DELET SYS$SYSDEVICE:[000000...]TCPIP$*.DAT save_location:tcpipdat.bck/sav&lt;BR /&gt;&lt;BR /&gt;Then I reboot the machine without to start TCPIP. Finnaly I do a TCPIP$CONFIG. &lt;BR /&gt;&lt;BR /&gt;After this configuration, we transport the machine to the final destination and during a timeslot of 4 hours, we exchange the hardware, by  first copying some files like sysuaf.dat, rightslist.dat from the old to the new config, then shuting down the old config and booting the new config.&lt;BR /&gt;&lt;BR /&gt;This is a (very) short description of what I'm doing to change Names and Addresses of a OpenVMS Machine.&lt;BR /&gt;&lt;BR /&gt;In Your case you have only to change the IP Addresses. In this case it's not required to delete all the old TCPIPxy.DAT-files. Or optionally you can also restore some of the TCPIP$xx.DAT form tha backup made in the beginning, (eg. TCPIP$EXPORT, TCPIP$PRINTCAP....) after configuring TCPIP&lt;BR /&gt;&lt;BR /&gt;I hope that helps a litle bit.&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;&lt;BR /&gt;Heinz</description>
      <pubDate>Thu, 24 Aug 2006 08:19:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/ip-address-change-on-cluster/m-p/3849762#M10355</guid>
      <dc:creator>Heinz W Genhart</dc:creator>
      <dc:date>2006-08-24T08:19:33Z</dc:date>
    </item>
    <item>
      <title>Re: IP Address change on Cluster</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/ip-address-change-on-cluster/m-p/3849763#M10356</link>
      <description>Heinz, Thanks for a prompt reply.&lt;BR /&gt;So in order to change the IP Addresses I 'just  need to run tcpip$config'?</description>
      <pubDate>Thu, 24 Aug 2006 08:51:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/ip-address-change-on-cluster/m-p/3849763#M10356</guid>
      <dc:creator>Zahid Ghani</dc:creator>
      <dc:date>2006-08-24T08:51:04Z</dc:date>
    </item>
    <item>
      <title>Re: IP Address change on Cluster</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/ip-address-change-on-cluster/m-p/3849764#M10357</link>
      <description>HI Zahid&lt;BR /&gt;&lt;BR /&gt;It's not so easy. Because the IP name associated with the first address you define is also used for other things. If You do a TCPIP sho config communication, you will find the nodename and the domain. &lt;BR /&gt;You will also find the IP name and address of the local node in your hosts file.&lt;BR /&gt;&lt;BR /&gt;I found out, adding some new interfaces is no problem. Changing the Address of the first interface may become tricky. That's why I delete the TCPIP$*.dat. Doing so, I never have problems to change addresses (especialy the address of the first interface)&lt;BR /&gt;&lt;BR /&gt;As mentioned in my first response, you can restore some other tcpip datafiles (eg. TCPIP$EXPORT if used) from the backup you made in the beginnig. &lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;&lt;BR /&gt;Heinz</description>
      <pubDate>Thu, 24 Aug 2006 09:02:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/ip-address-change-on-cluster/m-p/3849764#M10357</guid>
      <dc:creator>Heinz W Genhart</dc:creator>
      <dc:date>2006-08-24T09:02:02Z</dc:date>
    </item>
  </channel>
</rss>

