home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Network Support Encyclopedia 96-1
/
novell-nsepro-1996-1-cd2.iso
/
download
/
netware
/
e100s.exe
/
NW312.TXT
< prev
next >
Wrap
Text File
|
1995-07-14
|
7KB
|
194 lines
Server: NetWare 3.12 server
NetWare 3.12 server driver installation notes
for Intel's EtherExpress(TM) PRO/100 adapter
=============================================
Location of driver: \NWSERVER\E100.LAN
Location of NLM's: \NWSERVER\NLM312
Sample load commands
====================
LOAD C:<PATH>\MSM31X
LOAD C:<PATH>\ETHERTSM
LOAD C:<PATH>\E100 SLOT=n FRAME=ETHERNET_802.2
BIND IPX TO E100 NET=xxxxxxxx
General instructions
====================
1. Install NetWare* 3.12 according to the NetWare 3.12
installation manual.
2. Load the following NLMs (located in the \NWSERVER\NLM312
directory):
MSM31X.NLM (06-28-94 v2.31)
ETHERTSM.NLM (06-28-94 v2.31)
Make sure you use these (or later) versions. Earlier versions
won't work properly.
If you can log in to the server, copy the driver to the SYSTEM
subdirectory. If you do this, you won't need to specify a
path on the load line. If you copy it to another directory,
make sure the LOAD statement includes the correct path.
3. Before starting the server, copy the E100.LAN driver from
the \NWSERVER directory on the Configuration and Driver disk
to the root directory of the hard drive of the server.
If you can log in to the server, copy the driver to the SYSTEM
subdirectory. If you do this, you won't need to specify a
path on the load line. If you copy it to another directory,
make sure the LOAD statement includes the correct path.
4. Start the server. At the server console issue the load and
bind statement(s) in this order:
LOAD C:<PATH>\MSM31X
LOAD C:<PATH>\ETHERTSM
LOAD C:<PATH>\E100 SLOT=x FRAME=ETHERNET_802.2
BIND IPX TO E100 NET=xxxxxxxx
Where:
SLOT=x specifies the EISA slot number or PCI device number.
Substitute x with the valid value for the adapter.
NET=xxxxxxxx is the unique network address for that LAN
segment.
If you have workstations using the 802.3 frame type, see
the section later in this document about using multiple frame
types on one adapter.
5. Add the load and bind statements you need to the server's
AUTOEXEC.NCF file so the EtherExpress(TM) PRO/100 adapter driver
loads automatically each time the server starts.
Hints and tips
==============
Installing multiple adapters
----------------------------
- If you have multiple adapters in a single server, each
adapter must have a different network number and SLOT
number. Also, you may want to name each adapter. For
example:
LOAD C:\E100 SLOT=3 NAME=LAN_A
BIND IPX TO LAN_A NET=222
LOAD C:\E100 SLOT=4 NAME=LAN_B
BIND IPX TO LAN_B NET=333
- If you have problems loading the driver on multiple adapters
and the initialization fails due to "Insufficient RCBs,"
increase the number of buffers allocated to the server.
Add the following to STARTUP.NCF:
SET MINIMUM PACKET RECEIVE BUFFERS = 100 (or larger)
SET MAXIMUM PACKET RECEIVE BUFFERS = 500 (or larger)
The MINIMUM value you specify must be at least 30 times
the number of EtherExpress PRO/100 adapters in the computer.
Recommended settings:
1-3 adapters: 100
4 adapters: 150
The MAXIMUM you can specify depends on the amount of memory
in the server, but it must be greater than the MINIMUM.
Installing one adapter with multiple frame types
------------------------------------------------
When binding multiple frame types to one adapter, enter a
LOAD and BIND statement for each frame type. Each LOAD
statement uses the same SLOT number, but each BIND statement
needs a unique network number. You must also include a name
on each load line to avoid being prompted for the board to
bind IPX to.
Example:
LOAD C:\E100 SLOT=3 FRAME=ETHERNET_802.3 NAME=LAN8023
BIND IPX TO LAN8023 NET=77777
LOAD C:\E100 SLOT=3 FRAME=ETHERNET_802.2 NAME=LAN8022
BIND IPX TO LAN8022 NET=88888
Optional LOAD line parameters
-----------------------------
SLOT: Specifies the slot number for EISA adapters. This is
optional for single adapter installations but required
for multiple adapters installations.
For PCI adapters, SLOT is derived from DEVICE LOCATION
and doesn't map to the physical location of the
adapter. Currently, the PCI specification doesn't
tell you how to determine which adapter corresponds
to a device number. One way to do this is to load the
driver from the command line. You'll be prompted with
valid device numbers for the adapter. Select one of
them.
Syntax: SLOT=n (n = 1,2,3,4,...).
SPEED: Specifies the speed the driver uses. If you don't
use this parameter, the driver automatically detects
the network speed. If no cable is attached, the driver
defaults to 100 Mbps.
If you use this parameter, the driver operates at the
specified speed instead of detecting network speed.
Syntax: SPEED=n (n = 10 or 100)
Default: none, the adapter automatically senses speed
THRESHOLD: Represents the threshold for transmits from
extender SRAM FIFO.
Syntax: THRESHOLD=n (n = number of 8 bytes). For
example, 16 represents 16x8 (or 128
bytes). In this case, the LAN controller
transmits after copying 128 bytes from the
host memory.
Default: 16
The maximum number that you can specify is 200
(200x8=1600 bytes).
NODE: Specifies a local node address unique to each adapter.
The first four digits of the address indicate who
assigned the address when the driver loads.
Syntax: NODE=00aa12345678
02aa => Locally administered address, 02 is set
by MSM
00aa => Typical Intel address (default)
BUSARCH: This parameter is required only if the system has
both EISA and PCI slots and an EtherExpress PRO/100
adapter is in both type of slots.
Syntax: BUSARCH=n (n = 2 for EISA, 1 for PCI)
FRAME: Indicates one of four valid frame types the
system is transmitting and receiving.
Syntax: FRAME n
n = Ethernet_802.2
Ethernet_802.3
Ethernet_II
Ethernet_SNAP
Default: Ethernet_802.2
* Third-party trademarks are the property of their respective owners.