hdca deployment guide (mk-96hdca001-00) · hdca uses various unobtrusive methods to collect metrics...

HDCA Deployment Guide

HDCA version : 5.0 Document updated : 08th January, 2016

© 2015 Cumulus Systems Inc. All Rights Reserved.

2 HDCA Deployment Guide

Table of Contents

1 Introduction ............................................................................................................................................ 4

2 Deployment Overview ............................................................................................................................ 5

Deployment................................................................................................................................... 5 2.1

Deployment Sequence .................................................................................................................. 5 2.2

Distribution Format ....................................................................................................................... 6 2.3

3 Prerequisites ........................................................................................................................................... 7

HDCA Server .................................................................................................................................. 7 3.1

RIAT Probe..................................................................................................................................... 7 3.2

4 Installing HDCA Server ............................................................................................................................ 8

HDCA Server on VMware vSphere Client using OVA .................................................................... 8 4.1

HDCA Server on Hyper-V Manager using VHD ............................................................................ 11 4.2

HDCA Server on Linux Machine using RPM ................................................................................ 13 4.3

5 Configuring HDCA Server ...................................................................................................................... 15

Connecting to HDCA Server ........................................................................................................ 15 5.1

Registering the License for HDCA Server .................................................................................... 15 5.2

Creating an Administrator Account ............................................................................................ 16 5.3

Logging in to HDCA Server .......................................................................................................... 16 5.4

Set Time Zone for HDCA Server .................................................................................................. 16 5.5

6 Installing RIAT Probe ............................................................................................................................ 17

Installing RIAT Probe on VMware vSphere Client using OVA ..................................................... 17 6.1

Installing RIAT Probe on Linux Machine using VMware Player .................................................. 19 6.2

Installing RIAT Probe on Linux Machine using RPM .................................................................... 19 6.3

7 Configuring RIAT Probe ........................................................................................................................ 21

Determining IP address of RIAT Probe ................................................................................ 21 7.1.1

Connecting to RIAT Probe ................................................................................................... 22 7.1.2

Registering License for the RIAT Probe ............................................................................... 22 7.1.3

Creating an Administrator Account .................................................................................... 22 7.1.4

Logging on to RIAT Probe Appliance ................................................................................... 22 7.1.5

Specifying Customer Details for RIAT Probe Appliance ...................................................... 22 7.1.6


Setting Time Zone for RIAT Probe ....................................................................................... 22 7.1.7

FTP configuration ................................................................................................................ 23 7.1.8

Defining Data Collection Duration for RIAT Probe .............................................................. 23 7.1.9

8 Adding Probes in RIAT Probe VM ......................................................................................................... 24

Storage ........................................................................................................................................ 24 8.1

Adding Hitachi Enterprise Storage Probe ........................................................................... 24 8.1.1

Adding AMS probe .............................................................................................................. 26 8.1.2

Adding VMAX probe ............................................................................................................ 26 8.1.3

Adding XIV Probe ................................................................................................................ 29 8.1.4

Adding NetApp probe ......................................................................................................... 30 8.1.5

Hypervisors ................................................................................................................................. 35 8.2

Adding VMware probe ........................................................................................................ 35 8.2.1

Switches ...................................................................................................................................... 35 8.3

Adding Brocade Network Advisor probe ............................................................................ 35 8.3.1

Adding Cisco DCNM probe .................................................................................................. 36 8.3.2

Retrieving Diagnostic Data from RIAT Probe .............................................................................. 36 8.4

9 Advanced Operations ........................................................................................................................... 38

Assigning a static IP address to RIAT Probe ................................................................................ 38 9.1

Assigning static IP address to RIAT Probe in vSphere ......................................................... 38 9.1.1

Assigning static IP address to RIAT Probe in VMware Player ............................................. 39 9.1.2

Setting Console Time .................................................................................................................. 39 9.2

10 Troubleshooting ................................................................................................................................... 42

Common Errors ........................................................................................................................... 42 10.1

Ftp connection issue on server m/c .................................................................................... 42 10.1.1


1 Introduction Hitachi Data Center Analytics (HDCA) is a software product that provides Data Center managers useful insights about their infrastructure using sophisticated analytics.

HDCA uses various unobtrusive methods to collect metrics such as IOPS, Transfers, Latency, etc. from the target devices. These metrics are collected by RIAT Probe at regular intervals and then periodically transferred to the Server for processing. The HDCA server reports this processed data using various built-in Reports and interactive Charts. This allows the IT manager to get a better understanding of the infrastructure and proactively take actions as required.

HDCA can provide analytics on the different elements of the Data Center such as Storage Systems, Servers, Hypervisors, Switches, etc.

The different components of HDCA are summarized in the following table. Both the components need to be installed.

Component Description

HDCA Server The HDCA Server processes the data that it receives from the different Probes. It consolidates and correlates this data to create the built-in and interactive Reports.

RIAT Probe VM RIAT Probe collects performance and configuration data from different types of targets.


2 Deployment Overview Deployment 2.1

The below diagram illustrate the deployment of Probe and Server.

Deployment Sequence 2.2

Step Task Description 1 Check prerequisites Make sure that the host on which you plan to install HDCA

Server and RIAT Probe meet the system requirements. • For information about HDCA Server requirements, see

Prerequisites for HDCA Server. • For information about RIAT Probe requirements, see

Prerequisites for RIAT Probe. 2 Install and Configure

HDCA Server Install and Configure the HDCA server. For more information, see Installing HDCA Server.

3 Install RIAT Probe Install the RIAT Probe VM. For more information, see Installing RIAT Probe.


Distribution Format 2.3The HDCA Server installer is provided in the following formats:

• OVA file This is the Open Virtualization Format (OVF) package that allows the HDCA Server to be deployed easily on a VMware infrastructure. The HDCA Server becomes a VM within the environment with all the required components pre-installed.

• VHD file This is similar to the above situation for a Microsoft Hyper-V environment. It can be installed on a host running Microsoft Windows Server 8.

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


3 Prerequisites HDCA Server 3.1The following table lists the prerequisites based on the distribution formats:

Format → OVA VHD

RPM

Prerequisites ↓

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

OS/Platform vSphere Client on ESX Server 3.5 or higher

Win2k8R2 and Win2k12 (both 64 bit)

Linux

• RHEL 6.1(64 bit)

• CentOS 6.2 (64bit)

RIAT Probe 3.2The following table lists the prerequisites for RIAT Probe:

Prerequisites Description

Operating Systems OVA and VHD deployment: vSphere client on ESX Server 3.5 or higher. RPM deployment: VMware Player running on Linux 64-bit.

RAM Minimum: 2 GB and Recommended: 4 GB Storage 50 GB


4 Installing HDCA Server You can install the HDCA Server on:

• VMware vSphere Client using OVA

• Hyper-V Manager using VHD

• Linux machine using RPM

The recommended format to install HDCA server is VMware vSphere Client using OVA.

HDCA Server on VMware vSphere Client using OVA 4.1To Install HDCA Server on VMware vSphere Client using OVA:

1. Open the vSphere Client application.

2. From the File menu, click Deploy OVF Template.

3. Click Browse, and then select HDCA Server OVA file.

4. Click Next.

The OVF Template Details window appears with the OVA file details.

5. Click Next and enter the following details:

• Name: HDCA Server will be identified by this name in vCenter.

• Inventory location: HDCA Server will be added under the selected inventory in the vSphere application.

6. Click Next.

7. (Optional) Select the appropriate cluster from the list of available clusters inside the inventory.


8. Click Next.

The system displays the list of resource pools that are available in the cluster. You can deploy HDCA Server in the resource pool or in the cluster.

9. Select the pool or cluster and click Next.

10. Select the datastore for HDCA Server. The system saves all the reports and log data in the

selected datastore.

11. Click Next, and define the appropriate disk format:

• Thick Provision Lazy Zeroed: Space required for the virtual disk is allocated at the time of creation. Each disk block is zeroed out only after it is accessed for the first time by the VM.

• Thick Provision Eager Zeroed: Space required for the virtual disk is allocated at the time of creation. Each disk block is zeroed out immediately after creating the disk.

• Thin Provision: The system initially allocates 2.8 GB and keeps allocating more space until 120 GB.


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

13. Proceed to the Configuring HDCA Server section.


HDCA Server on Hyper-V Manager using VHD 4.2To install HDCA Server on Hyper-V using VHD, add the Primary and Secondary hard disk.

Adding Primary VHD:

1. Right-click on the Hyper-V machine, point to New and then click Virtual Machine.

2. Click Next.

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

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

Note: Minimum Memory for VHD is 4 GB and Recommended Memory is 8 GB.

5. Configure a network for the VM, and click Next.

6. Click Use an existing virtual hard disk button, and click browse to select the HDCA Server primary VHD.

7. Click Finish.


Adding Secondary VHD:

1. Right-click the on the VM that you have created, and click Settings.

2. Select the IDE Controller 0, and select the Hard Drive.

3. Click Add. A new hard drive is added.

4. In the Hard Drive section, select 1 from the Location list.

5. In the Virtual hard disk (.vhd) file section, click Browse and select secondary VHD.

6. Click Apply, and then click OK.

7. Right-click VM and start it.



HDCA Server on Linux Machine using RPM 4.3Before you start installing HDCA server using RPM, please verify the following on the machine.

Prerequisites:

• Please ensure that the console and clock property is in the same time zone. If it is not then change it to the same time zone, to change the time zone see, Setting Time Zone.

• Check the current mode, the currtent mode should be Permissive, run the following command :

sudo sestatus

If the current mode is not set to Permissive, then run the following command :

setenforce 0

Dependencies:

• openssl-devel

• java-1.7.0-openjdk

To install HDCA Server on Linux machine using RPM:

1. Copy the HDCA Server rpm file to a folder on the Linux machine.

2. Run the following command:

rpm -ivh <HDCA Server RPM>

3. Run HDCA Server configuration script as below:

sh /usr/local/megha_installer/config.sh

4. Type N if you do not want Japanese support - or- Type Y if you want Japanese support. Install the package (fonts-japanese, dejavu-lgc-fonts) for Japanese support as mentioned in the screen capture.

Note: If you already have installed package required for Japanese support, this message will not display.

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

The dafault directory patch can be changed as per your requirement.


6. Press Enter. Default port is assigned to HDCA Server.

Note: The default ports are, for http:// 8080 and https:// 8443. If the default port is busy, system prompts you to enter another port number. Enter the appropriate port number.

7. To check the status, run the following command: sh /usr/local/megha/bin/megha-jetty.sh status

If the server is not running, run the following command:

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

8. The URL to access HDCA Server is provided at the end of the installation, as displayed in the following screen capture.



5 Configuring HDCA Server To configure HDCA Server:

• Connect to HDCA server

• Register the license

• Create an admin account

• Log on to HDCA Server

• Set time zone

Connecting to HDCA Server 5.1In the internet browser, type the HDCA Server URL https://<ip_address>:<Port Number> and click Enter.

Note: The default ports for HDCA server are, for http:// 8080 and https:// 8443

Read the License Agreement and accept it.

Registering the License for HDCA Server 5.21. Contact your HDS representative for getting the required HDCA license.

On the Upload License window, click Choose File.

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

Note: If you get License Invalid message, then try to do a dos2unix conversion on the license file before importing.

Run the following command, dos2unix <License File Name>


Creating an Administrator Account 5.3To create an administrator account:

1. Set the password for the built-in “admin” user.

2. On the Create Administrator Account window, specify the password and locale . The current version of HDCA supports only the English locale.

3. Click Submit.

Logging in to HDCA Server 5.4Enter the user name and password to log on to HDCA Server.

Set Time Zone for HDCA Server 5.5Time zone of HDCA Server needs to be set at the time of deployment. You can set the HDCA Server time zone as per your business requirement. The reports are presented in the defined time zone.

For example, in a scenario, where the Server is in IST time zone, one storage system is in the Eastern time zone and another in the Central America time zone, the reports of both storage systems are displayed in IST time zone.

If you want to change the time zone according to storage systems time zone, you can change it using this feature.

Note: This time zone will be applicable for reporting of each storage system.


6 Installing RIAT Probe You can install the RIAT Probe on:

• VMware vSphere Client using OVA

• Hyper-V Manager using VHD

• Linux machine using VMware Player

The recommended format to install RIAT Probe is VMware vSphere Client using OVA.

Installing RIAT Probe on VMware vSphere Client using OVA 6.1This is the Open Virtualization Format (OVF) package that allows the RIAT Probe to be deployed easily on a VMware infrastructure.

To install RIAT probe on VMware vSphere Client using OVA:

1. Open the vSphere Client application.

2. From the File menu, select the Deploy OVF Template.

3. Click Browse, and select the RIAT Probe OVA file.

4. Click Next. In the OVF Template Details section, OVA file details are displayed.

5. Click Next. In the Name and Location section, enter the following details:

• Name: RIAT Probe will be identified by this name in the vCenter.

• Inventory location: RIAT Probe will be added under the selected inventory in the vSphere application.

6. Click Next.

7. (Optional) In the Host/Cluster section, select the appropriate cluster from the list of available clusters inside the inventory.

8. Click Next.


9. (Optional) The system displays the list of resource pools that are available in the cluster. You can deploy RIAT Probe in the resource pool or in the cluster.

10. Click Next. Select the datastore for RIAT Probe. The system saves all the reports and log data in the selected datastore.

11. Click Next, and define the required disk format:

• Thick Provision Lazy Zeroed: Space required for the virtual disk is allocated at the time of creation. Each disk block is zeroed out only after it is accessed for the first time by the VM.

• Thick Provision Eager Zeroed: Space required for the virtual disk is allocated at the time of creation. Each disk block is zeroed out immediately after creating the disk.

• Thin Provision: The system initially allocates 2.8 GB and keeps allocating more space until 104 GB.

12. Click Next. The options you selected are displayed.

13. Select the Power on after deloyment check box.

14. Click Finish, to complete the deployment.


Installing RIAT Probe on Linux Machine using VMware Player 6.2To install the RIAT Probe appliance on Linux machine, using VMware Player:

1. Install the VMware Player on Linux machine.

2. Open the VMware Player application.

3. From the File menu, select Open a Virtual Machine. The Open Virtual Machine window appears.

4. Navigate to RIAT Probe VMX, select it and then click Open.

5. On Import Virtual Machine window, click Import.

6. Click Play Virtual Machine to start RIAT Probe.

Installing RIAT Probe on Linux Machine using RPM 6.3Before you start installing RIAT Probe using RPM, please verify the following on the machine.

Prerequisites:

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

RIAT Probe RPM build version: riat-probe-12.0.D-15093017.x86_64.rpm

Yum/rpm dependencies:

• Perl • gcc

• java-1.7.0-openjdk • 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

To install RIAT Probe on Linux machine using RPM:

1. Copy the RIAT Probe rpm file to a folder on the Linux machine.

2. Run the following command:

rpm -ivh < RIAT Probe RPM>


3. Run RIAT Probe configuration script as below:

sh /usr/local/megha_installer/config.sh

4. Type N if you do not want Japanese support - or- Type Y if you want Japanese support. Install the package (fonts-japanese, dejavu-lgc-fonts) for Japanese support as mentioned in the screen capture.

Note: If you already have installed package required for Japanese support, this message will not display.

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

The dafault directory patch can be changed as per your requirement.

6. Press Enter. Default port is assigned to RIAT Probe.

Note: The default ports are, for http:// 8080 and https:// 8443. If the default port is busy, system prompts you to enter another port number. Enter the appropriate port number.

7. To check the status, run the following command: sh /usr/local/megha/bin/megha-jetty.sh status

If the RIAT Probe server is not running, run the following command:

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

8. The URL to access RIAT Probe is provided at the end of the installation.


7 Configuring RIAT Probe Note: Before you install RIAT Probe, make sure that you have installed the HDCA server. HDCA servers IP is required in the configuration process of RIAT Probe.

RIAT Probe configuration is a one-time operation that sets up RIAT Probe. The workflow guides the user through the following steps. Console can be opened either through the vSpere screen or through the Hyper-V screen.

Note: The 'root' user login is disabled on Vsphere console and hyper-V console, you can login through SSH client (like putty) using the following credentials, Username: root & Password: app.jeos

Important: Please do not change the time zone setting manually, after login into a ssh client like putty. The RIAT Probe VM time zone is UTC by default.

RIAT Probe application time zone can be configured only from UI with any suitable value.

Determining IP address of RIAT Probe 7.1.1

1. Open RIAT Probe console. In the command prompt, enter the following login credentials:

Localhost login: config

Password: megha!234

IP address assigned to RIAT Probe is displayed next to the ‘inet addr’ field.

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

2. Type no and then press Enter.

You can also assign the static IP address to RIAT Probe see, Assigning static IP address to RIAT Probe.


Connecting to RIAT Probe 7.1.2

Open a browser and access RIAT Probe at the URL https://< RIAT Probe IP Address>:8443 where RIAT Probe IP is the IP address of RIAT Probe.

Read and accept the License Agreement. The Create New User window appears.

Registering License for the RIAT Probe 7.1.3

1. On the Upload License window, click Browse.

2. Browse to the license file and click Submit to register the license. The Create Administrator account window appears.

Creating an Administrator Account 7.1.4

A user account with administrator privileges must be created to manage RIAT Probe.

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

• User ID and Password

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

• Locale: RIAT Probe is available in two languages – US English and Japanese.

• Group: Select Admin to create administrator account.

2. Click Submit to create the login account.

Logging on to RIAT Probe Appliance 7.1.5

Enter defined user ID and password to log into RIAT Probe appliance.

Specifying Customer Details for RIAT Probe Appliance 7.1.6

In the Basic Information window, specify the basic information of customer.

1. Enter the following details:

• Customer Name: The customer name is diaplyed by default, you cannot edit the customer name. This field displays the name that is specified in the licence.

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

• Technical Contact Name and Technical Contact Email: Resource (generally administrator) who needs to be notified in case of technical issues.

2. Click Next. The Select Timezone window appears.

Setting Time Zone for RIAT Probe 7.1.7

Select the time zone where RIAT Probe appliance is deployed, and then click Next.


FTP configuration 7.1.8

On the FTP Information page, provide the appropriate details in each field, and then Click Next.

FTP Method: Select the SFTP as the FTP method from the drop-down.

Server: Enter the IP of Server where you want to upload the data.

Port: Port is displayed based on the selected FTP method.

User: Enter the FTP server user name as meghadata.

Password: Enter the user password as meghadata123

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

Proxy: Select Proxy, to provide the proxy details.

Defining Data Collection Duration for RIAT Probe 7.1.9

Data collection duration is defined as per the imported license. It can be reduced.

Click Next. This completes the initial set up of RIAT Probe.


8 Adding Probes in RIAT Probe VM You can add one or more types of RIAT Probes to collect data from different targets.

Storage 8.1

Adding Hitachi Enterprise Storage Probe 8.1.1

The Hitachi Enterprise Storage Probe collects the required metrics from Hitachi Enterprise (RAID) Storage Systems such as VSP G1000, VSP Gxxx, VSP, HUS-VM and USP-V.

Pre-requisites:

Before you add the Hitachi Enterprise Storage Probe, verify the following:

• Make sure that the Raid agent is installed.

• Verify that the Instance is added for the storage in Raid agent and Data collection is started for the added instances.

1. Click the Home link and then click Add Probe.

2. Select Hitachi Enterprise Storage Probe from the Probe list.

The Provide RAID Agent details screen appears.

3. Enter the following details:

• Probe Name: The name of the probe. Example, Hitachi Enterprise Storage Probe.

• RAID Agent IP Address: IP address of the Raid Agent.

• RAID Agent Hostname: Host name of the RAID Agent.

• RAID Agent Port: Port number of the RAID Agent.

• Storage System Serial number: The Storage serial number, with which the RAID Agent is assoiciated.

• Storage System Instance: Storage Instance number, with which the RAID Agent is assoiciated.

4. Click Next.

The system displays Configure RAID Agent Collection Interval screen. This lists the default data collection interval time. You can edit the collection interval time.


5. Click Next.

The system validates the Raid Agent, and displays the Provide Hitachi Device Manager details screen. This is an optional step, if you want to collect configuration metrics from Hitachi Device Manager then enter the required details.

6. On the Provide Hitachi Device Manager details screen, select Yes to configure to Hitachi Device Manager. Select No to skip this step.

• If you select No, the Hitachi Device Manager Section remains disabled, click Next the success message appears, that the Hitachi Enterprise Storage Probe is successfully added.

• If you select Yes, Hitachi Device Manager Section is enabled, enter the following details:

o IP Address: IP address of the Hitachi Device Manager.

o Port: Port number of the Hitachi Device Manager.

o Username/Password: Username and Password of the Hitachi Device Manager.

7. Click Next, the success message appears, that the Hitachi Enterprise Storage Probe is successfully added.


8. Click Ok. Start the probe on the Status page.

Adding AMS probe 8.1.2

The AMS Probe collects data through the AMS storage controllers.

1. Click Home link and then click Add Probe.

2. Select AMS from the Probes list.

3. Enter the following values:

• AMS Storage Name: Name of the AMS storage system. The name denotes the storage system for which this probe will be added. This need not be the same as storage name defined in your environment.

Note: After you add the probe, it will be identified with this name in RIAT Probe appliance.

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

• Username and Password: User credential of a user who has “read only” permissions.

Note: If the user authentication for AMS storage is “Off”, you need to enter a dummy Username and Password since these two fields are mandatory for adding AMS probe.

4. Click Next. The system validates the entered details.

5. Click Next after the successful validation.

6. Click Ok and start the probe on the Status page to start collecting data.

Adding VMAX probe 8.1.3

VMAX probe collects the data from EMC VMAX storage systems.

Pre-requisites:

Configuration in Target environment

• EMC Unisphere for VMAX: A machine with EMC Unisphere for VMAX (v1.6.2.4 or above) 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 (v7.6.2.26 or above) installed, monitoring all the target storage systems for which probe needs to be added.

Configuration on RIAT Probe appliance

• Install EMC Solutions Enabler Symmetrix CLI on RIAT Probe appliance.

1. Log into RIAT Probe appliance. (Username: root Password: app.jeos)

2. Copy EMC Solutions Enabler Symmetrix CLI tar.


Note: It is recommended to install same version of EMC Solutions Enabler Symmetrix CLI, as installed in the target environment.

3. Untar it: tar zxf se<version>-Linux-i386-SMI.tar.gz

4. Install it: ./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 netcnfg file.

1. Log into RIAT Probe appliance. (Username: root Password: app.jeos)

2. Edit netcnfg file: vi /var/symapi/config/netcnfg

3. At the end of the file, add entry as follow:

SYMAPI_SERVER - TCPIP <*IP Address> <*IP Address> <Port> NONSECURE

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

Default port number: 2707

Example:

SYMAPI_SERVER - TCPIP 172.17.40.19 172.17.40.19 2707 NONSECURE

4. Save the file.


To add the VMAX probe:


2. Select VMAX from the Probes list.

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

4. On the Add VMAX Unisphere window, enter IP Address of the machine where EMC Unisphere for VMAX is installed, Unisphere’s Username and Password.

5. Click Next. After successful validation, click Next again.

6. On the Managed VMAX Storage System window, select the VMAX storage systems for which you want to add VMAX probe.

For each VMAX storage a separate probe will be added. If you do not want to add probe for all the listed storage systems, you can add those later on. To add probe for remaining storage systems later on, see Managing VMAX probe.

7. Click Finish and then click OK. Proceed to start added probe(s).

8.1.3.1 Managing VMAX probe

After you add VMAX probe, you can:

• Add VMAX probe for the remaining VMAX storage systems

• Edit details of EMC Unisphere for VMAX

8.1.3.1.1 Adding VMAX probe for already added EMC Unisphere for VMAX Click Home link and then click Add Probe. 1. Select VMAX from the Probes list. The VMAX Unisphere Details window appears. 2. Click Add Storage link corresponding to the Unisphere for which you want to add Probe. The 3.

Managed VMAX Storage System window appears. Select the checkbox for which you have not added probe(s): 4.


Click Finish and then click OK. Proceed to start added probe(s). 5.

8.1.3.1.2 Edit details of EMC Unisphere for VMAX

Due to security reasons, EMC Unisphere for VMAX’s administrator may change password or user name in future. To continue data collection, you need to change password or username in RIAT Probe appliance as well.

On the Status page, if VMAX probe corresponding to EMC Unisphere for VMAX is (which you 1.want to edit) is running, stop it.

Click Edit link corresponding to the EMC Unisphere for VMAX that you want to edit. The Edit 2.VMAX Unisphere Details window appears.

Edit the username or password of the EMC Unisphere for VMAX. 3. Click Next. The system validates entered details. 4. After successful validation, click Next. 5. Click OK. 6.

Adding XIV Probe 8.1.4

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

Pre-requisites:

• XIV CLI – Can be downloaded from IBM support site.

• After downloading it, you need to keep it in MARS Server appliance in /opt directory:

I. Log into MARS Probe console through SSH client (like putty) using the below credentials

• Host: <IP address of MARS probe>

• User: root

• Password: app.jeos

• Port: 22

II. Navigate to /opt directory: cd /opt

III. Copy the XIV CLI package in /opt directory (package name should be something like this: xivcli-3.0.1-build3-linux32.tar )

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


1. Click the Home link and then click Add Probe.

2. Select XIV from the Probes list.

3. Enter values for the following:

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

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

• Password: Password of the above user.

4. Click Next. RIAT Probe appliance will validate the entered details.

5. After successfully validating the details, click Next and then click OK.

6. Start the probe on the Status page to start collecting data.

Adding NetApp probe 8.1.5

RIAT NetApp Probe allows you to collect configuration and performance data from NetApp storage systems using the ONTAP API.

Pre-requisites:

• Ensure that you have a user (read-only privileges) available on NetApp storage system with appropriate role to collect configuration and performance data. RIAT Probe supports 7-mode and C-mode types of NetApp storage system. The procedure of creating user differs as per the target storage system type.

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

• SSL must be enabled on the target NetApp storage system. NetApp probe uses Port 443 (Https connection) for connecting to NetApp Storage.

To ensure if SSL is enabled for NetApp follow the below steps:

1. Log on to NetApp Filer through SSH client (like putty).

2. Run the command “options http” and you should observe “httpd.admin.ssl.enable” status as “on”.


To Add NetApp probe in RIAT Probe Appliance:


2. Select NetApp from the Probes list.

3. Enter the following values:

• NetApp Server: IP address of NetApp server

• Username and Password: Enter the username and password that you have created.


5. Click Next after successful validation.

6. Click Ok and start the probe on Status page to start collecting data.


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

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

For example:


Add a group: 3.

useradmin group add <Group Name> -r marsrole

For example:

Add a user: 4.

useradmin user add <User Name> -g mars_group

For example:

Enter the password. 5. Proceed to Adding NetApp Probe. 6.

8.1.5.2 Creating user for NetApp C-mode

Log on to target NetApp storage system using NetApp OnCommand System Manager. 1. Navigate to <NetApp Storage system name> Configuration Security Users. 2.

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


• UserName: Enter any valid username.

• Password & Confirm Password: Enter password for above user and confirm it.

• Under User login methods section, click Add and do the following:

Select ontapi in the Application column.

In the Role column, select readonly.

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

Click OK.

Click Add. The new user will be added. You can use this user to collect configuration and 4.performance data.

5. Proceed to Adding NetApp Probe


Hypervisors 8.2

Adding VMware probe 8.2.1

VMware Probe collects data of the Virtual Machines from the VMware vCenter Server and standalone ESX Server.

To add VMware probe,

1. Log on to RIAT Probe Appliance.

2. On the Home Page, Click Add Probe.

3. From the Probes list, select VMware.

4. Enter the details for the following:

• vCenter Server: Host name or IP address of the vCenter Server.

• Username: Any user having access to vCenter. Read-only privileges are also sufficient.

• Password: Password of the vCenter user


6. Click Next, after a successful validation.

7. Click OK, and start the probe on the Status page to start collecting data.

Switches 8.3

Adding Brocade Network Advisor probe 8.3.1

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

Pre-requisites:

A user should have Area of Responsibility as All Fabrics.


2. Select Brocade Network Advisor from the Probes list.


• Network Advisor IP: IP address of Brocade Network Advisor

• Username and Password of Borcade Network Advisor.

• Collect Event Logs: Select this check to collect log data to see log analysis in Server.





Adding Cisco DCNM probe 8.3.2

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


2. Select Cisco DCNM from the Probes list.


• Cisco DCNM IP: IP address of DCNM

• Username and Password of DCNM




Retrieving Diagnostic Data from RIAT Probe 8.4Diagnostic data gathers all the essential logs required to find the root cause of any issue that is encountered on the HDCA Server. It consists of various configuration and log files, which help to resolve the issue. If the issue is not resolved, the generated data file can be sent along with the error messages to the support team for analysis.

To retrieve the diagnostic data:

4. In the internet browser, type the RIAT Probe URL https://<ip_address>:<Port Number>and click Enter.

5. The Login screen appears. Log on to RIAT Probe.

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

6. In the Main menu, click on the Manage link.

The Mange window appears.


7. Click on the Download Diagnostic Data link.

The Download Diagnostic Data window appears.

8. Click Download to start downloading the file.


9 Advanced Operations This chapter describes steps that are not common but required only in specific situations.

Assigning a static IP address to RIAT Probe 9.1An IP address is dynamically assigned to RIAT Probe using DHCP at the time of deployment. If you need to assign a static IP address to RIAT Probe, follow the steps in this section.

Assigning static IP address to RIAT Probe in vSphere 9.1.1

1. In the vSphere application, select RIAT Probe that you have deployed and then click the Console tab in the right navigation pane.

2. Log on to the console,

• localhost login: config

• Password: megha!234

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

3. Type yes and then press Enter.

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

• IP address

• NetMask

• Gateway

• Domain Name

• Server Name

The system assigns the desired static IP address to the RIAT Probe.


Assigning static IP address to RIAT Probe in VMware Player 9.1.2

The process for assigning a static IP address to RIAT Probe using VMware Player is similar to that using vSphere.

Log on to the console in VMware Player,

• localhost login: config

• Password: megha!234

Follow the steps from the section, Assigning static IP address to RIAT Probe in vSphere .

Setting Console Time 9.2Note: In the below example we have used ETC/UTC as sample time zone.

To verify the time zone:

1. Log on to the HDCA server through SSH client (like putty) with the below credentials.

User: root

Password: megha.jeos

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

2. To check console time property, run command “date”and check the time zone. As shown in below sample output.

3. To check clock time property, run command “cat /etc/sysconfig/clock” and check time zone as

shown in below sample output.


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


To set the time zone:

1. Login to HDCA server through SSH clinet (like putty) using the below credentials.

User: root

Password: megha.jeos

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

2. Go to “/etc” directory.

3. Rename the current localtime file under /etc directory using the following comman,

mv localtime localtime.bak

4. Link the Etc/UTC time zone directory from /usr/share/zoneinfo to the /etc/localtime directory as following,

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

5. Run command “date”. It should conatins the same time as clock property.

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

• Execute the “service crond stop” command.

• Stop the megha service using the command “/usr/local/megha/bin/megha-jetty.sh stop”

• Confirm the Stopped status of megha service using command “/usr/local/megha/bin/megha-jetty.sh status”

7. Start the megha service using command “/usr/local/megha/bin/megha-jetty.sh start”

8. Start the "crond" service using the command “service crond start”.


10 Troubleshooting Common Errors 10.1

Ftp connection issue on server m/c 10.1.1

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 HDCA Server console.

hdca deployment guide (mk-96hdca001-00) · hdca uses various unobtrusive methods to collect metrics...

Documents