StorageWorks RAID Array 200 Software Kit for Intel-Based Systems V3.0 Release Notes These notes identify information not available at publication time of the online management utilities for Intel-Based Systems user guides, and identify known limitations of these utilities, and various specifications for these products, such as part numbers and version levels. COPYRIGHT Digital Equipment Corporation 1994/95. All Rights Reserved. COPYRIGHT Mylex Corporation 1994/95. All rights reserved. This software is proprietary to and embodies the confidential technology of Mylex Corporation and Digital Equipment Corporation. Possession, use, or copying of the software and media is authorized only pursuant to a valid written license from Digital Equipment Corporation or an authorized sublicensor. RESTRICTED RIGHTS: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of DFARS 252.227-7013, or in FAR 52.227- 19, or in FAR 52.227-14 Alt. III, as applicable. Note: The printed copy of Release Notes provided with the software kit may vary from this softcopy. The softcopy is more recent. GENERAL NOTES FEEDBACK We encourage you to send us feedback on our products. If there are any suggestions or comments you would like to make, please send: Email to: sbemgr@subsys.enet.dec.com U.S. Mail to: SBEMGR Digital Equipment Corporation Mail stop SHR3-2/W8 334 South Street Shrewsbury, MA 01545 CONTROLLER TERMINOLOGY In reading the accompanying RAID Array 200 documentation, please note the following terminology associations: This Refers to Or RAID Array 210 EISA KZESC-xA, KZESC-xB SWXCR-EA, SWXCR-EB controller RAID Array 230 PCI KZPSC-xA, KZPSC-xB SWXCR-PA, SWXCR-PB controller The RAID Array 200 Controller documentation and software uses SWXCR for generic references to controllers. NUMBER OF SWXCR CONTROLLERS SUPPORTED All of our drivers and utilities are setup to support four controllers (any combination of EISA or PCI) with the exception of SCO UNIX. The total number of EISA/PCI SWXCR controllers supported under SCO UNIX is two (in any combination). CONFIGURATION WITH SHARED INTERRUPTS We recommend using edge triggered interrupts for the SWXCR controller.However, if you choose to use level interrupts, limit the number of boards sharing the same interrupt to avoid performance problems. TERMINATION The SWXCR-Px (KZPSC-xx) must be at the end of the SCSI bus in an 8 bit environment for proper termination of the unused SCSI signals. You do not need to make any changes on the shelf end of the SCSI connection, simply follow the appropriate documentation. When using Fault Management the terminators used must support Fault Management. The SWXCR controllers are supplied with termination that supports Fault Management. Check with your system supplier to be sure that system/device termination supports Fault Management, otherwise the Fault Management option must be DISABLED on the controller. If there is termination attached to any channel of the SWXCR that does not support Fault Management the results are unpredictable with Fault Management is not DISABLED. REVISION MATRIX The following table cross references the hardware board revision levels for the RAID Array 200 family of controllers with the release date and revision level of the software accompanying the board. The FW and BIOS columns refer to firmware and BIOS revision levels; the other columns refer to the version numbers of the respective distribution diskettes for the release of all Intel based utilities (KIT), the Standalone Configuration Utility (RCU), Windows NT (NT), NetWare (NW) and SCO UNIX (SCO) utilities. Hardware Software/Documentation Rev Matrix for INTEL Platforms Product Board FW BIOS KIT RCU NT NW SCO Rev KZESC C01 1.99 1.17 1.0 1.0 1.0 1.0 1.0 (4/94) KZESC C02 2.15 1.17 2.0 2.0 2.0 2.0 1.0 (3/95) KZESC C02 2.15 1.19 3.0 2.1 2.1 3.0 2.0 (4/95) KZPSC A02 2.19 1.02 N/A N/A N/A N/A N/A (3/95) KZPSC B01 2.19 1.02 3.0 2.1 2.1 3.0 2.0 (4/95) N/A = Not Available under this kit release. KIT/BOARD COMPATIBILITY As a general rule, the latest kit can be used with any board revision and provided upgrade paths. Older kit revisions cannot be used with newer board revisions, because they are not compatible. PART NUMBERS Product Part Number Description CK-SWXCR-AA Cable kit for KZESC-xB (SWXCR- EB) includes internal and external "Y" cables BN21H-02 8 bit SCSI cable (2m) for KZESC BN31L-1E 8 bit SCSI cable for KZPSC BN31K-0E 16 bit internal cable for KZPSC-xB BN31M-1E 16 bit SCSI cable for KZPSC to BA346 BN31S-1E 16 bit SCSI (right angle) cable for KZPSC to BA356 KZPSC-UB Battery backup for KZPSC cache memory MS100-AA 16MB Cache memory for KZPSC and KZESC MS100-AB 32MB Cache memory for KZPSC and KZESC WRITE BACK CACHE If you plan to use write back cache on the SWXCR-Px controllers you should order the Battery backup option for the controller to avoid data loss under circumstances where the controller is unable to complete a write operation to disk (for example, power failure). Also we recommend that the disk drives attached to the controller have their write cache disabled; contact your drive vendor for more information. STANDALONE AND CONFIGURATION UTILITY Standalone RAID Array 200 Software V2.1 for Intel systems swxcrmgr.exe Intel RAID configuration utility. swxcrbio.exe Bios upgrade utility for EISA controllers swxcrbio.119 1.19 version of the EISA RAID controller Bios. swxcrfw.exe Firmware download utility for EISA and PCI controllers. swxcrfwa.215 2.15 Firmware for EISA RAID controller. swxcrfwp.219 2.19 Firmware and 1.02 Bios for the PCI RAID controller. !mlx0075.cfg Generic EISA configuration file for the 3 channel Eisa raid controller. !mlx0077.cfg Generic EISA configuration file for the 1 channel Eisa raid controller. WARNING!!! Make sure you use the correct firmware file for the controller to be upgraded. Using the wrong firmware file can render your controller useless. The FWA file is for EISA controllers and the FWP file is for PCI controllers. FAILING A DRIVE. Failing a drive in the standalone utility will spin the drive down. Selecting Format under the Rebuild option will not spin the drive up. Reselecting the controller under the Select SWXCR option will spin the drive up and allow a format under the rebuild option. NOVELL NETWARE NOTES RAID Array 200 Software V3.0 for Intel NetWare 3.1x/4.x USE OF INTERRUPT 15 IN NETWARE SWXCR controllers in the Novell NetWare operating environment must not be configured to use IRQ 15. PASSTHRU DEVICE SUPPORT ON THE SWXCR CONTROLLER UNDER NETWARE Use of passthru devices (for example, CD-ROM and tape drives) is possible by loading the included ASPI drivers for NetWare (SWXCRASP.DSK for v3.1x and SWX40ASP.DSK for v4.x). Please note that only one ASPI driver from any vendor may be loaded under NetWare at any one time. Some vendors (for example, Adaptec) do not allow optional loading of their ASPI module. If you choose to use drivers of this type you will not be able to use the SWXCR ASPI modules to provide passthru support. This would not prevent use of the SWXCR to controller disk devices. When using passthru devices on the SWXCR, the following restrictions apply: Each controller may be configured with a maximum of 7 passthru devices. Each passthru device must occupy a unique SCSI ID (for example., ID 0 to ID 6) within the controller. NETWARE DOCUMENTATION Chapters 2 and 3 of the RAID Array 200 Online Management Utility for NetWare 3.1x and 4.x indicate by example two methods for loading the NetWare utilities. The method in Chapter 2 describes copying the utilities to the NetWare SYS: volume. This method enables loading the utilities from the system console without specification of a path component. The alternative method described in Chapter 3 is to copy the utility files to a MS-DOS directory. This procedure avoids the necessity of logging into the server from a client workstation to complete the installation. You may choose which ever method is most convenient for your needs. Note that the disk driver modules (SWXCRDRV.DSK for v3.x and SWX40NET.DSK for v4.x) must be installed into a MS-DOS directory in order to remain accessible to the server at boot time. UTILITY VERSION NUMBERS The revision levels for the NetWare utilities are: SWXCRMON.NLM v3.07 SWXCRMGR.NLM v3.04 NOVELL NETWARE RELEASE DISK V3.0 FILE LIST release.txt swxasp40.dsk swxcrasp.dsk swxcrdrv.dsk swxcrmgr.nlm swxcrmon.nlm swxnet40.ddi swxnet40.dsk SCO UNIX Notes RAID Array 200 Software V2.0 for Intel SCO UNIX SCO UNIX DISTRIBUTION DISKETTE FORMAT The distribution diskette for SCO UNIX is a UNIX formatted floppy for BTLD installations. It is unreadable under MS-DOS. CONFIGURATION OF DEVICES ON THE SWXCR CONTROLLER Configuration of disk and passthru devices is performed using the standard SCO UNIX command, mkdev. Disk devices are configured using mkdev hd syntax. Likewise, tape and CD-ROM drives use mkdev tape and mkdev cdrom syntax. In use, the mkdev command will prompt for a SCSI ID and logical unit number (LUN) when creating each device. All disk devices should be configured with LUN = 0. All passthru devices should be defined with LUN = 1. Each of the controller’s 8 possible disk drives must be assigned a unique SCSI Id (for example, ID 0 to ID 7). Each controller may be configured with a maximum of 7 passthru devices. Each passthru device must occupy a unique SCSI ID (for example, ID 0 to ID 6) within the controller. SCO UNIX SWXCR NAMING CONVENTIONS Name Description swxcr Driver package name xcr Driver name /dev/rreX00 Controller node name where X is 0 for the first SWXCR controller where X is 1 for the second SWXCR controller Use SCO standard device names For Hard disk/Tape/CD-ROM node names PARTITION RESTRICTIONS UNDER SCO UNIX SCO UNIX imposes a file system size limit of 2 GB for each of 7 partitions per logical drive. This yields a total usable logical RAID drive size of 14 GB (7x2 GB). Please note this when configuring Logical RAID Drives with the Standalone Utility. SCO UNIX DOCUMENTATION In the Main Menu of the swxcrtk utility, options 3, 4, 5, and A contain a Note referring the user to the SWXCR manual chapter entitled "Terminology." Please refer to table 2-2 in the StorageWorks RAID Array 200 Online Management Utility for SCO UNIX Users Guide in these instances. UPGRADES SHOULD BE PERFORMED IN SINGLE-USER MODE To upgrade an existing SCO UNIX installation with the RAID Array 200 Online Management Utility, bring the system to a single-user mode prior to beginning the upgrade. This will ensure that the swxcrmon process is properly updated. FRESH SCO UNIX INSTALLATIONS ON THE SWXCR CONTROLLER When performing a fresh installation of SCO UNIX in conjunction with the RAID Array 200 Online Management Utility, the following devices are automatically configured to facilitate the SCO installation: First Hard Disk: @SCSI ID 0 on the first SWXCR controller, LUN 1 Tape @ SCSI ID 2 on the first SWXCR controller, LUN 0 STOPPING AND STARTING THE SWXCRMON PROCESS The swxcrmon process is configured to start automatically when installed. If you do not want the swxcrmon process to automatically start at system startup, you can relocate the script file xcr which is located in the directory /etc/idrc.d. Move the xcr script file to another directory for safekeeping; the swxcrmon process will then not start automatically. Restoring the file to the /etc/idrc.d directory will resume the automatic invocation of the swxcrmon process on system startup. You can start the swxcrmon process anytime by manually running the command swxcrmon from a shell prompt. DEFAULT LOCATION OF THE SWXCRMON LOG FILE The default location for the swxcrmon log file is /usr/adm/swxcrmon.log. You can change this to another file specification by giving the desired file specification as a command line argument when manually invoking swxcrmon or by editing the /etc/idrc.d/xcr file. In the latter case, add the new log file specification after each occurrence of the swxcrmon command. SWXCRMON MESSAGE OUTPUT When swxcrmon is invoked as a foreground process, its message output is sent to its log file and the terminal window from which is was started. In the case of invoking swxcrmon as a daemon process (for example, with the -d switch), the message output will go to the log file and the console. UTILITY VERSION NUMBERS The revision levels for the SCO UNIX utilities are: swxcrmon v2.4 swxcrsh v2.3 swxcrtk v2.4 SCO UNIX RELEASE DISK V2.0 FILE LIST ./install/INSTALL ./man/swxcrmon.ADM ./man/swxcrsh.ADM ./man/swxcrtk.ADM ./sco_rel.txt ./swxcr/install/btld ./swxcr/install/drivers ./swxcr/install/postinstall ./swxcr/install/swxcr.name ./swxcr/new/usr/lib/mkdev/swxcr ./swxcr/new/usr/swxcr/2.mod ./swxcr/new/usr/swxcr/3.mod ./swxcr/new/usr/swxcr/id.dat ./swxcr/new/usr/swxcr/locking ./swxcr/new/usr/swxcr/unlocking ./swxcr/new/tmp/mdevice ./swxcr/new/tmp/scsihas ./swxcr/new/etc/perms/swxcr ./swxcr/new/etc/conf/pack.d/xcr/mdac.h ./swxcr/new/etc/swxcrsh ./swxcr/new/etc/rbldsh ./swxcr/new/etc/swxcrmon ./swxcr/new/etc/swxcrtk ./swxcr/driver/xcr/Driver.o ./swxcr/driver/xcr/Bootload ./swxcr/driver/xcr/Space.c ./swxcr/driver/xcr/Master ./swxcr/driver/xcr/System ./swxcr/driver/xcr/Node ./swxcr/driver/xcr/Rc ./swxcr/driver/xcr/Space.o ./swxcr/driver/xcr/mdac.h ./swxcr/driver/xcr/Driver.boot WINDOWS NT NOTES RAID Array 200 Software V2.1 for Intel Windows NT WINDOWS NT ON THE DIGITAL PRIORIS HX 590 FAMILY OF SERVERS When a PCI SWXCR controller is used on the Digital Prioris HX 590 server, it must be installed in the primary PCI bus slots (slots 1, 2, and 3). Windows NT version 3.51 is the minimum required revision level of the NT operating system on this platform. INSTALLATION OF NT ON SWXCR BOOT PARTITIONS WITH MULTIPLE LOGICAL DRIVES There is a limitation in the Windows NT installation mechanism which results in a failure to successfully complete an installation to a SWXCR boot device when more than one logical drive is defined on that device. The failure will occur when the system attempts to boot after the first three floppy disks are loaded. This limitation can be overcome by one of two methods. Method one is to simply install an MS-DOS partition on the first logical drive before beginning the Windows NT installation. Method two is to postpone creation of the second and subsequent logical drives until after Windows NT is completely installed on the first logical drive. PARTITION RESTRICTIONS UNDER WINDOWS NT The Windows NT boot partition size cannot exceed 2024 MB in size. Please note that any FAT partition created which is over 2 GB in size will be inaccessible to MS-DOS. Please see Microsoft’s Windows NT documentation for further details. PASSTHRU DEVICE SUPPORT ON THE SWXCR CONTROLLER Windows NT v3.1 does not support passthru devices such as tape drives and CD-ROMs, for example. Windows NT 3.5 and later support any number of passthru devices without restrictions. SYSTEM SERVICES VERSION OF THE SWXCRMON UTILITY There is provided an alternative version of the SWXCRMON utility that operates as system service under Windows NT. This version will start automatically whenever the NT system is booted. Otherwise, the system service monitor is identical in functionality to the standard version provided through the SETUP routine. You may use each version separately or together. We welcome any comments you have regarding this utility; please see the address shown under the feedback section of the General release notes. The files for the system service monitor utility are located on the NT release disk under the directory \serv_mon. The instructions for installation and removal of the utility are contained in the file SWXCRSRV.REL located in that directory. UTILITY VERSION NUMBERS The revision levels for the Windows NT utilities are: SWXCRMON v1.35 SWXCRMGR v1.26 SWXCR DRIVER ON THE WINDOWS NT V3.5 CD-ROM The miniport driver for the SWXCR controller is included on the Windows NT distribution media for Windows NT 3.5. The version of the driver included on the v3.5 CD has the following problems: a) Level interrupts can not be used for any SWXCR controller as this will cause the system to hang. b) There is a bug while using tape devices to backup data on any Logical RAID Drive while there is activity to the same or other Logical RAID Drives which will cause the system to panic and crash. The above problems have been fixed and a new version of the SWXCR driver is included on this floppy in the root directory. To load and use this new driver simply copy the file DAC960NT.sys from the floppy to the Winnt35\system32\drivers directory of your system. This can only be done after installing the operating system and the controller using the driver on the distribution CD. USE OF DISK ADMINISTRATOR IN WINDOWS NT 3.5 There is a problem in the Windows NT 3.5 operating system that may be seen while using the SWXCR Monitor or SWXCR Manager in conjuction with the Disk Administrator utility. Using the above utilities together may cause the system to crash. Contact Microsoft support and say you want the fix for bug #25912, which is a new SCSIPORT.SYS file for Windows NT 3.5, to correct this problem. HELP FILE IN THE SWXCRMGR The 'Help file...' option under the Help menu of the SWXCR Manager has not been enabled. Windows NT default help will be displayed. WINDOWS NT RELEASE DISK V2.1 FILE LIST dac960nt.sys mscomstf.dll mscuistf.dll msdetstf.dll msinsstf.dll msshlstf.dll msuilstf.dll oemsetup.inf release.txt setup.exe sw31mgr.exe sw31mon.exe sw_scsi swxcr.inf swxcrmgr.exe swxcrmon.exe txtsetup.oem upgrade.txt a:\nt31 dac960nt.sys oemsetup.inf a:\serv_mon messages.dll swxcrsrv.exe swxcrsrv.rel xcrsrvc.exe