File Name: SYMMPI2K.TXT LSI Logic Fusion-MPT (TM) Driver: SYMMPI.SYS V1.08.16 CONTENTS --------- 1.0 Overview 2.0 Change history 3.0 Installation and setup instructions 4.0 Configuration information 5.0 Unattended mode 6.0 Web sites and support phone number 7.0 Trademarks and notices 8.0 Disclaimer 1.0 Overview: This file describes the features and use of the LSI Logic Fusion-MPT small computer interface (SCSI) device drivers for the Windows 2000 operating system environment. 1.1 Overview about this code: None. 1.2 Limitations: o If upgrading an existing LSI driver installation, version 1.08.12 or higher is required. Do not use this driver package to update from versions earlier than 1.08.12. Instead, use the driver update utility from the IBM support web page to install version 1.08.12 and then upgrade to the latest level. The Windows 2000 operating system may have to be reinstalled if this package is used to update the older SYMMPI.SYS driver. o Download and install the latest level of the system BIOS before installing this driver. IBM eserver xSeries 345 and IBM eserver xSeries 235 should be at BIOS level 1.02 or later. 1.3 Enhancements: The SYMMPI.SYS miniport driver supports these features: o Supports 320 Mbytes/s parallel SCSI transfers (for LSI453C1020 and LSI53C1030) o Supports Integrated Mirroring (TM) technology (for LSI453C1020 and LSI53C1030) o Supports PCI and PCI-X bus protocols (for LSI53C1020 and LSI53C1030) o Supports LSI Logic MPT common software interface o Supports multiple host adapters o Supports multiple Logical Unit Numbers (LUNs) o Supports Scatter-Gather o Supports SCSI pass-through functionality o Supports disk array configurations with no LUN 0 o Supports disk array configurations with non-contiguous LUNs o Auto request sense o Maximum block size support: 1 Mbyte 1.4 Level of recommendations and prerequisites for the Update: o If upgrading an existing LSI driver installation, version 1.08.12 or higher is required. Do not use this driver package to update from versions earlier than 1.08.12. Instead, use the driver update utility from the IBM support web page to install version 1.08.12 and then upgrade to the latest level. The Windows 2000 operating system may have to be reinstalled if this package is used to update the older SYMMPI.SYS driver. o Download and install the latest level of the system BIOS before installing this driver. IBM eserver xSeries 345 and IBM eserver xSeries 235 should be at BIOS level 1.02 or later. 1.5 Dependencies: None. 2.0 Change history -------------------- 1.08.16 o Fixed more hibernation issues 1.08.12 o Fixed more hibernation issues o Fixed Windows Blue Screen when hot-swapping drives o Fixed Driver Update issue so future drivers can be updated without update utility 1.08.04 o Fixed hibernation issues o Fixed Windows Blue Screen for LSI FW 1.00.03 or greater 1.08.00 New release. 3.0 Installation and Setup Instructions ----------------------------------------- 3.1.0 Introduction for Windows 2000 Windows 2000 is an operating system designed to run on Intel-architecture processors using current technology. It provides a graphical user interface (GUI) environment incorporating many high-level features. Refer to the Microsoft Windows 2000 documentation for details. An input/output (I/O) manager handles I/O requests in Windows 2000. To address a SCSI peripheral, the I/O manager goes through the appropriate drivers. Windows 2000 provides class drivers for hard disk, optical, CD-ROM, printer, and scanner peripherals. Other class drivers, provided by peripheral manufacturers, may be added to support new devices. Tape device support is built into the operating system and does not require a class driver. Microsoft provides the port driver and LSI Logic provides the miniport driver,called SYMMPI.SYS. This driver completes the path to the LSI Logic controller or processor with an optional SCSI BIOS. LSI Logic uses the same filenames for their drivers for different Windows operating systems. The driver files are packaged either in separate subdirectories based on the Windows operating system or on different disks. To determine the driver file for Windows 2000, note that the filename ends with .SYS. For example, this driver is SYMMPI.SYS. To determine the operating system version, go into Windows Explorer, display the driver file, right click on the filename, click Properties, and click on the Version tab. Finally, click the Internal Filename in the lower section. For Windows 2000, the filename appears as filename (Win2K). The next sections describe these drivers and their installation. 3.1.1 Features The SYMMPI.SYS miniport driver supports these features: o Supports 320 Mbytes/s parallel SCSI transfers (for LSI453C1020 and LSI53C1030) o Supports Integrated Mirroring (TM) technology (for LSI453C1020 and LSI53C1030) o Supports PCI and PCI-X bus protocols (for LSI53C1020 and LSI53C1030) o Supports LSI Logic MPT common software interface o Supports multiple host adapters o Supports multiple Logical Unit Numbers (LUNs) o Supports Scatter-Gather o Supports SCSI pass-through functionality o Supports disk array configurations with no LUN 0 o Supports disk array configurations with non-contiguous LUNs o Auto request sense o Maximum block size support: 1 Mbyte 3.1.2 LSI Logic devices supported The name of the SYMMPI.SYS driver is "LSI Logic PCI SCSI/FC MPI Miniport Driver" It supports the following devices and their associated host adapters: o LSI53C1020 (LSI20320) o LSI53C1030 (LSI21320, LSI22320) 3.1.3 Description The SYMMPI.SYS driver meets the Microsoft specification for miniport drivers. This driver allows connection of parallel SCSI devices including disk drives, CD-ROMs, and tape drives for PCI and PCI-X based machines. To support a different SCSI device type, the Windows 2000 architecture requires that a class driver for that type of device be present (usually supplied by Microsoft, or possibly by the peripheral manufacturer). No changes to SYMMPI.SYS are required. The driver supports only Windows 2000 and all subsequent Service Packs. A Windows application passes SCSI commands directly to the parallel SCSI Protocol devices by using the SCSI pass-through facility. This facility allows applications to directly control and access devices by filling in a data structure and calling into the port or class driver. Refer to the Microsoft Windows 2000 documentation for more details. 3.2.0 Installing the SYMMPI.SYS driver This procedure installs the SYMMPI.SYS driver onto a new Windows 2000 system. Depending upon the media used to distribute LSI Logic drivers (web or CD-ROM), you will create a driver diskette. Copy the files listed in this section to the root directory of a clean diskette as shown below. Label this diskette "Windows 2000 Driver Diskette". You will use this diskette during the installation process. \txtsetup.oem \symmpi.sys \symmpi.tag \oemsetup.inf 3.2.1 New system installation Download and install the latest level of the system BIOS before installing this driver. IBM eserver xSeries 345 and IBM eserver xSeries 235 should be at BIOS level 1.02 or later. This procedure installs the SYMMPI.SYS driver onto a Windows 2000 system. Use this procedure when installing Windows 2000 onto an unused drive. Windows 2000 automatically adds the driver to the registry and copies the driver to the appropriate directory. The method for installing Windows 2000 on a new system involves using a CD-ROM. Refer to the Microsoft document for installing Windows 2000 using boot floppy diskettes. 3.2.1.1 CD-ROM installation 1. Begin the Windows 2000 installation by starting from the Windows 2000 CD-ROM: The system BIOS must support starting from a CD-ROM. BIOS settings may need to be changed to allow CD-ROM starting. 2. Press the F6 key to install the SYMMPI.SYS driver when the screen displays "Windows 2000 Setup". This must be done or else the new driver will not be recognized. Note: Be sure to press the F6 key as any driver loaded later in the installation process is not recognized by Windows 2000 Setup. If F6 is not pressed, all devices controlled by the drivers are not available during Windows 2000 setup. 3. Choose S to specify an additional device when the screen displays "Setup could not determine the type of one or more mass storage devices...". Note: If the setup program does not display this screen first for user input, the setup program did not recognize pressing the F6 key. Restart the system and try again. The system prompts for the manufacturer-supplied hardware support disk. 4. Insert the appropriate driver diskette containing the Windows 2000 driver required to support your LSI Logic adapter(s) and press Enter. Note: You can go to the IBM Support Web site at http://www.ibm.com/pc/support/ to check for the current Windows 2000 drivers. 5. Press Enter to proceed. Return to the Windows 2000 Setup screen. 6. Press Enter to proceed. The message about setup loading files appears. 7. Follow the Microsoft Windows 2000 installation procedure at this point. 3.2.2 Existing system installation This driver package should be used for new installations only. Do not use this driver package to update a current Windows 2000 installation! Instead of using this package, download the driver update utility from the IBM support web page. The Windows 2000 operating system may have to be reinstalled if this package is used to update the SYMMPI.SYS driver. 3.2.3 Performance tuning for Windows 2000 Windows 2000 has registry entries that can be used to tune the performance of SCSI I/O for certain configurations. The tunable parameters are large transfer block size support and a assured number of concurrent I/Os for a particular SCSI bus. 3.2.3.1 Large block size support The SYMMPI.SYS drivers can support up to a 1 Mbyte transfer size in Windows 2000; however, the default Windows 2000 transfer size is 64 Kbytes. To enable better performance, the driver installation process adds a registry entry to enable a maximum 256 Kbytes transfer size. Also, the mpi_256K.reg file can be used to set or re-enable a 256 Kbytes maximum, but it can be edited to set other maximum transfer sizes that you want. There are two methods to add this registry setting. 1. Locate the mpi_256K.reg data file (supplied with the driver files) using Windows Explorer and double-click on the file. or 2. Type at the command prompt: regedit mpi_256K.reg This inserts an entry in the registry to enable 256 Kbytes block size support. Editing the mpi_256K.reg can set any maximum block size between 64 Kbytes and 1 Mbyte. The formula to calculate the proper value for MaximumSGList is: MaximumSGList = ((Maximum Block Size)/4 Kbytes) +1 For 256 Kbytes: 256 Kbytes/4 Kbytes = 64, add 1 for 65 (decimal) or 0x41 (hexadecimal). The maximum value allowed for MaximumSGLIst is 255 or 0xFF. For the particular value of 0xFF, the internal value passed to Windows is increased to 0x101, allowing support for a full 1 Mbyte transfer. Be sure to read the information in the mpi_256K.reg data file before editing it. The system must be restarted for the new registry setting to be effective. To reset the maximum block size to the default of 64 Kbytes, follow the instructions above, except use mpidfblk.reg as the data file. 3.2.3.2 Maximum number of concurrent I/Os (Assured) Windows 2000 guarantees a maximum of 32 concurrent I/Os active on a particular SCSI bus. However, due to the method of memory allocation, the actual limit of concurrent I/Os can vary greatly between various drivers or versions of drivers. This can have a huge impact on performance benchmarking between different driver versions or adapter vendors. In effect, one adapter may actually be able to have 70 or 80 I/Os outstanding, while another adapter could only have 32. This can also affect systems with high performance storage subsystems, such as disk arrays. In order to enable better performance, the driver installation process adds a registry entry to support 128 concurrent I/Os. If a different maximum value is not what you want, the file mpi100io.reg can be used to add a registry entry to guarantee the number of concurrent I/Os that you want. There are two methods to add this registry setting. One is to locate the mpi100io.reg data file (supplied with the driver files) using Windows Explorer and double click on the file. The other method is to type at the command prompt: regedit mpi100io.reg This inserts an entry in the registry to guarantee a maximum of 100 concurrent I/Os per adapter. If a maximum other than 100 is what you want, the mpi100io.reg can be edited; however, setting this value to a high number uses increasing amounts of non-paged pool memory, a critical NT resource. High values for this setting can degrade system performance. Be sure to read the information in the mpi100io.reg data file before editing it. The system must be restarted for the new registry setting to be effective. To reset the number of concurrent I/Os to the default of 32, follow the instructions above, except use mpidefio.reg as the data file. 3.2.3.3 Miniport driver configuration options The SYMMPI driver is configured by default to provide optimum performance in most standard systems. Some non-standard systems may require some fine tuning to obtain peak system memory utilization and performance. After installation, if less than advertised functionality and performance is observed on any platform, please contact LSI Logic support. Go to the LSI Logic Technical Support Home Page, which is located at: http://www.lsilogic.com/support/index.html and call the listed number for assistance. LSI can provide additional registry settings if required, to customize the driver for specific systems and applications. 3.3.0 Troubleshooting The SYMMPI.SYS driver will log error messages to the system error log. For these errors, the system errorlog EventID will be 11, and the specific error code values will be displayed at offset 0x10. Data should be displayed in words. 4.0 Configuration Information ------------------------------- 4.1 Include any configuration installation: None. 4.2 Configuration Settings: None. 4.3 Hardware Status and Information: None. 5.0 Unattended Mode ------------------------------- 5.1 Steps for unattended mode: None. 6.0 WEB Sites and Support Phone Number ---------------- 6.1 IBM Support Web Site: http://www.ibm.com/pc/support 6.2 IBM Support Telephone Numbers: http://www.ibm.com/planetwide/ 7.0 Trademarks and Notices ---------------------------- 7.1 The following terms are trademarks of the IBM Corporation in the United States or other countries or both: IBM 7.2 Intel trademarks or registered trademarks are trademarks of Intel Corporation. Microsoft and Windows 2000 are trademarks of Microsoft Corporation in the United States, other countries, or both. 7.3 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 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. Appendix A: Package Specific Installation Instruction This update is packaged as a self-extracting Package for the web (PFW). To unpack, this update requires that your TEMP environment variable be set to a path with read/write access. You must be logged in as an administrator. The command-line syntax for Package-For-The-Web Driver update package is: Package.exe [-s] [-a [-s] | [-x directory] | [-?] ] [-s] This initial -s tells the Package-For-The-Web software to install silently and will not prompt if files need to be over-written in the %temp% directory. [-a] Tells the Package-For-The-Web software to pass all subsequent commands to the install package (i.e. the update). [-s] The second -s option indicates to run the update silently and unattended. For firmware updates the update is scheduled to run on the next reboot. An immediate reboot can be forced with the -r option. [-x directory] Use with firmware updates to extract the update to directory named directory. Since the Package-For-The-Web extracts itself to subdirectory in the %TEMP% directory, a relative directory will be relative to that location. Normally the user will want to specify an absolute directory. [-?] Display information about the command line switches. Only the apply-update-silently (-s) option is necessarily unattended, that is the other command line options such as display help (-?) may require the user to "hit any key" to continue. If Windows packages are run without any command line options, a GUI is displayed. This GUI offers all the options available at the command line, except that the -w option is not available.