IBM SSA RAID Adapter for PC Servers ----------------------------------- Novell Netware Device Drivers and Utilities - README.TXT -------------------------------------------------------- This file contains information you need to install the IBM SSA RAID Adapter for use with Netware. Please also refer to the sections "Possible Problems" and "PC Server BIOS levels" for other important information about this product. This README file is divided into the following categories: - Before You Install the IBM SSA RAID Adapter - Software Requirements - Hardware Requirements - Getting Help - Installing IBM SSA RAID Adapter - Using SSA for Operating System Boot - Possible Problems - Configurator Error codes - Trademarks Before You Install the IBM SSA RAID Adapter ------------------------------------------- PC Server BIOS Level -------------------- NOTE: It is recommended that you ensure that the Server you are using has the latest BIOS. These can be obtained from the follow sites: (919)-517-0001 : IBM PC Company BBS Research Triangle Park, USA. ftp.pc.ibm.com : IBM PC Company anonymous ftp site. www.compaq.com : Compaq company web site. www.hp.com : Hewlett Packard company web site. At the time of writing, the tested levels are: PC Server 704 PCI/EISA, Flash BIOS 10 (06-26-97) PC Server 720 PCI/MCA, Flash BIOS v1.09 (06-16-97) PC Server 520 PCI/EISA, Flash BIOS 16T3C (07-15-96) PC Server 320 PCI/EISA, Flash BIOS 16T3B (07-15-96) PC Server 330/325 PCI/EISA, Ship level at time of writing COMPAQ ProLiant 1500, COMPAQ System BIOS E12 (12/30/1996) COMPAQ ProLiant 2500, COMPAQ System BIOS E24 (12/30/1996) COMPAQ ProLiant 5000, COMPAQ System BIOS E16 (12/30/1996) COMPAQ ProLiant 6000, COMPAQ System BIOS E20 (05/16/1997) HP NetServer LH Pro, Phoenix BIOS v 4.05.14PF Plug and Play (12/11/96) HP NetServer LX Pro, AMIBIOS - American Megatrends V 1.00.4.CD0L Software Requirements --------------------- - Novell Netware version 4.1 with OS Patches. Refer to the Novell web site at: http://www.novell.com) for details. Hardware Requirements --------------------- - A supported PC Server platform which has a PCI bus (specification level 2.1) and runs Novell Netware version 4.1. - 1 MB of fixed disk space above that required by Netware. - .5 MB of memory above that required by Netware. - IBM SSA RAID Adapter, installed into a PCI slot of the PC Server. Getting Help ------------ Documentation. Service and Technical Support. Available Documentation ----------------------- - Installation and Users Guide S32H-3816-xx - Maintenance Information Manual S32H-3817-xx - Technical Reference Manual SA33-3268-xx Service and Technical Support ----------------------------- We are ready to help you with your IBM SSA RAID Adapter questions. You can contact us through one of the following: For Technical Support: - Please contact your supplier in the first instance - BBS, for latest files etc. o US: (919) 517-0001 (300 - 28.8K, 8-N-1) o UK: (0)1705-492831 (2.4K - 14.4K, 8-N-1) o Germany: (0)6131-845070 (2.4K - 14.4K, 8-N-1) For Product Information: - WWW, http://www.storage.ibm.com/storage Installing IBM SSA RAID Adapter Device Driver and Utilities for Netware ----------------------------------------------------------------------- The following files may be found on this diskette: ISSAPCI.DSK - Device driver for the IBM adapter ISSADSK.DSK - Device driver for the IBM adapter ISSACFG.NLM - SSA Configurator CFGMENU.NLS - National Language Support (UK English) CFGHELP.NLS - National Language Support (UK English) ISSAELOG.NLM - SSA Event Logger EVNCTLRF.TXT - Control File EVNLOG.NLS - National Language Support (UK English) ISSAINST.NLM - Install NLM (copies files to SYS:SYSTEM) ISSAPCI.DDI - Device Driver Install Script ISSADSK.DDI - Device Driver Install Script README.TXT - This file To install the device drivers on a system with Netware already installed and running, Put the driver install diskette into your diskette drive (A:) From the System Console command prompt, type: load install [ENTER]. now select "Driver options". select "Configure disk and storage device drivers". select "Load an additional driver". press the INSert key to install an unlisted driver and accept A:\ as the path to scan. Install ISSAPCI.DSK then ISSADSK.DSK (in that order). (the install action will copy all necessary files to the DOS Netware boot directory, typically c:\nwserver and copy some files to SYS:SYSTEM). Now exit from the installation menu. Return to the System Console command prompt. If the install did not invoke ISSAINST.NLM (typical when installing drivers that are already loaded) invoke it now by typing. LOAD C:ISSAINST Press when this NLM completes. DOWN, EXIT and restart your server. To install the device drivers on a system whilst installing Netware, Follow the instructions provided by Novell for installing Netware 4.1 When selecting disk device drivers to install, put the driver install diskette into your diskette drive (A:) select "additional drivers" press the INSert key to install an unlisted driver and accept A:\ as the path to scan. Install ISSAPCI.DSK then ISSADSK.DSK (in that order). (the install action will copy all necessary files to the DOS Netware boot directory, typically c:\nwserver). NOTE: The install NLM (ISSAINST.NLM) will report that it is unable to access SYS:SYSTEM. Press any key to continue. Continue with Netware install to load LAN drivers, etc. Once a SYS volume exists copy files to it by typing: LOAD A:\ISSAINST press when this NLM completes. DOWN, EXIT and restart your server. NOTES: - ONLY versions 4.x and 4.1 SMP of Netware are supported. - For performance reasons it is recommended that the .NLM and .NLS files are copied to the SYS: partition. However please note that the SYS: partition is used in preference and you MUST ensure that if you ever update the SSA RAID adapter software that any copies of code on the SYS: partition are refreshed at the same time using ISSAINST.NLM. - The Event Logger (ISSAELOG.NLM) records SSA events in a log file. It is advisable that the Event Logger be active at all times. This can be simply accomplished by adding the following line to your AUTOEXEC.NCF: LOAD ISSAELOG Using SSA for Operating System Boot =================================== If your primary boot device is a logical SSA drive, then the SSA adapter must be installed into a PCI slot with a lower number than that in which any SCSI adapters are installed. Verify that the SSA CBIOS has been enabled. During the power-up sequence of your computer you will see a message such as: SSA CBIOS is disabled, press the Tab key to enable it. Ensure that the message indicates that the CBIOS is ENABLED. You should also ensure that the SSA device drivers (ISSAPCI.DSK and ISSADSK.DSK) are loaded before any SCSI device drivers. INSTALLING FROM SERVER GUIDE FOR SSA OPERATING SYSTEM BOOT ========================================================== If you are installing your operating system onto an SSA disk then follow the instructions in your SSA Installation and Users Guide to: - Boot from the DOS Configurator and Service Aids diskette in order to attach an SSA resource to your PC Server. NOTE: Attach ONLY the devices which are to be the target for the installation. Start the installation normally, after the software keys have been entered the system will reboot. Immediately after the reboot process has begun insert a bootable DOS diskette with an editor available in the diskette drive. At the command line enter the following: C: [ENTER] cd \NW410 [ENTER] mkdir PCIDASD Insert the IBM SSA Drivers diskette in the diskette drive and enter the following: copy *.dsk c:\NW410\PCIDASD [ENTER] Edit the STARTUP.NCF in the root directory of the C drive and add the following lines at the BEGINING: load c:\NW410\PCIDASD\issapci.dsk slot=0 load c:\NW410\PCIDASD\issadsk.dsk slot=0 Rebooting the machine with the diskette removed should now allow the installation to complete normally. Possible Problems ----------------- ISSACFG/ISSAELOG UNABLE TO ACCESS NLS FILES? This probably means that the server has been set up to REMOVE DOS without ISSAINST.NLM having been run to copy the IBM SSA support files to the SYS volume. 520 WILL NOT BOOT? Isolated instances have been seen when a 520 server, will not boot first time from an operating system installed on an SSA DRIVE. The temporary solution is to reboot the PC Server. CREATING RAID ARRAYS? If you wish to create a RAID array you should ensure that all of the disks you elect to use as array members are the same capacity. NOTE: The smallest capacity of an array member is used when determining the size of the array. SYSTEM HANGS ON RELOAD Isolated incidents have been seen when Netware fails to restart if the server is downed and restarted. It is recommended that your PC is rebooted each time you wish to start Netware. ABENDS WITH "SET MEMORY ALLOC CHECK FLAG" PARAMETER SET It has been observed that, if the "set memory alloc check flag" parameter is set, then Novell Netware abends when exiting from the mirror status menu. This is a Novell Netware issue (not related to whether or not your SSA RAID Adapter is installed) and is believed to be fixed in an operating system patch available from Novell. SYSTEM DISKS 'DISAPPEAR' AFTER AN ADAPTER FIRMWARE UPGRADE It has been observed that after an adapter firmware update system disks disappear from the Netware configuration. This situation can be resolved by running 'scan for disks' from the Netware install utility. Adapter Firmware Download - ISSAADLD.NLM ------------------------- What it does ------------ ISSAADLD downloads an adapter microcode image to a specific SSA adapter, or to all SSA adapters it can find. Usage ----- usage: issaadld [-n node] [-a] [-Q] microcode flags: -n node identify adapter by node number (default all adapters) -a microcode is in AIF format (default is customer package) -Q quiet mode (default is verbose) microcode input adapter microcode image file Examples -------- To download a particular adapter microcode image (LD960701.dnd, for instance) to all SSA adapters: issaadld LD960701.dnd To download just to the adapter which is 'Node 13':- issaadld -n 13 LD960701.dnd *** IMPORTANT *** ----------------- Do NOT download whilst disks are performing I/O. All open occurrences of the SSA Configurator should also be closed, prior to performing the download. Only use this utility program when instructed to do so by your service representative since downloading incorrect images, for example, could have a detrimental effect on your SSA Subsystem. If after performing a download resources appear to be missing then the following action should be taken from the system console: 1. LOAD "INSTALL" [ENTER]. 2. Select the DISK OPTIONS menu and press ENTER. 3. Select the SCAN FOR ADDITIONAL DEVICES option and press ENTER. This will restore the original configuration. DASD Microcode Download - ISSADDLD.NLM ----------------------- ISSADDLD downloads a disk microcode image to a specific disk, or to all disks on a given SSA Adapter, or to all disks on all SSA Adapters. usage: issaddld [-a node] [-u serial] [-v vendor] [-f] [-q] microcode flags: -a node identify adapter by node number (default all adapters) -u serial 15 character full serial number (default all disks) -v vendor identify drive vendor (default is IBM) -f force download (default is to upgrade) -q quiet mode (default is verbose) microcode input disk microcode image file Examples -------- To download a new IBM DFHC microcode image (for instance, DFHC7968.DL) to all the disks on all the adapters: issaddld DFHC7968.DL To update all the DFHC disks on the adapter referred to as node 13:- issaddld -a 13 DFHC7968.DL Important --------- Do not download to disks whilst they are performing I/O. Only use this utility program when instructed to do so by your service representative since downloading incorrect images, for example, could have a detrimental effect on your SSA Subsystem. Errors may be generated in SSA Event Log. These can be ignored and are a result of adapter reset which is necessary to initialise the new microcode. SSA Configurator Error Messages ------------------------------- The Configurator does not currently display all error codes it in a meaningful textual fashion. The error codes include: 0xfffd : General non-specific failure return code. 0xfffc : Hardware error. 0xfff8 : Illegal request. 0xfff0 : Not in table. Can't find disk with given serial number. 0xffe2 : Not yet implemented. 0xffef : Disk is currently offline. 0xffe0 : Not found. 0xfe1e : Array is broken or degraded. Some operations require a non-degraded array. 0xfe1a : NVRAM error. Its probably full with dormant entries. You could go and delete a few and then retry. 0xfe17 : Bad component exchange candidate. 0xfe18 : Array is broken. Some operations require a non-broken array. 0xfe13 : Bad new component serial number. New component is not suitable for component exchange. 0xfe11 : Bad disk serial number. Perhaps the disk went offline. 0xfe0c : Bad serial number. Perhaps there is already an array with this name. 0xff3a : Can't delete in-use resource. You can only delete dormant NVRAM entries. 0xff39 : Operation is not applicable for resource type. Perhaps you're trying to do a disk type of operation to an NVRAM entry (you can only list and delete these). 0xff38 : NVRAM is defective. The only sensible option here is to replace the module. Trademarks and Notices ---------------------- The following terms are trademarks of the IBM Corporation in the United States or other countries or both: IBM, OS/2 Microsoft and Windows are trademarks or registered trademarks of Microsoft Corporation. Novell Netware is a trademark or registered trademark of Novell Inc. Other company, product, and service names may be trademarks or service marks of others. THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE AND MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM GRANTS NO LICENSES TO ANY PATENTS OR COPYRIGHTS. Note to U.S. Government Users -- Documentation related to restricted rights -- Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp.