IBM Netfinity Imbedded 10/100 Ethernet Adapter
                 and Adapter 2 Device Driver
                  Installation README File

This README file contains the latest information about installing
Windows 2000 ethernet device drivers for IBM Netfinity servers whose
imbedded ethernet controllers are compatible with the IBM Netfinity
10/100 Ethernet Adapter.

CONTENTS
________

1.0   Known Problems
2.0   Change History
3.0   Installation and Configuration
      3.1 Windows 2000
        3.1.1 Unattended Installation (Push)
      3.2 Advanced Features
        3.2.1 Adapter Fault Tolerance (AFT)
        3.2.2 Adaptive Load Balancing (ALB)
        3.2.3 Fast EtherChannel* (FEC)
        3.2.4 Virtual LAN (VLAN)
        3.2.5 Wake on LAN (WOL)
          3.2.5.1 Troubleshooting Wake on LAN
        3.2.6 Boot Agent
          3.2.6.1 Parameters
          3.2.6.2 Troubleshooting Boot Agent
        3.2.7 DMI and SNMP Software Support
        3.2.8 Priority Packet
          3.2.8.1 IEEE 802.1p tagging
          3.2.8.2 Priority Queuing
4.0   Web Sites and Support Phone Number
5.0   Trademarks and Notices
6.0   Disclaimer

1.0   Known Problems
____________________

o  None

2.0  Change History
_____________________

Changes made in this diskette, version 3.7.2c:

o  None (first release)

3.0   Installation and Configuration
____________________________________

3.1   Windows 2000
------------------

Location of driver:    \WIN2000\IBMFENT5.SYS

When Windows 2000 installs, Windows automatically installs a driver
for the adapter from its own library of drivers.  However, you should
still install the driver that is included on this diskette to ensure
you have the complete set of features for the controller.  You can
install this driver manually using the following instructions:

To update the driver for the adapter:

1.  From the Control Panel, double-click the System icon, select
    the Hardware tab, and click the Device Manager button.
2.  Select "Network Adapters" and right-click on the appropriate
    adapter listing to display its menu.  Then click
    the Properties menu option.
3.  From the Properties dialog box, click the Driver tab and
    click the Update Driver button.  The Update Device Driver
    Wizard appears.  Click Next.
4.  At the prompt "What do you want the wizard to do?", select
    the "Search for a suitable driver for my device" radio button,
    and click Next.
5.  Select the appropriate media checkbox and click Next.
6.  Select the "Install one of the other drivers" check box and
    click Next.
7.  Select the driver on this diskette and click Next.
8.  Restart your computer.

After restarting Windows, connect to your network by double-clicking
the My Network Places icon on the desktop.


3.1.1  Windows 2000 Unattended Install (Push)
---------------------------------------------

The main objective of the Push Installation is to get the client
properly connected to the distribution server before the installation
begins using the NDIS2 driver, and to keep the same client connected
using the NDIS5 driver after the Windows 2000 system is installed
without any end user action. A distribution server is any system
capable of being accessed from the network that contains the
Windows 2000 distribution folder (the I386 directory and supporting
files).

The main steps of the process are:

1. Create a Network Installation Startup disk from a Windows NT 4.0
   Server and modify it for your adapter.

2. Create a shared directory for the Windows 2000 Workstation
   Installation files on a distribution Server.

3. Modify the UNATTEND.TXT installation script to automate the
   procedure and add the proper adapter installation and
   configuration information.

4. Integrate the adapter driver files into the Windows 2000 installation
   source files.

5. Perform the Unattended Setup booting with the prepared setup disk
   from the client system.

The Procedure:

1) Prepare a distribution server:

   a)  Create a folder on the server's hard disk for the installation
       files (e.g., "PUSHW2K").  Make this folder shared (e.g., with
       shared name "PUSHW2K").

   b)  Create a user (e.g., "USERID" with a password "password") and
       granted read and view rights for the PUSHW2K folder.

2) Use a CD-ROM drive at the distribution server and copy the files
   from the i386 folder with Windows 2000 installation files to the
   shared folder PUSHW2K on this server (e.g., using Explorer).

3) Create / Modify the installation answer file UNATTEND.TXT as
   required by your specific system and desired Windows 2000
   configurations.  A sample UNATTEND.TXT file with comments is
   included in the \UNATTEND directory of this diskette. Microsoft
   also includes a sample UNATTEND.TXT in the I386 directory.

   Specify the full path to the UNATTEND.TXT file in the batch file
   for the WINNT command (see Step 6(L) below).

4) Create the \IBMFE directory:    PUSHW2K\$OEM$\Drivers\Net\IBMFE.

5) Copy driver installation files:

   Xcopy the files from this diskette to the proper place under
   Adapter Device Driver folder (PUSHW2K\$OEM$\Drivers\Net\IBMFE
   on the distribution server).  This enables the installation
   program to find the same file structure as on the Drivers disk.
   Be sure to use the /s /e switches on xcopy.

   Then copy Unattend.txt from the \UNATTEND directory of this
   diskette into the shared directory Z:\PUSHW2K.  Make sure that
   Unattend.txt has got the latest changes you made for customizing
   the push installation.

6) Prepare a Microsoft Client Installation disk using the Windows NT
   Network Client Administrator from a Windows NT 4.0 Server:

   a)  Prepare a bootable diskette (e.g., DOS 6.22: format a: /s).

   b)  Use the Windows NT Administrative Tools (Common), start
       Network Client Administrator and choose "Make Network
       Installation Startup Disk".

   c)  Set "Existing Path" to use the previously installed software
       for MS Client or, if it is the first time, create the shared
       directory on the server's hard drive, using the Windows NT 4.0
       Server CD-ROM as a source (e.g., by copying from \client on
       the CD-ROM to c:\client).

   d)  Choose "Network Client v3.0 for MS-DOS and Windows".

   e)  Choose any of the Network Adapters from the list
       (e.g., NE2000 compatible).

   f)  Set Computer name, User name, Domain and Network protocol when
       prompted.

   g)  Select OK and wait while files are copied to the disk.

   h)  Copy the proper ndis2 dos driver (IBMFE.DOS) to this disk in
       the \NET directory.  IBMFE.DOS can be found in the \UNATTEND
       directory of this diskette.

   i)  Modify A:\NET\SYSTEM.INI :  netcard = IBMFE.DOS

   j)  Modify A:\NET\PROTOCOL.INI :  drivername = IBMFE$

   k)  Add a line: CACHEFLUSH = 1
       just after the "drivername = IBMFE$" line.

   l)  Verify or modify A:\AUTOEXEC.BAT to have the following
       commands:

       NET USE W: \\PST\PUSHW2K
       W:\WINNT /s:W:\ /u:W:\unattend.txt

       Note that W is an example for the logical drive mapped to
       the share on the Windows NT server with computer name PST
       in this example.

   m)  Remove the invocation of setup.exe from A:\AUTOEXEC.BAT.

7) Boot up your DOS client with the disk prepared above installed.
   After connecting to the network:

   a)  Input "USERID" as a User name when prompted.

   b)  Input "password" as a password when prompted.

                OR

   c)  Modify the NET START line in the AUTOEXEC.BAT to

   NET LOGON USERID PASSWORD /YES



Sample Templates:

1) PROTOCOL.INI

[network.setup]
version=0x3110
netcard=ms$ne2clone,1,MS$NE2CLONE,1
transport=ms$ndishlp,MS$NDISHLP
transport=ms$netbeui,MS$NETBEUI
lana0=ms$ne2clone,1,ms$netbeui
lana1=ms$ne2clone,1,ms$ndishlp

[ms$ne2clone]
drivername = IBMFE$
CACHEFLUSH = 1
; CACHEFLUSH line is required ONLY IF NDIS2 does not shut down
; properly

;INTERRUPT=3
;IOBASE=0x300
;SlotNumber=1

[protman]
drivername=PROTMAN$
PRIORITY=MS$NDISHLP

[MS$NDISHLP]
drivername=ndishlp$
BINDINGS=ms$ne2clone

[ms$netbeui]
drivername=netbeui$
SESSIONS=10
NCBS=12
BINDINGS=ms$ne2clone
LANABASE=0

2. SYSTEM.INI

[network]
filesharing=no
printsharing=no
autologon=yes
computername=COMPUTERNAME
lanroot=A:\NET
username=Administrator
workgroup=DOMAIN
reconnect=no
directhost=no
dospophotkey=N
lmlogon=0
logondomain=DOMAIN
preferredredir=full
autostart=full
maxconnections=8

[network drivers]
netcard=IBMFE.DOS
transport=ndishlp.sys,*netbeui
devdir=A:\NET
LoadRMDrivers=yes

[Password Lists]
*Shares=a:\net\Share000.PWL
USERID=A:\NET\USERID.PWL

3. AUTOEXEC.BAT

path=a:\net
a:\net\net start
rem a:\net\net logon userid password /yes
net use W: \\PST\PUSHW2K
W:
winnt /s:W:\ /u:W:\unattend.txt


REFERENCES:

1. Microsoft Windows 2000 Unattended Setup Mode Parameters Guide
2. Microsoft Windows NT Resource Kit - Microsoft Press 19NT
3. Microsoft TechNet CD-ROM, April 1997
4. Microsoft support web page at http://support.microsoft.com/support
   Article ID : Q155197, Q156795


3.2 Advanced Features
---------------------

3.2.1 Adapter Fault Tolerance (AFT)
-----------------------------------

Adapter Fault Tolerance creates a team of 2 - 8 controllers
to provide automatic redundancy for your ethernet connection. If
the primary controller adapter fails, a secondary takes over enabling
you to maintain uninterrupted network performance.

AFT is implemented with a primary controller and one or more backup,
or secondary, controllers. These ethernet controllers can be the
imbedded controller(s) in your server or IBM Server Adapters. During
normal operation, the backup will have transmit disabled. If the link
to the primary adapter fails, the link to the next backup
adapter automatically takes over.


3.2.2 Adaptive Load Balancing (ALB)
-----------------------------------

Adaptive Load Balancing creates a team of 2 - 8 controllers to
increase transmission throughput.  With ALB, as you add adapters to
your server, you can group them in teams to provide up to a 800 Mbps
transmit rate and a 100 Mbps receive rate, with a maximum of eight
controllers. The ALB software continuously analyzes transmit loading
on each adapter and balances the transmission across the adapters as
needed. Adapter teams configured for ALB also provide the benefits of
AFT described in the preceeding paragraph.  Receive rates remain at
100 Mbps.

To use ALB, you must have two to eight compatible network controllers
installed in your server and all linked to the same network
switch/segment.  ALB works with any 100BASE-TX switch.


3.2.3 Fast EtherChannel* (FEC)
------------------------------

Fast EtherChannel* creates a team of 2, 4, 6 or 8 controllers
to increase transmission and reception throughput.  FEC is a
performance technology developed by Cisco to increase your server's
throughput.  Unlike ALB, FEC can be configured to increase both
transmission and reception channels between your server and switch.
FEC works only with FEC-enabled Cisco switches such as the Catalyst
5000 series.  With FEC, as you add adapters to your server, you can
group them in teams, with a maximum of eight compatible controllers.
The FEC software continuously analyzes loading on each controller
and balances network traffic across the controllers as needed.
Adapter teams configured for FEC also provide the benefits of AFT.

To use FEC, you must have 2, 4, 6, or 8 compatible network
controllers installed in your server and all linked to the same
FEC-enabled Cisco switch. (Note that the switch must support more
than 4 controllers in FEC in order for more than 4 controllers to
work in FEC . Consult your switch documentation.)


3.2.4 Virtual LAN (VLAN)
------------------------

Virtual LAN is a logical grouping of network devices put
together as a LAN regardless of their physical grouping or collision
domains. VLANs let a user see and access only specified network
segments. This increases network performance and improves network
security.

VLANs offer the ability to group users and stations together into
logical work-groups. This can simplify network administration when
connecting clients to servers that are geographically dispersed
across the building, campus, or enterprise network.

Typically, VLANs consist of co-workers within the same department but
in different locations, groups of users running the same network
protocol, or a cross-functional team working on a joint project.
Joining workers with VLANs forms logical working groups.

Normally, VLANs are configured at the switch and any computer can be
a member of one VLAN per installed network adapter. The controller
in your IBM server supersedes this by communicating directly with a
switch, allowing multiple VLANs on a single adapter (up to 64 VLANs).

To set up VLAN membership, your adapter must be attached to a switch
with VLAN capability.

3.2.5 Wake on LAN (WOL)
-----------------------

NOTE: The information in this section applies only to servers which
      implement the WOL function.  Consult your server documentation.

The Wake on LAN (WOL) feature of the server allows it to be
powered-on remotely by a network management program. In some
operating systems, it can also wake the computer from suspend mode.
This is accomplished by sending a special type of data packet
containing the adapter's specific Ethernet address.  When the
computer is powered off, the ethernet controller continues to operate
by using standby power.

As long as AC power is available to the power supply, the controller
will draw standby power when the machine is powered off, allowing it
to "listen" to the network for a wake up packet.

3.2.5.1 Troubleshooting Wake on LAN
-----------------------------------

NOTE: The reception of a wake up packet will set the adapter to a
special state. This condition must be reset before the adapter will
accept another wake up packet and power-on the computer. The drivers
for this adapter are written to reset this condition when they load.
Once you have sent the computer a wake up packet and powered-on the
computer, you must let a driver load or it will no longer accept any
wake up packets.  The only other way of resetting this condition is
removing AC power from the computer for a short duration (~10 - 15
seconds). If the computer still will not power-on when a wake up
packet is sent, check the computer's BIOS for power settings.

If you are connected to a hub or switch, the link LED on the back of
the adapter should be on, even though computer power is off.  If the
link LED it is not on, try powering the computer on. If the LED now
lights, then the controller is not receiving power in standby mode.
If this is the case, the computer may need to be serviced.

If the link LED does not come on when the computer is powered-on, you
have not established link with your hub or switch. Check your cabling
or substitute it with a cable that has been verified to work
correctly.  Make sure your hub or switch is either 10baseT or
100baseTX and is powered-on and fully functional.

If everything listed above is correct and the computer will still not
respond to a wake up packet, your computer may need to be serviced.


3.2.6 Boot Agent
----------------

The Boot Agent is a utility program that is stored in a portion of
system BIOS, allowing the ethernet controller to remotely boot the
system from the network using either of 2 methods. The default method
is PXE, a remote boot procedure defined by the "Wired for Management"
specifications and used by powerful network management programs.  The
alternate method is RPL, an established industry standard
historically utilized for remote booting of diskless workstations
from network operating systems such as NetWare* and Windows NT*
Server.

Computers do not need to be Wake on LAN enabled to use this feature.

When the computer is first powered-on, the Boot Agent will execute
and display a message similar to the following, with the current
version number:

Initializing Boot Agent Version X.X
Press Ctrl+S to enter the Setup Program..

By default, this message will display for 2 seconds, then attempt to
boot from a local drive. If the attempt to boot from a local drive
fails, the agent will attempt to boot remotely.

To change the configuration of the Boot Agent, press the "Ctrl" key
and "S" key simultaneously during the time that this message is
displayed.  This will bring up the Boot Agent configuration screen.

NOTE: Depending on the current setup options, the "Press Ctrl+S"
message may not appear.  In this case the user can still press the
"Ctrl" and "S" keys to enter the Setup Program.

3.2.6.1 Parameters
------------------

There are 7 configurable parameters. Follow the on-screen
instructions to select, change and save the different parameters. The
different parameters are explained below, with the default parameter
listed first.

Boot Protocol
  Selections are PXE and RPL. Select PXE for use with Wired for
  Management compliant network management programs.  Select RPL for
  legacy style remote booting.

PnP/BEV Boot
  Selections are Disable and Enable. Select Disable to use the Boot
  Agent for remote boot operation. Select Enable if your computer
  BIOS has a BEV (Boot Entry Vector) capable remote boot program
  built in and you wish to use that remote boot agent instead of the
  IBM Boot Agent.

Default Boot
  Selections are Local and Network. If Local is selected, the Boot
  Agent will attempt to boot according to the boot sequence option
  (defined in the system BIOS setup) first, then attempt to boot from
  the network if local boot fails. If Network is selected, the Boot
  Agent will attempt to boot from the network first, regardless of
  the boot sequence option defined in system BIOS.

Local Boot
  Selections are Enable and Disable. If Enable is selected, the
  system will be able to boot from a local drive (floppy drive or
  hard drive). If disable is selected, the system will not be able to
  boot from a local drive. This will be true regardless of the
  Default Boot setting.

Prompt Time
  Selections are 2, 3, 5 and 8. The number represents the amount of
  time in seconds the "Initializing Boot Agent Version 2.2 - Press
  Ctrl+S to enter the Setup Program.." message is displayed every
  time the system is booted.

Setup Message
  Selections are Disable and Enable. If enabled, the message
  "Initializing Boot Agent Version 2.2 - Press Ctrl+S to enter the
  Setup Program.." will be displayed during boot up. If Disable is
  selected, only the message "Initializing Boot Agent Version 2.2"
  will appear. However, you will still be able to enter Ctrl+S to
  enter the setup program at that time.

Power Management
  The selections are ACPI and APM. ACPI should work in most
  computers.  In servers supporting Wake-on-LAN, the APM selection
  will pre-enable the Wake-on-LAN function of the adapter.  Set this
  selection to APM if you are having difficulty with remote wake up
  in computers that are compliant to the PCI 2.2 specification and
  are running an OS that is not ACPI (Advanced Control and Power
  Interface) aware.


3.2.6.2 Troubleshooting Boot Agent
----------------------------------

If you do not see a message similar to " Initializing Boot Agent
Version X.X" during the computer start-up, check the following:

In the system BIOS setup menu, select "Devices and I/O Ports".
Then check that the parameter "Planar Ethernet PXE/DHCP" option is
enabled.

When using an RPL remote boot with a plug-in adapter based on an
Intel 82557, 82558 or 82559 LAN controller chip, the boot agent may
try to remote boot using the controller built into your server
instead of the plug-in adapter. To avoid this, disable the built-in
controller in the computer BIOS settings.


3.2.7 DMI and SNMP Software Support
-----------------------------------

This adapter provides Desktop Management Interface 2.0 and SNMP
capability for your Management applications. Software for DMI and
SNMP is located on a separate diskette which is available from this
same site.


3.2.8 Priority Packet
---------------------

This adapter provides support for Priority Packet.  Software for
Priority Packet is located on a separate diskette which is available
from this same site.

Priority Packet is a program that adds IEEE 802.1p tagging (also
known as Traffic Class Expediting) and Priority Queue features to
adapters.

3.2.8.1 IEEE 802.1p tagging
---------------------------

IEEE 802.1p tagging (IEEE 802.1p) is a new IEEE standard for tagging,
or adding additional bytes of information to, packets with different
priority levels.  Tagging is a method of assigning different levels
of priority to data packets based on user defined Priority Filters.
This allows you to grant a greater share of available network
bandwidth to critical applications.  Packets are tagged with 4
additional bytes, which increase the packet size and indicate a
priority level. The addition of 4 bytes to the packet increases the
maximum Ethernet packet size from 1514 bytes to 1518 bytes. This
increase in maximum packet size imposes certain restrictions on the
use of this technology.

First, your interconnecting network infrastructure must support this
standard or you will realize no gain from tagging. Furthermore, many
LAN adapters, switches and routers that do not support 802.1p will
reject any packets over 1514 bytes. Check with the hardware vendor if
you are not sure if your network hardware will forward packets up to
1518 bytes in length.

Simple repeater type hubs (class I and II) will forward the tagged
packets, but no gain will be realized from tagging.

802.1p compliant hardware must be configured to remove the additional
4 bytes from the tagged packet before forwarding it to
internetworking hardware or end nodes that will reject packets over
1514 bytes in length or do not support 802.1p tagging.

If your network infrastructure does not support 802.1p tagging, set
IEEE 802.1p/802.1q tagging to "Disable" (the default setting) in the
adapter advanced properties. Priority queuing will still prioritize
packets based on your priority filter settings.

In systems equipped with more than one supported adapter, each
adapter must have IEEE 802.1p/802.1q tagging enabled separately.

Priority filters apply to all adapters in a system and cannot be
applied individually to adapters in multi-homed systems.

Tagging is currently not supported in conjunction with adapter
teaming features (Adapter Fault Tolerance, Adaptive Load Balancing
and Fast EtherChannel*).

3.2.8.2 Priority Queuing
------------------------

Priority queuing is a feature that creates a separate high priority
queue in addition to the existing queue. Data packets are entered
into these queues prior to being transmitted. The priority assigned
to a packet determines which queue it goes into. Packets with a
priority of 4-7 go into the high priority queue and are sent ahead of
packets in the normal queue. This feature does not modify the packet
contents and will work over legacy network equipment.

You can assign priorities based on network layer properties, such as
the Node address of the destination computer, the Ethernet type, or
by various properties of the TCP/IP and IPX protocol suites.


4.0   WEB Sites and Support Phone Number
________________________________________

IBM Support Web Site:
http://www.pc.ibm.com/support

IBM Marketing Netfinity Web Site:
http://www.pc.ibm.com/netfinity

If you have any questions about this update, or problems
applying the update go to the following Help Center World
Telephone Numbers URL:
http://www.pc.ibm.com/qtechinfo/YAST-3P2QLY.html.

5.0   Trademarks and Notices
____________________________


The following terms are trademarks of the IBM Corporation in the
United States or other countries or both:

IBM
OS/2
Netfinity

Microsoft, Windows NT, and Windows 2000 are trademarks or registered
trademarks of Microsoft Corporation.

Cisco and FastEtherchannel are trademarks or registered trademarks of
Cisco Systems, Inc.

Novell and NetWare are registered trademarks of Novell Corporation.

SCO is a registered trademark of Santa Cruz Operations.

Intel is a registered trademark of Intel Corporation.

Other company, product, and service names may be trademarks or service
marks of others.

6.0  Disclaimer
_______________

THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND.  IBM
DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING
WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR
PURPOSE AND MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS
DOCUMENT.  BY FURNISHING THIS DOCUMENT, IBM GRANTS NO LICENSES TO ANY
PATENTS OR COPYRIGHTS.

Note to U.S. Government Users -- Documentation related to restricted
rights -- Use, duplication or disclosure is subject to restrictions
set forth in GSA ADP Schedule Contract with IBM Corp.