Hitachi Dynamic Link Manager (for Linux ) Release Notes

Transcription

1 Hitachi Dynamic Link Manager (for Linux ) Release Notes Contents About this document... 1 Intended audience... 1 Getting help... 2 About this release... 2 Product package contents... 2 New features and important enhancements... 2 System requirements... 2 Resolved problems... 6 Known problems... 6 Closing known problems Installation precautions Usage precautions Documentation Appendix A Copyrights and licenses About this document This document () provides late-breaking information about the Hitachi Dynamic Link Manager (for Linux) It includes information that was not available at the time the technical documentation for this product was published, as well as a list of known problems and solutions. Intended audience This document is intended for customers and Hitachi Data Systems partners who license and use the Hitachi Dynamic Link Manager (for Linux). 2014, 2015, Hitachi, Ltd. All rights reserv ed. 1

2 Getting help Getting help The Hitachi Data Systems Support Center staff is available 24 hours a day, seven days a week. To reach us, please visit the support website at for current telephone numbers and other contact information. If you purchased this product from an authorized HDS reseller, contact that reseller for support. About this release This release is a major release that adds new features and fixes bug. Product package contents Medium CD-ROM Revision Release Type Software D ocume nts Hitachi Dynamic Link Manager (for Linux) Release Notes (this document) Full Package MK-92DLM Hitachi Command Suite Dynamic Link Manager (for Linux ) User Guide Statement of Delivery and Usage Consent Form New features and important enhancements [ Additional Functions and Modifications] (1) Functionality for specifying the number of times the same path can be used for extended load balancing (random I/O) is now supported. System requirements Refer to Chapter 3. Creating an HDLM Environment of the Hitachi Command Suite Dynamic Link Manager (for Linux ) User Guide. Host For details on supported hosts, refer to the following manual: 3. Creating an HDLM Environment - HDLM System Requirements - Hosts and OSs Supported by HDLM Supported OSs in a HAM environment are listed below: 2014, 2015, Hitachi, Ltd. All rights reserv ed. 2

3 System requirements Supported OS AS4/ES4(x86/x64/IPF) 5(x86/x64/IPF) Server 9(x86/x64/IPF) Server 10(x86/x64/IPF) Host bus adapter (HBA) For information on supported HBAs and drivers, refer to Appendix A - Host Bus Adapter (HBA) Support Matrix. Storage For details on supported storage subsystems, refer to the following manual: 3. Creating an HDLM Environment - HDLM System Requirements - Storage Subsystems Supported by HDLM Requirements to use a HAM environment are as follows: - HDLM supports the HAM functionality of the following storage system: - Hitachi Universal Storage Platform V/VM - Hitachi Virtual Storage Platform - HP XP24000/XP HP P Hitachi Unified Storage VM 2014, 2015, Hitachi, Ltd. All rights reserv ed. 3

4 System requirements The required microprogram versions are listed below: Storage system Interface Microprogram version Universal Storage Platform V/VM FC I/F XX/XX or later Virtual Storage Platform FC I/F XX/XX or later (*1) XP24000/XP20000 FC I/F XX/XX or later P9500 FC I/F XX/XX or later (*1) Hitachi Unified Storage VM FC I/F X-XX/XX or later Remark X: voluntary number X: voluntary number X: voluntary number X: voluntary number X: voluntary number *1: If you use the HAM functionality with USP V or XP24000, apply XX/XX or later. Virtualization The virtualization to which HDLM can be applied is shown below: Hitachi Virtualization Manager (Hitachi Compute Blade with Itanium 2 server modules) Xen (Virtualization) in Server 10 SP2, SP3, SP4, SUSE LINUX Enterprise Server 11, and Server 11 SP1, SP3 KVM (Virtualization) in 5.4 Advanced Platform, Red Hat Enterprise Linux 5.4, 5.5 Advanced Platform, Red Hat Enterprise Linux 5.5, 5.6 Advanced Platform, Red Hat Enterprise Linux 5.6, 5.7 Advanced Platform, Red Hat Enterprise Linux 5.7, 5.8 Advanced Platform, Red Hat Enterprise Linux 5.8, 5.9 Advanced Platform, Red Hat Enterprise Linux 5.9, 5.10 Advanced Platform, Red Hat Enterprise Linux 5.10, 5.11 Advanced Platform, Red Hat Enterprise Linux 5.11, 6, 6.1, 6.2, 6.3, Red Hat Enterprise Linux 6.4, 6.5, 6.6, Red Hat Enterprise Linux 7, Oracle Linux 7, Oracle Unbreakable Enterprise Kernel 5.6, Oracle Unbreakable Enterprise Kernel 5.7, Oracle Unbreakable Enterprise Kernel 5.8, Oracle Unbreakable Enterprise Kernel 6.2, Oracle Unbreakable Enterprise Kernel 6.3, Oracle Unbreakable Enterprise Kernel 6.4, Oracle Unbreakable Enterprise Kernel 6.5, and Oracle Unbreakable Enterprise Kernel 7 Operating systems requirements For details on supported operating systems, refer to the following manual: 3. Creating an HDLM Environment - HDLM System Requirements - Hosts and OSs Supported by HDLM 2014, 2015, Hitachi, Ltd. All rights reserv ed. 4

5 System requirements Prerequisite programs None. Related programs For details on related programs, refer to the following manual: 3. Creating an HDLM Environment - HDLM System Requirements - Related Products When Using AS4/ES4 3. Creating an HDLM Environment - HDLM System Requirements - Related Products When Using 5 3. Creating an HDLM Environment - HDLM System Requirements - Related Products When Using 6 3. Creating an HDLM Environment - HDLM System Requirements - Related Products When Using 7 3. Creating an HDLM Environment - HDLM System Requirements - Related Products When Using Server Creating an HDLM Environment - HDLM System Requirements - Related Products When Using Server Creating an HDLM Environment - HDLM System Requirements - Related Products When Using Oracle Enterprise Linux 4 3. Creating an HDLM Environment - HDLM System Requirements - Related Products When Using Oracle Enterprise Linux 5 3. Creating an HDLM Environment - HDLM System Requirements - Related Products When Using Oracle Unbreakable Enterprise Kernel 5 3. Creating an HDLM Environment - HDLM System Requirements - Related Products When Using Oracle Unbreakable Enterprise Kernel 6 3. Creating an HDLM Environment - HDLM System Requirements - Related Products When Using Oracle Linux , 2015, Hitachi, Ltd. All rights reserv ed. 5

6 Resolved problems 3. Creating an HDLM Environment - HDLM System Requirements - Related Products When Using Oracle Unbreakable Enterprise Kernel 7 Memory and disk space requirements For details on memory and disk space requirements, refer to the following manual: 3. Creating an HDLM Environment - HDLM System Requirements - Memory and Disk Space Requirements HDLM supported configurations For details on the condition that HDLM can manage space requirements, refer to the following manual: 3. Creating an HDLM Environment - HDLM System Requirements - Number of Paths Guaranteed in HDLM Resolved problems [ Modifications] (1) The following problem has been corrected: The system may hang up if you execute I/O by using a file system on the following OSs: Oracle Enterprise Linux 4 - Oracle Enterprise Linux 5 - Server 10 - Server 11 SP0 [Conditions] This symptom may occur when both of the following conditions are met: 1) Any of the following OS environments is used: Oracle Enterprise Linux 4 - Oracle Enterprise Linux 5 - Server 10 - Server 11 SP0 2014, 2015, Hitachi, Ltd. All rights reserv ed. 6

7 Know n problems 2) I/O is executed by using a file system. [Case ID] HDS Known problems If an environment is created in which HDLM is installed on the boot disk, the server is started, and a module name contains a hyphen (-), even if the module is successfully loaded, a message indicating that the module failed to load (KAPL12324-E) might be output to the console and the /etc/opt/dynamiclinkmanager/hdlmboot.log file. After the server has started, execute the lsmod command. If the hyphens in module names are changed and displayed as underscores (_), then there are no problems, and the action for the KAPL12324-E message in the Hitachi Command Suite Dynamic Link Manager (for Linux ) User Guide does not need to be taken. Message output example (example of an error occurring for dm-region-hash) # vi /etc/opt/dynamiclinkmanager/hdlmboot.log : KAPL12323-I The insertion of the module was started. Module name = dm-log KAPL12323-I The insertion of the module was started. Module name = dmregion-hash KAPL12324-E The module could not be inserted. Module name = dm-region-hash KAPL12323-I The insertion of the module was started. Module name = dm-mirror : # Example of using lsmod to confirm that there are no problems (example of confirming the information displayed for dm_region_hash) # lsmod : dm_mirror dm_region_hash dm_log : # dm_mirror dm_mirror,dm_region_hash 2014, 2015, Hitachi, Ltd. All rights reserv ed. 7

8 Know n problems Operation when all paths are disconnected during intermittent error monitoring: When I/O operations are performed continuously for an LU whose paths are all Offline(E), Online(E), or Offline(C) (because, for example, all paths have been disconnected), the number of times that an error occurs (the IEP value when dlnkmgr view -path -iem is executed) during intermittent error monitoring might increase even though the auto failback function did not recover all paths. In such a case, even though an intermittent error did not occur, HDLM often assumes an intermittent error, and excludes paths from the auto failback function. In such a case, after recovery from the failure, to change the status of a path excluded from auto failback to online, manually change the status to online. Although the following messages are output when executing the "rpm -V HDLM" command, HDLM operations are not affected. In AS4/ES4 (IA32/IPF), AS4.5/ES4.5 (IA32/IPF), AS4.6/ES4.6 (IA32/IPF), AS4.7/ES4.7 (IA32/IPF), AS4.8/ES4.8 (IA32/IPF), AS4.9/ES4.9 (IA32/IPF), 5 Advanced Platform (IA32/IPF), 5 (IA32/IPF), 5.1 Advanced Platform (IA32/IPF), 5.1 (IA32/IPF), 5.2 Advanced Platform (IA32/IPF), 5.2 (IA32/IPF), 5.3 Advanced Platform (IA32/IPF), 5.3 (IA32/IPF), 5.4 Advanced Platform (IA32/IPF), 5.4 (IA32/IPF), 5.5 Advanced Platform (IA32/IPF), 5.5 (IA32/IPF), 5.6 Advanced Platform (IA32/IPF), 5.6 (IA32/IPF), 5.7 Advanced Platform (IA32/IPF), 5.7 (IA32/IPF), 5.8 Advanced Platform (IA32/IPF), 5.8 (IA32/IPF), 5.9 Advanced Platform (IA32/IPF), 5.9 (IA32/IPF), 5.10 Advanced Platform (IA32/IPF), 5.10 (IA32/IPF), 5.11 Advanced Platform (IA32/IPF), 5.11 (IA32/IPF), 6, 6.1, 6.2, 6.3, 6.4, 6.5, 6.6, 2014, 2015, Hitachi, Ltd. All rights reserv ed. 8

9 Know n problems Oracle Enterprise Linux 4 Update 5, Oracle Enterprise Linux 4 Update 6, Oracle Enterprise Linux 5 Update 1, Oracle Enterprise Linux 5.4, Oracle Enterprise Linux 5.5, Oracle Enterprise Linux 5.6, Oracle Unbreakable Enterprise Kernel 5.7, Oracle Unbreakable Enterprise Kernel 5.8, Oracle Unbreakable Enterprise Kernel 6.2, Oracle Unbreakable Enterprise Kernel 6.3, Oracle Unbreakable Enterprise Kernel 6.4, and Oracle Unbreakable Enterprise Kernel 6.5 missing /etc/opt/dynamiclinkmanager/dlmmgr_e.xml - In case of AS4/ES4, AS4.5/ES4.5, AS4.6/ES4.6, AS4.7/ES4.7, AS4.8/ES4.8, AS4.9/ES4.9, 5 Advanced Platform, 5, 5.1 Advanced Platform, 5.1, 5.2 Advanced Platform, 5.2, 5.3 Advanced Platform, 5.3, 5.4 Advanced Platform, 5.4, 5.5 Advanced Platform, 5.5, 5.6 Advanced Platform, 5.6, 5.7 Advanced Platform, 5.7, 5.8 Advanced Platform, 5.8, 5.9 Advanced Platform, 5.9, 5.10 Advanced Platform, 5.10, 5.11 Advanced Platform, 5.11, 6, 6.1, 2014, 2015, Hitachi, Ltd. All rights reserv ed. 9

10 Know n problems 6.2, 6.3, 6.4, 6.5, 6.6, 7, Oracle Enterprise Linux 4 Update 5, Oracle Enterprise Linux 4 Update 6, Oracle Enterprise Linux 5 Update 1, Oracle Enterprise Linux 5.4, Oracle Enterprise Linux 5.5, Oracle Enterprise Linux 5.6, Oracle Linux 7, Oracle Unbreakable Enterprise Kernel 5.6, Oracle Unbreakable Enterprise Kernel 5.7, Oracle Unbreakable Enterprise Kernel 5.8, Oracle Unbreakable Enterprise Kernel 6.2, Oracle Unbreakable Enterprise Kernel 6.3, Oracle Unbreakable Enterprise Kernel 6.4, Oracle Unbreakable Enterprise Kernel 6.5, and Oracle Unbreakable Enterprise Kernel 7 missing /etc/opt/dynamiclinkmanager/dlmmgr_e.xml missing /opt/dynamiclinkmanager/lib/libdlm.so_32 missing /opt/dynamiclinkmanager/lib/libdlmgui_jni.so_32 missing /opt/dynamiclinkmanager/lib/libhdlmhcc-x.x.x.so_32 (*1) missing /opt/dynamiclinkmanager/lib/libhdlmhccmp-x.x.x.so_32 (*1) - Server 10 (IA32/IPF), and Server 11 (IA32/IPF) missing /etc/opt/dynamiclinkmanager/dlmmgr_e.xml - Server 10, and Server 11 missing /etc/opt/dynamiclinkmanager/dlmmgr_e.xml missing /opt/dynamiclinkmanager/lib/libdlm.so_32 missing /opt/dynamiclinkmanager/lib/libdlmgui_jni.so_32 missing /opt/dynamiclinkmanager/lib/libhdlmhcc-x.x.x.so_32 (*1) missing /opt/dynamiclinkmanager/lib/libhdlmhccmp-x.x.x.so_32 (*1) 2014, 2015, Hitachi, Ltd. All rights reserv ed. 10

11 Closing know n problems Notes: *1: voluntary number. While installation and uninstallation of HDLM are performed, do not interrupt the processing (for example, do not press the Ctrl+C keys). If there are 1025 or more paths, including those other than Online, you cannot execute the dlmchname utility. If the operation is performed with the following procedure, the status is returned to what it was before the refresh operation was executed. As a result, make sure to re-execute the refresh command after restarting the host and recovering from a path failure. (a) The dlnkmgr command is used to perform a refresh. (b) Path errors occur for some or all of the paths, and a path status becomes Offline(E). (c) The host is restarted before a path failure is recovered. The partition numbers that can be used for HDLM management targets are from 1 to 15. A partition number of 16 or higher can be assigned in UEFI, but a SCSI device with a partition number of 16 or higher cannot be used for an HDLM management target. An HDLM device cannot be specified on a boot disk in a RHEL7 and Oracle Linux 7 environment The KAPL12354-E error occurs when an initial RAM disk image file is created for HDLM. Execution example: # dracut /boot/initramfs el7.x86_64.img `uname -r` KAPL12354-E In the current OS version, HDLM does not support the boot disk. # Closing known problems None 2014, 2015, Hitachi, Ltd. All rights reserv ed. 11

12 Installation precautions Installation precautions For Hitachi Dynamic Link Manager and later, the HDLM installation media has been changed to a DVD-ROM. Also, the directory structure of the HDLM installation media has changed. Refer to Contents_list.txt on the HDLM installation media, and then replace the descriptions regarding the HDLM installation media directories in the Hitachi Command Suite Dynamic Link Manager (for Linux ) User Guide. For details on HDLM installation, refer to the following manual: 2. HDLM Functions - Failover and Failback Using Path Switching 3. Creating an HDLM Environment - HDLM System Requirements - Hosts and OSs Supported by HDLM 3. Creating an HDLM Environment - HDLM System Requirements - Related Products When Using AS4/ES4 3. Creating an HDLM Environment - HDLM System Requirements - Related Products When Using 5 3. Creating an HDLM Environment - HDLM System Requirements - Related Products When Using 6 3. Creating an HDLM Environment - HDLM System Requirements - Related Products When Using 7 3. Creating an HDLM Environment - HDLM System Requirements - Related Products When Using Server Creating an HDLM Environment - HDLM System Requirements - Related Products When Using Server Creating an HDLM Environment - HDLM System Requirements - Related Products When Using Oracle Enterprise Linux 4 3. Creating an HDLM Environment - HDLM System Requirements - Related Products When Using Oracle Enterprise Linux 5 3. Creating an HDLM Environment - HDLM System Requirements - Related Products When Using Oracle Unbreakable Enterprise Kernel , 2015, Hitachi, Ltd. All rights reserv ed. 12

13 Usage precautions 3. Creating an HDLM Environment - HDLM System Requirements - Related Products When Using Oracle Unbreakable Enterprise Kernel 6 3. Creating an HDLM Environment - HDLM System Requirements - Related Products When Using Oracle Linux 7 3. Creating an HDLM Environment - HDLM System Requirements - Related Products When Using Oracle Unbreakable Enterprise Kernel 7 3. Creating an HDLM Environment - Knowledge Required Before You Install HDLM 3. Creating an HDLM Environment - Notes on Creating an HDLM Environment 3. Creating an HDLM Environment - Installing HDLM for Managing Boot Disks - Notes on Installing HDLM in a Boot Disk Environment 3. Creating an HDLM Environment - The Process-specific-trace Information File - Notes on Using the Hitachi Network Objectplaza Trace Library Updating installation of HDLM precautions For details on updating HDLM, refer to the following manual: 3. Creating an HDLM Environment - Notes on Creating an HDLM Environment - Notes on Installing HDLM Uninstallation precautions For details on HDLM uninstallation, refer to the following manual: 3. Creating an HDLM Environment - Canceling the Settings for HDLM - Uninstalling HDLM System generation precautions None. Usage precautions For details on usage precautions when using HDLM, refer to the following manual: 2014, 2015, Hitachi, Ltd. All rights reserv ed. 13

14 Usage precautions 2. HDLM Functions - Load Distribution Using Load Balancing - Algorithms for Load Balancing 2. HDLM Functions - Failover and Failback Using Path Switching - Path Status Transition 2. HDLM Functions - Cluster Support 3. Creating an HDLM Environment - HDLM System Requirements - Related Products When Using AS4/ES4 3. Creating an HDLM Environment - HDLM System Requirements - Related Products When Using 5 3. Creating an HDLM Environment - HDLM System Requirements - Related Products When Using 6 3. Creating an HDLM Environment - HDLM System Requirements - Related Products When Using 7 3. Creating an HDLM Environment - HDLM System Requirements - Related Products When Using Server Creating an HDLM Environment - HDLM System Requirements - Related Products When Using Server Creating an HDLM Environment - HDLM System Requirements - Related Products When Using Oracle Enterprise Linux 4 3. Creating an HDLM Environment - HDLM System Requirements - Related Products When Using Oracle Enterprise Linux 5 3. Creating an HDLM Environment - HDLM System Requirements - Related Products When Using Oracle Unbreakable Enterprise Kernel 5 3. Creating an HDLM Environment - HDLM System Requirements - Related Products When Using Oracle Unbreakable Enterprise Kernel 6 3. Creating an HDLM Environment - HDLM System Requirements - Related Products When Using Oracle Linux , 2015, Hitachi, Ltd. All rights reserv ed. 14

15 Usage precautions 3. Creating an HDLM Environment - HDLM System Requirements - Related Products When Using Oracle Unbreakable Enterprise Kernel 7 3. Creating an HDLM Environment - Settings for md Devices - Notes on Settings Up md Devices 3. Creating an HDLM Environment - Settings for LVM 3. Creating an HDLM Environment - Settings for Oracle RAC 3. Creating an HDLM Environment - Settings for the RHCM - Notes on Using RHCM 3. Creating an HDLM Environment - Canceling the Settings for HDLM - Canceling the Settings for LVM 3. Creating an HDLM Environment - Canceling the Settings for HDLM - Uninstalling HDLM 4. HDLM Operation - Notes on Using HDLM 4. HDLM Operation - Notes on Using Commands 4. HDLM Operation - HDLM Operations Using Commands - Updating the License 4. HDLM Operation - Starting and Stopping the HDLM Manager 4. HDLM Operation - Reconfiguring the HDLM Operating Environment - Changing the HDLM Device Configuration 5. Troubleshooting - Actions Taken for a Path Error - Place the Path Online 6. Command Reference - Overview of the HDLM Command (dlnkmgr) 7. Utility Reference - Overview of the Utilities 7. Utility Reference - DLMgetras (Utility for Collecting HDLM Error Information) - Parameters 2014, 2015, Hitachi, Ltd. All rights reserv ed. 15

16 Usage precautions 7. Utility Reference - dlmcfgmgr (HDLM-Configuration Definition Utility) - Parameters 7. Utility Reference - dlmsetopt (Utility for Setting HDLM Driver Option) 8.Messages - Before Viewing the List of Messages - Components That Output Messages to syslog - Hitachi Command Suite Dynamic Link Manager (for Linux ) User Guide Notes on Linux Commands and Files - Hitachi Command Suite Dynamic Link Manager (for Linux ) User Guide Differences in Functionality Between HDLM Versions Additional Usage Precautions Note that if descriptions include the term or Red Hat Enterprise Linux 5, and there is no specific explanation about Red Hat Enterprise Linux 6, read them as 6 when necessary. When using an Emulex HBA driver, and if you execute the HDLM-configuration definition utility (dlmcfgmgr -v), a hyphen (-) might be displayed in the Device column of the execution results. To change to a status that does not display a hyphen, execute the dlmcfgmgr utility with the -u parameter specified. For details on the dlmcfgmgr utility, see dlmcfgmgr Utility for Managing the HDLM Configuration. Settings of OS and other programs, which were changed at HDLM introduction, must be returned to the original settings after the uninstallation of HDLM. Version numbers are displayed as follows after this version of HDLM is installed. Function Item Version number HDLM command (dlnkmgr) HDLM Version HDLM Manager HDLM Alert Driver HDLM Driver , 2015, Hitachi, Ltd. All rights reserv ed. 16

17 Usage precautions The following example shows the text displayed when dlnkmgr view -sys is executed. # /opt/dynamiclinkmanager/bin/dlnkmgr view -sys HDLM Version : Service Pack Version : Load Balance Support Cluster : Elog Level : 3 Elog File Size (KB) : 9900 Number Of Elog Files : 2 Trace Level : 0 Trace File Size (KB) : 1000 Number Of Trace Files : 4 Path Health Checking Auto Failback : on(extended lio) : on(1) Reservation Status : Intermittent Error Monitor Dynamic I/O Path Control HDLM Manager Ver : on(30) : off : off(10) WakeupTime Alive /01/15 19:03:42 HDLM Alert Driver Ver WakeupTime ElogMem Size Alive /01/15 19:02: HDLM Driver Ver WakeupTime Alive /01/15 19:02:24 License Type Expiration Temporary 2015/01/17(2days after) KAPL01001-I The HDLM command completed normally. Operation name = view, completion time = 2015/01/15 20:22:01 This version of HDLM does not support the virtualization (the Xen function) provided by AS4.5/ES4.5, AS4.6/ES4.6, AS4.7/ES4.7, AS4.8/ES4.8, AS4.9/ES4.9, 5 Advanced Platform, 5, , 2015, Hitachi, Ltd. All rights reserv ed. 17

18 Usage precautions Advanced Platform, 5.1, 5.2 Advanced Platform, 5.2, 5.3 Advanced Platform, 5.3, 5.4 Advanced Platform, 5.4, 5.5 Advanced Platform, 5.5, 5.6 Advanced Platform, 5.6, 5.7 Advanced Platform, 5.7, 5.8 Advanced Platform, 5.8, 5.9 Advanced Platform, 5.9, 5.10 Advanced Platform, 5.10, 5.11 Advanced Platform, 5.11, 6, 6.1, 6.2, Red Hat Enterprise Linux 6.3, 6.4, 6.5, Red Hat Enterprise Linux 6.6, 7, and Oracle Linux 7. HDLM cannot be used in the domain 0 and the domain U of the virtualization (the Xen function). HDLM cannot be installed on an unsupported OS. Even if the installation is successful, the operation cannot be guaranteed. If HDLM is used with LifeKeeper for Linux, the following message may be output to the LifeKeeper for Linux log, but there is no effect on operation: quickcheck: The daemon "dlmmgr" was restarted by quickcheck. quickcheck: The daemon "dlmmgr" does not appear to be running and could not be restarted. Path failures may not be correctly handled without this daemon. Execute the following command to check whether the HDLM manager is running: # /opt/dynamiclinkmanager/bin/dlnkmgr view -sys -msrv HDLM Manager Ver Alive WakeupTime yyyy/mm/dd hh:mm:ss KAPL01001-I The HDLM command ended successfully. (operation name = view, end time = yyyy/mm/dd hh:mm:ss) When all of the following conditions are met, if you execute the shutdown command with specifying the -F option which always executes fsck at reboot, a host boot fails with an error in the fsck command which is executed at the OS boot. If your environment meets the conditions, do not specify the -F option for the shutdown command. If you do execute the shutdown command with the -F option specified, when the setup screen for the boot loader startup is displayed, select the startup from the SCSI device and boot the host. After that, reboot the host without specifying the -F option. Conditions 2014, 2015, Hitachi, Ltd. All rights reserv ed. 18

19 Usage precautions - AS4/ES4, 5, Oracle Enterprise Linux 4, Oracle Enterprise Linux 5, or Oracle Unbreakable Enterprise Kernel 5 is used. - An HDLM device is used as a boot disk. - A value other than 0 is set for the sixth field (fs_passno) in the /etc/fstab file. - UTC is not used for the system clock on the host. If you restart the host, the route information changes and an increased number of offline (E) paths per LU might be displayed. If the number of online paths per LU is the same as before the host was restarted, remove unnecessary offline (E) paths by using dlmcfgmgr -u {HDLM device}. In 6, Oracle Unbreakable Enterprise Kernel 5, Oracle Unbreakable Enterprise Kernel 6, and Server 11: If you execute the dlmcfgmgr utility (dlmcfgmgr -u), path information is deleted when a path failure occurs. The path information is deleted even if a hyphen (-) is not displayed for an SCSI device name in the device row displayed as a result of executing the dlmcfgmgr utility or the HDLM command view operation (specifying -lu or -drv). If path information is deleted as described above, execute dlmcfgmgr -r after recovering the failed path, make sure the recovered path is discovered by HDLM, and then confirm that the path status has become online. HDLM for Linux does not support cluster software in a HAM environment. In the case of displaying the LU information, the HAM information is not output by specifying the "all" parameter-value for the HDLM command. Specify the "ha" and "hastat" parameter-value instead of it. An online operation is performed on an owner path, a non-owner path's status may change to Offline(E). After performing an online operation on an owner path, use the HDLM command to make sure that the non-owner path's status is Online. If the non-owner path's status is Offline(E), change the status of HAM pairs to PAIR, and then perform an online operation on the Offline(E) path again. When you set up a HAM pair to be managed by HDLM, make sure that the host recognizes paths to the MCU (Primary VOL) and RCU (Secondary VOL) after the HAM pair is created. Execute the dlnkmgr view -lu -item hastat operation. If ha is not displayed in the HaStat column, then the corresponding LU is not recognized as being in a HAM configuration. If the host recognizes the paths to the MCU and RCU before the HAM pair is created, restart the host after the HAM pair is created. If you release a HAM pair to recover the system after a HAM volume failure, do not restart a host that is connected to the MCU and RCU while the HAM pair is 2014, 2015, Hitachi, Ltd. All rights reserv ed. 19

20 Documentation released. If you need to restart the host while the HAM pair is released, disconnect all paths to the MCU and RCU, restart the host, re-create the HAM pair, and then reconnect the paths. If you restart a host that is connected to the MCU and RCU while the HAM pair is released, the RCU volume will be recognized as a volume other than an MCU volume. If this occurs, restart the host after the HAM pair is re-created. Execute the dlnkmgr view -lu -item hastat operation, and then confirm that ha is displayed in the HaStat column. While the path health check provided by HDLM is enabled (on), if a HAM pair is released, the status of the paths (non-owner paths) connected to the RCU might become Offline(E) or Online(E). After creating (recovering) a HAM pair, return t he status of the paths to Online by using the HDLM command online operation. Documentation Available documents Manual Name Manual No. Issue Date Hitachi Command Suite Dynamic Link Manager (for Linux ) User Guide MK-92DLM February, , 2015, Hitachi, Ltd. All rights reserv ed. 20

21 Appendix A Host bus adapter (HBA) support matrix Use the Fibre Channel I/F adapters given below. When using two or more adapters, use the same type of adapter. If you combine different types of HBA, HDLM may not be able to switch a path when an error occurs. (1) QLogic (*1) AS4/ES EL ELsmp ELhugemem EL ELsmp ELhugemem EL ELsmp ELhugemem EL ELhugemem ELsmp (*5) EL ELsmp ELhugemem b21-k (*3)(*4) (*6) (*6) d4 (*3)(*4) (*6) d4 (*3)(*4) d7 (*3)(*4) (*2)(*6) d7 (*3)(*4) d8 AS4 AS4/ES4 (IPF) EL (*6) ELsmp ELhugemem EL (*6) ELsmp ELhugemem EL b21-k (*3) (*6) (*6) EL d4 (*3) (*6) , 2015, Hitachi, Ltd. All rights reserv ed. 21

22 EL d7 (*3) (*2)(*6) d EL d7 (*3) d8 AS4 (IPF) AS4/ES EL (*6) EL (*6) EL b21-k (*3)(*4) ELsmp (*6) (*6) AS4 AS4.5/ES4.5 AS4.5 AS4.5/ES4.5 (IPF) EL ELsmp ELlargesmp EL ELsmp ELlargesmp EL ELsmp ELlargesmp EL ELsmp ELlargesmp EL ELsmp ELlargesmp EL ELsmp ELlargesmp EL ELsmp ELhugemem EL ELsmp ELhugemem EL ELlargesmp d4 (*3)(*4) (*6) d4 (*3)(*4) d7 (*3)(*4) (*2)(*6) d d7 (*3)(*4) d (*6) (*6) d8 (*3)(*4) (*6) (*6) (*6) (*6) d8 (*3) (*6) (*6) (*6) 2014, 2015, Hitachi, Ltd. All rights reserv ed. 22

23 AS4.5/ES4.5 (IPF) AS4.5/ES4.5 AS4.5 AS4.6/ES4.6 AS4.6 AS4.6/ES4.6 (IPF) AS4.6 (IPF) AS4.6/ES4.6 AS4.6 AS4.7/ES4.7 AS4.7 AS4.7/ES4.7 (IPF) EL ELlargesmp EL ELsmp ELlargesmp EL ELsmp ELlargesmp EL ELsmp ELhugemem EL ELsmp ELhugemem EL ELlargesmp EL ELlargesmp EL ELsmp ELlargesmp EL ELsmp ELlargesmp EL ELsmp ELhugemem EL ELsmp ELhugemem EL ELlargesmp (*6) d8 (*3)(*4) (*6) (*6) (*6) (*6) d4 (*3)(*4) (*6) (*6) (*6) (*6) d4 (*3) (*6) (*6) (*6) (*6) d4 (*3)(*4) (*6) (*6) (*6) (*6) d0 (*3)(*4) (*6) (*6) (*6) d0 (*3) (*6) (*6) 2014, 2015, Hitachi, Ltd. All rights reserv ed. 23

24 AS4.7 (IPF) AS4.7/ES4.7 AS4.7 AS4.8/ES4.8 AS4.8/ES4.8 (IPF) AS4.8/ES4.8 AS4.9/ES4.9 AS4.9/ES4.9 (IPF) AS4.9/ES4.9 5 Advanced Enterprise Linux EL ELlargesmp EL ELsmp ELlargesmp EL ELsmp ELlargesmp EL ELsmp ELhugemem EL ELlargesmp EL ELsmp ELlargesmp EL ELsmp ELhugemem EL ELlargesmp EL ELsmp ELlargesmp el el5PAE (*6) d0 (*3)(*4) (*6) (*6) (*6) d (*3)(*4) (*6) d (*3)(*4)(*10) d (*3) (*6) d (*3)(*10) d (*3)(*4) (*6) d (*3)(*4)(*10) d (*3)(*4) d (*3) d (*3)(*4) k1 (*3)(*4) 5 Advanced Enterprise Linux 5 (IPF) 5 Advanced Enterprise Linux el k1 (*3) el k1 (*3)(*4) 5.1 Advanced Platform/Red Hat Enterprise Linux el el5PAE k7 (*3)(*4) (*6) 5.1 Advanced Platform/Red Hat Enterprise Linux 5.1 (IPF) el k7 (*3) (*6) 2014, 2015, Hitachi, Ltd. All rights reserv ed. 24

25 5.1 Advanced Platform/Red Hat Enterprise Linux el k7 (*3)(*4) (*6) 5.2 Advanced Platform/Red Hat Enterprise Linux el el5PAE k5 (*3)(*4) (*6) (*6) 5.2 Advanced Platform/Red Hat Enterprise Linux 5.2 (IPF) 5.2 Advanced Platform/Red Hat Enterprise Linux Advanced Platform/Red Hat Enterprise Linux Advanced Platform/Red Hat Enterprise Linux 5.3 (IPF) 5.3 Advanced Platform/Red Hat Enterprise Linux Advanced Platform/Red Hat Enterprise Linux Advanced Platform/Red Hat Enterprise Linux 5.4 (IPF) el k5 (*3) (*6) (*6) el k5 (*3)(*4) (*6) (*6) el k (*3)(*4) el5PAE (*6) (*4) el k (*3) (*6) el k (*3)(*4) (*6) (*4) el k (*3)(*4) el5PAE k (*3)(*4)(*9) (*4) (*4) el k (*3) k (*3)(*9) 5.4 Advanced Platform/Red Hat Enterprise Linux el k (*3)(*4) k (*3)(*4)(*9) (*4) (*4) 2014, 2015, Hitachi, Ltd. All rights reserv ed. 25

26 5.5 Advanced Platform/Red Hat Enterprise Linux Advanced Platform/Red Hat Enterprise Linux 5.5 (IPF) 5.5 Advanced Platform/Red Hat Enterprise Linux Advanced Platform/Red Hat Enterprise Linux Advanced Platform/Red Hat Enterprise Linux 5.6 (IPF) 5.6 Advanced Platform/Red Hat Enterprise Linux el k (*3)(*4) el5PAE (*4) (*4) k k-sw el k (*3) el k (*3)(*4) (*4) (*4) k k-sw el k (*3)(*4) el5PAE k el k (*3) el k (*3)(*4) k 5.7 Advanced Platform/Red Hat Enterprise Linux el el5PAE k (*3)(*4) 5.7 Advanced Platform/Red Hat Enterprise Linux 5.7 (IPF) 5.7 Advanced Platform/Red Hat Enterprise Linux el k (*3) el k (*3)(*4) p MCL 5.8 Advanced Platform/Red Hat Enterprise Linux el el5PAE k (*3)(*4) k 5.8 Advanced Platform/Red Hat Enterprise Linux 5.8 (IPF) 5.8 Advanced Platform/Red Hat Enterprise Linux el k (*3) el k (*3)(*4) k 2014, 2015, Hitachi, Ltd. All rights reserv ed. 26

27 5.9 Advanced Platform/Red Hat Enterprise Linux el el5PAE k (*3)(*4) k 5.9 Advanced Platform/Red Hat Enterprise Linux 5.9 (IPF) 5.9 Advanced Platform/Red Hat Enterprise Linux el k (*3) el k (*3)(*4) k 5.10 Advanced Platform/Red Hat Enterprise Linux el el5PAE k (*3)(*4) k 5.10 Advanced Platform/Red Hat Enterprise Linux 5.10 (IPF) 5.10 Advanced Platform/Red Hat Enterprise Linux el k (*3) el k (*3)(*4) k 5.11 Advanced Platform/Red Hat Enterprise Linux el el5PAE k (*3)(*4) 5.11 Advanced Platform/Red Hat Enterprise Linux 5.11 (IPF) 5.11 Advanced Platform/Red Hat Enterprise Linux el k (*3) el k (*3)(*4) el6.i k8 (*3)(*4) el6.x86_ k8 (*3)(*4) el6.i k (*3)(*4) el6.x86_ k k (*3)(*4) k 2014, 2015, Hitachi, Ltd. All rights reserv ed. 27

28 el6.i k (*3)(*4) k k k el6.x86_ k (*3)(*4) k k k el6.i k (*3)(*4) k k el6.x86_ k (*3)(*4) k k el6.i k (*3)(*4) k k el6.x86_ k (*3)(*4) k k el6.i k2 (*3)(*4) el6.x86_ k2 (*3)(*4) el6.i k1 (*3)(*4) el6.x86_ k1 (*3)(*4) el7.x86_ k (*3) Server default smp bigsmp default smp bigsmp default smp bigsmp k (*3) k3 (*3)(*4) (*6) k6 (*3)(*4) (*6) xenpae k6 (*3)(*4) 2014, 2015, Hitachi, Ltd. All rights reserv ed. 28

29 default k4 (*3)(*4) smp bigsmp xenpae k4 (*3)(*4) default k4 (*3)(*4) smp bigsmp xenpae k4 (*3)(*4) Server 10 (IPF) default k (*3) default k3 (*3) (*6) default k6 (*3) (*6) default k4 (*3) default k4 (*3) Server default smp default smp default smp k (*3) k3 (*3)(*4) (*6) k6 (*3)(*4) (*6) xen k6 (*3)(*4) default k4 (*3)(*4) smp xen k4 (*3)(*4) default k4 (*3)(*4) smp xen k4 (*3)(*4) Server default k9(*3)(*4) pae xen k9 (*3)(*4) default pae k8 (*3)(*4) k8 (*3)(*4)(*9) k 2014, 2015, Hitachi, Ltd. All rights reserv ed. 29

30 k0 (*4) xen k8 (*3)(*4) k8 (*3)(*4)(*9) k k0 (*4) Server 11 (IPF) default k (*3)(*4) pae default k (*3)(*4) pae default k9 (*3) default k8 (*3) k8 (*3)(*9) default k (*3) default k (*3) Server default k9 (*3)(*4) xen k9 (*3)(*4) default k8 (*3)(*4) k8 (*3)(*4)(*9) k k0 (*4) xen k8 (*3)(*4) k8 (*3)(*4)(*9) k k0 (*4) default k (*3)(*4) default k (*3)(*4) xen k (*3)(*4) Oracle Enterprise Linux 4 Oracle Enterprise Linux EL ELsmp ELhugemem EL ELsmp ELhugemem EL ELsmp ELlargesmp d8 (*3)(*4) d4 (*3)(*4) d8 (*3)(*4) , 2015, Hitachi, Ltd. All rights reserv ed. 30

31 EL ELsmp ELlargesmp d4 (*3)(*4) Oracle Enterprise Linux 5 Oracle Enterprise Linux 5 Oracle Enterprise Linux 5.4 Oracle Enterprise Linux 5.4 Oracle Enterprise Linux 5.5 Oracle Enterprise Linux 5.5 Oracle Enterprise Linux 5.6 Oracle Enterprise Linux 5.6 Oracle Enterprise Linux 5.7 Oracle Enterprise Linux 5.7 Oracle Linux 7 Oracle Unbreakable Enterprise Kernel 5.6 Oracle Unbreakable Enterprise Kernel 5.7 Oracle Unbreakable Enterprise Kernel 5.7 Oracle Unbreakable Enterprise Kernel el el5PAE k7 (*3)(*4) el k7 (*3)(*4) el el5PAE k (*3)(*4) el k (*3)(*4) el el5PAE k (*3)(*4) el k (*3)(*4) el el5PAE k (*3)(*4) el k (*3)(*4) el el5PAE k (*3)(*4) el k (*3)(*4) el7.x86_ k (*3) el k9 (*3)(*4) el5uek k (*3)(*4) el5uek k (*3)(*4) el5uek k (*3)(*4) el5uek k (*3)(*4) el5uek k (*3)(*4) 2014, 2015, Hitachi, Ltd. All rights reserv ed. 31

32 Oracle Unbreakable Enterprise Kernel 5.8 Oracle Unbreakable Enterprise Kernel 6.2 Oracle Unbreakable Enterprise Kernel 6.2 Oracle Unbreakable Enterprise Kernel 6.3 Oracle Unbreakable Enterprise Kernel 6.3 Oracle Unbreakable Enterprise Kernel 6.4 Oracle Unbreakable Enterprise Kernel 6.4 Oracle Unbreakable Enterprise Kernel 6.5 Oracle Unbreakable Enterprise Kernel 6.5 Oracle Unbreakable Enterprise Kernel el5uek k (*3)(*4) el6uek el6uek el6uek.x86_ el6uek.x86_ el6uek el6uek.x86_ el6uek el6uek.x86_ el6uek el6uek.x86_ k (*3)(*4) k (*3)(*4) k (*3)(*4) k (*3)(*4) k (*3)(*4) k (*3)(*4) k (*3)(*4) k (*3)(*4) k (*3)(*4) k (*3)(*4) el7uek.x86_ k1 (*3) Note: *1: Do not use the HBA driver's failover function. Check the setting for the failover function by performing the following procedure: - For AS4/ES4, AS4.5/ES4.5, AS4.6/ES4.6, AS4.7/ES4.7, AS4.8/ES4.8, AS4.9/ES4.9, and Oracle Enterprise Linux 4: 1) Execute the following command to check the version of the driver: # grep version /proc/scsi/driver-name/adapter-id driver-name: qlaxxxx (name of the driver currently being used) 2014, 2015, Hitachi, Ltd. All rights reserv ed. 32

33 adapter-id: Host port number 2) Check the output result to see whether the characters "fo" are added to the version notation. - When the failover function is enabled: Firmware version: , Driver version fo - When the failover function is disabled: Firmware version: , Driver version For 5 Advanced Platform, 5, Red Hat Enterprise Linux 5.1 Advanced Platform, 5.1, Red Hat Enterprise Linux 5.2 Advanced Platform, 5.2, Red Hat Enterprise Linux 5.3 Advanced Platform, 5.3, Red Hat Enterprise Linux 5.4 Advanced Platform, 5.4, Red Hat Enterprise Linux 5.5 Advanced Platform, 5.5, Red Hat Enterprise Linux 5.6 Advanced Platform, 5.6, Red Hat Enterprise Linux 5.7 Advanced Platform, 5.7, Red Hat Enterprise Linux 5.8 Advanced Platform, 5.8, Red Hat Enterprise Linux 5.9 Advanced Platform, 5.9, Red Hat Enterprise Linux 5.10 Advanced Platform, 5.10, Red Hat Enterprise Linux 5.11 Advanced Platform, 5.11, Red Hat Enterprise Linux 6, 6.1, 6.2, Red Hat Enterprise Linux 6.3, 6.4, 6.5, Red Hat Enterprise Linux 6.6, 7, Oracle Enterprise Linux 5, Oracle Enterprise Linux 5.4, Oracle Enterprise Linux 5.5, Oracle Enterprise Linux 5.6, Oracle Unbreakable Enterprise Kernel 5.6, Oracle Unbreakable Enterprise Kernel 5.7, Oracle Unbreakable Enterprise Kernel 5.8, Oracle Unbreakable Enterprise Kernel 6.2, Oracle Unbreakable Enterprise Kernel 6.3, Oracle Unbreakable Enterprise Kernel 6.4, Oracle Unbreakable Enterprise Kernel 6.5, Oracle Unbreakable Enterprise Kernel 7, SUSE LINUX Enterprise Server 10, and Server 11 1) Execute the following command to check the version of the driver: # cat /sys/class/scsi_host/hostn/driver_version n: the instance number of the HBA port 2) Check the output result to see whether the characters "fo" are added to the version notation. - When the failover function is enabled: k1-fo - When the failover function is disabled: k1 *2: The drivers mentioned in the page of "Hitachi Data Systems - HBA Approved Software" in the QLogic website are supported. Get the drivers from the following URL: 2014, 2015, Hitachi, Ltd. All rights reserv ed. 33

34 =237 The above-mentioned URL may be changed without notice. When the URL is changed, look for the page of "Hitachi Data Systems - HBA Approved Software" in the QLogic website. *3: Use the driver bundled with the kernel. *4: Using an HDLM device as the boot disk is supported. *5: HDLM also supports the environments in which 32-bit kernel packages are installed on a system using an AMD Opteron processor. *6: Since the failover function is Enable by default, change it to Disable. For changing the setting of the failover function to Disable, set the following in /etc/modprobe.conf file. Example: When the driver version is options qla2xxx ql2xfailover=0 Refer to the document of the HBA attachment for details of the setting change of the failover function. *7: EM64T indicates the environments in which 64-bit kernel packages are installed on a system using an Intel EM64T processor. *8: AMD64 indicates the environments in which 64-bit kernel packages are installed on a system using an AMD Opteron processor. *9: Supported by Kernel or later. *10: Supported by Kernel or later. (2) Emulex AS4/ES EL ELsmp ELhugemem EL ELsmp ELhugemem AS4/ES4 (IPF) EL (*2) ELhugemem ELsmp (*4) EL (*2) ELsmp ELhugemem EL EL (*2) 2014, 2015, Hitachi, Ltd. All rights reserv ed. 34

35 EL (*2) AS4/ES EL ELsmp ELlargesmp AS4.5/ES4.5 AS4.5 AS4.5/ES4.5 (IPF) EL ELsmp ELlargesmp EL ELsmp ELlargesmp EL ELsmp ELlargesmp EL ELsmp ELhugemem EL ELsmp ELhugemem EL ELlargesmp (*2) (*2) (*2)(*3) (*6) (*2)(*3) (*6) AS4.5 (IPF) AS4.5/ES EL ELlargesmp EL ELsmp ELlargesmp (*2)(*3) (*6) AS4.5 AS4.6/ES4.6 AS EL ELsmp ELlargesmp EL ELsmp ELhugemem EL ELsmp ELhugemem (*2)(*3) , 2015, Hitachi, Ltd. All rights reserv ed. 35

36 AS4.6/ES4.6 (IPF) AS4.6 (IPF) AS4.6/ES4.6 AS4.6 AS4.7/ES4.7 AS4.7/ES4.7 (IPF) AS4.7/ES4.7 AS4.8/ES EL ELlargesmp EL ELlargesmp EL ELsmp ELlargesmp EL ELsmp ELlargesmp EL ELsmp ELhugemem EL ELlargesmp EL ELsmp ELlargesmp EL ELsmp ELhugemem (*2)(*3) (*2)(*3) (*2)(*3) (*2)(*3) (*2)(*3) (*2)(*3) (*2)(*3)(*9) AS4.8/ES4.8 (IPF) AS4.8/ES EL ELlargesmp EL ELsmp ELlargesmp (*2)(*3) (*2)(*3)(*9) (*2)(*3) (*2)(*3)(*9) AS4.9/ES4.9 AS4.9/ES4.9 (IPF) AS4.9/ES4.9 5 Advanced EL ELsmp ELhugemem EL ELlargesmp EL ELsmp ELlargesmp el el5PAE (*2)(*3) (*2)(*3) (*2)(*3) (*2)(*3) , 2015, Hitachi, Ltd. All rights reserv ed. 36