Transcription
Hitachi Dynamic Link Manager (for VMware )v8.4.0-00 Release NotesContentsAbout this document. 1Intended audience. 1Getting help . 1About this release . 2Product package contents. 2New features and important enhancements . 2System requirements. 2Resolved problems . 4Known problems . 6Installation precautions . 6Usage precautions . 8Documentation . 10Copyrights and licenses . 11About this documentThis document (RN-91HC190-16, February 2016) provides late-breakinginformation about Hitachi Dynamic Link Manager (for VMware) 8.4.0-00. Itincludes information that was not available at the time the technicaldocumentation for this product was published, as well as a list of known problemsand solutions.Intended audienceThis document is intended for customers and Hitachi Data Systems partners wholicense and use Hitachi Dynamic Link Manager (for VMware).Getting helpHitachi Data Systems Support Connect is the destination for technical support ofproducts and solutions sold by Hitachi Data Systems. To contact technicalsupport, log on to Hitachi Data Systems Support Connect for contact information:https://support.hds.com/en us/contact-us.html. 2014, 2016, Hitachi, Ltd. All rights reserved.RN-91HC190-16, February 20161
About this releaseHitachi Data Systems Community is a global online community for HDScustomers, partners, independent software vendors, employees, and prospects.It is the destination to get answers, discover insights, and make connections.Join the conversation today! Go to community.hds.com, register, andcomplete your profile.About this releaseThis release is a major release that adds new features.Product package achi Dynamic Link Manager (forVMware)8.4.0-00FullPackageDocumentsHitachi Command Suite Dynamic LinkManager (for VMware ) User GuideMK-92DLM130-15Prerequisiteversion ofService Pack-New features and important enhancements[8.4.0-00 Additional Functions and Modifications](1) The dlnkmgr command was enhanced to display "VSP Fx00" as the model IDof the storage system when Virtual Storage Platform (VSP) F400, F600, orF800 is used.System requirementsRefer to Chapter 3. Creating an HDLM Environment in the Hitachi Command SuiteDynamic Link Manager (for VMware ) User Guide.HostFor details on supported Hosts refer to the Hitachi Command Suite Dynamic LinkManager (for VMware ) User Guide, Chapter 3, Creating an HDLM Environment HDLM System Requirements - Hosts and OSs Supported by HDLM.Supported OSs in a HAM environment are listed below:Supported OSVMware vSphere ESXi 5.0VMware vSphere ESXi 5.1VMware vSphere ESXi 5.5 2014, 2016, Hitachi, Ltd. All rights reserved.RN-91HC190-16, February 20162
System requirementsHost Bus Adapter (HBA)Applicable HBAs and HBA drivers:- Inbox driver for ESXi 5.0/5.1/5.5/6.0 or HBA drivers that support ESXi5.0/5.1/5.5/6.0 as listed in VMware Compatibility Guide.- HBAs and HBA drivers for BladeSymphony that support ESXi 5.0/5.1/5.5/6.0 aslisted in VMware Compatibility Guide.StorageFor details on supported storage refer to the Hitachi Command Suite DynamicLink Manager (for VMware ) User Guide, Chapter 3, Creating an HDLMEnvironment - HDLM System Requirements - Storage Systems Supported byHDLM.When the Dynamic I/O Path Control function is enabled on Hitachi AMS 2000series, use a microprogram version 08B8/D or later.Requirements to use a HAM environment are as follows: HDLM supports the HAM functionality of the following storage systems:- Hitachi Virtual Storage Platform- HP P9500- Hitachi Unified Storage VMThe required microprogram versions are listed below:Storage systemInterfaceMicroprogramversionRemarkVirtual Storage PlatformFC I/F70-03-XX-XX/XX orlater(*1)X: voluntarynumberP9500FC I/F70-03-XX-XX/XX orlater(*1)X: voluntarynumberHitachi Unified Storage VMFC I/F73-03-0X-XX/XX orlaterX: voluntarynumber*1: If you use the vStorage APIs for Array Integration with HAM, apply70-05-00-XX/XX or later.Operating Systems RequirementsThe following operating systems are supported.- VMware vSphere ESXi 5.0 Standard Edition/ Enterprise Edition/ Enterprise Plus Edition- VMware vSphere ESXi 5.0 update 1 Standard Edition/ Enterprise Edition/ Enterprise Plus Edition- VMware vSphere ESXi 5.0 update 2 Standard Edition/ Enterprise Edition/ Enterprise Plus Edition- VMware vSphere ESXi 5.0 update 3 Standard Edition/ Enterprise Edition/ Enterprise Plus Edition- VMware vSphere ESXi 5.1 Standard Edition/ Enterprise Edition/ Enterprise Plus Edition- VMware vSphere ESXi 5.1 update 1 Standard Edition/ Enterprise Edition/ Enterprise Plus Edition- VMware vSphere ESXi 5.1 update 2 Standard Edition/ Enterprise Edition/ Enterprise Plus Edition 2014, 2016, Hitachi, Ltd. All rights reserved.RN-91HC190-16, February 20163
Resolved problems- VMware vSphere ESXi 5.1 update 3 Standard Edition/ Enterprise Edition/ Enterprise Plus Edition- VMware vSphere ESXi 5.5 Standard Edition/ Enterprise Edition/ Enterprise Plus Edition- VMware vSphere ESXi 5.5 update 1 Standard Edition/ Enterprise Edition/ Enterprise Plus Edition- VMware vSphere ESXi 5.5 update 2 Standard Edition/ Enterprise Edition/ Enterprise Plus Edition- VMware vSphere ESXi 5.5 update 3 Standard Edition/ Enterprise Edition/ Enterprise Plus Edition- VMware vSphere ESXi 6.0 Standard Edition/ Enterprise Edition/ Enterprise Plus Edition- VMware vSphere ESXi 6.0 update 1 Standard Edition/ Enterprise Edition/ Enterprise Plus EditionPrerequisite Programs- HostNone- Remote management hostVMware vSphere CLI 5.0/5.1/5.5/6.0 must be installed and set up to beconnected to the host.Resolved problems(1) In the HGLM path status log, a 6-digit number, instead of a 5-digitnumber, is displayed for the serial number of VSP G1000.[Conditions]This problem occurs when all of the following conditions are met:1. VSP G1000 or XP7 is being used.2. HDLM 8.0.0-00 to 8.2.1-00 is being used.3. HDLM is managed by using HGLM.4. In HGLM, the acquisition of path availability information (path status log)is enabled.5. From HGLM, the path status log is output.[Case ID]None.(2) When HDLM 8.1.2-00 to 8.2.1-00 is used on a remote management client,the severity level of the following audit log messages is 3 (Error), instead of4 (Warning):KAPL15102, KAPL15106, KAPL15108, and KAPL15110[Conditions]This problem occurs when all of the following conditions are met:1. HDLM 8.1.2-00 to 8.2.1-00 is being used on a remote managementclient.2. The output of audit log data is enabled. 2014, 2016, Hitachi, Ltd. All rights reserved.RN-91HC190-16, February 20164
Resolved problems3. An operation to view or update configuration information fails.[Case ID]None.(3) When HDLM 8.1.2-00 to 8.2.1-00 is used on a remote management client,reports on path availability generated by HGLM are incorrect.[Conditions]This problem occurs when all of the following conditions are met:1. HDLM 8.1.2-00 to 8.2.1-00 is being used on a remote managementclient.2. HDLM is managed by using HGLM.3. In HGLM, the acquisition of path availability information (path status log)is enabled.4. From HGLM, a path availability report or the path status log is output.[Case ID]None.(4) During installation of HDLM, installation of the Hitachi Command SuiteCommon Agent Component sometimes fails.[Conditions]This problem may occur when both of the following conditions are met.1. Any of the following products was installed:- HDLM 7.3.0-00 to 8.2.1-00- Device Manager agent of HDvM 5.0.0-00 to earlier than 8.4.0-00- Replication Manager Application Agent of HRpM 6.3.0-00 to earlier than8.4.0-002. The following message is output to the installation log of HitachiCommand Suite Common Agent Component on which the product of 1.was installed. SystemDrive :\HBaseAgent install.logINFO MM-DD-YYYY HH:MM:SS KAIE60004-I INVOKE XCopyFile( Hitachi Command Suite Common Agent Componentinstallation folder \HBaseAgent\agent\JRE1.5\*, Hitachi CommandSuite Common Agent Component installationfolder \HBaseAgent\agent\JRE1.4) RC -2147024891INFO MM-DD-YYYY HH:MM:SS KAIE60004-I INVOKE FormatMessage(Access denied.3. HDLM 7.3.0-00 to 8.2.1-00 is installed on a remote management client.[Case ID]None. 2014, 2016, Hitachi, Ltd. All rights reserved.RN-91HC190-16, February 20165
Known problemsKnown problems(1) If you change the default PSP setting and reboot a target ESXi, the defaultPSP, which is of SATP provided by HDLM for Hitachi storage system, might beautomatically changed to "HTI PSP HDLM EXLIO". Therefore, if you add LUs,check the load balance setting (PSP) for LUs recognized by ESXi.(2) When you remove HDLM by using removehdlm (utility for Removing HDLM) in"HDLM-installation-folder\bin", perform the following operations.- "HDLM-installation-folder\bin" is not deleted. Delete "HDLM-installationfolder".- The dialog box "removehdlm is in use" is displayed during a remove. Select"Continue" to continue the remove.The above phenomena can be avoided by performing either of the followingprocedures.- Obtain the HDLM installation DVD, and then remove HDLM by usingremovehdlm utility stored in "drive-containing-installation-DVDROM:\HDLM VMware\DLMTools".- Copy removehdlm utility in "HDLM-installation-folder\bin" to any location,and then remove HDLM by using the copied removehdlm utility.(3) When you change the setting of user account or Credential Store file bydlmrmcenv (utility for Configuring HDLM Remote Management ClientEnvironments), restart the following two services by using the Windowsservice console to enable the change.- DLMManagerVM- HBsA Service(4) A dialog box is displayed to prompt a system reboot even when a newinstallation or upgrade installation is aborted. Select "No" since the rebootassociated with the installation abort is not required.(5) In an ESXi 5.5/6.0 environment where MSCS is used, the load-balancingfunction cannot be enabled. If you install MSCS in an ESXi5.5/6.0environment, use VMW PSP MRU.Installation precautionsFor details on HDLM installation refer to the Hitachi Command Suite Dynamic LinkManager (for VMware ) User Guide, Chapter 3, Creating an HDLM Environment Installing HDLM.(1) ESXi and VIB package that is a module package of VMware respectively havefour acceptance levels: VmwareCertified, VmwareAccepted, PartnerSupportedand CommunitySupported, from higher levels. If the acceptance level of anESXi is higher than that of a VIB package, the VIB package cannot beinstalled on the ESXi. In this case, an operation of lowering the acceptancelevel of the ESXi to an appropriate level is required. For the operation 2014, 2016, Hitachi, Ltd. All rights reserved.RN-91HC190-16, February 20166
Installation precautionsprocedures, refer to the Hitachi Command Suite Dynamic Link Manager (forVMware ) User Guide, Chapter 3, Creating an HDLM Environment - InstallingHDLM.(2) Names of offline bundle files and plugin modules provided in this version arelisted below.- Offline bundle name and information of pluginsOffline bundle p(*2)Plugin namesatp-hdlmVersionAcceptance dsatp-hdlm*1: File name of the package for ESXi version 5.x*2: File name of the package for ESXi version 6.0(3) Before installing HDLM, make sure that VMware vSphere CLI (vCLI) isinstalled and the ESXi server can be accessed by vCLI.(4) If HDLM is managed with HGLM, confirm the following before the operation of"Hitachi Command Suite Dynamic Link Manager User Guide for VMware Settings When Managing HDLM by Using Global Link Manager".- On Remote Management Client, a host name of an ESXi host can beresolved into an IP address.- A Credential Store file is created by using the resolved IP address.(5) The command prompt which is displayed during an installation, upgrade, oruninstallation of remote management client is automatically closed after the 2014, 2016, Hitachi, Ltd. All rights reserved.RN-91HC190-16, February 20167
Usage precautionsoperation is completed. Make sure not to close it during the operation. IfCommand Prompt is closed during the operation, the operation of aninstallation, upgrade, or uninstallation ends before completion. In this case,perform an upgrade installation.(6) An ESXi host can recognize up to 256 LUs including all SCSI devices such asbuilt-in disk and CD-ROM drive. Although the maximum LU number for HDLMmanagement-target in a storage system is 256, the LU number that can beactually managed will be smaller depending on the status of other connecteddevices. Before applying HDLM to an ESXi host, confirm that the HDLMmanagement-target LUs are correctly recognized by the ESXi host.(7) To use VMware vSphere CLI 6.0 on the remote management client, performeither of the following:1. Add the path of the command esxcli to the environment variable Path.To link Hitachi Dynamic Link Manager to Global Link Manager, add thepath to the system environment variable Path. When adding the path tothe system environment variable Path, do not enclose the path in doublequotation marks ("). Add the following value to the environment variablePath: installation-folder-of-VMware-vSphere-CLI \bin (*)2. In the command prompt of VMware vSphere CLI, set up the environmentvariables perlpath and vclipath, and then execute the utility dlmrmcenv.Specify the following values for perlpath and vclipath:perlpath installation-folder-of-VMware-vSphere-CLI \bin (*)vclipath installation-folder-of-VMware-vSphere-CLI \perl\bin (*)Note that, if you restart the command prompt after executing the utilitydlmrmcenv, you do not need to set up the environment variables perlpathand vclipath.*: installation-folder-of-VMware-vSphere-CLI is the current directorywhen the command prompt of VMware vSphere CLI starts.(8) If the HDLM version installed on a host is older than the version on a remotemanagement client, the following configuration is supported:- If the configuration is an ESXi 5.5 host and a remote management clientusing the vSphere Command-Line Interface 6.0, the functionality of theHDLM version installed on the ESXi 5.5 host is supported.Remove PrecautionsFor details on HDLM installation refer to the Hitachi Command Suite DynamicLink Manager (for VMware ) User Guide, Chapter 3, Creating an HDLMEnvironment - Removing HDLM.Usage precautionsNotes on General procedures(1) HDLM provides NMP sub-plugins(SATP/PSP) to enable multipath managementfor Hitachi storages. For the information of NMP/SATP/PSP, refer to thefollowing documentation(*). 2014, 2016, Hitachi, Ltd. All rights reserved.RN-91HC190-16, February 20168
Usage 50-storageguide.pdf(*): It is the information as of May, 2012.(2) Any restrictions and precautions for NMP which VMware announces areapplied to your environment using HDLM. Check the restrictions andprecautions before you build an environment.(3) Any restrictions and precautions for PSP VMW PSP RR (Round Robin) that isprovided by VMware are applied to the following HDLM load balances.- HTI PSP HDLM EXLIO- HTI PSP HDLM EXLBK- HTI PSP HDLM EXRR(a): In ESXi 5.0/5.1, Round Robin is not supported in MSCS environment.http://kb.vmware.com/kb/1036189This restriction is also applied to HDLM PSP, so HDLM PSP cannot be used.Therefore, if your environment meet the condition, use VMW PSP MRU.Notes on HAM procedures(1) In the case of displaying the LU information, the HAM information is notoutput by specifying the "all" parameter-value for the HDLM command.Specify the "ha" and "hastat" parameter-value instead.(2) An online operation is performed on an owner path, a non-owner path'sstatus may change to Offline(E). After performing an online operation on anowner path, use the HDLM command to make sure that the non-owner path'sstatus is Online. If the non-owner path's status is Offline(E), change thestatus of HAM pairs to PAIR, and then perform an online operation on theOffline(E) path again.(3) When you set up a HAM pair to be managed by HDLM, make sure that thehost 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 inthe HaStat column, then the corresponding LU is not recognized as being in aHAM configuration.If the host recognizes the paths to the MCU and RCU or either one of thepaths, before the HAM pair is created, restart the host after the HAM pair iscreated.(4) 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 HAMpair is released. 2014, 2016, Hitachi, Ltd. All rights reserved.RN-91HC190-16, February 20169
DocumentationIf you need to restart the host while the HAM pair is released, disconnect allpaths to the MCU and RCU, restart the host, re-create the HAM pair, and thenreconnect the paths.If you restart a host that is connected to the MCU and RCU while the HAMpair is released, the RCU volume will be recognized as a volume other than anMCU 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 thatha is displayed in the HaStat column.DocumentationAvailable documentsDocument nameHitachi Command Suite Dynamic Link Manager (forVMware ) User Guide 2014, 2016, Hitachi, Ltd. All rights reserved.RN-91HC190-16, February 2016Document numberMK-92DLM130-15Issue dateFebruary201610
Copyrights and licensesCopyrights and licenses 2016, Hitachi, Ltd. All rights reserved.No part of this publication may be reproduced or transmitted in any form or by any means, electronicor mechanical, including copying and recording, or stored in a database or retrieval system forcommercial purposes without the express written permission of Hitachi, Ltd., or Hitachi Data SystemsCorporation (collectively “Hitachi”). Licensee may make copies of the Materials provided that any suchcopy is: (i) created as an essential step in utilization of the Software as licensed and is used in noother manner; or (ii) used for archival purposes. Licensee may not make any other copies of theMaterials. “Materials” mean text, data, photographs, graphics, audio, video and documents.Hitachi reserves the right to make changes to this Material at any time without notice and assumes noresponsibility for its use. The Materials contain the most current information available at the time ofpublication.Some of the features described in the Materials might not be currently available. Refer to the mostrecent product announcement for information about feature and product availability, or contactHitachi Data Systems Corporation at https://portal.hds.com.Notice: Hitachi products and services can be ordered only under the terms and conditions of theapplicable Hitachi agreements. The use of Hitachi products is governed by the terms of youragreements with Hitachi Data Systems Corporation.By using this software, you agree that you are responsible for:1) Acquiring the relevant consents as may be required under local privacy laws or otherwise fromauthorized employees and other individuals to access relevant data; and2) Verifying that data continues to be held, retrieved, deleted, or otherwise processed in accordancewith relevant laws.Notice on Export Controls. The technical data and technology inherent in this Document may besubject to U.S. export control laws, including the U.S. Export Administration Act and its associatedregulations, and may be subject to export or import regulations in other countries. Reader agrees tocomply strictly with all such regulations and acknowledges that Reader has the responsibility to obtainlicenses to export, re-export, or import the Document and any Compliant Products.Hitachi is a registered trademark of Hitachi, Ltd., in the United States and other countries.AIX, AS/400e, DB2, Domino, DS6000, DS8000, Enterprise Storage Server, eServer, FICON,FlashCopy, IBM, Lotus, MVS, OS/390, PowerPC, RS/6000, S/390, System z9, System z10, Tivoli,z/OS, z9, z10, z13, z/VM, and z/VSE are registered trademarks or trademarks of InternationalBusiness Machines Corporation.Active Directory, ActiveX, Bing, Excel, Hyper-V, Internet Explorer, the Internet Explorer logo,Microsoft, the Microsoft Corporate Logo, MS-DOS, Outlook, PowerPoint, SharePoint, Silverlight,SmartScreen, SQL Server, Visual Basic, Visual C , Visual Studio, Windows, the Windows logo,Windows Azure, Windows PowerShell, Windows Server, the Windows start button, and Windows Vistaare registered trademarks or trademarks of Microsoft Corporation. Microsoft product screen shots arereprinted with permission from Microsoft Corporation.All other trademarks, service marks, and company names in this document or website are propertiesof their respective owners. 2014, 2016, Hitachi, Ltd. All rights reserved.RN-91HC190-16, February 201611
- VMware vSphere ESXi 6.0 Standard Edition/ Enterprise Edition/ Enterprise Plus Edition - VMware vSphere ESXi 6.0 update 1 Standard Edition/ Enterprise Edition/ Enterprise Plus Edition Prerequisite Programs - Host None - Remote management host VMware vSphere CLI 5.0/5.1/5.5/6.0
