Readme: 3PAR® Multipath I/O 2.
For Printed Material Copyright © 2006-2007 3PAR Inc. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, without the prior written consent of 3PAR Inc., 4209 Technology Drive, Fremont, CA 94538. For Electronic Material The user may print one copy for personal use. Production of multiple copies or copies for sale is strictly prohibited.
Page 1 Introduction 3PAR® MPIO for IBM AIX enables the use of more than one physical I/O path to access a 3PAR InServ Storage Server. By offering fault tolerance and/or load balancing of I/O traffic with Active/Active support, multipathing provides improved system reliability and availability. The contents included within the CD are: • readme.doc This file. • 3PARmpio.bff 3PARmpio.64 package. • .toc Installation table of content.
Page 2 3. For AIX 5.2 ML1 and later, IBM introduced the dynamic tracking features. The dynamic tracking defaults to disabled by AIX. The installation adds the required 3PAR ODM attributes for the dynamic tracking; however, it will not enable it. To enable the dynamic tracking, execute the /usr/lpp/3PARmpio/bin/3par_dyntrk.sh script. NOTE: For an AIX host that will be attached to the 3PAR InServ Storage Server for the first time, the /usr/lpp/3PARmpio/bin/3par_dyntrk.
Page 3 Host Boot from an InServ Storage Server NOTE: Once 3PAR MPIO 2.2 for IBM AIX has been installed, it cannot be de-installed for a host boot disk. AIX host boot is supported by the InServ Storage Server. However, in order to successfully install the AIX operating system on InServ volumes, the following steps must be followed: 1. Configure the InServ Storage Server to the AIX system. Refer to the 3PAR Best Practice documents for IBM AIX for detailed instructions.
Page 4 Utility Scripts There are some useful 3PAR utility scripts that reside in the /usr/lpp/3PARmpio/bin: • 3par_dyntrk.sh [-a] - This script enables the dynamic tracking features on adapters that have 3PAR devices attached. If it is preferable to enable dynamic tracking on all adapters, the -a option can be used. • 3par hdisk2vv.sh - This script takes an AIX hdisk as input and converts it to its associated 3PAR virtual volume. • 3par_vv2hdisk.
Page 5 Manage 3PAR MPIO Device by SMIT The 3PAR AIX MPIO device can be managed by smit mpio. There are three categories under the smit mpio management: • MPIO Path Management • MPIO Device Management • MPIO Parent Management The common use for the Path Management is to enable the Failed status path. To enable the path, select MPIO Path Management > Enable Paths > Enable Selected or All Paths. The Device Management can be used to change the default device attributes setting.
Page 6 • max_transfer 0x40000 Maximum transfer size in bytes that can be transferred to the device in one operation. The default is 256K (0x40000). To change these attributes, select MPIO Device Management > Change/Show MPIO Device Characteristics. Select the Device Name by pressing F4. Change the attribute(s) value and then click Enter. The followings are sample SMIT actions: SMIT Action Steps Enable path 1. Execute smit mpio. 2.
Page 7 Change device reserve_policy 1. Execute smit mpio. 2. Select MPIO Device Management > Change/Show MPIO Device Characteristics. 3. Select the Device Name by pressing F4. 4. Move the cursor to the Reservation Policy attribute. 5. Press F4 to select preferred reservation policy 6. Press Enter. Change device hcheck_interval 1. Execute smit mpio. 2. Select MPIO Device Management > Change/Show MPIO Device Characteristics. 3. Select the Device Name by pressing F4. 4.
Page 8 Understanding 3PAR Support for HACMP You can run 3PAR MPIO 2.2 for IBM AIX in concurrent and non-concurrent multi-host environments. The same LUNs on the 3PAR storage device can be attached to the AIX hosts managed by HACMP. The 3PAR MPIO 2.2 can support HACMP version 5.3 running on pSeries servers with AIX 5.3 ML3. Refer to the 3PAR Configuration Matrix and the 3PAR Best Practice documents for IBM AIX for complete details on supported configurations. 3PAR MPIO 2.
Page 9 where X is the device number such as hdisk3. You can also change the hdisk device Reservation Policy to no_reserve through smit as described in the section, Manage 3PAR MPIO Device by SMIT. For HACMP configuration, refer to the HACMP 5.3 Concepts and Facilities Guide, or visit the HACMP 5.3 documentation website: http://www-03.ibm.com/servers/eserver/pseries/library/hacmp_docs.html NOTE: 320-1405-03 The APAR IY82920 is required for AIX 5.3 ML3 to fully support the HACMP fabric configuration.
