The Contents and Structure of this Manual. This document is composed of the following 12 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 server running HP-UX via a Fibre Channel interface. 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, Fibre Channel cards, drivers, etc. Note that this manual refers the following documents: Server Support Matrix Server Support Matrix for FC-SWITCH ETERNUS Disk storage systems Server Connection Guide (Fibre Channel) ETERNUS Disk Storage System Settings ETERNUS Disk storage systems Server Connection Guide (Fibre Channel) Fibre Channel Switch Settings 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. Fourth Edition December 2010 The Contents and Structure of this Manual This document is composed of the following 12 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's WWN settings. 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 Setting up the Fibre Channel Switches This describes how to setup the Fibre Channel switches. Chapter 8 Installing Drivers and Setting up the Server This describes the driver and server settings. Chapter 9 Checking Connections This describes how to check the connection status between server and ETERNUS Disk storage systems. Chapter 10 Setting up the Multipath Configuration This describes the settings when operating with a multipath configuration. Chapter 11 Creating Logical Volume Manager (LVM) Logical Volumes This describes how to create an LVM logical volume on the ETERNUS Disk storage systems. Chapter 12 SAN Boot This provides notes for a SAN Boot. 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. 4

5 Preface Acknowledgments HP-UX is a trademark of Hewlett-Packard Company in the U.S. and other countries. Symantec, Symantec logo, VERITAS, and VERITAS logo are registered trademarks of Symantec Corp. in the U.S. and its affiliated companies. VERITAS Volume Manager and VERITAS Cluster Server are trademarks of Symantec Corp. and its affiliated companies. The company names, product names and service names mentioned in this document are registered trademarks or trademarks of their respective companies. Naming Conventions Other names "Channel Adapter" (CA) refers to a Fibre Channel interface module used in the ETERNUS Disk storage systems to connect to the server. "Fibre Channel card" refers to the Fibre Channel interface module normally used in the server. A "Host Bus Adapter" (HBA) or "Channel Adapter" (CA) 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 OS Fibre Channel Cards Multipath Configuration Integrity VM VERITAS Volume Manager (VxVM) VERITAS Cluster Server (VCS) Chapter 3 Notes Setup Notes for the ETERNUS Disk Storage Systems Fibre Channel Switch Notes Logical Volume Manager (LVM) Notes HP Serviceguard Notes HP Integrity VM Notes VERITAS Volume Manager (VxVM) Notes VERITAS Cluster Server (VCS) Notes Server Startup and Power Supply Control Notes Chapter 4 Checking the Server Information...17 Chapter 5 Installing and Setting up ETERNUSmgr...19 Chapter 6 Setting up the ETERNUS Disk Storage Systems...20 Chapter 7 Setting up the Fibre Channel Switches...21 Chapter 8 Installing Drivers and Setting up the Server Installing the Drivers Setting up the Server Setting up the Command Queue Depth Maximum Number of Volume Group Settings Chapter 9 Checking Connections Turning on the Devices

7 Contents 9.2 Logical Unit Recognition Chapter 10 Setting up the Multipath Configuration Multipath Configuration using PV-Links Multipath Configuration using Native Multipath Chapter 11 Creating Logical Volume Manager (LVM) Logical Volumes Creating the Volume Group Creating the LVM Logical Volume Chapter 12 SAN Boot

8 Chapter 1 Workflow Applicable reference documents vary depending on the connection environment. The documents and workflow required are as follows. Documents required in the workflow: Server Support Matrix Server Support Matrix for FC-SWITCH ETERNUS Disk storage systems Server Connection Guide (Fibre Channel) ETERNUS Disk Storage System Settings ETERNUS Disk storage systems Server Connection Guide (Fibre Channel) Fibre Channel Switch Settings ETERNUS Disk storage systems Server Connection Guide (Fibre Channel) for HP-UX ETERNUSmgr Install Guide ETERNUSmgr User Guide Manuals supplied with the server, Fibre Channel card, Fibre Channel card driver, and Multipath Driver 8

9 Chapter 1 Workflow > 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 4 Checking the Server Information" (page 17) - "Chapter 5 Installing and Setting up ETERNUSmgr" (page 19) - "Chapter 6 Setting up the ETERNUS Disk Storage Systems" (page 20) - 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 (Fibre Channel) ETERNUS Disk Storage System Settings Set up the Fibre Channel Switches If a Fibre Channel switch is to be used, set it up now. Refer - Set up the Fibre Channel switches. "Chapter 7 Setting up the Fibre Channel Switches" (page 21) ETERNUS Disk storage systems Server Connection Guide (Fibre Channel) Fibre Channel Switch Settings - Check the Fibre Channel switch connection requirements. Server Support Matrix for FC-SWITCH Install the Fibre Channel Card Drivers and Set the Parameters Install the Fibre Channel card drivers, and set up the server environment. Refer - "Chapter 8 Installing Drivers and Setting up the Server" (page 22) - Check the driver version for the Fibre Channel card being used. Server Support Matrix 9

10 Chapter 1 Workflow > Set up the Server Environment Set up the OS to connect to the ETERNUS Disk storage system. Refer - "8.2 Setting up the Server" (page 22) Set the Server to Recognize the Logical Units Set up the server so that it can recognize the ETERNUS Disk storage system logical units (LUN). Refer - "9.2 Logical Unit Recognition" (page 25) Set the Server to Match the System Configuration Set up the server as required by the system configuration. Refer - Multipath configurations Set PV-Links "10.1 Multipath Configuration using PV-Links" (page 27) Set Native Multipath "10.2 Multipath Configuration using Native Multipath" (page 28) VERITAS Volume Manager Dynamic Multipathing (VxVM DMP) Facility "3.6 VERITAS Volume Manager (VxVM) Notes" (page 15) - Volume manager Logical Volume Manager (LVM) "Chapter 11 Creating Logical Volume Manager (LVM) Logical Volumes" (page 30) VERITAS Volume Manager (VxVM) "3.6 VERITAS Volume Manager (VxVM) Notes" (page 15) Create LVM Volumes Create LVM logical volumes. Refer - "Chapter 11 Creating Logical Volume Manager (LVM) Logical Volumes" (page 30) 10

11 Chapter 2 Checking the Server Environment ETERNUS Disk storage systems can connect to servers operating in the following environments. Check the environment of your server. 2.1 Hardware Refer to the "Server Support Matrix" for details. 2.2 OS Refer to the "Server Support Matrix" for details. 2.3 Fibre Channel Cards Refer to the "Server Support Matrix" for details. 2.4 Multipath Configuration Refer to the "Server Support Matrix" for details. 2.5 Integrity VM Refer to the "Server Support Matrix" for details. 11

12 Chapter 2 Checking the Server Environment > 2.6 VERITAS Volume Manager (VxVM) 2.6 VERITAS Volume Manager (VxVM) Refer to the "Server Support Matrix" to check the compatibility of HP-UX and VxVM versions. 2.7 VERITAS Cluster Server (VCS) Refer to the "Server Support Matrix" to check the compatibility of HP-UX and VCS versions. 12

13 Chapter 3 Notes 3.1 Setup Notes for the ETERNUS Disk Storage Systems Be sure to set the sub system parameters. Ensure that the ETERNUS Disk storage system Loop-IDs are set to "Manual". The Loop-IDs must be unique within each FC-AL loop, and should be assigned in the ascending order. Do not assign 0x7D as an ETERNUS Disk storage system Loop-ID. 3.2 Fibre Channel Switch Notes Which Fibre Channel switches can be connected to the ETERNUS Disk storage system varies depending on the connection environment (server OS and ETERNUS Disk storage system model). Refer to the "Server Support Matrix for FC-SWITCH" before starting. When using a Fibre Channel switch (ETERNUS SN200 series, Brocade DCX series) between the server and ETERNUS Disk storage system, refer to the "ETERNUS Disk storage systems Server Connection Guide (Fibre Channel) Fibre Channel Switch Settings" for help in preparing and setting up the Fibre Channel switch. Set the Fibre Channel switch domain ID, to anything other than "8". When the domain ID is set to "8", the device cannot be recognized correctly. When carrying out maintenance on the Fibre Channel switches, the switch domain ID must be the same after maintenance as it was before. Make certain that reconnection is made to the correct port after carrying out the maintenance of the ETERNUS Disk storage system by using the same port number as it was used before maintenance. Set the link speed of the Fibre Channel switch ports according to the link speeds of the server-side Fibre Channel cards, as follows: Maximum link speed of Fibre Channel card 8Gbps 4Gbps Combination of devices Maximum link speed of Fibre Channel switch 8Gbps 4Gbps 2Gbps 8Gbps 4Gbps 2Gbps Set the Fibre Channel switch port link speed to... 8Gbps fixed 4Gbps fixed 2Gbps fixed 4Gbps fixed 2Gbps fixed 13

14 Chapter 3 Notes > 3.3 Logical Volume Manager (LVM) Notes Maximum link speed of Fibre Channel card 2Gbps Combination of devices Maximum link speed of Fibre Channel switch 8Gbps 4Gbps 2Gbps Set the Fibre Channel switch port link speed to... 2Gbps fixed When connecting to a 1Gbps-only Fibre Channel card, the "Automatic" (default) Fibre Channel switch port link speed must be used. If the devices being connected together both have automatically set link speeds, the resulting link speed may be less than optimal. The default link speed setting for Fibre Channel switch ports is "Automatic". The link speed setting for true HP Fibre Channel cards is always "Automatic". The link speed setting of a true HP Fibre Channel card cannot be changed to other than "Automatic", so the Fibre Channel switch port link speeds must be fixed to match the actual speed of the server-side Fibre Channel cards, as per the above table, so that the same link speed is always used. Set AD355A and AD299A Fibre Channel card connected Fibre Channel switch ports to not LinkUp via the L-Port. This is because AD355A and AD299A Fibre Channel cards do not support PublicLoop LinkUp, and this setting prevents them from attempting to do so. Example: When an AD355A is connected to switch port 4 of an ETERNUS SN200 series, execute the following command to disable LinkUp via the L-Port on port 4: portcfggport 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. 14

15 Chapter 3 Notes > 3.4 HP Serviceguard Notes 3.4 HP Serviceguard Notes "HP Serviceguard" is HP-UX cluster software. For details on how to configure an HP Serviceguard system, refer to the relevant HP-UX manual. 3.5 HP Integrity VM Notes Apply the settings described in this document for a VM Host, which is an OS for operating Integrity VM. 3.6 VERITAS Volume Manager (VxVM) Notes Install VERITAS Array Support Library (ASL) after installing VxVM. Installing VxVM VxVM should be installed as specified in its accompanying documentation. VERITAS Array Support Library (ASL) If the ETERNUS Disk storage systems are connected to a configuration that uses the VxVM, the VERITAS Array Support Library (ASL) will also need to be installed. Which version of VERITAS ASL is required will depend on the storage system and version of VxVM used. Download the VERITAS ASL version that matches your environment from the following Symantec web-site. Refer to the Symantec web-site for VERITAS ASL installation details. Storage system VxVM ASL download URL ETERNUS2000 VxVM 5.0 MP1 or later ETERNUS4000 ETERNUS8000 VxVM 4.1 MP1 or later VxVM 5.0 MP1 or later VxVM or later VERITAS Cluster Server (VCS) Notes Installing VERITAS Cluster Server VERITAS Cluster Server should be installed according to the directions given in the manual provided with VERITAS Cluster Server. 15

16 Chapter 3 Notes > 3.8 Server Startup and Power Supply Control Notes 3.8 Server Startup and Power Supply Control Notes Before turning the server on, check that the ETERNUS Disk storage systems and Fibre Channel 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 Fibre Channel 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. 16

17 Chapter 4 Checking the Server Information Check the World Wide Name (WWN). When using the "Security" function (Affinity Mode) of the ETERNUS Disk storage systems, it is necessary to specify the WWN of the Fibre Channel card. Use the "fcmsutil" command to specify the device file of the Fibre Channel card, and the WWN of the Fibre Channel card can be checked. A WWN is not required if the "Host Affinity" function is not used. Procedure 1 Use the "ioscan" command to check the Fibre Channel card device files. # ioscan -func fc The format of the device file name will vary according to the Fibre Channel cards being used. In the following example, the recognized Fibre Channel card s device files are "/dev/fcd0", "/dev/fcd1", "/dev/fcd2", and "/dev/fcd3". # ioscan -func fc Class I H/W Path Driver S/W State H/W Type Description ================================================================= fc 0 0/3/1/0 fcd CLAIMED INTERFACE HP 2Gb Dual Port PCI/PCI-X Fibre Channel Adapter (Port 1) /dev/fcd0 fc 1 0/3/1/1 fcd CLAIMED INTERFACE HP 2Gb Dual Port PCI/PCI-X Fibre Channel Adapter (Port 2) /dev/fcd1 fc 2 0/4/1/0 fcd CLAIMED INTERFACE HP 2Gb Dual Port PCI/PCI-X Fibre Channel Adapter (Port 1) /dev/fcd2 fc 3 0/4/1/1 fcd CLAIMED INTERFACE HP 2Gb Dual Port PCI/PCI-X Fibre Channel Adapter (Port 2) /dev/fcd3 17

18 Chapter 4 Checking the Server Information > 2 Check the WWN of the Fibre Channel card. # fcmsutil Device_File Specify the Fibre Channel card device file names obtained in Step 1 in "Device_File". The following shows the result when this command is executed for "/dev/fcd0". The "N_Port Port World Wide Name" value is the Fibre Channel card WWN. # fcmsutil /dev/fcd0 Vendor ID is = 0x Device ID is = 0x PCI Sub-system Vendor ID is = 0x00103c PCI Sub-system ID is = 0x0012ba PCI Mode = PCI-X 133 MHz ISP Code version = ISP Chip version = 3 Topology = PRIVATE_LOOP Link Speed = 2Gb Local N_Port_id is = 0x Previous N_Port_id is = 0x Local Loop_id is = 125 N_Port Node World Wide Name = 0x50060b00001d69c9 N_Port Port World Wide Name = 0x50060b00001d69c8 Switch Port World Wide Name = N/A Switch Node World Wide Name = N/A Driver state = ONLINE Hardware Path is = 0/3/1/0 Maximum Frame Size = 2048 Driver-Firmware Dump Available = YES Driver-Firmware Dump Timestamp = Mon Aug 23 19:09: Driver Version libfcd.a HP Fibre Channel ISP 23x x Driver B /ux/kern/kisu/fcd/src/common/wsio/fcd_init.c:jan ,12: 44:56 The WWNs identified here are needed for the ETERNUSmgr "Add WWN" function. For details, refer to the "ETERNUSmgr User Guide -Settings/Maintenance-". End of procedure 18

19 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". 19

20 Chapter 6 Setting up the ETERNUS Disk Storage Systems Set up the ETERNUS Disk storage systems using ETERNUSmgr. ETERNUS Disk storage system 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 (Fibre Channel) ETERNUS Disk Storage System Settings" and "ETERNUSmgr User Guide". 20

21 Chapter 7 Setting up the Fibre Channel Switches This chapter describes the settings required to connect a server and ETERNUS Disk storage system via a Fibre Channel switch. Perform the settings according to the procedure given in "ETERNUS Disk storage systems Server Connection Guide (Fibre Channel) Fibre Channel Switch Settings". 21

22 Chapter 8 Installing Drivers and Setting up the Server 8.1 Installing the Drivers Install the necessary drivers and patches following the Fibre Channel card installation guide. 8.2 Setting up the Server The server control environment now needs to be set up. Set the command queue depth and the maximum number of volume groups for the server environment 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 Fibre Channel 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 Command queue depth on a single path 1 to or more 4 For the single path connection example shown below, 10 LUNs are recognized on the single path, so the command queue depth is set to "8". Server ETERNUS Disk Storage System FC Port FC Port 10 LUNs recognized on this path Number of LUNs: 10 Affinity Group 22

23 Chapter 8 Installing Drivers and Setting up the Server > 8.2 Setting up the Server For connection schemes in which an ETERNUS Disk storage system FC port is shared by multiple servers, the command queue depth is again determined by the number of LUNs recognized by each server on the single path. In this example, "8" is set as the command queue depth for both servers. Server A ETERNUS Disk Storage System FC Port FC Port 10 LUNs recognized on this path Number of LUNs: 10 Affinity Group A Server B FC Port 12 LUNs recognized on this path Number of LUNs: 12 Affinity Group B For multipath connection, the command queue depth is determined similarly. For the multipath connection example shown below, 20 LUNs are recognized on each path, so the command queue depth is set to "4". For all types of multipath, the command queue depth is always decided by the number of LUNs recognized on each individual path. 20 LUNs recognized on this path Server ETERNUS Disk Storage System FC Port FC Port FC Port 20 LUNs recognized on this path FC Port Number of LUNs: 20 Affinity Group Command queue depth setting procedure depends on the HP-UX version: For HP-UX11iv3 Set the command queue depth using the LU property "max_q_depth". The "max_q_depth" is set using the "scsimgr" command. - Example procedure: Setting the command queue depth of disk20 to 4 # scsimgr save_attr -D /dev/rdisk/disk20 -a max_q_depth=4 Refer to the HP-UX manuals for details of the "scsimgr" command. 23

24 Chapter 8 Installing Drivers and Setting up the Server > 8.2 Setting up the Server For HP-UX11iv1/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 For HP-UX11iv3, this setting is not required. 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. 24

25 Chapter 9 Checking Connections 9.1 Turning on the Devices To turn on the connected devices, use the following procedures: Procedure 1 Turn on the Fibre Channel switch power (if used). 2 After checking that the Ready (or equivalent) LED of the Fibre Channel 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 9.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 Enter as follows for AgileView (HP-UX11iv3 and newer format) results: # ioscan -fnn Check that all connected devices are listed in the ioscan output and "CLAIMED" is displayed in "S/W State". The following shows the output of ioscan (LegacyView) when ETERNUS Disk storage systems are directly connected to system. 25

26 Chapter 9 Checking Connections > 9.2 Logical Unit Recognition Class I H/W Path Driver S/W State H/W Type Description ============================================================================= disk 7 0/2/1/ sdisk CLAIMED DEVICE FUJITSU E4000 When the ETERNUS Disk storage systems are 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 The device file is displayed in the following format. LegacyDSF - Format /dev/(r)dsk/cxtydz X: Position of Fibre Channel card Y: Target number (0 to 15) Z: LUN (0 to 7) ETERNUS Disk storage systems' LUNs and device files correspond as follows: ETERNUS4000 Server device file LUN#0x00 cxt0d0 : : LUN#0x07 cxt0d7 LUN#0x08 cxt1d0 : : LUN#0x0F cxt1d7 LUN#0x10 cxt2d0 : : Persistent DSF - Format /dev/(r)disk/diskx X: disk instance number End of procedure 26

27 Chapter 10 Setting up the Multipath Configuration Three types of multipath configurations are available for the connection between the ETERNUS Disk storage system and an HP-UX server: "PV-Links", "Native Multipaths", and VxVM's "DMP". This chapter explains how to set up the HP-UX default "PV-Links" or "Native Multipaths". Refer to the Symantec Corp. manuals for VxVM's "DMP" details Multipath Configuration using PV-Links "PV-Links" is a Logical Volume Manager (LVM) function, 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, note the following: Confirm that the PV-Links paths have identical target IDs. For an FC-AL connection, confirm that the PV-Links paths have identical target IDs, by checking the ETERNUS Disk storage system CA port settings for each PV-Link path and comparing the target IDs. When set correctly, the device files for all paths that connect to a given ETERNUS Disk storage system LUN should all be the same after the "t" part of the name (e.g. "/dev/dsk/c4t0d0" "0d0"). Disable Native Multipaths when HP-UX11iv3 is used. For HP-UX11iv3, Native Multipaths are enabled by default. To enable PV-Links equivalent operation, the Native Multipaths must be disabled. Native Multipaths are disabled by setting the "leg_mpath_enable" parameter to "false" and using Legacy DSF for access. Native Multipaths are always enabled when using Persistent DSF access. - Reference Device special file type Legacy DSF Persistent DSF Example device special file /dev/dsk/c4t0d0 /dev/rdsk/c4t0d0 /dev/disk/disk25 /dev/rdisk/disk25 27

28 Chapter 10 Setting up the Multipath Configuration > 10.2 Multipath Configuration using Native Multipath - Example procedure: Setting "leg_mpath_enable" to "false" # scsimgr save_attr -D /dev/rdisk/diskx -a leg_mpath_enable=false Execute this "leg_mpath_enable" setting command for all LUNs in the ETERNUS Disk storage system Multipath Configuration using Native Multipath "Native Multipaths" is an OS function available for HP-UX11iv3 onwards. Native Multipaths can be used to set the I/O load balance policy (load_bal_policy). Set the I/O load balance policy to match the ETERNUS Disk storage system model. I/O load balance policy setting vs ETERNUS Disk storage system model ETERNUS Disk storage system ETERNUS2000 ETERNUS4000 models 300, 400, 500, and 600 ETERNUS8000 Example procedure I/O load balance policy setting - Setting the I/O load balance policy to "round_robin" I/O load balance policy setting preferred_path round_robin # scsimgr save_attr -D /dev/rdisk/disk25 -a load_bal_policy=round_robin Execute this "load_bal_policy" setting command for all LUNs in the ETERNUS Disk storage system. If the I/O load balance policy is "preferred_path", a priority path must be set. Set the path associated with CA port with the CM which owns the target RAID Group as the priority path. Example procedure Priority path setting - Specify the hardware path of the "Lunpath" that is to be the priority path. # scsimgr save_attr -D /dev/rdisk/disk25 -a preferred_path= 0/3/1/1.0x b5d6a0109.0x0 Lunpath hardware paths can be checked using the "ioscan -m lun" and "scsimgr lun_map" commands. The desired priority Lunpath hardware path will contain the ETERNUS Disk storage system's Fibre Channel port WWN. 28

29 Chapter 10 Setting up the Multipath Configuration > 10.2 Multipath Configuration using Native Multipath - Lunpath hardware path format HBA_hardware_path.ETERNUS_disk_storage_system_Fibre_Channel_port_WWN.LUN - Lunpath hardware path format example 0/3/1/1.0x b5d6a0109.0x WWN of Fibre Channel port in ETERNUS disk storage system 29

30 Chapter 11 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/HP-UX11iv1, 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. 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". 30

31 Chapter 11 Creating Logical Volume Manager (LVM) Logical Volumes > 11.1 Creating the Volume Group 3 Use the "pvcreate" command to create an LVM logical 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 31

32 Chapter 11 Creating Logical Volume Manager (LVM) Logical Volumes > 11.2 Creating the LVM Logical Volume 11.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. 32

33 Chapter 11 Creating Logical Volume Manager (LVM) Logical Volumes > 11.2 Creating the LVM Logical Volume 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 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 33

34 Chapter 12 SAN Boot If a logical unit (LUN) of the ETERNUS Disk storage systems is used as a boot disk, refer to "Server Support Matrix" to check the server environment. When using a LUN as a boot disk, make sure that the LUN has enough capacity to install the OS in the ETERNUS Disk storage system. 34

35 ETERNUS Disk storage systems Server Connection Guide (Fibre Channel) for HP-UX Date of issuance: Decvember 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.

36