---------------------------------------------------------------------------- Installing the NetWare 3/4 ODI Server Driver ---------------------------------------------------------------------------- This directory contains the following files: README.TXT - This file. DEFPA.LAN - Novell NetWare 3/4 ODI Server Driver for the DEC FDDIcontroller/PCI (v3.30). DEFPA.LDI - Driver installation file used by NetWare 4 installation utility (INSTALL.NLM) to install and configure the NetWare 3/4 ODI Server Driver in that environment. ODIDEFPA.INF - Installation file needed to install DEFPA.LAN driver under NetWare Client32 for Windows 95. NBI.NLM - NetWare Bus Interface Module for NetWare 4 servers (v1.49). MSM.NLM - Novell Multi-Processor Media Support Module for NetWare 4 servers (v3.18). FDDITSM.NLM - Novell FDDI Topology Specific Module for NetWare 3.12 and NetWare 4.10, and above servers (v3.11). DECLMA.NLM - Digital Local Management Application NetWare Loadable Module. This NLM runs on Novell NetWare 3 and 4 and communicates with DEFPA.LAN to manage the DEC FDDIcontroller/PCI. This directory contains the following subdirectory: \312 - Files for installing and configuring the NetWare 3/4 ODI Server Driver in NetWare 3.12 servers. Product Requirements: Oper. Sys. - Novell NetWare 4.10 with 410PTx.EXE and LANDRx.EXE installed, or later Novell NetWare 3.12 with 312PTx.EXE and LANDRx.EXE installed Novell NetWare Client32 for DOS and Windows 3.1x v2.1, or later Novell NetWare Client32 for Windows 95 v2.1, or later ***TRADEMARKS*** CompuServe is a registered trademark of CompuServe, Incorporated. DEC, Digital, and DECpc are trademarks of Digital Equipment Corporation. Novell, NetWare, and LAN WorkPlace are registered trademarks and NetWare Loadable Module, NLM, and NetWare SFT are trademarks of Novell, Incorporated. Windows is a trademark of Microsoft Corporation. Section 1 INSTALLING THE NETWARE 3/4 ODI SERVER DRIVER ------------------------------------------------------- You can install and use the NetWare 3/4 ODI server driver on NetWare 3.12, NetWare 4.10 and later servers. The installation procedures are different for each server. You can also install and use the NetWare 3/4 ODI server driver with NetWare Client32 for DOS and Windows 3.1x, and NetWare Client32 for Windows 95. To install the NetWare 3/4 ODI server driver on a NetWare 3.12 file server, follow the instructions in the README.TXT file located in the \312 directory. To install the NetWare 3/4 ODI server driver in a Client32 environment, follow the instructions in Section 2, INSTALLING THE NETWARE 3/4 ODI SERVER DRIVER UNDER CLIENT32. To install the NetWare 3/4 ODI server driver on a NetWare 4.10 or later file server, perform the following steps: I. Verify that the FDDI network interface card (NIC) is properly configured and installed. Refer to "DEC FDDIcontroller/PCI User Information" for instructions. II. The following patch file must be installed on NetWare 4.10 servers prior to using the new driver modules: 410PTx.EXE Where "x" is 6 or higher (410PT6.EXE or higher). This file can be obtained from the following places: Novell's anonymous FTP server at: ftp://ftp.novell.com/pub/updates/nwos/nw410/ Novell's WWW server at: http://support.novell.com/search and on CompuServe. III. The following patch file must be installed on NetWare 4.10 servers prior to using the new driver modules: LANDRx.EXE Where "x" is 9 or higher (LANDR9.EXE or higher). This file can be obtained from the following places: Novell's anonymous FTP server at: ftp://ftp.novell.com/pub/updates/nwos/nw410/ Novell's WWW server at: http://support.novell.com/search and on CompuServe. NOTE This driver kit includes the most current FDDITSM.NLM, MSM.NLM, and NBI.NLM modules available at the time the kit was built. These modules may equal, supercede, or be older than the modules provided by Novell in the current LANDRx.EXE patch kits. It is recommended that the user install the latest released versions of these modules unless otherwise indicated. IV. Perform the following steps to configure the server to allow the maximum FDDI frame size supported by the driver. A. With the NetWare 4 file server running, edit the STARTUP.NCF file using the INSTALL utility. 1. From the System Console, load INSTALL: :LOAD INSTALL 2. Select "Maintenance/Selective Install" then "NCF Files Options" under "Installation Options." 3. Select "Edit STARTUP.NCF file" and add the following SET parameter to set the proper FDDI packet size: set maximum physical receive packet size = 4500 NOTE NetWare 4 increased the maximum physical receive packet size from 4202 to 24K bytes. 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. 4. Save the file with the changes. Press the escape (ESC) key to return to the "Maintenance/Selective Install" menu. V. Perform the following steps to install the NetWare 3/4 ODI server driver to the server NetWare partition and to configure and load the driver: A. Install the driver files. 1. While at the "Maintenance/Selective Install" screen, select "LAN Driver Options" under "Installation Options." 2. Hit the Insert key to select the "Load a LAN driver not listed" option. 3. Place the DOS-format Distribution Diskette (Disk 1) into the server floppy drive then press RETURN to scan for NetWare 3/4 ODI server drivers. 4. When "DEC FDDIcontroller/PCI Novell NetWare Server Driver" appears, press RETURN and follow the instructions to install the driver files. B. From the "Driver DEFPA parameters" option screen, update the configurable options. 1. Enter the slot number for the DEC FDDIcontroller/PCI to be configured. The slot number is the physical slot number where the controller is installed or a unique number generated by NetWare. On PCI systems that adhere to PCI Specification Revision 2.1 or later, the slot number will be the actual slot number assigned by the vendor. On older systems, the physical slot number is not available, so NetWare will generate a unique number starting at 10000. You may wish to load the driver without specifying a slot parameter and select among the list presented on the System Console. This parameter is mandatory. 2. Enter an optional node address override in canonical-format. If you enter a node address override, that address is added to the driver configuration table and used as a source address on all transmitted frames for that controller. 3. Enter the number of host-based packet receive buffers to be pre-allocated by the driver. The default number is 8, and the valid range is 2-128. The DEC FDDIcontroller/PCI has 1 Megabyte of adapter memory, so the default is usually acceptable. If multiple option cards are installed, there may be a performance improvement by pre-allocating more buffers. 4. Enter the number of host-based packet transmit buffers (TCB's) to be pre-allocated by FDDITSM for this adapter. The default number is 32, and the valid range is 8-128. This number may be reduced to save memory resources. 5. Enter the requested target token rotation time. FDDI selects the target token rotation time during the claim process (eg. when an FDDI node has entered or left the ring). During this time, each FDDI node offers its requested TTRT (MACTReq MIB object) and the lowest bidder wins. Normally this parameter does NOT need to be modified from the default of 8ms. However, some installations may set this value arbitrarily high on end node stations so that the requested TTRT can be more easily managed from an FDDI concentrator or switch. For this reason, the range of 4-165ms. is supported with a default of 8. This parameter should only be modified by experienced FDDI network managers. 6. Enable/Disable Full-Duplex Mode. Digital FDDI adapters are in Full-Duplex (FDX) mode when the mode setting is enabled and the adapter is connected point-point with another similarly enabled FDDI adapter or the Digital GIGAswitch FDDI switch. FDX mode takes advantage of the point-point connection by removing the FDDI token and allowing simultaneous receive and transmit of packets. FDX mode will help reduce latency and may increase network throughput if the system is nearing the standard FDDI maximum throughput. 7. Edit the frame type by pressing the ENTER key when "FDDI 802.2" is highlighted. Use the ENTER and F3 keys to load either one or both of the supported FDDI frame types. If a frame type is not specified, the default frame type, FDDI_802.2, is used. Read Section 3, HINTS ON SELECTING PROPER FDDI FRAME TYPE, in this file for more information on choosing the frame type. 8. Press the F10 key to load the driver. If the driver does not load, use the Alt-Esc key sequence to switch to the System Console and view the driver load error message. 9. If the driver loaded successfully, the INSTALL utility asks whether IPX should be bound to the driver and prompts for a proper external IPX address. Follow the utility instructions to continue, then return to the "Installation Options" menu. 10. To save the configuration information, select "NCF Files Options" then "Create AUTOEXEC.NCF file" to add the driver LOAD and BIND statements to the AUTOEXEC.NCF file. The next time the server is restarted the driver loads and binds to IPX automatically. 11. Exit the INSTALL utility, DOWN the server, and return to the DOS prompt. VI. Follow the instructions in Chapter 2 of "DEC FDDIcontroller/PCI User Information" for connecting the controller to the FDDI network. VII. Restart the server with the NetWare 3/4 ODI server driver. Enter the following command at the DOS prompt: SERVER The changes made to the STARTUP.NCF and AUTOEXEC.NCF files, in steps IV-V above, take effect. Section 2 INSTALLING THE NETWARE 3/4 ODI SERVER DRIVER UNDER CLIENT32 ---------------------------------------------------------------------- You can install and use the NetWare 3/4 ODI server driver under NetWare Client32 for DOS and Windows 3.1x, and NetWare Client32 for Windows 95. To install the NetWare 3/4 ODI server driver under NetWare Client32 for DOS and Windows 3.1x, follow the directions provided by Novell for installing 32-bit ODI LAN drivers. To install the NetWare 3/4 ODI server driver under NetWare Client32 for Windows 95, perform the following steps: I. Verify that the NetWare Client32 files have been installed on your system. If not, they can be found on your NetWare server distribution or by downloading it from the Novell Product Support WWW site at http://support.novell.com/ II. Make sure the system is shutdown, then insert the network adapter in your system. III. Power up your system and boot Windows 95. During the boot of the operating system, Windows 95 will autodetect the new hardware you just installed and display a message. IV. Next, Windows 95 will request the driver that you wish to install. Select "Driver from disk provided by hardware manufacturer." and click on OK. V. When prompted, tell Windows 95 to copy manufacturer's files from: A:\NOVELL\SRVODI\ At this point Windows 95 should have copied ODIDEFPA.INF and DEFPA.LAN to the appropriate directories. VI. Windows 95 may ask for the location of the Windows 95 CD or floppy disks. Enter the proper path to your source media. VII. After all of the necessary files have been copied, a reboot may be requested by Windows 95. Click on YES to reboot the system and once the reboot is complete, the adapter will be operational. Section 3 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. Section 4 INSTALLING THE DIGITAL LOCAL MANAGEMENT APPLICATION -------------------------------------------------------------- Perform the following steps to install DEClma: I. Verify that the FDDI network interface card (NIC) is properly configured and installed. Refer to "DEC FDDIcontroller/PCI User Information" for instructions. II. Verify that the driver has been loaded and properly bound (steps IV-V in Section 1, INSTALLING THE NETWARE 3/4 ODI SERVER DRIVER). III. Copy the Digital Local Management Application (DEClma) to either a DOS partition (substep IIIA.) or a NetWare partition (substep IIIB.) of your NetWare 3/4 server hard disk. A. To copy the DEClma NetWare Loadable Module (DECLMA.NLM) to a DOS partition, enter the following command: COPY A:\NOVELL\SRVODI\DECLMA.NLM C:\ You may substitute C:\ with another DOS partition and subdirectory. B. To copy the DEClma NetWare Loadable Module (DECLMA.NLM) to a NetWare partition, perform the following steps: 1. From a DOS workstation, connect to the NetWare 3/4 server. 2. Log in as user SUPERVISOR. 3. Change to the SYS:SYSTEM directory by entering the following command: CD SYS:SYSTEM 4. Copy the DEClma NetWare Loadable Module to the current directory by entering the following command: COPY A:\NOVELL\SRVODI\DECLMA.NLM 5. Log out of the session. IV. Run the DEClma application. A. To run DEClma in interactive mode, enter one of the following commands: - If you installed DEClma using step IIIA., enter the following command at the system console: :LOAD C:\DECLMA - If you installed DEClma using step IIIB., enter the following command at the system console: :LOAD DECLMA A drive path is included at the load statement in the second example. This is because the DECLMA.NLM file is copied to the SYS:SYSTEM directory which is the NetWare 3/4 default server path. A screen should appear with a "DEClma>" prompt as the only line, indicating that the application is ready for user input. For detailed descriptions of the available commands, refer to "Digital Local Management Application User's Guide", located at A:\DECLMA\DECLMA.DOC on the DOS-format Distribution Diskette (Disk 1) that comes with your controller. B. To run DEClma in command-line mode, enter the LOAD C:\DECLMA command followed by the device id and the desired DEClma command (as shown in the following example): :LOAD C:\DECLMA 1 SHOW SMT "1" represents the device number of the controller in the server and "SHOW SMT" is the desired DEClma command. For detailed descriptions of the available commands, refer to "Digital Local Management Application User's Guide", located at A:\DECLMA\DECLMA.DOC on the DOS-format Distribution Diskette (Disk 1) that came with your controller. NOTE If the DECLMA.NLM file was copied to the SYS:SYSTEM directory (substep IIIB.), the load statement is simplified because the SYS:SYSTEM directory is the NetWare 3/4 default server path. The above example in substep IVB. then becomes: :LOAD DECLMA 1 SHOW SMT