AIX MPIO、RDAC、SDDPCM多路径软件操作
AIX系统操作手册
AIX系统操作手册系统操作手册系统操作手册武汉金力软件有限公司 WUHAN JINLI SOFTWARE CO., LTD版本：5LIAIX目录第一章 AIX操作系统的安装 ........................................................................... (5)安装介质与方式 ........................................................................... . (5)BOS（Base Operating System）安装 ........................................................................... (5)第二章 AIX操作系统基本命 ........................................................................... (8)? 系统的进入和退出 ........................................................................... .. (8)password...................................................................... ............................................................ 8 mkdir、rm、mv和cd ........................................................................... (8)ls ........................................................................... . (9)date ......................................................................... (10)wc ........................................................................... (10)who .......................................................................... .. (10)finger ....................................................................... .. (11)ps ........................................................................... . (11)kill ......................................................................... . (15)find ......................................................................... (15)grep.......................................................................... .. (16)第三章 vi编辑器 ........................................................................... (18)3.1 vi 简介 ........................................................................... ............................................. 18 3.2 vi的进入与离开 ........................................................................... ............................ 18 3.3 vi 的文本输入模式 ........................................................................... ...................... 18 3.4 vi 基本编辑命令............................................................................ .......................... 19 3.5 文件处理子命令 ........................................................................... ............................ 21 第四章存储管理............................................................................ (21)4.1 相关术语 ........................................................................... .. (21)PV (PhysicalVolume) ...................................................................... ..................................... 21 VG (VolumeGroup) ....................................................................... ....................................... 21 PP (PhysicalPartition) ................................................................... ....................................... 22 LP (LogicalPartition) ................................................................... ......................................... 22 LV(LogicalVolume) ...................................................................... ........................................ 22 Mirror(镜像) .......................................................................... ............................................... 22 VGDA(Volume Group Description Area,卷组描述区) ........................................................ 22 VGSA(Volume Group Status Area,卷组状态区) .................................................................. 23 4.2 PV的管理 ........................................................................... (23)硬盘安装 ........................................................................... .................................................... 23 配置一个PV ........................................................................... .............................................. 23 修改PV的属性 ........................................................................... ......................................... 24 删除一个PV ........................................................................... .............................................. 24 4.3 VG的管理 ........................................................................... .. (24)创建一个VG ........................................................................... ............................................. 24 删除一个VG ........................................................................... (25)第 2 页共 52 页对VG的管理 ........................................................................... ............................................ 25 4.4 LV的管理 ........................................................................... (27)增加一个LV ........................................................................... .............................................. 27 修改LV的属性 ........................................................................... ......................................... 28 删除一个LV ........................................................................... . (31)第五章 RS6000 更换硬盘的过程 ........................................................................... (32)HDISK0和HDISK1做成MIRROR，是ROOTVG ......................................................... 32 先做系统备份 ........................................................................... ............................................ 32 查看HDISK0的S/N，P/N号等，在换盘的时候做对照 ................................................ 33 查看所有硬盘（包括逻辑盘）的状态 # lsdev -Ccdisk ................................................ 33 停HACMP ........................................................................ ................................................... 34 把HDISK0从ROOTVG中不做MIRROW ......................................................................34 关机 ........................................................................... ............................................................ 34 开机 ........................................................................... ............................................................ 34 把HDISK0加到ROOTVG中并做镜像 ............................................................................35 重启动2号机 ........................................................................... ............................................ 35 关闭1号机的HACMP ........................................................................ ................................ 35 重启动1号机 ........................................................................... ............................................ 35 启动1号机的HACMP ........................................................................ ................................ 35 启动2号机的HACMP ........................................................................ .. (35)第六章 HACMP安装配置 ........................................................................... .. (36)准备工作 ........................................................................... .................................................... 36 检测连8port卡的TTY .......................................................................... .............................. 37 使用AIX安装CD安装文件 ........................................................................... ................... 37 修改电源管理 ........................................................................... ............................................ 38 Netscape安装和配置 ........................................................................... ................................ 38 安装HACMP/ES软件 ........................................................................... .............................. 38 安装最新的AIX和HACMP补丁............................................................................ .......... 38 SSA微码升级 ........................................................................... ........................................... 39 设置主机名 ........................................................................... ................................................ 39 为所有网卡绑定boot或standby的IP地址 (39)创建VG、LV和FS ........................................................................... .................................. 40 修改系统参数 ........................................................................... ............................................ 41 重启两台机器 ........................................................................... ............................................ 41 配置HACMP ........................................................................ ............................................... 41 HA测试(一)：启动和关闭 ........................................................................... .................... 43 HA测试(二)：本机IP接管 ........................................................................... ..................... 44 HA测试(三)：资源接管 ........................................................................... .. (44)第七章模拟硬盘更换............................................................................ (46)预做方案 ........................................................................... (46)查看硬盘信息 ........................................................................... ............................................ 46 把要更换硬盘从VG中拿掉 ........................................................................... .................... 46 关机 ........................................................................... ............................................................ 46 准备工作 ........................................................................... .................................................... 46 拆机箱 ........................................................................... ........................................................ 46 更换硬盘 ........................................................................... . (47)第 3 页共 52 页开机 ....................................................................................................................................... 47 查看硬盘 ........................................................................... .................................................... 47 改PV............................................................................ ......................................................... 47 做镜像 ........................................................................... ........................................................ 47 把另一块盘18G拿掉 ........................................................................... ............................... 47 关机 ........................................................................... ............................................................ 48 更换硬盘 ........................................................................... .................................................... 48 开机 ........................................................................... ............................................................ 48 查看硬盘信息 ........................................................................... ............................................ 48 改PV............................................................................ ......................................................... 48 做镜像 ........................................................................... ........................................................ 48 起服务 ........................................................................... ........................................................ 48 英迈强人 ........................................................................... ............................................................ 48 第二方案 ........................................................................... (50)把把机器的前面板拆下 ........................................................................... ............................ 50 查看硬盘信息，看哪个盘是干什么用的 ...........................................................................50 把要更换硬盘从VG中拿掉 ........................................................................... .................... 50 把硬盘做成PV ........................................................................... .......................................... 51 lspv查看硬盘情况 ........................................................................... .................................... 51 把硬盘加到VG中 ............................................................................................................... 51 把18G硬盘数据复制到36G上, .......................................................................... .............. 51 取下另一18G硬盘 ........................................................................... ................................... 51 把硬盘做成PV ........................................................................... .......................................... 51 做镜像 ........................................................................... ........................................................ 51 检查，OK ........................................................................... .. (52)第 4 页共 52 页第一章 AIX操作系统的安装安装介质与方式AIX操作系统的安装可以： 1）通过Tape安装。
各系统多路径检测
# fget_config -Av (适用于DS3K/DS4K的RDAC路径查询）
3、 查看SDDPCM存储盘的路径
# pcmpath query device (适用于DS6K/DS8K和v7000的SDDPCM路径查询)
#pcmpath query adapter 检查 SDDPCM 适配器状态
.执行重新配置
# powermt check
Warning: CLARiiON device path c2t0d0s0 is currently dead.
Do you want to remove it (y/n/a/q)? y
Warning: CLARiiON device path c2t0d1s0 is currently dead.
Do you want to remove it (y/n/a/q)? y
Warning: CLARiiON device path c2t0d2s0 is currently dead (y/n/a/q)? a
Warning: CLARiiON device path c2t0d3s0 is currently dead.
查看父设备
lsdev -Cl fscsi0 -F parent
lsdev -Cc disk
lsdev -Cc adapter
lscfg -vpl
AIX多路径：
1、 查看MPIO的存储盘的路径
# lspath (适用于所有存储的MPIO路径查询）
# mpio_get_config -Av (适用于DS3K/DS4K的MPIO路径查询）
Warning: CLARiiON device path c2t0d4s0 is currently dead.
AIX 下安装HDLM多路径软件概要
AIX下安装HDS HDLM多路径软件1.安装环境和软件准备 (2)1.1安装环境 (2)1.2软件上传至服务器 (2)1.3修改目录权限 (2)2．安装ODM包 (3)2.1.拷贝license文件 (3)2.2解压ODM (3)2.3安装ODM 软件 (3)2. 3.1 使用smit 安装 (3)2.3.2选择安装软件：Install Software (3)2.3.3目录选择当前：./ (4)2.3.4 ACCEPT new license agreements选择 yes和选择组件 (4)2.3.5回车安装 (5)2.3.6 重启VIOS (5)3.安装HDLM软件 (5)3.1删除旧的光纤卡 (6)3.2手动执行安装 (6)3.3重新扫描设备 (6)3.4.验证 (6)4.后续配置 (9)4.1修改光纤卡配置 (9)4.2修改磁盘属性 (10)1.安装环境和软件准备1.1安装环境VIO server ioslevel 2.2.1.0 oslevel 6.1.0.0HDLM软件版本 Dynamic Link Manager 6.6.0.01.2软件上传至服务器上传hdlm_license.plk、HTCODM3.tar、HDLM_AIX至/home/padmin/iso1.3修改目录权限chown -R root:staff /home/padmin/iso2．安装ODM包2.1.拷贝和重命名license文件cp /home/padmin/iso/hdlm_license.plk /var/tmp/hdlm_license2.2解压ODMcd /home/padmin/isotar -xvf HTCODM3.tar2.12.3安装ODM 软件2. 3.1 使用smit 安装smit installp2.3.2选择安装软件：Install Software Move cursor to desired item and press Enter. Install SoftwareUpdate Installed Software to Latest Level (Update All) Install Software Bundle Update Software by Fix (APAR)Install and Update from ALL Available Software2.3.3目录选择当前：./Install SoftwareType or select a value for the entry field.Press Enter AFTER making all desired changes.[Entry Fields]* INPUT device / directory for software [./]2.3.4 ACCEPT new license agreements选择 yes和选择组件 Install SoftwareType or select values in entry fields.Press Enter AFTER making all desired changes.[Entry Fields]* INPUT device / directory for software ./* SOFTWARE to install [_all_latest] +(标移到软件安装，按F4(esc+4)选择要安装的包，如果是HACMP环境，就将所有包选择上，如果是环境就选择除HACMP包外的所有包安装)Install SoftwarePREVIEW only? (install operation will NOT occur) no +COMMIT software updates? yes +SAVE replaced files? no +AUTOMATICALLY install requisite software? yes +EXTEND file systems if space needed? yes +OVERWRITE same or newer versions? no +VERIFY install and check file sizes? no +Include corresponding LANGUAGE filesets? yes +DETAILED output? no + Process multiple volumes? yes +ACCEPT new license agreements? yes + #按F4（Esc+4）选择Preview new LICENSE agreements? no +2.3.5回车安装2.3.6 重启VIOS登陆IVM关闭所有LPARshutdown –Fr3.安装HDLM软件3.1删除旧的光纤卡rmdev -Rdl fcs0rmdev -Rdl fcs13.2手动执行安装installp -aXgd /home/padmin/iso/HDLM_AIX/HDLM_AIX all3.3重新扫描设备cfgmgr3.4.验证查看磁盘：# lspvhdisk0 0001eb2b7fcddab9 rootvgactivehdisk1 0001eb2bdc16a0ad rootvgactivehdisk2 0001eb2b019d78ea None hdisk3 0001eb2b019d7b85 None hdisk40001eb2b019d7e45 None hdisk5 0001eb2b019d8107 None hdisk6 0001eb2b019d83c7 None# lsdev -Cc diskhdisk0 Available 00-08-00 SAS Disk Drivehdisk1 Available 00-08-00 SAS Disk Drivehdisk2 Available 01-00-01 Hitachi Disk Array (Fibre)hdisk3 Available 01-00-01 Hitachi Disk Array (Fibre)hdisk4 Available 01-00-01 Hitachi Disk Array (Fibre)hdisk5 Available 01-00-01 Hitachi Disk Array (Fibre)hdisk6 Available 01-00-01 Hitachi Disk Array (Fibre)出现：Hitachi Disk Array (Fibre) 表示磁盘使用HDLM软件，多路径软件安装成功查看安装软件：# lslpp -la DLManager.mpio.rteFileset Level State Description ----------------------------------------------------------------------------Path: /usr/lib/objreposDLManager.mpio.rte 6.6.0.0 COMMITTED Dynamic Link ManagerPath: /etc/objreposDLManager.mpio.rte 6.6.0.0 COMMITTED Dynamic Link Manager验证多路径链路和磁盘详细信息：/usr/DynamicLinkManager/bin/dlnkmgr view -luProduct : AMSSerialNumber : 85005322LUs : 5iLU HDevName OSPathID PathID Status0091 hdisk2 00001 000005 Online00000 000006 Online0092 hdisk3 00000 000000 Online00001 000001 Online0093 hdisk4 00001 000003 Online00000 000004 Online0094 hdisk5 00000 000002 Online00001 000009 Online0095 hdisk6 00001 000007 Online00000 000008 OnlineKAPL01001-I The HDLM command completed normally. Operation name = view, completion time = 2012/06/25 11:08:03查看Status为Online,表示所有链路正常4.后续配置4.1修改光纤卡配置修改光纤卡fc_err_recov属性值(链路出现故障后快速切换策略)通过lspath命令查找到磁盘从那个光纤卡上映射过来的，然后对查到的光纤卡属性做修改lspathlsattr -El fscsi0lsattr -El fscsi1删除rmdev -l fscsi0 -Rrmdev -l fscsi1 -R更改属性chdev -l fscsi0 -a fc_err_recov=fast_failchdev -l fscsi1 -a fc_err_recov=fast_fail确认更改是否成功lsattr -El fscsi0lsattr -El fscsi1重新扫描cfgmgr4.2修改磁盘属性查看当前属性：# lsattr -El hdisk2PCM PCM/friend/hitachifcp N/A True PR_key_value 0x2c9f4204c Reserve Key True algorithm round_robin N/A Falseclr_q no Device CLEARS its Queue on error True dvc_support N/A Falselocation Location Label Truelun_id 0x0 Logical Unit Number ID Falsemax_transfer 0x40000 Maximum TRANSFER Size True node_name0x50060e80058f0c34 FC Node Name False pvid none Physical Volume ID Falseq_err yes Use QERR bit False q_type simple Queue TYPE Truequeue_depth 2 Queue DEPTH True reassign_to 120 REASSIGN time out True reserve_policy PR_exclusive Reserve Policy True rw_timeout 60 READ/WRITE time out True scsi_id 0x11d00 SCSI ID Falsestart_timeout 60 START UNIT time out Trueww_name 0x50060e80058f0c34 FC World Wide Name False修改属性：修改queue_depth值,推荐值为8chdev -l hdisk-name -a queue_depth=8 -a rw_timeout=60 查看修改后属性：# lsattr -El hdisk2PCM PCM/friend/hitachifcp N/A True PR_key_value 0x3c9f4604c Reserve Key True algorithm round_robin N/A Falseclr_q no Device CLEARS its Queue on error True dvc_support N/A Falselocation Location Label Truelun_id 0x0 Logical Unit Number ID Falsemax_transfer 0x40000 Maximum TRANSFER Size True node_name0x50060e80058f0c34 FC Node Name False pvid none Physical Volume ID False q_err yes Use QERR bit False q_type simple Queue TYPE Truequeue_depth 8 Queue DEPTH True reassign_to 120 REASSIGN time out True reserve_policy no_reserve Reserve Policy True rw_timeout 60 READ/WRITE time out True scsi_id 0x11d00 SCSI ID Falsestart_timeout 60 START UNIT time out Trueww_name 0x50060e80058f0c34 FC World Wide Name False。
ERPMRP管理方法及多路径冗余软件POWERPATH安装配置测试报
（ERPMRP管理)方法及多路径冗余软件POWERPATH安装配置测试报EMC磁盘连接AIX的方法及多路径冗余软件POWERPATH安装、配置、测试报告第一、ODM部分21.安装前准备工作2获取EMC ODM文件22.安装配置过程23、安装后确认3第二、POWERPATH部分4准备工作4安装配置过程4性能测试工作54、powermt提供的其他功能245、测试环境拓扑图26第三、Appendix：28第一、ODM部分1.安装前准备工作说明：一般情况下，AIX自带的FC驱动也可以让AIX正常识别出EMC的磁盘，但是会显示为otherFCdisk之类，这样powerpath是无法管理的，所以要加装ODM。
获取EMCODM文件1、下载EMCodm文件，这是针对emc在aix提供的驱动。
下载地址：ftp.emc./pub/elab/aix/ODM_DEFINITIONS2.安装配置过程1、下载的文件类型这个名字：EMC.AIX.5.3.0.1.tar.Z，通过FTP传到AIX上。
使用binary的方式传，否则无法解压。
2、gzip–d，tarxvf命令接包。
3、解包之后用installp命令。
4、安装的时候重点先看看包里面的readme文件，里面重点提到的是不管链接那种EMC设备都只能安装一种support软件，对于symmetric而言，只能安装如下3种文件的任意1种。
EMCSymmetrixFCPSupportSoftware;IBMFibreChanneldriversupport.EMCSymmetrixFCPMPIOSupportSoftware;IBMdefaultPCMMPIOsupport.EMCSymmetrixFCPPowerMPIOSupportSoftware;PowerPathcustomPCMMPIOsu pport.（这次测试大部分时间都耗在这个问题上，以前没有认真看readme，把全部的fileset都全部安装了。
AIX-多路径安装
hdisk5 Available 05-00-01 Hitachi Disk Array (Fibre)
hdisk6 Available 05-00-01 Hitachi Disk Array (Fibre)
#cfgmgr -vl fcs0;cfgmgr -vl fcs2
检查多路径配置
# ./dlnkmgr view -lu
Product : VSP
SerialNumber : 0090537
LUs : 17
iLU HDevName OSPathID PathID Status
000B00 hdisk2 00000 000014 Online
000B10 hdisk18 00000 000013 Online
KAPL01001-I The HDLM command completed normally. Operation name = view, completion time = 2013/06/06 04:55:17
查看系统磁盘设备已经都识别为Hitachi类型的设备
hdisk10 Available 05-00-01 Hitachi Disk Array (Fibre)
hdisk11 Available 05-00-01 Hitachi Disk Array (Fibre)
hdisk12 Available 05-00-01 Hitachi Disk Array (Fibre)
x Hitachi ALL x
x + 5.0.0.5 AIX Suபைடு நூலகம்port for Hitachi Disk Arrays(Update) x
方法及多路径冗余软件POWERPATH安装、配置、测试报
EMC磁盘连接AIX的方法及多路径冗余软件POWERPATH安装、配置、测试报告第一、ODM局部1. 安装前预备工作讲明：一般情况下，AIX自带的FC驱动也能够让AIX正常识不出EMC的磁盘，然而会显示为otherFCdisk之类，如此powerpath是无法治理的，因此要加装ODM。
猎取EMCODM文件1、下载EMCodm文件，这是针对emc在aix提供的驱动。
下载地址：2. 安装配置过程1、下载的文件类型那个名字：，通过FTP传到AIX上。
使用binary的方式传，否那么无法解压。
2、gzip–d，tarxvf命令接包。
3、解包之后用installp命令。
4、安装的时候重点先瞧瞧包里面的readme文件，里面重点提到的是不管链接那种EMC设备都只能安装一种support软件，关于symmetric而言，只能安装如下3种文件的任意1种。
EMCSymmetrixFCPSupportSoftware;IBMFibreChanneldriversupport.EMCSymmetrixFCPMPIOSupportSoftware;IBMdefaultPCMMPIOsupport.EMCSymmetrixFCPPowerMPIOSupportSoftware;PowerPathcustomPCMMPIOsupport.〔这次测试大局部时刻都耗在那个咨询题上，往常没有认真瞧readme，把全部的fileset都全部安装了。
一旦把全部fileset安装上，全然无法识不sysmmetrix的盘，如此导致了后面的powerpath也就无法做了费了2天时刻啊。
〕5、安装结果如下：#lslpp-l|grepEMC.*te5.3.0.1COMMITTEDEMCSymmetrixAIXSupportEMC.Symmetrix.fcp.rte5.3.0.1COMMITTEDEMCSymmetrixFCPSupportcfgmgr也能够把，但测试中发觉确实重启才行〕3、安装后确认第二、POWERPATH局部预备工作1. 猎取powerpath安装文件●到下载即可。
AIX系统操作手册
IAIX系统操作手册系统操作手册版本：5L目录第一章AIX操作系统的安装 (5)安装介质与方式 (5)BOS（Base Operating System)安装 (5)第二章AIX操作系统基本命 (8)➢系统的进入和退出 (8)password (8)mkdir、rm、mv和cd (8)ls (9)date (10)wc (10)who (10)finger (11)ps (11)kill (15)find (15)grep (16)第三章vi编辑器 (18)3。
1vi 简介 (18)3.2vi的进入与离开 (18)3.3vi 的文本输入模式 (18)3。
4vi 基本编辑命令 (19)3.5文件处理子命令 (21)第四章存储管理 (21)4.1相关术语 (21)PV (Physical V olume） (21)VG (Volume Group） (21)PP （Physical Partition) (22)LP (Logical Partition） (22)LV(Logical V olume） (22)Mirror（镜像） (22)VGDA(Volume Group Description Area，卷组描述区) (22)VGSA（V olume Group Status Area,卷组状态区) (23)4.2PV的管理 (23)硬盘安装 (23)配置一个PV (23)修改PV的属性 (24)删除一个PV (24)4.3VG的管理 (24)创建一个VG (24)删除一个VG (25)对VG的管理 (25)4。
4LV的管理 (27)增加一个LV (27)修改LV的属性 (28)删除一个LV (31)第五章RS6000 更换硬盘的过程 (32)HDISK0和HDISK1做成MIRROR，是ROOTVG (32)先做系统备份 (33)查看HDISK0的S/N，P/N号等,在换盘的时候做对照 (33)查看所有硬盘（包括逻辑盘）的状态＃lsdev -Cc disk (34)停HACMP (34)把HDISK0从ROOTVG中不做MIRROW (34)关机 (34)开机 (35)把HDISK0加到ROOTVG中并做镜像 (35)重启动2号机 (35)关闭1号机的HACMP (35)重启动1号机 (36)启动1号机的HACMP (36)启动2号机的HACMP (36)第六章HACMP安装配置 (36)准备工作 (36)检测连8port卡的TTY (37)使用AIX安装CD安装文件 (37)修改电源管理 (38)Netscape安装和配置 (38)安装HACMP/ES软件 (38)安装最新的AIX和HACMP补丁 (39)SSA微码升级 (39)设置主机名 (39)为所有网卡绑定boot或standby的IP地址 (39)创建VG、LV和FS (40)修改系统参数 (41)重启两台机器 (41)配置HACMP (42)HA测试（一)：启动和关闭 (43)HA测试（二）：本机IP接管 (44)HA测试（三)：资源接管 (44)第七章模拟硬盘更换 (46)预做方案 (46)查看硬盘信息 (46)把要更换硬盘从VG中拿掉 (46)关机 (47)准备工作 (47)拆机箱 (47)更换硬盘 (47)开机 (47)查看硬盘 (47)改PV (47)做镜像 (47)把另一块盘18G拿掉 (47)关机 (48)更换硬盘 (48)开机 (48)查看硬盘信息 (48)改PV (48)做镜像 (48)起服务 (48)英迈强人 (48)第二方案 (50)把把机器的前面板拆下 (50)查看硬盘信息，看哪个盘是干什么用的 (50)把要更换硬盘从VG中拿掉 (50)把硬盘做成PV (50)lspv查看硬盘情况 (51)把硬盘加到VG中 (51)把18G硬盘数据复制到36G上， (51)取下另一18G硬盘 (51)把硬盘做成PV (51)做镜像 (51)检查，OK (52)第一章AIX操作系统的安装安装介质与方式AIX操作系统的安装可以：1）通过Tape安装。
AIX下安装HDLM多路径软件概要
AIX下安装HDS HDLM多路径软件1•安装环境和软件准备 (2)1.1安装环境 (2)1.2软件上传至服务器 (2)1.3修改目录权限 (2)2•安装ODM包 (3)2.1. 拷贝license文件 (3)2.2 解压ODM (3)2.3安装ODM软件 (3)2. 3.1使用smit安装 (3)2.3.2 选择安装软件：In stall Software (3)2.3.3目录选择当前：./ (4)2.3.4 ACCEPT new lice nse agreeme nt选择yes 和选择组件 (4)2.3.5回车安装 (5)2.3.6 重启VIOS (5)3. 安装HDLM 软件 (5)3.1删除旧的光纤卡 (6)3.2手动执行安装 (6)3.3重新扫描设备 (6)3.4.验证 (6)4. ..................................................................................................................................... 后续配置 (9)4.1修改光纤卡配置 (9)4.2修改磁盘属性 (10)1. 安装环境和软件准备1.1安装环境VIO server ioslevel 2.2.1.0 oslevel 6.1.0.0HDLM 软件版本Dynamic Link Manager 6.6.0.01.2软件上传至服务器上传hdlm_license.plk、HTCODM3.tar、HDLM_AIX 至/home/padmin/iso1.3修改目录权限chow n -R root:staff /home/padm in/iso2. 安装ODM包2.1. 拷贝和重命名license文件cp /home/padmi n/iso/hdlm」ice nse.plk /var/tmp/hdl m」ice nse 2.2解压ODM。
HDS-HDLM多路径的管理软件aix
1.多路径的管理软件Dynamic Link Manager是HDS配合各个主机厂家在主机高可用系统运行结构中提供的独特软件，安装在主机上，需要存储系统微码支持。
它使用最优的调度算法使连接主机与磁盘阵列的各I/O通道间的I/O自动达到均衡，这样可提高系统的I/O吞吐量，提高整个系统的性能。
Dynamic Link Manager另一个功能是I/O通道故障自动隔离。
当主机与磁盘系统之间的I/O通道在链路环节上出现故障(如HBA卡、交换机、光缆、接口卡)，Dynamic Link Manager能实现自动故障隔离，即切换至另一通路，应用I/O可以在正常的通道上继续进行,确保生产业务的连续性。
当故障通道修复或替换完毕后,可在线激活,重新开始在原通路上工作。
HDLM可以在IBM AIX、 SUN Solaris、Microsoft Windows NT/2000、Linux及HP-UX等多种平台上提高系统的可靠性。
并支持其他的高可靠性（HA）软件，如HACMP、SUN CLUSTER、VCS、MCS等。
在没有多路径功能支持下，主机只能通过某一个路径访问一个磁盘（LUN），系统存在单点故障的隐患。
当该路径上的任何一个环节出现问题时，如主机HBA卡损坏、光纤或光纤交换机损坏等情况下，会造成主机无法访问磁盘的现象，而导致用户系统的中断。
在多路径软件（如HDLM）的支持下，使用多条路径连接主机和存储系统，主机可以通过多个路径访问同一个磁盘，避免出现单点故障，提高整个系统的可靠性。
1.1.HDLM的主要功能负载均衡（Load balancing）当多条路径连接主机和存储系统时，HDLM把负载分配到各个路径，避免单个路径负载繁重而影响处理速度。
∙路径切换（Path Failover ）当多条路径连接主机和存储系统时，如果某条路径出现错误，HDLM将把业务切换到其它活动的路径，保证系统不中断下业务的延续。
∙路径回复（Failback）当一个故障路径回复可用时，HDLM将把该路径恢复为Online，保证最大数目的路径可用和分担负载。
linux多路径软件rdac安装方法
RDAC安装方法首先把rdac的源文件拷贝到服务器上，rdac可以从管理软件SANtricity中的光盘中取得Rdac的安装需要系统装好make，gcc等编译工具，此外还需要安装kernel-devel内核源码包在没安装rdac之前在已经映射存在多路径的情况下，自检或者fdisk-l查看磁盘会有io报错这里以linuxrdac-99.03.0C00.0211.tar.gz版本为例首先解压软件tar –zxvf linuxrdac-99.03.0C00.0211.tar.gzroot@mu01 ~]# cd linuxrdac-99.03.0C00.0211/查看解压出的文件[root@mu01 linuxrdac-99.03.0C00.0211]# lsgenfileattributes mppiscsi_umountall mppLnx26p_vhbatask.cgenuniqueid.c mpp_linux_headers mpp_rcscript.REDHAThbaCheck mpp_linux_sys_headers mpp_rcscript.SUSELicense.txt mppLnx26p_sysdep.c mppSupportlsvdev mppLnx26p_upper.c Readme.txtMakefile mppLnx26p_vhba.c setupDriver.REDHA TmppCmn_s2tos3.c mppLnx26p_vhbaio.c setupDriver.SUSEmppCmn_SysInterface.c mppLnx26p_vhbalib.c setupMpp26p.shmpp.conf mppLnx26p_vhbamisc.c utilityMPP_hba.c mppLnx26p_vhbaproc.c执行编译[root@mu01 linuxrdac-99.03.0C00.0211]# makemake[1]: Entering directory `/usr/src/kernels/2.6.18-164.el5-x86_64'CC [M] /root/linuxrdac-99.03.0C00.0211/MPP_hba.oCC [M] /root/linuxrdac-99.03.0C00.0211/mppLnx26p_upper.oCC [M] /root/linuxrdac-99.03.0C00.0211/mppLnx26p_sysdep.oCC [M] /root/linuxrdac-99.03.0C00.0211/mppCmn_s2tos3.oCC [M] /root/linuxrdac-99.03.0C00.0211/mppCmn_SysInterface.oCC [M] /root/linuxrdac-99.03.0C00.0211/mppLnx26p_vhbamisc.oCC [M] /root/linuxrdac-99.03.0C00.0211/mppLnx26p_vhbatask.oCC [M] /root/linuxrdac-99.03.0C00.0211/mppLnx26p_vhba.oCC [M] /root/linuxrdac-99.03.0C00.0211/mppLnx26p_vhbaproc.oCC [M] /root/linuxrdac-99.03.0C00.0211/mppLnx26p_vhbalib.oCC [M] /root/linuxrdac-99.03.0C00.0211/mppLnx26p_vhbaio.oLD [M] /root/linuxrdac-99.03.0C00.0211/mppUpper.oLD [M] /root/linuxrdac-99.03.0C00.0211/mppVhba.oBuilding modules, stage 2.MODPOSTCC /root/linuxrdac-99.03.0C00.0211/mppUpper.mod.oLD [M] /root/linuxrdac-99.03.0C00.0211/mppUpper.koCC /root/linuxrdac-99.03.0C00.0211/mppVhba.mod.oLD [M] /root/linuxrdac-99.03.0C00.0211/mppVhba.komake[1]: Leaving directory `/usr/src/kernels/2.6.18-164.el5-x86_64'make[1]: Entering directory `/usr/src/kernels/2.6.18-164.el5-x86_64'Building modules, stage 2.MODPOSTmake[1]: Leaving directory `/usr/src/kernels/2.6.18-164.el5-x86_64'gcc -g -I/root/linuxrdac-99.03.0C00.0211 -I/root/linuxrdac-99.03.0C00.0211/mpp_linux_headers/ -I/root/linuxrdac-99.03.0C00.0211/mpp_linux_sys_headers/ -c ./utility/mppUtil.c -o mppUtil.o /bin/bash ./genfileattributes bldgcc -g -I/root/linuxrdac-99.03.0C00.0211 -I/root/linuxrdac-99.03.0C00.0211/mpp_linux_headers/ -I/root/linuxrdac-99.03.0C00.0211/mpp_linux_sys_headers/ -c ./utility/mppUtil26p_sysdep.c -o mppUtilSysdep.ogcc mppUtil.o mppUtilSysdep.o -o mppUtilgcc -o genuniqueid genuniqueid.c执行安装，执行安装完毕后会被/boot目录下生成mpp开头的initrd内核映像文件[root@mu01 linuxrdac-99.03.0C00.0211]# make installmake[1]: Entering directory `/usr/src/kernels/2.6.18-164.el5-x86_64'Building modules, stage 2.MODPOSTmake[1]: Leaving directory `/usr/src/kernels/2.6.18-164.el5-x86_64'make[1]: Entering directory `/usr/src/kernels/2.6.18-164.el5-x86_64'Building modules, stage 2.MODPOSTmake[1]: Leaving directory `/usr/src/kernels/2.6.18-164.el5-x86_64'/bin/bash ./genfileattributes bldgcc -g -I/root/linuxrdac-99.03.0C00.0211 -I/root/linuxrdac-99.03.0C00.0211/mpp_linux_headers/ -I/root/linuxrdac-99.03.0C00.0211/mpp_linux_sys_headers/ -c ./utility/mppUtil26p_sysdep.c -o mppUtilSysdep.ogcc mppUtil.o mppUtilSysdep.o -o mppUtilChecking Host Adapter Configuration...iSCSI software initiator found. Do you want MPP to manage an iSCSI storage array?Do you want to continue (yes or no) ? yesPlease wait while we modify the system configuration files.Your kernel version is 2.6.18-164.el5Preparing to install MPP driver against this kernel version...Generating module dependencies...Creating new MPP initrd image...红色为生成的mpp 内核映像[root@mu01 ~]# cd /boot[root@mu01 boot]# lsconfig-2.6.18-164.el5 initrd-2.6.18-164.el5_old.img mpp-2.6.18-164.el5xen.img vmlinuz-2.6.18-164.el5config-2.6.18-164.el5xen initrd-2.6.18-164.el5xen.img symvers-2.6.18-164.el5.gz vmlinuz-2.6.18-164.el5xengrub initrd-2.6.18-164.el5xen_old.img symvers-2.6.18-164.el5xen.gz xen.gz-2.6.18-164.el5initrd-2.6.18-164.el5.img lost+foundSystem.map-2.6.18-164.el5 xen-syms-2.6.18-164.el5initrd-2.6.18-164.el5kdump.img memtest86+-1.65 System.map-2.6.18-164.el5xen接下来需要把grub的把内核指向新生成的mpp内核注意：linux系统可能存在多个内核，在哪个内核下编译的rdac生成的mpp映像对应的此内核例如下面的例子系统是在Red Hat Enterprise Linux Server (2.6.18-164.el5xen)内核下编译的那么把需要修改Red Hat Enterprise Linux Server (2.6.18-164.el5xen)内核的initrd指向新生成的mpp内核，假如想Red Hat Enterprise Linux Server (2.6.18-164.el5)内核下mpio软件生效需要进系统时选择进此内核然后然后在此内核下编译指向相应的mpp映像更改前[root@mu01 grub]# cat grub.conf# grub.conf generated by anaconda## Note that you do not have to rerun grub after making changes to this file# NOTICE: You have a /boot partition. This means that# all kernel and initrd paths are relative to /boot/, eg.# root (hd0,0)# kernel /vmlinuz-version ro root=/dev/rootvg/lv0# initrd /initrd-version.img#boot=/dev/sdadefault=1timeout=5splashimage=(hd0,0)/grub/splash.xpm.gzhiddenmenutitle Red Hat Enterprise Linux Server (2.6.18-164.el5xen)root (hd0,0)kernel /xen.gz-2.6.18-164.el5module /vmlinuz-2.6.18-164.el5xen ro root=/dev/rootvg/lv0 rhgb quietmodule /initrd-2.6.18-164.el5xen.imgtitle Red Hat Enterprise Linux Server (2.6.18-164.el5)root (hd0,0)kernel /vmlinuz-2.6.18-164.el5 ro root=/dev/rootvg/lv0 rhgb quietinitrd /initrd-2.6.18-164.el5.img更改后[root@mu01 grub]# cat grub.conf# grub.conf generated by anaconda## Note that you do not have to rerun grub after making changes to this file# NOTICE: You have a /boot partition. This means that# all kernel and initrd paths are relative to /boot/, eg.# root (hd0,0)# kernel /vmlinuz-version ro root=/dev/rootvg/lv0# initrd /initrd-version.img#boot=/dev/sdadefault=0timeout=5splashimage=(hd0,0)/grub/splash.xpm.gzhiddenmenutitle Red Hat Enterprise Linux Server (2.6.18-164.el5xen)root (hd0,0)kernel /xen.gz-2.6.18-164.el5module /vmlinuz-2.6.18-164.el5xen ro root=/dev/rootvg/lv0 rhgb quietmodule / mpp-2.6.18-164.el5xen.imgtitle Red Hat Enterprise Linux Server (2.6.18-164.el5)root (hd0,0)kernel /vmlinuz-2.6.18-164.el5 ro root=/dev/rootvg/lv0 rhgb quietinitrd /initrd-2.6.18-164.el5.img查看多路径方法在radc make完毕后会生成mppUtil工具可以./mppUtil –g 0可以显示路径状态[root@mu01 linuxrdac-99.03.0C00.0211]# ./mppUtil -g 0Hostname = mu01Domainname = (none)Time = GMT 08/18/2010 11:58:53MPP Information:----------------ModuleName: AS1000G3 SingleController: N VirtualTargetID: 0x000 ScanTriggered: N ObjectCount: 0x000 A VTEnabled: N WWN: 60080e50001828f6000000004c60bd43 RestoreCfg: N ModuleHandle: none Page2CSubPage: Y FirmwareVersion: 7.60.34.xxScanTaskState: 0x00000000LBPolicy: LeastQueueDepthController 'A' Status:-----------------------ControllerHandle: none ControllerPresent: Y UTMLunExists: Y (007) Failed: N NumberOfPaths: 1 FailoverInProg: NServiceMode: NPath #1---------DirectoryVertex: present Present: Y PathState: OPTIMALPathId: 77020000 (hostId: 2, channelId: 0, targetId: 0)Controller 'B' Status:-----------------------ControllerHandle: none ControllerPresent: Y UTMLunExists: Y (007) Failed: N NumberOfPaths: 1 FailoverInProg: NServiceMode: NPath #1---------DirectoryVertex: present Present: Y PathState: OPTIMALPathId: 77010000 (hostId: 1, channelId: 0, targetId: 0)Lun Information---------------Lun #0 - WWN: 60080e5000181d8c000005e94c6a1995----------------LunObject: present CurrentOwningPath: A RemoveEligible: N BootOwningPath: A NotConfigured: N PreferredPath: A DevState: OPTIMAL ReportedPresent: YReportedMissing: NNeedsReservationCheck: NTASBitSet: YNotReady: NBusy: NQuiescent: NController 'A' Path--------------------NumLunObjects: 1 RoundRobinIndex: 0 Path #1: LunPathDevice: presentDevState: OPTIMALRemoveState: 0x0 StartState: 0x1 PowerState: 0x0Controller 'B' Path--------------------NumLunObjects: 1 RoundRobinIndex: 0 Path #1: LunPathDevice: presentDevState: OPTIMALRemoveState: 0x0 StartState: 0x1 PowerState: 0x0Lun #1 - WWN: 60080e50001828f6000005b64c6a1a08----------------LunObject: present CurrentOwningPath: B RemoveEligible: N BootOwningPath: B NotConfigured: N PreferredPath: B DevState: OPTIMAL ReportedPresent: YReportedMissing: NNeedsReservationCheck: NTASBitSet: NNotReady: NBusy: NQuiescent: NController 'A' Path--------------------NumLunObjects: 1 RoundRobinIndex: 0 Path #1: LunPathDevice: presentDevState: OPTIMALRemoveState: 0x0 StartState: 0x1 PowerState: 0x0Controller 'B' Path--------------------NumLunObjects: 1 RoundRobinIndex: 0 Path #1: LunPathDevice: presentDevState: OPTIMALRemoveState: 0x0 StartState: 0x1 PowerState: 0x0Lun #2 - WWN: 60080e5000181d8c000005ed4c6af8c9----------------LunObject: present CurrentOwningPath: A RemoveEligible: N BootOwningPath: A NotConfigured: N PreferredPath: A DevState: OPTIMAL ReportedPresent: YReportedMissing: NNeedsReservationCheck: NTASBitSet: NNotReady: NBusy: NQuiescent: NController 'A' Path--------------------NumLunObjects: 1 RoundRobinIndex: 0 Path #1: LunPathDevice: presentDevState: OPTIMALRemoveState: 0x0 StartState: 0x1 PowerState: 0x0Controller 'B' Path--------------------NumLunObjects: 1 RoundRobinIndex: 0 Path #1: LunPathDevice: presentDevState: OPTIMALRemoveState: 0x0 StartState: 0x1 PowerState: 0x0Lun #3 - WWN: 60080e50001828f6000005b84c6af904----------------LunObject: present CurrentOwningPath: B RemoveEligible: N BootOwningPath: B NotConfigured: N PreferredPath: B DevState: OPTIMAL ReportedPresent: YReportedMissing: NNeedsReservationCheck: NTASBitSet: NNotReady: NBusy: NQuiescent: NController 'A' Path--------------------NumLunObjects: 1 RoundRobinIndex: 0 Path #1: LunPathDevice: presentDevState: OPTIMALRemoveState: 0x0 StartState: 0x1 PowerState: 0x0Controller 'B' Path--------------------NumLunObjects: 1 RoundRobinIndex: 0 Path #1: LunPathDevice: presentDevState: OPTIMALRemoveState: 0x0 StartState: 0x1 PowerState: 0x0Lun #7 - WWN: 60080e50001828f6000004bc4c60bf47----------------LunObject: none CurrentOwningPath: A RemoveEligible: N BootOwningPath: A NotConfigured: N PreferredPath: A DevState: OPTIMAL ReportedPresent: YReportedMissing: NNeedsReservationCheck: NTASBitSet: NNotReady: NBusy: NQuiescent: NController 'A' Path--------------------NumLunObjects: 1 RoundRobinIndex: 0 Path #1: LunPathDevice: present UTMLunDevice: presentDevState: OPTIMALRemoveState: 0x0 StartState: 0x1 PowerState: 0x0Controller 'B' Path--------------------NumLunObjects: 1 RoundRobinIndex: 0 Path #1: LunPathDevice: present UTMLunDevice: presentDevState: OPTIMALRemoveState: 0x0 StartState: 0x1 PowerState: 0x0此外还有个简单的查看路径方法通过/proc/mpp/或者/proc/scsi/mpp查看因为不同的机型可能查看的文件不太一样不再说明可以根据机型在此目录下查看测试方法格式化存储然后挂载进入存储目录写一个50G的文件然后拔掉一个hba卡的光纤线测试，假如此lun正好是通过此hba卡访问的那么lun会进行控制器切换，切换会有一定的时间一般几十秒，在切换期间ls查看此目录的文件切换时间内会没有任何反应想hang死一样，切换完毕后就正常，切换完毕后插上此hba卡的线拔下另一个hba卡的线测试dd if=/dev/zero of=test bs=10M count=5000。
AIX 或 VIOS 多路径选择指南说明书
Guide to selecting a multipathing path control module for AIX or VIOSSkill Level:IntroductoryMichael Browne(*************.com)IBM Distinguished Engineer and Master InventorIBM08Feb2011This guide will assist a client in making the decision on identifying and deciding on which path control module to use in their AIX environment.The major functions for path control or multipathing are discussed and compared.IntroductionWhen determining the path control module to use for AIX and VIOS multi-path I/O supported devices,there are two choices the system administrator and storage administrator can make.One choice is the SDDPCM(Subsystem Device Path Control Module),and the other choice is the AIX default MPIOPCM(Multipathing Input/Output Path Control Module.)The SDDPCM product is provided by most IBM storage products for subsequent installation on the various server operating systems that the device supports.The AIX and VIOS default MPIO(AIXPCM)is provided as an integrated part of the base VIOS POWERVM firmware and AIX operating system product distribution.In this document,the term SDDPCM is used to refer to the Subsystem Device Path Control Module,and AIXPCM is used for both the AIX and VIOS default MPIO module.The term PCM is used when path control modules are being discussed generically.From a high level viewpoint,the SDDPCM provides many common functions and interfaces across various operating systems as an additional downloadable software entity for most IBM storage devices.The AIXPCM is a fully integrated component indeveloperWorks®/developerWorks the AIX and VIOS licensed program product and provides integrated device supportfor the AIX/VIOS environment.This allows existing AIX/VIOS device and upper levelcommands to be used regardless of the storage device.Both IBM and somenon-IBM storage devices are supported.Depending on your environment and mix ofvendor products and server/storage support alignment responsibilities,one PCMover the other may be a better choice for you.This article provides an understanding of the capabilities of them both.Operating system integration and product considerationsThe AIXPCM is included as part of the base AIX and VIOS licensed program producton the IBM System p platform.This enables a tighter integration of software levels interms of coexistence of various software and device firmware levels,as there is oneless part to integrate in the environment.The AIXPCM update levels are providedand are updated and migrated as a mainline part of all the normal AIX and VIOSservice strategy and upgrade/migration paths.Thus,by simply upgrading eitherVIOS or AIX,the AIXPCM is automatically updated to the appropriate level withoutthe need to install any additional modules or filesets.The SDDPCM is an add-on software entity and has its own update strategy andprocess for obtaining fixes.The customer must manage coexistence levels betweenboth the mix of devices,operating system levels and VIOS levels.SDDPCM is not alicensed program product.The customer also has additional responsibilities inperforming operating system migrations in an SDDPCM environment.The AIXPCM provides full fileset level APAR tracking,AIX software Vital ProductDatabase command support,and formal PTFs as part of the AIX and VIOS licensedprogram products.SDDPCM provides a list of items fixed in the software entityrelease documentation,full replacement file sets,and additional scripts.Supported devicesThe SDDPCM software entity is provided for specific IBM devices and is referencedby the particular device support statement.The supported devices differ betweenAIX and POWERVM VIOS,as well.AIXPCM supports all devices that the AIX operating system and VIOS POWERVMfirmware support,including selected third-party devices.Path selection algorithm optionsBoth PCMs provide Fail Over and Round Robin algorithms.The SDDPCM provides additional algorithms called Load Balancing and LoadBalancing Port.These algorithms take into account load statistics based on the/developerWorks developerWorks®number of currently outstanding I/O operations of the server adapters in selectingthe next path for an I/O operation.In the case of Load Balancing and in the case ofLoad Balancing Port,it also incorporates target port I/O statistics,as well.While AIXPCM doesn’t offer a"load balancing"attribute,load balancing using theAIXPCM can be accomplished through a"round_robin"algorithm,combined withuser-customizable path priorities.The default option for SDDPCM is Load Balance.The default option for AIXPCM isFail Over.SDDPCM allows for dynamic selection of path selection algorithm options,while theAIXPCM requires each hdisk be reconfigured for a new path selection algorithm totake affect.Dynamic path configuration capabilitiesBoth PCMs provide for the ability to add paths to a device dynamically,dynamicallyremove or replace physical adapters,and support AIX and VIOS fibre channeldynamic device tracking.Both PCMs provide an automated means of reclaiming failed paths of openeddevices via kernel processes.In addition,SDDPCM provides a health checkdaemon to provide an automated method of reclaiming failed paths to a closeddevice.AIXPCM has a path health checker built into its functionality to reclaim failedpaths automatically.Both PCMs provide user-customizable health check intervals.Clustered license program product supportBoth PCMs provide support of POWERHA and GPFS clustered software products.Device reservation policyBoth PCMs provide the same device reservation policy capabilities.SAN boot support,dump device and paging supportBoth PCMs support booting from SAN.Upon installation of AIX,the AIXPCM will bethe PCM for the boot devices.If SDDPCM is desired to be used for the boot device,another restart of the system is required after installation of the SDDPCM software.If NIM installation is used and the SDDPCM software is included in the NIMrepository environment,then the second restart is not required.Both PCMs allow for any MPIO device to be used as a paging device and a dumpdevice.Persistent reserve utilitiesdeveloperWorks®/developerWorks The SDDPCM provides a robust set of persistent reserve utilities for examining andmanaging persistent reserves on devices.Enhanced device utilities for SDDPCM supported devicesThe SDDPCM provides enhanced utilities(pcmpath commands)to show mappingsfrom adapters,paths,devices,as well as performance and error statistics than canbe useful in SAN management for those supported devices.Performance and error statistics when using the AIXPCM are gathered via standardperformance monitoring tools which ship with AIX,such as iostat and fcstat.ConclusionThis guide described the relevant features of the AIXPCM and the SDDPCM pathcontrol modules in a compare and contrast fashion.Reading this guide and usingthe provided product documentation for both of these path control modules allows asystem administrator the ability to make an informed decision on which multipathingsolution to use in their environment./developerWorks developerWorks®ResourcesLearn•See the IBM System Storage Multipath Subsystem Device Driver User’s Guide to learn how to install and configure the IBM System Storage MultipathSubsystem Device Driver Path Control Module(SDDPCM).•The AIX Version6.1Operating System and Device Management Guideprovides users and system administrators with device driver information.•The System Storage Interoperation Center(SSIC)provides detailedinteroperability and interoperation matrix information.Discuss•Follow developerWorks on Twitter.•Get involved in the My developerWorks community.•Participate in the AIX and UNIX®forums:•AIX Forum•AIX Forum for developers•Cluster Systems Management•Performance Tools Forum•Virtualization Forum•More AIX and UNIX ForumsAbout the authorMichael BrowneMichael Browne is an IBM chief test engineer responsible for testing allserver and storage platforms.Some of his areas of expertise are insystems design,SAN implementation,systems management andsystems testing.。
AIX下的MPIO
[基础知识]常见的多路径管理软件Multipath I/O (多路径)在计算机存储技术里,多路径提供了容错和性能提高,在计算机系统里CPU有多条物理路径通道,块存储设备通过总线,控制器,交换设备以及桥接设备来连接。
简单举例同一台计算机里1块SCSI磁盘连接2个SCSI控制器或者磁盘连接到两个FC端口。
如果其中1个控制器，端口或交换设备故障，那操作系统就会自动切换I/O路径到冗余的控制器为应用程序使用,但这样可能会增加延迟.一些多路径软件可以利用冗余的路径提高性能,例如:Dynamic load balancing 动态负载均衡Traffic shaping 流量控制Automatic path management 自动路径管理Dynamic reconfiguration 动态设置Multipath I/O software implementations 多路径软件工具一些操作系统自带支持多路径功能,如下SGI IRIX - using the LV, XLV and later XVM volume managers (1990s and onwards)AIX - MPIO Driver, AIX 5L 5.2 (October 2002) and laterHP-UX 11.31 (2007)Linux - Device-Mapper Multipath . Linux kernel 2.6.13 (August 2005)OpenVMS V7.2 (1999) and laterSolaris Multiplexed I/O (MPxIO), Solaris 8 (February 2000) and laterWindows MPIO Driver, Windows Server 2003 and Windows Server 2008 (April 2003)FreeBSD - GEOM_FOX moduleMac OS X Leopard and Mac OS X Leopard Server 10.5.2Multipath software products: (软件产品)AntemetA. Multipathing Software solution for AIX for HP EVA Disk ArraysNEC PathManagerEMC PowerPathFalconStorIPStorDynaPathFujitsu Siemens MultiPath for Linux and Windows OSFujitsu ETERNUS Multipath Driver (ETERNUSmpd) for Solaris, Windows, Linux and AIX.Hitachi HiCommand Dynamic Link Manager (HDLM)HP StorageWorks Secure PathNCR UNIX MP-RAS EMPATH for EMC Disk ArraysNCR UNIX MP-RAS RDAC for Engenio Disk ArraysONStor SDM multipathIBM System Storage Multipath Subsystem Device Driver (SDD), formerly Data Path OptimizerAccusysPathGuardInfortrendEonPathSun Multipath failover driver for Windows and AIXSun StorEdge Traffic Manager Software, included in Sun Java StorEdge Software suiteLinuxmultipath-tools, used to drive the Device Mapper multipathing driver, first released on September 2003 Fibreutils package for QLogic HBAsRDAC package for LSI disk controllerslpfcdriver package for Emulex HBAsVeritasVeritas Storage Foundation (VxSF)Veritas Volume Manager (VxVM)Pillar Data SystemsAxiom Path Manager for AIX, Windows, Linux, and SolarisAreca Multipath failover driver for WindowsAIX下的MPIO、RDAC、SDDPCM多路径软件操作一：查看存储盘的路径1、查看MPIO的存储盘的路径# lspath (适用于所有存储的MPIO路径查询）# mpio_get_config -Av (适用于DS3K/DS4K的MPIO路径查询）2、查看RDAC存储盘的路径# fget_config -Av (适用于DS3K/DS4K的RDAC路径查询）3、查看SDDPCM存储盘的路径# pcmpath query device (适用于DS6K/DS8K和v7000的SDDPCM路径查询)4、查看当前操作系统自带的支持IBM存储的多路径软件# manage_disk_drivers5、将DS4700默认的多路径软件更改成RDAC# manage_disk_drivers -d DS4700 -o AIX_fcparray二：MPIO路径的常用操作1、查看单个盘的路径# lspath -l hdisk3# lspath -F "status name path_id parent connection" | grep -w hdisk32、MPIO路径控制将fcs0卡下的hdisk2的路径禁用# chpath -l hdisk2 -p fscsi0 -s disable将fcs0卡下的hdisk2的路径启用# chpath -l hdisk2 -p fscsi0 -s enable3、其它参数# chdev -l hdisk3 -a queue_depth=1 //如果ODM是1.0.1.0以上可以是任何数字# chdev -l hdisk3 -a hcheck_interval=60 //链路失效检查时间间隔;如果等0，则不会自检# chdev -l hdisk3 hcheck_mode=nonaciveThis parameter specifies which I/O paths should be monitored by the path health checking functionality.nonactive: This mode will check all failed I/O paths and all standby paths of used/opened devices.failed: This mode with check failed I/O paths only.enabled: This mode will check all enabled I/O paths which are opened.Note:Non-opened devices are not monitored. Also, this attribute isnot being used at this time since path health checking is notenabled. This attribute can be ignored4、修改链路优先级lspath -AHE -l hdisk2 -p vscsi3 //查看链路优先级# chpath -l hdisk3 -p fscsi0 -w 链路1 -a priority=1# chpath -l hdisk3 -p fscsi0 -w 链路2 -a priority=25、处理故障1)如果发现有很多路径是missing的，可以用cfgmgr重新扫描，如果还有missing的，可以用步骤2和2来激活路径；2)如果要更换光纤线，可以该卡上的有的路径禁用，换完线后再启用，避免直接拨线产生的风险。
AIX MPIO and SDDPCM multipath options with DS3000,DS4000,DS5000 常见问题解答
AIX MPIO and SDDPCM multipath options with DS3000/DS4000/DS5000 常见问题解答FAQ: Where do I find information about the AIX MPIO and SDDPCM multipath options with DS3000/DS4000/DS5000?Answer to this FAQ:References for AIX MPIO and SDDPCM multipath options with DS3000/DS4000/DS5000While the RDAC driver is being deprecated with AIX, it is still the default driver on AIX 5.2 and 5.3 for DS4000 devices. With AIX 6.1, the default driver is MPIO for DS4000/DS5000 devices. All future DS4000/DS5000 models will only be supported with MPIO. The DS3K products are always configured as MPIO devices. The MPIO support for these devices removes the limitation of connecting only one adapter to each DS3/4K controller port and allows more than two paths to be configured to the device. This simplifies zoning and improves performance.DS3000: native MPIO onlyDS4000: RDAC, native MPIO, MPIO w/SDDPCMDS5000: native MPIO, MPIO w/SDDPCMFor more details about prerequisites and supported OS and driver levels take a look at the particular interoperability matrices:DS3000 family products interoperability matrix/systems/storage/disk/ds3000/pdf/interop.pdfDS4000 family products interoperability matrix/systems/resources/systems_storage_disk_ds4000_pdf_interop-matrix.pdfDS5000 family products interoperability matrix/systems/resources/systems_storage_disk_ds5000_interop-matrix.pdf第 1 页共14 页AIX MPIO is supported on AIX starting from AIX 5.2 TL10, AIX 5.3 TL6 and AIX 6.1 SP2 though various PTFs and fixes may be required (see interoperability matrix and AIX MPIO documentation below). It is supported with DS4000 firmware 6.60.xx.xx and higher on DS4800, DS4700, DS4200, DS4500 and DS4300. MPIO is the strategic driver for all current DS4000 platforms in AIX 6.1 and up - except for DS4400 which is RDAC only. RDAC is the default driver on all levels of AIX 5.2 and 5.3.In AIX Version 6.1, the DS4K products are configured as Multipath I/O (MPIO) devices by default. A DS4K product using the FCPARRAY (RDAC) driver may be migrated to the MPIO driver by using the instructions found in the documents below, or all DS4K devices may be migrated by uninstalling the devices.fcp.disk.array.rte package and then running the cfgmgr command or rebooting.For more information on how to manage MPIO on AIX with DS4000 subsystems, the required DS4000 NVSRAM settings and the newmanage_disk_driver and mpio_get_config commands, take a look at these documentsProcedures for AIX 6.1 and DS4000 Interoperability/systems/resources/systems_storage_disk_ds4000_pdf_aix.pdfAIX61 TL02 Release Notes (p.19ff)/infocenter/systems/scope/aix/topic/com.ibm.aix.resources/RELNOTES/SC23662903.pdfThe manage_disk_drivers command displays a list of DS4K storage models and the driver that manages each model. All disks of a storage model must be managed by the same driver. If you specify the -c flag, the command changes the driver selection to an alternate supported driver for the storage model.# manage_disk_drivers1: DS4100: currently MPIO; supported: RDAC/fcparray, MPIO2: DS4300: currently MPIO; supported: RDAC/fcparray, MPIO3: DS4500: currently MPIO; supported: RDAC/fcparray, MPIO4: DS4700/DS4200: currently MPIO; supported: RDAC/fcparray, MPIO5: DS4800: currently MPIO; supported: RDAC/fcparray, MPIO第 2 页共14 页According to these documents (and the DS4k/DS5k interoperability matrix) the following NVSRAM changes have to be applied to the DS4000 for MPIO support:set controller [a] HostNVSRAMBYTE [0x06,0x27] = 0;set controller [b] HostNVSRAMBYTE [0x06,0x27] = 0;Please note, that for the NVSRAM changes to take effect a reboot of the DS4K controller is required!The default settings on a DS4800 with firmware 07.36.14.00 and NVSRAM version N1815D48R1036V12 areshow controller [a] HostNVSRAMBYTE [0x06,0x27];show controller [b] HostNVSRAMBYTE [0x06,0x27];Executing script...Controller "a" Host Type Index 6 NVSRAM offset 0x27 = 0x8. (Default value is '8')Controller "b" Host Type Index 6 NVSRAM offset 0x27 = 0x8.第 3 页共14 页第 4 页共14 页Please check and note the default settings first by running the show controller command before actually applying the NVSRAM changes!These settings change bit 3 in NVSRAM for the host type 'AIX' to 0 for MPIO support. Bit 3 of the host type has the following meaning:Bit 3 = 0 A header is returned, along with a reservation key set to zero. This is not is in accordance with the current T10standards for the persistent reservations command set, but preserves compatibility with the legacy implementation.Bit 3 = 1 A header is returned (but no reservation key). This is in accordance with the current T10 standards for the persistent reservations command set.Examples for SAN attachment and zoning with AIX native MPIO and more than two paths can be found in theIBM System Storage DS3000 - Storage Manager v2 Installation and Support Guide for IBM AIX and Linux on POWER/systems/support/supportsite.wss/docdisplay?lndocid=MIGR-5073850&brandind=5000028in chapter 3, Preparing for a SAN attachment (p25ff):The following examples are a small subset of the connectivity configurations that are supported using the DS3400. The best practice is to use 2 to 4 adapters providing 4 to 8 paths.Example 1 Create one zone that contains two Fibre Channel HBA ports, one Fibre Channel port from controller A and one Fibre Channel port from controller B of the DS3400. This configuration provides four paths to hdisks. Two of the paths that are associated with the preferred storage controller will service I/Os when the DS3400 is optimal. The other two paths are used if the preferred controller is not accessible by the host. Note: The hdisk attribute “algorithm” should be set to round_robin. If the attribute is set to round_robin, the hdisk attribute “reserve_policy” must be set to no_reserve, pr_exclusive, or pr_shared.Example 2 Create separate zones for the connection between the HBA port and one port of the DS3400 controller. Two zones are required for a dual-controller storage configuration. One zone contains an HBA port and controller port from controller A. The other zone contains a different HBA port and controller port from controller B. This configuration provides two path s to hdisks. Note: Attributes “algorithm” and “algorithm of hdisks”第 5 页共14 页do not need to be altered from default values.Example 3 Create one zone that contains two Fibre Channel HBA ports and all four Fibre Channel ports from the DS3400. This configuration provides eight paths to hdisks. Four of the paths that are associated with the preferred storage controller will service I/Os when the DS3400 is Optimal. The other four paths are used if the preferred controller is inoperable. Note: The hdisk attribute ″algorithm″ should be set to round_robin. When this attribute is set to round_robin the hdisk attribute ″reserve_policy″ must be set to no_reserve, pr_exclusive, or pr_shared.The default multipath algorithm for DS4K/DS5K devices with MPIO on AIX is fail_over with a reserve_policy of single_path.# lsattr -El hdisk3PCM PCM/friend/otherapdisk Path Control Module FalsePR_key_value none Persistant Reserve Key Value Truealgorithm fail_over Algorithm Trueautorecovery no Path/Ownership Autorecovery Trueclr_q no Device CLEARS its Queue on error Truecntl_delay_time 0 Controller Delay Time Truecntl_hcheck_int 0 Controller Health Check Interval Truedist_err_pcnt 0 Distributed Error Percentage Truedist_tw_width 50 Distributed Error Sample Time Truehcheck_cmd inquiry Health Check Command Truehcheck_interval 60 Health Check Interval Truehcheck_mode nonactive Health Check Mode Truelocation Location Label Truelun_id 0x0 Logical Unit Number ID Falselun_reset_spt yes LUN Reset Supported Truemax_retry_delay 60 Maximum Quiesce Time Truemax_transfer 0x40000 Maximum TRANSFER Size Truenode_name 0x200600a0b81163b8 FC Node Name Falsepvid none Physical volume identifier False第 6 页共14 页q_err yes Use QERR bit Trueq_type simple Queuing TYPE Truequeue_depth 10 Queue DEPTH Truereassign_to 120 REASSIGN time out value Truereserve_policy single_path Reserve Policy Truerw_timeout 30 READ/WRITE time out value Truescsi_id 0xda SCSI ID Falsestart_timeout 60 START unit time out value Trueunique_id 3E213600A0B8000118FD000009A1F49D1EDB20F1815 FAStT03IBMfcp Unique device id Falseww_name 0x202700a0b81143a0 FC World Wide Name FalseIn order to use multiple paths to the preferred controller with native AIX MPIO it is required to set the hdisk's algorithm attribute to round_robin and the reserve_policy attribute to no_reserve (no_reserve will be fine for most situations but is depending on your specific SCSI reservation policy) using:# chdev -l <hdisk#> -a algorithm=round_robin -a reserve_policy=no_reserve -PThis change requires a reboot. Alternatively one can stop using the hdisks (varyoff any VG with the disks) and eliminate the -P flag to go into effect without a reboot.The MPIO reserve_policy defines whether a reservation methodology is employed when the device is opened. The values are as follows:# lsattr -Rl <hdisk#> -a reserve_policyno_reservesingle_pathPR_exclusivePR_sharedno_reserve Does not apply a reservation methodology for the device. The device might be accessed by other initiators, and these initiators might第7 页共14 页be on other host systems.single_path Applies a SCSI2 reserve methodology for the device, which means the device can be accessed only by the initiator that issued the reserve. This policy prevents other initiators in the same host or on other hosts from accessing the device. This policy uses the SCSI2 reserve to lock the device to a single initiator (path), and commands routed through any other path result in a reservation conflict.Path selection algorithms that alternate commands among multiple paths can result in thrashing when the single_path reserve value is selected. As an example, assume a device-specific PCM has a required attribute that is set to a value that distributes I/O across multiple paths. When single_path reserve is in effect, the disk driver must issue a bus device reset (BDR) and then issue a reserve using a new path for sending the next command to break the previous reservation. Each time a different path is selected, thrashing occurs and performance degrades because of the overhead of sending a BDR and issuing a reserve to the target device. (The AIX® PCM does not allow you to select an algorithm that could cause thrashing.)PR_exclusive Applies a SCSI3 persistent-reserve, exclusive-host methodology when the device is opened. The PR_key attribute value must be unique for each host system. The PR_key attribute is used to prevent access to the device by initiators from other host systems.PR_shared Applies a SCSI3 persistent-reserve, shared-host methodology when the device is opened. The PR_key value must be a unique value for each host system. Initiators from other host systems are required to register before they can access the device.The PR_key_value is required only if the device supports any of the persistent reserve policies (PR_exclusive or PR_shared).For more information on native AIX MPIO and the related device attributes please take a look at:System p and AIX Information Center - Multiple Path I/O/infocenter/pseries/v5r3/index.jsp?topic=/com.ibm.aix.baseadmn/doc/baseadmndita/devmpio.htmWith the release of SDDPCM version 2.4.0.0 DS4K and DS5K now are also supported with the additional SDDPCM path control module. SDDPCM is compliant with the MPIO architecture and as such, is an alternative to using the default MPIO PCM that comes with AIX, and is preferable to just using MPIO. RDAC is not an option for the DS5000 or DS3000, and one uses MPIO or preferably SDDPCM which adheres to the MPIO architecture.第8 页共14 页Be aware that the default path selection algorithm with SDDPCM is load_balance with the device reserve policy set to no_reserve which means that no reservation methodology for the device is applied. A SCSI-2 reservation which is typically in place when doing a varyonvg of an AIX volume group is _not_ applied actually with SDDPCM default settings for the device (here the hdisks in that VG) which are reserve_policy=no_reserve and algorithm=load_balance. Such an AIX volume group might be varied on and accessed by other initiators and even other host systems in this case!If the AIX volume group is shared between hosts (not using any cluster services like PowerHA with enhanced concurrent volume groups) and should _not_ be accessed by other hosts using a SCSI-2 reservation methodology the device reserve_policy can be set set to single_path ( SCSI-2 reserve) after setting the device path selection algorithm to fail_over. Any attempt to set the algorithm to round_robin, load_balance, orload_balance_port with single_path reserve policy will fail.For a general documentation of SDDPCM support with DS4000/DS5000 take a look at theMultipath Subsystem Device Driver User's Guide/support/docview.wss?rs=540&context=ST52G7&uid=ssg1S7000303ftp:///storage/subsystem/UG/1.8--2.4/SDD_1.8--2.4_User_Guide_English_version.pdfand also the SDDPCM readmeSDDPCM 2.4.0.0 for AIX Readmeftp:///storage/subsystem/aix/2.4.0.0/sddpcm.readme.2.4.0.0.txtwhich always provides latest information about prerequisites, APARs and other restrictions that currently apply.Please note, the following restrictions (taken from the SDDPCM 2.4.0.0 readme) currently apply with SDDPCM and DS4000/DS5000: ∙VIOS and HACMP are not supported with SDDPCM on DS4000 and DS5000 subsystem devices∙...the SAN boot function is not supported with DS4000 and DS5000 subsystem devices at this release第9 页共14 页Furthermore, the SDDPCM packages also provides the additional pcmpath query command to display and manage SDDPCM devices:# pcmpath query deviceTotal Dual Active and Active/Asymmetrc Devices : 2DEV#: 0 DEVICE NAME: hdisk1 TYPE: 2107900 ALGORITHM: Load BalanceSERIAL: 75KA3628201==========================================================================Path# Adapter/Path Name State Mode Select Errors0 fscsi0/path0 OPEN NORMAL 844158 01 fscsi0/path1 OPEN NORMAL 843779 02 fscsi1/path2 OPEN NORMAL 833541 03 fscsi1/path3 OPEN NORMAL 833459 0DEV#: 1 DEVICE NAME: hdisk2 TYPE: 2145 ALGORITHM: Load BalanceSERIAL: 60050768018082E29000000000000008==========================================================================Path# Adapter/Path Name State Mode Select Errors0* fscsi0/path0 OPEN NORMAL 6 01 fscsi0/path1 OPEN NORMAL 2124784 02 fscsi1/path2 OPEN NORMAL 2148331 03* fscsi1/path3 OPEN NORMAL 8 0Total Active/Passive Devices : 1DEV#: 3 DEVICE NAME: hdisk3 TYPE: 1815 ALGORITHM: Load BalanceSERIAL: 600A0B8000118FD00000878E49C33524==========================================================================第10 页共14 页Path# Adapter/Path Name State Mode Select Errors0* fscsi0/path0 OPEN NORMAL 0 01* fscsi1/path2 OPEN NORMAL 0 02 fscsi0/path1 OPEN NORMAL 94440 03 fscsi1/path3 OPEN NORMAL 94168 0The DS4000 and DS5000 products are dual array controller disk subsystems. Each LUN is assigned to one controller, which is considered the owner, or the active (primary) controller, of a particular LUN. The other controller is considered as an alternate, or passive (secondary), controller. The '*' next to the path ID in the pcmpath command output indicates that the related path is a non-preferred path. The indicator '*' for preferred and non-preferred paths are only shown after the device is opened once.SDDPCM distinguishes the following paths to a given LUN on a DS4000 and DS5000 subsystem:∙Paths to the primary (active) controller that currently owns the LUN and processes the I/Os to that LUN∙Paths to the alternate (passive/secondary) controllerWith this type of active/passive dual-controller subsystem device, I/O can be sent only to the controller that currently owns the LUN. When the SDDPCM selects paths for I/O, it selects paths that are connected only to the active controller for a given LUN. If there is no path on the active controller that can be used, SDDPCM changes the LUN controller ownership to an alternate controller, switches the paths that were passive to active, and then selects these active paths for I/O.As shown in the example above for a DS4800 (model type 1825) the '*' indicates the paths to the secondary or alternate controller for the LUN. That's why there were no I/Os seen on these paths. Here the I/O load for the given LUN is balanced only across the paths to the primary DS4K/DS5K controller that currently owns the LUN. With two host FC adapters (HBAs) in the server and each host adapter seeing both DS4K/DS5k controllers the load-balancing algorithm with SDDPCM will balance I/Os across both host FC adapters for all I/Os to all DS4K/DS5K LUNs.第11 页共14 页The SDDPCM fileset also provides the sddpcm_get_config command for DS4000/DS5000 devices which displays information about allMPIO-based DS4K/DS5K subsystems and the hdisks associated with them. Specifically, it displays information about the frame (subsystem), including the frame's assigned name and worldwide name, and a list of hdisks (only those currently in the Available state) associated with that subsystem, including the hdisk name, LUN number, current ownership, preferred path, and the user-assigned label for that volume.# sddpcm_get_config -AvFrame id 0:Storage Subsystem worldwide name: 60ab8001143a0000049b88968Controller count: 2Partition count: 1Partition 0:Storage Subsystem Name = 'VIOS_DS4800'hdisk LUN # Ownership User Label第12 页共14 页hdisk3 0 A (non-preferred) lpar3_vol01The SDDPCM support matrix and the SDDPCM filesets (devices.sddpcm.61.rte) for DS4000/DS5000 are available here:Support Matrix for Subsystem Device Driver, Subsystem Device Driver Path Control Module/support/docview.wss?rs=540&context=ST52G7&dc=DA400&uid=ssg1S7001350Subsystem Device Driver Path Control Module (SDDPCM)/support/docview.wss?rs=540&context=ST52G7&dc=D430&uid=ssg1S4000201SDDPCM also requires the AIX host attachment script fileset (devices.fcp.disk.ibm.mpio.rte) to be installed as prerequisite:Host Attachment for SDDPCM on AIX/support/docview.wss?rs=540&context=ST52G7&dc=D400&q1=host+script&uid=ssg1S4000203The AIX host attachment script provides the device definitions and ODM attributes for the supported SDDPCM devices. Without the AIX host attachment fileset installed the devices will be managed by the default AIX MPIO PCM and simply show up as:# lsdev -Cc diskhdisk0 Available Virtual SCSI Disk Drivehdisk1 Available 30-T1-01 MPIO Other FC SCSI Disk Drivehdisk2 Available 30-T1-01 MPIO Other FC SCSI Disk Drivehdisk3 Available 30-T1-01 MPIO Other DS4K Array DiskWith the AIX host attachment script installed the supported SDDPCM devices will show up as:# lsdev -Cc diskhdisk0 Available Virtual SCSI Disk Drivehdisk1 Available 30-T1-01 IBM MPIO FC 2107第13 页共14 页hdisk2 Available 30-T1-01 MPIO FC 2145hdisk3 Available 30-T1-01 IBM MPIO DS4800 Array DiskIf the DS4K/DS5K hdisks still show up as "MPIO Other DS4K Array Disk" after the installation of the AIX host attachment script fileset they will not be managed by SDDPCM and will not be displayed by the pcmpath query command. Here it would be necessary to manually remove and reconfigure the devices so that they show up as "IBM MPIO DS4800 Array Disk" (if the appropriate version of the AIX host attachment script for SDDPCM 2.4.x.x is installed).The Multipath Subsystem Device Driver User's Guide recommends a SAN attachment with four paths for DS4000 and DS5000 subsystems with SDDPCM:Because switching a device to another controller is a time-consuming recovery action and affects I/O performance, you can use this redundancy to avoid an unnecessary controller failover if a path fails. Therefore, configure a minimum of four paths for each LUN with two host adapter ports and two storage controller ports where each host adapter port has redundancy to each storage controller port and vice versa. (p.8)General information about DS4000/DS5000 host attachment can be found in theIBM System Storage DS Storage Manager v10.30 - Installation and Host Support Guide/systems/support/supportsite.wss/docdisplay?lndocid=MIGR-5075652&brandind=5000028第14 页共14 页。
AIX-操作指南
AIX 操作指南Free Use but Copyright ReservedMarch 25, 2020目录第1章 AIX操作系统介绍 (5)1.1 模块化内核 (5)1.2 动态调整内核 (6)1.3 多线程内核 (6)1.4 高效输入/输出 (6)1.5 实时处理运算 (8)1.6 日志文件系统 (8)1.7 存储管理 (9)1.8 镜像 (9)1.9 条块化 (10)1.10 安全性能 (10)1.11 系统管理 (11)1.12 在线帮助 (11)第2章系统启动和关机 (13)2.1 多用户引导模式 (13)2.2单用户引导模式 (14)2.3 系统关机 (15)第3章用户登录和退出 (17)3.1 启动CDE (17)3.2 登录 (17)3.3 退出 (18)3.4 用户属性 (19)第4章设备管理 (25)4.1 设备管理介绍 (25)4.2 对象数据库 (26)4.3 添加设备（命令行） (27)4.4 添加设备（SMIT） (28)4.5 ODM未定义的设备 (31)4.6 删除设备 (31)第5章磁盘和文件系统 (33)5.1 系统目录 (33)5.2 逻辑卷管理 (33)5.3 安装磁盘 (34)5.4 创建逻辑卷 (37)5.5 创建文件系统 (38)5.6 管理调页空间 (39)5.7 总结 (40)第6章进程管理 (41)6.1显示/修改进程属性 (41)6.2停止进程 (41)6.3 性能检测 (42)6.4系统资源控制器SRC (43)6.5进程的定时启动 (49)第7章备份和恢复 (51)7.1 备份 (51)7.2 恢复 (53)7.3 映象备份 (54)7.4 磁带驱动器 (55)第8章打印 (56)8.1 队列系统 (56)8.2 本地打印机 (57)8.3 远程打印机 (61)8.4 打印命令 (66)8.5 队列命令 (67)第9章 TCP/IP (68)9.1 配置IP地址和主机名 (68)9.2 路由管理 (69)9.3 网卡配置 (70)9.4 配置域名服务器 (71)9.5 编辑一些重要文件 (72)9.6 管理其它服务 (74)9.7 BSD配置风格 (75)第10章域名服务 (78)10.1 服务器配置文件 (78)10.2 主域名服务器 (78)10.3 次域名服务器 (80)10.4 代理（Cache-Only）域名服务器 (80)10.5 域名服务客户机 (81)10.6 域名解析顺序 (82)第11章网络信息系统 (83)11.1 服务器配置文件 (83)11.2 设置本机为主NIS服务器 (83)11.3 设置本机为次NIS服务器 (84)11.4 设置本机为NIS客户机 (85)11.5 描述图和命令 (85)11.6 NIS守护进程 (87)第12章网络文件系统 (90)12.1 NFS守护进程 (90)12.2 NFS服务器 (91)12.3 NFS客户机 (92)12.4 其他命令 (93)12.5 自动MOUNT (94)第13章邮件 (96)13.1 邮件系统配置文件 (96)13.2 邮件系统守护进程 (96)13.3 邮件别名 (97)13.4 邮件队列 (97)13.5 邮件日志和统计 (98)第14章 X Window (99)14.1 文件和目录结构 (99)14.2 启动X环境 (101)14.3 退出X环境 (102)14.4 终端仿真器 (102)14.5 字体服务器 (103)14.6 显示管理器 (103)14.7 X11互操作性 (103)14.8 CDE互操作性 (106)第1章 AIX操作系统介绍AIX全名为Advanced Interactive Executive,俗称“An IBM uniX”或“Advanced IBM uniX”。
多路径IO(MPIO)和RDAC之间的转换
多路径 I/O（MPIO ）在 AIX V6.1 中，缺省情况下，DS4K 产品将配置为多路径 I/O（MPIO ）设备。
DS3K 产品始终配置为 MPIO 设备。
没有对这些设备的任何 FCPARRAY 支持。
对这些设备的 MPIO 支持使得不再限制只能将一个适配器连接到每个 DS3/4K 控制器端口。
关于将 DS4000 磁盘从 FCPARRAY 转换至 MPIO 的指示信息已增强 MPIO 驱动程序，以支持大多数 DS4000 型号。
MPIO 驱动程序允许配置两条以上的指向设备的路径，这简化了分区并提高了性能。
为了让 DS4000 在MPIO 配置中正确工作，必须执行下列步骤。
下列 AIX 发行版和最低级别 service pack 可用来将 DS4000 磁盘从FCPARRAY 转换至 MPIO ：∙∙∙∙技术级别为 5200-10 且带 5200-10-04 Service Pack 的 AIX 5.2 技术级别为5300-06 且带 5300-06-05 Service Pack 的 AIX 5.3 技术级别为 5300-07 且带 5300-07-02 Service Pack 的 AIX 5.3 技术级别为 6100-00 且带 6100-00-02 Service Pack 的 AIX 6.1下列 DS4000 型号受 AIX MPIO 支持：∙∙∙∙ 1722-600 = DS4300 = FAStT 600 1742-900 = DS4500 = FAStT 900 1814 = DS4700/DS4200 1815 = DS4800要将 DS4000 磁盘从 FCPARRAY 转换至 MPIO，请执行下列步骤：1. 通过完成下列操作来对在 SAN（或直接连接）中使用的 DS4000 存储器的NVSRAM 设置进行更改：注:如果先前已执行此步骤，请转至步骤。
但是，如果已更新 DS4000 固件，那么必须再次执行此步骤。
Redhat 下多路径问题的解决---IBM RDAC
解决Redhat下多路径问题。
就是从存储--光纤交换机--Server，有一个图可以简单的解释这种情况：首先在Redhat网站找到一个关于多路径的软件，和相关技术说明，如下链接：/docs/manuals/csgfs/browse/4.6/DM_Multipath/inde x.html事实上，在IBMDS4800--X3650的环境中，这个软件无法正常收敛多路径。
经过多次尝试，求教IBM人员，方知需安装一个IBM的软件：RDAC。
终于在今天早上得以解决，简单写了个步骤，积累一下：Redhat下多路径解决--IBM RDAC1.到IBM网站下载RDAC软件。
软件版本需考虑几个因素：A.存储机器的型号。
此处为DS4800，可选在DS4000系列。
B.Redhat版本kernel。
此处为Linux 2.6.18-8.el5xen #1 SMP Fri Jan 26 14:29:35 EST 2007 x86_64 x86_64 x86_64 GNU/Linux。
需具体到2.6.18。
在软件下载界面的相关txt文档查找kernel版本。
参考链接：https:///systems/support/supportsite.wss/selectproduct taskind=2&brandind=5000028&familyind=5329626&typeind=0&modelind=0&os ind=0&psid=sr&continue.x=1&matrix=Y#Storage%20Manager2.Down下来之后版本为rdac-LINUX-09.02.C5.13-source.tar.gz上传rdac-LINUX-09.02.C5.13-source.tar.gz到机器上，然后tar zxvfrdac-LINUX-09.02.C5.13-source.tar.gz。
IBM AIX 的子系统设备驱动程序路径控制模块 (SDDPCM) 的安装
IBM AIX 的子系统设备驱动程序路径控制模块 (SDDPCM)的安装子系统设备驱动程序路径控制模块(Subsystem Device Driver Path Control Module，SDDPCM) 是用于使用IBM® System Storage® SAN Volume Controller (SVC)、IBM Storwize® V7000 和其他IBM Storage 产品实现多路径配置环境。
对于与存储设备连接的主机系统，SDDPCM 支持存储冗余的配置环境。
它提供了增强的数据可用性、跨多个路径的动态输入/输出(I/O) 负载平衡以及自动路径故障转移保护。
引言子系统设备驱动程序 (SDD) 是一个软件解决方案，它支持在受支持的存储设备中使用多路径配置环境。
它位于具有本机磁盘设备驱动程序的主机系统中，并提供以下功能：∙增强的数据可用性∙跨多个路径的动态输入/输出(I/O) 负载平衡∙自动路径故障转移保护∙授权计算机代码的并发下载∙在支持的存储上防止出现由主机总线适配器(HBA)、光纤通道(FC) 电缆、以太网电缆或主机接口适配器导致的单点故障回页首硬件先决条件需要以下硬件组件：∙一个或多个受支持的存储设备∙如果使用SAN Volume Controller 的话，则需要一台交换机（SVC 不允许直接连接）∙主机系统∙小型计算机系统接口(SCSI) 适配器和电缆[仅适用于企业存储服务器(ESS)]∙光纤通道适配器和电缆回页首软件先决条件需要以下软件组件：∙AIX 操作系统：从SDD 1.6.1.0（即AIX 5.3 的SDD 程序包devices.sdd.53.rte）开始，需要带有APAR IY76997 的AIX53 TL04。
从SDD 1.6.2.0（即AIX 5.2 的SDD 程序包devices.sdd.52.rte）开始，需要AIX52 TL08 或更高版本，而AIX 5.3 的SDD 程序包devices.sdd.53.rte 则需要AIX53 TL04 或更高版本。
- 1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。
一：查看IBM存储盘的路径
1、查看MPIO的存储盘的路径
# lspath (适用于所有存储的MPIO路径查询）
# mpio_get_config -Av (适用于DS3K/DS4K的MPIO路径查询）
2、查看RDAC存储盘的路径
# fget_config -Av (适用于DS3K/DS4K的RDAC路径查询）
3、查看SDDPCM存储盘的路径
# pcmpath query device (适用于DS6K/DS8K和v7000的SDDPCM路径查询)
4、查看当前操作系统自带的支持IBM存储的多路径软件
# manage_disk_drivers
5、将DS4700默认的多路径软件更改成RDAC
# manage_disk_drivers -d DS4700 -o AIX_fcparray
二：MPIO路径的常用操作
1、查看单个盘的路径
# lspath -l hdisk3
# lspath -F "status name path_id parent connection" | grep -w hdisk3
2、MPIO路径控制
将fcs0卡下的hdisk2的路径禁用
# chpath -l hdisk2 -p fscsi0 -s disable
将fcs0卡下的hdisk2的路径启用
# chpath -l hdisk2 -p fscsi0 -s enable
3、其它参数
# chdev -l hdisk3 -a queue_depth=1 //如果ODM是1.0.1.0以上可以是任何数字
# chdev -l hdisk3 -a hcheck_interval=60 //链路失效检查时间间隔;如果等0，则不会自检
# chdev -l hdisk3 hcheck_mode=nonacive
This parameter specifies which I/O paths should be monitored by the path health checking functionality. nonactive: This mode will check all failed I/O paths and all standby paths of used/opened devices. failed: This mode with check failed I/O paths only.
enabled: This mode will check all enabled I/O paths which are opened.
Note:
Non-opened devices are not monitored. Also, this attribute is
not being used at this time since path health checking is not
enabled. This attribute can be ignored
4、修改链路优先级
lspath -AHE -l hdisk2 -p vscsi3 //查看链路优先级
# chpath -l hdisk3 -p fscsi0 -w 链路1 -a priority=1
# chpath -l hdisk3 -p fscsi0 -w 链路2 -a priority=2
5、处理故障
1)如果发现有很多路径是missing的，可以用cfgmgr重新扫描，如果还有missing的，可以用步骤2和2来激活路径；
2)如果要更换光纤线，可以该卡上的有的路径禁用，换完线后再启用，避免直接拨线产生的风险。