Dear SCO Customer, Support Level Supplement (SLS) PTF7002J, the MPIO Update Supplement, addresses various MPIO, sdi, and sysdump issues found with UnixWare 7. Read this document completely before attempting to install this SLS. SLS PTF7002J contains modifications to the Base System (base) and OS Multiprocessor Support (osmp) packages of UnixWare 7. If you are preparing to install either the base and/or osmp packages, discontinue the installation of PTF7002J, install those packages first, and then install PTF7002J. If you later install either the base or osmp packages on your system, you must reinstall this SLS to get the fixes back for those packages. Note: SLS PTF7002J supersedes PTF7020A, the UnixWare 7 sysdump Supplement, and all previous versions of PTF7002. SLS PTF7020A should be removed from your system prior to installing PTF7002J. It is not necessary to remove earlier versions of PTF7002 before installing SLS PTF7002J. SLS PTF7002J contains these files: /etc/conf/pack.d/clariion/Driver.o /etc/conf/pack.d/clariion/space.c /etc/conf/pack.d/mpio/Driver.o /etc/conf/pack.d/sd01/Driver.o /etc/conf/pack.d/sd01/space.c /etc/conf/pack.d/sdi/Driver_atup.o /etc/conf/pack.d/sdi/Driver_mp.o /etc/conf/pack.d/sdi/space.c /etc/conf/sdevice.d/mpio /etc/rc2.d/S15static_conf /etc/scsi/pdi_hot /etc/scsi/pdimkdev /etc/scsi/sdipath /etc/scsi/sdistatic /usr/include/sys/mpio_ioctl.h /etc/conf/pack.d/sysdump/Driver_atup.o /etc/conf/pack.d/sysdump/Driver_mp.o /etc/conf/pack.d/sysdump/space.c SLS PTF7002J contains these changes: - Multipath I/O will be supported. - Error messages produced by MPIO will be more informative. - Output from sdipath will be more informative. - The system will no longer hang under a particular condition. - On a failure to a Clariion device, all logical units associated with the active SP will be trespassed onto the alternative SP. - Device tab will not lose entries when ghosting naming is in effect. - In cluster configurations, access to unstamped disks will not cause the system to hang. - The system will not panic when a SCSI bus reset is issued. The following resolved problems were new as of PTF7002B: - A temporary solution for static configuration is implemented. The system will detect and display warning messages for any change in the configuration of the SDI subsystem. - The sdirm(1M) command will no longer panic the system and now can handle devices with logical unit numbers (LUNs) greater than 7. The following resolved problem was new as of PTF7002C: - Changes to the trespass policy on the failure of an active path. Previously, when a trespass was issued on an alternative path, only the LUN in question would become active on this path. Now, all LUNs currently associated with the failed path will become active on the path that receives the trespass. The following resolved problems were new as of PTF7002F: - System avoids accessing devices which are supported but not currently connected. sdi_check_dev() will no longer call sdi_cklu() on devices which are supported but not currently connected resulting in 'check condition' errors. - Modification to sdi_check_dev() behavior so that it cannot be called before the sdi_HotAdd(). This addresses the problem of sdi_check_dev() being called by sdi_hot_add() before the HBA was correctly initialized to handle it, resulting in sdi driver panics when disk was hot-added. - Modified memory allocated for B_RXEDT* ioctls. Insufficient memory may result in sdi driver panics when target has a large number of LUNs. - Incorporated sd01intn() mods from UW2.1.3 which are required in a multiple-initiator environment to avoid BUSY/QUEUE FULL conditions from causing I/O errors. The following resolved problems were new as of PTF7002H: - kmem_free panic under heavy disk-tape-diskette-cdrom-memory usage. - Recursive dumping - system can repeatedly panic while writing a dump. - Private page tables are now included in selective dump. - Fixed hang in qlc1020_timeout_remove+97 when testing MPIO. - Fixed path fail panic. - Speeded up MPIO dual path failover. - Made changes to increase probability of a successful dump. The following resolved problems were new as of PTF7002I: - Memory leak on IH112 IU48 connected to vtoc opens. - Unable to create emergency recovery diskettes after PTF7036C applied. - sar data not useful with large EMC RAID box. The following resolved problem is new as of PTF7002J: - potential of kma corruption, fix to sd01 target driver. The manual page for sdistatic has been provided with PTF7002J: sdistatic(1M) sdistatic -- validate Current I/O Subsystem Config against Desired Config Synopsis /sbin/sdistatic [-f|-r|-c] Description The sdistatic command is used to save, compare and restore a desired disk subsystem configuration (disks and paths), based on the boot time groped configuration. Options sdistatic takes the following options: -f Snapshot the current I/O subsystem configuration and use it in all further invocations of sdistatic as the current desired configuration. -r Restore the desired I/O Subsystem configuration as the currently active configuration. -c Compare the current I/O subsystem configuration against the saved desired configuration, reporting differences as below: If paths to devices (or the devices themselves) are missing: WARNING: Path was removed from disk stamp . The failure of a device is reported as the failure of all paths to that device. If new paths (or disks) have been added: WARNING: Path was added to disk stamp . Software Notes and Recommendations ---------------------------------- SLS PTF7002J should only be installed on: UnixWare 7 with UnixWare 7 Release Supplement (uw7rs) applied To find out what release your system is running, use the command: # uname -sv The command will return "UnixWare 7" if this release is installed. To determine if the UnixWare 7 Release Supplement is installed, run the command: # pkginfo | grep uw7rs If the Release Supplement is installed, this command will return "patch uw7rs uw7rs - SCO UnixWare 7 Release Supplement". Installation Instructions ------------------------- 1. Download the ptf7002j.Z and ptf7002j.txt files to the /tmp directory on your machine. 2. As root, uncompress the file and add the SLS package to your system using these commands: $ su # uncompress /tmp/ptf7002j.Z # pkgadd -d /tmp/ptf7002j 3. Shut down and reboot the system after installing the SLS package. Note: A system reboot is required following installation of this SLS for the kernel sections to take effect. However, if you have not already installed any other SLS that you need, you should do so before rebooting. Removal Instructions -------------------- 1. As root, remove the SLS package using this command: pkgrm ptf7002 2. Shut down and reboot the system after removing the SLS package. If you have questions regarding this SLS, or the product on which it is installed, please contact your software supplier.