hitachi data center analytics deployment guide · windows azure, windows powershell, ... retrieving...

Hitachi Data Center Analytics Deployment Guide

MK-96HDCA001-05 August 2016

© 2016 Hitachi, Ltd. All rights reserved.

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

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

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

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

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

authorized employees and other individuals to access relevant data; and 2. Verifying that data continues to be held, retrieved, deleted, or otherwise processed in

accordance with relevant laws.

Notice on Export Controls. The technical data and technology inherent in this Document may be subject to U.S. export control laws, including the U.S. Export Administration Act and its associated regulations, and may be subject to export or import regulations in other countries. Reader agrees to comply strictly with all such regulations and acknowledges that Reader has the responsibility to obtain licenses to export, re-export, or import the Document and any Compliant Products.

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

AIX, AS/400e, DB2, Domino, DS6000, DS8000, Enterprise Storage Server, eServer, FICON,

FlashCopy, IBM XIV, Lotus, MVS, OS/390, PowerPC, RS/6000, S/390, System z9, System z10, Tivoli,

z/OS, z9, z10, z13, z/VM, and z/VSE are registered trademarks or trademarks of International

Business Machines Corporation.

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

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

EXPORT CONTROLS - Licensee will comply fully with all applicable export laws and regulations of the United States and other countries, and Licensee shall not export, or allow the export or re-export of, the Software, API or Materials in violation of any such laws or regulations. By downloading or using the Software, API, or Materials, Licensee agrees to the foregoing and represents and warrants that Licensee is not located in, under the control of, or a national or resident of any embargoed or restricted country.

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

3 Hitachi Data Center Analytics Deployment Guide

Contents Preface ................................................................................................. 6

Intended audience ................................................................................................. 6

Product version ...................................................................................................... 6

Release notes ........................................................................................................ 6

Accessing product documentation ........................................................................... 6

Getting help........................................................................................................... 6

Comments ............................................................................................................. 7

Introduction .......................................................................................... 8

Deployment overview ............................................................................. 9

Deployment ........................................................................................................... 9

Distribution formats ............................................................................................. 10

Installing Data Center Analytics server .................................................. 11

Server installation prerequisites ............................................................................ 12

Desktop prerequisites ........................................................................................... 12

Installing the server on VMware vSphere Client ..................................................... 12

Installing the server on Microsoft Hyper-V Manager ............................................... 14

Adding the primary hard disk ............................................................................. 14

Adding the secondary hard disk ......................................................................... 14

Installing the server on a Linux machine ............................................................... 16

Configuring Data Center Analytics server ............................................... 18

Connect to the Data Center Analytics server .......................................................... 18

Registering the Data Center Analytics server license ............................................... 18

Creating an administrator account......................................................................... 19

Logging on to the Data Center Analytics server ...................................................... 19

Setting the time zone for the Data Center Analytics server ..................................... 19

Installing Data Center Analytics probe ................................................... 20


Probe installation prerequisites ............................................................................. 20

Probe port and firewall requirements .................................................................... 21

Desktop prerequisites ........................................................................................... 23

Installing the probe on the VMware vSphere Client ................................................ 23

Installing the probe on the Microsoft Hyper-V Manager .......................................... 24

Installing the probe on a Linux machine ................................................................ 25

Configuring Data Center Analytics probe ............................................... 27

Determining the IP address of the probe ............................................................... 27

Connecting to the probe ....................................................................................... 28

Registering the probe ........................................................................................... 28

Creating an administrator account for the probe appliance ..................................... 28

Logging on to the probe appliance ........................................................................ 29

Specifying user details for the probe appliance ...................................................... 29

Setting the time zone for the probe ....................................................................... 29

Configuring the FTP server ................................................................................... 29

Defining the data collection duration for the probe ................................................. 30

Adding probes in Data Center Analytics probe machine .......................... 31

Default collection and data export interval ............................................................. 31

Storage ............................................................................................................... 33

Adding Hitachi Adaptable Modular Storage (AMS) probe ...................................... 33

Adding Hitachi Enterprise Storage probe ............................................................ 34

Adding Hitachi Device Manager probe ................................................................ 37

Adding Hitachi HNAS probe ............................................................................... 38

Adding IBM XIV probe ....................................................................................... 38

Adding NetApp probe ........................................................................................ 39

Adding EMC VNX File probe ............................................................................... 45

Adding EMC VNX Block probe ............................................................................ 46

Adding EMC VMAX probe ................................................................................... 47

Hypervisor ........................................................................................................... 51

Adding VMware probe ....................................................................................... 51

Switches .............................................................................................................. 52


Adding Brocade Network Advisor probe .............................................................. 52

Adding Cisco DCNM probe ................................................................................. 52

Adding Cisco SAN Switch probe ......................................................................... 53

Retrieving diagnostic data from the probe ............................................................. 55

Installing Data Center Analytics Windows-based probe ........................... 56

Data collection methods ....................................................................................... 57

Windows-based probe installation prerequisites ..................................................... 60

Installing the Windows-based probe ...................................................................... 61

Configuring Data Center Analytics Windows-based probe ....................................... 62

Configuring the collection method ...................................................................... 62

Configuring the FTP or HTTPS server ................................................................. 65

Starting the Windows-based probe service ......................................................... 66

Special procedures ............................................................................... 67

Assigning a static IP address ................................................................................ 67

Assigning a static IP address in the VMware vSphere .......................................... 67

Verifying the console time .................................................................................... 68

Setting the console time zone ............................................................................... 69

Adding a megha user for the symmetrix array ....................................................... 70

Uninstalling the rpm file for server and probe ........................................................ 70

Changing the opcode property file value ................................................................ 70

Installing HTTP proxy server ................................................................................. 72

Encrypting the CVS file ......................................................................................... 72

Troubleshooting ................................................................................... 74

FTP connection problem on Data Center Analytics server ....................................... 74

Preface This document describes how to deploy Hitachi Data Center Analytics server and probe.

Intended audience

This document is intended for Infrastructure Administrators who manage complex data centers.

Product version

This document revision applies to Hitachi Data Center Analytics version 6.0 or later.

Release notes Read the release notes before installing and using this product. They may contain requirements or restrictions that are not fully described in this document or updates or corrections to this document.

Accessing product documentation

Product documentation is available on Hitachi Data Systems Support Connect: https://support.hds.com/en_us/documents.html. Check this site for the most current documentation, including important updates that may have been made after the release of the product.

Getting help

The Hitachi Data Systems Support Center staffs are available 24 hours a day, seven days a week. If you need technical support, log on to the Hitachi Data Systems Portal for contact information: https://portal.hds.com.

Before calling the Hitachi Data Systems Support Center, please provide as much information about the problem as possible, including:

• The circumstances surrounding the error or failure.

• The exact content of any error messages displayed on the host systems.

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

https://portal.hds.com/


Comments

Please send us your comments on this document to [email protected]. Include the document title and number, including the revision level (for example, -07), and refer to specific sections and paragraphs whenever possible. All comments become the property of Hitachi Data Systems Corporation.

Thank you!

mailto:[email protected]


Introduction Hitachi Data Center Analytics (HDCA) provides visibility into storage infrastructure using sophisticated analytics. The product uses various methods to collect metrics, such as IOPS, transfers, and latency, from target devices, and does so without changing data or affecting performance. These metrics are collected by Data Center Analytics probe at regular time periods, and then periodically transferred to the Data Center Analytics server for processing. Data Center Analytics builds reports from this processed data using built-in reports and interactive charts. The reports give you a view into your data center infrastructure to monitor its health and to identify areas of actual and potential problems.

Data Center Analytics can collect metrics from target devices such as storage systems, servers, hypervisors, and switches.

The product has two components:

Data Center Analytics Server: Consolidates and compares the collected data and creates reports.

Data Center Analytics Probe: Collects the performance and configuration data from target devices.


Deployment overview

Deployment

The following workflow shows the high-level tasks for deploying Hitachi Data Center Analytics:

Verify that the host on which you plan to install the Data Center Analytics server 1.and probe meets the minimum system requirements:

• See Server installation prerequisites

• See Probe installation prerequisites

Install and configure the Hitachi Data Center Analytics server: 2.

• See Installing Data Center Analytics server

• See Configuring Data Center Analytics server

Install and configure Hitachi Data Center Analytics probe: 3.

• See Installing Data Center Analytics probe

• See Configuring Data Center Analytics probe


Distribution formats • The Hitachi Data Center Analytics Server and Probe installer is available in the

following formats:

• OVA file This is the Open Virtualization Format (OVF) package which allows the Data Center Analytics server to be deployed on VMware infrastructure. The Data Center Analytics server becomes a (VM) in the environment with all the required components installed.

• VHD file This file is similar to the OVA file but it is for a Microsoft Hyper-V environment. Install on a host running Microsoft Windows Server 8.

• RPM® file This file can be deployed on a standalone physical machine that is running the Linux® operating system.

• The Hitachi Data Center Analytics Windows probe is available in .exe format.


Installing Data Center Analytics server You can install the Data Center Analytics server on any of the following systems:

• VMware vSphere Client using OVA

• Hyper-V Manager using VHD

• Linux using rpm

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


Server installation prerequisites

Prerequisites

Formats

OVA (for VMware vSphere Client)

VHD ( for Hyper-V Manager)

RPM for Linux

RAM Minimum: 4 GB

Recommended: 8 GB

Minimum: 4 GB

Recommended: 8 GB

Minimum: 4 GB

Recommended: 8 GB

Storage Minimum: 150 GB Minimum: 150 GB Minimum: 150 GB

Operating systems/Platform

vSphere Client on ESX Server 3.5 or later

Win2k8R2 and Win2k12 (both 64 -bit)

Linux

RHEL 6.1 (64-bit)

CentOS 6.5 (64-bit)

Desktop prerequisites

Data Center Analytics server

Source IP address

Target IP address

Default port

Protocol

User Desktop Server IP address

8443 TCP

22 TCP

Installing the server on VMware vSphere Client

You can deploy the Data Center Analytics server using the Open Virtualization Format (OVF) package on a VMware infrastructure.

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

Procedure

Open the vSphere Client application. 1.

From the File > Deploy OVF Template. 2.

On the Deploy OVF Template window, click Browse, navigate to the directory 3.that contains the OVA file, select it, and click Next.

On the OVF Template Details window, verify the details and click Next. 4.

On the Name and Location window, type the following details and click Next. 5.

• Name: A name for the Hitachi Data Center Analytics server. The server is identified by this name


• Inventory location:The inventory in the vMware application to add the Data Center Analytics server

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

On the Disk Format window, select the appropriate disk format, and then click 7.Next:

• Thick Provision Lazy Zeroed: The system allocates the required space at the time of disk creation. Each disk block is zeroed-out only after it is accessed for the first time by VM.

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

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

Click Next, and then click Finish to complete the deployment. 8.

Configure the Data Center Analytics server next. See Configuring Data Center 9.Analytics server.


Installing the server on Microsoft Hyper-V Manager

To install the Data Center Analytics server on Hyper-V Manager using Virtual Hard Disk (VHD), create a VM first, and then add the primary and secondary hard disk.

Adding the primary hard disk

Procedure

Right-click the Hyper-V machine, select New > Virtual Machine, and then click 1.Next.

In the Name field, type the name of the virtual machine, and then click Next. 2.

In the Memory field, type the required memory, and then click Next. 3.

Note: The minimum memory for VHD is 4 GB and the recommended memory is 8 GB.

Configure network, and click Next. 4.

Click Use an existing virtual hard disk, and click browse to navigate to and 5.select the primary hard disk.

Click Finish. 6.

Adding the secondary hard disk

Procedure

Right-click the VM that you created for installing the Data Center Analytics server, 1.and click Settings.

Select IDE Controller 0 and Hard Drive, and then click Add. 2.

A new hard drive is added.

Select the new hard drive, and select 1 from the Location list. 3.


Click Browse to navigate to the secondary hard drive folder, and select the drive. 4.

Click Apply, and then click OK. 5.

Right-click the new VM and start it. 6.



Installing the server on a Linux machine

You can use the rpm file to install the Data Center Analytics server on a Linux machine.

Prerequisites

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

• Ensure that the console and clock properties are set to the same time zone, and change them if they are not.To verify the time zone, see Verifying the console time zone and To change the time zone, see Setting the console time zone.

• Yum/rpm dependencies:

• Perl • gcc

• java-1.7.0-openjdk-1.7.0.95-2.6.4.0.el6_7

• samba

• expect • openssl-devel

• ftp

• CPAN dependencies:

• IO::Pty • Date::Gregorian

• Date::Calc • Log::Log4perl

• Net::OpenSSH • Module::Implementation

• DateTime • Log::Dispatch::FileRotate

• DateTime::Format::Strptime • Sys::RunAlone

• XML::Simple • Net::SSH::Perl


Procedure

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

Run the following command: 2.

rpm -ivh <Data Center Analytics Server rpm>

Run the Data Center Analytics server configuration script: 3.

sh /usr/local/megha_installer/config.sh

The following message appears: Do you want Japanese Language support? Type 4.N, currently we do not support the Japanese language.

Provide the directory path to store the application data. By default, it is stored in 5.the /data folder.

Change the default directory path as necessary. 6.

Press Enter. The default port is assigned to the Data Center Analytics server. 7.

Note: The default ports are 8080 for normal mode (http) and 8443 for secure mode (https). If the default port is busy, then the system notifies you that you must type an alternative port number. Type the appropriate port number.

If the Data Center Analytics server is running, run the appropriate command: 8.

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

Note: The URL to access Data Center Analytics server is provided at the end of the installation. Add the rule in your firewall to bypass the port numbers and opens the UI for the server.



Configuring Data Center Analytics server To configure Data Center Analytics server, perform the following task:

□ Connect to the Data Center Analytics server

□ Register the Data Center Analytics server license

□ Creating an administrator account

□ Logging on to the Data Center Analytics server

□ Setting the time zone for the Data Center Analytics server

Connect to the Data Center Analytics server

Procedure

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

Note: The default ports for Data Center Analytics server are: for http:// 8080 and https:// 8443

Read the License Agreement and accept it. 2.

Registering the Data Center Analytics server license

Procedure

Contact HDS support (See, Getting help) for the Data Center Analytics license. 1.

On the Upload License window, click Choose File. 2.

Browse to the license file and click Submit to register the server. 3.


Creating an administrator account

Procedure

Set the password for the built-in administrator user. 1.

Note: The username of the built-in administrator user is admin.

On the Create Administrator Account window, type the password and locale. 2.

The current version of Data Center Analytics supports only the English locale.

Click Submit. 3.

Logging on to the Data Center Analytics server

Type the user name and password to log on to the Data Center Analytics server.

Setting the time zone for the Data Center Analytics server

The time zone of the Data Center Analytics server must be set at the time of deployment. Reports display data in the set time zone.

For example, if the server is in the IST time zone, one storage system is in the Eastern time zone and another is in the Central America time zone, the reports of both storage systems display the IST time zone.

To change the time zone to match with that of the storage system, select the appropriate time zone in the Select Time zone window.

Note: This time zone applies to each storage system.


Installing Data Center Analytics probe You can install the Data Center Analytics probe on these systems:

• VMware vSphere Client using OVA

• Hyper-V Manager using VHD

• Linux machine using rpm

Installing Data Center Analytics probe in VMware vSphere Client is the best practice.

Probe installation prerequisites

Prerequisites Description

Operating systems OVA and VHD deployment: VMware vSphere Client on ESX Server 3.5 or later.

RPM deployment: Linux

RHEL 6.1(64-bit)

CentOS 6.2 (64-bit).

RAM Minimum: 2 GB and Recommended: 4 GB

Storage 50 GB


Probe port and firewall requirements The target device must allow the incoming connection from the Data Center Analytics probes for the following default ports.

Probe name Collection method

Source IP address

Target IP address

Default port

Protocol

Notes

Storage

AMS SNM2API Probe machine

AMS Controller 2000 TCP

Hitachi Enterprise Storage

RAID Agent Probe machine

RAID Agent Server

24221 HTTP

24222 HTTPS

Hitachi Device Manager API

Probe machine

Hitachi Device Manager Server

2001 HTTP

2443 HTTPS

HNAS RUSC/CLI Probe machine HNAS SMU 22 SSH

IBM XIV xcli Probe machine

XIV Storage System Management IP

7778 TCP

CLI installer ("xivcli-3.0.1-build3-linux32.tar") is available from the IBM support site, deployed on the probe.

NetApp ONTAP API Probe machine NetApp Filer 443 HTTPS

VMAX

Unisphere REST API

Probe machine

Unisphere Server 8443 TCP

SYMCLI Probe machine

Solution Enabler 2707 TCP

VNX Block naviseccli Probe machine

VNX Storage Processor A & B

443 HTTPS

The NAVCLI are executed locally on probe


Probe name Collection method

Source IP address

Target IP address

Default port

Protocol

Notes

80 HTTP

machine which internally makes HTTP/S calls to the VNX Storage

VNX File VNX Control Station CLI

Probe machine VNX Storage 22 SSH

Hypervisors

VMware vCenter API Probe machine

vCenter Server/ESX Host/ESXi Host

443 TCP

Windows and Hyper V Host

WMI

Windows Probe machine

Windows Host/ / Hyper-v

135

TCP

Perfmon 135 and 445

SCOM SCOM server 5723, 5724, and 51905

SCCM SCCM server 1433

FC Switches

Brocade Network Advisor

BNA (REST API)

Probe machine BNA server 80 HTTP

Cisco DCNM DCNM (Web Services)

Probe machine

DCNM server

80 HTTP

443 HTTPS

Cisco SAN Switch

Cisco Switch CLI

Probe machine

Cisco FC Switch 22 SHH

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


Desktop prerequisites

Data Center Analytics probe

Source IP address

Target IP address

Default port

Protocol Notes

User desktop

Server IP address

8443 TCP

22 TCP Needed for SSH to the probe VM

Installing the probe on the VMware vSphere Client

You can deploy the probe using the Open Virtualization Format (OVF) package on a VMware infrastructure.

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

Procedure

Open the vSphere Client application. 1.

Select the File > Deploy OVF Template. 2.

On the Deploy OVF Template window, click Browse, navigate to the directory 3.that contains the OVA file, select it, and click Next.

On the OVF Template Details window, verify the details and click Next. 4.

On the Name and Location window, type the following details and click Next: 5.

• Name: A name for the Hitachi Data Center Analytics probe. The probe is identified by this name.

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

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

On the Disk Format window, select the appropriate disk format, and then click 7.Next:

• Thick Provision Lazy Zeroed: The system allocates the required space at the time of disk creation. Each disk block is zeroed-out only after it is accessed for the first time by VM.

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

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


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

Configure the Data Center Analytics probe next. See Configuring Hitachi Data 9.Center Analytics probe.

Installing the probe on the Microsoft Hyper-V Manager

Procedure

Right-click the Hyper-V machine, select New > Virtual Machine, and then click 1.Next.

In the Name field, type the name of a virtual machine, and then click Next. 2.

In the Memory field, type the required memory, and then click Next. 3.

Note: The minimum memory for VHD is 4 GB and the recommended memory is 8 GB.

In the Configure Networking section, configure the network, and then click 4.Next.

In the Connect Virtual Hard Disk section, click Use an existing virtual hard 5.disk, and then click Browse to navigate to and select the disk.

Click Finish. 6.

Right-click the new VM and start it. 7.



Installing the probe on a Linux machine Verify the following prerequisites on the machine, before you start installing the Data Center Analytics probe using rpm.

Prerequisites

• You must congigure the firewall rule to allow incoming connection on 80, 8080, 8443 TCP ports.

• RHEL OS version, Red Hat Enterprise Linux Server release 6.1 (Santiago)

• Data Center Analytics Probe rpm build.

Yum/rpm dependencies

• Perl • gcc

• java-1.7.0-openjdk-1.7.0.95-2.6.4.0.el6_7

• samba

• expect • openssl-devel

• ftp

CPAN dependencies

• IO::Pty • Date::Gregorian

• Date::Calc • Log::Log4perl

• Net::OpenSSH • Module::Implementation

• DateTime • Log::Dispatch::FileRotate

• DateTime::Format::Strptime • Sys::RunAlone

• XML::Simple • Net::SSH::Perl


Procedure

Copy the Data Center Analytics probe .rpm file to a folder on the Linux machine. 1.

Run the following command: 2.

rpm -ivh < Data Center Analytics Probe rpm>

Run the probe configuration script: 3.

sh /usr/local/megha_installer/config.sh

The following message appears; Do you want Japanese Language support? Type 4.N, currently we do not support the Japanese language.

Provide the directory path to store application data. By default, it is stored at 5./data.

Change the default directory path as necessary, and press Enter. 6.

The default port is assigned to the probe.

Note: The default ports are: for http:// 8080 and https:// 8443. If the default port is busy, then the system notifies you that you must type an alternative port number. Type the appropriate port number.

Depending on if the probe is running, run the appropriate command: 7.

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

Note The URL to access Data Center Analytics server is provided at the end of the installation. Add the rule in your firewall to bypass the port numbers and opens the UI for the probe.



Configuring Data Center Analytics probe Data Center Analytics probe configuration is a one-time operation that sets up the Data Center Analytics probe. You can access the console using either the VMware vSphere window or the Microsoft Hyper-V window.

Make sure that you install the Data Center Analytics server, before you install the Data Center Analytics probe. The Data Center Analytics server’s IP address is required in the configuration process of the Data Center Analytics probe.

The root user log on is not available on the vSphere console and Hyper-V console. You can log on through SSH client (like putty) using the following credentials: User name: root Password: app.jeos

Do not change the time zone setting manually after you log on to an SSH client like putty. The default time zone of the Data Center Analytics probe is UTC.

You can configure the Data Center Analytics probe application time zone from the UI with any appropriate value.

Determining the IP address of the probe Procedure

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

Localhost log on: config Password: megha!234 The IP address assigned to the probe displays in the inet addr box.

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


Type no, and then press Enter. 2.

You can also assign the static IP address to the probe. See Assigning static IP 3.address to the probe.

Connecting to the probe

Procedure

In the browser, type the probe URL https://< Data Center Analytics Probe 1.IP Address>:8443, and press Enter.

Read and accept the License Agreement. 2.

The Upload License window appears.

Registering the probe

Procedure

In the Upload License window, click Browse. 1.

Browse to the license file, and click Submit to register the probe. 2.

The Create Administrator Account window appears.

Creating an administrator account for the probe appliance

Create a user account with administrator privileges to manage the probe.

Procedure

On the Create Administrator Account window, specify the following details: 1.

• User ID and Password.

• First name, last name, and email of the user.

• Locale: Data Center Analytics probe is available in two languages – US English and Japanese.

• Group: Select Admin to create the administrator account.

Click Submit. 2.


Logging on to the probe appliance

Type the defined user ID and password to log on to the Data Center Analytics probe.

When you log on for the first time, the Basic Information window appears.

Specifying user details for the probe appliance

Procedure

On the Basic Information window, type the following details: 1.

• Customer Name: The customer name displays by default, you cannot edit the customer name. This field displays the name in the license.

• Administrator Contact Name and the Administrator Contact Email: Administrator’s name and email address.

• Technical Contact Name and Technical Contact Email: Resource (generally administrator) to notify about technical problems.

Click Next. 2.

The Select Time zone window appears.

Setting the time zone for the probe

Select the time zone where Data Center Analytics probe appliance is deployed, and then click Next.

Configuring the FTP server

Procedure

On the FTP Information window, complete the following information: 1.

• FTP Method: Select the SFTP method.

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

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

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

• Password: Type the user password as meghadata123

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

• Proxy: Select Proxy to provide the proxy details.


Click Next. 2.

Defining the data collection duration for the probe

Data collection duration is defined by the license.


Adding probes in Data Center Analytics probe machine

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

Default collection and data export interval

The following table lists the default data collection and default data export interval in minutes:

Probes Default data collection interval (Minutes)

Default data export time periods (Minutes)

Storage

Hitachi Enterprise Storage

Collection interval depends on storage system resource. The default values are in the Hitachi Enterprise Storage probe section.

5

HNAS 1 15

VNX Block 1 15

VNX File 1 15

Hitachi AMS 1 15

IBM XIV 1 15

NetApp 1 15

EMC VMAX 5 15

Hypervisor

VMware 1 15

Windows 1 15

FC Switches

Brocade Network Advisor

5 15


Probes Default data collection interval (Minutes)

Default data export time periods (Minutes)

Cisco DCNM 5 15

Cisco SAN Switch 5 15


Storage

Adding Hitachi Adaptable Modular Storage (AMS) probe

The AMS probe collects data through the HUS storage controllers.

Procedure

On the Home page, click Add Probe. 1.

On the Add Probe window, from the Probes drop-down list, select AMS. 2.

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

• AMS Storage Name: Name of the HUS storage system for which the probe is added. This must not be the same as the storage name that is defined in your environment.

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

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

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

Note: If the user authentication for AMS storage is disabled, then you must type a dummy user name and password because these two fields are mandatory for adding the AMS probe.

On the Validation window, click Next, and then click OK. 4.

On the Status window, in Action, click Start to start collecting data. 5.


Adding Hitachi Enterprise Storage probe

The Hitachi Enterprise Storage probe collects the required metrics from Hitachi Enterprise (RAID) Storage Systems such as VSP Gx00 models, HUS VM, and USP V.

The steps to configure the Hitachi Enterprise Storage probe are as follows:

Configure the probe to use the RAID Agent. 1.

Specify the collection interval for the RAID Agent. 2.

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

Prerequisites

• Make sure that the RAID Agent is installed as part of Hitachi Tuning Manager installation or as a standalone.

Note: You can install the standalone RAID Agent on independent server or on the Data Center Analytics probe machine.

• Verify that the storage instance is added in the RAID Agent and data collection is started for that instance. Make sure that you add the storage instance using command device.

• If you want to monitor a logical device that is not mapped to any port, then verify if the following property is set to Yes: UNASSIGN_VOL=Y. The UNASSIGN_VOL=Yproperty is in the file jpcagt.ini, at the following location: <Installation directory of Raid Agent>/jp1pc/agtd/agent/<Instance Name> on the RAID Agent server.

• The minimum supported RAID Agent version is 8.4.1-00

• To collect the data from following resources hbaPort, raidOwner, raidPortWWN, raidLU, and raidHG enable the data collection of the following opcode HGC, HHGC, and LHGC on the RAID Agent instance. To enable data collection of opcode, see Changing value of the opcode property file.

Prerequisites for Hitachi Device Manager

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

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

• The Data Center Analytics probe machine must be able to access the Hitachi Device Manager.


• Hitachi Device Manager Version must be 7.5 or later.

Procedure


On the Add Probe window, from the Probes drop-down list, select Hitachi 2.Enterprise Storage probe.

In the Provide RAID Agent Details section, type the following details, and then 3.click Next:

• Probe Name: Name of the probe. The probe name must contain a minimum of 4 alphanumeric characters. Example: HESP53076 .

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

• Connection Type: Choose HTTP or HTTPS.

• RAID Agent IP Address: IP address of the machine on which the RAID Agent is installed. This is usually the same as the Hitachi Tuning Manager server IP address.

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

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

• RAID Agent Port: Port number used by the RAID Agent on the RAID Agent host. Default port number: 24221-HTTP 24222-HTTPS

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

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

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

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


(Optionl) Select No to skip this step. 5.

If you select No, then the Hitachi Device Manager Section is unavailable, click 6.Next, the success message appears, that the Hitachi Enterprise Storage probe is successfully added.

(Optional) On the Provide Hitachi Device Manager details window, select Yes 7.to configure the Hitachi Device Manager to collect configuration metrics from Hitachi Device Manager.

If you select Yes, then the Hitachi Device Manager Section is enabled, type the 8.following details, and then click Next:

• Connection Type: Choose HTTP or HTTPS

• IP Address: IP address of the Hitachi Device Manager (HDvM) server for accessing the XML API.

• Example, http://<Device Manager IP address Address>:<Port>/service/StorageManager

• Port: Port number of the Hitachi Device Manager Default port numbers: 2001-HTTP 2443-HTTPS

• Username/Password: User name and password of the Hitachi Device Manager.

On the Validation window, click Next, and then OK. 9.



Adding Hitachi Device Manager probe The Hitachi Device Manager (HDvM) probe collects storage capacity and host information related to configuration data of the Hitachi storage systems that use the Hitachi Device Manager (HDvM) API.

Prerequisites

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

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

• The Data Center Analytics probe machine must be able to access the Hitachi Device Manager.

• Hitachi Device Manager Version must be 7.5 or later.

Procedure


On the Add Probe window, from the Probes drop-down list, select Hitachi 2.Device Manager.

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

• Connection Type: Choose HTTP or HTTPS.

• IP Address: IP address of the Hitachi Device Manager (HDvM) server.

• Default port number: 2001-HTTP 2443-HTTPS

• User name and Password: User name and password with at least read-only privileges of the Hitachi Device Manager (HDvM) server.




Adding Hitachi HNAS probe

The Hitachi HNAS probe collects data from Hitachi HNAS (Hitachi NAS platform) storage systems.

Procedure


On the Add Probe window, from the Probes drop-down list, select Hitachi 2.HNAS.

In the Probes Details section, type the following details, and the click Next: 3.

• HNAS SMU IP: The IP address of the HNAS System Management Unit (SMU).

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

On the Validation window, click Next. 4.

On the Choose Server window, select the server, and then click Next. 5.

The Choose Server window list all the server associated with the SMU.



Adding IBM XIV probe IBM XIV probe collects configuration and performance data from IBM XIV storage systems.

Prerequisites

• XIV CLI: Download from the IBM support site and save it in Data Center Analytics probe appliance in the /opt directory.

Procedure

Log on to the Data Center Analytics probe console through an SSH client (like 1.putty) using the following credentials:

• Host: <IP address of Data Center Analytics probe>

• User: root

• Password: app.jeos

Navigate to the /opt directory: cd /opt 2.

Copy the XIV CLI package in the /opt directory (package name must be similar to 3.the following: xivcli-3.0.1-build3-linux32.tar)


Extract the package at the /opt location using command: tar –xvf <package 4.name>

Verify the following after extracting the package at /opt location. 5.

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

b. If the structure is not as mentioned, then check if it contains the binary file. For example, xivcli-3.0.1-build3-linux32.bin.

c. Install the required package using the binary file. d. To install the package, go to directory that contains the binary file and run the

following command: ./binary file For example, ./xivcli-3.0.1-build3-linux32.bin

e. System prompts for a location. Provide the installation directory location as /opt/XIVGUI.


On the Add Probe window, from the Probes drop-down list, select XIV. 7.

In the Probes Details section, type the following details, and the click Next: 8.

• Storage System IP Address: IP address of the target IBM XIV storage system

• User name: User name of the storage system. Ensure that the user has the minimum read-only permissions to collect configuration and performance data.

• Password: Password of the user.



Adding NetApp probe The NetApp probe collects configuration and performance data from NetApp storage systems using the ONTAP API.

Prerequisites

• Ensure that you have a user (read-only privileges) available on the NetApp storage system with the appropriate role to collect configuration and performance data. Data Center Analytics probe supports 7-mode and C-mode types of NetApp storage systems. The procedure for creating users depends on the target of the storage system type.

To create a user for 7-mode, see Creating user for NetApp 7-mode and to create a user for C-mode, see Creating user for NetApp C-mode.

• Configure security settings for NetApp storage systems. See Configuring security setting for NetApp storage systems.


Adding the Netapp probe in the Data Center Analytics probe

Procedure


On the Add Probe window, from the Probes drop-down list, select NetApp. 2.

In the Probe Details section, type the following details, and then click Next: 3.

NetApp Server: IP address of NetApp server. 4.

• Username and Password: Type the user name and password that you have created.



Creating a user for NetApp 7-mode Log on to the NetApp command line. 1.

Add a role: 2.

Run the following command for NetApp storage system version 7.3.6:

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, login-ssh,cli-fcp

For example:

Run the following command for NetApp storage system version 8.0.1:

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,login-ssh,cli-fcp

For example:

Add a group: 3.

useradmin group add <Group Name> -r RoleName For example:

Add a user: 4.

useradmin user add User_Name -g Group_Name For example:

Type the password. 5.

Continue with Adding NetApp probe. 6.


Creating a user for NetApp C-mode Log on to the target NetApp storage system using NetApp OnCommand System 1.

Manager.

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

In the Users pane, click Add and type details in the Add User window: 3.

• User Name: Type any valid user name.

• Password and Confirm Password: Type the user password and confirm it.

In the User login methods section, click Add. 4.

In the Application column, select ontapi. 5.


In the Role column, select readonly, and then click Ok. 6.

Note: By default, the password is selected in the Authentication column.

Click Add. 7.

The new user is added. You can use this user to collect configuration and performance data.

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

The 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

After the following condition exist: Case 1: On the NetApp storage system, TLS is enabled (most preferred)

• 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 This line must be uncommented and must have ‘RSA keySize < 1024’

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

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

• tls.enable=OFF

• sslv3.enable=ON

• CertificateKey length=1024 or 2048


• jdk.certpath.disabledAlgorithms=MD2, MD5, RSA keySize < 1024 This line must be uncommented and have RSA keySize < 1024


• jdk.tls.disabledAlgorithms=SSLv3, MD5withRSA, DH keySize < 768 This line must be commented (comment-out this line if currently uncommented). Basically, this enables SSLv3 to be used.

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

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

If it is not possible (that is, Length of Certificate Key 512 or lower)

• Either tls.enable=ON or sslv3.enable=ON


• jdk.certpath.disabledAlgorithms=MD2, MD5, RSA keySize < 512 This line must be uncommented and must have ‘RSA keySize < 512 or the present key length

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


Adding EMC VNX File probe The EMC VNX file probe collects the NAS configuration and NAS performance data from the VNX file storage.

Procedure


On the Add Probe window, from the Probes drop-down list, select VNX File. 2.

On the VNX File Probe Details window, type the following details, and then 3.click Next:

• IP Address: IP address of VNX File control station.

• User name: User name to log on to the VNX file storage. Ensure that the this user has at least an operator role. For this, verify that the nasadmin operator role and CLI access allowed options are selected for the user.

• Password: Password to log on to the VNX File storage.




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

Prerequisites

The VNX Block Storage system user with minimum operator’s role.

Enable the Statistics logging to collect performance data.

Caution: Statistics logging affects storage-system performance, so you may want to leave it off unless you want to monitor performance.

Install NaviCLI on the Hitachi Data center Analytics probe machine.

To install the NaviCLI, perform the following,

Log on to the probe appliance using SSH client like putty, with following 1.credentials:

User name: root

Password: app.jeos

Copy NaviCLI package on the Data Center Analytics probe machine. 2.

Run the following command: 3.# rpm -ivh NaviCLI-Linux-64-x86-en_US-7.33.8.1.19-1.x86_64.rpm

Note: The NaviCLI executable file must be at the following location: /opt/Navisphere/bin/naviseccli

Procedure


On the Add Probe window, from the Probes drop-down list, select VNX Block. 2.

On the VNX Block Probe Details window, type the following details, and then 3.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.

• User name: User name of the user with minimum operator role to logon to the VNX Block storage.

• Password: Password of the user name.

On the Validation window, click Next, and then OK. 4.



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

Prerequisites

Configuration in target environment

• EMC Unisphere for VMAX: A machine with EMC Unisphere for VMAX (1.6.2.4, 8.1.0.3, and 8.2.0.5) installed, monitoring target storage systems.

• EMC Solutions Enabler Symmetrix CLI: A machine (could be the same as above for EMC Unisphere for VMAX or different) with EMC Solutions Enabler Symmetrix CLI (7.6.2.26, 8.0.3, 8.2.0.1 and 8.1.0.0) installed, monitoring all the target storage systems for which probe must be added.

Configuration on the probe

• Install EMC Solutions Enabler Symmetrix CLI.

a) Log on to the probe console using the following information:

User name: root

Password: app.jeos.

b) Copy the EMC Solutions Enabler Symmetrix CLI tar.

Note: We recommend that you install the same version of EMC Solutions Enabler Symmetrix CLI, as installed in the target environment.

c) Extract tar: tar -zxvf se<version>-Linux-i386-SMI.tar.gz

d) Install EMC Solutions Enabler Symmetrix CLI: ./se<version>_install.sh -install -all

• Configure environment variable entry in netcnfg file: To collect data from target storage systems using EMC Solutions Enabler Symmetrix CLI , edit the netcnfg file.

a) Log on to Data Center Analytics probe appliance (Username: root Password: app.jeos).

b) Verify the security_level property on the target machine where EMC Solutions Enabler Symmetrix CLI server is installed. You can verify the security_level in the daemon_options file at the following location <Installation Directory>\EMC\SYMAPI\config.

Case 1: The security_level property is NONSECURE or ANY

a) Edit the netcnfg file: vi /var/symapi/config/netcnfg


b) 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 Solutions Enabler Symmetrix CLI is installed in target environment.

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

Default port number 2707-TCP for SYMCLI 8443 TCP for Unisphere REST API

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

c) Go to /etc/hosts file, and add an entry for the target SYMAPI server: <SYMAPI SERVER IP ADDRESS> <SYMAPI SERVER HOST NAME> eg: 10.10.10.10 WIN-PC1 Note: If you are using the DNS server, then make sure you configure it on the probe. To avoid making changes in /etc/hosts file.

Case 2: The security_level property is SECURE

a) Edit the netcnfg file: vi /var/symapi/config/netcnfg

b) At the end of the file, add the following:

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

< Server's Nodname > = Server’s host name where EMC Solutions Enabler Symmetrix CLI is installed in target environment.

<IP Address> = IP address of the machine where EMC Solutions Enabler Symmetrix CLI is installed.

Default port number: 27070 -TCP

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

c) Go to : /etc/hosts file, and add an entry for the target SYMAPI server: <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 make sure you configure it on the probe appliance to avoid making changes in the /etc/hosts file.

d) Save the file.


Note: If the authentication is enabled for Symmetrix arrays, then add a megha user with monitor role for each Symmetrix array. To add a megha user, see Adding a megha user for the Symmetrix array.

Procedure


On the Add Probe window, from the Probes drop-down list, select VMAX. 2.

On the VMAX Unisphere Details window, click Add Unisphere. 3.

On the Add VMAX Unisphere window, type the following details, and then click 4.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.

On the Managed VMAX Storage System window, select the VMAX storage 5.systems, type the Sym CLI Host IP address, and then click Finish.


Managing VMAX probe

After you add VMAX probe, do these actions:

• Adding VMAX probe for already added EMC Unisphere for VMAX

• Editing details of EMC Unisphere for VMAX

Adding VMAX probe for an already added EMC Unisphere for VMAX

Procedure

On the Home Page, click Add Probe. 1.

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

On the Managed VMAX Storage System window, select the VMAX storage 3.systems for which you want to add VMAX probe and enter the Sym CLI Host IP


address where EMC Solutions Enabler Symmetrix CLI is installed in the target environment.

Click Finish, and then click OK. 4.

Editing details of EMC Unisphere for VMAX

The EMC Unisphere for EMC Unisphere for VMAX administrator can change the password or user name in the Data Center Analytics probe appliance to continue data collection.

Procedure

On the Status window, stop the VMAX probe. 1.

Click the Edit link corresponding to the EMC Unisphere for VMAX. 2.

On the Edit VMAX Unisphere Details window, edit the user name or password 3.of the EMC Unisphere for VMAX, and then click Next.



Hypervisor

Adding VMware probe VMware probe collects data from the VMware vCenter Server Appliance and standalone ESX server.

Procedure


On the Add Probe window, from the Probes drop-down list, select the VMware. 2.

On the Probe Details section, type the following details, and then click Next: 3.

• vCenter Server: Host name or IP address of the VMware vCenter Server Appliance or ESX host IP address.

• User name: Any user having access to VMware vCenter Server. Read-only privileges are sufficient.

• Password: Password of the vCenter user.




Switches

Adding Brocade Network Advisor probe

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

Prerequisites

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

• BNA Professional plus or BNA Enterprise must be installed.

Procedure


On the Add Probe window, from the Probes drop-down list, select Brocade FC 2.Switch (BNA).

On the Probe Details window, type the following details, and then click Next. 3.

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

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

On the Validation window, Click Next, and then click OK. 4.


Adding Cisco DCNM probe

This probe collects data from Cisco Data Center Network Manager a management system for the Cisco Unified Fabric.

Note: It is not recommend adding Same Cisco SAN switches using both Cisco DCNM probe and Cisco SAN probe.

Procedure


On the Add Probe window, from the Probes drop-down list, select Cisco DCNM. 2.

On the Probe Details window, type the following details and click Next: 3.

• Cisco DCNM IP: IP address of DCNM.


• DCNM Webservice Port: Type the port number to access web service on the DCNM server. Note: In some environments, the port number is optional: For example, http://<dcnmip>:80/sanService, here the 80 is port number. If you have a problem adding the probe, check the web service port.

• Protocol : Select HTTP or HTTPS.

• User name and password of DCNM

• Default Ports: 80 – HTTP 443 - HTTPS

On the Validation window, Click Next, and then click OK. 4.


Adding Cisco SAN Switch probe

This probe collects data from Cisco SAN switches.

Note: It is not recommend adding Same Cisco SAN switches using both Cisco DCNM probe and Cisco SAN probe.

Procedure


On the Add Probe window, from the Probes drop-down list, select Cisco SAN 2.Switch.

On the Cisco SAN Switch Details window, in Add Switch Details, type the 3.following details:

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

o Data Center: Name of the data center where the Cisco SAN switch exists.

o Start IP Address and End IP Address: Range of the IP address, from where you want to start collecting data. This scans all the switch IP addresses from that range, and the valid switch IP address is added in the system.

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

o Password: Password of the user name.

o SSH Port: The port number. The default port number is 22.


• Upload CSV: Select Upload CSV, to upload the switch details in CSV file, and then click Import CSV.

• The CSV file must be in specific format. You can download the sample file by clicking the Download Sample CSV File link.

• Upload Encrypted CSV: Select Upload Encrypted CSV, to upload details in the encrypted CSV file, and then click Import CSV. To encrypt the CSV file, see Encrypting the CSV file.

• The Encrypted CSV file must be in specific format. You can download the sample file by clicking the Download Sample CSV File link.

The list of Cisco SAN switch IP address appears.

If you want to add more Cisco SAN switch IP address, click Add More. 4.

Click Next. 5.

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

On the Switch Validation window, click Next, and then OK. 6.

The switch IP passed the validation is added as probe.



Retrieving diagnostic data from the probe Diagnostic data gathers all the essential logs that are required to find the root cause of any problem on the Data Center Analytics probe. It consists of various configuration and log files, which help resolve any problem. If you cannot resolve the problem, then you can send the generated data file with the error messages to customer support for analysis. See Getting help.

Procedure

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

The Log on window appears. Log on to Data Center Analytics probe. 2.

Note: The user name and password is set at the time of deployment.

On the Home page, in the application menu area, click the Manage link. 3.

On the Manage window, click the Download Diagnostic Data link. 4.

On the Download Diagnostic Data window, click Download to download the 5.file.


Installing Data Center Analytics Windows-based probe

Data Center Analytics Windows-based probe is desktop-based software that collects performance and configuration data from the Windows-based host and Hyper-V machines. You can install Windows-based probe on Windows-based machine using Data Center Analytics Windows-based probe installer.

• Data collection method

• Windows-based probe installation prerequisites

• Installing Windows-based probe

• Configuring Windows-based probe


Data collection methods

You can use one of the following methods to collect data using the Windows-based probe:

Method 1: Data collection from System Center Operation Manager (SCOM) and System Center Configuration Manager (SCCM).

• Performance data is collected from SCOM.

• Configuration data is collected from SCCM.

Prerequisites

SCOM

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

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

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

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

• Add following DLLs in Data Center Analytics Windows-based probe installer folder:\bin

Microsoft.EnterpriseManagement.OperationsManager.Common.dll Microsoft.EnterpriseManagement.OperationsManager.dll

The above DLLs are under the following folder on Windows-based machine System Center Operations Manager 2007\SDK Binaries

SCCM

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

• Hardware Inventory Client Agent of SCCM must be running on the target machines. This agent collects required configuration data and stores it in the SCCM database.

• A user from the db_datareader group in the SQL Server who can access the SCCM database.


Method 2: Data collection from the System Center Operation Manager (SCOM) and WMI query

• Performance data is collected from the SCOM.

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

Prerequisites

SCOM

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

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

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

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

• Add following DLLs in Data Center Analytics Windows-based probe installer folder: \bin

Microsoft.EnterpriseManagement.OperationsManager.Common.dll Microsoft.EnterpriseManagement.OperationsManager.dll

The above DLLs are under the following folder on Windows-based machine System Center Operations Manager 2007\SDK Binaries

WMI Query

• A user with the Domain Administrator role, and with the permissions to access ROOT/WMI , ROOT, ROOT/CIMV2, and WMI namespaces on the target machine. The Execute Methods and Remote Enable permissions are required for the namespaces.

• Firewall exceptions must be added for the WMI on the target machine. To add the exceptions run the following commands on the target machine:

o netsh firewall set service RemoteAdmin

o netsh firewall set service type=fileandprint mode=enable profile=all scope=all

• For workgroup computers: Change the settings for the Remote User Account Control (UAC) LocalAccountTokenFilterPolicyregistry entry.


For more information, see http://support2.microsoft.com/kb/942817/en-us

Method 3: Data collection using Perfmon API and WMI query

• Performance and configuration data is collected from individual machines using the Perfmon API and WMI query.

Prerequisites

• The probe machine and the target machines must be part of either workgroup or domain.

• Firewall exceptions must be added for the WMI and Perfmon on the target machine. To add the firewall exceptions, run the following commands on the target machine:

o netsh firewall set service RemoteAdmin

o netsh firewall set service type=fileandprint mode=enable profile=all scope=all

• To connect to Windows-based machines remotely, the following must exist:

o The remote registry service must be running on the target machine.

o On the target machine, the Local Service must have read permissions for the following registry key:

o HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurePipeServers\winreg

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

• For workgroup computer: The following settings are required if you are not using the built-in administrator for connections:

o A user with Domain Administrator role, and with the permissions to access ROOT and ROOT/CIMV2 WMI namespaces on the target machine. Execute Methods and Remote Enable permissions are required for the namespaces.

o 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

o Computer browser service must be running on the target machine.

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




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

Windows-based probe is installed:

o Windows 7

o Windows 8

o Windows Server 2008

o Windows Server 2008 R2



• RAM: Minimum 8 GB.

• Disk space: Minimum 50 GB.

• Microsoft .Net Framework 3.5 SP1 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:

o Windows 7

o Windows 8






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


Installing the Windows-based probe

Procedure

Run the Data Center Analytics Windows-based probe installer. 1.

To continue installation, click Next. 2.

On the Log on Information window, type the Domain Administrator’s or Local 3.user’s credentials for the Windows-based machine in the format specified on the window, and click Next.

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

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

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

Click Finish. 6.


Configuring Data Center Analytics Windows-based probe

Configuring the Windows-based probe requires using the following procedures:

• Configuring the collection method

• Configuring the FTP or HTTPS server

• Starting the Windows-based probe service

Configuring the collection method

Procedure

Double-click the Windows-based probe icon on the desktop. 1.

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

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

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


Method 1: Data collection from SCOM and SCCM

1. In the Performance section, select Use SCOM and type the following details:

• SCOM Server: SCOM server IP address.

• User Name (Advanced Operator): SCOM server user name.

• Password: SCOM server password.

2. In the Configuration section, select Use SCCM and type the following details:

• SCCM Database Server: SCCM Server IP address or the name.

• Database Name: SCCM database name.

• SQL Server User Name: SCCM database user name.

• SQL Server Password: SCCM database password.

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

Method 2: Data collection from SCOM and WMI

3. In the Performance section, select Use SCOM and type the following details:

• SCOM Server: SCOM server IP address.

• User Name (Advanced Operator): SCOM server user name.

• Password: SCOM server password.

4. In the Configuration section, select Use WMI and type the following details:

• User Name (Administrator): Domain administrator user name.

• Password: Domain administrator user name password.

• Collect Event Logs: Select the check box to collect event logs.


Method 3: Data collection through WMI and PerfMon

5. In the Performance section, select Use Perfmon. This enables the Use WMI option automatically.

6. Type the following details for Use Perfmon and Use WMI options:

• User name (Administrator):

o In Workgroup environment: Machine Name\User

Computer Name: Machine name on which the Windows-based probe is installed.

User: A user with an Administrator role.

o In the Active Directory environment: Domain Name\User

Domain Name: Name of the domain.

User: A user with the Domain Administration role.

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

7. To collect event logs, in the Configuration section, select the Collect Event Logs check box to allow you to select the types of logs.

8. In the Performance section, select Collect Process.


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

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

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

•

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

Configuring the FTP or HTTPS server You must configure the FTP server for the Windows-based probe to send the data.

Procedure

On the Windows-based probe console, click the Upload Settings Tab. 1.

On the Upload Settings window, select the protocol FTP or HTTPS. 2.

Note: If you select HTTPS, see Installing HTTP proxy server.

Type the following details: 3.

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

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

• Logon: meghadata

• Password: meghadata123


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

Click Validate & Save. 5.

Start the Windows-based probe service. See, Starting the Windows-based probe 6.service.

Starting the Windows-based probe service

Procedure

On the Windows-based probe console, click the Status tab. 1.

The Status window list the details of the upload information and service information.

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


Special procedures This section contains procedures required in special situations.

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

Assigning a static IP address An IP address is dynamically assigned to the server and the probe using DHCP at the time of deployment. If you want to assign a static IP address to server and probe, complete the procedure in this section.

Assigning a static IP address in the VMware vSphere

Procedure

In the VMware vSphere application, select the server or probe that you have 1.deployed, and then click the Console tab in the right navigation pane.

Log on to the console as follows: 2.

• localhost logon: config

• Password: megha!234

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

Type yes, and then press Enter. 3.

Specify the following details and type yes to apply the changes. 4.

• IP address

• NetMask

• Gateway

• Domain Name

• Name Server


The system assigns the required static IP address.

Verifying the console time

In the example, we use ETC/UTC as the sample time zone.

Procedure

Log on to the Data Center Analytics server through SSH (like putty) using the 1.following credentials.

• User: root

• Password: megha.jeos

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

To verify the console time property. Run the command date and verify the time 2.zone. The time zone as shown in the sample output as follows.

To verify the clock time property run the command cat /etc/sysconfig/clock 3.and verify the time zone as shown in sample output as follows:


Note: If the output of the console and clock property is different, then make sure you change the property to the same time zone. See, Setting the console time zone.

Setting the console time zone

To set the time zone:

Log on to the Data Center Analytics server through the SSH client (like putty) 1.using the following credentials:

User: root Password: megha.jeos

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

Go to the /etc directory and rename the current localtime file under the /etc 2.directory using the following command: mv localtime localtime.bak

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

ln-s /usr/share/zoneinfo/Etc/UTC localtime

Run the command date. It must contain the same time as the clock property. 4.

Update the time zone as Etc/UTC in /etc/sysconfig/clock. 5.

Run the command service crond stop. 6.

Stop the megha service using the command /usr/local/megha/bin/megha-7.jetty.sh stop

Confirm the stopped status of megha service /usr/local/megha/bin/megha-8.jetty.sh status

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


Start the crond service using the command service crond start. 10.

Adding a megha user for the Symmetrix array

Procedure

Log on to the EMC Solutions Enabler Symmetrix CLI server. 1.

Go to the <Installation Directory>/symcli/bin directory. 2.

Verify that authentication is enabled using the following command: symauth list 3.

Add the megha user with the monitor access using the following command: 4.symauth -sid <SYMMETRIX ID> -file <fileName> commit

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

Uninstalling the rpm file for server and probe

Procedure

Log on using OS user account with root user permission. 1.

Stop the security monitoring software, antivirus software, and process monitoring 2.software. If these software programs are running, the uninstallation fail.

Run the following command: sh /usr/local/megha/uninstall.sh 3.

Changing the opcode property file value

Procedure

To enable the collection of the following opcode HGC, HHGC, and LHGC on the RAID Agent instance, change the Log=N to Log=Y in the following configuration file /opt/jp1pc/agtd/agent/<instance_name>/jpcagt.ini on the RAID Agent instance.

For example,

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

[[HGC]]

Description=Host Group Configuration

Log=N


Collection Interval=21600

Collection Offset from Top of Minute=0

LOGIF=

-----------------------------------------------------

[[HHGC]]

Description=Host Per Host Group Configuration

Log=N

Sync Collection With=Detail Records, HGC

LOGIF=

-----------------------------------------------------

[[LHGC]]

Description=LUN Per Host Group Configuration

Log=N

Sync Collection With=Detail Records, HGC

LOGIF=

Note: After enabling the data collection, the Hitachi Enterprise Storage Probe receives the data after 21,600 seconds (6 hours).


Installing HTTP proxy server

Before you install HTTP proxy server, make sure that Java 7 or later is installed on the Linux machine and the megha user exists on the Linux machine.

Procedure

Create directory /usr/local/httpProxy. 1.

Unzip the httpProxy-<timestamp>.zip inside this directory. For the httpProxy-2.<timestamp>.zip file contact HDS support, see Getting help.

Change ownership to megha using the command: 3.$ chown –R megha:megha /usr/local/httpProxy

Give executable permission to the start and stop the scripts using the command: 4.$ chmod +x /usr/local/httpProxy/bin/*

Configure the default FTP settings by editing the following file: 5./usr/local/httpProxy/conf/target/ftp.properties

Configure user-specific settings by creating a file as <user>.ftp.properties in 6.the same directory (target) and writing your settings inside.

Start the http proxy server using the command: 7./usr/local/httpProxy/bin/megha-jetty.sh start

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

Encrypting the CVS file

Procedure

Contact HDS support for the public key for encryption, see Getting help. 1.

Log on to the probe console through SSH client (like putty). 2.

Create the temporary folder in the /data folder and save the public key. 3.

Generate the random Key by running the command: 4.

openssl rand -base64 32 > randomkey.bin

Encrypt the random key by using the public key, using the command: 5.

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

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

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


Download the encrypted random file and encrypted CSV file on your local 7.machine.

Provide the encrypted random file and CSV file as an input. 8.


Troubleshooting

FTP connection problem on Data Center Analytics server Example, java.net.ConnectException: Connection timed out

at 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.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: Make sure that you can connect to the FTP server from the Data Center Analytics server console.

Hitachi Data Systems

Corporate Headquarters 2845 Lafayette Street Santa Clara, California 95050-2639 U.S.A. www.hds.com

Regional Contact Information

Americas +1 408 970 1000 [email protected]

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

Asia Pacific +852 3189 7900 [email protected]

MK-96HDCA001-05 August 2016

http://www.hds.com/

mailto:[email protected]

hitachi data center analytics deployment guide · windows azure, windows powershell, ... retrieving...

Documents