@(#) HTC_MPIO_ODM_5404U(devices.fcp.disk.Hitachi.array.mpio.rte) @(#) Ver. 5.4.1.1 This readme includes explanation of the following fileset (1)HTC_MPIO_ODM(devices.fcp.disk.Hitachi.array.mpio.rte) This fileset is for using default MPIO functionality on AIX 5L V5.2 and ML03 or later for RAID400/RAID450/RAID500(USP)/RAID600(USP V)/RAID700(VSP)/HM700(HUS VM)/RAID800(VSP G1000)/HM800(VSP Gx00) product [Note] In order to install the above filesets on Virtual I/O server with AIX 5.3 or later , oem_setup_env command is necessary to be executed. Please refer to IBM docume nt about oem_setup_env usage. HTC_MPIO_ODM history Rev 1: 5400I(04/08) First release Rev 2: 5401U(05/09) Auto Failback Support Rev 3: 5402U(07/09) Distinguish USP/NSC and USP V/USP VM Rev 4: 5402(1)(07/12) Correction of readme(incorrect APAR number) Rev 5: 5402(2)(09/03) SANBoot info is included and OS/HBA info is updated Rev 6: 5403 (10/06) Support RAID700(VSP) Rev 7: 5404 (11/06) timeout_policy attribute Support Rev 8: 5405 (12/05) Support HM700 Rev 9: 5405(1)(12/06) Support HM700(HUS VM) and correction of readme Rev 10: 5410 (13/09) Support RAID800(VSP G1000) Rev 11: 5411 (15/02) Support HM800 (VSP Gx00) ############## Welcome to HTC_MPIO_ODM_5411U package ######### # # # Software Attached Document # # # # Ver. 5.4.1.1 # # # # Copyright (C) 2004, 2015 Hitachi,Ltd. All rights reserved # ############################################################### HTC_MPIO_ODM(devices.fcp.disk.Hitachi.array.mpio.rte) 1. Introduction This attached document describes the contents by the following supported program products. HTC_MPIO_ODM package (fileset name is devices.fcp.disk.Hitachi.array.mpio.rte) HTC_MPIO_ODM package consists of the following 8 packages (a)HTC_MPIO_ODM_5400I devices.fcp.disk.Hitachi.array.mpio.rte 5.4.0.0 AIX MPIO Support for Hitachi Disk Arrays(New Install) (b)HTC_MPIO_ODM_5401U devices.fcp.disk.Hitachi.array.mpio.rte 5.4.0.1 AIX MPIO Support for Hitachi Disk Arrays(New Update) (c)HTC_MPIO_ODM_5402U devices.fcp.disk.Hitachi.array.mpio.rte 5.4.0.2 AIX MPIO Support for Hitachi Disk Arrays(New Update) (d)HTC_MPIO_ODM_5403U devices.fcp.disk.Hitachi.array.mpio.rte 5.4.0.3 AIX MPIO Support for Hitachi Disk Arrays(New Update) (e)HTC_MPIO_ODM_5404U devices.fcp.disk.Hitachi.array.mpio.rte 5.4.0.4 AIX MPIO Support for Hitachi Disk Arrays(New Update) (f)HTC_MPIO_ODM_5405U devices.fcp.disk.Hitachi.array.mpio.rte 5.4.0.5 AIX MPIO Support for Hitachi Disk Arrays(New Update) (g)HTC_MPIO_ODM_5410U devices.fcp.disk.Hitachi.array.mpio.rte 5.4.1.0 AIX MPIO Support for Hitachi Disk Arrays(New Update) (h)HTC_MPIO_ODM_5411U devices.fcp.disk.Hitachi.array.mpio.rte 5.4.1.1 AIX MPIO Support for Hitachi Disk Arrays(New Update) In order for Default PCM(MPIO) functionality to work with the Hitachi Disk Array, the HTC_MPIO_ODM needs to be installed on AIX machine before recognizing the devices. HTC_MPIO_ODM has the following functionality to add its own device definitions for Hitachi and set the proper attributes to AIX ODM like PdDv(a predefined set of devices), PdAt(a predefined set of attributes), PdPathAt, andPdAtXtd that IBM provide to recognize Hitachi disk device as MPIO(Default PCM). # This odm supports Hitachi devices with dynamic tracking and MPIO # This should only be given to customers running AIX 5.2(ML03) or greater # who want to utilize AIX dynamic tracking and AIX MPIO 2. Prerequisite operating system and Applying machine type. (1) Operating System - AIX 5.2 ML03 or later(IY49013)+APARs IY56769 and IY58170 on the AIX Pseries or RS6000 Server - APAR IY49823(For FC6239) devices.fcp.disk.rte 5.2.0.40 or later devices.common.IBM.mpio.rte 5.2.0.31 or later - AIX 5.2 ML04 or later(For FC5716) For MPIO_ODM_5401 or later, the following APAR is necessary. - AIX 5.2 ML06 or later or APAR IY67465 on the AIX Pseries or RS6000 Server - AIX 5.3 ML02 or later or APAR IY67625 on the AIX Pseries or RS6000 Server - AIX 6.1 or later on the AIX Pseries or RS6000 Server devices.common.IBM.mpio.rte.5.2.0.60 or later devices.common.IBM.mpio.rte.5.3.0.20 or later devices.common.IBM.mpio.rte.6.1.0.00 or later [How to confirm] (a) The result of "oslevel -r" is 5200-03 or later (b) The result of "lslpp -l devices.common.IBM.mpio.rte" is 5.2.0.31 or later (2)HBA - FC6227/FC6228/FC6239/FC5716/FC5758/FC5759/FC1910/FC1905/FC1957/FC1977/FC5773/FC5774/FC5735/EN0A/EN0B (IBM branded HBA) (3)Microcode for the RAID(Evaluated) - RAID400: 01-19-62-00/00 or later - RAID450: 21-06-37-00/00-01 or later - RAID500(USP): 50-01-19-00 or higher - RAID500(NSC): 50-03-93-00 or higher - RAID600(USP V): 60-01-3x-00 or higher - RAID600(USP VM): 60-01-68-00 or higher - RAID700(VSP ): 70-01-xx-00 or higher - HM700 (HUS VM): 73-01-xx-00 or higher - RAID800(VSP G1000): 80-01-xx-00 or higher - HM800 (VSP G1000): 83-01-xx-00 or higher 3. Installation on the AIX System < Installation > (1) Log-in as superuser (2) Mount the CD-ROM or copy HTCMPIO6.tar to an AIX server (3) Copy HTCMPIO7.tar into AIX directly(ex. /usr/sys/inst.images): # cp HTCMPIO7.tar /usr/sys/inst.images (4) Extract HTCMPIO7.tar # tar xvf HTCMPIO7.tar (5) Eight of HTC_MPIO_ODM packages(HTC_MPIO_ODM_5400I and HTC_MPIO_ODM_5401U and HTC_MPIO_ODM_5402U and HTC_MPIO_ODM_5403U and HTC_MPIO_ODM_5404U and HTC_MPIO_ODM_5405U and HTC_MPIO_ODM_5410U and HTC_MPIO_ODM_5411U) are created (6) Create a new .toc file # cd /usr/sys/inst.images # inutoc . (7) Use installp to install the AIX support fileset: # smitty install (8) Select Install and Update Software. (9) Select Install and Update from LATEST Available Software. (10) You will be prompted for an input device. Enter the directory where the fileset was copied. (11) Select F4 to list the available installation packages. (12) Select F7 to select "5.4.0.0 AIX MPIO Support for Hitachi Disk Arrays(New Install)" and "5.4.0.1 AIX MPIO Support for Hitachi Disk Arrays(Update)" and "5.4.0.2 AIX MPIO Support for Hitachi Disk Arrays(Update)" and "5.4.0.3 AIX MPIO Support for Hitachi Disk Arrays(Update)" and "5.4.0.4 AIX MPIO Support for Hitachi Disk Arrays(Update)" and "5.4.0.5 AIX MPIO Support for Hitachi Disk Arrays(Update)" and "5.4.1.0 AIX MPIO Support for Hitachi Disk Arrays(Update)" and "5.4.1.1 AIX MPIO Support for Hitachi Disk Arrays(Update)", then select Enter (13) Select Enter to start the installation process Fileset name : devices.fcp.disk.Hitachi.array.mpio.rte (14) If necessary, remove any Hitachi devices already defined as MPIO Other FC SCSI disk drive. - To remove one device: # rmdev -dl hdisk(n) - To remove all devices on a path: # rmdev -dl fscsi(n) -R (15) Confirm whether installation has completed successfully. (16) Reboot AIX. (17) Confirm that the parameters have the following values: # lsattr -E -l hdisk(n) PCM PCM/friend/Hitachi algorithm fail_over hcheck_cmd inquiry (when HTC_MPIO_ODM 5401U is installed) hcheck_interval 60 hcheck_mode nonactive pvid *** queue_depth 2 q_type simple q_err yes clr_q no rw_timeout 60 start_timeout 60 reassign_timeout 120 # lsdev -Cc disk hdisk0 Available 1S-08-00-8,0 16 Bit LVD SCSI Disk Drive hdisk1 Available 1H-08-01 Hitachi MPIO Disk USP (Fibre) hdisk2 Available 1Z-08-01 Hitachi MPIO Disk USP V (Fibre) [Note] In order to disable Auto Failback functionality, hcheck_interval is changed to 0. The hcheck_interval parameter can be changed by: Unmounting filesystems Varying off the volume groups chdev -l hdiskx -a hcheck_interval=0 [Note] When MPIO and HACMP is configured with Hitachi Disk, the following setting is necessary. (A)Volume Groups configured as Enhanced Concurrent (B)Allow chdev command to be issued to change algorithm from "fail_over" to "round_robin", reserve_policy from "single_path" to "no_reserve" Allow loadbalancing chdev -l hdiskx -a algorithm=round_robin -a reserve_policy=no_reserve [Note] The default IBM rw timeout and queue depth value are different from the recommended values for Hitachi devices. The IBM default values are queue_depth=1 and rw timeout=60. The Hitachi default values are queue_depth=2 and rw timeout=60. Contact HDS for more information on the recommended queue depth value. [Note] In order to support timeout_policy attribute, filesets including timeout_policy attribute need to be installed on the AIX server. Confirm whether each LU is configured with several paths(device or path status) using following command. # lspath Enabled hdisk0 scsi0 Enabled hdisk1 fscsi0 Enabled hdisk2 fscsi0 Enabled hdisk3 fscsi0 Enabled hdisk4 fscsi0 Enabled hdisk1 fscsi2 Enabled hdisk2 fscsi2 Enabled hdisk3 fscsi2 Enabled hdisk4 fscsi2 < Uninstallation > (1) Remove all Hitachi LUNs from the system using the rmdev command: - To remove one device: # rmdev -dl hdisk(n) - To remove all devices on a path: # rmdev -dl fscsi(n) -R [Note] The deinstall will fail if Hitachi devices (hdisks) are not removed first. (2) Enter smitty install from command line. (3) Select Software Maintenance and Utilities. (4) Select Remove Installed Software. (5) Select F4 for SOFTWARE name to list all installed software. (6) Select (/) for Hitachi devices.fcp.disk.Hitachi.array.mpio.rte (7) Select the package to remove pressing F7 and then Enter (8) Use either the Tab key or F4 to change PREVIEW only to No. (9) Select Enter to confirm the warning message. (10) Confirm OK whether the fileset is deleted correctly (11) Reboot AIX. (12) hdisk(n) is recognized as "MPIO Other FC SCSI Disk Drive" [Note] Alternative method to uninstall MPIO after removing hdisk devices: installp -u devices.fcp.disk.Hitachi.array.mpio.rte Reboot AIX System. [Caution] (1) devices.fcp.disk.Hitachi.array.mpio.rte can not be installed on the machine with Hitachi.aix.support.rte installed. (2) When sharing ports on the Hitachi Disk Array with multiple AIX servers, the same level of the HTC ODM is required. [Note] There are various possible implemenations of SAN boot with AIX. (1) To implement SAN boot on a system with an already installed AIX operating system, you can: a. Use the alt_disk_install system utility. b. Do this by mirroring of the rootvg volume to the SAN disk. (2)To implement SAN boot for a new system, you can: a. Start the AIX installation from a bootable AIX CD install package. b. Or, use the Network Installation Manager (NIM). The methods known as Alt_disk_install or mirroring are simpler