<?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: TCP IP Address in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/tcp-ip-address/m-p/4314987#M92213</link>
    <description>Ah ...makes sense.&lt;BR /&gt;&lt;BR /&gt;Thanks for the quick reply.&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Fri, 28 Nov 2008 13:35:01 GMT</pubDate>
    <dc:creator>Kevin Raven (UK)</dc:creator>
    <dc:date>2008-11-28T13:35:01Z</dc:date>
    <item>
      <title>TCP IP Address</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tcp-ip-address/m-p/4314985#M92211</link>
      <description>Quick question.&lt;BR /&gt;Where does the unique IP address per node get written to ?&lt;BR /&gt;i.e. ALPHA1 = 10.10.10.100 = ALPHA1.KEVIN.COM&lt;BR /&gt;     ALPHA2 = 10.10.10.200 = ALPHA2.KEVIN.COM&lt;BR /&gt;Both servers use interface EIA0: for IP trafic.&lt;BR /&gt;If all IP details are recorded in the following common files ....&lt;BR /&gt;$ dir sys$system:*tcp*.dat&lt;BR /&gt;&lt;BR /&gt;Directory SYS$COMMON:[SYSEXE]&lt;BR /&gt;&lt;BR /&gt;TCPIP$CONFIGURATION.DAT;1               TCPIP$HOST.DAT;1    TCPIP$NETWORK.DAT;1&lt;BR /&gt;TCPIP$PROXY.DAT;1   TCPIP$ROUTE.DAT;1   TCPIP$SERVICE.DAT;1 &lt;BR /&gt;&lt;BR /&gt;Total of 6 files.&lt;BR /&gt;$ &lt;BR /&gt;&lt;BR /&gt;How does during boot ALPHA1 know its details and ALPHA1 known what to read from the file.&lt;BR /&gt;&lt;BR /&gt;My guess is that it uses mac address of the card to find the correct IP address ?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 28 Nov 2008 13:08:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tcp-ip-address/m-p/4314985#M92211</guid>
      <dc:creator>Kevin Raven (UK)</dc:creator>
      <dc:date>2008-11-28T13:08:15Z</dc:date>
    </item>
    <item>
      <title>Re: TCP IP Address</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tcp-ip-address/m-p/4314986#M92212</link>
      <description>The TCPIP configuration file is indexed by the SCSNODE name of the system. So TCPIP can find the interface name and IP address and other node-specific parameters based on the nodename of the node, on which it is being started.&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
      <pubDate>Fri, 28 Nov 2008 13:27:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tcp-ip-address/m-p/4314986#M92212</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2008-11-28T13:27:39Z</dc:date>
    </item>
    <item>
      <title>Re: TCP IP Address</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tcp-ip-address/m-p/4314987#M92213</link>
      <description>Ah ...makes sense.&lt;BR /&gt;&lt;BR /&gt;Thanks for the quick reply.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 28 Nov 2008 13:35:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tcp-ip-address/m-p/4314987#M92213</guid>
      <dc:creator>Kevin Raven (UK)</dc:creator>
      <dc:date>2008-11-28T13:35:01Z</dc:date>
    </item>
    <item>
      <title>Re: TCP IP Address</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tcp-ip-address/m-p/4314988#M92214</link>
      <description>A write-up of where the node names and the node addresses get written with OpenVMS:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://64.223.189.234/node/589" target="_blank"&gt;http://64.223.189.234/node/589&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 28 Nov 2008 16:37:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tcp-ip-address/m-p/4314988#M92214</guid>
      <dc:creator>Hoff</dc:creator>
      <dc:date>2008-11-28T16:37:47Z</dc:date>
    </item>
  </channel>
</rss>

