Hp Hitachi Dynamic Link Manager Software Manuel d'utilisateur

Hitachi Dynamic Link Manager Software User's Guide (for Linux(R))3000-3-F04-60(E)

viNote that if descriptions include the term Red Hat Enterprise Linux or Red Hat Enterprise Linux AS4/ES4, and there is no specific explanation about

3. Creating an HDLM Environment76#1Only configurations that include Oracle Cluster Management Software using raw devices are supported.2.6.9-55.EL2.6.

3. Creating an HDLM Environment77For details, see 3.14 Settings for Oracle RAC.#2Only configurations that include the Automatic Storage Management (AS

3. Creating an HDLM Environment78function (raw devices used) and Oracle Clusterware• Configurations that include the Automatic Storage Management (ASM

3. Creating an HDLM Environment79Table 3-11: Cluster Software When Using Red Hat Enterprise Linux ES4 (IA32)Usable kernels Cluster software2.6.9-11.EL

3. Creating an HDLM Environment802.6.9-42.EL2.6.9-42.ELsmp2.6.9-42.ELhugememLifeKeeper v6LifeKeeper v6 Update1LifeKeeper v6 Update2LifeKeeper v6 Updat

3. Creating an HDLM Environment81#1Only configurations that include the Automatic Storage Management (ASM) function (the ASMLib kernel driver (ASMLib)

3. Creating an HDLM Environment82#3The following configurations are supported:• Configurations that include the Automatic Storage Management (ASM) fun

3. Creating an HDLM Environment83function (raw devices used) and Cluster Ready Service (CRS)For details, see 3.14 Settings for Oracle RAC.#8Only confi

3. Creating an HDLM Environment84For details, see 3.14 Settings for Oracle RAC.#2The following configurations are supported:• Configurations that incl

3. Creating an HDLM Environment852.6.9-34.EL2.6.9-34.ELsmp2.6.9-34.ELlargesmpLifeKeeper v6LifeKeeper v6 Update1LifeKeeper v6 Update2LifeKeeper v6 Upda

viiCLPR Cache Logical PartitionCPU Central Processing UnitCU Control UnitDBMS Database Management SystemDev DeviceDMI Desktop Management InterfaceDNS

3. Creating an HDLM Environment862.6.9-42.EL2.6.9-42.ELsmp2.6.9-42.ELlargesmpLifeKeeper v6LifeKeeper v6 Update1LifeKeeper v6 Update2LifeKeeper v6 Upda

3. Creating an HDLM Environment87#1The following configurations are supported:• Configurations that include raw devices and Cluster Ready Service (CRS

3. Creating an HDLM Environment88For details, see 3.14 Settings for Oracle RAC.#2The following configurations are supported:• Configurations that incl

3. Creating an HDLM Environment89#6Only configurations that include the Automatic Storage Management (ASM) function (using raw devices) and Oracle Clu

3. Creating an HDLM Environment902.6.9-100.EL2.6.9-100.ELsmp2.6.9-100.ELhugememLVM2.02.42-9.el4IPF 2.6.9-11.EL LVM2.01.08-1.0.RHEL42.6.9-34.EL LVM2.02

3. Creating an HDLM Environment91(3) File Systems Supported by HDLMWhen using a file system, the related programs are as follows:• ext2 (supplied with

3. Creating an HDLM Environment92Table 3-15: Operating Environments for BladeSymphony When Using Red Hat Enterprise Linux AS4/ES4#1The XP series is no

3. Creating an HDLM Environment93Table 3-16: Operating Environments for Boot Disks When Using Red Hat Enterprise Linux AS4/ES4(IA32)Kernel HBA Support

3. Creating an HDLM Environment94Table 3-17: Operating Environments for Boot Disks When Using Red Hat Enterprise Linux AS4/ES4 (IPF)Table 3-18: Operat

3. Creating an HDLM Environment95Table 3-19: Operating Environments for BladeSymphony and Boot Disks When Using Red Hat Enterprise Linux AS4/ES4 lists

viiiIPF Itanium(R) Processor FamilyIRQ Interrupt ReQuestiSCSI Internet Small Computer System InterfaceKVM Kernel-based Virtual MachineLAN Local Area N

3. Creating an HDLM Environment96Notes on using HDLM in a BladeSymphony environmentWhen HDLM is used in a BladeSymphony environment, the following fun

3. Creating an HDLM Environment97Table 3-20: Cluster Software Used with Red Hat Enterprise Linux 5 (IA32)Usable kernels Cluster software2.6.18-8.el52.

3. Creating an HDLM Environment98#1The following configurations are supported:• Configurations that include the Oracle Cluster File System 2 and Clust

3. Creating an HDLM Environment99Clusterware• Configurations that include the Oracle Cluster File System 2 and Oracle ClusterwareFor details, see 3.14

3. Creating an HDLM Environment100Table 3-22: Cluster Software Used with Red Hat Enterprise Linux 5 (EM64T/AMD64)Usable kernels Cluster software2.6.18

3. Creating an HDLM Environment1012.6.18-92.el5 LifeKeeper v6 Update3LifeKeeper v6 Update4LifeKeeper v7LifeKeeper v7 Update1LifeKeeper v7 Update2LifeK

3. Creating an HDLM Environment102#1Only configurations that include the Automatic Storage Management (ASM) function (raw devices used) and Cluster Re

3. Creating an HDLM Environment103• Configurations that include raw devices and Oracle Clusterware• Configurations that include the Automatic Storage

3. Creating an HDLM Environment104(3) File Systems Supported by HDLMTable 3-24: Supported File Systems When Using Red Hat Enterprise Linux 5 lists and

3. Creating an HDLM Environment105Table 3-24: Supported File Systems When Using Red Hat Enterprise Linux 5#Kernel architecture Kernel File systemIA32

ixConventions: DiagramsThis manual uses the following conventions in diagrams:Conventions: Fonts and SymbolsFont and symbol conventions are classified

3. Creating an HDLM Environment106An HDLM device on a GFS2 file system cannot be used as a boot disk.(4) Boot Disk Environments and BladeSymphony Envi

3. Creating an HDLM Environment107Table 3-26: Operating Environments for Boot Disks When Using Red Hat Enterprise Linux 5Kernel architecture Kernel HB

3. Creating an HDLM Environment108#LUKS is not available in an environment where an HDLM device is used as a boot disk.Table 3-27: Operating Environme

3. Creating an HDLM Environment109• HotPlug• SystemManager linkageNote that HDLM cannot use the functions provided by ServerConductor/DeploymentManage

3. Creating an HDLM Environment110Table 3-29: Supported File Systems When Using Red Hat Enterprise Linux 6#An HDLM device on a GFS2 file system cannot

3. Creating an HDLM Environment111 # /opt/DynamicLinkManager/bin/dlnkmgr view -sys Always use Heartbeat (1.2.5-0.3) in order to create a cluster confi

3. Creating an HDLM Environment112HDLM on all the nodes that comprise the cluster. If different versions of HDLM are installed, the cluster system may

3. Creating an HDLM Environment113#1Only configurations that include the Automatic Storage Management (ASM) function (using raw devices) and Cluster R

3. Creating an HDLM Environment114Notes on using a volume managerNote the following when using a volume manager:2.6.16.46-0.14-default2.6.16.46-0.14-s

3. Creating an HDLM Environment115• Although disk partitioning and system backup functions are supported for disks in a YaST2 system, the combination

xCode examples and messages appear as follows (though there may be some exceptions, such as when the code is part of a diagram):MakeDatabase...StoreDa

3. Creating an HDLM Environment116Table 3-33: Operating Environments for BladeSymphony When Using SUSE LINUX Enterprise Server 10#1The XP series is no

3. Creating an HDLM Environment117Table 3-35: Operating Environments for BladeSymphony and Boot Disks When Using SUSE LINUX Enterprise Server 10 lists

3. Creating an HDLM Environment118Note that HDLM cannot use the functions provided by ServerConductor/DeploymentManager other than the following:• Bac

3. Creating an HDLM Environment119IOCTL when installing HDLM because HDLM devices are not SCSI devices. HDLM rejects the IOCTL request and assumes tha

3. Creating an HDLM Environment120Table 3-37: Operating Environments for Boot Disks When Using SUSE LINUX Enterprise Server 113.1.9 Related Products W

3. Creating an HDLM Environment121(2) File Systems Supported by HDLMWhen using a file system, the related programs are as follows:• ext2 (supplied wit

3. Creating an HDLM Environment122 # /opt/DynamicLinkManager/bin/dlnkmgr view -sys Table 3-40: Cluster Software When Using Oracle Enterprise Linux 5 l

3. Creating an HDLM Environment123(3) File Systems Supported by HDLMTable 3-42: Supported File Systems When Using Oracle Enterprise Linux 5 lists and

3. Creating an HDLM Environment124Table 3-43: Operating Environments for Boot Disks When Using Oracle Enterprise Linux 53.1.11 Memory and Disk Capacit

3. Creating an HDLM Environment125#1This size differs depending on the settings for log files (maximum size: 30 GB).p is obtained by the following for

xiConventions: KB, MB, GB, and TBThis manual uses the following conventions:• 1 KB (kilobyte) is 1,024 bytes.• 1 MB (megabyte) is 1,0242 bytes.• 1 GB

3. Creating an HDLM Environment126Agent Component.The size of each log file (dlmwebagent[1-N].log) is 9900 KB (approximately 10 MB). The size of the l

3. Creating an HDLM Environment1273.1.12 Number of Paths Supported in HDLMTable 3-46: Number of LUs and Paths Supported in HDLM lists the number of LU

3. Creating an HDLM Environment128Table 3-47: Xen Hypervisor Operating Environments Supported by HDLM shows the Xen hypervisor operating environments

3. Creating an HDLM Environment1293.2 Flow for Creating an HDLM EnvironmentSet up the environment to use HDLM as shown in the following diagram.If you

3. Creating an HDLM Environment130Figure 3-1: Flow of HDLM Environment Setup

3. Creating an HDLM Environment1313.3 HDLM Installation TypesThis subsection describes the following types of HDLM installation: new installation, upg

3. Creating an HDLM Environment1323.4 Knowledge Required Before You Install HDLM You can install HDLM on the following disks or devices:• An internal

3. Creating an HDLM Environment1333.5 Notes on Creating an HDLM EnvironmentThis section provides notes on creating an HDLM environment.For notes on op

3. Creating an HDLM Environment134However, you can avoid the above situations by setting a permanent target ID for each LU with the HBA driver persist

3. Creating an HDLM Environment135 # grep DLM /etc/rc.d/rc.sysinit# grep DLM /etc/init.d/halt If nothing is output after command execution, HDLM infor

3. Creating an HDLM Environment136configuration, memory might become insufficient due to the HAL daemon#. In this case, the host will not respond.To a

3. Creating an HDLM Environment137# /sbin/dlmcfgmgr -i 5. Start the HAL daemon.Execute the /sbin/service command to start the HAL daemon. # /sbin/serv

3. Creating an HDLM Environment138

3. Creating an HDLM Environment1393.6 Installing HDLMThe following section describes how to install HDLM for a new installation, for a re-installatio

3. Creating an HDLM Environment140First, check the current settings. Execute the following command: # mount The current settings will be output as sho

3. Creating an HDLM Environment141(2) Checking the Volume GroupIf you have already created a physical volume, volume group, or logical volume by using

3. Creating an HDLM Environment142Figure 3-4: Result of Executing vgdisplay -v (When There Is One Physical Vo l u m e )Check the shaded portion and co

3. Creating an HDLM Environment143Figure 3-5: Result of Executing vgdisplay -v (When There Are Two Physical Vo lu m e s) Check the shaded portion and

3. Creating an HDLM Environment144Figure 3-6: Example of the Contents of the syslogd Settings File (In Red Hat Enterprise Linux)When you collect audit

3. Creating an HDLM Environment1451. Log on to Linux as the root user.2. Prepare the license key.Use either of the following methods to store the lice

xiiiContentsPreface iIntended Readers ...iOrganiz

3. Creating an HDLM Environment146Note 1HDLM cannot be installed if the DVD-ROM is mounted to a mount point other than the above.Note 2To copy the DVD

3. Creating an HDLM Environment147• When executing installux.sh # /media/cdrom/installux.sh -v • When executing the installhdlm utility # /media/cdrom

3. Creating an HDLM Environment148# rpm -qi HDLMName : HDLMVersion : x.x.x.x.xxxRelease : xx : If HDLM Version is x.x.x.x.xxx, th

3. Creating an HDLM Environment149 A path will be established in the HDLM device and the HDLM manager will start.14. If you have edited the /etc/fstab

3. Creating an HDLM Environment150For details on operating environments for the virtual environments supported by HDLM, see 3.1.13 Virtual Environment

3. Creating an HDLM Environment15121. Check that the correct version of HDLM is installed.If HDLM version x.x.x-xx is displayed, the installed HDLM ve

3. Creating an HDLM Environment1522. Execute the following command to make sure that the md devices have been deactivated. In the following example, R

3. Creating an HDLM Environment1532. Prepare the license key.Store the license key file (*.plk) in the /var/tmp directory, under the name hdlm_license

3. Creating an HDLM Environment154Table 3-50: Mount Point for Each DistributionNote 1HDLM cannot be installed if the DVD-ROM is mounted to a mount poi

3. Creating an HDLM Environment155#4. Check the version of HDLM.Execute installux.sh or the HDLM installation utility (installhdlm) stored on the HDLM

xiv2.11.3 Collecting Error Information Using the Utility for Collecting HDLM Error Information (DLMgetras)...

3. Creating an HDLM Environment1566. The KAPL09093-I message is displayed to confirm that you want to perform an upgrade installation. Check the HDLM

3. Creating an HDLM Environment15712. Restart the host.Execute the following command to restart the host: # shutdown -r now A path will be established

3. Creating an HDLM Environment158Personalities : [raid1]md0 : active raid1 sddlmaa1[0] sddlmab1[1] 5238528 blocks [2/2] [UU] unused devices: <

3. Creating an HDLM Environment159HDLM, see 3.1.13 Virtual Environments Supported by HDLM. For details on how to set up a virtual environment, see 3.1

3. Creating an HDLM Environment160The following shows an example of command execution when the mount point is /media/cdrom: # mount /dev/cdrom /media/

3. Creating an HDLM Environment161This refers to the volume name for the CD-ROM or other media, formatted for ISO-9660 file systems. Use the volname c

3. Creating an HDLM Environment162# /media/cdrom/installux.sh • When executing the installhdlm utility # /media/cdrom/HDLM_Linux/installhdlm 6. The KA

3. Creating an HDLM Environment163settings file for the root user. This makes executing the HDLM commands and HDLM utilities easier.When the BourneAga

3. Creating an HDLM Environment164For details on setting up LUKS, see 3.8 Settings for LUKS.16. If md devices are used, execute the following command

3. Creating an HDLM Environment16520. Mount the logical volume that was moved.In the following example, the logical volume is /dev/vg01/lvol1 and the

xv3.7.1 Notes on Installing HDLM in a Boot Disk Environment...1723.7.2 Overview of the Procedure for Installing HDLM in a B

3. Creating an HDLM Environment166installation.For an unattended installation, you can specify any directory to store the license key file. For detail

3. Creating an HDLM Environment167Note 2To copy the DVD-ROM to a directory, and then install HDLM from that directory, copy the DVD-ROM to a directory

3. Creating an HDLM Environment168Edit the installation information settings file based on your desired settings. Specify any settings that are not sp

3. Creating an HDLM Environment169Name : HDLMVersion : x.x.x.x.xxxRelease : xx : If HDLM Version is x.x.x.x.xxx, the installed ve

3. Creating an HDLM Environment170Add the shaded line shown in the above figure.11. Specify the settings required for using LUKS.Perform this step if

3. Creating an HDLM Environment17116. Specify the settings required for using virtual environments.If you are using Xen, set up Xen to use HDLM device

3. Creating an HDLM Environment1723.7 Installing HDLM for Managing Boot DisksThis section explains the procedure for installing HDLM in an environment

3. Creating an HDLM Environment1731. Check the installation directory of the OS specified in the LABEL setting.# cat /etc/fstabLABEL=/ / ext3

3. Creating an HDLM Environment174In an environment where HDLM has been installed, you can use the dlmcfgmgr utility to check the correspondence betwe

3. Creating an HDLM Environment175in a single-path boot disk environment that uses a SCSI device.3.7.2 Overview of the Procedure for Installing HDLM i

 Relevant program products Hitachi Dynamic Link Manager version 6.6.2For details about applicable OSs, see the Release Notes. TrademarksAIX

xvi3.20.2 When Using Red Hat Enterprise Linux AS4/ES4 or SUSE LINUX Enterprise Server ...

3. Creating an HDLM Environment176After completing the above procedure, you can perform an upgrade installation of HDLM in a boot disk environment tha

3. Creating an HDLM Environment1773. Change the definition such that the HDLM device can be used as a boot disk.Restore the configuration file to its

3. Creating an HDLM Environment178 :image = vmlinuz-2.6.16.60-0.54.5-default label = 51 append = "splash=silent multipath=of

3. Creating an HDLM Environment179 root (hd0,0) kernel /vmlinuz-2.6.16.60-0.54.5-smp root=/dev/VG/root vga=0x31a \ resume=/dev/VG/swap spla

3. Creating an HDLM Environment180 : :title Red Hat Enterprise Linux (2.6.18-194.el5) root (hd0,0) kernel /vmlinuz-2.6.18-194.el5

3. Creating an HDLM Environment181 : :title XEN root (hd0,1) kernel /boot/xen.gz module /boot/vmlinuz-2.6.16.60-0.21-xen root=

3. Creating an HDLM Environment182# udevadm info --query name -n /dev/disk/by-uuid/55574d05-07dc-4c94-a585-5599c284d79bsda2 The sda2 value output is t

3. Creating an HDLM Environment183contained in the boot loader configuration file.The following shows an example configuration. Note that option in th

3. Creating an HDLM Environment184 append="option root=LABEL=/ option"12. Change the name of the configuration contained in the boot lo

3. Creating an HDLM Environment185Change the default number so that a boot can be performed using the configuration copied in step 11.default=2• When

xvii4.3.5 Displaying Corresponding Information About an HDLM Device, SCSI Device, and LDEV...

3. Creating an HDLM Environment186Root directory (/), /boot/efi, /tmp, /usr, /var, swap• When GRUB is used as the boot loader:Root directory (/), /boo

3. Creating an HDLM Environment187Change the underlined text as follows:Before:label=linux-sdAfter:label=linux-HDLM25. Delete the root specification c

3. Creating an HDLM Environment18829. If LILO is used as the boot loader, execute the /sbin/lilo command to have the new settings take effect.30. Shut

3. Creating an HDLM Environment189The name of the boot loader configuration file used in these procedures differs depending on the boot loader and OS.

3. Creating an HDLM Environment190parameter specified to check the correspondence between the HDLM device and the SCSI device. # dlmcfgmgr -vHDevName

3. Creating an HDLM Environment191 root (hd0,1) kernel /boot/xen.gz module /boot/vmlinuz-2.6.16.60-0.21-xen vga=0x31a splash=silent showopts

3. Creating an HDLM Environment192After:title sd-Red Hat Enterprise Linux (2.6.18-194.el5)• When LILO or ELILO is used as the boot loader:Change the u

3. Creating an HDLM Environment193• When GRUB is the boot loaderChange the default number so that a boot can be performed using the configuration copi

3. Creating an HDLM Environment19416. Perform an upgrade installation of HDLM.To perform an upgrade installation of HDLM, see 3.6.5 Performing an Upgr

3. Creating an HDLM Environment195title HDLM-Red Hat Enterprise Linux (2.6.18-194.el5)• When LILO or ELILO is used as the boot loader:Change the under

xviii6.3.1 Format... 4026.3.2 Parameter ...

3. Creating an HDLM Environment196• When GRUB is used as the boot loader:Root directory (/), /boot, /tmp, /usr, /var, swap• When LILO is used as the b

3. Creating an HDLM Environment197/dev/sddlmaa6 on /usr type ext2 (rw)none on /dev/shm type tmpfs (rw) Check the underlined section.30. If Red Hat Ent

3. Creating an HDLM Environment198 append = "splash=silent multipath=off" description = Linux initrd = initrd-2.6.16.60

3. Creating an HDLM Environment199multipath=off initrd /initrd-2.6.16.60-0.54.5-smpmultipath=off is set in the underlined section.3. Check whether

3. Creating an HDLM Environment200Figure 3-9: Example of Executing the mount CommandThe shaded portion indicates the SCSI device for which LABEL is se

3. Creating an HDLM Environment201 # udevadm info --query name -n /dev/disk/by-uuid/55574d05-07dc-4c94-a585-5599c284d79bsda1 The sda1 value output is

3. Creating an HDLM Environment202that uses ELILO as the boot loader, the mount point is displayed as /boot/efi instead of /boot (in the line where /b

3. Creating an HDLM Environment203Figure 3-11: Example of Editing /etc/lvm/lvm.conf fileComment out the existing filter and types lines, and add the s

3. Creating an HDLM Environment204KAPL12329-I The utility for supporting the boot disk started.KAPL12344-I A compressed initial ramdisk image /boot/in

3. Creating an HDLM Environment205/dev/sddlmaa1 /boot ext3 defaults 1 2 :

xix7.10.3 Editing an Installation-Information Settings File...5147.11 installux.sh Utility for HDLM Common Instal

3. Creating an HDLM Environment206Figure 3-13: Example of Editing /boot/grub/menu.lst file (When using a kernel that supports Xen)Edit the shaded port

3. Creating an HDLM Environment20719. Assign a name to the copied configuration that indicates that the configuration is used for specifying the HDLM

3. Creating an HDLM Environment208# vgscan Reading all physical volumes. This may take a while... Found volume group "VolGroup00" using m

3. Creating an HDLM Environment2093.7.6 Upgrade Installation in an Environment Where a Logical Volume (LVM2) on an HDLM Device Is Used as a Boot DiskT

3. Creating an HDLM Environment210device. Note that if settings are incorrect, the OS might not start.In this subsection, the procedure assumes that y

3. Creating an HDLM Environment211/dev/sda1 /boot ext3 defaults 1 2 :

3. Creating an HDLM Environment2127. Edit the /etc/lvm/lvm.conf file so that the LVM2 recognizes the SCSI device, not the HDLM device.Figure 3-15: Exa

3. Creating an HDLM Environment213Figure 3-15: Example of Editing /etc/lvm/lvm.conf fileComment out the existing filter and types lines, and add the s

3. Creating an HDLM Environment214Figure 3-16: Example of Editing /etc/grub.conf fileEdit the shaded portion.Figure 3-17: Example of Editing /boot/gru

3. Creating an HDLM Environment215Figure 3-18: Example of Editing /etc/elilo.conf fileEdit the shaded portion.9. Copy the configuration that was used

xxC.3 Functional Differences Between Version 6.0 or Later and Versions Earlier Than 6.0...

3. Creating an HDLM Environment21613. Specify the configuration that will be used for booting.• When GRUB is the boot loaderSpecify the position of th

3. Creating an HDLM Environment21720. Perform an upgrade installation of HDLM.To perform an upgrade installation of HDLM, see 3.6.5 Performing an Upgr

3. Creating an HDLM Environment218procedure differs depending on whether the host is restarted after installation.21. Execute the dlmcfgmgr utility wi

3. Creating an HDLM Environment219for uninstallation or upgrade installation of HDLM.23. Execute the dlmmkinitrd utility for supporting a boot disk to

3. Creating an HDLM Environment220initrd-2.6.16.46-0.14-default.hdlm was created.KAPL12330-I The utility for supporting the boot disk completed. 24. W

3. Creating an HDLM Environment221Server 11, check the /boot/grub/menu.lst file instead of the /etc/grub.conf file.The detailed procedure is explained

3. Creating an HDLM Environment222Figure 3-21: Example of Editing /boot/grub/menu.lst file (When using a kernel that supports Xen)Edit the shaded port

3. Creating an HDLM Environment223Figure 3-22: Example of Editing /etc/elilo.conf fileEdit the shaded portion.27. Copy the configuration that was used

3. Creating an HDLM Environment22430. In initrd, specify the initial RAM disk image file you created in step 23.If you are using a kernel that support

3. Creating an HDLM Environment225 Found volume group "VolGroup00" using metadata type lvm2 37. Check the relationship between the volume g

1Chapter1. Overview of HDLMHDLM is a software package that manages paths between a host and a storage system. HDLM is designed to distribute loads acr

3. Creating an HDLM Environment2263.7.7 Countermeasures for Unsuccessful Startup of the OS from an HDLM DeviceThis subsection explains what actions yo

3. Creating an HDLM Environment227An error message appears and the OS stops. A prompt for a password for starting maintenance appears, and the OS st

3. Creating an HDLM Environment228etc/elilo.conf file, or /boot/grub/menu.lst file to make sure that the initial RAM disk image file and ramdisk_size

3. Creating an HDLM Environment2293.8 Settings for LUKSThis section explains the procedures that the user must perform when using LUKS.3.8.1 Notes on

3. Creating an HDLM Environment230# dlmcfgmgr -vHDevName Management Device Host Channel Target Lun/dev/sddlmaa configured /dev/sdh 1

3. Creating an HDLM Environment231Before:luks-volume1 UUID="050f9901-3ab8-4556-a091-9c6e4a404f09" /etc/cryptpassword1After:luks-volume1 /dev

3. Creating an HDLM Environment2323.9 Settings for md DevicesThis section explains the procedures that the user must perform when using md devices.3.9

3. Creating an HDLM Environment233Figure 3-23: Example of Incorrectly Configured md DevicesIf you want to manage md devices by using HDLM, migrate the

3. Creating an HDLM Environment234During this procedure, /dev/md0 is created on /dev/sddlmaa1 and /dev/sddlmab1. Use the following procedure to config

3. Creating an HDLM Environment235Selected partition 1Hex code (type L to list codes): 83 Command (m for help): p Disk /dev/sddlmaa: 5368 MB, 53687091

1. Overview of HDLM21.1 What is HDLM?With the widespread use of data warehousing and increasing use of multimedia data, the need for high-speed proces

3. Creating an HDLM Environment236If the configuration file /etc/mdadm.conf has already been created, execute the following command to create a backup

3. Creating an HDLM Environment237Make sure that md0 : active and the HDLM devices are displayed.3.9.3 Using HDLM in an md Device EnvironmentThis subs

3. Creating an HDLM Environment2382. If necessary, back up the application data residing on the md device.3. If file systems have been mounted on the

3. Creating an HDLM Environment239 For details about the contents of the configuration file, see the Linux documentation or use the man command.If you

3. Creating an HDLM Environment240 # mdadm -Ss /dev/md0 11. Make sure that the md device has been deactivated.In the following example, RAID1 (mirrori

3. Creating an HDLM Environment241The following example shows how to execute the fdisk command to change the disk partition type to 83: # fdisk /dev/s

3. Creating an HDLM Environment242 5238528 blocks [2/2] [UU]unused devices: <none> Make sure that md0 : active and the HDLM devices are dis

3. Creating an HDLM Environment2431. Stop all applications that are using the existing md device.2. If necessary, back up the application data residin

3. Creating an HDLM Environment244 size=5238528K mtime=Wed Feb 6 19:17:08 2008mdadm: /dev/sddlmaa1 appears to be part of a raid array: level=-

3. Creating an HDLM Environment245ARRAY /dev/md0 level=linear num-devices=1 UUID=426a9f1c:9cfa6310:6aa9a80b:11ea2102 auto=yes 11. On the DEVICE line o

1. Overview of HDLM3• Lightning 9900V series• Thunder 9500V series• Universal Storage Platform V/VM• Virtual Storage Platform

3. Creating an HDLM Environment2463.10 Settings for LVM2This section describes the procedure for setting the following items in an LVM2 environment:•

3. Creating an HDLM Environment247logical volume. Use the following procedure to configure the environment shown in Figure 3-28: Device configuration

3. Creating an HDLM Environment248Example of executing the parted command (IA32, IPF or EM64T/AMD64):

3. Creating an HDLM Environment249When you use the parted command to change the partition, to let the system recognize the partitions on the HDLM devi

3. Creating an HDLM Environment250• Adding types entry informationAdd the following line:types = [ "sddlmfdrv", 16 ]Make sure that types=[ &

3. Creating an HDLM Environment251Figure 3-29: Example of Editing the /etc/lvm/lvm.conf File4. Create the physical volumes.The following example shows

3. Creating an HDLM Environment252 Physical volume "/dev/sddlmad2" successfully created5. Create a volume group.In the following example, t

3. Creating an HDLM Environment253# mkdir /mnt/lvol1 9. Mount the logical volume.The following example shows how to mount the logical volume to the /m

3. Creating an HDLM Environment254In Figure 3-30: Device Configuration When a Logical Volume on a SCSI Device Is Moved to an HDLM Device, sdn indicate

3. Creating an HDLM Environment2557. Edit the /etc/lvm/lvm.conf file.Edit the device section in the file as shown below to disable the SCSI device con

1. Overview of HDLM41.2 HDLM FeaturesHDLM features include the following:The ability to distribute a load across multiple paths. This is also known as

3. Creating an HDLM Environment256Figure 3-31: Example of Editing the /etc/lvm/lvm.conf File8. Execute the VG scan.To re-create the volume group on th

3. Creating an HDLM Environment2579. Import the volume group.In the following example, the command imports the vg01 volume group: # vgimport vg01 Vol

3. Creating an HDLM Environment2583.11 Settings for XenWhen HDLM is installed in an environment that uses Xen, the SCSI devices corresponding to HDLM

3. Creating an HDLM Environment259 (dev sdx) (uname phy:/dev/sda) (mode w) ) ) : :If the SCSI dev

3. Creating an HDLM Environment2603.12 Settings for KVMIf you install HDLM in an environment in which KVM is used, you need to register HDLM devices i

3. Creating an HDLM Environment261After:<source dev='/dev/sddlmad'/> For details on which SCSI devices correspond to which HDLM device

3. Creating an HDLM Environment2623.13 Settings for HeartbeatThis section describes the procedure that the user must perform when HDLM is installed in

3. Creating an HDLM Environment2633.14 Settings for Oracle RACThe following are notes on using Oracle RAC: When you use Oracle Cluster file System in

3. Creating an HDLM Environment264Table 3-55: Formula for Calculating MISSCOUNT• When using Oracle RAC 10g 10.2.0.2.0 or later or Oracle RAC 11g:In ad

3. Creating an HDLM Environment265If the Oracle command oracleasm is executed for HDLM devices, the KAPL05023-E message might be output to syslog.If

5Chapter2. HDLM FunctionsThis chapter describes the various functions that are built into HDLM. Before the function specifications are explained thoug

3. Creating an HDLM Environment2663.15 Settings for the RHCMThe user must execute the following procedure when HDLM is installed in an environment tha

3. Creating an HDLM Environment2673.15.3 When Using Red Hat Enterprise Linux 5, or Red Hat Enterprise Linux 6To specify settings for RHCM:1. Stop the

3. Creating an HDLM Environment2683.16 Settings for VCSThe following is the procedure that must be executed by the user when HDLM is installed in an e

3. Creating an HDLM Environment2693.17 Checking the Path ConfigurationHDLM functions, such as load balancing and failover, are only available for HDLM

3. Creating an HDLM Environment270see whether the HDLM device corresponding to the SCSI device has been created.

3. Creating an HDLM Environment2713.18 Setting Up HDLMHDLM includes functions like the load balancing function, the automatic failback function, the e

3. Creating an HDLM Environment272Table 3-57: The Recommended and Default Values of Each Function(1) Setting Up Load BalancingYou can select whether t

3. Creating an HDLM Environment273• rr for the Round Robin algorithm•exrr for the Extended Round Robin algorithm•lio for the Least I/Os algorithm•exli

3. Creating an HDLM Environment274If you set the number of times that the error needs to occur to 1, the above condition does not need to be satisfied

3. Creating an HDLM Environment275monitoring, specify off. When you specify on, you can use the -intvl and -iemnum parameters to specify intermittent

Summary of AmendmentsThe following table lists changes in this manual (3000-3-F04-60(E)) and product changes related to this manual.In addition to the

2. HDLM Functions62.1 Devices Managed by HDLMBelow is a list of devices that can or cannot be managed by HDLM. The devices that can be managed by HDLM

3. Creating an HDLM Environment276from 1 to 64).Table 3-59: Values for the Trace Level Setting lists and describes the possible values for the trace l

3. Creating an HDLM Environment277# /opt/DynamicLinkManager/bin/dlnkmgr set -elfs 1000 Specify the size of the error log file in KB.(8) Setting the Nu

3. Creating an HDLM Environment278message will be displayed to confirm the execution, and the trace file will be temporarily deleted.By specifying bot

3. Creating an HDLM Environment279This example shows how to enable the collection of audit log data: # /opt/DynamicLinkManager/bin/dlnkmgr set -audlog

3. Creating an HDLM Environment280This example shows how to specify the audit log facility: # /opt/DynamicLinkManager/bin/dlnkmgr set -audfac local0 3

3. Creating an HDLM Environment2813.19 The Process-specific-trace Information FileWhen HDLM is used, the dlnkmgr command logs are output to the follow

3. Creating an HDLM Environment2823.20 Creating a Character-Type Device File for an HDLM DeviceThis section describes how to create a character-type d

3. Creating an HDLM Environment283Figure 3-32: Executing the raw CommandIn this example, the command creates /dev/raw/raw1 as a character-type device

3. Creating an HDLM Environment2843.21 Creating File Systems for HDLM (When Volume Management Software Is Not Used)This section describes how to build

3. Creating an HDLM Environment285Figure 3-33: Example of Creating an ext2 File System

2. HDLM Functions72.2 System ConfigurationHDLM manages routes between a host and a storage system by using the SCSI driver. A host and a storage syste

3. Creating an HDLM Environment2863.22 Settings for Automatic MountingIf you specify the name of a logical device file of an HDLM device at host start

3. Creating an HDLM Environment287In the example, the name of the logical device file of the HDLM device that corresponds to /dev/sda can be identifie

3. Creating an HDLM Environment288Figure 3-35: Example of Executing the dlnkmgr Command's View Operation (With -drv Specified) In the example, th

3. Creating an HDLM Environment289option.3. Restart the host or manually mount the HDLM device. The HDLM-managed device is mounted using the logical d

3. Creating an HDLM Environment2903.23 Canceling the Settings for HDLMReturn the HDLM environment to the way it was before HDLM was installed by follo

3. Creating an HDLM Environment291If an HDLM-managed device is registered in an application (including cluster software, but excluding volume manageme

3. Creating an HDLM Environment292Migrate to the SCSI devices from an environment where HDLM devices use LUKS.For details on how to cancel the LUKS se

3. Creating an HDLM Environment293company with which you have a support service contract for Oracle.• When using release 10.2.0.2.0 or later of Oracle

3. Creating an HDLM Environment294# service ccsd start# service cman start# service rgmanager start (2) When Using Red Hat Enterprise Linux 5 or When

3. Creating an HDLM Environment295 # service cman start# service rgmanager start 3.23.5 Canceling the Settings for VCSThis section describes how to ca

2. HDLM Functions8Figure 2-1: Configuration of an HDLM System When Using an FC-SANTable 2-1: HDLM System Components When Using an FC-SAN lists the HDL

3. Creating an HDLM Environment296In the following example, the domU configuration information is checked from the management domain:# /usr/sbin/xm li

3. Creating an HDLM Environment297If you have temporarily changed the settings so that domainU does not automatically start in step 3, restore the pre

3. Creating an HDLM Environment298For details on which HDLM device correspond to which SCSI device, see 4.3.5 Displaying Corresponding Information Abo

3. Creating an HDLM Environment299Figure 3-37: Device Configuration When a Logical Volume on an HDLM Device Is Moved to a SCSI DeviceIn Figure 3-37: D

3. Creating an HDLM Environment300 # vgchange -an vg010 logical volume(s) in volume group "vg01" now active4. Export the volume group.In the

3. Creating an HDLM Environment301enabled. Figure 3-38: Example of Editing the /etc/lvm/lvm.conf File shows an example of editing the file by adding a

3. Creating an HDLM Environment302To re-create the volume group on the HDLM device, execute the vgscan command as shown in the following example: # vg

3. Creating an HDLM Environment303When md devices have been constructed by using SCSI devices, if you do not use the MULTIPATH function for the md dev

3. Creating an HDLM Environment3044. If necessary, back up the application data residing on the md device.5. If file systems have been mounted on the

3. Creating an HDLM Environment305checked in step 9, change the HDLM device names on the DEVICE line to the SCSI device names.Before the correction:DE

2. HDLM Functions92.2.2 System Configuration Using an IP-SANIn an IP-SAN, LAN cables are used to connect hosts to storage systems. The cable port on t

3. Creating an HDLM Environment306 Calling ioctl() to re-read partition table.Syncing disks. Also perform the above operation for /dev/sddlmab.12. Exe

3. Creating an HDLM Environment307Figure 3-40: Device Configuration When an md Device on an HDLM Device Is Moved to a SCSI Device (An Environment that

3. Creating an HDLM Environment308# cat /proc/mdstatPersonalities : [linear]unused devices: <none> Make sure that md0 : active is not displayed.

3. Creating an HDLM Environment309# mdadm --detail --scan | grep -w "/dev/md0" >> /etc/mdadm.conf The following example shows the cont

3. Creating an HDLM Environment310DEVICE /dev/sddlmaa1After the correction:DEVICE /dev/sdh1 /dev/sdo1Specify all SCSI devices that correspond to HDLM

3. Creating an HDLM Environment311parameter specified to check the correspondence between the SCSI device and the HDLM device.The following shows an e

3. Creating an HDLM Environment312• If you uninstall HDLM, the error logs (/var/tmp/hdlminstlog/installhdlm[01-10].log) generated during installation

3. Creating an HDLM Environment313sddlmfdrv 254092 0 If a value other than 0 is displayed for Used, perform the operation described in 3

3. Creating an HDLM Environment3142. Make sure that the HDLM device is defined in the /etc/fstab file.Make sure that the mount points for the followin

3. Creating an HDLM Environment315Figure 3-41: Example of Executing the dlmcfgmgr Utility with the -v Parameter SpecifiedFigure 3-42: Example of Execu

2. HDLM Functions10Figure 2-2: Configuration of an HDLM System When Using an IP-SANTable 2-2: HDLM System Components When Using an IP-SAN lists the HD

3. Creating an HDLM Environment316to step 7.5. Execute the following commands to check the device name:• For Red Hat Enterprise Linux 6Execute the ude

3. Creating an HDLM Environment317pci-0000:20:01.0-scsi-0:0:1:0-part2 disk/by-uuid/c230c70d-1b18-4d95-b50a-31edb3bd038c In the execution result, disk/

3. Creating an HDLM Environment318installation.7. Edit the boot loader configuration file for SCSI startup.If you are using SUSE LINUX Enterprise Serv

3. Creating an HDLM Environment319image=/boot/vmlinuz-2.6.18-194.el5 label=linux initrd=/boot/initrd-2.6.18-194.el5 read-only appe

3. Creating an HDLM Environment320option initrd /initrd-2.6.18-194.el5 Example 2: Example of Editing /boot/grub/menu.lst file (When using a kernel

3. Creating an HDLM Environment321prompttimeout=50#default= HDLM_2.6.18-194.el5default= 2.6.18-194.el5-sd image=vmlinuz-2.6.18-194.el5 label=HDLM

3. Creating an HDLM Environment322 kernel /vmlinuz-2.6.9-11.EL ro rhgb quiet initrd /initrd-hdlm-2.6.9-11.EL.gz title Red Hat Enterprise Linux A

3. Creating an HDLM Environment323image file for the SCSI device.When editing the file, be careful of the following:• When an option that depends on t

3. Creating an HDLM Environment324Figure 3-44: Example of Executing the mount Command When the Boot Loader Is LILO or GRUB• When the boot loader is EL

3. Creating an HDLM Environment32518. Delete the initial RAM disk image file that was created with the dlmmkinitrd utility for supporting a boot disk.

2. HDLM Functions11IP-SAN environments supported by HDLMHDLM supports system configurations that use an IP-SAN in the following environments:• OS• Red

3. Creating an HDLM Environment326• When an IA32 host is used:# rm /boot/initrd-hdlm-2.6.18-194.el5.gz• When an IPF host is used:# rm /boot/efi/efi/re

3. Creating an HDLM Environment327To uninstall HNTRLib2:1. Log in to Linux as the root user.2. Execute the following command to unregister the name of

329Chapter4. HDLM OperationThis chapter describes operating procedures for HDLM, including how to operate HDLM and the HDLM manager, and how to change

4. HDLM Operation3304.1 Notes on Using HDLMNote the following when using HDLM.4.1.1 Notes Common to OSsThe following notes are common to OSs: Do not

4. HDLM Operation331Figure 4-1: Overview of the Period Required to Respond to an Application's I/O RequestAs shown in the preceding diagram, when

4. HDLM Operation332fsck, the operation may not finish. In such a case, perform the operation again after restoring the path error. The name of the H

4. HDLM Operation333even while the HDLM device is in use. Before doing so, perform the following operations:1. Unmount any devices mounted on the HDLM

4. HDLM Operation334When a device is dynamically configured by using the udev function, the messages shown below might be output to the console or sy

4. HDLM Operation335 JBD: barrier-based sync failed on sddlmaa1 - disabling barriers  Before you update the OS SP, uninstall HDLM. After you have upd

2. HDLM Functions122.3 LU ConfigurationAfter you have properly installed HDLM, the LU configuration will change as follows:Before the installation of

4. HDLM Operation336JBD: barrier-based sync failed on sddlmaa1 - disabling barriers  Before you update the OS SP, uninstall HDLM. After you have upda

4. HDLM Operation3371. Unmount any devices mounted on the HDLM device.2. Execute the dlmcfgmgr -o command to exclude the HDLM device from management.

4. HDLM Operation338• A Fibre Channel switch's zone setting is changed.

4. HDLM Operation3394.2 Updating Kernel Packages and Applying OS Update PackagesWhen using Red Hat Enterprise Linux 5 or Red Hat Enterprise Linux 6, y

4. HDLM Operation340Perform step 1 to 15 in 3.7.4 Upgrade Installation in an Environment Where an HDLM Device Is Used as a Boot Disk.3. Update the ker

4. HDLM Operation3414.3 HDLM Operations Using CommandsThis section explains how to use the HDLM command. For details on the various command operations

4. HDLM Operation3421. Check the current status of the paths.To place paths online by specifying an HBA port, CHA port, or single path check the path

4. HDLM Operation343port, or single path check the path name or PATH_ID used to manage the path.The following is an example of executing the command:

4. HDLM Operation344To display LU information, execute the dlnkmgr command's view operation with the -lu parameter specified. The following is an

4. HDLM Operation345The following is an example of executing the dlnkmgr command's view operation:# /opt/DynamicLinkManager/bin/dlnkmgr view -drv

2. HDLM Functions13Figure 2-3: LU Configuration Recognized by the Host After HDLM Installation Table 2-3: LU Components lists the components recognize

4. HDLM Operation346Operation name = clear [y/n]:yKAPL01001-I The HDLM command completed normally. Operation name = clear, completion time = yyyy/mm/d

4. HDLM Operation347 # /opt/DynamicLinkManager/bin/dlnkmgr view -sys -audlogAudit Log : offAudit Log Category : -Audi

4. HDLM Operation348# To check whether the settings have been applied, see (1) Viewing the Operating Environment.4.3.8 Viewing License InformationThis

4. HDLM Operation349 # /opt/DynamicLinkManager/bin/dlnkmgr set -licKAPL01049-I Would you like to execute the operation? Operation name = set [y/n]: yK

4. HDLM Operation3504.3.11 Viewing HDLM Component InformationThis section explains how to display HDLM component information.To display HDLM component

4. HDLM Operation351

4. HDLM Operation3524.4 Starting and Stopping the HDLM ManagerIf an error occurs in the system, such as in an HDLM program, you may need to manually s

4. HDLM Operation353 # /opt/DynamicLinkManager/bin/dlnkmgr view -sys -msrvHDLM Manager Ver WakeupTimeAlive x.x.x-xx yyyy/mm/dd hh:mm

4. HDLM Operation354# When the HDLM Manager column shows Dead, the HDLM manager is inactive.Use a script for confirmation:Execute the following comman

4. HDLM Operation3554.5 HDLM Resident ProcessesTable 4-2: HDLM resident processes lists and describes the resident processes in HDLM. To monitor these

2. HDLM Functions142.4 Program ConfigurationHDLM is actually a combination of several programs. Because each program corresponds to a specific HDLM op

4. HDLM Operation3564.6 Reconfiguring the HDLM Operating EnvironmentThis section describes tasks required for reconfiguring the HDLM operating environ

4. HDLM Operation357 # /sbin/lsmod | grep acpiphpacpiphp 58713 0 If the acpiphp module has been loaded, replace the HBAs as described i

4. HDLM Operation358 # /etc/sysconfig/modules/acpiphp.modules After the above command has been executed, confirm that the acpiphp module has been load

4. HDLM Operation359Firmware : 260803 WWPN:2400000047010270 Device:hfcldd2 [LinkUp] WWPN:2400000047010272 Device:hfcldd3 [LinkUp] The

4. HDLM Operation3603. Execute the offline operation of the dlnkmgr command (dlnkmgr offline -hba) to place in Offline(C) status all paths that pass t

4. HDLM Operation361In the above figure, new paths that have been added are indicated by shading.Although the information about the old paths (underli

4. HDLM Operation362information) before the HBAs were replaced remains, this information will be deleted when step 8 is performed.8. Execute the dlmcf

4. HDLM Operation363The paths existing when the HBAs were replaced remain in Offline(E) status.2. Execute the dlmcfgmgr utility (dlmcfgmgr -v) to chec

4. HDLM Operation364HDevName device for which a hyphen (-) is displayed for Device.The following shows an example of the command you execute if the HD

4. HDLM Operation365Figure 4-2: System Configuration for Replacing a Fiber Cable (Explained in the Following Steps)To replace a fiber cable:1. Place i

2. HDLM Functions15Table 2-4: Functionality of HDLM ProgramsProgram name FunctionsHDLM command Provides the dlnkmgr command, which enables you to:• Ma

4. HDLM Operation366Figure 4-3: When the Status of the Path That Goes Through the Fiber Cable to Be Replaced Is Offline(C)2. Replace the fiber cable f

4. HDLM Operation367# /opt/DynamicLinkManager/bin/dlnkmgr view -path For details about the path information, see 6.7 view (Displays Information).4.6.

4. HDLM Operation368be replaced (path that goes through the HBA to which the Fibre Channel switch is connected).For example, to place in Offline (C) s

4. HDLM Operation369In this example, replace the Fibre Channel switch connected to the HBA with host port number 0001.3. Place in Online status the pa

4. HDLM Operation370management, HDLM places online all the normal paths to that HDLM device regardless of the previous status (such as Online(E) or Of

4. HDLM Operation371• A path gets disconnected.• An LU is deleted.• A fiber cable connection is changed.• A Fibre Channel switch's zone setting i

4. HDLM Operation372Table 4-3: Adding or Deleting a SCSI DeviceOperation CommandAdding a device (for FC-SAN environments)• When using a QLogic HBA dri

4. HDLM Operation373Legend:a: Host ID (host port number)b: Channel number (bus number)c: Target IDd: Lun (host LU number)n: host port numberdriver-nam

4. HDLM Operation374The following is an example of executing the dlmcfgmgr utility:# /sbin/dlmcfgmgr -v(3) Adding a Path to an Existing LU To add a pa

4. HDLM Operation375allocations (that is, to delete the paths) to the relevant LU from ports of the storage system.For details on canceling path alloc

2. HDLM Functions162.5 Position of the HDLM Driver and HDLM DeviceThe HDLM driver is positioned above the SCSI driver. Each application on the host us

4. HDLM Operation376The following is an example of executing the dlmcfgmgr utility:# /sbin/dlmcfgmgr -u logical_device_file_name_of_HDLM_device9. Chec

4. HDLM Operation377Perform this operation if necessary. If it is not necessary to check this, go to step 7.If the SCSI device name is not represented

4. HDLM Operation378HDLM.The following is an example of executing the dlmcfgmgr utility:# /sbin/dlmcfgmgr -vIf the Management status of the relevant H

4. HDLM Operation3794. Refer to /var/opt/DynamicLinkManager/log/dlmcfgmgr1.log or execute the dlmcfgmgr utility (dlmcfgmgr -v) or the view operation (

4. HDLM Operation380relevant HDLM device is restored.The following is an example of executing the dlmcfgmgr utility:# /sbin/dlmcfgmgr -v(9) Restoring

4. HDLM Operation381Table 4-4: Add SCSI DevicesPurpose CommandAdd a device (for FC-SAN environments)• When using a QLogic HBA driver on Red Hat Enterp

4. HDLM Operation382Legend:a: Host ID (Port number of the host)b: Channel number (Bus number)c: Target IDd: Lun (LU number of the host)n: host port nu

4. HDLM Operation383If the SCSI device name mapped with the path to the relevant HDLM device is represented with a hyphen (-), in the execution result

4. HDLM Operation384If the SCSI device of the new path that HDLM detected is not yet registered, a new HDLM device is allocated to the path. For examp

4. HDLM Operation385to create an HDLM device file for the new LU.Even if you add a path to an HDLM device that is not managed by HDLM and restart the

2. HDLM Functions172.6 Logical Device Files for HDLM DevicesThe logical device file name of an HDLM device is different from the logical device file n

387Chapter5. TroubleshootingThis chapter describes how to properly use HDLM error information, and then how to resolve the problem, if an error has oc

5. Troubleshooting3885.1 Information Collected by the DLMgetras Utility for Collecting HDLM Error InformationImmediately after an error occurs, execut

5. Troubleshooting3895.2 Checking Error Information in MessagesWhen you want to configure the system so that HDLM messages are output to syslog, speci

5. Troubleshooting390• Host port number (hexadecimal)• Bus number (hexadecimal)• Target ID (hexadecimal)• Host LU number (hexadecimal)This path name i

5. Troubleshooting3915.3 What To Do for a Path ErrorWhen a path error is detected, HDLM performs a failover on the path and outputs the KAPL08022-E me

5. Troubleshooting392Figure 5-2: Troubleshooting Procedure When a Path Error OccursThe following shows the procedure for using the HDLM command (dlnkm

5. Troubleshooting3935.3.3 Identifying the Error PathCheck the obtained path information to find the path with the error. In the Status column, the er

5. Troubleshooting3945.4 What To Do for a Program ErrorThe following describes what to do to handle errors that occur in an HDLM program. Figure 5-3:

5. Troubleshooting3955.4.3 What To Do for the Program ErrorFollow the recommended actions for messages in 8. Messages.If the error occurs again after

2. HDLM Functions18Figure 2-6: About Alphabetic Letters Used in the Logical Device File NameAbout numeric values used in a logical device file name:[1

5. Troubleshooting3965.5 What To Do for Other ErrorsWhen the cause of an error may be related to HDLM but is neither a path error nor an HDLM program

397Chapter6. Command ReferenceThis chapter describes the HDLM command (dlnkmgr) and its operations.6.1 Overview of the HDLM Command dlnkmgr6.2 clear (

6. Command Reference3986.1 Overview of the HDLM Command dlnkmgrThis section describes how to specify the HDLM command dlnkmgr and its subcommands (cal

6. Command Reference399Notes:• Execute the command as a user with root permissions.• To specify a value that contains a space in its parameter, enclos

6. Command Reference4006.2 clear (Returns the Path Statistics to the Initial Value)The dlnkmgr command's clear operation clears the statistics (I

6. Command Reference401(2) To Display the Format of the clear Operation-helpDisplays the format of the clear operation.Example # /opt/DynamicLinkManag

6. Command Reference4026.3 help (Displays the Operation Format)The dlnkmgr command's help operation displays the list of operations available for

6. Command Reference403# /opt/DynamicLinkManager/bin/dlnkmgr help online offline helponline: Format dlnkmgr online [-path] [-s] dlnkmgr online

6. Command Reference4046.4 offline (Places Paths Offline)The dlnkmgr command's offline operation places online paths offline. Specify the paths t

6. Command Reference405HBA port that has the specified host port number and bus number.Specify the host port number and bus number of the target HBA p

2. HDLM Functions192.7 Distributing a Load Using Load BalancingWhen the system contains multiple paths to a single LU, HDLM can distribute the load ac

6. Command Reference406connected to the target CHA port:When the confirmation message is displayed, the user enters y to continue, or n to cancel the

6. Command Reference407device name is /dev/sde while confirming command operation.# /opt/DynamicLinkManager/bin/dlnkmgr offline -path -device /dev/sde

6. Command Reference408 AutoPATH_ID { 000000 - 999999 }(Decimal)KAPL01001-I The HDLM command completed normally. Operation name = offline, comp

6. Command Reference4096.5 online (Places Paths Online)The dlnkmgr command's online operation places offline paths online. Specify the paths to b

6. Command Reference410Specify the host port number and bus number of the target HBA port: the numbers are found in the PathName field displayed using

6. Command Reference411KAPL01057-I All the paths which pass the specified CHA port will be changed to the Online status. Is this OK? [y/n]:yKAPL01061-

6. Command Reference412the response to the confirmation message: for example, when you want to execute the command in a shell script or batch file.Exa

6. Command Reference413target paths before you execute the online operation to place online all the paths connected to a specific HBA port or CHA port

6. Command Reference4146.6 set (Sets Up the Operating Environment)The dlnkmgr command's set operation sets the HDLM operating environment.6.6.1 F

6. Command Reference415Table 6-2: Default and Recommended Values-lb {on [-lbtype {rr|exrr|lio|exlio|lbk|exlbk}]|off}Enables or disables load balancing

2. HDLM Functions20Figure 2-7: Flow of I/O Data When the Load Balancing Function Is Not UsedWhen the load balancing function is not used, I/O operatio

6. Command Reference416exrr: The Extended Round Robin algorithmlio: The Least I/Os algorithmexlio: The Extended Least I/Os algorithmlbk: The Least Blo

6. Command Reference417Operation name = set, completion time = yyyy/mm/dd hh:mm:ss#-elfs error-log-file-sizeSpecify a value from 100 to 2,000,000 (in

6. Command Reference418time before existing information will be overwritten becomes shorter.-systfs trace-file-sizeSpecify a value from 100 to 16,000

6. Command Reference419The explanation for the following sub-parameter describes how to specify the checking interval.-intvl checking-intervalSpecify

6. Command Reference420will be checked in the following way:• When the checking interval has not been specified before:Every minute (default setting)•

6. Command Reference421on: Enabledoff: DisabledIntermittent error monitoring can be set automatic failback is set to on.The default is off. When you u

6. Command Reference422Specify the monitoring interval for an intermittent error. Use a value from 1 to 1440 minutes. The default is 30.During intermi

6. Command Reference423started are reset to 0. Intermittent error monitoring will then resume with the changed settings.If you set the automatic failb

6. Command Reference424Legend:AFB: Automatic failbackIEM: Intermittent error monitoring#1When this condition is not satisfied, the KAPL01080-W message

6. Command Reference425-licSpecify this option for when a license is updated. The HDLM license is provided via a license key or license key file. A li

2. HDLM Functions21Figure 2-8: Flow of I/O Data When the Load Balancing Function Is UsedWhen the load balancing function is used, I/O operations are d

6. Command Reference426KAPL01049-I Would you like to execute the operation? Operation name = set [y/n]: yKAPL01071-I A permanent license was installed

6. Command Reference427-category [[ss] [a] [ca]|all]Specifies the categories of audit log data to be collected. Table 6-8: Values Indicating Audit Log

6. Command Reference428for load balancing.You can specify a decimal (base 10) value from 0 to 999999. The default is 32.If you specify 0, operation is

6. Command Reference429 [ -intvl Error-Monitor-Interval ] [ -iemnum Number-Of-Times ] | -

6. Command Reference430 Facility-Name { user | local0 - local7 } (Default Value user) Facility-Number

6. Command Reference4316.7 view (Displays Information)The dlnkmgr command's view operation displays HDLM program information, path information, L

6. Command Reference432[-srt {lu|cp}][-t](3) To Display LU InformationTo display LU information/opt/DynamicLinkManager/bin/dlnkmgr view -lu[-hdev host

6. Command Reference433(5) To display the format of the view operation(1) To display program information-sys [-sfunc|-msrv|-adrv|-pdrv|-lic|-audlog|-l

6. Command Reference434Support ClusterBlank#Elog Level Error logging level:•0: Collects no error information.•1: Collects error information at the Err

6. Command Reference435Reservation StatusBlankIntermittent Error Monitor• Setting for intermittent error monitoring:on: Enabledoff: DisabledWhen autom

2. HDLM Functions22that uses a CHA other than the owner controller (a non-owner controller). Paths used for load balancing are selected from owner pat

6. Command Reference436-licInformation about the HDLM licenseLicense Type License type•Permanent• Temporary• EmergencyExpirationLicense expiration:Whe

6. Command Reference437#When you use cluster software, the settings of the cluster function and the kinds of cluster servers are not displayed. Howeve

6. Command Reference438HDLM Alert Driver Ver WakeupTime ElogMem SizeAlive x.x.x-xx yyyy/mm/dd hh:mm:ss 1000KAPL01001-I

6. Command Reference439-lbpathusetimesTimes Same Path Was Used : 32KAPL01001-I The HDLM command completed normally. Operation name = view, completi

6. Command Reference440Table 6-14: Product ID displayed by the view -path operation.-iemUse this parameter to add IEP to path information and display

6. Command Reference441When you specify the -path parameter together with the -item parameter, the command only displays the items specified by the va

6. Command Reference442information for all the paths in ascending order of AutoPATH_IDs.These sub-parameters are:-hdev host-device-nameDisplays inform

6. Command Reference443-tOmits the title for each information item.Example In the following example, IO-Count is selected as the display item and the

6. Command Reference444 When you use the -c parameter, the number of characters that can be displayed in the product ID element of the DskName field

6. Command Reference445Items of Path informationTable 6-12: Path Information describes the displayed path information. The following explains the tabl

2. HDLM Functions23Data When the Load Balancing Function Is Used, the load is balanced among the four paths A, B, C, and D. If one of the paths were t

6. Command Reference446PathStatus Status of the displayed paths. The displayed status indicates the following:•Online: All paths are available.•Reduce

6. Command Reference447iLU#iLU LU number of the storage system.This number combined with the storage system name (shown in DskName) identifies the LU

6. Command Reference448IO-Count#- Total I/O count for the path, indicated by a decimal number. The maximum value that can be displayed is 232 - 1 (429

6. Command Reference449Legend:- : Not displayed#The path information is displayed only when a value is specified for the -path -item parameter.Table 6

6. Command Reference450#If the -c parameter is specified together with the -path parameter, when the number of characters exceeds 10, any characters a

6. Command Reference451parameter and the LU information and displayed items.To display LU information-luWhen neither the -c nor -item parameter is spe

6. Command Reference452 /dev/sdj 000013 Online /dev/sdo 000018 Online0002 sddlmae /dev/sdu 000004 Online /dev/

6. Command Reference453In the sub-parameters, -hdev or -pathid, you can filter the LU information to be displayed. If you omit both parameters, the co

6. Command Reference454To display a summary of LU information-lu -cWhen the -c parameter is specified with the -lu parameter, a summary of LU configur

6. Command Reference455To display a summary of LU information (by selecting items to be displayed)-lu -c -itemThe items displayed when the -item optio

2. HDLM Functions24• Extended Round RobinThe paths are simply selected in order from among all the connected paths.• Extended Least I/OsThe path that

6. Command Reference456• Summary displayed: The user specifies the -lu -c parameter or -lu -c -item parameter.Table 6-17: LU InformationDisplayed item

6. Command Reference457Device - SCSI device associated with an HDLM device. If the SCSI device is not connected when a host starts, or the assigned L

6. Command Reference458Status - Status of the pathOnline: OnlineOffline(C): Offline status caused by a command operationOffline(E): Offline due to an

6. Command Reference459Legend:- : Not displayed#1 This information is displayed when one of the following conditions exist: - The user selected the it

6. Command Reference460- No value was specified for the parameter.(4) To display corresponding information about an HDLM device, SCSI device, and LDEV

6. Command Reference461To display corresponding information about an HDLM device, SCSI device, and LDEV# /opt/DynamicLinkManager/bin/dlnkmgr view -drv

6. Command Reference462 dlnkmgr view -lu [ -hdev HostDeviceName | -pathid AutoPATH_ID ] [-t] dlnkmgr view -lu -item [ [slpr] [pn

463Chapter7. Utility ReferenceThis chapter explains the utilities used by HDLM.7.1 Overview of the Utilities7.2 DLMgetras Utility for Collecting HDLM

7. Utility Reference4647.1 Overview of the UtilitiesHDLM provides the following utilities:• The DLMgetras utility for collecting HDLM error informatio

7. Utility Reference465For details, see 7.7 dlmstart Utility for Starting HDLM.• The installgetras utility for collecting HDLM installation error info

2. HDLM Functions252.8 Performing Failovers and Failbacks Using Path SwitchingWhen the system contains multiple paths to an LU and an error occurs on

7. Utility Reference4667.2 DLMgetras Utility for Collecting HDLM Error InformationThis utility collects information that is needed to analyze HDLM err

7. Utility Reference467Specify the output directory for the information that is to be collected by the DLMgetras utility for collecting HDLM error inf

7. Utility Reference468• The root directory (/) cannot be specified.• When a directory is specified, the DLMgetras utility collects all the files in t

7. Utility Reference469cluster.tar.gz file, which is recorded by the OS and cluster commands when the DLMgetras utility is executed.•hbsa.tar.gzThis f

7. Utility Reference470#1Each output directory is created in the directory that is specified when the user expands the cluster.tar.gz file.#2This info

7. Utility Reference471#This information is collected only if software for which information is to be collected is installed./opt/VRTSvcs/bin/hagrp -s

7. Utility Reference472Table 7-3: Information Stored in the getras.tar.gz FileOutput directory#1Files ExplanationThe output destination directory spec

7. Utility Reference473modprobe.conf.local Load module information file(when using SUSE LINUX Enterprise Server)mtab Mount informationqla*.conf QLogic

7. Utility Reference474/etc/modprobe.d All files Load module information file (when using Red Hat Enterprise Linux 5 or Red Hat Enterprise Linux 6)/et

7. Utility Reference475kernel Kernel configuration file (when using SUSE LINUX Enterprise Server)lvm Boot LVM information file (when using SUSE LINUX

iPrefaceThis manual describes the functions and use of the following program products:• Hitachi Dynamic Link ManagerIntended ReadersThis manual is int

2. HDLM Functions26For details on error levels, see 2.11.2 Filtering of Error Information.When the Thunder 9500V series, or Hitachi AMS/WMS series is

7. Utility Reference476/etc/xen/vm All subdirectories and filesDomain-related files (when using SUSE LINUX Enterprise Server 10 or SUSE LINUX Enterpri

7. Utility Reference477stat Statisticsswaps SWAP informationuptime System's operating time informationversion Kernel version information/proc/irq

7. Utility Reference478/tmp qemu.log KVM-related log file (when using Red Hat Enterprise Linux 5 or Red Hat Enterprise Linux 6)/var/lib/dhclient dhcli

7. Utility Reference479#1Each output directory is created in the directory that is specified when the user expands the getras.tar.gz file.#2Informatio

7. Utility Reference480directory is collected.#3The value N depends on the setting in the dlmwebagent.properties file. The default is 2.Table 7-4: Inf

7. Utility Reference481/bin/ls -altRZ /etc/rc.d rc_security.txt List of script files containing security context information (when using Red Hat Enter

7. Utility Reference482/etc/init.d/openais status openais-status.txt OpenAIS status information/opt/DynamicLinkManager/bin/dlmgetomtrace dlmgetomtrace

7. Utility Reference483/opt/DynamicLinkManager/bin/dlnkmgr view -sys,/opt/DynamicLinkManager/bin/dlnkmgr view -sys -sfunc,/opt/DynamicLinkManager/bin/

7. Utility Reference484/sbin/e2label e2label.txt Label information (all the SCSI device names and the corresponding label names are displayed in each

7. Utility Reference485/sbin/lvs lvs.txt Logical volume information (when using Red Hat Enterprise Linux 6 or SUSE LINUX Enterprise Server)/sbin/o2cb_

2. HDLM Functions27Figure 2-10: Path Switching(2) Automatic FailbacksWhen a path recovers from an error, HDLM can automatically place the recovered pa

7. Utility Reference486ulimit -a ulimit-a.txt Limit values of the available system resources (data segment, stack segment, and file descriptor) for th

7. Utility Reference487/usr/sbin/raw -qa raw-qa.txt Character-type device information (when using SUSE LINUX Enterprise Server 9 or SUSE LINUX Enterpr

7. Utility Reference488/usr/sbin/lvmdiskscan lvmdiskscan.txt lvm disk information (when using Red Hat Enterprise Linux AS4/ES4 or Red Hat Enterprise L

7. Utility Reference4897.3 dlmcfgmgr Utility for Managing the HDLM ConfigurationFor management by HDLM, the HDLM-configuration definition utility obta

7. Utility Reference490-sSpecify this parameter when you do not want to display the confirmation messages during execution of the dlmcfgmgr utility. W

7. Utility Reference491#A newly assigned logical device file name of the HDLM deviceEvery time the host starts, the dlmcfgmgr utility (dlmcfgmgr -r) i

7. Utility Reference492HDLM device that is not managed by HDLM, that HDLM device will not be managed by HDLM.-o {logical-device-file-name-of-the-HDLM-

7. Utility Reference493immediately after execution of the utility.You can use this parameter to reset an HDLM device that must be managed again to a m

7. Utility Reference494time once it is recognized. Even if the recognized HDLM device is not available because this path is disconnected or the LU is

7. Utility Reference495To exclude the HDLM device sddlmaa from being managed without confirming the execution of the utility:Example 3:To delete the i

2. HDLM Functions28Storage Platform V/VM, Virtual Storage Platform, Hitachi AMS2000 series, or Hitachi SMS is being used, all the paths are owner path

7. Utility Reference496Table 7-7: Information for the Management Status and Configuration Information of an HDLM DeviceExample 5:The following shows a

7. Utility Reference497#dlmcfgmgr -logfsKAPL10938-I dlmcfgmgr Log File Size(KB) : 10240# Reference informationIf you do not specify a parameter, the s

7. Utility Reference498device is executed. For example, when this utility executes an operation specified with the -o parameter for /dev/sddlmaa, /dev

7. Utility Reference499cannot be used might increase.1. Update the HDLM device with information about unavailable SCSI devices by executing the dlmcfg

7. Utility Reference5007.4 dlmmkinitrd Utility for Supporting a Boot DiskThis utility creates an initial RAM disk image file for using an HDLM device

7. Utility Reference501kernel-versionSpecify the kernel used for creating an initial RAM disk image file.ExampleThe following shows an execution examp

7. Utility Reference502parameter.-b boot-directorySpecify the path for the location in which the initial RAM disk image file is to be created. This pa

7. Utility Reference5037.5 dlmpr Utility for Clearing HDLM Persistent ReservationIf the persistent reservation of the LU is not canceled for some reas

7. Utility Reference504ExampleTo check the reservation keys, and then clear a reservation key:1. Execute the dlmpr utility to display the reservation

7. Utility Reference505- A persistent reservation has been set by the cluster software.Operation1. Clear persistent reservation, specifying the SCSI d

2. HDLM Functions29Executing the online operation places the offline path online. For details on the online operation, see 6.5 online (Places Paths On

7. Utility Reference5067.6 dlmsetopt Utility for Setting HDLM Driver OptionsThis utility changes the settings for the HDLM filter driver. Restart the

7. Utility Reference507command executed from another application.InquiryTimeoutSpecify a numeric value of -1 or in the range from 1 to 3,600.-1: This

7. Utility Reference508# /opt/DynamicLinkManager/bin/dlmsetopt -r 100000KAPL12554-I The utility for setting HDLM driver option has started.KAPL12555-I

7. Utility Reference509Table 7-9: Setting file names for boot loadersBoot loader File NameLILO/etc/lilo.confGRUB For Red Hat Enterprise Linux /etc/gru

7. Utility Reference5107.7 dlmstart Utility for Starting HDLMYou must perform the following operations after installing HDLM:• Load an HDLM alert driv

7. Utility Reference5117.8 dlmupdatesysinit Utility for Updating System ScriptsIn an environment that uses Red Hat Enterprise Linux, if you update the

7. Utility Reference5127.9 installgetras Utility for Collecting HDLM Installation Error InformationThis utility collects the error log information nee

7. Utility Reference513#This directory is created in directory-to-which-collected-information-is-output specified when the installgetras utility was e

7. Utility Reference5147.10 installhdlm Utility for Installing HDLMYou can use this utility to perform a new installation, upgrade installation, or re

7. Utility Reference515KAPL09228-W message is output.(2) Items To Be Defined in an Installation-Information Settings FileThe following describes the i

2. HDLM Functions30The status indicating that an I/O could not be issued on a given path, because an error occurred on the path.The (E) means error.(3

7. Utility Reference516Legend:Optional: If a key and its setting are not specified, the default value will be used.However, for an upgrade installatio

7. Utility Reference517[ENVIRONMENT_SETTINGS] sectionThis section defines HDLM operation information. If this section is omitted, the installer will u

7. Utility Reference518error_log_level Set the level of error information that is collected as error logs.You can set a level from 0 to 4. The default

7. Utility Reference519Legend:Optional: If a key and its setting are not specified, the installer uses the default.#1If you are upgrading or re-instal

7. Utility Reference520You can specify this key only in the following cases:• For a new installation:When on is specified for the auto_failback key in

7. Utility Reference5217.11 installux.sh Utility for HDLM Common InstallerThis utility determines what OS HDLM will be installed on, and installs the

523Chapter8. MessagesThis chapter describes the format and meaning of the message IDs, and also the terms used in the messages and message explanation

8. Messages5248.1 Before Viewing the List of MessagesThis section explains the following information that is needed to locate messages and understand

8. Messages525• HDLM driver (filter component)• HDLM alert driver• HDLM management target

2. HDLM Functions31• All the paths connected to an LU are Online(E), Offline(E), or Offline(C).• All the paths connected to an LU have been determined

8. Messages5268.2 KAPL01001 to KAPL02000KAPL01001-IThe HDLM command completed normally. Operation name = aa...aa, completion time = bb...bbDetailsThe

8. Messages527KAPL01005-WA parameter is invalid. Operation name = aa...aa, parameter = bb...bbDetailsaa...aa: clear, set, online, offline, or viewbb..

8. Messages528Specify the parameter value, and then retry.KAPL01009-WA parameter value is invalid. Operation name = aa...aa, parameter = bb...bb, para

8. Messages529KAPL01014-WNo authority to execute the HDLM command. Operation name = aa...aaDetailsYou do not have the administrator permissions necess

8. Messages530aa...aa: viewActionExecute the view operation of the HDLM command (dlnkmgr view -path) and check the value displayed in PathName. Specif

8. Messages531Stop unnecessary applications, increase the amount of free memory, and then re-execute the HDLM command.KAPL01023-WThe last Online path

8. Messages532To ignore this path and perform online processing for the next path, enter y.To cancel processing, enter n.aa...aa: Path ID (decimal (ba

8. Messages533Detailsaa...aa: offline, online, set, or viewbb...bb: Parameter namecc...cc: Parameter valueActionExecute help operation-name of the HDL

8. Messages534ActionIf you want to execute online processing, enter y. If you want to terminate processing, enter n. For details on the online operati

8. Messages535processing, enter n. For details on the offline operation, see 6.4 offline (Places Paths Offline).KAPL01054-WDuring the offline operatio

2. HDLM Functions322.9 Monitoring Intermittent Errors (Functionality When Automatic Failback Is Used)An intermittent error refers to an error that occ

8. Messages536If you want to execute offline processing for the paths that meet the specified requirements, enter y. If you want to terminate processi

8. Messages537dd...dd: view or setActionExecute help operation-name of the HDLM command (dlnkmgr) to check the parameter and parameter value, and then

8. Messages538ActionUse the view operation of the HDLM command (dlnkmgr) to check the status of the path. For details on the view operation, see 6.7 v

8. Messages539KAPL01072-IThe emergency license was installed. The license expires on aa...aa.DetailsA license was renewed and is registered as an emer

8. Messages540None.KAPL01079-WThe intermittent error monitoring function cannot be set up because automatic failback is disabled.DetailsThe intermitte

8. Messages541ActionMake sure that the license key file is correct, and then re-execute./var/tmp/hdlm_licenseKAPL01083-IThere is no license key file.

8. Messages542KAPL01089-EOne of the following was executed at the same time as an HDLM command set -lic operation: another set -lic operation, or an u

8. Messages543If you set a value that is less than the current value of the trace file size or number of trace files, all the current trace files will

8. Messages544aa...aa: clear, offline, online, set, or viewActionIf you did not perform HDLM configuration, Perform HDLM configuration.When performing

8. Messages545result, contact your HDLM vendor or maintenance company if there is a maintenance contract for HDLM.KAPL01116-WThe audit log configurati

2. HDLM Functions332.9.3 Intermittent Error Monitoring ActionsIntermittent error monitoring is performed on each path, and it automatically starts as

8. Messages546contract for HDLM.KAPL01120-WA storage subsystem model ID could not be displayed. Details = aa...aa, bb...bbDetailsA storage system mode

8. Messages547KAPL01125-EThe directory does not exist. Directory name = aa...aaDetailsaa...aa: /HDLM installation path, /HDLM installation path/libAct

8. Messages5488.3 KAPL03001 to KAPL04000KAPL03001-IHDLM API information - aa...aaDetailsThis information is required for resolving problems.aa...aa: T

8. Messages549aa...aa: API trace error informationActionExecute the DLMgetras utility for collecting HDLM error information, and then contact your HDL

8. Messages550contract for HDLM. For details on the DLMgetras utility, see 7.2 DLMgetras Utility for Collecting HDLM Error Information.

8. Messages5518.4 KAPL04001 to KAPL05000KAPL04001-IHDLM manager started.ActionNone.KAPL04002-ECould not start the HDLM manager.DetailsThe HDLM manager

8. Messages552aa...aa: Option definition file nameActionCheck whether another program is currently using this file (for example, the file is being ope

8. Messages553KAPL04012-ECould not create a communication pipe. RC = aa...aaDetailsHDLM manager could not start normally because it was unable to crea

8. Messages554DetailsAn attempt to read the log information from the alert driver failed.aa...aa: API return code (decimal (base-10) number)ActionExec

8. Messages555Utility for Collecting HDLM Error Information.KAPL04024-CA critical error occurred in the HDLM manager. (aa...aa)DetailsThis information

2. HDLM Functions34(2) When an Intermittent Error Does Not OccurIf an error does not occur on a path a specified number of times within a specified in

8. Messages556Install a permanent license by the expiration day.KAPL04028-EThe temporary license expired.ActionInstall a permanent license.KAPL04029-E

8. Messages557KAPL04034-EAn attempt to create the option definition file has failed.DetailsAn attempt to re-create an option definition file (/etc/opt

8. Messages558aa...aa: Trap IDbb...bb: Destination IP address of the trapcc...cc: Destination port number of the trapdd...dd: Community name given to

8. Messages559ActionReinstall HDLM.KAPL04051-EThe execution file does not exist. File name = aa...aaDetailsaa...aa: /HDLM installation path/bin/.dlnkm

8. Messages5608.5 KAPL05001 to KAPL06000KAPL05003-IThe HDLM driver (filter component) was successfully attached to Disk (aa...aa), Partition (bb...bb)

8. Messages561The path corresponding to the disk aa...aa and partition bb...bb could not be registered in the core logic. aa...aa: Disk sequence numbe

8. Messages562of the path, execute the DLMgetras utility for collecting error information, and then contact the HDLM vendor or the maintenance company

8. Messages563DetailsAn attempt to process the requested IOCTL call has failed.aa...aa: IOCTL code (hexadecimal number)bb...bb: Error code (hexadecima

8. Messages564separated by period)aa...aa: Host ID (host port number) (decimal number)bb...bb: Channel number (bus number) (decimal number)cc...cc: Ta

8. Messages565Detailsaa...aa: Memory allocation retry count (decimal number)ActionNone.KAPL05711-IThe timeout value and retry count of SCSI INQUIRY ha

2. HDLM Functions35(3) When the Conditions for an Intermittent Error Are Changed During Error MonitoringWhen the conditions for an intermittent error

8. Messages566dd...dd: Maintenance information (hexadecimal number)ActionNone.

8. Messages5678.6 KAPL06001 to KAPL07000KAPL06004-ECould not allocate memory. (aa...aa:bb...bb)DetailsAn attempt to reserve memory to save alert infor

8. Messages568aa...aa: IOCTL code (hexadecimal number)ActionNone.KAPL06010-ECould not process the IOCTL(aa...aa). (bb...bb:cc...cc)DetailsAn IOCTL req

8. Messages569Information.KAPL06014-ECould not write emergency information into the emergency information buffer. (aa...aa:bb...bb) DetailsUrgent info

8. Messages570aa...aa: Name of file where error was detected.ActionReinstall an HDLM.

8. Messages5718.7 KAPL07001 to KAPL08000KAPL07819-IData for maintenance: aa...aa bb...bb cc...cc dd...dd.DetailsThis message is generated by the core

8. Messages5728.8 KAPL08001 to KAPL09000KAPL08019-EThe path (aa...aa) detected an error (bb...bb). (cc...cc)DetailsAn error occurred in the path. The

8. Messages573ee...ee: Target ID (same as PathName of view -path) (hexadecimal number)ff...ff: HLU number (same as PathName of view -path) (hexadecima

8. Messages574KAPL08027-EA path was excluded from the items subject to automatic failback. PathID = aa...aaDetailsA path was excluded from being subje

8. Messages5758.9 KAPL09001 to KAPL10000KAPL09001-EThere is no system management permission. Login with root permission and re-install HDLM.DetailsThe

iiproblems that you might encounter.6. Command ReferenceChapter 6 describes all the HDLM commands.7. Utility ReferenceChapter 7 describes the HDLM uti

2. HDLM Functions36check the IEP item displayed when the dlnkmgr command's view -path operation is executed with the -iem parameter specified. If

8. Messages576KAPL09013-ESome HDLM drivers could not be removed.DetailsDeleting several HDLM drivers failed because these HDLM drivers were being used

8. Messages577maintenance contact of HDLM.KAPL09023-EA file or directory related to HDLM could not be found. Re-install HDLM.DetailsA target file to c

8. Messages578KAPL09035-EThe HDLM driver could not be loaded. Execute the dlmstart utility. For details on the dlmstart utility, refer to the HDLM Use

8. Messages579KAPL09039-EThe HDLM devices could not be configured. Execute the HDLM-configuration definition utility (dlmcfgmgr) with the -r parameter

8. Messages580KAPL09045-EAn attempt to create a file or directory related to HDLM has failed. Make sure that sufficient disk space exists, and then re

8. Messages581KAPL09050-EThe driver module dependencies could not be updated. Contact your HDLM vendor or the maintenance company if there is a mainte

8. Messages582KAPL09078-IThe emergency license was installed. The license expires on aa...aa.DetailsAn emergency license was installed.aa...aa: Year (

8. Messages583KAPL09083-WThe emergency license expired.ActionInstall a permanent license.KAPL09087-EThe entered license key is invalid. Renewal of the

8. Messages584KAPL09092-IThe installation was stopped because a stop request was received.DetailsThe installation was aborted, because a stop request

8. Messages585ActionNone.KAPL09097-EA package installable on this system was not found. Please check whether HDLM is supported for this system. For de

2. HDLM Functions37When you turn the intermittent error monitoring function off, information about paths not subject to automatic failback will be res

8. Messages586DetailsThere is no license key file in the designated directory.aa...aa: /var/tmp/hdlm_licenseActionSave the correct license key file in

8. Messages587DVD-ROM was copied, make sure that all the contents of the DVD-ROM have been copied to that directory, and then retry the installation.K

8. Messages588Detailsaa...aa: Referenced directory nameActionCheck the directory displayed in the message. Re-install HDLM after creating the director

8. Messages589/media/cdrom• For SUSE LINUX Enterprise Server 9:/media/cdrom/media/cdrecorder/media/dvd/media/dvdrecorder/media/dvdram• For SUSE LINUX

8. Messages590Linux 6 Kernels Supported by HDLM, Table 3-5: SUSE LINUX Enterprise Server 9 Kernels Supported by HDLM, Table 3-6: SUSE LINUX Enterprise

8. Messages591DetailsAlthough the aa...aa processing has ended, an error occurred during the processing.aa...aa: ENVIRONMENT_SETTINGS, driver_config_s

8. Messages592An error occurred during I/O of a file that installhdlm uses.aa...aa: Error number that indicates the executed processing (decimal (base

8. Messages593permission, re-execute installhdlm.If aa...aa is installhdlm_analysis:The correct location of installhdlm_analysis is /DVD-ROM/HDLM_Linu

8. Messages594KAPL09221-WThe definition of the installation information settings file includes an unusable character. Error Code = aa...aa,bb...bb, li

8. Messages595operation.KAPL09229-WThe definition of the installation information settings file includes an invalid section name. Error Code = aa...aa

2. HDLM Functions382.10 Detecting Errors by Using Path Health CheckingHDLM can check the status of paths for which I/O operations are not being perfor

8. Messages596Specify the revised installation information settings file and then retry the operation.KAPL09232-WThe composition of the definition of

8. Messages597operation.KAPL09238-WThe specified file is not a normal one. Fail name = aa...aaDetailsA file other than a normal one (for example, a di

8. Messages598KAPL09245-ECould not delete file supporting driver update.DetailsCould not delete file supporting driver update.ActionContact your HDLM

8. Messages599aa...aa: /HDLM installation directory, /HBsA installation directoryActionReinstall HDLM.KAPL09501-EHDLM is not installed on this system.

8. Messages600KAPL09510-EService Pack aa...aa cannot be installed. A newer version has already been installed.DetailsA newer version is already instal

8. Messages601all of the DVD-ROM files.KAPL09603-EThe installation will now stop because a command or utility cannot be executed. Confirm that the com

8. Messages6028.10 KAPL10001 to KAPL11000KAPL10001-WNo parameter has been specified.DetailsNo directory to which the collected information will be out

8. Messages603ActionCheck the parameters of the DLMgetras utility for collecting HDLM error information, and then retry. For details on the DLMgetras

8. Messages604DetailsYou do not have write permission for the specified directory, or the creation of a subdirectory of the specified directory failed

8. Messages605DetailsTwo or more file names or directory names exist in the file for defining the information to be collected.aa...aa: Line number of

2. HDLM Functions392.11 Error ManagementHDLM collects information for troubleshooting into log files. HDLM can also filter error information according

8. Messages606bb...bb: Indicated contents in a lineActionAfter the DLMgetras utility for collecting HDLM error information terminates, check the conte

8. Messages607DetailsThe root directory has been specified in the first parameter. A root "/" cannot be specified in a directory to which co

8. Messages608KAPL10022-IThe utility for collecting HDLM error information completed normally.DetailsError information has been collected.ActionNone.

8. Messages609The file to collect does not exist.aa...aa: Name of file to collectActionNone.KAPL10034-EThe file could not be copied. Filename = aa...a

8. Messages610the time of execution, and then contact your HDLM vendor or the maintenance company if you have a maintenance contract for HDLM.KAPL1003

8. Messages611Managing the HDLM Configuration.KAPL10302-I/sbin/dlmcfgmgr completed normally.DetailsThe HDLM-configuration definition utility (dlmcfgmg

8. Messages612DetailsThe configuration definition file (/etc/opt/DynamicLinkManager/.dlmfdrv.conf) could not be created.ActionExecute the DLMgetras ut

8. Messages613aa...aa: Logical device file name of HDLM deviceActionNone.KAPL10316-ECould not allocate memory. Size = aa...aa. Execute the DLMgetras u

8. Messages614 | -u {special-file-name ... | all} |-logfs [log-file-size]}DetailsSince the paramet

8. Messages615KAPL10322-EA file that defines HDLM-unmanaged disks could not be created. File name = aa...aa, Errno = bb...bb. Execute the DLMgetras ut

2. HDLM Functions40Figure 2-15: Flow of Data When Collecting Error InformationLogs might be collected in layers below HDLM, such as for the SCSI drive

8. Messages616None.KAPL10325-EA regular expression cannot be established. The files will not be deleted. Errno = aa...aa. Execute the DLMgetras utilit

8. Messages617KAPL10328-EThe entered value is invalid. The HDLM-configuration definition utility processing will now stop. Execute the HDLM-configurat

8. Messages618Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if the

8. Messages619information, and then contact your vendor or maintenance company.DetailsAn internal error occurred during file operation.aa...aa: File n

8. Messages620Execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the maintenance company if the

8. Messages621This message checks whether you want to change the configuration definition of an HDLM device.ActionEnter y to continue. Enter n to canc

8. Messages622KAPL10344-IHDLM has detected and registered a new path to an already registered HDLM device. HDLM device = aa...aa, Device = bb...bb (Ho

8. Messages623KAPL10346-IHDLM has unregistered an existing HDLM device. HDLM device = aa...aaDetailsBy executing the HDLM-configuration definition uti

8. Messages624aa...aa: Logical device file name of HDLM deviceActionNone. For details on the dlmcfgmgr utility, see 7.3 dlmcfgmgr Utility for Managing

8. Messages625KAPL10352-WThe HDLM device is in use. HDLM device = aa...aa. Stop the application using the HDLM device, unmount the HDLM device being m

2. HDLM Functions412.11.1 Types of Collected LogsHDLM collects information on the detected error and trace information in the process-specific-trace i

8. Messages626device, and re-execute the dlmcfgmgr utility. For details on the dlmcfgmgr utility, see 7.3 dlmcfgmgr Utility for Managing the HDLM Conf

8. Messages627(decimal number)ActionRevise the configuration of the HDLM device to reduce the number of HDLM devices used, and then re-execute the dlm

8. Messages628aa...aa: HDLM device namebb...bb: SCSI device namecc...cc: Host ID (decimal number)Channel: Channel ID (fixed value: 0) (decimal number)

8. Messages629bb...bb: SCSI device namecc...cc: Host ID (decimal number)Channel: Channel ID (fixed value: 0) (decimal number)dd...dd: Target ID (decim

8. Messages630KAPL10365-WThe LDEV for an HDLM device has changed. The processing for that HDLM device will be cancelled. HDLM device = aa...aa. Execut

8. Messages631KAPL10643-WA necessary parameter is not specified.DetailsA parameter is not specified for the dlmpr utility.ActionExecute the dlmpr -h u

8. Messages632and then retry. For details on the dlmpr utility, see 7.5 dlmpr Utility for Clearing HDLM Persistent Reservation.KAPL10648-EAn internal

8. Messages633DetailsThe dlmpr utility has been terminated because n was sent to a request.ActionNone. For details on the dlmpr utility, see 7.5 dlmpr

8. Messages634For details on the dlmcfgmgr utility, see 7.3 dlmcfgmgr Utility for Managing the HDLM Configuration.KAPL10922-EThe version of the kernel

8. Messages635For details on the DLMgetras utility, see 7.2 DLMgetras Utility for Collecting HDLM Error Information.KAPL10935-WAn internal error occur

2. HDLM Functions42#When you want to configure the system so that HDLM messages are output to syslog, specify user for the facility in the syslog sett

8. Messages636same as, the maximum number. Refer to the Messages section of the HDLM User's Guide for instructions to correct this problem.Detail

8. Messages637If it is not correct, execute the DLMgetras utility for collecting HDLM error information, and then contact your HDLM vendor or the main

8. Messages638DetailsAn error occurred during processing to read a file in the (aa...aa) function.bb...bb: File namecc...cc: ErrnoActionConfirm that t

8. Messages639iscsi_boot=yKAPL10949-EA necessary file was not found. File name = aa...aaDetailsA necessary file was not found.aa...aa: File nameAction

8. Messages6408.11 KAPL11001 to KAPL12000KAPL11901-Iaa...aa has started.DetailsThe operation has started on the host.aa...aa: Operation (character str

8. Messages641None.KAPL11903-Iaa...aa has completed normally.DetailsThe operation has completed normally on the host.aa...aa: Any of the following ope

8. Messages642• Clear Data• Get HDLM Driver Status• Get HDLM Manager Status• Get HDLM Alert Driver Status• Online• Offline• Get SNMP Trap Information•

8. Messages643KAPL11907-IXML reception - aa...aaDetailsThis information is required for resolving problems.aa...aa: XML information (character string)

8. Messages6448.12 KAPL12001 to KAPL13000KAPL12035-EThe version of the kernel supported by the installed HDLM does not match the currently running ker

8. Messages645ActionIf the file name displayed in the message is the file name specified in the fstab parameter of the Boot Disk Support Utility (dlmm

2. HDLM Functions43• Collects error information from the Information level and higher.• Collects error information from the Information level and high

8. Messages646KAPL12306-IThe list of files required in the initial ramdisk image is being created.ActionNone.KAPL12307-IThe initial ramdisk file syste

8. Messages647ActionNone.KAPL12314-IThe compressed initial ramdisk image is being created.ActionNone.KAPL12315-IA compressed initial ramdisk image aa.

8. Messages648This message is always preceded by some other specific error message.KAPL12320-EA file or directory already exists. File name = aa...aaD

8. Messages649aa...aa: The name of the module whose insertion has failedActionConfirm that the system environments are not changed after creating the

8. Messages650dlmcfgmgr utility.• Confirm that the user has write permission in the root directory (/).dlnkmgr:• Confirm that HDLM has been configured

8. Messages651KAPL12327-EAn invalid entry is registered in the file. File name = aa...aaDetailsaa...aa: The name of the file containing the invalid en

8. Messages652None.KAPL12331-EA directory with the specified kernel version does not exist. Directory name = aa...aaDetailsaa...aa: The directory wher

8. Messages653KAPL12333-EAn HBA that HDLM can support as a boot disk was not found in the file. File name = aa...aaDetailsaa...aa: The name of the fil

8. Messages654Modify the fstab file specified in the fstab parameter of the boot disk support utility (dlmmkinitrd), or the file system of the /etc/fs

8. Messages655ActionNone.KAPL12344-IA compressed initial ramdisk image (aa...aa) was created.Detailsaa...aa: The created initial ramdisk imageActionNo

2. HDLM Functions442.12 Collecting Audit Log DataHDLM and other Hitachi storage-related products provide an audit log function so that compliance with

8. Messages656Wait until the executing utility finishes, and then re-execute dlmsetopt.If two or more utilities are not executing simultaneously, dele

8. Messages657ActionRestart the computer.KAPL12559-EAn invalid value was specified in the parameter. Option = aa...aa, Parameter = bb...bbDetailsaa...

8. Messages658KAPL12563-EAn attempt to create a directory has failed. Directory = aa...aaDetailsaa...aa: Directory that an attempt was made to createA

8. Messages659dlmdrvopt.conf.• When the file contents match:Delete the /etc/opt/DynamicLinkManager/DLMSETOPT/modprobe.conf file. Then, re-execute the

8. Messages660ActionInstall HDLM that adjusts to the kernel that is running now.KAPL12802-EThe HDLM file is invalid. File name = aa...aaDetailsA file

8. Messages661ActionInstall HDLM that adjusts to the kernel that is running now.KAPL12902-EThe HDLM file is invalid. File name = aa...aaDetailsA file

8. Messages6628.13 KAPL13001 to KAPL14000KAPL13204-WThe file does not exist. File name = aa...aaDetailsaa...aa: /etc/.DynamicLinkManager/Path00, /etc/

8. Messages663KAPL13401-ENo parameter has been specified.DetailsNo parameter (directory to which collected information is output) has been specified.A

8. Messages664ActionThe specified directory already exists. Enter y to overwrite the existing file. Enter n or press any other key to terminate the ut

8. Messages665The process has been terminated by an operation such as Ctrl + c.ActionThe utility for collecting HDLM install error information termina

2. HDLM Functions45The categories of audit log data that can be collected differ depending on the product. The following sections explain only the cat

8. Messages666ActionRe-execute the utility for collecting HDLM install error information.KAPL13413-WThe file does not exist. File = aa...aaDetailsThe

8. Messages667aa...aa: gzip command output messageActionSee the details in the message, and then remove the cause of the error. For information about

8. Messages668KAPL13504-IA symbolic link has been modified. Symbolic link name = aa...aaDetailsaa...aa: Name of the modified symbolic linkActionNone.K

8. Messages669Re-execute dlmupdatesysinit utility as a user with root permission. Refer to 7.8 dlmupdatesysinit Utility for Updating System Scripts.KA

8. Messages670KAPL13514-WUsage: /opt/DynamicLinkManager/bin/dlmupdatesysinitActionCheck for parameters, and then re-execute the dlmupdatesysinit utili

8. Messages671Check for and, if necessary, restore the system file indicated in the message. Next, execute the dlmupdatesysinit utility. Refer to 7.8

8. Messages672Reinstall an HDLM.KAPL13601-WThe audit log configuration file does not exist. Restart the HDLM Manager, and execute the "dlnkmgr vi

8. Messages673file.ActionContact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM.KAPL13605-WAn error occurred

8. Messages674KAPL13904-IFilter driver had been loaded. Filter driver's loading was skipped.ActionNone.KAPL13905-IHDLM manager had started. HDLM

8. Messages675/opt/DynamicLinkManager/bin/dlmmgr file does not exist or does not have executable permissions. Reinstall an HDLM.KAPL13909-WUsage: /opt

iii• HITACHI Gigabit Fibre Channel Board User's Guide• ServerConductor/DeploymentManager User's GuideConventions: AbbreviationsThis manual u

2. HDLM Functions46Table 2-11: Categories and Audit Events that Can Be Output to the Audit LogCategory Explanation Audit event Severity#1Message IDSta

8. Messages676KAPL13913-EA command has failed. Command = aa...aa, details = bb...bbDetailsaa...aa: Command that failedbb...bb: Message that the comman

8. Messages6778.14 KAPL15001 to KAPL16000KAPL15001-IThe registered value of ReserveKey was successfully displayed. Command Line = aa...aaDetailsaa...a

8. Messages678Detailsaa...aa: Name of the utility that the user executedKAPL15044-IProcessing to add devices to HDLM management succeeded. Command Lin

8. Messages679Detailsaa...aa: Name of the utility that the user executedKAPL15051-EAn attempt to create an initial RAM disk image file for using an HD

8. Messages680Detailsaa...aa: Name of the utility that the user executedKAPL15058-IProcessing to re-register the HDLM information was successful. Comm

8. Messages681cc...cc: Name of the utility that the user executedKAPL15065-EAn attempt to clear ReserveKey has failed on aa...aa SCSI device(s). Comma

8. Messages682aa...aa: Command that the user executedKAPL15106-ESetting up the operating environment failed. Command Line = aa...aaDetailsaa...aa: Com

8. Messages683KAPL15404-WThe HDLM Manager was executed by the user who does not have the authority.

8. Messages6848.15 Return Codes for Hitachi Command Suite Common Agent ComponentWhen an operation requested of HDLM from Global Link Manager terminate

8. Messages685ActionClick Refresh to update the host information, check the path status, and then retry the offline operation.1015DetailsThe Offline p

2. HDLM Functions47Setup of the operating environment was successful.6KAPL15105-ISetup of the operating environment failed.3KAPL15106-EAn attempt to d

8. Messages686maintenance contract for HDLM. For details on the DLMgetras utility, see 7.2 DLMgetras Utility for Collecting HDLM Error Information.102

8. Messages687HDLM Error Information.1034DetailsAn attempt to acquire information about the HDLM version or SP version has failed.ActionRe-execute the

8. Messages688Refresh the host information, and then perform the operation again. If the same error occurs again, execute the DLMgetras utility for co

8. Messages689utility, see 7.2 DLMgetras Utility for Collecting HDLM Error Information.

691AppendixesA. Notes on Linux Commands and FilesB. Troubleshooting Products That Use the Weak-Modules ScriptC. Functional Differences Between Version

A. Notes on Linux Commands and Files692A. Notes on Linux Commands and FilesThis section provides notes on Linux commands and files.A.1 Notes on the /p

A. Notes on Linux Commands and Files693commands show little difference before and after HDLM installation.Table A-1: Examples of Linux Command Executi

A. Notes on Linux Commands and Files694Figure A-2: Example of Executing the iostat CommandA.4 Notes on the mkfs CommandIf you are going to create a fi

A. Notes on Linux Commands and Files695A.6 Notes on the sar CommandExecuting the sar command with the -d or -A option does not display HDLM devices. T

2. HDLM Functions48Processing of the dlmcfgmgr -i command was successful.6 KAPL15044-IProcessing of the dlmcfgmgr -i command failed.3 KAPL15045-EProce

A. Notes on Linux Commands and Files696SCSI device 1..n: The SCSI device names which are being managed by the above HDLM device (for example, /dev/sda

B. Troubleshooting Products That Use the Weak-Modules Script697B. Troubleshooting Products That Use the Weak-Modules ScriptIf you use an HDLM device a

B. Troubleshooting Products That Use the Weak-Modules Script698root directory:Example when the boot loader is elilo and LVM is not used:# cat /etc/fst

B. Troubleshooting Products That Use the Weak-Modules Script699For device, enter the device you determined in step 1.In each of the following examples

B. Troubleshooting Products That Use the Weak-Modules Script700used.6. Delete the kernel parameter you added in step 2 from the boot loader configurat

B. Troubleshooting Products That Use the Weak-Modules Script701Example when LVM is not used:The underlined portion is the device that indicates the ro

B. Troubleshooting Products That Use the Weak-Modules Script702The underlined portion is a device of the volume group that indicates the root director

C. Functional Differences Between Versions of HDLM703C. Functional Differences Between Versions of HDLMThis section explains the functional difference

C. Functional Differences Between Versions of HDLM704using the dlmcfgmgr utility.C.5 Functional Differences Between Version 5.9.1 or Later and Version

C. Functional Differences Between Versions of HDLM705Table C-1: JRE/JDK Version Required for HDLM GUIC.8 Functional Differences Between Version 5.7.1

2. HDLM Functions49#1The severity levels are as follows:3: Error, 4: Warning, 6: Informational#2If you use Ctrl + C to cancel the DLMgetras utility fo

C. Functional Differences Between Versions of HDLM706C.11 Functional Differences Between Version 5.6.3 or Later and Versions Earlier Than 5.6.3Table C

D. Glossary707D. GlossaryThis glossary explains the terms used in this manual.Aautomatic failbackA function for checking the status of paths at regula

D. Glossary708DDev (Device)A logical division of an LU that HDLM controls and operates. A Dev is equivalent to a partition in Linux. In Linux, each LU

D. Glossary709failoverA function for switching to another normal path if there is an error in the current access path, thereby enabling the system to

D. Glossary710host LU numberA number assigned to a host LU. The host LU number is part of a path name.(See also: host LU, path name)hypervisorSoftware

D. Glossary711logical device fileA device file in the /dev directory.Note that the term logical device here is different from LDEV.LU (Logical Unit)A

D. Glossary712owner controller is called a non-owner path.When using the Lightning 9900 series, Lightning 9900V series, Hitachi USP, Universal Storage

D. Glossary713physical pathAn access path from a host to an LU. A path name is used to identify a physical path.QQEMUA virtual emulator available for

715IndexSymbols/proc/partitions files 692Aabbreviations defined iiiactive host 56adding new LU 371adding path to existing LU 374audit logcategories an

2. HDLM Functions50• You might need to perform operations such as changing the log size and backing up and saving collected log data, because the amou

Index716collectingerror info. with HDLM utility (DLMgetras) 43collecting HDLM installation error informationusing installgetras 43commandformat 398ove

Index717errorsdetected by HDLM 42management 39examiningmessage 392, 394Ffailback 25, 708failover 25, 709FC-SAN 7, 709, 8fdisk commands 694, 695feature

Index718HDLM resident processes 355HDLM utility 15HDLM-configuration definition utility 489HDLM-managed deviceoperations on 290Heartbeatcanceling sett

Index719Linux commands and files 692load balancing 19, 415, 710load balancing algorithms 23log collection levelvalues 416log filter 42logical device f

Index720cluster software 121file system 123kernel 70volume manager 122organization of this manual iOS 58update packages 339overviewcommand 398HDLM 1ow

Index721RHCMnotes 266SSAN (Storage Area Network) 713sar commands 695SCSI device 713set 414setting automatic mounting 286setting Heartbeat 262setting K

Index722utility for starting HDLM 510Vvendor ID 446vgrename commands 696view 431virtual environment 127volume managerwhen using Oracle Enterprise Linu

2. HDLM Functions51Filtering by category:The following categories can be specified:•StartStop• Authentication• ConfigurationAccess• All of the aboveFo

2. HDLM Functions52Common specification revision numberFixed to 1.1Serial number Serial number of the audit log messageMessage ID Message ID in KAPL15

2. HDLM Functions53#: The output of this item depends on the audit event.Example of the message section for the audit event An attempt to display HDLM

2. HDLM Functions542.13 Integrated HDLM management using Global Link ManagerBy using Global Link Manager, you can perform integrated path management o

2. HDLM Functions55Figure 2-16: Example System Configuration Using HDLM and Global Link Manager

ivHP XP128 HP StorageWorks XP128 Disk ArrayHP XP1024 HP StorageWorks XP1024 Disk ArrayHP XP10000 HP StorageWorks XP10000 Disk ArrayHP XP12000 HP Stora

2. HDLM Functions562.14 Cluster SupportHDLM can also be used in cluster configurations.For details about the cluster software supported by HDLM, see (

57Chapter3. Creating an HDLM EnvironmentThis chapter explains the procedure for setting up an HDLM environment and the procedure for canceling the env

3. Creating an HDLM Environment583.1 HDLM System RequirementsCheck the following before installing HDLM:3.1.1 Hosts and OSs Supported by HDLMHDLM supp

3. Creating an HDLM Environment591. Execute the following command to check which kernel architecture is used: # uname -mx86_64# The following shows th

3. Creating an HDLM Environment60Table 3-2: Red Hat Enterprise Linux AS4/ES4 Kernels Supported by HDLMKernel architecture#1KernelIA32#22.6.9-11.EL2.6.

3. Creating an HDLM Environment612.6.9-55.EL2.6.9-55.ELlargesmp2.6.9-67.EL2.6.9-67.ELlargesmp2.6.9-78.EL2.6.9-78.ELlargesmp2.6.9-89.EL2.6.9-89.ELlarge

3. Creating an HDLM Environment62#1Only kernels that are provided by OS distributors in binary format are supported.#2HDLM supports an environment whe

3. Creating an HDLM Environment63#1Only kernels that are provided by OS distributors in binary format are supported.#2HDLM supports an environment whe

3. Creating an HDLM Environment64HDLM supports an environment where an IPF kernel is installed on a system that uses an Intel CPU.#4Note the following

3. Creating an HDLM Environment65- glibc-RPM package version.i686.rpmRPM package version depends on the OS version you are using.Table 3-5: SUSE LINUX

vOracle RAC A generic term for:• Oracle9i Real Application Clusters• Oracle Real Application Clusters 10g• Oracle Real Application Clusters 11gP9500 H

3. Creating an HDLM Environment66HDLM supports an environment where an IPF kernel is installed on a system that uses an Intel CPU.#4HDLM supports an e

3. Creating an HDLM Environment67Note:This subsection describes the operating environment common to SUSE LINUX Enterprise Server 10.• Among the functi

3. Creating an HDLM Environment68#4All of the packages of SP1 for SUSE LINUX Enterprise Server 10 must be installed.#5All of the SP2 packages for SUSE

3. Creating an HDLM Environment69• Among the functions for SUSE LINUX Enterprise Server, HDLM only supports CFQ, and the default I/O scheduler functio

3. Creating an HDLM Environment70#2HDLM supports an environment where an IA32 kernel is installed on a system that uses an Intel CPU or AMD Opteron pr

3. Creating an HDLM Environment71Note the following in an EM64T/AMD64 environment:• HDLM supports an environment where an EM64T/AMD64 kernel is instal

3. Creating an HDLM Environment72Storage systems that are used must have a dual controller configuration. If you use them in a HUB-connected environme

3. Creating an HDLM Environment73HDLM on all the nodes that comprise the cluster. If different versions of HDLM are installed, the cluster system may

3. Creating an HDLM Environment742.6.9-34.EL2.6.9-34.ELsmp2.6.9-34.ELhugememLifeKeeper v6LifeKeeper v6 Update1LifeKeeper v6 Update2LifeKeeper v6 Updat

3. Creating an HDLM Environment752.6.9-42.EL2.6.9-42.ELsmp2.6.9-42.ELhugememLifeKeeper v6LifeKeeper v6 Update1LifeKeeper v6 Update2LifeKeeper v6 Updat