Hitachi Dynamic Link Manager Software User's Guide (for Solaris(R))3000-3-F05-50(E)
viGMT Greenwich Mean TimeGUI Graphical User InterfaceHBA Host Bus AdapterHDev Host DeviceHLU Host Logical UnitHTTP Hypertext Transfer ProtocolI/O Inpu
3. Creating an HDLM Environment78Table 3-11: Formula for Calculating DISKTIMEOUTFor details on how to change MISSCOUNT and DISKTIMEOUT, contact the co
3. Creating an HDLM Environment79 Execution example:# ls -lL /dev/rdsk/c10t50060E8005271760d5s0crw-r----- 1 root sys 307, 1608 date/time /d
3. Creating an HDLM Environment804. Execute the following command for the created alias device file and check that the major number, minor number, own
3. Creating an HDLM Environment81Volume Manager ASM • ASM is bundled with Oracle RAC 11g.• ASM is used as the disk memory area for the Oracle database
3. Creating an HDLM Environment82Cluster Sun Cluster 3.2 and Oracle Clusterware 11.1.0.6.0Volume Manager None (Specify an HDLM raw device)--Configurat
3. Creating an HDLM Environment83Volume Manager ASM • ASM is bundled with Oracle RAC 11g.• ASM is used as the disk memory area for the Oracle database
3. Creating an HDLM Environment84#You must apply MP3 or later.Note When a host and an Oracle RAC 11g voting disk are connected by multiple paths, HDL
3. Creating an HDLM Environment85Table 3-13: Formula for Calculating MISSCOUNTIn addition to the value of MISSCOUNT shown above, also change the value
3. Creating an HDLM Environment86In Oracle RAC 11g, for the following devices, device name should be matching between the nodes:• voting disk• Oracle
3. Creating an HDLM Environment87#In this example, a device file for RAC whose major number is 307 and minor number is 1608 is created.3. For the crea
viiConventions: DiagramsThis manual uses the following conventions in diagrams:Conventions: Fonts and symbolsFont and symbol conventions are classifie
3. Creating an HDLM Environment88Only domains including I/O domains that manage the HBAs connected to HDLM-managed storage are supported.• HDLM cannot
3. Creating an HDLM Environment893.1.7 Memory and Disk Capacity RequirementsThis subsection explains the memory and disk capacity requirements.(1) Mem
3. Creating an HDLM Environment90up. 3.1.8 The Number of Paths Supported in HDLMTable 3-17: Number of LUs and Paths Supported in HDLM lists the number
3. Creating an HDLM Environment913.2 Flow for Creating an HDLM EnvironmentSet up the environment to use HDLM as follows.• The installation procedure i
3. Creating an HDLM Environment92Figure 3-1: Flow of HDLM Environment Setup
3. Creating an HDLM Environment933.3 HDLM Installation TypesThis subsection describes the following types of HDLM installation: new installation, upgr
3. Creating an HDLM Environment943.4 Notes on Creating an HDLM EnvironmentThis section gives points to be noted when creating an HDLM environment.For
3. Creating an HDLM Environment953.4.2 Notes on Installation You cannot edit the HDLM driver configuration definition file (/kernel/drv/dlmfdrv.conf)
3. Creating an HDLM Environment96• The HDLM driver unconfiguration definition file (/opt/DynamicLinkManager/config/dlmfdrv.unconf)However, if both the
3. Creating an HDLM Environment97Integrated trace files after re-installation: /var/opt/hitachi/HNTRLib2/spool/hntr2n.log (n indicates a file number)T
viii• General font conventions• Conventions in syntax explanationsThese conventions are described below.General font conventionsThe following table li
3. Creating an HDLM Environment98• To allocate the HDLM device for each LU, execute the following command: zonecfg:zone1:device> set match=/dev/rds
3. Creating an HDLM Environment99• Configuring a boot disk environment• Setting up HDLM functions• Setting up an integrated trace#• Creating a file sy
3. Creating an HDLM Environment100encapsulation while creating a disk group with an HDLM device or adding an HDLM device to a disk group, the KAPL0801
3. Creating an HDLM Environment1013.5 Installing HDLMWhen you install HDLM, Hitachi Network Objectplaza Trace Library (HNTRLib2) will also be installe
3. Creating an HDLM Environment1026. Unmount the device.If the device is mounted, unmount it. Also, if the device is set to be mounted automatically w
3. Creating an HDLM Environment103Figure 3-3: An example of how to edit the /etc/vfstab fileComment the shaded portions out by placing a hash mark (#)
3. Creating an HDLM Environment104(4) Set Up the /kernel/drv/sd.conf FileWhen using an sd driver, depending on the HBA driver, you need to edit the /k
3. Creating an HDLM Environment105 To boot at the ok prompt, execute the following command:boot boot-device kernel/unix other-boot-options• To switch
3. Creating an HDLM Environment106of "Error" or higher are to be output.Make sure that the /etc/syslog.conf file contains the following conf
3. Creating an HDLM Environment107For details, refer to the VxVM documentation.5. Remove any sd or ssd disk to be managed by HDLM from VxVM control.Fo
ixConventions: KB, MB, GB, and TBThis manual uses the following conventions:• 1 KB (kilobyte) is 1,024 bytes.• 1 MB (megabyte) is 1,0242 bytes.• 1 GB
3. Creating an HDLM Environment108• If an sd or ssd device to be managed by HDLM has been set as a Quorum device, perform the following procedures to
3. Creating an HDLM Environment109- The node is in the Offline status.- Both the current Quorum votes present and Quorum votes possible are 0.The foll
3. Creating an HDLM Environment1103.5.2 Preparation for Performing an Unattended Installation of HDLMAn unattended installation is an installation in
3. Creating an HDLM Environment111Notes• The license key file can be saved as a user-specified directory or a file name. However, this license key fil
3. Creating an HDLM Environment112In this example, the shaded portion shows information for each path of the device you are removing from HDLM managem
3. Creating an HDLM Environment113After confirming that the KAPL09211-I message has been output, execute the following command to delete the installat
3. Creating an HDLM Environment114# pkginfo -l DLManager PKGINST: DLManager NAME: Dynamic Link Manager CATEGORY: system ARCH: sparc
3. Creating an HDLM Environment115For details on how to perform this setting, see 3.5.5 Using the HDLM Device Unconfiguration Function When Performing
3. Creating an HDLM Environment116Path Health Checking : on(30)Auto Failback : on(1)Intermittent Error Monitor : offHDLM Mana
3. Creating an HDLM Environment117these devices.19. If you are using VxVM, execute the following command to confirm that the DEVICE column of the LUs
3. Creating an HDLM Environment11821. Based on the results of step 20, compare the logical device file names from before and after the HDLM 6.5.1 inst
3. Creating an HDLM Environment1192. Log in to Solaris as a user with root permissions.3. Execute the format command to make sure that the sd or ssd d
3. Creating an HDLM Environment1206. Make sure that the key to be used for disk reservation has been registered with the device to be managed by HDLM.
3. Creating an HDLM Environment1210x40235c52000000020x40235c52000000010x40235c5200000003Attempting to remove all keys from the disk...Scrubbing comple
3. Creating an HDLM Environment122# pkgadd -d DVD-ROM-mount-point/HDLM_Solaris DLManager• If you are performing an unattended installation of HDLM, ex
3. Creating an HDLM Environment123DynamicLinkManager directory exists. If the /var/opt/DynamicLinkManager directory exists, execute the following comm
3. Creating an HDLM Environment12417. Specify the devices that are to be excluded from management by HDLM, if there are any.This step is unnecessary i
3. Creating an HDLM Environment12520. With the reconfiguration option specified, start all nodes comprising the cluster in cluster mode, at the same t
3. Creating an HDLM Environment126name = view, completion time = yyyy/mm/dd hh:mm:ss#Nothing is displayed for Support Cluster even if you are using cl
3. Creating an HDLM Environment127Table 3-20: Information displayed by the dlmlisthdev utility for assisting HDLM transitions describes the items show
xiContentsPreface iIntended readers ...iOrganiza
3. Creating an HDLM Environment12830. Update the Sun Cluster global device namespace. Execute the following command:# /usr/cluster/bin/scgdevs 31. To
3. Creating an HDLM Environment129these devices.To use an HDLM-managed device with a file system created by using volume management software, perform
3. Creating an HDLM Environment130dlmfdrv.unconf file (before editing) and Figure 3-5: Example of an /opt/DynamicLinkManager/config/dlmfdrv.unconf fil
3. Creating an HDLM Environment131• # reboot -- -r• boot -r (at the ok prompt)4. Execute the following command to verify that the settings were applie
3. Creating an HDLM Environment132• When you install HDLM while the 32-bit kernel mode is being used, only the 32-bit version of HDLM will be installe
3. Creating an HDLM Environment133The following shows an example of executing the command for mounting the DVD-ROM:# mkdir /cdrom/cdrom0# mount -F hsf
3. Creating an HDLM Environment134hdlm_license is not already saved, a message is output asking whether a user-specified license key file has been sav
3. Creating an HDLM Environment135Then, execute the following command at the ok prompt in all nodes:boot NoteYou must restart the host immediately aft
3. Creating an HDLM Environment136load-balancing setting was previously on. The load-balancing algorithm options are Round Robin, Extended Round Robin
3. Creating an HDLM Environment137A virtual disk backend is a location where virtual disk data is stored. A disk, disk slice, file, or volume (such as
xii2.12 Collecting Audit Log Data... 422.12.1 Categories and Audit
3. Creating an HDLM Environment138To install HDLM to a host in which LDoms have been set:1. Log in to the control domain.2. Execute the ldm stop comma
3. Creating an HDLM Environment1393. Execute the ldm unbind command to unbind the resource of the guest domain.For example, to unbind a resource of th
3. Creating an HDLM Environment140backend.8. On the control domain, execute the ldm add-vdsdev command to export the virtual disk backends from the se
3. Creating an HDLM Environment141Figure 3-7: Configuration Example (After Installation)In this configuration example, /dev/dsk/c4t50060E8010027A82d0s
3. Creating an HDLM Environment1423.6 Configuring a Boot Disk EnvironmentThis section describes how to configure a boot disk environment in which HDLM
3. Creating an HDLM Environment143• Building a new pre-migration environment:Perform the procedure described in (4) Migration by Building a New Pre-Mi
3. Creating an HDLM Environment144Figure 3-8: Flow of setting up the boot disk environment when using an existing HDLM environment as the pre-migratio
3. Creating an HDLM Environment1453. Set the LU slices to be used by the post-migration boot disk.4. Execute the dlmsetconf utility as follows to crea
3. Creating an HDLM Environment146Figure 3-9: Flow of setting up the boot disk environment when installing HDLM in the existing local boot disk enviro
3. Creating an HDLM Environment147• To the slices of a single LU, allocate the Solaris file system, swap device, dump device, Sun Cluster global devic
xiii3.8.1 Precautions ...1653.8.2 Configuring a Boot
3. Creating an HDLM Environment148Figure 3-10: Flow of setting up the boot disk environment when using an existing boot disk environment without HDLM
3. Creating an HDLM Environment149• To the slices of a single LU, allocate the Solaris file system, swap device, dump device, Sun Cluster global devic
3. Creating an HDLM Environment150Figure 3-11: Flow of setting up the boot disk environment when building a new pre-migration environment
3. Creating an HDLM Environment1511. Install Solaris in the pre-migration environment.2. Install Sun Cluster if required.For details, see your Sun Clu
3. Creating an HDLM Environment152Cluster, also initialize the Sun Cluster global device file system.The following shows an example of executing the c
3. Creating an HDLM Environment1537. Set the rootdev parameter for the slice containing the / (root) file system of the post-migration boot disk to th
3. Creating an HDLM Environment154...30 node1:/dev/rdsk/c8t50060E80004361D1d1 /dev/did/rdsk/d309. Edit the post-migration boot disk's /etc/vfs
3. Creating an HDLM Environment155- Add the slice identifier of the / (root) file system (:a value from :a to :h) to the end.An example in which Sun M
3. Creating an HDLM Environment156specified for the boot device.12. Boot the system from the post-migration environment.• Perform steps 13 to 17 only
3. Creating an HDLM Environment157The following shows an example of executing the command: # metadb -d /dev/dsk/c0t0d0s7 /dev/dsk/c0t0d1s7 /dev/dsk/c0
xiv4. HDLM Operation 2674.1 Notes on Using HDLM... 2684.1.1
3. Creating an HDLM Environment1583.7 Migrating from a Boot Disk Environment to the Local Boot Disk EnvironmentThis section describes how to migrate f
3. Creating an HDLM Environment159Figure 3-12: Migration flow when coping the file system from a boot disk environment to the local boot disk environm
3. Creating an HDLM Environment160Perform steps 1 to 16 in the pre-migration environment.2. Allocate the LUs to be used by the boot disk in the post-m
3. Creating an HDLM Environment161# newfs /dev/rdsk/c0t0d0s0# newfs /dev/rdsk/c0t0d0s6# newfs /dev/rdsk/c0t0d0s3 11. Mount the Solaris file system in
3. Creating an HDLM Environment162/dev/dsk/c0t0d0s6 /dev/rdsk/c0t0d0s6 /usr ufs 1 no -/dev/did/dsk/d24s3 /dev/did/rdsk/d24s3 /global/.devices/
3. Creating an HDLM Environment163of the SDS or SVM state database to the post-migration environment. In this case, keep the pre-migration environment
3. Creating an HDLM Environment164For details on the required settings, see the documentation for the relevant application.• SDS• SVM• VxVM• Sun Stora
3. Creating an HDLM Environment1653.8 Configuring a Mirrored Boot Disk Environment Incorporating SVMA mirrored boot disk incorporating SVM can be mana
3. Creating an HDLM Environment166performing the procedures in (2) Uninstalling HDLM from the Boot Disk Environment in 3.17.3 Uninstalling HDLM.2. Upg
3. Creating an HDLM Environment167Figure 3-13: Configuring a boot disk environment in which HDLM manages the boot disk, from the local boot disk envir
xv5.2 Checking Error Information in Messages...3455.3 What To Do for a Path Error ...
3. Creating an HDLM Environment168Figure 3-14: Mirroring a boot disk environment in which HDLM manages the boot diskIn this example, the LU device nam
3. Creating an HDLM Environment169# metadb -a c8t50060E08000436D1d5s7 3. Decide the metadevice names.In this procedure, specify the settings as follow
3. Creating an HDLM Environment170 7. Execute the metaroot command. # metaroot d10 8. Reboot the host.9. When the host starts, check the swap device a
3. Creating an HDLM Environment171d10: Mirror Submirror 0: d11 State: Okay Submirror 1: d12 State: Okay Pass: 1 Read option: rou
3. Creating an HDLM Environment172131717 0 - c8t50060E08000436D1d4000003 0001.0000.0000000000653600.0006 HITACHI .DF600F .7701015
3. Creating an HDLM Environment173Figure 3-15: Current boot disks and boot disks after the migrationThe LU device names of the current boot disks are
3. Creating an HDLM Environment174Table 3-22: Metadevice names2. Create metadevices on the HDLM device, and then mirror them (single mirror). # metain
3. Creating an HDLM Environment175 # newfs /dev/md/rdsk/d100# newfs /dev/md/rdsk/d300 5. Mount the Solaris basic file system of the post-migration env
3. Creating an HDLM Environment1769. Execute the metaroot command, using the -R option to specify the mount point of the / (root) file system after th
3. Creating an HDLM Environment177Figure 3-16: Booting from the post-migration environment12. When the host starts, confirm that the swap device and d
Relevant program products Hitachi Dynamic Link Manager version 6.5.1For details about applicable OSs, see the Release Notes. TrademarksAIX
xvi7.2 The DLMgetras Utility for Collecting HDLM Error Information... 4387.2.1 Format...
3. Creating an HDLM Environment178largefiles/logging/xattr/onerror=panic/dev=1540064 on Mon Mar 9 11:00:25 2009/usr on /dev/md/dsk/d300 read/write/se
3. Creating an HDLM Environment179 d101: Submirror of d100 State: Okay Size: 25190400 blocks (12 GB) Stripe 0: Device
3. Creating an HDLM Environment180.77010152 0043 1C Online Non 35 0 - c8t50060E08000436D1d7000006 00
3. Creating an HDLM Environment181Figure 3-17: Current boot disks and boot disks after the migrationThe LU device names of the current boot disks are
3. Creating an HDLM Environment182Table 3-23: Metadevice names2. Create metadevices on the sd/ssd device, and then mirror them. (Single mirror) # meta
3. Creating an HDLM Environment183 # newfs /dev/md/rdsk/d10# newfs /dev/md/rdsk/d30 5. Mount the Solaris basic file system of the post-migration envir
3. Creating an HDLM Environment1849. Execute the metaroot command.Use the -R option to specify the mount point of the / (root) file system after the m
3. Creating an HDLM Environment185 # swap -lswapfile dev swaplo blocks free/dev/md/dsk/d20 85,20 16 8409584 8409584 # dumpadm
3. Creating an HDLM Environment18615. Execute the metastat command to confirm that the two-mirror configuration has been correctly configured. # metas
3. Creating an HDLM Environment1873.9 Checking the Path ConfigurationHDLM functions, such as load balancing and failover, are only available for HDLM
xvii8.10 KAPL10001 to KAPL11000 ...5608.11 KAPL11001 to KAPL12000 ...
3. Creating an HDLM Environment188making sure that an HDLM device corresponding to the sd or ssd device has been created.
3. Creating an HDLM Environment1893.10 Setting Up HDLM FunctionsHDLM includes functions like the load balancing function, the automatic failback funct
3. Creating an HDLM Environment190Table 3-24: The default and recommended values for each function(1) Setting Up Load BalancingYou can select whether
3. Creating an HDLM Environment191• exrr for the Extended Round Robin algorithm•lio for the Least I/Os algorithm•exlio for the Extended Least I/Os alg
3. Creating an HDLM Environment192If you set the number of times that the error needs to occur to 1, the above condition does not need to be satisfied
3. Creating an HDLM Environment193error in the -intvl parameter, and the number of times that the error needs to occur in the -iemnum parameter. When
3. Creating an HDLM Environment194Table 3-26: Values for the trace level settingIf an error occurs, you might have to set the trace level to 1 or high
3. Creating an HDLM Environment195(8) Setting the Number of Error Log FilesThe number of the error log files (the HDLM manager log (dlmmgrn.log (n ind
3. Creating an HDLM Environment196to 1024000 kilobytes of trace data.The following shows an example command that is used to set the number of trace fi
3. Creating an HDLM Environment197This example shows how to enable the collection of audit log data: # /opt/DynamicLinkManager/bin/dlnkmgr set -audlog
3. Creating an HDLM Environment198 # /opt/DynamicLinkManager/bin/dlnkmgr set -audfac local0 3.10.3 Checking the Updated SettingsThis chapter describes
3. Creating an HDLM Environment1993.11 Setting up Integrated TracesWhen HDLM is used, the dlnkmgr command logs are output to the integrated trace info
3. Creating an HDLM Environment200If HNTRLib2 has already been installed on a host when you install HDLM, the settings in the trace library will be i
3. Creating an HDLM Environment201press the Enter key.A screen to set the size of the integrated trace file appears. The current value is displayed in
3. Creating an HDLM Environment202The default value is 4. You can specify a value from 1 to 16. The value set here becomes the maximum of n in /var/op
3. Creating an HDLM Environment203A screen to set the monitoring interval appears. The current value is displayed in Current Span(sec).5. Enter a shor
3. Creating an HDLM Environment204value is 0.If you do not want to change the monitoring interval, leave New Span(sec) blank, type !, and then press t
3. Creating an HDLM Environment205The new setting is applied and the Hitachi Network Objectplaza Trace Library setup menu appears again.3.11.7 Finishi
3. Creating an HDLM Environment206# rm /opt/hitachi/HNTRLib2/mmap/hntr2mmap.mm 6. Execute the following command to start the integrated trace collecti
3. Creating an HDLM Environment2073.12 Creating File Systems for HDLM (When Volume Management Software Is Not Used)When volume management software is
1Chapter1. Overview of HDLMHDLM is a software package that manages paths between a host and a storage system. HDLM is designed to distribute loads acr
3. Creating an HDLM Environment208Figure 3-19: An output example for the mount -p commandEdit the /etc/vfstab file as appropriate based on the setting
3. Creating an HDLM Environment2093.13 Setting Up VxVMWhen you are using VxVM, VxVM accesses an LU by using an HDLM device.VxVM will automatically rec
3. Creating an HDLM Environment210The following describes the procedure for checking whether the shaded HDLM devices are recognized.•vxdisk commandMak
3. Creating an HDLM Environment211in the format cUtXdYsZ, corresponding to the device name of the enclosure.NoteThe device name of the enclosure corre
3. Creating an HDLM Environment212be removed from VxVM management. To remove non- HDLM devices from VxVM management, see (2) Removing Devices from VxV
3. Creating an HDLM Environment2133.13.3 Removing Devices from VxVMVxVM uses HDLM devices to access LUs managed by HDLM. Therefore, you must remove no
3. Creating an HDLM Environment214Figure 3-21: Devices That Are Recognized by VxVM before They Are Removed from VxVMYou must remove the following non-
3. Creating an HDLM Environment215actually created.Only one HDLM device is created for one LU#. However, for one LU, VxVM recognizes the same number o
3. Creating an HDLM Environment216The settings files necessary for device suppression are created by selecting menu task 17 (Prevent multipathing/Supp
3. Creating an HDLM Environment217Figure 3-23: When HBA ports on the alternate path differ from those on the primary path connected to the Hitachi sto
1. Overview of HDLM21.1 What is HDLM?With the widespread use of data warehousing and increasing use of multimedia data, the need for high-speed proces
3. Creating an HDLM Environment218execution result of the dlmvxexclude utility.For details on the dlmvxexclude utility, see 7.7 The dlmvxexclude Utili
3. Creating an HDLM Environment219Figure 3-24: Example of a description in the /etc/vx/vxvm.exclude (controllers section)The shaded portion indicates
3. Creating an HDLM Environment220The devices displayed for HDevName (the shaded portion) are the HDLM devices that must be recognized by VxVM. In the
3. Creating an HDLM Environment221VxVM of 3.13.3 Removing Devices from VxVM.6. Execute the vxdmpadm command on the HDLM devices listed by the vxdisk c
3. Creating an HDLM Environment222(3) Removing Devices From VxVM on a Path BasisIf all the physical paths to one LU go through the same HBA, devices a
3. Creating an HDLM Environment223Figure 3-25: When the HBA Port of the Physical Path Connected to a Hitachi Storage System Is the Same As the One Con
3. Creating an HDLM Environment224numbers and devices.The devices to be removed from VxVM are output to the paths section in the execution result of t
3. Creating an HDLM Environment225Figure 3-26: Example of a description in the /etc/vx/vxvm.exclude (paths section)The shaded portion indicates the sp
3. Creating an HDLM Environment226that must be recognized by VxVM. In the above example, it is c4t0d0.5. Execute the vxdisk command to list devices th
3. Creating an HDLM Environment2277. If you have set up vxvm.exclude again, execute the following command to restart the host and apply the setting. #
1. Overview of HDLM3• Lightning 9900V Series• Thunder 9500V Series• Universal Storage Platform V/VM• Virtual Storage Platform
3. Creating an HDLM Environment228Example 1:The vxdisk command does not display HDLM devices but displays the sd or ssd devices corresponding to those
3. Creating an HDLM Environment229The vxdmpadm command displays c3t0d0 and c4t1d0 in addition to the HDLM device c5t0d0, and the STATE column shows EN
3. Creating an HDLM Environment230• Devices in /etc/vx/vxvm.exclude that do not include dlmndrv@4. For devices whose tXdY portions are the same, chang
3. Creating an HDLM Environment231Figure 3-28: The /etc/vx/vxvm.exclude file (after editing)Among the non-HDLM devices in the ENABLED state, there mig
3. Creating an HDLM Environment232If there is more than one candidate for the controller number to be assigned in step 4, you might not be able to rem
3. Creating an HDLM Environment233group to be registered in Sun Cluster into only one of the nodes.5. If the VxVM disk group is not registered in Sun
3. Creating an HDLM Environment234NoteAfter registering the VxVM disk group into a Sun Cluster disk device group, do not use the VxVM command to impor
3. Creating an HDLM Environment2353.14 Setting Up SDSIf SDS is installed on an HDLM host, SDS uses the logical device file name of the HDLM device to
3. Creating an HDLM Environment236orboot -r (at the ok prompt)For more information on SDS settings, refer to the SDS documentation.3.14.2 Registering
3. Creating an HDLM Environment237metadevices created on a shared diskset. When using Sun Cluster, you use the device ID in the device name of the dis
1. Overview of HDLM41.2 HDLM FeaturesHDLM features include the following:The ability to distribute a load across multiple paths. This is also known as
3. Creating an HDLM Environment238When using Sun Cluster (stripe type):host1# metainit -s diskset1 d1 1 2 /dev/did/dsk/d10s0 /dev/did/dsk/d11s0 5. Cre
3. Creating an HDLM Environment2393.15 Setting Up SVMIf SVM is installed on an HDLM host, SVM uses the logical device file name of the HDLM device to
3. Creating an HDLM Environment240orboot -r (at the ok prompt)For more information on SVM settings, refer to the SVM documentation.3.15.2 Registering
3. Creating an HDLM Environment241created on a shared diskset. When using Sun Cluster, you use the device ID in the device name of the disk.NoteWhen y
3. Creating an HDLM Environment242When using Sun Cluster (stripe type):host1# metainit -s diskset1 d1 1 2 /dev/did/dsk/d10s0 /dev/did/dsk/d11s0 5. Cre
3. Creating an HDLM Environment2433.16 Setting Up VCSWhen VCS is installed on an HDLM host, you can register HDLM devices, or VxVM disk groups contain
3. Creating an HDLM Environment244If the number of paths differs depending on an HDLM device, use the maximum number for the calculation.#2The I/O tim
3. Creating an HDLM Environment2453.17 Uninstalling HDLMThis section explains how to return the HDLM environment to the way it was before HDLM was ins
3. Creating an HDLM Environment246storage system. This information will enable you to keep the correspondence with the logical device file names after
3. Creating an HDLM Environment2477. If HDLM devices are being used in Solaris 10 ZFS, execute the following command to export all ZFS storage pools t
5Chapter2. HDLM FunctionsThis chapter describes the various functions that are built into HDLM. Before the function specifications are explained thoug
3. Creating an HDLM Environment248As the utility instructs, enter the name of the VxVM disk device group you want to unregister.If the HDLM device has
3. Creating an HDLM Environment249 8. Confirm that the cluster node enters the maintenance mode.Make sure that the node that is in the maintenance mod
3. Creating an HDLM Environment250(3) Remove VCS SettingsIf you are using VCS, before uninstalling HDLM, unregister the HDLM devices and VxVM disk gro
3. Creating an HDLM Environment251# vxdg deport disk-group-name 3. To enable VxVM management, delete the entries for sd or ssd devices and the entries
3. Creating an HDLM Environment252When using Sun Cluster:host1# umount /global/diskset1/d1host1# metaclear -s diskset1 d1 2. Delete the disk from the
3. Creating an HDLM Environment253 When using a shared diskset1. Delete the shared volume.The following shows an example of executing the command.When
3. Creating an HDLM Environment254NoteWhen uninstalling HDLM on a host where a Device Manager Agent 5.0 or later is installed, do not execute any of t
3. Creating an HDLM Environment255Execute one of the following commands:•# reboot -- -r• boot -r (at the ok prompt)When Sun Cluster is being used:Exec
3. Creating an HDLM Environment256Figure 3-30: Configuration Example (Before Uninstallation)#A virtual disk backend is a location where virtual disk d
3. Creating an HDLM Environment257The following figure shows a configuration example for an LDoms environment before uninstalling HDLM.ldg1 An I/O dom
2. HDLM Functions62.1 Devices Managed by HDLMBelow is a list of devices that can or cannot be managed by HDLM. The devices that can be managed by HDLM
3. Creating an HDLM Environment258To uninstall HDLM from a host in which LDoms have been set:1. Log in to the control domain.2. Execute the ldm stop c
3. Creating an HDLM Environment259For example, to unbind a resource of the guest domain ldg2, execute the command as follows:# ldm unbind ldg24. Execu
3. Creating an HDLM Environment260virtual disk backends from the service domain on the I/O domain to which HDLM will be installed.For example, to expo
3. Creating an HDLM Environment261Figure 3-31: Configuration Example (After Uninstallation)In this configuration example, /dev/dsk/c2t50060E8010027A82
3. Creating an HDLM Environment262later:1. Execute the following command to import the disk group: # vxdg import disk-group-name 2. To use a volume th
3. Creating an HDLM Environment2635. Set up a Quorum device at any of the nodes that constitute the cluster.Check the device ID of the sd or ssd devic
3. Creating an HDLM Environment2643.17.5 Uninstalling Hitachi Network Objectplaza Trace Library (HNTRLib2)When you uninstall HDLM, if the KAPL09019-E
3. Creating an HDLM Environment265files will not be deleted during uninstallation. In this case delete these files after uninstallation.3.17.6 Uninsta
3. Creating an HDLM Environment266• Even if you attempt to uninstall HNTRLib2 when HNTRLib is installed, HNTRLib will not be uninstalled. If no other
267Chapter4. HDLM OperationThis chapter describes operating procedures for HDLM, including how to operate HDLM and the HDLM manager, and how to change
2. HDLM Functions72.2 System ConfigurationHDLM manages routes between a host and a storage system by using the SCSI driver (sd or ssd driver). The hos
4. HDLM Operation2684.1 Notes on Using HDLMThis section explains the notes on using HDLM and using the environment in which HDLM is installed. Make su
4. HDLM Operation269The shaded portion indicates mapping from combinations of sd or ssd device types and instance numbers to HDLM device logical devic
4. HDLM Operation2704.1.7 Starting the Host, System, and HDLM in a Solaris 10 EnvironmentWhen starting the hostIf the host is started in single-user m
4. HDLM Operation2712. Execute the following HDLM command to place the paths online: # /opt/DynamicLinkManager/bin/dlnkmgr online -s Even if the paths
4. HDLM Operation272• Changing the configuration of the HDLM operating environment• Applying an HDLM service pack#In single-user mode, HDLM command ac
4. HDLM Operation2734.2 HDLM Operations Using CommandsThis section explains how to use the HDLM command operations to utilize HDLM functions. For deta
4. HDLM Operation2744.2.3 Changing the Status of PathsThis section explains how to change path statuses.(1) Changing the Status of Paths to OnlineTo c
4. HDLM Operation275(2) Changing the Status of Paths to Offline(C)To change the status of paths to Offline(C):1. Check the current status of the paths
4. HDLM Operation276 4.2.4 Viewing LU InformationThis section explains how to display LU information by using the dlnkmgr command.To display LU inform
4. HDLM Operation277Information). The execution result of this operation is displayed on a single line for each path.The following shows an example of
Summary of amendmentsThe following table lists changes in this manual (3000-3-F05-50(E)) and product changes related to this manual.In addition to the
2. HDLM Functions8Figure 2-1: HDLM System ConfigurationTable 2-1: HDLM System Components lists the HDLM system components.Table 2-1: HDLM System Compo
4. HDLM Operation278# /opt/DynamicLinkManager/bin/dlnkmgr clear -pdstKAPL01049-I Would you like to execute the operation? Operation name = clear [y/n]
4. HDLM Operation279 # /opt/DynamicLinkManager/bin/dlnkmgr view -sys -audlogAudit Log : offAudit Log Category : -Audi
4. HDLM Operation280KAPL01001-I The HDLM command completed normally. Operation name = set, completion time = yyyy/mm/dd hh:mm:ss# To check whether th
4. HDLM Operation281the -sys -lic parameter to make sure that the license is installed correctly.The following shows an example of executing the comma
4. HDLM Operation2824.2.11 Viewing HDLM Component InformationThis section explains how to display HDLM component information.To display HDLM component
4. HDLM Operation2834.3 Starting and Stopping the HDLM ManagerIf an error occurs in the system, such as in an HDLM program, you may need to manually s
4. HDLM Operation284 # /opt/DynamicLinkManager/bin/dlnkmgr view -sys -msrvHDLM Manager Ver WakeupTimeDeadKAPL01001-I The HDLM command completed n
4. HDLM Operation2854.4 HDLM Resident ProcessesTable 4-1: HDLM resident processes lists and describes the resident processes in HDLM. To monitor these
4. HDLM Operation2864.5 Changing the Configuration of the HDLM Operating EnvironmentThis section describes how to reconfigure the environment for runn
4. HDLM Operation287dlmfdrv.conf).3. Execute the dlmsetconf utility for creating the HDLM driver configuration definition file.Edit the HDLM driver un
2. HDLM Functions92.3 LU ConfigurationAfter you have properly installed HDLM, the LU configuration will change as follows:Before the installation of H
4. HDLM Operation288When using VxVM, execute the following command to confirm that the DEVICE column of the LUs being managed by HDLM is displayed in
4. HDLM Operation289Execute the following command to display the driver configuration information, and then refer to the instance field of the HDLM dr
4. HDLM Operation290Environment.2. Change the path configuration.3. Return to the HDLM boot disk environment, following the procedure described in 3.6
4. HDLM Operation291• Reconfiguring an LU that is not managed by HDLM, as an HDLM-managed deviceReconfigure an LU that has already been added to the h
4. HDLM Operation292replaced, processing to unconfigure or reconfigure the HBA driver and either the sd or ssd driver might not complete until the hos
4. HDLM Operation293• If the major and minor numbers of the sd or ssd device of an LU to be newly added to HDLM matches the major or minor number of a
4. HDLM Operation294Figure 4-1: Example of executing the format command3. Execute the dlmsetconf utility for creating the HDLM driver configuration de
4. HDLM Operation295Specify settings as shown in (2) Removing Devices from VxVM on a Controller Basis or (3) Removing Devices From VxVM on a Path Basi
4. HDLM Operation2968. Register the added LU to the application.(3) Adding a New LU By Restarting the Nodes (When Using Sun Cluster)NoteHave the HDLM
4. HDLM Operation2971. Set up the storage system and switch so that Solaris recognizes the LU.2. Check the LU newly recognized by the node.You can che
2. HDLM Functions10Figure 2-2: LU Configuration Recognized by the Host After the Installation of HDLMTable 2-2: Components Recognized by the Host list
4. HDLM Operation298Execute the following command on any node: # /usr/cluster/lib/sc/scsi -c inkeys -d the-name-of-the-logical-device-file-on-slice-2-
4. HDLM Operation2999. Make sure that the logical device files for the sd or ssd device are backed up.When you restart the node, with the reconfigurat
4. HDLM Operation300Devices from VxVM.12. Stop all nodes in the cluster.If the key is displayed in step 4, and nodes are running in non-cluster mode i
4. HDLM Operation301Trace File Size(KB) : 1000Number Of Trace Files : 4Path Health Checking : on(30)Auto Failback
4. HDLM Operation30217. Delete the device ID information for devices that do not exist.Execute the following command: # /usr/cluster/bin/scdidadm -C 1
4. HDLM Operation303 # /usr/cluster/bin/scdidadm -r 19. Notify the node of the most recent device ID information.Execute the following command: # /usr
4. HDLM Operation304results of the command, compare the correspondence with the correspondence that took place before the HDLM installation, and then
4. HDLM Operation305Figure 4-3: Example of executing the format command3. If setup is performed for Quorum devices and disk device groups, on an LU ne
4. HDLM Operation306The following shows an example of executing the command: # /usr/cluster/lib/sc/scsi -c inkeys -d /dev/rdsk/c3t50060E80033A9902d2s2
4. HDLM Operation3077. If you do not want HDLM to manage one of the LUs newly recognized by the node, set up the LU so that it is excluded from HDLM m
2. HDLM Functions112.4 Program ConfigurationHDLM is actually a combination of several programs. Because each program corresponds to a specific HDLM op
4. HDLM Operation308indicates the path accessing the LU recognized for the first time by the HDLM driver.11. Delete the device ID information for devi
4. HDLM Operation30912. Allocate the device ID.Execute the following command: # /usr/cluster/bin/scdidadm -r 13. Notify the node of the most recent de
4. HDLM Operation310Check the correspondence between HDevName (the name of the logical device file of the HDLM device) and iLU (the internal LU number
4. HDLM Operation311(1) Changing the Configuration by Restarting the Host1. Back up the data in the file systems, volumes, and metadevices that use th
4. HDLM Operation312LU you are deleting, replace the LU.9. Shut down the host.10. Change the configuration.11. Boot the host.12. Make sure that Solari
4. HDLM Operation313 The KAPL10242-I message appears when you execute the dlmsetconf utility. Type y in response.15. Execute the following command to
4. HDLM Operation314> ### Path=/pci@8,700000/SUNW,emlxs@1/fp@0,0/ssd@w50060e80033a9938,2> ### Device=ssd84 target=134012 lun=2> ### Path=/pci
4. HDLM Operation315In the lines that define the LU that is to be removed from HDLM management, delete the hash mark (#) in front of the LDEV property
4. HDLM Operation316# /usr/cluster/bin/scgdevs 25. If you cleared the settings for a Quorum device in step 3, perform the following procedure:When usi
4. HDLM Operation317in step 1.31. If you released file system settings in steps 2 to 4, check the HDLM devices after reconfiguration, and then set up
2. HDLM Functions12Table 2-3: Function of HDLM ProgramsProgram name FunctionsHDLM command Provides the dlnkmgr command, which enables you to:• Manage
4. HDLM Operation318 # /opt/DynamicLinkManager/bin/dlmcfgmgr -a The HDLM device will be deleted without restarting the host.5. Execute the dlnkmgr com
4. HDLM Operation3194.5.5 Specifying Whether a Logical Unit Is To Be Managed by HDLM (When Not Using Sun Cluster)This section describes the procedures
4. HDLM Operation320 # /opt/DynamicLinkManager/bin/dlmsetconf -u 4. Restart the host, with the reconfiguration option specified: # reboot -- -r(2) Cha
4. HDLM Operation321Using a text editor, edit the definitions in the HDLM driver unconfiguration definition file (/opt/DynamicLinkManager/config/dlmfd
4. HDLM Operation322definition file (/kernel/drv/dlmfdrv.conf).Execute following the dlmsetconf utility to apply the settings in the HDLM driver uncon
4. HDLM Operation323The shaded portion indicates the LDEV information about the LU that is to be removed from HDLM management.3. If setup is being per
4. HDLM Operation324Figure 4-8: The /opt/DynamicLinkManager/config/dlmfdrv.unconf file (before editing)Figure 4-9: The /opt/DynamicLinkManager/config/
4. HDLM Operation325Figure 4-10: Result output by executing the dlmvxexclude utilityFigure 4-11: Coding in the /etc/vx/vxvm.exclude fileThe shaded por
4. HDLM Operation326For details on the dlmvxexclude utility, see 7.7 The dlmvxexclude Utility for Assisting Creation of the VxVM Configuration File.7.
4. HDLM Operation327HDLM Alert Driver Ver WakeupTime ElogMem SizeAlive x.x.x-xx yyyy/mm/dd hh:mm:ss 4096HDLM Driver Ver
2. HDLM Functions132.5 Position of the HDLM Driver and HDLM DeviceThe HDLM driver is positioned above the SCSI driver. Each application on the host us
4. HDLM Operation328Execute the following command: # /usr/cluster/bin/scdidadm -C 13. Allocate the device ID.Execute the following command: # /usr/clu
4. HDLM Operation329Execute the following command to clear the install mode of a cluster when it consists of two nodes:# /usr/cluster/bin/scconf -c -q
4. HDLM Operation3303. If setup is being performed for Quorum devices and disk device groups in the LU to be managed by HDLM, release the LU settings.
4. HDLM Operation331The following shows an example of executing the command: # /usr/cluster/lib/sc/scsi -c scrub -d /dev/rdsk/c3t50060E80033A9902d2s2
4. HDLM Operation332Figure 4-15: The /opt/DynamicLinkManager/config/dlmfdrv.unconf file (after editing)The shaded portion indicates the text to be edi
4. HDLM Operation333NoteThe following message might be output to the console window or syslog while the node is running: Could not read symbolic link
4. HDLM Operation334• Even when cluster software is used, it is not displayed in Support Cluster. Nevertheless, no problem exists with the functionali
4. HDLM Operation335Execute the following command: # /usr/cluster/bin/scdidadm -r 19. Notify the node of the most recent device ID information.Execute
4. HDLM Operation336that took place before the HDLM installation, and then re-register HDLM devices with the programs that will use them.If you want t
4. HDLM Operation337Figure 4-16: Example of executing the format command3. If setup is performed for Quorum devices and disk device groups in the LU t
2. HDLM Functions142.6 Logical Device Files for HDLM DevicesWhen you install HDLM, a logical device file to be used by HDLM will be created for each L
4. HDLM Operation338If the key is displayed, place the LU under HDLM management by following the steps from step 5 of (2) Changing a Non-HDLM-Managed
4. HDLM Operation339Figure 4-18: The /opt/DynamicLinkManager/config/dlmfdrv.unconf file (after editing)The shaded portion indicates the text to be edi
4. HDLM Operation3409. Delete the device ID information for devices that do not exist.Execute the following command: # /usr/cluster/bin/scdidadm -C 10
4. HDLM Operation341Execute the following command: # /usr/cluster/bin/scgdevs 13. When using an HDLM-managed device, as a Quorum device, set the Quoru
4. HDLM Operation34216. Create the file system and set up the global mount as necessary.For details, refer to the Sun Cluster documentation.
343Chapter5. TroubleshootingThis chapter describes how to properly use HDLM error information, and then how to resolve the problem, if an error occurs
5. Troubleshooting3445.1 Information collected by using the DLMgetras utility for collecting HDLM error informationImmediately after an error occurs,
5. Troubleshooting3455.2 Checking Error Information in MessagesWhen you want to configure the system so that HDLM messages are output to syslog, speci
5. Troubleshooting346• Host port number (hexadecimal)• Bus number (hexadecimal)• Target ID (hexadecimal)• Host LU number (hexadecimal)The path name is
5. Troubleshooting3475.3 What To Do for a Path ErrorWhen a path error is detected, HDLM performs a failover on the path and outputs the KAPL08022-E me
2. HDLM Functions15Block logical device files for HDLM devices are created in /dev/dsk. Character logical device files for HDLM devices are created in
5. Troubleshooting348Figure 5-2: Troubleshooting Procedure When a Path Error OccursIf an error occurs in a boot disk environment on a path connected t
5. Troubleshooting349environment.5.3.3 Identifying the Error PathCheck the obtained path information to find the path with the error. In the Status co
5. Troubleshooting3505.4 Actions to Take for a Path Error in a Boot Disk EnvironmentThis section describes the action to take if an error occurs in a
5. Troubleshooting351If an error occurs on one or more of the paths to the boot diskHDLM outputs the KAPL08022-E message to the console, syslog, and e
5. Troubleshooting3525.5 What To Do for a Program ErrorThe following describes what to do to handle errors that occur in an HDLM program. Figure 5-3:
5. Troubleshooting3535.5.3 What To Do for the Program ErrorFollow the recommended actions for messages in 8. Messages.If the error occurs again after
5. Troubleshooting3545.6 What To Do for Other ErrorsWhen the cause of an error may be related to HDLM but is neither a path error nor an HDLM program
355Chapter6. Command ReferenceThis chapter describes the HDLM command (dlnkmgr) and its operations.6.1 Overview of the HDLM Command dlnkmgr6.2 clear (
6. Command Reference3566.1 Overview of the HDLM Command dlnkmgrThis section describes how to specify the HDLM command dlnkmgr and its subcommands (cal
6. Command Reference357Note:• Execute the command as a user with root permissions.• To specify a value that contains a space in its parameter, enclose
2. HDLM Functions162.7 Distributing a Load Using Load BalancingWhen the system contains multiple paths to a single LU, HDLM can distribute the load ac
6. Command Reference3586.2 clear (Returns the Path Statistics to the Initial Value)The dlnkmgr command's clear operation clears the statistics (I
6. Command Reference359(2) To display the format of the clear operation-helpDisplays the format of the clear operation.Example # /opt/DynamicLinkManag
6. Command Reference3606.3 help (Displays the Operation Format)The dlnkmgr command's help operation displays the list of operations available for
6. Command Reference361#Example 2The following example shows how to display the formats of multiple operations. # /opt/DynamicLinkManager/bin/dlnkmgr
6. Command Reference362help: Format dlnkmgr help { clear | offline | online | set | view | monitor }KAPL01001-I The HDLM command completed normall
6. Command Reference3636.4 offline (Places Paths Offline)The dlnkmgr command's offline operation places online paths offline. Specify the paths t
6. Command Reference364-hba host-port-number.bus-numberUse this parameter to place offline, at one time, all the paths that pass through a specific HB
6. Command Reference365KAPL01102-I All the paths which pass the specified HBA port will be changed to the Offline(C) status. Is this OK? [y/n]:yKAPL01
6. Command Reference366-chaid CHA-port-IDUse this parameter to place offline, at one time, all paths that pass through a specific CHA port. The comman
6. Command Reference367device.For SCSI-device-name, specify the value of Device displayed by executing the view operation as follows:# /opt/DynamicLin
2. HDLM Functions17Figure 2-5: Flow of I/O Data When the Load Balancing Function Is Not UsedWhen the load balancing function is not used, I/O operatio
6. Command Reference368The following example shows how to display the format of the offline operation: # /opt/DynamicLinkManager/bin/dlnkmgr offline -
6. Command Reference369# /opt/DynamicLinkManager/bin/dlnkmgr view -path -stname | grep 9500V | grep 0A The above command will display information pert
6. Command Reference3706.5 online (Places Paths Online)The dlnkmgr command's online operation places offline paths online. Specify the paths to b
6. Command Reference371Use this parameter to place online, at one time, all the paths that pass through a specific HBA port. The command will place on
6. Command Reference3720 path(s) were not. Operation name = online#-cha -pathid AutoPATH_IDUse this parameter to place online, at one time, all the pa
6. Command Reference373CHA port whose CHA-port-ID is 00001.# /opt/DynamicLinkManager/bin/dlnkmgr offline -chaid 00001KAPL01104-I All the paths which p
6. Command Reference374-sExecutes the command without displaying the message asking for confirmation of command execution from the user. Specify this
6. Command Reference375ReferenceExecuting the view operation together with standard UNIX commands enables you to filter the path information listed fo
6. Command Reference3766.6 set (Sets Up the Operating Environment)The dlnkmgr command's set operation sets the HDLM operating environment.6.6.1 F
6. Command Reference377Table 6-2: Default and Recommended Values-lb {on [-lbtype {rr|exrr|lio|exlio|lbk|exlbk}]|off}Enables or disables load balancing
2. HDLM Functions18Figure 2-6: Flow of I/O Data When the Load Balancing Function Is UsedWhen the load balancing function is used, I/O operations are d
6. Command Reference378exlio: The Extended Least I/Os algorithmlbk: The Least Blocks algorithmexlbk: The Extended Least Blocks algorithmThe type of al
6. Command Reference379hh:mm:ss#-elfs error-log-file-sizeSpecify a value from 100 to 2000000 (in kilobytes) for the size of the error log files. The t
6. Command Reference380As the amount of log information to be output increases, the amount of time before existing information is overwritten becomes
6. Command Reference381• When the checking interval has been specified before:The interval specified in the last timeThe explanation for the following
6. Command Reference382Operations.When you specify on, specify the checking interval by specifying the parameter immediately following on. If you do n
6. Command Reference383number-of-times-error-is-to-occur] | off }Enables or disables intermittent error monitoring.on: Enabledoff: DisabledIntermitten
6. Command Reference384monitoring interval and the number of times that the error is to occur:-intvl error-monitoring-intervalSpecify the monitoring i
6. Command Reference385Intermittent error monitoring will then resume with the changed settings. If you set the automatic failback function to off wh
6. Command Reference386Legend:AFB: Automatic failbackIEM: Intermittent error monitoring#1When this condition is not satisfied, the KAPL01080-W message
6. Command Reference387# /opt/DynamicLinkManager/bin/dlnkmgr set -iem on -intvl 20 -iemnum 2KAPL01049-I Would you like to execute the operation? Opera
2. HDLM Functions19owner path also varies depending on the LU. A non-owner path is a path that uses a CHA other than the owner controller (a non-owner
6. Command Reference388A temporary license key cannot be installed by using the dlnkmgr command's set operation.Example 1The following example sh
6. Command Reference389-category [[ss] [a] [ca]|all]Specifies the categories of audit log data to be collected. Table 6-8: Values Indicating Audit Log
6. Command Reference390-sExecutes the command without displaying the message asking for confirmation of command execution from the user. Specify this
6. Command Reference391 | -afb off | -iem on [ -intvl Error-Monitor-Interval ]
6. Command Reference392 all } (Default Value all) Facility-Name { user |
6. Command Reference3936.7 view (Displays Information)The dlnkmgr command's view operation displays HDLM program information, path information, L
6. Command Reference394[-srt {lu|cp}][-t](3) To display LU informationTo display LU information/opt/DynamicLinkManager/bin/dlnkmgr view -lu[-hdev host
6. Command Reference3956.7.2 ParametersThis section describes the parameters for the view operation, in the following order: (1) To display program in
6. Command Reference396Load Balance Settings for load balancing• Setting status:on: Enabledoff: Disabled• Algorithm:When the setting status of load ba
6. Command Reference397Path Health Checking• Settings for path health checking:on: Enabledoff: Disabled• Checking interval:When the setting of the pat
2. HDLM Functions20(2) When Using the Lightning 9900 Series, Lightning 9900V Series, Hitachi USP, Universal Storage Platform V/VM, Virtual Storage Pla
6. Command Reference398WakeupTime Startup time of the HDLM alert driverElogMem Size Size of error log memory for the HDLM alert driver in kilobytes-pd
6. Command Reference399#When you use cluster software, the settings of the cluster support function and the kinds of cluster servers are not displayed
6. Command Reference400#Example 2The following example shows how to display information about the HDLM manager: # /opt/DynamicLinkManager/bin/dlnkmgr
6. Command Reference401Example 6The following example shows how to display information about the audit log settings: # /opt/DynamicLinkManager/bin/dln
6. Command Reference402Use this parameter to display the model ID of the storage system in the product ID element of the DskName field. When this para
6. Command Reference403To display path information (by selecting a display item)-path -itemWhen you specify the -path parameter together with the -ite
6. Command Reference404#Because both PathID and Status are always displayed, you do not have to specify any parameters. In the sub-parameters followin
6. Command Reference405Use this parameter to sort the path information in ascending order, according to the specified sorting key.The sorting keys are
6. Command Reference406To display a summary of path information-path -cWhen you specify the -path parameter together with the -c parameter, only the P
6. Command Reference40711 or more characters in the product ID, the 8th and following characters are abbreviated to an ellipsis (...). The following
2. HDLM Functions21was distributed will be used. However, if a specified number of I/Os has been issued to a path, processing switches to the next pat
6. Command Reference408Displayed path informationTable 6-12: Displayed Path Information describes the displayed path information. The following explai
6. Command Reference409PathStatus Status of the displayed paths. The displayed status indicates the following:•Online: All paths are available.•Reduce
6. Command Reference410iLU#iLU LU number of the storage system.This number combined with the storage system name (shown in DskName) identifies the LU
6. Command Reference411IO-Count#-- Total I/O count for the path, indicated by a decimal number. The maximum value that can be displayed is 232 - 1 (42
6. Command Reference412Legend:--: Not displayed#The path information is displayed only when a value is specified for the -path -item parameter.Table 6
6. Command Reference413#When a summary is displayed by specifying the -path -c parameter and there are more than 11 characters in the summary string,
6. Command Reference414(3) To display LU informationWhen displaying LU information, if the -item parameter, -c parameter, or the -c -item parameter is
6. Command Reference4150002 c6t2d1 sd62 000004 Online sd65 000010 Online0003 c6t2d2 sd63 000005 Online sd66 0000
6. Command Reference416In the sub-parameters, -hdev or -pathid, you can filter the LU information to be displayed. If you omit both parameters, the co
6. Command Reference417To display a summary of LU information-lu -cWhen the -c parameter is specified with the -lu parameter, a summary of LU configur
2. HDLM Functions22operation. For details on the set operation, see 6.6 set (Sets Up the Operating Environment).
6. Command Reference418Omits the title for each information item.Example # /opt/DynamicLinkManager/bin/dlnkmgr view -lu -cProduct S/N LUs iLU
6. Command Reference419Displayed LU informationTable 6-17: Displayed LU Information describes the displayed LU information. The following explains the
6. Command Reference420iLU LU number of the storage system.This number combined with the storage system name (shown in DskName) identifies the LU that
6. Command Reference421PathName#1-- The path name, which indicates a path. When you modify the system configuration or replace a hardware item, you sh
6. Command Reference422Legend:IO-Count#1-- Total I/O count for a path. The maximum value that can be displayed is 232 - 1 (4294967295). If the total I
6. Command Reference423--: Not displayed#1 This information is displayed when one of the following conditions exist: - The user selected the item to b
6. Command Reference424Example# /opt/DynamicLinkManager/bin/dlnkmgr view -hba HbaID Port.Bus IO-Count IO-Errors Paths OnlinePathsPhysical Device0
6. Command Reference425CHA port. HDLM displays the unique CHA port ID assigned to each CHA port. This CHA port ID is used in monitor operations, and c
6. Command Reference426(Product), storage system serial numbers (S/N), and CHA port numbers (ChaPort).-tOmits the title for each information item.(6)
6. Command Reference427000000 c6t5d0 sd74 9970/9980.15001.0670000001 c6t5d1 sd75 9970/9980.15001.0671000002 c6t5d2 sd76 9970/9980.15001.06
2. HDLM Functions232.8 Performing Failovers and Failbacks Using Path SwitchingWhen the system contains multiple paths to an LU and an error occurs on
6. Command Reference428 [ic] [ie] [dnu] [iep] [pd] | all ] [ -hdev HostDeviceName
6. Command Reference4296.8 monitor (Displays I/O Information at a Specified Interval)The dlnkmgr command's monitor operation displays I/O informa
6. Command Reference430are 500 or more paths for the -intvl parameter, the time interval of the monitor operation might be several seconds to 20 secon
6. Command Reference431Omits the title for each information item.Table 6-22: Items displayed as I/O information for each HBA portExample# /opt/Dynamic
6. Command Reference432format for the subsequent parameters are as follows:-intvl intervalSpecifies the interval at which I/O information is to be dis
6. Command Reference433ChaPort : 1RStartTime : yyyy/mm/dd hh:mm:ss ElapsedTime IO-Count IO-Errors00:00:30 1154 000:01:
435Chapter7. Utility ReferenceThis chapter explains the utilities used by HDLM.7.1 Overview of the Utilities7.2 The DLMgetras Utility for Collecting H
7. Utility Reference4367.1 Overview of the UtilitiesHDLM provides the following utilities:• The DLMgetras utility for collecting HDLM error informatio
7. Utility Reference437Assisting Creation of the VxVM Configuration File.• The installhdlm utility for installing HDLMThis utility performs a new inst
2. HDLM Functions24A fatal error that might stop the system.ErrorA high-risk error, which can be avoided by performing a failover or some other counte
7. Utility Reference4387.2 The DLMgetras Utility for Collecting HDLM Error InformationThis utility collects information that is needed to analyze HDLM
7. Utility Reference439Specify the output directory for the information that is to be collected by the DLMgetras utility for collecting HDLM error inf
7. Utility Reference440subdirectories. If no files are found in a specified directory, the utility does not perform file collection for that directory
7. Utility Reference441products other than HDLM. This file is output only when using the Hitachi Command Suite product that is the target for collecti
7. Utility Reference442opt/DynamicLinkManager/configdlmfdrv.unconf HDLM driver unconfiguration definition filedlmfdrv.unconf.bak Previous generation o
7. Utility Reference443dlmfdrv.conf_oldbackup#3Backup of the existing dlmfdrv.conf file, taken when you perform an upgrade installation from HDLM 5.6.
7. Utility Reference444gabtabllthostsllttabvxfendgvxfenmode#5vxfentabI/O fencing function setup filesmnttab File system mount informationsyslog.conf s
7. Utility Reference445df-k.txt Mount informationdf-o.txt i node utilization statusdlmgetomtrace.dmp In-memory trace informationdlmls-la.txt List of d
7. Utility Reference446prtconf-pv.txt Hardware configuration information of a host (output results of the prtconf -pv command)prtconf-vP.txt List of d
7. Utility Reference447VXVM_vxdmp.txt /dev/vx/dmp directory listVXVM_vxrdmp.txt /dev/vx/rdmp directory listVXVM_vxdsk.txt /dev/vx/dsk directory listVX
2. HDLM Functions25Figure 2-8: Path Switching(2) Automatic FailbacksWhen a path recovers from an error, HDLM can automatically place the recovered pat
7. Utility Reference448var/adm/syslog syslog.log.txt Log of error messagesThe output destination is either /var/vxvm/vxconfigd.log or /var/adm/syslog/
7. Utility Reference449#1etc/lvm#6md.tab SDS or SVM input parameter filemd.cf SDS or SVM configuration backup filemddb.cf Information on SDS or SVM st
7. Utility Reference450An output directory is created in the specified directory when you extract the getras.tar.Z file.#2The value N depends on the s
7. Utility Reference4517.3 The dlmcfgmgr Utility for Managing the HDLM ConfigurationThis utility makes the HDLM driver recognize the contents of the H
7. Utility Reference4527.3.2 Parameters-aApplies the contents of the HDLM driver configuration definition file (/kernel/drv/dlmfdrv.conf) to HDLM driv
7. Utility Reference453• You must restart the host after performing an upgrade installation or re-installation. LUs will not be added or deleted dynam
7. Utility Reference454occurs:-For the LU, you changed the LUN mapping, the mapping-destination storage port, or the HBA port on the recognizing host.
7. Utility Reference4557.4 The dlminstcomp HDLM Component Installation UtilityThis utility complements HDLM installation. Execute this utility when bo
7. Utility Reference4567.5 The dlmlisthdev Utility for Assisting HDLM TransitionsUse the dlmlisthdev utility when migrating to HDLM 6.5.1 from HDLM 04
7. Utility Reference457configuration in HDLM 6.5.1.5. Create a list that shows the correspondences between the logical device file names of the HDLM d
2. HDLM Functions26Storage Platform V/VM, Virtual Storage Platform, Hitachi AMS2000 Series, or Hitachi SMS is being used, all the paths are owner path
7. Utility Reference458The file that stores the output result of the dlnkmgr command's view -path operation must be created in a directory that i
7. Utility Reference4597.6 The dlmsetconf Utility for Creating the HDLM Driver Configuration Definition FileThis dlmsetconf utility obtains device inf
7. Utility Reference460In the subsequent explanations, the configuration definition file is indicated as the HDLM driver configuration definition file
7. Utility Reference461Depending on the contents of the HDLM driver unconfiguration definition file (/opt/DynamicLinkManager/config/dlmfdrv.unconf) th
7. Utility Reference462Example 4The -u parameter is specified:Defines a non- HDLM-managed LU based on the contents of the definitions in the HDLM driv
7. Utility Reference463definition file (/kernel/drv/dlmfdrv.conf) the utility adds an entry (that is, a definition) to the definition of the LU for wh
7. Utility Reference464option specified, and then restart the host.• If the below message appears after you execute the dlmsetconf utility, it means t
7. Utility Reference4657.7 The dlmvxexclude Utility for Assisting Creation of the VxVM Configuration FileThis utility outputs the file (vxvm_exclude.t
7. Utility Reference466# /opt/DynamicLinkManager/bin/dlmvxexclude -d /tmpDisplay exampleExampleThe entries for the following devices are output:• sd o
7. Utility Reference467• Do not use the output result of the dlmvxexclude utility as is for the vxvm.exclude file. If a device other than the HDLM-man
2. HDLM Functions27Executing the online operation places the offline path online. For details on the online operation, see 6.5 online (Places Paths On
7. Utility Reference4687.8 The installhdlm Utility for Installing HDLMYou can use the installhdlm utility to perform a new installation, upgrade insta
7. Utility Reference469Table 7-4: Keys that Can Be Defined in the [INSTALLATION_SETTINGS] SectionKey name#1Explanation#2Required or optional? Maximum
7. Utility Reference470Legend:Optional: If you omit the key name and value, the default is used.However, for an upgrade installation or re-installatio
7. Utility Reference471Table 7-5: Keys that Can Be Defined in the [ENVIRONMENT_SETTINGS] SectionKey name#1Explanation#2Required or optional? Maximum l
7. Utility Reference472trace_level Specify the output level for traces.You can specify a value from 0 to 4. The default is 0.Optional Optional 1trace_
7. Utility Reference473Legend:Optional: If you omit the key name and value, the following value is used:• For a new installationThe default is used.•
7. Utility Reference474For details on the settings functionality, see 6.6 set (Sets Up the Operating Environment).#3You can specify this key only in t
7. Utility Reference4757.8.4 About the Log FileDuring an unattended installation, information about installation progress is output to the log file in
7. Utility Reference4767.9 installux.sh Utility for HDLM Common InstallerThis utility determines what OS HDLM will be installed on, and installs the c
477Chapter8. MessagesThis chapter describes the format and meaning of the message IDs, and also the terms used in the messages and message explanation
iPrefaceThis manual describes the functions and use of the following program products.• Hitachi Dynamic Link ManagerIntended readersThis manual is int
2. HDLM Functions28error occurred on the path.The (E) in Offline(E) indicates the error attribute, which indicates that an error occurred in the path.
8. Messages4788.1 Before Viewing the List of MessagesThis section explains the following information that is needed to locate messages and understand
8. Messages479• HDLM driver (filter component)• HDLM alert driver• HDLM management target
8. Messages4808.2 KAPL01001 to KAPL02000KAPL01001-IThe HDLM command completed normally. Operation name = aa...aa, completion time = bb...bbDetailsThe
8. Messages481Detailsaa...aa: clear, set, monitor,online, offline, or viewbb...bb: Specified parameterActionExecute help operation-name of the HDLM co
8. Messages482KAPL01009-WA parameter value is invalid. Operation name = aa...aa, parameter = bb...bb, parameter value = cc...cc, Valid value = dd...dd
8. Messages483KAPL01014-WNo authority to execute the HDLM command. Operation name = aa...aaDetailsYou do not have the administrator permissions necess
8. Messages484the corresponding CHA_ID, and retry the operation. For details on the view operation, see 6.7 view (Displays Information).KAPL01018-WThe
8. Messages485KAPL01021-ECannot execute the HDLM command due to insufficient memory.DetailsMemory required for HDLM command processing could not be al
8. Messages486PathID = aa...aa Would you like to continue the processing of the online operation? [y/n]:DetailsA path that cannot be placed Online was
8. Messages487cc...cc: Duplicate parameter valueActionDelete the duplicate parameter value, and then retry.KAPL01045-WToo many parameter values are sp
2. HDLM Functions29LU.#2When the following conditions are satisfied, a path that has been determined to have an intermittent error also becomes subjec
8. Messages488Up the Operating Environment).KAPL01050-IThe currently selected paths will be changed to the Online status. Is this OK? [y/n]:DetailsThe
8. Messages489KAPL01053-IIf you are sure that there would be no problem when the path is placed in the Offline(C) status, enter y. Otherwise, enter n.
8. Messages490KAPL01056-IIf you are sure that there would be no problem when all the paths which pass the specified aa...aa are placed in the Offline(
8. Messages491KAPL01059-WCannot specify the parameter aa...aa at the same time if you specify parameter bb...bb and parameter value cc...cc. Operation
8. Messages492ActionNone. For details on the online operation, see 6.5 online (Places Paths Online). For details on the offline operation, see 6.4 off
8. Messages493Obtain a valid license key, and then retry.KAPL01071-IThe permanent license was installed.DetailsThe license was renewed and is register
8. Messages494Re-install HDLM.KAPL01076-IThe permanent license has been installed.DetailsYou need not install a license because a permanent license ha
8. Messages495number-of-times-error-is-to-occur-for-intermittent-error-monitoring).KAPL01081-EThe license key file is invalid. File name = aa...aaDeta
8. Messages496aa...aa: /var/tmp/hdlm_licenseActionIf a license key file exists, delete it./var/tmp/hdlm_licenseKAPL01088-WThe specified parameter valu
8. Messages497aa...aa: Path IDbb...bb: Code showing reason for errorActionResolve the error in the relevant path, and then re-execute.KAPL01091-EThe O
2. HDLM Functions302.9 Intermittent Error Monitoring (Functionality When Automatic Failback Is Used)An intermittent error means an error that occurs i
8. Messages498DetailsAn attempt to recover the path failed because the correct disk label has not been set in the LU for the path to be put online. aa
8. Messages499aa...aa: Code showing the reason for the errorActionRe-execute the command. If the same error occurs again, execute the DLMgetras utilit
8. Messages500DetailsMultiple paths will be collectively placed Offline(C) because the -hbaid or -chaid parameter was specified. To collectively place
8. Messages501want to terminate processing, enter n.KAPL01112-EAn attempt to connect to the HDLM driver has failed. Operation name = aa...aaDetailsHDL
8. Messages502KAPL01116-WThe audit log configuration file is invalid. Restart the HDLM Manager, and execute the "dlnkmgr view -sys -audlog"
8. Messages503KAPL01120-WA storage subsystem model ID could not be displayed. Details = aa...aa, bb...bbDetailsA storage system model ID could not be
8. Messages5048.3 KAPL03001 to KAPL04000KAPL03001-IHDLM API information - aa...aaDetailsThis information is required for resolving problems.aa...aa: T
8. Messages505aa...aa: API trace error informationActionExecute the DLMgetras utility for collecting HDLM error information, and then contact your HDL
8. Messages506contract for HDLM. For details on the DLMgetras utility, see 7.2 The DLMgetras Utility for Collecting HDLM Error Information.
8. Messages5078.4 KAPL04001 to KAPL05000KAPL04001-IHDLM manager started.ActionNone.KAPL04002-ECould not start the HDLM manager.DetailsThe HDLM manager
2. HDLM Functions312.9.3 Intermittent Error Monitoring ActionsIntermittent error monitoring is performed on each path, and it automatically starts as
8. Messages508aa...aa: Option definition file nameActionCheck whether another program is currently using this file (for example, the file is being ope
8. Messages509KAPL04012-ECould not create a communication pipe. RC = aa...aaDetailsHDLM manager could not start normally because it was unable to crea
8. Messages510DetailsAn attempt to read the log information from the alert driver failed.aa...aa: API return code (decimal (base-10) number)ActionExec
8. Messages511DLMgetras Utility for Collecting HDLM Error Information.KAPL04024-CA critical error occurred in the HDLM manager. (aa...aa)DetailsThis i
8. Messages512Install a permanent license by the expiration day.KAPL04028-EThe temporary license expired.ActionInstall a permanent license.KAPL04029-E
8. Messages513KAPL04034-EAn attempt to create the option definition file has failed.DetailsAn attempt to re-create an option definition file (/etc/opt
8. Messages514aa...aa: Start or stopActionNone.KAPL04045-IHDLM SNMP TRAP was sent. Trap ID = aa...aa, IP Address = bb...bb, Port Number= cc...cc, Comm
8. Messages5158.5 KAPL05001 to KAPL06000KAPL05003-IThe HDLM driver (filter component) was successfully attached to Disk (aa...aa), Partition (bb...bb)
8. Messages516aa...aa: Minor number of the sd or ssd device (decimal number)bb...bb: Slice number (decimal number)cc...cc: Error code (hexadecimal num
8. Messages517KAPL05019-IThe FO processing in the path (aa...aa) finished. The I/O request was processed in the path (bb...bb).Detailsaa...aa: Path ID
2. HDLM Functions32(2) When an Intermittent Error Does Not OccurIf an error does not occur in the path the specified number of times within the specif
8. Messages518cc...cc: 0 (fixed)ActionCheck the message of the HDLM command (dlnkmgr) or the HDLM manager, and then take the appropriate action. If yo
8. Messages519KAPL05041-EThe contents of the configuration definition file (dlmfdrv.conf) are invalid. (Instance = aa...aa) Execute the dlmsetconf com
8. Messages520The instance number of the HDLM filter driver instance that you tried to attach is already being used.aa...aa: Instance number (decimal
8. Messages521kernel/drv/dlmndrv.conf) of the filter driver or nexus driver is invalid.aa...aa: Driver nameActionCheck whether the path is correctly c
8. Messages522aa...aa: Path IDbb...bb: Error information (internal code)ActionStop any applications that are using the HDLM devices, and then re-execu
8. Messages523KAPL05904-EFailed to set device name. Execute the DLMgetras utility to collect error information, and then contact your vendor or mainte
8. Messages5248.6 KAPL06001 to KAPL07000KAPL06003-IInitialization of the HDLM alert driver (aa...aa) was successful.Detailsaa...aa: Address of the tab
8. Messages525ActionNone.KAPL06009-IInvalid IOCTL (aa...aa) was received. The processing is canceled.DetailsA request to the alert driver was made wit
8. Messages526written is discarded.Review the actual memory size when another error does not occur.When the actual memory size is insufficient, increa
8. Messages5278.7 KAPL07001 to KAPL08000KAPL07819-IData for maintenance: aa...aa bb...bb cc...cc dd...dd.DetailsThis message is generated by the core
2. HDLM Functions33and then manually place the path online.(3) When the Conditions for an Intermittent Error Are Changed During Error MonitoringWhen t
8. Messages5288.8 KAPL08001 to KAPL09000KAPL08019-EThe path (aa...aa) detected an error (bb...bb). (cc...cc)DetailsAn error occurred in the path. The
8. Messages529ee...ee: Target ID (same as PathName of view -path) (hexadecimal number)ff...ff: HLU number (same as PathName of view -path) (hexadecima
8. Messages530KAPL08027-EA path was excluded from the items subject to automatic failback. PathID = aa...aaDetailsA path was excluded from being subje
8. Messages5318.9 KAPL09001 to KAPL10000KAPL09002-EThe disk does not have sufficient free space.DetailsThe file system of the installation does not ha
8. Messages532Manually cancel the PP name registration, and then uninstall Hitachi Network Objectplaza Trace Library 2. If the attempt to cancel the r
8. Messages533An attempt to copy a file related to HDLM to the directory of Hitachi Command Suite products other than HDLM has failed.ActionIf you det
8. Messages534ActionSee 3.1.1 Hosts and OSs Supported by HDLM and install HDLM in a supported OS system.KAPL09029-EThis version of HDLM cannot be upda
8. Messages535None.KAPL09077-IThe temporary license was installed. The license expires on aa...aa.DetailsA temporary license was installed.aa...aa: Ye
8. Messages536The emergency license has been installed.aa...aa: Year (4 digits)/month (01-12)/day (01-31)ActionInstall a permanent license by the expi
8. Messages537You need to install a license because the license information cannot be acquired.ActionIn the case that the license key file is being pl
2. HDLM Functions34If you want to check whether intermittent error monitoring is being performed for the path, check the IEP item displayed when the d
8. Messages538Place the correct license key file in the designated directory (/var/tmp/hdlm_license), in a user-specified directory or with a user-spe
8. Messages539DetailsAn attempt to delete the license key file has failed.aa...aa: /var/tmp/hdlm_licenseActionIf a license key file exists, delete it.
8. Messages540ActionPlease perform the utility for collecting HDLM error information (DLMgetras), and acquire obstacle information, and then contact y
8. Messages541KAPL09148-WCould not modify file. File name = aa...aa, Details = bb...bb. Please contact product support.DetailsAn HDLM driver configura
8. Messages542KAPL09149-EAn attempt to update the file has failed. File name = aa...aa, Details = bb...bb. Please contact product support.DetailsAn HD
8. Messages543dlmfdrv.conf) by executing dlmsetconf utility.2. When you want to specify that a device is not to be managed by HDLM, edit the HDLM driv
8. Messages544More than two parameters have been specified for the installhdlm utility for installing HDLM.ActionMake sure that the parameters for ins
8. Messages545ActionFollow the message output at the same time.KAPL09203-WThere is no license key file. File name = aa...aaDetailsThere is no license
8. Messages546KAPL09208-EThere is no license key file. Renewal of the license key will now stop. File name = aa...aaDetailsThere is no license key fil
8. Messages547Check the error message that was output just before this message, and then perform the action indicated in that error message.KAPL09213-
2. HDLM Functions35When you disable the intermittent error monitoring function, information about paths not subject to automatic failback will be rese
8. Messages548You do not have write permission for the file system of the /var/tmp directory. Make sure you have access permissions for the file syste
8. Messages549ActionIf the error code is 9001,-1:You do not have read permissions for the installation information settings file. Make sure that you h
8. Messages550maintenance contract for HDLM.KAPL09220-WThe composition of the installation information settings file is invalid. Error Code = aa...aa
8. Messages551ActionSpecify the revised installation information settings file and then retry the operation.KAPL09228-WThe definition of the installat
8. Messages552bb...bb: Return value (decimal number) of the executed processingcc...cc: Line number (decimal number) of an installation information se
8. Messages553aa...aa: Error number (decimal number) that specifies the executed processingbb...bb: Return value (decimal number) of the executed proc
8. Messages554You do not have write permission for the installhdlm.log file.Modify your access permissions as necessary, and then retry the operation.
8. Messages555DetailsThe host will restart because restart was specified in the installation information settings file.ActionNone.KAPL09241-WAn attemp
8. Messages556The HDLM component installation utility (dlminstcomp) finished successfully.ActionNone.KAPL09246-EAn attempt to install an HDLM componen
8. Messages557An SP cannot be applied because HDLM is not installed on the system.ActionCheck whether HDLM has been correctly installed.KAPL09504-EThe
2. HDLM Functions362.10 Detecting Errors by Using Path Health CheckingHDLM can check the status of paths to which I/Os are not issued, at regular inte
8. Messages558DetailsA newer version of the SP (bb...bb) is already installed. Installation of SP (aa...aa) is stopped.aa...aa: The version of the SP
8. Messages559• If an installation is performed by using files copied from the DVD-ROM, re-copy all of the DVD-ROM files. After that, confirm the perm
8. Messages5608.10 KAPL10001 to KAPL11000KAPL10001-WNo parameter has been specified.DetailsNo directory to which the collected information will be out
8. Messages561ActionCheck the parameters of the DLMgetras utility for collecting HDLM error information, and then retry. For details on the DLMgetras
8. Messages562DetailsYou do not have write permission for the specified directory, or the creation of a subdirectory of the specified directory failed
8. Messages563Two or more file names or directory names exist in the file for defining the information to be collected.aa...aa: Line number of the fil
8. Messages564bb...bb: Indicated contents in a lineActionAfter the DLMgetras utility for collecting HDLM error information terminates, check the conte
8. Messages565DetailsA root "/" cannot be specified in a directory to which collected information is output. ActionCheck the parameters of t
8. Messages566KAPL10022-IThe utility for collecting HDLM error information completed normally.DetailsError information has been collected.ActionNone.
8. Messages567The file to collect does not exist.aa...aa: File to collectActionNone.KAPL10034-EThe file could not be copied. Filename = aa...aa, Detai
2. HDLM Functions372.11 Error ManagementFor troubleshooting purposes, HDLM collects information and stores it into log files. The error information to
8. Messages568company if you have a maintenance contract for HDLM.KAPL10049-IError information collection command = aa...aa, Return value = bb...bb, E
8. Messages569ActionCheck the capacity of the root file system or the file system including the directory specified by the -d option. Check the memory
8. Messages570KAPL10224-EAn error occurred when creating the configuration definition information.DetailsAn attempt to create a configuration definiti
8. Messages571KAPL10229-EInternal processing error.DetailsAn internal processing error occurred.ActionInternal processing error. Contact your HDLM ven
8. Messages572cc...cc: Errno stringActionRemove the error by referencing Errno, and then retry.KAPL10235-WGet symbolic link file(aa...aa) status faile
8. Messages573KAPL10238-WThe device (aa...aa) could not be opened. Errno = bb...bb (cc...cc)DetailsAn attempt to open an sd or ssd device failed.aa...
8. Messages574HDLM-managed sd or ssd device are deleted at reboot. To configure HDLM, enter y if you want to execute the dlmsetconf utility, enter n t
8. Messages575KAPL10252-WAn attempt to read the contents of symbolic link aa...aa failed. Function = readlink, errno = bb...bb (cc...cc)DetailsAn atte
8. Messages576Processing will stop because an incorrect value was entered three or more times for the message confirming the execution of the dlmsetco
8. Messages577If the disk indicated in Device is the LU that was dynamically deleted, no action is required. To prevent this message from being output
iiproblems that you might encounter.6. Command ReferenceChapter 6 describes all the HDLM commands.7. Utility ReferenceChapter 7 describes the HDLM uti
2. HDLM Functions38Figure 2-13: Flow of Data When Collecting Error InformationLogs might be collected in layers below HDLM, such as for the SCSI drive
8. Messages578DetailsAn attempt to acquire HDevList failed because the dlnkmgr view -path command failed.ActionRemove from the dlnkmgr view -path comm
8. Messages579KAPL10328-EThe entered value is invalid. The HDLM-configuration definition utility processing will now stop. Execute the HDLM-configurat
8. Messages580DetailsDisplays how to use dlmcfgmgr.ActionSpecify appropriate parameters, and then retry. For details on the dlmcfgmgr utility, see 7.3
8. Messages581DetailsA message could not be acquired from the message catalog.aa...aa: Errnobb...bb: Errno stringActionRemove the error by referencing
8. Messages582KAPL10376-EThe device (aa...aa) could not be opened. ErrorCode = bb...bb (cc...cc)DetailsAn attempt to open the device managing the HDLM
8. Messages583Contact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM.KAPL10380-EA parameter is invalid. Execu
8. Messages584KAPL10384-EThe value of the aa...aa property in the configuration definition file (bb...bb) is invalid. Execute the DLMgetras utility to
8. Messages585DetailsThe property value of the path described in the configuration definition file has the same value as a different LU path managed b
8. Messages586Check the capacity of the root file system or the file system including the file. Check the memory capacity which can be used.KAPL10391-
8. Messages587ActionContact your HDLM vendor or the maintenance company if there is a maintenance contract for HDLM.KAPL10396-WNo authority to execute
2. HDLM Functions39details, see the Solaris documentation.2.11.1 Types of Collected LogsHDLM collects information on detected errors and trace informa
8. Messages588KAPL10701-Iusage: dlmvxexclude [ -d dir | -h ]DetailsDisplays how to use dlmvxexclude.ActionSpecify appropriate parameters, and then ret
8. Messages589for Assisting Creation of the VxVM Configuration File.KAPL10705-EInternal processing error.DetailsAn internal error occurred while the d
8. Messages590KAPL10709-EAn error occurred when creating the file aa...aa.DetailsAn attempt to create a file has failed.aa...aa: File nameActionCheck
8. Messages591Check the system configuration and then execute the dlmsetconf utility for creating the HDLM driver configuration definition file.KAPL10
8. Messages592DetailsThe specified file name is not the name of a directory.aa...aa: Directory nameActionSpecify the correct directory.KAPL10717-EThe
8. Messages593KAPL10720-WThe entered value is invalid. Re-enter [y/n]:DetailsAn incorrect value was entered for the message confirming execution of th
8. Messages594Configuration File.KAPL10951-IThe LU (LDEV = aa...aa) was successfully deleted.DetailsThe LU was successfully deleted.aa...aa: LDEV name
8. Messages595KAPL10954-EMultiple paths have the same property (aa...aa) value for the LU (LDEV = bb...bb) that will be deleted. The LU configuration
8. Messages5968.11 KAPL11001 to KAPL12000KAPL11901-Iaa...aa has started.DetailsThe operation has started on the host.aa...aa: Operation (character str
8. Messages597None.KAPL11903-Iaa...aa has completed normally.DetailsThe operation has completed normally on the host.aa...aa: Any of the following ope
2. HDLM Functions40#When you want to configure the system so that HDLM messages are output to syslog, specify user for the facility in the /etc/syslog
8. Messages598• Clear Data• Get HDLM Driver Status• Get HDLM Manager Status• Get HDLM Alert Driver Status•Online• Offline• Get SNMP Trap Information•
8. Messages599KAPL11907-IXML reception - aa...aaDetailsThis information is required for resolving problems.aa...aa: XML information (character string)
8. Messages6008.12 KAPL13001 to KAPL14000KAPL13601-WThe audit log configuration file does not exist. Restart the HDLM Manager, and execute the "d
8. Messages601An internal error occurred during processing to read the audit log configuration file.ActionContact your HDLM vendor or the maintenance
8. Messages6028.13 KAPL15001 to KAPL16000KAPL15010-WThe HDLM utility was executed by the user who does not have the authority. Command Line = aa...aaD
8. Messages603aa...aa: Name of the utility that the user executedKAPL15026-IInformation about exclusion from VxVm management was successfully output.
8. Messages604dd...dd: Command that the user executedKAPL15104-Waa...aa path(s) were failed to place bb...bb. Command Line = cc...ccDetailsaa...aa: Nu
8. Messages605aa...aa: Command that the user executedKAPL15111-WThe HDLM command was started or stopped by the user who does not have the authority. C
8. Messages6068.14 Return Codes for Hitachi Command Suite Common Agent ComponentWhen an operation requested of HDLM from Global Link Manager terminate
8. Messages607ActionClick Refresh to update the host information, check the path status, and then retry the offline operation.1015DetailsThe Offline p
2. HDLM Functions41• Collects no error information.• Collects error information from the Error level and higher.• Collects error information from the
8. Messages608maintenance contract for HDLM. For details on the DLMgetras utility, see 7.2 The DLMgetras Utility for Collecting HDLM Error Information
8. Messages609An attempt to recover the path failed because of insufficient memory. Online processing will be stopped if online processing is running
8. Messages6101032DetailsAn attempt to recover the path failed because the correct disk label has not been set in the LU for the path to be put online
8. Messages611utility for collecting HDLM error information to collect the error information, and then contact your HDLM vendor or maintenance company
8. Messages612ActionRefresh the host information, check the path status, and then perform the operation again.1045DetailsA parameter is invalid.Action
613AppendixesA. Sun Cluster 3.2 CommandsB. Functional Differences Between Versions of HDLMC. Glossary
A. Sun Cluster 3.2 Commands614A. Sun Cluster 3.2 CommandsTable A-1: Correspondence Between Sun Cluster 3.1 Commands and Sun Cluster 3.2 Commands shows
A. Sun Cluster 3.2 Commands615#1Execute this command in step 13 in (10) Set Up Sun Cluster of 3.5.1 Preparations for a New Installation of HDLM and in
B. Functional Differences Between Versions of HDLM616B. Functional Differences Between Versions of HDLMThis section explains the functional difference
C. Glossary617C. GlossaryThis glossary explains the terms used in this manual.Aautomatic failbackA function for checking the status of paths at regula
2. HDLM Functions422.12 Collecting Audit Log DataHDLM and other Hitachi storage-related products provide an audit log function so that compliance with
C. Glossary618DDevA logical division of an LU that HDLM controls and operates. A Dev is equivalent to a slice or a partition in Solaris.In Solaris, ea
C. Glossary619failoverA function for switching to another normal path if there is an error in the current access path, thereby enabling the system to
C. Glossary620A host device name is assigned using the cUtXdY format.The variables used in cUtXdY indicate the following:U: Controller number reserved
C. Glossary621• The Extended Least Blocks algorithmlocal boot disk environmentAn environment in which a boot disk is located on the host.logical devic
C. Glossary622(See also: owner path, non-owner controller)owner pathA path that passes through an owner controller for an LU in the Thunder 9500V Seri
C. Glossary623RreservationThe reservation function enables a host to declare that it has exclusive rights to use a particular LU, and prevents other h
625IndexSymbols/etc/system filesetup 105/kernel/drv/sd.conf filesetup 104Aabbreviations defined iiiactive host 53addinga new logical unit 292audit log
Index626cUtXdYsZ 14Ddefault and recommended values 377Dev 7, 8, 618Dev number 618diagram conventions viidirectory to which collected information is ou
Index627path error 347HBA 8HBA (Host Bus Adapter) 619hbsa.tar.Z 440HDev 10HDevName 346HDLMfeatures 4functions 5installing 101, 110, 118installing with
2. HDLM Functions43The categories of audit log data that can be collected differ depending on the product. The following sections explain only the cat
Index628INSTALLATION_SETTINGS 468installhdlm 468installhdlm.log 475installingHDLM 110, 118HDLM with Sun Cluster 118HDLM without Sun Cluster 110install
Index629Oobtainingpath information 348program information 352offline 23, 363offline(C) status 27offline(E) status 27online 23, 370online status 27onli
Index630HDLM manager 283in Solaris 10 270statistics 358clearing to the initial value 358status transitions 28stoppingHDLM manager 283storage systems 2
2. HDLM Functions44Table 2-9: Categories and Audit Events that Can Be Output to the Audit LogCategory Explanation Audit eventSeverity#1Message IDStart
2. HDLM Functions45ConfigurationAccess Viewing or updating configuration informationInitialization of path statistics was successful.6 KAPL15101-IInit
2. HDLM Functions46#1The severity levels are as follows:3: Error, 4: Warning, 6: Informational#2If you use Ctrl + C to cancel the DLMgetras utility fo
2. HDLM Functions47example, an HDLM utility is executed from external media.##:The following audit log data is output:• Categories: StartStop, Authent
iiiConventions: AbbreviationsThis manual uses the following abbreviations for product names.Abbreviation Full name or meaningDevice Manager Agent Devi
2. HDLM Functions48Filtering by category:The following categories can be specified:•StartStop• Authentication• ConfigurationAccess• All of the aboveFo
2. HDLM Functions49sage-ID,date-and-time,entity-affected,location-affected,audit-event-type,audit-event-result,subject-ID-for-audit-event-result,hardw
2. HDLM Functions50#: The output of this item depends on the audit event.Example of the message section for the audit event An attempt to display HDLM
2. HDLM Functions512.13 Integrated HDLM management using Global Link ManagerBy using Global Link Manager, you can perform integrated path management o
2. HDLM Functions52Figure 2-14: Example System Configuration Using HDLM and Global Link Manager
2. HDLM Functions532.14 Cluster SupportHDLM can also be used in cluster configurations.For details on cluster software supported by HDLM, the supporte
55Chapter3. Creating an HDLM EnvironmentThis chapter describes the procedures for setting up an HDLM environment and the procedure for canceling those
3. Creating an HDLM Environment563.1 HDLM System RequirementsCheck the following before installing HDLM:3.1.1 Hosts and OSs Supported by HDLMYou can i
3. Creating an HDLM Environment57• Hitachi Universal Storage Platform 100• Hitachi Universal Storage Platform 600• Hitachi Universal Storage Platform
ivHP XP512 HP StorageWorks Disk Array XP512HP XP1024 HP StorageWorks XP1024 Disk ArrayHP XP10000 HP StorageWorks XP10000 Disk ArrayHP XP12000 HP Stora
3. Creating an HDLM Environment58• HP XP10000/HP XP12000/HP XP20000/HP XP24000• SVS(2) HBAsFor details on the applicable HBAs, see the HDLM Release No
3. Creating an HDLM Environment59#4You must apply MP2 or later when using the I/O fencing function. The I/O fencing function can be used only when Hit
3. Creating an HDLM Environment60#1When used with the Thunder 9500V series, Lightning 9900V series, Hitachi USP, Hitachi AMS2000/AMS/TMS/WMS/SMS serie
3. Creating an HDLM Environment61SVM 1.0#4VxVM 4.1#5VxVM 5.0#5Sun Cluster 3.1#1 #5NoneSVM 1.0#6Sun Cluster 3.1 (9/04)#1 #5NoneSVM 1.0#6Sun Cluster 3.1
3. Creating an HDLM Environment62#1In either of the following cases, the load balancing function is disabled because a reservation is issued to one of
3. Creating an HDLM Environment63Does not support the I/O fencing function.#3Does not support linkage with SFVS (Storage Foundation Volume Server).#4D
3. Creating an HDLM Environment64#11For a two-node configuration, the pathcount setting is only supported for the SCSI protocol (fencing protocol) of
3. Creating an HDLM Environment65(3) When Creating an Oracle RAC 10g EnvironmentRequired programsTable 3-5: Programs required to create an Oracle RAC
3. Creating an HDLM Environment66Vo l u m e M a n a g e r A S M • ASM is bundled with Oracle RAC 10g.• ASM is used as the disk memory area for files
3. Creating an HDLM Environment67Cluster Oracle Clusterware 10.1.0.5.0 --Volume Manager None (Specify an HDLM raw device)--Configuration 5 OS Solaris
vThis manual also uses the following abbreviations.UNIX A generic term for:• AIX• Solaris• Linux• HP-UXVirtual Storage Platform A generic term for:• H
3. Creating an HDLM Environment68Table 3-6: Programs required to create an Oracle RAC 10g environment (For Solaris 10)ConfigurationProgram RemarksConf
3. Creating an HDLM Environment69Volume Manager ASM • ASM is bundled with Oracle RAC 10g.• ASM is used as the disk memory area for files and recovery
3. Creating an HDLM Environment70Cluster Sun Cluster 3.1 8/05 and Oracle Clusterware 10.2.0.2.0Volume Manager None (Specify an HDLM raw device by the
3. Creating an HDLM Environment71Volume Manager ASM • ASM is bundled with Oracle RAC 10g.• ASM is used as the disk memory area for files and recovery
3. Creating an HDLM Environment72Configuration 12OS Solaris 10 --Oracle RAC 10g Oracle 10g Database 10.2.0.3.0 Only two-node configurations are suppor
3. Creating an HDLM Environment73Configuration 15OS Solaris 10 --Oracle RAC 10g Oracle 10g Database 10.2.0.3.0 --Cluster Oracle Solaris Cluster 3.3 an
3. Creating an HDLM Environment74Configuration 18OS Solaris 10 --Oracle RAC 10g Oracle 10g Database 10.2.0.4.0 Only two-node configurations are suppor
3. Creating an HDLM Environment75#You must apply MP1 or later.Required patchesTable 3-7: Patches required to create an Oracle RAC 10g environment (For
3. Creating an HDLM Environment76#When using Oracle RAC 10g 10.2.0.1.0, apply 108993-45, not 108993-19.Table 3-8: Patches required to create an Oracle
3. Creating an HDLM Environment77Change the value of MISSCOUNT to the following value or greater: (number-of-paths-connected-to-the-voting-disk x 60 s
Commenti su questo manuale