Skip to main content
Outside service Partner
Hitachi Vantara Knowledge

Installing HIAA in an OVA

Install Infrastructure Analytics Advisor in an OVA by preparing your environment, installing all components, and performing initial setup.

Infrastructure Analytics Advisor overview

Infrastructure Analytics Advisor provides a comprehensive application service-level and storage performance management solution that enables you to quickly identify and isolate performance problems, determine the root cause, and provide solutions. It enables proactive monitoring from the application level through all network and storage resources for end-to-end visibility of your monitored environment. It also increases performance of existing storage resources and storage availability by identifying problems before they can affect applications.

Infrastructure Analytics Advisor collects and correlates data from these sources:

  • Storage systems
  • Fibre channel switches
  • Hypervisors
  • Hosts
Installation components

To use Infrastructure Analytics Advisor, you install and configure the following components:

  • Infrastructure Analytics Advisor server The primary component that communicates with the Data Center Analytics server. It correlates the configuration and performance data obtained by Data Center Analytics server to generate reports and enable data analytics for performance monitoring and problem resolution in your monitored infrastructure resources.
  • Data Center Analytics server This server processes performance and configuration data received from probes that connect to devices that are enabled for monitoring and provide the data to be used for reporting and analysis on the Infrastructure Analytics Advisor server.
  • Analytics probe server This server enables you to collect performance and configuration data from a target.

Infrastructure Analytics Advisor system configuration

The various installation and configuration methods and components are explained and illustrated.

The following figure shows an example of a two-host configuration where Infrastructure Analytics Advisor server and Data Center Analytics server are installed on the same host, and Analytics probe server is installed on a different host.

The following figure shows an example of a three-host configuration where Infrastructure Analytics Advisor server, Data Center Analytics server, and Analytics probe server are all installed on different hosts.

Note the following when configuring the system:

  • Make sure that Data Center Analytics server and Analytics probe server are installed on different hosts.
  • When you install Analytics probe server, RAID Agent is also installed. If you have Hitachi Tuning Manager - Agent for RAID installed in your environment, you can configure Tuning Manager - Agent for RAID with Infrastructure Analytics Advisor, instead of using RAID Agent.
  • The Data Center Analytics server must be connected to one Infrastructure Analytics Advisor server only.
  • If you want to limit the I/O activity of resources by using the Storage I/O controls feature of Infrastructure Analytics Advisor, install Hitachi Automation Director and the Hitachi Configuration Manager REST API on a host of your choice. If you are already using Automation Director or the Configuration Manager REST API, you can configure the product or products that you are currently using with Infrastructure Analytics Advisor.
  • The Analytics probe server cannot be installed on a host where the following products are installed:
    • Tuning Manager
    • Agent components for Tuning Manager
  • The components of Infrastructure Analytics Advisor cannot be installed in a cluster environment.

Installation workflow for a two-host configuration

The workflow from installation to setup differs depending on the installation method you use. If you want to create a two-host configuration where Infrastructure Analytics Advisor server and Data Center Analytics server are installed on the same host, and Analytics probe server is installed on a different host, we recommend deploying virtual appliances.

The following figure shows the workflow for creating an Infrastructure Analytics Advisor system in a two-host configuration.

Installing Infrastructure Analytics Advisor server and Data Center Analytics server on VMware vSphere Client

The installation of Infrastructure Analytics Advisor server and Data Center Analytics server on a VMware vSphere Client is explained and illustrated.

Preparing for installation

Before you start deploying virtual appliances for Infrastructure Analytics Advisor server and Data Center Analytics server, review the following prerequisites.

Prerequisites Description

Review hardware and software requirements

Review the requirements for Infrastructure Analytics Advisor server and Data Center Analytics server. Make sure that you meet all the hardware and software requirements.

Port requirements

Make sure that the ports you specify are available for communication. The default ports are 8443 (Data Center Analytics server) and 22015 (Infrastructure Analytics Advisor server).

Time zone settings

The times and time zones of the following servers must all be synchronized:

  • Infrastructure Analytics Advisor server
  • Data Center Analytics server
  • Analytics probe server
License Obtain the Infrastructure Analytics Advisor server and the Data Center Analytics server licenses from your Hitachi representative.

Host name resolution

When you use DHCP to assign an IP address to a host, configure the Domain Name System (DNS) server so that the IP address can be resolved from the host name.

Note that if you use a static IP address, the setting to resolve the IP address from the host name will be added to the hosts file automatically.

Installation

Deploy the OVA file for Infrastructure Analytics Advisor server and Data Center Analytics server using the installation media.

Procedure

  1. From a VMware vSphere client, log on to the VMware ESXi server.

  2. Deploy the OVA file for Infrastructure Analytics Advisor server and Data Center Analytics server from the installation media for virtual appliances.

    From the VMware vSphere client, select File Deploy OVF Template, and then follow the on-screen instructions.

    TipSelect Thick Provision Lazy Zeroed in the window for selecting the disk provisioning method.
  3. Change the settings so that the virtual machine does not connect to the network when started.

    When deployment is complete, the following network settings will be set by default for the virtual machine. This operation is not required if you are sure that the IP addresses will not conflict.
    • IP address172.17.29.166
    • Net mask255.255.128.0
    • Default gateway172.17.0.1
    1. Right-click the virtual machine that you want to edit, and then select Edit Settings.

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

  4. Start the virtual machine.

    When you logon for the first time, use the following user ID and password:

    • User IDroot
    • Passwordmanager

    After you logon, you can change the root password.

  5. Confirm that the network setting is correct.

Next steps

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

Initial setup of the guest OS or VMs

After deploying the virtual appliance, run the setup tool (hvaconfig) to specify the initial settings for the guest OS.

Procedure

  1. From the VMware vSphere Client, log on to the guest OS.

  2. Run the hvaconfig command that is stored in /opt/HIAA/vmtool.

    NoteYou can run the setup tool only once. To change the settings after running the setup tool, use the operating system commands.
  3. In the setup tool, you can specify the following settings.

    • Network settings
      • Host name: The Analytics probe server does not support FQDNs. Omit the domain name when specifying the host name.
      • IP address: The setup tool specifies an IPv4 address.
      • Default gateway
      • Network mask
      • DNS server (2 servers maximum)
    • Time settings
      • Time zone
        • Specify the time zone in the area/location format. If you do not know the specifiable values, use the following command in advance to check the time zone values that can be set.
          timedatectl list-timezones
        • The times and time zones of the following servers must be synchronized:
          • Infrastructure Analytics Advisor server
          • Data Center Analytics server
          • Analytics probe server
      • NTP server
    • Security setting
      • Server certificate
  4. Check the contents of the list that displays your specified settings, and then apply the settings.

    After the settings are applied, the guest OS restarts automatically.

  5. If the virtual machine is not connected to the network when deployed, perform the following steps to enable the network adapter:

    1. Log on to the guest OS.

    2. Stop the virtual machine by running the shutdown command.

    3. Right-click the virtual machine that you want to stop, and then select Edit Settings

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

    5. Run the Power On the virtual machine.

Next steps

Perform the initial setup of Data Center Analytics server and Analytics probe server.

Initial setup of Data Center Analytics server

Open the URL of the Data Center Analytics server and follow the prompts.

Before you begin

  • Check the IP address of the Data Center Analytics server.
  • Obtain the Data Center Analytics license from your Hitachi representative.
NoteThe Data Center Analytics server creates the following users for the supported OS: megha, meghadata, mars, and config. Do not change them.

Procedure

  1. Enter the Data Center Analytics server URL in your browser:

    https://ip-address:port-number The default port for https access is 8443.
  2. Read and accept the license agreement, and then click Next.

  3. In the Upload License window, click Choose File to browse to the license file and click Open.

  4. Click Submit to register the license.

  5. In the Set Details For Existing admin User window, enter the password, select the locale, and then click Submit (The user name for the built-in administrator account is admin) .

    NoteThe current version of Data Center Analytics supports only the English locale.
  6. In the Data Center Analytics server login window, enter the administrator user credentials and click Login.

  7. In the Select Time zone window, select the appropriate time zone and click Next.

    The Data Center Analytics server home page is displayed.
    NoteReports display data using the time zone of the Data Center Analytics server (not that of the storage systems). For example, if your server is located in the IST time zone, reports will use IST time regardless of where individual storage systems are located.
  8. (Optional) Create an Infrastructure Analytics Advisor server account that belongs to the Administrator group on the Data Center Analytics server.

    For information about how to add accounts, see the Hitachi Data Center Analytics User Guide. If you use the built-in administrator account to access the Infrastructure Analytics Advisor server, this step is unnecessary.

    NoteSeveral accounts are created automatically in Data Center Analytics server when you configure Infrastructure Analytics Advisor server for connecting with the Data Center Analytics server. Do not change or delete the information of the following user accounts:
    • HIAA_Server_Admin

    • HIAA_REST_Admin

    • HIAA_REST_Normal

    • HIAA_GUI_Report

Installing Analytics probe server on VMware vSphere Client

Review the prerequisites before installing an Analytics probe server using the virtual appliance.

Preparing for installation

Before you deploy a virtual appliance for Analytics probe server, review the hardware, software, and port requirements, synchronize the time zone, and obtain the license.

Prerequisites Description

Review hardware and software requirements

Review the Analytics probe server requirements. Make sure that you meet all the hardware and software requirements.

Port requirements

Make sure that the ports you specify are available for communication. The default port is 8443. The default port for SSH is 22.

Review virtual system operations

Review the following requirements when you run RAID Agent in a virtual environment.

  • Setting the LANG environment variable*

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

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

    If you want to monitor VSP, VSP F series, VSP G series, or HUS VM, you must configure the settings to enable accesses from a guest OS to command devices. For details, see the documentation for your virtual system.

    Use VMware vSphere Client file to add a device to the guest OS. By doing so, if you designate a command device as the device to be added, the command device can be accessed from the guest OS.

    When configuring settings to add a device, make sure that the following requirements are met:

    • Device type: Hard disk
    • Disk selection: Raw device mapping
    • Compatibility mode: Physical
    • Virtual disks (including VMware VVols) are not used for the command device.
  • Note about replication

    When you use a virtualization system to replicate an OS environment in which the RAID Agent is running, do not apply the replicated environment to any other host. Startup of the RAID Agent might fail in the replicated environment.

Time zone settings

The times and time zones of the following servers must all be synchronized:

  • Infrastructure Analytics Advisor server
  • Data Center Analytics server
  • Analytics probe server
License Obtain the Analytics probe server license from your Hitachi representative.
*: At startup, RAID Agent is subject to the system LANG environment variable. If the LC_ALL environment variable differs from the LANG environment variable, either unset LC_ALL or change its value to match the LANG value. Use the following example as a reference when setting the LANG value for RAID Agent. The last line is an example of coding that unsets the LC_ALL value.
  • Example settings:

    ## Set Environment-variables
    PATH=/sbin:/bin:/usr/bin:/opt/jp1pc/bin
    SHLIB_PATH=/opt/hitachi/common/lib
    LD_LIBRARY_PATH=/opt/hitachi/common/lib
    LIBPATH=/opt/hitachi/common/lib
    HCCLIBCNF=/opt/jp1/hcclibcnf
    LANG=C
    export PATH SHLIB_PATH LD_LIBRARY_PATH LIBPATH HCCLIBCNF LANG
    unset LC_ALL

Installation

Deploy the OVA file for an Analytics probe server using the installation media.

Procedure

  1. From a VMware vSphere client, log on to the VMware ESXi server.

  2. Deploy the OVA file for Analytics probe server from the installation media for virtual appliances.

    From the VMware vSphere client, select File Deploy OVF Template, and then follow the on-screen instructions.

    TipSelect Thick Provision Lazy Zeroed in the window for selecting the disk provisioning method.
  3. Change the settings so that the virtual machine does not connect to the network when started.

    When deployment is complete, the following network settings will be set by default for the virtual machine. This operation is not required if you are sure that the IP addresses will not conflict.
    • IP address172.17.29.167
    • Net mask255.255.128.0
    • Default gateway172.17.0.1
    1. Right-click the virtual machine that you want to edit, and then select Edit Settings.

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

  4. Start the virtual machine.

    When you logon for the first time, use the following user ID and password:

    User ID: root

    Password: manager

    After you logon, you can change the root password.

  5. Confirm that the network setting is correct.

Next steps

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

Initial setup of Analytics probe server

Open the URL of the Analytics probe server and follow the prompts.

Before you begin

  • Check the IP address of the Data Center Analytics server.
  • Check the IP address of the Analytics probe server.
  • Obtain the Data Center Analytics license from your Hitachi representative.
NoteThe Analytics probe server creates the following user accounts: megha, meghadata, mars, and config. Do not change them.

Procedure

  1. Open your browser and enter the Analytics probe server URL.

    https://Analytics-probe-server-IP-address:8443
  2. When you first launch the Analytics probe server UI, you see the license agreement details. Read, and then click Next.

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

  4. Click Submit to add the license.

  5. In the Create Administrator Account window, provide the following, and then click Submit:

    • User name and password.
    • First name, last name, and email address of the user.
    • Locale: Only the U.S. English locale is currently supported.
    • Group: Select Admin to create an administrator account.
  6. In the Analytics probe login window, enter the administrator user credentials and click Login.

  7. The Basic Information window displays the Customer Name (which cannot be changed). Provide the following contact information and click Next:

    • Administrator Contact Name and email
    • Technical Contact Name and email
  8. In the Select Time zone window, set the same time zone for the Analytics probe server as that of the Infrastructure Analytics Advisor server, and then click Next.

  9. In the Primary HDCA Server Information window, specify the following details:

    • Protocol: FTP, FTPS, SFTP, or HTTPS.
    • Host: Data Center Analytics server or FTP server IP address.

      If you are using FTP server as a primary server, then make sure that you configure downloader on the Data Center Analytics server to download the data from this intermediate FTP server.

    • Port: Based on the selected protocol.
    • User: User name for the host. For a Data Center Analytics server the user name is: meghadata
    • Password: Password for the host. For a Data Center Analytics server the password is: meghadata123
      Note You cannot change the password of the FTP user account (meghadata). To enhance security for the FTP account, you can disable the login shell of the meghadata user.
    • Advanced Settings:
      • Passive: Connect to the FTP server in Passive mode.
      • Proxy: Select to configure a proxy server.
      • Real time server: By default the Real time server field uses the value that you entered in the Host field.

        If you are using FTP server, then make sure you type in the Data Center Analytics server IP address that is processing the data of the primary server.

    NoteThe Analytics probe server must be reachable by Data Center Analytics server using the port 9092.
  10. Click Next.

    In addition to sending probe data to a single (local) Data Center Analytics server, you can configure a secondary, cloud-based Data Center Analytics server. The purpose is to host a copy of the probe data where it can be accessed outside of your internal network. You can add this secondary server from the Analytics probe server UI.

    NoteThe secondary Data Center Analytics server does not support real-time collection; the data may be received at different times from the Analytics probe server.
  11. In the Data Collection duration window, verify the license expiry date in your license, and then click Next.

  12. From the list of probes, select the probe type and configure it to collect data from the monitoring target. (You must add at least one probe to complete the installation)

    To add additional probes, go to the Analytics probe server web UI home page and click Add Probe. The following are available:
    • Hitachi Adaptable Modular Storage (AMS) probe

    • Hitachi Enterprise Storage probe

    • Hitachi NAS probe

    • IBM XIV® probe

    • EMC VMAX probe

    • EMC VNX Block probe

    • EMC VNX File probe

    • EMC XtremIO probe

    • NetApp probe

    • Pure Storage probe

    • VMware probe

    • Brocade Network Advisor probe

    • Cisco DCNM probe

    • Cisco SAN Switch probe

    • Linux probe

Initial setup of Analytics probe server

Open the URL of the Analytics probe server and follow the prompts.

Before you begin

  • Check the IP address of the Data Center Analytics server.
  • Check the IP address of the Analytics probe server.
  • Obtain the Data Center Analytics license from your Hitachi representative.
NoteThe Analytics probe server creates the following user accounts: megha, meghadata, mars, and config. Do not change them.

Procedure

  1. Open your browser and enter the Analytics probe server URL.

    https://Analytics-probe-server-IP-address:8443
  2. When you first launch the Analytics probe server UI, you see the license agreement details. Read, and then click Next.

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

  4. Click Submit to add the license.

  5. In the Create Administrator Account window, provide the following, and then click Submit:

    • User name and password.
    • First name, last name, and email address of the user.
    • Locale: Only the U.S. English locale is currently supported.
    • Group: Select Admin to create an administrator account.
  6. In the Analytics probe login window, enter the administrator user credentials and click Login.

  7. The Basic Information window displays the Customer Name (which cannot be changed). Provide the following contact information and click Next:

    • Administrator Contact Name and email
    • Technical Contact Name and email
  8. In the Select Time zone window, set the same time zone for the Analytics probe server as that of the Infrastructure Analytics Advisor server, and then click Next.

  9. In the Primary HDCA Server Information window, specify the following details:

    • Protocol: FTP, FTPS, SFTP, or HTTPS.
    • Host: Data Center Analytics server or FTP server IP address.

      If you are using FTP server as a primary server, then make sure that you configure downloader on the Data Center Analytics server to download the data from this intermediate FTP server.

    • Port: Based on the selected protocol.
    • User: User name for the host. For a Data Center Analytics server the user name is: meghadata
    • Password: Password for the host. For a Data Center Analytics server the password is: meghadata123
      Note You cannot change the password of the FTP user account (meghadata). To enhance security for the FTP account, you can disable the login shell of the meghadata user.
    • Advanced Settings:
      • Passive: Connect to the FTP server in Passive mode.
      • Proxy: Select to configure a proxy server.
      • Real time server: By default the Real time server field uses the value that you entered in the Host field.

        If you are using FTP server, then make sure you type in the Data Center Analytics server IP address that is processing the data of the primary server.

    NoteThe Analytics probe server must be reachable by Data Center Analytics server using the port 9092.
  10. Click Next.

    In addition to sending probe data to a single (local) Data Center Analytics server, you can configure a secondary, cloud-based Data Center Analytics server. The purpose is to host a copy of the probe data where it can be accessed outside of your internal network. You can add this secondary server from the Analytics probe server UI.

    NoteThe secondary Data Center Analytics server does not support real-time collection; the data may be received at different times from the Analytics probe server.
  11. In the Data Collection duration window, verify the license expiry date in your license, and then click Next.

  12. From the list of probes, select the probe type and configure it to collect data from the monitoring target. (You must add at least one probe to complete the installation)

    To add additional probes, go to the Analytics probe server web UI home page and click Add Probe. The following are available:
    • Hitachi Adaptable Modular Storage (AMS) probe

    • Hitachi Enterprise Storage probe

    • Hitachi NAS probe

    • IBM XIV® probe

    • EMC VMAX probe

    • EMC VNX Block probe

    • EMC VNX File probe

    • EMC XtremIO probe

    • NetApp probe

    • Pure Storage probe

    • VMware probe

    • Brocade Network Advisor probe

    • Cisco DCNM probe

    • Cisco SAN Switch probe

    • Linux probe

Initial setup of Infrastructure Analytics Advisor server

Set up the Infrastructure Analytics Advisor server, change the system account password, connect to the Data Center Analytics server, and then configure the mail server.

Logging on to Infrastructure Analytics Advisor server

Register the license for Infrastructure Analytics Advisor server, and then use the built-in account to log on to Infrastructure Analytics Advisor server.

Before you begin

  • Confirm that initial setup of the Data Center Analytics server and the Analytics probe server is complete.
  • Check the IP address or host name of the Infrastructure Analytics Advisor server.
  • Check the IP address of the Data Center Analytics server.
  • Obtain the Infrastructure Analytics Advisor server license from your Hitachi representative.

Procedure

  1. Add the Infrastructure Analytics Advisor server product URL to the list of exceptions in your browser's popup blocker.

  2. Enter the URL for the Infrastructure Analytics Advisor server in your web browser:

    http://host-name-or-IP-address-of-the-Infrastructure-Analytics-Advisor-server:22015/Analytics/login.htm
  3. In the logon window, click Licenses.

    1. Use either of the following methods:

      • Enter the license key
      • Specify the license file
    2. Click Save.

      The license is added in the list.
  4. To log on to the Infrastructure Analytics Advisor server, use these credentials:

    • User IDsystem
    • Passwordmanager

      (default)

Results

The logon is complete, and the Infrastructure Analytics Advisor server Dashboard displays.

Changing the system account password

Change the default password for the system account. The system account is a built-in account that has the user management permission, and permissions for all Infrastructure Analytics Advisor server operations.

  1. In the Administration tab, select User Management Users and Permissions.

  2. From the displayed dialog box, display Users, and then select System.

  3. Click Change Password.

Setting up a connection with Data Center Analytics server

Set up a connection so that the data collected by the Data Center Analytics server can be analyzed by the Infrastructure Analytics Advisor server.

Procedure

  1. In the Administration tab, select System Settings Data Center Analytics Server.

  2. Click Edit Settings, and specify the Data Center Analytics server information.

    NoteSpecify the built-in administrator account as the user account. If you want to use a different account, specify the account created during the initial setup of Data Center Analytics server. If you change the password of the specified user in the Data Center Analytics server, also change the same password in Password of the Edit Settings dialog box.
  3. Click Check Connection to confirm that the server is connected properly.

    If you cannot access the Data Center Analytics server, verify the following:
    • The certificate is correctly specified on the Infrastructure Analytics Advisor server.
    • The certificate is not expired.
  4. Click OK.

Results

The Data Center Analytics server is connected.

Configuring the mail server

Configure the mail server and the email address of the sender to notify the administrator of problems that occur in target resources and information related to Infrastructure Analytics Advisor server operations.

Before you begin

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

Procedure

  1. In the Administration tab, select Notification Settings Email Server.

  2. Click Edit Settings to specify information about the mail server.

  3. To verify mail server is configured correctly, click Send Test Mail.

  4. Confirm that the test email arrives, and then click Save Settings.

Default installation directory

The default installation directory for each component is as shown in the following table.

Component name

Default installation directory

Infrastructure Analytics Advisor server

In Windows

C:\Program Files\HITACHI

In Linux

/opt/hitachi

Data Center Analytics server

/data

Analytics probe server

/home

Configuration Manager REST API

/opt/HiCommand/ConfManager