IBM* Hot-Plug PCI System Bus Driver v1.08c for IntranetWare I (NetWare v4.11/v4.2) and Novell NetWare v5.x Installation Instructions Readme.txt Version 1.08c CONTENTS --------- 1.0 Hot-Plug PCI Installation Overview for IntranetWare (NetWare v4.11/v4.2) and Novell NetWare v5.x 1.1 Overview 1.2 Minimum requirements 1.3 Limitations 1.4 Enhancements 1.5 Level of Recommendations and Prerequisites for the Update: 1.6 Dependencies: 2.0 Change History 3.0 Installation and Setup Instructions 3.1 Installation steps for NetWare v4.11/v4.2 3.2 Installation steps for NetWare v5.x 4.0 How to perform Hot-Plug PCI Operations 4.1 Required steps in Hot-Plug Operations 4.1.1 Removing an adapter 4.1.2 Replacing an adapter 4.1.3 Adding a new adapter to an empty slot 4.2 Hot-Plug PCI driver support 4.2.1 IBM Netfinity 10/100 Fault Tolerant Adapter 4.2.2 IBM 10/100 EtherJet PCI Adapter, the IBM Netfinity Ethernet Adapter, and the IBM Netfinity Ethernet Adapter 2 4.2.3 IBM Netfinity Gigabit Ethernet Adapter SX 4.2.4 IBM PCI Token-Ring Adapter 4.2.5 IBM ServeRAID II/3H/3L/4L/4M/4H/4Lx/4Mx PCI Ultra SCSI Adapter 4.2.6 How to determine if your driver supports Hot-Plug PCI Operations 4.3 Warnings about incorrect usage of Hot Plug PCI. 5.0 Troubleshooting hot plug PCI operations 5.1 Basic Troubleshooting 5.1.1 Attention Indicator LED 5.1.2 IBMSBD.NLM messages 5.1.3 Adapter Driver error messages 5.2 Advanced Troubleshooting 5.2.1 How to determine if the problem is with the adapter driver or the hot-plug driver. 5.2.2 Use of switches and log file for IBMSBD driver 5.2.3 Interrupt handling 5.2.4 NCMCON issues 6.0 Web Sites and Support Phone Number 7.0 Trademarks and Notices 8.0 Disclaimer 1.0 Hot-Plug PCI Installation Overview for IntranetWare (NetWare v4.11/v4.2) and Novell NetWare v5.x 1.1 Overview The Hot Plug PCI support for NetWare v4.11/v4.2/v5.x provided by IBM is compliant with many different specifications including full compliance with the NetWare System Bus Driver specification v1.01, PCI v2.1, and the PCI Hot-Plug PCI v1.1 specification. The IBM Hot Plug PCI system support consists of an interlock switch and a set of two LED's for each hot plug PCI slot. One LED will remain on when power is ON to the given slot. The other LED will indicate that attention is required to that slot. Slots that do not have these devices are NOT hot plug slots. All hot plug operations must be controlled through a console provided by Novell. IN NO CASE SHOULD HOT PLUG OPERATIONS BE DONE WITHOUT FIRST REMOVING POWER FROM THE SLOT THROUGH THE NETWARE CONFIGURATION MANAGER CONSOLE (NCMCON). IF A SLOT DOES NOT HAVE AN INTERLOCK, DO NOT REMOVE THE ADAPTER. DOING SO CAN CAUSE SERIOUS DAMAGE TO THE SYSTEM AND ADAPTER. The order of events in any hot-plug operation are: - Load the appropriate drivers (as described in Section 4.2) to provide hot plug PCI support. - Go to the NetWare Configuration Manager Console (NCMCON) - Choose an add or remove operation for the given slot. - When the adapter power is OFF, open the interlock and remove, replace or add an adapter and any necessary cabling. - Close the interlock and return to the NCMCON console. NOTE: The power to a slot cannot be turned ON until the interlock is closed for the given slot. The position of the interlock switch (opened or closed) is not important if no adapter is in the given slot. - In the case of adding a new adapter or replacing an old one, the NCMCON console will prompt you to turn on the newly added adapter. - If selected, the adapter power is turned ON and the adapter is configured. At this point, if you are using a LAN driver, HWDETECT.NLM will run and load the appropriate driver for you. If you are using any other type of adapter, you will have to go to the system console and manually load the appropriate driver. NOTE: In the case of a SCSI controller, you may need to issue the console command 'SCAN FOR NEW DEVICES' prior to the drive being recognized by NetWare. 1.2 Minimum requirements The minimum system requirements are: - Any IBM Netfinity/eserver xSeries server with Hot Plug PCI slots except the IBM Netfinity 8500R 7RY, 8RY and IBM eserver xSeries 370. The IBM Netfinity 8500R 7RY, 8RY and IBM eserver xSeries 370 use a different Hot Plug PCI system Bus Driver. NOTE: The IBMSBD.NLM driver is designed not to load on any system that does not have Hot Plug PCI slots including non-IBM systems. If you wish to verify that your system hot-plug subsystem is working properly, load the IBMSBD.NLM driver with the -DETECT flag. (ie. LOAD IBMSBD -DETECT). A message will be displayed on the console which informs the user as to whether the driver believes the system to be an IBM Hot Plug PCI System or not. - IBM Hot Plug PCI System Bus Driver v1.08c (IBMSBD.NLM) provided by this diskette. - An adapter and Novell NetWare adapter driver that supports the ODI v3.31 specification or NWPA v3.00b specification published by Novell. and either: - Novell IntranetWare I (NetWare v4.11/v4.2) with Support Pack 5a or later. or - Novell NetWare v5.x The IBMSBD.NLM module from this diskette should be installed using the NWCONFIG utitlity or during the NetWare v5 installation program. To bypass this step, copy the IBMSBD.NLM and IBMSBD.HDI modules to the SYS:\SYSTEM and C:\NWSERVER directories on the hot plug PCI-capable server. Sections 2 and 3 below regarding operations and troubleshooting are still valid. NOTE: Novell is not providing the support modules to allow support for any version of Novell NetWare prior to Novell IntranetWare I (NetWare v4.11/v4.2). NOTE: To add a new adapter to an empty slot, the server must have the MPS14.PSM (NetWare v4.11/v4.2/v5.x) and SMP.NLM (not used in NetWare v5.x) modules loaded in the STARTUP.NCF to have interrupts properly handled. Failure to have these modules loaded may prevent clients from connecting to the server after a hot plug PCI operation. 1.3 Limitations - Bridge adapters or PCI devices containing PCI-to-PCI bridges are NOT supported. - Some LAN adapter drivers may not handle interrupts correctly if their wake-on-lan setting is active after being hot-added. The driver will normally load, but clients will not be able to attach to the server through that adapter. - Multi-Function PCI devices are supported as long as the multi-function capability is not provided with or through a PCI-to-PCI bridge. - Video adapters are not supported in the hot plug PCI environment due to I/O space limitations and restrictions. - Devices that are not PCI v2.1 compliant or that do not implement the PCI presence detection pins are not supported. - Device drivers that are not LAN ODI v3.31 compliant or SCSI NWPA v3.00b compliant are NOT supported. - Non-PCI devices are not hot pluggable. - HWDETECT.NLM, a Novell provided module, may not find the correct driver if more than one driver is capable of loading for the given adapter. - HWDETECT.NLM may give an error about not being able to open the SYS:\SYSTEM\AUTOEXEC.NCF file. Ignore this message by pressing Enter and proceeding through the driver detection. - Because of errors encountered in testing, HWDETECT.NLM is not provided by IBM. If you want the capability of being able to auto-detect the correct driver for newly added adapters, download the latest HWDETECT.NLM from the Novell web site. The URL to find the latest version of HWDETECT.NLM from Novell's web site is: http://support.novell.com/search/ff_index.htm 1.4 Enhancements v1.08c of the hot plug PCI support was changed to allow the IBM ServeRAID-4Mx/4Lx/4L/4M/4H Ultra160 SCSI controllers to initialize properly. This release of software is compatible with all IBM hot plug PCI systems using the requirements mentioned in Section 1.2. NOTE: The IBM Netfinity 8500R 7RY, 8RY and IBM eserver xSeries 370 is not supported with this diskette. This server has a unique system bus driver diskette release. 1.5 Level of Recommendations and Prerequisites for the Update: All IBM eserver xSeries/Netfinity hot plug PCI capable servers released PRIOR to 2Q2001 are supported by this version of software drivers. 1.6 Dependencies: The IBM Hot Plug System Bus Driver requires five drivers in the AUTOEXEC.NCF file plus several other support files in order to perform hot plug operation. NOTE: These operations are all performed by the IBM Hot Plug PCI System Bus Driver Installation Program and the installation steps in Section 2.0. (Note: Some drivers have their DOS date timestamps changed with different) ( versions of Support Packs and NOS releases. Only drivers whose ) ( NetWare version and/or timestamp changes are listed as 'updated'. ) ( If the NetWare timestamp does not change, the driver is identical ) ( regardless of the DOS date timestamp on it. ) The five drivers required in the AUTOEXEC.NCF are: (these are order dependent) ODINEB.NLM 12,824 5-15-98 4:32pm (v1.09) IOCONFIG.NLM 2,810 6-02-98 9:13am (v1.00) NCM.NLM 14,320 6-08-99 10:40am (v1.10) IBMSBD.NLM 113,576 4-19-01 1:43pm (v1.08c) (updated) NCMCON.NLM 25,605 6-04-99 2:37pm (v1.16) In addition, several other support files require replacement in order for Hot Plug PCI Operations to work correctly. The IBMSBD.NLM module requires the following files be replaced: NEB.NLM 10,929 8-28-98 2:27pm (v1.01) NBI.NLM 31,531 9-17-98 11:25am (v2.25) NCMCON.CFG 8,352 3-07-00 11:28am For all Ethernet Drivers, the following support files must be replaced: ETHERTSM.NLM 12,507 1-25-00 4:11am (v3.81) (updated) MSM.NLM 95,676 7-13-00 10:58am (v3.98a) (updated) For all Token-Ring Drivers, the following support files must be replaced: TOKENTSM.NLM 12,689 3-05-99 3:28pm (v3.77) MSM.NLM 95,676 7-13-00 10:58am (v3.98a) (updated) For all FDDI Drivers, the following support files must be replaced: FDDITSM.NLM 12,787 3-05-99 3:15pm (v3.74) MSM.NLM 95,676 7-13-00 10:58am (v3.98a) (updated) For all SCSI Disk Controllers, the following support files must be replaced: SCSIHD.CDM 25,645 11-23-99 4:16pm (v1.36a) SCSICD.CDM 25,814 11-23-99 4:16pm (v1.34k) SCSI2TP.CDM 38,047 11-23-99 4:16pm (v1.02q) NWASPI.CDM 15,734 5-14-98 2:41pm (v2.00) NWPALOAD.NLM 3,219 11-23-99 4:16pm (v3.00) NWPAMS.NLM 73,905 11-23-99 4:16pm (v2.34) NWPAIO.NLM 34,491 11-23-99 4:16pm (v2.34) NPAPATCH.NLM 1,989 6-21-99 6:41pm (v1.02) NWPA.NLM 94,727 11-23-99 4:16pm (v3.03) The supported drivers shipped on this diskette are: - IBM PCI Token-Ring Adapter IBMTRPO.LAN 97,225 10-20-99 2:47am (v2.47) (updated) IBMTRPO.LDI 47,680 2-04-01 11:37am (updated) IBMCOS.NLM 27,414 8-12-98 12:00pm (v1.01) - IBM EtherJet 10/100 PCI Adapter CE100B.LAN 83,909 1-06-01 9:29pm (v3.29) (updated) CE100B.LDI 41,219 2-14-01 4:13am (updated) IANS.LAN 113,961 1-10-01 4:24am (v3.24) (updated) IANS.LDI 1,270 12-28-00 1:00am (updated) - IBM Netfinity Gigabit Adapter SX CE1000.LAN 84,632 3-16-01 3:09pm (v2.72) (updated) CE1000.LDI 9,738 3-16-01 2:57pm (updated) IANS.LAN 113,961 1-10-01 4:24am (v3.24) (updated) IANS.LDI 1,270 12-28-00 1:00am (updated) - IBM ServeRAID II/3-H/3-L Ultra SCSI Adapter IPSRAID.HAM 30,583 3-28-01 11:51pm(v4.70q) (updated) IPSRAID.DDI 9,263 3-28-01 10:47pm (updated) - IBM Netfinity 10/100 Fault Tolerant Adapter PCNTNW.LAN 26,927 1-05-00 10:24am (v4.18) PCNTNW.LDI 19,579 4-08-99 1:12pm - Other files on the diskette are: PINSTALL.NLM IBM Hot Plug PCI System Bus Driver Installation Program (Updated) IBMSBD.TXT This file. (updated) CHANGES.TXT Change log contents (also included in Section 2.0) CPQPATCH.NLM Patch file written by Compaq** and Novell** to fix a memory management problem where multiple adapters would be allocated memory within a single 4K range, however, when an adapter was unloaded, the server would abend because the full 4K was returned to inactive storage even though an adapter was still using the memory. The patch, courtesy of our friends at Compaq**, patches the memory release API's so that if any adapter is still using memory within the 4K range, the range is not returned to inactive storage until all drivers using the memory space have unloaded. This patch is required for all versions of NetWare from v5.00a through v5.00g. All other versions of NetWare, including later versions of NetWare v5 do not exhibit this problem. The patch will not load if the version of NetWare does not exhibit the problem. 2.0 Change History -------------------- ********************** * v1.08c Changes * ********************** Added the following device drivers... CE100B.LAN CE100B.LDI CE1000.LAN CE1000.LDI IANS.LAN IANS.LDI ASCONF.NLM Updated the following device drivers... IBMSBD.NLM MSM.NLM ETHERTSM.NLM IPSRAID.HAM IPSRAID.DDI PCNTNW.LAN PCNTNW.LDI PINSTALL.NLM CHANGES.TXT IBMSBD.TXT Removed the following device drivers... IBMGE.LAN IBMGE.LDI CIBMFE.LAN CIBMFE.LDI IBMAFT.NLM PCNTNW.RED IPSRAID.RED IBMRNIC.NLM Fixed a problem of IBMSBD.NLM assigning the same memory address to two different IBM ServeRAID-4Lx/4Mx/4L/4M/4H Ultra160 SCSI Controllers. Fixed a problem of IBMSBD.NLM assigning interrupt value FF to adapters. The adapter driver may not load or may not load correctly if interrupt value FF is assigned. Design change to send a second power-on command to each slot to allow the IBM ServeRAID-4Lx/4Mx/4L/4M/4H Ultra160 SCSI Controllers to be initialized correctly. Fixed an error message to correctly tell user when a hot add operation failed. Original message was only reported on the console and not in the NCMCON manager. Updated PINSTALL.NLM to copy drivers to the c:\nwserver\drivers subdirectory. End of v1.08c changes. ********************** * v1.06a Changes * ********************** Added the following device drivers... IBMGE.LAN IBM Netfinity Gigabit SX Adapter driver v1.29 IBMGE.LDI IBM Netfinity Gigabit SX Adapter driver support file IBMAFT.NLM IBM Netfinity Gigabit SX, IBM Netfinity Ethernet Adapter and IBM Netfinity Ethernet Adapter 2 Fault Tolerant Device Driver v3.22 CIBMFE.LAN IBM Netfinity Ethernet Adapter and IBM Netfinity Ethernet Adapter 2 Device Driver CIBMFE.LDI IBM Netfinity Ethernet Adapter and IBM Netfinity Ethernet Adapter 2 Device Driver Descriptor File PCNTNW.RED Readme File for Netfinity Fault Tolerant Adapter IBMCOS.NLM IBM PCI Token-Ring Adapter Redundant NIC support driver Updated the following device drivers... ETHERTSM.NLM FDDITSM.NLM IPSRAID.DDI IPSRAID.HAM IPSRAID.RED IBMSBD.NLM IBMSBD.TXT MSM.NLM NBI.NLM NCM.NLM NCMCON.NLM NWPA.NLM NWPAIO.NLM NWPAMS.NLM PCNTNW.LAN PCNTNW.LDI PINSTALL.NLM SCSIHD.CDM Removed the following drivers IBMFE.LAN IBMFE.LDI IBMFE.RED PCNET40.TXT IPSADM.NLM IPSRADM.NLM - Added support for the Netfinity 8500R, Netfinity 6000R, and Netfinity 7600 servers. - Updated drivers for all supported IBM adapters. - The installation program was changed to fix a problem where the NCMCON.NLM modules was placed before the IBMSBD.NLM module by the PINSTALL.NLM installation program. The problem would be seen as all slots showing up as NOT being hot-pluggable and all slots being shown as powered on, even though they were powered off. End changes v1.06a ********************** * v1.05 Changes * ********************** -Support added for NetWare v5.1 -Fixed an issue where replace operation would not work with the IBM Netfinity Ethernet Adapter and IBM Netfinity Ethernet Adapter 2 because the CIBMFE.LAN Driver was working in persistent mode. - Added messages for wrong bus frequency on 66MHz capable slots ********************** * v1.04 Changes * ********************** Not released, development test version ********************** * v1.03 Changes * ********************** Updated the following device drivers... ETHERTSM.NLM FDDITSM.NLM IBMFE.LAN IBMFE.LDI IBMFE.RED IPSRAID.DDI IPSRAID.HAM IPSRAID.RED IBMSBD.NLM IBMSBD.TXT IBMTRPO.LAN IBMTRPO.LDI MSM.NLM NBI.NLM NCM.NLM NCMCON.NLM NWPA.NLM NWPAIO.NLM NWPAMS.NLM PCNTNW.LAN PCNTNW.LDI PCNET40.TXT PINSTALL.NLM RNIC.NLM SCSIHD.CDM TOKENTSM.NLM Design change to support future IBM Netfinity Server systems where the start address of resources is not on a 4KB boundary (I/O) or 1MB boundary (Mem and PFMem) Design change to add ConsolePrintf statements to show user what interrupt assignment was actually made Remove bridge adjustment because BIOS provides big enough resource windows already. Design change to export the resource assignments to the console so that a user would know what was assigned to the added adapter. Updated drivers for all supported IBM adapters. End changes v1.03 ********************** * v1.02 Changes * ********************** Not released, development test version ********************** * v1.01 Changes * ********************** Updated the following device drivers... ODINEB.NLM NEB.NLM MSM.NLM TOKENTSM.NLM IBMTRPO.LAN IBMTRPO.LDI RNIC.NLM IBMSBD.TXT The IBMTRPO.LAN file was updated to fix a problem found when loading the IBM PCI Token-Ring Adapter as the third or later network adapter in the system. CAUSE: If an interrupt was received on one of the first two network adapters while the IBMTRPO.LAN driver was registering with the Novell Event Bus (NEB), the system would hang. The IBMTRPO.LAN driver registers when the driver is loaded. SOLUTION: Replace the IBMTRPO.LAN file listed above with v2.43 or later. End changes since v1.01 ********************** * v1.00 Changes * ********************** Original Release (May 1998) 3.0 Installation and Setup Instructions ----------------------------------------- 3.1 Installation steps for NetWare v4.11/v4.2 To install the IBM Hot Plug PCI driver and support files on this diskette to the appropriate directories and add the appropriate entries to SYS:\SYSTEM\AUTOEXEC.NCF: 1. Start the NetWare server and go to the NetWare console. 2. Type LOAD CLIBAUX. 3. Type LOAD INSTALL and press Enter. 4. From the installation menu, choose 'Product Options' 5. From the Product Options menu, choose 'Product Not Listed' 6. Place the IBM Hot Plug PCI driver diskette (this diskette) into the floppy drive. 7. Press Enter to accept the default path of A:\ NOTE: The contents of this diskette can also be copied to a subdirectory on the server (in either the DOS or NetWare partitions) and the path in step 6 changed to match the path to the subdirectory. 8. After a brief moment, the Main Menu of the IBM Hot Plug PCI System Bus Driver v1.06 Installation Program is displayed. 9. Choose 'Install NetWare v4.11/v4.2/v5.x Support for IBM Hot Plug PCI System' 10. Type the path where this diskette image is located or accept the default of A:\ and press Enter. NOTE: If the installation program immediately returns to the Main Menu when selecting a path that is not on a NetWare volume, it is because the LIBUPI.EXE package has not been applied. The LIBUPI.EXE package contains a new CLIB.NLM module that is required by the installation program so that file accesses to the DOS partition will be successful. Before the installation program can continue, apply the LIBUPI.EXE package fixes and then restart these installation instructions. The LIBUPI.EXE file can be obtained from the Novell web site at URL: http://support.novell.com/search/ff_index.htm and entering the filename LIBUPI. 11. After the file copy takes place, press Escape to return to the Main Menu. 12. Choose 'Exit' to return to the Install Program. 13. After installation go into the 'NCF files options' and verify the following files were added to autoexec.ncf in this order (edit the file to change the order if necessary): ODINEB.NLM, IOCONFIG.NLM, NCM.NLM,IBMSBD.NLM, AND NCMCON.NLM. 14. Press Escape two times then 'Yes' to exit the NetWare Installation Program. 15. DOWN and restart the server to have the required modules load. NOTE: If installation is successful, you should see the the NetWare Configuration Manger Console (NCMCON) showing the available Hot Plug PCI slots, their current status, and any adapters that are currently in the Hot Plug PCI slots. 3.2 Installation steps for NetWare v5.x To determine if the IBM Hot Plug PCI Support has been installed on your Hot Plug PCI capable server, issue the following command: MODULES IBMSBD.NLM If the module returned is v1.08b, all appropriate drivers have been updated and further installation steps are NOT required. If no module version is displayed, or if the module displayed is less than v1.08b, additional installation steps are required. The additional installation steps can be accomplished one of two ways: 1) Install NetWare v5.0 Support Pack 2 or later. NetWare v5.1 does not require a Support Pack. 2) Install the IBM Hot Plug PCI System Bus Driver by following these steps: a) Start the NetWare server and go to the NetWare console b) Type: NWCONFIG and press Enter. c) From the installation menu, choose 'Product Options' d) From the Product Options menu, choose 'Product Not Listed' e) Place the IBM Hot Plug PCI driver diskette (this diskette) into the floppy drive. f) Press Enter to accept the default path of A:\ NOTE: The contents of this diskette can also be copied to a subdirectory on the server (in either the DOS or NetWare partitions) and the path in step 6 changed to match the path to the subdirectory. g) After a brief moment, the Main Menu of the IBM Hot Plug PCI System Bus Driver Installation Program is displayed. h) Choose 'Install NetWare v4.11/v4.2/v5.x Support for IBM Hot Plug PCI System' i) Type the path where this diskette image is located or accept the default of A:\ and press Enter. j) After the file copy takes place, press Escape to return to the Main Menu. k) Choose 'Exit' to return to the Install Program. l) Press Escape two times then 'Yes' to exit the NetWare Installation Program. m) Type: RESTART SERVER to have the required modules load. 4.0 How to perform Hot-Plug PCI Operations 4.1 Required steps in Hot-Plug Operations NOTE: Opening an adapter interlock switch will turn off the power to the slot. If a device driver was loaded for that slot, the system will most likely hang, requiring the system to be rebooted. 4.1.1 Removing an adapter 1. Verify that the IBMSBD.NLM and NCMCON.NLM modules are loaded. 2. Go to the NetWare Configuration Manager Console (NCMCON) screen. 3. Select the slot where the adapter you want to remove is located and Press Enter. 4. Select 'Remove Adapter' and press Enter. 5. If a driver is loaded for the adapter, you will get a prompt asking if you want to unload the driver. You must have the driver unloaded for the power to the slot to be removed. 6. If you receive a message stating that the driver could not be unloaded, go to the system console and manually remove the driver. Return to NCMCON after the driver has been unloaded and repeat steps 3 through 5. 7. Verify that the status for the slot reads 'Powered off'. 8. Open the top cover of the system using the two thumb screws at the rear of the system. 9. Verify that the power-on light status for the adapter is OFF. If the light is ON, go back to the console and verify that the given slot is powered OFF. NOTE: NEVER REMOVE AN ADAPTER FROM A SLOT WITH THE SLOT POWER STILL ON. THIS COULD RESULT IN A SYSTEM HANG AND/OR SERIOUS DAMAGE TO THE ADAPTER CARD AND/OR SYSTEM UNIT. 10. Remove the interlock by swiveling the vertical lockdown counterclockwise and lift the interlock switch up. 11. Remove the adapter from the slot. 4.1.2 Replacing an adapter 1. Verify that the IBMSBD.NLM and NCMCON.NLM modules are loaded. 2. Go to the NetWare Configuration Manager Console (NCMCON) screen. 3. Select the slot where the adapter you want to remove is located and Press Enter. 4. Select 'Remove Adapter' and press Enter. 5. If a driver is loaded for the adapter, you will get a prompt asking if you want to unload the driver. You must have the driver unloaded for the power to the slot to be removed. 6. If you receive a message stating that the driver could not be unloaded, go to the system console and manually remove the driver. Return to NCMCON after the driver has been unloaded and repeat steps 3 through 5. NOTE: Beware that unloading the driver in most cases unloaded it for ALL instances of the adapter in the system. See Section 2.2 for any special commands that may be required to remove an individual instance of the driver. In the case where a driver does not have a special command to unload it and NCMCON is not able to unload the driver, a new device driver supporting 'instance unload' must be obtained from the adapter vendor. 'Instance unload' is part of the Novell NetWare ODI v3.31 LAN Specification and the Novell NetWare NWPA v3.00b Disk Specification. 7. Verify that the status for the slot reads 'Powered off'. 8. Open the top cover of the system using the two thumb screws at the rear of the system. 9. Verify that the power-on light status for the adapter is OFF. If the light is ON, go back to the console and verify that the given slot is powered OFF. NOTE: NEVER REMOVE AN ADAPTER FROM A SLOT WITH THE SLOT POWER STILL ON. THIS COULD RESULT IN A SYSTEM HANG AND/OR SERIOUS DAMAGE TO THE ADAPTER CARD AND/OR SYSTEM UNIT. 10. Remove the interlock by swiveling the vertical lockdown counterclockwise and lift the interlock switch up. 11. Remove the adapter from the slot. 12. Place the new adapter in the slot and close the interlock switch. Swivel the vertical lockdown clockwise to lock the interlock in place. 13. Go back to the NCMCON screen. A message should be displayed asking if power should be turned on to the given slot. 14. After selecting to turn on the power to a given slot, you will be prompted to verify that any necessary cables have been attached to the adapter card prior to power being applied. 15. Press Enter at the cable reminder screen. The adapter power will be turned on, the adapter configured, and a message displayed as to the success of adding the adapter. NOTE: If an error occurs during power ON and configuration of the adapter, the power to the slot will be turned back OFF, and an appropriate message displayed on the NCMCON screen and the system console screen. If an adapter does not power up, go to Section 3.0 Troubleshooting Hot Plug PCI Operations. NOTE: In the case of a network adapter, be sure to BIND the appropriate protocols to the driver after the driver is loaded. NOTE: In the case of a SCSI controller, you may need to issue the console command 'SCAN FOR NEW DEVICES' prior to the drive being recognized by NetWare. NOTE: Drivers for newly added adapters do not automatically reload. Please see the instructions for the specifically supported adapters for information on how to reload drivers. 16. The status of the adapter in the NCMCON screen will show READY if a driver is not loaded for the given slot, and ACTIVE when a driver is loaded. 4.1.3 Adding a new adapter to an empty slot NOTE: Adding a new adapter to a slot with an adapter already in the slot is the same as replacing an adapter. The steps to replacing an adapter are given in Section 4.1.2 above. NOTE: To add a new adapter to an empty slot, the server must have the MPS14.PSM and SMP.NLM modules loaded in the STARTUP.NCF to have interrupts properly handled. Failure to have these modules loaded may prevent clients from connecting to the server. 1. Verify that the IBMSBD.NLM and NCMCON.NLM modules are loaded. 2. Go to the NetWare Configuration Manager Console (NCMCON) screen. 3. Verify that the status for the slot reads 'Powered off'. 4. Open the top cover of the system using the two thumb screws at the rear of the system. 5. Verify that the power-on light status for the adapter is OFF. If the light is ON, go back to the console and verify that the given slot is powered OFF. NOTE: NEVER REMOVE AN ADAPTER FROM A SLOT WITH THE SLOT POWER STILL ON. THIS COULD RESULT IN A SYSTEM HANG AND/OR SERIOUS DAMAGE TO THE ADAPTER CARD AND/OR SYSTEM UNIT. 6. Remove the interlock by swiveling the vertical lockdown counterclockwise and lift the interlock switch up. 7. Remove the adapter from the slot. 8. Place the new adapter in the slot and close the interlock switch. Swivel the vertical lockdown clockwise to lock the interlock in place. 9. Go back to the NCMCON screen. A message should be displayed asking if power should be turned on to the given slot. 10. After selecting to turn on the power to a given slot, you will be prompted to verify that any necessary cables have been attached to the adapter card prior to power being applied. 11. Press Enter at the cable reminder screen. The adapter power will be turned on, the adapter configured, and a message displayed as to the success of adding the adapter. NOTE: If an error occurs during power ON and configuration of the adapter, the power to the slot will be turned back OFF, and an appropriate message displayed on the NCMCON screen and the system console screen. If an adapter does not power up, go to Section 3.0 Troubleshooting Hot Plug PCI Operations. NOTE: In the case of a network adapter, be sure to BIND the appropriate protocols to the driver after the driver is loaded. NOTE: In the case of a SCSI controller, you may need to issue the console command 'SCAN FOR NEW DEVICES' prior to the drive being recognized by NetWare. NOTE: Drivers for newly added adapters do not automatically reload. Please see the instructions for the specifically supported adapters for information on how to reload drivers. 12. The status of the adapter in the NCMCON screen will show READY if a driver is not loaded for the given slot, and ACTIVE when a driver is loaded. 4.2 Hot-Plug PCI driver support IBM has tested and certified the following adapters in hot plug PCI systems. Adapters other than the ones listed below may work. See Section 4.2.6 for steps on determining whether an adapter driver is capable of supporting hot plug PCI operations. NOTE: For questions about non-IBM adapters supporting hot plug PCI, please contact the appropriate adapter vendor. Information in Section 2.2.5 can be used when contacting the adapter vendor to determine level of hot plug PCI support provided. 4.2.1 IBM Netfinity 10/100 Fault Tolerant Adapter This adapter is fully supported in hot plug PCI operations. The driver provided with this diskette, PCNTNW.LAN, should be used to provide hot plug PCI support. If the PCNTNW.LAN driver is already loaded, and a second IBM Netfinity 10/100 Fault Tolerant Adapter is loaded, you must use the following command to find the new adapter: LOAD PCNTNW SCAN The latest version of this driver can be found at: http://www.pc.ibm.com/us/searchfiles.html on the World Wide Web. 4.2.2 IBM 10/100 EtherJet PCI Adapter, the IBM Netfinity Ethernet Adapter, and the IBM Netfinity Ethernet Adapter 2 These adapters are fully supported in hot plug PCI operations. The driver provided with this diskette, CE100B.LAN, should be used to provide hot plug PCI support and is compatible with all versions of the listed adapters. The CE100B.LAN driver will auto-detect newly added adapters when it is reloaded. Once the adapter is hot added to the system, use the following command to load the driver for this adapter if HWDETECT does not find the correct driver: LOAD CE100B No additional information is provided with this diskette for this adapter. The latest version of this driver can be found at: http://www.networking.ibm.com/servers on the World Wide Web. 4.2.3 IBM Netfinity Gigabit Ethernet Adapter SX This adapter is fully supported in hot plug PCI operations. The driver provided with this diskette, CE1000.LAN, should be used to provide hot plug PCI support. The CE1000.LAN driver will auto-detect newly added adapters when it is reloaded. Once the IBM Netfinity Gigabit Ethernet Adapter SX is hot added to the system, use the following command to load the driver for this adapter: LOAD CE1000 No additional information is provided with this diskette for this adapter. The latest version of this driver can be found at: http://www.networking.ibm.com/servers on the World Wide Web. 4.2.4 IBM PCI Token-Ring Adapter This adapter is fully supported in hot plug PCI operations. The driver provided with this diskette, IBMTRPO.LAN, should be used to provide hot plug PCI support. The IBMTRPO.LAN driver will auto-detect newly added adapters when it is reloaded. Once the IBM PCI Token-Ring Adapter is hot added to the system, use the following command to load the driver for this adapter: LOAD IBMTRPO NOTE: If the new adapter is the first adapter in the network, it is necessary to set the datarate for the adapter to the speed that your Token-Ring network operates. The following command will allow for 16Mbps operations: LOAD IBMTRPO datarate=m16 For 4Mbps operation, replace the m16 with m4 in the previous command. NOTE: The redundant NIC capability provided by the IBMTRPO.LAN and IBMRNIC currently does not work with NetWare 5.1 and Support Pack 1a or later. This diskette will be updated with IBMRNIC.NLM when this support is available. For the redundant NIC capability provided by the IBMTRPO.LAN, you will have to re-establish the failover pair after a hot plug PCI operation. For more information about the parameters that should be to re-establish the failover pair, please see the document at the following web site: http://www.networking.ibm.com/trl/trlrnic.html No additional information is provided with this diskette for this adapter. The latest version of this driver can be found at: http://www.networking.ibm.com/servers on the World Wide Web. 4.2.5 IBM ServeRAID II, IBM ServeRAID-3H/3L Ultra2 SCSI, IBM ServeRAID-4L/4M/4H/4Lx/4Mx Ultra160 SCSI Adapter This adapter is fully supported in hot plug PCI operations. The driver provided with this diskette, IPSRAID.HAM, should be used to provide hot plug PCI support. NOTE: The original IBM ServeRAID adapter is not supported for hot plug operations. The IPSRAID.HAM driver will auto-detect newly added adapters when it is reloaded. Once the IBM ServeRAID II/3H/3L/4L/4M/4H/4Mx/4Lx Ultra SCSI Adapter is hot added to the system, use the following command to load the driver for this adapter: LOAD IPSRAID NOTE: Loading the IPSRAID adapter may take several minutes to complete. This is because the driver searches all SCSI channels for all fifteen possible SCSI devices. SCSI devices have up to five seconds to timeout. Control will be returned to the console prior to the IPSRAID SCSI search completion so that other server console commands can be issued. The IPSRAID driver requires a special command to unload a single instance of the driver. The command to remove the single instance is: REMOVE STORAGE ADAPTER Ax where x is the adapter number. NOTE: The adapter numbers for Netfinity servers start at A1 for the integrated RAID controller. For other systems, it is dependent on the order in which the slot is found during initial system scan (ie Slots on bus 1 will be found in the order prior to slots in bus 2, with the exception that the hot-plugged adapters will be the last in the list.) Example (You have one ServeRAID II adapter in slot 2 and slot 5 on a Netfinity 5500). The ServeRAID II adapters adapters are labeled as follows: A1 is the integrated RAID controller. A2 is the ServeRAID 3H adapter in slot 5. A3 is the ServeRAID II adapter in slot 2. The latest version of this driver can be found at: http://www.pc.ibm.com/us/searchfiles.html on the World Wide Web. 4.2.6 How to determine if your driver supports Hot-Plug PCI Operations NOTE: This section shows how to handle devices that are not on the IBM approved list of hot plug PCI devices. Some devices may work correctly, but have not been tested and approved by IBM. NOTE: There are no changes to the physical adapter required to support hot plug PCI operations. Many other adapter vendors will be providing drivers that meet the required Novell specifications for hot plug PCI in the future. However, there are times where you may have a driver and will not know whether the driver is hot plug compatible. The following is a list of methods to determine if a given driver supports hot plug PCI operations. 1. Almost any driver will allow a singular instance in the hot plug environment. NOTE: The limitations to this are any adapters with PCI-to-PCI bridges. Because of limitations in how NetWare handles interrupts in NetWare v4.11/v4.2/v5.x, any device with a PCI-to-PCI bridge will not be successfully added. These devices will generate a message stating that they are not supported during PCI operations. 2. The device can be powered OFF through the NCMCON screen with a driver loaded or has a command-line option to remove a single instance of the driver. NOTE: A driver that forces all instances of itself to be unloaded is not considered a hot plug PCI driver. 3. Can the driver detect newly added adapters after a hot plug operation? NOTE: Many adapters will not detect new slot numbers because they do a static scan for cards on their first load. If a new card is added, the driver will report that no slots are available. Unloading the adapter (and sometimes the underlying support module, TOKENTSM.NLM, ETHERTSM.NLM, etc) and reloading them will allow the new slots to be seen in most instances. However, this will require unloading the driver for all adapters in the system. 4. Does the driver complain about PCI configuration problems? NOTE: Some older drivers do not allow for PCI configuration resources to be reallocated or changed. These drivers will report that one or more of the PCI resource requirements (IRQs, I/O ports, Memory, or Prefetchable Memory) are not correct/unavailable. 4.3 Warnings about incorrect usage of Hot Plug PCI. Below are several warnings about hot plug PCI operations: 1. Do not remove an adapter from a non hot plug PCI slot. 2. Grounding equipment, including wrist straps, should be used when working inside any system unit to protect against electrostatic discharge (ESD) that could damage system components and adapter cards. 3. Make sure that any adapter card hot added to the system is fully seated before attempting to turn on power. 4. Opening an adapter interlock switch will turn off the power to the slot. If a device driver was loaded for that slot, the system will most likely hang, requiring the system to be rebooted. 5. Do NOT remove the plastic cover over the system components. Removal of the plastic cover exposes system components that may be shorted by adapter brackets during hot plug PCI operations. 6. Processors, memory and integrated systems devices are not hot swappable. 7. Opening the adapter interlock with an adapter powered in the slot or closing the interlock after such an activity may lead to an NMI being reported by the system. If this occurs, the system must be rebooted for the NMI to be cleared. 5.0 Troubleshooting hot plug PCI operations ------------------------------------------- 5.1 Basic Troubleshooting There are several troubleshooting techniques that can be used to determine why a hot plug PCI operation failed. Two LED's are provided for each hot plug PCI capable slot. One LED blinks to indicate that attention is required. The second LED indicates power state. Messages are generated by the NCMCON screen, IBMSBD.NLM driver, and the various adapter drivers. 5.1.1 Attention Indicator LED The Attention Indicator LED is controlled by NetWare. At present, the Attention Indicator LED is used only by device drivers to indicate that an adapter in a given slot needs attention. Not all device drivers support the attention indicator messaging. The Attention Indicator will only be cleared upon successful replacement of the adapter in the slot or by the device driver clearing the condition that led it to turn on the Attention Indicator LED in the first place. 5.1.2 IBMSBD.NLM messages The IBMSBD.NLM IBM System Bus Driver generates messages to indicate change of state in the hot plug PCI system. If the driver is not loaded, no system messages are generated. The messages that you may see generated by the IBMSBD driver will all be proceeded by the IBMSBD: or IBMSBD Error: tags. The messages that may be seen are: "IBMSBD: New Adapter added. Please use the Novell Configuration Manager console (NCMCON) to configure this new adapter." This indicates that a new adapter was added into a previously empty slot. The empty slot can occur as a result of a previous replace or add hot plug PCI operation. This is an information message directing you to use the console (NCMCON) to configure the newly added adapter. "IBMSBD Error: Allocate NEB.AESTag() failed." This error indicates that the IBMSBD driver was unable to allocate an asynchronous event system (AES) tag. Because events happen asynchronously in the hot plug PCI system, IBMSBD must have an AES handle to function. Unloading other NLM's that have AES tags registered will free up AES resources so that the IBMSBD driver can properly load. "IBMSBD Error: Not enough memory to generate event for queue." This error indicates that memory could not be allocated to place a hot plug PCI event onto the internal resource queue. This normally occurs when the system runs out of available memory. To fix this problem, unload other NLM's or add additional memory to the system. "IBMSBD Error: Add Adapter command failed because of empty slot. Slot is x" This messages occurs when NCMCON is directed to add an adapter to a slot that does not currently have an adapter card in it. This error may also occur if a PCI adapter does not meet the PCI v2.1 specification requirement that the adapter use presence pins. The IBMSBD module uses the presence pins to determine when an adapter has been inserted and removed from the system. "IBMSBD: The IBM Hot-Plug PCI controller is not present." This error occurs when an attempt is made to run the IBMSBD module on a system that does not have a hot plug PCI controller. This error may also occur if the hot plug PCI controller is malfunctioning or not working. The -COMMAND -DEBUG switches can be used on the IBMSBD driver to determine if the hot plug controller is working. See Section 3.2.2 for more information about debug switches for the IBMSBD device driver. All other messages are provided through the Novell Configuration Manager Console (NCMCON) screen. For information about problems in NCMCON such as all slots show 'No' in the Hot Plug field or a message appears asking whether to continue waiting another 10 seconds, see Section 3.2.4. If IBMSBD.NLM fails to load with a message stating that a symbol was not found NBIDetect(), this means that an old level of NBI.NLM is being used Replace the NBI.NLM with the one from this diskette and IBMSBD.NLM will load properly. 5.1.3 Adapter Driver error messages Many non hot plug PCI device drivers will not load correctly with the ODI v3.31 or the NWPA v3.00b specifications. If you have such a device driver, first determine if you adapter vendor has a certified driver available. If no such driver exists, you will need to either use a different adapter or lose at least some of the hot plug functionality. Drivers that do not support the Novell specifications may exhibit such problems as: - Failure to see new adapters until unloaded and reloaded. - Failure to support single instance unload. Single instance unload is the ability to unload the driver for a single adapter even though the driver may be supported many adapters. - Failure to be able to register PCI resources such as interrupt, I/O ports, memory or prefetchable memory ranges. Some drivers that support the Novell specification may exhibit problems such as those above if the support modules (NWPA.NLM, ETHERTSM.NLM, TOKENTSM.NLM, FDDITSM.NLM, and NBI.NLM) are down-level. Verify that all drivers are at least at the level of drivers on this diskette. Since these are Novell support modules, check the Novell web site for later versions that may be on this diskette. The web site is http://support.novell.com. 5.2 Advanced Troubleshooting This section contains information that is more technically advanced than the Basic Troubleshooting section. Information contained in this section includes: - How to determine if a problem loading an adapter device driver is caused by the hot plug PCI driver, IBMSBD.NLM, or the device driver itself - debug switches available with the IBMSBD.NLM driver - how interrupts are assigned - NCMCON issues such as no hot plug slots showed, or a query about waiting another ten seconds 5.2.1 How to determine if the problem is with the adapter driver or the hot-plug driver. NOTE: There are no changes to the physical adapter required to support hot plug PCI operations. Many other adapter vendors will be providing drivers that meet the required Novell specifications for hot plug PCI in the future. However, there are times where you may have a driver and will not know whether the driver is hot plug compatible. The following is a list of methods to determine if a given driver supports hot plug PCI operations. 1. Almost any driver will allow a singular instance in the hot plug environment. NOTE: The limitations to this are any adapters with PCI-to-PCI bridges. Because of limitations in how NetWare handles interrupts in NetWare v4.11/v4.2/v5.x, any device with a PCI-to-PCI bridge will not be successfully added. These devices will generate a message stating that they are not supported during PCI operations. 2. The device can be powered OFF through the NCMCON screen with a driver loaded or has a command-line option to remove a single instance of the driver. NOTE: A driver that forces all instances of itself to be unloaded is not considered a hot plug PCI driver. 3. Can the driver detect newly added adapters after a hot plug operation? NOTE: Many adapters will not detect new slot numbers because they do a static scan for cards on their first load. If a new card is added, the driver will report that no slots are available. Unloading the adapter (and sometimes the underlying support module, TOKENTSM.NLM, ETHERTSM.NLM, etc) and reloading them will allow the new slots to be seen in most instances. However, this will require unloading the driver for all adapters in the system. 4. Does the driver complain about PCI configuration problems? NOTE: Some older drivers do not allow for PCI configuration resources to be reallocated or changed. These drivers will report that one or more of the PCI resource requirements (IRQs, I/O ports, Memory, or Prefetchable Memory) are not correct/unavailable. 5. If new device drivers, support modules, and installation of the latest Support Packs does not fix the problem, then proceed to Section 3.2.2 to debug the IBMSBD.NLM module. 5.2.2 Use of switches and log file for IBMSBD driver There are a number of command line switches that can be used to create an IBMSBD.LOG file in the SYS:\SYSTEM directory. This file can be looked at to verify that the IBMSBD.NLM module is working properly. The following are the command line switches and a description of each: The following commands are NOT case sensitive, NOR do they require the leading hyphen. If multiple commands are given, they should be separated by spaces. (ie. LOAD IBMSBD -DETECT DEBUG -COMMAND) /?,-?, ? These flags are used to print out the following list of switches. -DETECT This parameter will allow the IBMSBD.NLM driver to detect if the hot plug PCI system and controller are detected. The driver will print a message to the system console as to its finding and then terminate. This flag cannot be used with any other flag. -DEBUG This parameter must be listed for any debug actions to be logged to the IBMSBD.LOG file. Various system information including version of NetWare, PCI BIOS discovery, Novell Event Bus (NEB) events, Novell HIN numbers, driver deregistration, memory release traces and the PCI Interrupt Routing Options table are documented. -COMMAND This parameter displays the returns codes from the PCI hot plug controller, return codes to NCMCON, and all PCI hot plug operations and return codes. -RESOURCE This parameter designates that resource tables are to be generated in the IBMSBD.LOG file. This parameter must be used in conjunction with one of the following three parameters to generate anything. -IO This parameter, used in conjunction with the -RESOURCE parameter, will generate tables by system bus showing all I/O resources assigned by BIOS and the IBMSBD.NLM module. This parameter also shows all I/O assignments during the hot plug PCI operation. -MEM This parameter, used in conjunction with the -RESOURCE parameter, will generate tables by system bus showing all PCI memory resources assigned by BIOS and the IBMSBD.NLM module. This parameter also shows all memory assignments during the hot plug PCI operation. -PFMEM This parameter, used in conjunction with the -RESOURCE parameter, will generate tables by system bus showing all PCI prefetchable memory resources assigned by BIOS and the IBMSBD.NLM module. This parameter also shows all prefetchable memory assignments during the hot plug PCI operation. -IRQ This parameter shows all system devices by PCI deviceID and vendorID. The information provided shows the slot that the adapter occupies and the IRQ number (1-15) assigned to offset 0x3c of the PCI Configuration Header for the given adapter. Slot numbers of 0000 indicate that the device is an integrated PCI device. Interrupts for reserved system resources and non-PCI devices are not displayed. All information is reported in the IBMSBD.LOG file in the SYS:\SYSTEM directory. -DEVICE This parameter places information in the IBMSBD.LOG file about PCI devices found in the system. Information about the bus, slot number, device/function ID, classCode, VendorID, and device type are logged. -ALL This parameter turns all debug tracking in the driver. This parameter forces all driver internal output to be placed in the SYS:\SYSTEM\IBMSBD.LOG file. The log file is closed when the IBMSBD.NLM driver is unloaded. Be aware that this log file can become rather large quickly (several MB), so it is not recommended that this parameter be used unless directed by HelpCenter service personnel. If a problem arises where you must create the IBMSBD.LOG file, the file can be submitted as part of the call to the HelpCenter for further diagnostic help. 5.2.3 Interrupt handling Interrupts are handled in the following manner: - Only interrupts 9, 10, and 11 will be assigned to hot plug PCI devices. These options are not settable. If during BIOS setup, these three interrupts are reserved for ISA Legacy devices, all hot plug PCI operations will fail. - IRQ 15 will never be assigned to hot plug PCI devices unless an adapter already installed in the server of the same type has already been assigned to IRQ 15. - Interrupts are preserved from the MPS table located in the extended BIOS data area (EBDA) of the system. - For slots that do not have an adapter in them at boot, interrupts are assigned according to the following formula: - If another device that matches the vendorID and deviceID in the PCI Configuration header is found, then the newly added adapter will receive the same interrupt as the other device. - An unused interrupt between 9, 10, and 11 is assigned. - The least used interrupt between interrupts 9, 10, and 11 is assigned. NOTE: There may be instances where a LAN and SCSI controller may be assigned the same interrupt. If this occurs, the LAN adapter may fail to handle interrupts correctly when the SCSI controller accesses the DOS partition and lose connections. If this occurs, it will be necessary to down the server, reboot it, go into System Setup, and manually assign the interrupts so the devices do not share interrupts. 5.2.4 NCMCON issues - If NCMCON.NLM fails to show any slots with 'Yes' in the Hot Plug field, the IBMSBD.NLM module is not loaded. To fix the problem, exit NCMCON, load IBMSBD at the system console, and reload NCMCON. - If you receive a message about Slot Status not being available with a query to wait another 10 seconds, NCM.NLM or one of its support modules, IOCONFIG.NLM or NEB.NLM is not loaded. To fix this problem, exit NCMCON, load the appropriate support modules, load NCM, then NCMCON. It is not necessary for NCM or NCMCON to be loaded for the IBMSBD driver to load properly. - If the adapter names are not displayed correctly in the Adapter Name field of NCMCON, verify that the NCMCON.CFG file is located in the SYS:\SYSTEM subdirectory. - If a fully supported ODI v3.31 LAN device driver cannot be unloaded, verify that ODINEB.NLM is loaded. It can be loaded at the system console after NEB.NLM is loaded. - All SCSI controller drivers must be unloaded from the system console. The following command to remove a single adapter and its volumes from the system: REMOVE STORAGE ADAPTER Ax where x is the adapter number as determined by the scan order of the PCI buses in the system. All integrated devices will be assigned first, followed by adapters in PCI Bus 0, PCI Bus 1, etc. - When using failover pairs in conjunction with hot plug PCI, you should not setup failover pairs using the Netfinity Ethernet Adapter 2 and the Netfinity Fault Tolerant Ethernet Adapter as two independent pairs. Failover pairs should consist of one adapter type or the other, but not both simultaneously. 6.0 WEB Sites and Support Phone Number ---------------- 6.1 IBM Support Web Site: http://www.pc.ibm.com/support 6.2 IBM Marketing Netfinity Web Site: http://www.pc.ibm.com/netfinity 6.3 If you have any questions about this update, or problems applying the update go to the following Help Center World Telephone Numbers URL: http://www.pc.ibm.com/qtechinfo/YAST-3P2QLY.html. 7.0 Trademarks and Notices ---------------------------- The following terms contained in this README, are trademarks or registered trademarks of the IBM Corporation in the United States or other countries: ------------------------------------------ IBM ------------------------------------------ NetFinity ------------------------------------------ ServeRAID ------------------------------------------ EtherJet ------------------------------------------ The following terms contained in this README, are trademarks of other companies as follows: Trademark: Owner: -------------------------------------------------------------- NetWare Novell, Inc. -------------------------------------------------------------- IntranetWare Novell, Inc. -------------------------------------------------------------- Compaq Compaq Computer Corporation -------------------------------------------------------------- 8.0 Disclaimer ---------------------------- 8.1 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. 8.2 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 Corporation.