eternus2000 disk storage systems server connection guide ...• "eternusmgr install...

P

Preface

This document briefly explains the operations that need to be performed by the user in order toconnect an ETERNUS2000 model 100 or 200 Disk storage system to a server running Linux viaa SAS interface.

This document should be used in conjunction with any other applicable user manuals, such asthose for the ETERNUS2000 model 100 or 200 Disk storage system, server, OS used, SAScards, drivers, etc.Note that this manual refers the following documents.

• Server Support Matrix• ETERNUS2000 Disk storage systems Server Connection Guide (SAS) ETERNUS Disk

Storage System Settings• ETERNUSmgr Install Guide• ETERNUSmgr User Guide

Also, note that in this document the ETERNUS2000 models 100 and 200 Disk storage systemsare collectively referred to as ETERNUS Disk storage systems.

Second EditionDecember 2010

The Contents and Structure of this Manual

This document is composed of the following 11 chapters.

• Chapter 1 Workflow

This describes how to connect the ETERNUS Disk storage systems to a server running Linux

• Chapter 2 Checking the Server Environment

This describes which servers can be connected to ETERNUS Disk storage systems.

• Chapter 3 Notes

This describes issues that should be noted when connecting the ETERNUS Disk storagesystems and server.

• Chapter 4 Installing and Setting Up ETERNUSmgr

This describes how to install ETERNUSmgr.

• Chapter 5 Setting Up the ETERNUS Disk Storage Systems

This describes how to set up the ETERNUS Disk storage systems using ETERNUSmgr.

ETERNUS2000 Disk storage systems Server Connection Guide (SAS) for Linux

3 Copyright 2010 FUJITSU LIMITED

3AM-4212-02ENZ0

Preface

P

• Chapter 6 Installing the SAS Card Drivers

This describes how to install the SAS card drivers and set up the server.

• Chapter 7 Setting Up the Server

This describes how to connect the server and ETERNUS Disk storage systems.

• Chapter 8 LUN Recognition

This describes how to recognize the ETERNUS Disk storage system logical units from server.

• Chapter 9 Setting Up and Checking the ETERNUS Multipath Driver

This describes how to set up and check the ETERNUS Multipath Driver.

• Chapter 10 Setting Up and Checking the device-mapper multipath

This describes how to set up and check the device-mapper multipath.

• Chapter 11 Setting Up the File System

This describes how to create a file system on the ETERNUS Disk storage systems.

Safe Use of this Product

■ Using this manual

This manual contains important information to ensure the safe use of this product. Be sure tothoroughly read and understand its contents before using the product. After reading, store thismanual in a safe place for future reference.FUJITSU has made every effort to ensure the safety of the users and other personnel, and toprevent property damage. When using this product, carefully follow the instructions described inthis manual.

Acknowledgments

• Linux is a trademark or registered trademark of Linus Torvalds in the USA and other countries.

• Red Hat, PRM, and all Red Hat-based trademarks and logos are trademarks or registered trademarks of Red Hat, Inc. in the USA and other countries.

• SUSE is a registered trademark of SUSE Linux AG., a subsidiary of Novell, Inc.• LSI and the LSI logo design are trademarks or registered trademarks of LSI Logic

Corporation or its subsidiaries.• The company names, product names and service names mentioned in this document are

registered trademarks or trademarks of their respective companies.



3AM-4212-02ENZ0

Preface

P

Naming Conventions

■ Product Names

• Red Hat Enterprise Linux series products are as described below."xxx" in the following table indicates an architecture name (example: x86), and "x" indicates a version number.

• SUSE Linux Enterprise Server series products are as described below."xxx" in the following table indicates an architecture name (example: x86), and "x" indicates a version number.

Product Names Abbreviation

Red Hat Enterprise Linux RHEL

Red Hat Enterprise Linux 5 RHEL5

Red Hat Enterprise Linux 5.x RHEL5.x

Red Hat Enterprise Linux 5 (for xxx) RHEL5 (xxx)

Red Hat Enterprise Linux 5.x (for xxx) RHEL5.x (xxx)

Red Hat Enterprise Linux AS v.4 RHEL-AS4

Red Hat Enterprise Linux AS v.4 Update x RHEL-ASS4 Update x

Red Hat Enterprise Linux AS 4.x RHEL-AS4.x

Red Hat Enterprise Linux AS (v.4 for xxx) RHEL-AS4 (xxx)

Red Hat Enterprise Linux AS (v.4 for xxx) Update x RHEL-AS4 (xxx) Update x

Red Hat Enterprise Linux AS (4.x for x86) RHEL-AS4.x (xxx)

Red Hat Enterprise Linux ES v.4 RHEL-ES4

Red Hat Enterprise Linux ES v.4 Update x RHEL-ES4 Update x

Red Hat Enterprise Linux ES 4.x RHEL-ES4.x

Red Hat Enterprise Linux ES (v.4 for xxx) RHEL-ES4 (xxx)

Red Hat Enterprise Linux ES (v.4 for xxx) Update x RHEL-ES4 (xxx) Update x

Red Hat Enterprise Linux ES (4.x for xxx) RHEL-ES4.x (xxx)

Product Names Abbreviation

SUSE Linux Enterprise Server SLES

SUSE Linux Enterprise Server 11 SLES11

SUSE Linux Enterprise Server 11 Service Packx SLES11 SPx

SUSE Linux Enterprise Server 11 for xxx SLES11 (xxx)

SUSE Linux Enterprise Server 11 Service Packx for xxx SLES11 SPx (xxx)

SUSE Linux Enterprise Server 10 SLES10

SUSE Linux Enterprise Server 10 Service Packx SLES10 SPx

SUSE Linux Enterprise Server 10 for xxx SLES10 (xxx)

SUSE Linux Enterprise Server 10 Service Packx for xxx SLES10 SPx (xxx)



3AM-4212-02ENZ0

Preface

P

■ Other names

• "SAS card" refers to the SAS interface module normally used by the server. A "Host Bus Adapter" (HBA) or "Channel Adapter" (CA) may be used instead, depending on the server.

• "SAS cable" refers to the SAS interface cables used to connect the ETERNUS Disk storage system and server.

• Italics are used to show variables such as values and characters that appear in command parameters and output examples.

Copyright 2010 FUJITSU LIMITED



3AM-4212-02ENZ0

P

Contents

Chapter 1 Workflow ...................................................................................91.1 When the Multipath Driver is not Used ............................................................... 91.2 When the Multipath Driver is Used ................................................................... 11

Chapter 2 Checking the Server Environment........................................132.1 Server Hardware .............................................................................................. 132.2 Basic Software ................................................................................................. 132.3 SAS Cards ....................................................................................................... 132.4 ETERNUS Multipath Driver or device-mapper multipath ................................. 13

Chapter 3 Notes .......................................................................................143.1 SAS Card Notes ............................................................................................... 143.2 Server Startup and Power Supply Control Notes ............................................. 143.3 RHEL Notes ..................................................................................................... 143.4 SLES Notes ...................................................................................................... 14

Chapter 4 Installing and Setting Up ETERNUSmgr ..............................15

Chapter 5 Setting Up the ETERNUS Disk Storage Systems ................16

Chapter 6 Installing the SAS Card Drivers ............................................176.1 For Fujitsu SAS Cards ..................................................................................... 176.2 For LSI Logic SAS Cards ................................................................................. 17

Chapter 7 Setting Up the Server.............................................................187.1 For Fujitsu SAS Cards ..................................................................................... 187.2 For LSI Logic SAS Cards ................................................................................. 18

Chapter 8 LUN Recognition ....................................................................198.1 Making the Server Recognize the LUNs .......................................................... 198.2 Displaying the Recognized Logical Units ......................................................... 20

8.2.1 For Red Hat Enterprise Linux .................................................................................................... 208.2.2 For SUSE Linux Enterprise Server ............................................................................................ 21



3AM-4212-02ENZ0

Contents

P

Chapter 9 Setting Up and Checking the ETERNUS Multipath Driver .............................................22

Chapter 10 Setting Up and Checking the device-mapper multipath ................................................23

10.1 For RHEL ......................................................................................................... 2310.1.1 Modifying "/etc/multipath.conf" .................................................................................................. 2310.1.2 Enabling the device-mapper multipath ...................................................................................... 2410.1.3 Rebooting the Linux Server ....................................................................................................... 2410.1.4 Recognizing the Post device-mapper multipath LUNs .............................................................. 2410.1.5 Checking the device-mapper multipath Status and Created Devices ....................................... 25

10.2 For SLES .......................................................................................................... 2510.2.1 Editing "/etc/multipath.conf" ....................................................................................................... 2510.2.2 Enabling the device-mapper multipath ...................................................................................... 2610.2.3 Rebooting the Linux Server ....................................................................................................... 2710.2.4 Recognizing the Post device-mapper multipath LUNs .............................................................. 2710.2.5 Checking the device-mapper multipath Status and Created Devices ....................................... 27

Chapter 11 Setting Up the File System ....................................................29



3AM-4212-02ENZ0

Chapter 1 Workflow

P

Which documents need to be referred to varies with the connection environment. Refer to theworkflow that follows to determine which documents are required.

Required Documents

• ETERNUS2000 Disk storage systems Server Connection Guide (SAS) for Linux (This manual)

• Server Support Matrix• ETERNUS2000 Disk storage systems Server Connection Guide (SAS) ETERNUS Disk

Storage System Settings• ETERNUSmgr Install Guide• ETERNUSmgr User Guide• Other manuals provided with each product (server, SAS Cards, and Multipath Driver)

1.1 When the Multipath Driver is not Used

The documents and workflow required when a multipath driver is not used are as follows.

Workflow

Install ETERNUSmgr and Set Up the ETERNUS Disk Storage SystemIf ETERNUSmgr is to be used, install it and set up the ETERNUS Disk storage system.

Refer

- "Chapter 2 Checking the Server Environment" (page 13)- "Chapter 4 Installing and Setting Up ETERNUSmgr" (page 15)- "Chapter 5 Setting Up the ETERNUS Disk Storage Systems" (page 16)- Installing ETERNUSmgr

• "ETERNUSmgr Install Guide"- Checking the setup and maintenance operations

• "ETERNUSmgr User Guide"- Setting up the ETERNUS Disk storage system

• "ETERNUS2000 Disk storage systems Server Connection Guide (SAS) ETERNUS Disk Storage System Settings"



3AM-4212-02ENZ0

Chapter 1 Workflow > 1.1 When the Multipath Driver is not Used

P

Install the SAS Card DriverInstall the appropriate driver for the SAS card being used.

Refer

- Checking the SAS Card driver versions• "Chapter 6 Installing the SAS Card Drivers" (page 17)• "Server Support Matrix"

Set Up the Linux ServerSet the parameters required for connection to the ETERNUS Disk storage system.

Refer

- "7.1 For Fujitsu SAS Cards" (page 18)- "7.2 For LSI Logic SAS Cards" (page 18)

Set the Server to Recognize the Logical UnitsSet up the server so that it can recognize the ETERNUS Disk storage systems' LUN (logical units).

Refer

- "Chapter 8 LUN Recognition" (page 19)



3AM-4212-02ENZ0

Chapter 1 Workflow > 1.2 When the Multipath Driver is Used

P

1.2 When the Multipath Driver is Used

The documents and workflow required when a multipath driver is used are as follows.

Workflow

Set Up the ETERNUS Disk Storage SystemSet the various parameters required to operate the ETERNUS Disk storage system.

Refer

- "Chapter 2 Checking the Server Environment" (page 13)- "Chapter 5 Setting Up the ETERNUS Disk Storage Systems" (page 16)- Installing ETERNUSmgr

• "ETERNUSmgr Install Guide"- Checking the setup and maintenance operations

• "ETERNUSmgr User Guide"- Setting up the ETERNUS Disk storage system

• "ETERNUS2000 Disk storage systems Server Connection Guide (SAS) ETERNUS Disk Storage System Settings"

Install the SAS Card DriverInstall the appropriate driver for the SAS card being used.

Refer

- Checking the SAS Card driver versions• "Chapter 6 Installing the SAS Card Drivers" (page 17)• "Server Support Matrix"

Set Up the Linux ServerSet up the required parameters for the connection to the ETENRUS Disk storage system.

Refer

- "7.1 For Fujitsu SAS Cards" (page 18)- "7.2 For LSI Logic SAS Cards" (page 18)



3AM-4212-02ENZ0

Chapter 1 Workflow > 1.2 When the Multipath Driver is Used

P

Set the Server to Recognize the Logical UnitsSet up the server so that it can recognize the ETERNUS Disk storage systems' LUN (logical units).

Refer

- "Chapter 8 LUN Recognition" (page 19)

For ETERNUS Multipath Driver For device-mapper multipath

Set Up ETERNUS Multipath DriverSet up ETERNUS Multipath Driver.

Refer

- "Chapter 9 Setting Up and Checking the ETERNUS Multipath Driver" (page 22)

Set Up the device-mappermultipath

Set up and confirm the device-mapper multipath.

Refer

- "Chapter 10 Setting Up and Checking the device-mapper multipath" (page 23)



3AM-4212-02ENZ0

Chapter 2 Checking the Server Environment

P

Server environment details are provided in the "Server Support Matrix".

2.1 Server Hardware

Refer to the "Server Support Matrix".

2.2 Basic Software


2.3 SAS Cards


2.4 ETERNUS Multipath Driver or device-mapper multipath




3AM-4212-02ENZ0

Chapter 3 Notes

P

Note the following issues when performing the relevant operation.

3.1 SAS Card Notes

Check the BIOS and firmware versions for the SAS cards being used. If these are different fromthe versions in the "Server Support Matrix", download and install the appropriate BIOS or firm-ware version from the SAS card vendor's web-site.

3.2 Server Startup and Power Supply Control Notes

Before turning the server on, check that the ETERNUS Disk storage systems are all "Ready". If the server is turned on and they are not "Ready", the server will not be able to recognize theETERNUS Disk storage systems.Also, when the ETERNUS Disk storage system power supply is being controlled by a connectedserver, make sure that the ETERNUS Disk storage system does not shut down before the con-nected servers. If turned off, data writes from the running server cannot be saved to the ETERNUS Disk storagesystems, and already saved data may also be affected.

3.3 RHEL Notes

For details involving RHEL, refer to the Red Hat web-site and any documentation available.

3.4 SLES Notes

For details involving SLES, refer to the Novell web-site and any documentation available.



3AM-4212-02ENZ0

Chapter 4 Installing and Setting Up ETERNUSmgr

P

If ETERNUSmgr is to be used, install it according to the directions given in the "ETERNUSmgrInstall Guide". After the installation, set up ETERNUSmgr following the instructions in the"ETERNUSmgr User Guide".



3AM-4212-02ENZ0

Chapter 5 Setting Up the ETERNUS Disk Storage Systems

P

Set up the ETERNUS Disk storage systems using ETERNUSmgr.

ETERNUS Disk storage systems' setup can be performed independently of server setup.For details on how to perform these settings, refer to the "ETERNUS2000 Disk storage systemsServer Connection Guide (SAS) ETERNUS Disk Storage System Settings" and "ETERNUSmgrUser Guide".



3AM-4212-02ENZ0

Chapter 6 Installing the SAS Card Drivers

P

6.1 For Fujitsu SAS Cards

Refer to the documentation provided with the SAS card for the SAS card driver installation proce-dure.

6.2 For LSI Logic SAS Cards

The SAS card driver does not need to be installed because it is one of the OS default drivers.



3AM-4212-02ENZ0

Chapter 7 Setting Up the Server

P

7.1 For Fujitsu SAS Cards

Refer to the documentation provided with the SAS card for the server setup procedure.

7.2 For LSI Logic SAS Cards

The server does not need to be set up.



3AM-4212-02ENZ0

Chapter 8 LUN Recognition

P

8.1 Making the Server Recognize the LUNs

The following procedure is used to get the server to recognize the ETERNUS Disk storage sys-tem LUNs.

Procedure

1 When the driver installation process is complete, shut down the OS and turn the server power off.

2 Turn the ETERNUS Disk storage system power off.

3 Use the SAS cables to connect the Linux server to the ETERNUS Disk storage system.

4 Turn the ETERNUS Disk storage system back on.

5 Turn the server power back on and boot the OS.Check that the Linux server recognizes the ETERNUS Disk storage system LUNs.At boot up, Linux automatically recognizes all SCSI disks and assigns them successivedevice names starting from "sda". When assigning the device names, any internal SCSIdisks are assigned first, followed by the assignment of the ETERNUS Disk storagesystems' LUNs. Example: If there is one internal SCSI disk, it is assigned a SCSI devicename as follows:

End of procedure

SCSI device name by-id name (Example) Explanation

/dev/sda /dev/disk/by-id/scsi-36003005700026cc011251e4b0b80ac59 Internal SCSI disk

/dev/sdb /dev/disk/by-id/scsi-3600000e00d0000000001000000000000

ETERNUS Disk Storage Systems' LUN/dev/sdc /dev/disk/by-id/scsi-

3600000e00d0000000001000000010000

/dev/sdd /dev/disk/by-id/scsi-3600000e00d0000000001000000020000



3AM-4212-02ENZ0

Chapter 8 LUN Recognition > 8.2 Displaying the Recognized Logical Units

P

8.2 Displaying the Recognized Logical Units

The driver version and information of each LUN's SCSI device name, etc. are displayed in theconsole message when Linux is booted up. Although this console message disappears soonfrom the screen, it can be re-displayed using the following command:

8.2.1 For Red Hat Enterprise Linux

The driver version and information of each LUN's SCSI device name, etc. are displayed in theconsole message when Linux is booted up. Although this console message disappears soonfrom the screen, it can be re-displayed using the following command:

• "dmesg" command for LUN displayUse the "dmesg" command in order to confirm whether Linux has recognized the LUNs in theETERNUS Disk storage systems.The following shows an example:

• "cat" command for LUN displayUse the "cat" command to display the "/proc/scsi/scsi" file, where you can confirm therecognized SCSI devices.The following shows an example of this.

At this point the Multipath Driver has not been set up yet, so two SCSI devices are shown foreach connected LUN (i.e. if there are 3 LUNs, 6 SCSI devices are shown).

#dmesg|less :ioc0: LSISAS1068E B3: Capabilities={Initiator}PCI: Setting latency timer of device 0000:09:00.0 to 64scsi1 : ioc0: LSISAS1068E B3, FwRev=011b2900h, Ports=1, MaxQ=483, IRQ=169 Vendor: FUJITSU Model: E2000 Rev: 0000 Type: Direct-Access ANSI SCSI revision: 05 Vendor: FUJITSU Model: E2000 Rev: 0000 Type: Direct-Access ANSI SCSI revision: 05

# cat /proc/scsi/scsiAttached devices:Host: scsi0 Channel: 02 Id: 00 Lun: 00 Vendor: LSI Model: MegaRAID SAS RMB Rev: 1.02 Type: Direct-Access ANSI SCSI revision: 05Host: scsi1 Channel: 00 Id: 01 Lun: 00 Vendor: FUJITSU Model: E2000 Rev: 0000 Type: Direct-Access ANSI SCSI revision: 05Host: scsi1 Channel: 00 Id: 01 Lun: 01 Vendor: FUJITSU Model: E2000 Rev: 0000 Type: Direct-Access ANSI SCSI revision: 05Host: scsi1 Channel: 00 Id: 01 Lun: 02 Vendor: FUJITSU Model: E2000 Rev: 0000 Type: Direct-Access ANSI SCSI revision: 05Host: scsi1 Channel: 00 Id: 01 Lun: 03 Vendor: FUJITSU Model: E2000 Rev: 0000 Type: Direct-Access ANSI SCSI revision: 05Host: scsi1 Channel: 00 Id: 01 Lun: 04 Vendor: FUJITSU Model: E2000 Rev: 0000 Type: Direct-Access ANSI SCSI revision: 05



3AM-4212-02ENZ0

Chapter 8 LUN Recognition > 8.2 Displaying the Recognized Logical Units

P

8.2.2 For SUSE Linux Enterprise Server

• Checking for LUNs in the boot messageOpen the /var/log/boot.msg file to confirm that Linux has recognized the ETERNUS Diskstorage systems' LUNs.The following shows an example (Messages can be scrolled (back and forth) using the arrowkeys).

• Checking for LUNs with the "cat" commandUse the "cat" command to display the "/proc/scsi/scsi" file, which contains a list of recognizedSCSI devices.The following shows an example of this.

At this point the Multipath Driver has not been set up yet, so two SCSI devices are shown foreach connected LUN (i.e. if there are 3 LUNs, 6 SCSI devices are shown).

<5> Vendor: FUJITSU Model: E2000 Rev: 0000<5> Type: Direct-Access ANSI SCSI revision: 05<5> Vendor: FUJITSU Model: E2000 Rev: 0000<5> Type: Direct-Access ANSI SCSI revision: 05 : : :<5>SCSI device sdb: 4096000 512-byte hdwr sectors (2147 MB)<7> sdb: unknown partition table<5>SCSI device sdc: 4096000 512-byte hdwr sectors (2147 MB)<7> sdc: unknown partition table

# cat /proc/scsi/scsiAttached devices:Host: scsi0 Channel: 02 Id: 00 Lun: 00 Vendor: LSI Model: MegaRAID SAS RMB Rev: 1.02 Type: Direct-Access ANSI SCSI revision: 05Host: scsi1 Channel: 00 Id: 01 Lun: 00 Vendor: FUJITSU Model: E2000 Rev: 0000 Type: Direct-Access ANSI SCSI revision: 05Host: scsi1 Channel: 00 Id: 01 Lun: 01 Vendor: FUJITSU Model: E2000 Rev: 0000 Type: Direct-Access ANSI SCSI revision: 05Host: scsi1 Channel: 00 Id: 01 Lun: 02 Vendor: FUJITSU Model: E2000 Rev: 0000 Type: Direct-Access ANSI SCSI revision: 05Host: scsi1 Channel: 00 Id: 01 Lun: 03 Vendor: FUJITSU Model: E2000 Rev: 0000 Type: Direct-Access ANSI SCSI revision: 05Host: scsi1 Channel: 00 Id: 01 Lun: 04 Vendor: FUJITSU Model: E2000 Rev: 0000 Type: Direct-Access ANSI SCSI revision: 05



3AM-4212-02ENZ0

Chapter 9 Setting Up and Checking the ETERNUS Multipath Driver

P

Refer to the documentation provided with the ETERNUS Multipath Driver for the setup and con-firmation procedures when ETERNUS Multipath Driver is used.



3AM-4212-02ENZ0

Chapter 10 Setting Up and Checking the device-mapper multipath

P

Set up and check the device-mapper multipath.

10.1 For RHEL

10.1.1 Modifying "/etc/multipath.conf"

Edit the "/etc/multipath.conf" device-mapper multipath configuration file as follows:

Procedure

1 Comment out the following three lines in "/etc/multipath.conf".

The blacklist section is used to specify any internal disks or other devices that are to beexcluded from the multipath configuration. If required, refer to the Red Hat web-site fordetails.

2 Confirm that the following description is present.

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

End of procedure

# blacklist{ # devnode "*" # }

## Use user friendly names, instead of using WWIDs as names.defaults{ user_friendly_names yes}

devices{ device{ vendor "FUJITSU" product "E2000" prio_callout "/sbin/mpath_prio_alua %d" path_grouping_policy group_by_prio path_selector "round-robin 0" failback immediate no_path_retry 10 } }



3AM-4212-02ENZ0

Chapter 10 Setting Up and Checking the device-mapper multipath > 10.1 For RHEL

P

10.1.2 Enabling the device-mapper multipath

Execute the following command to enable the device-mapper multipaths.

10.1.3 Rebooting the Linux Server

Reboot the Linux server.

Example:

10.1.4 Recognizing the Post device-mapper multipath LUNs

Check the device file created by the device-mapper multipath.

Also check that the device file is linked to the "/dev/dm-X" file.

Example:

# multipath -v 1 # chkconfig --add multipathd # chkconfig multipathd on # multipath # /etc/init.d/multipathd start

# shutdown -r now

# cd /dev/mpath# ls -l lrwxrwxrwx 1 root root 8 Feb 15 20:21 mpath0 -> ../dm-28 lrwxrwxrwx 1 root root 8 Feb 15 20:21 mpath1 -> ../dm-29 lrwxrwxrwx 1 root root 8 Feb 15 20:21 mpath10 -> ../dm-13 : lrwxrwxrwx 1 root root 7 Feb 15 20:21 mpath247 -> ../dm-46 lrwxrwxrwx 1 root root 8 Feb 15 20:21 mpath248 -> ../dm-50 lrwxrwxrwx 1 root root 7 Feb 15 20:21 mpath249 -> ../dm-155



3AM-4212-02ENZ0

Chapter 10 Setting Up and Checking the device-mapper multipath > 10.2 For SLES

P

10.1.5 Checking the device-mapper multipath Status and Created Devices

Check the path status using the "multipath -ll" command.

• When both paths are in normal status (This example is for the ETERNUS2000)

10.2 For SLES

10.2.1 Editing "/etc/multipath.conf"

Edit the "/etc/multipath.conf" device-mapper multipath configuration file as follows:

Procedure

1 Copy the "/usr/share/doc/packages/multipath-tools/multipath.conf.synthetic" file to "/etc".

2 Add the following lines to the file.Add the following lines at the end of the "defaults" section.

# multipath -llmpath2 (3600000e00d00000000000f7e00010000) dm-1 FUJITSU,E2000[size=10G][features=1 queue_if_no_path][hwhandler=0][rw]\_ round-robin 0 [prio=50][active] \_ 4:0:0:1 sde 8:64 [active][ready]\_ round-robin 0 [prio=10][enabled] \_ 3:0:0:1 sdc 8:32 [active][ready]::

When the path status is normal, "[active][ready]" is displayed.

The multipath consists of the block device names "sde" and "sdc". "mpath2" is created.

"E2000" is displayed since the ETERNUS2000 is connected.

Two block device names are displayed for a two-path configuration.

# cp /usr/share/doc/packages/multipath-tools/multipath.conf.synthetic /etc/multipath.conf

defaults{ user_friendly_names yes }



3AM-4212-02ENZ0


P

3 Add the following lines at the end of the "devices" section

• For SLES11

• For SLES10

The blacklist section is used to specify any internal disks or other devices that are to beexcluded from the multipath configuration. If required, refer to the Novell web-site fordetails.

End of procedure

10.2.2 Enabling the device-mapper multipath

Execute the following command to enable the device-mapper multipaths.

devices{ device{ vendor "FUJITSU" product "E2000" prio alua path_grouping_policy group_by_prio path_selector "round-robin 0" failback immediate no_path_retry 10 } }

devices{ device{ vendor "FUJITSU" product "E2000" prio_callout "/sbin/mpath_prio_alua %d" path_grouping_policy multibus path_selector "round-robin 0" failback immediate no_path_retry 10 } }

# insserv boot.multipath multipathd # chkconfig multipathd on # chkconfig boot.multipath on # /etc/init.d/boot.multipath start # /etc/init.d/multipathd start



3AM-4212-02ENZ0


P

10.2.3 Rebooting the Linux Server

Reboot the Linux server.

Example:

10.2.4 Recognizing the Post device-mapper multipath LUNs

Check the device file created by the device-mapper multipath.Also check that the device file is linked to the "/dev/dm-X" file.

Example:

10.2.5 Checking the device-mapper multipath Status and Created Devices

Check the path status using the "multipath -ll" command.

• When both paths are in normal status (This example is for the ETERNUS2000)

# shutdown -r now

#cd /dev/disk/by-name/#ls -llrwxrwxrwx 1 root root 10 Aug 25 13:40 mpatha -> ../../dm-0lrwxrwxrwx 1 root root 10 Aug 25 13:40 mpathb -> ../../dm-1lrwxrwxrwx 1 root root 10 Aug 25 13:39 mpathc -> ../../dm-2lrwxrwxrwx 1 root root 10 Aug 25 13:39 mpathd -> ../../dm-3lrwxrwxrwx 1 root root 10 Aug 25 13:40 mpathe -> ../../dm-4lrwxrwxrwx 1 root root 10 Aug 25 13:39 mpathf -> ../../dm-5lrwxrwxrwx 1 root root 10 Aug 25 13:39 mpathg -> ../../dm-6 :

# multipath -llmpathc (3600000e00d00000000000f7e00010000) dm-2 FUJITSU,E2000size=10G features=’1 queue_if_no_path’ hwhandler=’0’ wp=rw|-+- policy=’round-robin 0’ prio=150 status=active| ‘- 4:0:0:1 sde 8:64 active ready running‘-+- policy=’round-robin 0’ prio=10 status=enabled ‘- 3:0:0:1 sdc 8:32 active ready running::

"E2000" is displayed since the ETERNUS2000 is connected.

The multipath consists of the block device names "sde" and "sdc". "mpathc" is created.

Two block device names are displayed for a two-path configuration.

When the path status is normal, "active ready" is displayed.



3AM-4212-02ENZ0


P

For SLES10, the following message may appear in the path status after executing the "multipath-ll" command. However, there is no actual problem with multipath configuration and operation.

sde: Using deprecated prio_callout '/sbin/mpath_prio_alua %d' (controller setting) Please fixup /etc/multipath.confsdc: Using deprecated prio_callout '/sbin/mpath_prio_alua %d' (controller setting) Please fixup /etc/multipath.conf



3AM-4212-02ENZ0

Chapter 11 Setting Up the File System

P

After Linux has recognized the ETERNUS Disk storage systems' LUNs, access for data storagewill be possible after completing the following steps:

• Setting Up Partitions• Formatting Partitions• Mounting Partitions

If by-id names are being used with Red Hat Enterprise Linux AS v.4 Update4 or Red Hat Enterprise Linux ES v.4 Update 4 or later, then the accessibledevice names will be by-id names.



3AM-4212-02ENZ0

• The contents of this manual are liable to being updated without notice.• While the contents of this manual are the product of all due care and diligence, no

responsibility can be accepted for operational problems arising from any errors or missing information, or other use of the information contained in this manual.

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

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

ETERNUS2000 Disk storage systemsServer Connection Guide (SAS) for Linux

P3AM-4212-02ENZ0

Date of issuance: December 2010Issuance responsibility: FUJITSU LIMITED