Upload
others
View
13
Download
0
Embed Size (px)
Citation preview
© 2016 Hitachi, Ltd. All rights reserved. 1
RN-96HIAA000-02 (October 2016)
Hitachi Infrastructure Analytics Advisor
v2.1.0-01 Release Notes
Contents
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........................................................................................ 4
Resolved problems ......................................................................................... 11
Known problems ............................................................................................ 13
Installation notes ........................................................................................... 18
Usage notes .................................................................................................. 19
Accessing documentation ................................................................................ 25
Copyrights and licenses .................................................................................. 25
About this document
This document (RN-96HIA000-02, October 2016) provides late-breaking information
about Hitachi Infrastructure Analytics Advisor 2.1.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.
© 2016 Hitachi, Ltd. All rights reserved. 2
RN-96HIAA000-02 (October 2016)
Hitachi Data Systems Community is a global online community for HDS customers,
partners, independent software vendors, employees, and prospects. It is the destination
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) v2.1.0-01 and
Data Center Analytics (DCA).
This release adds new features and resolves multiple known problems.
Product package contents
Medium DVD-ROM Revision Release type
Software Hitachi Infrastructure Analytics Advisor 2.1.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-16082315.zip
hdca-server-6.1-16082315.zip.hash
/PATCH/DCA/v7.0 hdca-server-7.0-16092213.zip
hdca-server-7.0-16092213.zip.hash
Analytics probe server (Upgrade /PATCH/DCAPROBE/v6.1 hdca-probe-6.1-
© 2016 Hitachi, Ltd. All rights reserved. 3
RN-96HIAA000-02 (October 2016)
patch) 16082612.zip
hdca-probe-6.1-16082612.zip.hash
/PATCH/DCAPROBE/v7.0 hdca-probe-7.0-16092215.zip
hdca-probe-7.0-16092215.zip.hash
Media Program to be installed Directory Installation program included
HIAA installation media
(Disk 2)
IAA server(Linux)
Data Center Analytics server
/ analytics_2.1.0-00.ova
Analytics probe server
Configuration Manager
/ dcaprobe_2.1.0-00.ova
Data Center Analytics server Windows-based probe
/DCAWINPROBE/ DCA_Windows_Probe.exe
New features and important enhancements
The following storage systems are now supported as monitoring targets:
- VSP G1500
- VSP F1500
For a complete list of supported monitoring targets, see Supported management
resources.
You can now obtain settings of the capacity saving function (deduplication and
compression) and capacity data In the "Pool Information" of the windows:
- Volume Detail window
- Pool Detail window
HIAA can now control IO between a host and volume using the IO Control Settings
feature. Using this feature, you can set an upper limit on the amount of IO assigned
to a volume to ensure that the performance of your critical applications are not
affected by applications from other hosts when there is contention for IO resources.
The following Operating Systems are now supported:
- Red Hat Enterprise Linux 6.7
- VMware Fault Tolerance
For a complete list of supported operating systems, see Operating system
requirements.
© 2016 Hitachi, Ltd. All rights reserved. 4
RN-96HIAA000-02 (October 2016)
System requirements
For using installer
Infrastructure Analytics Advisor server
Operating system requirements (Windows)
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 - 6.7
- tcsh
x64
Oracle Enterprise Linux 6.7-6.8 (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 Hitachi, Ltd. All rights reserved. 5
RN-96HIAA000-02 (October 2016)
OS name Yum/rpm dependencies Architecture
Red Hat Enterprise Linux 6.5 - 6.7
- perl - java-1.7.0-openjdk
- expect - openssl-devel - parted - xfsprogs - nss-3.21.0 or higher
x64
Oracle Enterprise Linux 6.7-7.0 (Unbreakable Enterprise Kernel)
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). Please note that you need to prepare a physical disk for installing the Data Center Analytics server on physical machines.
Analytics probe server
Operating system requirements
© 2016 Hitachi, Ltd. All rights reserved. 6
RN-96HIAA000-02 (October 2016)
OS name Yum/rpm dependencies CPAN dependencies Architecture
Red Hat Enterprise Linux 6.5 - 6.7
- perl - perl-CPAN - gcc - java-1.7.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-softokn-freebl.x86_64 - iproute.x86_64 - ncurses - openssh-clients - nss-3.21.0 or higher
- Module::Build - YAML - IO::Pty - Date::Gregorian - Date::Calc - Log::Log4perl - Net::OpenSSH - DateTime - Log::Dispatch::FileRotate - DateTime::Format::Strptime - Sys::RunAlone - HTTP::Request - LWP::UserAgent - LWP::Protocol::https - Time::HiRes
x64
Oracle Enterprise Linux 6.7-7.0 (Unbreakable Enterprise Kernel)
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
(*) 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
© 2016 Hitachi, Ltd. All rights reserved. 7
RN-96HIAA000-02 (October 2016)
OS name Yum/rpm dependencies Architecture
Red Hat Enterprise Linux 6.5(*)-6.7
- x64 Oracle Enterprise 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
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)
© 2016 Hitachi, Ltd. All rights reserved. 8
RN-96HIAA000-02 (October 2016)
Memory 16 GB
Disk space 200 GB (Configure as two separate disks.)
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 38
ESR 45
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.
© 2016 Hitachi, Ltd. All rights reserved. 9
RN-96HIAA000-02 (October 2016)
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
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 2.0 Windows-based probe
© 2016 Hitachi, Ltd. All rights reserved. 10
RN-96HIAA000-02 (October 2016)
Hyper-V
Windows Server 2012 Hyper-V
Hyper-V 3.0
Windows Server 2012 R2 Hyper-V
Hyper-V 3.1
Host
OS name 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
FC switches
Switch name Version Analytics probe name
Brocade Brocade Network Advisor Professional Plus
12.0 Brocade Network Advisor probe
Brocade Network Advisor Enterprise
12.0
Cisco Cisco Data Center Network Manager
- Cisco DCNM probe
(*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 NAS 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
© 2016 Hitachi, Ltd. All rights reserved. 11
RN-96HIAA000-02 (October 2016)
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.
Resolved problems
From 2.0.0-02 to 2.1.0-00
Resolved problems for Infrastructure Analytics Advisor server
The following table list the problems that are resolved in this release by defect ID.
Defect ID Problems
IAA-06842 In the License dialog box, "-" is always displayed for the current capacity of the storage system.
IAA-06851 If some nodes are added as monitoring targets, they might display as if the license was exceeded in the DCA server.
IAA-07131 If a folder name containing one of the following character strings is specified in an option of a command for specifying a folder path, the KNAQ03212-E system message is output and the command ends in an error.
・LPTM1~LPTM9
IAA-06829 The following performance metric is not supported in Sparkline View:
• Access Path Usage (MPB ESW)
• Access Path Usage (CHA ESW)
• Write Pending Rate (MPB CLPR)
• Utilization (MP)
IAA-06837 The bottleneck analysis for the following metrics when used as a base point in Sparkline View is not supported.
• Used Space % (Hyper-V Logical Disk)
• Bus Resets (VMware Virtual Disk Partition)
• Commands Aborted (VMware Virtual Disk Partition)
• Read KBps (VMware Virtual Disk Partition)
• Write KBps (VMware Virtual Disk Partition)
• Read Operations (VMware Virtual Disk Partition)
• Write Operations (VMware Virtual Disk Partition)
IAA-06462 Even when Hyper-V services are running on a particular server, if no virtual machines exist, the server is recognized as a Windows host.
IAA-06838 In the E2E view, if you display the Sparkline view when Windows or Hyper-V was set
as a base point, the storage name on a volume for the following supported storage systems is not correctly displayed:
• HUS 100 models
• HUS VM
• VSP Gx00 models
© 2016 Hitachi, Ltd. All rights reserved. 12
RN-96HIAA000-02 (October 2016)
• VSP Fx00 models
IAA-06333 The following performance metric is not supported in Sparkline View:
• Memory Usage (VMware Host)
IAA-06458 The relationships between Windows hosts (Hyper-V) and the following supported storage systems are not displayed.
• HUS 100 models
• HUS VM
• VSP Gx00 models
• VSP Fx00 models
IAA-06329 When a resource (such as a virtual machine or volume) is added, the change in the configuration of this resource is not detected.
IAA-06823 All the change histories in "Time period" may not be displayed on the "Analyze Related Changes" page.
IAA-06848 The KNAQ01000-E error can occur if you change the time period in the "Analyze Related Changes" page.
IAA-06860 The "Consumer Name of Related VM/Host" of Volume Assignment Rules for Consumers does not work.
Resolved problems for Data Center Analytics server
The following table list the problems that are resolved in this release by defect ID.
Defect ID Problems
15252 Indicator is shown for a volume which does not belong to Pool.
The dashboard indicator is shown in red or amber instead a – (dash) for volume without the data.
15432 You cannot reset the password if you upload the multiple licenses with different keys.
16106 Incorrect high values display for Disk Response Time in the EMC VNX Block node.
16450 In the Alerts Violation tab, the incorrect violation count displays for the resources if you apply any other filter with the Category filter.
16817 After upgrading the Data Center Analytics server, the Zone Member Summary is showing NA value.
16832 The dashboard indicators are not calculated for specific time duration for Synthetic Attributes.
17099 The zone information of Brocade Network Advisor is not visible in tree view.
17169 When all of the following conditions are met, the window cannot be displayed correctly, and operations can no longer be performed:
- Internet Explorer is used to connect to Data Center Analytics. - Internet Explorer recognizes the Data Center Analytics management server as
being in the local intranet zone.
IAA-06845 If a new license has been added after the existing one expired, the connections from the IAA server to the DCA server might fail.
Resolved problems for Analytics probe server
The following table list the problems that are resolved in this release by defect ID.
© 2016 Hitachi, Ltd. All rights reserved. 13
RN-96HIAA000-02 (October 2016)
Defect ID Problems
15432 You cannot reset the password if you upload the multiple licenses with
different keys.
16822 On the Status window, the Cisco SAN Switch probe displays an error message
Error in Data Collection, even after the Cisco SAN Switch probe is collecting
the data appropriately.
17169 When all of the following conditions are met, the window cannot be displayed correctly, and operations can no longer be performed:
- Internet Explorer is used to connect to Data Center Analytics. - Internet Explorer recognizes the Data Center Analytics management server as
being in the local intranet zone.
Known problems
Known problems for the Infrastructure Analytics Advisor server
The following table lists the known problems in the current release of Infrastructure
Analytics Advisor server by defect ID.
Defect ID Problem Workaround/Comments
IAA-06326 In 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
No workaround.
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.
© 2016 Hitachi, Ltd. All rights reserved. 14
RN-96HIAA000-02 (October 2016)
IAA-06747 Data on the following metrics is not collected from virtual machines (Hyper-V):
• CPU Ready
• NIC Dropped
• Disk Latency
As a result, data about virtual machines (Hyper-V) is
not included in the aggregation results in the following Dashboard reports:
• System Status Summary
• VM Summary
• VM CPU Ready
• VM NIC Dropped
• VM Disk Latency
No workaround.
IAA-06817 When a virtual machine on Hyper-V is monitored with the Data Center Analytics server Windows-based probe, the relation of the FC switch and host is not displayed.
No workaround
IAA-06469 When a Windows server monitored by a probe switches from being recognized as a Windows server
to being recognized as a Hyper-V, or when a Hyper-V monitored by a probe switches from being recognized as a Hyper-V to being recognized as a Windows server, a CPU addition/deletion event occurs.
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-06332 The following performance metrics are not supported:
• RX Rate (Fabric Brocade Switch Port)
• TX Rate (Fabric Brocade Switch Port)
• Random Read Hit (LDEV)
• Seq Read Hit (LDEV)
• Backend Transfers (LDEV)
• Cache to Drive Transfers (LDEV)
• Random Drive to Cache Transfers (LDEV)
• Seq Drive to Cache Transfers (LDEV)
• CTL 0 Total Write Hit (RAID Group)
• CTL 1 Total Write Hit (RAID 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-06535 If a virtual machine on Hypervisor is set to be
monitored by a probe for monitoring Windows servers, the relationships between hosts and storage systems are no longer displayed.
Please monitor Hypervisors by a probe.
© 2016 Hitachi, Ltd. All rights reserved. 15
RN-96HIAA000-02 (October 2016)
IAA-06330 For monitoring profiles, the following conditions occur:
When static thresholds are used, measured
values are evaluated based on whether they are greater than or equal to the warning threshold. An event occurs when the measured value of the metric reaches the warning threshold.
When you use either of the following thresholds, measured values are evaluated based on whether they are greater than or equal to the critical threshold. An event occurs when the measured value of the metric reaches the critical threshold.
- Dynamic thresholds
- Static thresholds when the same value is set for both the warning threshold and the critical threshold
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
IAA-06279 The following field in "Edit Consumer" may not be updated.
• Grade
Please delete the setting of consumer, and create again.
IAA-06858 If you assign resources from dynamic threshold type to another target monitoring profile, the existing monitoring profile name can be displayed in events that occur 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-07443 It can take some time (over 5 minutes) to display status of monitored resources properly. For a while after Infrastructure Analytics Advisor starts, the status of monitored resources is displayed as "Unknown".
Please wait for a while.
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-07401 When the volume of a storage system is deleted, the volume is not displayed in the IO Control Task Detail.
No workaround
IAA-07513 The usable WWN of the message in a change history is separated by “^”.
Read “^” as with “:”.
© 2016 Hitachi, Ltd. All rights reserved. 16
RN-96HIAA000-02 (October 2016)
IAA-07252 During installation of the product on a Linux host, if
you specify an installation directory name that is more than 94 bytes long, the installation fails.
Specify an installation directory name that is 93 bytes or less.
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 whether two or more ports are related.
No workaround
Known problems for 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 save it on the following
location
/usr/local/megha/tmp with
the following name:
diag_20160503070628.gz
16309 Alerts created for VSP/HUS-VM resources are also
applied on VSP G1000/Gx00 resources.
No workaround.
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.
No workaround.
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.
18272 After upgrading sometimes the plug-in key license
type shows as Commercial instead of Trial. This does not affect the data processing and report generation.
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.
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.
This issue is observed only on Chrome browser version 52.0.2743.116
18492 While adding an alert or indicator, the drop-down
list can display duplicate metric entries. No workaround.
18612 In the Global Search, entering a space displays all
resources for all tree nodes. No workaround.
© 2016 Hitachi, Ltd. All rights reserved. 17
RN-96HIAA000-02 (October 2016)
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:
No workaround.
18668 The Import threshold does not work on Internet
Explorer browser. Supported browsers are: Chrome and Firefox.
18697 The Global Search does not search by switch IP
address for Brocade Network Advisor and for VM
clusters.
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 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.
Known problems for 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.
18298 For the EMC VMAX probe, Unisphere version 8.2,
performance data of the Port Group is not collected. No workaround.
18659 While adding the Hitachi Adaptable Modular Storage
(AMS) probe, and 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 #.
Known problems for Data Center Analytics server Windows-based probe
The following table lists the known problems in the current release of Data Center
Analytics server Windows-based probe by defect ID.
Defect ID Problem Workaround/Comments
18491 FTP to HDCA Server does not work after upgrade of the Windows-based probe when FIPS compliance is enabled.
No workaround.
© 2016 Hitachi, Ltd. All rights reserved. 18
RN-96HIAA000-02 (October 2016)
Installation notes
During the installation of the CPAN library Net::OpenSSH by the Analytics probe
server installer, you may see the following message.
Message:”root@localhost’s password:”
In such cases, make sure that the installation process resumes approximately 10
seconds after the message is displayed.
The data migration between the Infrastructure Analytics Advisor server for Windows
and the Infrastructure Analytics Advisor server for Linux cannot be done.
You cannot install all programs of Hitachi Infrastructure Analytics Advisor in a cluster
environment.
When you add the Hitachi Enterprise Storage probe, the following message displays.
Some required opcodes are turned off by default on RAID Agent. Ensure that
these are enabled to collect the related metrics. Before proceeding further,
refer to 'Adding Hitachi Enterprise Storage probe' section in the Deployment
Guide for details.
This setting is enabled on RAID Agent in Hitachi Infrastructure Analytics Advisor.
Therefore, ignore the message and click OK.
In Linux, you must set the values of certain kernel parameters before you install the
Data Center Analytics server and the Infrastructure Analytics Advisor server.
- Kernel parameters (/etc/sysctl.conf)
You must set the maximum value in <1024> and <24 + Present value of the
system> to 4th parameter of "kernel.sem (SEMMNI)".
- Shell restrictions (/etc/security/limits.conf)
You must set the maximum value in <8514> and <4418 + Present value of
the system> to "nofile".
To enable verification of the server certificate for the Hitachi Automation Director
server on the Infrastructure Analytics Advisor server, import the certificate as
described in this section.
Before you begin
You must have the Administrator permission (for Windows) or the root permission
(for Linux) of the Infrastructure Analytics Advisor server to do this operation.
Procedure
1. Run the following command to import the certificates for the Hitachi
Automation Director server to the truststore file:
In Windows
Infrastructure-Analytics-Advisor-server-installationdestination-
folder\Base64\bin\hcmds64keytool –import – alias alias-name –file certificate-file-
© 2016 Hitachi, Ltd. All rights reserved. 19
RN-96HIAA000-02 (October 2016)
name –keystore truststore-file-name –storepass password-to-access-the-
truststore
In Linux
Infrastructure-Analytics-Advisor-server-installationdestination-
directory/Base64/uCPSB/jdk/bin/keytool –import –alias alias-name –file certificate-
file-name –keystore truststore-file-name –storepass password-to-access-the-
truststore
- For the alias-name, specify a name to identify which host server has the
certificate.
- For the certificate-file-name, specify the absolute path.
- The truststore file is stored in the following location:
In Windows
Infrastructure-Analytics-Advisor-server-installationdestination-
folder\Base64\uCPSB\jdk\jre\lib\security\jssecacerts
In Linux
Infrastructure-Analytics-Advisor-server-installationdestination-
directory/Base64/uCPSB/jdk/jre/lib/security/jssecacerts
- The password to access the default truststore is changeit.
2. To enable the verification of server certificates, change the following properties
in the config_user.properties file:
- Storage location:
In Windows
Infrastructure-Analytics-Advisor-server-installationdestination-
folder\Analytics\conf
In Linux
Infrastructure-Analytics-Advisor-server-installationdestination-
directory/Analytics/conf
- Key: cert.verify.enabled
- Value: true
3. Start Infrastructure Analytics Advisor server services.
Usage notes
Sorting and filtering capabilities in certain table columns may not work correctly.
Available values for REST API parameters are limited to the supported resources.
© 2016 Hitachi, Ltd. All rights reserved. 20
RN-96HIAA000-02 (October 2016)
When devices to be managed are added, the collection of configuration information
can take some time. During this time, Infrastructure Analytics Advisor server is
unable to display complete configuration information. Wait for a few minutes, and
then make sure the configuration information displays correctly before using
Infrastructure Analytics Advisor server.
During setup of the Hitachi Enterprise Storage probe, for the name of the RAID Agent
host, specify the host name that is returned when you run the following command on
the Analytics probe server: uname –n
You cannot specify localhost.
• 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.
If you cannot access the Data Center Analytics server, make sure that the certificate
of the Data Center Analytics server is correctly specified on the Infrastructure
Analytics Advisor server and that the specified certificate is not expired.
If you try to set up the Hitachi Enterprise Storage Probe immediately after setting up
an instance in the RAID Agent, setup might fail with the following error:
Validating RAID Agent details
Validating RAID Agent details failed. Error:Storage details are not available through
PD record
Verify the values you specified. If they are correct, wait a few minutes, and then try
again. You may have to wait for a considerable amount of time.
The window for specifying the locale of the Data Center Analytics server or the
Analytics probe server displays the option Japanese/Japan. The Japanese language
is not supported. Select the option English/United States instead.
Do not use secure connection (HTTPS) for the Hitachi Enterprise Storage probe to
collect data from the RAID Agent. When setting up the Hitachi Enterprise Storage
probe, select HTTP for Connection Type in the Provide RAID Agent Details
section.
The probe provides performance data to the Data Center Analytics server by
individual probes, and Data Center Analytics server determines the threshold of the
performance information accordingly. Since the Data Center Analytics server is
notified of the performance data differently by each probe, the thresholds are also
determined differently, and this in turn can delay the detection of performance
events/alerts.
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.
Do not change the password of the FTP user meghadata used in Data Center Analytics
server. Disable the relevant shell of meghadata if needed.
The Data Center Analytics server and the Analytics probe server create the following
users for the supported OS. Do not change these users.
© 2016 Hitachi, Ltd. All rights reserved. 21
RN-96HIAA000-02 (October 2016)
Megha
Mars
config
Some resources may have fixed thresholds even when using the dynamic threshold.
In such cases, you will not be able to monitor the resources when you perform the
following tasks:
Setting monitoring mode as other
Setting monitoring mode as the dynamic threshold again
If you re-create the monitoring profile, you can monitor the resources using the
dynamic threshold.
When the Data Center Analytics server Windows-based probe is used, the
authentication information (username and password) on the Data Center Analytics
server Windows-based probe server and the monitoring target server should be the
same.
Even when Hyper-V services are enabled on a particular server, if no virtual machines
exist on the server, that server is recognized as a Windows host.
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.
For probes that monitor Windows servers, the only supported data collection methods
are collection by using the Perfmon API and collection by using WMI queries.
When data is to be collected by using System Center Operation Manager (SCOM) and
System Center Configuration Manager (SCCM) or by using System Center Operation
Manager (SCOM) and WMI queries, only Windows machines can be monitored in Data
Center Analytics server.
If you want to monitor storage systems, enable LUN security. If LUN security is not
enabled, the Infrastructure Analytics Advisor server might not be able to correctly
obtain information about relationships between devices.
In the environment using the Open Virtualization Format Archive (OVA) package,
install VMware tools when you do time synchronization without using NTP.
In the environment using the Open Virtualization Format Archive (OVA) package, a
network card (NIC) is installed, and the udev function is disabled: if you add a
network card, a network device name for each NIC changes dynamically by every OS
startup. Execute the following procedure to make the network device name static.
1. Enable the udev function.
cp /lib/udev/rules.d/75-persistent-net-generator.rules.back
/lib/udev/rules.d/75-persistent-net-generator.rules
2. Reboot a virtual host.
3. Confirm whether network setting is right.
© 2016 Hitachi, Ltd. All rights reserved. 22
RN-96HIAA000-02 (October 2016)
The Data Center Analytics server has to be connected to one Infrastructure Analytics
Advisor server only.
During an operation to change the monitoring mode of a profile to "Dynamic" or "OFF",
if a performance-related event of a resource monitored by that profile occurs, the
threshold value for that event sometimes cannot be obtained. In such cases,
"Threshold: Could not get the value" is displayed in the Message column of the event,
and "-" is displayed in the Threshold column.
When you register information about the storage system for which IO Control settings
are to be configured to Web Service Connections in Automation Director, please
specify the user of a storage system which is different from the user used by the
other applications(such as RAID Agent). If you use the user name which is used by
the other applications, the tasks of the IO Control Setting will fail.
If you want to change the maximum number of the IO Control Task History, please
change the value of the iocontrol.history.maxcount property in
config_user.properties. The upper limit of the property is 10000; the lower limit is
30; and the default value is 5000.
Please specify "000" for "nnn" of the environment variable "ANALYTICS_GROUPSnnn"
that you specify in a batch file for running an event action.
If an upgrade from version 2.1.0 or earlier is performed, the dashboard settings will
return to their default values.
In VSP Gx00 models and VSP Fx00 models with DKCMAIN firmware 83-03-0x or
earlier, if you specify or refer SPM information via IO Control Settings in
Infrastructure Analytics Advisor, an error might occur.
After upgrading Hitachi Infrastructure Analytics Advisor, the table contents in the
Infrastructure Analytics Advisor window sometimes do not display properly or are
missing. In this case, select File > Clear Settings, and then click OK to clear the
settings saved in the browser.
Note that this operation will clear the following information:
- Table configuration information (column settings, column widths, column
sorting status, filtering status)
- History of search keywords
If you execute the task for IO Control Settings by using Hitachi Automation Director
and the following error occurs, the setting up SSL communication between the
Configuration Manager REST Server and the storage system may not be appropriate.
Please refer to Configuration Manager REST API Reference Guide and confirm the
setting up SSL communication.
- Error Message : Storage session could not be got. Check the error detail at the
[Results] tab.
- Error Detail : {"StepName":"Get Session","Exception":"{\n \"errorSource\" :
\"/ConfigurationManager/v1/objects/storages/storageDeviceId/sessions\",\n
\"message\" : \"An internal error is occurred in REST API server.\",\n
\"cause\" : \"The server may be busy.\",\n \"solution\" : \"Wait a while and try
again. If the problem persists, detailed investigation is required to determine
the cause and resolve the problem. Contact customer support, who might ask
© 2016 Hitachi, Ltd. All rights reserved. 23
RN-96HIAA000-02 (October 2016)
you to collect troubleshooting information.\",\n \"messageId\" : \"KART00003-
E\"\n}"}
You can confirm the above information in the following screen.
Tasks tab > Task > Show Details > Results Tab > Default Properties
If you execute the task for IO Control Settings by using Hitachi Automation Director
and the following error occurs, the number of WWNs associated with the target
volume might have been set to more than 32.
- Error Message: Execution of a part of targets was failed. Check the reasons by messages of [Failed Resources] at the [Results] tab.
- Error Detail : {"StepName":"Generate Results"}
- Failed Resources: {"ldevId":ldevId,"hostWwn":wwn,"message":"An error occurred in the storage system. (message = The number of WWNs that can be registered in the LDEV exceeded the maximum number.)"}
You can confirm the above information on the following window in Automation
Director:
Tasks tab > Task > Show Details > Results Tab
If you execute the task for IO Control Settings, please use a different user when you
register the storage system to REST Server and when HIAA access to the storage
system (*).
* If you execute the task for IO Control Settings by using Hitachi Automation Director,
the user that access to storage system is “User ID” that you have set in ”Web
Service Connections”.
If you use the same user, the following error might occur.
- Error Message: Storage session could not be got. Check the error detail at the
[Results] tab.
- Error Detail : {"StepName":"Get Session","Exception":"{\n \"errorSource\" :
\"/ConfigurationManager/v1/objects/storages/storageDeviceId/sessions\",\n
\"message\" : \"The operation could not be performed, because processing for
the specified user is currently being executed on the storage system.\",\n
\"solution\" : \"Wait a few minutes, and then try again.\",\n \"messageId\" :
\"KART30090-E\",\n \"errorCode\" : {\n \"errCode1\" : \"1\",\n
\"errCode2\" : \"5132\"\n }\n}"}
You can confirm the above information on the following window in Automation
Director.
Tasks tab > Task > Show Details > Results Tab > Default Properties
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 GUI or log files, and then
© 2016 Hitachi, Ltd. All rights reserved. 24
RN-96HIAA000-02 (October 2016)
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. On the Manage window, click the Download Diagnostic Data link.
5. On 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.
3. Do steps 3 to 5 from the previous section.
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
© 2016 Hitachi, Ltd. All rights reserved. 25
RN-96HIAA000-02 (October 2016)
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
Copyrights and licenses
© 2016 Hitachi, Ltd. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or by any
means, electronic or mechanical, including photocopying and recording, or stored in a
database or retrieval system for any purpose without the express written permission of
Hitachi, Ltd.
Hitachi, Ltd., reserves the right to make changes to this document at any time without
notice and assumes no responsibility for its use. This document contains the most
current information available at the time of publication. When new or revised
information becomes available, this entire document will be updated and distributed to
all registered users.
Some of the features described in this document might not be currently available. Refer
to the most recent product announcement for information about feature and product
availability, or contact Hitachi, Ltd., at https://support.hds.com/en_us/contact-us.html.
Notice: Hitachi, Ltd., products and services can be ordered only under the terms and
conditions of the applicable Hitachi Data Systems Corporation agreements. The use of
Hitachi, Ltd., products is governed by the terms of your agreements with Hitachi Data
Systems Corporation.
© 2016 Hitachi, Ltd. All rights reserved. 26
RN-96HIAA000-02 (October 2016)
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 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.
Hitachi is a registered trademark of Hitachi, Ltd., in the United States and other
countries. Hitachi Data Systems is a registered trademark and service mark of Hitachi,
Ltd., in the United States and other countries.
Archivas, BlueArc, Essential NAS Platform, HiCommand, Hi-Track, ShadowImage,
Tagmaserve, Tagmasoft, Tagmasolve, Tagmastore, TrueCopy, Universal Star Network,
and Universal Storage Platform are registered trademarks of Hitachi Data Systems
Corporation.
AIX, AS/400, DB2, Domino, DS6000, DS8000, Enterprise Storage Server, ESCON,
FICON, FlashCopy, IBM, Lotus, MVS, OS/390, RS/6000, S/390, System z9, System z10,
Tivoli, VM/ESA, z/OS, z9, z10, zSeries, z/VM, and z/VSE are registered trademarks and
DS6000, MVS, and z10 are trademarks of International Business Machines Corporation.
All other trademarks, service marks, and company names in this document or website
are properties of their respective owners.
Microsoft product screen shots are reprinted with permission from Microsoft Corporation.
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.
IBM, AIX are trademarks of International Business Machines Corporation, registered in
many jurisdictions worldwide.
Internet Explorer is either a registered trademark or trademark of Microsoft Corporation
in the United States and/or other countries.
Linux(R) is the registered trademark of Linus Torvalds in the U.S. and other countries.
Microsoft and Hyper-V are either registered trademarks or trademarks of Microsoft
Corporation in the United States and/or other countries.
Oracle and Java are registered trademarks of Oracle and/or its affiliates.
This product includes software developed by the Apache Software Foundation
(http://www.apache.org/).
This product includes software developed by IAIK of Graz University of Technology.
RSA and BSAFE are either registered trademarks or trademarks of EMC Corporation in
the United States and/or other countries.
SUSE is a registered trademark or a trademark of SUSE LLC in the United States and
other countries.
Windows is either a registered trademark or a trademark of Microsoft Corporation in the
United States and/or other countries.
© 2016 Hitachi, Ltd. All rights reserved. 27
RN-96HIAA000-02 (October 2016)
Windows Server is either a registered trademark or a trademark of Microsoft
Corporation in the United States and/or other countries.
JP1/Operations Analytics includes RSA BSAFE(R) Cryptographic software of EMC
Corporation.
This product includes software developed by Ben Laurie for use in the Apache-SSL HTTP
server project.
Portions of this software were developed at the National Center for Supercomputing
Applications (NCSA) at the University of Illinois at Urbana-Champaign.
This product includes software developed by the University of California, Berkeley and
its contributors.
This software contains code derived from the RSA Data Security Inc. MD5 Message-
Digest Algorithm, including various modifications by Spyglass Inc., Carnegie Mellon
University, and Bell Communications Research, Inc (Bellcore).
Regular expression support is provided by the PCRE library package, which is open
source software, written by Philip Hazel, and copyright by the University of Cambridge,
England. The original software is available from
ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/
This product includes software developed by Ralf S. Engelschall <[email protected]>
for use in the mod_ssl project (http://www.modssl.org/).
This product includes software developed by Daisuke Okajima and Kohsuke Kawaguchi
(http://relaxngcc.sf.net/).
This product includes software developed by the Java Apache Project for use in the
Apache JServ servlet engine project (http://java.apache.org/).
This product includes software developed by Andy Clark.
Java is a registered trademark of Oracle and/or its affiliates.