<?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: lan setup in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/lan-setup/m-p/3110593#M896480</link>
    <description>As pointed-out, APA is the best way to go for #1. Bond both links together into one virtual NIC as seen by the transport, and give it one IP address.&lt;BR /&gt;&lt;BR /&gt;For 2 and 3, which I suspect are to be considered together, if you configure two physical (from the standpoint of the transport) NICs into the same IP subnet, the way routing works by default under HP-UX, both will be used for inbound (based on the IP address in the packet) and only one will be used for outbound.&lt;BR /&gt;&lt;BR /&gt;Now, in that two NICs in the one subnet case you can start to control which interface is used for outbound by adding explicit static routes.  Or you can set ip_strong_es_model in which case, both nics will be used for inbound and outbound, based (very) strictly on the IP addresses in the headers.&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Wed, 05 Nov 2003 20:51:42 GMT</pubDate>
    <dc:creator>rick jones</dc:creator>
    <dc:date>2003-11-05T20:51:42Z</dc:date>
    <item>
      <title>lan setup</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lan-setup/m-p/3110589#M896474</link>
      <description>Is it feasible to configure the two NIC into the ff. setup.&lt;BR /&gt;&lt;BR /&gt;1.Use both NIC for incoming and outgoing with load sharing &lt;BR /&gt;2.Use 1 NIC for incoming only &lt;BR /&gt;3.Use 1 NIC for outgoing only &lt;BR /&gt;</description>
      <pubDate>Wed, 05 Nov 2003 03:29:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lan-setup/m-p/3110589#M896474</guid>
      <dc:creator>Jay C. Quibuloy</dc:creator>
      <dc:date>2003-11-05T03:29:22Z</dc:date>
    </item>
    <item>
      <title>Re: lan setup</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lan-setup/m-p/3110590#M896476</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;You need a product called:APA ( Auto Port Aggregation )&lt;BR /&gt;to bind two physical network card to single Logical interface.&lt;BR /&gt;&lt;BR /&gt;TT</description>
      <pubDate>Wed, 05 Nov 2003 03:40:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lan-setup/m-p/3110590#M896476</guid>
      <dc:creator>Thayanidhi</dc:creator>
      <dc:date>2003-11-05T03:40:35Z</dc:date>
    </item>
    <item>
      <title>Re: lan setup</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lan-setup/m-p/3110591#M896478</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Thayanidhi has given you the answer for 1.&lt;BR /&gt;&lt;BR /&gt;the answers for 2. and 3. are NO.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Bernhard</description>
      <pubDate>Wed, 05 Nov 2003 04:14:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lan-setup/m-p/3110591#M896478</guid>
      <dc:creator>Bernhard Mueller</dc:creator>
      <dc:date>2003-11-05T04:14:47Z</dc:date>
    </item>
    <item>
      <title>Re: lan setup</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lan-setup/m-p/3110592#M896479</link>
      <description>Ok thanks for immediate reply.&lt;BR /&gt;&lt;BR /&gt;cheers:&amp;gt;</description>
      <pubDate>Wed, 05 Nov 2003 20:34:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lan-setup/m-p/3110592#M896479</guid>
      <dc:creator>Jay C. Quibuloy</dc:creator>
      <dc:date>2003-11-05T20:34:22Z</dc:date>
    </item>
    <item>
      <title>Re: lan setup</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lan-setup/m-p/3110593#M896480</link>
      <description>As pointed-out, APA is the best way to go for #1. Bond both links together into one virtual NIC as seen by the transport, and give it one IP address.&lt;BR /&gt;&lt;BR /&gt;For 2 and 3, which I suspect are to be considered together, if you configure two physical (from the standpoint of the transport) NICs into the same IP subnet, the way routing works by default under HP-UX, both will be used for inbound (based on the IP address in the packet) and only one will be used for outbound.&lt;BR /&gt;&lt;BR /&gt;Now, in that two NICs in the one subnet case you can start to control which interface is used for outbound by adding explicit static routes.  Or you can set ip_strong_es_model in which case, both nics will be used for inbound and outbound, based (very) strictly on the IP addresses in the headers.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 05 Nov 2003 20:51:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lan-setup/m-p/3110593#M896480</guid>
      <dc:creator>rick jones</dc:creator>
      <dc:date>2003-11-05T20:51:42Z</dc:date>
    </item>
  </channel>
</rss>

