Red Hat DEVICE-MAPPER MULTIPATH 5.2 Manual de usuario descargar pdf (Pagina 9)

3 Confirm that the following description is present.

## Use user friendly names, instead of using WWIDs as names.

defaults {

user_friendly_names yes (*1)

queue_without_daemon no (*2)

# find_multipaths yes　　　 (*3)

}

*1: For "user_friendly_names", "no" can be specified as necessary for middleware or applications.

*2: Add the "queue_without_daemon no" line for iSCSI connections.

*3: If there is a "find_multipaths yes" line, add a "#" to the beginning of the line to comment out the

line.

Enter a space between "defaults" and "{".

4 Add the following lines at the end of the file.

• For ETERNUS DX storage systems

(Example: Connecting the ETERNUS DX80)

devices {

device {

vendor "FUJITSU"

product "ETERNUS_DXL"

prio alua

path_grouping_policy group_by_prio

path_selector "round-robin 0"

failback immediate

no_path_retry 0 (*1)

path_checker tur

dev_loss_tmo 2097151 (*2)

fast_io_fail_tmo 1

}

*1: When using the Storage Cluster function, or a 10Gbit/s iSCSI connection with an ETERNUS DX S3

series, specify "no_path_retry 10".

*2: For Oracle Linux 5.x UEK or Oracle Linux 5.x, the "dev_loss_tmo" line is not required.

- Enter a space between "devices" and "{".

- Enter a space between "device" and "{".

- The "dev_loss_tmo" parameter value is not applied correctly when a Brocade Fibre Channel card

is used. This may cause the device file to be cleared if the ETERNUS DX is turned off due to a

power failure. If this occurs, the server may have to be rebooted.

Chapter 2 For Red Hat Enterprise Linux 7, Red Hat Enterprise Linux 6, or Oracle Linux

2.1 Setting Up the device-mapper multipath

FUJITSU Storage ETERNUS DX Configuration Guide -Server Connection-

(Fibre Channel/FCoE/iSCSI/SAS) for Linux

P3AM-3912-21ENZ0

1 2 3 4 5 6 7 8 9 10 11 12 13 14 ... 30 31

Sin comentarios

Red Hat DEVICE-MAPPER MULTIPATH 5.2 Manual de usuario Pagina 9