Hitachi Infrastructure Analytics Advisor v Release Notes

Transcription

1 Hitachi Infrastructure Analytics Advisor v Release Notes Contents About this document... 1 Intended audience... 1 Getting help... 1 About this release... 2 Product package contents... 2 New features... 2 System requirements... 3 Known problems... 9 Installation notes Usage notes Accessing documentation Copyrights and licenses About this document This document (RN-96HIA000-01, July 2016) provides late-breaking information about Hitachi Infrastructure Analytics Advisor It includes information that was not available at the time that 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 Hitachi Infrastructure Analytics Advisor and Data Center Analytics. Getting help Hitachi Data Systems Support Connect is the destination for technical support of products and solutions sold by Hitachi Data Systems. To contact technical support, log on to Hitachi Data Systems Support Connect for contact information: Hitachi, Ltd. All rights reserved. 1

2 Hitachi Data Systems Community is a global online community for HDS customers, 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, and complete your profile. About this release These release notes cover Hitachi Infrastructure Analytics Advisor (HIAA) v and Data Center Analytics (DCA). Product package contents Medium DVD-ROM Revision Release type Software Hitachi Infrastructure Analytics Advisor Full Package For details on the paths of the installation scripts, see the following table. Media Program to be installed Directory Installation program included HIAA installation media IAA /IAA/ ANALYTICS.msi DCA server /DCA/ dcaserver_install.sh dcaserver_uninstall.sh /DCA/RPM/ hdca-server.rpm DCA probe /DCAPROBE/ dcaprobe_install.sh dcaprobe_uninstall.sh DCA Windows-based probe /DCAPROBE/ DCA_PROBE/RPM/ /DCAWINPROBE/ hdca-probe.rpm HDCA_Windows_Probe.exe New features Some of the key Infrastructure Analytics Advisor capabilities include: Unified infrastructure monitoring dashboard Hitachi Infrastructure Analytics Advisor dashboards are visual representations of the performance metrics of your infrastructure resources. The consolidated view allows you to quickly interpret the performance metrics and identify performance problems Hitachi, Ltd. All rights reserved. 2

3 Advanced reporting Infrastructure Analytics Advisor reporting capabilities enable you to monitor the infrastructure resources and assess their current performance, capacity and utilization. Reporting data provides you the information with which you must make informed business decisions and plan for future growth. SLO management SLOs are measurable parameters that are defined for monitoring the performance of user resources. With Infrastructure Analytics Advisor you can evaluate, define, and customize the service level objectives defined for monitored resources such as volumes and VMs. By monitoring the SLOs you can determine whether your objectives comply with your business requirements. End-to-end infrastructure topology view The E2E topology view provides detailed configuration of the infrastructure resources and lets you view the relationship between the infrastructure components. You can manually analyze the dependencies between the components in your environment and identify the resource causing performance problems. By using the topology maps, you can easily monitor and manage your resources. You can use this view to monitor resources in your data center from applications, virtual machines, servers, networks and storage. Problem identification and root cause analysis The performance problems might occur because of varying system loads, application updates, capacity upgrades, configuration changes and inefficient management of resources in shared infrastructure. Infrastructure Analytics Advisor advanced diagnostic engine aids in rapidly diagnosing, troubleshooting and finding the root cause of performance bottlenecks. System requirements Infrastructure Analytics Advisor management server requirements Operating system requirements (Windows) OS name OS version SP Architecture Windows Server 2008 R2 (*1) Standard Enterprise Datacenter SP1 x64 Windows Server 2012 (*2) Standard Datacenter No SP x64 Windows Server 2012 R2 (*2) Standard Datacenter No SP x Hitachi, Ltd. All rights reserved. 3

4 Hardware requirements Prerequisite Minimum Recommended (Best practice) Processor Dual-Core processor Quad-Core processor Memory 8 GB 16 GB minimum Disk space 50 GB 100 GB minimum (*1) Server core is not supported. (*2) Server core and Minimal Server Interface are not supported. Data Center Analytics management server requirements For installation using RPM installer Operating system requirements OS name Yum/rpm dependencies Architecture Red Hat Enterprise Linux perl - java openjdk - expect - openssl-devel - parted - xfsprogs x Hitachi, Ltd. All rights reserved. 4

5 Hardware requirements Prerequisite Minimum Recommended (Best practice (*1)) Processor Dual-Core processor Quad-core processor Memory 8 GB 16 GB minimum Disk space(*2) 150 GB 600 GB minimum (*1) The memory requirement and the disk capacity vary depending on the amount or configuration of the managed resources. For example, if there are many volumes in the managed storage systems, the volumes occupy much disk space in the database. If you decrease the interval at which you obtain performance information from the managed resources, the volumes occupy more disk space in the database. (*2) Prepare a disk other than the disk of the operating system installed for installing the Data Center Analytics management server. You must specify the disk to install the product in the installer (dcaserver_install.sh). Please note that you need to prepare a physical disk for installing the Data Center Analytics management server on physical machines. For installation using OVA format on VMware vsphere Client When the virtual appliance is deployed, a virtual machine with the following default settings is created. Verify that the virtualization server has enough resources to create the virtual machine. Hardware requirements Item Settings Processor Quad-Core processor (the number of virtual sockets: 4, the number of cores per virtual socket: 1) Memory 8 GB Disk space 150 GB (Configure as two separate disks.) Note: The default installation directory of Data Center Analytics is /data. Analytics probe server requirements For installation using RPM installer Operating system requirements 2016 Hitachi, Ltd. All rights reserved. 5

6 OS name Yum/rpm dependencies CPAN dependencies Architecture Red Hat Enterprise Linux perl - perl-cpan - gcc - java openjdk - samba - expect - openssl-devel - ftp - unzip - wget - glibc.i686 - libstdc++.i686 - net-tools - tcsh - libyaml - Module::Build - YAML - IO::Pty - Date::Gregorian - Date::Calc - Log::Log4perl - Net::OpenSSH - DateTime - Log::Dispatch::FileRotate - DateTime::Format::Strptime - Sys::RunAlone LWP::UserAgent - LWP::Protocol::https - Time::HiRes x64 Hardware requirements Prerequisite Minimum Recommended (Best practice (*)) Processor Dual-Core processor Quad-core processor Memory 8 GB 16 GB minimum Disk space 100GB 150GB minimum (*) The memory requirement and the disk capacity vary depending on the amount or configuration of the managed resources. For example, if there are many volumes in the managed storage, the volumes occupy much disk space in the database. If you decrease the interval at which to obtain performance information from the managed resources, the volumes occupy more disk space in the database. For installation using OVA format on VMware vsphere Client When the virtual appliance is deployed, a virtual machine with the following default settings is created. Verify that the virtualization server has enough resources to create the virtual machine Hitachi, Ltd. All rights reserved. 6

7 Hardware requirements Item Settings Processor Memory Disk space Quad-Core processor (the number of virtual sockets: 4, the number of cores per virtual socket: 1) 8 GB 100 GB Note: The default installation directory of Analytics probe is /home. Browser requirements Web browser/other Version Firefox ESR 38 ESR 45 Internet Explorer 11 Chrome for Work Latest version of stable channel Flash Player 21.0 or later (to use custom reports in Data Center Analytics GUI) Management target requirements Supported management resources The following tables show the monitoring targets of Infrastructure Analytics Advisor. Storage Storage system Microcode version/hnas model Analytics probe name Hitachi Virtual Storage Platform or later Hitachi Enterprise Storage probe (*1) Hitachi Unified Storage VM or later Hitachi Virtual Storage Platform G or later Hitachi Virtual Storage Platform G400 Hitachi Virtual Storage Platform G Hitachi, Ltd. All rights reserved. 7

8 Storage system Hitachi Virtual Storage Platform G800 Microcode version/hnas model Analytics probe name Hitachi Virtual Storage Platform F or later Hitachi Virtual Storage Platform F600 Hitachi Virtual Storage Platform F800 Hitachi Virtual Storage Platform G or later Hitachi Unified Storage or later Hitachi Adaptor Modular Storage probe Hitachi Unified Storage 130 Hitachi Unified Storage 150 HNAS 3090 HNAS probe (*2) Hypervisors Product name Version Analytics Probe name VMWare vcenter Server 5.0 or later VMWare probe VMware ESXi 5.0 or later Hyper-V Windows Server 2008 R2 Hyper-V Hyper-V 2.0 Windows-based probe Windows Server 2012 Hyper-V Hyper-V 3.0 Windows Server 2012 R2 Hyper-V Hyper-V 3.1 Host OS name Edition Analytics Probe name Windows Windows Server 2008 Standard / Enterprise / Datacenter Windows-based probe Windows Server 2008 R2 Standard / Enterprise / 2016 Hitachi, Ltd. All rights reserved. 8

9 Datacenter Windows Server 2012 Standard / Datacenter Windows Server 2012 R2 Standard / Datacenter FC switches Switch name Version Analytics probe name Brocade Brocade Network Advisor Professional Plus Brocade Network Advisor Enterprise 12.0 Brocade Network Advisor probe 12.0 Cisco Cisco Data Center Network Manager - Cisco DCNM probe (*1) When using Hitachi Enterprise Storage probe, make sure that the RAID Manager LIB is installed on the same host as the Hitachi Enterprise Storage probe. (*2) The data collected by the NAS probe can be viewed in DCA but cannot be analyzed by HIAA. Related programs To manage additional information about Hitachi storage systems (such as information about storage capacity and hosts), use the following program: License keys Hitachi Device Manager version or later The Hitachi Infrastructure Analytics Advisor product requires a license key. In addition, the Data Center Analytics server and the Analytics probe also require a license key. Obtain license keys for Hitachi Infrastructure Analytics Advisor, Data Center Analytics Server, and Analytics probe from your HDS representative. Known problems Known problems for Infrastructure Analytics Advisor management server The following table lists the known problems in the current release of Infrastructure Analytics Advisor management server by defect ID Hitachi, Ltd. All rights reserved. 9

10 Defect ID Problem Workaround/Comments IAA IAA In following windows, the number of components listed in the Available Components table and Selected Components table is limited to 30: Analytics tab > Sparkline View > Show Performance > Select Component Administration tab > Monitoring Settings > User Resource Threshold Profiles > Threshold Profile > Target Resources > Resources > Threshold Detail > Select Component IP address information does not display for the following storage systems: Hitachi Virtual Storage Platform VSP G1000 VSP Gx00 models VSP Fx00 models Hitachi Unified Storage VM IAA Parity groups of external storage do not display. IAA IAA IAA IAA Data on the following metrics is not collected from virtual machines (Hyper-V): CPU Ready NIC Dropped Disk Latency As a result, data about virtual machines (Hyper-V) is not included in the aggregation results in the following Dashboard reports: System Status Summary VM Summary VM CPU Ready VM NIC Dropped VM Disk Latency When a virtual machine on Hyper-V is monitored with the Windows-based probe, the relation of the FC switch and host is not displayed. Even when Hyper-V services are running on a particular server, if no virtual machines exist, the server is recognized as a Windows host. When a Windows server monitored by a probe switches from being recognized as a Windows server to being recognized as a Hyper-V, or when a Hyper-V monitored by a probe switches from being recognized as a Hyper-V to being recognized as a Windows server, a CPU addition/deletion event occurs. No workaround 2016 Hitachi, Ltd. All rights reserved. 10

11 IAA IAA IAA IAA IAA IAA If you have a VM as a base point to display the E2E view, in the disk list, a disk other than the disk that is displayed in the E2E view is displayed. In the E2E view, if you display the Sparkline view when Windows or Hyper-V was set as a base point, the storage name on volume for the following supported storage systems is not correctly displayed: HUS 100 models HUS VM VSP Gx00 models VSP Fx00 models Performance events for the following metrics are not detected: Total IOPS (Pool) Utilization (Pool) Read Hit (Parity Group) Utilization (Parity Group) The following performance metrics are not supported: RX Rate (Fabric Brocade Switch Port) TX Rate (Fabric Brocade Switch Port) Random Read Hit (LDEV) Seq Read Hit (LDEV) Backend Transfers (LDEV) Cache to Drive Transfers (LDEV) Random Drive to Cache Transfers (LDEV) Seq Drive to Cache Transfers (LDEV) CTL 0 Total Write Hit (RAID Group) CTL 1 Total Write Hit (RAID Group) The following performance metric is not supported in Sparkline View: Memory Usage (VMware Host) The following performance metric is not supported in Sparkline View: - Access Path Usage (MPB ESW) - Access Path Usage (CHA ESW) - Write Pending Rate (MPB CLPR) - Utilization (MP) No workaround No workaround No workaround 2016 Hitachi, Ltd. All rights reserved. 11

12 IAA IAA IAA IAA IAA IAA IAA The bottleneck analysis for the following metrics when used as a base point in Sparkline View is not supported. - Used Space % (Hyper-V Logical Disk) - Bus Resets (VMware Virtual Disk Partition) - Commands Aborted (VMware Virtual Disk Partition) - Read KBps (VMware Virtual Disk Partition) - Write KBps (VMware Virtual Disk Partition) - Read Operations (VMware Virtual Disk Partition) - Write Operations (VMware Virtual Disk Partition) The relationships between the storage systems and pass-through disks that are connected to virtual machines on Hyper-V are not displayed. If a virtual machine on Hypervisor is set to be monitored by a probe for monitoring Windows servers, the relationships between hosts and storage systems are no longer displayed. The relationships between Windows hosts (Hyper-V) and the following supported storage systems are not displayed. HUS 100 models HUS VM VSP Gx00 models VSP Fx00 models When a resource (such as a virtual machine or volume) is added, the change in the configuration of this resource is not detected. For monitoring profiles, the following conditions occur: When static thresholds are used, measured values are evaluated based on whether they are greater than or equal to the warning threshold. An event occurs when the measured value of the metric reaches the warning threshold. When you use either of the following thresholds, measured values are evaluated based on whether they are greater than or equal to the critical threshold. An event occurs when the measured value of the metric reaches the critical threshold. - Dynamic thresholds - Static thresholds when the same value is set for both the warning threshold and the critical threshold In the License dialog box, "-" is always displayed for the current capacity of the storage system. No workaround Please monitor Hypervisors by a probe Hitachi, Ltd. All rights reserved. 12

13 IAA IAA IAA IAA IAA IAA IAA When the following characters are included in configuration information of the monitoring target, you may not be able to monitor the monitoring target. - Multi byte character - [, ], {, },,, (, ) For the monitoring target that cannot be monitored, KNAQ33033-I message is output to the log. You may also see KNAQ01000-E error message. All the change histories in "Time period" may not be displayed on the "Analyze Related Changes" page. The KNAQ01000-E error can occur if you change the time period in the "Analyze Related Changes" page. "Threshold" displayed in the table of "Threshold Detail" page may not display correctly. The following field in "Edit Consumer" may not be updated. Grade The "Consumer Name of Related VM/Host" of Volume Assignment Rules for Consumers does not work. If you assign resources from dynamic threshold type to another target monitoring profile, the existing monitoring profile name can be displayed in events that occur after the reassignment. No workaround No workaround No workaround No workaround Please delete the setting of consumer, and create again. Assign volumes to a consumer manually. Reassign the resources to the old monitoring profile after the dynamic threshold calculation of the monitoring profile is completed. Then, assign the resources to the new target monitoring profile. Review the log to verify an entry for the KNAQ33008-I message that confirms the completion of the dynamic threshold calculation of the monitoring profile. Known problems for Data Center Analytics server The following table lists the known problems in the current release of Data Center Analytics server by defect ID. Defect ID Problem Workaround/Comments Wrong CPU and Memory Utilization are observed for the Cisco DCNM switch Indicator is shown for a volume that does not belong to Pool. The dashboard indicator is shown in red or amber instead of a (dash) for volumes without data You cannot reset the password to log on to the DCA management server and probe GUI if you upload multiple licenses with different keys. Download the license.txt file from /usr/local/megha/conf folder at temporary location, and upload this downloaded file while resetting the password Hitachi, Ltd. All rights reserved. 13

14 15588 You cannot download the diagnostic data from the Data Center Analytics server after upgrading from version 5.0 to a later version. Log on to SSH client like putty. Run the following command: $ sudo /usr/local/megha/bin/diag.sh It collects the diagnostic dump and save it on the following location /usr/local/megha/tmp with the name: High, incorrect values display for Disk Response Time in the EMC VNX Block node In the Alerts Violation tab, an incorrect violation count displays for the resources if you apply any other filter with the Category filter On the Cisco SAN Switch node, in the Zone Member Summary section, sometimes the fields display NA (not applicable) after you upgrade to v The dashboard indicators are not calculated for a specific time duration for Synthetic Attributes On the Alert Violation tab, in the alert details the Triggered at field displays the wrong time if the system time zone is set other than GMT. The zone information of Brocade Network Advisor is not visible in tree view. When all of the following conditions are met, the DCA GUI window cannot be displayed correctly, and operations can no longer be performed: - Internet Explorer is used to connect to Data Center Analytics. - Internet Explorer recognizes the Data Center Analytics management server as being in the local intranet zone. IAA If a new license has been added after the existing one expired, the connections from HIAA to DCA server may fail. diag_ gz Use Firefox or Google Chrome. Run the following command to stop the Data Center Analytics service: /usr/local/megha/bin/meghajetty.sh stop IAA If some nodes are added as a monitoring target, it may be displayed as license exceeded in DCA. And then run the following command to start the Data Center Analytics service: /usr/local/megha/bin/meghajetty.sh start If the current usage of "Base Nodes" is less than its limit, even the license exceeded message exists, there is no impact to the behavior Hitachi, Ltd. All rights reserved. 14

15 Known problems for Data Center Analytics probe The following table lists the known problems in the current release of Data Center Analytics probe by defect ID. Defect ID Problem Workaround/Comments You cannot reset the Analytics probe password if you upload multiple licenses with different keys On the Status window, the Cisco SAN Switch probe displays an error message Error in Data Collection, even if the data collection is successful. When all of the following conditions are met, the DCA GUI window cannot be displayed correctly, and operations can no longer be performed: - Internet Explorer is used to connect to Data Center Analytics. - Internet Explorer recognizes the Data Center Analytics management server as being in the local intranet zone. Download the license.txt file from /usr/local/megha/conf folder at temporary location, and upload this downloaded file while resetting the password. Use Firefox or Google Chrome. Installation notes Use a different host for the Data Center Analytics management server and the Analytics probe server. You cannot use a host on which Hitachi Command Suite Tuning Manager is installed for the Analytics probe server. Make sure the time zone setting is the same as on the server. For details, see "Setting the time zone for Data Center Analytics management server" and "Setting Time Zone for Analytics probe" in the Hitachi Infrastructure Analytics Advisor Installation and Configuration Guide. (IAS-6450) During the installation of the CPAN library Net::OpenSSH by the Data Center Analytics probe installer, you may see the following message. Output message: root@localhost s password: In such cases, make sure that the installation process resumes approximately 10 seconds after the message is displayed. Usage notes Sorting and filtering capabilities in certain table columns may not work correctly. Available values for REST API parameters are limited to the supported resources. When devices to be managed are added, collection of configuration information can take some time. During this time, HIAA is unable to display complete configuration information. Wait for a few minutes, and then make sure the configuration information displays correctly before using HIAA Hitachi, Ltd. All rights reserved. 15

16 During setup of the Hitachi Enterprise Storage probe, for the name of the RAID Agent host, specify the host name that is returned when you run the following command on the Analytics Probe server: uname n You cannot specify localhost. Use the default value for the RAID Agent collection interval. If you cannot access the DCA server, make sure that the certificate of the DCA server is correctly specified on the HIAA server and that the specified certificate is not expired. If you try to set up the Hitachi Enterprise Storage Probe immediately after setting up an instance in the RAID Agent, setup might fail with the following error: Validating RAID Agent details Validating RAID Agent details failed. Error:Storage details are not available through PD record Verify the values you specified. If they are correct, wait a few minutes, and then try again. You may have to wait for a considerable amount of time. The window for specifying the locale of the Data Center Analytics management server or the Analytics Probe server displays the option Japanese/Japan. The Japanese language is not supported. Select the option English/United States instead. Do not use secure connection (HTTPS) for the Hitachi Enterprise Storage probe to collect data from the RAID Agent. When setting up the Hitachi Enterprise Storage probe, select HTTP for Connection Type in the Provide RAID Agent Details section. The probe provides performance data to DCA by individual probes, and DCA determines the threshold of the performance information accordingly. Since DCA is notified of the performance data differently by each probe, the thresholds are also determined differently, and this in turn can delay the detection of performance event/alert. When you delete the monitoring target from the Analytics probe, reboot HIAA after 24 hours. If you fail to reboot, HIAA will not show the most up-to-date status of resources and instead continue to display the status before the deletion of the monitoring target. Do not change the password of FTP user meghadata used in DCA. Disable the relevant shell of meghadata as needed. DCA Server and DCA probe create the following users for the supported OS. Do not change these users. Megha Mars config Some resources may have fixed thresholds even when using the dynamic threshold. In such cases, you will not be able to monitor the resources when you perform the following tasks: Setting monitoring mode as other Setting monitoring mode as the dynamic threshold again If you re-create the monitoring profile, you can monitor the resources using the dynamic threshold Hitachi, Ltd. All rights reserved. 16

17 When Windows-based probe is used, the authentication information (username and password) on the Windows-based probe server and the monitoring target server should be the same. Even when Hyper-V services are enabled on a particular server, if no virtual machines exist on the server, the server is recognized as a Windows host. When a virtual machine is migrated by using Hyper-V's live migration function, the virtual machine before migration and the one after migration are recognized as two different virtual machines, and information about performance and configuration is not inherited. For probes for monitoring Windows servers, the only supported data collection methods are collection by using the Perfmon API and collection by using WMI queries. When data is to be collected by using System Center Operation Manager (SCOM) and System Center Configuration Manager (SCCM) or by using System Center Operation Manager (SCOM) and WMI queries, only Windows machines can be monitored in Data Center Analytics. If you want to monitor storage systems, enable LUN security. If LUN security is not enabled, HIAA might not be able to correctly obtain information about relationships between devices. In the environment using the Open Virtualization Format Archive (OVA) package, install VMware tools when you do time synchronization without using NTP. In the environment using the Open Virtualization Format Archive (OVA) package, a network card (NIC) is installed, and the udev function is disabled: if you add a network card, a network device name for each NIC changes dynamically by every OS startup. Execute the following procedure to make a network device name static. Enable the udev function. cp /lib/udev/rules.d/75-persistent-net-generator.rules.back /lib/udev/rules.d/75-persistent-net-generator.rules Reboot a virtual host. Confirm whether network setting is right. The DCA server has to be connected to one HIAA management server only. Error handling procedures This section describes the procedures for handling errors that may occur when using Infrastructure Analytics Advisor. Install the following package: java openjdk-devel Check the messages If a problem occurs, check any messages output to the GUI or log files, and then follow the instructions provided. In addition, check the log files to determine the cause of the problem, and then take appropriate action. Follow the troubleshooting steps If no messages are output when a problem occurs, or you are unable to correct the problem even after following the instructions in the message, collect maintenance information, and then contact customer support Hitachi, Ltd. All rights reserved. 17

18 Collecting maintenance information Collecting the log file for the Infrastructure Analytics Advisor management server 1. Run the hcmds64getlogs command. Collecting the log file of the Data Center Analytics management server 1. In the browser, type the Data Center Analytics management server URL 2. Log on to Data Center Analytics server. 3. On the Home page, from the Application menu, clickmanage. 4. On the Manage window, click the Download Diagnostic Data link. 5. On the Download Diagnostic Data window, click Download to download the file. Collecting the log file for the Analytics probe server 1. In the browser, type the Analytics probe URL Number>. 2. Log on to Analytics probe server. 3. Do steps 3 to 5 from the previous section. Collecting the log file for the RAID Agent To do the following procedure, you must use an OS user account with root user permissions: 1. Log on to the host on which the Analytics Probe server is installed. 2. Run the jpcras command with the following specific information: the information to be collected and the directory in which to store the collected information. The following is an example of how to run the jpcras command to collect all information and store the collected information in the /tmp/jpc/agt directory: /opt/jp1pc/tools/jpcras /tmp/jpc/agt all all The collected information is compressed by the tar command and the compress command, and then stored in the specified directory. The file name is as follows: jpcrasyymmdd.tar.z Where YYMMDD represents the year, month, and date. Accessing documentation This section lists the Infrastructure Analytics Advisor user documentation. Product documentation is available on Hitachi Data Systems Support Connect: Check this site for the most current 2016 Hitachi, Ltd. All rights reserved. 18

19 documentation, including important updates that may have been made after the release of the product Document name Hitachi Infrastructure Analytics Advisor User Guide Hitachi Infrastructure Analytics Advisor Installation and Configuration Guide Hitachi Infrastructure Analytics Advisor REST API Reference Guide Hitachi Infrastructure Analytics Advisor Data Analytics and Performance Monitoring Overview Hitachi Data Center Analytics User Guide Hitachi Data Center Analytics REST API Reference Guide Hitachi Data Center Analytics Query Language User Guide Document number MK-96HIAA MK-96HIAA MK-96HIAA MK-96HIAA MK-96HDCA MK-96HDCA MK-96HDCA Copyrights 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, electronic or mechanical, including photocopying and recording, or stored in a database or retrieval system for any purpose without the express written permission of Hitachi, Ltd. Hitachi, Ltd., reserves the right to make changes to this document at any time without notice and assumes no responsibility for its use. This document contains the most current information available at the time of publication. When new or revised information becomes available, this entire document will be updated and distributed to all registered users. Some of the features described in this document might not be currently available. Refer to the most recent product announcement for information about feature and product availability, or contact Hitachi, Ltd., at Notice: Hitachi, Ltd., products and services can be ordered only under the terms and conditions of the applicable Hitachi Data Systems Corporation agreements. The use of Hitachi, Ltd., products is governed by the terms of your agreements 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 from employees and other individuals to access relevant data; and 2) Verifying that data continues to be held, retrieved, deleted, or otherwise processed in accordance with relevant laws Hitachi, Ltd. All rights reserved. 19

20 Hitachi is a registered trademark of Hitachi, Ltd., in the United States and other countries. Hitachi Data Systems is a registered trademark and service mark of Hitachi, Ltd., in the United States and other countries. Archivas, BlueArc, Essential NAS Platform, HiCommand, Hi-Track, ShadowImage, Tagmaserve, Tagmasoft, Tagmasolve, Tagmastore, TrueCopy, Universal Star Network, and Universal Storage Platform are registered trademarks of Hitachi Data Systems Corporation. AIX, AS/400, DB2, Domino, DS6000, DS8000, Enterprise Storage Server, ESCON, FICON, FlashCopy, IBM, Lotus, MVS, OS/390, RS/6000, S/390, System z9, System z10, Tivoli, VM/ESA, z/os, z9, z10, zseries, z/vm, and z/vse are registered trademarks and DS6000, MVS, and z10 are trademarks of International Business Machines Corporation. All other trademarks, service marks, and company names in this document or website are properties of their respective owners. Microsoft product screen shots are reprinted with permission from Microsoft Corporation. Notice on Export Controls. The technical data and technology inherent in this Document may be subject to U.S. export control laws, including the U.S. Export Administration Act and its associated regulations, and may be subject to export or import regulations in other countries. Reader agrees to comply strictly with all such regulations and acknowledges that Reader has the responsibility to obtain licenses to export, re-export, or import the Document and any Compliant Products. IBM, AIX are trademarks of International Business Machines Corporation, registered in many jurisdictions worldwide. Internet Explorer is either a registered trademark or trademark of Microsoft Corporation in the United States and/or other countries. Linux(R) is the registered trademark of Linus Torvalds in the U.S. and other countries. Microsoft and Hyper-V are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Oracle and Java are registered trademarks of Oracle and/or its affiliates. This product includes software developed by the Apache Software Foundation ( This product includes software developed by IAIK of Graz University of Technology. RSA and BSAFE are either registered trademarks or trademarks of EMC Corporation in the United States and/or other countries. SUSE is a registered trademark or a trademark of SUSE LLC in the United States and other countries. Windows is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries. Windows Server is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries. JP1/Operations Analytics includes RSA BSAFE(R) Cryptographic software of EMC Corporation Hitachi, Ltd. All rights reserved. 20

21 This product includes software developed by Ben Laurie for use in the Apache-SSL HTTP server project. Portions of this software were developed at the National Center for Supercomputing Applications (NCSA) at the University of Illinois at Urbana-Champaign. This product includes software developed by the University of California, Berkeley and its contributors. This software contains code derived from the RSA Data Security Inc. MD5 Message- Digest Algorithm, including various modifications by Spyglass Inc., Carnegie Mellon University, and Bell Communications Research, Inc (Bellcore). Regular expression support is provided by the PCRE library package, which is open source software, written by Philip Hazel, and copyright by the University of Cambridge, England. The original software is available from ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/ This product includes software developed by Ralf S. Engelschall for use in the mod_ssl project ( This product includes software developed by Daisuke Okajima and Kohsuke Kawaguchi ( This product includes software developed by the Java Apache Project for use in the Apache JServ servlet engine project ( This product includes software developed by Andy Clark. Java is a registered trademark of Oracle and/or its affiliates Hitachi, Ltd. All rights reserved. 21