<?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 HPUX server network identification in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/hpux-server-network-identification/m-p/2755541#M583288</link>
    <description>I currently have a server running on two different networks concurrently using DNS (two databases) and logical instances on a single lan card.  I'm trying to find some way to tell the server to operate exclusively on one network until I tell it to switch to the other, this is to ensure the correct client addresses are issued.  The domain must remain the same.  Could I place all network processes under a pair of hostnames and use these to switch?  Any ideas?</description>
    <pubDate>Mon, 01 Jul 2002 12:28:33 GMT</pubDate>
    <dc:creator>D Waghorn</dc:creator>
    <dc:date>2002-07-01T12:28:33Z</dc:date>
    <item>
      <title>HPUX server network identification</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/hpux-server-network-identification/m-p/2755541#M583288</link>
      <description>I currently have a server running on two different networks concurrently using DNS (two databases) and logical instances on a single lan card.  I'm trying to find some way to tell the server to operate exclusively on one network until I tell it to switch to the other, this is to ensure the correct client addresses are issued.  The domain must remain the same.  Could I place all network processes under a pair of hostnames and use these to switch?  Any ideas?</description>
      <pubDate>Mon, 01 Jul 2002 12:28:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/hpux-server-network-identification/m-p/2755541#M583288</guid>
      <dc:creator>D Waghorn</dc:creator>
      <dc:date>2002-07-01T12:28:33Z</dc:date>
    </item>
    <item>
      <title>Re: HPUX server network identification</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/hpux-server-network-identification/m-p/2755542#M583289</link>
      <description>Hello,&lt;BR /&gt;&lt;BR /&gt;I saw you posted this question and another similar posting a few days ago and not received any replies.  That is probably because none of us can think of a way to implement what you want to do in a standard or supported configuration. &lt;BR /&gt;&lt;BR /&gt;The only other idea that I had is to run each instance of your application in a different MC/ServiceGuard package.  That way you can stop and start the application from listening on a specific (virtual) IP. &lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;-&amp;gt; Brian Hackley</description>
      <pubDate>Tue, 02 Jul 2002 12:14:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/hpux-server-network-identification/m-p/2755542#M583289</guid>
      <dc:creator>Brian Hackley</dc:creator>
      <dc:date>2002-07-02T12:14:12Z</dc:date>
    </item>
    <item>
      <title>Re: HPUX server network identification</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/hpux-server-network-identification/m-p/2755543#M583290</link>
      <description>Thanks Brian,&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 03 Jul 2002 06:42:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/hpux-server-network-identification/m-p/2755543#M583290</guid>
      <dc:creator>D Waghorn</dc:creator>
      <dc:date>2002-07-03T06:42:53Z</dc:date>
    </item>
    <item>
      <title>Re: HPUX server network identification</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/hpux-server-network-identification/m-p/2755544#M583291</link>
      <description>Brian&lt;BR /&gt;&lt;BR /&gt;I've done some tinkering and now have a script&lt;BR /&gt;to change the IP address of the server from restricted SAM and reboot.  The resolver then picks this up for the correct DNS database.&lt;BR /&gt;&lt;BR /&gt;However DHCP still appears to issue the wrong client subnet addresses, using the first range listed, not the correct one.  Any ideas? All clients connect locally through a hub.</description>
      <pubDate>Wed, 03 Jul 2002 06:50:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/hpux-server-network-identification/m-p/2755544#M583291</guid>
      <dc:creator>D Waghorn</dc:creator>
      <dc:date>2002-07-03T06:50:03Z</dc:date>
    </item>
    <item>
      <title>Re: HPUX server network identification</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/hpux-server-network-identification/m-p/2755545#M583292</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;If you want your server to operate exclusively on one network, why don't you bring down the other IP address using ifconfig ? If oyu want to switch, bring it up and bring the other IP address down.&lt;BR /&gt;&lt;BR /&gt;HtH,&lt;BR /&gt;Mark</description>
      <pubDate>Wed, 03 Jul 2002 07:34:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/hpux-server-network-identification/m-p/2755545#M583292</guid>
      <dc:creator>Mark van Hassel</dc:creator>
      <dc:date>2002-07-03T07:34:38Z</dc:date>
    </item>
    <item>
      <title>Re: HPUX server network identification</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/hpux-server-network-identification/m-p/2755546#M583293</link>
      <description>You don't say what your database software is... If its Oracle, its possible to configure 'failover' connections in the tnsnames.ora file of your clients (assuming you connect to the database via SQLNet/Net8) - Using this along with a combination of adding/removing the IP addresses on the fly should give you the desired functionality. &lt;BR /&gt;&lt;BR /&gt;HTH&lt;BR /&gt;&lt;BR /&gt;Duncan</description>
      <pubDate>Wed, 03 Jul 2002 08:35:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/hpux-server-network-identification/m-p/2755546#M583293</guid>
      <dc:creator>Duncan Edmonstone</dc:creator>
      <dc:date>2002-07-03T08:35:24Z</dc:date>
    </item>
    <item>
      <title>Re: HPUX server network identification</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/hpux-server-network-identification/m-p/2755547#M583294</link>
      <description>Thanks Mark and Duncan&lt;BR /&gt;&lt;BR /&gt;Tried the ifconfig 'switch'.  Interesting. For some reason the software distributor daemon then fails and Oracle (the db Duncan) won't start.  Bringing the original lan instance back up re-enables the software dist. daemon, but Ora still refuses.&lt;BR /&gt;&lt;BR /&gt;Unfortunately our NT4 clients are 'dumb' on a rembo image.  They call a URL in IE5 to access ORA(Apache).  Everything is on the server.&lt;BR /&gt;&lt;BR /&gt;Thought I had my dual DNS databases and resolver sorted, but using an ifconfig 'switch' seems to kill this as well.&lt;BR /&gt;&lt;BR /&gt;Thanks for all your ideas guys, I seem to be having a problem assigning points, but all your help is much appreciated.</description>
      <pubDate>Wed, 03 Jul 2002 13:52:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/hpux-server-network-identification/m-p/2755547#M583294</guid>
      <dc:creator>D Waghorn</dc:creator>
      <dc:date>2002-07-03T13:52:46Z</dc:date>
    </item>
  </channel>
</rss>

