Aix Odm For Mpio User Guide

AIX ODM for MPIO
User Guide
Issue 15
Date 2021-03-01
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2021. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees
or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: https://e.huawei.com
Issue 15 (2021-03-01) Copyright © Huawei Technologies Co., Ltd. i

AIX ODM for MPIO
User Guide About This Document
About This Document
Purpose
This document describes the AIX ODM for MPIO and explains how to configure
and manage AIX ODM for MPIO.
Intended Audience
This document is intended for:
● Technical support engineers

● Maintenance engineers
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Indicates a hazard with a high level of risk which, if not

avoided, will result in death or serious injury.
Indicates a hazard with a medium level of risk which, if not

avoided, could result in death or serious injury.
Indicates a hazard with a low level of risk which, if not

avoided, could result in minor or moderate injury.
Indicates a potentially hazardous situation which, if not

avoided, could result in equipment damage, data loss,
performance deterioration, or unanticipated results.
NOTICE is used to address practices not related to personal
injury.
Supplements the important information in the main text.

NOTE is used to address information not related to personal
injury, equipment damage, and environment deterioration.
Issue 15 (2021-03-01) Copyright © Huawei Technologies Co., Ltd. ii

AIX ODM for MPIO
Conventions
The purchased products, services, and features are stipulated by the commercial
contract made between Huawei and the customer. All or partial products, services
and features described in this document may not be within the purchased scope or
the usage scope. Unless otherwise agreed by the contract, all statements,
information, and recommendations in this document are provided "AS IS" without
warranties, guarantees, or representations of any kind, either express or implied.
As part of an effort to improve and enhance the product performance and
capabilities, Huawei Technologies Co., Ltd. periodically releases revisions of the
hardware and software. Therefore, some functions described in this document may
not be supported by all versions of the software or hardware currently in use. For
the most up-to-date information about product features, refer to the product
release notes.
If a product does not function as described in this document, contact Huawei
technical support engineers.
Change History
Changes between document issues are cumulative. The latest document issue
contains all the changes made in earlier issues.
Issue 15 (2021-03-01)
This is the fifth official release.
Optimized some descriptions in documents.
Issue 14 (2021-01-10)
This is the fourteenth official release.
Issue 13 (2020-10-10)
This is the thirteenth official release.
Issue 12 (2020-06-30)
This is the twelfth official release.
Issue 11 (2019-02-26)
This is the eleventh official release.
Issue 15 (2021-03-01) Copyright © Huawei Technologies Co., Ltd. iii

AIX ODM for MPIO
Issue 10 (2019-01-30)
This is the tenth official release.
Issue 09 (2018-03-01)
This is the ninth official release.
Issue 08 (2017-12-14)
This is the eighth official release.
Issue 07 (2017-06-24)
This is the seventh official release.
Added the functional description of the software optimization
Issue 06 (2017-03-30)
This is the sixth official release.
Added description of configuring the ReserveCheck and ReserveBreak functions.
Issue 05 (2016-09-20)
This is the fifth official release.
Added description of software functions.
Issue 04 (2016-05-20)
This is the fourth official release.
● Updated the AIX ODM for MPIO version to the latest one in the command
output.
● Added the description of the load balancing mode.
Issue 03 (2016-01-30)
This is the third official release.
Issue 02 (2015-10-20)
This is the second official release.
Issue 15 (2021-03-01) Copyright © Huawei Technologies Co., Ltd. iv

AIX ODM for MPIO
Issue 01 (2015-01-30)
This issue is the first official release.
Issue 15 (2021-03-01) Copyright © Huawei Technologies Co., Ltd. v

AIX ODM for MPIO
User Guide Contents
Contents
About This Document................................................................................................................ ii

1 Software Functions................................................................................................................. 1
2 Installation Preparation......................................................................................................... 2
2.1 Environment Requirements................................................................................................................................................. 2
2.2 Checking Disk Space.............................................................................................................................................................. 5
2.3 Deleting the Redundant Disks............................................................................................................................................ 6
2.4 Optional: Checking the SAN Boot Environment Before Installing AIX ODM for MPIO.................................. 7
2.5 Optional: Configuring an HBA Before Installing AIX ODM for MPIO in the SAN Boot Environment........9
3 Installing AIX ODM for MPIO............................................................................................. 10

4 Upgrading AIX ODM for MPIO........................................................................................... 13
5 Uninstalling AIX ODM for MPIO........................................................................................ 14
6 Troubleshooting.....................................................................................................................17
6.1 Deleting Residual Information......................................................................................................................................... 17
6.2 Disks in the Defined State Exist in the System........................................................................................................... 20
6.3 In SAN Boot, Changing Target Ports on the Disk Array Causing AIX Startup Failure................................... 20
6.4 Possible Software Installation Failure in a SAN Boot Environment Where There Are Two or More Paths
Between the Storage Array and the Host............................................................................................................................21
6.5 No OS Image Is Detected After the SAN Boot Environment Restarts................................................................25
6.6 An error occurred during bosboot verification processing Is Prompted When You Install or Uninstall
Software in AIX............................................................................................................................................................................. 26
7 FAQs..........................................................................................................................................29
7.1 What Are Known Bugs That Affect This Software and Corresponding Patches?........................................... 29
7.2 Modifying the Attributes of the fscsi Device............................................................................................................... 30
7.3 How Can I Set a Load Balancing Mode for a Disk?.................................................................................................. 32
7.4 How Can I Configuring the ReserveCheck and ReserveBreak Functions?.........................................................34
7.5 How Do I Use UltraPath for AIX to Replace AIX ODM for MPIO in SAN Boot Scenarios?......................... 35
7.6 How Do I Use System Commands to Query Detailed Information About a LUN? (Applicable to
odmcfg.fcp.MPIO.rte 2.1.8.1 and Later Versions).............................................................................................................. 36
7.7 How Do I Install AIX ODM for MPIO Using the NIM RTE Deployment Mode?.............................................. 38
8 Software Security Feature................................................................................................... 43
Issue 15 (2021-03-01) Copyright © Huawei Technologies Co., Ltd. vi

AIX ODM for MPIO
User Guide Contents
9 Files Related to the ODM.................................................................................................... 44
Issue 15 (2021-03-01) Copyright © Huawei Technologies Co., Ltd. vii

AIX ODM for MPIO
User Guide 1 Software Functions
1 Software Functions
The AIX ODM for MPIO software identifies and takes control of Huawei storage
devices, masks physical disks, and generates virtual disks, but it cannot switch
LUNs' owning controllers. AIX ODM for MPIO supports SAN Boot on controlled
Huawei storage devices.
Issue 15 (2021-03-01) Copyright © Huawei Technologies Co., Ltd. 1

AIX ODM for MPIO
User Guide 2 Installation Preparation
2 Installation Preparation
About This Chapter

This chapter introduces software installation requirements and check items before
the installation.
2.1 Environment Requirements
This section describes the requirements of the software running environment for
the application server.
2.2 Checking Disk Space
This section explains how to check disk space before software installation.
2.3 Deleting the Redundant Disks
This section explains how to delete the redundant disks.
2.4 Optional: Checking the SAN Boot Environment Before Installing AIX ODM for
MPIO
Check the system environment to ensure that AIX ODM for MPIO can be
successfully installed in the SAN Boot environment.
2.5 Optional: Configuring an HBA Before Installing AIX ODM for MPIO in the SAN
Boot Environment
In the AIX 5.3 and AIX 6.1 systems, you need to configure attributes of the fscsi
device in the SAN Boot environment. (In the AIX 7100-00 to 7100-04 and 7200-00
to 7200-03 systems, the default value is used to support SAN Boot.)
2.1 Environment Requirements

This section describes the requirements of the software running environment for
the application server.
Operating System Requirements

1. AIX ODM for MPIO supports the following AIX operating systems.

AIX ODM for MPIO
Version Remarks
5300-03~5300-12 For versions earlier than 5300-08,

you are advised to upgrade the
operating system to 5300-08 or
later.
In the SAN Boot environment:
5300-08 requires patch IZ66562;
5300-12 requires patch IZ65775.
6100-00~6100-09 In the SAN Boot environment:

6100-06 requires patch IZ66023.
7100-00~7100-04 -
7200-00~7200-03 -
NOTE
For details about the AIX operating system version, see Huawei Storage
Interoperability Navigator.
You need to acquire root permission to install AIX ODM for MPIO.
Run the oslevel -s command to check the system version.
bash-3.00# oslevel -s
6100-07-00
2. Do not install UltraPath for AIX, AIX ODM for Non-MPIO, AIX ODM for MPIO,
or AIX ODM for MPIO_RTE before installing AIX ODM for MPIO. Run the
following commands to check whether UltraPath for AIX, AIX ODM for Non-
MPIO, AIX ODM for MPIO, and AIX ODM for MPIO_RTE have been installed.
NOTE
The following uses UltraPath for AIX, AIX ODM for Non-MPIO, and AIX ODM for MPIO
as an example.
● If UltraPath for AIX is installed, uninstall it by referring to "Uninstalling UltraPath"
in the OceanStor UltraPath for AIX User Guide.
● If AIX ODM for Non-MPIO is installed, uninstall it by referring to "Uninstalling AIX
ODM for Non-MPIO" in the AIX ODM for Non-MPIO User Guide.
● If AIX ODM for MPIO is installed, uninstall it by referring to "Uninstalling AIX ODM
for MPIO" in the AIX ODM for MPIO User Guide.
● If the AIX ODM for MPIO_RTE software has been installed, uninstall it by referring
to "Uninstalling AIX ODM for MPIO_RTE" in the AIX ODM for MPIO_RTE User
Guide.

AIX ODM for MPIO
– Run the lslpp -l U*.rte command to check whether UltraPath for AIX is
installed.
bash-3.00# lslpp -l U*.rte
Fileset Level State Description
----------------------------------------------------------------------------
Path: /usr/lib/objrepos
UltraPath.AIX.ppc_64.rte X.X.XXX.X COMMITTED UltraPath for AIX
– Run the lslpp -l odmcfg.fcp.AIX.rte command to check whether AIX

ODM for Non-MPIO is installed.
bash-3.00# lslpp -l odmcfg.fcp.AIX.rte
----------------------------------------------------------------------------
odmcfg.fcp.AIX.rte X.X.X.X COMMITTED AIX Support for Disk Arrays
– Run the lslpp -l odmcfg.fcp.MPIO.rte command to check whether AIX

ODM for MPIO or AIX ODM for MPIO_RTE is installed.
bash-3.00# lslpp -l odmcfg.fcp.MPIO.rte
----------------------------------------------------------------------------
odmcfg.fcp.MPIO.rte X.X.X.X COMMITTED MPIO Support for Disk Arrays
Optional: Operating System Requirements in the SAN Boot Environment

AIX operating system and Virtual I/O Server (VIOS) version requirements in the
SAN Boot N_Port_ID Virtualization (NPIV) environment:
The AIX operating system version is 5300-10 to 5300-12, 6100-03 to 6100-09,
7100-00 to 7100-04, or 7200-00 to 7200-03.
The recommended VIOS version is 2.1.3.10-Fix Pack-23 or 2.2.0.10-Fix Pack-24 to
2.2.6.10.
NOTE
● For details about the AIX operating system version and VIOS version, see Huawei
Storage Interoperability Navigator.
Software Packages
Check whether you have prepared the required software packages. Table 2-1 lists
the software packages.
Table 2-1 Required software packages

Package Software Package Content Description
AIX ODM for Packages and Docs The Packages

MPIO contains the software
installation installation file. The
package Docs contains the
statement of use for
open-source software.

AIX ODM for MPIO
Package Software Package Content Description
AIX ODM for ODM-MPIO- ODM-MPIO-

MPIO X.XX.XXX.AIX.ppc_64.install.bff X.XX.XXX.AIX.ppc_64.
installation install.bff is the
file software installation
file.
NOTICE
In the AIX operating system, the name of the directory where the installation
package resides cannot contain spaces. Otherwise, running installp fails.
SAN Boot Environment Description

When the installation environment is SAN Boot environment, note the following:
1. Before the installation, delete the other Huawei storage disks except system
disks.
2. Restart the host after the installation, so that the software can correctly
manage system disks.
3. The virtual LUN running the host's operating system must be a common
virtual LUN. You can modify a common virtual LUN to a HyperMetro LUN
only after AIX ODM for MPIO software is installed on the host and the host is
restarted.
NOTE
Common virtual LUNs are virtual LUNs except virtual HyperMetro LUNs and virtual
migration LUNs.
2.2 Checking Disk Space

This section explains how to check disk space before software installation.
Context
The space of /opt and /usr directories must be both larger than 10 MB.
NOTE
If the space of either of them is smaller than 10 MB, the software cannot be successfully
installed.
Procedure
Step 1 Run df -m to check the space of /opt and /usr directories.
bash-3.00# df -m
Filesystem MB blocks Free %Used Iused %Iused Mounted on
/dev/hd4 17152.00 10209.42 41% 67463 3% /

AIX ODM for MPIO
/dev/hd2 11648.00 9966.45 15% 36677 2% /usr

/dev/hd9var 2176.00 1990.70 9% 353 1% /var
/dev/hd3 2176.00 1620.12 26% 215 1% /tmp
/dev/fwdump 1152.00 1151.50 1% 4 1% /var/adm/ras/platform
/dev/hd1 30720.00 17189.78 45% 97037 3% /home
/proc - -- - - /proc
/dev/hd10opt 1280.00 1091.34 15% 837 1% /opt
The free space of the /opt and /usr directories is 1091.34 MB and 9966.45 MB
respectively.
----End
2.3 Deleting the Redundant Disks

This section explains how to delete the redundant disks.
Procedure
Step 1 Run lsdev -Cc disk to check whether the redundant disks are found.
# lsdev -Cc disk
hdisk0 Available 1Z-08-00-8,0 16 Bit LVD SCSI Disk Drive
hdisk1 Available 1Z-08-00-9,0 16 Bit LVD SCSI Disk Drive
hdisk2 Available 1A-08-02 Other FC SCSI Disk Drive
Command output description:
● 16 Bit LVD SCSI Disk Drive indicates a local disk on the application server.
● Other FC SCSI Disk Drive indicates a redundant physical disk detected by the
application server when UltraPath for AIX is not installed.
● hdisk0 and hdisk1 are local hard disks on the application server. hdisk2 to
hdisk4 are the redundant physical disks.
Step 2 Run the lscfg -vpl Name command to check the manufacturer's information of
redundant disks. If redundant disks of Huawei storage system exist, run the rmdev
-dl command to delete all redundant physical disks mapped from the storage
system to the application server. If redundant disks of Huawei storage do not exist,
skip this step. Checking the manufacturer's information of hdisk2 is used as an
example.
# lscfg -vpl hdisk2
hdisk2 U787B.001.DNWF39F-P1-C1-T1-W20180022A1073FDD-
L1000000000000 Huawei S5500T FC Disk Drive
Manufacturer................HUAWEI
Machine Type and Model......S5500T
...
PLATFORM SPECIFIC
Name: disk
Node: disk
Device Type: block
If the Manufacturer of a redundant disk is HUAWEI, the redundant disk belongs

to a Huawei array. You need to delete the redundant disk.

AIX ODM for MPIO
NOTICE
● Before running the rmdev -dl command to delete the disks, run the lspv
command to check whether the disks belong to a VG one by one. If a disk
belongs to a VG and is Active, run the varyoffvg command to deactivate the
VG.
● In the SAN Boot environment, you do not need to delete the system disk.
Command format:
rmdev -dl disk_name
Command description:
disk_name indicates the name of a redundant physical disk.
For example:
# rmdev -dl hdisk2
Command output:
hdisk2 deleted
----End
2.4 Optional: Checking the SAN Boot Environment

Before Installing AIX ODM for MPIO
Check the system environment to ensure that AIX ODM for MPIO can be
successfully installed in the SAN Boot environment.
Procedure
Step 1 Run the lslv -m hd5 command to obtain the boot device of the current operating
system. In the following command output, the boot device is hdisk0.
# lslv -m hd5
hd5:N/A
LP PP1 PV1 PP2 PV2 PP3 PV3
0001 0001 hdisk0
Step 2 Run the bootinfo -b command to obtain the boot device of the current operating
system. In the following command output, the boot device is hdisk0.
# bootinfo -b
hdisk0
NOTE
The boot devices obtained by the lslv -m hd5 and bootinfo -b commands must be the
same.
● If the query result of the bootinfo -b command is empty, go to Step 3.
● If the query result of the bootinfo -b command is not empty, go to Step 4.
Step 3 Run the bootlist -m normal -o hdiskX command to configure the boot device
item. In the command, hdiskX is the boot device obtained in Step 1.

AIX ODM for MPIO
# bootlist -m normal -o hdisk0

hdisk0 blv=hd5
NOTE
After the configuration, restart the AIX operating system and go to Step 1 to perform the
check again.
Step 4 Run the ls -l /dev/ipldevice and ls -l /dev/rhdiskX commands to check whether

the device linked to /dev/ipldevice is the boot device. In the command, "rhdiskX"
is the disk drive letter obtained in Step 2.
# ls -l /dev/ipldevice
crw------- 2 root system 22, 0 Dec 24 14:54 /dev/ipldevice
# ls -l /dev/rhdisk0
crw------- 2 root system 22, 0 Dec 24 14:54 /dev/rhdisk0
NOTE
In the command output, the device number of ipldevice (22, 0) and that of rhdiskX (22, 0)
must be the same. If the device numbers are different, run the ln /dev/rhdiskX /dev/
ipldevice command to re-create a boot device link.
Step 5 Run the lsvg -p rootvg command to show the disk used by rootvg.
# lsvg -p rootvg
rootvg:
PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION
hdisk0 active 546 0 00..00..00..00..00
NOTE
In the command output, rootvg uses disk hdisk0.
Step 6 If there is more than one path between the host and the storage device,
redundant physical disks are generated. Then run the lspv command to check
whether there are repeated PVIDs.
# lspv
hdisk0 0001fa696441ac6d rootvg active
The PVIDs read from the same LUN are the same, so the rootvg states of these
physical disks are all active.
● If the lspv command output contains multiple repeated PVIDs, go to Step 7.
● If the lspv command output does not contain any repeated PVIDs, go to Step
8.
Step 7 Run the rmdev -dl hdiskX command to delete the redundant disks rather than
the boot device.
# rmdev -dl hdisk1
hdisk1 deleted
# rmdev -dl hdisk2
hdisk2 deleted
# rmdev -dl hdisk3
hdisk3 deleted
Step 8 Run the bosboot -v command to perform the bosboot command verification. If
the verification is successful, no command output is displayed.
# bosboot -v
#
----End

AIX ODM for MPIO
2.5 Optional: Configuring an HBA Before Installing AIX

ODM for MPIO in the SAN Boot Environment
In the AIX 5.3 and AIX 6.1 systems, you need to configure attributes of the fscsi
device in the SAN Boot environment. (In the AIX 7100-00 to 7100-04 and 7200-00
to 7200-03 systems, the default value is used to support SAN Boot.)
Procedure
Step 1 Run the lsdev -Cc driver|grep fscsi command to obtain the fscsi device in the
current system.
# lsdev -Cc driver|grep fscsi
fscsi0 Available 00-08-01 FC SCSI I/O Controller Protocol Device
fscsi1 Available 09-08-01 FC SCSI I/O Controller Protocol Device
Step 2 Run the chdev -l fscsiX -a dyntrk=yes -P and chdev -l fscsiX -a

fc_err_recov=fast_fail -P commands to modify all attributes of the fscsi device
displayed in Step 1.
# chdev -l fscsi0 -a dyntrk=yes -P
fscsi0 changed
-bash-3.00# chdev -l fscsi1 -a dyntrk=yes -P
fscsi1 changed
-bash-3.00# chdev -l fscsi0 -a fc_err_recov=fast_fail -P
fscsi0 changed
fscsi1 changed
----End

AIX ODM for MPIO
User Guide 3 Installing AIX ODM for MPIO
3 Installing AIX ODM for MPIO
The AIX ODM for MPIO software enables the built-in MPIO of the AIX system to
identify and take over Huawei storage devices and allows SAN Boot to be
performed on Huawei storage devices that have been taken over. This chapter
describes the environment requirements and procedures for installing AIX ODM for
MPIO.
Prerequisites
The application server and storage system meet the operating requirements and
the software package has been prepared.
Procedure
Step 1 Log in to the application server as user root.
Step 2 Use the digital signature verification tool to verify the integrity of the software
package.
NOTE
Download the digital signature verification tool from Huawei technical support website
(https://support.huawei.com/enterprise for enterprises; https://support.huawei.com for
carriers) to verify the integrity of the software package. If the verification fails, contact
technical support engineers to obtain the secure software package.
Step 3 Optional: Check whether the AIX application server on which you want to install
AIX ODM for MPIO is based on the VIOS environment.
1. If the NPIV of the VIOS mechanism is used, AIX ODM for MPIO must be
installed on the client AIX partition.
2. If the vSCSI of the VIOS mechanism is used, AIX ODM for MPIO must be
installed on the VIOS partition. If you log in to the application server as user
padmin, run the oem_setup_env command to enter the oem mode of the
VIOS before the installation.
Step 4 Check whether UltraPath for AIX, AIX ODM for MPIO, or AIX ODM for Non-MPIO
has been installed. For details, see 2.1 Environment Requirements.
Step 5 Decompress the OceanStor_AIX_ODM.zip package on the Windows host. After
the decompression, the AIX_ODM folder is generated.

AIX ODM for MPIO
Step 6 Obtain the MPIO folder from the AIX_ODM folder.

Step 7 Upload the MPIO folder to any directory (for example, the new temporary
directory /ODM_Install) on the AIX application server on which you want to
install AIX ODM for MPIO.
NOTE
The path to the software package cannot contain spaces.
Step 8 Run the cd /ODM_Install/MPIO/Packages command to go to the directory where

the installation package is stored.
Step 9 Run the installp command to install the software.
bash-3.00# installp -acd ODM-MPIO-X.XX.XXX.AIX.ppc_64.install.bff all
+-----------------------------------------------------------------------------+
Pre-installation Verification...
+-----------------------------------------------------------------------------+
Verifying selections...done
Verifying requisites...done
Results...
SUCCESSES
---------
Filesets listed in this section passed pre-installation verification
and will be installed.
Selected Filesets
-----------------
odmcfg.fcp.MPIO.rte X.X.X.X # MPIO Support for Disk Arrays
<< End of Success Section >>
FILESET STATISTICS
------------------
1 Selected to be installed, of which:
1 Passed pre-installation verification
----
1 Total to be installed
0503-409 installp: bosboot verification starting...

installp: bosboot verification completed.
+-----------------------------------------------------------------------------+
Installing Software...
+-----------------------------------------------------------------------------+
installp: APPLYING software for:

odmcfg.fcp.MPIO.rte X.X.X.X
NOTE: On a SAN network, set dyntrk of the HBAs to yes and fc_err_recov to fast_fail.
Finished processing all filesets. (Total time: 11 secs).

0503-408 installp: bosboot process starting...
bosboot: Boot image is 36307 512 byte blocks.

0503-292 This update will not fully take effect until after a
system reboot.
*** ATTENTION ***

System boot image has been updated. You should reboot the
system as soon as possible to properly integrate the changes
and to avoid disruption of current functionality.
installp: bosboot process completed.

+-----------------------------------------------------------------------------+

AIX ODM for MPIO
Summaries:
+-----------------------------------------------------------------------------+
Installation Summary
--------------------
Name Level Part Event Result
-------------------------------------------------------------------------------
odmcfg.fcp.MPIO.rte X.X.X.X USR APPLY SUCCESS
NOTE
The following information is displayed during the software installation:

*** ATTENTION ***
The information is the output of installp and can be ignored.
Step 10 Set fc_err_recov and dyntrk for the FC HBA.

NOTE
● If the operations described in 2.5 Optional: Configuring an HBA Before Installing AIX
ODM for MPIO in the SAN Boot Environment have been performed, skip Step 10 and
go to Step 11.
● In SAN networking, set dyntrk to yes and fc_err_recov to fast_fail for the fscsi logical
device.
● Modify the HBAs connected to Huawei storage only, excluding unused ones.
● IBM has configuration requirements on the Fibre Channel network of an AIX system,
that is, the HBA attributes must be modified. This has nothing to do with the storage
system.
1. Run the lsattr -El fscsiX command to query attributes of the fscsi device
connected to Huawei storage. The following example shows attributes of the
fscsi device in a SAN network.
-bash-3.00# lsattr -El fscsi0
attach switch How this adapter is CONNECTED False
dyntrk yes Dynamic Tracking of FC Devices True
fc_err_recov fast_fail FC Fabric Event Error RECOVERY Policy True
scsi_id 0x10000 Adapter SCSI ID False
sw_fc_class 3 FC Class for Fabric True
2. For details about how to modify attributes of the fscsi device, see 7.2
Modifying the Attributes of the fscsi Device.
Step 11 Optional: In the SAN Boot environment, restart the application server.
----End

AIX ODM for MPIO
User Guide 4 Upgrading AIX ODM for MPIO
4 Upgrading AIX ODM for MPIO
This chapter describes the procedure for upgrading AIX ODM for MPIO.
Prerequisites
● Services on the software-related disks have been stopped.
● The file system has been unmounted.
● All Huawei storage disks have been deleted.
NOTE
You do not need to delete system disks under the SAN Boot environment because the
SAN Boot system runs on Huawei storage and cannot be deleted.
Procedure
Step 1 Uninstall the software of the earlier version by referring to 5 Uninstalling AIX
ODM for MPIO.
Step 2 Install the software of the later version by referring to 3 Installing AIX ODM for
MPIO.
----End

AIX ODM for MPIO
User Guide 5 Uninstalling AIX ODM for MPIO
5 Uninstalling AIX ODM for MPIO
Procedure
Step 1 Log in to the application server.
Step 2 Optional: Check whether the AIX application server on which you want to install
AIX ODM for MPIO is based on the VIOS environment.
1. If the NPIV of the VIOS mechanism is used, AIX ODM for MPIO must be
installed on the client AIX partition.
2. If the vSCSI of the VIOS mechanism is used, AIX ODM for MPIO must be
installed on the VIOS partition. If you log in to the application server as user
padmin, run the oem_setup_env command to enter the oem mode of the
VIOS before the installation.
Step 3 Check whether there are Huawei storage disks.

● Run the lsdev -Cc disk command to check the disks.
# lsdev -Cc disk
hdisk1 Available 04-08-01-8,0 16 Bit LVD SCSI Disk Drive
hdisk2 Available 07-08-01 Other FC SCSI Disk Drive
● Run the lscfg -vpl name command to check whether the disks are Huawei
storage disks.
bash-3.00# lscfg -vpl hdisk2
hdisk2 U788C.001.AAB4099-P1-C14-C2-T1-W20080022A10BB2D5-L1000000000000 Other FC
SCSI Disk Drive
...
PLATFORM SPECIFIC
Name: disk
Node: disk
Device Type: block
NOTE
Manufacturer................HUAWEI: Indicates that the disk is a Huawei storage disk.
Step 4 Determine whether virtual disks need to be deleted. If no, skip this step. If yes, run
the rmdev -dl command to delete virtual disks.

AIX ODM for MPIO
NOTE
● In SAN Boot, run the rmdev -dl name command to delete virtual disks except system
disks.
● In non-SAN Boot, run the rmdev -dl name command to delete virtual disks.
bash-3.00# rmdev -dl hdisk2
hdisk2 deleted
NOTE
Before deleting virtual disks, confirm that no I/Os are being processed on the disks and the
virtual group to which the virtual disks belong is not activated. Otherwise, the virtual disks
cannot be successfully deleted.
Step 5 Check the name of the installed AIX ODM for MPIO software.
Run the lslpp -l odmcfg.fcp.MPIO.rte command to check the name of the
installed AIX ODM for MPIO software.
----------------------------------------------------------------------------
odmcfg.fcp.MPIO.rte X.X.X.X COMMITTED MPIO Support Disk Arrays
Step 6 Uninstall the software.

Run the installp -u program_name command to uninstall the software.
NOTE
program_name indicates the name of AIX ODM for MPIO.

bash-3.00# installp -u odmcfg.fcp.MPIO.rte
+-----------------------------------------------------------------------------+
Pre-deinstall Verification...
+-----------------------------------------------------------------------------+
Verifying selections...done
Verifying requisites...done
Results...
SUCCESSES
---------
Filesets listed in this section passed pre-deinstall verification
and will be removed.
Selected Filesets
-----------------
odmcfg.fcp.MPIO.rte X.X.X.X # MPIO Support for Disk Arrays
<< End of Success Section >>
FILESET STATISTICS
------------------
1 Selected to be deinstalled, of which:
1 Passed pre-deinstall verification
----
1 Total to be deinstalled

+-----------------------------------------------------------------------------+
Deinstalling Software...
+-----------------------------------------------------------------------------+
installp: DEINSTALLING software for:

odmcfg.fcp.MPIO.rte X.X.X.X

AIX ODM for MPIO
Finished processing all filesets. (Total time: 5 secs).

0503-408 installp: bosboot process starting...

0503-292 This update will not fully take effect until after a
system reboot.
*** ATTENTION ***

installp: bosboot process completed.

+-----------------------------------------------------------------------------+
Summaries:
+-----------------------------------------------------------------------------+
--------------------
-------------------------------------------------------------------------------
odmcfg.fcp.MPIO.rte X.X.X.X USR DEINSTALL SUCCESS
NOTE
The following information is displayed during the software uninstallation:

*** ATTENTION ***
The information is the output of installp -u and can be ignored.
Step 7 Optional: Restart the application server under the SAN Boot environment. Clear
residual ODM information following 6.1 Deleting Residual Information after the
AIX system is started. Otherwise, the AIX system may fail to be started during
subsequent installation of UltraPath for AIX.
----End

AIX ODM for MPIO
User Guide 6 Troubleshooting
6 Troubleshooting
6.1 Deleting Residual Information

6.2 Disks in the Defined State Exist in the System
6.3 In SAN Boot, Changing Target Ports on the Disk Array Causing AIX Startup
Failure
After the AIX system is installed in SAN Boot mode, it may fail to start up after
you change the target ports on the disk array.
6.4 Possible Software Installation Failure in a SAN Boot Environment Where There
Are Two or More Paths Between the Storage Array and the Host
6.5 No OS Image Is Detected After the SAN Boot Environment Restarts
6.6 An error occurred during bosboot verification processing Is Prompted When
You Install or Uninstall Software in AIX
6.1 Deleting Residual Information

Context
If AIX ODM for MPIO is uninstalled before the disks taken over by it are deleted,
residual information may be generated in the system. In this case, you need to
delete the residual information.
Procedure
Step 1 Check whether there are Huawei storage disks.
1. Check disks.
Run lsdev -Cc disk to check disks.
bash-3.00# lsdev -Cc disk
lsdev: 0514-521 Cannot find information in the predefined device
configuration database for the customized device hdisk2.
hdisk2 Available 01-08-01 N/A
hdisk3 Available 01-08-01 N/A

AIX ODM for MPIO
2. Check whether the disks that described as N/A are Huawei storage disks, as in
the example hdisk2.
Run lscfg -vpl name to check whether the disks are Huawei storage disks.
bash-3.00# lscfg -vpl hdisk2
0519-004 libodm: The specified search criteria is incorrectly formed.
Make sure the criteria contains only valid descriptor names and
the search values are correct.
hdisk2 U787B.001.DNWGM17-P1-C4-T1-W2210200BC71F822B-L1000000000000 n/a
...
PLATFORM SPECIFIC
Name: disk
Node: disk
Device Type: block
NOTE
Manufacturer................HUAWEI indicates that the disks are Huawei storage disks.

3. If no residual information about Huawei storage disks exists, no further action
is required. If residual information about Huawei storage disks exists and the
AIX system is not restarted after AIX ODM for MPIO is uninstalled, restart the
AIX system.
4. Optional: After restarting the host, delete Huawei storage disks.
a. After restarting the host, run the lsdev -Cc disk command to view disks.
hdisk2 Defined 01-08-01 N/A
hdisk3 Defined 01-08-01 N/A
b. Delete the disks that are reported by Huawei storage after restarting the
host. These disks are described as Other FC SCSI Disk Drive, for example,
hdisk4.
hdisk4 deleted
c. After the disks are deleted, these disks are in Defined state and are
described as N/A, for example, hdisk2.
Step 2 Run odmdelete to delete residual disk information from the ODM library.
1. Delete the residual information from CuAt.
Run odmdelete -o CuAt -q"name=diskname" to delete the residual
information.
NOTE
diskname indicates the name of the disk that has residual information in CuAt.
bash-3.00# odmdelete -o CuAt -q"name=hdisk2"
0518-307 odmdelete: 7 objects deleted.
2. Delete the residual information from CuDv.
Run odmdelete -o CuDv -q"name=diskname" to delete the residual
information.

AIX ODM for MPIO
NOTE
diskname indicates the name of the disk that has residual information in CuDv.
bash-3.00# odmdelete -o CuDv -q"name=hdisk2"
3. Delete the residual information from CuPath.
Run odmdelete -o CuPath -q"name=diskname" to delete the residual
information.
NOTE
diskname indicates the name of the disk that has residual information in CuPath.
bash-3.00# odmdelete -o CuPath -q"name=hdisk2"
4. Delete the residual information from CuPathAt.
Run odmdelete -o CuPathAt -q"name=diskname" to delete the residual
information.
NOTE
diskname indicates the name of the disk that has residual information in CuPathAt.
bash-3.00# odmdelete -o CuPathAt -q"name=hdisk2"
5. Delete the residual information from CuVPD.
Run odmdelete -o CuVPD -q"name=diskname" to delete the residual
information.
NOTE
diskname indicates the name of the disk that has residual information in CuVPD.
bash-3.00# odmdelete -o CuVPD -q"name=hdisk2"
6. Delete the residual information from CuDvDr.
Run odmdelete -o CuDvDr -q value3=diskname to delete the residual
information.
NOTE
diskname indicates the name of the disk that has residual information in CuDvDr.
bash-3.00# odmdelete -o CuDvDr -q value3=hdisk2
7. Run bosboot -a to update the boot image.
bash-3.00# bosboot -a
Step 3 Run rm to delete residual disk information from /dev.

1. Check the residual information.
Run ls -l to check the residual information.
bash-3.00# ls -l /dev/ | grep *hdisk2
brw------- 1 root system 49, 7 Sep 29 22:11 /dev/hdisk2
crw------- 1 root system 49, 7 Sep 29 22:11 /dev/rhdisk2
2. Delete the residual information.
Run rm to delete the residual information.
bash-3.00# rm /dev/hdisk2
bash-3.00# rm /dev/rhdisk2

AIX ODM for MPIO
Step 4 Check whether the residual information has been deleted.

Run lsdev -Cc disk to check whether the residual information has been deleted.
Step 5 Add LUN mappings to an array and run the cfgmgr command on the host to scan
for disks to check whether disks are reported correctly. If disks are reported
correctly, the system environment is cleared successfully. Otherwise, contact
technical support engineers.
----End
6.2 Disks in the Defined State Exist in the System

Context
Some disks in the Defined state exist in the system after software is installed or
uninstalled and the host is restarted because disks are not deleted before the
software is installed or uninstalled. The management personnel must manually
delete these disks. The disks in the Defined state are unavailable.
Procedure
Step 1 Run the lsdev -Cc disk command to view disks.
hdisk2 Defined 01-08-01 Other FC SCSI Disk Drive
In the command output, hdisk2 and hdisk3 are in the Defined state.
Step 2 Run the rmdev -dl disk_name command to delete the disks in the Defined state.
hdisk2 deleted
Step 3 Check whether the disks are deleted.

Run the lsdev -Cc disk command to check whether the disks are deleted.
----End
6.3 In SAN Boot, Changing Target Ports on the Disk

Array Causing AIX Startup Failure
After the AIX system is installed in SAN Boot mode, it may fail to start up after
you change the target ports on the disk array.

AIX ODM for MPIO
Cause
1. In AIX system, each device corresponds to one physical address.
For example, a disk has the following physical address: U788C.001.AAB4099-
P1-C14-C2-T1-W20080022A10BB2D5-L0000000000000. In the address, the
target WWN (20080022A10BB2D5) on the disk array is included.
2. When the AIX system starts up, it will try to find the addresses of boot
devices.
If a target port is changed, for example, from 20080022A10BB2D5 to
20180022A10B848D, the physical address of this boot disk changes to U788C.
001.AAB4099-P1-C14-C2-T1-W20180022A10B848D-L0000000000000.
3. When the AIX system fails to find the boot disk, "No OS image was detected
by firmware" displays.
You view the following error messages through the serial port.
No OS image was detected by firmware.
At least one disk in the bootlist was not found yet.
Firmware is now retrying the entries in the bootlist.
Press ctrl-C to stop retrying.
Solutions
Solution 1: Insert the optical fibre back to the original port.
Solution 2: Use a serial port tool or HMC to go to SMS and manually select the
boot device to start the system.
14. - SAS Tape
(loc=U78AB.001.WZSJJTR-P1-D1 )
15. - SATA CD-ROM
(loc=U78AB.001.WZSJJTR-P3-D7 )
16. - SCSI 59 GB FC Harddisk
(loc=U78AB.001.WZSJJTR-P1-C4-T2-W20180022a10b848d-L0 )
NOTE
In the output, the device whose ID is 16 is the correct boot device.
6.4 Possible Software Installation Failure in a SAN Boot

Environment Where There Are Two or More Paths
Between the Storage Array and the Host
Symptom
During the installation of AIX ODM for Non-MPIO in a SAN Boot environment, the
bosboot -a command is executed. If one of the following command outputs is
displayed, the software installation fails.
The first type of output:
# bosboot -a
0301-150 bosboot: Invalid or no boot device specified!
The second type of output:

# bosboot -a

AIX ODM for MPIO
0301-168 bosboot: The current boot logical volume, /dev/hd5,

does not exist on /dev/hdisk3.
Alarm Information
None.
Possible Causes
During the software installation, the system runs the bosboot command to create
a boot image again. During the execution of bosboot, the boot logical volume
(hd5) of the boot disk will be accessed.
However, in a SAN Boot environment, if there are multiple paths between a host
and a storage array, one LUN will correspond to multiple disks. As a result, during
the execution of bosboot, the boot logical volume (hd5) of the boot disk cannot
be accessed.
The following two cases will cause the failure to access the boot logical volume
(hd5) of the boot disk, leading to the software installation failure.
● When the bootinfo -b command cannot query the boot disk
The bootinfo -b command cannot query the boot disk, and the bootlist -m
normal -o command cannot query the current boot disk.
# bootinfo -b
# bootlist -m normal -o
-
During the execution of bosboot, bootinfo -b is invoked to query the boot
disk. If the returned value is empty, the execution of bosboot -a that is used
to create a boot image fails.
If the command output of lspv indicates that rootvg resides only in one disk
and the other disks do not have a pvid.
# lspv
hdisk0 none None
hdisk1 none None
hdisk2 none None
hdisk3 00f991a3e6eae6bd rootvg active
NOTE
hdisk0 to hdisk3 are disks reported by the same LUN over four paths.
In the preceding scenario, the following incorrect command output will be

displayed after bosboot is executed.
# bosboot -a
After redundant disks that do not have a pvid are deleted, the following command
output will be displayed.
# lspv
After bosboot -a that is used to create a boot image is executed, the following
incorrect command output will be displayed.
# bosboot -a

AIX ODM for MPIO
0301-150 bosboot: Invalid or no boot device specified!

usage: bosboot {-a | -v} [-d device] [-p proto] [-k kernel] [-l lvdev]
[-b file] [-M primary|standby|both] [-D|-I] [-LTq]
Where:
-a Create boot image and write to device or file.
-v Verify, but do not build boot image.
-d device Device for which to create the boot image.
-p proto Use given proto file for RAM disk file system.
-k kernel Use given kernel file for boot image.
-l lvdev Target boot logical volume for boot image.
-b file Use given file name for boot image name.
-D Load kernel debugger.
-I Load and Invoke kernel debugger.
-M primary|standby|both Boot mode - primary or standby.
-T platform Specifies the hardware platform type.
-q Query disk space required to create boot image.
-L Enable MP locks instrumentation.
● When the command output of lslv -m hd5 indicates that the disk where hd5
resides is not the disk queried from the ODM configuration based on the pvid
lspv is first executed to check disk statuses. The pvids read from the same
LUN are the same. Therefore, rootvg in each disk is active.
# lspv
NOTE
hdisk0 to hdisk3 are disks reported by the same LUN over four paths. They have the same
pvid stored in the ODM configuration.
The bosboot command will use the lslv -m hd5 command to query the boot disk,
and compare it with the boot disk queried from the ODM configuration based on
the pvid. If the two disks are not the same one, the execution of bosboot will fail.
In this case, you can run lslv -m hd5 to check whether rootvg is running in
hdisk0.
# lslv -m hd5
hd5:N/A
0001 0001 hdisk0
At this time, if bosboot -a is executed, the following incorrect command output

will be displayed:
# bosboot -a
NOTE
When the bosboot command is executed, the disk that is checked by PVID in ODM is
hdisk3. However, after lslv -m hd5 is used for the check, the logical volume resides on
hdisk0. The two disks are different. As a result, the bosboot command fails to be executed.
Procedure
● If the boot disk cannot be queried by running bootinfo -b, perform the
following steps.
a. Run lslv -m hd5 to obtain the current boot device.
In the following command output, the boot device is hdisk3.

AIX ODM for MPIO
# lslv -m hd5
hd5:N/A
01 0001 hdisk3
b. Run rmdev -dl hdiskX to delete the other disks.

# rmdev -dl hdisk0
hdisk0 deleted
# rmdev -dl hdisk1
hdisk1 deleted
# rmdev -dl hdisk2
hdisk2 deleted
c. Run bootlist -m normal -o hdiskXX to configure the boot device item.

# bootlist -m normal -o hdisk3
hdisk3 blv=hd5
NOTE
hdisk3 is the disk queried in a.

d. Run shutdown -Fr to restart the system.
e. After the system is restarted, run lslv -m hd5 to query the current boot
device. Then, run rmdev -dl hdiskXX to delete non-boot devices.
# lslv -m hd5
hd5:N/A
0001 0001 hdisk3
# rmdev -dl hdisk0
hdisk0 deleted
# rmdev -dl hdisk1
hdisk1 deleted
# rmdev -dl hdisk2
hdisk2 deleted
f. Install the software as instructed in 3 Installing AIX ODM for MPIO.

g. Run shutdown -Fr to restart the system.
● If the command output of lslv -m hd5 indicates that the disk where hd5
resides is not the disk queried from the ODM configuration based on the pvid,
perform the following steps.
a. Run lspv to query disk information.
# lspv
b. Run lslv -m hd5 to query the current boot device.

In the following command output, the boot device is hdisk0.
# lslv -m hd5
hd5:N/A
02 0001 hdisk0
c. Run rmdev -dl hdiskX to delete the other disks.

# rmdev -dl hdisk1
hdisk1 deleted
# rmdev -dl hdisk2
hdisk2 deleted
# rmdev -dl hdisk3
hdisk3 deleted
d. Install the software as instructed in 3 Installing AIX ODM for MPIO.

e. Run shutdown -Fr to restart the system.

AIX ODM for MPIO
6.5 No OS Image Is Detected After the SAN Boot

Environment Restarts
Symptom
After the AIX operating system is installed using the SAN Boot method, it fails to
start up in the SAN Boot mode after being shut down. The following error
message is displayed through the serial port.
No OS image was detected by firmware.
At least one disk in the bootlist was not found yet.
Firmware is now retrying the entries in the bootlist.
Press ctrl-C to stop retrying.
Possible Causes
After the AIX operating system is installed using the SAN Boot method, a change
of physical paths may cause the AIX operating system to fail to start up in the
SAN Boot mode after being shut down.
Fault Diagnosis
1. In the AIX operating system, each device corresponds to one physical address.
For example, a disk has the following physical address:
U788C.001.AAB4099-P1-C14-C2-T1-W20080022A10BB2D5-L0000000000000
In this address, 20080022A10BB2D5 indicates the target WWN of the storage
array.
2. When the AIX operating system is starting up, it tries to find the address of
the boot device.
If a target port is changed, for example, from 20080022A10BB2D5 to
20180022A10B848D, the physical address of this boot disk changes to:
U788C.001.AAB4099-P1-C14-C2-T1-W20180022A10B848D-L0000000000000
3. When the AIX operating system fails to find the boot disk, the "No OS image
was detected by firmware" error message is displayed.
Procedure
Step 1 Log in to the serial port terminal by using the serial port or HMC, manually select
a proper boot device.
14. - SAS Tape

(loc-U78AB.001.WZSJJTR-P1-D1)
15. - SATA CA-ROM
(loc-U78AB.001.WZSJJTR-P3-D7)
16. - SCSI 59 GB FC Harddisk
(loc-U78AB.001.WZSJJTR-P1-C4-T2-W20180022a10b848d-L0
NOTE
The device numbered 16 is the proper boot device.
Step 2 Run the bootlist -m normal -o hdiskX command to go to the system and modify
the system boot list.

AIX ODM for MPIO
bash-3.00#bootlist -m normal -o hdisk4

hdisk4 blv = hd5
----End
6.6 An error occurred during bosboot verification

processing Is Prompted When You Install or Uninstall
Software in AIX
Symptom
An error occurred during bosboot verification processing may be prompted
when you install or uninstall software in the AIX operating system, causing
installation or uninstallation failure. The error information is as follows:
FILESET STATISTICS
------------------
1 Selected to be deinstalled, of which:
1 Passed pre-deinstall verification
----
1 Total to be deinstalled
0503-497 installp: An error occurred during bosboot verification processing.
Possible Causes
Possible causes for failure in executing the bosboot command include:
● The operating system is booted from an EMC PowerPath device, namely, the
startup disk is hdiskpowerX.
● The boot device of the current operating system cannot be queried by running
bootinfo -b.
● The /dev/ipldevice file does not exist or the /dev/ipldevice file is inconsistent
with the boot disk.
● The PVID of the disk where hd5 belongs is not unique.
Procedure
Step 1 Run lslv -m hd5 to query the booth disk of the current operating system.
● As shown in the following example, the operating system is running on
hdisk8.
bash-3.00# lslv -m hd5
hd5:N/A
0001 0001 hdisk8
● As shown in the following example, the operating system is running on
hdiskpower1. In this case, run pprootdev fix to make the bosboot command
function properly.
bash-3.00# lslv -l hd5
hd5:N/A
PV COPIES IN BAND DISTRIBUTION
hdiskpower1 001:000:000 100% 001:000:000:000:000
bash-3.00# pprootdev fix

AIX ODM for MPIO
You may now run bosboot.

PowerPath boot remains enabled for the next system boot.
Step 2 Run bootinfo -b to query the boot disk of the current operating system.
● As shown in the following example, the boot disk of the current operating
system is hdisk8.
bash-3.00# bootinfo -b
hdisk8
● As shown in the following example, the boot disk of the current operating
system is null.
bash-3.00# bootinfo -b
bash-3.00#
In this case, run bootlist -m normal -o hdiskXX to configure the boot device.
In the command, hdiskXX indicates the boot disk obtained by running lslv -m
hd5. Then run shutdown -Fr to restart the operating system.
bash-3.00# bootlist -m normal -o hdisk8
hdisk8 blv=hd5
bash-3.00# shutdown -Fr
Step 3 Run ls -l /dev/ipldevice to check whether the /dev/ipldevice file exists.

● As shown in the following example, the /dev/ipldevice file does not exist.
bash-3.00# ls -l /dev/ipldevice
ls: 0653-341 The file /dev/ipldevice does not exist.
If the /dev/ipldevice file does not exist, run ln /dev/rhdiskX /dev/ipldevice

to rebuild the link between the boot disk and the /dev/ipldevice file, as
shown in the following figure.
bash-3.00# ln /dev/rhdisk8 /dev/ipldevice
● As shown in the following example, the /dev/ipldevice file exists.

crw------- 2 root system 13, 3 May 13 14:57 /dev/ipldevice
Step 4 Run ls -l /dev/ipldevice to check whether the /dev/ipldevice file matches with the
booth disk. If the /dev/ipldevice file is consistent with the primary and secondary
device numbers of the boot disk (13 and 3 respectively in the following example),
the /dev/ipldevice file matches with the boot disk.
crw------- 2 root system 13, 3 May 13 14:57 /dev/ipldevice
bash-3.00# ls -l /dev/rhdisk8
crw------- 2 root system 13, 3 May 13 14:57 /dev/rhdisk8
If they do not match, run ln /dev/rhdiskX /dev/ipldevice to rebuild the link

between the boot disk and the /dev/ipldevice file.
Step 5 Run lspv to check whether the PVID of the boot disk is unique. In the following
example, the PVID is not unique.
bash-3.00# lspv
hdisk0 00f9c44c34aa0fb8 None
hdisk1 00f9c44c02b74191 old_rootvg
hdisk8 00f9c44c91fa6e37 rootvg active
hdisk9 00f9c44c91fa6e37 rootvg active
The PVID is not unique, run rmdev -dl hdiskX to delete the non-boot disk.
Step 6 Specifying the device update boot mirror
ash-3.00# bosboot -ad /dev/ipldevice

bash-3.00# bosboot -ad /dev/hdisk8

AIX ODM for MPIO
Step 7 Synchronizing VG information

bash-3.00# syncvg -v rootvg
bash-3.00# synclvodm -Pv rootvg
synclvodm: Physical volume data updated.
synclvodm: Logical volume hd5 updated.
synclvodm: Logical volume hd9var updated.
synclvodm: Logical volume hd10opt updated.
synclvodm: Logical volume hd11admin updated.
synclvodm: Logical volume livedump updated.
----End

AIX ODM for MPIO
User Guide 7 FAQs
7 FAQs
About This Chapter

This chapter provides answers to frequently asked questions (FAQs) during AIX
ODM for MPIO configuration and management. You can refer to this chapter for
troubleshooting if necessary.
7.1 What Are Known Bugs That Affect This Software and Corresponding Patches?
7.2 Modifying the Attributes of the fscsi Device
7.3 How Can I Set a Load Balancing Mode for a Disk?
7.4 How Can I Configuring the ReserveCheck and ReserveBreak Functions?
7.5 How Do I Use UltraPath for AIX to Replace AIX ODM for MPIO in SAN Boot
Scenarios?
7.6 How Do I Use System Commands to Query Detailed Information About a
LUN? (Applicable to odmcfg.fcp.MPIO.rte 2.1.8.1 and Later Versions)
7.7 How Do I Install AIX ODM for MPIO Using the NIM RTE Deployment Mode?
7.1 What Are Known Bugs That Affect This Software

and Corresponding Patches?
Question
What are known bugs that affect this software and corresponding patches?
Answer
The following describes the known system bugs that may cause SAN Boot failure
and corresponding patches:
● Bug description:
A REBOOT MAY RESULT IN RANDOM MPIO PATHS IN A MISSING STATE
● Patch information:
5300-08 maps to patch IZ66562; 5300-09 maps to patch IZ64005; 5300-10
maps to patch IZ64011; 5300-11 maps to patch IZ65325; 5300-12 maps to

AIX ODM for MPIO
User Guide 7 FAQs
patch IZ65775; 6100-01 maps to patch IZ71807; 6100-02 maps to patch

IZ64000; 6100-03 maps to patch IZ63159; 6100-04 maps to patch IZ64133;
6100-05 maps to patch IZ65870; 6100-06 maps to patch IZ66023.
7.2 Modifying the Attributes of the fscsi Device

Question
How do you modify the dyntrk and fc_err_recov parameters for the fscsi device?
Answer
There are three methods to modify the dyntrk and fc_err_recov parameters of the
fscsi device. Select a proper method based on actual conditions.
● Method 1
If the host can be restarted, use method 1 to modify the parameters.
a. Run the chdev -l fscsiX -a dyntrk=yes -P and chdev -l fscsiX -a
fc_err_recov=fast_fail -P commands to modify the attributes of all HBAs
that connect to switches.
-bash-3.00# chdev -l fscsi0 -a dyntrk=yes -P
fscsi0 changed
fscsi0 changed
b. Restart the host to make the modification take effect.

● Method 2
If the fscsi device connected to Huawei storage has no virtual disks or has
virtual disks that can be deleted, use method 2. If it has virtual disks that
cannot be deleted or may not be deleted, use method 3 instead.
a. Run the rmdev -l fscsiX -R command to set the states of all fscsi devices
connected to Huawei storage to defined.
-bash-3.00# rmdev -l fscsi0 -R
fscsi0 Defined
b. Run the chdev -l fscsiX -a dyntrk=yes and chdev -l fscsiX -a

fc_err_recov=fast_fail commands to modify the attributes of all fscsi
devices connected to Huawei storage.
-bash-3.00# chdev -l fscsi0 -a dyntrk=yes
fscsi0 changed
-bash-3.00# chdev -l fscsi0 -a fc_err_recov=fast_fail
fscsi0 changed
c. Run the cfgmgr -l fscsiX command to reconfigure all fscsi devices

connected to Huawei storage.
-bash-3.00# cfgmgr -l fscsi0
-bash-3.00#
● Method 3
If the reported virtual disks of Huawei storage are connected to multiple fscsi
devices, use method 3 (no virtual disks need to be deleted). If there is only
one fscsi device connected to Huawei storage, use method 1 or 2.
a. Run the lspath command to confirm the fscsi device in use. In the
following figure, hdisk1 and hdisk2 are virtual disks of Huawei storage,
which are connected to fscsi0 and fscsi1.

AIX ODM for MPIO
User Guide 7 FAQs
-bash-3.00# lspath
Enabled hdisk0 scsi0
Enabled hdisk1 fscsi0
NOTE
The previous screen message indicates that hdisk1 and hdisk2 are virtual disks
of Huawei storage, and they are connected to fscsi0 and fscsi1.
b. Run the rmdev -l fscsi0 -R command to set the state of fscsi0 to defined.
fscsi0 Defined
c. Run the chdev -l fscsi0 -a dyntrk=yes and chdev -l fscsi0 -a

fc_err_recov=fast_fail commands to modify the attributes of fscsi0.
fscsi0 changed
fscsi0 changed
d. Run the cfgmgr -l fscsi0 command to reconfigure fscsi0.

-bash-3.00#
e. Run the lspath command to ensure that all disk paths are normal.
-bash-3.00# lspath
f. Run the rmdev -l fscsi1 -R command to set the state of fscsi1 to defined.
fscsi1 Defined
g. Run the chdev -l fscsi1 -a dyntrk=yes and chdev -l fscsi1 -a

fc_err_recov=fast_fail commands to modify the attributes of fscsi1.
fscsi1 changed
fscsi1 changed
h. Run the cfgmgr -l fscsi1 command to reconfigure fscsi1.

-bash-3.00#
i. Run the lspath command to ensure that all disk paths are normal.
-bash-3.00# lspath

AIX ODM for MPIO
User Guide 7 FAQs
7.3 How Can I Set a Load Balancing Mode for a Disk?

Question
How can I set a load balancing mode for a disk?
Answer
The ODM software supports three load balancing modes: fail_over, round_robin,
and shortest_queue. For 31.0.RC16, the default mode is round_robin. For other
versions, the default mode is fail_over.
● The fail_over mode enables application servers to deliver I/Os over the
available path with the highest priority if the current path is marked as failed
or disabled.
NOTE
● The path priority depends on the value of the priority parameter. A smaller value of the
priority parameter indicates a higher priority. The value of the priority parameter
ranges from 1 to 255. If the value of the priority parameter is set to 1, the path priority
is the highest. If the value of the priority parameter is set to 255, the path priority is the
lowest.
● By default, the value of the priority parameter is 1.
● For the round_robin mode, when an application server delivers I/Os to a
storage system for the first time, the I/Os are transferred through path 1.
When the I/Os are delivered for the secondary time, path 2 is used. The paths
that will be used are deduced by analogy. Paths are used in turn to ensure
that each path is fully utilized.
● For the shortest_queue mode, when an application server delivers I/Os to a
storage system, the I/Os are transferred through a path that currently has the
fewest I/Os. If the transfer speed of a path is slow, the other paths whose
transfer speed is quick can be fully utilized.
NOTE
This mode can only be set in some operating systems that adopt the latest technologies.
For details, see the official website of IBM.
To set a load balancing mode for a disk, do as follows:

1. Query the disk properties.
Run the lsattr -El hdiskx command to query the disk properties (hdisk1 as an
example). The value of the algorithm field indicates the path selection
algorithm. For 31.0.RC16, the default mode is round_robin. For other versions,
the default mode is fail_over.
-bash-3.00# lsattr -El hdisk1
PCM PCM/friend/MPIOpcm Path Control Module False
PR_key_value none Persistant Reserve Key Value True
algorithm fail_over Algorithm True
clr_q no Device CLEARS its Queue on error True
dist_err_pcnt 0 Distributed Error Percentage True
dist_tw_width 50 Distributed Error Sample Time True
hcheck_cmd test_unit_rdy Health Check Command True
hcheck_interval 30 Health Check Interval True

AIX ODM for MPIO
User Guide 7 FAQs
hcheck_mode nonactive Health Check Mode True

location Location Label True
lun_id 0x1000000000000 Logical Unit Number ID False
lun_reset_spt yes LUN Level Reset True
max_transfer 0x40000 Maximum TRANSFER Size True
node_name 0x21000022a1073fdd FC Node Name False
pvid 00007e1d562bd42d0000000000000000 Physical volume identifier False
q_err yes Use QERR bit True
q_type simple Queuing TYPE True
queue_depth 32 Queue DEPTH True
reassign_to 120 REASSIGN time out value True
reserve_policy no_reserve Reserve Policy True
rw_timeout 30 READ/WRITE time out value True
scsi_id 0x10400 SCSI ID False
start_timeout 60 START unit time out value True
ww_name 0x20190022a1073fdd FC World Wide Name False
2. Set a load balancing mode for the disk.

– Run the chdev -l hdisk1 -a algorithm=round_robin command to set the
load balancing mode of the disk to round_robin.
– Run the chdev -l hdisk1 -a algorithm=fail_over command to set the load
balancing mode of the disk to fail_over.
– Run the chdev -l hdisk1 -a algorithm=shortest_queue command to set
the load balancing mode of the disk to shortest_queue.
3. Optional: If the load balancing mode is fail_over, set path priorities.
a. Query path priorities.
i. Run the lspath -F"name:parent:connection:path_id:status" command
to query path priorities. The command output is as follows:
-bash-3.00# lspath -F"name:parent:connection:path_id:status" hdisk0:scsi1:8,0:0:Enabled
hdisk1:fscsi0:20080022a10bb2d5,1000000000000:0:Enabled
ii. Run the lspath -l hdiskx -a priority -F value -p fscsix -w connection

command to check the priority of a specified path.

AIX ODM for MPIO
User Guide 7 FAQs
-bash-3.00# lspath -l hdisk1 -a priority -F value -p fscsi0 -w

20080022a10bb2d5,1000000000000 1
b. Set path priorities.
Run the chpath -l hdiskx -a priority=x -p fscsi0 -w connection command
to modify the priority of a specified path. The priority value ranges from
1 to 255 and 1 indicates the highest priority.
-bash-3.00# chpath -l hdisk1 -a priority=255 -p fscsi0 -w 20080022a10bb2d5,1000000000000
path Changed
-bash-3.00# lspath -l hdisk1 -a priority -F value -p fscsi0 -w 20080022a10bb2d5,1000000000000
255
7.4 How Can I Configuring the ReserveCheck and

ReserveBreak Functions?
Question
How can I configuring the ReserveCheck and ReserveBreak functions?
Answer
The odmget -q name = xxxx CuDv and smit hacmp commands are used to
configure the ReserveCheck and ReserveBreak functions. The name indicates
device name. If one node fails, another node automatically invokes ReserveCheck
and ReserveBreak to take over the resources on the failed node.
NOTE
Before configuring these functions, ensure that the HACMP software has been installed.
Perform the following steps to configure the ReserveCheck and ReserveBreak

functions:
1. Run odmget -q name = xxxx CuDv to obtain the disk type.
2. Run smit hacmp.
3. On the HACMP for AIX configuration page, choose Extended Configuration
> Extended Resource Configuration > HACMP Extended Resources
Configuration > Configure Custom Disk Methods > Add Custom Disk
Methods.
4. On the following output, enter the disk type in New Disk Type.
[Entry Fields]
* New Disk Type []
* Method to identify ghost disks
[SCSI3] +
* Method to determine if a reserve is held [/usr/sbin/
ReserveCheck] +
* Method to break a reserve [/usr/sbin/
ReserveBreak] +
Break reserves in parallel
false +
* Method to make the disk available [MKDEV]
5. Press Enter to finish configuring the ReserveCheck and ReserveBreak
functions.
For example, configure the ReserveCheck and ReserveBreak functions for hdisk2
(the disk type is disk/fcp/HWS5300).

AIX ODM for MPIO
User Guide 7 FAQs
# odmget -q 'name = hdisk2' CuDv

CuDv:
name = "hdisk2"
status = 1
chgstatus = 0
ddins = "scsidisk"
location = "1D-08-02"
parent = "fscsi1"
connwhere = "W_0"
PdDvLn = "disk/fcp/HWS5300"
# smit hacmp
[Entry Fields]
* New Disk Type [disk/fcp/HWS5300]
* Method to identify ghost disks [SCSI3]+
* Method to determine if a reserve is held [/usr/sbin/ReserveCheck] +
* Method to break a reserve [/usr/sbin/ReserveBreak] +
Break reserves in parallel false +
* Method to make the disk available [MKDEV]
7.5 How Do I Use UltraPath for AIX to Replace AIX

ODM for MPIO in SAN Boot Scenarios?
Question
How do I use UltraPath for AIX to replace AIX ODM for MPIO in SAN boot
scenarios?
Answer
1. Uninstall AIX ODM for MPIO following 5 Uninstalling AIX ODM for MPIO
and restart the AIX system.
2. After the AIX system is started, run bootlist -m normal -o hdiskXX to set the
boot list and run shutdown -Fr to restart the AIX system. You can run lslv -m
hd5 to query hdiskXX. For example:
bash-3.00# lslv -m hd5
hd5:N/A
0001 0001 hdisk9
bash-3.00# bootlist -m normal -o hdisk9
hdisk9 blv=hd5
bash-3.00#
bash-3.00# shutdown -Fr
SHUTDOWN PROGRAM
Tue Apr 11 11:48:02 CDT 2017
3. After the AIX system is started, run lsdev -Cc disk to check the residual
defined and N/A disks. For example:
hdisk0 Available Virtual SCSI Disk Drive
hdisk1 Available C4-T1-01 Other FC SCSI Disk Drive
hdisk8 Defined C4-T1-01 N/A
hdisk8 is the residual disk information.

AIX ODM for MPIO
User Guide 7 FAQs
4. Delete the residual disk information and run the following commands for the
disk:
odmdelete -o CuDv -q name=hdiskX
odmdelete -o CuAt -q name=hdiskX
odmdelete -o CuPath -q name=hdiskX
odmdelete -o CuPathAt -q name=hdiskX
odmdelete -o CuVPD -q name=hdiskX
odmdelete -o CuDvDr -q value3=hdiskX
Run bosboot -a to update the boot image. For example:
bash-3.00# odmdelete -o CuDv -q name=hdisk8
bash-3.00# odmdelete -o CuAt -q name=hdisk8
bash-3.00# odmdelete -o CuPath -q name=hdisk8
bash-3.00# odmdelete -o CuPathAt -q name=hdisk8
bash-3.00# odmdelete -o CuVPD -q name=hdisk8
bash-3.00# odmdelete -o CuDvDr -q value3=hdisk8
bash-3.00# bosboot -a

5. Run sh install.sh to install UltraPath. Restart the AIX system after the
installation.
6. If the AIX system fails to be started, go to the single user mode and run lsdev
-Cc disk to check whether a defined disk exists. Run rmdev -dl hdiskXX to
remove the defined disk. Execute bootlist -m normal -o hdiskXX to specify a
boot device and run bosboot -a. Restart the AIX system.
For details about how to go to the single user mode, refer to http://
www-01.ibm.com/support/docview.wss?uid=isg3T1011796.
7.6 How Do I Use System Commands to Query Detailed

Information About a LUN? (Applicable to
odmcfg.fcp.MPIO.rte 2.1.8.1 and Later Versions)
Question
How do I use system commands to query detailed information about a LUN?
(applicable to odmcfg.fcp.MPIO.rte 2.1.8.1 and later versions)
Answer
1. Run the lslpp -l odmcfg.fcp.MPIO.rte command to check the version of the
installed AIX ODM for MPIO software.
----------------------------------------------------------------------------
odmcfg.fcp.MPIO.rte X.X.X.X COMMITTED MPIO Support Disk Arrays
X.X.X.X indicates the software version.
2. In AIX ODM for MPIO, you can use lscfg -vpl Name to query detailed
information about a LUN. The following uses the command to query detailed
information about hdisk1.

AIX ODM for MPIO
User Guide 7 FAQs
-bash-3.00# lscfg -vpl hdisk1

hdisk1 U787B.001.DNWF39F-P1-C1-T1-W20180022A1073FDD-L2000000000000 HUAWEI
MPIO FC Disk Drive
Serial Number...............210235G6KCZ0B8000009
Device Specific.(Z0)........60022A1100073FDD0002A0A800000001
Device Specific.(Z1)........Lun_002
Device Specific.(Z2)........00000001
PLATFORM SPECIFIC
Name: disk
Node: disk
Device Type: block
-bash-3.00#
Table 7-1 describes the command output. Due to restrictions of the operating
system, only single-end information can be displayed for active-active LUNs.
Table 7-1 Parameter description

Parameter Description
Manufacturer Vendor ID, indicates the vendor

name.
Machine Type and Model Product ID, indicates the product

model.
Serial Number Indicates the SN of the disk array

connected to the LUN.
NOTE
The following storage system models
and versions do not support SN query:
● Versions earlier than S2300E/S2600,
S5300/S5500/S5600, Dorado2100,
and Dorado5100
V100R001C00SPC800 (excluding
V100R001C00SPCa00 and
V100R001C00SPCb00)
● Versions earlier than Dorado2100 G2
V100R001C00SPC500 (excluding
V100R001C00SPCa00 and
V100R001C00SPCb00)
● Versions earlier than S2200T/
S2600T/S5500T/S5600T/S5800T/
S6800T V1R5C00SPC400
● Versions earlier than S2200T/
S2600T/S5500T/S5600T/S5800T/
S6800T V1R5C01SPC100
Device Specific.(Z0) Indicates LUN WWN.

AIX ODM for MPIO
User Guide 7 FAQs
Parameter Description
Device Specific.(Z1) Indicates LUN name.

NOTE
If the LUN name contains Chinese
characters, Chinese characters cannot be
displayed.
Device Specific.(Z2) Dev LUN ID, Indicates the ID of the

LUN corresponding to the virtual
LUN in the storage system.
NOTE
● Dev LUN ID is a hexadecimal
number.
● In active-active scenarios, the
displayed Dev LUN ID and array SN
may come from storage arrays at
different ends.
7.7 How Do I Install AIX ODM for MPIO Using the NIM
RTE Deployment Mode?
Question
How do I install AIX ODM for MPIO using the NIM RTE deployment mode?
Answer
If you need to use the NIM RTE deployment mode to install AIX ODM for MPIO,
use the AIX ODM for MPIO RTE software package, which is dedicated for the NIM
RTE deployment mode. If the NIM RTE deployment mode is used, after the
lpp_source and spot resources are created, add the AIX ODM for MPIO RTE
software package to the lpp_source and spot resources, and then install the AIX
operating system. The procedure is as follows:
1. Add the AIX ODM for MPIO RTE software package to the lpp_source resource.
a. Run the smit nim command to access the management page, and then
select Perform NIM Administration Tasks.
Move cursor to desired item and press Enter.
Configure the NIM Environment

Perform NIM Software Installation and Maintenance Tasks
Perform NIM Administration Tasks
Create IPL ROM Emulation Media
NIM POWER5 Tools
Thin Server Maintenance
b. Select Manage Resources.

Manage Networks
Manage Machines
Manage Control Objects
Manage Resources

AIX ODM for MPIO
User Guide 7 FAQs
Manage Groups
Backup/Restore the NIM Database
Configure NIM Environment Options
Rebuild the niminfo File on the Master
Change the Master's Primary Interface
Manage Alternate Master Environment
Unconfigure NIM
c. Select Perform Operations on Resources.

List All Network Install Resources

Define a Resource
Change/Show Characteristics of a Resource
Show the Contents of a Resource
Remove a Resource
Perform Operations on Resources
Verify Resources
d. Select the lpp_source resource that has been created.

+--------------------------------------------------------------------------+
| Resource Name |
| |
| Move cursor to desired item and press Enter. |
| |
| lpp_source resources lpp_source |
| spot resources spot |
| |
| F1=Help F2=Refresh F3=Cancel |
| F8=Image F10=Exit Enter=Do |
| /=Find n=Find Next |
+--------------------------------------------------------------------------+
e. Select update to update the created lpp_source resource.

+--------------------------------------------------------------------------+
| Network Install Operation to Perform |
| |
| |
| showres = show contents of a resource |
| lslpp = list LPP information about an object |
| check = check the status of a NIM object |
| lppmgr = eliminate unnecessary software images in an lpp_source |
| update = add or remove software to or from an lpp_source |
| |
+--------------------------------------------------------------------------+
f. Select Add or Remove Software, and then select add.

Type or select a value for the entry field.
Press Enter AFTER making all desired changes.
[Entry Fields]
Add or Remove Software add
g. Select Media, directory or lpp_source to copy images from and enter

the directory for storing the AIX ODM for MPIO RTE software package,
for example, /home.
Type or select a value for the entry field.
[Entry Fields]
Media, directory or lpp_source to copy images from [/home]
h. Select SOFTWARE Packages to Add, press F4 to list all software

packages, select the AIX ODM for MPIO RTE software package to be
added, and execute the command.

AIX ODM for MPIO
User Guide 7 FAQs
Type or select values in entry fields.

[Entry Fields]
TARGET lpp_source lpp_source_720
SOURCE of Software to Add /home
SOFTWARE Packages to Add [odmcfg 2.1.12.1
I]
-OR-
INSTALLP BUNDLE containing packages to add
[]
gencopy Flags
DIRECTORY for temporary storage during copying [/tmp]
EXTEND filesystems if space needed?
yes
Process multiple volumes? yes
i. If the following information is displayed, the command is successfully

executed:
Command: OK stdout: yes stderr: no
Before command completion, additional instructions may appear below.
/export/lpp_source/lpp_source/installp/ppc/odmcfg.2.1.12.1.I.1
2. Add the AIX ODM for MPIO RTE software package to the spot resource.
a. Run the nim -o cust -a filesets=odmcfg.fcp.MPIO.rte -a
lpp_source=[LPP_SOURCE_NAME] [SPOT_NAME] command to add the
required AIX ODM for MPIO RTE software package to the created spot
resource.
-bash-3.00# nim -o cust -a filesets=odmcfg.fcp.MPIO.rte -a lpp_source=lpp_source spot
b. If the following information is displayed, the command is successfully

executed:
+-----------------------------------------------------------------------------+
Summaries:
+-----------------------------------------------------------------------------+
--------------------
-------------------------------------------------------------------------------
odmcfg.fcp.MPIO.rte 2.1.12.1 USR APPLY SUCCESS
Checking filesets and network boot images for SPOT "spot".

This may take several minutes ...
3. Run the following commands to check whether the AIX ODM for MPIO RTE
software package is successfully added to the lpp_source and spot resources:
– Check the lpp_source resource and ensure that the odmcfg.fcp.MPIO.rte
resource exists.
-bash-3.00# nim -o showres lpp_source|grep -i "odmcfg.fcp.MPIO.rte"
odmcfg.fcp.MPIO.rte 2.1.12.1 I b usr
– Check the spot resource and ensure that the odmcfg.fcp.MPIO.rte

resource exists.
-bash-3.00# nim -o showres spot|grep -i "odmcfg.fcp.MPIO.rte"
odmcfg.fcp.MPIO.rte 2.1.12.1 C F MPIO Support for Disk Arrays
4. After the lpp_source and spot resources are added successfully, you can use
the NIM RTE deployment mode to install AIX ODM for MPIO.

AIX ODM for MPIO
User Guide 7 FAQs
a. Run the smit nim command to access the management interface, and
then select Perform NIM Software Installation and Maintenance
Tasks.
Configure the NIM Environment

Perform NIM Software Installation and Maintenance Tasks
Perform NIM Administration Tasks
Create IPL ROM Emulation Media
NIM POWER5 Tools
Thin Server Maintenance
b. Select Install and Update Software.

Install and Update Software

List Software and Related Information
Installation Inventory
Software Maintenance and Utilities
Alternate Disk Installation
Manage Diskless/Dataless Machines
Manage Workload Partition Machines
c. Select Install the Base Operating System on Standalone Clients.

Install the Base Operating System on Standalone Clients

Install Software
Update Installed Software to Latest Level (Update All)
Install Software Bundle
Update Software by Fix (APAR)
Install and Update from ALL Available Software
d. Select the AIX client where the software is to be installed.

+--------------------------------------------------------------------------+
| Select a TARGET for the operation |
| |
| |
| aix machines standalone |
| |
+--------------------------------------------------------------------------+
e. Select the rte deployment mode.

+--------------------------------------------------------------------------+
| Select the installation TYPE |
| |
| |
| rte - Install from installation images |
| mksysb - Install from a mksysb |
| spot - Install a SPOT copy |
| |
+--------------------------------------------------------------------------+
f. Select the lpp_source resource that has been created.

+--------------------------------------------------------------------------+
| Select the LPP_SOURCE to use for the installation |
| |
| |
| lpp_source resources lpp_source |
| |

AIX ODM for MPIO
User Guide 7 FAQs

+--------------------------------------------------------------------------+
g. Select the spot resource that has been created.

+--------------------------------------------------------------------------+
| Select the SPOT to use for the installation |
| |
| |
| spot resources spot |
| |
+--------------------------------------------------------------------------+
h. On the Install the Base Operating System on Standalone Clients

interface, press F4 to select odmcfg.fcp.MPIO.rte in Additional FILESETS
to install. Ensure that the values of all ACCEPT new license agreements
are yes.
Additional FILESETS to install [odmcfg.fcp.MPIO.rte]
ACCEPT new license agreements? [yes]

AIX ODM for MPIO
User Guide 8 Software Security Feature
8 Software Security Feature
This chapter describes software security feature.

● Only user root can install and uninstall software.
● Install and uninstall logs can be accessed by user root only.
● Ports are not listened and personnel data and sensitive data are not accessed.

AIX ODM for MPIO
User Guide 9 Files Related to the ODM
9 Files Related to the ODM
After the ODM is correctly installed on a AIX operating system, the ODM adds and
modifies certain files that ensure its proper running. Do not modify or delete these
files unnecessarily.
Files Added to the ODM

File Name Path Description
setup.log /opt/ODM Install or uninstall the

log file of the ODM
package.
/opt/ODM /opt/ODM Install or uninstall the

log storage directory of
the ODM package.
ReserveCheck /usr/sbin File for querying the

reserved information of
Huawei disk devices.
ReserveBreak /usr/sbin File for clearing the

reserved information of
Huawei disk devices.
hw_odm_server /usr/sbin Binary file for clearing

Huawei disk devices in
defined state
File Modified by the ODM

After the ODM package is installed, the updated system files are as follows:
/etc/objrepos/CDiagDev
/etc/objrepos/CDiagAtt.vc
/etc/objrepos/CDiagAtt
/etc/objrepos/SWservAt.vc

AIX ODM for MPIO
/etc/objrepos/SWservAt
/etc/objrepos/CuVPD
/etc/objrepos/CuPathAt.vc
/etc/objrepos/CuPathAt
/etc/objrepos/CuPath.vc
/etc/objrepos/CuPath
/etc/objrepos/CuDvDr
/etc/objrepos/CuDv
/etc/objrepos/CuDep
/etc/objrepos/CuAt.vc
/etc/objrepos/CuAt
/etc/objrepos/lpp.vc
/etc/objrepos/lpp
/usr/lib/objrepos/PDiagRes.vc
/usr/lib/objrepos/PDiagRes
/usr/lib/objrepos/PDiagDev.vc
/usr/lib/objrepos/PDiagDev
/usr/lib/objrepos/PDiagAtt.vc
/usr/lib/objrepos/PDiagAtt
/usr/lib/objrepos/sm_cmd_opt.vc
/usr/lib/objrepos/sm_cmd_opt
/usr/lib/objrepos/sm_cmd_hdr.vc
/usr/lib/objrepos/sm_cmd_hdr
/usr/lib/objrepos/inventory.vc
/usr/lib/objrepos/inventory
/usr/lib/objrepos/PdPathAt.vc
/usr/lib/objrepos/PdPathAt
/usr/lib/objrepos/product.vc
/usr/lib/objrepos/product
/usr/lib/objrepos/lpp.vc
/usr/lib/objrepos/lpp
/usr/lib/objrepos/history.vc
/usr/lib/objrepos/history

AIX ODM for MPIO
/usr/lib/objrepos/PdDv.vc
/usr/lib/objrepos/PdDv
/usr/lib/objrepos/PdAt.vc
/usr/lib/objrepos/PdAt
/var/adm/sw/installp.summary

Aix Odm For Mpio User Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Aix Odm For Mpio User Guide

Uploaded by

Copyright:

Available Formats

AIX ODM for MPIO

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 15 (2021-03-01) Copyright © Huawei Technologies Co., Ltd. i

About This Document

● Technical support engineers

Indicates a hazard with a high level of risk which, if not

Indicates a hazard with a medium level of risk which, if not

Indicates a hazard with a low level of risk which, if not

Indicates a potentially hazardous situation which, if not

Supplements the important information in the main text.

Issue 15 (2021-03-01) Copyright © Huawei Technologies Co., Ltd. ii

Issue 15 (2021-03-01) Copyright © Huawei Technologies Co., Ltd. iii

Optimized some descriptions in documents.

Optimized some descriptions in documents.

Added the functional description of the software optimization

Added description of configuring the ReserveCheck and ReserveBreak functions.

Added description of software functions.

Optimized some descriptions in documents.

Optimized some descriptions in documents.

Issue 15 (2021-03-01) Copyright © Huawei Technologies Co., Ltd. iv

Issue 15 (2021-03-01) Copyright © Huawei Technologies Co., Ltd. v

About This Document................................................................................................................ ii

3 Installing AIX ODM for MPIO............................................................................................. 10

8 Software Security Feature................................................................................................... 43

Issue 15 (2021-03-01) Copyright © Huawei Technologies Co., Ltd. vi

9 Files Related to the ODM.................................................................................................... 44

Issue 15 (2021-03-01) Copyright © Huawei Technologies Co., Ltd. vii

Issue 15 (2021-03-01) Copyright © Huawei Technologies Co., Ltd. 1

About This Chapter

2.1 Environment Requirements

Operating System Requirements

Issue 15 (2021-03-01) Copyright © Huawei Technologies Co., Ltd. 2

5300-03~5300-12 For versions earlier than 5300-08,

6100-00~6100-09 In the SAN Boot environment:

Issue 15 (2021-03-01) Copyright © Huawei Technologies Co., Ltd. 3

– Run the lslpp -l odmcfg.fcp.AIX.rte command to check whether AIX

– Run the lslpp -l odmcfg.fcp.MPIO.rte command to check whether AIX

Optional: Operating System Requirements in the SAN Boot Environment

Table 2-1 Required software packages

AIX ODM for Packages and Docs The Packages

Issue 15 (2021-03-01) Copyright © Huawei Technologies Co., Ltd. 4

Package Software Package Content Description

AIX ODM for ODM-MPIO- ODM-MPIO-

SAN Boot Environment Description

2.2 Checking Disk Space

Issue 15 (2021-03-01) Copyright © Huawei Technologies Co., Ltd. 5

/dev/hd2 11648.00 9966.45 15% 36677 2% /usr

2.3 Deleting the Redundant Disks

Command output description:

If the Manufacturer of a redundant disk is HUAWEI, the redundant disk belongs

Issue 15 (2021-03-01) Copyright © Huawei Technologies Co., Ltd. 6

2.4 Optional: Checking the SAN Boot Environment

Issue 15 (2021-03-01) Copyright © Huawei Technologies Co., Ltd. 7

# bootlist -m normal -o hdisk0

Step 4 Run the ls -l /dev/ipldevice and ls -l /dev/rhdiskX commands to check whether

In the command output, rootvg uses disk hdisk0.

Issue 15 (2021-03-01) Copyright © Huawei Technologies Co., Ltd. 8

2.5 Optional: Configuring an HBA Before Installing AIX

Step 2 Run the chdev -l fscsiX -a dyntrk=yes -P and chdev -l fscsiX -a

Issue 15 (2021-03-01) Copyright © Huawei Technologies Co., Ltd. 9

3 Installing AIX ODM for MPIO

* ATTENTION *

* ATTENTION *