The Contents and Structure of this Manual. This document is composed of the following ten chapters.

Transcription

1

2

3 Preface This document briefly explains the operations that need to be performed by the user in order to connect an ETERNUS2000 model 100 or 200, ETERNUS4000 model 300, 400, 500, or 600, or ETERNUS8000 model 700, 800, 900, 1100, 1200, 2100, or 2200 Disk storage system to a HP- UX server. This document should be used in conjunction with any other applicable user manuals, such as those for the ETERNUS2000 model 100 or 200, ETERNUS4000 model 300, 400, 500, or 600, or ETERNUS8000 model 700, 800, 900, 1100, 1200, 2100, or 2200 Disk storage system, server, OS used, LAN cards, drivers, etc. Note that this manual refers the following documents: 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 Also, note that in this document the ETERNUS2000 models 100 and 200, ETERNUS4000 models 300, 400, 500, and 600, and ETERNUS8000 models 700, 800, 900, 1100, 1200, 2100, and 2200 Disk storage systems are collectively referred to as ETERNUS Disk storage systems. First Edition February 2010 The Contents and Structure of this Manual This document is composed of the following ten chapters. Chapter 1 Workflow This describes how to connect the ETERNUS Disk storage system to a server. 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 storage systems and server. Chapter 4 Checking the Server Information This describes how to check the server information registered in the ETERNUS Disk storage system. 3

4 Preface Chapter 5 Installing and Setting up ETERNUSmgr This describes how to install ETERNUSmgr. Chapter 6 Setting up the ETERNUS Disk Storage Systems This describes how to use ETERNUSmgr to set up the ETERNUS Disk storage systems. Chapter 7 Installing the iscsi Software Initiator and Setting up the Server This describes how to install the iscsi Software Initiator and set up the server. Chapter 8 Checking Connections This describes how to check the connection status between server and ETERNUS Disk storage systems. Chapter 9 Setting up the Multipath Configuration This describes the PV-Links settings. Chapter 10 Creating Logical Volume Manager (LVM) Logical Volumes This describes how to create an LVM logical volume 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 to thoroughly read and understand its contents before using the product. After reading, store this manual in a safe place for future reference. FUJITSU has made every effort to ensure the safety of the users and other personnel, and to prevent property damage. When using this product, carefully follow the instructions described in this manual. Acknowledgments HP-UX is a trademark of Hewlett-Packard Company in the U.S. and other countries. The company names, product names and service names mentioned in this document are registered trademarks or trademarks of their respective companies. 4

5 Preface Naming Conventions Other names The iscsi interface modules used by the ETERNUS Disk storage system are referred to as "iscsi port". "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. Italics are used to show variables such as values and characters that appear in command parameters and output examples. 5

6 Contents Chapter 1 Workflow...8 Chapter 2 Checking the Server Environment Hardware Basic Software Network Interface Card Multipath Configuration Chapter 3 Notes ETERNUS Disk Storage System Setup Notes Number of LUNs Notes LAN Environment Notes Logical Volume Manager (LVM) Notes Server Startup and Power Supply Control Notes Chapter 4 Checking the Server Information...14 Chapter 5 Installing and Setting up ETERNUSmgr...15 Chapter 6 Setting up the ETERNUS Disk Storage Systems...16 Chapter 7 Installing the iscsi Software Initiator and Setting up the Server Downloading and Installing the iscsi Software Initiator Setting up the Server Setting up the Command Queue Depth Maximum Number of Volume Group Settings iscsi Basic Settings Server Settings when CHAP Authentication is Used Server Settings when Bidirectional CHAP Authentication is Used Chapter 8 Checking Connections Turning on the Devices Logical Unit Recognition

7 Contents Chapter 9 Chapter 10 Setting up the Multipath Configuration...26 Creating Logical Volume Manager (LVM) Logical Volumes Creating the Volume Group Creating the LVM Logical Volume

8 Chapter 1 Workflow This chapter describes how to connect the ETERNUS Disk storage systems to a server. The workflow is shown below. Documents required in the workflow: 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 Manuals supplied with the server, Multipath Driver, and LAN card Workflow Install the ETERNUSmgr and set up the ETERNUS Disk storage system If the ETERNUSmgr is to be used, install it and set up the ETERNUS Disk storage system, and identify the WWNs of the server-side Fibre Channel cards (required later). Refer - "Chapter 5 Installing and Setting up ETERNUSmgr" (page 15) - "Chapter 6 Setting up the ETERNUS Disk Storage Systems" (page 16) - Install ETERNUSmgr. ETERNUSmgr Install Guide - Check ETERNUSmgr operation. ETERNUSmgr User Guide - Set 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 8

9 Chapter 1 Workflow > Install the iscsi Software Initiator and Set up the Server Refer Set up the OS to connect to the ETERNUS Disk storage system. - "Chapter 7 Installing the iscsi Software Initiator and Setting up the Server" (page 17) Set the Server to Recognize the Logical Units Refer Set up the server so that it can recognize the ETERNUS Disk storage system logical units (LUN). - "8.2 Logical Unit Recognition" (page 24) Set up the server as required by the system configuration. Refer - Set PV-Links "Chapter 9 Setting up the Multipath Configuration" (page 26) - Set Logical Volume Manager (LVM) "Chapter 10 Creating Logical Volume Manager (LVM) Logical Volumes" (page 27) 9

10 Chapter 2 Checking the Server Environment Server environment details are provided in the "Server Support Matrix". 2.1 Hardware Refer to the "Server Support Matrix" for details. 2.2 Basic Software Refer to the "Server Support Matrix" for details. 2.3 Network Interface Card Refer to the "Server Support Matrix" for details. 2.4 Multipath Configuration Refer to the "Server Support Matrix" for details. 10

11 Chapter 3 Notes 3.1 ETERNUS Disk Storage System Setup Notes Be sure to set the sub system parameters. 3.2 Number of LUNs Notes When using PV-Links, no more than 128 LUNs should be visible on any given path. If more than 128 LUNs are found in one path, assignment of unique Target IDs and Disk IDs will not be possible and desired behavior will not be observed in this environment. This is because the PV-Links function assumes that if devices on different paths have the same Target ID and Disk ID, then they must connect to the same LUN. The maximum number of unique Target IDs and Disk IDs for the device is

12 Chapter 3 Notes > 3.3 LAN Environment Notes 3.3 LAN Environment Notes The ETERNUS Disk storage system can be connected to a server via an existing LAN. However, a decrease in LAN performance may be observed by prior users of said LAN. 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 LAN switch [Business LAN] Business LAN Business server A LAN card #2 LAN card #1 LAN card #3 Business server B LAN card #2 LAN card #1 LAN card #3 Business server C LAN card #2 LAN card #1 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 LUN3 ETERNUS Disk storage system 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 disk storage systems (equivalent to the FC zones). 12

13 Chapter 3 Notes > 3.4 Logical Volume Manager (LVM) Notes 3.4 Logical Volume Manager (LVM) Notes A mirrored LVM configuration using ETERNUS Disk storage systems LUNs is not recommended. [Bad Block Relocation] attribute must be disabled on LVM Logical volume which resides on ETERNUS Disk storage systems. - Example procedure # lvchange -r N /dev/vg01/lvol_name Execute this command for all logical volumes created on ETERNUS Disk storage systems' LUNs to disable [Bad Block Relocation]. If [Bad Block Relocation] is not disabled, file system may be damaged. Raw device access to an LVM logical volume must use an I/O block size that is a multiple of 1024bytes. 3.5 Server Startup and Power Supply Control Notes Before turning the server on, check that the ETERNUS Disk storage systems and LAN switches are all "Ready". If the server is turned on and they are not "Ready", the server will not be able to recognize the ETERNUS Disk storage systems. Also, when the ETERNUS Disk storage system power supply is being controlled by a connected server, make sure that the ETERNUS Disk storage system 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 Disk storage systems, and already saved data may also be affected. 13

14 Chapter 4 Checking the Server Information Check the server information registered in the ETERNUS Disk storage system. The following server information should be checked: iscsi initiator name Execute the following command: iscsiutil -l The iscsi name is displayed in the "Initiator Name" column. IP address of the LAN card used to connect the ETERNUS Disk storage system Execute the following command: ifconfig Set this IP address if it is not already set. Initiator CHAP Name The Initiator CHAP Name is the user name for unidirectional CHAP authentication, and is not required if CHAP authentication is not used. Execute the following command: iscsiutil -pd The Initiator CHAP Name is displayed in the "Initiator CHAP Name" column of the applicable target information. CHAP Secret The CHAP Secret is the password for unidirectional CHAP authentication, and is not required if CHAP authentication is not used. Execute the following command: iscsiutil -pd The CHAP Secret is displayed in the "CHAP Secret" column of the applicable target information. 14

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

16 Chapter 6 Setting up the ETERNUS Disk Storage Systems 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 "ETERNUS Disk storage systems Server Connection Guide (iscsi) ETERNUS Disk Storage System Settings for ETERNUS2000" or "ETERNUS Disk storage systems Server Connection Guide (iscsi) ETERNUS Disk Storage System Settings for ETERNUS4000, ETERNUS8000", and "ETERNUSmgr User Guide". 16

17 Chapter 7 Installing the iscsi Software Initiator and Setting up the Server 7.1 Downloading and Installing the iscsi Software Initiator Procedure 1 Use a Web browser to access the web-site at the following URL: 2 Use the web-site's Search function to search for "iscsi Software Initiator". The search results table is displayed. 3 In the search results table, click the [Receive for Free >>] button. 4 Enter the required information on the screen and click the [Next >>] button. 5 In the "Download Software" field, click the [Download Directly >>] button. The "iscsi Software Initiator" package is downloaded. 6 In the "Document" field, click the "Installation Instructions" link. Install the iscsi Software Initiator according to the displayed installation procedure. End of procedure 17

18 Chapter 7 Installing the iscsi Software Initiator and Setting up the Server > 7.2 Setting up the Server 7.2 Setting up the Server iscsi connection settings depend on the CHAP authentication method. Perform the settings to match the CHAP authentication to be used. CHAP authentication method None Required settings Command queue depth Maximum number of volume groups iscsi basic settings Refer - "7.2.1 Setting up the Command Queue Depth" - "7.2.2 Maximum Number of Volume Group Settings" - "7.2.3 iscsi Basic Settings" Unidirectional CHAP authentication Bidirectional CHAP authentication Command queue depth Maximum number of volume groups iscsi basic settings CHAP authentication Refer - "7.2.1 Setting up the Command Queue Depth" - "7.2.2 Maximum Number of Volume Group Settings" - "7.2.3 iscsi Basic Settings" - "7.2.4 Server Settings when CHAP Authentication is Used" Command queue depth Maximum number of volume groups iscsi basic settings CHAP authentication Bidirectional CHAP authentication Refer - "7.2.1 Setting up the Command Queue Depth" - "7.2.2 Maximum Number of Volume Group Settings" - "7.2.3 iscsi Basic Settings" - "7.2.4 Server Settings when CHAP Authentication is Used" - "7.2.5 Server Settings when Bidirectional CHAP Authentication is Used" 18

19 Chapter 7 Installing the iscsi Software Initiator and Setting up the Server > 7.2 Setting up the Server Setting up the Command Queue Depth Set the number of commands allowed to be queued (command queue depth) on each LUN in the ETERNUS Disk storage systems from the LAN card. This setting optimizes the connection between the ETERNUS Disk storage systems and the server. The command queue depth setting will depend on the number of the ETERNUS Disk storage system LUNs recognized by the server on a single path, as shown in the table below. No. of LUNs recognized by the server on a single path Command queue depth 1 to or more 4 For HP-UX11iv2 Set the command queue depth using the kernel parameter "scsi_max_qdepth". The "scsi_max_qdepth" is set using System Administration Manager (SAM). When the command queue depth is set using SAM, all SCSI devices are affected. When changing the command queue depth of a particular SCSI device, the "scsictl" command is used. However, because the information set by the "scsictl" command becomes invalid when the server is shut down, it is necessary to carry out setting every time the server is activated. For details about the "scsictl" command, refer to the HP-UX manual Maximum Number of Volume Group Settings Set the kernel parameter maxvgs that limits the number of volume groups. Default value is 10. If 11 or more volume groups are to be created, maxvgs will need to be changed. Kernel parameter maxvgs is set using System Administration Manager (SAM). One volume group is created for OS installation area. If 10 (default) is set for maxvgs, up to 9 new volume groups can be created. 19

20 Chapter 7 Installing the iscsi Software Initiator and Setting up the Server > 7.2 Setting up the Server iscsi Basic Settings The following items are required for the iscsi connection and must be set: iscsi Initiator Name iscsi connection target information Authentication Method Procedure 1 Set the shell environment variable PATH. Add the location of the iscsi Software Initiator executable files to the PATH environment variable. # PATH=$PATH:/opt/iscsi/bin 2 Set the iscsi Initiator name. Either the iscsi Qualified Name (iqn) or IEEE EUI-64 (eui) format may be used. This setting is not required if the default iscsi Initiator name is to be used. To set the iscsi Initiator name, execute the "iscsiutil" command as follows: # iscsiutil [iscsi-device-file] -i -N <initiator-name> 3 Confirm the iscsi Initiator name. Use the "iscsiutil" command to check the iscsi Initiator name. The iscsi Initiator name shown here is used for the ETERNUS Disk storage system settings. # iscsiutil -l 4 Save the statically-recognized iscsi target information in the kernel registry. Use the "iscsiutil" command to save the iscsi target information. # iscsiutil [iscsi-device-file] -a -I <ip-address> [-P <tcp-port>][-m <portal-grp-tag>] Example: For an ETERNUS Disk storage system with a connection target iscsi port IP address of : # iscsiutil -a -I

21 Chapter 7 Installing the iscsi Software Initiator and Setting up the Server > 7.2 Setting up the Server 5 Confirm the iscsi target information is now in the kernel registry. # iscsiutil -p -D 6 Set whether CHAP authentication is to be used or not. If CHAP authentication is to be performed, set "CHAP". If CHAP authentication is not required, set "None". Example: When CHAP authentication is not used: # iscsiutil -t authmethod None Note: # iscsiutil -t authmethod CHAP None The above command sets CHAP authentication to operate according to the ETERNUS Disk storage system setting. The CHAP authentication method is selected if the ETERNUS Disk storage system uses CHAP for its responses, otherwise CHAP authentication is not performed. End of procedure Server Settings when CHAP Authentication is Used The following items are required for CHAP authentication and must be set: CHAP Method Initiator CHAP Name CHAP Secret Procedure 1 Set the CHAP Method. The CHAP authentication method (unidirectional or bidirectional) must be set. Set the CHAP Method value indicated in the following table: CHAP authentication method Unidirectional CHAP authentication Bidirectional CHAP authentication CHAP Method setting CHAP_UNI CHAP_BI 21

22 Chapter 7 Installing the iscsi Software Initiator and Setting up the Server > 7.2 Setting up the Server Use the "iscsiutil" command to set the CHAP Method. # iscsiutil [iscsi-device-file] -u -H <chap-authentication-type> [-T <target-name> [-I <ip-address>] [-P <tcp-port>] Example: To set unidirectional CHAP authentication for the ETERNUS Disk storage system whose iscsi port IP address is # iscsiutil -u -H CHAP_UNI -I Set Initiator CHAP Name. An Initiator CHAP Name must be set for each target set in Step 4 of "7.2.3 iscsi Basic Settings". The Initiator CHAP Name set here must match that set in target information. Use the "iscsiutil" command to set the Initiator CHAP Name. # iscsiutil [iscsi-device-file] -u -N <chap-initiator-name> [-T <target-name> [-I <ip-address>] [-P <tcp-port>] [-M <portal-grp-tag>]] Example: To set "mychapname" as the CHAP name for a specific target ( ): # iscsiutil -u -N mychapname -I Set CHAP Secret. A CHAP Secret must be set for each target set in Step 4 of "7.2.3 iscsi Basic Settings". The CHAP Secret set here must match that set in target information. Use the "iscsiutil" command to set the CHAP Secret. # iscsiutil [iscsi-device-file] -u -W <chap-initiator-secret> [-T <target-name> [-I <ip-address>] [-P <tcp-port>] [-M <portal-grp-tag>]] Example: To set "mychapsecret" as the CHAP Secret for a specific target ( ): # iscsiutil -u -W mychapsecret -I End of procedure 22

23 Chapter 7 Installing the iscsi Software Initiator and Setting up the Server > 7.2 Setting up the Server Server Settings when Bidirectional CHAP Authentication is Used The following items are required for bidirectional CHAP authentication and must be set: NAS Hostname NAS Secret RADIUS Server Hostname iradd activation Procedure 1 Set the parameters relating to the NAS (Network Access Server) and RADIUS server. Use the "iscsiutil" command to set the NAS Hostname, NAS Secret, and RADIUS Server Hostname: # iscsiutil [iscsi-device-file] -u -R <nas-hostname> <nas-secret> <radius-server-hostname> Description of the NAS and RADIUS parameters: Setting item <nas-hostname> <nas-secret> <radius-server-hostname> Description Specify the IP address or hostname of the Network Access Server (NAS). This is the server that is to connect to the ETERNUS Disk storage system via the iscsi interface. The specified IP address or hostname must be for a LAN card that is able to communicate with the RADIUS server. Set the NAS secret already set in the RADIUS server. Specify the IP address or hostname of the RADIUS server. 2 Activate the daemon (iradd) that communicates with the RADIUS server. # iradd The iradd daemon will automatically restart every time the system is started. End of procedure 23

24 Chapter 8 Checking Connections 8.1 Turning on the Devices To turn on the connected devices, use the following procedures: Procedure 1 Turn on any devices (such as LAN switches) on the LAN path between the ETERNUS Disk storage system and server. 2 After checking that the Ready (or equivalent) LED of the LAN switch is lit, turn on the ETERNUS Disk storage systems. 3 After checking that the ETERNUS Disk storage systems' Ready LED is lit, turn on the server. End of procedure 8.2 Logical Unit Recognition Make the server recognize the logical units (LUN) set in the ETERNUS Disk storage systems. Procedure 1 Use the "ioscan" command to check which devices are connected. Enter as follows for LegacyView (old format) results: # ioscan -fn Check that all connected devices are listed in the ioscan output and "CLAIMED" is displayed in "S/W State". 24

25 Chapter 8 Checking Connections > 8.2 Logical Unit Recognition The following shows the output of ioscan (LegacyView) when ETERNUS Disk storage system is connected to the server. # ioscan H/W Path Class Description ============================================================ : 255/0 iscsi iscsi Virtual Node 255/0/0.0 ext_bus iscsi-scsi Protocol Interface 255/0/0.0.0 target 255/0/ disk FUJITSU E /0/ disk FUJITSU E /0/ disk FUJITSU E /0/ disk FUJITSU E /0/ disk FUJITSU E2000 : # When the ETERNUS Disk storage system is connected for the first time, the device file (for example, /dev/dsk/c4t0d0) sometimes may not be created. If this happens, use the "insf" command to create the device file. Specify the hardware path name as follows, and execute. # insf -H hw_path_to_device -e End of procedure 25

26 Chapter 9 Setting up the Multipath Configuration This chapter explains how to set up the multipath configuration using HP-UX s default "PV-Links" function. "PV-Links" is a Logical Volume Manager (LVM) function that is available for all HP-UX versions. LVM for HP-UX supplies PV-Links as a standard function for configuring paths in a redundant configuration (path failover function). PV-Links is set by including multiple paths connected to one physical volume in one volume group. Only one of the paths will be set as the Active path, with the other paths being made Standby paths. However, load on the system may be better balanced by spreading the server accesses over multiple Active paths. PV-Links are only available for LVM configurations. When using PV-Links, confirm that the PV-Links paths have identical target IDs. 26

27 Chapter 10 Creating Logical Volume Manager (LVM) Logical Volumes This chapter explains how to create LVM logical volumes using commands. Refer to the applicable manuals for more on how to use these commands. Do not execute the "mediainit" command on ETERNUS Disk storage systems. No problems in operation will occur even if this command is not used Creating the Volume Group Procedure 1 Create a directory with the same name as the volume group that is to be created. E.g. if volume group "/dev/vg01" is to be created: # mkdir /dev/vg01 2 Create a character special file called "group". Create this character special file in the directory created in Step 1. # mknod /dev/vg01/group c 64 0x In order to prevent volume group overlaps, a 0xNN0000 (minor number) must be specified for the "mknod" command (where NN is some value between 00 and FF). For HP-UX11iv2, the upper limit for NN is determined by the "maxvgs" tunable kernel parameter (default is 10, max is 256). The "ls" command may be used to check the 0xNN0000 values currently being used by "group" files. 27

28 Chapter 10 Creating Logical Volume Manager (LVM) Logical Volumes > 10.1 Creating the Volume Group Example: Checking the 0xNN0000 in current use # ls -l /dev/*/group crw-r root sys 64 0x Dec 14 14:08 /dev/vg00/group # In this example, only the "dev/vg00" volume group exists, with a "group" file minor number (NN) of "00". 3 Use the "pvcreate" command to create an LVM physical volume for the volume group. Format this disk ("c4t0d0") as an LVM compatible physical disk. # pvcreate /dev/rdsk/c4t0d0 Note that if the LUN is accessible via multiple paths, this procedure only needs to be executed for one of them. 4 Create the volume group. Create the volume group "/dev/vg01" on the physical volume "/dev/dsk/c4t0d0". # vgcreate /dev/vg01 /dev/dsk/c4t0d0 Use the following, if alternative paths are to be configured using the PV-Links function: # vgcreate /dev/vg01 /dev/dsk/c4t0d0 /dev/dsk/c5t0d0 Here "/dev/dsk/c4t0d0" and "/dev/dsk/c5t0d0" are different paths that access the same physical volume. In this example "/dev/dsk/c4t0d0" is the primary link (that is normally used) and "/dev/dsk/c5t0d0" is the alternative link (that is used if the primary link fails). 5 Confirm the details of the created volume group. Display and confirm the volume group information for "dev/vg01": # vgdisplay -v /dev/vg01 For a PV-Links configuration, confirm that the alternative path is set as planned. This is indicated by an "Alternative Link" note after the device path in the "PV Name" column. The maximum available logical volume capacity may also be confirmed from the output information. Maximum logical volume size = PE Size Free PE End of procedure 28

29 Chapter 10 Creating Logical Volume Manager (LVM) Logical Volumes > 10.2 Creating the LVM Logical Volume 10.2 Creating the LVM Logical Volume Procedure 1 Create a 100MB logical volume "lvol1" in the volume group "/dev/vg01". # lvcreate -L 100 -n lvol1 /dev/vg01 The logical volume capacity may be increased as necessary. The logical volume capacity should be a multiple of the PE Size. When the specified logical volume capacity is not an exact multiple of the PE Size, it is rounded up to the next multiple of the PE Size. 2 Disable Bad Block Relocation. Disable [Bad Block Relocation] for all LVM logical volumes created on the ETERNUS Disk storage system LUNs. Add a "N" (upper-case) after the "-r" option. # lvchange -r N /dev/vg01/lvol1 This command must be executed for all logical volumes created on ETERNUS Disk storage system LUNs. If Bad Block Relocation is not disabled on all logical volumes, the file system may be damaged. 3 Confirm the details of the created LVM logical volume. Display and confirm the LVM logical volume information for "/dev/vg01/lvol1": # lvdisplay /dev/vg01/lvol1 29

30 Chapter 10 Creating Logical Volume Manager (LVM) Logical Volumes > 10.2 Creating the LVM Logical Volume Double-check that the "Bad block" row shows a value of "NONE" in the output. This indicates that Bad Block Relocation is totally disabled. --- Logical volumes --- LV Name /dev/vg01/lvol1 VG Name /dev/vg01 LV Permission read/write LV Status available/syncd Mirror copies 0 Consistency Recovery MWC Schedule parallel LV Size (Mbytes) 100 Current LE 25 Allocated PE 25 Stripes 0 Stripe Size (Kbytes) 0 Bad block NONE Allocation strict IO Timeout (Seconds) default # End of procedure 30

31 ETERNUS Disk storage systems Server Connection Guide (iscsi) for HP-UX Date of issuance: February 2010 Issuance responsibility: FUJITSU LIMITED 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.

32