<?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: Nic Redundancy in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/nic-redundancy/m-p/3100370#M571369</link>
    <description>Get APA (Auto Port Aggregation) - this is exactly what its for.&lt;BR /&gt;&lt;BR /&gt;It needs a license,  but I don't think its a lot of money compared to what it can do.  And if you connect the cards through different switches,  you have even more resilience and the network guys can do maintenance without affecting your server connectivity.&lt;BR /&gt;&lt;BR /&gt;Its quite easy to set up too.</description>
    <pubDate>Fri, 24 Oct 2003 19:18:27 GMT</pubDate>
    <dc:creator>Neil Steurs</dc:creator>
    <dc:date>2003-10-24T19:18:27Z</dc:date>
    <item>
      <title>Nic Redundancy</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/nic-redundancy/m-p/3100366#M571365</link>
      <description>Hello all.&lt;BR /&gt;I got 4 nic Ethernet Card (A5506B) over HP-UX B.11.00 9000/800. I want it to have 2 ports with same ip and to be redundent. Any suggestions on how doing it?</description>
      <pubDate>Thu, 23 Oct 2003 05:11:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/nic-redundancy/m-p/3100366#M571365</guid>
      <dc:creator>Liadi</dc:creator>
      <dc:date>2003-10-23T05:11:08Z</dc:date>
    </item>
    <item>
      <title>Re: Nic Redundancy</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/nic-redundancy/m-p/3100367#M571366</link>
      <description>Hi,&lt;BR /&gt;Few rules.&lt;BR /&gt;Rule 1. You can not have same IP address for NIC cards at the same time. What you can do is &lt;BR /&gt;a)configure them but keep it down using, &lt;BR /&gt;ifconfig lan1 down&lt;BR /&gt;and as soon as lan0 goes down you can bring up lan1&lt;BR /&gt;b) Buy other products like MC/SG&lt;BR /&gt;c) Write you'r own script which configures the 2nd lan card as soon as first goes down.&lt;BR /&gt;Rule 2. You can not have 2 NIC cards on the same network</description>
      <pubDate>Thu, 23 Oct 2003 05:25:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/nic-redundancy/m-p/3100367#M571366</guid>
      <dc:creator>Rajeev  Shukla</dc:creator>
      <dc:date>2003-10-23T05:25:04Z</dc:date>
    </item>
    <item>
      <title>Re: Nic Redundancy</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/nic-redundancy/m-p/3100368#M571367</link>
      <description>First thanks for the quick response.&lt;BR /&gt;&lt;BR /&gt;I don't have 2 cards, I have one card with 4 nics. isn't there any way to configure 2 (or more) of them in such a way that if one is down the other goes up with same ip?</description>
      <pubDate>Thu, 23 Oct 2003 05:37:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/nic-redundancy/m-p/3100368#M571367</guid>
      <dc:creator>Liadi</dc:creator>
      <dc:date>2003-10-23T05:37:18Z</dc:date>
    </item>
    <item>
      <title>Re: Nic Redundancy</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/nic-redundancy/m-p/3100369#M571368</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Rajeev has said the most important things.&lt;BR /&gt;&lt;BR /&gt;Alternatively you may consider using APA (Auto Port Aggregation) which allows failover and trunking of network ports, but this requires a license while you could write a monitoring/failover script on your own.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Bernhard</description>
      <pubDate>Thu, 23 Oct 2003 05:40:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/nic-redundancy/m-p/3100369#M571368</guid>
      <dc:creator>Bernhard Mueller</dc:creator>
      <dc:date>2003-10-23T05:40:01Z</dc:date>
    </item>
    <item>
      <title>Re: Nic Redundancy</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/nic-redundancy/m-p/3100370#M571369</link>
      <description>Get APA (Auto Port Aggregation) - this is exactly what its for.&lt;BR /&gt;&lt;BR /&gt;It needs a license,  but I don't think its a lot of money compared to what it can do.  And if you connect the cards through different switches,  you have even more resilience and the network guys can do maintenance without affecting your server connectivity.&lt;BR /&gt;&lt;BR /&gt;Its quite easy to set up too.</description>
      <pubDate>Fri, 24 Oct 2003 19:18:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/nic-redundancy/m-p/3100370#M571369</guid>
      <dc:creator>Neil Steurs</dc:creator>
      <dc:date>2003-10-24T19:18:27Z</dc:date>
    </item>
    <item>
      <title>Re: Nic Redundancy</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/nic-redundancy/m-p/3100371#M571370</link>
      <description>Very important for APA: your swicth *must* support duplicate IP's on different interfaces. APA works with the switch to not only provide a failover path but to load balance for higher throughput. You can read all about APA at &lt;A href="http://docs.hp.com" target="_blank"&gt;http://docs.hp.com&lt;/A&gt; (look for the keyword aggregation.</description>
      <pubDate>Fri, 24 Oct 2003 19:53:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/nic-redundancy/m-p/3100371#M571370</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2003-10-24T19:53:47Z</dc:date>
    </item>
    <item>
      <title>Re: Nic Redundancy</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/nic-redundancy/m-p/3100372#M571371</link>
      <description>Hi bill ,&lt;BR /&gt;&lt;BR /&gt;I think APA software part will take care of Ip and all ip (even MAC address) related communication. It has nothing to do with switch / hub. I mean no special criteria for selecting the switch.&lt;BR /&gt;&lt;BR /&gt;It is true that for better redundancy, switch has to provide a failover path.&lt;BR /&gt;&lt;BR /&gt;Pl revert back if am wrong...</description>
      <pubDate>Mon, 10 Nov 2003 18:43:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/nic-redundancy/m-p/3100372#M571371</guid>
      <dc:creator>PVR</dc:creator>
      <dc:date>2003-11-10T18:43:16Z</dc:date>
    </item>
    <item>
      <title>Re: Nic Redundancy</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/nic-redundancy/m-p/3100373#M571372</link>
      <description>APA can be configured to operate in LAN Monitor mode with anyu hub or switch. However there won't be any load balancing or parallel data channels. For that, support for Cisco's proprietary Fast EtherChannel (FEC/PAgP) technology or IEEE 802.3ad link aggregation control protocol (LACP) is required. Switches with this feature can provide load balancing as well as duplicate switch paths (two switches provide redundancy as well as load balancing).</description>
      <pubDate>Mon, 10 Nov 2003 23:37:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/nic-redundancy/m-p/3100373#M571372</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2003-11-10T23:37:55Z</dc:date>
    </item>
  </channel>
</rss>

