Hp Hitachi Dynamic Link Manager Software Licenses Manuel d'utilisateur

Hitachi Command SuiteDynamic Link Manager(for Solaris) User GuideMK-92DLM114-28Document OrganizationProduct VersionGetting HelpContents

online (Places Paths Online)...6-12Format...

a. Check the major number and minor number of HDLM raw devicesused by Oracle RAC 11g by executing the following command in eachnode:# ls -lL HDLM-raw-

Virtualization Environments Supported by HDLMHDLM supports LDoms in a virtualization environment.LDoms consist of a control domain, and one or more se

OS LDoms Disk LabelVolumeManagerFile SystemNone UFS VxFS ZFSZFS Y Y N YEFI None Y Y N YSVM Y Y N NZFS Y Y N YLegend:Y: Can be usedN: Cannot be usedMem

#3This value depends on the trace file settings. The maximum is 1000 MB.q = (t × n) ÷ 1024 (in MB),where:t is the size of the trace file (units: KB, d

Figure 3-1 Flow of HDLM Environment SetupHDLM Installation TypesThis subsection describes the following types of HDLM installation: newinstallation, u

Notes on Creating an HDLM EnvironmentThis section gives points to be noted when creating an HDLM environment.For points to be noted during operation o

Notes on Installation• You cannot edit the HDLM driver configuration definition file (/kernel/drv/dlmfdrv.conf). To change an HDLM-managed device to a

¢SVS is an HDLM management-target device.¢You are upgrading from HDLM 5.6.1 or earlier.When both these conditions are satisfied, the previous generati

/var/opt/hitachi/HNTRLib2/spool/hntr2n.log (n indicates a filenumber)Trace files after upgrade installation or re-installation:/var/opt/DynamicLinkMan

For details about the commands, refer to Solaris 10 or Solaris 11documentation. The following table shows Solaris zones supported inHDLM.Table 3-20 Su

To Display the Format of the delete Operation...6-81Parameters...

desired kernel mode. If you switch the kernel mode from 32 bits to 64bits when only the 32-bit version of HDLM is installed, you must reinstallHDLM af

You can use zoning of Fibre Channel switches or storage-system'sWWN security function to separately use HBA ports. You can also usepoint-to-point

you can keep the correspondence with the logical device file names onceinstallation is complete.4. When you execute the dlmsetconf utility for creatin

# umount /mntpt¢Clear the automatic mount setting.The following figure shows an example of how to edit the /etc/vfstab file.Figure 3-3 An example of h

Set Up the /kernel/drv/sd.conf FileWhen using an sd driver, depending on the HBA driver, you need to edit the /kernel/drv/sd.conf file to recognize th

¢To switch to the 64-bit kernel mode:If Solaris is running, execute the following command:# reboot -- "boot-device kernel/sparcv9/unix other-boot

the data. We also recommend that you specify info as the severity level forthe extended facility. This example shows how to specify the recommendedset

Set Up Solaris ClusterIf you are using Sun Cluster, before installing HDLM, perform the followingoperations to release the device group and Quorum dev

f. At another node in the same cluster, switch to become the superuser,and then place the node that was stopped in step 5 into themaintenance mode.The

In a Solaris 11 environment, if you cannot access the publisher of theSolaris package currently in use, HDLM installation fails. If this happens,you n

Format and Meaning of Message IDs... 8-3Terms Used in Messages and Message Explanations.

# zoneadm list -cv ID NAME STATUS PATH BRAND IP 0 global running /

sample_installhdlm.conf /any-directory/sample_installhdlm For details on the installation-information settings file and the installhdlmutility, see Th

In this example, the shaded portion shows information for each path ofthe device you are removing from HDLM management. Type in theappropriate device

# DVD-ROM-mount-point/installux.sh -f /any-directory/installation-information-settings-fileWhen executing the installhdlm utility# DVD-ROM-mount-point

# rm -rf /var/opt/DynamicLinkManager 8. Execute the following command to check whether HDLM has beeninstalled successfully:For Solaris 8, Solaris 9, o

Type y in response to the KAPL10242-I message displayed when youexecute the dlmsetconf utility.Information pertaining to LUs to which the physical pat

# /opt/DynamicLinkManager/bin/dlnkmgr view -sysHDLM Version : x.x.x-xxService Pack Version : Load Balance : on

the HDLM device) and iLU (the internal LU number). Then, compare thecorrespondence of the logical device file names and internal LUs that tookplace be

21. Based on the results of step 20, compare the logical device file namesfrom before and after the HDLM installation, and re-register the correctHDLM

In this example, the shaded portion shows information for each path ofthe device you are removing from HDLM management. Type in theappropriate device

PrefaceThis document describes how to use the Hitachi Dynamic Link Manager.□Intended audience□Product version□Release notes□Document revision level□Do

If no key is displayed, perform the steps beginning with step 11.7. Stop all nodes that comprise the cluster. On any one node, execute thefollowing co

cdrom/cdrom0 12. Perform the installation.¢If you are not performing an unattended installation of HDLM, executeeither of the following installation c

¢When a correct license key is entered, the installation programdisplays a message that indicates the license was installed.¢Take care that if you ent

HDLM on page 3-45 in Preparations for a New Installation of HDLM onpage 3-45.16. Execute the following dlmsetconf utility to create the HDLM drivercon

19. Stop all nodes that comprise the cluster.If one or more keys were displayed at step 6 and the node was started innon-cluster mode at step 8, execu

= view, completion time = yyyy/mm/dd hh:mm:ss# Nothing is displayed for Support Cluster even if you are using clustersoftware. However, the cluster-su

Table 3-22 Information displayed by the dlmlisthdev utility forassisting HDLM transitionsItem DescriptionOldHDevNameIndicates the HDLM 04-00 logical d

¢In a two-node configuration, execute the following command torelease the cluster installation mode:# /usr/cluster/bin/scconf -c -q reset32. On all no

host1# mount -g /dev/global/dsk/d5s0 /global/mntpt Using the HDLM Device Unconfiguration Function When Performing aNew Installation of HDLMYou can use

# /opt/DynamicLinkManager/bin/dlmsetconf -u 3. Restart the host with the reconfiguration option specified.Execute one of the following commands:¢# reb

Intended audienceThis document is intended for storage administrators who use HitachiDynamic Link Manager (HDLM) to operate and manage storage systems

immediately after the upgrade installation or re-installation hasfinished.¢Do not interrupt the upgrade installation or re-installation.¢When you inst

cdrom/cdrom0 4. Perform the installation.¢If you are not performing an unattended installation of HDLM, executeeither of the following installation co

¢When a correct license key is entered, the installation programdisplays a message that indicates the license was installed.¢Take care that if you ent

¢# reboot¢boot (at the ok prompt)When Sun Cluster is being used:Execute the following command at one of the nodes:# /usr/cluster/bin/scshutdown -g0 -y

Extended Least Blocks. See Setting Up the HDLM Functions on page3-140, and select the appropriate load balancing algorithm as required.¢Nothing is dis

In this configuration example, /dev/dsk/c2t50060E8010027A82d0s2and /dev/dsk/c2t50060E8010027A82d1s2 are sd or ssd devices.The following table shows a

To install HDLM to a host in which LDoms have been set:1. Log in to the control domain.2. Execute the ldm stop command to stop the guest domain.For ex

4. Execute the ldm rm-vdisk command to remove virtual disks from theguest domain.For example, to remove virtual disks vdisk1 and vdisk2 from the guest

/dev/dsk/c4t50060E8010027A82d0s2 and /dev/dsk/c4t50060E8010027A82d1s2 are HDLM device names after exporting.9. On the control domain, execute the ldm

Overview of Configuring a Boot Disk EnvironmentTo configure a boot disk environment in which HDLM manages the boot disk,prepare a separate disk that i

Document organizationThe following table provides an overview of the contents and organization ofthis document. Click the chapter title in the left co

• Slice 0: / (root) file system• Slice 1: Swap device and dump device• Slice 3: Sun Cluster global device file system• Slice 6: /usr file system• Slic

1. Allocate the LUs to be used by the boot disk in the post-migrationenvironment.2. Get Solaris to recognize the LUs to be used by the post-migration

Figure 3-9 Flow of setting up the boot disk environment when installingHDLM in the existing local boot disk environment1. Allocate the LUs to be used

3. Set the LU slices to be used by the post-migration boot disk.4. Complete the preparations for installing HDLM in the pre-migrationenvironment and t

Figure 3-10 Flow of setting up the boot disk environment when using anexisting boot disk environment without HDLM installed as the pre-migration envir

2. Get Solaris to recognize the LUs to be used by the post-migration bootdisk.3. Set the LU slices to be used by the post-migration boot disk.4. Compl

Figure 3-11 Flow of setting up the boot disk environment when building anew pre-migration environment1. Install Solaris in the pre-migration environme

¢To the slices of a single LU, allocate the Solaris file system, swapdevices, dump devices, Sun Cluster global device file system, andreplica of the S

# newfs /dev/rdsk/c8t50060E80004361D1d1s3 3. Mount the Solaris file system in the post-migration environment. If usingSun Cluster, also mount the Sun

/dev/dsk/c0t0d0s0 /dev/rdsk/c0t0d0s0 / ufs 1 no -/dev/dsk/c0t0d0s6 /dev/rdsk/c0t0d0s6 /usr ufs 1 no -/dev/did/dsk/d24s3 /dev/did/rdsk/d24s3 /global/.d

• Hitachi Adaptable Modular Storage Series User's Guide• Hitachi Simple Modular Storage Series User's Guide• Hitachi Unified Storage Series

As the boot device, you can specify any owner path of the boot disk.¢In Solaris 10 or Solaris 11:As the boot device, you can only specify a boot disk

NoteIn Solaris 8 or Solaris 9, find and make a note of the boot devicenames to specify in the OBP for all owner paths in case an erroroccurs on the pa

18. Back up the contents of both the pre-migration and post-migrationenvironments.Perform a backup so that you can take action in the following situat

For Solaris 10Figure 3-12 Creating a ZFS boot disk environment1. Copy the local boot disk environment from the ZFS file system to the LUs(SCSI device)

For Solaris 11Figure 3-13 Creating a ZFS boot disk environment1. Migrate the local boot disk environment in ZFS to an LU (HDLM device) inthe storage s

Copying the local boot disk environment to the LUs (SCSI device) in the storagesystemCopy the local boot disk environment to the LUs (SCSI device) in

In the following example, the boot disk environment name is zfsBE, andthe root pool name is rpool2.# lucreate -n zfsBE -p rpool2When the command termi

migration root pool. In addition, the pre-migration UFS file systemremains mounted in the post-migration environment.If you do not want to use the pre

3. Execute the zpool status command to confirm that the replacement hasbeen completed.# zpool statusWhen the replacement has been completed, the follo

# zpool create hdlmpool /dev/dsk/c6t50060E8010027A80d7s02. Execute the zpool status command and make sure that the root poolhas been created correctl

Physical capacity unit Value1 kilobyte (KB)1,000 (103) bytes1 megabyte (MB)1,000 KB or 1,0002 bytes1 gigabyte (GB)1,000 MB or 1,0003 bytes1 terabyte (

# eeprom boot-device=/pci@7c0/pci@0/pci@1/pci@0,2/SUNW,qlc@2,1/fp@0,0/disk@w50060e8010027a80,7:aFor how to set a boot device name, see step 11 in Sett

Before editing/dev/zvol/dsk/rpool/swap - - swap - no -After editing/dev/zvol/dsk/hdlmpool/swap -

3. Execute the zfs list command to make sure the data is copied to theroot pool (hdlmpool) in the ZFS boot disk environment after themigration.# zfs l

c6t50060E8010027A80d8s0-> ../../devices/pseudo/dlmndrv@1/dlmfdrv@w50060e8010027a80,8:a2. Execute the zpool replace command to change the current ZF

The following is an example when the post-replacement HDLM device isc6t50060E8010027A80d8s0:# installboot -F zfs /usr/platform/`uname -i`/lib/fs/zfs/b

PathID PathName DskName iLU ChaPort Status Type IO-Count IO-Errors DNum

In the following example, the boot disk environment name is zfsBE2 andthe name of the device on the built-in disk is c1t0d0s0:# luactivate zfsBE2# ins

2. Execute the zpool status command to check whether replacement iscomplete.# zpool status hdlmpool pool: hdlmpool state: ONLINE scan: resilvered 12

Creating a New Boot Environment1. Execute the zpool import command to check the ID of the root pool(rpool).# zpool import pool: rpool id: 64623162

# beadm create -p rpool -a solaris-25. Execute the beadm list command to check that the ZFS boot diskenvironment was created.Make sure that R appears

our existing Support Portal and support services by providing an area whereyou can get answers to non-critical issues and questions. Join theconversat

disk in the pre-migration environment to the ZFS boot disk in the post-migration environment.The following is an example:Before editing/dev/zvol/dsk/h

# zfs destroy –r rpool/export# zfs send -vRp hdlmpool/[email protected] | zfs receive -uvdF rpool3. Execute the zfs list command to check that data

# df / (rpool/ROOT/rboot):124234885 blocks 124234885 files /var (rpool/ROOT/rboot/var):124234885 blocks 124234885 files /export (

Figure 3-14 Migration flow when coping the file system from a boot diskenvironment to the local boot disk environment1. Boot the system from the pre-m

5. Assign device IDs.The following shows an example of executing the command: # /usr/cluster/bin/scdidadm -r 6. Notify the server of the new device I

rf -) 13. In the post-migration /etc/system file, delete the rootdev parameterthat specifies the HDLM physical device file name.14. Edit the post-migr

Before editingDUMPADM_DEVICE=/dev/dsk/c8t50060E80004361D1d1s1After editingDUMPADM_DEVICE=/dev/dsk/c0t0d0s117. Boot the system from the post-migration

¢VxVM¢Sun StorageTek Traffic Manager software (or, in Solaris 10, theSolaris multipathing software MPxIO)Configuring a Mirrored Boot Disk Environment

a. Remove HDLM after migration to a local boot disk environment byperforming the procedures in Removing HDLM from the Boot DiskEnvironment on page 3-1

Figure 3-15 Configuring a boot disk environment in which HDLM managesthe boot disk, from the local boot disk environmentMirroring a Boot Disk Environm

1Overview of HDLMHDLM is a software package that manages paths between a host and astorage system. HDLM is designed to distribute loads across multipl

• Slice 0: / (root) file system• Slice 1: Swap device and dump device• Slice 6: /usr file system• Slice 7: SVM state database1. Prepare another LU wit

7. Execute the metaroot command.# metaroot d10 8. Reboot the host.9. When the host starts, check the swap device and dump device. Thenexecute the moun

Stripe 0: Device Start Block Dbase State Reloc Hot Spare /dev/dsk/c8t50060E08000436D1d4s0

Installing HDLM and then Configuring the Environment1. Install HDLM by referring to Installing HDLM on page 3-45.2. Execute the dlmsetconf utility for

• Slice 7: SVM state database1. Decide the metadevice names.In this section, it is assumed that the metadevice names of the existingboot disks and the

# newfs /dev/md/rdsk/d300 5. Mount the Solaris basic file system of the post-migration environment.For example:# mount /dev/md/dsk/d100 /mnt0# mount /

To determine this path, perform the procedure in When the PathConfiguration Is Changed on page 4-17 in Precautions RegardingChanges to the Configurati

# swap -lswapfile dev swaplo blocks free/dev/md/dsk/d200 85,200 16 8409584 8409584# dumpadm Dump content: kernel pages

Size: 25190400 blocks (12 GB)d101: Submirror of d100 State: Okay Size: 25190400 blocks (12 GB) Stripe 0: Device

Backups of the environments are required for the following situations:¢If an error occurs in the post-migration environment:Reboot from the pre-migrat

© 2014 Hitachi, Ltd. All rights reserved.No part of this publication may be reproduced or transmitted in any form or by any means,electronic or mechan

What is HDLM?With the widespread use of data warehousing and increasing use ofmultimedia data, the need for high-speed processing of large volumes of

Figure 3-19 Current boot disks and boot disks after the migrationThe LU device names of the current boot disks are c8t50060E08000436D1d4and c8t50060E0

Boot disk File system Mirror Sub mirror/usr d300 d301d302After migration /(root)d10 d11d12swap d20 d21d22/usr d30 d31d322. Create metadevices on the s

# ufsdump 0f - /usr | (cd /mnt1; ufsrestore rf -) 7. Edit the file /etc/vfstab (/mnt0/etc/vfstab) of the boot disk after themigration to change the de

Figure 3-20 Booting from the post-migration environment11. When the host starts, confirm that the swap device and dump devicehave been correctly confi

# metainit -f d22 1 1 c6t50060E08000436D1d7s1# metattach d20 d22# metainit -f d32 1 1 c6t50060E08000436D1d7s6# metattach d30 d32 13. Copy the SVM stat

Remove HDLM by referring to Removing HDLM on page 3-184.Checking the Path ConfigurationHDLM functions, such as load balancing and failover, are only a

Setting Up HDLM FunctionsHDLM includes functions like the load balancing function, the automaticfailback function, the error logging function, the aud

Table 3-26 The default and recommended values for each functionFunction Default value Recommended valueLoad-balancingonThe Extended Least I/Osalgorith

The following is an example command to set load-balancing: # /opt/DynamicLinkManager/bin/dlnkmgr set -lb on -lbtype exlio When load balancing is enabl

If this condition is not satisfied, an error will occur and the warning messageKAPL01080-W will be output.If this happens, change any of the following

The ability to continue running operations between a host and storagesystem, even if there is a failure. This is also known as performing a failover.W

To enable intermittent error monitoring, set it to on. Otherwise, set it to off.When on is specified, you can use the -intvl and -iemnum parameters to

The higher this value is set, the more information that will be output. As theamount of log information to be output increases, it will take less time

You can specify a value (in kilobytes) from 100 to 2000000 for the error logfile size. The specified value is applied for HDLM manager logs.If each er

# /opt/DynamicLinkManager/bin/dlnkmgr set -systfs 2000 Specify the size of the trace file in kilobytes.Setting the Number of Trace FilesTrace files f

Table 3-30 Values Indicating Audit Log Data CategoriesValue ExplanationssAudit log events of the StartStop category are collected.aAudit log events of

Value Corresponding facility value in the /etc/syslog.conf filelocal7 or 23local7This example shows how to specify the audit log facility:# /opt/Dynam

(HNTRLib2) (/var/opt/hitachi/HNTRLib2/spool/hntr2n.log (n indicates afile number)).If a lot of integrated trace information is output, the older infor

Displaying the Hitachi Network Objectplaza Trace Library setupMenuTo display the Hitachi Network Objectplaza Trace Library setup menu:1. Log in as a u

the Buffer Size Per Monitoring Interval Duration on page 3-152. Therecommend value is 4096 for collecting an integrated trace.If you do not want to ch

2. Enter a larger size in New Size(KB).Set a new buffer size to fit the monitoring interval set in 5: IntervalTimer. The default value is 64. You can

1-4Overview of HDLMHitachi Dynamic Link Manager (for Solaris) User Guide

A screen to set the monitoring interval for the number of messagesoutput to the integrated trace file appears. The current value is displayedin Curren

If you do not want to change the maximum number of messages output,leave New Max(sec) blank, enter !, and then press the Enter key toreturn to the Hit

# /opt/hitachi/HNTRLib2/bin/hntr2mon -d & 7. Start the programs stopped in step 3.If you stopped programs other than HDLM in step 3, start them.Cr

Figure 3-21 An output example for the mount -p commandEdit the /etc/vfstab file as appropriate based on the settings output.The shaded portion indicat

To register an HDLM device:1. Make sure that VxVM recognizes HDLM devices.Execute the following commands sequentially to check whether VxVMrecognizes

NoteThe device name of the enclosure corresponding to the LU might varybefore and after installing HDLM. Make sure that you perform step 1to check the

NoteDo not add an HDLM device to a disk group registered as bootdg.Also, do not register a disk group containing an HDLM device inbootdg.4. If you are

Devices to Be Removed from VxVMThe following figure shows devices that are recognized by VxVM before theyare disabled.Figure 3-23 Devices That Are Rec

#For logical device files of HDLM devices, the number of such files to becreated is the same as the number of slices for one LU.The following figure s

the configuration example shown in Figure 3-25 When HBA ports on thealternate path differ from those on the primary path connected to the Hitachistora

2HDLM FunctionsThis chapter describes the various functions that are built into HDLM. Beforethe function specifications are explained though, this cha

The shaded portion, in the next step, is contained in the /etc/vx/vxvm.exclude file.2. Make an entry for the controller of the device you wish to remo

The devices displayed for HDevName (the shaded portion) are the HDLMdevices that must be recognized by VxVM. In the above example, twodevices, c5t0d0

If any non-HDLM devices are ENABLED, perform the procedure describedin Actions To Be Taken if an sd or ssd Device Has Not Been Suppressedfrom VxVM on

Figure 3-27 When the HBA Port of the Physical Path Connected to aHitachi Storage System Is the Same As the One Connected to a Third-partyStorage Syste

The shaded portion indicates the devices that need to be removed fromVxVM.2. Make an entry for the device you wish to removed from VxVM in thepaths se

The devices displayed for HDevName (the shaded portion) are the HDLMdevices that must be recognized by VxVM. In the above example, it isc4t0d0.5. Exec

from VxVM on page 3-170 of Removing Devices from VxVM on page3-160 to set up vxvm.exclude again.When the display resulting from the vxdmpadm command i

Example 1:The vxdisk command does not display HDLM devices but displays the sdor ssd devices corresponding to those HDLM devices.The vxdisk command di

The vxdmpadm command displays c3t0d0 and c4t1d0 in addition to theHDLM device c5t0d0, and the STATE column shows ENABLED.If sd or ssd devices have not

Figure 3-29 The /etc/vx/vxvm.exclude file (before editing)Figure 3-30 The /etc/vx/vxvm.exclude file (after editing)Among the non-HDLM devices in the E

□Collecting Audit Log Data□Integrated HDLM management using Global Link Manager□Cluster Support2-2HDLM FunctionsHitachi Dynamic Link Manager (for Sola

If the STATE column shows DISABLED, the device has been removed fromVxVM. The following shows an example of executing the command:If there is more tha

4. Verify that the VxVM disk group has been imported into only one of thenodes that constitute a cluster.If the VxVM disk group has been deported from

KAPL05023-E Could not process the IOCTL(00004D03).(0000000D:00000000)6. If the VxVM volume has not been created, create a VxVM volume in thedisk group

• Even if you use a local diskset or shared diskset, do not specify the -roption when changing the path configuration and executing thedlmsetconf util

host1# metadb -a -f c1t1d0s1 c1t1d0s3 c1t1d0s7 2. Create a local metadevice.Use the HDLM device (slice) to create a local metadevice (logical disk).Th

host1# metaset -s diskset1 -a -h host1 host2 3. Register a disk into the shared diskset.The following shows examples of executing the commands:When n

Setting Up SVMIf SVM is installed on an HDLM host, SVM uses the logical device file name ofthe HDLM device to access the HDLM-managed device. Therefor

Registering HDLM DevicesIf SVM is used, perform the following settings after installing HDLM, andregister the SVM volume.To Use a Local VolumeTo use a

Create these replicas on all hosts that use the shared diskset. Make surethat all the following conditions are satisfied for the creation-target disk:

host1# mkdir /diskset1host1# mount /dev/md/diskset1/dsk/d1 /diskset1 When using Sun Cluster:host1# mkdir -p /global/diskset1/d1host2# mkdir -p /global

Devices Managed by HDLMBelow is a list of devices that can or cannot be managed by HDLM. Thedevices that can be managed by HDLM are called HDLM manage

d: The total number of all HDLM devices#1If the number of paths differs depending on an HDLM device, use themaximum number for the calculation.#2The I

Preparations for HDLM RemovalPerforming Operations on HDLM-Managed DevicesTo perform operations on HDLM-managed disks:1. If necessary, back up the con

6. Use the following command to unmount all mount points that are usingHDLM: # umount mount-point 7. If HDLM devices are being used in Solaris 10 ZFS,

As the utility instructs, enter the name of the VxVM disk device group youwant to unregister.If the HDLM device has been configured as a Quorum device

Make sure that the node that is in the maintenance mode has thefollowing status:¢The node is in the Offline status.¢Both the current Quorum votes pres

For details on how to remove the VCS settings, refer to the VCSdocumentation.Remove VxVM SettingsIf you are using both HDLM and VxVM on the same host,

When using a local metadevice1. Execute the following command to unmount the file systemThe following shows an example of executing the command:host1#

The following shows an example of executing the command to delete SVMlocal volume d0.host1# metaclear d0When using a shared diskset1. Delete the share

¢When removing HDLM in a Solaris 11 environment, be sure toexecute /opt/DynamicLinkManager/bin/removehdlm. Do not use thepkg uninstall command to dire

Then, execute the following command at the ok prompt on all nodes:boot -r NoteWhile a node is starting, the message below may be output to theconsole

paths. The ID that HDLM assigns to each path (physical path) is called aAutoPATH_ID. A path is also sometimes called a managed object.The following fi

A virtual disk backend is a location where virtual disk data is stored. Adisk, disk slice, file, or volume (such as ZFS, SVM, and VxVM) can beused for

To remove HDLM from a host in which LDoms have been set:1. Log in to the control domain.2. Execute the ldm stop command to stop the guest domain.For e

For example, to remove virtual disks vdisk1 and vdisk2 from the guestdomain ldg2, execute the command as follows:# ldm rm-vdisk vdisk1 ldg2# ldm rm-vd

9. On the control domain, execute the ldm add-vdisk command to assignthe virtual disk backends to the guest domain.For example, to assign the virtual

Settings Needed After HDLM RemovalVxVM SettingsWhen using VxVM, execute the following command to confirm that theDEVICE column of the LUs previously m

1. Remove the device ID information of devices that do not exist. Thefollowing shows an example of executing the command: # /usr/cluster/bin/scdidadm

File System SettingsFor the file systems of the LUs that were managed by HDLM, specify settingsthat allow the Solaris sd or ssd driver to be mounted o

If you are unable to complete removal even though no programsother than HDLM are using HNTRLib2, contact your HDLM vendor ormaintenance company if the

¢Even if you attempt to remove HNTRLib2 when HNTRLib is installed,HNTRLib will not be removed. If no other programs are usingHNTRLib, delete it manual

4HDLM OperationThis chapter describes operating procedures for HDLM, including how tooperate HDLM and the HDLM manager, and how to change the configur

LU ConfigurationAfter you have properly installed HDLM, the LU configuration will change asfollows:Before the installation of HDLM:The host recognizes

Notes on Using HDLMThis section explains the notes on using HDLM and using the environment inwhich HDLM is installed. Make sure that you read this sec

The shaded portion indicates mapping from combinations of sd or ssd devicetypes and instance numbers to HDLM device logical device file names.Storage

If the host is started in single-user mode, the displayed path statusindicates an error even when the actual path status is normal. Therefore,before y

3. Execute the following command to set the HDLM logical device file namein the HDLM filter driver: # /opt/DynamicLinkManager/bin/dlmsetdevname 4. Exe

Maintenance Tasks on Devices Connected by Paths in the Boot DiskEnvironmentNote the following points when performing maintenance on devices connectedt

For details on the displayed items and their descriptions, see view (DisplaysInformation) on page 6-34.Changing the Status of PathsThis section explai

KAPL01061-I 3 path(s) were successfully placed Online; 0 path(s) were not. Operation name = online# 3. Check to see if the statuses of all the applica

# /opt/DynamicLinkManager/bin/dlnkmgr view -path Viewing LU InformationThis section explains how to display LU information by using the dlnkmgrcomman

The following shows an example of executing the view operation: # /opt/DynamicLinkManager/bin/dlnkmgr view -drvPathID HDevName Device LDEV000000 c6t5d

# /opt/DynamicLinkManager/bin/dlnkmgr view -path Viewing and Setting Up the Operating EnvironmentThis section explains how to display and set up the

Figure 2-2 LU Configuration Recognized by the Host After the Installationof HDLMThe following table lists and describes the components recognized by t

• Load balancing• Path health checking• Automatic failback• Intermittent error monitoring• Dynamic I/O path control• Displaying the physical storage s

Permanent -KAPL01001-I The HDLM command completed normally. Operation name = view, completion time = yyyy/mm/dd hh:mm:ss# For details on the displa

Elog Level : 3Elog File Size (KB) : 9900Number Of Elog Files : 2Trace Level : 0Trace File Size(KB)

# Among the displayed items, HDLM Manager, HDLM Alert Driver, and HDLMDriver indicate the HDLM component information.Also, you can view information fo

# /etc/init.d/dlmmanager stop The stop script that was set up during HDLM installation runs, and stops theHDLM manager.Execute the following dlnkmgr c

• Changing the HBA mounting slot• Installing or removing the FCode on an HBA• Changing the LU default controller for a storage system• Adding, deletin

• The -r parameter was specified when executing the dlmsetconf utility forcreating the HDLM driver configuration definition file.• The LUN configurati

Execute the following command to display the driver configurationinformation, and then refer to the instance field of the HDLM driverobtained in step

3. Return to the HDLM boot disk environment, following the proceduredescribed in Configuring a Boot Disk Environment on page 3-82.Dynamic Reconfigurat

• Adding a pathAdd a path to an existing LU.The following operations are not supported in the dynamic reconfiguration ofthe HDLM device. To enable the

Figure 2-3 Configuration of the HDLM ProgramsThe following table lists and describes the functions of these programs.Table 2-3 Function of HDLM Progra

new LUs, execute the dlmsetconf utility, and then execute the dlmcfgmgrutility for managing the HDLM configuration.• Without restarting the system, wh

• After you execute the dlmcfgmgr utility to add a new LU, when youexecute the path status display command (the view -path operation),the HDevName of

Figure 4-1 Example of executing the format commandIn the above execution example, when you specify an LU, the messageDisk not labeled. Label it now? w

In environments supporting dynamic reconfiguration of HDLM devices,execute the dlmcfgmgr utility for managing the HDLM configuration.HDLM device will

Have the HDLM drivers on all nodes in the cluster recognize the LU newlyrecognized by the node, and make the configuration the same for eachnode.To ad

4. Make sure that the key used for disk reservation has been registered forthe LU newly recognized by the node.Execute the following command on any no

10. Use the following dlmsetconf utility to create the HDLM driverconfiguration definition file (/kernel/drv/dlmfdrv.conf) and the HDLMdriver unconfig

NoteThe following message might be output to the console window orsyslog while the node is running:Could not read symbolic link for: /dev/rdsk/c3t5006

The following shows an example of executing the command. The shadedportion indicates the path accessing the LU recognized for the first timeby the HDL

20. Update the Sun Cluster global device namespace.Execute the following command: # /usr/cluster/bin/scgdevs 21. When using, as a Quorum device, an HD

ContentsPreface...xiiiIntended audience...

Program name Functions• Request path health checks and automatic failbacksto be performed• Collect error log dataHDLM alert driver Reports the log inf

¢A new LU cannot be added via dynamic reconfiguration when you areusing VxVM, because the host must be restarted in order to use (inVxVM) an LU that h

page 3-185. For details on how to remove SDS or SVM disksets, seeRemove SDS Settings on page 3-189 or Remove SVM Settings on page3-190 of Preparations

Installation of HDLM on page 3-45, and then execute the dlmsetconfutility.All sd or ssd devices connected to the host will be set as HDLM-manageddevic

11. Delete the device ID information for devices that do not exist.Execute the following command: # /usr/cluster/bin/scdidadm -C 12. Allocate the devi

# /usr/cluster/bin/scgdevs 15. When using, as a Quorum device, an HDLM device of an LU newlyrecognized for the first time by HDLM driver, set up the

•Changing an LU#• Changing the host LUN• Changing, adding, or deleting a CHA port• Changing a target ID• Adding or replacing a Fibre Channel switch• R

For details, see Set Up Solaris Cluster on page 3-51 in Preparations for aNew Installation of HDLM on page 3-45.6. If you are using VCS, unregister th

Execute the format command to make sure that the reconfiguredenvironment is recognized by Solaris.13. Move to the /opt/DynamicLinkManager/config direc

Execution example after a path is added by the addition of an HBA port:Check that a path for the same HBA port has been added:36a41,44> ### Device=

Use the following command to apply the settings in the HDLM driverunconfiguration definition file (/opt/DynamicLinkManager/config/dlmfdrv.unconf) to t

Figure 2-4 Position of the HDLM Driver and HDLM DevicesLogical Device Files for HDLM DevicesWhen you install HDLM, a logical device file to be used by

# /usr/cluster/bin/scconf -a -q globaldev=d4 For cluster configurations with two nodes, execute the following commandto clear the install mode for th

For details on how to perform these settings, refer to the documentationfor the HBA being used. You may need to restart the host, depending onthe HBA

When an LU is deleted via dynamic reconfiguration, path IDs becomeinconsecutive, as shown in this example. If you reboot the host, path IDsmight chang

pci@2/pci@0/pci@8/SUNW,qlc@0,1/fp@0,0/ssd@w50060e8010027a84,5 (ssd4127) onlineApr 2 16:03:36 shiga devfsadmd[89]: [ID 937045 daemon.error] failed to

ssd@w50060e8010027a80,2 ssd4119 000041 Online /devices/pci@400/pci@2/pci@0/pci@8/SUNW,qlc@0/fp@0,0/ssd@w50060e8010027a84

pci@400/pci@2/pci@0/pci@8/SUNW,qlc@0/fp@0,0/ssd@w50060e8010027a80,1 ssd12 000047 Online /devices/pci@400/pci@2/pci@0/p

about the LUs that are to be deleted but still contains information aboutother LUs.3. Execute the HDLM configuration management utility (dlmcfgmgr) to

Changing an HDLM-managed Device to a Non-HDLM-Managed DeviceTo change an HDLM-managed device to a non-HDLM-managed device:1. Check the LDEV informatio

Figure 4-5 Example of executing the format commandIn this example, the shaded portion indicates the path information of theLU to be managed by HDLM.In

Figure 4-6 The /opt/DynamicLinkManager/config/dlmfdrv.unconffile (before editing)Figure 4-7 The /opt/DynamicLinkManager/config/dlmfdrv.unconffile(afte

and for one of the Dev (slices) in that LU, the corresponding logical devicefile names of the sd or ssd devices are c2t1d1s0 and c3t2d1s0. In thiscase

Specifying Whether a Logical Unit Is To Be Managed by HDLM (WhenUsing Solaris Cluster)Changing an HDLM-Managed Device to a Non-HDLM-Managed DeviceNote

specifies that the LU indicated by that LDEV attribute is not to bemanaged by HDLM.The following figure shows examples of editing the HDLM driveruncon

Figure 4-10 Result output by executing the dlmvxexclude utilityFigure 4-11 Coding in the /etc/vx/vxvm.exclude fileThe shaded portion indicates the dev

NoteThe following message might be output to the console window orsyslog while the node is running:Unable to open '/dev/rdsk/c5t50060E80033A9902d

You can check the LU by using the format command. The following figureshows an example of the format command. The shaded portionrepresents an LU not m

16. When using a non-HDLM-managed device, as a Quorum device, set upthe Quorum device in any node on the cluster.The following shows examples of execu

Figure 4-13 Example of executing the format commandIn the above execution example, when you specify an LU, the messageDisk not labeled. Label it now?

Execute the following command on any node:# /usr/cluster/bin/scshutdown -g0 -y6. Start all nodes in the cluster in non-cluster mode.At the ok prompt,

Figure 4-15 The /opt/DynamicLinkManager/config/dlmfdrv.unconffile (after editing)The shaded portion indicates the text to be edited.NoteDo not make an

message is not output next time the node starts. For details, refer tothe Sun Cluster documentation.14. Execute the dlnkmgr command's view operat

Figure 2-5 Flow of I/O Data When the Load Balancing Function Is NotUsedWhen the load balancing function is not used, I/O operations converge onto asin

17. Delete the device ID information for devices that do not exist.Execute the following command: # /usr/cluster/bin/scdidadm -C 18. Allocate the devi

Set up the Quorum device: # /usr/cluster/bin/scconf -a -q globaldev=d4 Execute the following command to clear the install mode of a clusterwhen it con

You can check the LU and verify that the disk label is specified by usingthe format command. Figure 4-16 Example of executing the formatcommand on pag

If the key is displayed, place the LU under HDLM management byfollowing the steps from step 5 of Changing a Non-HDLM-Managed Deviceto an HDLM-Managed

6. Apply the settings in the HDLM driver unconfiguration definition file(/opt/DynamicLinkManager/config/dlmfdrv.unconf) to the HDLMdriver configuratio

# /usr/cluster/bin/scdidadm -ui 12. Update the Sun Cluster global device namespace.Execute the following command: # /usr/cluster/bin/scgdevs 13. When

Inheriting logical device names during storage system migrationThis subsection describes inheritance of logical device names during storagesystem migr

switches, cables between hosts and the storage system devices, and theHBA driver.6. Set up switches and other devices so that the logical units in the

Then, execute the dlmsetconf utility with the -u parameter specified toupdate configuration definition files. # /opt/DynamicLinkManager/bin/dlmsetconf

5TroubleshootingThis chapter describes how to properly use HDLM error information, and thenhow to resolve the problem, if an error occurs in HDLM. The

Figure 2-6 Flow of I/O Data When the Load Balancing Function Is UsedWhen the load balancing function is used, I/O operations are distributed viamultip

Information collected by using the DLMgetras utility forcollecting HDLM error informationImmediately after an error occurs, execute the DLMgetras util

The path name indicates a physical path. When you modify the systemconfiguration or replace a piece of hardware, you should check the pathnames to ide

Figure 5-1 Error Location When the KAPL08022-E Message is OutputThe following figure shows the troubleshooting procedure when theKAPL08022-E message i

The following shows the procedure for using the dlnkmgr command to handlea path error.Examining the MessagesExamine the message that is output to sysl

If any path cannot be placed online due to an error, the KAPL01039-Wmessage will appear. To ignore such paths and to continue processing, typey. To ca

¢The message output to the console by Solaris¢The message output to the console by the HBA driverIf an error occurs on one or more of the paths to the

Figure 5-3 Troubleshooting Procedure When a Program Error OccursThe following shows the procedure for handling a program error by using thedlnkmgr com

# /opt/DynamicLinkManager/bin/dlnkmgr view -sysIf the KAPL01012-E message appears as a result of executing the commandThe following shows the KAPL0101

5-10TroubleshootingHitachi Dynamic Link Manager (for Solaris) User Guide

6Command ReferenceThis chapter describes the HDLM command (dlnkmgr) and its operations.□Overview of the HDLM Command dlnkmgr□clear (Returns the Path S

remaining usable owner paths. When all owner paths cannot be used, loadbalancing is performed among the non-owner paths.For the example in Figure 2-7

Overview of the HDLM Command dlnkmgrThis section describes how to specify the HDLM command dlnkmgr and itssubcommands (called operations in HDLM).Comm

Operation FunctionsdeleteDynamically deletes a path that is an HDLM-management target. Fordetails, see delete (Deletes a Path Dynamically) on page 6-8

example, when you want to execute the command in a shell script orbatch file.Example # /opt/DynamicLinkManager/bin/dlnkmgr clear -pdst -sKAPL01001-I T

¢set¢view¢monitor¢add¢deleteIf you do not specify any operations, the help operation displays alloperations available for the dlnkmgr command.Examples

Valid value AutoPATH_ID { 000000 - 999999 }(Decimal) HBA_ID { 00000 - 99999 }(Decimal) CHA_ID { 00000 - 99999 }(Decim

|-pathid AutoPATH_ID|-device SCSI-device-name}[-s]To display the format of the offline operation/opt/DynamicLinkManager/bin/dlnkmgr offline -helpParam

# /opt/DynamicLinkManager/bin/dlnkmgr view -hba For details about how to execute the view operation to display the HBAport IDs, seeTo display HBA port

the Offline(C) status, enter y. Otherwise, enter n. [y/n]:yKAPL01061-I 2 path(s) were successfully placed Offline(C); 0 path(s) were not. Operation n

-device SCSI-device-nameUse this parameter to place offline all paths connected to the specifiedSCSI device.For SCSI-device-name, specify the value of

# /opt/DynamicLinkManager/bin/dlnkmgr offline -helpoffline: Format dlnkmgr offline [-path] { -hba HBAPortNumber.BusNumber |

¢Hitachi AMS2000 series#¢Hitachi SMS series#¢HUS100 series#¢HUS VM#: This storage system applies when the dynamic I/O path controlfunction is disabled

online (Places Paths Online)The dlnkmgr command's online operation places offline paths online. Specifythe paths to be placed online by specifyin

Specify the host port number and bus number of the target HBA port: thenumbers are found in the PathName field displayed using the viewoperation. Ente

Specify the current AutoPATH_ID of the target path, which is displayed byusing the view operation. For details on the view operation, see view(Display

Specify the current AutoPATH_ID of the target path, which is displayed byusing the view operation. For details on the view operation, see view(Display

parameter specification. To change the status of a specific LU, use the -lu and -pathid parameters to specify the path to the LU. To change thestatus

HBA_ID { 00000 - 99999 }(Decimal) CHA_ID { 00000 - 99999 }(Decimal)KAPL01001-I The HDLM command completed normally. Operation

|-elfs error-log-file-size|-elfn number-of-error-log-files|-systflv trace-level|-systfs trace-file-size|-systfn number-of-trace-files|-pchk {on [-intv

Item name Default value Recommended valueNumber of errorlog files2 2Trace level 0: Do not output any trace. 0: Do not output any trace.Trace file size

off: Disabled-lbtype {rr|exrr|lio|exlio|lbk|exlbk}Specify the algorithm to be used for load balancing.rr: The Round Robin algorithmexrr: The Extended

name = set, completion time = yyyy/mm/dd hh:mm:ss#-elfs error-log-file-sizeSpecify a value from 100 to 2000000 (in kilobytes) for the size of the erro

The paths are simply selected in order from among all the connectedpaths.¢Extended Least I/OsThe path that has the least number of I/Os being processe

Specify the size of the trace file in kilobytes. Specify a value from 100 to16000.By specifying both the trace file size and the number of trace files

When you change the checking interval, the new setting takes effectimmediately. When the checking interval is shortened and thechecking interval after

Specify the interval between path status checks. Specify a value from1 to 1440 minutes. The default is 1. Specify an interval appropriate foryour oper

If you omit the intermittent error monitoring interval or the number oftimes that the error is to occur, each setting is specified as follows:¢When th

During intermittent error monitoring, if you change the number oftimes that the error is to occur, the error count and the elapsed timemeasured since

SettingExecutable operation Result of operationAFB IEMSet IEM to on. • When a path is being monitored(during a period of conditionalintermittent error

#2Because automatic failback is off, intermittent error monitoring isdisabled.ExampleThe following example shows how to monitor for intermittent error

A temporary license key cannot be installed by using the dlnkmgrcommand's set operation.Example 1The following example shows how to update the li

-category [[ss] [a] [ca]|all]Specifies the categories of audit log data to be collected. The tablebelow lists and describes the values used for this s

Specifies the number of times the same path can be used for sequentialI/O operations when the extended Round Robin (exrr), Least I/Os(exlio), or Least

If a path in which an error has occurred recovers from the error, HDLM canthen switch back to that path. This is called a failback.Two types of failov

Table 6-10 Display items for which the display results of the viewoperation differ depending on the -pstv parameter specificationOperation Display Ite

| -iem off | -lic | -audlog on [ -audlv AudlogLevel ]

yyyy/mm/dd hh:mm:ss#view (Displays Information)The dlnkmgr command's view operation displays HDLM program information,path information, LU infor

[-pstv|-vstv][-stname][-srt {lu|cp}][-t]To display LU informationTo display LU information/opt/DynamicLinkManager/bin/dlnkmgr view -lu[-pstv|-vstv][-h

To display the format of the view operation/opt/DynamicLinkManager/bin/dlnkmgr view -helpParametersThis section describes the parameters for the view

Parameterand programinformationto bedisplayedItem DescriptionHDLM functionsettingsLoad BalanceSettings for load balancing• Setting status:on: Enabledo

Parameterand programinformationto bedisplayedItem Description• 4: Outputs all information.Trace FileSize(KB)Trace file size in kilobytesNumber OfTrace

Parameterand programinformationto bedisplayedItem Description• Checking intervalThe parentheses following the setting statusshows the checking interva

Parameterand programinformationto bedisplayedItem DescriptionFor example, when there are 100 days left untilthe license period (2006/08/21) expires, t

Parameterand programinformationto bedisplayedItem Descriptionextended loadbalancingIf you used Global Link Manager to set the number oftimes the same

For example, in Figure 2-8 Path Switching on page 2-17, the ownercontroller of LU is CHA0, and access to the LU is made only via the physicalpath (A).

= view, completion time = yyyy/mm/dd hh:mm:ss#Example 3The following example shows how to display information about the HDLMalert driver: # /opt/Dynam

# Example 8The following example shows how to display the number of times thesame path can be used for extended load balancing:# /opt/DynamicLinkMana

displayed according to the value specified in the -pstv parameter ofset operations.For information about the items that are displayed differentlydepen

Omits the title for each information item.ExampleThe following example shows how to display information about thepaths that access a host device.To di

Selectable items Sub-parametersDNum dnuHDevName hdIEP iepHBAPortWWN hbaportwwnPhysical-LDEV physVirtual-LDEV virtPhysical-DskName vidPhysical-iLU vidP

-stnameUse this parameter to display the model ID of the storage system inthe product ID element of the DskName field. When this parameter isomitted,

To display a summary of path information-path -cWhen you specify the -path parameter together with the -c parameter,only the PathID, DskName, iLU, CP,

displayed according to the value specified in the -pstv parameter ofset operations.For information about the items that are displayed differentlydepen

Displayed path informationTable 6-13 Displayed Path Information on page 6-50 describes the displayedpath information. The following explains the table

Displayed ItemDescriptionNosummarydisplayedSummarydisplayedIO-CountTotal I/O count for all the displayed paths, indicated by adecimal number. The maxi

Path Status Transition... 2-19The Online Path Status...

Automatic FailbacksWhen a path recovers from an error, HDLM can automatically place therecovered path back online. This function is called the automat

Displayed ItemDescriptionNosummarydisplayedSummarydisplayedThis number combined with the storage system name(shown in DskName) identifies the LU that

Displayed ItemDescriptionNosummarydisplayedSummarydisplayed• Online(D): The paths to the primary volume (P-VOL)in an HAM environment can be recovereda

Displayed ItemDescriptionNosummarydisplayedSummarydisplayedOne of the following values is displayed for each path:•-Indicates that intermittent error

Displayed ItemDescriptionNosummarydisplayedSummarydisplayed• For HUS VM indicated by a hexadecimal number. Thefirst two characters of iLU are the CU n

#1The path information is displayed only when a value is specified for the -path -item parameter.#2This storage system applies when the dynamic I/O pa

Model names of storagesystemsProduct IDWithout the -stnameparameterWith the -stnameparameter(Displays the followingfor the model ID)• Hitachi Universa

displayed. The sorting key is iLU and its configuration information isdisplayed for each LU.For details on the content of each displayed item, see Tab

0671 c6t5d1 sd75 000001 Online sd81 000007 Offline(E)0672 c6t5d2 sd76 000002 Online sd82 000008 Offline(C)KAPL01

Item that can be added Sub-parameterPhysical-ChaPort vidOrg-Product haOrg-SerialNumber haOrg-iLU haHaStat hastatAll items are displayedallFor details

Example 2When using Hitachi AMS2000 series, Hitachi SMS series, or HUS100 seriesand displaying LU information with DPC added to the display items: # /

However, if there is only one online path for a particular LU, that path cannotbe manually switched offline. Also, a path with an error that has not b

When the -c parameter is specified with the -lu parameter, a summaryof LU configuration information is displayed on one line. The total numberof paths

The following table lists the correspondence between the display itemsthat can be added by using the -item parameter and the parametervalues that can

Table 6-18 Displayed LU InformationDisplayed itemDescriptionNo summarydisplayedSummarydisplayedProductModel ID of the storage systemSerialnumberS/NSer

Displayed itemDescriptionNo summarydisplayedSummarydisplayedthe storage system. You can identify an actualLU by referencing iLU from the storage syste

Displayed itemDescriptionNo summarydisplayedSummarydisplayed• Host port number (hexadecimal number)• Bus number (hexadecimal number)• Target ID (hexad

Displayed itemDescriptionNo summarydisplayedSummarydisplayedseries, Hitachi AMS2000 series#3, Hitachi SMSseries#3, HUS100 series#3, or HUS VM all path

Displayed itemDescriptionNo summarydisplayedSummarydisplayedYou can identify the physical volume from thisinformation. If the volume is not virtualize

Displayed itemDescriptionNo summarydisplayedSummarydisplayedpaths and take resolve the problem for any pathsthat have an error status.Org-Product-- Fo

This storage system applies when the dynamic I/O path control function isdisabled.To display HBA port information-hbaUse this parameter to display inf

name = view, completion time = yyyy/mm/dd hh:mm:ss#The following shows the subsequent sub-parameters:-srt pbSorts the HBA port information by the host

If none of the paths accessing a single LU are in the Online status, one ofthe paths will be changed to the Online(E) status. All the paths thataccess

Item DescriptionOnlinePathsNumber of available paths in the displayed paths, indicated by adecimal number. When the value of Paths equals the value of

-tOmits the title for each information item.Table 6-21 To Display Corresponding Information About an HDLMDevice, sd or ssd Device, and LDEVItem Descri

# /opt/DynamicLinkManager/bin/dlnkmgr view -helpview: Format dlnkmgr view -sys [ -sfunc | -msrv | -adrv | -pdrv | -lic | -audlog |

If you perform dynamic reconfiguration of the HDLM device during themonitor operation, the KAPL01078-W message is displayed and the monitoroperation s

Table 6-22 Recommended values for the -intvl parameter when thereare 500 or more pathsNumber of paths(approximate)Recommended value specified for the

Item Description(4294967295). If the total I/O count reaches the maximumvalue, it is reset, and the count is re-started from 0.IO-ErrorsTotal I/O erro

Table 6-24 Items displayed as I/O information for each CHA portItem DescriptionChaIDCHA port IDProductModel ID of the storage systemSerialNumberSerial

dlnkmgr monitor -hbaid HBA_ID [-intvl Interval-Time] [-count Number-Of-Times] [-t] dlnkmgr monitor {

-sExecutes the command without displaying the message asking forconfirmation of command execution from the user. Specify this parameterif you want to

FormatTo Delete a Path Dynamically/opt/DynamicLinkManager/bin/dlnkmgr delete -path [-s]To Display the Format of the delete Operation/opt/DynamicLinkMa

Figure 2-9 Path Status TransitionsLegend:Online operation: Online operation performed by executing the dlnkmgrcommand's online operation.Offline

• Set up the storage system (remove the mapping between theinternal LU and the storage port LUN).• Terminate the connection between the storage port a

7Utility ReferenceThis chapter explains the utilities used by HDLM.□Overview of the Utilities□The DLMgetras Utility for Collecting HDLM Error Informat

Overview of the UtilitiesHDLM provides the following utilities:• The DLMgetras utility for collecting HDLM error informationWhen an error occurs, this

This utility outputs the file that has the same format as the VxVMmanagement target exclusion file that matches the definition in the HDLMdriver confi

When the host is restarted, a part of the information that was collected bythe DLMgetras utility will be cleared. If an error occurs, immediately exec

¢Do not specify a directory that contains the directory to which thecollected information is output. If you specify this directory, theDLMgetras utili

List of Collected Error InformationThe following illustrates the error information collected by executing theDLMgetras utility, which is explained sep

Output directory#1Files Explanationdlmcfgmgr1.logdlmcfgmgr2.logExecution log file of thedlmcfgmgr utility whichcollects the details oferror occurred d

Output directory#1Files Explanationopt/hitachi/HNTRLib/mmap hntrmmap.mmMemory mapped filecreated when HDLM04-00 or earlier is usedopt/hitachi/HNTRLib2

Output directory#1Files Explanationbfa.conf,emlxs.conf,fca-pci.conf,fcaw.conf,fcp.conf,fjpfca.conf,fjfcif.conf,fp.conf,jnic.conf,jnic146x.conf,jfca.co

#4One of the Offline(E) paths is changed to the Online(E) path.#5When an Offline(E) path exists among the paths that access the same LU.Figure 2-10 Pa

Output directory#1Files ExplanationmnttabFile system mountinformationsyslog.confsyslog output directorydefinitionrsyslog.confrsyslog definition file (

Output directory#1Files Explanationdlmgetomtrace.dmpIn-memory traceinformationdlmls-la.txtList of directories and filesrelated to the HDLMinstallation

Output directory#1Files Explanationpkginfo-l.txtList of packageinformationpkg-info.txtList of packageinformation (for Solaris11)pkg-history-l.txtList

Output directory#1Files Explanationwhat.txtOutput of what commandzfs-list.txt#6ZFS file systeminformation (outputresults of the zfs listcommand)zpool-

Output directory#1Files Explanationsystem-hdlm-manager:default.log.[0-9]system-hdlm-manager:default.logsystem-hdlm-initpath:default.log.[0-9]Log of th

Output directory#1Files ExplanationVCS_hasys-list.txtSystem information in theVCS clusterVCS_hagrp-display.txtService group informationVCS_hares-displ

Output directory#1Files ExplanationSC3.0#6(Not applicable) Sun Cluster informationcollection directorySC3.0_pkginfo.txtPackage informationSC3.0_scstat

The dlmcfgmgr Utility for Managing the HDLM ConfigurationThis utility makes the HDLM driver recognize the contents of the HDLM driverconfiguration def

Parameters-aApplies the contents of the HDLM driver configuration definition file (/kernel/drv/dlmfdrv.conf) to HDLM driver. The added LU becomes vali

¢If the HDLM driver configuration definition file (/kernel/drv/dlmfdrv.conf) contains the definition of a newly added LU, thedlmcfgmgr utility makes t

When you are using intermittent error monitoring, the path in which theintermittent error occurred is not automatically placed online even when thepat

¢If no change is made to the HDLM-managed devices when thedlmcfgmgr utility is executed, the utility outputs the message andterminates.¢You cannot con

Format/opt/DynamicLinkManager/bin/dlmlisthdev input-file-nameParametersinput-file-nameSpecifies, as an input file, the name of the output file that st

in HDLM 04-00 and those in the newer version of HDLM, and displays theresult in the standard output. The result of the command execution is asfollows:

The dlmsetboot Utility for Assisting Configuration of anHDLM Boot Disk EnvironmentThis utility automates part of the tasks for configuring a boot disk

configuration definition file (/kernel/drv/dlmfdrv.conf) and the HDLMnexus driver configuration definition file (/kernel/drv/dlmndrv.conf).The sd or s

Parameters-d output-directory-nameSpecifies the name of the directory to which the configuration definitionfile created by the dlmsetconf utility is t

LU is managed by HDLM is updated, and applied in the system when thereconfiguration option is specified to restart the host.When the -u parameter is s

The -d parameter is specified:A configuration definition file is created in the /tmp directory:# mkdir /tmp/dlmdir# /opt/DynamicLinkManager/bin/dlmset

dlmfdrv.unconf file exists either in the /opt/DynamicLinkManager/config directory or in a user-defined directory, the file is renameddlmfdrv.unconf.ba

• If you want HDLM to manage a device that is not currently managing,comment out the LDEV line (add a hash mark (#) at the beginning of theline) of th

determined to have an intermittent error if an error occurs 3 or more times in30 minutes.You can set up intermittent error monitoring by executing the

The dlmstart Utility for Configuring HDLM DevicesThis utility configures HDLM devices without needing to restart the hostimmediately after HDLM is ins

This example uses the existing dlmfdrv.conf content to configure theHDLM devices. # /opt/DynamicLinkManager/bin/dlmstart -t Note• To reconfigure HDLM

Format/opt/DynamicLinkManager/bin/dlmvxexclude [-d output-directory-name|-h ]Parameters-d output-directory-nameSpecifies the path name of the director

physical paths. Thus, executing the dlmvxexclude utility outputsentries for HDLM devices that have not actually been created.Entries for these devices

Used) on page 3-55, Performing a New Installation of HDLM (When SolarisCluster Is Being Used) on page 3-62, or Performing an Upgrade Installationor Re

[INSTALLATION_SETTINGS] sectionThis section defines operation information for the installhdlm utility. The[INSTALLATION_SETTINGS] section must be spec

Key name#1Explanation#2Required oroptional?Maximum length(characters)For newinstallationForupgradeinstallation or re-installationdriver_configSpecify

#1Only one key name and value can be specified on each line.#2Specifying an invalid value causes an error.#3When you perform a new installation of HDL

Key name#1Explanation#2Required oroptional?Maximumlength(characters)Requiredfor newinstallationRequiredforupgradeinstallation or re-installationlio: T

Key name#1Explanation#2Required oroptional?Maximumlength(characters)Requiredfor newinstallationRequiredforupgradeinstallation or re-installationerror_

Figure 2-11 Action What Will Happen When an Intermittent Error Occurson a PathWhen an Intermittent Error Does Not OccurIf an error does not occur in t

Key name#1Explanation#2Required oroptional?Maximumlength(characters)Requiredfor newinstallationRequiredforupgradeinstallation or re-installationoff: D

Key name#1Explanation#2Required oroptional?Maximumlength(characters)Requiredfor newinstallationRequiredforupgradeinstallation or re-installationabout

#5The checking interval can be set regardless of whether the dynamic I/Opath control function is enabled or disabled.The following is an example of an

Note• If VxVM is installed on the host, do not use the -r option or the -t option.Perform the installation without specifying any options.After the in

installux.sh Utility for HDLM Common InstallerThis utility determines what OS HDLM will be installed on, and installs thecorresponding version of HDLM

Log fileThe installux.sh utility outputs execution information to the logfile /var/tmp/hdlm_installux_sh.log. If the hdlm_installux_sh.log logfile alr

# reboot -- -rAt the ok prompt, execute the following:boot -r • If HDLM devices are used in ZFS or in SVM, do not use the -r option orthe -t option.Pe

8MessagesThis chapter describes the format and meaning of the message IDs, and alsothe terms used in the messages and message explanations. For detail

□Return Codes for Hitachi Command Suite Common Agent Component8-2MessagesHitachi Dynamic Link Manager (for Solaris) User Guide

Before Viewing the List of MessagesThis section explains the following information that is needed to locatemessages and understand the explanations in

As shown in Figure 2-12 What Will Happen When an Intermittent Error DoesNot Occur on a Path on page 2-25, normally, the count for the number oftimes t

• HDLM management targetKAPL01001 to KAPL02000MessageIDMessage Text ExplanationKAPL01001-IThe HDLM command completednormally. Operation name =aa...aa,

MessageIDMessage Text Explanationretry. For details on the helpoperation, see help (Displays theOperation Format) on page 6-4.KAPL01006-WA necessary p

MessageIDMessage Text ExplanationExecute the view operation of theHDLM command (dlnkmgr) tocheck whether the HDLMmanager has started. Start theHDLM ma

MessageIDMessage Text Explanationfor the relevant HBA port, andthen retry. For details on theview operation, seeview (DisplaysInformation) on page 6-3

MessageIDMessage Text Explanationdetails on the view operation,seeview (Displays Information)on page 6-34.KAPL01019-WThe target path was not found.Ope

MessageIDMessage Text ExplanationTerminate unnecessaryapplications to increase theamount of free memory, and thenretry.KAPL01023-WThe last Online path

MessageIDMessage Text ExplanationIf you want to continueprocessing of the onlineoperation of the HDLM commandfor other paths, enter y. If youwant to t

MessageIDMessage Text ExplanationThe specified operation is not anoperation of the HDLM command.aa...aa: Specified operation nameActionUse the help op

MessageIDMessage Text ExplanationIf you want to execute onlineprocessing, enter y. If you wantto terminate processing, enter n.Before you execute thep

MessageIDMessage Text ExplanationIf you want to continueprocessing the offline operationof the HDLM command for otherpaths, enter y. If you want toter

When a User Changes the Intermittent Error InformationThe following might be reset when a user changes any of the values set forthe intermittent error

MessageIDMessage Text Explanationenter y. If you want to terminateprocessing, enter n.KAPL01058-WThe specified parameter value isnot needed. Operation

MessageIDMessage Text Explanationaa...aa: Number of paths wherethe online/offline operationwas successful (decimal(base-10) number)bb...bb: Online, On

MessageIDMessage Text ExplanationNone.KAPL01069-WThe entered license key is invalid. DetailsThe entered license key is invalid.ActionEnter a valid lic

MessageIDMessage Text ExplanationRe-install HDLM.KAPL01076-IThe permanent license has beeninstalled.DetailsYou need not install a licensebecause a per

MessageIDMessage Text ExplanationKAPL01082-EThere is no installable license keyin the license key file. File name =aa...aaDetailsThere is no useable l

MessageIDMessage Text ExplanationKAPL01089-EOne of the following was executedat the same time as an HDLMcommand set -lic operation:another set -lic op

MessageIDMessage Text Explanationto be put online has beenreserved by another path.aa...aa: Path IDbb...bb: Code showing reason forerrorActionUse the

MessageIDMessage Text ExplanationHDLM error information to collectthe error information, and thencontact your HDLM vendor ormaintenance company if you

MessageIDMessage Text ExplanationActionNone.KAPL01101-WThe target HBA port was not found.Operation name = aa...aaDetailsThe HBA having the HBA_IDspeci

MessageIDMessage Text Explanationor -chaid parameter wasspecified. To collectively placemultiple paths Online, enter y. Tonot collectively place themO

Notes on Hardware Settings... 3-39Notes on Installation...

User operationNumber oferrors and timepassed sinceerrormonitoringstartedInformationabout pathsnot subject toautomaticfailbackmonitoring is beingperfor

MessageIDMessage Text ExplanationKAPL01115-WThe audit log configuration filecannot be opened. Execute the"dlnkmgr view -sys -audlog"command

MessageIDMessage Text ExplanationKAPL01120-WA storage system model ID couldnot be displayed. Details = aa...aa,bb...bbDetailsA storage system model ID

MessageIDMessage Text ExplanationKAPL01134-IThe target paths are alreadyOnline or Online(S).DetailsThe specified paths are already inthe Online or Onl

MessageIDMessage Text ExplanationUse the view operation of theHDLM command (dlnkmgr) tocheck the setting for the host,storage, and LUs. For details on

MessageIDMessage Text ExplanationKAPL01162-IA path was added. (path ID =aa...aa, storage = bb...bb, iLU =cc...cc)DetailsThis message displaysinformati

MessageIDMessage Text ExplanationTo set all paths to Online orOnline(D), enter y. To cancel theoperation, enter n. Before youexecute the processing, y

MessageIDMessage Text ExplanationKAPL01171-IThe target paths are alreadyaa...aa or bb...bb.DetailsThe specified paths are already inthe Online, Online

MessageIDMessage Text Explanationaa...aa: virtActionWhen specifying virtual storageinformation as a display item,enable the Physical Storage View.KAPL

MessageIDMessage Text Explanationaa...aa: API trace errorinformationActionExecute the DLMgetras utility forcollecting HDLM errorinformation, and then

MessageIDMessage Text ExplanationThis information is required forresolving problems.aa...aa: API trace errorinformationActionExecute the DLMgetras uti

connected to non-owner paths, we recommend that you use path healthchecking to detect errors. This enables the system to use the most up-to-datepath-s

MessageIDMessage Text Explanationyour HDLM vendor or themaintenance company if there isa maintenance contract forHDLM. For details on theDLMgetras uti

MessageIDMessage Text ExplanationUse the dlnkmgr set operationto return options settings back towhere you had them.If the KAPL04033-W message isnot ou

MessageIDMessage Text Explanationa maintenance contract forHDLM. For details on theDLMgetras utility, see TheDLMgetras Utility for CollectingHDLM Erro

MessageIDMessage Text ExplanationExecute the DLMgetras utility forcollecting HDLM errorinformation, and then contactyour HDLM vendor or themaintenance

MessageIDMessage Text ExplanationHDLM Error Information on page7-3.KAPL04024-CA critical error occurred in the HDLMmanager. (aa...aa)DetailsThis infor

MessageIDMessage Text ExplanationKAPL04029-EThe emergency license expired. ActionInstall a permanent license.KAPL04030-EThe temporary license has alre

MessageIDMessage Text ExplanationKAPL04036-IThe path health check for the pathaa...aa was executed. Number oferror paths = bb...bbDetailsaa...aa: Numb

MessageIDMessage Text ExplanationKAPL04054-IThe owner controller will now berevised. (number of LUs = aa...aa)Detailsaa...aa: number of targeted LUsAc

MessageIDMessage Text Explanationnot started or contains an error,execute the DLMgetras utility forcollecting HDLM errorinformation, and then contacty

MessageIDMessage Text Explanationthe DLMgetras utility to collect errorinformation, and then contact yourvendor or maintenance company.Refer to the HD

Error ManagementFor troubleshooting purposes, HDLM collects information and stores it into logfiles. The error information to be collected can be filt

MessageIDMessage Text Explanationinstructions how to execute theDLMgetras utility.Check the message of the HDLMcommand (dlnkmgr) or theHDLM manager, a

MessageIDMessage Text ExplanationKAPL05041-EThe contents of the configurationdefinition file (dlmfdrv.conf) areinvalid. (Instance = aa...aa) Executeth

MessageIDMessage Text ExplanationContact the HDLM vendor, or themaintenance company if youhave a maintenance contract forHDLM.KAPL05412-WAn attempt to

MessageIDMessage Text Explanationhow to execute the dlmsetconfcommand.bb...bb: Instance number(decimal number)ActionCheck whether the path iscorrectly

MessageIDMessage Text Explanationproblems, this message issometimes output in Oracle ASMenvironments. If this is the case,you can ignore this messageb

MessageIDMessage Text ExplanationRefer to the HDLM User's Guide forinstructions how to execute theDLMgetras utility.name of the HDLM device to th

MessageIDMessage Text Explanationbb...bb: Target memory size(hexadecimal number)ActionCheck whether the HDLM driverhas started normally. If it hasnot

MessageIDMessage Text ExplanationActionCheck the message of the HDLMcommand (dlnkmgr) or HDLMmanager, and then take theappropriate action. If you do n

MessageIDMessage Text ExplanationKAPL06014-ECould not write emergencyinformation into the emergencyinformation buffer. (aa...aa:bb...bb)DetailsUrgent

MessageIDMessage Text Explanationcc...cc: Detailed information 2(decimal (base-10) number)dd...dd: Detailed information 3(decimal (base-10) number)Act

Types of Collected LogsHDLM collects information on detected errors and trace information in theintegrated trace file, trace file, error logs, log for

MessageIDMessage Text Explanation¢When a path error isdetected by a path healthchecking or the onlineoperation:Displays0x000F0000(Fixed).¢When a path

MessageIDMessage Text Explanationhh...hh: Host device name(same as HDevName of view -path)ActionThere could be an error in thepath. See What To Do for

MessageIDMessage Text ExplanationKAPL08027-EA path was excluded from the itemssubject to automatic failback. PathID= aa...aaDetailsA path was excluded

KAPL09001 to KAPL10000MessageIDMessage Text ExplanationKAPL09002-EThe disk does not have sufficientfree space.DetailsThe file system of the installati

MessageIDMessage Text ExplanationNetwork Objectplaza Trace Library2 fails again, contact your HDLMvendor or the maintenancecompany if there is a maint

MessageIDMessage Text Explanation/opt/HDVM/agent/classes/com/Hitachi/soft/HiCommand/DVM/agent/module/HDLMManager.class/opt/HDVM/agent/docroot/webstart

MessageIDMessage Text ExplanationNone.KAPL09077-IThe temporary license wasinstalled. The license expires onaa...aa.DetailsA temporary license was inst

MessageIDMessage Text Explanationnow stop. Obtain a valid licensekey, and then re-install HDLM.license key was entered threetimes in a row.ActionObtai

MessageIDMessage Text ExplanationInstall a permanent license at alater time.KAPL09091-EA fatal error occurred in HDLM.The system environment is invali

MessageIDMessage Text ExplanationAlternatively, cancel theinstallation, save the correctlicense key file in the designateddirectory, and then re-execu

Log name Description Output destinationfile /etc/syslog.conf or /etc/rsyslog.conf are collected. #We recommend that you configurethe system so that in

MessageIDMessage Text Explanationresult of a user operationoccurred.ActionExecute the utility for collectingHDLM error information(DLMgetras), and acq

MessageIDMessage Text Explanationaa...aa: One of the following filenames:¢/kernel/drv/dlmfdrv.conf¢/opt/DynamicLinkManager/config/dlmfdrv.unconf¢/kern

MessageIDMessage Text ExplanationKAPL09149-EAn attempt to update the file hasfailed. File name = aa...aa, Details= bb...bb. Please contact productsupp

MessageIDMessage Text Explanationby HDLM, edit the HDLMdriver unconfigurationdefinition file (/opt/DynamicLinkManager/config/dlmfdrv.unconf) andre-exe

MessageIDMessage Text ExplanationKAPL09190-WThe installation informationsettings file is not specified.DetailsThe installation-informationsettings fil

MessageIDMessage Text ExplanationCheck the absolute path of thelicense key file, and then re-installHDLM.KAPL09205-EThere is no license key file. TheH

MessageIDMessage Text Explanationaa...aa: installhdlm, pkgadd,dlnkmgr, dlmsetconf, ordlmstartActionNone.KAPL09212-Eaa...aa ended abnormally. Detailsaa

MessageIDMessage Text ExplanationThe /var/tmp directory doesnot exist. Preparethe /var/tmp directory, andthen retry the operation.If the error code is

MessageIDMessage Text ExplanationMake sure that sufficient freecapacity exists for the /var/tmpdirectory. If the capacity isinsufficient, allocate the

MessageIDMessage Text Explanationpermission, re-executeinstallhdlm.If aa...aa isinstallhdlm_analysis:The correct location ofinstallhdlm_analysis is th

In syslog, the HDLM messages on and above the level set by the userconfigured in /etc/syslog.conf or /etc/rsyslog.conf are collected. It isrecommended

MessageIDMessage Text ExplanationSpecify the revised installationinformation settings file, and thenretry the operation.KAPL09221-WThe definition of t

MessageIDMessage Text ExplanationSpecify the revised installationinformation settings file and thenretry the operation.KAPL09229-WThe definition of th

MessageIDMessage Text ExplanationSpecify the revised installationinformation settings file and thenretry the operation.KAPL09232-WThe composition of t

MessageIDMessage Text ExplanationKAPL09235-EThe log file cannot be output to itsdestination because theenvironment is invalid. Error Code= aa...aaDeta

MessageIDMessage Text Explanationexists. If the directory exists,delete it by using the followingcommand:# rm -rf /var/opt/DynamicLinkManagerHowever,

MessageIDMessage Text Explanationinstallation utility(dlminstcomp).If the error code is 5:Install the prerequisite JDK,and then execute the HDLMcompon

MessageIDMessage Text ExplanationContact your HDLM vendor or yourmaintenance company if you havea maintenance contract for HDLM.KAPL09248-WA parameter

MessageIDMessage Text Explanationremovehdlm: DVD-ROM-mount-point/HDLM_Solaris/IPS/remove_scripts/removehdlmKAPL09290-IA user operation endedremovehdlm

MessageIDMessage Text ExplanationAn SP cannot be applied becauseHDLM is not installed on thesystem.ActionCheck whether HDLM has beencorrectly installe

MessageIDMessage Text ExplanationInstallation of SP (aa...aa) isstopped.aa...aa: The version of the SP tobe installedbb...bb: The version of theinstal

following table describes the categories of audit log data that Hitachi storage-related products can collect.Table 2-8 Categories of Audit Log Data th

MessageIDMessage Text Explanation¢Confirm that the OS commandexists, and that you have theproper permission.KAPL09604-EA system error occurred. Theins

MessageIDMessage Text ExplanationThe first parameter must be adirectory to which collectedinformation will be output.aa...aa: First parameterActionChe

MessageIDMessage Text ExplanationActionCheck whether the specified filefor defining the information to becollected exists, and checkwhether you have a

MessageIDMessage Text ExplanationDLMgetras Utility for CollectingHDLM Error Information on page7-3.KAPL10010-WA root directory has been specified.Line

MessageIDMessage Text ExplanationKAPL10012-WThe specified file or directory doesnot exist. Line = aa...aa, Value =bb...bbDetailsThe specified file or

MessageIDMessage Text ExplanationDLMgetras utility, see TheDLMgetras Utility for CollectingHDLM Error Information on page7-3.KAPL10014-WYou lack read

MessageIDMessage Text ExplanationA root "/" cannot be specified in adirectory to which collectedinformation is output.ActionCheck the parame

MessageIDMessage Text ExplanationNone. For details on theDLMgetras utility, see TheDLMgetras Utility for CollectingHDLM Error Information on page7-3.K

MessageIDMessage Text Explanationbb...bb: cq command outputmessageActionAn error occurred during copyingof the file to be collected. Theuser environme

MessageIDMessage Text ExplanationNone.KAPL10050-IThe utility for collecting HDLM errorinformation started. Start time =aa...aa (GMT aa...aa)DetailsThe

Category Explanation• Updating account settings, such as adding and deletingaccounts• Setting up security• Viewing or updating audit log settingsMaint

MessageIDMessage Text Explanationaa...aa: Name of the configurationdefinition fileActionCheck the system configuration.KAPL10223-EAn error occurred wh

MessageIDMessage Text ExplanationKAPL10229-EInternal processing error. DetailsAn internal processing erroroccurred.ActionInternal processing error. Co

MessageIDMessage Text ExplanationRemove the error by referencingErrno, and then retry.KAPL10236-ECould not allocate memory. Errno= aa...aa (bb...bb)De

MessageIDMessage Text ExplanationActionRemove the error by referencingErrno, and then retry.KAPL10242-ITo configure HDLM, device files ofsd/ssd device

MessageIDMessage Text ExplanationActionCheck the system configuration.KAPL10251-WAn attempt to retrieve informationfor the directory aa...aa failed.Fu

MessageIDMessage Text ExplanationProcessing will stop because anincorrect value was entered threeor more times for the messageconfirming the execution

MessageIDMessage Text Explanationproperly connected to the server.If there are any errors, removethe error, and then re-execute thecommand.If the disk

MessageIDMessage Text Explanationcommand differs from the outputof the dlnkmgr view -pathcommand.ActionCheck the input file, and thenretry. For detail

MessageIDMessage Text ExplanationConfirm the existence of the fileand access permission. If there isno problem, contact your HDLMvendor or maintenance

MessageIDMessage Text ExplanationKAPL10371-WThe HDLM support disk informationdoes not exist in the configurationfile (dlmfdrv.conf). Check thesystem c

Category Explanation Audit eventSeverity#1Message IDStartup of the I/Oinformationmonitoring functionwas successful.6 KAPL15112-IStartup of the I/Oinfo

MessageIDMessage Text Explanationdlmcfgmgr Utility for Managingthe HDLM Configuration on page7-17.KAPL10376-EThe device (aa...aa) could not beopened.

MessageIDMessage Text Explanationdlmcfgmgr Utility for Managingthe HDLM Configuration on page7-17.KAPL10382-WThere is no instance of the HDLMnexus dri

MessageIDMessage Text Explanationthe LDEV name has changed,reboot the host.ActionIf the path configuration of the LUshown by the LDEV name haschanged,

MessageIDMessage Text ExplanationKAPL10391-EThe output file (aa...aa) could notbe opened. ErrorCode = bb...bb(cc...cc). Resolve the error byreferencin

MessageIDMessage Text Explanationto complete execution and then runthe command.cannot be simultaneouslyexecuted for multiple processes.ActionWait unti

MessageIDMessage Text ExplanationActionIt is not necessary to execute thiscommand. For details on thedlmvxexclude utility, see Thedlmvxexclude Utility

MessageIDMessage Text ExplanationCreation of the VxVMConfiguration File on page 7-31.KAPL10708-ENo authority to executedlmvxexclude.DetailsYou do not

MessageIDMessage Text ExplanationA valid entry does not exist inthe /kernel/drv/dlmfdrv.conffile.ActionCheck the system configurationand then execute

MessageIDMessage Text Explanationaa...aa: Directory nameActionSpecify the correct directory.KAPL10717-EThe directory specified by the -doption does no

MessageIDMessage Text Explanationmessage confirming execution ofthe dlmvxexclude utility forassisting creation of the VxVMconfiguration file.ActionRet

Category Explanation Audit eventSeverity#1Message IDenvironment wassuccessful.Setup of theoperatingenvironment failed.3 KAPL15106-EAn attempt todispla

MessageIDMessage Text Explanationaa...aa: Physical-device file pathof the sd or ssd device thatcorresponds to the HDLM devicefor which the path was de

MessageIDMessage Text ExplanationNone.KAPL10752-IThe dlmsetboot utility completedsuccessfully. End time = aa...aaDetailsThe dlmsetboot utility complet

MessageIDMessage Text ExplanationKAPL10756-EThe entered value is invalid. Thedlmsetboot utility processing willnow stop. Execute the utility again.End

MessageIDMessage Text ExplanationKAPL10760-EThe post-migration boot disk deviceis not an HDLM managementtarget. (aa...aa)DetailsThe post-migration boo

MessageIDMessage Text Explanation#The following information isoutput:/usr/sbin/installboot/usr/sbin/newfs/usr/sbin/mount/usr/sbin/ufsdump/usr/sbin/ufs

MessageIDMessage Text ExplanationKAPL10768-IThe post-migration boot disk deviceconfiguration was updated.(aa...aa) (bb...bb)DetailsThe post-migration

MessageIDMessage Text Explanationaa...aa: Physical device path ofthe sd or ssd device associatedwith the HDLM device for which apath was successfully

MessageIDMessage Text Explanationaa...aa: SerialNobb...bb: iLuActionNone.KAPL10776-IFor LU information that is not in thestorage migration information

MessageIDMessage Text ExplanationKAPL10780-EThe storage migration informationdefinition file is invalid. It is empty.(aa...aa)DetailsThe storage migra

MessageIDMessage Text ExplanationKAPL10784-WThe storage migration informationdefinition file does not exist.(aa...aa)DetailsThe storage migration info

Creating a New Boot Environment... 3-112Configuring the Post-Migration ZFS Boot Disk Environment.

Category Explanation Audit eventSeverity#1Message IDd] command wassuccessful.Processing of thedlmvxexclude [-d] commandfailed.3 KAPL15027-EThe status

MessageIDMessage Text ExplanationKAPL10863-EThe aa...aa service cannot beenabled.DetailsA service cannot be enabled.aa...aa: Service nameActionCheck t

MessageIDMessage Text ExplanationNoneKAPL10868-ELog in as the root user before usingthe dlmstart utility.DetailsLog in as the root user beforeusing th

MessageIDMessage Text ExplanationExecute the DLMgetras utility forcollecting HDLM error information,and then contact your HDLMvendor or the maintenanc

MessageIDMessage Text ExplanationMake sure that the other instanceof dlmstart finished successfully.KAPL10880-EAn attempt to generate a linkfailed. Th

MessageIDMessage Text Explanationaa...aa: LDEV namebb...bb: Filter pathActionIf you want to use the LU, rebootthe host.KAPL10953-EDeletion of the path

MessageIDMessage Text Explanation¢Get HDLM Alert Driver Status¢Get SNMP Trap Information¢Set SNMP Trap Information¢Set LU Load Balance¢Get Path Status

MessageIDMessage Text Explanation¢Get Local Time¢Add Path Information¢Delete Path Information¢Set Storage IdentificationInformationActionNone.KAPL1190

MessageIDMessage Text ExplanationKAPL11905-EAn unexpected error occurred. DetailsAn exception occurred duringprocessing on the host.ActionExecute the

MessageIDMessage Text ExplanationManager, and execute the "dlnkmgrview -sys -audlog" command andcheck the setting.ActionRestart the HDLM Man

MessageIDMessage Text ExplanationContact your HDLM vendor or themaintenance company if there isa maintenance contract forHDLM.KAPL13606-WAn error occu

¢If the severity specified by the HDLM command's set operation differsfrom the severity specified by the configuration file /etc/syslog.confor /e

MessageIDMessage Text ExplanationKAPL15027-EAn attempt to output informationabout exclusion from VxVMmanagement has failed. CommandLine = aa...aaDetai

MessageIDMessage Text ExplanationKAPL15109-IInformation about HDLM-management targets wassuccessfully displayed. CommandLine = aa...aaDetailsaa...aa:

MessageIDMessage Text ExplanationKAPL15401-IHDLM Manager successfully started. -KAPL15402-ECould not start the HDLM manager. -KAPL15403-IHDLM Manager

Message ID ExplanationThe target path of the offline operation is the last,remaining path connected to the device and therefore,cannot be placed in th

Message ID Explanationyou have a maintenance contract for HDLM. For details onthe DLMgetras utility, see The DLMgetras Utility forCollecting HDLM Erro

Message ID ExplanationRefresh the host information, and then perform theoperation again. If the same error occurs even afterremoving the reservation,

Message ID Explanationcontact your HDLM vendor or maintenance company if thereis a maintenance contract for HDLM.For details on the DLMgetras utility,

Message ID ExplanationRefresh the host information, check the path status, andthen perform the operation again.1045 DetailsA parameter is invalid.Acti

8-142MessagesHitachi Dynamic Link Manager (for Solaris) User Guide

ASun Cluster 3.2 CommandsThis section describes the Sun Cluster 3.2 commands.□Sun Cluster 3.2 CommandsSun Cluster 3.2 CommandsA-1Hitachi Dynamic Link

¢All of the aboveFor details on how to specify audit log settings, see Setting Up the HDLMFunctions on page 3-140.Audit Log Data FormatsThe following

Sun Cluster 3.2 CommandsThe table below shows the correspondence between Sun Cluster 3.1commands and Sun Cluster 3.2 commands used in this manual. For

Commands for Sun Cluster 3.1 Commands for Sun Cluster 3.2scswitch -F -D device-group-name cldevicegroup offline device-group-namescswitch -S -h node-n

A-4Sun Cluster 3.2 CommandsHitachi Dynamic Link Manager (for Solaris) User Guide

BFunctional Differences BetweenVersions of HDLMThis section explains the functional differences between newer and olderversions of HDLM.□Functional Di

Functional Differences Between Version 6.1 or Later andVersions Earlier Than 6.1In a new installation of HDLM, the default load balancing algorithm ha

Acronyms and abbreviationsThe following acronyms and abbreviations might be used in this guide.AALArbitrated LoopAPIApplication Programming InterfaceA

DDBMSDatabase Management SystemDevDeviceDMPDynamic MultipathingDNSDomain Name ServerDRDynamic ReconfigurationFFCFibre ChannelFC-SPFibre Channel Securi

HHBAHost Bus AdapterHDevHost DeviceHLUHost Logical UnitHTTPHypertext Transfer ProtocolII/OInput/OutputIPInternet ProtocoliSCSIInternet Small Computer

LULogical UnitLUNLogical Unit NumberMMPMaintenance PackNNASNetwork Attached StorageNFSNetwork File SystemNTPNetwork Time ProtocolOOBPOpenBoot PROMOSOp

SSANStorage Area NetworkSCSISmall Computer System InterfaceSLPRStorage Logical PartitionSMTPSimple Mail Transfer ProtocolSNMPSimple Network Management

Item#ExplanationAudit event type Event typeAudit event result Event resultSubject ID for auditevent resultDepending on the event, an account ID, proce

ZZFSZettabyte File System#A B C D E F G H I J K L M N O P Q R S T U V W X Y ZAcronyms-6Hitachi Dynamic Link Manager (for Solaris) User Guide

GlossaryThis glossary explains the terms used in this manual.Aautomatic failbackA function for checking the status of paths at regular intervals, and

CLPR(Cache Logical Partition)A function supported by the Hitachi USP series, Universal Storage Platform V/VM series,Virtual Storage Platform series, V

FfailbackA function for placing the status of a path recovered from an error into the Onlinestatus, and then switching the access path to the path tha

hostA generic term for both servers and clients.host deviceA logical area in a host LU.(See also: host LU, host device name)host device nameA name ass

- The Least Blocks algorithm- The Extended Least Blocks algorithmlocal boot disk environmentAn environment in which a boot disk is located on the host

owner pathA path that passes through an owner controller for an LU in the Thunder 9500V Series,or Hitachi AMS/WMS series is in use. A path that passes

an LU that has been reserved is given only to the host that issued the reservation, sothe LU cannot be accessed from multiple paths (coming from multi

# A B C D E F G H I J K L M N O P Q R S T U V W X Y ZGlossary-8Hitachi Dynamic Link Manager (for Solaris) User Guide

IndexSymbols/etc/system filesetup 3-49/kernel/drv/sd.conf filesetup 3-48Aactive host 2-43add 6-79addinga new logical unit 4-22adding path to existing

For large-scale system configurations using many hosts running HDLM, theoperational load for managing paths on individual hosts increases with thesize

offline 6-6online 6-12set 6-17view 6-34commands of HDLM (dlnkmgr)help 6-4monitor 6-74componentsHDLM system components 2-4core logic component 2-8Criti

functions of HDLM 2-1Ggetras.tar.Z 7-6Global Link Manager 2-41glossary Glossary-1HHAM environment Glossary-3handlingpath error 5-3HBA 2-4HBA (Host Bus

installation 3-45performing an upgrade installation or re-installation 3-73preparations for a new installation of HDLM 3-45preparations for an upgrade

Oobtainingpath information 5-5program information 5-8offline 2-16, 6-6offline(C) status 2-20offline(E) status 2-20online 2-16, 6-12online status 2-19o

/kernel/drv/sd.conf file 3-48HDLM functions 3-140integrated traces 3-149Sun Cluster 3-51VxVM (before installing HDLM) 3-50single-user modeoperation 4-

Hitachi Dynamic Link Manager (for Solaris) User Guide

Hitachi Data SystemsCorporate Headquarters2845 Lafayette StreetSanta Clara, California 95050-2639U.S.A.www.hds.comRegional Contact InformationAmericas

For details on cluster software supported by HDLM, the supported Solarisversion, and usable volume management software, see Combinations ofCluster Sof

2-44HDLM FunctionsHitachi Dynamic Link Manager (for Solaris) User Guide

3Creating an HDLM EnvironmentThis chapter describes the procedures for setting up an HDLM environmentand the procedure for canceling those settings.Ma

□Creating File Systems for HDLM (When Volume Management Software IsNot Used)□Setting Up VxVM□Setting Up SDS□Setting Up SVM□Setting Up VCS□Removing HDL

HDLM System RequirementsCheck the following before installing HDLM:For the requirements for using HDLM in an HAM environment, see the releasenotes of

Devices to Be Removed from VxVM...3-161Removing Devices from VxVM on a Controller Basis...

Table 3-2 JDK required for linking with Global Link ManagerOS JDK packageSolaris 8 or Solaris 9 • JDK 1.4.2_15 or later (32 bit version)• JDK 5.0_11 o

The applicable storage systems require a dual controller configuration. Ifyou use the system in a hub-connected environment, you must setunique loop I

Cluster Software Supported by HDLMThe following table lists the cluster software versions supported by HDLMwhen building a cluster configuration.Table

• When combining configurations by using VxVMVxVM 4.1#1 or VxVM 5.0#1HDLM-managed boot disks do not support a mirrored boot disk configurationincorpor

OS Cluster Volume managerSun Cluster 3.1 (9/04)#1NoneSDS 4.2.1Sun Cluster 3.1 (8/05)#1NoneSDS 4.2.1VCS 5.0#2 #3NoneVxVM 5.0Solaris 9 None NoneSVM#4VxV

OS Cluster Volume managerSVM #4 #9VxVM 5.0Oracle Solaris Cluster 3.3#10 #13NoneSVM#5 #6 #8 #9VxVM 5.1#5 #8VCS 5.0#3None#14VxVM 5.0#5 #8 #15VCS 5.1#14N

¢Multi-owner disksets¢Diskset import¢Automatic (top down) volume creation#7In a configuration that uses a driver other than the Oracle HBA driver(othe

The I/O fencing function can be used only when Hitachi USP series,Universal Storage Platform V/VM series, or Virtual Storage Platform seriesstorage sy

Table 3-6 Programs required to create an Oracle RAC 10g environment(For Solaris 8 or Solaris 9)ConfigurationProgram RemarksConfiguration1OS Solaris 8

ConfigurationProgram Remarksthe documentation forOracle RAC 10g.Configuration3OS Solaris 9 --Oracle RAC 10g Oracle 10g Database10.1.0.4.0--Cluster Ora

Initializing HDLM When the Host Is Started in Single-User Mode...4-4Tasks that Can Be Performed in Single-User Mode...

ConfigurationProgram Remarksof the Oracle database.In Oracle RAC 10g,HDLM devices can beused following thesame procedures asfor disk devices.For detai

ConfigurationProgram RemarksCluster Oracle Clusterware10.2.0.1.0--VolumeManagerASM • ASM is bundled withOracle RAC 10g.• ASM is used as the diskmemory

ConfigurationProgram RemarksOracle RAC10gOracle 10g Database10.2.0.2.0Only two-nodeconfigurations aresupported.Cluster Sun Cluster 3.1 8/05 andOracle

ConfigurationProgram Remarksprocedures as for diskdevices.For details on how toinstall ASM, refer to thedocumentation forOracle RAC 10g.Configuration

ConfigurationProgram Remarksrefer to the documentationfor Oracle RAC 10g.Configuration 13OS Solaris 10 --Oracle RAC10gOracle 10g Database10.2.0.4.0Onl

ConfigurationProgram RemarksOracle database filesand recovery files. Forthe disk device used byASM, specify the SunCluster device ID.For details on ho

ConfigurationProgram RemarksCluster Oracle Solaris Cluster 3.3and Oracle Clusterware10.2.0.4.0VolumeManagerNone (Specify an HDLM rawdevice from the Su

Target program Patch ID Timing for applying108773-18 or later108921-16 or later108940-53 or later108987-13 or later108989-02 or later108993-19 or late

#It is necessary only when using Oracle RAC 10g 10.1.0.4.0.Note• When a host and an Oracle RAC 10g voting disk are connected bymultiple paths, HDLM pe

• 600 seconds (default value of Oracle Clusterware)Table 3-12 Formula for Calculating MISSCOUNTStorage system typeFormula for obtaining the value ofMI

Specifying Whether a Logical Unit Is To Be Managed by HDLM (When Using SolarisCluster)...

For details on how to change MISSCOUNT and DISKTIMEOUT, contact thecompany with which you have a contract for Oracle Support Services.Note that when y

c. For the created alias device file, set the owner, group, and accesspermission mode by using the following command. The owner, group,and access perm

ConfigurationProgram RemarksVolumeManagerASM • ASM is bundled withOracle RAC 11g.• ASM is used as the diskmemory area for theOracle database files and

ConfigurationProgram RemarksVolumeManagerNone (Specify an HDLMraw device)--Configuration 6OS Solaris 10 --Oracle RAC 11g Oracle 11g Database11.1.0.6.0

ConfigurationProgram Remarksdocumentation forOracle RAC 11g.Configuration 9OS Solaris 10 --Oracle RAC 11g Oracle 11g Database11.1.0.7.0--Cluster Oracl

ConfigurationProgram RemarksOracle RAC 11g Oracle 11g Database11.2.0.1.0--Cluster Oracle Grid Infrastructure11.2.0.1.0--VolumeManagerASM • ASM is bund

ConfigurationProgram RemarksVolumeManagerASM • ASM is bundled withOracle GridInfrastructure.• ASM is used as the diskmemory area for theOracle databas

ConfigurationProgram Remarksrecovery files. In OracleRAC 11g, HDLM devicescan be used as diskdevices by following theusual procedures forHDLM devices.

ConfigurationProgram RemarksFor details on how to useASM, refer to thedocumentation forOracle RAC 11g.#You must apply MP3 or later.Note• When a host a

the change, use the following table to obtain the value to be specified,and then change the current value to a value equal to or greater thanthe value