<?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 I64 NIC redundancy in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/i64-nic-redundancy/m-p/3954187#M53980</link>
    <description>Does anyone know if the I64/OpenVMS supports NIC redundancy transparently?&lt;BR /&gt;I think Tru64 supports this and that it there is known as NetRAIN.&lt;BR /&gt;Linux on Intel Pro/100S NIC's supports this. Intel calls it "adaptive fault tolerance". Basically what I am after is system support for one IP for 2 or more NICs such that each and every end applications need not worry at the application level about fail over from one network path gone bad to a backup path.&lt;BR /&gt;</description>
    <pubDate>Thu, 01 Mar 2007 18:36:36 GMT</pubDate>
    <dc:creator>Claus Olesen</dc:creator>
    <dc:date>2007-03-01T18:36:36Z</dc:date>
    <item>
      <title>I64 NIC redundancy</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/i64-nic-redundancy/m-p/3954187#M53980</link>
      <description>Does anyone know if the I64/OpenVMS supports NIC redundancy transparently?&lt;BR /&gt;I think Tru64 supports this and that it there is known as NetRAIN.&lt;BR /&gt;Linux on Intel Pro/100S NIC's supports this. Intel calls it "adaptive fault tolerance". Basically what I am after is system support for one IP for 2 or more NICs such that each and every end applications need not worry at the application level about fail over from one network path gone bad to a backup path.&lt;BR /&gt;</description>
      <pubDate>Thu, 01 Mar 2007 18:36:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/i64-nic-redundancy/m-p/3954187#M53980</guid>
      <dc:creator>Claus Olesen</dc:creator>
      <dc:date>2007-03-01T18:36:36Z</dc:date>
    </item>
    <item>
      <title>Re: I64 NIC redundancy</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/i64-nic-redundancy/m-p/3954188#M53981</link>
      <description>Welcome the VMS Forum,&lt;BR /&gt;&lt;BR /&gt;You have two options, and you can combine the two for really interesting network diagrams.&lt;BR /&gt;&lt;BR /&gt;FAILsafe IP, described very well at &lt;A href="http://h71000.www7.hp.com/openvms/journal/v2/articles/tcpip.html" target="_blank"&gt;http://h71000.www7.hp.com/openvms/journal/v2/articles/tcpip.html&lt;/A&gt; handles TCPIP connections only.&lt;BR /&gt;&lt;BR /&gt;LAN Failover, is described in Chapter 10, Volume 2 of the System Manager's Manual.  &lt;A href="http://h71000.www7.hp.com/doc/82FINAL/aa-pv5nj-tk/aa-pv5nj-tk.HTMl" target="_blank"&gt;http://h71000.www7.hp.com/doc/82FINAL/aa-pv5nj-tk/aa-pv5nj-tk.HTMl&lt;/A&gt;  &lt;BR /&gt;&lt;BR /&gt;You can create FAILsafe IP addresses on LAN failover logical adapters.  For true redundancy, you'll also want redundant network equipment.&lt;BR /&gt;&lt;BR /&gt;LAN Failover tends to provide slightly faster failover, but ties up multiple NICs.  FailSAFE IP can provide better bandwidth if that's an issue.  &lt;BR /&gt;&lt;BR /&gt;Andy</description>
      <pubDate>Thu, 01 Mar 2007 19:05:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/i64-nic-redundancy/m-p/3954188#M53981</guid>
      <dc:creator>Andy Bustamante</dc:creator>
      <dc:date>2007-03-01T19:05:03Z</dc:date>
    </item>
  </channel>
</rss>

