1. nw_3_4.exe Driver
2. inetcfg.txt File Contents

inetcfg.txt Driver File Contents (nw_3_4.exe)

CONFIGURING ADAPTER TEAMING WITH INETCFG
----------------------------------------

INETCFG is a utility provided with Netware that provides a menu system
for adapter and protocol configuration.  It works by removing the
adapter and protocol control lines from AUTOEXEC.NCF and placing them in
its own control files.  Once this has been done, changes to the network 
configuration are made through a series of menus.

Using INETCFG provides a convenient way to organize your network
configuration, especially if you have WAN and other components in your
network.  However, the automation that INETCFG provides does not take
into account features that go above and beyond the normal functions of
network adapters.  Network teaming is one of the functions not supported
by INETCFG.

For a network teaming to work the following elements must be configured.

1.  AFT.NLM must be loaded
2.  At least two adapters must be installed and drivers must be loaded
    for each adapter in the team and for each frame type that will be
    used.
3.  The Primary Adapter in the team must have all protocols that will be
    used bound to it, while the secondary adapter(s) must not have any
    protocols bound to them.

INETCFG, by default loads each adapter with each frame type, and binds 
all protocols to each adapter.  If the bindings to the adapter are
removed, INETCFG assumes that the board is not in use and will not load
the driver for it.  So, to support teaming, we must remove the bindings
from the secondary adapter(s) but still load the drivers for these
adapters.  To do this, we change the status of the adapters from
"Enabled" to "Force" and manually disable the bindings from the
secondary adapter(s).  After this, we will edit the AUTOEXEC.NCF file to
load the AFT.NLM driver, and to set up our team.

The following steps describe how to do this:

1.  Change the status of the adapters from "Enabled" to "Force".
    a.  From the Internetworking Configuration menu, select Boards.
    b.  For each board in the Configured Boards list who's status
        is "Enabled" or "Disabled":
        - Use the Up and Down Arrow keys to highlight the board.
        - Press <TAB> until the board's status is "Force".
    c.  Note the board name (ex: CE100B_1) and slot number for each 
        adapter you wish to set up as secondary adapters.  You will 
        use the board name(s) disable the bindings for the adapter(s) 
        and the slot numbers to assign the adapters to teams.    
    This will force the driver to load for each adapter, even if
    no protocols are bound to that adapter.

2.  Remove the bindings from the secondary adapter(s).
    a.  From the Internetworking Configuration menu, select Bindings.
    b.  For each Binding in the Protocol To Interface/Group Bindings
        list
        - Use the Up and Down Arrow keys to select the first binding
          with the board name(s) you noted in the above step.
        - Press <TAB> to change the binding from Enabled to Disabled.
        - There may be multiple bindings for each physical board, so
          repeat this operation for each binding with the selected
          board name(s).

3.  Edit AUTOEXEC.NCF to load AFT.NLM and to set up teams on server
    startup.
    a.  From the Internetworking Configuration menu, select Manage
        Configuration.
    b.  From the Manage Configuration menu, select Edit AUTOEXEC.NCF.
    c.  Locate the line in AUTOEXEC.NCF that reads
        "sys:etc\initsys.ncf".
    d.  Place a line above the "sys:etc\initsys.ncf" line that reads
        LOAD AFT.NLM
    e.  Place the AFT BIND line to set up your adapter team below the
        "sys:etc\initsys.ncf" line.  (EX:  AFT BIND 9 10)  Use the
        slot numbers you recorded earlier to specify the adapters to
        be teamed.

    The file NWTEAM.TXT provides a detailed description of the commands
    used to set up a team.

After the above steps have been completed the server must be restarted
before the changes take effect.


IDENTIFYING THE ADAPTERS IN YOUR SYSTEM

    Because different computer systems assign "Slot" numbers
    differently, the slot number of a given adapter does not always
    correspond to the physical slot the adapter is plugged into.  To
    avoid confusion, it is a good idea to start by identifying which
    adapters are in which "slot".  An easy way to do this is by using
    the Netware Monitor application.  

  a.  Make sure the CE100B.LAN or E100B.LAN driver is loaded
      for each adapter.  (Type LOAD CE100B.LAN or LOAD E100B.LAN.
      answering No if the "Do you want to add another frame type
      for a previously loaded board?" prompt.  You will be presented
      with a list of available slots. Make a selection from the
      list.  Continue this process until you get the "All supported
      options are ALREADY in use" message.  This will indicate that
      drivers are loaded for all adapters.
      
  b.  Type "LOAD MONITOR" to load the MONITOR.NLM application. Select
      the LAN/WAN drivers option from the Available Options menu. You
      will be presented with a list of Available LAN Drivers.  For each
      item in the list:
        -  Select the item and press <TAB>.  This will bring up the 
           statistics screen for this adapter.
        -  Arrow down until you get to the Custom Counters section
           of the display.  The first item in the Custom Counters
           is the Link Status statistic.  This statistic will be 0
           if the link is active, 1 if it is not.  
        -  Physically change the link status of the first card of the 
           system by removing or inserting a "live" cable, then examine
           the link status to determine if it has changed.  If not,
           repeat the operation with the other cards in the system
           until you find the one that affects the Link Status
           statistic.
        -  Press <ESC> to return to the Available Lan Drivers list, and
           note the slot number of this adapter.
        -  Repeat this operation with the other adapters in the list.

*  Third-party trademarks are the property of their respective owners.