<?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: Two network interfaces load balancing in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/two-network-interfaces-load-balancing/m-p/2482224#M596919</link>
    <description>Exact answer and great ideas.&lt;BR /&gt;&lt;BR /&gt;Thanks a lot.</description>
    <pubDate>Wed, 14 Feb 2001 14:12:52 GMT</pubDate>
    <dc:creator>Zelenskii Andrei</dc:creator>
    <dc:date>2001-02-14T14:12:52Z</dc:date>
    <item>
      <title>Two network interfaces load balancing</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/two-network-interfaces-load-balancing/m-p/2482221#M596916</link>
      <description>Hi Experts!&lt;BR /&gt;&lt;BR /&gt;Does anybody know, - is there possibilities&lt;BR /&gt;to make load balancing over two network interfaces on same server? (both in the same subnet)&lt;BR /&gt;&lt;BR /&gt;Mean by software method.&lt;BR /&gt;&lt;BR /&gt;Thank you in advance.</description>
      <pubDate>Fri, 12 Jan 2001 13:35:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/two-network-interfaces-load-balancing/m-p/2482221#M596916</guid>
      <dc:creator>Zelenskii Andrei</dc:creator>
      <dc:date>2001-01-12T13:35:33Z</dc:date>
    </item>
    <item>
      <title>Re: Two network interfaces load balancing</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/two-network-interfaces-load-balancing/m-p/2482222#M596917</link>
      <description>Yes.  Included with AutoPort Aggregation software is something called Lan Monitor.  This has a "hot standby" feature whereas if one card fails, the other comes up.&lt;BR /&gt;&lt;BR /&gt;see&lt;BR /&gt;&lt;A href="http://docs.hp.com/hpux/onlinedocs/netcom/hp_apa_using11i.pdf" target="_blank"&gt;http://docs.hp.com/hpux/onlinedocs/netcom/hp_apa_using11i.pdf&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;and&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://docs.hp.com/hpux/onlinedocs/J4240-90005/J4240-90005.html" target="_blank"&gt;http://docs.hp.com/hpux/onlinedocs/J4240-90005/J4240-90005.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Berlene &lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 12 Jan 2001 15:01:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/two-network-interfaces-load-balancing/m-p/2482222#M596917</guid>
      <dc:creator>Berlene Herren</dc:creator>
      <dc:date>2001-01-12T15:01:35Z</dc:date>
    </item>
    <item>
      <title>Re: Two network interfaces load balancing</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/two-network-interfaces-load-balancing/m-p/2482223#M596918</link>
      <description>APA is the proper way to go here, but if you are really strapped and cannot buy the software, you might get part of the way there through some cruder and less effective means. This presumes that your system is a server, responding to queries from others, and not initiating connections on its own.&lt;BR /&gt;&lt;BR /&gt;First, you would do something to balance the use of the two IP addresses by your clients. One way would be to implement a DNS round-robbing scheme. each time they ask for the IP address(es) of your server DNS RR would shuffle the order of the IPs in the reply.&lt;BR /&gt;&lt;BR /&gt;Another even cruder way would be to have two names, one for each IP address, and tell 1/2 your clients to use one name, the other half the other.&lt;BR /&gt;&lt;BR /&gt;Next, on the server, you use ndd to set the parameter ip_strong_es_model to a value of one. This tells the transport (among other things) to use the source IP address in addition to the destination IP address when selecting outbound routes. In a nutshell, it means that if the request comes-in on interface 1, the replies will also go out interface 1.&lt;BR /&gt;&lt;BR /&gt;However, like I said above, APA is really the better way to go. It will load balance, allow you to only consume one IP address, and will do automagic failover if one link goes belly-up.</description>
      <pubDate>Fri, 12 Jan 2001 19:22:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/two-network-interfaces-load-balancing/m-p/2482223#M596918</guid>
      <dc:creator>rick jones</dc:creator>
      <dc:date>2001-01-12T19:22:07Z</dc:date>
    </item>
    <item>
      <title>Re: Two network interfaces load balancing</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/two-network-interfaces-load-balancing/m-p/2482224#M596919</link>
      <description>Exact answer and great ideas.&lt;BR /&gt;&lt;BR /&gt;Thanks a lot.</description>
      <pubDate>Wed, 14 Feb 2001 14:12:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/two-network-interfaces-load-balancing/m-p/2482224#M596919</guid>
      <dc:creator>Zelenskii Andrei</dc:creator>
      <dc:date>2001-02-14T14:12:52Z</dc:date>
    </item>
  </channel>
</rss>

