Hitachi Tuning Manager 8.5.0-02 Release Notes · 8.5.0-02 Release Notes ... This document (RN-00HS262-78, December 2016) provides late-breaking information about the Hitachi Tuning

© 2016 Hitachi, Ltd. All rights reserved. 1

RN-00HS262-78 (December 2016)

Hitachi Tuning Manager

8.5.0-02 Release Notes

Contents

Contents .................................................................................................. 1

About this document .................................................................................. 1

Intended audience ..................................................................................... 1

Getting help ............................................................................................. 2

About this release ..................................................................................... 2

Product package contents ........................................................................... 2

New features and important enhancements ................................................... 3

System requirements ................................................................................. 5

Resolved problems .................................................................................... 5

Known problems ..................................................................................... 10

Installation precautions ............................................................................ 15

Upgrade precautions ................................................................................ 17

Removal precautions ............................................................................... 25

Usage precautions ................................................................................... 25

Documentation ....................................................................................... 48

Copyrights and licenses ............................................................................ 54

About this document

This document (RN-00HS262-78, December 2016) provides late-breaking

information about the Hitachi Tuning Manager 8.5.0-02. 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 Data Systems partners who license and use the Hitachi Tuning Manager.



Getting help

Hitachi Data Systems Support Connect is the destination for technical support of

products and solutions sold by Hitachi Data Systems. To contact technical

support, log on to Hitachi Data Systems Support Connect for contact information: https://support.hds.com/en_us/contact-us.html.

Hitachi Data Systems Community is a global online community for HDS

customers, partners, independent software vendors, employees, and prospects. It is the destination to get answers, discover insights, and make connections.

Join the conversation today! Go to community.hds.com, register, and complete your profile.

About this release

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.5.0-00 Full

Package

-

Hitachi Tuning Manager - Agent for

Server System

8.5.0-00 Full

Package

-


Oracle 8.5.0-00 Full

Package -


RAID

8.5.0-02 Full

Package

-


Network Attached Storage 8.5.0-02 Full

Package -


SAN Switch

8.5.0-00 Full

Package

-


Microsoft(R) SQL Server

8.5.0-00 Full

Package

-


IBM DB2

8.5.0-00 Full

Package

-

Documents Hitachi Command Suite Tuning

Manager Installation Guide

MK-96HC141-33

Hitachi Command Suite Tuning

Manager Server Administration

Guide

MK-92HC021-43


Manager Agent Administration Guide

MK-92HC013-42

Hitachi Command Suite Tuning MK-95HC113-21

https://support.hds.com/en_us/contact-us.html

https://support.hds.com/en_us/contact-us.html

http://community.hds.com/

http://community.hds.com/



Manager Application Reports

Reference


Manager User Guide MK-92HC022-43


Manager Hardware Reports

Reference

MK-95HC111-31


Manager Operating System Reports

Reference

MK-95HC112-22


Manager Messages

MK-95HC114-33


Manager CLI Reference Guide MK-96HC119-33


Manager Getting Started Guide

MK-96HC120-24


Manager API Reference Guide

MK-92HC218-08

New features and important enhancements

For 8.5.0-00

# New Features and Enhancements Applied products Applied OS

1 The following Operating System is now supported:

- Red Hat Enterprise Linux 6.8

Tuning Manager

server

Agent for RAID

Agent for SAN

Switch

Agent for NAS

Linux


- Red Hat Enterprise Linux 7.2

Agent for SAN

Switch

Linux


- Oracle Linux 7.2

Tuning Manager

server

Agent for RAID

Agent for NAS

Linux


- SUSE Linux Enterprise Server 12 SP1

Agent for Server

System

Agent for SAN

Switch

Agent for NAS

Agent for Oracle

Linux


- Operation in a VMware Fault Tolerance environment

is now supported.

Tuning Manager

server

Tuning Manager

agents

Windows

Linux



6 The following NAS systems are now supported as

monitoring targets:

- Hitachi File Services Manager v5.4.0, 6.1.0, 6.1.1

Agent for NAS Windows

Linux

7 The following storage systems are now supported as

monitoring targets:

- VSP G200 (Firmware version: 83-04-0X)





- VSP G1500 (Firmware version: 80-05-0X)(*)

- VSP F400 (Firmware version: 83-04-0X)



- VSP F1500 (Firmware version: 80-05-0X)(*)

(*) VSP G1500 or VSP F1500 is now displayed as the

model name of the storage unit.

Tuning Manager

server

Agent for RAID

Agent for Server

System

All1

8 Viewing of the Tuning Manager server window is now

supported in an environment installed Adobe Flash

Player 23.

Tuning Manager

server

All1

9 The following NAS Platforms are now supported as

monitoring targets:

- HNAS4100 (Firmware version: 12.7, 13.0)






Agent for NAS All1

10 The Unified NAS modules of the following storage

systems are now supported as monitoring targets:







Agent for NAS All1

11 In the following records, you can now obtain settings

and amount of the data reduced when the dedupe and

compression is used.

- Pool Configuration (PD_PLC)

Settings of the dedupe and compression for pools

Amount of the data reduced when the dedupe and

compression is used for pools

- Virtual Volume Configuration(PD_VVC)

Settings of the dedupe and compression for a volume

Agent for RAID All1

12 For VSP Gx00 models and VSP Fx00 models, Tuning Agent for RAID All1



Manager now supports environments in which a single

SVP manages multiple DKCs.

13 The following Brocade switch is now supported as a

monitoring target:

- Network Advisor 14.0.x

Agent for Switch All1

14 For instance setup performed by using the jpcinssetup

command, the default value of the following items was

changed from N to Y:

- Unassigned Open Volume Monitoring (Y/N)

- Mainframe Volume Monitoring (Y/N)

Agent for RAID All1


- Windows Server 2016 Standard noSP (x64)

- Windows Server 2016 Datacenter noSP (x64)

Tuning Manager

server

Windows

16 Collecting performance data by using a TCP/IP

connection from storage systems of the following

microcode version is supported.

- HUS VM (73-03-49-XX/XX, 73-03-50-XX/XX)

- VSP (70-06-42-XX/XX, 70-06-43-XX/XX)

- VSP Gx00/Fx00 (83-03-07-XX/XX)

- VSP Gx00/Fx00 (83-03-24-XX/XX, 83-03-25-XX/XX)

- VSP Gx00/Fx00 (83-04-01-XX/XX)

- VSP G1000 (80-03-40-XX/XX)

- VSP G1000 (80-04-07-XX/XX, 80-04-08-XX/XX)

- VSP G1000 (80-04-23-XX/XX, 80-04-24-XX/XX)

- VSP G1000/G1500/F1500 (80-05-01-XX/XX)

Agent for RAID

All1

Note1: 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

For 8.5.0-00

# Resolved problems Applied products Applied OS

1 Overwrite installations or upgrade installations might

fail in Agent for RAID or Agent for NAS.

This problem might occur if overwrite installations or

upgrade installations are performed when all of the

Agent for RAID

Agent for NAS

Windows(

x64),

Linux(x6

4)



following conditions are met:

(1) Hybrid Store is used.

(2) There are many monitoring storage resources on

the same host.

(3) The value set for Collection Interval is too small.

2 If an attempt to start Tuning Manager - Agent REST

Web Service failed, information indicating the failure is

not output to the log.

This problem occurs if execution of the htmsrv

command fails.

Agent for RAID

Agent for NAS

Linux,

AIX, HP-

UX

3 When the OS stops, the stop script of the REST service

is not executed.

The following problem occurs.

In RHEL 6.x:

The stop script is not executed, because the

processing to deploy the service name file is not

implemented in /var/lock/subsys/.

In AIX:

The stop script is not executed, because the

processing to execute the stop script is not included in

/etc/rc.shutdown.

Agent for RAID

Agent for NAS

Linux,

AIX

4 The htmsrv command might not be able to start Agent

REST Application Service normally.

This problem occurs if all of the following conditions

are met:

(1) Either of the following is installed:

- Agent for RAID 8.0.0-00 or later

- Agent for NAS 8.2.1-00 or later

(2) Agent REST Service (Tuning Agent) is stopped.

(3) The htmsrv start -webservice command is

executed.

Agent for RAID

Agent for NAS

Windows,

Linux,

AIX, HP-

UX

5 When polling starts in an environment in which the

time zone is set to GMT+xx:yy or GMT-xx:yy (where

YY is not zero), no processor is displayed in the Tuning

Manager Main Console.


are met:

(1) Hybrid Store is used.

(2) The OS time zone is set to GMT+xx:yy or GMT-

xx:yy (where YY is not zero) in one of the following

environments:

In Windows:

- Caracas (GMT-04:30)

- Newfoundland (GMT-03:30)

- Tehran (GMT+03:30)

Agent for RAID Windows(

x64),

Linux(x6

4)



- Kabul (GMT+04:30)

- Sri Jayawardenepura (GMT+05:30)

- Chennai, Kolkata, Mumbai, New Delhi

(GMT+05:30)

- Kathmandu (GMT+05:45)

- Yangon (Rangoon) (GMT+06:30)

- Pyongyang (GMT+08:30)

- Adelaide (GMT+09:30)

- Darwin (GMT+09:30)

In Linux:

- Pacific/Marquesas (GMT-0930)

- America/Caracas (GMT-0430)

- America/St_Johns (GMT-0230)

- Asia/Kabul (GMT+0430)

- Asia/Tehran (GMT+0430)

- Asia/Colombo (GMT+0530)

- Asia/Kolkata (GMT+0530)

- Asia/Kathmandu (GMT+0545)

- Asia/Rangoon (GMT+0630)

- Indian/Cocos (GMT+0630)

- Australia/Eucla (GMT+0845)

- Australia/Adelaide (GMT+0930)

- Australia/Broken_Hill (GMT+0930)

- Australia/Darwin (GMT+0930)

- Australia/Lord_Howe (GMT+1030)(*)

- Pacific/Norfolk (GMT+1130)

- Pacific/Chatham (GMT+1245)

(*) Except during daylight saving time.

(3) Polling is performed at the appropriate time, as

shown below.

If the time zone is set to GMT+XX:YY:

Polling is performed from XX:00 to XX:YY local

time.

Example: The time zone is set to GTM+XX and the

polling time period is for an hour beginning at 0:00.

0:00 to (0:00 + 45 minutes) = From 0:00 to

0:45

If the time zone is set to GMT-XX:YY:

Polling is performed during the period from XX:00

to (XX + 1:00 - YY minutes).

Example: The time zone is set to GMT-3:15, and

the polling time period is for an hour beginning at

0:00.

0:00 to (1:00 - 15 minutes) = From 0:00 to 0:45

6 Symptom 1 or 2 shown below occurs when storage

system information is displayed in the Tuning Manager

Tuning Manager

server

Windows(

x64),



Main Console.

Symptom 1:

Processor information cannot be displayed.

- In the summary area, "0" is displayed for the

number of processors.

- The processor list in the information area displays

"No object".

- Processors cannot be displayed in a tree in the

navigation area.

Symptom 2:

The association between LDEVs and processors

cannot be displayed.

- The LDEV list displays "no data" for related

processors.

- The list of LDEVs related to processors displays

"No object".

Condition of occurrence for symptom 1:

Problem A occurs if the PI_PRCS record (in hours)

cannot be acquired from Agent for RAID during polling

on the Tuning Manager server.

Conditions of occurrence for symptom 2

Problem B occurs if all of the following conditions are

met:

(1) The type of the device being monitored by Agent

for RAID is VSP, VSP G1000, HUS VM, a VSP Gx00

model, or a VSP Fx00 model.

(2) During polling on the Tuning Manager server, the

PI_PRCS record (in hours) cannot be acquired from the

instance of Agent for RAID that is monitoring the

device in (1).

(3) During polling on the Tuning Manager server

performed after (2), the PI_PRCS record (in hours) is

acquired from the instance of Agent for RAID in (2).

Linux(x6

4)

7 Hitachi Command Suite products are vulnerable to a

denial of service (DoS) attack related to Apache

Commons FileUpload (CVE-2016-3092).

This problem might occur if a Hitachi Command Suite

product receives an invalid request from a malicious

third party.

Tuning Manager

server

Windows,

Linux

8 When the Server Priority Manager (SPM) group

settings are valid in a storage system, Agent for RAID

cannot collect performance data by using a TCP/IP

connection.


are met:

(1) Acquisition of performance data via TCP/IP is set to

Agent for RAID Windows(

x64),

Linux(x6

4)



ON. (For jpcinssetup, TCP/IP or "both" is specified.)

(2) The storage system contains a Server Priority

Manager (SPM) group.

(3) The PI_HBAS record is collected.

9 When the Copy-on-Write Snapshot secondary volume

and Thin Image secondary volume are displayed in the

Tuning Manager Main Console, POOL is displayed by

mistake in the Volume Attribute column.


are met:

(1) A storage system that contains the secondary

volume (V-VOL) of Copy-on-Write Snapshot or Thin

Image is being monitored.

(2) Polling for the storage system in (1) is performed

in the Tuning Manager Main Console.

(3) The Copy-on-Write Snapshot or Thin Image

secondary volume (V-VOL) in the storage system for

which polling was performed in (2) is displayed in the

Tuning Manager Main Console window or by using the

htm-logicaldisks command.

Tuning Manager

server

Windows,

Linux

10 When the htmsrv start -all command is executed,

Agent REST Web Service and Agent REST Application

Service do not start, performance data cannot be

summarized, and access via the Tuning Manager API is

disabled.


are met:

(1) Either or both of the following products are

installed:

- Agent for RAID 8.0.0-00 or later

- Agent for NAS 8.2.1-00 or later

(2) Either or both of the following conditions are met:

- Hybrid Store is used as the storage location for

the Performance database (in Windows and Linux

only).

- The Tuning Manager API is used.

(3) Either or both of the following services are

stopped:

- Agent REST Web Service

- Agent REST Application Service

(4) Because of an error in the Agent instance settings

or environment, some Agent instances successfully

start services, but other Agent instances fail to start

services on the same host.

(5) The htmsrv start -all command is executed.

Agent for RAID

Agent for NAS

Windows,

Linux,

AIX, HP-

UX

11 When an alarm is imported, no confirmation message

for overwriting the alarm appears.

This problem occurs when all of the following

conditions are met.

Tuning Manager

server

Linux



- LANG is not EUC.

- The alarm name to be imported by the jpctool alarm

import command contains multibyte characters.

- The alarm already exists.

- The jpcalarm import command is executed.

For 8.5.0-02

# Resolved problems Applied products Applied OS

1 Agent for RAID or Agent for NAS, once operated with

Store database and migrated to Hybrid Store, might

fail to upgrade to 8.5.0-00 or might fail to start HTnM

Agent services after having upgraded to 8.5.0-00.

This problem might occur when both of the following

conditions are met:

(1)Agent for RAID or Agent for NAS has once operated

with Store database and is then migrated to Hybrid

Store.

(2)The HTnM Agent is upgraded to 8.5.0-00.

Agent for RAID

Agent for NAS

Windows,

Linux

Known problems

# Known Problems Applied products Applied OS

1 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.

Tuning Manager

server

All1

2 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.

Agent for RAID

Agent for NAS

Windows,

Linux

3 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-

Agent for RAID

Agent for NAS

Linux



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.

4 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.



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:



2. Make sure that the host that executes the

upgrade can connect to the shared disk.

3. Start the upgrade.




Agent for RAID

Agent for NAS

Windows,

Linux





Component services.


webservice".

(Execute steps 2-6 for all hosts.)



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








5. Select [Transfer performance data after

installation] and finish installation.


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.



(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.



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.






Component services.


webservice".

(* If there are multiple standby hosts, execute

steps 7-11 for all standby hosts)




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:



software.









Component services.


webservice".



9. In the clustering software, register the script that

registers the Tuning Manager agents service.



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



software.






6. Select [Transfer performance data after

installation] and finish installation.


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.


9. In the clustering software, register the script that

registers the Tuning Manager agents service.



5 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

Agent for RAID

Agent for NAS

Windows,

Linux



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.


Resolved known problems

For 8.5.0-00

# Resolved known problems Applied products Applied OS

1 In the following environments, if you install the Tuning

Manager server or the Tuning Manager agents on an XFS

file system whose size exceeds 1 TB, the installation

might fail or startup of the service after the installation

might fail.

- Red Hat Enterprise Linux 7

- Oracle Linux 7

- SUSE Linux Enterprise Server 12

You can use one of the following methods to prevent this

problem:

(a) Use another file system such as ext4.

(b) If you do use XFS, use one of the following methods:

1. Split the partition so that the size of the file system

is less than 1 TB.

2. Mount the XFS file system by specifying the option

-o inode32.

Tuning Manager

server

Tuning Manager

agents

Linux

2 If Tuning Manager agents are used with Hybrid Store and

the disk space for the installation directory or the Hybrid

Store output directory is insufficient, the Tuning Manager

Agent REST API component might not start normally. To

avoid this, make sure that you estimate the necessary

disk space before performing operations.

Agent for RAID

Agent for NAS

Windows,

Linux



Installation precautions

Tuning Manager server and Tuning Manager agents

# Installation Precautions Applied products

Applied OS

1 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

Tuning

Manager

server

Tuning

Manager

agents

All1


Tuning Manager server


Applied OS

1 After installing the Tuning Manager server 8.5.0, 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.

Tuning

Manager

server

All1

2 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.

Tuning

Manager

server

Windows

3 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

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

Tuning

Manager

server

Windows

4 The following library was added as a prerequisite library for

Red Hat Enterprise Linux 6.5.

Apply this patch if you use Red Hat Enterprise Linux 6.5.

- upstart-0.6.5-13.el6_5.3.x86_64 or later

Tuning

Manager

server

Linux

5 Port numbers in the range from 24235 to 24242 were added

for use in Tuning Manager 8.5.0 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

All1



Tuning Manager Server Administration Guide

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

Tuning

Manager

server

All1


Tuning Manager agents


Applied OS

1 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.

Tuning

Manager

agents

Windows

2 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.

a. Specify an existing path. The path must be from 1 to 80

bytes long.

b. Specify an absolute path. Do not use the following:

- Symbolic link

- Network folder

- Network drive

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

spaces.

Do not use the following characters:

; , * ? ' " < > |

Agent for

RAID

Agent for

NAS

Windows,

Linux

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

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

Tuning

Manager

agents

All1




Upgrade precautions


# Upgrade Precautions Applied products Applied OS

1 If you upgraded the Tuning Manager server from version

6.0.0 to 6.4.0 to version 8.5.0, the Tuning Manager server

might take approximately 1 hour to start at the first time

after upgrade.

Tuning Manager

server All1

2 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

Tuning Manager

server

All1

3 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.

Tuning Manager

server Windows

4 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 1TB

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

Tuning Manager

server All1



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

Comp

osition

Backu

p

Import etc.

1 -Device

Manager,

-Tiered

Storage

Manager,

-

Replication

Manager

-

Volum

es:

128,0

00

-

Paths:

512,0

00

-

Hosts:

1,000

11 35 49

2 -Tuning

Manager 14 9 48

3 -Global

Link

Manager

-

Paths/

hosts:

1,000

-

Hosts:

60

-

Pathst

atuslo

g:

4GB

(total

capaci

ty)

2 7 43

4 -Compute

Systems

Manager

-

Chassi

s: 200

-

Blades

:

1,000

-

Hosts:

1,000

2 2 21



Table2 estimating time for installation (Linux)

units: minutes

# Product

name

Comp

osition

Backu

p

Import etc.

1 -Device

Manager,

-Tiered

Storage

Manager,

-

Replication

Manager

-

Volum

es:

128,0

00

-

Paths:

512,0

00

-

Hosts:

1,000

4 36 35

2 -Tuning

Manager 3 7 17

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

Tuning Manager

server

All1

6 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

(i) 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.

(ii) 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

Tuning Manager

server

Agent for RAID

Windows

Linux



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.

(iii) 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 DeviceManager

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.

In Windows:

jpcstart agtd inst=Agent-for-RAID-instance-name

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.

1. From the Administration menu, display the

Polling Settings screen.

2. In the agent list, select the objects to be

monitored.

3. 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.




1 To upgrade the version of Tuning Manager to 8.5.0 or later, Tuning Manager All1



you must also upgrade the Tuning Manager server and Tuning Manager agents running on the same host to version 8.5.0 or later.

agents

2 For Agent for SAN Switch 8.5.0 or later, a 64-bit edition of

the JDK is now required (rather than a 32-bit edition).

Therefore, in an environment where the Oracle JDK is used

to monitor Agent for SAN Switch, if Agent for SAN Switch is

upgraded to version 8.5.0 or later, the Oracle JDK is

automatically switched to the default JDK.

If you want to use the Oracle JDK, change the settings again after the version has been upgraded.

Agent for SAN

Switch

All1

3 In Windows or Linux, after Agent for Oracle is upgraded from

a version earlier than 8.5.0 to 8.5.0 or a later version, the

instance information must be updated. If you start an Agent

for Oracle service without updating the instance information,

the service abnormally stops with the following messages:

OS Error messages

Window

s

KAVF12020-E While executing function-name function called-function-name failed.

KAVF12023-E Agent Collector is going to stop because the error has occurred.

KAVF12004-E Agent Collector stopped

abnormally.

Linux KAVF12011-E Initialization of interprocess communication failed.

KAVF12021-E Error occurred by function functionname. (en=error-code,arg1=argument-1,arg2=argument-2,arg3=argument-3)

KAVF12023-E Agent Collector is going to stop because the error has occurred.

KAVF12004-E Agent Collector stopped abnormally.

For the sections where the instance information must be

updated, see Precautions for collecting the record with Agent

for Oracle.

If you upgrade Agent for Oracle from a version earlier than 8.5.0 to 8.5.0 or a later version, the 32-bit edition of Oracle Client will become unnecessary. You can uninstall Oracle Client if it is used with Agent for Oracle only.

Agent for Oracle Windows

Linux




Removal precautions


None.



1 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.

Tuning Manager

agents

Windows

2 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.

Tuning Manager

agents Windows

Linux

Usage precautions

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

# Usage Precautions Applied products Applied OS

1 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.

Tuning Manager

server

Windows



Notes on the use of Performance Reporter when using Internet Explorer 9 or later on Windows Server 2008:


1 If you move the Message dialog box in the browser, an

image of the Message dialog box might remain displayed

in the pre-move location. If this displayed image

remains, close the Message dialog box by clicking the

[OK] or [Cancel] button in the Message dialog box.

Tuning Manager

server

Windows

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


1 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.

Tuning Manager

server

Windows

Precautions for displaying a list of installed programs



1 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

server

Windows


None.

Precautions for monitoring Brocade SAN switches


None.





1 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.

Agent for SAN

Switch

Applies to

all

supported

operating

systems

2 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.

Agent for SAN

Switch

Applies to

all

supported

operating

systems

Notes for trouble on an operation of Agent for SAN Switch


None.



1 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.

Agent for SAN

Switch

Applies to

all

supported

operating

systems

Precautions for displaying a correlation reports



1 Even if a system failover is performed by High

Availability Manager functionality for the Universal

Storage Platform V/VM series, Virtual Storage Platform,

Virtual Storage Platform G1000 or Virtual Storage

Platform Gx00 series, the Tuning Manager server

continues to display the active volume, not the standby

volume, as related to the relevant device file.

Tuning Manager

server

Applies to

all

supported

operating

systems




None.

Precautions for monitoring a storage system



1 If LDEVs are being configured by combining various

LDEVs in multiple parity groups in a LUSE configuration,

the [Write Hit Ratio] of the parity groups might

temporarily exceed 100% depending on the level of

measurement error used by the storage system. (In such

a case, treat the value that exceeds 100% as 100%.)

This problem might occur while the Thunder 9200 series,

the Thunder 9500V series, or the Hitachi AMS/WMS

series is being monitored.

Tuning Manager

server

Applies to

all

supported

operating

systems


None.

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



1 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 Virtualiz

ation

server

Oracle

(a) * Relevant

information

between storage

components is not

properly

Tuning Manager

server

Applies to

all

supported

operating

systems



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.

(d) * * Relevant

information

between hosts

and Oracle 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:

1. Conditions

This error might occur if either of the following

operations is performed:

(a) Operation 1:

(i) Add the devices indicated by * in Table-1 (b), (c), or

(d) to the list of targets to be monitored by the Tuning

Manager server. Then, refresh the list of Agents on the

Tuning Manager server.

(ii) From the Tuning Manager server, perform automatic

or manual polling on the monitoring targets that were

added in step (i).

(iii) 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:

[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.

[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).

(iv) Refresh the list of Agents on the Tuning Manager

server.



(v) Add the monitoring targets that were deleted in step

(iii) and whose configurations have not been changed

since step (iii) to the list of targets to be monitored by

the Tuning Manager server again by using one of the


[For storage devices]

- Add Agent for RAID to the list of targets to be


- Add the storage devices to Device Manager.

[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).

(vi) Refresh the list of Agents on the Tuning Manager

server.

(vii) From the Tuning Manager server, perform automatic

or manual polling again on the monitoring targets on

which polling was performed in step (ii).

(b) Operation 2:

(i) 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.

(ii) From the Tuning Manager server, perform automatic

or manual polling on the monitoring targets that were

added in step (i).

(iii) 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.

(iv) From the Tuning Manager server, perform automatic



(v) For the monitored storage devices indicated in step

(iii), restore them to their status before step (iii).

(vi) From the Tuning Manager server, perform automatic



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

1 Operation 1 Table-1 (b), (c), and (d)

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



2. 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 Recovery

procedure

1 The error occurs on a host that

is being monitored in agentless

mode.

Procedure 1

2 The error occurs on a

virtualization server.

Procedure 2

3 In cases other than 1 and 2. Procedure 3

(a) Procedure 1:

(i) Remove from Device Manager the storage device that

contains volumes that are connected to the host.

(ii) Use Device Manager to refresh the host indicated in

step (i).

(iii) From the Tuning Manager server, perform manual

polling on Device Manager.#1

(iv) Add the storage device that was removed from

Device Manager in step (i) to Device Manager again.

(v) Use Device Manager to refresh the host indicated in

step (i) again.

(vi) From the Tuning Manager server, perform manual


#1: Be sure to wait at least one hour after the last

polling was performed before you perform manual

polling.

(b) Procedure 2:

(i) 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:

- Delete Agent for RAID from the list of targets to be


- Remove the storage devices from Device Manager.

(ii) From the Tuning Manager server, perform manual

polling on the Device Manager that manages the

virtualization server indicated in step (i).#1

(iii) Add the storage device that was removed from the

list of targets to be monitored by the Tuning Manager

server in step (i) to the list of monitoring targets again.

- Add Agent for RAID to the list of targets to be


- Add the storage devices to Device Manager.



(iv) From the Tuning Manager server, perform manual




polling.

(c) Procedure 3:

(i) Delete the monitoring targets whose information is

not properly displayed from the list of targets to be


(ii) Add the monitoring targets that were removed in

step (i) to the list of targets to be monitored by the

Tuning Manager server again.

(iii) From the Tuning Manager server, perform manual

polling on the Tuning Manager Agents that monitor the

added targets.#1



polling.


None.

Precautions for displaying a report with the Tuning Manager server



1 When all of the following conditions are met, the

hyperlink for a related host is not displayed on a report

displayed by procedures described in the [How to display

a report].

[Conditions]

(1) Connect the Agent for Oracle to the Tuning Manager

server.

(2) Monitor the host in which the Agent for Oracle has

been installed by the Agent for Server System.

(3) The hostname mentioned in (2) contains a lower-

case letter.

[How to display a report]

(a) Select the Resources - Applications in the Explorer

area.

(b) Select the Oracle in the Navigation area.

(c) Select the Oracle Instances tab in the Information

Tuning Manager

server

Applies to

all

supported

operating

systems



area (Correlation View).

If you want to display a report for the host related to an

Oracle instance, select the host from the resource tree.


None.

Precautions for collecting the record with Agent for Oracle


None.



1 In Windows or Linux, Agent for Oracle version 8.5.0 or later

monitors Oracle Database by using the 64-bit edition of the

Oracle Client library that is bundled with Oracle Database.

However, Agent for Oracle versions earlier than 8.5.0 use

the 32-bit edition of the Oracle Client library. The table

below describes differences in the instance information

settings between versions earlier than 8.5.0 and version

8.5.0 or later. Note that Agent for Oracle version 8.5.0 or

later cannot connect to Oracle Database with the settings

that were used in versions earlier than 8.5.0. In version

8.5.0 or later, therefore, you must set the 64-bit edition of

the Oracle Client library.

Item Version of Agent for Oracle

Earlier than 8.5.0 8.5.0 or later

oracle_home Specify the Oracle

home of the 32-bit

edition of Oracle

Client.

Specify the

Oracle home of

Oracle Database.

oracle_versio

n

Specify the

version of the 32-

bit edition of

Oracle Client.

Specify the

version of Oracle

Database.

sqlnet Specify [Y]. Specify [Y] in one

of the following

cases:

1. When the

Oracle RAC

Agent for Oracle Windows

Linux



configuration is

used.

For details about

the RAC

configuration, see

the

documentation

for Oracle.

2. When the

PD_PDIA record

is used to monitor

the availability of

listeners.

3. When any

Oracle service is

operating with an

account that is

not the Local

System Account.

If you specify [N]

in case 1 or 3, an

error might occur

in Oracle.

net_service_

name

Specify the name

of a net service

that can connect

to the monitored

Oracle Database

set in the 32-bit

edition of Oracle

Client.

Specify this item

only if [Y] is

specified for

sqlnet. Specify

the name of a net

service that can

connect to the

monitored Oracle

Database set in

the monitored

Oracle Database.

Precautions for changing a command device name in an AIX environment


None.



1 In an environment where AIX v6.1 or AIX v7.1 is Tuning Manager AIX



installed, if the command device name specified to the

"Command Device File Name" item is changed to other

than the following format, the performance information

cannot be collected from Storage System.

Therefore, specify the name according to the following

format to the rendev command as the command device

name after change.

[Format of the command device name]

"hdisk" + (Arbitrary half-width alphanumeric characters)

agents

Notes applying when Load Reduction for Changing Configuration Mode is enabled in a Hitachi AMS2000 series or Hitachi SMS series storage system



1 When the Tuning Manager server is monitoring a Hitachi

AMS2000 series or Hitachi SMS series storage system

with "Load Reduction for Changing Configuration Mode"

enabled, the following problems might occur if the

configuration of the system is changed:

(1) Collection of performance data fails.

(2) Polling fails.

To prevent these problems from occurring, before you

change the storage system configuration, stop the

services of the Tuning Manager server and the Agent for

RAID instance that is monitoring the storage system, and

restart these services after the configuration has been

changed.

Tuning Manager

server,

Agent for RAID

All1


Precautions for displaying a vendor name of the switch



1 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.

Tuning Manager

server,

Agent for SAN

Switch

All1



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



1 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.

Tuning Manager

server,

Tuning Manager

agents

Windows



To start Service Control Manager, from the Windows

Start menu, select Administrative Tools, and then

select Services.

Precautions for installation folder



1 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.

Tuning Manager

server,

Tuning Manager

agents

Windows

Notes on InPrivate Browsing of Internet Explorer 9.0


1 During InPrivate Browsing Mode, the browsing history

might remain in the browser.

Tuning Manager

server

Windows

Notes on enabling SSL(*1) between the Tuning Manager server and management clients when using Firefox


1 To enable SSL between the Tuning Manager server and

management clients by using Firefox, perform the


(1) Disable SSL between the Tuning Manager server and

management clients.

(2) register the license files

(3) Enable SSL between the Tuning Manager server and

management clients.

Tuning Manager

server

Linux

Note1: For details about enabling SSL, see "Security settings for Common

Component (communication with the GUI)" in the Hitachi Command Suite Administrator Guide.



Notes of using Firefox ESR 45


1 When using Firefox ESR 45 to browse Tuning Manager

GUI, the following Flash Player is required.

- Flash Player 10.3 to earlier than 11

- Flash Player 11.2

Tuning Manager

server

Linux

Notes of using Firefox or Chrome


1 When the browser being used is Firefox or Chrome, in

some cases the Close button of the Main Console does

not work in Tuning Manager. In this case, close the

browser window itself.

Tuning Manager

server All1


Notes of using Chrome


1 When the browser being used is Chrome, 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 Chrome 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.

Tuning Manager

server

Windows

Notes of the Server Core option of Windows


1 Server Core mode is not supported.

Tuning Manager

server,

Tuning Manager

agents

Windows



Notes of the Minimal Server Interface of Windows Server 2012


1 Minimal Server Interface is not supported. Tuning Manager

server,

Tuning Manager

agents

Windows

When the Tuning Manager service does not start or stop


1 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.

Tuning Manager

server,

Tuning Manager

agents

All

Monitoring Windows hosts


1 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.

Note that, when a host with Windows Server 2012 is

Agent for Server

System

Windows



monitored, CPU information might not be able to be

collected for more than 40 CPUs.

Operating in a Red Hat Enterprise Linux 6.2 or Oracle Linux 6.2 environment


1 In a Red Hat Enterprise Linux 6.2 or Oracle Linux 6.2

environment, the "jpcras<YYMMDD>.tar.Z" file created

by the jpcras command may be unable to be extracted.

This is because there is a problem in the ncompress

package shown below.

- ncompress-4.2.4-54.el6

Therefore, when you use this product in a Red Hat

Enterprise Linux 6.2 or Oracle Linux 6.2 environment,

perform either of the following procedures:

(1) Do not install the ncompress package. Or when the

ncompress package is already installed, remove it.

Note: If the ncompress package does not exist, the

jpcras command compresses the files by the gzip

command.

(2) When the following fixed version can be obtained,

update it.

- ncompress-4.2.4-54.el6_2.1

Tuning Manager

server,

Agent for RAID ,

Agent for Server

System,

Agent for Switch,

Agent for DB2,

Agent for Oracle

Linux

Precautions when installing on Windows Server 2012 or 2016


1 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.

Tuning Manager

server,

Tuning Manager

agents

Windows

Precautions for monitoring the HUS100 series


1 When the monitoring target storage system is the

HUS100 series with "packet filtering" function enabled,

perform either of the following procedures:

- Disable "NetBIOS over TCP/IP" on Windows.

- When "NetBIOS over TCP/IP" on Windows cannot be

disabled, before executing the maintenance-material-

acquisition command, stop Agent for RAID and Device

Agent for RAID Windows



Manager. Wait for 5 minutes, and then execute the

command.

And when executing the netstat command, specify "-n"

option.

Note on using Tuning Manager on a Linux server


1 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.

Tuning Manager

server Linux

Precautions for collecting the record with Agent for Microsoft Exchange Server


1 To use Agent for Microsoft Exchange Server for

monitoring, Mailbox Role for the Microsoft Exchange

Server must be installed.

Agent for

Microsoft

Exchange Server

All1


Precautions for monitoring the NAS Platform


1 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.

Agent for NAS All1


Notes on using Hybrid Store


1 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.

Agent for RAID

Agent for NAS

Windows,

Linux



For details about the amount of memory for Agent for

RAID, see the Hitachi Command Suite System

Requirements (MK-92HC209).

2 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).

Agent for RAID

Agent for NAS

Windows,

Linux

Notes on using SUSE Linux Enterprise Server


1 When a file system setting is btrfs that is default setting

on SUSE Linux Enterprise Server 12, value of PD_FSL

and PD_FSR record might be incorrect.

Agent for Server

System

Linux

Notes on the alert function


1 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.

Tuning Manager

server

All1


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


1 The prerequisite checker creates the following directories

when checking the prerequisites:

Tuning Manager

server

Linux



- <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


1 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:

Tuning Manager

agents

Windows,

Linux



/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 when the Legacy DSF path name is invalid in an HP-UX environment


1 If the Legacy DSF path name#1 is invalid in an HP-UX

environment, and if only the Persistent DSF path name#2

is valid, the execution results for the jpctdlistraid

command of Agent for RAID might not show the

command device file name.

In this case, perform the following procedure to specify

the Command Device File Name when setting an

instance.

(1) Execute the ioscan -Nkfnd esdisk command.

Copy the Persistent DSF device file name of the

command device for the storage system from the

command execution results.#3

[Command example]

ioscan -Nkfnd esdisk

Class I H/W Path Driver S/W State H/W Type Description

===================================

================================

disk 5 64000/0xfa00/0x9 esdisk CLAIMED DEVICE

HITACHI OPEN-V-CM

/dev/disk/disk5 /dev/rdisk/disk5

(2) Specify the device file name copied in (1) to specify

the Command Device File Name when creating the

instance (example: /dev/rdisk/disk5).

(3) Execute the jpctdchkinst command for the instance

created in (2) to make sure that the specified storage

system is correct.

Agent for RAID HP-UX

#1: Path name with the /dev/rdsk/cXtXdX format

#2: Path name with the /dev/rdisk/diskX format



#3: The device shown by -CM in the description is the command device. In the

above example, copy the device name of /dev/rdisk/disk5.

Precautions for monitoring a host in agentless mode Tuning Manager server


1 When virtual IDs are assigned to volumes for using a

virtual storage machine, the volumes cannot be

monitored in agentless mode.

Tuning Manager

server All1


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


1 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:

- Suppressing failover when upgrading or

overwriting Hitachi Command Suite (Windows)

For 8.2.0-00 or later:

- Taking Hitachi Command Suite services offline

Tuning Manager

server

Windows,

Linux



(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 or AIX hosts in the global-active device configuration using Agent for Server System


1 If an AIX or Windows host monitored by Agent for Server Agent for Server Windows,



System uses a disk or device special file in the global-

active device (GAD) configuration, 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.

System AIX

Precautions for using Internet Explorer 11


1 To use the GUI on Windows Server 2016, the Flash

Player must be enabled if both of Tuning Manager and

Device Manager are installed on the same server or

charts of the historical report or the forecast report in

the Main Console can be viewed using Flash Player.

To enable the Flash Player, perform the following

procedure or add a role of Remote Desktop Session

HOST in the operating system. If you add the role, there

is no need to execute the command.

1. Start a command prompt as an administrator.

2. Run the following command.

- Dism /online /add-package

/packagepath:C:\Windows\servicing\Packages\Adobe-

Flash-For-Windows-

Package~31bf3856ad364e35~amd64~~10.0.14393.0.m

um

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 HSC 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 HCS 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.

Tuning Manager

server

Windows



Temporary Restrictions

# Temporary Restrictions Applied products Applied OS

1 When installed on a Windows Server 2016 host, the

Tuning Manager server displays incorrect operating

system information about the host as follows.

- The OS Version property of Collection Manager services

is wrongly shown as "6.03.9600", not correctly as

"10.0.14393".

- The OS Name property of Collection Manager services

is wrongly shown as "Win2012", not correctly as

"Windows".

Tuning Manager

server Windows

Documentation

Available documents

Document name Document number

Issue Date

Hitachi Command Suite Tuning Manager Installation Guide MK-96HC141-33 October

2016

Hitachi Command Suite Tuning Manager Server

Administration Guide

MK-92HC021-43 October

2016

Hitachi Command Suite Tuning Manager Agent

Administration Guide


2016

Hitachi Command Suite Tuning Manager Application Reports

Reference


2016

Hitachi Command Suite Tuning Manager User Guide MK-92HC022-43 May 2016

Hitachi Command Suite Tuning Manager Hardware Reports

Reference


2016

Hitachi Command Suite Tuning Manager Operating System

Reports Reference MK-95HC112-21 October

2016

Hitachi Command Suite Tuning Manager Messages MK-95HC114-33 October

2016

Hitachi Command Suite Tuning Manager CLI Reference Guide MK-96HC119-33 October

2016

Hitachi Command Suite Tuning Manager Getting Started

Guide MK-96HC120-24 November

2015

Hitachi Command Suite Tuning Manager API Reference Guide MK-92HC218-08 October

2016



Documentation errata

The Hitachi Tuning Manager User Guide is 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.

For 8.5.0-00

Contents of corrections of the Hitachi Command Suite Tuning Manager User

Guide:

Location to be corrected: Multiple pages

Existing content:

VSP G1000

Revised content:

VSP G1000, G1500, VSP F1500

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.

:




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

• 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

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


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.


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.


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.

From 8.5.0-00 Rev.0 to 8.5.0-00 Rev.1

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

No. Location

to be corrected

Corrections

1 Installing or

upgrading the

Tuning

Manager

server

Adding the

Tuning

Manager

server to the

exceptions list

Before 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:


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



No. Location

to be corrected

Corrections

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

- The Programs and Services list contains cjstartweb.exe.

- 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




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"

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


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:

-For Windows Server 2008 R2

[Allow an program or feature through Windows Firewall] - [Allow programs to communicate through Windows Firewall] - [Allow another program...] - [Add a program]

-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]




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





No. Location

to be corrected

Corrections

-For Windows Server 2008 R2

[Allow a program or feature through Windows Firewall] - [Allowed programs and features:]

-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:

- cjstartsv is displayed.

- 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




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"

Copyrights and licenses

© 2016 Hitachi, Ltd. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, or

stored in a database or retrieval system for any purpose without the express written permission of Hitachi, Ltd.

Hitachi, Ltd., reserves the right to make changes to this document at any time without notice and assumes no responsibility for its use. This document contains

the most current information available at the time of publication. When new or



revised information becomes available, this entire document will be updated and

distributed to all registered users.

Some of the features described in this document might not be currently available.

Refer to the most recent product announcement for information about feature and product availability, or contact Hitachi, Ltd., at

https://support.hds.com/en_us/contact_us.html.

Notice: Hitachi, Ltd., products and services can be ordered only under the terms

and conditions of the applicable Hitachi Data Systems Corporation agreements. The use of Hitachi, Ltd., products is governed by the terms of your agreements

with Hitachi Data Systems Corporation.

By using this software, you agree that you are responsible for:

1) Acquiring the relevant consents as may be required under local privacy laws or

otherwise from employees and other individuals to access relevant data; and

2) Verifying that data continues to be held, retrieved, deleted, or otherwise

processed in accordance with relevant laws.

Hitachi is a registered trademark of Hitachi, Ltd., in the United States and other

countries. Hitachi Data Systems is a registered trademark and service mark of Hitachi, Ltd., in the United States and other countries.

Archivas, Essential NAS Platform, HiCommand, Hi-Track, ShadowImage,

Tagmaserve, Tagmasoft, Tagmasolve, Tagmastore, TrueCopy, Universal Star Network, and Universal Storage Platform are registered trademarks of Hitachi

Data Systems Corporation.

AIX, AS/400, DB2, Domino, DS6000, DS8000, Enterprise Storage Server, ESCON,

FICON, FlashCopy, IBM, Lotus, MVS, OS/390, RS/6000, S/390, System z9, System z10, Tivoli, VM/ESA, z/OS, z9, z10, zSeries, z/VM, and z/VSE are

trademarks of International Business Machines Corporation, registered in many jurisdictions worldwide.

All other trademarks, service marks, and company names in this document or

website are properties of their respective owners.

Microsoft product screen shots are reprinted with permission from Microsoft

Corporation.

Notice on Export Controls. The technical data and technology inherent in this

Document may be subject to U.S. export control laws, including the U.S. Export Administration Act and its associated regulations, and may be subject to export

or import regulations in other countries. Reader agrees to comply strictly with all such regulations and acknowledges that Reader has the responsibility to obtain

licenses to export, re-export, or import the Document and any Compliant

Products.

https://support.hds.com/en_us/contact_us.html