This README file contains the latest information about installing the IBM eServer BladeCenter (TM) Fibre Channel Expansion Card Device Driver version 6.80f1 on Novell Netware 6.5 Refer to the IBM eServer BladeCenter (TM) Fibre Channel Expansion Card Support CD and Installation and User's guide. Refer to the IBM Support Website listed in "Web Sites and Support" section in this ReadMe document for the latest information and updated README file. Refer to the readme.txt file contained within the 6.80f1 driver package for additional information. Products supported: IBM eServer BladeCenter Fibre Channel Expansion Card (IBM Option P/N 13N2203) IBM eServer BladeCenter Fibre Channel Expansion Card (IBM Option P/N 48P7061) IBM eServer BladeCenter SFF Fibre Channel Expansion Card (IBM Option P/N 26K4841) Last Update: 10/3/2004 =================================================== Contents -------- 1. OS Support 2. Supported Features 3. Release History 4. Creating the Driver Diskette 5. Host Adapter configuration 5.1 Configure NOVRAM for the IBM eServer BladeCenter (TM) Fibre Channel Expansion Card 6. Installing the Driver 6.1. Initial OS installation with the Expansion Card as Boot 6.2. Adding the Expansion Card to the Existing OS 6.2.1. Adding the Driver for the First Time 6.3. Updating the Existing Expansion Card Driver 7. NetWare Failover 8. Install FAStT_MSJ 9. Removing the Driver 10. Driver Optional Parameters 10.1. System Parameters 11. Known Issues and Limitations 12. Additional Notes 12.1. 256 LUN Support 12.2. Server Memory Recommendations 13. Diskette Content 14. WEB Sites and Support Phone Number 15. Trademarks and Notices 16. Disclaimer ====================================================================== 1. OS Support ------------- NetWare 6.5 Support Pack 2 ====================================================================== 2. Supported Features --------------------- * NetWare Multi-Processor Compliance * NetWare PCI Hot Plug Compliance * Driver 256 LUN Support * Driver Adapter/Lun Failover * Driver DMI and QMS Support ====================================================================== 3. Release History ------------------ Version 6.80f1 10/3/04 * Changed ham module id back to 0x597. * Changed byte order of port id in HAM_Return_Port_Info(). * Corrected hardware type in get adapter info ioctl to use lookup table. * Corrected risc parity enable command (moved to after start firmware). * Corrected failure to failover on driver single instance unload. * Corrected port logins to be conditional for all device types. * Corrected loopback error counts on successful loopback. * Corrected reading of bios version from flash. * Corrected loop id exhaustion on port disappear with link timeout. * Removed disabling of failover mode on detection of QLA200 board. * Moved optical driver initialization before firmware initialization. Version 6.51d 03/11/04 * Initial Release for IBM eServer BladeCenter (TM) Fibre Channel Expansion Card ====================================================================== 4. Creating the Driver Diskette ------------------------------- 1. Download the IBM eServer BladeCenter (TM) Fibre Channel Expansion Card Device Driver: - Download the device driver from the IBM Support website listed in Support section of this Readme document. 2. If prompted with "What would you like to do with this file?” choose "Save this program to disk". 3. Specify a temporary location on your hard drive and download the device driver. 4. Unzip the file to a floppy disk that will be used to install the device driver ======================================================================= 5. Host Adapter configuration ------------------------------ 5.1 Update the Fibre Channel Expansion Card Host Bus Adapter BIOS -------------------------------------------------- IMPORTANT NOTE: The adapter BIOS must be at least 1.43 for the 6.80F1 driver. The adapter BIOS can be updated by booting the server to the BIOS update diskette, available from the IBM Support website. Refer to the install instructions provided with the BIOS update. 5.2 Configure NOVRAM for the IBM eServer BladeCenter (TM) Fibre Channel Expansion Card ---------------------------------------------------------------- All the settings should maintain the IBM defaults except the following. - Advanced Adapter Settings LUNs per target - 32 1. As the host boots, press CTRL-Q when prompted Press for Fast!Util. 2. After the Fast!Util program loads, the display will depend on whether there are multiple IBM eServer BladeCenter (TM) Fibre Channel Expansion Card installed: If there are multiple Expansion cards, a list of addresses occupied by those Expansion cards ports will appear. Using the arrow keys, select the desired expansion card port and press ENTER. The Fast!Util Options menu will then appear. For further information refer to the IBM eServer BladeCenter (TM) Fibre Channel Expansion Card publication. ====================================================================== 6. Installing the Driver ------------------------ This section is divided into the following three sections. · Initial operating system installation with the Expansion Card as Boot · Adding the IBM eServer BladeCenter (TM) Fibre Channel Expansion Card to the existing operating system · Updating the existing IBM eServer BladeCenter (TM) Fibre Channel Expansion Card Device Driver ====================================================================== 6.1. Initial OS installation with the Expansion Card as Boot -------------------------------------------------------------------- Contact IBM Support for supported configurations and instructions for configuring the IBM eServer BladeCenter (TM) Fibre Channel Expansion Card as the boot device. ====================================================================== 6.2. Adding the Expansion Card to the Existing OS --------------------------------------------------------- Perform the following steps to add the driver to the existing NetWare system. 6.2.1. Adding the Driver for the First Time ------------------------------------------- 1. From the NetWare server prompt, load the appropriate NetWare program: LOAD HDETECT 2. Select and press . 3. Select and press . 4. Select the storage adapters and press . 5. Select and press . 6. Press to install an unlisted driver. 7. Insert the Fibre Channel Expansion Card driver diskette and press to specify the path to the QLogic HAM driver: A:\NETWARE 8. Press to select the QLogic HAM driver. 9. Select and press to load the new driver. 10. Press to exit the installation. 11. At the server console type: Load edit c:\nwserver\startup.ncf The load statement for the Expansion Card should read as follows if the LSIMPE.CDM is used for multi-path failover: LOAD QL2300.HAM SLOT=n /LUNS /ALLPATHS /PORTNAMES /XRETRY=400 For more information on the lsimpe driver on Netware refer to the document at http://support.novell.com/cgi-bin/search/searchtid.cgi?/2966837.htm ====================================================================== 6.3. Updating the Existing Expansion Card Driver -------------------------------------------------------- Perform the following steps if the driver is already installed and you want to install an updated version of the driver. 1. From the NetWare server prompt, load the appropriate NetWare program: LOAD HDETECT 2. Select and press . 3. Select and press . 4. Select the storage adapters and press . 5. Select and press . 6. Press to install an unlisted driver. 7. Insert the IBM FAStT FC2-133 Host Bus Adapter driver diskette and press to specify the path to the QLogic HAM driver: A:\NETWARE 8. Press to select the QLogic HAM driver. 9. Select and press to load the new driver. 10. Press to exit the installation. ====================================================================== 7. NetWare Failover ------------------- IMPORTANT: NetWare 6.5 with Support Pack 2 comes with the latest drivers and does not need to be updated. NOTE: Do not use the drivers that are available with NetWare 6.5 Support Pack 1.1. Download the following 3 files and place in c:\nwserver on the NetWare server. Download the newest LSIMPE.CDM from http://support.novell.com : TID# 2966837 and follow the installation instructions in the Novell TID. Download the updated NWPA.NLM from http://support.novell.com : TID # 2968190 and follow the installation instructions in the Novell TID. Download the newer MM.NLM from http://support.novell.com : TID# 2968794 and follow the installation instructions in the Novell TID. After the Device Driver is installed, edit the STARTUP.NCF for the following: Add 'SET MULTI-PATH SUPPORT = ON' Add 'Load LSIMPE.CDM' before the SCSIHD.CDM driver Add the 'AEN' command line option to SCSIHD.CDM, expl: 'Load SCSIHD.CDM AEN' Your STARTUP.NCF file should look somewhat like the following: SET Multi-path Support = ON LOAD MPS14.PSM LOAD IDECD.CDM LOAD IDEHD.CDM LOAD LSIMPE.CDM LOAD SCSIHD.CDM AEN LOAD IDEATA.HAM SLOT=10007 LOAD QL2300.HAM SLOT=4 /LUNS /ALLPATHS /PORTNAMES /XRETRY=400 LOAD QL2300.HAM SLOT=5 /LUNS /ALLPATHS /PORTNAMES /XRETRY=400 Disable all other multi-path support. For example, when using QLogic adapters, load the driver with '/luns /allpaths /portnames'. The 'allpaths' option disables the QLogic failover support. Startup the server. If your configuration is correct you will not need to set the failover priorities for your LUNs, the LSIMPE.CDM driver will configure these. Use the multi-path documentation to verify the failover devices. This documentation is available from http://support.novell.com/cgi- bin/search/searchtid.cgi?/10070244.htm ====================================================================== 8. Install FAStT_MSJ -------------------- If FAStT_MSJ for WIN32/NetWare is not currently installed you should install it now. FAStT_MSJ and the qlremote agent are needed for Fibre path diagnostics. See the FAStT_MSJ publications for instructions on the installation procedure for FAStT_MSJ and the qlremote agent for WIN32 / NetWare. FastT_MSJ is available from the IBM Support website. ====================================================================== 9. Removing the Driver ---------------------- 1. From the NetWare server prompt, load the appropriate NetWare program: LOAD HDETECT 2. Select and press . 3. Select and press . 4. Select the storage adapters and press . 5. Select and press . 6. Select the correct driver and press . ====================================================================== 10. Driver Optional Parameters ----------------------------- The HAM driver has selectable optional parameters: 1. System parameters (specified at driver load time) These are described in the following subsection. ====================================================================== 10.1. System Parameters ---------------------- Driver optional system parameters are specified on the driver load line. There are two types of driver opional parameters: 1. Global - the parameter acts on all driver instances. 2. Instance - the parameter acts only on the individual driver instance in which it is specified. SLOT=n (Instance) Specifies to NetWare the PCI slot number n of the adapter for which to load this driver instance. LOAD QL2300.HAM SLOT=3 /LUNS (Instance) Specifies to NetWare to scan for all luns during the load of this driver instance (otherwise NetWare will only scan for lun zero devices); this is required for all RAID susbsystems. LOAD QL2300.HAM SLOT=3 /LUNS /ALLPATHS (Global) Disables failover and reports to NetWare all devices on all adapter paths; this is required when failover is being handled by an upper layer driver or CDM such as the LSIMPE driver. LOAD QL2300.HAM SLOT=3 /LUNS /ALLPATHS /PORTNAMES (Global) Internally tracks devices by portname rather than nodename; this is required when storage luns do not have a 1:1 correspondence across portnames. LOAD QL2300.HAM SLOT=3 /LUNS /PORTNAMES /GNNFT (Instance) Uses a single GNNFT rather than a GAN sequence to query the fabric name server. LOAD QL2300.HAM SLOT=3 /LUNS /GNNFT /XRETRY This will extend the retry count for any I/O command that experiences failure with one of the following SK/ASC/ASCQ codes: 2/04/01 6/8B/02 /CONSOLE (Global) Sends system alerts to the server console when failover and failback events occur. LOAD QL2300.HAM SLOT=3 /LUNS /CONSOLE ====================================================================== 11. Known Issues and Limitations -------------------------------- - The Storage Manager Agent should be unloaded when not used for system configuration. When the Storage Manager Agent is loaded and a fibre path suffers a failure it is possible for the NetWare server to abend. The Storage Manager Agent can be unloaded by following these steps. 1. At the server console type: java -show look for the line "devmgr.versioned.agent.AgentServer.......................QQQ" where QQQ is the process id. 2. At the server console type: java -killQQQ where QQQ is the process id from the java -show command.. - NetWare 6.5 may install the following in your 'startup.ncf' file" LOAD QLCSFTE.CDM You must either remove or comment this line out of your startup.ncf file for use with the IBM FAStT Storage Subsystems. ====================================================================== 12. Additional Notes -------------------- 12.1. 256 LUN Support --------------------- To find all LUNS, load the driver with the /LUNS qualifier. For example: LOAD QL2300.HAM SLOT=3 /LUNS Or, if the driver is already loaded, use the command SCAN ALL LUNS at the server console prompt to find all LUNS (new and existing LUNS). ** To set the LUNs Per Target parameter: 1. Reboot the hardware, and do CTRL - Q when QL2300 banner appears. 2. Select the desired adapter. 3. Select Configuration Settings. 4. Select Advanced Adapter Settings. 5. Select LUNs Per Target and change the LUNs Range. 6. Press ESC twice and select Save. 7. Press ESC again and select Reboot. ====================================================================== 12.2 Server Memory Recommendations ---------------------------------- In general, at least 512MB of memory is recommended. For large numbers of large volumes, in excess of 1024MB is required. ====================================================================== 12.3 Debug Driver Information ------------------------------ This package also includes the debug version of the QL2300 adapter driver. This driver is identified as ql2300d.HAM. The debug driver provides additional driver information that is dumped to an additional console screen. The format for the debug information is as follows. HAM DRIVER DEBUG SCREEN ======================= Every 1 second: A0=0/1234 <0,0> {0,0} 5678 A1=0/1234 <0,0> {0,0} 5678 A0 adapter instance index 0 A1 adapter instance index 1 0/1234 0 unresolved interrupts / 1234 total number of interrupts <0,0> 0 io command timeouts ,0 mailbox command timeouts {0,0} 0 io commands in pending queue structures , 0 io commands currently executing on fibre 5678 5678 seconds since last interrupt occurred Notes: a. Unresolved interrupt is when the isp indicates that it has an interrupt pending, but when the driver reads the completion registers it finds no work to do. b. The total number of io commands outstanding from Netware is the sum x+y of the numbers inside braces {x,y}. Every 10 seconds: FindTimedOutCommands(An): Searching... An adapter instance index n This indicates that the driver is searching for any IO commands that have not completed and have expired their timeout counter; when none are found, nothing is printed; otherwise the timed out IO commands are identified and then requeued for retry. ====================================================================== 13. Diskette Content -------------------- \QL2300.DDI Driver installation description file \QL2300.HAM NetWare HAM driver for supporting the IBM eServer BladeCenter (TM) Fibre Channel Expansion Card \QL2300d.DDI Driver installation description file \QL2300d.HAM NetWare Debug HAM driver for supporting \RELEASE.TXT Release notes (change history) \README.TXT Qlogic readme for 6.80f1 driver ====================================================================== 14. WEB Sites and Support Phone Number -------------------------------------- IBM Support Web Site: http://www.ibm.com/pc/support IBM eServer xSeries BladeCenter Marketing Web Site: http://www.ibm.com/servers/eserver/bladecenter If you have any questions about this update, or problem applying the update go to the following Help Center World Telephone Numbers URL: http://www.ibm.com/planetwide ====================================================================== 15. Trademarks and Notices -------------------------- The following terms are trademarks of the IBM Corporation in the United States or other countries or both: IBM eServer BladeCenter Microsoft, Windows, and Windows 2000 are trademarks of Microsoft Corporation in the United States, other countries, or both. Other company, product, and service names may be trademarks or service marks of others. ====================================================================== 16. Disclaimer -------------- THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE AND MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM GRANTS NO LICENSES TO ANY PATENTS OR COPYRIGHTS. Note to Government Users 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.