Fujitsu ETERNUS Multipath Driver V2 User Manual

FUJITSU Storage ETERNUS Multipath Driver V2 User's Guide

for Linux

P2U3-0031-15ENZ0

This page is intentionally left blank.

This FUJITSU Storage ETERNUS Multipath Driver User's Guide describes the features, functions, and operation of the "ETERNUS Multipath Driver" (hereinafter referred to as "Multipath Driver") software on a Linux server. This manual describes how to use the Multipath Driver to manage the path control, connection status, and other features of FUJITSU Storage "ETERNUS Disk storage system, ETERNUS All Flash Array, GR series" (hereinafter referred to as "storage system" unless stated otherwise). The latest information is provided in the "FUJITSU Storage ETERNUS Multipath Driver V2 (for Linux) Installation Information" found under "Downloads" at the following URL:

http://www.fujitsu.com/global/products/computing/storage/software/eternus-mpd/

Intended Audience

This guide is intended for system administrators who are connecting the storage system to a Linux server.

Preface

Fifteenth Edition

October 2014

Organization and Contents

This guide is composed of the following 11 chapters and an appendix.

● Chapter 1 What is Multipath Driver?

This chapter explains the features, functions, and connection patterns of the Multipath Driver.

● Chapter 2 Multipath Driver System Setup

This chapter explains how to install and uninstall the Multipath Driver. Instructions are provided for setting up the system environment, including setup of logical units, partitions, and file systems, and mounting the storage system.

● Chapter 3 Multipath Driver Functions and Operation

This chapter explains how to use the main commands to operate various functions of the Multipath Driver.

● Chapter 4 Changing the Multipath Configuration (FC/FCoE Connection for RHEL-AS4, RHEL-ES4, RHEL5,

SLES9, or SLES10)

This chapter explains how to change a multipath configuration for a FC/FCoE connection with RHEL-AS4, RHEL-ES4, RHEL5, SLES9, or SLES10.

3

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Preface

● Chapter 5 Changing the Multipath Configuration (SAS Connection for RHEL-AS4, RHEL-ES4, RHEL5, or

SLES10)

This chapter explains how to change a multipath configuration for a SAS connection with RHEL-AS4, RHELES4, RHEL5, or SLES10.

● Chapter 6 Changing the Multipath Configuration (iSCSI Connection for RHEL5, SLES9, or SLES10)

This chapter explains how to change a multipath configuration for an iSCSI connection with RHEL5, SLES9, or SLES10.

● Chapter 7 Changing the Multipath Configuration (FC/FCoE Connection for RHEL6, RHEL7, or SLES11)

This chapter explains how to change a multipath configuration for a FC/FCoE connection with RHEL6, RHEL7, or SLES11.

● Chapter 8 Changing the Multipath Configuration (SAS Connection for RHEL6, RHEL7, or SLES11)

This chapter explains how to change a multipath configuration for a SAS connection with RHEL6, RHEL7, or SLES11.

● Chapter 9 Changing the Multipath Configuration (iSCSI Connection for RHEL6, RHEL7, or SLES11)

This chapter explains how to change a multipath configuration for an iSCSI connection with RHEL6, RHEL7, or SLES11.

● Chapter 10 Notes when Using the Multipath Driver

This chapter contains important notes for using the Multipath Driver.

● Chapter 11 Command Reference

This chapter contains important notes for using the Multipath Driver.

A list of "Syslog Messages" is provided in the appendix.

4

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Preface

Trademarks, Product Names, and Abbreviations Used in this Guide

• "HBA" represents a Host Bus Adapter, which is a Linux server-installed Fibre Channel card, Serial Attached

SCSI (SAS) card, or Converged Network Adapter (CNA) that connects to a storage system.

• "NIC" is a Network Interface Card.

• "CA" is a storage system Channel Adapter.

• "CM" is a storage system Controller Module.

• The following software bundle is described as "ETERNUS Web GUI".

- Web-based GUI management tool that is provided with the storage system as standard

- ETERNUSmgr that is installed in some storage systems

• Red Hat Enterprise Linux series products are as described below.

Product names Abbreviation

Red Hat Enterprise Linux 7 RHEL7

Red Hat Enterprise Linux 6 RHEL6

Red Hat Enterprise Linux 5 RHEL5

Red Hat Enterprise Linux AS v.4 RHEL-AS4

Red Hat Enterprise Linux ES v.4 RHEL-ES4

• SUSE Linux Enterprise Server series products are as described below.

Product names Abbreviation

SUSE Linux Enterprise Server 11 SLES11

SUSE Linux Enterprise Server 10 SLES10

SUSE Linux Enterprise Server 9 SLES9

Related Manuals

Refer to the following related manuals for more information:

• The storage system manual

• The manual provided with ETERNUS Web GUI/GRmgr/ETERNUSmgr

5

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Preface

Typographical Conventions

The following conventions are used in this guide.

A product-usage caution that must be followed. Not doing so may result in loss of data.

A note that provides additional information.

High Safety

This Product is designed, developed and manufactured as contemplated for general use, including without limitation, general office use, personal use, household use, and ordinary industrial use, but is not designed, developed and manufactured for use in situations with accompanying fatal risks or dangers that, unless extremely high safety is secured, could lead directly to death, personal injury, severe physical damage or other loss (hereinafter "High Safety Required Use"), including without limitation, nuclear reaction control in nuclear facility, aircraft flight control, air traffic control, mass transport control, medical life support system, and missile launch control in weapon systems. Do not use this Product for High Safety Required Use without securing the sufficient safety level required. If you wish to use this Product for High Safety Required Use, please consult with our sales representative before such use.

Linux is a registered trademark of Linus Torvalds. Red Hat is a registered trademark of Red Hat, Inc. in the U.S. and other countries. SUSE is a registered trademark of Novell, Inc. in the United States and other countries. Intel, the Intel logo, Itanium, and the Itanium logo are trademarks of Intel Corporation in the U.S. and other countries. The company names, product names and service names mentioned in this document are registered trademarks or trademarks of their respective companies.

6

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Multipath Driver Modification History

This section provides a history of modifications for the Multipath Driver.

■ V2.0L03 modifications

● Modification outline

Previously, when a response from the device was "Illegal Request", it was changed to "DID_SOFT_ERROR". For V2.0L03, the "Illegal Request" response does not change to "DID_SOFT_ERROR".

- Modification target

Multipath Driver

- Modification details

Version Modification details

V2.0L02 or earlier The "Illegal Request" response from the device changes to "DID_SOFT_ERROR".

V2.0L03 The "Illegal Request" response from the device does not change to "DID_SOFT_ERROR".

Release Information

- Modification effect

Previously, some I/Os for which the cause of the error was "Illegal Request" returned "DID_SOFT_ERROR". After this modification, "Illegal Request" is returned for I/Os for which the error factor is "Illegal Request".

● Modification outline

The error levels of some messages that were NOTICE or lower error levels have been changed to WARNING or higher. In addition, the error levels of some messages that were WARNING or higher have been changed to NOTICE or lower.

- Modification target

Multipath Driver

- Modification details

Version Modification details

V2.0L02 or earlier Some error messages that require device monitoring have "NOTICE" error level. Some

error messages that do not require device monitoring have "WARNING" error level.

V2.0L03 For error messages that require device monitoring, "WARNING" or higher error level are

displayed. For error messages that do not require device monitoring, "NOTICE" or a lower error level are displayed.

- Modification effect

This change affects when error levels are used for message monitoring.

7

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Release Information

■ V2.0L10 modification

● Modification outline

■ V2.0L11 modification

● Modification outline

The "by-path" name for the udev function is not created after V2.0L10 is applied. Use the "by-id" name.

- Modification target

Multipath Driver

- Modification details

Version Modification details

V2.0L03 or earlier Creates a "by-path" name.

V2.0L10 Does not create a "by-path" name.

- Modification effect

The "by-path" name for the udev function cannot be used. Use the "by-id" name.

Removed the function that inquires whether the udev function is used or not when using the "mpdconfig s" command.

- Modification target

"mpdconfig" command

- Modification details

Version Modification details

V2.0L10 or earlier Inquires whether the udev function is used or not when using the "mpdconfig -s"

command.

V2.0L11 Does not inquire whether the udev function is used or not when using the "mpdconfig -s"

command.

- Modification effect

Does not affect any other operation.

8

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Release Information

■ V2.0L12 modifications

● Modification outline

The default Max Throttle value of the ETERNUS2000 is changed from "256" to "40".

- Modification target

Multipath Driver

- Modification details

Version Modification details

V2.0L11 or earlier The default Max Throttle value of the ETERNUS2000 is "256".

V2.0L12 The default Max Throttle value of the ETERNUS2000 is "40".

- Modification effect

After a connected ETERNUS2000 is initially recognized, the Max Throttle value is changed from "256" to "40".

The default Max Throttle setting of the ETERNUS8000, the ETERNUS6000, and the ETERNUS4000 model 300 and 500 is automated.

- Modification target

Multipath Driver

- Modification details

Version Modification details

V2.0L11 or earlier The default Max Throttle value of the ETERNUS8000, the ETERNUS6000, and the

ETERNUS4000 model 300 and 500 has to be manually specified.

V2.0L12 The default Max Throttle value of the ETERNUS8000, the ETERNUS6000, and the

ETERNUS4000 model 300 and 500 is automatically specified.

- Modification effect

When connecting to the ETERNUS8000, the ETERNUS6000, and the ETERNUS4000 model 300 and 500, Max Throttle does not have to be set with the "mpdconfig -m" command.

9

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Release Information

MPDH%d: NOTICE: %s: Device configuration is without CFL redundancy. All paths connect to (ZZ%x, ZZ%x).

■ V2.0L13 modifications

● Modification outline

The maximum number of devices for the specifying recognition order is changed from "20" to "32".

- Modification target

Multipath Driver, "mpdconfig" command

- Modification details

Version Modification details

V2.0L12 or earlier Up to 20 devices can be specified for the recognition order.

V2.0L13 Up to 32 devices can be specified for the recognition order.

- Modification effect

Up to 32 storage systems can be specified for the recognition order. If 33 or more storage systems are specified for the recognition order and the "mpdconfig -s" command is executed, the following error message is displayed:

Cannot setup because the number of devices is greater than 32.

● Modification outline

Added a message for loading concurrent firmware in storage systems.

- Modification target

Multipath Driver

- Modification details

Version Modification details

V2.0L12 or earlier Even when performing concurrent firmware loading closes all the paths for the

connected storage system, a message is not output in "/var/log/messages".

V2.0L13 When performing concurrent firmware loading closes all the paths for the connected

storage system, the following message is output in "/var/log/messages":

- Modification effect

When performing message monitoring, the newly added message may not be monitored as intended. Note that this change does not affect the message monitoring function with Fujitsu middleware.

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

10

Release Information

MPDH%d: NOTICE: SCSI%u (%u, %u, %u) : I/O LUN degrade. number of online paths left of this LUN =%d

MPDH%d: WARNING: I/O LUN degraded, no more online path of this LUN.

SCSI%u (%u, %u ,%u): ERROR=0x05: abort

SCSI%u (%u, %u ,%u): ERROR=0x06: parity error

SCSI%u (%u, %u ,%u): ERROR=0x07: internal error

SCSI%u (%u, %u ,%u): ERROR=0x08: reset

SCSI%u (%u, %u ,%u): ERROR=0x0b: soft error

● Modification outline

Some error messages for I/O are added or changed.

- Modification target

Multipath Driver

- Modification details

Version Modification details

V2.0L12 or earlier When an I/O error occurs, the following message is output in "/var/log/ messages":

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

11

Release Information

MPDH%d: NOTICE: SCSI%u (%u, %u, %u) : I/O LUN degrade. MPDH%d: NOTICE: SCSI%u (%u, %u, %u) : I/O LUN failed. number of online paths left for this LUN =%d

or

MPDH%d: NOTICE: SCSI%u (%u, %u, %u) : I/O rejection. number of online paths left for this LUN =%d.

MPDH%d: WARNING: I/O LUN failed, no more online path for this LUN.

or

MPDH%d: WARNING: I/O rejection, no more online path for this LUN.

SCSI%u (%u, %u ,%u): ERROR=0x05: HBA abort

SCSI%u (%u, %u ,%u): ERROR=0x06: HBA parity error

SCSI%u (%u, %u ,%u): ERROR=0x07: HBA internal error

SCSI%u (%u, %u ,%u): ERROR=0x08: HBA reset

SCSI%u (%u, %u ,%u): ERROR=0x0b: HBA soft error

MPDH%d: WARNING: SCSI%u (%u, %u, --) : I/O timeout was detected by the scsi timer.

SCSI%u (%u, %u ,%u): ERROR=0x02: HBA bus busy

SCSI%u (%u, %u ,%u): ERROR=0x04: HBA bad target

SCSI%u (%u, %u ,%u): STATUS ERROR=%d

Version Modification details

V2.0L13 When an I/O error occurs, the following message is output in "/var/log/ messages":

• Changed message

• Added message

- Modification effect

When performing message monitoring, the newly added message may not be monitored as intended. Note that this change does not affect the message monitoring function with Fujitsu middleware.

12

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Release Information

LUN degraded,

bus busy,

parity,

abort,

internal error,

reset,

soft error

LUN trouble

or

I/O rejection,

HBA bus busy,

HBA parity error,

HBA abort,

HBA internal error,

HBA reset,

HBA soft error,

HBA bad target,

● Modification outline

Some of the path details in the output of the "iompadm info" command are added or changed.

- Modification target

"iompadm" command

- Modification details

Version Modification details

V2.0L12 or earlier The path details in the "iompadm info" command output when executing the "iompadm

info" command after an I/O error occurs are shown below.

V2.0L13 The path details in the "iompadm info" command output when executing the "iompadm

info" command after an I/O error occurs are shown below.

- Modification effect

When analyzing the result of the "iompadm info" command, the newly added message may not be analyzed as intended. Note that this change does not affect the Fujitsu middleware that analyzes the "iompadm info" command result.

13

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Release Information

SCSI%u (%u, %u ,%u): incomplete scsi cdb=0x%x - giving up

SCSI%u (%u, %u ,%u): incomplete scsi cdb=0x%x

● Modification outline

Changed the message that is displayed when the I/O by diagnosis function fails.

- Modification target

Multipath Driver

- Modification details

Version Modification details

V2.0L12 or earlier The following message is displayed when the I/O by diagnosis function fails:

V2.0L13 The following message is displayed when the I/O by diagnosis function fails:

- Modification effect

When performing message monitoring, the newly added message may not be monitored as intended. Note that this change does not affect the message monitoring function with Fujitsu middleware.

■ V2.0L14 modification

● Modification outline

The initial RAM disk and boot loader settings for an Multipath Driver that is not used any more are automatically deleted.

- Modification target

Multipath Driver

- Modification details

Version Modification details

V2.0L13 or earlier Does not delete the initial RAM disk and boot loader settings for an Multipath Driver that

V2.0L14 Deletes the initial RAM disk and boot loader settings for an Multipath Driver that will not

- Modification effect

Initial RAM disk settings that are not needed are deleted. The boot loader setting to boot up with this Initial RAM disk is also deleted.

will not be used.

be used.

14

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Release Information

SCSI%u (%u, %u ,%u): SK=0x04 SC=0xf2 SSC=0x%x FRU=0x%x: FRU broken SCSI%u (%u, %u ,%u): SK=0x%x SC=0x%x SSC=0x%x FRU=0x%x SCSI%u (%u, %u ,%u): ERROR=0xf: HBA transport fail fast

■ V2.0L20 modifications

● Modification outline

Added an output message when an I/O error is occurred.

- Modification target

Multipath Driver

- Modification details

Version Modification details

V2.0L14 or earlier In the following conditions, no messages are output even when an I/O error occurs:

• When the storage system responds the sense information below:

Sense key= 0x04, ASC=0xf2, ASCQ=0x00 – 0xff Sense key= 0x06, ASC=0xfb, ASCQ=0x81 – 0x8f

• When the HBA responds "DID_TRANSPORT_FAILFAST".

V2.0L20 In the following conditions, messages are output when an I/O error occurs:

• When the storage system responds the sense information below:

Sense key= 0x04, ASC=0xf2, ASCQ=0x00 – 0xff Sense key= 0x06, ASC=0xfb, ASCQ=0x81 – 0x8f

• When the HBA responds "DID_TRANSPORT_FAILFAST".

The following shows the example of the output message when an I/O error occurs:

- Modification effect

When performing message monitoring, the newly added message may not be monitored as intended. Note that this change does not affect the message monitoring function with Fujitsu middleware.

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

15

Release Information

MPDH%d: NOTICE: %s: Device configuration succeeded.

MPDH%d: WARNING: %s: Device configuration is without redundancy.

MPDH%d: NOTICE: %s: Device configuration is without CFL redundancy. All paths connect to (RT%x, RT%x).

MPDH%d: NOTICE: %s: Device configuration is without CFL redundancy. All paths connect to (CM%x, CM%x).

MPDH%d: NOTICE: %s: Device configuration succeeded.

MPDH%d: WARNING: %s: Device configuration is without redundancy.

MPDH%d: NOTICE: %s: Device configuration is without CFL redundancy. All paths connect to (RT%x, RT%x).

MPDH%d: NOTICE: %s: Device configuration is without CFL redundancy. All paths connect to (CM%x, CM%x).

MPDH%d: WARNING: %s: This path was unrecognizable.

MPDH%d: NOTICE: %s: Device configuration succeeded.

■ V2.0L23 modifications

● Modification outline

Added syslog messages and changed the output timing of syslog messages that are output when starting up a Red Hat Enterprise Linux 5 or SUSE Linux Enterprise Server 10 system.

- Modification target

Multipath Driver

- Modification details

Version Modification details

V2.0L22 or earlier The following syslog messages are sequentially output during system startup:

Note that the following syslog message is output when path redundancy is maintained regardless of whether the path is recognized or not.

V2.0L23 The following syslog messages are sequentially output during system startup:

Note that the following syslog message is output when path redundancy is maintained

- Modification effect

When performing message monitoring, the newly added message may not be monitored as intended. Note that this change does not affect the message monitoring function with Fujitsu middleware.

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

and all the paths are recognized.

16

Release Information

!!! WARNING !!! ETERNUS Multipath Driver is not loaded.

● Modification outline

Added console messages that are output when starting up the system.

- Modification target

Multipath Driver

- Modification details

Version Modification details

V2.0L22 or earlier No messages are output on the console if the Multipath Driver is not loaded when

starting up the system.

V2.0L23 The following message is output on the console if the Multipath Driver is not loaded

when starting up the system:

- Modification effect

When performing message monitoring, the newly added message may not be monitored as intended. Note that this change does not affect the message monitoring function with Fujitsu middleware.

■ V2.0L24 modifications

● Modification outline

Changed the command so that a backup file is created for the initial RAM disk when the "mpdsetup" command is executed.

- Modification target

"mpdsetup" command

- Modification details

Version Modification details

V2.0L23 or earlier If there are no problems with the load order when the "mpdsetup" command is executed:

V2.0L24 If there are no problems with the load order when the "mpdsetup" command is executed:

- Modification effect

A backup file for the initial RAM disk is added under the /boot directory.

the existing initial RAM disk name is used as the file name of ".mpdbak".

If there are problems with the load order when the "mpdsetup" command is executed:

a backup file is not created.

the existing initial RAM disk name is used as the file name of ".mpdbak".

If there are problems with the load order when the "mpdsetup" command is executed:

the existing initial RAM disk name is used as the file name of ".mpdsetup".

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

17

Release Information

● Modification outline

Added conditions that trigger the recreation of the initial RAM disk and restarting of the system when Red Hat Enterprise Linux 9 system, SUSE Linux Enterprise Server 10 system, or SUSE Linux Enterprise Server 11 system starts up.

- Modification target

Multipath Driver

- Modification details

Version Modification details

V2.0L23 or earlier There are problems with the load order of the Multipath Driver modules.

V2.0L24

• There are problems with the load order of the Multipath Driver modules.

• The Multipath Driver modules are not loaded, and the Multipath Driver modules that

correspond to the initial RAM disk that is used at system startup do not exist.

- Modification effect

When the system starts without loading the Multipath Driver modules, recreation of the initial RAM disk and restarting of the system may occur.

Added a service (mpdprerc) to the Multipath Driver.

- Modification target

Multipath Driver

- Modification details

Version Modification details

V2.0L23 or earlier The Multipath Driver has the following two services.

• mpdrc

• mpdstrrc

V2.0L24 The Multipath Driver has the following two services.

• mpdrc

• mpdstrrc

In the following conditions, mpdprerc is added as a service:

• When a server with Red Hat Enterprise Linux 5 is connected to the storage system via

an iSCSI interface

• When Red Hat Enterprise Linux 6 is used

• When a server with SUSE Linux Enterprise Server 10 is connected to the storage

system via an iSCSI interface

• When SUSE Linux Enterprise Server 11 is used and the open-iscsi service is enabled

- Modification effect

A service (mpdprerc) for the Multipath Driver is added to the services that are executed at system startup. Apart from the adding of the services listed above, there is no other affect on servers.

18

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Release Information

MPDH%d: NOTICE: SCSI%u (%u, %u, %u) : I/O rejection. number of online paths left for this LUN =%d.

■ V2.0L25 modifications

● Modification outline

Changed the command so that the offline status is checked for a device when the "iompadm info" command is executed.

- Modification target

"iompadm" command

- Modification details

Version Modification details

V2.0L24 or earlier The offline status is not checked for a device when the "iompadm info" command is

executed.

V2.0L25 The offline status is checked for a device when the "iompadm info" command is

executed. The following syslog message may be output if offline status is detected:

- Modification effect

When performing message monitoring, the newly added message may not be monitored as intended. Note that this change does not affect the message monitoring function with Fujitsu middleware.

● Modification outline

The default Max Throttle setting of the ETERNUS DX60/DX60 S2, DX80/DX80 S2, DX90/DX90 S2 is automated.

- Modification target

Multipath Driver

- Modification details

Version Modification details

V2.0L24 or earlier The default Max Throttle value of the ETERNUS DX60/DX60 S2, DX80/DX80 S2, DX90/

DX90 S2 has to be manually specified.

V2.0L25 The default Max Throttle value of the ETERNUS DX60/DX60 S2, DX80/DX80 S2, DX90/

DX90 S2 is automatically specified.

- Modification effect

When connecting to the ETERNUS DX60/DX60 S2, DX80/DX80 S2, DX90/DX90 S2, Max Throttle does not have to be set with the "mpdconfig -m" command.

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

19

Release Information

Multipath Driver Updates

The following table shows the updates for each Multipath Driver version:

Fibre Channel connections are available for all the supported OSs.

The latest information is provided in the "FUJITSU Storage ETERNUS Multipath Driver V2 (for Linux) Installation Information" found under "Downloads" at the following URL:

http://www.fujitsu.com/global/products/computing/storage/software/eternus-mpd/

(1/5)

Version Modifications

V2.0L01 (May 2005)

V2.0L02 (October 2005)

V2.0L03 (June 2006)

V2.0L10 (February 2007)

The first version.

• The following OSs are supported:

- Red Hat Enterprise Linux AS (v.4 for x86) Update 1

- Red Hat Enterprise Linux ES (v.4 for x86) Update 1

- Red Hat Enterprise Linux AS (v.4 for EM64T) Update 1

- Red Hat Enterprise Linux ES (v.4 for EM64T) Update 1

• The following OSs are supported:

- Red Hat Enterprise Linux AS (v.4 for x86) Update 2

- Red Hat Enterprise Linux ES (v.4 for x86) Update 2

- Red Hat Enterprise Linux AS (v.4 for EM64T) Update 2

- Red Hat Enterprise Linux ES (v.4 for EM64T) Update 2

- Red Hat Enterprise Linux AS (v.4 for Itanium) Update 2

- Red Hat Enterprise Linux AS (v.4 for x86) Update 3

- Red Hat Enterprise Linux ES (v.4 for x86) Update 3

- Red Hat Enterprise Linux AS (v.4 for EM64T) Update 3

- Red Hat Enterprise Linux ES (v.4 for EM64T) Update 3

- SUSE Linux Enterprise Server 9 for x86 Service Pack 3

- SUSE Linux Enterprise Server 9 for EM64T Service Pack 3

- SUSE Linux Enterprise Server 9 for Itanium Processor Family Service Pack 3

• The following storage systems are supported:

- ETERNUS4000 models 80, 100, 300, and 500

- ETERNUS8000 models 700, 900, 1100, and 2100

• The following OSs are supported:

- Red Hat Enterprise Linux AS (v.4 for x86) Update 4

- Red Hat Enterprise Linux ES (v.4 for x86) Update 4

- Red Hat Enterprise Linux AS (v.4 for EM64T) Update 4

- Red Hat Enterprise Linux ES (v.4 for EM64T) Update 4

- Red Hat Enterprise Linux AS (v.4 for Itanium) Update 4

- SUSE Linux Enterprise Server 9 for x86 Service Pack 2

- SUSE Linux Enterprise Server 9 for EM64T Service Pack 2

- SUSE Linux Enterprise Server 9 for Itanium Processor Family Service Pack 2

20

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Release Information

(2/5)

V2.0L11 (May 2007)

V2.0L12 (January 2008)

Version Modifications

• The following OSs are supported:

- Red Hat Enterprise Linux AS (4.5 for x86)

- Red Hat Enterprise Linux ES (4.5 for x86)

- Red Hat Enterprise Linux AS (4.5 for EM64T)

- Red Hat Enterprise Linux ES (4.5 for EM64T)

- Red Hat Enterprise Linux AS (4.5 for Itanium)

- Red Hat Enterprise Linux 5 (for x86)

- Red Hat Enterprise Linux 5 (for Intel64)

- Red Hat Enterprise Linux 5 (for Intel Itanium)

• The following OSs are supported:

- Red Hat Enterprise Linux AS (4.6 for x86)

- Red Hat Enterprise Linux ES (4.6 for x86)

- Red Hat Enterprise Linux AS (4.6 for EM64T)

- Red Hat Enterprise Linux ES (4.6 for EM64T)

- Red Hat Enterprise Linux AS (4.6 for Itanium)

- Red Hat Enterprise Linux 5.1 (for x86)

- Red Hat Enterprise Linux 5.1 (for Intel64)

- Red Hat Enterprise Linux 5.1 (for Intel Itanium)

- SUSE Linux Enterprise Server 9 for x86 Service Pack 4

- SUSE Linux Enterprise Server 9 for EM64T Service Pack 4

- SUSE Linux Enterprise Server 9 for Itanium Processor Family Service Pack 4

- SUSE Linux Enterprise Server 10 Service Pack 1 for x86

- SUSE Linux Enterprise Server 10 Service Pack 1 for EM64T

- SUSE Linux Enterprise Server 10 Service Pack 1 for Itanium Processor Family

• Driver Update Program for Red Hat Enterprise Linux 5 is supported.

• The following storage system is supported:

- ETERNUS2000

• LifeKeeper clustering software with Red Hat Enterprise Linux AS (v.4 for x86) Update

4 and Red Hat Enterprise Linux ES (v.4 for x86) Update 4 is supported.

21

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Release Information

(3/5)

V2.0L13 (June 2009)

V2.0L14 (November 2009)

Version Modifications

• The following OSs are supported:

- Red Hat Enterprise Linux AS (4.7 for x86)

- Red Hat Enterprise Linux ES (4.7 for x86)

- Red Hat Enterprise Linux AS (4.7 for EM64T)

- Red Hat Enterprise Linux ES (4.7 for EM64T)

- Red Hat Enterprise Linux AS (4.7 for Itanium)

- Red Hat Enterprise Linux AS (4.8 for x86)

- Red Hat Enterprise Linux ES (4.8 for x86)

- Red Hat Enterprise Linux AS (4.8 for EM64T)

- Red Hat Enterprise Linux ES (4.8 for EM64T)

- Red Hat Enterprise Linux AS (4.8 for Itanium)

- Red Hat Enterprise Linux 5.2 (for x86)

- Red Hat Enterprise Linux 5.2 (for Intel64)

- Red Hat Enterprise Linux 5.2 (for Intel Itanium)

- Red Hat Enterprise Linux 5.3 (for x86)

- Red Hat Enterprise Linux 5.3 (for Intel64)

- Red Hat Enterprise Linux 5.3 (for Intel Itanium)

- SUSE Linux Enterprise Server 10 Service Pack 2 for x86

- SUSE Linux Enterprise Server 10 Service Pack 2 for EM64T

- SUSE Linux Enterprise Server 10 Service Pack 2 for Itanium Processor Family

• SAS connection of the following OSs is supported:

- Red Hat Enterprise Linux AS (4.7 or later)

- Red Hat Enterprise Linux ES (4.7 or later)

- Red Hat Enterprise Linux 5 (Update 3 or later)

• iSCSI connection of the following OSs is supported:

- SUSE Linux Enterprise Server 9 (Service Pack 3 or later)

• The following storage systems are supported:

- ETERNUS DX60 FC model

- ETERNUS DX80 FC model

- ETERNUS4000 models 400 and 600

- ETERNUS8000 models 800, 1200, and 2200

• The following OSs are supported:

- Red Hat Enterprise Linux 5.4 (for x86)

- Red Hat Enterprise Linux 5.4 (for Intel64)

- Red Hat Enterprise Linux 5.4 (for Intel Itanium)

• The following storage systems are supported:

- ETERNUS DX60 SAS model

- ETERNUS DX80 SAS model

- ETERNUS DX90

- ETERNUS DX400 series

- ETERNUS DX8000 series

22

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Release Information

(4/5)

V2.0L20 (April 2010)

V2.0L21 (February 2011)

V2.0L22 (June 2011)

V2.0L23 (June 2012)

V2.0L24 (February 2013)

Version Modifications

• The following OSs are supported:

- Red Hat Enterprise Linux 5.5 (for x86)

- Red Hat Enterprise Linux 5.5 (for Intel64)

- Red Hat Enterprise Linux 5.5 (for Intel Itanium)

- SUSE Linux Enterprise Server 10 Service Pack 3 for x86

- SUSE Linux Enterprise Server 10 Service Pack 3 for EM64T

- SUSE Linux Enterprise Server 10 Service Pack 3 for Itanium Processor Family

• iSCSI connection of the following OSs is supported:

- Red Hat Enterprise Linux 5 (Update 4 or later)

- SUSE Linux Enterprise Server 10 (Service Pack 2 or later)

• The following storage systems are supported:

- ETERNUS DX60 iSCSI model

- ETERNUS DX80 iSCSI model

• The following OSs are supported:

- Red Hat Enterprise Linux 6 (for x86)

- Red Hat Enterprise Linux 6 (for Intel64)

- SUSE Linux Enterprise Server 11 Service Pack 1 for x86

- SUSE Linux Enterprise Server 11 Service Pack 1 for EM64T

• SAS connection of the following OS is supported:

- SUSE Linux Enterprise Server 10 (Service Pack 3 or later)

• The following OSs are supported:

- Red Hat Enterprise Linux 6.1 (for x86)

- Red Hat Enterprise Linux 6.1 (for Intel64)

• 6G SAS connection of the following OSs is supported:

- Red Hat Enterprise Linux 5 (Update 3 or later)

- Red Hat Enterprise Linux 6

- SUSE Linux Enterprise Server 10 (Service Pack 3 or later)

- SUSE Linux Enterprise Server 11 (Service Pack 1 or later)

• The following OSs are supported:

- SUSE Linux Enterprise Server 11 Service Pack 2 for x86

- SUSE Linux Enterprise Server 11 Service Pack 2 for EM64T

• EFI boot of the following OSs is supported:

- SUSE Linux Enterprise Server 11 (Service Pack 1 or later)

• LifeKeeper is supported for the following OSs:

- Red Hat Enterprise Linux 5 (Update 8 or later)

23

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Release Information

(5/5)

V2.0L25 (October 2013)

V2.0L26 (October 2014)

Version Modifications

• The following OSs are supported:

- SUSE Linux Enterprise Server 11 Service Pack 3 for x86

- SUSE Linux Enterprise Server 11 Service Pack 3 for EM64T

• The TPG Referrals function is supported by the following OSs:

- Red Hat Enterprise Linux 5

- Red Hat Enterprise Linux 6

- SUSE Linux Enterprise Server 10 (Service Pack 1 or later)

- SUSE Linux Enterprise Server 11 (Service Pack 1 or later)

For details, refer to "ETERNUS Web GUI User's Guide ETERNUS DX80 S2/DX90 S2, ETERNUS DX410 S2/DX440 S2, ETERNUS DX8100 S2/DX8700 S2" (tenth edition or later).

• The following OSs are supported:

- Red Hat Enterprise Linux 7 (for Intel64)

• The Storage Cluster function is supported by the following OSs:

- Red Hat Enterprise Linux 5

- Red Hat Enterprise Linux 6

- Red Hat Enterprise Linux 7

- SUSE Linux Enterprise Server 10 (Service Pack 1 or later)

- SUSE Linux Enterprise Server 11 (Service Pack 1 or later)

24

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

List of Figures

Figure 1.1 Sample multipath connection ..................................................................................................................... 33

Figure 3.1 Path status transitions ................................................................................................................................ 40

Figure 3.2 2-path load balancing on a storage system with CM assigned .................................................................... 44

Figure 3.3 4-path load balancing on a storage system with CM assigned .................................................................... 45

Figure 3.4 Multipath load balancing on a storage system with CM not assigned ......................................................... 45

Figure 3.5 2-path failover on a storage system with CM assigned................................................................................ 46

Figure 3.6 4-path failover, active to active ................................................................................................................... 47

Figure 3.7 4-path failover, active to standby................................................................................................................ 47

Figure 3.8 Multipath failover, a storage system with CM not assigned......................................................................... 48

Figure 10.1 Use identical LUNs..................................................................................................................................... 106

Figure 10.2 Start from LUN0......................................................................................................................................... 107

30

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

List of Tables

Table 3.1 Path status values ....................................................................................................................................... 39

Table 3.2 Online path sub-states ................................................................................................................................ 40

Table 3.3 Device identification example..................................................................................................................... 49

Table 3.4 Change unit specification ............................................................................................................................ 51

Table 11.1 "iompadm" command output elements..................................................................................................... 117

Table 11.2 "iompadm" command status detail information........................................................................................ 117

31

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 1

What is Multipath Driver?

This chapter explains the features and operating environment of the Multipath Driver.

1.1 Features

The ETERNUS Disk storage systems, ETERNUS All Flash Array, GR series are storage systems designed to prevent the loss of data and down time due to a drive failure, thus creating a high-speed, high-capacity system with high reliability. Note, however, that even use of a storage system cannot prevent down time if a path failure occurs (HBA, NIC, cable, CA, etc.). The Multipath Driver creates a redundant multipath configuration that switches the failed path over to a standby path, thus allowing continuous operation not only for a disk failure but for a path failure as well. The Multipath Driver connects a storage system and Linux server, with functions to diagnose the path status, and control commands.

Even when multiple HBAs are installed in the server and the configured connection between the server and the storage systems is redundant, an error may occur in the PCI bus of the server depending on the failed part of the HBA. If an error occurs in the PCI bus of the server, access to the server may not be possible or the server may crash. To prevent this situation from occurring, configure a clustering server to continue the operation by switching the cluster to save an HBA.

32

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 1 What is Multipath Driver?

Storage system

HBA

CA

HBA

CA

HBA

CA

Linux server

1.2 Connections

Multipath Driver is used to set up and control multiple connections between the server's HBAs or NICs, and the storage system's CAs. Multipath connections provide greater system control and improve reliability. The following figure illustrates a multipath connection.

● Multi-path connection

Figure 1.1 Sample multipath connection

In a multipath connection, all HBAs or NICs must be of the same type. Fibre Channel Hubs cannot be used. HA Port Devices for ETERNUS3000 model 50 and ETERNUS GR710 can be used.

33

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 2

Multipath Driver System Setup

The following sections describe the steps that must be taken to properly reference the Multipath Driver software for the hardware and software environment. Refer to the software information (readme.pdf) provided on the CD for the installation method of the Multipath Driver, uninstallation method, and the latest notes.

2.1 Accessing the Storage System Disks

Refer to "2.1.1 Using the udev Function" (page 34) and make sure to use the "by-id name" for referring to storage system disks.

When using FUJITSU Software PRIMECLUSTER Global Disk Services with a Red Hat Enterprise Linux AS v.4 environment, a Red Hat Enterprise Linux ES v.4 environment, or a Red Hat Enterprise Linux environment, refer to "2.1.2

Order Setting)" (page 35).

When Using FUJITSU Software PRIMECLUSTER Global Disk Services (Storage System Recognition

2.1.1 Using the udev Function

When using the following OSs, the storage system disks should be referred to using their udev function by-id names.

• Red Hat Enterprise Linux AS v.4 (Update 4 or later)

• Red Hat Enterprise Linux ES v.4 (Update 4 or later)

• Red Hat Enterprise Linux 5

• Red Hat Enterprise Linux 6

• Red Hat Enterprise Linux 7

• SUSE Linux Enterprise Server 10 (Service Pack 1 or later)

• SUSE Linux Enterprise Server 11 (Service Pack 1 or later)

Since OSs other than the ones listed above do not support the udev function, upgrading to OSs that support the udev function is recommended.

Using the by-id names has the following advantages:

• The same device names can be always assigned to the storage system LUs.

The generally used device names (/dev/sda, etc.), may change whenever the server is started, if multiple storage systems are connected to one server via Fibre Channel switch. Storage system failures and LU addition may also cause the device names to change. This does not occur when the by-id names are used.

34

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 2 Multipath Driver System Setup

2.1 Accessing the Storage System Disks

2.1.1.1 Creating by-id Names

Details of how to create by-id names are provided in the "FUJITSU Storage ETERNUS Multipath Driver V2 (for Linux) Installation Information" found under "Downloads" at the following URL:

http://www.fujitsu.com/global/products/computing/storage/software/eternus-mpd/

2.1.1.2 Reference by-id Names

Details of how to check the correspondence between the created by-id names and the usual /dev/sda type names are provided in the "FUJITSU Storage ETERNUS Multipath Driver V2 (for Linux) Installation Information" found under "Downloads" at the following URL:

http://www.fujitsu.com/global/products/computing/storage/software/eternus-mpd/

2.1.1.3 Notes

Notes of how to use by-id names are provided in the "FUJITSU Storage ETERNUS Multipath Driver V2 (for Linux) Installation Information" found under "Downloads" at the following URL:

http://www.fujitsu.com/global/products/computing/storage/software/eternus-mpd/

2.1.2 When Using FUJITSU Software PRIMECLUSTER Global Disk Services (Storage System Recognition Order Setting)

When the following configurations are used, the relation of the device name and the LU may change after every reboot:

• When multiple storage systems are connected to a single server via a Fibre Channel switch

• When multiple connections are created between a single server and a storage system with multiple LUN

mappings, affinity groups, and zones via a Fibre Channel switch

When the relation of the device name (such as /dev/sda) and the LU is changed, FUJITSU Software PRIMECLUSTER Global Disk Services determines that an unanticipated error occurs and suspends access from the server to the LU.

Using the Multipath Driver recognition order setting function can prevent device names changing as described in the above examples.

35

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 2 Multipath Driver System Setup

Procedure

2.1 Accessing the Storage System Disks

• Setting the storage system recognition order can prevent the relation between the device name and the

LU to be changed by a Fibre Channel switch specification. However, this cannot prevent the relation between the device name and the LU to be changed by actual disk failure or LU expansion.

• If this function is used to set the recognition order and a storage system then becomes unrecognizable for

some reason, the storage systems that should be recognized after the failed storage system will not be recognized. For example, if the recognition order is set while three storage systems are connected, and the second storage system fails, the third storage system will not be recognized either, even though it is nominally normal status. This is to avoid the device names (/dev/sda, etc.) changing due to the storage systems being recognized in a different order from the original setting.

• When using Red Hat Enterprise Linux 6, Red Hat Enterprise Linux 7, or SUSE Linux Enterprise Server 11

(Service Pack 1 or later), the recognition order setting function by Multipath Driver cannot be used. The by-id names must be used.

• If the LU that is allocated to LUN0 is changed, the storage system is not recognized. In this case, the rec-

ognition order setting must be cleared before changing the LU.

• For a Storage Cluster configuration, the recognition order setting function cannot be used. The by-id

names must be used.

If only one LUN mapping is set up when a single storage system is connected to the server, it is not necessary to use the recognition order setting function.

2.1.2.1 Setting the Recognition Order

Perform the following procedure to set the recognition order.

1 Execute the "mpdconfig -s" command.

Set the storage system recognition order according to the on-screen instructions. The "mpdconfig" command is installed in the /opt/FJSVmpd/bin directory. Only the root-level user may execute the "mpdconfig" command.

[Example]

# /opt/FJSVmpd/bin/mpdconfig -s

2 Restart the server.

If the recognition order set in Step 1 is different from the current order, the server must be restarted to enable the setting. If the order is unchanged, the server does not need to be restarted.

36

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 2 Multipath Driver System Setup

End of procedure

Procedure

End of procedure

2.2 Multipath Driver Related Log

3 Check the result by the "iompadm info" command.

Check that the storage systems are correctly recognized in the order that was set. For details of the "iompadm info" command, refer to "3.4

[Example]

# /opt/FJSVmpd/bin/iompadm info

2.1.2.2 Clearing the Recognition Order

Perform the following procedure to clear the recognition order.

1 Execute the "mpdconfig -c" command.

Clear the storage system recognition order according to the on-screen instructions.

Multipath Status Display" (page 50).

[Example]

# /opt/FJSVmpd/bin/mpdconfig -c

2.2 Multipath Driver Related Log

Multipath Driver creates the following log files in the /var/opt/FJSVmpd directory.

File name Maximum size Description

mpdstrc (mpdstrc.1, mpdstrc.2)

mpdconfig.log (mpdconfig.log.1, mpdconfig.log.2)

mpdsetup.log (mpdsetup.log.1, mpdsetup.log.2)

Approx. 1MB I/O error information log. When the mpdstrc reaches its maximum

size, the file rotates in the order of mpdstrc.1 and mpdstrc.2.

Approx. 1MB History log of "mpdconfig" command execution. When the

mpdconfig.log reaches its maximum size, the file rotates in the order of mpdconfig.log.1 and mpdconfig.log.2.

Approx. 1MB Installation history log. When the mpdsetup.log reaches its

maximum size, the file rotates in the order of mpdsetup.log.1 and mpdsetup.log.2.

37

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 3

Multipath Driver Functions and Operation

This chapter explains various the Multipath Driver functions and how to use the main commands to operate the functions. The Multipath Driver performs the following functions.

• Automatic multi-path configuration

When the Multipath Driver is installed, and the storage system is connected to a Linux server, the paths are automatically configured to perform path failover and load balancing.

• Failover

If a currently used path fails, the system automatically switches over to another path to access the storage system, allowing the host application to continue normal operation. The Failover function operates differently for each storage system model. For details, refer to section "3.2

44).

• Load balancing

Load balancing (load distribution) is performed on all available paths, improving data performance. The Load Balancing function operates differently for each storage system model. For details, refer to section

"3.2

Load Balancing/Failover" (page

Load Balancing/Failover" (page 44).

• Auto path check

Regular checks are performed on all paths even when they are not being accessed by an application. If an unusable path is detected, it is disconnected from the system and its status is reported to ETERNUS Multipath Manager or recorded in the event log.

• Auto path recovery

Regular checks are also performed on disconnected paths to reconnect those paths that have recovered from their failure. This function reinforces path redundancy and provides increased reliability.

• Path disconnection

You can disconnect a specified path by placing it in Offline status. This allows any necessary maintenance work to be performed. The path can be reconnected after the maintenance.

38

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 3 Multipath Driver Functions and Operation

3.1 Path Management

3.1.1 Path Status

The Multipath Driver manages the status of each path based on whether the path is available for use by user I/O request processes. Current path status can be checked using the "iompadm info" command. (Refer to "3.4

Multipath Status Display" (page 50) for details on iompadm info.)

I/O request ready paths may be classified into the following three ready statuses:

Table 3.1 Path status values

Ready status Description

• Normal operating status (no failures have been detected).

active

standby

warning

• If there are two or more active paths, load balancing is performed between them.

• [active "online"] is displayed by the "iompadm info" command.

• Path is connected to the non-assigned CM, which is (normally) on standby.

• If the assigned CM (active) path fails, the standby path becomes the active path.

• When the assigned CM path returns to active status, this path returns to standby.

• [standby "online"] is displayed by the "iompadm info" command.

• I/O errors have been detected on the path, and it is currently being monitored by Auto Path

Check.

• Warning status paths are checked every minute.

• Each type of error is allowed a certain number of checks. If a path is determined to be usable

before this limit is reached, its status is reverted to active or standby, otherwise its status is changed to fail.

• Warning paths are never used for I/O if an active or standby path is available.

• If no active or standby path is available, a warning path may be used for I/O.

• [active "warning"] or [standby "warning"] is displayed by the "iompadm info" command.

39

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 3 Multipath Driver Functions and Operation

active

standby

fatal fail

(1)

(2)

(3) (4)

(7)

fail

stop

warning

(6)

(5)

(8)

3.1 Path Management

I/O request not-ready paths may be classified into the following three unready statuses:

Table 3.2 Online path sub-states

Unready status Description

• I/O errors have been detected on the path, and Auto Path Check has judged it to be

unusable.

• Fail paths are checked every 10 minutes for replacement of the failed parts.

• If the Auto Path Check detects no problem, the status reverts to warning.

fail

• After replacement of the failed parts, the "iompadm restart" command may be

used to instantly return the path to active/standby status.

• Fail paths will never be used for I/O.

• [fail "error information"] is displayed by the "iompadm info" command (details of

the error appears in "error information").

• Result of the Auto Path Check is constantly switching back and forth between

normal and abnormal, so the appropriate checks cannot be performed.

• Fatal fail paths are not checked.

fatal fail

• After replacement of the failed parts, the "iompadm restart" command must be

used to return the path to active/standby status.

• Fatal fail paths will never be used for I/O.

• [fail "forcible fail"] is displayed by the "iompadm info" command.

• Path has been disconnected by the "iompadm change" command.

• Stop paths are not checked.

• The "iompadm restart" command must be used to return the path to active/standby

stop

status.

• Stop paths will never be used for I/O. However, if no active or standby path is

available, a stop path may be returned to active status for use (unless all paths are stop status).

• [stop "stop by command"] is displayed by the "iompadm info" command.

These path status transitions are shown in the following figure.

Figure 3.1 Path status transitions

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

40

Chapter 3 Multipath Driver Functions and Operation

3.1 Path Management

(1) initialization active/standby

The Multipath Driver automatically configures the path connections at system startup. Paths connected to assigned CMs are automatically set to active. Paths connected to non-assigned CMs are set to standby.

(2)standby  active

When an error in an active path is detected during I/O, or the path status changes from active to stop, the standby path becomes the active path if no other active path is available. When the path connected to the assigned CM is recovered and becomes the active path again, the activated standby path connected to the non-assigned CM returns to standby.

(3)active/standby  warning

When a path error occurs during a normal I/O process or upon checking, the active/standby path status changes to warning. When the path is re-enabled by path checking, the path status returns to active/standby.

(4)warning  fail

When judged as unusable as a result of the warning period checking, path status changes to fail. When the check result is normal for a failed path, its status changes to warning.

(5)warning  fatal fail

When the status stays in warning for a long period of time, or when the status frequently changes between active/standby and warning, it is determined that appropriate checks cannot be performed and the status changes to fatal fail, in which the target is not checked.

(6)fatal fail  active/standby

When a failed path is re-enabled by the "iompadm restart" command, the path status changes back to active/standby. When the status frequently changes between active/standby and warning, it is determined that appropriate checks cannot be performed and the status changes to fatal fail, in which the target is not checked.

(7)active/standby  stop

When the path is disconnected by the "iompadm change" command, the path status changes to stop. When the path is re-enabled by the "iompadm restart" command, the path status changes to active/ standby.

(8)active/standby  fail

When a serious failure is detected in the ordinary I/O process or active/standby check, the path status changes to fail. When the path is re-enabled by the "iompadm restart" command, the path status changes to active/ standby.

When the path status changes, the path connected to the assigned CM becomes active, and the path connected to the non-assigned CM becomes standby. However, if there are no active paths connected to the assigned CM, the path connected to the non-assigned CM will become active.

For SAS connection, the operating path information will disappear (not be displayed in the result of the "iompadm info" command) for "Link Down" paths. This path information will reappear when the link is restored.

41

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 3 Multipath Driver Functions and Operation

3.1 Path Management

3.1.2 Checks and Path Status Transitions

The following three types of checks are performed. The check interval cannot be changed.

Target path status Check interval Post check status Transition trigger

active/standby Checked normal.

active/standby 10 minutes

warning 1 minutes

fail 10 minutes

In the warning status, the transition to another status is determined by the error counter.

■ Check in active/standby

warning Checked failure. 0 < Error counter < 200

fail Checked failure. Error counter == 200

active/standby Checked normal. Error counter == 0

warning Check result: 0 < Error counter < 200

fail Checked failure. Error counter == 200

warning Checked normal. Error counter == 100

fail Checked failure. Error counter == 200

Active/Standby status paths are checked every 10 minutes. When a failure is detected by the check, the status changes to either warning or fail. The warning error counter is determined by the failure cause. The status may change directly to fail if the detected failure is sufficiently serious. The status changes in the same way when an error is detected during a normal I/O process.

■ Check in warning

Warning status paths are checked every minute. When a failure is detected by the check, 10 is added to the error counter. When it is normal, 10 is deducted. If the error counter reaches 0, the status becomes active/standby. If it reaches 200, the status becomes fail.

■ Check in fail

Fail status paths are checked every 10 minutes. When a failure is detected by the check, the status does not change. When it is normal, the error counter is set to 100 and the status becomes warning.

42

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 3 Multipath Driver Functions and Operation

3.1 Path Management

● Example 1

Path status progression when a continuing error is detected by a normal active path I/O process.

Time passed

-activestandby-

0 warning (50) active

1 minutes warning (60) active Check error. 10 added.

::::

10 minutes warning (150) active Check error. 10 added.

::::

14 minutes warning (190) active Check error. 10 added.

15 minutes fail active

Path 1 status Path 2 status Operation

Error in normal I/O process on Path 1. Path 1 status changes to warning, and the error counter is set by the error cause (the minimum value of 50 in this example). Retry after setting Path 2 active for the I/O process.

Check error. 10 added. Error counter reaches 200 and the status changes to fail. Path degradation message is sent to the console.

● Example 2

Auto path recovery operation after a failed path is replaced.

Time passed

- fail active Maintenance replacement procedure completes.

0 to 10 minutes

1 minutes warning (90) active Check normal. 10 deducted.

::::

5 minutes warning (50) active Check normal. 10 deducted.

::::

9 minutes warning (10) active Check normal. 10 deducted.

10 minutes active standby

Path 1 status Path 2 status Operation

Check is performed 10 minutes after completion of the

warning (100) active

maintenance replacement. Post replacement check gives a normal result, so status changes to warning and the error counter is set to 100.

Check normal. 10 deducted. Error counter reaches 0 and the status changes to active. Path 2 reverts to standby.

■ Transition to fatal fail

In the following cases, it is judged that the appropriate check cannot be performed and the path status changes to fatal fail, after which the path will not be checked. A "forcible path degrade" message is sent to the console.

• Path stays in warning status for one hour.

• Within one hour the path status changes from active/standby to warning and back 10 times.

43

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 3 Multipath Driver Functions and Operation

Storage system with CM assigned (2-path)

Linux server

Multipath Driver

I/O request

LUN0

LUN1

CM #0 CM #1

HBA #0 HBA #1

3.2 Load Balancing/Failover

There are two types of storage systems. The first is a storage system whose access paths are assigned to one of the two CMs (hereinafter referred to as "storage system with CM assigned"), the second is a storage system whose access paths are not assigned to a particular CM (hereinafter referred to as "storage system with CM not assigned"). In the storage system with CM assigned, paths that belong to the assigned CM are active and other paths connected to non-assigned CM are standby. In the storage system with CM not assigned, all paths are active, and used to access data. Load balance and failover control operations vary according to the storage system type (whether the storage system has assigned CM or not) and number of paths. For details on which storage systems have assigned CMs or not are provided in the "FUJITSU Storage ETERNUS Multipath Driver V2 (for Linux) Installation Information" found under "Downloads" at the following URL:

http://www.fujitsu.com/global/products/computing/storage/software/eternus-mpd/

3.2.1 Load Balancing

The Multipath Driver uses all active paths to perform load balancing (load distribution) to improve performance.

■ Storage system with CM assigned (2 path connections)

For a storage system with CM assigned (2-path) connection, one path is connected to each controller. Of the two paths, the path connected to the assigned CM is active and the path connected to the nonassigned CM is on standby. If there is only one active path, load balancing is not performed.

Figure 3.2 2-path load balancing on a storage system with CM assigned

44

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 3 Multipath Driver Functions and Operation

Multipath Driver

LU0

I/O request

LU1

Storage system with CM assigned (4-path)

HBA #0 HBA #1 HBA #2 HBA #3

CM #0 CM #1

LU1 Load balance

LU0 Load balance

Linux server

Multipath Driver

LU0

I/O request

LU1

Storage system with CM not assigned

HBA #3HBA #0 HBA #1

CM #0

HBA #2

CM #1

LUN0/1 Load balance

Linux server

3.2 Load Balancing/Failover

■ Storage system with CM assigned (4 path connections)

For a storage system with a 4-path configuration, two paths are connected to each of the two CMs, for a total of four paths. The two paths connected to the assigned CM are active, and load balance control is executed on these two paths. For an 8-path configuration, two paths are connected to each of the four CMs, for a total of eight paths.

Figure 3.3 4-path load balancing on a storage system with CM assigned

■ Storage system with CM not assigned

For a storage system that does not have an assigned CM, there is no concept of standby path, so all connected paths are active, and load balancing is performed over all paths.

Figure 3.4 Multipath load balancing on a storage system with CM not assigned

45

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 3 Multipath Driver Functions and Operation

LU0

I/O request

Storage system with CM assigned (2-path)

CM #0

HBA #0

Multipath Driver

CM #1

HBA #1

Linux server

Failure

Standby pathActive path

3.2 Load Balancing/Failover

3.2.2 Failover

When the Multipath Driver detects that an active path has failed, it switches to another path, disables the bad path, and continues executing the I/O requests. This can prevent the host application from shutting down unnecessarily. Failover operates differently depending on the storage system type, as described below.

■ Storage system with CM assigned (2 path connections)

When an active path becomes unavailable, the standby path is activated to continue processing.

Figure 3.5 2-path failover on a storage system with CM assigned

46

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 3 Multipath Driver Functions and Operation

Multipath Driver

LU0

I/O request

Storage system with CM assigned (4-path or more)

HBA #0 HBA #1 HBA #2

CM #0 CM #1

HBA #3

Linux server

Failure

Active path Active path

Multipath Driver

LU0

I/O request

Storage system with CM assigned (4-path or more)

HBA #0

CM #0

Linux server

Active path

CM #1

HBA #2 HBA #3HBA #1

Standby pathStandby path

Active path

Failure

3.2 Load Balancing/Failover

■ Storage system with CM assigned (4 path or more connections)

• Example 1

In a 4-path connection, when one of two active paths becomes unavailable, processing continues on the remaining active path. Switching to the standby path is not performed because the CM still has one active path available.

Figure 3.6 4-path failover, active to active

• Example 2

If both active paths for a CM become unavailable, a standby path is then switched to active state to continue processing. When there are two or more standby paths, load balancing is also performed.

Figure 3.7 4-path failover, active to standby

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

47

Chapter 3 Multipath Driver Functions and Operation

LU0

Multipath Driver

I/O request

LU1

HBA #3HBA #0 HBA #1

CM #0

HBA #2

CM #1

LU0/1 Load balance

Storage system with CM not assigned

Linux server

Active path Active pathActive pathActive path

Failure

3.2 Load Balancing/Failover

■ Storage system with CM not assigned

When an active path becomes unavailable, it is disabled, leaving the remaining paths to continue load balancing in a degraded state.

Figure 3.8 Multipath failover, a storage system with CM not assigned

48

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 3 Multipath Driver Functions and Operation

DISK: ETERNUS_DXL- 130011-0000-0000 (sdb)

LUN_V Magic code Serial number/Device identification no. Storage system name

DISK: ETERNUS_DXL- 130011-0000-0000 (sdb) PATH:

sdb 0000:03:04.0 active "online" 10, 10, 0 <- path identifier sdb 0000:03.05.0 standby "online" 11, 11, 2

3.3 Identifying Disks and Paths

3.3.1 Device Identification

A storage system Logical Unit (LU) in a multipath configuration can be recognized by the Multipath Driver using the "iompadm info" command.

Example:

Table 3.3 Device identification example

Disk ID segment Description

Storage system name The model name of the connected storage system

Serial number/Device identification no.

Magic code Used by the Multipath Driver for internal control

LUN_V LUN_V of the logical unit

The above information allows you to confirm the connected storage system and the recognized LUN_Vs.

3.3.2 Path Identification

Path connections and status between the Multipath Driver and the storage system can be monitored using the "iompadm info" command. In the following example, the path identifier has been outlined.

Example:

The 3rd number is called the port number. Details of the port numbers (CAID) of each storage system model and their connections are provided in the "FUJITSU Storage ETERNUS Multipath Driver V2 (for Linux) Installation Information" found under "Downloads" at the following URL:

Unique serial number ID or Device identification no. of the connected storage system

http://www.fujitsu.com/global/products/computing/storage/software/eternus-mpd/

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

49

Chapter 3 Multipath Driver Functions and Operation

3.4 Multipath Status Display

You can also use the "iompadm info" command to display the status of multiple paths for a device. The "iompadm" command is installed in the /opt/FJSVmpd/bin directory. Only a root-level user may execute the "iompadm" command.

3.4.1 "iompadm info" Command

Use the "iompadm info" command to display the status of multiple paths. When a disk_device_node is specified, the path status for the specified storage system is displayed. A disk_device_node represented by a special file (/dev/sdb, /dev/sdc, etc.) indicates the connection point

between a disk device and the storage system device.

iompadm info [disk_device_node]

The output of the command appears as follows:

IOMP: Control_unit Element: DISK: disk_device_id (disk_device_name) PATH: disk_device_name PCI_bus_number path_status status_details path_id

path_status: "active", "standby", "stop", or "fail" is displayed. status_details: "online", "warning", "stop by command", or an error message is displayed.

[Output example]

# /opt/FJSVmpd/bin/iompadm info

IOMP:vhba0 Element: DISK: ETERNUS_DXL- 130011-0000-0000 (sdb) PATH: sdb 0000:03:04.0 active "online" 10, 10, 0 sdb 0000:03:05.0 standby "online" 11, 11, 2

DISK: ETERNUS_DXL- 130011-0000-0001 (sdc) PATH: sdc 0000:03:04.0 active "online" 10, 10, 0 sdc 0000:03:05.0 standby "online" 11, 11, 2

50

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 3 Multipath Driver Functions and Operation

3.5 Disconnecting/Reconnecting Paths when Replacing Hardware

When performing maintenance, you can disconnect and/or reconnect a specified path using the "iompadm" command.

3.5.1 "iompadm change" Command

Use the "iompadm change" command to change a path's status to stop.

[Command format]

iompadm change [change_unit] disk_device_node port_number

When "adapter" is specified as the change unit, the following is also available:

iompadm change adapter PCI_bus_number

[Function overview]

This command is used in preparation for hardware hot replacement. It disconnects all paths that use the target hardware (specified by change unit, disk device node, and port number), and stops any I/O processes. If a change unit is not specified, the process is performed as if "controller" had been specified. Disk device node and port number can be checked from the output result of the "iompadm info" command. This command changes an active, standby, or warning status path to stop status. This command cannot change a fail or fatal fail status path to stop status.

[Example]

# /opt/FJSVmpd/bin/iompadm change controller /dev/sdb 30

[Change unit specification]

Table 3.4 Change unit specification

adapter (a) Use this when replacing a cable between an HBA and Switch or SFP connected to

the cable.

controller (c) (default) Use this when replacing a cable directly connecting an HBA and CA, or a cable

between a CA and Switch, or a SFP connected to the cable.

controllerunit (cu) Use this when replacing a Channel Adapter.

groupmodule (g) Use this when replacing a group module.

Details of the relationship between change units and storage systems are provided in the "FUJITSU Storage ETERNUS Multipath Driver V2 (for Linux) Installation Information" found under "Downloads" at the following URL:

http://www.fujitsu.com/global/products/computing/storage/software/eternus-mpd/

51

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 3 Multipath Driver Functions and Operation

Procedure

End of procedure

3.6 Multipath Recovery

3.5.2 "iompadm restart" Command

Use the "iompadm restart" command to reinstate the active/standby status.

[Command format]

iompadm restart [change_unit] disk_device_node port_number

When "adapter" is specified as the change unit, the following is also available:

iompadm restart adapter PCI_bus_number

[Function overview]

This command is used to tidy up after hardware hot replacement. It recovers all paths that use the target hardware (specified by change unit, disk device node, and port number). If a change unit is not specified, the process is performed as if "controller" had been specified. Disk device node and port number can be checked from the output result of the "iompadm info" command. This command changes a fail, fatal fail or stop status path to active/standby. To change a warning status path to active/standby, change its status to stop status using the "iompadm change" command, and then use the "iompadm restart" command.

[Example]

# /opt/FJSVmpd/bin/iompadm restart controller /dev/sdb 30

[Change unit specification]

Refer to "3.5.1

"iompadm change" Command" (page 51).

3.6 Multipath Recovery

Perform the following procedure to recover from a path failure in a multipath configuration by using the "iompadm" command.

1 Use the "iompadm info" command to identify the failed path. 2 Perform the necessary maintenance (change HBAs, cables, CAs, etc.) on the failed path. 3 Use the "iompadm restart" command to switch the recovered path back to an active/standby

status.

For details on using the "iompadm restart" command, refer to "3.5.2 "iompadm restart" Command" (page 52).

Reboot the server when the "iompadm restart" command is executed for a path for which "I/O rejection" is displayed as the "iompadm info" result but this path fails to recover.

52

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 4

Changing the Multipath Configuration (FC/FCoE Connection for RHEL-AS4, RHEL-ES4, RHEL5, SLES9, or SLES10)

The procedure to change the multipath configuration varies depending on the OS that is used. In this chapter, the multipath configuration of the following OSs is described:

• Red Hat Enterprise Linux AS v.4

• Red Hat Enterprise Linux ES v.4

• Red Hat Enterprise Linux 5

• SUSE Linux Enterprise Server 9 (Service Pack 2 or later)

• SUSE Linux Enterprise Server 10 (Service Pack 1 or later)

When using the following OSs, refer to "Chapter 7

for RHEL6, RHEL7, or SLES11)" (page 82).

• Red Hat Enterprise Linux 6

• Red Hat Enterprise Linux 7

• SUSE Linux Enterprise Server 11 (Service Pack 1 or later)

The multipath configuration can be changed using the "mpdconfig" command. The "mpdconfig" command is installed in the /opt/FJSVmpd/bin directory. Only a root-level user may execute the "mpdconfig" command. This chapter describes how to change multipath configuration for FC/FCoE connection.

• When by-id names are not used, changing the multipath configuration may change the device names.

• Before starting an addition process, use the "iompadm info" command to check that the existing devices

are in normal status.

• Before starting a reduction process, check that the device not to be reduced is in normal status.

Changing the Multipath Configuration (FC/FCoE Connection

53

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 4 Changing the Multipath Configuration (FC/FCoE Connection for RHEL-AS4, RHEL-ES4, RHEL5, SLES9, or SLES10)

Procedure

4.1 Storage System and LU Addition

4.1.1 Addition without Server Rebooting

Using the "mpdconfig" command, extra storage systems and LUs can be added without shutting down the server. Use the following procedure.

1 Attach the hardware.

Proceed as follows, depending on the addition target.

• Storage system addition

Set up the storage system so that its LUs are accessible to the server, and then connect it to the server. For details on the settings, refer to the storage system manual.

Red Hat Enterprise Linux AS v.4, Red Hat Enterprise Linux ES v.4, and SUSE Linux Enterprise Server 9 require the server be rebooted for storage system addition.

• LU addition

Add a LU in the storage system. For details on adding LUs, refer to the storage system manual.

When adding LUs without server rebooting, make sure that all paths are in online status.

2 Incorporate the new hardware using the "mpdconfig -a" command.

[Example]

# /opt/FJSVmpd/bin/mpdconfig -a

The "iompadm rescan" command can also be used to incorporate the new hardware.

[Example]

# /opt/FJSVmpd/bin/iompadm rescan

3 When a new storage system is added, an enquiry is sent regarding the storage system

recognition order.

If by-id names are not being used, or are being used with FUJITSU Software PRIMECLUSTER Global Disk Services installed, follow the on-screen instructions.

54

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 4 Changing the Multipath Configuration (FC/FCoE Connection for RHEL-AS4, RHEL-ES4, RHEL5, SLES9, or SLES10)

End of procedure

4.1 Storage System and LU Addition

4 Use the "iompadm info" command to check that the new hardware has been correctly

recognized and incorporated.

[Example]

# /opt/FJSVmpd/bin/iompadm info

When a LU is added, it is initially added as a new SCSI disk device after the LUs that have already been incorporated. However, after the system is restarted, the newly added LU is incorporated into the system according to the storage system LU number. Therefore, to access the SCSI disk via a sd* device name, add the LU so that it has the same device name before and after the system restart. If by-id names are used, this problem does not occur.

5 If a storage system has been added, set its Max Throttle value.

Execute the "mpdconfig -m" command to set a Max Throttle value for the new storage system. Refer to the software information (/opt/FJSVmpd/manual/english/readme.pdf) for the Max Throttle value computation method.

[Example]

# /opt/FJSVmpd/bin/mpdconfig -m

55

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 4 Changing the Multipath Configuration (FC/FCoE Connection for RHEL-AS4, RHEL-ES4, RHEL5, SLES9, or SLES10)

Procedure

4.1 Storage System and LU Addition

4.1.2 Addition with Server Rebooting

Use the following procedure to add extra storage systems and LUs while the server is shut down:

When adding storage systems and LUs, the device names (sd*) may be changed. Alter the settings for any applications and OSs that access to the storage system as necessary. If by-id names are used, this problem does not occur.

1 When adding storage systems to a configuration in which "by-id names" are not used or "by-

id names" are used with FUJITSU Software PRIMECLUSTER Global Disk Services installed, set the recognition order for the storage systems that have already been recognized.

If it has already been set, the recognition order does not need to be set again. Execute the "mpdconfig -s" command to set the recognition order.

[Example]

# /opt/FJSVmpd/bin/mpdconfig -s

2 Shut down the server. 3 Attach the hardware.

Proceed as follows, depending on the addition target.

• Storage system addition

Set up the storage system so that its LUs are accessible to the server, and then connect it to the server. For details on the settings, refer to the storage system manual.

• LU addition

Add a LU in the storage system. For details on adding LUs, refer to the storage system manual.

4 Restart the server.

Power on the server and boot it up.

5 Use the "iompadm info" command to check that the new hardware has been correctly

recognized and incorporated.

[Example]

# /opt/FJSVmpd/bin/iompadm info

6 When a storage system has been added, set its Max Throttle value.

Execute the "mpdconfig -m" command to set a Max Throttle value for the new storage system. Refer to the software information (/opt/FJSVmpd/manual/english/readme.pdf) for the Max Throttle value computation method.

[Example]

# /opt/FJSVmpd/bin/mpdconfig -m

56

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 4 Changing the Multipath Configuration (FC/FCoE Connection for RHEL-AS4, RHEL-ES4, RHEL5, SLES9, or SLES10)

End of procedure

Procedure

4.2 Storage System and LU Reduction

7 When a new storage system is added without using the by-id names, or using the by-id

names with FUJITSU Software PRIMECLUSTER Global Disk Services installed, execute the "mpdconfig -s" command to set the recognition order that includes new storage systems.

[Example]

# /opt/FJSVmpd/bin/mpdconfig -s

4.2 Storage System and LU Reduction

4.2.1 Reduction without Server Rebooting

Using the "mpdconfig" command, storage systems and LUs can be removed without shutting down the server. Use the following procedure.

• Red Hat Enterprise Linux AS v.4, Red Hat Enterprise Linux ES v.4, and SUSE Linux Enterprise Server 9

require the server be rebooted for storage system and LU reduction.

• When removing the storage systems and LUs without server rebooting, completely halt all access to the

storage systems or LUs that are to be removed. If access cannot be halted, follow the procedures described in "4.2.2

• Never attempt to remove LU0.

Reduction with Server Rebooting" (page 58).

1 Detach the hardware.

Proceed as follows, depending on the reduction target.

• Storage system reduction

Disconnect the target storage system from the server (turn the storage system power off, disconnect the cables, etc.).

• LU reduction

Perform LU reduction in the storage system (so that the server cannot recognize the LU). Refer to the storage system manual for LU reduction details.

2 Delete the removed hardware from the Multipath Driver target list using the "mpdconfig -d"

command.

[Example]

# /opt/FJSVmpd/bin/mpdconfig -d

57

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 4 Changing the Multipath Configuration (FC/FCoE Connection for RHEL-AS4, RHEL-ES4, RHEL5, SLES9, or SLES10)

End of procedure

Procedure

4.2 Storage System and LU Reduction

3 If a storage system is removed and the recognition order function is being used, execute the

"mpdconfig -s" command to reconfigure the recognition order.

[Example]

# /opt/FJSVmpd/bin/mpdconfig -s

However, if the storage system reduction reduces the number of storage systems connected to the server to one or less, execute the "mpdconfig -c" command to clear the recognition order setting instead.

[Example]

# /opt/FJSVmpd/bin/mpdconfig -c

4 Use the "iompadm info" command to check that the removed hardware has disappeared

from view.

[Example]

# /opt/FJSVmpd/bin/iompadm info

If SCSI disks are accessed using sd* device name, the deleted LUs will cause the device names to not match after the server is restarted. Alter the OS and application settings as necessary. If by-id names are used, this problem does not occur.

4.2.2 Reduction with Server Rebooting

Use the following procedure to remove storage systems and LUs while the server is shut down.

Never attempt to remove LU0.

1 If the storage system recognition order has been set, change the settings before removing

the storage system.

• When the storage system reduction reduces the number of storage systems connected to the server

to one or less, execute the "mpdconfig -c" command to clear the storage system recognition order.

[Example]

# /opt/FJSVmpd/bin/mpdconfig -c

58

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 4 Changing the Multipath Configuration (FC/FCoE Connection for RHEL-AS4, RHEL-ES4, RHEL5, SLES9, or SLES10)

4.2 Storage System and LU Reduction

• When the storage system reduction reduces the number of storage systems connected to the server

to more than one, execute the "mpdconfig -s" command to set the recognition order of the storage system that is to be removed to last place. If not, the storage systems with a lower recognition order may not be recognized after rebooting.

[Example]

# /opt/FJSVmpd/bin/mpdconfig -s

If SCSI disks are accessed using sd* device names then when the server is restarted after changing the storage system recognition order, the device names will also change. Alter the OS and application settings as necessary. If by-id names are used, this problem does not occur.

2 Shut down the server. 3 Detach the hardware.

Proceed as follows, depending on the reduction target.

• Storage system reduction

Disconnect the target storage system from the server (turn the storage system power off, disconnect the cables, etc.).

• LU reduction

Perform LU reduction in the storage system (release the LU configuration so that the server does not recognize the LU). Refer to the storage system manual for LU reduction details.

If SCSI disks are accessed using sd* device names then when the server is restarted after changing the storage system recognition order, the device names will also change. Alter the OS and application settings as necessary. If by-id names are used, this problem does not occur.

4 Restart the server.

Power on the server and boot it up.

5 Use the "iompadm info" command to check that the removed hardware is displayed as "fail".

[Example]

# /opt/FJSVmpd/bin/iompadm info

6 Delete the removed hardware from the Multipath Driver target list using the "mpdconfig -d"

command.

[Example]

# /opt/FJSVmpd/bin/mpdconfig -d

7 If a storage system is removed and the recognition order function is being used, execute the

"mpdconfig -s" command to reconfigure the recognition order.

[Example]

# /opt/FJSVmpd/bin/mpdconfig -s

59

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 4 Changing the Multipath Configuration (FC/FCoE Connection for RHEL-AS4, RHEL-ES4, RHEL5, SLES9, or SLES10)

End of procedure

Procedure

End of procedure

4.3 Path Addition (Cable Addition)

8 Use the "iompadm info" command to check the results.

[Example]

# /opt/FJSVmpd/bin/iompadm info

4.3 Path Addition (Cable Addition)

This section describes how to increase the paths by adding cables.

4.3.1 Addition without Server Rebooting

Using the "mpdconfig" command, cables can be added without shutting down the server. Use the following procedure.

Red Hat Enterprise Linux AS v.4, Red Hat Enterprise Linux ES v.4, and SUSE Linux Enterprise Server 9 require the server be rebooted for cable addition.

1 Attach the hardware.

Set up the storage system so that its LUs are accessible via the cable, and then connect the cable between the server and the storage system (an HBA must already be installed in the server). For details on the settings, refer to the storage system manual.

2 Use the "iompadm info" command to check that the new cable has been correctly

recognized and incorporated.

[Example]

# /opt/FJSVmpd/bin/iompadm info

3 Set a Max Throttle value for the new path.

Execute the "mpdconfig -m" command to set a Max Throttle value for the new path. Refer to the software information (/opt/FJSVmpd/manual/english/readme.pdf) for the Max Throttle value computation method.

[Example]

# /opt/FJSVmpd/bin/mpdconfig -m

60

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 4 Changing the Multipath Configuration (FC/FCoE Connection for RHEL-AS4, RHEL-ES4, RHEL5, SLES9, or SLES10)

Procedure

End of procedure

4.3 Path Addition (Cable Addition)

4.3.2 Addition with Server Rebooting

Use the following procedure to add extra cables while the server is shut down.

1 Shut down the server. 2 Attach the hardware.

Set up the storage system so that its LUs are accessible via the cable, and then connect the cable between the server and the storage system (an HBA must already be installed in the server). For details on the settings, refer to the storage system manual.

3 Restart the server.

Power on the server and boot it up.

4 Use the "iompadm info" command to check that the new cable has been correctly

recognized and incorporated.

[Example]

# /opt/FJSVmpd/bin/iompadm info

5 Set a Max Throttle value for the new path.

Execute the "mpdconfig -m" command to set a Max Throttle value for the new path. Refer to the software information (/opt/FJSVmpd/manual/english/readme.pdf) for the Max Throttle value computation method.

[Example]

# /opt/FJSVmpd/bin/mpdconfig -m

61

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 4 Changing the Multipath Configuration (FC/FCoE Connection for RHEL-AS4, RHEL-ES4, RHEL5, SLES9, or SLES10)

Procedure

End of procedure

4.4 Path Reduction (Cable Reduction)

This section describes how to decrease the paths by removing cables.

4.4.1 Reduction without Server Rebooting

Using the "mpdconfig" command, cables can be removed without shutting down the server. Use the following procedure.

Red Hat Enterprise Linux AS v.4, Red Hat Enterprise Linux ES v.4, and SUSE Linux Enterprise Server 9 require the server be rebooted for cable reduction.

1 Detach the hardware.

Disconnect the target cable from the server (remove the connected cable, etc.).

2 Delete the removed cable from the Multipath Driver target list using the "mpdconfig -d"

command.

[Example]

# /opt/FJSVmpd/bin/mpdconfig -d

3 Use the "iompadm info" command to check that the removed cable has disappeared from

view.

[Example]

# /opt/FJSVmpd/bin/iompadm info

4 Reset the Max Throttle value if necessary.

When the number of paths connected to a given CA port in the storage system is reduced due to the path removal, execute the "mpdconfig -m" command to set the Max Throttle value correctly. Refer to the software information (/opt/FJSVmpd/manual/english/readme.pdf) for the Max Throttle value computation method.

62

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 4 Changing the Multipath Configuration (FC/FCoE Connection for RHEL-AS4, RHEL-ES4, RHEL5, SLES9, or SLES10)

Procedure

End of procedure

4.4 Path Reduction (Cable Reduction)

4.4.2 Reduction with Server Rebooting

Use the following procedure to remove cables while the server is shut down.

1 Shut down the server. 2 Detach the hardware.

Disconnect the target cable from the server (remove the connected cable, etc.).

3 Restart the server.

Power on the server and boot it up.

4 Use the "iompadm info" command to check that the removed cable is displayed as "fail".

[Example]

# /opt/FJSVmpd/bin/iompadm info

5 Delete the removed cable from the Multipath Driver target list using the "mpdconfig -d"

command.

[Example]

# /opt/FJSVmpd/bin/mpdconfig -d

6 Use the "iompadm info" command to check the results.

[Example]

# /opt/FJSVmpd/bin/iompadm info

7 Reset the Max Throttle value if necessary.

When the number of paths connected to a given CA port in the storage system is reduced due to the path removal, execute the "mpdconfig -m" command to set the Max Throttle value correctly. Refer to the software information (/opt/FJSVmpd/manual/english/readme.pdf) for the Max Throttle value computation method.

63

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 4 Changing the Multipath Configuration (FC/FCoE Connection for RHEL-AS4, RHEL-ES4, RHEL5, SLES9, or SLES10)

4.5 Path Addition and Reduction (HBA Addition and Reduction)

This section describes how to increase paths by adding HBAs, and decrease paths by removing HBAs. Adding and reducing HBAs without server rebooting (PCI Hot Plug) is only supported for PRIMEQUEST servers. For details on this procedure, refer to the PRIMEQUEST manual. Adding and reducing HBAs with server rebooting is the same procedure as adding and reducing cables with server rebooting. Add or reduce HBAs at the same time that cables are being added or reduced. When a HBA is added, execute the "mpdconfig -m" command to set the Max Throttle values for the new path. Refer to the software information (/opt/FJSVmpd/manual/english/readme.pdf) for the Max Throttle value computation method.

64

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 5

Changing the Multipath Configuration (SAS Connection for RHEL-AS4, RHEL-ES4, RHEL5, or SLES10)

The procedure to change the multipath configuration varies depending on the type of OS that is used. In this chapter, the multipath configuration of the following OSs is described:

• Red Hat Enterprise Linux AS (4.6 or later)

• Red Hat Enterprise Linux ES (4.6 or later)

• Red Hat Enterprise Linux 5 (Update 3 or later)

• SUSE Linux Enterprise Server 10 (Service Pack 3 or later)

When using the following OSs, refer to "Chapter 8

RHEL6, RHEL7, or SLES11)" (page 94).

• Red Hat Enterprise Linux 6

• Red Hat Enterprise Linux 7

• SUSE Linux Enterprise Server 11 (Service Pack 1 or later)

The multipath configuration can be changed using the "mpdconfig" command. The "mpdconfig" command is installed in the /opt/FJSVmpd/bin directory. Only a root-level user may execute the "mpdconfig" command. This chapter describes how to change multipath configuration for SAS connection.

• When by-id names are not used, changing the multipath configuration may change the device names.

• Before starting an addition process, use the "iompadm info" command to check that the existing devices

are in normal status.

• Before starting a reduction process, check that the device not to be reduced is in normal status.

Changing the Multipath Configuration (SAS Connection for

65

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 5 Changing the Multipath Configuration (SAS Connection for RHEL-AS4, RHEL-ES4, RHEL5, or SLES10)

Procedure

End of procedure

5.1 Storage System Addition

5.1.1 Addition without Server Rebooting

Extra storage systems can be added without shutting down the server. Use the following procedure.

1 Attach the hardware.

Set up the storage system so that its LUs are accessible to the server, and then connect it to the server. For details on the settings, refer to the storage system manual.

2 Use the "iompadm info" command to check the result.

When the new storage system is connected to the server, it should be automatically recognized and incorporated in the list.

[Example]

# /opt/FJSVmpd/bin/iompadm info

3 Set its Max Throttle value.

Execute the "mpdconfig -m" command to set a Max Throttle value for the new storage system. Refer to the software information (/opt/FJSVmpd/manual/english/readme.pdf) for the Max Throttle value computation method.

[Example]

# /opt/FJSVmpd/bin/mpdconfig -m

4 If by-id names are not being used, or are being used with FUJITSU Software PRIMECLUSTER

Global Disk Services installed, use the "mpdconfig -s" command to set the recognition order.

[Example]

# /opt/FJSVmpd/bin/mpdconfig -s

5.1.2 Addition with Server Rebooting

Same as for FC/FCoE connection. Refer to "4.1.2

Addition with Server Rebooting" (page 56).

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

66

Chapter 5 Changing the Multipath Configuration (SAS Connection for RHEL-AS4, RHEL-ES4, RHEL5, or SLES10)

Procedure

End of procedure

5.2 Storage System Reduction

5.2.1 Reduction without Server Rebooting

Storage systems can be removed without shutting down the server. Use the following procedure.

When removing the storage systems without server rebooting, completely halt all access to the storage systems or LUs that are to be removed. If access cannot be halted, follow the procedures described in "5.2.2

Reduction with Server Rebooting" (page 67).

1 Disconnect all cables to the server.

Disconnect all the SAS cables that connect the server to the storage system that is to be reduced.

2 Use the "iompadm info" command to check the result.

When the cables are removed, the disconnected storage system should be automatically removed and disappear from the list.

[Example]

# /opt/FJSVmpd/bin/iompadm info

3 If a storage system is removed and the recognition order function is being used, execute the

"mpdconfig -s" command to reconfigure the recognition order.

[Example]

# /opt/FJSVmpd/bin/mpdconfig -s

However, if the storage system reduction reduces the number of storage systems connected to the server to one or less, execute the "mpdconfig -c" command to clear the recognition order setting instead.

[Example]

# /opt/FJSVmpd/bin/mpdconfig -c

5.2.2 Reduction with Server Rebooting

Same as for FC/FCoE connection. Refer to "4.2.2

Reduction with Server Rebooting" (page 58).

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

67

Chapter 5 Changing the Multipath Configuration (SAS Connection for RHEL-AS4, RHEL-ES4, RHEL5, or SLES10)

Procedure

5.3 LU Addition

Same as for FC/FCoE connection. Refer to "4.1

Storage System and LU Addition" (page 54).

5.4 LU Reduction

Same as for FC/FCoE connection. Refer to "4.2

Storage System and LU Reduction" (page 57).

5.5 Path Addition (Cable Addition)

This section describes how to increase the paths by adding cables.

5.5.1 Addition without Server Rebooting

Cables can be added without shutting down the server. Use the following procedure.

1 Attach the hardware.

Set up the storage system so that its LUs are accessible via the cable, and then connect the cable between the server and the storage system (an HBA must already be installed in the server). For details on the settings, refer to the storage system manual.

2 Use the "iompadm info" command to check the result.

When the cables are connected, the storage system should be automatically recognized and the cables added to the list.

[Example]

# /opt/FJSVmpd/bin/iompadm info

3 Set a Max Throttle value for the new path.

Execute the "mpdconfig -m" command to set a Max Throttle value for the new path. Refer to the software information (/opt/FJSVmpd/manual/english/readme.pdf) for the Max Throttle value computation method.

68

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 5 Changing the Multipath Configuration (SAS Connection for RHEL-AS4, RHEL-ES4, RHEL5, or SLES10)

End of procedure

Procedure

End of procedure

5.6 Path Reduction (Cable Reduction)

[Example]

# /opt/FJSVmpd/bin/mpdconfig -m

5.5.2 Addition with Server Rebooting

Same as for FC/FCoE connection. Refer to "4.3.2

Addition with Server Rebooting" (page 61).

5.6 Path Reduction (Cable Reduction)

This section describes how to decrease the paths by removing cables.

5.6.1 Reduction without Server Rebooting

Cables can be removed without shutting down the server. Use the following procedure.

1 Disconnect the surplus cables from the server. 2 Use the "iompadm info" command to check the result.

When the cables are disconnected, they should be automatically removed and disappear from the list.

[Example]

# /opt/FJSVmpd/bin/iompadm info

3 Reset the Max Throttle value if necessary.

When the number of paths connected to a given CA port in the storage system is reduced due to the path removal, execute the "mpdconfig -m" command to set the Max Throttle value correctly. Refer to the software information (/opt/FJSVmpd/manual/english/readme.pdf) for the Max Throttle value computation method.

5.6.2 Reduction with Server Rebooting

Same as for FC/FCoE connection. Refer to "4.4.2

Reduction with Server Rebooting" (page 63).

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

69

Chapter 5 Changing the Multipath Configuration (SAS Connection for RHEL-AS4, RHEL-ES4, RHEL5, or SLES10)

5.7 Path Addition and Reduction (HBA Addition and Reduction)

This section describes how to increase paths by adding HBAs, and decrease paths by removing HBAs. Adding and reducing HBAs without server rebooting (PCI Hot Plug) is not supported. Adding and reducing HBAs with server rebooting is the same procedure as adding and reducing cables with server rebooting. Add or reduce HBAs at the same time that cables are being added or reduced.

70

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 6

Changing the Multipath Configuration (iSCSI Connection for RHEL5, SLES9, or SLES10)

The procedure to change the multipath configuration varies depending on the type of OS that is used. In this chapter, the multipath configuration of the following OSs is described:

• Red Hat Enterprise Linux 5 (Update 4 or later)

• SUSE Linux Enterprise Server 9 (Service Pack 3 or later)

• SUSE Linux Enterprise Server 10 (Service Pack 2 or later)

When using the following OSs, refer to "Chapter 9

RHEL6, RHEL7, or SLES11)" (page 98).

• Red Hat Enterprise Linux 6

• Red Hat Enterprise Linux 7

• SUSE Linux Enterprise Server 11 (Service Pack 1 or later)

The multipath configuration can be changed using the "mpdconfig" command. The "mpdconfig" command is installed in the /opt/FJSVmpd/bin directory. Only a root-level user may execute the "mpdconfig" command. This chapter describes how to change multipath configuration for iSCSI connection.

• When by-id names are not used, changing the multipath configuration may change the device names.

• Before starting an addition process, use the "iompadm info" command to check that the existing devices

are in normal status.

• Before starting a reduction process, check that the device not to be reduced is in normal status.

Changing the Multipath Configuration (iSCSI Connection for

71

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 6 Changing the Multipath Configuration (iSCSI Connection for RHEL5, SLES9, or SLES10)

Procedure

End of procedure

6.1 Storage System Addition

6.1.1 For Red Hat Enterprise Linux 5 or SUSE Linux Enterprise Server 10

Use the following procedure to add extra storage systems.

When adding storage systems, the device names (sd*) may be changed. Alter the settings for any applications and OSs that access to the storage system as necessary. If by-id names are used, this problem does not occur.

1 Attach the hardware.

Set up the storage system so that its LUs are accessible to the server, and then connect it to the server. For details on the settings, refer to the storage system manual.

2 Set the server iSCSI service.

Set iSCSI initiator/iSCSI target information and log in to the iSCSI target. Make sure that automatic login to the iSCSI target has been specified. Refer to storage systems User's Guide -Server Connection- or any other relevant manuals and "Appendix 2" in the software information (/opt/FJSVmpd/manual/english/ readme.pdf) for details about iSCSI connection.

3 Use the "iompadm info" command to check the result.

The new storage system should be automatically recognized and incorporated in the list.

[Example]

# /opt/FJSVmpd/bin/iompadm info

4 Set its Max Throttle value.

Execute the "mpdconfig -m" command to set a Max Throttle value for the new storage system. Refer to the software information (/opt/FJSVmpd/manual/english/readme.pdf) for the Max Throttle value computation method.

[Example]

# /opt/FJSVmpd/bin/mpdconfig -m

5 If by-id names are not being used, or are being used with FUJITSU Software PRIMECLUSTER

Global Disk Services installed, use the "mpdconfig -s" command to set the recognition order.

[Example]

# /opt/FJSVmpd/bin/mpdconfig -s

72

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 6 Changing the Multipath Configuration (iSCSI Connection for RHEL5, SLES9, or SLES10)

Procedure

6.1 Storage System Addition

6.1.2 For SUSE Linux Enterprise Server 9

Use the following procedure to add extra storage systems.

When adding storage systems, the device names (sd*) may be changed. Alter the settings for any applications and OSs that access to the storage system as necessary.

1 Set the storage system recognition order.

If it has already been set, the recognition order does not need to be set again. Execute the "mpdconfig -s" command to set the recognition order.

[Example]

# /opt/FJSVmpd/bin/mpdconfig -s

2 Set the server iSCSI service.

Set an iSCSI initiator and add the IP addresses of the storage systems to be added to the iSCSI initiator configuration file. Refer to the iSCSI initiator manual for details about iSCSI initiator settings.

3 Shut down the server. 4 Attach the hardware.

Set up the storage system so that its LUs are accessible to the server, and then connect it to the server. For details on the settings, refer to the storage system manual.

5 Restart the server.

Power on the server and boot it up.

6 Use the "iompadm info" command to check the result.

When the server is restarted, the new storage system should be automatically recognized and incorporated in the list.

[Example]

# /opt/FJSVmpd/bin/iompadm info

7 Set its Max Throttle value.

Execute the "mpdconfig -m" command to set a Max Throttle value for the new storage system. Refer to the software information (/opt/FJSVmpd/manual/english/readme.pdf) for the Max Throttle value computation method.

[Example]

# /opt/FJSVmpd/bin/mpdconfig -m

73

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 6 Changing the Multipath Configuration (iSCSI Connection for RHEL5, SLES9, or SLES10)

End of procedure

Procedure

6.2 Storage System Reduction

8 Use the "mpdconfig -s" command to set the recognition order.

[Example]

# /opt/FJSVmpd/bin/mpdconfig -s

6.2 Storage System Reduction

6.2.1 Reduction without Server Rebooting

Using the "mpdconfig" command, storage systems can be removed without shutting the server. Use the following procedure.

• SUSE Linux Enterprise Server 9 requires the server be rebooted for storage system reduction.

• When removing the storage systems and LUs without server rebooting, completely halt all access to the

storage systems or LUs that are to be removed. If access cannot be halted, follow the procedures described in "6.2.2

Reduction with Server Rebooting" (page 75).

1 Detach the hardware.

Log out of the iSCSI target and disconnect the storage system to be removed from the server.

2 Delete the removed hardware from the Multipath Driver target list using the "mpdconfig -d"

command.

[Example]

# /opt/FJSVmpd/bin/mpdconfig -d

3 If a storage system is removed and the recognition order function is being used, execute the

"mpdconfig -s" command to reconfigure the recognition order.

[Example]

# /opt/FJSVmpd/bin/mpdconfig -s

However, if the storage system reduction reduces the number of storage systems connected to the server to one or less, execute the "mpdconfig -c" command to clear the recognition order setting instead.

74

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 6 Changing the Multipath Configuration (iSCSI Connection for RHEL5, SLES9, or SLES10)

End of procedure

Procedure

6.2 Storage System Reduction

[Example]

# /opt/FJSVmpd/bin/mpdconfig -c

4 Use the "iompadm info" command to check that the removed hardware has disappeared

from view.

[Example]

# /opt/FJSVmpd/bin/iompadm info

5 Set the iSCSI service and delete the iSCSI target information of the removed storage system.

6.2.2 Reduction with Server Rebooting

Use the following procedure to remove storage systems while the server is shut down.

1 If the storage system recognition order has been set, change the settings before removing

the storage system.

• When the storage system reduction reduces the number of storage systems connected to the server

to one or less, execute the "mpdconfig -c" command to clear the storage system recognition order.

[Example]

# /opt/FJSVmpd/bin/mpdconfig -c

• When the storage system reduction reduces the number of storage systems connected to the server

to more than one, execute the "mpdconfig -s" command to set the recognition order of the storage system that is to be removed to last place. If not, the storage systems with a lower recognition order may not be recognized after rebooting.

[Example]

# /opt/FJSVmpd/bin/mpdconfig -s

If SCSI disks are accessed using sd* device names then when the server is restarted after changing the storage system recognition order, the device names will also change. Alter the OS and application settings as necessary. If by-id names are used, this problem does not occur.

2 Shut down the server. 3 Detach the hardware.

Disconnect the target storage system from the server (turn the storage system power off, disconnect the cables, etc.).

75

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 6 Changing the Multipath Configuration (iSCSI Connection for RHEL5, SLES9, or SLES10)

End of procedure

6.3 LU Addition

4 Restart the server.

Power on the server and boot it up.

5 Use the "iompadm info" command to check that the removed hardware is displayed as "fail".

[Example]

# /opt/FJSVmpd/bin/iompadm info

6 Delete the removed hardware from the Multipath Driver target list using the "mpdconfig -d"

command.

[Example]

# /opt/FJSVmpd/bin/mpdconfig -d

7 If the recognition order function is being used, execute the "mpdconfig -s" command to

reconfigure the recognition order.

[Example]

# /opt/FJSVmpd/bin/mpdconfig -s

8 Use the "iompadm info" command to check the result.

[Example]

# /opt/FJSVmpd/bin/iompadm info

9 Set the iSCSI service and delete the iSCSI target information of the removed storage system.

6.3 LU Addition

Same as for FC/FCoE connection. Refer to "4.1

Storage System and LU Addition" (page 54).

6.4 LU Reduction

Same as for FC/FCoE connection. Refer to "4.2

Storage System and LU Reduction" (page 57).

76

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 6 Changing the Multipath Configuration (iSCSI Connection for RHEL5, SLES9, or SLES10)

Procedure

End of procedure

6.5 Path Addition (Cable Addition)

This section describes how to increase the paths by adding cables.

6.5.1 For Red Hat Enterprise Linux 5 or SUSE Linux Enterprise Server 10

Using the "mpdconfig" command, cables can be added. Use the following procedure.

1 Attach the hardware.

Set up the storage system so that its LUs are accessible via the cable, and then connect the cable between the server and the storage system (a NIC must already be installed in the server). For details on the settings, refer to the storage system manual.

2 Set the server iSCSI service.

Set iSCSI initiator/iSCSI target information and log in to the iSCSI target. Make sure that automatic login to the iSCSI target has been specified. Refer to storage systems User's Guide -Server Connection- or any other relevant manuals and "Appendix 2" in the software information (/opt/FJSVmpd/manual/english/ readme.pdf) for details about iSCSI connection.

3 Use the "iompadm info" command to check that the new cable has been correctly

recognized and incorporated.

[Example]

# /opt/FJSVmpd/bin/iompadm info

4 Set a Max Throttle value for the new path.

Execute the "mpdconfig -m" command to set a Max Throttle value for the new path. Refer to the software information (/opt/FJSVmpd/manual/english/readme.pdf) for the Max Throttle value computation method.

[Example]

# /opt/FJSVmpd/bin/mpdconfig -m

77

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 6 Changing the Multipath Configuration (iSCSI Connection for RHEL5, SLES9, or SLES10)

Procedure

End of procedure

6.5 Path Addition (Cable Addition)

6.5.2 For SUSE Linux Enterprise Server 9

Using the "mpdconfig" command, cables can be added. Use the following procedure.

1 Set the server iSCSI service.

Set an iSCSI initiator and add the IP addresses of the paths to be added to the iSCSI initiator configuration file. Refer to the iSCSI initiator manual for details about iSCSI initiator settings.

2 Shut down the server. 3 Attach the hardware.

Set up the storage system so that its LUs are accessible via the cable, and then connect the cable between the server and the storage system (a NIC must already be installed in the server). For details on the settings, refer to the storage system manual.

4 Restart the server.

Power on the server and boot it up.

5 Use the "iompadm info" command to check that the new cable has been correctly

recognized and incorporated.

[Example]

# /opt/FJSVmpd/bin/iompadm info

6 Set a Max Throttle value for the new path.

Execute the "mpdconfig -m" command to set a Max Throttle value for the new path. Refer to the software information (/opt/FJSVmpd/manual/english/readme.pdf) for the Max Throttle value computation method.

[Example]

# /opt/FJSVmpd/bin/mpdconfig -m

78

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 6 Changing the Multipath Configuration (iSCSI Connection for RHEL5, SLES9, or SLES10)

Procedure

End of procedure

6.6 Path Reduction (Cable Reduction)

This section describes how to decrease the paths by removing cables.

6.6.1 Reduction without Server Rebooting

Cables can be removed without shutting down the server. Use the following procedure.

SUSE Linux Enterprise Server 9 requires the server be rebooted for cable reduction.

1 Disconnect the surplus cables from the server.

Disconnect the cables after logging out of the iSCSI target.

2 Use the "iompadm info" command to check that the removed cable is displayed as "fail".

[Example]

# /opt/FJSVmpd/bin/iompadm info

3 Delete the removed cable from the Multipath Driver target list using the "mpdconfig -d"

command.

[Example]

# /opt/FJSVmpd/bin/mpdconfig -d

4 Use the "iompadm info" command to check that the removed cable has disappeared from

view.

[Example]

# /opt/FJSVmpd/bin/iompadm info

5 Reset the Max Throttle value if necessary.

When the number of paths connected to a given port in the storage system is reduced due to the path removal, execute the "mpdconfig -m" command to set the Max Throttle value correctly. Refer to the software information (/opt/FJSVmpd/manual/english/readme.pdf) for the Max Throttle value computation method.

6 Set the iSCSI service and delete the iSCSI target information of the removed path.

79

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 6 Changing the Multipath Configuration (iSCSI Connection for RHEL5, SLES9, or SLES10)

Procedure

End of procedure

6.6 Path Reduction (Cable Reduction)

6.6.2 Reduction with Server Rebooting

Use the following procedure to remove cables while the server is shut down.

1 Shut down the server. 2 Detach the hardware.

Disconnect the target cable from the server (remove the connected cable, etc.).

3 Restart the server.

Power on the server and boot it up.

4 Use the "iompadm info" command to check that the removed cable is displayed as "fail".

[Example]

# /opt/FJSVmpd/bin/iompadm info

5 Delete the removed cable from the Multipath Driver target list using the "mpdconfig -d"

command.

[Example]

# /opt/FJSVmpd/bin/mpdconfig -d

6 Use the "iompadm info" command to check the result.

[Example]

# /opt/FJSVmpd/bin/iompadm info

7 Reset the Max Throttle value if necessary.

When the number of paths connected to a given CA port in the storage system is reduced due to the path removal, execute the "mpdconfig -m" command to set the Max Throttle value correctly. Refer to the software information (/opt/FJSVmpd/manual/english/readme.pdf) for the Max Throttle value computation method.

8 Set the iSCSI service and delete the iSCSI target information of the removed path.

80

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 6 Changing the Multipath Configuration (iSCSI Connection for RHEL5, SLES9, or SLES10)

6.7 Path Addition and Reduction (NIC Addition and Reduction)

This section describes how to increase paths by adding NICs, and decrease paths by removing NICs.

Adding and reducing NICs without server rebooting (PCI Hot Plug) is only supported for PRIMEQUEST servers.

• For SUSE Linux Enterprise Server 9

Adding and reducing NICs without server rebooting (PCI Hot Plug) is not supported.

• For Red Hat Enterprise Linux 5 and SUSE Linux Enterprise Server 10

Adding and reducing NICs without server rebooting is the same procedure as adding and reducing cables without server rebooting. Add or reduce NICs at the same time that cables are being added or reduced. For details on this procedure, refer to the PRIMEQUEST manual.

Adding and reducing NICs with server rebooting is the same procedure as adding and reducing cables with server rebooting. Add or reduce NICs at the same time that cables are being added or reduced.

81

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 7

Changing the Multipath Configuration (FC/FCoE Connection for RHEL6, RHEL7, or SLES11)

The procedure to change the multipath configuration varies depending on the type of OS that is used. In this chapter, the multipath configuration of the following OSs is described:

• Red Hat Enterprise Linux 6

• Red Hat Enterprise Linux 7

• SUSE Linux Enterprise Server 11 (Service Pack 1 or later)

When using the following OSs, refer to "Chapter 4

for RHEL-AS4, RHEL-ES4, RHEL5, SLES9, or SLES10)" (page 53).

• Red Hat Enterprise Linux AS v.4

• Red Hat Enterprise Linux ES v.4

• Red Hat Enterprise Linux 5

• SUSE Linux Enterprise Server 9 (Service Pack 2 or later)

• SUSE Linux Enterprise Server 10 (Service Pack 1 or later)

The multipath configuration can be changed using the "mpdconfig" command. The "mpdconfig" command is installed in the /opt/FJSVmpd/bin directory. Only a root-level user may execute the "mpdconfig" command. This chapter describes how to change multipath configuration for FC/FCoE connection.

• When by-id names are not used, changing the multipath configuration may change the device names.

• Before starting an addition process, use the "iompadm info" command to check that the existing devices

are in normal status.

• Before starting a reduction process, check that the device not to be reduced is in normal status.

Changing the Multipath Configuration (FC/FCoE Connection

82

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 7 Changing the Multipath Configuration (FC/FCoE Connection for RHEL6, RHEL7, or SLES11)

Procedure

End of procedure

Procedure

7.1 Storage System Addition

7.1.1 Addition without Server Rebooting

Using the "mpdconfig" command, extra storage systems can be added without shutting down the server. Use the following procedure.

1 Attach the storage system.

Set up the storage system so that its LUs are accessible to the server, and then connect it to the server. For details on the settings, refer to the storage system manual.

2 Use the "iompadm info" command to check that the added storage system has been

correctly recognized and incorporated.

[Example]

# /opt/FJSVmpd/bin/iompadm info

3 Set the Max Throttle value for the new storage system.

Execute the "mpdconfig -m" command to set a Max Throttle value for the new storage system. Refer to the software information (/opt/FJSVmpd/manual/english/readme.pdf) for the Max Throttle value computation method.

[Example]

# /opt/FJSVmpd/bin/mpdconfig -m

7.1.2 Addition with Server Rebooting

Use the following procedure to add extra storage systems while the server is shut down.

1 Shut down the server. 2 Attach the storage system.

Set up the storage system so that its LUs are accessible to the server, and then connect it to the server. For details on the settings, refer to the storage system manual.

3 Restart the server.

Power on the server and boot it up.

83

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 7 Changing the Multipath Configuration (FC/FCoE Connection for RHEL6, RHEL7, or SLES11)

End of procedure

Procedure

7.2 Storage System Reduction

4 Use the "iompadm info" command to check that the added storage system has been

correctly recognized and incorporated.

[Example]

# /opt/FJSVmpd/bin/iompadm info

5 Set the Max Throttle value for the new storage system.

Execute the "mpdconfig -m" command to set a Max Throttle value for the new storage system. Refer to the software information (/opt/FJSVmpd/manual/english/readme.pdf) for the Max Throttle value computation method.

[Example]

# /opt/FJSVmpd/bin/mpdconfig -m

7.2 Storage System Reduction

7.2.1 Reduction without Server Rebooting

Using the "mpdconfig" command, storage systems can be removed without shutting down the server. Use the following procedure.

When removing the storage systems without server rebooting, completely halt all access to the storage systems that are to be removed. If access cannot be halted, follow the procedures described in "7.2.2

Reduction with Server Rebooting" (page 85).

1 Detach the storage system.

Disconnect the target storage system from the server (turn the storage system power off, disconnect the cables, etc.).

2 Delete the removed storage system from the Multipath Driver target list using the

"mpdconfig -d" command.

[Example]

# /opt/FJSVmpd/bin/mpdconfig -d

84

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 7 Changing the Multipath Configuration (FC/FCoE Connection for RHEL6, RHEL7, or SLES11)

End of procedure

Procedure

End of procedure

7.2 Storage System Reduction

3 Use the "iompadm info" command to check that the removed storage system has

disappeared from view.

[Example]

# /opt/FJSVmpd/bin/iompadm info

7.2.2 Reduction with Server Rebooting

Use the following procedure to remove storage systems while the server is shut down.

1 Shut down the server. 2 Detach the storage system.

Disconnect the target storage system from the server (turn the storage system power off, disconnect the cables, etc.).

3 Restart the server.

Power on the server and boot it up.

4 Use the "iompadm info" command to check that the removed storage system has

disappeared from view.

[Example]

# /opt/FJSVmpd/bin/iompadm info

5 Delete the removed storage system from the Multipath Driver target list using the

"mpdconfig -d" command.

[Example]

# /opt/FJSVmpd/bin/mpdconfig -d

85

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 7 Changing the Multipath Configuration (FC/FCoE Connection for RHEL6, RHEL7, or SLES11)

Procedure

End of procedure

7.3 LU Addition

7.3.1 Addition without Server Rebooting

Using the "mpdconfig" command, extra LUs can be added without shutting down the server. Use the following procedure.

1 Attach the LU.

Add a LU in the storage system. For details on adding LUs, refer to the storage system manual.

2 Incorporate the new LU using the "mpdconfig -a" command.

[Example]

# /opt/FJSVmpd/bin/mpdconfig -a

The "iompadm rescan" command can also be used to incorporate the new LU.

[Example]

# /opt/FJSVmpd/bin/iompadm rescan

3 Use the "iompadm info" command to check that the added LU has been correctly recognized

and incorporated.

[Example]

# /opt/FJSVmpd/bin/iompadm info

When a LU is added, it is initially added as a new SCSI disk device after the LUs that have already been incorporated. However, after the system is restarted, the newly added LU is incorporated into the system according to the storage system LU number. Therefore, to access the SCSI disk via a sd* device name, add the LU so that it has the same device name before and after the system restart. If by-id names are used, this problem does not occur.

86

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 7 Changing the Multipath Configuration (FC/FCoE Connection for RHEL6, RHEL7, or SLES11)

Procedure

End of procedure

7.3 LU Addition

7.3.2 Addition with Server Rebooting

Use the following procedure to add extra LUs while the server is shut down:

When adding LUs, the device names (sd*) may be changed. Alter the settings for any applications and OSs that access to the storage system as necessary. If by-id names are used, this problem does not occur.

1 Shut down the server. 2 Attach the LU.

Add a LU in the storage system. For details on adding LUs, refer to the storage system manual.

3 Restart the server.

Power on the server and boot it up.

4 Use the "iompadm info" command to check that the new LU has been correctly recognized

and incorporated.

[Example]

# /opt/FJSVmpd/bin/iompadm info

87

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 7 Changing the Multipath Configuration (FC/FCoE Connection for RHEL6, RHEL7, or SLES11)

Procedure

End of procedure

7.4 LU Reduction

7.4.1 Reduction without Server Rebooting

Using the "mpdconfig" command, LUs can be removed without shutting down the server. Use the following procedure.

• When removing the LUs without server rebooting, completely halt all access to the LUs that are to be

removed. If access cannot be halted, follow the procedures described in "7.4.2

Rebooting" (page 89).

• For storage systems other than the ETERNUS DX S2 series, ETERNUS DX S3 series, or ETERNUS All Flash

Array, never attempt to remove LU0.

Reduction with Server

1 Remove the LUs.

Perform LU reduction in the storage system (release the LU configuration so that the server does not recognize the LU). Refer to the storage system manual for LU reduction details.

2 Delete the removed LUs from the Multipath Driver target list using the "mpdconfig -d"

command.

[Example]

# /opt/FJSVmpd/bin/mpdconfig -d

3 Use the "iompadm info" command to check that the removed LUs have disappeared from

view.

[Example]

# /opt/FJSVmpd/bin/iompadm info

If SCSI disks are accessed using sd* device names, discrepancies will occur for the device names according to the number of deleted LUs when the server is restarted after deleting LUs. Alter the OS and application settings as necessary. If by-id names are used, this problem does not occur.

88

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 7 Changing the Multipath Configuration (FC/FCoE Connection for RHEL6, RHEL7, or SLES11)

Procedure

End of procedure

7.4 LU Reduction

7.4.2 Reduction with Server Rebooting

Use the following procedure to remove LUs while the server is shut down.

For storage systems other than the ETERNUS DX S2 series, ETERNUS DX S3 series, or ETERNUS All Flash Array, never attempt to remove LU0.

1 Shut down the server. 2 Remove the LUs.

Perform LU reduction in the storage system (so that the server cannot recognize the LU). Refer to the storage system manual for LU reduction details.

If SCSI disks are accessed using sd* device names, discrepancies will occur for the device names according to the number of deleted LUs when the server is restarted after deleting LUs. Alter the OS and application settings as necessary. If by-id names are used, this problem does not occur.

3 Restart the server.

Power on the server and boot it up.

4 Use the "iompadm info" command to check that the removed LUs are disappeared from

view.

[Example]

# /opt/FJSVmpd/bin/iompadm info

89

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 7 Changing the Multipath Configuration (FC/FCoE Connection for RHEL6, RHEL7, or SLES11)

Procedure

End of procedure

Procedure

7.5 Path Addition (Cable Addition)

This section describes how to increase the paths by adding cables.

7.5.1 Addition without Server Rebooting

Using the "mpdconfig" command, cables can be added without shutting down the server. Use the following procedure.

1 Attach the hardware.

Set up the storage system so that its LUs are accessible via the cable, and then connect the cable between the server and the storage system (an HBA must already be installed in the server). For details on the settings, refer to the storage system manual.

2 Use the "iompadm info" command to check that the new cable has been correctly

recognized and incorporated.

[Example]

# /opt/FJSVmpd/bin/iompadm info

3 Set a Max Throttle value for the new path.

Execute the "mpdconfig -m" command to set a Max Throttle value for the new path. Refer to the software information (/opt/FJSVmpd/manual/english/readme.pdf) for the Max Throttle value computation method.

[Example]

# /opt/FJSVmpd/bin/mpdconfig -m

7.5.2 Addition with Server Rebooting

Use the following procedure to add extra cables while the server is shut down.

1 Shut down the server.

90

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 7 Changing the Multipath Configuration (FC/FCoE Connection for RHEL6, RHEL7, or SLES11)

End of procedure

Procedure

7.6 Path Reduction (Cable Reduction)

2 Attach the hardware.

Set up the storage system so that its LUs are accessible via the cable, and then connect the cable between the server and the storage system (an HBA must already be installed in the server). For details on the settings, refer to the storage system manual.

3 Restart the server.

Power on the server and boot it up.

4 Use the "iompadm info" command to check that the new cable has been correctly

recognized and incorporated.

[Example]

# /opt/FJSVmpd/bin/iompadm info

5 Set a Max Throttle value for the new path.

Execute the "mpdconfig -m" command to set a Max Throttle value for the new path. Refer to the software information (/opt/FJSVmpd/manual/english/readme.pdf) for the Max Throttle value computation method.

[Example]

# /opt/FJSVmpd/bin/mpdconfig -m

7.6 Path Reduction (Cable Reduction)

This section describes how to decrease the paths by removing cables.

7.6.1 Reduction without Server Rebooting

Using the "mpdconfig" command, cables can be removed without shutting down the server. Use the following procedure.

1 Detach the hardware.

Disconnect the target cable from the server (remove the connected cable, etc.).

2 Delete the removed cable from the Multipath Driver target list using the "mpdconfig -d"

command.

[Example]

# /opt/FJSVmpd/bin/mpdconfig -d

91

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 7 Changing the Multipath Configuration (FC/FCoE Connection for RHEL6, RHEL7, or SLES11)

End of procedure

Procedure

End of procedure

7.6 Path Reduction (Cable Reduction)

3 Use the "iompadm info" command to check that the removed cable has disappeared from

view.

[Example]

# /opt/FJSVmpd/bin/iompadm info

4 Reset the Max Throttle value if necessary.

When the number of paths connected to a given CA port in the storage system is reduced due to the path removal, execute the "mpdconfig -m" command to set the Max Throttle value correctly. Refer to the software information (/opt/FJSVmpd/manual/english/readme.pdf) for the Max Throttle value computation method.

7.6.2 Reduction with Server Rebooting

Use the following procedure to remove cables while the server is shut down.

1 Shut down the server. 2 Detach the hardware.

Disconnect the target cable from the server (remove the connected cable, etc.).

3 Restart the server.

Power on the server and boot it up.

4 Use the "iompadm info" command to check that the removed cable has disappeared from

view.

[Example]

# /opt/FJSVmpd/bin/iompadm info

5 Delete the removed cable from the Multipath Driver target list using the "mpdconfig -d"

command.

[Example]

# /opt/FJSVmpd/bin/mpdconfig -d

6 Reset the Max Throttle value if necessary.

When the number of paths connected to a given CA port in the storage system is reduced due to the path removal, execute the "mpdconfig -m" command to set the Max Throttle value correctly. Refer to the software information (/opt/FJSVmpd/manual/english/readme.pdf) for the Max Throttle value computation method.

92

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 7 Changing the Multipath Configuration (FC/FCoE Connection for RHEL6, RHEL7, or SLES11)

7.7 Path Addition and Reduction (HBA Addition and Reduction)

This section describes how to increase paths by adding HBAs, and decrease paths by removing HBAs. Adding and reducing HBAs without server rebooting (PCI Hot Plug) is only supported for PRIMEQUEST servers. For details on this procedure, refer to the PRIMEQUEST manual. To shut down the server after the addition of paths by adding HBAs, change the status of the new paths to "stop" with the "iompadm change" command. Adding and reducing HBAs with server rebooting is the same procedure as adding and reducing cables with server rebooting. Add or reduce HBAs at the same time that cables are being added or reduced. When a HBA is added, execute the "mpdconfig -m" command to set the Max Throttle values for the new path. Refer to the software information (/opt/FJSVmpd/manual/english/readme.pdf) for the Max Throttle value computation method.

93

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 8

Changing the Multipath Configuration (SAS Connection for RHEL6, RHEL7, or SLES11)

The procedure to change the multipath configuration varies depending on the type of OS that is used. In this chapter, the multipath configuration of the following OSs is described:

• Red Hat Enterprise Linux 6

• Red Hat Enterprise Linux 7

• SUSE Linux Enterprise Server 11 (Service Pack 1 or later)

When using the following OSs, refer to "Chapter 5

RHEL-AS4, RHEL-ES4, RHEL5, or SLES10)" (page 65).

• Red Hat Enterprise Linux AS (4.6 or later)

• Red Hat Enterprise Linux ES (4.6 or later)

• Red Hat Enterprise Linux 5 (Update 3 or later)

• SUSE Linux Enterprise Server 10 (Service Pack 3 or later)

The multipath configuration can be changed using the "mpdconfig" command. The "mpdconfig" command is installed in the /opt/FJSVmpd/bin directory. Only a root-level user may execute the "mpdconfig" command. This chapter describes how to change multipath configuration for SAS connection.

• When by-id names are not used, changing the multipath configuration may change the device names.

• Before starting an addition process, use the "iompadm info" command to check that the existing devices

are in normal status.

• Before starting a reduction process, check that the device not to be reduced is in normal status.

8.1 Storage System Addition

Changing the Multipath Configuration (SAS Connection for

Same as for FC/FCoE connection. Refer to "7.1

Storage System Addition" (page 83).

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

94

Chapter 8 Changing the Multipath Configuration (SAS Connection for RHEL6, RHEL7, or SLES11)

Procedure

End of procedure

8.2 Storage System Reduction

8.2.1 Reduction without Server Rebooting

Storage systems can be removed without shutting down the server. Use the following procedure.

When removing the storage systems and LUs without server rebooting, completely halt all access to the storage systems or LUs that are to be removed. If access cannot be halted, follow the procedures described in

"8.2.2

Reduction with Server Rebooting" (page 95).

1 Disconnect all cables to the server.

Disconnect all the SAS cables that connect the server to the storage system that is to be reduced.

2 Use the "iompadm info" command to check the result.

When the cables are removed, the disconnected storage system should be automatically removed and disappear from the list.

[Example]

# /opt/FJSVmpd/bin/iompadm info

3 Delete the removed hardware from the Multipath Driver target list using the "mpdconfig -d"

command.

[Example]

# /opt/FJSVmpd/bin/mpdconfig -d

8.2.2 Reduction with Server Rebooting

Same as for FC/FCoE connection. Refer to "7.2.2

Reduction with Server Rebooting" (page 85).

95

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 8 Changing the Multipath Configuration (SAS Connection for RHEL6, RHEL7, or SLES11)

Procedure

8.3 LU Addition

Same as for FC/FCoE connection. Refer to "7.3

LU Addition" (page 86).

8.4 LU Reduction

Same as for FC/FCoE connection. Refer to "7.4

LU Reduction" (page 88).

8.5 Path Addition (Cable Addition)

Same as for FC/FCoE connection. Refer to "7.5

Path Addition (Cable Addition)" (page 90).

8.6 Path Reduction (Cable Reduction)

This section describes how to decrease the paths by removing cables.

8.6.1 Reduction without Server Rebooting

Cables can be removed without shutting down the server. Use the following procedure.

1 Disconnect the surplus cables from the server. 2 Use the "iompadm info" command to check the result.

When the cables are disconnected, they should be automatically removed and disappear from the list.

[Example]

# /opt/FJSVmpd/bin/iompadm info

96

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 8 Changing the Multipath Configuration (SAS Connection for RHEL6, RHEL7, or SLES11)

End of procedure

8.7 Path Addition and Reduction (HBA Addition and Reduction)

3 Delete the removed hardware from the Multipath Driver target list using the "mpdconfig -d"

command.

[Example]

# /opt/FJSVmpd/bin/mpdconfig -d

4 Reset the Max Throttle value if necessary.

When the number of paths connected to a given CA port in the storage system is reduced due to the path removal, execute the "mpdconfig -m" command to set the Max Throttle value correctly. Refer to the software information (/opt/FJSVmpd/manual/english/readme.pdf) for the Max Throttle value computation method.

8.6.2 Reduction with Server Rebooting

Same as for FC/FCoE connection. Refer to "7.6.2

Reduction with Server Rebooting" (page 92).

8.7 Path Addition and Reduction (HBA Addition and Reduction)

This section describes how to increase paths by adding HBAs, and decrease paths by removing HBAs. Adding and reducing HBAs without server rebooting (PCI Hot Plug) is not supported. Adding and reducing HBAs with server rebooting is the same procedure as adding and reducing cables with server rebooting. Add or reduce HBAs at the same time that cables are being added or reduced.

97

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 9

Changing the Multipath Configuration (iSCSI Connection for RHEL6, RHEL7, or SLES11)

The procedure to change the multipath configuration varies depending on the type of OS that is used. In this chapter, the multipath configuration of the following OSs is described:

• Red Hat Enterprise Linux 6

• Red Hat Enterprise Linux 7

• SUSE Linux Enterprise Server 11 (Service Pack 1 or later)

When using the following OSs, refer to "Chapter 6

RHEL5, SLES9, or SLES10)" (page 71).

• Red Hat Enterprise Linux 5 (Update 4 or later)

• SUSE Linux Enterprise Server 9 (Service Pack 3 or later)

• SUSE Linux Enterprise Server 10 (Service Pack 2 or later)

The multipath configuration can be changed using the "mpdconfig" command. The "mpdconfig" command is installed in the /opt/FJSVmpd/bin directory. Only a root-level user may execute the "mpdconfig" command. This chapter describes how to change multipath configuration for iSCSI connection.

• When by-id names are not used, changing the multipath configuration may change the device names.

• Before starting an addition process, use the "iompadm info" command to check that the existing devices

are in normal status.

• Before starting a reduction process, check that the device not to be reduced is in normal status.

Changing the Multipath Configuration (iSCSI Connection for

98

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 9 Changing the Multipath Configuration (iSCSI Connection for RHEL6, RHEL7, or SLES11)

Procedure

End of procedure

9.1 Storage System Addition

Use the following procedure to add extra storage systems.

When adding storage systems, the device names (sd*) may be changed. Alter the settings for any applications and OSs that access to the storage system as necessary. If by-id names are used, this problem does not occur.

1 Attach the hardware.

Set up the storage system so that its LUs are accessible to the server, and then connect it to the server. For details on the settings, refer to the storage system manual.

2 Set the server iSCSI service.

Set iSCSI initiator/iSCSI target information and log in to the iSCSI target. Make sure that automatic login to the iSCSI target has been specified. Refer to storage systems User's Guide -Server Connection- or any other relevant manuals and "Appendix 2" in the software information (/opt/FJSVmpd/manual/ english/readme.pdf) for details about iSCSI connection.

3 Use the "iompadm info" command to check the result.

The new storage system should be automatically recognized and incorporated in the list.

[Example]

# /opt/FJSVmpd/bin/iompadm info

4 Set its Max Throttle value.

Execute the "mpdconfig -m" command to set a Max Throttle value for the new storage system. Refer to the software information (/opt/FJSVmpd/manual/english/readme.pdf) for the Max Throttle value computation method.

[Example]

# /opt/FJSVmpd/bin/mpdconfig -m

99

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Chapter 9 Changing the Multipath Configuration (iSCSI Connection for RHEL6, RHEL7, or SLES11)

Procedure

End of procedure

9.2 Storage System Reduction

9.2.1 Reduction without Server Rebooting

Using the "mpdconfig" command, storage systems can be removed without shutting down the server. Use the following procedure.

When removing the storage systems and LUs without server rebooting, completely halt all access to the storage systems or LUs that are to be removed. If access cannot be halted, follow the procedures described in

Reduction with Server Rebooting" (page 101).

"9.2.2

1 Detach the hardware.

Log out of the iSCSI target and disconnect the storage system to be removed from the server.

2 Use the "iompadm info" command to check that the removed hardware has disappeared

from view.

The storage system is automatically removed from view after logging out.

[Example]

# /opt/FJSVmpd/bin/iompadm info

3 Delete the removed hardware from the Multipath Driver target list using the "mpdconfig -d"

command.

[Example]

# /opt/FJSVmpd/bin/mpdconfig -d

4 Set the iSCSI service and delete the iSCSI target information of the removed storage system.

100

FUJITSU Storage ETERNUS Multipath Driver V2 User’s Guide for Linux

Fujitsu ETERNUS Multipath Driver V2 User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Preface

Release Information

Table of Contents

List of Figures

List of Tables

1.1 Features

1.2 Connections

2.1 Accessing the Storage System Disks

2.1.1 Using the udev Function

2.1.2 When Using FUJITSU Software PRIMECLUSTER Global Disk Services (Storage System Recognition Order Setting)

2.2 Multipath Driver Related Log

3.1 Path Management

3.1.1 Path Status

3.1.2 Checks and Path Status Transitions

3.2 Load Balancing/Failover

3.2.1 Load Balancing

3.2.2 Failover

3.3 Identifying Disks and Paths

3.3.1 Device Identification

3.3.2 Path Identification

3.4 Multipath Status Display

3.4.1 "iompadm info" Command

3.5 Disconnecting/Reconnecting Paths when Replacing Hardware

3.5.1 "iompadm change" Command

3.6 Multipath Recovery

3.5.2 "iompadm restart" Command

4.1 Storage System and LU Addition

4.1.1 Addition without Server Rebooting

4.1.2 Addition with Server Rebooting

4.2 Storage System and LU Reduction

4.2.1 Reduction without Server Rebooting

4.2.2 Reduction with Server Rebooting

4.3 Path Addition (Cable Addition)

4.3.1 Addition without Server Rebooting

4.3.2 Addition with Server Rebooting

4.4 Path Reduction (Cable Reduction)

4.4.1 Reduction without Server Rebooting

4.4.2 Reduction with Server Rebooting

4.5 Path Addition and Reduction (HBA Addition and Reduction)

5.1 Storage System Addition

5.1.1 Addition without Server Rebooting

5.1.2 Addition with Server Rebooting

5.2 Storage System Reduction

5.2.1 Reduction without Server Rebooting

5.2.2 Reduction with Server Rebooting

5.3 LU Addition

5.4 LU Reduction

5.5 Path Addition (Cable Addition)

5.5.1 Addition without Server Rebooting

5.6 Path Reduction (Cable Reduction)

5.5.2 Addition with Server Rebooting

5.6.1 Reduction without Server Rebooting

5.6.2 Reduction with Server Rebooting

5.7 Path Addition and Reduction (HBA Addition and Reduction)

6.1 Storage System Addition

6.1.1 For Red Hat Enterprise Linux 5 or SUSE Linux Enterprise Server 10

6.1.2 For SUSE Linux Enterprise Server 9

6.2 Storage System Reduction

6.2.1 Reduction without Server Rebooting

6.2.2 Reduction with Server Rebooting

6.3 LU Addition

6.4 LU Reduction

6.5 Path Addition (Cable Addition)

6.5.1 For Red Hat Enterprise Linux 5 or SUSE Linux Enterprise Server 10

6.5.2 For SUSE Linux Enterprise Server 9

6.6 Path Reduction (Cable Reduction)

6.6.1 Reduction without Server Rebooting

6.6.2 Reduction with Server Rebooting

6.7 Path Addition and Reduction (NIC Addition and Reduction)

7.1 Storage System Addition

7.1.1 Addition without Server Rebooting

7.1.2 Addition with Server Rebooting

7.2 Storage System Reduction

7.2.1 Reduction without Server Rebooting

7.2.2 Reduction with Server Rebooting

7.3 LU Addition