ETERNUS Disk storage systems Server Connection Guide ... · server running SUSE Linux Enterprise Server via an iSCSI interface. This document should be used in conjunction with any

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, ETERNUS4000 model 300, 400, 500, or 600, orETERNUS8000 model 700, 800, 900, 1100, 1200, 2100, or 2200 Disk storage system to aserver running SUSE Linux Enterprise Server via an iSCSI interface.

This document should be used in conjunction with any other applicable user manuals, such asthose for the ETERNUS2000 model 100 or 200, ETERNUS4000 model 300, 400, 500, or 600, orETERNUS8000 model 700, 800, 900, 1100, 1200, 2100, or 2200 Disk storage system, server,OS used, adapters, drivers, etc.

This document references the following documents:• Server Support Matrix• ETERNUS Disk storage systems Server Connection Guide (iSCSI) ETERNUS Disk Storage

System Settings for ETERNUS ETERNUS2000• ETERNUS Disk storage systems Server Connection Guide (iSCSI) ETERNUS Disk Storage

System Settings for ETERNUS4000, ETERNUS8000• ETERNUSmgr Install Guide• ETERNUSmgr User Guide

Also, note that in this document the ETERNUS2000 models 100 and 200, ETERNUS4000 mod-els 300, 400, 500, and 600, and ETERNUS8000 models 700, 800, 900, 1100, 1200, 2100, and2200 Disk storage systems are 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 nine chapters.

• Chapter 1 Workflow

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

• Chapter 2 Checking the Server Environment

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

• Chapter 3 LAN Switch Connection

This describes how to connect the ETERNUS Disk storage system to the server via a LANswitch.

ETERNUS Disk storage systems Server Connection Guide (iSCSI) for Linux(SUSE Linux Enterprise Server)

3 Copyright 2010 FUJITSU LIMITED

3AM-4152-02ENZ0

Preface

P

• Chapter 4 Notes

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

• Chapter 5 Setting Up the Linux Server

This describes how to install and set up the Linux server.

• Chapter 6 Installing and Setting Up ETERNUSmgr

This describes how to install ETERNUSmgr.

• Chapter 7 Setting Up the ETERNUS Disk Storage Systems

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

• Chapter 8 ETERNUS Disk Storage System Logical Unit Recognition

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

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

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

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.

• SUSE is a registered trademark of SUSE Linux AG., a subsidiary of Novell, Inc.• The company names, product names and service names mentioned in this document are

registered trademarks or trademarks of their respective companies.



3AM-4152-02ENZ0

Preface

P

Naming Conventions

■ Product Names

• "SLES" refers to SUSE Linux Enterprise Server.

• "SLES11" refers to the following products:- SUSE Linux Enterprise Server 11

• "SLES10" refers to the following products:- SUSE Linux Enterprise Server 10

■ Other names

• "iSCSI port" or "Channel Adapter" (CA) refers to the iSCSI interface module used in the ETERNUS Disk storage systems to connect to the server.

• "LAN card" refers to the iSCSI interface module normally used in the server. A "Network Interface Card" (NIC), "LAN adapter", or "LAN board" may be used instead, depending on the server.

Copyright 2010 FUJITSU LIMITED



3AM-4152-02ENZ0

P

Contents

Chapter 1 Workflow ...................................................................................8

Chapter 2 Checking the Server Environment........................................102.1 Hardware .......................................................................................................... 102.2 Basic Software ................................................................................................. 102.3 LAN Cards ........................................................................................................ 102.4 Multipath Driver ................................................................................................ 10

Chapter 3 LAN Switch Connection.........................................................11

Chapter 4 Notes .......................................................................................124.1 LAN Environment Notes ................................................................................... 124.2 Server Startup and Power Supply Control Notes ............................................. 124.3 SLES Notes ...................................................................................................... 12

Chapter 5 Setting Up the Linux Server ..................................................135.1 Preparation ....................................................................................................... 13

5.1.1 Installing the "open-iscsi" package ............................................................................................ 135.1.2 Preparing the device-mapper multipath setup ........................................................................... 13

5.2 Setting Up Automatic iSCSI Service ................................................................ 145.3 Setting Up the Network Environment ............................................................... 145.4 Checking the iSCSI Initiator Name ................................................................... 14

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

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

Chapter 8 ETERNUS Disk Storage System Logical Unit Recognition.............................................................................17

8.1 When CHAP Authentication is not Used .......................................................... 178.2 When Unidirectional CHAP Authentication is Used ......................................... 188.3 When Bidirectional CHAP Authentication is Used ........................................... 198.4 Rebooting the Linux Server .............................................................................. 208.5 Recognizing LUNs ........................................................................................... 20

Chapter 9 Setting Up and Checking the device-mapper multipath.....219.1 Editing "/etc/multipath.conf" .............................................................................. 21



3AM-4152-02ENZ0

Contents

P

9.2 Enabling the device-mapper multipath ............................................................. 229.3 Rebooting the Linux Server .............................................................................. 229.4 Recognizing the Post device-mapper multipath LUNs ..................................... 239.5 Checking the device-mapper multipath Status ................................................. 23



3AM-4152-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

• ETERNUS Disk storage systems Server Connection Guide (iSCSI) for Linux (SUSE Linux Enterprise Server) (This manual)

• Server Support Matrix• ETERNUS Disk storage systems Server Connection Guide (iSCSI) ETERNUS Disk Storage

System Settings for ETERNUS2000• ETERNUS Disk storage systems Server Connection Guide (iSCSI) ETERNUS Disk Storage

System Settings for ETERNUS4000, ETERNUS8000• ETERNUSmgr Install Guide• ETERNUSmgr User Guide• Other manuals provided with each product (server, Multipath Driver, and LAN card)

Workflow

Set Up the Linux ServerSet up the OS, hardware, software, and iSCSI environment.

Refer

- "Chapter 5 Setting Up the Linux Server" (page 13)



3AM-4152-02ENZ0

Chapter 1 Workflow >

P

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 6 Installing and Setting Up ETERNUSmgr" (page 15)- "Chapter 7 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

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

• "ETERNUS Disk storage systems Server Connection Guide (iSCSI) ETERNUS Disk Storage System Settings for ETERNUS4000, ETERNUS8000"

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 ETERNUS Disk Storage System Logical Unit Recognition" (page 17)

Set Up and Check the device-mapper multipathsIf device-mapper multipathing is used, set up and check the device-mapper multipaths.

Refer

- "Chapter 9 Setting Up and Checking the device-mapper multipath" (page 21)



3AM-4152-02ENZ0

Chapter 2 Checking the Server Environment

P

Refer to the "Server Support Matrix" to check the server environment.

2.1 Hardware

Refer to the "Server Support Matrix".

2.2 Basic Software


2.3 LAN Cards


2.4 Multipath Driver




3AM-4152-02ENZ0

Chapter 3 LAN Switch Connection

P

• As with an FC-SAN, because of the large data flows (traffic volumes) the iSCSI LAN is assumed to be a dedicated LAN separate from the business and management LANs, and constructed with its own LAN switch.

• iSCSI LAN redundancy is achieved by the use of multipaths.• For IP network security reasons too, it is useful to separate the iSCSI LAN (for data transfers)

and management LAN (for administration) to prevent cross-access between them (use of VLAN to separate the LAN segments is recommended).

Example LAN switch connection configuration

*1: In this system configuration, multipaths provide redundant connections between the servers andstorage system. LAN switches #1 and #2 provide physical separation of the network paths.

*2: A separate LAN segment is provided in the LAN switch (using the switch VLAN function) for eachgrouping of business servers and disk storage systems (equivalent to the FC zones).

Business server A

LANcard#2

LANcard#1

Business server B

LANcard#2

LANcard#1

Business server C

LANcard#2

LANcard#1

LANcard#3

LAN switch[Business LAN]

LAN switch[Management LAN]ETERNUS Disk storage system

12

LAN switch #1[iSCSI LAN]

1 2 3

10 11 12

LUN1 LUN2

10

2 3

11

LAN switch #2[iSCSI LAN]

LANcard#3

LANcard#3

1

LUN3 ManagementLAN port

LAN switches should notbe inter-connected (*1)

A separate LAN segment is used for eachServer/Storage grouping. (*2)Here, LAN ports 1, 2 and 10 comprise VLAN1,while LAN ports 3 and 11 comprise VLAN2.

The iSCSI LAN and managementLAN segments are kept separatein the iSCSI LAN switches, helpingmaintain the security of each.

Similarly to FC-SAN, adedicated LAN is used foriSCSI, not the business LAN.

Business LAN

iSCSI LAN

Management LAN



3AM-4152-02ENZ0

Chapter 4 Notes

P

4.1 LAN Environment Notes

• A dedicated iSCSI connection LAN is required, separate to the operation LAN and manage-ment LAN.

• The iSCSI connection LAN should only contain 1000BASE-T compatible devices.• When connecting the ETERNUS Disk storage system and server via a LAN switch, use a

VLAN or similar function to isolate this connection on a separate segment within the LAN switch from other network or iSCSI access segments.

4.2 Server Startup and Power Supply Control Notes

Before turning the server on, check that the ETERNUS Disk storage systems and LAN switchesare 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. Similarly, the LAN switches must also be turned off after the connected servershave been shut down.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.

4.3 SLES Notes

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



3AM-4152-02ENZ0

Chapter 5 Setting Up the Linux Server

P

5.1 Preparation

5.1.1 Installing the "open-iscsi" package

Red Hat Package Manager (RPM) is used to set up the iSCSI environment in the Linux server.Check that one of the following RPMs is installed. If not, install it.

For SLES10 SP2: open-iscsi-2.0.707-0.44.<Architecture name> or later

Installation execution example

5.1.2 Preparing the device-mapper multipath setup

Use the following Red Hat Package Manager (RPM) to set up the device-mapper multipaths. Ifthis RPM is not installed, install it.

Installation execution example

# rpm -ivh open-iscsi-2.0.707-0.19.<Architecture_name>.rpm

device-mapper-1.02.03-8.2.<Architecture_name> or laterdevice-mapper-32bit-1.02.03-8.2.<Architecture_name> or latermultipath-tools-0.4.6-25.17.<Architecture_name> or later

# rpm -ivh device-mapper-1.02.03-8.2.<Architecture_name> or later



3AM-4152-02ENZ0

Chapter 5 Setting Up the Linux Server > 5.2 Setting Up Automatic iSCSI Service

P

5.2 Setting Up Automatic iSCSI Service

YaST is used to set up the iSCSI service. Refer to the Novell web-site for details of the setup pro-cedure.

Procedure

1 Start YaST and then run the iSCSI Initiator in Miscellaneous.The iSCSI Initiator Overview window appears.

2 In the iSCSI Initiator Overview window, open the Service tab and select "When Booting".

End of procedure

5.3 Setting Up the Network Environment

Set the IP information (IP address and subnet mask) of the LAN card.

5.4 Checking the iSCSI Initiator Name

Check which iSCSI initiator name is described as the default in the "/etc/iscsi/initiatorname.iscsi"file.This iSCSI initiator name should be used for the ETERNUS Disk storage system settings.

Set the same subnet as that set for the ETERNUS Disk storage systemLAN card. For details of the ETERNUS Disk storage system settings, refer to "Chapter7 Setting Up the ETERNUS Disk Storage Systems" (page 16).



3AM-4152-02ENZ0

Chapter 6 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-4152-02ENZ0

Chapter 7 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. Fordetails on how to perform these settings, refer to the "ETERNUS Disk storage systems ServerConnection Guide (iSCSI) ETERNUS Disk Storage System Settings for ETERNUS2000" or"ETERNUS Disk storage systems Server Connection Guide (iSCSI) ETERNUS Disk StorageSystem Settings for ETERNUS4000, ETERNUS8000", and "ETERNUSmgr User Guide".



3AM-4152-02ENZ0

Chapter 8 ETERNUS Disk Storage System Logical Unit Recognition

P

Connect the ETERNUS Disk storage system to the server with a LAN cable.After connecting, reboot the Linux server and check that the Linux server recognizes theETERNUS Disk storage system LUNs.YaST is used to set up the server. Refer to the Novell web-site for details of the setup procedurewith YaST.

8.1 When CHAP Authentication is not Used

Procedure

1 Start YaST and then run the iSCSI Initiator in Miscellaneous.

2 Select the "Discovered Targets" tab and click the [Discovery] button to open the iSCSI Initiator Discovery dialog.

3 Set the IP address for the ETERNUS Disk storage system iSCSI port in "IP Address".Keep the default port number value (3260).

4 Check that "No_Authentification" is selected and click the [Next] button.

5 Check that the desired Target is visible in the "Discovered Targets" tab.The "Connected" state of the Target should be "False" at this time.

6 Select the desired Target in the "Discovered Targets" tab, and click the [Log In] button to re-open the CHAP selection dialog.If CHAP authentication is not being used, check that "No_Authentification" is selected andclick the [Next] button.

7 After both path logins have completed, check that the information of the desired Target is visible in the "Connected Targets" of the iSCSI Initiator Overview.

8 Make sure that "Start-Up" for the desired Target is set to "automatic" (if currently set to "manual", select the Target and click the [Toggle Start_Up] button), then click the [Finish] button.

End of procedure



3AM-4152-02ENZ0

Chapter 8 ETERNUS Disk Storage System Logical Unit Recognition > 8.2 When Unidirectional CHAP Authentication is Used

P

8.2 When Unidirectional CHAP Authentication is Used

Procedure




4 Select "Outgoing Authentication" for unidirectional CHAP authentication.

4-1 Enter the UserName that is set in iSCSI Host of the ETERNUS Disk storage system in "UserName".

4-2 Enter the Password that is set in iSCSI Host of the ETERNUS Disk storage system in "Password".

4-3 Click the [Next] button.


6 Select the desired Target in the "Discovered Targets" tab, and click the [Log In] button to re-open the CHAP selection dialog.

6-1 Select "Outgoing Authentication" for unidirectional CHAP authentication.






End of procedure



3AM-4152-02ENZ0

Chapter 8 ETERNUS Disk Storage System Logical Unit Recognition > 8.3 When Bidirectional CHAP Authentication is Used

P

8.3 When Bidirectional CHAP Authentication is Used

Procedure




4 Perform the following procedure when bidirectional CHAP is used.

4-1 Select "Incoming Authentication".



4-4 Select "Outgoing Authentication".

4-5 Enter the UserName that is set in "Set iSCSI Port Parameters" of the ETERNUS Disk storage system in "UserName".

4-6 Enter the Password that is set in "Set iSCSI Port Parameters" of the ETERNUS Disk storage system in "Password".



6 Select the desired Target in the "Discovered Targets" tab, and click the [Log In] button to re-open the CHAP selection dialog.Perform the following procedure for unidirectional CHAP authentication.

6-1 Select "Incoming Authentication".



6-4 Select "Outgoing Authentication".

6-5 Enter the UserName that is set in "Set iSCSI Port Parameters" of the ETERNUS Disk storage system in "UserName".



3AM-4152-02ENZ0

Chapter 8 ETERNUS Disk Storage System Logical Unit Recognition > 8.4 Rebooting the Linux Server

P

6-6 Enter the Password that is set in "Set iSCSI Port Parameters" of the ETERNUS Disk storage system in "Password".




End of procedure

8.4 Rebooting the Linux Server

Reboot the Linux server.

Execution example

8.5 Recognizing LUNs

After rebooting, check that the Linux server recognizes the ETERNUS Disk storage systemLUNs. At boot up, Linux automatically recognizes all SCSI disks and assigns them successivedevice names starting from "sda". When assigning the device names, any internal SCSI disksare assigned first, followed by the assignment of the ETERNUS Disk storage systems' LUNs. Forexample, if there is one internal SCSI disk and three ETERNUS Disk storage system LUNs,SCSI device names are assigned as follows:

# shutdown -r now

SCSI device name by-id name 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-4152-02ENZ0

Chapter 9 Setting Up and Checking the device-mapper multipath

P

Set up and check the device-mapper multipath.

9.1 Editing "/etc/multipath.conf"

Edit the 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.

Add the following lines at the end of the "devices" section.(This example is for the ETERNUS2000)

• For SLES11

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

defaults{ user_friendly_names yes}

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 }}



3AM-4152-02ENZ0

Chapter 9 Setting Up and Checking the device-mapper multipath > 9.2 Enabling the device-mapper multipath

P

• For SLES10

For the ETERNUS2000, specify "E2000" as the "product" option.For the ETERNUS4000, specify "E4000" as the "product" option. For the ETERNUS8000, specify "E8000" as the "product" option.

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

9.2 Enabling the device-mapper multipath

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

9.3 Rebooting the Linux Server

Reboot the Linux server.

Execution example

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

# shutdown -r now



3AM-4152-02ENZ0

Chapter 9 Setting Up and Checking the device-mapper multipath > 9.4 Recognizing the Post device-mapper multipath LUNs

P

9.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.

Execution example

9.5 Checking the device-mapper multipath Status

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

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

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.

#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 :

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

# 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::

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.

E2000 is displayed since theETERNUS2000 is connected.



3AM-4152-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.

ETERNUS Disk storage systemsServer Connection Guide (iSCSI) for Linux (SUSE Linux Enterprise Server)

P3AM-4152-02ENZ0

Date of issuance: December 2010Issuance responsibility: FUJITSU LIMITED