=================================================================== = Adaptec Duralink64 v5.2 LAN Software Drivers = = = = README for Novell NetWare = =================================================================== This is the readme document for the Duralink64 v5.2 LAN Software Drivers. The following information is available in this file: 1. Supported Hardware 2. Version History 3. Installation Instructions 4. Additional Notes 5. CD Driver Disk Structure 1. Supported Hardware The following network interface cards are supported by this driver set. DuraLAN Adapters Description ----------------- ----------------------------------------- ANA-69011TX 32-bit PCI Fast Ethernet Adapter ANA-62011TX 64-bit PCI Fast Ethernet Adapter ANA-62022 64-bit 2 port PCI Fast Ethernet Adapter ANA-62044 64-bit 4 port PCI Fast Ethernet Adapter ANA-64044 64-bit/66 MHz 4 port PCI Fast Ethernet Adapter ANA-62011LV 64-bit PCI Fast Ethernet Adapter ANA-64022LV 64-bit/66 MHz 2 port PCI Fast Ethernet Adapter ANA-64044LV 64-bit/66 MHz 4 port PCI Fast Ethernet Adapter 2. Version History (V5.2 December 2001) The following is a list of supported features: 2.1. Software/Hardware Features - Standalone (SA) - Failover (FO) - Port Aggregation (PA) - Fast EtherChannel (FEC) - Duralink64 Configuration GUI - Duralink64 Status GUI - Online Help for Configuration and Status GUI - Hotplug PCI (Requires Hotplug capable Server and Independent Hardware Vendor hotplug support modules) Hotplug is supported in NetWare 5.1 and 6.0 only. Refer to Novell's hotplug documentation. 2.2. Operating System Support NOTE: Support Packs can be found on Novell's Web Site http://support.novell.com. - NetWare v4.x: Support Pack 9 or higher must be installed before installing these drivers. - NetWare v5.0: Recommend Support Pack 6a or higher & OS5PT2A be installed before installing Duralink64 drivers. - NetWare v5.1: Recommend Support Pack 3 or higher be installed before installing Duralink64 drivers. - NetWare v6.0: Recommend to update to the latest service pack when avaliable from Novell support web site. 3. Installation Instructions This section describes basic installation procedures for a DuraLAN network adapter. Refer to the User's Guide for more details on this. Due to the necessary prior installation of the corresponding Support Pack 9 or higher for NetWare 4.11 and NetWare 4.2, fresh install of the operating system with this driver set is not possible. Due to resource issues during a fresh install of NetWare 5.x/6.0, only one instance of adptsf.lan should be loaded during new OS install. It is recommended to install all NICs after the operating system installation to avoid problems. 3.1. Installing the Duralink64 Driver when NetWare 4.x, 5.x, and 6.0 is Already Installed a. Insert the Duralink64 v5.2 CD Driver disk into the CDROM drive. b. For NetWare 4.x, type "load cdrom" on the System Console screen. For NetWare 5.x and above, just type "cdrom". c. To mount the cdrom volume, type "cd mount duralink64v52" in NetWare 4.x. Type " mount duralink64v52" in NetWare 5.x and above. d. To load the Duralink64 Configuration GUI, type "load duralink64v52:\nwserver\configsf" for NetWare 4.x and "duralink64v52:\nwserver\configsf" for NetWare 5.x and above. e. Use configsf to install and configure your DuraLAN NICs for either SA, FO, PA, or FEC. Installation Notes: - Remark out any adptsf.lan bindings in either Autoexec.ncf or Inetcfg (initsys) - In order to load the drivers, the following lines need to be in startup.ncf file: set minimum packet receive buffers = 2000 set maximum packet receive buffers = 10000 - If the server has difficulty loading the driver from the CD, it may be necesary to copy all driver files to a floppy disk and install from it. 3.2. Removing the Driver From NetWare 4.x, 5.x, and 6.0 - To remove the driver, load configsf and uninstall the driver. - If the CDROM is not mounted, refer to step 3.1. 4. Additional Notes The following is a list of FYIs related to the software and hardware of the DuraLAN Network Adapters: 4.1. Known/Unresolved or FYI Issues * NetWare Client32 driver does not support Client32 for Windows 3.1x, Windows 95, and Windows NT. * NetWare Client32 for DOS is supported. Include "iomap=1" on the LOAD line, otherwise a Page Fault may result when the driver is loaded. Also you will need to install the patch required for ODI 3.31 specification support (this patch is included in the Support Packs listed in Section 2). The driver used to support Client32 for DOS is located on the Adaptec Duralink64 NetWare CDROM driver disk: d:\NWSERVER\ADPTSF.LAN (d: is the path of the CDROM drive) * To ensure that connections remain active for Client32, it is recommended that the NT registry be updated. The RETRY COUNT should be changed from 16 (default) to 255. Refer to the Duralink64 user guide for instructions. * During installation of multiple DuraLAN adapters in a NetWare Server, you must configure each port for each Failover pair you have installed. If you exit the Duralink64 Failover configuration utility "configsf" without configuring each pair of ports, you will need to re-enter protocol information regarding those Failover pairs. * During installation of multiple DuraLAN adapters in a NetWare Server, you must configure each port for each Port Aggregation group you have installed. If you exit the Duralink64 Port Aggregation configuration utility "configsf" without configuring each group of ports, you will need to re-enter protocol information regarding those Port Aggregation groups. * When fixed connection type is used, and there is a mismatch between the speed on the switch/hub port and NIC port, there is a problem in link detection even after the mismatch is corrected. This results in the Link Status for the mismatched port to be marked active even if the switch indicates the link is down. In addition, link state changes are ignored (e.g. removing a mismatched speed port's cable will not allow the port to failover to a backup port). To avoid this problem, use AutoDetect Connection type or correctly configure the port and switch/hub speeds and reboot the system with the NIC(s). * Spantree - changing spantree state from default "normal" to "fast" improves performance: - Cisco 5000 Series Switches with FO, PA, and FEC. Failure to correctly configure the "spantree portfast" feature on the Cisco 5000 series switch ports may result in dropped clients. Switch ports connected to the server using Duralink64 FO, PA, and FEC must have the feature "spantree portfast" enabled. When a port with the feature "spantree portfast" enabled is connected, the port immediately enters the spanning-tree forwarding state rather than going through the normal spanning-tree states such as listening and learning. Ports in a Port Aggregation or Failover group must not go through the listening and learning states. Use the set command under Command Reference in the Catalyst 5000 Series Hardware and Software Documentation. Within the set commands there will be a set spantree portfast command. The full command line is: "set spantree portfast mod_num/port_num {enable | disable}" - Other Switches: By default, most switches have Spantree defaulted to "normal" mode. If you are running FO, PA, or FEC, set the spantree mode from "normal" to "fast" state. * Hotplug Support - Important Notes: Before Hotplug or Hot replacement of a DuraLAN NIC, the following modules has to be unloaded: Configsf.nlm, Duralink.nlm, Status.nlm, and Adptsf.lan. If you are Hotplugging or Hot Replacement of a NIC which is in a FO, PA, or FEC group. The whole group must be unloaded before Hotplug or Hotreplacement can be performed; ie., adptsf.lan must be unloaded first before running ncmcon.nlm. - The Duralink64 driver supports Hotplug/Hot Replacement functionality. Two sets of modules are required for Hotplug/Replacement to work. First set is the Hotplug modules provided by Novell 5.x/6.0 and the other set is the Hotplug modules provided by the IHV (Independant Hardware Vendor) system vendor. For latest Novell hotplug modules, go to www.novell.com. For IHV Hotplug modules, go to appropriate IHV webstie for latest updates. Refer to Novell users manual for Hotplug modules and support. - SA (Standalone) Mode: In standalone mode using Novell Configuration Manger Console (NCMCON.NLM), follow the GUI onscreen options to Hotplug/Hot-Replace the ANA-6x0xx NIC. This works in both modes: One, let Netware plug and play automatically load adptsf; or two, press escape to load the NIC bindings manually (ie, loading sys:\etc\configsf.ncf manually or user defined NCF file.). - FO (Failover) Mode: In Failover mode using Hotplug/Hot-Replacement. On the Duralink64 driver CD or diskette, load configsf and configure failover then save and install the drivers to the NetWare server. Once this is done, configsf will create a configuration file on the Netware server called configsf.ncf (located on sys:\etc) which contains all the failover settings. Next, follow these steps: 1. On the server prompt unload status.nlm and duralink.nlm. If configsf GUI is running, exit the GUI. 2. On the server prompt unload adptsf (this will unload all drivers and groups for failover). 3. Launch ncmcon.nlm hotplug support module. 4. Select the ANA-6x0xx NIC to Hotplug/Hot-Replace and follow the onscreen GUIs. 5. Insert the new ANA-6x0xx in the same PCI Slot and press the PCI power switch (Switch, latch lever, or button used to power up the PCI slot). 6. NCM will prompt to ask if you want to power this slot, select YES. 7. Do not let NCM automatically load the NIC drivers, instead press ESCAPE to not load any NIC drivers. 8. Go to the server prompt and type "sys:\etc\configsf.nlm to load the Failover driver settings, this will contain all previous networking settings including TCP/IP, IPX number, name, network ID, bindings, and etc.... - PortAggregation/FEC (Fast EtherChannel) Mode: 1. Same procedures as Failover Mode. Notes: 1. To modify Failover, PortAgg, or FEC settings, launch configsf at the server prompt. 2. To manually unload Failover, PortAgg, or FEC, unload the following modules: status.nlm, duralink.nlm, and adptsf.nlm. Exit configsf.nlm if running. 3. Once the Failover drivers has been unloaded, to reload and restore the network configurations, type: "sys:\etc\configsf.ncf" on the server prompt. 4. You can create a batch file to unload the Failover, PortAgg/FEC drivers by using load edit (useful for hotplug purposes). 5. CD Driver Disk Structure 5.1. NetWare 4.x/5.x/6.0 Driver Diskette Structure \NETWARE.TXT - Readme Instructions and FYI notes. \NWSERVER\ADPTSF.LAN - DuraLAN NIC driver \NWSERVER\ADPTSF.LDI - DuraLAN install file \NWSERVER\CONFIGSF.NLM - Duralink64 Configuration Utility \NWSERVER\DURALINK.NLM - Duralink64 Sub Agent utility used by Configsf. \NWSERVER\STATUS.NLM - Duralink64 Status GUI for DuraLAN NICs. ------------------------------------------------------------------- (c) 2001 Adaptec, Inc. All Rights Reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, without prior written consent of Adaptec, Inc., 691 South Milpitas Blvd., Milpitas, CA 95035.Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.