home *** CD-ROM | disk | FTP | other *** search
- This text file explains how to install the ODI server driver on this
- diskette into a Netware 3.11 server. Since the Netware installation program
- does not have driver import capability, the starting point for this process
- is assumed to be after the Netware server software is already installed, but
- not running yet. To install this server driver into a Netware 3.11 server,
- either use the INSTALL program on this diskette or manually copy the files
- to the server's hard disk. To manually install the driver, do the following
- steps:
-
- First, copy the 3C5X9.LAN server driver file from the \NETWARE\SERVER
- subdirectory on this EtherDisk to the server hard disk.
-
- Next, copy *.NLM files from the \NETWARE\SERVER\3.11 subdirectory to same
- place the server driver was copied. Failure to copy and use these five NLM
- files instead of the NLM files that came with the 3.11 version of Netware
- may result in network failure or server abends.
-
- Now boot the server, enter the installer, and edit the AUTOEXEC.NCF file
- to add the following line (assuming the server start directory is C:\SERVER,
- where the LAN drivers and NLM files were copied):
-
- LOAD C:\SERVER\LSLENH.NLM
- LOAD C:\SERVER\3C5X9.LAN PORT=<portnumber> SLOT=<slotnumber>
-
- Where <portnumber> is the hexadecimal base address of the EtherLink III ISA
- adapter, and <slotnumber> is the slot number containing a 3C579 EISA
- adapter, a 3C529 Microchannel adapter, or a 3C509 EtherLink III configured
- for EISA. Either or both parameters may be used, depending on your
- particular configuration. The ODI server driver will first look for an
- EISA adapter in the slot number specified by <slotnumber>. If an adapter
- is not found, the LAN driver will then search for an ISA adapter configured
- at the I/O address specified in <portnumber>.
-
- If you use the Monitor utility (MONITOR.NLM), be sure to use the version
- supplied on the EtherDisk rather than the version that came with Netware
- 3.11. To invoke the Monitor, enter:
-
- load C:\SERVER\MONITOR
-
- To support more than one adapter in a server, change the AUTOEXEC.NCF file
- to the format shown below:
-
- load C:\SERVER\LSLENH.NLM
- load C:\SERVER\3C5X9.LAN PORT=<port1> NAME=<name1> FRAME=<frametype>
- load C:\SERVER\3C5X9.LAN SLOT=<slot1> NAME=<name2> FRAME=<frametype>
-
- where <port1> and <slot1> the adapters' base address for ISA or slot number
- for EISA or Microchannel and <name1> and <name2> are user specified names
- that you assign to distinguish the multiple adapters.
-
- The FRAME parameter is optional. The default frame type is Ethernet_802.2.
- If you want the ODI server driver to support more than one frame type, then
- both the unique NAME= and FRAME= parameters must be paired on each load
- driver line. The valid frame types are Ethernet_802.2, Ethernet_802.3,
- Ethernet_II, and Ethernet_SNAP.
-
- The protocol(s) must be bound to the specific driver configuration using
- the user-assigned unique names. The following example shows how this can be
- done. Assume the first adapter is ISA and the second adapter is EISA in an
- EISA computer:
-
- load C:\SERVER\LSLENH.NLM
- load C:\SERVER\3C5X9.LAN PORT=300 FRAME=Ethernet_802.3 NAME=ADPONE
- load C:\SERVER\3C5X9.LAN SLOT=4 FRAME=Ethernet_II NAME=ADPTWO
- bind IPXODI to ADPONE
- bind IP to ADPTWO
-
- The protocols used in this example require other parameters to work
- properly. Consult the appropriate Novell Netware manuals for details.
-
-
- %VER - Netware 3.11 Server installation release notes V4.21
-