----------------------------------------------------------------------------- Installing the NetWare 3/4 ODI Server Driver on NetWare 3 Servers ----------------------------------------------------------------------------- This \NOVELL\SRVODI\3_1X subdirectory contains the following files: README.TXT - This file. MSM31X.NLM - Novell Media Support Module for NetWare 3 and NetWare SFT III 3.11 servers (v2.50). LSLENH.NLM - Novell Link Support Layer (LSL) chaining and filtering enhancement module (v1.01) that is loaded on NetWare 3.11 servers prior to loading MSM31X.NLM. PATCHMAN.NLM - Novell Patch Manager for NetWare 3.11 servers (v2.30). Required for LSLENH.NLM. ***TRADEMARKS*** Novell, NetWare, and LAN WorkPlace are registered trademarks and NetWare Loadable Module, NLM, NetWare MultiProtocol Router, and NetWare SFT are trademarks of Novell, Incorporated. Section 1 INSTALLING THE NETWARE 3/4 ODI SERVER DRIVER ON NETWARE 3 -------------------------------------------------------------------- You can install and use the NetWare 3/4 ODI server driver on NetWare 3 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 3 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 either a DOS partition (Step IIA.) or a NetWare partition (Step IIB.) of your NetWare server hard disk. NOTE The LSLENH.NLM patch should only be installed and loaded on NetWare 3.11 servers. NetWare 3.12 does not require this patch. A. To copy the files to a DOS partition, enter the following commands: 1. If installing on either NetWare 3.11 or NetWare 3.12: COPY A:\NOVELL\SRVODI\3C79X.LAN C:\ COPY A:\NOVELL\SRVODI\FDDITSM.NLM C:\ COPY A:\NOVELL\SRVODI\3_1X\MSM31X.NLM C:\ 2. If installing on NetWare 3.11 only, copy the following additional files: COPY A:\NOVELL\SRVODI\3_1X\LSLENH.NLM C:\ COPY A:\NOVELL\SRVODI\3_1X\PATCHMAN.NLM C:\ You may substitute C:\ with another DOS partition and subdirectory. B. To copy the files to a NetWare partition, you need to use the NetWare 3.x Command Processor (NWSHELL). Contact Novell for information on acquiring NWSHELL.NLM. Once you have NWSHELL.NLM, perform the following steps to copy the files: 1. Load the NetWare 3.x Command Processor (NWSHELL.NLM) by entering the following command at the server System Console prompt: :LOAD NWSHELL 2. Change to the SYS:SYSTEM directory by entering the following command: CD SYS:SYSTEM 3. Copy the driver files to the current directory by entering the following commands: a. If installing on either NetWare 3.11 or NetWare 3.12: COPY A:\NOVELL\SRVODI\3C79X.LAN COPY A:\NOVELL\SRVODI\FDDITSM.NLM COPY A:\NOVELL\SRVODI\3_1X\MSM31X.NLM b. If installing on NetWare 3.11 only, copy the following additional files: COPY A:\NOVELL\SRVODI\3_1X\LSLENH.NLM COPY A:\NOVELL\SRVODI\3_1X\PATCHMAN.NLM 4. Enter "exit" to log out of the session then press any key to return to the System Console prompt. III. Perform substeps IIIA. and IIIB. to configure the NetWare 3 server to use the 3Com 3C79x FDDILink PCI NetWare 3/4 ODI server driver. A. With the NetWare 3 server running, edit the STARTUP.NCF file using the INSTALL Program. 1. From the System Console, load INSTALL: :LOAD INSTALL 2. Select "System Options." 3. Select "Edit STARTUP.NCF file." 4. Add the following SET parameter to set the proper FDDI packet size. a. If installing on NetWare 3.11: set maximum physical receive packet size = 4202 b. If installing on NetWare 3.12: set maximum physical receive packet size = 4500 NOTE By default, the maximum physical receive packet size on NetWare 3.11 is 4202. Novell created a static patch for NetWare 3.11 called MPRPSFIX.EXE which modifies SERVER.EXE to increase the maximum packet size to 24K. This patch is currently available through NetWire in the 311PTD.ZIP file and is recommended when using the 3Com 3C79x FDDILink PCI on a NetWare 3.11 server running Novell's NetWare Multiprotocol Router (MPR) product. If the MPRPSFIX patch is used, it is recommended that the maximum physical receive packet size be set to 4500 or greater to allow maximum size FDDI frames to be sent, received, and (through MPR) routed. NetWare 3.12 has a maximum packet size of 24K by default, so no patch is necessary. The driver will, however, load properly for all packet size settings, and adjust the advertised maximum packet size accordingly. 5. Save the file with the changes. Answer "Yes" to the exit prompt. B. You can automatically load the server driver by adding the appropriate instructions to the AUTOEXEC.NCF file. You can also issue these commands directly from the System Console. 1. While still in the INSTALL program, select "Edit AUTOEXEC.NCF file." Add the following lines to AUTOEXEC.NCF 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 3Com 3C79x FDDILink PCI 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. If you installed the driver files on NetWare 3.12 using Step IIA1., enter the following commands: LOAD C:\3C79X pcicard=1 frame=FDDI_SNAP BIND IPX TO 3C79X net=00000001 b. If you installed the driver files on NetWare 3.11 using Steps IIA1. and IIA2., enter the following commands: LOAD C:\LSLENH LOAD C:\3C79X pcicard=1 frame=FDDI_SNAP BIND IPX TO 3C79X net=00000001 c. If you installed the driver files on NetWare 3.12 using Step IIB3a., enter the following commands: LOAD 3C79X pcicard=1 frame=FDDI_SNAP BIND IPX TO 3C79X net=00000001 d. If you installed the driver files on NetWare 3.11 using Steps IIB3a. and IIB3b., enter the following commands: LOAD LSLENH LOAD 3C79X pcicard=1 frame=FDDI_SNAP BIND IPX TO 3C79X net=00000001 A drive path is not included for the load statements in the third and fourth examples. This is because the 3C79X.LAN driver files are copied to the SYS:SYSTEM directory, which is the NetWare 3.1X default server path. In the above examples, note that LSLENH.NLM is only loaded under NetWare 3.11. Also, note that PATCHMAN.NLM is auto-loaded when loading LSLENH.NLM. Similarly, loading 3C79X.LAN auto-loads FDDITSM.NLM which in turn auto-loads MSM31X.NLM. This allows for fewer load statements in the AUTOEXEC.NCF file and less opportunity for driver load errors. NOTE Before saving the AUTOEXEC.NCF file, it is important to verify that no older NetWare 3 server drivers are loaded prior to loading LSLENH.NLM and/or MSM31X.NLM. Even though older NetWare 3 server drivers do not require the LSLENH patch or MSM31X, unexpected behavior may result if LSLENH or MSM31X are loaded after the driver. If using both older NetWare 3 and newer NetWare 3/4 server drivers, be sure to load LSLENH.NLM and MSM31X.NLM separately before loading any drivers. e. Save the file with the changes. Answer "Yes" to the exit prompt. IV. Shut down the server by entering "DOWN" at the system console and then enter "EXIT" 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: SERVER The changes made to the STARTUP.NCF and AUTOEXEC.NCF files 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.