IBM* Hot-Plug PCI System Bus Driver, version 1.10b for IntranetWare I (Novell NetWare, versions 4.11 and 4.2) and Novell NetWare, version 5.x Installation Instructions Readme.txt Version 1.10b CONTENTS ________ 1.0 Hot-plug PCI installation overview for IntranetWare (Novell NetWare, versions 4.11 and 4.2) and Novell NetWare, version 5.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, versions 4.11 and 4.2 3.2 Installation steps for NetWare, version 5.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 SCSI Adapters 4.3 Warnings about using Hot-plug PCI incorrectly 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 Determining whether the problem is the adapter driver or the Hot-plug PCI driver 5.2.2 Using switches and log files for IBMSBD driver 5.2.3 Interrupt handling 5.2.4 NCMCON issues 6.0 Web site 7.0 Trademarks and notices 8.0 Disclaimer 1.0 Hot-plug PCI installation overview for IntranetWare (Novell NetWare, versions 4.11 and 4.2) and Novell NetWare, version 5.x ________________________________________________________________________ 1.1 Overview ____________ IBM provides Hot-plug PCI (also called Active PCI) support for NetWare, versions 4.11, 4.2, and 5.x that is compliant with several specifications, including full compliance with the following specifications: o NetWare System Bus Driver specification, version 1.01 o PCI, version 2.1 o PCI Hot-plug PCI, version 1.1 The IBM Hot-plug PCI system support consists of an interlock switch and a set of two LEDs for each Hot-plug PCI slot. When power is on to a specified slot, one LED remains on. The other LED indicates that the slot requires attention. Slots that do not have these devices are NOT Hot-plug PCI slots. All Hot-plug operations must be controlled through a console provided by Novell. ATTENTION: 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 THE ADAPTER. The order of events in any Hot-plug operation are the following: 1. Load the appropriate drivers (as described in Section 4.2) to provide Hot-plug PCI support. 2. Go to the NetWare Configuration Manager Console (NCMCON). 3. Choose an add or remove operation for the specified slot. 4. When the adapter power is off, open the interlock and remove, replace, or add an adapter and any necessary cabling. 5. 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 specified slot. The position of the interlock switch (opened or closed) is not important if there is not an adapter in the specified slot. 6. If you are adding a new adapter or replacing an old adapter, the NCMCON console prompts you to turn on the newly added adapter. 7. 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 runs and loads the appropriate driver for you. If you are using any other type of adapter, you must go to the system console and manually load the appropriate driver. NOTE: NetWare might not recognize drives on SCSI controllers. To correct this problem, issue the console command 'SCAN FOR NEW DEVICES'. 1.2 Minimum requirements ________________________ The minimum system requirements are: o Only the IBM Netfinity 8500R 7RY, 8RY and IBM xSeries 370 servers are supported by this diskette release. NOTE: The IBMSBD.NLM driver is designed not to load on any server that does not have Hot-plug PCI slots, including non-IBM servers. To verify that your server Hot-plug subsystem is working properly, load the IBMSBD.NLM driver by typing the command 'LOAD IBMSBD -DETECT'. The console will display a message stating whether the driver detected an IBM Hot-plug PCI system in the server. o IBM Hot-Plug PCI System Bus Driver (version 1.10a) (IBMSBD.NLM) provided on this diskette. o An adapter and Novell NetWare adapter driver that supports the ODI version 3.31 specification or NWPA version 3.00b specification published by Novell. o One of the following: - Novell IntranetWare I (NetWare versions 4.11 or 4.2) with Support Pack (version 5a, or later). - Novell NetWare, version 5.x. Install the IBMSBD.NLM module from this diskette using the NWCONFIG utility or during the NetWare version 5 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 4 and 5 (see below) regarding operations and troubleshooting are still valid. NOTES: 1. Novell does not provide support modules for versions earlier than Novell IntranetWare I (NetWare versions 4.11 or 4.2). 2. To add a new adapter to an empty slot, the server must have the following modules loaded in the STARTUP.NCF to handle interrupts properly: o (For NetWare versions 4.11, 4.2, or 5.x) MPS14.PSM o (For NetWare versions 4.11 or 4.2) SMP.NLM If these modules are not loaded properly, clients might fail to connect to the server after a Hot-plug PCI operation. 1.3 Limitations _______________ o Bridge adapters or PCI devices containing PCI-to-PCI bridges are NOT supported. o Some LAN adapter drivers might not handle interrupts correctly if the Wake-on-LAN setting is active after a Hot-add operation. The driver might load, but clients cannot attach to the server through that adapter. o Multi-Function PCI devices are not supported if the multi-function capability is provided with or through a PCI-to-PCI bridge. o Video adapters are not supported in the Hot-plug PCI environment due to I/O space limitations and restrictions. o Devices are not supported if they are not PCI version 2.1 compliant or do not implement the PCI presence detection pins. o Device drivers that are not LAN ODI version 3.31 compliant or SCSI NWPA version 3.00b compliant are not supported. o Non-PCI devices do not support Hot-plug operations. o HWDETECT.NLM (a Novell-provided module) might not find the correct driver if more than one driver is capable of loading for the specified adapter. o HWDETECT.NLM might display an error failing to open the SYS:\SYSTEM\AUTOEXEC.NCF file. Ignore this message by pressing Enter and proceeding through the driver detection. o Because of errors encountered in testing, IBM does not provide HWDETECT.NLM. If you need the feature that auto-detects the correct driver for newly added adapters, download the latest HWDETECT.NLM from the Novell Web site at the following address: http://support.novell.com/search/ff_index.htm 1.4 Enhancements ________________ Version 1.10b of the Hot-plug PCI support was changed to allow the IBM ServeRAID-4 Ultra160 SCSI controllers to initialize properly. This release of software is compatible with the IBM Netfinity 8500R 7RY, 8RY servers and the IBM xSeries 370 server. 1.5 Level of recommendations and prerequisites for the update ______________________________________________________________ All IBM xSeries and IBM Netfinity Hot-plug PCI capable servers released PRIOR to 2Q2001 are supported by this version of software drivers. 1.6 Dependencies __________________ To perform Hot-plug operations, the IBM Hot-Plug System Bus Driver requires five drivers in the AUTOEXEC.NCF file, as well as several other support files. NOTES: 1. These operations are all performed by the IBM Hot-Plug PCI System Bus Driver Installation Program and the installation steps in Section 2.0. 2. Some drivers have their DOS date and timestamps change when shipping with different versions of Support Packs or NOS releases. Only drivers that have their NetWare version and/or timestamp changed are listed as 'updated'. If the NetWare timestamp does not change, the driver is identical regardless of the DOS date timestamp on it. o The five drivers required in the AUTOEXEC.NCF are the following. NOTE: These drivers are order dependent. ODINEB.NLM 12,824 5-15-98 4:32pm (version 1.09) IOCONFIG.NLM 2,810 6-02-98 9:13am (version 1.00) NCM.NLM 14,320 6-08-99 10:40am (version 1.10) IBMSBD.NLM 113,576 4-19-01 1:43pm (version 1.10a) (updated) NCMCON.NLM 25,605 6-04-99 2:37pm (version 1.16) o Additionally, the following 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 (version 1.01) NBI.NLM 31,531 9-17-98 11:25am (version 2.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 (version 3.81) (updated) MSM.NLM 95,676 7-13-00 10:58am (version 3.98a)(updated) - For all Token-Ring Drivers, the following support files must be replaced: TOKENTSM.NLM 12,689 3-05-99 3:28pm (version 3.77) MSM.NLM 95,676 7-13-00 10:58am (version 3.98a)(updated) - For all FDDI Drivers, the following support files must be replaced: FDDITSM.NLM 12,787 3-05-99 3:15pm (version 3.74) MSM.NLM 95,676 7-13-00 10:58am (version 3.98a)(updated) - For all SCSI Disk Controllers, the following support files must be replaced: SCSIHD.CDM 25,645 11-23-99 4:16pm (version 1.36a) SCSICD.CDM 25,814 11-23-99 4:16pm (version 1.34k) SCSI2TP.CDM 38,047 11-23-99 4:16pm (version 1.02q) NWASPI.CDM 15,734 5-14-98 2:41pm (version 2.00) NWPALOAD.NLM 3,219 11-23-99 4:16pm (version 3.00) NWPAMS.NLM 73,905 11-23-99 4:16pm (version 2.34) NWPAIO.NLM 34,491 11-23-99 4:16pm (version 2.34) NPAPATCH.NLM 1,989 6-21-99 6:41pm (version 1.02) NWPA.NLM 94,727 11-23-99 4:16pm (version 3.03) o The supported drivers shipped on this diskette are: - IBM PCI Token-Ring Adapter IBMTRPO.LAN 97,225 10-20-99 2:47am (version 2.47)(updated) IBMTRPO.LDI 47,680 2-04-01 11:37am (updated) IBMCOS.NLM 27,414 8-12-98 12:00pm (version 1.01) - IBM EtherJet 10/100 PCI Adapter CE100B.LAN 83,909 1-06-01 9:29pm (version 3.29)(updated) CE100B.LDI 41,219 2-14-01 4:13am (updated) IANS.LAN 113,961 1-10-01 4:24am (version 3.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 (version 2.72)(updated) CE1000.LDI 9,738 3-16-01 2:57pm (updated) IANS.LAN 113,961 1-10-01 4:24am (version 3.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 (version 4.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 (version 4.18) PCNTNW.LDI 19,579 4-08-99 1:12pm - Other files on the diskette are the following: 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. Multiple adapters would be allocated memory within a single 4 KB range, however, when an adapter was unloaded, the server would abend because the full 4 KB 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 so that if any adapter is still using memory within the 4 KB range, the range is not returned to inactive storage until all drivers using the memory space have unloaded. This patch is required for NetWare versions 5.00a through 5.00g. All other versions of NetWare, including later versions of NetWare version 5 do not exhibit this problem. The patch will not load if the version of NetWare does not exhibit the problem. 2.0 Change history ____________________ 2.1 Version 1.10b changes _________________________ o Added the following device drivers: CE100B.LAN CE100B.LDI CE1000.LAN CE1000.LDI IANS.LAN IANS.LDI ASCONF.NLM o 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 o Removed the following device drivers: IBMGE.LAN IBMGE.LDI CIBMFE.LAN CIBMFE.LDI IBMAFT.NLM IBMRNIC.NLM PCNTNW.RED IPSRAID.RED o Fixed a problem of IBMSBD.NLM assigning the same memory address to two IBM ServeRAID-4 Ultra160 SCSI Controllers. o Fixed a problem of IBMSBD.NLM assigning interrupt value FF to adapters. The adapter driver might not load or might not load correctly if interrupt value FF is assigned. o Design change to send a second power-on command to each slot to allow the IBM ServeRAID-4 Ultra160 SCSI Controllers to initialize correctly. o 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. o Updated PINSTALL.NLM to copy drivers to the c:\nwserver\drivers directory. 2.2 Version 1.06a changes _________________________ o Added the following device drivers: IBMGE.LAN IBM Netfinity Gigabit SX Adapter driver version 1.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 version 3.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 o 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 o Removed the following device drivers: IBMFE.LAN IBMFE.LDI IBMFE.RED PCNET40.TXT IPSADM.NLM IPSRADM.NLM o Added support for the Netfinity 8500R, Netfinity 6000R, and Netfinity 7600 servers. o Updated drivers for all supported IBM adapters. o The installation program was changed to fix a problem where the PINSTALL.NLM installation program placed the NCMCON.NLM module before the IBMSBD.NLM module. The problem resulted in all slots appearing to: o NOT support Hot-plug PCI. o Be powered on, even though they were powered off. 2.3 Version 1.05 changes _________________________ o Support added for NetWare version 5.1 o 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. o Added messages for wrong bus frequency on 66MHz capable slots. 2.4 Version 1.04 changes _________________________ Not released, development test version. 2.5 Version 1.03 changes _________________________ o 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 o Design change to support future IBM Netfinity server where the start address of resources is not on a 4 KB boundary (I/O) or a 1 MB boundary (Mem and PFMem). o Design change to add ConsolePrintf statements to show user what interrupt assignment was actually made. o Removed bridge adjustment because BIOS provides big enough resource windows already. o Design change to export the resource assignments to the console so that a user would know what was assigned to the added adapter. o Updated drivers for all supported IBM adapters. 2.6 Version 1.02 changes _________________________ Not released, development test version. 2.7 Version 1.01 changes _________________________ o Updated the following device drivers: ODINEB.NLM NEB.NLM MSM.NLM TOKENTSM.NLM IBMTRPO.LAN IBMTRPO.LDI RNIC.NLM IBMSBD.TXT o 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 version 2.43 or later. 2.7 Version 1.00 changes _________________________ Original release (May 1998) 3.0 Installation and setup instructions _________________________________________ 3.1 Installation steps for NetWare versions 4.11 or 4.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 the following and press Enter: LOAD INSTALL 4. From the installation menu, select 'Product Options'. 5. From the Product Options menu, select 'Product Not Listed'. 6. Insert the IBM Hot-Plug PCI driver diskette (this diskette) into the diskette drive. 7. To accept the default path of A:\, press Enter. NOTE: You also can copy the contents of this diskette to a subdirectory on the server (in either the DOS or NetWare partitions) and change the path in step 7 to match the path to the subdirectory. 8. After a brief moment, the Main Menu of the IBM Hot-Plug PCI System Bus Driver version 1.06 Installation Program displays. 9. Select 'Install NetWare version 4.11/version 4.2/version 5.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, 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 are successful. Before the installation program can continue, apply the LIBUPI.EXE package fixes. Then, begin these installation instructions again. You can download the LIBUPI.EXE file from the Novell Web site at the following address: http://support.novell.com/search/ff_index.htm 11. After the file copy is complete, press Esc to return to the Main Menu. 12. Select 'Exit' to return to the Installation Program. 13. After the installation, view the 'NCF files options' and verify that the following files were added to AUTOEXEC.NCF in the following order: ODINEB.NLM, IOCONFIG.NLM, NCM.NLM,IBMSBD.NLM, AND NCMCON.NLM. NOTE: If the files are not in the preceding order, edit AUTOEXEC.NCF to change the order. 14. Press Esc two times; then, select 'Yes' to exit the NetWare Installation Program. 15. Type: DOWN 16. To have the required modules load, type RESTART SERVER NOTE: If the installation is successful, the NetWare Configuration Manager Console (NCMCON) will display 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 version 5.x ______________________________________________ To determine if the IBM Hot-Plug PCI Support is installed on your Hot-plug PCI capable server, type the following command: MODULES IBMSBD.NLM If the module returned is version 1.10a, 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 earlier than version 1.10a, additional installation steps are required. You can complete the installation by installing the IBM Hot-Plug PCI System Bus Driver. To install the IBM Hot-Plug PCI System Bus Driver, do the following: 1. Start the NetWare server and go to the NetWare console. 2. Type the following and press Enter: NWCONFIG 3. From the installation menu, select 'Product Options'. 4. From the Product Options menu, select 'Product Not Listed'. 5. Insert the IBM Hot-Plug PCI driver diskette (this diskette) into the diskette drive. 6. To accept the default path of A:\, press Enter. NOTE: You also can copy the contents of this diskette to a subdirectory on the server (in either the DOS or NetWare partitions) and change the path in step 6 to match the path to the subdirectory. 7. After a brief moment, the Main Menu of the IBM Hot-Plug PCI System Bus Driver Installation Program displays. 8. Select 'Install NetWare version 4.11/version 4.2/version 5.x Support for IBM Hot Plug PCI System'. 9. Type the path where this diskette image is located, or accept the default of A:\, and press Enter. 10. After the file copy is complete, press Esc to return to the Main Menu. 11. Select 'Exit' to return to the Installation Program. 12. Press Esc two times; then, select 'Yes' to exit the NetWare Installation Program. 13. To have the required modules load, type: RESTART SERVER 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 might hang, requiring the system to be restarted. 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 receive a prompt asking if you want to unload the driver. You must unload the driver to remove the power to the slot. 6. If a message displays that the driver could not be unloaded, go to the system console and manually remove the driver. After unloading the driver, return to the NCMCON and repeat steps 3 through 5. 7. Verify that the status for the slot reads 'Powered off'. 8. Open the top cover of the server using the two thumb screws at the rear of the server. 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 specified slot is powered off. ATTENTION: 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, THE SYSTEM UNIT, OR BOTH. 10. Remove the interlock by swiveling the vertical lockdown counter- clockwise 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 receive a prompt asking if you want to unload the driver. You must unload the driver to remove the power to the slot. 6. If a message displays that the driver could not be unloaded, go to the system console and manually remove the driver. After unloading the driver, return to the NCMCON and repeat steps 3 through 5. NOTE: In most cases, unloading the driver unloads it for ALL instances of the adapter in the system. See Section 2.2 for any special commands that might 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 version 3.31 LAN Specification and the Novell NetWare NWPA version 3.00b Disk Specification. 7. Verify that the status for the slot reads 'Powered off'. 8. Open the top cover of the server using the two thumb screws at the rear of the server. 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 specified slot is powered off. ATTENTION: 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, THE SYSTEM UNIT, OR BOTH. 10. Remove the interlock by swiveling the vertical lockdown counter- clockwise 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. Return to the NCMCON screen. A message displays asking if power should be turned on to the specified slot. Select to turn on the power to a specified slot. 14. A prompt displays to verify that you have attached any necessary cables to the adapter card prior to power being applied. Press Enter at the cable reminder screen. 15. The adapter power turns on, the adapter is configured, and a message reports the success of adding the adapter. NOTES: 1. If an error occurs during power on and configuration of the adapter, the power to the slot is turned off, and an appropriate message displays on the NCMCON screen and the system console screen. If an adapter does not power on, go to section "3.0 Troubleshooting Hot-plug PCI operations." 2. If the adapter is a network adapter, BIND the appropriate protocols to the driver after the driver is loaded. 3. NetWare might not recognize drives on SCSI controllers. To correct this problem, issue the console command 'SCAN FOR NEW DEVICES'. 4. Drivers for newly added adapters do not automatically reload. See the instructions for the specifically supported adapters for information on how to reload drivers. 16. If a driver is not loaded for the specified slot, the adapter status displays READY in the NCMCON screen. When a driver is loaded for the specified slot, the adapter status displays ACTIVE in the NCMCON screen. 4.1.3 Adding a new adapter to an empty slot ___________________________________________ NOTES: 1. Adding a new adapter to a slot with an adapter already in the slot is the same as replacing an adapter. The steps for replacing an adapter are specified above in Section 4.1.2. 2. 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 handle interrupts properly. If these modules are not loaded properly, clients might fail to connect to the server after a Hot-plug PCI operation. 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 server using the two thumb screws at the rear of the server. 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 specified slot is powered off. ATTENTION: 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, THE SYSTEM UNIT, OR BOTH. 6. Remove the interlock by swiveling the vertical lockdown counter- clockwise and lift the interlock switch up. 7. Place the new adapter in the slot and close the interlock switch. Swivel the vertical lockdown clockwise to lock the interlock in place. 8. Return to the NCMCON screen. A message displays asking if power should be turned on to the specified slot. Select to turn on the power to a specified slot. 9. A prompt displays to verify that you have attached any necessary cables to the adapter card prior to power being applied. Press Enter at the cable reminder screen. 10. The adapter power turns on, the adapter is configured, and a message reports the success of adding the adapter. NOTES: 1. If an error occurs during power on and configuration of the adapter, the power to the slot is turned off, and an appropriate message displays on the NCMCON screen and the system console screen. If an adapter does not power on, go to section "3.0 Troubleshooting Hot-plug PCI operations." 2. If the adapter is a network adapter, BIND the appropriate protocols to the driver after the driver is loaded. 3. NetWare might not recognize drives on SCSI controllers. To correct this problem, issue the console command 'SCAN FOR NEW DEVICES'. 4. Drivers for newly added adapters do not automatically reload. See the instructions for the specifically supported adapters for information on how to reload drivers. 11. If a driver is not loaded for the specified slot, the adapter status displays READY in the NCMCON screen. When a driver is loaded for the specified slot, the adapter status displays ACTIVE in the NCMCON screen. 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 might work. See Section 5.2.1 for steps on determining whether an adapter driver supports Hot-plug PCI operations. NOTE: For questions about non-IBM adapters supporting Hot-plug PCI, contact the appropriate adapter vendor. You can use information in Section 5.2.1 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. Use the PCNTNW.LAN driver that is provided with this diskette to provide Hot-plug PCI support. If the PCNTNW.LAN driver is loaded already, and a second IBM Netfinity 10/100 Fault Tolerant Adapter is installed, you must use the following command to find the new adapter: LOAD PCNTNW SCAN You can download the latest version of this driver from the IBM Support Web site: http://www.ibm.com/pc/us/searchfiles.html 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. Use the CE100B.LAN driver that is provided with this diskette to provide Hot-plug PCI support. This driver is compatible with all versions of these adapters. When the CE100B.LAN driver is reloaded, it auto-detects newly added adapters. If HWDETECT does not find the correct driver after you complete the hot-add operation, use the following command to load the driver for this adapter: LOAD CE100B No additional information is provided with this diskette for this adapter. You can download the latest version of this driver at the following address: http://www.networking.ibm.com/servers 4.2.3 IBM Netfinity Gigabit Ethernet Adapter SX _______________________________________________ This adapter is fully supported in Hot-plug PCI operations. Use the CE1000.LAN driver provided with this diskette to provide Hot-plug PCI support. When the CE1000.LAN driver is reloaded, it auto-detects newly added adapters. After you complete the hot-add operation, use the following command to load the driver for this adapter: LOAD CE1000 No additional information is provided with this diskette for this adapter. You can download the latest version of this driver at the following address: http://www.networking.ibm.com/servers 4.2.4 IBM PCI Token-Ring Adapter ________________________________ This adapter is fully supported in Hot-plug PCI operations. Use the driver IBMTRPO.LAN provided with this diskette to provide Hot-plug PCI support. When the IBMTRPO.LAN driver is reloaded, it will auto-detect newly added adapters. After you complete the hot-add operation, use the following command to load the driver for this adapter: LOAD IBMTRPO NOTES: 1. If the new adapter is the first adapter in the network, you must set the data rate for the adapter to the speed that your Token-Ring network operates. The following command allows for 16 Mbps operations: LOAD IBMTRPO datarate=m16 For 4 Mbps operations, replace the m16 with m4 in the previous command. 2. The redundant NIC capability provided by the IBMTRPO.LAN and IBMRNIC 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 must re-establish the failover pair after a Hot-plug PCI operation. For more information about the parameters you must use to re-establish the failover pair, see the document at the following Web site address: http://www.networking.ibm.com/trl/trlrnic.html No additional information is provided with this diskette for this adapter. You can download the latest version of this driver at the following address: http://www.networking.ibm.com/servers 4.2.5 IBM ServeRAID II, IBM ServeRAID-3 Ultra2 SCSI, and IBM ServeRAID-4 Ultra160 SCSI Controllers ________________________________________________________ This controller is fully supported in Hot-plug PCI operations. Use the IPSRAID.HAM driver provided with this diskette to provide Hot-plug PCI support. NOTE: The original IBM ServeRAID controller is not supported for Hot-plug operations. When the IPSRAID.HAM driver is reloaded, it auto-detects newly added adapters. After you complete the hot-add operation, use the following command to load the driver for this controller: LOAD IPSRAID NOTE: Loading the IPSRAID controller might 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 the initial system scan. For example, 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 a ServeRAID II controller in slot 2 and a ServeRAID-3H controller in slot 5 on a Netfinity 5500. The ServeRAID controllers are labeled as follows: A1 is the integrated RAID controller. A2 is the ServeRAID-3H controller in slot 5. A3 is the ServeRAID II controller in slot 2. You can download the latest version of this driver at the following address: http://www.ibm.com/pc/us/searchfiles.html 4.3 Warnings about incorrect usage of Hot-plug PCI operations _____________________________________________________________ Below are several warnings about Hot-plug PCI operations: 1. Do not remove an adapter from a non Hot-plug PCI slot. 2. Use grounding equipment, including wrist straps, when working inside any system unit to protect against electrostatic discharge (ESD) that could damage system components and adapter cards. 3. Verify 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 and you must restart the system. 5. Do NOT remove the plastic cover over the system components. Removal of the plastic cover exposes system components that might 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, you must restart the system to clear the NMI. 5.0 Troubleshooting Hot-plug PCI operations ___________________________________________ 5.1 Basic troubleshooting _________________________ There are several troubleshooting techniques that you can use to determine why a Hot-plug PCI operation failed. Two LEDs are provided for each Hot-plug PCI capable slot. One LED blinks to indicate that attention is required. The second LED indicates the power state. The NCMCON screen, IBMSBD.NLM driver, and the other adapter drivers generate messages. 5.1.1 Attention Indicator LED _____________________________ The Attention Indicator LED is controlled by NetWare. Device drivers use the Attention Indicator LED to indicate that an adapter in a specified slot requires attention. Not all device drivers support Attention Indicator messages. The Attention Indicator stops blinking only if one of the following occurs: 1. An adapter is successfully replaced in the Hot-plug PCI slot. 2. The device driver clears the condition that generated the Attention Indicator message. 5.1.2 IBMSBD.NLM messages _________________________ The IBMSBD.NLM IBM System Bus Driver generates messages to indicate changes of state in the Hot-plug PCI system. If this driver is not loaded, system messages are not generated. IBMSBD.NLM messages use the "IBMSBD:" or "IBMSBD Error:" prefixes. The IBMSBD.NLM messages are the following: 5.1.2.1 "IBMSBD: New Adapter added. Please use the Novell Configuration Manager console (NCMCON) to configure this new adapter." ___________________________________________________________ This IBMSBD.NLM message indicates that a new adapter was added to a previously empty slot. The empty slot might be a result of a previous Hot-plug Replace or Hot-plug Add PCI operation. This message instructs you to use the console (NCMCON) to configure the newly added adapter. 5.1.2.2 "IBMSBD Error: Allocate NEB.AESTag() failed." _____________________________________________________ This IBMSBD.NLM error message indicates that the IBMSBD driver was unable to allocate an asynchronous event system (AES) tag. Because events occur asynchronously in the Hot-plug PCI system, IBMSBD must have an AES handle to function. To correct this problem, free up AES resources by unloading other NLMs that have AES tags registered. 5.1.2.3 "IBMSBD Error: Not enough memory to generate event for queue." ______________________________________________________________ This IBMSBD.NLM error message indicates that memory could not be allocated to place a Hot-plug PCI event into the internal resource queue. This normally occurs when the system runs out of available memory. To correct this problem, unload other NLMs or add additional memory to the system. 5.1.2.4 "IBMSBD Error: Add Adapter command failed because of empty slot. Slot is x" ____________________________________________________________ This IBMSBD.NLM error message occurs when NCMCON is directed to add an adapter to a slot that does not currently have an adapter card in it. This error also might occur if a PCI adapter does not use presence pins as specified by the PCI version 2.1 specification. The IBMSBD module uses the presence pins to determine when an adapter has been inserted or removed from the system. 5.1.2.5 "IBMSBD: The IBM Hot-plug PCI controller is not present." _______________________________________________________ This IBMSBD.NLM message occurs when an attempt is made to run the IBMSBD module on a system that does not have a Hot-plug PCI controller. This message also might occur if the Hot-plug PCI controller is malfunctioning or failed. Use the -COMMAND -DEBUG switches on the IBMSBD driver to determine if the Hot-plug controller is working. See Section 5.2.2 for more information about debug switches for the IBMSBD device driver. 5.1.2.6 Other IBMSBD.NLM messages _________________________________ The Novell Configuration Manager Console (NCMCON) screen provides all other messages. For information about problems in NCMCON, such as all slots show 'No' in the Hot-plug field or a message displays asking whether to continue waiting another 10 seconds, see Section 5.2.4. If IBMSBD.NLM fails to load and displays a message stating that a symbol was not found NBIDetect(), an old level of NBI.NLM is being used. Replace NBI.NLM with the version 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 version 3.31 or the NWPA version 3.00b specifications. If you have such a device driver, determine whether your adapter vendor has a certified device driver available. If a certified device driver does not exist, you must either use a different adapter or lose some of the Hot-plug functionality. Device drivers that do not support the Novell specifications might exhibit the following problems: o Failure to detect a new adapter until it is unloaded and reloaded. o Failure to support single-instance unload. Single-instance unload is the ability to unload the driver for a single adapter even though the driver might support many adapters. o Failure to register PCI resources such as interrupts, I/O ports, memory or prefetchable memory ranges. Some drivers that support the Novell specification might exhibit above problems 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 same level as the drivers on this diskette. Because these are Novell support modules, check the Novell Web site for versions later than those on this diskette: http://support.novell.com 5.2 Advanced troubleshooting ____________________________ This section contains the following information: o 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. o Debug switches available with the IBMSBD.NLM driver. o How interrupts are assigned. o NCMCON issues, such as no Hot-plug slots displayed, or a query about waiting another ten seconds. 5.2.1 How to determine if a problem is with the adapter driver or the Hot-plug driver. _________________________________________________________________ NOTES: 1. This section shows how to handle devices that are not on the IBM-approved list of Hot-plug PCI devices. Some devices might work correctly, but have not been tested and approved by IBM. 2. There are no changes to the physical adapter required to support Hot-plug PCI operations. Many other adapter vendors will provide drivers that meet the required Novell specifications for Hot-plug PCI in the future. However, there are times where you might have a driver and will not know whether the driver is Hot-plug PCI compatible. The following is a list of methods to determine if a specified 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 version 4.11, 4.2, and 5.x, any device with a PCI-to-PCI bridge will not be added successfully. 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, and so forth) and reloading them will allow the new slots to be detected 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 the new device drivers, support modules, and installing the latest support packs do not fix the problem, continue to Section 5.2.2 to debug the IBMSBD.NLM module. 5.2.2 Using the IBMSBD driver switches and log file ___________________________________________________ Use the following command line switches to create an IBMSBD.LOG file in the SYS:\SYSTEM directory. When calling the IBM HelpCenter, you can submit this file as part of your call. IBM service representatives use the file to verify that the IBMSBD.NLM module is working properly. NOTE: The following commands are NOT case sensitive. Also, they do NOT require the leading hyphen. If you specify multiple commands, separate the command with spaces. For example: LOAD IBMSBD -DETECT DEBUG -COMMAND 5.2.2.1 /?,-?, ? ________________ Use these flags to display information about the switches. 5.2.2.2 -DETECT _______________ This switch requests the IBMSBD.NLM driver to detect whether a Hot-plug PCI system and controller are present. The driver displays the results as a message on the system console; then, the switch terminates. You cannot use this switch with any other switch. 5.2.2.3 -DEBUG ______________ Use this switch to log debug actions and system information in the IBMSBD.LOG file. System information includes the following: the 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. 5.2.2.4 -COMMAND ________________ Use this switch to display the following: o The return codes from the PCI Hot-plug controller o The return codes to NCMCON o All PCI Hot-plug operations and return codes. 5.2.2.5 -RESOURCE _________________ Use this switch to generate resource tables in the IBMSBD.LOG file. To successfully generate tables, you must use this switch in conjunction with -IO, -MEM, or -PFMEM. 5.2.2.6 -IO ___________ Use this switch to generate resource tables that display all I/O resources assigned by BIOS and the IBMSBD.NLM module. This switch also displays all I/O assignments during the Hot-plug PCI operation. You must use this switch in conjunction with the -RESOURCE switch. 5.2.2.7 -MEM ____________ Use this switch to generate resource tables that display all PCI memory resources assigned by BIOS and the IBMSBD.NLM module. This switch also displays all memory assignments during the Hot-plug PCI operation. You must use this switch in conjunction with the -RESOURCE switch. 5.2.2.8 -PFMEM ______________ Use this switch to generate resource tables that display all PCI- prefetchable memory resources assigned by BIOS and the IBMSBD.NLM module. This switch also displays all prefetchable memory assignments during the Hot-plug PCI operation. You must use this switch in conjunction with the -RESOURCE switch. 5.2.2.9 -IRQ ____________ Use this switch to display all system devices by PCI deviceID and vendorID. The information provided displays the slot that the adapter occupies and the IRQ number (1-15) assigned to offset 0x3c of the PCI Configuration Header for the specified 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. 5.2.2.10 -DEVICE ________________ Use this switch to generate information for the IBMSBD.LOG file about PCI devices found in the system. The information logged include the following: the bus, slot number, device/function ID, classCode, VendorID, and device type. 5.2.2.11 -ALL _____________ Use this switch to turn on all debug tracking in the driver. This switch reports all driver internal output to the SYS:\SYSTEM\IBMSBD.LOG file. The log file is closed when the IBMSBD.NLM driver is unloaded. NOTE: This log file can become large quickly (several MB). Do not use this switch unless directed by HelpCenter service personnel. If a problem arises where you must create the IBMSBD.LOG file, you can submit the file as part of the call to the HelpCenter for further diagnostic help. 5.2.3 Interrupt handling ________________________ Interrupts are handled in the following manner: o Only interrupts 9, 10, and 11 are assigned to Hot-plug PCI devices. These options are not settable. During BIOS setup, if these three interrupts are reserved for ISA Legacy devices, all Hot-plug PCI operations will fail. o IRQ 15 is never assigned to Hot-plug PCI devices unless an adapter of the same type is installed in the server already, and that adapter is assigned to IRQ 15. o Interrupts are preserved from the MPS table located in the extended BIOS data area (EBDA) of the system. o For slots that do not have an adapter in them at system startup (boot), interrupts are assigned according to the following formula: 1. If another device that matches the vendorID and deviceID in the PCI Configuration header is found, then the newly-added adapter receives the same interrupt as the other device. 2. An unused interrupt between 9, 10, and 11 is assigned. 3. The least-used interrupt between interrupts 9, 10, and 11 is assigned. NOTE: There might be instances where a LAN and SCSI controller might be assigned the same interrupt. If this occurs, the LAN adapter might fail to handle interrupts correctly when the SCSI controller accesses the DOS partition and lose connections. If this occurs, shut down the server, restart it, go into System Setup, and manually assign the interrupts so the devices do not share interrupts. 5.2.4 NCMCON issues ___________________ o 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. o If you receive a message stating that the Slot Status is not available and then receive a prompt to wait 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 load NCMCON. It is not necessary for NCM or NCMCON to be loaded for the IBMSBD driver to load properly. o 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. o If a fully supported ODI version 3.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. o All SCSI controller drivers must be unloaded from the system console. Use 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 are assigned first, followed by adapters in PCI Bus 0, PCI Bus 1, and so forth. o When using failover pairs in conjunction with Hot-plug PCI, do not setup failover pairs using the Netfinity Ethernet Adapter 2 and the Netfinity Fault Tolerant Ethernet Adapter as two independent pairs. Failover pairs must consist of identical adapter models. 6.0 IBM Support Web site __________________________ http://www.ibm.com/pc/support 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 or both:: Active PCI Netfinity EtherJet ServeRAID HelpCenter xSeries IBM Other company, product, and service names may be trademarks or service marks of others. 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.