FUJITSU Storage ETERNUS DX Configuration Guide -Server Connection-

Transcription

1 FUJITSU Storage ETERNUS DX Configuration Guide -Server Connection- (iscsi) for Linux

2 This page is intentionally left blank.

3 Preface This manual briefly explains the operations that need to be performed by the user in order to connect an ETERNUS DX to a server running Linux via an iscsi interface. This manual explains how to set up software initiators. When using a hardware initiator, refer to the manuals for each network card. This manual should be used in conjunction with any other applicable user manuals, such as those for the ETERNUS DX, server, OS, adapters, and drivers. Refer to "FUJITSU Storage ETERNUS DX Configuration Guide -Server Connection- Notations" for the notations used in this manual such as product trademarks and product names. For storage systems that are supported by the OS, refer to the Server Support Matrix of the ETERNUS DX. 14th Edition June 2015 The Contents and Structure of this Manual This manual is composed of the following eight chapters. "Chapter 1 Workflow" (page 6) This chapter describes how to connect the ETERNUS DX to a server. "Chapter 2 Checking the Server Environment" (page 8) This chapter describes which servers can be connected to ETERNUS DX storage systems. "Chapter 3 Notes" (page 9) This chapter describes issues that should be noted when connecting the ETERNUS DX storage systems and server. "Chapter 4 Setting Up the Linux Server" (page 13) This chapter describes how to set up the Linux server. "Chapter 5 Installing and Setting Up ETERNUSmgr" (page 17) This chapter describes how to install ETERNUSmgr. "Chapter 6 Setting Up the ETERNUS DX" (page 18) This chapter describes how to use ETERNUS Web GUI or ETERNUSmgr to set up the ETERNUS DX storage systems. "Chapter 7 Setting Up the Server to Recognize LUNs" (page 19) This chapter describes how to make the server recognize the LUNs of the ETERNUS DX. "Chapter 8 Setting Up and Checking the device-mapper multipath" (page 26) This chapter describes what to be set in order to create multipath environment. 3

4 Table of Contents Chapter 1 Workflow Connecting the ETERNUS DX... 6 Chapter 2 Checking the Server Environment Hardware OS (Operating System) LAN Cards Multipath Driver... 8 Chapter 3 Notes Server Startup and Power Supply Control Notes Red Hat Enterprise Linux Notes SUSE Linux Enterprise Server Notes LAN Environment Notes Jumbo Frame Setting Notes Chapter 4 Setting Up the Linux Server For Red Hat Enterprise Linux Preparation Setting Up Automatic iscsi Service Setting CHAP Authentication Setting Up the Network Environment Checking the iscsi Initiator Name Starting the iscsi Service For SUSE Linux Enterprise Server Preparation Setting Up Automatic iscsi Service Setting Up the Network Environment Checking the iscsi Initiator Name...16 Chapter 5 Installing and Setting Up ETERNUSmgr 17 4

5 Table of Contents Chapter 6 Setting Up the ETERNUS DX 18 Chapter 7 Setting Up the Server to Recognize LUNs For ETERNUS DX Storage Systems For Red Hat Enterprise Linux For SUSE Linux Enterprise Server...22 Chapter 8 Setting Up and Checking the device-mapper multipath 26 5

6 Chapter 1 Workflow 1.1 Connecting the ETERNUS DX This chapter describes how to connect the ETERNUS DX to a server running Linux. Which documents need to be referred to varies with the connection environment. Refer to the workflow that follows to determine which documents are required. IPv4 is used for IP address examples in this manual. Required Documents "Server Support Matrix" "FUJITSU Storage ETERNUS DX Configuration Guide -Server Connection- Disk Storage System Settings" that corresponds to the ETERNUS DX to be connected "ETERNUS Web GUI User's Guide" "ETERNUSmgr Install Guide" "ETERNUSmgr User Guide" "FUJITSU Storage ETERNUS DX Configuration Guide -Server Connection- (Fibre Channel/FCoE/iSCSI/SAS) for Linux device-mapper multipath" Manuals supplied with the server, multipath driver, and LAN card Workflow Checking the Server Check that the hardware, OS, LAN cards, and onboard LANs of the server will allow the ETERNUS DX to be connected to. Also, check the notes for operation. "Chapter 2 Checking the Server Environment" (page 8) "Chapter 3 Notes" (page 9) 6

7 Chapter 1 Workflow 1.1 Connecting the ETERNUS DX Setting Up the Linux Server Set up the OS, the hardware, the software, and the iscsi environment. For Red Hat Enterprise Linux - "4.1 For Red Hat Enterprise Linux" (page 13) For SUSE Linux Enterprise Server - "4.2 For SUSE Linux Enterprise Server" (page 16) Installing ETERNUSmgr and Setting up the ETERNUS DX Set up the ETERNUS DX using ETERNUS Web GUI or ETERNUSmgr. "Chapter 5 Installing and Setting Up ETERNUSmgr" (page 17) "Chapter 6 Setting Up the ETERNUS DX" (page 18) Checking the ETERNUS Web GUI operational procedures - "ETERNUS Web GUI User's Guide" Installing ETERNUSmgr - "ETERNUSmgr Install Guide" Checking the ETERNUSmgr operational procedures - "ETERNUSmgr User Guide" Setting up the ETERNUS DX - "FUJITSU Storage ETERNUS DX Configuration Guide -Server Connection- Disk Storage System Settings" that corresponds to the ETERNUS DX to be connected Setting Up the Server to Recognize the Logical Units Set up the server so that it can recognize the LUNs (logical unit numbers) of the ETERNUS DX. For Red Hat Enterprise Linux - "7.1.1 For Red Hat Enterprise Linux" (page 19) For SUSE Linux Enterprise Server - "7.1.2 For SUSE Linux Enterprise Server" (page 22) Setting Up the device-mapper multipath Set up the device-mapper multipath. "Chapter 8 Setting Up and Checking the device-mapper multipath" (page 26) 7

8 Chapter 2 Checking the Server Environment Connection to servers is possible in the following environments. Check the "Server Support Matrix" for server environment conditions. 2.1 Hardware Refer to the "Server Support Matrix". 2.2 OS (Operating System) Refer to the "Server Support Matrix". 2.3 LAN Cards Refer to the "Server Support Matrix". 2.4 Multipath Driver Refer to the "Server Support Matrix". 8

9 Chapter 3 Notes Note the following issues when connecting the ETERNUS DX to a server. 3.1 Server Startup and Power Supply Control Notes Before turning the server on, check that the ETERNUS DX storage systems and LAN switches are all "Ready". Specifically, check that the Ready LED is lit for ETERNUS DX storage systems. If the server is turned on and they are not "Ready", the server will not be able to recognize the ETERNUS DX storage systems. Also, when the ETERNUS DX power supply is being controlled by a connected server, make sure that the ETERNUS DX does not shut down before the connected servers. Similarly, the LAN switches must also be turned off after the connected servers have been shut down. If turned off, data writes from the running server cannot be saved to the ETERNUS DX storage systems, and already saved data may also be affected. 3.2 Red Hat Enterprise Linux Notes For details involving RHEL, refer to the Red Hat web-site and any documentation available. 3.3 SUSE Linux Enterprise Server Notes For details involving SLES, refer to the Novell web-site and any documentation available. 3.4 LAN Environment Notes Since an iscsi LAN handles large amounts of data (traffic volumes) like an FC-SAN, the iscsi LAN must have its own switch and be a dedicated LAN that is separate from the business LANs. Use devices that support transfer speeds of 1Gbit/s or more for an iscsi connection LAN. iscsi LAN redundancy is achieved by the use of multipaths. For IP network security, separate the iscsi LAN from the management LAN (for administration). The iscsi LAN must be configured as a dedicated LAN for each path from a server to the ETERNUS DX. 9

10 Chapter 3 Notes 3.4 LAN Environment Notes Example of a LAN switch connection configuration LAN switch [Business LAN] LAN Card#1 LAN Card#1 LAN Card#1 Business LAN Business server A LAN Card#2 LAN Card#3 Business server B LAN Card#2 LAN Card#3 Business server C LAN Card#2 LAN Card#3 Similarly to FC-SAN, a dedicated LAN is used for iscsi, not the business LAN LAN switch #1 [iscsi LAN] LAN switches should not be inter-connected (*1) LAN switch #2 [iscsi LAN] iscsi LAN Management LAN LUN1 LUN2 ETERNUS DX LUN3 Management LAN port LAN switch [Management LAN] A separate LAN segment is used for each Server/Storage grouping (*2). Here, LAN ports 1, 2 and 10 comprise VLAN1, while LAN ports 3 and 11 comprise VLAN2. The iscsi LAN and management LAN segments are kept separate in the iscsi LAN switches, helping maintain the security of each. *1: In this system configuration, multipaths provide redundant connections between the servers and storage 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 each grouping of business servers and storage systems (equivalent to the FC zones). 10

11 Chapter 3 Notes 3.4 LAN Environment Notes Example of a network address configuration The following example shows a configuration in which multiple servers are connected to multiple CAs. Server A Server B / / / /24 LAN switch #1 (VLAN is recommended) LAN switch #2 (VLAN is recommended) / / / /24 P0 CM0 P1 P0 P1 CM1 ETERNUS DX The following example shows a configuration in which a single server is connected to multiple CAs. Server / /24 LAN switch #1 LAN switch # / / / /24 P0 CM0 P1 P0 P1 CM1 ETERNUS DX 11

12 Chapter 3 Notes 3.5 Jumbo Frame Setting Notes 3.5 Jumbo Frame Setting Notes To enable Jumbo Frame, all the connected devices must support Jumbo Frame. Set the appropriate values for various parameters (such as the MTU size) on each connected device. For details about how to set Jumbo Frame for a LAN card and LAN switch, refer to the OS and each device's manuals. Rebooting the server may be required to apply the new settings. The MTU size that is supported by the ETERNUS DX is 9,000 bytes. 12

13 Chapter 4 Setting Up the Linux Server 4.1 For Red Hat Enterprise Linux Preparation Installing the iscsi-initiator-utils Use the following Red Hat Package Manager (RPM) to set up the iscsi environment in the Linux server. Check that one of the following RPMs is installed. If not, install it. iscsi-initiator-utils el5. Enter the architecture name and the information following it for the underlined portion. Installation execution example # rpm -ivh iscsi-initiator-utils el5.x86_64.rpm Setting Up Automatic iscsi Service The iscsi service must be set to automatically activate when the Linux server starts up. Add the following line to the end of the "/etc/iscsi/iscsid.conf" file: node.conn[0].startup = automatic Setting CHAP Authentication If CHAP authentication is to be used, set it up according to the procedures that follow. If CHAP authentication is not required, these procedures are not required. There are two types of CHAP authentication: unidirectional and bidirectional. For both types, the appropriate CHAP authentication setting is required for the ETERNUS DX Setting Up Unidirectional CHAP Authentication Create the accounts used by the iscsi initiator to connect to the target. 13

14 Chapter 4 Setting Up the Linux Server 4.1 For Red Hat Enterprise Linux Add the following lines to the "/etc/iscsi/iscsid.conf" file: node.session.auth.authmethod = CHAP node.session.auth.username = <(1)> node.session.auth.password = <(2)> discovery.sendtargets.auth.authmethod = CHAP discovery.sendtargets.auth.username = <(1)> discovery.sendtargets.auth.password = <(2)> Enter any username in (1) and any password in (2). Each "username" and "password" must match the ones that are set in the ETERNUS DX. For details of the ETERNUS DX settings, refer to "Chapter 6 Setting Up the ETERNUS DX" (page 18) Setting Up Bidirectional CHAP Authentication In addition to the unidirectional CHAP authentication accounts, additional accounts are required to enable the target to connect to the initiator. Add the following lines to the "/etc/iscsi/iscsid.conf" file: node.session.auth.authmethod = CHAP node.session.auth.username = <(1)> node.session.auth.password = <(2)> node.session.auth.username_in = <(1)> node.session.auth.password_in = <(2)> discovery.sendtargets.auth.authmethod = CHAP discovery.sendtargets.auth.username = <(1)> discovery.sendtargets.auth.password = <(2)> discovery.sendtargets.auth.username_in = <(1)> discovery.sendtargets.auth.password_in = <(2)> Enter any username in (1) and any password in (2). The initiator accounts are shown below. - "node.session.auth.username " - "node.session.auth.password " - "discovery.sendtargets.auth.username " - "discovery.sendtargets.auth.password " The target accounts are shown below. - "node.session.auth.username_in " - "node.session.auth.password_in " - "discovery.sendtargets.auth.username_in " - "discovery.sendtargets.auth.password_in " Every such initiator and target account must be assigned a unique name. Each "username" and "password" must match the ones that are set in the ETERNUS DX. - For details of the ETERNUS DX settings, refer to "Chapter 6 Setting Up the ETERNUS DX" (page 18). 14

15 Chapter 4 Setting Up the Linux Server 4.1 For Red Hat Enterprise Linux Setting Up the Network Environment Set the IP information (IP address and subnet mask) of the LAN card. The LAN card should be set to use the same subnet as that set for the ETERNUS DX that is being connected to. - For details of the ETERNUS DX settings, refer to "Chapter 6 Setting Up the ETERNUS DX" (page 18). For RHEL7, leave the default gateway unspecified and set "Automatic" to OFF for the DNS and Routes settings. For details on how to perform these settings, refer to the Red Hat manuals 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 DX settings Starting the iscsi Service Execute the following command to activate the iscsi service. # /etc/init.d/iscsi start iscsid is stopped Turning off network shutdown. Starting iscsi daemon: [ OK ] [ OK ] Setting up iscsi targets: iscsiadm: No records found! [ OK ] Execute the following command to shut down the iscsi service. # /etc/init.d/iscsi stop The iscsi service does not need to be started for RHEL7 or RHEL6. 15

16 Chapter 4 Setting Up the Linux Server 4.2 For SUSE Linux Enterprise Server 4.2 For SUSE Linux Enterprise Server Preparation Installing the "open-iscsi" package Use the following Red Hat Package Manager (RPM) to set up the iscsi environment in the Linux server. Check that one of the following RPMs is installed. If not, install it. For SLES10SP2: open-iscsi <architecture name> or later Installation execution example # rpm -ivh open-iscsi rpm Enter the architecture name for the underlined portion 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 procedure. 1 Start YaST and then run the iscsi Initiator in Miscellaneous or Network Services. The iscsi Initiator Overview window appears. 2 In the iscsi Initiator Overview window, open the Service tab and select "When Booting" Setting Up the Network Environment Set the IP information (IP address and subnet mask) of the LAN card. The LAN card should be set to use the same subnet as that set for the ETERNUS DX that is being connected to. For details of the ETERNUS DX settings, refer to "Chapter 6 Setting Up the ETERNUS DX" (page 18) 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 DX settings. 16

17 Chapter 5 Installing and Setting Up ETERNUSmgr If ETERNUSmgr is to be used, install it according to the directions given in the "ETERNUSmgr Install Guide". After installation is complete, follow the instructions in "ETERNUSmgr User Guide" and set up ETERNUSmgr. 17

18 Chapter 6 Setting Up the ETERNUS DX Set up the ETERNUS DX storage systems using ETERNUS Web GUI or ETERNUSmgr. ETERNUS DX setup can be performed independently of server setup. For details on how to perform these settings, refer to the following manuals. "FUJITSU Storage ETERNUS DX Configuration Guide -Server Connection- Disk Storage System Settings" that corresponds to the ETERNUS DX to be connected "ETERNUS Web GUI User's Guide" or "ETERNUSmgr User Guide" 18

19 Chapter 7 Setting Up the Server to Recognize LUNs Connect the ETERNUS DX to the Linux server with a LAN cable. After connecting, reboot the Linux server and check that the Linux server recognizes the ETERNUS DX LUNs. 7.1 For ETERNUS DX Storage Systems For Red Hat Enterprise Linux When one of the following conditions applies, change the value of the iscsi initiator timer between a connection to the target and a login to the target. (Refer to " Setting iscsi Initiator Timer" (page 20).) Use a 10Gbit/s iscsi connection and device-mapper multipath for the multipath configuration in an ETER- NUS DX S3 series Use the ETERNUS Multipath Driver and to add a new iscsi connection when a path or device is added after installation of the driver Connecting to the Target Connect to the target ETERNUS DX. Check the iscsi name of the ETERNUS DX. Execute the following command to check that the iscsi name of the ETERNUS DX is displayed correctly: # iscsiadm -m discovery -t sendtargets -p " ":3260 Enter the IP address for the iscsi-ca port of the ETERNUS DX in the underlined portion. Command execution example # iscsiadm -m discovery -t sendtargets -p : :3260,1 iqn com.fujitsu:... The iscsi name "iqn com.fujitsu: " should be seen. 19

20 Chapter 7 Setting Up the Server to Recognize LUNs 7.1 For ETERNUS DX Storage Systems iscsi targets may not be recognized if the lldpad service is operating on the server side when a 10Gbit/s iscsi direct connection is used for the ETERNUS DX S3 series. If this happens, stopping the lldpad service and disabling the automatic service startup during a system boot are required. Execute the following command. Note that the lldpad service is not required to be stopped if the firmware version for ETERNUS DX S3 series is V10L30 or later. # service lldpad stop Stopping lldpad: [ OK ] # chkconfig lldpad off Setting iscsi Initiator Timer To use a 10Gbit/s iscsi connection and device-mapper multipath for the multipath configuration in an ETER- NUS DX S3 series, or to use the ETERNUS Multipath Driver, perform the following configuration before installing the driver. Change the value of iscsi initiator timer from 120 sec. (default) to 25 sec. Configure the following settings for each node of iscsi. # iscsiadm -m node -p " ":3260 -o update -n node.session.timeo.replacement_timeout -v 25 Enter the IP address for the iscsi-ca port of the ETERNUS DX in the underlined portion Logging in to the Target Use the iscsi name from " Connecting to the Target" (page 19) to log in to the target. Execute the following command to log in: # iscsiadm -m node -T "(1)" -p "(2)":3260 -l Enter the IQN for the ETERNUS DX in (1) and the IP address for the iscsi CA port of the ETERNUS DX in (2). Command execution example # iscsiadm -m node -T iqn com.fujitsu:... -p :3260 -l Login session [iface: default, target: iqn com.fujitsu:..., portal: ,3260] If the settings are to be changed or have been changed, the following command to log out of the target must be performed. # iscsiadm -m node -T "(1)" -p "(2)": logout Enter the IQN for the ETERNUS DX in (1) and the IP address for the iscsi CA port of the ETERNUS DX in (2). 20

21 Chapter 7 Setting Up the Server to Recognize LUNs 7.1 For ETERNUS DX Storage Systems Rebooting the Linux Server Reboot the Linux server. Example: # shutdown -r now Setting Up the Server to Recognize LUNs After rebooting, check that the Linux server recognizes the ETERNUS DX LUNs. At boot up, Linux automatically recognizes all SCSI disks and assigns them successive device names starting from "sda". When assigning the device names, any internal SCSI disks are assigned first, followed by the assignment of the ETERNUS DX storage systems' LUNs. For example, if there is one internal SCSI disk and three ETERNUS DX LUNs, SCSI device names are assigned as follows: SCSI device name by-id name (Example) Explanation /dev/sda /dev/disk/by-id/scsi cc011251e4b0b80ac59 Internal SCSI disk /dev/sdb /dev/disk/by-id/scsi e00d ETERNUS DX storage /dev/sdc /dev/disk/by-id/scsi e00d systems' LUN /dev/sdd /dev/disk/by-id/scsi e00d The following command can also be used for checking LUN recognition. # iscsiadm -m session -P 3 iscsi Transport Class version version Target: iqn com.fujitsu:storage-system.eternus-dx400cm1ca1p0 Current Portal: :3260,35 Persistent Portal: :3260,35 ********** Interface: ********** Iface Name: default Iface Transport: tcp Iface Initiatorname: iqn com.redhat:73e33c9424e3 Iface IPaddress: Iface HWaddress: <empty> Iface Netdev: <empty> SID: 1 iscsi Connection State: LOGGED IN iscsi Session State: LOGGED_IN Internal iscsid Session State: NO CHANGE ~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~ ************************ Attached SCSI devices: ************************ Host Number: 7 State: running scsi7 Channel 00 Id 0 Lun: 0 Attached scsi disk sdc State: running scsi7 Channel 00 Id 0 Lun: 1 Attached scsi disk sde State: running... 21

22 Chapter 7 Setting Up the Server to Recognize LUNs 7.1 For ETERNUS DX Storage Systems For SUSE Linux Enterprise Server YaST is used to set up the server. Refer to the Novell web-site for details of the setup procedure with YaST. To use the ETERNUS Multipath Driver, change the value of iscsi initiator timer after LUN is recognized and before the driver is installed. (Refer to " Setting iscsi Initiator Timer" (page 25).) To add a new iscsi connection when a path or device is added after installation of the ETERNUS Multipath Driver, change the value of the iscsi initiator timer between "discovery" and "login". (Refer to " Setting iscsi Initiator Timer" (page 25).) When CHAP Authentication is not Used 1 Start YaST and then run the iscsi Initiator in Miscellaneous or Network Services. 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 DX 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 and click 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 When Unidirectional CHAP Authentication is Used 1 Start YaST and then run the iscsi Initiator in Miscellaneous or Network Services. 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 DX iscsi port in "IP Address". Keep the default port number value (3260). 22

23 Chapter 7 Setting Up the Server to Recognize LUNs 7.1 For ETERNUS DX Storage Systems 4 Select "Outgoing Authentication" for unidirectional CHAP authentication. (1) Enter the UserName that is set in iscsi Host of the ETERNUS DX in "UserName". (2) Enter the Password that is set in iscsi Host of the ETERNUS DX in "Password". (3) 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. (1) Select "Outgoing Authentication" for unidirectional CHAP authentication. (2) Enter the UserName that is set in iscsi Host of the ETERNUS DX in "UserName". (3) Enter the Password that is set in iscsi Host of the ETERNUS DX in "Password". (4) Click 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 When Bidirectional CHAP Authentication is Used 1 Start YaST and then run the iscsi Initiator in Miscellaneous or Network Services. 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 DX iscsi port in "IP Address". Keep the default port number value (3260). 4 Perform the following procedure when bidirectional CHAP is used. (1) Select "Incoming Authentication". (2) Enter the UserName that is set in "Set iscsi Port Parameters" of the ETERNUS DX in "UserName". (3) Enter the Password that is set in "Set iscsi Port Parameters" of the ETERNUS DX in "Password". (4) Select "Outgoing Authentication". (5) Enter the UserName that is set in iscsi Host of the ETERNUS DX in "UserName". (6) Enter the Password that is set in iscsi Host of the ETERNUS DX in "Password". 23

24 Chapter 7 Setting Up the Server to Recognize LUNs 7.1 For ETERNUS DX Storage Systems (7) 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. Perform the following procedure for unidirectional CHAP authentication. (1) Select "Incoming Authentication". (2) Enter the UserName that is set in "Set iscsi Port Parameters" of the ETERNUS DX in "UserName". (3) Enter the Password that is set in "Set iscsi Port Parameters" of the ETERNUS DX in "Password". (4) Select "Outgoing Authentication". (5) Enter the UserName that is set in iscsi Host of the ETERNUS DX in "UserName". (6) Enter the Password that is set in iscsi Host of the ETERNUS DX in "Password". (7) Click 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 Rebooting the Linux Server Reboot the Linux server. Example: # shutdown -r now Setting Up the Server to Recognize LUNs After rebooting, check that the Linux server recognizes the ETERNUS DX LUNs. At boot up, Linux automatically recognizes all SCSI disks and assigns them successive device names starting from "sda". When assigning the device names, any internal SCSI disks are assigned first, followed by the assignment of the ETERNUS DX storage systems' LUNs. For example, if there is one internal SCSI disk and three ETERNUS DX LUNs, SCSI device names are assigned as follows: SCSI device name by-id name (Example) Explanation /dev/sda /dev/disk/by-id/scsi cc011251e4b0b80ac59 Internal SCSI disk /dev/sdb /dev/disk/by-id/scsi e00d ETERNUS DX storage /dev/sdc /dev/disk/by-id/scsi e00d systems' LUN /dev/sdd /dev/disk/by-id/scsi e00d

25 Chapter 7 Setting Up the Server to Recognize LUNs 7.1 For ETERNUS DX Storage Systems Setting iscsi Initiator Timer To use the ETERNUS Multipath Driver, configure the settings shown below before installing the driver. (The settings are not required for SLES9.) Change the value of iscsi initiator timer from 120 sec. (default) to 25 sec. Configure the following settings for each node of iscsi. # iscsiadm -m node -p " ":3260 -o update -n node.session.timeo.replacement_timeout -v 25 Enter the IP address for the iscsi-ca port of the ETERNUS DX in the underlined portion. 25

26 Chapter 8 Setting Up and Checking the device-mapper multipath Set up and check the device-mapper multipath. For the procedures, refer to "FUJITSU Storage ETERNUS DX Configuration Guide -Server Connection- (Fibre Channel/FCoE/iSCSI/SAS) for Linux device-mapper multipath". 26

27 FUJITSU Storage ETERNUS DX Configuration Guide -Server Connection- (iscsi) for Linux Date of issuance: June 2015 Issuance 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 any operational 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 information in this manual. The content of this manual may not be reproduced or distributed in part or in its entirety without prior permission from Fujitsu.

28