Hitachi Infrastructure Analytics Advisor · Microsoft, the Microsoft ... SmartScreen, SQL Server, Visual Basic, Visual C++, Visual Studio, ... • Hitachi Infrastructure Analytics

Hitachi Infrastructure Analytics AdvisorInstallation and Configuration Guide

MK-96HIAA002-00

July 2016

© 2016 Hitachi, Ltd. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or by any means, electronicor mechanical, including copying and recording, or stored in a database or retrieval system forcommercial purposes without the express written permission of Hitachi, Ltd., or Hitachi Data SystemsCorporation (collectively “Hitachi”). Licensee may make copies of the Materials provided that any suchcopy is: (i) created as an essential step in utilization of the Software as licensed and is used in noother manner; or (ii) used for archival purposes. Licensee may not make any other copies of theMaterials. “Materials” mean text, data, photographs, graphics, audio, video and documents.

Hitachi reserves the right to make changes to this Material at any time without notice and assumesno responsibility for its use. The Materials contain the most current information available at the timeof publication.

Some of the features described in the Materials might not be currently available. Refer to the mostrecent product announcement for information about feature and product availability, or contactHitachi Data Systems Corporation at https://support.hds.com/en_us/contact-us.html.

Notice: Hitachi products and services can be ordered only under the terms and conditions of theapplicable Hitachi agreements. The use of Hitachi products is governed by the terms of youragreements with Hitachi Data Systems Corporation.

By using this software, you agree that you are responsible for:1. Acquiring the relevant consents as may be required under local privacy laws or otherwise from

authorized employees and other individuals to access relevant data; and2. 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 besubject to U.S. export control laws, including the U.S. Export Administration Act and its associatedregulations, and may be subject to export or import regulations in other countries. Reader agrees tocomply strictly with all such regulations and acknowledges that Reader has the responsibility to obtainlicenses to export, re-export, or import the Document and any Compliant Products.

Hitachi is a registered trademark of Hitachi, Ltd., in the United States and other countries.

AIX, AS/400e, DB2, Domino, DS6000, DS8000, Enterprise Storage Server, eServer, FICON,FlashCopy, IBM, Lotus, MVS, OS/390, PowerPC, RS/6000, S/390, System z9, System z10, Tivoli,z/OS, z9, z10, z13, z/VM, and z/VSE are registered trademarks or trademarks of InternationalBusiness Machines Corporation.

Active Directory, ActiveX, Bing, Excel, Hyper-V, Internet Explorer, the Internet Explorer logo,Microsoft, the Microsoft Corporate Logo, MS-DOS, Outlook, PowerPoint, SharePoint, Silverlight,SmartScreen, SQL Server, Visual Basic, Visual C++, Visual Studio, Windows, the Windows logo,Windows Azure, Windows PowerShell, Windows Server, the Windows start button, and Windows Vistaare registered trademarks or trademarks of Microsoft Corporation. Microsoft product screen shots arereprinted with permission from Microsoft Corporation.

All other trademarks, service marks, and company names in this document or website are propertiesof their respective owners.

2Hitachi Infrastructure Analytics Advisor Installation and Configuration Guide

https://support.hds.com/en_us/contact-us.html

Contents

Preface................................................................................................. 7Intended audience................................................................................................... 8Product version........................................................................................................8Release notes.......................................................................................................... 8Related documents.................................................................................................. 8Document conventions............................................................................................. 8Conventions for storage capacity values.....................................................................9Accessing product documentation........................................................................... 10Getting help...........................................................................................................10Comments.............................................................................................................11

1 Overview........................................................................................13Hitachi Infrastructure Analytics Advisor overview...................................................... 14Infrastructure Analytics Advisor installation and configuration workflow......................14

2 System requirements.......................................................................19Infrastructure Analytics Advisor management server requirements.............................20Data Center Analytics management server requirements...........................................20Analytics probe server requirements........................................................................ 22Browser requirements............................................................................................ 24Management target requirements............................................................................25

3 Installation..................................................................................... 29Installing Data Center Analytics management server.................................................30

Selecting an installation method........................................................................ 30Installing Data Center Analytics management server on Linux host.......................30

Preparing for installation..............................................................................30Installation................................................................................................. 31

Installing Data Center Analytics management server on VMware vSphere Client ...34Preparing for installation..............................................................................34Installation................................................................................................. 35Post installation tasks.................................................................................. 36


Initial setup of Data Center Analytics management server after installation........... 38Installing Analytics probe server..............................................................................39

Selecting an installation method........................................................................ 39Installing Analytics probe server on Linux host....................................................39

Preparing for installation..............................................................................39Installation................................................................................................. 42

Installing Analytics Probe server on VMware vSphere Client................................. 44Preparing for installation..............................................................................44Installation................................................................................................. 45Post installation tasks.................................................................................. 47

Initial setup of Analytics probe server after installation........................................ 48Installing Infrastructure Analytics Advisor.................................................................50

Preparing for installation................................................................................... 50Installing Infrastructure Analytics Advisor........................................................... 51Post installation tasks........................................................................................51Initial setup of Infrastructure Analytics Advisor................................................... 52

Setting up a connection with Data Center Analytics management server......... 52Changing the system account password........................................................53Configuring the mail server.......................................................................... 53

4 Adding probes to Analytics probe server........................................... 55Adding Hitachi Enterprise Storage probe.................................................................. 56

Prerequisites for adding Hitachi Enterprise Storage probe.................................... 56Verify the connection between host and monitoring targets............................56Creating an instance environment................................................................ 58Instance settings for monitoring logical device or parity groups...................... 60Canceling setup of an instance environment..................................................61Starting and stopping Agent services............................................................ 62

Adding Hitachi Enterprise Storage probe.............................................................63Adding Hitachi Adaptable Modular Storage (AMS) probe............................................65Adding HNAS probe................................................................................................66Adding VMware probe............................................................................................ 67Adding Brocade Network Advisor probe................................................................... 67Adding Cisco DCNM probe...................................................................................... 68Initial setup after adding a probe............................................................................ 69

5 Installing Data Center Analytics Windows-based probe...................... 71Data collection methods......................................................................................... 72Installing the Windows-based probe........................................................................ 74Configuring Data Center Analytics Windows-based probe.......................................... 75

Configuring the collection method......................................................................75Configuring the FTP or HTTPS server................................................................. 77Starting the Windows-based probe service......................................................... 78

Initial setup after adding a probe............................................................................ 78

6 Configuring secure communications..................................................81About security settings........................................................................................... 82Configuring an SSL server (Infrastructure Analytics Advisor management server)........82


Creating a private key and a certificate signing request for Infrastructure AnalyticsAdvisor............................................................................................................ 82Applying for a server certificate for Infrastructure Analytics Advisor from thecertificate authority...........................................................................................83Enabling SSL communication for the Infrastructure Analytics Advisor managementserver.............................................................................................................. 84Checking the expiration date of the certificate for Infrastructure Analytics Advisor.......................................................................................................................87

Configuring SSL servers (Data Center Analytics management and Analytics probeservers).................................................................................................................88

Applying self-signed certificates to the Data Center Analytics management server.......................................................................................................................88Exporting a self-signed certificate for the Data Center Analytics management server.......................................................................................................................90Importing a certificate to the truststore file for the Infrastructure Analytics Advisormanagement server..........................................................................................91Applying server certificates to the Data Center Analytics management server andthe Analytics probe server................................................................................. 92Checking the expiration dates of certificates for Data Center Analytics and Analyticsprobe servers................................................................................................... 95Changing the SSL port number between the Infrastructure Analytics Advisormanagement server and a web client.................................................................95

7 Changing Infrastructure Analytics Advisor management server systemsettings.......................................................................................... 97

Changing the system information............................................................................ 98Changing the installation folder of Infrastructure Analytics Advisor....................... 98Changing the Infrastructure Analytics Advisor management server host name.......98Changing the Infrastructure Analytics Advisor management server IP address.......99Changing the port number used between Infrastructure Analytics Advisor and theweb browser.................................................................................................... 99Changing the port number used between Infrastructure Analytics Advisor andcommon component....................................................................................... 101Changing the port number between Infrastructure Analytics Advisor and the SMTPserver............................................................................................................ 102Changing the time settings of the Infrastructure Analytics Advisor managementserver............................................................................................................ 102Moving an Infrastructure Analytics Advisor installation to another host................103

Starting and stopping the Infrastructure Analytics Advisor service............................ 104Starting the Infrastructure Analytics Advisor services......................................... 104Stopping the Infrastructure Analytics Advisor services........................................104Starting the Data Center Analytics management server or Analytics probe service..................................................................................................................... 105Stopping the Data Center Analytics management server or analytics probe service..................................................................................................................... 106

Backing up and restoring Infrastructure Analytics Advisor........................................106Stopping services before a back up or restore................................................... 108Backing up Infrastructure Analytics Advisor settings information.........................109Backing up the settings information and database of Data Center Analytics ........109Backing up Analytics probe settings information................................................ 110Backing up the entire RAID Agent system.........................................................111


RAID Agent definition information files to be backed up.....................................112Restoring Infrastructure Analytics Advisor settings information........................... 113Restoring the settings information and database of Data Center Analytics........... 114Restoring Analytics probe settings information.................................................. 115Restoring the RAID Agent system.................................................................... 117Updating configuration information files that depend on the environment in whichthe RAID Agent is installed.............................................................................. 118Starting Infrastructure Analytics Advisor services after a back up or restoreoperation ...................................................................................................... 119

Enabling system account locking........................................................................... 120

8 Removing Infrastructure Analytics Advisor components.................... 123Removing Infrastructure Analytics Advisor management server................................124Removing Data Center Analytics management server..............................................124Removing Analytics probe server........................................................................... 124

9 Troubleshooting............................................................................ 127Connection to the Infrastructure Analytics Advisor web client unsuccessful............... 128Logging on to Infrastructure Analytics Advisor unsuccessful.....................................128Starting Infrastructure Analytics Advisor does not work........................................... 129When Infrastructure Analytics Advisor cannot be connected to Data Center Analytics...........................................................................................................................129

A Infrastructure Analytics Advisor CLI commands............................... 131List of Commands.................................................................................................132Command usage notes......................................................................................... 132Usable characters for command arguments............................................................ 133backupsystem...................................................................................................... 134encryptpassword.................................................................................................. 136hcmds64fwcancel.................................................................................................137hcmds64getlogs................................................................................................... 138hcmds64intg........................................................................................................ 141hcmds64srv......................................................................................................... 143hcmds64ssltool.................................................................................................... 147hcmds64unlockaccount.........................................................................................151reloadtemplate.....................................................................................................152restoresystem...................................................................................................... 153

B User-specified properties file (config_user.properties).......................159

C Default collection and data export interval for probes.......................163

D Infrastructure Analytics Advisor services........................................ 165

Index................................................................................................ 167


PrefaceThis 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 7Hitachi Infrastructure Analytics Advisor Installation and Configuration Guide

Intended audienceThis document is intended for system administrators and authorized serviceproviders.

The concepts, procedures, and information described in this documentrequire 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 versionThis document revision applies to Infrastructure Analytics Advisor 2.0 or later.

Release notesRead the release notes before installing and using this product. They maycontain requirements or restrictions that are not fully described in thisdocument or updates or corrections to this document. Release notes areavailable on Hitachi Data Systems Support Connect: https://support.hds.com/en_us/documents.html.

Related documentsThe following documents are referenced or contain more information aboutthe 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-96DCA002• Hitachi Data Center Analytics REST API Reference Guide, MK-96HDCA006• Hitachi Data Center Analytics Analytics Query Language User Guide,

MK-96HDCA005

Document conventionsThis document uses the following typographic conventions:

8 PrefaceHitachi Infrastructure Analytics Advisor Installation and Configuration Guide

https://support.hds.com/en_us/documents.html


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(For exceptions to this convention for variables, see the entry for anglebrackets.)

Monospace 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 youmust 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 performingtasks more effectively.

Caution Warns the user of adverse conditions and/or consequences (forexample, disruptive operations, data loss, or a system crash).

WARNING Warns the user of a hazardous situation which, if not avoided, couldresult in death or serious injury.

Conventions for storage capacity valuesPhysical storage capacity values (for example, disk drive capacity) arecalculated 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,0002 bytes

1 gigabyte (GB) 1,000 MB or 1,0003 bytes

1 terabyte (TB) 1,000 GB or 1,0004 bytes

1 petabyte (PB) 1,000 TB or 1,0005 bytes

1 exabyte (EB) 1,000 PB or 1,0006 bytes

Logical storage capacity values (for example, logical device capacity) arecalculated 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 (210) bytes

1 MB 1,024 KB or 1,0242 bytes

1 GB 1,024 MB or 1,0243 bytes

1 TB 1,024 GB or 1,0244 bytes

1 PB 1,024 TB or 1,0245 bytes

1 EB 1,024 PB or 1,0246 bytes

Accessing product documentationProduct user documentation is available on Hitachi Data Systems SupportConnect: https://support.hds.com/en_us/documents.html. Check this site forthe most current documentation, including important updates that may havebeen made after the release of the product.

Getting helpHitachi Data Systems Support Connect is the destination for technical supportof products and solutions sold by Hitachi Data Systems. To contact technicalsupport, log on to Hitachi Data Systems Support Connect for contactinformation: https://support.hds.com/en_us/contact-us.html.

Hitachi Data Systems Community is a global online community for HDScustomers, partners, independent software vendors, employees, andprospects. It is the destination to get answers, discover insights, and make





https://community.hds.com/welcome

connections. Join the conversation today! Go to community.hds.com,register, and complete your profile.

CommentsPlease send us your comments on this document to [email protected] the document title and number, including the revision level (forexample, -07), and refer to specific sections and paragraphs wheneverpossible. All comments become the property of Hitachi Data SystemsCorporation.

Thank you!


https://community.hds.com/welcome

mailto:[email protected]


1Overview

This chapter provides an overview of the Infrastructure Analytics Advisorinstallation.

□ Hitachi Infrastructure Analytics Advisor overview

□ Infrastructure Analytics Advisor installation and configuration workflow

Overview 13Hitachi Infrastructure Analytics Advisor Installation and Configuration Guide

Hitachi Infrastructure Analytics Advisor overviewHitachi Infrastructure Analytics Advisor provides a comprehensive applicationservice-level and storage performance management solution that enables youto quickly identify and isolate performance problems, determine the rootcause, and provide solutions. It enables proactive monitoring from theapplication level through all network and storage resources for end-to-endvisibility of your monitored environment. It also increases performance ofexisting storage resources and storage availability by identifying problemsbefore they can affect applications.

Infrastructure Analytics Advisor collects and correlates data from thesesources:• 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 followingcomponents:• Infrastructure Analytics Advisor management server: The primary

component that communicates with the Data Center Analyticsmanagement server. It correlates the configuration and performance dataobtained by Data Center Analytics to generate reports and enable dataanalytics for performance monitoring and problem resolution in yourmonitored infrastructure resources.

• Data Center Analytics management server: This server processesperformance and configuration data received from probes that connect todevices that are enabled for monitoring and makes it available toInfrastructure Analytics Advisor for analyzing, troubleshooting, andreporting.

• Analytics probe server: This server enables you to collect performanceand configuration data from a target.

Related topics

• Infrastructure Analytics Advisor installation and configuration workflow onpage 14

Infrastructure Analytics Advisor installation andconfiguration workflow

This section describes the procedure for installing and configuringInfrastructure Analytics Advisor. The figure that follow shows the workflowfrom installation to configuration.

14 OverviewHitachi Infrastructure Analytics Advisor Installation and Configuration Guide

Configuring Infrastructure Analytics Advisor in secure mode is optional.Communication between management servers, probe server, and the webclient uses a self-signed certificate that is installed by default so that noadditional configuration is required. The following figure shows the variousInfrastructure Analytics Advisor components and communication routes.


The product installation and initial configuration is quick if you use the defaultself-signed certificate installed with the product. However, if you want tostrengthen security for exchange of data between various components in theInfrastructure Analytics Advisor environment, you must do some tasks on theservers to generate certificates and have them verified by a certificate-signing authority before you apply them in your environment.

Installation methods

You can install the Infrastructure Analytics Advisor using the appropriatemethod for your environment.

Table 1 Installation Methods

Component Installation method

Infrastructure Analytics Advisor managementserver

Windows-based installation on a Windows-basedserver

Data Center Analytics management server RPM Package Manager on a Linux server

or

OVA format on a VMware vSphere client

Analytics probe server RPM Package Manager on a Linux server

or

OVA format on a VMware vSphere client

Related topics

• Installing Data Center Analytics management server on page 30• Initial setup of Data Center Analytics management server after installation

on page 38• Installing Analytics probe server on page 39• Initial setup of Analytics probe server after installation on page 48


• Installing Infrastructure Analytics Advisor on page 50• Initial setup of Infrastructure Analytics Advisor on page 52• Adding probes to Analytics probe server on page 55• Configuring secure communications on page 81



2System requirements

This chapter describes the Infrastructure Analytics Advisor systemrequirements.

□ Infrastructure Analytics Advisor management server requirements

□ Data Center Analytics management server requirements

□ Analytics probe server requirements

□ Browser requirements

□ Management target requirements

System requirements 19Hitachi Infrastructure Analytics Advisor Installation and Configuration Guide

Infrastructure Analytics Advisor management serverrequirements

This section describes the Infrastructure Analytics Advisor managementserver requirements.

Table 2 Operating system requirements (Windows)

OS name OS version SP Architecture

Windows Server 2008R21

• Standard• Enterprise• Datacenter

SP1 x64

Windows Server 2012 2 • Standard• Datacenter

No SP x64

Windows Server 2012R22

• Standard• Datacenter

No SP x64

Table 3 Hardware requirements (Windows)

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 management server requirementsThis section describes the Data Center Analytics management serverrequirements.

For installation using RPM Package Manager (RPM)

Table 4 Operating system requirements

Supported OS Yum/rpm dependencies Architecture

Red Hat Enterprise Linux6.5-6.7

- perl

- java-1.7.0-openjdk

- expect

x64

20 System requirementsHitachi Infrastructure Analytics Advisor Installation and Configuration Guide

Supported OS Yum/rpm dependencies Architecture

-parted

-openssl-devel

-xfsprogs

Table 5 Hardware requirements



Memory 8 GB 16 GB

Disk space 120 GB 600 GB

Note: Prepare a disk other than the one on the OS on which Data CenterAnalytics management server is installed. You must specify the disk forinstalling the product when you run the (dcaserver_install.sh) installationcommand. You must prepare a physical disk for installing the Data CenterAnalytics management server on physical machines.

Table 6 Desktop prerequisites

Source IP Target IP Default port Protocol

User Desktop Server IP 8443 TCP

Note: The memory requirement and disk capacity vary depending on thenumber of managed resources and frequency of performance data collection.For example, if you monitor a storage system that has a large number ofvolumes, the performance data from these volumes can take up a lot of diskspace in the database. Also, if you increase the frequency of performancedata collection, the required disk space increases.

For installation using Open Virtualization Application (OVA) format onVMware vSphere Client

When the virtual appliance is deployed, a virtual machine with the followingdefault settings is created. Confirm whether the virtualization server hasenough resources to create the virtual machine. The installation directory ofData Center Analytics is /data.

Table 7 Guest operating system settings

Item Settings

OS Oracle Linux 6.7 (Architecture x86_64)


Table 8 Resource settings for the virtual machine

Item Settings

Processor Quad-Core processor (the number of virtualsockets: 4, the number of cores per virtualsocket: 1)

Memory 8 GB

Disk space 120 GB (Configure as two separate disks.)

Analytics probe server requirementsThis section describes the Analytics probe server requirements.

Table 9 Desktop requirements

Source IP Target IP Default port Protocol Notes

User Desktop Server IP 8443 TCP

22 TCP Required forconnecting to theAnalytics probeserver throughthe SSH client

Table 10 Probe port and firewall requirements

Probe nameCollectionmethod


Storage systems

AMS SNM2API Probe machine AMS Controller 2000 TCP

HitachiEnterpriseStorage

RAID Agent Probe machine RAID AgentServer

24221 HTTP

24222 HTTPS

Hitachi DeviceManager API

Probe machine Hitachi DeviceManagerServer

2001 HTTP

2443 HTTPS

HNAS RUSC Probe machine HNAS SMU 22 SSH

Hypervisors

VMware VMwarevCenter API

Probe machine VMwarevCenterServer/VMware ESXHost/VMwareESXi Host

443 TCP

Windows-based(Hyper-V)

WMI Windows-based probemachine

Windows-based host

135 TCP

Perfmon 135 and 445


Probe nameCollectionmethod


SCOM SCOM server 5723, 5724,and 51905

SCCM SCCM server 1433

FC Switches

BrocadeNetworkAdvisor

BNA (RESTAPI)

Probe machine BNA server 80 HTTP

Cisco DCNM DCNM (WebServices)

Probe machine DCNM Server 80 HTTP

443 HTTPS

For installation using RPM Package Manager

Table 11 Operating system requirements

OS name yum/rpm dependenciesCPAN

dependenciesArchitecture

Red HatEnterprise Linux6.5-6.7

• perl

• perl-CPAN

• gcc

• java-1.7.0-openjdk

• samba

• expect

• openssl-devel

• ftp

• unzip

• wget

• glibc.i686

• libstdc++.i686

• net-tools

• tcsh

• libyaml

• YAML• Module::Build

• IO::Pty

• Date::Gregorian

• Date::Calc

• Log::Log4perl

• Net::OpenSSH

• DateTime

• Log::Dispatch::FileRotate

• DateTime::Format::Strptime

• Sys::RunAlone

• HTTP::Request

• LWP::UserAgent

• LWP::Protocol::https

• Time::HiRes

x64


Table 12 Hardware requirements



Memory 8 GB 16 GB minimum

Disk space 100 GB 150 GB minimum

Note: The memory requirement and disk capacity vary depending on thenumber of managed resources and frequency of performance data collection.For example, if you monitor a storage system that has a large number ofvolumes, the performance data from these volumes can take up a lot of diskspace in the database. Also, if you increase the frequency of performancedata collection, the required disk space increases.

For installation using Open Virtualization Application (OVA) format onVMware vSphere Client

When the virtual appliance is deployed, a virtual machine with the followingdefault settings is created. Confirm whether the virtualization server hasenough resources to create the virtual machine. The installation directory ofAnalytics probe is /home.

Table 13 Guest operating system settings

Item Settings

OS Oracle Linux 6.7 (Architecture x86_64)

Table 14 Resource settings for the virtual machine

Item Settings

Processor Quad-Core processor (the number of virtualsockets: 4, the number of cores per virtualsocket: 1)

Memory 8 GB

Disk space 100 GB

Browser requirementsThis section describes the supported browsers.


Table 15 Browser settings

Web browser Browser version

Firefox ESR 38

ESR 45

Internet Explorer 11

Chrome for Work Latest version of stable channel

Flash Player 21.0 or later (to use custom reports in DataCenter Analytics management server)

Management target requirementsThis section describes the supported management targets and itsrequirements.

Table 16 Storage systems

Storage systemseries

Storage systemMicrocode/SMUversion

Analytics probe name

Hitachi VSP Hitachi Virtual Storage Platform (VSP) 07-01 orlater

Hitachi EnterpriseStorage probe1

HUS VM Hitachi Unified Storage VM (HUS VM) 73-01 orlater

VSP Gx00models

Hitachi Virtual Storage Platform G200(VSP G200)

83-01 orlater




VSP Fx00 models Hitachi Virtual Storage Platform F400(VSP F400)

83-01 orlater

Hitachi Virtual Storage Platform F600(VSP F600)

Hitachi Virtual Storage Platform F800(VSP F800)

VSP G1000 Hitachi Virtual Storage Platform G1000(VSP G1000)

80-01 orlater

HUS100 series Hitachi Unified Storage 110 (HUS110) 09-10 orlater

Hitachi Adaptor ModularStorage (AMS) probeHitachi Unified Storage 130 (HUS130)

Hitachi Unified Storage 150 (HUS150)


Storage systemseries

Storage systemMicrocode/SMUversion

Analytics probe name

Hitachi NAS HNAS - HNAS Probe2

Note:1. When using Hitachi Enterprise Storage probe, make sure that the RAID

Manager LIB is installed in the same server as the Hitachi EnterpriseStorage probe.

2. The data collected by the HNAS probe can be viewed in Data CenterAnalytics only.

3. To manage additional information about Hitachi storage systems (such asinformation about storage capacity and hosts), use the Hitachi DeviceManager software 8.4.1 or later.

Table 17 Hypervisors

Product name Version Analytics Probe name

VMware vCenter server 5.0 or later VMware probe

VMware ESXi 5.0 or later

Hyper-V Windows Server 2008

R2 Hyper-V

Hyper-V 2.0 Windows-based probe

Windows Server 2012

Hyper-V

Hyper-V 3.0

Windows Server 2012

R2 Hyper-V

Hyper-V 3.1

Table 18 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


OS name Edition Analytics Probe name

• Datacenter

Table 19 FC switches

Switch name Software Version Analytics Probe name

Brocade Brocade Network

Advisor Professional

Plus

12.0 Brocade Network

Advisor probe

Brocade Network

Advisor Enterprise

12.0

Cisco Cisco Data Center

Network Manager

Not applicable Cisco DCNM Probe



3Installation

This chapter describes how to install a new instance of InfrastructureAnalytics Advisor and configure the required settings after installation.

□ Installing Data Center Analytics management server

□ Installing Analytics probe server

□ Installing Infrastructure Analytics Advisor

Installation 29Hitachi Infrastructure Analytics Advisor Installation and Configuration Guide

Installing Data Center Analytics management serverThis section describes how to install Data Center Analytics managementserver.

Selecting an installation methodUse the appropriate method from the following list to install the Data CenterAnalytics management server:• Installation on Linux host

Use the RPM Package Manager to install Data Center Analyticsmanagement server on a Linux host.

• Installation on VMware vSphere ClientUse the OVA file to install Data Center Analytics management server onVMware infrastructure. Deploy virtual appliance to create a virtual machineand then install Data Center Analytics management server on the VMwarevSphere Client.

Related topics

• Installing Data Center Analytics management server on Linux host onpage 30

• Installing Data Center Analytics management server on VMware vSphereClient on page 34

Installing Data Center Analytics management server on Linux host

You can install the Data Center Analytics management server on a Linux hostusing the RPM Package Manager.

Preparing for installation

Before you begin installation of Data Center Analytics management server ona Linux host, review the following prerequisites.

Prerequisites Description

Review hardware andsoftware requirements

Review the Data Center Analytics management server requirements. Makesure that your site meets all the hardware and software requirements.

Prepare an externalhard drive as theinstallation source

Prepare an external drive for installing the Data Center Analyticsmanagement server on a Linux host. For details about disk spacerequirements for the external drive, see the Data Center Analyticsmanagement server requirements.

Install the followingyum/rpm dependencypackages• perl• java-1.7.0-openjdk• openssl-devel

Install the yum/rpm dependencies from the Linux OS media or Red HatEnterprise Linux website.

The procedure for installing the yum/rpm dependencies using the LinuxOS media disc is as follows:

30 InstallationHitachi Infrastructure Analytics Advisor Installation and Configuration Guide


• expect• parted• xfsprogs

1. Mount the Linux OS media disc and obtain the yum/rpm dependencypackages.mkdir /media/OSImagemount /dev/cdrom /media/OSImage

2. Configure the yum repository.touch /etc/yum.repos.d/OSImage.repoecho [dvd]>>/etc/yum.repos.d/OSImage.repoecho name=dvd>>/etc/yum.repos.d/OSImage.repoecho baseurl=file:///media/OSImage/>>/etc/yum.repos.d/OSImage.repoecho gpgcheck=0>>/etc/yum.repos.d/OSImage.repoecho enabled=1>>/etc/yum.repos.d/OSImage.repo

3. Run the yum command to install the dependency packages.yum install java-1.7.0-openjdk openssl-devel perlexpect parted /media/OSImage/ScalableFileSystem/xfsprogs-3.1.1-16.el6.x86_64.rpmThe package xfsprogs-3.1.1-16.el6.x86_64.rpm differsdepending on your environment. Specify the package that matchesyour environment.

4. Unmount the Linux OS media.umount /media/OSImage/rm /etc/yum.repos.d/OSImage.repo

Port requirements Make sure that the ports you specify are available for communication. Thedefault port for communication is 8443. For more information, review theData Center Analytics management server port and firewall requirements.

User permissions You must have the root user permissions to install the Data CenterAnalytics management server on a Linux host.

Time zone settings Make sure that the console and clock properties are set to the same timezone.

The times and time zones of the following servers must all besynchronized:• Infrastructure Analytics Advisor management server• Data Center Analytics management server• Analytics probe server

License Obtain the Data Center Analytics management server license from yourHDS representative.

Note: You cannot install both Data Center Analytics management server andAnalytics probe server on the same host.

Related topics

• Data Center Analytics management server requirements on page 20• Installation on page 31

InstallationThe procedure for installing Data Center Analytics management server is asfollows:


Procedure

1. Stop all the programs running on the host including any antivirusprograms.

2. Mount the Infrastructure Analytics Advisor installation media and copythe directories and files in the DCA directory on the installation media to adirectory on the Linux machine.mkdir /media/HIAAImagemount /dev/cdrom /media/HIAAImagecp -r /media/HIAAImage/DCA /root/DCA

3. Run the sh ./dcaserver_install.sh NEW command.cd /root/DCA/sh ./dcaserver_install.sh NEWOutput example:

[INFO] Installation of the Data Center Analytics management server has started.

[Partition parameter]------------------------------------------------------------<System device information>NAME MAJ:MIN RM SIZE RO TYPEMOUNTPOINTsr0 11:0 1 3.6G 0 rom /media/cdromsda 8:0 0 60G 0 disk|-sda1 8:1 0 500M 0 part /boot`-sda2 8:2 0 59.5G 0 part|-VolGroup-lv_root (dm-0) 253:0 0 50G 0 lvm /|-VolGroup-lv_swap (dm-1) 253:1 0 3.9G 0 lvm [SWAP]`-VolGroup-lv_home (dm-2) 253:2 0 5.6G 0 lvm /homesdb 8:16 0 300G 0 disk

4. Specify a drive and directory to install the Data Center Analyticsmanagement 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. Specify Y to configure the firewall settings. Specify the IP addresses ofthe Analytics probe servers. You can also accept the default value0.0.0.0 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]: y

Specify the IP addresses of the Analytics probe servers,so that these IP addresses will be added in the configuration of iptables,and the connection from these servers can be accepted.(port


22/tcp)You can also use 0.0.0.0 and change it later.[0.0.0.0]:

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 unitWhat is the name of your organization? [Unknown]: Your organizationWhat is the name of your City or Locality? [Unknown]: Your city or localityWhat is the name of your State or Province? [Unknown]: Your state or provinceWhat 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 : /dataDevice name : /dev/sdbMount point : /dataPort number : 8443Firewall accept rule to be added : Protocol Source IP Destination IP Destination PORT -------- ---------------- ---------------- ---------------- ALL 0.0.0.0 0.0.0.0 ALL <RELATED,ESTABLISHED> TCP 0.0.0.0 0.0.0.0 22 TCP 0.0.0.0 0.0.0.0 8443Distinguished 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------------------------------------------------------------

8. When you are prompted with the following caution message, enter y tocontinue with the installation.

** CAUTION **

* This installation will delete all the partitions on the disk. (/dev/sdb)

* This installation will change iptables settings. (Listing above)

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 DCA service...[INFO] The DCA service started.[INFO] Environment settings have been applied.[INFO] Installation of the Data Center Analytics management server finished successfully.

Next steps

Perform the initial setup of Data Center Analytics management server.

Related topics

• Data Center Analytics management server requirements on page 20• Initial setup of Data Center Analytics management server after installation

on page 38

Installing Data Center Analytics management server on VMwarevSphere Client

You can deploy the Data Center Analytics management server using the OVAfile on VMware infrastructure.

Preparing for installationBefore you begin installation of the Data Center Analytics managementserver on a VMware vSphere Client, review the following prerequisites.


Review hardware and softwarerequirements

Review the Data Center Analytics management server

requirements for installation on VMware vSphere Client. Make sure

that you meet all the hardware and software requirements.

Port requirements Make sure that the ports you specify are available forcommunication. The default port for communication is 8443. Formore information, review the Data Center Analytics managementserver port and firewall requirements.

Time zone settings The times and time zones of the following servers must all besynchronized:• Infrastructure Analytics Advisor management server• Data Center Analytics management server• Analytics probe server

License Obtain the Data Center Analytics management server license from

your HDS representative.

Note: You cannot install both Data Center Analytics management server andAnalytics probe server on the same host.


Related topics

• Data Center Analytics management server requirements on page 20• Installation on page 35

InstallationThe procedure for deploying Data Center Analytics management server onVMware vSphere Client is as follows:

Procedure

1. Open the VMware vSphere Client application.2. From the File menu, select Deploy OVF Template.3. In the Deploy OVF Template window, click Browse, navigate to the

directory that contains the OVA file, select it, and click Next.4. In the OVF Template Details window, verify the details and click Next.5. In the Name and Location window, type the following details and click

Next.• Name: Name for identifying Data Center Analytics

• Inventory location: The inventory in the VMware application to addthe Data Center Analytics management server

6. In the Storage window, select the storage to save the virtual storagefiles, and then click Next.

7. In the Disk Format window, select the appropriate disk format, andthen click Next:• Thick Provision Lazy Zeroed (recommendation): The system

allocates the maximum amount of space at the time of disk creation.Each disk block is zeroed-out only after it is accessed for the first timeby the VMware application.

• Thick Provision Eager Zeroed: The system allocates the maximumamount of space at the time of disk creation. Each disk block iszeroed-out immediately after disk creation.

• Thin Provision: The system allocates only the minimum requiredamount of space at the time of disk creation.

8. Click Next, select the Power on after deployment and, then clickFinish to complete the deployment.

The default settings of the virtual machine network when deployment iscomplete are as follows:• IP address: 172.17.27.48• Net mask: 255.255.128.0• Default gateway: 172.17.0.1

9. (Optional) If an IP address conflict occurs, disable connectivity at poweron, start the virtual machine, and then change the network settings.


The procedure for resolving an IP address conflict is as follows:1. Right-click the virtual machine that you want to edit, and then select

Edit Setting.

2. In the Hardware tab, select Network adapter 1, and then clearthe Connect at power on check box.

3. Start the virtual machine, and then select the Connect at power oncheck box in the same way as described in step 2.

4. Change the network settings using the hvaconfig command,available in /opt/HIAA/vmtool.

Next steps

Run the setup tool on the guest OS, and then specify the initial settings forthe guest OS.

Related topics

• Preparing for installation on page 34• Post installation tasks on page 36• Initial setup of Data Center Analytics management server after installation

on page 38

Post installation tasksAfter deploying the virtual appliance, run the setup tool (hvaconfig) tospecify 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 andpassword:

User ID: root

Password: manager

After you logon, you can change the root password.2. Run the hvaconfig command to start the setup tool.

Note: You can run the setup tool only once. To change the settingsafter running the setup tool, use the operating system commands.

3. In the setup tool, you can specify the following settings.

Network settings• IP address


• Net mask• Default gateway

• 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 donot know the specifiable values, use the following procedure inadvance 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/zoneinfoOf the results output by the command, specify, for area,the name of the directory that includes the time zone thatyou want to specify.

2. Run the following command to check the values that canbe specified for location.ls -F /usr/share/zoneinfo/areaOf the results output by the command, specify, forlocation, the name of the file corresponding to the timezone that you want to specify.

○ The times and time zones of the following servers must besynchronized:– Infrastructure Analytics Advisor management server– Data Center Analytics management server– Analytics probe server

• NTP server

Security setting• Server certificate

4. Check the contents of the list that displays your specified settings, andthen 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. Run the Power On the virtual machine command from the VMwarevSphere Client.

Next steps

Perform the initial setup of the Analytics probe server.

Initial setup of Data Center Analytics management server afterinstallation

This section describes the initial settings for the Data Center Analyticsmanagement server.

Procedure

1. Open your browser, and enter the Data Center Analytics managementserver URL and press Enter.https://<ip_address>:<Port Number>The default port for https access is 8443.

2. When you first launch the Data Center Analytics management server UI,you see the License Agreement details. Read and accept the licenseagreement, and then click Next.

3. Obtain the Data Center Analytics management server license from yourHDS representative.

4. In the Upload License window, click Choose File to browse to a licensefile and click Open.

5. Click Submit to register the license.6. In the Create Administrator Account window, enter the password and

select the locale, and then click Submit.The current version of Data Center Analytics supports only the Englishlocale.

7. In the Data Center Analytics management server login window, enter theadministrator user credentials and click Login.

8. In the Select Time zone window, select the appropriate time zone andclick Next.The Data Center Analytics management server home page is displayed.

Note: Reports display data in the Data Center Analyticsmanagement server time zone. The server time zone settingsapply to all the storage systems. For example, if the server is inthe IST time zone, and one of the storage systems is in theEastern time zone and another in the Central America time zone,the reports of both storage systems display in the IST time zone.

9. Create an Infrastructure Analytics Advisor access user account thatbelongs to the Administrator group on the Data Center Analyticsmanagement server.


For information about how to add accounts, see the HitachiInfrastructure Analytics Advisor Data Center Analytics User Guide.

Note: The following user accounts are created automatically whenyou configure Infrastructure Analytics Advisor for connecting withthe Data Center Analytics management server. Do not change ordelete the information of the following user accounts:• HIAA_Server_Admin

• HIAA_REST_Admin

• HIAA_REST_Normal

• HIAA_GUI_Report

Installing Analytics probe serverThis section describes how to install Analytics probe server.

Selecting an installation methodUse the appropriate method from the following list to install the Analyticsprobe server:

• Installation on Linux hostUse the RPM Package Manager to install Analytics probe server on a Linuxhost.

• Installation on VMware vSphere ClientUse the OVA file to deploy Analytics probe on VMware infrastructure.Deploy virtual appliance to create a virtual machine and then installAnalytics probe server on the client.

When you install Analytics probe server, the RAID Agent is also installed.

Related topics

• Installing Analytics probe server on Linux host on page 39• Installing Analytics Probe server on VMware vSphere Client on page 44

Installing Analytics probe server on Linux host

You can install the Analytics probe server on a Linux host using the RPMPackage Manager. The RAID Agent is installed with the Analytics probe server.

Preparing for installationBefore you begin installation of Analytics probe server on a Linux host,review the following prerequisites.




Review the Analytics probe server requirements. Make sure that

you meet all the hardware and software requirements.

Install Data Center Analytics

management server

Make sure that you install the Data Center Analytics managementserver, before you install the Analytics probe server. The DataCenter Analytics management server’s IP address is required forsetting up the Analytics probe server.

Install the following yum/rpmdependency packages:• perl• perl-CPAN• gcc• java-1.7.0-openjdk• samba• expect• openssl-devel• ftp• unzip• wget• glibc.i686• libstdc++.i686• net-tools• tcsh• libyaml

You can install the yum/rpm dependencies from the Linux OSmedia or Red Hat Enterprise Linux website.

The procedure for installing the yum/rpm dependencies using theLinux OS media disc is as follows:1. Mount the Linux OS media disc and obtain the yum/rpm

dependency packages.

mkdir /media/OSImagemount /dev/cdrom /media/OSImage

2. Configure the yum repository.

touch /etc/yum.repos.d/OSImage.repoecho [dvd]>>/etc/yum.repos.d/OSImage.repoecho name=dvd>>/etc/yum.repos.d/OSImage.repoecho baseurl=file:///media/OSImage/>>/etc/yum.repos.d/OSImage.repoecho gpgcheck=0>>/etc/yum.repos.d/OSImage.repoecho enabled=1>>/etc/yum.repos.d/OSImage.repo

3. Run the yum command to install the dependency packages.yum install perl perl-CPAN gcc java-1.7.0-openjdk sambaexpect openssl-develftp unzip wget glibc.i686 libstdc++.i686 net-tools tcshlibyamlNote: If the environment you are using already has thelibstdc ++ package installed, x86_64 (the 64-bit library)and i686 (the 32-bit compatibility library) packages mightbe different versions. Therefore, installation of libstdc++.i686 might fail with an error message such as thefollowing:Protected multilib versions: libstdc++-xx.xx.xxxx.xx.el6.i686 != libstdc++-yy.yy.yyyy.yy.el6.x86_64If this happens, update x86_64 (the 64-bit library), andthen retry the installation of libstdc++.i686.#update libstdc++.x86_64yum update libstdc++.x86_64

4. Unmount the Linux OS media.

umount /media/OSImage/rm /etc/yum.repos.d/OSImage.repo

Review RAID Agent installationrequirements

When you install the Analytics probe server, the RAID Agent isinstalled automatically. Review the RAID Agent requirementsbefore you begin installation.• Check the installation directory



The installation directory is fixed (/opt/jp1pc) and cannot bechanged. Make sure that the /opt/jp1pc directory is empty.Also, make sure that you do not include any symbolic links inthe installation path.

• Check the work directory for installationWhen you install an agent, a temporary work directoryjp1pc_AGT in the /opt or /opt/jp1pc directory is created.This directory is automatically deleted after the installation issuccessful.If an error occurs during installation, verify the directoryexists, and delete it manually.

• Check the attributes of the installation directoryIf any attributes of the installation directory are different fromthe product-defined directory attributes, they are changed.

• Resolve the IP addressYou must define a hosts file or domain name system (DNS)environment so that the IP address can be resolved from thename of each host on which an agent is installed. Configurethe environment so that the IP address can be resolved fromthe host name using the uname -n command.

• Specify fixed IP addressThe RAID Agent cannot run on hosts that use DHCP to assignIP addresses. Specify a fixed IP address for Analytics probeserver.

• Check the name of the host on which RAID Agent isinstalledInfrastructure Analytics Advisor can be used in a DNSenvironment but does not support FQDN. Therefore, you mustexclude the domain name when you specify the host name.

• Setting the LANG environment variableBefore setting up the RAID Agent, you must specify C for theLANG environment variable on the Analytics probe serverhost.

Port requirements Make sure that the ports you specify are available forcommunication. The default port for communication is 8443. Thedefault port for SSH communication to the Analytics probe serveris 22. For more information, review the Analytics probe serverrequirements.

User permissions You must have the root user permissions to install the Analyticsprobe server on a Linux host.


License Obtain the Analytics probe server license from your HDS

representative.

Note:• You cannot install both Data Center Analytics management server and

Analytics probe server on the same host.


• You cannot install Analytics probe server on a host on which the followingproducts are installed:• Hitachi Command Suite Tuning Manager• Agent products of Hitachi Command Suite Tuning Manager

Related topics

• Analytics probe server requirements on page 22• Installation on page 42

InstallationThe procedure for installing Analytics probe server on a Linux host is asfollows:

Procedure

1. Stop all the programs running on the host including the antivirusprogram.

2. Mount the Infrastructure Analytics Advisor installation media and copythe directories and files in the DCAPROBE directory on the installationmedia to a directory on the Linux machine.mkdir /media/HIAAImagemount /dev/cdrom /media/HIAAImagecp -r /media/HIAAImage/DCAPROBE /root/DCAPROBE

3. Run the sh ./dcaprobe_install.sh NEW command.cd /root/DCAPROBE/sh ./dcaprobe_install.sh NEW

[INFO] Installation of the Data Center Analytics probes has started.

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]: 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 unitWhat is the name of your organization? [Unknown]: Your organizationWhat 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 provinceWhat 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/RAIDAgentData directory (for the Analytics probe server) : /homePort number (for the Analytics probe server) : 8443,24221Firewall accept rule to be added : Protocol Source IP Destination IP Destination PORT -------- ---------------- ---------------- ---------------- ALL 0.0.0.0 0.0.0.0 ALL <RELATED,ESTABLISHED> TCP 0.0.0.0 0.0.0.0 8443 TCP 10.197.102.197 10.197.102.197 ALL TCP 127.0.0.1 127.0.0.1 ALLRequired CPAN libraries : Module::Build YAML IO::Pty Date::Calc Net::OpenSSH DateTime DateTime::Format::Strptime Date::Gregorian Log::Log4perl Log::Dispatch::FileRotate Sys::RunAlone HTTP::Request LWP::UserAgent LWP::Protocol::https Time::HiResDistinguished 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

8. When you are prompted with the following caution message, enter y tocontinue 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] HTTP::Request[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.[INFO] Installation of the Data Center Analytics probes finished successfully.

Next steps

Perform the initial setup of Analytics probe server.

Related topics

• Preparing for installation on page 39• Initial setup of Analytics probe server after installation on page 48

Installing Analytics Probe server on VMware vSphere ClientYou can deploy the Analytics probe server using the OVA file on a VMwarevSphere Client.

Preparing for installationBefore you begin installation of Analytics probe server on a VMware vSphereClient, review the following prerequisites.



Review the Analytics probe server requirements. Make sure that

you meet all the hardware and software requirements.

Port requirements Make sure that the ports you specify are available forcommunication. The default port for communication is 8443. Formore information, review the Analytics probe server requirements.

Review virtual systemoperations

Review the following requirements when you run agents in avirtual environment.• Setting the LANG environment variable

Before setting up the RAID Agent, you must specify C for theLANG environment variable on the Analytics probe server host.

• Configuring settings so that the command device can beaccessed from a guest OS



If you want to monitor the Hitachi Virtual Storage Platform,VSP G1000, VSP Gx00 models, VSP Fx00 models, or HitachiUnified Storage VM, you must specify the settings so thataccesses from a guest OS to command devices becomeavailable. For details, see the documentation for your virtualsystem.Use VMware vSphere Client file to add a device to the guestOS. By doing so, if you designate a command device as thedevice to be added, the command device can be accessed fromthe guest OS.When configuring settings to add a device, make sure that thefollowing requirements are met:○ Device type: Hard disk

○ Disk selection: Raw device mapping

○ Compatibility mode: Physical

○ Virtual disks (including VMware VVols) are not used for thecommand device.

• Note about replicationWhen you use a virtualization system to replicate an OSenvironment in which the RAID Agent is running, do not applythe replicated environment to any other host. Startup of theRAID Agent might fail in the replicated environment.


License Obtain the Analytics probe server license from your HDS

representative.

Related topics

• Analytics probe server requirements on page 22• Installation on page 45

InstallationYou can deploy the Analytics probe server using the OVA file on a VMwarevSphere Client.

Note: The specific installation steps depend on the VMware vSphere Clientversion.

Procedure

1. Open the VMware vSphere Client application.2. From the File menu, select Deploy OVF Template.3. On the Deploy OVF Template window, click Browse, navigate to the

directory that contains the OVA file, select it, and click Next.


4. On the OVF Template Details window, verify the details and click Next.5. On the Name and Location window, type the following details and click

Next:• Name: Name for identifying Analytics probe

• Inventory location: The inventory in the VMware application inwhich to add the probe.

6. On the Storage window, select the storage to save the virtual storagefiles, and then click Next.

7. On the Disk Format window, select the appropriate disk format, andthen click Next:• Thick Provision Lazy Zeroed (recommendation): The system

allocates the maximum amount of space at the time of disk creation.Each disk block is zeroed-out only after it is accessed for the first timeby the VMware application.

• Thick Provision Eager Zeroed: The system allocates the maximumamount of space at the time of disk creation. Each disk block iszeroed-out immediately after disk creation.

• Thin Provision: The system allocates only the minimum requiredamount of space at the time of disk creation.

8. Click Next, select the Power on after deployment, and then clickFinish to complete the deployment.

The default settings of the virtual machine network when deployment iscomplete are as follows:• IP address: 172.17.27.49• Net mask: 255.255.128.0• Default gateway: 172.17.0.1

9. (Optional) If an IP address conflict occurs, disable connectivity at poweron, start the virtual machine, and then change the network settings.The procedure for resolving an IP address conflict is as follows:1. Right-click the virtual machine that you want to edit, and then select

Edit Setting.

2. In the Hardware tab, select Network adapter 1, and then clearthe Connect at power on check box.

3. Start the virtual machine, and then select the Connect at power oncheck box in the same way as described in step 2.

4. Change the network settings using the hvaconfig command.


Next steps

Run the setup tool on the guest OS, and then specify the initial settings forthe guest OS.

Related topics

• Preparing for installation on page 44• Initial setup of Analytics probe server after installation on page 48

Post installation tasksAfter deploying the virtual appliance, run the setup tool (hvaconfig) tospecify 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 andpassword:

User ID: root

Password: manager

After you logon, you can change the root password.2. Run the hvaconfig command to start the setup tool.

Note: You can run the setup tool only once. To change the settingsafter running the setup tool, use the operating system commands.

3. In the setup tool, you can specify the following settings.

Network settings• IP address• Net mask• Default gateway

• 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 donot know the specifiable values, use the following procedure inadvance 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/zoneinfoOf the results output by the command, specify, for area,the name of the directory that includes the time zone thatyou want to specify.

2. Run the following command to check the values that canbe specified for location.ls -F /usr/share/zoneinfo/areaOf the results output by the command, specify, forlocation, the name of the file corresponding to the timezone that you want to specify.

○ The times and time zones of the following servers must besynchronized:– Infrastructure Analytics Advisor management server– Data Center Analytics management server– Analytics probe server

• NTP server

Security setting• Server certificate

4. Check the contents of the list that displays your specified settings, andthen 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. Run the Power On the virtual machine command from the VMware

vSphere Client.

Next steps

Perform the initial setup of the Analytics probe server.

Initial setup of Analytics probe server after installationThis section describes the initial settings for the Analytics probe server.


Procedure

1. Open your browser, and type the Analytics probe server URL and pressEnter.https://<Analytics probe IP Address>:8443

2. When you first launch the Analytics probe server UI, you see the licenseagreement details. Read and accept the license agreement, and thenclick Next.

3. Obtain the Analytics probe server license from your HDS representative.4. In the Upload License window, click Choose File to browse to a license

file and click Open.5. Click Submit to register the license.6. In the Create Administrator Account window, specify the following

details, and then click Submit.• User name and password.

• First name, last name, and email of the user.• Locale: Analytics probe server is available in two languages – US

English and Japanese.• Group: Select Admin to create an administrator account.

7. In the Analytics probe server login window, enter the administrator usercredentials and click Login.

8. In the Basic Information window, specify the following details, andthen click Next.• Customer Name: The customer name displays by default. You cannot

modify the customer name. This field displays the customer nameincluded in the license.

• Administrator Contact Name and the Administrator ContactEmail: Specify the administrator's contact details.

• Technical Contact Name and Technical Contact Email: Specifythe point of contact (generally administrator) to notify about thetechnical problems.

9. In the Select Time zone window, select an appropriate time zone, andthen click Next.

10. In the FTP Information window, specify the following details, and thenclick Next.• FTP Method: Select the SFTP method.

• Server: Enter the Data Center Analytics management server IPaddress where you want to upload the data.

• Port: Port displays based on the selected FTP method.

• User: Enter the FTP server user name as meghadata.

• Password: Enter the user password as meghadata123.


• Passive: Select Passive to connect the FTP server in Passive mode.The default connection of FTP is in Active mode.

• Proxy: Select Proxy to provide the proxy details.

11. In the Data Collection duration window, verify the data collectionduration which is defined by your license, and then click Next.

12. In the Add Probes window, from the Probes list, select the probe typeand configure the probe to collect data from the monitoring target. Theprobes list displays the probes that you are licensed to use. You mustadd at least one probe to complete the installation.To add additional probes, go to the Analytics probe server web UI homepage and click Add Probe. You can add the following probes on theAnalytics probe server for collecting data from the monitoring targets:• Hitachi Adaptable Modular Storage (AMS) probe

• Hitachi enterprise storage probe

• HNAS probe

• VMware probe

• Brocade Network Advisor probe

• Cisco DCNM probe

Installing Infrastructure Analytics AdvisorThis section describes how to install Infrastructure Analytics Advisor server.

Preparing for installationBefore you begin installation, review the following prerequisites.

Prerequisite Description


Review the Infrastructure Analytics Advisor management server

requirements. Make sure that you meet all the hardware and

software requirements.

Install Data Center Analytics

management server

Perform the tasks in the section Installing the Data CenterAnalytics management server.

Install Analytics probe server Perform the tasks in the section Installing the Analytics probeserver.



Related topics

• Infrastructure Analytics Advisor management server requirements onpage 20

• Installing Infrastructure Analytics Advisor on page 51• Post installation tasks on page 51

Installing Infrastructure Analytics AdvisorThis section provides information about installing Infrastructure AnalyticsAdvisor.

Procedure

1. Log on to the machine where Infrastructure Analytics Advisor is to beinstalled as a user with the Administrator permission, and then close allprograms, including antivirus programs.

2. Run ANALYTICS.msi on the installation media to start InfrastructureAnalytics Advisor Installer.An installation wizard appears.

3. Go through the on-screen prompts and specify the required informationto complete the installation.

The default installation folder of Infrastructure Analytics Advisor is asfollows:

C:\Program Files\HITACHI

Note: You can specify only a fixed disk for the installation folder ofInfrastructure Analytics Advisor. You cannot install InfrastructureAnalytics Advisor on removable media, network drives, and UNCpaths.

Result

Infrastructure Analytics Advisor is now installed.

Related topics

• Preparing for installation on page 50• Post installation tasks on page 51• Initial setup of Infrastructure Analytics Advisor on page 52

Post installation tasksLog on and verify that the installation is successful by accessing theInfrastructure Analytics Advisor web interface.


Procedure

1. Open a web browser, and type the URL for the Infrastructure AnalyticsAdvisor management server in the address bar:

http://host-name-or-IP-address-of-the-server-on-which-Infrastructure Analytics Advisor-is-installed:22015/Analytics/login.htm

Note: Add the Infrastructure Analytics Advisor product URL to thelist of exceptions in your browser's popup blocker.

2. Obtain the license from your HDS representative.3. In the logon window, click License.

a. Use either of the following methods to register a license:• Enter the license key• Specify the license file

b. Click Save.The license you registered displays in the list of licenses.

4. To log on to the Infrastructure Analytics Advisor management server,type the credentials that follow:• User ID: system

• Password: managerThis is the default password.

Result

The logon is complete, and the Infrastructure Analytics Advisor Dashboarddisplays.

Related topics

• Initial setup of Infrastructure Analytics Advisor on page 52• Configuring secure communications on page 81

Initial setup of Infrastructure Analytics AdvisorThis section describes the initial settings for the Infrastructure AnalyticsAdvisor server.

Setting up a connection with Data Center Analytics management serverSet up a connection with the Data Center Analytics management server sothat the data collected by the Data Center Analytics management server canbe analyzed by the Infrastructure Analytics Advisor management server.


Procedure

1. In the Administration tab, select System Settings > DCAManagement Server.

2. Click Edit Settings, and specify the Data Center Analytics managementserver information for each item.

Note: If you change the password of the specified user in the DataCenter Analytics management server, also change the password tothe same password in Password of the Edit Settings dialog box.

3. Click Check Connection to check if the Data Center Analyticsmanagement server is connected properly.

4. Click OK.

Result

The Data Center Analytics management server is connected.

Changing the system account passwordChange the password for the system account. The system account is a built-in account that has the user management permission, and permissions for allInfrastructure Analytics Advisor operations.

Procedure

1. In the Administration tab, select User Management > Users andPermissions.

2. From the displayed dialog box, display Users, and then select System.3. Click Change Password to change the password.

Configuring the mail serverConfigure the mail server and the email address of the sender to allowInfrastructure Analytics Advisor to notify the administrator of problems thatoccur in target resources and information related to Infrastructure AnalyticsAdvisor operations.

Before you begin

Make sure you have the Admin permission of Infrastructure Analytics Advisor.

Procedure

1. In the Administration tab, select Notification Settings > EmailServer.

2. Click Edit Settings to specify information about the mail server.3. To make sure that the mail server is configured correctly, click Send

Test Mail, and in the dialog box that appears, send a test email.4. Confirm that the test email arrives, and then click Save Settings.


Result

The mail server and sender's mail address are configured.


4Adding probes to Analytics probe server

You can add one or more probes to collect data from different monitoringtargets.

□ Adding Hitachi Enterprise Storage probe

□ Adding Hitachi Adaptable Modular Storage (AMS) probe

□ Adding HNAS 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 55Hitachi Infrastructure Analytics Advisor Installation and Configuration Guide

Adding Hitachi Enterprise Storage probeYou must add the Hitachi Enterprise Storage probe on the Analytics probeserver to monitor the Hitachi enterprise storage systems.

Prerequisites for adding Hitachi Enterprise Storage probeReview the following sections before adding Hitachi Enterprise Storage probe.

Verify the connection between host and monitoring targetsReview the following information if you are monitoring Hitachi Virtual StoragePlatform, VSP G1000, VSP Gx00 models, VSP Fx00 models, or Hitachi UnifiedStorage VM storage systems.

1. RAID Agent accesses storage systems by using the following methods.Verify that the RAID Agent host and the storage system can beconnected by using both methods.• Fibre Channel, Fibre Channel over Ethernet (FCoE), or iSCSI

• TCP/IP connection

2. Verify that the RAID Agent host and the storage system are connectedvia a LAN.

3. Make sure that one of the logical units is assigned to a command device.Command devices must be defined as RAW devices. RAW devices mustcomply with these rules:• Command devices using RAID Agent cannot be used with ZFS file

system. Because using ZFS file system creates a file systemautomatically, the usage conditions listed below cannot be met.

• Do not create file systems in the logical devices specified as thecommand devices.

• Do not mount file systems to the logical devices specified as thecommand devices.

• In a Linux machine environment, the /dev/sd form of the device filename might be changed by rescanning the disk device. Werecommend that you use the WWID based form of the device filename (/dev/disk/by-id/scci hexadecimal-WWID). To specify theWWID based file name:1. Use the jpctdlistraid command to display the /dev/sd form of

the device file name.Example, /opt/jp1pc/tools/jpctdlistraid

56 Adding probes to Analytics probe serverHitachi Infrastructure Analytics Advisor Installation and Configuration Guide

2. Use the ls command to search for the symbolic links managed inthe /dev/disk/by-id directory for the WWID device file namemapped to the corresponding /dev/sd file name.For example, use the following to search for the WWID device filename corresponding to /dev/sdc:ls -la /dev/disk/by-id/* | grep sdc

3. Make the device name specified by this command output theCommand Device File Name.

4. Make sure that the RAID Manager LIB is installed on the RAID Agenthost. Obtain the latest version of RAID Manager LIB from your HDSrepresentative.

5. Verify that a Storage Navigator user account was created. One useraccount is required for each instance. Assign the following role to theuser accounts:

User account role needed for Performance Monitor settings:• Storage administrator (performance management)

User account roles needed to collect performance data viaTCP/IP:

• 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, seethe Storage Navigator manual relevant to your storage system.

6. Confirm that the following settings are set for the instance ofPerformance Monitor for the storage system.

Setting Description

Monitor switch To collect configuration performance data, enable the monitoring switchsetting, and accumulate data by using Performance Monitor with "shortrange" set.


Setting Description

Monitoring-targetCUs

Set the logical devices (on a CU basis) from which you want to collectperformance data. This setting is not required if HUS VM is used.

Monitoring-targetWWNs

Set the performance data collection-target WWNs.

Sampling interval Set the interval at which Performance Monitor collects performance data.If you use Performance Monitor to collect performance data, set "shortrange". The granularity set here becomes the granularity of data that canbe collected by RAID Agent.

For details about how to set the following settings, see the PerformanceMonitor manual relevant to your storage system.

Creating an instance environmentHitachi Enterprise Storage probe collects data by using a TCP/IP connection,or using the command device of Hitachi Virtual Storage Platform, VSP G1000,VSP Gx00 models, VSP Fx00 models, or Hitachi Unified Storage VM. To collectdata, you must create an instance environment of RAID Agent.

Procedure

1. On the Analytics probe server, run the jpcconf inst setup commandwith the service key and instance name specified. When specifying theinstance name as an argument in the jpcconf inst setup command,make sure that the length is from 1 to 32 bytes and only half-widthalphanumeric characters (A-Z, a-z, 0-9) are used.

For example, to create an instance environment for the instance named35053 for RAID Agent, run the following command:

/opt/jp1pc/tools/jpcconf inst setup -key RAID -inst 350532. Set up the instance information for the storage system you will monitor.

Enter the information in accordance with the command's instructions.When entering the displayed default value, or not specifying a value,press only the Enter key.

The following table lists the instance information to be specified.

Item Description

Description Specify 2 as the storage system to be monitored.This item is mandatory.

Method for collecting Specify 3.

Command Device File Name Specify the device file name of the command deviceto be output by using the /opt/jp1pc/tools/jpctdlistraid command. RAID Agent uses thiscommand device to collect information about thestorage system.


Item Description

The /dev/sd* form of the device file name might bechanged by rescanning the disk device. Werecommend that you use the WWID based form ofthe device file name. See Prerequisites for usingHitachi Enterprise Storage probe to monitor storagesystems for details about assigning a WWID baseddevice file name.

Mainframe Volume Monitoring# Select Y to monitor a logical device for which theemulation type used for a mainframe is set.• For Hitachi Unified Storage VM, mainframe

emulation is not supported. Mainframe volumesare excluded from monitoring when an HUS VM ismonitored.

• If no value is entered, the default value N is setand the logical unit for a mainframe is notmonitored.

• If you enter a value other than Y, y, N, or n, thesystem prompts you to enter a value again.

Unassigned Open Volume Monitoring# Specify Y to monitor a logical device or an paritygroup for which an open system emulation type hasbeen set and that has not been mapped to a port.• If no value is entered, the default value N is set.

• If you enter a value other than Y, y, N, or n, thesystem prompts you to enter a value again.

Storage IP Address or Host Name Specify the IP address or host name of the storagesystem to which the command device specified forCommand Device File Name belongs.

Storage User Credentials Specify the user credentials of the Storage Navigatoruser account.

Java VM Heap Memory Specify the amount of memory available in Java VM.Specify the largest value that does not exceed thephysical memory of the RAID Agent host. The defaultis 1.• If 1 is specified: Make 0.5 GB available.• If 2 is specified: Make 1.0 GB available.• If 3 is specified: Make 2.0 GB available.• If 4 is specified: Make 4.0 GB available.• If 5 is specified: Make 8.0 GB available.

Details of storage model Specify the storage type.• If 11 is specified: Hitachi Virtual Storage Platform• If 12 is specified: VSP G1000• If 21 is specified: HUS VM• If 22 is specified: VSP Gx00 models or VSP Fx00

models

SVP Port No Specify the port number if Detailed Storage Model isset to 22 (VSP Gx00 models or VSP Fx00 models).You can specify a value from 0 to 65535. The defaultvalue is 1099.


Item Description

This value is the same as the initial value for theRMIIFRegist port number of the storage system. Tochange the port number of the storage system, seethe part of the storage system's manual thatexplains how to change or initialize the port numberto be used with the SVP.

Serial No Specify the serial number of the storage system ifDetailed Storage Model is set to 22 (VSP Gx00models or VSP Fx00 models). You can specify a valuefrom 10000 to 999999.

SVP HTTPS Port No Specify the port number that is used for connectionvia the HTTPS protocol, from a host on which RAIDAgent is installed, to the SVP. You can specify a valuefrom 0 to 65535. The default value is 443.

This value is the same as the initial value for theMAPPWebServerHttps port number of the storagesystem. To change the port number of the storagesystem, see the part of the storage system's manualthat explains how to change or initialize the portnumber to be used with the SVP.

# Depending on the microcode version of the storage system, you might not be able to usethe Mainframe Volume Monitoring or Unassigned Open Volume Monitoring function eventhough you have enabled the setting.

3. To do the operation with multiple instances, repeat steps 1 and 2 foreach instance.

4. Make sure that RAID Manager LIB is installed.5. Before you start operation in an instance environment you have created,

run the jpctdchkinst command to verify the instance settings.

The jpctdchkinst command references the set instance information andchecks whether the settings allow information to be collected from thestorage system monitored by RAID Agent.

/opt/jp1pc/tools/jpctdchkinst –inst instance-name6. Start RAID Agent instance services.

Related topics

• Verify the connection between host and monitoring targets on page 56

Instance settings for monitoring logical device or parity groups

You must specify instance information for the storage system that RAIDAgent will monitor.

The following table shows the types of logical devices and parity groups inthe Hitachi Virtual Storage Platform, VSP G1000, VSP Gx00 models, VSPFx00 models, and Hitachi Unified Storage VM, and the corresponding settingsfor the instance information for monitoring these logical devices and paritygroups.


Type of logical device or parity groupSettings for monitoring a logical device

or parity group

A logical device or paritygroup for which an opensystem emulation typehas been set

A logical device or paritygroup that has beenmapped to a port

The logical device or parity group isalways monitored regardless of thesettings for the instance information.

A logical device or paritygroup that has not beenmapped to a ports

By default, the logical device or paritygroup is not monitored. To monitor thelogical device or parity group, you need tospecify Y or y for Unassigned OpenVolume Monitoring when you set theinstance information.

A logical device or parity group for which a mainframesystem emulation type has been set

By default, the logical device or paritygroup is not monitored. To monitor thelogical device or parity group, you need tospecify Y or y for Mainframe VolumeMonitoring when you set the instanceinformation.

Note: For Hitachi Unified Storage VM,mainframe emulation is not supported.Mainframe volumes are excluded frommonitoring when an HUS VM is monitored.

Also note that you cannot set an LU path for pool volumes for Copy-on-WriteSnapshot or Dynamic Provisioning. Therefore, to obtain performanceinformation related to the usage of a parity group that contains pool volumesfor Copy-on-Write Snapshot or Dynamic Provisioning, you need to specify Yor y for Unassigned Open Volume Monitoring. If Mainframe HDP ismonitored, you must specify Y or y for Mainframe Volume Monitoring. Usethe jpcconf inst setup command to create an instance environment.

Canceling setup of an instance environment

To cancel setup of multiple instance environments, you must delete theagent's instance environment on the agent host:

Procedure

1. Find the instance name of RAID Agent using the jpcconf inst listcommand.

/opt/jp1pc/tools/jpcconf inst list –key RAID

For example, if the instance name is 35053, the command displays35053.

2. Stop the RAID Agent services in the instance environment if it is active.3. Delete the instance environment using the jpcconf inst unsetup

command.

/opt/jp1pc/tools/jpcconf inst unsetup –key RAID –inst instance-name


Result

If the command is successful, the directories created during instanceenvironment setup are deleted. If a service with the specified instance nameis 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 35053

Starting and stopping Agent services

Before you beginLog 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 to move to the /opt/jp1pc directory:

cd /opt/jp1pc2. 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 of the service automatic start script to theservice automatic start script file to add execution permission. Runthe command as follows:cp -p jpc_start.model jpc_startchmod 555 jpc_start

Note: At startup, RAID Agent is subject to the LANG environmentvariable set in the environment where it operates. In an environmentwhere the LC_ALL environment variable is set to a different value fromthe LANG environment variable, either unset the LC_ALL environmentvariable or change its value to match the LANG environment variable.Use the following example as a reference when setting the LANGenvironment variable for RAID Agent:


Example settings:## Set Environment-variablesPATH=/sbin:/bin:/usr/bin:/opt/jp1pc/binSHLIB_PATH=/opt/hitachi/common/libLD_LIBRARY_PATH=/opt/hitachi/common/libLIBPATH=/opt/hitachi/common/libHCCLIBCNF=/opt/jp1/hcclibcnfLANG=Cexport PATH SHLIB_PATH LD_LIBRARY_PATH LIBPATH HCCLIBCNF LANGunset LC_ALL#

# An example of coding that unsets the LC_ALL environmentvariable.

To stop services manually:

Run the following command:/opt/jp1pc/htnm/bin/htmsrv stop -all

To stop services automatically:1. Run the following command to move to the /opt/jp1pc directory:

cd /opt/jp1pc2. 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 theservice automatic stop script file to add execution permission. Runthe command as follows:cp -p jpc_stop.model jpc_stopchmod 555 jpc_stop

Adding Hitachi Enterprise Storage probeHitachi Enterprise Storage probe collects data by using a TCP/IP connection,or using the command device of Hitachi Virtual Storage Platform, VSP G1000,VSP Gx00 models, VSP Fx00 models, or Hitachi Unified Storage VM.

The steps to configure the Hitachi Enterprise Storage probe are as follows:1. Configure the probe to use the RAID Agent.

2. Specify the collection interval for the RAID Agent.

3. (Optional) Configure the probe to use Hitachi Device Manager.


Before you begin

Verify that the storage instance is added in the RAID Agent and datacollection is started for that instance.

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

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: HESP53076.

Note: Special characters are not allowed. The name must beunique in the Data Center Analytics deployment, because it isused for creating unique folders, file name, and so on for theprobe in Data Center Analytics.

• Connection Type: Choose HTTP.

• RAID Agent IP Address: IP address of the machine on which theRAID Agent is installed.

• RAID Agent Host name: Host name of the machine on which theRAID Agent is installed.

Note: The host name must match (case-sensitive) the RAIDAgent’s host name.

• RAID Agent Port: Port number used by the RAID Agent on the RAIDAgent host.Default port number: 24221

• Storage System Serial number: The serial number of the storagesystem that is configured on the RAID Agent.

• Storage System Instance: Storage instance name (alias) that isused to register the storage system on the RAID Agent.

4. In the Configure RAID Agent Collection Interval window, change thedata collection value as necessary, and then click Next.


Note: The Configure RAID Agent Collection Interval windowlists the default RAID Agent data collection time. If you change thecollection interval, then make sure that you change it on the RAIDAgent.

5. On the Provide Hitachi Device Manager details window, select theappropriate option for collecting configuration metrics from HitachiDevice Manager.• Select No to skip this step.

Note: If you select No, then the Provide Hitachi DeviceManager details section is unavailable. Click Next, and amessage appears, stating that the Hitachi Enterprise Storageprobe is successfully added.

• Select Yes to enable the Provide Hitachi Device Manager details.

If Provide Hitachi Device Manager details is enabled, type the followingdetails, and then click Next:• Connection Type: Choose HTTP or HTTPS

• IP Address: IP address of the Hitachi Device Manager (HDvM) serverfor accessing the XML API.Example, http://<Device Manager IP Address>:<Port>/service/StorageManager

• Port: Port number of the Hitachi Device Manager serverDefault port numbers:2001-HTTP2443-HTTPS

• Username/Password: Username and Password of the Hitachi DeviceManager.

6. In the Validation window, Click Next, and then OK.7. On the Status window, in Action, click Start to start collecting data.

Related topics

• Default collection and data export interval for probes on page 163• Initial setup after adding a probe on page 69

Adding Hitachi Adaptable Modular Storage (AMS) probeThe AMS probe collects data through the HUS storage controllers.


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 AMS.3. In the Probes Details section, type the following details, and then click

Next.• AMS Storage Name: Name of the HUS storage system for which the

probe is added. This must not be the same as the storage name thatis defined in your environment.

Note: After you add the probe, it is identified with this name inthe Analytics probe.

• Controller 0 IP address and Controller 1 IP address: IPaddresses of Controller 0 and Controller 1.

• User name and Password: User name and password of the user withread-only permissions.

Note: If the user authentication for the HUS storage is disabled,then you must type a dummy user name and password becausethese 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


Adding HNAS probeThe HNAS probe collects data from Hitachi NAS Platform.

Procedure


HNAS.3. In the Probes Details section, type the following details, and then click

Next:• HNAS SMU IP: The IP address of the HNAS System Management Unit

(SMU).

• User name and Password: The user credentials to connect to SMU.


4. In the Validation window, click Next.5. In the Choose Server window, select the server, and then click Next.

The Choose Server window list all servers associated with 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


Adding VMware probeVMware probe collects data from the VMware vCenter Server and standaloneVMware 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. Read-only privileges are sufficient.

• Password: Password of the VMware vCenter user.


Related topics


Adding Brocade Network Advisor probeBrocade Network Advisor probe collects data from Brocade Network Advisor,which manages the entire Brocade IP address and SAN portfolio for unifiednetwork visibility and control.

Before you begin• The user must have Area of Responsibility as All Fabrics and at least one

role SAN Discovery setup or Performance with read-only permissions.


• Brocade Network Advisor Professional plus or Brocade Network AdvisorEnterprise must be installed.

Procedure


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 BorcadeNetwork Advisor.

• Collect Event Logs: Select this check box to collect log data to seelog analysis of the server.


Related topics


Adding Cisco DCNM probeThis probe collects data from Cisco Data Center Network Manager, amanagement 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 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 webservice on the DCNM server.

Note: In some environments, the port number is optional.Example, http://<dcnmip>:80/sanService, here the 80 isport number.

• Protocol : Select HTTP or HTTPS.


• User name and password of DCNMDefault Ports:80 - HTTP443 - 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 probeAfter adding a probe, check whether data is being collected by Data CenterAnalytics management server and is ready to be analyzed by InfrastructureAnalytics Advisor management server.

Procedure

1. Open a web browser, and then enter the following URL in the address barto log on to Data Center Analytics:

https://IP-address-of-the-server-on-which-Data Center Analytics-is-installed:8443/

2. In the displayed window, enter the following information to log on:• User ID：user-name-that-was-set-during-the-set-up-of-Data Center

Analytics

• Password: password-that-was-set-during-the-setup-of-Data CenterAnalytics

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 theprobe appears in the Data Center Analytics web client.

5. Open a web browser, and then enter the following URL in the address barto log on to Infrastructure Analytics Advisor:

http://IP-address-of-the-server-on-which- Infrastructure AnalyticsAdvisor-is-installed:22015/Analytics/login.htm

6. In the display window, enter the following information to log on:• User ID: system



7. In the Administration tab, select Resource Management.8. Verify that the resources monitored by the probe appear and are ready

to be analyzed by Infrastructure Analytics Advisor.

Note: After a probe is added, it might take some time before theregistered resources appear.


5Installing Data Center Analytics

Windows-based probe

Data Center Analytics Windows-based probe is desktop-based software thatcollects performance and configuration data from the Windows-based hostand Hyper-V machines. You can install this probe using Data Center AnalyticsWindows-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 Windows-based probe 71Hitachi Infrastructure Analytics Advisor Installation and Configuration Guide

Data collection methods

You can use one of the following methods to collect data using the Windows-based 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 permissionto log on remotely to the SCOM server.

• Remote registry service must be running on the machine that is configuredin the SCOM server.

• Access to the SCOM console, to import Management Pack in the SCOMserver, and this pack configures the performance rules.

• Add following DLLs in Data Center Analytics Windows-based probe installerfolder:\binMicrosoft.EnterpriseManagement.OperationsManager.Common.dllMicrosoft.EnterpriseManagement.OperationsManager.dllThe above DLLs are under the following folder on Windows-based machineSystem 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 targetmachines. This agent collects required configuration data and stores it inthe SCCM database.

• A user from the db_datareader group in the SQL Server who can accessthe 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.

72 Installing Data Center Analytics Windows-based probeHitachi Infrastructure Analytics Advisor Installation and Configuration Guide

Prerequisites

SCOM• Target Windows-based machines must be configured in the SCOM server.

• A user with Advanced Operator or Administrator role with the permissionto log on remotely to the SCOM server.

• Remote registry service must be running on the machine that is configuredin SCOM server.

• Access to the SCOM console, to import Management Pack in the SCOMserver, and this pack configures the performance rules.

• Add following DLLs in Data Center Analytics Windows-based probe installerfolder:\binMicrosoft.EnterpriseManagement.OperationsManager.Common.dllMicrosoft.EnterpriseManagement.OperationsManager.dllThe above DLLs are under the following folder on Windows-based machineSystem 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 thetarget machine.

The Execute Methods and Remote Enable permissions are required forthe namespaces.

• Firewall exceptions must be added for the WMI on the target machine. Toadd the exceptions run the following commands on the target machine:○ netsh firewall set service RemoteAdmin

○ netsh firewall set service type=fileandprint mode=enableprofile=all scope=all

• For workgroup computers: Change the settings for the Remote UserAccount Control (UAC) LocalAccountTokenFilterPolicyregistry entry.For more information, see http://support2.microsoft.com/kb/942817/en-us.

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• The probe machine and the target machines must be part of either

workgroup or domain.


http://support2.microsoft.com/kb/942817/en-us


• Firewall exceptions must be added for the WMI and Perfmon on the targetmachine. To add the firewall exceptions, run the following commands onthe target machine:○ netsh firewall set service RemoteAdmin

○ netsh firewall set service type=fileandprint mode=enableprofile=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 forthe following registry key:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurePipeServers\winreg

• For domain computers: A user with the Domain Administrator role orlocal administrator group of the target machine.

• For workgroup computer: The following settings are required if you arenot 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 targetmachine.Execute Methods and Remote Enable permissions are required forthe namespaces.

○ Change the settings for the Remote User Account Control (UAC)LocalAccountTokenFilterPolicy registry entry. For more information, see http://support2.microsoft.com/kb/942817/en-us.

○ 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. On the Log on Information window, type the Domain Administrator’s or

Local user’s user name and password for the Windows-based machine inthe format specified on the window, and click Next.



Note: The user must have the Logon as a Service permission.

4. On the Choose Destination Location window, browse to select theinstallation folder, and click Next.

5. On the Ready to Install the Program window, click Install tocomplete the installation.

6. Click Finish.

Configuring Data Center Analytics Windows-based probeThis section describes the settings that must be configured after Windows-based probe is installed.

Configuring the collection method

Procedure

1. Double-click the Windows Probe icon on the desktop.

Note: If you do not see the icon on the desktop, then in thecommand prompt, run the command ie4uinit.exe –ClearIconCache

This refreshes the icon in the database.

2. In the License tab, browse to the license file and click Submit toregister the probe.

3. Click the Collection tab, and configure the collection method settingsbased on your requirements:

Method 1: Data collection from SCOM and SCCM1. 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 thefollowing details:• SCCM Database Server: SCCM Server IP address or the name.

• Database Name: SCCM database name.

• SQL Server User Name: SCCM database user name.


• SQL Server Password: SCCM database password.

Note: If you select the Trusted Connection check-box, then theSQL Server User Name and SQL Server Password fields aredisabled.

Method 2: Data collection from SCOM and WMI1. 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 thefollowing 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 PerfMon1. 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\UserComputer Name: Machine name on which the Windows-basedprobe is installed.User: A user with an Administrator role.

• In the Active Directory environment: Domain Name\UserDomain Name: Name of the domain.User: A user with the Domain Administration role.

b. Password: Password for the user name typed in the User field.

3. To collect event logs, in the Configuration section, select theCollect Event Logs check box. To allow you to select the types oflogs.


4. In the Performance section, select Collect Process.

4. On the Collection tab, in the right most side section, click DiscoverHosts or Add Hosts, to add the host:

Discover Hosts: Click Discover Hosts to discover the hosts available inthe current domain. From the available host you can select the targethost that you want to monitor.

Add Hosts: Click Add Hosts, and type host names manually. The AddHosts window appears, enter a comma-separated list of Windows-basedmachines (host names or IP addresses) that you want to monitor.

5. Click Validate & Save to establish the connection, and click OK.

Related topics

• Starting the Windows-based probe service on page 78

Configuring the FTP or HTTPS serverYou must configure the FTP server for the Windows-based probe to senddata.

Procedure

1. On the Windows-based probe console, click the Upload Settings tab.2. On the Upload Settings window, select the protocol SFTP or HTTPS.3. Type the following details:

• FTP Server: Type the Data Center Analytics management server IPaddress where you want to upload the data.

• Port: Port number. The default port for SFTP is 22.

• User: meghadata

• Password: meghadata123

4. To use a proxy server, select the Use Proxy check box and type thefollowing 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. See Starting the Windows-based

probe service.


Related topics

• Starting the Windows-based probe service on page 78

Starting the Windows-based probe service

Procedure

1. On the Windows-based probe console, click the Status tab.The Status window list the details of the upload information and serviceinformation.

2. Verify the upload and service information, and click Start.

Initial setup after adding a probeAfter adding a probe, check whether data is being collected by Data CenterAnalytics management server and is ready to be analyzed by InfrastructureAnalytics Advisor management server.

Procedure

1. Open a web browser, and then enter the following URL in the address barto log on to Data Center Analytics:

https://IP-address-of-the-server-on-which-Data Center Analytics-is-installed:8443/

2. In the displayed window, enter the following information to log on:• User ID：user-name-that-was-set-during-the-set-up-of-Data Center

Analytics

• Password: password-that-was-set-during-the-setup-of-Data CenterAnalytics

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 theprobe appears in the Data Center Analytics web client.

5. Open a web browser, and then enter the following URL in the address barto log on to Infrastructure Analytics Advisor:

http://IP-address-of-the-server-on-which- Infrastructure AnalyticsAdvisor-is-installed:22015/Analytics/login.htm

6. In the display window, enter the following information to log on:• User ID: system



7. In the Administration tab, select Resource Management.8. Verify that the resources monitored by the probe appear and are ready

to be analyzed by Infrastructure Analytics Advisor.

Note: After a probe is added, it might take some time before theregistered resources appear.



6Configuring secure communications

This chapter describes the settings required to ensure security.

□ About security settings

□ Configuring an SSL server (Infrastructure Analytics Advisor managementserver)

□ Configuring SSL servers (Data Center Analytics management andAnalytics probe servers)

Configuring secure communications 81Hitachi Infrastructure Analytics Advisor Installation and Configuration Guide

About security settingsIn Infrastructure Analytics Advisor, you can use SSL and SSH to ensuresecure network communications. In SSL and SSH communications,communication routes are encrypted to prevent information leakage anddetect any data manipulation during transfer. You can further enhancesecurity using authentication.

In Infrastructure Analytics Advisor, SSL communication can be used for thefollowing routes:• Between the Infrastructure Analytics Advisor management server and web

clients

• Between the Data Center Analytics management server and web clients(by default)

• Between the Analytics probe server and web clients (by default)

• Between the Infrastructure Analytics Advisor management server and theData Center Analytics management server (by default)

In Infrastructure Analytics Advisor, SSH communication is always usedbetween the Data Center Analytics management server and the Analyticsprobe server.

If you use a certificate issued by a trusted certificate authority, use theinformation 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, youare not able to connect to Infrastructure Analytics Advisor using a secureconnection.

Configuring an SSL server (Infrastructure Analytics Advisormanagement server)

Use this section to configure the Infrastructure Analytics Advisormanagement server as an SSL server. Tasks include creating a private keyand a certificate signing request, applying for a server certificate, andconfiguring secure communication.

Creating a private key and a certificate signing request forInfrastructure Analytics Advisor

Use the hcmds64ssltool command to create a private key and a certificatesigning request (CSR) for Infrastructure Analytics Advisor.

82 Configuring secure communicationsHitachi Infrastructure Analytics Advisor Installation and Configuration Guide

Before you begin• You must have the Administrator permission for the operating system.

• Check with the certificate authority regarding the requirements for thecertificate signing request.

• Make sure that the signature algorithm of the server certificate issupported by the version of the web browser.

• When re-creating a private key, certificate signing request, or self-signedcertificate, send the output to a new location. (If a file of the same nameexists in the output location, the file cannot be re-created.)

Procedure

Run the hcmds64ssltool command to create private keys, certificatesigning requests, and self-signed certificates that support RSAcryptography and elliptic curve cryptography (ECC).

The certificate signing request is created in PEM format.

Tip: Use a self-signed certificate only to test encryptedcommunications.

Related topics

• hcmds64ssltool on page 147

Applying for a server certificate for Infrastructure Analytics Advisorfrom the certificate authority

In general, applications for server certificates are submitted online. Create acertificate signing request (CSR) for Infrastructure Analytics Advisor, andsend it to the certificate authority to obtain a digital signature.

Before you begin

Create a certificate signing request for Infrastructure Analytics Advisor.

You must have a server certificate that was issued in X.509 PEM format bythe certificate authority. For details on how to apply, see the website of thecertificate authority you use. In addition, make sure the certificate authoritysupports the signature algorithm.

Procedure

1. Send the created certificate signing request to the certificate authority.2. Save the response from the certificate authority.


Note: Certificates have expiration dates. Use thehcmds64checkcerts command to verify the expiration date.

Related topics

• Checking the expiration date of the certificate for Infrastructure AnalyticsAdvisor on page 87

Enabling SSL communication for the Infrastructure Analytics Advisormanagement server

To enable SSL communication, edit the user_httpsd.conf file.

Before you begin• Create a private key for the Infrastructure Analytics Advisor management

server.

• Prepare the Infrastructure Analytics Advisor management server certificatefile from the certificate authority.We recommend that you copy the file to the following location:Infrastructure-Analytics-Advisor-installation-folder\Base64\uCPSB\httpsd\conf\ssl\server

• Verify the host name specified for Common Name in the certificate signingrequest.

Procedure

1. Stop the Infrastructure Analytics Advisor services.2. Edit the user_httpsd.conf file.

Infrastructure-Analytics-Advisor-installation-folder\Base64\uCPSB\httpsd\conf\user_httpsd.conf

Example of the user_httpsd.conf file (default)


Settings required for enabling SSL communication:


• Remove the hash mark (#) as shown in the following example:

When using RSA cryptography only, you do not need to remove thehash mark (#) for the SSLECCCertificateKeyFile and theSSLECCCertificateFile settings.

• For the ServerName directive in the first line and the ServerNamedirective inside the <VirtualHost> tags, enter the host name that youspecified for Common Name in the certificate signing request. (Hostnames are case sensitive.)

• For the Infrastructure Analytics Advisor server certificate file, youmust have a certificate signed by a certificate authority and a self-signed certificate.

• Specify an absolute path to the key and certificate files:For RSA cryptography only:○ SSLCertificateFile○ SSLCertificateKeyFile

For elliptic curve cryptography:• SSLECCCertificateFile• SSLECCCertificateKeyFile

Note: You do not need to specify these settings if you aregoing to use RSA cryptography only.


For SSLCertificateKeyFile and SSLECCCertificateKeyFile, do notspecify a symbolic link and junction for the path.For SSLECCCertificateKeyFile, use a PEM-format private key file inPKCS#8 format.

• If the server certificate for Infrastructure Analytics Advisor originatedfrom 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 bythe intermediate certificate authorities. You can include multiplecertificates in a single file by using a text editor to chain thosecertificates 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 orcomment out the line Listen 22015.To interrupt non-SSL communication from a source outside ofthe network to the management server, add a hash mark (#) tothe beginning of the line Listen 22015 to comment it out, thenremove the hash mark from the beginning of the line #Listen127.0.0.1:22015.To close the port for non-SSL communication by theInfrastructure Analytics Advisor management server, close thisport for the HBase 64 Storage Mgmt Web Service.

3. Start the Infrastructure Analytics Advisor services.

Related topics

• Creating a private key and a certificate signing request for InfrastructureAnalytics Advisor on page 82

• Starting the Infrastructure Analytics Advisor services on page 104• Stopping the Infrastructure Analytics Advisor services on page 104

Checking the expiration date of the certificate for InfrastructureAnalytics Advisor

Use the hcmds64checkcerts command to check the expiration date of theInfrastructure Analytics Advisor server certificate and the certificate issued bya certificate authority.


Before you begin• In the user_httpsd.conf file, specify the path of the following certificates:

○ Server certificate for Infrastructure Analytics AdvisorWhen the certificate for both the RSA cryptography and the ellipticcurve cryptography is used, the path of both certificates must bespecified.

○ All certificates issued by intermediate certificate authorities

• You must have Admin permission for the operating system to do thisprocedure.

Procedure

Run the following command:

Infrastructure-Analytics-Advisor-Installation-destination-folder\Base64\bin\hcmds64checkcerts { [/days number-of-days][/log] | /all }

The options are:

daysSpecify the period (in days). The range of days is 30 to 3,652 (10years). This options displays expired certificates and those due toexpire during the specified period. (When you omit this option, thecommand displays certificates due to expire in 30 days.)

logSpecify this option if you want to regularly check the expirationdates of certificates as an operating system task. When certificatesare displayed, a warning message is output to the event log.

allSpecify the expiration date to display for all certificates listed in theuser_httpsd.conf file.

Configuring SSL servers (Data Center Analyticsmanagement and Analytics probe servers)

Use this section to configure SSL communication between the Data CenterAnalytics management and Analytics probe servers.

Applying self-signed certificates to the Data Center Analyticsmanagement server

Self-signed certificates are automatically created when the Data CenterAnalytics management server is installed. To re-create self-signedcertificates, 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 on which the Data

Center Analytics management server is installed, and the certificate isassociated 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 management server was installed• If you want to use server certificates that have been signed by a certificate

authorityIn the previous case, see the description of server certificates that havebeen signed by a certificate authority.

Procedure

1. Perform the following steps to stop the Data Center Analytics services:a. Run the following command:

crontab -eb. At the beginning of each line in the ordinary execution schedule that

was output for the Data Center Analytics management server, add ahash 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:/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:

[root@localhost ~]# /usr/local/megha/bin/megha-jetty.shstatusMegha 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 newkeystore:


keytool -keystore /usr/local/megha/jetty/etc/keystore -aliasalias-name -genkey -keyalg RSA• The default password is megha.jeos.

• For the alias-name, specify a name to identify which host server hasthe self-signed certificate.

4. Perform the following steps to start the Data Center Analytics services:a. Run the following command:

crontab -eb. Delete the hash marks (#) from the beginning of each line in the

ordinary execution schedule that generates output for the Data CenterAnalytics management server:*/5 * * * * F=/usr/local/megha/cron.5min; test -f $F && bash $F13 0 * * * F=/usr/local/megha/cron.1hr; test -f $F && bash $F11 * * * * 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 Analyticsservices are running:


Output example:

[root@localhost jetty]# /usr/local/megha/bin/megha-jetty.shstatusMegha server is running

Related topics

• Importing a certificate to the truststore file for the Infrastructure AnalyticsAdvisor management server on page 91

• Applying server certificates to the Data Center Analytics managementserver and the Analytics probe server on page 92

Exporting a self-signed certificate for the Data Center Analyticsmanagement server

This section provides information about exporting a self-signed certificate forthe Data Center Analytics management server.

Procedure

Run the following command to export the certificate for the Data CenterAnalytics management 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-signedcertificate, specify jetty.

• For certificate-file-name, specify the absolute path to the exportdestination of the self-signed certificate.

Importing a certificate to the truststore file for the InfrastructureAnalytics Advisor management server

To enable verification of the server certificate for the Data Center Analyticsmanagement server on the Infrastructure Analytics Advisor managementserver, import the certificate as described in this section.

Before you begin

You must have Admin permission for the Infrastructure Analytics Advisormanagement server.

Procedure

1. Run the following command to import the certificates for the Data CenterAnalytics management server to the truststore file:Infrastructure-Analytics-Advisor-installation-folder\Base64\bin\hcmds64keytool –import –alias alias-name –filecertificate-file-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.• The truststore file is stored in the following location:

Infrastructure-Analytics-Advisor-installation-folder\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: Infrastructure-Analytics-Advisor-

installation-folder\Analytics\conf• Key: cert.verify.enabled• Value: true

3. Start Infrastructure Analytics Advisor services.

Related topics

• Applying self-signed certificates to the Data Center Analytics managementserver on page 88


• Applying server certificates to the Data Center Analytics managementserver and the Analytics probe server on page 92

• Starting the Infrastructure Analytics Advisor services on page 104• User-specified properties file (config_user.properties) on page 159

Applying server certificates to the Data Center Analyticsmanagement server and the Analytics probe server

To apply server certificates to the Data Center Analytics management serverand 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 management server and the Analytics probe server.

• You can use any certificate in CRT format that has been signed by acertificate authority.

Procedure

1. Follow these steps by using a keystore where the user certificates inPKCS12 format are stored:a. Copy the server certificate created by the user to the Data Center

Analytics management server.b. Log on as a root user to the Data Center Analytics management server

by using an SSH client.

Note: A root user cannot log on from the VMware vCenter VMconsole.

c. Go to the directory of the server certificate the Data Center Analyticsmanagement server.

d. If the file for the server certificate request is not the same as the filecontaining the private key, combine those files into one file in PKCS12format.

The following example shows how to combine multiple files into onejetty.pkcs12 file, assuming that jetty.crt is a server certificatethat has been signed by a certificate authority and that jetty.key isthe private key.

openssl pkcs12 -inkey jetty.key -in jetty.crt -export -outjetty.pkcs12

Note: When the file is output, password confirmation isrequired. Do not specify an empty password. Make sure youwrite down the password because you need it when applyingthe server certificate to the Analytics probe server.


e. If the created server certificate is an intermediate certificate in a chainof certificates, create a file in PKCS12 format:

The following example shows how to specify a command for combiningchained certificates into cert-chain.txt. Specify server certificates inorder, starting from servers to the root CA.

cat jetty.crt intermediate.crt [intermediate2.crt]...rootCA.crt > cert-chain.txtopenssl pkcs12 -export -inkey jetty.key -in cert-chain.txt-out jetty.pkcs12

Note: When the file is output, password confirmation isrequired. Do not specify an empty password. Make sure youwrite down the password, because you need it when you applythe server certificate to the Analytics probe server.

f. Use the following command to import a file in PKCS12 format andcreate a keystore file:keytool -importkeystore -srckeystore jetty.pkcs12 -srcstoretype PKCS12 -destkeystore keystore

A keystore file is created in the current directory. Make sure youremember the location of the created keystore file.

2. Perform the following steps to stop the crond service of the Data CenterAnalytics management server:a. Run the following command:

crontab -eb. At the beginning of each line in the ordinary execution schedule that

was output for the Data Center Analytics management server, add ahash 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 Analyticsmanagement services:

/usr/local/megha/bin/megha-jetty.sh stop4. Use the following command to verify that the Data Center Analytics

management services have stopped:


Output example:


[root@localhost ~]# /usr/local/megha/bin/megha-jetty.shstatusMegha 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 management server.

Enter the password that you specified in step 1 for PASSWORD (threelocations) 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> <Setname="TrustStorePath"><Property name="jetty.base"default="." />/<Property name="jetty.truststore"default="etc/keystore"/></Set> <Setname="TrustStorePassword"> PASSWORD </Set>

7. Start the Data Center Analytics management services:

/usr/local/megha/bin/megha-jetty.sh start8. Use the following command to verify that the service status of the Data

Center Analytics management server is Running:


Output example:

[root@localhost jetty]# /usr/local/megha/bin/megha-jetty.shstatusMegha server is running

9. Do the following steps to start the crond service of the Data CenterAnalytics management server:a. Run the following command:

crontab -eb. Delete the hash marks (#) as follows from the beginning of each line

in the ordinary execution schedule that was output for the Data CenterAnalytics management server:*/5 * * * * F=/usr/local/megha/cron.5min; test -f $F && bash $F13 0 * * * F=/usr/local/megha/cron.1hr; test -f $F && bash $F11 * * * * 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)


10. Do steps 1 to 9 on the Analytics probe server.

Related topics

• Checking the expiration dates of certificates for Data Center Analytics andAnalytics probe servers on page 95

Checking the expiration dates of certificates for Data CenterAnalytics and Analytics probe servers

Check the expiration dates of the server certificates and Certificate Authoritycertificates for Data Center Analytics server and Analytics probe server.

Before you begin

You must have the root permission of the operating system.

Procedure

Run the following command on the Data Center Analytics managementserver 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 AnalyticsAdvisor management server and a web client

To change the port number for SSL communication, change the port numbersspecified in the definition files. Then, set the Windows-based firewallexceptions by using the hcmds64fwcancel command.

Before you begin

You must have the Admin permission of the operating system.

Procedure

1. Stop the Infrastructure Analytics Advisor services by running thehcmds64srv command with the /stop option.

2. Change the port numbers in the following definition files:• Infrastructure-Analytics-Advisor-Installation-destination-

folder\Base64\uCPSB\httpsd\conf\user_httpsd.confChange the following three lines:Listen 22016Listen [::]:22016<VirtualHost *:22016>

• installation-folder-of-Infrastructure-Analytics-Advisor\Analytics\conf\command_user.properties


Change the following line:command.https.port = 22016

3. Change the shortcut to the program as follows:

The default URL is: http://localhost:22015/Analytics/

For Windows Server 2008 R21. From the Start menu, click All Programs > Hitachi

Infrastructure Analytics Advisor > InfrastructureAnalytics Advisor > HIAA Login to display the properties.

2. Change the port number of the URL specified in Target.

For Windows Server 20121. 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 HitachiInfrastructure Analytics Advisor folder.

4. In the Web Document tab, change the port number of the URLspecified in URL.

4. Run the hcmds64fwcancel command to set Windows-based firewallexceptions.

5. Run the hcmds64srv command with the /start option.

Related topics

• Starting the Infrastructure Analytics Advisor services on page 104• Stopping the Infrastructure Analytics Advisor services on page 104• hcmds64fwcancel on page 137


7Changing Infrastructure Analytics

Advisor management server systemsettings

This chapter contains the procedures to change the Infrastructure AnalyticsAdvisor management server settings.

□ Changing the system information

□ Starting and stopping the Infrastructure Analytics Advisor service

□ Backing up and restoring Infrastructure Analytics Advisor

□ Enabling system account locking

Changing Infrastructure Analytics Advisor management server system settings 97Hitachi Infrastructure Analytics Advisor Installation and Configuration Guide

Changing the system informationThis section contains the procedures to change system information about theInfrastructure Analytics Advisor management server.

Changing the installation folder of Infrastructure Analytics AdvisorChanging the installation folder requires backup of existing data, uninstallingand reinstalling Infrastructure Analytics Advisor, and restoring data.

Procedure

1. Run the backupsystem command to back up the Infrastructure AnalyticsAdvisor system.

2. Uninstall Infrastructure Analytics Advisor.3. Reinstall Infrastructure Analytics Advisor.4. Run the restoresystem command to restore the Infrastructure Analytics

Advisor system.

Related topics

• backupsystem on page 134• Installing Infrastructure Analytics Advisor on page 51• restoresystem on page 153

Changing the Infrastructure Analytics Advisor management serverhost name

Use the hcmds64srv command to change the host name of the InfrastructureAnalytics Advisor management server.

Before you begin

Make sure you have Administrator permission for Windows-based OS.

Procedure

1. Run the hcmds64srv command with the /stop option to stop theInfrastructure Analytics Advisor service.

2. Change the host name of the Infrastructure Analytics Advisormanagement server.

3. Change the host name specified in ServerName in the user_httpsd.conffile.

Infrastructure-Analytics-Advisor-installation-folder\Base64\uCPSB\httpsd\conf\user_httpsd.conf

4. Restart the Infrastructure Analytics Advisor management server.5. Run the hcmds64srv command with the /start option to start the

Infrastructure Analytics Advisor services.

98 Changing Infrastructure Analytics Advisor management server system settingsHitachi Infrastructure Analytics Advisor Installation and Configuration Guide

Related topics


Changing the Infrastructure Analytics Advisor management serverIP address

Stop Infrastructure Analytics Advisor services by using the hcmds64srvcommand to change the IP address of the Infrastructure Analytics Advisormanagement server.

Before you begin


Procedure

1. Run the hcmds64srv command with the /stop option to stopInfrastructure Analytics Advisor services.

2. Change the IP address of the Infrastructure Analytics Advisormanagement server.

3. Run the hcmds64srv command with the /start option to start theInfrastructure Analytics Advisor services.

Related topics


Changing the port number used between Infrastructure AnalyticsAdvisor and the web browser

To change the port number used between Infrastructure Analytics Advisorand the web browser, change the port number in each definition file. Then,run the hcmds64fwcancel command to register Windows-based firewallexceptions.

Before you begin

Make sure you have Administrator permission for Windows-based operatingsystem.

Procedure

1. Run the hcmds64srv command with the /stop option to stopInfrastructure Analytics Advisor services.

2. Edit the definition files.

The port number settings to be edited depend on the communicationmethod between Infrastructure Analytics Advisor and the web browser,as follows:


When using HTTP:• Infrastructure-Analtyics-Advisor-installation-

destination-folder\Base64\uCPSB\httpsd\conf\user_httpsd.confChange the port number in the following three lines:Listen 22015Listen [::]:22015#Listen 127.0.0.1:22015

• Infrastructure-Analtyics-Advisor-installation-destination-folder\Analytics\conf\command_user.propertiesChange the port number in the following line:command.http.port = 22015

When using HTTPS:• Infrastructure-Analtyics-Advisor-installation-

destination-folder\Base64\uCPSB\httpsd\conf\user_httpsd.confChange the port number in the following three lines:Listen 22016Listen [::]:22016<VirtualHost *:22016>

• Infrastructure-Analtyics-Advisor-installation-destination-folder\Analytics\conf\command_user.propertiesChange the port number in the following line:command.https.port = 22016

3. Edit the program shortcut as follows.

Note: The default URL is: http://localhost:22015/Analytics/

For Windows Server 2008 R21. From the Start menu, select All Programs > Hitachi

Infrastructure Analytics Advisor > InfrastructureAnalytics Advisor > HIAA Login to display properties.

2. Change the port number of the URL in Target.

For Windows Server 2012


1. 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 HitachiInfrastructure Analytics Advisor folder.

4. Change the port number of the URL specified for URL in theWeb Document tab.

4. Run the hcmds64fwcancel command to register Windows-based firewallexceptions.


Related topics

• Starting the Infrastructure Analytics Advisor services on page 104• Stopping the Infrastructure Analytics Advisor services on page 104• hcmds64fwcancel on page 137

Changing the port number used between Infrastructure AnalyticsAdvisor and common component

To change the port number used between Infrastructure Analytics Advisorand common component, stop Infrastructure Analytics Advisor services usingthe hcmds64srv command, change the port number in the definition file.

Before you begin


Procedure

1. Run the hcmds64srv command with the /stop option to stop theInfrastructure Analytics Advisor services.

2. Edit the following definition files:• Infrastructure-Analtyics-Advisor-Installation-destination-

folder\Base64\uCPSB\CC\web\redirector\workers.propertiesChange the port number in the following line:worker.AnalyticsWebService.port=27100

• Infrastructure-Analtyics-Advisor-Installation-destination-folder\Base64\uCPSB\CC\web\containers\AnalyticsWebService\usrconf\usrconf.propertiesChange the port number in: webserver.connector.ajp13.port andwebserver.shutdown.port. :webserver.connector.ajp13.port=27100


:webserver.shutdown.port=27101 :


Related topics


Changing the port number between Infrastructure Analytics Advisorand the SMTP server

You can change the port number used between Infrastructure AnalyticsAdvisor and the SMTP server in the Email Server Settings window.

Before you begin

Make sure you have the Admin permission of Infrastructure Analytics Advisor.

Procedure

1. In the Administration tab, select Notification Settings > EmailServer.

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 Advisormanagement server

Stop the Infrastructure Analytics Advisor services using the hcmds64srvcommand, and then change the time settings of the Infrastructure AnalyticsAdvisor management server.

Before you begin


Procedure

1. Run the hcmds64srv command with the /stop option to stopInfrastructure Analytics Advisor service.

2. Change the time setting of the Infrastructure Analytics Advisormanagement server.

If you delayed the time settings of the server, wait until the change takeseffect, and then do step 3.

3. Run the hcmds64srv command with the /start option to start theInfrastructure Analytics Advisor service.


Moving an Infrastructure Analytics Advisor installation to anotherhost

To move the Infrastructure Analytics Advisor system to a host that has adifferent host name or IP address than that of the current host, first changethe host name and IP address of the new host to match those of the currenthost. After doing a restore operation, change the host name and IP addressof the new host back to their original values.

Before you begin• Stop the Infrastructure Analytics Advisor services on the current server.

• Verify that the following items are the same on the source server and thenew server:• System locale

• Environment for Hitachi Command Suite products (configuration,version number, revision number, and restriction code)

• Verify that Infrastructure Analytics Advisor is not installed on thedestination server.

Procedure

1. Back up Infrastructure Analytics Advisor on the current server.2. Change the host name and IP address of the destination host to match

those of the current host.3. Install Infrastructure Analytics Advisor on the destination server.

The migration-destination folder of Infrastructure Analytics Advisor mustbe the same on both the new host and the current host.

4. Restore Infrastructure Analytics Advisor on the new 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 namesand IP addresses.

6. Verify that the new server is running and then start operation.

Result

Infrastructure Analytics Advisor is migrated to the new host.

Related topics

• backupsystem on page 134• restoresystem on page 153• Installing Infrastructure Analytics Advisor on page 51• Changing the Infrastructure Analytics Advisor management server host

name on page 98


• Changing the Infrastructure Analytics Advisor management server IPaddress on page 99

Starting and stopping the Infrastructure Analytics Advisorservice

This section describes how to start and stop the Infrastructure AnalyticsAdvisor services.

Starting the Infrastructure Analytics Advisor servicesTo start the Infrastructure Analytics Advisor services, run the hcmds64srvcommand.

Before you begin

You must have the Administrator permission of the OS to do this operation.

Procedure

Run the hcmds64srv command with the /start option specified.

Note:• Do not use Service Control Manager to start the services.

• To stop or start only the Infrastructure Analytics Advisorservices 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 services starts.

Related topics

• hcmds64srv on page 143• Infrastructure Analytics Advisor services on page 165

Stopping the Infrastructure Analytics Advisor servicesTo stop the services, run the hcmds64srv command.

Before you begin

You must have the Administrator permission of the OS to do this operation.


Procedure

Run the hcmds64srv command with the /stop and /server optionsspecified.

Note:• Do not use Service Control Manager to stop the service. If you

use Service Control Manager to stop the service, the processingmight fail.

• To stop or start only the Infrastructure Analytics Advisorservices when the common component service is running, runthe command with AnalyticsWebService specified for the /server option. To stop the Infrastructure Analytics Advisorservicse during your daily operation, omit this option to stop allservices.

Result

The Infrastructure Analytics Advisor services stops.

Related topics


Starting the Data Center Analytics management server or Analyticsprobe service

Do the following steps to start the Data Center Analytics management serveror analytics probe service.

Before you begin

Log on to the Data Center Analytics management server or Analytics probeserver as the root user.

Procedure

1. Run the cron -e command.2. Delete the hash marks (#) as follows from the beginning of each line in

the regular execution schedule that was output for the Data CenterAnalytics management server or Analytics probe server:*/5 * * * * F=/usr/local/megha/cron.5min; test -f $F && bash $F13 0 * * * F=/usr/local/megha/cron.1hr; test -f $F && bash $F11 * * * * 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 management server or analyticsprobe service

Do the following steps to stop the Data Center Analytics management serveror analytics probe service.

Before you begin

Log on to the Data Center Analytics management server or analytics probeserver as the root user.

Procedure

1. Run the chron -e command.2. Delete the hash marks (#) as follows from the beginning of each line in

the ordinary execution schedule that was output for the Data CenterAnalytics management 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 stop the service:/usr/local/megha/bin/megha-jetty.sh stop

Note: If crontab has not been edited, the Data Center Analyticsmanagement server or analytics probe service might startautomatically. If the Data Center Analytics management server oranalytics probe server service starts, stop it by following thisprocedure.

Backing up and restoring Infrastructure Analytics AdvisorTo back up or restore the entire Infrastructure Analytics Advisor system, youmust perform operations for each server.

The following information is subject to backup or restoration:• Infrastructure Analytics Advisor settings

• Data Center Analytics settings

• Analytics probe 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

• Data Center Analytics

• Analytics probe

• RAID Agent

2. Back up the following data:• Infrastructure Analytics Advisor settings

• Data Center Analyticssettings

• Analytics probe settings

• RAID Agent definition information, settings, and performance data

3. Start the following services:• RAID Agent

• Analytics probe

• Data Center Analytics

• Infrastructure Analytics Advisor

Related topics

• Stopping services before a back up or restore on page 108• Backing up Infrastructure Analytics Advisor settings information on

page 109• Backing up the settings information and database of Data Center Analytics

on page 109• Backing up Analytics probe settings information on page 110• Backing up the entire RAID Agent system on page 111• RAID Agent definition information files to be backed up on page 112• Restoring Infrastructure Analytics Advisor settings information on

page 113• Restoring the settings information and database of Data Center Analytics

on page 114• Restoring Analytics probe settings information on page 115• Restoring the RAID Agent system on page 117


• Updating configuration information files that depend on the environment inwhich the RAID Agent is installed on page 118

• Starting Infrastructure Analytics Advisor services after a back up or restoreoperation on page 119

Stopping services before a back up or restoreStop all Infrastructure Analytics Advisor services before you perform back upor restore tasks.

Before you begin

• You must have the Administrator permission for the InfrastructureAnalytics Advisor management server.

• You must have the root permission for the Data Center Analyticsmanagement server and the Analytics probe server.

Procedure

1. From the Infrastructure Analytics Advisor management server, run thefollowing command to stop the Infrastructure Analytics Advisor service:hcmds64srv /stop

2. From the Data Center Analytics management server, do the followingsteps to stop the Data Center Analytics service.a. Run the following command:

crontab -eb. At the beginning of each line in the regular execution schedule for

Data Center Analytics, add a hash mark (#) to comment out a line asshown 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 management server onthe Analytics probe server to stop the Analytics probe service.

4. From the Analytics probe server, run the following command to stop theRAID Agent service.RAID-Agent-installation-directory/htnm/bin/htmsrv stop -all

Result

All of the services used by Infrastructure Analytics Advisor have beenstopped.


Related topics


Backing up Infrastructure Analytics Advisor settings informationTo back up the settings information of Infrastructure Analytics Advisor, runthe backupsystem command.

Before you begin• You must have the Administrator permission of the OS to do this

operation.

• Before starting this operation, stop all services of the InfrastructureAnalytics Advisor system.

Procedure

Run the backupsystem command to back up the Infrastructure AnalyticsAdvisor settings information.

Result

The system information of Infrastructure Analytics Advisor is output to thespecified directory.

Related topics

• backupsystem on page 134

Backing up the settings information and database of Data CenterAnalytics

To back up the settings information and database of Data Center Analytics,copy the folder containing the settings and database to an external storagedevice 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 hassufficient space.You can estimate the amount of space required by adding the sizes of thefollowing folders that are to be backed up:○ Data-Center-Analytics-installation-folder/megha/conf

○ Data-Center-Analytics-installation-folder/megha/db

○ Data-Center-Analytics-installation-folder/megha/misc


Procedure

Copy the following folders from the Data Center Analytics managementserver to the backup destination:

All files and folders in Data-Center-Analytics-installation-folder/megha/conf

All files and folders in Data-Center-Analytics-installation-folder/megha/db

All files and folders in Data-Center-Analytics-installation-folder/megha/misc

Result

The settings information and database of Data Center Analytics have beenbacked up.

Backing up Analytics probe settings informationTo back up the settings information of Analytics probe, copy the foldercontaining the settings to an external storage device or a new host.


• Make sure that the location where the backup files are to be stored hassufficient space.You can estimate the amount of space required by adding the sizes of thefollowing folders that are to be backed up:○ Data-Center-Analytics-installation-folder/megha/conf



Procedure

Back up the following folders on the Analytics probe server.

All files and folders in Data-Center-Analytics-installation-folder/megha/conf

All files and folders in Data-Center-Analytics-installation-folder/megha/db

All files and folders in Data-Center-Analytics-installation-folder/megha/misc


Result

The settings information of Analytics probe has been backed up.

Backing up the entire RAID Agent systemTo back up the entire RAID Agent system, use the htmhsbackup command toback up the performance data, the configuration information files, and someof the definition information files. Then, copy the remainder of the definitioninformation files.

Before you begin• All services of Infrastructure Analytics Advisor must be stopped.

• Make sure that the directory to which backed-up data is to be output hassufficient free space.

Data to be backed up

Data to be backed up Backup method

Performance data Use the htmhsbackup command

Configuration information files

Definition information filesDefinition 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, theconfiguration information files, and the definition information files whosetype is "Agent".RAID-Agent-installation-directory/htnm/bin/htmhsbackup -dir output-directory-for-the-backed-up-data

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 be backed up on page 112


RAID Agent definition information files to be backed upThe following table lists the RAID Agent definition information files that are tobe backed up.

Type Definition information file name Description

Common (to bebacked upmanually)

/opt/jp1pc/jpchosts Settings file containing RAID Agenthost information

/opt/jp1pc/*.ini Settings file of the RAID Agent

/opt/jp1pc/bin/action/*.ini Settings file of the RAID Agent

/opt/jp1pc/bin/statsvr/*.ini Settings file of the RAID Agent

Template (to bebacked upmanually)

/opt/jp1pc/agtd/agent/jpcagt.ini.instmpl

Internal file

Agent (to bebacked up byusing thehtmhsbackupcommand)

/opt/jp1pc/xxxx/*.ini1 Internal file

/opt/jp1pc/xxxx/agent/*.ini1 Settings file of the RAID Agent

/opt/jp1pc/xxxx/agent/instance-name/*.ini1 and 2

Settings file of the RAID Agent

/opt/jp1pc/xxxx/agent/instance-name/system/*.ini1 and 2

Internal file

/opt/jp1pc/xxxx/store/*.ini1 Settings file of the RAID Agent

/opt/jp1pc/xxxx/store/instance-name/*.ini1 and 2

Settings file of the RAID Agent

/opt/jp1pc/xxxx/agent/instance-name/raidperf_ldevlist.conf1 and 2

Internal file

/opt/jp1pc/htnm/agent/config/alertglobalconfig.ini

Settings file for emails sent by theAlert function

/opt/jp1pc/htnm/agent/config/apidataglobalconfig.ini

Settings file of the REST APIcomponent of the RAID Agent

/opt/jp1pc/htnm/agent/config/dbdataglobalconfig.ini

Settings file of the REST APIcomponent of the RAID Agent

/opt/jp1pc/htnm/agent/system/data_file_manage

Internal control file

/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

Option definition file for Javaapplications

/opt/jp1pc/htnm/HBasePSB/CC/server/usrconf/ejb/AgentRESTWebService/usrconf.properties

User properties file for Javaapplications

/opt/jp1pc/htnm/HBasePSB/CC/web/redirector/mod_jk.conf

Definition file for Redirector actions ofHTTP server


Type Definition information file name Description

/opt/jp1pc/htnm/HBasePSB/CC/web/redirector/workers.properties

Worker definition file

/opt/jp1pc/htnm/Rest/config/htnm_httpsd.conf

Definition file for the HTTP server (tobe edited by the user)

/opt/jp1pc/htnm/Rest/config/user.properties

User settings properties file for theREST API component of the RAIDAgent

/opt/jp1pc/htnm/Rest/system/sysconf/system.properties

System settings file (The settings inthis file are not disclosed.)

Notes:1. xxxx represents the agent identifier "agtd".

2. The number of instance-name directories is the same as the number of instances.

Restoring Infrastructure Analytics Advisor settings informationTo restore the settings information of Infrastructure Analytics Advisor, runthe restoresystem command. After restoration, specify the settings relatedto communication between Infrastructure Analytics Advisor and the webclient on the new host.

Before you begin• You must have the Administrator permission of the OS to do this

operation.

• Before starting this operation, stop all services of the InfrastructureAnalytics Advisor system.

• Run the backupsystem command to create backup data.

• Make sure that the following items are the same between the backup-source host and the restoration-destination host:○ Infrastructure Analytics Advisor-installation-folder

○ Version number, revision number, and restriction code of the installedinstance of Infrastructure Analytics AdvisorYou can check the version number, revision number, and restriction codeof Infrastructure Analytics Advisor in the Version window.

○ Host nameIf you are doing restoration as part of the procedure for changing thehost name of the Infrastructure Analytics Advisor management serveror the procedure for migrating the system to a host of a different hostname, the host names of the backup-source host and restoration-destination host do not need to match.

○ IP address

○ System locale


Procedure

1. Run the restoresystem command to restore the settings information ofInfrastructure Analytics Advisor.

2. Edit the definition files below based on the environment where theinformation is to be restored.

The definition files below are backed up but will not be restored. For thisreason, 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 folders:• backup-folder\HBase\base\conf

• backup-folder\HBase\base\httpsd.conf

3. If HTTPS connections are to be used between Infrastructure AnalyticsAdvisor and the web client on the new host, enable HTTPS connections.

4. If you changed the port number for communication betweenInfrastructure Analytics Advisor and the web client on the new host, re-set the port number in accordance with the procedure for changing portnumbers.

Result

The system information of Infrastructure Analytics Advisor has been restoredto the specified host, and Infrastructure Analytics Advisor can now be used.

Related topics

• restoresystem on page 153• Enabling SSL communication for the Infrastructure Analytics Advisor

management server on page 84• Changing the SSL port number between the Infrastructure Analytics

Advisor management server and a web client on page 95

Restoring the settings information and database of Data CenterAnalytics

To restore the settings information and database of Data Center Analytics,copy the backed-up data to the restoration-destination host, and then changethe owner of the restored data.


• Make sure that the restore has sufficient space.


You can estimate the amount of space by adding the sizes of the followingfolders that were backed up:○ Data-Center-Analytics-installation-folder/megha/conf



• Make sure that the following items are the same between the backup-source host and the restore-destination host:○ Data Center Analytics-installation-folder

○ Version number, revision number, and restriction code of the installedinstance of Data Center Analytics

○ Host name

○ IP address

○ System locale

Procedure

1. Copy the following backed-up data to the new host:

All files and folders in Data-Center-Analytics--installation-folder/megha/conf

All files and folders in Data-Center-Analytics--installation-folder/megha/db

All files and folders in Data-Center-Analytics--installation-folder/megha/misc

2. Run the following command on the restore-destination host to changethe owner of the data.

chown -R megha:megha /megha/

Result

The settings information and database of Data Center Analytics have beenrestored to the new host.

Restoring Analytics probe settings informationTo restore the settings information of Analytics probe, copy the backed-updata to the restoration-destination host, and then change the owner of therestored 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 thefollowing folders that were backed up:○ Analytics probe-installation-folder/usr/local/megha/conf

○ Analytics probe-installation-folder/usr/local/megha/db

○ Analytics probe-installation-folder/usr/local/megha/misc

• Make sure that the following items are the same between the backup-source host and the restoration-destination host:○ Analytics probe-installation-folder

○ Version number, revision number, and restriction code of the installedinstance of Analytics probe

○ Host name

○ IP address

○ System locale

Procedure

1. Copy the following backed-up data to the new host:

All files and folders in Analytics probe-installation-folder/usr/local/megha/conf

All files and folders in Analytics probe-installation-folder/usr/local/megha/db

All files and folders in Analytics probe-installation-folder/usr/local/megha/misc

2. Run the following command on the restoration-destination host tochange the owner of the data.

chown -R megha:megha /megha/

Result

The settings information of Analytics probe has been restored to the newhost.


Restoring the RAID Agent systemTo restore the entire RAID Agent system, use the htmhsrestore command torestore each type of data, and then manually restore the definitioninformation 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 restoration-destination host.

• The version number and revision number of the RAID Agent on therestoration-destination host must be the same as those of the RAID Agentused 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 nameon the restoration-destination host.

• Setup of the instance on the restoration-destination host must becomplete.

• The OS of the restoration destination must be the same as that of thebackup source.

Data to be restored

Data to be restored Restoration method

Performance data Restore by using the htmhsrestore command.

Configuration information filesConfiguration information files that do not dependon the installation environment

Restore by using the htmhsrestore command.

Configuration information files that depend on theinstallation environment

These files are not restored.

Definition information filesDefinition 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 hasstopped.RAID-Agent-installation-directory/htnm/bin/htmsrv status -allIf the service is running, run the following command to stop the RAIDAgent service.RAID-Agent-installation-directory/htnm/bin/htmsrv stop -all

2. Run the following command to restore the backed-up performance dataand configuration information files.RAID-Agent-installation-directory/htnm/bin/htmhsrestore –dir storage-directory-of-the-backed-up-data

3. Run the jpctdchkinst command to check whether the restored instanceis 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 thenrun 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 installationenvironment.

7. To use the Alert function, synchronize the alert definition information.

Result

The entire RAID Agent system has been restored.

Related topics

• Updating configuration information files that depend on the environment inwhich the RAID Agent is installed on page 118

• RAID Agent definition information files to be backed up on page 112

Updating configuration information files that depend on theenvironment in which the RAID Agent is installed

Of the RAID Agent configuration information files, the files containinginformation that depends on the installation environment are not restored bythe htmhsrestore command. If necessary, update the configurationinformation files in the restoration destination.

The following table describes configuration information files that must beupdated.


Configuration information files thatmust be updated

Description

RAID-Agent-installation-directory/htnm/Rest/config/htnm_httpsd.conf

Update the following items as needed.• Port number

• SSL communication settings

RAID-Agent-installation-directory/htnm/HBasePSB/CC/web/redirector/workers.properties

If you changed the port numbers described inworkers.properties and usrconf.properties in thebackup-source environment, also change them in therestoration-destination environment.RAID-Agent-installation-

directory/htnm/HBasePSB/CC/server/usrconf/ejb/AgentRESTService/usrconf.properties

Starting Infrastructure Analytics Advisor services after a back up orrestore operation

After backing up or restoring the entire Infrastructure Analytics Advisorsystem, start all of the services used by Infrastructure Analytics Advisor.

Before you begin• You must have the Administrator permission for the Infrastructure

Analytics Advisor management server to do this operation.

• You must have the root permission for the Data Center Analyticsmanagement server and the Analytics probe to do this operation.

Procedure

1. From the Analytics probe server, run the following command to start theRAID Agent service.RAID-Agent-installation-directory/htnm/bin/htmsrv start -all

2. Check htmRestDbEngineMessage#.log of the RAID Agent to make surethat the KATR13248-E message is not logged before KATR13244-I wasoutput.

After the RAID Agent service is started, it might take up to an hourbefore KATR13244-I is output.

3. From the Analytics probe server, do the following steps to start theAnalytics probe service.a. Run the following command:

crontab -eb. From the beginning of each line in the ordinary execution schedule

that was output for Analytics probe, delete the hash mark (# ) asfollows:*/5 * * * * F=/usr/local/megha/cron.5min; test -f $F && bash $F13 0 * * * F=/usr/local/megha/cron.1hr; test -f $F


&& bash $F11 * * * * 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 CenterAnalytics management server to start the Data Center Analytics service.

5. From the Infrastructure Analytics Advisor management server, run thefollowing command to start the Infrastructure Analytics Advisor service.hcmds64srv /start

Result

All of the services used by Infrastructure Analytics Advisor are running.

Related topics


Enabling system account lockingIn Infrastructure Analytics Advisor, you can configure on a web client basicuser-related settings, such as those related to user registration andpasswords. This section describes the optional settings that cannot beconfigured on a web client.

When Infrastructure Analytics Advisor is initially installed, the locking of thesystem account is disabled. For security purposes, you may want to lock thesystem account.

Note: Locking or unlocking an account requires user managementpermissions. You cannot unlock your own account on a web client, but youcan unlock your own account on the Infrastructure Analytics Advisormanagement server.

Procedure

1. Stop the Infrastructure Analytics Advisor services.2. Create a user.conf file in the following location:

Infrastructure-Analytics-Advisor-Installation-destination-folder\Base64\conf\

3. Add the following property account.lock.system=[true | false], andset the value to true to enable system account locking, then save thefile.If you do not want to lock the system account, specify false.

4. Start the Infrastructure Analytics Advisor services.


Related topics

• Stopping the Infrastructure Analytics Advisor services on page 104• Starting the Infrastructure Analytics Advisor services on page 104



8Removing Infrastructure Analytics

Advisor componentsThis chapter describe how to remove Infrastructure Analytics Advisorcomponents.

□ Removing Infrastructure Analytics Advisor management server

□ Removing Data Center Analytics management server

□ Removing Analytics probe server

Removing Infrastructure Analytics Advisor components 123Hitachi Infrastructure Analytics Advisor Installation and Configuration Guide

Removing Infrastructure Analytics Advisor managementserver

Use this procedure to remove Infrastructure Analytics Advisor.

Procedure

1. Log on to the Infrastructure Analytics Advisor management server withthe administrator permissions.

2. Stop the security monitoring software, antivirus software, and processmonitoring software.

3. Stop the services of products that use Common Component. To identifythese services, see the Infrastructure Analytics Advisor Servicesappendix.If the Common Component services are running, a dialog box promptingyou to stop these services appears.

4. Set Startup type for the Infrastructure Analytics Advisor managementserver services to Automatic or Manual.In Windows environment, if the Startup type is set to Disabled, theremoval process might fail because the services cannot be started.

5. To remove Infrastructure Analytics Advisor management server, go toControl Panel > Programs > Programs and Features and selectHitachi Infrastructure Analytics Advisor, and then click Uninstall.The settings files remain in the installation folder. You must delete thesettings files manually as necessary.

Removing Data Center Analytics management serverUse this procedure to remove the Data Center Analytics management server.

Procedure

1. Log on to the Data Center Analytics management server.2. Stop the security monitoring software, antivirus software, and process

monitoring software.If these software programs are running, the removal process might fail.

3. Run the following command:sh ./dcaserver_uninstall.sh SYS

Removing Analytics probe serverUse this procedure for removing Analytics probe server.

124 Removing Infrastructure Analytics Advisor componentsHitachi Infrastructure Analytics Advisor Installation and Configuration Guide

Procedure

1. Log on using an OS user account with root user permissions.2. Stop the security monitoring software, antivirus software, and process

monitoring software.

If these software programs are running, the removal process might fail.3. Run the following command:

sh ./dcaprobe_uninstall.sh SYS

Removing Infrastructure Analytics Advisor components 125Hitachi Infrastructure Analytics Advisor Installation and Configuration Guide

126 Removing Infrastructure Analytics Advisor componentsHitachi Infrastructure Analytics Advisor Installation and Configuration Guide

9Troubleshooting

This chapter describes how to troubleshoot common Infrastructure AnalyticsAdvisor problems.

□ Connection to the Infrastructure Analytics Advisor web client unsuccessful

□ Logging on to Infrastructure Analytics Advisor unsuccessful

□ Starting Infrastructure Analytics Advisor does not work

□ When Infrastructure Analytics Advisor cannot be connected to DataCenter Analytics

Troubleshooting 127Hitachi Infrastructure Analytics Advisor Installation and Configuration Guide

Connection to the Infrastructure Analytics Advisor webclient unsuccessful

If you cannot connect to the Infrastructure Analytics Advisor web client checkthe operation status of Infrastructure Analytics Advisor and the port numbersetting.

Procedure

1. Run the hcmds64srv command with the /status option to check theoperation status of Infrastructure Analytics Advisor.

If the services "HAnalytics Engine Web Service" and "HBase 64 StorageMgmt SSO Service" are running, and the service "HBase 64 StorageMgmt 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 numbersused by the Infrastructure Analytics Advisor management server:

Item Contents

Level Error

Source HitachiWebServer

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 theInfrastructure Analytics Advisor management server is normal.

4. Confirm that the web browser is supported by Infrastructure AnalyticsAdvisor.

For details about the types of web browsers supported by InfrastructureAnalytics Advisor, see the Release Notes of Infrastructure AnalyticsAdvisor.

Related topics

• hcmds64srv on page 143

Logging on to Infrastructure Analytics Advisor unsuccessfulWhen you cannot log on to Infrastructure Analytics Advisor, check your userinformation:1. Confirm that the user ID and password are correct.

128 TroubleshootingHitachi Infrastructure Analytics Advisor Installation and Configuration Guide

2. Confirm that the user is registered in Infrastructure Analytics Advisor.

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 does not workIf Infrastructure Analytics Advisor cannot start, check that the resources ofthe Infrastructure Analytics Advisor management server are sufficient, andthe hardware and OS are supported by Infrastructure Analytics Advisor.

Procedure

1. Confirm that resources such as memory and disk space are sufficient onthe Infrastructure Analytics Advisor management server.

2. Confirm that Infrastructure Analytics Advisor has been installed on theOS and hardware supported by Infrastructure Analytics Advisor.

For details about the types of hardware and OSs supported byInfrastructure Analytics Advisor, see the Release Notes of InfrastructureAnalytics Advisor.

3. Run the hcmds64srv command with the /status option to check theoperation status of Infrastructure Analytics Advisor.

4. If the Infrastructure Analytics Advisor service is not running, start theservice.

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 theadministrator or Hitachi customer support.

Related topics

• hcmds64srv on page 143• hcmds64getlogs on page 138

When Infrastructure Analytics Advisor cannot be connectedto Data Center Analytics

If Infrastructure Analytics Advisor cannot be connected to Data CenterAnalytics, check the operating status of Data Center Analytics and the statusof the connection between Infrastructure Analytics Advisor and Data CenterAnalytics.

Troubleshooting 129Hitachi Infrastructure Analytics Advisor Installation and Configuration Guide

Procedure

1. Run the following command on the Data Center Analytics managementserver to verify that the status of the service of the Data Center Analyticsmanagement server is "Running":/usr/local/megha/bin/megha-jetty.sh status

Output example:[root@localhost jetty]# /usr/local/megha/bin/megha-jetty.sh statusMegha server is running

2. In the Administration tab of Infrastructure Analytics Advisor, selectSystem Settings > HDCA Server.

3. Click Edit Settings to check information about the Data Center Analyticsmanagement server.

4. Click Check Connection to check whether Infrastructure AnalyticsAdvisor can be properly connected to the Data Center Analyticsmanagement server.

5. Click OK.

Related topics

• Setting up a connection with Data Center Analytics management server onpage 52

130 TroubleshootingHitachi Infrastructure Analytics Advisor Installation and Configuration Guide

AInfrastructure Analytics Advisor CLI

commandsThis appendix describes the commands of Infrastructure Analytics Advisor.

□ 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 131Hitachi Infrastructure Analytics Advisor Installation and Configuration Guide

List of CommandsThis section lists the Infrastructure Analytics Advisor commands:

Command Description

backupsystem Backs up Infrastructure Analytics Advisor setting information in thefolder you specify.

encryptpassword Creates a password file to be specified as an argument of commandsin Infrastructure Analytics Advisor.

hcmds64fwcancel Registers an exception so that communication between theInfrastructure Analytics Advisor management server and the webbrowser is not blocked by the Windows-based firewall.

hcmds64getlogs Collects log files that are output during operation of InfrastructureAnalytics Advisor, and then outputs the log files to an archive file.

hcmds64intg Deletes authentication data registered in the repository of the serverthat manages user accounts. The command also displays the addressof the server in which the authentication data is registered.

If you fail to delete authentication data when uninstallingInfrastructure Analytics Advisor, use this command to delete theauthentication data.

hcmds64srv Starts or stops Infrastructure Analytics Advisor services anddatabases. The command also displays the status of InfrastructureAnalytics Advisor services.

hcmds64ssltool Creates private keys, CSRs, and self-signed certificates (including itscontent files), which are required for SSL connection.

hcmds64unlockaccount Unlocks a user account. Use this command when you cannot log onto Infrastructure Analytics Advisor because all the user accounts arelocked.

reloadtemplate Reload the Infrastructure Analytics Advisor template files during thestartup of Infrastructure Analytics Advisor.

restoresystem Restores the backup for Infrastructure Analytics Advisor settings ordatabase information that you collected by running thebackupsystem command.

Command usage notesThe following describes the notes that you need to consider when usingcommands.

• If the command is to be run in an environment where User AccountControl (UAC) of Windows-based system is valid requires the Administratorpermission, run the command from the administrator console ofInfrastructure Analytics Advisor.To display the administrator console:

For Windows Server 2008 R2

132 Infrastructure Analytics Advisor CLI commandsHitachi Infrastructure Analytics Advisor Installation and Configuration Guide

1. In the Start menu, select All Programs, Hitachi InfrastructureAnalytics Advisor, and then Analytics Command.

For Windows Server 20121. 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, selectAnalytics Command.

• If you enable Quick Edit Mode in the command prompt, and then click themouse in the window, the window output is stopped until the quick editmode is canceled. Therefore, we recommend that you do not use the quickedit mode.

• To interrupt command running, press Ctrl+C at the same time. If youinterrupt command running, make sure that you read the message issuedat the interruption of the command to check for any problems. Ifnecessary, rerun the command. If you interrupt running command, thereturn value might become undefined.

Usable characters for command argumentsYou can specify the following characters for command arguments:

• The specification method for command arguments must comply with thespecifications of the OS command prompt. Therefore, if an argument valuecontains a space ( ) or special symbols, you must escape such charactersby enclosing each of the characters with double quotation marks (").

• You can use the following types of characters when specifying a path withan argument of a command:Alphanumeric characters, underscores (_), periods (.), hyphens (-), spaces( ), left parentheses ( ( ), right parentheses ( ) ), hash marks (#), atmarks (@), colons (:), and backslash (\)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 UNCformat.

• When specifying a path in an argument, you cannot use a path that has afolder name that begins or ends with a space. Also, you cannot specify afolder name that consists of only spaces.


• When specifying a path in an argument, you cannot use a path that has afolder name that begins or ends with a period (.). Also, you cannot specifya folder name that consists of only periods.

• Unless otherwise stated, the path length is from 1 to 230 characters in theabsolute 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.

backupsystemUse this command to back up Infrastructure Analytics Advisor settinginformation in the folder you specified.

Formatbackupsystem /dir output-directory /type {all | Analytics} [/auto]

Options

/dir output-directorySpecify the folder in which the backup file is stored with the absolute orrelative path.

/type {all | Analytics}Specify the type of information for backup.

allBacks up Infrastructure Analytics Advisor and common component.Common component manages the user information.

AnalyticsBacks up only Infrastructure Analytics Advisor.

/autoAutomatically stops or starts services and databases of InfrastructureAnalytics Advisor and products that use common component. If you omitthis option, these services and databases are not automatically stoppedor started.

Storage location

Infrastructure Analytics Advisor-installation-destination-folder\Analytics\bin


Permissions

Administrator permission

Notes• Make sure that the folder in which the backup file is to be stored has

sufficient free space. Use the following formula to calculate the requiredamount of free space:Size of folders and files in Infrastructure Analytics Advisor-installation-destination-folder\Analytics\data + 5 GBIf products that use common component are installed on the InfrastructureAnalytics Advisor management server, add the capacity required to backup information for those products.

• 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.conffile and the user_httpsd.conf file.

• If all of the following conditions are met, use the hcmds64srv command tostop 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 InfrastructureAnalytics Advisor management server, run the restoresystem commandby specifying /type Analytics to restore only Infrastructure AnalyticsAdvisor. You can back up the data required for restoring onlyInfrastructure Analytics Advisor by specifying /type Analytics for thebackupsystem 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 folder 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.

Example

The following example shows the use of this command to back up informationof Infrastructure Analytics Advisor:backupsystem /dir "C:\Users\Backup" /type Analytics /auto

encryptpasswordUse this command to generate a password file to be specified as theargument of a command in Infrastructure Analytics Advisor. To generate apassword file, the user must be registered in Infrastructure Analytics Advisor.

Formatencryptpassword /user user-ID /password password /passwordfile password-file-path

Options

/user user-IDSpecify the user ID of the Infrastructure Analytics Advisor user for whomyou want to create a password file.

/password passwordSpecify the password of the user specified in the /user option.

/passwordfile password-file-pathUse an absolute or relative path to specify a path of the password file tobe created.

Storage location



Permissions


Return values






4 An exclusion error occurred.

5 Communication failed.

6 Authentication failed. (The specified value is invalid.)


8 The output destination path exists.




200 The password file could not be generated.


hcmds64fwcancelUse this command to register an exception so that communication betweenthe Infrastructure Analytics Advisor management server and the web browseris not blocked by the Windows-based firewall.

Formathcmds64fwcancel

Storage location

Infrastructure Analytics Advisor-installation-destination-folder/Base64/bin

Permissions


Return values

This command has no return value. To determine whether the processing rannormally, check whether HBase (Web) is correctly registered in the inboundrules of the Windows-based firewall.


You can check the inbound rules for Windows Firewall in the Windows-based system control panel.

hcmds64getlogsUse this command to collect log files that are output during operation ofInfrastructure Analytics Advisor, and then output the log files to an archivefile.

Formathcmds64getlogs /dir output-folder-path [/types Analytics] [/arc archive-file-name] [/logtypes {log | db | csv}]

Options

/dir output-folder-pathSpecify the folder path for outputting the archive file. You can specifyonly a folder of a local disk.

As the output folder path, specify an empty folder in absolute or relativepath format. If the folder path does not exist, the folder is createdautomatically. The maximum allowable path length is 100 characters.The Write permission is set for the folder you specify in this option.

/types AnalyticsSpecify Analytics as the product name of the target of log filecollection. This is not case-sensitive. If you omit this option,Infrastructure Analytics Advisor and all Hitachi Command Suite productsthat have been installed are subject to the command processing. In thiscase, log collection might take while.

/arc archive-file-nameSpecify the name of the archive file to be created as the result ofcommon component's material collection tool. If you omit this option,the archive file name is HiCommand_log. Archive files are output underthe folder in the /dir option.

Characters that can be specified as the archive file name includeprintable ASCII characters (0x20 to 0x7E), excluding the followingspecial characters: Backslashes (\), slashes (/), colons (:), commas (,),semicolons (;), asterisks (*), question marks (?), double quotationmarks ("), left angle brackets (<), right angle brackets (>), vertical bars(|), dollar signs ($), percent signs (%), ampersands (&), singlequotation marks ('), and grave accent marks (`) You do not need tospecify an extension.


/logtypes {log | db | csv}Specify the type of the log file for common component for which youwant to collect logs. The following table shows the correspondencebetween 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 Archive file name in the /arc option_64.db.jarcsv 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 theoption.

To specify more than one type, use a space as a delimiter (forexample, /logtypes log db csv). If you use the /types option andthe /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 hcmds64getlogscommand.

Archive file Output result

output-destination-folder-in-/dir-option\archive-file-name-in-/arc-option_64.jar

• All files in Infrastructure Analytics Advisor-installation-destination-folder\Analytics\logs

• All files in Infrastructure Analytics Advisor-installation-destination-folder\Analytics\conf

• All files in Infrastructure Analytics Advisor-installation-destination-folder\Analytics\work

• All files in Infrastructure Analytics Advisor-installation-destination-folder\Analytics\data

• All files in Infrastructure Analytics Advisor-installation-destination-folder\Analytics\system

• All files in Windows-folder#\Temp\HITACHI_HICOMMAND_INST_LOG

• List of the files in Infrastructure Analytics Advisor-installation-destination\Analytics

• List of the registry keys in HKEY_LOCAL_MACHINE\SOFTWARE\HITACHI\


Archive file Output result

• hosts file

• services file

• Result of running the ipconfig command of the OS

• Result of running the netstat command of the OS withthe -na option specified

• Result of running the msinfo32 command of the OSwith the /report option specified

• Result of running the systeminfo command of the OS

• Result of running common component's materialcollection tool (hcmdsgetlogs, hcmdsras)

output-destination-folder-in-/dir-option\archive-file-name-in-/arc-option_64.hdb.jar

Result of running common component's material collectiontool (hcmdsgetlogs)

output-destination-folder-in-/dir-option\archive-file-name-in-/arc-option_64.db.jar

output-destination-folder-in-/dir-option\archive-file-name-in-/arc-option_64.csv.jar

# By default, this is C:\WINDOWS.

Storage locationInfrastructure Analytics Advisor-installation-destination-folder/Base64/bin

Permissions


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 in the /dir option has insufficient free space, running of thehcmdsgetlogs command or hcmds64getlogs command will not becompleted. Secure a sufficient amount of space in the folder in the /diroption, and then rerun this command. Use the following formula tocalculate the amount of required free space:Size of folders and files in Infrastructure Analytics Advisor-installation-destination-folder\Analytics\data + size of folders and files inInfrastructure Analytics Advisor-installation-destination-folder\Analytics\logs + 10 GB


If products that use common component are installed on the InfrastructureAnalytics Advisor management server, add the capacity required forcollecting 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 Advisormanagement server is not running.

Return values




2 The command ran abnormally.

Example

The following example shows the use of this command to collect log files inthe folder:hcmds64getlogs /dir "C:\Users\folder01" /types Analytics /arc HIAA_log

hcmds64intgUse this command to delete authentication data registered in the repositoryof the server that manages user accounts. The command also displays theaddress of the server in which the authentication data is registered.

If you fail to delete authentication data when uninstalling InfrastructureAnalytics Advisor, use this command to delete the authentication data.

Formathcmds64intg {/delete /type Analytics | /print | /primary} /user user-ID /pass password

Options

/deleteDeletes authentication data.

/type AnalyticsSpecify Analytics as the product name of the server in which theauthentication data is registered.


/printDisplays the name of the program in which the authentication data isregistered.

/primaryDisplays the host name or the IP address of the server in which theauthentication data is registered.

/user user-IDSpecify the user ID for connecting with the server in which theauthentication data is registered. The user ID you specify must have theUser Management permission.

/pass passwordSpecifies the password of the account that has the User Managementpermission.

Storage location


Permissions


Return values



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

4 Authentication data is not registered in the server on which you ran thecommand. In addition, an authentication error occurred on the server in whichauthentication data is registered.

253 An authentication error occurred on the server in which authentication data isregistered.

254 Communication with the server in which authentication data is registeredfailed.


Example

The following example shows the use of this command to deleteauthentication data from the server that manages the user account:


hcmds64intg /delete /type Analytics /user user1 /pass pass1

hcmds64srvUse this command to start or stop Infrastructure Analytics Advisor services..The command also displays the Infrastructure Analytics Advisor servicestatus or changes the service start method.

Format

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 Advisorand products that use common component:

hcmds64srv /statusall

To change the start method of a service:hcmds64srv /starttype {auto | manual} {/server service-name | /all}

Options

/startStarts the service and database you specified in the /server option.

/stopStops the service and database you specified in the /server option.

/checkDisplays the status of the server and database you specified in the /server option.

/statusDisplays the status of the server and database you specified in the /server option.

/server service-nameTo start, stop, or display the status of Infrastructure Analytics Advisorproduct services only, specify AnalyticsWebService as the servicename. By running this command by specifying AnalyticsWebService inthe server option, you can start, stop, or display the status of thefollowing services:


Service display name and process Start StopStatusdisplay

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

# An Infrastructure Analytics Advisor internal process corresponding to the service HiRDB/EmbeddedEdition _HD1

If you omit the /server option, the next service is started, stopped, orthe status of the next service displays.

Service display name and process Start StopStatusdisplay

Status display(/statusall)

HAnalytics Engine Web Service 　Y　　Y　　Y　　Y　

HBase 64 Storage Mgmt SSOService

　Y　　Y　　Y　　Y　

HBase 64 Storage Mgmt WebService

　Y　　Y　　Y　　Y　

HBase 64 Storage Mgmt Web SSOService

　Y　　Y　　Y　　Y　

Database process# 　Y　　Y　　Y　　Y　

Service of products that usecommon component

　Y　　Y　　Y　　Y　

Legend:

Y: Processed

N: Not processed

# An Infrastructure Analytics Advisor internal process corresponding to the service HiRDB/EmbeddedEdition _HD1

/statusallDisplays the service and data statuses, and the status of the productsregistered in common component. If you omit the /server option, thisargument is used.

/starttype {auto | manual}Specify the start type of the service with the /server option. Specifyauto for an automatic start. Specify manual for a manual start.

/all


If you specify this option, the command runs for all services ofInfrastructure Analytics Advisor and other products that use commoncomponent.

Storage location


Permissions


Notes• If you start or stop Infrastructure Analytics Advisor services as a daily

operation, omit the /server option to start or stop all the services. Tostart only Infrastructure Analytics Advisor services by specifying the /server option, specify AnalyticsWebService for the /server option tostart common component service.

• If you run the command with the /stop option and the terminationprocessing does not end within three minutes, an error occurs and amessage is displayed to indicate a time-out. In this case, wait a while, andthen rerun the command with the /stop option.

• If you start or stop a service with the /start　or /stop option, thecommand might end while the service does not start or stop completely. Toconfirm that the service has completely started or stopped, use either ofthe following operations:○ Confirm that either of the following messages has been output to a

disclosed log or the event log:

At startup

KNAQ10086-I Application is running.

When stopped

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 /startoption or /stop option:




1With /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:


0 The service has not started.

1 The service has started.


The following table shows the return values of the command with the /starttype option:




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 Advisorproducts:

hcmds64srv /start /server AnalyticsWebService


hcmds64ssltoolUse this command to create private keys, certificate signing requests (CSRs),self-signed certificates, and content files for self-signed certificates that arerequired for SSL connections. The created files are used for the followingpurposes:• Submitting the CSR to a CA to obtain an SSL server certificate. You can

build an SSL-connected environment by combining the obtained SSL servercertificate and the private key.

• Building an SSL-connected environment by combining the self-signedcertificate with the private key. However, we recommend that you use theenvironment for only test purposes because security is low.

• Checking the details of the registration of the self-signed certificate fromthe content file of the self-signed certificate.

Formathcmds64ssltool [/key private-key-file-name] [/csr CSR-file-name] [/cert self-signed-certificate-file-name] [/certtext name-of-the-content-file-of-the-self-signed-certificate] [/validity expiration-date-of-the-self-signed-certificate] [/dname distinguished-name (DN)] [/sigalg signature-algorithm] [/eccsigalg signature-algorithm-of-the-server-certificate-for-elliptic-curve-cryptography] [/ecckeysize size-of-the-private-key-for-elliptic-curve-cryptography]

Options

/key private-key-file-nameSpecify the absolute path for storing the private key. The private key forRSA cryptography will be output to a file of the specified file name. Theprivate key for elliptic curve cryptography will be output to another fileof the specified file name with the prefix ecc-.

If you omit this option, the httpsdkey.pem file and the ecc-httpsdkey.pem file will be output under Infrastructure AnalyticsAdvisorInstallation-destination-folder\Base64\uCPSB\httpsd\conf\ssl\server\.

/csr CSR-file-nameSpecify the absolute path for storing the CSR. The CSR for RSAcryptography is output to a file of the specified file name. The CSR for


elliptic curve cryptography will be output to another file of the specifiedfile name with the prefix ecc-.

If you omit this option, the httpsd.csr file and the ecc-httpsd.csr fileis output under Infrastructure Analytics AdvisorInstallation-destination-folder\Base64\uCPSB\httpsd\conf\ssl\server\.

/certself-signed-certificate-file-nameSpecify the absolute path for storing the self-signed certificate. The self-signed certificate for RSA cryptography will be output to a file of thespecified file name. The self-signed certificate for elliptic curvecryptography is output to another file of the specified file name with theprefix ecc-.

If you omit this option, the httpsd.pem file and the ecc-httpsd.pem fileis output under Infrastructure Analytics AdvisorInstallation-destination-folder\Base64\uCPSB\httpsd\conf\ssl\server\.

/certtext name-of-the-content-file-of-the-self-signed-certificate

Outputs the content of the self-signed certificate in text format. Specifythe absolute path for storing the content file. The content of the self-signed certificate for RSA cryptography is output to a file of the specifiedfile name. The content of the self-signed certificate for elliptic curvecryptography is output to another file of the specified file name with theprefix ecc-.

If you omit this option, the httpsd.txt file and the ecc-httpsd.txt fileis output under Infrastructure Analytics AdvisorInstallation-destination-folder\Base64\uCPSB\httpsd\conf\ssl\server\.

/validity expiration-date-of-the-self-signed-certificateSpecify the expiration date of the self-signed certificate in terms of thenumber of days. If you specify this option, the same value is specifiedfor RSA cryptography and elliptic curve cryptography. If you omit thisoption, the certificate expires in 3,650 days.

/dname distinguished-name (DN)Specify the distinguished-name (DN) described in the SSL servercertificate, in the format "attribute-type=attribute-value". You canspecify some attribute type values using a comma (,) as a delimiter.

Characters specified for attribute types are not case sensitive. Youcannot use a double quotation mark (") or a backslash (/) in theattribute type. For details about how to escape characters, follow theinstructions 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 theinstructions in the window displayed when you run the command.

The following table lists the attribute types that you can specify for thisoption:

Attributetype

Definition Window response Attribute value

CN Common Name Server Name Distinguished-name# of theInfrastructure Analytics Advisormanagement server, such ashost name, IP address, ordomain name

OU OrganizationalUnit Name

Organizational Unit Lower-level organization name,such as department or sectionname

O OrganizationName

Organization Name Company or otherorganization's name#

L Locality Name City or Locality City name or region name

ST State or ProvinceName

State or Province State name or district name

C Country Name two-character country-code

Country code

# Required in a response entry

The following is an example of response input:Enter Server Name [default=MyHostname]:example.comEnter Organizational Unit:Device Manager AdministrationEnter Organization Name [default=MyHostname]:HITACHIEnter your City or Locality:Santa ClaraEnter your State or Province:CaliforniaEnter your two-character country-code:USIs CN=example.com,OU=Device Manager Administration,O=HITACHI,L=Santa Clara, ST=California,C=US correct? (y/n) [default=n]:yIf the entry is incorrect, you can input again by typing n.

/sigalg signature-algorithmSpecify any of the following as the signature algorithm. If you omit thisoption, SHA256withRSA is used.


• SHA1withRSA

• SHA256withRSA

/eccsigalg signature-algorithm-of-the-server-certificate-for-elliptic-curve-cryptography

Specify the signature algorithm of the server certificate for elliptic curvecryptography. You can specify SHA512withECDSA, SHA384withECDSA,SHA256withECDSA, or SHA1withECDSA. If you omit this option, thesignature algorithm is SHA384withECDSA.

ecckeysize size-of-the-private-key-for-elliptic-curve-cryptography

Specify the size (in bits) of the private key for elliptic curvecryptography. You can specify 256 or 384. If you omit this option, thesize of the private key for elliptic curve cryptography is 384 bits. Thesize of the private key for RSA cryptography is fixed as 2,048 bits.

Storage location


Permissions


Notes

If the value of the attribute type CN of the SSL server certificate does notmatch the host name, IP address, or domain name as the connectiondestination of the Infrastructure Analytics Advisor management server fromthe web browser, a message indicates a server mismatch.

Return values




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.



hcmds64unlockaccountWhen the user accounts of all users who have the User Managementpermission are locked, use this command to unlock those user accounts.

Formathcmds64unlockaccount /user user-ID /pass password

Options

/user user-IDSpecify the user ID of the user account to be unlocked. The user ID youspecify must have the User Management permission.

/pass passwordSpecify the password of the user account to unlock.

Storage location


Permissions


Notes• You can use the hcmds64unlockaccount command to unlock only user

accounts that have the User Management permission.

• If the user name or password contains an ampersand, vertical bar, orcaret, enclose each of these symbols with double quotation marks or add acaret before each symbol as an escape character.For example, if the password is ^a^b^c^ in Windows-based, use either ofthe following:• hcmds64unlockaccount /user system /pass "^"a"^"b"^"c"^"

• hcmds64unlockaccount /user system /pass ^^a^^b^^c^^


Return values



251 An authentication error (logon error) occurred.

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.


Example

The following example shows how to use this command to unlock a useraccount:hcmds64unlockaccount /user test01 /pass TTdate00

reloadtemplateUse this command to reroad the template files of Infrastructure AnalyticsAdvisor during the startup of Infrastructure Analytics Advisor.

The following table describes the types of template files that the commandreferences, and the reference destination folders:

Type of template file Reference destination folder

Template file for linking with emails Infrastructure Analytics Advisor-installation-destination-folder\Analytics\conf\template\mail

Template file for linking with commands Infrastructure Analytics Advisor-installation-destination-folder\Analytics\conf\template\command

Formatreloadtemplate/user user-ID /passwordfile password-file

Arguments

/user user-IDSpecify the Infrastructure Analytics Advisor user ID to be used forcommand execution.

/passwordfile path-of-the-password-file


Specify the path to the password file of the user who is specified forthe /user option. Use the encryptpassword command to create thepassword file.

Storage location


Permissions


Notes

To run the command, the Infrastructure Analytics Advisor service must bestarted. If the Infrastructure Analytics Advisor service is not running, you donot have to run this command because the template files are automaticallyread when the Infrastructure Analytics Advisor service starts.

Return values




2 Command execution was interrupted.


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.


232 The reroading of the template files failed.

233 You do not have the necessary permissions to update the template file.


restoresystemUse this command to restore the backup for Infrastructure Analytics Advisorsettings or database information that you collected by running thebackupsystem command.


Formatrestoresystem /dir backup-directory /type {all | Analytics} [/auto]

Options

/dir backup-directorySpecify the folder in which the backup file is stored with the absolute orrelative path.

/type {all | Analytics}Specify the restoration target.• all

Restores information of Infrastructure Analytics Advisor and commoncomponent. Common component instance manages the userinformation.

• AnalyticsRestores information of only Infrastructure Analytics Advisor.

/autoAutomatically stops or starts services and databases of InfrastructureAnalytics Advisor and products that use common component. If you omitthis option, services and databases of Infrastructure Analytics Advisorand products that use common component are not automaticallystopped or started.

Storage location


Permissions


Notes• When restoring the backup, the folder in which the backup file is stored

requires at least 2 GB of free space.

• When you run the restoresystem command, for backup, theextension .original is appended to the file name of the file ininstallation-folder-of- Infrastructure Analytics Advisor\Analytics\conf. 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.

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 folders:• backup-folder\HBase\base\conf

• backup-folder\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 thehttpsd.conf file and the user_httpsd.conf file. Save each file to thestorage destination folder.

• If you do not specify the /auto option, stop the service by running thehcmds64srv command with the /stop option. The service to be stoppeddepends on the /type option.

If you specified all in the /type option:

You must stop not only the service of Infrastructure Analytics Advisor,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.

• Make sure that the following information is the same between theenvironment where the backup was collected and the environment wherethe information was restored:○ Version of Infrastructure Analytics Advisor

○ Installation directory of Infrastructure Analytics Advisor

• When products that use common component are installed on theInfrastructure Analytics Advisor management server, if you do arestoration with all specified in the /type option, the definitioninformation for common component is also restored. In this example, aninconsistency might occur in the definition information between theproducts that use common component and common component itself.


Therefore, if products that use common component are installed on theInfrastructure Analytics Advisor management server of the restorationdestination, do a restoration by using one of the following procedures:

To restore data for products that use common component, inaddition to Infrastructure Analytics Advisor data

1. Run the restore command for the product that uses commoncomponent.

2. Specify /type Analytics for the restoresystem command ofInfrastructure Analytics Advisor, and then run the command.

To restore only user information, in addition to InfrastructureAnalytics Advisor data

1. Specify /type Analytics for the restoresystem command ofInfrastructure Analytics Advisor, and then run the command.

2. Update the user management information.

To restore data of only Infrastructure Analytics Advisor1. Specify /type Analytics for the restoresystem command of

Infrastructure Analytics Advisor, and then run the command.

Return values






4 Another command is currently running.





110 Running of restoration failed.

111 The start or stop of the service failed.

113 The backup file is invalid.



Example

The following example shows the use of this command to restore informationof only Infrastructure Analytics Advisor:restoresystem /dir "C:\Users\Backup" /type Analytics /auto



BUser-specified properties file

(config_user.properties)This appendix describes the definition file for configuring public logs andsetting values for dynamic thresholds.

Format

key-name=value

Storage location

installation-folder-of- Infrastructure Analytics Advisor\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 user-specified properties file, note the following points:• Any line starting with # is treated as a comment line.

• Blank lines are ignored.

• ISO8859-1 is used for character encoding.

• Specified values are case-sensitive.

• To include "\" in a specified character string, specify "\\".In this situation, "\\" is counted as a single byte.

• If you specify an invalid value, the KNAQ02022-W message is output tothe 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 lastspecification takes effect.

User-specified properties file (config_user.properties) 159Hitachi Infrastructure Analytics Advisor Installation and Configuration Guide

Settings

Category

Key name SettingSpecifiable

valuesDefault value

Publiclogs

logger.sysloglevel Threshold value foroutputting event logs.

• 0

• 10

0

logger.message.server.MaxBackupIndex

Maximum number oflog backup files for theserver.

1 to 16 7

logger.message.server.MaxFileSize

Maximum size of logfiles for the server.(unit: KB)

4 to 2,097,151 10240

logger.message.command.MaxBackupIndex

Maximum number oflog backup files forcommands.

1 to 16 7

logger.message.command.MaxFileSize

Maximum size of logfiles for commands.(unit: KB)

4 to 2,097,151 1024

Dynamicthresholdvalues(parameters)

dynamicThreshold.calculateTime

Time when thecalculation of dynamicthreshold values starts.

00:00:00 to23:59:59

00:00:00

dynamicThreshold.startLatencyDay

Period (unit: days) forwhich to check thenumber of performancevalues that arerequired to start thecalculation of dynamicthreshold values.

To specify more thanone value, use commas(,) to delimit thevalues.

Single-bytenumerals andcommas (,)

1, 3, 7, 14

dynamicThreshold.minimumDataN

Specify the minimumnumber of performancevalues that is requiredto start the calculationof dynamic thresholdvalues.

The calculation ofdynamic thresholdvalues starts when thenumber of performancevalues in the periodspecified fordynamicThreshold.startLatencyDay exceedsthe minimum numberof performance valuesspecified fordynamicThreshold.minimumDataN.

1 to2,147,483,647

150

160 User-specified properties file (config_user.properties)Hitachi Infrastructure Analytics Advisor Installation and Configuration Guide

Category

Key name SettingSpecifiable

valuesDefault value

Dynamicthresholdvalues(margin)

dynamicThreshold.margin.Severe.plus

Specify the margin foraddition when thevalue of Margin isSevere.

0 to2,147,483,647

1

dynamicThreshold.margin.Severe.rate

Specify the margin formultiplication (unit: %)when the value ofMargin is Severe.

0 to 100 1

dynamicThreshold.margin.Normal.plus

Specify the margin foraddition when thevalue of Margin isNormal.

0 to2,147,483,647

5

dynamicThreshold.margin.Normal.rate

Specify the margin formultiplication (unit: %)when the value ofMargin is Normal.

0 to 100 5

dynamicThreshold.margin.Rough.plus

Specify the margin foraddition when thevalue of Margin isRough.

0 to2,147,483,647

10

dynamicThreshold.margin.Rough.rate

Specify the margin formultiplication (unit: %)when the value ofMargin is Rough.

0 to 100 10

Security

cert.verify.enabled Specify whether toenable the verificationof a server certificate.

true or false false

Exampleslogger.sysloglevel = 0logger.message.server.MaxBackupIndex = 7logger.message.server.MaxFileSize = 1024logger.message.command.MaxBackupIndex = 7logger.message.command.MaxFileSize = 1024dynamicThreshold.calculateTime = 00:00:00dynamicThreshold.startLatencyDay = 1, 3, 7, 14dynamicThreshold.minimumDataN = 150dynamicThreshold.margin.Severe.plus = 1dynamicThreshold.margin.Severe.rate = 1dynamicThreshold.margin.Normal.plus = 5dynamicThreshold.margin.Normal.rate = 5dynamicThreshold.margin.Rough.plus = 10dynamicThreshold.margin.Rough.rate = 10cert.verify.enabled = false

User-specified properties file (config_user.properties) 161Hitachi Infrastructure Analytics Advisor Installation and Configuration Guide

162 User-specified properties file (config_user.properties)Hitachi Infrastructure Analytics Advisor Installation and Configuration Guide

CDefault collection and data export

interval for probesThe following table lists the default data collection and default data exportinterval in minutes for all the probes:

Table 20 Default collection and data export interval

ProbesDefault collection interval

(Minutes)Default Export time periods

(Minutes)

Storage

Hitachi Enterprise Storage Collection interval depends onthe resources you monitor.

5

HNAS 1 15

Hitachi AMS 1 15

Hypervisor

VMware 1 15

Windows-based 1 15

FC Switches

Cisco DCNM 5 15

Brocade Network Advisor 5 15

Table 21 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)

CLMS CLPR Per MP Blade Summary 1

CLPS CLPR Summary 1

LDE LDEV Summary - Extended 5

LDS Logical Device Summary 5

PLC Pool Configuration 360

PLF Pool Frequency Distribution 60

PLR Pool Page Relocation 60

Default collection and data export interval for probes 163Hitachi Infrastructure Analytics Advisor Installation and Configuration Guide

Op-Code Description Default Value (Minutes)

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

PI Storage Summary 1

UMS Utilization Per MP Blade Summary 5

VVF V-VOL Frequency Distribution 60

VVTC V-VOL Tier Type Configuration 60

164 Default collection and data export interval for probesHitachi Infrastructure Analytics Advisor Installation and Configuration Guide

DInfrastructure Analytics Advisor

servicesAfter you install Infrastructure Analytics Advisor, the following InfrastructureAnalytics Advisor services are registered.

Displayed servicename

Service name Startup type Product

HAnalytics Engine WebService

AnalyticsWebService Automatic Infrastructure AnalyticsAdvisor

HBase 64 StorageMgmt SSO Service

HBase64StgMgmtSSOService

Automatic Common component

HBase 64 StorageMgmt Web Service

HBase64StgMgmtWebService


HBase 64 StorageMgmt Web SSO Service

HBase64StgMgmtWebSSOService

Manual Common component

HiRDB/EmbeddedEdition _HD1

HiRDBEmbeddedEdition_HD1


Infrastructure Analytics Advisor services 165Hitachi Infrastructure Analytics Advisor Installation and Configuration Guide

166 Infrastructure Analytics Advisor servicesHitachi Infrastructure Analytics Advisor Installation and Configuration Guide

IndexA

actionwhen you cannot log on to InfrastructureAnalytics Advisor 128

actionsunsuccessful attempt to connect to theInfrastructure Analytics Advisor web client 128when Infrastructure Analytics Advisor cannotstart 129when Infrastructure Analytics Advisor cannotbe connected to Data Center Analytics 129

addingAMS probe 65Brocade Network Advisor probe 67Cisco DCNM probe 68Hitachi Enterprise Storage probe 63HNAS probe 66probes to Analytics probe 55VMware probe 67

applying self-signed certificatesData Center Analytics management server 88

applying server certificatesData Center Analytics management server andAnalytics probe server 92

Bbacking up

Analytics probe settings information 110Data Center Analytics settings information anddatabase 109Infrastructure Analytics Advisor settinginformation 109RAID Agent 111

backupsystem command 134

Ccanceling

setup of an instance environment 61change

Host name 98installation folder 98IP address 99

port number (between Infrastructure AnalyticsAdvisor and a web browser) 99port number (between Infrastructure AnalyticsAdvisor and common component) 101port number (between Infrastructure AnalyticsAdvisor and the SMTP server) 102time (Infrastructure Analytics Advisormanagement server) 102

changingport number (for SSL communication) 95system account password 53

changing port numberbetween Infrastructure Analytics Advisor and aweb browser 99between Infrastructure Analytics Advisor andcommon component 101between Infrastructure Analytics Advisor andthe SMTP server 102

checkingcompletion of initial setup 69, 78expiration date of server certificates for DataCenter Analytics and Analytics probe 95Infrastructure Analytics Advisor servercertificate 87

commandlist 132notes 132usable characters for arguments 133

completion of initial setupchecking 69, 78

config_user.properties 159configuring

collection method 75FTP server 77mail server 53Windows-based probe 75

createinginstance environment 58

creatingprivate key and certificate signing request 82

Ddefinition information files (RAID Agent) 112

Index 167Hitachi Infrastructure Analytics Advisor Installation and Configuration Guide

Eencryptpassword command 136exporting self-signed certificate

for Data Center Analytics management server90

Ggeneral procedure

backing up 106restoring 106

Hhcmds64fwcancel command 137hcmds64getlogs command 138hcmds64intg command 141hcmds64srv command 143hcmds64ssltool command 147hcmds64unlockaccount command 151host name

change 98htmhsbackup command 111htmhsrestore command 117

Iimporting certificate

Infrastructure Analytics Advisor managementserver 91

Infrastructure Analytics Advisor managementserver SSL communication 84Infrastructure Analytics Advisor server certificate87

applying from certificate authority 83Install

Analytics probe (by using VMware vSphereClient) 45Data Center Analytics (by using VMwarevSphere Client) 35

installation folderchange 98

installingAnalytics probe 42Data Center Analytics management server 30Data Center Analytics Windows-based probe71Infrastructure Analytics Advisor 51Windows-based probe 74workflow 14

installingAnalytics probe server 39IP address

change 99

Llist

command 132

of services 165locking

system accounts 120logging on

changing password 53

Mmail server

configuring 53migrating

migrating Infrastructure Analytics Advisor toanother host 103

Nnotes

command 132

Ooverview 14

RRAID Agent

backing up 111restoring 117

RAID Agent definition information filesbackup targets 112

reloadtemplate command 152restoresystem command 153restoring

Analytics probe settings information 115Data Center Analytics settings information anddatabase 114Infrastructure Analytics Advisor settinginformation 113RAID Agent 117

Sservice

starting 104, 105stopping 104, 106

services 165setting

connection with the Data Center Analyticsmanagement server 52

setting upRAID Agent 60

SSL communicationchanging port number 95

startingAgent services 62Windows-based probe service 78

168 IndexHitachi Infrastructure Analytics Advisor Installation and Configuration Guide

starting servicesbacking up and restoring 119

stoppingAgent services 62

stopping servicesbacking up and restoring 108

system accountslocking 120

Ttime (Infrastructure Analytics Advisormanagement server)

change 102

Uusable characters for arguments

command 133user_httpsd.conf 84user-specified properties file 159

Wworkflow 14

Index 169Hitachi Infrastructure Analytics Advisor Installation and Configuration Guide

170 IndexHitachi Infrastructure Analytics Advisor Installation and Configuration Guide

Hitachi Infrastructure Analytics Advisor Installation and Configuration Guide

MK-96HIAA002-00

July 2016

Documents

Hitachi Infrastructure Analytics Advisor · Microsoft, the Microsoft ... SmartScreen, SQL Server, Visual Basic, Visual C++, Visual Studio, ... • Hitachi Infrastructure Analytics