configuration guide -server connection- · refer to "configuration guide -server connection-...

FUJITSU StorageETERNUS DX, ETERNUS AF

Configuration Guide -Server Connection-

(Fibre Channel) for Oracle SolarisMultipath Driver Settings

P3AM-6322-11ENZ0

This page is intentionally left blank.

Preface

This manual briefly explains the operations that need to be performed by the user in order to connect anETERNUS DX/AF to a server running Solaris OS via a Fibre Channel interface.

This manual should be used in conjunction with any other applicable user manuals, such as those for theETERNUS DX/AF, server, OS, Fibre Channel cards, and drivers.

Refer to "Configuration Guide -Server Connection- Notations" for the notations used in this manual such asproduct trademarks and product names. For storage systems that are supported by the OS, refer to the ServerSupport Matrix of the ETERNUS DX/AF.

11th Edition

April 2018

The Contents and Structure of this Manual

This manual is composed of the following two chapters.

• "Chapter 1 Using ETERNUS Multipath Driver" (page 5)

This chapter describes points to note when using the ETERNUS Multipath Driver.

• "Chapter 2 Using MPxIO Multipath Driver" (page 6)

This chapter describes procedures and points to note when using the MPxIO Multipath Driver.

3FUJITSU Storage ETERNUS DX, ETERNUS AF Configuration Guide -Server Connection- (Fibre Channel) for Oracle Solaris

Copyright 2018 FUJITSU LIMITEDP3AM-6322-11ENZ0

Table of Contents

Chapter 1 Using ETERNUS Multipath Driver 5

1.1 ETERNUS Multipath Driver Notes .................................................................................................... 5

Chapter 2 Using MPxIO Multipath Driver 6

2.1 Workflow ........................................................................................................................................ 6

2.2 MPxIO Usage Notes ........................................................................................................................ 7

2.3 Setting Up MPxIO ........................................................................................................................... 82.3.1 Solaris 11 OS or Solaris 10 OS................................................................................................................................8



Chapter 1Using ETERNUS Multipath Driver

Before installing the ETERNUS Multipath Driver, also check the usage conditions and list of supported envi-ronments given in the relevant notes in the "Notes" chapter of the "Configuration Guide -Server Connection-(Fibre Channel) for Oracle Solaris" and the "Server Support Matrix".

When using the ETERNUS Multipath Driver, read the following notes carefully.

1.1 ETERNUS Multipath Driver Notes

The following points should be noted about the ETERNUS Multipath Driver:

• Check the "Server Support Matrix" for the Fibre Channel cards available for the ETERNUS Multipath Driver.

• When the ETERNUS DX/AF and server are to be connected in a multipath configuration, install the ETERNUSMultipath Driver according to the installation guide provided with it.

• Refer to the ETERNUS Multipath Driver User's Guide and product manual for details of how to set up theserver for the ETERNUS Multipath Driver.

• ETERNUS Multipath Driver 2.0.1 to 2.0.3 include the following two drivers:

- "Driver for Solaris 10 OS and Solaris 9 OS"

- "Driver for Solaris 9 OS, Solaris 8 OS, Solaris 7 OS, and Solaris 2.6 OS"

• ETERNUS Multipath Driver 3.0.0 to 3.0.4 include the following driver:


• ETERNUS Multipath Driver 3.1.0 or later includes the following two drivers:





Chapter 2Using MPxIO Multipath Driver

2.1 Workflow

This chapter describes how to set up a multipath connection using MPxIO.

Refer to "2.3 Setting Up MPxIO" (page 8) for more details.

Workflow

Checking the Device StatusCheck the path status before multipathing is set up.

• "2.3.1.1 Checking the Device Status" (page 8)

Changing Settings

1 Enable multipathing.

• "2.3.1.2 "fp.conf" Settings" (page 9)

2 Enable the auto-failback function.

• "2.3.1.3 Checking "scsi_vhci.conf"" (page 9)

When the CPU that is installed in the server is x86, the default setting values for MPxIO are enabled.Confirm that the setting values for MPxIO are enabled.

Effecting the Changed SettingsReconfigure and restart the server to enable the new settings.

• "2.3.1.4 Enabling MPxIO" (page 10)



Checking the Multipath StatusCheck the status of the multipath connection after the MPxIO settings are complete.

• "2.3.1.5 Checking the MPxIO Multipath Status" (page 11)

If there are devices in which multipathing is not set, disable MPxIO on their paths (*1).

• "2.3.1.6 Disabling MPxIO on Some Paths" (page 12)

*1: This setting is not necessary when multipathing is set for all the LUNs.

2.2 MPxIO Usage Notes

When using MPxIO, read the following notes carefully.

• Before installing MPxIO, also check the usage conditions and list of supported environments given in therelevant notes in the "Notes" chapter of the "Configuration Guide -Server Connection- (Fibre Channel) forOracle Solaris" and the "Server Support Matrix".

• MPxIO is bundled with Solaris 10 OS from Update 1 onwards, so separate installation is not required forthese versions.

• Download and install the Sun StorEdge SAN (MPxIO) software from the following Oracle web-site for Solaris10 OS. Refer to "Oracle Solaris Administration: SAN Configuration and Multipathing" on the Oracle web-site(https://www.oracle.com) for details.

Chapter 2 Using MPxIO Multipath Driver2.2 MPxIO Usage Notes



2.3 Setting Up MPxIO

The MPxIO set up procedure is common to all ETERNUS DX/AF storage systems, but some settings vary de-pending on the Solaris OS version.

Refer to "Oracle Solaris Administration: SAN Configuration and Multipathing" on the Oracle web-site (https://www.oracle.com) for setting procedure details.

2.3.1 Solaris 11 OS or Solaris 10 OS

2.3.1.1 Checking the Device StatusUse the "format" command to check the path status before multipathing is set up (example output follows).

# formatSearching for disks...doneAVAILABLE DISK SELECTIONS: 0. c2t50000394281B523Ed0 <TOSHIBA-MBF2600RC-3706-558.91GB> /pci@8000/pci@4/pci@0/pci@0/scsi@0/iport@f/disk@w50000394281b523e,0 /dev/chassis/SYS/HDD0/disk 1. c2t500000E115FA8032d0 <FUJITSU-MBD2300RC-3702 cyl 46873 alt 2 hd 20 sec 625> /pci@8000/pci@4/pci@0/pci@0/scsi@0/iport@f/disk@w500000e115fa8032,0 /dev/chassis/SYS/HDD2/disk 2. c4t500000E0DAC103C5d0 <FUJITSU-ETERNUS_DXH-1050 cyl 6525 alt 2 hd 255 sec 63> /pci@8000/pci@4/pci@0/pci@8/QLGC,qlc@0/fp@0,0/ssd@w500000e0dac103c5,0 3. c4t500000E0DAC103C5d1 <FUJITSU-ETERNUS_DXH-1050 cyl 6525 alt 2 hd 255 sec 63> /pci@8000/pci@4/pci@0/pci@8/QLGC,qlc@0/fp@0,0/ssd@w500000e0dac103c5,1 4. c5t500000E0DAC10305d0 <FUJITSU-ETERNUS_DXH-1050 cyl 6525 alt 2 hd 255 sec 63> /pci@8000/pci@4/pci@0/pci@8/QLGC,qlc@0,1/fp@0,0/ssd@w500000e0dac10305,0 5. c5t500000E0DAC10305d1 <FUJITSU-ETERNUS_DXH-1050 cyl 6525 alt 2 hd 255 sec 63> /pci@8000/pci@4/pci@0/pci@8/QLGC,qlc@0,1/fp@0,0/ssd@w500000e0dac10305,1

The underlined portion indicates "d0" device that is connected to c4 and c5 paths.

Chapter 2 Using MPxIO Multipath Driver2.3 Setting Up MPxIO



2.3.1.2 "fp.conf" SettingsEdit the "fp.conf" file.

• Solaris 11 OS

Edit the "/etc/driver/drv/fp.conf" file.

• Solaris 10 OS

Edit the "/kernel/drv/fp.conf" file.

1 Enable MPxIO.

Check that an "mpxio-disable="no";" line exists.

Otherwise, add this line or change its value to "no".

mpxio-disable="no";

If the "/etc/driver/drv/fp.conf" file already exists, directly edit it and do not overwrite it.

2.3.1.3 Checking "scsi_vhci.conf"Check the "scsi_vhci.conf" settings.

• Solaris 11 OS

Check the "/etc/driver/drv/scsi_vhci.conf" file settings. If the "scsi_vhci.conf" file does not exist, copy the filefrom the "/kernel/drv/" directory and check the settings.

• Solaris 10 OS

Check the "/kernel/drv/scsi_vhci.conf" file settings.

1 Specify the multipath control method.

Check that a "load-balance="round-robin";" line exists.

Otherwise, add this line or change its value to "round-robin".

If the "/etc/driver/drv/scsi_vhci.conf" file already exists, directly edit it and do not overwrite it.

The internal disks are set.

2 Enable the auto-failback function.

Check that an "auto-failback="enable";" line exists.




Otherwise, add this line or change its value to "enable".

# Copyright 2004 Sun Microsystems, Inc. All rights reserved.# Use is subject to license terms.##pragma ident "@(#)scsi_vhci.conf 1.9 04/08/26 SMI"#name="scsi_vhci" class="root";## Load balancing global configuration: setting load-balance="none" will cause# all I/O to a given device (which supports multipath I/O) to occur via one# path. Setting load-balance="round-robin" will cause each path to the device# to be used in turn.#

load-balance="round-robin";

## Automatic failback configuration# possible values are auto-failback="enable" or auto-failback="disable"

auto-failback="enable";

## For enabling MPxIO support for 3rd party symmetric device need an# entry similar to following in this file. Just replace the "SUN SENA"# part with the Vendor ID/Product ID for the device, exactly as reported by# Inquiry cmd.## device-type-scsi-options-list =# "SUN SENA", "symmetric-option";## symmetric-option = 0x1000000;

Check that auto-failback is enabled.

Check that load-balance is set to "round-robin".

2.3.1.4 Enabling MPxIOUse the "stmsboot -e" command to enable MPxIO.

Example:

# /usr/sbin/stmsboot -e Do you wish to continue?[y/n](default:y) <RETURN> WARNING:This operation will require a reboot. Do you want to continue?[y/n](default:y) <RETURN> The changes will come into effect after rebooting the system. Reboot the system now?[y/n](default:y) <RETURN>

If the "/etc/driver/drv/scsi_vhci.conf" file is modified, execute the "/usr/sbin/stmsboot -u" command.




2.3.1.5 Checking the MPxIO Multipath StatusUse the "format" command to check the MPxIO multipath status after multipathing is set up.

Example of an execution result for the "format" command after multipathing is set (for the ETERNUS DX8700S3):

# formatSearching for disks...doneAVAILABLE DISK SELECTIONS: 0. c0t50000394281B523Cd0 <TOSHIBA-MBF2600RC-3706-558.91GB> /scsi_vhci/disk@g50000394281b523c /dev/chassis/SYS/HDD0/disk 1. c2t500000E115FA8032d0 <FUJITSU-MBD2300RC-3702 cyl 46873 alt 2 hd 20 sec 625> /pci@8000/pci@4/pci@0/pci@0/scsi@0/iport@f/disk@w500000e115fa8032,0 /dev/chassis/SYS/HDD2/disk 2. c0t600000E00D2B0000002B0101101A0000d0 <FUJITSU-ETERNUS_DXH-1050 cyl 6398 alt 2 hd 64 sec 256> /scsi_vhci/ssd@g600000e00d2b0000002b0101101a0000 3. c0t600000E00D2B0000002B0101101B0000d0 <FUJITSU-ETERNUS_DXH-1050 cyl 6398 alt 2 hd 64 sec 256> /scsi_vhci/ssd@g600000e00d2b0000002b0101101b0000

The underlined portion indicates that c4 and c5 paths changed to c0 path to make a multipath configuration.

Use the "mpathadm" command to check that each path in the multipath configuration is normal.

Example of an execution result for the "mpathadm" command (for the ETERNUS DX8700 S3):

# mpathadm show lu /dev/rdsk/c0t600000E00D2B0000002B0101101A0000d0s2Logical Unit: /dev/rdsk/c0t600000E00D2B0000002B0101101A0000d0s2 mpath-support: libmpscsi_vhci.so Vendor: FUJITSU Product: ETERNUS_DXH Revision: 1050 Name Type: unknown type Name: 600000e00d2b0000002b0101101a0000 Asymmetric: yes Current Load Balance: round-robin Logical Unit Group ID: NA Auto Failback: on Auto Probing: NA

Paths: Initiator Port Name: 21000024ff2eca38 Target Port Name: 500000e0dac103c5 Override Path: NA Path State: OK Disabled: no

Initiator Port Name: 21000024ff2eca39 Target Port Name: 500000e0dac10305 Override Path: NA Path State: OK Disabled: no

Target Port Groups: ID: 32917 Explicit Failover: no Access State: active optimized Target Ports: Name: 500000e0dac103c5 Relative ID: 16533

ID: 32901 Explicit Failover: no Access State: active optimized Target Ports: Name: 500000e0dac10305 Relative ID: 16517




The underlined portion indicates the path status. Both Path States show as "OK" indicating this multipath isnormal.

Refer to "Oracle Solaris Administration: SAN Configuration and Multipathing" on the Oracle web-site (https://www.oracle.com) for details.

2.3.1.6 Disabling MPxIO on Some PathsWhen multipathing is not required for some of the LUNs, use the following procedure to add physical pathsfor the relevant devices to the "fp.conf" file in order to disable the multipath function for the devices.

Disabling the multipath function is not necessary when multipathing is to be set up for all the LUNs that arerecognized by the OS. This ends the procedure for setting up MPxIO.

If this setting is omitted, multipathing is set up for all LUNs recognized by the OS. MPxIO must be disabledfor the paths of connected devices that MPxIO does not support (such as a tape device).

1 Use the "cat" command (etc.) to check the "/etc/path_to_inst" file and identify the physical pathname ofthe device for which multipathing is not required.

In this example, the physical path is "/pci@8,600000/SUNW,qlc@2".

# cat /etc/path_to_inst"/pci@8,600000/SUNW,qlc@2" 0 "qlc""/pci@8,600000/SUNW,qlc@2/fp@0,0" 5 "fp""/pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e0113ce2e1,0" 5 "ssd"

The underlined portion indicates the physical path name.

2 Add the following line to the "fp.conf" file using the "vi" command.

• Solaris 11 OS

Copy the "/kernel/drv/fp.conf" file to the "/etc/driver/drv" directory and add the line to the newly copied"fp.conf" file.

• Solaris 10 OS

Add the line to the "/kernel/drv/fp.conf" file.

name="fp" parent=" " port=0 mpxio-disable="yes";

Enter the physical path name for the underlined portion.

Example:

name="fp" parent="/pci@8,600000/SUNW,qlc@2" port=0 mpxio-disable="yes";

If the "/etc/driver/drv/fp.conf" file already exists, directly edit it and do not overwrite it.




3 Restart the server to effect the new settings.

The multipath can be configured by creating the "/reconfigure" file and restarting the server.

# touch /reconfigure# /usr/sbin/shutdown -y -g0 -i6




FUJITSU Storage ETERNUS DX, ETERNUS AF Configuration Guide -Server Connection-(Fibre Channel) for Oracle Solaris

Multipath Driver Settings

P3AM-6322-11ENZ0

Date of issuance: April 2018Issuance responsibility: FUJITSU LIMITED

• The content of this manual is subject to change without notice.

• This manual was prepared with the utmost attention to detail. However, Fujitsu shall assume no responsibility for anyoperational problems as the result of errors, omissions, or the use of information in this manual.

• Fujitsu assumes no liability for damages to third party copyrights or other rights arising from the use of any informationin this manual.

• The content of this manual may not be reproduced or distributed in part or in its entirety without prior permission fromFujitsu.

configuration guide -server connection- · refer to "configuration guide -server connection-...

Documents