<?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 Adapter Fault Tolerance in Netservers</title>
    <link>https://community.hpe.com/t5/netservers/adapter-fault-tolerance/m-p/2631464#M1029</link>
    <description>I'm trying to set up Network Adapter Fault tolerance on a new LH3000 running NetWare 5.0 (SP6a).  For cards, I have the integrated NIC built into the motherboard and an extra HP PCI NIC in Slot 2.  Both NIC work independantly, and using the HPAFT driver I can get a working fault tolerant pair - almost.  Everything is fine until a nic fails over. When the Preferred primary comes back on line, the server registers multiple ABENDs.  I'm using the CHPTX drivers that come with the Navigator CD (which, incidentally, doesn't provide an install script for NW5.0).  Why am I not using the newer HPANS driver, I hear someone ask? Well, I run two protocols on two different Ethernet Frame types - IPX on Eth. 802.2, and IP on Eth. II.  Yes, I need both protocols, and, yes, I need both frame types. I can't get both frame types to bind successfully to HPANS, so I'm using the older HPAFT.NLM instead.&lt;BR /&gt;&lt;BR /&gt;What I really need is simply to be able to run both protocols on their respective frame types in a fault tolerant manner.  I'd prefer to use load balancing, but i'll settle for a mere redundancy.&lt;BR /&gt;&lt;BR /&gt;Any ideas?</description>
    <pubDate>Fri, 14 Dec 2001 06:25:34 GMT</pubDate>
    <dc:creator>Stephen McKay</dc:creator>
    <dc:date>2001-12-14T06:25:34Z</dc:date>
    <item>
      <title>Adapter Fault Tolerance</title>
      <link>https://community.hpe.com/t5/netservers/adapter-fault-tolerance/m-p/2631464#M1029</link>
      <description>I'm trying to set up Network Adapter Fault tolerance on a new LH3000 running NetWare 5.0 (SP6a).  For cards, I have the integrated NIC built into the motherboard and an extra HP PCI NIC in Slot 2.  Both NIC work independantly, and using the HPAFT driver I can get a working fault tolerant pair - almost.  Everything is fine until a nic fails over. When the Preferred primary comes back on line, the server registers multiple ABENDs.  I'm using the CHPTX drivers that come with the Navigator CD (which, incidentally, doesn't provide an install script for NW5.0).  Why am I not using the newer HPANS driver, I hear someone ask? Well, I run two protocols on two different Ethernet Frame types - IPX on Eth. 802.2, and IP on Eth. II.  Yes, I need both protocols, and, yes, I need both frame types. I can't get both frame types to bind successfully to HPANS, so I'm using the older HPAFT.NLM instead.&lt;BR /&gt;&lt;BR /&gt;What I really need is simply to be able to run both protocols on their respective frame types in a fault tolerant manner.  I'd prefer to use load balancing, but i'll settle for a mere redundancy.&lt;BR /&gt;&lt;BR /&gt;Any ideas?</description>
      <pubDate>Fri, 14 Dec 2001 06:25:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/netservers/adapter-fault-tolerance/m-p/2631464#M1029</guid>
      <dc:creator>Stephen McKay</dc:creator>
      <dc:date>2001-12-14T06:25:34Z</dc:date>
    </item>
    <item>
      <title>Re: Adapter Fault Tolerance</title>
      <link>https://community.hpe.com/t5/netservers/adapter-fault-tolerance/m-p/2631465#M1030</link>
      <description>My documentation says that you can bind both protocols to the HPANS.LAN driver, so lets make sure your loading everything in the correct order. &lt;BR /&gt;&lt;BR /&gt;1) load chptx.lan slot=&lt;PRIMARYSLOT&gt; frame=ethernet_802.2 name=&lt;CHPTX_2_E82&gt;&lt;BR /&gt;2) LOAD CHPTX.LAN SLOT=&lt;SECONDARYSLOT&gt; FRAME=ETHERNET_802.2 NAME=&lt;CHPTX_1_E82&gt;&lt;BR /&gt;3) load chptx.lan slot=&lt;PRIMARYSLOT&gt; frame=ethernet_II name=&lt;CHPTX_2_EII&gt;&lt;BR /&gt;4) LOAD CHPTX.LAN SLOT=&lt;SECONDARYSLOT&gt; FRAME=ETHERNET_II NAME=&lt;CHPTX_1_EII&gt;&lt;BR /&gt;5) load hpans frame=ethernet_802.2 name=&lt;TMIPX&gt; team=&amp;lt;1&amp;gt;&lt;BR /&gt;6) load hpans frame=ethernet_II name=&lt;TMIP&gt; team=&amp;lt;1&amp;gt;&lt;BR /&gt;7) bind hpans &lt;CHPTX_1_E82&gt; team=&amp;lt;1&amp;gt; primary&lt;BR /&gt;8) bind hpans &lt;CHPTX_2_E82&gt; team=&amp;lt;1&amp;gt;&lt;BR /&gt;9) bind hpans &lt;CHPTX_1_EII&gt; team=&amp;lt;1&amp;gt; primary&lt;BR /&gt;10) bind hpans &lt;CHPTX_2_EII&gt; team=&amp;lt;1&amp;gt;&lt;BR /&gt;11) load hpans commit mode=&lt;AFT&gt; team=&amp;lt;1&amp;gt;&lt;BR /&gt;12) bind ipx tmipx net=&lt;NET&gt;&lt;BR /&gt;13) LOAD IPXRTRNM&lt;BR /&gt;14) LOAD TCPIP&lt;BR /&gt;15) bind ip tmip addr=&lt;IPADDRESS&gt; mask=&lt;SUBNETMASK&gt;&lt;BR /&gt;16) mount all&lt;BR /&gt;&lt;BR /&gt;Hope I didn't miss anything.  For entries in brackets &amp;lt; &amp;gt; fill in the blanks.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;If you still can't bind both protocols to the team, let me know.  I have a more complex process if this one doesn't work. Also, if you get an error message when trying to bind the protocol, let me know what it is. &lt;BR /&gt;&lt;BR /&gt;Chris&lt;/SUBNETMASK&gt;&lt;/IPADDRESS&gt;&lt;/NET&gt;&lt;/AFT&gt;&lt;/CHPTX_2_EII&gt;&lt;/CHPTX_1_EII&gt;&lt;/CHPTX_2_E82&gt;&lt;/CHPTX_1_E82&gt;&lt;/TMIP&gt;&lt;/TMIPX&gt;&lt;/CHPTX_1_EII&gt;&lt;/SECONDARYSLOT&gt;&lt;/CHPTX_2_EII&gt;&lt;/PRIMARYSLOT&gt;&lt;/CHPTX_1_E82&gt;&lt;/SECONDARYSLOT&gt;&lt;/CHPTX_2_E82&gt;&lt;/PRIMARYSLOT&gt;</description>
      <pubDate>Mon, 17 Dec 2001 20:01:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/netservers/adapter-fault-tolerance/m-p/2631465#M1030</guid>
      <dc:creator>Chris Blumenshine</dc:creator>
      <dc:date>2001-12-17T20:01:28Z</dc:date>
    </item>
  </channel>
</rss>

