![[Intel Navigation Header]](/CONTENT/PIX/HEADER.GIF)
TokenExpress(TM): Installing Multiple Adapters in a NetWare v3.11 Server
USING MULTIPLE TOKENEXPRESS MCA ADAPTERS IN A NETWARE 3.11 SERVER
These instructions apply to Release 5.0 of the software.
Symptom
The results of lab testing showing the multiple adapter capability of an
IBM PS/2 file server using NetWare 386 as the network operating system.
Test environment
IBM PS/2 Mod 65sx, 4mb memory, IBM PS/2 SCSI adapter, 4 Intel
TokenExpress 16/4 adapters, NetWare 386 v3.11, 4 IBM 8228 MAU's, 1 PS/2
Mod 50 workstation.
Testing demonstrates that up to 4 Intel TokenExpress 16/4 adapters can
be installed in a NetWare 386 server. It must be noted that no
performance evaluation is provided here. Memory and configurations may
need to be installed or modified to provide the best possible
performance.
The following outlines the hardware configuration for the computer and
the software configuration for the NOS.
IBM PS/2 Mod 65sx I/O Data Interrupt Cable
Rate
SLOT 1 Empty
SLOT 2 Intel Above Board Plus
SLOT 3 Intel TokenExpress 16/4 a20 16 11 STP
SLOT 4 Intel TokenExpress 16/4 a24 16 8 STP
SLOT 5 Intel TokenExpress 16/4 a50 16 9 STP
SLOT 6 Intel TokenExpress 16/4 a54 16 10 STP
SLOT 7 Empty
SLOT 8 IBM PS/2 SCSI
Note: The order in which the drivers for the TokenExpress adapters
are loaded is described below. Follow this example to load the drivers
correctly.
NetWare 386 v3.11 AUTOEXEC.ncf file
FILE SERVER NAME =
IPX INTERNAL NETWORK NUMBER =
LOAD NMAGENT
LOAD OCTOK161 SLOT=3 PORT=A20 FRAME=TOKEN-RING NAME=LAN_A
LOAD OCTOK161 SLOT=4 PORT=A24 FRAME=TOKEN-RING NAME=LAN_B
LOAD OCTOK161 SLOT=5 PORT=A50 FRAME=TOKEN-RING NAME=LAN_C
LOAD OCTOK161 SLOT=6 PORT=A54 FRAME=TOKEN-RING NAME=LAN_D
BIND IPX TO LAN_A NET=300
BIND IPX TO LAN_B NET=301
BIND IPX TO LAN_C NET=302
BIND IPX TO LAN_D NET=303
LOAD INSTALL
LOAD MONITOR
TRACK ON
Trademark information