Skip to main content
Hitachi Vantara Knowledge

Tuning Manager v8.8.3-00 Release Notes

About this document

This document (RN-00HS262-105, February 2022) provides late-breaking information about the Hitachi Tuning Manager 8.8.3-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 the Hitachi Tuning Manager.

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 is a major release that adds new features and resolves multiple known problems.

Product package contents

Medium

Components

Revision

Release type

Prerequisite version of service pack

Software

Hitachi Tuning Manager

8.8.3-00

Full package

-

Hitachi Tuning Manager - Agent for Server System

8.8.3-00

Full package

-

Hitachi Tuning Manager - Agent for RAID

8.8.3-00

Full package

-

Hitachi Tuning Manager - Agent for Network Attached Storage

8.8.3-00

Full package

-

Hitachi Tuning Manager - Agent for SAN Switch See Note

8.8.3-00

Full package

-

Documents

Hitachi Command Suite Tuning Manager Installation Guide

MK-96HC141-34

Hitachi Command Suite Tuning Manager Server Administration Guide

MK-92HC021-44

Hitachi Command Suite Tuning Manager Agent Administration Guide

MK-92HC013-43

Hitachi Command Suite Tuning Manager User Guide

MK-92HC022-44

Hitachi Command Suite Tuning Manager Hardware Reports Reference

MK-95HC111-32

Hitachi Command Suite Tuning Manager Operating System Reports Reference

MK-95HC112-23

Hitachi Command Suite Tuning Manager Messages

MK-95HC114-34

Hitachi Command Suite Tuning Manager CLI Reference Guide

MK-96HC119-34

Hitachi Command Suite Tuning Manager Getting Started Guide

MK-96HC120-25

Hitachi Command Suite Tuning Manager API Reference Guide

MK-92HC218-09

Note:

Support for Agent for SAN Switch will continue to be provided only for the purpose of correcting defects in existing systems. Support for the introduction of new Agent for SAN Switch systems has ended.

New features and important enhancements

For 8.8.3-00

New features and enhancements

Applied products

Applied OS

The following virtual environment is now supported as an operating environment:

·       Red Hat Enterprise Linux 8.1

·       Red Hat Enterprise Linux 8.2

·       Red Hat Enterprise Linux 8.4

·       Oracle Linux 8.1

·       Oracle Linux 8.2

·       Oracle Linux 8.4

·       Windows server 2022

Tuning Manager server

Agent for RAID

Agent for Server System

Agent for NAS

All*

The following storage systems are now supported as monitoring targets:

·       Hitachi Virtual Storage Platform (VSP) 5000 series (90-08-2X)

Tuning Manager server

Agent for RAID

Agent for Server System

All*

Viewing of the Tuning Manager server window is now supported in Edge environment.

Tuning Manager server

All*

The following menus are removed from the menu of the management server:

·       Online Help - HTnM

Tuning Manager server

All*

Tuning Manager now supports monitoring of storage systems for which the Fibre Channel port operating mode is set to NVMe mode.

Tuning Manager server

Agent for RAID

All*

The following fields can now be used to obtain information to determine whether a port or LDEV is related to NVMe mode:

·       Logical Device Configuration (PD_LDC) record

-       NVM Namespace ID (NVM_NAMESPACE_ID) field

-       NVM Subsystem ID (NVM_SUBSYSTEM_ID) field

·       Port Configuration (PD_PTC) record

-       Port Mode (PORT_MODE) field

Agent for RAID

All*

* Applies to all supported operating systems

System requirements

The system requirements for Tuning Manager can be found in Hitachi Command Suite System Requirements (MK-92HC209).

Resolved problems

8.8.3-00

The following vulnerabilities related to the JDK. CVE-2021-2341, CVE-2021-2369, CVE-2021-2388, CVE-2021-35567, CVE-2021-35550, CVE-2021-35586, CVE-2021-35564, CVE-2021-35556, CVE-2021-35559, CVE-2021-35561, CVE-2021-35565, CVE-2021-35578, CVE-2021-35603, CVE-2021-35588

Applied products: Tuning Manager server

The following vulnerabilities related to the JDK. CVE-2021-35567, CVE-2021-35550, CVE-2021-35586, CVE-2021-35564, CVE-2021-35556, CVE-2021-35559, CVE-2021-35561, CVE-2021-35565, CVE-2021-35578, CVE-2021-35603

Applied products: Agent for RAID, Agent for NAS, Agent for SAN Switch

Fixed a problem of the file permission vulnerability.

Applied products: Tuning Manager server, Agent for RAID, Agent for Server System, Agent for NAS, Agent for SAN Switch

When the Chrome web browser is used, in the window for checking the detailed polling result of Main Console, fixed columns (columns whose display position does not change due to scrollbar operations) and non-fixed columns might have different row heights.

Applied products: Tuning Manager server

This problem sometimes occurs when the Chrome web browser is used and the window for checking the detailed polling result of Main Console is opened.

When the jpctdraidperf command is executed, some of the MP-related and port-related performance information cannot be output.

Applied products: Agent for RAID

This problem occurs when all of the following conditions are met:

1)    The version of the Agent for RAID is 8.7.0-00 or later.

2)    The storage system to be monitored is the VSP 5500 or VSP 5500H.

3)    The monitored storage system consists of four or six controller chassis.

4)    During setup of the monitored storage system instance, a command device was specified as the connection method for collecting performance data.

5)    The user runs the command jpctdraidperf.

When the Tuning Manager API is used, the transmission in compressed format does not work and the amount of communication between clients and the machine on which Tuning Manager is installed increases incorrectly.

Applied products: Agent for RAID, Agent for NAS

This problem occurs when all of the following conditions are met:

1)    The Tuning Manager API is used to obtain performance data.

2)    The Accept-Encoding header is used when the Tuning Manager API is used.

3)    The value specified for the Accept-Encoding header contains the string gzip or an asterisk (*).

4)    The quality value (;q=) is specified after the string in (3).

Known problems

For all applied operating systems

Cannot obtain the corresponding performance data

Applied products: Tuning Manager server

When obtaining performance data by using Tuning Manager API, you cannot obtain the corresponding performance data in the case of sending the request message that includes "+" in the query-string.

For example, you cannot obtain the corresponding performance data in the case of specifying "RAID_TYPE=RAID5(3D+1P)" in the query-string.

For Windows and Linux

Hybrid Store as performance database

Applied products: Agent for RAID, Agent for NAS

When you use Hybrid Store as a performance database and change time zone, the following problems will happen:

It takes a long time (several tens of minutes to several hours. It depends on the number of resources on monitoring systems) to start Tuning Manager Agent REST API component.

Latest values of performance data that was aggregated are incorrect.

Hybrid Store when an agent of cluster configuration exists

Applied products: Agent for RAID, Agent for NAS

When you upgrade Agent for RAID or Agent for NAS in an environment where an agent of a cluster configuration exists, if you select Hybrid Store in upgrading process while the shared disk (that is, the environment directory of the logical host) cannot be connected, the process will be failed.

Always execute the following procedure when an agent of a cluster configuration exists in the target installation environment:

(a) In Windows

(a-1) If all data is inherited:

1)    Stop the Tuning Manager services from the clustering software.

2)    Make sure that the execution host can connect to the shared disk.

3)    Start the upgrade in the execution host.

4)    Select [Hybrid Store (recommended)] when you select the Performance database.

5)    Select [Transfer all performance data] and finish installation.

6)    Make sure the standby host can connect to the shared disk.

7)    Start the upgrade in the standby host.

8)    Select [Hybrid Store (recommended)] when you select the Performance database.

9)    Select [Do not transfer any performance data] and finish installation.

10) Stop the Tuning Manager Agent REST API Component services.
Execute the command "htmsrv stop -webservice".
(* If there are multiple standby hosts, execute steps 6-10 for all standby hosts)

11) Start the Tuning Manager services from the clustering software, and start operation.

(a-2) If data is not inherited:

1)    Stop the Tuning Manager services from the clustering software.

2)    Make sure that the host that executes the upgrade can connect to the shared disk.

3)    Start the upgrade.

4)    Select [Hybrid Store (recommended)] when you select the Performance database.

5)    Select [Do not transfer any performance data] and finish installation.

6)    Stop the Tuning Manager Agent REST API Component services.
Execute the command "htmsrv stop -webservice".
(Execute steps 2-6 for all hosts.)

7)    Start the Tuning Manager services from the clustering software, and start operation.

(a-3) If data is inherited after installation:

1)    Stop the Tuning Manager services from the clustering software.

2)    Make sure that the host that executes the upgrade can connect to the shared disk.

3)    Start the upgrade.

4)    Select [Hybrid Store (recommended)] when you select the Performance database.

5)    Select [Transfer performance data after installation] and finish installation.
(Execute steps 2-5 for all hosts.)

6)    Change the Performance databases of all hosts to Hybrid Store. For details, see "Migrating the Store database to the Hybrid Store" in the manual Hitachi Command Suite Tuning Manager Agent Administration Guide.

7)    Start the Tuning Manager services from the clustering software, and start operation.

(b) In Linux

(b-1) If all data is inherited:

1)    Stop the service from the clustering software.

2)    Remove the script registered in the clustering software.

3)    Make sure that the execution host can connect to the shared disk.

4)    Start the upgrade in the execution host.

5)    Select [Hybrid Store (recommended)] when you select the Performance database.

6)    Select [Transfer all performance data] and finish installation.

7)    Make sure the standby host can connect to the shared disk.

8)    Start the upgrade in the standby host.

9)    Select [Hybrid Store (recommended)] when you select the Performance database.

10) Select [Do not transfer any performance data] and finish installation.

11) Stop the Tuning Manager Agent REST API Component services.
Execute the command "htmsrv stop -webservice".
(* If there are multiple standby hosts, execute steps 7-11 for all standby hosts)

12) Stop the service from the clustering software.

13) In the clustering software, register the script that registers the Tuning Manager agents service.

14) Start the service from the clustering software, and start operation.

(b-2) If data is not inherited:

1)    Stop the service from the clustering software.

2)    Remove the script registered in the clustering software.

3)    Make sure that the host that executes the upgrade can connect to the shared disk.

4)    Start the upgrade.

5)    Select [Hybrid Store (recommended)] when you select the Performance database.

6)    Select [Do not transfer any performance data] and finish installation.

7)    Stop the Tuning Manager Agent REST API Component services.
Execute the command "htmsrv stop -webservice".
(Execute steps 3-7 for all hosts.)

8)    Stop the service from the clustering software.

9)    In the clustering software, register the script that registers the Tuning Manager agents service.

10) Start the service from the clustering software, and start operation.

(b-3) If data is inherited after installation:

1)    Stop the service from the clustering software.

2)    Remove the script registered in the clustering software.

3)    Make sure that the host that executes the upgrade can connect to the shared disk.

4)    Start the upgrade.

5)    Select [Hybrid Store (recommended)] when you select the Performance database.

6)    Select [Transfer performance data after installation] and finish installation.
(Execute steps 3-6 for all hosts.)

7)    Change the Performance databases of all hosts to Hybrid Store. For details, see "Migrating the Store database to the Hybrid Store" in the manual Hitachi Command Suite Tuning Manager Agent Administration Guide.

8)    Stop the service from the clustering software.

9)    In the clustering software, register the script that registers the Tuning Manager agents service.

10) Start the service from the clustering software, and start operation.

Operation fails when shared disk not connected

Applied products: Agent for RAID, Agent for NAS

When you execute the following commands in an environment where an agent of a cluster configuration exists, if the commands are executed while the shared disk (that is, the environment directory of the logical host) cannot be connected, the conversion process of the performance database of the agent on a logical host fails with the KATR00124-E message. Make sure that the shared disk can be connected when you perform the following operations:

Executing the htmhsmigrate command

Executing the htmhsconvert command

Also, when changing the Performance database by using the htmhsmigrate command, do not start the Agent for RAID or Agent for NAS service until migration of all the physical hosts to Hybrid Store has finished.

For Linux

Hybrid Store service fails to start

Applied products: Agent for RAID, Agent for NAS

When using Hybrid Store on Linux, the service fails to start and the message indicating incorrect property value is not output to the log.

The following property files are affected:

<installation-directory>/htnm/agent/config/dbdataglobalconfig.ini

<installation-directory>/agtx#/store/<instance-name>/dbconfig.ini

#: x is replaced with the Agent product ID.

If the service fails to start, review the value set for the property, and then start the service again.

The Agent Collector service ends abnormally or the values of the performance data become incorrect

Applied products: Agent for Server System

On a Linux machine on which Agent for Server System is installed, if the number of CPUs is set to change dynamically while the Agent for Platform service is running, the Agent Collector service process (jpcagtu) ends abnormally or the values of the performance data in the PI record and the PI_CPUP record become incorrect.

Before setting the number of CPUs to change dynamically, first stop the Agent for Platform service.

Resolved known problems

For 8.8.3-00

Tuning Manager do not support NVMe

Applied products: Tuning Manager server, Tuning Manager agents

Tuning Manager cannot monitor storage systems for which the Fibre Channel port operating mode is set to NVMe mode.

Installation precautions

Tuning Manager server and Tuning Manager agents

For all operating systems

Incompatible products

Do not install Tuning Manager server and Tuning Manager agents in the host on which the following products are installed:

Analytics probe of Hitachi Infrastructure Analytics Advisor

Analytics probe of Hitachi Ops Center Analyzer

Device Manager compatibility

If the version of the Tuning Manager server you use is 8.5.3 or later, the version of Device Manager in the system must also be 8.5.3 or later.

Port number range

Port numbers in the range from 24235 to 24242 were added for use in Tuning Manager 8.4.1 to enhance security. Therefore, confirmation is required that the port numbers from 24235 to 24242 are not used by other programs. If these port numbers are used by other programs, change any of the port numbers used by other programs, or temporarily suspend the other programs and change the port number used by the product from the default value after installation. For details on changing port numbers, see "Managing ports used by Common Component" in the Hitachi Command Suite Tuning Manager Server Administration Guide

When you install the Tuning Manager server of a version 8.8.3 or later

If you install any of the products in product group B on a server where any of the products in product group A below is installed, the installation fails. Also, if you install any of the products in product group A on a server where any of the products in product group B below is installed, the installation might affect the operation of product group B.

To avoid this problem, upgrade all installed products on the same server to Analyzer server 10.7.0 or later, Automator 10.8.0 or later, and Hitachi Command Suite 8.8.3 or later.

Product group A:

- Hitachi Ops Center Analyzer server 10.7.0 or later

- Hitachi Ops Center Automator 10.8.0 or later

- Hitachi Device Manager, Hitachi Tiered Storage Manager, Hitachi Tuning Manager, Hitachi Replication Manager, Hitachi Compute Systems Manager, Hitachi Global Link Manager 8.8.3 or later

Product group B:

- Hitachi Ops Center Analyzer server earlier than 10.7.0

- Hitachi Ops Center Automator earlier than 10.8.0

- Hitachi Device Manager, Hitachi Tiered Storage Manager, Hitachi Tuning Manager, Hitachi Replication Manager, Hitachi Compute Systems Manager, Hitachi Global Link Manager earlier than 8.8.3, or Hitachi Automation Director 10.6.1 or earlier

For Linux

Mutually exclusive products

You cannot install Tuning Manager on a host on which Ops Center Viewpoint RAID Agent is installed.

Tuning Manager server

For all operating systems

Time to start after import

After installing the Tuning Manager server, if the database of the Tuning Manager server which had been exported on version 6.0.0 to 6.4.0 was imported, the Tuning Manager server might take approximately 1 hour to start at the first time after the import.

Notes on using Tuning Manager 8.8.3 or later

If you are using Tuning Manager 8.8.3 or later, the hcmds64chgjdk command cannot be used.

For Windows

Shortcut folder

After an installation or removal, shortcut folder named "programs" might be incorrectly created under the Windows Start menu. This symptom is temporary, and this shortcut folder will no longer appear after you log off and log on to Windows.

Installation file registered to be updated

If the following message is recorded in the Common Component installation log file, the installation file is registered to be updated as a pending file for next start up.

Restart the server machine, and then start the installer again.

Log file location: <system drive>

File name: hcmdsist.log

----------------------------------------------------

[hh:mm:ss] Installation result:

[hh:mm:ss] 02

----------------------------------------------------

For Linux

Notes on using Tuning Manager 8.8.3 or later

If you want to use Japanese locale in a Linux environment, install the Japanese font package.

Tuning Manager agents

For all operating systems

Compatible agent versions

If the version of Tuning Manager you use is 8.6.4 or later, the versions of the Tuning Manager server and Tuning Manager agents running on the same host must also be 8.6.4 or later.

However, for Tuning Manager agents running on remote hosts on which a Tuning Manager server of version 8.6.4 or later is running, you do not need to upgrade the version to 8.6.4.

Introduction of Agent for SAN Switch

Support for the introduction of new Agent for SAN Switch systems has ended. Support for Agent for SAN Switch will continue to be provided only for the purpose of correcting defects in existing systems. To install Agent for SAN Switch for the purpose of correcting a defect, use the following installer provided on the installation DVD. Do not perform installation from the Product Select Page. Installation from the Product Select Page will be discontinued.

For Windows:

    \AGENTS\HTNM\Windows\Agent_for_Switch\setup.exe

For Linux:

    /AGENTS/HTNM/Linux/Agent_for_Switch/install.sh

For Windows

Start menu

If you install the Tuning Manager agent version 7.4.1 or earlier in an environment that already contains a Tuning Manager agent product of version 7.5.0 or later, the following items are displayed in the Start menu:(*)

Administrator Console

Administrator Console - HTnM

(*) Coexistence of these menu items does not affect program operations. Use either of them to start Administrator Console.

Installation path

Applied products: Agent for RAID, Agent for NAS

When installing Agent for RAID or Agent for NAS, the path which can be specified for the destination of Hybrid Store output is as follows. However, in Linux, the path which include spaces cannot be specified for the destination of Hybrid Store output.

1) Specify an existing path. The path must be from 1 to 80 bytes long.

2) Specify an absolute path. Do not use the following:

Symbolic link

Network folder

Network drive

Use single-byte alphanumeric characters, symbols, and spaces.

Do not use the following characters:

; , * ? ' " < > |

Upgrade precautions

Tuning Manager server and Tuning Manager agents

For Linux operating system

After the version upgrade, ordinary users can no longer perform operations. Therefore, after the version upgrade, perform operations as the root user.

Tuning Manager server

For all operating systems

Time to upgrade

If you upgraded the Tuning Manager server from version 6.0.0 to 6.4.0 to this version, the Tuning Manager server might take approximately 1 hour to start at the first time after upgrade.

Upgrade other products

If following products are installed, upgrade them to 8.0.0 or later.

Device Manager

Tiered Storage Manager

Replication Manager

Tuning Manager

Compute Systems Manager

Global Link Manager

About the lapse of time for upgrade installation.

When upgrading the version from 7.6.1 or earlier to 8.0.0 or later, the upgrade installation may take a long time to move the place of database from 32 bit to 64 bit. The estimate time for the upgrade installation depends on the size of the database. The following shows criterion of a configuration with which might take more than three hours for the installation of Hitachi Command Suite products.

An environment of installation

CPU: vCPU * 2 (4GHz)

HDD: SATA drive 7200rpm 1TiB

The estimate time for installation (upgrade from V7.6.1 to V8.0.0)

The estimate time for products first installation

1)    The estimate time for the installation is the total time of the Backup-time (*1) of every Hitachi Command Suite products that had already been installed which shown in Table 1 or Table 2, and the Import-time of the installing product, and etc. in the tables.
*1: The first upgrade installation takes longer time because backup of every installed Hitachi Command Suite products have to take place.

2)    The estimate time for the products installation after (1)
The estimate time for the installation is the total time of the Import-time of the products shown in Table1 and Table2, and etc. in the tables.

Table1 estimating time for installation (Windows)

units: minutes

Product name

Composition

Backup

Import

etc.

Device Manager

Tiered Storage Manager

Replication Manager

Volumes: 128,000

Paths: 512,000

Hosts: 1,000

11

35

49

Tuning Manager

14

9

48

Global Link Manager

Paths/hosts: 1,000

Hosts: 60

Pathstatuslog: 4GiB (total capacity)

2

7

43

Compute Systems Manager

Chassis: 200

Blades: 1,000

Hosts: 1,000

2

2

21

Table2 estimating time for installation (Linux)

Units: minutes

Product name

Composition

Backup

Import

etc.

Device Manager

Tiered Storage Manager

Replication Manager

Volumes: 128,000

Paths: 512,000

Hosts: 1,000

4

36

35

Tuning Manager

3

7

17

Device Manager compatibility

If you upgrade the version of the Tuning Manager server to 8.5.3 or later, you must also upgrade the version of Device Manager to 8.5.3 or later.

Upgrading Tuning Manager from a version prior to 8.8.3-00

Please be noted that this section describes important points if you have made any of the following changes in versions prior to 8.8.3-00.

- Restricted management clients that can access the management server.

- The port 22035/tcp used by the common components has been changed from the default.

- The port 24234/tcp, 24235/tcp, 24239/tcp used by the common components has been changed from the default.

- The JDK used by the products has been changed to Oracle JDK.

(1) If you have restricted management clients that can access the management server

The configuration that restricts the management clients to be connected to the management server in which written on the user_httpsd.conf file may not be inherited after upgrade installation.

Therefore, check the configuration of the user_httpsd.conf file and the file described below, and if the configuration is not written on the user_httpsd.conf file, make sure to add the specific configuration to the user_httpsd.conf file.

Windows:

    <HCS-installation-folder>\Base64\uCPSB11\httpsd\conf\v9_user_httpsd.conf.bak

Linux:

    <HCS-installation-directory>/uCPSB11/httpsd/conf/v9_user_httpsd.conf.bak

The location of the user_httpsd.conf file has been changed to the following folder or directory after upgrade installation.

Windows:

    <HCS-installation-folder>\Base64\uCPSB11\httpsd\conf\user_httpsd.conf

Linux:

    <HCS-installation-directory>/Base64/uCPSB11/httpsd/conf/user_httpsd.conf

(2) If you have changed the port 22035/tcp used by the common components from the default

Any changes made to port 22035/tcp, which is used by common components, written in webserver.connector.ajp13.port in the usrconf.properties file may not be inherited after upgrade installation.

Therefore, the configuration written in webserver.connector.ajp13.port in the following file must be configured to webserver.connector.nio_http.port in the user_httpsd.conf file after upgrade installation.

Windows:

    <HCS-installation-folder>\Base64\uCPSB11\httpsd\conf\v9_user_httpsd.conf.bak

Linux:

    <HCS-installation-directory>/uCPSB11/httpsd/conf/v9_user_httpsd.conf.bak

The location of the usrconf.properties file has been changed to the following folder or directory after upgrade installation. 

Windows:

    <HCS-installation-folder>\Base64\uCPSB11\CC\server\usrconf\ejb\HBase64StgMgmtSSOService\usrconf.properties

Linux:

    <HCS-installation-directory>/Base64/uCPSB11/CC/server/usrconf/ejb/HBase64StgMgmtSSOService/usrconf.properties

In addition, if you have changed the above ports, you will also need to change the port numbers from the default if they are listed in the following files.

- File location:

    Windows:

        <HCS-installation-folder>\Base64\uCPSB11\httpsd\conf

    Linux:

        <HCS-installation-directory>/Base64/uCPSB11/httpsd/conf

- Files: The following 4 files

    - reverse_proxy.conf

    - reverse_proxy_before.conf

    - reverse_proxy_after.conf

    - hsso_reverse_proxy.conf

(3) If you have changed the port 24234/tcp, 24235/tcp, 24239/tcp used by the common components from the default

Any changes made to port 24234/tcp, 24235/tcp, 24239/tcp, which is used by common components, written in webserver.connector.ajp13.port in the usrconf.properties file may not be inherited after upgrade installation.

Therefore, the configuration written in webserver.connector.ajp13.port in the following file must be configured to webserver.connector.nio_http.port in the user_httpsd.conf file after upgrade installation.

Windows:

    <HCS-installation-folder>\Base64\uCPSB11\httpsd\conf\v9_user_httpsd.conf.bak

Linux:

    <HCS-installation-directory>/uCPSB11/httpsd/conf/v9_user_httpsd.conf.bak

The location of the usrconf.properties file has been changed to the following folder or directory after upgrade installation.

Windows:

    <HCS-installation-folder>\Base64\uCPSB11\CC\server\usrconf\ejb\TuningManagerRESTService\usrconf.properties

Linux:

    <HCS-installation-directory>/Base64/uCPSB11/CC/server/usrconf/ejb/TuningManagerRESTService/usrconf.properties

In addition, if you have changed the above ports, you will also need to change the port numbers from the default if they are listed in the following files.

- File location:

    Windows:

        <HCS-installation-folder>\Base64\uCPSB11\httpsd\conf

    Linux:

        <HCS-installation-directory>/Base64/uCPSB11/httpsd/conf

- Files: The following 3 files

    - reverse_proxy.conf

    - reverse_proxy_before.conf

    - reverse_proxy_after.conf

(4) If you have changed the JDK used by the products to Oracle JDK

In an environment in which the JDK used by Tuning Manager server components has been switched to an Oracle JDK, if you upgrade the product to Tuning Manager 8.8.3 or later, the JDK used by Tuning Manager server components switches to the JDK bundled with the product.

Note on upgrade from Hitachi Command Suite 8.2.1-00

If you upgrade Tuning Manager to this version from an environment running Hitachi Command Suite 8.2.1-00 or earlier, the installation might fail. In this case, first upgrade the Tuning Manager server to a version in the range from 8.2.1-00 to 8.8.1-00, and then upgrade to this version.

For Windows operating system

Confirm Command Suite services are running

If you upgrade Hitachi Command Suite products from 7.6.1 or earlier to 8.0.0 or later, confirm the following services are running in the Services window in Windows. If both or one of them is not running, start them.

HiRDB/EmbeddedEdition_HD0

HiRDB/EmbeddedEdition_HD1

Upgrade Installation fails message with KATN00231-E if both or one of them is not running.

KATN00231-E An attempt to start the HiRDB database has failed. Processing will be stopped.

The error messages KAPM05050-E and KAPM05008-E are output to the event log when a command such as hcmds64backups is executed

When one of the following common component commands is executed with the /auto option specified (for example, to perform an operation in which the Tuning Manager services need to be stopped) or when the Tuning Manager server is installed, the error messages KAPM05050-E and KAPM05008-E are sometimes output to the Windows event log, even though the processing finishes normally. If no error message appears in the window where you executed the command, or if this problem occurs when you are performing an installation, you can ignore the error messages in the event log, because processing finishes normally in these situations.

Applicable commands and operations:

hcmds64backups

hcmds64db

hcmds64dbtrans

Installation of the Tuning Manager server

Contents of the error messages:

KAPM05050-E Failed to execute the command that stops services. (command name = "cjstopsv", return code = "1", server name = "TuningManagerRESTService")

KAPM05008-E Failed to stop service. service-name=HCS Tuning Manager REST Application Service

KAPM05050-E Failed to execute the command that stops services. (command name = "cjstopsv", return code = "1", server name = "PerfprmanceReporter")

KAPM05008-E Failed to stop service. service-name=HiCommand Performance Reporter

The error messages KAPM05050-E and KAPM05008-E are output to the event log when the command hcmds64srv /stop is executed

When the command hcmds64srv /stop is used to stop the Tuning Manager services, the error messages KAPM05050-E and KAPM05008-E are sometimes output to the Windows event log, even though the services are stopped normally. If this problem occurs, use the command hcmds64srv /statusall to check whether the services were stopped normally.

Contents of the error messages:

KAPM05050-E Failed to execute the command that stops services. (command name = "cjstopsv", return code = "1", server name = "TuningManagerRESTService")

KAPM05008-E Failed to stop service. service-name=HCS Tuning Manager REST Application Service

KAPM05050-E Failed to execute the command that stops services. (command name = "cjstopsv", return code = "1", server name = "PerfprmanceReporter")

KAPM05008-E Failed to stop service. service-name=HiCommand Performance Reporter

For Windows and Linux operating systems

When you upgrade the Tuning Manager server of a version earlier than 8.5.0 to 8.5.0 or later

Applied products: Tuning Manager Server, Agent for RAID

When you upgrade the Tuning Manager server of a version earlier than 8.5.0 to 8.5.0 or later, note the following:

In versions earlier than 8.5.0, the most recent association between LDEVs and processors might not be displayed due to invalid data in the Tuning Manager server database caused by a defect in the Tuning Manager server. If this problem occurs and the database data at a past time also has a problem, it might be possible to display the association by specifying the past time in the report window. However, after a certain time, the association cannot be displayed.

To avoid this problem, when upgrading from a version earlier than 8.5.0 to 8.5.0 or later, restore data in the database so that the most recent association between LDEVs and processors can be displayed correctly. Available modification methods are the automatic data restoration described below as a corrective action, as well as manually recovering before the upgrade. Each method has associated restrictions or side effects, as shown below. Therefore, perform one of the two options, (1) automatic restoration of data in the database during the upgrade or (2) manual recovery of data in the database before the upgrade.

1)    Automatic restoration of data in the database during the upgrade

a)    Task details
Perform an upgrade installation of the Tuning Manager server from a version earlier than 8.5.0 to 8.5.0 or later rather than performing the procedure described in (2) Manual recovery of data in the database before the upgrade, described later.

b)    Restrictions or side effects

-      Associations can no longer be displayed even for past times that were displayed correctly.
The past time for which associations can no longer be displayed depends on the LDEV. If the LDEV configuration has been changed, associations for the last time that the configuration changed can no longer be displayed, but those for earlier times can be displayed.

-      If polling is performed in a normal environment before a maximum of one hour has passed since the upgrade, the association between LDEVs and processors might not be displayed. In this case, you can display the association between LDEVs and processors by performing polling after a maximum of one hour has passed since the upgrade.

c)     Details and restrictions, and conditions for the occurrence of side effects
The information here applies if storage devices monitored by the Tuning Manager server have LDEVs for which the most recent associated processors cannot be displayed, and manual recovery of data in the database before the upgrade, the procedure described in (2) below, has not been performed.

2)    Manual recovery of data in the database before the upgrade

a)    Task details

                                                                      i.         Temporarily remove the affected storage from the monitoring targets of Tuning Manager Main Console, and then add it again as a monitoring target (the details are described later).

                                                                    ii.         Perform an upgrade installation of the Tuning Manager server.

                                                                   iii.         Perform polling.
For details about step (i), see <Step (i) details> described later. If you upgrade the Tuning Manager server of a version earlier than 8.5.0 to 8.5.0 or later after performing this recovery procedure, the side effects described in (1) do not occur, because automatic restoration of data in the database in (1) has not been performed.

b)    Restrictions or side effects
After the recovery procedure is performed, the Main Console handles the monitored storage as different storage compared to before the recovery. This causes the following side effects:

Problem with custom charts:

Charts defined for a storage system before a recovery is performed are no longer displayed after the recovery of the storage system. If the charts are necessary, re-define them after recovery.

Problem with performance information charts:

Performance charts for time periods before a recovery are not displayed in the report window.

Performance charts for time periods after a recovery can be displayed in Main Console on the Tuning Manager server. To view performance information collected before recovery, use Performance Reporter on the Tuning Manager server.

Problem with capacity information charts:

For the storage capacity charts displayed in Main Console on the Tuning Manager server, continuity of data collected before and after recovery will be lost. That is, if a time range that includes the time at which a recovery was performed is specified, the report window can display only data collected after the time at which recovery was performed.

To display a chart of data collected before recovery in the report window, set a time period before the time at which recovery was performed.

Recovery procedure:

Follow the recovery procedure below to delete, from the monitoring targets of the Tuning Manager server, the storage systems for which symptoms have occurred and then add those storage systems back to the monitoring targets.

1)    Clear the automatic-polling settings.

Note:

Before you clear the automatic-polling settings, make sure that you record them. You will need to restore these settings after the recovery in step 6).

For details about automatic-polling settings, see the following manual:

[Manual]

Tuning Manager Software Server Administration Guide

Specifying settings for data acquisition from Agents and Device Manager

Configuring the polling settings

2)    Stop the Agent for RAID instance.

a)    Log in (as a member of the Administrators group in Windows or as the root user in Linux) to the host that the Agent for RAID instance is running on.

b)    Stop the Agent for RAID instance that symptoms have occurred by executing the following commands.

-      In Windows:
cd Agent-installation-folder\tools
jpcstop agtd inst=Agent-for-RAID-instance-name

-      In Linux:
cd /opt/jp1pc/tools
./jpcstop agtd inst=Agent-for-RAID-instance-name

c)     Confirm that the service of the Agent for RAID instance that symptoms have occurred is in the Inactive status by executing the following command:

-      In Windows:
jpcctrl list "D*"

-      In Linux:
./jpcctrl list "D*"

3)    Remove the monitored Agent for RAID instance from the Tuning Manager server's monitoring targets.

a)    Log in (as a member of the Administrators group in Windows or as the root user in Linux) to the host that the Tuning Manager server is running on.

b)    Delete the service that corresponds to the Agent for RAID instance that symptoms have occurred from Collection Manager by executing the following commands:

-      In Windows:
cd Agent-installation-folder\tools
jpcctrl delete service-ID host=host-name

-      In Linux:
cd /opt/jp1pc/tools
./jpcctrl delete service-ID host=host-name

c)     Restart the Tuning Manager server on the host which was running the Tuning Manager server.

-      In Windows:
cd <Common-Component-installation-folder>\bin
hcmds64srv /stop /server TuningManager
hcmds64srv /start /server TuningManager

-      In Linux:
cd <Common-Component-installation-directory>/bin
./hcmds64srv -stop -server TuningManager
./hcmds64srv -start -server TuningManager

d)    Log in to the Tuning Manager server, and then perform refresh processing.

                                                                      i.         From the Administration menu, display the Polling Settings screen.

                                                                    ii.         In the application bar area, click the Refresh button.

e)    Confirm that the Agent for RAID instance that symptoms have occurred is not displayed as a related agent in the agent list of the Polling Settings screen.

4)    Start the Agent for RAID instance.
Start the Agent for RAID instance that symptoms have occurred on the host that was running the instance.

o   In Windows:
jpcstart agtd inst=Agent-for-RAID-instance-name

o   In Linux:
./jpcstart agtd inst=Agent-for-RAID-instance-name

5)    Start the Agent for RAID instance.

a)    On the Tuning Manager server, perform polling between from xx:15 and xx:59.

                                                                      i.         From the Administration menu, display the Polling Settings screen.

                                                                    ii.         In the agent list, select the objects to be monitored.

                                                                   iii.         In the report area, click the Start Polling button.

b)    Confirm that the Agent for RAID instance that symptoms have occurred is displayed as a related agent in the agent list of the Polling Settings screen.

c)     Check whether symptoms have occurred in the Agent for RAID instance. If a symptom has occurred, re-perform the steps from step 2). If the Agent for RAID instance has recovered from the symptoms, go to step 6).

6)    Restore the automatic-polling settings that you cleared.

Tuning Manager agents

For all operating systems

Upgrade all agents

To upgrade the version of Tuning Manager to 8.6.4 or later, you must also upgrade the Tuning Manager server and Tuning Manager agents running on the same host to version 8.6.4 or later.

Upgrading Agent for RAID or Agent for NAS from a version in the range from 8.5.1-00 to 8.5.3-00, to version 8.5.3-02 or later

In an environment where Hybrid Store is used or where the Tuning Manager API is enabled, before upgrading Agent for RAID or Agent for NAS from a version in the range from 8.5.1-00 to 8.5.3-00, to version 8.5.3-02 or later, make sure that all Tuning Manager Agent REST API component has been stopped.

Procedure:

1)    Use the command htmsrv stop -webservice to stop Tuning Manager Agent REST API component.

2)    Use the command htmsrv status -webservice to confirm that all Tuning Manager Agent REST API component has been stopped. If a component is still running, use an OS command or other means to forcibly stop the following process:

o   In Windows:

Name

Command Line

cjstartsv

<Agent-installation-folder>\htnm\HBasePSB\CC\server\bin\cjstartsv.exe AgentRESTService

o   In Linux:
/opt/jp1pc/htnm/HBasePSB/CC/server/bin/cjstartsv AgentRESTService

Storage systems monitored by Agent for RAID 8.8.0 or later

Monitoring of the following storage systems using the TCP/IP interface is no longer supported in Agent for RAID 8.8.0 or later.

Product name

Microcode version

VSP G1000

earlier than 80-06-63

VSP G1500

VSP F1500

earlier than 80-06-63

VSP F400

VSP F600

VSP F800

earlier than 83-05-29

VSP F350

VSP F370

VSP F700

VSP F900

earlier than 88-03-22

You can continue to monitor the storage systems listed in the table above by applying the microcode of a version described in "Hitachi Command Suite System Requirements" or the microcode of a later version. If you are using Agent for RAID 8.8.0 or later, upgrade the microcode version of your storage system in advance.

Notes on using Tuning Manager 8.8.0 or later

In an environment in which the JDK used by Tuning Manager Agent REST API components has been switched to an Oracle JDK, if you upgrade the product to Tuning Manager 8.8.0 or later, the JDK used by Tuning Manager Agent REST API components switches to the JDK bundled with the product.

If you are using Tuning Manager 8.8.0 or later, the htmchgjdk command cannot be used.

In an environment in which Agent for RAID and Agent for NAS are installed and operating on the same host, if you want to install v8.8.0-00 or later, install v8.8.0-00 or later on both Agent for RAID and Agent for NAS.

Notes on using RHEL 6 and Oracle Linux 6

Agents for Tuning Manager v8.8.0 and later do not support RHEL 6 and Oracle Linux 6. To upgrade Tuning Manager agents running on RHEL 6 or Oracle Linux 6 to v8.8.0 or later, migrate Tuning Manager products to a RHEL 7 or Oracle Linux 7 environment, and then install Tuning Manager v8.8.0 or later. Note that upgrading the OS in an environment where Tuning Manager has been installed is not supported.

Notes on upgrading Agent for RAID from a version earlier than v8.6.0 to v8.6.0 or later

Regarding environments in which Agent for RAID of a version earlier than v8.6.0 is installed and the Store database is used as the Performance database, when Agent for RAID in such an environment is upgraded to v8.6.0 or later but earlier than v8.8.0, the historical data prior to the upgrade might become invalid. If this occurs, you must delete the invalid historical data.

To determine in detail whether this situation applies, run the htmcheckdb command included with the product. Note that, if Hybrid Store was used as the performance database prior to Agent for RAID v8.6.0, there is no problem, so you do not need to run the htmcheckdb command.

[htmcheckdb command]

OS

Storage Location

User Authorized to Execute the Command

Command Name

Windows

DVD-ROM-mount-point\TOOL\htmcheckdb

Member of the Administrators group

htmcheckdb.bat

Linux

DVD-ROM-mount-point/TOOL/htmcheckdb

root user

htmcheckdb.sh

[Example]

# htmcheckdb.bat

installed version=085002

result: OK

If the output result of the executed command contains "result: OK", this situation does not apply. No action is required. However, if the following message is displayed during the upgrade process, continue the installation.

Part of the data in the Store database might be damaged. Normal operation might not be possible. Check the Release Notes and, before installation, take appropriate action. Installation might further damage the data. If no action has been taken yet, stop this installation and take appropriate action. Are you sure you want to continue this installation? (Y/N)

If the output result of the executed command contains something other than "result: OK", then the historical data might be corrupted. As a result, the corrupted historical data must be checked in detail and action is required. Use the jpcras command to collect maintenance information, and then contact your system administrator.

For Windows operating system

Backup files before upgrade

Applied products: Agent for RAID

On windows(x64), when you upgrade Agent for RAID from the version between 8.0.0 and 8.1.2 to 8.1.3 or later version, and if a private key file and a certificate file are stored in the following folders, you must backup those files before upgrade installation.

Those files must be manually restored to the same folder after upgrade installation.

Location of the private key file:

<Agent-installation-folder>/htnm/HBasePSB/httpsd/conf/ssl/server

Location of the certificate file:

<Agent-installation-folder>/htnm/HBasePSB/httpsd/conf/ssl/cacert

Removal precautions

Tuning Manager Server

None.

Tuning Manager agents

For Windows operating system

Not removed from Start menu

The menu item Administrator Console - HTnM is not removed from the Start menu if both of the following conditions are met:

1)    The Tuning Manager agent is not installed on the host on which the Tuning Manager server is installed.

2)    The version of the last uninstalled Tuning Manager agent is 7.4.1 or earlier.

Preventive measures:

Uninstall the Tuning Manager agent first.

Action to be taken if the problem has occurred:

After the Tuning Manager agent has been uninstalled from all hosts, manually remove Administrator Console - HTnM if it remains in the Start menu.

For Windows and Linux operating systems

Multiple versions installed in the same environment

A Tuning Manager agent whose version is 8.4.1 or earlier and a Tuning Manager agent whose version is 8.5.0 or later might be installed in the same environment. In such a case, if you want to uninstall both Tuning Manager agents, uninstall Tuning Manager agent 8.4.1 or earlier first.

Usage precautions

Notes on using in the built-in Administrator account when using Internet Explorer 11.0

Applied product: Tuning Manager server

Applied OS: Windows

When you click a button or anchor on the screen to open a new tab or new window, an extra blank window or transitional window might be displayed at the same time. In such a case, please close the unnecessary window.

If this problem occurs, create a new Windows user account, and then use the new user account to operate the browser.

Notes on the use of Performance Reporter when using Internet Explorer 11.0

Applied product: Tuning Manager server

Applied OS: Windows

When you select any record in [All Fields] in the [New Report > Field] window of the Report Wizard, the text box for the description may appear with its lower edge cut off. If this happens, adjust the display width of the frame information by adjusting the window size or position dividers.

Precautions for displaying a list of installed programs

Tuning Manager server

Applied OS: Windows

When the Add or Remove Programs dialog box is opened, the displayed icon of this product might switch from an icon displayed initially to the other icon (*1).

*1: Any of the icons registered in Windows

Even if this symptom occurs, the Tuning Manager server is operational normally.

Tuning Manager agents

None.

Precautions for monitoring Brocade SAN switches

Tuning Manager server

None.

Tuning Manager agents

If Brocade(R) SMI Agent v120.6.0x (x is "a" or later) or v120.7.1 is used for monitoring a fabric consisting of only Brocade switches whose firmware versions are v5.2.0 or later, a blank might appear for Model Name and Vendor Name for these switches. Brocade has corrected this problem in Brocade SMI Agent v120.7.2. To monitor Brocade switches, use Brocade SMI Agent v120.7.2 or later.

If Brocade SMI Agent v120.8.0 or v120.9.0 is used for monitoring a fabric including Brocade switches whose firmware versions are v5.2.x, Agent for SAN Switch might fail to collect the data necessary to create a record. Upgrade the firmware version of all switches in the same fabric to v5.3.x or later.

Notes for trouble on an operation of Agent for SAN Switch

Tuning manager server

None.

Tuning Manager agents

When Agent for SAN Switch causes a trouble while monitoring CISCO switches, we might ask to gather material for investigation with the packet capture tool etc.

Precautions for displaying a correlation reports

Tuning manager server

Even if a system failover is performed by High Availability Manager functionality for the Universal Storage Platform V/VM series, Virtual Storage Platform, the Tuning Manager server continues to display the active volume, not the standby volume, as related to the relevant device file.

Tuning manager agents

None.

Precautions for monitoring again a Storage System or a Server which had been monitored in the past

Tuning Manager server

If users accidentally delete a storage device or host from the list of targets to be monitored by Tuning Manager, or if users accidentally change the storage configuration, the Tuning Manager server might not properly display information even if the status of the storage device or host is restored. Table-1 describes the relationship between the devices monitored by the Tuning Manager server and the information that cannot be properly displayed.

Table-1 Devices monitored by the Tuning Manager server and related error

Item

Devices monitored by the Tuning Manager server

Error

Storage

Host

Virtualization server

a

*

Relevant information between storage components is not properly displayed

b

*

*

Relevant information between storage devices and hosts is not properly displayed.

c

*

*

Relevant information between storage devices and virtualization servers is not properly displayed.

Legend:

* Monitored devices for which the error occurs

Blank: Monitored devices for which the error does not occur.

The conditions that cause the error and the recovery procedure are as follows:

Conditions

This error might occur if either of the following operations is performed:

1)    Operation 1:

a)    Add the devices indicated by * in Table-1 (b) or (c) to the list of targets to be monitored by the Tuning Manager server. Then, refresh the list of Agents on the Tuning Manager server.

b)    From the Tuning Manager server, perform automatic or manual polling on the monitoring targets that were added in step (a).

c)     After polling, delete the storage devices or hosts from the list of targets to be monitored by the Tuning Manager server by using one of the following operations:

d)    [For storage devices]

-      Delete Agent for RAID from the list of targets to be monitored by the Tuning Manager server.

-      Remove the storage devices from Device Manager.

e)    [For hosts]

-      Delete Agent for Server System from the list of targets to be monitored by the Tuning Manager server (if the host is monitored in Agent mode).

-      Remove the host from Device Manager (if the host is monitored in agentless mode).

f)      Refresh the list of Agents on the Tuning Manager server.

g)    Add the monitoring targets that were deleted in step (c) and whose configurations have not been changed since step (c) to the list of targets to be monitored by the Tuning Manager server again by using one of the following operations:

h)    [For storage devices]

-      Add Agent for RAID to the list of targets to be monitored by the Tuning Manager server.

-      Add the storage devices to Device Manager.

i)      [For hosts]

-      Add Agent for Server System to the list of targets to be monitored by the Tuning Manager server (if the host is monitored in Agent mode).

-      Add the host to Device Manager (if the host is monitored in agentless mode).

j)      Refresh the list of Agents on the Tuning Manager server.

k)     From the Tuning Manager server, perform automatic or manual polling again on the monitoring targets on which polling was performed in step (ii).

2)    Operation 2:

a)    Add the devices indicated by * in Table-1 (a), (b), or (c) to the list of targets to be monitored by the Tuning Manager server. Then, refresh the list of Agents on the Tuning Manager server.

b)    From the Tuning Manager server, perform automatic or manual polling on the monitoring targets that were added in step (a).

c)     For the monitored storage devices, one of the following operation is performed:

-      Remove the hardware (port or disk)

-      Delete the SLPR or CLPR

-      Change SLPR that belongs to the command device.

d)    From the Tuning Manager server, perform automatic or manual polling again on the monitoring targets on which polling was performed in step (b).

e)    For the monitored storage devices indicated in step (c), restore them to their status before step (c).

f)      From the Tuning Manager server, perform automatic or manual polling again on the monitoring targets on which polling was performed in step (b).

Table-2 lists the information that is not properly displayed after Operation 1 or Operation 2 is performed.

Table-2 Operations that cause this error and the information that is not properly displayed

Operation

Information that is not properly displayed

Operation 1

Table-1 (b) and (c)

Operation 2

Table-1 (a), (b), and (c)

Recovery procedure

Perform one of the procedures below (from 1 to 3) indicated in Table-3 depending on the monitored device on which the error occurred.

Table-3 Procedures for recovering from the error

Condition

Information that is not properly displayed

The error occurs on a host that is being monitored in agentless mode.

Procedure 1

The error occurs on a virtualization server.

Procedure 2

In cases other than 1 and 2.

Procedure 3

Procedure 1:

1)    Remove from Device Manager the storage device that contains volumes that are connected to the host.

2)    Use Device Manager to refresh the host indicated in step (1).

3)    From the Tuning Manager server, perform manual polling on Device Manager.*

4)    Add the storage device that was removed from Device Manager in step (1) to Device Manager again.

5)    Use Device Manager to refresh the host indicated in step (1) again.

6)    From the Tuning Manager server, perform manual polling on Device Manager.#1

* Be sure to wait at least one hour after the last polling was performed before you perform manual polling.

Procedure 2:

1)    Delete the storage device that contains volumes being used as a datastore of the virtualization server from the list of targets to be monitored by the Tuning Manager server by using one of the following operations:

o   Delete Agent for RAID from the list of targets to be monitored by the Tuning Manager server.

o   Remove the storage devices from Device Manager.

2)    From the Tuning Manager server, perform manual polling on the Device Manager that manages the virtualization server indicated in step (1).*

3)    Add the storage device that was removed from the list of targets to be monitored by the Tuning Manager server in step (1) to the list of monitoring targets again.

o   Add Agent for RAID to the list of targets to be monitored by the Tuning Manager server.

o   Add the storage devices to Device Manager.

4)    From the Tuning Manager server, perform manual polling on Device Manager.#1

* Be sure to wait at least one hour after the last polling was performed before you perform manual polling.

Procedure 3:

1)    Delete the monitoring targets whose information is not properly displayed from the list of targets to be monitored by the Tuning Manager server.

2)    Add the monitoring targets that were removed in step (1) to the list of targets to be monitored by the Tuning Manager server again.

3)    From the Tuning Manager server, perform manual polling on the Tuning Manager Agents that monitor the added targets.*

* Be sure to wait at least one hour after the last polling was performed before you perform manual polling.

Tuning Manager agents

None.

Precautions for displaying a vendor name of the switch

Applied products: Tuning Manager server, Agent for SAN Switch

Applied OS: All supported operating systems.

When all of the following conditions are met, Unknown might be displayed for the switch's vendor name on the tree.

1)    In Agent for SAN Switch, Vendor Name field of PD record for some instance is empty string.

2)    The combination of the version of the prerequisite program, such as SMI Agent for FOS/EOS and DCFM, and the firmware version of the switch is not supported.

The recovery procedure is as follows:

a)    Stop the instance of Agent for SAN Switch for which Vendor Name field of PD record includes empty string.

b)    Confirm the version of the following prerequisite program for the switch which is monitored by the Agent for SAN Switch in a).

-      SMI Agent for FOS/EOS or DCFM (For the Brocade switch only)

-      firmware version of the switch

For details about the supported version of the prerequisite programs for Agent for SAN Switch., see the Hitachi Command Suite System Requirements (MK-92HC209).

c)     Start the service of Tuning Manager server.

d)    Execute the following command on the Tuning Manager server host to delete the instance of the Agent for SAN Switch from the monitoring target.
jpcctrl delete "<service ID of the Agent for SAN Switch instance in a)>"

e)    Click Refresh button on the screen of Administration - Data Polling.

f)      Start the service of Agent for SAN Switch which is stopped in a).

g)    Click Start Polling button on the screen of Administration - Data Polling.

h)    Confirm the Navigation area of the Fabrics and make sure that the switch which is monitored by the Agent for SAN Switch of a) is displayed under the vendor name other than Unknown.

Precautions when rebooting OS

Applied products: Tuning Manager server, Tuning Manager agents

Applied OS: Windows

When the available IPv6 address has been set in windows system, the symptom such as the following might occur, because the Tuning Manager service has been started abnormally after rebooting the OS.

The report might not be displayed by using Performance Reporter.

If the above symptom has occurred, perform the following actions after rebooting OS.

Stop the Tuning Manager services by executing the hcmds64srv /stop command and the jpcstop command.

Restart Tuning Manager services by the hcmds64srv /start command and the jpcstart command.

If the Tuning Manager services have failed to stop, stop all Tuning Manager services manually whose names are started with "PFM -" from Service Control Manager.

To start Service Control Manager, from the Windows Start menu, select Administrative Tools, and then select Services.

Precautions for installation folder

Applied products: Tuning Manager server, Tuning Manager agents

Applied OS: Windows

Do not put files or folders other than provided by Tuning Manager under the following folder.

<Tuning-Manager-installation-folder>\jp1pc\tools

If you put files or folders other than provided by Tuning Manager to the above folder, executing of commands or starting of the Tuning Manager services might fail.

Notes on InPrivate Browsing of Internet Explorer 9.0

Applied products: Tuning Manager server

Applied OS: Windows

During InPrivate Browsing Mode, the browsing history might remain in the browser.

Notes of using Chrome or Edge

Applied products: Tuning Manager server

Applied OS: Windows

When the browser being used is Chrome or Edge, in some cases the Close button of the Main Console does not work in Tuning Manager. In this case, close the browser window itself.

When the browser being used is Chrome or Edge, in some cases an option(*) appears to prevent dialog boxes from being displayed. This option must not be selected during operation of Tuning Manager. If this option is selected, no dialog boxes will be displayed in Tuning Manager and some windows might not work correctly. In this case, restart browser and log in to Tuning Manager again to display dialog boxes.

(*) Examples of messages displayed for the option:

Prevent this page from creating additional dialogs.

Notes of the Server Core or Nano Server option of Windows

Applied products: Tuning Manager server, Tuning Manager agents

Applied OS: Windows

Server Core or Nano Server mode is not supported.

Notes of the Minimal Server Interface of Windows Server 2012

Applied products: Tuning Manager server, Tuning Manager agents

Applied OS: Windows

Minimal Server Interface is not supported.

When the Tuning Manager service does not start or stop

Applied products: Tuning Manager server, Tuning Manager agents

Applied OS: All supported operating systems

When the Tuning Manager service starts, the following message may be output to the common message log, syslog(for UNIX) or event log(for Windows), causing a disk space shortage or some other factors.

KAVE00201-E An attempt to access the configuration file failed. (file=<file path of jpcns.ini>)

In this case, the following symptoms may occur:

a)    An attempt to stop the service fails outputting the following message to the common message log:
KAVE05034-E A service could not stop. (service=service-name, rc=maintenance-code)

b)    An attempt to start the service fails outputting the following message to the common message log, syslog(for UNIX) or event log(for Windows):
KAVE00100-E An error occurred in an OS API(bind). (en=os-detailcode, arg1=argument-1, arg2=argument-2, arg3=argument-3)
KAVE00107-E The network environment is invalid. (rc=maintenance-code)
KAVE00160-E An attempt to initialize a service failed. (rc=maintenance-code)

When these symptoms occur, check whether processes of the Tuning Manager services remain with the Task Manager (for Windows) or the ps command (for UNIX). If these processes remain, kill them and restart the service.

Monitoring Windows hosts

Applied products: Agent for Server System

Applied OS: Windows

CPU information can be collected only for up to 64 CPUs.

Therefore, if a host that has 65 or more CPUs is monitored, record instances exceeding 64 cannot be acquired for the PI_PCSR record of Agent for Platform. In addition, the value of the Active CPUs field in the PI record is always 64.

Precautions when installing on Windows Server

Applied products: Tuning Manager server, Tuning Manager agents

Applied OS: Windows

Immediately after performing installation, invalid menu "Performance Management" may be displayed in Apps windows, and Administrator Console may not be started.

In this case, sign-in to your host again.

Note on using Tuning Manager on a Linux server

Start X server

To use Tuning Manager on a Linux server, configure and start X server.

In Main Console of Tuning Manager, the performance chart is not displayed.

Services file

If you use the jpcnsconfig port list command to display the Status Server port number, or use the jpcnsconfig port define command to set the Status Server port number to 22350, the following message is sometimes output.

jpcnsconfig port list:

KAVE05919-E The port number is not registered correctly in the services file.

jpcnsconfig port define:

KAVE05918-W The specified port number is in use by another.

If this happens, /etc/services might contain the following:

CodeMeter 22350/tcp

The above text is added to the services file on installation of the OS, regardless of whether the described product is installed. For this reason, confirm whether the applicable product is used, and if it is not used, comment out this text. If the applicable product is used, or if the port number is registered for a different product, ensure that port number conflicts do not occur within the server.

Precautions for monitoring the NAS Platform

Applied products: Agent for NAS

Applied OS: All supported operating systems

NAS Platform in a single node configuration used with an internal SMU/NAS Manager is not supported by Agent for NAS as a monitoring target.

Notes on using Hybrid Store

Memory usage

Applied products: Agent for RAID, Agent for NAS

Applied OS: Windows, Linux

When the amount of memory that is available on the system is less than the memory usage by this software, the installation on Hybrid Store may fails, or the service may not start at after the installation or converting to Hybrid Store.

To avoid these cases, install the software on a system that has enough memory.

For details about the amount of memory for Agent for RAID, see the Hitachi Command Suite System Requirements (MK-92HC209).

Physical memory

Applied products: Agent for RAID, Agent for NAS

Applied OS: Windows, Linux

When the amount of physical memory that is available on the system is less than the memory used by this software, A delay to collect performance data might happens or performance data might be dropped because of the processing capacity shortage.

To avoid these cases, please try one of the following methods.

Set longer collection interval.

Install the software on a system that has enough physical memory.

For details about the amount of memory for Agent for RAID, see the Hitachi Command Suite System Requirements (MK-92HC209).

Checking the disk capacity

Applied products: Agent for RAID, Agent for NAS

Applied OS: Windows, Linux

The displayed Hybrid Store disk capacity (the Disk Usage node of the Performance Reporter - Agent Store service properties) is incorrect. The value -1 is displayed for the Product Interval and Product Details properties, and -2 is displayed for the Total Disk Usage property of the Disk Usage node of Hybrid Store. For this reason, to check the disk capacity of Hybrid Store, use the function provided by the OS of the machine on which Agent is running. Note that the displayed disk capacity of the Store database is correct.

For Windows:

In Explorer, display the properties of the output-destination folder of Hybrid Store and check the folder size.

For UNIX:

Use the OS command du (or a similar command) to check the size of the output-destination directory of Hybrid Store.

Example:

du -s -h <output-destination-directory-of-Hybrid-Store>

For information on the output destination of Hybrid Store, see the description Changing the destination of Hybrid Store output in the Hitachi Tuning Manager Agent Administration Guide.

Notes on the alert function

Applied products: Tuning Manager server

Applied OS: All supported operating systems.

To use the API of the alert function directly or via the htmrest command, make sure that API calls are serialized. (That is, if a request to execute an API function is issued, do not issue another API function request before the response is returned to the current request and the requested API function is executed.)

If API functions are executed concurrently, Device Manager processing might slow down temporarily.

Notes on the directories created by the prerequisite checker will remain (Linux)

Applied products: Tuning Manager server

Applied OS: Linux

The prerequisite checker creates the following directories when checking the prerequisites:

<Installation directory>/TuningManager

/var/<Installation directory>/TuningManager

Directory for saving the database

After checking the prerequisites, if the installation is continued with the same settings as when the checking was performed, a directory created by the prerequisite checker is used for the installation directory.

If the same settings used for checking the prerequisites are not used for the installation, the directories created by the prerequisite checker will remain. Delete them, if necessary.

For details about the prerequisite checker, see the Hitachi Command Suite Installation and Configuration Guide (MK-90HC173).

When a properties file is invalid for an environment where Hybrid Store is used

Applied products: Tuning Manager agents

Applied OS: Windows, Linux

If any of the following properties files are invalid for an environment where Hybrid Store is used, KATR13240-E is output to the message log (htmRestDbEngineMessage#.log) when the Tuning Manager Agent REST API component service is started. Even though the service could not be started, the console and the message log (htmsrvMessage#.log) show that the service is running.

If KATR13240-E is output, revise the invalid properties file, and then restart the Tuning Manager Agent REST API component service.

[Properties files]

In Windows:

installation-folder\htnm\agent\config\dbdataglobalconfig.ini

installation-folder\htnm\agent\config\alertglobalconfig.ini

In UNIX:

/opt/jp1pc/htnm/agent/config/dbdataglobalconfig.ini

/opt/jp1pc/htnm/agent/config/alertglobalconfig.ini

[Message log files]

In Windows:

installation-folder\htnm\log\htmRestDbEngineMessage#.log

installation-folder\htnm\log\htmsrvMessage#.log

In UNIX:

/opt/jp1pc/htnm/log/htmRestDbEngineMessage#.log

/opt/jp1pc/htnm/log/htmsrvMessage#.log

Examples of invalid descriptions in properties files:

The number of square brackets that indicate a section or subsection is not correct.

A subsection is not located under a section.

The same key is defined more than once in the same section.

The same section is defined more than once in the same file.

Precautions for monitoring a host in agentless mode Tuning Manager server

Applied products: Tuning Manager server

Applied OS: All supported operating systems

When virtual IDs are assigned to volumes for using a virtual storage machine, the volumes cannot be monitored in agentless mode.

New installation or upgrade installation on a machine with Hitachi Replication Manager.

Applied products: Tuning Manager server

Applied OS: Windows, Linux

New installation or upgrade installation on a machine with Hitachi Replication Manager.

Before an installation or upgrade installation on a server that has the following product version installed, complete the procedure described.

Version:

Hitachi Replication Manager 8.0.0-00 to earlier than 8.4.0-00

Hitachi Device Manager 8.0.0-00 to earlier than 8.4.0-00

Procedure:

For Windows:

1)    If Device Manager is remotely linked with Tuning Manager, shut down the Tuning Manager server.

2)    Log in to Windows as the administrator.

3)    When installing Hitachi Command Suite in a cluster environment, take Hitachi Command Suite services offline. Then suppress failover of the resource group according to the following sections in the Hitachi Command Suite Installation and Configuration Guide depending on the version from which you are upgrading.

For 8.0.0-00 to earlier than 8.2.0-00:

o   Suppressing failover when upgrading or overwriting Hitachi Command Suite (Windows)

For 8.2.0-00 or later:

o   Taking Hitachi Command Suite services offline (Windows)

4)    Run the Command Prompt as the administrator and then execute the following commands in the order listed.

a)    cd /d <Hitachi-Command-Suite-installation-folder>\Base64\bin

b)    hcmds64srv /stop

c)     hcmds64srv /statusall

d)    hcmds64dbsrv /start

e)    cd <Hitachi-Command-Suite-installation-folder>\Base64\sbin

f)      hcmdsdbreclaim -k index -a -c dic

g)    hcmdsdbreclaim -k index -j -c dic

h)    hcmdsdbreclaim -k table -a -c dic

i)      hcmdsdbreclaim -k table -j -c dic

For Linux:

1)    If Device Manager is remotely linked with Tuning Manager, shut down the Tuning Manager server.

2)    Log in as root.

3)    When installing Hitachi Command Suite in a cluster environment, delete the HCS product services from the Red Hat High Availability service group according to the section "Deleting HCS product services from the service group (Red Hat Enterprise Linux)" in the Hitachi Command Suite Installation and Configuration Guide.

4)    Start the terminal window and then execute the following commands in the order listed.

a)    cd <Hitachi-Command-Suite-installation-directory>/Base64/bin

b)    ./hcmds64srv -stop

c)     ./hcmds64srv -statusall

d)    ./hcmds64dbsrv -start

e)    cd <Hitachi-Command-Suite-installation-directory>/Base64/sbin

f)      ./hcmdsdbreclaim -k index -a -c dic

g)    ./hcmdsdbreclaim -k index -j -c dic

h)    ./hcmdsdbreclaim -k table -a -c dic

i)      ./hcmdsdbreclaim -k table -j -c dic

Precautions for monitoring Windows hosts in the global-active device configuration using Agent for Server System

Applied products: Agent for Server System

Applied OS: Windows

If a Windows host monitored by Agent for Server System uses a disk or device special file in the global-active device (GAD) configuration of VSP Fx00 models and VSP Gx00 models, the Product Name field of the PD_FSC records collected by Agent for Server System has the same value even for GAD pair volumes allocated in storage systems of different model.

Notes related to the use of alarms for operational monitoring

Applied products: Tuning Manager server

Applied OS: All supported operating systems

If you use more than one expression to configure an alarm condition, do not specify more than one record.

If multiple records are specified in the conditional expressions, the alarm condition will not be evaluated correctly.

When monitoring externally connected storage system

Applied products: Agent for RAID

Applied OS: Windows, Linux

If VSP G1000, G1500 or VSP F1500 is connected externally via iSCSI, the value in the DKC Name field of the PD_ELC records of Agent for RAID will be "unknown storage".

Using Agent for Microsoft Exchange Server environment

Applied products: Agent for Server System

Applied OS: Windows

When Agent for Server System is upgraded to the version 8.5.3 or later in an environment in which using Agent for Microsoft Exchange Server, Agent for Microsoft Exchange Server is no longer be able to uninstalled individually.

To remove Agent for Microsoft Exchange Server, you must remove Agent for Server System that contains Agent for Microsoft Exchange Server and then install Agent for Server System again.

Cautionary notes on Adobe® AIR® and Adobe Flash Player

Applied products: Tuning Manager server

Applied OS: Windows, Linux

When the Tuning Manager server and Device Manager are installed on the same host and the Device Manager version is 8.7.4 or later, if you log in from a browser on which Adobe Flash Player is disabled, you cannot check or register the license from the login window. To check or register the license, download the Adobe AIR desktop application from the Device Manager, and then check or register the license from the Device Manager window.

When the Tuning Manager server and Device Manager are installed on the same host and the Device Manager version is 8.7.4 or later, if you log in to Tuning Manager server from a browser on which Adobe Flash Player is disabled, you cannot then check or register the license. To check or register the license, download the Adobe AIR desktop application from the Device Manager, and then check or register the license from the Device Manager window.

If you use Device Manager version 8.7.4 by the GUI on Adobe AIR desktop application, you cannot start the Tuning Manager server from the Device Manager Tool menu. Start your browser and then enter the Tuning Manager server URL.

If you use the Tuning Manager server from a browser on which Adobe Flash Player is disabled, you need to revise the settings in the Tuning Manager server properties file. Edit the rpt.flashmode property in the user properties file (user.properties) to change from the setting that displays charts by using Adobe Flash Player, to the setting that displays images (PNG format). The default setting displays all charts as images (PNG format). For details on settings in the user properties file, see the manual Hitachi Command Suite Tuning Manager Server Administration Guide.

About switching to an Oracle JDK

Applied products: Tuning Manager server, Tuning Manager agents

Applied OS: Windows, Linux

When using Tuning Manager agents v8.8.0 or later, you cannot switch the JDK used by Tuning Manager Agent REST API components to an Oracle JDK.

When using Tuning Manager server v8.8.3 or later, you cannot switch the JDK used by Tuning Manager server components to an Oracle JDK.

Notes on monitoring storage systems for which the Fibre Channel port operating mode is set to NVMe mode

Applied products: Tuning Manager server, Tuning Manager agents

Applied OS: Windows, Linux

Both Tuning Manager and Device Manager must be v8.8.3 or later.

You cannot monitor concepts specific to NVMe mode (such as NVM subsystems) or host groups that belong to ports set to NVMe mode.

In RHEL 8 and Oracle Linux 8 environments, if you log in by using the OS GUI and then perform any of the following operations that involve starting the services of Tuning Manager agents, the services of Tuning Manager agents stop when you log out of the OS GUI.

Applied products: Tuning Manager agents

Applied OS: Linux

 (a) Execution of the following commands that involve starting the services of Tuning Manager agents

- htmsrv start command

- jpcstart command

(b) Installation of Tuning Manager agents

If you want to perform the above operations, connect to Linux remotely by using SSH, and then perform the operations.

In addition, if the services of Tuning Manager agents are running on the OS GUI, perform the following steps to continue running the services even after you log out of the OS GUI.

(a) Run the following command to stop all services of Tuning Manager agents.

- If Agent for RAID or Agent for NAS is installed on the host:

        /opt/jp1pc/htnm/bin/htmsrv stop -all

- If neither Agent for RAID nor Agent for NAS is installed on the host:

        /opt/jp1pc/tools/jpcstop all

(b)Start the services of Tuning Manager agents by using one of the following methods.

- Connect to Linux remotely by using SSH, and then run the command to start the services of Tuning Manager agents.

- Enable the automatic start of the services of Tuning Manager agents, and then restart the OS.

Documentation

Available documents

Document name

Document number

Issue Date

Hitachi Command Suite Tuning Manager Installation Guide

MK-96HC141-34

April 2018

Hitachi Command Suite Tuning Manager Server Administration Guide

MK-92HC021-44

April 2018

Hitachi Command Suite Tuning Manager Agent Administration Guide

MK-92HC013-43

October 2019

Hitachi Command Suite Tuning Manager User Guide

MK-92HC022-44

April 2018

Hitachi Command Suite Tuning Manager Hardware Reports Reference

MK-95HC111-32

October 2019

Hitachi Command Suite Tuning Manager Operating System Reports Reference

MK-95HC112-23

October 2019

Hitachi Command Suite Tuning Manager Messages

MK-95HC114-34

April 2018

Hitachi Command Suite Tuning Manager CLI Reference Guide

MK-96HC119-34

October 2019

Hitachi Command Suite Tuning Manager Getting Started Guide

MK-96HC120-25

April 2018

Hitachi Command Suite Tuning Manager API Reference Guide

MK-92HC218-09

October 2019

For this version, refer to the manuals for 8.6.0-00.

Documentation errata

The Hitachi Tuning Manager Documents are not revised for this version. Use the information in this section to search for specific content in the document and replace it with revised content for this version.

All documents

Location to be corrected

Multiple pages

Existing content

Windows Server 2012

Revised content

Windows Server 2012, Windows Server 2016, Windows Server 2019, Windows Server 2022

Location to be corrected

Multiple pages

Revised content

In locations where "FMC" is written, please read it as "FMD", "FMD DC2", or "FMD HDE".

Location to be corrected

Multiple pages

Existing content

Linux 7

Revised content

Linux 7, Linux 8

Location to be corrected

Multiple pages

Existing content

uCPSB

Revised content

uCPSB11

Location to be corrected

Multiple pages

Existing content

uCPSB/jdk/jre

Revised content

uCPSB11/jdk

Tuning Manager Installation Guide

Contents of corrections of the Hitachi Command Suite Tuning Manager Installation Guide

Location to be corrected

Multiple pages

Existing content

VSP Gx00 models or VSP Fx00 models

Revised content

VSP Gx00 models, VSP Fx00 models or VSP Nx00 models

Location to be corrected

Multiple pages

Existing content

VSP G1000, G1500, VSP F1500, VSP Gx00 models, VSP Fx00 models

Revised content

VSP 5000 series, G1000, G1500, VSP F1500, VSP Gx00 models, VSP Fx00 models, VSP Nx00 models

Location to be corrected

Multiple pages

Existing content

VSP G1000, G1500, or VSP F1500, VSP Gx00 models, VSP Fx00 models

Revised content

VSP 5000 series, G1000, G1500, or VSP F1500, VSP Gx00 models, VSP Fx00 models, VSP Nx00 models

Location to be corrected

Multiple pages

Existing content

VSP Gx00 models, VSP Fx00 models, HUS VM, VSP G1000, G1500, VSP F1500

Revised content

VSP 5000 series, Gx00 models, VSP Fx00 models, VSP Nx00 models, HUS VM, VSP G1000, G1500, VSP F1500

Location to be corrected

Multiple pages

Existing content

VSP Gx00 model, VSP Fx00 model, HUS VM, VSP G1000, G1500, VSP F1500

Revised content

VSP 5000 series, Gx00 model, VSP Fx00 model, VSP Nx00 model, HUS VM, VSP G1000, G1500, VSP F1500

Location to be corrected

1. Overview

Enhancing file permissions

Existing content

Create an HTnM users group, and assign the permissions from Modify downwards to the group. Once these permissions have been assigned, only users who belong to the HTnM users group will be able to execute HTnM commands that could be executed previously by users with general user permission. Modify the permissions for the folder Collection-Managerinstallation-folder and Agent-installation-folder as shown in the following table:

Revised content

Create an HTnM users group, and assign the permissions from Modify downwards to the group. Once these permissions have been assigned, only users who belong to the HTnM users group will be able to execute HTnM commands that could be executed previously by users with general user permission. Modify the permissions for the folder Collection-Managerinstallation-folder, Agent-installation-folder, Performance-database-output-folder and logical-host-folder as shown in the following table:

Location to be corrected

2. Preparing to install or upgrade the Tuning Manager server

Reviewing the installation notes

Items required for a Windows system

Added content

Notes on adding role of Remote Desktop Session HOST

If you add the role of Remote Desktop Session HOST, make sure to enable the "Turn off Windows Installer RDS Compatibility" setting in the Windows Local Group Policy Editor. If the setting is not configured or disabled, the installation of common component might fail with the KAIB20200-E error during the Hitachi Command Suite products installation.

To check the current policy configuration, browse the following directory tree with Windows Local Group Policy Editor.

[Local Computer Policy](*)

[Computer Configuration]

[Administrative Templates]

[Windows Components]

[Remote Desktop Services]

[Remote Desktop Session Host]

[Application Compatibility]

*: If the Hitachi Command Suite products installation target server machine is joined as a member of Windows Active Directory, ask your domain administrator about the configuration regarding the above policy.

Location to be corrected

2. Preparing to install or upgrade the Tuning Manager server

Before using in a cluster environment

Prerequisites for setting up a cluster environment

Shared disk

Deleted content

·       The shared disk is physically connected to the host.

Tuning Manager servers do not support configurations in which a network drive or a disk replicated through a network is used as a shared disk.

Location to be corrected

3. Installing or upgrading the Tuning Manager server

About upgrade installations

Added content

Note on the java.policy file that has been edited.

If the java.policy file has been edited, backup the file before upgrade or overwrite installation. The file must be manually restored after the installation.

Location of java.policy file

o   In Windows:
Tuning-Manager-server-installation-folder\jp1pc\mgr\viewsrv\java.policy

o   In Linux:
Tuning-Manager-server-installation-directory/jp1pc/mgr/viewsrv/java.policy

Location to be corrected

3. Installing or upgrading the Tuning Manager server

About upgrade installations

Deleted content

Notes on using Oracle JDK 7

If you are using Oracle JDK 7 and perform an upgrade installation for a Tuning Manager server earlier than v8.2.1, Oracle JDK 7 is automatically switched to the JDK version packaged with Hitachi Command Suite products. If you want to continue to use Oracle JDK, switch the JDK version to Oracle JDK supported by the Tuning Manager server again.

For details about how to switch to Oracle JDK, see the Hitachi Command Suite Tuning Manager Server Administration Guide.

Location to be corrected

3. Installing or upgrading the Tuning Manager server

Items to be checked after upgrading Tuning Manager

Added content

Upgrade installation from v8.7.3 or earlier

In the Linux edition, only operations by the root user are supported. After installing version 8.7.4 or upgrading to a later version, ordinary users cannot perform operations. Therefore, after upgrading, perform operations as the root user.

Also, if the output destination of the performance database was changed before the upgrade, check the settings related to that directory's permissions. For details, see 4. Using Hybrid Store to manage data in the Agent Administration Guide.

Location to be corrected

3. Installing or upgrading the Tuning Manager server

Installing on a Windows host

Hitachi Command Suite All-in-One Installer

Existing content

If you are installing multiple Hitachi Command Suite products you can use the Hitachi Command Suite's all-in-one installer to batch install the following products:

·       Hitachi Command Suite (Device Manager, Tiered Storage Manager, and Replication Manager)

·       Tuning Manager server

·       Compute Systems Manager

·       Storage Navigator Modular 2

·       Automation Director1

1)    Installation in a cluster configuration is not supported.

Revised content

If you are installing multiple Hitachi Command Suite products you can use the Hitachi Command Suite's all-in-one installer to batch install the following products:

·       Hitachi Command Suite (Device Manager, Tiered Storage Manager, and Replication Manager)

·       Tuning Manager server

·       Compute Systems Manager

·       Automation Director1

1)    Installation in a cluster configuration is not supported.

Location to be corrected

3. Installing or upgrading the Tuning Manager server

Installing on a Windows host

Setting up Windows firewall

Adding the Tuning Manager server to the exceptions list

Existing content

To add the Tuning Manager server to the exceptions list from the GUI

1)    Choose Control Panel, and then Windows Firewall.

2)    Choose Change settings (for Windows Server 2008).

3)    Click the Exceptions tab, and then click the Add Program button. In the displayed dialog box, specify the following:
Common-Component-installation-folder\Base64\CC\web\bin\cjstartweb.exe

4)    To apply the settings, restart the services of Hitachi Command Suite products by executing the following commands:
Common-Component-installation-folder\bin\hcmds64srv /stop
Common-Component-installation-folder\bin\hcmds64srv /start

To check that the Tuning Manager server has been added to the exceptions list by using the GUI:

1)    Choose Control Panel, and then Windows Firewall.

2)    Choose Change settings (for Windows Server 2008).

3)    Click the Exceptions tab, and make sure that:

o   The Programs and Services list contains cjstartweb.exe.

o   The check box to the left of cjstartweb.exe is selected.

To add the Tuning Manager server to the exceptions list by using the command line

1)    Execute the following command to add the Tuning Manager server to the exceptions list:
netsh advfirewall firewall add allowedprogram program="Common-Component-installation-folder\Base64\CC\web\bin\cjstartweb.exe" name="HBase(cjstartweb)" mode=ENABLE

2)    To apply the settings, restart the services of Hitachi Command Suite products by executing the following commands:
Common-Component-installation-folder\bin\hcmds64srv /stop
Common-Component-installation-folder\bin\hcmds64srv /start

3)    To check that the Tuning Manager server has been added to the exceptions list by using a command, execute the following command:
netsh advfirewall firewall show all

Verify the following:

·       HBase(cjstartweb) is displayed.

·       The mode is ENABLE.

·       The path for cjstartweb.exe is correct.

To remove an entry from the exceptions list, execute the following command:

netsh advfirewall firewall delete allowedprogram program="Common-Component-installation-folder\Base64\CC\web\bin\cjstartweb.exe"

Revised content

To add the Tuning Manager server to the exceptions list from the GUI

1)    Choose Control Panel, and then Windows Firewall.

2)    Specify the following file as an allowed program:
Common-Component-installation-folder\uCPSB\CC\server\bin\cjstartsv.exe
Use one of the following methods to specify the file:

o   For Windows Server 2012
[Allow an app or feature through Windows Firewall] - [Allow apps to communicate through Windows Firewall] - [Allow another app... ] - [Add an app]

3)    To apply the settings, restart the services of Hitachi Command Suite products by executing the following commands:
Common-Component-installation-folder\bin\hcmds64srv /stop
Common-Component-installation-folder\bin\hcmds64srv /start

To check that the Tuning Manager server has been added to the exceptions list by using the GUI:

1)    Choose Control Panel, and then Windows Firewall.

2)    To apply the settings, restart the services of Hitachi Command Suite products by executing the following commands:

o   For Windows Server 2012
[Allow an app or feature through Windows Firewall] - [Allowed apps and features:]

3)    In the list of allowed programs, confirm the following:

o   cjstartsv is displayed.

o   The check box to the left of cjstartsv is selected.

To add the Tuning Manager server to the exceptions list by using the command line

1)    Execute the following command to add the Tuning Manager server to the exceptions list:
netsh advfirewall firewall add rule name="HBase(cjstartsv)" dir=in action=allow program="Common-Component-installation-folder\CC\server\bin\cjstartsv.exe

2)    To apply the settings, restart the services of Hitachi Command Suite products by executing the following commands:
Common-Component-installation-folder\bin\hcmds64srv /stop
Common-Component-installation-folder\bin\hcmds64srv /start

3)    To check that the Tuning Manager server has been added to the exceptions list by using a command, execute the following command:
netsh advfirewall firewall show rule name="HBase(cjstartsv)" verbose

Verify the following:

·       HBase(cjstartsv) is displayed.

·       The mode is ENABLE.

·       The path for cjstartsv.exe is correct.

To remove an entry from the exceptions list, execute the following command:

netsh advfirewall firewall delete rule name="HBase(cjstartsv)" dir=in program="Common-Component-installation-folder\uCPSB\CC\server\bin\cjstartsv.exe"

Location to be corrected

4. Preparing to install or upgrade agents

Reviewing the installation requirements (all agents)

Notes on using Oracle JDK 7

Deleted content

Notes on using Oracle JDK 7

If you are using Oracle JDK 7 and install an Agent of v8.2.1 or later, JDK becomes unavailable.

Location to be corrected

4. Preparing to install or upgrade agents

Reviewing the installation requirements (all agents)

Before an upgrade or overwrite installation

Before starting an upgrade or overwrite installation (for Agents that use Hybrid Store)

Added content

+ The following directory might be deleted during an upgrade installation. For this reason, if you created files in this directory, move the files to another location. If the settings reference a file in this directory (for example, htnm_httpsd.conf), edit the settings so that the relocated files are referenced.

In Windows:

    installation-folder\htnm\HBasePSB\hjdk\jdk

In UNIX:

    /opt/jp1pc/htnm/HBasePSB/hjdk/jdk

Location to be corrected

4 Preparing to install or upgrade agents

Reviewing the installation requirements (all agents)

Before an upgrade or overwrite installation

Before starting an upgrade or overwrite installation (for Agents that use Store databases)

Added content

+ The following directory might be deleted during an upgrade installation. For this reason, if you created files in this directory, move the files to another location. If the settings reference a file in this directory (for example, htnm_httpsd.conf), edit the settings so that the relocated files are referenced.

In Windows:

    installation-folder\htnm\HBasePSB\hjdk\jdk

In UNIX:

    /opt/jp1pc/htnm/HBasePSB/hjdk/jdk

Location to be corrected

4. Preparing to install or upgrade agents

Reviewing the installation requirements (all agents)

Before an upgrade or overwrite installation

Before starting an upgrade or overwrite installation (for Agents that use Hybrid Store)

Deleted content

When Agent for SAN Switch is upgraded from a version earlier than v8.5 to v8.5 or later, after the upgrade the JDK that is bundled with Agent for SAN Switch is assumed to be set. This happens whether or not there was a switch to Oracle JDK before the upgrade. If you want to use Oracle JDK, you need to switch to the Oracle JDK that supports Agent for SAN Switch.

For procedures on how to switch to the Oracle JDK, see Specifying an Oracle Java installation path (Windows and Linux) on page 8-26.

Location to be corrected

4. Preparing to install or upgrade agents

Reviewing the installation requirements (all agents)

Before an upgrade or overwrite installation

Before starting an upgrade or overwrite installation (for Agents that use Store databases)

Deleted content

When upgrading the version of Agent for NAS from version 8.4 or earlier to version 8.4.1 or later, if the OS is Windows Server 2008, Linux, or Windows Server 2012 and the JDK bundled with Agent for NAS has been switched to Oracle JDK before a version upgrade, the Java installation path setting in the agtn.properties file will be invalid after a version upgrade. Therefore, switch to Oracle JDK by using the htmchgjdk command after a version upgrade. See the description about the setup for using Oracle JDK in the chapter about setting up Agents to use Tuning Manager API in the Hitachi Command Suite Tuning Manager Agent Administration Guide.

Location to be corrected

4. Preparing to install or upgrade agents

Reviewing the installation requirements (all agents)

Before an upgrade or overwrite installation

Before starting an upgrade or overwrite installation (for Agents that use Store databases)

Deleted content

When upgrading the version of Agent for NAS from version 8.4 or earlier to version 8.4.1 or later, if the OS is Windows Server 2008, Linux, or Windows Server 2012 and the JDK bundled with Agent for NAS has been switched to Oracle JDK before a version upgrade, the Java installation path setting in the agtn.properties file will be invalid after a version upgrade. Therefore, switch to Oracle JDK by using the htmchgjdk command after a version upgrade. For details, see Switching to Oracle JDK (Windows and Linux) on page 8-46.

Location to be corrected

4. Preparing to install or upgrade agents

Reviewing agent-specific installation requirements

Agent for RAID

When monitoring Hitachi Virtual Storage Platform, VSP G1000, G1500, VSP F1500, VSP Gx00 models, VSP Fx00 models, Hitachi Unified Storage VM, or Universal Storage Platform V/VM series

Added content

Selecting a protocol for secure communication (SSL communications)

Perform this procedure only if Hybrid Store is used and performance data is to be collected by using a TCP/IP connection.

In a storage system where you can select which protocol to use for secure communications, be sure to specify a communication protocol supported by the Agent for RAID you are going to use.

If the Agent for RAID supports none of the specified communication protocols, performance data cannot be collected.

For details on communication protocols supported by Agent for RAID, see the description Important considerations in the Release Notes.

Location to be corrected

4. Preparing to install or upgrade agents

Reviewing agent-specific installation requirements

Agent for RAID

Creating a Storage Navigator user account (Hitachi Virtual Storage Platform, VSP G1000, G1500, VSP F1500, VSP Gx00 models, VSP Fx00 models, and Virtual Storage Platform Series) (optional)

Existing content

To collect performance data by using a TCP/IP connection, you need to use Storage Navigator to create a user account. One user account is required for each instance. Assign one of the following roles to the user account:

Revised content

To collect performance data by using a TCP/IP connection, you need to use Storage Navigator to create a user account. Create the user account as a dedicated Agent for RAID account. One user account is required for each instance. Assign one of the following roles to the user account:

Location to be corrected

4. Preparing to install or upgrade agents

Reviewing agent-specific installation requirements

Agent for RAID

Table 4-2 Settings to be specified in Performance Monitor

Existing content

Setting

Description

Sampling interval

Set the interval at which Performance Monitor collects performance data. If you use Performance Monitor to collect performance data, set "short range". The granularity set here becomes the granularity of data that can be collected by Agent for RAID.

Revised content

Setting

Description

Sampling interval

Set the interval at which Performance Monitor collects performance data. The granularity set here becomes the granularity of data that can be collected by Agent for RAID.

Location to be corrected

4. Preparing to install or upgrade agents

Reviewing pre-installation requirements for cluster systems

Requirements for using an agent in a cluster system

Shared disk:

Deleted content

·       Shared disks must be physically connected to each node via Fibre Channel or SCSI.

Tuning Manager series programs do not support as shared disks the use of network drives or disks replicated via a network.

Location to be corrected

7. Removing the Tuning Manager server

Removing the Tuning Manager server from a Windows host

Hitachi Comman Suite All-in-One Uninstaller

Existing content

If you want to remove multiple Hitachi Command Suite products you can use the Hitachi Command Suite's all-in-one uninstaller. The all-in-one uninstaller batch removes the following products:

·       Hitachi Command Suite (Device Manager, Tiered Storage Manager, and Replication Manager)

·       Tuning Manager server

·       Replication Manager

·       Compute Systems Manager

·       Storage Navigator Modular 2

·       Automation Director1

1)    Installation in a cluster configuration is not supported.

Revised content

If you want to remove multiple Hitachi Command Suite products you can use the Hitachi Command Suite's all-in-one uninstaller. The all-in-one uninstaller batch removes the following products:

·       Hitachi Command Suite (Device Manager, Tiered Storage Manager, and Replication Manager)

·       Tuning Manager server

·       Replication Manager

·       Compute Systems Manager

·       Automation Director1

1)    Installation in a cluster configuration is not supported.

Location to be corrected

8. Setting up the agents

Setting up Agent for RAID

Existing content

Table 8-1 Abbreviations used for storage systems

Full name

Abbreviation

Hitachi Virtual Storage Platform G200

VSP G200

VSP Gx00 models

Hitachi Virtual Storage Platform G400

VSP G400

Hitachi Virtual Storage Platform G600

VSP G600

Hitachi Virtual Storage Platform G800

VSP G800

Hitachi Virtual Storage Platform F400

VSP F400

VSP Fx00 models

Hitachi Virtual Storage Platform F600

VSP F600

Hitachi Virtual Storage Platform F800

VSP F800

Revised content

Table 8-1 Abbreviations used for storage systems

Full name

Abbreviation

Hitachi Virtual Storage Platform G200

VSP G200

VSP Gx00 models

Hitachi Virtual Storage Platform G350

VSP G350

Hitachi Virtual Storage Platform G370

VSP G370

Hitachi Virtual Storage Platform G400

VSP G400

Hitachi Virtual Storage Platform G600

VSP G600

Hitachi Virtual Storage Platform G700

VSP G700

Hitachi Virtual Storage Platform G800

VSP G800

Hitachi Virtual Storage Platform G900

VSP G900

Hitachi Virtual Storage Platform F350

VSP F350

VSP Fx00 models

Hitachi Virtual Storage Platform F370

VSP F370

Hitachi Virtual Storage Platform F400

VSP F400

Hitachi Virtual Storage Platform F600

VSP F600

Hitachi Virtual Storage Platform F700

VSP F700

Hitachi Virtual Storage Platform F800

VSP F800

Hitachi Virtual Storage Platform F900

VSP F900

Hitachi Virtual Storage Platform N400

VSP N400

VSP Nx00 models

Hitachi Virtual Storage Platform N600

VSP N600

Hitachi Virtual Storage Platform N800

VSP N800

Hitachi Virtual Storage Platform 5100

VSP 5100

VSP 5000 series

Hitachi Virtual Storage Platform 5500

VSP 5500

Hitachi Virtual Storage Platform 5100H

VSP 5100H

Hitachi Virtual Storage Platform 5500H

VSP 5500H

Location to be corrected

8. Setting up the agents

Setting up Agent for RAID

Switching to Oracle JDK (when Tuning Manager API is used)

Deleted content

Switching to Oracle JDK (when Tuning Manager API is used)

You can switch the JDK used by the Tuning Manager Agent REST API Component to Oracle JDK. For details about how to switch to Oracle JDK, see the description on the setup for using Oracle JDK in the chapter about setting up Agents to use Tuning Manager API in the Tuning Manager Agent Administration Guide.

Location to be corrected

8. Setting up the agents

Setting up Agent for RAID

Setting up an instance environment

Added content

Note:

You can connect only one Agent for RAID to a storage system. If you connect two or more Agent for RAID, data collection might fail, some data might be missing, or the load on the storage system might increase.

Location to be corrected

8. Setting up the agents

Setting up Agent for RAID

Setting up an instance environment

Existing content

Table 8-7 Instance information required to collect performance data using a TCP/IP connection (VSP Gx00 models, VSP Fx00 models, HUS VM, VSP G1000, G1500, VSP F1500, and Virtual Storage Platform series)

Item

Description

Details of the Storage Model

Specify the storage type. This item is required.

If 11 is specified:

-       Virtual Storage Platform series

If 12 is specified:

-       VSP G1000, G1500, or VSP F1500

If 21 is specified:

-       HUS VM

If 22 is specified:

-       VSP Gx00 models or VSP Fx00 models

Revised content

Table 8-7 Instance information required to collect performance data using a TCP/IP connection (VSP 5000 series, VSP Gx00 models, VSP Fx00 models, VSP Nx00 models, HUS VM, VSP G1000, G1500, VSP F1500, and Virtual Storage Platform series)

Item

Description

Details of the Storage Model

Specify the storage type. This item is required.

If 11 is specified:

-       Virtual Storage Platform series

If 12 is specified:

-       VSP G1000, G1500, or VSP F1500

If 13 is specified:

-       VSP 5000 series

If 21 is specified:

-       HUS VM

If 22 is specified:

-       VSP Gx00 models, VSP Fx00 models or VSP Nx00 models

Location to be corrected

8. Setting up the agents

Setting up Agent for RAID

Updating an instance environment

Table 8-12 Instance information that can be updated for Agent for RAID required to collect performance data using a TCP/IP connection

Existing content

Item

Description

Details of the Storage Model

Specify the storage type. This item is required.

If 11 is specified:

-       Virtual Storage Platform series

If 12 is specified:

-       VSP G1000, G1500, or VSP F1500

If 21 is specified:

-       HUS VM

If 22 is specified:

-       VSP Gx00 models or VSP Fx00 models

Revised content

Item

Description

Details of the Storage Model

Specify the storage type. This item is required.

If 11 is specified:

-       Virtual Storage Platform series

If 12 is specified:

-       VSP G1000, G1500, or VSP F1500

If 13 is specified:

-       VSP 5000 series

If 21 is specified:

-       HUS VM

If 22 is specified:

-       VSP Gx00 models, VSP Fx00 models or VSP Nx00 models

Location to be corrected

8. Setting up the agents

Setting up Agent for SAN Switch

Specifying an Oracle Java installation path (Windows and Linux)

Deleted content

Specifying an Oracle Java installation path (Windows and Linux)

By default, the Windows and Linux versions of Agent for SAN Switch use the Java version that is bundled with the Agent for SAN Switch. No additional property settings are required.

Location to be corrected

8. Setting up the agents

Setting up Agent for SAN Switch

Changing the connection destination from Cisco Seed Switch to DCNM-SAN SMI-S Agent

Existing content

5. Execute the jpcconf inst unsetup command (jpcinsunsetup) for the instance that connects to Cisco Seed Switch to delete the instance. For details on the jpcconf inst unsetup command (jpcinsunsetup), see the Tuning Manager CLI Reference Guide.

6. On the Tuning Manager server host, execute the jpctool service delete command (jpcctrl delete) to delete the information about the instance that connects to Cisco Seed Switch. For details on the jpctool service delete command (jpcctrl delete), see the Tuning Manager CLI Reference Guide.

Revised content

5. Execute the jpcinsunsetup command for the instance that connects to Cisco Seed Switch to delete the instance. For details on the jpcinsunsetup command, see the Tuning Manager CLI Reference Guide.

6. On the Tuning Manager server host, execute the jpcctrl delete command to delete the information about the instance that connects to Cisco Seed Switch. For details on the jpcctrl delete command, see the Tuning Manager CLI Reference Guide.

Location to be corrected

8. Setting up the agents

Setting up Agent for NAS

Switching to Oracle JDK (Windows and Linux)

Deleted content

Switching to Oracle JDK (Windows and Linux)

Use the htmchgjdk command to switch to Oracle JDK. See the description about the setup for using Oracle JDK in the chapter about setting up Agents to use Tuning Manager API in the Hitachi Command Suite Tuning Manager Agent Administration Guide.

Location to be corrected

8. Setting up the agents

Operating agents in cluster systems

Setting up agents in cluster systems

Existing content

Manually setting the start of the services that are registered to the cluster

The start and stop of services registered to the cluster are controlled from the cluster. Therefore, set the Type of startup of the services to Manual so that they are not started when the OS starts. Note that, if you use the jpcconf ha setup (jpchasetup create) command to set up a service, the startup type of the service is set to Manual

Revised content

Manually setting the start of the services that are registered to the cluster

The start and stop of services registered to the cluster are controlled from the cluster. Therefore, set the Type of startup of the services to Manual so that they are not started when the OS starts. Note that, if you use the jpchasetup create command to set up a service, the startup type of the service is set to Manual

Location to be corrected

8. Setting up the agents

Operating agents in cluster systems

Setting up agents in cluster systems

Existing content

Creating scripts for registering the Agents services with Red Hat Hat High Availability

5. To add an Agent service, add the start commands for that Agent service as per the following setting.

exec_cmd "/opt/jp1pc/tools/jpcstart act lhost=$LHOST"

exec_cmd "/opt/jp1pc/tools/jpcstart agtd lhost=$LHOST inst=$RAID_INST_NAME1"

exec_cmd "/opt/jp1pc/tools/jpcstart agtd lhost=$LHOST inst=$RAID_INST_NAMEn"

exec_cmd "/opt/jp1pc/htnm/bin/htmsrv start -webservice"(see Note)

6. To add an Agent service, add the stop commands for that Agent service as per the following setting.

exec_cmd "/opt/jp1pc/htnm/bin/htmsrv stop -webservice" (see Note)

exec_cmd "/opt/jp1pc/tools/jpcstop agtd lhost=$LHOST inst=$AGENT_INST_NAMEn"

...

exec_cmd "/opt/jp1pc/tools/jpcstop agtd lhost=$LHOST inst=$AGENT_INST_NAME1"

exec_cmd "/opt/jp1pc/tools/jpcstop act lhost=$LHOST"

Revised content

Creating scripts for registering the Agents services with Red Hat High Availability

5. To add an Agent service, add the start commands for that Agent service as per the following setting.

exec_cmd "/opt/jp1pc/htnm/bin/htmsrv start -webservice"(see Note)

exec_cmd "/opt/jp1pc/tools/jpcstart act lhost=$LHOST"

exec_cmd "/opt/jp1pc/tools/jpcstart agtd lhost=$LHOST inst=$RAID_INST_NAME1"

...

exec_cmd "/opt/jp1pc/tools/jpcstart agtd lhost=$LHOST inst=$RAID_INST_NAMEn"

6. To add an Agent service, add the stop commands for that Agent service as per the following setting.

exec_cmd "/opt/jp1pc/tools/jpcstop agtd lhost=$LHOST inst=$RAID_INST_NAMEn"

...

exec_cmd "/opt/jp1pc/tools/jpcstop agtd lhost=$LHOST inst=$RAID_INST_NAME1"

exec_cmd "/opt/jp1pc/tools/jpcstop act lhost=$LHOST"

exec_cmd "/opt/jp1pc/htnm/bin/htmsrv stop -webservice" (see Note)

Location to be corrected

10. Tuning Manager security

Configuring an SSL server (Tuning Manager Agent)

Creating a secret key and a certificate signing request for Tuning Manager Agent host

Existing content

A certificate signing request and self-signed certificate are created with a private key size of 2,048 bits and the signature algorithm SHA256withRSA. The certificate signing request is created in PEM format. Although you can use this command to create a self-signed certificate, we recommend that you use a self-signed certificate only to test encrypted communications.

Revised content

The htmssltool command creates two types of private keys: certificate signing requests, and self-signed certificates supporting RSA ciphers and elliptic curve ciphers (ECC). The certificate signing request is created in PEM format. Although you can use this command to create a self-signed certificate, we recommend that you use a self-signed certificate only to test encrypted communications.

Location to be corrected

10. Tuning Manager security

Enabling SSL (Tuning Manager Agent)

Settings required for enabling SSL

Existing content

Set the following:

ServerName HostA

#Listen 127.0.0.1:24221

#Listen [::]:24221

#SSLDisable

Listen 24222

Listen [::]:24222

SSLEnable

SSLProtocol TLSv12

SSLRequiredCiphers AES256-SHA256:AES128-SHA256

SSLRequireSSL

SSLCertificateFile "C:/Program Files (x86)/HiCommand/TuningManager/jp1pc/htnm/HBasePSB/httpsd/conf/ssl/server/httpsd.pem"

SSLCertificateKeyFile "C:/Program Files (x86)/HiCommand/TuningManager/jp1pc/htnm/HBasePSB/httpsd/conf/ssl/server/httpsdkey.pem"

SSLCACertificateFile "C:/Program Files (x86)/HiCommand/TuningManager/jp1pc/htnm/HBasePSB/httpsd/conf/ssl/cacert/anycert.pem"

HWSLogSSLVerbose On

·       Enter hash marks (#) as shown in the examples, and remove the hash marks (#) from other lines.

·       For the SSLCertificateFile directive, specify the absolute path to the server certificate for Tuning Manager Agent host. For the server certificate, both a signed certificate issued by the certificate authority and a self-signed certificate exist.

·       For the SSLCertificateKeyFile directive, specify the absolute path to the private key file for Tuning Manager Agent host. Do not specify a symbolic link or a junction for the path.

Revised content

Set the following:

ServerName HostA

#Listen 127.0.0.1:24221

#Listen [::]:24221

#SSLEngine Off

Listen 24222

#Listen [::]:24222

SSLEngine On

SSLProtocol TLSv1.2

SSLCipherSuite ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256

SSLCertificateFile "C:/Program Files (x86)/HiCommand/TuningManager/jp1pc/htnm/HBasePSB/httpsd/conf/ssl/server/httpsd.pem"

SSLCertificateKeyFile "C:/Program Files (x86)/HiCommand/TuningManager/jp1pc/htnm/HBasePSB/httpsd/conf/ssl/server/httpsdkey.pem"

SSLCertificateFile "C:/Program Files (x86)/HiCommand/TuningManager/jp1pc/htnm/HBasePSB/httpsd/conf/ssl/server/ecc-httpsd.pem"

SSLCertificateKeyFile "C:/Program Files (x86)/HiCommand/TuningManager/jp1pc/htnm/HBasePSB/httpsd/conf/ssl/server/ecc-httpsdkey.pem"

SSLCACertificateFile "C:/Program Files (x86)/HiCommand/TuningManager/jp1pc/htnm/HBasePSB/httpsd/conf/ssl/cacert/anycert.pem"

HWSLogSSLVerbose On

·       Enter hash marks (#) as shown in the examples, and remove the hash marks (#) from other lines.

·       If you use the RSA cipher only, you do not need to remove the hash mark (#) at the beginning of the lines for the SSLECCCertificateKeyFile directive and the SSLCertificateFile directive. If you use the elliptic curve ciphers (ECC) cipher only, you do not need to remove the hash mark (#) at the beginning of the lines for the SSLCertificateKeyFile directive and the SSLCertificateFile directive.

·       If you connect multiple Hitachi Tuning Manager - Agents hosts to the same Tuning Manager server, use the same signature algorithm.

·       For the SSLCertificateFile directive, specify the absolute path to the server certificate for Tuning Manager Agent host of RSA ciphers. For the server certificate, both a signed certificate issued by the certificate authority and a self-signed certificate exist.

·       For the SSLCertificateKeyFile directive, specify the absolute path to the private key file for Tuning Manager Agent host of RSA ciphers. Do not specify a symbolic link or a junction for the path.

·       For the SSLCertificateFile directive, specify the absolute path to the server certificate for Tuning Manager Agent host of elliptic curve ciphers (ECC). For the server certificate, both a signed certificate issued by the certificate authority and a self-signed certificate exist. This setting is unnecessary if you use the RSA cipher only.

·       For the SSLCertificateKeyFile directive, specify the absolute path to the private key file for Tuning Manager Agent host of elliptic curve ciphers (ECC). Do not specify a symbolic link or a junction for the path. This setting is unnecessary if you use the RSA cipher only.

Location to be corrected

10. Tuning Manager security

Enabling SSL (Tuning Manager Agent)

Settings required for disabling SSL

Existing content

To disable SSL, enter hash marks (#) as shown in the examples, and remove the hash marks (#) from other lines.

ServerName HostA

Listen 24221

Listen [::]:24221

SSLDisable

#Listen 24222

#Listen [::]:24222

#SSLEnable

#SSLProtocol TLSv12

#SSLRequiredCiphers AES256-SHA256:AES128-SHA256

#SSLRequireSSL

#SSLCertificateFile "C:/Program Files (x86)/HiCommand/TuningManager/jp1pc/htnm/HBasePSB/httpsd/conf/ssl/server/httpsd.pem"

#SSLCertificateKeyFile "C:/Program Files (x86)/HiCommand/TuningManager/jp1pc/htnm/HBasePSB/httpsd/conf/ssl/server/httpsdkey.pem"

#SSLCACertificateFile "C:/Program Files (x86)/HiCommand/TuningManager/jp1pc/htnm/HBasePSB/httpsd/conf/ssl/cacert/anycert.pem"

#HWSLogSSLVerbose On

Revised content

To disable SSL, enter hash marks (#) as shown in the examples, and remove the hash marks (#) from other lines.

ServerName HostA

Listen 24221

#Listen [::]:24221

SSLEngine Off

#Listen 24222

#Listen [::]:24222

#SSLEngine On

#SSLProtocol TLSv1.2

#SSLCipherSuite ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256

#SSLCertificateFile "C:/Program Files (x86)/HiCommand/TuningManager/jp1pc/htnm/HBasePSB/httpsd/conf/ssl/server/httpsd.pem"

#SSLCertificateKeyFile "C:/Program Files (x86)/HiCommand/TuningManager/jp1pc/htnm/HBasePSB/httpsd/conf/ssl/server/httpsdkey.pem"

#SSLCertificateFile "C:/Program Files (x86)/HiCommand/TuningManager/jp1pc/htnm/HBasePSB/httpsd/conf/ssl/server/ecc-httpsd.pem"

#SSLCertificateKeyFile "C:/Program Files (x86)/HiCommand/TuningManager/jp1pc/htnm/HBasePSB/httpsd/conf/ssl/server/ecc-httpsdkey.pem"

#SSLCACertificateFile "C:/Program Files (x86)/HiCommand/TuningManager/jp1pc/htnm/HBasePSB/httpsd/conf/ssl/cacert/anycert.pem"

#HWSLogSSLVerbose On

Location to be corrected

10. Tuning Manager security

Enabling SSL (Tuning Manager Agent)

Existing content

Importing the certificate into the truststore (Tuning Manager server)

Use a secure method to obtain the server certificate that was created on the Agent host, and then import the server certificate into the trust store (jssecacerts) of the Tuning Manager server.

The trust store on the host on which the Tuning Manager server is installed is in the following location:

Revised content

Importing the certificate into the truststore (Tuning Managerserver and Device Manager)

Use a secure method to obtain the server certificate that was created on the Agent host, and then import the server certificate into the trust store(jssecacerts) of the Tuning Manager server and Device Manager.

The certificate must be imported into the truststore of the Device Manager host if both of the following conditions are met. If one or both the conditions are not met, import the certificate into the truststore of only the Tuning Manager server host.

- The alert function is used.

- The Tuning Manager server and Device Manager are installed on different hosts.

The trust store on the host on which the Tuning Manager server is installed is in the following location:

Location to be corrected

10. Tuning Manager security

Enabling SSL (Tuning Manager Agent)

Existing content

Checking the contents of a certificate (Tuning Manager agent)

Revised content

Cipher suites Settings (Tuning Manager server and Device Manager)

To use elliptic curve ciphers (ECC), the following settings must be configured. The default is RSA ciphers.

- To use elliptic curve ciphers (ECC) for communication between Hitachi Tuning Manager - Agent and the Tuning Manager server:

    For the property rest.discovery.agent.use.cipher.type in the user properties file (user.properties) for the Tuning Manager server, specify the encryption method to be used.

    For details about the user properties file (user.properties), see the Tuning Manager Server Administration Guide.

- To use elliptic curve ciphers (ECC) for communication between Hitachi Tuning Manager - Agent and Device Manager (only when the alert function is used):

    For the property htnm.agent.use.cipher.type in the tuningmanager.properties file, specify the encryption method to be used.

    For details about the tuningmanager.properties file, see the Hitachi Command Suite Administrator Guide.

Checking the contents of a certificate (Tuning Manager agent)

Location to be corrected

10. Tuning Manager security

Enabling SSL (Tuning Manager Agent)

Existing content

Checking the contents of a certificate (Tuning Manager Server)

Revised content

Checking the contents of a certificate (Tuning Manager Server and Device Manager)

Location to be corrected

10. Tuning Manager security

Enabling SSL (Tuning Manager Agent)

Existing content

Deleting a certificate (Tuning Manager Server)

Revised content

Deleting a certificate (Tuning Manager Server and Device Manager)

Location to be corrected

A. Upper limit and recommended values

Tuning Manager server system configuration

Number of monitored resources

Table A-1 Resources that can be monitored from the Tuning Manager server

Existing content

Category

Resource

Storage systems

Processors:

·       This is a resource number of channel processors and disk processors if the monitored storage system is a or Universal Storage Platform V/VM series.

·       This is a resource number of processors if the monitored storage system is Hitachi HUS100/AMS2000/AMS/WMS/SMS series.

·       This is a resource number of MP Blade (Microprocessor Blade) or MPU (Microprocessor Unit) if the monitored resource is a Virtual Storage Platform or Hitachi Unified Storage VM, or VSP Gx00 models or VSP Fx00 models..

Revised content

Category

Resource

Storage systems

Processors:

·       This is a resource number of channel processors and disk processors if the monitored storage system is a Universal Storage Platform V/VM series.

·       This is a resource number of processors if the monitored storage system is Hitachi HUS100/AMS2000/AMS/WMS/SMS series.

·       This is a resource number of MP Blade (Microprocessor Blade) or MPU (Microprocessor Unit) if the monitored resource is a Virtual Storage Platform, HUS VM, VSP 5000 series, VSP G1000, G1500, VSP F1500, VSP Gx00 models, VSP Fx00 models or VSP Nx00 models.

Location to be corrected

D. Items to check when collecting performance data by using a TCP/IP connection

Prerequisites for collecting performance data that can be collected by using a TCP/IP connection

Existing content

To collect the performance data that can be collected by using a TCP/IP connection, the following prerequisites must be met:

·       The target whose performance data is to be collected is included in the following storage systems:

o   Virtual Storage Platform series

o   VSP G1000

o   VSP G1500

o   VSP F1500

o   HUS VM

o   VSP Gx00 models

o   VSP Fx00 models

Revised content

To collect the performance data that can be collected by using a TCP/IP connection, the following prerequisites must be met:

·       The target whose performance data is to be collected is included in the following storage systems:

o   Virtual Storage Platform series

o   VSP 5000 series

o   VSP G1000

o   VSP G1500

o   VSP F1500

o   HUS VM

o   VSP Gx00 models

o   VSP Fx00 models

o   VSP Nx00 models

Location to be corrected

D. Items to check when collecting performance data by using a TCP/IP connection

Notes when collecting performance data by using a TCP/IP connection

Added content

Notes on the SVP for which the fixed time SVP reboot setting, or the recovery SVP reboot setting is enabled

When the fixed time SVP reboot setting or the recovery SVP reboot setting is enabled, performance data cannot be collected while the SVP is rebooting.

Location to be corrected

D. Items to check when collecting performance data by using a TCP/IP connection

Correspondence between the records when the command device is used and the records when a TCP/IP connection is used

Table D-2 Correspondence between the records when the command device is used and the records when a TCP/IP connection is used

Added content

Perforrmance data type

Record ID

When the command device is used

When a TCP/IP connection is used

This request obtains the performance data indicating the ratio of the total saving effect (excluding system data) achieved by the accelerated compression, capacity saving, snapshot, and provisioning.

·       PD_SEFF

·       PD_PEFF

-

Tuning Manager Server Administration Guide

Contents of corrections of the Hitachi Command Suite Tuning Manager Server Administration Guide

Location to be corrected

1. Overview

Logging in to a Tuning Manager server as an Administrator

Existing content

Note: Adobe Flash Player 10.1 or later is required to be installed in the client in which the browser is used. However, if Tuning Manager server is installed in a host that is different from a host Device Manager is installed in, and only Tuning Manager server is operated, Adobe Flash Player is not required.

The design of the login screen depends on whether Tuning Manager server and Device Manager are installed in the same host or not.

Revised content

Note: The design of the login screen depends on whether Tuning Manager server and Device Manager are installed in the same host or not.

Location to be corrected

1. Overview

Setting up the user property file

Properties for the user.properties file

Existing content

Table 1-5 Properties for the user.properties file

Property

Description

Specifiable values

Default value

rpt.flashmode

Specify whether the charts should be displayed in flash mode or HTML mode.

Values are not casesensitive.

true: The charts are displayed in flash mode.

false: The charts are displayed in HTML mode.

false

Revised content

Table 1-5 Properties for the user.properties file

Property

Description

Specifiable values

Default value

rpt.flashmode

Specify whether the charts should be displayed in flash mode or HTML mode.

If you are using Device Manager GUI on Adobe AIR desktop application, specify false.

Values are not casesensitive.

true: The charts are displayed in flash mode.

false: The charts are displayed in HTML mode.

false

Location to be corrected

1. Overview

Setting up the user property file

Properties for the user.properties file

Added content

Table 1-5 Properties for the user.properties file

Property

Description

Specifiable values

Default value

rest.discovery.agent.use.cipher.type

Specify the encryption method to be used to access a Hitachi Tuning Manager - Agent REST API component.

The characters are not case sensitive.

SUITEB128: Specify this value when using elliptic curve ciphers (ECC).

SUITEB192: Specify this value when using elliptic curve ciphers (ECC).

RSA: Specify this value when using RSA ciphers.

RSA

Location to be corrected

1. Overview

Added content

Restricting anonymous RMI access to Tuning Manager server

By edit the java.policy file, you can restrict host(server) to access Tuning Manager server with RMI protocol. It is available to prevent malicious attacks.

Following example shows the setting when both Tuning Manager server and Device Manager are installed on a same host.

To restrict RMI communication within the host:

1)    Stop the Tuning Manager server services.
For details on how to stop the Tuning Manager server services, see Stopping services in the manual Hitachi Command Suite Tuning Manager Server Administration Guide.

2)    Open the java.policy file with a text editor.
The java.policy file is located in the following directory.

o   In Windows:
Tuning-Manager-server-installation-folder\jp1pc\mgr\viewsrv\java.policy

o   In Linux:
Tuning-Manager-server-installation-directory/jp1pc/mgr/viewsrv/java.policy

3)    Replace the following contents.

----------------------------------------------------

grant {

permission java.io.FilePermission "<<ALL FILES>>", "read,write,execute,delete";

permission java.net.SocketPermission "localhost", "accept,connect,resolve,listen";

permission java.util.PropertyPermission "*", "read,write";

permission java.lang.RuntimePermission "*";

};

----------------------------------------------------

4)    Start the Tuning Manager server services.
For details on how to start the Tuning Manager server services, see Starting services in the manual Hitachi Command Suite Tuning Manager Server Administration Guide.

5)    Set localhost to the ownHost parameter in config.xml file and configforclient.xml file of Device Manager.
For details on the config.xml file and the configforclient.xml file, see the Hitachi Command Suite Administrator Guide.

When Tuning Manager server and Device Manager are installed on different hosts

To restrict hosts that can communicate with Tuning Manager server using RMI:

1)    Stop the Tuning Manager server services.
For details on how to stop the Tuning Manager server services, see Stopping services in the manual Hitachi Command Suite Tuning Manager Server Administration Guide.

2)    Open the java.policy file with a text editor.
The java.policy file is located in the following directory.

o   In Windows:
Tuning-Manager-server-installation-folder\jp1pc\mgr\viewsrv\java.policy

o   In Linux:
Tuning-Manager-server-installation-directory/jp1pc/mgr/viewsrv/java.policy

3)    Replace the following contents.

----------------------------------------------------

grant {

permission java.io.FilePermission "<<ALL FILES>>", "read,write,execute,delete";

permission java.net.SocketPermission "localhost", "accept,connect,resolve,listen";

permission java.net.SocketPermission "Device-Manager-IP-address-or-host-name#1", "accept,connect,resolve,listen";

permission java.net.SocketPermission "Tuning-Manager-IP-address-or-host-name#2", "accept,connect,resolve,listen";

permission java.util.PropertyPermission "*", "read,write";

permission java.lang.RuntimePermission "*";

};

----------------------------------------------------

#1 When multiple NICs are installed on the Device Manager and to specify an IP address instead of a host name, list all IP addresses that are allowed to communicate with Tuning Manager server in an individual line for each IP address.

Only IPv4 address is specifiable. For IPv6 environment, specify a host name instead.

#2 When multiple NICs are installed on the Tuning Manager and to specify an IP address instead of a host name, list all IP addresses that are allowed to communicate with Device Manager in an individual line for each IP address.

Only IPv4 address is specifiable. For IPv6 environment, specify a host name instead.

4)    Start the Tuning Manager server services.
For details on how to start the Tuning Manager server services, see Starting services in the manual Hitachi Command Suite Tuning Manager Server Administration Guide.

Location to be corrected

3. Managing the Tuning Manager server database

Restoring the database

Existing content

+ Before restoring the database, be sure to confirm that the following are the same in the backup source Tuning Manager server host and the restore destination Tuning Manager server host. If the following are not the same, the database cannot be restored.

- Types, versions, and revisions of the installed Hitachi Command Suite products

- Installation location for each Hitachi Command Suite product, Common Component, each Hitachi Command Suite product database, and Common Component database

- The IP address and host name of the machines

Revised content

+ Before restoring the database, be sure to confirm that the following are the same in the backup source Tuning Manager server host and the restore destination Tuning Manager server host. If the following are not the same, the database cannot be restored.

- Types, versions, and revisions of the installed Hitachi Command Suite products

- Installation location for each Hitachi Command Suite product, Common Component, each Hitachi Command Suite product database, and Common Component database

- Database capacity of the Tuning Manager server

- The IP address and host name of the machines

Location to be corrected

6. Specifying settings for data acquisition from Agents and Device Manager

Monitoring virtualization environments

Existing content

Notes

Because the Tuning Manager server does not support the analysis of virtualization environments that use VMware VVols, if you perform the operational procedure described in this section, some items will not be displayed in the Main Console. To analyze a virtualization environment that uses a VMware VVol, use the Analytics tab of Hitachi Command Suite to check the status.

For details about the display restrictions in the Tuning Manager server, see "Appendix A: Restrictions on the Tuning Manager series" in the Hitachi Command Suite Tuning Manager User Guide. For details about the Analytics tab of Hitachi Command Suite, see the Hitachi Command Suite User Guide.

Revised content

Notes

Because the Tuning Manager server does not support the analysis of virtualization environments that use VMware VVols, if you perform the operational procedure described in this section, some items will not be displayed in the Main Console.

For details about the display restrictions in the Tuning Manager server, see "Appendix A: Restrictions on the Tuning Manager series" in the Hitachi Command Suite Tuning Manager User Guide.

Location to be corrected

5. Configuring connection and initial settings

Configuring initial settings for Performance Reporter

Table 5-1 Initialization settings files (config.xml)

Existing content

Item

Description

service-agent-collector-node

Define a node to be added to the information tree displayed by the property distribution function of an agent. Use this tag to define the nodes for the Agent Collector service.

Specify the entries in the following format:

<param name="node-name" value="true" />

By default the following nodes are defined:

·       Detail Records5

·       Log Records5

·       Interval Records5

·       API Data Management6

·       DB Data Management7

Note 7:

This node name is added to the information tree of the agent that uses the Hybrid Store database.

Revised content

Item

Description

service-agent-collector-node

Define a node to be added to the information tree displayed by the property distribution function of an agent. Use this tag to define the nodes for the Agent Collector service.

Specify the entries in the following format:

<param name="node-name" value="true" />

By default the following nodes are defined:

·       Detail Records5

·       Log Records5

·       Interval Records5

·       API Data Management6

When you add a DB Data Management node to an information tree during operation in the Hybrid Store, edit the initial settings file to add the following setting:

<param name="DB Data Management" value="true" />

Location to be corrected

5. Configuring connection and initial settings

Deleted content

Overview of Oracle Java support

Location to be corrected

7. Error handling procedures

Performance Reporter log settings

Table 7-10 Log initialization settings

Existing content

Setting

Description

Value range

Default

Size

Specifies the size of one log file (in megabytes).1

1-100

10

Revised content

Setting

Description

Value range

Default

Size

Specifies the size of one log file (in megabytes).1

1-100

4

Location to be corrected

7. Error handling procedures

Collecting maintenance information

Information required to determine the circumstances in which a problem has occurred

Windows

Deleted content

If you are using Oracle JDK, DeviceManagerWebService.log file is output.

Location to be corrected

7. Error handling procedures

Collecting maintenance information

Information required to determine the circumstances in which a problem has occurred

Windows

Deleted content

If you are using Oracle JDK, TuningManager.log, PerformanceReporter.log, and TuningManagerRESTService.log files are created each time the service is restarted. Therefore, it is recommended that you rename these files before the service starts.

Location to be corrected

7. Error handling procedures

Collecting maintenance information

Information required to determine the circumstances in which a problem has occurred

Linux

Deleted content

If you are using Oracle JDK, DeviceManagerWebService.log file is output.

Location to be corrected

7. Error handling procedures

Collecting maintenance information

Information required to determine the circumstances in which a problem has occurred

Linux

Deleted content

If you are using Oracle JDK, TuningManager.log, PerformanceReporter.log, and TuningManagerRESTService.log files are output.

Location to be corrected

8. Working with Common Component

Managing ports used by Common Component

Table 8-3 Ports used by Common Component

Existing content

Default port number

Purpose

24234

AJP port of HCS TuningManager REST Application Service

24235

AJP port of HiCommand Suite TuningManager

24239

AJP port of HiCommand Performance Reporter

Revised content

Default port number

Purpose

24234

NIO HTTP port of HCS TuningManager REST Application Service

24235

NIO HTTP port of HiCommand Suite TuningManager

24239

NIO HTTP port of HiCommand Performance Reporter

Location to be corrected

8. Working with Common Component

Managing ports used by Common Component

Changing a Common Component port in Windows

Table 8-4 Changing Common Component ports (Windows)

Existing content

Port

Procedure for changing the port

22035

Port number that HBase 64 Storage Mgmt SSO Service uses to communicate with Web Server

Change the values of the following properties. Make sure that you specify the same value for all these properties:

- The worker.HBase64StgMgmtSSOService.port property in the Common-Component-installationfolder\uCPSB\CC\web\redirector\workers.properties file

- The webserver.connector.ajp13.port property in the Common-Component-installationfolder\uCPSB\CC\server\usrconf\ejb\HBase64StgMgmtSSOService\usrconf.properties file

24234

AJP port of HCS TuningManager REST Application Service

Change the value of the following property:

- The worker.TuningManagerRESTService.port property in Common-Component-installationfolder\uCPSB\CC\web\redirector\workers.properties

- The webserver.connector.ajp13.port property in Common-Component-installationfolder\uCPSB\CC\server\usrconf\ejb\TuningManagerRESTService\usrconf.properties

24235

AJP port of HiCommand Suite Tuning Manager

The same port number should be set for the following properties:

- The worker.TuningManager.port property in Common-Component-installationfolder\uCPSB\CC\web\redirector\workers.properties

- The webserver.connector.ajp13.port property in Common-Component-installationfolder\uCPSB\CC\server\usrconf\ejb\TuningManager\usrconf.properties

24239

AJP port of HiCommand Performance Reporter

The same port number should be set for the following properties:

- The worker.PerformanceReporter.port property in the Common-Component-installationfolder\uCPSB\CC\web\redirector\workers.properties

- The webserver.connector.ajp13.port property in the Common-Component-installationfolder\uCPSB\CC\server\usrconf\ejb\PerformanceReporter\usrconf.properties

Existing content

Port

Procedure for changing the port

22035

Port number that HBase 64 Storage Mgmt SSO Service uses to communicate with Web Server

Change the values of the following properties. Make sure that you specify the same value for all these properties:

- The worker.HBase64StgMgmtSSOService.port property in the Common-Component-installationfolder\uCPSB11\CC\web\redirector\workers.properties file

- The webserver.connector.nio_http.port property in the Common-Component-installationfolder\uCPSB11\CC\server\usrconf\ejb\HBase64StgMgmtSSOService\usrconf.properties file

24234

NIO HTTP port of HCS TuningManager REST Application Service

Change the value of the following property:

- The worker.TuningManagerRESTService.port property in Common-Component-installationfolder\uCPSB11\CC\web\redirector\workers.properties

- The webserver.connector.nio_http.port property in Common-Component-installationfolder\uCPSB11\CC\server\usrconf\ejb\TuningManagerRESTService\usrconf.properties

24235

NIO HTTP port of HiCommand Suite Tuning Manager

The same port number should be set for the following properties:

- The worker.TuningManager.port property in Common-Component-installationfolder\uCPSB11\CC\web\redirector\workers.properties

- The webserver.connector.nio_http.port property in Common-Component-installationfolder\uCPSB11\CC\server\usrconf\ejb\TuningManager\usrconf.properties

24239

NIO HTTP port of HiCommand Performance Reporter

The same port number should be set for the following properties:

- The worker.PerformanceReporter.port property in the Common-Component-installationfolder\uCPSB11\CC\web\redirector\workers.properties

- The webserver.connector.nio_http.port property in the Common-Component-installationfolder\uCPSB11\CC\server\usrconf\ejb\PerformanceReporter\usrconf.properties

Location to be corrected

8. Working with Common Component

Managing ports used by Common Component

Changing a Common Component port in Linux

Table 8-5 Changing Common Component ports (Linux)

Existing content

Port

Procedure for changing the port

22035

Port number that HBase 64 Storage Mgmt SSO Service uses to communicate with Web Server

Change the values of the following properties. Make sure that you specify the same value for all these properties:

- The worker.HBase64StgMgmtSSOService.port property in the Common-Component-installation-directory/uCPSB/CC/web/redirector/workers.properties file

- The webserver.connector.ajp13.port property in the Common-Component-installation-directory/uCPSB/CC/server/usrconf/ejb/HBase64StgMgmtSSOService/usrconf.properties file

24234

AJP port of HCS TuningManager REST Application Service

Change the value of the following property:

- The worker.TuningManagerRESTService.port property in Common-Component-installation-directory/uCPSB/CC/web/redirector/workers.properties

- The webserver.connector.ajp13.port property in Common-Component-installation-directory/uCPSB/CC/server/usrconf/ejb/TuningManagerRESTService/usrconf.properties

24235

AJP port of HiCommand Suite Tuning Manager

The same port number should be set for the following properties:

- The worker.TuningManager.port property in Common-Component-installation-directory/uCPSB/CC/web/redirector/workers.properties

- The webserver.connector.ajp13.port property in Common-Component-installation-directory/uCPSB/CC/server/usrconf/ejb/TuningManager/usrconf.properties

24239

AJP port of HiCommand Performance Reporter

The same port number should be set for the following properties:

- The worker.PerformanceReporter.port property in the Common-Component-installation-directory/uCPSB/CC/web/redirector/workers.properties

- The webserver.connector.ajp13.port property in the Common-Component-installation-directory/uCPSB/CC/server/usrconf/ejb/PerformanceReporter/usrconf.properties

Existing content

Port

Procedure for changing the port

22035

Port number that HBase 64 Storage Mgmt SSO Service uses to communicate with Web Server

Change the values of the following properties. Make sure that you specify the same value for all these properties:

- The worker.HBase64StgMgmtSSOService.port property in the Common-Component-installation-directory/uCPSB11/CC/web/redirector/workers.properties file

- The webserver.connector.nio_http.port property in the Common-Component-installation-directory/uCPSB11/CC/server/usrconf/ejb/HBase64StgMgmtSSOService/usrconf.properties file

24234

NIO HTTP port of HCS TuningManager REST Application Service

Change the value of the following property:

- The worker.TuningManagerRESTService.port property in Common-Component-installation-directory/uCPSB11/CC/web/redirector/workers.properties

- The webserver.connector.nio_http.port property in Common-Component-installation-directory/uCPSB11/CC/server/usrconf/ejb/TuningManagerRESTService/usrconf.properties

24235

NIO HTTP port of HiCommand Suite Tuning Manager

The same port number should be set for the following properties:

- The worker.TuningManager.port property in Common-Component-installation-directory/uCPSB11/CC/web/redirector/workers.properties

- The webserver.connector.nio_http.port property in Common-Component-installation-directory/uCPSB11/CC/server/usrconf/ejb/TuningManager/usrconf.properties

24239

NIO HTTP port of HiCommand Performance Reporter

The same port number should be set for the following properties:

- The worker.PerformanceReporter.port property in the Common-Component-installation-directory/uCPSB11/CC/web/redirector/workers.properties

- The webserver.connector.nio_http.port property in the Common-Component-installation-directory/uCPSB11/CC/server/usrconf/ejb/PerformanceReporter/usrconf.properties

Tuning Manager Agent Administration Guide

Contents of corrections of the Hitachi Command Suite Tuning Manager Agent Administration Guide:

Location to be corrected

4. Using Hybrid Store to manage data

Added content

In a Linux environment, if the path of the Hybrid Store output destination was changed for individual instances, or if you will make such a change in the future:

If Hybrid Store is selected as the performance database of Agent for RAID or Agent for NAS and the Hybrid Store output destination is changed for individual instances, change the permissions of any directory specified as an output destination to 700. In the same way, if you will change the Hybrid Store output destination for individual instances in the future, create the permissions of any directory specified as an output destination as 700. Also, if you change the Hybrid Store output destination for individual instances, change the permissions of any directory specified as an output destination to 700.

Location to be corrected

4. Using Hybrid Store to manage data

Changing the destination of Hybrid Store output

Changing the output destination for individual instances

Existing content

4. Move all record-name directories from the instance-name directory that was the output destination before the change to the directory created in step 3.

5. Start the Agent services with the following command:

Revised content

4. Set the permissions of the directory generated in step 3 to 700.

5. Move all record-name directories from the instance-name directory that was the output destination before the change to the directory created in step 3.

6. Start the Agent services with the following command:

Location to be corrected

5. Using Store databases to manage data

Added content

In a Linux environment, if the path of the Store DB output destination was changed for individual instances, or if you will make such a change in the future:

If the Store database is selected as the performance database and the Store database output destination is changed for individual instances, change the permissions of any directory specified as an output destination to 700. In the same way, if you will change the Store database output destination for individual instances in the future, create the permissions of any directory specified as an output destination to 700. Also, if you change the Store database output destination for individual instances, change the permissions of any directory specified as an output destination to 700.

Location to be corrected

7. Configuring the environment when the Tuning Manager API is enabled

Changing a port number of API Agent host (Windows)

Table 7-2 Changing Agent host ports (Windows)

Existing content

Port

Procedure for changing the port

24223

AJP port for Tuning Manager - Agent REST Application service

Change the values specified for the following properties. You must specify the same value for both properties.

·       The worker.worker1.port property in the Agent-installation-folder\htnm\HBasePSB\CC\web\redirector\workers.properties file

·       The webserver.connector.ajp13.port property in the Agent-installation-folder\htnm\HBasePSB\CC\server\userconf\ejb\AgentRESTService\usrconf.properties file

Revised content

Port

Procedure for changing the port

24223

Port for Tuning Manager - Agent REST Application service

Change the values specified for the following properties. You must specify the same value for both properties.

·       ProxyPass and ProxyPassReverse folders in Agent-installation-folder\htnm\Rest\config\htnm_httpsd.conf

·       The webserver.connector.ajp13.port property in the Agent-installation-folder\htnm\HBasePSB\CC\server\userconf\ejb\AgentRESTService\usrconf.properties file

Location to be corrected

7. Configuring the environment when the Tuning Manager API is enabled

Changing a port number of API Agent host (UNIX)

Table 7-3 Changing API Agent host ports (UNIX)

Existing content

Port

Procedure for changing the port

24223

AJP port for Tuning Manager - Agent REST Application service

AJP port for Tuning Manager - Agent REST Application service

Change the values specified for the following properties. You must specify the same value for both properties.

·       The worker.worker1.port property in the Agent-installation-directory/htnm/HBasePSB/CC/web/redirector/workers.properties file

·       The webserver.connector.ajp13.port property in the Agent-installation-directory/htnm/HBasePSB/CC/server/userconf/ejb/AgentRESTService/usrconf.properties file

Revised content

Port

Procedure for changing the port

24223

Port for Tuning Manager - Agent REST Application service

Change the values specified for the following properties. You must specify the same value for both properties.

·       ProxyPass and ProxyPassReverse directives in /opt/jp1pc/htnm/Rest/config/htnm_httpsd.conf

·       The webserver.connector.nio_http.port property in the Agent-installation-directory/htnm/HBasePSB/CC/server/userconf/ejb/AgentRESTService/usrconf.properties file

Location to be corrected

7. Configuring the environment when the Tuning Manager API is enabled

Deleted content

Switching to Oracle JDK

By default, the Tuning Manager Agent REST API Component uses the Java Development Kit (JDK) that comes along with Hitachi Command Suite products. To switch JDKs, you must run the htmchgjdk command after the Agents have been installed.

Location to be corrected

B List of port numbers

Port numbers used when monitoring a storage system

Table B-3 Port numbers used by TCP/IP connections

Existing content

Purpose

Port numbers for each destination storage system

VSP Gx00 models, VSP Fx00 models, VSP Nx00 models#

To collect performance data by a TCP/IP connection

1099

51099

51100

#

You can change the port number for VSP Gx00 models, VSP Fx00 models, and VSP Nx00 models. For details, see the storage system documentation that explains how to change or initialize the port number to be used with the SVP.

Note that, if you change a port number used by a storage system, you might also need to change the corresponding instance information. For details about how to change instance information, see the Tuning Manager Installation Guide.

However, if a port number (51099 or 51100) for RMIClassLoader and PreRMIServer of the storage system is changed, you do not need to change the instance information because Tuning Manager will automatically detect the changed port number.

Revised content

Purpose

Port numbers for each destination storage system

VSP Gx00 models, VSP Fx00 models, VSP Nx00 models#

To collect performance data by a TCP/IP connection

1099

51099

51100 - 51355

#

You can change the port number for VSP Gx00 models, VSP Fx00 models, and VSP Nx00 models. For details, see the storage system documentation that explains how to change or initialize the port number to be used with the SVP.

Note that, if you change a port number used by a storage system, you might also need to change the corresponding instance information. For details about how to change instance information, see the Tuning Manager Installation Guide.

However, if a port number (51099, 51100 to 51355) for RMIClassLoader and PreRMIServer of the storage system is changed, you do not need to change the instance information because Tuning Manager will automatically detect the changed port number.

Location to be corrected

F. List of files and directories

List of files and directories for Tuning Manager Agent components

Windows systems

Table F-1 List of files and directories for Tuning Manager common components

Deleted content

Folder name

File name

Description

installation-folder\htnm\bin\

htmchgjdk.exe

-

htmchgjdk.exe.manifest

Manifest file

installation-folder\htnm\bin\exec\

htmchgjdk.bat

JDK toggle command

htmchgjdkutil.vbs

Internal script used by the JDK toggle command

Location to be corrected

F. List of files and directories

List of files and directories for Tuning Manager Agent components

UNIX systems

Table F-2 List of files and directories for Tuning Manager common components (UNIX)

Deleted content

Folder name

File name

Description

/opt/jp1pc/htnm/bin/

htmchgjdk

JDK toggle command

Location to be corrected

F List of files and directories

List of Agent for RAID files and directories

Windows systems

Table F-7 Files and folders of Agent for RAID (Windows)

Added content

Files and folders of Agent for RAID (Windows)

Folder name

File name

Description

installation-folder\agtd\agent\

collectcommonconfig.ini

Internal file

installation-folder\agtd\agent\instance-name\lib\

-

Folder for storing common libraries for Agent for RAID

installation-folder\agtd\agent\instance-name\lib\pmmc\

-

Root folder for the function that acquires performance information in TCP/IP

installation-folder\agtd\agent\instance-name\lib\pmmc\collector\

-

Folder for storing libraries for the function that acquires performance information in TCP/IP

JSanRmiApiEx.jar

Internal file

JSanRmiServerUx.jar

Internal file

installation-folder\agtd\agent\instance-name\lib\pmmc\chkinst\

-

Folder for storing libraries for the function that acquires performance information in TCP/IP

JSanRmiApiEx.jar

Internal file

JSanRmiServerUx.jar

Internal file

Location to be corrected

F List of files and directories

List of Agent for RAID files and directories

Windows systems

Table F-7 Files and folders of Agent for RAID (Windows)

Deleted content

Files and folders of Agent for RAID (Windows)

Folder name

File name

Description

installation-folder\agtd\agent\lib\pmmc\rmi\70-06-23

-

Folder for storing libraries for the function that acquires performance information in TCP/IP

JSanRmiApiEx.jar

Internal file

JSanRmiServerUx.jar

Internal file

installation-folder\agtd\agent\lib\pmmc\rmi\70-06-31

-

Folder for storing libraries for the function that acquires performance information in TCP/IP

JSanRmiApiEx.jar

Internal file

JSanRmiServerUx.jar

Internal file

installation-folder\agtd\agent\lib\pmmc\rmi\70-06-35

-

Folder for storing libraries for the function that acquires performance information in TCP/IP

JSanRmiApiEx.jar

Internal file

JSanRmiServerUx.jar

Internal file

installation-folder\agtd\agent\lib\pmmc\rmi\70-06-36

-

Folder for storing libraries for the function that acquires performance information in TCP/IP

JSanRmiApiEx.jar

Internal file

JSanRmiServerUx.jar

Internal file

installation-folder\agtd\agent\lib\pmmc\rmi\73-03-40

-

Folder for storing libraries for the function that acquires performance information in TCP/IP

JSanRmiApiEx.jar

Internal file

JSanRmiServerUx.jar

Internal file

installation-folder\agtd\agent\lib\pmmc\rmi\73-03-46

-

Folder for storing libraries for the function that acquires performance information in TCP/IP

JSanRmiApiEx.jar

Internal file

JSanRmiServerUx.jar

Internal file

installation-folder\agtd\agent\lib\pmmc\rmi\73-03-50

-

Folder for storing libraries for the function that acquires performance information in TCP/IP

JSanRmiApiEx.jar

Internal file

JSanRmiServerUx.jar

Internal file

installation-folder\agtd\agent\lib\pmmc\rmi\73-03-51

-

Folder for storing libraries for the function that acquires performance information in TCP/IP

JSanRmiApiEx.jar

Internal file

JSanRmiServerUx.jar

Internal file

installation-folder\agtd\agent\lib\pmmc\rmi\75-03-40

-

Folder for storing libraries for the function that acquires performance information in TCP/IP

JSanRmiApiEx.jar

Internal file

JSanRmiServerUx.jar

Internal file

installation-folder\agtd\agent\lib\pmmc\rmi\75-03-46

-

Folder for storing libraries for the function that acquires performance information in TCP/IP

JSanRmiApiEx.jar

Internal file

JSanRmiServerUx.jar

Internal file

installation-folder\agtd\agent\lib\pmmc\rmi\xx-xx-xx

-

Folder for storing libraries for the function that acquires performance information in TCP/IP

JSanRmiApiEx.jar

Internal file

JSanRmiServerUx.jar

Internal file

SanRmiApi.jar

Internal file

Location to be corrected

F List of files and directories

List of Agent for RAID files and directories

UNIX systems

Table F-8 Files and directories of Agent for RAID (UNIX)

Added content

Files and directories of Agent for RAID (UNIX)

Directory name

File name

Description

/opt/jp1pc/agtd/

collectcommonconfig.ini

Internal file

/opt/jp1pc/agtd/agent/instance-name/lib/

-

Directory for common libraries for Agent for RAID

/opt/jp1pc/agtd/agent/instance-name/lib/pmmc/

-

Root directory for the function that acquires performance information in TCP/IP

/opt/jp1pc/agtd/agent/instance-name/lib/pmmc/collector/

-

Directory for storing libraries for the function that acquires performance information in TCP/IP

JSanRmiApiEx.jar

Internal file

JSanRmiServerUx.jar

Internal file

/opt/jp1pc/agtd/agent/instance-name/lib/pmmc/chkinst/

-

Directory for storing libraries for the function that acquires performance information in TCP/IP

JSanRmiApiEx.jar

Internal file

JSanRmiServerUx.jar

Internal file

Location to be corrected

F List of files and directories

List of Agent for RAID files and directories

UNIX systems

Table F-8 Files and directories of Agent for RAID (UNIX)

Deleted content

Files and directories of Agent for RAID (UNIX)

Directory name

File name

Description

/opt/jp1pc/agtd/agent/lib/pmmc/rmi/70-06-23/

-

Directory for storing libraries for the function that acquires performance information in TCP/IP

JSanRmiApiEx.jar

Internal file

JSanRmiServerUx.jar

Internal file

/opt/jp1pc/agtd/agent/lib/pmmc/rmi/70-06-31/

-

Directory for storing libraries for the function that acquires performance information in TCP/IP

JSanRmiApiEx.jar

Internal file

JSanRmiServerUx.jar

Internal file

/opt/jp1pc/agtd/agent/lib/pmmc/rmi/70-06-35/

-

Directory for storing libraries for the function that acquires performance information in TCP/IP

JSanRmiApiEx.jar

Internal file

JSanRmiServerUx.jar

Internal file

/opt/jp1pc/agtd/agent/lib/pmmc/rmi/70-06-36/

-

Directory for storing libraries for the function that acquires performance information in TCP/IP

JSanRmiApiEx.jar

Internal file

JSanRmiServerUx.jar

Internal file

/opt/jp1pc/agtd/agent/lib/pmmc/rmi/73-03-40/

-

Directory for storing libraries for the function that acquires performance information in TCP/IP

JSanRmiApiEx.jar

Internal file

JSanRmiServerUx.jar

Internal file

/opt/jp1pc/agtd/agent/lib/pmmc/rmi/73-03-46/

-

Directory for storing libraries for the function that acquires performance information in TCP/IP

JSanRmiApiEx.jar

Internal file

JSanRmiServerUx.jar

Internal file

/opt/jp1pc/agtd/agent/lib/pmmc/rmi/73-03-50/

-

Directory for storing libraries for the function that acquires performance information in TCP/IP

JSanRmiApiEx.jar

Internal file

JSanRmiServerUx.jar

Internal file

/opt/jp1pc/agtd/agent/lib/pmmc/rmi/73-03-51/

-

Directory for storing libraries for the function that acquires performance information in TCP/IP

JSanRmiApiEx.jar

Internal file

JSanRmiServerUx.jar

Internal file

/opt/jp1pc/agtd/agent/lib/pmmc/rmi/75-03-40/

-

Directory for storing libraries for the function that acquires performance information in TCP/IP

JSanRmiApiEx.jar

Internal file

JSanRmiServerUx.jar

Internal file

/opt/jp1pc/agtd/agent/lib/pmmc/rmi/75-03-46/

-

Directory for storing libraries for the function that acquires performance information in TCP/IP

JSanRmiApiEx.jar

Internal file

JSanRmiServerUx.jar

Internal file

/opt/jp1pc/agtd/agent/lib/pmmc/rmi/xx-xx-xx/

-

Directory for storing libraries for the function that acquires performance information in TCP/IP

JSanRmiApiEx.jar

Internal file

JSanRmiServerUx.jar

Internal file

SanRmiApi.jar

Internal file

Location to be corrected

G Program version compatibility with the data model or alarm table version

Correspondence between Agent versions, data model versions, and alarm table versions

Table G-1 Version Relationships Among Agents, Data Models, and Alarm Tables

Existing content

Agent Name

Agent Version

Data Model Version

Version of Alarm Table in Solution Set

Agent for RAID

8.6.2 - 8.7

11.0

9.40

Agent for RAID Map

8.0 - 8.7

5.0

-

Agent for Platform(Windows)

8.6.0 - 8.7

8.4

10.00

Agent for Platform(UNIX)

8.6.4 - 8.7

8.4

09.10

Agent for SAN Switch

6.0 - 8.7

5.0

7.00

Agent for NAS

8.4.1 - 8.7

6.8

8.13

Revised content

Agent Name

Agent Version

Data Model Version

Version of Alarm Table in Solution Set

Agent for RAID

8.8.3

15.0

9.40

8.8.0 - 8.8.1

14.0

8.7.7

13.0

8.7.3 - 8.7.6

12.0

8.6.2 - 8.7.1

11.0

Agent for RAID Map

8.0 - 8.8.3

5.0

-

Agent for Platform(Windows)

8.6.0 - 8.8.3

8.4

10.00

Agent for Platform(UNIX)

8.6.4 - 8.8.3

8.4

09.10

Agent for SAN Switch

6.0 - 8.8.3

5.0

7.00

Agent for NAS

8.4.1 - 8.8.3

6.8

8.13

Tuning Manager User Guide

Contents of corrections of the Hitachi Command Suite Tuning Manager User Guide:

Location to be corrected

1. Overview of the Tuning Manager series

Reviewing the reports

Reports generated from Performance Reporter

Existing content

Real-time report (single Agent):

Note that HTM - Agent for RAID cannot display real-time reports with performance data collected via a TCP/IP connection if the monitored storage system is one of the following: VSP G200, G400, G600, G800, HUS VM, VSP G1000, or Virtual Storage Platform series.

Revised content

Real-time report (single Agent):

Note that HTM - Agent for RAID cannot display real-time reports with performance data collected via a TCP/IP connection if the monitored storage system is one of the following: VSP 5000 series, VSP Fx00 models, VSP Gx00 models, VSP Nx00 models, HUS VM, VSP G1000, G1500, VSP F1500, or Virtual Storage Platform series.

Location to be corrected

3. Working with reports from Main Console

Reports overview

Types of reports displayed in Main Console

Existing content

Note: For Agent for RAID, when the monitored storage system is a storage system in the VSP G200, G400, G600, G800, HUS VM, VSP G1000, or Virtual Storage Platform series, the performance data that can be collected by using a TCP/IP connection cannot be displayed in reports in Main Console.

Revised content

Note: For Agent for RAID, when the monitored storage system is a storage system in the VSP 5000 series, VSP Fx00 models, VSP Gx00 models, VSP Nx00 models, HUS VM, VSP G1000, G1500, VSP F1500, or Virtual Storage Platform series, the performance data that can be collected by using a TCP/IP connection cannot be displayed in reports in Main Console.

Location to be corrected

3. Working with reports from Main Console

Reports overview

Displaying data using Main Console

Existing content

Information displayed if Full Allocation is enabled for VSP Gx00 models, VSP Fx00 models, and VSP G1000

For VSP Gx00 models, VSP Fx00 models, and VSP G1000, reserved is included in used and used rate for the pools and volumes of Dynamic Provisioning.

Revised content

Information displayed if Full Allocation is enabled for VSP 5000 series, VSP Gx00 models, VSP Fx00 models, VSP G1000, G1500, and VSP F1500

For VSP 5000 series, VSP Gx00 models, VSP Fx00 models, VSP G1000, G1500, and VSP F1500, reserved is included in used and used rate for the pools and volumes of Dynamic Provisioning.

Location to be corrected

3. Working with reports from Main Console

Reports overview

Displaying data using Main Console

Added content

Displaying the capacity of a Dynamic Provisioning pool

If the capacity saving function is enabled, the pool capacity items (total capacity, used capacity, and free capacity) displayed in Main Console indicate the values after capacity saving. if the pool contains a parity group of FMC, or a parity group that supports accelerated compression, the values before accelerated compression are displayed.

For a pool consisting of parity groups for which accelerated compression is enabled, a function that automatically adds volumes to the pool is available. If this function is enabled, the pool's total capacity will automatically increase.

To monitor the capacity exhaustion of a pool containing an FMC volume, you also need to monitor the physical capacity fields of the PD_PLC record by using Performance Reporter or Tuning Manager API. If the pool is set up to automatically add pool volumes, you only need to monitor the physical capacity.

Location to be corrected

3. Working with reports from Main Console

About generating reports

Display the historical and forecast (trend chart) reports with Flash Player

Existing content

The switch is made in the user.properties file with the rpt.Flashmode property. By default, the user.properties file is configured to display all reports as images (PNG format).

For information about configuring the user.properties file, see the Tuning Manager Server Administration Guide.

Revised content

The switch is made in the user.properties file with the rpt.flashmode property. By default, the user.properties file is configured to display all reports as images (PNG format).

If you use Device Manager GUI on Adobe AIR desktop application, specify the setting to display charts as images (PNG format).

For information about configuring the user.properties file, see the Tuning Manager Server Administration Guide.

Location to be corrected

4. Working with reports from Performance Reporter

Overview of reports from Performance Reporter

Types of reports displayed in Performance Reporter

Existing content

Real-time report (single Agent):

For Agent for RAID, when the monitored storage system is a storage system in the VSP G200, G400, G600, G800, HUS VM, VSP G1000, or Virtual Storage Platform series, real-time reports for the performance data that can be collected by using a TCP/IP connection cannot be displayed.

Revised content

Real-time report (single Agent):

For Agent for RAID, when the monitored storage system is a storage system in the VSP 5000 series, VSP Fx00 models, VSP Gx00 models, VSP Nx00 models, HUS VM, VSP G1000 , G1500, VSP F1500, or Virtual Storage Platform series, real-time reports for the performance data that can be collected by using a TCP/IP connection cannot be displayed.

Location to be corrected

7. Using alarms to monitor operations

Prerequisites for setting alarms

Setting up email alerts for an alarm

Mail Server Prerequisites

Deleted content

In some sections of the email sent when an alert event occurs in an Agent, only the line feed code (LF) is used to delimit lines. Make sure that the mail server supports emails in which only LF is used to delimit lines.

Location to be corrected

7. Using alarms to monitor operations

References for creating an alarm table

Variables to use when creating an alarm table

Table 7-4 Variables for configuring and defining an Alarm Table

Existing content

Variable

Description

%CVS[n][.p]

Measurement value that triggered the alarm notification (satisfying the conditional expression).

·       n

If multiple conditional expressions are specified, this variable specifies the field position (order), expressed as 1 or a greater value, where the first field is 1

:

Revised content

Variable

Description

%CVS[n][.p]

Measurement value that triggered the alarm notification (satisfying the conditional expression).

·       n

If multiple conditional expressions are specified, this variable specifies the field position (order), expressed as 1 or a greater value, where the first field is 1

If you specify 0 or a value greater than the number of conditional expressions, the measurement value in the first field is displayed.

:

Location to be corrected

7. Using alarms to monitor operations

Notes on creating alarms

Deleted content

Alarm evaluation time

If several records, specify monitoring conditions with different monitoring intervals and offsets (starting time) for an alarm, alarm evaluation is performed only when the monitoring time coincides with the scheduled data collection time. Change the collection interval setting as necessary.

Location to be corrected

Appendix A Restrictions on the Tuning Manager series

Performance information about drives or parity groups of flash drives

Table A-1 Main Console reports for which you cannot determine the load status from the usage rate

Existing content

Monitored storage system

Window name

Metric name

·       Hitachi USP

·       Universal Storage Platform V/VM series

·       Virtual Storage Platform series

·       Virtual Storage Platform G1000

·       HUS VM

·       VSP Gx00 models

·       VSP Fx00 models

Performance Summary window for parity groups

·       I/O Usage

·       Max I/O Usage

Historical Report window for parity groups

·       I/O Usage

·       Max I/O Usage

Revised content

Monitored storage system

Window name

Metric name

·       Universal Storage Platform V/VM series

·       Virtual Storage Platform series

·       HUS VM

Performance Summary window for parity groups

·       I/O Usage

·       Max I/O Usage

Historical Report window for parity groups

·       I/O Usage

·       Max I/O Usage

Location to be corrected

Appendix A Restrictions on the Tuning Manager series

Performance data for the Universal Storage Platform V/VM series, and Hitachi USP series

Existing content

Performance data for the Universal Storage Platform V/VM series, and Hitachi USP series

For the Universal Storage Platform V/VM series, and Hitachi USP series, the following performance data cannot be reported. n/a is displayed for all performance data that cannot be displayed:

·       Array group performance

Write Hit Rate

·       LDEV performance

Write Hit Rate

Revised content

Performance data for the Universal Storage Platform V/VM series

For the Universal Storage Platform V/VM series, the following performance data cannot be reported. n/a is displayed for all performance data that cannot be displayed:

·       Array group performance

Write Hit Rate

·       LDEV performance

Write Hit Rate

Location to be corrected

Appendix A Restrictions on the Tuning Manager series

Information displayed in Main Console

Existing content

Configuration information for Hitachi Virtual Storage Platform series, Hitachi Virtual Storage Platform G1000, and Hitachi Unified Storage VM

For Hitachi Virtual Storage Platform series, Hitachi Virtual Storage Platform G1000, and Hitachi Unified Storage VM, there is a limitation about configuration information report. The following path is used for navigation, No object is displayed as processor information.

Revised content

Configuration information for VSP 5000 series, VSP Gx00 models, VSP Fx00 models, HUS VM, VSP G1000, G1500, VSP F1500, or Virtual Storage Platform series

For VSP 5000 series, VSP Gx00 models, VSP Fx00 models, HUS VM, VSP G1000, G1500, VSP F1500, or Virtual Storage Platform series, there is a limitation about configuration information report. The following path is used for navigation, No object is displayed as processor information.

Location to be corrected

Appendix B Troubleshooting

Troubleshooting low cache hit rates leading to high backend read/write activity

Existing content

Note: For the Hitachi HUS100/AMS2000/AMS/WMS/SMS series, Hitachi USP, or Universal Storage Platform V/VM series, click CLPR Performance and CLPR History for more detailed information.

Revised content

Note: For the Hitachi HUS100/AMS2000/AMS/WMS/SMS series, or Universal Storage Platform V/VM series, click CLPR Performance and CLPR History for more detailed information.

Location to be corrected

Appendix B Troubleshooting

Processor information is not displayed in the Main Console (when Agents are used in Hybrid Store)

Existing content

Processor information is not displayed in the Main Console (when Agents are used in Hybrid Store)

If processor information is not displayed or performance information for processors cannot be viewed as in the cases described below, an error might have occurred in Tuning Manager Agent REST API component for the Agents host. Make sure that the services for Tuning Manager Agent REST API component are running normally.

·       The number of processors displayed in the summary area is 0.

·       Instead of the list of processors that should appear in the information area, "No object" is displayed.

·       No processors are displayed in the navigation area tree.

Note that if the disk space used for storing Hybrid Store has ever become insufficient, Tuning Manager Agent REST API component might be in a status where data summarized by the hour, day, week, month, and year is not output (Hybrid Store is in a read-only status). For details, see the Troubleshooting section that describes the action to be taken when the disk storing Hybrid Store does not have sufficient space in the Hitachi Command Suite Tuning Manager Agent Administration Guide.

Revised content

Processor information is not displayed or not updated by Main Console (When HTM-Agents are used in Hybrid Store)

If processor information is not displayed or updated, check whether the message KATN16014-W is output to the log. If it is output, follow the instruction provided by the message.

For details about the message KATN16014-W, see the Hitachi Command Suite Tuning Manager Messages.

Location to be corrected

Appendix B Troubleshooting

Added content

Intended Information is not displayed by Main Console or Performance Reporter

If intended information is not displayed by Main Console or Performance Reporter, delete internet temporary files from the web browser of the client.

Tuning Manager Hardware Reports Reference

Contents of corrections of the Hitachi Command Suite Tuning Manager Hardware Reports Reference

Location to be corrected

2. Working with Records

Notes on Collecting Records

Agent for RAID

Correspondence Between Microcode Versions for Storage Systems and Agent for RAID Functionality

Existing content

Table 2-10 Correspondence Between Microcode Versions for Storage Systems and Agent for RAID Functionality

Storage

Microcode Version

Correspondence to Agent for RAID Functionality

VSP 5000 series

·       VSP 5100

·       VSP 5500

·       VSP 5100H

·       VSP 5500H

09-01 or later

This is the required microcode version when using Agent for RAID to monitor VSP 5100, VSP 5500, VSP 5100H, VSP 5500H storage.

VSP G1000

08-01 or later

This is the required microcode version when using Agent for RAID to monitor VSP G1000 storage.

Revised content

Table 2-10 Correspondence Between Microcode Versions for Storage Systems and Agent for RAID Functionality

Storage

Microcode Version

Correspondence to Agent for RAID Functionality

VSP 5000 series

·       VSP 5100

·       VSP 5500

·       VSP 5100H

·       VSP 5500H

90-01 or later

This is the required microcode version when using Agent for RAID to monitor VSP 5100, VSP 5500, VSP 5100H, VSP 5500H storage.

90-04-03

In the drive type of a PD_RGC record, an SCM drive is displayed as "SSD NVMe".

90-04-04 or later

In the drive type of a PD_RGC record, an SCM drive is displayed as "SCM NVMe".

90-05 or later

"SCM NVMe" can be displayed as the tier type for each record.

90-07 or later

The following field information can be obtained.

PD_LDC record

- NVM Namespace ID (NVM_NAMESPACE_ID)

- NVM Subsystem ID (NVM_SUBSYSTEM_ID)

PD_PTC record

- Port Mode (PORT_MODE)

VSP G1000

80-01 or later

This is the required microcode version when using Agent for RAID to monitor VSP G1000 storage.

Location to be corrected

2. Working with Records

Notes on Collecting Records

Agent for RAID

Restrictions Regarding Volumes and Ports for Mainframes

Existing content

Restrictions when monitoring ports for mainframes

When a port is used for connecting to a mainframe, not all performance information can be obtained in the following storage systems: VSP G1000 (earlier than 80-03), Virtual Storage Platform series, or Universal Storage Platform V/VM series. The field values for the records listed in the table below are always 0 when monitoring ports for mainframes in the following storage systems: VSP G1000 (earlier than 80-03), Virtual Storage Platform series, or Universal Storage Platform V/VM series.

Table 2-14 Records Whose Field Values Are Always 0 When Monitoring Ports for Mainframes (for VSP G1000 (earlier than 80-03), Virtual Storage Platform series storage systems, and Universal Storage Platform V/VM series storage systems )

Revised content

Restrictions when monitoring ports for mainframes

When a port is used for connecting to a mainframe, not all performance information can be obtained in the following storage systems: VSP G1000 (earlier than 80-03), Virtual Storage Platform series, or Universal Storage Platform V/VM series. The field values for the records listed in the table below are always 0 when monitoring ports for mainframes in the following storage systems: VSP G1000 (earlier than 80-03), Virtual Storage Platform series, or Universal Storage Platform V/VM series.

Note, regarding the PI_PTSX record, you cannot collect performance data about mainframe systems, irrespective of the storage system or port attributes. The PI_MPTS record is not created for ports with FNP attributes.

Table 2-14 Records Whose Field Values Are Always 0 When Monitoring Ports for Mainframes (for VSP G1000 (earlier than 80-03), Virtual Storage Platform series storage systems, and Universal Storage Platform V/VM series storage systems, or for ports with FNP attributes )

Location to be corrected

2. Working with Records

Agent for RAID Records

Table 2-27 Agent for RAID Records

Added content

Record Name

Record ID

Information Stored in Record

Consistency Group

PI_CTGS

This record cannot be used because it is reserved.

Port Configuration Information EXTRA

PD_PTCX

This record cannot be used because it is reserved.

NVM Host Configuration

PD_NHC

This record cannot be used because it is reserved.

NVM Namespace Configuration

PD_NNC

This record cannot be used because it is reserved.

NVM Namespace Path Configuration

PD_NNPC

This record cannot be used because it is reserved.

NVM Subsystem Port Configuration

PD_NSPC

This record cannot be used because it is reserved.

NVM Subsystem Configuration

PD_NSSC

This record cannot be used because it is reserved.

Location to be corrected

2. Working with Records

Agent for RAID Records

Journal Group Summary (PI_JNLS)

Table 2-41 Journal Group Summary (PI_JNLS) Fields

Existing content

Journal Group Summary (PI_JNLS)

View Name

(Manager Name)

Description

Sum Rule

Format

Delta

Supported Storage

Data Source

Midrange

Enterprise

See Note

Note: The value of this field cannot be collected for the following storage systems: Universal Storage Platform V/VM series.

Revised content

Journal Group Summary (PI_JNLS)

View Name

(Manager Name)

Description

Sum Rule

Format

Delta

Supported Storage

Data Source

Midrange

Enterprise

See Note1, Note2

Note 1: The value of this field cannot be collected for the following storage systems: Universal Storage Platform V/VM series.

Note 2: Values for mainframe journal groups cannot be acquired for VSP G1000 (v02 or earlier).

Location to be corrected

2. Working with Records

Agent for RAID Records

LDEV Summary - Extended (PI_LDE)

Record Size

Existing content

+ Fixed part: 677 bytes

+ Variable part: 248 bytes

Revised content

+ Fixed part: 677 bytes

+ Variable part: 312 bytes

Location to be corrected

2. Working with Records

Agent for RAID Records

LDEV Summary - Extended (PI_LDE)

Table 2-43 LDEV Summary - Extended (PI_LDE) Fields

Added content

View Name (Manager Name)

Description

Virtual DKC Detail Name (VIRTUAL_DKC_DETAIL_NAME)

This field cannot be used because it is reserved.

 Location to be corrected

2. Working with Records

Agent for RAID Records

LDEV Summary 1 - Extended (PI_LDE1)

Record Size

Existing content

+ Fixed part: 677 bytes

+ Variable part: 248 bytes

Revised content

+ Fixed part: 677 bytes

+ Variable part: 312 bytes

Location to be corrected

2. Working with Records

Agent for RAID Records

LDEV Summary 1 - Extended (PI_LDE1)

Table 2-45 LDEV Summary 1 - Extended (PI_LDE1) Fields

Added content

View Name (Manager Name)

Description

Virtual DKC Detail Name (VIRTUAL_DKC_DETAIL_NAME)

This field cannot be used because it is reserved.

 Location to be corrected

2. Working with Records

Agent for RAID Records

LDEV Summary 2 - Extended (PI_LDE2)

Record Size

Existing content

+ Fixed part: 677 bytes

+ Variable part: 248 bytes

Revised content

+ Fixed part: 677 bytes

+ Variable part: 312 bytes

Location to be corrected

2. Working with Records

Agent for RAID Records

LDEV Summary 2 - Extended (PI_LDE2)

Table 2-47 LDEV Summary 2 - Extended (PI_LDE2) Fields

Added content

View Name (Manager Name)

Description

Virtual DKC Detail Name (VIRTUAL_DKC_DETAIL_NAME)

This field cannot be used because it is reserved.

 Location to be corrected

2. Working with Records

Agent for RAID Records

LDEV Summary 3 - Extended (PI_LDE3)

Record Size

Existing content

+ Fixed part: 677 bytes

+ Variable part: 248 bytes

Revised content

+ Fixed part: 677 bytes

+ Variable part: 312 bytes

Location to be corrected

2. Working with Records

Agent for RAID Records

LDEV Summary 3 - Extended (PI_LDE3)

Table 2-49 LDEV Summary 3 - Extended (PI_LDE3) Fields

Added content

View Name (Manager Name)

Description

Virtual DKC Detail Name (VIRTUAL_DKC_DETAIL_NAME)

This field cannot be used because it is reserved.

Location to be corrected

2. Working with Records

Agent for RAID Records

Logical Device Configuration (PD_LDC)

Record Size

Existing content

+ Fixed part: 681 bytes

+ Variable part: 506 bytes

Revised content

+ Fixed part: 681 bytes

+ Variable part: 602 bytes

Location to be corrected

2. Working with Records

Agent for RAID Records

Logical Device Configuration (PD_LDC)

Table 2-53 Logical Device Configuration (PD_LDC) Fields

Added content

Logical Device Configuration (PD_LDC)

View Name

(Manager Name)

Description

Sum Rule

Format

Delta

Supported Storage

Data Source

Midrange

Enterprise

NVM_NAMESPACE_ID

(NVM Namespace ID)

Namespace ID of the logical device.

--

string(16)

No

--

Supported

See Note 18

--

NVM_SUBSYSTEM_ID

(NVM Subsystem ID)

NVM subsystem ID of the logical device.

--

string(16)

No

--

Supported

See Note 18

--

Virtual DKC Detail Name (VIRTUAL_DKC_DETAIL_NAME)

This field cannot be used because it is reserved.

Note: 18: Not supported by VSP Gx00 models, VSP Fx00 models, VSP Nx00 models, HUS VM, VSP G1000, G1500, VSP F1500, or Virtual Storage Platform series storage systems.

Location to be corrected

2. Working with Records

Agent for RAID Records

Logical Device Summary (PI_LDS)

Record Size

Existing content

+ Fixed part: 677 bytes

+ Variable part: 348 bytes

Revised content

+ Fixed part: 677 bytes

+ Variable part: 412 bytes

Location to be corrected

2. Working with Records

Agent for RAID Records

Logical Device Summary (PI_LDS)

Table 2-55 Logical Device Summary (PI_LDS) Fields

Added content

View Name (Manager Name)

Description

Virtual DKC Detail Name (VIRTUAL_DKC_DETAIL_NAME)

This field cannot be used because it is reserved.

 Location to be corrected

2. Working with Records

Agent for RAID Records

Logical Device Summary 1 (PI_LDS1)

Record Size

Existing content

+ Fixed part: 677 bytes

+ Variable part: 348 bytes

Revised content

+ Fixed part: 677 bytes

+ Variable part: 412 bytes

Location to be corrected

2. Working with Records

Agent for RAID Records

Logical Device Summary 1 (PI_LDS1)

Table 2-57 Logical Device Summary 1 (PI_LDS1) Fields

Added content

View Name (Manager Name)

Description

Virtual DKC Detail Name (VIRTUAL_DKC_DETAIL_NAME)

This field cannot be used because it is reserved.

 Location to be corrected

2. Working with Records

Agent for RAID Records

Logical Device Summary 2 (PI_LDS2)

Record Size

Existing content

+ Fixed part: 677 bytes

+ Variable part: 348 bytes

Revised content

+ Fixed part: 677 bytes

+ Variable part: 412 bytes

Location to be corrected

2. Working with Records

Agent for RAID Records

Logical Device Summary 2 (PI_LDS2)

Table 2-59 Logical Device Summary 2 (PI_LDS2) Fields

Added content

View Name (Manager Name)

Description

Virtual DKC Detail Name (VIRTUAL_DKC_DETAIL_NAME)

This field cannot be used because it is reserved.

 Location to be corrected

2. Working with Records

Agent for RAID Records

Logical Device Summary 3 (PI_LDS3)

Record Size

Existing content

+ Fixed part: 677 bytes

+ Variable part: 348 bytes

Revised content

+ Fixed part: 677 bytes

+ Variable part: 412 bytes

Location to be corrected

2. Working with Records

Agent for RAID Records

Logical Device Summary 3 (PI_LDS3)

Table 2-61 Logical Device Summary 3 (PI_LDS3) Fields

Added content

View Name (Manager Name)

Description

Virtual DKC Detail Name (VIRTUAL_DKC_DETAIL_NAME)

This field cannot be used because it is reserved.

Location to be corrected

2. Working with Records

Agent for RAID Records

Pool Configuration (PD_PLC)

Table 2-67 Pool Configuration (PD_PLC) Fields

Existing content

View Name (Manager Name)

Description

Auto Expansion (AUTO_EXPANSION)

Whether to automatically add pool volumes according to the compression ratio of a parity group for which accelerated compression is enabled.

Enable: Automatically adds pool volumes according to the compression ratio of a parity group for which accelerated compression is enabled.

Disable: Pool volumes for which accelerated compression is enabled are not added automatically.

"": This function is not supported.

Revised content

View Name (Manager Name)

Description

Auto Expansion (AUTO_EXPANSION)

Whether to automatically add pool volumes according to the compression ratio of a parity group for which accelerated compression is enabled.

Enabled: Automatically adds pool volumes according to the compression ratio of a parity group for which accelerated compression is enabled.

Disabled: Pool volumes for which accelerated compression is enabled are not added automatically.

"": This function is not supported.

Location to be corrected

2. Working with Records

Agent for RAID Records

Pool Tier Page Relocation (PD_PLTR)

Table 2-77 Pool Tier Page Relocation (PD_PLTR) Fields

Existing content

Note: 6: For a flash drive, the field values are as follows:

"SSD SLC", "SSD MLC", "FMD", "FMC", "SSD(RI)", "SSD NVMe"

Revised content

Note: 6: For a flash drive, the field values are as follows:

"SSD SLC", "SSD MLC", "FMD", "FMC", "SSD(RI)", "SSD NVMe", "SCM NVMe"

Location to be corrected

2. Working with Records

Agent for RAID Records

Pool Tier Type Configuration (PD_PLTC)

Table 2-79 Pool Tier Type Configuration (PD_PLTC) Fields

Existing content

Note: 10: For a flash drive, the field values are as follows:

"SSD SLC", "SSD MLC", "FMD", "FMC", "SSD(RI)", "SSD NVMe"

Revised content

Note: 10: For a flash drive, the field values are as follows:

"SSD SLC", "SSD MLC", "FMD", "FMC", "SSD(RI)", "SSD NVMe", "SCM NVMe"

Location to be corrected

2. Working with Records

Agent for RAID Records

Pool Tier Type I/O Information (PI_PLTI)

Table 2-81 Pool Tier Type I/O Information (PI_PLTI) Fields

Existing content

Note: 2: For a flash drive, the field values are as follows:

"SSD SLC", "SSD MLC", "FMD", "FMC", "SSD(RI)", "SSD NVMe"

Revised content

Note: 2: For a flash drive, the field values are as follows:

"SSD SLC", "SSD MLC", "FMD", "FMC", "SSD(RI)", "SSD NVMe", "SCM NVMe"

Location to be corrected

2. Working with Records

Agent for RAID Records

Pool Tier Type Operation Status (PD_PLTS)

Table 2-83 Pool Tier Type Operation Status (PD_PLTS) Fields

Existing content

Note: 6: For a flash drive, the field values are as follows:

"SSD SLC", "SSD MLC", "FMD", "FMC", "SSD(RI)", "SSD NVMe"

Revised content

Note: 6: For a flash drive, the field values are as follows:

"SSD SLC", "SSD MLC", "FMD", "FMC", "SSD(RI)", "SSD NVMe", "SCM NVMe"

Location to be corrected

2. Working with Records

Agent for RAID Records

Port Configuration (PD_PTC)

Record Size

Existing content

+ Fixed part: 681 bytes

+ Variable part: 167 bytes

Revised content

+ Fixed part: 681 bytes

+ Variable part: 231 bytes

Location to be corrected

2. Working with Records

Agent for RAID Records

Port Configuration (PD_PTC)

Table 2-85 Port Configuration (PD_PTC) Fields

Added content

Port Configuration (PD_PTC)

View Name

(Manager Name)

Description

Sum Rule

Format

Delta

Supported Storage

Data Source

Midrange

Enterprise

PORT_MODE (Port Mode)

Operation mode of the storage system port.

--

string(64)

No

--

Supported

See Note 3

--

Note: 3: Not supported by VSP Gx00 models, VSP Fx00 models, VSP Nx00 models, HUS VM, VSP G1000, G1500, VSP F1500, or Virtual Storage Platform series storage systems.

Location to be corrected

2. Working with Records

Agent for RAID Records

RAID Group Configuration (PD_RGC)

Table 2-91 RAID Group Configuration (PD_RGC) Fields

Existing content

View Name (Manager Name)

Description

Display Drive Type (DISPLAY_DRIVE_TYPE)

Type of drive making up the parity group (display name)

Drive Type (DRIVE_TYPE)

Type of drive making up the parity group

See Note 5

Note: 5: For a flash drive, the field values are as follows:

"SSD SLC", "SSD MLC", "FMD", "FMC", "SSD(RI)", "SSD NVMe"

"FMC" is the value to be stored when the drive type is FMC, FMD DC2, or FMD HDE.

Revised content

View Name (Manager Name)

Description

Display Drive Type (DISPLAY_DRIVE_TYPE)

Type of drive making up the parity group (display name)

See Note 6

Drive Type (DRIVE_TYPE)

Type of drive making up the parity group

See Note 5 and Note6

Note: 5: For a flash drive, the field values are as follows:

"SSD SLC", "SSD MLC", "FMD", "FMC", "SSD(RI)", "SSD NVMe", "SCM NVMe"

"FMC" is the value to be stored when the drive type is FMC, FMD DC2, or FMD HDE.

Note: 6: For SCM drives of VSP 5000 series, the displayed content differs depending on the microcode version of the storage system.

- If the microcode version of the storage system is earlier than version 90-04-04, an SCM drive is displayed as an SSD drive (SSD NVMe).

- If the microcode version of the storage system is version 90-04-04 or later, an SCM drive is displayed as an SCM drive (SCM NVMe).

 Location to be corrected

2. Working with Records

Agent for RAID Records

Storage Detail (PD)

Record Size

Existing content

+ Fixed part: 863 bytes

+ Variable part: 0 bytes

Revised content

+ Fixed part: 927 bytes

+ Variable part: 0 bytes

Location to be corrected

2. Working with Records

Agent for RAID Records

Storage Detail (PD)

Table 2-95 Storage Detail (PD) Fields

Added content

View Name (Manager Name)

Description

DKC Detail Name (DKC_DETAIL_NAME)

This field cannot be used because it is reserved.

Location to be corrected

2. Working with Records

Agent for RAID Records

V-VOL Tier Type Configuration (PD_VVTC)

Table 2-105 V-VOL Tier Type Configuration (PD_VVTC) Fields

Existing content

Note: 4: For a flash drive, the field values are as follows:

"SSD SLC", "SSD MLC", "FMD", "FMC", "SSD(RI)", "SSD NVMe"

Revised content

Note: 4: For a flash drive, the field values are as follows:

"SSD SLC", "SSD MLC", "FMD", "FMC", "SSD(RI)", "SSD NVMe", "SCM NVMe"

Location to be corrected

2. Working with Records

Agent for RAID Records

V-VOL Tier Type I/O Information (PI_VVTI)

Table 2-107 V-VOL Tier Type I/O Information (PI_VVTI) Fields

Existing content

Note: 2: For a flash drive, the field values are as follows:

"SSD SLC", "SSD MLC", "FMD", "FMC", "SSD(RI)", "SSD NVMe"

Revised content

Note: 2: For a flash drive, the field values are as follows:

"SSD SLC", "SSD MLC", "FMD", "FMC", "SSD(RI)", "SSD NVMe", "SCM NVMe"

Location to be corrected

2. Working with Records

Agent for RAID Records (collection by using a TCP/IP connection)

Table 2-110 Agent for RAID Records

Added content

Record Name

Record ID

Information Stored in Record

Remote Path Configuration

PD_RPHC

This record cannot be used because it is reserved.

Location to be corrected

2. Working with Records

Agent for RAID Records (collection by using a TCP/IP connection)

Between Cache Switch and Cache Memory Summary (PI_CCMS)

Table 2-112 Between Cache Switch and Cache Memory Summary (PI_CCMS) Fields

Existing content

View Name (Manager Name)

Description

Max Access Path Usage % (MAX_ACCESS_PATH_USAGE_RATE)

Usage rate of the access path between a cache switch and cache memory (%). If the values of a smaller unit (e.g., minutes) are summarized to a greater unit (e.g., hours), the maximum value is stored rather than the average value.

Revised content

View Name (Manager Name)

Description

Max Access Path Usage % (MAX_ACCESS_PATH_USAGE_RATE)

Usage rate of the access path between a cache switch and cache memory (%). If the values of a smaller unit (e.g., minutes) are summarized to a greater unit (e.g., hours), the maximum value is stored rather than the average value.

See Note 4

Note: 4: Values cannot be stored in records in units of minutes. For this reason, the Tuning Manager API cannot obtain data that is saved in units of minutes. Note that, in Performance Reporter, "0" is displayed for such values.

Location to be corrected

2. Working with Records

Agent for RAID Records (collection by using a TCP/IP connection)

Between CHA and Cache Switch Summary (PI_CHAC)

Table 2-114 Between CHA and Cache Switch Summary (PI_CHAC) Fields

Existing content

View Name (Manager Name)

Description

Max Access Path Usage % (MAX_ACCESS_PATH_USAGE_RATE)

Usage rate of the access path between the channel adapter and the cache switch (%). If the values of a smaller unit (e.g., minutes) are summarized to a greater unit (e.g., hours), the maximum value is stored rather than the average value.

Revised content

View Name (Manager Name)

Description

Max Access Path Usage % (MAX_ACCESS_PATH_USAGE_RATE)

Usage rate of the access path between the channel adapter and the cache switch (%). If the values of a smaller unit (e.g., minutes) are summarized to a greater unit (e.g., hours), the maximum value is stored rather than the average value.

See Note 3

Note: 3: Values cannot be stored in records in units of minutes. For this reason, the Tuning Manager API cannot obtain data that is saved in units of minutes. Note that, in Performance Reporter, "0" is displayed for such values.

Location to be corrected

2. Working with Records

Agent for RAID Records (collection by using a TCP/IP connection)

Between CHB and Main Blade Summary (PI_CBMB)

Table 2-116 Between CHB and Main Blade Summary (PI_CBMB) Fields

Existing content

View Name (Manager Name)

Description

Max Access Path Usage % (MAX_ACCESS_PATH_USAGE_RATE)

Usage rate of the access path between the channel blade and the main blade (%). If the values of a smaller unit (e.g., minutes) are summarized to a greater unit (e.g., hours), the maximum value is stored rather than the average value.

Revised content

View Name (Manager Name)

Description

Max Access Path Usage % (MAX_ACCESS_PATH_USAGE_RATE)

Usage rate of the access path between the channel blade and the main blade (%). If the values of a smaller unit (e.g., minutes) are summarized to a greater unit (e.g., hours), the maximum value is stored rather than the average value.

See Note 1

Note: 1: Values cannot be stored in records in units of minutes. For this reason, the Tuning Manager API cannot obtain data that is saved in units of minutes. Note that, in Performance Reporter, "0" is displayed for such values.

Location to be corrected

2. Working with Records

Agent for RAID Records (collection by using a TCP/IP connection)

Between DKA and Cache Switch Summary (PI_DKAC)

Table 2-118 Between DKA and Cache Switch Summary (PI_DKAC) Fields

Existing content

View Name (Manager Name)

Description

Max Access Path Usage % (MAX_ACCESS_PATH_USAGE_RATE)

Usage rate of the access path between the disk adapter and the cache switch (%). If the values of a smaller unit (e.g., minutes) are summarized to a greater unit (e.g., hours), the maximum value is stored rather than the average value.

Revised content

View Name (Manager Name)

Description

Max Access Path Usage % (MAX_ACCESS_PATH_USAGE_RATE)

Usage rate of the access path between the disk adapter and the cache switch (%). If the values of a smaller unit (e.g., minutes) are summarized to a greater unit (e.g., hours), the maximum value is stored rather than the average value.

See Note 3

Note: 3: Values cannot be stored in records in units of minutes. For this reason, the Tuning Manager API cannot obtain data that is saved in units of minutes. Note that, in Performance Reporter, "0" is displayed for such values.

Location to be corrected

2. Working with Records

Agent for RAID Records (collection by using a TCP/IP connection)

Between DKB and Main Blade Summary (PI_DBMB)

Table 2-120 Between DKB and Main Blade Summary (PI_DBMB) Fields

Existing content

View Name (Manager Name)

Description

Max Access Path Usage % (MAX_ACCESS_PATH_USAGE_RATE)

Usage rate of the access path between the disk blade and the main blade (%). If the values of a smaller unit (e.g., minutes) are summarized to a greater unit (e.g., hours), the maximum value is stored rather than the average value.

Revised content

View Name (Manager Name)

Description

Max Access Path Usage % (MAX_ACCESS_PATH_USAGE_RATE)

Usage rate of the access path between the disk blade and the main blade (%). If the values of a smaller unit (e.g., minutes) are summarized to a greater unit (e.g., hours), the maximum value is stored rather than the average value.

See Note 1

Note: 1: Values cannot be stored in records in units of minutes. For this reason, the Tuning Manager API cannot obtain data that is saved in units of minutes. Note that, in Performance Reporter, "0" is displayed for such values.

Location to be corrected

2. Working with Records

Agent for RAID Records (collection by using a TCP/IP connection)

Between MP Blade and Cache Switch Summary (PI_MPCS)

Table 2-122 Between MP Blade and Cache Switch Summary (PI_MPCS) Fields

Existing content

View Name (Manager Name)

Description

Max Access Path Usage % (MAX_ACCESS_PATH_USAGE_RATE)

Usage rate of the access path between the disk blade and the main blade (%). If the values of a smaller unit (e.g., minutes) are summarized to a greater unit (e.g., hours), the maximum value is stored rather than the average value.

Revised content

View Name (Manager Name)

Description

Max Access Path Usage % (MAX_ACCESS_PATH_USAGE_RATE)

Usage rate of the access path between the MP Blade and the cache switch (%). If the values of a smaller unit (e.g., minutes) are summarized to a greater unit (e.g., hours), the maximum value is stored rather than the average value.

See Note 3

Note: 3: Values cannot be stored in records in units of minutes. For this reason, the Tuning Manager API cannot obtain data that is saved in units of minutes. Note that, in Performance Reporter, "0" is displayed for such values.

Location to be corrected

2. Working with Records

Agent for RAID Records (collection by using a TCP/IP connection)

Cache Path Summary (PI_CPS)

Table 2-124 Cache Path Summary (PI_CPS) Fields

Existing content

View Name (Manager Name)

Description

Max Access Path Usage % (MAX_ACCESS_PATH_USAGE_RATE)

Usage rate of the access path for the cache path in the main blade (%). If the values of a smaller unit (e.g., minutes) are summarized to a greater unit (e.g., hours), the maximum value is stored rather than the average value.

Revised content

View Name (Manager Name)

Description

Max Access Path Usage % (MAX_ACCESS_PATH_USAGE_RATE)

Usage rate of the access path for the cache path in the main blade (%). If the values of a smaller unit (e.g., minutes) are summarized to a greater unit (e.g., hours), the maximum value is stored rather than the average value.

See Note 1

Note: 1: Values cannot be stored in records in units of minutes. For this reason, the Tuning Manager API cannot obtain data that is saved in units of minutes. Note that, in Performance Reporter, "0" is displayed for such values.

Location to be corrected

2. Working with Records

Agent for RAID Records (collection by using a TCP/IP connection)

CHA DRR Summary (PI_CHDR)

Table 2-126 CHA DRR Summary (PI_CHDR) Fields

Existing content

View Name (Manager Name)

Description

Max Busy % (MAX_BUSY_RATE)

Usage rate of the data recovery reconfiguration circuit (DRR) of the channel adapter. If the values of a smaller unit (e.g., minutes) are summarized to a greater unit (e.g., hours), the maximum value is stored rather than the average value.

Revised content

View Name (Manager Name)

Description

Max Busy % (MAX_BUSY_RATE)

Usage rate of the data recovery reconfiguration circuit (DRR) of the channel adapter. If the values of a smaller unit (e.g., minutes) are summarized to a greater unit (e.g., hours), the maximum value is stored rather than the average value.

See Note 1

Note: 1: Values cannot be stored in records in units of minutes. For this reason, the Tuning Manager API cannot obtain data that is saved in units of minutes. Note that, in Performance Reporter, "0" is displayed for such values.

Location to be corrected

2. Working with Records

Agent for RAID Records (collection by using a TCP/IP connection)

CLPR Per MP Blade Summary Extra (PI_CLMX)

Table 2-128 CLPR Per MP Blade Summary Extra (PI_CLMX) Fields

Existing content

View Name (Manager Name)

Description

Max Cache Memory Usage % (MAX_CACHE_MEMORY_USAGE_RATE)

Of the cache memory allocated to each MP Blade in the CLPR, the percentage of memory used by the LDEV owned by the MP Blade in the Ldev Owner Id field

Max Cache Write Pending Usage % (MAX_CACHE_WRITE_PENDING_RATE)

Of the cache memory allocated to each MP Blade in the CLPR, the maximum percentage of memory used by write-pending data on the LDEV owned by the MP Blade in the Ldev Owner Id field

Revised content

View Name (Manager Name)

Description

Max Cache Memory Usage % (MAX_CACHE_MEMORY_USAGE_RATE)

Of the cache memory allocated to each MP Blade in the CLPR, the percentage of memory used by the LDEV owned by the MP Blade in the Ldev Owner Id field

See Note 1

Max Cache Write Pending Usage % (MAX_CACHE_WRITE_PENDING_RATE)

Of the cache memory allocated to each MP Blade in the CLPR, the maximum percentage of memory used by write-pending data on the LDEV owned by the MP Blade in the Ldev Owner Id field

See Note 1

Note: 1: Values cannot be stored in records in units of minutes. For this reason, the Tuning Manager API cannot obtain data that is saved in units of minutes. Note that, in Performance Reporter, "0" is displayed for such values.

Location to be corrected

2. Working with Records

Agent for RAID Records (collection by using a TCP/IP connection)

DKA DRR Summary (PI_DKDR)

Table 2-130 DKA DRR Summary (PI_DKDR) Fields

Existing content

View Name (Manager Name)

Description

Max Busy % (MAX_BUSY_RATE)

Usage of the data recovery reconfiguration circuit. If the values of a smaller unit (e.g., minutes) are summarized to a greater unit (e.g., hours), the maximum value is stored rather than the average value.

Revised content

View Name (Manager Name)

Description

Max Busy % (MAX_BUSY_RATE)

Usage of the data recovery reconfiguration circuit. If the values of a smaller unit (e.g., minutes) are summarized to a greater unit (e.g., hours), the maximum value is stored rather than the average value.

See Note 1

Note: 1: Values cannot be stored in records in units of minutes. For this reason, the Tuning Manager API cannot obtain data that is saved in units of minutes. Note that, in Performance Reporter, "0" is displayed for such values.

Location to be corrected

2. Working with Records

Agent for RAID Records (collection by using a TCP/IP connection)

LDEV Utilization (PI_LDU)

Table 2-148 LDEV Utilization (PI_LDU) Fields

Existing content

View Name (Manager Name)

Description

Max Busy % (MAX_BUSY_RATE)

Volume usage. If the values of a smaller unit (e.g., minutes) are summarized to a greater unit (e.g., hours), the maximum value is stored rather than the average value.

See Note 2

Revised content

View Name (Manager Name)

Description

Max Busy % (MAX_BUSY_RATE)

Volume usage. If the values of a smaller unit (e.g., minutes) are summarized to a greater unit (e.g., hours), the maximum value is stored rather than the average value.

See Note 2, Note 3

Note: 3: Values cannot be stored in records in units of minutes. For this reason, the Tuning Manager API cannot obtain data that is saved in units of minutes. Note that, in Performance Reporter, "0" is displayed for such values.

Location to be corrected

2. Working with Records

Agent for RAID Records (collection by using a TCP/IP connection)

Main Blade DRR Summary (PI_MBDR)

Table 2-156 Main Blade DRR Summary (PI_MBDR) Fields

Existing content

View Name (Manager Name)

Description

Max Busy % (MAX_BUSY_RATE)

Usage rate of the data recovery reconfiguration circuit (DRR). If the values of a smaller unit (e.g., minutes) are summarized to a greater unit (e.g., hours), the maximum value is stored instead of the average value.

Revised content

View Name (Manager Name)

Description

Max Busy % (MAX_BUSY_RATE)

Usage rate of the data recovery reconfiguration circuit (DRR). If the values of a smaller unit (e.g., minutes) are summarized to a greater unit (e.g., hours), the maximum value is stored instead of the average value.

See Note 1

Note: 1: Values cannot be stored in records in units of minutes. For this reason, the Tuning Manager API cannot obtain data that is saved in units of minutes. Note that, in Performance Reporter, "0" is displayed for such values.

Location to be corrected

2. Working with Records

Agent for RAID Records (collection by using a TCP/IP connection)

Mainframe Port Summary (PI_MPTS)

Table 2-158 Mainframe Port Summary (PI_MPTS) Fields

Existing content

View Name (Manager Name)

Description

Max I/O /sec (MAX_IO_RATE)

Maximum number of read and write operations per second measured for each port

Max Xfer /sec (MAX_XFER_RATE)

Maximum amount of data transferred by read and write operations for each port (kilobytes per second)

Revised content

View Name (Manager Name)

Description

Max I/O /sec (MAX_IO_RATE)

Maximum number of read and write operations per second measured for each port

See Note 6

Max Xfer /sec (MAX_XFER_RATE)

Maximum amount of data transferred by read and write operations for each port (kilobytes per second)

See Note 6

Note: 6: Values cannot be stored in records in units of minutes. For this reason, the Tuning Manager API cannot obtain data that is saved in units of minutes. Note that, in Performance Reporter, "0" is displayed for such values.

Location to be corrected

2. Working with Records

Agent for RAID Records (collection by using a TCP/IP connection)

MP Summary (PI_MPS)

Table 2-160 MP Summary (PI_MPS) Fields

Existing content

View Name (Manager Name)

Description

Max Busy % (MAX_BUSY_RATE)

Processor usage. If the values of a smaller unit (e.g., minutes) are summarized to a greater unit (e.g., hours), the maximum value is stored rather than the average value.

Revised content

View Name (Manager Name)

Description

Max Busy % (MAX_BUSY_RATE)

Processor usage. If the values of a smaller unit (e.g., minutes) are summarized to a greater unit (e.g., hours), the maximum value is stored rather than the average value.

See Note 1

Note: 1: Values cannot be stored in records in units of minutes. For this reason, the Tuning Manager API cannot obtain data that is saved in units of minutes. Note that, in Performance Reporter, "0" is displayed for such values.

Location to be corrected

2. Working with Records

Agent for RAID Records (collection by using a TCP/IP connection)

Port Summary Extra (PI_PTSX)

Existing content

Function

The Port Summary Extra (PI_PTSX) record stores the performance data indicating the performance of storage system ports.

Revised content

Function

The Port Summary Extra (PI_PTSX) record stores the performance data indicating the performance of storage system ports.

However, you will not be able to collect performance data about mainframe systems. You can collect performance data about mainframe system ports by using the PI_MPTS record.

Location to be corrected

2. Working with Records

Agent for RAID Records (collection by using a TCP/IP connection)

Port Summary Extra (PI_PTSX)

Table 2-162 Port Summary Extra (PI_PTSX) Fields

Existing content

View Name (Manager Name)

Description

Initiator Avg Xfer Rate (INITIATOR_AVG_XFER_RATE)

Average transfer rate of read and write operations for a storage system port (megabytes per second) (Initiator port value/External port value)

Max I/O /sec (MAX_IO_RATE)

Maximum frequency of read and write operations for a storage system port (number of operations per second)

Max Xfer /sec (MAX_XFER_RATE)

Maximum transfer rate of read and write operations for a storage system port (kilobytes per second)

Revised content

View Name (Manager Name)

Description

Initiator Avg Xfer Rate (INITIATOR_AVG_XFER_RATE)

Average transfer rate of read and write operations for a storage system port (kilobytes per second) (Initiator port value/External port value)

Max I/O /sec (MAX_IO_RATE)

Maximum frequency of read and write operations for a storage system port (number of operations per second)

See Note 1

Max Xfer /sec (MAX_XFER_RATE)

Maximum transfer rate of read and write operations for a storage system port (kilobytes per second)

See Note 1

Note: 1: Values cannot be stored in records in units of minutes. For this reason, the Tuning Manager API cannot obtain data that is saved in units of minutes. Note that, in Performance Reporter, "0" is displayed for such values.

Location to be corrected

2. Working with Records

Agent for RAID Records (collection by using a TCP/IP connection)

RAID Group Utilization (PI_RGU)

Table 2-166 RAID Group Utilization (PI_RGU) Fields

Existing content

View Name (Manager Name)

Description