V2.1a NetWare 4.2, 5.x Device Drivers Disk for 10/100 EtherLink Server Adapter by 3Com (3C98x Family) ========================================================= CONTENTS -------- 1.0 Overview 1.1 Limitations 2.0 Change History 3.0 Build and Installation Instructions 4.0 Configuration Information 4.1 Driver Parameters 4.2 Additional Configuration Information 5.0 Web Sites and Support Phone Number 6.0 Trademarks and Notices 7.0 License and Disclaimer 1.0 Overview _____________ This package includes NetWare driver version 2.01D for NetWare 4.2 and 5.x for the 10/100 EtherLink Server Adapter by 3Com PN 09N9901 and other adapters in the 3C98x family. 1.1 Limitations _________________ Service Pack 6 or higher is required to support the driver in NetWare 4.2. Service Pack 2 or higher is required if hardware checksumming is enabled in NetWare 5.0. If you are using NetWare 4.x and NetWare 5.0, you should load ODINEB.NLM before loading the driver otherwise the server may abend. This problem is fixed in NetWare 5.1. If you are using the DynamicAccess Advanced Features, i.e., SE.NLM, you should not use NWIP or the server will abend. The driver requires 200 packet receive buffers for each installed NIC. You must increase the minimum and maximum packet receive buffers values by 200 for each installed NIC. For example, if you install two NICs, increase the parameters in the STARTUP.NCF file by 400 as follows: Before installing NICs SET MINIMUM PACKET RECEIVE BUFFERS = 1000 SET MAXIMUM PACKET RECEIVE BUFFERS = 2500 After installing two NICs SET MINIMUM PACKET RECEIVE BUFFERS = 1400 SET MAXIMUM PACKET RECEIVE BUFFERS = 2900 2.0 Change History ____________________ This new v2.1a sw release replaces the current v2.0b sw release. v2.1a 3C980.LAN 2.01D v2.0b 3C980.LAN 2.00 3.0 Build and Installation Instructions _________________________________________ With NetWare installed and the server up and running, complete the following steps to install and configure the driver and DynamicAccess technology server features on a NetWare file server. Driver Installation: 1. Enter this command at the prompt: NetWare 4.2: load install NetWare 5.x: load nwconfig 2. In the "Configuration Options" screen, select 'Driver options'. 3. In the "Driver Options" screen, select 'Configure network drivers'. 4. In the "Additional Driver Actions" screen, select 'Select a driver'. The "Select a Driver" screen appears, listing all previously saved drivers in the system. NOTE: If this is the first installation of the 3Com server NIC driver, it does not appear in this list 5. Press 'Insert'. A system message for selecting a disk drive appears. 6. Press 'F3'. 7. Enter a path to the volume that contains the driver. For example: a:/nwserver The Select a Driver to Install screen appears with the 3Com EtherLink Server NIC driver name highlighted. 8. Press 'Enter' to select the driver. 9. Select 'Yes' at the prompt to confirm the name of the driver to copy. The installation program copies the driver to the appropriate server subdirectory. The "Configuration" screen appears. NOTE: Steps 10 - 11 are not required if installing a single NIC. 10. In the "Configuration" screen, select 'Slot Number'. 11. Enter the slot number of the NIC that you want to install. For example: 10001 12. Select 'Save parameters and load driver'. The installation program loads the configured driver and then writes the appropriate LOAD and BIND commands to the AUTOEXEC.NCF file. The system assigns a network number. 13. Enter a network number, or press 'Enter' to select the system-assigned number. If no errors are encountered, the installation program asks whether you want to select an additional network driver. 14. Select 'Yes' if you want to set up another NIC. 15. Follow the prompts for another NIC. 16. Repeat the process for all NICs to be set up. 17. After all NICs are set up, press 'Esc' several times to return to the "Installation Options" screen. Installing Server Features: Two drivers are associated with DynamicAccess technology server features under NetWare: SE and LBRSL. 1. From the "Configuration Options" screen select 'Product options'. 2. Select 'Install a product not listed'. 3. Press 'F3' to specify a different path. 4. Enter this path: a:\nwserver 5. Press 'Enter' to install the DynamicAccess technology server features. 4.0 Configuration Information _______________________________ Please refer to instructions below for configuring groups in NetWare. If further details are needed, please see the userguide.pdf available from this web site or from the software CD. 1. Enter this command at the prompt: NetWare 4.2: load install NetWare 5.x: load nwconfig 2. In the "Configuration Options" screen, select 'NCF files options (create/edit server startup files)'. 3. Select 'Edit AUTOEXEC.NCF file'. 4. Make the following changes to the AUTOEXEC.NCF file: - Add a command to load the SE and LBRSL drivers before any commands to load LAN drivers. For example: load se load lbrsl - Add or verify the LOAD commands for the LAN drivers for all slot-frame instances. - For each Load Balancing/RSL group, load the same protocols and frame types on the primary and all secondary NICs. - On the primary NIC only, bind a protocol to each slot-frame instance. - Remove any protocol BIND commands from each secondary NIC. - For each group, add an LBRSL GROUP command to group the primary and secondary NICs together. There can be only one LBRSL GROUP command per group, and it must list the primary and all secondary NICs. Place this command after the LAN driver. To specify a load balancing group with resilient server links, use the LB option. To specify a resilient server link group without load balancing, use the RSL option. 5. Save the AUTOEXEC.NCF file and return to the server prompt. The sample AUTOEXEC.NCF file below shows a group of two NICs. The primary NIC in slot 10001 is bound to a secondary NIC in slot 10002. Example of Autoexec.NCF ======================== load se load lbrsl ;Define primary NIC slot-frame instances load 3c980 slot=10001 frame=ethernet_802.2 name=p1_802.2 load 3c980 slot=10001 frame=ethernet_ii name=p1_ii ;Define secondary NIC slot-frame instances load 3c980 slot=10002 frame=ethernet_802.2 name=p2_802.2 load 3c980 slot=10002 frame=ethernet_ii name=p2_ii ;Bind protocols to primary NIC bind ipx to p1_802.2 net=FF02 bind ip to p1_ii address=192.1.1.1 mask=ff.ff.ff.00 ;Create a group with NIC 10001 primary and NIC 10002 secondary lbrsl group lb 10001 10002 ;To create a resilient server link group without load balancing (for ;use with NICs from manufacturers other than 3Com) use the rsl option: ;lbrsl group rsl 10001 10002 4.1 Driver Parameters _____________________ Refer to 4.0 above. 4.2 Additional Configuration Information ________________________________________ Refer to 4.0 above. 5.0 WEB Sites and Support Phone Number ________________________________________ IBM Support Web Site: http://www.ibm.com/pc/support IBM Marketing Netfinity Web Site: http://www.ibm.com/pc/netfinity ( or eServer xSeries ) If you have any questions about this update, or problems applying the update go to the following Help Center World Telephone Numbers URL: http://www.ibm.com/pc/qtechinfo/YAST-3P2QLY.html. 6.0 Trademarks and Notices ____________________________ The following terms are trademarks of the IBM Corporation in the United States or other countries or both: IBM Netfinity eServer xSeries 3Com, DynamicAccess, EtherLink, and EtherDisk are register trademarks of 3Com Corporation. Other company, product, and service names may be trademarks or service marks of others. 7.0 License and Disclaimer ___________________________ Copyright (c) 1999-2000, IBM Corporation All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. Neither the name of IBM Corporation nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.