IBM Netfinity 5500 Version 1.0 Ethernet Device Driver Installation README File This README file contains the latest information about installing the ethernet device drivers for the IBM Netfinity 5500. CONTENTS ________ 1.0 Known Problems 2.0 OS/2 3.0 Windows NT 4.0 NetWare 5.0 SCO 5.1 New Features 5.2 Installation Procedures 6.0 DMI Support 7.0 Trademarks and Notices 1.0 Known Problems ____________________ o If some cases, the ethernet controller does not establish good link with the hub or switch to which it is attached. This sometimes happens when all of the following conditions are true: - The ethernet controller is in auto negotiation mode (the default) - The hub or switch attached to the ethernet controller does NOT support auto negotiation - The length of cable between the ethernet controller and the hub or switch is between 35 and 42 meters In most cases, the ethernet controller can determine the line speed correctly even if the attached hub or switch does not support auto negotiation. If you are having problems use the device driver overrides to manually configure the ethernet controller mode to match the hub or switch mode. As with any adapter, if the hub or switch is configured for full duplex and does not support auto negotiation, then you must use the device driver manual overrides for proper operation. o Some configurations of the failover function do not operate correctly with the NetWare driver. See the NetWare section below for additional details. o Under SCO, there is a bug during driver removal when using netconfig. Users have to manually remove the pnt directory under /etc/conf/pack.d. Otherwise, the next installation of pnt driver will not work. 2.0 OS/2 __________ The OS/2 device driver can handle up to 4 ethernet controllers. These controllers can be configured as any combination of individual networks or redundant pairs. A redundant pair of network adapters can be defined such that a loss of good link status on the primary adapter will cause all ethernet traffic on this link to be automatically switched to the standby adapter. If the link for the primary adapter is restored, the sessions on the standby adapter will automatically switch back to the primary adapter. To enable failover operation, run the MPTS program and edit the AMD device driver parameters. Set the PermaNet Server feature to TRUE. Note that this parameter is case sensitive and must be entered in upper case. Enter the parameters for the Primary and Standby slots. The slot number for the onboard adapter is E. To have a message written into IBMCOM\LANTRAN.LOG whenever a failover occurs, copy the file PCNETOS2.EXE onto the hard disk and edit the CONFIG.SYS file. Add the statement: RUN=c:\path\PCNETOS2.EXE to the beginning of the file, where c is the hard disk and path is the directory path that you copied the PCNETOS2.EXE file into. 3.0 Windows NT ________________ The driver under the NT subdirectory supports the failover function. A redundant pair of network adapters can be defined such that a loss of good link status on the primary adapter will cause all ethernet traffic on this link to be automatically switched to the secondary adapter. If the link for the primary adapter is restored, the sessions on the secondary adapter will automatically switch back to the primary adapter. This driver has passed all IBM testing and has no known problems at the time of release. However, this driver has not yet received Microsoft certification. The NT device driver can handle up to 4 ethernet controllers. Two of these controllers can be configured as a redundant pair. To enable failover operation, select Settings from the Start menu. Then select Control Panel, then Network, then Adapters. Highlight the IBM Netfinity AMD PCNet Ethernet Controller and press the Properties button. Check the Grouping box and designate the primary and secondary adapters. The onboard controller is located at bus 0, slot 14. If a failover occurs, a message will be written to into the NT Event viewer. To enable a pop up message to be written to the screen when a failover occurs, run the PCNET.EXE program located in the NTPERM\DMI subdirectory. This program is the DMI instrumentation code for the NT driver. It is not necessary to install DMI support to use the pop-up feature. 4.0 NetWare _____________ The NetWare driver complies with the ODI 3.31 specification and requires the following minimal level of NetWare load modules for proper operation: MSM.NLM version 3.54 ETHERTSM.NLM version 3.52 These versions or later are available in NetWare service pack 4 or higher. The ethernet controller supports auto negotiation on the ethernet link. To override auto-negotiation and manually specify the mode, load the driver with the appropriate parameter as follows: LOAD PCNTNW LINESPEED=x where x is either 10H, 10F, 100H, 100F, or AUTO. 10H = 10 Mbits/sec, half duplex 10F = 10 Mbits/sec, full duplex 100H = 100 Mbits/sec, half duplex 100F = 100 Mbits/sec, full duplex AUTO = auto negotiation The NetWare driver supports both hot plug and failover operation. The failover function cannot be configured using the PCNTND.LDI file. To enable failover operation, load the driver at the console prompt with the following command: LOAD PCNTNW PRIMARY=d SECONDARY=e where d is the slot number of the primary adapter and e is the slot number of the secondary adapter. The slot number of the onboard adapter can vary depending on the configuration of the machine. To determine the onboard slot number, load the driver with no parameters. You will be prompted with a list of slot numbers to choose from. The onboard adapter will have a slot number greater than or equal to 10,000. Once the slot number is known, unload the driver and reload it using the failover parameters described above. A failover from the primary to the secondary will occur if a link failure condition is detected on the primary adapter. The failover status can be viewed in the custom counts fields of Monitor. If the link for the primary adapter is restored, the sessions on the secondary adapter will automatically switch back to the primary adapter. If a hot replace of the primary adapter occurred while traffic was being handled by the secondary adapter, an automatic failover back to the primary adapter will not occur once the primary link is restored. In this case use the following command to return the traffic to the primary controller: LOAD PCNTNW SCAN NOTE: Some .DSK drivers are not compatible with drivers written to the ODI 3.31 specification. In some cases, the failover feature will not operate correctly if the adapter associated with the .DSK driver shares the same interrupt as one of the ethernet controllers of the failover pair. It is recommended that the primary and secondary ethernet controllers share an interrupt that is not shared with any other adapter or device, though this is not necessary in all cases. 5.0 SCO ______________ 5.1 New Features ------------------ The file PNT401.TAR contains the archive of all the files required to build the driver.o file. The features added from the previous version of the AMD SCO drivers and instructions on their usage are: o 96bit IPG o Override auto-negotiation and automatic network port selection via keywords provided in space.c - To select a connecting medium, make only one variable from AUI, (internal) 10BaseT, or MII equal to '1'. If AUI, 10BaseT, and MII are all '0', then automatic port selection is activated. Only the MII port is supported on the IBM Netfinity 5500 and this port will be selected if automatic port selection is enabled. - To select 100 Mbits speed, set the variable SPEED100 to '1' in the space.c file. Set it to '0' to select 10 Mbits speed. - To select full duplex mode, set FULLDUP to '1' in the space.c file. Set FULLDUP to '0' for half duplex mode. o LED programming via keyword provided in space.h - The LED keyword is provided for knowledgeable users who want to override the default settings. If the user provides specific values for the LEDs in the driver's space.h file, then these values override the factory default values. The user specified values are then reflected by the adapter's LEDs. Go to the directory /etc/conf/pack.d/pnt/ in the system where the pnt driver config files are located. The space.h files contain the driver LED values. If the values are all 0xFFFFFFFF then the driver takes the default LED values from the EEPROM. The user can edit the space.h file to reflect the desired LED values. After the change is made, link the kernel by the command /etc/conf/cf.d/link_unix Reboot and when the system comes up the new LED value is reflected by the LEDs. 5.2 Installation Procedures ----------------------------- The current 4.01 release does come with its own installation scripts. To install, users need to install the older driver that comes with the SCO 5.0.4 CD with netconfig, and bind with TCPIP, relink and reboot, and make sure it works. Then copy four files from release 4.01: Driver.o space.c space.h pnt.h Do a relink from /etc/conf/cf.d and then a reboot. The following values are correct for the onboard controller of the IBM Netfinity 5500: PNT_0_PCI_BUS 0 PNT_0_PCI_DEV 14 PNT_0_PCI_FUNC 0 Make sure they are not -1. 6.0 DMI Support _________________ DMI is currently supported under Windows NT. The device driver component, PCNET.MIF, and the instrumentation code, PCNET.EXE are located in the NTPERM\DMI subdirectory. To install DMI support under Windows NT, install a third party service layer code. Then install a DMI browser of your choice. Copy the files from the NTPERM\DMI subdirectory onto your hard disk. Select Run from the Start menu and execute the PCNET.EXE instrumentation code that you copied to your hard disk. Then open the DMI browser and follow the steps necessary to add the PCNET.MIF component. Once the AMD PCNet component is installed, you can select it and view any parameter with the browser. NOTE: If more than 1 AMD controller is located in the system, the browser will only show values for one of them. 7.0 Trademarks and Notices ____________________________ The following terms are trademarks of the IBM Corporation in the United States or other countries or both: IBM OS/2 Netfinity Microsoft and Windows NT are trademarks or registered trademarks of Microsoft Corporation. AMD, PCNet, and PermaNet are trademarks or registered trademarks of Advanced Micro Devices, Inc. NetWare is a registered trademark of Novell Corporation. SCO is a registered trademark of Santa Cruz Operations. Other company, product, and service names may be trademarks or service marks of others. THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE AND MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM GRANTS NO LICENSES TO ANY PATENTS OR COPYRIGHTS. Note to U.S. Government Users -- Documentation related to restricted rights -- Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp. Revision History 4/15/98 Original release