Hitachi Infrastructure Analytics Advisor

Transcription

1 Hitachi Infrastructure Analytics Advisor Installation and Configuration Guide MK-96HIAA May 2017

2 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. 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. 2

3 Contents Preface... 9 Intended audience Product version...10 Release notes Related documents...10 Document conventions Conventions for storage capacity values...12 Accessing product documentation Getting help...13 Comments Overview...15 Infrastructure Analytics Advisor overview Infrastructure Analytics Advisor system configuration...16 Installation methods...18 Installation workflow for a two-host configuration...18 Installation workflow for a three-host configuration Default installation directory System requirements System requirements for using the virtual appliance Infrastructure Analytics Advisor server and Data Center Analytics server requirements...24 Analytics probe server and Configuration Manager requirements System requirements for using the installer...25 Infrastructure Analytics Advisor server requirements (Linux) Infrastructure Analytics Advisor server requirements (Windows)...25 Data Center Analytics server requirements Analytics probe server requirements...27 Configuration Manager REST API requirements...29 Port requirements Supported browsers

4 Management target requirements Installation with virtual appliances Installing Infrastructure Analytics Advisor server and Data Center Analytics server on VMware vsphere Client...36 Preparing for installation Installation...36 Installing Analytics probe server on VMware vsphere Client...37 Preparing for installation Installation...39 Initial setup of the guest OS or VMs Installation on a Linux host...43 Verifying the yum/rpm dependency packages...44 Installing Infrastructure Analytics Advisor server and Data Center Analytics server on a Linux host Preparing for installation Installation...47 Installing Analytics probe server on a Linux host Preparing for installation Installation Installation of Infrastructure Analytics Advisor server on a Windows host Preparing for installation...58 Installation Initial setup after installation Initial setup of Data Center Analytics server Initial setup of Analytics probe server Initial setup of Infrastructure Analytics Advisor server...66 Logging on to Infrastructure Analytics Advisor server Changing the system account password Setting up a connection with Data Center Analytics server Configuring the mail server...68 Configuring initial settings for limiting the I/O activity of Hitachi storage resources...68 Setting up an environment for limiting the I/O activity of resources using Automation Director...68 Configuration overview for I/O controls using Automation Director...68 Installing the Configuration Manager REST API...69 Downloading analytics service templates and register storage systems...70 Configuring I/O controls for Infrastructure Analytics Advisor with Automation Director Setting up a connection with Automation Director...74 Configuring I/O control settings with user-defined scripts Prerequisites for setting I/O controls (using a script)...75 Creating the script files...76 Editing built-in command templates

5 Creating an I/O control task...80 Running the script files Checking the status of the script execution Initial setup for enabling Granular Data Collection Configuring SSH Creating keys on the Infrastructure Analytics Advisor server Configuring the public key authentication...84 Verifying SSH connections...85 Registering storage systems to be monitored by Granular Data Collection Adding a secondary Data Center Analytics server Configuring the downloader on the Data Center Analytics server Adding probes to Analytics probe server Setting up the Hitachi Enterprise Storage probe (when using RAID Agent) Verify the connection between host and monitoring targets (when using RAID Agent) Creating an instance environment (when using RAID Agent)...95 Adding Hitachi Enterprise Storage probe...98 Deleting an instance environment (when using RAID Agent) Setting up the Hitachi Enterprise Storage probe (when using Tuning Manager - Agent for RAID) Requirements for adding the Hitachi Enterprise Storage probe (when using Tuning Manager - Agent for RAID) Changing data to be collected by Tuning Manager - Agent for RAID Settings for communication from Analytics probe server to Tuning Manager - Agent for RAID Notes on using Tuning Manager - Agent for RAID Adding Hitachi Enterprise Storage probe Values used for estimating disk space when using Tuning Manager - Agent for RAID Adding Hitachi Adaptable Modular Storage (AMS) probe Adding Hitachi NAS probe Adding IBM XIV probe Adding EMC VNX File probe Adding EMC VNX Block probe Adding the EMC XtremIO probe Adding EMC VMAX probe Configuration in target environment Adding a megha user for the Symmetrix array Install EMC Solutions Enabler Symmetrix CLI Configure the environment variable entry in netcnfg file Adding EMC VMAX probe Adding VMAX probe for an already added EMC Unisphere for VMAX Editing details of EMC Unisphere for VMAX Adding Netapp probe Adding the Netapp probe in the Analytics probe server Creating a user for NetApp 7-mode Creating a user for NetApp C-mode Configuring security settings for NetApp storage systems Adding the Pure Storage probe Adding VMware probe

6 Adding Brocade Network Advisor probe Adding Cisco DCNM probe Adding Cisco SAN Switch probe Encrypting the CSV file Adding Linux probe Initial setup after adding a probe Installing Data Center Analytics server Windows-based probe Data collection methods Installing the Windows-based probe Configuring Data Center Analytics Windows-based probe Configuring the collection method Configuring the FTP or HTTPS server Starting the Windows-based probe service Initial setup after adding a probe Upgrading Infrastructure Analytics Advisor environment Upgrade workflow for a two-host configuration Upgrade workflow for a three-host configuration Verifying the yum/rpm dependency packages Upgrade the Infrastructure Analytics Advisor server and the Data Center Analytics server on a Linux host Upgrading the Infrastructure Analytics Advisor server on a Windows host Upgrading the Analytics probe server Upgrading the RAID Agent Upgrading the Data Center Analytics server Windows-based probe Upgrading the Configuration Manager REST API Postupgrade guidelines Configuring secure communications About security settings Workflow for configuring secure communications Configuring an SSL server (Infrastructure Analytics Advisor server) Creating a private key and a certificate signing request for Infrastructure Analytics Advisor server Applying for a server certificate for Infrastructure Analytics Advisor server from the certificate authority Enabling SSL communication for the Infrastructure Analytics Advisor server Checking the expiration date of the certificate for Infrastructure Analytics Advisor server Configuring SSL servers (Data Center Analytics server and Analytics probe server) Applying self-signed certificates to the Data Center Analytics server Exporting a self-signed certificate for the Data Center Analytics server Importing a certificate to the truststore file for the Infrastructure Analytics Advisor server (Data Center Analytics server) Applying server certificates to the Data Center Analytics server and the Analytics probe server Checking the expiration dates of certificates for Data Center Analytics server and Analytics probe server

7 Changing the SSL port number between the Infrastructure Analytics Advisor server and a web browser (Linux) Changing the SSL port number between the Infrastructure Analytics Advisor server and a web browser (Windows) Deleting a certificate from the truststore for Infrastructure Analytics Advisor server Configuring an SSL server (Automation Director) Importing a certificate to the truststore for the Infrastructure Analytics Advisor server (Automation Director) Changing Infrastructure Analytics Advisor system settings Starting and stopping the Infrastructure Analytics Advisor services Starting the Infrastructure Analytics Advisor server services Stopping the Infrastructure Analytics Advisor server services Starting the Data Center Analytics server or Analytics probe server services Stopping the Data Center Analytics server or Analytics probe server services Starting the RAID Agent services Stopping the RAID Agent services Changing the system information of Infrastructure Analytics Advisor server Changing the installation directory of Infrastructure Analytics Advisor server Changing the Infrastructure Analytics Advisor server host name Changing the Infrastructure Analytics Advisor server IP address Changing the port number used between Infrastructure Analytics Advisor server and the web browser (Linux) Changing the port number used between Infrastructure Analytics Advisor server and the web browser (Windows) Changing the port number used between Infrastructure Analytics Advisor server and common component Changing the port number between Infrastructure Analytics Advisor server and the SMTP server Changing the time settings of the Infrastructure Analytics Advisor server Change the format of syslog output Moving an Infrastructure Analytics Advisor server installation to another host Changing the system information of Analytics probe server Changing the port number used by the RAID Agent Changing the port number of the RAID Agent REST Web Service Restricting access to servers that access RAID Agent Performing a backup of Infrastructure Analytics Advisor Stopping services before a backup or restore Backing up Infrastructure Analytics Advisor server settings information Backing up the settings information and database of Data Center Analytics server Backing up the settings information of Analytics probe server Backing up the RAID Agent system RAID Agent definition information files to back up Starting Infrastructure Analytics Advisor services after a backup or restore Performing a restore of Infrastructure Analytics Advisor Stopping services before a backup or restore Restoring Infrastructure Analytics Advisor server settings information Restoring the settings information and database of Data Center Analytics server. 221 Restoring Analytics probe server settings information

8 Restoring the RAID Agent system Updating configuration information files that depend on the environment in which the RAID Agent is installed Starting Infrastructure Analytics Advisor services after a backup or restore Enabling system account locking Removing Infrastructure Analytics Advisor components Removing Infrastructure Analytics Advisor server and Data Center Analytics server from a Linux host Removing Infrastructure Analytics Advisor server from a Windows host Removing Analytics probe server Troubleshooting Connection to the Infrastructure Analytics Advisor server web client unsuccessful Logging on to Infrastructure Analytics Advisor server unsuccessful Starting Infrastructure Analytics Advisor server does not work Infrastructure Analytics Advisor server cannot connect to Data Center Analytics server Analytics probe server cannot connect to Data Center Analytics server via HTTPS A Infrastructure Analytics Advisor CLI commands List of Commands Command usage guidelines Usable characters for command arguments backupsystem encryptpassword hcmds64chgurl hcmds64fwcancel hcmds64getlogs hcmds64intg hcmds64srv hcmds64ssltool hcmds64unlockaccount reloadtemplate restoresystem B Infrastructure Analytics Advisor server services C User-specified properties file (config_user.properties) Index

9 Preface This manual provides information for Hitachi Infrastructure Analytics Advisor. Intended audience Product version Release notes Related documents Document conventions Conventions for storage capacity values Accessing product documentation Getting help Comments Preface 9

10 Intended audience This document is intended for system administrators and service administrators. The concepts, procedures, and information described in this document require the following skills: Knowledge of VMware vsphere operations, and the understanding related to setting up these products Basic knowledge of Linux Familiarity with RAID storage systems and their basic functions Product version Release notes This document revision applies to Infrastructure Analytics Advisor 3.1 or later. Read the release notes before installing and using this product. They may contain requirements or restrictions that are not fully described in this document or updates or corrections to this document. Release notes are available on Hitachi Data Systems Support Connect: knowledge.hds.com/documents. Related documents The following documents are referenced or contain more information about the features described in this manual. Hitachi Infrastructure Analytics Advisor User Guide, MK-96HIAA001 Hitachi Infrastructure Analytics Advisor REST API Reference Guide, MK-96HIAA003 Hitachi Infrastructure Analytics Advisor Data Analytics and Performance Monitoring Overview, MK-96HIAA004 Hitachi Data Center Analytics User Guide, MK-96HDCA002 Hitachi Data Center Analytics REST API Reference Guide, MK-96HDCA006 Hitachi Data Center Analytics Query Language User Guide, MK-96HDCA005 Hitachi Command Suite Automation Director Installation and Configuration Guide, MK-92HC204 Hitachi Command Suite Automation Director User Guide, MK-92HC205 Hitachi Command Suite Configuration Manager REST API Reference Guide, MK-92HC229 Hitachi Command Suite Tuning Manager Agent Administration Guide, MK-92HC013 Hitachi Command Suite Tuning Manager Installation Guide, MK-96HC Preface

11 Hitachi Command Suite System Requirements, MK-92HC209 Document conventions This document uses the following typographic conventions: Convention Description Bold Indicates text in a window, including window titles, menus, menu options, buttons, fields, and labels. Example: Click OK. Indicates emphasized words in list items. Italic Indicates a document title or emphasized words in text. Indicates a variable, which is a placeholder for actual text provided by the user or for output by the system. Example: pairdisplay -g group Monospace (For exceptions to this convention for variables, see the entry for angle brackets.) Indicates text that is displayed on screen or entered by the user. Example: pairdisplay -g oradb < > angle brackets Indicates variables in the following scenarios: Variables are not clearly separated from the surrounding text or from other variables. Example: Status-<report-name><file-version>.csv Variables in headings. [ ] square brackets Indicates optional values. Example: [ a b ] indicates that you can choose a, b, or nothing. { } braces Indicates required or expected values. Example: { a b } indicates that you must choose either a or b. vertical bar Indicates that you have a choice between two or more options or arguments. Examples: [ a b ] indicates that you can choose a, b, or nothing. { a b } indicates that you must choose either a or b. This document uses the following icons to draw attention to information: Icon Label Description Note Calls attention to important or additional information. Tip Provides helpful information, guidelines, or suggestions for performing tasks more effectively. Preface 11

12 Icon Label Description Caution Warns the user of adverse conditions and/or consequences (for example, disruptive operations, data loss, or a system crash). WARNING Warns the user of a hazardous situation which, if not avoided, could result in death or serious injury. Conventions for storage capacity values Physical storage capacity values (for example, disk drive capacity) are calculated based on the following values: Physical capacity unit Value 1 kilobyte (KB) 1,000 (10 3 ) bytes 1 megabyte (MB) 1,000 KB or 1,000 2 bytes 1 gigabyte (GB) 1,000 MB or 1,000 3 bytes 1 terabyte (TB) 1,000 GB or 1,000 4 bytes 1 petabyte (PB) 1,000 TB or 1,000 5 bytes 1 exabyte (EB) 1,000 PB or 1,000 6 bytes Logical capacity values (for example, logical device capacity, cache memory capacity) are calculated based on the following values: Logical capacity unit Value 1 block 512 bytes 1 cylinder Mainframe: 870 KB Open-systems: OPEN-V: 960 KB Others: 720 KB 1 KB 1,024 (2 10 ) bytes 1 MB 1,024 KB or 1,024 2 bytes 1 GB 1,024 MB or 1,024 3 bytes 1 TB 1,024 GB or 1,024 4 bytes 1 PB 1,024 TB or 1,024 5 bytes 1 EB 1,024 PB or 1,024 6 bytes Accessing product documentation Product user documentation is available on Hitachi Data Systems Support Connect: Check this site for the 12 Preface

13 most current documentation, including important updates that may have been made after the release of the product. 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 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. Comments Please send us your comments on this document to doc.comments@hds.com. Include the document title and number, including the revision level (for example, -07), and refer to specific sections and paragraphs whenever possible. All comments become the property of Hitachi Data Systems Corporation. Thank you! Preface 13

14 14 Preface

15 1 Overview Install Hitachi Infrastructure Analytics Advisor and its components using any of the following options: OVA, installer. Perform initial setup after the installation is successful. Infrastructure Analytics Advisor overview Infrastructure Analytics Advisor system configuration Installation methods Installation workflow for a two-host configuration Installation workflow for a three-host configuration Default installation directory Overview 15

16 Infrastructure Analytics Advisor overview Infrastructure Analytics Advisor provides a comprehensive application service-level and storage performance management solution that enables you to quickly identify and isolate performance problems, determine the root cause, and provide solutions. It enables proactive monitoring from the application level through all network and storage resources for end-to-end visibility of your monitored environment. It also increases performance of existing storage resources and storage availability by identifying problems before they can affect applications. Infrastructure Analytics Advisor collects and correlates data from these sources: Storage systems Fibre channel switches Hypervisors Hosts Installation components To use Infrastructure Analytics Advisor, you install and configure the following components: Infrastructure Analytics Advisor server: The primary component that communicates with the Data Center Analytics server. It correlates the configuration and performance data obtained by Data Center Analytics server to generate reports and enable data analytics for performance monitoring and problem resolution in your monitored infrastructure resources. Data Center Analytics server: This server processes performance and configuration data received from probes that connect to devices that are enabled for monitoring and provide the data to be used for reporting and analysis on the Infrastructure Analytics Advisor server. Analytics probe server: This server enables you to collect performance and configuration data from a target. Related topics Installation workflow for a two-host configuration on page 18 Installation workflow for a three-host configuration on page 20 Infrastructure Analytics Advisor system configuration The various installation and configuration methods and components are explained and illustrated. The following figure shows an example of a two-host configuration where Infrastructure Analytics Advisor server and Data Center Analytics server are 16 Overview

17 installed on the same host, and Analytics probe server is installed on a different host. The following figure shows an example of a three-host configuration where Infrastructure Analytics Advisor server, Data Center Analytics server, and Analytics probe server are all installed on different hosts. Note the following when configuring the system: Make sure that Data Center Analytics server and Analytics probe server are installed on different hosts. When you install Analytics probe server, RAID Agent is also installed. If you have Hitachi Tuning Manager - Agent for RAID installed in your environment, you can configure Tuning Manager - Agent for RAID with Infrastructure Analytics Advisor, instead of using RAID Agent. The Data Center Analytics server must be connected to one Infrastructure Analytics Advisor server only. Overview 17

18 If you want to limit the I/O activity of resources by using the Storage I/O controls feature of Infrastructure Analytics Advisor, install Hitachi Automation Director and the Hitachi Configuration Manager REST API on a host of your choice. If you are already using Automation Director or the Configuration Manager REST API, you can configure the product or products that you are currently using with Infrastructure Analytics Advisor. The Analytics probe server cannot be installed on a host where the following products are installed: Tuning Manager Agent components for Tuning Manager The components of Infrastructure Analytics Advisor cannot be installed in a cluster environment. Installation methods You can install components of Infrastructure Analytics Advisor either by deploying a virtual appliance or by using an installer. For a new installation, we recommend deploying a virtual appliance. You can deploy a virtual appliance only when you perform a new installation. The following table shows the installation methods that can be used for each component of Infrastructure Analytics Advisor: Component OS of the target host Installation method Infrastructure Analytics Advisor server Linux virtual appliances 1 installer Windows installer Data Center Analytics server Linux virtual appliances 1 installer Analytics probe server Linux virtual appliances 2 installer Notes: 1. You can create an environment in which both the Infrastructure Analytics Advisor server and the Data Center Analytics server are installed. 2. Configuration Manager REST API is also installed in a deployed environment. Installation workflow for a two-host configuration The workflow from installation to setup differs depending on the installation method you use. If you want to create a two-host configuration where Infrastructure Analytics Advisor server and Data Center Analytics server are installed on the same host, and Analytics probe server is installed on a different host, we recommend deploying virtual appliances. The following figure shows the workflow for creating an Infrastructure Analytics Advisor system in a two-host configuration. 18 Overview

19 Related topics Installing Infrastructure Analytics Advisor server and Data Center Analytics server on VMware vsphere Client on page 36 Installing Analytics probe server on VMware vsphere Client on page 37 Initial setup of the guest OS or VMs on page 40 Verifying the yum/rpm dependency packages on page 44 Installing Infrastructure Analytics Advisor server and Data Center Analytics server on a Linux host on page 46 Installing Analytics probe server on a Linux host on page 51 Initial setup of Data Center Analytics server on page 62 Initial setup of Analytics probe server on page 63 Initial setup of Infrastructure Analytics Advisor server on page 66 Configuring initial settings for limiting the I/O activity of Hitachi storage resources on page 68 Adding probes to Analytics probe server on page 91 Configuring secure communications on page 159 Overview 19

20 Installation workflow for a three-host configuration The workflow from installation to setup depends on the OS of the Infrastructure Analytics Advisor server host. If you want to create a threehost configuration where Infrastructure Analytics Advisor server, Data Center Analytics server, and Analytics probe server are all installed on different hosts, run the installer to create the Infrastructure Analytics Advisor system. The following figure shows the workflow for creating an Infrastructure Analytics Advisor system in a three-host configuration. Related topics Verifying the yum/rpm dependency packages on page 44 Installing Infrastructure Analytics Advisor server and Data Center Analytics server on a Linux host on page 46 Installing Analytics probe server on a Linux host on page 51 Preparing for installation on page 58 Installation on page 58 Initial setup of Data Center Analytics server on page Overview

21 Initial setup of Analytics probe server on page 63 Initial setup of Infrastructure Analytics Advisor server on page 66 Configuring initial settings for limiting the I/O activity of Hitachi storage resources on page 68 Adding probes to Analytics probe server on page 91 Configuring secure communications on page 159 Default installation directory The default installation directory for each component is as shown in the following table. Component name Infrastructure Analytics Advisor server Default installation directory In Windows C:\Program Files\HITACHI In Linux /opt/hitachi Data Center Analytics server Analytics probe server Configuration Manager REST API /data /home /opt/hicommand/confmanager Overview 21

22 22 Overview

23 2 System requirements The system requirements for Infrastructure Analytics Advisor server, Data Center Analytics server, Analytics probe server, and Configuration Manager REST API are explained. System requirements for using the virtual appliance System requirements for using the installer Port requirements Supported browsers Management target requirements System requirements 23

24 System requirements for using the virtual appliance Infrastructure Analytics Advisor server and Data Center Analytics server requirements Before you install the Infrastructure Analytics Advisor server and Data Center Analytics server using the virtual appliance, review the guest operating system settings and virtual machine resource settings requirements. Guest operating system settings Item OS Settings Oracle Linux 7.3 (Architecture x86_64) Resource settings for the virtual machine Item Settings Processor Quad-Core processor (the number of virtual sockets: 4, the number of cores per virtual socket: 1) Memory Disk space 16 GB 700 GB (Configure as two separate disks.) sda: 100 GB LVM (DCAvg-DCAlv00): 600 GB (for Data Center Analytics server installation) Analytics probe server and Configuration Manager requirements Before you install the Analytics probe server and Configuration Manager using the virtual appliance, review the guest operating system settings and virtual machine resource settings requirements. Guest operating system settings Item OS Settings Oracle Linux 7.3 (Architecture x86_64) Resource settings for the virtual machine Item Settings Processor Quad-Core processor (the number of virtual sockets: 4, the number of cores per virtual socket: 1) 24 System requirements

25 Item Memory Disk space Settings 10 GB 110 GB System requirements for using the installer Infrastructure Analytics Advisor server requirements (Linux) The requirements for Linux operating systems, kernel parameters, and hardware are shown in the following. Supported operating systems Red Hat Enterprise Linux , (x64) Oracle Linux , (Unbreakable Enterprise Kernel) (x64) Yum/rpm dependencies tcsh net-tools Kernel parameters In Linux, before installing the Infrastructure Analytics Advisor server, you must set the following kernel parameter values: File Parameter Value to be set /etc/sysctl.conf Fourth parameter (SEMMNI) of kernel.sem The larger of 1024 and the following value: 24 + currentsystem-value /etc/security/limits.conf nofile The larger of 8514 and the following value: current-system-value Hardware requirements Prerequisites Minimum Recommended Processor Dual-Core processor Quad-Core processor Memory 8 GB 16 GB minimum Disk space 50 GB 100 GB minimum Infrastructure Analytics Advisor server requirements (Windows) The requirements for Windows operating systems and hardware are shown in the following. System requirements 25

26 Supported operating systems OS name Edition SP Architecture Windows Server 2008 R2 1 Standard Enterprise Datacenter Windows Server Standard Datacenter Windows Server 2012 R2 2 Standard Datacenter SP1 No SP No SP x64 x64 x64 Notes: 1. Server core is not supported. 2. Server core and Minimal Server Interface are not supported. Hardware requirements Prerequisites Minimum Recommended Processor Dual-Core processor Quad-Core processor Memory 8 GB 16 GB minimum Disk space 50 GB 100 GB minimum Data Center Analytics server requirements Before you install Data Center Analytics server, review the requirements for the OS, the kernel parameters, and the hardware. Supported operating systems Red Hat Enterprise Linux , (x64) Oracle Linux , (Unbreakable Enterprise Kernel) (x64) Yum/rpm dependencies java openjdk-devel (update 91 or later) expect parted openssl-devel nss or higher gcc unzip perl perl-cpan perl-xml-simple * epat-devel sysstat zip 26 System requirements

27 bc *: The rpm dependencies only exist in the following OS. Red Hat Enterprise Linux 7.0 or later. Oracle Linux 7.0 or later. Kernel parameters In a Linux environment, before installing the Data Center Analytics server, you need to set the following kernel parameter values: File Parameter Value to be set /etc/sysctl.conf Fourth parameter (SEMMNI) of kernel.sem The larger of 1024 and the following value: 24 + currentsystem-value /etc/security/limits.conf nofile The larger of 8514 and the following value: current-system-value Hardware requirements Prerequisites Minimum Recommended (Best practice 1 ) Processor Dual-Core processor Quad-Core processor Memory 8 GB 16 GB Disk space GB 600 GB Notes: 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 one on the OS on which Data Center Analytics server is installed. You must specify the disk for installing the product when you run the installation command analytics_install.sh. You must prepare a physical disk for installing the Data Center Analytics server on physical machines. Analytics probe server requirements Before you install the Analytics probe server, review the OS, hardware, and desktop requirements. Supported operating systems Red Hat Enterprise Linux , (x64) Oracle Linux , (Unbreakable Enterprise Kernel) (x64) Yum/rpm dependencies perl perl-cpan System requirements 27

28 perl-digest-md5 * perl-xml-simple * gcc java openjdk-devel (update 91 or later) 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-softoknfreebl.x86_64 iproute.x86_64 ncurses openssh-clients nss or higher expat-devel xinetd sysstat zip bc *: The rpm dependencies only exist in the following OS. Red Hat Enterprise Linux 7.0 or later. Oracle Linux 7.0 or later. Hardware requirements Prerequisites Minimum Recommended (Best practice * ) Processor Dual-Core processor Quad-Core processor Memory 8 GB 16 GB minimum Disk space 100 GB 150 GB 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. 28 System requirements

29 Configuration Manager REST API requirements Before you install the Configuration Manager REST API, review the OS and hardware requirements. Supported operating systems Red Hat Enterprise Linux , (x64) Oracle Linux , (Unbreakable Enterprise Kernel) (x64) Yum/rpm dependencies upstart el6_5.3.x86_64 or later 1 glibc el7.i686.rpm or later 2 net-tools git.el7.x86_64.rpm or later 2 openslp-server el7.x86_64.rpm or later 2 perl el7.x86_64.rpm or later 2 tcsh el7.x86_64.rpm or later 2 Note: 1. The rpm dependencies only exist in the following OS: Red Hat Enterprise Linux The rpm dependencies only exist in the following OS: Red Hat Enterprise Linux 7.0 or later Hardware requirements Prerequisites Minimum Recommended Processor Dual-Core processor Quad-Core processor Memory 2 GB 4 GB minimum Disk space 0.8 GB - Port requirements Before you install the Data Center Analytics server or Analytics probe server, review the desktop, port, and firewall requirements. Table 1 Desktop requirements (Data Center Analytics server) Source IP address Target IP address Default port Protocol User Desktop IP address of the Data Center Analytics server 8443 TCP System requirements 29

30 Table 2 Desktop requirements (Analytics probe server) Source IP address Target IP address Default port Protocol User Desktop IP address of the Analytics probe server 8443 TCP 22 * TCP * : Required for connecting to the Analytics probe server through the SSH client Table 3 Probe port and firewall requirements Probe name Collection method Source IP address Target IP address Default port Protocol Storage systems Hitachi AMS SNM2API Analytics probe server AMS Controller 2000 TCP Hitachi Enterprise Storage RAID Agent or Tuning Manager - Agent for RAID Analytics probe server RAID Agent Server or Tuning Manager - Agent for RAID Server HTTP Hitachi Device Manager API Analytics probe server Hitachi Device Manager Server 2001 HTTP 2443 HTTPS Hitachi NAS RUSC/CLI Analytics probe server HNAS SMU 22 SSH IBM XIV 1 xcli Analytics probe server XIV Storage System Management IP 7778 TCP NetApp ONTAP API Analytics probe server NetApp Filer 443 HTTPS VMAX Unisphere REST API Analytics probe server Unisphere Server 8443 TCP SYMCLI Analytics probe server Solution Enabler 2707 TCP VNX Block 2 naviseccli Analytics probe server VNX Storage Processor A and B 443 HTTPS 80 HTTP VNX File VNX CLI Station CLI Analytics probe server VNX Storage 22 SSH XtremIO XMS (Rest API) Analytics probe server Pure Storage Rest AP Analytics probe server XMS 443 HTTPS Pure Storage 80 HTTP 443 HTTPS Hypervisors 30 System requirements

31 Probe name Collection method Source IP address Target IP address Default port Protocol VMware Windowsbased (Hyper- V) VMware vcenter API Analytics probe server VMware vcenter Server/ VMware ESXi Host 443 TCP WMI Windowsbased Windows Host/ 135 TCP Perfmon probe Hyper-V 135 and 445 SCOM SCOM server 5723, 5724, and SCCM SCCM server 1433 FC Switches Brocade FC Switch (BNA) BNA (REST API) Analytics probe server BNA server 80 HTTP Cisco DCNM DCNM (Web Services) Analytics probe server DCNM Server 80 HTTP 443 HTTPS Cisco SAN Switch Cisco Switch CLI Analytics probe server Cisco FC Switch 22 SSH Hosts Linux ssh Analytics probe Linux host 22 SSH xinetd server 1111 xinetd Notes: 1. The CLI installer (xivcli build3-linux32.tar) for IBM XIV probe is available from the IBM support site, deployed on the probe. 2. The NaviCLI runs locally on the probe machine, which internally makes HTTP or HTTPS calls to the VNX storage. Supported browsers Infrastructure Analytics Advisor supports the following browsers. Table 4 Supported browsers Web browser/other Version Firefox ESR 45 Internet Explorer 11 ESR 52 Chrome for Work Flash Player Latest version of stable channel 21.0 or later (to use custom reports in Data Center Analytics server) System requirements 31

32 Management target requirements The following storage system series, hypervisors, hosts, and FC switches are supported for management targets. Table 5 Storage systems Storage system series Storage system Microcode/ HNAS model Analytics probe name VSP Hitachi Virtual Storage Platform or later VSP G series VSP Gx00 Hitachi Virtual Storage Platform or models 3 G200 (VSP G200) later Hitachi Enterprise Storage probe 1,2 Hitachi Virtual Storage Platform G400 (VSP G400) Hitachi Virtual Storage Platform G600 (VSP G600) Hitachi Virtual Storage Platform G800 (VSP G800) VSP G Hitachi Virtual Storage Platform or G1000 later VSP G Hitachi Virtual Storage Platform or later G1500 VSP F series VSP Fx00 Hitachi Virtual Storage Platform or models 3 F400 (VSP F400) later Hitachi Virtual Storage Platform F600 (VSP F600) Hitachi Virtual Storage Platform F800 (VSP F800) VSP F Hitachi Virtual Storage Platform or later F1500 HUS VM Hitachi Unified Storage VM or later HUS100 4 Hitachi Unified Storage 110 (HUS110) Hitachi Unified Storage 130 (HUS130) or later Hitachi Adaptor Modular Storage (AMS) probe Hitachi Unified Storage 150 (HUS150) Hitachi NAS 4 HNAS VSP G600 (Unified) HNAS probe 5 Notes: 32 System requirements

33 Storage system series Storage system Microcode/ HNAS model Analytics probe name 1. When using Hitachi Enterprise Storage probe, make sure that the RAID Manager LIB is installed in the same server as the Hitachi Enterprise Storage probe. 2. The storage systems from which the Hitachi Enterprise Storage probe can collect data are as listed in the above table irrespective of whether the Hitachi Enterprise Storage probe is used via RAID Agent or Tuning Manager - Agent for RAID. 3. The use of Server Priority Manager to limit I/O activity is supported. However, for VSP Gx00 models and VSP Fx00 models with microcode x or earlier, if you specify or refer to Server Priority Manager information via Storage I/O controls feature in Infrastructure Analytics Advisor, an error might occur. 4. Granular Data Collection cannot be used on this storage system series. 5. The data collected by the HNAS probe can be viewed only in the Data Center Analytics server. Note: To manage additional information about Hitachi storage systems (such as information about storage capacity and hosts), use the Device Manager or later. For I/O control settings using Server Priority Manager, use Automation Director or Table 6 Hypervisors Product name Version Analytics probe name VMware vcenter server 5.0 or later VMware probe VMware ESXi Hyper-V Windows Server 2008 R2 Hyper-V Windows Server 2012 Hyper-V Windows Server 2012 R2 Hyper-V 5.0 or later Hyper-V 2.0 Hyper-V 3.0 Hyper-V 3.1 Windows-based probe Table 7 Hosts OS name Version/Edition Analytics probe name Windows Windows Server 2008 Standard Enterprise Datacenter Windows-based probe Windows Server 2008 R2 Standard Enterprise Datacenter Windows Server 2012 Standard Datacenter System requirements 33

34 OS name Version/Edition Analytics probe name Windows Server 2012 R2 Standard Datacenter Linux Red Hat Enterprise Linux Linux probe * SUSE Linux Enterprise Server Oracle Linux 7.0 CentOS 6.6 *: The data collected by the Linux probe can be viewed only in the Data Center Analytics server. Table 8 FC switches Switch name Software Version Analytics probe name Brocade Brocade Network Advisor Professional Plus Brocade Network Advisor Enterprise Brocade Network Advisor Brocade FC Switch (BNA) probe Cisco Cisco Data Center Network Manager Cisco DCNM probe Cisco SAN Switch (CLI) - Cisco SAN Switch probe * *: The data collected by the Cisco SAN Switch probe can be viewed only in the Data Center Analytics server. 34 System requirements

35 3 Installation with virtual appliances Install Infrastructure Analytics Advisor using an OVA by preparing your environment, installing all components, and performing initial setup. Installing Infrastructure Analytics Advisor server and Data Center Analytics server on VMware vsphere Client Installing Analytics probe server on VMware vsphere Client Initial setup of the guest OS or VMs Installation with virtual appliances 35

36 Installing Infrastructure Analytics Advisor server and Data Center Analytics server on VMware vsphere Client The installation of Infrastructure Analytics Advisor server and Data Center Analytics server on a VMware vsphere Client is explained and illustrated. Preparing for installation Before you start deploying virtual appliances for Infrastructure Analytics Advisor server and Data Center Analytics server, review the following prerequisites. Prerequisites Review hardware and software requirements Port requirements Time zone settings License Host name resolution Description Review the requirements for Infrastructure Analytics Advisor server and Data Center Analytics server. Make sure that you meet all the hardware and software requirements. Make sure that the ports you specify are available for communication. The default ports are 8443 (Data Center Analytics server) and (Infrastructure Analytics Advisor server). The times and time zones of the following servers must all be synchronized: Infrastructure Analytics Advisor server Data Center Analytics server Analytics probe server Obtain the Infrastructure Analytics Advisor server and the Data Center Analytics server licenses from your HDS representative. When you use DHCP to assign an IP address to a host, configure the Domain Name System (DNS) server so that the IP address can be resolved from the host name. Note that if you use a static IP address, the setting to resolve the IP address from the host name will be added to the hosts file automatically. Related topics Infrastructure Analytics Advisor server and Data Center Analytics server requirements on page 24 Installation on page 36 Installation Deploy the OVA file for Infrastructure Analytics Advisor server and Data Center Analytics server using the installation media. Procedure 1. From a VMware vsphere client, log on to the VMware ESXi server. 36 Installation with virtual appliances

37 2. Deploy the OVA file for Infrastructure Analytics Advisor server and Data Center Analytics server from the installation media for virtual appliances. From the VMware vsphere client, select File > Deploy OVF Template, and then follow the on-screen instructions. Tip: Select Thick Provision Lazy Zeroed in the window for selecting the disk provisioning method. 3. Change the settings so that the virtual machine does not connect to the network when started. When deployment is complete, the following network settings will be set by default for the virtual machine. This operation is not required if you are sure that the IP addresses will not conflict. IP address: Net mask: Default gateway: a. Right-click the virtual machine that you want to edit, and then select Edit Settings. b. In the Hardware tab, select Network adapter 1, and then clear the Connect at power on check box. 4. Start the virtual machine. When you logon for the first time, use the following user ID and password: User ID: root Password: manager After you logon, you can change the root password. 5. Confirm that the network setting is correct. Next steps Run the setup tool on the guest OS, and then specify the initial settings for the guest OS. Related topics Initial setup of the guest OS or VMs on page 40 Installing Analytics probe server on VMware vsphere Client Review the prerequisites before installing an Analytics probe server using the virtual appliance. Installation with virtual appliances 37

38 Preparing for installation Before you deploy a virtual appliance for Analytics probe server, review the hardware, software, and port requirements, synchronize the time zone, and obtain the license. Prerequisites Review hardware and software requirements Port requirements Review virtual system operations Time zone settings License Description Review the Analytics probe server requirements. Make sure that you meet all the hardware and software requirements. Make sure that the ports you specify are available for communication. The default port is The default port for SSH is 22. Review the following requirements when you run RAID Agent in a virtual environment. Setting the LANG environment variable*: Before setting up the RAID Agent, you must specify C for the LANG environment variable on the Analytics probe server host. Configuring settings so that the command device can be accessed from a guest OS: If you want to monitor VSP, VSP F series, VSP G series, or HUS VM, you must configure the settings to enable accesses from a guest OS to command devices. For details, see the documentation for your virtual system. Use VMware vsphere Client file to add a device to the guest OS. By doing so, if you designate a command device as the device to be added, the command device can be accessed from the guest OS. When configuring settings to add a device, make sure that the following requirements are met: Device type: Hard disk Disk selection: Raw device mapping Compatibility mode: Physical Virtual disks (including VMware VVols) are not used for the command device. Note about replication: When you use a virtualization system to replicate an OS environment in which the RAID Agent is running, do not apply the replicated environment to any other host. Startup of the RAID Agent might fail in the replicated environment. The times and time zones of the following servers must all be synchronized: Infrastructure Analytics Advisor server Data Center Analytics server Analytics probe server Obtain the Analytics probe server license from your HDS representative. *: At startup, RAID Agent is subject to the system LANG environment variable. If the LC_ALL environment variable differs from the LANG environment variable, either unset LC_ALL or change its value to match the LANG value. Use the following example as a reference when setting the LANG value for RAID Agent. The last line is an example of coding that unsets the LC_ALL value. 38 Installation with virtual appliances

39 Prerequisites Description Example settings: ## Set Environment-variables PATH=/sbin:/bin:/usr/bin:/opt/jp1pc/bin SHLIB_PATH=/opt/hitachi/common/lib LD_LIBRARY_PATH=/opt/hitachi/common/lib LIBPATH=/opt/hitachi/common/lib HCCLIBCNF=/opt/jp1/hcclibcnf LANG=C export PATH SHLIB_PATH LD_LIBRARY_PATH LIBPATH HCCLIBCNF LANG unset LC_ALL Related topics Analytics probe server and Configuration Manager requirements on page 24 Installation on page 39 Installation Deploy the OVA file for an Analytics probe server using the installation media. Procedure 1. From a VMware vsphere client, log on to the VMware ESXi server. 2. Deploy the OVA file for Analytics probe server from the installation media for virtual appliances. From the VMware vsphere client, select File > Deploy OVF Template, and then follow the on-screen instructions. Tip: Select Thick Provision Lazy Zeroed in the window for selecting the disk provisioning method. 3. Change the settings so that the virtual machine does not connect to the network when started. When deployment is complete, the following network settings will be set by default for the virtual machine. This operation is not required if you are sure that the IP addresses will not conflict. IP address: Net mask: Default gateway: a. Right-click the virtual machine that you want to edit, and then select Edit Settings. b. In the Hardware tab, select Network adapter 1, and then clear the Connect at power on check box. 4. Start the virtual machine. Installation with virtual appliances 39

40 When you logon for the first time, use the following user ID and password: User ID: root Password: manager After you logon, you can change the root password. 5. Confirm that the network setting is correct. Next steps Run the setup tool on the guest OS, and then specify the initial settings for the guest OS. Related topics Initial setup of the guest OS or VMs on page 40 Initial setup of the guest OS or VMs After deploying the virtual appliance, run the setup tool (hvaconfig) to specify the initial settings for the guest OS. Procedure 1. From the VMware vsphere Client, log on to the guest OS. 2. Run the hvaconfig command that is stored in /opt/hiaa/vmtool. Note: You can run the setup tool only once. To change the settings after running the setup tool, use the operating system commands. 3. In the setup tool, you can specify the following settings. Network settings: Host name: The Analytics probe server does not support FQDNs. Omit the domain name when specifying the host name. IP address: The setup tool specifies an IPv4 address. Default gateway Network mask DNS server (2 servers maximum) Time settings: Time zone Specify the time zone in the area/location format. If you do not know the specifiable values, use the following command in advance to check the time zone values that can be set. timedatectl list-timezones 40 Installation with virtual appliances

41 The times and time zones of the following servers must be synchronized: Infrastructure Analytics Advisor server Data Center Analytics server Analytics probe server NTP server Security setting: Server certificate 4. Check the contents of the list that displays your specified settings, and then apply the settings. After the settings are applied, the guest OS restarts automatically. 5. If the virtual machine is not connected to the network when deployed, perform the following steps to enable the network adapter: a. Log on to the guest OS. b. Stop the virtual machine by running the shutdown command. c. Right-click the virtual machine that you want to stop, and then select Edit Settings d. In the Hardware tab, select Network adapter 1, and then select the Connect at power on check box. e. Run the Power On the virtual machine. Next steps Perform the initial setup of Data Center Analytics server and Analytics probe server. Related topics Initial setup of Data Center Analytics server on page 62 Initial setup of Analytics probe server on page 63 Installation with virtual appliances 41

42 42 Installation with virtual appliances

43 4 Installation on a Linux host Install Infrastructure Analytics Advisor on Linux by preparing your environment, installing all components, and performing initial setup. Verifying the yum/rpm dependency packages Installing Infrastructure Analytics Advisor server and Data Center Analytics server on a Linux host Installing Analytics probe server on a Linux host Installation on a Linux host 43

44 Verifying the yum/rpm dependency packages Before installing or upgrading the Infrastructure Analytics Advisor server, Data Center Analytics server, or Analytics probe server, check whether all of the yum/rpm dependency packages required for each component are installed. If some packages are missing, you need to install them as an additional step. You can obtain the yum/rpm dependency packages from the Linux OS media or the distribution website, such as for Red Hat Enterprise Linux. Prerequisite packages The following table lists the packages required to run each component. Component name Yum/rpm dependencies Notes Infrastructure Analytics Advisor server tcsh net-tools - Data Center Analytics server java openjdk-devel (update 91 or later) expect parted openssl-devel nss or higher gcc unzip perl perl-cpan perl-xml-simple expat-devel sysstat zip bc Analytics probe server perl perl-cpan perl-digest-md5 perl-xml-simple gcc java openjdk-devel (update 91 or later) samba expect openssl-devel ftp unzip wget glibc.i686 glibc.x86_64 libstdc++.i686 libstdc++.x86_64 net-tools tcsh The package nss may not be included in the Linux OS media of certain versions. Obtain this package from the Linux OS media for version 6.8 or later, or from the distribution website. Regarding the package perl- XML-Simple, dependencies exist only in the following OSs: Red Hat Enterprise Linux 7.0 or later Oracle Linux 7.0 or later If the environment you are using already has the libstdc++ package installed, x86_64 (the 64-bit library) and i686 (the 32- bit compatibility library) packages might be different versions. Therefore, installation of libstdc++.i686 might fail with an error message such as the following: Protected multilib versions: libstdc++xx.xx.xx-xx.xx.el6.i686!= libstdc++-yy.yy.yyyy.yy.el6.x86_64 If this happens, update x86_64 (the 64-bit library), and then 44 Installation on a Linux host

45 Component name Yum/rpm dependencies Notes libyaml libgcc.x86_64 nss-softokn-freebl.x86_64 iproute.x86_64 ncurses openssh-clients nss or higher expat-devel xinetd sysstat zip bc retry the installation of libstdc+ +.i686: yum update libstdc++.x86_64 The package nss may not be included in the Linux OS media of certain versions. Obtain this package from the Linux OS media for version 6.8 or later, or from the distribution website. Regarding the packages perl- Digest-MD5 and perl-xml- Simple, dependencies exist only in the following OSs: Red Hat Enterprise Linux 7.0 or later Oracle Linux 7.0 or later The following example shows how to install the package by using the Linux OS media. Change the values that you need to specify during installation according to the environment you are using. Procedure 1. Mount the Linux OS media and obtain the yum/rpm dependency packages: mkdir /media/osimage mount /dev/cdrom /media/osimage 2. Configure the yum repository: touch /etc/yum.repos.d/osimage.repo echo [dvd]>>/etc/yum.repos.d/osimage.repo echo name=dvd>>/etc/yum.repos.d/osimage.repo echo baseurl=file:///media/osimage/>>/etc/yum.repos.d/ OSImage.repo echo gpgcheck=0>>/etc/yum.repos.d/osimage.repo echo enabled=1>>/etc/yum.repos.d/osimage.repo 3. Run the yum command to install the dependency packages: yum install package-to-be-installed Example: yum install java openjdk-devel sysstat zip 4. Unmount the Linux OS media: umount /media/osimage/ rm /etc/yum.repos.d/osimage.repo Installation on a Linux host 45

46 Installing Infrastructure Analytics Advisor server and Data Center Analytics server on a Linux host The method of installing Infrastructure Analytics Advisor server and Data Center Analytics server on a Linux host is described. Preparing for installation You can install the Infrastructure Analytics Advisor server and the Data Center Analytics server at a time by using the installer (analytics_install.sh). Alternatively, you can install only one of these two components. Table 9 Infrastructure Analytics Advisor server installation prerequisites (Linux) Requirements Review hardware and software requirements Host name resolution Description Review the Infrastructure Analytics Advisor server requirements. Make sure that you meet all the hardware and software requirements. The IP address must be resolved from the host name of the Infrastructure Analytics Advisor server. Check the hosts file or the domain name system (DNS) server configuration of the host on which the Infrastructure Analytics Advisor server is installed. Time zone settings Make sure that the console and clock properties are set to the same time zone. The time and time zones set for all of the following servers must be synchronized: Infrastructure Analytics Advisor server Data Center Analytics server Analytics probe server User permission License Installation destination directory The root permission is required. Obtain the Infrastructure Analytics Advisor server license from your HDS representative. During installation, when prompted to specify the installation directory for the Infrastructure Analytics Advisor server, observe the following rules: Specify a directory name of less than 94 bytes. The following characters can be used: A-Z a-z 0-9 / underscore (_) (space character not allowed) A path separator (/) cannot be specified at the end of a path. Table 10 Data Center Analytics server installation prerequisites (Linux) Prerequisites Review hardware and software requirements Description Review the Data Center Analytics server requirements. Make sure that your site meets all the hardware and software requirements. 46 Installation on a Linux host

47 Prerequisites Prepare an external hard drive as the installation source Time zone settings Description Prepare an external drive for installing the Data Center Analytics server on a Linux host. For details about disk space requirements, see the Data Center Analytics server requirements. Make sure that the console and clock properties are set to the same time zone. The time and time zones set for all of the following servers must be synchronized: Infrastructure Analytics Advisor server Data Center Analytics server Analytics probe server Do not change the time zone after installing Data Center Analytics server. Port requirements User permissions License Installation destination directory Make sure that the ports you specify are available for communication. The default port is The root permission is required. Obtain the Data Center Analytics server license from your HDS representative. Specify a directory name of less than 94 bytes for the installation destination directory. Related topics Infrastructure Analytics Advisor server requirements (Linux) on page 25 Data Center Analytics server requirements on page 26 Installation on page 47 Installation To install the Infrastructure Analytics Advisor server and Data Center Analytics server on a Linux host, run the installer and follow the prompts. Procedure 1. Stop the security monitoring software, antivirus software, and process monitoring software. 2. Mount the Infrastructure Analytics Advisor installation media and copy the directories and files in the ANALYTICS directory on the installation media to a directory on the Linux host: mkdir /media/hiaaimage mount /dev/cdrom /media/hiaaimage cp r /media/hiaaimage/analytics /root/analytics 3. Run the following command as the root user: cd /root/analytics sh./analytics_install.sh NEW Installation on a Linux host 47

48 A message is displayed, confirming that you want to install Data Center Analytics server and Infrastructure Analytics Advisor server. 4. Enter y, and then specify the components that you want to install. In the following execution example, both Data Center Analytics server and Infrastructure Analytics Advisor server are installed. Tip: The prompt displays the default value to be used when a user does not enter a value. To use the default value, press the Enter key only. Do you want to install the Data Center Analytics server? (y/n) [n]: y Do you want to install the Infrastructure Analytics Advisor server? (y/n) [n]: y [Confirmation] Installation Product (1) Data Center Analytics server (2) Infrastructure Analytics Advisor server Do you want to install the server listed above? (y/n) [n]: y 5. You are prompted for a drive and directory to install the Data Center Analytics server. ============================================================ Installation of the Data Center Analytics server ============================================================ [INFO] Installation of the Data Center Analytics server started. [Partition parameter] <System device information> NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT fd0 2:0 1 4K 0 disk sda 8:0 0 20G 0 disk sda1 8: M 0 part /boot sda2 8: G 0 part vg_testol67-lv_root (dm-0) 252: G 0 lvm / vg_testol67-lv_swap (dm-1) 252:1 0 2G 0 lvm [SWAP] sdb 8: G 0 disk sr0 11: G 0 rom Specify the device name in which to store application data. [sdb]: Specify the directory in which to store application data. 48 Installation on a Linux host

49 File permissions for all files in the top-level directory and below will be changed to 'megha:megha'. [/data]: 6. When prompted, enter y to configure the firewall settings. Specify the IP addresses of the Analytics probe servers. You can also accept the default value and configure the IP addresses later: [Firewall parameter ] Do you want to configure the firewall to accept connections from Analytics probe servers? (y/n) [y]: Specify the IP addresses of the Analytics probe servers, so that these IP addresses will be added in the configuration of iptables, and the connection from these servers can be accepted.(port 22/tcp) You can also use and change it later. [ ]: 7. (Optional) Configure the SSL settings: [Keytool parameter ] [INFO] This setting is for SSL configuration. What is the name of your organizational unit? [Unknown]: Your organizational unit What is the name of your organization? [Unknown]: Your organization What is the name of your City or Locality? [Unknown]: Your city or locality What is the name of your State or Province? [Unknown]: Your state or province What is the two-letter country code for this unit? [Unknown]: Two-letter country code for your unit 8. Verify the settings that you specified: [Confirmation] Installation directory : /data Device name : /dev/sdb Mount point : /data Port number : 8443 Firewall accept rule to be added : Protocol Source IP Destination IP Destination PORT TCP Required CPAN libraries : Module::Build YAML XML::Simple Log::Log4perl Distinguished Name for keytool : CN=Your Host Name, OU=Your organizational unit, O=Your organization, L=Your city or locality, ST=Your state or province, C=Two-letter country code for your unit Installation on a Linux host 49

50 9. When you are prompted with the following caution message, enter y to continue with the installation: ************************************************************ ************************************************************ ************************************************************ ** CAUTION ** * This installation will delete all the partitions on the disk. (/dev/sdb) * This installation will change iptables settings. (Listing above) * Installation of the required CPAN libraries may take more than 4 minutes. ************************************************************ ************************************************************ ************************************************************ Do you want to continue the installation? (y/n) [n]: y [INFO] Installing CPAN library [ 1/4] Module::Build [INFO] Installing CPAN library [ 2/4] YAML [INFO] Installing CPAN library [ 3/4] XML::Simple [INFO] Installing CPAN library [ 4/4] Log::Log4perl [INFO] Stopping crond service. [INFO] Crond is stopped. [INFO] Deploying files... [INFO] File deployment is complete. [INFO] Applying environmental settings... [INFO] Starting crond service. [INFO] Crond is running. [INFO] Starting the Data Center Analytics server service... [INFO] The Data Center Analytics server service started. [INFO] Environment settings have been applied. [INFO] Installation of the Data Center Analytics server finished successfully. 10. You are prompted for a directory in which to install Infrastructure Analytics Advisor server. ============================================================ Installation of the Infrastructure Analytics Advisor server ============================================================ [INFO] Installation of the Infrastructure Analytics Advisor server started. Specify the directory to store application data. [/opt/ hitachi]: 11. Install the Infrastructure Analytics Advisor server. [Firewall parameter ] Installation on a Linux host

51 The Infrastructure Analytics Advisor server sets port as the default port. This port can be changed after installation. If you change the port number, you must change the firewall setting. [Confirmation] Installation directory : /opt/hitachi Port number : Firewall accept rule to be added : Protocol Source IP Destination IP Destination PORT TCP Do you want to continue the installation? (y/n) [n]: y [INFO] Deploying files... [INFO] File deployment is complete. [INFO] Installation of the common component started. [INFO] Installation of the common component finished successfully. [INFO] Restarting the common component service. KAPM06439-I The HiRDB service has stopped. KAPM06438-I The HiRDB service has started. [INFO] The common component service restarted successfully. [INFO] Environment settings have been applied. [INFO] Installation of the Infrastructure Analytics Advisor server finished successfully. Next steps Perform the initial setup of Infrastructure Analytics Advisor server and Data Center Analytics server. Related topics Initial setup of Data Center Analytics server on page 62 Initial setup of Infrastructure Analytics Advisor server on page 66 Installing Analytics probe server on a Linux host Review the prerequisites before installing Analytics probe server. Preparing for installation Before you begin installation of Analytics probe server on a Linux host, review the following prerequisites. Installation on a Linux host 51

52 Prerequisites Review hardware and software requirements Install Data Center Analytics server Review RAID Agent installation requirements Port requirements User permissions Time zone settings Description Review the Analytics probe server requirements. Make sure that you meet all the hardware and software requirements. Make sure that you install the Data Center Analytics server before you install the Analytics probe server. The Data Center Analytics server's IP address is required for setting up the Analytics probe server. When you install the Analytics probe server, the RAID Agent is installed automatically. Review the RAID Agent requirements before you begin installation. Check the installation directory: The installation directory is fixed (/opt/jp1pc) and cannot be changed. Make sure that the directory is empty. Also, make sure that you do not include any symbolic links in the installation path. Check the work directory for installation: When you install an agent, a temporary work directory jp1pc_agt is created in the /opt or /opt/jp1pc directory. (This directory is automatically deleted after the installation is successful.) If an error occurs during installation, verify the directory exists and delete it manually. Check the attributes of the installation directory: If any attributes of the installation directory are different from the product-defined directory attributes, they are changed. Set up host name resolution: The IP address must be able to be resolved from the host name of the host on which RAID Agent is installed. Check the hosts file or the domain name system (DNS) server configuration of the host on which RAID Agent is installed. Specify fixed IP address: The RAID Agent cannot run on hosts that use DHCP to assign IP addresses. Specify a fixed IP address for Analytics probe server. Check the name of the host on which RAID Agent is installed: Infrastructure Analytics Advisor server can be used in a DNS environment but does not support FQDN. Therefore, you must exclude the domain name when you specify the host name. Setting the LANG environment variable*: Before setting up the RAID Agent, you must specify C for the LANG environment variable on the Analytics probe server host. Make sure that the ports you specify are available for communication. The default port is The default port for SSH is 22. The root permission is required. The times and time zones of the following servers must all be synchronized: Infrastructure Analytics Advisor server Data Center Analytics server Analytics probe server Do not change the time zone after installing Analytics probe server. 52 Installation on a Linux host

53 Prerequisites Description License Obtain the Analytics probe server license from your HDS representative. *: At startup, RAID Agent is subject to the system LANG environment variable. If the LC_ALL environment variable differs from the LANG environment variable, either unset LC_ALL or change its value to match the LANG value. Use the following example as a reference when setting the LANG value for RAID Agent. The last line is an example of coding that unsets the LC_ALL value. Example settings: ## Set Environment-variables PATH=/sbin:/bin:/usr/bin:/opt/jp1pc/bin SHLIB_PATH=/opt/hitachi/common/lib LD_LIBRARY_PATH=/opt/hitachi/common/lib LIBPATH=/opt/hitachi/common/lib HCCLIBCNF=/opt/jp1/hcclibcnf LANG=C export PATH SHLIB_PATH LD_LIBRARY_PATH LIBPATH HCCLIBCNF LANG unset LC_ALL Related topics Analytics probe server requirements on page 27 Installation on page 53 Installation Mount the installation media on the Linux host before installing and configuring the Analytics probe server. Procedure 1. Stop the security monitoring software, antivirus software, and process monitoring software. 2. Mount the Infrastructure Analytics Advisor installation media and copy the directories and files in the DCAPROBE directory on the installation media to a directory on the Linux host: mkdir /media/hiaaimage mount /dev/cdrom /media/hiaaimage cp -r /media/hiaaimage/dcaprobe /root/dcaprobe 3. Run the following commands: cd /root/dcaprobe/ sh./dcaprobe_install.sh NEW 4. Specify a directory to install the Analytics probe server: Installation on a Linux host 53

54 Tip: The prompt displays the default value to be used when a user does not enter a value. To use the default value, press the Enter key only. Specify the path of the directory in which to store application data. [/home]: 5. Specify Y to configure the firewall settings: Do you want to configure the firewall to accept connections from Analytics probe servers? (y/n) [y]: 6. (Optional) Configure the SSL settings: [Keytool parameter ] [INFO] This setting is for SSL configuration. What is the name of your organizational unit? [Unknown]: Your organizational unit What is the name of your organization? [Unknown]: Your organization What is the name of your City or Locality? [Unknown]: Your city or locality What is the name of your State or Province? [Unknown]: Your state or province What is the two-letter country code for this unit? [Unknown]: Two-letter country code for your unit 7. Verify the settings that you specified: The number of CPAN libraries to be installed varies depending on the environment. [Confirmation] Data directory (for the RAID Agent) : /home/ RAIDAgent Data directory (for the Analytics probe server) : /home Port number (for the Analytics probe server) : 8443,24221 Firewall accept rule to be added : Protocol Source IP Destination IP Destination PORT ALL ALL <RELATED,ESTABLISHED> TCP TCP ALL TCP ALL Required CPAN libraries : Module::Build YAML IO::Pty Date::Calc Net::OpenSSH DateTime DateTime::Format::Strptime Date::Gregorian Log::Log4perl Log::Dispatch::FileRotate Sys::RunAlone LWP::UserAgent LWP::Protocol::https Time::HiRes XML::Simple Distinguished Name for keytool : CN=Your Host Name, OU=Your organizational unit, O=Your organization, 54 Installation on a Linux host

55 L=Your city or locality, ST=Your state or province, C=Twoletter country code for your unit 8. When you are prompted with the following caution message, enter y to continue with the installation. Note: If the installation of the CPAN library Net::OpenSSH by the Analytics probe server installer displays the following message: root@localhost's password: 9. Confirm that the installation process resumes approximately 10 seconds after the message is displayed. ************************************************************ ************************************************************ ************************************************************ ** CAUTION ** * This installation will change iptables settings. (Listing above) * Installation of the required CPAN libraries may take more than 16 minutes. ************************************************************ ************************************************************ ************************************************************ Do you want to continue the installation? (y/n) [n]: y [INFO] Installing CPAN library [ 1/16] Module::Build [INFO] Installing CPAN library [ 2/16] YAML [INFO] Installing CPAN library [ 3/16] IO::Pty [INFO] Installing CPAN library [ 4/16] Date::Calc [INFO] Installing CPAN library [ 5/16] Net::OpenSSH [INFO] Installing CPAN library [ 6/16] DateTime [INFO] Installing CPAN library [ 7/16] DateTime::Format::Strptime [INFO] Installing CPAN library [ 8/16] Date::Gregorian [INFO] Installing CPAN library [ 9/16] Log::Log4perl [INFO] Installing CPAN library [10/16] Log::Dispatch::FileRotate [INFO] Installing CPAN library [11/16] Sys::RunAlone [INFO] Installing CPAN library [12/16] [INFO] Installing CPAN library [13/16] LWP::UserAgent [INFO] Installing CPAN library [14/16] LWP::Protocol::https [INFO] Installing CPAN library [15/16] Time::HiRes [INFO] Installing CPAN library [16/16] XML::Simple [INFO] Installation of the RAID Agent has started. [INFO] Applying environmental settings... [INFO] Stopping the RAID Agent service... [INFO] The RAID Agent service has stopped. [INFO] Environment settings have been applied. Installation on a Linux host 55

56 [INFO] Installation of the RAID Agent finished successfully. [INFO] Installation of the Analytics probe server has started. [INFO] Deploying files... [INFO] File deployment is complete. [INFO] Applying environmental settings... [INFO] Environment settings have been applied. [INFO] Starting the DCA service... [INFO] The DCA service started. [INFO] Installation of the Analytics probe server finished successfully. [INFO] Installation of the Analytics probe server finished successfully. Next steps Perform the initial setup of Analytics probe server. Related topics Initial setup of Analytics probe server on page Installation on a Linux host

57 5 Installation of Infrastructure Analytics Advisor server on a Windows host Use this installation method to install Infrastructure Analytics Advisor server on a Windows host. Preparing for installation Installation Installation of Infrastructure Analytics Advisor server on a Windows host 57

58 Preparing for installation Before you install an Infrastructure Analytics Advisor server, review the hardware, software, synchronize the time zone, and obtain the license. Prerequisites Review hardware and software requirements Time zone settings License Description Review the Infrastructure Analytics Advisor server requirements. Make sure that you meet all the hardware and software requirements. The times and time zones of the following servers must all be synchronized: Infrastructure Analytics Advisor server Data Center Analytics server Analytics probe server Obtain the Infrastructure Analytics Advisor server license from your HDS representative. Related topics Infrastructure Analytics Advisor server requirements (Windows) on page 25 Installation on page 58 Installation Start the wizard to install Infrastructure Analytics Advisor. Procedure 1. Log on to the host where Infrastructure Analytics Advisor server is to be installed as a user with the Administrator permission, and then stop the security monitoring software, antivirus software, and process monitoring software. 2. Run ANALYTICS.msi on the installation media to start installer. An installation wizard appears. 3. Go through the on-screen prompts and specify the required information to complete the installation. Note: You can specify only a fixed disk for the installation folder of Infrastructure Analytics Advisor server. You cannot install Infrastructure Analytics Advisor server on removable media, network drives, and UNC paths. 58 Installation of Infrastructure Analytics Advisor server on a Windows host

59 Next steps Perform the initial setup of Infrastructure Analytics Advisor server. Related topics Initial setup of Infrastructure Analytics Advisor server on page 66 Installation of Infrastructure Analytics Advisor server on a Windows host 59

60 60 Installation of Infrastructure Analytics Advisor server on a Windows host

61 6 Initial setup after installation After installing the Infrastructure Analytics Advisor components, continue with the setup of Data Center Analytics, the Analytics probe server, Infrastructure Analytics Advisor server, and the environment for Storage I/O controls feature, and Granular Data Collection. Initial setup of Data Center Analytics server Initial setup of Analytics probe server Initial setup of Infrastructure Analytics Advisor server Configuring initial settings for limiting the I/O activity of Hitachi storage resources Initial setup for enabling Granular Data Collection Adding a secondary Data Center Analytics server Initial setup after installation 61

62 Initial setup of Data Center Analytics server Open the URL of the Data Center Analytics server and follow the prompts. Before you begin Check the IP address of the Data Center Analytics server. Obtain the Data Center Analytics license from your HDS representative. Note: The Data Center Analytics server creates the following users for the supported OS: megha, meghadata, mars, and config. Do not change them. Procedure 1. Enter the Data Center Analytics server URL in your browser: The default port for https access is Read and accept the license agreement, and then click Next. 3. In the Upload License window, click Choose File to browse to the license file and click Open. 4. Click Submit to register the license. 5. In the Set Details For Existing admin User window, enter the password, select the locale, and then click Submit (The user name for the built-in administrator account is admin). Note: The current version of Data Center Analytics supports only the English locale. 6. In the Data Center Analytics server login window, enter the administrator user credentials and click Login. 7. In the Select Time zone window, select the appropriate time zone and click Next. The Data Center Analytics server home page is displayed. Note: Reports display data using the time zone of the Data Center Analytics server (not that of the storage systems). For example, if your server is located in the IST time zone, reports will use IST time regardless of where individual storage systems are located. 8. (Optional) Create an Infrastructure Analytics Advisor server account that belongs to the Administrator group on the Data Center Analytics server. For information about how to add accounts, see the Hitachi Data Center Analytics User Guide. If you use the built-in administrator account to 62 Initial setup after installation

63 access the Infrastructure Analytics Advisor server, this step is unnecessary. Note: Several accounts are created automatically in Data Center Analytics server when you configure Infrastructure Analytics Advisor server for connecting with the Data Center Analytics server. Do not change or delete the information of the following user accounts: HIAA_Server_Admin HIAA_REST_Admin HIAA_REST_Normal HIAA_GUI_Report Related topics Setting up a connection with Data Center Analytics server on page 67 Initial setup of Analytics probe server Open the URL of the Analytics probe server and follow the prompts. Before you begin Check the IP address of the Data Center Analytics server. Check the IP address of the Analytics probe server. Obtain the Data Center Analytics license from your HDS representative. Note: The Analytics probe server creates the following user accounts: megha, meghadata, mars, and config. Do not change them. Procedure 1. Open your browser and enter the Analytics probe server URL When you first launch the Analytics probe server UI, you see the license agreement details. Read, and then click Next. 3. In the Upload License window, click Choose File to browse to a license file and click Open. 4. Click Submit to add the license. 5. In the Create Administrator Account window, provide the following, and then click Submit: User name and password. First name, last name, and address of the user. Initial setup after installation 63

64 Locale: Only the U.S. English locale is currently supported. Group: Select Admin to create an administrator account. 6. In the Analytics probe login window, enter the administrator user credentials and click Login. 7. The Basic Information window displays the Customer Name (which cannot be changed). Provide the following contact information and click Next: Administrator Contact Name and Technical Contact Name and 8. In the Select Time zone window, set the same time zone for the Analytics probe server as that of the Infrastructure Analytics Advisor server, and then click Next. 9. In the Primary HDCA Server Information window, specify the following details: Protocol: FTP, FTPS, SFTP, or HTTPS. Host: Data Center Analytics server or FTP server IP address. If you are using FTP server as a primary server, then make sure that you configure downloader on the Data Center Analytics server to download the data from this intermediate FTP server. Port: Based on the selected protocol. User: User name for the host. For a Data Center Analytics server the user name is: meghadata Password: Password for the host. For a Data Center Analytics server the password is: meghadata123 Note: You cannot change the password of the FTP user account (meghadata). To enhance security for the FTP account, you can disable the login shell of the meghadata user. Advanced Settings: Passive: Connect to the FTP server in Passive mode. Proxy: Select to configure a proxy server. Real time server: By default the Real time server field uses the value that you entered in the Host field. If you are using FTP server, then make sure you type in the Data Center Analytics server IP address that is processing the data of the primary server. Note: The Analytics probe server must be reachable by Data Center Analytics server using the port Click Next. 64 Initial setup after installation

65 In addition to sending probe data to a single (local) Data Center Analytics server, you can configure a secondary, cloud-based Data Center Analytics server. The purpose is to host a copy of the probe data where it can be accessed outside of your internal network. You can add this secondary server from the Analytics probe server UI. Note: The secondary Data Center Analytics server does not support real-time collection; the data may be received at different times from the Analytics probe server. 11. In the Data Collection duration window, verify the license expiry date in your license, and then click Next. 12. From the list of probes, select the probe type and configure it to collect data from the monitoring target. (You must add at least one probe to complete the installation) To add additional probes, go to the Analytics probe server web UI home page and click Add Probe. The following are available: Hitachi Adaptable Modular Storage (AMS) probe Hitachi Enterprise Storage probe Hitachi NAS probe IBM XIV probe EMC VMAX probe EMC VNX Block probe EMC VNX File probe EMC XtremIO probe NetApp probe Pure Storage probe VMware probe Brocade Network Advisor probe Cisco DCNM probe Cisco SAN Switch probe Linux probe Related topics Adding a secondary Data Center Analytics server on page 88 Configuring the downloader on the Data Center Analytics server on page 89 Initial setup after installation 65

66 Initial setup of Infrastructure Analytics Advisor server Set up the Infrastructure Analytics Advisor server, change the system account password, connect to the Data Center Analytics server, and then configure the mail server. Logging on to Infrastructure Analytics Advisor server Register the license for Infrastructure Analytics Advisor server, and then use the built-in account to log on to Infrastructure Analytics Advisor server. Before you begin Confirm that initial setup of the Data Center Analytics server and the Analytics probe server is complete. Check the IP address or host name of the Infrastructure Analytics Advisor server. Check the IP address of the Data Center Analytics server. Obtain the Infrastructure Analytics Advisor server license from your HDS representative. Procedure 1. Add the Infrastructure Analytics Advisor server product URL to the list of exceptions in your browser's popup blocker. 2. Enter the URL for the Infrastructure Analytics Advisor server in your web browser: Analytics-Advisor-server:22015/Analytics/login.htm 3. In the logon window, click Licenses. a. Use either of the following methods: Enter the license key Specify the license file b. Click Save. The license is added in the list. 4. To log on to the Infrastructure Analytics Advisor server, use these credentials: User ID: system Password: manager (default) Result The logon is complete, and the Infrastructure Analytics Advisor server Dashboard displays. 66 Initial setup after installation

67 Related topics Configuring secure communications on page 159 Changing the system account password Change the default password for the system account. The system account is a built-in account that has the user management permission, and permissions for all Infrastructure Analytics Advisor server operations. Procedure 1. In the Administration tab, select User Management > Users and Permissions. 2. From the displayed dialog box, display Users, and then select System. 3. Click Change Password. Setting up a connection with Data Center Analytics server Set up a connection so that the data collected by the Data Center Analytics server can be analyzed by the Infrastructure Analytics Advisor server. Procedure 1. In the Administration tab, select System Settings > Data Center Analytics Server. 2. Click Edit Settings, and specify the Data Center Analytics server information. Note: Specify the built-in administrator account as the user account. If you want to use a different account, specify the account created during the initial setup of Data Center Analytics server. If you change the password of the specified user in the Data Center Analytics server, also change the same password in Password of the Edit Settings dialog box. 3. Click Check Connection to confirm that the server is connected properly. If you cannot access the Data Center Analytics server, verify the following: The certificate is correctly specified on the Infrastructure Analytics Advisor server. The certificate is not expired. 4. Click OK. Result The Data Center Analytics server is connected. Initial setup after installation 67

68 Related topics Initial setup of Data Center Analytics server on page 62 Configuring the mail server Configure the mail server and the address of the sender to notify the administrator of problems that occur in target resources and information related to Infrastructure Analytics Advisor server operations. Before you begin Make sure you have the Admin permission of Infrastructure Analytics Advisor. Procedure 1. In the Administration tab, select Notification Settings > Server. 2. Click Edit Settings to specify information about the mail server. 3. To verify mail server is configured correctly, click Send Test Mail. 4. Confirm that the test arrives, and then click Save Settings. Configuring initial settings for limiting the I/O activity of Hitachi storage resources Infrastructure Analytics Advisor enables storage administrators to prioritize I/O activity in a shared infrastructure. You can set the upper limit of IOPS processed by volumes during critical workload periods and optimize the performance of resources in a shared infrastructure. Setting up an environment for limiting the I/O activity of resources using Automation Director You can use the Storage I/O controls feature of Infrastructure Analytics Advisor to limit the I/O activity of resources. To use the feature, you must use the Server Priority Manager function provided by Hitachi storage systems. Configuration overview for I/O controls using Automation Director To configure Server Priority Manager, you must either set up an environment in advance by using the Configuration Manager REST API and Automation Director or use the script file created in advance instead of Automation Director. For details about each procedure, see the following manuals: Hitachi Command Suite Automation Director User Guide Hitachi Command Suite Configuration Manager REST API Reference Guide Hitachi Command Suite Automation Director Installation and Configuration Guide 68 Initial setup after installation

69 Hitachi Infrastructure Analytics Advisor User Guide I/O Control Configuration Workflow Before you begin Automation Director must be installed. For installation instructions, see the Hitachi Command Suite Automation Director Installation and Configuration Guide. The target storage systems must have the Server Priority Manager function enabled. Installing the Configuration Manager REST API The Configuration Manager REST API can be installed from the installation media for Infrastructure Analytics Advisor. The procedure is as follows: Procedure 1. Check the path of the installation destination of the Configuration Manager REST API. This information must be specified during installation. The Configuration Manager REST API will be installed in the ConfManager directory under the specified installation destination path. Default installation destination: /opt/hicommand If you change the installation destination from the default location, the new installation destination must meet conditions such as for the path Initial setup after installation 69

70 length and type of characters. For details, see the Hitachi Command Suite Configuration Manager REST API Reference Guide. 2. Copy the directories and the files in the CONFMANAGER directory on the installation media to the directory on the Linux host. 3. Use the sh command to run the installer (install.sh). For example: sh./install.sh 4. Following the on-screen prompt, specify the required information to finish installation. Downloading analytics service templates and register storage systems Before creating and initiating the services that communicate I/O control tasks between Infrastructure Analytics Advisor and Automation Director, you must download the service templates that enable I/O control and disable it, then register the target storage systems. Procedure 1. In Infrastructure Analytics Advisor, download the service templates. a. On the Administration tab, select System Settings > Automation Director Server. b. Click the link to download the service template. The name of the service template is AnalyticsServiceTemplate.zip. 2. Register the storage system information in the Configuration Manager REST API so that the Configuration Manager REST API can be used to configure the storage system. Run the following request. Request line: POST protocol://host-name:port-number/ ConfigurationManager/v1/objects/storages Example of the body of a request: { "svpip": " ", "serialnumber": , "model": "VSP G400", "issecure": true } Attribute Type Description svpip string (Required) IP address of the service processor that manages the storage system to be registered serialnumber int (Required) Serial number of the storage system to be registered 70 Initial setup after installation

71 Attribute Type Description model string (Required) Model number of the storage system to be registered. Specify one of the following values: VSP G200 VSP G400 VSP G600 VSP G800 VSP G1000 VSP G1500 VSP F400 VSP F600 VSP F800 VSP F1500 issecure boolean (Required) Settings for SSL communication between the Configuration Manager REST API and the storage system true: Enables SSL communication. false: Disables SSL communication. rmiport int (Optional) Port number to be used for RMI communications by the service processor that manages the storage system to be registered If this attribute is omitted, 1099 will be set. Another way to register the storage system information is to run a script. Script files are provided with the Analytics probe server: 1. Specify Configuration Manager REST API information in the following file: /opt/hitachi/analytics/sample/config.sh 2. Specify the storage system information in the following file, and then run the script:./operate_storage.sh register svpip serialnumber model userid password [issecure] For userid, specify an account that belongs to the Administrator user group (for VSP F series or VSP G series), or the account of a maintenance user (for VSP or HUS VM). 3. From the script execution result that is displayed, note the value of storagedeviceid. You need this value in the next step. Alternatively, you can check the execution result by running the following script:./operate_storage.sh list Note: If a VSP G1000 storage system is registered in the Configuration Manager REST API, and if SSL communication is enabled between the Configuration Manager REST API and the storage system, the storage system cannot be registered on Initial setup after installation 71

72 another instance of Configuration Manager REST API. For details about SSL communication settings of the Configuration Manager REST API, see the Hitachi Command Suite Configuration Manager REST API Reference Guide. Configuring I/O controls for Infrastructure Analytics Advisor with Automation Director Configuration tasks include registering your storage system on the Configuration Manager REST API and then setting up and initiating services on Automation Director. Procedure 1. Register the storage system in Automation Director. a. In the Administration tab, select Connection Settings > Web Service Connections. b. Click Add, and then specify the following information about the storage systems with Server Priority Manager: Category: Analytics (recommended) Name: Device number of the storage system IPAddress/HostName: IP address or host name of the host on which the Configuration Manager REST API is installed Protocol: http or https (protocol used by the Configuration Manager REST API) Port: Port number used by the Configuration Manager REST API User ID and Password: User account with permission to access the logical devices and ports used for I/O control. Note: When registering storage system information in Automation Director, specify a name different from that of other applications, such as RAID Agent. If you use the same name, I/O control tasks will fail. 2. Create an Automation Director user group to be used in Infrastructure Analytics Advisor. a. In the Administration tab, select Resources and Permissions > User Groups. b. Click Create, and then specify a name for the user group. Note: The best practice is to use the user group name "AnalyticsGroup". 3. Import the service templates in Automation Director. a. In the Service Templates tab, click Import. 72 Initial setup after installation

73 b. Click Browse, and then specify AnalyticsServiceTemplate.zip: This zip files contains two service templates: DeleteIoControlSettingsversion.st - This template disables an I/O control task. ModifyIoControlSettingsversion.st - This template enables or modifies an I/O control task. Tip: If you do not see the I/O control settings service templates, select Sort by Registered and the latest imported templates will appear with the New tag. c. Click OK. 4. Create a service group. a. In the Administration tab, select Resources and Permissions > Service Groups. b. Click Create, and then specify a name for the service group. Note: The best practice is to use the service group name "Analytics Service Group". 5. Use the service templates to create the services for Server Priority Manager: a. In the Administration tab, select Resources and Permissions > Service Groups. b. Select the service group you created. c. In the Services tab, click Create. d. Select the service templates, and then click Create Service. e. Specify the following information using the best practice names to create the service: Name of the service for updating Server Priority Manager settings: Modify IO Control Settings for Volume Name of the service for deleting Server Priority Manager settings: Delete IO Control Settings for Volume Status: Release Note: Do not modify the I/O control settings. These fields are autopopulated by the information entered on the Infrastructure Analytics Advisor user interface when you submit an I/O control task. f. Click Save and Close to close the window. 6. Assign the user group to the service group. a. In the Permissions tab, click Assign. b. Select the user group, and then click Add. Initial setup after installation 73

74 c. Select the Submit role, and then click OK. 7. Use the Automation Director user account for Infrastructure Analytics Advisor, assign the user account to the user group. a. In the Permissions tab, select a user group that has the Submit role. b. Click Assign, and then select the Automation Director user account that you want to use for Infrastructure Analytics Advisor. c. Click Add, and then click OK. 8. (Optional) Edit the config_user.properties file. If you want to use something other than the default value for the service group name, category name, or service name, specify, in the config_user.properties file, the name that you set in Automation Director. The location of the config_user.properties file is as follows: For Windows Infrastructure-Analytics-Advisor-server-installationdestination-folder\Analytics\conf For Linux Infrastructure-Analytics-Advisor-server-installationdestination-directory/Analytics/conf Specify the following keys and values: automation.parameter.servicegroupname: Service group name specified in Automation Director automation.parameter.productname: Category name specified in Automation Director automation.parameter.servicename.iocontrol.modify: Service name set in Automation Director as the name of the service for updating Server Priority Manager settings automation.parameter.servicename.iocontrol.delete: Service name set in Automation Director as the name of the service for deleting Server Priority Manager settings Result The environment setup for controlling storage resources is now complete. Next steps Set up a connection between Infrastructure Analytics Advisor and Automation Director. Setting up a connection with Automation Director Log on to Infrastructure Analytics Advisor to set up the connection with Automation Director. Before you begin Obtain the following information related to Automation Director: IP Address/Host Name 74 Initial setup after installation

75 User Name Password Protocol Port Procedure 1. In the Administration tab, select System Settings > Automation Director Server. 2. Click Edit Settings, and then provide the information for each field. 3. Click Check Connection to verify the connection with Automation Director. 4. Click OK. Configuring I/O control settings with user-defined scripts This example describes how to use Infrastructure Analytics Advisor and Configuration Manager REST API to configure the I/O control settings for the target storage resources with the user-defined scripts. Procedure 1. Create the script files. You must create two script files, one for create or modify operation and another for delete operation. 2. Specify the script file name in the built-in template file. 3. Submit an I/O control task from the Infrastructure Analytics Advisor Operations tab or from the Analyze Bottleneck > Analyze Shared Resources window. 4. Script execution is initiated by Infrastructure Analytics Advisor after you submit the I/O control task. 5. Check the status of the script execution on the Infrastructure Analytics Advisor Events tab. Related topics Prerequisites for setting I/O controls (using a script) on page 75 Creating the script files on page 76 Editing built-in command templates on page 79 Creating an I/O control task on page 80 Running the script files on page 81 Checking the status of the script execution on page 81 Prerequisites for setting I/O controls (using a script) You must have the Infrastructure Analytics Advisor User Interface login credentials with StorageOps permissions to configure the I/O control settings. Make sure the Configuration Manager REST API is installed. For installation instructions, see the Configuration Manager REST API Reference Guide. Initial setup after installation 75

76 Make sure the target storage systems are registered on the Configuration Manager REST API. Make sure the Server Priority Manager function is enabled for the target storage systems. You must have the operational service processor account with storage administrator permissions for the target storage systems. Related topics Configuring I/O control settings with user-defined scripts on page 75 Creating the script files Infrastructure Analytics Advisor server can run the user-defined script files for creating, updating and deleting storage I/O control settings. Procedure 1. Create the script files. You must create one script file for create or update operation and another for delete operation. You can specify any file name. 2. Save the script file anywhere on the Infrastructure Analytics Advisor server. Example of a create or update request You can set the upper limit of I/O activity for the volumes in a shared infrastructure. You can also update the existing I/O settings. While creating the scripts, you must determine the logical workflow for the successful completion of a task. Follow a logical sequence of tasks for creating or updating I/O control settings for the target storage resources. The script depends on the following parameters: The *.json file, which includes the I/O control parameters that you input from the UI. The *.json file is autocreated by the system after you submit the I/O control task using the Infrastructure Analytics Advisor UI. Storage device ID LDEV ID Host WWN The user-environment configuration details includes the following: SVP-account-user-name SVP-account-password Configuration-Manager-REST-API-host-name Configuration-Manager-REST-API-protocol Configuration-Manager-REST-API-access-port For example, when you run the script, it reads the *.json file to obtain the storage device ID based on which it determines the user-environment configuration details. 76 Initial setup after installation

77 The logical sequence of tasks to be executed by the script for creating or updating the I/O control settings is as follows: 1. Obtain the storage device ID and the user-environment configuration details. 2. Access the Configuration Manager REST API to obtain a list of storage resources enabled for I/O control settings. An example of the curl command used to communicate with the storage system for the current I/O control settings is as follows: curl --user SVP-account-user-name:SVP-account-password -H "Accept: application/json" -H "Contenttype:application/json" -X GET Configuration-Manager-REST-API-protocol://Configuration- Manager-REST-API-host-name(or IP address):configuration- Manager-REST-API-accessport/ConfigurationManager/v1/objects/ storages/storagedeviceid/io-control-ldev-wwns-iscsis/ The request returns a list of volumes enabled for I/O control settings. 3. Determine whether the request is to create or update by comparing the input I/O control settings and the existing I/O control settings. Identify the volumes without I/O control settings. Identify the volumes already configured with I/O control settings. 4. Access the Configuration Manager REST API to run the create request for the volumes without I/O control settings. An example of the curl command used to create the I/O control settings for the target storage resources is as follows: json={"ldevid":ldevid,"hostwwn":wwn,"upperlimitforiops":upper Limit} curl --user SVP-account-user-name:SVP-account-password -H "Accept:application/json" -H "Contenttype:application/json" - X POST -d $json "Configuration-Manager-REST-API-protocol:// Configuration-Manager-REST-API-host-name(or IP address):configuration-manager-rest-api-access-port/ ConfigurationManager/v1/objects/storages/storageDeviceID/ iocontrol-ldev-wwns-iscsis/" 5. Access the Configuration Manager REST API to run the update request for the volumes already configured with I/O control settings. An example of the curl command used to update the I/O control settings for the target storage resources is as follows: json={"upperlimitforiops":upperlimit} curl --user SVP-account-user-name:SVP-account-password -H "Accept:application/json" -H "Contenttype:application/json" - X PUT -d $json "Configuration-Manager-REST-API-protocol:// Configuration-Manager-REST-API-host-name(or IP address):configuration-manager-rest-api-access-port/ ConfigurationManager/v1/objects/storages/storageDeviceID/ iocontrol-ldev-wwns-iscsis/ldevid%2cwwn" Initial setup after installation 77

78 Note: The sample curl commands require you to provide the user credentials to access the resources in the protected zone. Apply security measures to protect the sensitive information. Example of a delete request You can delete the I/O control settings when the requirements change and when you no longer want to limit the I/O control activity of certain resources. While creating the scripts, you must determine the logical workflow for the successful completion of a task. Follow a logical sequence of tasks to delete the I/O control settings for the target storage resources. The script depends on the following parameters: The *.json file, which includes the I/O control parameters that you input from the UI. The *.json file is autocreated by the system after you submit the I/O control task using the Infrastructure Analytics Advisor UI. Storage device ID LDEV ID Host WWN The user-environment configuration details includes the following: SVP-account-user-name SVP-account-password Configuration-Manager-REST-API-host-name Configuration-Manager-REST-API-protocol Configuration-Manager-REST-API-access-port For example, when you run the script, it reads the *.json file to get the storage device ID based on which it determines the user-environment configuration details. The logical order of tasks to be executed by the script for deleting the I/O control settings is as follows: 1. Obtain the storage device ID and the user-environment configuration details. 2. Access the Configuration Manager REST API to obtain a list of storage resources enabled for I/O control settings. An example of the curl command used to communicate with the storage system for the current I/O control settings is as follows: curl --user SVP-account-user-name:SVP-account-password -H "Accept: application/json" -H "Contenttype:application/json" -X GET Configuration-Manager-REST-API-protocol://Configuration- Manager-REST-API-host-name(or IP address):configuration- 78 Initial setup after installation

79 Manager-REST-API-accessport/ConfigurationManager/v1/objects/ storages/storagedeviceid/io-control-ldev-wwns-iscsis/ The request returns a list of volumes enabled for I/O control settings. 3. Determine whether the target volumes exist and whether they are enabled for I/O control settings by initiating a comparison between the input I/O control settings and the existing I/O control settings. 4. Access the Configuration Manager REST API to delete the I/O control settings for the target volumes. An example of the curl command used to delete the I/O control settings for the target storage resources is as follows: curl --user SVP-account-user-name:SVP-account-password -H "Accept:application/json" -H "Contenttype:application/json" - X DELETE "Configuration-Manager-REST-API-protocol:// Configuration-Manager-REST-API-host-name(or IP address):configuration-manager-rest-api-access-port/ ConfigurationManager/v1/objects/storages/storageDeviceID/iocontrol-ldev-wwns-iscsis/ldevId%2Cwwn" Note: The sample curl commands require you to provide the SVP user credentials to access the storage resources. Apply security measures to protect the sensitive information. Related topics Configuring I/O control settings with user-defined scripts on page 75 Editing built-in command templates The built-in command template files contain details about the script files created for configuring I/O control settings. You must edit the built-in command templates to specify the script file path. Procedure 1. Edit the built-in command templates to specify the script file path. The built-in command templates are stored in the following location: Windows: <HIAA-server-installation-folder>\Analytics\conf\template \command\built-in Linux: /opt/hitachi/analytics/conf/template/command/built-in 2. For creating or updating the I/O control settings, edit the BuiltinTemplateIoControlModify.txt file. Initial setup after installation 79

80 An example of the BuiltinTemplateIoControlModify.txt is as follows: SE.template.name.string = Script to modify I/O control settings SE.cmd.template.timeOut.num = SE.cmd.template.cmdName.string = File-path-of-the-scriptfile 3. For deleting the I/O control settings, edit the BuiltinTemplateIoControlDelete.txt file. An example of the BuiltinTemplateIoControlDelete.txt is as follows: SE.template.name.string = Script to delete I/O control settings SE.cmd.template.timeOut.num = SE.cmd.template.cmdName.string = File-path-of-the-scriptfile where: SE.cmd.template.timeOut.num is the timeout period that specifies the system response after the command is executed. The default value is 18,000,000 milliseconds. You can specify a value ranging from 1 millisecond to 2,147,483,647 milliseconds. SE.cmd.template.cmdName.string specifies the command name. Specify the absolute path to the command. You can specify a value ranging from 0 to 255 bytes that do not include control characters. To specify \, type \\. Related topics Configuring I/O control settings with user-defined scripts on page 75 Creating an I/O control task You must submit an I/O control task using the Infrastructure Analytics Advisor UI. Before you begin You must be logged into the Infrastructure Analytics Advisor UI with StorageOps permissions. Make sure you have specified the name of script files that you want to run in the built-in command template files. Procedure 1. To launch the Set IO Control window, perform any of the following: From the Operations tab, search for the related volumes. Select the volumes, and then click Set IO Control. From the Analyze Bottleneck window, click the Analyze Shared Resources tab. In the Analyze Shared Resources window, select the target volumes, and click Set IO Control. 2. In the Set IO Control window, you can configure the I/O control settings: 80 Initial setup after installation

81 a. In Upper Limit Setting, select ON for creating or updating I/O control settings. Select OFF for deleting the I/O control settings. b. In Collective Settings, select the metric and enter the limit in Upper Limit for each volume. c. Enter a task name and description, and then click Next. A default task name based on the date and time is automatically assigned:yyyymmdd_hhmm_iocontrolsettings. 3. Review the information, and then click Submit. Related topics Configuring I/O control settings with user-defined scripts on page 75 Running the script files Infrastructure Analytics Advisor lets you configure the I/O control settings by executing the user-defined scripts. Procedure 1. After you submit the I/O control task, the system automatically creates a *.json file with the input I/O control parameters. Sample file format of the *.json file { "storagedeviceid":" ", "IOControlParameter": [{ "ldevid":101, "hostwwn":" cceccc9", "upperlimitforiops":50}, { "ldevid":102, "hostwwn":" cceccc0", "upperlimitforiops":400 }] } 2. The system then inputs the following parameters to the script files: Infrastructure Analytics Advisor user name You can use this information to track the users running the script files. File path of the *.json file 3. The scripts read the *.json file and interfaces with the Configuration Manager REST API to configure the I/O control settings for the target storage resources. Related topics Configuring I/O control settings with user-defined scripts on page 75 Checking the status of the script execution You can verify whether the scripts were successfully executed. The script execution task is logged in as an information event on the Events tab. Initial setup after installation 81

82 Procedure 1. From the Infrastructure Analytics Advisor home page, click the Events tab. 2. Click All Events or System Events tab to track the status of the script execution. The name of the script file is displayed as the command action name. Note: You can only track the status of the script execution on the Events tab. The I/O control task status cannot be viewed under History. Related topics Configuring I/O control settings with user-defined scripts on page 75 Initial setup for enabling Granular Data Collection If you enable Granular Data Collection from Infrastructure Analytics Advisor, the RAID Agent commands are run remotely, and performance data (in units of seconds) for the monitored storage systems is output in CSV format. You can use this data for further analysis. To enable Granular Data Collection perform the following initial setup: Configure SSH on both the Infrastructure Analytics Advisor server and the RAID Agent host. Register the storage systems to be monitored by using Granular Data Collection on the Infrastructure Analytics Advisor server. You must also specify the initial settings when using Tuning Manager - Agent for RAID to collect data from the monitored storage systems. Prerequisites for using Granular Data Collection If you want to use Granular Data Collection, the following conditions must be met: The Infrastructure Analytics Advisor server is running a Linux OS. RAID Agent or Tuning Manager - Agent for RAID is running on a Linux OS that is supported by the Infrastructure Analytics Advisor server. For each storage system to be monitored, the storage system is one of the following models: VSP VSP F series VSP G series HUS VM 82 Initial setup after installation

83 Related topics Configuring SSH on page 83 Registering storage systems to be monitored by Granular Data Collection on page 86 Configuring SSH To run a RAID Agent command remotely from Infrastructure Analytics Advisor server, configure SSH. You must also configure the SSH settings if you want to use Tuning Manager - Agent for RAID to collect data from the monitored storage systems. To enable SSH, specify the following settings: 1. Create keys on the Infrastructure Analytics Advisor server. 2. Register the public key for the RAID Agent host and configure authentication using public key cryptography. 3. Verify the connection. Creating keys on the Infrastructure Analytics Advisor server Create the public and private keys used for SSH on the Infrastructure Analytics Advisor server. You can use both the RSA and DSA cryptography key types. Before you begin You must have the root permission of the OS to perform this operation. Procedure 1. Run the ssh-keygen command as follows: For RSA keys: ssh-keygen -t rsa For DSA keys: ssh-keygen -t dsa 2. Specify the full pathname of the file where the private key will be stored. The default setting is ~/.ssh/id_rsa. 3. Press Enter twice. When you are prompted to enter the password for the private key, press Enter. When you are prompted again, press Enter again. An example of running the ssh-keygen -t rsa command follows: [root@host]$ ssh-keygen -t rsa Generating public/private rsa key pair. Enter file in which to save the key (/home/ssh-user/.ssh/ id_rsa): Enter passphrase (empty for no passphrase): Initial setup after installation 83

84 Enter same passphrase again: Your identification has been saved in /home/ssh-user/.ssh/ id_rsa. Your public key has been saved in /home/ssh-user/.ssh/ id_rsa.pub. The key fingerprint is: ax:xx:xx:xx:xx:bx:xx:xc:xx:xx:xx:xd:xd:xa:ed:xx 4. Run the chmod command to specify 600 as the attribute of the private key file. chmod 600 id_rsa Be sure to protect private keys. Result The private key and public key for authentication are created. Next steps Configure the public key authentication. Configuring the public key authentication Configure the public key authentication using public key cryptography. Before you begin You must have the root permission to perform this procedure. Procedure 1. Navigate to the.ssh directory. Specify 700 as the attribute of the directory. Note: If there is no.ssh directory, create one. 2. Run the scp command to copy the public key file to the RAID Agent host. The public key is copied to the.ssh directory. 3. Run the cat command to add the content of the public key file to the authentication key file. 4. Delete the copied public key file. 5. Run the chmod command to specify 600 as the attribute of the authentication key file. An example of running the scp command, the cat command, and the chmod command follows. In this example, the host name of the Infrastructure Analytics Advisor server where keys are created is "HIAAHost", and the host name of the RAID Agent host is "AgentHost". ]$ cd.ssh 84 Initial setup after installation

85 scp password: Enter a password here. id_rsa.pub 100% KB/s 00:00 [root@agenthost.ssh]$ cat id_rsa.pub >> authorized_keys [root@agenthost.ssh]$ rm id_rsa.pub [root@agenthost.ssh]$ chmod 600 authorized_keys 6. Set the authentication key file as the value of AuthorizedKeysFile in /etc/ssh/sshd_config. Note: By default, ~/.ssh/authorized_keys or.ssh/ authorized_keys is set as the value of AuthorizedKeysFile. If you have changed the path of the authentication key file, revise the value of AuthorizedKeysFile. 7. Specify yes for the value of PubkeyAuthentication in /etc/ssh/ sshd_config. 8. Specify yes for the value of PermitRootLogin in /etc/ssh/sshd_config. 9. Restart the sshd. Note: For details about the items to specify in sshd_config and how to specify settings, see the documentation for the SSH server that you plan to use. Result The public key is registered to the RAID Agent host, and the authentication is configured. Next steps Verify the SSH connection. Verifying SSH connections Verify whether an SSH connection can be established between the Infrastructure Analytics Advisor server and the RAID Agent host. Before you begin You must have the root permission of the OS to perform this operation. Procedure 1. Use the created private key to run the ssh command for the RAID Agent host. If a connection is successfully established without any prompt for an identity, SSH configuration is complete. If an error occurs or you are Initial setup after installation 85

86 prompted to enter a password and a passphrase, check whether the settings are configured as described. Registering storage systems to be monitored by Granular Data Collection Use a definition file to register the storage systems to be monitored when performance information (in seconds) is collected by using the Granular Data Collection feature in Infrastructure Analytics Advisor. As with RAID Agent, you also must use a definition file to register target storage systems if you use Tuning Manager - Agent for RAID to collect information from the monitored storage systems. Definition file storage_agent_map.txt Storage location Infrastructure-Analytics-Advisor-server-installation-destinationdirectory/Analytics/bin/command/granular Definition items Specify the following items by using commas to separate them. Setting item Description Required/Optional Model name of the storage system Serial number of the storage system IP address of the RAID Agent host Port number of the RAID Agent host Instance name for collecting performance information (in seconds) Use of a proxy server Model name of the storage system Serial number of the storage system IP address of the RAID Agent host Port number of the RAID Agent host If you fail to provide this information, is used as the default port number. The name of instance that you want collect performance information (in seconds) If you fail to provide this information, RAID Agent searches for the target instance by comparing the model name and serial number specified in the definition file to the information that RAID Agent holds. Whether to use a proxy server for communication between the Required Required Required Optional Optional Optional 86 Initial setup after installation

87 Setting item Description Required/Optional Infrastructure Analytics Advisor server and the RAID Agent host. If a proxy server is available, specify one of the following values: noproxy: Specify this if the server and the host communicate directly with each other without using a proxy server. proxy: Specify this if you use a proxy server. If a proxy server is not available, omit this item. URL of the proxy server Authentication information for the proxy server The URL of the proxy server. If you use a proxy server, you must specify a value for this item. Authentication information for the proxy server. If you use a proxy server that requires user authentication, specify the authentication information in the following format: user-name:password Optional Optional Definition example In the definition file example below, the following three storage systems are registered to be monitored once per second. VSP F1500 VSP G1000 HUS VM Table 11 Details about the storage systems to be monitored Storage system VSP F1500 VSP G1000 HUS VM Model name of the storage system Serial number of the storage system IP address of the RAID Agent host Port number of the RAID Agent host VSP F1500 VSP G1000 HUS VM Not set Not set Initial setup after installation 87

88 Storage system VSP F1500 VSP G1000 HUS VM Instance name for collecting performance information (in seconds) Not set INSTANCE1 INSTANCE2 Use of a proxy server Not set Not set Not set URL of the proxy server Authentication information for the proxy server Not set Not set Not set Not set Not set Not set Definition file example VSP F1500,123456, VSP G1000,7890, ,24221,INSTANCE1 HUS VM,10000, ,,INSTANCE2 Adding a secondary Data Center Analytics server In addition to sending Analytics probe server data to a single (local) Data Center Analytics server, you can configure a secondary, cloud-based Data Center Analytics server. The purpose is to host a copy of the probe data where it can be accessed outside of your internal network. Note: The secondary Data Center Analytics server does not support real-time data; the data may be received at different times from the Analytics probe server. The secondary Data Center Analytics server hosts an independent, nonsynchronous copy of the probe data and does not constitute a failover configuration. Furthermore, the secondary Data Center Analytics server does not include primary Data Center Analytics server configuration data, including: Alert definitions Custom reports Custom trees User logins and profiles You can use the Data Center Analytics server backup and restore feature to save or copy these settings. Procedure 1. On the Analytics probe server home page, click Reconfigure. 88 Initial setup after installation

89 2. Go to HDCA Server tab and click Add HDCA Server. 3. In the Secondary HDCA Server Details window, specify the following details: Protocol: FTP, FTPS, SFTP, or HTTPS. Host: Data Center Analytics server or FTP server IP address. If you are using FTP server as a secondary server, then make sure that you configure downloader on the Data Center Analytics server to download the data from this intermediate FTP server. Port: Based on the selected protocol. User: User name for the host. For a Data Center Analytics server the user name is: meghadata Password: Password for the host. For a Data Center Analytics server the password is: meghadata123 Note: You cannot change the password of the FTP user account (meghadata). To enhance security for the FTP account, you can disable the login shell of the meghadata user. Advanced Settings: Proxy: Select to configure a proxy server. 4. Click Save. Related topics Initial setup of Analytics probe server on page 63 Backing up the settings information and database of Data Center Analytics server on page 212 Restoring the settings information and database of Data Center Analytics server on page 221 Configuring the downloader on the Data Center Analytics server When the Analytics probe server sends the data to an intermediate FTP server instead of a Data Center Analytics server, then the Data Center Analytics server needs to know details of the FTP server to download the data. Procedure 1. Log on to Data Center Analytics server using an SSH client (like Putty). 2. Stop the crond service using the command: service crond stop 3. Stop the megha service using the command: /usr/local/megha/bin/megha-jetty.sh stop Initial setup after installation 89

90 4. Verify the stopped status of the megha service: /usr/local/megha/bin/megha-jetty.sh status 5. Go to cd /usr/local/megha/misc directory and create a file for the downloader. The file format is: probedatadownloadconfig_ftp server_username.properties 6. Add the following entries in the file and provide the appropriate input. The file name and content are case sensitive. applianceid.list= ftp.password= ftp.port= ftp.server= ftp.type= ftp.username= For example: applianceid.list=1c5fbdd9-8ed3-43fe e9cba6d103c6,39cfcb01-11b2-46b4-8fce-b4d84ea5acda ftp.password=abc123 ftp.port=22 ftp.server= ftp.type=sftp ftp.username=abc 7. Change ownership to megha using the command: chown megha:megha property file name 8. Start the megha service using the command: /usr/local/megha/bin/megha-jetty.sh start 9. Start the crond service using the command:. service crond start Related topics Adding a secondary Data Center Analytics server on page Initial setup after installation

91 7 Adding probes to Analytics probe server Start collecting information about your system resources by adding probes to the Analytics probe server. You can set up the Hitachi Enterprise Storage probe by either using the RAID Agent bundled with Infrastructure Analytics Advisor or by using Tuning Manager - Agent for RAID. Choose the appropriate setup procedure for your environment. Setting up the Hitachi Enterprise Storage probe (when using RAID Agent) Setting up the Hitachi Enterprise Storage probe (when using Tuning Manager - Agent for RAID) Adding Hitachi Adaptable Modular Storage (AMS) probe Adding Hitachi NAS probe Adding IBM XIV probe Adding EMC VNX File probe Adding EMC VNX Block probe Adding the EMC XtremIO probe Adding EMC VMAX probe Adding Netapp probe Adding the Pure Storage probe Adding VMware probe Adding probes to Analytics probe server 91

92 Adding Brocade Network Advisor probe Adding Cisco DCNM probe Adding Cisco SAN Switch probe Adding Linux probe Initial setup after adding a probe 92 Adding probes to Analytics probe server

93 Setting up the Hitachi Enterprise Storage probe (when using RAID Agent) The Hitachi Enterprise Storage probe collects data from the monitored Hitachi Enterprise storage systems using RAID Agent, which is bundled with Infrastructure Analytics Advisor. Perform this procedure to use RAID Agent. Verify the connection between host and monitoring targets (when using RAID Agent) To monitor VSP, VSP F series, VSP G series, or HUS VM by using RAID Agent, use the following workflow to add the Hitachi Enterprise Storage probe. Operation workflow for adding Hitachi Enterprise Storage probe (when using RAID Agent) The following figure contains the workflow for adding Hitachi Enterprise Storage probes when you are using RAID Agent: Configuring Analytics probe server Confirm that RAID Agent and the Analytics probe server are installed on the same host. RAID Agent is installed when the Analytics probe server is installed. If you used the installer to install Analytics probe server, confirm that RAID Manager Library is installed on the RAID Agent host. In an environment that was created by deploying the OVA file for Analytics probe server, the RAID Manager Library is already installed. Adding probes to Analytics probe server 93

94 Configuring monitoring targets (storage systems) On the storage system, verify that a Storage Navigator user account was created. One user account is required for each RAID Agent environment. Confirm that the following roles are assigned to the user account: User account role needed for Performance Monitor settings: Storage administrator (performance management) User account roles needed to set up an instance environment: Assign any of the following roles to the user account: Storage administrator (viewing) Storage administrator (initial setup) Storage administrator (system resource management) Storage administrator (provisioning) Storage administrator (performance management) Storage administrator (local backup management) Storage administrator (remote backup management) For details about how to create user accounts in Storage Navigator, see the online help for your storage system. Confirm that the following settings are set for the instance of Performance Monitor for the storage system. Setting Monitor switch Monitoring-target CUs Monitoring-target WWNs Sampling interval Description Enable the monitoring switch setting Set the logical devices (on a CU basis) from which you want to collect performance data. This setting is not required if you use HUS VM. Set the performance data collection-target WWNs. Set the interval to short range. Verify that one of the logical units is assigned to a command device. Command devices must be defined as RAW devices. RAW devices must comply with the following rules: Command devices for the ZFS file system cannot be used. Do not create file systems in the logical devices specified as the command devices. Do not mount file systems to the logical devices specified as the command devices. For details about how to specify command devices, see the documents for the storage system you are using. Tip: In a Linux host environment, rescanning a disk device might change a device file of the form /dev/sd. To prevent this, use the WWID based form of the device file name (/dev/disk/by-id/scci hexadecimal-wwid). To specify the WWID based file name: 94 Adding probes to Analytics probe server

95 1. Use the jpctdlistraid command to display the /dev/sd form of the device file name: /opt/jp1pc/tools/jpctdlistraid 2. Use the ls command to search for the symbolic links managed in the /dev/disk/by-id directory for the WWID device file name mapped to the corresponding /dev/sd file name. For example: ls -la /dev/disk/by-id/* grep sdc 3. Use the output as the Command Device File Name. Connecting the RAID Agent host and the storage system Verify that the RAID Agent host and the storage system are connected by LAN, and are connected with both of the following methods: Fibre Channel, Fibre Channel over Ethernet (FCoE), or iscsi TCP/IP connection Some functions cannot be run while performance data is being collected over a TCP/IP connection. Before using a function for which the problem occurs, run the htmsrv stop command (/opt/jp1pc/htnm/bin/htmsrv stop -all) to temporarily stop the RAID Agent instance. The following are examples of functions that cannot be run while performance data is being collected over a TCP/IP connection: Data migration in Device Manager Displaying the following Storage Navigator: Server Priority Manager window Volume Migration window Usage Monitor window of True Copy (for HUS VM and Virtual Storage Platform) Usage Monitor window of Universal Replicator (for HUS VM and Virtual Storage Platform) Using the export tools described in the Performance Monitor manuals Related topics Creating an instance environment (when using RAID Agent) on page 95 Creating an instance environment (when using RAID Agent) Hitachi Enterprise Storage probe collects data by using a TCP/IP connection, or using the command device of VSP, VSP F series, VSP G series, or HUS VM. To collect data, you must create an instance environment of RAID Agent on the Analytics probe server host. Adding probes to Analytics probe server 95

96 Procedure 1. On the Analytics probe server, run the jpcinssetup command with the service key and instance name specified. Instance names must be no longer than 32 bytes and only half-width alphanumeric characters (A-Z, a-z, 0-9) are allowed. For example, to create an instance environment for the instance named for RAID Agent, run the following command: /opt/jp1pc/tools/jpcinssetup agtd -inst Set up the instance information for the storage system you will monitor. To use the default value (or no value), just press Enter. The following table lists the instance information to specify. Item Description Storage Model Always specify 2. Method for collecting Always specify 3. Command Device File Name Specify the device file name of the command device to be output by using the /opt/jp1pc/tools/ jpctdlistraid command. RAID Agent uses this command device to collect information about the storage system. The /dev/sd* form of the device file name might be changed by rescanning the disk device. The best practice is to use the WWID based form of the device file name. See the Verify the connection between host and monitoring targets (when using RAID Agent) for details about assigning a WWID based device file name. Mainframe Volume Monitoring * Specify Y to monitor a logical device for which the emulation type used for a mainframe is set. For HUS VM, mainframe emulation is not supported. Mainframe volumes are excluded from monitoring when an HUS VM is monitored. If no value is entered, the default value Y is set. If you enter a value other than Y, y, N, or n, the system prompts you to enter a value again. Unassigned Open Volume Monitoring * Specify Y to monitor a logical device or an parity group for which an open system emulation type has been set and that has not been mapped to a port. If no value is entered, the default value Y is set. If you enter a value other than Y, y, N, or n, the system prompts you to enter a value again. 96 Adding probes to Analytics probe server

97 Item Storage IP Address or Host Name Storage User ID Storage Password Java VM Heap Memory Details of storage model SVP Port No Description Specify the IP address or host name of the storage system to which the command device specified for Command Device File Name belongs. Specify the user ID of the user account that was created to monitor the target storage system. Specify the password of the user account that was created to monitor the target storage system. Specify the amount of memory available in Java VM. Specify the largest value that does not exceed the physical memory of the RAID Agent host. The default is 1. 1 = 0.5 GB 2 = 1.0 GB 3 = 2.0 GB 4 = 4.0 GB 5 = 8.0 GB Specify the storage type. 11 = Virtual Storage Platform 12 = VSP G1000, G1500, VSP F = HUS VM 22 = VSP Gx00 models or VSP Fx00 models Specify the port number if Detailed Storage Model is set to 22 (VSP Gx00 models or VSP Fx00 models). You can specify a value from 0 to The default value is This value is the same as the initial value for the RMIIFRegist port number of the storage system. To change the port number of the storage system, see the part of the storage system manual that explains how to change or initialize the port number to be used with the SVP. Serial No SVP HTTPS Port No Specify the serial number of the storage system if Detailed Storage Model is set to 22 (VSP Gx00 models or VSP Fx00 models). You can specify a value from to If 22 (VSP Gx00 models or VSP Fx00 models) is specified for Details of storage model, specify the port number that is used for connection via the HTTPS protocol, from a host on which RAID Agent is installed, to the SVP. You can specify a value from 0 to The default value is 443. This value is the same as the initial value for the MAPPWebServerHttps port number of the storage system. To change the port number of the storage system, see the part of the storage system manual that explains how to change or initialize the port number to be used with the SVP. *: Depending on the microcode version of the storage system, you might not be able to use the Mainframe Volume Monitoring or Unassigned Open Volume Monitoring function although you have enabled the setting (even if enabled). Adding probes to Analytics probe server 97

98 3. When configuring multiple instances, repeat steps 1 and 2 for each instance. 4. Make sure that RAID Manager LIB is installed. 5. Before you start operation in an instance environment, run the jpctdchkinst command to verify the instance settings. The command references the set instance information. (This command checks whether the settings allow information to be collected from the storage system monitored by RAID Agent.) /opt/jp1pc/tools/jpctdchkinst inst instance-name 6. Run the following command to start the RAID Agent instance services. /opt/jp1pc/htnm/bin/htmsrv start -all Next steps Add the Hitachi Enterprise Storage probe from the Analytics probe server home page. Related topics Verify the connection between host and monitoring targets (when using RAID Agent) on page 93 Adding Hitachi Enterprise Storage probe on page 98 Starting the RAID Agent services on page 191 Adding Hitachi Enterprise Storage probe The Hitachi Enterprise Storage probe collects data from VSP G1000, VSP G1500, VSP F1500, VSP Gx00 models, VSP Fx00 models, Virtual Storage Platform, and HUS VM storage systems. This procedure presumes you are using the RAID Agent bundled with Infrastructure Analytics Advisor server. The procedure is the same for using Tuning Manager - Agent for RAID. Note: When you add the Hitachi Enterprise Storage probe, the following message might be displayed: Some required opcodes are turned off by default on RAID Agent. Ensure that these are enabled to collect the related metrics. Before proceeding further, refer to product user documentation. Ignore this message as this setting is automatically enabled on RAID Agent in Hitachi Infrastructure Analytics Advisor. Procedure 1. On the Analytics probe server home page, click Add Probe. 2. In the Add Probe window, from the Probes list, select Hitachi Enterprise Storage. 98 Adding probes to Analytics probe server

99 3. In the Provide RAID Agent Details section, provide the following details, and then click Next: Probe Name: The probe name must contain a minimum of four alphanumeric characters. Example: HESP The probe name must be unique in the Data Center Analytics deployment. The probe name cannot include any special characters other than hyphen and underscore. Connection Type: Choose HTTP. Note: HTTPS is not supported. RAID Agent IP Address: IP address of the machine on which the RAID Agent is installed. RAID Agent Host name: Host name of the machine on which the RAID Agent is installed. The host name must match the host name (case-sensitive). Specify the host name that is returned when you run the uname -n command on the RAID Agent server. Do not use localhost. RAID Agent Port: Port number used by the RAID Agent on the RAID Agent host. The default port number is: HTTP Storage System Serial number: The serial number of the storage system that is configured on the RAID Agent. Storage System Instance: Storage instance name (alias) that is used to add the storage system to the RAID Agent. Enable real time data collection: Select the check box to collect real-time data that can be used for alerts, reports, and the REST API. Note: Enabling the real-time data collection increases the load on the Data Center Analytics server CPU and memory. To disable the real-time data collection, clear the Enable real time data collection check box. 4. In the Configure RAID Agent Collection Interval window, set PLC (Poll Configuration) to 60, and then click Next. Note: Do not change any other default values in this window. 5. In the Provide Hitachi Device Manager details window, select the appropriate option for collecting configuration metrics from Hitachi Device Manager. Select No to skip this step. If you select No, then the Provide Hitachi Device Manager details section is unavailable. Click Next, Adding probes to Analytics probe server 99

100 and a message appears, stating that the Hitachi Enterprise Storage probe is successfully added. Select Yes to enable the Provide Hitachi Device Manager details. If the Provide Hitachi Device Manager details option is enabled, type the following details, and then click Next: Connection Type: Choose HTTP or HTTPS. IP Address: IP address of the Hitachi Device Manager (HDvM) server. Port: Port number of the Hitachi Device Manager server. The default port numbers are: 2001-HTTP 2443-HTTPS Username/Password: User name and password of the Hitachi Device Manager. The user must be added in the ViewGroup user group of Hitachi Device Manager. 6. In the Validation window, Click Next, and then click OK. 7. In the Status window, in Action, click Start to start collecting data. 8. If you try to set up the Hitachi Enterprise Storage probe immediately after setting up an instance in the RAID Agent, the setup task fail with the following alert: 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 try again. You might have to wait approximately one hour before you can add the Hitachi Enterprise Storage probe. Related topics Initial setup after adding a probe on page 128 Deleting an instance environment (when using RAID Agent) To delete multiple instance environments, repeat the following procedure for each instance environment. Procedure 1. Find the instance name of RAID Agent using this command: /opt/jp1pc/tools/jpcinslist agtd For example, if the instance name is 35053, the command displays Adding probes to Analytics probe server

101 2. Run the following command to stop any active RAID Agent services in the instance environment. /opt/jp1pc/htnm/bin/htmsrv stop -all 3. Delete the instance environment using this command: /opt/jp1pc/tools/jpcinsunsetup agtd -inst instance-name The following example shows how to delete the instance environment 35053: /opt/jp1pc/tools/jpcinsunsetup agtd -inst Result If the command is successful, the directories created during instance environment setup are deleted. If a service with the specified instance name is active, a message appears asking whether the service is to be stopped. If this message appears, stop the service of the applicable instance. Related topics Stopping the RAID Agent services on page 192 Setting up the Hitachi Enterprise Storage probe (when using Tuning Manager - Agent for RAID) The Hitachi Enterprise Storage probe collects data from the monitored Hitachi Enterprise storage systems using Tuning Manager - Agent for RAID. Perform this procedure to use Tuning Manager - Agent for RAID. Requirements for adding the Hitachi Enterprise Storage probe (when using Tuning Manager - Agent for RAID) To monitor VSP, VSP F series, VSP G series, or HUS VM by using Tuning Manager - Agent for RAID, you must perform the following operations before adding the Hitachi Enterprise Storage probe. Adding probes to Analytics probe server 101

102 Example system configuration for Infrastructure Analytics Advisor (when using Tuning Manager - Agent for RAID) Operation workflow for adding Hitachi Enterprise Storage probe (when using Tuning Manager - Agent for RAID) The following figure contains the workflow for adding Hitachi Enterprise Storage probes when you use Tuning Manager - Agent for RAID. Prerequisites To use Tuning Manager - Agent for RAID, make sure that all of the following conditions are met: Version of Tuning Manager - Agent for RAID: Version or later. 102 Adding probes to Analytics probe server

103 Performance database for Tuning Manager - Agent for RAID: Hybrid Store. If you are using a Store database, switch to Hybrid Store. Value specified for Method for collecting (the connection method to be used when collecting performance data) in the Tuning Manager - Agent for RAID instance information: Verify that 3 (Collect from both command devices and TCP/IP) is selected. If 3 is not selected, update the instance environment. Disk capacity of Tuning Manager - Agent for RAID: There is sufficient space for the additional records that will be collected for Infrastructure Analytics Advisor analysis. Related topics Values used for estimating disk space when using Tuning Manager - Agent for RAID on page 107 Changing data to be collected by Tuning Manager - Agent for RAID To enable Tuning Manager - Agent for RAID to collect the following additional records for use in Infrastructure Analytics Advisor, you must modify the existing data collection settings (Log property settings) in Tuning Manager - Agent for RAID. PD_HGC PD_HHGC PD_LDCC PD_LDD PD_LHGC PD_LWPC PD_MPBC PD_PWPC PD_RGD Procedure 1. Log on to the Tuning Manager software as a user with administrator permissions. 2. Start Performance Reporter. 3. In the main window of Performance Reporter, in the Navigation frame, select the Services tab. This tab is displayed only for users with administrator permissions. 4. In the main window of Performance Reporter, in the Navigation frame, select System > Machines > folder-representing-tuning-manager- Agent-for-RAID-installation-host > Agent Collector Service. 5. In the main window of Performance Reporter, in the method pane, select Properties, and then Detail Records. A list of records is displayed. 6. Select the record for which you need to change the settings, and then change the Log property value to Yes. Adding probes to Analytics probe server 103

104 Note: To use Tuning Manager - Agent for RAID after upgrading it from a version earlier than to version or a later version, change the Collection Interval value for the PD_RGD record to Settings for communication from Analytics probe server to Tuning Manager - Agent for RAID To use the data collected by Tuning Manager - Agent for RAID in Infrastructure Analytics Advisor, you must specify the necessary settings for communication with Analytics probe server. Procedure 1. On the host on which Tuning Manager - Agent for RAID is installed, register the port that is to be used for communication with Analytics probe server as a firewall exception. The default port number is To limit the servers that can access the performance data of Tuning Manager - Agent for RAID, add Analytics probe server to the htnm_httpsd.conf file managed by Tuning Manager - Agent for RAID. a. Stop the Tuning Manager Agent REST API component services. b. To the last line of the htnm_httpsd.conf file, register information about the management server that can connect to the agents on which use of the API is enabled. c. Start the Tuning Manager Agent REST API component services. Note: To use the API functions that access RAID Agent, you also need to register information about Infrastructure Analytics Advisor server in the htnm_httpsd.conf file. Related topics Restricting access to servers that access RAID Agent on page 207 Notes on using Tuning Manager - Agent for RAID Read the following if you want to use Tuning Manager - Agent for RAID with Infrastructure Analytics Advisor. Collecting additional records for Infrastructure Analytics Advisor might affect the performance of Tuning Manager - Agent for RAID. Check whether the message KAVE00213-W, which indicates that the PI record type could not be generated, is output to the common message log at a specific time every hour. 104 Adding probes to Analytics probe server

105 When you change the host name or port number used for Tuning Manager - Agent for RAID, update the settings information for the Hitachi Enterprise Storage probe by using Analytics probe server. Adding Hitachi Enterprise Storage probe The Hitachi Enterprise Storage probe collects data from VSP G1000, VSP G1500, VSP F1500, VSP Gx00 models, VSP Fx00 models, Virtual Storage Platform, and HUS VM storage systems. This procedure presumes you are using the RAID Agent bundled with Infrastructure Analytics Advisor server. The procedure is the same for using Tuning Manager - Agent for RAID. Note: When you add the Hitachi Enterprise Storage probe, the following message might be displayed: Some required opcodes are turned off by default on RAID Agent. Ensure that these are enabled to collect the related metrics. Before proceeding further, refer to product user documentation. Ignore this message as this setting is automatically enabled on RAID Agent in Hitachi Infrastructure Analytics Advisor. Procedure 1. On the Analytics probe server home page, click Add Probe. 2. In the Add Probe window, from the Probes list, select Hitachi Enterprise Storage. 3. In the Provide RAID Agent Details section, provide the following details, and then click Next: Probe Name: The probe name must contain a minimum of four alphanumeric characters. Example: HESP The probe name must be unique in the Data Center Analytics deployment. The probe name cannot include any special characters other than hyphen and underscore. Connection Type: Choose HTTP. Note: HTTPS is not supported. RAID Agent IP Address: IP address of the machine on which the RAID Agent is installed. RAID Agent Host name: Host name of the machine on which the RAID Agent is installed. The host name must match the host name (case-sensitive). Specify the host name that is returned when you run the uname -n command on the RAID Agent server. Do not use localhost. RAID Agent Port: Port number used by the RAID Agent on the RAID Agent host. The default port number is: Adding probes to Analytics probe server 105

106 24221-HTTP Storage System Serial number: The serial number of the storage system that is configured on the RAID Agent. Storage System Instance: Storage instance name (alias) that is used to add the storage system to the RAID Agent. Enable real time data collection: Select the check box to collect real-time data that can be used for alerts, reports, and the REST API. Note: Enabling the real-time data collection increases the load on the Data Center Analytics server CPU and memory. To disable the real-time data collection, clear the Enable real time data collection check box. 4. In the Configure RAID Agent Collection Interval window, set PLC (Poll Configuration) to 60, and then click Next. Note: Do not change any other default values in this window. 5. In the Provide Hitachi Device Manager details window, select the appropriate option for collecting configuration metrics from Hitachi Device Manager. Select No to skip this step. If you select No, then the Provide Hitachi Device Manager details section is unavailable. Click Next, and a message appears, stating that the Hitachi Enterprise Storage probe is successfully added. Select Yes to enable the Provide Hitachi Device Manager details. If the Provide Hitachi Device Manager details option is enabled, type the following details, and then click Next: Connection Type: Choose HTTP or HTTPS. IP Address: IP address of the Hitachi Device Manager (HDvM) server. Port: Port number of the Hitachi Device Manager server. The default port numbers are: 2001-HTTP 2443-HTTPS Username/Password: User name and password of the Hitachi Device Manager. The user must be added in the ViewGroup user group of Hitachi Device Manager. 6. In the Validation window, Click Next, and then click OK. 7. In the Status window, in Action, click Start to start collecting data. 106 Adding probes to Analytics probe server

107 8. If you try to set up the Hitachi Enterprise Storage probe immediately after setting up an instance in the RAID Agent, the setup task fail with the following alert: 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 try again. You might have to wait approximately one hour before you can add the Hitachi Enterprise Storage probe. Related topics Initial setup after adding a probe on page 128 Values used for estimating disk space when using Tuning Manager - Agent for RAID The following information is necessary for calculating the disk space required to use Tuning Manager - Agent for RAID with Infrastructure Analytics Advisor. Calculate the disk space required by Tuning Manager - Agent for RAID and verify that there is adequate disk space available. The calculation is performed based on information about records already collected by Tuning Manager - Agent for RAID, and information about records that will be additionally collected for Infrastructure Analytics Advisor by Tuning Manager - Agent for RAID. The record information described here relates to records to be additionally collected by Tuning Manager - Agent for RAID. For details about other records, see Hitachi Command Suite System Requirements. Method for estimating number of instances Record ID PD_HGC PD_HHGC PD_LDCC PD_LDD PD_LHGC PD_LWPC PD_MPBC Method for estimating number of instances Number of host groups that exist in the storage system Total number of hosts that belong to the host groups that exist in the storage system Number of copied logical devices Number of logical devices Total number of LUNs that belong to the host groups that exist in the storage system Sum of the number of settings related to LDEVs and the WWNs of host bus adapters *, and the number of settings related to LDEVs and iscsi names * Number of MP blades Adding probes to Analytics probe server 107

108 Record ID PD_PWPC PD_RGD Method for estimating number of instances Total number of settings related to ports and the WWNs of host bus adapters * Number of parity groups *: To specify this setting, use Server Priority Manager, which is provided by Hitachi storage systems. Size of each record Record ID Fixed part 1 (bytes) Variable part 1 (bytes) Fixed part 2 (bytes) Variable part 2 (bytes) PD_HGC PD_HHGC PD_LDCC PD_LDD PD_LHGC PD_LWPC PD_MPBC PD_RGD PD_PWPC Retention period for the records (default value) Record ID Retention period (unit: hours) PD_HGC 168 PD_HHGC 168 PD_LDCC 168 PD_LDD 168 PD_LHGC 168 PD_LWPC 168 PD_MPBC 168 PD_RGD 168 PD_PWPC Adding probes to Analytics probe server

109 Adding Hitachi Adaptable Modular Storage (AMS) probe The AMS probe also supports HUS storage controllers. Procedure 1. On the Analytics probe server home page, click Add Probe. 2. In the Add Probe window, from the Probes list, select Hitachi AMS. 3. In the Add Hitachi AMS Probe section, type the following details, and then click Next: Hitachi AMS Probe Name: Name of the HUS100 storage system for which the probe is added. (This must not be the same as the storage name that is defined in your environment.) After you add the probe, it is identified with this name in the Analytics probe server. Controller 0 IP address and Controller 1 IP address: IP addresses of Controller 0 and Controller 1. User name and Password: User name and password of the user with read-only permissions. Note: If the user authentication for the HUS100 storage system is disabled, then you must type a dummy user name and password because these two fields are mandatory for adding the AMS probe. 4. In the Validation window, click Next, and then click OK. 5. In the Status window, in Action, click Start to start collecting data. Related topics Initial setup after adding a probe on page 128 Adding Hitachi NAS probe Add a Hitachi NAS probe to collect data from the Hitachi NAS platform. Before you begin Make sure that the external NAS System Management Unit (SMU) users have SMU CLI access and internal SMU users have Administrator User Group access. Procedure 1. On the Analytics probe server home page, click Add Probe. Adding probes to Analytics probe server 109

110 2. In the Add Probe window, from the Probes list, select Hitachi NAS. 3. In the Add Hitachi NAS Probe section, type the following details, and then click Next: SMU IP: The IP address of the Hitachi NAS System Management Unit (SMU). User name and Password: User credentials of the SMU user. 4. In the Validation window, click Next. 5. Based on the IP address that you entered in the SMU IP field, the Choose Server window for external SMU or Provide Controller Details window for internal SMU appears : External SMU: In the Choose Server window, select the servers, and then click Next. (The Choose Server window lists all servers associated with the SMU.) Internal SMU: In the Provide Controller Details window, type the username and the password of the controller that you want to add. 6. In the Validation window, click Next, and then click OK. 7. In the Status window, in Action, click Start to start collecting data. Related topics Initial setup after adding a probe on page 128 Adding IBM XIV probe The IBM XIV probe collects configuration and performance data from IBM XIV storage systems. Before you begin Download XIV CLI v3.0.1 from the IBM support site and save it in Analytics probe server in the /opt directory. Procedure 1. Log on to the Analytics probe server through an SSH client (like putty) using the following credentials: Host: IP address of the Analytics probe server User: root Password: app.jeos 2. Navigate to the /opt directory: cd /opt 3. Copy the IBM XIV CLI package in the /opt directory (package name must be similar to the following: xivcli build3-linux32.tar). 4. Extract the package at the /opt location using the following command: tar xvf package-name 5. Verify the following after extracting the package at the/opt location: 110 Adding probes to Analytics probe server

111 a. The /opt directory must have the following subdirectories: XIVGUI/ lib, XIVGUI/jre, and XIVGUI/xcli. b. If the structure does not match, then check if it contains the binary file. For example, xivcli build3-linux32.bin. c. Go to the directory that contains the binary file and run it. For example:./xivcli build3-linux32.bin d. The software prompts for a location. Provide the installation directory location as /opt/xivgui. 6. On the Analytics probe server home page, click Add Probe. 7. In the Add Probe window, from the Probes list, select IBM XIV. 8. In the Probes Details section, type the following details, and then click Next: Storage System IP Address: IP address of the target IBM XIV storage system. User name: User name of the storage system. Verify that the user has the minimum read-only permissions to collect configuration and performance data. Password: User password 9. In the Validation window, click Next, and then click OK. 10. In the Status window, in Action, click Start to start collecting data. Related topics Initial setup after adding a probe on page 128 Adding EMC VNX File probe The EMC VNX file probe collects the NAS configuration and NAS performance data from the VNX file storage systems. Procedure 1. On the Analytics probe server home page, click Add Probe. 2. In the Add Probe window, from the Probes list, select VNX File. 3. In the VNX File Probe Details window, type the following details, and then click Next: IP Address: IP address of VNX File control station. Username: User name to log on to the VNX file storage. Verify that the user has at least an operator role. For this, verify that the nasadmin operator role and CLI access allowed options are selected. Password: Password to log on to the VNX File storage. 4. In the Validation window, click Next, and then click OK. 5. In the Status window, in Action, click Start to start collecting data. Adding probes to Analytics probe server 111

112 Related topics Initial setup after adding a probe on page 128 Adding EMC VNX Block probe EMC VNX block probe collects data from VNX storage systems. Before you begin Authorize the VNX Block storage system user to perform a minimum operator role. Enable the Statistics logging to collect performance data. Statistics logging affects storage-system performance, so leave it off unless you want to monitor performance. Install the NaviCLI on the Analytics probe server machine. Procedure 1. Log on to the probe appliance using an SSH client like putty, with the following credentials: User name: root Password: app.jeos 2. Copy the NaviCLI package on the Analytics probe server. 3. Go to the location you saved NaviCLI package and run the following command to install the package: rpm -ivh <NaviCLI package RPM> Note: The NaviCLI executable file must be at the following location: /opt/navisphere/bin/ The group level permissions of the /opt/navisphere/ directory must be read and write, you can set the group level permission using the following commands: chmod -R 755 /opt/navisphere/ chown -R root:megha /opt/navisphere/ 4. On the Analytics probe server home page, click Add Probe. 5. In the Add Probe window, from the Probes list, select VNX Block. 6. In the VNX Block Probe Details window, type the following details, and then click Next: Probe Name: Unique name of the probe. Processor-A IP Address: IP address of Processor A of VNX block storage. 112 Adding probes to Analytics probe server

113 Processor-B IP Address: IP address of Processor B of VNX block storage. Username: User name of the user to log on to VNX Block storage. Password: Password of the user name. Scope: Select the user level from the drop-down. The available options are Global, Local, and LDAP. Enable real time data collection: Select the check box to collect real-time data that can be used for alerts, reports, and REST API. Note: Enabling the real-time data collection increases the load on the Data Center Analytics server CPU and memory. To disable the real time data collection, clear the Enable real time data collection check box. 7. In the Validation window, click Next, and then click OK. 8. In the Status window, in Action, click Start to start collecting data. Related topics Initial setup after adding a probe on page 128 Adding the EMC XtremIO probe The EMC XtremIO probe collects configuration and performance data from the EMC XtremIO storage systems. Before you begin The host name or IP address of the XtremIO Management server must be accessible from Analytics probe server using the default port 443. User with read-only permissions on XtremIO Management server to execute REST API calls. Procedure 1. On the Analytics probe server home page, click Add Probe. 2. In the Add Probe window, from the Probes list, select EMC XtremIO. 3. In the Provide XtremIO Management Server Details section, click Add XMS. 4. Type the following details, and then click Next: Host Name / IP: The host name or IP address of the XtremIO Management server. User Name: User with read-only permissions on XtremIO Management server to execute REST API calls. Password: User password. Enable real time data collection: Select the check box to collect real-time data that can be used for alerts, reports, and REST API. Adding probes to Analytics probe server 113

114 Note: Enabling the real-time data collection increases the load on the Data Center Analytics server CPU and memory. To disable the real time data collection, clear the Enable real time data collection check box. 5. In the Validation window, click Next. The Managed XtremIO cluster section appears. 6. Select the cluster and click Next. Note: If you select multiple clusters, then the system adds a new EMC XtremIO probe for each cluster. 7. When adding multiple clusters, the Status window shows multiple probes. Start each probe individually to collect data. 8. In the Validation window, click Next, and then click OK. 9. In the Status window, in Action, click Start to start collecting data. Related topics Initial setup after adding a probe on page 128 Adding EMC VMAX probe EMC VMAX probe collects data from EMC VMAX storage systems. Configuration in target environment EMC Unisphere for VMAX: A machine with EMC Unisphere for VMAX ( , , , ) installed, monitoring target storage systems. EMC Solutions Enabler Symmetrix CLI: A machine (could be the same as for EMC Unisphere for VMAX or different) with EMC Solutions Enabler Symmetrix CLI ( , 8.0.3, , ) installed, monitoring all the target storage systems for which you are adding the probe. If authentication is enabled for Symmetrix arrays, then add a megha user with the monitor role for each Symmetrix array. Adding a megha user for the Symmetrix array Procedure 1. Log on to the EMC Solutions Enabler Symmetrix CLI server. 2. Go to the <Installation Directory>/symcli/bin directory. 3. Verify that authentication is enabled using the following command: symauth list 114 Adding probes to Analytics probe server

115 4. Add the megha user with the monitor access using the following command: symauth -sid <SYMMETRIX ID> -file <filename> commit Create a new file with the content (assign user megha to role Monitor;) and provide it as a file name in the add mega user with monitor access command. Install EMC Solutions Enabler Symmetrix CLI Procedure 1. Log on to the Analytics probe server with the following credentials: User name: root Password: app.jeos. 2. Copy the EMC Solutions Enabler Symmetrix CLI tar file on Analytics probe server machine. Note: We recommend that you install the same version of EMC Solutions Enabler Symmetrix CLI, as installed in the target environment. 3. Extract the tar file using the following command: tar -zcxf se<version>-linux-i386-smi.tar.gz 4. Install EMC Solutions Enabler Symmetrix CLI using the following command:./se<version>_install.sh -install -all Configure the environment variable entry in netcnfg file To collect data from target storage systems using EMC Solutions Enabler Symmetrix CLI, edit the netcnfg file. Before you begin Verify the security_level property on the machine where EMC Solutions Enabler Symmetrix CLI server is installed. Procedure 1. Log on to the Analytics probe server with the following credentials: Username: root Password: app.jeos 2. Edit the netcnfg file: vi/var/symapi/config/netcnfg Adding probes to Analytics probe server 115

116 3. At the end of the file, add the following: SYMCLI_<SYMCLI SERVER IP address> - TCPIP address <Server Nodname> <IP Address> <Port> <Security Level> <Server Nodname> is the Server host name where EMC Solutions Enabler Symmetrix CLI is installed in target environment. <IP Address> is the IP address of the machine where EMC Solutions Enabler Symmetrix CLI is installed. <Security Level > if security level is set as NONSECURE or ANY, then use NONSECURE. if security level is set as SECURE, then use SECURE. Default port number 2707-TCP for SYMCLI Example: SYMCLI_ TCPIP WIN-PC NONSECURE SYMCLI_ TCPIP WIN-PC SECURE 4. Edit the /etc/hosts file, and add an entry for the target SYMAPI server: <SYMAPI SERVER IP ADDRESS> <SYMAPI SERVER HOST NAME> For example: WIN-PC1 Note: If you are using the DNS server, then configure it on the probe to avoid making changes in the /etc/hosts file. 5. Save the file. Adding EMC VMAX probe EMC VMAX probe collects data from EMC VMAX storage systems. Procedure 1. On the Analytics probe server home page, click Add Probe. 2. In the Add Probe window, from the Probes menu, select VMAX. 3. In the VMAX Unisphere Details window, click Add Unisphere. 4. In the Add VMAX Unisphere window, type the following details, and then click Next: IP Address: IP Address of the machine where EMC Unisphere for VMAX is installed. User name and Password: User name and password for EMC Unisphere. 116 Adding probes to Analytics probe server

117 5. In the Managed VMAX Storage System window, select the VMAX storage systems, type the Sym CLI Host IP address, and then click Finish. 6. In the Status window, in Action, click Start to start collecting data. Adding VMAX probe for an already added EMC Unisphere for VMAX You can VMAX probe for previously added EMC Unisphere for VMAX. Procedure 1. On the Analytics probe server home page, click Add Probe. 2. In the Add Probe window, from the Probes menu, select VMAX. 3. In the Managed VMAX Storage System window, select the VMAX storage systems for which you want to add VMAX probe and enter the Sym CLI Host IP address where the EMC Solutions Enabler Symmetrix CLI is installed. Adding probes to Analytics probe server 117

118 4. Click Finish, and then click OK. Editing details of EMC Unisphere for VMAX The EMC Unisphere for VMAX administrator can change the password or user name in the Analytics probe server to continue data collection. Procedure 1. In the Status window, stop the VMAX probe. 2. Click the Edit link corresponding to the EMC Unisphere for VMAX. 3. In the Edit VMAX Unisphere Details window, edit the user name or password of the EMC Unisphere for VMAX, and then click Next. 4. In the Validation window, click Next, and then click OK. Adding Netapp probe The NetApp probe collects configuration and performance data from NetApp storage systems using the ONTAP API. Prerequisites Ensure that you have a user with read-only privileges available on the NetApp storage system with the appropriate role to collect configuration and performance data. Analytics probe server supports 7-mode and C- mode types of NetApp storage systems. The procedure for creating users depends on the target of the storage system type. 118 Adding probes to Analytics probe server

119 The recommended security settings on the NetApp storage system are: tls.enable=on ssl.v3.enable=off CertificateKey length=2048 Adding the Netapp probe in the Analytics probe server Procedure 1. On the Analytics probe server home page, click Add Probe. 2. In the Add Probe window, from the Probes menu, select NetApp. 3. In the Probe Details section, type the following details, and then click Next: NetApp Server: IP address of the NetApp server. Username and Password: Type the user name and password you created. Enable real time data collection: Select the check box to collect real-time data that can be used for alerts, reports, and REST API. Note: Enabling the real-time data collection increases the load on the Data Center Analytics server CPU and memory. To disable the real time data collection, clear the Enable real time data collection check box. 4. In the Validation window, click Next, and then click OK. 5. In the Status window, in Action, click Start to start collecting data. Related topics Creating a user for NetApp 7-mode on page 119 Creating a user for NetApp C-mode on page 121 Configuring security settings for NetApp storage systems on page 121 Initial setup after adding a probe on page 128 Creating a user for NetApp 7-mode Procedure 1. Log on to the NetApp command line. 2. Add a role using the following command: Run the following command for NetApp storage system version 7.3.6: useradmin role add <role name> -a login-http-admin,apisystem-get-info,api-license-list-info,api-aggr-listinfo,api-volume-list-info,api-nfs-exportfs-list-rules,apidisk-list-info,api-quota-report,api-lun-list-info,api-lunmap-list-info,api-qtree-list,api-perf-object-instance-listinfo,api-perf-object-counter-list-info,api-perf-object-get- Adding probes to Analytics probe server 119

120 instances,api-system-get-version,api-snapmirror-getstatus,api-useradmin-user-list,api-volume-get-rootname,api-volume-options-list-info,api-useradmin-grouplist,api-snapshot-list-info,api-useradmin-role-list,apinet-ifconfig-get,security-api-vfiler,api-fcp-adapterinitiators-list-info,api-fcp-adapter-list-info,api-igrouplist-info,api-iscsi-initiator-list-info,api-perf-objectinstance-list-info-iter* For example: dataontap> useradmin role add role_name -a login-httpadmin,api-system-get-info,api-license-list-info,api-aggrlist-info,api-volume-list-info,api-nfs-exportfs-listrules,api-disk-list-info,api-quota-report,api-lun-listinfo,api-lun-map-list-info,api-qtree-list,api-perf-objectinstance-list-info,api-perf-object-counter-list-info,apiperf-object-get-instances,api-system-get-version,apisnapmirror-get-status,api-useradmin-user-list,api-volumeget-root-name,api-volume-options-list-info,api-useradmingroup-list,api-snapshot-list-info,api-useradmin-rolelist,api-net-ifconfig-get,security-api-vfiler,api-fcpadapter-initiators-list-info,api-fcp-adapter-list-info,apiigroup-list-info,api-iscsi-initiator-list-info,api-perfobject-instance-list-info-iter* Role <Role_Name> added. Mon Apr 25 16:03:02 IST [netapp73-1 (takeover): useradmin.added.deleted.info]: The role 'Role_Name' has been added. Run the following command for NetApp storage system version 8.0.1: useradmin role add <role name> -a login-http-admin,apisystem-get-info,api-license-list-info,api-aggr-listinfo,api-volume-list-info,api-nfs-exportfs-list-rules,apidisk-list-info,api-quota-report,api-lun-list-info,api-lunmap-list-info,api-qtree-list,api-perf-object-instance-listinfo,api-perf-object-counter-list-info,api-perf-object-getinstances,api-system-get-version,api-snapmirror-getstatus,api-useradmin-user-list,api-volume-get-rootname,api-volume-options-list-info,api-useradmin-grouplist,api-snapshot-list-info,api-useradmin-role-list,apinet-ifconfig-get,security-api-vfiler,api-fcp-adapterinitiators-list-info,api-fcp-adapter-list-info,api-igrouplist-info,api-iscsi-initiator-list-info,api-perf-objectinstance-list-info-iter* For example: dataontap> useradmin role add role_name -a login-httpadmin,api-system-get-info,api-license-list-info,api-aggrlist-info,api-volume-list-info,api-nfs-exportfs-listrules,api-disk-list-info,api-quota-report,api-lun-listinfo,api-lun-map-list-info,api-qtree-list,api-perf-objectinstance-list-info,api-perf-object-counter-list-info,apiperf-object-get-instances,api-system-get-version,apisnapmirror-get-status,api-useradmin-user-list,api-volume- 120 Adding probes to Analytics probe server

121 get-root-name,api-volume-options-list-info,api-useradmingroup-list,api-snapshot-list-info,api-useradmin-rolelist,api-net-ifconfig-get,security-api-vfiler,api-fcpadapter-initiators-list-info,api-fcp-adapter-list-info,apiigroup-list-info,api-iscsi-initiator-list-info,api-perfobject-instance-list-info-iter* Role <Role_Name> added. dataontap> Mon Apr 25 16:03:02 IST [dataontap: useradmin.added.deleted.info]: The role 'Role Name' has been added. 3. Add a group using the following command: useradmin group add group_name -r role_name 4. Add a user using the following command: useradmin user add user_name -g group_name 5. Type the password for the user. Creating a user for NetApp C-mode Procedure 1. Log on to the target NetApp storage system using NetApp OnCommand System Manager. 2. Navigate to NetApp Storage system name > Configuration > Security > Users. 3. In the Users pane, click Add and type details in the Add User window: User Name: Type any valid user name. Password and Confirm Password: Type the user password and confirm it. Note: By default, the password is selected in the Authentication column. 4. In the User login methods section, click Add. 5. In the Application column, select ontapi. 6. In the Role column, select readonly, and then click OK. 7. Click Add. Result The new user is added. You can use this user to collect configuration and performance data. Configuring security settings for NetApp storage systems You must configure the probe to work with the security settings on the NetApp storage system. You can view and edit the security settings using the options command in the NetApp storage system. The recommended security Adding probes to Analytics probe server 121

122 settings on the NetApp storage system are: tls.enable=on, ssl.v3.enable=off, and CertificateKey length= The relevant security settings on the NetApp storage system are as follows: TLS is enabled or disabled Check value of tls.enable=[on OFF] SSL.v3 is enabled or disabled Check value of ssl.v3.enable=[on OFF] Length of Certificate Key on NetApp Verify your system complies with one of the following examples: Case 1: On the NetApp storage system, TLS is enabled (most preferred) tls.enable=on ssl.v3.enable=can be either ON or OFF CertificateKey length=1024 or 2048 On the probe VM, verify the java.security file for the following lines: jdk.certpath.disabledalgorithms=md2, MD5, RSA keysize < 1024 This line must be uncommented and must include RSA keysize < 1024 jdk.tls.disabledalgorithms=sslv3, MD5withRSA, DH keysize < 768 This line must be uncommented and must include SSLv3 Case 2: On the NetApp storage system, TLS is disabled and SSLv3 is enabled (less preferred) tls.enable=off ssl.v3.enable=on CertificateKey length=1024 or 2048 On the probe VM, verify the java.security file for the following lines: jdk.certpath.disabledalgorithms=md2, MD5, RSA keysize < 1024 This line must be uncommented and have RSA keysize < 1024 jdk.tls.disabledalgorithms=sslv3, MD5withRSA, DH keysize < 768 This line must be commented (comment-out this line if currently uncommented). This enables SSL.v3 to be used. Case 3: On the NetApp storage system, the length of the certificate key is less than 1024 (for example, 512) Certificate keys less than 1024 are not common. In such a case, verify with the NetApp system administrator if it can be upgraded to a Certificate Key with the length 2048 (preferred) or If the upgrade is possible, Case 1 or Case 2 is applicable. 122 Adding probes to Analytics probe server

123 If the length of Certificate is Key 512 or less, either tls.enable=on or ssl.v3.enable=on On the probe VM, verify the java.security file for the following lines: jdk.certpath.disabledalgorithms=md2, MD5, RSA keysize < 512 This line must be uncommented and must include RSA keysize < 512' or the present key length. jdk.tls.disabledalgorithms=sslv3, MD5withRSA, DH keysize < 768 This line must be commented (uncommented to enable). This enables SSL.v3 use. Adding the Pure Storage probe The Pure Storage probe collects configuration and performance data from the Pure Storage storage systems. Before you begin The host name or IP address of the storage system must be accessible from the Analytics probe server. The port number 80 (HTTP) and 443 (HTTPS) must be open on the storage system. You have obtained the API token of a user with read-only permission for executing API calls. Procedure 1. On the Analytics probe server home page, click Add Probe. 2. In the Add Probe window, from the Probes list, select Pure Storage. 3. In the Provide Pure Storage Details section, type the following details, and then click Next: IP Address/FQDN: The host name or IP address of the storage system. Connection Type: Select HTTP or HTTPS protocol for REST connection. API Token: Type the API token of a user with read-only permission for running REST API calls. Enable real-time data collection: Select the check box to collect real-time data be used for alerts, reports, and REST API. Note: Enabling real-time data collection can increase the load on the Data Center Analytics server CPU and memory. To disable the real time data collection, clear the Enable real time data collection check box. 4. In the Validation window, click Next, and then click OK. Adding probes to Analytics probe server 123

124 5. In the Status window, in Action, click Start to start collecting data. Related topics Initial setup after adding a probe on page 128 Adding VMware probe VMware probe collects data from the VMware vcenter Server and standalone VMware ESXi server. Procedure 1. From the Analytics probe server home page, click Add Probe. 2. In the Add Probe window, from the Probes drop-down list, select the VMware. 3. In the Add VMware Probe section, type the following details, and then click Next: vcenter Server: Host name or IP address of the VMware vcenter Server Appliance or VMware ESXi host IP address. User name: Any user having access to VMware vcenter Server. (Read-only privileges are sufficient.) Password: Password of the VMware vcenter user. 4. In the Validation window, click Next, and then click OK. 5. In the Status window, in Action, click Start to start collecting data. Related topics Initial setup after adding a probe on page 128 Adding Brocade Network Advisor probe Brocade Network Advisor probe collects data from Brocade Network Advisor, which manages the entire Brocade IP address and SAN portfolio for unified network visibility and control. Before you begin Make sure you can access Brocade Network Advisor using the port 80. The user must have Area of Responsibility as All Fabrics and at least one role SAN Discovery setup or Performance with read-only permissions. Brocade Network Advisor Professional plus or Brocade Network Advisor Enterprise must be installed. 124 Adding probes to Analytics probe server

125 Procedure 1. From the Analytics probe server home page, click Add Probe. 2. In the Add Probe window, from the Probes drop-down list, select Brocade FC Switch (BNA). 3. In the Add Brocade FC Switch (BNA) Probe window, type the following details, and then click Next.. Network Advisor IP Address: IP address of Brocade Network Advisor. Username and Password: User name and password of the Brocade Network Advisor. 4. In the Validation window, click Next, and then click OK. 5. In the Status window, in Action, click Start to start collecting data. Related topics Initial setup after adding a probe on page 128 Adding Cisco DCNM probe Add a probe to collect data from the Cisco Data Center Network Manager. Procedure 1. From the Analytics probe server home page, click Add Probe. 2. In the Add Probe window, from the Probes drop-down list, select Cisco FC Switch (DCNM). 3. In the Add Cisco FC Switch (DCNM) Probe window, type the following details and click Next: Cisco FC Switch (DCNM) IP Address: IP address of DCNM. DCNM Web service Port: Type the port number to access web service on the DCNM server. Note: In some environments, the port number is optional: For example, 80 is the port number: sanservice. Protocol : Select HTTP or HTTPS. Default ports are: 80 - HTTP HTTPS Username and password of DCNM. 4. In the Validation window, click Next, and then click OK. Adding probes to Analytics probe server 125

126 5. In the Status window, under Action, click Start to start collecting data. Related topics Initial setup after adding a probe on page 128 Adding Cisco SAN Switch probe Add a probe to collect data from Cisco SAN switches. Note: If the Cisco SAN switches are managed by Cisco DCNM, then use either the Cisco DCNM probe or Cisco SAN Switch probe to collect the data. Do not use both the Cisco DCNM and Cisco SAN Switch probes to collect data for the same switch. Procedure 1. On the Analytics probe server home page, click Add Probe. 2. In the Add Probe window, from the Probes menu, select Cisco FC Switch (CLI). 3. In the Add Cisco FC Switch (CLI) window, in Add Switch Details, type the following details: Select Add Device, type the following details, and then click Add Switch: Data Center: Name of the data center with the Cisco SAN switch. Start IP Address and End IP Address: Range of the IP address, from which to start collecting data. This scans all the switch IP addresses in that range, and the switch IP address is added in the system. User Name: User name with the network-operator role and readonly privileges. Password: Password of the user name. SSH Port: The port number. (default: 22) Select Upload CSV, to upload the switch details in the CSV file, and then click Import CSV. The CSV file must be in a specific format. You can download the sample file by clicking Download Sample CSV File. Select Upload Encrypted CSV to upload details in the encrypted CSV file, and then click Import CSV. The Encrypted CSV file must be in a specific format. You can download the sample file by clicking Download Sample CSV File link. The list of Cisco SAN switch IP address appears. 4. If you want to add more Cisco SAN switch IP addresses, click Add More. 5. Click Next. This scans all the switch IP addresses from the specified range, and the valid switch IP address is added in the system. 126 Adding probes to Analytics probe server

127 6. In the Switch Validation window, click Next, and then OK. The switch IP passed the validation and is added as a probe. 7. In the Status window, in Action, click Start to start collecting data. Related topics Encrypting the CSV file on page 127 Initial setup after adding a probe on page 128 Encrypting the CSV file Before uploading the CSV file you must encrypt it using the public key. 1. Contact HDS support for the public key. 2. Log on to the probe console through an SSH client (like putty). 3. Create the temporary folder in the /data folder and save the public key. 4. Generate the random key using the following command: openssl rand -base64 32 > randomkey.bin 5. Encrypt the random key by using the public key, using the following command: openssl rsautl -encrypt -inkey public-key.pem -pubin -in randomkey.bin -out randomkey.bin.enc 6. Encrypt the CSV file by using the random key (not encrypted): openssl enc -aes-256-cbc -salt -in ResourceDef1.xml -out ResourceDef1.enc -pass file:./randomkey.bin 7. Download the encrypted random file and encrypted CSV file to your local machine. 8. Provide the encrypted random file and CSV file when adding the Cisco SAN Switch probe. Adding Linux probe The Linux probe collects performance and configuration data from individual machines running the Linux operating system. You can add a Linux probe for each target separately or a single probe for multiple targets. Before you begin The sysstat rpm package must be installed on the target machine or host. The target machine must have Perl installed with the following packages: IO::Select, IO::Handle, File::Path, File::Path qw(mkpath), Getopt::Std, Time::HiRes qw(gettimeofday), LWP::UserAgent, and The openssh-client must be installed on the target machine or host. Adding probes to Analytics probe server 127

128 Create an installation directory with read, write, and execute permissions. Create an installation directory only with alphanumeric, hypen, and underscore (other characters are not supported). Procedure 1. On the Analytics probe server home page, click Add Probe. 2. In the Add Probe window, from the Probes list, select Linux. 3. In the Add Host Details section, type the following details, and then click Next: Host IP Address: The IP address of the Linux host. USERNAME: A user on the target Linux machine with read, write, and execute permissions. PASSWORD: User password INSTALLATION DIRECTORY: Location for the data collection scripts 4. To add multiple targets, click Add More. The Host Validation section appears. The system validates the host IP address. 5. When adding multiple targets the Status window shows multiple probes. Start each probe individually to collect data. 6. Click Next. The Script Deployment section appears. The data collection scripts are deployed on the target host. 7. Click Next, and then click OK. 8. In the Status window, in Action, click Start to start collecting data. Related topics Initial setup after adding a probe on page 128 Initial setup after adding a probe After adding a probe, check if the Data Center Analytics server is collecting data. Procedure 1. Open a web browser, and then enter the following URL in the address bar to log on to Data Center Analytics server: 2. In the Data Center Analytics server logon window, enter the user name and password used to set up Data Center Analytics server. 3. Click the Server Status icon. 4. Verify that the added probe appears in Last Configuration Import Time and Last Performance Import Time of Data Import Status, and that data is collected. 128 Adding probes to Analytics probe server

129 Note: After a probe is added, it might take some time before the probe appears in the Data Center Analytics server GUI. 5. Open a web browser, and then enter the following URL in the address bar to log on to Infrastructure Analytics Advisor server: 6. Enter the following information to log on: User ID: system Password: manager (default) 7. In the Administration tab, select Resource Management. 8. Verify that the resources monitored by the probe appear and are ready to be analyzed by Infrastructure Analytics Advisor server. Note: After a probe is added, it might take some time before the registered resources appear in the Infrastructure Analytics Advisor server GUI. Adding probes to Analytics probe server 129

130 130 Adding probes to Analytics probe server

131 8 Installing Data Center Analytics server Windows-based probe Data Center Analytics server Windows-based probe is desktop-based software that collects performance and configuration data from the Windowsbased host and Hyper-V machines. You can install this probe using Data Center Analytics Windows-based probe installer. Data collection methods Installing the Windows-based probe Configuring Data Center Analytics Windows-based probe Initial setup after adding a probe Installing Data Center Analytics server Windows-based probe 131

132 Data collection methods You can use one of the following methods to collect data using the Windowsbased probe: Note: Infrastructure Analytics Advisor only supports Method 3 (data collection using Perfmon API and WMI query). Method 1: Data collection from System Center Operation Manager (SCOM) and System Center Configuration Manager (SCCM). Performance data is collected from SCOM Configuration data is collected from SCCM Prerequisites SCOM Target Windows-based machines must be configured in the SCOM server. A user with Advanced Operator or Administrator role with the permission to log on remotely to the SCOM server. Remote registry service must be running on the machine that is configured in the SCOM server. Access to the SCOM console, to import Management Pack in the SCOM server, and this pack configures the performance rules. Add following DLLs in Data Center Analytics server Windows-based probe installer folder: \bin Microsoft.EnterpriseManagement.OperationsManager.Common.dll Microsoft.EnterpriseManagement.OperationsManager.dll The above DLLs are under the following folder on Windows-based machine: System Center Operations Manager 2007\SDK Binaries SCCM Target Windows-based machines must be configured in the SCCM server. Hardware Inventory Client Agent of SCCM, must be running on the target machines. This agent collects required configuration data and stores it in the SCCM database. A user from the db_datareader group in the SQL Server who can access the SCCM database. Method 2: Data collection from the System Center Operation Manager (SCOM) and WMI query 132 Installing Data Center Analytics server Windows-based probe

133 Performance data is collected from the SCOM. Configuration data is collected from the individual machine and WMI query. Prerequisites SCOM Target Windows-based machines must be configured in the SCOM server. A user with Advanced Operator or Administrator role with the permission to log on remotely to the SCOM server. Remote registry service must be running on the machine that is configured in SCOM server. Access to the SCOM console, to import Management Pack in the SCOM server, and this pack configures the performance rules. Add following DLLs in Data Center Analytics server Windows-based probe installer folder: \bin Microsoft.EnterpriseManagement.OperationsManager.Common.dll Microsoft.EnterpriseManagement.OperationsManager.dll The above DLLs are under the following folder on Windows-based machine: System Center Operations Manager 2007\SDK Binaries WMI Query You must be a user who has been assigned the Domain Administrator role and who has permission to access WMI namespaces (ROOT\WMI, ROOT, and ROOT\CIMV2) on the target host. The Execute Methods and Remote Enable permissions are required for the namespaces. Firewall exceptions must be added for the WMI on the target machine. To add the exceptions run the following commands on the target machine: netsh advfirewall firewall set rule group="remote administration" new enable=yes netsh advfirewall firewall set rule group="file and Printer Sharing" new enable=yes For workgroup computers: Change the settings for the Remote User Account Control (UAC) LocalAccountTokenFilterPolicy registry entry. For more information, see Method 3: Data collection using Perfmon API and WMI query Installing Data Center Analytics server Windows-based probe 133

134 Performance and configuration data is collected from individual machines using the Perfmon API and WMI query. Prerequisites The probe machine and the target machines must be part of either workgroup or domain. Firewall exceptions must be added for the WMI and Perfmon on the target machine. To add the firewall exceptions, run the following commands on the target machine: netsh firewall set service RemoteAdmin netsh firewall set service type=fileandprint mode=enable profile=all scope=all To connect to Windows-based machines remotely, the following must exist: The remote registry service must be running on the target machine. On the target machine the Local Service must have read permissions for the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control \SecurePipeServers\winreg Users who are to use this method must be added to Log on as a service of the Local Group Policy Editor. To add these users, perform the following procedure: Execute the Local Group Policy Editor (gpedit.msc), select Computer Configuration > Windows Settings > Security Settings > Local Policies > User Rights Assignment, and then add the users who are to use this method to the Log on as a service policy. Distributed COM must be enabled in Component Services. To enable distributed COM, perform the following procedure: Execute Component Services (dcomcnfg.exe), and then select Component Services > Computers. When My Computer is displayed, rightclick My Computer, and then select Properties. After that, select the Default Properties tab, and then select Enable Distributed COM on this computer. For domain computers: A user with the Domain Administrator role or local administrator group of the target machine. For workgroup computer: The following settings are required if you are not using the built-in administrator for connections: You must be a user who has been assigned the Domain Administrator role and who has permission to access WMI namespaces (ROOT\WMI, ROOT, and ROOT\CIMV2) on the target host. 134 Installing Data Center Analytics server Windows-based probe

135 Execute Methods and Remote Enable permissions are required for the namespaces. Change the settings for the Remote User Account Control (UAC) LocalAccountTokenFilterPolicy registry entry. For more information, see Computer Browser service must be running on the target machine. Installing the Windows-based probe Install a probe with the Data Center Analytics Windows-based probe installer. Before you begin The authentication information (user name and password) on the Data Center Analytics server Windows-based probe server and the monitoring target server must match. Procedure 1. Run the Data Center Analytics Windows-based probe installer. 2. To continue installation, click Next. 3. In the Log on Information window, type the Domain Administrator s or Local user s user name and password for the Windows-based machine in the format specified in the window, and click Next. Note: The user must have the Logon as a Service permission. 4. In the Choose Destination Location window, browse to select the installation folder, and click Next. 5. In the Ready to Install the Program window, click Install to complete the installation. 6. Click Finish. Configuring Data Center Analytics Windows-based probe After installing the Windows-based probe, you must configure a collection method, set up an FTP or HTTPS server, and start the service for that probe. Configuring the collection method You must register the probe and select the data collection method for that probe. Installing Data Center Analytics server Windows-based probe 135

136 Procedure 1. Double-click the HDCA Windows Probe icon on the desktop. Note: If you do not see the icon on the desktop, then open a command prompt and enter the following to refresh the icon in the database: ie4uinit.exe ClearIconCache 2. In the License tab, browse to the license file and click Submit to register the probe. 3. Click the Collection tab, and configure the collection method settings based on your requirements: Method 1: Data collection from SCOM and SCCM a. In the Performance section, select Use SCOM and type the following details: SCOM Server: SCOM server IP address User Name (Advanced Operator): SCOM server user name Password: SCOM server password b. In the Configuration section, select Use SCCM and type the following details: SCCM Database Server: SCCM Server IP address or the name Database Name: SCCM database name SQL Server User Name: SCCM database user name SQL Server Password: SCCM database password Note: If you select the Trusted Connection check-box, then the SQL Server User Name and SQL Server Password fields are disabled. Method 2: Data collection from SCOM and WMI 1. In the Performance section, select Use SCOM and type the following details: SCOM Server: SCOM server IP address User Name (Advanced Operator): SCOM server user name Password: SCOM server password 2. In the Configuration section, select Use WMI and type the following details: User Name (Administrator): Domain administrator user name 136 Installing Data Center Analytics server Windows-based probe

137 Password: Domain administrator user name password Collect Event Logs: Select the check box to collect event logs Method 3: Data collection through WMI and PerfMon 1. In the Performance section, select Use Perfmon. This enables the Use WMI option automatically. 2. Type the following details for Use Perfmon and Use WMI options: a. User name (Administrator): In Workgroup environment: Machine Name\User Computer Name: Machine name on which the Windows-based probe is installed. User: A user with an Administrator role. In the Active Directory environment: Domain Name\User Domain Name: Name of the domain. User: A user with the Domain Administration role. b. Password 3. To collect event logs, in the Configuration section, select the Collect Event Logs check box. To allow you to select the types of logs. 4. In the Performance section, select Collect Process Data. 4. On the Collection tab, in the right most side section: Click Discover Hosts to discover the hosts available in the current domain. You can then select the target host that you want to monitor. Click Add Hosts and type host names manually. The Add Hosts window appears, enter a comma-separated list of Windows-based machines (host names or IP addresses). 5. Click Validate & Save to establish the connection, and click OK. Related topics Starting the Windows-based probe service on page 138 Configuring the FTP or HTTPS server You must configure the FTP server for the Windows-based probe to send data. Procedure 1. On the Windows-based probe console, click the Upload Settings tab. Installing Data Center Analytics server Windows-based probe 137

138 2. On the Upload Settings tab, select the protocol FTP or HTTPS. 3. Type the following details: FTP Server: Type the Data Center Analytics server server IP address where you want to upload the data. Port: Port number. The default port for FTP is 22. User: meghadata Password: meghadata123 Note: Do not change the password of the FTP user meghadata used on the Data Center Analytics server. You can disable the shell assigned to meghadata if you want to protect the account from login attempts. 4. To use a proxy server, select the Use Proxy check box and type the following details: Proxy Server: Name or IP address of the proxy server. Proxy Type: Proxy type of the proxy server HTTP or SOCKS5. Port: Proxy FTP port. Login and Password: User name and Password of the proxy server. 5. Click Validate & Save. 6. Start the Windows-based probe service. Related topics Starting the Windows-based probe service on page 138 Starting the Windows-based probe service Start the probe service from the Status tab in the probe console. Procedure 1. On the Windows-based probe console, click the Status tab. The Status tab list the details of the upload information and service information. 2. Verify the upload and service information, and click Start. Initial setup after adding a probe After adding a probe, check if the Data Center Analytics server is collecting data. 138 Installing Data Center Analytics server Windows-based probe

139 Procedure 1. Open a web browser, and then enter the following URL in the address bar to log on to Data Center Analytics server: 2. In the Data Center Analytics server logon window, enter the user name and password used to set up Data Center Analytics server. 3. Click the Server Status icon. 4. Verify that the added probe appears in Last Configuration Import Time and Last Performance Import Time of Data Import Status, and that data is collected. Note: After a probe is added, it might take some time before the probe appears in the Data Center Analytics server GUI. 5. Open a web browser, and then enter the following URL in the address bar to log on to Infrastructure Analytics Advisor server: 6. Enter the following information to log on: User ID: system Password: manager (default) 7. In the Administration tab, select Resource Management. 8. Verify that the resources monitored by the probe appear and are ready to be analyzed by Infrastructure Analytics Advisor server. Note: After a probe is added, it might take some time before the registered resources appear in the Infrastructure Analytics Advisor server GUI. Installing Data Center Analytics server Windows-based probe 139

140 140 Installing Data Center Analytics server Windows-based probe

141 9 Upgrading Infrastructure Analytics Advisor environment You can upgrade Infrastructure Analytics Advisor and its components. Upgrade workflow for a two-host configuration Upgrade workflow for a three-host configuration Verifying the yum/rpm dependency packages Upgrade the Infrastructure Analytics Advisor server and the Data Center Analytics server on a Linux host Upgrading the Infrastructure Analytics Advisor server on a Windows host Upgrading the Analytics probe server Upgrading the RAID Agent Upgrading the Data Center Analytics server Windows-based probe Upgrading the Configuration Manager REST API Postupgrade guidelines Upgrading Infrastructure Analytics Advisor environment 141

142 Upgrade workflow for a two-host configuration For a two-host configuration where Infrastructure Analytics Advisor server and Data Center Analytics server are installed on the same host and Analytics probe server is installed on a different host, run the installer to upgrade the following components: Infrastructure Analytics Advisor server Data Center Analytics server Analytics probe server RAID Agent Note: The following notes apply when using Tuning Manager - Agent for RAID: You do not need to upgrade RAID Agent. Check whether relationship with the upgraded version of Infrastructure Analytics Advisor is supported for the current version of Tuning Manager - Agent for RAID. If relationship is not supported, upgrade Tuning Manager - Agent for RAID. For the upgrade procedure, see the Hitachi Command Suite Tuning Manager Installation Guide. This upgrade cannot be performed by deploying the OVA file for virtual appliances. Perform the upgrade by using the installer even if a new installation was performed by deploying the OVA file for virtual appliances. The following figure shows the sequence for upgrading an Infrastructure Analytics Advisor system that uses a two-host configuration. 142 Upgrading Infrastructure Analytics Advisor environment

143 Related topics Verifying the yum/rpm dependency packages on page 44 Upgrade the Infrastructure Analytics Advisor server and the Data Center Analytics server on a Linux host on page 148 Upgrading the Analytics probe server on page 153 Upgrading the RAID Agent on page 156 Upgrading the Data Center Analytics server Windows-based probe on page 157 Upgrading the Configuration Manager REST API on page 157 Postupgrade guidelines on page 157 Stopping the Infrastructure Analytics Advisor server services on page 189 Stopping the Data Center Analytics server or Analytics probe server services on page 190 Stopping the RAID Agent services on page 192 Performing a backup of Infrastructure Analytics Advisor on page 209 Upgrading Infrastructure Analytics Advisor environment 143

144 Upgrade workflow for a three-host configuration For a three-host configuration where Infrastructure Analytics Advisor server, Data Center Analytics server, and Analytics probe server are all installed on different hosts, run the installer to upgrade the following components: Infrastructure Analytics Advisor server Data Center Analytics server Analytics probe server RAID Agent Note: The following notes apply when using Tuning Manager - Agent for RAID: You do not need to upgrade RAID Agent. Check whether relationship with the upgraded version of Infrastructure Analytics Advisor is supported for the current version of Tuning Manager - Agent for RAID. If relationship is not supported, upgrade Tuning Manager - Agent for RAID. For the upgrade procedure, see the Hitachi Command Suite Tuning Manager Installation Guide. The following figure shows the sequence for upgrading an Infrastructure Analytics Advisor system that uses a three-host configuration. 144 Upgrading Infrastructure Analytics Advisor environment

145 Related topics Verifying the yum/rpm dependency packages on page 44 Upgrade the Infrastructure Analytics Advisor server and the Data Center Analytics server on a Linux host on page 148 Upgrading the Analytics probe server on page 153 Upgrading the RAID Agent on page 156 Upgrading the Infrastructure Analytics Advisor server on a Windows host on page 152 Upgrading the Data Center Analytics server Windows-based probe on page 157 Upgrading the Configuration Manager REST API on page 157 Postupgrade guidelines on page 157 Stopping the Infrastructure Analytics Advisor server services on page 189 Upgrading Infrastructure Analytics Advisor environment 145

146 Stopping the Data Center Analytics server or Analytics probe server services on page 190 Stopping the RAID Agent services on page 192 Performing a backup of Infrastructure Analytics Advisor on page 209 Verifying the yum/rpm dependency packages Before installing or upgrading the Infrastructure Analytics Advisor server, Data Center Analytics server, or Analytics probe server, check whether all of the yum/rpm dependency packages required for each component are installed. If some packages are missing, you need to install them as an additional step. You can obtain the yum/rpm dependency packages from the Linux OS media or the distribution website, such as for Red Hat Enterprise Linux. Prerequisite packages The following table lists the packages required to run each component. Component name Yum/rpm dependencies Notes Infrastructure Analytics Advisor server tcsh net-tools - Data Center Analytics server java openjdk-devel (update 91 or later) expect parted openssl-devel nss or higher gcc unzip perl perl-cpan perl-xml-simple expat-devel sysstat zip bc Analytics probe server perl perl-cpan perl-digest-md5 perl-xml-simple gcc java openjdk-devel (update 91 or later) samba expect openssl-devel ftp unzip wget glibc.i686 The package nss may not be included in the Linux OS media of certain versions. Obtain this package from the Linux OS media for version 6.8 or later, or from the distribution website. Regarding the package perl- XML-Simple, dependencies exist only in the following OSs: Red Hat Enterprise Linux 7.0 or later Oracle Linux 7.0 or later If the environment you are using already has the libstdc++ package installed, x86_64 (the 64-bit library) and i686 (the 32- bit compatibility library) packages might be different versions. Therefore, installation of libstdc++.i686 might fail with an error message such as the following: Protected multilib versions: libstdc++xx.xx.xx-xx.xx.el6.i686!= 146 Upgrading Infrastructure Analytics Advisor environment

147 Component name Yum/rpm dependencies Notes 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 bc libstdc++-yy.yy.yyyy.yy.el6.x86_64 If this happens, update x86_64 (the 64-bit library), and then retry the installation of libstdc+ +.i686: yum update libstdc++.x86_64 The package nss may not be included in the Linux OS media of certain versions. Obtain this package from the Linux OS media for version 6.8 or later, or from the distribution website. Regarding the packages perl- Digest-MD5 and perl-xml- Simple, dependencies exist only in the following OSs: Red Hat Enterprise Linux 7.0 or later Oracle Linux 7.0 or later The following example shows how to install the package by using the Linux OS media. Change the values that you need to specify during installation according to the environment you are using. Procedure 1. Mount the Linux OS media and obtain the yum/rpm dependency packages: mkdir /media/osimage mount /dev/cdrom /media/osimage 2. Configure the yum repository: touch /etc/yum.repos.d/osimage.repo echo [dvd]>>/etc/yum.repos.d/osimage.repo echo name=dvd>>/etc/yum.repos.d/osimage.repo echo baseurl=file:///media/osimage/>>/etc/yum.repos.d/ OSImage.repo echo gpgcheck=0>>/etc/yum.repos.d/osimage.repo echo enabled=1>>/etc/yum.repos.d/osimage.repo 3. Run the yum command to install the dependency packages: yum install package-to-be-installed Example: yum install java openjdk-devel sysstat zip Upgrading Infrastructure Analytics Advisor environment 147

148 4. Unmount the Linux OS media: umount /media/osimage/ rm /etc/yum.repos.d/osimage.repo Upgrade the Infrastructure Analytics Advisor server and the Data Center Analytics server on a Linux host You can upgrade the Infrastructure Analytics Advisor server and the Data Center Analytics server at a time by using the installer (analytics_install.sh). If you are installing only one of these components, also refer to this section. The upgrade procedure varies depending on whether the version of Infrastructure Analytics Advisor to be upgraded is or Before you begin Upgrade each component in the order described in the upgrade workflow. Caution: Before upgrading, you must save the user-imported certificate onto the host where Data Center Analytics server is installed. This certificate prevents the certificate warning message when accessing the Data Center Analytics server GUI. Saving the user-imported certificate 1. Log on to the host on which Data Center Analytics server is installed using an SSH client. 2. Stop the crond service: service crond stop 3. Stop the megha service: /usr/local/megha/bin/megha-jetty.sh stop 4. Confirm the stopped status of megha service: /usr/local/megha/bin/megha-jetty.sh status 5. Back up the keystore files to /tmp using the following commands: cp /usr/local/megha/jetty/etc/keystore /tmp cp /usr/local/megha/jetty/etc/jetty-ssl.xml /tmp cp /usr/local/megha/jetty/etc/keystore.pkf /tmp 6. Start the megha service: /usr/local/megha/bin/megha-jetty.sh start 7. Start the crond service: service crond start 148 Upgrading Infrastructure Analytics Advisor environment

149 Upgrading from Infrastructure Analytics Advisor system or a later version 1. Log on to the host where the Infrastructure Analytics Advisor server and the Data Center Analytics server are installed. 2. Stop the security monitoring software, antivirus software, and process monitoring software. 3. Mount the Infrastructure Analytics Advisor installation media and copy the directories and files in the ANALYTICS directory from the installation media to a directory on the Linux host: mkdir /media/hiaaimage mount /dev/cdrom /media/hiaaimage cp -r /media/hiaaimage/analytics /root/analytics 4. Run the following command as a root user: cd /root/analytics sh./analytics_install.sh VUP Output example: Do you want to install the Data Center Analytics server? (y/n) [n]: y Do you want to install the Infrastructure Analytics Advisor server? (y/n) [n]: y [Confirmation] Installation Product (1) Data Center Analytics server (2) Infrastructure Analytics Advisor server Do you want to install the server listed above? (y/n) [n]: y ============================================================ Installation of the Data Center Analytics server ============================================================ [INFO] Installation of the Data Center Analytics server started. [INFO] Installing CPAN library [ 1/ 4] Module::Build [INFO] Installing CPAN library [ 2/ 4] YAML [INFO] Installing CPAN library [ 3/ 4] XML::Simple [INFO] Installing CPAN library [ 4/ 4] Log::Log4perl [INFO] Stopping crond service. [INFO] Crond is stopped. [INFO] Stopping the Data Center Analytics server service... [INFO] The Data Center Analytics server service stopped. [INFO] Deploying files... [INFO] File deployment is complete. [INFO] Applying environmental settings... [INFO] Starting crond service. [INFO] Crond is running. [INFO] Starting the Data Center Analytics server service... [INFO] The Data Center Analytics server service started. Upgrading Infrastructure Analytics Advisor environment 149

150 [INFO] Environment settings have been applied. [INFO] Installation of the Data Center Analytics server finished successfully. ============================================================ Installation of the Infrastructure Analytics Advisor server ============================================================ [INFO] Installation of the Infrastructure Analytics Advisor server started. The common component is already installed. To install the Infrastructure Analytics Advisor server, the common component service must be stopped. Do you want to stop the common component service? (y/n) [n]: y Do you want to continue the installation? (y/n) [n]: y [INFO] Deploying files... [INFO] File deployment is complete. [INFO] Installation of the common component started. [INFO] Installation of the common component finished successfully. [INFO] Restarting the common component service. [INFO] The common component service restarted successfully. [INFO] Environment settings have been applied. [INFO] Installation of the Infrastructure Analytics Advisor server finished successfully. Upgrading from Infrastructure Analytics Advisor system version To upgrade Infrastructure Analytics Advisor system from version 2.0.0, you must execute the rpm file before executing analytics_install.sh. 1. Log on to the host where the Data Center Analytics server is installed. 2. Stop the security monitoring software, antivirus software, and process monitoring software. 3. Mount the Infrastructure Analytics Advisor installation media and copy the directories and files from the installation media to a directory on the Linux host: mkdir /media/hiaaimage mount /dev/cdrom /media/hiaaimage cp -r /media/hiaaimage/patch/dca/v6.1 /root/analytics 4. Execute the following command as the root user: cd /root/analytics/v6.1 rpm -U hdca-server-6.1-xxxxxxxx.x86_64.rpm 5. Execute the following script: sh /usr/local/megha_installer/upgrade.sh 150 Upgrading Infrastructure Analytics Advisor environment

151 6. Copy the directories and files in the ANALYTICS directory from the installation media to a directory on the Linux host: cp -r /media/hiaaimage/analytics /root/analytics 7. Run the following command as a root user: cd /root/analytics sh./analytics_install.sh VUP Output example: Do you want to install the Data Center Analytics server? (y/n) [n]: y Do you want to install the Infrastructure Analytics Advisor server? (y/n) [n]: y [Confirmation] Installation Product (1) Data Center Analytics server (2) Infrastructure Analytics Advisor server Do you want to install the server listed above? (y/n) [n]: y ============================================================ Installation of the Data Center Analytics server ============================================================ [INFO] Installation of the Data Center Analytics server started. [INFO] Installing CPAN library [ 1/ 4] Module::Build [INFO] Installing CPAN library [ 2/ 4] YAML [INFO] Installing CPAN library [ 3/ 4] XML::Simple [INFO] Installing CPAN library [ 4/ 4] Log::Log4perl [INFO] Stopping crond service. [INFO] Crond is stopped. [INFO] Stopping the Data Center Analytics server service... [INFO] The Data Center Analytics server service stopped. [INFO] Deploying files... [INFO] File deployment is complete. [INFO] Applying environmental settings... [INFO] Starting crond service. [INFO] Crond is running. [INFO] Starting the Data Center Analytics server service... [INFO] The Data Center Analytics server service started. [INFO] Environment settings have been applied. [INFO] Installation of the Data Center Analytics server finished successfully. ============================================================ Installation of the Infrastructure Analytics Advisor server ============================================================ [INFO] Installation of the Infrastructure Analytics Advisor Upgrading Infrastructure Analytics Advisor environment 151

152 server started. The common component is already installed. To install the Infrastructure Analytics Advisor server, the common component service must be stopped. Do you want to stop the common component service? (y/n) [n]: y Do you want to continue the installation? (y/n) [n]: y [INFO] Deploying files... [INFO] File deployment is complete. [INFO] Installation of the common component started. [INFO] Installation of the common component finished successfully. [INFO] Restarting the common component service. [INFO] The common component service restarted successfully. [INFO] Environment settings have been applied. [INFO] Installation of the Infrastructure Analytics Advisor server finished successfully. Note: If you upgrade Data Center Analytics server in an environment where Oracle Linux 7.0 is used, warning messages are displayed for all files. Ignore these messages. Related topics Upgrade workflow for a two-host configuration on page 142 Upgrade workflow for a three-host configuration on page 144 Starting the Data Center Analytics server or Analytics probe server services on page 190 Stopping the Data Center Analytics server or Analytics probe server services on page 190 Upgrading the Infrastructure Analytics Advisor server on a Windows host Upgrade the Infrastructure Analytics Advisor server on a Windows host using the installation media. Before you begin Upgrade each component in the order described in the upgrade workflow. Procedure 1. Log on to the Infrastructure Analytics Advisor server as a user with administrator permissions. 2. Stop the security monitoring software, antivirus software, and process monitoring software. 152 Upgrading Infrastructure Analytics Advisor environment

153 3. Run ANALYTICS.msi on the installation media to start Infrastructure Analytics Advisor server the installer. Follow the on-screen prompts and specify the required information. You can specify, as an option, whether to back up the data before performing the upgrade (best practice). This option is yes by default. Related topics Upgrade workflow for a two-host configuration on page 142 Upgrade workflow for a three-host configuration on page 144 Upgrading the Analytics probe server You must save the user imported certificate before you upgrade the Analytics probe server. Before you begin Upgrade each component in the order described in the upgrade workflow. Note: Before upgrading, you must save the user-imported certificate onto the host where Analytics probe server is installed. This certificate prevents the certificate warning message while accessing the server and probe GUI. Saving the user-imported certificate 1. Log on to the host on which Analytics probe server is installed using an SSH client. 2. Stop the crond service: service crond stop 3. Stop the megha service: /usr/local/megha/bin/megha-jetty.sh stop 4. Confirm the stopped status of megha service: /usr/local/megha/bin/megha-jetty.sh status 5. Back up the keystore files to /tmp using the following commands: cp /usr/local/megha/jetty/etc/keystore /tmp cp /usr/local/megha/jetty/etc/jetty-ssl.xml /tmp cp /usr/local/megha/jetty/etc/keystore.pkf /tmp 6. Start the megha service: /usr/local/megha/bin/megha-jetty.sh start Upgrading Infrastructure Analytics Advisor environment 153

154 7. Start the crond service: service crond start Upgrading from Infrastructure Analytics Advisor system or a later version 1. Log on to the host where the Analytics probe server is installed. 2. Stop the security monitoring software, antivirus software, and process monitoring software. 3. Mount the Infrastructure Analytics Advisor installation media and copy the directories and files in the DCAPROBE directory from the installation media to a directory on the Linux host: mkdir /media/hiaaimage mount /dev/cdrom /media/hiaaimage cp -r /media/hiaaimage/dcaprobe /root/dcaprobe 4. Run the following command as a root user: cd /root/dcaprobe sh./dcaprobe_install.sh VUP Output example: [INFO] Installation of the Analytics probe servers started. [INFO] Installing CPAN library [ 1/ 1] XML::Simple [INFO] Installation of the Analytics probe server started. [INFO] Stopping crond service. [INFO] Crond is stopped. [INFO] Stopping the Data Center Analytics server service... [INFO] The Data Center Analytics server service stopped. [INFO] Deploying files... [INFO] File deployment is complete. [INFO] Applying environmental settings... [INFO] Environment settings have been applied. [INFO] Starting crond service. [INFO] Crond is running. [INFO] Starting the Data Center Analytics server service... [INFO] The Data Center Analytics server service started. [INFO] Installation of the Analytics probe server finished successfully. [INFO] Installation of the Analytics probe servers finished successfully. Upgrading from Infrastructure Analytics Advisor system version To upgrade Infrastructure Analytics Advisor system from version 2.0.0, you must execute the rpm file before executing dcaprobe_install.sh. 1. Log on to the host on which the Analytics probe server is installed. 2. Stop the security monitoring software, antivirus software, and process monitoring software. 154 Upgrading Infrastructure Analytics Advisor environment

155 3. Mount the Infrastructure Analytics Advisor installation media and copy the directories and files from the installation media to a directory on the Linux host: mkdir /media/hiaaimage mount /dev/cdrom /media/hiaaimage cp -r /media/hiaaimage/patch/dcaprobe/v6.1 /root/analytics 4. Execute the following command as the root user: cd /root/analytics/v6.1 rpm -U hdca-probe-6.1-xxxxxxxx.x86_64.rpm 5. Execute the following script: sh /usr/local/megha_installer/upgrade.sh 6. Copy the directories and files in the DCAPROBE directory from the installation media to a directory on the Linux host: cp -r /media/hiaaimage/dcaprobe /root/dcaprobe 7. Run the following command as a root user: cd /root/dcaprobe sh./dcaprobe_install.sh VUP Output example: [INFO] Installation of the Analytics probe servers started. [INFO] Installing CPAN library [ 1/ 1] XML::Simple [INFO] Installation of the Analytics probe server started. [INFO] Stopping crond service. [INFO] Crond is stopped. [INFO] Stopping the Data Center Analytics server service... [INFO] The Data Center Analytics server service stopped. [INFO] Deploying files... [INFO] File deployment is complete. [INFO] Applying environmental settings... [INFO] Environment settings have been applied. [INFO] Starting crond service. [INFO] Crond is running. [INFO] Starting the Data Center Analytics server service... [INFO] The Data Center Analytics server service started. [INFO] Installation of the Analytics probe server finished successfully. [INFO] Installation of the Analytics probe servers finished successfully. Note: If you upgrade the Analytics probe server in an environment where Oracle Linux 7.0 is used, warning messages are displayed for all files. Ignore these messages. Related topics Upgrade workflow for a two-host configuration on page 142 Upgrading Infrastructure Analytics Advisor environment 155

156 Upgrade workflow for a three-host configuration on page 144 Starting the Data Center Analytics server or Analytics probe server services on page 190 Stopping the Data Center Analytics server or Analytics probe server services on page 190 Upgrading the RAID Agent Upgrade the RAID agent that is installed with the Analytics probe server. Note: This procedure is applicable for RAID Agent installed with Infrastructure Analytics Advisor. If you are using Tuning Manager - Agent for RAID, see Hitachi Command Suite Tuning Manager Installation Guide. Before you begin Upgrade each component in the order described in the upgrade workflow. Procedure 1. Log on to the host where the RAID Agent is installed. 2. Stop the security monitoring software, antivirus software, and process monitoring software. 3. Mount the Infrastructure Analytics Advisor installation media and copy the directories and files in the DCAPROBE directory from the installation media to a directory on the Linux host: mkdir /media/hiaaimage mount /dev/cdrom /media/hiaaimage cp -r /media/hiaaimage/dcaprobe /root/dcaprobe 4. Run the following command as a root user: cd /root/dcaprobe/ sh./agent_update.sh The following shows an example of output that confirms a successful upgrade of the RAID Agent. [INFO] Applying environmental settings... [INFO] Stopping the RAID Agent service... [INFO] The RAID Agent service has stopped. [INFO] Environment settings have been applied. [INFO] Starting the RAID Agent service... [INFO] The RAID Agent service has started. [INFO] Update Agent finished successfully. Related topics Upgrade workflow for a two-host configuration on page 142 Upgrade workflow for a three-host configuration on page Upgrading Infrastructure Analytics Advisor environment

157 Upgrading the Data Center Analytics server Windows-based probe Upgrade the Windows-based probe using the DCA_Windows_Probe.exe command on the installation media. Procedure 1. Log on to the host where Windows-based probe is to be installed as a user with administrator permissions. 2. Stop the security monitoring software, antivirus software, and process monitoring software. 3. Run DCA_Windows_Probe.exe on the installation media, and follow the prompts to specify required information to finish installation. Upgrading the Configuration Manager REST API You can upgrade the Configuration Manager REST API using the upgrade installer from the Infrastructure Analytics Advisor installation media. Procedure 1. Check the path of the database backup destination. Specify this information if you want to obtain a backup during an upgrade installation. 2. Copy the directories and files in the CONFMANAGER directory on the installation media to a directory on the Linux host. 3. Use the sh command to run the installer. sh./install.sh 4. Follow the on-screen prompts and specify the required information to finish installation. Related topics Configuration Manager REST API requirements on page 29 Postupgrade guidelines After a successful upgrade, certain custom settings can be reset or items displayed incorrectly in the Infrastructure Analytics Advisor web user interface. Check the following: Upgrading Infrastructure Analytics Advisor environment 157

158 If any tables do not display any content or displays data incorrectly, select File > Clear Settings, and then click OK to clear the settings saved in the browser. This procedure will also clear the following information: Table configuration information (column settings, column widths, column sorting status, filtering status) History of search keywords If you upgrade the Infrastructure Analytics Advisor system from version or earlier, the dashboard settings return to their default values. 158 Upgrading Infrastructure Analytics Advisor environment

159 10 Configuring secure communications You can configure secure communications. About security settings Workflow for configuring secure communications Configuring an SSL server (Infrastructure Analytics Advisor server) Configuring SSL servers (Data Center Analytics server and Analytics probe server) Configuring an SSL server (Automation Director) Configuring secure communications 159

160 About security settings In Infrastructure Analytics Advisor, you can use SSL and SSH to ensure secure network communications. In SSL and SSH communications, communication routes are encrypted to prevent information leakage and detect any data manipulation during transfer. You can further enhance security using authentication. The following shows the security communication routes for Infrastructure Analytics Advisor. The following shows the security communication routes that can be used in Infrastructure Analytics Advisor and the supported protocols for each route that is used. Note that the number in the table corresponds with the number in the figure. Route SSL server (program) SSL client Protocol 1 Infrastructure Analytics Advisor server Web client HTTP HTTPS 2 Data Center Analytics server Web client HTTPS * 3 Analytics probe server Web client HTTPS * 4 Data Center Analytics server Infrastructure Analytics Advisor server 5 Data Center Analytics server Analytics probe server FTP HTTPS * FTPS 160 Configuring secure communications

161 Route SSL server (program) SSL client Protocol HTTPS SFTP 6 Data Center Analytics server Windows host FTP HTTPS 7 Automation Director Infrastructure Analytics Advisor server 8 Configuration Manager REST API *: SSL communication is set by default. Automation Director HTTP HTTPS HTTP HTTPS If you use a certificate issued by a trusted certificate authority, use the information in this module to enhance security. Note: To use Infrastructure Analytics Advisor with security settings enabled, the server certificate must be valid. If the server certificate has expired, you will not be able to connect to Infrastructure Analytics Advisor using a secure connection. For security settings for communication route 8, see the Hitachi Command Suite Configuration Manager REST API Reference Guide. Workflow for configuring secure communications The following figure describes the workflow for configuring secure communication in the Infrastructure Analytics Advisor environment. Configuring secure communications 161

162 Configuration workflow for secure communication between the Infrastructure Analytics Advisor server and the web client Configuration workflow for secure communication between the Data Center Analytics server and the web client 162 Configuring secure communications

163 Configuration workflow for secure communication between the Analytics probe server and the web client Configuring secure communications 163

164 Configuration workflow for secure communication between the Data Center Analytics server and the Infrastructure Analytics Advisor server 164 Configuring secure communications

165 Configuration workflow for secure communication between the Automation Director and Infrastructure Analytics Advisor server Related topics Logging on to Infrastructure Analytics Advisor server on page 66 Creating a private key and a certificate signing request for Infrastructure Analytics Advisor server on page 166 Applying for a server certificate for Infrastructure Analytics Advisor server from the certificate authority on page 166 Enabling SSL communication for the Infrastructure Analytics Advisor server on page 167 Applying self-signed certificates to the Data Center Analytics server on page 171 Exporting a self-signed certificate for the Data Center Analytics server on page 174 Importing a certificate to the truststore file for the Infrastructure Analytics Advisor server (Data Center Analytics server) on page 174 Applying server certificates to the Data Center Analytics server and the Analytics probe server on page 176 Configuring secure communications 165