Highlighted
Absent Member.
Absent Member.
4027 views

How to enable NIC teaming for Netware 6.5 server

I have a Netware 6.5 server running on IBM xSeries 345. It comes with dual
NIC. With Windows OS, I set them up as Virtual NIC for automatic fail over.
Can anyone give me tips on how to do the same on NetWAre 6.5.

Thanks
Labels (1)
0 Likes
2 Replies
Highlighted
Absent Member.
Absent Member.

Re: How to enable NIC teaming for Netware 6.5 server

Most lan cards come with a driver to do this, Intel use iANS.lan,
Broadcom use Qasp.lan, etc. Instructions owuld have to come from them.

Also the NetWare TCPIP stack has this ability built in. TID 10072189
explains this very well.
--
Andrew C Taubman
Novell Support Forums Volunteer SysOp
http://support.novell.com/forums
(Sorry, support is not provided via e-mail)

Opinions expressed above are not
necessarily those of Novell Inc.
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: How to enable NIC teaming for Netware 6.5 server

On Tue, 18 Apr 2006 16:52:38 +0000, user wrote:

> I have a Netware 6.5 server running on IBM xSeries 345. It comes with
> dual NIC. With Windows OS, I set them up as Virtual NIC for automatic
> fail over. Can anyone give me tips on how to do the same on NetWAre 6.5.
>
> Thanks


I am using teaming on two NW 6.5 servers. One system uses the Intel iANS
driver, the other uses the Broadcom BASP driver. The way I do it, and is
generally recommended, is to use a separate ncf file to load the drivers
instead of allowing inetcfg to handle the configuration.

I created a ncf named lacpteam.ncf and call it from the autoexec.ncf.

Here are the contents of both my lacpteam.ncf files. Note I have double
spaced the lines to foil my newsreaders desire join and word wrap the
lines. Please feel free to use and modify, simply adjust the slot numbers
and IP addresses acordingly.

For the Intel NICs
========================
load ce1000.lan slot=10008 frame=ethernet_ii name=ce1000_1_eii Jumbo=9000

load ce1000.lan slot=10009 frame=ethernet_ii name=ce1000_2_eii Jumbo=9000

load ians.lan frame=ethernet_ii name=ad_team team=1

bind ians ce1000_1_eiiteam=1

bind ians ce1000_2_eii team=1

load ians commit mode=ad team=1

bind ip ad_team addr=192.168.10.102 mask=255.255.255.0

========================


For the Broadcom NICs
============================
load basp.lan frame=ethernet_ii name=basp_1_eii vslot=1 mode=802.3ad

load b57.lan frame=ethernet_ii name=b57_1_eii slot=10016 jumbo=9000

load b57.lan frame=ethernet_ii name=b57_2_eii slot=10017 jumbo=9000

basp bind basp_1_eii b57_1_eii

basp bind basp_1_eii b57_2_eii

bind ip basp_1_eii addr=192.168.10.100 mask=255.255.255.0

============================

Also you should know there are three or four types of teaming depending on
which NIC you are using. As you can see from my configs, I'm using LACP
with both types of Nics.

Intel supports four types
=======================
Adapter Fault Tolerance (AFT) or AKA as Failover

Adaptive Load Balancing (ALB) or AKA as Load Balancing

Link Aggregation or AKA Cisco EtherChannel Trunking

IEEE 802.3ad Dynamic Link Aggregation (LACP)

=============================

Broadcom supports three types
=========================
Smart Load Balancing (SLB) or AKA as Load Balancing

Generic Link Aggregation (Trunking) AKA Cisco EtherChannel Trunking

IEEE 802.3ad Dynamic Link Aggregation (LACP)

=========================================

Here are a couple of links that I found very helpful.

A document from Dell about NIC teaming with Broadcom nics.

http://support.dell.com/support/edocs/network/r35278/broadcom%20nic%20teaming_1.1_final.doc

Information for teaming Intel Nics:

http://bcr2.uwaterloo.ca/~brecht/servers/docs/PowerEdge-2600/en/IntelNIC/nw_ians.htm

Hope this helps..
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.