Skip to main content
Hitachi Vantara Knowledge

Hitachi Ops Center Analyzer 10.0.1-00 Release Notes

About this document

This document (RN-99ANA000-02, December 2019) provides late-breaking information about Hitachi Ops Center Analyzer 10.0.1-00. It includes information that was not available at the time 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 Vantara partners who license and use Hitachi Ops Center Analyzer, Analyzer detail view, and Analyzer viewpoint.

Accessing product downloads

Product software, drivers, and firmware downloads are available on Hitachi Vantara Support Connect:  https://support.hitachivantara.com/.

Log in and select Product Downloads to access the most current downloads, including important updates that may have been made after the release of the product.

About this release

This release adds new features and resolves known problems.

Starting with version 10.0.0:

·         Hitachi Infrastructure Analytics Advisor (HIAA) is called Hitachi Ops Center Analyzer

·         Hitachi Data Center Analytics (HDCA) is called Ops Center Analyzer detail view

·         Hitachi Data Center Probe is called Analyzer Probe

Hitachi Ops Center suite includes the following software:

·         Ops Center Administrator

·         Ops Center Analyzer

·         Ops Center API Configuration Manager

·         Ops Center Automator

·         Ops Center Common Services

·         Data Instance Director

See https://knowledge.hitachivantara.com/Documents/Management_Software/Ops_Center for more information.

Product package contents

Media

Products

Revision

Release type

Software

Hitachi Ops Center Analyzer

10.0.1-00

Full Package

Software

Hitachi Ops Center Analyzer viewpoint

10.0.1-00

Full Package

Software

Hitachi Ops Center Analyzer detail view

10.0.1-00

Full Package

Software

Hitachi Ops Center Analyzer probe

10.0.1-00

Full Package

Software

RAID Agent

8.7.1-00

Full Package

Software

Ops Center Analyzer Windows probe

10.0.1-00

Full Package

Software

Hitachi Ops Center API Configuration Manager

10.0.1-00

Full Package

New features and important enhancements

·         Ops Center Analyzer viewpoint now supports license management function.

·         Support for storage systems with the following firmware versions:

o    VSP 5100, 5500, 5100H, 5500H (90-02-0x)

·         The following Ops Center Analyzer operations that are time-consuming in large-scale environments have been changed to execute asynchronously :

o    Create / Update / Delete resource profile

o    Apply Assignment rule

·         Brocade FOS 8.2.1c is now supported as a target FOS in the Brocade FC Switch (CLI) probe.

System requirements

Related products

To manage additional information about Hitachi storage systems (such as information about storage capacity and hosts), use Hitachi Ops Center API Configuration Manager 8.6.5 or later.

License keys

Hitachi Ops Center Analyzer, Ops Center Analyzer detail view server, Analyzer probe server, and Windows probe all require a license key.

The latest Brocade FC Switch (CLI) probe is version 4.2.0-00, and the license is enabled by default. Existing customers who are upgrading and want to use the new probe must request the license (free of charge) from their Hitachi representative.

Obtain these license keys from your Hitachi representative.

Supported microcode/firmware

Ops Center Analyzer supports:

·         VSP model with firmware versions:

o    70-0x

·         VSP F350, F370, F700, F900 and VSP G350, G370, G700, G900 models with firmware versions:

o    88-03-0x

o    88-03-2x

·         VSP Gx00/Fx00 with firmware version:

o    83-05-2x

·         VSP G1000/G1500/F1500 with microcode version:

o    80-06-6x

·         VSP 5100/5500/5100H/5500H with firmware versions:

o    90-01-0x

o    90-02-0x

Resolved problems

From 10.0.0-01 to 10.0.1-00

Resolved problems for Analyzer server

The following table lists the problems that are resolved in this release by defect ID.

Defect ID

Problems

IAS-35662

When you configure the Common Services, single sign-on from Analyzer to Automator now works correctly.

IAS-39049

The Analyzer service now works correctly even if configuration alerts with a string value are added in Analyzer detail view.

IAS-39692

You can now use the single sign-on functionality of Ops Center Common Services in environments upgraded from versions earlier than 10.0.0-00.

IAS-39970

Multiple vulnerabilities in Hitachi Ops Center Analyzer have been addressed (CVE-2019-2894, and so on).

Resolved problems for Analyzer viewpoint server

The following table lists the problems that are resolved in this release by defect ID.

Defect ID

Problems

Viewpoint-751

When you click the viewpoint license status in the Ops Center Portal, the license screen now opens correctly.

Viewpoint-814

Ops Center Analyzer viewpoint no longer contains the following vulnerabilities:

CVE-2019-2949, CVE-2019-2989, CVE-2019-2958, CVE-2019-2975, CVE-2019-2977, CVE-2019-2999, CVE-2019-2964, CVE-2019-2962, CVE-2019-2973, CVE-2019-2978, CVE-2019-2981, CVE-2019-2983, CVE-2019-2987, CVE-2019-2988, CVE-2019-2992, CVE-2019-2894, CVE-2019-2933, and CVE-2019-2945

Resolved problems for Analyzer detail view server

The following table lists the problems that are resolved in this release by defect ID.

Defect ID

Problems

26553

The "MPB Utilization by LDEV" report no longer shows utilization exceeding100%.

26838

Pools node in the Analyzer detail view tree can now be expanded for Hitachi Enterprise storage systems using Hitachi Device Manager.

Note: Hitachi Device Manager probe is not supported.

27306

The following error message in the licenseInfo.log file on Analyzer detail view server and Analyzer probe server is no longer output:

licenseInfo-ERROR-[LicenseKeyManager] [readKeyLicenseFile] Invalid license content found, ignoring them

27633

Data holes no longer occur in some of the performance reports available at Storage Systems > Hitachi > [Storage model instance] > [Storage system instance] node when real-time data collection is enabled.

28085

When you change the unit of measure among Bytes, KB, MB, GB on a report, the value displayed in the report now is calculated based on the following:

1KB = 1024Bytes

1MB = 1024KB

1GB = 1024MB

Previously, the value was multiplied or divided by 1000.

28113

The option to change the unit of measure now is available for the "User IO Throughput" and "'User Memory Usage" reports on the following resource tree nodes:

Hosts > Windows > [Host Instance] > Users > [Instance]

Hosts > Hyper V > [Host Instance] > Users > [Instance]

28161

After changing the meghadata user password on Analyzer detail view using the changePassword.sh script, data now can be reported on the server even if the new password contains the following unsupported special characters.

For meghadata user:

·         $

·         `'

·         ""

·         )

·         &

·         (

·         ;

·         <

 

·         >

 

·         \

·         |

For megha user:

·         '

·         \ 

28359

The Analyzer detail view now displays the list of fabrics related to a Brocade switch even the switch role is other than Principal.

28371

Brocade switch data collected by Brocade FC (CLI) probe is now correctly reported in the Analyzer detail view when multiple virtual fabric IDs are configured on switch.

28393

The Health Check view now can be displayed when the Analyzer detail view server is monitoring more than 1000 targets.

Resolved problems for Ops Center Analyzer probe server

The following table lists the problems that are resolved in this release by defect ID.

Defect ID

Problems

27306

The following error message in the licenseInfo.log file on Analyzer detail view server and Analyzer probe server is no longer output:

licenseInfo-ERROR-[LicenseKeyManager] [readKeyLicenseFile] Invalid license content found, ignoring them

27720

The message "[WPREA6C4D3B7]: Unable to connect to : host-name-or-IP-address" is displayed in the following windows, and an attempt to connect to the server specified in the Host column no longer fails.

·         Primary Analyzer detail view server Information

·         Edit Primary Analyzer detail view server

·         Add Secondary Analyzer detail view server

·         Edit Secondary Analyzer detail view server

This problem occurred when a connection using the following KexAlgorithms and MACs is not permitted by the ssh daemon of the Linux server specified in the Host , FTP server, or HTTPS server columns in the previously listed windows.

·         KexAlgorithms:

             diffie-hellman-group1-sha1

·         MACs:

             hmac-sha1

Resolved problems for Ops Center Analyzer Windows probe server

The following table lists the problems that are resolved in this release by defect ID.

Defect ID

Problems

27720

The message "Unable to connect to <host-name-or-IP-address>" is no longer displayed in the Upload Settings window, and an attempt to connect to the server specified in the FTP server  or  HTTPS server columns no longer fails.

This problem occurred when the connection using the following KexAlgorithms and MACs is not permitted by the ssh daemon of the Linux server specified in the Host, FTP server, or HTTPS server columns in the previously listed windows.

·         KexAlgorithms:

diffie-hellman-group1-sha1

·         MACs:

hmac-sha1

Known problems

Known problems for Analyzer server

The following table lists the known problems in this current release of Ops Center Analyzer server by defect ID.

Defect ID

Problem

Workaround / Comments

IAS-24017

Sending a dashboard pdf file based on a schedule may differ by an hour under the following circumstances:

·         The schedule is set during daylight-saving time and daylight-saving time ends.

·         The schedule is set during standard time and daylight-saving time starts.

N/A

IAS-23535

The UI sorting capability does not work for tabular formats.

Click the column to sort the items.

IAS-23476

If you set I/O control to OFF for all volumes, the last setting is retained.

The value you set is applied for the storage system.

IAS-16535

Because old entries in the Events tab are periodically deleted, clicking the last page button might display an internal error if the entries no longer exist.

Refresh the window and try again. If the problem persists, log in to Ops Center Analyzer again.

IAA-6385

In the E2E view, when you select a VM as the base point resource, unrelated disks might be displayed in the disk list.

Identify the disks related to the VM from the disk list in the E2E view.

IAS-12239

Performance events for the metric Read Hit (Parity Group) are not logged.

N/A

IAA-7418

When you select a component from "Access Path Usage (CHA ESW)" in the Sparkline view and open the bottleneck analysis window, only one port is displayed even if there are additional ports.

N/A

IAS-12312

When you search for resources or consumers that include the "less than" character (<), the search might not return the correct results.

Do not use a < symbol in a search.

For example, if the name of the target resource is "abc<def123", then specify "abc" as the search string. Alternatively, you can search using the resource description or other resource properties.

IAS-12324

If the API string for querying the RAID Agent database contains the plus symbol (+), the query fails.

For example, the query fails if you specify "RAID_TYPE=RAID5(3D+1P)" in the API query-string.

Do not specify the plus character (+) and the characters that follow it.

Using the previous example, you would specify this instead: RAID_Type=RAID5(3D.

IAS-13735

Recent license changes may not be reflected in the Licenses window.

Wait a while, and then reopen the license screen to confirm the change.

IAS-28824

If you use the Ops Center Analyzer server immediately after setting up a connection with the Ops Center Analyzer detail view server and the initial data has not been obtained from the Ops Center Analyzer detail view server, the following problems might occur:

·         If you open the Administration tab > Predictive Analytics Settings > Report Definitions and select the definition from Copy From in the Create Report Definition window, the Ops Center Analyzer server UI does not accept all operations.

·         If you open the Administration tab > Predictive Analytics Settings > Report Definitions and select the definition and click the Target Resources tab, the tab remains loaded.

·         If you open the following windows, the message KNAQ00997-E is displayed:

-         Each window and tab in the Administration tab and Monitoring Settings windows.

-         Each window and tab in the Administration tab and Predictive Analytics Settings windows.

Confirm that the initial data was obtained from Ops Center Analyzer detail view server by completing the following steps and then try the action again.

1.     Close the Ops Center Analyzer server window.

2.     Open the Administration tab > Resource Management window and confirm that the message KNAQ01007-I is not displayed. If this message appears, wait five more minutes and then confirm that the message no longer appears.

IAS-29710

The relationship between migration source and destination volumes does not show in the E2E View when the migration source volume is one of the following storage models:

·         HUS VM

·         VSP

In this case, you can check the end-to-end relationship by searching for the volumes in the Analytics tab and selecting them as the base point before launching the E2E view.

IAS-34939

Under certain conditions, GAD pair information does not display.

N/A

IAS-36591

When the number of resources monitored by Ops Center Analyzer server is "Medium scale" or more than listed in the "Maximum number of resources" table in the "Hardware requirements based on system scale" section of the Hitachi Ops Center Analyzer Installation and Configuration Guide, the following actions take a long time:

·         Editing or deleting a User Resource Threshold Profile

·         Editing or deleting a System Resource Threshold Profile

·         Removing a monitored resource

Medium scale

·         VM: 1,000

·         ESXi: 15

·         Volume: 35000

·         Storage: 5

·         FC switch: 5

N/A

IAS-37014

Ops Center Analyzer (Windows OS only) 

When Ops Center Analyzer (Windows OS) is upgraded in the environment where the single sign-on function of Ops Center Common Services is set, the settings stored in Ops Center Analyzer will be cleared and the single sign-on function will not be available.

Register Ops Center Analyzer to Ops Center Common Services again by running setupcommonservice command on the Analyzer server.

IAS-39555

After applying the Assignment rule, a system event for resource assignment completion may not be issued for several hours.

Apply the Assignment rule again after approximately 24 hours.

IAS-39705

When applying the Assignment rule, the lock status and progress display of the resource assignment target profile may not be updated immediately.

The lock status and progress display will eventually be updated. Please wait.

Known problems for Analyzer viewpoint server

The following table lists the known problems in this current release of Ops Center Analyzer viewpoint by defect ID.

Defect ID

Problem

Workaround / Comments

Viewpoint-749

When you use Ops Center Common Service installed on a different host, searching resources fails.

Open any Analyzer E2E view from Analyzer viewpoint before searching resources.

Viewpoint-750

When you change the IP address of a VM for which you changed a port number using the changeportnumber command, the IP address is not applied to Analyzer viewpoint.

Run the setservicehostname command to apply the IP address.

Viewpoint-848

Searching resources might fail when you use Active Directory.

Clear the browser cache and reopen the browser.

Viewpoint-875

400 bad request error occurs on Ops Center Analyzer viewpoint when Ops Center Common Services deployed from Analyzer viewpoint OVF was upgraded from previous versions, or the Ops Center Common Services was overwritten by the same version 10.0.1-00.

Correct the configuration file according to the following procedure.

1.     Log in to the management server as the root user.

2.     Stop the csportal service:
systemctl stop csportal

3.     Modify the nginx.conf.template file with the following command:
sed -i -e "/include mime.types/a large_client_header_buffers 4 16k;" /opt/hitachi/CommonService/nginx/template/nginx.conf.template

4.     Start the csportal service:
systemctl start csportal

Viewpoint-876

The ETL process fails when you change a port number.

Set the property value as follows:

File:

/var/opt/hitachi/analyzer_viewpoint/etl/config/user.properties

Property:

oca.gi.license.access.port=<port-number>

(for example: oca.gi.license.access.port=50000)

Known problems for Analyzer detail view server

The following table lists the known problems in the current release of Ops Center Analyzer detail view server by defect ID.

Defect ID

Problem

Workaround / Comments

22923

When the Access Gateway and BNA switches are connected with two different ports, the reports for both ports are shown when you click either the BNA or Access Gateway switch port instance in the navigation tree.

For example, if Access Gateway and BNA switches are connected with Port 1 and Port 2, clicking the Port 1 instance in the navigation tree displays reports for both ports (instead of just port 1).

Deselect the unwanted ports in the report.

28055

When you add a report on the VSAN or zone set instance nodes (Switches > Cisco FC Switch (CLI) > VSANs > VSAN-Instance-Node or Zone-Set-Instance-Node) for the metrics associated with the Cisco Fabric Switch Port resource, the report shows the "No data available for current view" message even if the data is available for the port.

N/A

27825

When creating a query using the Query Builder option in Report Builder, duplicate metrics are displayed for some resources in the Filters list under the Enter Filter Details box.

These metrics are listed because one of them is direct and other is synthetic metric.

28381

The Hitachi NAS probe is unable to collect data because the password decryption request is not completed in default duration (60000 milliseconds).

Increase the request completion duration as follows:

1.     Log on to the Analyzer probe server through an SSH client (like putty) as a root user.

  If the root login is disabled, do the following:

    a. Log on with the megha user instead.

         Default password: megha!234

    b. Switch to the root user using the command: su - root and enter the root password.

2.     Stop the crond service using the command:

  service crond stop

3.     Stop the jetty service and confirm if it is stopped using the commands:

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

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

4.     Navigate to /usr/local/megha/conf:

  cd /usr/local/megha/conf

5.     Open the custom.properties file using an editor such as vi.

6.     Add the  validate.timestamp.time.difference property and define the value (in milliseconds) as required.

7.     Save the changes.

8.     Start the jetty service and confirm  it has started using the commands:

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

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

9.     Start the crond service using the command:

  service crond start

28421

In some cases, when you attempt to add an alert from the Global Alert window in Analyzer detail view, you cannot add switches to the alert. This problem only occurs for monitored switches such as the Brocade FC Switch (CLI) probe or Cisco FC Switch (CLI) probe.

To add an alert for either of these switches:

1.     Log on to Analyzer detail view.

2.     From the tree view, navigate to the Fabric Switch for which you want to add an alert:
Switches > Brocade FC Switch (CLI) OR Cisco FC Switch (CLI) > <Data Center> > Fabric Switches
For example:
Switches > Brocade FC Switch (CLI) > Pune > Fabric Switches

3.     Right-click the Fabric Switches node and select Add Alert.

4.     Configure the alert.

Known problems for Analyzer probe server

The following table lists the known problems in the current release of Ops Center Analyzer probe server by defect ID.

Defect ID

Problem

Workaround / Comments

IAS-39956

Hitachi Configuration Manager can be selected for collecting additional configuration metrics even for unsupported storage models.

N/A

Known problems for Analyzer Windows probe server

None.

Installation notes

About Ops Center Analyzer

·         The time difference between the host running Analyzer and the hosts running other Ops Center products cannot exceed 1 minute. We recommend configuring  an NTP server.

·         To access the Ops Center Analyzer installer for Windows:

1)      Decompress the following file:

 Analyzer/ HOC10-01-00_E02_WIN_HIAA.zip

2)      Go to the following folder:

ANALYTICS/IAA folder

3)      Run the installer:

ANALYTICS.msi

About Ops Center Common Services and VM appliance

·         Refer to  the Hitachi Ops Center release notes for critical information.

·         Single sign-on functionality to Automator using Common Services is supported in Automator 10.0.1-00 or later.

About Ops Center Analyzer viewpoint

Upgrading from a previous version

If you changed the port number before upgrading from the previous version, you must set the property value as follows after upgrading it.

Note: You must have root privilege.

File:

                /var/opt/hitachi/analyzer_viewpoint/etl/config/user.properties

Property:

                oca.gi.license.access.port=<port-number>

                (for example:  oca.gi.license.access.port=50000)

Third-party storage probes (add-on package)

In addition to the Hitachi storage probes, you can also collect data about third-party storage systems by installing the third-party add-on package. The third-party storage probes require a separate license and are delivered in a third-party add-on package, which you can download from Support Connect. For information on licensing, contact your Hitachi Vantara sales representative.

Note: If you are currently using third-party storage probes, you must install the add-on package using the -u option after you upgrade the Analyzer probe server.

For details on how to install and use the third-party add-on package, see the following:

https://knowledge.hitachivantara.com/Documents/Management_Software/Ops_Center/Analyzer/10.0.x/Add_and_manage_probes_on_the_Analyzer_probe_server/01_Installing_the_third-party_storage_probe_add-on_package

Limits on the number of open files (Linux hosts)

Before you upgrade the Ops Center Analyzer detail view server or Analyzer probe server, ensure that the system-wide and user-level limits on the number of open files is set as follows on the Linux host:

·         Minimum values for system-wide and user-level: 65535

·         Recommended values:

o    System-level: 327675

o    User-level: 262140

Refer to "Increasing the maximum number of open files" in the Hitachi Ops Center Analyzer Installation and Configuration Guide.

Ops Center Analyzer detail view or Analyzer probe server upgrade failure

In some scenarios, the Analyzer detail view or probe server upgrade returns the error "not running" and the upgrade fails.

Condition 1: Even if the Ops Center Analyzer detail view server or Analyzer probe server is running, the following command returns the message "not running":

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

Condition 2: The PID (process ID) reported by the following commands are different:

ps -ef | head -n 1; ps -ef | grep start.jar | grep /usr/local/megha
cat /usr/local/megha/misc/jetty.pid

For example:

# ps -ef | head -n 1; ps -ef | grep start.jar | grep /usr/local/megha
UID        PID  PPID  C STIME TTY          TIME CMD
megha     2271     1 15 13:37 ?        01:15:38 java -XX:+UseParNewGC -XX:MinHeapFreeRatio=20 -XX:MaxHeapFreeRatio=20 -Xmx15534m -jar start.jar -Dapp.home=/usr/local/megha
# cat /usr/local/megha/misc/jetty.pid
31534


When both these conditions occur, run the following procedures for both the Ops Center Analyzer detail view server and Analyzer probe server.

Analyzer detail view server

4)      From an SSH client, log in as root to the Ops Center Analyzer detail view server.

5)      Run the following command, and insert a hash mark (#) at the beginning of each line to comment out the entry:
crontab -e

#*/5 * * * * F=/usr/local/megha/cron.5min; test -f $F && bash $F
#13 0 * * * F=/usr/local/megha/cron.1hr; test -f $F && bash $F
#11 * * * * F=/usr/local/megha/cron.24hr; test -f $F && bash $F
#*/5 * * * * F=/usr/local/megha/bin/sysstat.sh; test -f $F && (bash $F >> /usr/local/megha/logs/sys/`date +\%Y\%m\%d`.log)

6)      Run the following commands to stop the kafka service and confirm it is stopped:

/usr/local/megha/bin/manage-kafka.sh stop
ps -f -g megha | grep kafka

If the second command displays no output, the service has stopped.

7)      Run the following commands to stop the redis service and confirm it is stopped:
/usr/local/megha/bin/manage-redis.sh stop_All
ps -f -g megha | grep redis

8)      Run the following commands to stop the httpProxy service and confirm it has stopped:
/usr/local/httpProxy/bin/megha-jetty.sh stop
ps -f -g megha | grep httpProxy

9)      Run the following command to obtain the PID (process ID) of the jetty service:
ps -f | head -n 1; ps -f -g megha | grep start.jar | grep /usr/local/megha

10)   Use the reported PID with the following command to stop the jetty process:

kill <PID>

11)   Repeat the command in step 6 to confirm that the jetty process is stopped.

12)   Run the following command to confirm that no Ops Center Analyzer detail view server process is running:

ps -f | head -n 1; ps -f -g megha | grep megha

13)   If the process exists, run the following command to stop it:
kill <PID>

14)   Repeat the command in step 9 to confirm the process has stopped.

15)   Run the following commands to start the Ops Center Analyzer detail view server service and confirm it has started:
/usr/local/megha/bin/megha-jetty.sh start
/usr/local/megha/bin/megha-jetty.sh status

16)   Run the following commands and confirm that the two reported PIDs match:
ps -f | head -n 1; ps -ef | grep start.jar | grep /usr/local/megha
cat /usr/local/megha/misc/jetty.pid
For example:

# ps -f | head -n 1; ps -ef | grep start.jar | grep /usr/local/megha
UID        PID  PPID  C STIME TTY          TIME CMD
megha     2271     1 15 13:37 ?        01:15:38 java -XX:+UseParNewGC -XX:MinHeapFreeRatio=20 -XX:MaxHeapFreeRatio=20 -Xmx15534m -jar start.jar -Dapp.home=/usr/local/megha
# cat /usr/local/megha/misc/jetty.pid
2271

17)   Run this command again and delete the hash marks (#) from the beginning of each line that you added earlier:
crontab -e

*/5 * * * * F=/usr/local/megha/cron.5min; test -f $F && bash $F
13 0 * * * F=/usr/local/megha/cron.1hr; test -f $F && bash $F
11 * * * * F=/usr/local/megha/cron.24hr; test -f $F && bash $F
*/5 * * * * F=/usr/local/megha/bin/sysstat.sh; test -f $F && (bash $F >> /usr/local/megha/logs/sys/`date +\%Y\%m\%d`.log)

Analyzer probe server

1)      From an SSH client, use the root user to log in to the Analyzer probe server.

2)      Run the following command, and insert a hash mark (#) at the beginning of each line to comment out the entry:
crontab -e

#*/5 * * * * F=/usr/local/megha/cron.5min; test -f $F && bash $F
#*/5 * * * * F=/usr/local/megha/bin/sysstat.sh; test -f $F && (bash $F >> /usr/local/megha/logs/sys/`date +\%Y\%m\%d`.log)

3)      Run the following command to obtain the PID (process ID) of the jetty service:
ps -f | head -n 1; ps -f -g megha | grep start.jar | grep /usr/local/megha

4)      Run the following command to stop the jetty process:
kill <PID>

5)      Repeat the command in step 3 to confirm the jetty process has stopped.

6)      Run the following command to confirm that there is no Analyzer probe process running:
ps -f | head -n 1; ps -f -g megha | grep megha

7)      If the process is still running, run the following command using the reported PID:
kill <PID>

8)      Repeat the command in step 6 to confirm the Analyzer probe process has stopped.

9)      Run the following commands to start the Analyzer probe server service and confirm it has started:
/usr/local/megha/bin/megha-jetty.sh start
/usr/local/megha/bin/megha-jetty.sh status

10)   Run the following commands and confirm that the two reported PIDs match:
ps -f | head -n 1; ps -ef | grep start.jar | grep /usr/local/megha
cat /usr/local/megha/misc/jetty.pid
For example:

# ps -f | head -n 1; ps -ef | grep start.jar | grep /usr/local/megha
UID        PID  PPID  C STIME TTY          TIME CMD
megha     2271     1 15 13:37 ?        01:15:38 java -XX:+UseParNewGC  XX:MinHeapFreeRatio=20 -XX:MaxHeapFreeRatio=20 -Xmx15534m -jar start.jar -Dapp.home=/usr/local/megha
# cat /usr/local/megha/misc/jetty.pid
2271

11)   Run this command again and delete the hash marks (#) from the beginning of each line that you added earlier:
crontab -e

*/5 * * * * F=/usr/local/megha/cron.5min; test -f $F && bash $F
*/5 * * * * F=/usr/local/megha/bin/sysstat.sh; test -f $F && (bash $F >> /usr/local/megha/logs/sys/`date +\%Y\%m\%d`.log)

Usage notes

Analyzer server

·         In the E2E View, the relationship between Linux hosts and Brocade FC switches might not be displayed.

·         If a Linux server is running as a virtual machine on a hypervisor and connected to storage/switches using a virtual HBA adapter, then the topology relation is not displayed in the "Other Servers" window.

·         Monitoring NDM and GAD volumes is available only when the RAID Agent access type is set as 1 or 2.

·         For Predictive Analytics, the Profile Settings default parameters in Advanced Settings were updated to cover a wide range of data behavior, including spiky data that reports a high value in a short time. This change is not applied to the built-in profile.

·         You may observe the following if the Brocade Network Advisor version is earlier than 14.2.0:

o    The Received and Transferred (Mb/second) data for the switch port might be swapped.

o    Some switch information might not be displayed in the E2E view of Ops Center Analyzer.

·         The Cisco DCNM switch shows the wrong details for CPU and Memory Utilization because incorrect values are reported by the Cisco API.

·         The I/O Control setting value is set to the volume-host paths instead of the volumes. If a volume has multiple paths, the value displayed on the Ops Center Analyzer and Ops Center Analyzer detail view GUI might be multiplied by the number of active paths.

·         When you delete a monitoring target from the Analyzer probe server, restart the Ops Center Analyzer server after 24 hours. If you fail to do so, the server does not show the most up-to-date resource status.

·         The host name must resolve to the IP address on the Ops Center Analyzer server and the host running the browser. Also, to integrate Ops Center Analyzer with Automator, the host name of the Automator server must resolve to the IP address on the Automator server and the host running the browser.

·         Mainframe volumes information are displayed to the UI of Analyzer by specifying Y for Mainframe Volume Monitoring in the instance setting of the RAID Agent.

Analyzer detail view or Analyzer probe server

·         If Command Device Authentication is set as false on command device, data is collected by Hitachi Configuration Manager (CM REST API) option in Hitachi Enterprise Storage probe only for resources which are present in meta-resource group for the VSP 5000 series storage model. Ops Center Analyzer detail view cannot verify this setting due to a CM REST API limitation.

·         The Cisco DCNM switch shows the wrong details for CPU and Memory Utilization because incorrect values are reported by the Cisco API.

·         Hitachi Content Platform (HCP) probe and all references to it was removed from Ops Center Analyzer detail view 10.0.0-00.

·         If you are using the Hitachi Device Manager probe (HDvM probe), use the following procedure to change the probe that monitors the storage system:

1)      Log in to the Analyzer probe server UI.

2)      Stop, and then delete the Hitachi Device Manager probe as follows:

a) In the Status window, go to Action and click Stop for the corresponding
Hitachi Device Manager probe.

b)  After stopping the probe, select Action and click Delete.

c)  Repeat these steps for all Hitachi Device Manager probes.

3)      Add Hitachi Device Manager probe as a part of Hitachi Enterprise Storage probe as follows:

a) In the Status window, go to Action and click Stop for the corresponding Hitachi Enterprise Storage probe.

b) After stopping the probe, go to Action and click Edit for the corresponding  Hitachi Enterprise Storage probe.

c) In the Edit window, select the Use Hitachi Device Manager checkbox.

d) Enter the required information, click Next, and follow the wizard to save the changes.

e) In the Status window, go to Action and click Start for the corresponding Hitachi Enterprise Storage probe.

f) Repeat these steps for each Hitachi Enterprise Storage probe.

Note: The HDVM probe can be added in Analyzer probe server by selecting Add Probe > Select Probe Type > Hitachi Device Manager.

·         Active Directory group users cannot log in to the Ops Center Analyzer detail view server or Analyzer probe server using the domain\username format. You must use user@domain instead.

·         After upgrading to the Analyzer probe server and Analyzer detail view server, sometimes the UI is distorted. To view the UI, refresh the browser cache. For example, press Ctrl+F5 for Windows or press command+R for Mac to refresh the browser cache.

·         If you are accessing the Analyzer detail view through supported Internet Explorer version, when you expand a node in resource tree, the UI shows a + icon instead of a - icon on the node. If you want to collapse the node, click the + icon again. Similarly, when you collapse a node, the UI shows the - icon instead of the + icon. If you want to expand the node, click the - icon again.

·         The Ops Center Analyzer detail view server and Analyzer probe server UI is not displayed correctly in Internet Explorer 10 or 11 compatibility mode. If this happens, disable compatibility mode for the server URL in Internet Explorer.

·         If the Ops Center Analyzer detail view server is installed on the Red Hat Enterprise Linux 7.x or Oracle Enterprise Linux 7.x, the export features (such as Export Reports) do not function as expected due to a font incompatibility. To resolve this, you must update the following packages:

o    xorg-x11-font-utils: v7.5-21 or later

o    fontconfig: v2.13.0-4.3 or later

·         In Ops Center Analyzer detail view server versions before v9.0.0-01, only the IP address was collected when using the ifconfig command. From v9.0.0-01 onwards, the subnet is also collected if the ip a command is supported on the Linux targets. This change history (IP address to IP address and subnet) is available in Ops Center Analyzer detail view.

·         Enterprise Virtual Servers (EVSs) of Hitachi NAS storage system are assigned to nodes and displayed in the Ops Center Analyzer detail view server navigation tree under Storage Systems > Hitachi > HNAS > HNAS storage system instance > Nodes > Node instance > EVSs. If an EVS is subsequently assigned to a different node, it is displayed under the current and previous nodes. To view the EVSs that are currently assigned to a node, refer to the EVS Summary report available on the EVSs node.

·         If you upgrade from the Ops Center Analyzer detail view version earlier than 9.2.0-00 and the following message is displayed for an existing Hitachi NAS probe, make sure that you edit the Hitachi NAS probe to provide the REST API server details:

HNSE1B77A715: Data collection has stopped. Edit probe and enter REST API server details.

·         In Ops Center Analyzer detail view server backup and restore facility, the -r parameter, which took the raw data backup in a separate zip file, was removed from v9.3.0-00. Now, the raw data is backed up with the regular data backup. This enables you to back up all the data in one zip file.

·         Hitachi NAS REST API does not return the expected output if the Hitachi NAS storage system firmware version is 13.3.4633.02. Therefore, the Hitachi NAS probe cannot collect configuration data.

·         When managing and monitoring Hitachi NAS systems, all models in a series are considered functionally equivalent. This means that Ops Center Analyzer supports the following HNAS models:

o    HNAS 3090 and 3080

o    HNAS 4080, 4060, 4040, and 4100

o    VSP G800, G600, G400, F800, F600, and F800

o    N Series N400, N600, and N800

Because storage systems in the VSP N series are equivalent to those in the VSP F series or VSP G series, Ops Center Analyzer uses the VSP F series or the VSP G series storage model names to indicate storage system models in the VSP N series.  The following table lists each model in the VSP N series and the corresponding model in the VSP F series or in the VSP G series.

Storage system model in the VSP N series

Notation in Ops Center Analyzer

VSP N400

VSP F400 or VSP G400

VSP N600

VSP F600 or VSP G600

VSP N800

VSP F800 or VSP G800

·         The following Hitachi NAS probe metrics, which were supported before Ops Center Analyzer detail view version 9.2.0-00, are no longer supported:

Resource

Metrics

HNAS System

Time zone

Daylight Saving

Usable Capacity

HNAS FS

ID

Snapshot Size

Volume Number

Deduplication

HNAS System Drives

Preferred Host Port

Preferred Controller

Preferred Target Path

Super Flush

Current Host Port

LUID

Used in Span

Type Revision

HDP Pool

Analyzer viewpoint

·         When you log in or launch viewpoint with a user account for which an email address has not been set, the error message "login.OAuthLogin(get info from generic_oauth)" occurs.

·         After upgrading viewpoint from an OVF for which a port number was changed with the changeportnumber command, you must edit firewall setting again

·         When you click Access product-level roles for Analyzer viewpoint in the Ops Center Portal, the Global Overview is displayed. To assign roles to users, click Configuration > Users, and select a Role to assign to the user.

·         When you delete the viewpoint product from the Ops Center Common Portal, KAOP20060-W message is displayed, but the deletion is successful.

·         If you run the  setupcommonservice command to register Analyzer viewpoint in Ops Center Common Services which has managed Analyzer viewpoint before, the command might fail with a 409 error. If the error occurs, delete the old Analyzer viewpoint information from the Ops Center Common Services product screen, and then try again.

Changing the port number of Analyzer viewpoint

You must have root privilege to complete this procedure.

1)      To change the port number, use the following command:

/opt/hitachi/analyzer_viewpoint/bin/changeportnumber port-number

2)      Set the property value as follows:

File:

/var/opt/hitachi/analyzer_viewpoint/etl/config/user.properties

Property:

oca.gi.license.access.port=port-number

(example: oca.gi.license.access.port=50000)

3)      After running this command, you must use the following URL to access Analyzer viewpoint:

https://host-name-or-IP-address-of-the-virtual-machine:port-number/

Note: If you are using the instance of Ops Center Common Services bundled with Analyzer viewpoint, this command also changes the port number of Ops Center Common Services. Run the setupcommonservice command for the products registered in Ops Center Common Services to set new port numbers. For details, see the documentation for each product.

Replacing the JDK for Analyzer detail view

The default JDK included in the OVA for the Ops Center Analyzer detail view and Analyzer probe servers is OpenJDK 1.8.0.161. You can switch to Open JDK 1.8.0.232 or Oracle JDK 1.8.0.231 by using the following procedures.

Analyzer detail view server

1)      Stop all services by following the procedure described in "Stopping the Ops Center Analyzer server services" in the Hitachi Ops Center Analyzer Installation and Configuration Guide.

2)      Use SSH to log in to the server as root.

3)      Stop the crond service using the command:

service crond stop

4)      Stop all Ops Center Analyzer detail view server processes using the command:

/usr/local/megha/bin/stop-all-services.sh

5)      Upload the JDK 1.8.0.232 RPM package to /tmp on the server.

6)      Install the package using the command:

rpm -ivh /tmp/<pkgname>

7)      Switch to the JDK 1.8.0.232 version using the following command:

alternatives --config java

The following is sample output:

There are 2 programs which provide 'java'.
  Selection    Command
-----------------------------------------------
 + 1          java-1.7.0-openjdk.x86_64 (/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.141-2.6.10.5.0.1.el7.x86_64/jre/bin/java)
*  2           java-1.8.0-openjdk.x86_64 (/usr/lib/jvm/java-1.8.0-openjdk-devel-1.8.0.232.b09-1.el7_6.x86_64/jre/bin/java)
Enter to keep the current selection[+], or type selection number:

Enter 2 to set the JDK version to 1.8.0.232. Run the command again and confirm the new Java version is marked with a plus (+).

8)      Run the following command, then select the required javac command.

alternatives --config javac

The following is sample output:

There are 2 programs which provide 'javac'.
  Selection    Command
-----------------------------------------------
 + 1          java-1.7.0-openjdk.x86_64 (/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.141-2.6.10.5.0.1.el7.x86_64/bin/javac)
*  2           java-1.8.0-openjdk.x86_64 (/usr/lib/jvm/java-1.8.0-openjdk-devel-1.8.0.232.b09-1.el7_6.x86_64/bin/javac)
Enter to keep the current selection[+], or type selection number:

Enter 2 to set the javac command to JDK 1.8.0.232. Run the command again and confirm the new Java version is marked with a plus (+).

9)      Check whether the Ops Center Analyzer detail view server service is running. If it isn't, start it and run status command again to confirm it is running:

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

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

10)   Start the crond service using the command:

service crond start

11)   Start all services by follow the procedure described in "Starting the Ops Center Analyzer server services" in the Hitachi Ops Center Analyzer Installation and Configuration Guide.

Analyzer probe server

1)      Use SSH to log in to the server as root

2)      Stop the crond service using the command:

service crond stop

3)      Stop all Analyzer probe services using the command:

/usr/local/megha/bin/stop-all-services.sh

4)      Upload the JDK 1.8.0.232 RPM package to /tmp on the server.

5)      Install the package using the command:

rpm -ivh /tmp/<pkgname>

6)      Switch to the JDK 1.8.0.232 version using the following command:

alternatives --config java

7)      Run the following command, then select the required javac command.

alternatives --config javac

8)      Check whether the Analyzer probe service is running. If it isn't, start it and run the status command again to confirm it is running:

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

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

9)      Start the crond service using the command:

service crond start

Error handling procedures

This section describes the procedures for handling errors that may occur on the Ops Center Analyzer server.

Check the messages

If a problem occurs, check for messages output to the UI or log files and follow the instructions provided. In addition, check the log files to determine the cause of the problem and take the 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 the necessary maintenance information and then contact customer support.

Accessing documentation

This section lists the Ops Center Analyzer user documentation. Product documentation is available on Hitachi Vantara Support Connect: https://knowledge.hitachivantara.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 Ops Center Analyzer User Guide

MK-99ANA002

Hitachi Ops Center Analyzer Installation and Configuration Guide

MK-99ANA001

Hitachi Ops Center Analyzer REST API Reference Guide

MK-99ANA003

Hitachi Ops Center Analyzer detail view Query Language User Guide

MK-99ANA006

Hitachi Ops Center Analyzer detail view REST API Reference Guide

MK-99ANA004

Copyrights and licenses

© 2019 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 Vantara 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 Vantara Corporation at https://support.hitachivantara.com/e...ontact-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 Vantara 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; and

2)      Verifying that your 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 and Lumada are trademarks or registered trademarks 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 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.

Copyright and license information for third-party and open source software used in Hitachi Vantara products can be found at https://www.hitachivantara.com/en-us...any/legal.html.