GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- Legacy
- >
- Netservers
- >
- Re: Adapter Fault Tolerance
Netservers
1857330
Members
3230
Online
110372
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
- Integrity Servers
- Server Clustering
- HPE NonStop Compute
- HPE Apollo Systems
- High Performance Computing
Knowledge Base
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Knowledge Base
Forums
Discussions
- Cloud Mentoring and Education
- Software - General
- HPE OneView
- HPE Ezmeral Software platform
- HPE OpsRamp Software
Knowledge Base
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-13-2001 10:25 PM
12-13-2001 10:25 PM
Adapter Fault Tolerance
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.
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.
Any ideas?
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.
Any ideas?
- Tags:
- NIC
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-17-2001 12:01 PM
12-17-2001 12:01 PM
Re: Adapter Fault Tolerance
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.
1) load chptx.lan slot= frame=ethernet_802.2 name=
2) LOAD CHPTX.LAN SLOT= FRAME=ETHERNET_802.2 NAME=
3) load chptx.lan slot= frame=ethernet_II name=
4) LOAD CHPTX.LAN SLOT= FRAME=ETHERNET_II NAME=
5) load hpans frame=ethernet_802.2 name= team=<1>
6) load hpans frame=ethernet_II name= team=<1>
7) bind hpans team=<1> primary
8) bind hpans team=<1>
9) bind hpans team=<1> primary
10) bind hpans team=<1>
11) load hpans commit mode= team=<1>
12) bind ipx tmipx net=
13) LOAD IPXRTRNM
14) LOAD TCPIP
15) bind ip tmip addr= mask=
16) mount all
Hope I didn't miss anything. For entries in brackets < > fill in the blanks.
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.
Chris
1) load chptx.lan slot=
2) LOAD CHPTX.LAN SLOT=
3) load chptx.lan slot=
4) LOAD CHPTX.LAN SLOT=
5) load hpans frame=ethernet_802.2 name=
6) load hpans frame=ethernet_II name=
7) bind hpans
8) bind hpans
9) bind hpans
10) bind hpans
11) load hpans commit mode=
12) bind ipx tmipx net=
13) LOAD IPXRTRNM
14) LOAD TCPIP
15) bind ip tmip addr=
16) mount all
Hope I didn't miss anything. For entries in brackets < > fill in the blanks.
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.
Chris
There's always room for J-E-L-L-O
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2026 Hewlett Packard Enterprise Development LP