----------------------------------------------------------------------------- Installing the NetWare 3/4 ODI Server Driver on NetWare SFT III 3.11 Servers ----------------------------------------------------------------------------- This \NOVELL\SRVODI\SFT3 subdirectory contains the following files: README.TXT - This file. LSLENH3.NLM - Novell Link Support Layer (LSL) chaining and filtering enhancement module (v3.00) that is loaded on NetWare SFT III 3.11 servers prior to loading MSM31X.NLM. PM311IO.NLM - Novell Patch Manager for NetWare SFT III 3.11 IOEngine (v1.01). Required for LSLENH3.NLM. ***TRADEMARKS*** Novell, NetWare, and LAN WorkPlace are registered trademarks and NetWare Loadable Module, NLM, and NetWare SFT are trademarks of Novell, Incorporated. Section 1 INSTALLING THE NETWARE 3/4 ODI SERVER DRIVER ON NETWARE SFT III -------------------------------------------------------------------------- You can install and use the NetWare 3/4 ODI server driver on NetWare SFT III 3.11 file servers by loading some operating system patches and driver support files in addition to the driver. To install the NetWare 3/4 ODI server driver on a NetWare SFT III 3.11 file server, perform the following six steps: I. Verify that the FDDI network interface card (NIC) is properly configured and installed. Refer to your user's guide for instructions. II. Copy the NetWare 3/4 ODI server driver files to a DOS partition of your NetWare server hard disk. To copy the files to a DOS partition, enter the following commands: COPY A:\NOVELL\SRVODI\3C79X.LAN C:\ COPY A:\NOVELL\SRVODI\FDDITSM.NLM C:\ COPY A:\NOVELL\SRVODI\3_1X\MSM31X.NLM C:\ COPY A:\NOVELL\SRVODI\SFT3\LSLENH3.NLM C:\ COPY A:\NOVELL\SRVODI\SFT3\PM311IO.NLM C:\ You may substitute C:\ with another DOS partition and subdirectory. III. Perform substeps IIIA. and IIIB. to configure the NetWare SFT III 3.11 server to use the 3Com 3C79x FDDILink PCI NetWare 3/4 ODI server driver. A. With the NetWare SFT III 3.11 server MSEngine running, edit the IOSTART.NCF file using the INSTALL Program. 1. From the MSEngine, load INSTALL: :LOAD INSTALL 2. Select "System Options." 3. From "Available System Options", select the IOSTART.NCF option for the appropriate IOEngine. 4. Add the following SET parameter to set the proper FDDI packet size. Set maximum physical receive packet size = 4500 NOTE By setting the maximum physical receive packet size to 4500 (or greater) the controller is able to send and receive the maximum FDDI frame size, increasing controller performance during file transfers and other large packet transactions. The driver will, however, load properly for all packet size settings, and adjust the advertised maximum packet size accordingly. B. You can automatically load the server driver by adding the appropriate instructions to the IOSTART.NCF file. You can also issue these commands directly from the IOEngine. 1. While still editing the IOSTART.NCF file, add the following lines to automatically load and bind the new driver every time the server is brought up: NOTE The "pcicard," "frame," and "net" values given below are examples. The pcicard number is the instance or index of the controller in the PCI computer if there are multiple FDDI controllers adapters installed. If there is only one adapter installed, use the default value of 1 for this parameter. The frame type is either of the two supported frame types "FDDI_SNAP" or "FDDI_802.2". Read Section 2, HINTS ON SELECTING PROPER FDDI FRAME TYPE, in this file for more information on choosing the frame type. The net address is the external network address. Refer to the Novell NetWare documentation on "Bind" for more information. a. Substituting C:\ with the DOS partition and subdirectory used in Step II, enter the following commands: LOAD C:\PM311IO LOAD C:\LSLENH3 LOAD C:\3C79X pcicard=1 frame=FDDI_SNAP BIND IPX TO 3C79X net=00000001 NOTE Before saving the IOSTART.NCF file, it is important to verify that no older NetWare 3 server drivers are loaded prior to loading LSLENH3.NLM and/or MSM31X.NLM. Even though older NetWare 3 server drivers do not require the LSLENH3 patch or MSM31X, unexpected behavior may result if LSLENH3 or MSM31X are loaded after the driver. If using both older NetWare 3 and newer NetWare 3/4 server drivers, be sure to load LSLENH3.NLM and MSM31X.NLM separately before loading any drivers. b. Save the file with the changes. Answer "Yes" to the exit prompt. IV. Shut down the server by entering "DOWN" at the MSEngine and then enter "EXIT" from the IOEngine to return to the DOS prompt. V. Follow the instructions in Chapter 2 of your user's guide for connecting the controller to the FDDI network. VI. Restart the server with the 3Com 3C79x FDDILink PCI server driver. Enter the following command at the DOS prompt: MSERVER The changes made to the IOSTART.NCF file in step III above take effect. Section 2 HINTS ON SELECTING PROPER FDDI FRAME TYPE ---------------------------------------------------- It is important to specify the correct FDDI frame type to interoperate with Novell NetWare clients. If the DOS clients use FDDI_SNAP or ETHERNET_II frame types, configure the driver to use FDDI_SNAP frame type. If the clients use FDDI_802.2 or ETHERNET_802.2 frame types, configure the driver to use FDDI_802.2 frame type. For Appletalk clients using the ETHERNET_SNAP frame type, configure the driver to use FDDI_SNAP. NetWare 3/4 ODI server drivers for FDDI do not support connections to clients using the ETHERNET_802.3 frame type, unless the frames are translated into proper FDDI_SNAP or FDDI_802.2 frames. To allow client connections from all supported frame types, you can load the server driver twice, once for each frame type. You must bind a protocol for each instance. See the NetWare documentation for information on how to do this.