<?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: TCPIP-databases in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/tcpip-databases/m-p/4856904#M47758</link>
    <description>Jan,&lt;BR /&gt;&lt;BR /&gt;Unless he was expecting someone that says "I've got that situation and it works". In that case I would close it too without giving 8+. &lt;BR /&gt;&lt;BR /&gt;Wim</description>
    <pubDate>Mon, 13 Sep 2004 23:41:41 GMT</pubDate>
    <dc:creator>Wim Van den Wyngaert</dc:creator>
    <dc:date>2004-09-13T23:41:41Z</dc:date>
    <item>
      <title>TCPIP-databases</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tcpip-databases/m-p/4856882#M47736</link>
      <description>Hello,&lt;BR /&gt;I'm have problem with cluster with 4 nodes, when they start up, they seam to sometimes get wrong tcpip$hostname. So I'm wondering about the tcpip-databases. Should they not be located on SYS$SPECIFIC for each node not on SYS$COMMON?&lt;BR /&gt;Hope to hear from some one.&lt;BR /&gt;Thanks&lt;BR /&gt;Kjartan</description>
      <pubDate>Tue, 27 Jul 2004 15:39:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tcpip-databases/m-p/4856882#M47736</guid>
      <dc:creator>Kjartan Konradsson</dc:creator>
      <dc:date>2004-07-27T15:39:08Z</dc:date>
    </item>
    <item>
      <title>Re: TCPIP-databases</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tcpip-databases/m-p/4856883#M47737</link>
      <description>Kjartan,&lt;BR /&gt;&lt;BR /&gt;  I'm not sure what you mean by "tcpip$hostname" that's not a standard TCPIP logical name. Perhaps you mean TCPIP$INET_HOST? &lt;BR /&gt;&lt;BR /&gt;  Whatever, the TCPIP data base files are cluster aware and intended to be physically shared between nodes (ie: they should be in SYS$COMMON). The choice of host configuration should be determined by the SCS* SYSGEN parameters. If this isn't working correctly, you should log a case with your local customer support centre for proper diagnosis.&lt;BR /&gt;</description>
      <pubDate>Tue, 27 Jul 2004 18:58:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tcpip-databases/m-p/4856883#M47737</guid>
      <dc:creator>John Gillings</dc:creator>
      <dc:date>2004-07-27T18:58:28Z</dc:date>
    </item>
    <item>
      <title>Re: TCPIP-databases</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tcpip-databases/m-p/4856884#M47738</link>
      <description>Hi Kjartan,&lt;BR /&gt;&lt;BR /&gt;if we are talking about files that determine the identity of the host, modparams.dat should be in the specific tree, not in sys$common. &lt;BR /&gt;Also make sure you are not booting by chance into the wrong root of your system disk.&lt;BR /&gt;&lt;BR /&gt;Greetings, Martin</description>
      <pubDate>Tue, 27 Jul 2004 20:39:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tcpip-databases/m-p/4856884#M47738</guid>
      <dc:creator>Martin P.J. Zinser</dc:creator>
      <dc:date>2004-07-27T20:39:01Z</dc:date>
    </item>
    <item>
      <title>Re: TCPIP-databases</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tcpip-databases/m-p/4856885#M47739</link>
      <description>the TCPIP datafiles are in sys$common:[sysexe] and are indexed by SCSNODENAME. &lt;BR /&gt;Whats the exact logical that is wrong?&lt;BR /&gt;</description>
      <pubDate>Wed, 28 Jul 2004 04:41:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tcpip-databases/m-p/4856885#M47739</guid>
      <dc:creator>Ian Miller.</dc:creator>
      <dc:date>2004-07-28T04:41:42Z</dc:date>
    </item>
    <item>
      <title>Re: TCPIP-databases</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tcpip-databases/m-p/4856886#M47740</link>
      <description>Hi!&lt;BR /&gt;The logicals are TCPIP$INET_HOST and TCPIP$INET_HOSTADDR. They seem to be ok at startup but after some time they have changed and are the same as another node in the cluster. I have 4 node cluster (GS140,GS60E and 2 ES80) and this seems to happen only between the ES80 nodes. I have checked the SCSNODE and SCSSYSTEMID and they differ on the nodes.&lt;BR /&gt;KK</description>
      <pubDate>Wed, 28 Jul 2004 05:55:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tcpip-databases/m-p/4856886#M47740</guid>
      <dc:creator>Kjartan Konradsson</dc:creator>
      <dc:date>2004-07-28T05:55:46Z</dc:date>
    </item>
    <item>
      <title>Re: TCPIP-databases</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tcpip-databases/m-p/4856887#M47741</link>
      <description>Kjartan,&lt;BR /&gt;&lt;BR /&gt;Is the value of the nodename as seen in "ucx sho comm" also changed ? If so try a&lt;BR /&gt;search sys$startup:*:com new-host&lt;BR /&gt;&lt;BR /&gt;Did you try a &lt;BR /&gt;search sys$startup:*.com TCPIP$INET_HOST&lt;BR /&gt;to see if nobody defined the logical e.g. during applic startup ?&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Wed, 28 Jul 2004 06:24:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tcpip-databases/m-p/4856887#M47741</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2004-07-28T06:24:12Z</dc:date>
    </item>
    <item>
      <title>Re: TCPIP-databases</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tcpip-databases/m-p/4856888#M47742</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;If they were OK when startup, then why and how they got changed afterwards? &lt;BR /&gt;Was someone doing any reconfiguration?&lt;BR /&gt;Are you using common system disk for all the nodes ? &lt;BR /&gt;&lt;BR /&gt;Check the Audit file and operator.log if any clue is there .&lt;BR /&gt;&lt;BR /&gt;Thanks &amp;amp; regards,&lt;BR /&gt;Lokesh</description>
      <pubDate>Wed, 28 Jul 2004 06:25:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tcpip-databases/m-p/4856888#M47742</guid>
      <dc:creator>Lokesh_2</dc:creator>
      <dc:date>2004-07-28T06:25:16Z</dc:date>
    </item>
    <item>
      <title>Re: TCPIP-databases</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tcpip-databases/m-p/4856889#M47743</link>
      <description>&lt;A href="http://64.233.161.104/search?q=cache:uGjPYXs5r4sJ:starlet.deltatel.ru/sys%24common/syshlp/tcpip53eco02.release_notes+TCPIP%24INET_HOST+release&amp;amp;hl=nl" target="_blank"&gt;http://64.233.161.104/search?q=cache:uGjPYXs5r4sJ:starlet.deltatel.ru/sys%24common/syshlp/tcpip53eco02.release_notes+TCPIP%24INET_HOST+release&amp;amp;hl=nl&lt;/A&gt;&lt;BR /&gt;and find TCPIP$INET_HOST&lt;BR /&gt;&lt;BR /&gt;Do you use DHCP ? If not, what version of tcpip ?&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Wed, 28 Jul 2004 06:51:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tcpip-databases/m-p/4856889#M47743</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2004-07-28T06:51:18Z</dc:date>
    </item>
    <item>
      <title>Re: TCPIP-databases</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tcpip-databases/m-p/4856890#M47744</link>
      <description>I'm using 5.3 ECO 2 of tcpip services. And under those conditions the local host name in UCX SHOW COMM is rigth.&lt;BR /&gt;I'm not using DHCP. As I saw in the notes there is a correction on this matter in ECO 2. But what I find strange is that it began after we installed our ES80's, we were replacing for old GS80 machines.&lt;BR /&gt;&lt;BR /&gt;Kjartan</description>
      <pubDate>Wed, 28 Jul 2004 07:16:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tcpip-databases/m-p/4856890#M47744</guid>
      <dc:creator>Kjartan Konradsson</dc:creator>
      <dc:date>2004-07-28T07:16:46Z</dc:date>
    </item>
    <item>
      <title>Re: TCPIP-databases</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tcpip-databases/m-p/4856891#M47745</link>
      <description>On the es80 nodes :&lt;BR /&gt;&lt;BR /&gt;dir sys$system:*tcp*.dat &lt;BR /&gt;Are all files in sys$common ?&lt;BR /&gt;&lt;BR /&gt;Or check &lt;BR /&gt;dir sys$specific:[*]*tcp*&lt;BR /&gt;Are important files shown ?&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Wed, 28 Jul 2004 07:28:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tcpip-databases/m-p/4856891#M47745</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2004-07-28T07:28:17Z</dc:date>
    </item>
    <item>
      <title>Re: TCPIP-databases</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tcpip-databases/m-p/4856892#M47746</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;All the tcpip files are on sys$common and only TCPIP$SERVICES_LIST.DAT;1&lt;BR /&gt;TCPIP$SHUTDOWN_LIST.DAT;1&lt;BR /&gt;TCPIP$STARTUP_LIST.DAT;1&lt;BR /&gt;TCPIP$STARTUP_ORDER.DAT;1&lt;BR /&gt;are in sys$specific:&lt;BR /&gt;&lt;BR /&gt;kjartan</description>
      <pubDate>Wed, 28 Jul 2004 11:24:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tcpip-databases/m-p/4856892#M47746</guid>
      <dc:creator>Kjartan Konradsson</dc:creator>
      <dc:date>2004-07-28T11:24:40Z</dc:date>
    </item>
    <item>
      <title>Re: TCPIP-databases</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tcpip-databases/m-p/4856893#M47747</link>
      <description>The files seem ok to me. The ones in specific are work files of startup/shutdown.&lt;BR /&gt;&lt;BR /&gt;But the logicals are wrong.&lt;BR /&gt;&lt;BR /&gt;Is ucx show interface giving the correct IP address ?&lt;BR /&gt;&lt;BR /&gt;If yes, how was the gs replaced by the es ? Same name ? Same system root in cluster ?&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Thu, 29 Jul 2004 01:04:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tcpip-databases/m-p/4856893#M47747</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2004-07-29T01:04:47Z</dc:date>
    </item>
    <item>
      <title>Re: TCPIP-databases</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tcpip-databases/m-p/4856894#M47748</link>
      <description>Hi,&lt;BR /&gt;ucx show inferf shows the rigth address when this happens. The swapping of the machines was done by just replacing the hardware. Same name same address. &lt;BR /&gt;&lt;BR /&gt;Is it not any tool one can use to see what is in those tcpip databases?&lt;BR /&gt;I was rebooting one of my nodes yesterday and got an error in setting up the interfaces, it was trying to set up 2 though only 1 has ever been defined for this machine?</description>
      <pubDate>Thu, 29 Jul 2004 04:53:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tcpip-databases/m-p/4856894#M47748</guid>
      <dc:creator>Kjartan Konradsson</dc:creator>
      <dc:date>2004-07-29T04:53:32Z</dc:date>
    </item>
    <item>
      <title>Re: TCPIP-databases</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tcpip-databases/m-p/4856895#M47749</link>
      <description>KK,&lt;BR /&gt;&lt;BR /&gt;I give up. As John suggested, open a case.&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Thu, 29 Jul 2004 06:05:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tcpip-databases/m-p/4856895#M47749</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2004-07-29T06:05:59Z</dc:date>
    </item>
    <item>
      <title>Re: TCPIP-databases</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tcpip-databases/m-p/4856896#M47750</link>
      <description>&amp;gt; Is it not any tool one can use to see what is in those tcpip databases?&lt;BR /&gt;&lt;BR /&gt;Do you mean other than:&lt;BR /&gt;&lt;BR /&gt;@sys$manager:tcpip$config&lt;BR /&gt;&lt;BR /&gt;?&lt;BR /&gt;</description>
      <pubDate>Thu, 29 Jul 2004 14:54:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tcpip-databases/m-p/4856896#M47750</guid>
      <dc:creator>Doug Phillips</dc:creator>
      <dc:date>2004-07-29T14:54:14Z</dc:date>
    </item>
    <item>
      <title>Re: TCPIP-databases</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tcpip-databases/m-p/4856897#M47751</link>
      <description>Hi,&lt;BR /&gt;yes other than tcpip$config so one can see what is in the databases. How can one remove definitions for interfaces that are no longer valid for operations?&lt;BR /&gt;&lt;BR /&gt;Kjartan</description>
      <pubDate>Thu, 29 Jul 2004 15:17:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tcpip-databases/m-p/4856897#M47751</guid>
      <dc:creator>Kjartan Konradsson</dc:creator>
      <dc:date>2004-07-29T15:17:41Z</dc:date>
    </item>
    <item>
      <title>Re: TCPIP-databases</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tcpip-databases/m-p/4856898#M47752</link>
      <description>Via that same tcpip$config, select core then interfaces and go from there. That should work, no?&lt;BR /&gt;</description>
      <pubDate>Thu, 29 Jul 2004 15:22:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tcpip-databases/m-p/4856898#M47752</guid>
      <dc:creator>Doug Phillips</dc:creator>
      <dc:date>2004-07-29T15:22:07Z</dc:date>
    </item>
    <item>
      <title>Re: TCPIP-databases</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tcpip-databases/m-p/4856899#M47753</link>
      <description>Hi,&lt;BR /&gt;No, I have one node in my cluster, that is trying to initialize EWA1 that is not in the machine, when I start up tcpip, when I go into tcpip$config it does not ask me about this interface.&lt;BR /&gt;&lt;BR /&gt;Kjartan</description>
      <pubDate>Thu, 29 Jul 2004 15:26:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tcpip-databases/m-p/4856899#M47753</guid>
      <dc:creator>Kjartan Konradsson</dc:creator>
      <dc:date>2004-07-29T15:26:27Z</dc:date>
    </item>
    <item>
      <title>Re: TCPIP-databases</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tcpip-databases/m-p/4856900#M47754</link>
      <description>Stop or don't start TCPIP before you do tcpip$config; it really should rebuild the database properly when you run through the interface reconfigure option. If it doesn't, then I don't know what else to try.&lt;BR /&gt;&lt;BR /&gt;I don't have v5.3 eco2 running anyplace so I can't try anything. Sorry.&lt;BR /&gt;</description>
      <pubDate>Thu, 29 Jul 2004 16:04:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tcpip-databases/m-p/4856900#M47754</guid>
      <dc:creator>Doug Phillips</dc:creator>
      <dc:date>2004-07-29T16:04:09Z</dc:date>
    </item>
    <item>
      <title>Re: TCPIP-databases</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tcpip-databases/m-p/4856901#M47755</link>
      <description>Hi,&lt;BR /&gt;Thanks for your input, I will use the next chance I get to stop and reconfig for each node to try get red of this profblem.&lt;BR /&gt;&lt;BR /&gt;Kjartan</description>
      <pubDate>Thu, 29 Jul 2004 16:11:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tcpip-databases/m-p/4856901#M47755</guid>
      <dc:creator>Kjartan Konradsson</dc:creator>
      <dc:date>2004-07-29T16:11:46Z</dc:date>
    </item>
  </channel>
</rss>

