ETERNUS MPIO for IBM AIX 2.0.1 Installation & Configuration Guide

ETERNUS MPIO for IBM AIX 2.0.1 

Installation & Configuration Guide 

P2U3-0150-04ENZ0

This page is intentionally left blank.

Preface 

This document describes how to connect an AIX server and storage system in a multiple path configuration. 

ETERNUS MPIO for IBM AIX is a Path Control Module (PCM) for MultiPath I/O (MPIO) devices that was 

introduced for AIX5.2 and later. Installing it allows the storage system to be used as a MPIO device. 

Fourth Edition 

February 2009 

P2U3-0150-04ENZ0 ETERNUS MPIO for IBM AIX 2.0.1 Installation & Configuration Guide i

Preface 

Safe Use of this Product 

Using this manual 

This manual contains important information to ensure the safe use of this product. Be sure to thoroughly read 

and understand its contents before using the product. After reading, store this manual in a safe place for future 

reference. 

FUJITSU has made every effort to ensure the safety of the users and other personnel, and to prevent property 

damage. When using this product, carefully follow the instructions described in this manual. 

Acknowledgments 

● AIX, RS/6000, pSeries are trademarks of IBM Corp. in the U.S. and other countries. 

● The company names and product names mentioned in this document are registered trademarks or 

trademarks of their respective companies. 

Naming Conventions 

● "Channel Adapter" (CA) refers to the Fibre Channel interface module used by the storage system (This 

is also sometimes used by the servers). 

● "Fibre Channel card" refers to the Fibre Channel interface module normally used by the server. A Host 

Bus Adapter (HBA), PCI Fibre Channel Adapter (PFCA), or Channel Adapter may be used instead, 

depending on the server. 

● "Fibre Channel cable" refers to the cable that is used to connect the storage system and server over a 

Fibre Channel interface. "FC cable", "optical fibre cable", or "multi mode Fibre Channel cable" may be 

used instead, depending on the storage system. 

● Italics are used to show variables such as values and characters that appear in command parameters and 

output examples. 

High Safety Required 

The Product is not designed, developed and manufactured for use in situations that could lead to death, personal 

injury, severe physical damage or other loss (hereinafter called "High Safety Required Use"). Such usage 

includes, but is not limited to, nuclear reaction control in nuclear facilities, aircraft flight control, air traffic 

control, mass transport control, medical life support systems, or missile launch control in weapon systems. The 

Customer shall not use the Product without taking the necessary safety precautions required for High Safety 

Required Use. In addition, Fujitsu (and its affiliates) shall not be held liable for any claims or damages arising 

in connection with the High Safety Required Use of the Product. 

Copyright 2009 FUJITSU LIMITED 

ii ETERNUS MPIO for IBM AIX 2.0.1 Installation & Configuration Guide P2U3-0150-04ENZ0

Contents 

1 Server Compatibility Requirements ................................................................................................................................................1 

1.1 Operation Notes........................................................................................................................................................................3 

1.2 Installation Workflow...............................................................................................................................................................4 

2 Setting Up the Fibre Channel Cards................................................................................................................................................7 

3 Installing ETERNUS MPIO for IBM AIX ......................................................................................................................................9 

3.1 ETERNUS MPIO for IBM AIX Installation ..........................................................................................................................10 

4 Checking the WWN ......................................................................................................................................................................15 

5 Setting up the Storage System.......................................................................................................................................................17 

5.1 Setting up the Storage System ................................................................................................................................................18 

5.1.1 Host Response Settings ...................................................................................................................................................18 

5.1.2 Reset Group Settings .......................................................................................................................................................20 

5.1.3 PowerHA (HACMP) Cluster Settings .............................................................................................................................20 

6 Recognizing Logical Units............................................................................................................................................................21 

7 Creating Volumes ..........................................................................................................................................................................23 

8 Updating ETERNUS MPIO for IBM AIX ....................................................................................................................................25 

8.1 ETERNUS MPIO for IBM AIX Installation Update..............................................................................................................26 

9 Operating MPIO Devices ..............................................................................................................................................................27 

9.1 Path Operations ......................................................................................................................................................................28 

9.1.1 Checking the Path Status.................................................................................................................................................28 

9.1.2 Path Load-balancing Function.........................................................................................................................................29 

9.1.3 Checking the Path Status (Active or Standby).................................................................................................................31 

9.1.4 Disabling a Path...............................................................................................................................................................32 

9.1.5 Deleting a Path ................................................................................................................................................................32 

9.1.6 Adding a Path..................................................................................................................................................................32 

9.2 ETERNUS MPIO for IBM AIX Device Attributes................................................................................................................33 

Appendix 1 Checking the Error Logs...............................................................................................................................................35 

Appendix 2 Collecting Troubleshooting Data ..................................................................................................................................39 

Appendix 3 Notes on Concurrent Firmware Loading (CFL)............................................................................................................41 

Appendix 4 Uninstalling ETERNUS MPIO for IBM AIX...............................................................................................................43 

P2U3-0150-04ENZ0 ETERNUS MPIO for IBM AIX 2.0.1 Installation & Configuration Guide iii

Contents 

This page is intentionally left blank. 

iv ETERNUS MPIO for IBM AIX 2.0.1 Installation & Configuration Guide P2U3-0150-04ENZ0

1 Server Compatibility Requirements 

Storage system can connect to servers that meet the following requirements. Check your server details. 

● Server Hardware 

Hardware name Remarks 

RS/6000 — 

pSeries — 

Power — 

System p — 

When an ETERNUS disk storage system is connected to multiple servers, one of which is allowed to 

control the storage system power supply via an RCI connection or a power control box, make sure that 

the ETERNUS disk storage system and Fibre Channel switches are never turned off while any of the 

other servers are still running. If the ETERNUS disk storage system or Fibre Channel switch is turned 

off before the server shuts down, data may be lost. 

● Server OS 

OS Fix Level 

AIX 5.2 Technology Level 09-CSP or later 

AIX 5.3 Technology Level 05-CSP or later 

AIX 6.1 Not required 

To operate a cluster configuration, use IBM’s "PowerHA (HACMP)" software, and PowerHA 

(HACMP) compatible applications. 

Apply Service Pack 2 or later when any of the following TL (Technology Level) versions are used, as a 

path cannot be set to Enable state with the "chpath" command for the following TL versions. 

– AIX 5.2 TL10 

– AIX 5.2 TL10-SP1 

– AIX 5.3 TL06 

– AIX 5.3 TL06-SP1 

● Supported Disk Storage Systems (All Models) 

– ETERNUS8000 





P2U3-0150-04ENZ0 ETERNUS MPIO for IBM AIX 2.0.1 Installation & Configuration Guide 1


● Fibre Channel Cards 

Fibre Channel card name Microcode Revision Level Remarks 

IBM 1905/5758 2.10X8 or later Made by IBM Corporation, 4Gbps, 1 port 

IBM 1910/5759 2.10X8 or later Made by IBM Corporation, 4Gbps, 2 port 

IBM 1977/5716 1.91a5 or later Made by IBM Corporation, 2Gbps, 1 port 

IBM 6239 1.91X4 or later Made by IBM Corporation, 2Gbps, 1 port 

IBM 6228 3.93a0 or later Made by IBM Corporation, 2Gbps, 1 port 



2 ETERNUS MPIO for IBM AIX 2.0.1 Installation & Configuration Guide P2U3-0150-04ENZ0

1.1 Operation Notes 

Turning off and rebooting the ETERNUS disk storage system 

Always shut down the AIX server before the storage system is turned off and rebooted. 

Troubleshooting 

Power-related problems 

ETERNUS disk storage system is not 

recognized by the server. 

Server is booted with the cable 

disconnected. 

1.1 Operation Notes 

The storage system may not be recognized if turned on after the 

server. The storage system must be turned on before the server. 

If the storage system is not recognized, perform the following 

steps after the storage device has started up: 

• Define the storage system physical volumes: 

# rmdev –Rl fscsiN 

Where "N" is the path number that is to be "Defined". Do 

this for every path in the physical volume configuration. 

• Reconfigure the paths using the "cfgmgr" command. 

# cfgmgr 

If the server is booted with paths disconnected, the storage 

system is not recognized. 

Define the storage system physical volumes and reconfigure the 

storage system physical volume paths using the "rmdev" and 

"cfgmgr" commands, as described in "ETERNUS disk storage 

system is not recognized by the server". 

Command-related problems 

"mkpath" command error If the following error message is displayed, execute the 

command again. 

"smit" command - path configuration 

menu error 

"smit" command - path deletion menu 

error 

(Example) 

# mkpath –p fscsi0 

Method error (/usr/lib/methods/cfgscsidisk): 

0514-077 Cannot perform the requested 

function because none of the 

specified paths match those for 

the specified device. 

The following path configuration menu may not be used: 

[Configure Paths] 

[Configure Selected or All Paths] 

- May not be executed with a path specified 

Alternative action: use the "mkpath" command. 

The following path deletion menu may not be used: 

[Remove Paths] 

[Remove Paths under a Parent] 

- May not be executed with all paths specified 

Alternative action: use the "rmpath" command. 



1.2 Installation Workflow 

This section explains how to install ETERNUS MPIO for IBM AIX on a server and connect it to the storage 

system. 

Refer to the following manual when installing ETERNUS MPIO for IBM AIX. 

● ETERNUS Server Connection Guide for each storage system 

The actual work required will depend on whether ETERNUS MPIO for IBM AIX is being newly installed or 

upgraded. The new installation workflow should also be used when upgrading ETERNUS Multipath Driver 

1.0.x or FJspio (single path connection environment) to ETERNUS MPIO for IBM AIX. 

The workflows are as follows: 

When installing ETERNUS MPIO for IBM AIX or upgrading from ETERNUS Multipath 

Driver 1.0.x or FJspio 

1. Set up the Fibre Channel cards 

Install the driver for the Fibre Channel cards and set the driver parameters. 

Refer to: Setting Up the Fibre Channel Cards (p. 7) 

2. Install ETERNUS MPIO for IBM AIX 

Install the ETERNUS MPIO for IBM AIX module. 

Refer to: Installing ETERNUS MPIO for IBM AIX (p. 9) 

3. Check the WWN 

Check the WWN (World Wide Names) required to setup the storage system. 

Refer to: Checking the WWN (p. 15) 

4. Install ETERNUSmgr and setup the storage system 

Install ETERNUSmgr and setup the storage system. 

Refer to: Setting up the Storage System (p. 17) 

5. Recognize the Logical Units 

Acquire the Logical Units from the storage system. 

Refer to: Recognizing Logical Units (p. 21) 


6. Create volumes 

Create the LVM logical volumes. 

When Updating an existing ETERNUS MPIO for IBM AIX installation 

1.2 Installation Workflow 

Refer to: Creating Volumes (p. 23) 

1. Update ETERNUS MPIO for IBM AIX 

Perform the ETERNUS MPIO for IBM AIX update procedure. 

Refer to: Updating ETERNUS MPIO for IBM AIX (p. 25) 





2 Setting Up the Fibre Channel Cards 

Install the driver for the Fibre Channel card and set the parameter for the driver, following the procedures in 

"Server Connection Guide" for each storage system. 


2 Setting Up the Fibre Channel Cards 



3 Installing ETERNUS MPIO for IBM AIX 



3.1 ETERNUS MPIO for IBM AIX Installation 

If ETERNUS Multipath Driver 1.0.x or FJspio (single path connection environment) has been installed, it must 

be uninstalled. 

The following procedure should be used: 

1. Prepare the installation fileset 

Save the ETERNUS MPIO for IBM AIX installer file downloaded from Fujitsu's web site to an 

appropriate directory, and untar the file. 

# gzip -d Download-File 

# tar -xvf Download-File 

2. Check the current physical volume/installed driver configuration 

Check the storage system physical volumes and installed driver configuration. 

# lsdev -p fscsi* 

# lsdev -p cbx* 

If ETERNUS Multipath Driver 1.0.x has previously been installed, the result will be as follows: 

hdisk1 Available 10-68-01 e3000 Fibre Channel Storage 

If FJspio has been installed, the result will be as follows: 

hdisk1 Available 10-68-01 e3000 - Fujitsu Storage Systems ETERNUS 

If the standard AIX driver has been installed, the result will be as follows: 

hdisk1 Available 10-70-01 Other FC SCSI Disk Driver 

If none of these is displayed, skip directly to Step 7. 

3. Take the volume groups offline 

(1) Check the volume groups of the physical volumes identified in Step 2. 

# lspv 

hdisk0 00096600b56e30f2 rootvg active 

hdisk1 00096600f8ff100a vg1 active 

The third column shows the volume group and the fourth column shows its status. 

If all volume groups are "None", skip to Step 5. 

If a status is not displayed, the status is inactive. If all volume groups are inactive, skip to Step 4. 


(2) Check the file system MOUNT POINT for each active volume group. 

# lsvg -l vg1 


vg1: 

LV NAME TYPE LPs PPs PVs LV STATE MOUNT POINT 

lv01 jfs 400 400 1 open/syncd /lv01 

loglv01 jfslog 1 1 1 open/syncd N/A 

(3) Unmount any file system whose LV STATE is "open/syncd". 

# unmount /lv01 

(4) Render the volume group inactive. 

# varyoffvg vg1 



4. Export the volume groups 

(1) Execute the following command to record the QUORUM and AUTO ON values before 

exporting the volume groups, because exporting/importing the volume groups will reset 

QUORUM and AUTO ON to their default values. 

# lsvg vg1 

VOLUME GROUP: vg1 VG IDENTIFIER: 00ce3f9b00004c0000000 

VG STATE: active PP SIZE: 4 megabyte(s) 

VG PERMISSION: read/write TOTAL PPs: 511 (2044 megabytes) 

MAX LVs: 256 FREE PPs: 287 (1148 megabytes) 

LVs: 1 USED PPs: 224 (896 megabytes) 

OPEN LVs: 1 QUORUM: 2 

TOTAL PVs: 1 VG DESCRIPTORS: 2 

STALE PVs: 0 STALE PPs: 0 

ACTIVE PVs: 1 AUTO ON: no 

MAX PPs per VG: 32512 

MAX PPs per PV: 1016 MAX PVs: 32 

LTG size (Dynamic): 256 kilobyte(s) AUTO SYNC: no 

HOT SPARE: no BB POLICY: relocatable 

Attribution Description 

QUORUM Specifies if a volume group is deactivated when less than the minimum number 

of physical volumes required for a volume group remain usable. 

2 = yes (default value) 

1 = no 

AUTO ON Specifies if a volume group is automatically activated when the system is 

started up. 

yes (default value) 

no 

If QUORUM is set to "1" and AUTO ON is set to "no", these values must be set again after the 

volume groups have been imported. 

(2) Export the volume groups 

Execute the following command. 

# exportvg vg1 


5. Delete the physical volumes 

(1) Identify the parent adapter devices for the physical volumes. 

# lsparent -C -l hdisk1 


fscsi0 Available 10-68-01 FC SCSI I/O Controller Protocol Device 

fscsi1 Available 10-70-01 FC SCSI I/O Controller Protocol Device 

(2) Delete all the "fscsiN" devices displayed. This deletes the child device physical volumes. 

# rmdev -Rdl fscsi0 

# rmdev -Rdl fscsi1 

6. Uninstall ETERNUS Multipath Driver 1.0.x or FJspio 

If ETERNUS Multipath Driver 1.0.x or FJspio was found in Step 2, uninstall it. 

(1) Check which driver is installed. 

# lslpp -l FJspio.rte 

# lslpp -l cbxdpf.driver.obj 

(2) Uninstall the driver. 

# installp -u FJspio.rte 

# installp -u cbxdpf.driver.obj 

A message prompting you to reboot the server is displayed after uninstalling the driver. Ignore 

this and proceed to the next step without rebooting. 


(1) Install ETERNUS MPIO for IBM AIX. 

# installp -acd device all 

Specify the installer file that is being used for the device-parameter. 

AIX Version Installer File 

AIX 5.2 FJmpio_52.bff 



(2) Reboot the server. 

# shutdown -Fr 



8. Check the installation fileset version 

After the server starts up, check the fileset version by executing the "lslpp" command. 

AIX Version Fileset Version 

AIX 5.2 5.2.0.2 



# lslpp -l FJmpio.rte 

Fileset Level State Description 

--------------------------------------------------------------------- 

Path: /usr/lib/objrepos 

FJmpio.rte 5.3.0.2 COMMITTED ETERNUS MPIO for IBM AIX 


4 Checking the WWN 

Check the WWN (World Wide Name), which is required for the storage system setup. 

For example, execute the following command to display the WWN of fcs0: 

# lscfg -vl fcs0 

The WWN is displayed next to the "Network Address" label. 

When multiple Fibre Channel cards are installed, execute the command with the appropriate parameter 

for each. 


4 Checking the WWN 



5 Setting up the Storage System 



5.1 Setting up the Storage System 

Setup the storage system, following the procedure in "Server Connection Guide" for each storage system. 

This section explains notes about the settings when installing and using ETERNUS MPIO for IBM AIX. 

5.1.1 Host Response Settings 

Set the Host Response as follows when using ETERNUS MPIO for IBM AIX. 

The appropriate Host Response settings for each storage system model follow. 

5.1.1.1 ETERNUS4000 model 80 and 100, and ETERNUS3000 Host Response 

Settings 

Select the [Enable] option for [Inquiry Standard Data NACA Function]. 

Select the [Disable] option for [Reservation Conflict Response to Test Unit Ready Commands]. 

Select the [Disable] option for [Response Sense at Firmware Hot Switching]. 

Select the default option for all other settings. 


5.1.1.2 ETERNUS6000 Host Response Settings 

Select the [normal response] option for [Reservation Conflict response for Test Unit Ready]. 

Select the [AIX mode] option for [host specific mode]. 

Select the default option for all other settings. 

5.1 Setting up the Storage System 



5.1.1.3 ETERNUS8000, and ETERNUS4000 models 300, 400, 500, and 600 Host 

Response Settings 

Refer to "ETERNUS disk storage systems Server Connection Guide (Fibre Channel) for AIX" to set the Host 

Response. 

5.1.1.4 ETERNUS2000 Host Response Settings 

Refer to "ETERNUS disk storage systems Server Connection Guide (Fibre Channel) for AIX" to set the Host 

Response. 

5.1.2 Reset Group Settings 

When using ETERNUS MPIO for IBM AIX, reset group settings are not required. 

5.1.3 PowerHA (HACMP) Cluster Settings 

When using ETERNUS MPIO for IBM AIX with a PowerHA (HACMP) cluster server, exactly the same 

settings as for a single (unclustered) server should be used. 


6 Recognizing Logical Units 

After connecting the storage system and the server by Fibre Channel cable, execute the "cfgmgr" command to 

force the server to acquire the Logical Units (LUN) from the ETERNUS disk storage system. 

# cfgmgr –v 

Storage system Logical Units (LUN) recognized by the server are regarded as physical volumes (hdisk). 

Confirm that ETERNUS MPIO for IBM AIX has recognized these physical volumes. 


The following type of message should appear: 

hdisk1 Available 10-68-01 MPIO E3000 - Fujitsu Storage Systems ETERNUS 


6 Recognizing Logical Units 



7 Creating Volumes 

To create new logical volumes, follow the procedures in "Server Connection Guide" for each storage system. 

If any volume groups were exported 

If any volume groups were exported during the installation of ETERNUS MPIO for IBM AIX, they should now 

be reimported using the following command: 

# importvg –y vg1 hdisk1 

Confirm the state of the imported volume groups. 

# lsvg vg1 

If the QUORUM and AUTO ON attributes are changed from their initial (pre-export) values, reset them using 

the following commands: 

To set QUORUM to "1", execute the following command: 

# chvg –Qn vg1 

To set AUTO ON to "no", execute the following command: 

# chvg –an vg1 


7 Creating Volumes 



8 Updating ETERNUS MPIO for IBM AIX 

This chapter explains how to update the ETERNUS MPIO for IBM AIX fileset. 


8 Updating ETERNUS MPIO for IBM AIX 

8.1 ETERNUS MPIO for IBM AIX Installation Update 

The procedure is as follows: 

1. Prepare the update fileset 

Save the ETERNUS MPIO for IBM AIX installer file downloaded from Fujitsu's web site to an 

appropriate directory, and untar the file. 

# gzip -d Download-File 

# tar –xvf Download-File 


Check the volume groups of the physical volumes. 



Deactivate the volume groups, as described in Step 3 "Take the volume groups offline" in "3.1 

ETERNUS MPIO for IBM AIX Installation". 

3. Change the physical volume status 

Execute the following command to define the storage system physical volumes: 

# rmdev –Rl fscsiN 

Where "N" is the path number that is to be "Defined". 

Do this for every path in the physical volume configuration. 


(1) Install ETERNUS MPIO for IBM AIX. 

# installp –acd device all 

Where device is the fileset that is to be used. 

AIX Version Fileset 




# shutdown –Fr 

5. Check the update fileset version 

Check the fileset version, as described in Step 8 "Check the installation fileset version" of "3.1 



9 Operating MPIO Devices 

This chapter explains how to operate an MPIO device. 



9.1 Path Operations 

By installing ETERNUS MPIO for IBM AIX, physical volumes are configured as MPIO devices for AIX. Path 

operations can be performed using the normal AIX commands. 

● lspath 

Displays path related information. 

● chpath 

Changes the path attributes. 

● mkpath 

Adds a path. 

● rmpath 

Removes a path. 

9.1.1 Checking the Path Status 

Execute the following command to check the path status. 

# lspath 

The status of each path is displayed as follows: 

Enabled hdisk1 fscsi0 








When an active path fails, the path status changes as follows: 

Failed hdisk1 fscsi0 




"Failed" is displayed for the failed path. 


9.1.2 Path Load-balancing Function 


ETERNUS MPIO for IBM AIX performs load-balancing over the usable paths to improve the access 

performance. 

Some storage systems (hereafter called Assigned CM type systems) fix the normal access path for each LUN to 

a given controller, while other systems (hereafter called Non-assigned CM type systems) do not fix the access 

paths. 

For Assigned CM type systems, the path(s) connecting to the controller that is normally used will have active 

status, while the path(s) connecting to other controllers will have standby status. 

For Non-assigned CM type systems, all paths are in active status and available for access. 

9.1.2.1 ETERNUS4000, ETERNUS2000, and ETERNUS3000 

ETERNUS4000, ETERNUS2000, and ETERNUS3000 are Assigned CM type systems. 

Paths connected to the assigned CM are in active status, while paths connected to the non-assigned CM are in 

standby status. 

Load-balancing is performed on the paths in active status (hereafter called active paths). 

Paths in standby status (hereafter called standby paths) are normally not used for access. 



9.1.2.2 ETERNUS8000 and ETERNUS6000 

ETERNUS8000 and ETERNUS6000 are Non-assigned CM type systems. 

Non-assigned CM type systems do not have any Assigned CMs and all connected paths are in active status. 

Load-balancing is performed for all paths. 


9.1.3 Checking the Path Status (Active or Standby) 


Execute the following command to check whether the fscsi0 paths for hdisk1 are in active or standby status. 

"path_type" indicates the active or standby status. 

# lspath –El hdisk1 –p fscsi0 –a path_type 

The following is displayed for active paths. 

path_type active Path Type True 

The following is displayed for standby paths. 

path_type passive Path Type True 

Execute the following command to display the path status list. 

#/usr/lpp/FJmpio/FJpathinfo 

[For an Assigned CM System (4-path)] 

fscsi0 fscsi1 fscsi2 fscsi3 

hdisk pri type pri type pri type pri type 

-------- --- ------- --- ------- --- ------- --- ------hdisk1 

1 active 1 active 1 passive 1 passive 

hdisk2 1 active 1 active 1 passive 1 passive 

hdisk3 1 passive 1 passive 1 active 1 active 

hdisk4 1 passive 1 passive 1 active 1 active 

[For a Non-assigned CM System (4-path)] 

fscsi0 fscsi1 fscsi2 fscsi3 

hdisk pri type pri type pri type pri type 

-------- --- ------- --- ------- --- ------- --- ------hdisk1 

1 active 1 active 1 active 1 active 

hdisk2 1 active 1 active 1 active 1 active 



*: pri column: priority (path priority order) 

type column: path_type (path type) 



9.1.4 Disabling a Path 

Usable paths may be purposely disabled. Disabled paths will not be used in case of failover (switching paths). 

Execute the following command will disable the fscsi0 path of hdisk1. 

# chpath -l hdisk1 -p fscsi0 -s dis 

Disabled paths are displayed by the "lspath" command as follows: 


Disabled hdisk2 fscsi1 

Execute the following command to re-enable the path. 

# chpath -l hdisk1 -p fscsi0 -s en 

9.1.5 Deleting a Path 

Disabled paths revert to usable after the system is rebooted. 

Use the "rmpath" command to delete a path. 

# rmpath -p fscsiN 

Where "N" is the number of the path that is to be deleted. 

9.1.6 Adding a Path 

Use the "mkpath" command to add a path. 

# mkpath -p fscsiN 

Where "N" is the number of the path that is to be added. 


9.2 ETERNUS MPIO for IBM AIX Device Attributes 

9.2 ETERNUS MPIO for IBM AIX Device Attributes 

The physical volume attributes of ETERNUS MPIO for IBM AIX are as follows. 

Attribute Setting value Description 

algorithm load_balance Path selection algorithm 

Priority is given to the usable active paths with low I/O counts when 

load-balancing. 

If all active paths are disabled, load-balancing is performed on the 

standby paths. 

reserve_policy no_reserve Reservation policy 

Disk reservation is not used 

hcheck_mode nonactive Health check mode 

Specifies which paths are to be periodically checked. 

Check the idle paths (no I/O) and check the abnormal paths. 

hcheck_interval 40 Health check interval 

Specifies the health check interval. 

40 seconds 

The path attributes of ETERNUS MPIO for IBM AIX are as follows. 

Attribute Setting value Description 

path_type active/passive Path type 

Indicates whether the path status is active or standby. 

Active paths are displayed as "active", while standby paths are 

displayed as "passive". 

priority 1 Path priority order 

Not used 

This attribute is not required because ETERNUS MPIO for IBM AIX 

performs load-balancing automatically. 





Appendix 1 Checking the Error Logs 

Error logs are saved in case of system problems, and may be checked with the "errpt" command. 

# errpt 

IDENTIFIER TIMESTAMP T C RESOURCE_NAME DESCRIPTION 

DE3B8540 1221090106 P H hdisk1 PATH HAS FAILED 

DESCRIPTION: PATH HAS FAILED 

RESOURCE_NAME: Physical volume name 

Meaning: 

Path failure has been detected. If a usable alternative path exists, the active path is switched and disk I/O 

operations continue. 

Action: 

Check the device displayed under RESOURCE_NAME and fix any problems. If this message is 

displayed frequently, contact your sales representative. 


3074FEB7 1221094106 T H fscsi0 ADAPTER ERROR 

DESCRIPTION: ADAPTER ERROR 

RESOURCE_NAME: FC I/O controller protocol device name 

Meaning: 

Hardware error has been detected at the adapter. 

Action: 

Check the device displayed under RESOURCE_NAME and fix any problems. If this message occurs 

frequently, contact your sales representative. 




B8FBD189 1221111106 T S fscsi1 SOFTWARE PROGRAM ERROR 

DESCRIPTION: SOFTWARE PROGRAM ERROR 

RESOURCE_NAME: FC I/O controller protocol device name 

Meaning: 

Communication error has been detected at the FC I/O controller protocol device. 

Action: 




B8113DD1 1221090106 T H fcs0 LINK ERROR 

DESCRIPTION: LINK ERROR 

RESOURCE_NAME: FC adapter name 

Meaning: 

Link down error has been detected at the FC adapter. 

Action: 

Check the connection between the FC adapter and FC cable. If this message occurs frequently, contact 

your sales representative. 


C62E1EB7 1221101106 P H hdisk1 DISK OPERATION ERROR 

DESCRIPTION: DISK OPERATION ERROR 

RESOURCE_NAME: Physical volume name 

Meaning: 

Error has been detected at the disk I/O operation. 

Action: 





613E5F38 1221101106 P H LVDD I/O ERROR DETECTED BY LVM 

DESCRIPTION: I/O ERROR DETECTED BY LVM 

RESOURCE_NAME: LVM 

Meaning: 

I/O error has been detected by LVM. 

Action: 

Check for related error logs before and after this one and fix any problems. If this message occurs 

frequently, contact your sales representative. 





Appendix 2 Collecting Troubleshooting 

Data 

Obtain the following data in case of system problems. 

Note that when a command saves output to a file that already exists, the old data will be overwritten. 

Use new file names as necessary. 

The "/tmp" directory is used to hold the collected troubleshooting data. Confirm that "/tmp" directory has 

enough free space before starting. 

The data collection procedure is as follows: 

1. Collect the data required to understand the current situation. 

(1) Run the system log collection tool. 

# /usr/lpp/FJmpio/FJmpioGetlog 

(2) Check the collected files. 

# tar -tvf /tmp/FJmpio_log.tar 

-rw-r--r-- 0 0 2406 May 30 22:36:32 2008 /tmp/errpt.log 

-rw-r--r-- 0 0 124048 May 30 22:36:32 2008 /tmp/lslpp.log 

-rw-r--r-- 0 0 24855 May 30 22:36:32 2008 /tmp/lsdev.log 

-rw-r--r-- 0 0 1254 May 30 22:36:32 2008 /tmp/lspv.log 

-rw-r--r-- 0 0 780 May 30 22:36:33 2008 /tmp/lspath.log 

-rw-r--r-- 0 0 6948 May 30 22:36:38 2008 /tmp/iostat.log 

-rw-r--r-- 0 0 131052 May 30 22:36:38 2008 /tmp/alog.log 

-rw-r--r-- 0 0 818 May 30 22:36:39 2008 /tmp/pathinfo.log 

-rw-r--r-- 0 0 11413 May 30 22:36:40 2008 /tmp/lscfg.log 

(3) After executing the system log collection tool, save the following file: 

- /tmp/FJmpio_log.tar 

If the problem is reproducible, proceed to the next set of steps. 


Appendix 2 Collecting Troubleshooting Data 

2. Collect further data in order to trace the problem 

(1) Change to the English-language environment. 

# export LANG=C 

(2) Delete any old system logs. 

# errclear 0 

This will delete all existing system logs, and is not absolutely necessary. 

You may wish to just note the time at which you attempt to reproduce the problem. 

(3) Start the trace program. 

# /usr/lpp/FJmpio/FJruntrace 

(4) Reproduce the problem. 

(5) Stop the trace after the problem has appeared. 

# trcstop 

(6) Output the trace results. 

# trcrpt > /tmp/trc.log 

(7) Output the system log. 

# errpt -a > /tmp/errpt.log 

(8) Collect the following two files, which have just been created: 

- /tmp/trc.log 

- /tmp/errpt.log 


Appendix 3 Notes on Concurrent Firmware 

Loading (CFL) 

This appendix provides information for the maintenance of the ETERNUS disk storage system. 

Selectable modes for Concurrent Firmware Loading (CFL) vary according to the ETERNUS disk storage 

system models. 

The following table shows the individual notes on each ETERNUS disk storage system model: 

Model Notes 

ETERNUS8000 all models CFL can be performed in either the Normal Mode or Operator 

Cooperation Mode. 

In Operator Cooperation Mode, "Path status confirmation" 

ETERNUS4000 models 300, 400, 

500, and 600 

described below is required. 

CFL can be performed in either the Normal Mode or Operator 

Cooperation Mode. 



ETERNUS4000 models 80 and 100 Only one operation mode is available. 

"Path status confirmation" described below is required during 

CFL. 

ETERNUS2000 all models Operator Cooperation Mode must be used in order to perform 

CFL. Normal mode is not recommended in AIX MPIO 

environment. 



ETERNUS6000 all models Operator Intervention Mode must be used in order to perform 

CFL. Normal mode is not recommended in AIX MPIO 

environment. 

In Operator Intervention Mode, "Path status confirmation" 


ETERNUS3000 all models Only one operation mode is available. 

"Path status confirmation" described below is required during 

CFL. 

Path status confirmation 

When CFL is performed in operator cooperation (operator intervention) mode, the firmware update process is 

performed on each CM in turn and waits for operator confirmation before proceeding to the next CM. 

For the ETERNUS MPIO for IBM AIX fileset, perform the following operations instead of switching the paths 

offline/online: 

● After loading the firmware on the first CM, wait for the failed paths to transition back to enabled state 

(this should take about three to five minutes). 

● Only start loading the firmware of the other CM after confirming that the paths have transitioned back 

to the Enable state. 

● After loading the firmware on the other CM, confirm that the paths have transitioned back to the Enable 

state. 


Appendix 3 Notes on Concurrent Firmware Loading (CFL) 

CFL workflow 

ETERNUS AIX 

------------------------- --------------------------------------------------------- 

1. CM#0 CFL start -> CM#0 paths are set to the Fail state 

2. CM#0 CFL end -> Confirm that CM#0 paths are in the Enable state 

(should take about 3 to 5 minutes) 

3. CM#1 CFL start -> CM#1 paths are set to the Fail state 

4. CM#1 CFL end -> Confirm that CM#1 paths are in the Enable state 

(should take about 3 to 5 minutes) 


Appendix 4 Uninstalling ETERNUS MPIO for 

IBM AIX 

The following shows how to uninstall ETERNUS MPIO for IBM AIX: 


Check the volume groups of the physical volumes. 



Deactivate the volume groups, as described in Step 3 "Take the volume groups offline" of "3.1 


2. Delete the physical volumes 

Delete the physical volumes, as described in Step 5 "Delete the physical volumes" of "3.1 ETERNUS 

MPIO for IBM AIX Installation". 

3. Uninstall ETERNUS MPIO for IBM AIX 

(1) Uninstall ETERNUS MPIO for IBM AIX. 

# installp –u FJmpio.rte 


# shutdown –Fr 


Appendix 4 Uninstalling ETERNUS MPIO for IBM AIX 



ETERNUS MPIO for IBM AIX 2.0.1 

Installation & Configuration Guide 

P2U3-0150-04ENZ0 

Date of issuance: February 2009 

Issuance responsibility: FUJITSU LIMITED 

- The contents of this manual are liable to being updated without notice. 

- While the contents of this manual are the product of all due care and diligence, no responsibility can be 

accepted for operational problems arising from any errors or missing information, or other use of the 

information contained in this manual. 

- Fujitsu assumes no liability for damages to third party copyrights or other rights arising from the use of 

any information in this manual. 

- Contents of this manual are not to be reproduced without permission from Fujitsu.

ETERNUS MPIO for IBM AIX 2.0.1 Installation & Configuration Guide

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?