<?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: 3 NICs in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/3-nics/m-p/4663059#M532822</link>
    <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;lan0 is probably defined as the default gateway on your system. That is why some traffic goes on it, in spite of your APA configuration.&lt;BR /&gt;&lt;BR /&gt;Take a look at nwmgr output for more data here.&lt;BR /&gt;&lt;BR /&gt;A good way to get all traffic to go over your aggregate LAN is to build an aggregate including all interfaces.&lt;BR /&gt;&lt;BR /&gt;Right now you are not really load balancing. To support LB_MAC load balancing, you will need to have your switch configuration adjusted to accommodate this.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
    <pubDate>Mon, 19 Jul 2010 14:42:28 GMT</pubDate>
    <dc:creator>Steven E. Protter</dc:creator>
    <dc:date>2010-07-19T14:42:28Z</dc:date>
    <item>
      <title>3 NICs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/3-nics/m-p/4663058#M532821</link>
      <description>I need help understanding why certain network traffic are using lan900(lan1 and lan2) while other traffic uses lan0.  for instance traffic on 172.20.x.x uses lan900 while 172.18.1.x uses lan0 as seen from 'lsof'&lt;BR /&gt;&lt;BR /&gt;root@pigpen:/&amp;gt;  netstat -rn&lt;BR /&gt;Routing tables&lt;BR /&gt;Destination           Gateway            Flags   Refs Interface  Pmtu&lt;BR /&gt;127.0.0.1             127.0.0.1          UH        0  lo0        4136&lt;BR /&gt;172.20.20.67          172.20.20.67       UH        0  lan900     4136&lt;BR /&gt;172.18.1.73           172.18.1.73        UH        0  lan0       4136&lt;BR /&gt;172.18.1.0            172.18.1.73        U         2  lan0       1500&lt;BR /&gt;172.20.20.0           172.20.20.67       U         2  lan900     1500&lt;BR /&gt;127.0.0.0             127.0.0.1          U         0  lo0           0&lt;BR /&gt;default               172.20.20.250      UG        0  lan900        0&lt;BR /&gt;&lt;BR /&gt;root@pigpen:/&amp;gt;  lanadmin -x -v 900&lt;BR /&gt;Link Aggregate PPA #      : 900&lt;BR /&gt;Number of Ports           : 2&lt;BR /&gt;Ports PPA                 : 2 1&lt;BR /&gt;Link Aggregation State     : LINKAGG MANUAL&lt;BR /&gt;Group Capability          : 5&lt;BR /&gt;Load Balance Mode         : MAC Address based (LB_MAC)</description>
      <pubDate>Mon, 19 Jul 2010 14:10:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/3-nics/m-p/4663058#M532821</guid>
      <dc:creator>Mike Boswell_1</dc:creator>
      <dc:date>2010-07-19T14:10:43Z</dc:date>
    </item>
    <item>
      <title>Re: 3 NICs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/3-nics/m-p/4663059#M532822</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;lan0 is probably defined as the default gateway on your system. That is why some traffic goes on it, in spite of your APA configuration.&lt;BR /&gt;&lt;BR /&gt;Take a look at nwmgr output for more data here.&lt;BR /&gt;&lt;BR /&gt;A good way to get all traffic to go over your aggregate LAN is to build an aggregate including all interfaces.&lt;BR /&gt;&lt;BR /&gt;Right now you are not really load balancing. To support LB_MAC load balancing, you will need to have your switch configuration adjusted to accommodate this.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Mon, 19 Jul 2010 14:42:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/3-nics/m-p/4663059#M532822</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2010-07-19T14:42:28Z</dc:date>
    </item>
    <item>
      <title>Re: 3 NICs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/3-nics/m-p/4663060#M532823</link>
      <description>Thanks.  Looks like I misunderstood my APA setup.  &lt;BR /&gt;&lt;BR /&gt;Can you help me dig a bit deeper into lan0.  I would like to unplug it but that results in some networks being unreachable.&lt;BR /&gt;&lt;BR /&gt;Mike</description>
      <pubDate>Mon, 19 Jul 2010 15:03:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/3-nics/m-p/4663060#M532823</guid>
      <dc:creator>Mike Boswell_1</dc:creator>
      <dc:date>2010-07-19T15:03:10Z</dc:date>
    </item>
    <item>
      <title>Re: 3 NICs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/3-nics/m-p/4663061#M532824</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;No, do not unplug lan0.&lt;BR /&gt;&lt;BR /&gt;Go through the APA configuration guide and set up an Aggregate network that includes lan0. &lt;BR /&gt;&lt;BR /&gt;Then lan0 traffic will be lan900 traffic, even in manual mode.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Mon, 19 Jul 2010 15:47:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/3-nics/m-p/4663061#M532824</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2010-07-19T15:47:48Z</dc:date>
    </item>
    <item>
      <title>Re: 3 NICs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/3-nics/m-p/4663062#M532825</link>
      <description>Thanks Steven,&lt;BR /&gt;I would like to disable/remove the lan0 connection.  The APA has 2 links now.  We really dont need the 3rd.  So I would like unplug and have all traffic route thru the APA but when we unplug it we loose some connectivity.  I would like to figure out why this lan0 has any traffic at all and config it out of any use.&lt;BR /&gt;&lt;BR /&gt;Mike</description>
      <pubDate>Mon, 19 Jul 2010 16:23:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/3-nics/m-p/4663062#M532825</guid>
      <dc:creator>Mike Boswell_1</dc:creator>
      <dc:date>2010-07-19T16:23:16Z</dc:date>
    </item>
    <item>
      <title>Re: 3 NICs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/3-nics/m-p/4663063#M532826</link>
      <description>Conceptually speaking, when the transport stack goes to figure-out how to reach a given destination IP address, it will first look for a matching host route, then a matching (sub)network route and then finally the default route.  So, given the initial routing table, lan0 is in a 172.18.1 subnet (would want to see the netmasks from ifconfig lan0 to know precisely but I'm guessing it is 255.255.255).  If the destination IP happens to be in 172.18.something then lan0 will have the matching subnet route and will be used rather than lan900, which appears to be a different subnet. &lt;BR /&gt;&lt;BR /&gt;If you simply unplug lan0 and do not bring it down and/or unplumb it, it could be that the routing code takes a while to decide that route is no good.  Assuming that 172.20.20.250 knows how to reach the 172.18.1 subnet, if you ifconfig lan0 0.0.0.0 traffic should start flowing via your lan900 interface.</description>
      <pubDate>Tue, 20 Jul 2010 16:37:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/3-nics/m-p/4663063#M532826</guid>
      <dc:creator>rick jones</dc:creator>
      <dc:date>2010-07-20T16:37:35Z</dc:date>
    </item>
  </channel>
</rss>

