IBM(R) Multipath Subsystem Device Driver Path Control Module (PCM) Version 2.6.0.3 README FOR AIX October 14, 2011 --------------------------------------------------------------------------- CONTENTS 1.0 About this README file 1.1 Who should read this README file 1.2 How to get latest support version information 2.0 Prerequisites for SDDPCM 3.0 SDDPCM change history 3.1 Defects Fixed 3.2 New Features 3.3 Feature Details 4.0 User license agreement for IBM device drivers 4.1 Background / Purpose 4.2 Definitions 4.3 License grant 4.4 Responsibilities 4.5 Confidential information 4.6 Limitation of liability 4.7 Termination 4.8 Representations and warranties 4.9 General provisions 4.10 Appendix A 5.0 Notices 6.0 Trademarks and service marks --------------------------------------------------------------------------- 1.0 About this README file Welcome to IBM Multipath Subsystem Device Driver Path Control Module(SDDPCM). This README file contains the most recent information about the IBM Multipath Subsystem Device Driver PCM, Version 2 Release 6 Modification 0 Level 3 (SDDPCM 2.6.0.3) for AIX. IBM recommends that you print and review the contents of this README file before installing and using SDDPCM on AIX with MPIO-capable disk driver. 1.1 Who should read this README file This README file is intended for storage administrators, system programmers, and performance and capacity analysts. The information in this file only applies to customers who run: 1. DS8000 2. DS6000 3. SAN Volume Controller 4. IBM Storwize V7000 5. ESS 6. DS4000 7. DS5000 8. DS5020 9. DS3950 10. IBM BladeCenter S SAS RAID Controller Module 1.2 How to get latest support version information Go to the following Web site for SDD/SDDPCM technical support and for the most current SDD documentation and support information: http://www.ibm.com/servers/storage/support/software/sdd/ Go to the following SAN Volume Controller web site for latest SDD/SDDPCM support version for SAN Volume Controller: http://www-03.ibm.com/systems/storage/software/virtualization/svc/interop.html Go to the following System Storage Interoperation center(SSIC) web site for latest SDD/SDDPCM support version for all other supported IBM storage subsystems: http://www-03.ibm.com/systems/support/storage/config/ssic/displayesssearchwithoutjs.wss --------------------------------------------------------------------------- 2.0 Prerequisites for SDDPCM Prior to install SDDPCM, you must deinstall fileset "ibm2105.rte"(version of 32.6.100.XX) and "devices.fcp.disk.ibm.rte"(version of 1.0.0.XX) host attachment for SDD driver, along with the SDD package. The SDD driver and SDDPCM module can not coexist on one server. You must install the following host attachment for SDDPCM to support DS4000, DS5000, DS5020 and DS3950 storage devices and a new ESS/SVC/DS6K/DS8K storage device attribute - 'retry_timeout': ESS/DS8000/DS6000/SVC/IBM Storwize V7000/DS4000/DS5000/DS5020/DS3950: devices.fcp.disk.ibm.mpio.rte (version 1.0.0.21) You must install the following host attachment for SDDPCM to support IBM BladeCenter S SAS RAID Controller Module on JS12, JS22, JS23, and JS43 blades. IBM BladeCenter S SAS RAID Controller Module: devices.sas.disk.ibm.mpio.rte(version 1.0.0.0) Following lists of required AIX and VIOS apars and service packs are cumulative. Apars required in earlier versions of SDDPCM packages are also required for later versions of SDDPCM packages, unless specifically noted as 'no longer applicable' or 'not required'. Note: VIOS is not supported with SDDPCM on DS4000/DS5000/DS5020/DS3950 subsystem devices. sddpcm 2.2.0.3 or higher supports ESS/DS8000/DS6000/SVC storage devices. It requires the following AIX and VIOS releases if you are running SVC release v4.2.1.6 and above that supports LONG BUSY function: AIX Level AIX52 TL10-07 AIX53 TL06-09 AIX53 TL07-06 AIX53 TL08-04 AIX61 TL00-07 AIX61 TL01-03 AIX61 TL02-00 VIOS Level 1.5.2.5-FP-11.1 SP-01 and above sddpcm 2.4.0.0 or higher supports ESS/DS8000/DS6000/SVC/DS4000/DS5000 storage devices. It requires the following AIX and VIOS releases: AIX Level AIX53 TL06-10 AIX53 TL07-07 AIX53 TL08-05 AIX53 TL09-00 AIX61 TL00-08 AIX61 TL01-04 AIX61 TL02-00 VIOS Level 1.5.2.5-FP-11.1 SP-01 and above (NOT for DS4000 or DS5000) VIOS Level 2.1.0.10-FP-20.1 and above (NOT for DS4000 or DS5000) Note: VIOS is not supported with SDDPCM on DS4000/DS5000/DS5020/DS3950 subsystem devices. sddpcm 2.4.0.3 or higher supports ESS/DS8000/DS6000/SVC/DS4000/DS5000 storage devices. It requires the following AIX and VIOS releases: AIX Level APAR AIX53 TL08 IZ48395 AIX53 TL09 IZ52471 AIX53 TL10 IZ54856 AIX53 TL11 IZ50064 AIX61 TL00 IZ54857 AIX61 TL01 IZ54858 AIX61 TL02 IZ49639 AIX61 TL03 IZ52470 AIX61 TL04 IZ49804 VIOS Level 1.5.2.5-FP-11.1-SP-01 (NOT for DS4000 or DS5000) VIOS Level 2.1.0.10-FP-20.1 and above (NOT for DS4000 or DS5000) VIOS Level 2.1.1.10-FP-21 and above (NOT for DS4000 or DS5000) sddpcm 2.5.0.0 or higher supports ESS/DS8000/DS6000/SVC/DS4000/DS5000/DS5020 storage devices. It requires the following AIX releases: AIX Level APAR sddpcm 2.5.0.1 or higher supports ESS/DS8000/DS6000/SVC/DS4000/DS5000/DS5020 storage devices. It requires the following AIX disk driver/VIOS release ifix if the storage system is in VIO configuration environment: AIX Level APAR AIX53 TL08 IZ63805 IZ57627 IZ46640 AIX53 TL09 IZ63806 IZ59656 IZ46070 AIX53 TL10 IZ63807 IZ53813 IZ44846 AIX53 TL11 IZ63808 IZ56557 IZ44851 AIX61 TL01 IZ63810 IZ58076 IZ42057 AIX61 TL02 IZ63811 IZ57549 IZ42029 AIX61 TL03 IZ63812 IZ57216 IZ44323 AIX61 TL04 IZ63813 IZ56859 IZ44417 VIOS Level APAR VIOS 1.5.2.5-FP-11 SP-01 IZ61662 (NOT for DS4000/DS5000/DS5020) VIOS 2.1.1.10-FP-21 IZ62591 (NOT for DS4000/DS5000/DS5020) Please check the AIX fix central website for fix availability: http://www-912.ibm.com/eserver/support/fixes/fixcentral/main/pseries/aix For VIO servers: http://www14.software.ibm.com/webapp/set2/sas/f/vios/home.html If not available for download, contact AIX software support to determine eligibility for a temporary fix. sddpcm 2.5.1.0 or higher supports ESS/DS8000/DS6000/SVC/DS4000/DS5000/DS5020/DS3950 storage devices. It requires the following AIX releases and ifix if system has SAN BOOT configuration with DS4000/DS5000/DS5020/DS3950 devices: AIX Level APAR AIX53 TL08-00 IZ66557 AIX53 TL09-06 IZ69197 AIX53 TL10-03 IZ69238 AIX53 TL11-01 IZ59764 AIX53 TL12-01 AIX61 TL03-03 IZ60317 AIX61 TL04-01 IZ59788 AIX61 TL05-01 VIOS Level VIOS 2.1.1.10-FP-22.1 includes above AIX APAR (NOT for DS4000/DS5000/DS5020/DS3950) If you are running AIX53, and you want to configure SANBOOT with DS4000/DS5000/ DS5020/DS3950 devices, please contact IBM AIX software support. Following AIX ifix is required if DS3950 storage devices are configured: AIX Level APAR AIX53 TL10-01 IZ65660 AIX61 TL03-01 IZ65658 The AIX APARs are available from AIX fix central website: http://www-912.ibm.com/eserver/support/fixes/fixcentral/main/pseries/aix Note: Please contact IBM AIX support team for the APARs not listed above in order to support DS4000/DS5000/DS5020/DS3950 devices as SAN BOOT disks. sddpcm 2.6.0.0 or higher support ESS/DS8000/DS6000/SVC/DS4000/DS5000/DS5020/DS3950/ IBM BladeCenter S SAS RAID Controller Module storage devices. It requires the following AIX releases and ifix if system(JS12/J22/JS23/JS43) has IBM BladeCenter S SAS RAID Controller Module devices configured: AIX Level APAR AIX61 TL03-02 IZ68569, IZ62617, IZ68572, IZ70078 AIX61 TL04-01 IZ68571, IZ68574, IZ70079 For VIO servers: sddpcm 2.6.0.0 or higher supports VIO Servers connected to IBM BladeCenter S SAS RAID Controller Module devices. Please contact IBM AIX support team for the appropriate VIOS level --------------------------------------------------------------------------- 3.0 SDDPCM change history =============================================================================== 3.1 Defects Fixed v2.6.0.0 --------- 4722 (AIX defect 736797)Need to synchronize device cfg/uncfg with pcmsrv device interface calls to prevent system crashing. 4723 pcmsrv checking trace buffer interval is reduced from 5 seconds to 1 second to prevent loosing trace data. 4727 smit mpio change path function fails on Active/Active storage devices. v2.6.0.1 --------- 4748 SVC Concurrent Code down load(CCDL) or note reset may fail application in VIOS environment due to the change made in the AIX disk driver for handling check condition sense code from SVC. 4750 Incorrect adapter/port state(FAILED) after CLOSED path being removed 4766 Miss to handle SC_TRANSPORT_FAULT adapter error for non-RSSM devices. 4769 Need to set path to FAILED state if healthchecker command hit TIMEOUT (A/P) 4770 Setting hc_interval/hc_mode for DS4K/DSK devices caused system crash or hanging(A/P) 4772 System hang when controller failover occurred on open device 4781 (PMR40765) Need to retry inquiry command when hit ACA_ACTIVE SCSI error, to avoid path open failure in dual VIOS environment 4782 (PMR33750) System hung when mounting remote FS in GPFS environment with DS4K/5K devices 4833 Newly added path(s) may set to OFFLINE state mistakenly when a new FC HBA is configured v2.6.0.2 --------- 4729 Deinstall SDDPCM package will stop pcmsrv automatically. Stopping pcmsrv prior to SDDPCM deinstallation is not required. 4810 New script commands are provided to start and stop pcmsrv daemon. 4867 Unmatched lock/unlock call caused system crash 4868 (PMR30514) Replacing a controller on DS4K/5K storage subsystem caused system crash 4895 (PMR40765) Need to return EBUSY to delay path open retry calls, allowing the disk driver to have time to clear ACA_ACTIVE condition on the device. 4907 Distinguish device state byte with different FW level, in order to handle LUN unmap scenario correctly. 4908 Fix buffer overrun problem to close TCP/IP security issue when TCP/IP port is enabled. v2.6.0.3 --------- 4850 query port does not display 2 hdisks of disk pair from one machine. 4929 Only fail IO if both prefer and non-prefer paths are unavailable 4930 Adapter state is displayed as Degraded after removing a few paths 4940 Fix buffer overrun in pcmsrv tracing code ========================================================================================== 3.2 New Features 2.4.0.5 --------- 4585 Add a new device attribute - 'retry_timeout', which sets the timeout value for I/O retry on last path. 2.5.0.0 --------- 4546 Add a new command 'lspcmcfg' to display SDDPCM device information 4556 Add DS5020 new device model support 2.5.1.0 --------- 4666 Add DS3950 new device model support 4676 Support DS4000/5000/DS5020/DS3950 devices as SAN BOOT disks and the AIX 'manage_disk_drivers' tool to switch drivers for DS4000/5000/DS5020/DS3950 storage devices configuration. Note: This function requires certain AIX APARs to be installed on the system. APAR information for different AIX OS or TL is listed above under 'Prerequisites for SDDPCM' section. 2.5.2.0 --------- 4713 Support DS4K and DS5K family device controller health check function 4721 Add two new pcmpath commands to allow dynamically change controller health check attributes 2.6.0.0 --------- 4573 Support 'pcmpath query wwpn' command to display SAS adapter WWPN 4717 Support IBM BladeCenter S SAS RAID Controller Module R2.1 GA 4713 Support DS4K and DS5K family device controller health check function 4721 Add two new pcmpath commands to allow dynamically change controller health check attributes 2.6.0.3 --------- 4934 Support DS8800 8 port FC adapter by 'pcmpath query portmap' and 'pcmpath query essmap' commands. =============================================================================== 3.3 Feature/defect Details 4585 Starting from v2.4.0.3, a new device attribute - 'retry_timeout' is added for ESS/DS6K/DS8K/SVC devices. This attribute allows user to set the timeout value for I/O retry on the last path. The default value of this attribute is 120 seconds and it is user-changeable with the valid range of 30 to 600 seconds. pcmpath provides a new CLI command to dynamically change this device retry_timeout attribute. The syntax of this command: pcmpath set device /( ) retry_timeout This feature enables user to adjust the timeout value to control how long SDDPCM will retry the I/O on last path before it fails to the application. In the situation where a device access is lost on all the paths permanently and command fails with TIMEOUT error, which takes rw_timeout time to fail a command. By setting retry_timeout value to default (120 seconds) or smaller value, this feature enables fast path failure and avoids I/O hanging problem under this condition. In the situation where a device loss of access is only temporary, the retry_timeout value may need to be set to a larger value. For example, during certain storage concurrent code download or storage warmstart, it is possible that all the paths to a device may lost access for a short period of time temporarily, such as from a few seconds to a few minutes. Under such situation, I/O should be retried on the last path for an extended period of time to prevent failing the I/O back to application. This will open the window for path recovery from temporary errors. 4713 This feature is for Active/Passive storage devices, which includes DS4K and DS5K family of devices. This controller health check function, when enabled, will be invoked when an enabled path become unavailable due to transport problems. Enabling this feature results in faster I/O failure time when the access to a LUN is lost. The faster failure time is controlled by one of the controller health check attriubte - cntl_delay_time setting. By default, this feature is DISABLED. To enable this feature, user needs to set following two ODM attributes to non-zero value for the active/passive storage devices: cntl_delay_time: is the amount of time in seconds the storage device's controller(s) will be health checked after a transport failure. At the end of this period, if no paths are detected as good, then all pending and subsequent I/O to the device will be failed, until the device health checker detects a failed path has recovered. cntl_hcheck_int: The first controller health check will only be issued after a storage fabric transport failure had been detected. cntl_hcheck_int is the amount of time in seconds, which the next controller health check command will be issued. This value must be less than the cntl_delay_time (unless set to "0", to disable this feature). NOTE: Setting either value to "0" disables this feature. Setting cntl_delay_time to '1' also disables this feature For example, if you wish to allow the storage device within 30 seconds to come back on the fabric(after leaving the fabric), then you can set cntl_delay_time=30 and cntl_hcheck_int=2. The device, /dev/hdisk#, must not be in use, when setting the ODM values with 'chdev' command(or the chdev "-P" option must be used, which requires a reboot to make the change to take effect). CAUTION: There are cases where the storage device may reboot both of the controllers and become inaccessible for a period of time. If the controller health check feature is enabled, and 'cntl_delay_time' is set too short, then this may result in an I/O failure. It is recommended to make sure you have an mirrored volume to failover to, or with GPFS configuration if you are running with controller health check enabled and cntl_delay_time setting is under 60 seconds, or is not long enough to cover the temporary device inaccessible conditions, which may occur during the storage concurrent code load operation or other error injection operations. 4721 This feature allows user to change both controller health check ODM attributes dynamically (using 'chdev' command requires unconfigure/reconfigure device). pcmpath set device cntlhc_interval The pcmpath set device cntlhc_interval command dynamically changes the Active/Passive MPIO device controller health check time interval or disables this feature. Syntax pcmpath set device [num2] cntlhc_interval Parameters num1 [ num2 ] * When only num1 is specified, then the command applies to the hdisk specified by num1. * When 2 device logical numbers are entered, this command applies to all the Active/Passive devices whose logical numbers fit within the range of the two device logical numbers. t The range of supported values for controller health check time interval is 0-300 seconds. Setting the value to 0 will disable this feature. Examples If you enter pcmpath set device 2 10 cntlhc_interval 3, the controller health check time interval of hdisk2 to hdisk10 is immediately changed to 3 seconds, if hdisk2 to hdisk10 are all Active/Passive devices. pcmpath set device cntlhc_delay The pcmpath set device cntlhc_delay command dynamically changes the Active/Passive MPIO device controller health check delay time or disables this feature. Syntax pcmpath set device [num2] cntlhc_delay Parameters num1 [ num2 ] * When only num1 is specified, then the command applies to the hdisk specified by num1. * When 2 device logical numbers are entered, this command applies to all the Active/Passive devices whose logical numbers fit within the range of the two device logical numbers. t The range of supported values for controller health check delay time is 0-300 seconds. Setting the value to 0 will disable this feature. Examples If you enter pcmpath set device 2 10 cntlhc_delay 30, the controller health check delay time of hdisk2 to hdisk10 is immediately chnaged to 30 seconds, if hdisk2 to hdisk10 are all Active/Passive devices. Note: If cntl_delay_time is set to '1', this will disable the controller health check feature, just like set it to '0'. If user tries to set cntl_hcheck_int with a value larger than cntl_delay_time, then cntl_hcheck_int will be set to the same value as cntl_delay_time. If user tries to set cntl_delay_time with a value smaller than cntl_hcheck_int, the command will fail with INVALID parameter. 4810 Due to supporting pcmsrv respawning function, "startsrc -s pcmsrv" and "stopsrc -s pcmsrv" should not be used for starting and stopping pcmsrv because pcmsrv will keep respawning. Two new scripts which prevent pcmsrv from respawning are provided to start and stop pcmsrv. "startpcmsrv" will start pcmsrv daemon and "stoppcmsrv" will stop pcmsrv daemon. e.g. To start pcmsrv, issue "startpcmsrv" on system command prompt #startpcmsrv To stop pcmsrv, issue "stoppcmsrv" on system command prompt #stoppcmsrv 4908 Fix sddsrv buffer overrun problem to close TCP/IP security issue Fix potential security problem due to buffer overrun problem in sddsrv when TCP/IP port is enabled. This defect only impact customers who has enabled TCP/IP port. TCP/IP port is disabled by default. 4934 Support DS8800 8 port FC adapter by 'pcmpath query portmap' and 'pcmpath query essmap' commands. The output is changed in order to display 8 ports per adapter. Example of 'pcmpath query portmap' display: BAY-X BAY-Y ESSID DISK H1 H2 H3 H4 H1 H2 H3 H4 ABCDEFGH ABCDEFGH ABCDEFGH ABCDEFGH ABCDEFGH ABCDEFGH ABCDEFGH ABCDEFGH 75TL811 hdisk1 Bay3-Bay4: -------- -------- Y-Y----- -------- Y-Y----- -------- -------- -------- 75TL811 hdisk2 Bay3-Bay4: -------- -------- Y-Y----- -------- Y-Y----- -------- -------- -------- 75TL811 hdisk3 Bay3-Bay4: -------- -------- O-O----- -------- O-O----- -------- -------- -------- 75TL811 hdisk4 Bay3-Bay4: -------- -------- O-O----- -------- O-O----- -------- -------- -------- 75TL811 hdisk5 Bay3-Bay4: -------- -------- O-O----- -------- O-O----- -------- -------- -------- 75TL811 hdisk6 Bay3-Bay4: -------- -------- O-O----- -------- O-O----- -------- -------- -------- 75TL811 hdisk7 Bay3-Bay4: -------- -------- O-O----- -------- O-O----- -------- -------- -------- 75TL811 hdisk8 Bay3-Bay4: -------- -------- O-O----- -------- O-O----- -------- -------- -------- Y = online/open y = (alternate path) online/open O = online/closed o = (alternate path) online/closed N = offline n = (alternate path) offline - = path not configured ? = path information not available PD = path down Note: 2105 devices' essid has 5 digits, while 1750/2107 device's essid has 7 digits. Example of 'pcmpath query essmap' display: Disk Path P Location adapter LUN SN Type Size LSS Vol Rank C/A S Connection port RaidMode ------- ----- - ---------- -------- -------- ------------ ---- --- --- ---- --- - ----------- ---- -------- hdisk1 path0 03-00-01[FC] fscsi0 75TL811010D IBM 2107-900 1.0GB 1 13 0001 17 Y R1-B3-H3-ZA 230 RAID5 hdisk1 path1 03-00-01[FC] fscsi0 75TL811010D IBM 2107-900 1.0GB 1 13 0001 17 Y R1-B4-H1-ZA 300 RAID5 hdisk1 path2 03-01-01[FC] fscsi1 75TL811010D IBM 2107-900 1.0GB 1 13 0001 17 Y R1-B4-H1-ZC 302 RAID5 hdisk1 path3 03-01-01[FC] fscsi1 75TL811010D IBM 2107-900 1.0GB 1 13 0001 17 Y R1-B3-H3-ZC 232 RAID5 hdisk2 path0 03-00-01[FC] fscsi0 75TL811010E IBM 2107-900 1.0GB 1 14 0001 17 Y R1-B3-H3-ZA 230 RAID5 hdisk2 path1 03-00-01[FC] fscsi0 75TL811010E IBM 2107-900 1.0GB 1 14 0001 17 Y R1-B4-H1-ZA 300 RAID5 hdisk2 path2 03-01-01[FC] fscsi1 75TL811010E IBM 2107-900 1.0GB 1 14 0001 17 Y R1-B4-H1-ZC 302 RAID5 hdisk2 path3 03-01-01[FC] fscsi1 75TL811010E IBM 2107-900 1.0GB 1 14 0001 17 Y R1-B3-H3-ZC 232 RAID5 hdisk3 path0 03-00-01[FC] fscsi0 75TL811010F IBM 2107-900 1.0GB 1 15 0001 17 Y R1-B3-H3-ZA 230 RAID5 hdisk3 path1 03-00-01[FC] fscsi0 75TL811010F IBM 2107-900 1.0GB 1 15 0001 17 Y R1-B4-H1-ZA 300 RAID5 hdisk3 path2 03-01-01[FC] fscsi1 75TL811010F IBM 2107-900 1.0GB 1 15 0001 17 Y R1-B4-H1-ZC 302 RAID5 hdisk3 path3 03-01-01[FC] fscsi1 75TL811010F IBM 2107-900 1.0GB 1 15 0001 17 Y R1-B3-H3-ZC 232 RAID5 hdisk4 path0 03-00-01[FC] fscsi0 75TL8110113 IBM 2107-900 1.0GB 1 19 0001 17 Y R1-B3-H3-ZA 230 RAID5 hdisk4 path1 03-00-01[FC] fscsi0 75TL8110113 IBM 2107-900 1.0GB 1 19 0001 17 Y R1-B4-H1-ZA 300 RAID5 hdisk4 path2 03-01-01[FC] fscsi1 75TL8110113 IBM 2107-900 1.0GB 1 19 0001 17 Y R1-B4-H1-ZC 302 RAID5 hdisk4 path3 03-01-01[FC] fscsi1 75TL8110113 IBM 2107-900 1.0GB 1 19 0001 17 Y R1-B3-H3-ZC 232 RAID5 hdisk5 path0 03-00-01[FC] fscsi0 75TL8110114 IBM 2107-900 1.0GB 1 20 0001 17 Y R1-B3-H3-ZA 230 RAID5 hdisk5 path1 03-00-01[FC] fscsi0 75TL8110114 IBM 2107-900 1.0GB 1 20 0001 17 Y R1-B4-H1-ZA 300 RAID5 hdisk5 path2 03-01-01[FC] fscsi1 75TL8110114 IBM 2107-900 1.0GB 1 20 0001 17 Y R1-B4-H1-ZC 302 RAID5 hdisk5 path3 03-01-01[FC] fscsi1 75TL8110114 IBM 2107-900 1.0GB 1 20 0001 17 Y R1-B3-H3-ZC 232 RAID5 hdisk6 path0 03-00-01[FC] fscsi0 75TL8110115 IBM 2107-900 1.0GB 1 21 0001 17 Y R1-B3-H3-ZA 230 RAID5 hdisk6 path1 03-00-01[FC] fscsi0 75TL8110115 IBM 2107-900 1.0GB 1 21 0001 17 Y R1-B4-H1-ZA 300 RAID5 hdisk6 path2 03-01-01[FC] fscsi1 75TL8110115 IBM 2107-900 1.0GB 1 21 0001 17 Y R1-B4-H1-ZC 302 RAID5 hdisk6 path3 03-01-01[FC] fscsi1 75TL8110115 IBM 2107-900 1.0GB 1 21 0001 17 Y R1-B3-H3-ZC 232 RAID5 ====================================================================================== 3.4 Known issues SDDPCM supports 'pcmpath set adapter online|offline aa|ap' command. For FC adapter connected to DS4000/DS5000/DS5020/DS3950 active/passive storage devices, you should use 'ap' parameter to indicate this is an adapter connected to DS4000/ DS5000/DS5020/DS3950 storage devices. If an adapter is connected to other storage devices, then you should use 'aa' parameter. Since set an adapter OFFLINE may cause DS4000, and/or DS5000, and/or DS5020, and/or DS3950 LUNs fail over to an alternate controller, this command is only supported when the AIX server has one DS4000, or DS5000, or DS5020, or DS3950 storage subsystem configured. This command may not work correctly if you have more than one storage subsystem device models configured on an AIX server, and 'set adapter offline ap' command may cause multiple subsystems migrating from one controller to an alternate controller. Please refer to SDD User's Guide, chapter 3 for detail information of this command. VIOS is not supported with SDDPCM on DS4000/DS5000/DS5020/DS3950 subsystem devices. If user removes host FC HBA port from DS4000, DS5000, DS5020, or DS3950 storage subsystem while application is running, this will cause I/O performance degradation. The correct procedures are: 1. identify the host FC HBA you plan to remove from DS4000, DS5000, DS5020, or DS3950 storage subsystem. 2. issue 'pcmpath set adapter X offline ap' or issue 'pcmpath set device M path N offline' command to set all the paths that connected to this FC HBA you plan to remove offline. 3. from the DS4000 or DS5000 storage subsystem to remove the FC HBA port. 4. if removing this host FC HBA port is a permanent configuration change, make sure you remove this configuration on the host side by issuing either remove adapter or remove path command. ================================================================================== 3.5 Corrections to User's Guide User's Guide 1.8-2.4* version, on page 134, under "3. To query and display which type of persistent reservation is on a device, enter pcmquerypr -Vh /dev/hdisk#.", a note should be added: Note: Since SVC LUN returns Good status for SCSI-3 persistent reserve commands, even SCSI-2 reserve presents on the LUN, therefore, pcmquerypr command can not be used to verify if SCSI-2 reserve presents on the SVC LUN or not. User's Guide 1.8-2.4* version, on page 123, and 1.8-2.4 User Guide Errata, on page 33, under "Removing SDDPCM from an AIX host system", sentence of "SDDPCM server daemon(pcmsrv) is stopped," should be removed from this paragraph. Starting from SDDPCM version 2.6.0.2 and above, SDDPCM deinstall procedure will stop the SDDPCM server daemon automatically. User's Guide 1.8-2.4*, 1.8-2.6* and 1.8-3.0 versions, on page 102, and 1.8-2.4 User Guide Errata, on page 14, under "Unsupported environments", sentence of "Mirror write Consistency with volume group in a concurrent resource group" should be "HACMP with Mirror Write Consistency with volume group in concurrent resource group". User's Guide 1.8-3.0 version, on page 1 and 2, under Chapter 1. Overview of the SDD, need to add followings lines to claim support IBM Storwize V7000 virtualization product: . IBM Storwize V7000 _ IBM Storwize V7000 User's Guide 1.8-3.0 version, on page 1 and 2, Table 1. 'SDD platforms that are supported by supported storage devices' should add addition colume for "IBM Storwize V7000", and supported by AIX SDDPCM, Window 2003 and Window 2008 SDDDSM. User's Guide 1.8-3.0 version, on page 101, under "Supported SDDPCM feagures", 'Support for all...." should be change to ". Support for all DS4000, DS5000, DS3900, DS6000. DS8000, ESS FCP, SAN Volume Controller, and IBM Storwize V7000 devices". --------------------------------------------------------------------------- 4.0 User license agreement for IBM device drivers NOTICE: PLEASE READ THIS AGREEMENT CAREFULLY BEFORE USING THE PROGRAM AND DOCUMENTATION. IBM(R) WILL ONLY LICENSE THIS PROGRAM AND DOCUMENTATION TO YOU IF YOU FIRST ACCEPT THE TERMS OF THIS AGREEMENT. BY USING THE PROGRAM AND DOCUMENTATION, YOU AGREE TO ABIDE BY THESE TERMS AND APPLICABLE COPYRIGHT LAWS. IBM LIMITS YOUR ACCEPTANCE OF THE PROGRAM AND DOCUMENTATION TO THE TERMS OF THIS AGREEMENT. The Program and Documentation is owned by International Business Machines Corporation or one of its subsidiaries (IBM) or IBM suppliers, and is copyrighted and licensed, not sold. IBM does not transfer title to this Program and Documentation to you. The terms of this Agreement apply to any additional license copy of the Program or Documentation that IBM authorizes you to make. The term "Program" means the original program and all whole or partial copies of it, including portions merged with other programs. A Program consists of machine-readable instructions and related license materials. Under this Agreement, IBM provides you with a license to use the Program and Documentation only. 4.1 Background/Purpose IBM provides certain device drivers and Documentation under this Agreement. The device drivers and library support that IBM provides under this Agreement are in object code form only. Appendix A of this Agreement indicates the server platforms that are supported. IBM uses announcements to withdraw service for device drivers, feature codes, etc., on hardware and/or operating system platforms. IBM reserves the right to change the Programs or Documentation at any time without prior notice. 4.2 Definitions Derivative Work is a work based on a preexisting work, including a compilation. A Derivative Work prepared without the authorization of the copyright owner of the preexisting work would constitute a copyright infringement. Documentation is the Program documentation that IBM provides to you as follows: IBM Subsystem Device Driver and README files. Object Code is machine-readable instructions in Object Code format. It is substantially in binary form and directly executable by a computer after suitable processing but without the intervening steps of compilation or assembly. Program is the IBM Subsystem Device Driver in Object Code form. 4.3 License grant IBM grants you a revocable, nontransferable, nonexclusive, worldwide, paid-up copyright license to: 1. Use the Program and Documentation solely on the platforms and with the applicable IBM devices described in Appendix A of this Agreement. 2. Maintain one copy of the Program for backup purposes only. Your license to the Programs and Documentation terminates when you no longer rightfully possess the IBM device described in Appendix A. This Agreement does not grant you any right or license to prepare Derivative Works of the Program and Documentation. Nothing in this Agreement grants either party any rights or licenses under any patents or patent applications regardless of whether use and/or execution of the software licensed herein may be construed to practice one or more patents. 4.4 Responsibilities You agree to use the Program and Documentation only with the IBM device described in Appendix A of this Agreement. You will not: 1. otherwise copy, display, transfer, adopt, modify or distribute in any form, the Program and Documentation, except as IBM expressly authorizes in the Documentation 2. decompile, disassemble, reverse engineer, or in any way modify the Program or Documentation 3. sell, rent, lease, sublicense the Program or Documentation, unless explicitly permitted by law without the possibility of contractual waiver; and sublicense or assign the license for the Program and Documentation 4.5 Confidential information Any information which either party may disclose to the other party shall not be deemed to be confidential. If the parties require the exchange of confidential information, such exchange will be made under a separate written confidentiality agreement. 4.6 Limitation of liability IN NO EVENT SHALL IBM OR ITS SUPPLIERS BE LIABLE FOR COSTS OF PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES, LOSS OF DATA, LOST PROFITS, BUSINESS INTERRUPTION OR ANY SPECIAL, INCIDENTAL, INDIRECT, CONSEQUENTIAL, PUNITIVE OR EXEMPLARY DAMAGES , EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES AND NOTWITHSTANDING THE FAILURE OF ESSENTIAL PURPOSE OF ANY REMEDY. You acknowledge that circumstances may arise where, because of a default on IBM's part or other liability, you may be entitled to recover damages. Under any such circumstances, you agree that in each such instance, regardless of the basis on which you are entitled to claim damages, IBM shall be liable only up to an amount equal to five thousand U.S. dollars ($5,000). This limitation will not apply to claims relating to bodily injury (including death), and damage to real property and personal property. 4.7 Termination Termination for Cause. If either party fails to perform its obligations hereunder, then the other party may terminate this Agreement or the license granted hereunder for cause. Effect of Termination. The rights and licenses granted to you under this Agreement shall automatically terminate upon the termination of this Agreement. 4.8 Representations and warranties THE PROGRAM AND DOCUMENTATION IS PROVIDED ON AN "AS IS" BASIS. IBM MAKES NO REPRESENTATION OR WARRANTY, EXPRESS OR IMPLIED, WITH RESPECT TO THE PROGRAM AND DOCUMENTATION.IBM DISCLAIMS THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. THE ENTIRE RISK ARISING OUT OF THE USE OR PERFORMANCE OF THE PROGRAM AND DOCUMENTATION REMAINS WITH YOU. 4.9 General Provisions Transfer. You may transfer possession of the program and its media and Documentation to another pay with the transfer of the IBM device described in Appendix A on which such Program is used with. If you do so, you must give the other party a copy of these terms and provide all user documentation to that party, and such party must first agree to such terms before it uses the Program and Documentation. Upon transfer of the Program and Documentation, you must destroy all your copies of the Program and Documentation. Severability. If any provision of this Agreement is found to be illegal or unenforceable, the remainder of this Agreement shall continue in full force and effect provided that the Agreement still effectuates the parties' original intent. Governing Law and Jury Trial Waiver. This Agreement shall be governed by the laws of the State of New York, excluding its conflict of law rules. Each party hereby agrees to waive its rights to a trial by jury. Modifications. No modification to this Agreement, nor any waiver of any rights, shall be effective unless agreed to in a writing that is executed by both parties, and the waiver of any breach or default of this Agreement shall not constitute a waiver of any other right or of any subsequent breach or default. Limitations on Legal Actions. Neither party will bring a legal action against the other more than two (2) years after the cause of action arose. Both parties will act in good faith to resolve disputes. Order of Precedence. In the event of a conflict in terms between this Agreement and another agreement, the terms of this Agreement shall take precedence and prevail over such other terms. Entire Agreement. This Agreement constitutes the entire and exclusive agreement between the parties with respect to this subject matter. All previous discussions and agreements with respect to this subject matter are superseded by this Agreement. 4.10 Appendix A This Appendix indicates: 1. Which specific IBM devices the Program and Documentation are to be used with: IBM devices: IBM Enterprise Storage Server (ESS) IBM devices: IBM TotalStorage DS8000 IBM devices: IBM TotalStorage DS6000 IBM devices: IBM System Storage SAN Volume Controller 2. For what specific server platforms the Program and Documentation are to be used and for what software requirements apply to the use of the Program and Documentation, refer to the following websites: - IBM Enterprise Storage Server (ESS) support: www.storage.ibm.com/hardsoft/products/ess/supserver.htm - IBM TotalStorage DS8000 www.ibm.com/servers/storage/disk/ds8000/index.html - IBM TotalStorage DS6000 www.ibm.com/servers/storage/disk/ds6000/index.html - IBM System Storage SAN Volume Controller support www.ibm.com/storage/support/2145 CONTINUING WITH THIS INSTALLATION CONSTITUTES YOUR ACCEPTANCE OF THE TERMS OF THE ABOVE 'USER LICENSE AGREEMENT FOR IBM DEVICE DRIVERS' ------------------------------------------------------------------------------- 5.0 Notices This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services,or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries,in writing, to: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo 106, Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND,EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation Information Enabling Requests Dept. DZWA 5600 Cottle Road San Jose, CA 95193 U.S.A. Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM License Agreement for Non-Warranted Programs. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurement may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. =============================================================================== IBM agreement for licensed internal code +---- Read Before Using -----------------------------------------------+ |IMPORTANT | | | |YOU ACCEPT THE TERMS OF THIS IBM LICENSE AGREEMENT FOR MACHINE CODE BY| |YOUR USE OF THE HARDWARE PRODUCT OR MACHINE CODE. PLEASE READ THE | |AGREEMENT CONTAINED IN THIS BOOK BEFORE USING THE HARDWARE PRODUCT.SEE| |IBM agreement for licensed internal code. | | | +----------------------------------------------------------------------+ You accept the terms of this Agreement(3) by your initial use of a machine that contains IBM Licensed Internal Code (called "Code"). These terms apply to Code used by certain machines IBM or your reseller specifies (called "Specific Machines"). International Business Machines Corporation or one of its subsidiaries ("IBM") owns copyrights in Code or has the right to license Code. IBM or a third party owns all copies of Code, including all copies made from them. If you are the rightful possessor of a Specific Machine, IBM grants you a license to use the Code (or any replacement IBM provides) on, or in conjunction with, only the Specific Machine for which the Code is provided. IBM licenses the Code to only one rightful possessor at a time. Under each license, IBM authorizes you to do only the following: 1. execute the Code to enable the Specific Machine to function according to its Official Published Specifications (called "Specifications"); 2. make a backup or archival copy of the Code (unless IBM makes one available for your use), provided you reproduce the copyright notice and any other legend of ownership on the copy. You may use the copy only to replace the original, when necessary; and 3. execute and display the Code as necessary to maintain the Specific Machine. You agree to acquire any replacement for, or additional copy of, Code directly from IBM in accordance with IBM's standard policies and practices. You also agree to use that Code under these terms. You may transfer possession of the Code to another party only with the transfer of the Specific Machine. If you do so, you must 1) destroy all your copies of the Code that were not provided by IBM, 2) either give the other party all your IBM-provided copies of the Code or destroy them, and 3) notify the other party of these terms. IBM licenses the other party when it accepts these terms. These terms apply to all Code you acquire from any source. Your license terminates when you no longer rightfully possess the Specific Machine. Actions you must not take You agree to use the Code only as authorized above. You must not do, for example, any of the following: 1. Otherwise copy, display, transfer, adapt, modify, or distribute the Code (electronically or otherwise), except as IBM may authorize in the Specific Machine's Specifications or in writing to you; 2. Reverse assemble, reverse compile, or otherwise translate the Code unless expressly permitted by applicable law without the possibility of contractual waiver; 3. Sublicense or assign the license for the Code; or 4. Lease the Code or any copy of it. ------------------------------------------------------------------------------- 6.0 Trademarks and service marks The following terms are trademarks of the International Business Machines Corporation in the United States,other countries, or both: AIX AS/400 Enterprise Storage Server HACMP/6000 IBM IBM logo iSeries Netfinity NetVista Operating System/400 pSeries RS/6000 Seascape SP System/360 System/370 System/390 The eServer logo TotalStorage Versatile Storage Server xSeries zSeries z/Architecture z/OS Microsoft, Windows, Windows NT, and the Windows logo are registered trademarks of Microsoft Corporation. Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Other company, product, and service names may be trademarks or service marks of others. ------------------------------------------------------------------------------- (C) Copyright IBM Corporation 2000, 2002, 2003, 2004. All rights reserved.