Hitachi Infrastructure Analytics Advisor

Transcription

1 Hitachi Infrastructure Analytics Advisor Installation and Configuration Guide MK-96HIAA November 2016

2 2016 Hitachi, Ltd. All rights reserved. No part of this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical, including 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 option Infrastructure Analytics Advisor installation and configuration workflow...18 Default installation location System requirements Infrastructure Analytics Advisor requirements...24 Data Center Analytics server requirements...24 Analytics probe server requirements Configuration Manager REST API requirements VMware vsphere Client requirements...28 Browser requirements Management target requirements Installation with virtual appliances Installing Infrastructure Analytics Advisor server and Data Center Analytics server on VMware vsphere Client...34 Preparing for installation Installation

4 Installing Analytics probe server on VMware vsphere Client...35 Preparing for installation Installation...36 Initial setup of the guest OS or VMs Installation on a Linux host...41 Installing Infrastructure Analytics Advisor server and Data Center Analytics server on a Linux host Preparing for installation Installation...44 Installing Analytics probe server on a Linux host Preparing for installation Installation Installation of Infrastructure Analytics Advisor server on Windows...55 Installing Infrastructure Analytics Advisor server on a Windows host...56 Preparing for installation 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...63 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...64 Configuring initial settings for limiting the IO activity of Hitachi storage resources...65 Setting up an environment for limiting the IO activity of resources Setting up a connection with Hitachi Automation Director Adding probes to Analytics probe server Setting up the Hitachi Enterprise Storage probe...72 Verify the connection between host and monitoring targets Creating an instance environment...75 Adding Hitachi Enterprise Storage probe...77 Deleting an instance environment Starting and stopping RAID Agent services Adding Hitachi Adaptable Modular Storage (AMS) probe...82 Adding Hitachi NAS probe...83 Adding VMware probe Adding Brocade Network Advisor probe Adding Cisco DCNM probe Initial setup after adding a probe Installing Data Center Analytics server Windows-based probe Data collection methods Installing the Windows-based probe

5 Configuring Data Center Analytics Windows-based probe Configuring the collection method...93 Configuring the FTP or HTTPS server Starting the Windows-based probe service Initial setup after adding a probe Upgrading Infrastructure Analytics Advisor environment Upgrade the Infrastructure Analytics Advisor system Upgrade the Data Center Analytics server Upgrade the Analytics probe server Upgrade the RAID Agent Upgrade the Infrastructure Analytics Advisor server Upgrade the Data Center Analytics server Windows-based probe 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 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 Changing the SSL port number between the Infrastructure Analytics Advisor server and a web client Deleting a certificate from the truststore for Infrastructure Analytics Advisor server Changing Infrastructure Analytics Advisor system settings Starting and stopping the Infrastructure Analytics Advisor service Starting the Infrastructure Analytics Advisor server service Stopping the Infrastructure Analytics Advisor server service Starting the Data Center Analytics server or Analytics probe server service Stopping the Data Center Analytics server or Analytics probe server service 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

6 Changing the port number used between Infrastructure Analytics Advisor server and the web browser 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 Changing the format of output by Infrastructure Analytics Advisor server to syslog 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 Backing up and restoring Infrastructure Analytics Advisor Stopping services before a back up 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 backed up Restoring Infrastructure Analytics Advisor server settings information Restoring the settings information and database of Data Center Analytics server. 154 Restoring Analytics probe server settings information 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 from a Windows host Removing Infrastructure Analytics Advisor server and Data Center Analytics server 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 be connected to Data Center Analytics server A Infrastructure Analytics Advisor CLI commands List of Commands Command usage notes Usable characters for command arguments backupsystem encryptpassword hcmds64fwcancel

7 hcmds64getlogs hcmds64intg hcmds64srv hcmds64ssltool hcmds64unlockaccount reloadtemplate restoresystem B Infrastructure Analytics Advisor server services C User-specified properties file (config_user.properties) D Default collection and data export interval for probes E Configuring initial settings for limiting IO activity of Hitachi storage resources (using a script) Creating a script file for limiting the IO activity of resources by using IO Control Command template definition files formats Index

8 8

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 authorized service providers. 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 2.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 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 Automation Director API Reference Guide, MK-92HC217 Hitachi Command Suite Configuration Manager REST API Reference Guide, MK-92HC Preface

11 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. Caution Warns the user of adverse conditions and/or consequences (for example, disruptive operations, data loss, or a system crash). Preface 11

12 Icon Label Description 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) 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 most current documentation, including important updates that may have been made after the release of the product. 12 Preface

13 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 This section provides an overview of the Infrastructure Analytics Advisor installation. Infrastructure Analytics Advisor overview Infrastructure Analytics Advisor system configuration Installation option Infrastructure Analytics Advisor installation and configuration workflow Default installation location 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: Hitachi storage systems Brocade and Cisco Fibre channel switches Microsoft and VMware hypervisors 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 makes it available to Infrastructure Analytics Advisor server for analyzing, troubleshooting, and reporting. Analytics probe server: This server enables you to collect performance and configuration data from a target. Related topics Infrastructure Analytics Advisor installation and configuration workflow on page 18 Infrastructure Analytics Advisor system configuration This section describes the system configuration of Infrastructure Analytics Advisor. The following figure indicates the system configuration when each components of Infrastructure Analytics Advisor is installed to a different host: 16 Overview

17 The Data Center Analytics server and Analytics probe server must be installed on separate hosts. RAID Agent is installed with the Analytics probe server. The Infrastructure Analytics Advisor server and Data Center Analytics server can also be installed on the same host. The REST server is a program for using the Configuration Manager REST API. If you want to limit the IO activity of resources by using the IO Control Settings function of Infrastructure Analytics Advisor, install Hitachi Automation Director and the REST server on a host of your choice. By using a virtual appliance, a virtual machine with both the Analytics probe server and REST server installed can be configured in a single deployment. In addition, the Analytics probe server cannot be installed on a host where the following products are installed: Hitachi Command Suite Tuning Manager Agent components for Hitachi Command Suite Tuning Manager Installation option Choose a method for installing each Infrastructure Analytics Advisor component based on the configuration of the system you want to create. To install the Infrastructure Analytics Advisor server and the Data Center Analytics server on the same host, use virtual appliance installation or the installer. You can install the Infrastructure Analytics Advisor server and the Data Center Analytics server at the same time. To install the Infrastructure Analytics Advisor server and the Data Center Analytics server on different hosts, use the installer relevant to the OS of the target installation host. Overview 17

18 The following table shows which installation methods can be used for each type of Infrastructure Analytics Advisor system configuration. Installation method System configuration Infrastructure Analytics Advisor server Data Center Analytics server Analytics probe server #1 Infrastructure Analytics Advisor server and Data Center Analytics server are installed on the same host Infrastructure Analytics Advisor server and Data Center Analytics server are installed on different hosts Deploy the virtual appliance. Run the installer. (Linux) Run the installer. (Windows or Linux) Run the installer. (Linux) Deploy the virtual appliance. #2 Run the installer. (Linux) Run the installer. (Linux) #1: Install Windows-based probes by running a Windows-based dedicated installer. Add other probes to the Analytics probe server as needed. #2: The Configuration Manager REST API (REST server) is also installed with the Analytics probe server installation. Infrastructure Analytics Advisor installation and configuration workflow This section describes the procedure for installing and configuring Infrastructure Analytics Advisor. The workflow from installation to setup differs according to the installation option. The following figure shows the workflow for deploying a virtual appliance and installing Infrastructure Analytics Advisor. 18 Overview

19 The following figure shows the workflow for installing Infrastructure Analytics Advisor using the installer. Overview 19

20 Configuring Infrastructure Analytics Advisor in secure mode is optional. Communication between the web client and the Data Center Analytics server or Analytics probe server, and communication between the Infrastructure Analytics Advisor server and Data Center Analytics server is performed securely by using a self-signed certificate that is installed by default so that no additional configuration is required. 20 Overview

21 However, if you want to strengthen security for exchange of data between various program in Infrastructure Analytics Advisor, you must do some tasks on the servers to generate certificates and have them verified by a certificate-signing authority before you apply them in your environment. In addition, if you want to use the IO Control Settings function for Infrastructure Analytics Advisor, you must install Hitachi Automation Director and the Configuration Manager REST API, and perform initial settings for limiting the IO activity of resources. Default installation location The default installation location for each component is as shown below. Program 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 /data /home /opt/hicommand Overview 21

22 22 Overview

23 2 System requirements This section describes the Infrastructure Analytics Advisor system requirements. Infrastructure Analytics Advisor requirements Data Center Analytics server requirements Analytics probe server requirements Configuration Manager REST API requirements VMware vsphere Client requirements Browser requirements Management target requirements System requirements 23

24 Infrastructure Analytics Advisor requirements This section describes the Infrastructure Analytics Advisor server requirements. Table 1 Operating system requirements (Windows) OS name OS version 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 Table 2 Operating system requirements (Linux) Supported OS Yum/rpm dependencies Architecture Red Hat Enterprise Linux tcsh x64 Oracle Enterprise Linux (Unbreakable Enterprise Kernel) Table 3 Hardware requirements (Windows/Linux) Prerequisites Minimum Recommended Processor Dual-Core processor Quad-Core processor Memory 8 GB 16 GB minimum Disk space 50 GB 100 GB minimum Note: 1. Server core is not supported. 2. Server core and Minimal Server Interface are not supported. Data Center Analytics server requirements This section describes the Data Center Analytics server requirements. 24 System requirements

25 For installation using RPM Package Manager (RPM) Table 4 Operating system requirements Supported OS Yum/rpm dependencies Architecture Red Hat Enterprise Linux Oracle Enterprise Linux (Unbreakable Enterprise Kernel) - perl - java openjdk - expect - parted - openssl-devel - xfsprogs - nss or higher x64 Table 5 Hardware requirements Prerequisites Minimum Recommended (Best practice #1 ) Processor Dual-Core processor Quad-Core processor Memory 8 GB 16 GB Disk space #2 150 GB 600 GB Note: #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 dcaserver_install.sh. You must prepare a physical disk for installing the Data Center Analytics server on physical machines. Table 6 Desktop prerequisites Source IP address Target IP address Default port Protocol User Desktop IP address of the Data Center Analytics server 8443 TCP Note: The memory requirement and disk capacity vary depending on the number of managed resources and frequency of performance data collection. For example, if you monitor a storage system that has a large number of volumes, the performance data from these volumes can take up a lot of disk System requirements 25

26 space in the database. Also, if you increase the frequency of performance data collection, the required disk space increases. Analytics probe server requirements This section describes the Analytics probe server requirements. Table 7 Desktop requirements Source IP address User Desktop Target IP address IP address of the Analytics probe server Default port Protocol Notes 8443 TCP 22 TCP Required for connecting to the Analytics probe server through the SSH client Table 8 Probe port and firewall requirements Probe name Collection method Source IP address Target IP address Default port Protocol Storage systems AMS SNM2API Analytics probe server Hitachi Enterprise Storage RAID Agent Hitachi Device Manager API Analytics probe server Analytics probe server HNAS RUSC/CLI Analytics probe server AMS Controller 2000 TCP RAID Agent Server Hitachi Device Manager Server HTTP 2001 HTTP 2443 HTTPS HNAS SMU 22 SSH Hypervisors VMware Windows- based(hyper- V) VMware vcenter API Analytics probe server VMware vcenter Server/ VMware ESX Host/VMware ESXi Host 443 TCP WMI Windowsbased Windows- 135 TCP Perfmon probe based host 135 and 445 SCOM SCOM server 5723, 5724, and SCCM SCCM server 1433 FC Switches 26 System requirements

27 Probe name Collection method Source IP address Target IP address Default port Protocol Brocade Network Advisor BNA (REST API) Analytics probe server BNA server 80 HTTP Cisco DCNM DCNM (Web Services) Analytics probe server DCNM Server 80 HTTP 443 HTTPS For installation using RPM Package Manager Table 9 Operating system requirements OS name yum/rpm dependencies CPAN dependencies Architecture Red Hat Enterprise Linux Oracle Enterprise Linux (Unbreakable Enterprise Kernel) perl perl-cpan gcc java openjdk samba expect openssl-devel ftp unzip wget glibc.i686 glibc.x86_64 libstdc++.i686 libstdc++.x86_64 net-tools tcsh libyaml libgcc.x86_64 nsssoftoknfreebl.x86_64 iproute.x86_64 ncurses openssh-clients nss or higher YAML Module::Build IO::Pty Date::Gregorian Date::Calc Log::Log4perl Net::OpenSSH DateTime Log::Dispatch::FileRotat e DateTime::Format::Strpt ime Sys::RunAlone LWP::UserAgent LWP::Protocol::https Time::HiRes x64 Table 10 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 Note: #: 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 System requirements 27

28 space in the database. If you decrease the interval at which to obtain performance information from the managed resources, the volumes occupy more disk space in the database. Configuration Manager REST API requirements This section describes the Configuration Manager REST API requirements. Table 11 Operating system requirements OS name Yum/rpm dependencies Architecture Red Hat Enterprise Linux 6.5(*)-6.7 Oracle Enterprise Linux (Unbreakable Enterprise Kernel) (*) upstart el6_5.3.x86_6 4 or later x64 Table 12 Hardware requirements Prerequisites Minimum Recommended Processor Dual-Core processor Quad-Core processor Memory 2 GB 4 GB minimum Disk space 0.8 GB - VMware vsphere Client requirements This section describes VMware vsphere Client requirements. Infrastructure Analytics Advisor server and Data Center Analytics server Table 13 Guest operating system settings Item OS Settings Oracle Linux 6.8 (Architecture x86_64) Table 14 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 200 GB (Configure as two separate disks.) 28 System requirements

29 Analytics probe server and Configuration Manager Table 15 Guest operating system settings Item Settings OS Oracle Linux 6.8 (Architecture x86_64) Table 16 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 10 GB 110 GB Browser requirements This section describes the supported browsers. Table 17 Browser settings Web browser/other Version Firefox ESR 38 Internet Explorer 11 ESR 45 Chrome for Work Flash Player Latest version of stable channel 21.0 or later (to use custom reports in Data Center Analytics server) Management target requirements This section describes the supported management targets and its requirements. Table 18 Storage systems Storage system series Storage system Microcode /SMU version Analytics probe name Hitachi VSP Hitachi Virtual Storage Platform (VSP) or later Hitachi Enterprise Storage probe 1 HUS VM Hitachi Unified Storage VM (HUS VM) or later System requirements 29

30 Storage system series Storage system Microcode /SMU version Analytics probe name VSP Gx00 Hitachi Virtual Storage Platform G models 2 (VSP G200) or later Hitachi Virtual Storage Platform G400 (VSP G400) Hitachi Virtual Storage Platform G600 (VSP G600) Hitachi Virtual Storage Platform G800 (VSP G800) VSP Fx00 Hitachi Virtual Storage Platform F models 2 (VSP F400) or later Hitachi Virtual Storage Platform F600 (VSP F600) Hitachi Virtual Storage Platform F800 (VSP F800) VSP G Hitachi Virtual Storage Platform G (VSP G1000) or later VSP G Hitachi Virtual Storage Platform G or VSP F Hitachi Virtual Storage Platform F1500 later HUS100 Hitachi Unified Storage 110 (HUS110) or Hitachi Unified Storage 130 (HUS130) later Hitachi Adaptor Modular Storage (AMS) probe Hitachi Unified Storage 150 (HUS150) Hitachi NAS HNAS - HNAS Probe 3 Notes: 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 use of Server Priority Manager to limit IO 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 IO Control Settings in Infrastructure Analytics Advisor, an error might occur. 3. The data collected by the HNAS probe can be viewed in Data Center Analytics server only. Note: To manage additional information about Hitachi storage systems (such as information about storage capacity and hosts), use the Hitachi Device Manager software or later. For IO control settings using Server Priority Manager, use Hitachi Automation Director or later. 30 System requirements

31 Table 19 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 20 Hosts OS name 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 Windows Server 2012 R2 Standard Datacenter Table 21 FC switches Switch name Software Version Analytics Probe name Brocade Cisco Brocade Network Advisor Professional Plus Brocade Network Advisor Enterprise Cisco Data Center Network Manager 12.0 Brocade Network Advisor probe Cisco DCNM Probe System requirements 31

32 32 System requirements

33 3 Installation with virtual appliances This section describes how to install Infrastructure Analytics Advisor server, Data Center Analytics server, and Analytics probe server using virtual appliances. 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 33

34 Installing Infrastructure Analytics Advisor server and Data Center Analytics server on VMware vsphere Client This section describes how to deploy virtual appliances for Infrastructure Analytics Advisor server and Data Center Analytics server on a VMware vsphere Client. 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 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 communication port used for Data Center Analytics server are 8443 (Data Center Analytics server) and (Infrastructure Analytics Advisor server). For more information, review the Infrastructure Analytics Advisor server and the Data Center Analytics server port and firewall 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 and the Data Center Analytics server licenses from your HDS representative. Related topics Infrastructure Analytics Advisor requirements on page 24 Data Center Analytics server requirements on page 24 Installation on page 34 Initial setup of the guest OS or VMs on page 37 Installation This topic describes how to deploy virtual appliances for Infrastructure Analytics Advisor server and Data Center Analytics server. Procedure 1. From a VMware vsphere client, log in to the VMware ESXi server. 2. Deploy the OVA file for Infrastructure Analytics Advisor server and Data Center Analytics server from the installation media for virtual appliances. 34 Installation with virtual appliances

35 From the VMware vsphere client, select File-Deploy OVF Template, and then follow the on-screen instructions. Tip: We recommend selecting 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. 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 37 Installing Analytics probe server on VMware vsphere Client This section describes how to deploy virtual appliances for Analytics probe server using VMware vsphere Client. Preparing for installation Before you start deploying a virtual appliance for Analytics probe server, review the following prerequisites. Prerequisites Review hardware and software requirements Port requirements 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 for communication is For more information, review the Analytics probe server requirements. Installation with virtual appliances 35

36 Prerequisites Review virtual system operations Time zone settings License Description Review the following requirements when you run agents 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 G1000, G1500, VSP F1500, VSP Gx00 models, VSP Fx00 models, Virtual Storage Platform, 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. Related topics Analytics probe server requirements on page 26 Installation on page 36 Initial setup of the guest OS or VMs on page 37 Installation This topic describes how to deploy a virtual appliance for Analytics probe server. Procedure 1. From a VMware vsphere client, log in to the VMware ESXi server. 2. Deploy the OVA file for Analytics probe server from the installation media for virtual appliances. 36 Installation with virtual appliances

37 From the VMware vsphere client, select File > Deploy OVF Template, and then follow the on-screen instructions. Tip: We recommend selecting 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. 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 37 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 in to the guest OS. 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. 2. Run the hvaconfig command that is stored in /opt/hiaa/vmtool. Installation with virtual appliances 37

38 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 procedure in advance to check the time zone values. 1. Run the following command to check the values that can be specified for area: ls -F /usr/share/zoneinfo Of the results output by the command, specify, for area, the name of the directory that includes the time zone you want to specify. 2. Run the following command to check the values that can be specified for location: ls -F /usr/share/zoneinfo/area Of the results output by the command, specify, for location, the name of the file corresponding to the time zone you want to specify. 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 38 Installation with virtual appliances

39 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 command. Next steps Perform the initial setup of Data Center Analytics server or Analytics probe server. Related topics Initial setup of Data Center Analytics server on page 60 Initial setup of Analytics probe server on page 61 Installation with virtual appliances 39

40 40 Installation with virtual appliances

41 4 Installation on a Linux host This section describes how to install components on a Linux host using the installer. 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 41

42 Installing Infrastructure Analytics Advisor server and Data Center Analytics server on a Linux host This section describes how to install Infrastructure Analytics Advisor server and Data Center Analytics server on a Linux host. Refer to this section if you want to install one (but not both) of these programs. Preparing for installation You can install the Infrastructure Analytics Advisor server and the Data Center Analytics server at the same time by using the installer (analytics_install.sh). Alternatively, you can install only one of these two programs. Select the program to be installed based on the configuration of the system you want to create. Table 22 Infrastructure Analytics Advisor serverinstallation prerequisites (Linux) Requirements Review hardware and software requirements Resolve the IP address Time zone settings Install the following yum/rpm dependency packages tcsh Description Review the Infrastructure Analytics Advisor server requirements. Make sure that you meet all the hardware and software requirements. You must define a hosts file or domain name system (DNS) environment so that the IP address can be resolved from the name of each host on which the Infrastructure Analytics Advisor server is installed. Configure the environment so that the IP address can be resolved from the host name using the uname -n command. 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 An example of how to execute the command to install the package is provided below. Change the specified values based on the environment you are using. 1. Mount the Linux OS media disc 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 42 Installation on a Linux host

43 Requirements Description 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 tsch 4. Unmount the Linux OS media: umount /media/osimage/ rm /etc/yum.repos.d/osimage.repo rm /etc/yum.repos.d/osimage.repoage.repo User permission License The root permission is required. Obtain the Infrastructure Analytics Advisor server license from your HDS representative. Table 23 Data Center Analytics server installation prerequisites (Linux) Prerequisites Review hardware and software requirements Prepare an external hard drive as the installation source Install the following yum/rpm dependency packages perl java openjdk openssl-devel expect parted xfsprogs nss Description Review the Data Center Analytics server requirements. Make sure that your site meets all the hardware and software requirements. Prepare an external drive for installing the Data Center Analytics server on a Linux host. For details about disk space requirements for the external drive, see the Data Center Analytics server requirements. Install the yum/rpm dependencies from the Linux OS media or Red Hat Enterprise Linux website. The procedure for installing the yum/rpm dependencies using the Linux OS media disc is as follows: 1. Mount the Linux OS media disc 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 java openjdk openssl-devel perl expect parted nss /media/ OSImage/ScalableFileSystem/ xfsprogs el6.x86_64.rpm Installation on a Linux host 43

44 Prerequisites Description The package xfsprogs el6.x86_64.rpm differs depending on your environment. Specify the package that matches your environment. The package nss may not be included in the Linux OS media of certain versions. Obtain this package from the Linux website or the Linux OS media of version 6.8 or later. 4. Unmount the Linux OS media: umount /media/osimage/ rm /etc/yum.repos.d/osimage.repo Port requirements User permissions Time zone settings Make sure that the ports you specify are available for communication. The default port for communication is For more information, review the Data Center Analytics server port and firewall requirements. The root permission is required. Make sure that the console and clock properties are set to the same time zone. The times and time zones of the following servers must all be synchronized: Infrastructure Analytics Advisor server Data Center Analytics server Analytics probe server License Obtain the Data Center Analytics server license from your HDS representative. Related topics Installation option on page 17 Data Center Analytics server requirements on page 24 Installation on page 44 Installation The procedure for installing Infrastructure Analytics Advisor server and Data Center Analytics server is as follows. Procedure 1. Stop all the programs running on the host (including antivirus programs). 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 44 Installation on a Linux host

45 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. [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 4. You are prompted for a drive and directory to install the Data Center Analytics server. Specify the device name in which to store application data. [sdb]: Specify the directory in which to store application data. File permissions for all files in the top-level directory and below will be changed to 'megha:megha'. [/data]: 5. When prompted, specify 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, Installation on a Linux host 45

46 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. [ ]: 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: [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 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 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) ************************************************************ ************************************************************ 46 Installation on a Linux host

47 ************************************************************ Do you want to continue the installation? (y/n) [n]: y [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. 9. Install the 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]: [Firewall parameter ] 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] The restart of the common component service started. 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. Installation on a Linux host 47

48 [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 60 Initial setup of Infrastructure Analytics Advisor server on page 63 Installing Analytics probe server on a Linux host This section describes how to install Analytics probe server on a Linux host. Preparing for installation Before you begin installation of Analytics probe server on a Linux host, review the following prerequisites. Prerequisites Review hardware and software requirements Install Data Center Analytics server Install the following yum/rpm dependency packages: perl perl-cpan gcc java openjdk samba expect openssl-devel ftp unzip wget glibc.i686 glibc.x86_64 libstdc++.i686 libstdc++.x86_64 net-tools tcsh libyaml libgcc.x86_64 nss-softokn-freebl.x86_64 iproute.x86_64 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 initially setting up the Analytics probe server. You can install the yum/rpm dependencies from the Linux OS media or Red Hat Enterprise Linux website. The procedure for installing the yum/rpm dependencies using the Linux OS media disc is as follows: 1. Mount the Linux OS media disc 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 48 Installation on a Linux host

49 Prerequisites ncurses openssh-clients nss or higher Description 3. Run the yum command to install the dependency packages: yum install perl perl-cpan gcc java openjdk samba expect openssl-devel ftp unzip wget glibc.i686 glibc.x86_64 libstdc+ +.i686 libstdc++.x86_64 net-tools tcsh libyaml libgcc.x86_64 nss-softokn-freebl.x86_64 iproute.x86_64 ncurses openssh-clients nss Note: 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.xxxx. xx.el6.i686!= 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: #update libstdc++.x86_64 yum update libstdc++.x86_64 Note: The package nss may not be included in the Linux OS media of certain versions. Obtain this package from the Linux website or the Linux OS media of version 6.8 or later. 4. Unmount the Linux OS media: umount /media/osimage/ rm /etc/yum.repos.d/osimage.repo Review RAID Agent installation requirements 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 /opt/jp1pc 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 in the /opt or /opt/jp1pc directory is created. 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. Resolve the IP address You must define a hosts file or domain name system (DNS) environment so that the IP address can be resolved from the name of each host on which an agent is installed. Configure Installation on a Linux host 49

50 Prerequisites Description the environment so that the IP address can be resolved from the host name using the uname -n command. 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. Port requirements User permissions Time zone settings License Make sure that the ports you specify are available for communication. The default port for communication is The default port for SSH communication to the Analytics probe server is 22. For more information, review the Analytics probe server requirements. 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 Obtain the Analytics probe server license from your HDS representative. Related topics Analytics probe server requirements on page 26 Installation on page 50 Initial setup of the guest OS or VMs on page 37 Installation The procedure for installing Analytics probe server on a Linux host is as follows: Procedure 1. Stop all the programs running on the host including the antivirus program. 50 Installation on a Linux host

51 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: 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: [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 Installation on a Linux host 51

52 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 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=Twoletter country code for your unit 8. When you are prompted with the following caution message, enter y to continue with the installation. ** CAUTION ** * This installation will change iptables settings. (Listing above) * Installation of the required CPAN libraries may take more than 15 minutes. Do you want to continue the installation? (y/n) [n]: y [INFO] Installing CPAN library [ 1/15] Module::Build [INFO] Installing CPAN library [ 2/15] YAML [INFO] Installing CPAN library [ 3/15] IO::Pty [INFO] Installing CPAN library [ 4/15] Date::Calc [INFO] Installing CPAN library [ 5/15] Net::OpenSSH [INFO] Installing CPAN library [ 6/15] DateTime [INFO] Installing CPAN library [ 7/15] DateTime::Format::Strptime [INFO] Installing CPAN library [ 8/15] Date::Gregorian [INFO] Installing CPAN library [ 9/15] Log::Log4perl [INFO] Installing CPAN library [10/15] Log::Dispatch::FileRotate [INFO] Installing CPAN library [11/15] Sys::RunAlone [INFO] Installing CPAN library [12/15] [INFO] Installing CPAN library [13/15] LWP::UserAgent [INFO] Installing CPAN library [14/15] LWP::Protocol::https [INFO] Installing CPAN library [15/15] Time::HiRes [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. [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. 52 Installation on a Linux host

53 [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 61 Installation on a Linux host 53

54 54 Installation on a Linux host

55 5 Installation of Infrastructure Analytics Advisor server on Windows This section describes how to install Infrastructure Analytics Advisor server on a Windows host by using the installer. Use this installation method to install Infrastructure Analytics Advisor server on a host other than the host on which Data Center Analytics server is installed. Installing Infrastructure Analytics Advisor server on a Windows host Installation of Infrastructure Analytics Advisor server on Windows 55

56 Installing Infrastructure Analytics Advisor server on a Windows host This section describes how to install Infrastructure Analytics Advisor server on a Windows host. Preparing for installation Before you begin installation of Infrastructure Analytics Advisor server on a Windows host, review the following prerequisites. 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 Installation option on page 17 Infrastructure Analytics Advisor requirements on page 24 Installing Analytics probe server on VMware vsphere Client on page 35 Installation on page 56 Installation The procedure for installing Infrastructure Analytics Advisor server on a Windows host is as follows: 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 close all programs, including antivirus programs. 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. 56 Installation of Infrastructure Analytics Advisor server on Windows

57 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. Next steps Perform the initial setup of Infrastructure Analytics Advisor server. Related topics Initial setup of Infrastructure Analytics Advisor server on page 63 Installation of Infrastructure Analytics Advisor server on Windows 57

58 58 Installation of Infrastructure Analytics Advisor server on Windows

59 6 Initial setup after installation This section describes the settings required after installation. 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 IO activity of Hitachi storage resources Initial setup after installation 59

60 Initial setup of Data Center Analytics server This section describes the initial settings for the Data Center Analytics server. Before you begin Check the IP address of the Data Center Analytics server. Obtain the Data Center Analytics server license from your HDS representative. Procedure 1. Enter the Data Center Analytics server URL in your browser: Number 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 a 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 username for the built-in administrator user 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. Create an Infrastructure Analytics Advisor server user account that belongs to the Administrator group on the Data Center Analytics server. For information about how to add accounts, see the Hitachi Infrastructure Analytics Advisor Data Center Analytics User Guide. 60 Initial setup after installation

61 Note: Several accounts are created automatically 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 64 Initial setup of Analytics probe server This section describes the initial settings for the Analytics probe server. Before you begin Check the IP address of the Data Center Analytics server. Check the IP address of the Analytics probe server. Obtain the Analytics probe server license from your HDS representative. Note: Do not change the time zone setting manually after you log on to an SSH client like putty. The default time zone of the Analytics probe server is UTC. Procedure 1. Open your browser, and type the Analytics probe server URL and press Enter 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 register 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 of the user Locale: Analytics probe server is available in two languages US English and Japanese Initial setup after installation 61

62 Group: Select Admin to create an administrator account 6. In the Analytics probe login window, enter the administrator user credentials and click Login. 7. In the Basic Information window, specify the following details, and then click Next. Customer Name: The customer name is displayed in the Basic Information window. Provide the following information and click Next. Administrator Contact Name and the Administrator Contact Technical Contact Name and Technical Contact (Specify the point of contact (administrator) to notify about the technical problems) 8. Make a selection in the Select Time zone window, and then click Next. 9. In the FTP Information window, specify the following details, and then click Next. FTP Method: SFTP Server: Data Center Analytics server IP address Port: Based on the selected FTP method User: meghadata Password: meghadata123 Passive: Select to connect the FTP server in Passive mode (default: Active) Proxy: Select to configure a proxy 10. In the Data Collection duration window, verify the information in your license, and then click Next. 11. From the Probes list, 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 Hitachi Device Manager probe VMware probe 62 Initial setup after installation

63 Cisco DCNM probe Initial setup of Infrastructure Analytics Advisor server This section describes the initial settings for the Infrastructure Analytics Advisor 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 Check whether 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 License. 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. Initial setup after installation 63

64 Related topics Configuring secure communications on page 105 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: Use the specified user 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. 4. Click OK. Result The Data Center Analytics server is connected. Related topics Initial setup of Data Center Analytics server on page 60 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. 64 Initial setup after installation

65 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, and in the dialog box that appears, send a test Confirm that the test arrives, and then click Save Settings. Result The mail server and sender's mail address are configured. Configuring initial settings for limiting the IO activity of Hitachi storage resources This section describes how to configure the initial settings required to limit the IO activity of resources by using the IO Control Settings feature. Setting up an environment for limiting the IO activity of resources You can use the IO Control Settings function of Infrastructure Analytics Advisor to limit the IO activity of resources. To use the IO Control Settings feature, you must use the Server Priority Manager function provided by Hitachi storage systems. To configure Server Priority Manager, you need to set up an environment in advance by using the Configuration Manager REST API and Hitachi Automation Director. For details about each procedure, see the following manuals. Hitachi Command Suite Automation Director User Guide Hitachi Command Suite Automation Director API Reference Guide Hitachi Command Suite Configuration Manager REST API Reference Guide Note: You can also limit the IO activity of resources by using a script file instead of using Hitachi Automation Director. For details, see Appendix E of this guide and the Hitachi Infrastructure Analytics Advisor User Guide. Before you begin Hitachi Automation Director is installed. For installation instructions, see the Hitachi Automation Director Installation and Configuration Guide. The Configuration Manager REST API is installed. For installation instructions, see the Configuration Manager REST API Reference Guide. Initial setup after installation 65

66 Note: The Configuration Manager REST API can be installed from the installation media for Infrastructure Analytics Advisor. The procedure is as follows: 1. Check the path of the installation destination of the Configuration Manager REST API. This information must be specified during installation. 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. Follow the on-screen prompt and specify the required information to finish installation. 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. On the REST server, register the storage system that you want to enable Server Priority Manager settings. Register the storage system information on the REST server so that the Configuration Manager REST API can be used to configure the storage system. Run the request below. Request line: POST protocol://host-name:port-number/ ConfigurationManager/v1/objects/storages You can also run a script to register storage system information. Sample script files are provided with the Analytics probe server. a. Specify REST server information in the following file. /opt/hitachi/analytics/sample/config.sh b. Specify storage system information in the following file. /opt/hitachi/analytics/sample/operate_storage.sh c. Run the script../operate_storage.sh register svpip serialnumber model userid password [issecure] d. In the Script execution result that is displayed, note the value of the storagedeviceid. You need this value in the next step. You can also check the execution result by running the following script:./operate_storage.sh list 66 Initial setup after installation

67 Note: When a VSP G1000 is registered and the SSL communication between the REST server and storage system is enabled, the storage system cannot be registered by other REST servers. For details about the SSL communication settings of the REST server, see the Configuration Manager REST API Reference Guide. 3. Register the storage system in Hitachi Automation Director. Register information about the storage system for which Server Priority Manager settings are to be configured. a. In the Administration tab, select Connection Settings > Web Service Connections. b. Click Add, and then specify the following information: Category: Analytics (recommended) Name: Device number of the storage system obtained in step 2 IPAddress/HostName: IP address or host name of the REST server Protocol: http or https (protocol used by the REST server) Port: Port number of the REST server User ID and Password: User account that has permission to access the LDEVs and ports for which operations are to be performed to set IO control. 4. In Hitachi Automation Director, create a Hitachi 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: We recommend using the user group name "AnalyticsGroup". 5. Import the service templates in Hitachi Automation Director. a. In the Service Templates tab, click Import. b. Click Browse, and then specify AnalyticsServiceTemplate.zip (the downloaded service template). c. Click OK. 6. Create a service group in Hitachi Automation Director. a. In the Administration tab, select Resources and Permissions > Service Groups. b. Click Create, and then specify a name for the service group. Note: We recommend using the service group name "Analytics Service Group". Initial setup after installation 67

68 7. In Hitachi Automation Director, use the service templates to create the Hitachi Automation Director services: One for updating the Server Priority Manager settings (Modify IO Control Settings for Volume) and one for deleting the Server Priority Manager settings (Delete IO Control Settings for Volume), and each service must be created. a. In the Administration tab, select Resources and Permissions > Service Groups. b. Select the service group that was created in step 6. c. In the Services tab, click Create. d. Select the service templates that were imported in step 5, and then click Create Service. e. Specify the information that is required 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 f. Click Save and Close to close the window. 8. In Hitachi Automation Director, assign the user group created in step 4 to the service group created in step 6. a. In the Permissions tab, click Assign. b. Select the user group, and then click Add. c. Select the Submit role, and then click OK. 9. In Hitachi Automation Director, to use the Hitachi Automation Director user account for Infrastructure Analytics Advisor, assign the user account to the user group that was created in step 4. a. In the Permissions tab, select a user group that has the Submit role. b. Click Assign, and then select the Hitachi Automation Director user account that you want to use for Infrastructure Analytics Advisor. c. Click Add, and then click OK. 10. (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 Hitachi 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: 68 Initial setup after installation

69 automation.parameter.servicegroupname: Service group name specified in Hitachi Automation Director automation.parameter.productname: Category name specified in Hitachi Automation Director automation.parameter.servicename.iocontrol.modify: Service name set in Hitachi Automation Director as the name of the service for updating Server Priority Manager settings automation.parameter.servicename.iocontrol.delete: Service name set in Hitachi 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 Hitachi Automation Director. Related topics Setting up a connection with Hitachi Automation Director on page 69 Creating a script file for limiting the IO activity of resources by using IO Control on page 214 Setting up a connection with Hitachi Automation Director Log in to Infrastructure Analytics Advisor, to set up the connection with Hitachi Automation Director. Before you begin Obtain the following information related to Hitachi Automation Director: IP Address/Host Name 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 a connection with Hitachi Automation Director has been established. 4. Click OK. Initial setup after installation 69

70 70 Initial setup after installation

71 7 Adding probes to Analytics probe server You can add one or more probes to collect data from different monitoring targets. Setting up the Hitachi Enterprise Storage probe Adding Hitachi Adaptable Modular Storage (AMS) probe Adding Hitachi NAS probe Adding VMware probe Adding Brocade Network Advisor probe Adding Cisco DCNM probe Initial setup after adding a probe Adding probes to Analytics probe server 71

72 Setting up the Hitachi Enterprise Storage probe You must add the Hitachi Enterprise Storage probe on the Analytics probe server to monitor the Hitachi enterprise storage systems. Verify the connection between host and monitoring targets Review the following information if you are monitoring VSP G1000, G1500, VSP F1500, VSP Gx00 models, VSP Fx00 models, Virtual Storage Platform, or HUS VM. Operation workflow for adding Hitachi Enterprise Storage probe The following figure describes workflow for adding Hitachi Enterprise Storage probes: Configuring Analytics probe server Confirm that RAID Agent and Analytics probe server are installed on the same host. Note that RAID Agent is installed when Analytics probe server is installed. Confirm that the RAID Manager LIB is installed on the RAID Agent host. Note that, in an environment that was created by deploying the OVA file for Analytics probe server, the RAID Manager LIB is already installed. Configuring monitoring targets (storage systems) Verify that a Storage Navigator user account is created. One user account is required for each instance. Assign the following role to the user accounts: User account role needed for Performance Monitor settings: 72 Adding probes to Analytics probe server

73 Storage administrator (performance management) User account roles needed to collect performance data via TCP/IP: 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 relevant to 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 To collect configuration performance data, enable the monitoring switch setting, and accumulate data by using Performance Monitor with short range set. Set the logical devices (on a CU basis) from which you want to collect performance data. This setting is not required if HUS VM is used. Set the performance data collection-target WWNs. Set the interval at which Performance Monitor collects performance data. If you use Performance Monitor to collect performance data, set short range. The granularity set here becomes the granularity of data that can be collected by RAID Agent. For details about how to set the following settings, see the Performance Guide relevant to your storage system. Make sure 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 these rules. Command devices using RAID Agent cannot be used with ZFS file system. Because using ZFS file system creates a file system automatically, the usage conditions listed below cannot be met. Adding probes to Analytics probe server 73

74 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, the /dev/sd form of the device file name might be changed by rescanning the disk device. We recommend that you use the WWID based form of the device file name (/dev/disk/by-id/scci hexadecimal-wwid). To specify the WWID based file name: 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, use the following to search for the WWID device file name corresponding to /dev/sdc: 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 by using both methods. Fibre Channel, Fibre Channel over Ethernet (FCoE), or iscsi TCP/IP connection Caution: Some of the functions of the programs cannot be executed while performance data is being collected via a TCP/IP connection. If you attempt to do both at the same time, one or the other (execution of the function or the collection of performance data) might fail. Before using a function for which the problem occurs, execute the htmsrv stop command to temporarily stop the RAID Agent instance. The following are examples of functions that cannot be executed while performance data is being collected via a TCP/IP connection: Data migration in Device Manager The following operations in Storage Navigator: Displaying the Server Priority Manager window Displaying the Volume Migration window 74 Adding probes to Analytics probe server

75 Displaying the Usage Monitor window of True Copy (for HUS VM and Virtual Storage Platform) Displaying the Usage Monitor window of Universal Replicator (for HUS VM and Virtual Storage Platform) Executing the export tools described in the Performance Monitor manuals Related topics Creating an instance environment on page 75 Creating an instance environment Hitachi Enterprise Storage probe collects data by using a TCP/IP connection, or using the command device of VSP G1000, G1500, VSP F1500, VSP Gx00 models, VSP Fx00 models, Virtual Storage Platform, or HUS VM. To collect data, you must create an instance environment of RAID Agent. Procedure 1. On the Analytics probe server, run the command with the service key and instance name specified. When specifying the instance name make sure that the length is from 1 to 32 bytes and only half-width alphanumeric characters (A-Z, a-z, 0-9) are used. For example, to create an instance environment for the instance named for RAID Agent, run the following command: /opt/jp1pc/tools/jpcconf inst setup -key RAID -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 be specified. 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. We recommend that you use the WWID based form of the device file name. See Verify the connection between host and monitoring targets 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. Adding probes to Analytics probe server 75

76 Item Description 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. Storage IP Address or Host Name Storage User ID Storage Password Java VM Heap Memory Details of storage model SVP Port No 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 in Verify the connection between host and monitoring targets. Specify the password of the user account that was created in Verify the connection between host and monitoring targets. 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's manual that explains how to change or initialize the port number to be used with the SVP. Serial No Specify the serial number of the storage system if Detailed Storage Model is set to 22 (VSP Gx00 76 Adding probes to Analytics probe server

77 Item Description models or VSP Fx00 models). You can specify a value from to SVP HTTPS Port No 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's manual that explains how to change or initialize the port number to be used with the SVP. Note: 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 even though you have enabled the setting. 3. To do the operation with 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 on page 72 Adding Hitachi Enterprise Storage probe on page 77 Starting and stopping RAID Agent services on page 81 Adding Hitachi Enterprise Storage probe Hitachi Enterprise Storage probe collects data of VSP G1000, G1500, VSP F1500, VSP Gx00 models, VSP Fx00 models, Virtual Storage Platform, or HUS VM. Adding probes to Analytics probe server 77

78 Before you begin The minimum supported RAID Agent version is Make sure that the storage instance is added in the RAID Agent using the command device. For each instance on the RAID Agent, make sure that the following services are running: Agent Store for RAID <RAID Instance name> Agent for <RAID Instance name> Make sure that the following services are running on the RAID Agent Server: HTnM REST Application Service HTnM REST Web Service To collect metrics from following resources hbaport, raidowner, raidportwwn, raidlu, and raidhg enable the data collection of the following opcode HGC, HHGC, and LHGC on the RAID Agent instance. To monitor a logical device that is not mapped to any port, value of UNASSIGN_VOL must be set to Y. Setting required to collect ESW metrics: Minimum RAID Agent version RAID agent instance is added using the command device and TCP/IP connection. Settings required to collect SPM metrics: Storage system must have the SPM setting enabled. The opcodes PWPC and LWPC must be enabled on the RAID Agent instance. Procedure 1. On the Home page, click Add Probe. 2. In the Add Probe window, from the Probes drop-down list, select Hitachi Enterprise Storage. 3. In the Provide RAID Agent Details section, type the following details, and then click Next: Probe Name: Name of the probe. The probe name must contain a minimum of 4 alphanumeric characters. Example: HESP Note: Special characters are not allowed. The name must be unique in the Data Center Analytics deployment, because it is used for creating unique folders, file names, and so on for the probe in Data Center Analytics. Connection Type: Choose HTTP or HTTPs. RAID Agent IP Address: IP address of the machine on which the RAID Agent is installed. 78 Adding probes to Analytics probe server

79 RAID Agent Host name: Host name of the machine on which the RAID Agent is installed. Note: The host name must match (case-sensitive) the RAID Agent s host name. RAID Agent Port: Port number used by the RAID Agent on the RAID Agent host. The default port numbers are: HTTP HTTPS 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 register the storage system on the RAID Agent. 4. In the Configure RAID Agent Collection Interval window, change the data collection value as necessary, and then click Next. Note: The Configure RAID Agent Collection Interval window lists the default RAID Agent data collection time. If you change the collection interval, then make sure that you change it on the RAID Agent. 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. Note: 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 Provide Hitachi Device Manager details 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 for accessing the XML API. Port: Port number of the Hitachi Device Manager server Adding probes to Analytics probe server 79

80 Default port numbers: 2001-HTTP Username/Password: User name and Password of the Hitachi Device Manager. The user must be added in ViewGroup user group. 6. In the Validation window, Click Next, and then OK. 7. In the Status window, in Action, click Start to start collecting data. Related topics Initial setup after adding a probe on page 86 Default collection and data export interval for probes on page 211 Deleting an instance environment To cancel setup of multiple instance environments, you must delete the agent's instance environment on the agent host: Procedure 1. Find the instance name of RAID Agent using this command: /opt/jp1pc/tools/jpcconf inst list key RAID For example, if the instance name is 35053, the command displays Run the following command to stop the RAID Agent services in the instance environment if it is active. /opt/jp1pc/htnm/bin/htmsrv stop -all 3. Delete the instance environment using this command: /opt/jp1pc/tools/jpcconf inst unsetup key RAID inst instance-name 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. Example: To delete an instance environment 35053: /opt/jp1pc/tools/jpcconf inst unsetup key RAID -inst Adding probes to Analytics probe server

81 Starting and stopping RAID Agent services Start or stop RAID Agent services when creating or deleting an instance environment for RAID Agent. Before you begin Log on as the root user to the host where you want to install the programs, or use the su command to assume root user privileges. Procedure To start services manually: Run the following command: /opt/jp1pc/htnm/bin/htmsrv start -all To start services automatically: 1. Run the following command: cd /opt/jp1pc 2. Set the service automatic start script file for the RAID Agent. Name of the.model file of the service automatic start script: jpc_start.model Name of the service automatic start script file: jpc_start Copy the.model file to the service automatic start script file to add execution permission. cp -p jpc_start.model jpc_start chmod 555 jpc_start Note: 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: 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 Adding probes to Analytics probe server 81

82 LANG unset LC_ALL The last line is an example of coding that unsets the LC_ALL value. To stop services manually: Run the following command: /opt/jp1pc/htnm/bin/htmsrv stop -all To stop services automatically: 1. Run the following command: cd /opt/jp1pc 2. Set the service automatic stop script file for the RAID Agent. Name of the.model file of the service automatic stop script: jpc_stop.model Name of the service automatic stop script file: jpc_stop Copy the.model file of the service automatic stop script to the service automatic stop script file to add execution permission. Run the command as follows: cp -p jpc_stop.model jpc_stop chmod 555 jpc_stop Adding Hitachi Adaptable Modular Storage (AMS) probe The AMS probe collects data from AMS 2x00 and HUS1x0 storage systems. Procedure 1. On the Home page, click Add Probe. 2. In the Add Probe window, from the Probes drop-down list, select Hitachi AMS. 3. In the Probes Details section, type the following details, and then click Next. AMS Storage Name: Name of AMS 2x00 or HUS1x0 system for which the probe is added. This must not be the same as the storage name that is defined in your environment. 82 Adding probes to Analytics probe server

83 Note: 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 AMS 2x00 or HUS1x0 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 86 Default collection and data export interval for probes on page 211 Adding Hitachi NAS probe The Hitachi NAS probe collects data from the Hitachi NAS platform Before you begin Make sure that the SMU users have CLI access. Procedure 1. On the Home page, click Add Probe. 2. In the Add Probe window, from the Probes drop-down list, select HItachi NAS. 3. In the Probes Details 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: The user credentials with minimum readonly privileges to connect to the SMU. 4. In the Validation window, click Next. 5. In the Choose Server window, select the server, and then click Next. Adding probes to Analytics probe server 83

84 The Choose Server window list all servers associated with the SMU. 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 86 Default collection and data export interval for probes on page 211 Adding VMware probe VMware probe collects data from the VMware vcenter Server and standalone VMware ESX 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 Probe Details section, type the following details, and then click Next: vcenter Server: Host name or IP address of the VMware vcenter Server Appliance or VMware ESX host IP address. User name: Any user having access to VMware vcenter Server. Readonly 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 86 Default collection and data export interval for probes on page 211 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. 84 Adding probes to Analytics probe server

85 Brocade Network Advisor Professional plus or Brocade Network Advisor Enterprise must be installed. Procedure 1. From the Analytics probe server 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 Probe Details window, type the following details, and then click Next.. Network Advisor IP: 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 86 Default collection and data export interval for probes on page 211 Adding Cisco DCNM probe This probe collects data from Cisco Data Center Network Manager, a management system for the Cisco Unified Fabric. 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 DCNM. 3. In the Cisco DCNM Probe Details window, type the following details and click Next: Cisco DCNM IP: IP address of DCNM. DCNM Webservice 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. Username and password of DCNM. Default ports are: Adding probes to Analytics probe server 85

86 80 - HTTP HTTPS 4. In the Validation window, click Next, and then click OK.. 5. In the Status window, under Action, click Start to start collecting data. Related topics Initial setup after adding a probe on page 86 Default collection and data export interval for probes on page 211 Initial setup after adding a probe After adding a probe, check whether data is being collected by Data Center Analytics server and is ready to be analyzed by Infrastructure Analytics Advisor server. 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 display window, enter the user name and password used to set up Data Center Analytics server. Username:user-name-that-was-set-during-the-set-up-of-Data Center Analytics-server Password: password-that-was-set-during-the-setup-of-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 web client. 5. Open a web browser, and then enter the following URL in the address bar to log on to Infrastructure Analytics Advisor server: 6. In the display window, enter the following information to log on: User ID: system Password: manager (default) 7. In the Administration tab, select Resource Management. 86 Adding probes to Analytics probe server

87 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. Adding probes to Analytics probe server 87

88 88 Adding probes to Analytics probe server

89 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 89

90 Data collection methods You can use one of the following methods to collect data using the Windowsbased probe: 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 Performance data is collected from the SCOM. Configuration data is collected from the individual machine and WMI query. 90 Installing Data Center Analytics server Windows-based probe

91 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 A user with the Domain Administrator role, and with the permissions to access ROOT/WMI, ROOT, ROOT/CIMV2, and WMI namespaces on the target machine. 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 firewall set service RemoteAdmin netsh firewall set service type=fileandprint mode=enable profile=all scope=all For workgroup computers: Change the settings for the Remote User Account Control (UAC) LocalAccountTokenFilterPolicyregistry entry. For more information, see Method 3: Data collection using Perfmon API and WMI query Performance and configuration data is collected from individual machines using the Perfmon API and WMI query. Prerequisites Installing Data Center Analytics server Windows-based probe 91

92 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 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: A user with Domain Administrator role, and with the permissions to access ROOT and ROOT/CIMV2 WMI namespaces on the target machine. 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 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.. 92 Installing Data Center Analytics server Windows-based probe

93 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 This section describes the settings that must be configured after Windowsbased probe is installed. Configuring the collection method 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 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 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 Installing Data Center Analytics server Windows-based probe 93

94 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 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. 94 Installing Data Center Analytics server Windows-based probe

95 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 96 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. 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: meghadata 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 96 Installing Data Center Analytics server Windows-based probe 95

96 Starting the Windows-based probe service 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 whether data is being collected by Data Center Analytics server and is ready to be analyzed by Infrastructure Analytics Advisor server. 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 display window, enter the user name and password used to set up Data Center Analytics server. Username:user-name-that-was-set-during-the-set-up-of-Data Center Analytics-server Password: password-that-was-set-during-the-setup-of-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 web client. 5. Open a web browser, and then enter the following URL in the address bar to log on to Infrastructure Analytics Advisor server: 6. In the display window, enter the following information to log on: User ID: system Password: manager (default) 7. In the Administration tab, select Resource Management. 96 Installing Data Center Analytics server Windows-based probe

97 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. Installing Data Center Analytics server Windows-based probe 97

98 98 Installing Data Center Analytics server Windows-based probe

99 9 Upgrading Infrastructure Analytics Advisor environment This section describes how to upgrade the Infrastructure Analytics Advisor environment. Upgrade the Infrastructure Analytics Advisor system Upgrade the Data Center Analytics server Windows-based probe Upgrading Infrastructure Analytics Advisor environment 99

100 Upgrade the Infrastructure Analytics Advisor system Upgrade all of the following components: Infrastructure Analytics Advisor server Data Center Analytics server Analytics probe server RAID Agent The Configuration Manager REST API (the REST server) must be installed on a host (if you are using the IO Control Settings function). To upgrade the Infrastructure Analytics Advisor system do the following steps. 1. Back up the Infrastructure Analytics Advisor systems. 2. Stop the Infrastructure Analytics Advisor components. 3. Upgrade the Data Center Analytics server. 4. Upgrade the Analytics probe server. 5. Upgrade the RAID Agent. 6. Upgrade the Infrastructure Analytics Advisor server. Related topics Starting and stopping RAID Agent services on page 81 Upgrade the Data Center Analytics server on page 100 Upgrade the Analytics probe server on page 101 Upgrade the RAID Agent on page 103 Upgrade the Infrastructure Analytics Advisor server on page 103 Stopping the Infrastructure Analytics Advisor server service on page 130 Stopping the Data Center Analytics server or Analytics probe server service on page 132 Backing up and restoring Infrastructure Analytics Advisor on page 145 Upgrade the Data Center Analytics server To upgrade the Data Center Analytics server, do the following procedures. Before you begin Upgrade the Data Center Analytics server by following the procedure for upgrading the Infrastructure Analytics Advisor system. If you do not follow this procedure, the product might not work properly. Caution: You must preserve the user-imported certificate stored at following location /usr/local/megha/jetty/etc/ keystore before upgrade. This certificate prevents the certificate warning while accessing the server and probe GUI. 100 Upgrading Infrastructure Analytics Advisor environment

101 Preserving the user-imported certificate 1. Log on to the host on which Data Center Analytics server is installed through the 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 4. Confirm the stopped status of megha service using the command: /usr/local/megha/bin/megha-jetty.sh status 5. Take the backup of the keystore files temporary location /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 using the command: /usr/local/megha/bin/megha-jetty.sh start 7. Start the crond service using the command: service crond start Procedure 1. Log on to the Data Center Analytics server. 2. In the application bar area, click the Manage link. 3. On the Manage window, in the Administrator section, click Upgrade Server. 4. Upload the hdca-server-6.1-xxxxxxxx.zip file and hdca-server-6.1- xxxxxxxx.zip.hash file available in the installation media, and click OK. 5. In the application bar area, click the Manage link. 6. On the Manage window, in the Administrator section, click Upgrade Server. 7. Upload the hdca-server-7.0-xxxxxxxx.zip file and hdca-server-7.0- xxxxxxxx.zip.hash file available in the installation media, and click OK. Related topics Upgrade the Infrastructure Analytics Advisor system on page 100 Upgrade the Analytics probe server To upgrade the Analytics probe server, do the following procedures. Before you begin Upgrade the Analytics probe server by following the procedure for upgrade the Infrastructure Analytics Advisor system. If you do not follow this procedure, the product might not work properly. Upgrading Infrastructure Analytics Advisor environment 101

102 Caution: You must preserve the user-imported certificate stored at following location /usr/local/megha/jetty/etc/keystore before upgrade. This certificate prevents the certificate warning while accessing the server and probe GUI. Preserving the user-imported certificate 1. Log on to the host on which Analytics probe server is installed through the 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 4. Confirm the stopped status of megha service using the command: /usr/local/megha/bin/megha-jetty.sh status 5. Take the backup of the keystore files temporary location /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 using the command: /usr/local/megha/bin/megha-jetty.sh start 7. Start the crond service using the command: service crond start Procedure 1. Log on to the Analytics probe server. 2. In the application bar area, click the Manage link. 3. On the Manage window, in the Administrator section, click Upgrade Probe. 4. Upload the hdca-probe-6.1-xxxxxxxx.zip file and hdca-probe-6.1- xxxxxxxx.zip.hash file available in the installation media, and click OK. 5. In the application bar area, click the Manage link. 6. On the Manage window, in the Administrator section, click Upgrade Probe. 7. Upload the hdca-probe-7.0-xxxxxxxx.zip file and hdca-probe-7.0- xxxxxxxx.zip.hash file available in the installation media, and click OK. Related topics Upgrade the Infrastructure Analytics Advisor system on page Upgrading Infrastructure Analytics Advisor environment

103 Upgrade the RAID Agent To upgrade the RAID Agent, do the following procedures. Before you begin Upgrade RAID Agent by following the procedure for upgrade the Infrastructure Analytics Advisor system. If you do not follow this procedure, the product might not work properly. Procedure 1. Log on to the host where the RAID Agent is installed. 2. Close all programs (including antivirus programs). 3. 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 4. Run the following command as a root user: cd /root/dcaprobe/ sh./agent_update.sh Output example: [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 the Infrastructure Analytics Advisor system on page 100 Upgrade the Infrastructure Analytics Advisor server To upgrade the Infrastructure Analytics Advisor server, do the following procedures. Upgrading Infrastructure Analytics Advisor environment 103

104 Before you begin Upgrade Infrastructure Analytics Advisor server by following the procedure for upgrade the Infrastructure Analytics Advisor system. If you do not follow this procedure, the product might not work properly. Procedure 1. Log on to the Infrastructure Analytics Advisor server as a user with the Administrator permission. 2. Close all programs (including antivirus programs). 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 to complete the upgrade. You can specify, as an option, whether to back up the data before performing the upgrade. We recommend a back up the data before upgrade in case of failure of upgrade. This option is "yes" by default. Related topics Upgrade the Infrastructure Analytics Advisor system on page 100 Upgrade the Data Center Analytics server Windows-based probe To upgrade the Windows-based probe, do the following procedures. Procedure 1. On the host on which the Windows-based probe is installed, log in as a user with Administrator permissions. 2. Close all programs (including antivirus programs). 3. Run DCA_Windows_Probe.exe on the installation media to start the installer. Follow the displayed prompts to complete the upgrade. 104 Upgrading Infrastructure Analytics Advisor environment

105 10 Configuring secure communications This section describes the settings required to ensure security. 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 secure communications 105

106 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. No. 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 HTTPS # 5 Data Center Analytics server Analytics probe server SFTP 6 Data Center Analytics server Windows host FTP 106 Configuring secure communications

107 No. SSL server (program) SSL client Protocol 7 Hitachi Automation Director Infrastructure Analytics Advisor server HTTPS HTTP HTTPS 8 REST server Hitachi Automation Director HTTP HTTPS Note: #: SSL communication is set by default. If you use a certificate issued by a trusted certificate authority, use the information in this chapter 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 routes 7 and 8, see the Automation Director Installation and Configuration Guide and Configuration Manager REST API Reference Guide. Workflow for configuring secure communications The following figure indicates the workflow for configuring a secure communication for Infrastructure Analytics Advisor. Configuration workflow for secure communication between the Infrastructure Analytics Advisor server and the web client Configuring secure communications 107

108 Configuration workflow for secure communication between the Data Center Analytics server and the web client Configuration workflow for secure communication between the Analytics probe server and the web client 108 Configuring secure communications

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

110 Related topics Logging on to Infrastructure Analytics Advisor server on page 63 Creating a private key and a certificate signing request for Infrastructure Analytics Advisor server on page 111 Applying for a server certificate for Infrastructure Analytics Advisor server from the certificate authority on page 112 Enabling SSL communication for the Infrastructure Analytics Advisor server on page 112 Applying self-signed certificates to the Data Center Analytics server on page 117 Exporting a self-signed certificate for the Data Center Analytics server on page 119 Importing a certificate to the truststore file for the Infrastructure Analytics Advisor server on page 119 Applying server certificates to the Data Center Analytics server and the Analytics probe server on page Configuring secure communications

111 Configuring an SSL server (Infrastructure Analytics Advisor server) Use this section to configure the Infrastructure Analytics Advisor server as an SSL server. Tasks include creating a private key and a certificate signing request, applying for a server certificate, and configuring secure communication. Creating a private key and a certificate signing request for Infrastructure Analytics Advisor server Use the hcmds64ssltool command to create a private key and a certificate signing request (CSR) for Infrastructure Analytics Advisor server. Before you begin You must have the Administrator permission (for Windows) or the root permission (for Linux) of the OS to do this operation. Check with the certificate authority regarding the requirements for the certificate signing request. Make sure that the signature algorithm of the server certificate is supported by the version of the web browser. When re-creating a private key, certificate signing request, or self-signed certificate, send the output to a new location. (If a file of the same name exists in the output location, the file cannot be re-created.) Procedure 1. Run the hcmds64ssltool command to create private keys, certificate signing requests, and self-signed certificates that support RSA cryptography and elliptic curve cryptography (ECC). The certificate signing request is created in PEM format. Tip: Use a self-signed certificate only to test encrypted communications. Related topics hcmds64ssltool on page 189 Configuring secure communications 111

112 Applying for a server certificate for Infrastructure Analytics Advisor server from the certificate authority In general, applications for server certificates are submitted online. Create a certificate signing request (CSR) for Infrastructure Analytics Advisor server, and send it to the certificate authority to obtain a digital signature. Before you begin Create a certificate signing request for Infrastructure Analytics Advisor server. You must have a server certificate that was issued in X.509 PEM format by the certificate authority. For details on how to apply, see the website of the certificate authority you use. In addition, make sure the certificate authority supports the signature algorithm. Procedure 1. Send the created certificate signing request to the certificate authority. 2. Save the response from the certificate authority. Note: Use the hcmds64checkcerts command to verify the expiration date of the certificate. Related topics Checking the expiration date of the certificate for Infrastructure Analytics Advisor server on page 116 Enabling SSL communication for the Infrastructure Analytics Advisor server To enable SSL communication, edit the user_httpsd.conf file. Before you begin Create a private key for the Infrastructure Analytics Advisor server. Prepare the Infrastructure Analytics Advisor server certificate file from the certificate authority. We recommend that you copy the file to the following location: In Windows Infrastructure-Analytics-Advisor-server-installation-folder \Base64\uCPSB\httpsd\conf\ssl\server In Linux 112 Configuring secure communications

113 Verify the host name specified for Common Name in the certificate signing request. Procedure 1. Stop the Infrastructure Analytics Advisor server services. 2. Edit the user_httpsd.conf file. In Windows In Linux Infrastructure-Analytics-Advisor-server-installationdirectory/Base64/uCPSB/httpsd/conf/ssl/server Infrastructure-Analytics-Advisor-server-installationfolder\Base64\uCPSB\httpsd\conf\user_httpsd.conf Infrastructure-Analytics-Advisor-server-installationdirectory/Base64/uCPSB/httpsd/conf/user_httpsd.conf Example of the user_httpsd.conf file (default) Settings required for enabling SSL communication: Configuring secure communications 113

114 Remove the hash mark (#) as shown in the following example: When using RSA cryptography only, you do not need to remove the hash mark (#) for the SSLECCCertificateKeyFile and the SSLECCCertificateFile settings. For the ServerName directive in the first line and the ServerName directive inside the <VirtualHost> tags, enter the host name that you specified for Common Name in the certificate signing request. (Host names are case sensitive.) For the Infrastructure Analytics Advisor server certificate file, you must have a certificate signed by a certificate authority and a selfsigned certificate. Specify an absolute path to the key and certificate files: For RSA cryptography only: SSLCertificateFile SSLCertificateKeyFile For elliptic curve cryptography: SSLECCCertificateFile SSLECCCertificateKeyFile 114 Configuring secure communications

115 Note: You do not need to specify these settings if you are going to use RSA cryptography only. For SSLCertificateKeyFile and SSLECCCertificateKeyFile, do not specify a symbolic link and junction for the path. For SSLECCCertificateKeyFile, use a PEM-format private key file in PKCS#8 format. If the server certificate for Infrastructure Analytics Advisor server originated from an intermediate certificate authority, remove the hash mark (#) from the beginning of the line of the SSLCACertificateFile directive, and then specify the absolute path of all server certificates issued by the intermediate certificate authorities. You can include multiple certificates in a single file by using a text editor to chain those certificates in PEM format. Note: Do not edit the httpsd.conf, hsso_httpsd.conf, or user_hsso_httpsd.conf files. Do not specify the same directive twice. Do not enter a line break in the middle of a directive. Even if you enable SSL communication, do not remove or comment out the line Listen To interrupt non-ssl communication from a source outside of the network to the management server, add a hash mark (#) to the beginning of the line Listen to comment it out, then remove the hash mark from the beginning of the line #Listen : To close the port for non-ssl communication by the Infrastructure Analytics Advisor server, close this port for the HBase 64 Storage Mgmt Web Service. 3. Start the Infrastructure Analytics Advisor server services. Related topics Creating a private key and a certificate signing request for Infrastructure Analytics Advisor server on page 111 Starting the Infrastructure Analytics Advisor server service on page 130 Stopping the Infrastructure Analytics Advisor server service on page 130 Configuring secure communications 115

116 Checking the expiration date of the certificate for Infrastructure Analytics Advisor server Use the hcmds64checkcerts command to check the expiration date of the Infrastructure Analytics Advisor server certificate and the certificate issued by a certificate authority. Before you begin In the user_httpsd.conf file, specify the path of the following certificates: Server certificate for Infrastructure Analytics Advisor server When the certificate for both the RSA cryptography and the elliptic curve cryptography is used, the path of both certificates must be specified. All certificates issued by intermediate certificate authorities You must have the Administrator permission (for Windows) or the root permission (for Linux) of the OS to do this operation. Procedure 1. Run the following command: In Windows Infrastructure-Analytics-Advisor-server-installationdestination-folder\Base64\bin\hcmds64checkcerts { [/days number-of-days] [/log] /all } In Linux Infrastructure-Analytics-Advisor-server-installationdestination-directory/Base64/bin/hcmds64checkcerts { [/ days number-of-days] [/log] /all } The options are: days log all Specify the period (in days). The range of days is 30 to 3,652 (10 years). This options displays expired certificates and those due to expire during the specified period. (When you omit this option, the command displays certificates due to expire in 30 days.) Specify this option if you want to regularly check the expiration dates of certificates as an operating system task. When certificates are displayed, a warning message is output to the event log. 116 Configuring secure communications

117 Specify the expiration date to display for all certificates listed in the user_httpsd.conf file. Configuring SSL servers (Data Center Analytics server and Analytics probe server) This section describes how to set the Data Center Analytics server and the Analytics probe server as SSL servers. Applying self-signed certificates to the Data Center Analytics server Self-signed certificates are automatically created when the Data Center Analytics server is installed. To re-create self-signed certificates, perform the procedure described in this section. Perform this procedure in the following cases: When you change the host name or the host IP address of the Data Center Analytics server, and the certificate is associated with the current host When the expiration date of the self-signed certificate has expired Do not perform this procedure in the following cases: If you want to use the server certificates that were automatically created when the Data Center Analytics server was installed If you want to use server certificates that have been signed by a certificate authority In the previous case, see the description of server certificates that have been signed by a certificate authority. Procedure 1. Perform the following steps to stop the Data Center Analytics server services: a. Run the following command: crontab -e b. At the beginning of each line in the ordinary execution schedule that was output for the Data Center Analytics server, add a hash mark (#) to comment out each line: # */5 * * * * F=/usr/local/megha/cron.5min; test -f $F && bash $F # 13 0 * * * F=/usr/local/megha/cron.1hr; test -f $F && bash $F # 11 * * * * F=/usr/local/megha/cron.24hr; test -f $F && bash $F # */5 * * * * F=/usr/local/megha/bin/sysstat.sh; test -f $F && (bash $F >> /usr/local/megha/logs/sys/`date +\%Y\%m\ %d`.log) c. Run the following command to stop the services: Configuring secure communications 117

118 /usr/local/megha/bin/megha-jetty.sh stop d. Use the following command to verify that the services have stopped: /usr/local/megha/bin/megha-jetty.sh status Output example: ~]# /usr/local/megha/bin/megha-jetty.sh status Megha server is not running 2. Run the following command to back up the default keystore: mv /usr/local/megha/jetty/etc/keystore /usr/local/megha/ jetty/etc/keystore.org 3. Run the following command to create self-signed certificates in a new keystore: keytool -keystore /usr/local/megha/jetty/etc/keystore -alias alias-name -genkey -keyalg RSA The default password is megha.jeos. For the alias-name, specify a name to identify which host server has the self-signed certificate. 4. Perform the following steps to start the Data Center Analytics server services: a. Run the following command: crontab -e b. Delete the hash marks (#) from the beginning of each line in the ordinary execution schedule that generates output for the Data Center Analytics server: */5 * * * * F=/usr/local/megha/cron.5min; test -f $F && bash $F 13 0 * * * F=/usr/local/megha/cron.1hr; test -f $F && bash $F 11 * * * * F=/usr/local/megha/cron.24hr; test -f $F && bash $F */5 * * * * F=/usr/local/megha/bin/sysstat.sh; test -f $F && (bash $F >> /usr/local/megha/logs/sys/`date +\%Y\%m\ %d`.log) c. Run the following command: /usr/local/megha/bin/megha-jetty.sh start 5. Run the following command to verify that the Data Center Analytics server services are running: /usr/local/megha/bin/megha-jetty.sh status Output example: [root@localhost jetty]# /usr/local/megha/bin/megha-jetty.sh status 118 Configuring secure communications

119 Megha server is running Related topics Importing a certificate to the truststore file for the Infrastructure Analytics Advisor server on page 119 Applying server certificates to the Data Center Analytics server and the Analytics probe server on page 121 Exporting a self-signed certificate for the Data Center Analytics server This section provides information about exporting a self-signed certificate for the Data Center Analytics server. Procedure 1. Run the following command to export the certificate for the Data Center Analytics server: keytool export keystore /usr/local/megha/jetty/etc/keystore alias alias-name file certificate-file-name For the alias-name, specify a name to identify which host server has the self-signed certificate. If you want to export the default self-signed certificate, specify jetty. For certificate-file-name, specify the absolute path to the export destination of the self-signed certificate. Importing a certificate to the truststore file for the Infrastructure Analytics Advisor server To enable verification of the server certificate for the Data Center Analytics server on the Infrastructure Analytics Advisor server, import the certificate as described in this section. Before you begin You must have the Administrator permission (for Windows) or the root permission (for Linux) of the Infrastructure Analytics Advisor server to do this operation. Procedure 1. Run the following command to import the certificates for the Data Center Analytics server to the truststore file: In Windows Infrastructure-Analytics-Advisor-server-installationdestination-folder\Base64\bin\hcmds64keytool import alias alias-name file certificate-file-name keystore truststore-file-name storepass password-to-access-thetruststore Configuring secure communications 119

120 For the alias-name, specify a name to identify which host server has the certificate. For the certificate-file-name, specify the absolute path. The truststore file is stored in the following location: In Windows In Linux Infrastructure-Analytics-Advisor-server-installationdestination-directory/Base64/uCPSB/jdk/bin/keytool import alias alias-name file certificate-file-name keystore truststore-file-name storepass password-toaccess-the-truststore Infrastructure-Analytics-Advisor-server-installationdestination-folder\Base64\uCPSB\jdk\jre\lib\security \jssecacerts In Linux Infrastructure-Analytics-Advisor-server-installationdestination-directory/Base64/uCPSB/jdk/jre/lib/ security/jssecacerts The password to access the default truststore is changeit. 2. To enable the verification of server certificates, change the following properties in the config_user.properties file: Storage location: In Windows In Linux Infrastructure-Analytics-Advisor-server-installationdestination-folder\Analytics\conf Infrastructure-Analytics-Advisor-server-installationdestination-directory/Analytics/conf Key: cert.verify.enabled Value: true 3. Start Infrastructure Analytics Advisor server services. Related topics Applying self-signed certificates to the Data Center Analytics server on page 117 Applying server certificates to the Data Center Analytics server and the Analytics probe server on page 121 Starting the Infrastructure Analytics Advisor server service on page 130 User-specified properties file (config_user.properties) on page Configuring secure communications

121 Applying server certificates to the Data Center Analytics server and the Analytics probe server To apply server certificates to the Data Center Analytics server and the Analytics probe server, first create a keystore file. Before you begin Copy the server certificate and the private key to the Data Center Analytics server and the Analytics probe server. You can use any certificate in CRT format that has been signed by a certificate authority. Procedure 1. Follow these steps by using a keystore where the user certificates in PKCS12 format are stored: a. Copy the server certificate created by the user to the Data Center Analytics server. b. Log on as a root user to the Data Center Analytics server by using an SSH client. Note: A root user cannot log on from the VMware vcenter VM console. c. Go to the directory of the server certificate the Data Center Analytics server. d. If the file for the server certificate request is not the same as the file containing the private key, combine those files into one file in PKCS12 format. The following example shows how to combine multiple files into one jetty.pkcs12 file, assuming that jetty.crt is a server certificate that has been signed by a certificate authority and that jetty.key is the private key. openssl pkcs12 -inkey jetty.key -in jetty.crt -export -out jetty.pkcs12 Note: When the file is output, password confirmation is required. Do not specify an empty password. Make sure you write down the password because you need it when applying the server certificate to the Analytics probe server. e. If the created server certificate is an intermediate certificate in a chain of certificates, create a file in PKCS12 format: Configuring secure communications 121

122 The following example shows how to specify a command for combining chained certificates into cert-chain.txt. Specify server certificates in order, starting from servers to the root CA. cat jetty.crt intermediate.crt [intermediate2.crt]... rootca.crt > cert-chain.txt openssl pkcs12 -export -inkey jetty.key -in cert-chain.txt -out jetty.pkcs12 Note: When the file is output, password confirmation is required. Do not specify an empty password. Make sure you write down the password, because you need it when you apply the server certificate to the Analytics probe server. f. Use the following command to import a file in PKCS12 format and create a keystore file: keytool -importkeystore -srckeystore jetty.pkcs12 - srcstoretype PKCS12 -destkeystore keystore A keystore file is created in the current directory. Make sure you remember the location of the created keystore file. 2. Perform the following steps to stop the crond service of the Data Center Analytics server: a. Run the following command: crontab -e b. At the beginning of each line in the ordinary execution schedule that was output for the Data Center Analytics server, add a hash mark (#) to comment out each line: # */5 * * * * F=/usr/local/megha/cron.5min; test -f $F && bash $F # 13 0 * * * F=/usr/local/megha/cron.1hr; test -f $F && bash $F # 11 * * * * F=/usr/local/megha/cron.24hr; test -f $F && bash $F # */5 * * * * F=/usr/local/megha/bin/sysstat.sh; test -f $F && (bash $F >> /usr/local/megha/logs/sys/`date +\%Y\%m\ %d`.log) 3. Use the following command to stop the Data Center Analytics server services: /usr/local/megha/bin/megha-jetty.sh stop 4. Use the following command to verify that the Data Center Analytics server services have stopped: /usr/local/megha/bin/megha-jetty.sh status Output example: 122 Configuring secure communications

123 ~]# /usr/local/megha/bin/megha-jetty.sh status Megha server is not running 5. Use the following command to copy the keystore file: cp location-of the-keystore-file/keystore /usr/local/megha/ jetty/etc/ 6. Apply the keystore file to the Data Center Analytics server. Enter the password that you specified in step 1 for PASSWORD (three locations) in /usr/local/megha/jetty/etc/jetty-ssl.xml. <Set name="keystorepath"><property name="jetty.base" default="." />/<Property name="jetty.keystore" default="etc/ keystore"/></set> <Set name="keystorepassword"> PASSWORD </ Set> <Set name="keymanagerpassword"> PASSWORD </Set> <Set name="truststorepath"><property name="jetty.base" default="." />/<Property name="jetty.truststore" default="etc/keystore"/></set> <Set name="truststorepassword"> PASSWORD </Set> 7. Start the Data Center Analytics server services: /usr/local/megha/bin/megha-jetty.sh start 8. Use the following command to verify that the service status of the Data Center Analytics server is Running: /usr/local/megha/bin/megha-jetty.sh status Output example: [root@localhost jetty]# /usr/local/megha/bin/megha-jetty.sh status Megha server is running 9. Do the following steps to start the crond service of the Data Center Analytics server: a. Run the following command: crontab -e b. Delete the hash marks (#) as follows from the beginning of each line in the ordinary execution schedule that was output for the Data Center Analytics server: */5 * * * * F=/usr/local/megha/cron.5min; test -f $F && bash $F 13 0 * * * F=/usr/local/megha/cron.1hr; test -f $F && bash $F 11 * * * * F=/usr/local/megha/cron.24hr; test -f $F && bash $F */5 * * * * F=/usr/local/megha/bin/sysstat.sh; test -f $F Configuring secure communications 123

124 && (bash $F >> /usr/local/megha/logs/sys/`date +\%Y\%m\ %d`.log) 10. Do steps 1 to 9 on the Analytics probe server. Related topics Checking the expiration dates of certificates for Data Center Analytics server and Analytics probe server on page 124 Checking the expiration dates of certificates for Data Center Analytics server and Analytics probe server Check the expiration dates of the server certificates and Certificate Authority certificates for Data Center Analytics server and Analytics probe server. Before you begin You must have the root permission of the operating system. Procedure 1. Run the following command on the Data Center Analytics server or the Analytics probe server: PEM format: openssl x509 -in server-certificate-file -noout -dates DER format: openssl x509 -inform der -in server-certificate-file - noout -dates Changing the SSL port number between the Infrastructure Analytics Advisor server and a web client To change the port number for SSL communication, change the port numbers specified in the definition files. Then, set the firewall exceptions. Before you begin You must have the Administrator permission (for Windows) or the root permission (for Linux) of the OS to do this operation. Procedure 1. Stop the Infrastructure Analytics Advisor server services by running the hcmds64srv command with the stop option. 2. Change the port numbers in the following definition files: In Windows 124 Configuring secure communications

125 Infrastructure-Analytics-Advisor-server-installationdestination-folder\Base64\uCPSB\httpsd\conf \user_httpsd.conf Change the following three lines: Listen Listen [::]:22016 <VirtualHost *:22016> Infrastructure-Analytics-Advisor-server-installationdestination-folder\Analytics\conf \command_user.properties Change the following line: command.https.port = In Linux Infrastructure-Analytics-Advisor-server-installationdestination-directory/Base64/uCPSB/httpsd/conf/ user_httpsd.conf Change the following three lines: Listen Listen [::]:22016 <VirtualHost *:22016> Infrastructure-Analytics-Advisor-server-installationdestination-directory/Analytics/conf/ command_user.properties Change the following line: command.https.port = For Windows, change the shortcut to the program as follows: The default URL is: For Windows Server 2008 R2 1. From the Start menu, click All Programs > Hitachi Infrastructure Analytics Advisor > Infrastructure Analytics Advisor > HIAA Login to display the properties. 2. Change the port number of the URL specified in Target. For Windows Server 2012 Configuring secure communications 125

126 1. From the desktop, display the Start window. 2. Right-click the Start window to display All apps. 3. Display the properties of HIAA Login in the Hitachi Infrastructure Analytics Advisor folder. 4. In the Web Document tab, change the port number of the URL specified in URL. 4. Set the firewall exceptions. In Windows Run the hcmds64fwcancel command to set Windows-based firewall exceptions. In Linux Run the iptable command to register Linux firewall exceptions. 1. Open the firewall settings file (/etc/sysconfig/iptables), for example by using a text editor. 2. Register the following line before the line "--reject-with icmphost-prohibited": -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport port-number -j ACCEPT Note: Make sure that you enter the entire text from "-A RH- Firewall-1-INPUT" to "-j ACCEPT" in one line. For port-number, enter the number of the port to be opened. You must specify the above setting for each port number. 3. Overwrite the firewall settings file to save the settings. 4. Restart the service. Execute the following command on the console: # /etc/rc.d/init.d/iptables restart 5. Run the hcmds64srv command with the start option. Related topics Starting the Infrastructure Analytics Advisor server service on page 130 Stopping the Infrastructure Analytics Advisor server service on page 130 hcmds64fwcancel on page Configuring secure communications

127 Deleting a certificate from the truststore for Infrastructure Analytics Advisor server You can delete a certificate for Data Center Analytics server, which was imported to Infrastructure Analytics Advisor server. Before you begin You must have Administrator permissions (for Windows) or root permissions (for Linux) for Infrastructure Analytics Advisor server. Procedure 1. Run the following command to delete the certificate for Data Center Analytics server, which was imported to Infrastructure Analytics Advisor server. In Windows Infrastructure-Analytics-Advisor-server-installationfolder\Base64\bin\hcmds64keytool delete alias aliasname keystore truststore-file-name storepass passwordto-access-the-truststore In Linux Infrastructure-Analytics-Advisor-server-installationdirectory/Base64/uCPSB/jdk/bin/keytool delete alias alias-name keystore truststore-file-name storepass password-to-access-the-truststore For the alias-name, specify a name to identify which host server has the certificate. For the certificate-file-name, specify the absolute path to the storage location of the certificate. The truststore file is stored in the following location: In Windows In Linux Infrastructure-Analytics-Advisor-server-installationfolder\Base64\uCPSB\jdk\jre\lib\security\jssecacerts Infrastructure-Analytics-Advisor-server-installationdirectory/Base64/uCPSB/jdk/jre/lib/security/jssecacerts The password to access the default truststore is changeit. Configuring secure communications 127

128 128 Configuring secure communications

129 11 Changing Infrastructure Analytics Advisor system settings This section contains the procedures to change the Infrastructure Analytics Advisor settings. Starting and stopping the Infrastructure Analytics Advisor service Changing the system information of Infrastructure Analytics Advisor server Changing the system information of Analytics probe server Backing up and restoring Infrastructure Analytics Advisor Enabling system account locking Changing Infrastructure Analytics Advisor system settings 129

130 Starting and stopping the Infrastructure Analytics Advisor service This section describes how to start and stop the Infrastructure Analytics Advisor services. Starting the Infrastructure Analytics Advisor server service To start the Infrastructure Analytics Advisor server services, run the hcmds64srv command. Before you begin You must have the Administrator permission (for Windows) or the root permission (for Linux) of the OS to do this operation. Procedure 1. Run the following command: For Windows: hcmds64srv /start For Linux: hcmds64srv -start Note: For Windows, do not use Service Control Manager to start the services. To stop or start only the Infrastructure Analytics Advisor server services when the common component services are running, run the command with AnalyticsWebService specified for the server option. To start the service during your daily operation, omit this option to start all services. Result The Infrastructure Analytics Advisor server services starts. Related topics hcmds64srv on page 185 Infrastructure Analytics Advisor server services on page 203 Stopping the Infrastructure Analytics Advisor server service To stop the services, run the hcmds64srv command. 130 Changing Infrastructure Analytics Advisor system settings

131 Before you begin You must have the Administrator permission (for Windows) or the root permission (for Linux) of the OS to do this operation. Procedure 1. Run the following command: For Windows: hcmds64srv /stop /server server-name For Linux: hcmds64srv -stop -server server-name Note: For Windows, do not use Service Control Manager to stop the service. If you use Service Control Manager to stop the service, the processing might fail. To stop or start only the Infrastructure Analytics Advisor server services when the common component service is running, run the command with AnalyticsWebService specified for the server option. To stop the Infrastructure Analytics Advisor server services during your daily operation, omit this option to stop all services. Result The Infrastructure Analytics Advisor server services stops. Related topics hcmds64srv on page 185 Infrastructure Analytics Advisor server services on page 203 Starting the Data Center Analytics server or Analytics probe server service Do the following steps to start the Data Center Analytics server or Analytics probe server service. Before you begin Log on to the Data Center Analytics server or Analytics probe server as the root user. Procedure 1. Run the crontab -e command. Changing Infrastructure Analytics Advisor system settings 131

132 2. Delete the hash marks (#) as follows from the beginning of each line in the regular execution schedule that was output for the Data Center Analytics server or Analytics probe server: */5 * * * * F=/usr/local/megha/cron.5min; test -f $F && bash $F 13 0 * * * F=/usr/local/megha/cron.1hr; test -f $F && bash $F 11 * * * * F=/usr/local/megha/cron.24hr; test -f $F && bash $F */5 * * * * F=/usr/local/megha/bin/sysstat.sh; test -f $F && (bash $F >> /usr/local/megha/logs/sys/`date +\%Y\%m\%d`.log) 3. Run the following command to start the service: /usr/local/megha/bin/megha-jetty.sh start Stopping the Data Center Analytics server or Analytics probe server service Do the following steps to stop the Data Center Analytics server or Analytics probe server service. Before you begin Log on to the Data Center Analytics server or Analytics probe server as the root user. Procedure 1. Run the crontab -e command. 2. At the beginning of each line in the regular execution schedule for Data Center Analytics server or Analytics probe server, add a hash mark (#) to comment out a line as shown in this example. # */5 * * * * F=/usr/local/megha/cron.5min; test -f $F && bash $F # 13 0 * * * F=/usr/local/megha/cron.1hr; test -f $F && bash $F # 11 * * * * F=/usr/local/megha/cron.24hr; test -f $F && bash $F # */5 * * * * F=/usr/local/megha/bin/sysstat.sh; test f $F && (bash $F >> /usr/local/megha/logs/sys/`date +\%Y\%m\ %d`.log) 3. Run the following command to stop the service: /usr/local/megha/bin/megha-jetty.sh stop Note: If crontab has not been edited, the Data Center Analytics server or Analytics probe server service might start automatically. If the Data Center Analytics server or Analytics probe server service starts, stop it by following this procedure. 132 Changing Infrastructure Analytics Advisor system settings

133 Changing the system information of Infrastructure Analytics Advisor server This section contains the procedures to change system information about the Infrastructure Analytics Advisor server. Changing the installation directory of Infrastructure Analytics Advisor server Changing the installation directory requires backup of existing data, uninstalling and reinstalling Infrastructure Analytics Advisor server, and restoring data. Procedure 1. Run the backupsystem command to back up the Infrastructure Analytics Advisor system. 2. Uninstall Infrastructure Analytics Advisor server. 3. Reinstall Infrastructure Analytics Advisor server. 4. Run the restoresystem command to restore the Infrastructure Analytics Advisor system. Related topics Installation on page 44 Installation on page 56 Backing up Infrastructure Analytics Advisor server settings information on page 148 Restoring Infrastructure Analytics Advisor server settings information on page 152 Removing Infrastructure Analytics Advisor server from a Windows host on page 162 Removing Infrastructure Analytics Advisor server and Data Center Analytics server on page 162 Changing the Infrastructure Analytics Advisor server host name Use the hcmds64srv command to change the host name of the Infrastructure Analytics Advisor server. Before you begin You must have the Administrator permission (for Windows) or the root permission (for Linux) of the OS to do this operation. Changing Infrastructure Analytics Advisor system settings 133

134 Procedure 1. Run the hcmds64srv command with the stop option to stop the Infrastructure Analytics Advisor server service. 2. Change the host name of the Infrastructure Analytics Advisor server. 3. Change the host name specified in ServerName in the user_httpsd.conf file. In Windows Infrastructure-Analytics-Advisor-server-installationdestination-folder\Base64\uCPSB\httpsd\conf \user_httpsd.conf In Linux Infrastructure-Analytics-Advisor-server-installationdestination-directory/Base64/uCPSB/httpsd/conf/ user_httpsd.conf 4. Restart the Infrastructure Analytics Advisor server. 5. Run the hcmds64srv command with the start option to start the Infrastructure Analytics Advisor server services. Related topics Starting the Infrastructure Analytics Advisor server service on page 130 Stopping the Infrastructure Analytics Advisor server service on page 130 Changing the Infrastructure Analytics Advisor server IP address Stop Infrastructure Analytics Advisor server services by using the hcmds64srv command to change the IP address of the Infrastructure Analytics Advisor server. Before you begin You must have the Administrator permission (for Windows) or the root permission (for Linux) of the OS to do this operation. Procedure 1. Run the hcmds64srv command with the stop option to stop Infrastructure Analytics Advisor server services. 2. Change the IP address of the Infrastructure Analytics Advisor server. 3. Run the hcmds64srv command with the start option to start the Infrastructure Analytics Advisor server services. Related topics Starting the Infrastructure Analytics Advisor server service on page 130 Stopping the Infrastructure Analytics Advisor server service on page Changing Infrastructure Analytics Advisor system settings

135 Changing the port number used between Infrastructure Analytics Advisor server and the web browser To change the port number used between Infrastructure Analytics Advisor server and the web browser, change the port number in each definition file. Then, register the firewall exceptions. Before you begin You must have the Administrator permission (for Windows) or the root permission (for Linux) of the OS to do this operation. Procedure 1. Run the hcmds64srv command with the stop option to stop Infrastructure Analytics Advisor server services. 2. Edit the definition files. The port number settings to be edited depend on the communication method between Infrastructure Analytics Advisor server and the web browser, as follows: In Windows When using HTTP: Infrastructure-Analtyics-Advisor-serverinstallation-destination-folder\Base64\uCPSB \httpsd\conf\user_httpsd.conf Change the port number in the following three lines: Listen Listen [::]:22015 #Listen :22015 Infrastructure-Analtyics-Advisor-serverinstallation-destination-folder\Analytics\conf \command_user.properties Change the port number in the following line: command.http.port = When using HTTPS: Infrastructure-Analtyics-Advisor-serverinstallation-destination-folder\Base64\uCPSB \httpsd\conf\user_httpsd.conf Changing Infrastructure Analytics Advisor system settings 135

136 Change the port number in the following three lines: Listen Listen [::]:22016 <VirtualHost *:22016> Infrastructure-Analtyics-Advisor-serverinstallation-destination-folder\Analytics\conf \command_user.properties Change the port number in the following line: command.https.port = In Linux When using HTTP: Infrastructure-Analtyics-Advisor-serverinstallation-destination-directory/Base64/uCPSB/ httpsd/conf/user_httpsd.conf Change the port number in the following three lines: Listen Listen [::]:22015 #Listen :22015 Infrastructure-Analtyics-Advisor-serverinstallation-destination-directory/Analytics/conf/ command_user.properties Change the port number in the following line: command.http.port = When using HTTPS: Infrastructure-Analtyics-Advisor-serverinstallation-destination-directory/Base64/uCPSB/ httpsd/conf/user_httpsd.conf Change the port number in the following three lines: Listen Listen [::]:22016 <VirtualHost *:22016> Infrastructure-Analtyics-Advisor-serverinstallation-destination-directory/Analytics/conf/ command_user.properties 136 Changing Infrastructure Analytics Advisor system settings

137 Change the port number in the following line: command.https.port = For Windows, edit the program shortcut as follows. Note: The default URL is: For Windows Server 2008 R2 1. From the Start menu, select All Programs > Hitachi Infrastructure Analytics Advisor > Infrastructure Analytics Advisor > HIAA Login to display properties. 2. Change the port number of the URL in Target. For Windows Server From the desktop, display the Start window. 2. Right-click the Start window to display All apps. 3. Display the HIAA Login property in the Hitachi Infrastructure Analytics Advisor folder. 4. Change the port number of the URL specified for URL in the Web Document tab. 4. Register the firewall exceptions. In Windows Run the hcmds64fwcancel command to set Windows-based firewall exceptions. In Linux Run the iptable command to register Linux firewall exceptions. 1. Open the firewall settings file (/etc/sysconfig/iptables), for example by using a text editor. 2. Insert the following line before the line "--reject-with icmp-hostprohibited": -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport port-number -j ACCEPT Note: Make sure that you enter the entire text in one line. Changing Infrastructure Analytics Advisor system settings 137

138 For port-number, enter the number of the port to be opened. You must specify the above setting for each port number. 3. Overwrite the firewall settings file to save the settings. 4. Restart the service. Execute the following command on the console: /etc/rc.d/init.d/iptables restart 5. Run the hcmds64srv command with the start option to start the Infrastructure Analytics Advisor server services. Related topics Starting the Infrastructure Analytics Advisor server service on page 130 Stopping the Infrastructure Analytics Advisor server service on page 130 hcmds64fwcancel on page 176 Changing the port number used between Infrastructure Analytics Advisor server and common component To change the port number used between Infrastructure Analytics Advisor server and common component, stop Infrastructure Analytics Advisor server services using the hcmds64srv command, change the port number in the definition file. Before you begin You must have the Administrator permission (for Windows) or the root permission (for Linux) of the OS to do this operation. Procedure 1. Run the hcmds64srv command with the stop option to stop the Infrastructure Analytics Advisor server services. 2. Edit the following definition files: In Windows Infrastructure-Analtyics-Advisor-server-installationdestination-folder\Base64\uCPSB\CC\web\redirector \workers.properties Change the port number in the following line: worker.analyticswebservice.port= Changing Infrastructure Analytics Advisor system settings

139 Infrastructure-Analtyics-Advisor-server-installationdestination-folder\Base64\uCPSB\CC\web\containers \AnalyticsWebService\usrconf\usrconf.properties Change the port number in: webserver.connector.ajp13.port and webserver.shutdown.port. : webserver.connector.ajp13.port=27100 : webserver.shutdown.port=27101 : In Linux Infrastructure-Analytics-Advisor-server-installationdestination-directory/Base64/uCPSB/CC/web/redirector/ workers.properties Change the port number in the following line: worker.analyticswebservice.port=27100 Infrastructure-Analytics-Advisor-server-installationdestination-directory/Base64/uCPSB/CC/web/containers/ AnalyticsWebService/usrconf/usrconf.properties Change the port number in: webserver.connector.ajp13.port and webserver.shutdown.port. : webserver.connector.ajp13.port=27100 : webserver.shutdown.port=27101 : 3. Run the hcmds64srv command with the start option to start the Infrastructure Analytics Advisor server services. Related topics Starting the Infrastructure Analytics Advisor server service on page 130 Stopping the Infrastructure Analytics Advisor server service on page 130 Changing the port number between Infrastructure Analytics Advisor server and the SMTP server You can change the port number used between Infrastructure Analytics Advisor server and the SMTP server in the Server Settings window. Changing Infrastructure Analytics Advisor system settings 139

140 Before you begin Make sure you have the Admin permission of Infrastructure Analytics Advisor server. Procedure 1. In the Administration tab, select Notification Settings > Server. 2. Click Edit Settings and enter the new port number in Port Number, and then click Save Settings. Changing the time settings of the Infrastructure Analytics Advisor server Stop the Infrastructure Analytics Advisor server services using the hcmds64srv command, and then change the time settings of the Infrastructure Analytics Advisor server. Before you begin You must have the Administrator permission (for Windows) or the root permission (for Linux) of the OS to do this operation. Procedure 1. Run the hcmds64srv command with the stop option to stop Infrastructure Analytics Advisor server service. 2. Change the time setting of the Infrastructure Analytics Advisor server. If you delayed the time settings of the server, wait until the change takes effect, and then do step Run the hcmds64srv command with the start option to start the Infrastructure Analytics Advisor server service. Related topics Starting the Infrastructure Analytics Advisor server service on page 130 Stopping the Infrastructure Analytics Advisor server service on page 130 Changing the format of output by Infrastructure Analytics Advisor server to syslog When using Infrastructure Analytics Advisor server, you can output records of user operations to syslog. Syslogs are listed using the following format: syslog-header-part message-part The format of the syslog-header-part differs depending on the OS environment settings. If necessary, change the settings. 140 Changing Infrastructure Analytics Advisor system settings

141 For example, if you use rsyslog and specify the following in /etc/ rsyslog.conf, messages are output in a format corresponding to RFC5424: $ActionFileDefaultTemplate RSYSLOG_SyslogProtocol23Format Moving an Infrastructure Analytics Advisor server installation to another host To move Infrastructure Analytics Advisor server to a host that has a different host name or IP address than that of the source host, first change the host name and IP address of the destination host to match those of the source host. After doing a restore operation, change the host name and IP address of the destination host back to their original values. Before you begin Stop the Infrastructure Analytics Advisor server services on the source server. Verify that the following items are the same on the source server and the destination server: System locale Environment for Hitachi Command Suite products (configuration, version number, revision number, and restriction code) Verify that Infrastructure Analytics Advisor server is not installed on the destination server. Procedure 1. Back up Infrastructure Analytics Advisor server on the source server. 2. Change the host name and IP address of the destination host to match those of the source host. 3. Install Infrastructure Analytics Advisor server on the destination server. The migration-destination directory of Infrastructure Analytics Advisor server must be the same on both the destination host and the source host. 4. Restore Infrastructure Analytics Advisor server on the destination server. 5. Change the host name and IP address of the destination host back to their original values by following the procedure for changing host names and IP addresses. 6. Verify that the destination server is running and then start operation. Result Infrastructure Analytics Advisor server is migrated to the destination host. Changing Infrastructure Analytics Advisor system settings 141

142 Related topics Installation on page 44 Installation on page 56 Changing the Infrastructure Analytics Advisor server host name on page 133 Changing the Infrastructure Analytics Advisor server IP address on page 134 Backing up Infrastructure Analytics Advisor server settings information on page 148 Restoring Infrastructure Analytics Advisor server settings information on page 152 Changing the system information of Analytics probe server This section contains procedures for changing port numbers used in Analytics probe server. Changing the port number used by the RAID Agent To change the port number used by the RAID Agent, use the jpcconf port command. Procedure 1. Run the following command to stop the RAID Agent services. /opt/jp1pc/htnm/bin/htmsrv stop -all 2. Run the jpcconf port command. For example, execute the command as follows: /opt/jp1pc/tools/jpcconf port define -key all 3. Configure a port number for each service. If the jpcconf port command is run, the system displays either the port number currently configured or the default port number. For example, the system displays the following if the port number is currently configured for the Name Server service: Component[Name Server] ServiceID[PN1001] Port[22285] : Tasks in this procedure might vary depending on how you set the port number. The following table shows port number settings and related tasks. Unless the port numbers conflict in the system, use the port numbers which display when you run the jpcconf port command. 142 Changing Infrastructure Analytics Advisor system settings

143 Setting Task When using the number displayed as a fixed port number as is Press Enter. When changing the displayed port number Specify a port number from 1024 to You cannot specify the port number currently in use. When not setting a fixed port number Specify 0. Even if 0 is specified for the following services, the default value is set: Name Server service Status Server service 4. Run the jpcconf port command again to make sure that the port number is configured correctly. For example, to display port numbers for all services, run the command as follows: /opt/jp1pc/tools/jpcconf port list key all If <error> is displayed in either the Services column or the Port column, the configuration is incorrect. Reset the port number. If an error still results, the following causes are possible: The port number is not registered in the services file. The same port number is registered more than once in the services file. Note: If the jpcconf port command is canceled with the Ctrl +C key, the port number is not set correctly. Run the jpcconf port command again and reset the port numbers. You do not need to change the port number for the Name Server service, because it will not be used. If you use the jpcconf port list command to display the port number for Status Server or use the jpcconf port define command to set the Status Server port number to 22350, the following message is displayed: For jpcconf port list: KAVE05919-E The port number is not registered correctly in the services file. For jpcconf port define: KAVE05918-W The specified port number is in use by another. In such cases, the following text is included in \etc\services: CodeMeter 22350/tcp Changing Infrastructure Analytics Advisor system settings 143

144 This text has been in the services file since the installation of the OS, regardless of whether the CodeMeter is actually installed. Check whether the CodeMeter is being used. If it is not being used, comment out the text. If the CodeMeter is being used or the port number is registered for a different product, make sure that there are no conflicting port numbers on the server. Changing the port number of the RAID Agent REST Web Service When a port number of the RAID Agent REST Web Service is changed, the settings of Hitachi Enterprise Storage Probe also change. Procedure 1. Run the following command to stop the RAID Agent services. /opt/jp1pc/htnm/bin/htmsrv stop -all 2. Use the table that follows to change the port number. Note that to change the port number, open the relevant file shown in the following table by using a text editor. Port Access port for Agent REST Web Service AJP port for Agent REST Application service Port number of RMI registry used by Agent REST Application service Port number server management commands used to communicate with Agent REST Application service Procedure for changing the port Change the Listen directive in the following file: /opt/jp1pc/htnm/rest/config/ htnm_httpsd.conf Change the values for the following properties. You must specify the same value for both properties. The worker.worker1.port property in the /opt/jp1pc/htnm/hbasepsb/cc/web/ redirector/workers.properties file The webserver.connector.ajp13.port property in the /opt/jp1pc/htnm/ HBasePSB/CC/server/userconf/ejb/ AgentRESTService/usrconf.properties file Change the value of the following property: The ejbserver.rmi.naming.port property in the /opt/jp1pc/htnm/hbasepsb/cc/server/ userconf/ejb/agentrestservice/ usrconf.properties file Change the value for the following property: The ejbserver.rmi.remote.listener.port property in the /opt/jp1pc/htnm/ HBasePSB/CC/server/userconf/ejb/ 144 Changing Infrastructure Analytics Advisor system settings

145 Port Procedure for changing the port AgentRESTService/usrconf.properties file Port number of the Agent REST Application Service simple Web server Change the value for the following property: The ejbserver.http.port property in the /opt/ jp1pc/htnm/hbasepsb/cc/server/ userconf/ejb/agentrestservice/ usrconf.properties file 3. Run the following command to start the RAID Agent services. /opt/jp1pc/htnm/bin/htmsrv start -all 4. When a port number of Agent REST Web Service is changed, you must change the settings of Hitachi Enterprise Storage Probe as follows: a. On the Analytics probe server home page, stop the target probe and click Edit. b. In the Edit Hitachi Enterprise Storage Probe section, enter the access port number of Agent REST Web Service in the RAID Agent Port field. Then, click Next. c. On the Validation window, click Next, and then click OK d. On the Status window, in Action, click Start to start collecting data. Backing up and restoring Infrastructure Analytics Advisor To back up or restore the entire Infrastructure Analytics Advisor system, you must perform operations for each server. The following information is subject to backup or restoration: Infrastructure Analytics Advisor server settings Data Center Analytics server settings Analytics probe server settings RAID Agent definition information, settings, and performance data The general backup procedure is as follows. (It applies to restore as well. 1. Stop the following services: Infrastructure Analytics Advisor server Data Center Analytics server Analytics probe server RAID Agent 2. Back up the following data: Infrastructure Analytics Advisor server settings Data Center Analytics server settings Changing Infrastructure Analytics Advisor system settings 145

146 Analytics probe server settings RAID Agent definition information, settings, and performance data 3. Start the following services: RAID Agent Analytics probe server Data Center Analytics server Infrastructure Analytics Advisor server Related topics Stopping services before a back up or restore on page 146 Backing up Infrastructure Analytics Advisor server settings information on page 148 Backing up the settings information and database of Data Center Analytics server on page 148 Backing up the settings information of Analytics probe server on page 149 Backing up the RAID Agent system on page 150 RAID Agent definition information files to backed up on page 151 Restoring Infrastructure Analytics Advisor server settings information on page 152 Restoring the settings information and database of Data Center Analytics server on page 154 Restoring Analytics probe server settings information on page 155 Restoring the RAID Agent system on page 156 Updating configuration information files that depend on the environment in which the RAID Agent is installed on page 158 Starting Infrastructure Analytics Advisor services after a backup or restore on page 158 Stopping services before a back up or restore Stop all Infrastructure Analytics Advisor services before you perform back up or restore tasks. Before you begin You must have the Administrator permission (for Windows) or the root permission (for Linux) of the Infrastructure Analytics Advisor server to do this operation. You must have the root permission for the Data Center Analytics server and the Analytics probe server. 146 Changing Infrastructure Analytics Advisor system settings

147 Procedure 1. From the Infrastructure Analytics Advisor server, run the following command to stop the Infrastructure Analytics Advisor server service: In Windows hcmds64srv /stop In Linux hcmds64srv -stop 2. From the Data Center Analytics server, do the following steps to stop the Data Center Analytics server service. a. Run the following command: crontab -e b. At the beginning of each line in the regular execution schedule for Data Center Analytics server, add a hash mark (#) to comment out a line as shown in this example. # */5 * * * * F=/usr/local/megha/cron.5min; test -f $F && bash $F # 13 0 * * * F=/usr/local/megha/cron.1hr; test -f $F && bash $F # 11 * * * * F=/usr/local/megha/cron.24hr; test -f $F && bash $F # */5 * * * * F=/usr/local/megha/bin/sysstat.sh; test -f $F && (bash $F >> /usr/local/megha/logs/sys/`date +\%Y\%m\ %d`.log) c. Run the following command to stop the service. sh /usr/local/megha/bin/megha-jetty.sh stop 3. Do the same step as the Data Center Analytics server on the Analytics probe server to stop the Analytics probe server service. 4. From the Analytics probe server, run the following command to stop the RAID Agent service. /opt/jp1pc/htnm/bin/htmsrv stop -all Result All of the services used by Infrastructure Analytics Advisor have been stopped. Related topics Starting the Infrastructure Analytics Advisor server service on page 130 Stopping the Infrastructure Analytics Advisor server service on page 130 Infrastructure Analytics Advisor server services on page 203 Changing Infrastructure Analytics Advisor system settings 147

148 Backing up Infrastructure Analytics Advisor server settings information To back up the settings information of Infrastructure Analytics Advisor server, run the backupsystem command. Before you begin You must have the Administrator permission (for Windows) or the root permission (for Linux) of the OS to do this operation. Before starting this operation, stop all services of the Infrastructure Analytics Advisor system. Procedure 1. Run the backupsystem command to back up the Infrastructure Analytics Advisor server settings information. Result The settings information of Infrastructure Analytics Advisor server is output to the specified directory. Related topics backupsystem on page 172 Backing up the settings information and database of Data Center Analytics server To back up the settings information and database of Data Center Analytics server, copy the directory containing the settings and database to an external storage device or a new host. Before you begin Stop all services of the Infrastructure Analytics Advisor system. Make sure that the location where the backup files are to be stored has sufficient space. You can estimate the amount of space required by adding the sizes of the directories to be backed up. Data-Center-Analytics-server-installation-directory/megha/ conf Data-Center-Analytics-server-installation-directory/megha/db Data-Center-Analytics-server-installation-directory/megha/ misc 148 Changing Infrastructure Analytics Advisor system settings

149 Procedure 1. Copy the following directories from the Data Center Analytics server to the backup destination: Data-Center-Analytics-server-installation-directory/megha/ conf Data-Center-Analytics-server-installation-directory/megha/db Data-Center-Analytics-server-installation-directory/megha/ misc Result The settings information and database of Data Center Analytics server have been backed up. Backing up the settings information of Analytics probe server To back up the settings information of Analytics probe server, copy the folder containing the settings to an external storage device or a new host. Before you begin Stop all services of the Infrastructure Analytics Advisor system. Make sure that the location where the backup files are to be stored has sufficient space. You can estimate the amount of space required by adding the sizes of the following directories that are to be backed up: Analytics-probe-server-installation-directory/megha/conf Analytics-probe-server-installation-directory/megha/db Analytics-probe-server-installation-directory/megha/misc Procedure 1. Back up the following directories on the Analytics probe server. All files and directories in Analytics-probe-server-installationdirectory/megha/conf All files and directories in Analytics-probe-server-installationdirectory/megha/db All files and directories in Analytics-probe-server-installationdirectory/megha/misc Changing Infrastructure Analytics Advisor system settings 149

150 Result The settings information of Analytics probe server has been backed up. Backing up the RAID Agent system To back up the entire RAID Agent system, use the htmhsbackup command to back up the performance data, the configuration information files, and some of the definition information files. Then, copy the remainder of the definition information files. Before you begin All services of the Infrastructure Analytics Advisor system must be stopped. Make sure that the directory to which backed-up data is to be output has sufficient free space. Data to be backed up Data to be backed up Performance data Backup method Use the htmhsbackup command Configuration information files Definition information files Definition information files whose type is "Agent" Use the htmhsbackup command. Definition information files whose type is "Common" or "Template" Copy these files manually. Procedure 1. Run the following command to back up the performance data, the configuration information files, and the definition information files whose type is "Agent". /opt/jp1pc/htnm/bin/htmhsbackup -dir output-directory 2. To back up the definition information files whose type is "Common" or "Template", manually copy these files to a directory. Result The entire RAID Agent system has been backed up. Related topics RAID Agent definition information files to backed up on page Changing Infrastructure Analytics Advisor system settings

151 RAID Agent definition information files to backed up The following table lists the RAID Agent definition information files that are to backed up. Type Definition information file name Description Common (to be backed up manually) Template (to be backed up manually) Agent (to be backed up by using the htmhsbackup command) /opt/jp1pc/jpchosts /opt/jp1pc/*.ini /opt/jp1pc/bin/action/*.ini /opt/jp1pc/bin/statsvr/*.ini /opt/jp1pc/agtd/agent/ jpcagt.ini.instmpl /opt/jp1pc/xxxx/*.ini 1 /opt/jp1pc/xxxx/agent/*.ini 1 /opt/jp1pc/xxxx/agent/instancename/*.ini 1 and 2 /opt/jp1pc/xxxx/agent/instancename/system/*.ini 1 and 2 /opt/jp1pc/xxxx/store/*.ini 1 /opt/jp1pc/xxxx/store/instancename/*.ini 1 and 2 /opt/jp1pc/xxxx/agent/instancename/raidperf_ldevlist.conf 1 and 2 /opt/jp1pc/htnm/agent/config/ alertglobalconfig.ini /opt/jp1pc/htnm/agent/config/ apidataglobalconfig.ini /opt/jp1pc/htnm/agent/config/ dbdataglobalconfig.ini /opt/jp1pc/htnm/agent/system/ data_file_manage /opt/jp1pc/htnm/agent/system/ data_file_manage.ini /opt/jp1pc/htnm/agent/system/ systemenv.properties /opt/jp1pc/htnm/agent/system/ sdblogger.properties /opt/jp1pc/htnm/hbasepsb/cc/ server/usrconf/ejb/ AgentRESTService/usrconf.cfg /opt/jp1pc/htnm/hbasepsb/cc/ server/usrconf/ejb/ AgentRESTWebService/ usrconf.properties /opt/jp1pc/htnm/hbasepsb/cc/web/ redirector/mod_jk.conf Settings file containing RAID Agent host information Settings file of the RAID Agent Settings file of the RAID Agent Settings file of the RAID Agent Internal file Internal file Settings file of the RAID Agent Settings file of the RAID Agent Internal file Settings file of the RAID Agent Settings file of the RAID Agent Internal file Settings file for s sent by the Alert function Settings file of the REST API component of the RAID Agent Settings file of the REST API component of the RAID Agent Internal control file Internal control file Internal control file Internal control file Option definition file for Java applications User properties file for Java applications Definition file for Redirector actions of HTTP server Changing Infrastructure Analytics Advisor system settings 151

152 Type Definition information file name Description /opt/jp1pc/htnm/hbasepsb/cc/web/ redirector/workers.properties /opt/jp1pc/htnm/rest/config/ htnm_httpsd.conf /opt/jp1pc/htnm/rest/config/ user.properties /opt/jp1pc/htnm/rest/system/ sysconf/system.properties Notes: 1. xxxx represents the agent identifier agtd. Worker definition file Definition file for the HTTP server (to be edited by the user) User settings properties file for the REST API component of the RAID Agent System settings file (The settings in this file are not disclosed.) 2. The number of instance-name directories is the same as the number of instances. Restoring Infrastructure Analytics Advisor server settings information To restore the settings information of Infrastructure Analytics Advisor server, run the restoresystem command. After restoration, specify the settings related to communication between Infrastructure Analytics Advisor server and the web client on the new host. Before you begin You must have the Administrator permission (for Windows) or the root permission (for Linux) of the OS to do this operation. Before starting this operation, stop all services of the Infrastructure Analytics Advisor system. Run the backupsystem command to create backup data. Make sure that the following items are the same between the backupsource host and the restoration-destination host: Infrastructure-Analytics-Advisor-server-installation-destination-directory Version number, revision number, and restriction code of the installed instance of Infrastructure Analytics Advisor server You can check the version number, revision number, and restriction code of Infrastructure Analytics Advisor server in the Version window. Host name If you are doing restoration as part of the procedure for changing the host name of the Infrastructure Analytics Advisor server or the procedure for migrating the system to a host of a different host name, the host names of the backup-source host and restoration-destination host do not need to match. IP address 152 Changing Infrastructure Analytics Advisor system settings

153 System locale Procedure 1. Run the restoresystem command to restore the settings information of Infrastructure Analytics Advisor server. 2. Edit the definition files below based on the environment where the information is to be restored. The definition files below are backed up but will not be restored. For this reason, they must be edited. Security definition file (security.conf) File for setting port numbers and host names (user_httpsd.conf) These files are backed up in the following directories: In Windows backup-folder\hbase\base\conf\sec backup-folder\hbase\base\httpsd.conf In Linux backup-directory/hbase/base/conf/sec backup-directory/hbase/base/httpsd.conf 3. If HTTPS connections are to be used between Infrastructure Analytics Advisor server and the web client on the new host, enable HTTPS connections. 4. If you changed the port number for communication between Infrastructure Analytics Advisor server and the web client on the new host, re-set the port number in accordance with the procedure for changing port numbers. Result The settings information of Infrastructure Analytics Advisor server has been restored to the specified host, and Infrastructure Analytics Advisor server can now be used. Related topics Enabling SSL communication for the Infrastructure Analytics Advisor server on page 112 Changing the SSL port number between the Infrastructure Analytics Advisor server and a web client on page 124 restoresystem on page 198 Changing Infrastructure Analytics Advisor system settings 153

154 Restoring the settings information and database of Data Center Analytics server To restore the settings information and database of Data Center Analytics server, copy the backed-up data to the restoration-destination host, and then change the owner of the restored data. Before you begin Stop all services of the Infrastructure Analytics Advisor system. Make sure that the restore has sufficient space. You can estimate the amount of space by adding the sizes of the following directories that were backed up: Data-Center-Analytics-server-installation-directory/megha/ conf Data-Center-Analytics-server-installation-directory/megha/db Data-Center-Analytics-server-installation-directory/megha/ misc Make sure that the following items are the same between the backupsource host and the restore-destination host: Data-Center-Analytics-server-installation-directory Version number, revision number, and restriction code of the installed instance of Data Center Analytics server Host name IP address System locale Procedure 1. Copy the following backed-up data to the new host: All files and directories in Data-Center-Analytics-serverinstallation-directory/megha/conf All files and directories in Data-Center-Analytics-serverinstallation-directory/megha/db All files and directories in Data-Center-Analytics-serverinstallation-directory/megha/misc 154 Changing Infrastructure Analytics Advisor system settings

155 2. Run the following command on the restore-destination host to change the owner of the data. chown -R megha:megha Data-Center-Analytics-serverinstallation-directory/megha/ Result The settings information and database of Data Center Analytics server have been restored to the new host. Restoring Analytics probe server settings information To restore the settings information of Analytics probe server, copy the backed-up data to the restoration-destination host, and then change the owner of the restored data. Before you begin Before starting this operation, stop all services of the Infrastructure Analytics Advisor system. Make sure that the restoration destination has sufficient space. The required amount of space can be estimated by adding the sizes of the following directories that were backed up: Analytics-probe-server-installation-directory/megha/conf Analytics-probe-server-installation-directory/megha/db Analytics-probe-server-installation-directory/megha/misc Make sure that the following items are the same between the backupsource host and the restoration-destination host: Analytics-probe-server-installation-directory Version number, revision number, and restriction code of the installed instance of Analytics probe server Host name IP address System locale Procedure 1. Copy the following backed-up data to the new host: All files and directories in Analytics-probe-server-installationdirectory/megha/conf Changing Infrastructure Analytics Advisor system settings 155

156 All files and directories in Analytics-probe-server-installationdirectory/megha/db All files and directories in Analytics-probe-server-installationdirectory/megha/misc 2. Run the following command on the restoration-destination host to change the owner of the data. chown -R megha:megha /megha/ Result The settings information of Analytics probe server has been restored to the new host. Restoring the RAID Agent system To restore the entire RAID Agent system, use the htmhsrestore command to restore each type of data, and then manually restore the definition information files. After that, edit some of the configuration information files. Before you begin The performance data and configuration information files must be backed up by using the htmhsbackup command. All services of the RAID Agent must be stopped on the restorationdestination host. The version number and revision number of the RAID Agent on the restoration-destination host must be the same as those of the RAID Agent used when the data was backed up. The output directory for Hybrid Store must have sufficient space. The instance name of the backed-up data must match the instance name on the restoration-destination host. Setup of the instance on the restoration-destination host must be complete. The OS of the restoration destination must be the same as that of the backup source. Data to be restored Performance data Data to be restored Restoration method Restore by using the htmhsrestore command. 156 Changing Infrastructure Analytics Advisor system settings

157 Data to be restored Configuration information files Restoration method Configuration information files that do not depend on the installation environment Restore by using the htmhsrestore command. Configuration information files that depend on the installation environment These files are not restored. Definition information files Definition information files whose type is "Agent" Restore by using the htmhsrestore command. Definition information files whose type is "Common" or "Template" Manually copy and paste these files. Procedure 1. Run the following command to make sure the RAID Agent service has stopped. /opt/jp1pc/htnm/bin/htmsrv status -all If the service is running, run the following command to stop the RAID Agent service. /opt/jp1pc/htnm/bin/htmsrv stop -all 2. Run the following command to restore the backed-up performance data and configuration information files. /opt/jp1pc/htnm/bin/htmhsrestore dir storage-directory-ofthe-backed-up-data 3. Run the jpctdchkinst command to check whether the restored instance is monitoring the monitored targets correctly. 4. If the restored instance is not properly monitoring the monitored targets, run the jpcconf inst setup command to change the settings, and then run the jpctdchkinst command again to check the monitoring status. 5. Copy and paste the definition information files whose type is "Common" or "Template" to the restoration destination. 6. Update the configuration information files that depend on the installation environment. 7. To use the Alert function, synchronize the alert definition information. Result The entire RAID Agent system has been restored. Changing Infrastructure Analytics Advisor system settings 157

158 Related topics RAID Agent definition information files to backed up on page 151 Updating configuration information files that depend on the environment in which the RAID Agent is installed on page 158 Updating configuration information files that depend on the environment in which the RAID Agent is installed Of the RAID Agent configuration information files, the files containing information that depends on the installation environment are not restored by the htmhsrestore command. If necessary, update the configuration information files in the restoration destination. The following table describes configuration information files that must be updated. Configuration information files that must be updated /opt/jp1pc/htnm/rest/config/ htnm_httpsd.conf Description Update the following items as needed. Port number SSL communication settings /opt/jp1pc/htnm/hbasepsb/cc/web/ redirector/workers.properties /opt/jp1pc/htnm/hbasepsb/cc/ server/usrconf/ejb/ AgentRESTService/ usrconf.properties If you changed the port numbers described in workers.properties and usrconf.properties in the backup-source environment, also change them in the restoration-destination environment. Starting Infrastructure Analytics Advisor services after a backup or restore After backing up or restoring the entire Infrastructure Analytics Advisor system, start all of the services used by Infrastructure Analytics Advisor. Before you begin You must have the Administrator permission (for Windows) or the root permission (for Linux) of the Infrastructure Analytics Advisor server to do this operation. You must have the root permission for the Data Center Analytics server and the Analytics probe server to do this operation. Procedure 1. From the Analytics probe server, run the following command to start the RAID Agent service. /opt/jp1pc/htnm/bin/htmsrv start -all 158 Changing Infrastructure Analytics Advisor system settings

159 2. Check htmrestdbenginemessage#.log of the RAID Agent to make sure that the KATR13248-E message is not logged before KATR13244-I was output. After the RAID Agent service is started, it might take up to an hour before KATR13244-I is output. 3. From the Analytics probe server, do the following steps to start the Analytics probe server service. a. Run the following command: crontab -e b. From the beginning of each line in the ordinary execution schedule that was output for Analytics probe server, delete the hash mark (# ) as follows: */5 * * * * F=/usr/local/megha/cron.5min; test -f $F && bash $F 13 0 * * * F=/usr/local/megha/cron.1hr; test -f $F && bash $F 11 * * * * F=/usr/local/megha/cron.24hr; test -f $F && bash $F */5 * * * * F=/usr/local/megha/bin/sysstat.sh; test -f $F && (bash $F >> /usr/local/megha/logs/sys/`date +\%Y\%m\ %d`.log) c. Run the following command to start the service. sh /usr/local/megha/bin/megha-jetty.sh start 4. Do the same step as the Analytics probe server on the Data Center Analytics server to start the Data Center Analytics server service. 5. From the Infrastructure Analytics Advisor server, run the following command to start the Infrastructure Analytics Advisor server service. In Windows hcmds64srv /start In Linux hcmds64srv -start Result All of the services used by Infrastructure Analytics Advisor are running. Related topics Starting the Infrastructure Analytics Advisor server service on page 130 Stopping the Infrastructure Analytics Advisor server service on page 130 Infrastructure Analytics Advisor server services on page 203 Changing Infrastructure Analytics Advisor system settings 159

160 Enabling system account locking In Infrastructure Analytics Advisor server, you can configure on a web client basic user-related settings, such as those related to user registration and passwords. This section describes the optional settings that cannot be configured on a web client. When Infrastructure Analytics Advisor server is initially installed, the locking of the system account is disabled. For security purposes, you may want to lock the system account. Note: Locking or unlocking an account requires user management permissions. You cannot unlock your own account on a web client, but you can unlock your own account on the Infrastructure Analytics Advisor server. Procedure 1. Stop the Infrastructure Analytics Advisor server. 2. Create a user.conf file in the following location: In Windows In Linux Infrastructure-Analytics-Advisor-server-Installationdestination-folder\Base64\conf\ Infrastructure-Analytics-Advisor-server-Installationdestination-directory/Base64/conf/ 3. Add the following property account.lock.system=[true false], and set the value to true to enable system account locking, then save the file. If you do not want to lock the system account, specify false. 4. Start the Infrastructure Analytics Advisor server services. Related topics Starting the Infrastructure Analytics Advisor server service on page 130 Stopping the Infrastructure Analytics Advisor server service on page Changing Infrastructure Analytics Advisor system settings

161 12 Removing Infrastructure Analytics Advisor components This section describe how to remove Infrastructure Analytics Advisor components. Removing Infrastructure Analytics Advisor server from a Windows host Removing Infrastructure Analytics Advisor server and Data Center Analytics server Removing Analytics probe server Removing Infrastructure Analytics Advisor components 161

162 Removing Infrastructure Analytics Advisor server from a Windows host This section describes how to remove Infrastructure Analytics Advisor server from a Windows host. Procedure 1. Log on to the Infrastructure Analytics Advisor server by using a user account with the Administrator permission. 2. Stop the security monitoring software, antivirus software, and process monitoring software. 3. Stop the services of products that use Common Component. To identify these services, see the Infrastructure Analytics Advisor server Services appendix. If the Common Component services are running, a dialog box prompting you to stop these services appears. 4. Set Startup type for the Infrastructure Analytics Advisor server services to Automatic or Manual. In Windows environment, if the Startup type is set to Disabled, the removal process might fail because the services cannot be started. 5. To remove Infrastructure Analytics Advisor server, go to Control Panel > Programs > Programs and Features and select Hitachi Infrastructure Analytics Advisor, and then click Uninstall. The settings files remain in the installation folder. You must delete the settings files manually as necessary. Related topics Infrastructure Analytics Advisor server services on page 203 Removing Infrastructure Analytics Advisor server and Data Center Analytics server This section describes how to remove Infrastructure Analytics Advisor server and Data Center Analytics server from a Linux host. You can choose that you remove only one program. Procedure 1. Log on to the Infrastructure Analytics Advisor server or Data Center Analytics server by using a user account with the root permission. 2. Stop the security monitoring software, antivirus software, and process monitoring software. 3. Run the following command: sh./analytics_uninstall.sh SYS 162 Removing Infrastructure Analytics Advisor components

163 Copy analytics_uninstall.sh from the installation media before using it. 4. Following the prompt, select the program to be removed, and then complete the uninstallation process. Removing Analytics probe server This section describes how to remove Analytics probe server from a Linux host. Procedure 1. Log on to the Analytics probe server by using a user account with the root permission. 2. Stop the security monitoring software, antivirus software, and process monitoring software. 3. Run the following command: sh./dcaprobe_uninstall.sh SYS Copy dcaprobe_uninstall.sh from the installation media before using it. Removing Infrastructure Analytics Advisor components 163

164 164 Removing Infrastructure Analytics Advisor components

165 13 Troubleshooting This section describes how to troubleshoot common Infrastructure Analytics Advisor server problems. 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 be connected to Data Center Analytics server Troubleshooting 165

166 Connection to the Infrastructure Analytics Advisor server web client unsuccessful If you cannot connect to the Infrastructure Analytics Advisor server web client check the operation status of Infrastructure Analytics Advisor server and the port number setting. Procedure 1. Run the hcmds64srv command with the status option to check the operation status of Infrastructure Analytics Advisor server. If the services "HAnalytics Engine Web Service" and "HBase 64 Storage Mgmt SSO Service" are running, and the service "HBase 64 Storage Mgmt Web Service" is not running, a port number might be redundant. 2. Check the event log. If the following log is output, review the configuration of port numbers used by the Infrastructure Analytics Advisor server: Item Contents Level Source Error HitachiWebServer Message Message: The service named HBase 64 Storage Mgmt Web Service reported the following error: >>> (OS 10048) Only one usage of each socket address (protocol/network address/port) is normally permitted. : make_sock: could not bind to address [::]:[redundant-port-number] 3. From the web browser, confirm that communication with the Infrastructure Analytics Advisor server is normal. 4. Confirm that the web browser is supported by Infrastructure Analytics Advisor server. For details about the types of web browsers supported by Infrastructure Analytics Advisor server, see the Browser requirements. Related topics hcmds64srv on page 185 Infrastructure Analytics Advisor server services on page 203 Logging on to Infrastructure Analytics Advisor server unsuccessful When you cannot log on to Infrastructure Analytics Advisor server, check your user information: 166 Troubleshooting

167 1. Confirm that the user ID and password are correct. 2. Confirm that the user is registered in Infrastructure Analytics Advisor server. 3. Ask a user with User Management permissions to confirm the following: User has required permissions User account is not locked Starting Infrastructure Analytics Advisor server does not work If Infrastructure Analytics Advisor server cannot start, check that the resources of the Infrastructure Analytics Advisor server are sufficient, and the hardware and OS are supported by Infrastructure Analytics Advisor server. Procedure 1. Confirm that resources such as memory and disk space are sufficient on the Infrastructure Analytics Advisor server 2. Confirm that Infrastructure Analytics Advisor server has been installed on the OS and hardware supported by Infrastructure Analytics Advisor server. For details about the types of hardware and OSs supported by Infrastructure Analytics Advisor server, see the Infrastructure Analytics Advisor server requirements. 3. Run the hcmds64srv command with the status option to check the operation status of Infrastructure Analytics Advisor server. 4. If the Infrastructure Analytics Advisor server service is not running, start the service. 5. See the log data and take appropriate actions from the error message. 6. If no error message is output to the log, or the problem is not solved, run the hcmds64getlogs command to collect the log file, and contact the administrator or Hitachi customer support. Related topics hcmds64getlogs on page 177 hcmds64srv on page 185 Infrastructure Analytics Advisor server services on page 203 Troubleshooting 167

168 Infrastructure Analytics Advisor server cannot be connected to Data Center Analytics server If Infrastructure Analytics Advisor server cannot be connected to Data Center Analytics server, check the operating status of Data Center Analytics server and the status of the connection between Infrastructure Analytics Advisor server and Data Center Analytics server. Procedure 1. Run the following command on the Data Center Analytics server to verify that the status of the service of the Data Center Analytics server is "Running": /usr/local/megha/bin/megha-jetty.sh status Output example: Megha server is running 2. In the Administration tab of Infrastructure Analytics Advisor server, select System Settings > HDCA Server. 3. Click Edit Settings to check information about the Data Center Analytics server. 4. Click Check Connection to check whether Infrastructure Analytics Advisor server can be properly connected to the Data Center Analytics server. 5. Click OK. Related topics Setting up a connection with Data Center Analytics server on page Troubleshooting

169 A Infrastructure Analytics Advisor CLI commands This appendix describes the commands of Infrastructure Analytics Advisor server. List of Commands Command usage notes Usable characters for command arguments backupsystem encryptpassword hcmds64fwcancel hcmds64getlogs hcmds64intg hcmds64srv hcmds64ssltool hcmds64unlockaccount reloadtemplate restoresystem Infrastructure Analytics Advisor CLI commands 169

170 List of Commands This section lists the Infrastructure Analytics Advisor server commands: Command backupsystem encryptpassword hcmds64fwcancel hcmds64getlogs hcmds64intg hcmds64srv hcmds64ssltool hcmds64unlockaccount reloadtemplate restoresystem Description Backs up Infrastructure Analytics Advisor server setting information in the folder you specify. Creates a password file to be specified as an argument of commands in Infrastructure Analytics Advisor server. Registers an exception so that communication between the Infrastructure Analytics Advisor server and the web browser is not blocked by the Windows-based firewall. Collects log files that are output during operation of Infrastructure Analytics Advisor server, and then outputs the log files to an archive file. Deletes authentication data registered in the repository of the server that manages user accounts. The command also displays the address of the server in which the authentication data is registered. If you fail to delete authentication data when uninstalling Infrastructure Analytics Advisor server, use this command to delete the authentication data. Starts or stops Infrastructure Analytics Advisor server services and databases. The command also displays the status of Infrastructure Analytics Advisor server services. Creates private keys, CSRs, and self-signed certificates (including its content files), which are required for SSL connection. Unlocks a user account. Use this command when you cannot log on to Infrastructure Analytics Advisor server because all the user accounts are locked. Reload the Infrastructure Analytics Advisor server template files during the startup of Infrastructure Analytics Advisor server. Restores the backup for Infrastructure Analytics Advisor server settings or database information that you collected by running the backupsystem command. Command usage notes The following describes the notes that you need to consider when using commands. To interrupt command running, press Ctrl+C at the same time. If you interrupt command running, make sure that you read the message issued at the interruption of the command to check for any problems. If necessary, return the command. If you interrupt running command, the return value might become undefined. In Windows 170 Infrastructure Analytics Advisor CLI commands

171 If the command is to be run in an environment where User Account Control (UAC) of Windows-based system is valid requires the Administrator permission, run the command from the administrator console of Infrastructure Analytics Advisor server. To display the administrator console: For Windows Server 2008 R2 1. In the Start menu, select All Programs, Hitachi Infrastructure Analytics Advisor, and then Analytics Command. For Windows Server From the desktop, display the Start window. 2. Right-click the Start window to display All apps. 3. In the Hitachi Infrastructure Analytics Advisor folder, select Analytics Command. If you enable Quick Edit Mode in the command prompt, and then click the mouse in the window, the window output is stopped until the quick edit mode is canceled. Therefore, we recommend that you do not use the quick edit mode. In Linux When the maximum output size of the core file is 0, a core dump will not be output. To output a core dump when a failure occurs, run the ulimit command before running each command, and set the maximum output size of the core file to unlimited. Usable characters for command arguments You can specify the following characters for command arguments: The specification method for command arguments must comply with the specifications of the OS command prompt. Therefore, if an argument value contains a space ( ) or special symbols, you must escape such characters by enclosing each of the characters with double quotation marks ("). You can use the following types of characters when specifying a path with an argument of a command: Alphanumeric characters, underscores (_), periods (.), hyphens (-), spaces ( ), left parentheses ( ( ), right parentheses ( ) ), hash marks (#), at marks (@), colons (:), and backslash (\) Infrastructure Analytics Advisor CLI commands 171

172 You can use a colon only as a drive delimiter. You can use a backslash (\) only as a folder delimiter. When specifying a path in an argument, you cannot use a path in UNC format. When specifying a path in an argument, you cannot use a path that has a folder name that begins or ends with a space. Also, you cannot specify a folder name that consists of only spaces. When specifying a path in an argument, you cannot use a path that has a folder name that begins or ends with a period (.). Also, you cannot specify a folder name that consists of only periods. Unless otherwise stated, the path length is from 1 to 230 characters in the absolute path. Unless otherwise stated, each command argument is case-sensitive. Do not specify reserved words for the OS as a file name or folder name. backupsystem Use this command to back up Infrastructure Analytics Advisor server setting information in the directory you specified. Format In Windows backupsystem /dir output-folder /type {all Analytics} [/auto] In Linux backupsystem -dir output-directory -type {all Analytics} [-auto] Options dir output-directory Specify the directory in which the backup file is stored with the absolute or relative path. type {all Analytics} 172 Infrastructure Analytics Advisor CLI commands

173 auto Specify the type of information for backup. all Backs up Infrastructure Analytics Advisor server and common component. Common component manages the user information. Analytics Backs up only Infrastructure Analytics Advisor server. Automatically stops or starts services and databases of Infrastructure Analytics Advisor server and products that use common component. If you omit this option, these services and databases are not automatically stopped or started. Storage location In Windows In Linux Infrastructure-Analytics-Advisor-server-installationdestination-folder\Analytics\bin Infrastructure-Analytics-Advisor-server-installationdestination-directory/Analytics/bin Permissions Administrator permission(for Windows) or a root user permission(for Linux). Notes Make sure that the directory in which the backup file is to be stored has sufficient free space. Use the following formula to calculate the required amount of free space: In Windows 5 GB + Size of Infrastructure-Analytics-Advisor-serverinstallation-destination-folder\Analytics\data In Linux 5 GB + Size of Infrastructure-Analytics-Advisor-serverinstallation-destination-directory/Analytics/data If products that use common component are installed on the Infrastructure Analytics Advisor server, add the capacity required to back up information for those products. Infrastructure Analytics Advisor CLI commands 173

174 The following files for HTTPS connections are not backed up. If necessary, back up these files manually. SSL server certificate file Private-key file In addition, the files for HTTPS connections are defined in the httpsd.conf file and the user_httpsd.conf file. If all of the following conditions are met, use the hcmds64srv command to stop the service before running the backupsystem command. The auto option is not specified. all is specified for the type option. If products that use common component are installed on the Infrastructure Analytics Advisor server, run the restoresystem command by specifying type Analytics to restore only Infrastructure Analytics Advisor server. You can back up the data required for restoring only Infrastructure Analytics Advisor server by specifying type Analytics for the backupsystem command. Return values Return value Description 0 The command ran normally. 1 The argument is invalid. 2 Command running was interrupted. 3 The service status is invalid. 4 Another command is currently running. 7 The path is invalid. 9 The path does not exist. 10 The path cannot be accessed. 11 The directory is not empty. 14 You do not have permission to run this command. 100 The backup operation failed. 101 The start or stop of the service failed. 255 Command running was interrupted because of another error. 174 Infrastructure Analytics Advisor CLI commands

175 Example The following example shows the use of this command to back up information of Infrastructure Analytics Advisor server: backupsystem /dir "C:\Users\Backup" /type Analytics /auto encryptpassword Use this command to generate a password file to be specified as the argument of a command in Infrastructure Analytics Advisor server. To generate a password file, the user must be registered in Infrastructure Analytics Advisor server. Format In Windows encryptpassword /user user-id /password password /passwordfile password-file-path In Linux encryptpassword -user user-id -password password -passwordfile password-file-path Options user user-id Specify the user ID of the Infrastructure Analytics Advisor server user for whom you want to create a password file. password password Specify the password of the user specified in the user option. passwordfile password-file-path Use an absolute or relative path to specify a path of the password file to be created. Storage location In Windows Infrastructure-Analytics-Advisor-server-installationdestination-folder\Analytics\bin Infrastructure Analytics Advisor CLI commands 175

176 In Linux Infrastructure-Analytics-Advisor-server-installationdestination-directory/Analytics/bin Permissions Administrator permission(for Windows) or a root user permission(for Linux). Return values Return value Description 0 The command ran normally. 1 The argument is invalid. 2 Command running was interrupted. 3 The service status is invalid. 4 An exclusion error occurred. 5 Communication failed. 6 Authentication failed. (The specified value is invalid.) 7 The path is invalid. 8 The output destination path exists. 9 The path does not exist. 10 The path cannot be accessed. 14 You do not have permission to run this command. 200 The password file could not be generated. 255 Command running was interrupted because of another error. hcmds64fwcancel Use this command to register an exception so that communication between the Infrastructure Analytics Advisor server and the web browser is not blocked by the Windows-based firewall. Format hcmds64fwcancel Storage location In Windows Infrastructure-Analytics-Advisor-server-installationdestination-folder\Base64\bin In Linux Infrastructure-Analytics-Advisor-server-installationdestination-directory/Base64/bin 176 Infrastructure Analytics Advisor CLI commands

177 Permissions Administrator permission(for Windows) or a root user permission(for Linux). Return values This command has no return value. To determine whether the processing ran normally, check whether HBase (Web) is correctly registered in the inbound rules of the Windows-based firewall. You can check the inbound rules for Windows Firewall in the Windowsbased system control panel. hcmds64getlogs Use this command to collect log files that are output during operation of Infrastructure Analytics Advisor server, and then output the log files to an archive file. Format In Windows hcmds64getlogs /dir output-folder-path [/types Analytics] [/arc archive-file-name] [/logtypes {log db csv}] In Linux hcmds64getlogs -dir output-directory-path [-types Analytics] [-arc archive-file-name] [-logtypes {log db csv}] Options dir output-folder-path-or-output-directory-path Specify the folder path or directory path for outputting the archive file. You can specify only a folder or directory of a local disk. As the output folder path or output directory path, specify an empty folder or directory in absolute or relative path format. If the folder path or directory path does not exist, the folder or directory is created automatically. The maximum allowable path length is 100 characters. The Write permission is set for the folder or directory you specify in this option. Infrastructure Analytics Advisor CLI commands 177

178 types Analytics Specify Analytics as the product name of the target of log file collection. This is not case-sensitive. If you omit this option, Infrastructure Analytics Advisor server and all Hitachi Command Suite products that have been installed are subject to the command processing. In this case, log collection might take while. arc archive-file-name Specify the name of the archive file to be created as the result of common component's material collection tool. If you omit this option, the archive file name is HiCommand_log. Archive files are output under the folder or directory in the dir option. Characters that can be specified as the archive file name include printable ASCII characters (0x20 to 0x7E), excluding the following special characters: Backslashes (\), slashes (/), colons (:), commas (,), semicolons (;), asterisks (*), question marks (?), double quotation marks ("), left angle brackets (<), right angle brackets (>), vertical bars ( ), dollar signs ($), percent signs (%), ampersands (&), single quotation marks ('), and grave accent marks (`) You do not need to specify an extension. logtypes {log db csv} Specify the type of the log file for common component for which you want to collect logs. The following table shows the correspondence between the log file type and the log files that can be collected: Log file type Archive file to be created log Archive file name in the arc option_64.jar Archive file name in the arc option_64.hdb.jar db csv Archive file name in the arc option_64.db.jar Archive file name in the arc option_64.csv.jar If you omit this option, all log files of common component are collected. Therefore, we recommend that you run the command by omitting the option. To specify more than one type, use a space as a delimiter (for example, logtypes log db csv). If you use the types option and the logtypes option at the same time, specify log as the value of the logtypes option. Output format The following table lists the log files collected using the hcmds64getlogs command. 178 Infrastructure Analytics Advisor CLI commands

179 Table 24 In Windows Archive file output-destination-folder-indir-option\archive-file-name-inarc-option_64.jar Output result All files in Infrastructure-Analytics-Advisorserver-installation-destination-folder \Analytics\logs All files in Infrastructure-Analytics-Advisorserver-installation-destination-folder \Analytics\conf All files in Infrastructure-Analytics-Advisorserver-installation-destination-folder \Analytics\work All files in Infrastructure-Analytics-Advisorserver-installation-destination-folder \Analytics\data All files in Infrastructure-Analytics-Advisorserver-installation-destination-folder \Analytics\system All files in Windows-folder # \Temp\ HITACHI_HICOMMAND_INST_LOG List of the files in Infrastructure-Analytics- Advisor-server-installation-destination \Analytics List of the registry keys in HKEY_LOCAL_MACHINE \SOFTWARE\HITACHI\ hosts file services file Result of running the ipconfig command of the OS Result of running the netstat command of the OS with the na option specified Result of running the msinfo32 command of the OS with the report option specified Result of running the systeminfo command of the OS Result of running common component's material collection tool (hcmdsgetlogs, hcmdsras) output-destination-folder-in- Result of running common component's material collection tool (hcmdsgetlogs) dir-option\archive-file-name-in- arc-option_64.hdb.jar output-destination-folder-in- dir-option\archive-file-name-in- arc-option_64.db.jar Infrastructure Analytics Advisor CLI commands 179

180 Archive file Output result output-destination-folder-indir-option\archive-file-name-inarc-option_64.csv.jar # By default, this is C:\WINDOWS. Table 25 In Linux Archive file output-destination-directory-indir-option/archive-file-name-inarc-option_64.jar Output result All files in Infrastructure-Analytics-Advisorserver-installation-destination-directory/ Analytics/logs All files in Infrastructure-Analytics-Advisorserver-installation-destination-directory/ Analytics/conf All files in Infrastructure-Analytics-Advisorserver-installation-destination-directory/ Analytics/work All files in Infrastructure-Analytics-Advisorserver-installation-destination-directory/ Analytics/data All files in Infrastructure-Analytics-Advisorserver-installation-destination-directory/ Analytics/system All files in /tmp/hiaa/* List of the files in Infrastructure-Analytics- Advisor-server-installation-destination/ Analytics Result of running the netstat command of the OS with the -nao option specified Result of running the uname command of the OS with the -a option specified Result of running the free command of the OS Result of running the ps command of the OS with the - elfa option specified /var/log/messages* files /etc/hosts file /etc/services file Result of running the env command of the OS Result of running the sysctl command of the OS with the -a option specified 180 Infrastructure Analytics Advisor CLI commands

181 Archive file Output result Result of running the ulimit command of the OS with the -a option specified Result of running the ipcs command of the OS with the -a option specified Result of running the cat /proc/meminfo command of the OS Result of running the df command of the OS with the - k option specified Result of running the dmesg command of the OS Result of running the rpm command of the OS with the -qa option specified /etc/inittab file /etc/redhat-release file /etc/nsswitch.conf file /etc/resolv.conf file Result of running the ip command of the OS with the - a option specified /etc/.hitachi/analytics/installinfo file /etc/sysconfig/iptables-config file Result of running the service iptables status command of the OS Result of running common component's material collection tool (hcmdsgetlogs, hcmdsras) output-destination-directory-in- Result of running common component's material collection tool (hcmdsgetlogs) dir-option/archive-file-name-in- arc-option_64.hdb.jar output-destination-directory-indir-option/archive-file-name-inarc-option_64.db.jar output-destination-directory-indir-option/archive-file-name-inarc-option_64.csv.jar Storage location In Windows Infrastructure-Analytics-Advisor-server-installationdestination-folder\Base64\bin In Linux Infrastructure Analytics Advisor CLI commands 181

182 Permissions Administrator permission(for Windows) or a root user permission(for Linux). Notes Do not interrupt the running of this command. Do not run more than one instance of this command at the same time. If the folder or directory in the dir option has insufficient free space, running of the hcmdsgetlogs command or hcmds64getlogs command will not be completed. Secure a sufficient amount of space in the folder or directory in the dir option, and then rerun this command. Use the following formula to calculate the amount of required free space: Size of directories and files in In Windows Infrastructure-Analytics-Advisor-server-installationdestination-directory/Base64/bin Infrastructure-Analytics-Advisor-server-installationdestination-folder\Analytics\data + size of folders and files in Infrastructure-Analytics-Advisor-server-installationdestination-folder\Analytics\logs + 10 GB In Linux Infrastructure-Analytics-Advisor-server-installationdestination-directory/Analytics/data + size of directories and files in Infrastructure-Analytics-Advisor-server-installationdestination-directory/Analytics/logs + 10 GB If products that use common component are installed on the Infrastructure Analytics Advisor server, add the capacity required for collecting logs for these products in the calculation. If you use the same option more than once, only the first option is used. You can run this command even if the Infrastructure Analytics Advisor server is not running. Return values Return value Description 0 The command ran normally. 1 The argument is invalid. 2 The command ran abnormally. 182 Infrastructure Analytics Advisor CLI commands

183 Example The following example shows the use of this command to collect log files in the folder: hcmds64getlogs /dir "C:\Users\folder01" /types Analytics /arc HIAA_log hcmds64intg Use this command to delete authentication data registered in the repository of the server that manages user accounts. The command also displays the address of the server in which the authentication data is registered. If you fail to delete authentication data when uninstalling Infrastructure Analytics Advisor server, use this command to delete the authentication data. Format In Windows hcmds64intg {/delete /type Analytics /print /primary} /user user-id /pass password In Linux hcmds64intg {-delete /type Analytics -print -primary} -user user-id -pass password Options delete Deletes authentication data. type Analytics print Specify Analytics as the product name of the server in which the authentication data is registered. Displays the name of the program in which the authentication data is registered. primary Displays the host name or the IP address of the server in which the authentication data is registered. Infrastructure Analytics Advisor CLI commands 183

184 user user-id Specify the user ID for connecting with the server in which the authentication data is registered. The user ID you specify must have the User Management permission. pass password Specifies the password of the account that has the User Management permission. Storage location In Windows In Linux Infrastructure-Analytics-Advisor-server-installationdestination-folder\Base64\bin Infrastructure-Analytics-Advisor-server-installationdestination-directory/Base64/bin Permissions Administrator permission(for Windows) or a root user permission(for Linux). Return values Return value Description 0 The command ran normally. 1 The authentication data has already been deleted. 2 Authentication data is registered in the server on which you ran the command. 3 Authentication data is not registered in the server on which you ran the command. 4 Authentication data is not registered in the server on which you ran the command. In addition, an authentication error occurred on the server in which authentication data is registered. 253 An authentication error occurred on the server in which authentication data is registered. 254 Communication with the server in which authentication data is registered failed. 255 The command ran abnormally. Example The following example shows the use of this command to delete authentication data from the server that manages the user account: hcmds64intg /delete /type Analytics /user user1 /pass pass1 184 Infrastructure Analytics Advisor CLI commands

185 hcmds64srv Use this command to start or stop Infrastructure Analytics Advisor server services.. The command also displays the Infrastructure Analytics Advisor server service status or changes the service start method. Format In Widows To start, stop, or display only the status of a specific service: hcmds64srv {/start /stop /check /status} [/server service-name] To display the status of services of Infrastructure Analytics Advisor server and products that use common component: hcmds64srv /statusall To change the start method of a service: hcmds64srv /starttype {auto manual} {/server service-name /all} In Linux To start, stop, or display only the status of a specific service: hcmds64srv {-start -stop -check -status} [-server service-name] To display the status of services of Infrastructure Analytics Advisor server and products that use common component: hcmds64srv -statusall To change the start method of a service: hcmds64srv -starttype {auto manual} {-server service-name /all} Infrastructure Analytics Advisor CLI commands 185

186 Options start stop status Starts the service and database you specified in the server option. Stops the service and database you specified in the server option. Displays the status of the server and database you specified in the server option. server service-name To start, stop, or display the status of Infrastructure Analytics Advisor server product services only, specify AnalyticsWebService as the service name. By running this command by specifying AnalyticsWebService in the server option, you can start, stop, or display the status of the following services: Service display name and process Start Stop Status display HAnalytics Engine Web Service Y Y Y HBase 64 Storage Mgmt Web Service Y N N HBase 64 Storage Mgmt Web SSO Service Y N N Database process # Y N N Legend: Y: Processed N: Not processed Note: An Infrastructure Analytics Advisor server internal process corresponding to the service HiRDB/EmbeddedEdition _HD1 If you omit the server option, the next service is started, stopped, or the status of the next service displays. Service display name and process Start Stop Status display Status display (/statusall) HAnalytics Engine Web Service Y Y Y Y HBase 64 Storage Mgmt SSO Service HBase 64 Storage Mgmt Web Service Y Y Y Y Y Y Y Y 186 Infrastructure Analytics Advisor CLI commands

187 Service display name and process Start Stop Status display Status display (/statusall) HBase 64 Storage Mgmt Web SSO Service Y Y Y Y Database process # Y Y Y Y Service of products that use common component Y Y Y Y Legend: Y: Processed N: Not processed Note: An Infrastructure Analytics Advisor server internal process corresponding to the service HiRDB/EmbeddedEdition _HD1 statusall Displays the service and data statuses, and the status of the products registered in common component. If you omit the server option, this argument is used. starttype {auto manual} all Specify the start type of the service with the server option. Specify auto for an automatic start. Specify manual for a manual start. If you specify this option, the command runs for all services of Infrastructure Analytics Advisor server and other products that use common component. Storage location In Windows In Linux Infrastructure-Analytics-Advisor-server-installationdestination-folder\Base64\bin Infrastructure-Analytics-Advisor-server-installationdestination-directory/Base64/bin Permissions Administrator permission(for Windows) or a root user permission(for Linux). Infrastructure Analytics Advisor CLI commands 187

188 Notes If you start or stop Infrastructure Analytics Advisor server services as a daily operation, omit the server option to start or stop all the services. To start only Infrastructure Analytics Advisor server services by specifying the server option, specify AnalyticsWebService for the server option to start common component service. If you run the command with the stop option and the termination processing does not end within three minutes, an error occurs and a message is displayed to indicate a time-out. In this case, wait a while, and then rerun the command with the stop option. If you start or stop a service with the start or stop option, the command might end while the service does not start or stop completely. To confirm that the service has completely started or stopped, use either of the following operations: Confirm that either of the following messages has been output to a disclosed log or the event log: At startup Message: KNAQ10086-I Application is running. When stopped Message: KNAQ10089-I Application is stopped. Specify the statusall option to check the status of the service. Return values The following table shows the return values of the command with start option or stop option: Return value Description 0 The command ran normally. 1 With start option The service was already started. With stop option The service was already stopped. 255 The command failed. The following table shows the return values of the command with the check, status, or statusall option: 188 Infrastructure Analytics Advisor CLI commands

189 Return value Description 0 The service has not started. 1 The service has started. 255 The command failed. The following table shows the return values of the command with the starttype option: Return value Description 0 The command ran normally. 255 The command failed. Examples To start all services: hcmds64srv /start To stop all services: hcmds64srv /stop To check the status of all services: hcmds64srv /status To start the services of only Infrastructure Analytics Advisor server products: hcmds64srv /start /server AnalyticsWebService hcmds64ssltool Use this command to create private keys, certificate signing requests (CSRs), self-signed certificates, and content files for self-signed certificates that are required for SSL connections. The created files are used for the following purposes: Submitting the CSR to a CA to obtain an SSL server certificate. You can build an SSL-connected environment by combining the obtained SSL server certificate and the private key. Infrastructure Analytics Advisor CLI commands 189

190 Building an SSL-connected environment by combining the self-signed certificate with the private key. However, we recommend that you use the environment for only test purposes because security is low. Checking the details of the registration of the self-signed certificate from the content file of the self-signed certificate. Format In Windows hcmds64ssltool [/key private-key-file-name] [/csr CSR-file-name] [/cert self-signed-certificate-file-name] [/certtext name-of-the-content-file-of-the-self-signedcertificate] [/validity expiration-date-of-the-self-signedcertificate] [/dname distinguished-name (DN)] [/sigalg signature-algorithm] [/eccsigalg signature-algorithm-of-the-servercertificate-for-elliptic-curve-cryptography] [/ecckeysize size-of-the-private-key-for-elliptic-curvecryptography] In Linux hcmds64ssltool [-key private-key-file-name] [-csr CSR-file-name] [-cert self-signed-certificate-file-name] [-certtext name-of-the-content-file-of-the-self-signedcertificate] [-validity expiration-date-of-the-self-signedcertificate] [-dname distinguished-name (DN)] [-sigalg signature-algorithm] [-eccsigalg signature-algorithm-of-the-servercertificate-for-elliptic-curve-cryptography] [-ecckeysize size-of-the-private-key-for-elliptic-curvecryptography] Options key private-key-file-name Specify the absolute path for storing the private key. The private key for RSA cryptography will be output to a file of the specified file name. The private key for elliptic curve cryptography will be output to another file of the specified file name with the prefix ecc Infrastructure Analytics Advisor CLI commands

191 If you omit this option, the httpsdkey.pem file and the ecchttpsdkey.pem file will be output under Infrastructure-Analytics- Advisor-server-Installation-destination-folder\Base64\uCPSB \httpsd\conf\ssl\server\(for Windows) or Infrastructure- Analytics-Advisor-server-Installation-destination-directory/ Base64/uCPSB/httpsd/conf/ssl/server/(for Linux). csr CSR-file-name Specify the absolute path for storing the CSR. The CSR for RSA cryptography is output to a file of the specified file name. The CSR for elliptic curve cryptography will be output to another file of the specified file name with the prefix ecc-. If you omit this option, the httpsd.csr file and the ecc-httpsd.csr file is output under Infrastructure-Analytics-Advisor-server- Installation-destination-folder\Base64\uCPSB\httpsd\conf\ssl \server\(for Windows) or Infrastructure-Analytics-Advisorserver-Installation-destination-directory/Base64/uCPSB/ httpsd/conf/ssl/server/(for Linux). certself-signed-certificate-file-name Specify the absolute path for storing the self-signed certificate. The selfsigned certificate for RSA cryptography will be output to a file of the specified file name. The self-signed certificate for elliptic curve cryptography is output to another file of the specified file name with the prefix ecc-. If you omit this option, the httpsd.pem file and the ecc-httpsd.pem file is output under Infrastructure-Analytics-Advisor-server- Installation-destination-folder\Base64\uCPSB\httpsd\conf\ssl \server\(for Windows) or Infrastructure-Analytics-Advisorserver-Installation-destination-directory/Base64/uCPSB/ httpsd/conf/ssl/server/(for Linux). certtext name-of-the-content-file-of-the-self-signed-certificate Outputs the content of the self-signed certificate in text format. Specify the absolute path for storing the content file. The content of the selfsigned certificate for RSA cryptography is output to a file of the specified file name. The content of the self-signed certificate for elliptic curve cryptography is output to another file of the specified file name with the prefix ecc-. If you omit this option, the httpsd.txt file and the ecc-httpsd.txt file is output under Infrastructure-Analytics-Advisor-server- Installation-destination-folder\Base64\uCPSB\httpsd\conf\ssl \server\(for Windows) or Infrastructure-Analytics-Advisor- Infrastructure Analytics Advisor CLI commands 191

192 server-installation-destination-directory/base64/ucpsb/ httpsd/conf/ssl/server/(for Linux). validity expiration-date-of-the-self-signed-certificate Specify the expiration date of the self-signed certificate in terms of the number of days. If you specify this option, the same value is specified for RSA cryptography and elliptic curve cryptography. If you omit this option, the certificate expires in 3,650 days. dname distinguished-name (DN) Specify the distinguished-name (DN) described in the SSL server certificate, in the format "attribute-type=attribute-value". You can specify some attribute type values using a comma (,) as a delimiter. Characters specified for attribute types are not case sensitive. You cannot use a double quotation mark (") or a backslash (/) in the attribute type. For details about how to escape characters, follow the instructions in RFC2253. To use the following symbols, add a backslash (/) before each symbol as an escape character. Plus signs (+), commas (,), semicolons (;), left angle brackets (<), equal signs (=), right angle brackets (>) Spaces at the beginning of character strings Spaces at the end of character strings Hash marks (#) at the beginning of character strings If you omit this option, you must enter attribute values according to the instructions in the window displayed when you run the command. The following table lists the attribute types that you can specify for this option: Attribute type Definition Window response Attribute value CN Common Name Server Name Distinguished-name # of the Infrastructure Analytics Advisor server, such as host name, IP address, or domain name OU O Organizational Unit Name Organization Name Organizational Unit Organization Name Lower-level organization name, such as department or section name Company or other organization's name # L Locality Name City or Locality City name or region name ST State or Province Name State or Province State name or district name 192 Infrastructure Analytics Advisor CLI commands

193 Attribute type Definition Window response Attribute value C Country Name two-character countrycode Country code # Required in a response entry The following is an example of response input: Enter Server Name [default=myhostname]:example.com Enter Organizational Unit:Device Manager Administration Enter Organization Name [default=myhostname]:hitachi Enter your City or Locality:Santa Clara Enter your State or Province:California Enter your two-character country-code:us Is CN=example.com,OU=Device Manager Administration,O=HITACHI,L=Santa Clara, ST=California,C=US correct? (y/n) [default=n]:y If the entry is incorrect, you can input again by typing n. sigalg signature-algorithm Specify any of the following as the signature algorithm. If you omit this option, SHA256withRSA is used. SHA1withRSA SHA256withRSA eccsigalg signature-algorithm-of-the-server-certificate-forelliptic-curve-cryptography Specify the signature algorithm of the server certificate for elliptic curve cryptography. You can specify SHA512withECDSA, SHA384withECDSA, SHA256withECDSA, or SHA1withECDSA. If you omit this option, the signature algorithm is SHA384withECDSA. Specify the size (in bits) of the private key for elliptic curve cryptography. You can specify 256 or 384. If you omit this option, the size of the private key for elliptic curve cryptography is 384 bits. The size of the private key for RSA cryptography is fixed as 2,048 bits. Storage location In Windows ecckeysize size-of-the-private-key-for-elliptic-curvecryptography Infrastructure-Analytics-Advisor-server-installationdestination-folder\Base64\bin Infrastructure Analytics Advisor CLI commands 193

194 In Linux Infrastructure-Analytics-Advisor-server-installationdestination-directory/Base64/bin Permissions Administrator permission(for Windows) or a root user permission(for Linux). Notes If the value of the attribute type CN of the SSL server certificate does not match the host name, IP address, or domain name as the connection destination of the Infrastructure Analytics Advisor server from the web browser, a message indicates a server mismatch. Return values Return value Description 0 The command ran normally. 1 The argument is invalid. 250 Deletion of the key store failed. 251 Creation of the private key failed. 252 Creation of the self-signed certificate failed. 253 Creation of the CSR failed. 254 Creation of the content file of the self-signed certificate failed. 255 The command ran abnormally. hcmds64unlockaccount When the user accounts of all users who have the User Management permission are locked, use this command to unlock those user accounts. Format In Windows hcmds64unlockaccount /user user-id /pass password In Linux hcmds64unlockaccount -user user-id -pass password 194 Infrastructure Analytics Advisor CLI commands

195 Options user user-id Specify the user ID of the user account to be unlocked. The user ID you specify must have the User Management permission. pass password Specify the password of the user account to unlock. Storage location In Windows In Linux Infrastructure-Analytics-Advisor-server-installationdestination-folder\Base64\bin Infrastructure-Analytics-Advisor-server-installationdestination-directory/Base64/bin Permissions Administrator permission(for Windows) or a root user permission(for Linux). Notes You can use the hcmds64unlockaccount command to unlock only user accounts that have the User Management permission. In Windows, if the user name or password contains an ampersand, vertical bar, or caret, enclose each of these symbols with double quotation marks or add a caret before each symbol as an escape character. In Linux, if the user name or password contains an ampersand, vertical bar, or caret, add a caret before each of these symbols as an escape character. For example, if the password is ^a^b^c^ in Windows-based, use either of the following: hcmds64unlockaccount /user system /pass "^"a"^"b"^"c"^" hcmds64unlockaccount /user system /pass ^^a^^b^^c^^ Return values Return value Description 0 The command ran normally. 251 An authentication error (logon error) occurred. Infrastructure Analytics Advisor CLI commands 195

196 Return value Description 252 An authentication error (no User Management permission) occurred. 253 Communication with the authentication server failed. 254 The command was run on the secondary server side. 255 The command ran abnormally. Example The following example shows how to use this command to unlock a user account: hcmds64unlockaccount /user test01 /pass TTdate00 reloadtemplate Use this command to reroad the template files of Infrastructure Analytics Advisor server during the startup of Infrastructure Analytics Advisor server. The following table describes the types of template files that the command references, and the reference destination directories: Type of template file Template file for linking with s In Windows Reference destination folder Infrastructure-Analytics-Advisor-serverinstallation-destination-folder \Analytics\conf\template\mail In Linux Infrastructure-Analytics-Advisor-serverinstallation-destination-directory/ Analytics/conf/template/mail Template file for linking with commands In Windows Infrastructure-Analytics-Advisor-serverinstallation-destination-folder \Analytics\conf\template\command In Linux Infrastructure-Analytics-Advisor-serverinstallation-destination-directory/ Analytics/conf/template/command 196 Infrastructure Analytics Advisor CLI commands

197 Format In Windows reloadtemplate /user user-id /passwordfile password-file In Linux reloadtemplate -user user-id -passwordfile password-file Arguments user user-id Specify the Infrastructure Analytics Advisor server user ID to be used for command execution. passwordfile path-of-the-password-file Specify the path to the password file of the user who is specified for the user option. Use the encryptpassword command to create the password file. Storage location In Windows In Linux Infrastructure-Analytics-Advisor-server-installationdestination-folder\Analytics\bin Infrastructure-Analytics-Advisor-server-installationdestination-directory/Analytics/bin Permissions Administrator permission(for Windows) or a root user permission(for Linux). Notes To run the command, the Infrastructure Analytics Advisor server service must be started. If the Infrastructure Analytics Advisor server service is not running, you do not have to run this command because the template files are automatically read when the Infrastructure Analytics Advisor server service starts. Infrastructure Analytics Advisor CLI commands 197

198 Return values Return value Description 0 The command ran normally. 1 The argument is invalid. 2 Command execution was interrupted. 3 The service status is invalid. 5 Communication failed. 6 An authentication error occurred. 7 The specified path is invalid. 9 The specified path does not exist. 10 The specified path could not be accessed. 14 You do not have permission to run this command. 232 The reroading of the template files failed. 233 You do not have the necessary permissions to update the template file. 255 The command ran abnormally. restoresystem Use this command to restore the backup for Infrastructure Analytics Advisor server settings or database information that you collected by running the backupsystem command. Format In Windows restoresystem /dir backup-folder /type {all Analytics} [/auto] In Linux restoresystem -dir backup-directory -type {all Analytics} [-auto] Options dir backup-directory Specify the directory in which the backup file is stored with the absolute or relative path. 198 Infrastructure Analytics Advisor CLI commands

199 type {all Analytics} Specify the restoration target. all Restores information of Infrastructure Analytics Advisor server and common component. Common component instance manages the user information. Analytics Restores information of only Infrastructure Analytics Advisor server. auto Automatically stops or starts services and databases of Infrastructure Analytics Advisor server and products that use common component. If you omit this option, services and databases of Infrastructure Analytics Advisor server and products that use common component are not automatically stopped or started. Storage location In Windows In Linux Infrastructure-Analytics-Advisor-server-installationdestination-folder\Analytics\bin Infrastructure-Analytics-Advisor-server-installationdestination-directory/Analytics/bin Permissions Administrator permission (for Windows) or a root user permission (for Linux). Notes When restoring the backup, the directory in which the backup file is stored requires at least 2 GB of free space. When you run the restoresystem command, for backup, the extension.original is appended to the file name of the file in Infrastructure-Analytics-Advisor-server-installationdestination-folder\Analytics\conf (for Windows) or Infrastructure-Analytics-Advisor-server-installationdestination-directory/Analytics/conf (for Linux). This file is overwritten every time the restoresystem is run. The following files are not restored by this command. If necessary, manually set or save the files again. Infrastructure Analytics Advisor CLI commands 199

200 Files that require resettings Security definition file (security.conf) Settings file for changing port numbers (user_httpsd.conf) These files are backed up in the following directories: In Windows backup-folder\hbase\base\conf\sec backup-folder\hbase\base\httpsd.conf In Linux backup-directory/hbase/base/conf/sec backup-directory/hbase/base/httpsd.conf Files for HTTPS connections that must be stored SSL server certificate file Private-key file In addition, the settings for HTTPS connections are defined in the httpsd.conf file and the user_httpsd.conf file. Save each file to the storage destination directory. If you do not specify the auto option, stop the service by running the hcmds64srv command with the stop option. The service to be stopped depends on the type option. If you specified all in the type option: You must stop not only the service of Infrastructure Analytics Advisor server, but also the services of the products that use common component. If you specified Analytics in the type option: You must stop the service of only Infrastructure Analytics Advisor server. Make sure that the following information is the same between the environment where the backup was collected and the environment where the information was restored: Version of Infrastructure Analytics Advisor server Installation directory of Infrastructure Analytics Advisor server 200 Infrastructure Analytics Advisor CLI commands

201 When products that use common component are installed on the Infrastructure Analytics Advisor server, if you do a restoration with all specified in the type option, the definition information for common component is also restored. In this example, an inconsistency might occur in the definition information between the products that use common component and common component itself. Therefore, if products that use common component are installed on the Infrastructure Analytics Advisor server of the restoration destination, do a restoration by using one of the following procedures: To restore data for products that use common component, in addition to Infrastructure Analytics Advisor server data 1. Run the restore command for the product that uses common component. 2. Specify type Analytics for the restoresystem command of Infrastructure Analytics Advisor server, and then run the command. To restore only user information, in addition to Infrastructure Analytics Advisor server data 1. Specify type Analytics for the restoresystem command of Infrastructure Analytics Advisor server, and then run the command. 2. Update the user management information. To restore data of only Infrastructure Analytics Advisor server 1. Specify type Analytics for the restoresystem command of Infrastructure Analytics Advisor server, and then run the command. Return values Return value Description 0 The command ran normally. 1 The argument is invalid. 2 Command running was interrupted. 3 The service status is invalid. 4 Another command is currently running. 7 The path is invalid. Infrastructure Analytics Advisor CLI commands 201

202 Return value Description 9 The path does not exist. 10 The path cannot be accessed. 14 You do not have permission to run this command. 110 Running of restoration failed. 111 The start or stop of the service failed. 113 The backup file is invalid. 255 Command running was interrupted because of another error. Example The following example shows the use of this command to restore information of only Infrastructure Analytics Advisor server: restoresystem /dir "C:\Users\Backup" /type Analytics /auto 202 Infrastructure Analytics Advisor CLI commands

203 B Infrastructure Analytics Advisor server services After you install Infrastructure Analytics Advisor server on a Windows host, the following Infrastructure Analytics Advisor services are registered. Displayed service name Service name Startup type Product HAnalytics Engine Web Service HBase 64 Storage Mgmt SSO Service HBase 64 Storage Mgmt Web Service HBase 64 Storage Mgmt Web SSO Service HiRDB/ EmbeddedEdition _HD1 AnalyticsWebService Automatic Infrastructure Analytics Advisor HBase64StgMgmtSSOS ervice HBase64StgMgmtWebS ervice HBase64StgMgmtWebS SOService HiRDBEmbeddedEdition _HD1 Automatic Automatic Manual Automatic Common component Common component Common component Common component Infrastructure Analytics Advisor server services 203

204 204 Infrastructure Analytics Advisor server services

205 C User-specified properties file (config_user.properties) This appendix describes the definition file for configuring public logs and setting values for dynamic thresholds. Format key-name=value Storage location For Windows For Linux Infrastructure-Analytics-Advisor-server-installationdestination-folder\Analytics\conf Infrastructure-Analytics-Advisor-server-installationdestination-directory/Analytics/conf Timing at which definitions are applied When the HAnalytics Engine web service starts Content to be specified Specify each key name and its value on one line. When defining the userspecified properties file, note the following points: Any line starting with # is treated as a comment line. Blank lines are ignored. ISO (for Windows) or UTF-8 (for Linux) is used for character encoding. Specified values are case-sensitive. To include "\" in a specified character string, specify "\\". User-specified properties file (config_user.properties) 205

206 In this situation, "\\" is counted as a single byte. If you specify an invalid value, the KNAQ02022-W message is output to the integrated trace logs and public logs, and the default value is used. If you specify the same key more than once in the same file, the last specification takes effect. Settings Cate gory Key name Setting Specifiable values Default value Public logs Dyna mic thresh old values (para meter s) logger.sysloglevel logger.message.server.maxba ckupindex logger.message.server.maxfi lesize logger.message.command.maxb ackupindex logger.message.command.maxf ilesize dynamicthreshold.calculatet ime dynamicthreshold.startlaten cyday Specify a threshold value for outputting an event log (in Windows) or syslog (in Linux). Maximum number of log backup files for the server. Maximum size of log files for the server. (unit: KB) Maximum number of log backup files for commands. Maximum size of log files for commands. (unit: KB) Time when the calculation of dynamic threshold values starts. Period (unit: days) for which to check the number of performance values that are required to start the calculation of dynamic threshold values to to 2,097, to to 2,097, :00:00 to 23:59:59 Single-byte numerals and commas (,) 00:00:00 1, 3, 7, 14 dynamicthreshold.minimumdat an To specify more than one value, use commas (,) to delimit the values. Specify the minimum number of performance values that is required to start the calculation of dynamic threshold values. The calculation of dynamic threshold values starts when the number of performance 1 to 2,147,483, User-specified properties file (config_user.properties)

207 Cate gory Key name Setting Specifiable values Default value values in the period specified for dynamicthreshold.sta rtlatencyday exceeds the minimum number of performance values specified for dynamicthreshold.min imumdatan. Dyna mic thresh old values (margi n) Securi ty Contro lling resour ces by using IO Contro l dynamicthreshold.margin.sev ere.plus dynamicthreshold.margin.sev ere.rate dynamicthreshold.margin.nor mal.plus dynamicthreshold.margin.nor mal.rate dynamicthreshold.margin.rou gh.plus dynamicthreshold.margin.rou gh.rate cert.verify.enabled automation.parameter.servic egroupname automation.parameter.produc tname Specify the margin for addition when the value of Margin is Severe. Specify the margin for multiplication (unit: %) when the value of Margin is Severe. Specify the margin for addition when the value of Margin is Normal. Specify the margin for multiplication (unit: %) when the value of Margin is Normal. Specify the margin for addition when the value of Margin is Rough. Specify the margin for multiplication (unit: %) when the value of Margin is Rough. Specify whether to enable the verification of a server certificate. Specify the service group name that was set in Hitachi Automation Director for Infrastructure Analytics Advisor. Specify the name that was set for Category in the Web Service Connections window of Hitachi Automation Director. 0 to 2,147,483, to to 2,147,483, to to 2,147,483, to true or false A value between 1 and 80 characters long, using only singlebyte alphanumeric characters and underscores (_) A value between 1 and 32 characters long, using only singlebyte false Analytics Service Group Analytics User-specified properties file (config_user.properties) 207

208 Cate gory Key name Setting Specifiable values Default value automation.parameter.servic ename.iocontrol.modify automation.parameter.servic ename.iocontrol.delete iocontrol.cmd.parameterfile.maxcount iocontrol.cmd.parameterfile.minretention.minute Specify the service name that was set when the service was created by using the service template "Modify IO Control Settings for Volume" in Hitachi Automation Director. Specify the service name that was set when the service was created by using the service template "Delete IO Control Settings for Volume" in Hitachi Automation Director. Specify the maximum number of files that are used as the parameter file for IO control by using script files. Specify the minimum retention of files that are used as the parameter file for IO control by using script files. alphanumeric characters, underscores (_), periods (.), and hyphens (-) A value between 1 and 128 characters long A value between 1 and 128 characters long 1 to 5, to 14,400 5 Modify IO Control Settings for Volume Delete IO Control Settings for Volume Examples logger.sysloglevel = 0 logger.message.server.maxbackupindex = 7 logger.message.server.maxfilesize = logger.message.command.maxbackupindex = 7 logger.message.command.maxfilesize = 1024 dynamicthreshold.calculatetime = 00:00:00 dynamicthreshold.startlatencyday = 1, 3, 7, 14 dynamicthreshold.minimumdatan = 150 dynamicthreshold.margin.severe.plus = 1 dynamicthreshold.margin.severe.rate = 1 dynamicthreshold.margin.normal.plus = 5 dynamicthreshold.margin.normal.rate = 5 dynamicthreshold.margin.rough.plus = 10 dynamicthreshold.margin.rough.rate = 10 cert.verify.enabled = false automation.parameter.servicegroupname = Analytics Service Group 208 User-specified properties file (config_user.properties)

209 automation.parameter.productname = Analytics automation.parameter.servicename.iocontrol.modify = Modify IO Control Settings for Volume automation.parameter.servicename.iocontrol.delete = Delete IO Control Settings for Volume User-specified properties file (config_user.properties) 209

210 210 User-specified properties file (config_user.properties)

211 D Default collection and data export interval for probes The following table lists the default data collection and default data export interval in minutes for all the probes: Table 26 Default collection and data export interval Probes Default collection interval (Minutes) Default Export time periods (Minutes) Storage Hitachi Enterprise Storage Collection interval depends on the resources you monitor. HNAS 1 15 Hitachi AMS 1 15 Hypervisor VMware 1 15 Windows-based 1 15 FC Switches Cisco DCNM 5 15 Brocade Network Advisor Table 27 Hitachi Enterprise Storage probe default collection interval The following table lists the default data collection interval for Hitachi Enterprise Storage probe: Op-Code Description Default Value (Minutes) CHAC Between CHA and Cache Switch Summary 1 CBMB Between CHB and Main Blade Summary 1 CCMS Between Cache Switch and Cache Memory Summary 1 DKAC Between DKA and Cache Switch Summary 1 DBMB Between DKB and Main Blade Summary 1 MPCS Between MP Blade and Cache Switch Summary 1 CLMS CLPR Per MP Blade Summary 1 Default collection and data export interval for probes 211

212 Op-Code Description Default Value (Minutes) CLPS CLPR Summary 1 CPS Cache Path Summary 1 LDE LDEV Summary - Extended 5 LDA Logical Device Aggregation 5 LDS Logical Device Summary 5 PLC Pool Configuration 60 PLF Pool Frequency Distribution 60 PLR Pool Page Relocation 60 PLS Pool Summary 5 PLTR Pool Tier Page Relocation 60 PLTC Pool Tier Type Configuration 60 PLTS Pool Tier Type Operation Status 60 PTS Port Summary 1 PRCS Processor Summary 1 RGS RAID Group Summary 5 PI Storage Summary 1 UMS Utilization Per MP Blade Summary 5 VVF V-VOL Frequency Distribution 60 VVTC V-VOL Tier Type Configuration 60 VVTI V-VOL Tier Type I/O Information 15 VVC Virtual Volume Configuration Default collection and data export interval for probes

213 E Configuring initial settings for limiting IO activity of Hitachi storage resources (using a script) This section describes how to use Infrastructure Analytics Advisor and the Configuration Manager REST API to configure the initial settings required to limit the IO activity of resources by using the IO Control Settings function. Creating a script file for limiting the IO activity of resources by using IO Control Command template definition files formats Configuring initial settings for limiting IO activity of Hitachi storage resources (using a script) 213

214 Creating a script file for limiting the IO activity of resources by using IO Control You can also limit the IO activity of resources by using a script file that is executed by the Configuration Manager REST API. Before you begin The Configuration Manager REST API (REST server) is installed. For installation instructions, see the Configuration Manager REST API Reference Guide. Procedure 1. Create a script file for limiting the IO activity of resources. To limit the IO activity of resources, you can use the Server Priority Manager function that is provided by the storage system. Use the Configuration Manager REST API to configure the Server Priority Manager settings. In the script file, the following information is specified as arguments from Infrastructure Analytics Advisor. First argument: User ID of the user logged in to Infrastructure Analytics Advisor Second argument: The folder path of the file that includes information about the Server Priority Manager settings Note: Information about the Server Priority Manager settings is specified in JSON format. Specification format { "storagedeviceid":"storage-device-id", "IOControlParameter": [ {"ldevid":ldev-id, "hostwwn":"wwn-of-the-host", "upperlimitforiops":maximum-iops-to-be-specified, "upperlimitfortransferrate":maximum-transfer-rate-tobe-specified} ] } For details about the parameters, see the following descriptions in Configuration Manager REST API Reference Guide. Getting Server Priority Manager information by specifying a volume and the WWN or iscsi name of an HBA Getting a list of Server Priority Manager information 214 Configuring initial settings for limiting IO activity of Hitachi storage resources (using a script)

215 Setting Server Priority Manager information by specifying a volume and the WWN or iscsi name of the HBA Changing the Server Priority Manager information Deleting Server Priority Manager information The following are examples of arguments to be specified from Infrastructure Analytics Advisor to modify or delete the Server Priority Manager settings, as well as examples of API requests that use the values of these arguments and that must be run by using scripts. To add the Server Priority Manager settings to LDEV 101 and to update the Server Priority Manager settings for LDEV 102 Arguments specified from Infrastructure Analytics Advisor In Windows Smith C:\Program Files\HITACHI\Analytics\data\ioControl \ _modify_ _0.json In Linux Smith /opt/hitachi/analytics/data/iocontrol/ _modify_ _0.json The file content is as follows: {"storagedeviceid":" ","iocontrolparame ter" :[{"ldevid": 101,"hostWwn":" cceccc9","upperLimitForIop s": 50},{"ldevId": 102,"hostWwn":" cceccc0","upperLimitForIop s": 400}]} API request that must be run by using a script curl --user user-name:password -H "Accept: application/ json" -H "Content-type:application/json" -X GET protocol://host-name:port-number/ ConfigurationManager/v1/objects/storages/ /io-control-ldev-wwns-iscsis/ curl --user user-name:password -H "Accept: application/ json" -H "Content-type:application/json" -X POST - d'{"ldevid": 101,"upperLimitForIops":"50","hostWwn":" cceccc 9"}' protocol://host-name:port-number/ Configuring initial settings for limiting IO activity of Hitachi storage resources (using a script) 215

216 ConfigurationManager/v1/objects/storages/ /io-control-ldev-wwns-iscsis/ curl --user user-name:password -H "Accept: application/ json" -H "Content-type:application/json" -X PUT -d '{"upperlimitforiops":"400"}' protocol://hostname:port-number/configurationmanager/v1/objects/ storages/ /io-control-ldev-wwns-iscsis/ 102%2C% cceccc0 To delete the Server Priority Manager settings from LDEV 101 Arguments specified from Infrastructure Analytics Advisor In Windows Smith C:\Program Files\HITACHI\Analytics\data\ioControl \ _delete_ _0.json In Linux Smith /opt/hitachi/analytics/data/iocontrol/ _delete_ _0.json The file content is as follows: {"storagedeviceid":" ","iocontrolparame ter" :[{"ldevid":101,"hostwwn":" cceccc9"}]} API request that must be run by using a script curl --user user-name:password -H "Accept: application/ json" -H "Content-type:application/json" -X GET protocol://host-name:port-number/ ConfigurationManager/v1/objects/storages/ /io-control-ldev-wwns-iscsis/ curl --user user-name:password -H "Accept: application/ json" -H "Content-type:application/json" -X DELETE protocol://host-name:port-number/ ConfigurationManager/v1/objects/storages/ /io-control-ldev-wwns-iscsis/ 101%2C cceccc9 2. Edit the command definition file. In the command definition file that is stored in the location below, add the storage location of the script file that was created in step 1. There are two command definition files: one for updating Server Priority Manager settings and one for deleting Server Priority Manager settings. 216 Configuring initial settings for limiting IO activity of Hitachi storage resources (using a script)

217 Storage location In Windows: Infrastructure-Analytics-Advisor-server-installationdestination-folder\Analytics\conf\template\command\Built-in In Linux: Infrastructure-Analytics-Advisor-server-installationdestination-directory/Analytics/conf/template/command/Builtin Command definition file for updating settings: BuiltinTemplateIoControlModify.txt Command definition file for deleting settings: BuiltinTemplateIoControlDelete.txt In each command definition file, add the storage location of the script file to the following line: Command definition file SE.cmd.template.cmdName.string = storage-location-of-thescript-file For details about the SE.cmd.template.cmdName.string key, see Command template definition files formats. Result Configuration of the settings for limiting the IO activity of resources by using IO Control is now complete. Note: You can check the script execution results in the System Events tab. Related topics Command template definition files formats on page 217 Command template definition files formats If you create a command template definition file, you can use the Execute Action window to run commands of other products, user programs, and resources on the Infrastructure Analytics Advisor management server. Format specified-key-name=specified-value File You can specify any file name and file extension. Save the file in UTF-8 format. The maximum number of files that can be set in Infrastructure Analytics Advisor (including the number of template definition Configuring initial settings for limiting IO activity of Hitachi storage resources (using a script) 217