© 2016, 2017 Hitachi, Ltd. All rights reserved. 1
RN-96HIAA000-07 (April 2017)
Hitachi Infrastructure Analytics Advisor
v3.0.0-01 Release Notes
About this document......................................................................................... 1
Intended audience ............................................................................................ 1
Getting help .................................................................................................... 1
About this release ............................................................................................ 2
Product package contents.................................................................................. 2
New features and important enhancements ......................................................... 3
System requirements........................................................................................ 3
Resolved problems ......................................................................................... 12
Known problems ............................................................................................ 15
Installation notes ........................................................................................... 19
Usage notes .................................................................................................. 20
Accessing documentation ................................................................................ 23
Copyrights and licenses .................................................................................. 23
About this document
This document (RN-96HIA000-07, April 2017) provides late-breaking information about
Hitachi Infrastructure Analytics Advisor 3.0.0-01. It includes information that was not
available at the time that the technical documentation for this product was published, as
well as a list of known problems and solutions.
Intended audience
This document is intended for customers and Hitachi Data Systems partners who license
and use Hitachi Infrastructure Analytics Advisor and Data Center Analytics.
Getting help
Hitachi Data Systems Support Connect is the destination for technical support of
products and solutions sold by Hitachi Data Systems. To contact technical support, log
on to Hitachi Data Systems Support Connect for contact information:
https://support.hds.com/en_us/contact-us.html.
Hitachi Data Systems Community is a global online community for HDS customers,
partners, independent software vendors, employees, and prospects. It is the destination
© 2016, 2017 Hitachi, Ltd. All rights reserved. 2
RN-96HIAA000-07 (April 2017)
to get answers, discover insights, and make connections. Join the conversation
today! Go to community.hds.com, register, and complete your profile.
About this release
These release notes cover Hitachi Infrastructure Analytics Advisor (HIAA) v3.0.0-01 and
Data Center Analytics (DCA).
This release resolves multiple known problems.
Product package contents
Media DVD-ROM Revision Release type
Software Hitachi Infrastructure Analytics Advisor 3.0.0-01 Full Package
For details on the paths of the installation scripts, see the following table.
Media Program to be installed Directory Installation program included
HIAA installation media
(Disk 1)
Infrastructure Analytics Advisor server (Linux)
Data Center Analytics server
/ANALYTICS/ analytics_install.sh
analytics_uninstall.sh
Infrastructure Analytics Advisor server (Windows)
/IAAWIN/ ANALYTICS.msi
Analytics probe server /DCAPROBE/ dcaprobe_install.sh
dcaprobe_uninstall.sh
agent_update.sh
Data Center Analytics server Windows-based probe
/DCAWINPROBE/ DCA_Windows_Probe.exe
Configuration Manager /CONFMANAGER/ install.sh
Data Center Analytics server (Upgrade patch)
/PATCH/DCA/v6.1 hdca-server-6.1-16082316.x86_64.rpm
Analytics probe server (Upgrade patch)
/PATCH/DCAPROBE/v6.1 hdca-probe-6.1-16082613.x86_64.rpm
Media Program to be installed Directory Installation program included
HIAA installation media
(Disk 2)
IAA server(Linux)
Data Center Analytics server
/ analytics_3.0.0-01.ova
Analytics probe server / dcaprobe_3.0.0-01.ova
© 2016, 2017 Hitachi, Ltd. All rights reserved. 3
RN-96HIAA000-07 (April 2017)
Configuration Manager
Data Center Analytics server Windows-based probe
/DCAWINPROBE/ DCA_Windows_Probe.exe
New features and important enhancements
Support for storage systems with the following firmware versions:
- VSP Gx00 models, VSP Fx00 models (83-04-02-XX/XX or earlier)
- VSP G1000, VSP G1500, VSP F1500 (80-05-03-XX/XX or earlier)
New reports that report on storage capacity and capacity trends are introduced in
Dashboard.
You can now access detail performance reports in Data Center Analytics for
resources that are being analyzed in the E2E view of Hitachi Infrastructure Analytics
Advisor.
6 months reports are available in the Detail window of Hitachi Infrastructure
Analytics Advisor for Hitachi storage pools.
This release enables collection of granular data for intelligent and deep analysis of
data when searching for spikes during trend pattern analysis of storage resources.
Provides the capability to generate recovery plans for processor and cache
bottlenecks.
The Execute Action function is enabled at additional entry points, allows for multiple
resources as target resources, and shows command line usage by definition in the
template file.
This version introduces new design improvements in web user interface.
Linux is supported as a monitoring target in Data Center Analytics. For a complete
list of supported management resources, see the Supported management resources
section in this document.
Logical Volume Manager (LVM) systems are supported as installation destination
devices for the Data Center Analytics server.
The following operating systems are now supported:
- Red Hat Enterprise Linux 7.0, 7.1
- Oracle Linux 7.0, 7.1
System requirements
For using installer
Infrastructure Analytics Advisor server
Operating system requirements (Windows)
© 2016, 2017 Hitachi, Ltd. All rights reserved. 4
RN-96HIAA000-07 (April 2017)
OS name OS version SP Architecture
Windows Server 2008 R2 (*1)
Standard Enterprise Datacenter
SP1 x64
Windows Server 2012 (*2) Standard Datacenter
No SP x64
Windows Server 2012 R2 (*2) Standard Datacenter
No SP x64
Operating system requirements (Linux)
OS name Yum/rpm dependencies Architecture
Red Hat Enterprise Linux 6.5 - 7.1
tcsh x64
Oracle Linux 6.7-7.1 (Unbreakable Enterprise Kernel)
Hardware requirements (Windows/Linux)
Prerequisite Minimum Recommended (Best
practice)
Processor Dual-Core processor Quad-Core processor
Memory 8 GB 16 GB minimum
Disk space 50 GB 100 GB minimum
(*1) Server core is not supported.
(*2) Server core and Minimal Server Interface are not supported.
Data Center Analytics server
Operating system requirements
© 2016, 2017 Hitachi, Ltd. All rights reserved. 5
RN-96HIAA000-07 (April 2017)
OS name Yum/rpm dependencies Architecture
Red Hat Enterprise Linux 6.5 - 7.1
- perl - java-1.8.0-openjdk update 91 or higher - expect - openssl-devel - parted - nss-3.21.0 or higher - gcc - unzip - perl-CPAN - expat-devel - sysstat - zip - bc - perl-XML-Simple(*1)
x64
Oracle Linux 6.7-7.1 (Unbreakable Enterprise Kernel)
(*1) The rpm dependencies only exist in the following OS:
- Red Hat Enterprise Linux 7.0 or later.
- Oracle Linux 7.0 or later.
Hardware requirements
Prerequisite Minimum Recommended (Best
practice (*1))
Processor Dual-Core processor Quad-core processor
Memory 8 GB 16 GB minimum
Disk space(*2) 150 GB 600 GB minimum
(*1) The memory requirement and the disk capacity vary depending on the amount or configuration of the managed resources. For example, if there are many volumes in the managed storage systems, the
volumes occupy much disk space in the database. If you decrease the interval at which you obtain performance information from the managed resources, the volumes occupy more disk space in the database.
(*2) Prepare a disk other than the disk of the operating system installed for installing the Data Center Analytics server. You must specify the disk to install the product in the installer (dcaserver_install.sh). Prepare a physical disk for installing the Data Center Analytics server on physical machines.
Analytics probe server
Operating system requirements
© 2016, 2017 Hitachi, Ltd. All rights reserved. 6
RN-96HIAA000-07 (April 2017)
OS name Yum/rpm dependencies Architecture
Red Hat Enterprise Linux 6.5 - 7.1
- perl - perl-CPAN - gcc - java-1.8.0-openjdk update 91 or higher - samba - expect - openssl-devel - ftp - unzip - wget - glibc.i686 - glibc.x86_64 - libstdc++.i686 - libstdc++.x86_64 - net-tools - tcsh - libyaml - libgcc.x86_64 - nss-softokn-freebl.x86_64 - iproute.x86_64 - ncurses - openssh-clients - nss-3.21.0 or higher - expat-devel - xinetd - sysstat - zip - bc - perl-XML-Simple(*1) - perl-Digest-MD5(*1)
x64
Oracle Linux 6.7-7.1 (Unbreakable Enterprise Kernel)
(*1) The rpm dependencies only exist in the following OS:
- Red Hat Enterprise Linux 7.0 or later.
- Oracle Linux 7.0 or later.
Hardware requirements
Prerequisite Minimum Recommended (Best practice)
(*)
Processor Dual-core processor Quad-core processor
Memory 8 GB 16 GB minimum
Disk space 100GB 150GB minimum
© 2016, 2017 Hitachi, Ltd. All rights reserved. 7
RN-96HIAA000-07 (April 2017)
(*) The memory requirement and the disk capacity vary depending on the amount or configuration of the managed resources. For example, if there are many volumes in the managed storage, the volumes occupy much disk space in the database. If you decrease the interval at which to obtain performance information from the managed resources, the volumes occupy more disk space in the database.
Configuration Manager
Operating system requirements
OS name Yum/rpm dependencies Architecture
Red Hat Enterprise Linux 6.5(*)-6.7
- x64 Oracle Linux 6.7-6.8 (Unbreakable Enterprise Kernel)
(*) The following package is required:
upstart-0.6.5-13.el6_5.3.x86_64 or later.
Hardware requirements
Prerequisite Minimum Recommended
Processor Dual-core processor Quad-core processor
Memory 2 GB 4 GB minimum
Disk space 0.8 GB -
Virtual appliance requirements
When the virtual appliance is deployed, a virtual machine with the following default
settings is created. Verify that the virtualization server has enough resources to
create the virtual machine.
Note: For questions related to the Oracle Linux OS that is packaged with this
product, contact Oracle customer support.
Infrastructure Analytics Advisor server and Data Center Analytics server
Guest operating system settings
© 2016, 2017 Hitachi, Ltd. All rights reserved. 8
RN-96HIAA000-07 (April 2017)
Item Settings
OS Oracle Linux 6.8 (Architecture x86_64)
Resource settings for the virtual machine
Item Settings
Processor Quad-core processor (the number of virtual sockets: 4, the number of cores per virtual socket: 1)
Memory 16 GB
Disk space [Initial settings] 200 GB (Configure as two separate disks.) - sda 100GB - LVM(DCAvg-DCAlv00) 100GB
(for Data Center Analytics server installation)
[Recommended settings] 700GB - sda 100GB - LVM(DCAvg-DCAlv00) 600GB
(for Data Center Analytics server installation)
Note: The default installation directory is as follows.
- The Infrastructure Analytics Advisor server directory is /opt/hitachi.
- The Data Center Analytics server directory is /data.
Analytics probe server and Configuration Manager
Guest operating system settings
Item Settings
OS Oracle Linux 6.8 (Architecture x86_64)
Resource settings for the virtual machine
Item Settings
Processor Quad-Core processor (the number of virtual sockets: 4, the number of cores per virtual socket: 1)
Memory 10 GB
Disk space 110 GB
Note: The default installation directory is as follows.
- The Analytics probe server directory is /home.
- The Configuration Manager directory is /opt/HiCommand.
Browser requirements
Web browser/other Version
Firefox ESR 45
© 2016, 2017 Hitachi, Ltd. All rights reserved. 9
RN-96HIAA000-07 (April 2017)
Web browser/other Version
Internet Explorer 11
Chrome for Work Latest version of stable channel
Flash Player
21.0 or later
(to use custom reports in Data Center Analytics server GUI)
Management target requirements
Supported management resources
The following tables show the monitoring targets of Infrastructure Analytics Advisor
server.
Storage
Storage system Microcode version/HNAS model
Analytics probe name
Hitachi Virtual Storage Platform 07-01 or later Hitachi Enterprise Storage probe (*1)
Hitachi Unified Storage VM 73-01 or later
Hitachi Virtual Storage Platform G200
83-01 or later
Hitachi Virtual Storage Platform G400
Hitachi Virtual Storage Platform G600
Hitachi Virtual Storage Platform G800
Hitachi Virtual Storage Platform F400
83-01 or later
Hitachi Virtual Storage Platform F600
Hitachi Virtual Storage Platform F800
Hitachi Virtual Storage Platform G1000
80-01 or later
Hitachi Virtual Storage Platform G1500
80-05 or later
Hitachi Virtual Storage Platform F1500
© 2016, 2017 Hitachi, Ltd. All rights reserved. 10
RN-96HIAA000-07 (April 2017)
Storage system Microcode version/HNAS model
Analytics probe name
Hitachi Unified Storage 110 09-10 or later Hitachi Adaptor Modular Storage probe
Hitachi Unified Storage 130
Hitachi Unified Storage 150
HNAS 3090 HNAS probe (*2)
Hypervisors
Product name Version Analytics Probe name
VMWare vCenter Server 5.0 or later VMWare probe
VMware ESXi 5.0 or later
Hyper-V Windows Server 2008 R2 Hyper-V
Hyper-V 2.0 Windows-based probe
Windows Server 2012 Hyper-V
Hyper-V 3.0
Windows Server 2012 R2 Hyper-V
Hyper-V 3.1
Hosts
OS name Version/Edition Analytics Probe name
Windows Windows Server 2008 • Standard
• Enterprise
• Datacenter
Windows-based probe
Windows Server 2008 R2 • Standard
• Enterprise
• Datacenter
Windows Server 2012 • Standard
• Datacenter
Windows Server 2012 R2 • Standard
• Datacenter
Linux Red Hat Enterprise Linux • 6.5
• 7.1
Linux Probe (*2)
© 2016, 2017 Hitachi, Ltd. All rights reserved. 11
RN-96HIAA000-07 (April 2017)
SUSE Linux Enterprise Server
• 11
• 12
Oracle Linux 7.0
CentOS 6.6
FC switches
Switch name Version Analytics probe name
Brocade Brocade Network Advisor Professional Plus
12.3.1 Brocade Network Advisor probe
Brocade Network Advisor Enterprise
12.3
Brocade Network Advisor • 12.3.3
• 12.4.1
• 12.4.2
• 12.4.4
• 14.0.1
Cisco Cisco Data Center Network Manager
• 6.3
• 7.1
Cisco DCNM probe
Cisco SAN Switch (CLI) - Cisco SAN Switch probe (*2)
(*1) When using Hitachi Enterprise Storage probe, make sure that the RAID Manager LIB is installed on the same host as the Hitachi Enterprise Storage probe.
(*2) The data collected by the probe can be viewed in DCA server but cannot be analyzed by the IAA server.
Related products
To manage additional information about Hitachi storage systems (such as
information about storage capacity and hosts), use the following products:
Hitachi Device Manager version 8.4.1 or later
License keys
The Hitachi Infrastructure Analytics Advisor product requires a license key.
In addition, the Data Center Analytics server and the Analytics probe server also
require a license key.
Obtain license keys from your HDS representative.
© 2016, 2017 Hitachi, Ltd. All rights reserved. 12
RN-96HIAA000-07 (April 2017)
Resolved problems
From 3.0.0-00 to 3.0.0-01
Resolved problems for Infrastructure Analytics Advisor server
The following table lists the problems that are resolved in this release by defect ID.
Defect ID Problems
IAS-070024 Dynamic threshold values are not displayed for some metrics.
IAS-010132 The HIAA server will try to authenticate users even if you set the authentication field
to "OFF" and authentication of the mail server to optional in the Administration tab of the Email Server Settings window.
IAS-010136 When performing the Execute Action by selecting a resource from those listed below on the bottleneck analysis window, an error is shown:
VMWare Virtual CPU
VMWare Virtual Disk Partition
Virtual Disk
VMWare Virtual NIC
Hyper-V Virtual Storage Device
Hyper-V Virtual Network Adapter
Hyper-V Virtual Hypervisor Virtual Processor
IAA-070022 If the Data Center Analytics server has not started when the Infrastructure Analytics Advisor server starts, the following two events are shown in the System Events tab:
• An error occurred in the processing to migrate the database. Take the follow
actions to make sure that communication with the Data Center Analytics server is possible.
1. Confirm that Data Center Analytics server started.
2. In the Administration tab, select System Settings > Data Center Analytics server.
3. Click Edit Settings, and Check Connection to check if the Data Center Analytics server is connected properly.
4. Click OK.
If the problem persists, collect the log information, and then contact the system administrator.
• A communication error occurred during an attempt to change the plan.
IAS-070023 The I/O control settings for Automation Director fail when a target storage includes one or more I/O control settings for a volume using an iSCSI port.
Resolved problems for Data Center Analytics server
The following table lists the problems that are resolved in this release by defect ID.
Defect ID Problems
20583 The Web Socket was returning data in Data Center Analytics server time zone.
Web Socket now returns data in UTC time zone as default. To obtain data in a
different time zone, you have to use the utcOffset parameter to specify the new
time zone value.
© 2016, 2017 Hitachi, Ltd. All rights reserved. 13
RN-96HIAA000-07 (April 2017)
Resolved problems for Data Center Analytics Windows-based probe
The following table lists the problems that are resolved in this release by defect ID.
Defect ID Problems
20253 The Windows-based probe stops soon after it is launched.
From 2.1.0-02 to 3.0.0-00
Resolved problems for Infrastructure Analytics Advisor server
The following table lists the problems that are resolved in this release by defect ID.
Defect ID Problems
IAA-06279 The following field in "Edit Consumer" may not be updated.
• Grade
IAA-06326 In the following windows, the number of components listed in the Available Components table and Selected Components table is limited to 30:
• Analytics tab > Sparkline View > Show Performance > Select Component
• Administration tab > Monitoring Settings > User Resource Threshold Profiles > Threshold Profile > Target Resources > Resources > Threshold Detail > Select Component
IAS-10016 When you select a resource in E2E View and open "Show Detail", the display value of "Capacity Saving" in the "Pool information" is incorrect.
[2.1.0-02 / 3.0.0-00 or later]
Disabled / Deduplication not available
Compression / Deduplication not available
Compression and Deduplication / Deduplication available
IAS-10049 If the path of the installation folder contains “ “ (blank space), the following command fails.
reloadtemplate
encryptpassword
IAS-10125 Discovered hosts are not automatically assigned to the corresponding threshold profile even if there are Host Assignment Rules.
IAS-70005 In [Dashboard Setting], each item in the [Report to Display] table is displayed in duplicate form when all the following conditions are met:
Log on as the user without "Admin" permission and open [Dashboard Setting].
Change radio button from "Default Settings" to "Custom Settings".
IAS-70015 Uninstallation of RAID Agent fails because the permission to execute the script for uninstalling RAID Agent was not granted.
In 2.1.0-02, this problem can be avoided by granting permission to execute the following script.
/DCAPROBE/AGENTS/Agent_for_RAID/uninstall.sh
© 2016, 2017 Hitachi, Ltd. All rights reserved. 14
RN-96HIAA000-07 (April 2017)
Resolved problems for Data Center Analytics server
The following table lists the problems that are resolved in this release by defect ID.
Defect ID Problems
16309 Alerts created for VSP/HUS-VM resources are also applied on VSP G1000/Gx00 resources.
16842 On the Alert Violation tab, in the alert details the Triggered At field displays the wrong time if the machine time zone is set to any other than GMT.
18449 While adding a new indicator, when the user clicks the Cancel button, the Add Alert that appears does not display Yes and No options to cancel the operation.
18492 While adding an alert or indicator, the drop-down list can display duplicate metric entries.
18612 In the Global Search, entering a space displays all resources for all tree nodes.
18656 While adding the alert, in the Alert Notification section, an error is shown in
the following scenario: If the email address after the @ contains a period, then
the special character and numbers are not allowed after this period.
Examples of email ids that are allowed: [email protected] [email protected] [email protected] [email protected]
Examples of email ids that are not allowed: [email protected].
18668 The Import threshold does not work on an Internet Explorer browser.
18697 The Global Search does not search by switch IP address for Brocade Network
Advisor and for VM clusters.
Resolved problems for Analytics probe server
The following table lists the problems that are resolved in this release by defect ID.
Defect ID Problems
18298 For the EMC VMAX probe, Unisphere version 8.2, performance data of the Port
Group is not collected.
Resolved problems for Data Center Analytics Windows-based probe
The following table lists the problems that are resolved in this release by defect ID.
Defect ID Problems
18491 FTP to HDCA Server does not work after upgrade of the Windows-based probe
when FIPS compliance is enabled.
© 2016, 2017 Hitachi, Ltd. All rights reserved. 15
RN-96HIAA000-07 (April 2017)
Known problems
Known problems for the Infrastructure Analytics Advisor server
The following table lists the known problems in this current release of Infrastructure
Analytics Advisor server by defect ID.
Defect ID Problem Workaround/Comments
IAA-06327 IP address information does not display for the following storage systems:
• Hitachi Virtual Storage Platform
• VSP G1000
• VSP G1500
• VSP F1500
• VSP Gx00 models
• VSP Fx00 models
• Hitachi Unified Storage VM
No workaround.
IAA-06328 Parity groups of external storage do not display. No workaround.
IAA-06817 When a virtual machine on Hyper-V is monitored with
the Data Center Analytics server Windows-based probe, the relation between the FC switch and host is not displayed.
No workaround
IAA-06385 If you have a VM as a base point to display the E2E view, in the disk list, a disk other than the disk displayed in the E2E view displays.
No workaround
IAA-06331 Performance events for the following metrics are not detected:
• Total IOPS (Pool)
• Read Hit (Parity Group)
• Utilization (Parity Group)
No workaround.
IAA-06717 The relationships between the storage systems and
pass-through disks that are connected to virtual machines on Hyper-V are not displayed.
No workaround.
IAA-06819 When the following characters are included in configuration information of the monitoring target, you may not be able to monitor that target.
- Multi byte character
- ”[”, ”]”, ”{”, ”}”, ”,”,”(”,”)”
For the monitoring target that cannot be monitored,
the KNAQ33033-I message is output to the log. You may also see the KNAQ01000-E error message.
No workaround
IAA-06836 A "Threshold" displayed in the table of "Threshold Detail" page may not display correctly.
No workaround
© 2016, 2017 Hitachi, Ltd. All rights reserved. 16
RN-96HIAA000-07 (April 2017)
IAA-06858 If you assign resources from dynamic threshold type
to another target monitoring profile, the existing monitoring profile name can be displayed if that occurs after the reassignment.
Reassign the resources to the old
monitoring profile after the dynamic threshold calculation of the monitoring profile is completed.
Then, assign the resources to the new target monitoring profile.
Review the log to verify an entry for the KNAQ33008-I message that confirms the completion of the dynamic threshold calculation of the monitoring profile.
IAA-06897 The status of a resource is not changed even when the
monitoring mode is changed from “ON”, “Static” or “Dynamic” to “OFF”.
Please restart IAA 24 hours after you change the monitoring mode.
IAA-07410 It is not able to change the case of definition set by user saved via HIAA.
No workaround
IAA-07418 When you select a component from "Access Path Usage (CHA ESW)" in Sparkline view and open the bottleneck analysis window, only one port is displayed even if additional ports are related.
No workaround
Known problems for the Data Center Analytics server
The following table lists the known problems in the current release of Data Center
Analytics server by defect ID.
Defect ID Problem Workaround/Comments
14858 Wrong CPU and Memory Utilization are observed for the switch of Cisco DCNM.
No workaround.
15588 You cannot download the diagnostic data from the Data Center Analytics server after upgrading from base version 5.0 to any later versions.
Log on to SSH client
like PuTTY. Run the
following command:
$ sudo
/usr/local/megha/bin/diag.sh
It collects the diagnostic dump and saves it on the following
location
/usr/local/megha/tmp with
the following name:
diag_20160503070628.gz
17537 The user from the Active Directory group can log on using the user@domain format. However, the user
cannot log on using the domain\username format.
No workaround.
17919 Chart Reports are not plotted for Ports instances even though data is available No workaround.
18382 A chart report does not get exported if its chart
type is ‘Stack’ and the scale is ‘Logarithmic’. Change the plot, scale type for that report and perform Batch Export.
19132 When you upgrade the Data Center Analytics server to v8.0 using RPM on OEL 7.0 or RHEL 7.1, several warning messages are displayed.
Ignore the warning message and continue with the upgrade.
© 2016, 2017 Hitachi, Ltd. All rights reserved. 17
RN-96HIAA000-07 (April 2017)
19003 Global search functionality slows down when there are a large number of resources on Data Center Analytics server.
No workaround
19708 Alert violations for the Alert definitions created before upgrading are not shown in the UI after upgrade. This is intermittently observed for the data collected in real time.
No workaround.
20174 Sometimes real time data is not shown in the chart reports even though it is available with the server. You must restart the megha jetty
service to view the data in chart reports:
1. Stop the megha service using the command: /usr/local/megha/bin/megha-jetty.sh stop
2. Verify the stopped status of megha service: /usr/local/megha/bin/megha-jetty.sh status
3. Start the megha service using the command: /usr/local/megha/bin/megha-jetty.sh start
20442 When you upgrade the Data Center Analytics server,
the advertised.listeners property is not updated with Data Center Analytics server IP.
1. Log on to the Data Center
Analytics server through an SSH client (like PuTTY) using the following credentials:
• User: root
• Password: megha.jeos
2. Switch to megha user, using the
command: su megha
3. Stop Kafka and Redis server: /usr/local/megha/bin/manage-kafka.sh stop
/usr/local/megha/bin/manage-redis.sh stop_All
4. Start the Kafka and Redis servers: usr/local/megha/bin/manage-kafka.sh start /usr/local/megha/bin/manage-redis.sh start_All
5. Verify the Data Center Analytics server IP addresses is in following property file: “/usr/local/megha/kafka/config/server.properties" against property “advertised.listeners="
20449 Real time alerts sometimes are received at 5 minutes’ interval even if minute interval condition is met. No workaround.
20461 In the tree designer, the Active Directory group user cannot publish the imported schema on the new Data
Center Analytics server.
No workaround.
20492 In the tree designer, instances are not getting added to appropriate node when there are more than one node with the same name.
No workaround.
© 2016, 2017 Hitachi, Ltd. All rights reserved. 18
RN-96HIAA000-07 (April 2017)
20397 In the tree designer > customized tree, when user try to add Indicators for Switches, all the related resources are not listed.
No workaround.
20488 In the tree designer, for a published tree you cannot rename a node if its parent node is a placeholder node.
No workaround.
20474 When editing a published tree in the tree designer, only the schema and reports are displayed (no instances).
No workaround.
20439 In the tree designer, for a published tree you cannot rename a node if the new name is the same but with different capitalization.
No workaround.
20412 In the tree designer, after adding an existing report to the LDEV group level instance, an additional report is added with an invalid query.
No workaround.
IAA-07544 In the output of the installer console, you may see the following message after entering the device name to store application.
Failed to find device for physical volume specified in the device or Failed to find physical volume
This does not affect the installation of the Data Center Analytics server.
Ignore the message and continue with the installation.
IAS-010149 Users in the Normal group can perform operations with privileges equivalent to those with Administrator authority.
No workaround.
20770 Alert notification email subject shows incorrect time for hourly notification.
No workaround.
Known problems for the Analytics probe server
The following table lists the known problems in the current release of Analytics probe
server by defect ID.
Defect ID Problem Workaround/Comments
17537 The user in the Active Directory group can log on using the user@domain format. However, the user cannot
log on using the domain\username format.
No workaround.
17974 In the Summary report, some values are shown as
‘NA’ for Cisco SAN Switches. No workaround.
18659 While adding the Hitachi Adaptable Modular Storage
(AMS) probe, an Invalid message is displayed. In the following location:
/usr/local/megha/logs/ams in the
in utl*.inf files, comment the
entry of the registered AMS using
#.
19132 When you upgrade the Data Center Analytics probe to
v8.0 using RPM on OEL 7.0 or RHEL 7.1, several
warning messages are displayed.
Ignore the warning message and continue with the upgrade.
20131 You cannot add the NetApp probe when TLS = off.
1. Log on to NetApp Storage System.
2. Run the command: options
tls.enable off
3. Verify the TLS Status option is On.
© 2016, 2017 Hitachi, Ltd. All rights reserved. 19
RN-96HIAA000-07 (April 2017)
20494 Real time data is not sent from probe if Kafka is not
running. Even when Kafka server is recovered it
requires a probe restart to start transmitting
automatically.
Stop and start the real time data collection for the specific probe that is showing this error.
070027 When the virtual appliance is deployed and the
Analytics probe server is set up with the hvacomfig
command, sometimes you might not be able to access
the Analytics probe server via the Web browsers.
1. Stop the probe service using the command:
# /usr/local/megha/bin/megha-jetty.sh stop
2. Start the probe service using the command:
# /usr/local/megha/bin/megha-jetty.sh stop
Installation notes
• If the installation of Infrastructure Analytics Advisor server on Windows failed, do the
following procedure.
Procedure
1. Backup registry
Start the registry editor by clicking Start and then Run, and then entering regedit.
Then, export the whole registry.
2. Delete the following registry keys, if they exist.
• HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products\< HIAA User
Data Code>
• HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\
UserData\S-1-5-18\Products\< HIAA User Data Code>
• HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
\< HIAA Product Code>
Note: Registry information of Hitachi Infrastructure Analytics Advisor server vary with
versions. Refer to the following table for registry values relevant to the product version.
Name in the
procedure
version Registry value
HIAA User Data Code 2.0.0-02 0E19CA03B15A77F489452ECA1E03754A
2.1.0-01 8D7A275629D579948B484350182BCC9A
2.1.0-02 F2B317B6467E1474FA84579F8B36E45F
3.0.0-00 A5F47144E8BE2F74ABFCF66AC58B09FC
HIAA Product Code 2.0.0-02 {30AC91E0-A51B-4F77-9854-E2ACE13057A4}
2.1.0-01 {6572A7D8-5D92-4997-B884-340581B2CCA9}
2.1.0-02 {6B713B2F-E764-4741-AF48-75F9B8634EF5}
3.0.0-00 {44174F5A-EB8E-47F2-BACF-6FA65CB890CF}
3. Install Infrastructure Analytics Advisor server.
© 2016, 2017 Hitachi, Ltd. All rights reserved. 20
RN-96HIAA000-07 (April 2017)
• If you want to use Oracle JDK instead of Open JDK, perform the following procedure
for each Data Center Analytics server and each Analytics probe server:
1. Log in to the server.
2. Install the Oracle JDK to the target server.
3. Execute the following command to set the default Java installation to the Oracle
JDK.
# alternatives --install /usr/bin/java java <OracleJDK path>/bin/java 1 # alternatives --set java <OracleJDK path>/bin/java # alternatives --install /usr/lib/jvm/jre-1.8.0 jre_1.8.0 <OracleJDK path>/jre 1
# alternatives --set jre_1.8.0 <OracleJDK path>/jre # echo "export JAVA_HOME=/usr/local/java_home" > /etc/profile.d/java_home.sh # source /etc/profile.d/java_home.sh # alternatives --install /usr/local/java_home java_home <OracleJDK path> 1 # alternatives --set java_home <OracleJDK path>
4. Execute the following command to set the default keytool installation to the
keytool of Oracle JDK.
# alternatives --install /usr/bin/keytool keytool <OracleJDK path>/bin/keytool 1
# alternatives --set keytool <OracleJDK path>/bin/keytool
• To install the Windows-based probe, do the following procedure.
Procedure
1. Run the DCA_Windows_Probe.exe to install the Windows-based probe.
2. If you have the DCA_Windows_Probe_Patch.exe, run the
DCA_Windows_Probe_Patch.exe to install the patch version.
Usage notes
• When you set up the Hitachi Enterprise Storage probe, use the default value for the
RAID Agent collection interval except the "PLC (Pool Configuration)". Set 60 for the
"PLC (Pool Configuration)" collection interval.
When you delete the monitoring target from the Analytics probe server, reboot the
Infrastructure Analytics Advisor server after 24 hours. If you fail to reboot, the
Infrastructure Analytics Advisor server will not show the most up-to-date status of
resources and instead continues to display the status before the deletion of the
monitoring target.
When a virtual machine is migrated by using Hyper-V's live migration function, the
virtual machine before migration and the one after migration are recognized as two
different virtual machines, and information about performance and configuration is
not inherited.
© 2016, 2017 Hitachi, Ltd. All rights reserved. 21
RN-96HIAA000-07 (April 2017)
In the following dashboards, information is displayed based on the latest value in
the past 24 hours. In addition, the item displaying the total value of multiple
resources shows the total value of all the related resources in the last 24 hours.
For example, in "Recent Capacity by Consumer", it aggregates volumes which are
currently related, and also volumes which are removed from the consumer within
the last 24 hours.
Capacity by Storage System
Capacity by Storage System (HUS 100 Storage Systems)
Capacity of Drive Types by Storage System (HDP)
Capacity of Drive Types by Storage System (HDT)
Capacity of Drive Types by Storage System (HUS 100 Storage Systems)
Capacity by Pool
Capacity by Pool (HUS 100 Storage Systems)
Capacity by Consumer
Capacity by Consumer in the Past 6 Months
Capacity by Consumer (HUS 100 Storage Systems)
Capacity by Consumer in the Past 6 Months (HUS 100 Storage Systems)
When using I/O activity with Automation Director, the minimum supported version
is 8.5.0.
The Data Center Analytics Windows-based probe requires Microsoft .NET Framework
3.5.
Without intervention, the amount of disk space used by the Data Center Analytics
continues to increase. Therefore, monitor the disk usage and expand it if needed.
The disk usage can be monitored through the Data Center Analytics server. You can
configure an alert notification email when disk capacity runs short.
For instructions on setting up the mail server, refer to "Configuring the SMTP
server" in the Hitachi Data Center Analytics User Guide.
Use the following procedure to monitor disk capacity with Data Center Analytics
server alerts:
1. In the application bar area, click the Alerts menu, and select Definitions.
2. Select the System Alerts tab.
3. Select System Disk Usage and click Subscribe.
4. In the Subscribe for System Disk Usage window, select the Email tab.
5. Enter email addresses separated by commas.
6. Click Subscribe.
For details, please refer to "Monitoring Data Center Analytics server alerts" in the
Hitachi Data Center Analytics User Guide.
“Display internet sites in compatibility view” in Internet Explorer 11 is not supported
by Data Center Analytics UI or Analytics probe UI. When you access the Data Center
© 2016, 2017 Hitachi, Ltd. All rights reserved. 22
RN-96HIAA000-07 (April 2017)
Analytics UI or Analytics probe UI by using Internet Explorer 11, do not specify the
option "Display internet sites in compatibility mode".
There may be a warning about Hitachi Storage capacity on the [Home] page and
[License Information] page for Data Center Analytics server.
This does not affect the Data Center Analytics server.
Please check the license page for the Infrastructure Analytics Advisor server to
confirm the Hitachi Storage license information.
Error handling procedures
This section describes the procedures for handling errors that may occur when using
Infrastructure Analytics Advisor server. Install the following package:
java-1.7.0-openjdk-devel
Check the messages
If a problem occurs, check any messages output to the UI or log files, and then
follow the instructions provided. In addition, check the log files to determine the
cause of the problem, and then take appropriate action.
Follow the troubleshooting steps
If no messages are output when a problem occurs, or you are unable to correct the
problem even after following the instructions in the message, collect maintenance
information, and then contact customer support.
Collecting maintenance information
Collecting the log file for the Infrastructure Analytics Advisor server
1. Run the hcmds64getlogs command.
Collecting the log file of the Data Center Analytics server
1. In the browser, type the Data Center Analytics server URL
https://<ip_address>:<Port-Number>.
2. Log on to Data Center Analytics server.
3. On the Home page, from the Application menu, click Manage.
4. In the Manage window, click the Download Diagnostic Data link.
5. In the Download Diagnostic Data window, click Download to download the
file.
Collecting the log file for the Analytics probe server
1. In the browser, type the Analytics probe server URL https://<ip_address>:<Port-
Number>.
2. Log on to Analytics probe server.
© 2016, 2017 Hitachi, Ltd. All rights reserved. 23
RN-96HIAA000-07 (April 2017)
3. Do steps 3 to 5 from the preceding task.
Collecting the log file for the RAID Agent
To do the following procedure, you must use an OS user account with root user
permissions:
1. Log on to the host on which the Analytics probe server is installed.
2. Run the jpcras command with the following specific information: the information
to be collected and the directory in which to store the collected information.
The following is an example of how to run the jpcras command to collect all
information and store the collected information in the /tmp/jpc/agt directory:
/opt/jp1pc/tools/jpcras /tmp/jpc/agt all all
The collected information is compressed by the tar command and the compress
command, and then stored in the specified directory. The file name is as follows:
jpcrasYYMMDD.tar.Z
Where YYMMDD represents the year, month, and date.
Accessing documentation
This section lists the Infrastructure Analytics Advisor user documentation. Product
documentation is available on Hitachi Data Systems Support Connect:
https://knowledge.hds.com/Documents. Check this site for the most current
documentation, including important updates that may have been made after the release
of the product
Document name Document number
Hitachi Infrastructure Analytics Advisor User Guide
MK-96HIAA001
Hitachi Infrastructure Analytics Advisor Installation and Configuration Guide
MK-96HIAA002
Hitachi Infrastructure Analytics Advisor REST API Reference Guide
MK-96HIAA003
Hitachi Infrastructure Analytics Advisor Data Analytics and Performance Monitoring Overview
MK-96HIAA004
Hitachi Data Center Analytics User Guide
MK-96HDCA002
Hitachi Data Center Analytics REST API Reference Guide
MK-96HDCA006
Hitachi Data Center Analytics Query Language User Guide
MK-96HDCA005
Documentation errata
Corrections to the Hitachi Infrastructure Analytics Advisor Installation and
Configuration Guide:
© 2016, 2017 Hitachi, Ltd. All rights reserved. 24
RN-96HIAA000-07 (April 2017)
No. Correction location Correction
1 Infrastructure Analytics Advisor overview
From Infrastructure Analytics Advisor collects and correlates data from these sources: • Hitachi storage systems • Brocade and Cisco fibre channel switches • Microsoft and VMware hypervisors • Linux hosts
To Infrastructure Analytics Advisor collects and correlates data from these sources: • Hitachi storage systems • HP P9500 Storage and HP XP7 Storage • Brocade and Cisco fibre channel switches • Microsoft and VMware hypervisors • Windows hosts • Linux hosts
2 Data Center Analytics
server requirements Table 7 Hardware requirements
From Prepare a disk other than the one on the OS on which Data Center
Analytics server is installed. You must specify the disk for installing the product when you run the installation
command dcaserver_install.sh. You must prepare a physical disk for
installing the Data Center Analytics server on physical machines.
To Prepare a disk other than the one on the OS on which Data Center Analytics server is installed. You must specify the disk for installing the product when you run the installation
command analytics_install.sh. You must prepare a physical disk for
installing the Data Center Analytics server on physical machines.
3 Upgrade workflow for a two-host configuration Back up the Infrastructure Analytics Advisor
system and stop system services step 3
From Stop the Data Center Analytics server or Analytics probe server service
To Stop the Data Center Analytics server and Analytics probe server service
4 Restoring Infrastructure Analytics Advisor server settings information
From Make sure that the following items are the same between the backup source host and the restore-destination host:
○ Infrastructure Analytics Advisor server installation destination
directory
To Make sure that the following items are the same between the backup source host and the restore-destination host:
○ Infrastructure Analytics Advisor server installation destination
directory If you are doing the restore as part of the procedure for changing the installation directory of Infrastructure Analytics Advisor server, the installation directory of the backup-source host and restore-destination host do not need to match.
5 Infrastructure Analytics Advisor server requirements Table 2 Operating system requirements (Linux) Supported OS
From Red Hat Enterprise Linux 6.5-6.7 Oracle Linux 6.7-6.8 (Unbreakable Enterprise Kernel)
To Red Hat Enterprise Linux 6.5-7.1 Oracle Linux 6.7-7.1 (Unbreakable Enterprise Kernel)
© 2016, 2017 Hitachi, Ltd. All rights reserved. 25
RN-96HIAA000-07 (April 2017)
6 Data Center Analytics server requirements Table 5 Operating system requirements Supported OS
From Red Hat Enterprise Linux 6.5-6.7 Oracle Linux 6.7-7.0 (Unbreakable Enterprise Kernel)
To Red Hat Enterprise Linux 6.5-7.1 Oracle Linux 6.7-7.1 (Unbreakable Enterprise Kernel)
7 Data Center Analytics server requirements Table 5 Operating system requirements Yum/rpm dependencies
From • java-1.8.0-openjdk • expect • parted • openssl-devel • xfsprogs • nss-3.21.0 or higher • gcc • unzip • perl • perl-CPAN • expat-devel • sysstat • zip
To • java-1.8.0-openjdk update91 or higher • expect • parted • openssl-devel • nss-3.21.0 or higher • gcc • unzip • perl • perl-CPAN • expat-devel • sysstat • zip • bc • perl-XML-Simple(*1) (*1) The rpm dependencies only exists in the following OS. - Red Hat Enterprise Linux 7.0 or later. - Oracle Linux 7.0 or later.
8 Analytics probe server requirements Table 11 Operating system requirements Supported OS
From Red Hat Enterprise Linux 6.5-6.7 Oracle Linux 6.7-7.0 (Unbreakable Enterprise Kernel)
To Red Hat Enterprise Linux 6.5-7.1 Oracle Linux 6.7-7.1 (Unbreakable Enterprise Kernel)
© 2016, 2017 Hitachi, Ltd. All rights reserved. 26
RN-96HIAA000-07 (April 2017)
9 Analytics probe server requirements Table 11 Operating system requirements Yum/rpm dependencies
From • perl • perl-CPAN • gcc • java-1.8.0-openjdk • samba • expect • openssl-devel • ftp • unzip • wget • glibc.i686 • glibc.x86_64 • libstdc++.i686 • libstdc++.x86_64 • net-tools • tcsh
• libyaml • libgcc.x86_64 • nss-softoknfreebl.x86_64 • iproute.x86_64 • ncurses • openssh-clients • nss-3.21.0 or higher • expat-devel • xinetd • sysstat • zip
To • perl • perl-CPAN • gcc • java-1.8.0-openjdk • samba • expect • openssl-devel • ftp • unzip • wget • glibc.i686 • glibc.x86_64 • libstdc++.i686 • libstdc++.x86_64 • net-tools • tcsh • libyaml • libgcc.x86_64 • nss-softoknfreebl.x86_64 • iproute.x86_64 • ncurses • openssh-clients • nss-3.21.0 or higher • expat-devel • xinetd • sysstat
• zip • bc • perl-XML-Simple(*1) • perl-Digest-MD5(*1) (*1) The rpm dependencies only exists in the following OS. - Red Hat Enterprise Linux 7.0 or later. - Oracle Linux 7.0 or later.
© 2016, 2017 Hitachi, Ltd. All rights reserved. 27
RN-96HIAA000-07 (April 2017)
10 Installing Infrastructure Analytics Advisor server and Data Center Analytics server on a Linux host Table 25 Data Center Analytics server installation prerequisites (Linux) Install the following yum/rpm dependency packages
From [About Prerequisites column] Install the following yum/rpm dependency packages • java-1.8.0-openjdk • expect • parted • openssl-devel • nss-3.21.0 or higher • gcc • unzip • perl • perl-CPAN • expat-devel • sysstat • zip • xfsprogs
[About Description column] 3. Run the yum command to install the dependency packages: yum install java-1.8.0-openjdk expect parted openssl-devel nss-3.21.0 gcc unzip perl perl-CPAN expat-devel sysstat zip /media/OSImage/ScalableFileSystem/xfsprogs-3.1.1-16.el6.x86_64.rpm The package xfsprogs-3.1.1-16.el6.x86_64.rpm differs depending on your environment. The package nss-3.21.0 may not be included in the Linux OS media of certain versions. Obtain this package from the Linux website or the Linux OS media of version 6.8 or later.
To [About Prerequisites column] Install the following yum/rpm dependency packages • java-1.8.0-openjdk • expect • parted • openssl-devel • nss-3.21.0 or higher • gcc • unzip • perl • perl-CPAN • expat-devel • sysstat • zip • bc • perl-XML-Simple(*1) (*1) The rpm dependencies only exists in the following OS. - Red Hat Enterprise Linux 7.0 or later. - Oracle Linux 7.0 or later. [About Description column] 3. Run the yum command to install the dependency packages: yum install java-1.8.0-openjdk expect parted openssl-devel nss-
3.21.0 gcc unzip perl perl-CPAN expat-devel sysstat zip The package nss-3.21.0 may not be included in the Linux OS media of certain versions. Obtain this package from the Linux website or the Linux OS media of version 6.8 or later.
© 2016, 2017 Hitachi, Ltd. All rights reserved. 28
RN-96HIAA000-07 (April 2017)
11 Installing Analytics probe server on a Linux host Preparing for installation Install the following yum/rpm dependency packages
From [About Prerequisites column] • perl • perl-CPAN • gcc • java-1.8.0-openjdk update 91 or higher • samba • expect • openssl-devel • ftp • unzip • wget • glibc.i686 • glibc.x86_64 • libstdc++.i686 • libstdc++.x86_64 • net-tools
• tcsh • libyaml • libgcc.x86_64 • nss-softokn-freebl.x86_64 • iproute.x86_64 • ncurses • openssh-clients • nss-3.21.0 or higher • expat-devel • xinetd • sysstat • zip
To [About Prerequisites column] • perl • perl-CPAN • gcc • java-1.8.0-openjdk update 91 or higher • samba • expect • openssl-devel • ftp • unzip • wget • glibc.i686 • glibc.x86_64 • libstdc++.i686 • libstdc++.x86_64 • net-tools • tcsh • libyaml • libgcc.x86_64 • nss-softokn-freebl.x86_64 • iproute.x86_64 • ncurses • openssh-clients • nss-3.21.0 or higher • expat-devel
• xinetd • sysstat • zip • bc • perl-XML-Simple(*1) • perl-Digest-MD5(*1) (*1) The rpm dependencies only exists in the following OS. - Red Hat Enterprise Linux 7.0 or later. - Oracle Linux 7.0 or later.
© 2016, 2017 Hitachi, Ltd. All rights reserved. 29
RN-96HIAA000-07 (April 2017)
Correction: Added the followings as prerequisites
Preparing for upgrade
Infrastructure Analytics Advisor server upgrade prerequisites (Linux)
Prerequisites Description
Review hardware
and software requirements
Review the Infrastructure Analytics Advisor server requirements.
Make sure that you meet all the hardware and software
requirements.
Install the following yum/rpm dependency packages • tcsh
An example of how to execute the command to install the package is provided below. Change the specified values based on the environment you are using. 1. Mount the Linux OS media and obtain the yum/rpm
dependency packages: mkdir /media/OSImage
mount /dev/cdrom /media/OSImage
2. Configure the yum repository:
touch /etc/yum.repos.d/OSImage.repo
echo [dvd]>>/etc/yum.repos.d/OSImage.repo
echo name=dvd>>/etc/yum.repos.d/OSImage.repo
echo baseurl=file:///media/OSImage/>>/etc/yum.
repos.d/OSImage.repo
echo gpgcheck=0>>/etc/yum.repos.d/OSImage.repo
echo enabled=1>>/etc/yum.repos.d/OSImage.repo
3. Run the yum command to install the dependency packages:
yum install tsch
4. Unmount the Linux OS media:
umount /media/OSImage/
rm /etc/yum.repos.d/OSImage.repo
rm /etc/yum.repos.d/OSImage.repoage.repo
User permission The root permission is required.
License Obtain the Infrastructure Analytics Advisor server license from
your HDS representative.
Data Center Analytics server upgrade prerequisites (Linux)
Prerequisites Description
Review hardware and software requirements
Review the Data Center Analytics server requirements. Make sure
that your site meets all the hardware and software requirements.
© 2016, 2017 Hitachi, Ltd. All rights reserved. 30
RN-96HIAA000-07 (April 2017)
Install the following yum/rpm dependency packages • java-1.8.0-openjdk update 91 or higher • expect • parted • openssl-devel • nss-3.21.0 or higher
• gcc • unzip • perl • perl-CPAN • expat-devel • sysstat • zip • bc • perl-XML-Simple(*1)
Install the yum/rpm dependencies from the Linux OS media or Red Hat Enterprise Linux website. The procedure using the Linux OS media is as follows: 1. Mount the Linux OS media and obtain the yum/rpm
dependency packages: mkdir /media/OSImage
mount /dev/cdrom /media/OSImage
2. Configure the yum repository:
touch /etc/yum.repos.d/OSImage.repo
echo [dvd]>>/etc/yum.repos.d/OSImage.repo
echo name=dvd>>/etc/yum.repos.d/OSImage.repo
echo baseurl=file:///media/OSImage/>>/etc/yum.
repos.d/ OSImage.repo
echo gpgcheck=0>>/etc/yum.repos.d/OSImage.repo
echo enabled=1>>/etc/yum.repos.d/OSImage.repo
3. Run the yum command to install the dependency packages:
yum install java-1.8.0-openjdk expect parted o
penssl-devel nss-3.21.0 gcc unzip perl perl
- CPAN expat-devel sysstat zip
The package nss-3.21.0 may not be included in the Linux OS media of certain versions. Obtain this package from the Linux website or the Linux OS media of version 6.8 or later.
4. Unmount the Linux OS media:
umount /media/OSImage/
rm /etc/yum.repos.d/OSImage.repo
User permissions The root permission is required.
License Obtain the Data Center Analytics server license from your HDS
representative.
(*1) The rpm dependencies only exist in the following OS: - Red Hat Enterprise Linux 7.0 or later. - Oracle Linux 7.0 or later.
Analytics probe server upgrade prerequisites (Linux)
Prerequisites Description
Review hardware and software requirements
Review the Analytics probe server requirements. Make sure that
you meet all the hardware and software requirements.
© 2016, 2017 Hitachi, Ltd. All rights reserved. 31
RN-96HIAA000-07 (April 2017)
Install the following yum/rpm dependency packages: • perl • perl-CPAN • gcc • java-1.8.0-openjdk update 91 or higher • samba • expect
• openssl-devel • ftp • unzip • wget • glibc.i686 • glibc.x86_64 • libstdc++.i686 • libstdc++.x86_64 • net-tools • tcsh • libyaml • libgcc.x86_64 • nss-softokn-freebl.x86_64 • iproute.x86_64 • ncurses • openssh-clients • nss-3.21.0 or higher • expat-devel • xinetd • sysstat • zip • bc • perl-XML-Simple(*1) • perl-Digest-MD5(*1)
You can install the yum/rpm dependencies from the Linux OS media or Red Hat Enterprise Linux website. The procedure for installing the yum/rpm dependencies using the Linux OS media is as follows: 1. Mount the Linux OS media and obtain the yum/rpm
dependency packages: mkdir /media/OSImage
mount /dev/cdrom /media/OSImage
2. Configure the yum repository: touch /etc/yum.repos.d/OSImage.repo
echo [dvd]>>/etc/yum.repos.d/OSImage.repo
echo name=dvd>>/etc/yum.repos.d/OSImage.repo
echo baseurl=file:///media/OSImage/>>/etc/yum.
repos.d/ OSImage.repo
echo gpgcheck=0>>/etc/yum.repos.d/OSImage.repo
echo enabled=1>>/etc/yum.repos.d/OSImage.repo
3. Run the yum command to install the dependency packages:
yum install perl perl-CPAN gcc java-1.8.0-open
jdk samba expect openssl-devel ftp unzip wg
et glibc.i686 glibc.x86_64 libstdc++.i686 l
ibstdc++.x86_64 net-tools tcsh libyaml libg
cc.x86_64 nsssoftokn-freebl.x86_64 iproute.
x86_64 ncurses openssh-clients nss-3.21.0 e
xpat-devel xinetd sysstat zip
Note: If the environment you are using already has the libstdc
++ package installed, x86_64 (the 64-bit library) and i686 (the 32-bit compatibility library) packages might be different versions. Therefore, installation of libstdc++.i686 might fail with an error message such as the following:
Protected multilib versions: libstdc++-xx.xx.xxxx.xx.el6.i686 !=
libstdc++-yy.yy.yyyy.yy.el6.x86_64
If this happens, update x86_64 (the 64-bit library), and then retry the installation of libstdc++.i686:
#update libstdc++.x86_64
yum update libstdc++.x86_64
Note: The package nss-3.21.0 may not be included in the
Linux OS media of certain versions. Obtain this package from the Linux website or the Linux OS media of version 6.8 or later.
4. Unmount the Linux OS media:
umount /media/OSImage/
rm /etc/yum.repos.d/OSImage.repo
User permissions The root permission is required.
License Obtain the Analytics probe server license from your HDS representative.
(*1) The rpm dependencies only exist in the following OS: - Red Hat Enterprise Linux 7.0 or later. - Oracle Linux 7.0 or later.
© 2016, 2017 Hitachi, Ltd. All rights reserved. 32
RN-96HIAA000-07 (April 2017)
Copyrights and licenses
© 2016, 2017 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, 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
© 2016, 2017 Hitachi, Ltd. All rights reserved. 33
RN-96HIAA000-07 (April 2017)
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.