Allied Telesis AT-2711FX Installation And User Manual

All rights reserved. No part of this publication may be reproduced without prior written permission from Allied Telesyn, Inc. Microsoft and Internet Explorer are registered trademarks of Microsoft Corporation. Netscape Navigator is a registered trademark of Netscape Communications Corporation. All other product names, company names, logos or other designations mentioned herein are trademarks or registered trademarks of their respective owners. Allied Telesyn, Inc. reserves the right to make changes in specifications and other information contained in this document without prior written notice. The information provided herein is subject to change without notice. In no event shall Allied Telesyn, Inc. be liable for any incidental, special, indirect, or consequential damages whatsoever, including but not limited to lost profits, arising out of or related to this manual or the information contained herein, even if Allied Telesyn, Inc. has been advised of, known, or should have known, the possibility of such damages.

This product meets the following standards. RFI Emissions FCC Class B, EN55022 Class B, VCCI Class B, C-TICK, CE Immunity EN55024 Electrical Safety EN60950 (TUV), UL 60950 (CULUS) Federal Communications Commission Interference Statement Declaration of Conformity Manufacturer Name: Allied Telesyn, Inc. Declares that the product: Fast Ethernet Adapter Model Numbers: AT-2711FX This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio or television reception. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one of the following measures: - Reorient or relocate the receiving antenna. - Increase the separation between the equipment and the receiver. - Connect the equipment into an outlet on a circuit different from that to which the receiver is connected. - Consult the dealer or an experienced radio/TV technician for help. This device complies with part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) This device must not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation. FCC Caution: Any changes or modifications not expressly approved by the party responsible for compliance could void the user’s authority to operate this equipment. Industry Canada This Class B digital apparatus meets all requirements of the Canadian Interference-Causing Equipment Regulations. Cet appareil numérique de la classe B respecte toutes les exigences du Règlement sur le matériel brouilleur du Canada. Laser Safety EN60825

Important: Appendix C contains translated safety statements for installing this equipment. When you see the , go to Appendix C for the translated safety statement in your language. Wichtig: Anhang C enthält übersetzte Sicherheitshinweise für die Installation dieses Geräts. Wenn Sie  sehen, schlagen Sie in Anhang C den übersetzten Sicherheitshinweis in Ihrer Sprache nach. Importante: El Apéndice C contiene mensajes de seguridad traducidos para la instalación de este equipo. Cuando vea el símbolo , vaya al Apéndice C para ver el mensaje de seguridad traducido a su idioma. Important : L'annexe C contient les instructions de sécurité relatives à l'installation de cet équipement. Lorsque vous voyez le symbole , reportez-vous à l'annexe C pour consulter la traduction de ces instructions dans votre langue. Importante: l’Appendice C contiene avvisi di sicurezza tradotti per l’installazione di questa apparecchiatura. Il simbolo , indica di consultare l’Appendice C per l’avviso di sicurezza nella propria lingua. Важно: Приложение C содержит переведенную инструкцию по безопасности при установке данного устройства. Если Вы встретите , перейдите к Приложению C для получения переведенной инструкции по безопасности.

Where to Find Web-based Guides .......................................................................................................................................15 Contacting Allied Telesyn .....................................................................................................................................................16 Online Support ..............................................................................................................................................................16 Email and Telephone Support.......................................................................................................................................16 Returning Products........................................................................................................................................................16 Sales or Corporate Information .....................................................................................................................................16 Management Software Updates....................................................................................................................................16 Chapter 1: Introduction to the Fast Ethernet Network Adapter ....................................................................................17 Functional Description ..........................................................................................................................................................18 Contents of Your Shipment ...........................................................................................................................................18 Features ...............................................................................................................................................................................19 Physical Description .............................................................................................................................................................20 Chapter 2: Installing the Hardware ..................................................................................................................................21 System Requirements ..........................................................................................................................................................22 Windows Requirements ................................................................................................................................................22 NetWare Requirements.................................................................................................................................................22 Linux Requirements ......................................................................................................................................................22 Reviewing Safety Precautions..............................................................................................................................................23 Pre-Installation Checklist ......................................................................................................................................................25 Installing a Network Adapter Card........................................................................................................................................26 Connecting the Network Cables ...........................................................................................................................................30 Chapter 3: Installing Windows Server 2003 and Windows XP Driver Software ...........................................................31 Installing the Driver Software................................................................................................................................................32 Using the Driver Installer ...............................................................................................................................................32 Updating the Adapter Software .....................................................................................................................................35 Updating the Windows 2003 Server or Windows XP Driver Software ...................................................................35 Modifying Configuration Properties.......................................................................................................................................41 802.1p QOS ..................................................................................................................................................................41 Checksum Offload.........................................................................................................................................................43 Ethernet Wire Speed .....................................................................................................................................................44 Flow Control ..................................................................................................................................................................44 Large Send Offload .......................................................................................................................................................45 Locally Administered Address .......................................................................................................................................46 Wake Up Capabilities ....................................................................................................................................................46 WOL Speed...................................................................................................................................................................47 Uninstalling the Driver Software ...........................................................................................................................................49 Chapter 4: Installing Windows 2000 Driver Software .....................................................................................................51 Installing the Windows 2000 Driver Software .......................................................................................................................52 Installing the Adapter Software .....................................................................................................................................52 Modifying Configuration Properties.......................................................................................................................................54 Configuring Driver Properties ........................................................................................................................................54 802.1p QOS ..................................................................................................................................................................55 Checksum Offload.........................................................................................................................................................56 Ethernet Wire Speed .....................................................................................................................................................57 Flow Control ..................................................................................................................................................................57 Contents

Speed & Duplex.............................................................................................................................................................59 Wake Up Capabilities ....................................................................................................................................................60 WOL Speed ...................................................................................................................................................................61 Updating the Driver Software................................................................................................................................................63 Removing the Driver Software..............................................................................................................................................64 Chapter 5: Installing the Linux Driver Software ..............................................................................................................67 Installing the Linux Driver Software ......................................................................................................................................68 Building a Driver from a TAR File ..................................................................................................................................68 Removing the tg3 Driver.........................................................................................................................................68 Network Installation...............................................................................................................................................................70 Removing the Linux Driver from a TAR Installation..............................................................................................................71 Module Parameters...............................................................................................................................................................72 Chapter 6: Installing the NetWare Driver Software .........................................................................................................77 Driver Installation ..................................................................................................................................................................78 Pre-Installation Requirements...............................................................................................................................................79 Installing Novell NetWare Server 5.x or 6.0 Driver Software ................................................................................................80 Verifying or Modifying Adapter Parameters ..........................................................................................................................82 Removing Drivers from Autoexec.ncf ...................................................................................................................................87 Chapter 7: Installing the Boot Agent Driver Software ....................................................................................................89 Overview...............................................................................................................................................................................90 Enabling and Disabling MBA .........................................................................................................................................90 Boot Method ...........................................................................................................................................................90 Setup BIOS ............................................................................................................................................................91 Server Setup.........................................................................................................................................................................92 Windows 2000 ...............................................................................................................................................................92 Windows Server 2003 and Windows XP .......................................................................................................................92 DOS UNDI/APITEST .....................................................................................................................................................92 Red Hat Linux................................................................................................................................................................92 Chapter 8: Installing the NDIS2 Driver Software .............................................................................................................95 Installing the NDIS2 Driver Software for Use on MS-DOS Platforms ...................................................................................96 Pre-Installation Requirements .......................................................................................................................................96 Modifying the Startup Disk.............................................................................................................................................96 Using Keywords for the B57.dos Drivers ............................................................................................................................101 Chapter 9: Troubleshooting ............................................................................................................................................103 Hardware Diagnostics.........................................................................................................................................................104 Checking the Port LED on the Adapter...............................................................................................................................105 Troubleshooting Checklist...................................................................................................................................................106 Verifying the Correct Drivers are Loaded............................................................................................................................107 NetWare ......................................................................................................................................................................107 Linux ............................................................................................................................................................................107 Testing Network Connectivity .............................................................................................................................................108 Windows ......................................................................................................................................................................108 NetWare ......................................................................................................................................................................109 Linux ............................................................................................................................................................................110 Software Problems and Solutions.......................................................................................................................................111 Microsoft Remote Installation Service (RIS) Instructions.............................................................................................111 Windows 2000 Image...........................................................................................................................................111 Windows XP Image ..............................................................................................................................................111 Linux ............................................................................................................................................................................111 Chapter 10: DOS Diagnostics .........................................................................................................................................113 Introduction .........................................................................................................................................................................114 Prerequisites................................................................................................................................................................114 DOS Prompt Commands ....................................................................................................................................................115 Diagnostic Tests .................................................................................................................................................................116 Test Names .................................................................................................................................................................116

7 Test Descriptions.........................................................................................................................................................117 Error Messages ..................................................................................................................................................................123 Chapter 11: Broadcom Advanced Control Suite 2 (BACS 2) Applications ................................................................127 Overview.............................................................................................................................................................................128 Information Provided by the BACS 2 Applications ......................................................................................................129 Installing the BACS 2 Application .......................................................................................................................................130 Installing and Using the GUI........................................................................................................................................130 Using Silent Installation ...............................................................................................................................................130 Managing the BACS Application ........................................................................................................................................132 Initializing the BACS 2 Application ..............................................................................................................................132 Updating the BACS Application...................................................................................................................................132 Removing the BACS Application.................................................................................................................................132 Configuring the BACS 2 Application...................................................................................................................................134 Vital Sign Tab ..............................................................................................................................................................134 Resources Tab ............................................................................................................................................................136 Hardware Tab..............................................................................................................................................................137 Advanced Tab .............................................................................................................................................................138 Network Test Tab ........................................................................................................................................................140 Diagnostics Tab...........................................................................................................................................................141 Cable Analysis Tab .....................................................................................................................................................143 Statistics Tab...............................................................................................................................................................143 General Statistics .................................................................................................................................................144 IEEE 802.3 Statistics............................................................................................................................................144 Custom Statistics .................................................................................................................................................145 Appendix A: Specifications ............................................................................................................................................147 Physical Specifications .......................................................................................................................................................147 Environmental Specifications..............................................................................................................................................147 Power Specifications ..........................................................................................................................................................147 Maximum Cabling Distances ..............................................................................................................................................148 Appendix B: Cleaning Fiber Optic Connectors ............................................................................................................149 Using a Cartridge-Type Cleaner.........................................................................................................................................150 Using a Swab .....................................................................................................................................................................152 Appendix C: Translated Safety Statements ..................................................................................................................155

Figure 2. Removing the PC Cover.......................................................................................................................................26 Figure 3. Removing the Faceplate From PCI Slot...............................................................................................................27 Figure 4. Inserting the Network Adapter Card .....................................................................................................................28 Figure 5. Securing the Adapter Card...................................................................................................................................29 Figure 6. Welcome to Found New Hardware Wizard Window.............................................................................................33 Figure 7. Found New Hardware Wizard Window.................................................................................................................34 Figure 8. System Properties Dialog Box..............................................................................................................................36 Figure 9. Hardware Tab.......................................................................................................................................................37 Figure 10. Device Manager Window....................................................................................................................................38 Figure 11. Welcome to Hardware Update Wizard Window .................................................................................................39 Figure 12. Hardware Update Wizard Window .....................................................................................................................39 Figure 13. Advanced Tab ....................................................................................................................................................42 Figure 14. Advanced Tab ....................................................................................................................................................55 Figure 15. Run Command Window....................................................................................................................................108 Figure 16. Command Window with pconfig/all displayed ..................................................................................................109 Figure 17. Command Window with ping displayed............................................................................................................109 Figure 18. Broadcom Advanced Control Suite 2 Window..................................................................................................129 Figure 19. Vital Sign Tab ...................................................................................................................................................134 Figure 20. Resources Tab .................................................................................................................................................136 Figure 21. Hardware Tab...................................................................................................................................................137 Figure 22. Advanced Tab ..................................................................................................................................................138 Figure 23. Network Test Tab .............................................................................................................................................141 Figure 24. Diagnostics Tab................................................................................................................................................142 Figure 25. Statistics Tab....................................................................................................................................................143 Figure 26. Ferrule in an SC Connector Plug......................................................................................................................149 Figure 27. Unclean and Clean Ferrule...............................................................................................................................149 Figure 28. Cartridge Cleaner .............................................................................................................................................150 Figure 29. Rubbing the Ferrule Tip on the Cleaning Surface ............................................................................................150 Figure 30. Lint-Free and Alcohol-Free Swabs...................................................................................................................152 Figure 31. Cleaning a Recessed Ferrule...........................................................................................................................152 Figures

Table 2. Fiber Optic Port 100 LED Status ..........................................................................................................................20 Table 3. 100BASE-FX Fiber Optic Cable Specifications ....................................................................................................30 Table 4. NetWare Support Files .........................................................................................................................................79 Table 5. Fiber Optic Port 100 LED Status ........................................................................................................................105 Table 6. Linux Driver Software Information ......................................................................................................................107 Table 7. DOS Diagnostics Prerequisites ..........................................................................................................................114 Table 8. DOS Prompt Commands ....................................................................................................................................115 Table 9. DMA Test Patterns .............................................................................................................................................119 Table 10. Default Register ................................................................................................................................................120 Table 11. BACS Application Information ..........................................................................................................................129 Tables

Ethernet adapter. In addition, procedures are provided that describe how to install and configure the software drivers. The Preface contains the following sections: ˆ “Safety Symbols Used in this Document” on page 14 ˆ “Where to Find Web-based Guides” on page 15 ˆ “Contacting Allied Telesyn” on page 16

This document uses the safety symbols defined in Table 1. Table 1. Safety Symbols Symbol Meaning Description Caution Performing or omitting a specific action may result in equipment damage or loss of data. Warning Performing or omitting a specific action may result in electrical shock.

15 Where to Find Web-based Guides The installation and user guides for all Allied Telesyn products are available in portable document format (PDF) on our web site at www.alliedtelesyn.com. You can view the documents online or download them onto a local workstation or server.

This section provides Allied Telesyn contact information for technical support as well as sales and corporate information. Online Support You can request technical support online by accessing the Allied Telesyn Knowledge Base: http://kb.alliedtelesyn.com. You can use the Knowledge Base to submit questions to our technical support staff and review answers to previously asked questions. Email and Telephone Support For Technical Support via email or telephone, refer to the Support & Services section of the Allied Telesyn web site: www.alliedtelesyn.com. Returning Products Products for return or repair must first be assigned a return materials authorization (RMA) number. A product sent to Allied Telesyn without an RMA number will be returned to the sender at the sender’s expense. To obtain an RMA number, contact Allied Telesyn Technical Support through our web site: www.alliedtelesyn.com. Sales or Corporate Information You can contact Allied Telesyn for sales or corporate information through our web site: www.alliedtelesyn.com. To find the contact information for your country, select Contact Us -> Worldwide Contacts. Management Software Updates New releases of management software for our managed products are available from either of the following Internet sites: ˆ Allied Telesyn web site: www.alliedtelesyn.com ˆ Allied Telesyn FTP server: ftp://ftp.alliedtelesyn.com If you prefer to download new software from the Allied Telesyn FTP server from your workstation’s command prompt, you will need FTP client software and you must log in to the server. Enter “anonymous” for the user name and your email address for the password.

Network Adapter This chapter provides an introduction to the Allied Telesyn AT-2711FX Fast Ethernet network adapter and contains the following sections: ˆ “Functional Description” on page 18 ˆ “Features” on page 19 ˆ “Physical Description” on page 20

18 Functional Description The adapter connects a PCI-E compliant server or workstation to a Fast Ethernet network using fiber optic cabling and a connector that meets 62.5/125 µm or 50/125 µm multimode specifications. This adapter operates at 100 Mbps full-duplex and half-duplex mode. The AT-2711FX Fast Ethernet network adapter is a PCI-Ex1 Express card and is available in three versions: ˆ AT-2711FX/SC adapter ˆ AT-2711FX/ST adapter ˆ AT-2711FX/MT adapter The adapter versions differ only in their connector type. The SC version adapters have an SC connector, as shown in Figure 1 on page 20, and the ST version adapters have an ST connector. The MT version has an MTRJ connector. The LEDs and software drivers are identical for all adapter models and versions. Contents of Your Shipment Included with your adapter are the following items: ˆ Antistatic bag (used for protecting the adapter when stored or shipped). Keep the adapter in its packaging until ready for installation. ˆ CD-ROM with AT-2711FX Fast Ethernet network adapter driver software and documentation. ˆ Low-profile bracket Inform your network supplier of any missing or damaged items. If you need to return the adapter, you must pack it in the original (or equivalent) packing material or the warranty will be voided. See “Returning Products” on page 16.

19 Features Following is a list of the AT-2711FX Fast Ethernet network adapter features: ˆ PCI-Express x1 interface ˆ Flow Control (IEEE 802.1x) ˆ Layer 2 Priority Encoding (802.1p) ˆ TCP checksum RX/TX support ˆ 72 KB packet buffer ˆ PXE remote root support ˆ Wake on LAN (WOL) ˆ Available with SC, ST, or MT-RJ multimode fiber connectors

20 Physical Description The faceplate on the AT-2711FX Fast Ethernet network adapter provides two fiber optic connectors for attaching the adapter to a compatible link partner. See Figure 1 for an illustration of the adapter’s faceplate. Figure 1. Adapter Faceplate The adapter has one LED as described in Table 1. Table 1. Fiber Optic Port 100 LED Status State Description Green The port is operating at 100 Mbps and has a valid link. Flashing The port is receiving or transmitting network packets at 100 Mbps. TX RX 100 ATI 998

This chapter contains the following sections: ˆ “System Requirements” on page 22 ˆ “Reviewing Safety Precautions” on page 23 ˆ “Pre-Installation Checklist” on page 25 ˆ “Installing a Network Adapter Card” on page 26 ˆ “Connecting the Network Cables” on page 30

22 System Requirements Before installing the AT-2711FX Fast Ethernet network adapter, make sure your system meets the requirements listed for your operating system. Windows Requirements The following lists the requirements for the Windows 2000, Windows XP SP2, and Windows Server 2003 systems: ˆ Pentium-based computer that meets Windows 2000, Windows XP SP2, or Windows Server 2003 software requirements ˆ One open PCI-Ex1 (Express) slot ˆ 128 MB RAM (minimum) ˆ Microsoft Windows 2000 Server, Microsoft Windows XP SP2, Microsoft Windows 2000 Advanced Server, or Microsoft Windows Datacenter (Windows 2000 only) ˆ Microsoft Windows Server 2003 Server, or Microsoft Windows Server 2003 Enterprise Server (Windows Server 2003 only) NetWare Requirements The following lists the requirements for NetWare: ˆ Pentium-based computer that meets Novell NetWare 5.1 and 6.0 software requirements ˆ One open PCI-Ex1 (Express) slot ˆ 64 MB RAM (minimum) ˆ Novell NetWare 5.1 and 6.0, with Support Pack 3 or the most recent NetWare 5 Support Pack You can get the appropriate updates from the Novell support website http:/ /www.novell.com/productupdate/patchlist.html. Linux Requirements The following lists the requirements for a Linux system: ˆ Pentium-based computer that meets Linux software requirements ˆ One open PCI-Ex1 (Express) slot with a 128 MB RAM (minimum)

23 Reviewing Safety Precautions Please review the following safety precautions before you begin to install the network adapter card. Refer to Appendix C, “Translated Safety Statements” on page 155 for translated safety statements in your language. Warning This is a “Class 1 LED product”.  1 Warning Do not stare into the laser beam.  2 Warning Warning: Do not look directly at the fiber optic cable ends or inspect the cable ends with an optical lens.  31 Warning Do not work on this equipment or cables during periods of lightning activity.  4 Warning Operating Temperature: This product is designed for a maximum ambient temperature of 40 degrees C.  9 Note All Countries: Install this product in accordance with local and National Electric Codes.  10 Warning The adapter is being installed in a system that operates with voltages that can be lethal. Before you remove the cover of your system, you must observe the following precautions to protect yourself and to prevent damage to the system components. - Remove any metallic objects or jewelry from your hands and wrists. - Make sure to use only insulated or nonconducting tools. - Verify that the system is powered OFF and unplugged before accessing internal components.

24 - Installation or removal of adapters must be performed in a static- free environment. The use of a properly grounded wrist strap or other personal antistatic devices and an antistatic mat is strongly recommended.

25 Pre-Installation Checklist 1. Check that your server meets the hardware and software requirements listed under “System Requirements” on page 22. 2. Verify that your system is using the latest BIOS. 3. Review the information in the readme.txt file on the CD-ROM for important information not available at the time this manual was created. Note If you acquired the adapter software on floppy disk or from the Allied Telesyn support website, enter the path to where the adapter driver files reside on your system. 4. If your system is active, shut it down. 5. When system shut down is complete, power OFF and unplug your system. 6. Holding the adapter card by the edges, remove it from its shipping package and place it on an antistatic surface. 7. Check the adapter for visible signs of damage, particularly on the card’s edge connector. Never attempt to install any damaged adapter. If the adapter is damaged, report it to Allied Telesyn. See “Contacting Allied Telesyn” on page 16.

26 Installing a Network Adapter Card The following instructions apply to installing the Fast Ethernet adapter in most systems. Refer to the manuals that were supplied with your system for details about performing these tasks on your particular system. To install the network adapter card, perform the following procedure: 1. Review the “Pre-Installation Checklist” on page 25 and “Reviewing Safety Precautions” on page 23. Before installing the adapter, ensure the system power is OFF and unplugged from the power outlet, and that proper electrical grounding procedures have been followed. Warning High voltage inside the system presents a safety hazard. Make sure the power is off before removing the cover. 2. Remove the system cover and select any empty PCI-E slot. See Figure 2. If you do not know how to identify a PCI-E slot, refer to your system documentation. Figure 2. Removing the PC Cover

27 3. Select an empty, non-shared PCI-E slot and remove the faceplate. Keep the faceplate in a safe place. You may need it for future use. See Figure 3. Figure 3. Removing the Faceplate From PCI Slot Note If you cannot locate or know how to find an PCI-E slot, refer to the documentation that came with your system. 4. Remove the network adapter card from the shipping package and store the packaging material in a safe location. Caution Wear a grounding device and observe electrostatic discharge precautions when installing the network adapter card in a system. Failure to observe this caution could result in damage to the card. 5. Applying even pressure at both corners of the card, push the adapter card until it is firmly seated in the PCI-E slot.

28 Make sure the card is securely seated. See Figure 4. Figure 4. Inserting the Network Adapter Card Caution Do not use excessive force when seating the card, as this may damage the system or the adapter. If the card resists seating, remove it from the system, realign it, and try again.

29 6. Secure the network adapter card to the chassis with a Phillips-head screw (not provided) as shown in Figure 5. Figure 5. Securing the Adapter Card 7. Replace the system’s cover and secure it with the screws removed in Step 2. 8. Disconnect any personal antistatic devices. 9. Power the system on. Note If you installed the adapter card in a Microsoft Windows 2003, WindowsXP, or Windows2000 system before installing the driver software, the Found New Hardware Wizard launches automatically. For more information, see Chapter 3, “Installing Windows Server 2003 and Windows XP Driver Software” on page 31 or Chapter 4, “Installing Windows 2000 Driver Software” on page 51. When the system returns to proper operation, the adapter hardware is fully installed. Next, connect the network cables. See “Connecting the Network Cables” on page 30.

30 Connecting the Network Cables To connect a network cable to the adapter, perform the following procedure: 1. Prepare a fiber optic cable according to the specifications in Table 2. Warning The fiber optic ports contain a Class 1 laser device. When the ports are disconnected, always cover them with the provided plug. Exposed ports may cause skin or eye damage. 2. Connect one end of the cable to the adapter. 3. Connect the other end of the cable to the appropriate Ethernet network port or fiber optic port. Note After the cable is properly connected at both ends, the adapter port LEDs should be functional. See Table 1 on page 20 for a description of adapter port LED operation. For driver installation and configuration instructions, refer to the software configuration for a specific driver. Table 2. 100BASE-FX Fiber Optic Cable Specifications Port Type Connector Media Maximum Distance 100BASE-FX Fiber Optic 50 µm multimode 2000 meters (6561.68 feet) 100BASE-FX Fiber Optic 62.5 µm multimode 2000 meters (6561.68 feet)

Windows XP Driver Software This chapter describes how to install the Windows 2003 and Windows XP driver software. It contains the following sections: ˆ “Installing the Driver Software” on page 32 ˆ “Modifying Configuration Properties” on page 41 ˆ “Uninstalling the Driver Software” on page 49

32 Installing the Driver Software When a Windows Server 2003 or Windows XP system first boots up after you install a new Allied Telesyn AT-2711FX Fast Ethernet network adapter, the system automatically detects the new hardware and prompts you to install the driver software for that device. Note The adapter must be physically installed in your system before installing the driver software. See Chapter 2, “Installing the Hardware” on page 21 for details. Note If the Windows Server 2003 or Windows XP system detects an adapter and installs a default driver, update the driver as described in “Updating the Adapter Software” on page 35. Note If there is an onboard Broadcom network interface, the native Broadcom driver may load. You can use this driver, or the latest driver supplied by Allied Telesyn. Using the Driver Installer To install the adapter software on a Windows Server 2003 or Windows XP system, do the following: Note Before beginning this procedure, verify that the Windows Server 2003 or Windows XP system has been upgraded to the latest version with the latest service pack applied. Note If you are installing in a standard Windows XP or Windows 2003 environment, use the driver in \xp_w2k_w3k\IA32. If you are installing in a Windows XP or Windows 2003 64-bit environment, use the driver in \xp_w2k_w3k\x64. When you boot up either system after installing the adapter card, a series of Found New Hardware windows are displayed. Note You must have Administrator privileges to install the driver software.

33 Note If you have a Windows XP system, the window in Figure 6 opens. Start with step 1. If you have a Windows Server 2003 system, the window in Figure 7 on page 34 opens. Start with step 2 on the same page. Figure 6. Welcome to Found New Hardware Wizard Window 4. Click No, not this time to copy the driver software from the CD-ROM. 5. Click Next.

34 The second Welcome to Found New Hardware Wizard Window is shown in Figure 7. Figure 7. Found New Hardware Wizard Window 6. Insert the CD-ROM or floppy diskette. 7. Click Install the Software Automatically (Recommended). 8. Click Next. 9. If you are prompted to specify the location of the CD-ROM, click Browse (do not use the text field) and locate the path. 10. When the software installation is complete, click Finish to close the wizard and complete the software installation.

35 Updating the Adapter Software This section provides a procedure for updating the adapter software for the Windows Server 2003 or Windows XP systems. Note You may need to reboot your system after completing the driver update to properly load the new drivers. When you update the adapter software on existing devices, the Advanced Property settings may not be updated unless the existing device is removed by following the instructions in “Uninstalling the Driver Software” on page 49. Then you must perform a scan for hardware changes in the device manager, followed by reinstalling the device with the current adapter software as described in “Installing the Driver Software” on page 32. Note Before uninstalling a device, capture all of the Advanced Property settings because the properties will be lost. Updating the Windows 2003 Server or Windows XP Driver Software To update the adapter software on a Windows Server 2003 or a Windows XP system, perform the following procedure. Note Update all adapters by repeating the following steps on each device. 1. Start either a Windows Server 2003 system or a Windows XP system and log in. You must have Administrator privileges to update the driver software. 2. On the desktop, right click My Computer. The My Computer window opens. 3. Select Properties from the menu.

36 The System Properties dialog box opens, as shown in Figure 8. Figure 8. System Properties Dialog Box 4. Select the Hardware Tab. The Hardware Tab is shown in Figure 9 on page 37.

37 Figure 9. Hardware Tab 5. Click Device Manager.

38 The Device Manager Window is shown in Figure 10. Figure 10. Device Manager Window 6. Insert the CD-ROM. 7. In the Device Manager window, click the + next to the Network Adapters folder. The selection expands to show the list of installed network adapter cards. 8. Right click on the adapter whose driver you want to update and select Update Driver.

39 The Hardware Update Wizard Window opens, as shown in Figure 11. Figure 11. Welcome to Hardware Update Wizard Window 9. For a Windows 2003 system, skip to step 10. For a Windows XP system, click No, not this time to copy the driver software from the CD-ROM. 10. Click Next. The Second New Found Hardware Wizard Window opens, as shown in Figure 12. Figure 12. Hardware Update Wizard Window 11. Click Install the Software Automatically (Recommended). 12. Click Next. 13. If you are prompted to specify the location of the CD-ROM, click Browse (do not use the text field) and locate the path.

40 After driver software installation is complete, you are ready to modify the configuration properties. See “Modifying Configuration Properties” on page 41.

41 Modifying Configuration Properties Although the default values should be appropriate in most cases, you can change any of the available options to meet the requirements of your specific system. After the adapter driver software has been installed, you can use this procedure to verify or change the following adapter properties: ˆ “802.1p QOS” on page 41 ˆ “Checksum Offload” on page 43 ˆ “Ethernet Wire Speed” on page 44 ˆ “Flow Control” on page 44 ˆ “Large Send Offload” on page 45 ˆ “Locally Administered Address” on page 46 ˆ “Wake Up Capabilities” on page 46 ˆ “WOL Speed” on page 47 Note The following steps may be slightly different if the "Classic Start Menu" is set. 802.1p QOS The 802.1p QOS property is a standard that enables Quality of Service (QOS). It is responsible for the QOS provisions on the local segment, and the avoidance of the "all packets are treated equally" issue, which falls onto the hub or switch servicing segment. 802.1p QOS provides prioritization of packets traversing a subnet. Thus, when the local segment becomes congested and the hub or switch workload results in the delay (dropping) of packets, those packets with flags that correspond to higher priorities receive preferential treatment and are serviced before packets with lower priorities. To enable or disable the 802.1p QOS property, perform the following procedure: 1. Start either a Windows Server 2003 system or a Windows XP system and log in. You must have Administrator privileges to update the driver software. 2. On the desktop, right click My Computer. The My Computer window opens. 3. Select Properties from the menu.

42 The System Properties dialog box opens, as shown in Figure 8 on page 36. 4. Click the Advanced tab. The Advanced tab is shown in Figure 13. Figure 13. Advanced Tab 5. From the Properties list, select 802.1p QOS. 6. From the Values list, select one of the following: ˆ Enable - Enables the 802.1p QOS property. ˆ Disable - Disables the 802.1p QOS property. This is the default. Note Enabling 802.1p QOS also requires an 802.1p aware switch. 7. Click OK. 8. If prompted to restart your computer, click Yes. Even though it is not necessary to reboot the system for new adapter properties to take effect, rebooting is recommended to reinitialize all registers.

43 9. Verify that the adapter port LEDs operate as described in “Physical Description” on page 20. Checksum Offload Usually, the Checksum Offload function is computed by the protocol stack. By selecting one of the Checksum Offload properties, the adapter can compute the checksum. To change the Checksum Offload setting, perform the following procedure: 1. Start either a Windows Server 2003 system or a Windows XP system and log in. You must have Administrator privileges to update the driver software. 2. On the desktop, right click My Computer. The My Computer window opens. 3. Select Properties from the menu. The System Properties dialog box opens, as shown in Figure 8 on page 36. 4. Click the Advanced tab. The Advanced tab is shown in Figure 13 on page 42. 5. From the Properties list, select Checksum Offload. 6. From the Values list, select one of the following: ˆ None - Disables checksum offloading. ˆ Rx TCP/IP Checksum - Enables receive TCP, IP, and UDP checksum offloading. ˆ Tx TCP/IP Checksum - Enables transmit TCP, IP, and UDP checksum offloading. ˆ Tx/Rx TCP/IP Checksum (default) - Enables transmit and receive TCP, IP, and UDP checksum offloading. 7. Click OK. 8. If prompted to restart your computer, click Yes. Even though it is not necessary to reboot the system for new adapter properties to take effect, rebooting is recommended to reinitialize all registers. 9. Verify that the adapter port LEDs operate as described in “Physical Description” on page 20.

44 Ethernet Wire Speed This feature is not supported on the AT-2711FX Fast Ethernet network adapter. Flow Control The Flow Control property allows you to enable or disable the receipt or transmission of PAUSE frames which enable the adapter and the switch to control the transmit rate. The side that is receiving the PAUSE frame momentarily stops transmitting. The recommended selection is Disable, which configures the adapter to ignore PAUSE frames. By default, the Flow Control property is disabled. To change the Flow Control property, perform the following procedure: 1. Start either a Windows Server 2003 system or a Windows XP system and log in. You must have Administrator privileges to update the driver software. 2. On the desktop, right click My Computer. The My Computer window opens. 3. Select Properties from the menu. The System Properties dialog box opens, as shown in Figure 8 on page 36. 4. Click the Advanced tab. The Advanced tab is shown in Figure 13 on page 42. 5. From the Properties list, select Flow Control. 6. From the Values list, select one of the following: ˆ Auto - (default) PAUSE frame receipt and transmission is optimized. ˆ Disable - PAUSE frame receipt and transmission is disabled (recommended). ˆ Rx PAUSE - PAUSE frame receipt is enabled. ˆ Rx/Tx PAUSE - PAUSE frame receipt and transmission is enabled. ˆ Tx PAUSE - PAUSE frame transmission is enabled. 7. Click OK. 8. If prompted to restart your computer, click Yes.

45 Even though it is not necessary to reboot the system for new adapter properties to take effect, rebooting is recommended to reinitialize all registers. 9. Verify that the adapter port LEDs operate as described in “Physical Description” on page 20. Large Send Offload Normally, the protocol stack performs TCP segmentation. When you enable the Large Send Offload property, the network adapter can do the TCP segmentation. To change the Large Send Offload property, perform the following procedure: 1. Start either a Windows Server 2003 system or a Windows XP system and log in. You must have Administrator privileges to update the driver software. 2. On the desktop, right click My Computer. The My Computer window opens. 3. Select Properties from the menu. The System Properties dialog box opens, as shown in Figure 8 on page 36. 4. Click the Advanced tab. The Advanced tab is shown in Figure 13 on page 42. 5. From the Properties list, select Large Send Offload. 6. From the Values list, select one of the following: ˆ Enable - Enables the Large Send Offload property. ˆ Disable - Disables the Large Send Offload property. This is the default. 7. Click OK. 8. If prompted to restart your computer, click Yes. Even though it is not necessary to reboot the system for new adapter properties to take effect, rebooting is recommended to reinitialize all registers. 9. Verify that the adapter port LEDs operate as described in “Physical Description” on page 20.

46 Locally Administered Address The Locally Administered Address is a user-defined address that is used in place of the MAC address originally assigned to the adapter. Every adapter in the network must have its own unique MAC address. This locally administered address consists of a 12-digit hexadecimal number. To change the Locally Administered Address property, perform the following procedure: 1. Start either a Windows Server 2003 system or a Windows XP system and log in. You must have Administrator privileges to update the driver software. 2. On the desktop, right click My Computer. The My Computer window opens. 3. Select Properties from the menu. The System Properties dialog box opens, as shown in Figure 8 on page 36. 4. Click the Advanced tab. The Advanced tab is shown in Figure 13 on page 42. 5. From the Properties list, select Locally Administered Address. 6. In the Values list enter the Locally Administered Address. ˆ The range is 0000 0000 0001 to FFFF FFFF FFFD. ˆ Do not use a multicast address (least significant bit of the high byte = 1). ˆ Do not use all 0's or all F's. 7. Click OK. 8. If prompted to restart your computer, click Yes. Even though it is not necessary to reboot the system for new adapter properties to take effect, rebooting is recommended to reinitialize all registers. 9. Verify that the adapter port LEDs operate as described in “Physical Description” on page 20. Wake Up Capabilities The Wake Up Capabilities property enables the network adapter to wake up from a low-power mode when it receives a network wake-up frame. Two types of wake-up frames are possible: Magic Packet and Wake Up Frame.

47 To change the Wake Up Capabilities property, perform the following procedure: 1. Start either a Windows Server 2003 system or a Windows XP system and log in. You must have Administrator privileges to update the driver software. 2. On the desktop, right click My Computer. The My Computer window opens. 3. Select Properties from the menu. The System Properties dialog box opens, as shown in Figure 8 on page 36. 4. Click the Advanced tab. The Advanced tab is shown in Figure 13 on page 42. 5. From the Properties list, select Wake Up Capabilities. 6. From the Values list, select one of the following: ˆ Both - Implements Magic Packet and Wake Up Frame. ˆ Magic Packet - Selects Magic Packet as the Wake Up frame. ˆ None - Selects no wake-up frame. ˆ Wake Up Frame - Selects Wake Up Frame as the wake-up frame and allows the network adapter to wake up the system when an event, such as a ping or an ARP request, is received. WOL Speed The WOL Speed property sets the speed at which the network adapter connects to the network while the network adapter is in Wake on LAN mode. By default, the WOL Speed property is set to Auto. To change the WOL Speed property, perform the following procedure: 1. Start either a Windows Server 2003 system or a Windows XP system and log in. You must have Administrator privileges to update the driver software. 2. On the desktop, right click My Computer. The My Computer window opens. 3. Select Properties from the menu. The System Properties dialog box opens, as shown in Figure 8 on page 36.

48 4. Click the Advanced tab. The Advanced tab is shown in Figure 13 on page 42. 5. From the Properties list, select Wake Up Capabilities. 6. From the Values list, select one of the following: ˆ 100Mb - Sets the speed to 100 Mb. This is the default.

49 Uninstalling the Driver Software Before physically removing an adapter from your system, first uninstall the adapter driver software. For instructions on how to uninstall the driver software, see the chapter that pertains to your platform. Caution Before uninstalling the Allied Telesyn device, be sure to capture all Advanced Property settings because the properties are lost during the uninstall process. To uninstall the adapter software from your system, perform the following procedure: 1. Start Windows Server 2003 or Windows XP and log in. Note You must have Administrator privileges to remove the driver software. 2. Choose from the following: ˆ If you have a Windows 2003 Server system, click Start. Then select the Control Panel from the menu. Double-click the System icon. ˆ If you have a Windows XP system, right click on My Computer Then select Properties from the menu. The System Properties dialog box opens, as shown in Figure 8 on page 36. 3. Click the Hardware tab. The Hardware Tab is shown in Figure 9 on page 37. 4. Click Device Manager. The Device Manager Window is shown in Figure 10 on page 38. 5. In the Device Manager window, click the + next to the Network Adapters folder. The selection expands to show the list of installed network adapter cards. 6. Right-click on the adapter to be removed and select Uninstall. A Confirm Device Removal window opens.

50 7. Click OK to complete the uninstall. Note Not all driver files are removed as part of this procedure. Note that drivers and adapters can be removed via the Hot Plug application, if it is supported.

Software This chapter provides procedures for installing the Windows 2000 Driver software and contains the following sections: ˆ “Installing the Windows 2000 Driver Software” on page 52 ˆ “Modifying Configuration Properties” on page 54 ˆ “Updating the Driver Software” on page 63 ˆ “Removing the Driver Software” on page 64

52 Installing the Windows 2000 Driver Software Note The Allied Telesyn adapter must be physically installed in your system before installing the driver software. See Chapter 2, “Installing the Hardware” on page 21 for details. When the Windows 2000 system first boots up after installing a new hardware device, such as an Allied Telesyn adapter, the system automatically detects the new hardware and prompts you to install the driver software for that device. If the system automatically loads an onboard Broadcom adapter driver. You can use this driver, or the latest one supplied by Allied Telesyn. A network device driver must be installed before you can use the Allied Telesyn adapter with your Windows 2000 system. Installing the Adapter Software When you update the adapter software on existing Allied Telesyn devices, the Advanced Property settings may not be updated unless you remove the existing Allied Telesyn device by following the instructions in “Removing the Driver Software” on page 64. Then you must perform a scan for hardware changes in the device manager and reinstall the Allied Telesyn device with the current adapter software as described in “Installing the Windows 2000 Driver Software” on page 52. To install the adapter software for Windows 2000, perform the following procedure. Note Before beginning this procedure, verify that the Windows 2000 system has been upgraded to the latest version with the latest service pack applied. 1. Start your Windows 2000 system and log in. Note You must have Administrator privileges to install the driver software. When you boot up the Windows 2000 system after installing the adapter card, a series of windows opens. 2. In the Install Hardware Device Drivers window, click Search for a suitable driver for my device (recommended), then click Next.

53 3. In the Locate Driver Files window, select the applicable search location check boxes, then click Next. 4. When prompted, insert the media to be searched into your CD-ROM drive, type the path to the driver, and select OK. For example, where "e" is the designation of the CD-ROM drive on your system, enter: e:\xp_w2k_w3k 5. In the Driver Files Search Results window, verify that the correct path to the driver software is shown, then click Next.

54 Modifying Configuration Properties Although the default values should be appropriate in most cases, you can change any of the available options to meet the requirements of your specific system. After the adapter driver software has been installed, you can use this procedure to verify or change the following adapter properties: ˆ “802.1p QOS” on page 55 ˆ “Checksum Offload” on page 56 ˆ “Flow Control” on page 57 ˆ “Locally Administered Address” on page 58 ˆ “Speed & Duplex” on page 59 ˆ “Wake Up Capabilities” on page 60 ˆ “WOL Speed” on page 61 Configuring Driver Properties To configure the adapter properties, perform the following procedure: 1. On the desktop, right click My Computer. The My Computer window opens. 2. Select Properties from the menu. The System Properties dialog box opens, as shown in Figure 8 on page 36. 3. Click the Advanced tab. The Advanced tab is shown in Figure 14 on page 55.

55 Figure 14. Advanced Tab 4. Change the operating properties as needed. To change adapter operating property, click a property in the Property list and then select a setting from Value list. See the following sections for a description of the properties. 802.1p QOS The 802.1p QOS property is a standard that enables Quality of Service (QOS). It is responsible for the QOS provisions on the local segment, and the avoidance of the "all packets are treated equally" issue, which falls onto the hub or switch servicing segment. 802.1p QOS provides prioritization of packets traversing a subnet. Thus, when the local segment becomes congested and the hub or switch workload results in the delay (dropping) of packets, those packets with flags that correspond to higher priorities receive preferential treatment and are serviced before packets with lower priorities. To enable or disable the 802.1p QOS property, perform the following procedure: 1. Start either a Windows Server 2003 system or a Windows XP system and log in. You must have Administrator privileges to update the driver software. 2. On the desktop, right click My Computer. The My Computer window opens. 3. Select Properties from the menu.

56 The System Properties dialog box opens, as shown in Figure 8 on page 36. 4. Click the Advanced tab. The Advanced tab is shown in Figure 13 on page 42. 5. From the Properties list, select 802.1p QOS. 6. From the Values list, select one of the following: ˆ Enable - Enables the 802.1p QOS property. ˆ Disable - Disables the 802.1p QOS property. This is the default. Note Enabling 802.1p QOS also requires an 802.1p aware switch. 7. Click OK. 8. If prompted to restart your computer, click Yes. Even though it is not necessary to reboot the system for new adapter properties to take effect, rebooting is recommended to reinitialize all registers. 9. Verify that the adapter port LEDs operate as described in “Physical Description” on page 20. Checksum Offload Usually, the Checksum Offload function is computed by the protocol stack. By selecting one of the Checksum Offload properties, the adapter can compute the checksum. To change the Checksum Offload setting, perform the following procedure: 1. Start either a Windows Server 2003 system or a Windows XP system and log in. You must have Administrator privileges to update the driver software. 2. On the desktop, right click My Computer. The My Computer window opens. 3. Select Properties from the menu. The System Properties dialog box opens, as shown in Figure 8 on page 36. 4. Click the Advanced tab.

57 The Advanced tab is shown in Figure 13 on page 42. 5. From the Properties list, select Checksum Offload. 6. From the Values list, select one of the following: ˆ None - Disables checksum offloading. ˆ Rx TCP/IP Checksum - Enables receive TCP, IP, and UDP checksum offloading. ˆ Tx TCP/IP Checksum - Enables transmit TCP, IP, and UDP checksum offloading. ˆ Tx/Rx TCP/IP Checksum (default) - Enables transmit and receive TCP, IP, and UDP checksum offloading. 7. Click OK. 8. If prompted to restart your computer, click Yes. Even though it is not necessary to reboot the system for new adapter properties to take effect, rebooting is recommended to reinitialize all registers. 9. Verify that the adapter port LEDs operate as described in “Physical Description” on page 20. Ethernet Wire Speed This parameter is visible but not supported on the AT-2711FX Fast Ethernet adapter. Flow Control The Flow Control property allows you to enable or disable the receipt or transmission of PAUSE frames which enable the adapter and the switch to control the transmit rate. The side that is receiving the PAUSE frame momentarily stops transmitting. The recommended selection is Disable, which configures the adapter to ignore PAUSE frames. By default, the Flow Control property is disabled. To change the Flow Control property, perform the following procedure: 1. Start either a Windows Server 2003 system or a Windows XP system and log in. You must have Administrator privileges to update the driver software. 2. On the desktop, right click My Computer. The My Computer window opens. 3. Select Properties from the menu.

58 The System Properties dialog box opens, as shown in Figure 8 on page 36. 4. Click the Advanced tab. The Advanced tab is shown in Figure 13 on page 42. 5. From the Properties list, select Flow Control. 6. From the Values list, select one of the following: ˆ Auto - (default) PAUSE frame receipt and transmission is optimized. ˆ Disable - PAUSE frame receipt and transmission is disabled (recommended). ˆ Rx PAUSE - PAUSE frame receipt is enabled. ˆ Rx/Tx PAUSE - PAUSE frame receipt and transmission is enabled. ˆ Tx PAUSE - PAUSE frame transmission is enabled. 7. Click OK. 8. If prompted to restart your computer, click Yes. Even though it is not necessary to reboot the system for new adapter properties to take effect, rebooting is recommended to reinitialize all registers. 9. Verify that the adapter port LEDs operate as described in “Physical Description” on page 20. Locally Administered Address The Locally Administered Address is a user-defined address that is used in place of the MAC address originally assigned to the adapter. Every adapter in the network must have its own unique MAC address. This locally administered address consists of a 12-digit hexadecimal number. To change the Locally Administered Address property, perform the following procedure: 1. Start either a Windows Server 2003 system or a Windows XP system and log in. You must have Administrator privileges to update the driver software. 2. On the desktop, right click My Computer. The My Computer window opens. 3. Select Properties from the menu.

59 The System Properties dialog box opens, as shown in Figure 8 on page 36. 4. Click the Advanced tab. The Advanced tab is shown in Figure 13 on page 42. 5. From the Properties list, select Locally Administered Address. 6. From the Values list, select one of the following: ˆ The range is 0000 0000 0001 to FFFF FFFF FFFD. ˆ Do not use a multicast address (least significant bit of the high byte = 1). ˆ Do not use all 0's or all F's. 7. Click OK. 8. If prompted to restart your computer, click Yes. Even though it is not necessary to reboot the system for new adapter properties to take effect, rebooting is recommended to reinitialize all registers. 9. Verify that the adapter port LEDs operate as described in “Physical Description” on page 20. Speed & Duplex The Speed & Duplex property sets the connection speed and mode to that of the network. Note that Full-Duplex mode allows the adapter to transmit and receive network data simultaneously. To change the Speed & Duplex property, perform the following procedure: 1. Start either a Windows Server 2003 system or a Windows XP system and log in. You must have Administrator privileges to update the driver software. 2. On the desktop, right click My Computer. The My Computer window opens. 3. Select Properties from the menu. The System Properties dialog box opens, as shown in Figure 8 on page 36. 4. Click the Advanced tab. The Advanced tab is shown in Figure 13 on page 42.

60 5. From the Properties list, select Speed & Duplex. 6. From the Values list, select one of the following: ˆ 100 Mb Full. Sets the speed at 100 Mbit/s and the mode to Full- Duplex. ˆ 100 Mb Half. Sets the speed at 100 Mbit/s and the mode to Half- Duplex. ˆ 10 Mb Full (not supported on the AT-2711FX Fast Ethernet adapter) and 100 Mb Full settings force the network adapter to connect to the network in Full-Duplex mode. The network adapter may not function if the network is not configured to operate at the same mode. 7. Click OK. 8. If prompted to restart your computer, click Yes. Even though it is not necessary to reboot the system for new adapter properties to take effect, rebooting is recommended to reinitialize all registers. 9. Verify that the adapter port LEDs operate as described in “Physical Description” on page 20. Wake Up Capabilities The Wake Up Capabilities property enables the network adapter to wake up from a low-power mode when it receives a network wake-up frame. Two types of wake-up frames are possible: Magic Packet and Wake Up Frame. To change the Wake Up Capabilities property, perform the following procedure: 1. Start either a Windows Server 2003 system or a Windows XP system and log in. You must have Administrator privileges to update the driver software. 2. On the desktop, right click My Computer. The My Computer window opens. 3. Select Properties from the menu. The System Properties dialog box opens, as shown in Figure 8 on page 36. 4. Click the Advanced tab. The Advanced tab is shown in Figure 13 on page 42.

61 5. From the Properties list, select Wake Up Capabilties. 6. From the Values list, select one of the following: ˆ Both (default). Selects both Magic Packet and Wake Up Frame as wake-up frames. ˆ Magic Packet. Selects Magic Packet as the wake-up frame. ˆ None. Selects no wake-up frame. ˆ Wake Up Frame. Selects Wake Up Frame as the wake-up frame and allows the network adapter to wake the system when an event such as a ping or an Address Resolution Protocol (ARP) request is received. 7. Click OK. 8. If prompted to restart your computer, click Yes. Even though it is not necessary to reboot the system for new adapter properties to take effect, rebooting is recommended to reinitialize all registers. WOL Speed The WOL Speed property sets the speed at which the network adapter connects to the network while the network adapter is in Wake on LAN mode. By default, the WOL Speed property is set to Auto. To change the WOL Speed property, perform the following procedure: 1. Start either a Windows Server 2003 system or a Windows XP system and log in. You must have Administrator privileges to update the driver software. 2. On the desktop, right click My Computer. The My Computer window opens. 3. Select Properties from the menu. The System Properties dialog box opens, as shown in Figure 8 on page 36. 4. Click the Advanced tab. The Advanced tab is shown in Figure 13 on page 42. 5. From the Properties list, select WOL Speed. 6. From the Values list, select one of the following: ˆ 10 Mb. This is not supported on the AT-2711FX Fast Ethernet adapter.

62 ˆ 100 Mb. Sets the speed to 100 Mbit/s. ˆ Auto (default). Sets the speed for optimum network connection. 7. Click OK. 8. If prompted to restart your computer, click Yes. Even though it is not necessary to reboot the system for new adapter properties to take effect, rebooting is recommended to reinitialize all registers. 9. Verify that the adapter port LEDs operate as described in “Physical Description” on page 20.

63 Updating the Driver Software To replace adapter driver software with newer versions as they become available, perform the following procedure: 1. Start Windows 2000 and log in. Note You must have Administrator privileges to remove the driver software. 2. Open the Control Panel and double-click the System icon. The System Properties dialog box opens, as shown in Figure 8 on page 36. 3. Click the Hardware tab. The Hardware Tab is shown in Figure 9 on page 37. 4. Click Device Manager. The Device Manager Window is shown in Figure 10 on page 38. 5. In the Device Manager window, click the + next to the Network Adapters folder. The selection expands to show the list of installed network adapter cards. 6. Click Update Driver. The Update Device Driver Wizard opens. 7. Click Next. The Install Hardware Device Driver dialog box opens. 8. Click Display a list of known drivers for this device so that I can choose a specific driver, then click Next. 9. When prompted, click Have Disk and insert the media to be searched into your CD-ROM drive, type the path to the driver, and select OK. 10. Select the appropriate driver to update, then click Next. 11. After the software update is complete, click Finish to close the wizard and complete the driver update.

64 Removing the Driver Software To remove the network adapter driver software, perform the following procedure: Caution Before uninstalling the Allied Telesyn device, be sure to capture all Advanced Property settings because the properties are lost during the uninstall process. Note Before physically removing an adapter from your system, first remove the adapter driver software. 1. Start Windows 2000 and log in. Note You must have System Administrator privileges to remove the driver software. 2. Open the Control Panel and double-click the System icon. The System Properties dialog box opens, as shown in Figure 8 on page 36. 3. Click the Hardware tab. The Hardware Tab is shown in Figure 9 on page 37. 4. Click Device Manager. The Device Manager Window is shown in Figure 10 on page 38. 5. In the Device Manager window, click the + next to the Network Adapters folder. The selection expands to show the list of installed network adapter cards. 6. Right-click on the adapter to be removed and select Uninstall. A Confirm Device Removal window opens. 7. Click OK to complete the uninstall.

65 Note Not all driver files are removed as part of this procedure. Note that the driver and adapter can be removed via the Hot Plug application, if it is supported.

This chapter describes the Linux driver for the AT-2711FX Fast Ethernet adapter and includes the following sections: ˆ “Installing the Linux Driver Software” on page 68 ˆ “Network Installation” on page 70 ˆ “Removing the Linux Driver from a TAR Installation” on page 71 ˆ “Module Parameters” on page 72

68 Installing the Linux Driver Software The section describes the following Linux driver installations: ˆ “Building a Driver from a TAR File” on page 68 ˆ “Removing the tg3 Driver” on page 68 Note On some newer Distributions and Kernels, it may be necessary to remove the tg3 driver before loading the tg3 driver supplied on the CD. Follow the instructions in the “Removing the tg3 Driver” on page 68. Building a Driver from a TAR File To build a driver from a TAR file, perform the following procedure. 1. Create a directory and extract the TAR files: tar xvzf tg3-.tgz 2. Build the driver tg3.o as a loadable module for the running kernel: cd tg3-/src make 3. Test the driver by loading it: insmod tg3.o 4. Install the driver and man page: make install 5. To configure network protocol and address, refer to the manuals supplied with your operating system. Removing the tg3 Driver Many various Linux distributions may load the native tg3 driver by default for the Allied Telesyn Fast Ethernet adapters. It may be necessary to unload the native tg3 driver first, before installing the tg3.o driver from this installation. Note On some Distributions and Kernels, it may be necessary to remove the native tg3 driver before loading the Allied Telesyn tg3.o driver. Even though tg3 is a fully functioning driver, Allied Telesyn recommends

69 that you use the newer tg3 driver provided by Allied Telesyn. Use ifconfig to bring down all eth# interfaces used by tg3 and enter the following command to unload the tg3 driver. rmmod tg3 For more detailed Linux specific information on ifconfig, rmmod, or modules.conf, refer to the respective man pages.

70 Network Installation For network installations through NFS, FTP, or HTTP (using a network boot disk or PXE), a driver diskette that contains the tg3 driver may be needed. The driver diskette images for the most recent Red Hat versions are included. Boot drivers for other Linux versions can be compiled by modifying the Makefile and the make environment. Further information is available from Red Hat's website, http://www.redhat.com. To create the driver diskette, select the appropriate image file and do the following: dd if=dd.img of=/dev/fd0H1440.

71 Removing the Linux Driver from a TAR Installation If the driver was installed using make install from the tar file, you must manually delete the tg3.o driver.

72 Module Parameters Optional parameters for the driver can be supplied as command line arguments to the insmod command. Typically, these parameters are set in the file /etc/modules.conf (see the man page for modules.conf). These parameters take the following form: =value[,value,...] where the multiple values for the same parameter are for multiple Allied Telesyn Fast Ethernet adapters installed in the system. Note The default or other meaningful values are used when invalid values are selected. Some combinations of parameter values may conflict and lead to failures. The driver cannot detect all such conflicting combinations. The module parameters are listed below: ˆ line_speed Selects the line speed of the link. This parameter is used together with full_duplex and auto_speed to select the speed and duplex operation of the link and the setting of Auto-Negotiation. Choose from the following selections. – 0 - Autonegotiate for highest speed supported by link partner (default) – 10 - 10 Mbps – 100 - 100 Mbps – 1000 - 1000 Mbps If line_speed is set to 10, 100, or 1000 and the auto_speed is set to 1, the NIC autonegotiates for the selected speed (and selected duplexity). If auto_speed is set to 0, the selected speed and duplexity are set without Auto-Negotiation. Note that 1000 Mbps must be negotiated for copper twisted pair links. ˆ auto_speed Enables or disables Auto-Negotiation. Choose from the following selections. – 0 - Auto-Negotiation disabled – 1 - Auto-Negotiation enabled (default)

73 Note This parameter is ignored and assumed to be 1 if the line_speed parameter is set to 0. ˆ full_duplex Selects the duplexity of the link. This parameter is used together with line_speed to select the speed and duplexity of the link. Note that this parameter is ignored if line_speed is 0. Choose from the following selections. – 0 - half duplex – 1 - full duplex (default) ˆ rx_flow_control Enables or disables receiving flow control (pause) frames. This parameter is used together with auto_flow_control. Choose from the following selections. – 0 - pause receive disabled – 1 - pause receive enabled if auto_flow_control is set to 0, or pause receive advertised if auto_flow_control is set to 1 (default) ˆ tx_flow_control Enables or disables transmitting flow control (pause) frames. This parameter is used together with auto_flow_control. Choose from the following selections. – 0 - pause transmit disabled – 1 - pause transmit enabled if auto_flow_control is set to 0, or pause transmit advertised if auto_flow_control is set to 1 (default) ˆ auto_flow_control Enables or disables Auto-Negotiation of flow control. This parameter is used together with rx_flow_control and tx_flow_control to determine the advertised flow control capability. Choose from the following selections. – 0 - flow control Auto-Negotiation disabled – 1 - flow control Auto-Negotiation enabled with capability specified in rx_flow_control and tx_flow_control (only valid if line_speed is set to 0 or auto_speed is set to 1) (default) ˆ mtu

74 Enables jumbo frames up to the specified MTU size. The valid range for this parameter is 1500 to 9000. The default is 1500 which is the standard Ethernet (non-jumbo) MTU size. Note that the MTU size excludes the Ethernet header size of 14 bytes. Actual frame size is MTU size + 14 bytes. The MTU size can also be changed using ifconfig after the driver is loaded. See the ifconfig man page for details. ˆ tx_checksum Enables or disables hardware transmit TCP/UDP checksum. Choose from the following selections. – 0 - checksum disabled – 1 - checksum enabled (default) ˆ rx_checksum Enables or disables hardware receive TCP/UDP checksum validation. Choose from the following selections. – 0 - checksum disabled – 1 - checksum enabled (default) ˆ scatter_gather Enables or disables scatter-gather and 64-bit DMA on x86. This option is only useful when running on TUX-enabled kernels or kernels with zero-copy TCP. Choose from the following selections. – 0 - scatter-gather and 64-bit DMA on x86 disabled – 1 - scatter-gather and 64-bit DMA on x86 enabled (default) ˆ tx_pkt_desc_cnt Configures the number of transmit descriptors. Default is 100. The valid range is from 1 to 600. Depending on kernel and system architecture, the driver may require up to 268 bytes per descriptor. Note that the driver may not be able to allocate the required amount of memory if this parameter is set too high. This parameter should not be set less than 80 if adaptive_coalesce (see below) is enabled. ˆ rx_std_desc_cnt Configures the number of receive descriptors for frames up to 1528 bytes. Default is 200. The valid range is from 1 to 511. This parameter should not be set less than 80 on systems with high network traffic. Setting this parameter higher allows the NIC to buffer larger bursts of network traffic without dropping frames, especially on slower systems. Note that the driver may not be able to allocate the required amount of memory if this parameter is set too high. This parameter should not be set less than 50 if adaptive_coalesce (see below) is enabled.

75 ˆ rx_jumbo_desc_cnt Configures the number of receive descriptors for jumbo frames larger than 1528 bytes. The default is 128 and the valid range is from 1 to 255. When jumbo frames larger than 1528 bytes are used, this parameter should not be set lower than 60 on systems with high network traffic. Setting this parameter higher allows the NIC to buffer larger bursts of jumbo traffic without dropping frames, especially on slower systems. Depending on kernel and system architecture, the driver may require up to 268 bytes per descriptor. Note that each descriptor also requires a buffer the size of a maximum jumbo frame. On systems with insufficient memory, it may be necessary to reduce this parameter. This parameter should not be set to less than 50 if adaptive_coalesce (see below) is enabled. When the maximum frame size is less than 1528 (MTU size less than 1514), this parameter is not used and is always 0. ˆ adaptive_coalesce Enables or disables adaptive adjustments to the various interrupt coalescing parameters. Enabling it allows the driver to dynamically adjust the interrupt coalescing parameters to achieve high throughput during heavy traffic and low latency during light traffic. rx_std_desc_cnt, (and rx_jumbo_desc_cnt if using jumbo frames) should not be set less than 50, and tx_pkt_desc_cnt should not be set less than 80 when this parameter is enabled. Choose from the following selections. – 0 - disabled – 1 - enabled (default) ˆ rx_coalesce_ticks Configures the number of 1 usec ticks before the NIC generates receive interrupt after receiving a frame. This parameter works in conjunction with the rx_max_coalesce_frames parameter. Interrupt will be generated when either of these thresholds is exceeded. A value of 0 means this parameter is ignored and an interrupt is generated when the rx_max_coalesce_frames threshold is reached. The valid range is from 0 to 500 and default is 80. This parameter is not used and is adjusted automatically if adaptive_coalesce is set to 1. ˆ rx_max_coalesce_frames Configures the number of received frames before the NIC generates receive interrupt. The valid range is from 0 to 100 and the default is 15. This parameter and rx_coalesce_ticks cannot both have a value of 0. If both parameters are set to 0, no receive interrupts are generated. It should also be set significantly lower than rx_std_desc_cnt (and rx_jumbo_desc_cnt if using jumbo frames). This parameter is not used and is adjusted automatically if adaptive_coalesce is set to 1.

76 ˆ tx_coalesce_ticks Configures the number of 1 usec ticks before the NIC generates transmit interrupt after transmitting a frame. This parameter works in conjunction with the tx_max_coalesce_frames parameter. Interrupt is generated when either of these thresholds is exceeded. A value of 0 means this parameter is ignored and an interrupt is generated when the tx_max_coalesce_frames threshold is reached. The valid range is from 0 to 500 and the default is 400. This parameter is not used and is adjusted automatically if adaptive_coalesce is set to 1. ˆ tx_max_coalesce_frames Configures the number of transmitted frames before the NIC generates transmit interrupt. The valid range is from 0 to 100 and the default is 40. This parameter and tx_coalesce_ticks cannot both have a value of 0. If both parameters have a value of 0, no transmit completion interrupt is generated. This parameter should always be set lower than tx_pkt_desc_cnt. This parameter is not used and is adjusted automatically if adaptive_coalesce is set to 1. ˆ stats_coalesce_ticks Configures the number of 1 usec ticks between periodic statistics block DMAs. The valid range is from 0 to 3600000000, and the default is 1000000 (1 sec.). Set this parameter to a value of 0 to disable statistics updates. This parameter is not used and is set to default if rx_adaptive_coalesce is set to 1. ˆ enable_wol Enables or disables magic packet Wake-On-LAN when the system is shut down. Note that not all systems support Wake-On-LAN. Choose from the following selections. – 0 magic packet Wake-On-LAN disabled (default) – 1 magic packet Wake-On-LAN enabled ˆ enable_tso Enables or disables TCP Segmentation Option (TSO) when using kernels that support it. Choose from the following selections. – TSO disabled (default) – TSO enabled

This chapter provides procedures for installing the NetWare Driver software and contains the following sections: ˆ “Driver Installation” on page 78 ˆ “Pre-Installation Requirements” on page 79 ˆ “Installing Novell NetWare Server 5.x or 6.0 Driver Software” on page 80 ˆ “Verifying or Modifying Adapter Parameters” on page 82 ˆ “Removing Drivers from Autoexec.ncf” on page 87

78 Driver Installation This chapter describes how to perform the following tasks: ˆ Verify that the required OS support files are installed on the server and the NetWare pre-installation parameters are set correctly. ˆ Install the driver software in the Novell NetWare environment. ˆ If necessary, reconfigure the driver software after installation. ˆ For an adapter installation with an existing NetWare server, NetWare automatically detects the new adapter and attempts to load the appropriate driver. Ensure that your Allied Telesyn CD-ROM is loaded and select the appropriate driver for your Allied Telesyn Fast Ethernet adapter. A commonly used method to install a driver on a NetWare server running 5.x or 6.0 and higher is through NWCONFIG.

79 Pre-Installation Requirements A network device driver must be installed before the Fast Ethernet adapter can be used with your Novell NetWare system. Before you can successfully install the adapter driver for Novell NetWare, the adapter card must be physically installed in the server and, typically, the NetWare OS software must already be running on the server. Make sure that your server meets the hardware and operating system software requirements described Chapter 2, “Installing the Hardware” on page 21. To enable the Allied Telesyn Fast Ethernet adapter to function correctly, you need to install the latest Novell NetWare support pack files. The NetWare support pack or patch file(s) needed for the operating system running on your server are indicated in Table 3. Note If you are installing NetWare 5.x or 6.0 for the first time on a system, the process to install the adapter driver occurs during the OS installation procedure. Install the NetWare 5 support pack after you have successfully installed the operating system on the server. To obtain the latest support pack files, go to the Novell support website and click on the Minimum Patch List option in the navigation bar. Scroll down the page and, using Table 3 above as a guide, select and download the latest support pack or patch file(s) for the operating system running on your server. Table 3. NetWare Support Files NetWare OS Support Pack or Patch Files to be Installed NetWare 5.1 Latest NetWare 5.1 Support Pack The latest support pack can be found at http:// support.novell.com/ patlst.htm NetWare 6.0 Latest NetWare 6.0 Support Pack

80 Installing Novell NetWare Server 5.x or 6.0 Driver Software Ensure that the server has the latest support pack available installed. The latest support packs can be found at: http://support.novell.com/misc/ patlst.htm. You may want to create an archive disk by copying all the files from the CDROM\Driver\Netware directory onto a floppy disk. If you use the CD- ROM directly, be sure that the CDROM.NLM is loaded and that you are aware of the NetWare Volume name for the CD-ROM that you just installed. To install the Novell NetWare Server 5.x or 6.0 Driver software, perform the following procedure: 1. From the NetWare Server console, type LOAD NWCONFIG (or just NWCONFIG) and press Enter. 2. From the Configuration Options screen, select Driver options and press Enter. 3. Select the Configure network drivers option and press Enter. 4. Choose the Load an additional driver option and press Enter. 5. Insert the CD-ROM and select the Install an unlisted driver option, by pressing Insert. 6. If you are using the archive disk that you created, insert the disk into drive A: and press Enter. If you have the CD-ROM mounted as a NetWare volume, go to step 7. 7. If you have the CD-ROM mounted as a NetWare volume, press F3 and enter : Driver\Netware as the source path. Where is the name of the NetWare Volume for the CD-ROM and Netware\Driver is the directory of the specific files on the CD-ROM needed for this installation. The name of the driver is displayed. 8. Press Enter to select the highlighted driver. A copy the driver prompt appears. 9. Select Yes and press Enter. 10. Select Yes and press Enter to copy the .LDI file. This is the installation script for the driver. 11. Follow the instructions for the installation.

81 12. Select Save parameters and load driver to continue. 13. Choose Exit to return to the server console prompt. Note If you are performing an initial installation of NetWare 5.x or 6.0 and have more than two adapters installed, the install program allows you to allocate the actual number of packet receive buffers needed by the adapter. During installation, make sure the RxBuffers value is set to 32 which is the minimum number of buffers the driver requires for each adapter. While this setting affects adapter performance, it allows installation of the operating system and up to eight adapters during the initial installation. Once installation is complete, increase the number of buffers allocated to the driver as described in “Verifying or Modifying Adapter Parameters” on page 82. 14. 5.x or 6.05.x or 6.0 NetWare 5.x or 6.0 has been successfully installed, set the minimum packet receive buffers parameter in the startup.ncf file to 1500 for each adapter in the system. Set the maximum packet receive buffers to three times the minimum packet receive buffers. Typically 4 MB of RAM is required per 1000 receive buffers. For more information, see “Verifying or Modifying Adapter Parameters” on page 82. 15. In the autoexec.ncf file, delete the packet receive buffers parameter (RxBuffers=32) in the load statement for this adapter. Deleting the receive buffers phrase from the load statement resets the receive buffers parameter to the default value of 200 for this adapter. Note The server needs to be restarted for the new configuration. Example: The default maximum number of receive buffers for the system is 500; the default minimum is 128. Edit the startup.ncf file to have the following entries. The actual numbers will be a function of the number of ports in the system. The following is an example for a system with 8 ports installed: set maximum packet receive buffers = 36000 set minimum packet receive buffers = 12000

82 Verifying or Modifying Adapter Parameters When an adapter configuration is saved, the NetWare install program adds load and bind statements to the autoexec.ncf file. By accessing this file, you can verify the parameters configured for each adapter, modify them, or enter additional parameters. Note The Novell monitor program and the config command are also useful for verifying driver configuration. For information on how to use these programs, see the Utilities Reference in your Novell NetWare online documentation. The parameters that can be defined in the load statements are described below: Configuration Parameters for B57.LAN driver: TxDescriptors= This is to initialize Descriptor resources on the adapter for transmits. Min = 100 Max = 512 Default = 120 RxBuffers= This is to pre-allocate receive ECBs & Receive adapter resources. This setting may be affected by the NetWare server maximum/minimum packet receive buffer settings. Min = 32 Max = 1000 Default = 200 RxTicks= This is to enable the use of batching receives within a specific time period. Min = 0, disabled Max = 5000000, 5 seconds Units are in micro seconds Default value is 300 TxTicks= This is to enable the use of a transmit "tick" threshold interrupt within a specific time period. Min = 0, disabled Max = 5000000, 5 seconds Units are in micro seconds Default is 200

83 TxPacketsPer= This is to enable the use of allowing an interrupt to occur after a specific amount of packets are transmitted. Min = 0, disabled Max = 100 Default is 20 RxPacketsPer= This is to enable the use of allowing an interrupt to occur after a specific amount of packets are received. Min = 0, disabled Max = 100 Default is 75 CheckSum= This is to enable or disable the transmit & receive checksum off loading feature.The checksum off loading support is only for TCP/IP packets, for that reason it is defaulted to OFF. Choices are: OFF, ON, TX, RX Default value is OFF TxFlow= This keyword allows enabling/disabling of TxFlow control. Choices are: ON, OFF Default value is OFF. RxFlow= This keyword allows enabling/disabling of RxFlow control. Choices are: ON, OFF Default value is OFF. PDriver= Allows for the driver to operate in persistent driver mode. Only use if adapter is placed in a Hot Plug PCI slot and only if required to swap with an exact same board. Choices are: OFF, ON Default value is OFF. NODE= This is a Novell NetWare keyword. This keyword will allow an input Ethernet node address to replace the adapter factory programmed Ethernet node address until a subsequent reboot. Choices are: NODE=nnnnnnnnnnnn

84 FRAME= This is a Novell NetWare keyword. String specifying the frame type. Choices are: ETHERNET_II ETHERNET_802.3 ETHERNET_802.2 ETHERNET_SNAP Default value is ETHERNET_802.2 SLOT= This is a Novell NetWare keyword. System-wide unique Hardware Instance Number (HIN) that may be the physical slot number on a slot based bus such as PCI. SLOT=n Jumbo= Keyword to enable Jumbo frame support. When enabled, jumbo packets of up to 9000 bytes are supported. Choices are: Jumbo=1536-9100 Default is no jumbo packets Note Jumbo frames are only supported on NetWare 6.0 and above. Plus the first frame loaded must be ETHERNET_II Note Jumbo frame support must have the following text in the Startup.ncf file: "Set maximum physical receive packet size = 18000". P3= This keyword is used when running perform3.exe tests and may increase performance on networks running with many ipx clients. Set P3=1, when running the perform3 test back to back to a single client. Set P3=2, when running the perform3 test with many clients. Default: P3=0. Spuriousfix= When this keyword is set to 1 (spurious fix is on), the spurious interrupts count that is sometimes displayed on the NetWare console monitor, may be reduced. By setting this keyword to 0 (spurious fix is OFF), performance of the driver may be enhanced.

85 The Default is spurious fix = 1 (spurious fix is on). Choices are: Spuriousfix=0 Spuriousfix=1 (default). Poll= To disable interrupt driven mode in the driver set Poll=1 and the driver will not use interrupts, but will be polled by the NetWare OS. This is a common feature supported in NW. The poll mode may increase driver performance in some environments. Choices are: Poll=1 (ON) Poll=0 (OFF) (default). WireSpeed= This feature provides adapter link & data integrity even when attached to a questionable cable and/or switch. For example; an adapter trying to run 1000 speed on a cat3 cable ordinarily would not link. With the WireSpeed=1, the link will occur at 100Mbs. Choices are: WireSpeed=1 (ON) (Default) WireSpeed=0 (OFF). Model= This keyword is to allow the addition of a sub-system ID of a specific NIC so that the driver loads only on the first NIC found with a matching sub-system ID. e.g., MODEl= 0x14e4 Default = 0 MagicP= When the MagicP=1 the driver will enable the adapter to wake up the system when a magic packet is received after the system is shutdown. MagicP=0 is the default setting with the adapter having no wake up ability. Choices are: MagicP=0 (default) MagicP=1 Fiber= The driver has support for the 1000FD fiber adapter. The fiber autonegotiates link with a fiber switch even though it only supports 1000FD. In some cases the user may want to force the adapter to 1000FD. Choices are: Fiber=AUTO (default) Fiber=FORCE

86 Note If you modify any adapter parameters, you must reboot the system before the changes take effect. If you make changes and do not reboot, you may experience configuration problems. A valid autoexec.ncf file is shown below. One set of load and bind commands (in bold) is added for each frame type the adapter is configured to support. Set Time Zone = PST8PDT set Daylight Savings Time Offset = 1 set Start Of Daylight Savings Time = (APRIL SUNDAY FIRST 2:00:00 AM) set End Of Daylight Savings Time = (OCTOBER SUNDAY LAST 2:00:00 AM) set Default Time Server Type = SINGLE set Bindery Context = O=LAN # WARNING!! file server name NOVELLSERVER51 # WARNING!! # If you change the name of this server, you must update # all the licenses that are assigned to this server. # Using NWAdmin, double-click on a license object and # click on the Certificate Assignments button. If the # old name of this server appears, you must delete it and # then add the new server name. Do this for all license # objects. ServerID 1C8EE2C LOAD ODINEB.NLM LOAD TCPIP LOAD B57 SLOT=2 FRAME=Ethernet_802.2 NAME=B57_1_E82 BIND IPX B57_1_E82 NET=FAFD3D25 LOAD B57 SLOT=2 FRAME=Ethernet_802.3 NAME=B57_1_E83 BIND IPX B57_1_E83 NET=5A2D8D6D LOAD B57 SLOT=2 FRAME=Ethernet_SNAP NAME=B57_1_ESP BIND IPX B57_1_ESP NET=477A35BD LOAD B57 SLOT=2 FRAME=Ethernet_II NAME=B57_1_EII BIND IPX B57_1_EII NET=C3C8F2E4 BIND IP B57_1_EII ADDR=172.16.1.1 MASK=ff.ff.ff.0 mount all SEARCH ADD SYS:\JAVA\BIN SEARCH ADD SYS:\JAVA\NWGFX

87 Removing Drivers from Autoexec.ncf To remove the drivers from the Autoexec.ncf, locate the Load and Bind command lines associated with the Broadcom driver and remark them out by inserting the # symbol at the beginning of each command line, or by deleting the statement. Example: # LOAD B57 SLOT=2 FRAME=Ethernet_802.2 NAME=B57_1_E82 # BIND IPX B57_1_E82 NET=FAFD3D25 # LOAD B57 SLOT=2 FRAME=Ethernet_802.3 NAME=B57_1_E83 # BIND IPX B57_1_E83 NET=5A2D8D6D # LOAD B57 SLOT=2 FRAME=Ethernet_SNAP NAME=B57_1_ESP # BIND IPX B57_1_ESP NET=477A35BD # LOAD B57 SLOT=2 FRAME=Ethernet_II NAME=B57_1_EII # BIND IPX B57_1_EII NET=C3C8F2E4 # BIND IP B57_1_EII ADDR=172.16.1.1 MASK=ff.ff.ff.0 Note If you modify the Autoexec.ncf, you must reboot the system before the changes take effect.

Software This chapter provides procedures for installing the Allied Telesyn Boot Agent Driver Software. It contains the following sections: ˆ “Overview” on page 90 ˆ “Server Setup” on page 92

90 Overview The Allied Telesyn Fast Ethernet adapter provides PXE (Preboot Execution Environment) and RPL (Remote Program Load) support. Multi- Boot Agent (MBA) is a software module that allows your networked computer to boot with the images provided by remote servers across the network. The MBA driver complies with the PXE-2.1 specification and is released with both monolithic and split binary images. This provides flexibility to users on different environments where the motherboard may or may not have built-in base-code. Enabling and Disabling MBA MBA is enabled by default. To enable MBA, boot up into DOS. Place the Allied Telesyn CD -ROM in the CD drive. d:\diagnostics b57udiag -mba [ 0-disable | 1-enable ] -c where: devnum= specific device(s) number (0,1,2,...) to be programmed Boot Method By default, MBA detects if the BIOS supports BBS (BIOS Boot Specification). If the BIOS supports BBS, then MBA uses BBS as the boot method. If it does not support BBS, then it uses Int18h instead. However, for some legacy machines equipped with an old BIOS, this may not work. In this case, you must force MBA to use Int18h, Int19h, or BBS as the boot method. To specify the boot method, press the following keys when you see the startup banner: ______________________________________ Broadcom NetXtreme Ethernet Boot Agent v3.1.29 Copyright (c) 2000-2003 Broadcom Corporation All rights reserved ___________________________________________ 1. For Int18h: Ctrl + F8 2. For Int19h: Ctrl + F9 3. For BBS: Ctrl + F10

91 Setup BIOS To boot from the network with MBA, make MBA the first bootable device under BIOS. This procedure depends on server BIOS implementation. Please refer to the server's user manual.

92 Server Setup This section discusses how to set up a server on a Windows 2000, Windows Server 2003, Windows XP, DOS UNDI/APITEST, and Red Hat Linux systems. Windows 2000 The current version of Windows 2000 does not include a network driver for the Allied Telesyn Fast Ethernet adapters. To do remote installation with PXE, include a network driver for the adapter as a part of the client's installation image on the server. Please refer to Microsoft Article ID Q246184 - "How to Add Third-Party OEM Network Adapters to RIS Installations." An example of this RIS installation to modify your inf file, refer to the troubleshooting section under Software Problems and Solutions. Also, verify that you have the latest Windows 2000 service pack installed on your system. Note For Windows 2000, if service pack 3 is installed, no modification to the inf file is necessary. Windows Server 2003 and Windows XP The current version of Windows Server 2003 does not include network drivers for the Allied Telesyn Fast Ethernet adapters. To do remote installation with PXE, include a network driver for the adapter as a part of the client's installation image on the server. Please refer to Microsoft Article ID Q246184 - "How to Add Third-Party OEM Network Adapters to RIS Installations." An example of this RIS installation to modify your inf file, refer to the troubleshooting section under Software Problems and Solutions. DOS UNDI/ APITEST To boot in DOS and connect to a network for the DOS environment, download the Intel® PXE PDK from the Intel Web site. This PXE PDK comes with a TFTP/ProxyDHCP/Boot server. The PXE PDK can be downloaded from Intel at http://developer.intel.com/ial/WfM/tools/pxe/ index.htm. Red Hat Linux Red Hat Linux 7.3 (or higher) distribution has PXE server support. It allows you to do a complete Linux installation over the network. Distribution also comes with boot images - boot kernel (vmlinuz) and initial ram disk (initrd). The following images can be found on the CD-ROM disk#1: /images/pxeboot/vmlinuz /images/pxeboot/initrd.img Refer to Red Hat documentation for how to install PXE server on Linux.

93 In this version, it prompts you to insert a driver disk for drivers that are not part of the standard distribution. You can create a driver disk for the adapter from the image distributed with the Allied Telesyn CD-ROM. A remote boot does not require a standard Linux network driver for the adapter. After the PXE client downloads the Linux kernel and initial ram disk, the Linux universal driver that came with the Linux distribution binds with the UNDI code of the PXE to form a Linux network driver.

This chapter provides procedures for installing the NDIS2 Driver software. and contains the following sections: ˆ “Installing the NDIS2 Driver Software for Use on MS-DOS Platforms” on page 96 ˆ “Using Keywords for the B57.dos Drivers” on page 101

96 Installing the NDIS2 Driver Software for Use on MS-DOS Platforms You can run the NDIS2 driver software from an MS-DOS startup disk using Microsoft Network Client 3.0. Pre-Installation Requirements Before you can successfully install the NDIS2 driver software, the Allied Telesyn Fast Ethernet adapter must be physically installed in the computer. Modifying the Startup Disk To modify the startup disk, perform the following procedure: 1. Edit A:\Net\Protocol.ini with Notepad or a similar text editor. a. Change DriverName=$ to DriverName=B57$. b. Remove all other parameter entries under the [MS$NE2CLONE] or equivalent section such as IOBASE=0x300 or INTERRUPT=3, and so on. Example Protocol.ini for IP [network.setup] version=0x3110 netcard=ms$ne2clone,1,MS$NE2CLONE,1 transport=tcpip,TCPIP lana0=ms$ne2clone,1,tcpip [MS$NE2CLONE] DriverName=B57$ [protman] DriverName=PROTMAN$ PRIORITY=MS$NDISHLP [tcpip] NBSessions=6 DefaultGateway=0 ; SubNetMask=255 0 0 0 ; IPAddress=192 168 0 1 DisableDHCP=0 DriverName=TCPIP$

97 BINDINGS=MS$NE2CLONE LANABASE=0 Example Protocol.ini for IPX [network.setup] version=0x3110 netcard=ms$ne2clone,1,MS$NE2CLONE,1 transport=ms$ndishlp,MS$NDISHLP transport=ms$nwlink,MS$NWLINK lana0=ms$ne2clone,1,ms$nwlink lana1=ms$ne2clone,1,ms$ndishlp [MS$NE2CLONE] DriverName=B57$ [protman] DriverName=PROTMAN$ PRIORITY=MS$NDISHLP [MS$NDISHLP] DriverName=ndishlp$ BINDINGS=ms$ne2clone [ms$nwlink] DriverName=nwlink$ FRAME=Ethernet_802.2 BINDINGS=MS$NE2CLONE LANABASE=0 Example Protocol.ini for NetBEUI [network.setup] version=0x3110 netcard=ms$ne2clone,1,MS$NE2CLONE,1 transport=ms$ndishlp,MS$NDISHLP transport=ms$netbeui,MS$NETBEUI

98 lana0=ms$ne2clone,1,ms$ndishlp lana1=ms$ne2clone,1,ms$netbeui [MS$NE2CLONE] DriverName=B57$ [protman] DriverName=PROTMAN$ PRIORITY=MS$NDISHLP [MS$NDISHLP] DriverName=ndishlp$ BINDINGS=MS$NE2CLONE [MS$NETBEUI] DriverName=netbeui$ SESSIONS=10 NCBS=12 BINDINGS=MS$NE2CLONE LANABASE=0 2. Edit A:\Net\System.ini. a. Change netcard= to netcard=b57.dos. b. Check for references to C:\NET and change C:\NET to A:\NET if necessary. Example SYSTEM.INI [network] sizworkbuf=1498 filesharing=no printsharing=no autologon=yes computername=MYPC lanroot=A:\NET username=USER1 workgroup=WORKGROUP

99 reconnect=yes dospophotkey=N lmlogon=0 logondomain= preferredredir=basic autostart=basic maxconnections=8 [network drivers] netcard=B57.dos transport=ndishlp.sys,*netbeui devdir=A:\NET LoadRMDrivers=yes 3. Copy B57.dos to A:\Net. 4. Create the appropriate Autoexec.bat file in drive A for the chosen protocol as shown below. For TCP/IP path=a:\net a:\net\net initialize a:\net\netbind.com a:\net\umb.com a:\net\tcptsr.exe a:\net\tinyrfc.exe a:\net\nmtsr.exe a:\net\emsbfr.exe a:\net\net start basic net use z: \\SERVERNAME\SHARENAME For IPX SET PATH=A:\NET A:\NET\net initialize A:\NET\nwlink

100 A:\NET\NET START BASIC net use z: \\SERVERNAME\SHARENAME For NetBEUI SET PATH=A:\NET A:\NET\NET START BASIC net use z: \\SERVERNAME\SHARENAME 5. Create a Config.sys file on the startup disk in drive A as shown below. files=30 device=a:\net\ifshlp.syslastdrive=z