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 and important enhancements... 3 System requirements... 3 Resolved problems Known problems Installation notes Usage notes Accessing documentation Copyrights and licenses About this document This document (RN-96HIA000-05, Februray 2017) 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: , 2017 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). This release is a major release that adds new features and resolves multiple known problems. Product package contents Media 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 (Disk 1) Infrastructure Analytics Advisor server (Linux) Data Center Analytics server Infrastructure Analytics Advisor server (Windows) /ANALYTICS/ /IAAWIN/ analytics_install.sh analytics_uninstall.sh ANALYTICS.msi Analytics probe server /DCAPROBE/ dcaprobe_install.sh dcaprobe_uninstall.sh agent_update.sh Data Center Analytics server Windows-based probe /DCAWINPROBE/ DCA_Windows_Probe.exe Configuration Manager /CONFMANAGER/ install.sh Data Center Analytics server (Upgrade patch) Analytics probe server (Upgrade patch) /PATCH/DCA/v6.1 /PATCH/DCAPROBE/v6.1 hdca-server x86_64.rpm hdca-probe x86_64.rpm Media Program to be installed Directory Installation program included HIAA IAA server(linux) / analytics_ ova 2016, 2017 Hitachi, Ltd. All rights reserved. 2

3 installation media (Disk 2) Data Center Analytics server Analytics probe server Configuration Manager / dcaprobe_ ova Data Center Analytics server Windows-based probe /DCAWINPROBE/ DCA_Windows_Probe.exe New features and important enhancements New reports that report on storage capacity and capacity trends are introduced in Dashboard. You can now access detail performance reports in Data Center Analytics for resources that are being analyzed in the E2E view of Hitachi Infrastructure Analytics Advisor. 6 months reports are available in the Detail window of Hitachi Infrastructure Analytics Advisor for Hitachi storage pools. This release enables collection of granular data for intelligent and deep analysis of data when searching for spikes during trend pattern analysis of storage resources. Provides the capability to generate recovery plans for processor and cache bottlenecks. The Execute Action function is enabled at additional entry points, allows for multiple resources as target resources, and shows command line usage by definition in the template file. This version introduces new design improvements in web user interface. Linux is supported as a monitoring target in Data Center Analytics. For a complete list of supported management resources, see the Supported management resources section in this document. System requirements For using installer Infrastructure Analytics Advisor server 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 , 2017 Hitachi, Ltd. All rights reserved. 3

4 Operating system requirements (Linux) OS name Yum/rpm dependencies Architecture Red Hat Enterprise Linux Oracle Enterprise Linux (Unbreakable Enterprise Kernel) tcsh x64 Hardware requirements (Windows/Linux) 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 server Operating system requirements OS name Yum/rpm dependencies Architecture Red Hat Enterprise Linux Oracle Enterprise Linux (Unbreakable Enterprise Kernel) - perl - java openjdk - expect - openssl-devel - parted - xfsprogs - nss or higher - gcc - unzip - perl-cpan - expat-devel - sysstat - zip x64 Hardware requirements Prerequisite Minimum Recommended (Best practice (*1)) Processor Dual-Core processor Quad-core processor 2016, 2017 Hitachi, Ltd. All rights reserved. 4

5 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 server. You must specify the disk to install the product in the installer (dcaserver_install.sh). Prepare a physical disk for installing the Data Center Analytics server on physical machines. Analytics probe server Operating system requirements OS name Yum/rpm dependencies Architecture Red Hat Enterprise Linux Oracle Enterprise Linux (Unbreakable Enterprise Kernel) - perl - perl-cpan - gcc - java openjdk - samba - expect - openssl-devel - ftp - unzip - wget - glibc.i686 - glibc.x86_64 - libstdc++.i686 - libstdc++.x86_64 - net-tools - tcsh - libyaml - libgcc.x86_64 - nss-softokn-freebl.x86_64 - iproute.x86_64 - ncurses - openssh-clients - nss or higher - expat-devel - xinetd - sysstat - zip x64 Hardware requirements 2016, 2017 Hitachi, Ltd. All rights reserved. 5

6 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. Configuration Manager Operating system requirements OS name Yum/rpm dependencies Architecture Red Hat Enterprise Linux 6.5(*)-6.7 Oracle Enterprise Linux (Unbreakable Enterprise Kernel) - x64 (*) The following package is required: upstart el6_5.3.x86_64 or later. Hardware requirements Prerequisite Minimum Recommended Processor Dual-core processor Quad-core processor Memory 2 GB 4 GB minimum Disk space 0.8 GB , 2017 Hitachi, Ltd. All rights reserved. 6

7 Virtual appliance requirements 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. Note: For questions related to the Oracle Linux OS that is packaged with this product, contact Oracle customer support. Infrastructure Analytics Advisor server and Data Center Analytics server Guest operating system settings OS Item Settings Oracle Linux 6.8 (Architecture x86_64) Resource settings for the virtual machine Processor Memory Disk space Item Settings Quad-core processor (the number of virtual sockets: 4, the number of cores per virtual socket: 1) 16 GB 200 GB (Configure as two separate disks.) Note: The default installation directory is as follows. - The Infrastructure Analytics Advisor server directory is /opt/hitachi. - The Data Center Analytics server directory is /data. Analytics probe server and Configuration Manager Guest operating system settings OS Item Settings Oracle Linux 6.8 (Architecture x86_64) Resource settings for the virtual machine Item Settings Processor Memory Disk space Quad-Core processor (the number of virtual sockets: 4, the number of cores per virtual socket: 1) 10 GB 110 GB Note: The default installation directory is as follows. - The Analytics probe server directory is /home. - The Configuration Manager directory is /opt/hicommand. 2016, 2017 Hitachi, Ltd. All rights reserved. 7

8 Browser requirements Web browser/other Version Firefox 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 server GUI) Management target requirements Supported management resources The following tables show the monitoring targets of Infrastructure Analytics Advisor server. 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 G600 Hitachi Virtual Storage Platform G800 Hitachi Virtual Storage Platform F or later Hitachi Virtual Storage Platform F600 Hitachi Virtual Storage Platform F800 Hitachi Virtual Storage Platform G1000 Hitachi Virtual Storage Platform or later or later 2016, 2017 Hitachi, Ltd. All rights reserved. 8

9 Storage system Microcode version/hnas model Analytics probe name G1500 Hitachi Virtual Storage Platform F1500 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 Hosts OS name Version/Edition Analytics Probe name Windows Windows Server 2008 Standard Windows-based probe Enterprise Datacenter Windows Server 2008 R2 Standard Enterprise Datacenter Windows Server 2012 Standard Datacenter Windows Server 2012 R2 Standard Datacenter 2016, 2017 Hitachi, Ltd. All rights reserved. 9

10 Linux Red Hat Enterprise Linux 6.5 Linux Probe (*2) 7.1 SUSE Linux Enterprise Server Oracle Linux 7.0 CentOS 6.6 FC switches Switch name Version Analytics probe name Brocade Brocade Network Advisor Professional Plus Brocade Network Advisor Enterprise Brocade Network Advisor probe 12.3 Brocade Network Advisor Cisco Cisco Data Center Network Manager Cisco DCNM probe Cisco SAN Switch (CLI) - Cisco SAN Switch probe (*2) (*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 probe can be viewed in DCA server but cannot be analyzed by the IAA server. Related products To manage additional information about Hitachi storage systems (such as information about storage capacity and hosts), use the following products: Hitachi Device Manager version or later License keys The Hitachi Infrastructure Analytics Advisor product requires a license key. 2016, 2017 Hitachi, Ltd. All rights reserved. 10

11 In addition, the Data Center Analytics server and the Analytics probe server also require a license key. Obtain license keys from your HDS representative. Resolved problems From to Resolved problems for Infrastructure Analytics Advisor server The following table lists the problems that are resolved in this release by defect ID. Defect ID IAA IAA IAS IAS IAS IAS IAS Problems The following field in "Edit Consumer" may not be updated. Grade In the 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 When you select a resource in E2E View and open "Show Detail", the display value of "Capacity Saving" in the "Pool information" is incorrect. [ / or later] Disabled / Deduplication not available Compression / Deduplication not available Compression and Deduplication / Deduplication available If the path of the installation folder contains (blank space), the following command fails. reloadtemplate encryptpassword Discovered hosts are not automatically assigned to the corresponding threshold profile even if there are Host Assignment Rules. In [Dashboard Setting], each item in the [Report to Display] table is displayed in duplicate form when all the following conditions are met: Log on as the user without "Admin" permission and open [Dashboard Setting]. Change radio button from "Default Settings" to "Custom Settings". Uninstallation of RAID Agent fails because the permission to execute the script for uninstalling RAID Agent was not granted. In , this problem can be avoided by granting permission to execute the following script. /DCAPROBE/AGENTS/Agent_for_RAID/uninstall.sh Resolved problems for Data Center Analytics server The following table lists the problems that are resolved in this release by defect ID. 2016, 2017 Hitachi, Ltd. All rights reserved. 11

12 Defect ID Problems Alerts created for VSP/HUS-VM resources are also applied on VSP G1000/Gx00 resources On the Alert Violation tab, in the alert details the Triggered At field displays the wrong time if the machine time zone is set to any other than GMT While adding a new indicator, when the user clicks the Cancel button, the Add Alert that appears does not display Yes and No options to cancel the operation While adding an alert or indicator, the drop-down list can display duplicate metric entries In the Global Search, entering a space displays all resources for all tree nodes While adding the alert, in the Alert Notification section, an error is shown in the following scenario: If the address after contains a period, then the special character and numbers are not allowed after this period. Examples of ids that are allowed: abc-xyz@abc-xyz.abc abc-xyz@abc-xyz.abc.xyz abc-xyz@abcxyz.abc abc@xyz2.rte4.com Examples of ids that are not allowed: abc-xyz@abc-xyz.abc-xyz The Import threshold does not work on an Internet Explorer browser The Global Search does not search by switch IP address for Brocade Network Advisor and for VM clusters. Resolved problems for Analytics probe server The following table lists the problems that are resolved in this release by defect ID. Defect ID Problems For the EMC VMAX probe, Unisphere version 8.2, performance data of the Port Group is not collected. Resolved problems for Data Center Analytics Windows-based probe The following table lists the problems that are resolved in this release by defect ID. Defect ID Problems FTP to HDCA Server does not work after upgrade of the Windows-based probe when FIPS compliance is enabled. Known problems Known problems for the Infrastructure Analytics Advisor server The following table lists the known problems in this current release of Infrastructure Analytics Advisor server by defect ID. 2016, 2017 Hitachi, Ltd. All rights reserved. 12

13 Defect ID Problem Workaround/Comments IAA IP address information does not display for the following storage systems: Hitachi Virtual Storage Platform VSP G1000 VSP G1500 VSP F1500 VSP Gx00 models VSP Fx00 models Hitachi Unified Storage VM IAA Parity groups of external storage do not display. IAA IAA IAA IAA IAA IAA IAA IAA When a virtual machine on Hyper-V is monitored with the Data Center Analytics server Windows-based probe, the relation between the FC switch and host is not displayed. If you have a VM as a base point to display the E2E view, in the disk list, a disk other than the disk displayed in the E2E view displays. Performance events for the following metrics are not detected: Total IOPS (Pool) Read Hit (Parity Group) Utilization (Parity Group) The relationships between the storage systems and pass-through disks that are connected to virtual machines on Hyper-V are not displayed. When the following characters are included in configuration information of the monitoring target, you may not be able to monitor that target. - Multi byte character - [, ], {, },,, (, ) For the monitoring target that cannot be monitored, the KNAQ33033-I message is output to the log. You may also see the KNAQ01000-E error message. A "Threshold" displayed in the table of "Threshold Detail" page may not display correctly. If you assign resources from dynamic threshold type to another target monitoring profile, the existing monitoring profile name can be displayed if that occurs after the reassignment. The status of a resource is not changed even when the monitoring mode is changed from ON, Static or Dynamic to OFF. No workaround No workaround No workaround No workaround 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. Please restart IAA 24 hours after you change the monitoring mode. 2016, 2017 Hitachi, Ltd. All rights reserved. 13

14 IAA IAA It is not able to change the case of definition set by user saved via HIAA. When you select a component from "Access Path Usage (CHA ESW)" in Sparkline view and open the bottleneck analysis window, only one port is displayed even if additional ports are related. No workaround No workaround Known problems for the 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 switch of Cisco DCNM You cannot download the diagnostic data from the Data Center Analytics server after upgrading from base version 5.0 to any later versions. Log on to SSH client like PuTTY. Run the following command: $ sudo /usr/local/megha/bin/diag.sh It collects the diagnostic dump and saves it on the following location /usr/local/megha/tmp with the following name: The user from the Active Directory group can log on using the user@domain format. However, the user cannot log on using the domain\username format. Chart Reports are not plotted for Ports instances even though data is available A chart report does not get exported if its chart type is Stack and the scale is Logarithmic. When you upgrade the Data Center Analytics server to v8.0 using RPM on OEL 7.0 or RHEL 7.1, several warning messages are displayed. Global search functionality slows down when there are a large number of resources on Data Center Analytics server. Alert violations for the Alert definitions created before upgrading are not shown in the UI after upgrade. This is intermittently observed for the data collected in real time. diag_ gz Change the plot, scale type for that report and perform Batch Export. Ignore the warning message and continue with the upgrade. No workaround 2016, 2017 Hitachi, Ltd. All rights reserved. 14

15 Sometimes real time data is not shown in the chart reports even though it is available with the server. When you upgrade the Data Center Analytics server, the advertised.listeners property is not updated with Data Center Analytics server IP. Real time alerts sometimes are received at 5 minutes interval even if minute interval condition is met. In the tree designer, the Active Directory group user cannot publish the imported schema on the new Data Center Analytics server. In the tree designer, instances are not getting added to appropriate node when there are more than one node with the same name. In the tree designer > customized tree, when user try to add Indicators for Switches, all the related resources are not listed. In the tree designer, for a published tree you cannot rename a node if its parent node is a placeholder node. You must restart the megha jetty service to view the data in chart reports: 1. Stop the megha service using the command: /usr/local/megha/bin/meghajetty.sh stop 2. Verify the stopped status of megha service: /usr/local/megha/bin/meghajetty.sh status 3. Start the megha service using the command: /usr/local/megha/bin/meghajetty.sh start 1. Log on to the Data Center Analytics server through an SSH client (like PuTTY) using the following credentials: User: root Password: megha.jeos 2. Switch to megha user, using the command: su megha 3. Stop Kafka and Redis server: /usr/local/megha/bin/managekafka.sh stop /usr/local/megha/bin/manageredis.sh stop_all 4. Start the Kafka and Redis servers: usr/local/megha/bin/managekafka.sh start /usr/local/megha/bin/manageredis.sh start_all 5. Verify the Data Center Analytics server IP addresses is in following property file: /usr/local/megha/kafka/config/ser ver.properties" against property advertised.listeners=" 2016, 2017 Hitachi, Ltd. All rights reserved. 15

16 IAA When editing a published tree in the tree designer, only the schema and reports are displayed (no instances). In the tree designer, for a published tree you cannot rename a node if the new name is the same but with different capitalization. In the tree designer, after adding an existing report to the LDEV group level instance, an additional report is added with an invalid query. In the output of the installer console, you may see the following message after entering the device name to store application. Failed to find device for physical volume specified in the device or Failed to find physical volume This does not affect the installation of the Data Center Analytics server. Ignore the message and continue with the installation. Known problems for the Analytics probe server The following table lists the known problems in the current release of Analytics probe server by defect ID. Defect ID Problem Workaround/Comments The user in the Active Directory group can log on using the user@domain format. However, the user cannot log on using the domain\username format. In the Summary report, some values are shown as NA for Cisco SAN Switches. While adding the Hitachi Adaptable Modular Storage (AMS) probe, an Invalid message is displayed. When you upgrade the Data Center Analytics probe to v8.0 using RPM on OEL 7.0 or RHEL 7.1, several warning messages are displayed. You cannot add the NetApp probe when TLS = off. Real time data is not sent from probe if Kafka is not running. Even when Kafka server is recovered it requires a probe restart to start transmitting automatically. In the following location: /usr/local/megha/logs/ams in the in utl*.inf files, comment the entry of the registered AMS using #. Ignore the warning message and continue with the upgrade. 1. Log on to NetApp Storage System. 2. Run the command: options tls.enable off 3. Verify the TLS Status option is On. Stop and start the real time data collection for the specific probe that is showing this error. Installation notes If the installation of Infrastructure Analytics Advisor server on Windows failed, do the following procedure. 2016, 2017 Hitachi, Ltd. All rights reserved. 16

17 Procedure 1. Backup registry Start the registry editor by clicking Start and then Run, and then entering regedit. Then, export the whole registry. 2. Delete the following registry keys, if they exist. HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products\< HIAA User Data Code> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\ UserData\S \Products\< HIAA User Data Code> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall \< HIAA Product Code> Note: Registry information of Hitachi Infrastructure Analytics Advisor server vary with versions. Refer to the following table for registry values relevant to the product version. Name in the version Registry value procedure HIAA User Data Code E19CA03B15A77F489452ECA1E03754A D7A275629D579948B BCC9A F2B317B6467E1474FA84579F8B36E45F A5F47144E8BE2F74ABFCF66AC58B09FC HIAA Product Code {30AC91E0-A51B-4F E2ACE13057A4} {6572A7D8-5D B B2CCA9} {6B713B2F-E AF48-75F9B8634EF5} {44174F5A-EB8E-47F2-BACF-6FA65CB890CF} 3. Install Infrastructure Analytics Advisor server. Usage notes When you set up the Hitachi Enterprise Storage probe, use the default value for the RAID Agent collection interval except the "PLC (Pool Configuration)". Set 60 for the "PLC (Pool Configuration)" collection interval. When you delete the monitoring target from the Analytics probe server, reboot the Infrastructure Analytics Advisor server after 24 hours. If you fail to reboot, the Infrastructure Analytics Advisor server will not show the most up-to-date status of resources and instead continues to display the status before the deletion of the monitoring target. 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. In the following dashboards, information is displayed based on the latest value in the past 24 hours. In addition, the item displaying the total value of multiple resources shows the total value of all the related resources in the last 24 hours. 2016, 2017 Hitachi, Ltd. All rights reserved. 17

18 For example, in "Recent Capacity by Consumer", it aggregates volumes which are currently related, and also volumes which are removed from the consumer within the last 24 hours. Capacity by Storage System Capacity by Storage System (HUS 100 Storage Systems) Capacity of Drive Types by Storage System (HDP) Capacity of Drive Types by Storage System (HDT) Capacity of Drive Types by Storage System (HUS 100 Storage Systems) Capacity by Pool Capacity by Pool (HUS 100 Storage Systems) Capacity by Consumer Capacity by Consumer in the Past 6 Months Capacity by Consumer (HUS 100 Storage Systems) Capacity by Consumer in the Past 6 Months (HUS 100 Storage Systems) When using I/O activity with Automation Director, the minimum supported version is Error handling procedures This section describes the procedures for handling errors that may occur when using Infrastructure Analytics Advisor server. Install the following package: java openjdk-devel Check the messages If a problem occurs, check any messages output to the UI 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. Collecting maintenance information Collecting the log file for the Infrastructure Analytics Advisor server 1. Run the hcmds64getlogs command. Collecting the log file of the Data Center Analytics server 1. In the browser, type the Data Center Analytics server URL 2. Log on to Data Center Analytics server. 3. On the Home page, from the Application menu, click Manage. 2016, 2017 Hitachi, Ltd. All rights reserved. 18

19 4. In the Manage window, click the Download Diagnostic Data link. 5. In 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 server URL Number>. 2. Log on to Analytics probe server. 3. Do steps 3 to 5 from the preceding task. 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 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 Document number MK-96HIAA001 MK-96HIAA002 MK-96HIAA003 MK-96HIAA , 2017 Hitachi, Ltd. All rights reserved. 19

20 Document name 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-96HDCA002 MK-96HDCA006 MK-96HDCA005 Copyrights and licenses 2016, 2017 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 copying and recording, or stored in a database or retrieval system for commercial purposes without the express written permission of Hitachi, Ltd., or Hitachi Data Systems Corporation (collectively Hitachi ). Licensee may make copies of the Materials provided that any such copy is: (i) created as an essential step in utilization of the Software as licensed and is used in no other manner; or (ii) used for archival purposes. Licensee may not make any other copies of the Materials. 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 no responsibility for its use. The Materials contain the most current information available at the time of publication. Some of the features described in the Materials might not be currently available. Refer to the most recent product announcement for information about feature and product availability, or contact Hitachi Data Systems Corporation at Notice: Hitachi products and services can be ordered only under the terms and conditions of the applicable Hitachi agreements. The use of Hitachi 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 authorized 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. 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. Hitachi is a registered trademark of Hitachi, Ltd., in the United States and other countries. 2016, 2017 Hitachi, Ltd. All rights reserved. 20

21 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 International Business 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 Vista are registered trademarks or trademarks of Microsoft Corporation. Microsoft product screen shots are reprinted with permission from Microsoft Corporation. All other trademarks, service marks, and company names in this document or website are properties of their respective owners. 2016, 2017 Hitachi, Ltd. All rights reserved. 21