---------------------------------------------------------------------------- Digital Equipment Corporation ATMworks 351 NetWare ODI Server Driver V1.00 Release Notes ---------------------------------------------------------------------------- DIGITAL ATMworks 351 NetWare ODI Server Driver (v1.00) ---------------------------------------------------------------- - The driver has not been NetWare certified. - There are three drivers in the Novell subdirectory of the ATMworks 351 distribution media. There are three locations on the web page for the Novell drivers. The drivers all have the name, DGLPA.LAN. Novell NetWare 4.x, ODI 3.3 driver: Nw41xo33\novell\srvodi\dglpa.lan This driver conforms to v3.3 of the Novell ODI specification, September 29, 1995. This driver supports NetWare 4.x servers. The following versions of the NetWare ODI V3.3 files have been used on NetWare 4.1 with the ATMworks 351 driver: NBI.NLM v1.49 8/30/96 MSM.NLM v3.18 8/22/96 ETHERTSM.NLM v3.11 7/03/96 Novell NetWare 3.12, ODI 3.3 driver: Nw312o33\novell\srvodi\dglpa.lan This driver conforms to v3.3 of the Novell ODI specification, September 29, 1995. This driver is slightly different from the 4.x driver due to the idiosyncracies of NetWare 3.12. This driver must switch stacks when called by NetWare. The stack usage by the common ATM code and the ATM signaling code causes stack overflows if the driver is called with a small stack. Use the NetWare modules from the landr9 patch kit (or later) that support the ODI v3.3 specification. Either rename msm31x.nlm and nib31x.nlm to msm.nlm and nbi.nlm respectively to allow the ATMworks 351 driver to autoload those modules, or make sure that msm31x.nlm and nbi31x.nlm are loaded before loading the ATMworks 351 driver. The following versions of the NetWare ODI V3.3 files have been used on NetWare 3.12 with the ATMworks 351 driver: NBI31X.NLM v1.49 8/30/96 MSM31X.NLM v3.18 8/22/96 ETHERTSM.NLM v3.11 7/03/96 Novell NetWare 3.12, ODI 3.2 driver: Nw312o32\novell\srvodi\dglpa.lan This driver conforms to v3.2 of the Novell ODI specification. Use the NetWare modules from the landr9 patch kit (or later) that support the ODI v3.2 specification. Either rename msm31x.nlm to msm.nlm to allow the ATMworks 351 driver to autoload this module, or make sure that msm31x.nlm is loaded before loading the ATMworks 351 driver. The following versions of the NetWare ODI V3.2 files have been used on NetWare 3.12 with the ATMworks 351 driver: MSM31X.NLM v2.50 11/23/94 ETHERTSM.NLM v2.55 4/18/95 - Please contact Novell to obtain the latest patches. All of the current patches for the NetWare server must be installed. A known problem exists when trying to map two memory regions or a memory region above 0xC8000000 on a NetWare 4.1 server. The following text is from the loader.exe patch description in the issue.txt file in the Novell patch file labeled 410pt6.exe. This patch is available for NetWare 4.1 only. UPDATE FOR LATEST PATCH KIT. 10) FIXED problems with GetSharedMemoryLinearAddress where it was having problems dealing with shared memory addresses above 0xC8000000 - note that this is used by RegisterHardwareOptions which many LAN drivers call. The problems are: 1 - not handling multiple regions in the same IOConfig structure - it would return overlapping logical addresses. 2 - The logical address it would return would always be 4K aligned even if the physical address wasn't. And 3 - If the region crossed N number of pages, but the size rounded up to the nearest page size was (N - 1) pages, it would not reserve enough space - sometimes causing a page fault and always not reserving enough space. Without applying this patch to replace the loader component of server.exe, the ATMworks 351 adapter memory will not be mapped correctly on all processors. As a result the ATMworks 351 driver will not load because it will be unable to map the PCI configuration space. NOTE: When you are installing NetWare 4.x for the first time, this patch will not be loaded. As a result, any attempt to install the ATMworks 351 driver will fail. Continue with the installation even if there are warnings indicating that you have not installed a network adapter. You can complete the installation without a network adapter. After you install the patches, install the ATMworks 351 driver as outlined in the \novell\srvodi\readme.txt file. - SDH/SONET parameter. For most installations in the U.S., use the default framing parameter, SONET. For European installations, you might need to add SDH to your command line parameter configuration file. During testing, we loaded the ATMworks 351 driver with the SDH parameter and it connected and functioned with a GIGAswitch/ATM system using SONET; no errors were detected. This might not be the case with all switches, so match the driver's framing with that of your switch. - The driver defaults to using 16 receive buffers. However, if you have loaded the driver on a slow server relative to your clients, or if the network is very busy, you might need to increase the number of receive buffers. Load the MONITOR.NLM and check the custom statistics: Receive small free slot fifo low, Receive small free slot fifo empty or Receive big free slot fifo low, Receive big free slot fifo empty. If any of these counters are above zero, you might want to increase the number of receive buffers specified in the configuration file. For more information about receive buffers and custom counters, please refer to the novell\srvodi\readme.txt file. - Due to the parsing format of the RCV_BUFS command line parameter, if an invalid value is entered NetWare does not call the driver's parameter action routine, instead it sets the value for this parameter to zero. The driver later detects that this paramter value is invalid and prints a console error which will show a zero value rather than the value you entered. The driver may be changed in a uture release to parse some of the parameters differently to avoid this abnormal behavior. - This driver uses a configuration file to obtain command line parameters. The configuration file name must include the '@' character. See the novell\srvodi\readme.txt file for additional information. NOTE: The configuration file must not contain any comments (such as those allowed in autoexec.ncf). - You can use INETCFG to modify the required parameters for loading the ATMworks 351 NetWare driver. If you make an error in the configuration file name and want to restore it to the default value @elan.cfg, INETCFG will not make the change. You can restore the configuration file name by deleting the value in the "Board Configuration" screen and then pressing the key. INETCFG will inform you that the configuration file name is required. Now you can enter the correct name such as @elan.cfg and when you exit the "Board Configuration" screen, INETCFG will prompt you to save the changes. Respond YES to update the LOAD command line parameter. Select the "View Configuration" menu item and then the "All INETCFG Commands" menu item to verify the load command line before exiting INETCFG. - Configuring your NetWare server involves the use of command line parameters. Many of these parameters can be verified by the driver. Other parameters, such as ATM addresses, cannot be verified except by checking for valid digits. If an invalid ATM address is entered for the LES or LECS, the ATM common code in the driver will attempt to use the addresses provided to contact the LES or LECS. If a timeout occurs, and the number of retries is exhausted, the well known LECS address is used to contact the LECS to obtain the LES ATM address. No notification is made to the NetWare specific portion of the driver so that this can be reported to the user. Use the MONITOR NetWare utility to check the custom counter LAN Emulation Availability for the ATMworks 351 adapter to determine whether the NetWare server managed to join the emulated LAN. If it has not joined, check Section 1.IV novell\srvodi\readme.txt file for additional parameters to verify. - The ATMworks 351 driver may not reconnect to the switch if the driver is running on your NetWare server and the switch reboots. The UNI version negotiation may not work correctly due to a difference in timing on each end. The result is a mismatch in UNI versions on the switch and the NetWare server. If the MONITOR utility shows that the ELAN is unavailable, and disconnecting and reconnecting the link at the server does not reestablish the connection to the switch, it will be necessary to unload and reload the driver. New Features ------------ This is the first release of the driver. Changes since the last release ------------------------------ This is the first release of the driver. Features not yet supported -------------------------- - Classical IP. - IP Switching. - More than one ATMworks 351 adapter on a PC. - More than one LEC and more than one LIS per ATMworks 351 adapter. - NetWare 4.11. Known Problems -------------- If the NetWare server has loaded the ATMworks 351 driver with the ethernet_802.3 frame type only, a Windows NT NetWare client configured to use the 802.3 Ethernet protocol is unable to map a drive on the server. However, if the ATMworks 351 NetWare driver is loaded with both the ethernet_802.3 and the ethernet_802.2 frame types on the server, the NT client is able to map a drive on the NetWare server. An ATM analyzer trace shows that the NT client resolves the NetWare server's MAC address. Why the mapping is not successful is yet to be determined. For now, configure the NT client IPX/SPX protocol to autodetect frame types and load both the ethernet_802.2 and ethernet_802.3 frame types on the NetWare server. ***TRADEMARKS*** ATMworks, DIGITAL, and GIGAswitch are trademarks of Digital Equipment Corporation. Microsoft, MS, and MS-DOS are registered trademarks and Windows and Windows NT are trademarks of Microsoft Corporation. Novell and NetWare are registered trademarks, and NetWare Loadable Module and NLM are trademarks of Novell, Incorporated.