Hitachi Data Center Analytics Deployment Guide · Product version This document revision applies to Hitachi Data Center Analytics version 8.0 or later. Intended audience This document

Hitachi Data Center AnalyticsDeployment Guide

MK-96HDCA001-09February 2017

© 2016, 2017 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 Data Center Analytics Deployment Guide

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

Contents

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

1 Deployment overview...........................................................................11Deployment...........................................................................................................12Distribution formats................................................................................................12

2 Installing Data Center Analytics server.................................................. 13Server installation prerequisites...............................................................................14Desktop prerequisites.............................................................................................14Installing the server on VMware vSphere Client........................................................ 14Installing the server on a Linux machine .................................................................15Initial setup of Data Center Analytics server............................................................. 17

3 Installing Analytics probe server............................................................19Probe installation prerequisites................................................................................20Probe port and firewall requirements....................................................................... 20Desktop prerequisites.............................................................................................22Installing the probe on the VMware vSphere Client................................................... 22Installing the probe on a Linux machine ..................................................................23Initial setup of Analytics probe server...................................................................... 25

4 Adding probes in Analytics probe server................................................ 29Storage probes...................................................................................................... 30


Adding Hitachi Adaptable Modular Storage (AMS) probe...................................... 30Adding Hitachi Enterprise Storage probe.............................................................30Adding Hitachi Device Manager probe................................................................ 33Adding Hitachi NAS probe..................................................................................34Adding IBM XIV® probe ...................................................................................34Adding EMC VNX File probe ..............................................................................35Adding EMC VNX Block probe............................................................................ 36Adding the EMC XtremIO probe......................................................................... 37Adding EMC VMAX probe...................................................................................38

Configuration in target environment............................................................. 38Install EMC Solutions Enabler Symmetrix CLI.................................................38Configure the environment variable entry in netcnfg file.................................38Adding EMC VMAX probe............................................................................. 40Adding VMAX probe for an already added EMC Unisphere for VMAX................41Editing details of EMC Unisphere for VMAX....................................................42

Adding Netapp probe........................................................................................ 42Adding the Netapp probe in the Analytics probe server.................................. 43Creating a user for NetApp 7-mode.............................................................. 43Creating a user for NetApp C-mode.............................................................. 45Configuring security settings for NetApp storage systems...............................45

Adding the Pure Storage probe.......................................................................... 46Hypervisor.............................................................................................................47

Adding VMware probe.......................................................................................47Switches................................................................................................................48

Adding Brocade Network Advisor probe..............................................................48Adding Cisco DCNM probe.................................................................................48Adding Cisco SAN Switch probe......................................................................... 49

Hosts.................................................................................................................... 50Adding Linux probe...........................................................................................50

Retrieving diagnostic data from the probe................................................................51

5 Installing Data Center Analytics Windows-based probe........................... 53Data collection methods......................................................................................... 54Windows-based probe installation prerequisites........................................................56Installing the Windows-based probe........................................................................ 57Configuring Data Center Analytics Windows-based probe.......................................... 58

Configuring the FTP or HTTPS server................................................................. 58Starting the Windows-based probe service......................................................... 59

6 Special procedures...............................................................................61Assigning a static IP address in the VMware vSphere application............................... 62Verifying console time ........................................................................................... 62Setting the time zone............................................................................................. 63Adding a megha user for the Symmetrix array..........................................................64Uninstalling the RPM Manager file for server and probe.............................................64Changing the opcode property file value.................................................................. 65Installing the HTTP proxy server..............................................................................66Encrypting the CSV file........................................................................................... 66Determining the IP address of the probe..................................................................67Backing up and restoring Data Center Analytics settings and data..............................68


Backing up the settings and data....................................................................... 68Restoring the settings and data......................................................................... 69

7 Troubleshooting...................................................................................71FTP connection problem on Data Center Analytics server.......................................... 72



PrefaceThis document describes how to use the Hitachi Data Center Analytics server.

□ Product version

□ Intended audience

□ Release notes

□ Accessing product documentation

□ Document conventions

□ Conventions for storage capacity values

□ Getting help

□ Comments

Preface 7Hitachi Data Center Analytics Deployment Guide

Product versionThis document revision applies to Hitachi Data Center Analytics version 8.0 orlater.

Intended audienceThis document is intended for Infrastructure Administrators who managecomplex data centers.

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://knowledge.hds.com/Documents.

Accessing product documentationProduct user documentation is available on Hitachi Data Systems SupportConnect: https://knowledge.hds.com/Documents. Check this site for themost current documentation, including important updates that may havebeen made after the release of the product.

Document conventionsThis document uses the following typographic conventions:

Convention Description

Bold • Indicates text in a window, including window titles, menus, menu options,buttons, fields, and labels. Example:Click OK.

• Indicates emphasized words in list items.

Italic • Indicates a document title or emphasized words in text.• Indicates a variable, which is a placeholder for actual text provided by the

user or for output by the system. Example:

pairdisplay -g group

(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

8 PrefaceHitachi Data Center Analytics Deployment Guide

https://knowledge.hds.com/Documents



Convention Description

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

Preface 9Hitachi Data Center Analytics Deployment Guide

Logical capacity values (for example, logical device capacity, cache memorycapacity) are calculated based on the following values:

Logical capacity unit Value

1 block 512 bytes

1 cylinder Mainframe: 870 KB

Open-systems:• OPEN-V: 960 KB• Others: 720 KB

1 KB 1,024 (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

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 makeconnections. 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!

10 PrefaceHitachi Data Center Analytics Deployment Guide

https://knowledge.hds.com/

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

https://community.hds.com/welcome

https://community.hds.com/welcome

mailto:[email protected]

1Deployment overview

□ Deployment

□ Distribution formats

Deployment overview 11Hitachi Data Center Analytics Deployment Guide

DeploymentThe following workflow shows the high-level tasks for deploying Data CenterAnalytics:1. Verify that the hosts on which you plan to install the Data Center

Analytics server and Analytics probe server meet the minimum systemrequirements.

2. Install and configure the Data Center Analytics server.3. Install and configure Analytics probe server.4. (Optional) Install and configure Windows-based probe, to collect data

from Windows-based machine and Hyper-V.

Distribution formatsThe Hitachi Data Center Analytics Server and Probe installer is available inthe following formats:• OVA file: This is the Open Virtualization Format (OVF) package, which

allows the Data Center Analytics server to be deployed on the VMwareinfrastructure. The Data Center Analytics server becomes a VM in theenvironment with all the required components installed.

• RPM file: This file can be deployed on a standalone physical machine thatis running the Linux operating system.

• The Data Center Analytics Windows-based probe is available in .EXEformat.

12 Deployment overviewHitachi Data Center Analytics Deployment Guide

2Installing Data Center Analytics server

You can install the Data Center Analytics server on the following systems:• VMware vSphere Client using OVA• Linux OS using RPM Manager

Installing Data Center Analytics server in VMware vSphere Client is the bestpractice.

□ Server installation prerequisites

□ Desktop prerequisites

□ Installing the server on VMware vSphere Client

□ Installing the server on a Linux machine

□ Initial setup of Data Center Analytics server

Installing Data Center Analytics server 13Hitachi Data Center Analytics Deployment Guide

Server installation prerequisites

PrerequisitesFormats

OVA (for VMware vSphere Client) RPM Manager (for Linux OS)

RAM Minimum: 4 GB

Recommended: 8 GB

Minimum: 4 GB

Recommended: 8 GB

Storage Minimum: 150 GB Minimum: 150 GB

Operating systems/Platform

vSphere Client on ESX Server 3.5or later

Linux

RHEL 6.1 (64-bit), 6.5 (64-bit), and7.1 (64-bit)

OEL 6.7 to 7.0 with UEK release 3

Desktop prerequisites

Source IP address Target IP address Default port Protocol

User Desktop Server IP address 8443 TCP

22 TCP

Installing the server on VMware vSphere ClientYou can install the Data Center Analytics server using the Open VirtualizationFormat (OVF) package on a VMware infrastructure.

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

Procedure

1. Open the vSphere Client application, then go to File > Deploy OVFTemplate.

2. In the Deploy OVF Template window, click Browse, navigate to thedirectory on the installation media that contains the OVA file, select it,and click Next.

3. In the OVF Template Details window, verify the information and clickNext.

4. In the Name and Location window, type the following details and clickNext.• Name: Name the Data Center Analytics server.

14 Installing Data Center Analytics serverHitachi Data Center Analytics Deployment Guide

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

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

6. In the Disk Format window, select the appropriate disk format, andthen click Next.• Thick Provision Lazy Zeroed: The system allocates the required

space at the time of disk creation. Each disk block is zeroed out onlyafter it is accessed for the first time by a VM.

• Thick Provision Eager Zeroed: The system allocates the requiredspace at the time of disk creation. Each disk block is zeroed outimmediately after disk creation.

• Thin Provision: The system allocates 2.8 GB space at the time ofdisk creation and, as data is added, allocates more space up to 120GB.

7. Select Power on after deployment, and click Finish.

Next steps

Configure the Data Center Analytics server.

Related tasks

• Initial setup of Data Center Analytics server on page 17

Installing the server on a Linux machineYou can use the .rpm file to install the Data Center Analytics server on aLinux Oracle Enterprise Linux (OEL) server or Red Hat Enterprise Linux server(RHEL).

Before you begin

• Do not deploy Data Center Analytics server on the same machine asAnalytics probe server.

• You must configure a firewall rule to allow incoming connection on 80,8080, and 8443 TCP ports.

• Verify that the console and clock properties are set to the same time zone,and change them if they are not.

CPAN dependencies:• ExtUtils::MakeMaker• XML::Simple• Log::Log4perl

yum/rpm dependencies:• perl• java-1.8.0-openjdk


• gcc• sysstat• openssl-devel• sudo• nss >= 3.21.0• unzip• crontabs• zip

Procedure

1. Copy the Data Center Analytics server.rpm file to a folder on the Linuxmachine.

2. Run the following command:

rpm -ivh <Data Center Analytics Server rpm>3. Run the Data Center Analytics server configuration script:

sh /usr/local/megha_installer/config.sh4. The following message appears: Do you want Japanese Language

support? Type N. (Japanese is not currently supported).5. Provide the directory path to store the application data.

By default, it is stored in /data.6. Change the default directory path as necessary.7. Press Enter.

The default port is assigned to the Data Center Analytics server.The default ports are 8080 for normal mode (http) and 8443 for securemode (https). If the default port is busy, then the system notifies youthat you must type an alternative port number. Type the appropriate portnumber.

8. If the Data Center Analytics server is running, run the appropriatecommand:• To verify the status:

sh /usr/local/megha/bin/megha-jetty.sh status• If the Data Center Analytics server is not running:

sh /usr/local/megha/bin/megha-jetty.sh start9. Add the URL of Data Center Analytics server (provided at the end of the

installation) in your firewall to bypass the port numbers and open the UIfor the server .

Next steps

Configure the Data Center Analytics server.


Related tasks

• Initial setup of Data Center Analytics server on page 17

Initial setup of Data Center Analytics serverOpen the URL of the Data Center Analytics server and follow the prompts.

Before you begin• Check the IP address of the Data Center Analytics server.• Obtain the Data Center Analytics server license from your HDS

representative.

Note: The Data Center Analytics server creates the following users for thesupported OS: megha, meghadatamars, and config. Do not change them.

Procedure

1. Enter the Data Center Analytics server URL in your browser:https://ip-address:port-numberThe default port for https access is 8443.

2. Read and accept the license agreement, and then click Next.3. In the Upload License window, click Choose File to browse to the

license file and click Open.4. Click Submit to register the license.5. In the Set Details For Existing admin User window, enter the

password, select the locale, and then click Submit (The user name forthe built-in administrator account is admin) .

Note: The current version of Data Center Analytics supports onlythe English locale.

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

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

Note: Reports display data using the time zone of the Data CenterAnalytics server (not that of the storage systems). For example, ifyour server is located in the IST time zone, reports will use ISTtime regardless of where individual storage systems are located.



3Installing Analytics probe server

You can install the Analytics probe server on the following systems:• VMware vSphere Client using OVA• Linux machine using RPM Package Manager

Installing Analytics probe server in VMware vSphere Client is the bestpractice.

□ Probe installation prerequisites

□ Probe port and firewall requirements

□ Desktop prerequisites

□ Installing the probe on the VMware vSphere Client

□ Installing the probe on a Linux machine

□ Initial setup of Analytics probe server

Installing Analytics probe server 19Hitachi Data Center Analytics Deployment Guide

Probe installation prerequisites

Prerequisites Description

Operating systems OVA deployment : VMware vSphere Client onESX Server 3.5 or later.

RPM deployment: Linux

RHEL 6.1 (64-bit), 6.5 (64-bit), and 7.1 (64-bit)

OEL 6.7 to 7.0 with UEK release 3

RAM Minimum: 2 GB

Recommended: 4 GB

Storage 50 GB

Probe port and firewall requirementsTable 1 Storage

Probe nameCollectionmethod

Source IPaddress

Target IPaddress

Default port Protocol

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

HitachiContentPlatform

SNMP Probe machine HitachiContentPlatformsystem

9090 SNMP

REST API HTTP

Hitachi NAS RUSC/CLI Probe machine HNAS SMU 22 SSH

IBM XIV® xcli Probe machine XIV StorageSystemManagementIP

7778 TCP

NetApp ONTAP API Probe machine NetApp Filer 443 HTTPS

VMAX UnisphereREST API

Probe machine Unisphereserver

8443 TCP

SYMCLI Probe machine SolutionEnabler

2707 TCP

20 Installing Analytics probe serverHitachi Data Center Analytics Deployment Guide


Source IPaddress

Target IPaddress


VNX Block2 naviseccli Probe machine VNX StorageProcessor Aand B

443 HTTPS

80 HTTP

VNX File VNX CLIStation CLI

Probe machine VNX Storage 22 SSH

XtremIO XMS (Rest API) Probe machine XMS 443 HTTPS

Pure Storage Rest AP Probe machine Pure Storage 80 HTTP

443 HTTPS

Notes:1. The CLI installer (xivcli-3.0.1-build3-linux32.tar) is available from the IBM support site,

deployed on the probe.2. The NaviCLI runs locally on the probe machine, which internally makes HTTP or HTTPS calls to

the VNX storage.

Table 2 Hypervisors


Source IPaddress

Target IPaddress


VMware vCenter API Probe machine vCenterServer / ESXHost / ESXiHost

443 TCP

Windows-based andHyper-V host

WMI Windows-based probemachine

Windows Host/Hyper-V

135 TCP

Perfmon 135 and 445

SCOM SCOM server 5723, 5724,and 51905

SCCM SCCM server 1433

Table 3 FC switches


Source IPaddress

Target IPaddress


BrocadeNetworkAdvisor

BNA (RESTAPI)

Probe machine BNA server 80 HTTP

Cisco DCNM DCNM (WebServices)

Probe machine DCNM server 80 HTTP

443 HTTPS

Cisco SANSwitch

Cisco SwitchCLI

Probe machine Cisco FCSwitch

22 SSH


Table 4 Hosts


Source IPaddress

Target IPaddress


Linux ssh Probe machine Linux Host 22 SSH

xinetd 1111 xinetd

Note: At the time of deployment, the user might have changed the actualport used on the target device.

Desktop prerequisites

Source IP address Target IP address Default port Protocol

User Desktop Server IP address 8443 TCP

22 TCP

Installing the probe on the VMware vSphere ClientYou can install the probe using the Open Virtualization Format (OVF) packageon a VMware infrastructure.

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

Procedure

1. Open the vSphere Client application, then go to File > Deploy OVFTemplate.

2. In the Deploy OVF Template window, click Browse, navigate to thedirectory on the installation media that contains the OVA file, select it,and click Next.

3. In the OVF Template Details window, verify the information and clickNext.

4. In the Name and Location window, type the following details and clickNext:• Name: Name of the Analytics probe server. The probe is identified by

this name.• Inventory location: The inventory in the VMware application in

which to add the probe.5. In the Storage window, select the storage to save the virtual storage

files, and then click Next:


6. In the Disk Format window, select the appropriate disk format, andthen click Next.• Thick Provision Lazy Zeroed: The system allocates the required

space at the time of disk creation. Each disk block is zeroed out onlyafter it is accessed for the first time by a VM.

• Thick Provision Eager Zeroed: The system allocates the requiredspace at the time of disk creation. Each disk block is zeroed outimmediately after disk creation.

• Thin Provision: The system allocates 2.8 GB space at the time ofdisk creation and, as data is added, allocates more space up to 120GB.

7. Select Power on after deployment, and click Finish.

Next steps

Configure the Analytics probe server.

Related tasks

• Initial setup of Analytics probe server on page 25

Installing the probe on a Linux machineBefore you begin

• Do not deploy Analytics probe server on the same machine as the DataCenter Analytics server.

• You must configure a firewall rule to allow incoming connection on TCPports 80, 8080, and 8443 .

yum/rpm dependencies:• sudo• expect• unzip• Perl• java-1.8.0-openjdk• openssl-devel• make• gcc• glibc(x86-32)• crontabs• xinetd• sysstat• Zip

CPAN dependencies• ExtUtils::MakeMaker


• IO::Pty• Date::Gregorian• Date::Calc• Log::Log4perl• Net::OpenSSH• HTTP::Request• LWP::UserAgent• LWP::Protocol::https• Module::Implementation• DateTime• Log::Dispatch::FileRotate• DateTime::Format::Strptime• Data::Dumper• File::Basename• File::Copy• File::Path• File::stat• Net::Ping• Time::HiRes• Time::Local• Sys::RunAlone• XML::Simple

Procedure

1. Copy the RPM file to a folder on the Linux machine.2. Run the following command:

rpm -ivh < Data Center Analytics Probe rpm >3. Run the probe configuration script:

sh /usr/local/megha_installer/config.sh4. The following message appears: Do you want Japanese Language

support? Type N. (Japanese is not currently supported).5. Provide the directory path to store the application data.

By default, it is stored in /data.6. Change the default directory path as necessary, and press Enter.

The default port is assigned to the probe. The default ports are: 8080(HTTP) and 8443 ( HTTPS) . If the default port is busy, then the systemnotifies you that you must type an alternative port number.

7. Depending on whether the probe is running, run the appropriatecommand:• To verify the status:

sh /usr/local/megha/bin/megha-jetty.sh status


• If the probe is not running:

sh /usr/local/megha/bin/megha-jetty.sh start8. Add the URL of Analytics probe server (provided at the end of the

installation) in your firewall to bypass the port numbers and open the UIfor the probe

Next steps

Configure the Analytics probe server.

Related tasks

• Verifying console time on page 62• Setting the time zone on page 63• Initial setup of Analytics probe server on page 25

Initial setup of Analytics probe serverOpen the URL of the Analytics probe server and follow the prompts.

Before you begin• Check the IP address of the Data Center Analytics server.• Check the IP address of the Analytics probe server.• Obtain the Data Center Analytics license from your HDS representative.

Notes:• The Analytics probe server creates the following user accounts: megha,

meghadata, mars, and config. Do not change them.• Do not change the time zone setting manually after you log on to an SSH

client like putty. The default time zone of the Analytics probe server isUTC.

Procedure

1. Open your browser, type the Analytics probe server URL, and pressEnter.https://Analytics-probe-server-IP-address:8443

2. When you first launch the Analytics probe server UI, you see the licenseagreement details. Read, and then click Next.

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

4. Click Submit to add the license.5. In the Create Administrator Account window, provide the following,

and then click Submit:• User name and password• First name, last name, and email address of the user


• Locale: Only the U.S. English locale is currently supported.• Group: Select Admin to create an administrator account

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

7. In the Basic Information window, specify the following details, andthen click Next:• Customer Name: The customer name is displayed in the Basic

Information window. Provide the following information and clickNext.

• Administrator Contact Name and the Administrator ContactEmail.

• Technical Contact Name and Technical Contact Email: Specifythe point of contact (administrator) to notify about the technicalproblems.

8. In the Select Time zone window, make a selection and then click Next.9. In the FTP Information window, specify the following details:

• FTP Method: FTP, FTPS, SFTP, or HTTPS• Server: Data Center Analytics server IP address• Port: Based on the selected FTP method. The default port for HTTPS is

7443.• User: meghadata• Password: meghadata123• Passive: Connect to the FTP server in Passive mode (default: Active)• Proxy: Select to configure a proxy

Note: Do not change the password of the FTP user meghadataused by the Data Center Analytics server. Instead, disable therelevant shell of meghadata if necessary.

10. Click Next.11. In the Data Collection duration window, verify the information in your

license, and then click Next.12. From the list of probes, select the probe type and configure it to collect

data from the monitoring target, (You must add at least one probe tocomplete the installation).To add additional probes, go to the Analytics probe server web UI homepage and click Add Probe. The following are available:• Hitachi Adaptable Modular Storage (AMS) probe

• Hitachi Enterprise Storage probe

• Hitachi NAS probe

• Hitachi Device Manager probe


• IBM XIV® probe

• EMC VMAX probe

• EMC VNX Block probe

• EMC VNX File probe

• EMC XtremIO probe

• NetApp probe

• Pure Storage probe

• VMware probe

• Brocade Network Advisor probe

• Cisco DCNM probe

• Cisco SAN Switch probe

• Linux probe

Related tasks

• Determining the IP address of the probe on page 67• Assigning a static IP address in the VMware vSphere application on

page 62



4Adding probes in Analytics probe server

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

□ Storage probes

□ Hypervisor

□ Switches

□ Hosts

□ Retrieving diagnostic data from the probe

Adding probes in Analytics probe server 29Hitachi Data Center Analytics Deployment Guide

Storage probesAdding Hitachi Adaptable Modular Storage (AMS) probe

The AMS probe also supports HUS storage controllers.

Procedure

1. On the Analytics probe server home page, click Add Probe.2. In the Add Probe window, from the Probes list, select Hitachi AMS.3. In the Probes Details section, type the following details, and then click

Next:• AMS Storage Name: Name of the AMS2000 family or HUS100 family

storage system for which the probe is added. (This must not be thesame as the storage name that is defined in your environment.) Afteryou add the probe, it is identified with this name in the Analyticsprobe server.

• 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 AMS2000 family orHUS100 family storage system is disabled, then you must typea dummy user name and password because these two fields aremandatory 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.

Adding Hitachi Enterprise Storage probeThe Hitachi Enterprise Storage probe collects data from VSP G1000, VSPG1500, VSP F1500, VSP Gx00 models, VSP Fx00 models, Virtual StoragePlatform, and HUS VM storage systems.

Before you begin

• The minimum supported RAID Agent version is 8.4.1-00.• Make sure that the storage instance is added in the RAID Agent using the

command device. For each instance on the RAID Agent, make sure thatthe following services are running:○ Agent Store for RAID Instance name

30 Adding probes in Analytics probe serverHitachi Data Center Analytics Deployment Guide

○ RAID Agent Instance name• Make sure that the following services are running on the RAID Agent

Server:○ HTnM REST Application Service○ HTnM REST Web Service

• To collect metrics from hbaPort, raidOwner, raidPortWWN, raidLU, andraidHG resources, enable the data collection of the HGC, HHGC, and LHGCoperation codes on the RAID Agent instance.

• To monitor a logical device that is not mapped to any port, the value ofUNASSIGN_VOL must be set to Y.

• The following are required to collect ESW metrics:○ The minimum supported RAID Agent version is 8.5.0-00○ Each RAID Agent instance is added using the command device and

TCP/IP connection• The following are required to collect Server Priority Manager (SPM)

metrics:○ Storage system must have the SPM setting enabled.○ The operation codes PWPC and LWPC must be enabled on the RAID

Agent instance.

Procedure

1. On the Analytics probe server home page, click Add Probe.2. In the Add Probe window, from the Probes list, select Hitachi

Enterprise Storage.3. In the Provide RAID Agent Details section, provide the following

details, and then click Next:• Probe Name: The probe name must contain a minimum of four

alphanumeric characters. Example: HESP53076. The probe name mustbe unique in the Data Center Analytics deployment. The probe namecannot include any special characters other than hyphen andunderscore.

• Connection Type: Choose HTTP or HTTPS.

Note: Do not use the secure connection (HTTPS) for the HitachiEnterprise Storage probe to collect data from the RAID Agent.

• 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. The host name must match the RAID Agenthost name (case-sensitive). Specify the host name that is returnedwhen you run the uname -n command on the Analytics probe server.Do not use localhost.


• RAID Agent Port: Port number used by the RAID Agent on the RAIDAgent host. The default port numbers are:24221-HTTP24222-HTTPS

• 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 add the storage system to the RAID Agent.

• Enable real time data collection: Select the check box to collectreal-time data that can be used for alerts, reports, and the REST API.

Note: Enabling the real-time data collection increases the loadon the Data Center Analytics server CPU and memory. Todisable the real-time data collection, clear the Enable realtime data collection check box.

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, make sure that you change it on the RAIDAgent.

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

Hitachi Device Manager details section is unavailable. Click Next,and a message appears, stating that the Hitachi Enterprise Storageprobe is successfully added.

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

If the Provide Hitachi Device Manager details option is enabled, typethe following details, 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:http://Device-Manager-IP-Address:Port/service/StorageManager

• Port: Port number of the Hitachi Device Manager server. The defaultport numbers are:2001-HTTP2443-HTTPS


• Username/Password: User name and password of the HitachiDevice Manager. The user must be added in the ViewGroup user groupof Hitachi Device Manager.

6. In the Validation window, Click Next, and then click OK.7. In the Status window, in Action, click Start to start collecting data.8. If you try to set up the Hitachi Enterprise Storage probe immediately

after setting up an instance in the RAID Agent, the setup task fail withthe following alert:

Validating RAID Agent details Validating RAID Agent details failed.Error:Storage details are not available through PD record

Verify the values you specified. If they are correct, wait a few minutesand try again. You might have to wait approximately one hour before youcan add the Hitachi Enterprise Storage probe.

Related references

• Changing the opcode property file value on page 65

Adding Hitachi Device Manager probeThe Hitachi Device Manager probe collects storage capacity and hostinformation related to the Hitachi storage systems that use the Hitachi DeviceManager API.

Before you begin

• Configure the Hitachi Device Manager with the storage devices for whichyou want to collect data.

• The user account of the Hitachi Device Manager that you use while addingthe Hitachi Device Manager (HDvM) probe must have access to queryingthe storage capacity and host information.

• The Analytics probe server must be able to access the Hitachi DeviceManager.

• The Hitachi Device Manager version must be 7.5 or later.

Procedure

1. On the Analytics probe server home page, click Add Probe.2. In the Add Probe window, from the Probes list, select Hitachi Device

Manager.3. In the Add Details section, type the following details, and then click

Next:• Connection Type: HTTP or HTTPS.• IP Address: IP address of the Hitachi Device Manager server.• Default port number:

2001-HTTP


2443-HTTPS• Username and Password: User name and password with at least

read-only privileges on the Hitachi Device Manager server. The usermust be a member of the ViewGroup user group.


Adding Hitachi NAS probeAdd a Hitachi NAS probe to collect data from the Hitachi NAS platform.

Before you begin

Make sure that the NAS System Management Unit (SMU) users have CLIaccess.

Procedure

1. On the Analytics probe server home page, click Add Probe.2. In the Add Probe window, from the Probes list, select Hitachi NAS.3. In the Probes Details section, type the following details, and then click

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

(SMU)

• User name and Password: The user credentials with minimum read-only privileges to connect to the SMU

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

The Choose Server window list all servers associated with the SMU.6. In the Validation window, click Next, and then click OK.7. In the Status window, in Action, click Start to start collecting data.

Adding IBM XIV® probeThe IBM XIV probe collects configuration and performance data from IBM XIVstorage systems.

Before you begin

Download XIV CLI from the IBM support site and save it in Analytics probeserver in the /opt directory.

Procedure

1. Log on to the Analytics probe server through an SSH client (like putty)using the following credentials:• Host: IP address of the Analytics probe server


• User: root• Password: app.jeos

2. Navigate to the /opt directory:

cd /opt3. Copy the IBM XIV CLI package in the /opt directory (package name

must be similar to the following: xivcli-3.0.1-build3-linux32.tar).4. Extract the package at the /opt location using the following command:

tar –xvf package-name5. Verify the following after extracting the package at the/opt location:

a. The /opt directory must have the following subdirectories: XIVGUI/lib, XIVGUI/jre, and XIVGUI/xcli.

b. If the structure does not match, then check if it contains the binaryfile. For example, xivcli-3.0.1-build3-linux32.bin.

c. Go to the directory that contains the binary file and run it. Forexample:./xivcli-3.0.1-build3-linux32.bin

d. The software prompts for a location. Provide the installation directorylocation as /opt/XIVGUI.

6. On the Analytics probe server home page, click Add Probe.7. In the Add Probe window, from the Probes list, select XIV.8. In the Probes Details section, type the following details, and then click

Next:• Storage System IP Address: IP address of the target IBM XIV®

storage system.• User name: User name of the storage system. Verify that the user

has the minimum read-only permissions to collect configuration andperformance data.

• Password: User password9. In the Validation window, click Next, and then click OK.

10. In the Status window, in Action, click Start to start collecting data.

Adding EMC VNX File probeThe EMC VNX file probe collects the NAS configuration and NAS performancedata from the VNX file storage systems.

Procedure

1. On the Analytics probe server home page, click Add Probe.2. In the Add Probe window, from the Probes list, select VNX File.3. In the VNX File Probe Details window, type the following details, and

then click Next:• IP Address: IP address of VNX File control station.• Username: User name to log on to the VNX file storage.

Verify that the user has at least an operator role.


For this, verify that the nasadmin operator role and CLI accessallowed options are selected.

• Password: Password to log on to the VNX File storage.4. In the Validation window, click Next, and then click OK.5. In the Status window, in Action, click Start to start collecting data.

Adding EMC VNX Block probeEMC VNX block probe collects data from VNX storage systems.

Before you begin• Authorize the VNX Block storage system user to perform a minimum

operator role.• Enable the Statistics logging to collect performance data. Statistics logging

affects storage-system performance, so leave it off unless you want tomonitor performance.

• Install the NaviCLI on the Analytics probe server machine.

Procedure

1. Log on to the probe appliance using an SSH client like putty, with thefollowing credentials:• User name: root• Password: app.jeos

2. Copy the NaviCLI package on the Analytics probe server.3. Run the following command to install the package:

rpm -ivh <NaviCLI package RPM>

Note: The NaviCLI executable file must be at the followinglocation: /opt/Navisphere/bin/

4. On the Analytics probe server home page, click Add Probe.5. In the Add Probe window, from the Probes list, select VNX Block.6. In the VNX Block Probe Details window, type the following details, and

then click Next:• Probe Name: Unique name of the probe.• Processor-A IP Address: IP address of Processor A of VNX block

storage.• Processor-B IP Address: IP address of Processor B of VNX block

storage.• Username: User name of the user to log on to VNX Block storage.• Password: Password of the user name.• Enable real time data collection: Select the check box to collect

real-time data that can be used for alerts, reports, and REST API.


Note: Enabling the real-time data collection increases the loadon the Data Center Analytics server CPU and memory. Todisable the real time data collection, clear the Enable real timedata collection check box.


Adding the EMC XtremIO probeThe EMC XtremIO probe collects configuration and performance data fromthe EMC XtremIO storage systems.

Before you begin• The host name or IP address of the XtremIO Management server must be

accessible from Analytics probe server using the default port 443.• User with read-only permissions on XtremIO Management server to

execute REST API calls.

Procedure

1. On the Analytics probe server home page, click Add Probe.2. In the Add Probe window, from the Probes list, select EMC XtremIO.3. In the Provide XtremIO Management Server Details section, click

Add XMS.4. Type the following details, and then click Next:

• Host Name / IP: The host name or IP address of the XtremIOManagement server.

• User Name: User with read-only permissions on XtremIOManagement server to execute REST API calls.

• Password: User password.• Enable real time data collection: Select the check box to collect



5. In the Validation window, click Next.The Managed XtremIO cluster section appears.

6. Select the cluster and click Next.

Note: If you select multiple clusters, then the system adds a newEMC XtremIO probe for each cluster.


7. When adding multiple clusters, the Status window shows multipleprobes. Start each probe individually to collect data.


Adding EMC VMAX probeEMC VMAX probe collects data from EMC VMAX storage systems.

Configuration in target environment• EMC Unisphere for VMAX: A machine with EMC Unisphere for VMAX

(1.6.2.4, 8.1.0.3) installed, monitoring target storage systems.• EMC Solutions Enabler Symmetrix CLI: A machine (could be the same

as for EMC Unisphere for VMAX or different) with EMC Solutions EnablerSymmetrix CLI (7.6.2.26, 8.0.3) installed, monitoring all the targetstorage systems for which you are adding the probe.

Install EMC Solutions Enabler Symmetrix CLI

Procedure

1. Log on to the Analytics probe server with the following credentials:• User name: root• Password: app.jeos.

2. Copy the EMC Solutions Enabler Symmetrix CLI tar file on Analyticsprobe server machine.

Note: We recommend that you install the same version of EMCSolutions Enabler Symmetrix CLI, as installed in the targetenvironment.

3. Extract the tar file using the following command:

tar -zcxf se<version>-Linux-i386-SMI.tar.gz4. Install EMC Solutions Enabler Symmetrix CLI using the following

command:

./se<version>_install.sh -install -all

Configure the environment variable entry in netcnfg fileTo collect data from target storage systems using EMC Solutions EnablerSymmetrix CLI, edit the netcnfg file.

Procedure

1. Log on to the Analytics probe server with the following credentials:• Username: root


• Password: app.jeos2. Verify the security_level property on the machine where EMC

Solutions Enabler Symmetrix CLI server is installed using the applicableprocedure from the following:• If the security_level property is NONSECURE or ANYa. Edit the netcnfg file: vi/var/symapi/config/netcnfgb. At the end of the file, add the following:

SYMCLI_<SYMCLI SERVER IP address> - TCPIP address <Server Nodname> <IP Address> <Port> NONSECURE

<Server Nodname> is the Server host name where EMC SolutionsEnabler Symmetrix CLI is installed in target environment.

<IP Address> is the IP address of the machine where EMC SolutionsEnabler Symmetrix CLI is installed.

Default port number2707-TCP for SYMCLI8443 TCP for Unisphere REST API

Example:SYMCLI_10.10.10.10 - TCPIP WIN-PC1 10.10.10.10 2707NONSECURE

c. Edit the /etc/hosts file, and add an entry for the target SYMAPIserver:

<SYMAPI SERVER IP ADDRESS> <SYMAPI SERVER HOST NAME>

For example: 10.10.10.10 WIN-PC1

Note: If you are using the DNS server, then configure it on theprobe to avoid making changes in the /etc/hosts file.

• The security_level property is SECURE.a. Edit the netcnfg file: vi /var/symapi/config/netcnfgb. At the end of the file, add the following:

SYMCLI_<SYMCLI SERVER IP> - TCPIP <Server Nodname> <IP Address> <Port> SECURE

<Server's Nodname> is the Server’s host name where EMC SolutionsEnabler Symmetrix CLI is installed in the target environment.

<IP Address> is the IP address of the machine where EMC SolutionsEnabler Symmetrix CLI is installed.

Default port number


27070 for TCP

Example:SYMCLI_10.10.10.10 - TCPIP WIN-PC110.10.10.10 2707SECURE

c. Edit the/etc/hosts file, and add an entry for the target SYMAPIserver:

<SYMAPI SERVER IP ADDRESS> <SYMAPI SERVER HOST NAME>

For example: 10.10.10.10 WIN-PC1

Note: If you are using a DNS server, then make sure youconfigure it on the probe appliance to avoid making changes inthe /etc/hosts file.

d. Save the file.

Note: If authentication is enabled for Symmetrix arrays, then adda megha user with the monitor role for each Symmetrix array.

Adding EMC VMAX probeEMC VMAX probe collects data from EMC VMAX storage systems.

Procedure

1. On the Analytics probe server home page, click Add Probe.2. In the Add Probe window, from the Probes menu, select VMAX.3. In the VMAX Unisphere Details window, click Add Unisphere.4. In the Add VMAX Unisphere window, type the following details, and

then click Next:• IP Address: IP Address of the machine where EMC Unisphere for

VMAX is installed.• User name and Password: User name and password for EMC

Unisphere.5. In the Managed VMAX Storage System window, select the VMAX

storage systems, type the Sym CLI Host IP address, and then clickFinish.



Related tasks

• Adding a megha user for the Symmetrix array on page 64

Adding VMAX probe for an already added EMC Unisphere for VMAXYou can VMAX probe for previously added EMC Unisphere for VMAX.

Procedure

1. On the Analytics probe server home page, click Add Probe.2. In the Add Probe window, from the Probes menu, select VMAX.3. In the Managed VMAX Storage System window, select the VMAX

storage systems for which you want to add VMAX probe and enter theSym CLI Host IP address where the EMC Solutions Enabler SymmetrixCLI is installed.


4. Click Finish, and then click OK.

Editing details of EMC Unisphere for VMAXThe EMC Unisphere for VMAX administrator can change the password or username in the Analytics probe server to continue data collection.

Procedure

1. In the Status window, stop the VMAX probe.2. Click the Edit link corresponding to the EMC Unisphere for VMAX.3. In the Edit VMAX Unisphere Details window, edit the user name or

password of the EMC Unisphere for VMAX, and then click Next.4. In the Validation window, click Next, and then click OK.

Adding Netapp probeThe NetApp probe collects configuration and performance data from NetAppstorage systems using the ONTAP API.

Prerequisites

• Ensure that you have a user with read-only privileges available on theNetApp storage system with the appropriate role to collect configurationand performance data. Analytics probe server supports 7-mode and C-mode types of NetApp storage systems. The procedure for creating usersdepends on the target of the storage system type.

• Configure security settings for NetApp storage systems.


Adding the Netapp probe in the Analytics probe server

Procedure

1. On the Analytics probe server home page, click Add Probe.2. In the Add Probe window, from the Probes menu, select NetApp.3. In the Probe Details section, type the following details, and then click

Next:• NetApp Server: IP address of the NetApp server.• Username and Password: Type the user name and password you

created.• Enable real time data collection: Select the check box to collect




Creating a user for NetApp 7-mode

Procedure

1. Log on to the NetApp command line.2. Add a role:

• Run the following command for NetApp storage system version 7.3.6:For example:

useradmin role add <Role Name> -a login-http-admin,api-system-get-info,api-license-list-info,api-aggr-list-info,api-volume-list-info,api-nfs-exportfs-list-rules,api-disk-list-info,api-quota-report,api-lun-list-info,api-lun-map-list-info,api-qtree-list,api-perf-object-instance-list-info,api-perf-object-counter-list-info,api-perf-object-get-instances,api-system-get-version,api-snapmirror-get-status,api-useradmin-user-list,api-volume-get-root-name,api-volume-options-list-info,api-useradmin-group-list,api-snapshot-list-info,api-useradmin-role-list,security-api-vfiler

dataontap> useradmin role add Role_Name -a login-http-admin,api-system-get-info,api-license-list-info,api-aggr-list-info,api-volume-list-info,api-nfs-exportfs-list-rules,api-disk-list-info,api-quota-report,api-lun-list-info,api-lun-map-list-info,api-qtree-list,api-perf-object-instance-list-info,api-perf-object-counter-list-info,api-


perf-object-get-instances,api-system-get-version,api-snapmirror-get-status,api-useradmin-user-list,api-volume-get-root-name,api-volume-options-list-info,api-useradmin-group-list,api-snapshot-list-info,api-useradmin-role-list,security-api-vfilerRole <Role_Name> added.Mon Apr 25 16:03:02 IST [netapp73-1 (takeover): useradmin.added.deleted.info]: The role 'Role_Name' has been added.

• Run the following command for NetApp storage system version 8.0.1:For example:

useradmin role add <Role Name> -a login-http-admin,api-system-get-info,api-license-list-info,api-aggr-list-info,api-volume-list-info,api-nfs-exportfs-list-rules,api-disk-list-info,api-quota-report,api-lun-list-info,api-lun-map-list-info,api-qtree-list,api-perf-object-instance-list-info,api-perf-object-counter-list-info,api-perf-object-get-instances,api-system-get-version,api-snapmirror-get-status,api-useradmin-user-list,api-volume-get-root-name,api-volume-options-list-info,api-useradmin-group-list,api-snapshot-list-info,api-useradmin-role-list,api-net-ifconfig-get,security-api-vfiler

dataontap> useradmin role add Role_Name -a login-http-admin,api-system-get-info,api-license-list-info,api-aggr-list-info,api-volume-list-info,api-nfs-exportfs-list-rules,api-disk-list-info,api-quota-report,api-lun-list-info,api-lun-map-list-info,api-qtree-list,api-perf-object-instance-list-info,api-perf-object-counter-list-info,api-perf-object-get-instances,api-system-get-version,api-snapmirror-get-status,api-useradmin-user-list,api-volume-get-root-name,api-volume-options-list-info,api-useradmin-group-list,api-snapshot-list-info,api-useradmin-role-list,api-net-ifconfig-get,security-api-vfilerRole <Role_Name> added.dataontap> Mon Apr 25 16:03:02 IST [dataontap: useradmin.added.deleted.info]: The role 'Role Name' has been added.

3. Add a group:

useradmin user add User_Name -g Group_Name

For example:

dataontap>dataontap> useradmin user add User_Name -g Group_NameNew password:Retype new password:Mon Apr 25 16:22:00 IST [dataontap: useradmin.added.deleted.info]: The user 'User_Name' has been added.User <User_Name> added.

4. Type the password for the user added by you.


Creating a user for NetApp C-mode

Procedure

1. Log on to the target NetApp storage system using NetApp OnCommandSystem Manager.

2. Navigate to NetApp Storage system name > Configuration >Security > Users.

3. In the Users pane, click Add and type details in the Add User window:• User Name: Type any valid user name.• Password and Confirm Password: Type the user password and

confirm it.

Note: By default, the password is selected in the Authenticationcolumn.

4. In the User login methods section, click Add.5. In the Application column, select ontapi.6. In the Role column, select readonly, and then click OK.7. Click Add.

ResultThe new user is added. You can use this user to collect configuration andperformance data.

Configuring security settings for NetApp storage systemsYou must configure the probe to work with the security settings on theNetApp storage system. You can view and edit the security settings using theoptions command in the NetApp storage system.

The relevant security settings on the NetApp storage system are as follows:• TLS is enabled or disabled

Check value of tls.enable=[ON|OFF]• SSLv3 is enabled or disabled

Check value of sslv3.enable=[ON|OFF]• Length of Certificate Key on NetApp

Verify your system complies with one of the following examples:

Case 1: On the NetApp storage system, TLS is enabled (mostpreferred)

• tls.enable=ON• sslv3.enable=can be either ON or OFF• CertificateKey length=1024 or 2048

On the probe VM, verify the java.security file for the following lines:


• jdk.certpath.disabledAlgorithms=MD2, MD5, RSA keySize < 1024 Thisline must be uncommented and must include ‘RSA keySize < 1024’

• jdk.tls.disabledAlgorithms=SSLv3, MD5withRSA, DH keySize < 768This line must be uncommented and must include ‘SSLv3’

Case 2: On the NetApp storage system, TLS is disabled and SSLv3 isenabled (less preferred)

• tls.enable=OFF• sslv3.enable=ON• CertificateKey length=1024 or 2048

On the probe VM, verify the

java.security

file for the following lines:• jdk.certpath.disabledAlgorithms=MD2, MD5, RSA keySize <

1024 This line must be uncommented and have RSA keySize < 1024• jdk.tls.disabledAlgorithms=SSLv3, MD5withRSA, DH keySize <

768 This line must be commented (comment-out this line if currentlyuncommented). This enables SSLv3 to be used.

Case 3: On the NetApp storage system, the length of the certificatekey is less than 1024 (for example, 512)

Certificate keys less than 1024 are not common. In such a case, verifywith the NetApp system administrator if it can be upgraded to aCertificate Key with the length 2048 (preferred) or 1024. If the upgradeis possible, Case 1 or Case 2 is applicable.

If the length of Certificate is Key 512 or less, either tls.enable=ON orsslv3.enable=ON

On the probe VM, verify the java.security file for the following lines:• jdk.certpath.disabledAlgorithms=MD2, MD5, RSA keySize < 512

This line must be uncommented and must include ‘RSA keySize <512' or the present key length.

• jdk.tls.disabledAlgorithms=SSLv3, MD5withRSA, DH keySize <768 This line must be commented (uncommented to enable). Thisenables SSLv3 use.

Adding the Pure Storage probeThe Pure Storage probe collects configuration and performance data from thePure Storage storage systems.


Before you begin• The host name or IP address of the storage system must be accessible

from the Analytics probe server.• The port number 80 (HTTP) and 443 (HTTPS) must be open on the storage

system.• You have obtained the API token of a user with read-only permission for

executing API calls.

Procedure

1. On the Analytics probe server home page, click Add Probe.2. In the Add Probe window, from the Probes list, select Pure Storage.3. In the Provide Pure Storage Details section, type the following details,

and then click Next:• IP Address/FQDN: The host name or IP address of the storage

system.• Connection Type: Select HTTP or HTTPS protocol for REST

connection.• API Token: Type the API token of a user with read-only permission

for running REST API calls.• Enable real-time data collection: Select the check box to collect

real-time data be used for alerts, reports, and REST API.

Note: Enabling real-time data collection can increase the loadon the Data Center Analytics server CPU and memory. Todisable the real time data collection, clear the Enable real timedata collection check box.


HypervisorAdding VMware probe

VMware 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 vCenterServer 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.


SwitchesAdding Brocade Network Advisor probe

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

Before you begin• Make sure you can access Brocade Network Advisor using the port 80.

• The user must have Area of Responsibility as All Fabrics and at least onerole SAN Discovery setup or Performance with read-only permissions.

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

Procedure

1. From the Analytics probe server server home page, click Add Probe.2. In the Add Probe window, from the Probes drop-down list, select

Brocade FC Switch (BNA).3. In the Probe Details window, type the following details, and then click

Next..• Network Advisor IP: IP address of Brocade Network Advisor.

• Username and Password: User name and password of the BrocadeNetwork Advisor.


Adding Cisco DCNM probeAdd a probe to collect data from the Cisco Data Center Network Manager.

Procedure

1. From the Analytics probe server home page, click Add Probe..


2. In the Add Probe window, from the Probes drop-down list, select CiscoDCNM.

3. In the Cisco DCNM Probe Details window, type the following detailsand 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: Forexample, 80 is the port number: http://<dcnmip>:80/sanService.

• Protocol : Select HTTP or HTTPS.Default ports are:80 - HTTP443 - HTTPS

• Username and password of DCNM.

4. In the Validation window, click Next, and then click OK.5. In the Status window, under Action, click Start to start collecting data.

Adding Cisco SAN Switch probeAdd a probe to collect data from Cisco SAN switches.

Note: If the Cisco SAN switches are managed by Cisco DCNM, then useeither the Cisco DCNM probe or Cisco SAN Switch probe to collect the data.Do not use both the Cisco DCNM and Cisco SAN Switch probes to collect datafor the same switch.

Procedure

1. On the Analytics probe server home page, click Add Probe.2. In the Add Probe window, from the Probes menu, select Cisco SAN

Switch.3. In the Cisco SAN Switch Details window, in Add Switch Details, type

the following details:• Select Add Device, type the following details, and then click Add

Switch:○ Data Center: Name of the data center with the Cisco SAN switch.○ Start IP Address and End IP Address: Range of the IP address,

from which to start collecting data. This scans all the switch IPaddresses in that range, and the switch IP address is added in thesystem.


○ User Name: User name with the network-operator role and read-only privileges.

○ Password: Password of the user name.○ SSH Port: The port number. (default: 22)

• Select Upload CSV, to upload the switch details in the CSV file, andthen click Import CSV.The CSV file must be in a specific format. You can download thesample file by clicking Download Sample CSV File.

• Select Upload Encrypted CSV to upload details in the encrypted CSVfile, and then click Import CSV.The Encrypted CSV file must be in a specific format. You can downloadthe sample file by clicking Download Sample CSV File link.

The list of Cisco SAN switch IP address appears.4. If you want to add more Cisco SAN switch IP addresses, click Add More.5. Click Next.

This scans all the switch IP addresses from the specified range, and thevalid switch IP address is added in the system.

6. In the Switch Validation window, click Next, and then OK.The switch IP passed the validation and is added as a probe.


Related references

• Encrypting the CSV file on page 66

Hosts

Adding Linux probeThe Linux probe collects performance and configuration data from individualmachines running the Linux operating system. You can add a Linux probe foreach target separately or a single probe for multiple targets.

Before you begin• The sysstat rpm package must be installed on the target machine or host.• The target machine must have Perl installed with the following packages:

IO::Select, IO::Handle, File::Path, File::Path qw(mkpath), Getopt::Std, Time::HiRes qw(gettimeofday), LWP::UserAgent, and HTTP::Request

• The openssh-client must be installed on the target machine or host.• Create an installation directory with read, write, and execute permissions.

Create an installation directory only with alphanumeric, hypen, andunderscore (other characters are not supported).


Procedure

1. On the Analytics probe server home page, click Add Probe.2. In the Add Probe window, from the Probes list, select Linux.3. In the Add Host Details section, type the following details, and then

click Next:• HostIP: The IP address of the Linux host.• User Name: A user on the target Linux machine with read, write, and

execute permissions.• Password: User password• Installation Directory: Location for the data collection scripts

4. To add multiple targets, click Add More.

The Host Validation section appears. The system validates the host IPaddress.

5. When adding multiple targets the Status window shows multiple probes.Start each probe individually to collect data.

6. Click Next.The Script Deployment section appears. The data collection scripts aredeployed on the target host.

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

Retrieving diagnostic data from the probeDiagnostic data comprises the essential logs that are required to find the rootcause of any problem on the Analytics probe server. If you cannot resolve theproblem, then you can send the generated data file with the error messagesto customer support for analysis.

Procedure

1. In the browser, type the Analytics probe server URL: https://<ip_address>:<Port Number> and press Enter.

2. Log on to Analytics probe server. Using the user name and password setat the time of deployment.

3. On the Home page, in the application menu area, click the Manage link.4. In the Manage window, click the Download Diagnostic Data link.5. In the Download Diagnostic Data window, click Download to

download the file.



5Installing Data Center Analytics

Windows-based probeData 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 Windows-based probe on Windows-based machines using Data Center Analytics Windows-based probe installer.

□ Data collection methods

□ Windows-based probe installation prerequisites

□ Installing the Windows-based probe

□ Configuring Data Center Analytics Windows-based probe

Installing Data Center Analytics Windows-based probe 53Hitachi Data Center Analytics Deployment Guide

Data collection methodsYou 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 server Windows-based probeinstaller folder: \binMicrosoft.EnterpriseManagement.OperationsManager.Common.dllMicrosoft.EnterpriseManagement.OperationsManager.dllThe above DLLs are under the following folder on Windows-basedmachine:System Center Operations Manager 2007\SDK Binaries

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

• Hardware Inventory Client Agent of SCCM, must be running on the 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.

54 Installing Data Center Analytics Windows-based probeHitachi Data Center Analytics Deployment Guide

• Configuration data is collected from the individual machine and WMI query.

Prerequisites

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

• A user with Advanced Operator or Administrator role with the 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 server Windows-based probeinstaller folder: \binMicrosoft.EnterpriseManagement.OperationsManager.Common.dllMicrosoft.EnterpriseManagement.OperationsManager.dllThe above DLLs are under the following folder on Windows-basedmachine:System Center Operations Manager 2007\SDK Binaries

WMI Query• A user with the Domain Administrator role, and with the permissions to

access ROOT/WMI, ROOT, ROOT/CIMV2, and WMI namespaces on 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.


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


Prerequisites• The probe machine and the target machines must be part of either

workgroup or domain.

• Firewall exceptions must be added for the WMI and Perfmon on the 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.

Windows-based probe installation prerequisites• Supported Windows-based operating systems for the machine on which

the Windows-based probe is installed:○ Windows 7○ Windows 8○ Windows Server 2008○ Windows Server 2008 R2



○ Windows Server 2012○ Windows Server 2012 R2

• RAM: Minimum 8 GB.• Disk space: Minimum 50 GB.• Microsoft .NET Framework 3.5 Service Pack1 or later.• A user with the Logon as a Service permission.• Supported Windows operating systems for the target machines from which

the Windows-based probes collects the data:○ Windows 7○ Windows 8○ Windows Server 2003○ Windows Server 2008○ Windows Server 2008 R2○ Windows Server 2012○ Windows Server 2012 R2

Note: One Windows-based probe can collect data from a maximum of 100machines. To collect data from more than 100 machines, you must installanother Windows-based probe.

Installing the Windows-based probeInstall a probe with the Data Center Analytics Windows-based probe installer.

Before you begin

The authentication information (user name and password) on the DataCenter Analytics server Windows-based probe server and the monitoringtarget server must match.

Procedure

1. Run the Data Center Analytics Windows-based probe installer.2. To continue installation, click Next.3. In the Log on Information window, type the Domain Administrator’s or

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

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

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

5. In the Ready to Install the Program window, click Install to completethe installation.


6. Click Finish.

Configuring Data Center Analytics Windows-based probeThe following sections describe the settings that must be configured afterWindows-based probe is installed.

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 tab, select the protocol FTP or HTTPS.3. Type the following details:

• FTP Server: Type the Data Center Analytics server server IP addresswhere you want to upload the data.

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

• User: meghadata

• Password: meghadata123

Note: Do not change the password of the FTP user meghadataused on the Data Center Analytics server. Disable the relevantshell of meghadata if needed.

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.

Related tasks

• Starting the Windows-based probe service on page 59


Starting the Windows-based probe serviceStart the probe service from the Status tab in the probe console.

Procedure

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

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



6Special procedures

This section contains procedures required in special situations.

For example, after the deployment you want to verify or change the consoletime.

□ Assigning a static IP address in the VMware vSphere application

□ Verifying console time

□ Setting the time zone

□ Adding a megha user for the Symmetrix array

□ Uninstalling the RPM Manager file for server and probe

□ Changing the opcode property file value

□ Installing the HTTP proxy server

□ Encrypting the CSV file

□ Determining the IP address of the probe

□ Backing up and restoring Data Center Analytics settings and data

Special procedures 61Hitachi Data Center Analytics Deployment Guide

Assigning a static IP address in the VMware vSphereapplication

An IP address is dynamically assigned to the server and the probe usingdynamic host configuration protocol at the time of deployment. If you want toassign a static IP address to the server and probe, follow these instructions.

Procedure

1. In the VMware vSphere application, select the server or probe that youhave deployed, and then click the Console tab in the right navigationpane.

2. Log on to the console as follows:• localhost logon: config• Password: megha!234

The system displays a notification to assign a static IP address.

***********************************************ASSIGN STATIC IP ADDRESS TO THE APPLIANCE***********************************************

Continue ? [yes/no] :3. Type yes, and then press Enter.4. Specify the requested details and type yes to apply the changes.

Continue ? [yes/no] : yesEnter IP Address: 192.168.20.156Enter NetMask: 255.255.255.10Enter Gateway: 192.168.0.45Enter Domain Name (Optional): Enter Name Server (Optional):Apply changes? [yes/no]:

ResultThe system assigns the required static IP addresses.

Verifying console timeProcedure

1. Log on to the Data Center Analytics server through an SSH client (likeputty) using the following credentials:• User: root• Password: megha.jeos

62 Special proceduresHitachi Data Center Analytics Deployment Guide

Note: If you install the RPM Manager on a standalone machine,then use the root credentials that you set for the same.

2. To verify the console time property, run the command date and verify thetime zone. The following time zone is a sample:

login as: [email protected]'s password:Last login: Mon Aug 10 08:46:21 2015 from 192.168.1.191[root@localhost ~]# dateMon Aug 10 12:00:32 UTC 2015[root@localhost ~]#

3. To verify the clock time property, run the command cat /etc/sysconfig/clock and verify the time zone. The following time zone is asample:

login as: [email protected]'s password:Last login: Mon Aug 10 08:46:21 2015 from 192.168.1.191[root@localhost ~]# dateMon Aug 10 12:00:32 UTC 2015[root@localhost ~] cat /etc/sysconfig/clockZONE="Etc/UTC"UTC=trueARC=false[root@localhost ~]#

4. If the output of the console and clock property is different, then makesure you change the property to the same time zone.

Setting the time zoneProcedure

1. Log on to the Data Center Analytics server through an SSH client (likeputty) using the following credentials:• User: root• Password: megha.jeos

Note: If you install the rpm on a standalone machine, then usethe root credentials that you set for the same.

2. Go to the /etc directory and rename the current localtime file usingthe following command:

mv localtime localtime.bak


3. Link the Etc/UTC time zone directory from /usr/share/zoneinfo tothe /etc/localtime directory:

ln-s /usr/share/zoneinfo/Etc/UTC localtime4. Run the command date.

It must contain the same time as the clock property.5. Update the time zone as Etc/UTC in /etc/sysconfig/clock.6. Run the command service crond stop.7. Stop the megha service using the command /usr/local/megha/bin/

megha-jetty.sh stop8. Verify the stopped status of megha service /usr/local/megha/bin/

megha-jetty.sh status9. Start the megha service using the command /usr/local/megha/bin/

megha-jetty.sh start10. Start the crond service using the command service crond start.

Adding a megha user for the Symmetrix arrayProcedure

1. Log on to the EMC Solutions Enabler Symmetrix CLI server.2. Go to the <Installation Directory>/symcli/bin directory.3. Verify that authentication is enabled using the following command:

symauth list4. Add the megha user with the monitor access using the following

command:

symauth -sid <SYMMETRIX ID> -file <fileName> commit

Create a new file with the content (assign user megha to role Monitor)and provide it as a file name in the add mega user with monitor accesscommand.

Uninstalling the RPM Manager file for server and probeTo uninstall the RPM Manager file, run the following command:

sh /usr/local/megha/uninstall.sh


Changing the opcode property file valueTo enable the collection of the following opcodes HGC, HHGC, LHGC, PWPC,and LWPC on the RAID Agent instance, change the Log=N to Log=Y in thefollowing configuration file on the RAID Agent instance: /opt/jp1pc/agtd/agent/<instance_name>/jpcagt.ini

After enabling the data collection, the Hitachi Enterprise Storage Probereceives the data after 6 hours.

Following are the sample entries in the /opt/jp1pc/agtd/agent/<instance_name>/jpcagt.ini configuration file. Change the Log=N toLog=Y.

[[HGC]]Description=Host Group ConfigurationLog=NCollection Interval=21600Collection Offset from Top of Minute=0LOGIF=-----------------------------------------------------[[HHGC]]Description=Host Per Host Group ConfigurationLog=NSync Collection With=Detail Records, HGCLOGIF=-----------------------------------------------------[[LHGC]]Description=LUN Per Host Group ConfigurationLog=NSync Collection With=Detail Records, HGCLOGIF=-----------------------------------------------------[[PWPC]]Description=Port-WWN Priority ConfigurationLog=NCollection Interval=3600Collection Offset from Top of Minute=0LOGIF=-----------------------------------------------------[[LWPC]]Description=LDEV-WWN Priority ConfigurationLog=NCollection Interval=3600Collection Offset from Top of Minute=0LOGIF=


Installing the HTTP proxy serverBefore you install the HTTP proxy server, make sure that Java 7 or later isinstalled on the Linux machine and the megha user exists on the Linuxmachine.

Procedure

1. Create the directory /usr/local/httpProxy.2. Unzip the httpProxy-<timestamp>.zip inside this directory.

For the httpProxy-<timestamp>.zip file, contact HDS support.3. Change ownership to megha using the command:

$ chown –R megha:megha /usr/local/httpProxy4. Give executable permission to the start and stop the scripts using the

command:

$ chmod +x /usr/local/httpProxy/bin/*5. Configure the default FTP settings by editing the following file:

/usr/local/httpProxy/conf/target/ftp.properties6. Configure user-specific settings by creating a file as

<user>.ftp.properties in the same directory (target) and writing yoursettings inside.

7. Start the http proxy server using the command:

/usr/local/httpProxy/bin/megha-jetty.sh start8. Check the status of the HTTP proxy server using the command:

/usr/local/httpProxy/bin/megha-jetty.sh status

Encrypting the CSV fileBefore uploading the CSV file you must encrypt it using the public key.

1. Contact HDS support for the public key.2. Log on to the probe console through an SSH client (like putty).3. Create the temporary folder in the /data folder and save the public key.4. Generate the random key using the following command:

openssl rand -base64 32 > randomkey.bin5. Encrypt the random key by using the public key, using the following

command:

openssl rsautl -encrypt -inkey public-key.pem -pubin -in randomkey.bin -out randomkey.bin.enc


6. Encrypt the CSV file by using the random key (not encrypted):

openssl enc -aes-256-cbc -salt -in ResourceDef1.xml -out ResourceDef1.enc -pass file:./randomkey.bin

7. Download the encrypted random file and encrypted CSV file to your localmachine.

8. Provide the encrypted random file and CSV file when adding the CiscoSAN Switch probe.

Determining the IP address of the probeProcedure

1. Log on to the probe console through an SSH client (like putty) using thefollowing credentials:

Localhost log on: configPassword: megha!234

The IP address assigned to the probe displays in the inet addr box.

login as: [email protected]'s password:nameserver=8.8.8.8nameserver=8.8.4.4********************************************************CURRENT NETWORK CONFIGURATION********************************************************DHCP IP Address: inet addr:192.168.156.82

The system displays a notification to assign a static IP address.

**************************************************ASSIGN STATIC IP ADDRESS TO THE APPLIANCE**************************************************

Continue ? [yes/no]: 2. You have two choices:

a. Type no, then press Enter.b. Assign the static IP address to the probe.

Next steps

Assign the static IP address to the probe.


Backing up and restoring Data Center Analytics settings anddata

You can use the backup and restore facility to import and export theconfiguration settings and database contents of the Data Center Analyticsserver and Analytics probe server.

Perform backup and restore operations in these cases:• Simple backup and restore of the Data Center Analytics and Analytics

probe server setup.• Performing a clean install without manually rebuilding the customized

features and losing historical content.• Migrating to a another server (for example in another data center or to a

more powerful server).

Before you begin• The modules that are backed up by this utility are controlled by the

properties file /usr/local/megha/conf/backup.properties• If you do not want to backup a particular module, then comment out the

entry in the /usr/local/megha/conf/backup.properties file (insert a #symbol at the beginning of the entry).

• If you add a new module to the /usr/local/megha/conf/backup.properties file, then you must add that module to the /usr/local/megha/conf/backup-mapping.properties file.

• The RAW_BACKUP_DATA setting in the backup.properties file is used toback up the db/backup folder where the raw data is stored. This entry iscommented-out by default. so the raw data is not included in the backup.If you want the raw data then uncomment the line (remove the # symbol).(The raw data is stored in a separate file from the regular data backup.).

• To restore the data you must have a fresh set up with settings thatmatching the original: brand, mode, version, release version, and machinetime zone.

Backing up the settings and data

Procedure

1. Log on to the Data Center Analytics server or Analytics probe serverusing an SSH client (like Putty).

2. Go to the following location: /usr/local/megha/bin.3. Run this command:

sh /usr/local/megha/bin/backupAndRestore.sh -o operation -z zip_file_path [-r raw_databackup_zip_path]


Where:• operation : backup or restore• zip_file_path : Location of the backup file• raw_databackup_zip_path : (Optional) Location of the raw data zip

file.

Examples

Backup : sh /usr/local/megha/bin/backupAndRestore -o backup -z /root/bakupDir

Restoring the settings and dataFor restoring the data you must have fresh setup of the Data Center Analytics

Procedure

1. Log on to the Data Center Analytics server or Analytics probe serverusing an SSH client (like Putty).

2. Copy the backup file (backup-hdca-server-8.0-16122112.zip) to adirectory (/root/zipDir) on this setup.

3. If you have created a backup of the raw data, do the same for thebackup file created for the raw data. For example, copy rawbackup-hdca-server-8.0-16122112.zip to /root/rawZipDir.

4. Go to the following location: /usr/local/megha/bin5. Run this command:

sh /usr/local/megha/bin/backupAndRestore -o restore - z /root/zipDir/backup-hdca-server-8.0-16122112.zip -r /root/rawZipDir/rawbackup-hdca-server-8.0-16122112.zip



7Troubleshooting

□ FTP connection problem on Data Center Analytics server

Troubleshooting 71Hitachi Data Center Analytics Deployment Guide

FTP connection problem on Data Center Analytics server

Example

java.net.ConnectException: Connection timed outat java.net.PlainSocketImpl.socketConnect(Native Method)at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)at java.net.Socket.connect(Socket.java:579)at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)at java.lang.reflect.Method.invoke(Method.java:606)at com.jscape.inet.util.n.a(Unknown Source)at com.jscape.inet.util.n.a(Unknown Source)at com.jscape.inet.util.n.a(Unknown Source)at com.jscape.inet.util.ConnectionParameters.createPlainSocket(Unknown Source)at com.jscape.inet.util.ConnectionParameters.createSocket(Unknown Source)at com.jscape.inet.ssh.transport.TransportClient.<init>(Unknown Source)at com.jscape.inet.ssh.SshConfiguration.createConnectionClient(Unknown Source)at com.jscape.inet.ssh.SshStandaloneConnector.openConnection(Unknown Source)... 4 more

Resolution

Verify that you can connect to the FTP server from the Data Center Analyticsserver console.

72 TroubleshootingHitachi Data Center Analytics Deployment Guide

Hitachi Data Center Analytics Deployment Guide

Hitachi Data Systems

Corporate Headquarters2845 Lafayette StreetSanta Clara, California 95050-2639U.S.A.www.hds.com

Regional Contact Information

Americas+1 408 970 [email protected]

Europe, Middle East, and Africa+44 (0) 1753 [email protected]

Asia Pacific+852 3189 [email protected]

Contact Uswww.hds.com/en-us/contact.html

MK-96HDCA001-09February 2017

http://www.hds.com

MAILTO:[email protected]

